Oracle® Fusion Middleware

Error Messages Reference

11g Release 1 (11.1.1.7.0)

E10113-10

February 2013

Oracle Fusion Middleware Error Messages Reference, 11g Release 1 (11.1.1.7.0)

E10113-10

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

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

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

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

U.S. GOVERNMENT 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 America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

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

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

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

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

Contents

Preface

- Audience

- Documentation Accessibility

- Conventions

1 ADF_FACES-00001 to ADF_FACES-60098

2 ADF-MNC-10000 to ADF-MNC-50073

3 ADF_TRINID-00001 to ADF_TRINID-30336

4 ADFC-00001 to ADFC-14016

5 ADFDI-00100 to ADFDI-55516

6 ADFF_BIND-00001 to ADFF_BIND-00046

7 APM-10000 to APM-10015

8 ASCRS-00001 to ASCRS-00143

9 BAM-00001 to BAM-07041

10 B2B-50006 to B2B-53011

11 BEA-000001 to BEA-2163006

12 BDSS-00000 to BDSS-65160

13 BI-DCBEANS-00001 to BI-DCBEANS-00017

14 BI-DCWBSVC-05001 to BI-DCWBSVC-05079

15 BI-EUL-00001 to BI-EUL-00002

16 BI-PDFRDR-02001 to BI-PDFRDR-02047

17 BI-PLUS-00001 to BI-PLUS-00050

18 BI-POPVD-00001 to BI-POPVD-00053

19 BI-SVR-00300 to BI-SVR-03964

20 BI-VIEWER-00001 to BI-VIEWER-01245

21 BIACM-00007 to BIACM-00082

22 BPM-09708 to BPM-40011

23 BRW-15000 to BRW-16976

24 CFGFWK-20300 to CFGFWK-69510

25 CLONE-20200 to CLONE-53030

26 CONF-30000 to CONF-35141

27 DFW-40004 to DFW-40204

28 DIP-00003 to DIP-87002

29 DISCMAN-00100 to DISCMAN-90001

30 DMS-50700 to DMS-58073

31 DVT-02012 to DVT-26021

32 ECSF-10001 to ECSF-13310

33 EM-00251 to EM-02804

34 ENS-00000 to ENS-00213

35 EPMBPMUI-00101 to EPMBPMUI-01804

36 EPMFR-00001 to EPMFR-00356

37 EPMWKSP-00101 to EPMWKSP-02508

38 ESS-00001 to ESS-09408

39 FED-10104 to FED-18084

40 FEDSTS-10102 to FEDSTS-20100

41 FRC-60000 to FRC-60107

42 FRM-41838 to FRM-99999

43 FTS-40001 to FTS-40006

44 HELP-00001 to HELP-40001

45 IAU-01023 to IAU-62023

46 IFS-47010 to IFS-47091

47 INST-01000 to INST-10117

48 IRM-00001 to IRM-03012

49 J2EE HTTPC-00004 to J2EE HTTPC-12011

50 J2EE JMX-46000 to J2EE JMX-47006

51 J2EE JOC-00001 to J2EE JOC-00859

52 J2EE JSP-00002 to J2EE JSP-00302

53 JBO-24000 to JBO-80008

54 JPS-00001 to JPS-90642

55 JRF-10001 to JRF-20030

56 MAPVIEWER-00001 to MAPVIEWER-06057

57 MDS-00001 to MDS-91023

58 MODPLSQL-00001 to MODPLSQL-00868

59 OAAM-00000 to OAAM-94100

60 OAMAP-60501 to OAMAP-60521

61 OAM-00001 to OAM-36105

62 OAMCFG-60001 to OAMCFG-60085

63 OAMSSA-00001 to OAMSSA-22030

64 OBI_OFFICE-00001 to OBI_OFFICE-00077

65 ODF-10000 to ODF-15222

66 ODI-01100 to ODI-40960

67 ODL-52001 to ODL-52807

68 ODSM-00001 to ODSM-01007

69 ODV-00000 to ODV-00172

70 OID-03053 to OID-23737

71 OHS-03501 to OHS-03813

72 OPM-00500 to OPM-00745

73 ORABPEL-00006 to ORABPEL-20511

74 ORAMED-01001 to ORAMED-09001

75 OSSOIAP-90001 to OSSOIAP-90005

76 OVD-00001 to OVD-80015

77 OWS-00001 to OWS-65005

78 PKI-01001 to PKI-07007

79 PROV-40000 to PROV-40000

80 RCS-00001 to RCS-23000

81 RCU-06000 to RCU-06138

82 REP-00001 to REP-80012

83 RTD-10001 to RTD-10532

84 RUL-00000 to RUL-09043

85 SDF-10001 to SDF-10601

86 SDP-25001 to SDP-26455

87 SOA-00000 to SOA-31033

88 SSL-28750 to SSL-29249

89 SSLCFG-00131 to SSLCFG-00202

90 STS-10506 to STS-15541

91 TCM-00006 to TCM-99009

92 TOP-00001 to TOP-72023

93 TPC-00001 to TPC-90022

94 TRS-10000 to TRS-30030

95 UCM-CS-000001 to UCM-CS-800279

96 UCS-45209 to UCS-45412

97 UIX-00001 to UIX-00025

98 UPGAST-00001 to UPGAST-02007

99 UPGCMP-00019 to UPGCMP-06005

100 WCS-03051 to WCS-47826

101 WOR-70021 to WOR-70229

102 WSM-00001 to WSM-09024

103 WWC-00000 to WWC-59083

104 WWS-18000 to WWS-33951

105 WWU-52262 to WWU-83028

106 WWV-00100 to WWV-61294

107 WXE-00010 to WXE-21271

108 XDF-10001 to XDF-10571

Preface

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

Audience

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

Documentation Accessibility

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

Access to Oracle Support

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

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

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

italic

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

monospace

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

1 ADF_FACES-00001 to ADF_FACES-60098

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

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

Cause: The RegionModel was incorrectly subclassed.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

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

Cause: Marshalling from client to server was invalid.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

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

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

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

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

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

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

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

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

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-00008: A null QueryModel object was found.

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: NOTIFICATION

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

Cause: No TimeZone information exists for this Locale.

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

Type: WARNING

Impact: Logging

ADF_FACES-10001: No representationClass provided.

Cause: An illegal argument was passed to framework.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-10002: wrappedEvent

Cause: An illegal argument was passed to framework.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-10003: Basename is null.

Cause: Application never called setBaseName().

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-10004: No null numbers allowed in NumberRange.

Cause: An illegal argument was passed to framework.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-10005: unregistered key: {0}

Cause: An illegal argument was passed to framework.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

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

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

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

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

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

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-10008: Parent cannot be null.

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

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-10011: attempt to add a duplicate ID

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

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

Type: ERROR

Impact: Logging

ADF_FACES-10012: Allowed actions must be specified.

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-10013: Attempt to unsecure an always secured attribute

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

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

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

Action: Contact Oracle Support Services.
Level: 2

Type: ERROR

Impact: Logging

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

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

Action: Contact Oracle Support Services.
Level: 2

Type: ERROR

Impact: Logging

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

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

Action: Contact Oracle Support Services.
Level: 2

Type: ERROR

Impact: Logging

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

Cause: An unhandled exception in page template context setup.

Action: Contact Oracle Support Services.
Level: 2

Type: ERROR

Impact: Logging

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

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

Action: Contact Oracle Support Services.
Level: 2

Type: ERROR

Impact: Logging

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

Cause: An unhandled exception in include component context setup.

Action: Contact Oracle Support Services.
Level: 2

Type: ERROR

Impact: Logging

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

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

Action: Contact Oracle Support Services.
Level: 2

Type: ERROR

Impact: Logging

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

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

Action: Contact Oracle Support Services.
Level: 2

Type: ERROR

Impact: Logging

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

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

Action: Contact Oracle Support Services.
Level: 2

Type: ERROR

Impact: Logging

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

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

Action: Contact Oracle Support Services.
Level: 2

Type: ERROR

Impact: Logging

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

Cause: AdfFacesContextImpl was not found on the class path.

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

Type: ERROR

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

Cause:

Action:
Level: 1

Type: WARNING

Impact: Logging

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

Cause: An error occurred in the ActiveModel implementation.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

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

Cause: An error occurred in the ActiveModel implementation.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

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

Cause: An error occurred in the ActiveModel implementation.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

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

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

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

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

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

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

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

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

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

Cause: Drop listener threw an exception.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

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

Cause: Drop listener threw an exception.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

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

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

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

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

Cause: CollectionDragSource was not attached to UIXCollections.

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

Type: WARNING

Impact: Logging

ADF_FACES-30027: invalid align value: {0}

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: ERROR

Impact: Logging

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

Cause: A column was used outside of a table.

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

ADF_FACES-30037: expected script element: {0}

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

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

Type: ERROR

Impact: Logging

ADF_FACES-30038: illegal component hierarchy detected

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

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

Type: ERROR

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

Cause: No mode was set on QueryDescscriptor.

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

Type: ERROR

Impact: Logging

ADF_FACES-30046: A null QueryDescriptor object was found.

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

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

Type: WARNING

Impact: Logging

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

Cause: A ClientComponent is required where none is supported.

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

ADF_FACES-30049: overwriting preexisting page flow scope parameters

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

Action: Ensure the parameters are valid.
Level: 1

Type: WARNING

Impact: Logging

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

Cause: No viewRoot was set.

Action: Check servlet filter order.
Level: 1

Type: ERROR

Impact: Logging

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

Cause: No group attribute was set on selectBooleanRadio.

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

Type: WARNING

Impact: Logging

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

Cause: The property was not an integer.

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

Type: WARNING

Impact: Logging

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

Cause: State of the shuttle was corrupted.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

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

Cause: Table contains no visible columns.

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

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

Action: Remove the table width attribute.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30059: unknown table fetch type

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

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

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

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

Action: Correct the train definition.
Level: 1

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

Cause: The parent stop label was null.

Action: Add a stop label.
Level: 1

Type: WARNING

Impact: Logging

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

Cause: No nodeStamp facet was specified on treeTable.

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: ERROR

Impact: Logging

ADF_FACES-30067: Multithreaded execution was interrupted.

Cause: Execution of the multithreaded streaming request was interrupted.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-30068: multithreaded execution exception

Cause: The model threw an exception during multithreaded rendering.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

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

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

Action: Specify a valid component ID.
Level: 1

Type: ERROR

Impact: Logging

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

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

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

Type: ERROR

Impact: Logging

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

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

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

Type: ERROR

Impact: Logging

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

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

Action: Correct the returnActionListener .
Level: 1

Type: ERROR

Impact: Logging

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

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

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

Type: ERROR

Impact: Logging

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

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

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

Type: ERROR

Impact: Logging

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

Cause: Application configured to run in development mode.

Action: No action needed.
Level: 1

Type: NOTIFICATION

Impact: Logging

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

Cause: A required component attribute is not specified.

Action: Ensure all attributes are defined.
Level: 1

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

Cause: The include metadata attribute name was not specified.

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

Type: WARNING

Impact: Logging

ADF_FACES-30082: exception at: {0}

Cause: An exception occurred when parsing the include metadata.

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

Type: ERROR

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

Cause: The JSP to include could not be found.

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

Type: ERROR

Impact: Logging

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

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

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

Type: ERROR

Impact: Logging

ADF_FACES-30086: Cannot find parent include component.

Cause: Cannot find parent include component.

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

Type: ERROR

Impact: Logging

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

Cause: The URI of the include was null.

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

Type: ERROR

Impact: Logging

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

Cause: XmlContentTag is missing an end tag.

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

Type: WARNING

Impact: Logging

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

Cause: No root element was started on XmlContentTag.

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

Type: WARNING

Impact: Logging

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

Cause: XmlContentTag had no root element.

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

Type: WARNING

Impact: Logging

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

Cause: No XML namespace found for prefix.

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

Type: WARNING

Impact: Logging

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

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

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

Type: ERROR

Impact: Logging

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

Cause: Specified resource was not found in classpath.

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

Type: WARNING

Impact: Logging

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

Cause: Marshalling of StateHolders not supported and was skipped.

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

Type: WARNING

Impact: Logging

ADF_FACES-30096: Unmarshaling of StateHolders not yet supported.

Cause: Unmarshaling of StateHolders not supported.

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

Type: WARNING

Impact: Logging

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

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

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

Type: ERROR

Impact: Logging

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

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

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

Type: ERROR

Impact: Logging

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

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

Action: Do not use this element.
Level: 2

Type: ERROR

Impact: Logging

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

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

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

Type: ERROR

Impact: Logging

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

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

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

Type: ERROR

Impact: Logging

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

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

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

Type: ERROR

Impact: Logging

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

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

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

Type: ERROR

Impact: Logging

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

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

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

Type: ERROR

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

ADF_FACES-30110: export requires HTTP Servlet

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

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

Type: ERROR

Impact: Logging

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

Cause: exportCollectionActionListener used with invalid collection.

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

Type: ERROR

Impact: Logging

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

Cause: Unsupported export type was specified.

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

Type: ERROR

Impact: Logging

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

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

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

Type: ERROR

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: ERROR

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

Cause: Multiple af:skipLinkTargets were found.

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

Cause: Unsupported exported rows type was specified.

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

Type: ERROR

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

Cause: A partition element contained an unknown feature.

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

Type: WARNING

Impact: Logging

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

Cause: A circular dependency exists between partitions.

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

Type: WARNING

Impact: Logging

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

Cause: A circular dependency exists between partitions.

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

Type: WARNING

Impact: Logging

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

Cause: A request was made for an unknown partition.

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

Type: WARNING

Impact: Logging

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

Cause: A request was made for an unknown feature.

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

Cause: A circular dependency exists between features.

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

Type: WARNING

Impact: Logging

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

Cause: A circular dependency exists between features.

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

Cause: CalendarDropTarget was not attached to UIXCalendar.

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

Type: WARNING

Impact: Logging

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

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

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

Type: ERROR

Impact: Logging

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

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

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

Type: ERROR

Impact: Logging

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

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

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

Type: NOTIFICATION

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: SEVERE

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: SEVERE

Impact: Logging

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

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

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

Type: SEVERE

Impact: Logging

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

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

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

Type: SEVERE

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

Cause: The provided width is too large.

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

Cause: one of the parameter undefined for varyElement.

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

ADF_FACES-30167: No rule defined for caching.

Cause: No rule defined for caching.

Action: Define rule for caching.
Level: 1

Type: WARNING

Impact: Logging

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

Cause: No keys defined for Search-Key.

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

Type: WARNING

Impact: Logging

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

Cause: No vary-element defined for VaryBy element.

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

Type: WARNING

Impact: Logging

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

Cause: Suppressing Cache header.

Action: Do not override cache header.
Level: 1

Type: NOTIFICATION

Impact: Logging

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

Cause: WEB CACHE is installed ahead of Application Server.

Action: None.
Level: 1

Type: NOTIFICATION

Impact: Logging

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

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

Action: Contact Oracle Support Services.
Level: 1

Type: SEVERE

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

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

Action: None.
Level: 1

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

ADF_FACES-60001: ActiveDataModel is null.

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60002: attempt to register component for STATIC ActiveDataPolicy

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

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

Cause: Component was not registered properly.

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

Type: ERROR

Impact: Logging

ADF_FACES-60004: ActiveDataModel is not registered.

Cause: The activeDataModel was not registered.

Action: Register the activeDataModel.
Level: 2

Type: ERROR

Impact: Logging

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

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

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

Type: ERROR

Impact: Logging

ADF_FACES-60006: Request has not begun.

Cause: An IllegalStateException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

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

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60008: Attribute name required.

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60009: dropHandler required

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60010: allowed actions required

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60011: Allowed actions must be specified.

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

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

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60013: End of pattern not found.

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

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

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60015: Must have a drop component.

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60016: Must have parameters.

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

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

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60018: clientActions out of range

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60019: illegal character

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

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

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60021: No DnDActions specified.

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

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

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

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

Cause: An invalid client listener was encountered.

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

Type: ERROR

Impact: Logging

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

Cause: Only UIXComponents support client attributes.

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

Type: ERROR

Impact: Logging

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

Cause: An IllegalStateException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60026: Path contains a null rowKey.

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60027: unexpected navigationPane hint: {0}

Cause: An invalid navigationPane hint was encountered.

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

Type: ERROR

Impact: Logging

ADF_FACES-60028: targetComponent must be specified.

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

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

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60030: Fetch ClientEvent must not specify component.

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

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

Cause: An IllegalStateException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60032: Could not find ExtendedRenderKitService.

Cause: Render kit does not support the ExtendedRenderKitService.

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

Type: ERROR

Impact: Logging

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

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

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

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

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

Cause: A component was found with an invalid index.

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

Type: ERROR

Impact: Logging

ADF_FACES-60036: bad PhaseId: {0}

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60037: ClientId must be specified.

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60038: Component ID parameter is null.

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60039: AsyncFetch model parameter is null.

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60040: AsyncFetcher is null.

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

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

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

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

Cause: These elements were recursively nested.

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

Type: ERROR

Impact: Logging

ADF_FACES-60043: {0} is null.

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

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

Cause: Parent tag was not a FacesTag.

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

Type: ERROR

Impact: Logging

ADF_FACES-60045: Parent UIComponent instance is null.

Cause: Parent FacesTag had no UIComponent.

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

Type: ERROR

Impact: Logging

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

Cause: No render kit with this ID was found.

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

Type: ERROR

Impact: Logging

ADF_FACES-60047: Iterator cannot be null.

Cause: Iterator was found to be null.

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

Type: ERROR

Impact: Logging

ADF_FACES-60048: JavaScript does not support null keys.

Cause: A null key was found in the JavaScript.

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

Type: ERROR

Impact: Logging

ADF_FACES-60049: rowKeys cannot be null.

Cause: A null row key was found.

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

Type: ERROR

Impact: Logging

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

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

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

Type: ERROR

Impact: Logging

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

Cause: A column was found with an invalid width.

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

Type: ERROR

Impact: Logging

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

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

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

Type: ERROR

Impact: Logging

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

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

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

Type: ERROR

Impact: Logging

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

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

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

Type: ERROR

Impact: Logging

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

Cause: A converter was encountered with a missing method.

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

Type: ERROR

Impact: Logging

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

Cause: A converter was encountered with an invalid method.

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

Type: ERROR

Impact: Logging

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

Cause: A converter was encountered with an invalid method.

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

Type: ERROR

Impact: Logging

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

Cause: An IllegalStateException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60059: A null QueryModel object was found.

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

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

Type: WARNING

Impact: Logging

ADF_FACES-60060: A null ListOfValuesModel object was encountered.

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

ADF_FACES-60064: unsupported element: {0}

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

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

Type: WARNING

Impact: Logging

ADF_FACES-60065: unsupported namespace: {0}

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

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

Type: WARNING

Impact: Logging

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

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

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

Type: ERROR

Impact: Logging

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

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

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

Type: ERROR

Impact: Logging

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

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

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

Type: ERROR

Impact: Logging

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

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

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

Type: ERROR

Impact: Logging

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

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

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

Type: ERROR

Impact: Logging

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

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

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

Type: ERROR

Impact: Logging

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

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

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

Type: ERROR

Impact: Logging

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

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

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

Type: ERROR

Impact: Logging

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

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

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

Type: ERROR

Impact: Logging

ADF_FACES-60075: Drop handler cannot return null.

Cause: Drop handler cannot return null.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60076: Active Data Service is already initialized

Cause: AdsInitializerListener is registered in web.xml.

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

Type: WARNING

Impact: Logging

ADF_FACES-60077: The CalendarModel is null.

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

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

Type: SEVERE

Impact: Logging

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

Cause: Component was not registered properly.

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

Type: ERROR

Impact: Logging

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

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

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

Type: ERROR

Impact: Logging

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

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

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

Type: ERROR

Impact: Logging

ADF_FACES-60081: OutputStream already retrieved.

Cause: OutputStream already retrieved.

Action: OutputStream should be null.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-60082: Writer already retrieved.

Cause: Writer already retrieved.

Action: Writer should be null.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-60083: Response has already been committed.

Cause: Response has already been committed.

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

Type: ERROR

Impact: Logging

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

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

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

Cause: Validator tag requires an EditableValueHolder parent

Action: Add validator to an EditableValueHolder parent
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

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

Cause: A valid validatorId or binding has to be specified

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

Type: INCIDENT_ERROR

Impact: Logging

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

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

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

Type: ERROR

Impact: Logging

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

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

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

Type: WARNING

Impact: Logging

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

Cause: An exception was thrown durring a PPR request.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Logging

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

Cause: An exception was thrown durring a PPR request.

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

Type: ERROR

Impact: Logging

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

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

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Logging

2 ADF-MNC-10000 to ADF-MNC-50073

ADF-MNC-10000: Cannot find schema resource at {0}.

Cause: Schema file is missing.

Action: Place Schema file in the required location.
Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10001: Problem registering schema {0}, exception = {1}.

Cause: Schema file is invalid.

Action: Fix Schema file.
Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10002: Cannot instantiate rendering class {0} for platform {1}, exception = {2}.

Cause: Exception occurred during creation of rendering kit.

Action: Check ADF Mobile Client configuration file.
Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10003: {0} attribute is missing for one of the platforms in {1}.

Cause: Required attribute missing in configuration file.

Action: Check ADF Mobile Client configuration file.
Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10004: Duplicate platform with id = {0}, display value = {1} found in {2}.

Cause: Duplicate Platform Id specified in configuration file.

Action: Check ADF Mobile Client configuration file.
Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10005: {0} element is missing in {1}.

Cause: Required element missing in configuration file.

Action: Check ADF Mobile Client configuration file.
Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10006: Missing or invalid width/height attribute found for one of the form factors in {0}, exception = {1}.

Cause: Width/Height attribute is missing or invalid in the configuration file.

Action: Check ADF Mobile Client configuration file.
Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10007: Form factor element has negative width/height attribute defined in {0}, width = {1}, height = {2}.

Cause: Width/Height attribute has negative value in configuration file.

Action: Check ADF Mobile Client configuration file.
Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10008: Missing or invalid idref attribute found for {0} in {1}, idref = {2}.

Cause: idref missing or invalid in configuration file.

Action: Check ADF Mobile Client configuration file.
Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10009: Rendering kit factory class is not specified for id = {0} in {1}.

Cause: Missing rendering kit factory class in configuration file.

Action: Check ADF Mobile Client configuration file.
Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10010: Platform {0} does not have a rendering kit mapping defined in {1}.

Cause: Rendering kit mapping missing in configuration file.

Action: Check ADF Mobile Client configuration file.
Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10011: Problem opening configuration file {0}, exception = {1}.

Cause: Exception opening configuration file.

Action: Check ADF Mobile Client configuration file.
Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10012: Image repository is not specified for {0}.

Cause: Missing image repository in configuration file.

Action: Check ADF Mobile Client configuration file.
Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10013: Invalid configuration file for control {0}. The control will be loaded using default configuration.

Cause: Exception loading control configuration file.

Action: Check control configuration file in image repository.
Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10014: Invalid {0} attribute found for control id = {1}.

Cause: Invalid attribute in mcx file.

Action: Check mcx file.
Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10015: Unable to resolve EL = {0}.

Cause: Exception occurred while resolving EL expression.

Action: Check EL expression in mcx file.
Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10016: Missing or invalid group/index/weight attribute found for one of the default menu items in {0}, exception = {1}.

Cause: Group/Index/Weight attribute is missing or invalid in the configuration file.

Action: Check ADF Mobile Client configuration file.
Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10017: Invalid group/index attribute found for one of the default menu items in {0}, group = {1}, index={2}.

Cause: Group/Index attribute is not in the valid range of 0 to 65535.

Action: Check ADF Mobile Client configuration file.
Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10018: Invalid weight attribute found for one of the default menu items in {0}, weight = {1}.

Cause: Weight attribute has negative value in configuration file.

Action: Check ADF Mobile Client configuration file.
Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10019: An error occurred when attempting to read or write a record in table REPLAY_TYPE with TYPE_NAME value "{0}"

Cause: A database error occurred.

Action: Ensure that the required database is accessible and is configured properly for Transaction Replay Service. If necessary, run the TRS configuration wizard to reconfigure TRS for the mobile application.
Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10020: Failed to find record in table REPLAY_TYPE with TYPE_NAME value "{0}" when it is expected to exist. Run the TRS configuration wizard to reconfigure TRS for your mobile application.

Cause: The specified database record does not exist in table REPLAY_TYPE when it is expected to exist.

Action: Run the TRS configuration wizard to reconfigure TRS for your mobile application.
Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10021: Failed to update a record in database table REPLAY_TYPE. The database record has Type Name "{0}"

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10022: Type Name "{0}" conflicts with an existing record in database table REPLAY_TYPE. Each type name must be unique. Specify a different type name.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10023: A database access error occurred.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10024: The chosen database connection "{0}" is not valid. Run the Transaction Replay Service configuration wizard to choose a valid database connection that identifies where the ADFmc Transaction Replay Schema is deployed.

Cause: Cannot find or validate the selected database connection indicated in the message.

Action: Run the Transaction Replay Service configuration wizard for the mobile application to choose a valid database connection.
Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10025: The chosen database connection is not valid. Connection Name: "{0}", Connection Store Name: "{1}"

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10026: The chosen database connection is corrupt. Connection Name: "{0}", Connection Store Name: "{1}". Run the TRS Configuration Wizard.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10027: Cannot update file adf-config.xml to configure Transaction Replay Service for mobile application.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-10027: TRS configuration has been corrupted. To fix it, run the Transaction Replay Service configuration wizard to configure your mobile application to use Transaction Replay Service.

Cause: Corrupt internal metadata has been detected in the project .JPR file for the Transaction Replay Service configuration wizard.

Action: Run the Transaction Replay Service configuration wizard to configure Transaction Replay Service for your mobile application. This will fix the problem by overwriting the corrupt metadata.
Level: 1

Type: ERROR

Impact: Configuration

ADF-MNC-50000: Could not open {0}.

Cause: File is missing.

Action: Check that location and file both exist.
Level: 1

Type: ERROR

Impact: Files

ADF-MNC-50001: Corrupt COD: {0}.

Cause: The COD file is corrupt.

Action: Delete the COD file and attempt to regenerate it.
Level: 1

Type: ERROR

Impact: Files

ADF-MNC-50002: Error: The specified module was rejected by the device and cannot be loaded.

Cause: The file is corrupt.

Action: Delete the file and attempt to regenerate it.
Level: 1

Type: ERROR

Impact: Files

ADF-MNC-50003: Unknown Error: Examine logging information for additional details

Cause: An unknown error occurred.

Action: Examine logging information for additional details.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50004: BlackBerry JDE directory not specified. Set this in JDeveloper Preferences on the Mobile Client panel.

Cause: BlackBerry JDE directory not specified.

Action: Set the BlackBerry JDE directory in JDeveloper Preferences on the Mobile Client panel.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50005: Could not create destination directory {0}

Cause: Location may have disk problem.

Action: Examine disk for problems or permission issues.
Level: 1

Type: ERROR

Impact: Files

ADF-MNC-50006: Could not create directory {0}

Cause: Location may have disk problem.

Action: Examine disk for problems or permission issues.
Level: 1

Type: ERROR

Impact: Files

ADF-MNC-50007: Illegal install directory (must be absolute): {0}

Cause: Illegal install directory specified. This cannot be relative.

Action: Change to legal installation directory.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50008: Illegal source path (must be absolute): {0}

Cause: Illegal source path specified. This cannot be relative.

Action: Change to legal source path.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50009: File not found: {0}

Cause: File being added to CAB cannot be found.

Action: Check packaging directory for file.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50010: Invalid argument (CPU): {0}

Cause: Specified CPU is not supported.

Action: Select a supported CPU value.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50011: Mobile server connection not specified.

Cause: No mobile server connection has been specified.

Action: Select a mobile server connection.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50012: Cannot find connection {0} in {1}.

Cause: Specified connection cannot be found.

Action: Select a different connection.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50013: Mobile Client application failed to deploy to BlackBerry device.

Cause: Device or device connection may not be working.

Action: Examine device and device connection. Consider restarting device.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50014: General failure deploying package to device.

Cause: Device or device connection may not be working.

Action: Examine device and device connection. Consider restarting device.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50015: Connection timeout attempting to deploy package to device.

Cause: Device or device connection may not be working.

Action: Examine device and device connection. Consider restarting device.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50016: Error attempting to deploy package to device: {0} not found.

Cause: Application CAB not found after packaging.

Action: Check packaging directory for file.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50017: Error attempting to deploy package to device: {0} found on device, but overwrite flag not set.

Cause: Application CAB already exists on device.

Action: Delete CAB from device.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50018: Error attempting to deploy package to device: Could not write {0} to device.

Cause: Device storage might be full.

Action: Check device storage for available space and permissions.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50019: Error attempting to deploy package to device: Could not execute {0} on device.

Cause: User might not have permissions.

Action: Check user permissions on device.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50020: Error attempting to deploy package to device: Could not create directory {0} on device.

Cause: User might not have permissions.

Action: Check user permissions on device.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50021: Error attempting to deploy package to device: Unknown error code ({0}).

Cause: An unknown error occurred.

Action: Examine logging information for additional details.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50022: Mobile Client Runtime failed to deploy to BlackBerry device.

Cause: There was a problem deploying the ADF Mobile Client Runtime library to the BlackBerry device.

Action: Examine logging information for additional details.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50023: Failed to deploy application debug files to BlackBerry simulator directory.

Cause: JDeveloper could not deploy application debug files to BlackBerry simulator directory.

Action: Make sure you have write privileges for BlackBerry simulator directory.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50024: Exception caught: {0}

Cause: Exception caught while updating root-task-flow in adf-config.xml.

Action: Check adf-config.xml for write permissions.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50025: File exists: {0}

Cause: File exists in destination location preventing copy operation.

Action: Delete file.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50026: BlackBerry JDE directory specified refers to a location that does not exist. Set this in JDeveloper Preferences on the Mobile Client panel.

Cause: BlackBerry JDE directory does not exist.

Action: Set the BlackBerry JDE directory in JDeveloper Preferences on the Mobile Client panel.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50027: Mobile Client application failed to deploy to BlackBerry simulator.

Cause: Device simulator or simulator connection may not be working.

Action: Examine device simulator and simulator connection. Consider restarting device simulator.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50028: BlackBerry simulator directory not specified. Set this in JDeveloper Preferences on the Mobile Client panel.

Cause: BlackBerry simulator directory not specified.

Action: Set the BlackBerry simulator directory in JDeveloper Preferences on the Mobile Client panel.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50029: BlackBerry simulator directory specified refers to a location that does not exist. Set this in JDeveloper Preferences on the Mobile Client panel.

Cause: BlackBerry simulator directory specified refers to a location that does not exist.

Action: Set the BlackBerry simulator directory in JDeveloper Preferences on the Mobile Client panel.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50030: Error attempting to deploy package to device: There is not enough free space on device.

Cause: There is not enough free space on device.

Action: Attempt to free up space on device by removing unnecessary applications or files.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50031: Mobile Client Runtime failed to deploy to BlackBerry simulator.

Cause: There was a problem deploying the ADF Mobile Client Runtime library to the BlackBerry simulator.

Action: Examine logging information for additional details.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50032: Mobile Client Runtime failed to deploy to BlackBerry device as the device is not connected.

Cause: BlackBerry device was not detected

Action: Connect the BlackBerry device and try the operation again.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50033: Failed to delete all old files in the Deployment Folder at {0}

Cause: Some or all old files were not deleted from the deployment folder

Action: Verify user file privileges and try the operation again.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50034: Failed to create Deployment folder: {0}

Cause: Unable to create deployment folder

Action: Verify user privileges and try the operation again.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50035: The Client Database Name must be alpha-numeric and 1 to 28 characters long.

Cause: The client database name contains invalid characters or is not the correct length.

Action: Rename the client database to contain alpha-numerical characters only and ensure its length is valid.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50036: The path of the standalone database must be between 1 and 255 characters long.

Cause: The path to the location of the standalone database is not specified or has an invalid length.

Action: Specify a valid path to the location of the database and ensure its length is valid.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50037: The path of the standalone database script must between 1 and 255 characters long.

Cause: The path to the location of the standalone database initialization script has an invalid length.

Action: Specify a valid path to the location of the script contained in the application JAR file and ensure the path has a valid length.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50038: Failed to obtain the workspace.

Cause: Context information did not contain a valid value for the workspace property.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50039: Failed to locate a project containing adf-config.xml.

Cause: The workspace either does not have a project containing the 'ADF Mobile Client UI' technology or has an invalid or missing adf-config.xml configuration file.

Action: Ensure the workspace has a 'Mobile Client View Controller Project' containing the 'ADF Mobile Client UI' technology. Also, verify that the project has a valid adf-config.xml configuration file.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50040: Failed to get the client database. Exception message: {0}

Cause: An exception occurred when attempting to obtain the client database configuration value.

Action: Check the log file for more details.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50041: Failed to save the client database. Exception message: {0}

Cause: Failed to update adf-config.xml or failed to determine if a publication already exists for the application.

Action: Check adf-config.xml for write permissions. Verify the data publication configuration is correct and retry.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50042: Deployment failed as Preverify returned an error code.

Cause: Preverify utility failed to preverify the application jar file.

Action: Check the log file for more details.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50043: Deployment failed as RAPC returned an error code.

Cause: RAPC utility failed.

Action: Check the log file for more details.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50044: Application Name cannot be empty

Cause: Application name field in BlackBerry Deployment Options panel was empty.

Action: Valid application name is required to deploy the application on BlackBerry device.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50045: Application Name cannot contain any of the following characters: / ? : \ * " < > | -

Cause: BlackBerry application name contained one of the un-supported characters.

Action: Remove un-supported characters from the BlackBerry application name.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50046: Application Name cannot begin with '.'

Cause: BlackBerry application name contained period in the beginning of the name.

Action: Remove the period from the beginning of the BlackBerry application name.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50047: Application Name cannot be empty

Cause: Application name field in Windows Mobile Deployment Options panel was empty.

Action: Valid application name is required to deploy the application on Windows Mobile device.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50048: Application Name cannot contain any of the following characters: / ? : & \ * " < > | # %

Cause: Windows Mobile application name contained one of the un-supported characters.

Action: Remove un-supported characters from the Windows Mobile application name.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50049: Application Name cannot begin or end with '.'

Cause: Windows Mobile application name contained period in the beginning or ending of the name.

Action: Remove the period from the beginning and ending of the Windows Mobile application name.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50050: Application Name cannot be Windows system reserved names, including CON, AUX, PRN, COM1 or LPT2

Cause: Windows Mobile application name used one of the Windows system reserved names.

Action: Modify Windows Mobile application name not to use any Windows system reserved names as specified.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50051: Unable to locate {0}. Make sure to enter valid path.

Cause: Invalid Icon file path was entered.

Action: Verify the path entered.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50052: Selected icon file is not within the project directory. Please select the icon from within the following project directory: {0}

Cause: The icon file was selected from outside the project directory.

Action: Select the icon file from within the project directory. Copy the icon in the project if it is not there.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50053: File type is not a supported icon type. Please provide supported icon type ({0}).

Cause: Invalid Icon file type selected

Action: Select one of the supported file types only.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50054: Invalid parameter detected in method {0}. Parameter {1} is null or empty.

Cause: Internal programming error.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50055: Invalid parameter detected in method {0}. The value {1} is not allowed for a ADF setting of {2}.

Cause: Internal programming error.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50056: Failed to obtain a database provider for connection named {0}.

Cause: Unable to obtain connection information for the Oracle Mobile Server Repository.

Action: Verify the database connection definition for the Oracle Mobile Server Repository is correct and ensure the database is available.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50057: Connection with ActiveSync could not be established. Ensure that PC-to-device/emulator connectivity is working correctly. Restarting JDeveloper may restore communications. See ADF Mobile Client documentation on Troubleshooting if the problem persists.

Cause: JDeveloper could not connect to ActiveSync and initialize communication channel.

Action: Restart Windows Mobile Emulator, Windows Mobile Emulator Manager and ActiveSync. Ensure that PC-to-device/emulator connectivity is working correctly. Restarting JDeveloper may restore communications. See ADF Mobile Client documentation on Troubleshooting if the problem persists.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50058: Method {0} detected a invalid null parameter {1}.

Cause: Internal programming error.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50059: MDK is not installed or the path is not set. Publication is not created.

Cause: The location to your Oracle Database Lite installation is not configured.

Action: Specify the location to your Oracle Database Lite installation available as an ADF Mobile Client preference option.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50060: The TRS database is either not configured correctly or does not have the TRS schema installed. TRS Publication is not created.

Cause: The database may not be avaiable or does not have the TRS schema installed.

Action: Verify the database is available and has the TRS schema installed.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50061: Detected an invalid profile type.

Cause: Internal programming error.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50062: There are no entity objects defined in the application. The Synchronization Publication deployment profile cannot be edited unless there are entity objects to be synchronized in the application.

Cause: The application does not have entity objects imported from an ADF library.

Action: Import entity objects from an ADF library using the 'Business Components from ADF Library' wizard.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50063: Could not find dummy class file: {0}

Cause: ADFMC_Dummy.class file is required but was not found in the source location

Action: Check with the administrator.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50064: You have specified an application schema outside of the database where the mobile server repository schema is installed. You must run the "apprepwizard" to install the remote application repository and then specify the password in the "Remote Application Repository Credential" section.

Cause: The application schema and Oracle Mobile Server Repository schema are in different databases.

Action: Run the "apprepwizard" and specify the credential needed to access the application schema.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50065: Failed to determine if the connection {0} has the TRS Schema installed. Exception: {1}.

Cause: A database error occurred.

Action: Verify the database containing the TRS Schema is available and examine logging information for additional details.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50066: Connection {0} does not have the TRS Schema installed. Please select a different connection or install the TRS Schema and try again.

Cause: The schema does not have the TRS tables installed.

Action: Install the TRS schema.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50067: The connection, {0}, is not valid and has been reset.

Cause: The TRS connection defintiion was not valid.

Action: Verify the database containing the TRS schema is available.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50068: Failed to get the TRS configuration from the profile.

Cause: The project did not contain TRS configuration options.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50069: Failed to establish a connection to {0}. Exception: {1}.

Cause: A connection exception occurred when connecting to the database.

Action: Verify the connection configuration is correct and the database is online and available.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50070: Failed to initialize the TRS Publication panel. Exception: {0}.

Cause: The panel failed to initialize.

Action: Check the log file for more details.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50071: Mobile server repository connection information must be entered first.

Cause: There is no connection configuration for the Oracle Mobile Server Repository schema or the connection is not valid.

Action: Verify there is a valid connection definition for the Oracle Mobile Server Repository schema.
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50072: Windows Mobile deployment tool file not found: {0}

Cause: The PPCDeployer DLL file is missing. Windows Mobile deployment requires this file.

Action: Check the location of the PPCDeployer.dll. Reinstall the ADF Mobile Client extension to restore this file
Level: 1

Type: ERROR

Impact: Deployment

ADF-MNC-50073: Windows Mobile deployment tool file is corrupt, or not supported on this operating system: {0}

Cause: The PPCDeployer DLL file is present, but it cannot be loaded correctly. It is either corrupt, or being invoked on an unsupported operating system.

Action: Reinstall the ADF Mobile Client extension to restore this file. Perform this operation in a Windows operating system environment.
Level: 1

Type: ERROR

Impact: Deployment

3 ADF_TRINID-00001 to ADF_TRINID-30336

ADF_TRINID-00001: Could not find FacesBean class {0}

Cause: FacesBean class name could not be found.

Action: Log a bug against the application. Check that the jsf jars are all installed correctly.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-00002: Could not create instance of FacesBean {0}

Cause: IllegalArgumentException

Action: Log a bug against the application. Check that the jsf jars are all installed correctly.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-00003: No faces-bean.properties files located

Cause: Could not find the faces-bean.properties file in any jar

Action: Log a bug against the application. Check that the jsf jars are all installed correctly.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF_TRINID-00004: Could not load {0}

Cause: Cannot find the url

Action: Log a bug against the application. Check that the jsf jars are all installed correctly. Check that the url is written correctly.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-00005: Error on trying to create new component instance for {0}

Cause: Error in ChangeManager

Action: Log a bug against the application. Check that the Trinidad and jsf jars are all installed correctly.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00006: Conversion class: {0} not of type {1}

Cause: Error in ChangeManager

Action: Change the type so that it can be converted or log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00007: Unable to instantiate converterClass: {0}

Cause: Error in ChangeManager

Action: Make sure the converter class can be instantiated or log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00008: Saved child count does not match current count (was {0}, now {1})

Cause: Error in TreeState implementation

Action: Fix the TreeState implementation or log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00009: State for some facets of {0} is missing, and will not be restored.

Cause: Error in TreeState implementation

Action: Fix the TreeState facet state implementation or log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00010: Saved facet state includes state for facet "{0}" which is not present in restored tree; discarding this state.

Cause: Error in TreeState implementation

Action: Fix the TreeState facet state implementation or log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00011: Saved state includes state for a transient component: {0}

Cause: Error in TreeState implementation

Action: Fix the TreeState state implementation or log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00012: Could not find rowKey for clientRowKey:{0}

Cause: Error in UIXCollection implementation when setting/getting clientRowKey

Action: Fix UIXCollection implementation or log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-00013: There was no initial stamp state for currencyKey:{0} and currencyKeyForInitialStampState:{1} and stampId:{2}

Cause: Error in UIXCollection

Action: Fix UIXCollection implementation or log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-00014: Could not find renderer for {0} rendererType = {1}

Cause: Error in renderer registration on render kit

Action: Log a bug against the application and make sure the Trinidad jars are installed and check the faces-config.xml files.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00015: Could not load type properties

Cause: Error getting faces-bean-type.properties from any jar

Action: Log a bug against the application and make sure the Trinidad and jsf jars are installed.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-00016: Could not get resource key {0} from skin {1}

Cause: ResourceBundle key does not exist in any resource bundle in framework or skin.

Action: Log a bug against the application or make sure the resource key exists in skin by checking the skin resource files (see trinidad-skins.xml).
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-00017: Trying to attach RenderingContext to a thread that already had one.

Cause: Thread already had a RenderingContext attached to it.

Action: Log a bug against the application. Call release()
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00018: Cannot find RequestContext; two-digit-year-start will be defaulted

Cause: RequestContext was not set up yet.

Action: Log a bug against the application. Make sure all jars are installed and filters are specified correctly in web.xml
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00019: Cannot find RequestContext; TimeZone will default.

Cause: RequestContext was not set up yet.

Action: Log a bug against the application. Make sure all jars are installed and filters are specified correctly in web.xml
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00020: Failed to get hold of DecimalFormat for type: {0} decimal separator, number grouping separator, currency code will be defaulted based on locale {1}

Cause: DecimalFormat not set up

Action: Log a bug against the application. Make sure all jars are installed and filters are specified correctly in web.xml
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00021: RequestContext is null: decimal separator, number grouping separator, currency code will be defaulted based on locale

Cause: RequestContext was not set up yet.

Action: Log a bug against the application. Make sure all jars are installed and filters are specified correctly in web.xml
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00022: RequestContext is null, unable to get currency code

Cause: RequestContext was not set up yet.

Action: Log a bug against the application. Make sure all jars are installed and filters are specified correctly in web.xml
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00023: Number format was not instance of DecimalFormat: ignoring currency information while formatting.

Cause: Number format was not set up correctly.

Action: Set up the Number format correctly or log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00024: CollectionModel was set to null

Cause: setCollectionModel was passed a null parameter

Action: Check the code that calls setCollectionModel or log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00025: Invalid rowkey:{0} type:{1}

Cause: ClassCastException rowkey should be an Integer

Action: Fix the rowkey to be an Integer or log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00026: The viewId property in ViewIdPropertyMenuModel is null. The viewId property is needed to find the focus rowKey.

Cause: viewIdProperty that is used to retrieve the viewId from a node in the tree is null.

Action: Set the viewIdProperty to be non-null or log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00027: EL Expression {0} is invalid or returned a bad value

Cause: ELExpression evaluation caused an exception

Action: Fix the ELExpression to be valid or log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00028: Exception opening URI {0}

Cause: Exception in openStream

Action: Check the URI. Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-00029: Exception creating menu model {0}

Cause: Exception while creating menu model

Action: Fix the menu model code or log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-00030: Resource "{0}" at path "{1}" not found

Cause: Error calling getResource

Action: Make sure the resource can be found or log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00031: Unable to retrieve image data for icon of type {0}. Try using ContextImageIcon.

Cause: Icon openStream method called, and it is not supported.

Action: Try using a ContextImageIcon in your code instead or log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00032: Error parsing:{0}

Cause: Error parsing a service from a file in /META-INF/services

Action: Check the services to make sure the urls are valid or log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00033: error loading resource:{0}

Cause: IOException while loading services

Action: Check your server or log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-00034: Resource name "{0}" begins with a slash, which is not portable.

Cause: resource name begins with a slash and it shouldn't.

Action: Fix the resource name to not begin with a slash or log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00035: unable to load bundle {0}

Cause: MissingResourceException; bundle could not be loaded.

Action: Fix the resource bundle so that it can be loaded or log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-00036: Unable to load faces bundle {0}

Cause: MissingResourceException

Action: Make sure the jsf jars are installed correctly. Make sure you can find the faces bundle. Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-00037: Unable to find ResourceLoader for ResourceServlet at servlet path:{0} Cause: Could not find resource:{1}

Cause: Resource missing

Action: Make sure the resource can be found. Make sure the jars are installed correctly. Log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00038: Trinidad ResourceServlet is running in debug mode. Do not use in a production environment. See the {0} parameter in /WEB-INF/web.xml

Cause: Application is running in debug mode.

Action: Change the parameter in web.xml so that it is not running in debug mode.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF_TRINID-00039: Could not find context class loader.

Cause: Thread.getContextClassLoader returned null.

Action: Fix the code so the ContextClassLoader can be loaded. Check the web server.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-00040: Could not convert:{0} into int[]

Cause: value is not a list of integers

Action: Change the value so that it can be converted to an array of integers. Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-00041: Could not parse value {0} into a Date using pattern "yyyy-MM-dd"; ignoring.

Cause: date property's value is not in the correct format

Action: Nothing if the pattern it uses is ok. Otherwise log a bug against the application.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF_TRINID-00042: no parent <tr:componentRef> found!

Cause: No parent componentRef component exists

Action: Log a bug against the application. Add a componentRef component on the page.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-00043: Event {0} was delivered to a showDetail already in that disclosure state.

Cause: Renderer delivered an unnecessary event or it set disclosed on its own instead of waiting for the disclosure event.

Action: Check the showDetail renderer code or log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00044: Name "{0}" had already been registered.

Cause: FacesBean addKey with name already added.

Action: Make sure you do not have duplicate names. Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00045: Index "{0}" had already been registered.

Cause: FacesBean addkey with index already added

Action: Make sure you do not have duplicate indexes. Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00046: Type is already locked

Cause: The FacesBean type object is locked, preventing further changes. . IllegalStateException, name already in keymap

Action: Fix code that has locked the FacesBean.Type. Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00047: Property "{0}" cannot be bound.

Cause: IllegalArgumentException, trying to set valuebinding on a key that does not support binding

Action: Do not valuebind the property or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00048: Key {0} cannot be used for lists

Cause: IllegalArgumentException, PropertyKey is not a list and it should be to call this method.

Action: Fix the code so that the PropertyKey can be used for lists or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00049: Key {0} is a list key

Cause: IllegalArgumentException, propertykey passed is a list and it shouldn't be.

Action: Fix code so that the propertyKey is not a list key or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00050: Default value {0} is not assignable to type {1}

Cause: IllegalStateException; PropertyKey constructor error

Action: Fix the PropertyKey constructor to pass in a non-null defaultValue parameter or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00051: Capability mask {0} not understood

Cause: IllegalStateException; PropertyKey constructor error

Action: Check the PropertyKey API and use a valid Capability mask or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00052: Invalid index

Cause: IllegalStateException; PropertyKey constructor error

Action: Check the PropertyKey API and provide a valid index to the PropertyKey constructor or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00053: Attempt to add a duplicate ID {0}

Cause: ChangeManager, already a child with ID

Action: Remove duplicate ids or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00054: No node specified

Cause: ChangeManager, componentNode passed to the method is null.

Action: Specify a node or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00055: component required

Cause: ChangeManager, constructor error

Action: Check the ChangeManager API and code or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00056: DocumentFragment required

Cause: ChangeManager, IllegalArgumentException

Action: Check the ChangeManager API and code or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00057: Cannot construct an AttributeChange with null attribute name.

Cause: ChangeManager, IllegalArgumentException, constructor error

Action: Check the ChangeManager API and code or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00058: Cannot add a Change with either of facesContext, uiComponent or Change being null.

Cause: ChangeManager, IllegalArgumentException, constructor error

Action: Check the ChangeManager API and code or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00059: Cannot construct an ChangeComponentProxy with null uiComponent.

Cause: ChangeManager, IllegalArgumentException, constructor error

Action: Use a non null UIComponent parameter in the ChangeComponentProxy. Check the API. Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00060: target class name must be provided

Cause: ChangeManager, IllegalArgumentException

Action: Fix call to ChangeManager.registerDocumentFactory to provide a targetClassName or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00061: converter class name must be provided

Cause: ChangeManager, IllegalArgumentException

Action: Fix call to ChangeManager.registerDocumentFactory to provide a converterClassName or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00062: Parent cannot be null

Cause: ChangeManager, null parameter

Action: Set the parent to be non-null or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00063: Cannot construct a RemoveChildChange with null childId.

Cause: ChangeManager, IllegalArgumentException, constructor error

Action: Fix the constructor to provide a non-null childId or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00064: Cannot construct a RemoveFacetChange with null facetName.

Cause: ChangeManager, IllegalArgumentException, constructor error

Action: Fix the constructor to use a non-null facetName or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00065: Cannot construct a ReorderChange with null childIds.

Cause: ChangeManager, IllegalArgumentException, constructor error

Action: Fix the constructor to use a non-null childId or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00066: Cannot construct an AddFacetChange with either of facetName or facetComponent being null.

Cause: ChangeManager, IllegalArgumentException, constructor error

Action: Fix the constructor to use a non-null facetName or facetComponent or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00067: Facet name must be specified

Cause: ChangeManager, IllegalArgumentException, constructor error

Action: Fix the constructor to use a non-null facetName or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00068: index:{0} size:{1}

Cause: ChildArrayList was not built properly

Action: Fix the code that builds the ChildArrayList or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00069: Bad PhaseId:{0}

Cause: The phaseId passed to the method is invalid

Action: Make sure the phaseId is valid when calling this method or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00070: Illegal id: {0}

Cause: The component has a bad id. First character might be a separator character or empty

Action: Fix the illegal component id in your page or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00071: wrappedEvent

Cause: Illegal use of the WrapperEvent constructor. The wrappedEvent parameter was null.

Action: Fix the code that creates a WrappedEvent object or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00072: RenderingContext was already released or had never been attached.

Cause: An attempt was made to release an unattached RenderingContext

Action: Fix the code that tried to release the RenderingContext or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00073: Trying to release a different RenderingContext than the current context.

Cause: An attempt was made to release a RenderingContext that is not the current RenderingContext.

Action: Fix the code that tried to release the RenderingContext or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00074: This is not an error. This trace is for debugging.

Cause: This is not an error. This trace is for debugging the RequestContext class.

Action: No action needed since this is a debugging log message only. You can set the LOG to greater than FINEST to turn off the message.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00075: Trying to release a different RequestContext than the current context.

Cause: An attempt was made to release a RequestContext that is not the current RequestContext.

Action: Make sure the release method was called by the same code that created the RequestContext or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00076: Factory already available for this class loader.

Cause: IllegalStateException, an attempt was made to set in a map a RequestContextFactory that already exists for this classloader

Action: Do not call setFactory(RequestContextFactory factory) with a RequestContextFactory that already exists for the class loader or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00077: Supplied FacesContext or UIComponent is null

Cause: NullPointerException, the FacesContext or UIComponent passed to the method was null.

Action: Fix the code that caused this NullPointerException or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00078: FacesContext or UIComponent is null

Cause: NullPointerException, the FacesContext or UIComponent passed to the method was null.

Action: Fix the code that caused this NullPointerException or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00079: Patterns should contain atleast one value and cannot be null

Cause: IllegalArgumentException in ColorConverter; pattern is null or empty

Action: Fix the pattern in the ColorConverter or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00080: Cannot format given Object as a Color

Cause: Object passed to method was not an instance of Color or Number

Action: Fix the Object that you pass into the method or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00081: Invalid attribute name {0}

Cause: IllegalArgumentException, attribute name not found in FacesBean.Type

Action: Check your value bindings to make sure the attribute name exists or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00082: value:"{0}" is not of type java.util.Date, it is {1}

Cause: ClassCastException, value is not a String or Date.

Action: Fix the value binding to point to a String or a Date or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00083: Invalid date style ''{0}''

Cause: IllegalStateException, the date style was not default, short, medium, long, full, or shortish.

Action: Fix the DateTimeConverter's dateStyle attribute or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00084: Invalid time style ''{0}''

Cause: IllegalStateException, the time style was not default, short, medium long or full.

Action: Fix the DateTimeConverter's timeStyle attribute or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00085: Invalid type ''{0}''

Cause: IllegalStateException, the type was not "date", "time", or "both"

Action: Fix the DateTimeConverter's type attribute or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00086: Illegal message id unexpected value {0}

Cause: IllegalArgumentException in DateTimeConverter.

Action: Fix the message pattern or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00087: Illegal value for attribute "type" unexpected value {0}

Cause: IllegalArgumentException

Action: Fix the DateTimeConverter's type attribute or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00088: FacesContext or Component is null

Cause: NullPointerException, the FacesContext or UIComponent passed to the method was null.

Action: Fix the code that caused the NullPointerException or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00089: Either "pattern" or "type" must be specified

Cause: IllegalArgumentException, pattern and type parameters were both null.

Action: Set the NumberConverter's type or pattern attribute or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00090: "value" is not of type java.lang.Number

Cause: IllegalArgumentException in NumberConverter

Action: Fix NumberConverter's value to be a Number or String or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00091: {0} is not a valid type

Cause: IllegalArgumentException in NumberConverter. type should be number, currency or percent

Action: Fix NumberConverter's type attribute or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00092: Illegal pattern character ''{0}''

Cause: IllegalArgumentEcxeption in RGBColorFormat when checking the rgb pattern character

Action: Fix the rgb pattern in RGBColorFormat or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00093: Logger required

Cause: TrinidadLogger constructor error

Action: Fix the code that creates the TrinidadLogger or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00094: Logger Name required

Cause: Attempt was made to create a TrinidadLogger without a name which is a required parameter to this method.

Action: Check the call to TrinidadLogger.createTrinidadLogger or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00095: Class required

Cause: Attempt was made to create a TrinidadLogger without a Class which is a required parameter to this method.

Action: Fix the call to TrinidadLogger.createTrinidadLogger or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00096: Package required

Cause: Attempt was made to create a TrinidadLogger without a package which is a required parameter to this method.

Action: Fix the call to TrinidadLogger.createTrinidadLogger or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00097: rowData is null

Cause: IllegalStateException in TreeModel or MenuModel. rowData is null.

Action: Fix rowData or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00098: Cannot exit the root container

Cause: IllegalStateException in TreeModel or MenuModel.

Action: Fix code in the TreeModel or MenuModel regarding the path size or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00099: Illegal value being set - value should be between -1 and maximum

Cause: The constructor was called with the wrong value

Action: Fix the code that creates a DefaultBoundedRangeModel or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00100: Could not convert:{0} into a MenuModel

Cause: IllegalArgumentException, the value could not be converted to a MenuModel.

Action: Fix the MenuModel's value so it can be converted to a MenuModel or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00101: rowKey

Cause: IllegalStateException, PathHelper's rowKey has not been set and is null.

Action: Set PathHelper's rowKey or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00102: No Path element to pop

Cause: IllegalStateException in PathHelper

Action: Fix the path or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00103: Could not clone

Cause: CloneNotSupported, an attempt was made to call clone() on an object that is not clonable.

Action: Make sure the object is clonable before calling the method or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00104: No element to remove

Cause: IllegalStateException, an attempt was made to remove a null element.

Action: Fix the rowKeySet code or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00105: todo

Cause: This is only a todo. No cause.

Action: This is only a todo. No action.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00106: property is null

Cause: SortCriterion constructor error, NullPointerException

Action: Fix the NullPointerException or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00107: No MenuContentHandler was registered.

Cause: IllegalStateException, no MenuContentHandler was registered on services.

Action: Fix the code to register a MenuContentHandler or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00108: No RenderingContext

Cause: IllegalStateException, RenderingContext is null and it shouldn't be.

Action: Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00109: Resource path regular expression "{0}" does not have leading slash

Cause: IllegalArgumentException, there was no leading slash and there should be.

Action: Fix the resource path by adding a leading slash or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00110: Factory already available for this class loader.

Cause: IllegalStateException, SkinFactory already available for the class loader.

Action: Fix call to SkinFactory.setFactory or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00111: byte[] cannot be null

Cause: NullPointerException, argument is null

Action: Fix the NullPointerException by setting byte[] to a non-null value or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00112: Actual Length:{0} offset:"{1} length:{2}

Cause: IndexOutOfBoundsException, byte[], offset, length arguments passed to the method are incorrect.

Action: Fix the IndexOutOfBoundsException or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00113: FastMessageFormat only supports numeric arguments

Cause: IllegalArgumentException, in FastMessageFormat while formatting.

Action: Fix the arguments passed into the method to be numeric or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00114: End of pattern not found

Cause: IllegalArgumentException, in FastMessageFormat while formatting.

Action: Fix the FastMessageFormat pattern or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00115: FastMessageFormat: empty argument - {} - found

Cause: IllegalArgumentException, in FastMessageFormat while formatting.

Action: Fix the call to the method to have a non-empty argument or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00116: bundle not found

Cause: No bundle was found.

Action: Fix the resource bundle (for example, the ApplicationFacesMessageBundle) so that it can be found by the code or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00117: resourceId is null

Cause: NullPointerException. A null value was passed to a method.

Action: Fix the NullPointerException by passing in a non-null resourceid or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00118: The default FacesMessage.FACES_MESSAGES cannot be found

Cause: NullPointerException. FacesMessage.FACES_MESSAGES from the jsf spec could not be found.

Action: Log a bug against the application. Check that the jsf jars are all installed correctly.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00119: FacesContext is null

Cause: NullPointerException, FacesContext is null when it is passed to a method and it should not be null.

Action: Log a bug against the application. Check that the jsf jars are all installed correctly.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00120: custom message should be of type ValueBinding or String

Cause: IllegalArgumentException, custom message in method was not of the correct type.

Action: Fix the customMessagePattern to be a ValueBinding or a String Object or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00121: Provider {0} did not return an object implementing {1}

Cause: This error is no longer in the code.

Action: Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00122: FacesContext.getRenderKit() returned null while trying to get the {0} service; please check your configuration.

Cause: IllegalStateException, while getting a service in the Service utility code.

Action: Log a bug against the application. Check your configuration and check that the jsf jars are all installed correctly.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00123: FacesContext or Component is null

Cause: NullPointerException, the FacesContext or UIComponent passed to the method was null.

Action: Log a bug against the application. Check your configuration and check that the jsf jars are all installed correctly.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00124: Encoding: {0} is unsupported by JVM

Cause: IllegalCharsetNameException while trying to encode in the ByteLength Validator using an encoding that is not supported by the JVM.

Action: Check the encoding and check the JVM. Otherwise log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00125: ''value'' is not of type java.util.Date

Cause: Value is not the type it should be.

Action: Change the value to be of type java.util.Date or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00126: Pattern null

Cause: The regular expression's pattern is null and it shouldn't be.

Action: Fix the regular expression to be a non-null value or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00127: Invalid attribute name {0}

Cause: This error is no longer in the code.

Action: Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00128: <f:view> was not present on this page; tag {0}encountered without an <f:view> being processed.

Cause: view tag was not present on the page.

Action: Log a bug against the application. Add a view tag on your jspx page.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30001: The User-Agent "{0}" is unknown; creating an agent with null agent attributes.

Cause: The user-agent of the user's agent is unknown.

Action: Use a known agent, like IE7 or Firefox.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30002: The agent type is unknown; creating an agent with null agent attributes.

Cause: The agent type of the user's agent is unknown.

Action: Use a known agent, like IE7 or Firefox.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30003: could not get capabilities from capabilities document

Cause: RuntimeException when trying to get user agent's capabilities map

Action: Use a known agent, like IE7 or Firefox. Log a bug against the Apache Trinidad framework.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30004: Could not locate Capabilities document

Cause: Could not find Capabilities document META-INF/agent/capabilities.xml

Action: Make sure the Apache Trinidad framework jars are installed. Log a bug against the Apache Trinidad framework.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30005: "Cannot resolve capabilities file"

Cause: Exception while attempting to load the Capabilities document META-INF/agent/capabilities.xml

Action: Make sure the Apache Trinidad framework jars are installed. Log a bug against the Apache Trinidad framework.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30006: Invalid dependency found in include by reference

Cause: Invalid dependency found while resolving the capabilities for a give capabilitiesNode

Action: Use a known agent, like IE7 or Firefox. Log a bug against the Apache Trinidad framework.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30007: Reference to id: {0} not found

Cause: An attempt to get capabilities of node using a node refid, and refid was not found.

Action: Log a bug against the Apache Trinidad framework. Make sure the capabilities document is valid xml.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30008: Failed to parse capabilities document

Cause: An IOException while parsing the XML-based capabilities document.

Action: Log a bug against the Apache Trinidad framework. Make sure the capabilities document is valid xml.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30009: Unable to parse agent string

Cause: ParseException while parsing the agent string.

Action: Use a known agent, like IE7 or Firefox.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30010: Element {0} has missing (or empty) attributes

Cause: While attempting to parse a document, the element should have attributes but doesn't.

Action: Make sure the document that is being parsed has the correct syntax and attributes. Log a bug against the Apache Trinidad framework or the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30011: Failed to parse capabilities data document

Cause: The capabilities data document was being parsed and failed.

Action: Log a bug against the Apache Trinidad framework. Make sure the capabilities document is valid xml.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30012: Unable to parse model string

Cause: Error occured while parsing the device nodes in the capabilities file

Action: Check the capabilities document. Make sure the capabilities document is valid xml. Log a bug against the Apache Trinidad framework.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30013: Capability data url {0} is invalid

Cause: MalformedURLException while creating the URL.

Action: Check the capabilities document and make sure url is correctly formed.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30014: Could not find saved view state for token {0}

Cause: Could not find the saved view state in the StateManager.

Action: Log a bug against the Apache Trinidad framework.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30015: No structure available and no root available

Cause: While attempting to restore the state in the StateManager, no view root was available.

Action: Log a bug against the Apache Trinidad framework or against the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30016: No structure available

Cause: While attempting to restore the state in the StateManager, no structure was available.

Action: Log a bug against the Apache Trinidad framework or against the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30017: Ignoring servlet init parameter:{0} unable to parse:{1}

Cause: Attempting to parse servlet init parameter gave error.

Action: Check servlet init parameters. Check your web server.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30018: Could not load ViewHandler {0}

Cause: Attempting to load viewhandler threw exception.

Action: Log a bug against the Apache Trinidad framework or against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30019: Apache Trinidad is running with time-stamp checking enabled. This should not be used in a production environment. See the {0} property in WEB-INF/web.xml

Cause: time-stamp checking is enabled in web.xml.

Action: Turn off time-stamp checking in a production environment.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF_TRINID-30020: Could not load {0}

Cause: Attempting to load an url and an exception occurred.

Action: Make sure the url can be found on the server. Log a bug against the Apache Trinidad framework or the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30021: Could not instantiate UploadedFileProcessor

Cause: Attempting to instantiate UploadedFileProcessor failed.

Action: Make sure the Trinidad jars are installed correctly. Log a bug against the Apache Trinidad framework.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30022: Trinidad is running in debug mode. Do not use in a production environment. See:{0}

Cause: debug mode is turned on.

Action: Set debug to false in web.xml.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF_TRINID-30023: Element {0} is not understood

Cause: Attempting to parse WEB-INF/trinidad-config.xml, an invalid element was found.

Action: Check the trinidad-config.xml file to make sure the element is valid.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30024: Element {0} does not support EL expressions.

Cause: Attempting to parse WEB-INF/trinidad-config.xml, and found an element that does not support EL binding EL bound.

Action: Check the trinidad-config.xml file and don't EL bind the element.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30025: "Element {0} only accepts integer values

Cause: Found problem in WEB-INF/trinidad-config.xml.

Action: Check the trinidad-config.xml file.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30026: Could not find context class loader.

Cause: Attempting to call Thread.currentThread().getContextClassLoader()

Action: Check the web server. Log a bug against the Apache Trinidad framework or the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30027: Configurator services already initialized.

Cause: While initializing the global configurator and the configurator services, discovered they are already initialized.

Action: Do not initial configurator services more than once.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30028: RequestContext had not been properly released on earlier request.

Cause: RequestContext was checked to see if it was released and it wasn't.

Action: No action needed, since the code will clean this up. Check the code to make sure it is properly releasing the RequestContext.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30029: Unable to set request character encoding to {0}, because request parameters have already been read.

Cause: Attempting to set the character encoding after parameters have been retrieved.

Action: Log a bug against the Apache Trinidad framework because the code is calling setCharacterEncoding at the wrong time.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30030: No 'DialogUsedRK' key available for returnFromDialog to do the right thing!

Cause: Return from a dialog caused this error.

Action: Log a bug against the Apache Trinidad framework.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30031: Could not queue return event: no launch source

Cause: Attempting to queue return event.

Action: Check your dialog code to make sure the launch source exists. Log a bug against the Apache Trinidad framework or the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30032: RenderKit {0} does not support DialogRenderKitService, and cannot be used to launch dialogs; using a single window instead.

Cause: Attempting to launch dialog.

Action: Use a renderkit that supports DialogRenderKitService or don't use DialogRenderKitService.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF_TRINID-30033: Apache Trinidad is using HTTPSession for change persistence

Cause: Notification to tell application developer that Trinidad is using HTTPSession

Action: No action needed.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF_TRINID-30034: Unable to create ChangeManager:{0}

Cause: Exception attempting to create the ChangeManager.

Action: Check your ChangeManager configuration. Log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30035: Could not find partial trigger {0} from {1}

Cause: Attempting to find partial trigger.

Action: Make sure the partialTriggers are set to an existing component's id. View the jspx page in JDeveloper and JDeveloper will flag the errors for you. Log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30036: Failed to set character encoding {0}

Cause: Attempting to set character encoding failed.

Action: Log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30037: Detecting request character encoding is disable.

Cause: Exception getting character encoding from ServletRequest.

Action: Enable ServletRequest's character encoding if needed.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30038: Failed to obtain ServletRequest#setCharacterEncoding() method: {0}

Cause: Exception getting character encoding from ServletRequest

Action: Enable ServletRequest's character encoding if needed.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30039: The component is null, but it is needed for the client id, so no script written

Cause: The UIComponent passed to the method is null.

Action: Make sure you pass an non-null UIComponent into the method. Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30040: Client id is null, no script rendered

Cause: The UIComponent passed to the method is null.

Action: Make sure you pass an non-null UIComponent into the method. Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30041: Tried to create converter for type {0}, but could not, likely because no converter is registered.

Cause: Attempting to create a converter failed.

Action: Log a bug against the application. Register a converter.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30042: Client id is null, no script rendered

Cause: Attempting to create a converter failed.

Action: Log a bug against the application. Register a converter.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30043: Instantiation of Property {0} failed.

Cause: Attempting to instantiated a Property caused an Exception.

Action: Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30044: Couldn't get unique name!

Cause: Attempting to get a unique name from the image cache failed.

Action: Log a bug against the Apache Trinidad framework. This exception should never happen.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30045: Elapsed time:{0} secs to encode gif

Cause: Encoding gifs.

Action: No action needed.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF_TRINID-30046: laf "{0}" not found.

Cause: Attempting to find the look and feel failed.

Action: Log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30047: Illegal character (space) in "name" attribute

Cause: Attempting to parse the name attribute.

Action: Log a bug against the application. Check the name attribute and remove space
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30048: "name" attribute incorrectly set to "name"

Cause: Attempting to parse the name attribute.

Action: Log a bug against the application. Check the name attribute and remove space
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30049: "name" attribute set to "target", which will cause Javascript errors.

Cause: Attempting to parse the name attribute.

Action: Log a bug against the application. Check the name attribute and remove space
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30050: The value of the "{0}" attribute starts with "javascript:"; this is unnecessary, and in fact can lead to Javascript errors.

Cause: Attempting to write the html to the page.

Action: Fix the attribute in the jspx page. Log a bug against the application or if it is in the renderer, against the Apache Trinidad framework
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF_TRINID-30051: Elements not closed:

Cause: Attempting to write the html to the page.

Action: Fix the element in the jspx page. Log a bug against the application or if it is in the renderer, against the Apache Trinidad framework
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30052: Comments cannot include "--"

Cause: Attempting to write the html to the page.

Action: Fix this in the jspx page. Log a bug against the application or if it is in the renderer, against the Apache Trinidad framework
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30053: Ending {0} when {1} expected. Passes:{2}

Cause: Attempting to write the html to the page.

Action: Fix this in the jspx page.Log a bug against the application or if it is in the renderer, against the Apache Trinidad framework
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30054: Writing attribute outside of element

Cause: Attempting to write the html to the page.

Action: Fix this in the jspx page. Log a bug against the application or if it is in the renderer, against the Apache Trinidad framework
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30055: Attribute "{0}" output twice; writing attribute as "duplicate_{1}" instead.

Cause: Attempting to write the html to the page.

Action: Fix this in the jspx page. Log a bug against the application or if it is in the renderer, against the Apache Trinidad framework
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30056: Element End name:{0} does not match start name:{1}

Cause: Attempting to write the html to the page.

Action: Fix this in the jspx page. Log a bug against the application or if it is in the renderer, against the Apache Trinidad framework
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30057: GroupNode {0} refers to no valid node.

Cause: Attempting to process the group node.

Action: Log a bug against the Apache Trinidad framework.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30058: Exception creating model {0}

Cause: Attempting to create a menu model.

Action: Fix the menuModel. Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30059: EL Expression {0} is invalid or returned a bad value.

Cause: Attempting to create a menu model, and invalid EL expression was found.

Action: Fix the invalid EL expression. Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30060: Resource bundle {0} could not be found.

Cause: Attempting to load a bundle in the menu model.

Action: Make sure the resource bundle can be found. Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30061: error closing file:{0}

Cause: Attempting to process the region metatdata file.

Action: Fix the region metadata file to be a valid xml. Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30062: Error getting region-metadata files:{0}

Cause: Attempting to process the region metatdata file.

Action: Fix the region metadata file to be a valid xml and make sure it can be found on the filesystem. Log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30063: Error reading region-metadata file:{0}

Cause: Attempting to process the region metatdata file.

Action: Fix the region metadata file to be a valid xml. Log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30064: Replaced jspUri {0} with {1} for componentType:{2}

Cause: Attempting to process the region metatdata file.

Action: Fix the region metadata file to be a valid xml. Log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30065: Unknown element:{0} at {1}

Cause: Attempting to process the region metatdata file.

Action: Fix the region metadata file to be a valid xml. Log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30066: <{0}> is missing at {1}

Cause: Attempting to process the region metatdata file.

Action: Fix the region metadata file to be a valid xml. Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30067: Exception at {0}

Cause: Attempting to process the region metatdata file.

Action: Fix the region metadata file to be a valid xml. Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30068: Instantiation of Renderer {0} failed

Cause: Attempting to instantiate a Renderer failed.

Action: Check that your renderer is registered correctly in faces-config.xml. Log a bug against the application or Apache Trinidad framework.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30069: Renderer '{0}' not found for component family '{1}'

Cause: Attempting to instantiate a Renderer failed.

Action: Check that your renderer is registered correctly in faces-config.xml. Log a bug against the application or Apache Trinidad framework.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30070: There is no SkinFactory

Cause: Trying to find the SkinFactory failed. The SkinFactory was not registered.

Action: Log a bug against the application. Make sure the TrinidadFilter is installed since this registers the SkinFactory.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30071: The skin {0} specified on the requestMap will not be used because the styleSheetDocument id on the requestMap does not match the local skin's styleSheetDocument's id.

Cause: A skin was specified on the requestMap but it can't be used.

Action: Log a bug against the application. Check to make sure the jars on the portal server match the jars on the portlet server to make the skin's styleSheetDocument ids match.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30072: The skin {0} specified on the requestMap will not be used because its styleSheetDocument id was not in the requestMap and it is needed to compare with the local skin's styleSheetDocument's id to make sure the skins are the same.

Cause: A skin was specified on the requestMap but it can't be used.

Action: Log a bug against the application. Check to make sure the jars on the portal server match the jars on the portlet server to make the skin's styleSheetDocument ids match. Also, send the styleSheetDocument id to the server as well as the skin id.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30073: The skin {0} specified on the requestMap will not be used because it does not exist.

Cause: A skin was specified on the requestMap but it can't be used because it does not exist on the server.

Action: Log a bug against the application. Check to make sure the jars on the portal server match the jars on the portlet server to make the skin's styleSheetDocument ids match.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30074: Could not get skin {0} from the SkinFactory

Cause: Attempted to get a skin failed.

Action: Log a bug against the application. The skin requested was not registered with the SkinFactory on startup. Make sure the TrinidadFilter is installed.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30075: The java.io.File handle ("javax.servlet.context.tempdir") is not set in the ServletContext

Cause: Attempting to get the file handle from the ServletContext.

Action: Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30076: No AdfRenderingContext available

Cause: Attempting to get the RenderingContext failed.

Action: Check that your Trinidad jars are installed properly. Log a bug against the Apache Trinidad framework.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30077: Basic HTMLRenderKit could not be located

Cause: Attempting to locate the HTMLRenderKit failed.

Action: Check that your Trinidad jars are installed properly.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30078: Could not find basic HTML renderer for {0}, type={1}

Cause: Could not find basic HTML renderer.

Action: Check that your Trinidad jars are installed properly.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30079: Could not get stylesheet cache

Cause: Attempting to get the stylesheet cache failed.

Action: Make sure your stylesheet directory is writable.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30080: Model not specified for the chart component.

Cause: Attempting to get the model on the chart component failed.

Action: Specify the model for the chart component. Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30081: Trains must be used inside of a form

Cause: The train component is not inside a form component.

Action: Log a bug against the application. Put the train inside a form
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30082: Train expect a nodeStamp facet, no such facet was found for train {0}

Cause: Problem found while rendering the train.

Action: Log a bug against the application. Set a nodeStamp facet on the train
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30083: Visible stop count must be > 0, found {0}

Cause: Problem found while rendering the train.

Action: Log a bug against the application. Set the train visible count to > 0.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30084: Visible stop count must be an integer, found {0}

Cause: Problem found while rendering the train.

Action: Log a bug against the application. Set the train visible count to > 0.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30085: 'nodeStamp' facet missing!

Cause: Problem found while rendering the train.

Action: Log a bug against the application. Set a nodeStamp facet on the train
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30086: Frames must appear inside FrameBorderLayouts

Cause: Problem found while rendering frames.

Action: Log a bug against the application. Set frame inside of frameborderlayout
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30087: No PPR-capable 'id' found for elements of {0}. This component has not written-out an 'id' attribute.

Cause: Trying to PPR update components failed.

Action: Log a bug against the application. Add ids to your components.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30088: Invalid string attribute for chooseDate: {0}

Cause: Attempting to convert value to a Date.

Action: Log a bug against the application. See the chooseDate documentation.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30089: Unable to encode URL '{0}' using encoding '{1}'

Cause: Attempting to encode an url failed.

Action: Recheck your url to make sure it is valid. Log a bug against the Apache Trinidad framework.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30090: Sorting disabled; table is not in a form

Cause: Attempting to render a table that is not in a form.

Action: Log a bug against the application. Add a form as a parent to the table.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30091: {0}: Column used outside of a Table

Cause: Attempting to render a table that has a column outside of the table.

Action: Log a bug against the application. Put all column components inside a table component.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30092: Cannot add client side converter and validators as the node name is null

Cause: Attempting to add client-side converters and validators to the page.

Action: Log a bug against the applicaton. Set the node name.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30093: Null validators iterator for {0}

Cause: Attempting to process validators found null validator iterators.

Action: Log a bug against the application. Check the validators.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30094: There is already a converter on "{0}". There should only be one converter per component.

Cause: More than one converter found on a component.

Action: Log a bug against the application. Ensure you have only one converter per component in your page.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30095: frame:{0} is missing attribute:{1}

Cause: Missing attribute in frameborderlayout.

Action: Log a bug against the application. Add the missing attribute.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30096: Warning: illegal component hierarchy detected, expected UIXCommand but found another type of component instead.

Cause: Did not find the expected command component in the hierarchy.

Action: Log a bug against the application. Check your component hierarchy in your page.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30097: Warning: NavigationLevelRenderer was looking for child property "{0}" but none was found, it is likely that an unexpected child component was found (expected CommandNavigationItem).

Cause: Rendering navigationLevel component and did not find expected child.

Action: Log a bug against the application. Make sure CommandNavigationItem is a child of the navigationLevel component
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30098: PanelAccordion must be used inside of a form

Cause: Rendering panelAccordion that was not in a form.

Action: Log a bug against the application. Make sure panelAccordion is inside a form.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30099: Error during partial-page rendering

Cause: Rendering a partial-page pass failed.

Action: Log a bug against the application. Check your page to make sure you are using PPR correctly.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30100: The poll component must be inside of a form; disabling poll {0}

Cause: Rendering poll component that wasn't in a form component.

Action: Log a bug against the application. Make sure poll is inside a form
Level: 1

Type: WARNING

Impact: Logging

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

Cause: Rendering the shuttle component and the selected items.

Action: Log a bug against the application. Check the shuttle component and its children.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30102: showDetail is not in a form, and will not function correctly

Cause: Rendering showDetail component that wasn't in a form component.

Action: Log a bug against the application. Make sure showDetail is inside a form
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30103: Some entries in value of {0} not found in SelectItems: {1}

Cause: Rendering a selectMany component found inconsistency in selectItem values.

Action: Log a bug against the application. Check your selectMany components and the selectItems.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30104: Could not find selected item matching value "{0}" in {1}

Cause: Rendering a select component and found problem with the select items.

Action: Log a bug against the application. Check your select components and the value and selectItems
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30105: Table with id: {0} has no visible columns!

Cause: Rendering a table found no visible columns.

Action: Log a bug against the application. Make sure your table has at least one visible column.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30106: The tree component must be used inside of a form.

Cause: Rendering tree component that wasn't in a form component.

Action: Log a bug against the application. Make sure tree is inside a form
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30107: Couldn't find scriptlet: {0}

Cause: Rendering a component and a scriptlet could not be found.

Action: Check the code that registers teh scriptlet if this is in our component. Log a bug against the application or the Apache Trinidad framework.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30108: Unable to get resource {0}

Cause: Rendering a scriptlet.

Action: Log a bug against the Apache Trinidad framework. Possibly a problem in the build system.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30109: Apache Trinidad is running with debug javascript. Do not use in a production environment. See the "+_DEBUG_JAVASCRIPT+" parameter in /WEB-INF/web.xml

Cause: debug javascript is enabled in web.xml.

Action: Turn off debug javascript checking in a production environment in web.xml.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF_TRINID-30110: Illegal value:{0} for {1}

Cause: Rendering the table component and found illegal banding interval.

Action: Log a bug against the application. See the table and column component documentation regarding column and row banding intervals.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30111: Unknown value for align:{0}

Cause: Rendering the table component and found illegal value for the align attribute.

Action: Log a bug against the application. See the column component documentation for valid align attribute values.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30112: tableSelect components may only be used inside table and treeTable

Cause: While rendering tableSelect component the valid parent component was not found.

Action: Log a bug against the application. Make sure tableSelect components are inside table or treeTable.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30113: nodeStamp facet on treeTable:{0} is missing or not of type UIXColumn

Cause: While rendering a treeTable component, a problem with the nodeStamp facet was found.

Action: Log a bug against the application. See the treeTable documentation and check your jspx page.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30114: Unexpected tree state: focus rowKey is empty on an expand/collapse all request.

Cause: While rendering a tree component an unexpected tree state was found.

Action: Log a bug against the application. See the treeTable or tree documentation and check your jspx page.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30115: Page contains no form, it will not work properly

Cause: Rendering the page without a form component.

Action: Log a bug against the application. Make sure there is a form in the page
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30116: Only tr:showDetailItem is allowed as child of tr:panelTabbed.

Cause: While rendering a panelTabbed component an illegal child was found.

Action: Log a bug against the application. Use showDetailItem as the child of panelTabbed.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30117: Value for component with id '{0}' is not a valid BoundedRangeModel instance

Cause: Rendering component and found an invalid BoundedRangeModel.

Action: Log a bug against the application. See the BoundedRangeModel documentation.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30118: Resource "{0}" at path "{1}" not found

Cause: While rendering the resource was not found.

Action: Make sure the resource exists. Log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30119: Could not find bundle {0}

Cause: While rendering, a translation bundle could not be found.

Action: Log a bug against the Apache Trinidad framework. Make sure the jars are installed correctly.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30120: Required attribute "{0}" not found.

Cause: While rendering, a required attribute was not found.

Action: Set the required attribute on the component in the jspx file. Log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30121: {0} is not an understood child element

Cause: While parsing a document, an unknown element was found.

Action: Log a bug against the application. Check your jspx page in JDeveloper so it can flag the errors.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30122: "{0}" is not an understood attribute

Cause: While parsing the document, an unknown attribute was found.

Action: Log a bug against the application. Check your jspx page in JDeveloper so it can flag the errors.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30123: Only one child element is allowed here.

Cause: While parsing the document, an error was found.

Action: Log a bug against the application. Check your jspx page in JDeveloper so it can flag the errors.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30124: Could not parse value of attribute: {0}

Cause: While parsing the document, an error was found.

Action: Log a bug against the application. Check your jspx page in JDeveloper so it can flag the errors.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30125: Could not parse value of attribute: {0}, namespace={1}

Cause: While parsing the document, an error was found.

Action: Log a bug against the application. Check your jspx page in JDeveloper so it can flag the errors.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30126: Unknown attribute: {0}

Cause: While parsing the document, an error was found.

Action: Log a bug against the application. Check your jspx page in JDeveloper so it can flag the errors.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30127: Unknown attribute: {0}, namespace={1}

Cause: While parsing the document, an error was found.

Action: Log a bug against the application. Check your jspx page in JDeveloper so it can flag the errors.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30128: Error when parsing the skin css file. The property's name cannot be null or the empty string. The parser will ignore it. name is '{0}' and value is '{1}'

Cause: While parsing the skin css file, an error was found.

Action: Log a bug against the application. Check your skin css file.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30129: Ignoring properties {0} because there is no corresponding selector.

Cause: While parsing the skin css file, an error was found.

Action: Log a bug against the application. Check your skin css file.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30130: Error reading from the skin css file

Cause: While parsing the skin css file, an error was found.

Action: Log a bug against the application. Check your skin css file.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30131: Can't add Skin with null skinId or null skin

Cause: While registering skins, an error was found.

Action: Log a bug against the application. Check your trinidad-skins.xml file to make sure the skin is defined correctly.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30132: Can't get Skin with null skinId

Cause: While retrieving a skin, an error was found.

Action: Log a bug against the application. Check your trinidad-skins.xml file to make sure the skin is defined correctly.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30133: Can't find a skin that matches family {0} and renderkit {1}, so we will use the simple skin

Cause: While retrieving a skin, an error was found.

Action: Log a bug against the application. Check your trinidad-skins.xml file to make sure the skin is defined correctly. Check trinidad-config and the skin-family element. Make sure the skin's renderkitid matches the current renderkit id
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30134: Could not get the stylesheet document's timestamp because we couldn't open the connection.

Cause: Trying to get the skin's stylesheet document's timestamp failed.

Action: Log a bug against the application. Check the stylesheet document file and directory to make sure it can be opened.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30135: The following skins extend each other in a circular fashion or the skin they extend does not exist:{0}

Cause: While registering the skins from the trinidad-skins.xml files, an error was found.

Action: Log a bug against the application. Check all the trinidad-skins.xml files (even the ones in jars on the classpath) to fix any skins that extend others in a circular fashion.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30136: Unable to locate base skin "{0}" for use in defining skin of id "{1}", family "{2}", renderkit ID "{3}". Using the default base skin "{4}".

Cause: While registering the skins from the trinidad-skins.xml files, an error was found.

Action: Log a bug against the application. Check all the trinidad-skins.xml files (even the ones in jars on the classpath) to make sure the base skin exists and do not extend a skin that doesn't exist.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30137: Error parsing:{0}

Cause: While parsing the trinidad-skins.xml file, an error was found.

Action: Log a bug against the application. Check the trinidad-skins.xml files (even ones in jars) for format problems.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30138: error loading file:{0}

Cause: While attempting to load the trinidad-skins.xml file, an error was found.

Action: Log a bug against the application. Check the trinidad-skins.xml files (even ones in jars) for format problems.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30139: Could not load style sheet: {0}

Cause: Could not load the skin's css file.

Action: Log a bug against the application. Check the skin's css file to make sure it exists and the style-sheet-name url in trinidad-skins.xml is correct.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30140: IOException during parse of {0}

Cause: IOException while creating a skin's stylesheet document.

Action: Log a bug against the application. Check the stylesheet document.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30141: No styles found context - {0}

Cause: While creating the skin's stylesheet document, no styles were found that matched the StyleContext.

Action: Log a bug against the application. There should always be base skin definitions for all contexts.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30142: IOException while creating file: {0}

Cause: IOException while creating the skin's stylesheet document.

Action: Log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30143: Unable to generate the style sheet {0} in cache directory {1}.Please make sure that the cache directory exists and is writable.

Cause: Error while generating skin's stylesheet.

Action: Log a bug against the application. Make sure that the cache directory exists and is writable.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30144: IOException while opening file for writing: {0}

Cause: Error while generating skin's stylesheet.

Action: Log a bug against the application. Check the cache directory to make sure it is writable.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30145: The css file has hit IE's limit of 4095 CSS selectors. It has {0} selectors. The selectors after that will be ignored.

Cause: Error while generating the skin's stylesheet.

Action: Log a bug against the application. You will need to simplify your skinning file if possible. Otherwise log a bug against Apache Trinidad.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30146: Consecutive sub-element (::) syntax used in selector {0}. This is not supported.

Cause: Problem found in skin's stylesheet css file.

Action: Log a bug against the application. The skin's css file has two pseudo-elements in one selector and that is illegal in CSS.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30147: An url value delimited by url() is expected for the property '{0}' in style sheet '{1}'. Found: '{2}'.

Cause: Problem found in skin's stylesheet css file.

Action: Log a bug against the application. Check the skin's css file.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30148: Invalid image uri '{0}' in style sheet '{1}'

Cause: Problem found in skin's stylesheet css file.

Action: Log a bug against the application. Check the skin's css file.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30149: An empty URL was found in style sheet'{0}'

Cause: Problem found in skin's stylesheet css file.

Action: Log a bug against the application. Check the skin's css file.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30150: "<style> elements must have either a name or a selector attribute

Cause: Problem found in skin's XSS stylesheet.

Action: Log a bug against the application. Check the skin's XSS file.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30151: Could not parse import: {0}

Cause: Problem found in skin's stylesheet.

Action: Log a bug against the application. Check the skin's stylesheet files.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30152: Import missing required href attribute

Cause: Problem found in skin's stylesheet.

Action: Log a bug against the application. Check the skin's stylesheet files.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30153: 'componentType' attribute is required

Cause: Problem found processing page.

Action: Log a bug against the application. Check your jspx page in JDeveloper so it can flag the errors.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30154: Could not find metadata for componentType:{0} in region-metadata

Cause: Problem found processing page.

Action: Log a bug against the application. Check your jspx page in JDeveloper so it can flag the errors.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30155: There was no jspUri for componentType:{0}

Cause: Problem found processing page.

Action: Log a bug against the application. Check your jspx page in JDeveloper so it can flag the errors.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30156: attribute:{0} is missing on componentType:{1}

Cause: Problem found processing page.

Action: Log a bug against the application. Check your jspx page in JDeveloper so it can flag the errors.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30157: facetRef must be inside of a UIComponent tag.

Cause: Problem found processing page.

Action: Log a bug against the application. Check your jspx page in JDeveloper so it can flag the errors.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30158: Cannot find parent <tr:componentRef>>

Cause: Problem found processing page.

Action: Log a bug against the application. Check your jspx page in JDeveloper so it can flag the errors.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30159: facetName is required on facetRef

Cause: Problem found processing page.

Action: Log a bug against the application. Check your jspx page in JDeveloper so it can flag the errors.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30160: validator tag is not inside a UIComponent.

Cause: Problem found processing page.

Action: Log a bug against the application. Check your jspx page in JDeveloper so it can flag the errors.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30161: could not create validator for validatorId:{0} and binding:{1}

Cause: Problem found creating the validator.

Action: Log a bug against the application. Check your jspx page in JDeveloper so it can flag the errors.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30162: attribute 'validatorId' is missing

Cause: Problem found creating the validator.

Action: Log a bug against the application. Check your jspx page in JDeveloper so it can flag the errors.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30163: Could not parse value {0} into a Date using pattern "yyyy-MM-dd"; ignoring.

Cause: Problem found parsing the date value.

Action: Log a bug against the application. Check the jspx page. Use the yyyy-MM-dd format.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF_TRINID-30164: No RendererFactory registered for components in namespace {0}

Cause: RendererFactory not registered.

Action: Log a bug against the Apache Trinidad framework. Make sure the Trinidad and jsf jars are installed correctly.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30165: No Renderer registered for {0}

Cause: Renderer was not registered.

Action: Log a bug against the Apache Trinidad framework or the application. Check the faces-config.xml file.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30166: Could not get image cache

Cause: Could not find the image cache.

Action: Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30167: Cannot convert {0} of class:{1} into DataObjectList

Cause: Creating a DataObjectList adapter class around an object fails

Action: Log a bug against the Apache Trinidad framework.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF_TRINID-30168: Could not convert {0} into a {1}

Cause: Error converting a value into another value.

Action: Log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30169: Unsupported UINode:{0}, path = {1}

Cause: Unsupported UINode found while rendering.

Action: Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30170: Invalid value. Defaulting component with id '{0}' to indeterminate mode

Cause: Invalid value rendering processing component.

Action: Log a bug against the application. Check your jspx page in JDeveloper so it can flag the errors.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30171: No form found for {0}

Cause: Rendering a component that wasn't in a form component.

Action: Log a bug against the application. Make sure your form components are inside a form. Check your jspx page in JDeveloper so it can flag the errors.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30172: Could not get image provider for icon: {0}

Cause: Error while attempting to get image provider.

Action: Log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30173: Could not get colorized icon for: {0}

Cause: Error while attempting to get colorized image.

Action: Log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30174: Could not find icon with key given

Cause: Error while attempting to get colorized image.

Action: Log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30175: Could not find renderer for alias {0}

Cause: Error finding renderer.

Action: Check the faces-config.xml file to make sure the renderer is registered. Log a bug against the Apache Trinidad framework.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30176: Unable to flip icon '{0}' because it is not under the current request context, which is '{1}'

Cause: Error trying to flip laf icon.

Action: Log a bug against the Apache Trinidad framework.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30177: Could not locate parent form for formValue {0}

Cause: Rendering the page and couldn't find a form as a parent..

Action: Log a bug against the application. Make sure the formValue has a form parent.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30178: The component is null for node with local name {0}

Cause: Error while finding component.

Action: Check the faces-config.xml file to make sure the component/renderers are registered. Log a bug against the Apache Trinidad framework.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30179: Could not get flipped icon for: {0}

Cause: Error while trying to find a flipped icon.

Action: Log a bug against the Apache Trinidad framework.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30180: The node name is null and therefore no client side required validator added for node with local name {0}

Cause: Error finding validator.

Action: Log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30181: Could not find class {0}

Cause: Error finding class in Coercions.

Action: Make sure the jars are installed correctly. Log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30182: Could not load class {0}:{1}

Cause: Error finding class in Coercions.

Action: Make sure the jars are installed correctly. Log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30183: Method {0} does not return an Icon

Cause: Error attempting to retrieve an Icon.

Action: Log a bug against the Apache Trinidad framework.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30184: Could not find method {0} in {1}

Cause: Error trying to find method.

Action: Log a bug against the Apache Trinidad framework.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30185: Could not find access {0} in {1}

Cause: This error is no longer in the code.

Action: Log a bug against the Apache Trinidad framework.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30186: Required element 'skin-id' not found.

Cause: Error in trinidad-skins.xml file.

Action: Log a bug against the appication. Check the trinidad-skins.xml file and make sure your skin has a skin-id
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30187: Required element 'style-sheet-name' not found.

Cause: Error in trinidad-skins.xml file.

Action: Log a bug against the appication. Check the trinidad-skins.xml file and make sure your skin has a style-sheet-name
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30188: Required element 'id' not found.

Cause: Error in trinidad-skins.xml file.

Action: Log a bug against the appication. Check the trinidad-skins.xml file and make sure your skin has a unique id.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30189: Required element 'family' not found.

Cause: Error in trinidad-skins.xml file.

Action: Log a bug against the appication. Check the trinidad-skins.xml file and make sure your skin has the skin-family set.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30190: Malformed property entry: {0}={1}

Cause: Error in renderertype-localname.properties.

Action: Log a bug against the Apache Trinidad framework.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30191: Could not load renderer type to local name mapping.

Cause: Error in renderertype-localname.properties.

Action: Log a bug against the Apache Trinidad framework.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30192: Encoding {0} is not supported at the client side. This will skip client side validation.

Cause: Attempting to use an encoding the client doesn't support.

Action: Contact the system administrator to see if the encoding is supposed to be supported.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30193: The TrinidadFilter has not been installed. Apache Trinidad requires this filter for proper execution.

Cause: Detected that the TrinidadFilter was not installed.

Action: Log a bug against the application. Install the TrinidadFilter; see web.xml
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30194: mergeCapabilities() may only be used with Agents created by this class.

Cause: Attempting to merge capabilities with unsupported agent.

Action: Use a supported agent/browser. Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30195: Invalid Namespace: {0}

Cause: Invalid namespace parsing capabilities document.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30196: Invalid Root Element: {0} {1}

Cause: Invalid root element parsing capabilities document.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30197: Unexpected ''\''.

Cause: Error parsing agent's name and version.

Action: Log a bug against the Apache Trinidad framework. Try a different browser.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30198: Unexpected character. Expecting ''.'' or ''\''

Cause: Error parsing agent's name and version.

Action: Log a bug against the Apache Trinidad framework. Try a different browser.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30199: Unexpected character. Expecting ''*''

Cause: Error parsing agent's name and version.

Action: Log a bug against the Apache Trinidad framework. Try a different browser.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30200: Expecting char

Cause: Error parsing agent's name and version.

Action: Log a bug against the Apache Trinidad framework. Try a different browser.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30201: Unterminated quote.

Cause: Error parsing agent's name and version.

Action: Log a bug against the Apache Trinidad framework. Try a different browser.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30202: Unexpected char.

Cause: Error parsing agent's name and version.

Action: Log a bug against the Apache Trinidad framework. Try a different browser.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30203: Invalid saved state object

Cause: Saved state wasn't an instance of PageState.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30204: Don't support transient here

Cause: transient isn't supported.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30205: Per-request disk space limits exceeded.

Cause: per-request disk space limits exceeded.

Action: See the System Administrator.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30206: popView(): No view has been pushed.

Cause: IlegalStateException in DialogService.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30207: popView(): No view has been pushed.

Cause: IlegalStateException in DialogService.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30208: You must call next() at least once

Cause: This is no longer an error in the code.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30209: {0} UnsupportedOperationException

Cause: This is no longer an error in the code.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30210: Only HttpServletRequest supported

Cause: Attempting to get a paramter from ServletExternalContext without a HTTPServletRequest.

Action: Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30211: {0} can not be null.

Cause: Attempting to get a paramter from ServletExternalContext without a HTTPServletRequest.

Action: Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30212: Request is null on this context.

Cause: Calling ServletExternalContext's dispatch without a servletRequest.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30213: Response is null on this context.

Cause: Calling ServletExternalContext's dispatch without a servletResponse.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30214: Unsupported conversion from:{0} to:{1}

Cause: IllegalArgumentException while converting values in the BaseConverter.

Action: Check the converter code. Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30215: Cannot convert to:{0}"

Cause: This is no longer an error in the code.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30216: Null name

Cause: The name attribute is null.

Action: Log a bug against the application. Set the name to a non-null value.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30217: Null value

Cause: The value attribute is null.

Action: Log a bug against the application. Set the value to a non-null value.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30218: putAll operation not supported for WrappingMap

Cause: UnsupportedOperationException, the WrappingMap which implements Map does not support the putAll operation and it was called.

Action: Log a bug against the Apache Trinidad framework. Fix code to not call putAll.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30219: clear operation not supported for WrappingMap

Cause: UnsupportedOperationException, the WrappingMap which implements Map does not support the clear operation and it was called.

Action: Log a bug against the Apache Trinidad framework. Fix code to not call clear.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30220: Problem loading...

Cause: While generating images, there was a problem.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30221: While grabbing pixels:

Cause: While generating images, there was a problem.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30222: Error while fetching image. grabbed {0} pixel values of the {1} x {2} image.

Cause: While generating images, there was a problem.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30223: Exceeded gif color limit.

Cause: While generating images, there was a problem.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30224: No space left for transparency

Cause: While generating images, there was a problem.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30225: Different lengths - sourceColors and targetColors

Cause: While generating images, there was a problem.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30226: Cannot yet nest:{0} elements

Cause: Region metadata was nested and it shouldn't be.

Action: Log a bug against the application. Do not nest region metadata in your page. Use JDeveloper to check the syntax of your page.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30227: Duplicate renderer type "{0}" for family "{1}"

Cause: Attempting to add a duplicate renderer for a family to the render kit.

Action: Log a bug against the Apache Trinidad framework. Check the renderer registration in the faces-config.xml file.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30228: No returnId is available for returning from the dialog; this usually means that you aren't in a dialog in the first place.

Cause: Returning from a dialog and found no returnId.

Action: Log a bug against the application. To return from a dialog, you need to be in a dialog, or make the pageFlowScope available
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30229: TrainRenderer can only renders instances of {0}, found {1}

Cause: While rendering the train the wrong instance was found.

Action: Log a bug against the application. Check your jspx page.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30230: SelectOne submittedValue's index {0} is out of bounds. It should be between 0 and {1}

Cause: Rendering the selectOne component, the submittedValue was out of bounds from what it should be.

Action: Log a bug against the application. Possibly the model changed when it shouldn't have, so check the model.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30231: SelectOne could not convert submittedValue's index {0} into int {1}

Cause: While rendering the selectOne component, the submittedValue couldn't be converted to an int.

Action: Log a bug against the application. Check the selectOne component's model.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30232: Don't call this for column headers

Cause: While rendering the table, the method getHeaderFormatClass was called for a column header.

Action: Log a bug against the Apache Trinidad framework. Fix code to not call the method for a column header.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30233: contextURI is null

Cause: Attempting to get a configuration context url where the directory is unavailable.

Action: Log a bug against the Apache Trinidad framework. Check the directory.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30234: context URI for {0} ends with a slash

Cause: The configuration context URI ends with a slash and it shouldn't.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30235: contextPath is null {0}

Cause: The configuration context path is null.

Action: Log a bug against the Apache Trinidad framework
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30236: Registered null URI

Cause: Registering a configuration url and found it is null.

Action: Log a bug against the Apache Trinidad framework
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30237: A null path was registered for {0}

Cause: Registering a configuration found a null path being registered.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30238: No base path registered

Cause: Registering a configuration found no base path was registered.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30239: # of keys and values must match

Cause: While processing ServletRequestParameters an error was found.

Action: Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30240: {0} is not a character

Cause: Trying to coerce a type to a character and found that it wasn't a character.

Action: Log a bug against the application. Check the valuebindings.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30241: Could not find class {0}

Cause: Error finding class in Coercions.

Action: Log a bug against the application. Check the valuebindings.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30242: {0} cannot be parsed into a {1}

Cause: Attempting to coerce a value.

Action: Log a bug against the application. Check the valuebindings.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30243: type is null

Cause: Attempting to coerce a value.

Action: Log a bug against the application. Check the valuebindings.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30244: Could not coerce value of type {0} into type {1}

Cause: Attempting to coerce a value.

Action: Log a bug against the application. Check the valuebindings.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30245: {0} cannot be coerced into a java.awt.Color

Cause: Attempting to coerce a value.

Action: Log a bug against the application. Check the valuebindings.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30246: Could not find {1}

Cause: Attempting to find file failed.

Action: Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30247: DecimalFormatContext is not cloneable!

Cause: IllegalStateException while attempting to clone the DecimalFormatContext.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30248: User-defined subclasses not supported.

Cause: IllegalStateException because you cannot subclass the LocaleContextImpl.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30249: Unknown reading direction: {0}

Cause: Attempting to set the reading direction to an unknown value.

Action: Log a bug against the application. Try a different browser.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30250: Format.parseObject(String) failed

Cause: Attempting to parse a ColorFormat failed.

Action: Ensure the ColorFormat is correct. Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30251: Cannot format given Object as a Color

Cause: Attempting to parse a ColorFormat failed.

Action: Ensure the ColorFormat is correct. Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30252: Illegal pattern character ''{0}''

Cause: Attempting to parse a ColorFormat failed.

Action: Ensure the ColorFormat is correct. Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30253: Illegal pattern character ''{0}''

Cause: Attempting to parse a ColorFormat failed.

Action: Ensure the ColorFormat is correct. Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30254: FastMessageFormat only supports numeric arguments

Cause: IllegalArgumentException, in FastMessageFormat while formatting.

Action: Use only numeric arguments in FastMessageFormat. Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30255: End of pattern not found

Cause: IllegalArgumentException, in FastMessageFormat while formatting.

Action: Fix the pattern in FastMessageFormat. Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30256: FastMessageFormat: empty argument - {} - found

Cause: IllegalArgumentException, in FastMessageFormat while formatting.

Action: Fix the FastMessageFormat. Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30257: Content is not multipart form data

Cause: IllegalStateException while attempting to create a MultipartFormHandler for the given InputStream and content

Action: Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30258: Item is not a file

Cause: IOException while attempting to create a MultipartFormHandler for the given InputStream and content

Action: Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30259: Item has already been read past.

Cause: IOException while attempting to create a MultipartFormHandler for the given InputStream and content

Action: Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30260: Input stream has already been requested.

Cause: IOException while attempting to create a MultipartFormHandler for the given InputStream and content

Action: Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30261: Uploaded file of length {0} bytes exceeded maximum allowed length ({1} bytes)

Cause: EOFException while attempting to create a MultipartFormHandler for the given InputStream and content

Action: Use smaller files. Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30262: Item has already been read past.

Cause: IOException while attempting to create a MultipartFormHandler for the given InputStream and content

Action: Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30263: End Of File

Cause: IOException while attempting to create a MultipartFormHandler for the given InputStream and content

Action: Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30264: Undeclared prefix: {0}

Cause: Exception while attempting to parse the namespace from a value.

Action: Log a bug against the application. Check the format of the namespace in the file that is being parsed. JDeveloper will flag errors.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30265: parser is null

Cause: While setting up the ParserManager, a null parser was passed in.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30266: Both rootClass and rootParser are null

Cause: While parsing an xml document the root parser and root class were null.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30267: Circular include of {0} detected!

Cause: SAXParseException while parsing an xml file because a cirular include was detected.

Action: Log a bug against the application. Check the file that is being parsed and remove the circular include.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30268: Null id

Cause: While creating a SkinExtension the skin id was null.

Action: Log a bug against the application. Check that the skin-extensions (defined in trinidad-skins.xml) have an id specified.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30269: Null lContext

Cause: While getting a translated value from the Skin, the locale context was null.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30270: Null iconName

Cause: A null icon was being registered with the Skin.

Action: Log a bug against the Apache Trinidad framework. Check the skin-extensions to make sure the icons are defined correctly.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30271: "Null styleSheetName"

Cause: A null stylesheet was being registered with the Skin.

Action: Log a bug against the Apache Trinidad framework. Check the skin-extensions to make sure the stylesheet name is defined correctly.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30272: No Skin specified.

Cause: Creating a SkinStyleProvider with no skin object.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30273: Null inputStream

Cause: NullPointerException, no inputStream while parsing trinidad-skins.xml file.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30274: Null parserManager

Cause: NullPointerException, no parserManager while parsing trinidad-skins.xml file.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30275: Required XSS file {0} does not exist.

Cause: While registering a skin, the required XSS file does not exist.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30276: Null sourceName

Cause: No source name found while parsing the skin's xss stylesheet.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30277: Null argument

Cause: Error registering a look and feel extension, null baselookandfeel, id or family.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30278: Null propertyName

Cause: While trying to parse an include from an xss file a null property name was found.

Action: Log a bug against the application. Check the xss file being parsed for a null property name.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30279: PropertyNode's name cannot be null or the empty string.name is ''{0}'' and value is ''{1}''

Cause: While trying to parse an include from an xss file a null property name was found.

Action: Log a bug against the application. Check the xss file being parsed for a null property name.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30280: child not instance of PropertyNode

Cause: While trying to parse an include from an xss file an invalid child node was found.

Action: Log a bug against the application. Check the xss file being parsed.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30281: child not an instance of IncludePropertyNode

Cause: While trying to parse an include from an xss file an invalid child node was found.

Action: Log a bug against the application. Check the xss file being parsed.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30282: Not nested in a UIComponentTag

Cause: JSPException while processing an attribute tag.

Action: Log a bug against the application. Check the jspx page and fix error.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30283: No component associated with UIComponentTag

Cause: JSPException while processing an attribute tag.

Action: Log a bug against the application. Check the jspx page and fix error.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30284: Name attribute cannot be EL bound

Cause: JSPException while processing an attribute tag.

Action: Log a bug against the application. Check the jspx page and fix error.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30285: "componentDef cannot be run as a stand-alone. It must be included inside a JSF component tree.

Cause: JSPException while processing an componentDef tag.

Action: Log a bug against the application. Check the jspx page and fix error.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30286: componentDef must be included as a child of an <tr:componentRef>.

Cause: JSPException while processing an componentDef tag.

Action: Log a bug against the application. Check the jspx page and fix error.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30287: tr:componentDef does not support EL on ''var''

Cause: JSPException while processing an componentDef tag.

Action: Log a bug against the application. Check the jspx page and fix error.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30288: "items" must be a simple JSF EL expression

Cause: IllegalArgumentException while processing a forEach/items tags.

Action: Log a bug against the application. Check the jspx page and fix error with 'items'.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30289: "var" cannot be an expression

Cause: IllegalArgumentException while processing a forEach tag.

Action: Log a bug against the application. Check the jspx page and fix error with 'var'.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30290: "varStatus" cannot be an expression

Cause: IllegalArgumentException while processing a forEach tag.

Action: Log a bug against the application. Check the jspx page and fix error with 'varStatus'.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30291: "items" must point to a List or array

Cause: IllegalArgumentException while processing a forEach/items tags.

Action: Log a bug against the application. Check the jspx page and fix error with 'items'.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30292: ''begin'' and ''end'' should be specified if ''items'' is not specified

Cause: IllegalArgumentException while processing a forEach tag.

Action: Log a bug against the application. Check the jspx page and fix error.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30293: ''var'' and ''varStatus'' must not have same value

Cause: IllegalArgumentException while processing a forEach tag.

Action: Log a bug against the application. Check the jspx page and fix error.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30294: ''begin'' < 0

Cause: IllegalArgumentException while processing a forEach tag.

Action: Log a bug against the application. Check the jspx page and fix error.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30295: ''step'' < 1

Cause: IllegalArgumentException while processing a forEach tag.

Action: Log a bug against the application. Check the jspx page and fix error.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30296: ResetActionListener must be inside of a UIComponent tag.

Cause: JSPException while processing an resetActionListener tag.

Action: Log a bug against the application. Check the jspx page and fix error.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30297: returnActionListener must be inside of a UIComponent tag.

Cause: JSPException while processing an returnActionListener tag.

Action: Log a bug against the application. Check the jspx page and fix error.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30298: setActionListener must be inside of a UIComponent tag.

Cause: JSPException while processing an setActionListener tag.

Action: Log a bug against the application. Check the jspx page and fix error.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30299: setActionListener's ''to'' attribute must be an EL expression.

Cause: JSPException while processing an setActionListener tag.

Action: Log a bug against the application. Check the jspx page and fix error.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30300: Color code {0} in ''{1}'' does not start with a ''#''

Cause: ParseException processing the chooseColor's colordata.

Action: Log a bug against the application. Start the color code with a '#'.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30301: This method changed to getRenderer(RenderingContext, UINode)

Cause: IllegalStateException, calling an unsupported method.

Action: Log a bug against the Apache Trinidad framework. Call the correct method
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30302: Replaced in 2.0 by getIndexedNodeList()

Cause: IllegalStateException, calling an unsupported method.

Action: Log a bug against the Apache Trinidad framework. Call the correct method
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30303: Instantiation of UIX Components Renderer failed, class {0} not found.

Cause: Attempting to register a uix component rendered failed.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30304: Reusing role index

Cause: IllegalArgumentException creating NodeRoles.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30305: Attempt to register a null renderer for {0}

Cause: Attempting to register a null renderer.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30306: Only ContextBasedConfiguration is supported

Cause: Attempting to set an invalid configuration type on the RenderingContext.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30307: The facet may not be set after the RendererManager has been assigned.

Cause: IllegalStateException trying to set the facet after the RendererManager has been assigned.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30308: It is illegal to set children on a {0}

Cause: UnsupportedOperationException trying to replace a child.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30309: It is illegal to add children to a {0}

Cause: UnsupportedOperationException trying to add a child.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30310: It is illegal to remove children from a {0}

Cause: UnsupportedOperationException trying to remove a child.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30311: It is illegal to set children on an UnmodifiableCompoundNodeList

Cause: UnsupportedOperationException trying to modify a child.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30312: It is illegal to add children to an UnmodifiableCompoundNodeList

Cause: UnsupportedOperationException trying to add a child.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30313: It is illegal to remove children from an UnmodifiableCompoundNodeList

Cause: UnsupportedOperationException trying to remove a child.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30314: Adapter class doesn't implement BeanDOAdapter

Cause: IllegalArgumentException registered ia BeanAdapter class.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30315: {0} is not an instance of {1}

Cause: IllegalArgumentException trying to attach an instance of the bean class to the adapter.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30316: leftSideValue is null

Cause: Attempting to create a ComparisonBoundValue caused IllegalArgumentException.

Action: Log a bug against the appication.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30317: rightSideValue is null

Cause: Attempting to create a ComparisonBoundValue caused IllegalArgumentException.

Action: Log a bug against the appication.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30318: Unknown comparison

Cause: Attempting to create a ComparisonBoundValue caused IllegalArgumentException.

Action: Log a bug against the appication.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30319: test BoundValue required

Cause: Attempting to create a IfBoundValue with IllegalArgumentException.

Action: Log a bug against the appication.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30320: Null list argument

Cause: NullPointerException in deprecated code.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30321: Null data object argument

Cause: NullPointerException in deprecated code.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30322: No factory registered for {0}

Cause: No renderer factory found in LookAndFeelExtension.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30323: Null baseScorer

Cause: NullPointerException in skinning's NameOnly scorer.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30324: Null baseScore

Cause: NullPointerException in skinning's NameOnly scorer.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30325: Facet {0} is not supported on {1}

Cause: IllegalArgumentException returning Skins RendererFactory.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30326: # of keys and values much match

Cause: Error encoding the Javascript event object because the number of keys and values did not match.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30327: child is not null and not an instance of IconNode

Cause: This error is no longer in the code.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30328: "Null renderers or no renderers passed"

Cause: This error is no longer in the code.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30329: Null child or child not an instance of RendererNode

Cause: This error is no longer in the code.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30330: Null family

Cause: While parsing skin nodes a null skin-family was found.

Action: Log a bug against the application. Check all trinidad-skins.xml on classpath and WEB-INF and make sure that the skin-family is set for each skin
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30331: Non Null child and child not an instance of SkinPropertyNode

Cause: This error is no longer in the code.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30332: RenderingContext has already been created!

Cause: Attempting to create a RenderingContext when it already exists.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30333: {0} not superclass of {1}

Cause: IntrospectionException

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30334: Unexpected reflection exception: {0}

Cause: This error is no longer in the code.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30335: Javascript does not support null keys

Cause: IllegalArgumentException while encoding a Map in JavaScript Object Notation.

Action: Do not use null keys. Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30336: Encoding: {0} is unsupported by JVM

Cause: IllegalCharsetNameException while enabling byte length validation at the client side.

Action: Use a supported JVM. Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

4 ADFC-00001 to ADFC-14016

ADFC-00001: An exception is encountered.

Cause: An unknown problem caused an exception.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00002: The ADF Controller cannot run without {0}. Ensure that ''{1}'' is present in the classpath.

Cause: The ADF Controller was unable to locate the required class on the classpath.

Action: Modify the classpath to include the required class.
Level: 2

Type: ERROR

Impact: Installation

ADFC-00003: AdfFacesContext is not found. The ADF Controller cannot run.

Cause: The ADF Controller was unable to locate the required class on the classpath.

Action: Modify the classpath to include the required class.
Level: 2

Type: ERROR

Impact: Installation

ADFC-00004: RequestContext is not found. The ADF Controller cannot run.

Cause: The ADF Controller was unable to locate the required class on the classpath.

Action: Modify the classpath to include the required class.
Level: 2

Type: ERROR

Impact: Installation

ADFC-00005: The ADF Controller cannot execute task flow template ''{0}''.

Cause: An attempt was made to execute a task flow template. Task flow templates cannot be executed.

Action: Correct the associated task flow call activity to refer to a task flow definition.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00006: Existing transaction is required when calling task flow ''{0}''.

Cause: The ADF Controller attempted to enter a task flow that requires an existing transaction, but no transaction was open.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00007: Transaction type is unknown.

Cause: The ADF Controller encountered an unknown transaction type.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00008: The ADF Controller is unable to find DataControlFrame for a task flow.

Cause: The ADF Controller was unable to find the model layer DataControlFrame for a task flow.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00010: A DataControlFrame savepoint handle does not exist.

Cause: Restore of a DataControlFrame savepoint was attempted when a savepoint handle did not exist. Savepoint handle can become null after an ADFc save for later savepoint was restored.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00011: The ADF Controller is unable to create an MDSSession. See exception for details.

Cause: The ADF Controller requires an MDSSession to locate metadata. An attempt to create an MDSSession failed. This could be caused by a number of problems.

Action: See the accompanying exception.
Level: 2

Type: ERROR

Impact: Configuration

ADFC-00012: The ADF Controller is unable to parse configuration file adf-config.xml.

Cause: An unspecified error occurred while parsing configuration file adf-config.xml.

Action: See the accompanying exception.
Level: 2

Type: ERROR

Impact: Configuration

ADFC-00013: Configuration file adf-config.xml has too many ''{0}'' elements.

Cause: Configuration file adf-config.xml contained more instances of the specified element than are allowed.

Action: Correct the contents of the file.
Level: 2

Type: ERROR

Impact: Configuration

ADFC-00014: Configuration file adf-config.xml contains duplicate phase-listener ''{0}'' registrations.

Cause: One or more phase-listeners had the same listener-id value.

Action: Correct the contents of the file.
Level: 2

Type: ERROR

Impact: Configuration

ADFC-00015: Configuration file adf-config.xml contains duplicate phase-listener ''{0}'' in either 'before-id-set' or 'after-id-set'.

Cause: A phase-listener was specified twice in the same set.

Action: Correct the contents of the file.
Level: 2

Type: ERROR

Impact: Configuration

ADFC-00016: Configuration file adf-config.xml contains an invalid value: [element, value] = [''{0}'', ''{1}''].

Cause: Configuration file adf-config.xml contained invalid XML.

Action: Correct the contents of the file.
Level: 2

Type: ERROR

Impact: Configuration

ADFC-00017: Configuration file adf-config.xml does not contain mandatory element ''{0}''.

Cause: Configuration file adf-config.xml contained invalid XML.

Action: Correct the contents of the file.
Level: 2

Type: ERROR

Impact: Configuration

ADFC-00018: EL expression for UrlParameterConverter is null.

Cause: An attempt was made to convert a URL parameter, but the converter EL expression was null.

Action: Correct the metadata for the converter.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00019: An incorrect object is specified by EL expression ''{0}'' for a URL parameter converter.

Cause: An object was specified by the EL expression that did not implement the oracle.adf.controller.UrlParameterConverter interface.

Action: Specify an object that implements the oracle.adf.controller.UrlParameterConverter interface.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00020: Task flow ''{0}'' requires a new transaction, but a transaction is already open on the frame.

Cause: A new transaction could not be started on the frame because a transaction was already open.

Action: Correct the application's flow or the task flow's metadata.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00021: Task flow ''{0}'' requires a shared DataControlFrame but parent frame is null.

Cause: The task flow is configured to share its DataControl scope with its parent. The parent DataControlFrame is null.

Action: Correct the application's flow or the task flow's metadata.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00022: Unable to create logger ''{0}''.

Cause: An attempt was made to create a logger with a null name.

Action: Contact your Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADFC-00023: The ControllerContext is null.

Cause: The ControllerContext was found to be null when expected to be non-null.

Action: Contact your Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Programmatic

ADFC-00024: No ExternalContext could be found.

Cause: No ExternalContext value could be found.

Action: Contact your Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Programmatic

ADFC-00025: The ADF controller has not been successfully initalized.

Cause: The ADF controller has not been successfully initialized, probably due to a configuration error.

Action: Contact the system administrator and inspect the server logs for information on why the initialization failed.
Level: 2

Type: ERROR

Impact: Configuration

ADFC-00026: Attempt made to unlock a request lock that is not locked.

Cause: Attempt made to unlock a request lock that is not locked.

Action: Contact the system administrator and inspect the server logs.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00027: Attempt to modify a reuqest lock by another request.

Cause: Attempt to modify a reuqest lock by another request.

Action: Contact the system administrator and inspect the server logs.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00028: The ADF controller encountered an error while parsing the /WEB-INF/web.xml file.

Cause: The ADF controller encountered an error while parsing the /WEB-INF/web.xml file.

Action: Review the /WEB-INF/webg.xml file and inspect the server logs for information on why the parsing failed.
Level: 2

Type: ERROR

Impact: Configuration

ADFC-00029: Attempt to acquire the root view port request lock faild due to a timeout.

Cause: Typically caused by another thread holding the request lock for to long, possible due to a deadlock.

Action: Contact the system administrator and inspect the server logs.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-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-00621: The ADF Controller is unable to make a view bookmarkable.

Cause: The ADF Controller was unable to make a view bookmarkable.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00622: Attempt to set view port view ID outside of INVOKE_APPLICATION phase.

Cause: The view ID of a view port may only be set during the INVOKE_APPLICATION phase of the request lifecycle.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00625: A new session URL may only be requested during the RENDER_RESPONSE phase.

Cause: A request for a new session URL was made during an incorrect phase of the request lifecycle.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-02000: The ADF Controller is not able to initialize the metadata service.

Cause: The ADF Controller was unable to initialize the metadata service.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Configuration

ADFC-02001: The ADF Controller cannot find ''{0}''.

Cause: An attempt was made to load metadata that cannot be found.

Action: Verify that all required files are available.
Level: 2

Type: ERROR

Impact: Files

ADFC-02002: The ADF Controller cannot parse the task flow metadata.

Cause: The metadata did not represent a valid task flow.

Action: See the associated exceptions. Validate the metadata.
Level: 2

Type: ERROR

Impact: Compliance

ADFC-02003: Default activity must be specified in task flow definition ''{0}''.

Cause: The ADF Controller was unable to find task flow default activity in the task flow definition.

Action: Add a default activity to the task flow definition.
Level: 2

Type: ERROR

Impact: Compliance

ADFC-02004: Default activity ID ''{0}'' is invalid.

Cause: The ADF Controller was unable to construct the default activity ID.

Action: Correct the default activity ID.
Level: 2

Type: ERROR

Impact: Compliance

ADFC-02005: Task flow definition is not found: ''{0}''.

Cause: An attempt was made to read the specified task flow. The task flow cannot be found.

Action: Verify that the required file is available.
Level: 2

Type: ERROR

Impact: Compliance

ADFC-02006: A task flow ID is not found in the URL.

Cause: The specified task flow ID was requested and could not be found.

Action: Verify that the task flow reference is correct. Verify that all required files can be found.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-02007: A task flow document is not found in the URL.

Cause: An attempt was made to access a task flow using URL parameters. The specified document could not be found.

Action: Correct the value for the document parameter.
Level: 2

Type: ERROR

Impact: Browser

ADFC-02008: The value for 'documentName' cannot be null or empty.

Cause: An attempt was made to reference a task flow using a null value for 'documentName'.

Action: Correct the value.
Level: 2

Type: ERROR

Impact: Compliance

ADFC-02009: The value for 'localTaskFlowId' cannot be null or empty.

Cause: An attempt was made to reference a task flow using a null value for 'localTaskFlowId'.

Action: Correct the value.
Level: 2

Type: ERROR

Impact: Compliance

ADFC-02010: The value for 'localTaskFlowId' cannot be '#'.

Cause: An attempt was made to reference a task flow using an invalid value for 'localTaskFlowId'.

Action: Correct the value.
Level: 2

Type: ERROR

Impact: Compliance

ADFC-02011: The value for 'localActivityId' cannot be null or empty.

Cause: An attempt was made to construct an oracle.adf.controller.internal.metadata.ActivityId using an invalid value for 'localActivityId'.

Action: Correct the value.
Level: 2

Type: ERROR

Impact: Compliance

ADFC-02012: The activity ID string cannot be null or empty.

Cause: An attempt was made construct an oracle.adf.controller.internal.metadata.ActivityId using an invalid value.

Action: Correct the value.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-02013: The ADF Controller cannot find metadata for activity ''{0}''.

Cause: An attempt was made to access an activity that has no metadata defined.

Action: Validate the task flow document.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-02014: No activity implementation is available for activity type ''{0}''.

Cause: An attempt was made to access an activity that is not a known activity type.

Action: Validate the task flow document.
Level: 2

Type: ERROR

Impact: Compliance

ADFC-02015: Task flow ID ''{0}'' in document ''{1}'' is invalid.

Cause: The ADF Controller was unable to construct the task flow ID.

Action: Correct the task flow ID.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-02016: A possible cyclic reference to template ''{0}'' is detected when parsing ''{1}''.

Cause: The task flow metadata references a template that is already referenced by this task flow.

Action: Verify that the task flow templates do not reference each other in a cyclic manner.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-02017: The value for 'url' cannot be null or empty.

Cause: An attempt was made to reference a URL view activity using a null value for 'url'.

Action: Correct the value.
Level: 2

Type: ERROR

Impact: Browser

ADFC-02018: Root tag ''{0}'' in ''{1}'' does not match <adfc-config>.

Cause: A document with an invalid root tag was referenced.

Action: Correct the root tag.
Level: 2

Type: ERROR

Impact: Compliance

ADFC-02019: No activities are specified in task flow definition ''{0}''.

Cause: The task flow definition did not contain any activities.

Action: Add activities to the task flow definition.
Level: 2

Type: ERROR

Impact: Compliance

ADFC-02020: Cannot find default activity ''{0}'' in task flow definition ''{1}''.

Cause: The ADF Controller was unable to find a default activity in the task flow definition.

Action: Add a default activity.
Level: 2

Type: ERROR

Impact: Compliance

ADFC-02021: Customization of the documents that appear multiple times on the classpath is not supported. Document name: ''{0}''.

Cause: A document appears multiple times on the classpath.

Action: Remove multiple documents.
Level: 2

Type: ERROR

Impact: Compliance

ADFC-02022: Either 'parent-outcome' or 'root-outcome' has to be specified.

Cause: An attempt was made to parse a parent action activity with neither 'parent-outcome' and nor 'root-outcome' specified.

Action: Correct the value.
Level: 2

Type: ERROR

Impact: Browser

ADFC-04000: The value of PagePhaseListener cannot be null.

Cause: An attempt was made to use a PagePhaseListener with a null value.

Action: Correct the value.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-04001: The value of a listener ID string cannot be null or empty.

Cause: An attempt was made to identify a PagePhaseListener using a null listener ID.

Action: Use a nonempty string for the listener ID.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-04002: A PagePhaseListener with the listener ID of ''{0}'' already exists.

Cause: Each PagePhaseListener should be registered with a unique listener ID.

Action: Use a listener ID that does not already exist.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-04003: The PagePhaseListener of type ''{0}'' with listener ID of ''{1}'' cannot be registered because it is part of the internal API.

Cause: The ADF Controller was unable to register an internal PagePhaseListener using the public API.

Action: Use a PagePhaseListener that is not internal.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-04004: The value 'any_public_listener' is not allowed.

Cause: The value 'any_public_listener' was part of the afterSet or beforeSet parameter.

Action: Do not use 'any_public_listener' as the listener ID for beforeSet or afterSet.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-04005: The PagePhaseListener with ID ''{0}'' is internal and cannot be removed.

Cause: A failed attempt was made to remove an internal PagePhaseListener. This operation is not supported.

Action: Ensure that a PagePhaseListener is public, not internal, before attempting to remove it.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-04006: The value of LifecycleContext cannot be null.

Cause: An attempt was made to create a PagePhaseEvent with a null LifecycleContext.

Action: Correct the value.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-04007: The FacesPageLifecycleContext does not exist yet.

Cause: An attempt was made to retrieve the FacesPageLifecycleContext before it was created.

Action: Wait until the RestoreView phase of the JavaServer Faces lifecycle to retrieve the FacesPageLifecycleContext.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-04008: The BindingContext on the session is null.

Cause: The BindingContext retreived from the session was null.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-06000: The ADF Controller caught exception '{0}' while performing control flow routing. See the stack trace for details.

Cause: An unhandled exception occurred while the ADF Controller was executing the application's control flow.

Action: See the associated exception. Verify that the navigation rules are correctly specified. Verify that the correct outcome was generated to trigger routing.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-06001: TaskFlowId ''{0}'' is invalid.

Cause: An attempt was made to construct a TaskFlowId using an invalid string.

Action: Correct the value.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-06002: unhandled exception

Cause: The ADF Controller encountered an exception. Either no exception handler activity was defined or the ADF Controller and task flow were not configured to catch this exception.

Action: See the associated exception. Verify that the exception handler activity is correctly defined. Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-06003: TaskFlowId for a child view port must be specified.

Cause: An attempt was made to create a child view port using a null value for TaskFlowId.

Action: Correct the value.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-06004: Invalid transport ''{0}'' used. Task flows require ''{1}''.

Cause: An attempt was made to access a task flow without using the required transport.

Action: Use the appropriate transport. Contact the system administrator.
Level: 2

Type: ERROR

Impact: Security

ADFC-06005: The ADF Controller is unable to invoke URL parameter validator.

Cause: A view activity defines one or more parameter validators. Invoking the parameter validator failed.

Action: See the associated exception. Verify that the metadata refers to the correct class and method.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-06006: The ADF Controller is unable to invoke application method.

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-06012: Return task flow ID ''{0}'' is invalid.

Cause: The task flow ID being returned from did not match the ID of the task flow that was called.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-06013: The ADF Controller is unable to encode bookmark parameter ''{0}''.

Cause: The ADF Controller was unable to encode a bookmark parameter.

Action: See the associated exception.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-06014: An exception 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 mamanged 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.

Cause: A null window ID value was detected.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-12011: Window ID ''{0}'' is invalid.

Cause: A window ID was submitted that was not a valid window ID generated during the current HTTP session.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-12012: The request has an invalid state ID, and the session timed out.

Cause: The request contained a state instance ID, but the session was created during the current request.

Action: Return to the start page of the application.
Level: 2

Type: ERROR

Impact: Session

ADFC-12013: Controller state has not been initialized for the current request.

Cause: Controller request initialization has not been performed on the current request.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Session

ADFC-12014: Attempted access to an object that has already been released.

Cause: Attempted access to an object that has already been released.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Session

ADFC-12015: Null backingBeanScope ID.

Cause: Null backingBeanScope ID detected.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Session

ADFC-12016: Attempt to add the ADF Controller state to URL failed.

Cause: Attempt to add the ADF Controller state to URL failed.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Session

ADFC-12017: A non-ADF scope was specifed is a place where only an ADF scope is permitted.

Cause: A non-ADF scope was specifed is a place where only an ADF scope is permitted.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Session

ADFC-12018: A null ADF controller state was encountered.

Cause: The ADF controller state was found to be null when it should not be.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Session

ADFC-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-14006: Client ID ''{0}'' already exists.

Cause: Attempt to create child view port with a client ID that's already in use.

Action: Circular references to regions are not supported. Remove the region from the page.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14007: Display name ''{0}'' must evaluate to java.lang.String.

Cause: An EL expression for the display-name property must evaluate to a java.lang.String.

Action: Fix the EL expression.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14008: Task flow call activity cannot invoke remote task flow inside a region.

Cause: An attempt was made to invoke a remote task flow from inside a region.

Action: Fix the application.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14009: No RegionData stack was found was found while executing pop operation.

Cause: The RegionStack did not exist or was empty when attempting a pop operations, possibly the results of a pop without a push.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14010: Attempt to suspend a task flow context that's already suspended.

Cause: Attempt to suspend a task flow context that's already suspended.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14011: Attempt to resume a task flow context that has not been suspended.

Cause: Attempt to resume a task flow context that has not been suspended.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14012: Attempt to set the request's submitted view ID on a region's view port.

Cause: Attempt to set the request's submitted view ID on a region's view port.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14013: Task flow binding 'active' attribute is not a boolean value, binding=''{0}'', expression=''{1}''.

Cause: The 'active' attribute of a task flow binding did not evaluate to a boolean value.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14014: Task flow binding 'active' attribute evaluated to null, binding=''{0}''.

Cause: The 'active' attribute of a task flow binding evaluated to null.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14015: Task flow binding 'active' attribute was not specified, binding=''{0}''.

Cause: The 'active' attribute must be specified when activation="conditional" is used.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14016: Unknown value for task flow binding attribute 'activation', binding=''{0}'', value=''{1}''.

Cause: An unknown value for the task flow binding attribute 'activation' was encountered.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

5 ADFDI-00100 to ADFDI-55516

ADFDI-00100: Unable to send a request for BindingContext: a DIRemoteServlet call is already in progress.

Cause: A request to DIRemoteServlet was attempted while another one is already in progress.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00101: unexpected value found in attribute metadata: {0}

Cause: The XML response returned from the DIRemoteServlet is invalid.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00103: Unable to locate start element: BindingContainer in response stream.

Cause: The XML response returned from the DIRemoteServlet is invalid.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00105: invalid child element <{0}> encountered within <{1}> element

Cause: The XML response returned from the DIRemoteServlet is invalid.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00106: missing end element: </{0}>

Cause: The XML response returned from the DIRemoteServlet is invalid.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00107: row limit exceeded

Cause: Too many rows exist in result set.

Action: Refine your query in order to reduce the number of matching rows.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00108: user session required

Cause: A valid user session is required to communicate with server.

Action: Log in to server and retry request.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00109: invalid GetResourceBundle response

Cause: The XML response returned from the DIRemoteServlet is invalid.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00110: unable to locate element {0} or parse its contents

Cause: The XML response returned from the DIRemoteServlet is invalid.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00111: unable to create request object

Cause: Unable to establish a connection to the DIRemoteServlet.

Action: Verify that the DIRemoteServlet URL is specified properly and retry request. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00112: unable to create XmlTextWriter

Cause: An unexpected error occurred while sending a request to the DIRemoteServlet.

Action: Retry your request. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00113: unable to get request stream

Cause: An unexpected error occurred while sending a request to the DIRemoteServlet.

Action: Retry your request. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00114: The DIRemoteServlet returned an unrecognized value for element {0}, attribute {1}: {2}.

Cause: The XML response returned from the DIRemoteServlet is invalid.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00115: The DIRemoteServlet returned an unexpected element type in the response XML: {0}

Cause: The XML response returned from the DIRemoteServlet is invalid.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00116: The DIRemoteServlet returned invalid XML: unexpected end of response.

Cause: An unexpected error occurred while reading the DIRemoteServlet response.

Action: Retry your request. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00117: An unexpected error occurred while reading the server response. Consult the logs for more information.

Cause: An unexpected error occurred while reading the DIRemoteServlet response.

Action: Retry your request. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00118: The DIRemoteServlet returned an error. A subsequent error occurred reading the error details from the response.

Cause: An unexpected error occurred while reading the DIRemoteServlet response.

Action: Retry your request. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00119: The DIRemoteServlet returned an error. A subsequent error occurred reading the error details from the response: unexpected element type: {0}.

Cause: The XML response returned from the DIRemoteServlet is invalid.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00120: The DIRemoteServlet returned an error. A subsequent error occurred reading the error details from the response: unexpected element name: {0}.

Cause: The XML response returned from the DIRemoteServlet is invalid.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00121: The expected XML element {0} was not found. Instead, the element {1} of type {2} was found.

Cause: The XML response returned from the DIRemoteServlet is invalid.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00122: An unexpected XML element name was encountered (expected: {0}, found {1}).

Cause: The XML response returned from the DIRemoteServlet is invalid.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00123: The expected XML end element {0} was not found. Instead, the element {1} of type {2} was found.

Cause: The XML response returned from the DIRemoteServlet is invalid.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00124: The expected XML end element {0} was not found. Instead, the element {1} was found.

Cause: The XML response returned from the DIRemoteServlet is invalid.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00125: The expected XML attribute {0} for element {1} was not found.

Cause: The XML response returned from the DIRemoteServlet is invalid.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00126: An attempt was made to set the row position for control binding {0} to {1}. Iterator has {2} rows.

Cause: Row index out of bounds.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00127: A version mismatch was detected for {0}. Version {1} was found, version {2} was expected.

Cause: The servlet version did not match the required level for the client.

Action: Upgrade the client and/or server so that compatible versions are in use.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-00128: unable to locate the column metadata for column with ID: {0}

Cause: The binding container metadata did not match the data returned from the server.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00129: invalid Encode URL response

Cause: The response received from the server for this request could not be processed. It may be caused by an exception in the server component.

Action: Retry your request. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00130: The size of requested resource bundle ({1}) exceeds the maximum allowable limit: {0} bytes.

Cause: The size of the resource bundle exceeded the supported size.

Action: Reduce the size of the resource bundle.
Level: 1

Type: WARNING

Impact: Files

ADFDI-00131: The connection attempt has been canceled.

Cause: The attempt to connect to the server was canceled.

Action: Retry the current action.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00132: unable to execute Wininet method {0}; error code: {1}

Cause: The Wininet library was unable to provide the requested service.

Action: Retry the current action, confirm connectivity, and/or consult the client logs for more information.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-00133: The user session has changed.

Cause: The user session timed out or was otherwise invalid.

Action: Retry the current action, re-login, or re-establish a valid user session.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00134: An attempt to connect to the web application has failed.

Cause: The web application may not have been running or may not have been configured to allow client connections.

Action: Confirm that the web application is accepting connections from a web browser.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00135: The server-side list is not positioned as expected.

Cause: The server-side list was not positioned as expected.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00136: A server side certificate could not be verified. Open Internet Explorer, visit the site that your workbook is attempting to reach, install the certificate, and retry the current action.

Cause: A server side certificate could not be verified.

Action: Open Internet Explorer, visit the site that your workbook is attempting to reach, install the certificate and retry the current action.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00137: The client and server versions are not compatible. Contact the system administrator and ensure that the client and server versions match.

Cause: The version of the server was not compatible with the version of the client.

Action: Contact the system administrator and ensure that the client and server versions match.
Level: 1

Type: ERROR

Impact: Deployment

ADFDI-00500: unable to execute Wininet method {0}; error code: {1}

Cause: The Wininet library was unable to provide the requested service.

Action: Retry the current action, confirm connectivity, and/or consult the client logs for more information.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-00501: An unexpected status: {0} ({1}) was returned from the server while requesting the URL: {2}

Cause: The client was unable to complete its request to the server for the given URL. The server returned an unexpected status code.

Action: Retry the current action, confirm connectivity, and/or consult the client logs for more information.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-00502: The client was unable to establish an unauthenticated session with the web application.

Cause: An unexpected problem prevented the client from establishing a valid, unauthenticated session with the web application.

Action: Retry the current action, confirm the authentication configuration and connectivity, and/or consult the client logs and exception details for more information.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-00505: Unexpected exception

Cause: There was an unexpected error during the current operation.

Action: Review configuration and installation. Then, retry the operation.
Level: 1

Type: ERROR

Impact: Other

ADFDI-01001: A validation error occurred for metadata property {0}. Detail: {1}

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

Action: Correct the specified property.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-01002: A validation warning occurred for metadata property {0}. Detail: {1}

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

Action: Correct the specified property.
Level: 1

Type: WARNING

Impact: Configuration

ADFDI-05000: Unexpected components exist at origin, {0}.

Cause: More than one component was found at the specified origin.

Action: Delete the unwanted components.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-05001: An unsupported binding type {0} exists in the page definition {1}.

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

Action: Remove the unsupported binding from the page definition file.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-05002: unable to locate page definition element in {0}

Cause: The root element was missing from the page definition file.

Action: Ensure that the page definition file is well formed.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-05006: A component already exists at origin {0}.

Cause: An attempt was made to insert or move a component to a cell that is already in use as the origin of another component.

Action: Choose a different destination cell for the insertion or move operation.
Level: 1

Type: WARNING

Impact: Programmatic

ADFDI-05010: unable to move the component to new position; cannot parse position {0}

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

Action: Specify a valid cell reference. For example, use $B$3 for the cell in the second column and third row.
Level: 1

Type: WARNING

Impact: Programmatic

ADFDI-05011: unable to move the component to new position; a component already exists at that position: {0}

Cause: An attempt was made to move a component to a cell that is already in use as the origin of another component.

Action: Choose a different destination cell for the move operation.
Level: 1

Type: WARNING

Impact: Programmatic

ADFDI-05012: Unable to locate or open the page definition: {0}. Control bindings are not available for this worksheet. File: {1}.

Cause: An attempt was made to load the file specified. Either some portion of the file path was invalid, the file did not exist, or the user had insufficient permissions to open the file.

Action: Ensure that the relevant properties are configured correctly.
Level: 1

Type: WARNING

Impact: Programmatic

ADFDI-05013: There is no page definition selected. Control bindings are not available for this worksheet.

Cause: User canceled the operation of selecting a page definition.

Action: Select a valid page definition to associate with the current worksheet.
Level: 1

Type: WARNING

Impact: Programmatic

ADFDI-05015: An error occurred while updating the client registry

Cause: The attempt to update the client registry was unsuccessful.

Action: Check client log file for more details.
Level: 1

Type: ERROR

Impact: Session

ADFDI-05016: The workbook, {0}, is missing one or more required settings: ApplicationHomeFolder, WebPagesFolder.

Cause: The specified workbook was missing one or more settings required for publishing.

Action: Provide valid values for all settings required for publishing.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-05017: The value '{0}' is not valid for the property {1}.

Cause: The property value entered was not valid.

Action: Enter a valid property value.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-05018: Unable to locate or open the page definition: {0}. Control bindings are not available for this worksheet.

Cause: The specified page definition could not be located or opened.

Action: Check the spelling of the page defintion usage id and refresh the bindings list.
Level: 1

Type: WARNING

Impact: Configuration

ADFDI-05019: The component cannot be placed at the requested location since it would overlap with one or more other components.

Cause: An attempt was made to place a component in a position that would overlap with other components.

Action: Choose a different location that will not overlap.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-05020: Unexpected components exist at cell, {0}.

Cause: More than one component was found at the specified cell.

Action: Delete the unwanted components.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-05500: error restoring server data context

Cause: A failed attempt was made to re-establish the server state for a new user session.

Action: Check the configuration of the workbook to ensure that the attributes and actions used to reestablish the server state are defined correctly. Check the server to determine whether data has been deleted.
Level: 1

Type: ERROR

Impact: Data

ADFDI-05501: value does not match for attribute {0}

Cause: The value in the cache was not equal to the attribute value.

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

Type: ERROR

Impact: Data

ADFDI-05502: unable to locate control binding {0} in binding container {1}

Cause: A failed attempt was made to locate the binding information of a UI component.

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

Type: ERROR

Impact: Programmatic

ADFDI-05503: An incorrect binding type, {0}, exists for the control binding {1} in the binding container {2}.

Cause: The binding type of the component differed from the binding type defined in the binding container.

Action: Check the configuration of the workbook and retry the operation. Ensure that the control binding type is defined correctly.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-05504: unable to find attribute: {0}

Cause: A failed attempt was made to find an attribute in the data context cache.

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

Type: ERROR

Impact: Programmatic

ADFDI-05505: unable to find action: {0}

Cause: A failed attempt was made to find a restore data context action in the data context cache.

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

Type: ERROR

Impact: Programmatic

ADFDI-05506: unable to find list control binding: {0}

Cause: A failed attempt was made to locate the list control binding.

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

Type: ERROR

Impact: Programmatic

ADFDI-05507: invalid list control binding: {0}

Cause: The binding type of the list control was not valid.

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

Type: ERROR

Impact: Programmatic

ADFDI-05509: unable to find component: {0}

Cause: A failed attempt was made to find the binding of the component.

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

Type: ERROR

Impact: Programmatic

ADFDI-05510: unable to insert column; column out-of-bounds

Cause: A failed attempt was made to insert a dynamic column into the Table because the column was not within the named range.

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

Type: ERROR

Impact: Programmatic

ADFDI-05511: unable to remove column; column out-of-bounds

Cause: A failed attempt was made to delete a dynamic column into the Table because the column was not within the named range.

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

Type: ERROR

Impact: Programmatic

ADFDI-05513: cannot find record

Cause: A failed attempt was made to locate the record flagged for deletion.

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

Type: ERROR

Impact: Data

ADFDI-05517: unable to find control {0}

Cause: A failed attempt was made to locate the control in the binding container.

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

Type: ERROR

Impact: Programmatic

ADFDI-05518: unable to set expression value for read-only expression

Cause: A failed attempt was made to set the value for a read-only expression.

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

Type: ERROR

Impact: Programmatic

ADFDI-05519: unable to find component method, {0}, to invoke.

Cause: A failed attempt was made to invoke the specified component method.

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

Type: ERROR

Impact: Programmatic

ADFDI-05524: unable to position on current table row

Cause: A failed attempt was made to update the row position in a table for the purpose of invoking an action set on the row.

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

Type: ERROR

Impact: Programmatic

ADFDI-05529: unable to load binding container metadata

Cause: A failed attempt was made to load the metadata that defines the binding container.

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

Type: ERROR

Impact: Data

ADFDI-05530: unable to initialize worksheet: {0}

Cause: A failed attempt was made to initialize a worksheet.

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

Type: ERROR

Impact: Session

ADFDI-05531: one or more rows could not be uploaded

Cause: A failed attempt was made to upload data to the web application.

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

Type: ERROR

Impact: Session

ADFDI-05535: one or more flagged rows could not be deleted

Cause: A failed attempt was made to delete flagged rows.

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

Type: ERROR

Impact: Session

ADFDI-05537: The integrity of the workbook integration could not be determined. This workbook cannot be used safely. The integration will now terminate.

Cause: The server was unable to read the client registry.

Action: Verify/correct the client registry in the web application.
Level: 1

Type: ERROR

Impact: Session

ADFDI-05538: The workbook integration has been altered after publishing. It can no longer be used safely. The integration will now terminate.

Cause: The tampering check has determined that the workbook has been altered.

Action: Obtain a fresh, unaltered copy of the published workbbook.
Level: 1

Type: ERROR

Impact: Session

ADFDI-05553: An invalid character was found in the server XML response. Verify the data from the data source and avoid any invalid character or binary data such as image be sent in the response.

Cause: An attempt was made to read an invalid character in the XML data sent by the server.

Action: Verify the data from the data source and remove the invalid character from the data.
Level: 1

Type: ERROR

Impact: Session

ADFDI-05554: An incorrect version of the UI metadata schema is used in the workbook. Convert the UI metadata to the current version.

Cause: The workbook contains UI metadata from an obsolete schema version.

Action: Convert the UI metadata to the current version.
Level: 1

Type: WARNING

Impact: Session

ADFDI-05555: Required property {0} missing for component {1}.

Cause: Required component property not defined.

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

Type: ERROR

Impact: Programmatic

ADFDI-05557: inserted row data must first be refreshed from server

Cause: The row was successfully inserted to the database, but the row data has not been updated in the worksheet.

Action: First perform a Download or DownloadFlaggedRows operation, then retry the DeleteFlaggedRows operation.
Level: 1

Type: ERROR

Impact: Data

ADFDI-05558: CacheDataContext must specify an action and at least one attribute.

Cause: The metadata for this worksheet contains one or more invalid CacheDataContext definitions.

Action: Review and resolve CacheDataContext configuration issues and retry.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-05559: Row cache data is invalid.

Cause: The row data cached for an ADF Table component is not valid.

Action: Re-download ADF Table data.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-05560: Download action ignored for insert-only table, {0}.

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

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

Type: WARNING

Impact: Programmatic

ADFDI-05561: Failed to read multi-sync response as expected.

Cause: The number of multi-sync responses did not match the number of multi-sync requests.

Action: Check your configuration and try the operation again.
Level: 1

Type: WARNING

Impact: Programmatic

ADFDI-05562: Dependent list component has been misconfigured.

Cause: The developer has incorrectly configured a list component that depends on another list component.

Action: Enable verbose logging on the client and review log for additional details on the specific configuration issue.
Level: 1

Type: WARNING

Impact: Programmatic

ADFDI-05563: Restore Server Data Context Cache is corrupted

Cause: The hidden cache of data was not in the expected format

Action: Obtain a new version of the workbook or Clear All Data
Level: 1

Type: WARNING

Impact: Programmatic

ADFDI-05564: The list binding "{0}" has {1} values. Only the first {2} items are stored in the cache.

Cause: The number of items in the list exceeded the allowable limit.

Action: Reduce the number of items in the list. Or, configure the workbook to use a web page dialog for selecting an item from a large list of values.
Level: 1

Type: WARNING

Impact: Programmatic

ADFDI-05565: unable to retrieve values for the list binding "{0}"

Cause: A failed attempt was made to retrieve list values from the server.

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

Type: ERROR

Impact: Programmatic

ADFDI-05566: unable to retrieve values for the list binding "{0}", or for one or more of its dependent lists

Cause: A failed attempt was made to retrieve list values from the server.

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

Type: ERROR

Impact: Programmatic

ADFDI-05567: Unable to restore server state. This condition is an unrecoverable error. You will now be logged out of your current session.

Cause: The attempt to restore server state failed.

Action: Log in to the application and retry the operation. Examine the server logs for additional information.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-05568: Failed to initialize cache for List binding: {0} in component/column: {1}, owned by type: {2} (in table: {3}).

Cause: A failed attempt was made to retrieve and cache list values from the server.

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

Type: WARNING

Impact: Programmatic

ADFDI-05569: Unable to report table status: status column is not visible.

Cause: The table was configured so that the Status column is not visible.

Action: Configure the table so that the Status column is visible.
Level: 1

Type: WARNING

Impact: Configuration

ADFDI-05570: The Automation API encountered an unexpected condition. Details: {0}

Cause: The Automation API encountered an unexpected condition.

Action: Check the configuration of the workbook and/or the automation scripts.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-05571: Failed to find resource. Alias: {0} Key: {1}

Cause: The specified alias-key combination could not be located.

Action: Check the configuration of the workbook and/or resource files.
Level: 1

Type: WARNING

Impact: Configuration

ADFDI-05572: Failed to find resource bundle. Alias: {0}

Cause: The specified resource bundle could not be located.

Action: Check the configuration of the workbook and/or resource files.
Level: 1

Type: WARNING

Impact: Configuration

ADFDI-05573: Unable to perform the requested action because the worksheet protection could not be changed.

Cause: A failed attempt was made to temporarily remove protection from the worksheet.

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

Type: ERROR

Impact: Configuration

ADFDI-05574: You have modified cells in the key column. This operation can lead to data corruption. Your change will now be reverted.

Cause: An attempt was made to modify cells in the key column of an ADF Table.

Action: Do not modify cells in the key column.
Level: 1

Type: WARNING

Impact: Data

ADFDI-05575: Unable to revert the changes to cells in the key column. The affected table(s) should be considered corrupt. You should revert to a previous version.

Cause: A failed attempt was made to revert changes to the key column.

Action: Obtain a fresh copy of the integrated workbook and re-attempt the operation without modifying cells in the key column.
Level: 1

Type: ERROR

Impact: Other

ADFDI-05576: The action, {0}, cannot be invoked in this context.

Cause: An attempt was made to invoke a row-level action in a non-row-level action set.

Action: Remove this action from this action set.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-05577: Failed to retrieve table row data from the server.

Cause: A failed attempt was made to retrieve table row data from the server.

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

Type: ERROR

Impact: Data

ADFDI-05578: The reserved table named range, '{0}', cannot be not found or is invalid.

Cause: A failed attempt was made to access the reserved named range for the table component.

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

Type: ERROR

Impact: Configuration

ADFDI-05579: An unexpected exception occurred while performing an operation on the table identified by: {0}. Close the workbook without saving it and retry the operation.

Cause: A failed attempt was made to execute a table operation.

Action: Close the workbook without saving it and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-05580: unable to bind expression part: {0}

Cause: A failed attempt was made to bind the expression part.

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

Type: ERROR

Impact: Configuration

ADFDI-05581: Unable to write component data into worksheet: {0}

Cause: A failed attempt was made to write component data to the worksheet.

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

Type: ERROR

Impact: Programmatic

ADFDI-05582: Unable to download flagged rows because the table structure has changed.

Cause: The DownloadFlaggedRows action was invoked on a table and the column structure is different from when rows were last downloaded.

Action: Check the configuration of the worksheet.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-05584: Unable to convert: '{0}' to the target time zone. Close the workbook without saving it and retry the operation.

Cause: An unexpected failure has occurred while converting date time values from one time zone to another.

Action: Close the workbook without saving it and retry the operation.
Level: 1

Type: ERROR

Impact: Data

ADFDI-05585: The {0} element in the dialog page {1} should be a <span> element; the type <{2}> is not supported.

Cause: The html tag used for the reserved element in the dialog page was not supported.

Action: Contact the developer of this dialog page to use <span> tag for the reserved element
Level: 1

Type: Warning

Impact: Configuration

ADFDI-05586: Fail to hook event handler to the {0} element due to {1}. Closing the dialog with client side scripts is disabled.

Cause: Unable to hook an event handler to the reserved html element in the dialog page.

Action: Close the dialog manually if it is not closed automatically. The developer of this dialog page should avoid using client side scripts to change the value of the reserved element.
Level: 1

Type: Warning

Impact: Other

ADFDI-05587: The client and server versions do not match. Using this version of the client may result in unexpected behavior or errors.

Cause: The client and server versions did not match.

Action: Install a client that matches the server version.
Level: 1

Type: Warning

Impact: Upgrade

ADFDI-05588: The number of resource bundles ({1}) exceeds the supported limit of {0}.

Cause: The number of resource bundles exceeded the supported limit.

Action: Reduce the number of resource bundles in this workbook.
Level: 1

Type: WARNING

Impact: Files

ADFDI-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-07000: unable to open Excel file

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

Action: Ensure that the necessary file permissions have been applied, that the file exists, is not in use, and that it is a valid workbook file.
Level: 1

Type: ERROR

Impact: Files

ADFDI-07001: unable to find Excel file

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 ADF Desktop Integration

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 ADF Desktop Integration

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 ADF Desktop Integration installer

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 ADF Desktop Integration 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-07507: given buffer size is incorrect; given: {0}

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

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

Type: ERROR

Impact: Data

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

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

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

Type: ERROR

Impact: Data

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

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

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

Type: ERROR

Impact: Data

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

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

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

Type: ERROR

Impact: Data

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

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

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

Type: ERROR

Impact: Data

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

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

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

Type: ERROR

Impact: Session

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

Cause: Internal buffer size mismatch detected.

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

Type: ERROR

Impact: Data

ADFDI-07516: A worksheet version mismatch was detected in worksheet {0}. Version {1} was found, version {2} was expected.

Cause: The workbook's internal format may be corrupted, or incompatible versions of the framework are in use.

Action: Ensure that compatible versions of the framework are in use; upgrade the workbook and framework.
Level: 1

Type: ERROR

Impact: Data

ADFDI-07517: There are no more rows available in the metadata worksheet {0}.

Cause: The maximum capacity for storing metadata has been reached, or the workbook's internal format may be corrupted.

Action: Remove some components from the workbook in order to free up space.
Level: 1

Type: ERROR

Impact: Data

ADFDI-07518: The workbook has no metadata.

Cause: The workbook may be corrupted or the metadata has been erased manually.

Action: Publish the workbook and try again or contact administrator.
Level: 1

Type: ERROR

Impact: Data

ADFDI-07520: Unable to evaluate the expression '{0}' in '{1}'. Detail: {2}

Cause: A failed attempt was made to evaluate an invalid expression.

Action: Verify and correct the expression.
Level: 1

Type: WARNING

Impact: Programmatic

ADFDI-07521: Unable to evaluate the Excel formula '{0}' in '{1}'. Detail: {2}

Cause: A failed attempt was made to evaluate an invalid Excel formula.

Action: Verify and correct the Excel formula.
Level: 1

Type: WARNING

Impact: Programmatic

ADFDI-07522: Unable to execute the command '{0}' while a cell is in edit mode. Accept or cancel the changes to the current cell and then retry the command.

Cause: An attempt was made to invoke a menu or toolbar command while a cell is open in editing mode.

Action: Accept or cancel the changes to the current cell and then retry the command.
Level: 1

Type: WARNING

Impact: Programmatic

ADFDI-07527: An unexpected exception has occurred. The Workbook Designer cannot initialize. The design-time session will now abort.

Cause: A failed attempt was made to initialize the workbook for Design Time mode.

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

Type: ERROR

Impact: Session

ADFDI-07528: An unexpected exception has occurred. The UI Controller cannot initialize. The runtime session will now abort.

Cause: A failed attempt was made to initialize the workbook for Run Time mode.

Action: Check the configuration of the workbook and retry the operation. Ensure that the web application is running and accepting requests.
Level: 1

Type: ERROR

Impact: Session

ADFDI-07529: An unexpected exception has occurred. The workbook cannot initialize and will now abort.

Cause: A failed attempt was made to initialize the workbook for an unknown mode.

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

Type: ERROR

Impact: Session

ADFDI-07530: An unexpected exception has occurred. The workbook cannot switch to test mode.

Cause: A failed attempt was made to switch from Design Time mode to Test mode.

Action: Check the configuration of the workbook and retry the operation. Ensure that the web application is running and accepting requests.
Level: 1

Type: ERROR

Impact: Session

ADFDI-07532: The workbook {0} cannot be used with this edition of {1}.

Cause: An attempt was made to open a design-time or test mode workbook using the runtime edition.

Action: Use only published workbooks with the runtime edition. Install the designer edition for other workbook types.
Level: 1

Type: ERROR

Impact: Files

ADFDI-07533: Unable to load add-in {0} because multiple editions are installed.

Cause: Multiple editions of the add-in were installed.

Action: Remove one of the editions.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-07537: Ignored exception thrown by {0} event subscriber

Cause: An event subscriber threw an exception.

Action: Review and correct the event subscriber implementation.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-07538: The Automation API encountered an unexpected condition. Details: {0}

Cause: The Automation API encountered an unexpected condition.

Action: Check the configuration of the workbook and/or the automation scripts.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-07539: The workbook '{0}' was created or altered by version '{1}' of {2} and is not compatible with the current version ({3}).

Cause: The workbook was created or altered by a newer version of the product and is not compatible with the current version.

Action: Use a newer version of the Oracle ADF Desktop Integration client.
Level: 1

Type: ERROR

Impact: Upgrade

ADFDI-07540: The workbook '{0}' was created or altered by version '{1}' of {2} and is not compatible with the current version ({3}). Do you wish to use it anyway?

Cause: The workbook was created or altered by a newer version of the product and is not compatible with the current version.

Action: Use a newer version of the Oracle ADF Desktop Integration client, or continue with the current client. You may encounter unexpected errors.
Level: 1

Type: WARNING

Impact: Upgrade

ADFDI-08200: A valid {0} property must be chosen before editing this property.

Cause: An attempt was made to edit the Web Pages Folder or Page Definition Folders properties before specifying a valid Web Application Home folder.

Action: Specify a valid Web Application Home folder property and retry the operation.
Level: 1

Type: WARNING

Impact: Configuration

ADFDI-08201: A valid 'Web Pages' folder must be chosen. Do you want to do that now?

Cause: An attempt was made to choose a web page for an ActionSet's Dialog.Page property before a valid Web Pages Folder property was specified.

Action: Specify a valid Web Pages Folder property and retry the operation.
Level: 1

Type: WARNING

Impact: Configuration

ADFDI-08202: A valid path that is relative to the 'ApplicationHomeFolder' property must be chosen.

Cause: An attempt was made to choose a folder that is not a valid subfolder of the parent folder property.

Action: If necessary, change the 'ApplicationHomeFolder' property to a different value, and then choose a valid subfolder for this property.
Level: 1

Type: WARNING

Impact: Configuration

ADFDI-08203: A valid, absolute path name must be entered for this property.

Cause: An attempt was made to choose a folder for the Application Home Folder property that is not a valid, absolute folder.

Action: Navigate to the folder in which your web application resides.
Level: 1

Type: WARNING

Impact: Configuration

ADFDI-50001: Resource bundle not found. bundle: {0}

Cause: Unable to load the desired resource bundle class.

Action: Review the server logs for additional detail on the underlying cause.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-50002: Resource key not found. bundle

Cause: Unable to find the desired key in the bundle.

Action: Review the server logs for additional detail on the underlying cause.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-55000: An unexpected exception occurred on the server. Consult the server logs for more detail.

Cause: An unexpected condition arose while handling the desktop integration request.

Action: Review the server logs for additional detail on the underlying cause.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55001: XML element {0} missing required attribute {1}

Cause: Invalid request XML was received.

Action: Review the server logs to ensure that only supported clients are accessing the ADFdi Remote Servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55002: The object, {0}, is not available.

Cause: An expected object was not found or was unavailable.

Action: Ensure that both the client and server metadata are configured correctly.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-55003: The object, {0}, is not available. Name: {1}

Cause: An expected object was not found or was unavailable.

Action: Ensure that both the client and server metadata has been configured correctly.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-55004: invalid GetResourceBundle request XML

Cause: An invalid request was received.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55005: invalid SyncModel request XML

Cause: An invalid request was received.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55006: unexpected value specified for XML element {0}

Cause: An invalid request was received.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55007: invalid request XML

Cause: An invalid request was received.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55008: invalid request method: {0}

Cause: An invalid request was received.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55009: user session unavailable

Cause: The user was not authenticated.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Session

ADFDI-55010: expected XML element {0}; current element is {1}

Cause: An invalid request was received.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55011: unexpected end-of-file in XML input stream

Cause: An invalid request was received.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55012: invalid XML element: {0}

Cause: An invalid request was received.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55013: expected XML reader state {0}; current state is {1}

Cause: An invalid request was received.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55014: invalid child XML element {1} within XML element {0}

Cause: The XML request sent by the client was invalid.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55017: The current row count exceeds the configured limit.

Cause: The maximum number of rows requested by the client was exceeded.

Action: Submit a new request that conforms to the limit.
Level: 1

Type: ERROR

Impact: Data

ADFDI-55018: exception occurred while reading an XML request

Cause: A malformed request was received.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55019: exception occurred while writing the XML response

Cause: Details about the underlying cause of the error are contained in the server logs.

Action: Review the server logs for details about additional steps to take.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55021: A version mismatch was detected for {0}. Version {1} was found, version {2} was expected.

Cause: The client version does not match the required level for the DIRemoteServlet.

Action: Upgrade the client and/or server so that compatible versions are in use.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55022: invalid SessionStatus request XML

Cause: An invalid request was received.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55023: invalid MultiSyncModel request XML

Cause: An invalid request was received.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55025: The control binding definition for item {0} is incorrect or incompatible. {1}

Cause: The control binding definition has been misconfigured, or an incompatible control binding has been encountered.

Action: Check the control binding definition and ensure that only supported control bindings are used.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55026: invalid TamperCheck request XML

Cause: An invalid request was received.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55027: invalid EncodeURL request XML

Cause: An invalid request was received.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55028: unexpected value specified for XML element {0}: {1}

Cause: An invalid request was received.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55030: Cannot find the client registry file: {0}

Cause: System could not find the client registry file in the web-inf location.

Action: Contact administrator
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55031: An error occurred while trying to read client registry file

Cause: While trying to read the client registry file, an I/O error occurred.

Action: Check logs for details of I/O error and address root case to enable file access.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55032: Unable to set attribute {0} (row object unavailable: {1})

Cause: Client attempted to set an attribute value when no server row is available.

Action: Refresh the client data and retry the operation.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55033: {0}: cannot convert the input value ({1}) to the expected data type ({2}).

Cause: The input values were not consistent with expected data type.

Action: Correct input values according to data type.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55034: Tamper check is disabled.

Cause: The servlet was configured to disable the tamper check feature.

Action: Adjust servlet initialization parameters as desired.
Level: 1

Type: WARNING

Impact: Configuration

ADFDI-55035: Tamper check did not succeed. Result: {0}

Cause: Tamper check was unable to match the hashcode of the client to the expected value.

Action: Adjust the configuration of tamper check or obtain a new copy of the workbook.
Level: 1

Type: WARNING

Impact: Data

ADFDI-55036: Received a request with unexpected content type: {0}

Cause: A request with an unexpected content type was received.

Action: Use only supported content types.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55037: Tamper check is configured to allow missing entries.

Cause: The tamper check feature was configured to allow missing entries.

Action: Adjust servlet initialization parameters as desired.
Level: 1

Type: WARNING

Impact: Configuration

ADFDI-55038: The region binding includes an unsupported control type: {0}

Cause: The page definition was configured to use an unsupported control type.

Action: Remove the unsupported type.
Level: 1

Type: WARNING

Impact: Configuration

ADFDI-55039: Unexpected servlet failure

Cause: The servlet has failed due to an unexpected condition.

Action: Review the server logs for more information.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55040: Unable to read requested resource bundle: {0}

Cause: An attempt was made to load a resource bundle that was not available.

Action: Review the configuration to ensure that the resource bundle is available.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-55041: Aborting the commit action for a transaction.

Cause: The commit action was aborted for the transaction due to error in the binding container.

Action: Clear the error conditions and retry the operation.
Level: 1

Type: ERROR

Impact: Data

ADFDI-55042: Unable to set position for {0} with value {1}

Cause: A failed attempt was made to position a control binding by attribute value.

Action: Refresh the client data and retry the operation or review the server logs for more information.
Level: 1

Type: ERROR

Impact: Data

ADFDI-55043: Unable to locate parameter {0} for binding container {1}

Cause: A failed attempt was made to set a parameter.

Action: Review the configuration to ensure that the parameter is available.
Level: 1

Type: WARNING

Impact: Configuration

ADFDI-55044: user session has changed

Cause: The client user session timed out or was otherwise invalid.

Action: Establish a valid user session.
Level: 1

Type: ERROR

Impact: Session

ADFDI-55045: unable to set position to row {0}

Cause: A failed attempt was made to position a control binding by row index value.

Action: Refresh the client data and retry the operation or review the server logs for more information.
Level: 1

Type: ERROR

Impact: Data

ADFDI-55046: A value is required for {0}.

Cause: An attempt was made to set an empty value for a mandatory attribute.

Action: Provide a non-empty value for this property.
Level: 1

Type: ERROR

Impact: Data

ADFDI-55047: retry failed for batch request #{0}

Cause: A failed attempt was made to retry a successful batch request after restoring to datacontrol savepoint.

Action: Review the server logs for more details about the cause of the failure.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55502: The length of the source data, {0}, is greater than the size of the destination buffer, {1}.

Cause: Internal buffer size mismatch was detected.

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

Type: ERROR

Impact: Data

ADFDI-55510: unable to find expected workbook parameters start tag; found: {0}

Cause: The internal format of the workbook might be corrupted.

Action: Run the workbook admin tool on this workbook. Ensure that compatible versions of the client and server framework are in use.
Level: 1

Type: ERROR

Impact: Data

ADFDI-55511: unable to find expected workbook parameters end tag; found: {0}

Cause: The internal format of the workbook might be corrupted.

Action: Run the workbook admin tool on this workbook. Ensure that compatible versions of the client and server framework are in use.
Level: 1

Type: ERROR

Impact: Data

ADFDI-55512: The workbook parameters buffer size is incorrect: {0}.

Cause: The internal format of the workbook might be corrupted.

Action: Run the workbook admin tool on this workbook. Ensure that compatible versions of the client and server framework are in use.
Level: 1

Type: ERROR

Impact: Data

ADFDI-55513: The workbook parameters mode length is incorrect: {0}.

Cause: The internal format of the workbook might be corrupted.

Action: Run the workbook admin tool on this workbook. Ensure that compatible versions of the client and server framework are in use.
Level: 1

Type: ERROR

Impact: Data

ADFDI-55514: The workbook parameters application root length is incorrect: {0}.

Cause: The internal format of the workbook might be corrupted.

Action: Run the workbook admin tool on this workbook. Ensure that compatible versions of the client and server framework are in use.
Level: 1

Type: ERROR

Impact: Data

ADFDI-55515: The workbook parameters collection length is incorrect: {0}.

Cause: The internal format of the workbook might be corrupted.

Action: Run the workbook admin tool on this workbook. Ensure that compatible versions of the client and server framework are in use.
Level: 1

Type: ERROR

Impact: Session

ADFDI-55516: Unexpected filter failure

Cause: The filter has failed due to an unexpected condition.

Action: Review the server logs for more information.
Level: 1

Type: ERROR

Impact: Requests/Responses

6 ADFF_BIND-00001 to ADFF_BIND-00046

ADFF_BIND-00001: ADFv: Trouble getting the mutable document from MDS. {0}.

Cause: MDS repository may be configured incorrectly, or may have been corrupted.

Action: Check MDS repository configuration and clear repository.
Level: 2

Type: WARNING

Impact: Programmatic

ADFF_BIND-00002: ADFv: ADF JSF databinding support installed.

Cause: n/a.

Action: n/a.
Level: 2

Type: NOTIFICATION

Impact: Configuration

ADFF_BIND-00003: ADFv: ADF JSF databinding support for BC4J installed.

Cause: n/a.

Action: n/a.
Level: 2

Type: NOTIFICATION

Impact: Configuration

ADFF_BIND-00004: ADFv: Cannot convert "{0}" into Array. Updating of arrays not supported.

Cause: Error in application.

Action: Contact your application support person.
Level: 2

Type: ERROR

Impact: Programmatic

ADFF_BIND-00005: ADFv: closing } not found in expression: {0}.

Cause: Error in binding expression in application.

Action: Contact your application support person to correct binding expression.
Level: 2

Type: ERROR

Impact: Programmatic

ADFF_BIND-00006: ADFv: rowIterator is null.

Cause: Internal error.

Action: Contact your application support person.
Level: 2

Type: WARNING

Impact: Data

ADFF_BIND-00007: ADFv: Rowkey does not have any primary key attributes. Rowkey: {0}, table: {1}.

Cause: Application or data error.

Action: Contact your application support person to check for data corruption.
Level: 2

Type: ERROR

Impact: Programmatic

ADFF_BIND-00008: ADFv: No row found for rowKey: {0}.

Cause: Application or data error.

Action: Contact your application support person to check for data corruption.
Level: 2

Type: WARNING

Impact: Data

ADFF_BIND-00009: ADFv: Could not find selected item matching value {0} of type: {1} in the list-of-values.

Cause: Application or data error.

Action: Contact your application support person to ensure list data has not been corrupted.
Level: 2

Type: WARNING

Impact: Programmatic

ADFF_BIND-00010: ADFv: AttributeDef not found for property: {0}.

Cause: Application or binding metadata error.

Action: Contact your application support person to ensure binding metadata is correct.
Level: 2

Type: WARNING

Impact: Programmatic

ADFF_BIND-00011: ADFv: Property '{0}' not supported on AttributeHints.

Cause: Application or binding metadata error.

Action: Contact your application support person to ensure binding metadata is correct.
Level: 2

Type: WARNING

Impact: Programmatic

ADFF_BIND-00012: ADFv: Row is null for rowKey: {0}.

Cause: Application or data error.

Action: Contact your application support person to ensure data is correct.
Level: 2

Type: ERROR

Impact: Programmatic

ADFF_BIND-00013: ADFv: Row is null at absoluteIndex: {0} rangeStart: {1} rangeSize: {2} estimatedRowCount: {3}.

Cause: Application or data error.

Action: Contact your application support person to ensure data is correct.
Level: 2

Type: WARNING

Impact: Programmatic

ADFF_BIND-00014: ADFv: Unable to create the temporary file while saving the layout of the resultant component for the query.

Cause: Error in MDS configuration.

Action: Ensure MDS configuration is correct and resources are accessible.
Level: 2

Type: WARNING

Impact: Programmatic

ADFF_BIND-00015: ADFv: Something bad has happened. The file should have been there.

Cause: Error in MDS file.

Action: Ensure MDS configuration is correct and all resources are accessible.
Level: 2

Type: ERROR

Impact: Programmatic

ADFF_BIND-00016: ADFv: The resultant component with the Id {0} does not exist.

Cause: Error in MDS repository metadata.

Action: Contact your application support person to ensure that MDS repository isn't corrupted.
Level: 2

Type: WARNING

Impact: Programmatic

ADFF_BIND-00017: ADFv: Result component with the Id {0} not found in the parent.

Cause: Error in MDS repository metadata.

Action: Contact your application support person to ensure that MDS repository isn't corrupted.
Level: 2

Type: WARNING

Impact: Programmatic

ADFF_BIND-00018: ADFv: The resultant component layout was not saved for the {0} viewcriteria.

Cause: Error in MDS repository metadata.

Action: Contact your application support person to ensure that MDS repository isn't corrupted.
Level: 2

Type: WARNING

Impact: Programmatic

ADFF_BIND-00019: ADFv: Unable to read the contents of the streamedObject.

Cause: Error in MDS repository metadata.

Action: Contact your application support person to ensure that MDS repository isn't corrupted.
Level: 2

Type: WARNING

Impact: Programmatic

ADFF_BIND-00020: ADFv: Error filtering based on date strings is not supported(filter field): {0}.

Cause: Error in MDS repository metadata.

Action: Contact your application support person to ensure that MDS repository isn't corrupted.
Level: 2

Type: WARNING

Impact: Programmatic

ADFF_BIND-00021: ADFv: Null PagePhaseListener.

Cause: Trying to add a null phase listener to a page.

Action: Contact your application support person to check the page configuration.
Level: 2

Type: ERROR

Impact: Programmatic

ADFF_BIND-00022: ADFv: Unknown DataChangeType: {0}.

Cause: Cause unknown.

Action: Contact your application support person.
Level: 2

Type: ERROR

Impact: Programmatic

ADFF_BIND-00023: ADFv: Invalid attribute name: {0}.

Cause: Check source page for attribute and correct.

Action: Contact your application support person.
Level: 2

Type: ERROR

Impact: Programmatic

ADFF_BIND-00024: ADFv: Illegal DataExceptionEvent severity type: {0}.

Cause: Cause unknown.

Action: Contact your application support person.
Level: 2

Type: ERROR

Impact: Data

ADFF_BIND-00025: ADFv: Could not convert instance: {0} of type: {1} into type {2} {3}.

Cause: Cause unknown.

Action: Contact your application support person.
Level: 2

Type: ERROR

Impact: Data

ADFF_BIND-00026: ADFv: Property: {0} not found on Row: {1}.

Cause: Cause unknown.

Action: Contact your application support person.
Level: 2

Type: ERROR

Impact: Data

ADFF_BIND-00027: ADFv: Unsupported operation exception.

Cause: Application performed an unsupported operation.

Action: Contact your application support person to correct application error.
Level: 2

Type: ERROR

Impact: Programmatic

ADFF_BIND-00028: ADFv: Abort processing exception.

Cause: Cause unknown.

Action: Contact your application support person.
Level: 2

Type: ERROR

Impact: Programmatic

ADFF_BIND-00029: ADFv: No container available.

Cause: Binding metadata is incorrect or corrupted.

Action: Contact your application support person to ensure binding metadata is correct.
Level: 2

Type: ERROR

Impact: Programmatic

ADFF_BIND-00030: ADFv: Not inside a container.

Cause: Binding metadata is incorrect or corrupted.

Action: Contact your application support person to ensure binding metadata is correct.
Level: 2

Type: ERROR

Impact: Programmatic

ADFF_BIND-00031: ADFv: Unknown DataChangeEventPolicy {0}.

Cause: Binding metadata is incorrect or corrupted.

Action: Contact your application support person to ensure binding metadata is correct.
Level: 2

Type: ERROR

Impact: Programmatic

ADFF_BIND-00032: ADFv: Illegal state exception.

Cause: Cause unknown.

Action: Contact your application support person.
Level: 2

Type: ERROR

Impact: Data

ADFF_BIND-00033: ADFv: Attempt to start active for same DataUpdateListener.

Cause: Cause unknown.

Action: Contact your application support person.
Level: 2

Type: ERROR

Impact: Programmatic

ADFF_BIND-00034: ADFv: stopActiveData called for the unregistered listener.

Cause: Cause unknown.

Action: Contact your application support person.
Level: 2

Type: ERROR

Impact: Programmatic

ADFF_BIND-00035: ADFv: Illegal state, parent can't be null.

Cause: Cause unknown.

Action: Contact your application support person.
Level: 2

Type: ERROR

Impact: Data

ADFF_BIND-00036: ADFv: rowIndex: {0} cannot be less than -1.

Cause: Cause unknown.

Action: Contact your application support person.
Level: 2

Type: ERROR

Impact: Data

ADFF_BIND-00037: ADFv: Could not find row: {0} with key: {1} inside parent: {2} with key: {3}.

Cause: Cause unknown.

Action: Contact your application support person.
Level: 2

Type: ERROR

Impact: Data

ADFF_BIND-00038: ADFv: Error getting the application factory.

Cause: Error configuring databinding library.

Action: Ensure that the databinding library is included in the application.
Level: 2

Type: WARNING

Impact: Data

ADFF_BIND-00039: ADFv: Error getting the application object from factory.

Cause: Error configuring databinding library.

Action: Ensure that the databinding library is included in the application.
Level: 2

Type: WARNING

Impact: Data

ADFF_BIND-00040: Invalid Data Provided for search operation.

Cause: Invalid data.

Action: Clear Search Data and enter valid data.
Level: 2

Type: WARNING

Impact: Data

ADFF_BIND-00041: ADFv: Null Calendar Activity Definition. Please check the page definition page.

Cause: Application error.

Action: Contact your application support person.
Level: 2

Type: ERROR

Impact: Data

ADFF_BIND-00042: ADFv: Calendar Activity Id and Provider Id cannot be null.

Cause: Application data error.

Action: Contact your application support person.
Level: 2

Type: ERROR

Impact: Programmatic

ADFF_BIND-00043: ADFv: Illegal state, trying to associate client id {0} with databinding which is already associated with a different client id {1}.

Cause: Application data error.

Action: Contact your application support person.
Level: 2

Type: ERROR

Impact: Programmatic

ADFF_BIND-00044: ADFv: Unable to resolve URL through MDS for the facelet resource. Customizations if any will not be applied. {0}.

Cause: Failed to attach MDS stream handler to the URL for facelet resource.

Action: Contact your application support person.
Level: 2

Type: WARNING

Impact: Programmatic

ADFF_BIND-00045: Invalid value: {0}.

Cause: Invalid value entered in the input field of listofvalues component.

Action: Enter a valid value or pick a value from the list of values.
Level: 2

Type: ERROR

Impact: Programmatic

ADFF_BIND-00046: ViewCriteriaItem for lov attribute not found.

Cause: Search Viewcriteria doesn't have lov attribute as vcItem defined.

Action: While configuring search VC for lov search and select dialog, include lov attribute.
Level: 2

Type: WARNING

Impact: Programmatic

7 APM-10000 to APM-10015

APM-10000: Template cannot be saved because a template with same name already exits.

Cause: You are trying to save a role-template name that already exists in the system.

Action: Change the name of the template being saved to a different name that doesn't already exit in the system.
Level: 1

Type: ERROR

Impact: Authorization Policy Manager/Role-Template

APM-10001: Duplicate dimension alias name detected.

Cause: You have specified a name of dimension column-alias that has been defined for another column.

Action: Change the name of the column-alias to one that has not been used for a different column.
Level: 1

Type: ERROR

Impact: Authorization Policy Manager/Role-Template

APM-10002: Template naming convention definition requires at least two rows.

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Authorization Policy Manager/Role-Template

APM-10003: Template naming convention definition requires at least one dimension base object.

Cause: You are trying to save a role-template document without defining any dimension values.

Action: Specify a valid SQL statement that returns at least a single row.
Level: 1

Type: ERROR

Impact: Authorization Policy Manager/Role-Template

APM-10004: Template naming convention definition requires at least one role base object.

Cause: You are trying to save a role-template document without specifying a base-role.

Action: Specify a valid base-role in the base-role tab.
Level: 1

Type: ERROR

Impact: Authorization Policy Manager/Role-Template

APM-10005: Template name contains invalid character.

Cause: The name of the template contains one or more invalid characters.

Action: Remove the invalid character and retry the operation.
Level: 1

Type: ERROR

Impact: Authorization Policy Manager/Role-Template

APM-10006: Template display name cannot be blank.

Cause: You are trying to save a role-template document without specifying its display name.

Action: Specify valid display-name, and retry the opeartion.
Level: 1

Type: ERROR

Impact: Authorization Policy Manager/Role-Template

APM-10007: Template name is too long (Max length is 30 characters)

Cause: The number of characters you have entered for the template-name exceeds the max-number allowed.

Action: Reduce the number of characters for the template-name, and retry the operation.
Level: 1

Type: ERROR

Impact: Authorization Policy Manager/Role-Template

APM-10008: Template name cannot contains white space.

Cause: The template-name cannot contain any spaces.

Action: Remove any spaces in the template-name, and retry the operation.
Level: 1

Type: ERROR

Impact: Authorization Policy Manager/Role-Template

APM-10009: Template operation did not complete due to system error. Please contact administrator for detail.

Cause: Unexpected error occurred during Role-Template operation.

Action: Contact your system administrator.
Level: 1

Type: ERROR

Impact: Authorization Policy Manager/Role-Template

APM-10010: Dimension column alias cannot contain blank value.

Cause: One or more column-aliases contain null values.

Action: Provide values for all the column-aliases.
Level: 1

Type: ERROR

Impact: Authorization Policy Manager/Role-Template

APM-10011: Template dimension sql has not been defined yet.

Cause: You must define a SQL statement before the document can be saved.

Action: Provide a valid SQL statement.
Level: 1

Type: ERROR

Impact: Authorization Policy Manager/Role-Template

APM-10012: Template naming convention definition requires at least two rows.

Cause: You have not provided enough values to enforce name-uniqueness during data-role generation. There has to be at least two naming-rule defined for attributes from each entity: one or more attributes from base-role and one or more attributes from dimenstion.

Action: Select an attribute from base-role attributes and one from dimension-value attributes.
Level: 1

Type: ERROR

Impact: Authorization Policy Manager/Role-Template

APM-10013: Template dimension alias value cannot contains white space.

Cause: One of the column-aliases contain invalid characters.

Action: Remove the invalid character from the column-alias and retry the operation.
Level: 1

Type: ERROR

Impact: Authorization Policy Manager/Role-Template

APM-10014: No data return from sql. Please check the syntax of the SQL you provided.

Cause: The SQL you have entered is either invalid and/or not returning any data.

Action: Correct the SQL statement and/or ensure the SQL returns data.
Level: 1

Type: ERROR

Impact: Authorization Policy Manager/Role-Template

APM-10015: Error occurs and template operation did not complete. Please contact administrator for detail.

Cause: Role-Template execution did not complete successfully due to unknown reason.

Action: Contact your system-administrator.
Level: 1

Type: ERROR

Impact: Authorization Policy Manager/Role-Template

8 ASCRS-00001 to ASCRS-00143

ASCRS-00001: {0} of {1} completed successfully.

Cause: Operation is completed successfully.

Action: Informational, no further action is needed.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00002: {0} of {1} canceled.

Cause: Operation is canceled.

Action: Informational, no further action is needed.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00003: {0} of {1} failed.

Cause: Operation failed.

Action: Inspect the log files for the detailed cause.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00004: UP state of CRS with CRS HOME {0} could not be verified.

Cause: CRS could be down.

Action: Try to restart CRS. Refer to CRS documentation if it persists.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00006: Please run the following as root to complete this operation. {0}

Cause: Root privilege is needed for some resource task.

Action: Do as instructed.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00007: Cluster nodes specified {1} is different from cluster nodes - {2} - for dependent resource {0}

Cause: Not matching cluster nodes between this resource and its dependents.

Action: Please ensure the same set of cluster nodes for this resource and its dependents.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00008: Resource {0} cannot be deleted since dependent resources exist.

Cause: Named resource cannot be deleted since other resources depend on it.

Action: Delete all the dependent resources first.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00009: Resource {0} already manages same object as {1} wants to manage: {2}.

Cause: One physical resource shouldn't be managed twice by CRS.

Action: Delete and re-create the existing resource or update it.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00012: Invalid cluster node: {0}.

Cause: The named node is not in the cluster.

Action: Specify the correct node name. Refer to CRS command olsnodes for listing node names.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00013: Invalid policy type: {0}.

Cause: Invalid policy type specification.

Action: Refer to ASCRS online help for this operation and read about policy values.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00016: Malformed IP address or invalid host name : {0}.

Cause: Malformed IP address or invalid host name

Action: Supply a valid IP or host name.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00017: Invalid file or directory: {0}.

Cause: The named file or directory doesn't exist.

Action: Specify a valid file or directory for this argument.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00019: Resource not found: {0}.

Cause: Named resource doesn't exist.

Action: Please provide correct resource name.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00020: CRS error while calling {0}. Return code {1}.

Cause: Failure of CRS command as indicated.

Action: Refer to CRS troubleshooting documentation.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00021: Resource of type {0} and name {1} already exists.

Cause: Named resource was already created.

Action: Create a different resource or delete this one and try again.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00022: File {0} cannot be read.

Cause: Unreadable file.

Action: Change the file permission to make it readable for the ASCRS user.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00026: Error trying to retrieve require resources for {0}.

Cause: CRS cs_stat has failed to return complete information for named resource.

Action: Ensure CRS is running, diagnose CRS cs_stat. Refer to CRS troubleshooting documentation.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00028: Error writing or creating file {0}.

Cause: The file cannot be opened or created for writing.

Action: Ensure the file directory exists and the user has write permission on the named file.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00030: VIP {0} provided is up but not on this node.

Cause: The named VIP is already in use on this network.

Action: Forfeit the use of this VIP on the other host, or select a different VIP.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00031: Resource {0} is already down.

Cause: The named resource is already down.

Action: None.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00032: Resource {0} is already up on the node {1}.

Cause: The named resource is already up on the node when trying to start it.

Action: None.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00033: Resource {0} is not in state to switch.

Cause: Resource is not in good state for switch operation.

Action: Please refer to the CRS documentation for resource switchover.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00034: Specified node {1} is not in hosting members for {0}.

Cause: Invalid node member name for the names resource.

Action: Specify the correct node name.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00035: Permissions and/or ownership on resource {0} are not correct for this operation.

Cause: The user is not qualified to perform this operation.

Action: Delegate this task to the owner of this resource.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00036: No parameters to update.

Cause: No updatable information is specified for update operation.

Action: Specify updatable parameter/value. Refer to the online help.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00037: Network Interface {0} is invalid.

Cause: Network Interface is invalid.

Action: Specify a valid network interface that is in working state.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00038: VIP {0} is up on this node but not on the provided interface.

Cause: The named vip is in use by another interface on this node.

Action: Please make sure the vip is used for one interface.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00039: Update operation not allowed if either the target or resource state is not in offline state.

Cause: Resource is not in good state for update operation.

Action: Stop and take the resource offline.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00040: Are you sure you want to delete {0} (y/n) ?

Cause: Need user confirmation for resource deletion.

Action: Answer "y" for yes or "n" for no.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00041: Are you sure you want to stop {0} (y/n) ?

Cause: Need user confirmation for resource stop.

Action: Answer "y" for yes or "n" for no.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00042: Are you sure you want to switch over {0} (y/n) ?

Cause: Need user confirmation for resource switchover.

Action: Answer "y" for yes or "n" for no.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00043: Unrecognized ASCRS resource name {0}.

Cause: Without type information, this name cannot be resolved to a canonical ASCRS resource name.

Action: Use a canonical name, or specify resource type.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00044: ASCRS resource name {0} is not of type {1}.

Cause: The resource name and type are not consistent.

Action: When the name is canonical, ensure its type is consistent if it is specified.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00045: Malformed CRS parameter specification: {0}.

Cause: Syntax error in CRS resource "-o" parameter.

Action: Refer to CRS documentation or ASCRS online help for this operation.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00046: Invalid parameter name "{0}" for this resource.

Cause: This is not an ASCRS parameter or it is not applicable to this resource.

Action: Avoid using this parameter for this resource.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00047: Parameter "{0}" can only assume integer values.

Cause: This argument doesn't accept non-integer values.

Action: Supply a valid integer value for this argument.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00048: Value is out of range for parameter: {0}.

Cause: Integer value is out of valid range.

Action: Follow ASCRS online help for this command for correct value.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00049: "{0}" is not a valid value for parameter "{1}".

Cause: The value for the command-line switch is not valid.

Action: Follow ASCRS online help for this command for the correct value.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00050: No disk is mounted at "{0}".

Cause: No shared disk is mounted on the named mount point.

Action: Mount the shared disk.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00051: No signature found on shared disk at "{0}".

Cause: Signature file is missing on the root of the shared disk.

Action: Create the .ascrssf file on the root of the shared disk.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00052: Value must be an absolute path name for argument: "{0}".

Cause: The path name is not an absolute path.

Action: Use a valid absolute path name.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00053: Path does not exist: "{0}".

Cause: The named path doesn't exist as a disk mount point.

Action: Create the path name if it is intended, or use a different valid path.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00054: Unrecognized AS component name: "{0}".

Cause: User has supplied an invalid AS component name.

Action: Supply the correct WebLogic server name if this is WebLogic resource, or the OPMN component id if it is OPMN resource.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00055: Not a valid AS config file: "{0}".

Cause: The AS config file in the component home is damaged, or this is not an AS component home.

Action: Correct the configuration file and make sure this is a valid AS component home.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00056: Not recognized as an AS component home: "{0}".

Cause: User has supplied an invalid AS component home.

Action: Follow the ASCRS online help to identify the component home correctly.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00057: Node manager is not reachable at "{0}:{1}".

Cause: AS node manager is down.

Action: Make sure node manager is running on the specified host and port.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00058: Managed server "{0}" is not reachable.

Cause: The named AS server is down or invalid as user input.

Action: Make sure the server name is correct and running.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00059: Please run ascrsctl prepare command.

Cause: AS environment is not ready for CRS management.

Action: Run ascrsctl prepare command to set it up.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00060: Please run ascrsctl check command for details.

Cause: AS environment preparation failed.

Action: Run ascrsctl check command for details.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00061: Cannot write on the shared disk mounted at {0}.

Cause: The user doesn't have write permission on the name disk.

Action: Make sure this is the right user for this operation, or grant this user write permission on this disk.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00062: Cannot connect to the node manager with the existing saved credential.

Cause: Cannot log in to AS node manager due to invalid login credential file.

Action: Follow the Oracle Fusion Middleware High Availability Guide to re-create the node manager login credential files.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00063: Cannot connect to server {0} with the existing saved credential.

Cause: Cannot log in to the named AS server due to invalid login credential file.

Action: Follow the Oracle Fusion Middleware High Availability Guide to re-create the WebLogic server login credential files.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00064: CRS command {0} execution encountered I/O errors.

Cause: This command could be missing, corrupted, or other I/O issue.

Action: Ensure this CRS command can be executed manually. Check CRS logs.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00065: Stop of this resource will also stop these dependent resources:

Cause: Other resources are or will be running and it depends on this resource.

Action: Confirm or cancel when this message is prompted.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00066: Start of resource {0} on node {1} completed successfully.

Cause: Another resource is running and it depends on this resource.

Action: Either stop avoid this operation or use -f option.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00067: The current user is not the CRS home owner.

Cause: The current user is not the CRS home owner.

Action: Run this command as CRS home owner.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00068: Circular ASCRS resource dependency is detected.

Cause: The specified dependency resources depends on the updated resource.

Action: Choose different required resources.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00069: Switch of this resource will also switch these related resources:

Cause: Other resources are running that depend on or are required by this resource.

Action: Confirm or cancel when this message is prompted.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00070: Command {0} finished with errors. Refer to ASCRS log files for details.

Cause: The named ASCRS command has failed for some unknown reason.

Action: Refer to ASCRS ascrsctl.log or the ASCRS agent log for this resource.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00071: The number of cluster nodes should be more than one.

Cause: Too few cluster nodes are specified for hosting the resource.

Action: Use default or specify at least two cluster nodes
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00072: Type {0} dependencies cannot be empty for this resource.

Cause: The specified type of dependencies are not allowed to be all removed.

Action: Update the dependencies with other resource names of the desired type
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00073: Not a valid XML file: "{0}".

Cause: The XML file is damaged.

Action: Correct the file and try again.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00074: Value is not a number or out of bound for {0} in configuration for policy {1} and resource type {2}.

Cause: The specified value for the named CRS property is either a non-number or out of range.

Action: Choose a number in range. Consult ASCRS configuration for property ranges.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00075: Invalid monitor name: "{0}".

Cause: The monitor name is not found in ASCRS monitor configuration.

Action: Select a valid monitor name.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00102: ASCRS command is missing or invalid.

Cause: ASCRS command is missing or invalid.

Action: Supply correct ASCRS command, or run "ascrsctl help" for details.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00103: Value is missing or empty for argument -{0}.

Cause: The named argument cannot have an empty value.

Action: Supply the correct value for the argument. Run "ascrsctl help" for details
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00104: No value is needed for argument -{0}.

Cause: The named argument cannot have a value.

Action: Remove the value for the argument. Run "ascrsctl help" for details.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00105: Invalid ASCRS command-line syntax: {0}.

Cause: Invalid ASCRS command-line syntax.

Action: Run "ascrsctl help" for details.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00106: Required argument is missing: -{0}.

Cause: The named argument is mandatory for this operation.

Action: Refer to ascrsctl online help for details about this operation.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00107: Multiple occurrence of the same argument or its aliases not allowed: {0}.

Cause: This argument cannot be followed with multiple values.

Action: Supply a single value or refer to the ascrsctl online help for details.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00108: Invalid database component id: {0}.

Cause: Invalid database component id is specified.

Action: If componentID is specified, it should be dbinstance, dbconsole, jobscheduler (Windows only) or vsswriter (Windows only).
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00140: Online help does not exist for this request.

Cause: Invalid ascrsctl help specification.

Action: Run "ascrsctl help" for details.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00141: Invalid ASCRS resource type {0}.

Cause: Invalid ASCRS resource type.

Action: Run "ascrsctl help" for details.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00142: Invalid ASCRS command-line keyword {0}.

Cause: Invalid ASCRS argument name for ASCRS online help.

Action: Run "ascrsctl help" for details.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

ASCRS-00143: Invalid ASCRS resource name: "{0}".

Cause: An ASCRS resource name must start with an English alphabet or number and it can only contain English alphabets, numbers and the dot character. It cannot be called "nil".

Action: Check for invalid special characters in the name.
Level: 1

Type: SET_AT_RUNTIME

Impact: High Availability

9 BAM-00001 to BAM-07041

BAM-00001: Specified DataTable or DataColumn is missing.

Cause: The column mapping was missing, and the missing schema action was Error.

Action: Change the missing schema action, or add column mapping.
Level: 1

Type: ERROR

Impact: Data

BAM-00002: Cannot add object to data table mapping collection: invalid type.

Cause: The object being added to the data table mapping collection was of the incorrect type.

Action: Verify schema.
Level: 1

Type: ERROR

Impact: Programmatic

BAM-00003: invalid xsd:datetime: {0}

Cause: The date is invalid for the XML Schema datetime type.

Action: Provide a valid date.
Level: 1

Type: ERROR

Impact: Data

BAM-00004: Column value overflow: {0} value {1} is not between {2} and {3}

Cause: The specified value is beyond the range of the column data type.

Action: Provide a valid value or change the column data type.
Level: 1

Type: ERROR

Impact: Data

BAM-00005: invalid connection string provided

Cause: One or more parameters in connection string are invalid.

Action: Ensure parameters in connection string are valid.
Level: 1

Type: ERROR

Impact: Data

BAM-00006: IO exception: The network adapter could not establish the connection.

Cause: In the connection string an improper host name has been given.

Action: Ensure that the parameters in the connection string are valid.
Level: 1

Type: ERROR

Impact: Data

BAM-00007: invalid Oracle URL

Cause: In connection string, improper parameter has been given.

Action: Ensure parameters in connection string are valid.
Level: 1

Type: ERROR

Impact: Data

BAM-00008: invalid Oracle driver name

Cause: In the driver definition an invalid driver name has been provided.

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

Type: ERROR

Impact: Data

BAM-00200: A custom parameter with the ID {0} does not exist.

Cause: A custom parameter with the specified ID was not found while importing or processing a report.

Action: If the custom parameter no longer exists, then ignore this error; otherwise, verify that the ID is correct.
Level: 1

Type: ERROR

Impact: Data

BAM-00201: Cannot create calculated field {0} from modifier.

Cause: Failed to retrieve the calculated field because it has not been added to the modifier.

Action: Check the reason why the calculated field was not added to the modifier.
Level: 1

Type: ERROR

Impact: Data

BAM-00202: Cannot create decimal field {0} with scale {1}. Maximum scale is {2}.

Cause: The specified scale for a Decimal column exceeded the maximum scale supported by the Oracle BAM Server.

Action: Limit the scale to 38 or less on Oracle.
Level: 1

Type: ERROR

Impact: Data

BAM-00203: Data object {0} contains no column named {1}.

Cause: The specified column name was not found in the specified data object.

Action: Verify the column name.
Level: 1

Type: ERROR

Impact: Data

BAM-00204: There is no data object named {0}.

Cause: The specified data object was not found in the Oracle BAM Server.

Action: Verify the data object name.
Level: 1

Type: ERROR

Impact: Data

BAM-00205: Cannot create folder {0}. A data object with that name already exists.

Cause: A data object with the name specified for the folder already existed.

Action: Use a different folder name.
Level: 1

Type: ERROR

Impact: Data

BAM-00206: GetUIXml call failed for external data source type.

Cause: Failed to retrieve UI XML for an external data source type.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Data

BAM-00207: Unable to instantiate Windows Admin assembly for external data source type.

Cause: Failed to create an instance of the specified type using a constructor that matches the specified parameter.

Action: Verify the Admin type name.
Level: 1

Type: ERROR

Impact: Process

BAM-00208: No external data source type exists with ID {0}.

Cause: Failed to find the external data source type with the specified ID.

Action: Verify the external data source type ID.
Level: 1

Type: ERROR

Impact: Data

BAM-00209: Cannot find the name of the Java class that implements specified external data source type.

Cause: Failed to retrieve the AdminType value for specified external data source type from SysIterExternalDataSourceType table in the Oracle BAM schema.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Data

BAM-00210: Internal Error: Middleware.Persistence.ExternalDataSourceType: No current external data source type has been loaded.

Cause: Load by ID failed, and there was no current external data source type.

Action: Check why load by ID failed.
Level: 1

Type: ERROR

Impact: Data

BAM-00211: invalid security filter ID

Cause: Failed to load the security filter with the specified ID.

Action: Verify the security filter ID.
Level: 1

Type: ERROR

Impact: Data

BAM-00212: unknown user: {0}

Cause: Failed to retrieve a user by the specified name.

Action: Verify the user name.
Level: 1

Type: ERROR

Impact: Data

BAM-00213: unknown user

Cause: There was no current user loaded in User object.

Action: Find out why the system failed to load the user.
Level: 1

Type: ERROR

Impact: Data

BAM-00214: The aggregates {0} and {1} are of different lengths.

Cause: The two aggregates had different lengths.

Action: Make sure the two aggregates have the same length.
Level: 1

Type: ERROR

Impact: Data

BAM-00215: invalid sort in modifier: {0}

Cause: The sort is invalid for the named modifier. The user chose a combination of fields and conditions to which a sort cannot be applied.

Action: Provide a valid sort.
Level: 1

Type: ERROR

Impact: Data

BAM-00216: invalid group in modifier: {0}

Cause: The group is invalid for the named modifier.

Action: Provide a valid group.
Level: 1

Type: ERROR

Impact: Data

BAM-00217: invalid XML modifier: {0}

Cause: The XML modifier is invalid.

Action: Provide a valid XML modifier.
Level: 1

Type: ERROR

Impact: Data

BAM-00218: invalid RecordField in modifier: {0}

Cause: The record field for the named modifier is invalid.

Action: Provide a valid record field.
Level: 1

Type: ERROR

Impact: Data

BAM-00219: No data set has been specified in the modifier

Cause: No data set has been specified in the modifier.

Action: Specify a data set for the modifier.
Level: 1

Type: ERROR

Impact: Data

BAM-00220: The modifier does not have a valid fieldRef element: {0}

Cause: The modifier does not have a valid fieldRef element.

Action: Specify a valid fieldRef element for the modifier.
Level: 1

Type: ERROR

Impact: Data

BAM-00221: unknown operator in modifier

Cause: An unknown operator was encountered in the modifier.

Action: Verify the operators and retry.
Level: 1

Type: ERROR

Impact: Data

BAM-00222: Exception in remoting framework {0}.

Cause: An unhandled exception was thrown by the Oracle BAM remoting framework.

Action: Examine additional information provided with this message, and take appropriate action or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BAM-00223: Service {0} is unavailable.

Cause: The specified Oracle BAM Service is currently unavailable.

Action: Ensure that the specified Oracle BAM Service is started.
Level: 1

Type: ERROR

Impact: Data

BAM-00224: The current platform ({0}) is not supported by BAM.

Cause: The specified platform is not supported by BAM.

Action: Check the Oracle BAM documentation for details on supported platforms.
Level: 1

Type: ERROR

Impact: Process

BAM-00225: Unable to determine the current platform.

Cause: The BAM server was unable to determine the platform in which it is running.

Action: Check the log for more details.
Level: 1

Type: ERROR

Impact: Process

BAM-00300: Conflicting conversion methods encountered for version {0,number,#}. Methods {1} and {2}.

Cause: Two conflicting conversion methods were found for the version.

Action: Fix the methods.
Level: 1

Type: ERROR

Impact: Upgrade

BAM-00301: The conversion from version {0} to version {1} failed.

Cause: Failed to convert from the source version to the target version.

Action: Check the log for more details.
Level: 1

Type: ERROR

Impact: Upgrade

BAM-00302: Invocation of conversion method {0} failed.

Cause: Failed to invoke the specified conversion method.

Action: Check the log for more details.
Level: 1

Type: ERROR

Impact: Upgrade

BAM-00303: The user already exists.

Cause: This administrative user already exists.

Action: Rename this user and rerun the upgrade process.
Level: 1

Type: ERROR

Impact: Upgrade

BAM-00304: Conversion Warnings:

Cause: Warnings encountered during execution of upgrade.

Action: Review the warnings in the upgrade log file.
Level: 1

Type: WARNING

Impact: Upgrade

BAM-00400: Authentication failed.

Cause: The session ID cannot be validated.

Action: To be added.
Level: 1

Type: ERROR

Impact: Security

Cause: The user cannot be authenticated.

Action: Provide the correct credential for the given user, or add the user to the Oracle BAM Server account.

BAM-00401: Unable to authenticate request. Request scheme {0} is not supported.

Cause: Non-HTTP requests were received by Oracle BAM Web Application.

Action: Only HTTP and HTTPS requests are supported.
Level: 1

Type: ERROR

Impact: Requests/Responses

BAM-00402: Unable to authenticate request. No request or invalid request specified.

Cause: The servlet request was null.

Action: Provide a valid servlet request.
Level: 1

Type: ERROR

Impact: Requests/Responses

BAM-00403: Unauthenticated request received.

Cause: No user credentials were found.

Action: Provide valid user credentials.
Level: 1

Type: ERROR

Impact: Requests/Responses

BAM-00404: Authentication failed. User is marked inactive.

Cause: User accounts that were deleted from the configured identity store are not immediately deleted from Oracle BAM, but are marked inactive to allow the preservation of Oracle BAM objects belonging to that user.

Action: When the user is deleted, all of the associated Oracle BAM objects, such as reports and alerts, will also be deleted. Use the Oracle BAM Administrator application to reassign any of the Oracle BAM objects belonging to this user that must be assigned to another Oracle BAM user before deleting the inactive user.
Level: 1

Type: ERROR

Impact: Security

Cause: This user was no longer defined in the configured identity store and has been marked inactive.

Action: Use the Oracle BAM Administrator application to permanently delete any inactive users so that these user names can be reused.

BAM-00405: Reauthentication required.

Cause: The session id provided by the client is unknown by the server; may be due to server restart.

Action: The client library attempts to provide additional credentials to the server automatically. If this fails, AuthAuthenticationFailed will be thrown.
Level: 1

Type: ERROR

Impact: Security

BAM-00500: exception in messaging framework: {0}

Cause: An unhandled exception was thrown by the Oracle BAM messaging framework.

Action: Examine additional information provided with this message, and take appropriate action or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BAM-00501: Unrecoverable exception for destination {0}.

Cause: Unrecoverable exception occurred.

Action: Examine other error messages that may have led to this message, and take appropriate action or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BAM-00510: Resource acquisition for destination {0} timed out after {1} milliseconds.

Cause: Resources, such as a connection, for the specified destination could not be acquired during open (initialization) or recovery in a timely manner.

Action: Ensure that the specified destination is available.
Level: 1

Type: ERROR

Impact: Process

BAM-00511: Resource acquisition for destination {0} was interrupted.

Cause: Resources, such as a connection, for the specified destination could not be acquired during open (initialization) or recovery due to an interrupt, likely caused by server shutdown, application stop, undeployment, or redeployment.

Action: Examine other error messages that may have led to this message, and take appropriate action or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BAM-00512: Resource acquisition for destination {0} due to invalid internal state {1}.

Cause: Resources, such as a connection, for the specified destination could not be acquired during open (initialization) or recovery due to an internal invalid state, likely caused by a timing issue or concurrent execution of conflicting requests, such as a start, stop or close request during open (initialization) or recovery execution.

Action: Examine other error messages that may have led to this message, and take appropriate action or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BAM-00513: Resource acquisition for destination {0} failed.

Cause: Resources, such as a connection, for the specified destination could not be acquired during open (initialization) or recovery.

Action: Examine other error messages that may have led to this message, and take appropriate action or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BAM-00520: Resource recovery for destination {0} timed out after {1} milliseconds.

Cause: Resources, such as a connection, for the specified destination were lost and could not be reacquired after repeated attempts in a timely manner.

Action: Ensure that the specified destination is available.
Level: 1

Type: ERROR

Impact: Process

BAM-00521: Resource recovery for destination {0} was interrupted.

Cause: Resources, such as a connection, for the specified destination were lost and could not be reacquired after repeated attempts due to an interrupt, likely caused by server shutdown, application stop, undeployment, or redeployment.

Action: Examine other error messages that may have led to this message, and take appropriate action or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BAM-00522: Resource recovery for destination {0} due to invalid internal state {1}.

Cause: Resources, such as a connection, for the specified destination could not be recovered due to an internal invalid state, likely caused by a timing issue or concurrent execution of conflicting requests, such as a start, stop or close request during recovery execution.

Action: Examine other error messages that may have led to this message, and take appropriate action or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BAM-00523: Resource recovery for destination {0} failed.

Cause: Resources, such as a connection, for the specified destination were lost and could not be recovered.

Action: Examine other error messages that may have led to this message, and take appropriate action or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BAM-00530: Resource open for destination {0} timed out after {1} milliseconds.

Cause: Resources, such as a connection, for the specified destination could not be opened (initialized) in a timely manner.

Action: Ensure that the specified destination is available.
Level: 1

Type: ERROR

Impact: Process

BAM-00531: Resource open for destination {0} was interrupted.

Cause: Resources, such as a connection, for the specified destination could not be opened (initialized) due to an interrupt, likely caused by server shutdown, application stop, undeployment, or redeployment.

Action: Examine other error messages that may have led to this message, and take appropriate action or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BAM-00532: Resource open for destination {0} due to invalid internal state {1}.

Cause: Resources, such as a connection, for the specified destination could not be opened (initialized) due to an internal invalid state, likely caused by a timing issue or concurrent execution of conflicting requests, such as a stop or close request, during initialization.

Action: Examine other error messages that may have led to this message, and take appropriate action or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BAM-00533: Resource open for destination {0} failed.

Cause: Resources, such as a connection, for the specified destination could not be opened (initialized).

Action: Examine other error messages that may have led to this message, and take appropriate action or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BAM-00543: Resources for destination {0} were not closed.

Cause: Resources, such as a connection, for the specified destination could not be closed.

Action: Examine other error messages that may have led to this message, and take appropriate action or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BAM-00550: Resource start operation for destination {0} timed out after {1} milliseconds.

Cause: Resources, such as a connection, for the specified destination could not be started in a timely manner.

Action: Ensure that the specified destination is available.
Level: 1

Type: ERROR

Impact: Process

BAM-00551: Resource start operation for destination {0} was interrupted.

Cause: Resources, such as a connection, for the specified destination could not be started due to an interrupt, likely caused by server shutdown, application stop, undeployment, or redeployment.

Action: Examine other error messages that may have led to this message, and take appropriate action or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BAM-00552: Resource start for destination {0} due to invalid internal state {1}.

Cause: Resources, such as a connection, for the specified destination could not be started due to an internal invalid state, likely caused by a timing issue or concurrent execution of conflicting requests, such as open (initialization) or recovery, or a stop or close request, during execution of a start request.

Action: Examine other error messages that may have led to this message, and take appropriate action or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BAM-00553: Resources start operation for destination {0} failed.

Cause: Resources, such as a connection, for the specified destination could not be started.

Action: Examine other error messages that may have led to this message, and take appropriate action or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BAM-00560: JMS destination {0} not found.

Cause: The specified JMS destination was not found.

Action: Ensure that the specified JMS destination is defined.
Level: 1

Type: ERROR

Impact: Process

BAM-00561: Only Topics are allowed to have durable subscriptions.

Cause: The specified JMS Destination was not found be Topic.

Action: Ensure that the specified JMS Destination is a Topic.
Level: 1

Type: ERROR

Impact: Process

BAM-00562: Authentication Failure

Cause: There was authentication failure against the JMS server.

Action: Ensure that you have specified the right credentials.
Level: 1

Type: ERROR

Impact: Process

BAM-01000: The Oracle BAM Active Data Cache Server failed to start. {0}.

Cause: The Oracle BAM Active Data Cache Server failed to start.

Action: Check the log for more details.
Level: 1

Type: ERROR

Impact: Process

BAM-01001: The Oracle BAM Active Data Cache Server stopped, but with a failure: {0}.

Cause: An exception was thrown when the Oracle BAM Active Data Cache Server stopped.

Action: Check the log for more details.
Level: 1

Type: ERROR

Impact: Process

BAM-01200: The Administrator role is required by the system and cannot be deleted.

Cause: An attempt was made to delete the Administrator role.

Action: The Administrator role cannot be deleted.
Level: 1

Type: ERROR

Impact: Security

BAM-01201: The root folder cannot be deleted.

Cause: An attempt was made to delete the root folder.

Action: Do not attempt to delete the root folder.
Level: 1

Type: ERROR

Impact: Security

BAM-01202: User cannot be deleted.

Cause: An attempt was made by the user to delete his own account.

Action: A user cannot delete his own account.
Level: 1

Type: ERROR

Impact: Security

BAM-01203: insufficient permission to get the ACL for this object

Cause: An attempt was made to retrieve the access control list for this object.

Action: Only the object owner or Administrator can retrieve the access control list for this object.
Level: 1

Type: ERROR

Impact: Security

BAM-01204: The account used to run the Oracle BAM Active Data Cache does not have permission to retrieve the list of groups for this user.

Cause: The account used to run the Oracle BAM Active Data Cache did not have permission to retrieve the list of groups for the specified user.

Action: Contact the network administrator.
Level: 1

Type: ERROR

Impact: Security

BAM-01205: Only an administrator can impersonate another user.

Cause: An attempt was made to impersonate another user.

Action: Log in as an administrator to impersonate another user.
Level: 1

Type: ERROR

Impact: Security

BAM-01206: Permission to set the ACL for this object is not available.

Cause: An attempt was made to set the access control list for this object.

Action: Only the object owner or administrator can set the access control list for this object.
Level: 1

Type: ERROR

Impact: Security

BAM-01207: The value of a timestamp column cannot be set explicitly.

Cause: An attempt was made to set the value of a read-only timestamp column.

Action: The value of a read-only timestamp column cannot be set.
Level: 1

Type: ERROR

Impact: Data

BAM-01208: GetChangeList() called on non-active viewset.

Cause: An attempt was made to get a change list on a non-active viewset.

Action: Provide an active viewset.
Level: 1

Type: ERROR

Impact: Programmatic

BAM-01209: The column {0} is read-only.

Cause: An attempt was made to set the value of a read-only column.

Action: The value of a read-only column cannot be set.
Level: 1

Type: ERROR

Impact: Data

BAM-01210: The column {0} cannot be null.

Cause: The value of column is null.

Action: Set the value of column to be not null.
Level: 1

Type: ERROR

Impact: Data

BAM-01211: The error, {0}, has occurred involving dataset {1} in the Active Data Cache internal data access system.

Cause: An internal exception has occurred in the Active Data Cache.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

BAM-01212: The Active Data Cache data files are read-only. Startup cannot continue.

Cause: The Active Data Cache data files are read-only.

Action: Change the access rights of Active Data Cache data files.
Level: 1

Type: ERROR

Impact: Process

BAM-01213: The Active Data Cache data files path {0} is invalid.

Cause: The Active Data Cache data files path is invalid.

Action: Verify that the directory exists. If the directory is on a network, make sure that the network is available.
Level: 1

Type: ERROR

Impact: Files

BAM-01214: Active Data Cache data object already exists.

Cause: The data object already exists in the Active Data Cache.

Action: Choose another data object name or delete the old data object.
Level: 1

Type: ERROR

Impact: Data

BAM-01215: Active Data Cache data object could not be created.

Cause: Connection failed.

Action: Check the log file for more details and report the error.
Level: 1

Type: ERROR

Impact: Data

Cause: Create Table SQL statement failed.

Action: Check the log file for more details and report the error.

BAM-01216: The data object could not be deleted from the Active Data Cache.

Cause: Connection failed.

Action: Check the log file for more details and report the error.
Level: 1

Type: ERROR

Impact: Data

Cause: Drop Table SQL statement failed.

Action: Check the log file for more details and report the error.

BAM-01217: Active Data Cache data object could not be loaded.

Cause: getDataSetSchema() failed.

Action: Check the log file for more details and report the error.
Level: 1

Type: ERROR

Impact: Data

BAM-01218: The data object {0} does not exist.

Cause: The data object does not exist.

Action: Create the data object first or take appropriate action.
Level: 1

Type: ERROR

Impact: Data

BAM-01219: Active Data Cache data object row could not be deleted.

Cause: Connection failed.

Action: Check the log file for more details and report the error.
Level: 1

Type: ERROR

Impact: Data

Cause: Delete row command failed.

Action: Check the log file for more details and report the error.

BAM-01220: Active Data Cache data object row could not be inserted.

Cause: There was a failure trying to insert a row.

Action: Check the log for more details.
Level: 1

Type: ERROR

Impact: Data

BAM-01221: The row in the data object could not be updated.

Cause: There was a failure trying to update a row.

Action: Check the log for more details.
Level: 1

Type: ERROR

Impact: Data

BAM-01222: Active Data Cache data objects list could not be loaded.

Cause: There was a failure to load a list of Active Data Cache data objects.

Action: Check the log for more details.
Level: 1

Type: ERROR

Impact: Data

BAM-01223: Only one column of type autoincrement is permitted in a single data object.

Cause: The data object already contains an autoincrement column. The limit is one autoincrement column per data object.

Action: Change the column type to integer, or remove the existing autoincrement column.
Level: 1

Type: ERROR

Impact: Data

BAM-01224: The data object cannot be deleted or edited when it is in use by an open view or alert.

Cause: The data object is not in edit mode.

Action: Stop the attempted operation.
Level: 1

Type: ERROR

Impact: Data

Cause: The data object or its dependent data objects are in use.

Action: Stop the attempted operation, or try the operation after freeing the view or alert.

Cause: Failed to grab the lock for updating.

Action: Stop the attempted operation, or try the operation after freeing the view or alert.

BAM-01225: A timeout trying to obtain a lock on the data object {0} expired.

Cause: Have timed out while waiting to obtain a lock on the data object.

Action: Try the attempted operation later or after the interfering tasks are finished.
Level: 1

Type: ERROR

Impact: Data

BAM-01226: The decimal value does not fit in this column.

Cause: This decimal value does not fit in this column.

Action: Check the accuracy of provided number.
Level: 1

Type: ERROR

Impact: Data

BAM-01227: A data object with a Lookup into the current data object is in use.

Cause: A data object depending on the current data object is in use.

Action: Stop the attempted operation (for example, destroy).
Level: 1

Type: ERROR

Impact: Data

BAM-01228: The folder already contains an object named {0}.

Cause: Another object with the same name exists in the folder.

Action: Assign a unique name to the object.
Level: 1

Type: ERROR

Impact: Data

BAM-01229: A group can be added to a role only once.

Cause: A group cannot be added to a role more than once.

Action: Stop the operation.
Level: 1

Type: ERROR

Impact: Data

BAM-01230: duplicate identifier

Cause: The given identifier is already in use.

Action: Change the identifier.
Level: 1

Type: ERROR

Impact: Data

BAM-01231: A user can be added to a role only once.

Cause: A user cannot be added to a role more than once.

Action: Stop the operation.
Level: 1

Type: ERROR

Impact: Data

BAM-01232: Exception was previously caught during transaction processing for this viewset.

Cause: An exception occurred during the processing of active data.

Action: Check the log for more details.
Level: 1

Type: ERROR

Impact: Process

BAM-01233: The folder {0} is already defined.

Cause: The caller is attempting to create a folder with an existing name.

Action: Stop the operation.
Level: 1

Type: ERROR

Impact: Data

BAM-01234: Folder {0} cannot be deleted.

Cause: The folder cannot be deleted because it is not empty.

Action: Delete the items in the folder before attempting to delete the folder.
Level: 1

Type: ERROR

Impact: Data

BAM-01235: Folder {0} not found.

Cause: The folder was not found by its name.

Action: Check the spelling of folder name.
Level: 1

Type: ERROR

Impact: Data

BAM-01236: The Active Data Cache Satellite does not support this function.

Cause: A clause to the monitor list was added; however, its function was not recognized.

Action: Provide the correct name for the viewset change.
Level: 1

Type: ERROR

Impact: Data

BAM-01237: The Active Data Cache cannot group on column {0}.

Cause: The Active Data Cache cannot group on a column containing null values.

Action: Provide non-null column values.
Level: 1

Type: ERROR

Impact: Data

BAM-01238: invalid arguments

Cause: The supplied parameters are invalid.

Action: Provide valid parameters.
Level: 1

Type: ERROR

Impact: Programmatic

BAM-01239: The Active Data Cache has been secured using a security key.

Cause: The Active Data Cache has been secured using a security key.

Action: The user must provide the correct security key in order to access it. To provide a security key, add a value for BAMSecureServerKey to the application configuration file.
Level: 1

Type: ERROR

Impact: Security

BAM-01240: Active Data Cache invalid data type

Cause: The data is not the correct type for this column.

Action: Make sure that the data being inserted or updated is of the correct type for this column.
Level: 1

Type: ERROR

Impact: Data

BAM-01241: invalid expression

Cause: An invalid aggregate operation has been specified for the aggregate expression.

Action: Choose one of the following operations: COUNT, COUNTDISTINCT, AVG, SUM, MAX, MIN, FirstInGroup, or LastInGroup.
Level: 1

Type: ERROR

Impact: Programmatic

BAM-01242: Invalid calculated column: {0}

Cause: The expression specified for the calculated column is invalid.

Action: Correct the expression.
Level: 1

Type: ERROR

Impact: Data

BAM-01243: The viewset count cannot be obtained if it was opened using the bRetrieveSchemaOnly option.

Cause: The viewset was opened with the bRetrieveSchemaOnly option.

Action: Open the viewset and set the bRetrieveSchemaOnly option to false.
Level: 1

Type: ERROR

Impact: Data

BAM-01244: invalid identifier

Cause: The identifier contains an invalid character.

Action: The identifier must start with an alphanumeric character or underscore (_), and it must contain only underscore and alphanumeric characters.
Level: 1

Type: ERROR

Impact: Data

BAM-01245: Active Data Cache invalid max length

Cause: Column type is decimal and its maximum size specification exceeds an accepted maximum system value.

Action: Change the column value.
Level: 1

Type: ERROR

Impact: Programmatic

BAM-01246: The scale must be greater than or equal to zero.

Cause: The column is of type decimal and its scale is smaller than zero.

Action: Change the scale value.
Level: 1

Type: ERROR

Impact: Programmatic

BAM-01247: An invalid transaction type sequence exists in the transaction map.

Cause: An invalid transaction type sequence was encountered in the transaction map, such as Insert or Update followed by Insert, or Delete followed by Insert or Update.

Action: Resequence the transactions.
Level: 1

Type: ERROR

Impact: Data

BAM-01248: A group-level calculation exists in an operation that is invalid, such as sorting, filtering, or grouping.

Cause: An aggregate expression is specified in a group-level calculation.

Action: Remove the aggregate expression.
Level: 1

Type: ERROR

Impact: Data

BAM-01249: The maximum number of users automatically added to the Active Data Cache has been reached.

Cause: The maximum number of users automatically added to the Active Data Cache has been reached.

Action: Add new users with the Oracle BAM Administrator application.
Level: 1

Type: ERROR

Impact: Data

BAM-01250: The column {0} must have a default value or allow null values.

Cause: The datetime column does not have a default or is not nullable.

Action: Provide a default for the datetime column or make it nullable.
Level: 1

Type: ERROR

Impact: Data

BAM-01251: When using OpenViewsets, all of the modifiers must be on the same data object.

Cause: Some modifiers are not applied on the same data object.

Action: Change the modifiers in the opened viewset.
Level: 1

Type: ERROR

Impact: Data

BAM-01252: Multiple parent aggregate rows found.

Cause: Multiple matching rows were found in Group Table.

Action: Trace the history to find out why multiple aggregate rows have been inserted.
Level: 1

Type: ERROR

Impact: Data

BAM-01253: object name not found: {0}

Cause: The object name was not found.

Action: Check the spelling of the name.
Level: 1

Type: ERROR

Impact: Data

BAM-01254: No record fields specified in the modifier on {0}.

Cause: No record fields specified in the modifier.

Action: Provide record fields in the modifier.
Level: 1

Type: ERROR

Impact: Data

BAM-01255: Path name {0} does not start with a slash (/).

Cause: The path name started without a slash.

Action: The path name should start with a slash (/).
Level: 1

Type: ERROR

Impact: Data

BAM-01256: Operation not allowed.

Cause: An invalid operation was performed.

Action: Avoid performing the invalid operation.
Level: 1

Type: ERROR

Impact: Data

BAM-01257: Insufficient permission to perform the requested action.

Cause: The user performed an action without permission.

Action: Grant the permission to the user or group.
Level: 1

Type: ERROR

Impact: Security

BAM-01258: The user does not have the required privileges to perform the requested action.

Cause: Privilege was required to create a data object.

Action: Log in as another user who has the required privilege.
Level: 1

Type: ERROR

Impact: Security

Cause: Privilege was required to move a subtree in the folder hierarchy to a new owner.

Action: Log in as an Administrator user.

Cause: Privilege was required to add a new role to the Oracle BAM server.

Action: Log in as an Administrator user.

Cause: Privilege was required to update the description, privileges, and members of a role in Oracle BAM server.

Action: Log in as an Administrator user.

Cause: Privilege was required to delete a role in Oracle BAM server.

Action: Log in as an Administrator user.

Cause: Privilege was required to rename a role in Oracle BAM server.

Action: Log in as an Administrator user.

BAM-01259: Only objects of type {0} can be added to this folder.

Cause: The object inserted to a folder is not a folder and it does not match the parent folder's type restriction.

Action: Either remove the type restriction or choose the right type name.
Level: 1

Type: ERROR

Impact: Data

BAM-01260: The Active Data Cache schema version {1,number,#} does not match the expected version {0,number,#}.

Cause: At startup, the Data Store Server version did not match the ADC schema version.

Action: Check the versions of the Active Data Cache schema and Oracle BAM Server used, and make sure that they are compatible.
Level: 1

Type: ERROR

Impact: Upgrade

BAM-01261: Cannot connect to the Oracle BAM Server.

Cause: The system was unable to connect to the Oracle BAM Server.

Action: Contact the system administrator if the error persists.
Level: 1

Type: ERROR

Impact: Process

BAM-01262: Active Data Cache server exception in {0}.

Cause: Active Data Cache server failed to start up.

Action: Check system configurations and retry.
Level: 1

Type: ERROR

Impact: Process

Cause: DataStoreServer failed to start up.

Action: Check system configurations and retry.

Cause: Failed to connect to Active Data Cache server locally.

Action: Check system configurations and retry.

BAM-01263: The Oracle BAM Server has restarted.

Cause: The Oracle BAM Server was restarted.

Action: None
Level: 1

Type: WARNING

Impact: Process

BAM-01264: Sorting required on TopN with ties.

Cause: The viewset does not have the required sorting on the query.

Action: Specify sorting on the query.
Level: 1

Type: ERROR

Impact: Data

BAM-01265: An error ({0}) has occurred in the Active Data Cache storage system.

Cause: An error occurred in the Active Data Cache storage system.

Action: Check the log to see more details.
Level: 1

Type: ERROR

Impact: Process

BAM-01266: System object not found.

Cause: No system object could be found with the given ID.

Action: Check the provided ID.
Level: 1

Type: ERROR

Impact: Data

BAM-01267: Active Data Cache system type not found ({0}).

Cause: No system type could be found with the given ID.

Action: Check the provided ID.
Level: 1

Type: ERROR

Impact: Data

BAM-01268: A transaction is already in progress.

Cause: An attempt was made to begin a transaction a second time without a commit or roll back.

Action: Commit or roll back the previous transaction first.
Level: 1

Type: ERROR

Impact: Data

BAM-01269: invalid Active Data Cache transaction ID: {0}

Cause: The transaction with the specified ID does not exist.

Action: Check the provided transaction ID.
Level: 1

Type: ERROR

Impact: Data

BAM-01270: The Active Data Cache transaction with ID {0} is in use and cannot be committed or rolled back.

Cause: The specified transaction is in use. There are open DataReaders in the transaction.

Action: All DataReaders created in this transaction must be closed prior to a commit or rollback operation.
Level: 1

Type: ERROR

Impact: Data

BAM-01271: No transaction is in progress.

Cause: An attempt was made to call commit or rollback without a call to begin transaction.

Action: Begin a transaction first.
Level: 1

Type: ERROR

Impact: Data

BAM-01272: The user in the current thread is not authenticated.

Cause: The user in the current thread was not authenticated.

Action: The user should be authenticated first.
Level: 1

Type: ERROR

Impact: Security

BAM-01273: Active Data Cache unique constraint violation

Cause: A row cannot be inserted because a similar row has already been inserted.

Action: Delete the previous row or discard the new row.
Level: 1

Type: ERROR

Impact: Data

BAM-01274: The field ID {0} is not recognized.

Cause: No column could be found in the given data set with the given ID.

Action: Check the field ID.
Level: 1

Type: ERROR

Impact: Data

BAM-01275: The field {0} is not recognized.

Cause: The Field ID in the expression of a calculated column was for neither a Column nor a Calculated column.

Action: Check the field ID.
Level: 1

Type: ERROR

Impact: Data

Cause: An operand in an aggregate expression is an instance of Field ID, but it is not a recognized column ID.

Action: Check the field ID.

BAM-01276: Active Data Cache unknown internal event

Cause: An unrecognized change occurred in a viewset.

Action: The change should be one of the following: Insert, Update, or Delete.
Level: 1

Type: ERROR

Impact: Process

BAM-01277: Active Data Cache unknown type data column

Cause: Unknown data type found.

Action: A valid Oracle BAM data type should be one of the following: BOOLEAN, CLOB, TIMESTAMP, DATETIME, DECIMAL, FLOAT, INTEGER, ITERID, or STRING.
Level: 1

Type: ERROR

Impact: Data

Cause: Unknown Java class found.

Action: A valid native type should be one of the following: String, Integer, BigDecimal, DateTime, Byte, Boolean, Short, Double, Long, or DBNull.

BAM-01278: unsupported data type in result schema: {0}

Cause: Unsupported data type in the column definition or in the result set coming from storage.

Action: Check the data type and provide the appropriate data.
Level: 1

Type: ERROR

Impact: Data

Cause: Incompatible data types of two operands are involved in a math operation.

Action: Check the data types and provide the appropriate data.

BAM-01279: unsupported expression: {0}

Cause: An invalid aggregate operation was found.

Action: Provide a valid aggregate operation: COUNT, SUM, AVG, MIN, MAX, FirstInGroup, LastInGroup, STDDEV, RANGE, QUOTA, NOOP, PERCENTOFTOTAL, or COUNTDISTINCT.
Level: 1

Type: ERROR

Impact: Data

BAM-01280: User not found.

Cause: The given user name was not found in the Oracle BAM Server account.

Action: Provide a valid user in the Oracle BAM Server account.
Level: 1

Type: ERROR

Impact: Security

BAM-01281: Values {0} not found in table {1}.

Cause: The specified key values in the group table were not found.

Action: Check if specified key values are missing from the group table.
Level: 1

Type: ERROR

Impact: Data

BAM-01282: This viewset not found: {0}.

Cause: The viewset manager cannot find the specified viewset.

Action: Make sure that the specified viewset was not closed.
Level: 1

Type: ERROR

Impact: Data

Cause: The viewset was closed.

Action: None

BAM-01283: The calculated column {0} contains a circular reference.

Cause: A circular reference was found in the calculated column definition.

Action: When defining a calculated column there can be no circular references.
Level: 1

Type: ERROR

Impact: Data

BAM-01284: Key column IDs cannot be changed within a transaction.

Cause: Key column IDs were changed within a transaction.

Action: Avoid changing key column IDs within a transaction.
Level: 1

Type: ERROR

Impact: Data

BAM-01285: Upsert value column IDs cannot be changed within a transaction.

Cause: A list of columns to be updated was changed within a transaction.

Action: Avoid changing the list of columns to be updated during a single transaction.
Level: 1

Type: ERROR

Impact: Data

BAM-01286: The super user cannot be deleted.

Cause: The deleted user was the super user.

Action: The super user cannot be deleted.
Level: 1

Type: ERROR

Impact: Security

BAM-01287: The data object with ID {0} is external, and its contents cannot be edited.

Cause: An attempt was made to update a data object derived from an external data source.

Action: Data objects created using external data sources cannot be updated.
Level: 1

Type: ERROR

Impact: Data

BAM-01288: The data object {0} is external and cannot have lookup columns.

Cause: An external data object definition contained lookup columns.

Action: Do not include lookup columns in external data object definitions.
Level: 1

Type: ERROR

Impact: Data

BAM-01289: The external data source for this data object has been deleted.

Cause: The external data source for this data object was not found.

Action: Provide the correct connection information.
Level: 1

Type: ERROR

Impact: Data

BAM-01290: The external data source type {0} does not exist.

Cause: The specified external data source type was not found.

Action: Provide a valid external data source type.
Level: 1

Type: ERROR

Impact: Data

BAM-01291: The index {0} already exists.

Cause: This index was found in the data object.

Action: Do not use an index twice within a data object.
Level: 1

Type: ERROR

Impact: Data

BAM-01292: The column {0} cannot be removed because it is indexed.

Cause: The column {0} was not removed because it is indexed.

Action: Remove the index before attempting to remove the column.
Level: 1

Type: ERROR

Impact: Data

BAM-01293: The layout of the column {0} cannot be changed because it is indexed.

Cause: The layout of the column {0} was not changed because it is indexed.

Action: Remove the index before attempting to change the layout of the column.
Level: 1

Type: ERROR

Impact: Data

BAM-01294: The column {0} cannot be indexed because it is a calculated column.

Cause: The column used in the index is a calculated column.

Action: Do not use a calculated column in an index.
Level: 1

Type: ERROR

Impact: Data

BAM-01295: The column {0} cannot be indexed because it is a lookup.

Cause: The column used in the index is a lookup column.

Action: Do not use a lookup column in an index.
Level: 1

Type: ERROR

Impact: Data

BAM-01296: The specified set of columns is already indexed.

Cause: The specified column list was already indexed.

Action: Do not attempt to index a set of indexed columns.
Level: 1

Type: ERROR

Impact: Data

BAM-01297: The index {0} does not exist.

Cause: The specified index was not found in the edit or remove operations.

Action: Verify that the provided index ID is correct.
Level: 1

Type: ERROR

Impact: Data

BAM-01298: An invalid ConnectionString is specified in Active Data Cache configuration. Parameter {0} is invalid.

Cause: An invalid ConnectionString was specified in Active Data Cache configuration.

Action: Correct the ConnectionString specification.
Level: 1

Type: ERROR

Impact: Configuration

BAM-01299: One of the String columns being used as a filter, group by, or sort in this view is too large.

Cause: This column is too long to use in a sort, filter, or group operation.

Action: Do not use this column in a sort, filter, or group operation.
Level: 1

Type: ERROR

Impact: Data

BAM-01300: The column {0} is a calculation and cannot be used as a lookup key.

Cause: A calculated column was used as a lookup key.

Action: Do not use a calculated column as a lookup key.
Level: 1

Type: ERROR

Impact: Data

BAM-01301: A lookup on the data object {0} cannot be created because it contains lookups.

Cause: A lookup was created to a data object that contains lookups.

Action: A lookup cannot be created on a data object that contains lookups.
Level: 1

Type: ERROR

Impact: Data

BAM-01302: The primary key list and the foreign key list are of different lengths, or one of the data types does not match.

Cause: The primary key list and the foreign key list were of different lengths.

Action: Verify that the key lists match.
Level: 1

Type: ERROR

Impact: Data

Cause: One of the data types on the matching key lists did not match.

Action: Match the data types of the matching keys.

BAM-01303: The data object {0} cannot have lookups because it is already being used as a dimension.

Cause: The data object was already used as a dimension, and creating lookups in it was not permitted.

Action: Do not create lookups in data objects being used as dimensions.
Level: 1

Type: ERROR

Impact: Data

BAM-01304: The foreign key column {0} does not exist.

Cause: The foreign key column specified did not exist.

Action: Verify the column name or create the missing column.
Level: 1

Type: ERROR

Impact: Data

BAM-01305: The primary key column {0} does not exist.

Cause: The primary key column specified did not exist.

Action: Verify the column name or create the missing column.
Level: 1

Type: ERROR

Impact: Data

BAM-01306: The column {0} is a lookup and cannot be used as a lookup key.

Cause: A lookup column was used as a lookup key.

Action: Do not use lookup columns as lookup keys.
Level: 1

Type: ERROR

Impact: Data

BAM-01307: The user must specify at least one column for the foreign and primary keys.

Cause: No columns were specified for the foreign and primary keys.

Action: Specify at least one column for the foreign and primary keys.
Level: 1

Type: ERROR

Impact: Data

BAM-01308: Lookups on calculated columns are not supported.

Cause: Columns to be looked up were calculated columns.

Action: Do not attempt lookups on calculated columns.
Level: 1

Type: ERROR

Impact: Data

BAM-01309: A negative or zero grouped time bucket cannot be created.

Cause: A negative or zero grouped time bucket size was specified.

Action: Specify a positive grouped time bucket size.
Level: 1

Type: ERROR

Impact: Data

BAM-01310: Time buckets with a non-time-based function cannot be created.

Cause: A non-time-based function was specified for a time bucket.

Action: Specify one of the time-based functions: YEAR, HOUR, MINUTE, SECOND, WEEK, or MONTH.
Level: 1

Type: ERROR

Impact: Data

BAM-01311: {0} is not divisible by {1}.

Cause: The time bucket dimension was not divisible by bucket size.

Action: Change either the time bucket dimension or bucket size.
Level: 1

Type: ERROR

Impact: Programmatic

BAM-01312: The batch is full and FlushOnDemand is in effect.

Cause: An attempt was made to add a new operation to the batch when the batch was full and FlushOnDemand was enabled.

Action: When using FlushOnDemand it is the caller's responsibility to call the flush method when the batch becomes full. The batch call will return false when the batch becomes full. At this point flush must be called or the next batch operation will throw this exception.
Level: 1

Type: ERROR

Impact: Configuration

BAM-01313: Unable to obtain URL for resource "{0}."

Cause: Could not find the resource with the given name.

Action: Verify the resource name, or make sure that the resource exists at the given path name.
Level: 1

Type: ERROR

Impact: Files

BAM-01314: Unable to obtain path for resource "{0}."

Cause: Could not determine the appropriate classpath entry for the given class name using the specified class loader.

Action: Verify the resource name, or make sure that the resource exists at given path name.
Level: 1

Type: ERROR

Impact: Files

BAM-01315: Evaluator has not been initialized.

Cause: Evaluator was not successfully initialized.

Action: Find out why the static block of Evaluator failed to perform static initialization.
Level: 1

Type: ERROR

Impact: Process

BAM-01316: Evaluator initialization failed.

Cause: Evaluator was not successfully initialized.

Action: Find out why the static block of Evaluator failed to perform static initialization.
Level: 1

Type: ERROR

Impact: Process

BAM-01317: Compilation for class {0} failed with error {1}.

Cause: The compilation for a Java file failed.

Action: Check the syntax of the provided Java file or the version of the compiler used.
Level: 1

Type: ERROR

Impact: Process

BAM-01318: Expression evaluation failed.

Cause: Failed to evaluate the specified method of the class represented by this Evaluator with the given arguments.

Action: Check the log for more details.
Level: 1

Type: ERROR

Impact: Process

BAM-01319: Unable to obtain class loader.

Cause: Failed to get Evaluator's class loader.

Action: Check whether or not this class was loaded by the bootstrap class loader.
Level: 1

Type: ERROR

Impact: Deployment

BAM-01320: Cannot add an auto-incrementing field to a data object that contains data.

Cause: The data object contains data, so a mandatory non-null column cannot be added.

Action: Clear the data from the data object before adding the auto-incrementing field.
Level: 1

Type: ERROR

Impact: Data

BAM-01321: Cannot add a timestamp field to a data object that contains data.

Cause: The data object contains data, so a mandatory non-null column cannot be added.

Action: Clear the data from the data object before adding the timestamp field.
Level: 1

Type: ERROR

Impact: Data

BAM-01322: Calculated field does not have a name.

Cause: Calculated field does not have a name.

Action: Provide a name for the calculated field.
Level: 1

Type: ERROR

Impact: Programmatic

BAM-01323: This functionality is not supported.

Cause: This functionality is not supported.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BAM-01324: Unable to establish Oracle BAM administrator account.

Cause: The Oracle BAM Active Data Cache failed to establish the Oracle BAM administrator account.

Action: Confirm that the Oracle BAM administrator account is properly defined in the configured identity store.
Level: 1

Type: ERROR

Impact: Process

BAM-01325: Cannot delete a data object that is a lookup source for another data object.

Cause: Data object is lookup source for another data object.

Action: Delete dependent data objects before deleting lookup source data object.
Level: 1

Type: ERROR

Impact: Data

BAM-01326: Aggregates are not allowed in this Filter condition.

Cause: Aggregates are not allowed in this Filter condition.

Action: Change the Filter condition specified for the report/alert to remove aggregates.
Level: 1

Type: ERROR

Impact: Process

BAM-01327: The batch is full and BlockOnBatchFull is set to false.

Cause: An attempt was made to add a new operation to the batch when the batch was full and Block_On_Batch_Full is set to false.

Action: When Block_On_Batch_Full is set to false this exception will be thrown if an attempt is made to add a batch operation to a full batch. When Block_On_Batch_Full is set to true (the default) the caller's thread will block until the batch full condition is cleared and the operation is successfully added. The batch full condition will clear when pending batches are processed to the Oracle BAM Server freeing up space in the batch.
Level: 1

Type: ERROR

Impact: Configuration

BAM-01328: The field being added already exists in Data Object "{0}".

Cause: The field being added already exists in the Data Object.

Action: Check the Data Object schema, and if necessary, drop the existing field and then add it again.
Level: 1

Type: ERROR

Impact: Data

BAM-01329: The storage engine factory failed to start.

Cause: The Oracle BAM storage engine factory failed to start. The storage engine factory is needed to establish communication with the database.

Action: Check the log for more details on the cause of the failure.
Level: 1

Type: ERROR

Impact: Data

BAM-01330: The default storage engine has not been instantiated.

Cause: An attempt was made to use the default Oracle BAM storage engine, however, it has not been successfully instantiated.

Action: Check the log for more details on the cause of the failure to instantiate the default storage engine.
Level: 1

Type: ERROR

Impact: Data

BAM-01331: Unable to obtain database metadata for configured data source.

Cause: Oracle BAM failed to obtain database metadata for the configured data source. The database metadata is needed to establish communication with the configured database.

Action: Check the log for more details on the cause of the failure.
Level: 1

Type: ERROR

Impact: Data

BAM-01332: The configured data source specifies an unsupported database: {0}.

Cause: The data source configuration for Oracle BAM specifies a database that is not currently supported.

Action: Check the Oracle BAM documentation for details on supported databases.
Level: 1

Type: ERROR

Impact: Data

BAM-01333: Unable to instantiate a storage engine for the configured data source.

Cause: Oracle BAM was unable to instantiate a storage engine for the configured data source. The storage engine is needed to establish communication with the database.

Action: Check the log for more details on the cause of the failure.
Level: 1

Type: ERROR

Impact: Data

BAM-01334: Failed to find data source: {0}.

Cause: Oracle BAM failed to find the specified data source.

Action: Check that the data source is properly configured in the application server and that the correct data source name is being used.
Level: 1

Type: ERROR

Impact: Data

BAM-01390: Cannot delete a Data Object that is used in an Enterprise Message Source definition.

Cause: This Data Object is used in an Enterprise Message Source definition.

Action: Remove the Data Object reference from the Enterprise Message Source definition.
Level: 1

Type: ERROR

Impact: Data

BAM-01391: Cannot delete a field that is used in an Enterprise Message Source definition.

Cause: This field is referenced in an Enterprise Message Source definition Source to Data Object Field Mapping.

Action: Remove the field from the Enterprise Message Source definition Source to Data Object Field Mapping.
Level: 1

Type: ERROR

Impact: Data

BAM-01392: Cannot rename a field that is used in an Enterprise Message Source definition.

Cause: This field is referenced in an Enterprise Message Source definition Source to Data Object Field Mapping.

Action: Remove the field from the Enterprise Message Source definition Source to Data Object Field Mapping.
Level: 1

Type: ERROR

Impact: Data

BAM-01393: Cannot rename or move a Data Object that is used by an Enterprise Message Source definition.

Cause: This Data Object is used in an Enterprise Message Source definition.

Action: Remove the Data Object reference from the Enterprise Message Source definition.
Level: 1

Type: ERROR

Impact: Data

BAM-01500: No value specified for key column {0}.

Cause: A row was updated/upserted without key column values.

Action: Provide key column values in the update/upsert operation.
Level: 1

Type: ERROR

Impact: Data

BAM-01501: No key columns specified for update request.

Cause: A row was updated/upserted, but none of the columns were specified as keys.

Action: Specify some columns as keys in the operation.
Level: 1

Type: ERROR

Impact: Data

BAM-01502: No columns to be updated were specified for upsert request.

Cause: The list of columns to be changed were null in an upsert operation.

Action: Specify a list of columns that should be changed if the upsert evaluates to an update instead of an insert.
Level: 1

Type: ERROR

Impact: Data

BAM-01503: No value specified for update column {0}.

Cause: A row was upserted with a missing update column value.

Action: Provide key column values for all update columns specified in an upsert operation.
Level: 1

Type: ERROR

Impact: Data

BAM-01600: An aggregate expression is not allowed.

Cause: An aggregate expression was specified in a calculated column definition.

Action: Avoid specifying an aggregate expression in a calculated column.
Level: 1

Type: ERROR

Impact: Data

BAM-01601: Argument {1} in function {0} must be a Boolean value.

Cause: A non-Boolean operand was found in an IF function expression.

Action: Change the operand type to Boolean.
Level: 1

Type: ERROR

Impact: Programmatic

BAM-01602: Argument {1} in function {0} must be a datetime type value.

Cause: Non-datetime operands were specified for a datetime-related function expression.

Action: Provide the datetime type of operands in this expression.
Level: 1

Type: ERROR

Impact: Programmatic

BAM-01603: Argument {1} in function {0} must be an integer.

Cause: Integer type operands were expected in the function expression, but other types of operands were found.

Action: Provide integer type operands in the function expression.
Level: 1

Type: ERROR

Impact: Programmatic

BAM-01604: Argument {1} in function {0} must be numeric.

Cause: Numeric type operands were expected in the function expression, but other types of operands were found.

Action: Provide numeric type operands in the function expression.
Level: 1

Type: ERROR

Impact: Programmatic

BAM-01605: Argument {1} in function {0} must be a string.

Cause: String type operands were expected in the function expression, but other types of operands were found.

Action: Provide string type operands in the function expression.
Level: 1

Type: ERROR

Impact: Programmatic

BAM-01606: Cannot divide by zero.

Cause: Dividing by zero was attempted.

Action: Avoid dividing by zero.
Level: 1

Type: ERROR

Impact: Data

BAM-01607: The MOD operator can only be used with integers.

Cause: Non-integer operands were used in a MOD operation.

Action: Provide operands of type integer for the MOD operation.
Level: 1

Type: ERROR

Impact: Data

BAM-01608: invalid aggregate operand

Cause: Operands of type datetime were specified in the aggregate expression.

Action: Avoid using operands of type datetime.
Level: 1

Type: ERROR

Impact: Data

Cause: Constant operands were specified in the aggregate expression.

Action: Avoid using constant operands.

Cause: Aggregate operands were specified in the aggregate expression.

Action: Avoid nested aggregate expressions.

Cause: Non-numeric operands were found in AVG or SUM aggregates.

Action: Avoid using non-numeric operands in these aggregates.

BAM-01609: The function {0} requires {1} arguments.

Cause: An invalid number of arguments were found in the aggregate definition.

Action: Provide the correct number of arguments in the aggregate definition.
Level: 1

Type: ERROR

Impact: Programmatic

BAM-01610: invalid filter expression

Cause: Invalid operands were found in the filter expression.

Action: Provide the correct operands.
Level: 1

Type: ERROR

Impact: Data

BAM-01611: Math expression contains a non-numeric operand.

Cause: Non-numeric operands were found in math expressions (for example, ADD, SUB, and so on).

Action: Provide numeric operands in math expressions.
Level: 1

Type: ERROR

Impact: Data

BAM-01612: Return values differ in type.

Cause: The return values differed in type.

Action: Provide values of the same type.
Level: 1

Type: ERROR

Impact: Programmatic

BAM-01613: unknown expression type

Cause: An unknown expression type was found.

Action: Specify one of the valid expression types: MathExpression, FunctionExpression, CaseExpression, and so on.
Level: 1

Type: ERROR

Impact: Compliance

BAM-01614: The function {0} requires argument values of same data type.

Cause: The argument values differed in data type.

Action: Provide argument values of the same data type
Level: 1

Type: ERROR

Impact: Programmatic

BAM-01700: Active Data Cache exception: {0}

Cause: The Active Data Cache Servlet failed to register the Active Data Cache callback.

Action: Check the log for more details.
Level: 1

Type: ERROR

Impact: Process

Cause: The Active Data Cache Servlet failed in doGet().

Action: Check the log for more details.

BAM-01701: Value {0} specified for parameter {1} is unknown.

Cause: An invalid parameter, call, was found for doGet() in the ADC Servlet.

Action: The value must be one of the following: ping or config.
Level: 1

Type: ERROR

Impact: Programmatic

BAM-01702: Invalid request specified. Parameter {0} is missing.

Cause: No call parameter was found for doGet() in the ADC Servlet.

Action: Provide a call parameter.
Level: 1

Type: ERROR

Impact: Process

BAM-01800: ping failure

Cause: Ping failed.

Action: See the console output for more details.
Level: 1

Type: ERROR

Impact: Process

BAM-01801: Parameter {0} is not recognized.

Cause: An invalid parameter was found.

Action: Check the parameter.
Level: 1

Type: ERROR

Impact: Data

BAM-01802: Type {0} is not recognized.

Cause: An invalid type parameter was found.

Action: The type must be one of the following: network, storage, transaction, activeviewset, or staticviewset.
Level: 1

Type: ERROR

Impact: Data

BAM-01803: Parameter Dataobject requires an argument.

Cause: An invalid value was found for the Dataobject parameter.

Action: Provide a valid parameter value.
Level: 1

Type: ERROR

Impact: Programmatic

BAM-01804: Parameter domain requires an argument.

Cause: An invalid value was found for the domain parameter.

Action: Provide a valid parameter value.
Level: 1

Type: ERROR

Impact: Programmatic

BAM-01805: Parameter timeout requires an argument.

Cause: An invalid value was found for the timeout parameter.

Action: Provide a valid parameter value.
Level: 1

Type: ERROR

Impact: Programmatic

BAM-01806: Parameter type requires an argument.

Cause: An invalid value was found for the type parameter.

Action: Provide a valid parameter value.
Level: 1

Type: ERROR

Impact: Programmatic

BAM-01807: Timeout exceeded.

Cause: The Active Data Cache server failed to respond within a specified time interval.

Action: Check the status of the Active Data Cache server.
Level: 1

Type: ERROR

Impact: Process

BAM-02000: The report contains prompts or parameters.

Cause: PARAMETER was found in the filter value when the filter expression was built.

Action: Avoid using a parameter in the filter value.
Level: 1

Type: ERROR

Impact: Data

BAM-02001: invalid expression

Cause: An invalid expression was found.

Action: Check the syntax of the XML payload.
Level: 1

Type: ERROR

Impact: Data

BAM-02002: unrecognized constant expression: {0}

Cause: Failed to get constant expression from the given string.

Action: Correct the syntax of the constant expression.
Level: 1

Type: ERROR

Impact: Data

BAM-02200: Version to convert to is earlier than the version to convert from.

Cause: Version to convert to was earlier than the version to convert from.

Action: Verify the version numbers.
Level: 1

Type: ERROR

Impact: Upgrade

BAM-02201: Target version specified for conversion is unsupported.

Cause: Version to convert to was invalid.

Action: Verify the version number.
Level: 1

Type: ERROR

Impact: Upgrade

BAM-02202: Source version specified for conversion is unsupported.

Cause: Version to convert from was invalid.

Action: Verify the version number.
Level: 1

Type: ERROR

Impact: Upgrade

BAM-02300: Event engine cannot find matching external action entry.

Cause: A null pointer exception has been thrown.

Action: Verify that an external action entry was correctly configured.
Level: 1

Type: ERROR

Impact: Data

BAM-02301: At least one recipient is required, but none were found.

Cause: There were no recipients specified on either send-to list or Cc: list.

Action: Provide at least one recipient.
Level: 1

Type: ERROR

Impact: Data

BAM-02302: invalid rule: malformed action

Cause: Failed to parse or process the XML for actions.

Action: Check the log for details.
Level: 1

Type: ERROR

Impact: Data

Cause: Failed to append the action clauses.

Action: Check the log for details.

BAM-02303: invalid rule: malformed condition

Cause: The operator count was not correct.

Action: Check the log for details.
Level: 1

Type: ERROR

Impact: Data

Cause: The bracket count was not correct.

Action: Check the log for details.

Cause: Failed to load the condition clauses.

Action: Check the log for details.

Cause: Failed to retrieve the content of the expected XML element.

Action: Check the log for details.

BAM-02304: invalid rule: malformed action constraint

Cause: Failed to append the constraint clause.

Action: Check the log for details.
Level: 1

Type: ERROR

Impact: Data

Cause: Failed to load the constraint clause.

Action: Check the log for details.

BAM-02305: invalid rule: malformed escalation clause

Cause: Failed to parse or process the escalation clause.

Action: Check the log for details.
Level: 1

Type: ERROR

Impact: Data

BAM-02306: invalid rule: malformed event

Cause: An incomplete escalation component was found.

Action: Check the log for details.
Level: 1

Type: ERROR

Impact: Data

Cause: An incomplete event component was found.

Action: Check the log for details.

Cause: An incomplete condition was found.

Action: Check the log for details.

Cause: Failed to parse the event clause.

Action: Check the log for details.

BAM-02307: invalid rule: malformed using clause

Cause: Failed to parse the import clause.

Action: Check the log for details.
Level: 1

Type: ERROR

Impact: Data

BAM-02308: Event Engine must run with an account that has the Oracle BAM Administrator role.

Cause: An attempt was made to run the Event Engine with an account that did not have the Oracle BAM Administrator role.

Action: Grant the user sufficient privileges before retrying this operation.
Level: 1

Type: ERROR

Impact: Security

BAM-02309: Unable to load rule {0}. Verify that the rule is based on the event when this rule is launched.

Cause: The rule manager failed to retrieve the rule with the specified ID.

Action: Verify the alert name.
Level: 1

Type: ERROR

Impact: Data

BAM-02310: Event Engine failure. Rule failed to fire.

Cause: A rule failed to fire by either its ID or name.

Action: Check the log for details.
Level: 1

Type: ERROR

Impact: Process

BAM-02311: Event Engine failure. Cannot deliver e-mail.

Cause: The Event Engine failed to send e-mail.

Action: Check the Event Engine log for details.
Level: 1

Type: ERROR

Impact: Process

BAM-02312: Event rule identifier duplicated.

Cause: The specified event rule identifier already existed in the Event Engine.

Action: Change the event rule identifier.
Level: 1

Type: ERROR

Impact: Data

BAM-02313: Event rule not found.

Cause: The event rule ID was less than or equal to zero.

Action: Provide a valid event rule ID.
Level: 1

Type: ERROR

Impact: Data

Cause: The event rule with the specified ID was not found in the Event Engine.

Action: Verify the correct event rule ID.

Cause: Failed to retrieve parameters using specified event rule ID.

Action: Verify the correct event rule ID.

Cause: Failed to retrieve a clause function using the specified event rule ID.

Action: Verify the correct event rule ID.

BAM-02314: The specified rule is not based on the event when this rule is launched.

Cause: The specified rule cannot be fired because it is not based on the event when this rule is launched.

Action: Build the rule to be a manual type.
Level: 1

Type: ERROR

Impact: Data

BAM-02315: Event satellite could not load clause.

Cause: Failed to add a clause to a monitor list.

Action: Check the log for more details.
Level: 1

Type: ERROR

Impact: Data

BAM-02316: Event satellite does not support this function.

Cause: An unknown function type to Date satellite was found.

Action: The function must be one of the following: On or OnEvery.
Level: 1

Type: ERROR

Impact: Data

Cause: An unknown function type to Manual satellite was found.

Action: The function must be Fire.

Cause: An unknown function type to Time satellite was found.

Action: The function must be one of the following: At, In, or AtEvery.

BAM-02317: Event satellite not found.

Cause: An unknown event satellite was found.

Action: The event satellite must be one of the following: time, date, viewset, or manual.
Level: 1

Type: ERROR

Impact: Data

BAM-02318: Event satellite indicated an unexpected action.

Cause: An invalid action was found.

Action: The action must be one of the following: Add, Delete, or Modify.
Level: 1

Type: ERROR

Impact: Data

BAM-02319: Unable to connect to the Oracle BAM Event Engine.

Cause: Failed to send mail.

Action: Contact the system administrator if the error persists.
Level: 1

Type: ERROR

Impact: Process

Cause: Failed to fire rule.

Action: Contact the system administrator if the error persists.

BAM-02400: The All value and a match cannot be specified at the same time.

Cause: Both All and a match were specified.

Action: Specify only one of them.
Level: 1

Type: ERROR

Impact: Compliance

BAM-02401: The All value and a name cannot be specified at the same time.

Cause: Both All and a name were specified.

Action: Specify only one of them.
Level: 1

Type: ERROR

Impact: Compliance

BAM-02402: The All value and a regular expression cannot be specified at the same time.

Cause: Both All and a regular expression were specified.

Action: Specify only one of them.
Level: 1

Type: ERROR

Impact: Compliance

BAM-02403: premature end of command file

Cause: The end of command file was found prematurely.

Action: Check the syntax of the command file.
Level: 1

Type: ERROR

Impact: Data

BAM-02404: Specified file is not a valid ICommand command file.

Cause: A file with invalid contents was found.

Action: Check the syntax of the command file.
Level: 1

Type: ERROR

Impact: Files

BAM-02405: Extra arguments present with CmdFile.

Cause: Extra arguments were present with CmdFile.

Action: Remove the extra arguments.
Level: 1

Type: ERROR

Impact: Data

BAM-02406: Either Cmd or CmdFile argument must be present.

Cause: Neither Cmd nor CmdFile was present.

Action: Provide one of them.
Level: 1

Type: ERROR

Impact: Compliance

BAM-02407: The Cmd and CmdFile arguments cannot be present in the same command.

Cause: Both Cmd and CmdFile were found in the command.

Action: Provide only one of them.
Level: 1

Type: ERROR

Impact: Compliance

BAM-02408: ICommand authentication failure. Unable to connect as user {0}.

Cause: Failed to create a Context object using the specified credentials.

Action: Verify the credentials.
Level: 1

Type: ERROR

Impact: Security

BAM-02409: There is no data object named {0}.

Cause: The specified data object was not found.

Action: Verify the data object name.
Level: 1

Type: ERROR

Impact: Data

BAM-02410: There is no distribution list named {0}.

Cause: The specified distribution list was not found.

Action: Verify the correct distribution list name.
Level: 1

Type: ERROR

Impact: Data

BAM-02411: Too many {0} parameters.

Cause: A parameter was specified more than once.

Action: Remove the duplicate parameters.
Level: 1

Type: ERROR

Impact: Compliance

BAM-02412: There is no external data source named {0}.

Cause: The specified external data source was not found.

Action: Verify the correct external data source name.
Level: 1

Type: ERROR

Impact: Data

BAM-02413: There is no external data source type named {0}.

Cause: The specified external data source type was not found.

Action: Verify the correct external data source type name.
Level: 1

Type: ERROR

Impact: Data

BAM-02414: There is no enterprise message source named {0}.

Cause: The specified enterprise message source was not found.

Action: Verify the correct enterprise message source name.
Level: 1

Type: ERROR

Impact: Data

BAM-02415: There is no enterprise message source type named {0}.

Cause: The specified enterprise message source type was not found.

Action: Verify the correct enterprise message source type name.
Level: 1

Type: ERROR

Impact: Data

BAM-02416: There is no folder named {0}.

Cause: The specified folder was not found.

Action: Verify the correct folder name.
Level: 1

Type: ERROR

Impact: Data

BAM-02417: The Inline parameter cannot be set to 1 if the File parameter is also specified.

Cause: The Inline parameter was set to 1, and the File parameter was also specified in the command arguments.

Action: Provide only one of them.
Level: 1

Type: ERROR

Impact: Compliance

BAM-02418: The Inline parameter can only be set to 1 from within a command file.

Cause: The Inline parameter was used from the command-line.

Action: Specify the Inline parameter from a command file only.
Level: 1

Type: ERROR

Impact: Compliance

BAM-02419: The Inline parameter can only be set to 1 if a log file is also specified.

Cause: The Inline parameter was set to 1 when there was no log file specified.

Action: Specify a log file when using the Inline parameter.
Level: 1

Type: ERROR

Impact: Compliance

BAM-02420: invalid command: {0}

Cause: An unrecognized command name was found.

Action: Use one of the following commands: export, import, delete, rename, or clear.
Level: 1

Type: ERROR

Impact: Compliance

BAM-02421: unrecognized parameter: {0}

Cause: An invalid Clear command parameter was found.

Action: Provide one of the following parameters: type or name.
Level: 1

Type: ERROR

Impact: Compliance

Cause: An invalid Delete command parameter was found.

Action: Provide one of the following parameters: type, all, systemobjects, name, match, regex.

Cause: An invalid Rename command parameter was found.

Action: Provide one of the following parameters: type, name, newname.

Cause: An invalid command-line parameter was found.

Action: Provide the following parameter: continueonerror.

Cause: An invalid command-line parameter was found. A dash (-) was found without a name.

Action: Provide the parameter name behind the dash.

Cause: An invalid command-line parameter was found. Only a user name or password was found.

Action: Provide both the user name and the password in the command arguments.

BAM-02422: invalid object type: {0}

Cause: An invalid Type parameter for the Delete or Export command was found.

Action: Provide one of the following parameters: dataobject, report, ems, emstype, securityfilters, rule, folder, role, user, distributionlist, plan, eds, edstype, or all.
Level: 1

Type: ERROR

Impact: Data

Cause: An invalid Type parameter for the Rename command was found.

Action: Provide one of the following parameters: dataobject, report, ems, emstype, folder, role, user, distributionlist, plan, rule, eds, or edstype.

BAM-02423: The Dependencies parameter is invalid for Type {0}.

Cause: The Dependencies parameter was provided with an invalid Type parameter.

Action: Provide one of the following types: dataobject, report, or all.
Level: 1

Type: ERROR

Impact: Compliance

BAM-02424: invalid log mode: {0}

Cause: An invalid Logmode parameter was found.

Action: Provide one of the following parameters: overwrite or append.
Level: 1

Type: ERROR

Impact: Data

BAM-02425: A match and a regular expression cannot be specified at the same time.

Cause: Both a match and a regular expression were specified in the command line.

Action: Provide only one of them.
Level: 1

Type: ERROR

Impact: Compliance

BAM-02426: missing file name

Cause: A File parameter was not found for the export command when neither Preview nor Inline parameters were found.

Action: Add a File parameter.
Level: 1

Type: ERROR

Impact: Compliance

Cause: A File parameter was missing when it was not in Inline mode.

Action: Add a File parameter.

BAM-02427: The Name parameter must be specified.

Cause: The Name parameter was not found.

Action: Provide a Name parameter.
Level: 1

Type: ERROR

Impact: Compliance

BAM-02428: A name and a match cannot be specified together.

Cause: Both a name and a match were specified.

Action: Provide only one of them.
Level: 1

Type: ERROR

Impact: Compliance

BAM-02429: A name and a regular expression cannot be specified together.

Cause: Both a name and a regular expression were specified.

Action: Provide only one of them.
Level: 1

Type: ERROR

Impact: Compliance

BAM-02430: invalid new name for data object

Cause: A path was specified as the new name of a data object.

Action: Provide a valid name.
Level: 1

Type: ERROR

Impact: Data

BAM-02431: New name must be specified.

Cause: The Newname parameter was missing in the Rename command.

Action: Provide the Newname parameter.
Level: 1

Type: ERROR

Impact: Compliance

BAM-02432: invalid new name for report

Cause: The new name specified was a path.

Action: Provide a new name without path.
Level: 1

Type: ERROR

Impact: Data

BAM-02433: invalid object type: {0}

Cause: An invalid Type parameter was found.

Action: Provide one of the following parameters: dataobject, folder, role, or distributionlist.
Level: 1

Type: ERROR

Impact: Data

BAM-02434: Current user does not have security credentials to perform this operation.

Cause: A user who performed the operation did not have sufficient privileges.

Action: Grant the user sufficient privileges before retrying this operation.
Level: 1

Type: ERROR

Impact: Security

BAM-02435: There is no role named {0}.

Cause: The specified role was not found.

Action: Verify the correct role name.
Level: 1

Type: ERROR

Impact: Data

BAM-02436: There is no report named {0}.

Cause: The specified report was not found.

Action: Verify the correct report name.
Level: 1

Type: ERROR

Impact: Data

BAM-02437: There is no rule named {0}.

Cause: The specified rule was not found.

Action: Verify the correct rule name.
Level: 1

Type: ERROR

Impact: Data

BAM-02438: There is no user named {0}.

Cause: The specified user was not found.

Action: Verify the correct user name.
Level: 1

Type: ERROR

Impact: Data

BAM-02439: ICommand is unable to connect to the Oracle BAM server. Check the configured host name and port number.

Cause: The specified host name or port number is incorrect.

Action: Verify the correct host name or port number.
Level: 1

Type: ERROR

Impact: Data

BAM-02440: ICommand is unable to connect to the Oracle BAM server because user credentials (username/password) have not been specified.

Cause: The user credentials (username/password) required to connect to the Oracle BAM server were not specified.

Action: Provide user credentials using the -username command-line parameter. ICommand will prompt for the password. If running ICommand from a script then provide the user credentials in ICommand configuration file.
Level: 1

Type: ERROR

Impact: Data

BAM-02441: Parameter: {0} must be preceded by a hyphen (-).

Cause: Command parameter was found without hyphen (-).

Action: Provide parameter with hyphen (-).
Level: 1

Type: ERROR

Impact: Compliance

BAM-02442: There is no data object matching the given regular expression "{0}."

Cause: There is no data object matching the regular expression.

Action: Verify the regular expression given.
Level: 1

Type: ERROR

Impact: Data

BAM-02443: There is no security filter matching the given regular expression "{0}."

Cause: There is no security filter matching the regular expression.

Action: Verify the regular expression given.
Level: 1

Type: ERROR

Impact: Data

BAM-02444: There is no enterprise message source matching the given regular expression "{0}."

Cause: There is no enterprise message source matching the regular expression.

Action: Verify the regular expression given.
Level: 1

Type: ERROR

Impact: Data

BAM-02445: There is no report matching the given regular expression "{0}."

Cause: There is no report matching the regular expression.

Action: Verify the regular expression given.
Level: 1

Type: ERROR

Impact: Data

BAM-02446: There is no rule matching the given regular expression "{0}."

Cause: There is no rule matching the regular expression.

Action: Verify the regular expression given.
Level: 1

Type: ERROR

Impact: Data

BAM-02447: There is no folder matching the given regular expression "{0}."

Cause: There is no folder matching the regular expression.

Action: Verify the regular expression given.
Level: 1

Type: ERROR

Impact: Data

BAM-02448: There is no distribution list matching the given regular expression "{0}."

Cause: There is no distribution list matching the regular expression.

Action: Verify the regular expression given.
Level: 1

Type: ERROR

Impact: Data

BAM-02449: There is no external data source matching the given regular expression "{0}."

Cause: There is no external data source matching the regular expression.

Action: Verify the regular expression given.
Level: 1

Type: ERROR

Impact: Data

BAM-02450: There is syntax error in the given regular expression "{0}" at or near index {1}.

Cause: There is syntax error in the given regular expression.

Action: Verify the regular expression given.
Level: 1

Type: ERROR

Impact: Data

BAM-02500: External Data Source is not available.

Cause: The specified External Data Source does not exist.

Action: Verify the External Data Source ID.
Level: 1

Type: ERROR

Impact: Data

BAM-02501: There is no data object named {0}.

Cause: The specified data object was not found.

Action: Verify the name of the data object in the Oracle BAM Server.
Level: 1

Type: ERROR

Impact: Data

BAM-02502: There is no distribution list named {0}.

Cause: The Specified distribution list was not found.

Action: Verify the name of the distribution list in the Oracle BAM Server.
Level: 1

Type: ERROR

Impact: Data

BAM-02503: There is no external data source named {0}.

Cause: Failed to create an external data source with the specified name.

Action: Verify the name of the external data source in the Oracle BAM Server.
Level: 1

Type: ERROR

Impact: Data

BAM-02504: There is no external data source type named {0}.

Cause: The specified external data source type was not found.

Action: Verify external data source type name defined in the Oracle BAM Server.
Level: 1

Type: ERROR

Impact: Data

BAM-02505: There is no enterprise message source named {0}.

Cause: The specified enterprise message source was not found.

Action: Verify the enterprise message source name defined in the Oracle BAM Server.
Level: 1

Type: ERROR

Impact: Data

BAM-02506: There is no enterprise message source type named {0}.

Cause: The specified enterprise message source type was not found.

Action: Verify the enterprise message source type name defined in the Oracle BAM Server.
Level: 1

Type: ERROR

Impact: Data

BAM-02507: There is no folder named {0}.

Cause: The specified folder was not found.

Action: Verify the folder name defined in the Oracle BAM Server.
Level: 1

Type: ERROR

Impact: Data

BAM-02508: unsupported or unrecognized item type

Cause: An exported item type was not recognized.

Action: Provide one of the following types: DataObject, Dataset, EntMsgSource, EMS, Report, SecurityFilters, Rule, Folder, DistributionList, ExternalDataSource, or EDS.
Level: 1

Type: ERROR

Impact: Data

BAM-02509: Contents and Layout cannot be disabled at the same time.

Cause: A data object cannot be exported without both Contents and Layout.

Action: Export either Contents or Layout.
Level: 1

Type: ERROR

Impact: Compliance

Cause: A role cannot be exported without both Contents and Layout.

Action: Export either Contents or Layout.

BAM-02510: data object ID {0} not found

Cause: The specified data object was not found.

Action: Verify either the data object name or data object definitions in the Oracle BAM Server.
Level: 1

Type: ERROR

Impact: Data

BAM-02511: There is no report named {0}.

Cause: Failed to load the specified report.

Action: Verify either the report name or report definitions in the Oracle BAM Server.
Level: 1

Type: ERROR

Impact: Data

BAM-02512: There is no role named {0}.

Cause: Failed to load the specified role.

Action: Verify either the role name or role definitions in the Oracle BAM Server.
Level: 1

Type: ERROR

Impact: Data

BAM-02513: The data object {0}, referenced by this rule, does not exist.

Cause: The data object referenced by the rule was not found.

Action: Verify the data object name in the Oracle BAM Server.
Level: 1

Type: ERROR

Impact: Data

BAM-02514: There is no rule named {0}.

Cause: Failed to load the specified rule.

Action: Verify the rule name in the Oracle BAM Server.
Level: 1

Type: ERROR

Impact: Data

BAM-02515: There is no user named {0}.

Cause: Failed to create the specified user.

Action: Verify the user name or the user list in the Oracle BAM Server.
Level: 1

Type: ERROR

Impact: Data

BAM-02516: The report assigned to this user's home page is missing or invalid.

Cause: Failed to load the report assigned to the user's home page.

Action: Check the report list in the Oracle BAM Server.
Level: 1

Type: ERROR

Impact: Process

BAM-02517: invalid mode: {0}

Cause: An invalid data object import mode was found.

Action: Provide one of the following modes: preserveid, update, or updateonly.
Level: 1

Type: ERROR

Impact: Data

Cause: An invalid distribution list import mode was found.

Action: Provide one of the following modes: overwrite, append, rename, or error.

Cause: An invalid External Data Source import mode was found.

Action: Provide one of the following modes: overwrite, rename, or error.

Cause: An invalid enterprise message source import mode was found.

Action: Provide one of the following modes: overwrite, rename, or error.

Cause: An invalid folder import mode was found.

Action: Provide one of the following modes: overwrite, rename, or error.

Cause: An invalid report import mode was found.

Action: Provide one of the following modes: overwrite, rename, or error.

Cause: An invalid Security Filter import mode was found.

Action: Provide the overwrite mode.

Cause: An invalid user import mode was found.

Action: Provide one of the following modes: overwrite, rename, or error.

BAM-02518: unrecognized parameter: {0}

Cause: An invalid data object export parameter was found.

Action: Provide one of the following parameters: layout, contents, or permissions.
Level: 1

Type: ERROR

Impact: Data

Cause: An invalid data object import parameter was found.

Action: Provide one of the following parameters: null, now, or value.

Cause: An invalid distribution list export parameter was found.

Action: No parameters are allowed.

Cause: An invalid distribution list import parameter was found.

Action: Provide the following parameter: mode.

Cause: An invalid external data source export parameter was found.

Action: No parameters are allowed.

Cause: An invalid external data source import parameter was found.

Action: Provide the following parameter: mode.

Cause: An invalid enterprise message source export parameter was found.

Action: No parameters are allowed.

Cause: An invalid enterprise message source import parameter was found.

Action: Provide the following parameter: mode.

Cause: An invalid folder export parameter was found.

Action: Provide one of the following parameters: permissions or owner.

Cause: An invalid folder import parameter was found.

Action: Provide one of the following parameters: mode or preserveowner.

Cause: An invalid report export parameter was found.

Action: Provide the following parameter: owner.

Cause: An invalid report import parameter was found.

Action: Provide one of the following parameters: mode or preserveowner.

Cause: An invalid role export parameter was found.

Action: Provide one of the following parameters: privileges or members.

Cause: An invalid role import parameter was found.

Action: Provide the following parameter: mode.

Cause: An invalid rule export parameter was found.

Action: Provide one of the following parameters: owner or planmonitorservicename.

Cause: An invalid rule import parameter was found.

Action: Provide one of the following parameters: preserveowner or planmonitorservicename.

Cause: An invalid Security Filter export parameter was found.

Action: No parameters are allowed.

Cause: An invalid Security Filter import parameter was found.

Action: Provide the following parameter: mode.

Cause: An invalid user export parameter was found.

Action: No parameters are allowed.

Cause: Invalid user import parameter was found.

Action: Provide the following parameter: mode.

BAM-02519: invalid column type

Cause: An invalid column type was found.

Action: A column type must be one of the following types: string, integer, auto-incr-integer, float, decimal, datetime, timestamp, Boolean, iterid, lookup, or calculated.
Level: 1

Type: ERROR

Impact: Data

BAM-02520: Contents end tag is missing or extra elements are present.

Cause: A Contents end tag was missing or extra elements were present.

Action: Check the syntax of the XML payload.
Level: 1

Type: ERROR

Impact: Data

BAM-02521: Error while creating data object.

Cause: Failed to create the data object in the importer.

Action: Check the log for more details.
Level: 1

Type: ERROR

Impact: Process

BAM-02522: The data object was created successfully, but an error occurred while creating the indexes.

Cause: Failed to create the indexes.

Action: Check the log for more details.
Level: 1

Type: ERROR

Impact: Process

BAM-02523: DataObject end tag missing or extra elements present

Cause: A DataObject end tag was missing or extra elements were present.

Action: Check the syntax of the XML payload.
Level: 1

Type: ERROR

Impact: Data

BAM-02524: Error while editing data object layout.

Cause: An exception was thrown while editing a data object layout.

Action: Check the log for more details.
Level: 1

Type: ERROR

Impact: Process

BAM-02525: The data object layout was edited successfully, but an error occurred while editing the indexes.

Cause: Failed to edit the indexes.

Action: Check the log for more details.
Level: 1

Type: ERROR

Impact: Process

BAM-02526: Error while creating folder.

Cause: Failed to create the folder.

Action: Check the log for more details.
Level: 1

Type: ERROR

Impact: Process

BAM-02527: A data object already exists with ID {0}.

Cause: A data object with same ID was already created.

Action: Choose a unique ID.
Level: 1

Type: ERROR

Impact: Data

BAM-02528: Column ID {0} in the Contents section of the import XML does not match any Column ID in the data object.

Cause: An invalid column ID was found.

Action: Verify the correct column ID.
Level: 1

Type: ERROR

Impact: Data

BAM-02529: The external data source {0} does not exist.

Cause: The specified external data source was not found.

Action: Verify the correct external data source name.
Level: 1

Type: ERROR

Impact: Data

BAM-02530: invalid data object name: {0}

Cause: A maximum length limit was violated.

Action: Limit the length of the data object name to 30 characters.
Level: 1

Type: ERROR

Impact: Data

Cause: The first character in the data object name was not an alphabetical character.

Action: Start the name with an alphabetical character.

Cause: The first character was not an English letter or an underscore.

Action: Start the data object name with an English letter or an underscore.

Cause: The remaining characters were not English letters, digits, or underscores.

Action: Choose English letters, digits, or underscores in the remaining characters.

Cause: The column ID was either null or empty.

Action: Enter a valid column ID.

BAM-02531: invalid row ID in import file: {0}

Cause: The row ID was not a valid long-typed data.

Action: Provide a valid row ID.
Level: 1

Type: ERROR

Impact: Data

BAM-02532: improper XML in Layout element

Cause: A syntax error was found in the Layout tag.

Action: Provide valid XML payload.
Level: 1

Type: ERROR

Impact: Data

BAM-02533: The data object {0} is marked as external, but the ExternalDataSource attribute is missing.

Cause: The ExternalDataSource attribute was missing.

Action: Provide the ExternalDataSource attribute.
Level: 1

Type: ERROR

Impact: Compliance

BAM-02534: The data object {0} is marked as external, but the ExternalName attribute is missing.

Cause: The ExternalName attribute was missing.

Action: Provide the ExternalName attribute.
Level: 1

Type: ERROR

Impact: Compliance

BAM-02535: The data object {0} does not exist, or its layout is being edited, and Layout tag is missing or out of order.

Cause: A data object layout is being edited and the Layout tag is missing or out of order.

Action: Provide the Layout tag in the correct place.
Level: 1

Type: ERROR

Impact: Data

Cause: An update of a data object definition is executed, but the data object does not exist.

Action: Do a create operation instead.

BAM-02536: The data object name is missing or invalid.

Cause: A data object name was missing or invalid.

Action: Provide a valid data object name.
Level: 1

Type: ERROR

Impact: Data

BAM-02537: Current user does not have security credential to perform this operation.

Cause: Failed to create the data object.

Action: Grant this user sufficient privileges to create data objects.
Level: 1

Type: ERROR

Impact: Security

BAM-02538: Unable to set column with ID {0} to value {1}.

Cause: Failed to set the value in the specified column.

Action: Check the log for more details.
Level: 1

Type: ERROR

Impact: Data

BAM-02539: parameter {0}: column {1}: Lookup and calculated columns cannot be set.

Cause: The values of the lookup and calculated columns were overridden.

Action: Avoid overriding the lookup and calculated column values.
Level: 1

Type: ERROR

Impact: Compliance

BAM-02540: improper format for parameter {0}: {1}

Cause: An invalid parameter value for Setcol was found.

Action: Provide a valid value with lhs and rhs separated by a slash (/).
Level: 1

Type: ERROR

Impact: Compliance

BAM-02541: import internal error: unknown override type {0}

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Data

BAM-02542: parameter {0}: There is no column named {1} in data object {2}.

Cause: The specified column was not found in the Setcol parameter.

Action: Verify the correct column name.
Level: 1

Type: ERROR

Impact: Data

BAM-02543: parameter {0}: Column {1} is not nullable; null cannot be used.

Cause: A non-nullable column was set to null.

Action: Provide a valid value for the column.
Level: 1

Type: ERROR

Impact: Compliance

BAM-02544: Parameter {0}: column {1} is not of type datetime, timestamp or string; the Now function cannot be used.

Cause: A column was set to Now.

Action: Verify that the column is one of the following types: datetime, timestamp, or string.
Level: 1

Type: ERROR

Impact: Data

BAM-02545: Invalid value type {0} for parameter {1}. The type must be null, now, or value:.

Cause: The right-hand side was set to a value not belonging to one of the following types: null, now, or value:.

Action: Provide the null, now, or value: type on the right-hand side.
Level: 1

Type: ERROR

Impact: Data

BAM-02546: unsupported data object version

Cause: An invalid version of data object exporter was found.

Action: An acceptable data object Exporter version is: 0, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, or 14.
Level: 1

Type: ERROR

Impact: Compliance

BAM-02547: The Delay value must be an integer greater than zero.

Cause: An integer less than or equal to zero was found.

Action: Provide a valid Delay value.
Level: 1

Type: ERROR

Impact: Data

BAM-02548: The distribution list {0} already exists.

Cause: The specified distribution list was already created and the import mode is Error.

Action: Either change the import mode or change the distribution list name.
Level: 1

Type: ERROR

Impact: Data

BAM-02549: Distribution list name is missing or invalid.

Cause: The distribution list name was missing or invalid.

Action: Provide a valid distribution list name.
Level: 1

Type: ERROR

Impact: Data

BAM-02550: There is no user named {0}.

Cause: The specified user was not found.

Action: Verify the correct user name.
Level: 1

Type: ERROR

Impact: Data

BAM-02551: An external data source {0} already exists.

Cause: The specified external data source was already created and the import mode was Error.

Action: Either change the import mode or change the external data source name.
Level: 1

Type: ERROR

Impact: Data

BAM-02552: unsupported external data source version

Cause: An invalid external data source version was found.

Action: The acceptable version is 1.
Level: 1

Type: ERROR

Impact: Compliance

BAM-02553: An external data source type {0} already exists.

Cause: The specified external data source type was already created and the import mode was Error.

Action: Either change the import mode or change the external data source type name.
Level: 1

Type: ERROR

Impact: Data

BAM-02554: The enterprise message source already exists.

Cause: The specified enterprise message source was already created and the import mode was Error.

Action: Either change the import mode or change the enterprise message source name.
Level: 1

Type: ERROR

Impact: Data

BAM-02555: unsupported enterprise message source version

Cause: An invalid enterprise message source version was found.

Action: The supported version is 2.
Level: 1

Type: ERROR

Impact: Compliance

BAM-02556: premature EOF in import file

Cause: More XML payload was expected, but the end of file was found.

Action: Check the syntax of the XML payload.
Level: 1

Type: ERROR

Impact: Data

BAM-02557: Import failed at or near line {0}.

Cause: The import operation failed.

Action: Check the log for more details.
Level: 1

Type: ERROR

Impact: Data

BAM-02558: Import failed at or near line {0} of file {1}.

Cause: The import operation failed.

Action: Check the log for more details.
Level: 1

Type: ERROR

Impact: Files

BAM-02559: The folder {0} already exists.

Cause: The specified folder was already created and the import mode was Error.

Action: Either change the import mode or change the folder name.
Level: 1

Type: ERROR

Impact: Data

BAM-02560: The folder owner is missing or invalid.

Cause: The folder had no Owner and the user specified the Preserveowner option in the import command.

Action: Do not use the Preserveowner option on a folder with no owner.
Level: 1

Type: ERROR

Impact: Data

BAM-02561: Unrecognized item type in import file {0}.

Cause: An unrecognized item type was found.

Action: Provide one of the following item types: DataObject, EDS, EDSType, Report, EMS, EMSType, SecurityFilters, Rule, Folder, or DistributionList.
Level: 1

Type: ERROR

Impact: Data

BAM-02562: The data object {0} was not found.

Cause: Could not retrieve the data object ID with the specified name.

Action: Verify the correct data object name.
Level: 1

Type: ERROR

Impact: Data

BAM-02563: The report {0} already exists.

Cause: A report with this name was already created and the import mode was Error.

Action: Either check the name or change the import mode.
Level: 1

Type: ERROR

Impact: Data

BAM-02564: improper report content in XML

Cause: No Contents section was available to import from the XML payload.

Action: Add a Contents section to the XML payload.
Level: 1

Type: ERROR

Impact: Data

BAM-02565: The report name is missing or invalid.

Cause: No Name attribute was specified for the report.

Action: Provide a Name attribute.
Level: 1

Type: ERROR

Impact: Data

Cause: The report name was invalid.

Action: Verify the correct report name.

BAM-02566: The report owner is missing or invalid.

Cause: There was no Owner attribute specified, and the Preserveowner parameter was set.

Action: Either add the Owner attribute or remove the Preserveowner parameter.
Level: 1

Type: ERROR

Impact: Data

BAM-02567: Role {0} already exists.

Cause: The specified role was already created, and the import mode was Error.

Action: Either change the import mode or change the name.
Level: 1

Type: ERROR

Impact: Data

BAM-02568: This rule contains a reference to a data object that is missing or invalid.

Cause: The data object referenced from the rule was not found.

Action: Verify the correct data object name.
Level: 1

Type: ERROR

Impact: Data

BAM-02569: This rule contains a reference to a distribution list that is missing or invalid.

Cause: The distribution list referenced by the rule was not found.

Action: Verify the correct distribution list name.
Level: 1

Type: ERROR

Impact: Data

BAM-02570: There is already a rule named {0}.

Cause: The specified rule was already created.

Action: Verify the correct rule name.
Level: 1

Type: ERROR

Impact: Data

BAM-02571: Rule content is missing or invalid.

Cause: No Contents section was specified in the rule.

Action: Provide a Contents section in the XML payload.
Level: 1

Type: ERROR

Impact: Compliance

BAM-02572: The rule ID is missing or invalid.

Cause: No ID attribute was found in the rule definition.

Action: Provide an ID attribute.
Level: 1

Type: ERROR

Impact: Data

Cause: The specified ID attribute was an empty string.

Action: Provide a valid ID attribute.

BAM-02573: The rule name is missing or invalid.

Cause: No ID attribute was found.

Action: Provide a Name attribute.
Level: 1

Type: ERROR

Impact: Data

Cause: The specified ID attribute was an empty string.

Action: Provide a valid Name attribute.

BAM-02574: The rule owner is missing or invalid.

Cause: There was no Owner attribute specified and the Preserveowner parameter was set.

Action: Either add an Owner attribute or remove the Preserveowner parameter.
Level: 1

Type: ERROR

Impact: Data

BAM-02575: Package ID is missing or invalid.

Cause: There was no PackageID attribute specified, and the Preserveowner parameter was set.

Action: Either add a PackageID attribute or remove the Preserveowner parameter.
Level: 1

Type: ERROR

Impact: Data

BAM-02576: The report {0}, required by this alert, does not exist.

Cause: The specified report was not found.

Action: Verify the correct report name.
Level: 1

Type: ERROR

Impact: Data

BAM-02577: The rule contains a reference to a rule that is missing or invalid.

Cause: The rule referenced was not found.

Action: Verify the correct rule name.
Level: 1

Type: ERROR

Impact: Data

BAM-02578: The rule contains a reference to a user that is missing or invalid.

Cause: The user referenced was not found.

Action: Verify the correct user name.
Level: 1

Type: ERROR

Impact: Data

BAM-02579: A security filter named {0} already exists.

Cause: The specified security filter was already created, and the mode was not Overwrite.

Action: Either change the security filter name or change the mode.
Level: 1

Type: ERROR

Impact: Data

BAM-02580: There is no data object named {0}.

Cause: No DataObjectName attribute was specified.

Action: Provide a DataObjectName attribute.
Level: 1

Type: ERROR

Impact: Data

Cause: The DataObjectName attribute specified was an empty string.

Action: Provide a valid DataObjectName attribute.

BAM-02581: Security filter XML has no data object name.

Cause: Security filter XML has no data object name.

Action: Verify the Security filter XML for proper data object name.
Level: 1

Type: ERROR

Impact: Data

BAM-02582: There is no data object named {0} in path {1}.

Cause: No DataObjectName attribute was specified.

Action: Provide a DataObjectName attribute.
Level: 1

Type: ERROR

Impact: Data

Cause: The DataObjectName attribute specified was an empty string.

Action: Provide a valid DataObjectName attribute.

BAM-02583: improper security filter XML

Cause: The SecurityFilters element end-tag was expected, but it was not found.

Action: Check the syntax of the XML payload.
Level: 1

Type: ERROR

Impact: Data

BAM-02584: improper import file

Cause: The specified root element was invalid.

Action: The root element must be one of the following: OracleBAMExport, PeopleSoftRTSExport, IstanteExport, or IterationExport.
Level: 1

Type: ERROR

Impact: Files

BAM-02585: User {0} already exists.

Cause: The specified user was already created, and the import mode was Error.

Action: Either change the mode or change the name.
Level: 1

Type: ERROR

Impact: Data

BAM-02586: missing or invalid user name

Cause: No Name attribute was specified.

Action: Provide a Name attribute.
Level: 1

Type: ERROR

Impact: Data

Cause: The Name attribute specified was an empty string.

Action: Provide a valid Name attribute.

BAM-02587: unsupported import file version

Cause: No Version attribute was found.

Action: Provide a Version attribute.
Level: 1

Type: ERROR

Impact: Upgrade

Cause: Version number in MajorVersion.MinorVersion format was expected.

Action: Provide a valid Version attribute.

BAM-02588: The report ID is missing or invalid.

Cause: No ID attribute was found.

Action: Provide ID attribute.
Level: 1

Type: ERROR

Impact: Data

BAM-02589: The report with ID {0} already exists.

Cause: A report with this ID was already created and the import mode was Preserveid.

Action: Either check the ID or change the import mode.
Level: 1

Type: ERROR

Impact: Data

BAM-02590: A report already exists with ID {0}.

Cause: A report with same ID was already created.

Action: Choose a unique ID.
Level: 1

Type: ERROR

Impact: Data

BAM-02591: premature EOF at or near line {0}

Cause: Unexpected end of file was found.

Action: Check the syntax of the XML file.
Level: 1

Type: ERROR

Impact: Data

BAM-02592: premature EOF in import file {0} at or near line {1}

Cause: Unexpected end of file was found.

Action: Check the syntax of the XML file.
Level: 1

Type: ERROR

Impact: Data

BAM-02700: invalid Changelist

Cause: The returned Changelist did not contain valid XML.

Action: Correct the XML.
Level: 1

Type: ERROR

Impact: Data

Cause: The Changelist was overwritten, but one viewset was lagging behind and requested an older one.

Action: No action is necessary.

BAM-02701: Report Cache server error

Cause: Report Cache failed with the specified operation (for example, start active data, open viewset, and so on).

Action: Check the log for more details.
Level: 1

Type: ERROR

Impact: Process

BAM-02702: The viewset expired.

Cause: The viewset with specified ID has expired.

Action: Open a new viewset.
Level: 1

Type: ERROR

Impact: Session

BAM-02703: RecordSet size cannot be zero (0).

Cause: An e-mail with a report attachment failed when the Oracle BAM Server was asked to return zero records for the viewset.

Action: Ensure that the configuration entry, RecordsLimitForEmail, has value greater than zero.
Level: 1

Type: ERROR

Impact: Process

Cause: Save offline failed when the Oracle BAM Server was asked to return zero records for the viewset.

Action: Ensure that the configuration entry, RecordsLimitForSaveOffline, has value greater than zero.

Cause: For all other cases, the viewset could not be opened because a request was made that the Oracle BAM Server send back zero records for that viewset.

Action: Check the log file for more details and report the error.

BAM-02704: Invalid RecordSet start row index {0} for the viewset with RecordSetSize {1} and RecordCount {2}.

Cause: The RecordSet with the specified start row index could not be returned.

Action: Ensure that the start row index is a multiple of RecordSetSize, and that it has a value from 0 to a maximum of RecordCount minus RecordSetSize.
Level: 1

Type: ERROR

Impact: Process

BAM-04000: syntax error in calculated field {0}

Cause: There was a syntax error in a calculated column definition.

Action: Correct the calculated column definition.
Level: 1

Type: ERROR

Impact: Data

BAM-04001: Unable to set value {0} in column {2} (type {1}).

Cause: Failed to set the specified value in a column.

Action: Check the given data value.
Level: 1

Type: ERROR

Impact: Data

BAM-04002: Specified data object was not found.

Cause: The given data object was not found.

Action: The data object may have been deleted by another process.
Level: 1

Type: ERROR

Impact: Data

BAM-04003: Data objects cannot be edited while they are in use.

Cause: There were open viewsets on this data object.

Action: Close any viewsets on this data object before proceeding to edit it.
Level: 1

Type: ERROR

Impact: Threads

BAM-04004: Data objects cannot be deleted while they are in use.

Cause: There were open viewsets on this data object.

Action: Close any viewsets on this data object before proceeding to delete it.
Level: 1

Type: ERROR

Impact: Threads

BAM-04005: Cannot edit a data object that is a lookup source for a data object that is currently in use.

Cause: There were open viewsets on data objects with a lookup into this data object.

Action: Close any viewsets on dependent data objects before proceeding to edit lookup source data objects.
Level: 1

Type: ERROR

Impact: Threads

BAM-04006: Cannot delete a data object that is a lookup source for a data object that is currently in use.

Cause: There were open viewsets on data objects with a lookup into this data object.

Action: Close any viewsets on dependent data objects before proceeding to delete lookup source data objects.
Level: 1

Type: ERROR

Impact: Threads

BAM-04007: Dimension name {0} is not unique.

Cause: The specified dimension name was not unique.

Action: Specify a unique dimension name.
Level: 1

Type: ERROR

Impact: Compliance

BAM-04008: Hierarchy name {0} is not unique.

Cause: The specified hierarchy name was not unique.

Action: Specify a unique hierarchy name.
Level: 1

Type: ERROR

Impact: Compliance

BAM-04009: Cannot change column {0} from a non-calculated column to a calculated column.

Cause: An attempt was made to convert a non-calculated column to a calculated column.

Action: Do not attempt to convert a non-calculated column to a calculated column.
Level: 1

Type: ERROR

Impact: Compliance

BAM-04010: Cannot change column {0} to a datetime/timestamp column.

Cause: An attempt was made to convert a column from a non-datetime type to a datetime type.

Action: Do not attempt to convert a non-datetime column to a datetime column.
Level: 1

Type: ERROR

Impact: Compliance

BAM-04011: Folder or data object {0} already exists.

Cause: An attempt was made to create a folder that already exists.

Action: A unique name must be specified when creating folders.
Level: 1

Type: ERROR

Impact: Data

BAM-04012: Folder does not exist.

Cause: The folder was deleted by another process.

Action: Create the folder before proceeding with the current operation.
Level: 1

Type: ERROR

Impact: Data

BAM-04013: The source lookup data object {0} for column {1} cannot be found.

Cause: The source lookup data object was deleted.

Action: Create the source lookup data object before proceeding with the current operation.
Level: 1

Type: ERROR

Impact: Data

BAM-04014: Cannot move {0}. The destination folder is a subfolder of the source folder.

Cause: The folder specified was a subfolder of the source folder.

Action: Do not attempt to move folders to their own subfolders.
Level: 1

Type: ERROR

Impact: Compliance

BAM-04015: Cannot move {0}.

Cause: A FolderException was thrown when a folder was moved.

Action: Check the log for details.
Level: 1

Type: ERROR

Impact: Operating System

BAM-04016: Cannot move {0}. The destination folder is the same as the source folder.

Cause: The destination folder was the same as the source folder.

Action: Do not attempt to move an object to a folder that is the same as its source folder.
Level: 1

Type: ERROR

Impact: Compliance

BAM-04017: The external data sources cannot be created when there are no external data source types defined.

Cause: There were no external data source types defined.

Action: Define external data source types in the Oracle BAM Administrator application.
Level: 1

Type: ERROR

Impact: Compliance

BAM-04018: The data object does not contain a column named {0} that is used as a matching field in the lookup column {1}.

Cause: The foreign key column was missing from this data object.

Action: Verify the name of the foreign key column.
Level: 1

Type: ERROR

Impact: Data

BAM-04019: An index cannot be created because this data object does not contain a column named {0}.

Cause: The column referenced in the index was missing in this data object.

Action: Verify the column name.
Level: 1

Type: ERROR

Impact: Data

BAM-04020: Folder named {0} not found.

Cause: The specified folder did not exist.

Action: Create the folder before proceeding with the current operation.
Level: 1

Type: ERROR

Impact: Data

BAM-04021: At least one column must be defined in the index.

Cause: No column has been specified in the index.

Action: Define at least one column in the index.
Level: 1

Type: ERROR

Impact: Compliance

BAM-04022: The date value must have the following format: {0}.

Cause: Failed to set the specified date value in a column.

Action: Input date value in suggested format.
Level: 1

Type: ERROR

Impact: Data

BAM-04200: Action {0} ({1}) failed.

Cause: The action order with the given action type failed.

Action: Check the log for more details.
Level: 1

Type: ERROR

Impact: Programmatic

BAM-04201: An error occurred while deleting the data.

Cause: A delete operation initiated by a Delete action button failed with a reason other than missing permissions.

Action: Check the log for more details.
Level: 1

Type: ERROR

Impact: Process

BAM-04202: Enter a new value.

Cause: An incorrect data type was found.

Action: Enter a new value.
Level: 1

Type: NOTIFICATION

Impact: Data

BAM-04203: The value {0} is not a valid {1}.

Cause: A column was updated with data of an invalid type.

Action: Provide data of the correct type for the update operation.
Level: 1

Type: ERROR

Impact: Data

BAM-04204: An error occurred while submitting the data.

Cause: An insert operation failed due to reasons other than missing permissions or non-null requirements.

Action: See the log for more details.
Level: 1

Type: ERROR

Impact: Programmatic

BAM-04205: insufficient permission to modify the data object

Cause: An attempt was made to modify the data object without sufficient permission.

Action: Request that the administrator assign sufficient permission to the user account before attempting this operation.
Level: 1

Type: ERROR

Impact: Security

BAM-04206: Cannot insert or update null value in column {0}.

Cause: A null value was encountered.

Action: Specify a non-null value.
Level: 1

Type: ERROR

Impact: Data

BAM-04207: An error occurred while updating the data.

Cause: An update operation failed due to reasons other than missing permissions or non-null requirements.

Action: Check the log for more details.
Level: 1

Type: ERROR

Impact: Programmatic

BAM-04208: Report not found.

Cause: The report with the ID specified was not found.

Action: Check the log for more details.
Level: 1

Type: ERROR

Impact: Data

BAM-06000: Authentication failed.

Cause: Credentials were not provided.

Action: Provide credentials in the service request.
Level: 1

Type: ERROR

Impact: Security

BAM-06001: details -- {0}

Cause: For information only.

Action: This is a piggyback message which provides details of the Exception.
Level: 1

Type: ERROR

Impact: Data

BAM-06002: Web services object {0} is null.

Cause: A null pointer exception occurred in Web services. A Web services object was found null.

Action: Check the log message for more details.
Level: 1

Type: ERROR

Impact: Programmatic

BAM-06003: Data object {0} does not exist.

Cause: The specified data object does not exist in the Oracle BAM Server.

Action: Provide the correct data object name including the full path to its location.
Level: 1

Type: ERROR

Impact: Data

BAM-06004: The rule name does not include a period (.) separator between the user name and the alert name.

Cause: There was no period (.) found in the rule name.

Action: A period must be used as the separator between the user name and the alert name.
Level: 1

Type: ERROR

Impact: Data

BAM-06005: The rule name includes a user name that does not match the user making the actual call to the Web service.

Cause: The user name embedded in the rule name did not match the user making the actual call to the Web service.

Action: Invoke Web services using the specified user name.
Level: 1

Type: ERROR

Impact: Compliance

BAM-06006: Exception occurred when firing the rule.

Cause: An exception was thrown when firing the rule.

Action: Check the log for more details.
Level: 1

Type: ERROR

Impact: Process

BAM-06007: The XML payload is invalid; {0} is expected.

Cause: The XML payload is invalid.

Action: Check the Web services schema and provide the correct payload.
Level: 1

Type: ERROR

Impact: Data

BAM-06008: The XML payload is invalid; extra contents were found.

Cause: Extra contents were found in the XML payload.

Action: Check the Web services schema and provide the correct payload.
Level: 1

Type: ERROR

Impact: Data

BAM-06009: invalid column name: {0}

Cause: An invalid column name was found in the payload.

Action: Check the Web services schema and provide the correct payload.
Level: 1

Type: ERROR

Impact: Data

BAM-06010: invalid XML payload; {0} found

Cause: Premature end of XML payload reached.

Action: Check the Web services schema and provide the correct payload.
Level: 1

Type: ERROR

Impact: Data

BAM-06011: invalid key specification; {0} found

Cause: An invalid key was specified.

Action: Provide keys in a comma separated format (for example, Salesperson,SalesNumber).
Level: 1

Type: ERROR

Impact: Data

BAM-06012: invalid credentials

Cause: The credentials were invalid or not supplied by the user.

Action: Supply valid credentials for the secured web service.
Level: 1

Type: ERROR

Impact: Security

BAM-06100: Data object definition creation failed.

Cause: The Oracle BAM Server failed to process the create operation.

Action: Verify that the Oracle BAM server is running. Check the log message if it is available.
Level: 1

Type: ERROR

Impact: Process

Cause: Invalid message content was present in the XML payload.

Action: Correct the message content in the XML payload.

BAM-06101: Cannot delete the {0} data object definition.

Cause: The Oracle BAM Server failed to process the delete operation.

Action: Verify that the Oracle BAM server is running. Check the log message if it is available.
Level: 1

Type: ERROR

Impact: Process

Cause: Invalid message content was present in the XML payload

Action: Correct the message content in the XML payload.

BAM-06102: Cannot update data object definition.

Cause: The Oracle BAM Server failed to process the update operation.

Action: Verify that the Oracle BAM server is running. Check the log message if it is available.
Level: 1

Type: ERROR

Impact: Process

Cause: Invalid message content was present in the XML payload

Action: Correct the message content in the XML payload.

BAM-06103: invalid XML payload for DataObjectDefinition Web service

Cause: The XML payload was invalid.

Action: Provide a valid XML payload for the associated operation.
Level: 1

Type: ERROR

Impact: Data

BAM-06104: Error serializing the definition of data object {0}.

Cause: Web services failed to serialize the object to XML.

Action: Verify that the Oracle BAM Server is running. Check the log message if it is available.
Level: 1

Type: ERROR

Impact: Programmatic

BAM-06140: Failure on data object {0} batch operation.

Cause: The Oracle BAM Server failed to process the batch operation.

Action: Verify that the Oracle BAM Server is running. Check the log message if it is available.
Level: 1

Type: ERROR

Impact: Process

Cause: Invalid message content was present in the XML payload

Action: Correct the message content in the XML payload

BAM-06141: Failure on data object {0}, {1} operation.

Cause: A specific operation on the target data object failed.

Action: Verify that the Oracle BAM Server is running. Check the log message if it is available.
Level: 1

Type: ERROR

Impact: Process

Cause: Invalid message content was present in the XML payload.

Action: Correct the message content in the XML payload.

BAM-06142: Cannot delete the rows of data object {0}.

Cause: The Oracle BAM Server failed to process the delete operation.

Action: Verify that the Oracle BAM Server is running. Check the log message if it is available.
Level: 1

Type: ERROR

Impact: Process

Cause: Invalid message content was present in the XML payload.

Action: Correct the message content in the XML payload

BAM-06143: Cannot look up the rows of data object {0}.

Cause: The Oracle BAM Server failed to process the lookup operation.

Action: Verify that the Oracle BAM Server is running. Check the log message if it is available.
Level: 1

Type: ERROR

Impact: Process

Cause: Invalid message content was present in the XML payload.

Action: Correct the message content in the XML payload.

BAM-06144: Cannot insert rows into data object {0}.

Cause: The Oracle BAM Server failed to process the insert operation.

Action: Verify that the Oracle BAM Server is running. Check the log message if it is available.
Level: 1

Type: ERROR

Impact: Process

Cause: Invalid message content was present in the XML payload.

Action: Correct the message content in the XML payload.

BAM-06145: Cannot update rows in data object {0}.

Cause: The Oracle BAM Server failed to process the update operation.

Action: Verify that the Oracle BAM Server is running. Check the log message if it is available.
Level: 1

Type: ERROR

Impact: Process

Cause: Invalid message content was present in the XML payload.

Action: Correct the message content in the XML payload.

BAM-06146: Cannot upsert rows in data object {0}.

Cause: The Oracle BAM Server failed to process the upsert operation.

Action: Verify that the Oracle BAM Server is running. Check the log message if it is available.
Level: 1

Type: ERROR

Impact: Process

Cause: Invalid message content was present in the XML payload.

Action: Correct the message content in the XML payload.

BAM-06147: invalid XML payload for DataObjectOperations Web service

Cause: Invalid message content was present in the XML payload.

Action: Correct the message content in the XML payload.
Level: 1

Type: ERROR

Impact: Data

BAM-06180: Decoding {0} failed.

Cause: Failed to decode the request's URL.

Action: Check the log message for more details.
Level: 1

Type: ERROR

Impact: Programmatic

BAM-06181: Encoding {0} failed.

Cause: The WSIL Browser failed to encode the URL in the response.

Action: Check the log message for more details.
Level: 1

Type: ERROR

Impact: Programmatic

BAM-06182: Folder {0} does not exist.

Cause: The folder specified in the URL does not exist.

Action: Correct the path in the URL.
Level: 1

Type: ERROR

Impact: Data

BAM-06183: MetadataBrowser initialization failed.

Cause: Failed to initialize the MetadataBrowser object.

Action: Check the log message for more details.
Level: 1

Type: ERROR

Impact: Process

BAM-06184: MetadataBrowser.browseDataObjects(): exception={0}

Cause: Failed to browse and generate the response.

Action: Check the log message for more details.
Level: 1

Type: ERROR

Impact: Programmatic

BAM-06185: invalid URL: {0}

Cause: Invalid URL was found.

Action: Correct the URL.
Level: 1

Type: ERROR

Impact: Data

BAM-06220: Exception while processing {0}.

Cause: WSIL browser failed to process the request.

Action: Check the log message for more details.
Level: 1

Type: ERROR

Impact: Process

BAM-06221: WSIL document creation failure

Cause: Instantiating WSILCreator object failed.

Action: Check the log message for more details.
Level: 1

Type: ERROR

Impact: Process

BAM-06260: Query string DataObjectID=_Xxxx not found in the URL.

Cause: The query string that specifies the data object ID was not found in the URL.

Action: Provide a URL similar to: http://999.99.999.99:9001/OracleBAM/WebServices/GetDataObjectDefinition?DataObjectID=_Employees
Level: 1

Type: ERROR

Impact: Data

BAM-07000: Invalid field maximum size in enterprise message source definition.

Cause: The field maximum size value in enterprise message source definition is an invalid number.

Action: Provide a valid numeric value for the field maximum size.
Level: 1

Type: ERROR

Impact: Compliance

BAM-07001: invalid XSL transformation for field {0}: {1}

Cause: The XSL transformation for the field is invalid.

Action: Look at the error message for details and correct the errors.
Level: 1

Type: ERROR

Impact: Data

BAM-07002: Unrecognized field type in enterprise message source definition.

Cause: A field type other than the following was specified: String, Integer, Float, DateTime, Decimal, or Boolean.

Action: Check the spelling of field type or choose one from the above list.
Level: 1

Type: ERROR

Impact: Data

BAM-07003: The enterprise message source definition could not be loaded.

Cause: The enterprise message source definition could not be loaded using the given ID.

Action: Check the spelling of the ID.
Level: 1

Type: ERROR

Impact: Process

BAM-07004: unrecognized enterprise message source definition version

Cause: The version number in the enterprise message source definition is not one of the following values: 2, 3, 4, 5, or 6.

Action: Provide a supported version in the enterprise message source definition.
Level: 1

Type: ERROR

Impact: Upgrade

BAM-07020: The required keys to perform the requested operation were not supplied.

Cause: Keys were missing for the requested operation.

Action: Provide the required keys for the requested operation.
Level: 1

Type: ERROR

Impact: Data

BAM-07021: The data object {0} must have a surrogate key column named {1}.

Cause: The surrogate key column does not exist in the data object.

Action: Check the spelling of the column name and correct it.
Level: 1

Type: ERROR

Impact: Data

BAM-07022: The surrogate key column {0} must be an autoincrementing integer type.

Cause: The surrogate key column was not of type autoincrementing integer.

Action: Change the type of surrogate key column to autoincrementing integer.
Level: 1

Type: ERROR

Impact: Data

BAM-07023: The data object {0} must have a natural key column named {1}.

Cause: The natural key column does not exist in the data object.

Action: Check the spelling of the column name and correct it.
Level: 1

Type: ERROR

Impact: Data

BAM-07024: The data object {0} must have an error column named {1}.

Cause: The required error column does not exist in the data object.

Action: Check the spelling of the column name and correct it.
Level: 1

Type: ERROR

Impact: Data

BAM-07025: Unsupported column name {0} in the result set.

Cause: The column name provided is not supported in the result set.

Action: Check the spelling of the column name and correct it.
Level: 1

Type: ERROR

Impact: Data

BAM-07026: unsupported method

Cause: The method name provided is not supported in the ResultSet.

Action: Use other methods.
Level: 1

Type: ERROR

Impact: Compliance

BAM-07027: no more rows

Cause: There are no more rows in the ResultSet.

Action: Check the return value of the next method before invoking this method.
Level: 1

Type: ERROR

Impact: Data

BAM-07028: The key condition {0} is invalid.

Cause: The key condition is invalid.

Action: Valid key conditions are: *, =, !-, <, <=, >, and >=.
Level: 1

Type: ERROR

Impact: Data

BAM-07029: invalid XML payload

Cause: None of the input fields match any data object field.

Action: Check the source field names and provide the correct payload.
Level: 1

Type: ERROR

Impact: Data

BAM-07030: Invalid XML payload for enterprise message source definition. Error={0}

Cause: An exception was thrown while getting the default enterprise message source field definition list.

Action: Check the log for more details.
Level: 1

Type: ERROR

Impact: Data

Cause: An exception was thrown while loading up fields of this enterprise message source type with the information read from the System Object.

Action: Check the log for more details.

BAM-07031: invalid message type: {0}

Cause: An invalid message type was found.

Action: Provide either XML or MAP message type.
Level: 1

Type: ERROR

Impact: Data

BAM-07032: Oracle BAM enterprise message source is already started.

Cause: The Oracle BAM enterprise message source was already started.

Action: No action is necessary.
Level: 1

Type: WARNING

Impact: Process

BAM-07033: The enterprise message source failed with error: {0}.

Cause: The Oracle BAM enterprise message source failed.

Action: Check the log file for more details and report the error.
Level: 1

Type: ERROR

Impact: Process

BAM-07034: Oracle BAM enterprise message source is not running.

Cause: The Oracle BAM enterprise message source is not running, and an application tried to stop it.

Action: Check the log file for more details and report the error.
Level: 1

Type: WARNING

Impact: Process

BAM-07035: Invalid request specified; parameter {0} is missing.

Cause: The enterprise message source failed because the parameter was not provided.

Action: Check the log file for more details and report the error.
Level: 1

Type: ERROR

Impact: Programmatic

BAM-07036: The value {0} specified for parameter {1} is unknown.

Cause: The enterprise message source failed because wrong the parameter value was provided.

Action: Check the log file for more details and report the error.
Level: 1

Type: ERROR

Impact: Data

BAM-07037: Multiple matching rows were found in dimension table.

Cause: Multiple matching rows were found in dimension table.

Action: Trace the history to find out why multiple rows with the same key have been inserted.
Level: 1

Type: ERROR

Impact: Compliance

BAM-07038: Non-key columns do not match.

Cause: A matching is found in dimension table. But, non-key columns do not match.

Action: Provide the correct source column values in the looksert operation.
Level: 1

Type: ERROR

Impact: Compliance

BAM-07039: Row update failed with no matching rows.

Cause: There was a failure trying to update a row because there is no matching rows in target table.

Action: Provide the correct source key values in the update operation.
Level: 1

Type: ERROR

Impact: Data

BAM-07040: Data object {0} not found.

Cause: There was a failure trying to access the Data object.

Action: Make sure the Data object exists.
Level: 1

Type: ERROR

Impact: Data

BAM-07041: Invalid Message Selector format

Cause: The attempt to parse the Message Selector data failed.

Action: Verify that the format meets the guidelines specified in the documentation.
Level: 1

Type: ERROR

Impact: Data

10 B2B-50006 to B2B-53011

B2B-50006: Exception Received

Cause: B2B received an exception message from the trading partner.

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50007: Notification of failure received

Cause: B2B received a notification of failure - out of band exception from trading partner

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50008: Document level retry count is exhausted.

Cause: Maximum number of document level retries has been reached.

Action: Increase the maximum number of document level retries
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50009: Failed to Send

Cause: B2B cannot send message to the trading partner

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50010: Trading partner agreement identification error

Cause: B2B cannot identify an agreement using the current details

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50011: Message Correlation Error

Cause: B2B cannot correlate the message

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50012: Pack/Unpack Error

Cause: Error in packaging

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50013: Security Error

Cause: Error in security validation

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50014: General Error

Cause: Internal error in engine

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50015: In-band notification error

Cause: Internal engine error

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50017: Document protocol identification error.{0}

Cause: Failed to identify the document protocol for the message.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50018: Interchange Sender Id is not present.

Cause: Interchange Sender Id is not present.

Action: Verify the Interchange Sender Id is the same in payload and configuration.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50019: Interchange Receiver Id is not present.

Cause: Interchange Receiver Id is not present.

Action: Verify the Interchange Receiver Id is the same in payload and configuration.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50025: Repository error

Cause: Error accessing metadata repository

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50027: Failed to write data into output stream.

Cause: Failed to write data into output stream.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50028: Failed to read data from input stream.

Cause: Failed to read data from input stream.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50029: B2B runtime error

Cause: A runtime error has occurred.

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50030: B2B Negative Ack Received

Cause: B2B has received a negative acknowledgement

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50031: B2B general error

Cause: A general error has occurred

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50032: B2B exchange protocol negative acknowledge received

Cause: Received a negative exchange acknowledge message.

Action: Review the negative exchange acknowledge message to determine the cause, or check with the trading partner.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50033: B2B functional acknowledgment processing error

Cause: An error occurred during functional acknowledgment processing.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50034: B2B negative functional acknowledgment

Cause: A negative functional acknowledgment is received.

Action: Review the negative functional acknowledge message to determine the cause or check with the trading partner.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50035: B2B exception message processing error

Cause: An error occurred during exception message processing.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50036: B2B trading partner agreement identification error

Cause: An error had occurred during identify trading partner agreement.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50037: B2B inbound message processing error

Cause: An error occurred during incoming message processing.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50038: B2B outbound app message input {0} header processing error

Cause: An error occurred during outbound {0} input processing.

Action: Review the input properties sent for outbound message processing. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50039: Negative Interchange acknowledgment received

Cause: A negative Interchange acknowledgment is received.

Action: Review the negative Interchange acknowledge message to determine the cause or check with the trading partner.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50041: TopLink server session initialization error

Cause: An error occurred during TopLink server session initialization.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50042: B2B trace context initialization error

Cause: An error occurred during trace context initialization.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50050: Engine initialization error.

Cause: An error occurred during engine initialization.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. If the problem persists, contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50051: Failed to shut down the B2B engine.

Cause: An error occurred during engine shut down.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. If the problem persists, contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50052: Engine already initialized.

Cause: Attempt made to initialize B2B engine which has been initialized already.

Action: Ensure that the engine is stopped before attempting to initialize
Level: 1

Type: NOTIFICATION

Impact: Process

B2B-50059: Error in starting B2B Server.

Cause: An error has occurred while starting the server.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INTERNAL_ERROR

Impact: Process

B2B-50060: Error in stopping B2B Server

Cause: An error has occurred while stopping the server.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50075: Error loading document or exchange plug-in.

Cause: Error loading document or exchange plug-in.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50076: Error loading packaging plug-in.

Cause: Error loading packaging plug-in.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50077: Cannot Initialize Transport.

Cause: Cannot Initialize Transport.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50078: Cannot shut down transport.

Cause: Cannot shut down transport.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50079: Transport error

Cause: An error has occurred in transport layer

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50080: Exchange protocol identification error.

Cause: Failed to identify the exchange protocol of the message.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50081: Duplicate exchange protocol message error

Cause: Duplicate exchange protocol message generated by the trading partner.

Action: Report this error to the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-50082: Duplicated Control Number error

Cause: Message received with duplicate control number {0}.

Action: Report this error to the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-50083: Document protocol identification error.

Cause: Failed to identify the document protocol for the message.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50084: No service found

Cause: Requested service was not registered in system

Action: Check requested web service URL
Level: 1

Type: ERROR

Impact: Process

B2B-50085: Duplicated transaction number error for xpath {0} with value {1}. The message id : {2}

Cause: Message received with duplicate transaction number error for xpath {0} with value {1}. The message id : {2}

Action: Check the xpath value of the message
Level: 1

Type: ERROR

Impact: Process

B2B-50545: An agreement {0} has expired or is not in force as yet. The effective From/To dates are {1} - {2}.

Cause: An agreement effective From/To dates are invalid.

Action: Change the agreement effective From/To dates.
Level: 1

Type: ERROR

Impact: Process

B2B-50546: Information given to identify an agreement is insufficient: FromTP {0}, ToTP {1}, document type {2}.

Cause: Failed to identify the agreement

Action: Make sure From/To TP and document information is not Null.
Level: 1

Type: ERROR

Impact: Process

B2B-50547: Agreement not found for trading partners: FromTP {0}, ToTP {1} with document type {2}.

Cause: Failed to identify the trading partner agreement from the given input values.

Action: Make sure there is an agreement configured for the From/To trading partner and document information that presents in the message.
Level: 1

Type: ERROR

Impact: Process

B2B-50548: Agreement {0} not in active state.

Cause: Agreement was not in active state.

Action: Make sure the agreement is deployed and it is in Active state.
Level: 1

Type: ERROR

Impact: Process

B2B-50549: Cannot uniquely identify the trading partner. The trading partners {0} have the same set of identifications.

Cause: The trading partners {0} have the same set of identifications

Action: Make sure the trading partners have unique identifications
Level: 1

Type: ERROR

Impact: Process

B2B-50550: Cannot find the trading partner for the given identification type {0} and value {1}

Cause: The trading partner was not exist for the given identification type and value.

Action: Create or update the trading partner with the given identification type and value.
Level: 1

Type: ERROR

Impact: Process

B2B-50601: Agreement found but the certificate used for client authentication may not represent the Trading Partner {0} whom it claims to be.

Cause: Certificate used for client authentication may not belong to the Trading Partner.

Action: Please make sure Trading partner alias has been configured correctly against Security Identifier. If it is, then it is a serious security error, please consult your security administrator for further course of action.
Level: 1

Type: ERROR

Impact: Process

B2B-50602: Keystore not available to validate the incoming certificate over SSL.

Cause: Keystore may not be properly configured in B2B to validate the incoming SSL client certificate.

Action: Please make sure keystore has been configured correctly in B2B.
Level: 1

Type: ERROR

Impact: Process

B2B-50603: Agreement found but authenticated principal(user) over http do not represent the Trading Partner {0} whom it claims to be.

Cause: Authenticated user may not represent the Trading Partner.

Action: Please make sure the Security Identifier configuration in B2B against the Trading Partner is correct. If the value is correct, then it is serious security error, please consult your security administrator for further course of action.
Level: 1

Type: ERROR

Impact: Process

B2B-50651: Agreement not found for trading partners: FromTP {0}, ToTP {1} with {2}.

Cause: Failed to match the service, action, servicetype for the trading partner agreement from the message.

Action: Make sure there is an agreement that contains a matching service, action, servicetype in the CPA configured for the From/To, service,action, servicetype information that is present in the message.
Level: 1

Type: ERROR

Impact: Process

B2B-50701: The agreement {0} cannot be activated because a similar agreement {1} found in active state

Cause: Similar agreement found in active state. There cannot be two agreements with the same trading partners, document type, version, and direction.

Action: Make inactive existing active agreement which has the same trading partners, document type, version, and direction.
Level: 1

Type: ERROR

Impact: Process

B2B-50702: {0} does not exist in the repository.

Cause: {0} does not exist in the repository.

Action: Channel/TPName does not exist in the repository. Get the latest list of channels.
Level: 1

Type: ERROR

Impact: Process

B2B-50703: Endpoint {0} does not exist in the group.

Cause: Endpoint {0} does not exist in the group.

Action: Endpoint does not exist in the group. Get the latest list of endpoints.
Level: 1

Type: ERROR

Impact: Process

B2B-50704: Group {0} does not exist in the repository.

Cause: Group {0} does not exist in the repository.

Action: Group does not exist in the repository. Get the latest list of group.
Level: 1

Type: ERROR

Impact: Process

B2B-50705: Duplicate Endpoint {0}.

Cause: Endpoint {0} already exist in the repository

Action: Endpoint already exist in the repository.Can not create same name endpoint
Level: 1

Type: ERROR

Impact: Process

B2B-50706: No callout for internal delivery channel.

Cause: Callout can not be set for internal delivery channel.

Action: Remove callout from internal delivery channel.
Level: 1

Type: ERROR

Impact: Process

B2B-50707: Endpoint Validation Error

Cause: Endpoint validation error.

Action: Endpoint validation error.Check the diagnostic log for more details.
Level: 1

Type: ERROR

Impact: Process

B2B-50708: Mandatory parameter value missing.

Cause: Mandatory Parameter can not be null.

Action: Provide the mandatory parameter value.
Level: 1

Type: ERROR

Impact: Process

B2B-50709: Endpoint Disablement Failed.

Cause: Endpoint can not disabled

Action: Endpoint Disablement Failed. Check the diagnostic log.
Level: 1

Type: ERROR

Impact: Process

B2B-50710: Document Protocol {0} does not supported

Cause: Document Protocol {0} not supported.

Action: Document Protocol doesnot supported.
Level: 1

Type: ERROR

Impact: Process

B2B-50711: Document definition {0} not exists

Cause: Document definition {0} does not exists.

Action: Document definition does not exists.
Level: 1

Type: ERROR

Impact: Process

B2B-50712: Error in removing document.

Cause: Error while removing document from endpoint.

Action: There is error while removing document from endpoint. Check the diagnostic log.
Level: 1

Type: ERROR

Impact: Process

B2B-50713: Internal Delivery Channel is used in endpoint document

Cause: Internal Delivery Channel is used in endpoint document

Action: Internal Delivery Channel is used in endpoint document. Check the diagnostic log.
Level: 1

Type: ERROR

Impact: Process

B2B-50714: IDREF_KEY Missing.

Cause: IDREF_KEY Missing in configuration.

Action: IDREF_KEY Missing in configuration. Check the diagnostic log.
Level: 1

Type: ERROR

Impact: Process

B2B-50715: No document attached to endpoint

Cause: There is no document attached to endpoint.

Action: There is no document attached to endpoint.There should be atleast one document attached to enable the endpoint.Check the diagnostic log.
Level: 1

Type: ERROR

Impact: Process

B2B-50716: FTP Sequencing Parameters missing

Cause: timestamp_format,timestamp_offset,timestamp_source values are must for FTP if Sequencing is enabled

Action: Provide timestamp_format,timestamp_offset,timestamp_source values for FTP endpoint.
Level: 1

Type: ERROR

Impact: Process

B2B-50717: Block characters missing

Cause: Block characters parameters values are missing.

Action: Provide the Block characters parameters.
Level: 1

Type: ERROR

Impact: Process

B2B-50718: Channel is associated with {0} TradingPartner(s) and associated TradingPartner(s) are {1}

Cause: Channel is associated with {0} TradingPartner(s) and associated TradingPartner(s) are {1}

Action: Make sure channel is not associated with any TradingPartner(s).
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50741: WS-HTTP transport protocol must have WSDL Artifacts.

Cause: WS-HTTP transport protocol did not have WSDL Artifacts.

Action: make sure WS-HTTP transport protocol has WSDL Artifacts.
Level: 1

Type: ERROR

Impact: Process

B2B-50742: Service parameter are not well formed in WS-HTTP channel.

Cause: service parameter did not have namespace encloses with curly braces in WS-HTTP Channel.

Action: Make sure service parameter has namespace encloses with curly braces in WS-HTTP channel.
Level: 1

Type: ERROR

Impact: Process

B2B-50743: Invalid Payload received for Sync Request from Backend. Payload is null

Cause: Either Back-end composite is a One-Way composite, or it is not configured properly to return a response.

Action: Make sure Composite is configured to send a response
Level: 1

Type: ERROR

Impact: Process

B2B-50801: No input value is specified. At least one input value is needed: From/To trading partner or Document or Action

Cause: Missing input values

Action: Specify input values such as From/To trading partner or Document or Action
Level: 1

Type: ERROR

Impact: Process

B2B-50901: Failed to find a business message with B2BMessageId {0}.

Cause: Failed to find a business message with B2BMessageId.

Action: Review the UI report to verify that a message exists with B2BMessageId.
Level: 1

Type: ERROR

Impact: Process

B2B-50902: Failed to find a wire message with B2BMessageId {0}.

Cause: Failed to find a wire message with B2BMessageId.

Action: Review the UI report to verify that a message exists with B2BMessageId.
Level: 1

Type: ERROR

Impact: Process

B2B-50903: Message {0} retry count is zero.

Cause: The maximum number of message retries has been reached.

Action: Increase the maximum number of retries in delivery channel.
Level: 1

Type: NOTIFICATION

Impact: Process

B2B-50904: ReferTo message not found.

Cause: The message ID specified in the header RefToMessageID not found.

Action: It is possible that the original message was purged. Try resubmitting the original message.
Level: 1

Type: ERROR

Impact: Process

B2B-50906: Failed to retrieve value for the given XPATH.

Cause: Error occurred while extracting XPATH value.

Action: Make sure XPATH in document definition is correct and applicable for the payload
Level: 1

Type: ERROR

Impact: Process

B2B-51000: General packaging Error

Cause: Packaging details were incorrect.

Action: Correct the packaging details in delivery channel.
Level: 1

Type: INTERNAL_ERROR

Impact: Process

B2B-51001: Packaging fail

Cause: Packaging information were insufficient.

Action: Correct the packaging details in delivery channel.
Level: 1

Type: ERROR

Impact: Process

B2B-51002: Unpacking fail

Cause: Packaging headers were incorrect.

Action: Correct the packaging details in delivery channel.
Level: 1

Type: ERROR

Impact: Process

B2B-51003: Encoding failed

Cause: Encoding type was incorrect.

Action: Review the UI report for the exact error, which begins with the string 'ERROR:' This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-51004: Decoding failed

Cause: Decoding type was incorrect.

Action: Review the UI report for the exact error, which begins with the string 'ERROR:' This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-51005: Validating packaging metadata failed.

Cause: Packaging metadata was insufficient.

Action: Verify packaging metadata to pack the message.
Level: 1

Type: ERROR

Impact: Process

B2B-51006: Invalid input parameter

Cause: Packaging input parameters were invalid.

Action: Verify the packaging parameters and packaging metadata.
Level: 1

Type: ERROR

Impact: Process

B2B-51007: Missing packaging metadata information.

Cause: Missing few packaging metadata.

Action: Verify the packaging metadata.
Level: 1

Type: ERROR

Impact: Process

B2B-51008: Circular dependency in packaging metadata.

Cause: Circular dependency found in packaging metadata.

Action: Review the UI report for the exact error, which begins with the string 'ERROR:' This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-51009: Missing one or more packaging elements in packaging metadata.

Cause: Missing one or more packaging elements in packaging metadata.

Action: Verify packaging metadata has packaging elements.
Level: 1

Type: ERROR

Impact: Process

B2B-51010: Missing composite packaging element in packaging metadata.

Cause: None of the composite packaging elements exist in the Multipart message.

Action: Make sure Multipart message has at least one composite packaging element.
Level: 1

Type: ERROR

Impact: Process

B2B-51011: Invalid packaging metadata.

Cause: Message has more than one simple part. Hence, failed to package the message.

Action: Verify MIME message has only one simple part.
Level: 1

Type: ERROR

Impact: Process

B2B-51012: Missing list of message components.

Cause: Missing list of message component in the message.

Action: Verify the message has list of component.
Level: 1

Type: ERROR

Impact: Process

B2B-51013: Missing one or more message components in the list of message components.

Cause: Protocol components did not have all the required components while packaging information.

Action: Verify the protocol components and set all the required components for packaging the information.
Level: 1

Type: ERROR

Impact: Process

B2B-51014: Missing data for message component.

Cause: Invalid data for message component.

Action: Verify message has component data.
Level: 1

Type: ERROR

Impact: Process

B2B-51015: Missing security information.

Cause: Invalid security information.

Action: Verify security information is exist in packaging.
Level: 1

Type: ERROR

Impact: Process

B2B-51016: Missing signature information.

Cause: Invalid digital signature information.

Action: Review the UI report for the exact error, which begins with the string 'ERROR:' This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-51017: Missing encryption information.

Cause: Required envelope information did not exist.

Action: Verify the required envelope information available in packaging.
Level: 1

Type: ERROR

Impact: Process

B2B-51018: Message is not digitally signed.

Cause: Message was not digitally signed.

Action: Review the UI report for the exact error, which begins with the string 'ERROR:' This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-51019: Message is not encrypted.

Cause: Message was not encrypted.

Action: Verify the message which has to be encrypted.
Level: 1

Type: ERROR

Impact: Process

B2B-51020: Signature protocol is not supported.

Cause: Signature protocol was not Secure Multipurpose Internet Mail Extensions (S/MIME).

Action: Use Secure Multipurpose Internet Mail Extensions (S/MIME) as a signature protocol.
Level: 1

Type: ERROR

Impact: Process

B2B-51021: Encryption protocol is not supported.

Cause: Encryption protocol was not a Secure Multipurpose Internet Mail Extensions (S/MIME).

Action: Use Secure Multipurpose Internet Mail Extensions (S/MIME) as a encryption protocol.
Level: 1

Type: ERROR

Impact: Process

B2B-51022: Digest algorithm does not match.

Cause: Invalid digest algorithm.

Action: Verify digest algorithm.
Level: 1

Type: ERROR

Impact: Process

B2B-51023: Required signature information are already set for message.

Cause: Attempt made to set the signature information when it already has been set.

Action: Remove the existing signature information before attempting to set this new signature information.
Level: 1

Type: ERROR

Impact: Process

B2B-51024: Required envelope information is already set for message.

Cause: Attempt made to set envelope information when it has already been set.

Action: Remove the existing envelope information before attempting to set this new envelope information.
Level: 1

Type: ERROR

Impact: Process

B2B-51025: Keystore resource location incorrect

Cause: Incorrect keystore location specified.

Action: Specify correct keystore location.
Level: 1

Type: ERROR

Impact: Process

B2B-51026: Encoding type is not supported

Cause: Encoding type was not supported.

Action: Verify supported encoding type as any one of base64, quoted-printable, 7bit, 8bit, or binary.
Level: 1

Type: ERROR

Impact: Process

B2B-51050: MIME Content-Types do not match.

Cause: Mismatched MIME body part and MIME type.

Action: Verify the Content-Types in MIME body part.
Level: 1

Type: ERROR

Impact: Process

B2B-51051: MIME Content-Type parameter lists do not match.

Cause: While creating MIME body part, MIME Content-Type parameter lists mismatch.

Action: Verify the MIME Content-Type parameters list.
Level: 1

Type: ERROR

Impact: Process

B2B-51052: Invalid MIME Content-Type header or information.

Cause: Missing MIME Content-Type and value.

Action: Review the UI report for the exact error, which begins with the string 'ERROR:' This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-51053: Invalid MIME content disposition header or information.

Cause: Missing MIME content disposition header value.

Action: Verify MIME header content disposition.
Level: 1

Type: ERROR

Impact: Process

B2B-51054: Missing MIME Content-Type header information.

Cause: MIME Content-Type information was not exist.

Action: Verify MIME Content-Type header exist.
Level: 1

Type: ERROR

Impact: Process

B2B-51055: Missing information for message component.

Cause: Information were not exist for message component.

Action: Verify the message component information.
Level: 1

Type: ERROR

Impact: Process

B2B-51056: Missing or unable to read data from message.

Cause: Failed to read data from message.

Action: Verify the message data.
Level: 1

Type: ERROR

Impact: Process

B2B-51057: Invalid or corrupted message.

Cause: Invalid message format.

Action: Verify the message format.
Level: 1

Type: ERROR

Impact: Process

B2B-51075: Missing signer certificate.

Cause: Signer certificate not found.

Action: Provide the certificate to sign the message.
Level: 1

Type: ERROR

Impact: Process

B2B-51076: Missing encryption certificate.

Cause: Encryption certificate not found.

Action: Provide the certificate to encrypt the message.
Level: 1

Type: ERROR

Impact: Process

B2B-51077: Missing certificate chain.

Cause: Invalid certificate chain was exist.

Action: Provide the proper certificate with certificate chain.
Level: 1

Type: ERROR

Impact: Process

B2B-51078: Message has invalid digest information.

Cause: Failed to digest message or message corrupted.

Action: Provide appropriate digest for message.
Level: 1

Type: ERROR

Impact: Process

B2B-51079: S/MIME version is not supported.

Cause: Unsupported S/MIME version.

Action: Verify the S/MIME version should be either 2.0 or 3.0.
Level: 1

Type: ERROR

Impact: Process

B2B-51080: Signature algorithm {0} is not supported.

Cause: Unsupported signature algorithm specified.

Action: Review the UI report for the exact error, which begins with the string 'ERROR:' This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-51081: Digest algorithm {0} is not supported.

Cause: Unsupported digest algorithm specified.

Action: Review the UI report for the exact error, which begins with the string 'ERROR:' This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: ERROR

Impact: Process

B2B-51082: Encryption algorithm {0} is not supported.

Cause: Unsupported encryption algorithm specified.

Action: Review the UI report for the exact error, which begins with the string 'ERROR:' This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-51083: General failure creating S/MIME digital signature.

Cause: A failure has occurred when creating the S/MIME digital signature.

Action: Verify that the keystore has the correct private key and certificate.
Level: 1

Type: ERROR

Impact: Process

B2B-51084: General failure verifying S/MIME digital signature.

Cause: A general failure has occurred when attempting to verify the S/MIME digital signature.

Action: 1. Use correct certificate to verify the signature. 2. Message might have been corrupted. Check with the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-51085: General failure encrypting S/MIME message.

Cause: A general failure has occurred when attempting to encrypt the S/MIME digital signature.

Action: Use valid trading partner certificate.
Level: 1

Type: ERROR

Impact: Process

B2B-51086: General failure while decrypting S/MIME message.

Cause: General failure while decrypting S/MIME message.

Action: 1. Use correct Key Pair to decrypt the message. 2. Message might have been corrupted. Check with the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-51087: Could not create digest data for S/MIME digital signature {0}.

Cause: Creating digest data for S/MIME digital signature failed {0}.

Action: Use the supported algorithm as per the S/MIME standard or as per the exchange protocol.
Level: 1

Type: ERROR

Impact: Process

B2B-51088: Creating S/MIME digital signature failed {0}.

Cause: Failed to create S/MIME digital signature.

Action: Check the signing credentials.
Level: 1

Type: ERROR

Impact: Process

B2B-51089: Unable to verify S/MIME digital signature.

Cause: Verifying S/MIME digital signature failed {0}.

Action: Use correct certificate to verify the message.
Level: 1

Type: ERROR

Impact: Process

B2B-51090: Unable to create S/MIME message recipient.

Cause: Creating S/MIME message recipient list failed {0}.

Action: Check the recipient certificate.
Level: 1

Type: ERROR

Impact: Process

B2B-51091: Unable to add a recipient to S/MIME message recipient list {0}.

Cause: Adding recipient to S/MIME message recipient list failed {0}.

Action: Check the recipient certificate.
Level: 1

Type: ERROR

Impact: Process

B2B-51092: Encrypting S/MIME message failed {0}.

Cause: Failed to encrypt S/MIME message.

Action: Check the certificate used to encrypt the message.
Level: 1

Type: ERROR

Impact: Process

B2B-51093: Decrypting S/MIME message failed {0}.

Cause: Message encrypted using a wrong certificate.

Action: Check the key-pair used to decrypt the message or verify with the trading partner that the certificate used to encrypt the message is correct.
Level: 1

Type: ERROR

Impact: Process

B2B-51094: Processing signature information for S/MIME message failed.

Cause: Failed to Process signature information for S/MIME message.

Action: Request a re-send from the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-51095: Processing envelope information for S/MIME message failed.

Cause: Failed to process envelope information for S/MIME message.

Action: Request a re-send from the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-51096: Cannot include more than one signer in the S/MIME digital signature.

Cause: More than one signer in the S/MIME digital signature was not supported.

Action: Ask the trading partner to send the message with the single signer.
Level: 1

Type: ERROR

Impact: Process

B2B-51097: Found empty packaging IDs list during packaging plug-in initialization.

Cause: An empty packaging IDs list is passed for packaging plug-in initialization.

Action: Make sure correct packaging is mentioned.
Level: 1

Type: ERROR

Impact: Process

B2B-51098: Invalid Content-Type {0} in packaging metadata.

Cause: Packaging metadata contains invalid Content-Type.

Action: Make sure correct packaging details are mentioned.
Level: 1

Type: ERROR

Impact: Process

B2B-51099: An incorrect RosettaNet version has been found in the message.

Cause: Not a RosettaNet 1.1 message.

Action: Verify the packaging version.
Level: 1

Type: ERROR

Impact: Process

B2B-51105: Unsupported algorithm

Cause: Algorithm used was not supported by the S/MIME or exchange protocol.

Action: Use correct algorithm as specified by the exchange protocol or S/MIME standard.
Level: 1

Type: ERROR

Impact: Process

B2B-51107: Digest mismatch

Cause: Document might have been corrupted during transport.

Action: Request a re-send from the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-51108: Failed to digest the message.

Cause: Failed to create the digest for the message.

Action: Check the payload or digest algorithm.
Level: 1

Type: ERROR

Impact: Process

B2B-51112: An invalid CRL has been found in the incoming message.

Cause: Invalid CRL.

Action: Check with the trading partner that CRL is correct and request a re-send from the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-51114: CRL missing issuer

Cause: Issuer not found in CRL.

Action: Check with the trading partner that CRL issuer is correct and request a re-send from the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-51120: Invalid Content-Type

Cause: Content-Type of the signed/encrypted message was not correct.

Action: Request a re-send from the partner or resend the message with correct Content-Type.
Level: 1

Type: ERROR

Impact: Process

B2B-51121: Empty recipient list

Cause: No recipient list was exist in the encrypted message.

Action: Check with the trading partner and request a re-send with recipient list.
Level: 1

Type: ERROR

Impact: Process

B2B-51122: Certificate decode error

Cause: Certificate was not correct.

Action: Check if the certificate is in correct format.
Level: 1

Type: ERROR

Impact: Process

B2B-51124: Failed to create certificate chain

Cause: Unable to create certificate chain while generating the message.

Action: Check if the certificate used is a trusted certificate.
Level: 1

Type: ERROR

Impact: Process

B2B-51125: No certificate to sign

Cause: Certificate used to sign the message was not available in the keystore.

Action: Check if the certificate is available in the keystore.
Level: 1

Type: ERROR

Impact: Process

B2B-51128: Certificate missing issuer

Cause: The certificate that is being used was missing issuer information.

Action: Use a trusted certificate.
Level: 1

Type: ERROR

Impact: Process

B2B-51143: Certificate expired

Cause: The certificate has expired.

Action: 1. Make sure host and trading partner has selected the local time zone, 2. If the time zone is correct request the trading partner to generate a new certificate.
Level: 1

Type: ERROR

Impact: Process

B2B-51145: Certificate is not valid yet.

Cause: Certificate was not valid. Because the certificate creation date was later than current system date.

Action: 1. Make sure Host and trading partner has selected the local time zone 2. System current date is later than certificate creation date.
Level: 1

Type: ERROR

Impact: Process

B2B-51147: Missing recipient information

Cause: Missed recipient information.

Action: Ask the trading partner to check the recipient certificate added during encryption and request for a re-send.
Level: 1

Type: ERROR

Impact: Process

B2B-51150: Failed to verify certificate chain.

Cause: Unable to verify the certificate chain while processing the message.

Action: Verify the certificates used and request a re-send.
Level: 1

Type: ERROR

Impact: Process

B2B-51152: CRL verification failed

Cause: CRL verification failed.

Action: CRL received not matching with the certificates in the keystore. Request the trading partner to send the correct CRL.
Level: 1

Type: ERROR

Impact: Process

B2B-51153: Certificate revoked

Cause: Certificate revoked.

Action: Request a re-send with the valid certificate from the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-51154: Certificate signature verification failed.

Cause: Failed to verify the certificate signature.

Action: Request for the valid certificate from the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-51165: Digest algorithm missing.

Cause: Message received with incorrect digest algorithm.

Action: Request a re-send from the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-51193: Failed to open keystore.

Cause: Keystore file was not in correct format, incorrect location or incorrect password.

Action: Make sure the keystore is generated properly or the location or password is correct.
Level: 1

Type: ERROR

Impact: Process

B2B-51195: Failed to get key pair from keystore

Cause: Unable to retrieve key pair from the keystore.

Action: Verify that the keystore has valid key pair.
Level: 1

Type: ERROR

Impact: Process

B2B-51197: LDAP error

Cause: LDAP error

Action: Check the LDAP details.
Level: 1

Type: ERROR

Impact: Process

B2B-51198: LDAP connect failed.

Cause: LDAP connect failed.

Action: Check the LDAP details.
Level: 1

Type: ERROR

Impact: Process

B2B-51199: LDAP bind failed.

Cause: LDAP bind failed.

Action: Check the LDAP details.
Level: 1

Type: ERROR

Impact: Process

B2B-51200: LDAP search failed.

Cause: LDAP search failed.

Action: Check the LDAP details.
Level: 1

Type: ERROR

Impact: Process

B2B-51201: LDAP entry missing attribute.

Cause: LDAP entry missing attribute.

Action: Check the LDAP details.
Level: 1

Type: ERROR

Impact: Process

B2B-51202: No certificate in the directory for this user

Cause: Unable to retrieve the certificate for this user from the directory.

Action: Make sure that the certificate is available in the directory.
Level: 1

Type: ERROR

Impact: Process

B2B-51203: Error compressing data.

Cause: An error has occurred while compressing data.

Action: Check the payload.
Level: 1

Type: ERROR

Impact: Process

B2B-51204: Error decompressing data.

Cause: An error has occurred while compressing data.

Action: Check the payload received or request for re-send from the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-51205: The alias is not present or configured incorrectly in partner profile

Cause: The alias is not present or configured incorrectly in partner profile.

Action: Make sure that the alias is available in the partner profile.
Level: 1

Type: ERROR

Impact: Process

B2B-51206: Validation of signatures or checks on the authenticity or authority of the sender of the message have failed.

Cause: Alias is present but received message is unsigned

Action: Make sure received message is signed
Level: 1

Type: ERROR

Impact: Process

B2B-51207: Database Connection Failed.

Cause: Database Connection failed.

Action: Check the Datasource details.
Level: 1

Type: ERROR

Impact: Process

B2B-51208: SQL Exception occured during JDBC processing

Cause: SQL Exception occured during JDBC processing.

Action: Check the Datasource details.
Level: 1

Type: ERROR

Impact: Process

B2B-51300: Interface Sequencing failure - Inbound sequence row not present for correlation

Cause: Inbound sequence row not present for correlation.

Action: Check if the group count is configured incorrectly or if the sequence row was discarded.
Level: 1

Type: ERROR

Impact: Process

B2B-51500: Document exchange success.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

B2B-51501: Document exchange initialization failure.

Cause: Failed to initialize the document specific guidelines.

Action: Verify the document specific initialization parameters.
Level: 1

Type: ERROR

Impact: Process

B2B-51503: General create message error.

Cause: Failed to create message components.

Action: Verify values for message creation components.
Level: 1

Type: ERROR

Impact: Process

B2B-51504: General decode error.

Cause: Failed to decode the message.

Action: Verify the incoming message contents.
Level: 1

Type: ERROR

Impact: Process

B2B-51505: General validation error.

Cause: An unexpected error occurred during validation.

Action: Verify the validity of the document against the document definition.
Level: 1

Type: ERROR

Impact: Process

B2B-51506: Message digest validation error.

Cause: Message digest obtained from the incoming message payload, did not match with the original message digest.

Action: Verify the digest algorithm.
Level: 1

Type: ERROR

Impact: Process

B2B-51507: Payload validation error.

Cause: An error occurred during message payload processing in document plug-in.

Action: Verify the message payload validity against the document definition.
Level: 1

Type: ERROR

Impact: Process

B2B-51508: Validation of Group parameters failed. Verify all the Group parameters in the B2B configuration match the Group parameters in the message. The following parameters do not match the configured parameters in system. {0}

Cause: Validation of Group parameters failed. Verify all the Group parameters in the B2B configuration match the Group parameters in the message. The following parameters do not match the configured parameters in system.{0}

Action: Verify the EDI group header parameters of the message validity against the document definition.
Level: 1

Type: ERROR

Impact: Process

B2B-51509: Create message error: component- {0}.

Cause: Failed to create message components.

Action: Verify all components of the message.
Level: 1

Type: ERROR

Impact: Process

B2B-51510: Validation of Batch header parameters failed. Verify all the Batch header parameters in the B2B configuration match the Batch header parameters in the message. Following parameters are not matching with the configured parameters in system.

Cause: Validation of Batch header parameters failed. Verify all the Batch header parameters in the B2B configuration match the Batch header parameters in the message. Following parameters are not matching with the configured parameters in system.

Action: Verify the batch message payload validity against the document definition.
Level: 1

Type: ERROR

Impact: Process

B2B-51511: Validation of Interchange parameters failed. Verify all the Interchange parameters in the B2B configuration match the Interchange parameters in the message. Following parameters are not matching with the configured parameters in system.{0}

Cause: Validation of Interchange parameters failed. Verify all the Interchange parameters in the B2B configuration match the Interchange parameters in the message. Following parameters are not matching with the configured parameters in system.{0}

Action: Verify the EDI Interchange header parameters of the message validity against the document definition
Level: 1

Type: ERROR

Impact: Process

B2B-51512: Message payload parameter validation error.

Cause: Document parameters validation failed.

Action: Verify the parameters of the message against the document protocol parameters.
Level: 1

Type: ERROR

Impact: Process

B2B-51513: Validation of Interchange parameters failed. Verify all the Interchange parameters in the B2B configuration match the Group parameters in the message. Make sure that the ecs file for this Interchange is valid.

Cause: Validation of Interchange parameters failed. Verify all the Interchange parameters in the B2B configuration match the Group parameters in the message. Make sure that the ecs file for this Interchange is valid.

Action: Verify the EDI Interchange header parameters of the message validity against the document definition
Level: 1

Type: ERROR

Impact: Process

B2B-51514: Validation of Message header parameters failed. Verify all the Message header parameters in the configuration match the Message header parameters in the message. Following parameters are not matching with the configured parameters.

Cause: An error occurred in message header of document during message processing.

Action: Verify all the Message header parameters in the configuration match the Message header parameters in the message. Following parameters are not matching with the configured parameters.
Level: 1

Type: ERROR

Impact: Process

B2B-51515: Validation of parameters failed. Some or all of the following parameters do not match the configured parameters in B2B.

Cause: Document parameters validation failed.

Action: Verify the parameters of the message against the document protocol parameters.
Level: 1

Type: ERROR

Impact: Process

B2B-51516: Validation of File header parameters failed. Verify all the File header parameters in the B2B configuration match the File header parameters in the message. Following parameters are not matching with the configured parameters in system.

Cause: Validation of File header parameters failed. Verify all the File header parameters in the B2B configuration match the File header parameters in the message. Following parameters are not matching with the configured parameters in system.

Action: Verify all the File header parameters in the B2B configuration match the File header parameters in the message. Following parameters are not matching with the configured parameters in B2B.
Level: 1

Type: ERROR

Impact: Process

B2B-51520: Validation of Interchange parameters failed. Following parameters are not matching with the configured parameters in B2B. {0}

Cause: Validation of Interchange parameters failed. Following parameters are not matching with the configured parameters in B2B. {0}

Action: Verify the document Interchange parameters parameters of the message validity against the document definition
Level: 1

Type: ERROR

Impact: Process

B2B-51550: Invalid usage code.

Cause: Specified usage code was neither production nor test.

Action: Verify that the usage code is either production or test.
Level: 1

Type: ERROR

Impact: Process

B2B-51551: Invalid timestamp.

Cause: Timestamp was not in the correct format.

Action: Correct timestamp format is CCYYMMDDThhmmss.sssZ.
Level: 1

Type: ERROR

Impact: Process

B2B-51552: Mismatch in the PIP binding ID.

Cause: PIP binding ID in the initiating message did not match the PIP binding ID in the response message.

Action: Ensure that the PIP binding ID in the initiating message matches the PIP binding ID in the response message.
Level: 1

Type: ERROR

Impact: Process

B2B-51553: Mismatch in PIP code.

Cause: PIP code in the initiating message did not match the PIP code in the response message.

Action: Ensure that PIP Code in the initiating message matches the PIP code in the response message.
Level: 1

Type: ERROR

Impact: Process

B2B-51554: Mismatch PIP in instance ID.

Cause: PIP instance ID in the initiating message did not match the PIP instance ID in the response message.

Action: Ensure that the PIP instance ID in the initiating message matches the PIP instance ID in the responding message.
Level: 1

Type: ERROR

Impact: Process

B2B-51555: Mismatch in PIP version.

Cause: PIP version in the initiating message did not match the PIP version in the response message.

Action: Ensure that PIP version in the initiating message matches the PIP version in the response message.
Level: 1

Type: ERROR

Impact: Process

B2B-51556: Invalid response message.

Cause: Message ID in the initiating message did not match the message ID in the RefTo field of the response message.

Action: Ensure that message ID in the initiating message matches the message ID in the RefTo field of the response message.
Level: 1

Type: ERROR

Impact: Process

B2B-51557: PIP binding ID exceeds 255 characters.

Cause: PIP binding ID cannot exceed 255 characters.

Action: Limit the total characters of PIP binding ID to 255.
Level: 1

Type: ERROR

Impact: Process

B2B-51558: Invalid value for secure transport required attribute.

Cause: Secure transport was neither Yes nor No.

Action: Ensure that the secure transport has values Yes or No.
Level: 1

Type: ERROR

Impact: Process

B2B-51559: Mismatch in manifest content-type.

Cause: Content-type in the manifest did not match the content-type associated with the attachment.

Action: Ensure that the content-type in the manifest and attachment are the same.
Level: 1

Type: ERROR

Impact: Process

B2B-51560: Mismatch in manifest content-ID.

Cause: Content-ID in the manifest did not match the content-ID associated with the attachment.

Action: Ensure that the content-ID in the manifest matches the content-ID associated with the attachment.
Level: 1

Type: ERROR

Impact: Process

B2B-51561: Mismatch in the service of the host and the trading partner.

Cause: FromService field in the initiating message did not match the ToService field in the response message.

Action: Verify the FromService field of the host matches with ToService field of the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-51562: Mismatch in the service of the host and the trading partner.

Cause: ToService field in the initiating message did not match the FromService field in the response message.

Action: Verify the ToService field of the host matches with FromService of the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-51563: Mismatch in the role of the host and the trading partner.

Cause: FromRole field in the initiating message did not match the ToRole field in the response message.

Action: Verify the FromRole field of the host matches with ToRole field of the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-51564: Mismatch in the role of the host and the trading partner.

Cause: ToRole field in the initiating message did not match the FromRole field in the response message.

Action: Verify the ToRole field of the host matches with FromRole field of the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-51565: An unexpected error occurred while initializing the XML parser.

Cause: Failed to initialize XML parser.

Action: Ensure that the XML parser initialized properly.
Level: 1

Type: ERROR

Impact: Process

B2B-51566: Parse stream error

Cause: An unexpected error occurred while parsing the input stream.

Action: Verify the message components of incoming message.
Level: 1

Type: ERROR

Impact: Process

B2B-51567: Invalid Content-Type

Cause: Sub-type of the Content-Type in the HTTP header was neither Multipart/related nor Multipart/signed.

Action: Check for the Content-Type in the HTTP header.
Level: 1

Type: ERROR

Impact: Process

B2B-51568: encoding error

Cause: An unexpected error occurred while encoding data.

Action: Verify encoded type is base64.
Level: 1

Type: ERROR

Impact: Process

B2B-51569: decoding error

Cause: An unexpected error occurred while decoding data.

Action: Verify the decode type is base64.
Level: 1

Type: ERROR

Impact: Process

B2B-51570: Attachment error

Cause: An unexpected error occurred while creating an attachment as component data.

Action: Verify the well-form of the XML content for attachment.
Level: 1

Type: ERROR

Impact: Process

B2B-51571: Attachment error

Cause: An unexpected error occurred while forming an attachment as XML data.

Action: Verify that the XML format of the data for the attachment is well-formed XML. Also verify the encoding and type attributes of attachment.
Level: 1

Type: ERROR

Impact: Process

B2B-51572: Error reading input stream.

Cause: An unexpected error occurred while reading the input stream.

Action: Ensure the input value is nonempty.
Level: 1

Type: ERROR

Impact: Process

B2B-51573: Unexpected payload file naming, default format is <FromPartyName>_<MessageID>.<Extension> e.g. Sun_1234235.dat

Cause: Payload file name was not as per expected naming convention.

Action: Expect default format is <FromPartyName>_<MessageID>.<Extension> e.g. Sun_1234235.dat.
Level: 1

Type: ERROR

Impact: Process

B2B-51574: Error loading XEngine libraries. XEngine is most likely not installed.

Cause: XEngine was not installed.

Action: Make sure XEngine is installed.
Level: 1

Type: ERROR

Impact: Process

B2B-51575: Incorrect document exchange version.

Cause: Document exchange version mismatch.

Action: Verify the document exchange header value.
Level: 1

Type: ERROR

Impact: Process

B2B-51576: Incorrect document exchange.

Cause: Document exchange mismatch.

Action: Verify the document exchange name.
Level: 1

Type: ERROR

Impact: Process

B2B-51577: Document exchange validation error

Cause: Document exchange validation failed.

Action: Verify the document exchange header values
Level: 1

Type: ERROR

Impact: Process

B2B-51703: Failed to unpack the message.

Cause: An unexpected error occurred during the unpackaging of the RosettaNet business message.

Action: Verify the message headers.
Level: 1

Type: ERROR

Impact: Process

B2B-51705: Unable to read the preamble.

Cause: Failed to read preamble.

Action: Ensure the correctness of preamble content.
Level: 1

Type: ERROR

Impact: Process

B2B-51707: Unable to read the delivery header.

Cause: Failed to read delivery header.

Action: Ensure the correctness of the delivery header content.
Level: 1

Type: ERROR

Impact: Process

B2B-51709: Unable to read the service header.

Cause: Failed to read the service header.

Action: Ensure the correctness of the service header.
Level: 1

Type: ERROR

Impact: Process

B2B-51715: Failed to unpack the message - reading the service content.

Cause: Failed to read the service content.

Action: Ensure the correctness of the service content.
Level: 1

Type: ERROR

Impact: Process

B2B-51915: No type is specified in party ID.

Cause: No type was specified in party ID.

Action: Specify a party ID type.
Level: 1

Type: ERROR

Impact: Process

B2B-51916: Reference ID in the manifest does not match payload ID.

Cause: Reference ID in the manifest did not match payload ID.

Action: Make sure that reference ID in the manifest matches the payload ID.
Level: 1

Type: ERROR

Impact: Process

B2B-51917: Content-Type set for ebMS message is incorrect.

Cause: Content-Type set for ebMS message was incorrect.

Action: Set a valid Content-Type for the ebMS message.
Level: 1

Type: ERROR

Impact: Process

B2B-51918: This version of ebMS is not supported. Only version 2.0 is supported.

Cause: This version of ebMS was not supported. Only version 2.0 is supported.

Action: Make sure to exchange messages for the supported version.
Level: 1

Type: ERROR

Impact: Process

B2B-51919: Hub mode not supported.

Cause: As Hub mode was not supported, the actor value is incorrect.

Action: Specify the actor as urn:oasis:names:tc:ebXML-msg:actor:toPartyMSH
Level: 1

Type: ERROR

Impact: Process

B2B-51921: SOAP message has defective packaging.

Cause: Defect identified in packaging of the SOAP message.

Action: Make sure that the message is a valid SOAP message.
Level: 1

Type: ERROR

Impact: Process

B2B-51922: If the service type is not specified then the service must be a URI.

Cause: If the service type was not specified then the service must be a URI.

Action: Specify a service URI if the service type is not specified.
Level: 1

Type: ERROR

Impact: Process

B2B-51923: Value {0} for the element {1} is not recognized.

Cause: Failed to recognise value for the element.

Action: Specify a correct value for the element.
Level: 1

Type: ERROR

Impact: Process

B2B-51924: Message failed the security check.

Cause: Message failed the security check.

Action: Verify that the message has been encrypted and signed with the correct credentials.
Level: 1

Type: ERROR

Impact: Process

B2B-51925: Feature {0} is not supported.

Cause: Selected feature is not supported.

Action: Make sure the feature is currently supported.
Level: 1

Type: ERROR

Impact: Process

B2B-51926: SyncReply element must exist in the message.

Cause: SyncReply element must be present in the message.

Action: Add a SyncReply element in the message.
Level: 1

Type: ERROR

Impact: Process

B2B-51927: Time to live has expired for the message.

Cause: Time to live has expired for the message.

Action: Make sure to send a message with a valid time to live value.
Level: 1

Type: ERROR

Impact: Process

B2B-51928: Message header validation failed. The received {0} does not match with the configured {1}.

Cause: Message header did not have the element.

Action: Make sure to add element to the message header.
Level: 1

Type: ERROR

Impact: Process

B2B-51929: No payload is found for the reference ID {0}.

Cause: No payload attached for the reference ID.

Action: Make sure to have a payload for the reference ID, or remove this reference ID from the message.
Level: 1

Type: ERROR

Impact: Process

B2B-51930: Message with ID {0} is a duplicate message.

Cause: Duplicate message identified with same ID.

Action: Make sure to send a message with a unique message ID, a message which is not duplicated.
Level: 1

Type: ERROR

Impact: Process

B2B-51931: Error found in decrypting or verifying the message.

Cause: Error in decryption or on message verification.

Action: Make sure that the message is being decrypted and verified with the correct credentials.
Level: 1

Type: ERROR

Impact: Process

B2B-51932: Multiple parts with same Content-ID or Content-Location header.

Cause: Multiple parts with same Content-ID or Content-Location header.

Action: Use different Content-ID or Content-Location header values for different MIME parts of the message.
Level: 1

Type: ERROR

Impact: Process

B2B-51933: Referenced Content-ID or Content-Location header not found.

Cause: Referenced Content-ID or Content-Location header not found.

Action: Make sure that the referenced Content-ID or Content-Location header values are valid.
Level: 1

Type: ERROR

Impact: Process

B2B-51934: Unhandled attachment object {0} found.

Cause: Unhandled attachment object found.

Action: Make use of correct attachment type for attaching objects.
Level: 1

Type: ERROR

Impact: Process

B2B-51935: Error in resolving the content ID reference.

Cause: Failed to resolve the content ID reference.

Action: Make sure that the content ID reference is valid.
Level: 1

Type: ERROR

Impact: Process

B2B-51936: Signed acknowledgement requested, but not configured in delivery channel.

Cause: Signed acknowledgement requested, but not configured in delivery channel.

Action: Make sure that the sign acknowledgement is configured in delivery channel.
Level: 1

Type: ERROR

Impact: Process

B2B-52250: Error decoding incoming message at MLLP exchange.

Cause: Message received consists of more than one part or component.

Action: Check the payload to make sure it has only one part/component.
Level: 1

Type: ERROR

Impact: Process

B2B-52251: Error identifying remote trading partner at MLLP exchange with MLLP ID {0}.

Cause: MLLP ID received from in the message header did not exist.

Action: Make sure that the MLLP ID of the remote trading partner is configured as in the trading partner identification section or the anonymous trading partner is configured.
Level: 1

Type: ERROR

Impact: Process

B2B-52252: Only one trading partner in the system can have hosted=true.

Cause: More than one trading partner has hosted=true.

Action: Make sure only one trading partner in the system has hosted=true.
Level: 1

Type: ERROR

Impact: Process

B2B-52253: Trading partner {0} must have trading partner name as one of the identification.

Cause: Trading partner must have trading partner name as one of the identification.

Action: Make sure trading partner has an identification with value as name of trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-52254: Delivery channel {0} must have exchange protocol, if listening=false.

Cause: Delivery channel did not have exchange protocol.

Action: Make sure delivery channel has exchange protocol.
Level: 1

Type: ERROR

Impact: Process

B2B-52255: Certificate alias not specified in the secure delivery channel {0}.

Cause: Security was enabled in delivery channel, but no certificate alias specified.

Action: Make sure certificate alias specified in the delivery channel.
Level: 1

Type: ERROR

Impact: Process

B2B-52256: In delivery channel {0}, Transport protocol {1} is not supported by exchange protocol {2}.

Cause: Specified transport protocol was not supported by exchange protocol.

Action: Choose transport protocol which is supported by exchange protocol.
Level: 1

Type: ERROR

Impact: Process

B2B-52257: In delivery channel {0}, algorithm {1} is not supported for exchange protocol {2}.

Cause: Specified algorithm was not supported by exchange protocol.

Action: Choose algorithm which is supported by exchange protocol.
Level: 1

Type: ERROR

Impact: Process

B2B-52258: In delivery channel {0}, exchange protocol parameter {1} is not supported for exchange protocol {2}.

Cause: Selected exchangeProtocolParameter was not part of the specified exchange protocol.

Action: Select specified exchangeProtocol and re-save again in UI.
Level: 1

Type: ERROR

Impact: Process

B2B-52259: In delivery channel {1}, exchange protocol {0} has to have acknowledge mode as ASYNC or NONE.

Cause: RNIF exchange protocol did not support SYNC acknowledge mode.

Action: Verify RNIF exchange protocol has acknowledge mode as ASYNC or NONE.
Level: 1

Type: ERROR

Impact: Process

B2B-52260: effectiveToDate {0} in agreement {1} must be a date in the future.

Cause: Date specified in effectiveToDate was not a future date.

Action: Ensure that the effectiveToDate in the agreement is a date in the future.
Level: 1

Type: ERROR

Impact: Process

B2B-52261: The effectiveFromDate {0} should be less than effectiveToDate {1} in agreement {2}.

Cause: The effectiveFromDate should be less than effectiveToDate.

Action: Make sure the effectiveFromDate is less than effectiveToDate.
Level: 1

Type: ERROR

Impact: Process

B2B-52262: Agreement {0} does not have a host and trading partner.

Cause: Agreement did not have a host and trading partner.

Action: Make sure agreement has a host and trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-52263: One of the participants must be a host in an agreement {0}.

Cause: None of the participants was host in agreement.

Action: Make sure a participant in agreement is host.
Level: 1

Type: ERROR

Impact: Process

B2B-52264: Document type name {0} and document protocol version {1} used in agreement {2} are not in sync with the corresponding definition in trading partner {3}.

Cause: Document type name and document protocol version used in agreement were not in sync with the corresponding definition in trading partner.

Action: Make sure agreement has document type name and document type version as given in trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-52265: DUNS identification value {0} must be 9 digit.

Cause: DUNS identification was not have value in 9 digit.

Action: Verify DUNS identification has value in 9 digit.
Level: 1

Type: ERROR

Impact: Process

B2B-52266: Identification type {0} and value {1} must be unique in the trading partner.

Cause: Identification type and value occurred more than once in the trading partner.

Action: Make sure type and value of identification unique in the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-52267: Only one exchange protocol can have default=true.

Cause: More than one exchange protocol has default=true.

Action: Make sure only one exchange protocol has default=true.
Level: 1

Type: ERROR

Impact: Process

B2B-52268: Only one document protocol can have default=true.

Cause: More than one document protocol has default=true.

Action: Make sure only one document protocol has default=true.
Level: 1

Type: ERROR

Impact: Process

B2B-52269: Participant {0} cannot have more than one identification of the same type {1}.

Cause: Participant has more than one identification of the same type.

Action: Make sure participant is not referring to more than one identification of same type.
Level: 1

Type: ERROR

Impact: Process

B2B-52270: Participant {0} identification reference {1} is not part of same trading partner identification.

Cause: Participant refer to some other trading partner identification.

Action: Make sure identification referred in participant is part of same trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-52271: Participant {0} delivery channel reference {1} is not part of same trading partner.

Cause: Participant delivery channel reference was not part of either same trading partner or host.

Action: Make sure delivery channel referred in participant is part of trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-52272: Participant {0} document definition {1} is not part of same trading partner.

Cause: Participant document definition was not part of same trading partner.

Action: Make sure trading partner has specified document definition.
Level: 1

Type: ERROR

Impact: Process

B2B-52273: Participant {0} identification type {1} and value {2} are not synchronous with trading partner identification.

Cause: Participant identification type and value were not sync with trading partner identification.

Action: Make sure the value and type given in identification reference in participant is synchronous with trading partner identification.
Level: 1

Type: ERROR

Impact: Process

B2B-52274: Participant {0} can have only one exchange identifier.

Cause: Participant has more than one exchange identification.

Action: Make sure only one exchange identification found in participant.
Level: 1

Type: ERROR

Impact: Process

B2B-52275: Type of the parameter {0} must match with the default value {1}.

Cause: Parameter type and default value type mismatched.

Action: Check the type and value of parameter are same type.
Level: 1

Type: ERROR

Impact: Process

B2B-52276: Type of the parameter {0} must match with the value.

Cause: Parameter type and given value mismatched.

Action: Check the type and value of parameter are same type.
Level: 1

Type: ERROR

Impact: Process

B2B-52277: Only Custom document protocol can set custom attribute equal to true.

Cause: Other than custom document protocol has custom attribute set to true.

Action: Make sure only custom document protocol has this attribute set to true.
Level: 1

Type: ERROR

Impact: Process

B2B-52278: Document protocol {0} must have ID {1} starts with doc_

Cause: Document protocol has ID which did not start with doc_

Action: Make sure document protocol has ID starts with doc_
Level: 1

Type: ERROR

Impact: Process

B2B-52279: Document protocol {0} reference must be doc_id.xml

Cause: Document protocol reference was not in the form of doc_id.xml

Action: Make sure document protocol reference is in the form of doc_id.xml
Level: 1

Type: ERROR

Impact: Process

B2B-52280: Trading partner {0} must have at least one exchange identification.

Cause: None of the exchange identification found in trading partner.

Action: Add at least one exchange identification in trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-52281: Trading partner {0} must have ID {1} starts with tp_

Cause: Trading partner has ID which did not start with tp_

Action: Make sure trading partner has ID which starts with tp_
Level: 1

Type: ERROR

Impact: Process

B2B-52282: Trading partner {0} reference must be tp_id.xml

Cause: Trading partner reference was not in the form of tp_id.xml

Action: Make sure trading partner has reference in the form of tp_id.xml
Level: 1

Type: ERROR

Impact: Process

B2B-52283: In delivery channel {0}, certificate alias {1} not found in the keystore.

Cause: Given certificate alias did not exist in the keystore.

Action: Verify certificate alias is present in the keystore.
Level: 1

Type: ERROR

Impact: Process

B2B-52284: Delivery channel {0} which has transport protocol {1} cannot be a listening channel.

Cause: Selected transport protocol was not capable of listening

Action: Select listening transport to create listening delivery channel
Level: 1

Type: ERROR

Impact: Process

B2B-52285: Internal delivery channel {0} must use generic exchange.

Cause: Internal delivery channel has other than generic exchange protocol.

Action: Make sure internal delivery channel uses generic exchange.
Level: 1

Type: ERROR

Impact: Process

B2B-52286: HTTP transport protocol must have a URL.

Cause: HTTP transport protocol did not have a URL.

Action: Make sure HTTP transport protocol has a URL.
Level: 1

Type: ERROR

Impact: Process

B2B-52287: Agreement {0} must have ID {1} starts with tpa_

Cause: Agreement has ID which did not start with tpa_

Action: Make sure agreement has ID which starts with tpa_
Level: 1

Type: ERROR

Impact: Process

B2B-52288: Agreement {0} reference must be tpa_id.xml

Cause: Agreement reference was not in the form of tpa_id.xml

Action: Make sure agreement has reference which is in the form of tpa_id.xml
Level: 1

Type: ERROR

Impact: Process

B2B-52289: Agreement {0} has document definition with mismatching initiator flag.

Cause: Agreement has document definition with mismatching initiator flag in trading partner.

Action: Make sure document definition is supported to send or receive by trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-52290: Agreement {0} must have exactly one supported document type.

Cause: Agreement has not exactly one supported document type.

Action: Make sure agreement has only one supported document type.
Level: 1

Type: ERROR

Impact: Process

B2B-52291: Duplicate agreement {0} found with same combination of trading partners {1}, {2}, and document type {3} and document protocol version {4}.

Cause: More than one agreement has same combination of trading partners, document type and version.

Action: Make sure only one agreement has same combination of trading partners, document type and version.
Level: 1

Type: ERROR

Impact: Process

B2B-52292: In agreement {0}, trading partner {1} must have a delivery channel.

Cause: The trading partner did not have delivery channel to send out bound message.

Action: Make sure in a agreement, the trading partner has a delivery channel to send out bound message.
Level: 1

Type: ERROR

Impact: Process

B2B-52293: In agreement {0}, the host {1} can refer to only the internal delivery channel.

Cause: Host refers to other than internal delivery channel.

Action: Make sure host is not referring to other than internal delivery channel.
Level: 1

Type: ERROR

Impact: Process

B2B-52294: In agreement {0}, participant {1} cannot have more than one delivery channel.

Cause: Participant has more than one delivery channel.

Action: Make sure only one delivery channel exist for participant.
Level: 1

Type: ERROR

Impact: Process

B2B-52295: At least one name identification type present in system.

Cause: Name identification type did not present in system.

Action: Check at least one name identification type present in system.
Level: 1

Type: ERROR

Impact: Process

B2B-52296: Exchange identification {0} must have a value.

Cause: Exchange identification did not have a value.

Action: Make sure all exchange identification has a value.
Level: 1

Type: ERROR

Impact: Process

B2B-52297: Packaging protocol reference {0} must point to packaging protocol element.

Cause: Packaging protocol reference refer to other than packaging protocol element.

Action: Verify packaging protocol reference refers to packaging protocol element.
Level: 1

Type: ERROR

Impact: Process

B2B-52298: Transport URL {0} already used in system.

Cause: More than once same endpoint used in system.

Action: Make sure same endpoint not attached with different delivery channel in system.
Level: 1

Type: ERROR

Impact: Process

B2B-52299: Participant {0} must have at least one exchange identification.

Cause: None of the exchange identification referred in participant.

Action: Make sure participant has at least one exchange identification.
Level: 1

Type: ERROR

Impact: Process

B2B-52300: Duplicate ID {0} found in node {1} and node {2}.

Cause: Duplicate unique ID found in two different nodes.

Action: Target system has element with the same , change ID of importing node.
Level: 1

Type: ERROR

Impact: Process

B2B-52301: MDSReference {0} is not referring to the trading partner.

Cause: MDSReference did not refer to the trading partner.

Action: Make sure given reference is pointing to the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-52302: MDSReference {0} is not referring to an agreement.

Cause: MDSReference did not refer to an agreement.

Action: Make sure given reference is pointing to an agreement.
Level: 1

Type: ERROR

Impact: Process

B2B-52303: Compressed file expected to import.

Cause: Given file was not compressed using ZIP format.

Action: Verify given file is in compressed in ZIP format.
Level: 1

Type: ERROR

Impact: Process

B2B-52304: Agreement {0} cannot have listening channels.

Cause: Listening channels referred in agreement.

Action: Verify agreement is not referring to any listening channels.
Level: 1

Type: ERROR

Impact: Process

B2B-52305: In agreement {0}, trading partner {1} cannot have internal delivery channel.

Cause: Trading partner has internal delivery channel(s).

Action: Make sure none of the trading partners has internal delivery channel.
Level: 1

Type: ERROR

Impact: Process

B2B-52306: Internal delivery channel {0} must not use HTTP transport.

Cause: Internal delivery channel has HTTP as transport.

Action: Make sure internal delivery channel is not using HTTP transport.
Level: 1

Type: ERROR

Impact: Process

B2B-52307: Listening delivery channel {0} must have a polling interval value.

Cause: Listening channel did not have value for polling interval.

Action: Make sure listening channel has polling interval value.
Level: 1

Type: ERROR

Impact: Process

B2B-52308: Listening delivery channel {0} with transport {1} does not have user name and password.

Cause: Listening delivery channel did not have user name and password in transport.

Action: Make sure listening delivery channel has user name and password in transport.
Level: 1

Type: ERROR

Impact: Process

B2B-52309: Validation error: see the diagnostic log for more details.

Cause: Unknown exception found in validation engine.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-52310: The XML {0} is not well-formed.

Cause: Given XML content was not well-formed.

Action: Check XML content is well-formed and valid based on XSD/DTD constraints.
Level: 1

Type: ERROR

Impact: Process

B2B-52311: New document protocol {0} found in source reference {1}.

Cause: New document protocol name found in import source.

Action: Check name of the document protocol is correct.
Level: 1

Type: ERROR

Impact: Process

B2B-52312: Document protocol {0} must have ID {1} starts with doc_

Cause: Document protocol has ID which did not start with doc_

Action: Make sure document protocol has ID which starts with doc_
Level: 1

Type: ERROR

Impact: Process

B2B-52313: Document protocol {0} reference must be doc_id.xml

Cause: Document protocol reference was not in the form of doc_id.xml

Action: Make sure document protocol has reference in the form of doc_id.xml
Level: 1

Type: ERROR

Impact: Process

B2B-52314: Repository host name {0} and source Host name {1} are different.

Cause: Different host name found in repository and source.

Action: Make host name as unique in source and target system, while doing import.
Level: 1

Type: ERROR

Impact: Process

B2B-52315: Duplicate identification type {1} and value {2} found in source trading partner {0}.

Cause: More than one identification type found in source trading partner(s) for a same value and type.

Action: Make sure combination of identification type and value unique in the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-52316: Pre-import transfer operation failed.

Cause: Pre-import validation(s) failed while importing.

Action: Check validation error messages found below this message and correct source files accordingly.
Level: 1

Type: ERROR

Impact: Process

B2B-52317: Duplicate identification type {1} and value {2} found in source agreement {0}.

Cause: More than one identification type found in source agreement(s) for a same value and type.

Action: Make sure combination of identification type and value unique in agreement.
Level: 1

Type: ERROR

Impact: Process

B2B-52318: MDSReference {0} does not exist in Repository.

Cause: Specified reference was not available in repository.

Action: Make sure specified reference is available in repository.
Level: 1

Type: WARNING

Impact: Process

B2B-52319: Transfer error: see log for more details.

Cause: Unknown exception identified in transfer.

Action: Check the diagnostic log. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-52320: In agreement {0}, functional acknowledge can be enabled only when translate=true.

Cause: Agreement has functional acknowledge with translate flag set to inactive.

Action: Functional acknowledge can be active only when translate is active.
Level: 1

Type: ERROR

Impact: Process

B2B-52321: No metadata found to import.

Cause: No metadata identified in recommended package.

Action: Check given import file has metadata in correct package.
Level: 1

Type: ERROR

Impact: Process

B2B-52322: Mandatory field {0} is missing in {1}.

Cause: Metadata might be imported without all mandatory fields.

Action: Import metadata with all mandatory fields or save again the business object which has error, using UI.
Level: 1

Type: ERROR

Impact: Process

B2B-52323: Out-bound agreement {0} has to have only one exchange identifier type - {1}, in both participants

Cause: Out-bound agreement has more than one exchange identifier, or has different type of exchange identifier which is not suitable to exchange protocol.

Action: Make sure given exchange identifier is supported by chosen exchange protocol in delivery channel.
Level: 1

Type: ERROR

Impact: Process

B2B-52324: Listening Delivery channel {0} has duplicate endpoint {1}

Cause: Already a delivery channel has same endpoint, hence new delivery channel cannot be activated with same endpoint.

Action: Make sure all listening channel endpoints are unique.
Level: 1

Type: ERROR

Impact: Backup and Recovery

B2B-52325: Error in the SOA Composite {0}

Cause: See the base error message in the SOA Composite.

Action: Correct the error in the Fabric Composite.
Level: 1

Type: ERROR

Impact: Process

B2B-52326: Transport protocol with HTTPs URL has to have valid keystore location and password in host

Cause: Valid keystore location and password was not specified in host.

Action: Check with administrator, whether valid keystore location specified in host.
Level: 1

Type: ERROR

Impact: Process

B2B-52327: Channel {0} with transport {1} should have Queue name along with either datasource or the combination of SID, port number, user name, host name and password.

Cause: AQ channel does not have required parameter values to connect to AQ queue.

Action: Provide AQ Queue name along with either datasource or the combination of SID, port number, user name, host name and password.
Level: 1

Type: ERROR

Impact: Process

B2B-52328: Channel {0} with transport {1} should have either password or the combination of private key file and pass phrase.

Cause: SFTP channel does not have required parameter values to connect to SFTP server.

Action: Provide either password or the combination of private key file and pass phrase.
Level: 1

Type: ERROR

Impact: Process

B2B-52329: Web Service outbound flow invocation error.

Cause: An abnormal condition occurred during outbound flow invocation.

Action: Review the SOAP Fault for the exact error and correct the same. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-52330: Error invoking translation Web Service.

Cause: An abnormal condition occurred during translation Web Service invocation.

Action: Review the SOAP Fault for the exact error and correct the same. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-52331: Translated content is not available

Cause: B2B metadata or XEngine configuration was invalid.

Action: Review the SOAP Fault for the exact error and correct the same. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-52332: Message is discarded and moved to error state with message id {0}

Cause: Message is discarded and moved to a error state based on a user input.

Action: Resubmit the message
Level: 3

Type: ERROR

Impact: Process

B2B-52333: received data from trading partner is too long

Cause: received data from trading partner is too long.

Action: resend hllp message where payload length should be less than or equal to 99994 bytes.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-52334: checksum validation failed

Cause: checksum validation failed for received data.

Action: resend hllp message with correct checksum value.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-52335: payload length is incorrect in received hllp packed message.

Cause: payload length is incorrect in received hllp packed message.

Action: resend hllp message with correct payload length.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-52336: validation of received hllp message failed

Cause: validation of received hllp message failed

Action: resend hllp message
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-52337: payload length is too large(>99994 bytes) at client side

Cause: payload length is too large(>99994 bytes) at client side

Action: resend hllp message with payload length less than or equal to 99994 bytes.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-52338: Negative Ack Received from trading partner.

Cause: received negative ack from trading partner

Action: resend hllp message
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-52339: Large Payload directory is inaccessible

Cause: Specified directory for large payload is inaccessible

Action: Ensure specified directory for large payload exists and it is write enabled
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-52340: Un-delivered Sequenced Message has been resubmitted. Moved to ERROR state

Cause: Un-delivered Sequenced Message has been resubmitted. Moved to error state

Action: N/A
Level: 3

Type: ERROR

Impact: Process

B2B-53001: Handler is null while registering a Webserve End point

Cause: The handler is null when registering an endpoint.

Action: Provide a valid handler implementation while registering an endpoint. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53002: Unable to find a registered handler for this end point.

Cause: Unable to process the message due to handler identification failure.

Action: Re-register a valid handler for the end point. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53003: Unable to register an endpoint.

Cause: Registration of the webservice end point failed.

Action: Review the log to evaluate the exact cause for failure. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53004: Unable to remove a registered end point

Cause: Removal of the webservice end point failed.

Action: Review the log to evaluate the exact cause for failure. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53005: Unable to package the payload to a SOAP message

Cause: Packing the payload into a message caused an exception.

Action: Review the log to evaluate the exact cause for failure. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53006: Unable to retrieve the payload from the SOAP message

Cause: Unpacking the soap message caused an exception.

Action: Review the log to evaluate the exact cause for failure. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53007: No payload component found in the message

Cause: No payload component found in the message

Action: Provide a payload component when enqueuing the message. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53008: Unable to create the SOAP Protocol components

Cause: Unable to create the SOAP Protocol components

Action: Review the log to evaluate the exact cause for failure. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53009: Unable to decode the soap message

Cause: Unable to decode the soap message

Action: Review the log to evaluate the exact cause for failure. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53010: An exception occurred while processing the received message.

Cause: Unable to process the SOAP message received in the transport layer.

Action: Review the log to evaluate the exact cause for failure. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53011: Duplicate message with same message id found in a batch. Changing original message id {0} to new message id {1} and rejecting the message.

Cause: Duplicate message with same message id found in a batch.

Action: Make sure that duplicate messages with same message id are not passed in the same batch.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

11 BEA-000001 to BEA-2163006

BEA-000001: Server must be started by Node Manager when consensus leasing is enabled.

Cause: The server was not started by Node Manager.

Action: Start the server using Node Manager.
Level: 1

Type: INTERNAL_ERROR

Impact: ConsensusLeasing

BEA-000002: Failed to initialize a Coherence cluster due to {0}

Cause: Failed to initialize a Coherence cluster due to {0}

Action: Take corrective action based on the exception details.
Level: 1

Type: ERROR

Impact: weblogic-coherence-integration

BEA-000003: Shutting down a Coherence cluster scoped to classloader {0}

Cause: Shutting down a Coherence cluster scoped to classloader {0}

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: weblogic-coherence-integration

BEA-000004: Failed to shut down a Coherence cluster due to {0}

Cause: Failed to shut down a Coherence cluster due to {0}

Action: Take corrective action based on the exception details.
Level: 1

Type: ERROR

Impact: weblogic-coherence-integration

BEA-000005: Deployed a GAR ({0}) without a CoherenceClusterSystemResourceMBean definition on this server.

Cause: Deployed a GAR ({0}) without a CoherenceClusterSystemResourceMBean definition on this server.

Action: Create a CoherenceClusterSystemResourceMBean appropriately and associate it with the server, or the cluster of which this server is a member.
Level: 1

Type: WARNING

Impact: weblogic-coherence-integration

BEA-000006: Using localhost as the ListenAddress when generating a Coherence WKA list will not operate correctly across multiple machines.

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

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

Type: NOTIFICATION

Impact: weblogic-coherence-integration

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

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

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

Type: NOTIFICATION

Impact: weblogic-coherence-integration

BEA-000101: Cannot resolve ClusterAddress: {0}

Cause: The cluster address {0} could not be resolved. ClusterAddress should be a DNS name that maps to multiple IP addresses.

Action: Set the correct ClusterAddress property for the cluster.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000102: Joining cluster {0} on {1}:{2}

Cause: The server has joined cluster {0}.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000103: Disconnecting from cluster {0}

Cause: When a server is suspended, it is no longer a member of cluster {0}.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000104: Cluster members are running incompatible versions. Local version: {0}. Remote version ({1}): {2}

Cause: This server is a different version than other servers in this cluster.

Action: Ensure that all members of this cluster are running the same version.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000105: The server is leaving the cluster because it is an incompatible version.

Cause: This server is running a different version of WebLogic Server.

Action: Set a different multicast address for this cluster. Use an address in the range of 224.0.0.0 - 239.255.255.255. Avoid the reserved range 224.0.0.0 - 224.0.1.255.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000107: Failed to install {0} in place of those currently installed due to {1}.

Cause: An error occurred while resolving non-local conflicting offers for a node in the JNDI tree.

Action: Check the preceding conflict start message in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000108: Attempt to retract offer {0}, which is neither installed nor pending.

Cause: An attempt was made to retract an offer, which was neither previously installed nor is in the conflict resolution stage.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000109: An error occurred while sending multicast message: {0}.

Cause: An error occurred while trying to send a message over multicast.

Action: WebLogic Server will try to recover from this error. If the problem continues to persist, make sure that the network infrastructure and NIC are functioning properly. If you believe no environment problems exist, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000110: Multicast socket receive error: {0}.

Cause: An error occurred while trying to receive a message over the multicast.

Action: Ensure that the NIC is functioning properly. If it appears that no environment problems exist, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000111: Adding {0} with ID {2} to cluster: {1} view.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000112: Removing {0} from cluster view due to timeout.

Cause: Removing {0} from cluster as it failed to send heartbeats over the multicast in the past 30 seconds.

Action: If a server has been shut down or suspended, no action is required. If the remote server {0} appears to be hung, take thread dumps and send them to My Oracle Support.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000113: Removing {0} from cluster view due to PeerGone.

Cause: The TCP/IP connection to server {0} was lost.

Action: If a server has been shut down or suspended, no action is required. If the remote server {0} appears to be hung, take thread dumps and send them to My Oracle Support.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000114: Failed to find cluster license: {0}

Cause: A valid license file is required to run clusters.

Action: Contact an Oracle sales representative for a valid license.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000115: Lost {0} multicast message(s).

Cause: This is an informational message. When a server joins a stable cluster, this message will appear since multicast messages sent out by servers in the cluster were not received.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000116: Failed to join cluster {0} at address {1} due to: {2}.

Cause: This happens if you specify an incorrect multicast address for the cluster. Use an address in the range of 224.0.0.0 - 239.255.255.255. Avoid the reserved range 224.0.0.0 - 224.0.1.255.

Action: Set a valid multicast address and try again.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000117: Received a stale replication request for object {0}.

Cause: This happens when a network problem exists, or one of the servers is taking a long time to collect garbage, causing the virtual machine to freeze.

Action: Tune garbage collection so that it does not pause. If the problem still persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000118: Lost {0} replication updates of object {1}.

Cause: If the secondary failed to receive some of the updates, it indicates this to the primary server by causing a NotFoundException to the primary so that the primary server can recreate the session state.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000119: Missing multicast address for cluster: {0}. Set the MulticastAddress="a.b.c.d" property for the cluster. Use an address in the range of 224.0.0.0 - 239.255.255.255. Avoid the reserved range 224.0.0.0 - 224.0.1.255.

Cause: The cluster does not have a defined multicast address.

Action: Specify a valid multicast address.
Level: 1

Type: INTERNAL_ERROR

Impact: Cluster

BEA-000120: Received error while creating ClusterRuntimeMBean.

Cause: The JMX framework failed to initialize the ClusterRuntimeMBean.

Action: Check the cluster configuration. If it appears that there are no configuration problems, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000121: Two domains in the same LAN should not use the same multicast address. Domains in conflict are {0} and {1}.

Cause: Two clusters on the local area network are using the same multicast address.

Action: Change the multicast address of either domain {0} or {1}.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000122: Clusters {0} and {1} cannot use the same multicast address.

Cause: Multiple clusters in the same domain are using the same multicast address.

Action: For efficiency purposes, use two different multicast addresses.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000123: Conflict start: You tried to bind an object under the name {0} in the JNDI tree. The object {1} is non-clusterable, and you have tried to bind more than once from two or more servers. Such objects can only be deployed from one server.

Cause: The cluster is not homogeneous. Two servers in the cluster are providing different services under the same name {0}. If the object is non-clusterable, only one server in the cluster can provide this service.

Action: There are various options. 1. Make the object clusterable. 2. Change the JNDI name of the object under which it is bound. 3. Make sure the object gets deployed only on one server. 4. Deploy the service on all the servers. However, binding it into the JNDI tree, set the replicate bindings property to false.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000124: Conflict start: The object {1} you tried to bind under the name {0} in the JNDI tree is clusterable but is incompatible. Ensure that all the servers in the cluster use an identical copy of the object.

Cause: The object {1} is clusterable. However, it implements different or incompatible interfaces on different servers.

Action: Ensure that all the servers in the cluster use an identical copy of the object.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000125: Conflict resolved: {0} for the object {1} under the bind name {0} in the JNDI tree.

Cause: Corrective action was taken to resolve the conflict.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000126: All session objects should be serializable to replicate. Check the objects in the session. Failed to replicate a non-serializable object.

Cause: Objects in the session are not serializable or externalizable.

Action: Ensure that all user-defined objects in the HTTP session are serializable.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000127: Adding {0} to the cluster.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000128: Updating {0} in the cluster.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000129: Removing {0} from the cluster.

Cause: This is an informational message.

Action: No action is required unless you did not shut down a server.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000133: Waiting to synchronize with other running members of {0}.

Cause: The cluster member is waiting to synchronize cluster information with other cluster members before completing startup and entering running mode.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000137: Error sending multicast message: {0}.

Cause: The multicast message failed to send due to an IOException.

Action: Enable cluster debugging to see a detailed message.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000138: Listening for announcements from cluster {0} on {1}:{2}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000139: There are two clusters in the network that are possibly running different versions of WebLogic Server. These two clusters probably have the same name {0} and they are using the same address {1} and port {2}.

Cause: There are two clusters in the network that are possibly running different versions of WebLogic Server. These two clusters probably have the same name {0} and they are using the same address {1} and port {2}.

Action: Change either the multicast address or the multicast port.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000140: Failed to deserialize statedump from server {0} with {1}.

Cause: The server failed to deserialize an object since it does not have the class definition. This usually happens if the application classes are not deployed on all the nodes in the cluster. It is preferable to deploy beans to all the nodes of the cluster.

Action: Ensure that all the classes are available on all the nodes of the cluster.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000141: TCP/IP socket failure occurred while fetching state dump over HTTP from {0}.

Cause: An IOException occurred in the operating system.

Action: Ensure that no problems exist in the network. If the problem persists, contact My Oracle Support with the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000142: Trying to download cluster JNDI tree from server {0}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000143: Trying to download JNDI tree from a server listening on {0}.

Cause: This is an informational message.

Action: If this message continues to appear, ensure that the network is stable. Contact My Oracle Support for further assistance.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000144: Managed Server {0} has been suspended or shut down.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000145: Managed Server {0} is tagged as a migratable server. A cluster that has migratable servers should configure a JDBC data source to ensure that the migratable server is highly available.

Cause: The cluster is misconfigured.

Action: Configure the DataSourceForAutomaticMigration property.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000147: Server "{0}" failed to renew lease in the {1}.

Cause: The server failed to renew the lease on time.

Action: No action is required.
Level: 1

Type: WARNING

Impact: Cluster

BEA-000148: Migratable server "{0}" is misconfigured. For automatic migration, a pool of machines should be assigned to the cluster or each migratable server in the cluster should have at least a couple of machines assigned to it for automatic migration.

Cause: The migratable server is misconfigured.

Action: Ensure that the server is targeted to a machine and restart the migratable server.
Level: 1

Type: WARNING

Impact: Cluster

BEA-000149: Server failed to get a connection to the {1} during {0}.

Cause: The database or the consensus leasing basis appears to be down.

Action: Ensure that the database is accessible to the cluster. In the case of consensus leasing basis the server is in the minority partition and the leasing basis is in some other partition that is not reachable.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000150: Server failed to get a connection to the {1} in the past {0} seconds for lease renewal. Server will shut itself down.

Cause: The database or consensus leasing basis appears to be down.

Action: Ensure that the database is accessible to the cluster. In the case of consensus leasing basis, the server is in the minority partition and the leasing basis is in some other partition that is not reachable.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000151: Server "{0}" has taken over the role of Cluster Master.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000152: Server "{0}" lost the privileges to be the Cluster Master.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000153: Cluster is misconfigured. For automatic migration, a pool of machines should be assigned to the cluster or each migratable server in the cluster should at least have a couple of machines assigned to it for automatic migration.

Cause: The cluster is misconfigured.

Action: Assign a pool of machines for automatic migration and refer to WebLogic Server documentation for more details.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000154: Cluster is misconfigured. The remote cluster address {0} is not a valid URL.

Cause: The server is misconfigured.

Action: Set the correct remote cluster address and restart the servers. If it is not clear on how to set remote ClusterAddress, refer to WebLogic Server documentation.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000155: Configured cluster address is invalid : {0}. Constructing cluster address dynamically.

Cause: The cluster configuration is invalid.

Action: Ensure that the cluster address contains either a DNS name or a comma-separated host list (or IP list) or a comma-separated host:port list (or IP:port list).
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000156: Could not send out new attributes for cluster member {0}: {1}.

Cause: There was a problem sending out changed member attributes.

Action: Examine the server logs.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000158: Server has stopped sending cluster heartbeats and announcements. It is still receiving heartbeats and announcements from other cluster members.

Cause: The server is going out of the cluster as a result of the suspend or shutdown operation.

Action: No action is required
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000159: The clocks of the machines hosting local server and remote server "{0}" are off by {1} seconds

Cause: The clocks of the machines hosting servers in the cluster are not synchronized.

Action: Ensure that all the machines are synchronized to the same time.
Level: 1

Type: WARNING

Impact: Cluster

BEA-000160: A request to synchronize the JNDI tree has been made over an insecure channel. Configure a secure HTTP channel for all of the servers in the cluster.

Cause: The cluster was configured to encrypt multicast data but the request to synchronize the JNDI tree was done on a non-secure channel (HTTP). To secure the cluster completely, configure a secure HTTP channel for all of the servers in the cluster.

Action: Configure a secure HTTP channel on all of the servers in the cluster.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000161: Multicast message from server {0} appears to have been tampered with.

Cause: The authenticity of the message could not be verified.

Action: Ensure that the network is not being hijacked.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000162: Starting "{0}" replication service with remote cluster address "{1}"

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000163: Stopping "{0}" replication service

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000164: Synchronized cluster JNDI tree from server {0}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000165: Some other domain has a cluster that is configured to use the same multicast address and port as a cluster in {0}. Two domains in the same LAN should not use the same multicast address.

Cause: Two clusters on the local area network are using the same multicast address.

Action: Change the multicast address of either domain.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000166: Some other cluster in this domain is configured to use the same multicast address as {0}. Clusters cannot use the same multicast address.

Cause: Multiple clusters in the same domain are using the same multicast address.

Action: For efficiency purposes, use two different multicast addresses.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000167: Some services failed to roll back successfully when trying to abort the migration: {0}.

Cause: An exception caused the rollback to fail: {0}.

Action: It would be safest to shut down this server so that any lingering services will stop. They will not be automatically restarted upon reboot. Once the cause of the rollback has been fixed, attempts to migrate to this server should be successful.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000168: Failed to restart/migrate server "{0}" because of {1}

Cause: There was an error while restarting migratable server: {1}

Action: Examine the server logs.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000170: The server {0} did not receive the multicast packets that it sent.

Cause: Each WebLogic Server instanec is expected to receive the messages it multicast to its multicast group. Since the server does not receive its own messages, the multicast address configuration in the cluster configuration or the interface address specification may be wrong.

Action: Ensure that the cluster configuration and server interface configuration are valid
Level: 1

Type: ERROR

Impact: Cluster

BEA-000171: Failed to load the custom Singleton Services SQL Query Helper: {0}, because of {1}.

Cause: The most likely cause for failing to load the named class is either a typo in the name of the class or that the class is missing from the server classpath.

Action: Ensure that the provided classname is valid and that the class exists in the classpath of the server.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000172: TCP/IP socket failure occurred while fetching state dump over HTTP from {0}. Error message received: {2}. The request was generated by {3}. {1}

Cause: An IOException occurred in the operating system.

Action: Ensure that no problems exist in the network. If the problem persists, contact My Oracle Support with the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000176: {0} does not specify a machine.

Cause: {0}'s configuration does not specify the machine on which it is running. Machines must be specified if scripts are to be executed when migrations happen.

Action: Specify the machine on which {0} is running in the server's console page.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000178: Failed to execute {0} because of {1}.

Cause: While trying to run {0}, an exception occurred: {1}.

Action: Check that the script, {0}, is fully debugged. It may help to run the script by hand to see if any errors are raised.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000179: {0} failed while altering its lease.

Cause: An exception occurred: {1}.

Action: Ensure that, if a database is being used for leasing, it is available.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000180: Unable to retrieve Job {0} from the database. The retrieval failed with {1}

Cause: An error occurred while reading a job from the database.

Action: ENsure that the classes corresponding to the job are present in the server classpath and are of the correct version.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000182: Job Scheduler created a job with ID {0} for TimerListener with description {1}

Cause: Job Scheduler created an entry in the database for a submitted job.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000183: Successfully cancelled job with ID {0}

Cause: Job Scheduler removed a job entry from the database based on application request

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000184: This server did not attempt to renew its lease for {0} seconds. The server may need to be restarted or migrated.

Cause: The thread that is supposed to regularly renew the lease has become blocked for some reason.

Action: Ensure that the server is not overloaded with work and that there are enough system resources available on the machine.
Level: 1

Type: WARNING

Impact: Cluster

BEA-000185: Despite the delay in the lease-renewing thread, the server has successfully renewed its lease. It is no longer in imminent risk of being migrated or restarted.

Cause: The thread that is supposed to regularly renew the lease became blocked, but is running properly again and has successfully renewed the lease.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000186: An error was encountered while migrating {0}: {1}

Cause: See the error in the message body.

Action: Ensure that there are enough candidate servers running in the cluster.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000187: The Singleton Service {0} is now registered on this server. This server may be chosen to host this service.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000188: The Singleton Service {0} is no longer registered on this server.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000189: The Singleton Service {0} is now active on this server.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000190: The Singleton Service {0} has been deactivated on this server.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000191: Now monitoring the Migratable Server {0}

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000192: A running server was not found to host {0}. The server will retry in a few seconds.

Cause: All running servers failed when asked to activate {0}.

Action: Ensure that there is at least one active candidate server for this service and that there is no bug in the activate() method. The service will be tried on all running servers in another few seconds.
Level: 1

Type: WARNING

Impact: Cluster

BEA-000193: The JTA service for {0} has failed, but {0} is still running. JTA cannot be migrated from a running server.

Cause: The JTA service failed.

Action: Check the logs of {0}; {0} should be restarted once the cause of the error has been determined and fixed. Upon restart, the JTA service will be migrated and running transactions recovered.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000194: An error was encountered while trying to report a migration event: {0}.

Cause: The most likely cause is the Administration Server being unavailable. If this is intended, this message can be ignored.

Action: If monitoring information is desired, the Administration Server should be running and reachable.
Level: 1

Type: WARNING

Impact: Cluster

BEA-000195: An error was encountered while trying to save a migration event. The error was: {0}.

Cause: An internal error occurred while trying to create a runtime MBean to encapsulate this data.

Action: Contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: WARNING

Impact: Cluster

BEA-000196: Received data about a migration of type {0}, but no such type is recognized by the Administration Server.

Cause: If the Managed Servers have been upgraded to a newer version of WebLogic Server, they may be reporting data that the Administration Server does not know how to handle.

Action: Upgrade the Administration Server to the same version as the cluster members.
Level: 1

Type: WARNING

Impact: Cluster

BEA-000197: Listening for announcements from cluster using unicast cluster messaging

Cause: Unicast cluster messaging mode is enabled.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000198: All replication calls for cluster {0} must be made over channel {1}

Cause: All replication calls for cluster {0} must be made over channel {1}

Action: Check the configured channel for replication calls.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000199: Replication calls can only be made by {0} over {1} channel

Cause: Replication calls can only be made by {0} over {1} channel

Action: Check the roles of the users for whom the replication calls are being made.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000214: WebLogic Server "{1}" version: {0} Copyright (c) 1995, 2011, Oracle and/or its affiliates. All rights reserved.

Cause: The startup banner used when a server starts.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000215: Loaded license: {0}.

Cause: This prints from the location from which the license file was loaded.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000220: Cannot shut down the server because the request was from a null user (Principal).

Cause: The server refused to shut down since the command came from an unauthorized user.

Action: Only users within the Administrators group can shut down the server. Retry the command with a user who has administrator credentials.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000221: Cannot shut down the server because the request was from a nameless user (Principal).

Cause: The server refused to shut down since the command came from an unauthorized user.

Action: Only users within the Administrators group can shut down the server. Retry the command with a user who has administrator credentials.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000222: Cannot disable server logins because the request was from a null user (Principal).

Cause: The server refused to lock itself since the command came from an unauthorized user.

Action: Retry the command with a user who has the privileges necessary to perform this operation.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000223: Cannot disable server logins because the request was from a nameless user (Principal).

Cause: The server refused to lock itself since the command came from an unauthorized user.

Action: Retry the command with a user who has the privileges necessary to perform this operation.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000224: Cannot enable server logins because the request was from a null user (Principal).

Cause: The server refused to unlock itself since the command came from an unauthorized user.

Action: Retry the command with a user who has the privileges necessary to perform this operation.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000225: Cannot enable server logins because the request was from a nameless user (Principal).

Cause: The server refused to unlock itself since the command came from an unauthorized user.

Action: Retry the command with a user who has the privileges necessary to perform this operation.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000226: The enabling of server logins has been requested by {0}.

Cause: The server has been requested to unlock itself and enable server logins again.

Action: No action is needed.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000227: Server logins have been enabled.

Cause: Server logins have been enabled.

Action: No action is needed.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000228: The disabling of server logins has been requested by {0}.

Cause: A LOCK command was issued by an administrator.

Action: No action is needed.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000229: Server logins have been disabled.

Cause: A LOCK command was issued by an administrator.

Action: No action is needed.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000231: Waiting {0} seconds for server shutdown.

Cause: A shutdown command was issued with a wait time. The server will wait the specified number of seconds before starting shutdown.

Action: A cancel shutdown command can be issued during the wait time to cancel the shutdown process. Otherwise no action is needed.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000232: Server shutdown is commencing now and is irreversible.

Cause: A shutdown command was issued by an administrator.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000236: Stopping execute threads.

Cause: An administrator issued a shutdown command.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000238: Shutdown has completed.

Cause: Shutdown has completed.

Action: No action needed.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000240: Cannot cancel the server shutdown because the request was from a null user (Principal).

Cause: Server shutdown could not be canceled because the user account that was used to issue the cancel command does not have the appropriate privileges.

Action: The command can only be executed by a user from the administrator group. Retry the command with a user account that has administrator privilieges.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000241: Cannot cancel the server shutdown because the request was from a nameless user (Principal).

Cause: Server shutdown could not be canceled because the user account that was used to issue the cancel command does not have the appropriate privileges.

Action: The command can only be executed by a user from the administrator group. Retry the command with a user account that has administrator privilieges.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000242: Cannot cancel server shutdown because there is no shutdown in progress.

Cause: The server shutdown cannot be canceled as the server is not in the state 'Shutdown in Progress'.

Action: No action is needed. Check the Administration Console for the state of the server.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000243: It is too late to cancel the server shutdown because the shutdown is already in progress.

Cause: The server has already started to shut down. It is too late to cancel shutdown at this point.

Action: No action is needed.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000244: Canceling server shutdown.

Cause: An administrator has issued a cancel shutdown operation.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000246: Server shutdown has been canceled and logins are enabled.

Cause: The cancel shutdown operation was successful.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000248: An exception occurred while trying to find a localized T3Srvr message, message ID {0}, {1}

Cause: The localized version of the message could not be found.

Action: No action is required.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000249: Because the weblogic.ConsoleInputEnabled property is set to true, the server can only be shut down from the command line. Type the command "shut" in the window in which the server was started.

Cause: The weblogic.ConsoleInputEnabled property was set true on the server startup command line.

Action: To shut down the server, type the command "shut" in the window in which the server was started.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000251: The server switched to the group "{0}".

Cause: A non-privileged group was specifed. The server switched to the specified group after starting.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000252: Cannot switch to the group "{0}". {1}

Cause: The server was unable to switch to the specified group.

Action: Ensure that the specified group exists.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000253: Switched to the user "{0}".

Cause: A non-privileged user was specified. The server switched to the specified user after starting.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000254: Cannot switch to the user "{0}". {1}

Cause: The server could not switch to the specified non-privileged user.

Action: Ensure that the specified user exists.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000256: Invoking {0}.main({1})

Cause: The server configuration specifies startup and shutdown classes to run.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000257: Exception reading command: {0}

Cause: An exception occurred while reading commands from the shell window.

Action: Disable the shell command input property weblogic.ConsoleInputEnabled.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000258: Command [{0}]

Cause: The Administration Console received the specified command and is about to execute it.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000259: Administration Console: profiling enabled.

Cause: Profiling has been enabled in the Administration Console.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000260: Administration Console: profiling disabled.

Cause: Profiling has been disabled in the Administration Console.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000261: The system user is not permitted to shut down, {0}.

Cause: The server was not shut down because the user is not authorized to shut down the server.

Action: See the exception text in {0} for more information on diagnosing the problem. See the previous log messages for more information on authorization failure. If the user does not have permission to shut down the server, but should, use the Administration Console to define a policy for this server that allows the user to shut down.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000262: No such command: {0}.

Cause: The unknown command was entered.

Action: Refer to the list of known commands.
Level: 1

Type: ERROR

Impact: WebLogicServer

BEA-000263: GC: before free/total={0}/{1} ({2}%).

Cause: The GS statistics are shown before forcing GC.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000264: GC: after free/total={0}/{1} ({2}%).

Cause: The GS statistics are shown after forcing GC.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000265: Attempt to unbind ClientContext "{0}" that is not bound.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000266: {0} has {1,choice,1#one pending ExecuteRequest|2#{1,number} pending ExecuteRequests}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000267: {0} had a negative workQueueDepth of {1}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000268: Failed to send unsolicted message "{0}" to client, {1}

Cause: Deprecated functionality

Action: Deprecated functionality
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000269: The connection to the client using "{0}" has been unexpectedly lost due to {1}. The server is initiating a hard disconnect.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000270: Timing out "{0}" because it was idle.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000271: Ignoring a repeated request to schedule the death of "{0}".

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000272: Scheduling the death of "{0}".

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000273: Removing "{0}" because of hard disconnect timeout.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000274: Removing "{0}" because of soft disconnect timeout.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000275: Soft disconnect pending for {0,choice,0#less than a minute|1#one minute|2#{0} minutes}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000276: Hard disconnect pending for {0,choice,0#less than a minute|1#one minute|2#{0} minutes}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000277: Idle disconnect pending for {0,choice,0#less than a minute|1#one minute|2#{0} minutes}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000283: Failed to marshal response, {0}

Cause: Deprecated functionality

Action: Deprecated functionality
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000284: Unexpected failure to marshal response, {0}

Cause: Deprecated functionality

Action: Deprecated functionality
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000286: Failed to invoke startup class "{0}", {1}.

Cause: An exception occurred in a startup class.

Action: Determine the error in the startup class code and restart the server. To work around the problem, set the "abort on startup failure" property to false.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000287: Invoking startup class: {0}.startup({1}).

Cause: The startup class was invoked with the specified arguments.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000288: {0} reports: {1}.

Cause: The return value of the startup class was logged.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000289: Failed to invoke shutdown class "{0}", {1}.

Cause: An exception occurred in a shutdown class.

Action: Determine the error in the shutdown class code and restart the server.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000290: Invoking shutdown class: {0}.shutdown({1}).

Cause: The server is invoking shutdown classes as a part of shutdown.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000291: {0} reports: {1}.

Cause: The server logs the return value of the shutdown class.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000297: Inconsistent security configuration, {0}

Cause: An exception occurred in SSL initialization.

Action: Look at the exception in {0} for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: WebLogicServer

BEA-000298: Certificate expires in {0} days: {1}

Cause: The certificate is about to expire.

Action: Obtain a new server certificate or trusted CA certificate before it expires.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000306: Cannot use SSL because no certificates have been specified in the WebLogic Server configuration.

Cause: No certificates can be found for use by SSL.

Action: If using a keystore for the server certificate, set the ServerPrivateKeyAlias in the SSL MBean. If using the Server Certificate File, ensure that valid certificates are contained within the file.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000307: Exportable key maximum lifespan set to {0} uses.

Cause: The server logs the exportable key maximum lifespan so it is clear what lifespan is being used.

Action: Verify that the lifespan is the desired value.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000314: The execution class "{0}" did not retrieve a T3Executable or T3ExecutableLazy.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000315: Unexpected failure of T3ExecutableLazy, {0}

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000316: enableWatchDog() is not permitted from within a server.

Cause: Deprecated functionality

Action: Deprecated functionality
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000317: disableWatchDog() is not permitted from within a server.

Cause: Deprecated functionality

Action: Deprecated functionality
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000320: Error creating runtime MBean for execute queue {0}.

Cause: An internal system error occurred.

Action: Contact My Oracle Support with the server logs.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000329: Started the WebLogic Server Administration Server "{0}" for domain "{1}" running in production mode.

Cause: The production mode of the server is enabled.

Action: Set the weblogic.ProductionModeEnabled property of the domain in the startup script to change the server mode.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000330: Started the WebLogic Server Managed Server "{0}" for domain "{1}" running in production mode.

Cause: The production mode of the server is enabled.

Action: Set the weblogic.ProductionModeEnabled property of the domain in the startup script file to change the server mode.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000331: Started the WebLogic Server Administration Server "{0}" for domain "{1}" running in development mode.

Cause: The production mode of the server is disabled (default).

Action: Set the weblogic.ProductionModeEnabled property of the domain in the configuration script to change the server mode.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000332: Started the WebLogic Server Managed Server "{0}" for domain "{1}" running in development mode.

Cause: The production mode of the server is disabled (default).

Action: Set the weblogic.ProductionModeEnabled property of the domain in the startup script to change the server mode.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000333: Queue usage is greater than QueueLengthThresholdPercent "{0}%" of the maximum queue size. An attempt will be made to allocate ThreadsIncrease "{1}" thread(s) to help.

Cause: The server is under high load.

Action: Review the execute queue settings.
Level: 1

Type: WARNING

Impact: WebLogicServer

BEA-000337: {0} has been busy for "{1}" seconds working on the request "{2}", which is more than the configured time (StuckThreadMaxTime) of "{3}" seconds in "{4}". Stack trace: {5}

Cause: The server is extremely busy or the thread is hung.

Action: Monitor the method that the hung thread is running. Use the Administration Console monitor execute request feature or take a thread dump (weblogic.Admin THREAD_DUMP).
Level: 1

Type: ERROR

Impact: WebLogicServer

BEA-000339: {0} has become "unstuck".

Cause: A thread previously stuck is now available.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000342: Unable to initialize the server: {0}.

Cause: An exception occurred during the server initialization.

Action: Analyze the weblogic.log file to determine why the server did not initialize completely.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000343: The health monitor for "{0}" failed to register because of exception "{1}".

Cause: Refer to the exception printed in the log message.

Action: Refer to the exception printed in the log message.
Level: 1

Type: WARNING

Impact: WebLogicServer

BEA-000344: The health monitor for "{0}" failed to unregister because of exception "{1}".

Cause: Refer to the exception printed in the log message.

Action: Refer to the exception printed in the log message.
Level: 1

Type: WARNING

Impact: WebLogicServer

BEA-000357: Started WebLogic Server independent Managed Server "{0}" for domain "{1}" running in development mode.

Cause: The server started with the Managed Server independence mode enabled.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000358: Started WebLogic Server independent Managed Server "{0}" for the domain "{1}" running in production mode.

Cause: The production mode of the server is enabled.

Action: Set the ProductionModeEnabled property of the domain in the configuration file to change the server mode.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000360: The server started in {0} mode.

Cause: The startup mode was set to SUSPENDED.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000362: Server failed. Reason: {0}

Cause: Inspect the log file for indications of the root cause of the failure.

Action: Inspect the log file for indications of the root cause of the failure.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000365: Server state changed to {0}.

Cause: The server progressed through the startup or shutdown sequence.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000366: The server failed to shut down. Exception: {0}

Cause: Inspect the log file for indications of the root cause of the failure.

Action: Inspect the log file for indications of the root cause of the failure.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000371: An error occurred during server shutdown: {0}.

Cause: Inspect the log file for indications of the root cause of the failure.

Action: Inspect the log file for indications of the root cause of the failure.
Level: 1

Type: ERROR

Impact: WebLogicServer

BEA-000374: Waiting for ExecuteQueue {0} to finish {1} pending requests.

Cause: The server found pending requests in one of the execute queues while suspending. The server will wait for the requests to complete.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000377: Starting WebLogic Server with {0} Version {1} from {2}.

Cause: The server is starting.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000378: The server failed to shut down within the configured timeout of {0} seconds. The server process will now exit.

Cause: Forced shutdown is taking too long to complete.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000381: ServerLifeCycle operation failed. Message: {0} {1}

Cause: A server operation, such as shutdown, failed.

Action: If the error is not application related, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: WebLogicServer

BEA-000382: A critical service failed. The server will automatically transition to the ADMIN state.

Cause: A server lifecycle operation or a critical service failed.

Action: The server logs contain information about the failure. If the error is not application related, contact My Oracle Support.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000383: A critical service failed. The server will shut itself down.

Cause: A critical service failed.

Action: The server logs contain information about the failure. If the error is not application related, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: WebLogicServer

BEA-000384: A fatal configuration failure occurred during startup. Check if the config.xml file contains invalid entries. Reason: {0}

Cause: The server failed to start due to invalid configuration.

Action: Check if the config.xml file contains invalid entries. Contact My Oracle Support for more information.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000385: Server health failed. Reason: {0}

Cause: Inspect the log file for indications of the root cause of the failure.

Action: Inspect the log file for indications of the root cause of the failure.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000386: Server subsystem failed. Reason: {0}

Cause: Inspect the log file for indications of the root cause of the failure.

Action: Inspect the log file for indications of the root cause of the failure.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000388: JVM called the WebLogic Server shutdown hook. The server will force shutdown now.

Cause: The JVM called the WebLogic Server shutdown hook. The server will force shutdown now.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000394: Deadlock detected: {0}.

Cause: There are threads deadlocked in the server.

Action: Report this error to My Oracle Support if the deadlock involves WebLogic Server internal code.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000395: The following extensions directory contents added to the end of the classpath: {0}.

Cause: Extensions directory contents were added to the classpath.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000396: Server {0} has been requested by {1}.

Cause: A request was made to perform the specified server operation.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000398: WebLogic Server "{0}" for domain "{1}" is running with class caching enabled in production mode. Class caching is not supported in production mode. Disable class caching by setting CLASS_CACHE to "false" in the startWeblogic script and then restarting the server.

Cause: Class caching is turned on by default when server production mode is enabled.

Action: Set the CLASS_CACHE to false in the startWeblogic script and then restart the server.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000401: Socket queue full, dropping socket {0}.

Cause: This is an internal error.

Action: Capture the errors and send the server log files to My Oracle Support.
Level: 1

Type: INTERNAL_ERROR

Impact: Socket

BEA-000402: There are: {0} active sockets, but the maximum number of socket reader threads allowed by the configuration is: {1}. The configuration may need altered.

Cause: When non-native I/O is used, I/O is performed in a blocking manner. Therefore, if the number of socket reader threads is less than the number of active sockets, performance may degrade significantly.

Action: Optimally, increase the ThreadPoolPercentSocketReaders, or the ThreadPoolSize, or both. Optimally, decrease the SocketReaderTimeoutMinMillis, or the SocketReaderTimeoutMaxMillis, or both.
Level: 1

Type: WARNING

Impact: Socket

BEA-000403: IOException occurred on socket: {0} {1}.

Cause: An unexpected IOException occurred while performing I/O for the socket.

Action: Check network connectivity. If the situation persists after environmental issues are resolved, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Socket

BEA-000404: ThreadDeath in processSockets {0}.

Cause: This is an internal error.

Action: Capture the errors and send the server log files to My Oracle Support.
Level: 1

Type: INTERNAL_ERROR

Impact: Socket

BEA-000405: Uncaught Throwable in processSockets {0}.

Cause: This is an internal error.

Action: Capture the errors and send the server log files to My Oracle Support.
Level: 1

Type: ERROR

Impact: Socket

BEA-000406: {0}

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Socket

BEA-000409: Problem on socket: {0} {1}

Cause: An exception occurred while registering the socket with the muxer. It is possible that the file descriptor cannot be obtained from the socket.

Action: Capture the errors and send the server log files to My Oracle Support.
Level: 1

Type: ERROR

Impact: Socket

BEA-000414: Could not initialize the POSIX performance pack.

Cause: The shared library for the POSIX performance pack could not be loaded.

Action: Ensure that the muxer shared library (libmuxer.so) exists in a directory that is in the LD_LIBRARY_PATH. If the situation persists, contact My Oracle Support.
Level: 1

Type: INTERNAL_ERROR

Impact: Socket

BEA-000415: System has file descriptor limits of soft: {0}, hard: {1}

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Socket

BEA-000416: Using effective file descriptor limit of: {0} open sockets and files.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Socket

BEA-000421: Uncaught Throwable in processSockets {0}.

Cause: This is an internal error.

Action: Capture the errors and send the server log files to My Oracle Support.
Level: 1

Type: ERROR

Impact: Socket

BEA-000429: Muxer received error: {0} {1}.

Cause: An unexpected error occurred while processing socket I/O requests.

Action: Capture the errors and send the server log files to My Oracle Support.
Level: 1

Type: ERROR

Impact: Socket

BEA-000431: Accepted connection: filtering is set to: "{0}", remote address: "{1}", remote port: "{2,number,0}", local address: "{3}", local port: "{4,number,0}", protocol: "{5}"

Cause: This is an informational message for the administrator.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Socket

BEA-000432: Unable to load performance pack. Using Java I/O instead. {0}

Cause: The native library for the performance pack was unable to be loaded.

Action: Ensure that the classpath and the environment is set up properly. If the situation persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Socket

BEA-000435: Unable to initiate read for the socket. The maximum allowed number of pending I/O requests ({0}) has been exceeded.

Cause: This is an internal error.

Action: Capture the errors and send the server log files to My Oracle Support.
Level: 1

Type: ERROR

Impact: Socket

BEA-000436: Allocating {0} reader threads.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Socket

BEA-000437: The default setting for MuxerClass was overridden and no muxer class name was specified. Resorting to implementation class: {0}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Socket

BEA-000438: Unable to load performance pack. Using Java I/O instead. {0}

Cause: The native performance pack was unable to be loaded.

Action: Ensure that the appropriate path for the native libraries is set properly in the environment.
Level: 1

Type: ERROR

Impact: Socket

BEA-000439: Unable to create the Java socket muxer.

Cause: This is an internal error.

Action: Ensure that the classpath is set properly. If the situation persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Socket

BEA-000440: Unable to initiate I/O for {0} {1}.

Cause: The initiation of the I/O operation failed, which could have been caused by the network, I/O or other problems. It could also have been an internal error.

Action: Correct any conditions as suggested by the error message, if applicable. If the situation persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Socket

BEA-000441: Unable to find internal data record for the socket {0}, with I/O completion result {1}

Cause: This is an internal error.

Action: If the situation persists, contact My Oracle Support.
Level: 1

Type: WARNING

Impact: Socket

BEA-000442: The connection attempt was rejected because the incoming protocol is not enabled on channel "{0}".

Cause: The connection attempt was rejected because a protocol was not enabled for this server, as determined by the ServerMBean, or was not enabled on this particular channel.

Action: Enable the protocol on the channel.
Level: 1

Type: WARNING

Impact: Socket

BEA-000443: The connection attempt was rejected because the incoming protocol {1} is not enabled on channel {0}.

Cause: The connection attempt was rejected because the {1} protocol was not enabled for this server, as determined by the ServerMBean, or was not enabled on this particular channel.

Action: Enable the {1} protocol on the channel.
Level: 1

Type: WARNING

Impact: Socket

BEA-000444: Could not load the performance pack that can take advantage of the /dev/(e)poll device due to: {0}. Will attempt to use the performance pack that does not depend on the /dev/(e)poll device.

Cause: The operating system does not support the /dev/(e)poll or the device is not initialized.

Action: Ensure that the operating system supports the /dev/(e)poll device.
Level: 1

Type: WARNING

Impact: Socket

BEA-000445: Connection rejected, filter blocked {0}, {1}

Cause: The incoming message was not recognized as one of the supported protocols.

Action: Ensure that the server is configured for the relevant protocol.
Level: 1

Type: NOTIFICATION

Impact: Socket

BEA-000446: Native I/O enabled.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Socket

BEA-000447: Native I/O disabled. Using Java I/O.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Socket

BEA-000448: Socket channel support has been enabled for a JVM on which the feature is unsupported.

Cause: This error is caused by turning on a feature that is not supported on the underlying JVM.

Action: Either disable socket channel support or use a JVM version on which this feature is supported.
Level: 1

Type: ERROR

Impact: Socket

BEA-000449: Closing the socket, as no data read from it on {1}:{2} during the configured idle timeout of {0} seconds.

Cause: The WebLogic Server instance or the network may be overloaded, which is causing the socket to idle timeout.

Action: Capacity tuning of the server is required.
Level: 1

Type: WARNING

Impact: Socket

BEA-000451: Closing the socket, as end of file is encountered while reading from the socket to the ONS server at {0}.

Cause: The connection to the remote Oracle Notification Server (ONS) process might have been disconnected.

Action: Check the status of the remote ONS process.
Level: 1

Type: WARNING

Impact: Socket

BEA-000452: An exception occurred on the socket to the ONS server at {0}: {1}.

Cause: An exception occurred while reading from the socket. The connection to the remote Oracle Notification Server (ONS) process might have been disconnected.

Action: Check the network connectivity to the remote ONS process. If the situation persists after environmental issues are resolved, contact My Oracle Support.
Level: 1

Type: WARNING

Impact: Socket

BEA-000453: An exception occurred while processing the message sent from the ONS at {0}: {1}

Cause: An error occurred while parsing the message received from the remote ONS.

Action: Check the ONS log file for additional details.
Level: 1

Type: ERROR

Impact: Socket

BEA-000454: Unable to establish connection to the remote ONS process at {0}:{1}. Exception occurred while doing handshake: {2}

Cause: An exception occurred while doing handshake with the remote ONS process.

Action: Check the exception and ONS log file for additional details.
Level: 1

Type: ERROR

Impact: Socket

BEA-000455: Attempting to remove unregistered HandshakeCompletedListener: class={0}, instance={1}.

Cause: The unregistered HandshakeCompletedListener: class={0}, instance={1}, is attempting to be removed.

Action: The unregistered HandshakeCompletedListener: class={0}, instance={1}, is attempting to be removed.
Level: 1

Type: ERROR

Impact: Socket

BEA-000456: Unable to load performance pack. Using Java I/O instead.

Cause: The native library for the performance pack could not be loaded.

Action: Ensure that the classpath and the environment is set up properly. If the situation persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Socket

BEA-000457: NIOInputStream received error while closing java.nio.channels.Selector: : {0} {1}.

Cause: An unexpected error occurred while processing socket I/O requests.

Action: If the situation persists, capture the errors and send the server log files to My Oracle Support.
Level: 1

Type: WARNING

Impact: Socket

BEA-000458: {0}

Cause: See the message body.

Action: Review the message body to determine the appropriate action to take.
Level: 1

Type: WARNING

Impact: Socket

BEA-000501: Peergone send failed - target unreachable.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: RJVM

BEA-000502: Peergone send failed - target already gone.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: RJVM

BEA-000503: Incoming message header or abbreviation processing failed. {0}

Cause: While processing an incoming message an error was encountered. It is likely that the message was corrupted.

Action: This is most likely a temporary situation. No action is required. If this situation continues, contact My Oracle Support with the server logs and configuration.
Level: 1

Type: ERROR

Impact: RJVM

BEA-000504: Unmarshal exception: received illegal command code: {0}

Cause: A message containing an invalid command code was received. This message cannot be processed. One of the possible reasons is that the message was corrupted in transit.

Action: This is most likely a temporary situation. No action is required. If this situation continues, contact My Oracle Support with the server logs and configuration.
Level: 1

Type: ERROR

Impact: RJVM

BEA-000505: Peer did not send us a valid heartbeat interval; using the default heartbeat specified as a property.

Cause: The incoming message has an invalid heartbeat interval. This is either due to message corruption in transit or to an invalid choice for the heartbeat interval on the peer that is attempting to establish communication with this JVM.

Action: If the peer that is attempting to establish communication is overriding the default heartbeat interval, ensure that a valid interval is used. If not, contact My Oracle Support with the server logs and configuration.
Level: 1

Type: ERROR

Impact: RJVM

BEA-000506: Closing: {0} because of {1}

Cause: This JVM has received an incoming message that is incompatible with the way the protocols are supposed to work.

Action: This is most likely a temporary situation. No action is required. If this situation continues, contact My Oracle Support with the server logs and configuration.
Level: 1

Type: ERROR

Impact: RJVM

BEA-000507: Could not create/send request to close duplicate connection message. {0}

Cause: Creation or sending of the message to request closing a connection caused an I/O error.

Action: This is most likely a temporary situation. No action is required. If this situation continues, contact My Oracle Support with the server logs and configuration.
Level: 1

Type: WARNING

Impact: RJVM

BEA-000508: ID: {0} in use by: {1}, can not install {2}

Cause: The ID {0} is already associated with and in use by {1} and hence cannot be used in association with {2}.

Action: Ensure that unique IDs are used in registration.
Level: 1

Type: ERROR

Impact: RJVM

BEA-000509: Finder not initialized.

Cause: This JVM was created without a valid finder.

Action: Ensure that a valid finder is used when creating this JVM.
Level: 1

Type: ERROR

Impact: RJVM

BEA-000510: Unsolicited response: {0}

Cause: A duplicate response has been received for a request that has already received its response.

Action: This is most likely a temporary situation. No action is required. If this situation continues, contact My Oracle Support with the server logs and configuration.
Level: 1

Type: WARNING

Impact: RJVM

BEA-000511: Unsolicited error response for: {0}

Cause: A duplicate error response was received for a request that has already received its response or its error response.

Action: This is most likely a temporary situation. No action is necessary. If this situation continues, contact My Oracle Support with the server logs and configuration.
Level: 1

Type: WARNING

Impact: RJVM

BEA-000512: New heartbeat period: {0} is different from established heartbeat period: {1}; using established heartbeat period

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: RJVM

BEA-000513: Failure in heartbeat trigger for RJVM: {0}. {1}

Cause: This error indicates a temporary failure in the heartbeat trigger mechanism.

Action: No action is required. This is usually a temporary failure.
Level: 1

Type: NOTIFICATION

Impact: RJVM

BEA-000514: openConnection() failed. {0}

Cause: Possible causes are an invalid target address or the target not being active or reachable.

Action: This is most likely a temporary situation. No action is required. If this situation continues, contact My Oracle Support with the server logs and configuration.
Level: 1

Type: ERROR

Impact: RJVM

BEA-000515: execute failed {0}

Cause: A failure was encountered when handling the incoming HTTP message.

Action: This is most likely a temporary situation. No action is required. If this situation continues, contact My Oracle Support with the server logs and configuration.
Level: 1

Type: ERROR

Impact: RJVM

BEA-000519: Unable to connect to a remote server on address {1} and port {2,number,0} with protocol {0}. The exception is {3}

Cause: The target is either not reachable or is not active.

Action: Ensure that the target is active.
Level: 1

Type: WARNING

Impact: RJVM

BEA-000570: Network Configuration for Channel "{0}" Listen Address {1} Public Address {2} Http Enabled {3} Tunneling Enabled {4} Outbound Enabled {5} Admin Traffic Enabled {6}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: RJVM

BEA-000572: The server rejected a connection attempt {0} probably due to an incorrect firewall configuration or administrative command.

Cause: The incoming connection attempt was probably made through an address translating firewall. WebLogic Server needs to be correctly configured for this to work. This message can also occur if an administration connection attempt, requiring administrator level security, is made on a non-administrative port.

Action: Configure the public and private addresses for this WebLogic Server instance to reflect the configuration of the firewall. The private address is the actual address the server is running. The public address is the address that external clients use to connect.
Level: 1

Type: ERROR

Impact: RJVM

BEA-000600: Callback {0} failed: {1}

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: ERROR

Impact: Common

BEA-000601: AdminProxyWatchDog: Enabled. Interval = {0} secs.

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000602: AdminProxyWatchDog: Enable failed.

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: ERROR

Impact: Common

BEA-000603: AdminProxyWatchDog: Disabled.

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000604: AdminProxyWatchDog: Disable failed.

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: ERROR

Impact: Common

BEA-000605: Connectivity lost to WatchDog Client. Shutting down.

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: ERROR

Impact: Common

BEA-000606: AdminProxyWatchDog: No echo received in last {0} minutes. Shutting down.

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: ERROR

Impact: Common

BEA-000607: AdminProxyWatchDog: Echo Received.

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000608: AdminProxyWatchDog: Tick. diff = {0}

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000609: An error occurred during server shutdown: {0}.

Cause: This is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Common

BEA-000611: No resources in the pool {0} will be tested, as the specified MaxUnavailable {1} has been reached.

Cause: The application MaxUnavailable attribute for this pool has been configured. Since the number of unavailable resources in the pool has reached or exceeded the configured limit, no more resources will be tested. Resources become unavailable to the application during the testing.

Action: Tune the MaxUnavailable attribute for the pool if so desired.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000612: All {1} resource instances currently available in the pool {0} are being tested.

Cause: This is a warning indicating that all currently available resources in the pool are being tested, and therefore some or all of them may become unavailable to the application for a short time.

Action: Reduce the current setting of the MaxUnavailable attribute for the pool.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000613: Testing of resources upon creation has been dynamically enabled for pool "{0}".

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000614: Testing of resources upon creation has been dynamically disabled for pool "{0}".

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000615: Testing of resources when being reserved has been dynamically disabled for pool "{0}".

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000616: Testing of resources when being reserved has been dynamically enabled for pool "{0}".

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000617: Testing of resources when being released has been dynamically enabled for pool "{0}".

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000618: Testing of resources when being released has been dynamically disabled for pool "{0}".

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000619: Unable to forcibly release resource "{1}" back into the pool "{0}". Received exception: {2}.

Cause: As part of the InactiveResourceTimeout feature, resources that are found to be inactive for the configured period of time are forcibly released back into the pool. The operation could not be performed for the indicated reason.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Common

BEA-000620: Forcibly releasing inactive resource "{1}" back into the pool "{0}".

Cause: The resource was found to be unused by the application for the specified duration and is being forcibly released back into pool.

Action: Check application code for leakages of resource objects or tune the configured value of the relevant pool attribute.
Level: 1

Type: WARNING

Impact: Common

BEA-000621: Expected RemoteException, RuntimeException, or Error {0}

Cause: An unexpected low-level message was sent to the server.

Action: This is likely due to an internal client/server error that should be reported to My Oracle Support.
Level: 1

Type: ERROR

Impact: Common

BEA-000622: Ignoring an attempt to release resource "{1}" to pool "{0}" after the pool has been shut down.

Cause: Application is trying to release a resource to a pool after the pool has been shut down.

Action: Check application behavior. All resources should be closed before the application is shut down.
Level: 1

Type: WARNING

Impact: Common

BEA-000623: Setting CapacityIncrement for pool "{0}" to 1. The specified value of "{1}" is not valid.

Cause: The application had specified an invalid value for CapacityIncrement.

Action: Check and correct the specified value for CapacityIncrement for the indicated pool.
Level: 1

Type: WARNING

Impact: Common

BEA-000624: Setting frequency of testing of free resources in pool "{0}" to five seconds since the specified value of "{1}" is not valid.

Cause: The application had specified an invalid value for the test frequency.

Action: Check and correct the specified value for TestFrequencySeconds for the indicated pool.
Level: 1

Type: WARNING

Impact: Common

BEA-000625: The application has disabled periodic testing of free resources in pool "{0}".

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000626: Free resources in pool "{0}" will be tested every "{1}" seconds.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000627: Reached maximum capacity of pool "{0}", making "{2}" new resource instances instead of "{1}".

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000628: Created "{1}" resources for pool "{0}", out of which "{2}" are available and "{3}" are unavailable.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000629: Recreated "{2}" out of "{1}" resources for pool "{0}".

Cause: As part of forcibly suspending a pool, all resources currently in use are destroyed and recreated. This message indicates that not all required resources were recreated.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: Common

BEA-000630: Unable to create "{1}" resources for pool "{0}".

Cause: As part of the ConnectionCreationRetry feature, pools periodically attempt to create unavailable resources. This message indicates that, in the current attempt, the indicated number of resources could not be created.

Action: Check if the failure condition that prevents the resources from being created (for example, database server or downed network connectivity to it) is still persisting.
Level: 1

Type: WARNING

Impact: Common

BEA-000631: Unknown resource "{1}" being released to pool "{0}": {2}

Cause: The application is trying to release a resource to a pool that is no longer part of the pool. This could happen if the pool was forcibly suspended (which results in all borrowed resources being closed and replaced with new ones) while the resource was borrowed by the application.

Action: Check the application behavior.
Level: 1

Type: WARNING

Impact: Common

BEA-000632: Resource Pool "{0}" shutting down, ignoring {1} resources still in use by applications.

Cause: The administrator is shutting down the pool while applications are still using resources they have obtained from the pool. It is possible that these resources may have been leaked by the applications.

Action: Check the application behavior.
Level: 1

Type: WARNING

Impact: Common

BEA-000633: Resource Pool "{0}" suspending due to consecutive number of resource creation failures exceeding threshold of {1}

Cause: Resource creation or resource tests have repeatedly failed.

Action: Determine the cause of resource failures and take corrective action.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000634: Resource hang detected for pool "{0}", group "{1}". Waited {2} milliseconds where a typical test has been taking {3}.

Cause: Resource tests have been taking longer than expected.

Action: Correct the condition that causes the resource tests to block for extended periods of time.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000635: Resource Pool "{0}", group "{1}" disabled due to number of resource creation or test failures exceeding threshold of {2}.

Cause: Resource creation or resource tests have repeatedly failed.

Action: Determine the cause of resource failures and correct.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000636: Resource Pool "{0}", group "{1}" enabled.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000637: Resource Pool "{0}" resuming due to successful resource creation or test.

Cause: This is an informmational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000638: Resource Pool "{0}" is being suspended by an external command (multi data source or console or other).

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000639: Resource Pool "{0}" is being force-suspended by an external command (multi data source or console or other).

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000640: Resource Pool "{0}" resuming by external command (multi data source or console or other).

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000701: Unable to mount the fileSystem named {0} {1}

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: ERROR

Impact: T3Misc

BEA-000702: Unable to unmount the fileSystem named {0} {1}

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: ERROR

Impact: T3Misc

BEA-000703: Unable to get fileSystem context from Root {0}

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: ERROR

Impact: T3Misc

BEA-000704: Cannot create file system at {0} {1}

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: ERROR

Impact: T3Misc

BEA-000705: Created file system at {0}

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: NOTIFICATION

Impact: T3Misc

BEA-000706: Unable to find remote file {0} {1}

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: ERROR

Impact: T3Misc

BEA-000707: Unable to open remote file {0} {1}

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: ERROR

Impact: T3Misc

BEA-000708: T3RemoteOutputStreamProxy: write timed out or interrupted - {0}, {1}

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: ERROR

Impact: T3Misc

BEA-000709: T3RemoteOutputStreamProxy: flush timed out or interrupted - {0}, {1}

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: ERROR

Impact: T3Misc

BEA-000710: TimeRepeat trigger scheduled to run at a date in the past : {0}, trigger will not repeat

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: ERROR

Impact: T3Misc

BEA-000711: Uncaught throwable in run {0}

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: ERROR

Impact: T3Misc

BEA-000712: Exception invoking {0} {1}

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: ERROR

Impact: T3Misc

BEA-000713: Exception closing stream {0}

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: ERROR

Impact: T3Misc

BEA-000800: {0} stopped.

Cause: A ThreadDeath exception caused a shutdown.

Action: No action is required.
Level: 1

Type: INTERNAL_ERROR

Impact: Kernel

BEA-000801: ExecuteRequest: {0} cancelled.

Cause: This only happens when WebLogic Server is used in conjunction with an IDE, which uses JVMDI to cancel in-flight requests. If this occurs in normal operation, contact My Oracle Support.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Kernel

BEA-000802: ExecuteRequest failed {0}.

Cause: An execute request generated an exception that was not handled.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Kernel

BEA-000803: The Class {0} has a setter {1} for attribute {2} which does not have a constructor that could be initialized from a String value of {3}.

Cause: No constructor that takes a String argument was found for the declared attribute type.

Action: Provide a constructor with a String argument.
Level: 1

Type: ERROR

Impact: Kernel

BEA-000804: The Class {0} attribute {1} could not be initialized with value {2}. The exception message is {3}.

Cause: See the exception stack trace for details.

Action: Take the appropriate action based on the error message.
Level: 1

Type: ERROR

Impact: Kernel

BEA-000805: The self-tuning thread pool is disabled. An execute queue will be created for each Work Manager definition.

Cause: The server is starting.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Kernel

BEA-000807: Work Manager {0} has reached its capacity. It is rejecting from thread {1}. The message is {2}. Throwable is {3}.

Cause: This is a Work Manager bug.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Kernel

BEA-000808: The executing thread is a non-WebLogic Server thread. Modify the application to use the Commonj Work Manager API.

Cause: The use of an application spawned a Java thread instead of the Commonj Work Manager API.

Action: Modify the application to use the Commonj Work Manager APIs.
Level: 1

Type: WARNING

Impact: Kernel

BEA-000902: A duplicate expression was found in the system property {0}.nonProxyHosts: {1}.

Cause: The system property {0}.nonProxyHosts contains a pipe character delimited list of hosts, which should be connected to directly and not through the proxy server.

Action: Check the system property {0}.nonProxyHosts. The value can be a list of hosts, each separated by a |. In addition, a wildcard character (*) can be used for matching. For example: -D{0}.nonProxyHosts="*.foo.com|localhost".
Level: 1

Type: ERROR

Impact: Net

BEA-000903: Failed to communicate with proxy: {0}/{1}. Will try connection {2}/{3} now.

Cause: An IOException was received while communicating with the proxy server.

Action: Check the exception for more information. Check if the proxy is running by pinging the proxy: {0}/{1} from the same machine.
Level: 1

Type: ERROR

Impact: Net

BEA-000904: {0} initializing the URL stream handler with custom factory: {1}.

Cause: The factory class that was specified against the system property weblogic.net.http.URLStreamHandlerFactory failed to load or invoke.

Action: Check the system property weblogic.net.http.URLStreamHandlerFactory. This property is used to set a custom URLStreamHandlerFactory.
Level: 1

Type: ERROR

Impact: Net

BEA-000905: Could not open connection with host: {0} and port: {1}.

Cause: The connection attempt failed.

Action: Ensure that the server is running on the specified host and port.
Level: 1

Type: WARNING

Impact: Net

BEA-001035: The following error has occurred: {0}.

Cause: The embedded message should contain an explanation of the failure.

Action: Take appropriate action based on the reported error.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001058: Could not get JNDI context: {0}

Cause: Look at the printed exception to see why the call failed.

Action: Correct the problem and re-run the operation.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001064: Ignoring the property "enableTwoPhaseCommit" for JDBCTxDataSource "{0}". This property is used only for those drivers that do not natively support XA.

Cause: The property EnableTwoPhaseCommit was configured to "true" for an XADataSource and will be ignored.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001066: Delaying {0,number} seconds before making a {1} pool connection.

Cause: Some databases cannot handle a tight loop of making multiple connections from one application. If this is the case and the delay is more than 2 seconds, this message will be printed.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001067: Connection for pool "{0}" refreshed.

Cause: A connection for the specified pool has been refreshed.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001068: Connection for pool "{0}" created.

Cause: A connection for the specified pool has been created.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001072: Connection for XA pool "{0}" created.

Cause: A connection for the specified XA pool has been created.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001073: Connection for XA pool "{0}" refreshed.

Cause: A connection for the specified XA pool has been refreshed.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001074: A JDBC pool connection leak has been detected. A connection leak occurs when a connection obtained from the pool was not closed explicitly by calling close() and then was disposed by the garbage collector and returned to the data source connection pool. The following stack trace at create shows where the leaked connection was created. {0}

Cause: A JDBC pool connection leak was detected. A connection leak occurs when a connection obtained from the pool was not closed explicitly by calling close() and then was disposed by the garbage collector and returned to the data source connection pool. A stack trace is printed indicating where the leaked connection was created.

Action: Close the connection appropriately.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001076: An attempt has been made to release a connection that belongs to a non-existing pool. Ensure that the pool "{0}" has been destroyed by intent.

Cause: An attempt was made to release a connection that belongs to a non-existing pool.

Action: Correct the destroy operation to specify a valid pool name.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001083: Multi data source "{0}" was created with {1,number} connection pools for {2}.

Cause: A multi data source was created with the specified number of connection pools.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001084: Multi data source "{0}" will be shutdown

Cause: The specified multi data source is being shut down.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001086: Data source "{0}" with JNDI name "{1}" will be shut down.

Cause: The specified data source is being shut down.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001089: Data source connection pool {0} has been started for application {1}, module {2}.

Cause: The specified data source connection pool is being started.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001099: Data source connection pool "{0}" reset by "{1}".

Cause: The specified connection pool has been reset.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001100: Data source connection pool "{0}" shut down by "{1}".

Cause: The specified data source connection pool has been shut down, as requested by the application.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001101: Data source connection pool "{0}" disabled by "{1}".

Cause: The specified data source connection pool has been disabled.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001102: Data source connection pool "{0}" enabled by "{1}".

Cause: The specified data source connection pool has been enabled.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001104: A globally scoped data source connection pool named ({0}) already exists.

Cause: When adding or referencing a JDBC data source connection pool that is an application-scoped pool, a globally scoped data source connection pool with the same name already exists. The locally scoped pool has precedence over the global pool.

Action: If you want to reference the global pool in your application, the name of the global pool or the application-scoped pool must be changed to be unique.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001105: Referenced global pool ({0}) has the same name as a locally defined data source connection pool or data source ({1}).

Cause: When deploying a JDBC data source connection pool (not application-scoped) an application (locally) scoped data source connection pool with the same name already exists. The locally scoped pool has precedence over the global pool.

Action: If you want to reference the global pool in your application, the name of the global pool or the application-scoped pool must be changed to be unique.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001107: There is a globally defined data source ({0}) with the same JNDI name ({1}) as a locally defined data source.

Cause: It is possible to use a resource descriptor with application-scoped pools. If the local JNDI lookup reveals that there is a pool with the JNDI name that is specified in the resource descriptor, it is assumed that this is a pool that the application meant to use and it is bound into comp/env. However, a check in the global namespace indicates that there is also a global pool with the same JNDI name.

Action: If you want to reference the global pool in your application, the JNDI name of the global pool or the application-scoped pool must be changed to be unique.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001108: A locally scoped pool ({0}) was bound into comp/env with the JNDI name ({1}).

Cause: It is possible to use a resource descriptor with application-scoped pools. If the local JNDI lookup reveals that there is a pool with the JNDI name specified in the resource-descriptor, it is assumed that this is the pool that the application meant to use and it is bound into comp/env.

Action: No action is required. If this association is not desired, specify a unique JNDI name in the resource descriptor.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001109: A globally scoped pool ({0}) was bound into comp/env with the JNDI name ({1}).

Cause: It is possible to use a resource descriptor with global data source connection pools. If the JNDI lookup reveals that there is a pool with the JNDI name that is specified in the resource descriptor, it is assumed that this is the pool that the application was meant to use and it is bound into comp/env.

Action: No action is required. If this association is not desired, specify a unique JNDI name in the resource descriptor.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001110: No test table set up for pool "{0}". Connections will not be tested.

Cause: TestConnectionsOnReserve, TestConnectionsOnRelease, TestConnectionsOnCreate, TestFrequencySeconds were configured but TestTableName was not configured.

Action: Configure a valid TestTableName for the data source connection pool.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001111: Unable to verify the test "{1}" set up for pool "{0}". Connections will not be tested. The test will not be used by isValid either.

Cause: While creating a data source connection pool with the attributes specified to test the pool connections, a test is run during the pool initialization. This test failed with the printed error.

Action: Check the SQL error that occurred and correct the problem. The specified TestTableName might not exist.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001112: Test "{1}" set up for pool "{0}" failed with exception: "{2}".

Cause: The specified data source connection pool has been configured with one or more attributes to test the pool connections. One of those test attempts failed. The associated error is printed.

Action: Check the associated error to see what the problem is and correct it. Normally, this indicates that a connection was lost to the database (the database is down). This needs to be corrected by the database administrator.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001113: Data source connection pool "{0}" shrunk by "{1}".

Cause: The data source connection pool has been shrunk by the specified amount as requested by the application.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001114: Soft shutdown called on data source connection pool "{0}" by "{1}".

Cause: A soft shutdown operation on the specified data source connection pool has been started, as requested by the application.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001115: Hard shutdown called on data source connection pool "{0}" by "{1}".

Cause: A hard shutdown operation on the specified data source connection pool has been started, as requested by the application.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001116: Disable and freeze users called on data source connection pool "{0}" by "{1}".

Cause: An operation to disable and freeze users on the specified data source connection pool has been started, as requested by the application.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001117: Disable and drop users called on data source connection pool "{0}" by "{1}".

Cause: An operation to disable and drop users on the specified data source connection pool has been started, as requested by the application.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001118: Unable to register for receiving MBean notifications of dynamic configurations changes for data source connection pool "{0}": "{1}". Pool will not be dynamically reconfigured.

Cause: The server was unable to register for receiving MBean notifications of dynamic configurations changes for the specified data source connection pool. The connection pool will not be dynamically reconfigured.

Action: Check the exception that is printed along with this message to see what the cause of the failure was.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001119: Unable to delete configuration MBean for pool "{0}": "{1}"

Cause: While doing a forced shutdown, the data source connection pool was removed but the associated MBean for the connection pool was not removed.

Action: Check the exception that is printed along with this message to see what the cause of the failure was.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001120: Created data source named {0} for Pool {1}.

Cause: There was a user request to create a data source, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001121: Created TX data source named {0} for Pool {1}.

Cause: The user requested that the TX data source be created, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001122: Destroyed TX data source named {0} for Pool {1}.

Cause: There was a user request to destroy the TX data source, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001123: Destroyed data source named {0} for Pool {1}.

Cause: There was a user request to destroy the data source, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001124: Created Connection Pool named {0}.

Cause: There was a user request to create the data source connection pool, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001125: Created multi data source named {0}.

Cause: There was a user request to create the multi data source, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001126: Destroyed Connection Pool named {0}.

Cause: There was a user request to destroy the data source connection pool, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001127: Destroyed multi data source named {0}.

Cause: There was a user request to destroy the multi data source, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001128: Connection for pool "{0}" has been closed.

Cause: A connection for the specified data source connection pool has been closed.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001129: Received exception while creating connection for pool "{1}": {0}.

Cause: The exception message should indicate the probable cause of the error.

Action: Check the error to see why the connection creation failed and correct the problem.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001130: Disabled statement caching for connection in pool "{0}" as it is using the WebLogic Type-2 XA driver.

Cause: Statement caching was disabled for the specified data source connection pool because it is using the WebLogic Type-2 XA driver. This driver has a limitation based on the implementation using the ORACLE OCI interface. Cursors are closed when the XAResource.end is called, causing all prepared statements to be no longer valid.

Action: No action is required. Use a different driver if you want to use the prepared statement cache with the driver.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001131: Received an exception when closing a cached statement for the pool "{0}": {1}.

Cause: When closing a prepared statement in the prepared statement cache for the specified data source connection pool, an error occurred.

Action: Check the associated error that is printed and, if possible, correct the problem.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001132: Initialized statement cache of size "{1}" for connection in pool "{0}".

Cause: A prepared statement cache has been enabled for a connection in the specified data source connection pool.

Action: No action is required. If you do not want statement caching turned on for the pool, do not configure or disable it.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001133: Statement caching is not enabled for connection in specified data source connection pool "{0}".

Cause: A configured data source connection pool has been started without statement caching being enabled.

Action: No action is required. If you want statement caching turned on for the pool, configure and enable it.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001134: Statement caches of connections in the data source connection pool "{0}" have been cleared by "{1}".

Cause: The statement caches for connections in the specified data source connection pool have been cleared, as requested by the application.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001135: Initializing the JDBC service.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001136: Initialization failed.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001137: Initialization complete.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001138: Resuming the JDBC service.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001139: Resume failed.

Cause: Check earlier messages that are printed in the log.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001140: Resume complete.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001141: Suspending the JDBC service.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001142: Suspend of JDBC service failed.

Cause: Check earlier messages that are printed in the log.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001143: Suspend completed.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001144: Force Suspending the JDBC service.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001145: Force suspend of the JDBC service failed.

Cause: Check earlier messages that are printed in the log.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001146: Force suspend of the JDBC service completed.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001147: Shutting down the JDBC service.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001148: Shutdown of the JDBC service failed.

Cause: Check earlier messages that are printed in the log.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001149: Shutdown of the JDBC service has completed.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001150: Connection pool "{0}" deployment failed with the following error: {1}.

Cause: The cause should be indicated in the exception message.

Action: Correct the problem described in the exception message.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001151: Data source "{0}" deployment failed with the following error: {1}.

Cause: The cause should be indicated in the exception message.

Action: Correct the problem described in the exception message.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001152: Cannot enable statement caching for connection in pool "{0}", because it is using the WebLogic Type-2 XA driver.

Cause: Statement caching has been disabled for the specified data source connection pool because the connection pool is using the WebLogic Type-2 XA driver. This driver has a limitation based on the implementation using the ORACLE OCI interface. Cursors are closed when XAResource.end is called, causing all prepared statements to no longer be valid.

Action: No action is required. Use a different driver if you want to use the prepared statement cache with the driver.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001153: Forcibly releasing inactive/harvested connection "{1}" back into the data source connection pool "{0}", currently reserved by: {2}.

Cause: The connection was found to be unused by the application for the specified duration (configured using InactiveConnectionTimeoutSeconds attribute of the pool MBean), and therefore is being forcibly released back into pool. Alternatively, the connection was harvested and the application callback did not close the connection.

Action: Check the application code for leakages of connection objects, or tune the configured value of the specifed connection pool attribute.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001154: Disabling statement caching for connection in pool "{0}".

Cause: Statement caching has been disabled for the specified data source connection pool for one or more reasons. 1. The size is explicitly configured to 0. 2. The Oracle replay driver is being used. 3. The Oracle statement cache is enabled.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001155: The following exception has occurred:

Cause: An error condition has occurred.

Action: Look for the associated exception in the log or your program to see what the results are. In general, this stack trace will help with debugging an existing problem.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001156: Stack trace associated with message {0} follows:

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001157: Data source connection pool "{0}" being suspended by user "{1}".

Cause: The specified data source connection pool is being suspended, as requested by the application.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001158: Data source connection pool "{0}" being forcibly suspended by user "{1}".

Cause: The specified data source connection pool is being forcibly suspended, as requested by the application.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001159: Data source connection pool "{0}" is being resumed by user "{1}".

Cause: The specified data source connection pool is being resumed, as requested by the application.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001160: Data source connection pool "{0}" being forcibly destroyed by user "{1}"

Cause: The specified data source connection pool is being forcibly destroyed, as requested by the application.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001161: Data source connection pool "{0}" being destroyed by user "{1}".

Cause: The specified data source connection pool is being destroyed, as requested by the application.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001162: Data source connection pool "{0}" being forcibly shutdown by user "{1}".

Cause: The specified data source connection pool is being forcibly shutdown, as requested by the application.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001163: Data source connection pool "{0}" being shut down by user "{1}".

Cause: The specified data source connection pool is being shut down, as requested by the application.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001164: Unable to initialize connection in pool "{0}". Initialization SQL = "{1}". Received exception: "{2}".

Cause: The exception message should contain a reason for the failure.

Action: Take appropriate corrective action.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001165: Invalid statment cache size "{1}" specified for connection in pool "{0}".

Cause: An invalid value has been specified for statement cache size for connections in the indicated data source connection pool.

Action: Check the allowed limits for statement cache size for this data source connection pool and fix the specified value.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001166: Activation of application-scoped data source connection pool "{1}":"{2}":"{0}" failed. Received exception: "{3}".

Cause: The error message should contain the reason for the failure.

Action: Take appropriate corrective action.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001167: Deactivation of application-scoped pool "{1}":"{2}":"{0}" failed. Received exception: "{3}".

Cause: The error message should contain the reason for the failure.

Action: Take appropriate corrective action.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001168: Attempt to resume JDBCService when it is already running...Ignoring.

Cause: The application attempted to resume JDBCService, although the service is already running.

Action: Take appropriate corrective action.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001169: Error occured during shutdown of pool "{0}". Received exception: "{1}".

Cause: The exception should contain the reason for the failure.

Action: Take appropriate corrective action.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001170: Unable to initialize JDBC Log. Received exception: "{0}".

Cause: The message should contain the reason for the failure.

Action: Take appropriate corrective action.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001171: Unable to close connection "{0}". Received exception: "{1}".

Cause: The message should contain the reason for the failure.

Action: Take suitable action if possible. Otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001172: Error occurred during shutdown of data source "{0}". Received exception: "{1}".

Cause: The message should contain the reason for the failure.

Action: Take appropriate corrective action.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001173: "TestTableName" attribute for pool "{0}" being dynamically changed to "{1}".

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001174: Creating data source named {0}, JNDI Name = {1}.

Cause: The user requested that the data source be created, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001175: Creating transactional data source named {0} for Pool {1}.

Cause: The user requested that the transactional data source be created, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001176: Creating multi data source named {0}.

Cause: The user requested that the multi data source be created, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001177: Creating data source connection pool named {0}, URL = {1}, Properties = {2}.

Cause: A request was issued to create the data source connection pool, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001178: Attempt to set query timeout on a statement failed : {0}.

Cause: The reported message should contain a description of the failure.

Action: Contact My Oracle Support.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001250: Unable to load application configured callback {1} for multi data source {0}, got error: {2}. Application control of multi data source failover behaviour will not work.

Cause: This is most likely because the application-defined class location has not been added to the CLASSPATH environment varible.

Action: Please check that you specified the correct class name and that your CLASSPATH includes this class.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001251: Application configured callback {1} for multi data source {0} does not implement required interface {2}. Application control of multi data source failover behaviour will not work.

Cause: The configured callback {1} does not implement the required interface {2}.

Action: Refer to the WebLogic Server documentation.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001252: Unable to add notification listener for Config MBean for multi data source {0} failed, got exception: {1}.

Cause: The reported exception should indicate the cause of the failure.

Action: Refer to the WebLogic Server documentation.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001254: Multi data source {0} unable to disable connection pool {1}, got exception: {2}.

Cause: The reported exception should indicate the cause of the failure.

Action: Refer to the WebLogic Server documentation.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001255: Multi data source {0} unable to disable connection pool {1}, got exception: {2}.

Cause: The reported exception should indicate the cause of the failure.

Action: Refer to the WebLogic Server documentation.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001256: Dynamically changing the value of attribute FailoverRequestIfBusy for multi data source {0} from {1} to {2}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001257: Dynamically changing value of attribute HealthCheckFrequencySeconds for multi data source {0} from {1} to {2}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001258: Unable to setup timer for multi data source {0}, got exception: {1}.

Cause: The reported exception should indicate the cause of the failure.

Action: Refer to the WebLogic Server documentation.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001259: Application has disallowed multi data source {0} from re-enabling data source connection pool {1}, which had previously been found dead and was disabled.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001260: Multi data source {0} unable to enable connection pool {1}, got exception: {2}.

Cause: The reported exception should indicate the cause of the failure.

Action: Refer to the WebLogic Server documentation.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001261: Multi data source {0} unable to enable connection pool {1}, got exception: {2}.

Cause: The reported exception should indicate the cause of the failure.

Action: Refer to the WebLogic Server documentation.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001262: Registered application callback {1} for multi data source {0} to control multi data source failover behavior.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001500: Creating application-coped multi data source {0}, algorithm type {3} for Application {1}, Module {2}.

Cause: The user requested that the multi data source be created, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001501: Creating multi data source {0}, algorithm type {1}.

Cause: A request was made to create the multi data source, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001503: Creating application-scoped data source connection pool {0} for Application {1}, Module {2}, URL = {3}, Properties = {4}.

Cause: A request was made to create the data source connection pool, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001504: Destroying multi data source {0}, created for Application {1}, Module {2}.

Cause: A request was made to destroy the multi data source, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001505: Destroying multi data source Pool {0}.

Cause: A request was made to destroy the multi data source, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001507: Destroying data source connection pool {0}, created for Application {1}, Module {2}.

Cause: A request was made to destroy the data source connection pool, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001508: Destroying data source connection pool {0}.

Cause: A request was made to destroy the data source connection pool, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001510: Creating application-scoped data source {0} for Application {1}, Module {2}, Application Context Name = {3}.

Cause: A request was made to create the data source, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001512: Data source {0} has been successfully created.

Cause: A request was made to create the data source, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001513: Destroying application-scoped data source {0}, created for Application {1}, Module {2}.

Cause: A request was made to destroy the data source, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001514: Destroying data source {0}.

Cause: A request was made to destroy the data source, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001515: Data source {0} has been successfully destroyed.

Cause: A request was made to destroy the data source, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001516: Data source connection pool "{0}" connected to Database: "{1}", Version: "{2}".

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001517: Data source connection pool "{0}" using Driver: "{1}", Version: "{2}".

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001518: Data source connection pool "{0}" Connection Usage Data:

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001519: Id : "{0}"

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001520: Timestamp : "{0}"

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001521: User : "{0}"

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001522: Data source connection pool "{0}" Connection Wait Data:

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001523: Data source connection pool "{0}" Connection Leak Data:

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001524: Data source connection pool "{0}" Connection Reserve Fail Data:

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001525: Data source connection pool "{0}" Statement Cache Entry Data:

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001526: Unable to load class "{0}", got exception : {1}. Driver Interception feature disabled.

Cause: This is most likely because the application-defined class' location has not been added to the CLASSPATH environment varible.

Action: Please check that you specified the correct class name and that your CLASSPATH includes this class.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001527: Application configured class {0} does not implement required interface {1}. Driver Interception feature disabled.

Cause: The configured class {0} does not implement the required interface {1}.

Action: Refer to the WebLogic Server documentation.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001528: Driver Interceptor class {0} loaded.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001529: JDBC loggging last resource (LLR) connection pool {0} did not find its table and is creating a new one using the following SQL: {1}

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001530: JDBC loggging last resource (LLR) connection pool {0} retrieved {1} record(s) from the database table {2}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001531: Received updated event for unexpected type of bean: {0}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001532: Data source connection pool "{0}" Statement Usage Data:

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001533: Pool Name : "{0}"

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001534: Data source connection pool "{0}" Connection Last Usage Data:

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001535: Data source connection pool "{0}" Connection Multi-threaded Usage Data:

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001536: Creating multi data source named {0}, JNDI Name = {1}.

Cause: A request was made to create the multi data source, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001537: Creating application-scoped multi data source {0} for Application {1}, Module {2}, Application Context Name = {3}.

Cause: A request was made to create the multi data source, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001538: Created multi data source named {0}.

Cause: A request was made to create the multi data source, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001539: Destroying multi data source {0}.

Cause: A request was made to destroy the multi data source, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001540: Destroying application-scoped multi data source {0}, created for Application {1}, Module {2}.

Cause: A request was made to destroy the multi data source, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001541: Destroyed multi data source named {0}.

Cause: A request was made to destroy the multi data source, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001542: JVM DriverManager Login Timeout value set to {0}.

Cause: The application has specified this behavior to be enabled, via the corresponding configuration setting.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001543: Received change event: {1} for unexpected type of bean: {0}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001544: Received add event: {1} for unexpected type of bean: {0}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001545: Received unexpected event: {1} for unexpected type of bean: {0}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001546: Data source connection pool "{0}" is being started by user "{1}".

Cause: The specified data source connection pool is being started, as requested by the administrator.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001547: The "{0}" field value "{1}" in table reference "{2}" format [[[catalog.]schema.]table) is too long. The database supports a maximum length of "{3}" for this field.

Cause: This is a configuration error.

Action: When configuring a table name, choose a shorter name for the indicated field. Note that JDBC stores automatically append "WLStore" to the table name.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001548: Empty field value in table reference "{0}" (format [[[catalog.]schema.]table).

Cause: This is a configuration error.

Action: Ensure that the entire table reference is blank, or that the table field is not blank. If there is no schema, ensure that there are no periods "." in the table reference. Do not start the table reference with a period ".". Note that JDBC stores automatically append "WLStore" to table references.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001549: An old style WebLogic driver URL {0} is used. Because the WebLogic driver URL auto-convert switch is turned on, it is converted to {1}.

Cause: An old style WebLogic driver URL is used and the WebLogic driver URL auto-convert switch is turned on.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001550: WebLogic Oracle driver is being used. The driver URL is {0}. WebLogic Server no longer supports the WebLogic Oracle driver.

Cause: The WebLogic Oracle driver has been deprecated and removed.

Action: Stop using the WebLogic Oracle driver, use the Oracle Thin driver instead.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001551: Application context for member data source {1} not found for standalone multi data source module {0}. Ensure that multi data source standalone modules have a higher deployment order than member data source standalone modules.

Cause: The deployment order of the multi data source is the same or lower than one of its member datasources.

Action: Change the deployment order of the standalone multi data source to be greater than each member data source's deployment order.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001552: The logging last resource (LLR) data source {0} will not function when it is a participant in a global transaction that spans multiple WebLogic Server instances because remote JDBC support is disabled. LLR will function in single-server configurations.

Cause: Remote JDBC access over RMI is disabled.

Action: Either configure the data source to use an XA-capable driver, or enable remote JDBC on all servers.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001553: Unable to deploy JDBC data source {0}. No credential mapper entry found for password indirection user {1}

Cause: No credential mapper entry was found for user {1} on data source {0}

Action: Ensure that a credential mapper entry is defined for the data source {0} that maps the specified user name {1} to a password. The WebLogic Server administration console provides support for managing data source credential mapper entries.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001554: Data source connection pool "{0}" Connection Unwrap Data:

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001555: Invalid member data source {1} specified for multi data source {0}. GridLink data source may not be used in multi data source configurations.

Cause: A GridLink data source was specified as a multi data source member.

Action: Either use a single GridLink data source or define generic data sources for use in a multi data source configuration.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001556: Data source {0} for service {1} registering with ONS daemons using configuration string {2}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001557: Data source {0} for service {1} unregistering with ONS daemons {2}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001558: Data source {0} for service {1} received a service down event for instance {2}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001559: Data source {0} for service {1} received a node down event for node {2}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001560: Data source {0} for service {1} received a service up event for instance {2}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001561: Data source {0} for service {1} received a node up event for node {2}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001562: Data source {0} for service {1} not registering for Fast Application Notification (FAN) events.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001563: ADM_DDL LLR (logging last resource) connection pool {0} did not find its table {1}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001564: JTSLoggableResourceTable.existsForADMDDL about to return: return value = {0}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001565: Logging last resource (LLR) data source {0} using LLR table {1} defined by system property weblogic.llr.table.{0}

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001566: JTSLoggableResourceTable.init for ADMDDL is generating SQL statement(createSQL): {0}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001567: SQLRuntimeException caught at existsForADMDDL for poolName: {0} ddlName: {1} by: {2}.

Cause: Look at the printed exception to see why the call failed.

Action: Correct the problem and run the operation again.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001568: Data source {0} for service {1} received a service up event

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001569: Data source {0} failed to create runtime MBean for RAC instance {1}. Exception={2}

Cause: Refer to the exception error message for the cause of the failure.

Action: Try redeploying the data source or restart the WebLogic Server instance.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001570: Attempt to enable Fast Application Notification (FAN) support for a non-GridLink data source {0}, which is not supported.

Cause: Subscribing to FAN events is only supported by GridLink data sources.

Action: Either set the FAN enabled attribute to false or configure a GridLink data source.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001571: Unable to load the connection labeling callback class "{0}", got exception : {1}.

Cause: This is most likely because the application-defined class' location has not been added to the CLASSPATH environment varible.

Action: Please check that you specified the correct class name and that your CLASSPATH includes this class.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001572: Application-configured connection labeling callback class {0} does not implement required interface {1}.

Cause: The configured class {0} does not implement the required interface {1}.

Action: Refer to the WebLogic Server documentation.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001573: Connection labeling callback class {0} loaded.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001574: Unable to load the connection Initialization callback class "{0}", got exception : {1}.

Cause: This is most likely because the application-defined class' location has not been added to the CLASSPATH environment varible.

Action: Please check that you specified the correct class name and that your CLASSPATH includes this class.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001575: Application configured connection initialization callback class {0} does not implement required interface {1}.

Cause: The configured class {0} does not implement the required interface {1}.

Action: Refer to the WebLogic Server documentation.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001576: Connection Initialization callback class {0} loaded.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001580: An exception was thrown from the ConnectionHarvestingCallback: {0}.

Cause: The application callback threw an exception when the callback was called.

Action: Look at the associated message. If more information is desired, turn on connection debuggging.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001581: An invalid scope of Application instead of Global is specified for data source {0}, URI = {1}.

Cause: The configuration is invalid. The specified datasource must have a Global scope.

Action: Correct the configuration for the specified datasource.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001582: oracle.jdbc.DRCPConnectionClass must be specified if and only if a Database Resident Connection Pooling (DRCP) pool is defined.

Cause: The configuration is invalid.

Action: Correct the configuration for the specified data source.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001583: The WebLogic statement cache size is disabled because Oracle statement cache is configured.

Cause: The WebLogic statement cache is disabled.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001584: Data source connection pool "{0}" disabled by multi data source "{1}".

Cause: The specified data source connection pool has been disabled by a multi data source.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001585: Data source connection pool "{0}" re-enabled by multi data source "{1}".

Cause: The specified data source connection pool has been re-enabled by a multi data source.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001586: EndRequest failed: {0}

Cause: This generally happens because the application failed to complete a local transaction before closing the connection. See the associated message to determine if this is the case.

Action: The error is ignored if the connection can be cleared. This is, however, an application error to not complete the transaction. Fix the software.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001587: For LLR RAC DataSource {0} Member of MultiDataSource, test-on-reserve is disabled, and the health of the DataSource can not be verified.

Cause: Test on Reserve is disabled in the DataSource configuration.

Action: Enable Test on Reserve in the DataSource configuration. If all memeber DataSources are marked as unhealthy and the WLS admin server fails to boot use WLST to change configuration.
Level: 1

Type: WARNING

Impact: JDBC

BEA-002001: Received an unknown message type.

Cause: This should not occur. This indicates that the client is sending garbaged messages. It might also indicate that malicious third parties are trying to access the server using IIOP.

Action: Contact My Oracle Support.
Level: 1

Type: NOTIFICATION

Impact: IIOP

BEA-002002: Failed to parse method name {0}.

Cause: This can happen for a variety of reasons. Normally, it is because the caller made a request for a non-existent method. Alternatively, the IDL mangling of the method name may be ambiguous, so WebLogic Server cannot decide which method to call.

Action: If the IDL mangling is causing a problem, try changing the name of the method. In particular, names such as getSomedata() (where somedata is also the name of an attribute or method) can cause problems. Also, some bugs with name mangling exist in JDK 1.3.1. Try using a JDK 1.4 client.
Level: 1

Type: NOTIFICATION

Impact: IIOP

BEA-002003: Unable to send the message: {0}.

Cause: Some sort of communication failure has occurred. This could be because the target closed the IIOP connection or because of some transient network fault.

Action: Verify that the client-server network connection is working.
Level: 1

Type: ERROR

Impact: IIOP

BEA-002005: OutOfMemoryError in adapter: {0}.

Cause: This is often caused by marshalling mismatches between the client and the server and is generally a bug in either the client or the server or both.

Action: Restart the server and contact My Oracle Support.
Level: 1

Type: INTERNAL_ERROR

Impact: IIOP

BEA-002006: Cannot scavenge idle connections, {0}

Cause: The server was unable to schedule a trigger to watch for idle IIOP connections. The fact that it was unable to do so indicates some core failure in the server.

Action: Restart the server. If this occurs again, contact Oracle Customer Support.
Level: 1

Type: ERROR

Impact: IIOP

BEA-002008: Failed to export {0}. The following exception occurred: {1}.

Cause: This is most often caused by the server being unable to find or generate an IIOP stub for the remote object. Ensure that the Common Object Request Broker API (CORBA) objects have corresponding _Stub classes in the server classpath. RMI-IIOP object stubs should be generated automatically.

Action: For CORBA objects, ensure that the idlj was run on the server class. For RMI-IIOP objects, contact My Oracle Support.
Level: 1

Type: NOTIFICATION

Impact: IIOP

BEA-002011: Failed to marshal exception {0}: {1}.

Cause: The server could not find the appropriate exception definitions in its classpath. For Common Object Request Broker API (CORBA) exceptions, the application must contain the exception helper classes as well as the exception classes.

Action: Add missing exception classes to the application.
Level: 1

Type: ERROR

Impact: IIOP

BEA-002012: Failed to send exception {0}: {1}.

Cause: This only happens if the connection between the client and server was very unreliable.

Action: Verify that the client-server network connection is working. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: IIOP

BEA-002013: Complete failure to send exception {0}: {1}.

Cause: Some sort of communication failure has occurred. This could be because the target closed the IIOP connection or because of some transient network fault.

Action: Verify the client-server network connection.
Level: 1

Type: ERROR

Impact: IIOP

BEA-002014: IIOP subsystem enabled.

Cause: The IIOP subsystem is operational and is listening for incoming IIOP requests.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: IIOP

BEA-002015: Using javax.rmi.CORBA.UtilClass {0}; The IIOP subsystem requires a WebLogic Server-compatible UtilClass.

Cause: Some application code, or a foreign object request broker (ORB), set the system property javax.rmi.CORBA.UtilClass or tried accessing javax.rmi.CORBA.Util functions before the IIOP subsystem had initialized.

Action: The IIOP subsystem will not function correctly in this scenario. Correct the application code and restart the server.
Level: 1

Type: ERROR

Impact: IIOP

BEA-002016: Using javax.rmi.CORBA.PortableRemoteObjectClass {0}, the IIOP subsystem requires a WebLogic Server-compatible PortableRemoteObjectClass.

Cause: Some application code, or a foreign object request broker (ORB), set the system property javax.rmi.CORBA.PortableRemoteObjectClass or tried accessing javax.rmi.PortableRemoteObject functions before the IIOP subsystem had initialized.

Action: The IIOP subsystem will not function correctly in this scenario. Correct the application code and restart the server.
Level: 1

Type: ERROR

Impact: IIOP

BEA-002017: LocateRequest is {0}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: IIOP

BEA-002018: Default GIOP version is 1.{0}

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: IIOP

BEA-002019: LocationForward policy is {0}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: IIOP

BEA-002021: SecurityService registered under {0}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: IIOP

BEA-002022: Could not bind SecurityService {0}.

Cause: This is an internal JNDI problem.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: IIOP

BEA-002023: Could not resolve SendingContext RunTime: {0}.

Cause: An invalid object reference for SendingContext RunTime was provided by the client.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: IIOP

BEA-002026: Transaction mechanism is {0}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: IIOP

BEA-002027: Complete failure to rewrite exception from {0}: {1}.

Cause: This error should not occur.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: IIOP

BEA-002028: An OTS error occurred: {0}, {1}.

Cause: OTS errors are generally not bugs but always result in exception information being lost when propagated to the caller. Thus, the root cause is always logged, so that system administrators can determine the real cause. OTS errors are generally caused by some transaction subsystem operation (for instance, a transaction being rolled back).

Action: Ensure that this is an expected error.
Level: 1

Type: WARNING

Impact: IIOP

BEA-002033: Codeset for {0} data set to {1}, OSF registry entry {2}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: IIOP

BEA-002037: CosNaming Service registered under {0}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: IIOP

BEA-002038: Could not bind the CosNaming Service {0}.

Cause: This is an internal JNDI problem.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: IIOP

BEA-002039: Replacer: {0}

Cause: The replacer did not have enough information to do a proper replacement.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: IIOP

BEA-002041: Connection attempt was rejected because IIOP is not enabled on this channel.

Cause: The connection attempt was rejected because IIOP is not enabled at all for this server, as determined by the ServerMBean, or is not enabled on this particular channel.

Action: Enable IIOP.
Level: 1

Type: WARNING

Impact: IIOP

BEA-002043: Naming exception: {0}

Cause: A standard exception was generated by the naming implementation.

Action: No action is required.
Level: 1

Type: WARNING

Impact: IIOP

BEA-002605: Adding address: {0} to the licensed client list.

Cause: The server accepted a connection from the specified client.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002606: The server is unable to create a server socket for listening on channel "{3}". The address {0} might be incorrect or another process is using port {1,number,0}: {2}

Cause: The address was incorrect or another process was using the port.

Action: Use ipconfig or ifconfig to check if the listen address is valid, and use netstat to check that the specified port is not in use by another process.
Level: 1

Type: ERROR

Impact: Server

BEA-002607: Channel "{2}", listening on {0}:{1,number,0}, was shut down.

Cause: The server or channel was shut down.

Action: No action is required. If this was an unexpected error, contact My Oracle Support.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002608: The ListenThread failed because of an error: {0}

Cause: An exception occurred when the server socket was unable to accept client connections.

Action: Check the file descriptor limit. Tune the operating system parameters that handle socket creation using ServerSocket.
Level: 1

Type: ERROR

Impact: Server

BEA-002609: Channel Service initialized.

Cause: The Channel subsystem is operational.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002610: Dynamic Listener Service initialized.

Cause: The dynamic listener subsystem is operational.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002611: The hostname "{0}", maps to multiple IP addresses: {1}.

Cause: The host name of the server resolved to multiple IP addresses, which can cause problems for the Administration Server.

Action: Check if this was done on purpose.
Level: 1

Type: WARNING

Impact: Server

BEA-002612: Channel "{2}", listening on {0}:{1,number,0}, did not start did not start properly.

Cause: Some of the listen ports did not open or failed within the configured grace period.

Action: Ensure that none of the configured listen ports are in use by other processes.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002613: Channel "{2}" is now listening on {0}:{1,number,0} for protocols {3}.

Cause: The server successfully started the listen thread and server socket.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002614: Reopening channel "{2}" on {0}:{1,number,0}.

Cause: The server backed off because a socket exception occurred while accepting client connections. The server is now ready to accept connections.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002615: After having failed to listen, the server is now listening on channel "{2}" on {0}:{1,number,0}.

Cause: The server backed off because a socket exception occurred while accepting client connections. The server is now ready to accept connections.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002616: Failed to listen on channel "{2}" on {0}:{1,number,0}, failure count: {3}, failing for {4} seconds, {5}

Cause: An exception occurred while trying to accept client connections. The server will try to back off to aid recovery.

Action: The operating system (OS) limit for the number of open file descriptors (FD limit) needs to be increased. Tune the OS parameters that might help the server to accept more client connections (for example, TCP accept back log).
Level: 1

Type: INTERNAL_ERROR

Impact: Server

BEA-002617: Attempting to close and reopen the server socket on channel "{2}" on {0}:{1,number,0}.

Cause: The server listener could not accept a socket connection and failed after several simple retries. It has closed and reopened the server socket.

Action: Check if the file decriptor limit needs to be increased. Tune the operating system parameters that might help the server accept more client connections.
Level: 1

Type: INTERNAL_ERROR

Impact: Server

BEA-002618: An invalid attempt was made to configure a channel for unconfigured protocol "{0}".

Cause: The server configuration specified a channel that uses a protocol that is not enabled.

Action: Enable the protocol in the server configuration.
Level: 1

Type: ERROR

Impact: Server

BEA-002619: One or more listen ports did not start properly.

Cause: One or more listen ports failed to open during server startup.

Action: Ensure that none of the configured listen ports are in use by other processes.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002620: An invalid attempt was made to configure a channel for server "{0}" on an unknown listen address "{1}".

Cause: The server configuration specified a channel that uses a listen address that does not exist.

Action: Correct the server configuration.
Level: 1

Type: ERROR

Impact: Server

BEA-002621: The connection was rejected because the server license only allows connections from {0} unique IP addresses.

Cause: Clients tried to connect from more distinct addresses than the license allows.

Action: Use a server license that allows for more clients to connect.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002622: The protocol "{0}" is now configured.

Cause: The server has loaded a protocol making it available for outbound traffic and configurable for inbound traffic.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002623: Connection rejected, the server is in the {0} state. Starting service {1}, {2} of {3}. Last service {4} took {5} milliseconds.

Cause: Clients tried to connect to the server before it was in the RUNNING state.

Action: Connect to the server after it has started.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002624: The administration protocol is "{0}" and is now configured.

Cause: The server has loaded the administration protocol making it available for outbound traffic and configurable for inbound traffic.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002625: An attempt to configure channel "{0}" failed because of {1}.

Cause: The cause is detailed in the accompanying exception.

Action: Review the exception.
Level: 1

Type: ERROR

Impact: Server

BEA-002626: The protocol "{0}" could not be loaded: {1}

Cause: Consult the exception for why the protocol could not be loaded.

Action: Consult the exception for why the protocol could not be loaded.
Level: 1

Type: WARNING

Impact: Server

BEA-002627: The domain configuration must have at least one administration channel on every server or no administration channels at all.

Cause: The server was contacted by a server that did not reflect the same administration state as itself.

Action: Modify the domain configuration so that all servers have administration channels, or enable the domain-wide administration port.
Level: 1

Type: ERROR

Impact: Server

BEA-002628: Unable to export RemoteLifeCycleOperations RMI object due to {0}.

Cause: The RMI export failed.

Action: Contact My Oracle Support and provide the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: Server

BEA-002630: Accepting connections again.

Cause: The server is accepting client connections again after refusing connections as part of server throttling.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002631: Max threshold reached for open sockets [total open sockets: {0}, allowed max: {1}]. No more connections allowed.

Cause: The MaxOpenSocketCount attribute of the server configuration defines the upper bound of the number of open sockets.

Action: Increase the MaxOpenSocketCount attribute of the server configuration. Use the server tuning tab in the Administration Console.
Level: 1

Type: WARNING

Impact: Server

BEA-002632: Found jrmp.jar in {0} directory. JRMP service is now enabled.

Cause: JRMP is enabled.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002633: A port conflict was detected in the server configuration. The server is configured to listen on two ports that have the same port number and IP address. Channel "{0}" address "{1}" conflicts with channel "{2}" address "{3}".

Cause: The server is configured to listen on two ports that have the same port number and IP address.

Action: Ensure that the address identities [ListenAddress and ListenPort combinations] are distinct and unique.
Level: 1

Type: INTERNAL_ERROR

Impact: Server

BEA-002634: The server "{0}" disconnected from this server.

Cause: The remote server may have crashed, been shut down normally or been partitioned from the network.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002635: The server "{0}" connected to this server.

Cause: The remote server may have been booted or a network partition may have been resolved.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002636: Unable to update server "{0}" with local channel information.

Cause: The remote server may have crashed, been shut down normally or been partitioned from the network.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Server

BEA-002637: Failed to register a disconnect listener because of {0}

Cause: This can happen during server startup when the incoming network connection is not suitable for callbacks and the booting server does not yet have a listen port open.

Action: No action is required. The server should eventually be connected properly.
Level: 1

Type: WARNING

Impact: Server

BEA-002638: {0} was issued remotely from {1}.

Cause: Log the host address of the machine that issued the SLC operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002639: ServerRuntime:{0}

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002640: A request has been received to force a shutdown of the server.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002641: -DserverType is set to an unrecognized value: {0}. The server will start with all services enabled.

Cause: An undefined server type was specified or a typographical error was made.

Action: See the WebLogic Server documentation for valid values for -DserverType.
Level: 1

Type: WARNING

Impact: Server

BEA-002642: {0} not found. The server will start with all services enabled.

Cause: The file was deleted or moved.

Action: Replace the file from the WebLogic Server installation.
Level: 1

Type: WARNING

Impact: Server

BEA-002643: Attempt to read {0}, failed: {1}

Cause: The file has been corrupted or had its permissions changed.

Action: Replace the file with one from the WebLogic Server installation.
Level: 1

Type: WARNING

Impact: Server

BEA-002644: The JAR file {0} being processed as a potential service plug-in could not be read: {1}

Cause: The file may be damaged.

Action: Check the file, replace & and try again.
Level: 1

Type: ERROR

Impact: Server

BEA-002645: The manifest of the JAR file {0} being processed as a potential service plug-in, could not be read: {1}

Cause: The manifest may be corrupted.

Action: Replace the file and retry.
Level: 1

Type: ERROR

Impact: Server

BEA-002646: Unable to load the service plug-in activator class from {0}: {1}

Cause: The plug-in JAR file does not meet the service plug-in requirements.

Action: Check the contents of the JAR file and retry.
Level: 1

Type: ERROR

Impact: Server

BEA-002647: The service plug-in, {1}, was added from {0}.

Cause: The plugin was placed in the domain lib directory.

Action: No action is required. To remove the plug-in, remove it from the domain lib directory.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002648: Could not obtain the relevant ServerRuntimeMBean for server {0}.

Cause: The remote server runtime object for server {0} could not be obtained. This can happen if the server has already been shut down or is otherwise unavailable.

Action: If the server is active when this error occurs, contact My Oracle Support.
Level: 1

Type: WARNING

Impact: Server

BEA-002649: A port conflict was detected in the server configuration. Both TCP and SDP channels are configured to listen on the same port number and IP address. Channels "{0}" and "{1}" on address "{2}".

Cause: Both TCP and SDP channels are configured to listen on the same port number and IP address.

Action: Ensure that the channels with the same [ListenAddress and ListenPort combinations] either all support SDP or do not support SDP.
Level: 1

Type: INTERNAL_ERROR

Impact: Server

BEA-002650: Unable to schedule reconnection to a disconnected server.

Cause: The default timer manager has stopped. This is normal during server shutdown.

Action: None required if the server is in the process of shutting down.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002651: The process for the server {0} has not completely shut down. This problem should be reported and you may have to kill the process manually.

Cause: The process for the server {0} has not completely shut down.

Action: Kill the process manually.
Level: 1

Type: ERROR

Impact: Server

BEA-002900: Initializing self-tuning thread pool.

Cause: The server is starting.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002901: Creating Work Manager "{2}" for module "{0}" and application "{1}"

Cause: The application is being initialized.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002902: Creating execute queue "{0}".

Cause: The server is starting.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002903: Creating Work Manager from "{1}" WorkManagerMBean for application "{0}"

Cause: The application is being initialized.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002905: Removing {0} threads from the thread pool.

Cause: The server has realized that some threads are not needed to handle the present load.

Action: No action is required as the server auto tunes.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002908: Unable to create runtime MBean for Work Manager {0}. {1}

Cause: A fatal error occurred while creating the runtime MBeans.

Action: Contact My Oracle Support with the server logs.
Level: 1

Type: INTERNAL_ERROR

Impact: WorkManager

BEA-002911: Work Manager {0} failed to schedule a request due to {1}

Cause: Work Manager did not schedule a request due to a fatal failure.

Action: This is a critical failure. Report to My Oracle Support with the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: WorkManager

BEA-002912: Overload Manager {0} rejected request as current length {1} exceeds max capacity of {2}

Cause: A request was rejected as the overload capacity was reached or exceeded.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002913: Work Manager {0} rejected request as the server is low on memory

Cause: A request was rejected as the server was low on memory.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002914: Shutdown callback invocation failed with: {0}

Cause: There was an internal error in the application shutdown.

Action: Report to My Oracle Support with the logs.
Level: 1

Type: ERROR

Impact: WorkManager

BEA-002916: Request belonging to Work Manager {0}, application {1} is rejected as the WorkManager is shutdown.

Cause: The request was refused entry because the Work Manager was shutdown.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002917: Enqueued request belonging to Work Manager {0}, application {1} is cancelled as the Work Manager is shutdown.

Cause: The request was refused because the Work Manager was shutdown.

Action: No action was required.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002918: Server detected execute queue(s) in self-tuning mode. Execute queues will not be self-tuned. They retain their behavior from earlier releases. Consider using Work Managers to take advantage of self-tuning.

Cause: The execute queues were detected in the self-tuning server.

Action: Consider removing the execute queues. The server automatically adjusts the thread pool size for optimal performance. Work Managers can be used to change the default behavior where needed.
Level: 1

Type: WARNING

Impact: WorkManager

BEA-002919: Unable to find a Work Manager with name {0}. Dispatch policy {0} will map to the default Work Manager for the application {1}

Cause: There is no Work Manager with the given name.

Action: This could indicate a configuration error. Check the dispatch-policy and ensure that it matches the name of a Work Manager defined either within the same application or globally.
Level: 1

Type: WARNING

Impact: WorkManager

BEA-002920: An instance of the mSA Work Manager

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002921: The name of the Work Manager

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002922: The number of waiting requests in the queue

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002923: The number of requests that have been processed

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002924: An instance of the MinThreadsConstraint for a particular Work Manager

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002925: Completed request count

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002926: Pending requests that are waiting for an available thread

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002927: Number of requests that are currently executing

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002928: Number of requests executed out of turn to satisfy this constraint

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002929: Number of requests that must be executed to satisfy the constraint

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002930: The maximum time a request had to wait for a thread. Only requests whose execution is needed to satisfy the constraint are considered.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002931: Number of requests that must be executed to satisfy the constraint

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002932: An instance of the MaxThreadsConstraint for a particular Work Manager

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002933: Number of requests that are currently executing

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002934: Number of requests that are denied a thread for execution because the constraint is exceeded

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002935: request-class-name reference within ContextCase element for entry {0} with value: {1} ;cannot be resolved for Work Manager.

Cause:

Action:
Level: 1

Type: WARNING

Impact: WorkManager

BEA-002936: maximum thread constraint {0} is reached

Cause: The number of threads assigned to this work manager has reached the configured value in the maximum threads constraint

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002937: The maximum thread constraint {0} is no longer reached.

Cause: The number of threads assigned to this Work Manager has dropped below the configured value in the maximum threads constraint.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002938: Global work manager "{0}" created with customized configuration

Cause: The default configuration for a global work manager has been overriden and the work manager is created with a customized configuration

Action: no action needed
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002939: The maximum thread constraint {0} has been reached {1} times for the last {2} seconds.

Cause: The number of threads assigned to this work manager has reached the configured value for the maximum threads constraint.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002940: Shutting down work manager "{0}" according to the configured work manager shutdown trigger.

Cause: A work manager is being shut down because the number of stuck threads has reached the configured value in a work manager shutdown trigger.

Action: Monitor the stuck threads to determine the reason why the requests have been taking a long time to process. If resumeWhenUnstuck is true, the work manager will be resumed when there are no more stuck threads for the work manager.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-003000: Could not send cache multicast message for key "{0}", {1}.

Cause: UThis error is usually caused by some communication failure.

Action: Check the exception message for details.
Level: 1

Type: WARNING

Impact: Cache

BEA-003001: Leasing failure: {0}

Cause: This error is usually caused by some communication failure.

Action: Check the exception message for details.
Level: 1

Type: WARNING

Impact: Cache

BEA-003002: Replication failure: {0}

Cause: This error is usually caused by some communication failure.

Action: Check the exception message for details.
Level: 1

Type: WARNING

Impact: Cache

BEA-003004: Unexpected failure {0}

Cause: This is a general purpose warning message.

Action: No action is required. The cache will try to adjust to the failure.
Level: 1

Type: WARNING

Impact: Cache

BEA-003005: CacheFilter not caching the response for uri: {0} reason: {1}

Cause: CacheFilter does not cache responses unless the status is 200.

Action: Check the message for information on how to fix the problem.
Level: 1

Type: WARNING

Impact: Cache

BEA-003090: Could not send cache multicast message for key "{0}", {1}.

Cause: This error is usually caused by some communication failure.

Action: Check the exception message for details.
Level: 1

Type: WARNING

Impact: LLD

BEA-003101: Modified non-dynamic {0} property on the Administration Server.

Cause: The non-dynamic {0} property was updated while the server was in a running state.

Action: Reboot the Administration Server so that the {0} property takes effect.
Level: 1

Type: WARNING

Impact: Cluster

BEA-003102: There was a failure in the execution of the post script {0} while deactivating MigratableTarget {1}. Since post script failure is marked as fatal, the MigratableTarget will not be automatically migrated. To enable automigration, fix the post script failure and manually migrate the failed migratable target or disable the post script failure fatal flag.

Cause: The execution ofthe post deactivation script failed.

Action: Fix the post deactivation script and migrate the MigratableTarget manually.
Level: 1

Type: ERROR

Impact: Cluster

BEA-003103: {0} failed to release its lease because of {1}. This may affect its automatic migration behavior.

Cause: An exception occurred: {1}.

Action: If a database is being used for leasing, ensure that it is available.
Level: 1

Type: ERROR

Impact: Cluster

BEA-003104: Failed to notify the execution failure of the post script {1} for {0} to the SingletonServiceStateManager because of {2}. This may affect its automatic migration behavior.

Cause: An exception occurred: {2}.

Action: Ensure that the network is working properly.
Level: 1

Type: ERROR

Impact: Cluster

BEA-003105: The asynchronous replication request timed out while attempting to add object {0} to the replication queue. This session has not been replicated to any backup at this point.

Cause: The asynchronous replication request timed out while attempting to add object {0} to the replication queue. Once full, the queue waits until it has space for the object. This wait took longer than the ClusterMBean specified AsyncSessionQueueTimeout, thus the session object was not put into the queue and will not be replicated at this time.

Action: This could be due to the secondary server or persistent store slowing down the replication process. To better handle this, the SessionFlushInterval and the SessionFlushThreshold can be reduced to replicate less at a time and to replicate more often. Checking the performance of the secondary server or persistent store is advised.
Level: 1

Type: WARNING

Impact: Cluster

BEA-003106: An unexpected exception occured during replication: {0}. Future session updates should replicate as expected.

Cause: An unexpected runtime exception occured during replication probably from the Remote Management Interface (RMI) stub. Future session updates should replicate as expected.

Action: Ensure that no problems exist in the network. If the problem persists, contact My Oracle Support. with the stack trace for further analysis.
Level: 1

Type: WARNING

Impact: Cluster

BEA-003107: Lost {0} unicast message(s).

Cause: This is an informational message. When a server joins a stable cluster, this message will appear since the server did not receive unicast messages sent out by other servers in the cluster.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-003108: Unicast receive error : {0}

Cause: An error occurred while trying to receive a message over the cluster broadcast.

Action: Ensure that the NIC is functioning properly. If it appears that no environment problems exist, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: Cluster

BEA-003109: Cluster {0} uses a database as the migration basis but no data source for migration has been configured.

Cause: Cluster {0} uses a database as the migration basis but no data source for migration has been configured.

Action: Ensure that the data source is created and set for database migration basis.
Level: 1

Type: ERROR

Impact: Cluster

BEA-003110: Connection attempt was rejected because the incoming protocol {1} is not enabled on channel {0}.

Cause: The connection attempt was rejected because the {1} protocol is not enabled at all for this server, as determined by the ServerMBean, or is not enabled on this particular channel.

Action: Enable the {1} protocol on the channel.
Level: 1

Type: WARNING

Impact: Cluster

BEA-003111: No channel exists for replication calls for cluster {0}

Cause: No channel exists for replication calls for cluster {0}

Action: Configure the channels for replication calls.
Level: 1

Type: ERROR

Impact: Cluster

BEA-003112: Channels "{0}" configured for replication traffic.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-003113: Using one-way RMI for replication

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-003114: Ignoring one-way RMI calls for replication because multiple replication channels are not present.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-003115: Failed to synchronize a secondary session due to missing updates.

Cause: The Work Manager queue might be full and as a result update messages were dropped.

Action: Either increase the number of servers in the cluster (preferred) or add more replication channels (requires server re-start).
Level: 1

Type: ERROR

Impact: Cluster

BEA-003116: Starting Member Death Detector.

Cause: None.

Action: None.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-003117: Starting Member Death Detector Heartbeat Receiver.

Cause: None.

Action: None.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-003118: WLS Server "{0}" does not have an associated machine configured. Member Death Detector will not be enabled for this server.

Cause: No associated machine configured with the server.

Action: Please associate a machine with this server.
Level: 1

Type: WARNING

Impact: Cluster

BEA-003119: The singleton service {0} is now registered on this server but will not be activated because this server is not part of a cluster.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-003120: hostname {0} is failed to resolve in cluster initialization

Cause: name service like DNS is unavailable or unstable.

Action: Please check name service configuration or name service availability.
Level: 1

Type: WARNING

Impact: Cluster

BEA-003121: Unicast cluster may not function correctly as the listen address of server {0} is not specified.

Cause: The listen address of the Managed Server is not specified.

Action: Set the listen address of the Managed Servers.
Level: 1

Type: WARNING

Impact: Cluster

BEA-003122: {0} : A cluster that has migratable servers could not create/execute SQL statement when validating the database connection. The cluster is misconfigured. Check the leasing table on the database and connection configuration.

Cause: The cluster is misconfigured.

Action: Check the leasing table on the database and connection configuration.
Level: 1

Type: ERROR

Impact: Cluster

BEA-003501: The migration of server {0} from machine {1} has failed. No suitable candidate machines could be found.

Cause: No candidate machines are available, or the server {0} has encountered an error on booting independent of its location.

Action: Further migration of server {0} has been disabled. When the cause of the problem has been determined and fixed, the server {0} should be started by the user, at which point it will resume standard automatic migration behavior.
Level: 1

Type: ERROR

Impact: Cluster

BEA-003502: Beginning the migration of server {0} from machine {1} to machine {2}

Cause: The failure of server {0} has provoked a migration attempt to a new machine, machine {2}.

Action: No action is required, but the logs of server {0} should be examined to determine why it crashed and could not successfully restart on machine {1}.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-003503: The migration of server {0} from machine {1} to machine {2} has succeeded.

Cause: The failure of server {0} provoked a migration attempt to a new machine, machine {2}. The migration is now complete.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-003504: The migration of server {0} from machine {1} to machine {2} has failed, because machine {2} is not reachable.

Cause: Machine {2} was not reachable. A new machine for server {0} will be chosen.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-010000: Exception occurred during ejbActivate: {0}

Cause: An error occurred while calling ejbActivate() on the bean.

Action: Check your implementation of the ejbActivate method.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010001: While deploying EJB "{0}", class {1} was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.

Cause: The specified class is located in the server classpath.

Action: Remove this class from the server classpath. It should only be located in the packaged application.
Level: 1

Type: WARNING

Impact: EJB

BEA-010002: An error occurred while undeploying: {0}.

Cause: An error occurred while undeploying.

Action: Please check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: EJB

BEA-010003: Exception occurred while loading _WL_TIMESTAMP FILE.

Cause: The container generates the _WL_GENERATED file, which stores the server version of the appc compiler. If the current server version is different from the version specified in the _WL_GENERATED file, appc recompiles the beans. There was an error reading this file.

Action: The container will automatically recompile the beans.
Level: 1

Type: ERROR

Impact: EJB

BEA-010006: Error occurred while saving ejb deployment timestamps. {0}

Cause: The container generates the _WL_GENERATED file, which stores the server version of the appc compiler. if the current server version is different from the version specified in the _WL_GENERATED file, appc recompiles the beans. There was an error writing this file.

Action: Please check the exception for the exact error message. The container will recompile the beans if this file is not found.
Level: 1

Type: ERROR

Impact: EJB

BEA-010007: License validation passed for {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010008: EJB Deploying file: {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010009: EJB deployed EJB with JNDI name {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010011: Exception looking up current transaction: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010012: Exception looking up current transaction: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010014: Error occurred while attempting to rollback transaction: {0}

Cause: There was an error when rolling back the transaction.

Action: Please check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010015: Error occurred while marking transaction for rollback: {0}.

Cause: The container was unable to mark the transaction for rollback.

Action: Please check the exception for exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010016: Exception occurred while marking transaction for rollback: {0}.

Cause: The container was unable to mark the transaction for rollback.

Action: Please check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010017: Exception occurred during rollback of transaction {0}: {1}.

Cause: The container was unable to rollback the transaction.

Action: Please check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010018: Error occurred while resuming caller transaction: {0}

Cause: The container was unable to resume the transaction.

Action: Please check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010019: Running in a cluster, but DNS name of cluster is not set. This may prevent EJB handles from operating properly.

Cause: The DNS name of the cluster is not set.

Action: Set the DNS cluster name.
Level: 1

Type: WARNING

Impact: EJB

BEA-010020: EJB-20 - MessageDriven - Could not start the JMS connection: {0}

Cause: The JMS provider may not be available, or the Message-Driven Bean deployment descriptors or annotation or both may not be correct.

Action: Verify that the JMS provider is running and accessible through the network. Verify that the deployment descriptors or annotation or both specify the correct configuration information for the JMS provider.
Level: 1

Type: ERROR

Impact: EJB

BEA-010022: Error occurred in ejbPassivate: {0}.

Cause: There was an error passivating the bean.

Action: Please check the exception for the exact error message. Verify the implementation of the ejbPassivate method in the bean.
Level: 1

Type: ERROR

Impact: EJB

BEA-010024: Error occurred during passivation: {0}

Cause: The container was unable to passivate the bean.

Action: Check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: EJB

BEA-010025: Exception occurred during rollback of transaction {0}: {1}

Cause: An error occurred when rolling back the transaction.

Action: Check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: EJB

BEA-010026: Exception occurred during commit of transaction {0}: {1}.

Cause: An error occurred when committing the transaction.

Action: Check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: EJB

BEA-010029: Exception occurred during commit of transaction {0}: {1}.

Cause: An error occurred while committing the transaction.

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010030: Ignoring exception that occurred when rolling back a transaction during undeployment of {0}.

Cause: An error occurred while undeploying the bean.

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010031: EJB exception in method: {0}: {1}.

Cause:

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010032: Exception during ejbActivate(): {0}

Cause:

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010033: Exception from ejbLoad: {0}

Cause:

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010034: Exception from ejbStore: {0}.

Cause:

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010036: Exception from ejbStore: {0}.

Cause:

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010038: Exception from __WL_superEjbLoad: {0}.

Cause:

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010039: Exception in ejbStore: {0}.

Cause:

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010040: Exception in ejbStore: {0}.

Cause:

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010043: Exception in ejbActivate: {0}.

Cause:

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010044: Exception trying to resume transaction: {0}.

Cause:

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010045: Exception in afterBegin: {0}.

Cause:

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010046: Exception in beforeCompletion: {0}.

Cause:

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010047: Exception during setRollbackOnly: {0}.

Cause:

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010048: Exception in afterCompletion: {0}.

Cause:

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010049: EJB exception in method: {0}: {1}.

Cause:

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010050: A stateless session bean with bean-managed transactions must commit or roll back a transaction before the business method completes.

Cause:

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010051: EJB exception occurred during invocation from home: {0} generated exception: {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010052: An exception occurred while creating the free pool for EJB {0}. Since this occurred during server startup, when a dependent resource may be unavailable, the error will be ignored and deployment will proceed. The EJB container will instead attempt to create the bean instances on demand. The exception was: {1}

Cause: An exception occurred while the EJB container was initializing the free pool of bean instances. The root exception should be printed as part of the warning message issued by the EJB container. Check the server log for further details.

Action: If you believe the root exception is due to a temporary condition that will automatically be resolved, no action is required. If this exception was not due to a temporary condition, fix the cause of the root exception. If changes to your application are required to fix this issue, redeploy the updated application.
Level: 1

Type: WARNING

Impact: EJB

BEA-010054: EJB deployment: {0} has a class {1} that is in the classpath. This class should only be located in the ejb-jar file.

Cause: {1} is in the classpath.

Action: Remove this class from the classpath. It should only be in the ejb-jar.
Level: 1

Type: WARNING

Impact: EJB

BEA-010055: Could not load the RDBMS deployment descriptor for EJB {0} from the file {1}. The file was not found in the JAR file {2}.

Cause: {1} is missing from the JAR file.

Action: Please add the missing file to the JAR file.
Level: 1

Type: ERROR

Impact: EJB

BEA-010057: Could not find a license for EJB 3.0. Please contact Oracle to get a license.

Cause: Unable to get license for EJB 3.0.

Action: Contact Oracle to get a license.
Level: 1

Type: ERROR

Impact: EJB

BEA-010058: The EJB deployment named {0} is being recompiled within the WebLogic Server instance. Please consult the server logs if there are any errors. It is also possible to run weblogic.appc as a standalone tool to generate the required classes.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010059: An error occurred while attempting to invalidate the target Read-Only Entity EJB: {0}. The error was: {1}

Cause: The invalidation of read-only beans failed.

Action: Check the message for the cause.
Level: 1

Type: ERROR

Impact: EJB

BEA-010060: The Message-Driven EJB {0} has connected or reconnected to the JMS destination {1}.

Cause: The JMS connection has been re-established.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010061: The Message-Driven EJB {0} is unable to connect to the JMS destination {1}. The Error was: {2}

Cause: The JMS destination is not available due to a network problem or a problem with the JMS provider, or the configuration information in the MDB deployment descriptor or annotation or both is incorrect. This warning may also occur during WebLogic cluster startup if the JMS destination is located on another server.

Action: Check that the JMS provider is running and that network connectivity is available. Also check that the configuration information in the MDB deployment descriptor and/or annotation is correct.
Level: 1

Type: WARNING

Impact: EJB

BEA-010065: MessageDrivenBean threw an Exception in onMessage(). The exception is: {0}.

Cause: The onMessage method of the MDB may have generated an exception for a legitimate reason, such as the loss of a database connection. If that is not the case, then the MDB may have a programming error that causes it to generate an unchecked Java exception, such as a NullPointerException.

Action: Unless you are sure that the MDB has generated the exception on purpose, check the source code to ensure that it does not contain any programming errors that might cause it to generate an unchecked Java exception such as a NullPointerException or IndexOutOfBoundsException.
Level: 1

Type: WARNING

Impact: EJB

BEA-010066: The Entity EJB {0} generated an exception when its unsetEntityContext was called. This error is ignored by the EJB container. The error is: {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010067: Exception during ejbRemove: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010071: Error occurred while performing Pop of Caller Principal: {0}

Cause: This is a possible internal container error.

Action: Check the security settings related to the run-as roles and principals setting.
Level: 1

Type: ERROR

Impact: EJB

BEA-010072: Error occurred while starting EJB module {0}. Exception is: {1}

Cause: The container was unable to start the EJB module.

Action: Check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: EJB

BEA-010073: Unable to add the {0} interface "{1}" and any dependent classes to the client-jar since it was loaded from the classpath.

Cause: EJB interface and other dependent classes exist in the system classpath.

Action: Please remove the classes from the system classpath.
Level: 1

Type: WARNING

Impact: EJB

BEA-010074: Unable to create the client-jar file due to classes being loaded from the classpath rather than the input JAR. Please modify your classpath so that it does not contain these classes and try again.

Cause: EJB interface and other dependent classes exist in the system classpath.

Action: Please modify your classpath so it does not contain these classes and try again.
Level: 1

Type: WARNING

Impact: EJB

BEA-010075: Skipping creation of the client-jar since no EJBs with a remote client view are contained in the JAR file.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010076: Client-jar {0} created.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010079: An error occurred while attempting to receive a message from JMS for processing by a Message-Driven Bean: {0} The exception is : {1}

Cause: The JMS provider for the MDB may have been shut down or has crashed, or network connectivity may have been lost.

Action: Check that the JMS provider is available and accessible through the network.
Level: 1

Type: ERROR

Impact: EJB

BEA-010080: An error occurred while attempting to process a message inside a Message-Driven Bean: {0} Exception is : {1}

Cause: This error usually occurs if the onMessage method of the MDB throws an exception.

Action: Check that the MDB is able to process messages by ensuring that any resources it uses (such as database connections) are available. Check the MDB source code to ensure that it does not have any bugs that cause an exception (such as a NullPointerException) to be generated.
Level: 1

Type: ERROR

Impact: EJB

BEA-010081: The Message-Driven Bean {0} was configured to use a JMS Topic, requires container-managed transactions, and uses a foreign JMS provider. Only one thread will be used to receive and process all messages.

Cause: The nature of the JMS API does not permit this in a standard way.

Action: No action is required. However, if you require better performance for a foreign JMS provider and do not need exactly-once transactional semantics, redeploy the MDB so that it has a transaction mode of NotSupported.
Level: 1

Type: WARNING

Impact: EJB

BEA-010082: Failed to undeploy security role for resource {0}, while undeploying EJB.

Cause: Unable to remove the role from the security layer.

Action: Check the exception for the exact error message.
Level: 1

Type: WARNING

Impact: EJB

BEA-010083: Failed to undeploy security policy for resource {0}, while undeploying EJB.

Cause: The policy could not be removed from the security layer.

Action: Check the exception for the exact error message.
Level: 1

Type: WARNING

Impact: EJB

BEA-010084: The Message-Driven Beans are being suspended. This may take a minute or two.

Cause: The server is being suspended or shut down.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010085: The Message-Driven Beans have all been suspended.

Cause: The server is being suspended or shut down.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010086: The deployment unit {0} that contains Message-Driven Beans is undeployed already. The server cannot start the Message-Driven Beans that are part of undeployed unit.

Cause: The beans were started after having been undeployed.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010087: The EJB deployment named {0} is being recompiled within the WebLogic Server instance. Please consult the server logs if there are any errors. It is also possible to run weblogic.appc as a standalone tool to generate the required classes. The generated source files will be placed in {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010088: Could not find a license for in-memory replication of the EJB. This feature is disabled.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010089: Failed to create copy of bean {0} with error: {1}.

Cause: The server was unable to create the secondary server.

Action: Check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: EJB

BEA-010090: Failed to update secondary copy with: {0}

Cause: The server was unable to update the secondary.

Action: Check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: EJB

BEA-010091: Failure during stateful session bean replication: {0}

Cause: The container was unable to replicate the stateful session bean.

Action: Check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: EJB

BEA-010092: Failure while updating secondary server during replication of {0}. The error was: {1}

Cause: The server was unable to update the secondary server.

Action: Check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: EJB

BEA-010094: Failed to update the secondary copy of a stateful session bean from home {0}.

Cause: The server was unable to update the secondary server.

Action: Check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: EJB

BEA-010096: The Message-Driven EJB {0} is unable to connect to the JMS destination or bind to JCA resource adapter {1}. The onnection failed after {2} attempts. The MDB will attempt to reconnect/rebind every {3} seconds. This log message will repeat every {4} seconds until the condition clears.

Cause: The JMS provider or JCA resource adapter is not available, or the configuration is incorrect and WebLogic Server is not able to connect.

Action: Ensure that the JMS provider is running and is reachable using the network, or the JCA resource adapter is deployed. Also ensure that the configuration information in the MDB deployment descriptor or the annotation or both are correct.
Level: 1

Type: WARNING

Impact: EJB

BEA-010097: Exception occurred during the invocation of EJB {0} with primary key {1}.

Cause: The bean generated a system exception.

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010098: The database type {0} mentioned in weblogic-cmp-rdbms-jar.xml does not match the database type returned by the driver {1}.

Cause: The database type {0} mentioned in weblogic-cmp-rdbms-jar.xml does not match the database type returned by the driver {1}.

Action: Check the database-type tag inside weblogic-cmp-rdbms-jar.xml.
Level: 1

Type: WARNING

Impact: EJB

BEA-010099: WARNING(S) from EJB QL Compiler. {0}

Cause: The compilation of EJB-QL succeeded. These are some non-fatal warnings.

Action: Check the message for the exact warnings.
Level: 1

Type: WARNING

Impact: EJB

BEA-010100: This server is not part of a cluster. Therefore the InMemory replication feature for StatefulSession EJB {0} will have no effect on this server.

Cause: The bean has been deployed on a server, which is not a part of cluster. Hence the InMemory replication feature will be ignored.

Action: No action is required.
Level: 1

Type: WARNING

Impact: EJB

BEA-010102: Error encountered while attempting to create default DBMS table {0}. Error text: {1}

Cause: An error was encountered while attempting to create the default DBMS table.

Action: Take appropriate action based on the logged error message.
Level: 1

Type: ERROR

Impact: EJB

BEA-010124: Method SecurityHelper.{0} returned a NULL principal. The CallerPrincipal stack has been corrupted.

Cause: One cause of corruption might be that a bean has created its own threads. Note that this would be in violation of EJB2.0 Final Spec Chapter: Runtime Management 24.1.2.

Action: Review your code about thread safety. If a bean does not create its own thread, this is likely a bug in the EJB subsystem and you should probably contact My Oracle Support.
Level: 1

Type: ERROR

Impact: EJB

BEA-010127: Incorrect data source type detected. The data source with JNDI name {0}, specified in the RDBMS deployment descriptor for the EJB {1}, does not support global transactions.

Cause: The EJB container requires that a data source which supports global transactions be specified for transactions to be managed correctly.

Action: Specify the correct data source for the EJB.
Level: 1

Type: ERROR

Impact: EJB

BEA-010128: Error during deployment of EJB {0}. The EJB references an application-level cache, {1}, that is not defined in the weblogic-application.xml descriptor.

Cause: The weblogic-ejb-jar.xml descriptor for the EJB refers to an unknown application-level cache.

Action: Ensure that the application-level cache is defined in the weblogic-application.xml descriptor and ensure the cache name defined in the weblogic-ejb-jar.xml is correct.
Level: 1

Type: ERROR

Impact: EJB

BEA-010129: Error during deployment of EJB {0}. The EJB references a MultiVersion application-level cache {1}, but it must use an Exclusive cache instead. EJBs with a concurrency-strategy of Exclusive must use an Exclusive cache.

Cause: An incorrect concurrency strategy is specified. The concurrency-strategy you specify for the bean must be compatible with the caching-strategy specified in weblogic-application.xml.

Action: Specify the correct concurrency strategy.
Level: 1

Type: ERROR

Impact: EJB

BEA-010130: An error occurred during deployment of EJB {0}. The EJB references an Exclusive application level cache {1}, but it must use a MultiVersion cache instead. EJBs with a concurrency-strategy of Database, ReadOnly, or Optimistic must use a MultiVersion cache.

Cause: An incorrect concurrency strategy is specified. The concurrency-strategy you specify for the bean must be compatible with the caching-strategy specified in weblogic-application.xml.

Action: Specify the correct concurrency strategy.
Level: 1

Type: ERROR

Impact: EJB

BEA-010132: Error during deployment of EJB {0}. The EJB has been deployed with use-select-for-update set to true. The database indicates it does not support SELECT ... FOR UPDATE.

Cause: The database indicates it does not support SELECT ... FOR UPDATE.

Action: Modify use-select-for-update to false, or use a different database that supports SELECT ... FOR UPDATE.
Level: 1

Type: ERROR

Impact: EJB

BEA-010139: Bean with primary key {0} already exists.

Cause: A bean with the indicated primary key value already exists.

Action: Do not use a non-unique value as a primary key.
Level: 1

Type: ERROR

Impact: EJB

BEA-010141: Creation of Many-To-Many relationship for primary key: {0} and {1} effected {2} rows in {3}, instead of just 1.

Cause: JoinTable contains a non-unique row for specified primary keys, indicating a Many-To-Many relationship.

Action: Check the JoinTable to remove the duplicate row.
Level: 1

Type: ERROR

Impact: EJB

BEA-010144: The setXXX method for a primary key field may only be called during ejbCreate.

Cause: The setXXX method for a primary key field may only be called during ejbCreate.

Action: Remove the setXXX method call (for a primary key field) from places other than ejbCreate.
Level: 1

Type: ERROR

Impact: EJB

BEA-010145: When a cmp-field and a cmr-field (relationship) are mapped to the same column, the setXXX method for the cmp-field may not be called.

Cause: The cmp-field is read-only.

Action: Remove the setXXX method call if cmp-filed is also used as cmr-field.
Level: 1

Type: ERROR

Impact: EJB

BEA-010146: The setXXX method for a cmr-field that is mapped to a primary key may not be called.

Cause: The cmr-field is read-only.

Action: Remove the setXXX method call if it is cmr-field mapped to a primary key.
Level: 1

Type: ERROR

Impact: EJB

BEA-010147: The setXXX method for a cmr-field may not be called during ejbCreate. The setXXX method should be called during ejbPostCreate instead.

Cause: The setXXX method should be called during ejbPostCreate instead.

Action: Move the setXXX method call for a cmr-field to ejbPostCreate.
Level: 1

Type: ERROR

Impact: EJB

BEA-010148: In EJB {0}, the primary key field {1} was not set during ejbCreate.

Cause: All primary key fields must be initialized during ejbCreate.

Action: Be sure to initialize the primary key field during ejbCreate.
Level: 1

Type: ERROR

Impact: EJB

BEA-010149: According to the EJB 2.0 specification, a value of "null" may not be assigned to a collection valued cmr-field.

Cause: This violates the EJB 2.0 specification.

Action: Avoid using a null argument for a collection valued cmr-field.
Level: 1

Type: ERROR

Impact: EJB

BEA-010152: Illegal value for concurrency-strategy. Value was {0}, but must be one of ReadOnly, Exclusive, Database, or Optimistic.

Cause: An illegal value was used for concurrency-strategy.

Action: Specify a correct value for concurrency-strategy. It must be one of ReadOnly, Exclusive, Database, or Optimistic
Level: 1

Type: ERROR

Impact: EJB

BEA-010153: Only instances of beans with a remote client view can invoke getEJBObject().

Cause: See the error message body.

Action: Remove the getEJBObject() method call from the local client.
Level: 1

Type: ERROR

Impact: EJB

BEA-010154: Only instances of beans with a local client view can invoke getEJBLocalObject().

Cause: See the error message body.

Action: Remove the getEJBLocalObject() method call from remote client.
Level: 1

Type: ERROR

Impact: EJB

BEA-010155: Only instances of beans with container-managed transaction demarcation can use getRollbackOnly().

Cause: See the error message body.

Action: Remove the getRollbackOnly() method call if container-managed transaction is not used, or enable container-managed transaction for EJB.
Level: 1

Type: ERROR

Impact: EJB

BEA-010156: Illegal attempt to call EJBContext.getRollbackOnly() from an EJB that was not participating in a transaction

Cause: See the error message body.

Action: Make sure to begin the transaction before calling the getRollbackOnly() method.
Level: 1

Type: ERROR

Impact: EJB

BEA-010157: Only instances of beans with container-managed transaction demarcation can use setRollbackOnly().

Cause: See the error message body.

Action: Remove the setRollbackOnly() method call if container-managed transaction is not used, or enable container-managed transaction for EJB.
Level: 1

Type: ERROR

Impact: EJB

BEA-010158: Illegal attempt to call EJBContext.setRollbackOnly() from an EJB that was not participating in a transaction

Cause: See the error message body.

Action: Begin the transaction before calling the setRollbackOnly() method.
Level: 1

Type: ERROR

Impact: EJB

BEA-010159: To support the use of Handles and HomeHandles, an EJB must be deployed with a JNDI name. This EJB, {0}, was deployed without specifying a JNDI name. To specify a JNDI name for this EJB, add a jndi-name element to the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for this EJB.

Cause: This EJB, {0}, was deployed without specifying a JNDI name.

Action: To specify a JNDI name for this EJB, add a jndi-name element to the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for this EJB.
Level: 1

Type: ERROR

Impact: EJB

BEA-010160: Security violation: User {0} has insufficient permission to access EJB {1}.

Cause: The specified user has insufficient permission to access the EJB.

Action: Grant sufficient permissions to the user to enable to access the EJBResource.
Level: 1

Type: ERROR

Impact: EJB

BEA-010166: Error occurred while starting transaction: {0}.

Cause: An exception occurred while starting the Message-Drive Bean transaction.

Action: Take appropriate action based on the text of the exception message.
Level: 1

Type: ERROR

Impact: EJB

BEA-010167: Message-Driven Beans are not allowed to call {0}.

Cause: The method is unavailable for MDBs.

Action: Remove the method call from the MDBs.
Level: 1

Type: ERROR

Impact: EJB

BEA-010168: Method {0} has been declared in an assembly-descriptor exclude-list and cannot be executed.

Cause: The specified method is declared in the exclude-list.

Action: Remove the method name from the exclude-list or remove the method call.
Level: 1

Type: ERROR

Impact: EJB

BEA-010173: env-entry for type java.lang.Character had length = 0.

Cause: If there is env-entry for type java.lang.Character, the parameter value should not be length = 0.

Action: Use a non-zero length value for java.lang.Character env-entry.
Level: 1

Type: ERROR

Impact: EJB

BEA-010188: Error encountered while attempting to drop Default DBMS Table {0}.

Cause: See the exception stack trace included in the logged message.

Action: Take appropriate action based on the exception stack trace in the logged message.
Level: 1

Type: ERROR

Impact: EJB

BEA-010189: Error encountered while attempting to alter Default DBMS Table: {0}.

Cause: See the exception stack trace included in the logged message.

Action: Take appropriate action based on the exception stack trace in the logged message.
Level: 1

Type: ERROR

Impact: EJB

BEA-010191: The alter table option is not supported in {0}. Use the DropAndCreate option.

Cause: The alter table option is not supported in the given database.

Action: Use the DropAndCreate option.
Level: 1

Type: ERROR

Impact: EJB

BEA-010194: Only instances of beans with bean-managed transaction demarcation can use getUserTransaction().

Cause: An illegal invocation was made to the getUserTransaction() method on a Container Managed Bean.

Action: Remove the getUserTransaction() method call from EJBs that are using container-managed transaction.
Level: 1

Type: ERROR

Impact: EJB

BEA-010195: Security violation: User {0} has insufficient permission to access method {1}.

Cause: The specified user has insufficient permission to access the specified method.

Action: Grant sufficient permissions to the user to enable access to the method.
Level: 1

Type: ERROR

Impact: EJB

BEA-010197: The entity bean {0} uses optimistic concurrency with read-verification enabled. The database indicates that exclusive row locks are not supported. Read-verification will not guarantee data integrity if the isolation level of the transaction is lower than repeatable read.

Cause: This is a mismatch problem between the concurrency strategy and the transaction isolation level.

Action: If data integrity should be guaranteed under a read-verification enabled configuration, use the appropriate transaction isolation level.
Level: 1

Type: WARNING

Impact: EJB

BEA-010198: An exception occurred while uninitializing the EJB module {0}.

Cause: Check the exception for the exact cause.

Action: Check the exception for the exact error message, and take appropriate action.
Level: 1

Type: WARNING

Impact: EJB

BEA-010199: EJB {0} with run as role {1} has no run-as-principal-name specified in its deployment descriptor or annotation. The EJB container has chosen principal-name {2} from the security-role-assignment list for role {1} to be the run as principal name.

Cause: The specified EJB with the specified run as role has no run-as-principal-name specified in its deployment descriptor or annotation.

Action: Specify run-as-principal-name explicitly if the chosen principal-name is not the appropriate one.
Level: 1

Type: WARNING

Impact: EJB

BEA-010201: The Message-Driven Bean {0} encountered an error while recovering a JMS session. This is a secondary error. The original error occurred while the Message-Driven Bean was processing a message. The recover action was taken in an attempt to recover from the original error, which will be logged separately.

Cause: The Message-Driven Bean may have generated an exception, or there may be a problem with the JMS provider.

Action: Check that the JMS provider is running and accessible through the network. In addition, check that the Message-Driven Bean onMessage method does not generate any unchecked Java exceptions such as NullPointerException or IndexOutOfBoundsException.
Level: 1

Type: ERROR

Impact: EJB

BEA-010202: Call-by-reference is not enabled for EJB {0}. The server will have better performance if it is enabled. To enable call-by-reference, set the enable-call-by-reference element to True in the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for this EJB.

Cause: Call-by-reference is not enabled.

Action: If appropriate, enable call-by-reference in the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for the EJB.
Level: 1

Type: WARNING

Impact: EJB

BEA-010204: The EJB component, {0}, will be rolled back and redeployed to update class {1}. This class is not a bean implementation class. Only bean implementation classes can be updated without redeploying the entire module, and only when enable-bean-class-redeploy is set to True in weblogic-ejb.jar.xml.

Cause: A command was issued to update the specified class.

Action: No action is necessary. This is just an informative message indicating why the EJB module is being redeployed, since this can cause disruption to clients using an EJB in this EJB module.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010205: The EJB module, {0}, will be rolled back and redeployed to update the class {1}. Bean implementation classes, such as this, can be updated without redeploying the entire EJB module. However, this can only be done if enable-bean-class-redeploy is set to True in weblogic-ejb.jar.xml or the corresponding annotation. If this is the behavior you want, set this value to True and redeploy.

Cause: A command was issued to update the specified class.

Action: No action is necessary. This is just an informative message indicating why the EJB module is being redeployed since this can cause disruption to clients using an EJB in this EJB module.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010206: The EJB module, {0}, will be rolled back and redeployed to update the class {1}. This bean implementation class could not be updated without redeploying the entire EJB module because it was changed incompatibly. Incompatible changes are any changes that cause the EJB compiler to be run. This includes modifying a public variable name or a public method signature.

Cause: A command was issued to update the specified class.

Action: No action is necessary. This is just an informative message to let the user know why the EJB module is being redeployed since this can cause disruption to clients using an EJB in this EJB module.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010207: License validation not passed for {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010208: ddl-file {0} created.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010209: ddl-file {0} could not be deleted.

Cause:

Action: Check the file permissions.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010210: Unable to write to ddl-file {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010211: Unable to alter the table, as the primary key has changed.

Cause:

Action: Use the DropAndCreate option to create the table.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010212: The EJB {0} contains at least one method without an explicit transaction attribute setting. The default transaction attribute of {1} will be used for the following methods: {2}.

Cause: The ejb-jar.xml deployment descriptor or corresponding annotation does not contain transaction attribute settings for the specified EJB methods.

Action: Assign transaction attributes for all methods of your EJB.
Level: 1

Type: WARNING

Impact: EJB

BEA-010213: Message-Driven EJB: {0}'s transaction was rolled back. The transaction details are: {1}.

Cause: The transaction was rolled back by the MDB container.

Action: This is an informational message. No action is needed.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010214: Error starting MDB {0}.

Cause: This error itself does not provide the cause of the error. The log file will contain an exception stack indicating the root cause of the failure.

Action: Inspect the log file for indications of the root cause of the failure.
Level: 1

Type: ERROR

Impact: EJB

BEA-010215: The durable subscription store with jms-client-id equal to {0} is deleted when MDB {1} is removed from the server.

Cause: The durable subscription store is deleted when the MDB is removed from the server and its durable-subscription-deletion is set to true.

Action: This is an informational message. No action is needed.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010216: The Message-Driven EJB: {0} is generating an exception when processing the messages. Delivery failed after {1} attempts. The EJB container will suspend the message delivery for {2} seconds before retry.

Cause: The Message-Driven Bean is generating an exception.

Action: Check the message delivery methods and resolve the exception condition.
Level: 1

Type: WARNING

Impact: EJB

BEA-010221: The Message-Driven EJB: {0} is unable to bind to the JCA resource adapter: {1}. The Error was: {2}

Cause: The JCA resource adapter is not deployed, or the configuration information in the MDB deployment descriptor or corresponding annotation is incorrect.

Action: Check that the JCA resource adapter is deployed and the configuration information in the MDB deployment descriptor or corresponding annotation is correct.
Level: 1

Type: WARNING

Impact: EJB

BEA-010222: The aggregate query {0} has a primitive return type but the query returned null because there were no values to which to apply the aggregate function.

Cause: There were no values to which to apply the aggregate function

Action: Handle ObjectNotFoundException correctly on the application side.
Level: 1

Type: ERROR

Impact: EJB

BEA-010223: EJB deployed Message Driven Bean {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010224: The EJB Timer: {0} has failed to successfully time out in {1} consecutive attempts. The container will delay the timeout for {2} milliseconds as configured for the timer.

Cause: This was caused by a failed ejbTimeout.

Action: It is possible that no action needs to be taken. However, it may be good to investigate why the original ejbTimeout failed.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010225: The EJB Timer: {0} has failed to successfully time out in {1} consecutive attempts. Since no retry delay was configured for this timer, the container will automatically delay the timeout for {2} seconds.

Cause: This was caused by a failed ejbTimeout.

Action: It is possible that no action needs to be taken. However, it may be good to investigate why the ejbTimeout has consecutively failed.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010226: Error executing clustered EJB timer for EJB {0} of module {1} of application {2}. While executing, the timer was unable to find a necessary internal resource required to execute. The most likely cause of this issue is that the EJB is no longer configured to use the clustered EJB timer service but timers still exist in the database.

Cause: The most likely cause of this error is that the EJB associated with this timer is no longer configured to use the clustered EJB timer service.

Action: If the EJB in question is no longer configured to use EJB timers, the timers associated with it should be removed from the database. This can be achieved by re-enabling clustered EJB timers for the EJB and then undeploying the EJB. This will cause any timers associated with the EJB to be removed from the database.
Level: 1

Type: ERROR

Impact: EJB

BEA-010227: EJB exception occurred during invocation from home or business: {0} generated exception: {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010228: Failed to update the secondary copy of a stateful session bean business: {0}.

Cause: The server was unable to update the secondary server.

Action: Check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: EJB

BEA-010230: EJB {0} : method name {1} and method name {2} are equal under case-insensitive comparison but both methods have declarative security settings. Declarative security checks are case-insensitive.

Cause: Both of the specified methods have declarative security settings.

Action: Avoid case-insensitive method name conflicts if method permissions are configured.
Level: 1

Type: WARNING

Impact: EJB

BEA-010231: The lock request from EJB {0} with primary key {1} timed-out after waiting {3} ns. The transaction or thread requesting the lock was {2}.

Cause: See error message body.

Action: See error message body.
Level: 1

Type: ERROR

Impact: EJB

BEA-010232: The version of EJB in Module "{0}" is "{1}". However, the deprecated "enable-bean-class-redeploy" feature is not supported in EJB 3.

Cause: See error message body.

Action: Use the FastSwap feature instead and remove the "enable-bean-class-redeploy" settings in the weblogic-ejb-jar.xml.
Level: 1

Type: WARNING

Impact: EJB

BEA-010233: The configuration of "MessagesMaximum" is ignored for non Weblogic JMS.

Cause: See error message body.

Action:
Level: 1

Type: WARNING

Impact: EJB

BEA-011047: In ejb-jar.xml or annotation, EJB {0} has container-transactions set when the EJB has a transaction-type of Bean. The container-transaction settings will be ignored.

Cause: The specified EJB has container-transactions set when the EJB has a transaction-type of Bean.

Action: No action is required.
Level: 1

Type: WARNING

Impact: EJB

BEA-011057: The table {0} was created by the user. The container does not drop or alter user-created tables. The container would verify the table in this case.

Cause: The table was already created by the user.

Action: Drop the table if the existing table is not correct. The container will then be able to create the table.
Level: 1

Type: WARNING

Impact: EJB

BEA-011059: The container was unable to create the DDL file.

Cause: This error does not provide the cause of the error. The log file will contain an exception stack indicating the root cause of the failure.

Action: Inspect the log file for indications of the root cause of the failure.
Level: 1

Type: WARNING

Impact: EJB

BEA-011061: Stack trace associated with message {0} follows:

Cause: An error condition was reported.

Action: Look for the associated exception in the log or your program to see what the results are. In general, this stack trace will help with debugging an existing problem.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011062: The following exception has occurred:

Cause: An error condition was reported.

Action: Review the stack trace, which will help with debugging an existing problem.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011063: Stateless session beans with bean-managed transactions must commit or roll back their transactions before completing a business method. The method {0} of EJB {1} either returned or generated an Exception without properly completing a transaction.

Cause: A transaction started by the stateless session bean method did not complete before the method completed.

Action: Check the bean code to determine what caused the transaction to not commit or roll back, and fix code. Pay special attention to any exceptions that may be generated by the method, causing commit or rollback calls to be skipped. Blocks can be used to ensure transactions are properly completed in all situations.
Level: 1

Type: ERROR

Impact: EJB

BEA-011070: In the <weblogic-rdbms-bean>, for <ejb-name> {0}, some <field-group>(s) are defined but are not used in any <weblogic-query>, <weblogic-relationship-role> or <relationship-caching> <caching-element>s. The <group-name>(s) of the unreferenced <field-group>(s) are: {1}

Cause: Some field group definitions are not referenced in any query or relationship.

Action: Remove the field groups listed in the logged message from the descriptor or include its usage appropriately.
Level: 1

Type: WARNING

Impact: EJB

BEA-011071: In the <weblogic-rdbms-bean>, for <ejb-name> {0}, some <relationship-caching>(s) are defined but are not used in any <weblogic-query>. The <caching-name>(s) of the unreferenced <relationship-caching>(s) are: {1}

Cause: There are unused relation cachings defined in the weblogic-rdbms descriptor.

Action: Remove the unused relationship cachings listed in the logged message from the descriptor or include its usage appropriately.
Level: 1

Type: WARNING

Impact: EJB

BEA-011073: An error occurred while the EJB container was attempting to obtain information about the table {0} from the database. This information is necessary to validate the mapping between the fields of the EJB {1} and the table. The exception is: {2}

Cause: The most likely cause is an error communicating with the database. The error message should include the specific error message.

Action: The action depends on the specific error that occurred. Actions may range from retrying the failed deployment to seeking help from your database administrator. Also, ensure that you are using a supported database.
Level: 1

Type: ERROR

Impact: EJB

BEA-011076: Unable to deploy the EJB {0} because the database table {1} is not accessible. Ensure that this table exists and is accessible.

Cause: A required database table was not accessible.

Action: Ensure that the database table exists and is accessible.
Level: 1

Type: ERROR

Impact: EJB

BEA-011077: The EJB deployment contains settings for automatically creating or altering database tables. However, the server is in production mode, so no database tables will be created or altered.

Cause: The server is in production mode so the create-default-dbms-tables settings are being ignored.

Action: No action is required. To suppress the warning, remove the create-default-dbms-tables setting from your EJB deployment.
Level: 1

Type: WARNING

Impact: EJB

BEA-011078: An exception occurred while starting the freepool idle timeout timer for ejb: {0}, {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011079: An exception occurred while stopping the freepool idle timeout timer for ejb: {0}, {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011080: An exception occurred while starting the Cache idle timeout timer for cache: {0}, {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011081: An exception occurred while stopping the Cache idle timeout timer for cache: {0}, {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011082: Error: The message-destination-link {0} for the Message-Driven Bean {1} in the application module {2} could not be resolved. The target message-destination for the Message-Driven Bean could not be found. Ensure that the link is correct.

Cause: The target of the message-destination-link could not be found in the application.

Action: Fix the message-destination-link to point to a valid message-destination.
Level: 1

Type: ERROR

Impact: EJB

BEA-011083: The EJB specification prohibits stateful session beans from using the TimerService.

Cause: An illegal call was made to the getTimerService() method on the stateful session beans SessionContext.

Action: Correct the stateful session bean code so that it does not call the getTimerService() method from the bean class.
Level: 1

Type: ERROR

Impact: EJB

BEA-011084: This EJB class does not support EJB timers and therefore is prohibited from using the TimerService. To use EJB timers, the bean class must implement javax.ejb.TimedObject or have a method that is annotated with @Timeout.

Cause: An illegal call to the getTimerService() method on the EJBContext.

Action: Correct the EJB class so it either implements the javax.ejb.TimedObject interface or ensure that it does not call the getTimerService() method on the EJBContext.
Level: 1

Type: ERROR

Impact: EJB

BEA-011085: This timer has either expired or been canceled and therefore cannot be invoked.

Cause: An illegal call to a timer object after the timer had expired or was canceled.

Action: Ensure your bean class does not invoke expired or canceled timers.
Level: 1

Type: ERROR

Impact: EJB

BEA-011086: The timer associated with this TimerHandle has either expired or been canceled.

Cause: The timer associated with the TimerHandle has expired or been canceled.

Action: No action is required.
Level: 1

Type: ERROR

Impact: EJB

BEA-011087: This TimerHandle is being invoked outside of the context of the application in which it was created. Since timers are local objects, they can only be called from within the same application in which they were created.

Cause: This TimerHandle is being invoked outside of the context of the application in which it was created.

Action: Ensure that your application does not pass any TimerHandle references outside of the scope of the application.
Level: 1

Type: ERROR

Impact: EJB

BEA-011088: The following error occurred while invoking the ejbTimeout(javax.ejb.Timer) method of EJB {0}.

Cause: This could be caused by erroneous code in the ejbTimeout method or by the failure of a dependent resource.

Action: All exceptions that occur while invoking or attempting to invoke the ejbTimeout method should be investigated and resolved. If the ejbTimeout method is non-transactional, that is, has a transaction attribute of NotSupported, or if the bean uses bean-managed transactions, the ejbTimeout method may not be retried, leading to missed timeout notifications.
Level: 1

Type: ERROR

Impact: EJB

BEA-011089: The following error occurred while attempting to remove an EJB timer from the persistent store for EJB {0}.

Cause: This is an unexpected error so the cause is unknown. The accompanying exception and stack trace should provide information as to the cause of the error.

Action: This cause of this error should be investigated and resolved promptly.
Level: 1

Type: ERROR

Impact: EJB

BEA-011090: The following error occurred while preparing to invoke the ejbTimeout(javax.ejb.Timer) method of EJB {0}.

Cause: This is an unexpected error so the cause is unknown. The accompanying exception and stack trace should provide information as to the cause of the error.

Action: All exceptions that occur while attempting to invoke the ejbTimeout method should be investigated and resolved.
Level: 1

Type: ERROR

Impact: EJB

BEA-011091: The table {0} cannot be dropped or created since it uses a trigger to update the optimistic column of the EJB. The container will only verify the existence of the table.

Cause: The table uses a trigger to update the optimistic column of the EJB.

Action: To suppress this warning, set the create-default-dbms-tables value in the RDBMS deployment descriptor to Disabled.
Level: 1

Type: WARNING

Impact: EJB

BEA-011092: In production mode, the DropAndCreate, DropAndCreateAlways, and AlterOrCreate options are ignored. The container will only attempt to verify the existence and increment value of the sequence {0}.

Cause: Options that apply only to development mode are ignored in production mode.

Action: Do not use these values for Automatic Oracle SEQUENCE Generation in production mode.
Level: 1

Type: WARNING

Impact: EJB

BEA-011093: The SEQUENCE named {0} with INCREMENT {1} was not found in the database. This SEQUENCE was specified in the CMP deployment descriptor to be used for automatic primary key generation.

Cause: The SEQUENCE was not found.

Action: Examine the <automatic-key-generation> tag in the CMP deployment descriptor. In particular, re-examine the <generator-name> and verify that this is the correct name of the SEQUENCE. Also, re-examine the <key-cache-size> and verify that this is the correct size of the SEQUENCE INCREMENT value.
Level: 1

Type: ERROR

Impact: EJB

BEA-011094: The SEQUENCE named {0} does not have INCREMENT value of {1} in the database as specified in the CMP deployment descriptor. Either modify the key-cache-value for this SEQUENCE in the deployment descriptor or update the SEQUENCE in the database.

Cause: The SEQUENCE named {0} does not have an INCREMENT value of {1} in the database as specified in the CMP deployment descriptor.

Action: In the <automatic-key-generation> tag of the CMP deployment descriptor, re-examine the <key-cache-size> and verify that this is the correct size of the SEQUENCE INCREMENT value.
Level: 1

Type: ERROR

Impact: EJB

BEA-011095: During EJB deployment, error(s) were encountered while attempting to CREATE the SEQUENCE named {0} with INCREMENT value {1}. {2}

Cause: During EJB deployment, error(s) were encountered while attempting to CREATE the SEQUENCE named {0} with INCREMENT value {1}.

Action: The message contains the cause of the error. See the message body and resolve the reported error.
Level: 1

Type: ERROR

Impact: EJB

BEA-011096: During EJB deployment, error(s) were encountered while setting up The SEQUENCE named {0} with INCREMENT value {1}. {2}

Cause: During EJB deployment, error(s) were encountered while setting up The SEQUENCE named {0} with INCREMENT value {1}.

Action: The message contains the cause of the error. See the message body and resolve the reported error.
Level: 1

Type: ERROR

Impact: EJB

BEA-011097: During EJB deployment, error(s) were encountered while attempting to ALTER the SEQUENCE named {0} with INCREMENT value {1}. {2}

Cause: During EJB deployment, error(s) were encountered while attempting to ALTER the SEQUENCE named {0} with INCREMENT value {1}.

Action: The message contains the cause of the error. See message body and resolve the reported error.
Level: 1

Type: ERROR

Impact: EJB

BEA-011098: No generated primary key was returned from the database insert statement as expected. Verify that the primary key database column for this EJB is an IDENTITY column as declared in the CMP deployment descriptor for this EJB.

Cause: This is most likely caused by a database configuration error. It may also be caused by a JDBC driver that does not support the getGeneratedKeys() method on java.sql.Statement.

Action: Verify that the primary key column in the database is marked as an IDENTITY column (or a functional equivalent is setup for the column such as a database trigger to insert a value into the primary key column).
Level: 1

Type: ERROR

Impact: EJB

BEA-011099: Multiple generated keys were returned from the database insert statement. The EJB container is unable to determine which generated key corresponds to the primary key column. To use the IDENTITY primary key generator, you must only have a single automatically generated database column per EJB.

Cause: This is most likely caused by a database configuration error. Each EJB may only have a single automatically generated database column.

Action: Verify that the database table corresponding to the EJB only has a single generated column.
Level: 1

Type: ERROR

Impact: EJB

BEA-011109: Failed to register JACC policy context handlers for the EJB container.

Cause: An unexpected error condition occurred while registering JACC context policy handlers.

Action: See the error message stack trace for details on how to resolve this issue.
Level: 1

Type: ERROR

Impact: EJB

BEA-011110: The SEQUENCE named {0} has key-cache-size set to {1}, which is less than the INCREMENT_BY value for the sequence in the database. This may generate missing keys.

Cause: The SEQUENCE named {0} has key-cache-size set to {1}, which is less than the INCREMENT_BY value for the sequence in the database.

Action: In the <automatic-key-generation> tag, re-examine the <key-cache-size> and verify that it is set correctly.
Level: 1

Type: WARNING

Impact: EJB

BEA-011111: The SEQUENCE named {0} has key-cache-size set to {1} which is greater than the INCREMENT_BY value for the sequence in the database. This is not allowed as it may generate duplicate keys.

Cause: The key-cache-set size for the SEQUENCE is not valid.

Action: in the <automatic-key-generation> tag, re-examine the <key-cache-size> and set it to a value less than or equal to the INCREMENT_BY value for the sequence in the database.
Level: 1

Type: ERROR

Impact: EJB

BEA-011120: The CMP EJB {0} has enable-batch-operations set to true. The update queries, however, are not suitable for batching. Batched operations are turned off for this batch and the queries will be executed with multiple update statements.

Cause: Batching is turned off for update queries.

Action: No action is required.
Level: 1

Type: WARNING

Impact: EJB

BEA-011121: Error in Message-Driven Bean EJB {0}. The plugin-class {1} could not be found in the server classpath.

Cause: The plugin-class could not be found in the server classpath.

Action: Add the plugin-class in the server classpath.
Level: 1

Type: ERROR

Impact: EJB

BEA-011122: Error in Message-Driven Bean EJB {0}. The plugin-class {1} could not be instantiated.

Cause: The plugin-class could not be instantiated.

Action: Add the plugin-class in the server classpath.
Level: 1

Type: ERROR

Impact: EJB

BEA-011123: Error in Message-Driven Bean EJB {0}. The plugin-class {1} could not be found in the server classpath.

Cause: The plugin-class could not be accessed.

Action: Add the plugin-class in the server classpath.
Level: 1

Type: ERROR

Impact: EJB

BEA-011124: Error in Message-Driven Bean EJB {0}. The plugin-class {1} does not implement weblogic.ejb.spi.SecurityPlugin.

Cause: The plugin-class does not implement weblogic.ejb.spi.SecurityPlugin.

Action: Make the plugin-class implement weblogic.ejb.spi.SecurityPlugin.
Level: 1

Type: ERROR

Impact: EJB

BEA-011125: An unexpected error was encountered while attempting to remove any EJB timers from the persistent store for the EJB {0}.

Cause: An unexpected error occurred while attempting to remove EJB timers from the persistent store.

Action: See the particular error message for details about the error. If your application is failing to deploy because of this error, it may be necessary to manually remove the timers from the store.
Level: 1

Type: ERROR

Impact: EJB

BEA-011126: The same exception has consecutively caused the expiration to fail for EJB timer {0}. Consecutive errors of this type will no longer be logged for the current timer expiration.

Cause: The same exception has consecutively caused expiration of an EJB timer to fail.

Action: Investigate what caused the ejbTimeout method to fail. The original exception will be logged in a previous error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011127: Error deserializing one or more EJB timers from the persistent store for the EJB deployment {0}. An incompatible change to the class of a Serializable object associated with the timer may be the cause. If this is the case, you can either undeploy your application entirely to remove the EJB timers from the persistent store or revert the incompatible changes to the Serializable class so the EJB timer can be deserialized. The error was: {1}

Cause: A common cause of this error is an incompatible serializable class change in your application.

Action: If the error is due to an incompatible serializable class change in your application, there are two options for dealing with the serialization errors. The first option is to completely undeploy the EJB. which will cause all of the EJB timers in the persistent store to be permanently removed. The second option is to revert changes to the serializable class that is associated with the EJB timer and redeploy the application. This allows the EJB timer to be deserialized.
Level: 1

Type: ERROR

Impact: EJB

BEA-011128: Error creating an instance of the EJB {0}: {1}

Cause: See the reported error message for the cause. This error may be due to a configuration issue or a bug in the EJB container.

Action: See the specific error message for details and take appropriate action.
Level: 1

Type: ERROR

Impact: EJB

BEA-011129: Error deploying EJB {0} to server {1}. This EJB is configured to use the clustered EJB Timer implementation but this server is not part of a cluster.

Cause: It is illegal to deploy an EJB that uses clustered EJB timers to a server that is not part of a cluster.

Action: You must either set the timer-implementation attribute of your weblogic-ejb-jar.xml descriptor to Local or ensure that any servers to which you deploy the EJB are part of a cluster.
Level: 1

Type: ERROR

Impact: EJB

BEA-011130: Error deploying EJB {0}. This EJB is configured to use the clustered EJB timer implementation but the data-source-for-job-scheduler cluster attribute is not configured.

Cause: While deploying this EJB, the EJB container determined the data-source-for-job-scheduler cluster attribute has not been set.

Action: You must either set the timer-implementation attribute of your weblogic-ejb-jar.xml descriptor to Local or configure the data-source-for-job-scheduler attribute for your cluster.
Level: 1

Type: ERROR

Impact: EJB

BEA-011132: Error deploying EJB {0}. While binding a business interface to the JNDI name {1}, the following error occurred: {2}

Cause: See the specific error for details.

Action: The action to take depends on the specific error that occurred. If the error was a JNDI naming conflict, you may need to choose a different JNDI name for the interface.
Level: 1

Type: ERROR

Impact: EJB

BEA-011135: The EJB {0} is a singleton session bean. EJB 2.1 client views are not supported for singleton session beans.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011136: wasCancelCalled() should only be invoked from within an asynchronous business method invocation with return type Future.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011137: A singleton session bean with bean-managed transactions must commit or roll back a transaction before the business method completes.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011138: Singleton session beans with bean-managed transactions must commit or rollback their transactions before completing a business method. The method {0} of EJB {1} either returned or generated an exception without properly completing a transaction.

Cause: A transaction started by the singleton session bean method did not complete before the method completed.

Action: Check the bean code to determine what caused the transaction to not commit or roll back and fix the code. Pay special attention to any exceptions that may be generated by the method, causing commit or rollback calls to be skipped. Blocks can be used to ensure transactions are properly completed in all situations.
Level: 1

Type: ERROR

Impact: EJB

BEA-011139: The following exception occurred when processing the asynchronous invocation : {0}.

Cause: There error was encountered during the asynchronous invocation.

Action: See the exception stack trace for details.
Level: 1

Type: ERROR

Impact: EJB

BEA-011140: The argument {0} is not a valid local client view for the EJB {1}.

Cause: The argument is not a valid local client view for the EJB.

Action: Review the EJB configuration and calling code to determine the discrepancy.
Level: 1

Type: ERROR

Impact: EJB

BEA-011141: This EJB has already been removed.

Cause: The EJB has already been removed.

Action: Avoid the call for removed objects.
Level: 1

Type: ERROR

Impact: EJB

BEA-011142: Error creating EJB reference: {0}

Cause: An exception occurred while creating an EJB reference.

Action: The reported exception contains the root cause of the issue. Review the exception to identify the exact problem.
Level: 1

Type: ERROR

Impact: EJB

BEA-011143: Error removing stateful session bean: {0}

Cause: An unexpected error occured while trying to remove a stateful session bean.

Action: The reported exception has the root cause of the issue. Review the exception to identify the actual problem.
Level: 1

Type: ERROR

Impact: EJB

BEA-011144: Singleton EJB {0} failed to initialize.

Cause: A singleton EJB {0} failed to initialize.

Action: The message body has the root cause of the issue. Review it to identify the essential problem.
Level: 1

Type: ERROR

Impact: EJB

BEA-011145: Illegal call to a Write method from a Thread holding Read lock.

Cause: An illegal call to a Write method was made

Action: Remove or rewrite the call.
Level: 1

Type: ERROR

Impact: EJB

BEA-011146: Timed out while trying to aquire lock on Singleton {0} to invoke method {1}.

Cause: A timeout occurred while trying to aquire a lock.

Action: Check Singleton concurrency. A timeout has been reached.
Level: 1

Type: ERROR

Impact: EJB

BEA-011147: Singleton {0} is in use by another thread.

Cause: While this Singleton is being invoked, it cannot be called from other threads.

Action: Check Singleton concurrency.
Level: 1

Type: ERROR

Impact: EJB

BEA-011148: Singleton {0} not initialized as Singleton {1} from the DependsOn transitive, closure failed initialization.

Cause: A singleton was not initialized as a Singleton from the DependsOn transitive, closure failed initialization.

Action: Check the server log for the cause of the dependent Singleton initialization error and resolve it.
Level: 1

Type: ERROR

Impact: EJB

BEA-011149: The EJB {0} contains an illegal value for the activation config property MessagesMaximum. The specified value is {1} but the legal values are -1, and 1 through 2^63-1.

Cause: See the error message body.

Action: Correct the activation config property.
Level: 1

Type: ERROR

Impact: EJB

BEA-011223: Cannot invoke stateful callback on {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011224: Unable to bind the interface {0} to {1}. Another EJB has already bound an interface to that name.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011225: Unable to bind the interface {0} to {1}. This EJB has declared another interface already bound to that name.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011226: Error during {0}. Could not get connection: {1} {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011227: Error during finder {0}. Exception while preparing query: {1} {2} {3}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011232: Error during finder {0}. Exception while setting parameters for query {1} {2} {3}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011233: Error during finder {0}. Exception while executing query {1} {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011234: Could not find an EJB with a field that is mapped to table {0} and column {1}. The SQL query is {2}. Try using an SqlShape annotation to describe the query results or check that the SqlShape annotation in use is correct.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011235: Error in {0}, could not map relationship {1} role {2} to an EJB populated by the query {3}. EJBs populated by this query are: {4}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011236: Error executing finder {0}: SqlShape {1} contains {2} columns, but the result set returned by JDBC contains {3} columns. The number of columns in the SqlShape and the JDBC result set must match.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011237: A stored procedure or function is used by {0}, but no SqlShape is specified.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011238: Error in {0}. SQL query {1} does not select column values for all primary key fields of bean {2}. No columns were selected for the following fields: {3}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011239: Query-caching is not supported for read-write beans.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011240: Error obtaining nativeQuery: {0}, {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011241: An attempt was made to do an executeQuery on query {0}, using a non-WebLogic EntityManager.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011242: Internal Error: Extended Persistence Context has been closed!

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011243: attempt at illegal state transaction from {0} to {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011244: An illegal call was made to the EJBContext method. getMessageContext can only be called from SLSBs with web-service endpoint interfaces.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011245: The EJB {0} is not an EJB3.0 bean.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011246: The EJB {0} does not declare a {1} home interface.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011247: The EJB {0} does not implement the business interface {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011248: The bean has not been invoked through a business interface.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011249: It is illegal to invoke UserTransaction methods in ejbCreate or the PostConstruct method of a Message-Driven Bean.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011250: It is illegal to invoke UserTransaction methods in ejbRemove or the PreDestroy method of a Message-Driven Bean.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011251: It is illegal to invoke UserTransaction methods in setSessionContext or a dependency injection of a Message-Driven Bean.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011252: It is illegal to invoke UserTransaction methods in setSessionContext or a dependency injection of a stateful session bean.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011253: It is illegal to invoke UserTransaction methods in ejbCreate or the PostConstruct method of a stateless session bean.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011254: It is illegal to invoke UserTransaction methods in ejbRemove or the PreDestroy method of a stateless session bean.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011255: It is illegal to invoke UserTransaction methods in setSessionContext or a dependency injection of a stateless session bean.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011256: Single expiration timers cannot be cancelled from within ejbTimeout.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011257: It is illegal to invoke Timer methods in ejbRemove or a PreDestroy method from asession bean or Message-Driven Bean.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011258: It is illegal to invoke Timer methods in ejbActivate or a PostActivate method.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011259: It is illegal to invoke Timer methods in ejbPassivate or a PrePassivate method.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011260: It is illegal to invoke Timer methods during a dependency injection.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011261: Invocation timed out. Timer is busy.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011262: Error cancelling timer

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011263: EjbJarBean is not set yet.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011264: Method {0} is marked TX_NEVER, but was called within a transaction.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011265: Unexpected exception in afterDelivery(): {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011266: An attempt was made to execute getDatabaseProductName using a non-WebLogic EntityManager.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011267: Error calling getDatabaseProductName: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011268: An attempt was made to execute nativeQuery on query {0}, using a non-WebLogic EntityManager.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011269: Error obtaining nativeQuery: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011270: Error preparing query: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011276: An illegal attempt was made to make a re-entrant call to a stateful session bean: {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011277: An illegal attempt was made to make a re-entrant call to a stateful session bean from home: {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011278: The following dependency that was declared by {0} is not a Singleton Session Bean: {1}.

Cause: A dependency that was specified by a Singleton Session Bean must also be a Singleton Session Bean.

Action: Remove the illegal dependency from the dependency list or replace it with a Singleton Session Bean.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011279: The following exception occured in PreDestroy processing for singleton session bean {0}: {1}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-012030: Illegal DOCTYPE for a WebLogic RDBMS CMP EJB11 descriptor file. DOCTYPE {0} not permitted. Only DOCTYPE {1} permitted here.

Cause: An illegal DOCTYPE was used.

Action: Make sure to update appropriate DOCTYPE to the descriptor file.
Level: 1

Type: ERROR

Impact: EJB

BEA-012031: The EJB {0} has a finder {1} for which the sql-select-distinct attribute has been specified. This attribute has been deprecated and will not be supported in future releases.

Cause: The deprecated sql-select-distinct attribute was used.

Action: Use the EJB-QL DISTINCT clause instead. The container will automatically filter duplicates if necessary.
Level: 1

Type: WARNING

Impact: EJB

BEA-012032: For EJB {0}, a weblogic-query element in the CMP deployment descriptor has no matching query element in the ejb-jar.xml descriptor. The settings specified in the weblogic-query element will be ignored. The EJB method referred to by the weblogic-query element is {1}.

Cause: The weblogic-query element references a wrong or non-existent query method for this entity EJB.

Action: Remove the weblogic-query element or update it so that it references the correct query method.
Level: 1

Type: WARNING

Impact: EJB

BEA-012033: Compiling generated EJB classes produced the following Java compiler output: {0}

Cause: While compiling EJB generated classes, the Java compiler produced output.

Action: Typically, there is no action to take. The Java compiler output is printed for informational purposes. If the Java compiler is unable to successfully compile the generated classes, this is likely a bug in the EJB subsystem and you should probably contact support.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-012035: The Remote interface method: {0} in EJB {1} contains a parameter of type {2} which is not serializable. Though the EJB {1} has call-by-reference set to false, this parameter is not serializable and hence will be passed by reference. A parameter can be passed using call-by-value only if the parameter type is serializable.

Cause: The EJB has call-by-reference set to false. A parameter can be passed using call-by-value only if the parameter type is serializable. As this parameter is not serializable, the parameter will be passed by reference.

Action: The parameter should implement the java.io.Serializable interface for it to be passed by value.
Level: 1

Type: WARNING

Impact: EJB

BEA-012036: Compiling generated EJB classes produced the following Java compiler error message: {0}

Cause: While compiling EJB generated classes, the Java compiler produced output.

Action: If the Java compiler is unable to successfully compile the generated classes, this is likely a bug in the EJB subsystem and you should probably contact My Oracle Support.
Level: 1

Type: ERROR

Impact: EJB

BEA-012037: In weblogic-ejb-jar.xml or annotation, a singleton-session-descriptor element was found for EJB {0}. This EJB was not declared as a singleton session bean in ejb-jar.xml or annotation.

Cause: There is an incompatible configuration between weblogic-ejb-jar.xml and ejb-jar.xml.

Action: Modify weblogic-ejb-jar.xml or ejb-jar.xml to keep configuration consistency whether singleton or non-singleton.
Level: 1

Type: ERROR

Impact: EJB

BEA-014000: Problem, encountered illegal value for transaction-isolation {0}.

Cause: See the error message body.

Action: Specify one of the following legal values: TransactionSerializable, TransactionReadCommitted, TransactionReadCommittedForUpdate, TransactionReadCommittedForUpdateNoWait, TransactionReadUncommitted, or TransactionRepeatableRead.
Level: 1

Type: ERROR

Impact: EJB

BEA-014001: RDBMS descriptor {0} contains transaction-isolation settings. These settings may conflict with isolation-level settings in your weblogic-ejb-jar.xml descriptor and will be lost if you edit this descriptor in the console.

Cause: The specified RDBMS descriptor contains transaction-isolation settings.

Action: Move the isolation-level settings to the weblogic-ejb-jar.xml descriptor.
Level: 1

Type: ERROR

Impact: EJB

BEA-014003: EJB {0} uses optimistic concurrency and contains a finder or select method, {1}, for which include-updates is true. This combination of features does not work properly with database {2}.

Cause: Optimistic concurrency is implemented by reading data in a local transaction to avoid holding database locks, unless Oracle is used as the database. Oracle read consistency does not hold read locks, so in this case reads are performed using the current JTA transaction. When reads are performed in a local transaction updates that have been flushed prior to commit of the transaction are not visible.

Action: Set include-updates for the query to false to avoid this warning message, or if you are using Oracle as your database, set the database-type to Oracle in weblogic-cmp-jar.xml.
Level: 1

Type: WARNING

Impact: EJB

BEA-014004: In EJB {0}, <generator-type> is set to {1}. It is incompatible with Batch Operations due to database limitations. Both order-database-operations and enable-batch-operations are turned off by EJB container.

Cause: These are database limitations.

Action: Turn off automatic-key-generation in order to use batch operations.
Level: 1

Type: WARNING

Impact: EJB

BEA-014005: The configured dispatch policy {1} for Message-Driven Bean (MDB) {0} will be ignored: the MDB is not running in a WebLogic thread.

Cause: The queue MDB is driven asynchronously by a non-WebLogic JMS implementation and runs in a non-WebLogic thread mechanism, so the MDBs application thread pool is not configurable.

Action: To disable this warning, remove the dispatch-policy setting from the MDBs WebLogic descriptor file.
Level: 1

Type: WARNING

Impact: EJB

BEA-014006: The Message-Driven Bean (MDB) named {0} has a dispatch policy {1} that refers to an unknown execute queue thread pool. The default execute thread pool will be used instead.

Cause: The specified MDB named has a dispatch policy that refers to an unknown execute queue thread pool.

Action: Create an execute thread queue pool for the server named {1}, or modify the dispatch-policy attribute in the MDBs WebLogic descriptor file to the name of an already existing execute queue thread pool.
Level: 1

Type: WARNING

Impact: EJB

BEA-014007: The bean named {0} contains BLOB or CLOB fields or both, and uses Optimistic Concurrency but no version or timestamp column has been specified. This may result in corruption of BLOB and CLOB data.

Cause: The specified bean contains BLOB or CLOB fields or both, and uses Optimistic Concurrency but no version or timestamp column has been specified.

Action: Specify "version" or "timestamp" in the <table-map> <verify-columns> element and specify the name of the <version> or <timestamp> column in the <optimistic-column> element.
Level: 1

Type: WARNING

Impact: EJB

BEA-014008: In EJB {0}, {1} references an SqlShape element {2} that is not defined. The list of SqlShape elements that are defined for this EJB is: {3}.

Cause: An undefined SqlShape element was referenced.

Action: Use an existing SqlShape or create the SqlShape that you wish to use.
Level: 1

Type: WARNING

Impact: EJB

BEA-014009: The Message-Driven Bean {0} of application {1} will now be suspended, as it listens to global JMS destination {2} and a new application version {3} is being redeployed.

Cause:

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-014010: The Message-Driven Bean {0} of application {1} will now be suspended, as it listens to global JMS topic {2} and a new application version {3} is being redeployed. Note also that the current Message-Driven Bean is not a durable subscriber to the topic, and messages published by the topic after the currently active version of the Message-Driven Bean is suspended may not be received by the new application version.

Cause: The specified Message-Driven Bean listens to the specified global JMS topic and a new application version is being redeployed.

Action: To ensure that the new application version will receive all messages published while the Message-Driven Bean was suspended, set the activation config property "subscriptionDurability" to "durable" in the deployment descriptor or annotation.
Level: 1

Type: WARNING

Impact: EJB

BEA-014011: EJB {0} uses optimistic-concurrency and has the use-select-for-update element in the RDBMS deployment descriptor set to true. This combination of features is incompatible. The use-select-for-update is turned off by the EJB container in this case.

Cause: Optimistic concurrency is implemented by reading data in a local transaction to avoid holding database locks. The element use-select-for-update in the RDBMS deployment descriptor when set to true, will cause SELECT ... FOR UPDATE to be used whenever the bean is loaded from the database, thus locking the table. This conflicts with the Optimistic Concurrency strategy.

Action: Set use-select-for-update element in the RDBMS deployment descriptor to false to avoid this warning message.
Level: 1

Type: WARNING

Impact: EJB

BEA-014012: EJB {0} uses optimistic-concurrency and disables cluster invalidation, but does not have verify-rows set to Read. This combination will prevent detection of stale data if the bean is never modified in a transaction.

Cause: Optimistic concurrency beans verify consistency of data only if the bean has been modified, unless verify-rows is set to Read. If some other member of a cluster modifies a bean, other members will not be notified of this modification and will continue to store stale data unless the other members also attempt to modify the bean.

Action: Set either of the elements verify-rows to Read or cluster-invalidation-disabled to false in the RDBMS deployment descriptor to avoid this warning message.
Level: 1

Type: WARNING

Impact: EJB

BEA-014013: EJB {0} does not have a concurrency-strategy of either optimistic or readOnly and disables cluster invalidation. Cluster invalidation is relevant only for these concurrency strategies.

Cause: When an EJB is using either optimistic or readOnly concurrency-strategy and is deployed to a cluster, the container invalidates such beans on modification to avoid throwing OptimisticConcurrencyExceptions. This invalidation can be turned off by setting the cluster-invalidation-disabled to true in the RDBMS deployment descriptor.

Action: Set cluster-invalidation-disabled to false in the RDBMS deployment descriptor to avoid this warning message.
Level: 1

Type: WARNING

Impact: EJB

BEA-014014: The Message-Driven Bean (MDB) named {0} has a dispatch policy {1} that refers to an unknown work manager. The default work manager will be used instead.

Cause: The specified MDB has a dispatch policy that refers to an unknown work manager.

Action: Create a work manager for the server named {1}, or modify the dispatch-policy attribute in the MDBs WebLogic descriptor file to the name of an already existing work manager.
Level: 1

Type: WARNING

Impact: EJB

BEA-014016: EJB {0} uses readonly-concurrency and has the use-select-for-update element in the RDBMS deployment descriptor set to true. As the bean is read-only, select-for-update is unnecessary.

Cause: Read-only beans cannot be updated. Therefore, use-select-for-update is unnecessary.

Action: Set use-select-for-update element in the RDBMS deployment descriptor to false to avoid this warning message.
Level: 1

Type: WARNING

Impact: EJB

BEA-014017: EJB {0} uses exclusive-concurrency and has the use-select-for-update element in the RDBMS deployment descriptor set to true. As the bean is locked at the server level during a transaction, select-for-update on the database is unnecessary.

Cause: Exclusive concurrency is implemented by locking the bean at the server level when the bean participates in a transaction. Setting the element use-select-for-update in the RDBMS deployment descriptor to true causes SELECT ... FOR UPDATE to be used whenever the bean is loaded from the database, thus locking the row in the database too. This may be unnecessary, as the bean is locked by the container.

Action: Set use-select-for-update element in the RDBMS deployment descriptor to false to avoid this warning message.
Level: 1

Type: WARNING

Impact: EJB

BEA-014018: EJB {0} uses a verify-columns element in the RDBMS deployment descriptor. This element is applicable only for optimistic concurrency beans. Since this bean does not use optimistic concurrency, this element will be ignored.

Cause: verify-columns is applicable only for optimistic concurrency beans. As the bean does not use optimistic concurrency, this element will be ignored.

Action: Remove verify-columns element in the RDBMS deployment descriptor to avoid this warning message.
Level: 1

Type: WARNING

Impact: EJB

BEA-014019: EJB {0} uses a verify-rows element in the RDBMS deployment descriptor. This element is applicable only for optimistic concurrency beans. Since this bean does not use optimistic concurrency, this element will be ignored.

Cause: verify-rows is applicable only for optimistic concurrency beans. As the bean does not use optimistic concurrency, this element will be ignored.

Action: Remove the verify-rows element in the RDBMS deployment descriptor to avoid this warning message.
Level: 1

Type: WARNING

Impact: EJB

BEA-014020: EJB {0} uses an optimistic-column element in the RDBMS deployment descriptor. This element is applicable only for optimistic concurrency beans. Since this bean does not use optimistic concurrency, this element will be ignored.

Cause: optimistic-column element is applicable only for optimistic concurrency beans. If the bean does not use optimistic concurrency, this element will be ignored.

Action: Remove the optimistic-column element in the RDBMS deployment descriptor to avoid this warning message.
Level: 1

Type: WARNING

Impact: EJB

BEA-014021: The EJB {0} has been successfully deployed. The following remote interfaces have been bound into JNDI with the specified JNDI names:

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-014022: {0} is bound with JNDI name {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015000: The following exception occured while processing annotations: {0}.

Cause: See the exception to determine the cause.

Action: See the exception to determine the action to take.
Level: 1

Type: ERROR

Impact: EJB

BEA-015001: Unable to link class {0} in Jar {1} : {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015002: Unable to load class {0} in Jar {1} : {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015003: Unable to create virual Jar {0} : {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015004: The super class {0} of session bean class {1} is also a session bean class.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015005: The session type is not set in the deployment descriptor or annotation for session bean {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015007: No ejbCreate method was found for init method {0} in bean {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015008: No matching create method for @Init method {0} in bean {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015009: Could not load interceptor class {0}: {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015010: In bean {0}, there are multiple method permission annotations for method {1}, which is illegal.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015011: There are multiple method permission annotations for class {0}, which is illegal.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015012: Unable to load interface class {0}: {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015013: Bean class {0} does not implement interface method {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015014: ServiceEndpoint class {0} was specified but cannot be found.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015015: The super class {0} of Message-Driven Bean class {1} is also a Message-Driven Bean class.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015016: Message-Drive Bean {0} does not implement the message listener interface, has no messaging-type specified in the deployment descriptor, or has no messageListenerInterface specified by using @MessageDriven annotation.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015017: In bean class {0}, the @EJB annotation is at class level, so the beanInterface must be explicitly specified.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015018: In interceptor class {0}, the @EJB annotation is at class level, so the beanInterface must be explicitly specified.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015022: {0} is not valid in this context. Bean class: {1}.

Cause: {0} is not valid in this context. Bean class: {1}.

Action: Remove {0} from the invalid location.
Level: 1

Type: ERROR

Impact: EJB

BEA-015023: {0} is not valid in this context. Bean method: {1}.{2}.

Cause: {0} is not valid in this context. Bean method: {1}.{2}.

Action: Remove {0} annotation from invalid location.
Level: 1

Type: ERROR

Impact: EJB

BEA-015024: Could not specify @JNDIName on local business interface {0} of Bean {1}.

Cause: The @JNDIName could not be specified on the local business interface {0} of Bean {1}.

Action: Remove the annotation from the local business interface.
Level: 1

Type: ERROR

Impact: EJB

BEA-015025: Unable to load a class that is specified in your ejb-jar.xml: {0}.

Cause: A class that is specified in your ejb-jar.xml cannot be loaded.

Action: Check ejb-jar.xml in the EJB JAR file.
Level: 1

Type: ERROR

Impact: EJB

BEA-015026: Reference name {0} of @{1} annotation on class {2} is not unique.

Cause: Reference name {0} of @{1} annotation on class {2} is not unique.

Action: Change the reference name {0} of @{1} annotation on class {2}.
Level: 1

Type: ERROR

Impact: EJB

BEA-015027: The Message-Driven EJB is transactional, but the JMS connection factory referenced by the JNDI name {0} is not a JMS XA connection factory.

Cause: The Message-Driven EJB is transactional, but the JMS connection factory referenced by the JNDI name {0} is not a JMS XA connection factory.

Action: Make the Message-Driven EJB non-transactional, or use a different connection factory that supports XA.
Level: 1

Type: ERROR

Impact: EJB

BEA-015028: The EJB {0} contains an illegal value for the activation config property DistributedDestinationConnection. The specified value is {1} but the legal values are EveryMember and LocalOnly.

Cause: See the error message body.

Action: Correct the activation config property.
Level: 1

Type: ERROR

Impact: EJB

BEA-015029: The EJB {0} contains an illegal value for the activation config property TopicMessagesDistributionMode. The specified value is {1} but the legal values are Compatibility, One-Copy-Per-Server, or One-Copy-Per-Application.

Cause: See the error message body.

Action: Correct the activation config property.
Level: 1

Type: ERROR

Impact: EJB

BEA-015030: The EJB {0} has an illegal permutation on distributed topic type and topicMessagesDistributionMode. Replicated distributed topics work with Compatibility, One-Copy-Per-Server, or One-Copy-Per-Application, but partitioned distributed topics only work with One-Copy-Per-Server or One-Copy-Per-Application. The EJB is configured to partitioned distributed topic and Compatibility.

Cause: See the error message body.

Action: Review the compatibility of distributed topic types and topicMessagesDistributionMode and fix them.
Level: 1

Type: ERROR

Impact: EJB

BEA-015031: The EJB {0} has a distributedDestinationConnection configured but the EJB is configured to connect to a remote cluster. Since the distributedDestinationConnection configuration is only valid in a local cluster, the setting will be ignored.

Cause: See the error message body.

Action: Connect to a local cluster, or remove the distributedDestinationConnection configuration.
Level: 1

Type: WARNING

Impact: EJB

BEA-015032: The EJB {0} is configured with the activation config property topicMessagesDistributionMode but the EJB is configured to connect to a JMS Queue. The topicMessagesDistributionMode is valid only for JMS Topic destinations.

Cause: See the error message body.

Action: Correct the activation config property.
Level: 1

Type: ERROR

Impact: EJB

BEA-015033: The EJB {0} has an invalid value configured for the activation config property {1}. Only WebLogic JMS server 10.3.4 or later versions support the values One-Copy-Per-Server or One-Copy-Per-Application. Prior to 10.3.4.0 Weblogic JMS server or other non-Weblogic JMS vendors, only the Compatibility value is supported.

Cause: See the error message body.

Action: Correct the activation config property.
Level: 1

Type: ERROR

Impact: EJB

BEA-015034: This destinaiton {1} is a remote replicated distribution topic which does not support durable subscriptions when the Message-Drive Bean {0} works in Compatibility mode.

Cause: See the error message body.

Action: Review and fix the compatibility of the activation config property SubscriptionDurability and topicMessagesDistributionMode.
Level: 1

Type: ERROR

Impact: EJB

BEA-015035: The EJB {0} is configured to support One-Copy-Per-Server mode but the partitioned topic is configured as LocalOnly. To support One-Copy-Per-Server mode, the LocalOnly setting will be overridden with EveryMember.

Cause: See the error message body.

Action: Change distributed-destination-connection to EveryMember to remove the warning.
Level: 1

Type: WARNING

Impact: EJB

BEA-015036: In the EJB {0}, the value for the activation config property {1} will be ignored since it is overridden with the value {2}.

Cause: See the error message body.

Action: To remove this warning, remove the duplicated configuration from the activation config property.
Level: 1

Type: WARNING

Impact: EJB

BEA-015037: In EJB {0}, the throws clause for method {1} in the bean class contains exceptions that are NOT in the throws clause of the corresponding {2} interface method.

Cause: See the error message body.

Action: Correct the throws clause. Implementation methods must have all exceptions that are provided by the corresponding interfaces.
Level: 1

Type: WARNING

Impact: EJB

BEA-015038: Problems definitively matching up the interface method {0} with a method in the bean class. Please modify your bean class to implement the interface {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015039: Cannot start an inactive Message-Driven Bean {0}. A redployment may be needed.

Cause: See the error message body.

Action: Redeploy the application and restart it.
Level: 1

Type: ERROR

Impact: EJB

BEA-015040: The Message-Driven Bean {0} is inactive now.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015041: The Message-Driven Bean {0} is active now.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015042: The JNDI name {0} is set for {1} home interface of EJB {2}, but cannot find {1} home in deployment descriptor. Specify {1} home in ejb-jar.xml.

Cause: See the error message body.

Action: Specify {1} home in ejb-jar.xml.
Level: 1

Type: WARNING

Impact: EJB

BEA-015043: A concurrent-call attempt failed on a stateful session bean instance because the lock was held by another thread or transaction, either because concurrent-access is prohibited or access could not be granted in a specific time period. You may change the concurrent-access behavior using the @AccessTimeout annotation or a corresponding element in deployment descriptor.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015044: @JNDIName is specified on multiple classes for the same business interface {0} but the value is different. Class: {1}; Class: {2}.

Cause: @JNDIName is specified on multiple classes for the same business interface {0} but the value is different. Class: {1}; Class: {2}.

Action: Remove @JNDIName from either {1} or {2}.
Level: 1

Type: ERROR

Impact: EJB

BEA-015045: @JNDIName on the bean implementation class does not provide the class of the client view, but more than one client view exists. Class: {0}.

Cause: @JNDIName on the bean implementation class does not provide the class of the client view, but more than one client view exists. Class: {0}.

Action: Remove @JNDIName from {0} or provide the class name of each client view.
Level: 1

Type: ERROR

Impact: EJB

BEA-015046: Illegal operation, context data is not supported for the Entity Bean.

Cause: An illegal operation has occurred, context data is not supported for the Entity Bean.

Action: Remove the retrieval operation for the Entity Bean's context data.
Level: 1

Type: ERROR

Impact: EJB

BEA-015047: Unable to bind portable JNDI name {0}.

Cause: The portable JNDI name could not be bound. See the exception for the cause.

Action: Check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: EJB

BEA-040010: JMSServer "{0}" configured {1,choice,0#no session pools|1#1 session pool|2#{1} session pools}.

Cause: This message indicates the number of session pools that were configured or deployed for the JMSServer while processing the configuration file.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040014: Failed to start JMSServer. JMS is shutting down.

Cause: The JMS server failed to initialize.

Action: Modify the configuration and restart the server file. Then reboot the system. There should be earlier messages that indicate the cause of the failure.
Level: 1

Type: ERROR

Impact: JMS

BEA-040015: JMS shutdown is complete.

Cause: JMS has been shut down, either at the request of the administrator or due to configuration errors.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040017: JMSServer "{0}" connection factory JNDI binding failed, {1}. JMS is shutting down.

Cause: An error was found when binding the connection factory to a JNDI name during configuration.

Action: Modify the configuration and restart the server file. Then reboot the system.
Level: 1

Type: ERROR

Impact: JMS

BEA-040018: Could not obtain a replicated or non-replicated InitialContext from the default provider, {0}.

Cause: An error was encountered when binding a JMS Server to a JNDI name during configuration.

Action: Modify the configuration and restart the server file. Then reboot the server.
Level: 1

Type: ERROR

Impact: JMS

BEA-040019: JMSServer "{0}" failed to bind to JNDI name: {1}.

Cause: An error was encountered when binding a JMS Server to a JNDI name during configuration.

Action: Modify the configuration and restart the server file. Then reboot the system.
Level: 1

Type: ERROR

Impact: JMS

BEA-040024: JMSServer "{0}" byte threshold for destination {1} has been exceeded.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: INTERNAL_ERROR

Impact: JMS

BEA-040025: JMSServer "{0}" byte threshold condition for destination {1} has cleared.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: INTERNAL_ERROR

Impact: JMS

BEA-040026: JMSServer "{0}" message threshold for destination {1} has been exceeded.

Cause: This is an informational message.

Action: No action
Level: 1

Type: INTERNAL_ERROR

Impact: JMS

BEA-040027: JMSServer "{0}" message threshold condition for destination {1} has cleared.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: INTERNAL_ERROR

Impact: JMS

BEA-040028: JMSServer "{0}" byte threshold for the server has been exceeded.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: INTERNAL_ERROR

Impact: JMS

BEA-040029: JMSServer "{0}" byte threshold for server has cleared.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: INTERNAL_ERROR

Impact: JMS

BEA-040030: JMSServer "{0}" message threshold for the server has been exceeded.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: INTERNAL_ERROR

Impact: JMS

BEA-040031: JMSServer "{0}" message threshold for the server has cleared.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: INTERNAL_ERROR

Impact: JMS

BEA-040068: JMSServer "{0}" error occurred while unregistering destination {1}.

Cause: Look for earlier messages that might explain the error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMS

BEA-040069: JMSServer "{0}" error occurred while unregistering producer {1}.

Cause: Look for earlier messages that might explain the error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMS

BEA-040070: JMSServer "{0}" error occurred while unregistering connection {1}.

Cause: Look for earlier messages that might explain the error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMS

BEA-040071: JMSServer "{0}" error occurred while unregistering session {1}.

Cause: Look for earlier messages that might explain the error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMS

BEA-040072: JMSServer "{0}" error occurred while unregistering consumer {1}.

Cause: Look for earlier messages that might explain the error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMS

BEA-040089: JMSServer "{0}". JMS messages in store ({1}) were migrated from version {2} to 600.

Cause: Message migration happens automatically when starting JMS and an old store exists.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040090: Deployed {0,choice,0#no default connection factories|1#1 default connection factory|2#{0} default connection factories}.

Cause: This message indicates the number of default connection factories deployed while processing the configuration file.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040095: JMSServer "{0}". Store I/O failure, {1}.

Cause: There is no more of file space, a disk failure occurred, or a database failure occurred.

Action: Restart the database, if applicable, and restart JMS.
Level: 1

Type: INTERNAL_ERROR

Impact: JMS

BEA-040107: Undeployed {0,choice,0#no default connection factories|1#1 default connection factory|2#{0} default connection factories}.

Cause: This message indicates the number of default connection factories that were undeployed.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040108: User connection factory "{0}" is started.

Cause: The specified user connection factory has been started.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040109: JMSServer "{0}" is started.

Cause: The specified JMS Server has been started.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040113: JMSServer "{0}", Opening file store "{1}" in directory "{2}". Starting scan of {3,choice,0#0 files|1#1 file|2#{3} files} totaling {4} bytes.

Cause: A JMS server has opened its persistent file store and is about to scan its contents for messages.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040119: Failed to deploy a JMS connection factory "{0}" due to {1}.

Cause: The JMS connection factory failed to initialize. Usually this is a configuration error. This may also happen when the server is shutting down but JMS still attempts to create a new connection factory.

Action: Modify the configuration and restart the server file. Then reboot the system.
Level: 1

Type: ERROR

Impact: JMS

BEA-040120: Failed to bind JMS connection factory "{0}" with its JNDI name due to {1}.

Cause: This is a JNDI failure.

Action: Modify the configuration and restart the server file. Then reboot the system.
Level: 1

Type: ERROR

Impact: JMS

BEA-040121: JMSServer "{0}". Cannot be deployed on multiple servers.

Cause: A JMS Server was deployed on more than one WebLogic Server instance, and this is not allowed.

Action: Change the configuration file and reboot the system.
Level: 1

Type: ERROR

Impact: JMS

BEA-040122: Failed to deploy JMS Server "{0}" due to {1}.

Cause: The JMS server failed to initialize. Usually this is a configuration error. This may also happen when the server is shutting down but JMS still attempts to create a new JMS server.

Action: Modify the configuration and restart the server file. Then reboot the system.
Level: 1

Type: ERROR

Impact: JMS

BEA-040123: Failed to start JMS Server "{0}" due to {1}.

Cause: A JNDI failure occurred, or there was a failure when starting destinations, server session pools and/or connection consumers.

Action: Modify the configuration and restart the server file. Then reboot the system.
Level: 1

Type: ERROR

Impact: JMS

BEA-040124: JMSServer "{0}". Failed to create JMS server session pool "{1}" due to {2}.

Cause: The JMS server session pool failed to initialize. Usually this is a configuration error. This may also happen when the server is shutting down but JMS still attempts to create a new JMS server session pool.

Action: Modify the configuration and restart the server file. Then reboot the system.
Level: 1

Type: ERROR

Impact: JMS

BEA-040125: JMSServer "{0}". Failed to create JMS connection consumer "{1}" due to {2}.

Cause: The JMS connection consumer failed to initialize. Usually this is a configuration error. This may also happen when the server is shutting down but JMS still attempts to create a new JMS connection consumer.

Action: Modify the configuration and restart the server file. Then reboot the system.
Level: 1

Type: ERROR

Impact: JMS

BEA-040127: Failed to create JMS multicast socket due to {0}.

Cause: The JMS multicast socket failed to initialize.

Action: Reboot the system.
Level: 1

Type: ERROR

Impact: JMS

BEA-040215: JMS server "{0}". Cannot set "{1}" to -1 when paging is enabled. The value of the attribute remains unchanged.

Cause: This is caused by an invalid configuration.

Action: Disable paging before setting this value to -1.
Level: 1

Type: ERROR

Impact: JMS

BEA-040305: JMS service is initialized and in standby mode.

Cause: The initialization phase of the JMS service is completed and the JMS service is in standby mode.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040306: JMS service is active now.

Cause: The activation phase of the JMS service is completed, and the JMS service is in active mode.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040307: JMS service is suspending gracefully.

Cause: The JMS service has started the suspension phase. No new work will be accepted and JMS Service will attempt to complete all existing work before it brings itself to standby mode.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040308: JMS service is suspending.

Cause: The JMS service has started the suspension phase. No new work will be accepted and all the existing work will be terminated immediately before the JMS service brings itself to standby mode.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040321: JMSServer "{0}" is resuming.

Cause: The JMSServer "{0}" is resuming.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040324: JMSServer "{0}" is suspending.

Cause: The JMSServer "{0}" is suspending.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040325: JMSServer "{0}" is suspended.

Cause: The JMSServer "{0}" is suspended.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040351: ExpiredJMSMessage JMSMessageID={0} > {1} {2} </ExpiredJMSMessage

Cause: A message has been expired and the policy is to log the message header fields and messages properties so that they are printed.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040352: ExpiredJMSMessage JMSMessageID={0} > {1} </ExpiredJMSMessage

Cause: A message has been expired and the policy is to log the message header fields so that they are printed.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040353: ExpiredJMSMessage JMSMessageID={0} > {1} </ExpiredJMSMessage

Cause: A message has been expired and the policy is to log the messages properties so that they are printed.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040354: ExpiredJMSMessage JMSMessageID={0} > </ExpiredJMSMessage

Cause: A message has been expired and the policy is to log only the MessageId, or there are no matching message header fields or message properties.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040359: Distributed Destination "{0}", member "{1}" is not associated with a physical destination.

Cause: This was caused by a onfiguration error.

Action: Modify the configuration and restart the server.
Level: 1

Type: WARNING

Impact: JMS

BEA-040368: The following exception has occurred:

Cause: An error condition has occurred.

Action: Look for the associated exception in the log or your program to see what the results are. In general, this stack trace will help in debugging an existing problem.
Level: 1

Type: ERROR

Impact: JMS

BEA-040370: Linked Exception -----------

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040371: JMSServer "{0}" JMS server session pool is invalid and has not been started "{1}". Exception is "{2}".

Cause: The server session pool is invalid because it has an invalid Connection Factory or Listener.

Action: Edit the JMS session pool, verify that it has valid attributes, and reboot the server. Alternatively, delete the session pool and add a new valid JMS session pool.
Level: 1

Type: ERROR

Impact: JMS

BEA-040372: JMSServer "{0}" error occurred while unregistering the runtime MBean, {1}.

Cause: Unable to contact the Administration Server or unable to find the runtime MBean.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JMS

BEA-040373: Could not find a license for JMS. Please contact Oracle to get a license.

Cause: Unable to get a license for JMS.

Action: Contact your Oracle sales representative to get a license.
Level: 1

Type: ERROR

Impact: JMS

BEA-040376: Destination {0} has been paused for new message production.

Cause: A Production Pause request was issued for the specified destination.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040377: Destination {0} has been resumed for new message production.

Cause: A Production Resume request was issued for the specified destination.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040378: Destination {0} has been paused for insertion of messages from in-flight work completion.

Cause: An Insertion Pause request was issued for the specified destination.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040379: Destination {0} has been resumed for insertion of messages from in-flight work completion.

Cause: An Insertion Resume request was issued for the specified destination.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040380: Destination {0} has been paused for consumption.

Cause: A Consumption Pause request has been issued for the specified destination.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040381: Destination {0} has been resumed for consumption.

Cause: A Consumption Resume request has been issued for the specified destination.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040382: JMSServer {0} has been paused for new message production.

Cause: A Production Pause request was issued for the specified JMSServer.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040383: JMSServer {0} has been resumed for new message production.

Cause: A Production Resume request was issued for the specified JMSServer.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040384: JMSServer {0} has been paused for insertion of messages from in-flight work completion.

Cause: An Insertion Pause request was issued for the specified JMS server.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040385: JMSServer {0} has been resumed for insertion of messages from in-flight work completion.

Cause: An Insertion Resume request has been issued for the specified JMS server.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040386: JMSServer {0} has been paused for consumption.

Cause: A Consumption Pause request has been issued for the specified JMS server.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040387: JMSServer {0} has been resumed for consumption.

Cause: A Consumption Resume request has been issued for the specified JMS server.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040404: Foreign JMS Server "{0}" is started.

Cause: The specified foreign JMS server was started.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040405: Failed to bind an entity of Foreign JMS Server "{0}" with their JNDI names due to {1}.

Cause: This was caused by a JNDI failure.

Action: Modify the JMS module descriptor of the corresponding application and redeploy the application.
Level: 1

Type: ERROR

Impact: JMS

BEA-040406: Distributed destination "{0}" is started.

Cause: The specified distributed destination was started.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040407: Default connection factory "{0}" with its JNDI name "{1}" is started.

Cause: The specified default connection factory was started.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040408: Failed to bind default connection factory "{0}" with its JNDI name "{1}" due to {2}.

Cause: This was caused by a JNDI failure.

Action: Modify the configuration and restart the server file. Then reboot the system.
Level: 1

Type: ERROR

Impact: JMS

BEA-040409: FailedJMSMessage for store-and-forward: JMSMessageID={0} > {1} {2} </FailedJMSMessage

Cause: A message was expired before it was successfully forwarded by the SAF agent, and the policy is to log the message header fields and messages properties so that they are printed.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040410: FailedJMSMessage for store-and-forward: JMSMessageID={0} > {1} </FailedJMSMessage

Cause: A message was expired before it was successfully forwarded by the SAF agent, and the policy is to log the message header fields and messages properties so that they are printed.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040411: FailedJMSMessage for store-and-forward: JMSMessageID={0} > {1} </FailedJMSMessage

Cause: A message was expired before it was successfully forwarded by the SAF agent, and the policy is to log the message header fields and messages properties so that they are printed.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040412: FailedJMSMessage for store-and-forward: JMSMessageID={0} > </FailedJMSMessage

Cause: A message was expired before it was successfully forwarded by the SAF agent, and the policy is to log only the MessageId. Alternatively, there are no matching message header fields or message properties.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040420: The JMS transaction branch {1} for destination {0} was administratively committed.

Cause: This was caused by an administrative action.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040421: An administrative request to commit the JMS transaction branch {1} on destination {0} failed with the following exception. {2}

Cause: The cause of the failure may be indicated by the exception provided in the error message.

Action: The transaction may be in an invalid state to allow commit processing. Attempt the operation again or wait for the Transaction Manager to resolve the transaction branch.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040422: The JMS transaction branch {1} for destination {0} was administratively rolled back.

Cause: This was caused by an administrative action.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040423: An administrative request to rollback the JMS transaction branch {1} on destination {0} failed with the following exception. {2}

Cause: The cause of the failure may be indicated by the exception provided in the error message.

Action: Attempt the operation again or wait for the Transaction Manager to resolve the transaction branch.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040430: The "UserTransactionsEnabled" attribute on the JMSConnectionFactory "{0}" has been deprecated and replaced by the "XAConnectionFactoryEnabled" attribute. The changes are propagated to/from this new attribute.

Cause: A deprecated attribute was used.

Action: Use the XAConnectionFactoryEnabled attribute instead.
Level: 1

Type: WARNING

Impact: JMS

BEA-040431: The "XAServerEnabled" attribute on the JMSConnectionFactory "{0}" has been deprecated and replaced by the "XAConnectionFactoryEnabled" attribute. The changes are propagated to/from this new attribute.

Cause: A deprecated attribute is used.

Action: Use the XAConnectionFactoryEnabled attribute instead.
Level: 1

Type: WARNING

Impact: JMS

BEA-040442: While attempting to bind JNDI name {0} for destination {1} in module {2}, a JNDI name conflict was found. This destination has not been bound into JNDI.

Cause: Some other entity has already bound this JNDI name globally.

Action: Determine the owner of the currently bound JNDI name and remove it if it should not be there, or change the JNDI name of this destination so that it does not conflict with the existing one.
Level: 1

Type: WARNING

Impact: JMS

BEA-040443: While attempting to change the JNDI name from {0} to {1} for destination {2} in module {3}, a JNDI name conflict was found. This destination is no longer globally bound into JNDI under any name.

Cause: Some other entity has already bound this JNDI name globally.

Action: Determine the owner the currently bound JNDI name and remove it if it should not be there, or change the JNDI name of this destination so that it does not conflict with the existing one.
Level: 1

Type: WARNING

Impact: JMS

BEA-040444: While attempting to unadvertise the JNDI name {0} for destination {1} in module {2}, an error occurred. The name may or may not be unadvertised globally.

Cause: A network connection between the local server and the Administration Server may have gone down.

Action: Make sure that network connectivity is working properly and that the Administration Server is reachable.
Level: 1

Type: WARNING

Impact: JMS

BEA-040445: While attempting to change the JNDI name from {0} to {1} for destination {2} in module {3}, a JNDI name conflict was found. This destination is no longer locally bound into JNDI under any name.

Cause: Some other entity has already bound this JNDI name locally.

Action: Determine the owner of the currently bound JNDI name and remove it if it should not be there or change the JNDI name of this destination so that it does not conflict with the existing one.
Level: 1

Type: WARNING

Impact: JMS

BEA-040446: While attempting to unadvertise the JNDI name {0} for destination {1} in module {2}, an error occurred. The name may or may not be unadvertised locally.

Cause: A network connection between the local server and the Administration Server may have gone down.

Action: Make sure that network connectivity is working properly and that the Administration Server is reachable.
Level: 1

Type: WARNING

Impact: JMS

BEA-040447: While attempting to bind the JNDI name {0} for destination {1} in module {2}, a JNDI name conflict was found. This destination has not been bound into JNDI locally.

Cause: Some other entity has already bound this JNDI name locally.

Action: Determine the owner of the currently bound JNDI name and remove it if it should not be there, or change the JNDI name of this destination so that it does not conflict with the existing one.
Level: 1

Type: WARNING

Impact: JMS

BEA-040448: JMSFileStoreMBean has been deprecated, and has been replaced with FileStoreMBean. The JMSFileStoreMBean "{0}" has been replaced in the configuration with a FileStoreMBean with the same name.

Cause: A deprecated MBean was replaced in the configuration.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JMS

BEA-040449: JMSJDBCStoreMBean has been deprecated, and has been replaced with JDBCStoreMBean. The JMSJDBCStoreMBean "{0}" has been replaced in the configuration with a JDBCStoreMBean with the same name.

Cause: A deprecated MBean was replaced in the configuration.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JMS

BEA-040450: The "PagingStore" attribute on the JMSServerMBean "{0}" has been deprecated. It is being replaced in the configuration with the new "PagingDirectory" attribute.

Cause: A deprecated MBean attribute was replaced in the configuration.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JMS

BEA-040451: The PagingStore attribute on the JMSServerMBean {0} has been deprecated. Since it currently refers to a JMSJDBCStoreMBean, and paging to a JDBC store is not supported, the JMS server will page messages to its local working directory.

Cause: A deprecated MBean attribute was replaced in the configuration.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JMS

BEA-040452: The server session pool feature has been deprecated, and it will be removed in an upcoming release. New applications should use message-driven beans (MDBs) instead.

Cause: A deprecated feature was detected in the configuration.

Action: Plan to replace use of server session pools in your application.
Level: 1

Type: WARNING

Impact: JMS

BEA-040453: The BytesPagingEnabled and MessagesPagingEnabled parmeters on the JMSServer {0} have been deprecated. These parameters are now ignored. The MessageBufferSize parameter should be used to configure paging in this release.

Cause: A deprecated parameter was encountered.

Action: Plan to use the new MessageBufferSize to control paging.
Level: 1

Type: WARNING

Impact: JMS

BEA-040455: Flow control has been enabled on JMS server "{0}" because memory is low

Cause: Too much memory is being used.

Action: Either increase the amount of memory available to the server, or decrease the MessageBufferSize parameter on the JMS server so that fewer messages remain in memory.
Level: 1

Type: WARNING

Impact: JMS

BEA-040456: An entity of type "{3}" with name "{2}" in JMS module "{0}" is not targeted. There is no subdeployment with name "{1}" in the configuration repository (config.xml). Therefore, this entity will not exist anywhere in the domain.

Cause: The entity of the given name and type in the given JMS module does not have a corresponding subdeployment in the configuration repository (config.xml). In order for this entity to exist in the domain, it must be targeted with a sub-deployment element.

Action: Add a sub-deployment stanza to the appropriate deployment descriptor in config.xml. This will either be a jms-system-resource for a system module, or an app-deployment for a stand-alone JMS deployable module. If the JMS module is inside a J2EE application (an EAR file), then you must add the sub-deployment stanza to the subdeployment that represents this JMS module in the J2EE application. You do not necessarily have to target the subdeployment yet. Simply adding the subdeployment with no targets will remove this warning. However, if you wish for this entity to exist somewhere in your domain you must target the sub-deployment.
Level: 1

Type: WARNING

Impact: JMS

BEA-040457: The Template named "{1}" element of Distributed Destination "{0}" is not supported and hence ignored. Please consider using a Uniform Distributed Destination.

Cause: An unsupported attribute JMSTemplate is used in a Distributed Destination.

Action: Use a Uniform Distributed Destination instead.
Level: 1

Type: WARNING

Impact: JMS

BEA-040458: Unable to unprepare {0} in module {1} due to {2}.

Cause: The prepared entity could not unprepare itself in a failure case.

Action: Refer to the available exception for more information.
Level: 1

Type: WARNING

Impact: JMS

BEA-040459: Unable to deactivate {0} in module {1} due to {2}.

Cause: The activated entity could not deactivate itself in a failure case.

Action: Refer to the available exception for more information.
Level: 1

Type: WARNING

Impact: JMS

BEA-040460: Unable to close the JMS component of module {0} due to {1}.

Cause: The JMS component could not close itself.

Action: Refer to the available exception for more information.
Level: 1

Type: WARNING

Impact: JMS

BEA-040461: Unable to deactivate {0} in module {1} due to {2}.

Cause: The activated entity could not deactivate itself in a failure case.

Action: Refer to the available exception for more information.
Level: 1

Type: WARNING

Impact: JMS

BEA-040464: Unable to destroy {0} in module {1} due to {2}.

Cause: The initialized entity could not destroy itself in a failure case.

Action: More information may be available from the exception.
Level: 1

Type: WARNING

Impact: JMS

BEA-040467: Unable to deactivate {0} in module {1} due to {2}.

Cause: The activated entity could not deactivate itself in a failure case.

Action: More information may be available from the exception.
Level: 1

Type: WARNING

Impact: JMS

BEA-040470: Unable to deactivate {0} in module {1} due to {2}.

Cause: The activated entity could not deactivate itself during dynamic deletion.

Action: More information may be available from the exception.
Level: 1

Type: WARNING

Impact: JMS

BEA-040475: The destination {0} does not have an associated quota object. The setting of bytesMaximum to {1} will have no effect.

Cause: Quotas have been reworked. They are no longer hierarchical in nature. Instead, they are objects that can be pointed to explicitly and can be optionally shared between destinations. Hence quotas no longer work as they did in previous releases. When converting from older releases, a decision is made about how to handle quotas based on the setting of the old parameters. These decisions may have been wrong, which would cause this warning to happen.

Action: Please consider removing this destination from the interop module. Put it in another module. This will allow you to use the new quota features.
Level: 1

Type: WARNING

Impact: JMS

BEA-040476: The destination {0} does not have an associated quota object. The setting of messagesMaximum to {1} will have no effect.

Cause: Quotas have been reworked. They are no longer hierarchical in nature. Instead, they are objects that can be pointed to explicitly and can be optionally shared between destinations. Hence quotas no longer work as they did in previous releases. When converting from older releases a decision is made about how to handle quotas based on the setting of the old parameters. These decisions may have been wrong, which would cause this warning to happen.

Action: Please consider removing this destination from the interop module. Put it in another module. This will allow you to use the new quota features.
Level: 1

Type: WARNING

Impact: JMS

BEA-040477: An error occurred while unbinding a remote JNDI object from local JNDI name "{0}". The exception encountered was {1}.

Cause: There may be an error in the JNDI subsystem. See the exception for more information.

Action: Check the exception message for more detail.
Level: 1

Type: WARNING

Impact: JMS

BEA-040478: The JMS subsystem could not deploy or undeploy the default JMS connection factories due to {0}.

Cause: There may be an error in the JNDI subsystem. See the exception for more information.

Action: Check the exception message for more detail.
Level: 1

Type: WARNING

Impact: JMS

BEA-040479: The system failed to roll back an added connection consumer of name {0}. The exception received was {1}.

Cause: See the exception for more information.

Action: Check the exception message for more detail.
Level: 1

Type: WARNING

Impact: JMS

BEA-040480: The system failed to remove a connection consumer of name {0}. The exception received was {1}.

Cause: See the exception for more information.

Action: Check the exception message for more detail.
Level: 1

Type: WARNING

Impact: JMS

BEA-040490: {0} {1} has a conflicting name attribute value, which is now changed to have a unique name with its JMSServer name. The new destination-name attribute now holds the original name value.

Cause: A name conflict has been detected during upgrade for JMS destinations, maybe because in WebLogic Server versions prior to 9.2, more than one destination was allowed to have the same name, as long as the destinations belonged to different JMS servers.

Action: Ensure that destinations are created with their name decorated with the target JMS server name to avoid conflict.
Level: 1

Type: WARNING

Impact: JMS

BEA-040491: A {0} {1} with multiple targets has been split into multiple deployments one for each unique target.

Cause: A JMS Deployment found with multiple unique targets configured.

Action: In WebLogic Server versions prior to 9.2, both JMSConnectionFactory and ForeignJMSServer were allowed to be targeted to more than one server, cluster, or both. During upgrade of this configuration to WebLogic Server 9.2, these configuration entities are split into more than one entity, one for each unique target.
Level: 1

Type: WARNING

Impact: JMS

BEA-040494: An error occurred while shutting down the JMS server {0}: {1}.

Cause: See the detail message.

Action: The server should still shut down normally. No action is required.
Level: 1

Type: WARNING

Impact: JMS

BEA-040496: The template {0} does not have an associated quota object. The setting of bytesMaximum to {1} will have no effect.

Cause: Quotas have been reworked. They are no longer hierarchical in nature. Instead, they are objects that can be pointed to explicitly and can be optionally shared between destinations. Hence quotas no longer work as they did in previous releases. When converting from older releases a decision is made about how to handle quotas based on the setting of the old parameters. These decisions may have been wrong, which would cause this warning to happen.

Action: Please consider removing this template from the interop module. Put it in another module. This will allow you to use the new quota features.
Level: 1

Type: WARNING

Impact: JMS

BEA-040497: The template {0} does not have an associated quota object. The setting of MessagesMaximum to {1} will have no effect.

Cause: Quotas have been reworked. They are no longer hierarchical in nature. Instead, they are objects that can be pointed to explicitly and can be optionally shared between destinations. Hence quotas no longer work as they did in previous releases. When converting from older releases a decision is made about how to handle quotas based on the setting of the old parameters. These decisions may have been wrong, which would cause this warning to happen.

Action: Consider removing this template from the interop module. Put it in another module. This will allow you to use the new quota features.
Level: 1

Type: WARNING

Impact: JMS

BEA-040498: An error occurred while forwarding a message for distributed destination member {0}: {1}

Cause: There may be a temporary network problem, or one of the members of the cluster may be unavailable.

Action: See the detail message.
Level: 1

Type: WARNING

Impact: JMS

BEA-040499: An error occurred while pushing messages to a JMS client: {0}

Cause: There may be a network failure.

Action: The JMS protocol will recover automatically from such a problem eventually. Check for networking issues or crashed clients.
Level: 1

Type: WARNING

Impact: JMS

BEA-040500: Unable to deactivate entity "{0}" in module "{1}" due to {2}.

Cause: The activated entity could not rollback the proposed targeting change.

Action: More information may be available from the exception.
Level: 1

Type: WARNING

Impact: JMS

BEA-040501: Unable to roll back targeting change of the entity "{0}" in module "{1}" due to {2}.

Cause: The changed entity could not roll back in a failure case.

Action: More information may be available from the exception.
Level: 1

Type: WARNING

Impact: JMS

BEA-040502: While attempting to change the targeting of JMS module "{0}", an error occurred while activating the change. The exception returned is: {1}

Cause: The JMS module failed to activate a prepared change during a targeting update.

Action: More information may be available from the exception.
Level: 1

Type: ERROR

Impact: JMS

BEA-040503: The delivery mode override value of destination "{0}" hosted on JMS server "{1}" has been changed from {2} to {3}.

Cause: During the upgrade process, a configuration was detected that would force all messages through the given destination to be non-persistent. Therefore, the upgrade process made that override explicit.

Action: Review your application code and configuration. If you need a behavior other than the one that the upgrade process chose, you can modify the resulting configuration using the DeliveryMode parameter of the OverridesParams of the destination, or with the HasStore or AllowsPersistentDowngrade parameters of the JMS server on which the destination is targeted.
Level: 1

Type: WARNING

Impact: JMS

BEA-040504: While attempting to add an entity with name "{0}", an error occurred while trying to convert the old style entity to the new style entity. The error was "{1}".

Cause: See the description of the exception that occurred for more information on the cause of this failure.

Action: Take appropriate action based on the determined cause.
Level: 1

Type: WARNING

Impact: JMS

BEA-040505: The JMS module named "{0}" inside application "{1}" does not have a sub-deployment stanza named "{0}". Without such a stanza, no entities inside the module will be deployed, since the subdeployments inside of the sub-deployment stanza named "{0}" control where JMS entities inside this module are targeted.

Cause: When a JMS module is inside an EAR file, the targeting information for entities inside that module are nested within a sub-deployment named after the name of the JMS module found in the weblogic-application.xml file of the EAR file. If no sub-deployment exists with the name of the JMS module, then no targeted entities inside the module will become available. This is usually an oversight on the part of the administrator.

Action: Add a sub-deployment stanza with the name of the JMS module as specified in the weblogic-application.xml file to the app-deployment stanza. Nested inside that sub-deployment, you can target the entities in the module as you normally would.
Level: 1

Type: WARNING

Impact: JMS

BEA-040506: The JMS store-and-forward (SAF) forwarder has successfully connected to the remote destination "{0}".

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040507: The JMS store-and-forward (SAF) forwarder failed to connect to the remote destination "{0}", because of {1}.

Cause: This is either due to a configuration error, a network failure, or the remote destination being temporarily unavailable.

Action: Check the configuration, network connection, or remote destination.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040508: BridgeDestinationMBean has been deprecated. The BridgeDestination "{0}" has been replaced in the configuration with a JMSBridgeDestination with the same name.

Cause: A deprecated MBean is being replaced in the configuration.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JMS

BEA-040509: Failed to ${1} JMS Server "{0}" because the earlier attempt to ${2} was failed.

Cause: This error occurred during deployment of the JMS server.

Action: Fix any deployment errors related to this JMS server.
Level: 1

Type: ERROR

Impact: JMS

BEA-040510: While attempting to rename a connection factory named "{0}", an error occurred while attempting to establish a JNDI listener. The cause was {1}.

Cause: There was an error while attempting to establish a JNDI listener. The description of the cause may provide more information about the true cause of the error.

Action: The cause of this problem may give an indication of the source of this problem. If this problem persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMS

BEA-040511: The system is waiting to unbind connection factory "{0}". An attempt is being made to change the JNDI name of this connection factory from "{1}" to "{2}".

Cause: An attempt is being made to unbind a connection factory from a JNDI name in order to dynamically change the JNDI from one name to another. This message will repeat every twenty seconds for five minutes.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040512: An attempt is being made to change the JNDI name of connection factory "{0}" from "{1}" to "{2}". The system has waited to unbind "{1}" for five minutes. The new JNDI name "{2}" may or may not be bound properly.

Cause: The connection factory was not fully unbound after five minutes. Some error may have occurred while attempting to unbind this connection factory.

Action: In order to maintain the integrity of the connection factory it is recommended you untarget and retarget the connection factory that failed. Otherwise, the connection factory is in an indeterminate state.
Level: 1

Type: ERROR

Impact: JMS

BEA-040513: While attempting to rename a connection factory named "{0}", an error occurred while attempting to remove a JNDI listener. The cause was {1}.

Cause: There was an error while attempting to remove a JNDI listener. The description of the cause may provide more information about the true cause of the error.

Action: The cause of this problem may give an indication of the source of this problem and the action to take. If this problem persists, contact My Oracle Support.
Level: 1

Type: WARNING

Impact: JMS

BEA-040514: While attempting to rename a connection factory named "{0}" an error occurred in the JNDI listener. The error was {1}

Cause: While attempting to dynamically change the JNDI name of a connection factory, a JNDI error occurred. The error itself will tell more about the cause of this failure.

Action: The cause of this problem may give an indication of the source of this problem and the action to take. If this problem persists, contact My Oracle Support.
Level: 1

Type: WARNING

Impact: JMS

BEA-040515: A failured occured while attempting to unregister an InterceptionPoint, {0}.

Cause: An exceptoin coccurred while attempting to unregister an InterceptionPoint. The error will provide more details about the cause of this failure.

Action: The cause of this problem may give an indication of the source of this problem. If this problem persists, contact My Oracle Support.
Level: 1

Type: WARNING

Impact: JMS

BEA-040520: One or more Weighted Distributed Destination (WDD) resources were detected in JMS configuration module "{1}": {0}. This resource type was deprecated as of WebLogic Server 10.3.4.0. Consider using a Uniform Distributed Destination (UDD) instead. If you want to suppress this warning, set system property "weblogic.jms.WDD.SuppressDeprecationWarnings" to true when starting each WebLogic Server instance.

Cause: Deprecated resource was used.

Action: Use the Uniform Distributed Destination instead.
Level: 1

Type: WARNING

Impact: JMS

BEA-040521: The JMS resource "{0}" that you are trying to create in module "{1}" is a Weighted Distributed Destination (WDD). This resource type was deprecated as of WebLogic Server 10.3.4.0. Consider using a Uniform Distributed Destination (UDD) instead. If you want to suppress this warning, set system property "weblogic.jms.WDD.SuppressDeprecationWarnings" to true when starting each WebLogic Server instance.

Cause: A deprecated resource is trying to create.

Action: Use the Uniform Distributed Destination instead.
Level: 1

Type: WARNING

Impact: JMS

BEA-045002: An error occurred while binding the remote JNDI object to the local JNDI name "{0}".

Cause: The local JNDI name that is attempting to bind to may not be valid.

Action: Check the JNDI name to see if its syntax is correct.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045028: The messages threshold for the JMS server {0} has been exceeded for more than one hour.

Cause: The threshold of the JMS server was exceeded.

Action: Verify that the messages are being consumed and that sufficient memory is available.
Level: 1

Type: WARNING

Impact: JMSExceptions

BEA-045029: The messages threshold for the JMS server {0} has been exceeded for more than 90 percent of the running time of the server.

Cause: The messages threshold of the JMS server was exceeded.

Action: Verify that the messages are being consumed and that sufficient memory is available.
Level: 1

Type: WARNING

Impact: JMSExceptions

BEA-045030: The bytes threshold for the JMS server {0} has been exceeded for more than one hour.

Cause: The bytes threshold of the JMS server was exceeded.

Action: Verify that the messages are being consumed and that sufficient memory is available.
Level: 1

Type: WARNING

Impact: JMSExceptions

BEA-045031: The bytes threshold for the JMS server {0} has been exceeded for more than 90 percent of the running time of the server.

Cause: The bytes threshold of the JMS server was exceeded.

Action: Verify that the messages are being consumed and that sufficient memory is available.
Level: 1

Type: WARNING

Impact: JMSExceptions

BEA-045032: While attempting to create destination {1} in module {2} the JMS server {0} could not be found.

Cause: The JMS server may be shutting down or may not have completed startup.

Action: Deploy the module again once the JMS server has completed startup.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045039: An attempt was made to add a JMS entity of an unknown type {1} in the module {0}.

Cause: The JMS module given to the update was invalid. It contained an unknown type.

Action: Ensure that the JMS module is valid.
Level: 1

Type: WARNING

Impact: JMSExceptions

BEA-045040: While attempting to add a {1} named {2} in module {0}, an error occurred.

Cause: A linked ModuleException will contain more detail about the cause of the failure.

Action: Examine the linked exception, which will contain more information about the cause of this failure.
Level: 1

Type: WARNING

Impact: JMSExceptions

BEA-045041: An attempt was made to remove a JMS entity of an unknown type {1} in the module {0}.

Cause: The JMS module given to the update was invalid. It contained an unknown type.

Action: Ensure that the JMS module is valid.
Level: 1

Type: WARNING

Impact: JMSExceptions

BEA-045042: An error occurred while adding {1} to the JMS module {0}.

Cause: See the linked exception for more detail.

Action: The linked exception will contain more information about why this add operation failed.
Level: 1

Type: WARNING

Impact: JMSExceptions

BEA-045043: An error occurred while removing {1} from the JMS module {0}.

Cause: See the linked exception for more detail.

Action: The linked exception will contain more information about why this add operation failed.
Level: 1

Type: WARNING

Impact: JMSExceptions

BEA-045045: A subdeployment named {1} was not found in the module {0}.

Cause: A subdeployment removal was attempted, but the subdeployment was unknown to the module.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045047: The SubDeploymentMBean {0} in deployment {1} can only be targeted to one JMSServerMBean because an entity that can only be targeted to a single JMS server (for example a queue, topic or quota) has a sub-deployment-name element with value {0}

Cause: The SubDeploymentMBean of the given name cannot be targeted to anything but a single JMS server because an element of the JMS module that points to that subdeployment can only be targeted to a single JMS server.

Action: Modify the target of the subdeployment so that it only contains a single JMS server.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045048: The JMS server named {0} has a temporary template configured. The JMSSystemResourceMBean name of the module containing the temporary template is {1}, and the template name is {2}. However, a JMSSystemResourceMBean of name {1} could not be found. The JMS server {0} will not boot until this problem has been fixed.

Cause: The temporary template for a JMS server must come from a JMSSystemResourceMBean. A common mistake is to put the temporary template into an AppDeployment. However, because the temporary template must be owned by the administrator, all temporary templates must come from JMSSystemResourceMBeans, not AppDeployments.

Action: Put the temporary template into a JMSSystemResource.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045049: JMS server {0} does not have a configured temporary template. However an attempt was made to create a temporary destination. This is not allowed.

Cause: A JMS server without a configured temporary template was used to create a temporary destination. This usage is not allowed.

Action: Create a JMSSystemResource that contains a template. Use that template as the temporary template for this JMS server.
Level: 1

Type: WARNING

Impact: JMSExceptions

BEA-045050: A destination named {3} has a jms-create-destination-identifier named {1}. However, another destination named {2} has the same jms-create-destination-identifier. Two destinations with the same jms-create-destination-identifier cannot both be located on the JMS server named {0}.

Cause: Two destinations cannot both have the same jms-create-destination-identifier on the same JMS server, even if the two destinations are from different modules.

Action: Either deploy the destination with the offending jms-create-destination-identifier to a different JMS server, or change the value of the jms-create-destination-identifier attribute.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045051: Two destinations with name {1} were deployed to the JMS server {0}.

Cause: Two destinations with the same fully qualified name cannot be deployed to the same JMS server. This error should have been caught during the validation phase of the JMS module.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045052: An attempt was made to change the target of a JMS entity that cannot have its target changed. The entity has name "{0}". The original target has name "{1}". The proposed target has name "{2}"

Cause: An attempt was made to change the target of an entity that cannot have its target changed dynamically.

Action: Untarget a subdeployment and then retarget that subdeployment elsewhere. However, by doing so, the persistent state maintained for entities retargeted in this fashion will not be kept on the old target and may or may not be removed by the system.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045054: Cannot dynamically add member {1} to sistributed destination {0}.

Cause: This member has either not been prepared yet or has already been removed.

Action: Ensure that the distributed destination member is not removed and is in a prepared state.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045055: Cannot dynamically remove member {1} from distributed destination {0}.

Cause: This member has either not been activated yet or is an invalid member.

Action: Ensure that the distributed destination member is valid and is in an activated state.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045060: The JMS module named "{0}" is neither an AppDeployment nor a JMSSystemResource.

Cause: An invalid application context was passed to a JMS module.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045061: An attempt was made to create a durable subscription on a queue named "{3}". The client identifier is "{0}", the subscriptionName is "{1}" and the selector is "{2}". Durable subscriptions may only be created on topics.

Cause: An attempt was made to create a durable subscription on a queue.

Action: Do not attempt to create a durable subscription on a queue.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045062: There can be no more than one jms-interop-module element in the config.xml file.

Cause: More than one jms-interop-module element was found in the config.xml file.

Action: Do not attempt to define more than one jms-interop-module element in the config.xml file.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045063: The jms-interop-module must have name interop-jms and a descriptor file name jms/interop-jms.xml. This has name "{0}".

Cause: An attempt was made to use a jms-interop-module with a name other than interop-jms.

Action: Do not attempt to define a jms-interop-module element in the config.xml file with a name other than interop-jms.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045064: The target named "{1}" of a JMS module inside a deployment named "{0}" must be a WebLogic Server instance or a cluster. Instead, it is of type "{2}".

Cause: An attempt was made to target a JMS module to an invalid type of target.

Action: Do not attempt to target a JMS module to anything other than WebLogic Server instances or clusters. Any other type of target is not understood.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045065: A JMS module with fully qualified name "{1}" in an application named "{0}" does not have the proper hierarchy of targets. In particular, the subdeployment named "{2}" has a target "{3}" that is not a subtarget of any of the targets of "{0}". For example, the target "{3}" is not a subtarget of "{4}".

Cause: A target of a subdeployment of a JMS module was not contained within the targets of the whole JMS module.

Action: Ensure that the JMS module is targeted to a super-set of all the targets of the subdeployment, or retarget the subdeployment within the set of targets for the JMS module.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045066: The target named "{1}" of a JMS subdeployment named "{3}" inside a deployment named "{0}" must be a JMS server, WebLogic Server instance, or a cluster. Instead, it is of type {2}.

Cause: An attempt was made to target a JMS subdeployment to an invalid type of target.

Action: Do not attempt to target a JMS subdeployment to anything other than JMS servers, WebLogic Server instances or clusters. Any other type of target is not understood.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045067: The field "destination-name" was set to "{3}", in the distributed destination member "{2}", in the distributed destination "{1}", in the module "{0}". The destination-name field of a distributed destination may only be set in the interop module.

Cause: An attempt was made to set the destination-name field of a distributed destination member type. This is only allowed in the interop module in order to accommodate older clients.

Action: Change the name of the distributed destination member to the name of the physical queue or topic being referenced, and unset the destination-name field.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045068: The physical destination named "{3}", in the distributed destination member "{2}", in the distributed destination "{1}", in the module "{0}" does not exist.

Cause: An attempt was made by a distributed destination member to reference a destination that does not exist. The physical destination referenced to by a distributed destination must already exist.

Action: Create the physical destination before referring to it, or create the physical destination in the same edit session as the creation of the distributed destination member.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045069: The JMS module entity named "{2}" of type "{1}" does not exist in the JMSSystemResource "{0}".

Cause: An attempt was made to reference a JMS module entity that does not exist in the specified JMSSytemResource.

Action: Create the JMS module entity in the specified JMSSystemResource before referring to it.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045070: The configuration entity named "{2}" of type "{1}" does not exist in the domain "{0}".

Cause: An attempt was made to reference a configuration entity that does not exist in the specified domain.

Action: Create the configuration entity in the specified domain before referring to it.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045071: The JMS module entity named "{2}" of type "{1}" cannot be created in JMSSystemResource "{0}".

Cause: The JMS module entity creation using the the JMSModuleHelper API failed. See the accompanying exception for details.

Action: Resolve the problem identified by the accompanying exception, and retry the operation.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045072: The configuration entity named "{2}" of type "{1}" cannot be created in domain "{0}".

Cause: The configuration entity creation using the JMSModuleHelper API failed. See the accompanying exception for details.

Action: Resolve the problem identified by the accompanying exception, and retry the operation.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045073: The JMS module entity named "{2}" of type "{1}" cannot be deleted from JMSSystemResource "{0}".

Cause: The JMS module entity deletion using the JMSModuleHelper API failed. See the accompanying exception for details.

Action: Resolve the problem identified by the accompanying exception, and retry the operation.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045074: The configuration entity named "{2}" of type "{1}" cannot be deleted from the domain "{0}".

Cause: The configuration entity deletion using the JMSModuleHelper API failed. See the accompanying exception for details.

Action: Resolve the problem identified by the accompanying exception, and retry the operation.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045075: The JMS module managed entity named "{2}" of type "{1}" cannot be found in the JMSSytemResource "{0}" for modification.

Cause: The JMS module entity modification using the JMSModuleHelper API failed. See the accompanying exception for details.

Action: Resolve the problem identified by the accompanying exception, and retry the operation.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045076: An attempt was made to find and modify a JMS module entity named "{2}", of type "{1}", from the JMSSystemResource "{0}" using a null modifier.

Cause: The JMSEntityModifier argument for the findAndModifyEntity() helper API cannot be null.

Action: Use a valid weblogic.jms.extensions.JMSEntityModifer implementation as the modifier argument.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045077: The destination named "{0}" on the JMS server "{1}" would have caused the JMS server not to boot because the destination StoreEnabled value is true, but the JMS server does not have a store.

Cause: This configuration does not work in older releases because the destination StoreEnabled value is true, but the JMS server does not have a store.

Action: Modify the configuration to remove this discrepency, and re-run the upgrade process. Either add a store to the JMS server or change the value of the StoreEnabled parameter on the destination.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045078: The destination named "{0}" on the JMS server "{1}" has a DeliveryParamsOverrides.DeliveryMode parameter set to persistent, but the JMS server does not have a store.

Cause: Messages cannot be made persistent on this JMS server because it does not have a store.

Action: Modify the configuration to remove this discrepency, and re-run the upgrade process. Either add a store to the JMS server or change the value of the DeliveryParamsOverrides.DeliveryMode parameter.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045079: An attempt was made to send a persistent message to the destination "{0}" hosted on the JMS server "{1}". This JMS server does not have a store, so the quality of service requested is not available.

Cause: An attempt was made to send a persistent message to a destination hosted by a JMS server that does not have a store. Since the message cannot be persisted, this message cannot be sent at the required quality of service.

Action: There is a parameter on the JMS server called "AllowsPersistentDowngrade". If this parameter is set to true, then persistent messages sent to this JMS server will be downgraded to non-persistent.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045080: The flow steps value {1} is larger than the flow interval value {2} in the connection factory "{0}". The flow steps value must be less than or equal to the flow interval value.

Cause: This is an invalid configuration. The flow steps value must be less than the entire flow interval.

Action: Modify the configuration of the connection factory to have the flow steps value be less than or equal to the flow interval.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045081: The SessionsMaximum attribute of a JMSSessionPoolMBean has the bad value {0}. The value should be -1 or a positive integer.

Cause: This is an invalid configuration.

Action: Modify the configuration of the JMSSessionPoolMBean.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045082: An unexpected naming exception occurred while binding the destination "{0}" to the JNDI name "{1}".

Cause: The naming exception should contain more information about why this operation failed.

Action: See the attached naming exception message, which should have more information about why this operation failed.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045083: An unexpected naming exception occurred while binding the destination "{0}" to the JNDI name "{1}" to the local JNDI context.

Cause: The naming exception should contain more information about why this operation failed.

Action: See the attached naming exception, which should have more information about why this operation failed.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045084: An unexpected naming exception occurred while binding the destination "{0}" to the JNDI name "{1}" to the application JNDI context.

Cause: The naming exception should contain more information about why this operation failed.

Action: See the attached naming exception, which should have more information about why this operation failed.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045085: Could not find a license for JMS. Contact Oracle to obtain a license.

Cause: A license for JMS was not obtained.

Action: Contact Oracle to obtain a license.
Level: 1

Type: WARNING

Impact: JMSExceptions

BEA-045086: The jms-system-resource cannot have the name interop-jms.

Cause: An attempt was made to define a jms-system-resource with the name interop-jms.

Action: Do not attempt to define a jms-system-resource element in the config.xml file with the name interop-jms.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045087: The JMS deployment "{0}" has the descriptor file name "{1}", which is reserved for internal use only.

Cause: An attempt was made to define a JMS deployment with the reserved file name "interop-jms.xml". This name is reserved by the system for use as the interop module.

Action: Do not attempt to define a JMS deployment with the reserved name "interop-jms.xml" as its file name.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045088: The JMS module descriptor file "{1}" used by the JMS system resource "{0}" is illegal. Either the descriptor file name does not end with -jms.xml or the descriptor is being used by another JMS system resource in the configuration.

Cause: An attempt was made to define a JMS system resource with the illegal descriptor file name.

Action: Do not attempt to define a jms-system-resource element in the config.xml file with the illegal descriptor file name.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045089: SAF error destination {2} of {1} is targeted to a different subdeployment from {0}.

Cause: The configuration was invalid.

Action: Correct the deployment descriptor.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045090: The error handling {1} configured for {0} does not exist in the module.

Cause: The configuration was invalid.

Action: Correct the deployment descriptor.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045091: One of the target ("{1}") of the subdeployment "{2}" for the imported destinations "{0}" is not a legal target type.

Cause: The configuration was invalid.

Action: Correct the configuration.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045092: Imported destinations "{0}": its subdeployment is targeted to a target ("{1}"), which is a receiving-only SAF agent.

Cause: The configuration was invalid.

Action: Correct the configuration.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045093: A UDQ named "{0}" was found in the JMS interop module. UDQs were not available prior to the 9.0 release of WebLogic Server, and therefore cannot be in the JMS interop module. Create another JMS module and put the UDQ in that module.

Cause: An invalid entity type was found in the JMS module that handles interoperating clients. This element should be placed into a different JMS module.

Action: Place the entity into another JMS module, and either deploy that module as a system resource or as a deployable resource.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045094: A UDT named "{0}" was found in the JMS interop module. UDTs were not available prior to the 9.0 release of WebLogic Server, and therefore cannot be in the JMS interop module. Create another JMS module and put the UDT in that module.

Cause: An invalid entity type was found in the JMS module that handles interoperating clients. This element should be placed into a different JMS module.

Action: Place the entity into another JMS module, and either deploy that module as a system resource or as a deployable resource.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045095: An SAF imported destinanation named "{0}" was found in the JMS interop module. SAF imported destinations were not available prior to the 9.0 release of WebLogic Server, and therefore cannot be in the JMS interop module. Create another JMS module and put the SAF imported destinations in that module.

Cause: An invalid entity type was found in the JMS module that handles interoperating clients. This element should be placed into a different JMS module.

Action: Place the entity into another JMS module, and either deploy that module as a system resource or as a deployable resource.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045096: An SAF remote context named "{0}" was found in the JMS interop module. SAF remote contexts were not available prior to the 9.0 release of WebLogic Server, and therefore cannot be in the JMS interop module. Create another JMS module and put the SAF remote context in that module.

Cause: An invalid entity type was found in the JMS module that handles interoperating clients. This element should be placed into a different JMS module.

Action: Place the entity into another JMS module, and either deploy that module as a system resource or as a deployable resource.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045097: An SAF error handlings named "{0}" was found in the JMS interop module. SAF error handlings were not available prior to the 9.0 release of WebLogic Server, and therefore cannot be in the JMS interop module. Create another JMS module and put the SAF error handlings in that module.

Cause: An invalid entity type was found in the JMS module that handles interoperating clients. This element should be placed into a different JMS module.

Action: Place the entity into another JMS module, and either deploy that module as a system resource or as a deployable resource.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045098: There is a JMS system resource and an application deployment both named "{0}". The names of all JMS system resources and all application deployments must be different.

Cause: Both a JMS system resource and an application deployment have the same name. This would cause similarly named resources in a JMS module descriptor file to have conflicting runtime names, and therefore is not allowed.

Action: Change the name of either the JMS system resource or application deployment so that there is no name conflict.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045099: An attempt was made to create a temporary destination. However, no JMS server in the cluster is able to host temporary destinations. Ensure that at least one of the JMS servers in the cluster has the HostingTemporaryDestinations parameter set to true (which is the default).

Cause: None of the JMS servers in the cluster are available for hosting temporary destinations.

Action: Modify the HostingTemporaryDestinations parameter on at least one JMS server in the cluster. Note that in releases prior to 9.0, the default for the ability to host temporary destinations was false, while in 9.0 and beyond, the default for the ability to host temporary destinations is true.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045100: The createQueue or createTopic call was made with a null or zero length destination name.

Cause: The createQueue or createTopic call must be made with the name of a destination to find.

Action: Do not pass a null or zero length string to createQueue or createTopic.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045101: The destination name passed to the createTopic or createQueue "{0}" is invalid. If the destination name does not contain a "/" character, then it must be the name of a distributed destination that is available in the cluster to which the client is attached. If it does contain a "/" character, then the string before the "/" must be the name of a JMS server or a ".". The string after the "/" is the name of a the desired destination. If the "./" version of the string is used then any destination with the given name on the local WebLogic Server instance will be returned.

Cause: Either a distributed destination of the given name does not exist in the cluster to which the client is attached or the destination name passed to createTopic or createQueue does not contain a "/" character, or there is nothing before the "/" character.

Action: Ensure that the distributed destination is available on the same cluster where the client is located, or format the destination name string properly.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045102: A destination named "{0}" was not found on WebLogic Server instance "{1}".

Cause: An attempt was made to find a destination of a given name on a particular WebLogic Server instance. No destination of that name could be found on that WebLogic Server instance.

Action: It is possible that the createTopic or createQueue call was routed to a WebLogic Server instance that does not contain a destination with the given name. The set of WebLogic Server instances where this request can be routed can be controlled by using a connection factory that is only targeted to WebLogic Werver instances that have destinations of the desired name.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045103: While trying to find a topic or a queue, the specific JMS server requested could not be found. The linked exception may contain more information about the reason for failure.

Cause: A specific JMS server was requested by a call to createTopic or createQueue. However, the system could not locate the JMS server of that name.

Action: The WebLogic Server instance on which that JMS server is targeted may be down. The JMS server may be suspended. Check on the status of the JMS server and also on the status of the communication between the servers in the cluster. Check the linked exception for more information about the cause of this failure.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045104: While trying to find a topic or a queue, the specific JMS server requested could not be found.

Cause: A specific JMS server was requested by a call to createTopic or createQueue. However, the system could not locate the JMS server of that name.

Action: Ensure that the JMS server requested exists in the configuration of the cluster to which the client is attached.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045105: While trying to find a topic or a queue, communication failed with the specific JMS server requested. The linked exception may contain more information about the reason for failure.

Cause: A specific JMS server was requested by a call to createTopic or createQueue. However, the system could not communicate with the JMS server of that name.

Action: The WebLogic Server instance on which that JMS server is targeted may be down. The JMS server may be suspended. Check on the status of the JMS server and also on the status of the communication between the servers in the cluster. Check the linked exception for more information about the cause of this failure.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045106: A destination named "{0}" was found. However, the requested destination was of type "{1}", and the destination found was not of that type.

Cause: Either the user called createTopic and the destination found was a queue or the user called createQueue and the destination found was a topic.

Action: Ensure that the destination name requested is of the correct type.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045107: A communication failure occurred while attempting to remove a durable subscription. The linked exception may contain more details about the cause of the failure.

Cause: While attempting to remove a durable subscription a communication failure occurred.

Action: Check on the status of WebLogic Server instance where the destination which the durable subscription refers to resides. Check the linked exception for more information about the cause of this failure.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045108: The JMS system does not understand request ID {0}.

Cause: An invalid request ID was presented to the front end manager.

Action: If this condition persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045109: A foreign server named "{0}" was found which does not have a connection URL specified. However, it contains a "{2}" named "{1}" that has the same local and remote JNDI name value "{3}". This is an invalid configuration and is not allowed.

Cause: The user has configured a foreign server without a connection URL and has either a foreign connection factory or a foreign destination with both the local and remote JNDI name matching.

Action: Ensure that either the foreign server has a connection URL to the foreign server or that the local and remote JNDI names are different.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045110: The JMS resource named "{0}" has incorrect targeting information. This resource has the default-targeting-enabled attribute set to true and has a valid sub-deployment-name value specified.

Cause: A JMS resource cannot have both default targeting enabled and a subdeployment name specified.

Action: Ensure that either the default targeting is enabled or that the valid subdeployment name is specified.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045111: The JMS resource named "{0}" has incorrect targeting information. A JMS physical destination cannot have the default-targeting-enabled attribute set.

Cause: A JMS physical destination cannot have the default-targeting-enabled attribute set.

Action: Ensure that the default-targeting-enabled attribute is not set for the physical destinations.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045112: The flow minimum value {1} is larger than or equal to the flow maximum value {2} in connection factory "{0}". The flow minimum value must be less than the flow maximum value.

Cause: This is an invalid configuration. The flow minimum value must be less than the flow maximum value.

Action: Modify the configuration of the connection factory to have the flow minimum value be less than the flow maximum value.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045113: JMS distributed destination forward request denied for the destination named "{1}". Reason "{0}".

Cause: JMS distributed destinations may not have been fully initialized.

Action: If forwarding does not begin after a few minutes, contact My Oracle Support.
Level: 1

Type: NOTIFICATION

Impact: JMSExceptions

BEA-045114: Failed to unsubscribe the subscription "{0}", client ID "{1}". This connection has a client ID policy of UNRESTRICTED and cannot unsubscribe a durable subscription without a topic object.

Cause: An attempt was made to unsubscribe a durable subscription using the standard javax.jms.Session.unsubscribe(String name) method from a connection that has a client ID policy of UNRESTRICTED.

Action: Use the weblogic.jms.extensions.WLSession.unsubscribe(Topic topic, String name) API to unsubscribe a durable subscription from a connection that has a client ID policy of UNRESTRICTED. If using a pre-AS11gR1PS3 Java client, upgrade to a AS11gR1PS3 client. If using a non-Java client, clean up the durable subscription from the Administration Console or use WebLogic Scripting Tool (WLST) commands or scripts.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045115: The SubDeploymentMBean {0} in JMS Module {1} can only be targeted to a single non-clustered JMSServer as it contains a standalone queue, topic or quota that can only be targeted to a single non-clustered JMSServer.

Cause: The SubDeploymentMBean of the given name cannot be targeted to anything but a single non-clusterd JMSServer.

Action: Modify the target of the subdeployment so that it contains only a single non-clustered JMSServer.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045116: The Replicated Distributed Topic (RDT) cannot have its members hosted by a cluster targeted JMSServer. The RDT named {0} in JMS Module {2} has its subdeployment {1} targeted to the Clustered JMSServer {3}.

Cause: The RDT named {0} in JMS Module {2} has its subdeployment {1} targeted to the Clustered JMSServer {3}.

Action: Modify the target of the subdeployment so that it does not contain a cluster targeted JMSServer.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045117: An SAFAgent (store-and-forward agent) cannot be targeted to cluster {0} which has dynamic servers enabled (dynamic servers exist in clusters where the MaximumDynamicServerCount is greater than zero). Instead of using cluster targeting, SAFAgents can be targeted directly to one or more of non-dynamic WebLogic Servers or any one of their migratable target counterparts.

Cause: An SAFAgent cannot be targeted to cluster {0} which has dynamic servers enabled (dynamic servers exist in clusters where the MaximumDynamicServerCount is greater than zero). Instead of using cluster targeting, SAFAgents can be targeted directly to one or more of non-dynamic WebLogic Servers or any one of their migratable target counterparts.

Action: Modify the target of the SAFAgent such that it is either targeted directly to one or more non-dynamic WebLogic Servers or any one of their migratable target counterparts.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045118: MaximumDynamicServerCount cannot be set higher than 0 for the DynamicServers {0} in cluster {1}. One or more SAFAgents (store-and-forward agents) are currently targeted to the same cluster, and SAFAgents are not supported for a cluster in which dynamic servers are enabled. Instead of using cluster targeting, SAFAgents can be targeted directly to one or more non-dynamic WebLogic Servers or any one of their migratable target counterparts.

Cause: MaximumDynamicServerCount cannot be set higher than 0 for the DynamicServers {0} in cluster {1}. One or more SAFAgents are currently targeted to the same cluster, and SAFAgents are not supported for a cluster in which dynamic servers are enabled. Instead of using cluster targeting, SAFAgents can be targeted directly to one or more non-dynamic WebLogic Servers or any one of their migratable target counterparts.

Action: Modify the target of the SAFAgent or SAFAgents that are targeted to this cluster such that they are either targeted directly to one or more of non-dynamic WebLogic Servers or any one of their migratable target counterparts.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045119: A JMS message send request failed for distributed destination {0}. Neither Unit-of-Order (UOO) nor Unit-of-Work (UOW) messages are supported for distributed destinations that have a member hosted by a clustered JMS Server. Distributed destination {0} has one or more of its members hosted by a clustered JMS server.

Cause: A JMS message send request failed for distributed destination {0}. Neither Unit-of-Order (UOO) nor Unit-of-Work (UOW) messages are supported for distributed destinations that have a member hosted by a clustered JMS Server. Distributed destination {0} has one or more of its members hosted by a clustered JMS server.

Action: To produce either UOO or UOW messages on a distributed destination, either use a distributed destination that is hosted only on one or more non-dynamic JMS servers, or send messages directly to a member of the distributed destination. Note that when an application sends messages directly to a distributed destination member, the application is responsible for making sure that all messages with the same UOO/UOW string are sent to the same distributed destination. This ensures strictly ordered message processing for the given UOO/UOW.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-050000: {0} is an obsolete property. Use {1} to create the context instead.

Cause: Property {0} is obsolete. However, this property name can still be used to retrieve the property value.

Action: Use property {1} instead of {0} in the future.
Level: 1

Type: WARNING

Impact: JNDI

BEA-050001: WLContext.close() was called in a different thread than the one in which it was created.

Cause: The threads used to create and close the context are different. As a result, the context entries associated with the creating thread might not be cleaned up.

Action: Close the context in the creating thread.
Level: 1

Type: WARNING

Impact: JNDI

BEA-050002: Cannot replicate the object that is bound in the JNDI under the name {0}.

Cause: A non-serializable object cannot be serialized.

Action: If the object was not intended to be replicated, set the replicate bindings to false. If the object should be replicated to all nodes in the cluster, ensure that the object is serializable or externalizable.
Level: 1

Type: ERROR

Impact: JNDI

BEA-050003: Cannot create initial context. Reason: {0}

Cause: Initial context cannot be created.

Action: Check the exception in the message body.
Level: 1

Type: ERROR

Impact: JNDI

BEA-050004: Unable to bind. Reason: {0}

Cause: This was unable to bind.

Action: Check the exception in the message body.
Level: 1

Type: ERROR

Impact: JNDI

BEA-050005: Unable to unbind. Reason: {0}

Cause: This was unable to unbind.

Action: Check the exception in the message body.
Level: 1

Type: ERROR

Impact: JNDI

BEA-050006: An attempt was made to look up the versioned object "{0}" from an external client or another application. This can potentially cause in-flight work of the application version not being tracked properly, and thus, be retired prematurely.

Cause: An attempt was made to look up the versioned object "{0}" from an external client or another application. This can potentially cause in-flight work of the application version not being tracked properly, and thus, be retired prematurely.

Action: Ensure that the possibility of premature retirement of the application version is either tolerated or handled properly. To disable this check, set the JNDI environment property as specified by weblogic.jndi.WLContext.ALLOW_EXTERNAL_LOOKUP to "true" when performing lookup of the versioned object.
Level: 1

Type: WARNING

Impact: JNDI

BEA-050007: An attempt was made to look up the non-versioned global resource "{0}" from an application version "{1}". This can potentially cause conflict of the global resource usages among multiple application versions.

Cause: An attempt was made to look up the non-versioned global resource "{0}" from an application version "{1}". This can potentially cause conflict of the global resource usages among multiple application versions.

Action: Ensure that usages of the global resource by multiple application versions do not conflict. To disable this check, set the JNDI environment property as specified by weblogic.jndi.WLContext.ALLOW_GLOBAL_RESOURCE_LOOKUP to "true" when performing lookup of the global resource.
Level: 1

Type: WARNING

Impact: JNDI

BEA-055001: Invalid time-to-deliver, must be >= -1

Cause: The time-to-deliver parameter passed to setTimeToDeliver was invalid.

Action: Change the code to pass a time-to-deliver parameter that is >= -1.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055002: Cannot convert {0} to a boolean.

Cause: An object that was not null, not a boolean, and not a string could not be converted to a boolean value.

Action: Ensure that the object passed in is either a boolean or a string.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055003: Cannot convert null to a byte.

Cause: The null object cannot be converted to a byte value

Action: Avoid passing null where a byte value is expected
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055004: Cannot convert {0} to a byte.

Cause: An object that was not null, not a byte, and not a string could not be converted to a byte value

Action: Ensure that the object passed in is either a byte or a string.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055005: Cannot convert null to a short.

Cause: The null object cannot be converted to a short value.

Action: Avoid passing null where a short value is expected.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055006: Cannot convert {0} to a short.

Cause: An object that was not null, not a short, and not a string could not be converted to a short value.

Action: Ensure that the object passed in is either a short or a string.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055007: Could not serialize object.

Cause: An object could not be serialized. The linked exception may contain more details.

Action: See the linked exception which may contain more details.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055008: Invalid RedeliveryLimit, must be >= -1.

Cause: The RedeliveryLimit parameter passed to setRedeliveryLimit was invalid.

Action: Change the code to pass a RedeliveryLimit parameter that is >= -1.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055009: Invalid SendTimeout, must be >= 0

Cause: The SendTimeout parameter passed to setSendTimeout was invalid.

Action: Change the code to pass a SendTimeout parameter that is >= 0.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055014: Error sending message

Cause: The linked exception will contain more details concerning the failure to send the message.

Action: The action will depend on the error that occurred. More information about the specific error that occurred can be found in the linked exception.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055015: Invalid DeliveryMode

Cause: The DeliveryMode parameter passed to setDeliveryMode was invalid.

Action: Change the code to pass a valid DeliveryMode value.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055016: Invalid Priority

Cause: The Priority parameter passed to setPriority was invalid.

Action: Change the code to pass a valid Priority value.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055017: Durable connection consumers are not supported.

Cause: The system does not support durable connection consumers.

Action: Do not attempt to create a durable connection consumer.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055018: QueueSessions do not support multicast.

Cause: The MULTICAST_NO_ACKNOWLEDGE flag was set in createQueueSession.

Action: Do not use MULTICAST_NO_ACKNOWLEDGE when creating a QueueSession.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055019: Duplicate session

Cause: The cause is unknown.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055021: ClientID is null

Cause: ClientID is null in a call to setClientID.

Action: Do not use null in a call to setClientID.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055022: Zero length clientID

Cause: The clientID passed to setClientID was zero length.

Action: The clientID must not be zero length.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055023: Invalid value for messagesMaximum, {0}

Cause: The value given for messagesMaximum in createConnectionConsumer is invalid.

Action: Change the code to pass a valid messagesMaximum value.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055024: No such method {0}

Cause: An internal error occurred.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055025: Invalid messagesMaximum value

Cause: The messagesMaximum parameter passed to setMessagesMaximum was invalid.

Action: Change the code to pass a valid messagesMaximum value.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055026: Invalid overrunPolicy value, {0}

Cause: The overrun policy passed to setOverrunPolicy is invalid.

Action: Change the code to pass a valid overrun policy value.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055027: Invalid redelivery delay, must be >= -1

Cause: The redeliveryDelay parameter passed to setRedeliveryDelay was invalid.

Action: Change the code to pass a valid redeliveryDelay value.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055028: Name must not be null.

Cause: The name parameter passed to createDurableSubscriber was null.

Action: Change the code to pass a valid name to createDurableSubscriber.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055029: Name must not be an empty string.

Cause: The name parameter passed to createDurableSubscriber had a length of zero.

Action: Change the code to pass a valid name to createDurableSubscriber.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055030: This topic does not support durable subscriptions.

Cause: Durable subscribers are not supported on Distributed Topics and no subscribers at all are supported on SAF topics

Action: Avoid attempting to create a durable subscriber on a distributed topic or do not create a subscriber on an SAF topic.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055031: This connection does not have a clientID.

Cause: Unsubscribe was called on a connection without a clientID.

Action: Avoid attempting to unsubscribe a connection with no clientID
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055032: An attempt was made to create a named consumer ({0}) on a connection with no clientID.

Cause: An attempt was made to create a named consumer on a connection with no clientID.

Action: Avoid attempting to create a named consumer on a connection with no clientID.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055033: Queues do not support multicast.

Cause: Queues do not support multicast.

Action: Avoid attempting to create a multicast consumer on a queue
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055034: Topic {0} does not support multicast.

Cause: An attempt was made to create a multicast consumer on a topic that does not support multicast.

Action: Avoid attempting to create a multicast consumer on the given topic.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055035: Cannot open multicast socket, {0}.

Cause: An attempt was made to open a multicast socket and failed. The reason for the failure may be in the exception

Action: For more details, check the printed exception on the failure to open the multicast socket.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055036: Cannot join multicast group ({0}) {1}

Cause: An attempt was made to join a multicast group and failed. The reason for failure may be in the exception.

Action: For more details, check the printed exception on the failure to join the multicast group.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055037: Subscription {0} is in use.

Cause: Two subscriptions with the same name are not allowed.

Action: Avoid attempting to use a subscription name more than once. If necessary, unsubscribe the previous subscription
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055038: An unexpected response ({0}) was received from the server.

Cause: An internal protocol error has occurred.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055039: A system error has occurred. The error is {0}.

Cause: The cause of this error may be contained in the printed exception.

Action: The action will depend on the error that has occurred. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055040: Subscription {0} is in use.

Cause: An attempt was made to remove the named subscription while the subscription was in use.

Action: Avoid attempting to remove a subscription that is currently in use.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055041: Cannot leave multicast group ({0}) {1}

Cause: An attempt was made to leave a multicast group and failed. The reason for failure may be in the exception.

Action: For more details, check the printed exception on the failure to leave the multicast group.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055042: No such method {0} for class {1}

Cause: An internal error has occurred.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055043: No such method {0} for class {1}

Cause: An internal error has occurred.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055044: Multicast sessions do not support synchronous receives.

Cause: An attempt was made to do a synchronous receive on a multicast consumer.

Action: Avoid attempting to make a synchronous receive with a multicast consumer.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055045: An invalid value ({0}) for timeout was specified.

Cause: The timeout given to a receive call is invalid. Timeout values must be positive.

Action: Change the code so that it does not pass a negative number into a receive call.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055046: A listener already exists.

Cause: A call to receive cannot be made if the consumer already has a listener.

Action: Avoid attempting to call receive if a listener already exists for the consumer.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055047: No such method {0}

Cause: An internal error occurred.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055048: Multicast selectors are not supported in the thin client.

Cause: Multicast selectors are not supported in the thin client.

Action: If selectors are required, avoid using the JMS thin client. If selectors are not required, avoid using them while using the thin client.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055049: Internal error {0}.

Cause: An internal error occurred. More detail about the error can be found in the exception.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055050: Internal error {0}

Cause: An internal error occurred. More detail about the error can be found in the exception.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055051: Internal error {0}

Cause: An internal error occurred. More detail about the error can be found in the exception.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055052: Invalid selector {0}

Cause: An error occurred while parsing a selector. The printed exception should have more detail.

Action: The course of action will depend on the nature of the error. Use a well-formed selector.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055053: Error creating connection to the server: {0}.

Cause: The printed exception may have information regarding the cause of this failure.

Action: The course of action will depend on the error printed out in the exception.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055054: Error finding dispatcher: {0}.

Cause: An internal error has occurred.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055055: No transaction

Cause: A call to commit was made on a session but there is no current transaction.

Action: Avoid calling commit on a session that is not currently in a transaction.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055056: Error committing session

Cause: An error occurred while committing an XA session.

Action: Examine the transaction logs to see what occurred to the transaction
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055057: No transaction

Cause: A call to rollback was made on a session but there is no current transaction.

Action: Do not call rollback on a session that is not currently in a transaction.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055058: Error committing session

Cause: An error occurred while committing an XA session.

Action: Examine the transaction logs to see what occurred to the transaction.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055059: getXAResource can be called only from the server.

Cause: A call to getXAResource was made from a client JVM; getXAResource is not supported in the client.

Action: Avoid calling getXAResource from a client JVM.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055060: No transaction.

Cause: A call to commit was made on a session but there is no current transaction.

Action: Avoid calling commit on a session that is not currently in a transaction.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055061: No transaction.

Cause: A call to rollback was made on a session but there is no current transaction.

Action: Avoid calling rollback on a session that is not currently in a transaction.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055062: This session is transacted.

Cause: A call to recover was made on a transacted session.

Action: Avoid calling recover on a transacted session. Use rollback instead.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055063: This session has consumer listeners.

Cause: The session on which setMessageListener was called already has consumer listeners.

Action: Avoid calling setMessageListener on a session that already has consumer listeners.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055064: Unsupported topic operation on a queue session

Cause: A call to createTopic was made on a QueueSession.

Action: Avoid calling createTopic on a QueueSession.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055065: Unsupported topic operation on a queue session

Cause: A call to createDurableSubscriber was made on a QueueSession.

Action: Avoid calling createDurableSubscriber on a QueueSession.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055066: Unsupported topic operation on a queue session

Cause: A call to createTemporaryTopic was made on a QueueSession.

Action: Avoid calling createTemporaryTopic on a QueueSession.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055067: Unsupported topic operation on a queue session

Cause: A call to unsubscribe was made on a QueueSession.

Action: Avoid calling unsubscribe on a QueueSession.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055068: There is no subscription from which to unsubscribe.

Cause: The user called unsubscribe on a session that does not have a subscription.

Action: Avoid calling unsubscribe on a session that does not have a subscription.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055069: Unsupported queue operation on a topic session

Cause: A call to createQueue was made on a TopicSession.

Action: Avoid calling createQueue on a TopicSession.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055070: Unsupported queue operation on a topic session

Cause: A call to createBrowser was made on a TopicSession.

Action: Avoid calling createBrowser on a TopicSession.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055071: Unsupported queue operation on a topic session

Cause: A call to createTemporaryQueue was made on a TopicSession.

Action: Avoid calling createTemporaryQueue on a TopicSession.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055072: Wrong connection for this temporary destination

Cause: An attempt was made to call createConsumer on an invalid connection from a temporary destination.

Action: Create consumers using the same connection that was used to create the temporary destination.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055073: Dropping new message

Cause: A new message is being dropped because too many messages have arrived.

Action: Either consume messages faster or produce messages slower for this session.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055074: Dropping old message

Cause: An old message is being dropped because too many messages have arrived.

Action: Either consume messages faster or produce messages slower for this session.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055075: It is possible that the client is malfunctioning: a RuntimeException was thrown from its onMessage method.

Cause: The onMessage method of the client threw a RuntimeException.

Action: Modify the code such that the RuntimeException does not occur from within the body of the user code. This warning is required by section 4.5.2 of the JMS Specification.
Level: 1

Type: WARNING

Impact: JMSClientExceptions

BEA-055076: The session is closed.

Cause: An operation was attempted on a closed session.

Action: Avoid attempting this operation on a closed session.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055077: Cannot override producer destination.

Cause: A call to send with a non-null destination was made on a producer that is already bound to a destination.

Action: Avoid calling send with a non-null destination on a producer that is already bound to a destination.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055078: Cannot override producer destination

Cause: A call to send with a non-null destination was made on a producer that is already bound to a destination.

Action: Avoid calling send with a non-null destination on a producer that is already bound to a destination.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055079: Must provide destination to send to

Cause: There is no destination to send to.

Action: Use the version of send that has a destination or bind a destination to the producer before calling send.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055080: Must provide destination to send to

Cause: There is no destination to send to.

Action: Use the version of send that has a destination or bind a destination to the producer before calling send.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055081: Unsupported topic operation on a queue session

Cause: A call to createDurableConnectionConsumer was made on a QueueConnection.

Action: Avoid calling createDurableConnectionConsumer on a QueueConnection.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055082: The connection is closed.

Cause: The connection has been closed. Only a few operations are valid on a closed connection.

Action: Avoid calling any illegal operations on a closed queue connection.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055083: Cannot set clientid to {0}. The client ID is already set to {1}

Cause: The clientID {1} is already set on this connection. The clientID cannot be set to {0}

Action: Avoid attempting to set a clientID on a connection that already has one.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055084: A connection consumer works only on the server.

Cause: A connection consumer can be created only in the same JVM in which the server is running.

Action: Avoid attempting to create a connection consumer on a JVM that is not running the server.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055085: Destination is null.

Cause: In a call to createConnectionConsumer or createConsumer, the destination parameter was null.

Action: Avoid using null for the destination in a call to createConnectionConsumer or createConsumer.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055086: Foreign destination

Cause: Foreign destinations are not supported when creating connectionConsumers.

Action: Avoid using a foreign destination in a call to createConnectionConsumer.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055087: The session already has a message listener.

Cause: A consumer may not have an individual message listener if its parent session already has one defined.

Action: Avoid attempting to set a message listener for a consumer if the session already has a listener defined.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055088: The consumer is closed.

Cause: The consumer has been closed. Only a few operations are valid on a closed consumer.

Action: Avoid calling any illegal operations on a closed consumer.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055089: Destination is null.

Cause: In a call to send, the destination parameter was null.

Action: Avoid using null for the destination in a call to send.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055090: Foreign destination

Cause: Foreign destinations are not supported when sending.

Action: Avoid using a foreign destination in a call to send.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055091: Destination {0} must be a queue.

Cause: An attempt was made to publish to a queue.

Action: Avoid using publish to a queue. Use send instead.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055092: Destination {0} must be a topic.

Cause: An attempt was made to send to a topic.

Action: Avoid using send to a topic. Use publish instead.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055093: Error converting foreign message

Cause: An I/O exception occurred while converting a foreign message. The cause of the failure may be contained in the linked exception.

Action: Examine the linked I/O exception.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055094: The producer is closed.

Cause: The producer has been closed. Only a few operations are valid on a closed producer.

Action: Avoid calling any illegal operations on a closed producer.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055095: The browser is closed.

Cause: The browser has been closed. Only a few operations are valid on a closed browser.

Action: Avoid calling any illegal operations on a closed browser.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055096: Cannot convert null to a char.

Cause: The null object cannot be converted to a char value.

Action: Avoid passing null where a char value is expected.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055097: Cannot convert {0} to a char.

Cause: An object that was not null, not a character, and not a string could not be converted to a char value.

Action: Ensure that the object passed in is either a character or a string.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055098: Cannot convert null to an int.

Cause: The null object cannot be converted to an int value.

Action: Avoid passing null where an int value is expected.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055099: Cannot convert {0} to an int.

Cause: An object that was not null, not an integer, and not a string could not be converted to an int value.

Action: Ensure that the object passed in is either an intenger or a string.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055100: Cannot convert null to a long.

Cause: The null object cannot be converted to a long value.

Action: Avoid passing null where a long value is expected.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055101: Cannot convert {0} to a long.

Cause: An object that was not null, not a long, and not a string could not be converted to a long value.

Action: Ensure that the object passed in is either a long or a string.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055102: Cannot convert null to a float

Cause: The null object cannot be converted to a float value.

Action: Avoid passing null where a float value is expected.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055103: Cannot convert {0} to a float

Cause: An object that was not null, not a float, and not a string could not be converted to a float value.

Action: Ensure that the object passed in is either a float or a string.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055104: Cannot convert null to a double

Cause: The null object cannot be converted to a double value.

Action: Avoid passing null where a double value is expected.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055105: Cannot convert {0} to a double.

Cause: An object that was not null, not a double, and not a string could not be converted to a short value.

Action: Ensure that the object passed in is either a double or a string.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055106: A byte[] cannot be converted to a string.

Cause: A byte[] cannot be converted to a string.

Action: Avoid passing a byte array that needs to be converted to a string.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055107: Cannot convert {0} to a byte[].

Cause: The given object could not be converted to a byte[].

Action: Ensure that the object passed in can be converted to a byte array.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055108: Read past end of message

Cause: An attempt was made to read past the end of a StreamMessage. A linked EOFException may contain more information

Action: Avoid attempting to read past the end of a StreamMessage. See the linked EOFException for more information.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055109: Error reading from stream

Cause: There was an error reading the stream from a StreamMessage. A linked IOException may contain more information.

Action: See the linked IOException for more information.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055110: Error writing to stream

Cause: There was an error writing to the stream of a StreamMessage. A linked IOException may contain more information.

Action: See the linked IOException for more information.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055111: Cannot convert from {0} to {1}

Cause: A StreamMessage was unable to convert one type to another.

Action: Ensure that the two types are compatible. Avoid attempting to convert incompatible types
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055112: Error reading from stream

Cause: There was an error reading the stream from a StreamMessage. A linked ArrayIndexOutOfBoundsException may contain more information.

Action: See the linked ArrayIndexOutOfBoundsException for more information.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055113: Error reading from stream

Cause: There was an error reading the stream from a StreamMessage. A linked ArrayStoreException may contain more information.

Action: See the linked ArrayStoreException for more information.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055114: There was an eeror when deserializing an object. Some typical reasons for failure are: missing application class, application class version mismatch, or Java objects not being supported.

Cause: There was an error deserializing an object. A linked IOException may have more details.

Action: See the linked IOException for more details.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055115: Error deserializing an object

Cause: There was an error deserializing an object. A linked ClassNotFoundException may have more details.

Action: See the linked ClassNotFoundException for more details.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055116: Internal error unknown message type {0}

Cause: This error should never happen.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055117: Invalid delivery mode {0}

Cause: The delivery mode passed into setJMSDeliveryMode is invalid

Action: Change the code so that it calls setJMSDeliveryMode with a valid delivery mode.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055118: Invalid redelivery limit, must be >= -1

Cause: The redelivery limit parameter passed to setJMSRedeliveryLimit was invalid.

Action: Change the code to pass a redelivery limit parameter that is >= -1.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055119: Invalid priority, {0}

Cause: The priority parameter passed to setJMSPriority was invalid.

Action: Change the code to pass a valid priority value.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055121: Invalid property name, "{0}"

Cause: The property name passed to setObjectProperty was invalid.

Action: Change the code to pass a valid property name.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055122: Property write attempted in READ mode.

Cause: An attempt was made to write a property but the message is read-only.

Action: Avoid attempting to write a property to a message in read-only mode.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055123: Invalid property value, {0}

Cause: The property value passed to setObjectProperty was invalid.

Action: Change the code to pass a valid property value.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055125: Unknown underlying stream type, cannot convert 6.0 class.

Cause: While attempting to read a message created by an older version of WebLogic Server, a failure occurred.

Action: It may not be possible to read the older version of the message. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055126: Stream is corrupted. Possible older version

Cause: While attempting to read a message created by an older version of WebLogic Server, a failure occurred.

Action: It may not be possible to read the older version of the message. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055127: Unsupported version

Cause: The version of the message being read is unsupported.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055128: Read attempted in WRITE mode.

Cause: An attempt was made to read a message in WRITE mode.

Action: Avoid attempting to read a message in WRITE mode.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055129: Write attempted in READ mode.

Cause: An attempt was made to write a message that is read-only.

Action: Avoid attempting to write to a message in read-only mode.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055130: Invalid data type: {0}

Cause: The class name given is not a valid data type. The type for setObject must be number, string, boolean, byte, character, or null.

Action: Pass one of the acceptable data types to setObject in a MapMessage.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055131: Illegal name: {0}

Cause: The given name is not legal. It is either null or of zero length.

Action: Pass a non-null or non-zero-length string as the name of a MapMessage element.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055132: Could not copy message.

Cause: The system could not copy a MapMessage. The linked IOException should contain more information about the nature of the error.

Action: Examine the linked exception to discover what caused the failure.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055133: Could not deserialize message.

Cause: The system could not deserialize a MapMessage. The linked IOException should contain more information about the nature of the error.

Action: Examine the linked exception to discover what caused the failure.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055134: Unsupported class version {0}. Expected a value between {1} and {2} inclusive.

Cause: While attempting to interoperate between different releases or service packs, an error occurred while attempting to serialize or deserialize an object. The version number of the object was not in the expected range. If {0} is larger than {1} then it is possible an attempt was made to access a newer JMS version than the current version. Otherwise a possible attempt has been made to interoperate with an unsupported older version of JMS.

Action: Ensure that the versions of Oracle products that are interoperating are supported. If the versions should be supported, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055135: Could not write object, expected simple type, but got class {0}

Cause: The given object class could not be written because it is not a simple type.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055136: Could not read object, unrecognized class code {0}.

Cause: An unknown class code was received. The object cannot be read.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055137: JMSProducerSendResponse versions {0}, {1} not compatible with peer: {2}

Cause: An interoperability error occurred.

Action: Only use versions of Oracle products that can interoperate with each other. If the versions being used should interoperate, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055138: Peer not compatible with DistributedDestinationImpl version {0}. Peer Major Version is less than 6.

Cause: An interoperability error occurred.

Action: Only use versions of Oracle products that can interoperate with each other. If the versions being used should interoperate, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055139: Invalid Temporary Destination

Cause: An attempt was made to delete an invalid temporary destination.

Action: Avoid attempting to delete invalid temporary destinations.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055140: Internal error or marshalling error, unknown destination type {0}

Cause: An unknown type was encountered when marshalling a destination.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055141: Destination is null.

Cause: While checking a destination type, the incoming destination was null.

Action: Avoid attempting to discover the type of a null destination.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055142: Foreign destination, {0}

Cause: While checking a destination type, the incoming destination was foreign.

Action: Avoid attempting to discover the type of a foreign destination.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055143: Destination must be a queue, {0}

Cause: The given destination must be a queue, but it is not a queue.

Action: Use the proper type of destination when checking types.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055144: Destination must be a topic, {0}

Cause: The given destination must be a topic, but it is not a topic.

Action: Use the proper type of destination when checking types.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055145: Unknown stream version: {0}

Cause: The given version number is invalid for a buffered stream.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055146: The stream cannot handle raw objects.

Cause: The stream is probably from an unintended source, such as a Web browser.

Action: Only connect to the Oracle product TCP port with a proper client. If the client is a proper client, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055147: Not implemented

Cause: readLine was called, but it has not been implemented.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055148: The stream cannot handle raw objects.

Cause: A raw object could not be written to the buffered stream.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055149: Attempt to read past end of message ({0})

Cause: The end of the BytesMessage was reached, but an attempt was made to read past it. {0} indicates where the attempt was made and will only be significant to My Oracle Support.

Action: Avoid attempting to read past the end of the BytesMessage.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055150: Error reading from stream ({0}).

Cause: The linked IOException will have more detail on the cause of the failure.

Action: Examine the linked exception to discover what caused the problem.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055151: Length ({0}) is negative.

Cause: In a call to readBytes, the length parameter is negative.

Action: Fix the code to ensure a negative length is not passed to readBytes.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055152: length ({0}) is greater than the length of the array ({1}).

Cause: In a call to readBytes, the length parameter is larger than the size of the bytes array to fill.

Action: Fix the code to ensure the length passed to readBytes is less than or equal to the length of the output array.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055153: Error writing to stream ({0}).

Cause: The linked IOException will have more detail on the cause of the failure.

Action: Examine the linked exception to discover what caused the problem.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055154: Invalid object type: {0}

Cause: The object passed to writeObject is not valid.

Action: Only send valid object types to writeObject. Example valid types include boolean, byte, short, and integer.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055155: Cannot forward message

Cause: Modified received messages are not supported when using forward methods.

Action: Avoid modifying a received message in a call to forward.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055156: Peer neither compatible with {0} or {1} or {2} or {3}. PeerInfo is {4}.

Cause: A version mismatch occurred in a message.

Action: This is an internal error that should not occur. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055157: Invalid compression threshold

Cause: The compression threshold was invalid.

Action: Change the code to pass a valid compression threshold.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055158: WebLogic Server JMS failed to decompress the message body.

Cause: The linked IOException will have more detail on the cause of the failure.

Action: Examine the linked exception to discover what caused the problem.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055159: Message consumer received a compressed message with unknown compression tag - {0}

Cause: Contact My Oracle Support.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055160: WebLogic Server JMS failed to deserialize the text message.

Cause: Contact My Oracle Support.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055161: Cannot forward foreign messages.

Cause: Foreign messages are not supported when using forward methods.

Action: Avoid forwarding a foreign message.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055162: WebLogic Server JMS failed to serialize the text message for interoperability.

Cause: Contact My Oracle Support.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055163: WebLogic Server JMS failed to serialize the XML message for interoperability.

Cause: Contact My Oracle Support.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055164: Cannot forward a message to a WebLogic Server instance prior than version 9.0.

Cause: Cannot forward a message to a WebLogic Server instance prior than 9.0.

Action: Avoid forwarding a message to a WebLogic Server instance prior than 9.0.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055165: The following exception has occurred: {0}.

Cause: An error condition has occurred.

Action: Look for the associated exception in the log or the program to see what the results are. In general, this stack trace will help in debugging an existing problem.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055167: Single session cannot support more than one synchronous message-prefetching consumer.

Cause: There is another opened synchronous message-prefetching consumer.

Action: Close the other synchronous message-prefetching consumer.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055168: Synchronous message-prefetching consumer cannot support user transaction.

Cause: Synchronous message-prefetching consumer cannot support user transaction.

Action: Disable the user transaction or the synchronous message-prefetching consumer in the jms connection factory setting.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055169: Network connection to server was lost.

Cause: The network connection to the server was lost.

Action: This is usually a recoverable error when the JMS client is using the auto-reconnect/failover feature. This error is exposed to the user (JMS client code developer) when the auto-reconnect feature cannot make a decision without user input on a particular course of action after failover. The user can consciously code to continue to use relevant refreshed JMS objects with a potential lowered quality of service such as duplicate/lost/out-of-order messages, or decide to close the relevant JMS object.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055170: Cannot convert string property from its internal format.

Cause: The string property cannot be converted from its internal format.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055171: Failed to unsubscribe subscription "{0}", client ID "{1}". This connection has a client ID policy of UNRESTRICTED and cannot unsubscribe a durable subscription using the standard javax.jms.Session.unsubscribe() API.

Cause: An attempt was made to unsubscribe a durable subscription using the standard javax.jms.Session.unsubscribe(String name) method from a connection that has a Client ID policy of UNRESTRICTED.

Action: Use weblogic.jms.extensions.WLSession.unsubscribe(Topic topic, String name) API to unsubscribe a durable subscription from a connection that has a Client ID policy of UNRESTRICTED.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055172: Failed to unsubscribe subscription "{0}", client ID "{1}". This connection has a Client ID policy of UNRESTRICTED and cannot unsubscribe a durable subscription with a null topic or distributed topic instance.

Cause: An attempt was made to unsubscribe a durable subscription with a null Topic object or a distributed topic object from a connection that has a Client ID policy of UNRESTRICTED.

Action: Provide a standalone topic object or a member of a distributed topic when calling weblogic.jms.extensions.WLSession.unsubscribe(String topic, String name).
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055173: Read past end of message ({0})

Cause: An attempt was made to read past the end of a StreamMessage. A linked EOFException may contain more information

Action: Do not attempt to read past the end of a StreamMessage. See the linked EOFException for more information
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055174: Error reading from stream ({0})

Cause: There was an error reading the stream from a StreamMessage. A linked IOException may contain more information

Action: See the linked IOException for more information
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055175: Error writing to stream ({0})

Cause: There was an error writing to the stream of a StreamMessage. A linked IOException may contain more information

Action: See the linked IOException for more information
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055176: Active transaction detected during send, publish, or receive while using a non-XATransaction Resource Adapter.

Cause: An active transaction was detected during send, publish, or receive while using a non-XATransaction Resource Adapter.

Action: Use the XATransaction Resource Adapter instead.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-080001: Error in dispatcher {0}

Cause: A runtime error occurred while dispatching a request to the server.

Action: If the error is not application related, contact My Oracle Support with the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: RMI

BEA-080002: Unexport failed for: {0}.

Cause: The remote object was unexported twice.

Action: No action is required.
Level: 1

Type: ERROR

Impact: RMI

BEA-080003: A RuntimeException was generated by the RMI server: {0} {1}.

Cause: A runtime exception occurred while dispatching the request to the server.

Action: No action is required.
Level: 1

Type: WARNING

Impact: RMI

BEA-080004: An error was generated by the RMI server: {0} {1}.

Cause: A runtime error occurred while dispatching a response to the client.

Action: The associated stack trace contains information about the error. Check the server logs for more details.
Level: 1

Type: WARNING

Impact: RMI

BEA-080005: An exception was generated by the RMI server: {0} {1}.

Cause: The error response could not be sent to the client. The underlying socket caused an IOException while dispatching the error response.

Action: The associated stack trace contains information about the error.
Level: 1

Type: WARNING

Impact: RMI

BEA-080006: Failed to associate the transaction context with the response while marshalling an exception to the client: {0}.

Cause: An IOException occurred while associating a transaction context with the response. This happened when marshalling an exception in the response. Most likely, the socket has been torn down or an error occurred in the stream.

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

Type: WARNING

Impact: RMI

BEA-080007: RMI runtime is disabled, since it could not initialize the DGC {0}.

Cause: RMI runtime could not be initialized.

Action: Restart the server. If the problem continues, contact My Oracle Support with the stack trace information.
Level: 1

Type: ERROR

Impact: RMI

BEA-080008: Failed to send error reply to client {0}.

Cause: An exception occurred while dispatching an error response to the client.

Action: No action is required.
Level: 1

Type: ERROR

Impact: RMI

BEA-080009: An error was generated by the RMI server: {0} invoking: {1}.

Cause: A java.lang.Error occurred while invoking method {1} on {0}. A ServerError occurred due to the server side RMI method call.

Action: Check the nested exception in the ServerError for more details.
Level: 1

Type: WARNING

Impact: RMI

BEA-080011: Empty workingSet found while assembling the heartbeat for {0}.

Cause: An empty set of references for {0} was found while assembling the deterministic garbage collector (DGC) heartbeats for all remote virtual machines that are referenced from this virtual machine.

Action: If a java.rmi.NoSuchObjectException occurs, contact My Oracle Support.
Level: 1

Type: NOTIFICATION

Impact: RMI

BEA-080012: No workingSet found for {0} residing in {1}.

Cause: An empty working set for {0} was found while periodically scanning the list of finalized references and decrementing the count for any reference found. This is related to the deterministic garbage collector (DGC).

Action: If a java.rmi.NoSuchObjectException occurs, contact My Oracle Support for further analysis of the error.
Level: 1

Type: ERROR

Impact: RMI

BEA-080013: Reference for {0} not found in working set.

Cause: Did not find {0} in the working set while attempting to decrement the reference count. This is related to the deterministic garbage collector (DGC).

Action: If a java.rmi.NoSuchObjectException occurs, contact My Oracle Support for further analysis of the error.
Level: 1

Type: ERROR

Impact: RMI

BEA-080015: Could not mark references {0}.

Cause: An exception occurred during the execution of the DGC trigger.

Action: If a java.rmi.NoSuchObjectException occurs, contact My Oracle Support for further analysis of the error.
Level: 1

Type: ERROR

Impact: RMI

BEA-080016: No connection available to: {0}. References to objects hosted by it are in jeopardy.

Cause: The client lost connection to the server {0}. If the server does not receive lease renewal messages on the server, RMI runtime removes the remote objects whose leases are not renewed.

Action: If the server {0} has been shut down or crashed, no action is required. Otherwise, ensure that the network is healthy.
Level: 1

Type: WARNING

Impact: RMI

BEA-080017: Failed to renew lease for: {0} objects hosted by: {1}.

Cause: This message is logged only in debug mode.

Action: No action is required.
Level: 1

Type: WARNING

Impact: RMI

BEA-080019: Marked in: {0} milliseconds

Cause: This message is logged only if the LogDGCStatistics debug flag is enabled.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: RMI

BEA-080020: An exception occurred in the DGC server sweep {0}.

Cause: A runtime error occurred while the DGC server (host of remote objects) requested a sweep to periodically clean up server references.

Action: Provide the log files to My Oracle Support for further analysis of the problem.
Level: 1

Type: ERROR

Impact: RMI

BEA-080021: Sweep freed: {0} objects in: {1} milliseconds. {2} exported objects remain.

Cause: This message is logged only if the LogDGCStatistics debug flag is enabled.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: RMI

BEA-080022: Tried to enroll lost reference: {0}.

Cause: This message is logged when an attempt is made to increment the reference count of a lost reference. The reference may have already been released.

Action: If a java.rmi.NoSuchObjectException occurs, contact My Oracle Support for further analysis of the error.
Level: 1

Type: NOTIFICATION

Impact: RMI

BEA-080023: Tried to unenroll a lost reference: {0}.

Cause: This message is logged only if the DebugDGCEnrollment flag is enabled for debugging.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: RMI

BEA-080024: Tried to renew the lease on the lost reference: {0}.

Cause: This message is logged only if the DebugDGCEnrollment flag is enabled for debugging.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: RMI

BEA-080026: Exporting remote object {0} with ID {1}.

Cause: When a remote object is exported into RMI, RMI runtime assigns an object ID to it, thus setting up the environment for remote invocation.

Action: This is an informational message. No action is required.
Level: 1

Type: NOTIFICATION

Impact: RMI

BEA-080027: A heartbeat was not sent due to probable client disconnect.

Cause: A thin-client was disconnected from the server.

Action: This is an informational message. No action is required.
Level: 1

Type: NOTIFICATION

Impact: RMI

BEA-090000: Unsupported circular group definition, {0}.

Cause: This is an unsupported feature.

Action: Do not define circular groups.
Level: 1

Type: ERROR

Impact: Security

BEA-090001: Failed to broadcast LoginFailureRecord to the other cluster servers, {0}.

Cause: An I/O exception occurred.

Action: For more information on how the invalid login attempts are handled, see the security documentation at http://www.oracle.com/technology/products/weblogic/index.html.
Level: 1

Type: ERROR

Impact: Security

BEA-090002: Failed to broadcast unlock user {0} to the other clustered servers. {1}

Cause: An I/O exception occurred.

Action: For more information on how locked user account lockouts are handled, see the security documentation at http://www.oracle.com/technology/products/weblogic/index.html.
Level: 1

Type: ERROR

Impact: Security

BEA-090004: Problem closing enumeration: {0}.

Cause: An unexpected exception occurred.

Action: Review the exception message in the log message to see if it identifies the cause of the exception.
Level: 1

Type: WARNING

Impact: Security

BEA-090010: ACL {0} contains non-existent principal {1} - ignoring principal.

Cause: The principal contained in the ACL does not exist.

Action: Modify the ACL and remove the principal.
Level: 1

Type: WARNING

Impact: Security

BEA-090020: User lockout expired, unlocking user {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090022: Explicitly unlocked, user {0}.

Cause: This is an informational message.

Action: For information about unlocking a user account, see the security documentation at http://www.oracle.com/technology/products/weblogic/index.html.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090034: Not listening for SSL, {0}.

Cause: An IOException occurred when creating the SSL listen thread.

Action: Read the exception text for more help on diagnosing the problem. Contact the system administrator.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090038: Checking User {0} for Permission {1} {2}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090039: Access failed (Thread = {0}), caused {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090040: The File realm contains more users than the specified maximum. Maximum = {0}, currently have {1}.

Cause: The File realm sets a limit on the maximum number of supported users. The system has exceeded that limit.

Action: Raise the value of the Max Users attribute.
Level: 1

Type: WARNING

Impact: Security

BEA-090041: The File realm contains more groups than the specified maximum. Maximum = {0}, currently have {1}.

Cause: The File realm sets a limit on the maximum number of supported groups. The system has exceeded that limit.

Action: Raise the value of the Max Groups attribute.
Level: 1

Type: WARNING

Impact: Security

BEA-090042: The File realm contains more ACLs than the specified maximum. Maximum = {0}, currently have {1}.

Cause: The File realm sets a limit on the maximum number of supported ACLs. The system has exceeded that limit.

Action: Raise the value of the Max ACLs attribute.
Level: 1

Type: WARNING

Impact: Security

BEA-090043: Group {0} should exist but does not.

Cause: When adding members to a group, the specified group was not found.

Action: Verify that the group is defined in the fileRealm.properties file or in the Groups tab of the Administration Console.
Level: 1

Type: WARNING

Impact: Security

BEA-090044: Principal {0} does not exist and therefore cannot be added to group {1}.

Cause: When specifying group members, a principal that does not exist was specified.

Action: Add the specified principal to a security realm.
Level: 1

Type: WARNING

Impact: Security

BEA-090045: Permission {0} does not exist.

Cause: When loading access control lists (ACLs), the specified permission was not found.

Action: Verify that the ACL and the permission are specified correctly.
Level: 1

Type: WARNING

Impact: Security

BEA-090046: ACL {0} does not exist.

Cause: When loading ACLs, the specified permission was not found.

Action: Verify that the ACL is specified correctly.
Level: 1

Type: WARNING

Impact: Security

BEA-090047: Principal {0} does not exist thus cannot be added to ACL {1}.

Cause: The principal specified in the access control list (ACL) does not exist in any security realm.

Action: Add the principal to a security realm.
Level: 1

Type: WARNING

Impact: Security

BEA-090048: Made an in-memory only change to the File realm.

Cause: Changes made to the File realm cannot be written to filerealm.properties.

Action: Make the changes on the Administration Server and the changes are propagated to the Managed Servers.
Level: 1

Type: WARNING

Impact: Security

BEA-090049: System user {0} does not exist, creating it.

Cause: The system user is required.

Action: Ensure that the system user was created in a security realm before booting the server.
Level: 1

Type: WARNING

Impact: Security

BEA-090051: Error creating security runtime management.

Cause: During initialization, the security runtime registers with the OAM infrastructure. If this process fails, a management exception occurs.

Action: Verify that the user booting the server is a member of the Administrator group.
Level: 1

Type: ERROR

Impact: Security

BEA-090052: Server installed as Windows NT service with incorrect password for user {0}. The password may have been changed since the server was installed as a Windows NT Service. Contact the Windows NT system administrator.

Cause: The server is incorrectly configured as a Windows NT service.

Action: Contact the Windows NT system administrator.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090055: The LDAP realm V1 is deprecated. Please use the LDAP realm V2.

Cause: The LDAP realm V1 is deprecated and will be removed in a future release.

Action: Use LDAP realm V2 or one of the LDAP authentication providers.
Level: 1

Type: WARNING

Impact: Security

BEA-090056: User {0} had{1,choice,1# one invalid login attempt|2# {1,number} invalid login attempts}, locking account for {2} minutes.

Cause: User exceeded the value of Lockout Threshhold attempts within the period of time specified in the Lockout Reset Duration attribute. The user account is locked.

Action: For more information about protecting user accounts, see the security documentation at http://www.oracle.com/technology/products/weblogic/index.html.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090060: The AccessDecision class "{0}" returned an error: {1}

Cause: There are multiple possible causes.

Action: Carefully read the returned error to determine if any action is required.
Level: 1

Type: ERROR

Impact: Security

BEA-090063: The DeployableRoleMapper "{0}" returned an error: {1}

Cause: There are multiple possible causes.

Action: Carefully read the returned error to determine if any action is required.
Level: 1

Type: ERROR

Impact: Security

BEA-090064: The DeployableAuthorizer "{0}" returned an error: {1}

Cause: There are multiple possible causes.

Action: Carefully read the returned error to determine if any action is required.
Level: 1

Type: ERROR

Impact: Security

BEA-090065: Getting boot identity from user.

Cause: The boot identity not provided by the command line argument or a problem exists with the boot.properties file.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090066: Problem handling boot identity. The following exception was generated: {0}

Cause: Security permissions are not correct.

Action: Contact the system administrator.
Level: 1

Type: WARNING

Impact: Security

BEA-090067: User lockout expired, unlocking user {0} in security realm {1}.

Cause: The period of time specified for the Lockout Duration attribute has expired for this user account. The user account was locked for exceeding the number of invalid login attempts specified in the Lockout Threshold attribute within the period of time specified in the Lockout Reset Duration attribute.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090070: Failed to broadcast unlock user {0} in security realm {1} to the other cluster servers, {2}.

Cause: An IOException occurred.

Action: For more information about unlocking user accounts, see the security documentation at http://www.oracle.com/technology/products/weblogic/index.html.
Level: 1

Type: ERROR

Impact: Security

BEA-090072: Boot problem with filter rules. The reason was: {0}. The problem is in the rules for the connection filter.

Cause: Rules for the filter are possibly corrupted.

Action: Contact the system administrator and have the rules corrected.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090073: Problem with updating filter rules. The reason was: {0}. The problem is in the rules for the connection filter. The rules will not be updated in the repository.

Cause: Rules for the filter are incorrect.

Action: Correct the offending rules.
Level: 1

Type: WARNING

Impact: Security

BEA-090074: Initializing {0} provider using LDIF template file {1}.

Cause: Either this is the first time this security provider has been initialized or the marker file indicating initialization (with a .initialized extension) has been removed from the system.

Action: Look for a matching LoadedLDIFFForProvider message which indicates the successful loading of the LDIF information for this security provider.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090075: The {0} provider has had its LDIF information loaded from: {1}.

Cause: The provider was requested to import data.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090076: A failure occurred while attempting to load LDIF for provider {0} from file {1}.

Cause: An exception occurred while attempting to open a temporary file as part of the load process.

Action: Examine the exception and correct the cause.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090077: A failure occurred while attempting to create {1} for the {0} provider had been loaded. The exception is {2}.

Cause: Read the exception to determine the cause.

Action: Take appropriate action to keep the exception from happening again. The marker file can be created manually.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090078: User {0} in security realm {1} has had {2,choice,1# one invalid login attempt|2# {2,number} invalid login attempts}, locking account for {3} minutes.

Cause: User exceeded the number of invalid login attempts specified in the Lockout Threshhold attribute within the period of time specified in the Lockout Reset Duration attribute. The user account is locked.

Action: For more information, see the security documentation at http://www.oracle.com/technology/products/weblogic/index.html.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090079: Failed to broadcast LoginFailureRecord for security realm {0} to the other cluster servers, {1}.

Cause: An I/O exception occurred.

Action: For more information, see the security documentation at http://www.oracle.com/technology/products/weblogic/index.html.
Level: 1

Type: ERROR

Impact: Security

BEA-090080: The Server Private Key for server {0} was found in SSL.ServerKeyFileName.

Cause: This is an informational message.

Action: For more information, see the security documentation at http://www.oracle.com/technology/products/weblogic/index.html.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090082: Security initializing using security realm {0}.

Cause: This message is for informational purposes.

Action: Verify that the correct security realm is configured.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090083: Storing boot identity in the file: {0}.

Cause: This message is for informational purposes.

Action: Do not delete this file if you want the server to continue to boot without prompting for username and password.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090087: Server failed to bind to the configured administrator port. The port may already be in use by another process.

Cause: Most likely another process opened the administrator port, thus causing a port conflict.

Action: Inspect the log file for messages that identify the reason why none of the listen ports could be opened.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090088: Private Key keystore alias is not specified in the SSL configuration of server {0}, security realm {1}. Assuming 6.x private key configuration. Loading the private key from a file.

Cause: The keystore alias is not specified in the Server Private Key Alias attribute.

Action: Set the Server Private Key Alias attribute with the alias used to load the private key of the server into the keystore.
Level: 1

Type: WARNING

Impact: Security

BEA-090089: SSL did not find the passphrase for the private key of the server on server {0} for security realm {1}. This may cause an error when SSL attempts to load the private key of the server.

Cause: Either the Server Private Key PassPhrase attribute is not set or the Identity PassPhrase attribute is not set.

Action: If a passphrase is required to retrieve the private key from a keystore, set the Server Private Key PassPhrase attribute.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090091: SSL was unable to get a required Security Service.

Cause: A security service was requested, but no value was returned.

Action: It is likely that the server's configuration has been corrupted. Restore the configuration files from backup. For more information, see the security documentation at http://www.oracle.com/technology/products/weblogic/index.html.
Level: 1

Type: ERROR

Impact: Security

BEA-090093: No pre-WLS 8.1 Keystore providers are configured for server {0} for security realm {1}.

Cause: This is an informational message.

Action: To use pre-WLS 8.1 keystores with the SSL configuration, at least one Keystore Provider must be configured.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090095: SSL cannot instantiate the keystore {1} on server {0}.

Cause: An exception occurred while creating the keystore. This exception caused the create to fail.

Action: Most likely, the keystore was not configured correctly. Ensure that the keystore provider has been configured on the named server. Review the server log for subsequent messages that contain the exception from the keystore provider.
Level: 1

Type: ERROR

Impact: Security

BEA-090096: The MBeans configured for the keystore provider on server {0} for security realm {1} are not Keystore MBeans.

Cause: The MBeans passed to the WebLogic Server key management initialization method are not Keystore MBeans.

Action: Most likely, the keystore provider was not configured correctly. Check that the keystore provider has been configured on the named server.
Level: 1

Type: ERROR

Impact: Security

BEA-090097: The KeyManager class for private keys server {0} for security realm {1} could not be instantiated.

Cause: The Key Manager Security service is null.

Action: There was a problem with the installation of WebLogic Server because the KeyManager is an internal class that supports the WebLogic Security service.
Level: 1

Type: ERROR

Impact: Security

BEA-090101: A keystore exception was returned when the server {1} attempted to load trusted CAs from the keystore file {0}.

Cause: The keystore JDK method threw a keystore exception.

Action: There is a problem with the keystore file. Verify that the file is intact and valid. Use the JDK keytool utility to display the contents of the file. If the file is corrupt, down load a new file from the JavaSoft web site or configure a trusted CA keystore. For more information, see the security documentation at http://www.oracle.com/technology/products/weblogic/index.html.
Level: 1

Type: ERROR

Impact: Security

BEA-090108: The server was unable to retrieve the private key aliased by {2} from the configured keystore on server {0} for security realm {1}. Private key password might be invalid.

Cause: An exception was returned by the keystore getKey method.

Action: Check that a private key keystore is configured on the server. Verify that the private key keystore exists. Ensure that the keystore is valid and contains the private key necessary to use SSL on the server. Verify that the passphrase configured for the private key was the one used to load the private key into the keystore when the private key was created. This exception most often occurs when the passphrase is invalid. Check the log for subsequent messages that contain the key store exception. For more information, see the security documentation at http://www.oracle.com/technology/products/weblogic/index.html.
Level: 1

Type: ERROR

Impact: Security

BEA-090109: The server was unable to find the configured private key on server {0} in the file specified by the SSL Server Key File Name attribute.

Cause: The server looks at the Server Key File Name attribute to load the private key of the server when it cannot find the private key in a configured keystore using the alias that is specified in the Server Private Key Alias attribute as the alias string. One possible cause of this error is that server is not configured with a private key keystore or the server is configured to use the pre-7.0 SSL attribute Server Key File Name.

Action: A pre-7.0 configuration is being used for SSL connections, however that configuration does not specify a value for the Server Key File Name attribute. Either provide a value for the Server Key File Name attribute or configure a keystore for the server. SSL will not be able to initialize until the configuration is corrected. For more information, see the security documentation available at http://www.oracle.com/technology/products/weblogic/index.html.
Level: 1

Type: ERROR

Impact: Security

BEA-090110: The server was unable to find the configured certificate on server {0} in the file specified by the Server Certificate File Name attribute {1}.

Cause: The server looks at the Server Certificate File Name attribute to load the certificate for the server. One possible cause of this error is that the server is not configured with a certificate, or there is a problem with the file configured as the server's certificate.

Action: Verify that a certificate file is configured for the server and that the certificate contained in the file is valid. For more information, see the security documentation available at http://www.oracle.com/technology/products/weblogic/index.html.
Level: 1

Type: ERROR

Impact: Security

BEA-090112: SSL is configured to require clients to present their certificates, however, no trusted certificates have been loaded. The trusted certificates are necessary for validating client certificates.

Cause: Either the "Client Certificates Enforced" option was set by mistake or the problem is with SSL trusted certificates configuration.

Action: Clear the "Client Certificates Enforced" option or specify the location of keystore that contains the trusted certificates.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090113: Loaded {0} client trusted CAs from keystore.

Cause: Loaded the specified number of trusted certificate authority from the trust keystore. This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090116: The server {0} is using the private key it retrieved from keystore aliased by {1}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090118: LDIF template file {1} was empty. The WebLogic provider {0} has been bootstrapped but has not been initialized with any LDIF data.

Cause: A WebLogic provider LDIF template file may have been overwritten with an empty file.

Action: If the server boots successfully, no action is needed. If the server does not boot successfully then an attempt should be made to recover non-empty LDIFT template file from the WebLogic Server kit.
Level: 1

Type: WARNING

Impact: Security

BEA-090119: LDIF template file {1} not found. The WebLogic Server provider {0} has been bootstrapped but has not been initialized with any LDIF data.

Cause: A WebLogic Server provider LDIF template file may have been deleted by mistake.

Action: If the server boots successfully, no action is needed. If the server does not boot successfully, an attempt should be made to recover the LDIFT template file from the WebLogic Server kit.
Level: 1

Type: WARNING

Impact: Security

BEA-090120: Cannot find the file specified by SSL.TrustedCAFileName {0} on server {1}.

Cause: The specified file was not found.

Action: Verify that the specified file exists in the expected directory and/or that the value of Trusted CA File Name attribute refers to an existing file.
Level: 1

Type: WARNING

Impact: Security

BEA-090121: Loaded {0} client root CAs from TrustedCA File.

Cause: Trusted CA certificates were loaded from a trusted CA file.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090122: Loaded {0} client root CAs from Default Key Store file {1}

Cause: Trusted CA certificates were loaded from the default keystore.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090123: Cannot access specified trusted CA file {0} on server {1}.

Cause: File might be read-protected

Action: Ensure that the trusted CA file is accessible by the server.
Level: 1

Type: WARNING

Impact: Security

BEA-090124: Cannot read certificates from the trusted CA file {0} on server {1}.

Cause: The file format is not supported by the server.

Action: Ensure that the file format is valid and is supported by the server.
Level: 1

Type: WARNING

Impact: Security

BEA-090125: Loaded {0} trusted certificates from keystore file specified on the command line: {1}.

Cause: Trusted certificates were loaded from the keystore specified on the command line.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090126: Unable to read a valid version number for property {0} from file {1}. Received exception {2}.

Cause: The value for the {0} property may have been corrupted.

Action: Shut down the server. Attempt to determine what the proper value for the {0} property should be and edit the file so that it reflects that value. If it is not possible to determine the proper value for the {0} property, edit the file and reset the {0} value to 0. Restart WebLogic Server.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090127: Encountered a {2} exception while attempting to read from file {1} for WebLogic {0} provider.

Cause: The {1} file may have been deleted while it was being accessed.

Action: Shut down the server. Attempt to restore the file from a backup. If no backup is available, restart the server. Note that the default WebLogic Server provider might not be correctly initialized.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090129: Updating {0} provider to version {2} using LDIF update template file {1}.

Cause: This security provider has not yet been updated or the marker file indicating initialization (with a .initialized extension) has been removed.

Action: Look for a matching LoadedLDIFFForProvider message in the log file which indicates success loading the LDIF information for this security provider.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090130: Failure {3} while attempting to update the LDIF to version {2} in file {1} for WebLogic {0} provider.

Cause: The directory into which the {1} is to be written may not be writable, the file may not be writable, or the file may not be a valid properties file.

Action: Ensure that both the directory and file are writable. If they are writable, restore the file from backup or open the file and see if the properties within it are corrupt and correct accordingly. The version for provider {0} needs to be set to {2} in the file.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090131: Could not create a {0} JDK keystore instance. Exception: {1}

Cause: {0} is not a valid JDK keystore type or the JDK keystore type is not properly configured.

Action: Verify that the correct keystore type was specified and that the keystore type is correctly specified in the java.security file. Verify that the code for the JDK keystore is in the JDK extensions directory. Restart the serverr after correcting the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090132: Could not open the keystore file {0} for read access. Exception: {1}

Cause: The file does not exist, the file is a directory rather than a regular file, or the file cannot be opened for reading.

Action: Verify that the correct path to the keystore file was specified and that the keystore file exists. Reboot the server after correcting the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090133: Could not load a {1} keystore from the file {0}. Exception: {2}

Cause: There is an I/O or format problem with the keystore data.

Action: Verify that the path to the keystore, the keystore type, and the password for the keystore were specified correctly. Note that some keystore types (for example, JKS) do not require a password for read-only access. Read the exception text for more help on diagnosing the problem. Reboot the server after correcting the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090134: Could not load a {1} keystore from the file {0}. Exception: {2}

Cause: Some certificates in the keystore could not be loaded.

Action: Verify that the crypto providers required by the certificates in the keystore are properly configured in the java.security file and that their code is in the JDK extensions directory. Look at the exception text for more information on diagnosing the problem. Reboot the server after correcting the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090135: Could not load a {1} keystore from the file {0}. Exception: {2}

Cause: The algorithm used to check the integrity of the keystore cannot be found.

Action: Verify that the algorithm used to check the keystore integrity is properly configured in the java.security file and that the code is in the JDK extensions directory. Read the exception text for more information on diagnosing the problem. Reboot the server after correcting the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090136: Could not open the keystore file {0} for write access. Exception {1}

Cause: The file may exist but is a directory rather than a regular file, the file does not exist and cannot be created, or the file cannot be opened.

Action: Verify that the correct pathname to the keystore was specified and that the parent directory exists. If neither of these problems exist, read the exception text for more information on diagnosing the problem. Reboot the server after correcting the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090137: Could not store a {1} keystore in the file {0}. Exception: {2}

Cause: There was an I/O problem with the keystore data.

Action: Verify that the passphrase is correct. Some JDK keystore implementations require the use of the password for a previous keystore. Read the exception text for more information on diagnosing the problem. Reboot the server after correcting the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090138: Could not store a {1} keystore in the file {0}. Exception: {2}

Cause: Some certificates included in the keystore could not be stored.

Action: Verify that the crypto providers required by the certificates in the keystore are properly configured in the java.security file and that their code is in the JDK extensions directory. Look at the exception text for more information on diagnosing the problem. Reboot the server after correcting the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090139: Could not store a {1} keystore in the file {0}. Exception: {2}

Cause: The data integrity algorithm for the keystore could not be found.

Action: Verify that the algorithm used to check the keystore integrity is properly configured in the java.security file and that the code is in the JDK extensions directory. Read the exception text for more information on diagnosing the problem. Reboot the server after correcting the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090140: Could not store a {1} keystore in the file {0}. Exception: {2}

Cause: The keystore has not been initialized (loaded).

Action: Make sure to load the keystore before storing it. Read the exception text for more information on diagnosing the problem. Reboot the server after correcting the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090141: The WebLogic keystore provider {1} in security realm {0} cannot be used for private keys because its private key keystore was not configured.

Cause: The Private Key Store Location attribute was not specified.

Action: To use the WebLogic keystore provider to store private keys, perform the following steps. Create a JDK keystore and load the private keys into the keystore. Use the Administration Console to attributes on the WebLogic keystore provider. Set the Private Key Store Location attribute to the path of the JDK keystore file. Set the Private Key Store Passphrase attribute to the passphrase of the JDK keystore file (some keystore types (for example, JKS) allow an empty passphrase for read-only access). Set the Type attribute to the type of the JDK keystore (the Type attribute may be left empty if the JDK keystore uses the default keystore type configured in the java.security file). Restart the server.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090142: The WebLogic keystore provider {1} in security realm {0} cannot be used for trusted (root) CAs because its trusted (root) CA keystore was not configured.

Cause: The Root Key Store Location attribute was not specified.

Action: To use the WebLogic keystore provider to store trusted CAs, perform the following steps. Create a JDK keystore. Load the trusted CA certificates into the keystore. Set attributes on the WebLogic keystore provider. Set the Root Key Store Location attribute to the path of the JDK keystore file. Set the Root Key Store Passphrase attribute to the passphrase of the JDK keystore file (some keystore types (for example, JKS) allow an empty passphrase for read-only access). Set the Type attribute to the JDK keystore type (the type may be left empty if the JDK keystore uses the default keystore type configured in the java.security file). Restart the server.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090143: The WebLogic keystore provider {1} in security realm {0} cannot be used for private keys because its configured private key keystore file {2} does not exist.

Cause: The file {2} does not exist as a global pathname or in the domain directory.

Action: To use the WebLogic keystore provider to store private keys, perform the following steps. Create a JDK keystore and load the private keys into the keystore. Use the Administration Console to set attributes on the WebLogic Keystore provider. Set the Private Key Store Location attribute to the path of the JDK keystore file. Set the Private Key Store Passphrase attribute to the passphrase of the JDK keystore file (some keystore types (for example, JKS) allow an empty passphrase for read-only access). Set the Type attribute to the type of the JDK keystore (the Type attribute may be left empty if the JDK keystore uses the default keystore type configured in the java.security file). Restart the server.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090144: The WebLogic keystore provider {1} in security realm {0} cannot be used for trusted (root) CAs because its configured trusted (root) CA keystore file {2} does not exist.

Cause: The file {2} does not exist as a global pathname or in the domain directory.

Action: To use the WebLogic keystore provider to store trusted CAs, perform the following steps. Create a JDK keystore. Load the trusted CA certificates into the keystore. Set attributes on the WebLogic keystore provider. Set the Root Key Store Location attribute to the path of the JDK keystore file. Set the Root Key Store Passphrase attribute to the passphrase of the JDK keystore file (some keystore types (for example, JKS) allow an empty passphrase for read-only access). Set the Type attribute to the JDK keystore type (the type may be left empty if the JDK keystore uses the default keystore type configured in the java.security file). Restart the server.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090145: The WebLogic keystore provider {1} in security realm {0} cannot be used for private keys because its private key {3} keystore could not be loaded from the file {2}.

Cause: See the error logged before this one for details.

Action: Verify that the Root Keystore Location attribute is specified correctly. Verify that the Root Keystore PassPhrase attribute matches the passphrase of the keystore. Some keystore types (for example, JKS) allow an empty passphrase for read-only access. Verify that the Type attribute is correct. The Type attribute may be left empty if the JDK keystore uses the keystore type configured in the java.security file. Verify that the private key keystore exists and is properly configured. Verify that a keystore for the specified type is properly configured. After correcting the problem, restart the server.
Level: 1

Type: ERROR

Impact: Security

BEA-090146: The WebLogic keystore provider {1} in security realm {0} cannot be used for trusted CAs because its trusted CA {3} keystore could not be loaded from the file {2}.

Cause: See the error logged before this one for details.

Action: Verify that the Private Keystore Location attribute is correct. Verify that the Private Keystore PassPhrase attribute matches the passphrase of the keystore. Note that some keystore types (for example, JKS) allow an empty passphrase for read-only access. Verify that the Type attribute is correct. The Type attribute may be empty if the JDK keystore uses the keystore type configured in the java.security file. Verify that the private key keystore exists and is properly configured. Verify that a JDK keystore for the type specified is properly configured. After correcting the problem, reboot the server.
Level: 1

Type: ERROR

Impact: Security

BEA-090152: Demo trusted CA certificate is being used in production mode: {0}. The system is vulnerable to security attacks, since it trusts certificates signed by the demo trusted CA.

Cause: A trusted CA keystore contains a demo certificate.

Action: Remove the demo certificate from the trusted CA keystore.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090153: Demo identity certificate is used in production mode: {0} The system is vulnerable to security attacks, since the server private key is available to the public.

Cause: The server is configured with Demo identity and is running in production mode.

Action: Configure the server to use a certificate obtained from a reputable certificate authority.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090154: Identity certificate has expired: {0}.

Cause: Certificate for the server has expired.

Action: Configure the server to use a certificate obtained from a reputable certificate authority.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090155: Identity certificate is not yet valid: {0}.

Cause: The server certificate is not yet valid.

Action: Replace the server certificate with a certificate obtained from a reputable certificate authority.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090156: Invalid identity certificate signature: {0}

Cause: The certificate of the server or the certificate authority that issued the certificate is invalid.

Action: Replace the certificate of the server with a valid certificate.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090157: Unable to verify certificate signature: {0}.

Cause: The certificate of the server or the certificate authority that issued the certificate is invalid.

Action: Replace certificate of the server with a valid certificate.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090158: The server was unable to find the private key with alias {0} at location {1} on server {2}, security realm {3}. Ensure that the keystore exists and contains the key entry under the specified alias.

Cause: The private key alias {0} was not found at location {1} on server {2}, security realm {3}.

Action: Verify that a keystore is configured on the server displayed in the log file. Verify that the keystore for the private key exists, the keystore is a valid, and contains the private key for the server. For more information, see the security documentation at http://www.oracle.com/technology/products/weblogic/index.html.
Level: 1

Type: ERROR

Impact: Security

BEA-090160: Cannot find default trusted CA keystore file {0} on server {1}.

Cause: The keystore does not exist.

Action: Configure a trusted CA keystore.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090161: A failure occurred while attempting to save LDIF for security provider {0} using file {1}.

Cause: An exception occurred while attempting to open a temporary file as part of the export process.

Action: Examine the exception and correct the cause.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090162: The {0} provider has had its LDIF information saved in: {1}.

Cause: The security provider was requested to export data.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090163: The {0} provider did not import a duplicate LDAP entry: {1}

Cause: The security provider already contained the imported data.

Action: Delete the existing data and import data into the security provider again.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090164: Failed to load trusted certificates from keystore {0} of type {1}

Cause: The keystore file cannot be loaded because of invalid password or Keystore type.

Action: Ensure that the keystore configuration is valid.
Level: 1

Type: WARNING

Impact: Security

BEA-090165: Cannot find identity keystore file {1} on server {0}

Cause: The identity keystore does not exist.

Action: Correct the SSL configuration of the server. Specify a valid identity keystore.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090166: Failed to load identity keystore of type {2} from file {1} on server {0}

Cause: File is not a valid keystore file or it is of a different keystore type.

Action: Ensure that the keystore file specified in SSL configuration of the server is valid and of the specified keystore type.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090167: Cannot retrieve identity certificate and private key on server {0}, because the keystore entry alias is not specified.

Cause: The alias for the private key entry in the identity keystore was not specified.

Action: Correct the private key alias in the SSL configuration of the server.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090168: No identity key/certificate entry was found under alias {2} in keystore {1} on server {0}.

Cause: The private key entry does not exist in the specified keystore under the specified alias. The wrong alias or keystore was specified or the entry under the specified alias is not a private key.

Action: Ensure that the entry for the private key exists in the specified keystore under the specified alias.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090169: Loading trusted certificates from the {1} keystore file {0}.

Cause: The server is loading trusted CA certificates from the specified keystore.

Action: Verify that the correct trusted CA certificate and keystore are being used.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090171: Loading the identity certificate and private key stored under the alias {2} from the {1} keystore file {0}.

Cause: The server is loading the identity certificate and the corresponding private key from the specified keystore.

Action: Verify that the certificate information such as keystore location, alias, and type are correct.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090172: No trusted certificates have been loaded. Server will not trust to any certificate it receives.

Cause: Keystores specified in the SSL configuration of the server do not contain certificates or do not exist.

Action: Correct the trusted CA information in the SSL configuration of the server.
Level: 1

Type: WARNING

Impact: Security

BEA-090173: The server's trust keystore configuration (specified on the command line or in boot.properties) is incorrect.

Cause: Either TrustKeyStores was set to an illegal value or TrustKeyStores was set to CustomTrust but CustomTrustKeyStoreFileName was not specified.

Action: If specifying the server's trust keystore on the command line: To use the trusted CAs in DemoTrust.jks and in the JDK''s cacerts, specify: -Dweblogic.security.TrustKeyStore=DemoTrust defaults to DemoTrust -Dweblogic.security.JavaStandardTrustKeyStorePassPhrase=passphrase defaults to no passphrase which means read-only access to the JDK''s cacerts. To use the trusted CAs in the JDK''s cacerts, specify: -Dweblogic.security.TrustKeyStore=JavaStandardTrust -Dweblogic.security.JavaStandardTrustKeyStorePassPhrase=passphrase defaults to no passphrase which means read-only access to the JDK''s cacerts. To use the trusted CAs from another keystore, specify: -Dweblogic.security.TrustKeyStore=CustomTrust -Dweblogic.security.CustomTrustKeyStoreFileName=filename either an absolute pathname or a pathname relative to the directory in which the server was started. -Dweblogic.security.CustomTrustKeyStoreType=type defaults to the default keystore type specified in the JDK''s java.security file. -Dweblogic.security.CustomTrustKeyStorePassPhrase=passphrase defaults to no passphrase. Some keystore types allow this but only grant read-access (for example, JKS). Other keystore types require a keystore passphrase even for read-access. If specifying the server's trust keystore via boot.properties, set the same properties as for the command line to boot.properties but remove the weblogic.security prefix. For example, set TrustKeyStore=JavaStandardTrust.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090174: The trust keystore configuration specified on the command line or in boot.properties does not match the trust keystore configuration specified in config.xml.

Cause: Either the trust keystore type does not match (for example, one specifies CustomTrust and the other specifies JavaStandardTrust) or the configuration values do not match (for example, the CustomTrustKeyStoreFileName values are not the same).

Action: To always specify the trusted CA keystore for the server on the command line or the boot.properties file, set the server's Keystores value in the config.xml file to CustomIdentityAndCommandLineTrust. Otherwise, ensure that the trust keystore configuration for this server in config.xml matches the trust keystore configuration specified on the command line or in boot.properties.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090175: Unrecognized Callback

Cause: Only callbacks of NameCallback or PasswordCallback are supported.

Action: Remove the unsupported callback from the list of callbacks.
Level: 1

Type: ERROR

Impact: Security

BEA-090176: Illegal null Subject passed as a parameter.

Cause: The Subject parameter cannot be null.

Action: Verify that the subject passed as a parameter is not null. If no subject utility methods are being called, this exception indicates an internal coding error in the server. This exception should not normally occur. Check with My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090177: Invalid Message Digest requested, only MD5, SHA, and MD2 are supported.

Cause: The Message Digest type is not supported.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090178: null Class

Cause: The class used to filter principals is null.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090179: Null action

Cause: The doAs method expects the action to not be null.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090180: Could not convert AS to AU: {0}.

Cause: An exception occurred when converting.

Action: Look at the exception text to diagnose the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090181: Attempting to modify a sealed subject.

Cause: A sealed subject is read-only and cannot be modified.

Action: This exception is an internal error. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090182: {0} is not a java.security.Principal.

Cause: The object is not a principal. Only principals can be added to a subject.

Action: Verify that the authentication provider is correctly creating principals.
Level: 1

Type: ERROR

Impact: Security

BEA-090183: Got a NullPointerException in AuthenticatedUser.hashCode() with actual type {0}.

Cause: The authenticated user name, qos, or localPort is null.

Action: This exception indicates an internal error. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090184: invalid constraints

Cause: None of the specified constraints are supported.

Action: Remove the unsupported constraints or pass-in supported constraints. Supported constraints are @quot;users@quot; and @quot;groups@quot;.
Level: 1

Type: ERROR

Impact: Security

BEA-090185: No CallbackHandler was specified.

Cause: The callback handler is null.

Action: Pass a non-null callback handler when initializing the UsernamePasswordLoginModule.
Level: 1

Type: ERROR

Impact: Security

BEA-090186: Error: Callback {0} is not available.

Cause: The callback handler does not support one of callbacks required by the UsernamePasswordLoginModule. The UsernamePasswordLoginModule requires 3 callbacks: NameCallback, PasswordCallback, and URLCallback.

Action: Verify that the callback handler that is specified in the initialize method of UsernamePasswordLoginModule supports the three required callbacks.
Level: 1

Type: ERROR

Impact: Security

BEA-090187: {0} (Unable to delete)

Cause: The file could not be deleted.

Action: Verify that the file can be deleted and is not locked by some other process.
Level: 1

Type: ERROR

Impact: Security

BEA-090188: Cannot update a read-only PermissionCollection.

Cause: The collection is read-only and permissions cannot be added.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090190: Error creating {0}

Cause: Either the file does not exist, the file is a directory rather than a regular file, or the file cannot be opened for reading.

Action: Verify the filename. Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090191: Error writing realm contents to {0}.

Cause: An error occurred while writing the file.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090192: Could not create temporary file for {0}, .new, {1}.

Cause: An error occurred while creating the temporary file.

Action: Verify the filename and directory. Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090193: Could not create temporary file for {0}, .old, {1}.

Cause: An error occurred when creating the temporary file.

Action: Verify the filename and directory. Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090194: Could not clear temporary file {0}.

Cause: The delete method returned false.

Action: Verify that the file can be deleted and is not locked by some other process.
Level: 1

Type: ERROR

Impact: Security

BEA-090195: Could not rename {0} to {1}.

Cause: The rename method returned false.

Action: Verify that the file can be renamed and is not locked by some other process.
Level: 1

Type: ERROR

Impact: Security

BEA-090196: Could not delete {0}.

Cause: The delete method returned false.

Action: Verify that the file can be deleted and is not locked by some other process.
Level: 1

Type: ERROR

Impact: Security

BEA-090197: Cannot find permission {0}.

Cause: A ClassNotFound exception occurred when instantiating the permission.

Action: Verify that the class is contained in the classpath.
Level: 1

Type: ERROR

Impact: Security

BEA-090198: No appropriate constructor for {0}

Cause: A NoSuchMethod exception occurred when instantiating the permission.

Action: Verify that the permission class implements the constructor.
Level: 1

Type: ERROR

Impact: Security

BEA-090199: Cannot instantiate abstract class {0}.

Cause: An Instantiation exception occurred when instantiating the permission.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090200: No permission to instantiate constructor for {0}

Cause: An IllegalAccess exception occurred when instantiating the permission.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090201: Incorrect argument for constructor for {0}

Cause: An IllegalArgument exception occurred when instantiating the permission.

Action: Verify that the permission class implements the appropriate constructor.
Level: 1

Type: ERROR

Impact: Security

BEA-090202: Exception in constructor for {0}

Cause: An InvocationTarget exception occurred when instantiating the permission.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090203: Trailing text after grant string

Cause: Text is present after the closing bracket and semicolon.

Action: Remove the text after the closing bracket and semicolon.
Level: 1

Type: ERROR

Impact: Security

BEA-090204: Unexpected end of string in grant statement

Cause: The grant statement is not complete.

Action: Verify the grant statement and add the necessary text.
Level: 1

Type: ERROR

Impact: Security

BEA-090205: Expected "{0}" but found "{1}".

Cause: The syntax is incorrect.

Action: Verify the syntax and add the specified expected construct.
Level: 1

Type: ERROR

Impact: Security

BEA-090206: Expected a guote (") but found "{0}".

Cause: An expected quote was not found.

Action: Verify the syntax and add the quote.
Level: 1

Type: ERROR

Impact: Security

BEA-090207: Version mismatch, have {0}, expected {1}.

Cause: The version number does not match the expected value.

Action: Verify that the SerializedSystemIni.dat file has not been corrupted.
Level: 1

Type: ERROR

Impact: Security

BEA-090208: Corrupt {0}

Cause: An IOException occurred when reading bytes from the file.

Action: Verify that the SerializedSystemIni.dat file is valid. Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090209: Could not close stream: {0}.

Cause: An IOException was returned by the input stream close method.

Action: Verify that the SerializedSystemIni.dat file is valid. Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090210: Error opening {0}

Cause: A FileNotFound exception occurred while opening the input stream.

Action: Verify that the SerializedSystemIni.dat file exists and is accessible. Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090218: decoding error: {0}

Cause: An IOException occurred.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090219: Error decrypting Secret Key {0}

Cause: An exception occurred when getting the secret key for the encryption service.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090220: rule {0}

Cause: A connection filter rule denied access.

Action: None. This exception is used to deny access to the server as specified in the rules of the connection filter.
Level: 1

Type: ERROR

Impact: Security

BEA-090221: Connection filter internal error!

Cause: An unknown connection filter rule was encountered.

Action: Verify the connection filter rules. This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090222: unknown protocol "{0}"

Cause: The protocol specified in the connection filter is not supported.

Action: Verify the protocol and ensure it is listed in the rules of the connection filter.
Level: 1

Type: ERROR

Impact: Security

BEA-090223: bad netmask: "{0}"

Cause: The netmask is greater than 32 bits or less than 0.

Action: Verify the netmask in the connection filter.
Level: 1

Type: ERROR

Impact: Security

BEA-090224: bad netmask: "{0}"

Cause: The number of tokens in the netmask is not 4.

Action: Verify the netmask.
Level: 1

Type: ERROR

Impact: Security

BEA-090225: bad netmask: "{0}"

Cause: The number in the netmask is less than 0 or greater than 255.

Action: Change the number in the netmask to be greater than or equal to 0 and less than or equal to 255.
Level: 1

Type: ERROR

Impact: Security

BEA-090226: bad netmask: "{0}"

Cause: A NumberFormat exception occurred when calling Integer.parseInt on the netmask token.

Action: Verify the netmask token to ensure it is an integer.
Level: 1

Type: ERROR

Impact: Security

BEA-090227: bad action "{0}"

Cause: The action is not deny or allow.

Action: Verify the action and change it to deny or allow.
Level: 1

Type: ERROR

Impact: Security

BEA-090228: null filter

Cause: A connection filter cannot be null.

Action: Verify the connection filter and ensure that a connection filter is not null.
Level: 1

Type: ERROR

Impact: Security

BEA-090229: Attempt to set connection filter more than once

Cause: A connection filter was set more than once.

Action: Modify the application code to only call the setFilter method once.
Level: 1

Type: ERROR

Impact: Security

BEA-090230: Zero length PEMInputStream

Cause: The Privacy Enhanced Mail (PEM) input stream contained zero bytes.

Action: Verify that the PEM file or PEM input stream is valid and does not contain zero bytes.
Level: 1

Type: ERROR

Impact: Security

BEA-090231: Security already configured

Cause: The Security service initialization method was called twice.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090232: salt is not set

Cause: The salt obtained from the MBean is null.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090233: problem with connection filter rules

Cause: An exception occurred while setting the connection filter rules. The filter class may not have been loaded or some other error may have caused the exception.

Action: Verify the connection filter class and rules. Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090238: could not create User Name Mapper

Cause: An exception occurred while loading the User Name Mapper class.

Action: Verify that the User Name Mapper class exists in the class path and the class implements the UserNameMapper interface.
Level: 1

Type: ERROR

Impact: Security

BEA-090239: Identity Assertion type cannot be null

Cause: The token type was null.

Action: The containers should not be passing a null token type. This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090240: Identity Assertion token cannot be null

Cause: The identity assertion token was null.

Action: The containers should not be passing a null token. This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090241: Identity Assertion type of {0} is not a configured active type.

Cause: The identity assertion token type was not configured in the WebLogic Identity Assertion provider.

Action: Configure the identity assertion type {0} in the Active Types attribute of the WebLogic Identity Assertion provider.
Level: 1

Type: ERROR

Impact: Security

BEA-090242: Client principal {0} is not trusted to assert identity.

Cause: Client principal {0} is not in the list of clients trusted to assert identity via CSIv2 identity assertion tokens.

Action: Add the client principal to the Trusted Client Principals attribute of the WebLogic Identity Asserter provider or specify asterisk (*) to allow any client to assert any identity.
Level: 1

Type: ERROR

Impact: Security

BEA-090243: user Name Mapper class not configured - cannot assert identity

Cause: No User Name Mapper is configured.

Action: Configure a User Name Mapper. Use either the default User Name Mapper or a custom User Name Mapper. To use the default implementation, set the Use Default User Name Mapper attribute for the WebLogic Identity Assertion provider. To use a custom User Name Mapper, set the User Name Mapper Class Name attribute to the name of the custom implementation.
Level: 1

Type: ERROR

Impact: Security

BEA-090244: Unknown Identity Assertion type {0}

Cause: Identity Assertion type {0} is not supported.

Action: Use a supported identity assertion type or write a custom Identity Assertion provider.
Level: 1

Type: ERROR

Impact: Security

BEA-090245: No mapping for Identity User Name

Cause: The identity assertion token could not be mapped to a username.

Action: If this is not the expected outcome, modify the custom User Name Mapper to correctly map the desired token to a username.
Level: 1

Type: ERROR

Impact: Security

BEA-090246: Token not of type {0}

Cause: The token does not match the token type.

Action: The containers should not be passing a token that is not an AuthenticatedUser. This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090247: Unable to verify {0}

Cause: The authenticated user is invalid.

Action: Verify that the user identity was from this domain or from a domain that is trusted by this domain.
Level: 1

Type: ERROR

Impact: Security

BEA-090248: Unrecognized Callback

Cause: Callback type is not supported.

Action: Verify that the LoginModule for the configured Authentication provider is only passing a NameCallback when calling the handle method.
Level: 1

Type: ERROR

Impact: Security

BEA-090249: Cursor is null

Cause: A null cursor is not supported.

Action: Modify the code to pass a non-null cursor.
Level: 1

Type: ERROR

Impact: Security

BEA-090250: Cursor not found {0}

Cause: Cursor was not found in the list of valid cursors.

Action: Verify that the cursor passed to the method is valid and was returned from a method that creates cursors. Examples of such methods are listUsers, listGroups and listRoles.
Level: 1

Type: ERROR

Impact: Security

BEA-090251: haveCurrent error for cursor name {0}

Cause: An LDAP exception occurred during the haveCurrent method.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090252: advance error for cursor name {0}

Cause: An LDAP exception occurred while advancing the list.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090253: close error for cursor name {0}

Cause: An LDAP exception occurred while closing this list cursor.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090258: max cannot be < 0

Cause: The maximumToReturn value cannot be less than zero.

Action: Pass in a maximumToReturn parameter value that is greater or equal to zero.
Level: 1

Type: ERROR

Impact: Security

BEA-090259: Group {0}

Cause: Group {0} does not exist in the LDAP server.

Action: Pass in a group that exists.
Level: 1

Type: ERROR

Impact: Security

BEA-090261: Wildcard cannot be null.

Cause: The wildcard parameter is null.

Action: Pass a non-null wildcard parameter to the method.
Level: 1

Type: ERROR

Impact: Security

BEA-090262: Error listing groups {0}

Cause: An LDAP exception occurred while searching for the groups in the LDAP server.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090263: parent group cannot be null

Cause: The parent group name is null.

Action: Pass a non-null parent group name parameter to this method.
Level: 1

Type: ERROR

Impact: Security

BEA-090264: member cannot be null

Cause: The member name is null.

Action: Pass a non-null member name parameter to this method.
Level: 1

Type: ERROR

Impact: Security

BEA-090265: member cannot be parent group

Cause: The member name and parent group name are the same value.

Action: Change either the member name or parent group name parameters of this method.
Level: 1

Type: ERROR

Impact: Security

BEA-090266: group name cannot be null

Cause: The group name cannot be null.

Action: Pass a non-null group name to the method.
Level: 1

Type: ERROR

Impact: Security

BEA-090271: Member {0}

Cause: The member does not exist.

Action: Pass in a member name that exists in the LDAP server.
Level: 1

Type: ERROR

Impact: Security

BEA-090278: Error listing member groups {0}

Cause: An LDAP exception occurred while listing the member groups in the LDAP server.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090279: Error listing users {0}

Cause: An LDAP exception occurred while listing the users in the LDAP server.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090281: user name cannot be null

Cause: The user name cannot be null.

Action: Pass a non-null user name to the method.
Level: 1

Type: ERROR

Impact: Security

BEA-090283: User {0}

Cause: User {0} already exists in the LDAP server.

Action: Pass in another user name.
Level: 1

Type: ERROR

Impact: Security

BEA-090287: User {0}

Cause: User {0} does not exist in the LDAP server.

Action: Pass a user name that exists.
Level: 1

Type: ERROR

Impact: Security

BEA-090294: could not get connection

Cause: An LDAP exception occurred because an LDAP connection could not be obtained from the connection pool.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090296: invalid URL {0}

Cause: An LDAP exception occurred because of an invalid dynamic group URL.

Action: Verify the dynamic group definition. Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090297: No CallbackHandler specified

Cause: The callback handler is null.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090298: No Delegate specified

Cause: The LDAP delegate is null.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090299: Username not supplied.

Cause: The user name returned from the NameCallback cannot be null.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090300: Identity assertion failed: User {0} does not exist.

Cause: The user does not exist in the LDAP server.

Action: Add the user to the LDAP server or configure the Identity Assertion provider to return a user that exists.
Level: 1

Type: ERROR

Impact: Security

BEA-090301: Password not supplied.

Cause: The password cannot be null.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090302: Authentication failed: User {0} denied.

Cause: The username and password could not bind to the LDAP server.

Action: Verify the username and password.
Level: 1

Type: ERROR

Impact: Security

BEA-090305: Authentication failed getting groups for User {0} {1}.

Cause: A group to which the user belongs was not found.

Action: Verify the groups to which the user belongs.
Level: 1

Type: ERROR

Impact: Security

BEA-090307: DefaultAuthenticatorImpl constructor failed: {0}

Cause: A exception was thrown in the constructor for the WebLogic Authentication provider.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090309: null subject

Cause: The subject cannot be null.

Action: Pass a non-null subject to the method.
Level: 1

Type: ERROR

Impact: Security

BEA-090310: Failed to create resource.

Cause: An EnCreateException occurred when creating the security policy.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090311: Failed to set resource expression.

Cause: An EnCreateException occurred when setting the security policy expression.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090313: policy removal error

Cause: A EnRemoveException occurred during the deletion of security policies for the application.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090314: Entitlement Engine unable to connect to the embedded LDAP server {0}

Cause: An exception occurred when initializing the entitlement engine for the WebLogic Authorization provider.

Action: Read the exception text in {0} for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090315: DefaultAuthorizerImpl init failed: {0}

Cause: An exception occurred during the initialization of the WebLogic Authorization provider.

Action: Read the exception text in {0} for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090316: null helper

Cause: The helper cannot be null.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090318: DefaultRoleMapperImpl init failed: {0}

Cause: An exception occurred in the initialization method of the WebLogic Role Mapping provider.

Action: Read the exception text in {0} for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090319: Unknown resource type: {0}

Cause: The role id cannot be null.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090320: Failed to create role

Cause: An exception occurred during the createRole method.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090321: Failed to set role expression

Cause: An exception was thrown during the setRole method.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090322: role removal error

Cause: An EnRemoveException occurred during the delete operation.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090323: Map cannot be modified.

Cause: Not all Map object methods are unsupported.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090330: DefaultCredentialMapperImpl.getCurrentMappingWLSUsername failed: No such resource maps list cursor available

Cause: The cursor is invalid.

Action: Verify that the cursor was returned from the listMappings method.
Level: 1

Type: ERROR

Impact: Security

BEA-090344: A valid security realm name must be specified when initializing.

Cause: The security realm name is null or does not exist.

Action: Verify the security configuration. Ensure that the default security realm is set and that the security realm exists.
Level: 1

Type: ERROR

Impact: Security

BEA-090347: Auditor not yet initialized

Cause: The Auditing provider was not initialized before the writeEvent method was called.

Action: This exception that indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090348: No AuthorizerMBeans and no AdjudicatorMBean provided.

Cause: No provider MBeans were passed during the initialization of the Authorization Manager.

Action: Configure at least one Authorization provider for the security realm.
Level: 1

Type: ERROR

Impact: Security

BEA-090349: Need at least one AuthorizerMBean

Cause: An empty array of provider MBeans were passed during the initialization of the Authorization Manager.

Action: Configure at least one Authorization provider for this security realm.
Level: 1

Type: ERROR

Impact: Security

BEA-090350: The RoleManager must be initialized prior to initializing an Authorization Manager.

Cause: Role Manager is not initialized.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090357: Calling isProtectedResource before the AuthorizationManager is initialized.

Cause: The Authorization Manager must be initialized before any method calls.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090358: Required parameter not supplied to isAccessAllowed.

Cause: A required parameter was null.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090359: Required parameter not supplied to isProtectedResource.

Cause: A required parameter was null.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090361: Exception: CredentialManager.initialize, Invalid or missing CredentialMapperMBean Mbean

Cause: The array of Credential Mapping MBeans was null or empty.

Action: Verify the security realm configuration and ensure that a Credential Mapping provider is configured.
Level: 1

Type: ERROR

Impact: Security

BEA-090364: Exception: CredentialManager.getCredentials, credentialsType = null

Cause: The credentialType parameter cannot be null.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090365: LoginModule error: loginModuleName {0}

Cause: A ClassNotFound, IllegalAccess, or Instantiation exception occurred while loading the delegate LoginModule.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090366: LoginModule error: null delegateLoginModuleName

Cause: The delegate LoginModule is null.

Action: Verify the Authentication provider has correctly implemented the getLoginModuleConfiguration method.
Level: 1

Type: ERROR

Impact: Security

BEA-090368: MBeans are not instances of Keystore MBean.

Cause: An MBean is not of type Keystore MBean.

Action: Verify the WebLogic Keystore provider is configured properly.
Level: 1

Type: ERROR

Impact: Security

BEA-090369: Problem instantiating Keystore provider

Cause: An exception occurred during the creation or initialization of the WebLogic Keystore provider.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090370: Invalid configuration, no AuthenticationProviderMBean passed to initialize.

Cause: No Authentication provider MBeans were passed.

Action: Verify the security realm configuration and ensure that an Authentication provider is configured.
Level: 1

Type: ERROR

Impact: Security

BEA-090372: No CallbackHandler Supplied

Cause: The callback handler is null.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090375: Null TokenType parameter

Cause: The token type is null.

Action: The containers should not pass a null token types. This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090376: Null Token parameter

Cause: The identity assertion token was null.

Action: The containers should not pass null tokens. This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090384: No Provider MBeans

Cause: No MBeans were passed during the initialization of the Role Manager.

Action: Configure a Role Mapping provider.
Level: 1

Type: ERROR

Impact: Security

BEA-090389: RoleManager not yet initialized.

Cause: The Role Manager must be initialized before the getRoles method can succeed.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090391: Null user identity

Cause: The identity for the runAs method cannot be null.

Action: Ensure that the subject passed to the runAs method is valid.
Level: 1

Type: ERROR

Impact: Security

BEA-090392: SecurityServiceManager not yet initialized.

Cause: The Security service must be initialized before any method calls.

Action: This exception indicates an internal coding error in the server. Contact Oracle support.
Level: 1

Type: ERROR

Impact: Security

BEA-090393: Security service not yet initialized: {0}.

Cause: The Security service must be initialized before it can be used.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090394: Must specify a Security realm.

Cause: The security realm name cannot be null.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090395: Must specify a SecurityService.ServiceType.

Cause: The Security service type cannot be null.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090396: Security Realm {0} does not exist.

Cause: The security realm is not a valid.

Action: Verify the security realm has all the required providers configured and the realm is set as the default (active) security realm.
Level: 1

Type: ERROR

Impact: Security

BEA-090397: Principal set does not contain a RealmAdapterUser.

Cause: A RealmAdapterUser is required to send a authenticated user to a previous version of WebLogic Server.

Action: Configure the Realm Adapter provider.
Level: 1

Type: ERROR

Impact: Security

BEA-090398: Invalid Subject: {0}

Cause: Principal validation failed for this subject.

Action: Ensure that the subject was created by this domain or in a domain trusted by this domain.
Level: 1

Type: ERROR

Impact: Security

BEA-090399: Security services unavailable

Cause: Authentication and Authorization services are required to perform the boot authorization checks.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090402: Authentication denied: Boot identity not valid. The user name or password or both from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.

Cause: The user name or password or both from the boot identity file may have been changed since the boot identity file was created.

Action: Update the boot identity file with the correct username and password for the boot identity.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090403: Authentication for user {0} denied.

Cause: The user supplied an invalid password or the user name was invalid.

Action: Reboot the server and specify the current user and password.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090404: User {0} is not permitted to start the server. The server policy may have changed in such a way that the user is no longer able to start the server. Restart the server with the administrative user account or contact the system administrator to update the server policy definitions.

Cause: The server policy may have changed in such a way that the user is no longer able to boot the server.

Action: Reboot the server from the administrative user account or contact the system administrator to update the server policy definitions.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090405: Can only initialize the SecurityService once.

Cause: The initialize method of the Security Service Manager was called more than once.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090407: Invalid security configuration, no default security realm found.

Cause: A default security realm is not defined.

Action: Set one of the configured security realms as the default (active) security realm by setting the Default Realm attribute at the domain.
Level: 1

Type: ERROR

Impact: Security

BEA-090408: Security configuration is unavailable.

Cause: The security configuration MBean was null.

Action: Verify that the SecurityConfiguration MBean is defined in the config.xml file.
Level: 1

Type: ERROR

Impact: Security

BEA-090409: Security credential is unavailable, a credential value must be supplied for the Security configuration.

Cause: The Credential attribute is invalid.

Action: Set the Credential attribute for the security configuration.
Level: 1

Type: ERROR

Impact: Security

BEA-090410: Invalid security realm name: {0}

Cause: The Realm MBean is null.

Action: Verify that the security realm name {0} refers to a valid configured security realm.
Level: 1

Type: ERROR

Impact: Security

BEA-090411: Security Realm [{0}] is improperly configured.

Cause: One or more exceptions occurred when the security realm was validated.

Action: Read the exception text and correct the configuration of the security realm.
Level: 1

Type: ERROR

Impact: Security

BEA-090412: Failed to initialize realm: {0}.

Cause: No security services were found in the security realm.

Action: Configure an Authentication, Authorization, Adjudication, Role Mapping, and Credential Mapping provider in the security realm.
Level: 1

Type: ERROR

Impact: Security

BEA-090413: No Realm MBean found. Bad configuration, unable to initialize Security.

Cause: A default security realm is not configured.

Action: Set one of the configured security realms as the default (active) security realm by setting the Default Realm attribute at the domain.
Level: 1

Type: ERROR

Impact: Security

BEA-090414: Need to configure at least one RoleMapperMBean.

Cause: The array of Role Mapping providers for this security realm is null or empty.

Action: Configure at least one Role Mapping provider for this security realm.
Level: 1

Type: ERROR

Impact: Security

BEA-090415: Need to configure at least one AuthorizerMBean.

Cause: The array of Authorization providers for this security realm is null or empty.

Action: Configure at least one Authorization provider for this security realm.
Level: 1

Type: ERROR

Impact: Security

BEA-090416: Cannot configure the Keystore providers : {0}

Cause: A Security exception occurred during the get or set of the Alg.Alias.KeyStore property.

Action: Read the exception text in {0} for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090419: Subject "{0}" is not the kernel identity.

Cause: The current subject is not the kernel identity.

Action: Verify that the subject in {0} is the correct identity. If so, this exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090420: Security provider error: providerClassName {0} creation exception.

Cause: An Instantiation exception or an IllegalAccess exception occurred while creating and initializing the security provider.

Action: Read the associated exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090421: Security provider error: providerClassName {0} not found.

Cause: A ClassNotFound exception occurred when loading the security provider {0}.

Action: Ensure that the class name in {0} is present. Read the associated exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090423: The Server {0} was unable to find the server certificate file {1} specified by the SSL ServerCertificateFileName attribute.

Cause: The server certificate file was not found.

Action: Verify that the Server Certificate File attribute for server is specified correctly.
Level: 1

Type: ERROR

Impact: Security

BEA-090424: Cannot find the private key with alias {0} in the keystore at location {1}.

Cause: The alias was not found.

Action: Verify that the alias specified in the Server Private Key Alias attribute. Also, verify the contents of the keystore.
Level: 1

Type: ERROR

Impact: Security

BEA-090425: Cannot read private key file {0}. Exception is {1}

Cause: An I/O exception was thrown when loading the private key.

Action: Read the exception text in {1} for more information in diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090426: Cannot read private key from file {0}. Ensure that the password specified in environment property {1} is valid. Exception is {2}

Cause: A KeyManagement exception occurred when loading the private key.

Action: Verify that the password specified in environment property {1}. Verify the format of the private key. Read the exception text in {2} for more information in diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090427: The server {0} was unable to find private key in the file {1} specified by the SSL ServerKeyFileName attribute.

Cause: The file {1} could not be found.

Action: Modify the Server Key File Name attribute to specify a file that exists.
Level: 1

Type: ERROR

Impact: Security

BEA-090428: Cannot call setJava2SecurityMode more than once.

Cause: The setJava2SecurityMode method can only be called once.

Action: Ensure that the setJava2SecurityMode method is only called once.
Level: 1

Type: ERROR

Impact: Security

BEA-090431: Received a null user name.

Cause: The user name cannot be null.

Action: Verify that the specified username is not null.
Level: 1

Type: ERROR

Impact: Security

BEA-090433: Inconsistent InvalidLogin record

Cause: The vector of failures is null.

Action: This exception indicates an internal coding error in the server. Contact My Oracle support.
Level: 1

Type: ERROR

Impact: Security

BEA-090434: Enumerator returned a null element for a key.

Cause: The invalid login information entry is null.

Action: Check the list of locked out users and unlock any users manually. Reboot the server if necessary. This exception indicates an internal coding error in the server. Contact Oracle support.
Level: 1

Type: ERROR

Impact: Security

BEA-090435: Subject {0} does not have permission to unlock user {1} in security realm {2}.

Cause: No permission to unlock the user.

Action: Use an identity that does have permission to unlock this user.
Level: 1

Type: ERROR

Impact: Security

BEA-090436: Inconsistent hashtable, key exists but not value.

Cause: The invalid login information entry is null.

Action: Check the list of locked out users and unlock any users manually. Reboot the server if necessary. This exception indicates an internal coding error in the server. Contact Oracle support.
Level: 1

Type: ERROR

Impact: Security

BEA-090437: Security service is unavailable.

Cause: The authentication service is null.

Action: If a security realm name is specified in the login method, verify that the name of the security realm is correct. Otherwise, this exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090438: Invalid parameter

Cause: The user, password, or output directory is null or a zero length string.

Action: Pass in a valid user, password, and output directory.
Level: 1

Type: ERROR

Impact: Security

BEA-090439: Invalid file parameter {0} specified for adminstrator account creation.

Cause: Either the template file does not exist or is not a file, or the output directory does not exist or is not a directory.

Action: Pass in a valid template file and a valid output directory.
Level: 1

Type: ERROR

Impact: Security

BEA-090440: Encryption error

Cause: The encrypted password was null.

Action: Verify that a non-zero length password was passed to the wizard.
Level: 1

Type: ERROR

Impact: Security

BEA-090442: location null or empty

Cause: A keystore filename cannot be null or a zero length string.

Action: Set the keystore location to a valid filename.
Level: 1

Type: ERROR

Impact: Security

BEA-090443: null file

Cause: The load and store methods require a non-null filename.

Action: Pass a valid filename to the keystore load or store method.
Level: 1

Type: ERROR

Impact: Security

BEA-090444: null keystore

Cause: A valid keystore is required for the store method. It cannot be null.

Action: Pass in a non-null keystore to the store method.
Level: 1

Type: ERROR

Impact: Security

BEA-090445: null or empty passphrase

Cause: A passphrase is required for the store method. It cannot be null or a zero length string.

Action: Pass in a valid passphrase.
Level: 1

Type: ERROR

Impact: Security

BEA-090446: Invalid base template

Cause: The file did not contain the appropriate templates for the user or password.

Action: If the Domain Configuration wizard was used, this exception indicates an internal coding error in the server. Contact My Oracle Support. If the Domain Configuration wizard is not being used, verify the contents of the specified template file.
Level: 1

Type: ERROR

Impact: Security

BEA-090447: invalid flag value {0}

Cause: The value specified for the LoginModule control flag is not supported.

Action: Pass in a valid value for the LoginModule control flag. Valid values are REQUIRED, OPTIONAL, REQUISITE, or SUFFICIENT.
Level: 1

Type: ERROR

Impact: Security

BEA-090448: Invalid Format: {0}

Cause: Import format was either null, zero length, or not supported by this provider.

Action: Pass in a supported format.
Level: 1

Type: ERROR

Impact: Security

BEA-090449: Invalid constraints

Cause: Constraints are not supported.

Action: Do not pass constraints to the provider.
Level: 1

Type: ERROR

Impact: Security

BEA-090450: Invalid name supplied

Cause: The filename, domain name, or security realm name cannot be null.

Action: Pass a non null filename, domain name, or security realm name.
Level: 1

Type: ERROR

Impact: Security

BEA-090451: Unable to read file: {0}

Cause: The import file cannot be read.

Action: Check the import file.
Level: 1

Type: ERROR

Impact: Security

BEA-090452: Import is only available on the Administration Server.

Cause: Import operation was attempted on a Managed Server.

Action: Run the MBean client on the Administration Server.
Level: 1

Type: ERROR

Impact: Security

BEA-090453: Import file error

Cause: An IO exception occurred while importing from the file.

Action: Verify the import filename. Read the exception text or the associated log message for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090454: No base data to export

Cause: The base DN to export from is null or empty.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090455: Export File Error

Cause: An I/O exception occurred while exporting to the file.

Action: Verify the export filename. Read the exception text or the associated log message for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090456: Three arguments are required.

Cause: Three arguments are not specified.

Action: Verify the signature condition in the Administration Console to ensure that three arguments are specified.
Level: 1

Type: ERROR

Impact: Security

BEA-090457: Type must be {0} or {1} value is {2}.

Cause: The Type argument is not valid.

Action: Verify the signature condition in the Administration Console to ensure that the Type argument is @quot;user@quot; or @quot;group@quot;.
Level: 1

Type: ERROR

Impact: Security

BEA-090458: Signature type cannot be null.

Cause: The Signature type value cannot be null.

Action: Verify the signature condition in the Administration Console to ensure that the signature type argument is not null.
Level: 1

Type: ERROR

Impact: Security

BEA-090459: Signed by cannot be null.

Cause: The Signed by value cannot be null.

Action: Verify the signature condition in the Administration Console to ensure that the Signed by argument is not null.
Level: 1

Type: ERROR

Impact: Security

BEA-090461: Class not Found {0}

Cause: An class not found exception occurred when getting an instance of the wrapper class.

Action: Read the exception text in {0} for more information on diagnosing the problem and determining which class was not found.
Level: 1

Type: ERROR

Impact: Security

BEA-090462: Illegal access on context wrapper class {0}

Cause: An illegal access exception occurred when getting an instance of the wrapper class.

Action: Read the exception text in {0} for more information on diagnosing the problem and determining which class was not found.
Level: 1

Type: ERROR

Impact: Security

BEA-090463: Instantiation exception on context wrapper class {0}

Cause: An instantiation exception occurred when getting an instance of the wrapper class.

Action: Read the exception text in {0} for more information on diagnosing the problem and determining which class was not found.
Level: 1

Type: ERROR

Impact: Security

BEA-090464: Problem accessing private key

Cause: A key management exception occurred when adding the private key and certificates to the SSL identity.

Action: Verify the private key. Read the exception text in {0} for more information on diagnosing the problem and determining which class was not found.
Level: 1

Type: ERROR

Impact: Security

BEA-090465: Problem with certificate chain {0}

Cause: A certificate exception occurred when adding the private key and certificates to the SSL identity.

Action: Verify the certificates. Read the exception text in {0} for more information on diagnosing the problem and determining which class was not found.
Level: 1

Type: ERROR

Impact: Security

BEA-090466: Assertion: illegal keystores value: {0}

Cause: The keystore attribute is not valid.

Action: Verify that value {0} is one of the legalvalues listed in the Server MBean Keystores attribute.
Level: 1

Type: ERROR

Impact: Security

BEA-090467: problem with connection filter

Cause: An exception occurred while calling the setRules method.

Action: Verify that the connection file class is specified correctly and present in the classpath. Verify that the setRules method is implemented correctly. Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090468: Set the AuditProviderClassName attribute to a valid value

Cause: An exception occurred while loading the class.

Action: Verify that the class is specified correctly and present in the classpath. Read the exception text from the log message for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090469: Invalid file format

Cause: LDIF template file did not contain any substitution entries and does not have the correct file format.

Action: Verify that the file specified to the import operation is really an LDIF template file produced by an export operation.
Level: 1

Type: ERROR

Impact: Security

BEA-090470: Inconsistent security configuration, the {0} security realm has been configured to use security data in deployment descriptors but no {1} has been configured with deployment enabled.

Cause: The {0} security realm has been configured to use security data in deployment descriptors but no {1} has been configured with deployment enabled.

Action: Either uncheck the "Ignore security data in deployment descriptors" attribute for the security realm to ignore all deployment descriptor security information or configure at least one {1} to have deployment enabled.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090473: DefaultAuthorizerImpl search failed: {0}

Cause: An exception occurred when trying to access the data store.

Action: Look at the exception text in {0} for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090474: Unable to create temporary file: {0}

Cause: The java.io.tmpdir system property is not set correctly or the temporary directory is not writeable.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090475: Plaintext data for protocol {0} was received from peer {1} instead of an SSL handshake.

Cause: A peer is trying to send plaintext data directly instead of using SSL.

Action: Check the port and protocol settings on the peer that is trying to connect. It may be pointing to the SSL port by mistake or it may be specifying a plaintext protocol by mistake.
Level: 1

Type: WARNING

Impact: Security

BEA-090476: Invalid/unknown SSL header was received from peer {0} during SSL handshake.

Cause: A peer is either sending invalid data, trying to connect using a newer version of SSL that is incompatible with the version of SSL used by WebLogic Server, or is trying to connect using plaintext data from a protocol for which WebLogic Server does not check.

Action: Check the peer that is trying to connect. It may be trying to connect using a plaintext protocol over SSL by mistake, or it may be using some newer incompatible version of SSL.
Level: 1

Type: WARNING

Impact: Security

BEA-090477: Certificate chain received from {0} was not trusted causing SSL handshake failure.

Cause: A peer presented a certificate chain to the server that the server does not trust.

Action: Check the certificate chain to determine if it should be trusted or not. If it should be trusted, then update the server trusted CA configuration to trust the CA certificate that signed the peer certificate chain.
Level: 1

Type: WARNING

Impact: Security

BEA-090478: Certificate chain received from {0} was not signed properly causing SSL handshake failure.

Cause: A peer presented a certificate chain to the server that was not signed correctly.

Action: Correct the peer certificate chain.
Level: 1

Type: WARNING

Impact: Security

BEA-090479: Certificate chain received from {0} failed date validity checks.

Cause: A peer presented a certificate chain to the server that is either not yet valid or has expired.

Action: Correct the peer certificate chain.
Level: 1

Type: WARNING

Impact: Security

BEA-090480: SSL alert ({1}) received from {0}. Check the peer SSL configuration, or enable SSL debug tracing on the peer.

Cause: The peer determined something was not correct, sent an alert, and ended the SSL session.

Action: Check the peer to determine why it sent the alert and what alert it believes it sent. This action may require enabling SSL debug tracing to determine the exact cause.
Level: 1

Type: WARNING

Impact: Security

BEA-090481: NO_CERTIFICATE alert was received from {0}. Verify that the SSL configuration has a proper SSL certificate chain and private key specified.

Cause: The SSL configuration for this server needs to supply a certificate chain.

Action: If using one-way SSL, verify that the certificate chain and private key are being specified for the SSL server. If using two-way SSL, verify that the certificate chain and private key are being specified for both the SSL server and the client.
Level: 1

Type: WARNING

Impact: Security

BEA-090482: BAD_CERTIFICATE alert was received from {0}. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason for which the certificate was rejected.

Cause: The certificate chain sent to the peer may not be valid, or the peer may not be configured to accept the certificates.

Action: Check the peer configuration to see if the certificate chain was rejected because the certificate was not trusted or because there was a hostname violation. Verify that the certificate chain sent to the peer had valid dates and had the correct issuer ordering. This action may require enabling SSL debug tracing to determine the exact cause.
Level: 1

Type: WARNING

Impact: Security

BEA-090483: CERTIFICATE_REVOKED alert was received from {0}. The certificate chain sent to the peer was rejected because it was revoked by the certificate authority.

Cause: A certificate in the configured certificate chain was revoked by the certificate authority and is no longer valid.

Action: A new certificate chain needs to be issued by the certificate authority, the SSL configuration then needs to be updated to use the new certificate chain and the new private key that corresponds to it.
Level: 1

Type: WARNING

Impact: Security

BEA-090484: CERTIFICATE_EXPIRED alert was received from {0}. A certificate in the certificate chain expired or is not yet valid, or the peer and local machine have a date/time mismatch.

Cause: A certificate in the chain is either expired or is not yet valid. Another possible cause is the peer machine date/time is not set properly causing the check to fail.

Action: Verify the certificate validity and expiration dates in the certificate chain are correct. If they are not, obtain new certificates issued by the certificate authority and update the SSL configuration with the new certificates and private key. If the dates are valid, check the peer machine date/time setup.
Level: 1

Type: WARNING

Impact: Security

BEA-090485: CERTIFICATE_UNKNOWN alert was received from {0}. The peer has an unspecified issue with the certificate. SSL debug tracing should be enabled on the peer to determine what the issue is.

Cause: The exact cause is unclear. To determine the cause, check messages from the peer to see if they explain the problem.

Action: Review the SSL messages from the peer by turning on SSL debug tracing.
Level: 1

Type: WARNING

Impact: Security

BEA-090486: UNSUPPORTED_CERTIFICATE alert was received from {0}. The peer rejected a certificate in the chain because it was an unsupported type. Verify all certificates in the chain are valid X.509 RSA certificates.

Cause: This problem could be caused by an incorrect type of certificate in the certificate chain or the peer not being able to handle certain attributes in a valid certificate.

Action: The certificate chain should first be checked to ensure the certificates are all valid X.509 RSA certificates and are using the proper strength. If that is correct, SSL debug tracing may be required on the peer to see if it gives more detail on what was specifically not supported.
Level: 1

Type: WARNING

Impact: Security

BEA-090487: UNKNOWN_CA alert received from {0}. The peer is rejecting the certificate chain as being untrusted or incomplete.

Cause: The peer is not configured to trust the CA that signed the certificate chain.

Action: Review the certificate chain and the peer trusted CA configuration to determine whether the peer should be trusting the certificate chain or whether a new certificate chain is required that is trusted by the peer.
Level: 1

Type: WARNING

Impact: Security

BEA-090488: PROTOCOL_VERSION alert received from {0}. Check that the peer supports the same level of the SSL/TLS protocol being used (SSL V3.0 and TLS V1.0).

Cause: The peer may not support the same level of the SSL/TLS protocol, or there was some sort of data corruption occurring with the low-level SSL records.

Action: The peer needs to be checked to determine whether it supports SSL V3.0 and TLS V1.0. If it does, SSL debug tracing may be required to see if the SSL record was rejected for another reason.
Level: 1

Type: WARNING

Impact: Security

BEA-090489: NO_RENEGOTIATION alert was received from {0}. The peer does not support renegotiation.

Cause: The peer does not support renegotiation and is responding to a renegotiation request with a warning to indicate it is not supported.

Action: No action is required.
Level: 1

Type: WARNING

Impact: Security

BEA-090490: ACCESS_DENIED alert received from {0}. The peer recognizes the certificate chain but a higher-level access control is rejecting it.

Cause: The peer is likely doing an authorization check, perhaps above the SSL layer and is rejecting the connection because of an authorization check failure.

Action: Check the peer configuration to determine why the authorization check is failing.
Level: 1

Type: WARNING

Impact: Security

BEA-090491: INSUFFICIENT_SECURITY alert received from {0}. The peer requires stronger ciphers to be supported.

Cause: The peer requires stronger ciphers than those specified in the SSL configuration of the server.

Action: Determine the ciphers required by the peer and update the SSL configuration. This update may not be possible if the required ciphers are stronger than allowed by the WebLogic Server license.
Level: 1

Type: WARNING

Impact: Security

BEA-090492: UNEXPECTED_MESSAGE alert received from {0}.

Cause: This message indicates a problem in the SSL implementations or data corruption.

Action: Enable SSL debug tracing on both sides of the SSL connection. Also, check the network for possible problems.
Level: 1

Type: WARNING

Impact: Security

BEA-090493: BAD_RECORD_MAC alert received from {0}. The peer indicated it received a record with an invalid MAC.

Cause: The certificate does not match the private key or data corruption has occurred.

Action: Check the SSL configuration to ensure the certificate and private key match, check the network, and verify the routes between the machines.
Level: 1

Type: WARNING

Impact: Security

BEA-090494: DECRYPTION_FAILED alert received from {0}. The peer detected errors when decrypting.

Cause: A cryptography error or a data corruption error.

Action: Check both sides of the SSL connection for relevant error information, check the network, and verify the routes between the machines.
Level: 1

Type: WARNING

Impact: Security

BEA-090495: RECORD_OVERFLOW alert received from {0}. The peer received an invalid record with a length greater than allowed.

Cause: A problem in the SSL implementation or a data corruption error.

Action: Check both sides of the SSL connection for relevant error information, check the network, and verify the routes between the machines.
Level: 1

Type: WARNING

Impact: Security

BEA-090496: DECOMPRESSION_FAILURE alert received from {0}. The peer was unable to decompress data.

Cause: WebLogic Server does not support data compression. This message likely indicates a data corruption problem.

Action: Check both sides of the SSL connection for any relevant error information, check the network, and verify the routes between the machines.
Level: 1

Type: WARNING

Impact: Security

BEA-090497: HANDSHAKE_FAILURE alert received from {0}. Check both sides of the SSL configuration for mismatches in supported ciphers, supported protocol versions, trusted CAs, and hostname verification settings.

Cause: There is a mismatch in the SSL configurations.

Action: Check both sides of the SSL configuration for mismatches in supported ciphers, supported protocol versions, trusted CAs, and hostname verification settings. SSL Debug tracing may be needed on both sides to determine the exact cause.
Level: 1

Type: WARNING

Impact: Security

BEA-090498: ILLEGAL_PARAMETER alert received from {0}.

Cause: This message is most likely caused by a data corruption error.

Action: Check both sides of the SSL connection for relevant error information, check the network, and verify the routes between the machines.
Level: 1

Type: WARNING

Impact: Security

BEA-090499: DECODE_ERROR alert received from {0}.

Cause: This message is most likely caused by a data corruption error.

Action: Check both sides of the SSL connection for relevant error information, check the network, and verify the routes between the machines.
Level: 1

Type: WARNING

Impact: Security

BEA-090500: DECRYPT_ERROR alert received from {0}. A decryption error occurred during the SSL handshake.

Cause: This message is most likely caused by a data corruption error.

Action: Check both sides of the SSL connection for relevant error information, check the network, and verify the routes between the machines.
Level: 1

Type: WARNING

Impact: Security

BEA-090501: EXPORT_RESTRICTION alert received from {0}.

Cause: This message could be caused by an SSL configuration mismatch between the implementations.

Action: Check both sides of the SSL connection for relevant error information, check the network, and verify the routes between the machines.
Level: 1

Type: WARNING

Impact: Security

BEA-090502: INTERNAL_ERROR alert received from {0}. Check for unrelated failures such as insufficient resources.

Cause: There may be failures because of an insufficient resource (memory, file descriptors, or other resource).

Action: Check both sides of the SSL connection for relevant error information.
Level: 1

Type: WARNING

Impact: Security

BEA-090503: The public key from the configured server certificate and the configured server private key do not match.

Cause: The server SSL configuration is incorrect. Either the certificate, the private key, or both are incorrectly specified.

Action: Check the SSL configuration. Check that the server certificate corresponds to the server private key.
Level: 1

Type: WARNING

Impact: Security

BEA-090504: Certificate chain received from {0} failed hostname verification check. Certificate contained {1} but check expected {2}

Cause: A peer presented a certificate chain to the server that did not pass the hostname verification check.

Action: Check that the hostname in the peer certificate matches the hostname expected by the hostname verifier.
Level: 1

Type: WARNING

Impact: Security

BEA-090505: No certificate chain was received from {0}, hostname verification check failed.

Cause: The peer is most likely not configured to support a cipher that presents a certificate.

Action: Check the supported ciphers on the peer and ensure that it supports a cipher that provides a certificate.
Level: 1

Type: WARNING

Impact: Security

BEA-090506: Unspecified exception occurred handling hostname verification for {0}.

Cause: The hostname verifier failed.

Action: Enable SSL debug tracing to determine the exact exception. If this is a custom hostname verifier, there may be coding problems in the implementation.
Level: 1

Type: WARNING

Impact: Security

BEA-090508: Certificate chain received from {0} was incomplete.

Cause: A peer presented a certificate chain to the server that was incomplete (it did not contain a trusted CA).

Action: Check the peer certificate chain to determine if it should be trusted or not. If it should be trusted, then update the server trusted CA configuration to trust the CA that signed the certificate chain. If the chain was incomplete, correct the chain.
Level: 1

Type: WARNING

Impact: Security

BEA-090509: The SSL ListenPort attribute {0} cannot be the same as the non-secure ListenPort for the server.

Cause: The same value was specified for the server Listen port and the SSL Listen port.

Action: Correct the configuration of the SSL Listen port. The value must be different that than the server Listen port.
Level: 1

Type: ERROR

Impact: Security

BEA-090510: Error: username not specified.

Cause: The username supplied in the NameCallback is null.

Action: Set a username when a NameCallback is passed to the CallbackHandler.
Level: 1

Type: ERROR

Impact: Security

BEA-090511: The following exception has occurred:

Cause: An error condition has occurred.

Action: Read the associated exception in the log or in the application to determine the problem. In general, the stack trace can be used to debug an existing problem.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090513: ServerIdentity failed validation, downgrading to anonymous.

Cause: Trust has not been properly established between two domains. If the domains are not configured properly, a hacker could make an attempt to guess the server identity for this domain.

Action: See the documentation on "Enabling Trust Between WebLogic Domains" at http://www.oracle.com/technology/products/weblogic/index.html.
Level: 1

Type: ERROR

Impact: Security

BEA-090514: The server certificate chain has settings that might cause it to be rejected by peers during SSL handshaking. No action is required unless peers are rejecting the certificate chain.

Cause: The server certificate chain has CA certificates that have BasicConstraints settings which are either missing or set in such a way that a peer may reject it during SSL handshaking.

Action: No action is necessarily required. If peers have trouble handshaking, check that the BasicConstraints settings in the CA certificates in the chain are specified correctly.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090515: The certificate chain could not be completely checked for issues that could cause it to be rejected by a peer during SSL handshaking. No action is required unless peers are rejecting the certificate chain.

Cause: The configured certificate chain was incomplete.

Action: No action is necessarily required. If the entire certificate chain is to be checked, ensure that the entire certificate chain is specified in the configuration.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090516: The {0} provider has pre-existing LDAP data.

Cause: The provider was initialized during a previous boot of the WebLogic Server instance.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090518: Could not decrypt the {1} attribute value of {2} from the file {0}. If an encrypted attribute was copied from boot.properties from another domain into {0}, change the encrypted attribute to its clear text value, and then restart the server. The attribute will be encrypted again. Otherwise, change all encrypted attributes to their clear text values, then restart the server. All encryptable attributes will be encrypted again. The decryption failed with the exception {3}.

Cause: An invalid encrypted value was found in boot.properties.

Action: If an encrypted attribute was copied from boot.properties from another domain into {0}, change the encrypted attribute to its clear text value, and then restart the server. The attribute will be encrypted again. Otherwise, change all encrypted attributes to their clear text values, then restart the server. All encryptable attributes will be encrypted again.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090519: The realm {0} is not properly configured. Follow the directions in subsequent errors to correctly configure the realm.

Cause: See the subsequent errors.

Action: Follow the directions in the subsequent errors to correctly configure the realm.
Level: 1

Type: WARNING

Impact: Security

BEA-090520: The realm {0} does not have an authenticator configured. To correct the problem, configure an authenticator.

Cause: The realm {0} does not have an authenticator configured.

Action: To correct the problem, configure an authenticator.
Level: 1

Type: WARNING

Impact: Security

BEA-090521: The realm {0} does not have a role mapper configured. To correct the problem, configure a role mapper.

Cause: The realm {0} does not have a role mapper configured.

Action: To correct the problem, configure a role mapper.
Level: 1

Type: WARNING

Impact: Security

BEA-090522: The realm {0} does not have a deployable role mapper configured. To correct the problem, configure a deployable role mapper.

Cause: The realm {0} does not have a deployable role mapper configured.

Action: To correct the problem, configure a deployable role mapper.
Level: 1

Type: WARNING

Impact: Security

BEA-090523: None of the deployable role mappers in realm {0} have deployments enabled. To correct the problem, enable deployments in one of the deployable role mappers.

Cause: None of the deployable role mappers in realm {0} have deployments enabled.

Action: To correct the problem, enable deployments in one of the deployable role mappers.
Level: 1

Type: WARNING

Impact: Security

BEA-090524: The realm {0} does not have an authorizer configured. To correct the problem, configure an authorizer.

Cause: The realm {0} does not have an authorizer configured.

Action: To correct the problem, configure an authorizer.
Level: 1

Type: WARNING

Impact: Security

BEA-090525: The realm {0} does not have a deployable authorizer configured. To correct the problem, configure a deployable authorizer.

Cause: The realm {0} does not have a deployable authorizer configured.

Action: To correct the problem, configure a deployable authorizer.
Level: 1

Type: WARNING

Impact: Security

BEA-090526: None of the deployable authorizers in realm {0} have deployments enabled. To correct the problem, enable deployments in one of the deployable authorizers.

Cause: None of the deployable authorizers in realm {0} have deployments enabled.

Action: To correct the problem, enable deployments in one of the deployable authorizers.
Level: 1

Type: WARNING

Impact: Security

BEA-090527: The realm {0} does not have a credential mapper configured. To correct the problem, configure a credential mapper.

Cause: The realm {0} does not have a credential mapper configured.

Action: To correct the problem, configure a credential mapper.
Level: 1

Type: WARNING

Impact: Security

BEA-090530: The realm {0} has more than one identity asserter configured with the token type {1} selected as an active type. To correct the problem, decide which of the identity asserters should handle this token type. Set it as an active type in that identity asserter, and unset it as an active type for all the other identity asserters.

Cause: The realm {0} has more than one identity asserter configured with the token type {1} selected as an active type.

Action: To correct the problem, decide which of the identity asserters should handle this token type. Set it as an active type in that identity asserter, and unset it as an active type for all the other identity asserters.
Level: 1

Type: WARNING

Impact: Security

BEA-090531: The realm {0} has multiple authorizers but no adjudicator. To correct the problem, configure an adjudicator.

Cause: The realm {0} has multiple authorizers but no adjudicator.

Action: To correct the problem, configure an adjudicator.
Level: 1

Type: WARNING

Impact: Security

BEA-090532: The realm {0} has a realm adapter adjudicator but no realm adapter authorizer. To correct the problem, configure a realm adapter authorizer.

Cause: The realm {0} has a realm adapter adjudicator but no realm adapter authorizer.

Action: To correct the problem, configure a realm adapter authorizer.
Level: 1

Type: WARNING

Impact: Security

BEA-090533: The realm {0} has a realm adapter adjudicator but no default authorizer. To correct the problem, configure a default authorizer.

Cause: The realm {0} has a realm adapter adjudicator but no default authorizer.

Action: To correct the problem, configure a default authorizer.
Level: 1

Type: WARNING

Impact: Security

BEA-090534: The realm {0} has a realm adapter adjudicator but multiple default authorizers. To correct the problem, remove all the default authorizers except one.

Cause: The realm {0} has a realm adapter adjudicator but multiple default authorizers.

Action: To correct the problem, remove all the default authorizers except one.
Level: 1

Type: WARNING

Impact: Security

BEA-090535: The realm {0} has a realm adapter adjudicator but is using an authorizer that is neither a realm adapter authorizer nor a default authorizer. To correct the problem, remove all authorizers except the realm adapter authorizer and the default authorizer.

Cause: The realm {0} has a realm adapter adjudicator but is using an authorizer that is neither a realm adapter authorizer nor a default authorizer.

Action: To correct the problem, remove all authorizers except the realm adapter authorizer and the default authorizer.
Level: 1

Type: WARNING

Impact: Security

BEA-090536: The realm {0} has multiple realm adapter authorizers. To correct the problem, remove all the realm adapter authorizers except one.

Cause: The realm {0} has multiple realm adapter authorizers.

Action: To correct the problem, remove all the realm adapter authorizers except one.
Level: 1

Type: WARNING

Impact: Security

BEA-090537: The realm {0} has multiple realm adapter authenticators. To correct the problem, remove all the realm adapter authenticators except one.

Cause: The realm {0} has multiple realm adapter authenticators.

Action: To correct the problem, remove all the realm adapter authenticators except one.
Level: 1

Type: WARNING

Impact: Security

BEA-090538: The realm {0} has a realm adapter authorizer but no realm adapter authenticator. To correct the problem, configure a realm adapter authenticator.

Cause: The realm {0} has a realm adapter authorizer but no realm adapter authenticator.

Action: To correct the problem, configure a realm adapter authenticator.
Level: 1

Type: WARNING

Impact: Security

BEA-090539: The realm {0} has keystore configured that is not a default keystore. To correct the problem, remove the non-default keystore.

Cause: The realm {0} has keystore configured that is not a default keystore.

Action: To correct the problem, remove the non-default keystore.
Level: 1

Type: WARNING

Impact: Security

BEA-090540: The realm {0} has more than one default keystore configured for trusted CAs. To correct the problem, ensure that only one default keystore provider has its root CA keystore location configured.

Cause: The realm {0} has more than one default keystore configured for trusted CAs.

Action: To correct the problem, ensure that only one default keystore provider has its root CA keystore location configured.
Level: 1

Type: WARNING

Impact: Security

BEA-090541: The realm {0} has more than one default keystore configured for private keys. To correct the problem, ensure that only one default keystore provider has its private key keystore location configured.

Cause: The realm {0} has more than one default keystore configured for private keys.

Action: To correct the problem, ensure that only one default keystore provider has its private key keystore location configured.
Level: 1

Type: WARNING

Impact: Security

BEA-090542: Certificate chain received from {0} was not trusted, causing SSL handshake failure. Check the certificate chain to determine whethr or not it should be trusted. If it should be trusted, then update the client trusted CA configuration to trust the CA certificate that signed the peer certificate chain. If you are connecting to a WebLogic Server instance that is using demo certificates (the default WebLogic Server behavior), and you want this client to trust demo certificates, then specify -Dweblogic.security.TrustKeyStore=DemoTrust on the command line for this client.

Cause: A peer presented a certificate chain to the server which the server does not trust.

Action: Check the certificate chain to determine if it should be trusted or not. If it should be trusted, then update the client trusted CA configuration to trust the CA certificate that signed the peer certificate chain. If you are connecting to a WLS server that is using demo certificates (the default WLS server behavior), and you want this client to trust demo certificates, then specify -Dweblogic.security.TrustKeyStore=DemoTrust on the command line for this client.
Level: 1

Type: WARNING

Impact: Security

BEA-090543: Certificate chain received from {0} was incomplete. Check the peer certificate chain to determine if it should be trusted or not. If it should be trusted, then update the client trusted CA configuration to trust the CA that signed the certificate chain. If the chain was incomplete, correct the chain. If you are connecting to a WLS server that is using demo certificates (the default WLS server behavior), and you want this client to trust demo certificates, then specify -Dweblogic.security.TrustKeyStore=DemoTrust on the command line for this client.

Cause: A peer presented a certificate chain to the server that was incomplete (it did not contain a trusted CA).

Action: Check the peer certificate chain to determine whether or not it should be trusted. If it should be trusted, then update the client trusted CA configuration to trust the CA that signed the certificate chain. If the chain was incomplete, correct the chain. If you are connecting to a WebLogic Server instance that is using demo certificates (the default WebLogic Server behavior), and you want this client to trust demo certificates, then specify -Dweblogic.security.TrustKeyStore=DemoTrust on the command line for this client.
Level: 1

Type: WARNING

Impact: Security

BEA-090544: No search filter was supplied.

Cause: The search filter was empty or not supplied.

Action: Supply a search filter when exporting data.
Level: 1

Type: ERROR

Impact: Security

BEA-090545: DefaultRoleMapperImpl search failed: {0}.

Cause: An exception occurred when trying to access the data store.

Action: Look at the exception text in {0} for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090546: The server is configured to use custom identity and command line trust, but either demo trust or no trust was specified on the command line or in boot.properties.

Cause: The server's KeyStore value in config.xml is CustomIdentityAndCommandLineTrust, but, on the command line to boot the server or in boot.properties, either no trust or DemoTrust was specified.

Action: To correct the problem, either specify -Dweblogic.security.TrustKeyStore=JavaStandardTrust or -Dweblogic.security.TrustKeyStore=CustomTrust and -Dweblogic.security.CustomTrustKeyStoreFileName on the command line when booting the server (or specify TrustKeyStore=JavaStandardTrust or TrustKeyStore=CustomTrust and CustomTrustKeyStoreFileName in boot.properties).
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090547: The certificate chain received from {0} contained a V3 CA certificate which had basic constraints that were not marked critical. This is being rejected due to the strict enforcement of basic constraints.

Cause: Strict basic constraints checking was explicitly enabled, and a certificate chain received by the peer contained a CA that failed due to the strict check but would have passed the strong check.

Action: If strict compliance of RFC 2459 for basic constraints is really required, then the peer certificate chain was correctly rejected and needs to be corrected. If strict compliance is not really required, consider setting the constraints checking back to the default value of strong to accept the certificate chain.
Level: 1

Type: WARNING

Impact: Security

BEA-090548: The certificate chain received from {0} contained a V3 CA certificate that was missing the basic constraints extension

Cause: The certificate chain received by the peer contained a V3 CA certificate that does not contain a basic constraints extension indicating that it really is a CA. This is rejected by the basic constraints checking for strong and strict, which protects against a specific certificate chain attack on SSL.

Action: The peer certificate chain needs to be looked at carefully to determine which CA was missing the basic constraints extension. If the certificate chain really is from a valid peer, you should look at updating the peer certificate chain with valid CA certificates. If this is not possible, you can disable the basic constraints checking to allow the certificate chain to be accepted and allows this vulnerability to be exploited.
Level: 1

Type: WARNING

Impact: Security

BEA-090549: The certificate chain received from {0} contained a V3 CA certificate that did not indicate it really is a CA.

Cause: The certificate chain received by the peer contained a V3 CA certificate that contained a basic constraints extension which was not marked as being a CA. This is rejected by the basic constraints checking for strong and strict, which protects against a specific certificate chain attack on SSL.

Action: The peer certificate chain needs to be looked at carefully to determine which CA is not correct. If the certificate chain really is from a valid peer, you should look at updating the peer certificate chain with valid CA certificates. If this is not possible, you can disable the basic constraints checking to allow the certificate chain to be accepted and allows this vulnerability to be exploited.
Level: 1

Type: WARNING

Impact: Security

BEA-090550: The certificate chain received from {0} contained a V3 CA certificate that indicated a certificate chain path length in the basic constraints that was exceeded.

Cause: The certificate chain received by the peer contained a V3 CA certificate that specified a path length in the basic constraints that was exceeded. This is rejected by the basic constraints checking for strong and strict, which protects against a specific certificate chain attack on SSL.

Action: The peer certificate chain needs to be looked at carefully to determine which CA indicated the path length limit that was exceeded. The path length, if specified, limits how many CA certificates are allowed to follow a CA certificate in a certificate chain. A path length of 0 indicates only an end entity certificate may follow it in the chain, positive values indicate how many CA certificates may be in the chain between that CA and the end entity certificate. If the certificate chain really is from a valid peer, you should look at updating the peer certificate chain with valid CA certificates. If this is not possible, you can disable the basic constraints checking to allow the certificate chain to be accepted and allows this vulnerability to be exploited.
Level: 1

Type: WARNING

Impact: Security

BEA-090551: The certificate chain received from {0} contained a V3 CA certificate that could not be converted to be checked for basic constraints.

Cause: The certificate chain received by the peer contained a V3 CA certificate that could not be converted to a format which allows the basic constraints to be checked. This is rejected by the basic constraints checking for strong and strict, which protects against a specific certificate chain attack on SSL.

Action: The peer certificate chain needs to be looked at carefully to confirm they are valid. If the certificates are all valid, this indicates an internal coding error or limitation in the server. Contact Oracle support. If the certificate can not be processed, you can disable the basic constraints checking as a workaround to allow the certificate chain to be accepted and allows this vulnerability to be exploited
Level: 1

Type: WARNING

Impact: Security

BEA-090552: The public and private key could not be checked for consistency.

Cause: The failure could be due to a keystore being used to hold the private key that does not allow access to private key material. Hardware keystores generally do not give access to the private key material that is needed to perform this operation.

Action: If a keystore is being used the warning should be ignored. If handshaking errors occurs with all clients, check that the private key and public key match.
Level: 1

Type: WARNING

Impact: Security

BEA-090554: Set the RealmClassName attribute of the BasicRealm {0} used by the CachingRealm to a valid value.

Cause: The RealmClassName attribute was not properly configured.

Action: Verify that the class is specified correctly and is present in the classpath. Read the exception text from the log message for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090560: Could not load the {0} class named {1}. The exception was {3}. The class was specified via the {2} system property value.

Cause: Could not load the {0} class named {1}.

Action: Ensure that the {2} system property is set to the proper {0} class. Also ensure that the class is in the classpath.
Level: 1

Type: ERROR

Impact: Security

BEA-090561: Could not instantiate a {0} of class {1}. The exception received is {3}. The class was specified via the {2} system property value.

Cause: Could not instantiate a {0} of class {1}.

Action: Ensure that the {2} system property is set to the proper {0} class. Also ensure that the class is a correct {0} implementation.
Level: 1

Type: ERROR

Impact: Security

BEA-090562: Could not create a {0} of class {1} because it is not assignable as a {2}. The class was specified via the {3} system property value.

Cause: Could not create a {0} of class {1} because it is not assignable as a {2}.

Action: Ensure that the {3} system property is set to the proper {0} class. Also ensure that the class is a correct {0} implementation.
Level: 1

Type: ERROR

Impact: Security

BEA-090563: Cannot create instance of Hostname Verifier {0}.

Cause: The class {0} was not found, does not have a public constructor without arguments, or has thrown an exception in its constructor.

Action: Ensure that the {0} class is in the class path, and has a public constructor without arguments.
Level: 1

Type: ERROR

Impact: Security

BEA-090564: Specified HostnameVerifier class {0} is invalid. It does not implement weblogic.security.SSL.HostnameVerifier interface.

Cause: An invalid HostnameVerifier class specified.

Action: Specify a different HostnameVerifier class, or ensure that the {0} class implements weblogic.security.SSL.HostnameVerifier interface.
Level: 1

Type: ERROR

Impact: Security

BEA-090565: The server SSL identity key algorithm {0} is not supported.

Cause: The server SSL identity key algorithm {0} is not supported.

Action: Configure the server identity with a different key pair using a supported RSA algorithm.
Level: 1

Type: WARNING

Impact: Security

BEA-090566: The certificate chain received from {0} contained a V3 certificate with unrecognized critical extension: {1}.

Cause: The certificate cannot be validated because it contains an unrecognized critical extension.

Action: The peer certificate chain needs to be looked at carefully to confirm that they are valid. If the certificates are all valid, this indicates an internal coding error or limitation in the server. Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: Security

BEA-090567: The certificate chain received from {0} contained a V3 certificate for which key usage constraints forbid its key use by the key agreement algorithm.

Cause: Certificate key usage constraints forbid certificate key use in a quality required by the key agreement algorithm.

Action: The peer certificate chain needs to be looked at carefully to confirm that they are valid. If the certificates are all valid, this indicates an internal coding error or limitation in the server. Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: Security

BEA-090568: Cannot check key usage constraints of certificate received from {0} because of the failure to determine the key agreement algorithm.

Cause: A NoSuchAlgorithmException occurred while trying to obtain the key agreement algorithm.

Action: The peer certificate chain needs to be looked at carefully to confirm that they are valid. If the certificates are all valid, this indicates an internal coding error or limitation in the server. Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: Security

BEA-090569: The certificate chain received from {0} contained a V3 CA certificate for which key usage constraints indicate its key cannot be used to sign certificates.

Cause: One of certificate in the check cannot pass validation check because its key is used to sign another certificate while key usage constraints indicate that it cannot be used for that.

Action: The peer certificate chain needs to be looked at carefully to confirm that they are valid. If the certificates are all valid, this indicates an internal coding error or limitation in the server. Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: Security

BEA-090570: {0} has been specified without enabling the SecurityManager.

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

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

Type: ERROR

Impact: Security

BEA-090571: Successfully loaded the JACC Policy object using {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090572: The javax.security.jacc.policy.provider property points to a non-existant {0} class.

Cause: JACC has been enabled by setting the javax.security.jacc.policy.provider property but the class it points to cannot be found.

Action: Ensure that the class is present or change javax.security.jacc.policy.provider property to point to an existing class.
Level: 1

Type: ERROR

Impact: Security

BEA-090573: {1} exception occurred while attempting to access {0}.

Cause: The class was not accessible.

Action: Check to make sure that the class is accessible.
Level: 1

Type: ERROR

Impact: Security

BEA-090574: {1} exception occurred while attempting to instantiate {0}.

Cause: The class was could not be instantiated.

Action: Check to make sure that the class is instantiatable.
Level: 1

Type: ERROR

Impact: Security

BEA-090575: The {0} class is not an instance of java.security.Policy.

Cause: An non-Policy object was passed as the value of the javax.security.jacc.policy.provider property.

Action: Change javax.security.jacc.policy.provider to point to an instance of a java.security.Policy object.
Level: 1

Type: ERROR

Impact: Security

BEA-090576: A PolicyConfigurationFactory could not be obtained successfully.

Cause: The javax.security.jacc.PolicyConfigurationFactory.provider property may not be set to a valid implementation of PolicyConfigurationFactory.

Action: Change javax.security.jacc.PolicyConfigurationFactory.provider to point to an instance of a javax.security.jacc.PolicyConfigurationFactory object.
Level: 1

Type: ERROR

Impact: Security

BEA-090577: Successfully obtained a {0} PolicyConfigurationFactory.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090578: The JACC provider returned a {0}.

Cause: JACC returned a PolicyContextException.

Action: Look at the details of the PolicyContextException to determine the action to take.
Level: 1

Type: ERROR

Impact: Security

BEA-090579: The javax.security.jacc.PolicyConfigurationFactory.provider property points to a non-existant class {0}.

Cause: JACC has been enabled by setting javax.security.jacc.PolicyConfigurationFactory.provider property but the class it points to cannot be found.

Action: Ensure that the class is present or change javax.security.jacc.PolicyConfigurationFactory.provider property to point to an existing class.
Level: 1

Type: ERROR

Impact: Security

BEA-090580: The CertPathBuilderParameters constructor was passed an illegal realm name.

Cause: The realm name must not be empty or null.

Action: Pass a valid security realm name to the CertPathBuilderParameters constructor.
Level: 1

Type: ERROR

Impact: Security

BEA-090581: The CertPathBuilderParameters constructor was passed an illegal CertPathSelector.

Cause: The CertPathSelector must not be null.

Action: Pass a valid CertPathSelector to the CertPathBuilderParameters constructor.
Level: 1

Type: ERROR

Impact: Security

BEA-090582: The CertPathValidatorParameters constructor was passed an illegal realm name.

Cause: The realm name must not be empty or null.

Action: Pass a valid security realm name to the CertPathValidatorParameters constructor.
Level: 1

Type: ERROR

Impact: Security

BEA-090589: The WLSJDKCertPathBuilder was passed an illegal CertPathParameters.

Cause: The CertPathParameters must be a weblogic.security.pk.CertPathBuilderParameters.

Action: Pass a weblogic.security.pk.CertPathBuilderParameters as the CertPathParameters.
Level: 1

Type: ERROR

Impact: Security

BEA-090590: The WLSJDKCertPathValidator was passed an illegal CertPathParameters.

Cause: The CertPathParameters must be a weblogic.security.pk.CertPathValidatorParameters.

Action: Pass a weblogic.security.pk.CertPathValidatorParameters as the CertPathParameters.
Level: 1

Type: ERROR

Impact: Security

BEA-090591: The realm {0} does not have any Certification Path providers configured. To correct the problem, configure at least one Certification Path provider.

Cause: The realm {0} does not have any Certification Path providers configured.

Action: To correct the problem, configure at least one Certification Path provider.
Level: 1

Type: WARNING

Impact: Security

BEA-090592: The realm {0} does not have a Certification Path builder configured. To correct the problem, select one of the realm"s Certification Path providers as the realm"s Certification Path builder.

Cause: The realm {0} does not have a Certification Path builder configured.

Action: To correct the problem, select one of the realm"s Certification Path providers as the realm"s Certification Path builder.
Level: 1

Type: WARNING

Impact: Security

BEA-090593: The realm {0} has an illegal Certification Path builder configured. To correct the problem, select one of the realm"s Certification Path providers as the realm"s Certification Path builder.

Cause: The realm {0} has an illegal Certification Path builder configured.

Action: To correct the problem, select one of the realm"s Certification Path providers as the realm"s Certification Path builder.
Level: 1

Type: WARNING

Impact: Security

BEA-090598: Unable to update the domain controller list

Cause: The most likely cause is that the attempt to lock the domain controller list for update timed out. This may happen if there are concurrent updates occurring to the configuration for the same provider instance, and the updates are taking a while to execute (perhaps a long domain controller list or slow network).

Action: If this is an update from the Administration Console, and the domain controller list was modified, apply the changes again.
Level: 1

Type: WARNING

Impact: Security

BEA-090599: Unable to initialize the domain controller list

Cause: The domain controller list was not able to be locked for initialization. This should not occur and was likely caused by an internal coding error.

Action: This indicates an internal coding error or limitation in the server. Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: Security

BEA-090600: Failed to retrieve the local machine name.

Cause: There may be a configuration error with either the user account rights required or the local NT machine.

Action: Verify that the user running the server has the specific NT account rights that are required to use the NT authentication provider.
Level: 1

Type: ERROR

Impact: Security

BEA-090601: Cannot access domain controller {0}.

Cause: The domain controller name may not be valid, may be down or unavailable on the network, or the user may not have permission to access it.

Action: If the domain controller is simply down, or temporarily unavailable, it may be retried later on depending on the domain controller retry settings. If the domain controller is available, check that the user account running the server has permission to access the domain controller. This may require logging into the domain controller that failed and verifying the user has been granted access.
Level: 1

Type: WARNING

Impact: Security

BEA-090602: The java and native library versions do not match for the WindowsNTAuthenticator.

Cause: The native library being found and loaded is not in synch with the java portion of the provider.

Action: Verify the correct native library for the WindowsNTAuthenticator is in the PATH and that the correct PATH is being used.
Level: 1

Type: ERROR

Impact: Security

BEA-090615: A CertPathBuilderParameters or CertPathValidatorParameters object was constructed with a list of trusted CAs that includes a null trusted CA.

Cause: A CertPathBuilderParameters or CertPathValidatorParameters object was constructed with a list of trusted CAs that includes a null trusted CA.

Action: Ensure that the list of trusted CAs passed in does not include a null trusted CA.
Level: 1

Type: ERROR

Impact: Security

BEA-090623: Failed to get the default trusted CAs for this server.

Cause: This exception is returned when an exception occurs when finding this server's trusted CAs.

Action: Look at the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090625: Policy context {0} not in open state.

Cause: Policy context must be in open state.

Action: Ensure that the policy context is open before attempting an operation on it that requires an open Policy Context. This indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090626: Received a {0} when attempting to delete Policy Directory {1}.

Cause: Received a {0} when attempting to delete Policy Directory {1}.

Action: Ensure that files in the policy directory are not open.
Level: 1

Type: ERROR

Impact: Security

BEA-090627: Cannot link a PolicyConfiguration to itself.

Cause: Cannot link a PolicyConfiguration to itself.

Action: This indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090628: Cannot have circular policy configuration links.

Cause: A PolicyConfiguration is linked to another PolicyConfiguration which ultimately is linked back to the original PolicyConfiguration. This means that no PolicyConfiguration actually holds the role to principal mapping.

Action: This indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090629: Received a {0} when attempting to use the passed role to principal map for PolicyConfiguration with a ContextID of {1}.

Cause: Received a {0} when attempting to use the passed role to principal map for PolicyConfiguration with a ContextID of {1}. The code attempts to do some simple validation the map.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090631: Unable to create the PolicyWriter directory {0}.

Cause: Unable to create the PolicyWriter directory {0}.

Action: Unable to create the PolicyWriter directory.
Level: 1

Type: ERROR

Impact: Security

BEA-090632: Cannot create {0}. Non directory file already exists with the same name. Please remove it.

Cause: A non directory file already exists with the same name.

Action: Remove the non directory file.
Level: 1

Type: ERROR

Impact: Security

BEA-090633: Cannot open policy file {0}. Received exception {1}.

Cause: If the exception is a FileNotFoundException, the file path name may be too long for the operating system, or the directory may have been deleted before the policy file was written to it.

Action: Try to shorten the file path name if it is too long for the operating system. The error may also occur if the directory has been deleted before the file was written to it.
Level: 1

Type: ERROR

Impact: Security

BEA-090634: Cannot write to policy file {0}. Received exception {1}.

Cause: The file may have been opened for exclusive access by something other than WebLogic Server.

Action: Ensure that the policy file is writable.
Level: 1

Type: ERROR

Impact: Security

BEA-090635: No results

Cause: There are no policies that match the search criteria.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090636: No results

Cause: There are no roles that match the search criteria.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090637: No role name was supplied.

Cause: The role name is null or contains no data.

Action: Specify a valid role name.
Level: 1

Type: ERROR

Impact: Security

BEA-090638: No resource data

Cause: The resource data parameter was not supplied or is empty.

Action: Specify valid resource data.
Level: 1

Type: ERROR

Impact: Security

BEA-090639: No resource type

Cause: The resource type information was not supplied.

Action: Specify a valid resource type.
Level: 1

Type: ERROR

Impact: Security

BEA-090640: No resource identifier

Cause: The resource identifier parameter was not supplied or is empty.

Action: Specify a valid resource identifier.
Level: 1

Type: ERROR

Impact: Security

BEA-090641: No resource keys were found.

Cause: An invalid resource identifier was supplied.

Action: Specify a valid resource identifier.
Level: 1

Type: ERROR

Impact: Security

BEA-090642: Invalid data type for {0} resource key value

Cause: The data type of a resource key value is not valid.

Action: Specify a valid resource key data type value.
Level: 1

Type: ERROR

Impact: Security

BEA-090643: Invalid resource type: "{0}"

Cause: An invalid or unknown resource type was supplied.

Action: Specify a valid resource type.
Level: 1

Type: ERROR

Impact: Security

BEA-090644: Expected resource type: {0}

Cause: An invalid or unknown resource type was supplied.

Action: Verify that a valid resource type was supplied and contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090645: Expected resource key: {0}

Cause: An invalid resource identifier was supplied.

Action: Specify a valid resource identifier.
Level: 1

Type: ERROR

Impact: Security

BEA-090646: Unknown resource key: {0}

Cause: The resource key supplied in the resource data is unknown.

Action: Specify only resource keys valid for a specific resource type.
Level: 1

Type: ERROR

Impact: Security

BEA-090647: Invalid application name

Cause: The application name parameter was empty or contains invalid values.

Action: Specify a valid application name.
Level: 1

Type: ERROR

Impact: Security

BEA-090648: Invalid component name

Cause: The component name parameter was empty or contains invalid values.

Action: Specify a valid component name.
Level: 1

Type: ERROR

Impact: Security

BEA-090649: Illegal application search name

Cause: The application name was not a legal search string.

Action: Specify a valid application name search string.
Level: 1

Type: ERROR

Impact: Security

BEA-090650: Illegal component search name

Cause: The component name was not a legal search string.

Action: Specify a valid component name search string.
Level: 1

Type: ERROR

Impact: Security

BEA-090651: No component type

Cause: The component type parameter is empty.

Action: Specify a valid component type of EJB, WebApp, Connector or WebService.
Level: 1

Type: ERROR

Impact: Security

BEA-090652: Invalid component type: "{0}"

Cause: The specified component type parameter is not valid.

Action: Specify a valid component type of EJB, WebApp, Connector or WebService.
Level: 1

Type: ERROR

Impact: Security

BEA-090653: Empty array value found

Cause: An empty string was supplied for an array element of the resource key.

Action: Specify a valid string.
Level: 1

Type: ERROR

Impact: Security

BEA-090654: Unexpected resource identifier data: "{0}"

Cause: An invalid resource identifier was supplied.

Action: Specify a valid resource identifier.
Level: 1

Type: ERROR

Impact: Security

BEA-090655: Unexpected resource key array value: "{0}"

Cause: An invalid resource identifier was supplied.

Action: Specify a valid resource identifier.
Level: 1

Type: ERROR

Impact: Security

BEA-090658: Unable to convert file {0} to URL. Got exception {1}.

Cause: File {0} could not be converted to a URL.

Action: This exception is an internal error. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090660: Certificate chain received from {0} was not validated by the custom trust manager {1} causing SSL handshake failure.

Cause: A peer presented a certificate chain to the server that the custom trust manager did not validate.

Action: Check the certificate chain to determine if it should be trusted or not. If it should be trusted, then update the custom trust manager to trust the peer certificate chain.
Level: 1

Type: WARNING

Impact: Security

BEA-090661: Certificate chain received from {0} was not validated by the custom trust manager {1} causing SSL handshake failure. Check the certificate chain to determine if it should be trusted or not. If it should be trusted, then update the custom trust manager to trust the certificate chain.

Cause: A peer presented a certificate chain to the server that the custom trust manager did not validate.

Action: Check the certificate chain to determine if it should be trusted or not. If it should be trusted, then update the custom trust manager to trust the certificate chain.
Level: 1

Type: WARNING

Impact: Security

BEA-090662: The DeployableAuthorizer "{0}" implements the deprecated {1} interface.

Cause: At security provider initialization, a deprecated security interface was detected.

Action: No immediate action is required. However, the security provider should be updated.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090663: The DeployableRoleMapper "{0}" implements the deprecated {1} interface.

Cause: At security provider initialization a deprecated security interface was detected.

Action: No immediate action is required. However, the security provider should be updated.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090666: Deployment handle was not supplied.

Cause: The deployment handle is null.

Action: This exception is an internal error. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090667: Application information was not supplied.

Cause: The application information is null.

Action: This exception is an internal error. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090668: Ignored deployment of role "{0}" for resource "{1}".

Cause: The application has been configured to ignore security data from deployment descriptors.

Action: Remove role mapping from the application deployment descriptor or change the security configuration to allow deployment of role mappings.
Level: 1

Type: WARNING

Impact: Security

BEA-090669: Ignored deployment of policy for resource "{0}".

Cause: The application has been configured to ignore security data from deployment descriptors.

Action: Remove security policy from the application deployment descriptor or change the security configuration to allow deployment of security policy.
Level: 1

Type: WARNING

Impact: Security

BEA-090670: Unable to verify user name token for user {0}

Cause: The UsernameToken could not be verified.

Action: Verify that the user exists in the WebLogic authentication provider, that the authentication provider has the PasswordDigestEnabled attribute set to true, and that the user entry has set the password since the attribute was set to true.
Level: 1

Type: ERROR

Impact: Security

BEA-090672: Identity assertion object for token type {0} was of type {1} instead of expected type of {2}.

Cause: The token object was not an instance of the correct type.

Action: If called from an application via the identity assertion public API, then modify the application to pass the expected token. If called from the container, then the container should not be passing a token that is not a UsernameToken, and this exception indicates an internal coding error in the server; contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090673: Digest data source {0} was not found. Disabling digest authentication.

Cause: The configured data source does not exist.

Action: Modify the DigestDataSourceName attribute on the WebLogic Identity Assertion provider to be the name of a valid WebLogic data source configured for this domain.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090674: Digest data source {0} was not initialized due to an exception. Disabling digest authentication. The exception text is {1}.

Cause: An exception was thrown when initializing the configured data source.

Action: Verify that the DigestDataSourceName attribute on the WebLogic Identity Assertion provider is valid and a WebLogic data source configured for this domain. Read the exception text for more information on diagnosing the problem.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090675: An SQL connection could not be obtained from a digest data source {0} due to an exception. Disabling digest authentication. The exception text is {1}.

Cause: An exception was thrown when obtaining a connection from the configured data source.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090676: The SQL statement {0} could not be prepared due to an exception. Disabling digest authentication. The exception text is {1}.

Cause: An exception occurred when preparing the SQL statement.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090677: The {0} table could not be created due to an exception. Disabling digest authentication. The exception text is {1}.

Cause: An exception occurred when validating or creating the table.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090678: Authentication failed with digest {0} due to an exception that occurred while detecting the replay attack. The exception text is {1}.

Cause: An exception occurred when inserting the digest information row into the database.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090679: Authentication failed due to detection of a replay attack for nonce {0} and digest {1}.

Cause: An entry for this nonce and digest has already been used for authentication in this domain.

Action: Ensure that the client is not performing a replay attack. Investigate the client performing the digest authentication and check that it is using unique nonce, digest, and created values.
Level: 1

Type: ERROR

Impact: Security

BEA-090680: Unable to verify the digest authentication for user {0} since the created time is not within the expiration time period.

Cause: The created timestamp of the digest authentication is not within the expiration time period.

Action: Increase the expiration time for the identity assertion provider or synchronize the system clocks on the client and server machines.
Level: 1

Type: ERROR

Impact: Security

BEA-090681: Digest authentication for user {0} has been disabled due to a previous fatal error in initializing replay detection

Cause: A previous fatal error disabled digest authentication. Therefore, digest authentication for this user has failed.

Action: Look in the log, identity the previous error, and correct the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090682: Problem handling security deployment validation: {0}

Cause: An initialization error or exception from a security provider occurred.

Action: This is an internal error. Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: Security

BEA-090700: There is a problem with the class {0} pointed to by the weblogic.security.jacc.RoleMapperFactory.provider property.

Cause: JACC Was enabled by setting weblogic.security.jacc.RoleMapperFactory.provider property but there are problems instantiating the class.

Action: Ensure that the class is present or change weblogic.security.jacc.RoleMapperFactory.provider property to a class that can be instantiated.
Level: 1

Type: ERROR

Impact: Security

BEA-090701: Unable to successfully obtain a RoleMapperFactory.

Cause: The weblogic.security.jacc.RoleMapperFactory.provider property may not be set to a valid implementation of RoleMapperFactory.

Action: Change weblogic.security.jacc.RoleMapperFactory.provider to point to an instance of a weblogic.security.jacc.RoleMapperFactory object.
Level: 1

Type: ERROR

Impact: Security

BEA-090705: The PolicyConfigurationFactory, Policy, RoleMapperFactory class names are not specified or not compatible with each other.

Cause: Incompatible class names have been specified. Generally this is caused by specifying but not specifying all three or by specifying class names that are not designed to work with each other.

Action: Check the documentation and make sure that compatible class names are set for the three system properties.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090707: Successfully obtained a {0} RoleMapperFactory.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090709: Inconsistent security configuration.

Cause: The security command line properties are not consistent with each other.

Action: Address the inconsistency and reboot.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090714: The certificate chain from the peer could not be validated. Chain : {0}. Reason : {1}.

Cause: Either the certificate chain from the peer should not be allowed to access the server or the server or one of the configured CertPathProviders is not properly configured to trust the peer.

Action: If the server is not supposed to trust the peer, inform the peer that it should use a different certificate chain. If the server should trust the peer, then either a configured CertPathProvider is improperly configured to not trust the peer, or the server is improperly configured to use the configured CertPathProviders for perform extra validation of SSL peer certificate chains. Check the server SSL configuration and the configured CertPathProvider configurations.
Level: 1

Type: WARNING

Impact: Security

BEA-090716: Failed to retrieve identity key/certificate from keystore {1} under alias {2} on server {0}.

Cause: An incorrect key password was used.

Action: Correct the server SSL configuration.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090717: Invalid server {0} SSL configuration

Cause: The server SSL configuration parameters are inconsistent.

Action: Verify that the SSL and keystore configuration options are consistent.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090718: Security initializing using java security manager.

Cause: This message is for informational purposes.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090719: Security initializing using JACC for EJB and Servlet authorization.

Cause: This message is for informational purposes.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090720: The Managed Server could not start because the NodeManager's encryption service data was not found.

Cause: The Managed Server could not start because the NodeManager's NodeManagerProperties file was not found. The NodeManager's encryption service could not be instantiated.

Action: Verify the existence and location of the NodeManager's NodeManagerProperties file.
Level: 1

Type: ERROR

Impact: Security

BEA-090721: The Managed Server could not start because it could not read the NodeManager's encryption service data.

Cause: The Managed Server could not start because it could not read the NodeManager's encryption service data.

Action: Verify the existence and location of the NodeManager's NodeManagerProperties file. Check that the read permissions are correct.
Level: 1

Type: ERROR

Impact: Security

BEA-090724: Challenge identity assertion has not completed, subject is not available yet.

Cause: The method to get the subject was called before the identity assertion completed.

Action: Call the hasChallengeIdentityCompleted method before calling the method to get the subject.
Level: 1

Type: ERROR

Impact: Security

BEA-090725: Challenge identity assertion has completed, challenge token is not available.

Cause: The method to get the challenge token was called after the identity assertion completed.

Action: Call the hasChallengeIdentityCompleted method before calling the method to get the challenge token.
Level: 1

Type: ERROR

Impact: Security

BEA-090764: The ApplicationVersioner "{0}" for application "{1}" returned an error: {2}.

Cause: There are multiple possible causes.

Action: Carefully read the returned error to determine if any action is required.
Level: 1

Type: ERROR

Impact: Security

BEA-090765: Failed to create policies for application version {0}.

Cause: An exception occurred during the application version created method.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090766: Failed to create roles for application version {0}.

Cause: An exception occurred during the application version created method.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090772: The security realm {0} does not support application versioning. Unable to deploy the application {1}.

Cause: The security realm {0} as configured does not support application versioning, and thus the deployment of the application version failed.

Action: Deploy the application using a security realm that supports application versioning.
Level: 1

Type: ERROR

Impact: Security

BEA-090773: Failure in creating security application version information for the application {0}.

Cause: An attempt to create security version information for application {0} failed.

Action: Check the server log for additional security error messages, correct security errors, and try again.
Level: 1

Type: ERROR

Impact: Security

BEA-090774: This method requires an encrypted argument but the argument passed to it was in clear text.

Cause: This method was called with a clear-text argument but requires an encrypted argument.

Action: To call this method programattically, call the non-encrypted set() method on the MBean. This will automatically encrypt the argument.
Level: 1

Type: ERROR

Impact: Security

BEA-090777: Exception when trying to sign a SAML assertion: {0}

Cause: An exception occurred during the signing of a SAML assertion.

Action: Read the exception text from the log message for more information on diagnosing the problem.
Level: 1

Type: WARNING

Impact: Security

BEA-090779: Identity {0} failed validation, downgrading to anonymous.

Cause: Trust has not been properly established between two domains. If the domains are not configured properly, a hacker could make an attempt to guess the server identity for this domain.

Action: See the documentation on "Enabling Trust Between WebLogic Domains" at http://www.oracle.com/technology/products/weblogic/index.html.
Level: 1

Type: ERROR

Impact: Security

BEA-090780: The values specified by -Dweblogic.security.URLResourceCaseMapping({0}) and WebAppFilesCaseInsensitive Attribute on SecurityConfiguraitonMBean({1}) do not match.

Cause: The value of the property -Dweblogic.security.URLResourceCaseMapping is different from the value for WebAppFilesCaseInsensitive attribute of the SecurityConfiguraitonMBean.

Action: Correct -Dweblogic.security.URLResourceCaseMapping to start the server.
Level: 1

Type: ERROR

Impact: Security

BEA-090782: Server is running in production mode, and the Native Library (terminalio) to read the password securely from the command line was not found.

Cause: Server could not start because it didn't find the Native Library in the PATH to read the password securely from command line.

Action: Verify that the terminalio library exists in the path. You can set this by setting -Djava.library.path to the directory where this library exists, you can use boot.properties to store the password, or you can use -Dweblogic.management.allowPasswordEcho=true to enter the password in echo mode.
Level: 1

Type: ERROR

Impact: Security

BEA-090783: Server is running in development mode and the Native Library (terminalio) to read the password securely from the command line wes not found.

Cause: Either the server could not start because it did not find the Native Library in the PATH to read the password securely from command line or -Dweblogic.management.allowPasswordEcho=false is set.

Action: Verify that the terminalio library exists in the path. You can set this by setting -Djava.library.path to the directory where this library exists, you can use boot.properties to store the password, or you can use -Dweblogic.management.allowPasswordEcho=true to enter the password in echo mode.
Level: 1

Type: ERROR

Impact: Security

BEA-090787: A null data source name was specified.

Cause: A configuration setting that required a data source name was null.

Action: Check configuration settings that require data source names to verify they are correctly specified.
Level: 1

Type: ERROR

Impact: Security

BEA-090788: Problem with data source or connection pool configuration, verify that data source name {0} is correct and pool configurations are correct.

Cause: A configuration setting that required a data source name was likely incorrect, or the pool settings associated with it are incorrect.

Action: Check configuration settings to ensure that the data source name is correct and the associated pool configuration settings are correct.
Level: 1

Type: ERROR

Impact: Security

BEA-090812: Could not create a {0} keystore instance for provider {1}. Exception: {2}

Cause: {0} is not a valid keystore type, or keystore provider {1} was not properly configured.

Action: Verify that the correct keystore type was specified and that the keystore provider is correctly specified in the java.security file.
Level: 1

Type: ERROR

Impact: Security

BEA-090814: Security Service is shutting down the security realm {0}.

Cause: This message is for informational purposes.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090817: These configuration changes cannot be activated because a default realm is not configured for the domain.

Cause: The quot;DefaultRealm" is not set for the domain's SecurityConfiguration.

Action: To correct the problem, set the "DefaultRealm" for the domain's SecurityConfiguration to one of its realms. If it does not have any realms, create and configure one.
Level: 1

Type: ERROR

Impact: Security

BEA-090818: These configuration changes cannot be activated because the domain does not have a properly configured default realm.

Cause: The "DefaultRealm" is not properly configured for the domain's SecurityConfiguration. See the nested exceptions that accompany this error for details.

Action: To correct the problem, review and address the nested exceptions that accompany this error.
Level: 1

Type: ERROR

Impact: Security

BEA-090819: The JACC property {0} is not set.

Cause: A JACC provider is attempting to initialize but {0} property has not been set.

Action: Set the property and reboot.
Level: 1

Type: ERROR

Impact: Security

BEA-090820: The internal variable {0} is null and it should not be.

Cause: The cause is unknown.

Action: This exception is an internal error. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090823: Could not register the WebLogic Server X509CertificateFactory as the default X509CertificateFactory for this JVM.

Cause: The WebLogic Server X509CertificateFactory could not be registered as the default X509CertificateFactory for this JVM.

Action: The WebLogic Server X509CertificateFactory orders the certificates in a CertPath that was created from PKCS7. Specify -Dweblogic.security.RegisterX509CertificateFactory=false on the command line for booting this server to indicate that WebLogic Server should not register the WebLogic Server X509CertificateFactory as the default X509CertificateFactory when the server boots (since your JDK does not support this). Also, since the WebLogic Server X509CertificateFactory cannot be registered with the JDK as the default X509CertificateFactory, the JDK will use its current default X509CertificateFactory. The default one (for example, the SUN implementation) may not properly convert PKCS7 to an ordered CertPath.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090827: LDIF template file {1} was empty. The WebLogic provider {0} has been bootstrapped but has not been initialized with any LDIF data.

Cause: A WebLogic provider LDIF template file may have been overwritten with an empty file.

Action: If the server boots successfully, no action is needed. If the server does not boot successfully then an attempt should be made to recover non-empty LDIFT template file from the WebLogic Server kit.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090838: The required WebLogic JACC RoleMapperFactory was not specified. Please specify the factory class using the weblogic.security.jacc.RoleMapperFactory.provider system property.

Cause: A WebLogic JACC RoleMapperFactory class is required.

Action: Check the documentation and ensure that the WebLogic JACC RoleMapperFactory system property is set properly.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090839: Unexpected exception while registering SAML {0} service in application context {1}.

Cause: This is an internal server error.

Action: Check server status.
Level: 1

Type: ERROR

Impact: Security

BEA-090840: Registered SAML service {0} at URI {1} in application context {2}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090846: {0} provider initialization failed: Invalid {1} attribute "{2}".

Cause: This was caused by an incorrect provider configuration.

Action: Check and update the indicated provider attribute.
Level: 1

Type: ERROR

Impact: Security

BEA-090847: {0} provider initialization failed: Missing {1} attribute.

Cause: This was caused by an invalid provider configuration.

Action: Check and update the indicated provider attribute.
Level: 1

Type: ERROR

Impact: Security

BEA-090859: The realm {0} does not have a certification path validator configured. To correct the problem, configure a cert path provider that supports cert path validation.

Cause: The realm {0} does not have a certification path validator configured.

Action: To correct the problem, configure a certification path provider that supports certification path validation.
Level: 1

Type: WARNING

Impact: Security

BEA-090861: Certificate policies extension processing failed. PolicyId: {0} does not exist in the allowed list.

Cause: Certificate policies extension processing failed. PolicyId: {0} does not exist in the allowed list.

Action: Add the Policyid to the Allowed Policyids list.
Level: 1

Type: ERROR

Impact: Security

BEA-090862: Certificate policies extension processing failed. PolicyQualifierID: {0} is not CPS.

Cause: Certificate policies extension processing failed. PolicyQualifierID: {0} is not CPS.

Action: Check the Certificate Presented, as certificates containing a PolicyQualifierID other than CPS are not supported.
Level: 1

Type: ERROR

Impact: Security

BEA-090865: The realm {0} is not configured to handle MBean authorization. To correct the problem, configure an authorization provider that supports MBean authorization.

Cause: The realm {0} is not configured to handle MBean authorization.

Action: To correct the problem, configure an authorization provider that supports MBean authorization.
Level: 1

Type: WARNING

Impact: Security

BEA-090866: The deployment of an unchecked policy for the resource "{0}" has been ignored. Unchecked policy is the default policy for URL and EJB resources. An unchecked policy can result if a deployment descriptor specifies a transport guarantee without the use of an authorization constraint.

Cause: The application has been configured to ignore security data from deployment descriptors.

Action: When the deployment descriptor specifies a transport guarantee without the use of an authorization constraint, no action is needed. Otherwise, remove the security policy from the application deployment descriptor or change the security configuration to allow deployment of security policy.
Level: 1

Type: WARNING

Impact: Security

BEA-090868: The realm {0} has an invalid SAML configuration. To correct the problem, ensure that there is only one of each SAML provider type and that the version of the SAML providers are the same.

Cause: The realm {0} has an invalid set of SAML providers.

Action: To correct the problem, ensure that there is only one of each SAML provider type and that the version of the SAML providers are the same.
Level: 1

Type: WARNING

Impact: Security

BEA-090869: The PolicyConsumer "{0}" returned an error: {1}.

Cause: There are multiple possible causes.

Action: Carefully read the returned error to determine if any action is required.
Level: 1

Type: ERROR

Impact: Security

BEA-090870: The realm "{0}" failed to be loaded: {1}.

Cause: There are multiple possible causes.

Action: Carefully read the returned error to determine if any action is required.
Level: 1

Type: ERROR

Impact: Security

BEA-090871: The RoleConsumer "{0}" returned an error: {1}.

Cause: There are multiple possible causes.

Action: Carefully read the returned error to determine if any action is required.
Level: 1

Type: ERROR

Impact: Security

BEA-090872: The {0} service can not be found for {1}.

Cause: A null was returned when performing a service lookup.

Action: Check the configuration to determine if the missing service was actually configured.
Level: 1

Type: ERROR

Impact: Security

BEA-090873: Expected a {0} object but did not get one.

Cause: There is a possible configuration problem.

Action: Check the configuration.
Level: 1

Type: ERROR

Impact: Security

BEA-090874: {0} returned a null {1}.

Cause: This should never happen.

Action: Examine the specific objects referenced in the error message to see what may be the cause.
Level: 1

Type: ERROR

Impact: Security

BEA-090875: Null parameter supplied to method {0}.

Cause: A parameter was not correctly specified.

Action: This is most likely a coding error.
Level: 1

Type: ERROR

Impact: Security

BEA-090876: {0} Consumer not configured.

Cause: An attempt was made to reference a Consumer, but none are configured

Action: Check the configuration.
Level: 1

Type: ERROR

Impact: Security

BEA-090877: Service {0} unavailable, see exception text: {1}

Cause: The exception text should indicate the cause. This is likely a configuration error.

Action: Check the configuration.
Level: 1

Type: ERROR

Impact: Security

BEA-090878: Unknown token type: {0}

Cause: This is likely caused by the token type not being properly configured.

Action: Check the configuration.
Level: 1

Type: ERROR

Impact: Security

BEA-090880: Could not load JAAS configuration file for JVM.

Cause: A class similar to com.sun/ibm.security.auth.login.ConfigFile was not located in the classpath.

Action: Ensure that com.sun.security.auth.login.ConfigFile/com.ibm.security.auth.login.ConfigFile is available as part of the classpath or that -Dweblogic.security.authentication.Configuration=class name is passed as a startup system property and is available as part of the classpath.
Level: 1

Type: WARNING

Impact: Security

BEA-090882: SSL has established a session that uses a Null cipher.

Cause: The connecting SSL client presented a ciphersuite list to the server that contains only ciphersuites with null ciphers. This may or may not be a problem, depending on your domain configuration.

Action: Verify that the client's security providers are configured correctly, or disable the use of Null ciphers on the server.
Level: 1

Type: WARNING

Impact: Security

BEA-090883: Resource name is null or empty.

Cause: Resource name should not be null or empty.

Action: Check that the resource name is not null or empty.
Level: 1

Type: ERROR

Impact: Security

BEA-090884: User name is null or empty.

Cause: User name should not be null or empty.

Action: Check that the User name is not null or empty.
Level: 1

Type: ERROR

Impact: Security

BEA-090885: Remote user name is null or empty.

Cause: Remote user name should not be null or empty.

Action: Check that the remote user name is not null or empty.
Level: 1

Type: ERROR

Impact: Security

BEA-090886: List number should not be negative.

Cause: The list number should not be negative.

Action: Check that the list number is not negative.
Level: 1

Type: ERROR

Impact: Security

BEA-090888: The SSL client running within the server does not have a certificate. It will use the server's certificate.

Cause: The SSL client running within the server does not have a certificate, but client certificates are required.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090889: The SSL client running within the server could not obtain the server's certificate.

Cause: An exception occurred when the SSL client running within the server tried to obtain the server's certificate.

Action: Check that the server's SSL configuration is correct, and that the server has a certificate and private key configured.
Level: 1

Type: WARNING

Impact: Security

BEA-090890: The loading of the OPSS java security policy provider class {0} failed due to a problem in creating the OPSS java security policy provider instance {0}. Illegal access to the constructor of the class.

Cause: The loading of the OPSS java security policy provider class {0} failed due to an IllegalAccessException.

Action: Ensure that the correct version of the OPSS java security policy provider {0} is used.
Level: 1

Type: ERROR

Impact: Security

BEA-090891: The loading of the OPSS java security policy provider failed due to a problem in instantiating the OPSS java security policy provider. An InstantiationException was received when creating an instance.

Cause: The loading of the OPSS java security policy provider class {0} failed due to InstantiationExceptions.

Action: Ensure that the correct version of the OPSS java security policy provider {0} is used.
Level: 1

Type: ERROR

Impact: Security

BEA-090892: The loading of an OPSS java security policy provider failed due to an exception. See the exception stack trace or the server log file for the root cause. If there is no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: {1}

Cause: The loading of the OPSS java security policy provider class {0} failed due to an exception: {1}.

Action: Check the stack trace or server log file for the root cause of the exception, check for a possible configuration error, or enable the debug flag -Djava.security.debug=jpspolicy to get more information.
Level: 1

Type: ERROR

Impact: Security

BEA-090893: The loading of the OPSS java security policy provider stopped due to a conflict with the JACC Policy provider. Only one security policy provider can be enabled.

Cause: The loading of the OPSS java security policy provider stopped due to a conflict with the JACC Policy provider. Only one security policy provider can be enabled.

Action: If enabling the OPSS java security policy provider {0}, please do not enable the JACC setting.
Level: 1

Type: ERROR

Impact: Security

BEA-090894: Successfully loaded the OPSS Policy Provider using {0}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090895: OPSS Java Security Policy Provider {0} has already been loaded statically, programmatical loading has been skipped.

Cause: OPSS Java Security Policy Provider {0} has already been loaded statically, programmatical loading has been skipped.

Action: No action is required.
Level: 1

Type: WARNING

Impact: Security

BEA-090896: The SSL ListenPort attribute {0} cannot be the same as the Administration Port for the server.

Cause: The same value was specified for the Administration Port and the SSL Listen port.

Action: Correct the configuration of the SSL Listen port or the Administration port. The SSL Listen port value must be different that than the Administration port.
Level: 1

Type: ERROR

Impact: Security

BEA-090897: A failure occurred while attempting to update XACML global policies for security provider {0}.

Cause: An exception occurred while attempting to update XACML global policies.

Action: Examine the exception and correct the cause.
Level: 1

Type: ERROR

Impact: Security

BEA-090898: Ignoring the trusted CA certificate "{0}". Loading of the trusted certificate list raised a certificate parsing exception {1}.

Cause: It is possible that the CA to be added used a signature algorithm that is not supported by the SSL stack.

Action: The server has a long list of trusted CAs, and the one that caused the exception in the server is ignored.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090899: User attribute name cannot be null.

Cause: The user attribute name is null for the request.

Action: Pass in a user attribute name that is not null.
Level: 1

Type: ERROR

Impact: Security

BEA-090900: User attribute name is not supported for the specified operation.

Cause: The user attribute name is not supported.

Action: Pass in a user attribute name that is supported. Refer to documentation for details.
Level: 1

Type: ERROR

Impact: Security

BEA-090901: Invalid group name: {0}. Cannot contain {1}.

Cause: There was improper usage of {1}.

Action: Never use a group name carrying {1}.
Level: 1

Type: ERROR

Impact: Security

BEA-090902: The certificate chain received from {0} contained a V1 certificate which cannot be a CA.

Cause: The certificate chain received by the peer contained a V1 certificate which cannot be a CA. This was rejected by the basic constraints checking for strong and strict and not allowing V1 certificates as CAs, which protects against a specific certificate chain attack on SSL.

Action: The peer certificate chain needs to be looked at carefully to determine which certificate is not correct. If the certificate chain really is from a valid peer, look at updating the peer certificate chain with valid CA certificates. If this is not possible, disable the basic constraints checking to allow the certificate chain to be accepted and to allow this vulnerability to be exploited.
Level: 1

Type: WARNING

Impact: Security

BEA-090903: The JPS or JRF JAR is present in the classpath, but the jps-config.xml file was not supplied in the command line: the required system property "{0}" has not been defined.

Cause: System parameter "oracle.security.jps.config" is not supplied in the command line, but a JPS or JRF JAR is present in the classpath.

Action: If this is not a JRF domain, remove the JPS or JRF JAR from the classpath; otherwise, and add the system parameter "oracle.security.jps.config" in the command line to supply the path to the jps-config.xml file.
Level: 1

Type: WARNING

Impact: Security

BEA-090904: The JPS or JRF JAR is present in the classpath, but no system property was supplied for "{0}" and "{1}". The server will start without setting the OPSS java policy provider.

Cause: System parameters "oracle.security.jps.config" and "oracle.domain.config.dir" are not supplied in the command line, but jps-internal.jar or jrf.jar is present in the classpath.

Action: If this is not a JRF domain, removed the jps-internal.jar and jrf.jar from the classpath. Otherwise, add the required system parameters for the JRF domain.
Level: 1

Type: WARNING

Impact: Security

BEA-090905: Disabling the CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -D{0}=true.

Cause: The CryptoJ JCE Provider self-integrity check incurs some performance penalty at server startup.

Action: No action is requirecx.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090906: Changing the default Random Number Generator in RSA CryptoJ from {1} to {2}. To disable this change, specify -D{0}=true.

Cause: CryptoJ's default RNG ECDRBG causes certain cryptographic operations to be slower.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090907: Invalid user name: {0}. Cannot contain {1}.

Cause: There was improper usage of {1}.

Action: Never use a user name carrying {1}.
Level: 1

Type: ERROR

Impact: Security

BEA-090908: Using the default WebLogic SSL Hostname Verifier implementation.

Cause: TBD

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090909: Using the configured custom SSL Hostname Verifier implementation: {0}.

Cause: TBD

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090910: Grant statement has invalid syntax: {0}

Cause: There is an error in the syntax of the grant statement.

Action: Verify that the grant statement syntax is correct.
Level: 1

Type: ERROR

Impact: Security

BEA-090911: Permission found in grant statement has invalid syntax: {0}

Cause: There is an error in the syntax of the permission within the grant statement.

Action: Verify that the grant statement permission syntax is correct.
Level: 1

Type: ERROR

Impact: Security

BEA-090912: Attempting to check revocation status for certificate with subject: {0}

Cause: X.509 certificate revocation checking is enabled.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090913: Unknown revocation status not causing failure for certificate with subject: {0}

Cause: X.509 certificate revocation checking is enabled, however, certificate revocation status cannot be determined, and is configured not to fail on an unknown status.

Action: If validation failure is required, configure certificate revocation status to fail on an unknown status. To determine why the status is unknown, enable debug logging.
Level: 1

Type: WARNING

Impact: Security

BEA-090914: Certificate revocation status: {0}

Cause: X.509 certificate revocation checking is enabled.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090915: Nonce was ignored by the OCSP responder, forcing certificate revocation status to be ignored and considered unknown: {0}.

Cause: X.509 certificate revocation checking is enabled, and OCSP is configured with nonces enabled.

Action: To enable use of the ignored status, configure to disable OCSP nonces.
Level: 1

Type: WARNING

Impact: Security

BEA-090916: Unknown revocation status causing failure for certificate with subject: {0}.

Cause: X.509 certificate revocation checking is enabled, certificate revocation status cannot be determined, and is configured to fail on an unknown status.

Action: If validation failure is not required, configure certificate revocation status to not fail on an unknown status. To determine why the status is unknown, enable debug logging.
Level: 1

Type: WARNING

Impact: Security

BEA-090917: Revoked certificate causing validation failure, certificate with subject: {0}.

Cause: X.509 certificate revocation checking is enabled, and the checked certificate was reported revoked.

Action: Contact the certificate presenter (for example, SSL peer) and request that the revoked certificate be updated.
Level: 1

Type: WARNING

Impact: Security

BEA-090918: Non-revoked certificate with subject: {0}.

Cause: X.509 certificate revocation checking is enabled, and the checked certificate was reported NOT revoked.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090919: The configured SSL minimum protocol version {0} is invalid or not supported. The minimum has been changed to {1}.

Cause: The current SSL implementation does not support the configured SSL minimum protocol version.

Action: No action is required.
Level: 1

Type: WARNING

Impact: Security

BEA-090920: Certicom SSL is available, however JSSE is being used for SSL, since JSSE has been selected by system property {0}, either explicitly or by default.

Cause: The system property {0} is selecting JSSE either explicitly or by default.

Action: To use Certicom for SSL, set the system property {0} to false.
Level: 1

Type: WARNING

Impact: Security

BEA-090921: JSSE has not been selected by system property {0}, however Certicom SSL is not available, so JSSE is being used for SSL.

Cause: Certicom SSL is not available, so JSSE is being used for SSL, even though JSSE was not selected.

Action: To use Certicom for SSL, install Certicom.
Level: 1

Type: WARNING

Impact: Security

BEA-090922: Certicom SSL is available, however JSSE is being used for SSL, since JSSE has been selected by the SSLMBean.JSSEEnabled attribute, either explicitly or by default.

Cause: The attribute SSLMBean.JSSEEnabled is selecting JSSE either explicitly or by default.

Action: To use Certicom for SSL, set the attribute SSLMBean.JSSEEnabled to false.
Level: 1

Type: WARNING

Impact: Security

BEA-090923: JSSE has not been selected by the SSLMBean.JSSEEnabled attribute, however Certicom SSL is not available, so JSSE is being used for SSL.

Cause: Certicom SSL is not available, so JSSE is being used for SSL, even though JSSE was not selected.

Action: To use Certicom for SSL, install Certicom.
Level: 1

Type: WARNING

Impact: Security

BEA-090924: JSSE has been selected by default, since the SSLMBean is not available.

Cause: This usually occurs early in server startup, before Management Service runtime access is available.

Action: No action is required. Eventually the Management Service will start and normal operation will commence.
Level: 1

Type: WARNING

Impact: Security

BEA-090925: JSSE has been selected by default, since the system property {0} has the invalid value "{1}".

Cause: The system property {0} was not set to "true" or "false".

Action: Change the system property {0} value to be either "true" or "false".
Level: 1

Type: WARNING

Impact: Security

BEA-090926: Illegal key store source value [keyStoreType="{0}", source="{1}", exception="{2}", message="{3}"]

Cause: The configured key store source value is not valid for the key store type.

Action: Correct the key store source value, ensuring that the source is appropriate for the key store type. For example, the "jks" key store type requires that the source be a file path to an existing key store file.
Level: 1

Type: ERROR

Impact: Security

BEA-090927: Illegal or unknown key store type value [keyStoreType="{0}", source="{1}"]

Cause: The configured key store type value is not recognized.

Action: Correct the key store type value. For example, the "jks" key store type requires the type value to be "jks".
Level: 1

Type: ERROR

Impact: Security

BEA-090928: Unable to instantiate key store [keyStoreType="{0}", provider="{1}", exception="{2}", message="{3}"]

Cause: Key store instantiation failure usually occurs because no appropriate specified or default provider is available. See the exception for details.

Action: Verify that key store type is correct, and that a supporting Java Cryptography Architecture (JCA) provider is available in the Java Runtime Environment. A "jks" key store provider is usually available by default. An Oracle Key Store Service (type "kss") provider is only available if Oracle Java Required Files (JRF) is installed.
Level: 1

Type: ERROR

Impact: Security

BEA-090929: Unable to load key store [keyStoreType="{0}", source="{1}", exception="{2}", message="{3}"]

Cause: A key store could fail to load due to an invalid source or password. Since key store instantiation succeeded, the key store type is valid. See the exception for details.

Action: Check the configured key store source and password values.
Level: 1

Type: ERROR

Impact: Security

BEA-099000: Invalid property value: {0}={1}

Cause: An exception occurred while processing the value for the specified property.

Action: Correct the property and restart. This exception should not normally occur as the properties are only used internally.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-099001: Caught exception while evaluating policy expression: {0} associated with: {1}

Cause: The evaluate method of the predicate used by the policy failed with a RuntimeException.

Action: Ensure that parameters which are passed to the predicates in the expression or context are valid.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-099002: An invalid predicate {0} was retrieved from the database. Ensure that the predicate class is in the server classpath.

Cause: The class file belonging to the condition was not in the server classpath.

Action: Update the classpath and restart the server.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-099003: Evaluation of policy associated with role {0} failed because the policy expression contains unregistered predicate: {1}.

Cause: The predicate that is specified in the log message is not registered, or the policy is out of date.

Action: Register the predicate or remove its reference from the policy.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-099004: Evaluation of policy associated with resource {0} failed because the policy expression contains unregistered predicate: {1}.

Cause: The redicate that is specified in the log message is not registered, or the policy is out of date.

Action: Register the predicate, or remove its reference from the policy.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-100000: Invalid call to the deprecated method {0}.

Cause: The method was deprecated in the latest servlet specification.

Action: Check the specification for an alternative. If not corrected, unpredictable behavior might occur.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100005: Could not remove session: "{0}".

Cause: An unexpected error occurred while removing the session.

Action: Check the exception text for the exact error message.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100006: HTTP session file persistence: storing sessions in directory: {0}.

Cause: This is an informational message.

Action: Ensure that the directory stores the sessions per the PeristentStoreDir session parameter (weblogic.xml).
Level: 1

Type: NOTIFICATION

Impact: HTTP Session

BEA-100007: Erasing the directory tree for persistent HTTP sessions: {0}.

Cause: The storage directory is being deleted as a result of session invalidation.

Action: Ensure that deletion is occurring while removing sessions.
Level: 1

Type: NOTIFICATION

Impact: HTTP Session

BEA-100008: Cannot delete "{0}".

Cause: The storage directory failed to be deleted.

Action: Ensure that the permissions on this directory are correct and that the file and directory are not in use by another process.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100011: An error occurred while serializing session data. Deleting this session.

Cause: This might be due to a change in the class definition or serialVersionUID.

Action: Check the exception text for the exact error message and take appropriate action.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100013: {0} not invalidated. The session that was serialized into the file system does not exist.

Cause: The session was not found and does not exist.

Action: This session might have been deleted by a trigger in another server, which is pointing to the same storage location.
Level: 1

Type: NOTIFICATION

Impact: HTTP Session

BEA-100015: Deleted file-based session persistent store file: {0}.

Cause: This is an informational message indicating that the storage file is being deleted.

Action: Ensure that the deletion is consistent with the path defined in the PersistentStoreDir (weblogic.xml)
Level: 1

Type: NOTIFICATION

Impact: HTTP Session

BEA-100016: Session expiration check failed for: {0}. Invalidating the session expiration check.

Cause: An unexpected error occurred while checking the session for expiration.

Action: The session will be removed from the persistent store. Check the exception text for the exact error message.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100018: An error occurred while loading the serialized session data for session {0}.

Cause: An unexpected error occurred.

Action: Check the exception text for the exact error message. The file could be corrupted.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100019: The file-based persistent session ID: "{0}" was stored in file: "{1}". File exists: {2}.

Cause: This is an informational message indicating that the session was stored in this path.

Action: Ensure that the file-based persistent session storage is consistent with the PersistentStoreDir (weblogic.xml).
Level: 1

Type: NOTIFICATION

Impact: HTTP Session

BEA-100020: Received malformed cookie ID: {0}.

Cause: The cookie could not be parsed properly.

Action: Check the cookie format and the exception text for the exact problem.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100022: Session invalidation interval: {0}

Cause: The session invalidation trigger is being created.

Action: Ensure that the session invalidation interval is consistent with the InvalidationIntervalSecs (weblogic.xml).
Level: 1

Type: NOTIFICATION

Impact: HTTP Session

BEA-100025: An unexpected error occurred in the HTTP session timeout callback while deleting sessions.

Cause: The invalidation trigger failed unexpectedly while deleting sessions.

Action: Check the exception message for the probable cause.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100026: An unexpected error occurred in the HTTP session timeout callback while checking session expiration.

Cause: An unexpected error occurred while checking the sessions for expiration.

Action: Check the exception text for the exact error message.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100028: The session data could not be deserialized.

Cause: The session data could not be deserialized.

Action: Ensure that the object being put into the session is serializable and that the non-transient objects it aggregates are also serializable. If any of the non-transient objects in the entire object graph are not serializable, this error message will occur.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100030: HTTP session expired. Session ID: {0}

Cause: This is an informational message indicating that the session with ID {0} has expired.

Action: If the session expired sooner than expected, check the SessionTimeout parameter in the weblogic.xml file.
Level: 1

Type: NOTIFICATION

Impact: HTTP Session

BEA-100031: An error occurred while unregistering the servlet session runtime MBean: {0}.

Cause: This MBean could not be removed.

Action: Check the exception text for the exact error message.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100032: An error occurred while creating a servlet session runtime MBean.

Cause: This MBean could not be created.

Action: Check the exception text for the exact error message.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100033: The license for replicated sessions is invalid: {0}. Downgrading sessions to memory, which are not replicated.

Cause: The license was not valid to support replicated sessions.

Action: Check the license. An upgrade to a clustering and replication license may be desired. Alternatively, file and JDBC persistence can be used for session store reliability.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100035: The timer invalidated session ID: {0}, Web application: {1}, because it expired.

Cause: This message was logged by the Web application level timer, which periodically checks the sessions for expiration. The session expired.

Action: If the session expired too soon, check the SessionTimeout in the weblogic.xml file.
Level: 1

Type: NOTIFICATION

Impact: HTTP Session

BEA-100038: Unknown persistent type: {0} for Web application: {1}. Valid types are: memory, file, replicated, JDBC, cookie, and replicated_if_clustered.

Cause: The specified persistent store type for this Web application was not recognized.

Action: Check the PersistentStoreType parameter in the weblogic.xml file. The valid values are: memory, file, replicated, cookie, JDBC, and replicated_if_clustered.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100039: Replicated HTTP sessions were specified for the Web application: {0}, but clustering was not enabled.

Cause: The session replication mechanism relies on clustering, which was not been configured.

Action: Set up clustering or change the PersistentStoreType in the weblogic.xml file to either memory, file, JDBC, or cookie.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100040: The getAttribute(): {0} was a handle. Reconstructing the EJB object.

Cause: This is an informational message indicating that the container is storing only the handle for the EJB object placed into the session.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP Session

BEA-100041: The setAttribute(): {0} was an EJB object. Storing the handle into the session.

Cause: The container found an EJB handle stored in the session. It will reconstruct the EJB object before returning it.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP Session

BEA-100042: An error occurred while reconstructing the EJB object: {0}, which was put into the session.

Cause: The container found an EJB handle stored in the session. However, it failed to reconstruct the EJB object using that handle.

Action: Ensure that the handle is still valid. Check the exception text for the exact error message.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100043: An error occurred while finding the handle for the EJB object: {0}.

Cause: The container stores only the handle for an EJB object put into the session. However, in this case, it failed to find the handle.

Action: Check the RemoteException for the exact error message details.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100044: Found WLCookie cookie {0}={1}.

Cause: The cookie persistence mechanism relies on setting the cookie header.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP Session

BEA-100045: Malformed WLCookie. Value: {0} will be ignored.

Cause: The cookie persistence mechanism relies on setting the cookie header.

Action: The cookie was found to be malformed. Only strings are supported for cookie-based persistence. Ensure that there are no characters in the attribute names and values, which can break the cookie syntax.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100046: Creating new session with ID: {0} for Web application: {1}.

Cause: A new session was created.

Action: Ensure that the length is equal to the IDLen parameter in the weblogic.xml file.
Level: 1

Type: NOTIFICATION

Impact: HTTP Session

BEA-100047: Performing the database operation: {0} with ID: {1} and Web application: {2}.

Cause: This is an informational message for JDBC-based persistence. It is meant for debugging purposes only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP Session

BEA-100048: Looked up ROID: {0} from host {1}:{2} for ID: {3}.

Cause: The replicated session ID was not found in the current server, perhaps because this server is not the primary or secondary server. Another attempt to retrieve the session from the assigned secondary server will be made if it is alive.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP Session

BEA-100049: An error occurred while looking up the session with ID:{0}.

Cause: A RemoteException occurred when looking up the session from the secondary server.

Action: Check if the secondary server is down. Note that it is not recommended to stop both the primary and secondary server at the same time. Because replication happens lazily, upon request, if the secondary server needs to end, give sufficient time so that the active end users hit their sessions and get replicated.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100050: The current server is becoming the primary server for replicated session ID: {0}.

Cause: The current server is taking the role of the primary server for the given session.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP Session

BEA-100051: The current server is becoming the secondary server for replicated session ID: {0}.

Cause: The current server is taking the role of the secondary server for the given session.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP Session

BEA-100052: Unregistering replicated session ID: {0}.

Cause: The current server will unregister the given session.

Action: The session was invalidated. No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP Session

BEA-100053: Failed to update the secondary server for HTTP session ID: {0}.

Cause: Failed to update the secondary server for the modification that occurred in the current request.

Action: Verify that the secondary server is alive, and ensure that the objects put into the session are all serializable. Also, check the exception text for the exact error message.
Level: 1

Type: WARNING

Impact: HTTP Session

BEA-100054: Failed to find the secondary server for HTTP session ID: {0}.

Cause: The secondary server could not be found for the replicated session.

Action: Verify that the clustering is configured properly and that there is more than one server in the cluster.
Level: 1

Type: WARNING

Impact: HTTP Session

BEA-100055: The generated session ID: {0} contains a reserved keyword and is regenerating.

Cause: On Windows 32-bit systems, if the session ID contains a reserved keyword, the file-based persistence fails. This is because it relies upon successful creation of subdirectories. The reserved keywords are: "CON", "PRN", "AUX", "NUL" "COM1", "COM2", "COM3", " COM4", "COM5", "COM6", "COM7", " COM8", "COM9", "LPT1", "LPT2", " LPT3", "LPT4", "LPT5", "LPT6", " LPT7", "LPT8", "LPT9", "CLOCK$"

Action: No action is required. The session ID will be regenerated.
Level: 1

Type: NOTIFICATION

Impact: HTTP Session

BEA-100056: For {0}: The session with ID: {1} was invalidated before the session creation and registration could complete.

Cause: This is a past-release problem.

Action: Contact My Oracle Support and file a bug report.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100057: This server does not have deployment for the Web application with context path: {0}. The callback: {1} failed while replicating the session. Check the configuration; only uniform configurations in a cluster are supported.

Cause: WebLogic Server clustering relies on uniform Web application deployment across the cluster. It seems the Web application was not deployed on all the servers.

Action: Redeploy the Web application, and ensure that it targets the cluster and all members in the cluster.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100058: The PersistentStoreType for the Web application with context path: {0} is not replicated. The callback: {1} failed while replicating the session. Check the configuration; only uniform configurations in a cluster are supported.

Cause: WebLogic Server clustering relies on uniform Web application deployment across the cluster. It seems the Web application was not deployed on all the servers with uniform configuration.

Action: Redeploy the Web application, and ensure that it targets the cluster and all members in the cluster. Also, the PersistentStoreType should be set to "replicated" for all cluster members.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100059: An unexpected error occurred while cleaning up sessions during undeployment of Web application: {0}.

Cause: The trigger failed to clean up the expired session.

Action: Check the exception text for the exact error message. When using JDBC-based HTTP session persistence, ensure that the database is set up properly. For file-based persistence, ensure that the permissions on the storage directory are appropriately set.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100060: An unexpected error occurred while retrieving the session for Web application: {0}.

Cause: The session from persistent store could not be retrieved.

Action: Check the configuration, and check the exception text for the exact error message. Also, check the WebLogic Server documentation for more details about how to configure session persistence for Web applications.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100061: Web application: {0} tried to place a non-serializable attribute: {1} into the session: {2}. This attribute will be lost upon redeployment. This message is logged only once per session.

Cause: The session.setAttribute(name, value) was invoked with a non-serializable value for memory-based sessions.

Action: If the session data should survive redeployment, ensure that all attributes are serializable. Otherwise, the non-serializable data will be lost upon redeployment.
Level: 1

Type: WARNING

Impact: HTTP Session

BEA-100062: Web application: {0} tried to place a non-serializable attribute: {1} into the session: {2}. This attribute will be lost upon redeployment or session failover. Also, such attributes will be scoped to the current server only and will not be replicated to the secondary server. This message is logged only once per session.

Cause: The session.setAttribute(name, value) was invoked with a non-serializable value for a replicated session.

Action: If the session data should survive redeployment and session failovers, ensure that all attributes are serializable. Otherwise, the non-serializable data will be lost upon failover and redeployment.
Level: 1

Type: WARNING

Impact: HTTP Session

BEA-100063: Web application: {0} tried to place a non-serializable attribute: {1} into the session: {2}. This attribute will be lost upon redeployment or session failover. Also, such attributes will be scoped to the current server only and will not be persisted to the disk. This message is logged only once per session.

Cause: The session.setAttribute(name, value) was invoked with a non-serializable value for a file-based persistent session.

Action: If the session data should survive redeployment and session failovers, ensure that all the attributes are serializable. Otherwise, the non-serializable data will be lost upon failover and redeployment.
Level: 1

Type: WARNING

Impact: HTTP Session

BEA-100064: Web application: {0} tried to place a non-serializable attribute: {1} into the session: {2}. The attribute will be lost upon redeployment or session failover. Also, such attributes will be scoped to the current server only and will not be persisted to the database. This message is logged only once per session.

Cause: The session.setAttribute(name, value) attribute was invoked with a non-serializable value for a JDBC-based persistent session.

Action: If the session data should survive redeployment and session failovers, ensure that all the attributes are serializable. Otherwise, the non-serializable data will be lost upon failover and redeployment.
Level: 1

Type: WARNING

Impact: HTTP Session

BEA-100065: {0}. Failed to remove attributes for HTTP session ID: {1}.

Cause: An unexpected error occurred during HTTP session invalidation.

Action: Check the error message for the exact cause.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100066: Failed to look up the replicated session object for Web application: {0}, session ID: {1}.

Cause: The ReplicationManager returned the NotFoundException.

Action: This happens if the object has been cleaned up underneath or the version number does not match with the secondary object. This should not happen normally. Unwanted failovers at the front end can cause unnecessary session failovers in the back end, which could result in this error in certain situations. Check the error message for more information.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100067: Failed to look up the secondary information for Web application: {0} session ID: {1}.

Cause: The ReplicationManager returned the NotFoundException. This happens if the object has been cleaned up underneath or the version number does not match with the secondary object. This should not happen normally. Unwanted failovers at the front end can cause unnecessary session failovers in the back end, which could result in this error in certain situations.

Action: Check the error message for more information.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100068: Failed to look up the secondary information for Web application: {0} session ID: {1}.

Cause: The ReplicationManager failed to look up the secondary information for a valid session.

Action: This is an unexpected error. Check the error message for details.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100069: The getAttribute(): {0} was a HomeHandle, reconstructing the EJBHome.

Cause: This is an informational message indicating that the container is storing only the handle for the EJBHome placed into the session.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP Session

BEA-100070: Error reconstructing the EJBHome put into session for name: {0}

Cause: The container found an EJBHome handle stored in the session. However, it failed to reconstruct the EJBHome using that EJBHome handle.

Action: Ensure that the HomeHandle is still valid. Check the exception text for the exact error message.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100071: The setAttribute(): {0} was an EJBHome, storing the HomeHandle into the session.

Cause: The container found an EJBHome handle stored in the session. It will reconstruct the EJBHome object before returning.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP Session

BEA-100072: Error in finding the HomeHandle for the EJBHome: {0}.

Cause: The container stores only the handle for an EJBHome put into the session. However, in this case, it failed to find the HomeHandle.

Action: Check the RemoteException for the exact error message details.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100073: Exception while serializing session object: {0}.

Cause: The session object failed to serialize.

Action: Check the exception text for the exact error message details.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100079: WAN failover configuration missing.

Cause: The JDBCTxDataSource or the backup cluster address was not properly configured.

Action: Set the JDBCTxDataSource or the backup cluster address to store session state.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100081: Persistent store settings cannot be changed between versions. The persistent store settings for application {0} is different from the settings for previous versions.

Cause: The persistent store settings of the new version were different from previous versions.

Action: Ensure that the persistent store settings are not changed when deploying a new version of an application.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100082: Failed to deploy {0} because the JDBC data source was missing. Target a JDBC data source to the cluster.

Cause: The configuration was incomplete.

Action: Target a JDBC data source to the cluster. Refer to the cluster documentation for more information.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100083: The Web application: {0} in application: {1} has its PersistenceStoreType set to: {2} for HTTP sessions. However, the target list does not contain all members of cluster: {3}. Non-homogeneous deployment for replicated sessions is not allowed.

Cause: Non-homogeneous deployment for replicated sessions is not allowed. The target list must be a cluster or a virtual host which is targeted to a cluster.

Action: Fix the targets for this Web application. Specify a cluster or virtual host as the target.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100084: The Web application: {0} in application: {1} has its PersistenceStoreType set to: {2} for HTTP sessions. However, the target list contains virtual host: {3}, for which the target list does not contain all members of cluster: {4}. Non-homogeneous deployment for replicated sessions is not allowed.

Cause: Non-homogeneous deployment for replicated sessions is not allowed. The target list must be a cluster or a virtual host which is targeted to a cluster.

Action: Fix the targets for this Web application.Specify a cluster or virtual host as the target.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100087: The JDBC session data for session ID: {0} has been modified by another server in the cluster.

Cause: The front-end Web server failed to maintain server affinity.

Action: Ensure that the front-end Web server or load balancer has been properly configured.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100089: The session ID: {0} has been accessed from {1}, a server that is neither the primary ({2}) nor the secondary ({3}). The request URL was: {4}

Cause: The most likely cause is a configuration error on a front end hardware loadbalancer or webserver plugin. They should be configured to respect the values of primary/secondary in the cookie (i.e., stickiness), when possible.

Action: Please ensure that the front end webserver or load-balancer has been properly configured.
Level: 1

Type: WARNING

Impact: HTTP Session

BEA-100090: An unexpected error occurred during a batched update of the last accessed time attribute of the updated sessions in application {0}.

Cause: Check the exception message for details.

Action: Check the exception message for details.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100094: The session ID: {0} has been accessed from {1}, a server that is not the primary ({2}). The request URL was: {3}.

Cause: The most likely cause is a configuration error on a front-end hardware load balancer or Web server plug-in. These should be configured to respect the values of the primary or secondary in the cookie (for example, stickiness), when possible.

Action: Ensure that the front-end Web server or load balancer has been properly configured.
Level: 1

Type: WARNING

Impact: HTTP Session

BEA-100095: persistent-data-source-jndi-name is required for an async-jdbc session.

Cause: persistent-data-source-jndi-name was not used to specify the data source JNDI name for the JDBC connection, but persistent-store-type is async-jdbc.

Action: Use persistent-data-source-jndi-name to specify the data source JNDI name for the JDBC connection.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100096: persistent-data-source-jndi-name will take effect and persistent-store-pool will be ignored for async-jdbc session in application {0}.

Cause: This is debug information.

Action: No action is required.
Level: 1

Type: WARNING

Impact: HTTP Session

BEA-100097: The IDLength {0} is too short. It is not secure. WebLogic Server will increase the length to {1}.

Cause: The IDLength of Session Descriptor is smaller than {1}.

Action: Mofify the Weblgoic deployment descriptor. Ensure that the IDLength of Session Descriptor is equal to or greater than {1}.
Level: 1

Type: WARNING

Impact: HTTP Session

BEA-100098: persistent-data-source-jndi-name or persistent-store-pool is required when persistent-store-type is jdbc.

Cause: persistent-data-source-jndi-name or persistent-store-pool was not used to configure the database connection, but persistent-store-type is jdbc.

Action: Use persistent-data-source-jndi-name or persistent-store-pool to configure the database connection.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-101002: [{0}] Could not deserialize the context attribute.

Cause: The classloader changed. When this happens, the old attributes will be deserialized using the new classloader.

Action: Ensure that the attribute class is available to the Web application scope and is serializable.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101003: [{0}] {1} called with a null document root.

Cause: The Web application did not initialize correctly.

Action: Check the log file for error messages about this Web application.
Level: 1

Type: INTERNAL_ERROR

Impact: HTTP

BEA-101005: [{0}] {1} called with unsafe path: "{2}".

Cause: The virtual path that was passed in points to a resource outside of the Web application scope.

Action: Check the virtual path being passed to the method and rectify the problem accordingly.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101008: [{0}] Cannot get InputStream of resource "{1}".

Cause: The getResourceAsStream() method failed to get an InputSteam for the resource.

Action: Ensure that the resource exists.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101017: [{0}] Root cause of ServletException.

Cause: The Web application container caught an unexpected exception.

Action: Check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101019: [{0}] Servlet failed with an IOException

Cause: An unexpected IOException was caught while processing the request.

Action: Check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101020: [{0}] Servlet failed with an Exception

Cause: An unexpected error occurred.

Action: Check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101024: [{0}] Unsupported error status code for the error-page element in web.xml.

Cause: The format of the error status code was invalid.

Action: Check the web.xml and fix the error-page element error status code.
Level: 1

Type: INTERNAL_ERROR

Impact: HTTP

BEA-101025: [{0}] Document root is null.

Cause: This should never happen. The initialization failed.

Action: Check the log file for error messages during the Web application initialization phase.
Level: 1

Type: INTERNAL_ERROR

Impact: HTTP

BEA-101027: [{0}] Document root: "{1}" does not exist.

Cause: This is an unexpected error message.

Action: Ensure that the directory exists.
Level: 1

Type: INTERNAL_ERROR

Impact: HTTP

BEA-101029: [{0}] cannot make temporary directory "{1}". Will not be able to compile JSPs.

Cause: The creation of the temporary directory failed.

Action: Check the write permissions.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101040: [{0}] Error occurred while trying to set "{1}{2}".

Cause: A NumberFormatException occurred while parsing the value assigned to the reloadCheckSecs parameter in web.xml.

Action: Ensure that the value was entered correctly.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101045: [{0}] {1}

Cause: This is a general purpose error message.

Action: Check the message for the exact cause and take proper action.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101046: [{0}] {1}

Cause: This is a general purpose error message.

Action: Check the exception for exact cause and take proper action.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101047: [{0}] {1}

Cause: This is a general purpose informational message for debug purpose only.

Action: This is a debug message. No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101051: [{0}] started

Cause: This is an informational message indicating that the Web server has been started.

Action: This is a debug message. No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101052: [{0}] Initialized

Cause: This is an informational message indicating that the Web server has been initialized.

Action: This is a debug message. No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101053: [{0}] Loading Web application: {1}

Cause: The Web application is being deployed.

Action: This is a debug message. No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101054: [{0}] {1} is the default Web application for {2}.

Cause: The given Web application is being registered as a default Web application.

Action: This is a debug message. No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101060: [{0}] Loading "{1}" from directory: "{2}"

Cause: The Web application was deployed using an exploded directory structure.

Action: This is a debug message. No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101061: [{0}] Could not find Web application "{1}".

Cause: The descriptor for the Web application with the name given could not be loaded.

Action: Check the error message for details and ensure that the Web application was configured properly.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101062: [{0}] Error reading Web application "{1}".

Cause: An IOException occurred while reading the descriptors for the Web application.

Action: Ensure that the web.xml and weblogic.xml descriptors exist in the right place.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101064: [{0}] Error parsing descriptor in Web appplication "{1}"

Cause: An unexpected error occurred while reading the descriptors for the Web application.

Action: Ensure that web.xml and weblogic.xml exist in the right place
Level: 1

Type: ERROR

Impact: HTTP

BEA-101066: [{0}] Cannot initialize HTTP URL resources. Could not get JNDI context: {1}.

Cause: The URL contexts could not be registered because the JNDI context was not found.

Action: Ensure that the JNDI resources were properly configured.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101067: [{0}] Disregarding null URL resource value for property {1}

Cause: The URL for the JNDI resource specified in URLResource was null.

Action: Correct the configuration (WebServerMBean). The URLs cannot be null.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101068: [{0}] Could not parse URL resource value {1}.

Cause: The URL for the JNDI resource specified in the URL resource was malformed.

Action: Correct the configuration (WebServerMBean). Specify a valid URL.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101069: [{0}] Could not bind URL {1} to JNDI name {2} error message: {3}.

Cause: The URL failed to bind with the JNDI name.

Action: Correct the configuration (WebServerMBean).
Level: 1

Type: ERROR

Impact: HTTP

BEA-101070: [{0}] Bound URL resource "{1}" to JNDI name "{2}".

Cause: This is an informational message only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101075: [{0}] HttpServer is shutting down.

Cause: The Web server is shutting down.

Action: This is a debug message. No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101083: Connection failure.

Cause: The connection failed while writing data into the stream.

Action: Check the exception for the exact cause and take appropriate action.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101086: No host in HTTP header. Dispatching to default HTTP server.

Cause: Host header missing.

Action: Ensure that the requests are accompanied with a host header in order for virtual hosting to work. Also, proper HTTP redirects must have a host header.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101087: {0} is not a virtual host. Dispatching to default HTTP server.

Cause: The host header is missing from the HTTP request.

Action: Make sure the requests are accompanied with a host header in order for Virtual Hosting to work. Also, proper HTTP redirects must have a host header.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101088: Dispatching request to {0}.

Cause: Dispatching the request to the Web server (Virtual Host) defined by the host header.

Action: Check the configuration.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101093: A problem occurred while dispatching the servlet request.

Cause: The request could not be dispatched into the execute queue.

Action: The request could be malformed. Check the exception for the exact cause.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101095: POST time exceeded the configured MaxPostTimeSecs of {0,number}.

Cause: The parameter makes sure that a malicious user does not send slow POSTs to cause a denial of service attack.

Action: If you think the time was too short, try increasing the value of MaxPostTimeSecs using the Administration Console.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101096: POST size exceeded the MaxPostSize={0,number}.

Cause: The parameter makes sure that a malicious user does not send huge POSTs to cause a denial of service attack.

Action: If you think the post size is unreasonable, try increasing MaxPostSize using the Administration Console.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101100: [{0}] Got bad cookie header: {1} from User-Agent: {2}

Cause: A cookie was malformed.

Action: Refer to the cookie specifications for the correct format: http://www.ietf.org/rfc/rfc2965.txt (Oct 2000; Obsoletes: 2109) http://www.ietf.org/rfc/rfc2109.txt (Feb 1997) http://www.ietf.org/rfc/rfc2616.txt (Jun 1999; Obsoletes: 2068) http://www.ietf.org/rfc/rfc2068.txt (Jan 1997)
Level: 1

Type: ERROR

Impact: HTTP

BEA-101101: [{0}] Unable to create new session.

Cause: A new session could not be created.

Action: Ensure that the persistent store has been properly configured.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101104: Servlet execution in servlet context "{0}" failed, {1}.

Cause: An unexpected error occurred while serving the request. This is not a simple client connection reset error.

Action: Check the error message for the exact cause.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101105: [{0}] error-page location: "{1}" for the error-code: "{2,number}" does not exist. Serving the default error page.

Cause: The error-page you configured in web.xml does not exist. A configuration error has occurred.

Action: Correct the web.xml descriptor, or make the resource available.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101106: [{0}] Could not serve custom error page: "{1}" for the error code: "{2,number}"

Cause: The error-page configured in web.xml does not exist. A configuration error has occurred.

Action: Correct the web.xml descriptor or make the resource available.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101107: [{0}] Problem occurred while serving the error page.

Cause: The error-page configured in web.xml could not be served.

Action: Check the configuration in web.xml.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101108: [{0}] Unsupported encoding: "{1}" specified.

Cause: The encoding specified is not supported by the underlying virtual machine(VM).

Action: Ensure that the encoding specified is valid or install the additional encoding classes.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101122: [{0}] Servlet: "{1}" is permanently unavailable.

Cause: The Web application is not currently available.

Action: Ensure that the Web application has been deactivated. Check to see if redeployment is in progress.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101123: [{0}] Servlet: "{1}" will be unavailable for the next: "{2,number}" seconds.

Cause: The servlet has been marked as unavailable.

Action: Make the request again after the specified time.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101125: [{0}] Error occurred while instantiating servlet: "{1}".

Cause: The servlet failed to instantiate.

Action: Ensure that the servlet has been configured properly in web.xml. Also, check the exception for the exact cause.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101126: [{0}] Error casting servlet: "{1}" to javax.servlet.Servlet

Cause: The servlet class that has been configured does not implement javax.servlet.Servlet.

Action: Fix the definition of the class.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101128: Initializing HTTP services.

Cause: This is an informational message.

Action: Ensure that the resources are available now.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101129: Initializing the Web application container.

Cause: This is an informational message.

Action: This is an informational message. No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101133: Initializing Web server {0}.

Cause: The Web server was just initialized.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101135: {0} is the default Web server.

Cause: The default Web server name is being logged.

Action: This is an informational message for debug purposes only. No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101136: Registering virtual host: {0}.

Cause: A Virtual Host (non-default Web server) has been registered.

Action: This is an informational message for debug purposes only. No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101138: {0} One of the getParameter family of methods was called after reading from the ServletInputStream. Not merging post parameters.

Cause: If the servlet reads the data from the input stream directly, then the request data will not be available for the getParameter family of methods.

Action: If the code relies on post parameters being available through the getParameter method, fix the code.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101140: An error occurred while creating servlet {1} (class: {2}, initArgs: {3}) for Web application {0}.

Cause: The servlet instance failed to initialize.

Action: Check the configuration and the exception for the exact error message.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101142: There was an error unregistering servlet runtime {0}.

Cause: The servlet runtime MBean that is used for monitoring could not be destroyed.

Action: Report this problem to My Oracle Support.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101143: An error occurred while unregistering Web application component runtime {0}.

Cause: The Web application runtime MBean that is used for monitoring could not be destroyed.

Action: Report this problem to My Oracle Support.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101159: [{0}] Received IllegalAccessException while instantiating servlet: "{1}". Ensure that the servlet implementation is a public class.

Cause: This occurs if WebLogic Server attempts to instantiate a servlet class that is not declared public.

Action: Ensure that the servlet implementation is a public class.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101160: Deployment descriptor is malformed; check against the DTD: {0}.

Cause: The web.xml file is not in strict conformance to the DTD. There may be deployment problems if this is not corrected.

Action: Check the web.xml file against the DTD to ensure conformance. Remember that the ordering of elements is important.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101162: User defined listener {0} failed: {1}.

Cause: The listener failed while processing the event fired by the container.

Action: Check the exception for the exact error message and fix the listener code.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101163: Could not load user defined listener: {0}

Cause: The listener class could not be loaded or instantiated.

Action: Check the exception for the exact error message and fix the listener code.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101164: User defined class {0} is not a listener, as it does not implement the correct interface(s).

Cause: The class is invalid.

Action: Fix the listener code to implement the appropriate interfaces.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101165: Could not load user defined filter in web.xml: {0}.

Cause: The filter class could not be loaded.

Action: Check the configuration and ensure that the class is avaliable to the context classloader.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101168: The security-role-assignment references an invalid security-role: {0}.

Cause: The security-role-assignment specified in weblogic.xml is not valid.

Action: Ensure that the role-name defined in web.xml, is valid. Also, check the DTD and examples for the correct syntax.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101169: The servlet {0} is referenced but not defined in web.xml.

Cause: The servlet-mapping element in web.xml refers to a servlet name that was not defined.

Action: Ensure that the servlet-name that is used for the mapping is defined. Check the DTD for the correct syntax.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101170: The servlet {0} is referenced in servlet-mapping {1} but not defined in web.xml.

Cause: The servlet-mapping element in web.xml refers to a servlet name that was not defined.

Action: Ensure that the servlet-name that is used for the mapping is defined. Check the DTD for the correct syntax.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101171: The web.xml descriptor has no resource-ref entries for the reference-descriptor defined in weblogic.xml.

Cause: The resource-ref-name referred to by the reference-descriptor in weblogic.xml should have a corresponding resource-ref-name defined in web.xml.

Action: Ensure that the resource-ref-name matches a resource-ref-name defined in web.xml.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101172: The web.xml descriptor has no ejb-ref entries.

Cause: The ejb-ref-name referred to by the reference-descriptor in weblogic.xml should have a corresponding ejb-ref-name defined in web.xml.

Action: Ensure that the ejb-ref-name matches a ejb-ref-name defined in web.xml.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101173: Did not find resource-ref in web.xml matching {0}.

Cause: The resource-ref-name referred to by the reference-descriptor in weblogic.xml should have a corresponding resource-ref-name defined in web.xml.

Action: Ensure that the resource-ref-name matches a resource-ref-name defined in web.xml.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101174: Did not find ejb-ref in web.xml matching {0}.

Cause: The ejb-ref-name referred to by the reference-descriptor in weblogic.xml should have a corresponding ejb-ref-name defined in web.xml.

Action: Ensure that the ejb-ref-name matches a ejb-ref-name defined in web.xml.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101175: [{0}] Exception occurred while closing zip file {1}.

Cause: A zip file failed to close while undeploying a Web application.

Action: Report this problem to My Oracle Support.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101180: The auth-constraint references security-role: {0}, which is not defined in web.xml.

Cause: The auth-constraint should refer to roles that have been defined in web.xml.

Action: Add the definition of this role in the security-role element of web.xml.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101188: A bad exception-type exists in web.xml: {0}.

Cause: An invalid class can cause this exception while registering the Web application.

Action: Check the classpath.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101189: Could not load the url-match-map class defined in weblogic.xml: {0}.

Cause: An invalid classname will cause this exception while registering the Web application.

Action: Check the classpath.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101194: The preprocessor {0} is referenced but not defined in weblogic.xml.

Cause: The preprocessor element is not defined in weblogic.xml.

Action: Check the weblogic.xml descriptor.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101196: [{0}]: Error while parsing the Tag Library Descriptor at "{1}".

Cause: A TLD parsing exception occurred.

Action: Check the exception for the exact cause.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101198: Could not deploy role: {0} for Web application: {1} application: {2}.

Cause: The Web application could not deploy the role defined in web.xml.

Action: Ensure that the security is configured properly in the server. Also, check the stack trace for the exact cause.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101199: Could not deploy policy for resource: {0}.

Cause: The Web application failed to deploy the policy for the security-constraint defined in web.xml.

Action: Ensure that the security is configured properly in the server. Also, check the stack trace for the exact cause.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101200: CacheFilter not caching the response for URI: {0} reason: {1}

Cause: The CacheFilter does not cache responses unless the status is 200.

Action: Check the message for information on how to fix the problem.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101212: {0}:{1} Failure while precompiling JSPs: {2}.

Cause: The JSPs failed to precompile at startup.

Action: Check the exception for the exact cause.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101214: Included resource or file "{0}" not found from requested resource "{1}".

Cause: The included resource or file is missing.

Action: Add the missing resource or file.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101215: Malformed request "{0}". Request parsing failed, Code: {1}

Cause: The request does not follow the pattern specified by the HTTP 1.0/1.1 specification(s).

Action: Fix the client that sent the invalid request.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101216: Servlet: "{0}" failed to preload on startup in Web application: "{1}".

Cause: The servlet that was marked as load-on-startup failed to preload on startup.

Action: Check the exception for the exact cause.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101217: Cannot deploy {0} from {1} on {2}, because there is already a Web application named {3} loaded from {4}, using the context path {5}.

Cause: The Web application that is being deployed has been assigned a context path that is already in use.

Action: Choose a different context path.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101218: An error exists in web.xml for servlet "{0}". Neither servlet-class nor jsp-file is defined.

Cause: The servlet element should contain either servlet-class or jsp-file. Both are missing.

Action: Update the web.xml descriptor.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101220: An error occurred while setting the document root for "{0}" to "{1}".

Cause: Setting the document root for the Web application failed. The Web application will not be deployed.

Action: Check the IOException message for exact cause of the problem.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101221: The url-pattern is empty or null for url-pattern {0} in {1}.

Cause: Not a valid url-pattern for the servlet.

Action: If the servlet is intended to be a default servlet, then specify / or /*.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101223: {0}: The server {1} is temporarily suspended.

Cause: The server has been suspended by the administrator.

Action: Wait until it comes back up again.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101226: AuthFilter: {0} invocation failed in: {1} phase for URI: {2}

Cause: The authentication filter that acts before and after the authentication phase failed to execute.

Action: Check the exception for the exact cause of the problem.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101228: Failed to undeploy security policy for resource: {0} while undeploying Web application.

Cause: The security policy defined in web.xml failed to undeploy upon Web application undeployment.

Action: Check the exception for the exact cause of the problem.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101229: Failed to undeploy security policy for resource: {0} while undeploying the Web application.

Cause: The security role defined in web.xml failed to undeploy upon Web application undeployment.

Action: Check the exception for the exact cause of the problem.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101231: The HTTP log file does not use version 1.0 of the Extended Log File format.

Cause: The ELF headers in the existing log file specify a version other than 1.0.

Action: Only version 1.0 is supported. Delete the existing log file and startover again.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101232: An exception occurred while reading headers of HTTP log file.

Cause: An IOException was received while reading the headers.

Action: Check the exception for the exact cause of the problem.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101234: Attempting to initialize ExtendedLogFormat application specific header: {0}. However, initialization failed due to an exception.

Cause: An unexpected error occurred while initializing the log file format.

Action: Check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101235: Attempting to initialize ExtendedLogFormat application specific header: {0}. However, initialization failed because class: {1} is not an instance of weblogic.servlet.logging.CustomELFLogger.

Cause: An unexpected error occurred while initializing the ExtendedLogFormat.

Action: Check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101236: The format of log field {0} is incorrect.

Cause: The format of the log field is invalid.

Action: Check the log field and fix the format.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101237: HTTP logging has been disabled for the Web server: {0}.

Cause: This is a debug message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101242: Failed to roll the HTTP log file for the Web server: {0}.

Cause: An unexpected error occurred.

Action: Check the exception message for the exact cause.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101247: {0}: Public ID references the old version of the Servlet DTD. Change the public ID in web.xml file to "{1}".

Cause: The public ID in WEB-INF/web.xml references the old version of servlet DTD.

Action: Generally, this will not cause any problems with the application unless the DTD has changed in a way such that the web.xml cannot be parsed. To avoid the message, change the public ID in the web.xml file to the current version of the servlet DTD.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101248: [{0}]: Deployment descriptor "{1}" is malformed. Check against the DTD: {4} (line {2}, column {3}).

Cause: The descriptor file is not in strict conformance to its DTD. There may be deployment problems if this is not corrected.

Action: Check the descriptor file against the DTD to ensure conformance. Remember that the ordering of elements is important.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101249: [{0}]: Servlet class {2} for servlet {1} could not be loaded because the requested class was not found in the classpath {3}. {4}.

Cause: The servlet class was not recognized by the Web application classloader.

Action: Ensure that the servlet class is available either in WEB-INF/classes or WEB-INF/lib or the system classpath.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101250: [{0}]: Servlet class {2} for servlet {1} could not be loaded because a class on which it depends was not found in the classpath {3}. {4}.

Cause: One of the classes the servlet class uses was not recognized by the Web application classloader.

Action: Make sure the class is available either in WEB-INF/classes or WEB-INF/lib or system classpath.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101251: [{0}]: Could not load servlet class {2} for servlet {1} because a resource on which it depends was not found in the classpath {3}. {4}.

Cause: This exception occurs if the Java Virtual Machine (JVM) cannot find an appropriate native-language definition of a method that is declared native.

Action: This could be due to a problem with path/LD_LIBRARY_PATH. Check if the resource it complains about exists.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101252: [{0}]: Servlet class {2} for servlet {1} could not be verified. {3}.

Cause: This exception occurs when the "verifier" detects that a class file, though well formed, contains some sort of internal inconsistency or security problem.

Action: Verify the servlet class.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101253: [{0}]: Servlet class {2} for servlet {1} could not be defined. The class file could be corrupt. {3}.

Cause: This exception occurs when the Java Virtual Machine (JVM) attempts to read a class file and determines that the file is malformed or otherwise cannot be interpreted as a class file.

Action: Check to see if the class file is corrupt.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101254: [{0}]: Servlet class {2} for servlet {1} could not be handled by the classloader with classpath {3}. {4}.

Cause: Subclasses of LinkageError indicate that a class has some dependency on another class; however, the latter class has incompatibly changed after the compilation of the former class.

Action: Check the class and its dependencies.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101256: The run-as user: {0} for the servlet: {1} for Web application: {2} could not be resolved to a valid user in the system. Verify that the user exists.

Cause: The run-as element in weblogic.xml refers to an invalid user.

Action: Check to see if the user exists.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101257: Failed to parse the client certificate in header: {0}. Ignoring this certificate.

Cause: The format of the client certificate was invalid.

Action: Check the exception for more details.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101258: Invalid JSP parameter in weblogic.xml with name: {0}.

Cause: The JSP parameter was not recognized.

Action: Check the weblogic.xml descriptor and refer to the DTD for the correct syntax and element information.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101260: The JSP parameter name in weblogic.xml is empty.

Cause: One of the mandatory elements in weblogic.xml was found to be empty.

Action: Check the weblogic.xml descriptor.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101261: Invalid session parameter name in weblogic.xml: {0}.

Cause: One of the session parameters configured in weblogic.xml was invalid.

Action: Check the weblogic.xml and correct the session parameter.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101262: The session parameter name "{0}" in weblogic.xml is deprecated.

Cause: This parameter has been deprecated.

Action: See the WebLogic Server documentation for an alternative. This parameter might be removed from future releases.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101263: The session parameter name in weblogic.xml is empty.

Cause: The param-name element is a mandatory element.

Action: Check the weblogic.xml descriptor.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101264: {0}: CLIENT-CERT-based authentication failed.

Cause: Authentication failed.

Action: Either the certificate was missing or the user the certificate resolves to is not a valid user in the system.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101267: Failed while destroying filter: {0}.

Cause: Destroying the filter on the Web application undeploy failed.

Action: There might be a problem in the implementation of the destroy method. Check the exception for the exact cause.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101268: {0}: Failed while destroying servlet: {1}.

Cause: Destroying a servlet on the Web application undeploy failed.

Action: There might be a problem in the implementation of the destroy method. Check the exception for the exact cause.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101271: The url-pattern element is not specified for the web-resource-collection/web-resource-name: {0} in the web.xml descriptor.

Cause: The url-pattern element is a mandatory element.

Action: If you want the security constraint to apply for all requests, specify url-pattern=/*.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101275: Server has detected non-replicated sessions while SUSPENDING. Server will wait for non-replicated sessions to either become invalidated or timed out or will wait until a secondary is chosen using the lazy process (meaning if a session does not have a secondary, the server waits until the next request to create the secondary). The current timeout value is {0} seconds. To terminate non-replicated sessions immediately, use the FORCESHUTDOWN option.

Cause: During graceful shutdown, the server waits for inflight work to complete. This includes non-replicated sessions.

Action: No action is required. Use FORCESHUTDOWN to ignore inflight work and force shutdown of the server.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101276: Web application(s) {1} still have non-replicated sessions after {0} minutes of initiating SUSPEND. Waiting for non-replicated sessions to finish.

Cause: The server is waiting for sessions to finish before gracefully shutting down.

Action: No action is required. Use FORCESHUTDOWN to ignore inflight work and shutdown the server.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101277: Web application(s) {0} has {1} non-replicated session(s) respectively.

Cause: The server has detected non-replicated sessions while gracefully shutting down.

Action: No action is required. Use FORCESHUTDOWN to ignore inflight work and shut down the server.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101278: There are no active sessions. The Web service is ready to suspend.

Cause: All active sessions have completed. The Web service is ready to gracefully shut down.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101280: Failed to create WebServerRuntimeMBean for the Web server: {0}.

Cause: The Web server creates a runtime MBean during the initialization phase for monitoring.

Action: Check the exception for exact cause.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101282: {0}: jspServlet "{1}" defined in weblogic.xml could not be registered. It should be a subclass of javax.servlet.http.HttpServlet.

Cause: The user-defined class should be a subclass of javax.servlet.http.HttpServlet.

Action: The jspServlet class must be a subclass of javax.servlet.http.HttpServlet.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101283: {0}: jspServlet "{1}" defined in weblogic.xml could not be loaded.

Cause: The user-defined class was unable to load.

Action: Ensure that the class appears in the webapp-classpath.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101287: {0}. The servlet: {1} received an exception during servlet destroy. Ensure that the super.init(config) is called in the init() method.

Cause: This is due to a bug in javax.servlet.GenericServlet.

Action: Ensure that the super.init(config) is called in the init() method for the servlet.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101288: Application:{0} WebAppModule: {1} failed to set contextPath: {2}.

Cause: The set context path call failed for the MBean.

Action: Check that the context path assigned to this Web application module is valid.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101291: The webAppModule: {1} in application: {0} is unable to reload classes because it shares a classloader with other modules.

Cause: An attempt to reload a class was made when the classloader was shared by other modules.

Action: Ensure that the module has its own classloader or reload all modules that share the classloader at once.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101292: Validation failed for the descriptor: {0} param: {1}.

Cause: The container found an illegal value assigned to this parameter.

Action: Check the error message for the exact cause.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101295: Recompiling JSP [{0}], resource [{1}], because it is stale. It was previously compiled using a different version of WebLogic Server. JSP build version: {2} WebLogic Server build version: {3}.

Cause: A JSP was compiled using a different version of WebLogic Server or JSPC.

Action: To precompile JSPs, ensure that you precompile them using the same version, service pack, rolling patches, and temporary-patches in your classpath for WebLogic Server or JSPC. This will ensure the same version string and compatibility at runtime.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101296: Unable to load the default compiler class "{0}". Using the default javac compiler to compile JSPs.

Cause: The compiler class was not found and hence could not be loaded.

Action: Ensure that the class exists in the classpath.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101297: The value assigned to the container-descriptor parameter: index-directory-sort-by in weblogic.xml is invalid: {0}. The valid values are "NAME", "LAST_MODIFIED", or "SIZE".

Cause: An invalid value is specified in weblogic.xml for the container-descriptor parameter: index-directory-sort-by.

Action: Fix the values in the weblogic.xml descriptor. Valid values are "NAME", "LAST_MODIFIED", or "SIZE".
Level: 1

Type: ERROR

Impact: HTTP

BEA-101299: The servlet-mapping for servlet-name "{0}" will override the default mapping for *.jsp. This can lead to a show code vulnerability.

Cause: The url-pattern *.jsp is being overriden in the web.xml by a user-defined servlet.

Action: Since the default JSP servlet will be overriden, care must be taken to ensure that JSP source code does not appear directly on the browser.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101302: Web application: {0}, the {1} role: {2} defined in the descriptor: {3} has not been mapped to a principal name in weblogic.xml. Will use the first principal-name: {4} specified in security-role-assignment as the run-as-identity. The run-as role can be mapped to a principal name in weblogic.xml using either run-as-role-assignment element or the servlet-descriptor/run-as-principal-name.

Cause: No mapping was found for the run-as role in weblogic.xml.

Action: Since the server has decided to use the implicit map, ensure that this is the principal-name you intended to use. The run-as role can be mapped to a principal name in weblogic.xml using either the run-as-role-assignment element or the servlet-descriptor/run-as-principal-name.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101303: Web application: {0}, the {1} role: {2} defined in the descriptor: {3} has not been mapped to a principal name in weblogic.xml. Also there is no security-role-assignment defined for this role. Will use the rolename itself as a principal-name for {1} for the servlet. The run-as role can be mapped to a principal name in weblogic.xml using either the run-as-role-assignment element or the servlet-descriptor/run-as-principal-name.

Cause: No mapping was found for the run-as role in weblogic.xml.

Action: Since the server has decided to use the implicit map, ensure that this is the principal-name you intended to use. The run-as role can be mapped to a principal name in weblogic.xml using either the run-as-role-assignment element or the servlet-descriptor/run-as-principal-name.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101304: Web application: {0}, the {1}: {3} defined in web.xml {2} not been mapped to principals in security-role-assignment in weblogic.xml. Will use the rolename itself as the principal-name.

Cause: Did not find a mapping for the roles which were supposed to be mapped to a principal in security-role-assignment in weblogic.xml.

Action: Since the server has decided to use the implicit map, ensure that this is the principal-name you intended to use.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101305: [{0}] Error-page location: "{1}" for the error code: "{2,number}" causes an infinite loop condition as it throws the same code for which it has been mapped.

Cause: The servlet for the error-page, which maps to the given error code, throws the same error code. This causes an infinite loop condition.

Action: Fix the error page
Level: 1

Type: ERROR

Impact: HTTP

BEA-101306: Could not resolve entity "{0}" for the webapp at: "{1}". Check the DTD reference in the corresponding descriptor (web.xml/weblogic.xml).

Cause: The descriptor validation failed.

Action: Check the DTD and ensure that the descriptors comply with that. Check the exception message for more details. Also, ensure that there are no typos in the DOCTYPE header.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101307: Got an error while resolving entity "{0}" for the Web application at: "{1}". Check the DTD reference in the corresponding descriptor (web.xml/weblogic.xml).

Cause: The descriptor validation failed.

Action: Check the DTD and ensure that the descriptors comply with that. Check the exception message for more details. Also, ensure that there are no typos in the DOCTYPE header.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101310: Web server: {0}, failed to perform batched update for replicated sessions against jndiname: {1} on the secondary server: {2} http-port: {3} https-port: {4}

Cause: The Remote Management Interface (RMI) call from the trigger, which was intended to periodically update the read-only replicated sessions on the secondary server, failed.

Action: Check the exception for the exact cause.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101317: The Web application: {0} has specified "DIGEST" as the auth-method in web.xml, which is not implemented. Will default to BASIC.

Cause: DIGEST authentication is not yet implemented. The Web application will fallback to BASIC authentication.

Action: Choose either BASIC, FORM, or CLIENT-CERT.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101318: The Web application: {0} has specified: {1} as the auth-method in web.xml, which is not valid. Valid values are BASIC (default), FORM, and CLIENT-CERT.

Cause: An invalid authentication method was specified in web.xml.

Action: The valid values are BASIC, FORM, and CLIENT-CERT. Fix the web.xml file for the Web application.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101319: The Web application: {0} has "FORM" based authentication specified but the mandatory element: {1} is left blank.

Cause: The form-login-page and form-error-page are mandatory elements when auth-method is "FORM."

Action: Fix the web.xml for the specified Web application.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101325: The local-path: {1} specified for the virtual-directory-mapping specified in weblogic.xml for the Web application: {0} (docroot={2}), is not valid.

Cause: A relative path was possibly assigned to the local-path. If so, the container makes the path relative to the document root.

Action: Ensure that the relative path exists with respect to the document root.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101326: The element: {1} contains an undefined security-role: {0}

Cause: The security-role definition is mandatory.

Action: Ensure that the security role-name is defined in web.xml. Also check the DTD and examples for the correct syntax.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101327: The element: {0} is not allowed to appear more than once in the descriptor: {1}

Cause: The parser found more than one occurrence for the element

Action: Ensure that than the element appears only once (check the schema).
Level: 1

Type: ERROR

Impact: HTTP

BEA-101328: {0}: invalid dispatcher: {2} for filter-mapping: {1}

Cause: An invalid value was found for the filter mapping dispatcher.

Action: Valid values are: "REQUEST," "FORWARD," "INCLUDE," or "ERROR."
Level: 1

Type: ERROR

Impact: HTTP

BEA-101331: Cannot deploy {0} from {1} on {2}, because there is already a non-versioned Web application named {3} loaded from {4}, using the context path {5}.

Cause: The Web application version that is being deployed has been assigned a context path that is already in use by a non-versioned Web application.

Action: Choose a different context path or undeploy the conflicting Web application.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101332: Failed to register JACC policy context handlers for the Web application container.

Cause: This is an unexpected error.

Action: See the error message for more information.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101337: Received a SecurityException during: {0}, for : {1}, Web application: {2}

Cause: The user does not have enough privileges.

Action: See the error message for more information.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101338: The context parameter "weblogic.httpd.defaultServlet" has been deprecated. Instead, use the servletMapping = "/" to define the default servlet.

Cause: A deprecated context parameter was used.

Action: The servlet weblogic.servlet.FileServlet is the default servlet. If you want to override the default, define a new servlet-mapping in web.xml with url-pattern = "/".
Level: 1

Type: WARNING

Impact: HTTP

BEA-101339: The context parameter: {0} has been deprecated. Instead, use the element: {1} in weblogic.xml.

Cause: A deprecated context parameter was used.

Action: Replace it with the suggested alternative in weblogic.xml.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101340: The context parameter "weblogic.httpd.servlet.classpath" has been deprecated. Instead use manifest classpath or WEB-INF/lib or WEB-INF/classes or virtual-directories in weblogic.xml

Cause: A deprecated context parameter was used.

Action: There are better ways to extend the classpath exposed to the Web application classloader, including virtual-directories and a manifest classpath.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101341: {0}: Class file up-to-date for JSP: {1}

Cause: This message indicates that the class file associated with the JSP is up-to-date.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101342: {0}: Error(s) encountered while precompiling JSP {1} {2}

Cause: The JSP file shown by the error message had errors and could not be precompiled.

Action: Correct the errors shown by the message so that it gets precompiled without errors.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101343: {0}: Attempting to precompile {1}, since the class file associated with it was found to be out-of-date.

Cause: This message indicates that the class file associated with the given JSP was out of date and needs recompilation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101344: {0}: Attempting to precompile {1}, since the class file associated with it was not found in the Web application classpath.

Cause: This message indicates that the class file associated with the given JSP was not found in the Web application classpath and thus needs to be compiled.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101345: A change in value was detected for the "Fields" directive in access.log for webserver: {0}. Rotating the access.log. The value defined for the WebServerMBean will take precedence. Default being "time cs-method cs-uri sc-status". Old value: "{1}" and new value: "{2}".

Cause: This message indicates that the value from WebServerMBean.getELFFields() was different that the value in the "Fields" directive on the top of access.log.

Action: Changing the ELF fields by hand editing access.log is no longer supported. Change the access.log "Fields" using the Administration Console.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101346: The virtual host name: {0} being used by the Virtual Host: {1} is already in use by: {2}

Cause: There is duplicate name usage for VirtualHostNames.

Action: Fix the VirtualHostNames fields for the Virtual Host and choose a unique name.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101347: The server channel name (NetworkAccessPoint): {0} being used by the Virtual Host: {1} is already in use by: {2}

Cause: There is uplicate name usage for ServerChannelName for Virtual Hosts.

Action: Fix the ServerChannelName field for the Virtual Host and choose a unique name.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101348: The server channel name (NetworkAccessPoint): {0} being used by the Virtual Host: {1} is not defined. This virtual host will not be deployed.

Cause: The NetworkAccessPoint is not yet defined.

Action: Choose a different NetworkAccessPoint name or define a new one using the Administration Console.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101349: Failed to save the WorkContexts into the session or cache for the request: {0}

Cause: An unexpected exception occurred.

Action: At the end of the request, the Web application container saves the WorkContexts into the session and the local cache in order to propagate them between successive HTTP requests. Contact My Oracle Support and report this problem.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101350: Web application(s) {2} of module {1} of application {0} has {3} pending session(s) respectively.

Cause: The server has detected pending sessions for the Web application module while the application is gracefully transitioning from running to administration mode.

Action: No action is required. Use the -force option to ignore inflight work and bring the application to administration mode.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101351: Server has detected pending sessions while gracefully transitioning webapp module {1} of application {0} from running to administration mode. Server will wait for pending sessions to either become invalidated or timed out. The current timeout value is {2} seconds. To terminate sessions immediately, use the -force option.

Cause: During graceful transition of the application from running to administration mode, the server waits for inflight work to complete. This includes pending sessions.

Action: No action is required. Use the -force to ignore inflight work and force transition of the application from running to administration mode.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101352: There are no active sessions. The Web application module {1} of application {0} is ready to go into administration mode.

Cause: All active sessions have completed. The Web service is ready to gracefully transition to administration mode.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101354: Web application(s) {3} of module {1} of application {0} still have pending sessions after {2} minutes of initiating transition from running to administration mode. Waiting for pending sessions to finish.

Cause: The server is waiting for the application sessions to finish before gracefully shutting down.

Action: No action is required. Use the -force option to ignore inflight work and force transition of the application into administration mode.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101355: [{0}] Version {2} is specified for Web Services {1}, but versioning of Web Services is not supported.

Cause: An attempt was made to deploy Web Services with versioning.

Action: Deploy the Web Services (or the application containing the Web Services) without versioning.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101356: Web application: {0} failed to load the shared library (fastfile) for using native I/O in the FileServlet, falling back to the standard I/O.

Cause: An unexpected error occurred while attempting to load the native library (fastfile) for using native I/O in the FileServlet.

Action: Ensure that the shared library (fastfile) exists in a directory that is in the LD_LIBRARY_PATH or PATH. Also, note that native I/O is supported on Windows, Linux, and Solaris. If problem persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101357: A force graceful production to administration mode transition was initiated. The Web application module {1} of application {0} is ready to go into administration mode.

Cause: A force graceful production to administration mode transition was initiated. The Web service is ready to transition to administration mode.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101359: The servlet {0} initilization method failed while it was run in the background. The exception was: {1}.

Cause: The servlet initilization method caused an exception.

Action: The cause of the exception must be corrected and then the application should be redeployed.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101360: Recompiling JSP [{0}], resource [{1}], because it is stale.

Cause: The JSP was changed from the last time it was compiled.

Action: The JSP will be always recompiled if it is different from the last compiled version.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101361: [{0}] A library reference in weblogic.xml has an illegal Specification-Version: {1}. The Specification-Version must be a valid version string: int(.int)*, int >=0. For example: 2.1.1.

Cause: The Specification-Version of a library reference in weblogic.xml cannot be parsed.

Action: Fix the library's Specification-Version in weblogic.xml to conform to the required version string syntax.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101362: [{0}] could not deserialize the {1} scoped attribute with name: "{2}"

Cause: Classloader changed. When this happens, the old attributes will be deserialized using the new classloader. The classloader can change either as the result of a dynamic reload of classes (controlled by weblogic.xml parameter "reload-check-secs" or upon across webapp dispatch (include or forward).

Action: Ensure that the attribute class is available to the Web application scope and that the attribute class and all the references it holds are serializable.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101363: Application: {0}, Web application: {1} has context-root specified in application.xml: "{2}". The context-root specified in weblogic.xml: "{3}" will be ignored.

Cause: The context-root specified in application.xml takes higher precedence than the one in weblogic.xml.

Action: This is an informational message. PEnsure that this is what you intended to do.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101364: {0}:{1} Failure while precompiling JSP: {2}.

Cause: The JSP failed to precompile on a partial update.

Action: Check the exception for the exact cause.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101366: The server could not send the HTTP message during the configured timeout value. The socket has been closed.

Cause: This is an informational message.

Action: Bump up the value of CompleteMessageTimeout. The default is 60 seconds. If you have slow clients that cannot complete the messsage transfer and are getting timed out, raise the value.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101367: An error occurred while extracting archived file for "{0}", located at "{1}".

Cause: An error occurred while extracting the archived WAR file, due to path length limitations on some OS's

Action: Some OS's only allow a certain number of characters in the file name. This limitation can be noticed when extracting an archive in a deeply nested directory. Since the default temporary directory for extracting all archives is relative to the server root directory, it is recommended that one use the system property weblogic.j2ee.application.tmpDir and set it to a shorter file path, or one could ensure that the server is started in a directory with a shorted file path.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101369: {0}: The encoding jsp-descriptor parameter has been deprecated. Consider declaring the encoding in the jsp-config element (web.xml) or as a page directive (pageEncoding) instead.

Cause: {0}: The encoding jsp-descriptor parameter has been deprecated.

Action: Consider declaring the encoding in the jsp-config element (web.xml) or as a page directive (pageEncoding) instead.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101370: There was a failure when merging library descriptors into the application descriptors for application {0}. Ensure that the descriptors are valid. The error is {1}

Cause: The library or the application descriptors are invalid.

Action: Fix the descriptors in the application or the library.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101371: There was a failure when processing annotations for application {0}. Ensure that the annotations are valid. The error is {1}

Cause: The descriptor has an invalid servlet-class, filter-class, or listener-class.

Action: Fix the descriptors in the application or the library.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101372: There was a failure in application {0} when attempting to inject dependencies into {1}. Dependencies will not be injected into this class.

Cause: The annotations defined in the class may be invalid or the descriptor may have conflicting entries.

Action: Check the annotations defined in this class. Also, verify that the descriptor has valid entries.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101373: Reloading classes in application {0} failed due to change of annotations on a refreshed class. Modified or new annotations will not be processed during servlet reload as they involve a non-dynamic change. Redeploy the application for these annotations to be processed.

Cause: New or modified annotations will not be processed in application {0} due to a servlet refresh.

Action: Redeploy the application for reloading classes when annotations are modified.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101374: The Web container failed to lookup the transaction associated with the current thread for Web application: ${0}.

Cause: After the response is sent, the container needs to check if there is any active transaction associated with the thread so that it can abort the transaction. See the exception message for more details.

Action: See the exception message for more details.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101375: [{0}]: Error while parsing the JSF Configuration Descriptor at "{1}".

Cause: A JSF Configuration Descriptor parsing exception occurred.

Action: Check the exception for the exact cause.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101376: Unable to purge cache of Bean classes from BeanELResolver, error occurs at "{0}".

Cause: Unable to get the cache property of BeanELResolver.

Action: Contact My Oracle Support and report this problem.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101377: Filtering class loader configuration ignored for web module {1} of application {0}

Cause: Filtering class loader configuration is only supported in descriptors at the main level of the deployment (for example, in enterprise applications or standalone web applications). Such configuration is not supported in web modules of an enteprise application.

Action: Remove the filtering class loader configuration from the deployment descriptor of web module {1} of application {0}
Level: 1

Type: WARNING

Impact: HTTP

BEA-101378: The version of OpenJPA shipped with WebLogic Server does not support JPA 2.0. Recompile the application with the JPA 1.0 API JAR available at http://www.jcp.org/en/jsr/summary?id=220

Cause: The Kodo-OpenJPA persistence provider that ships with WebLogic Server does not support JPA 2.0

Action: Recompile the application with the JPA 1.0 API jar available at http://www.jcp.org/en/jsr/summary?id=220 or use TopLink if you wish to use a JPA 2.0 persistence provider
Level: 1

Type: ERROR

Impact: HTTP

BEA-101379: Starting with WebLogic Server 10.3.4.0, some methods changed in the OpenJPA interfaces that ship with WebLogic Server. Recompile the application with the OpenJPA JAR in your WebLogic Server installation.

Cause: Some methods in the OpenJPA interfaces that ship with WebLogic Server have changed.

Action: Recompile the application with the OpenJPA JAR in your WebLogic Server installation.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101380: More than one web fragments with the same name: "{0}".

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

Action: Change one or more web fragment names to avoid the conflict.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101381: Both before others and after others found in web fragment: "{0}".

Cause: Both before others and after others found in web fragment.

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

Type: ERROR

Impact: HTTP

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

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

Action: Suggest to use servlet 3.0 annotations only
Level: 1

Type: ERROR

Impact: HTTP

BEA-101383: WLFilter annotation can't be used with WebFilter together

Cause: WLFilter annotation can't be used with WebFilter together.

Action: Suggest to use servlet 3.0 annotations only
Level: 1

Type: ERROR

Impact: HTTP

BEA-101384: {0} annotation is deprecated, please use servlet 3.0 annotation instead. App:{1}, Class:{2}

Cause: The older WL annotations are deprecated, and replaced by servlet 3.0 annotations , for example WLServlet is replaced by WebServlet, WLFilter is replaced by WebFilter.

Action: Suggest to use servlet 3.0 annotations instead if WL annotations
Level: 1

Type: WARNING

Impact: HTTP

BEA-101385: WebListener annotation is used illegally, the class annotated by WebListener must implement listener interface

Cause: WebListener annotation is used illegally, the class annotated by WebListener must implement listener interface, for example: javax.servlet.ServletContextListener and so on, please check the servlet 3.0 specification.

Action: The class annotated by WebListener must implement listener interface, for example: javax.servlet.ServletContextListener and so on, suggest to check the servlet 3.0 specification.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101386: The ServletSecurity Annotation is illegal, the root is {0}

Cause: The ServletSecurity Annotation is illegal, the root is {0}.

Action: Suggest not to correct ServletSecurity Annotation accroding to the Servlet 3.0 Specification.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101387: ServletContext has already been initialized, cannot call method {0} any longer.

Cause: ServletContext has already been initialized, cannot call method {0} any longer.

Action: Check Servlet 3.0 Specification and the corresponding javadoc.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101388: The ServletContext was passed to the ServletContextListener.contextInitialized method of a ServletContextListener that was neither declared in web.xml or web-fragment.xml, nor annotated with javax.servlet.annotation.WebListener.

Cause: The ServletContext was passed to the ServletContextListener.contextInitialized method of a ServletContextListener that was neither declared in web.xml or web-fragment.xml, nor annotated with javax.servlet.annotation.WebListener.

Action: Check Servlet 3.0 Specification and the corresponding javadoc.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101389: Cannot add this ServletContextListener

Cause: Because this ServletContext was passed to the ServletContextListener's contextInitialized() method of a ServletContextListener that was neither declared in web.xml or web-fragment.xml, nor annotated with javax.servlet.annotation.WebListener.

Action: Check Servlet 3.0 Specification and the corresponding javadoc.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101390: It is illegal to use both value and urlPatterns attributes together in the same WebServlet/WebFilter annotation: {0}.

Cause: As per the Servlet 3.0 specification, section 8.1, both the value attribute and urlPatterns attribute were detected in the identical WebServlet/WebFilter annotation.

Action: Use either the value attribute or urlPatterns attribute, but not both at the same time in the same annotation.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101391: Circular references found in web fragments relative ordering.

Cause: Circular references found in web fragments relative ordering.

Action: Use absolute ordering to overwrite relative ordering or change relative ordering config.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101392: Glassfish Descriptor element <{0}> was successfully parsed and applied.

Cause: This is an information message.

Action: No action is required if the element parsing was successful.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101393: Glassfish Descriptor element <{0}> is not supported by WebLogic.

Cause: This is an informational message.

Action: No action is required. Note that the element is ignored by the descriptor parser.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101394: The exception "{0}" occurred when processing getParameter or getParameterValues from a multipart value of a ServletRequest.

Cause: The exception "{0}" occurred when processing getPart or getParts from a ServletRequest.

Action: Check whether the size of the uploaded file exceeds the size limit. Check that the content of the post-multipart form data is correct.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101395: Application or module {0} is deployed as a web application.

Cause: The spplication or module {0} was deployed as a web application because there was no hint (descriptors or classes annotated by component annotations) detected. WebLogic Server deploys applications without deployment descriptors or classes annotated by component annotations as web application.

Action: No action is required if the application is a web application or a web module. Otherwise, add the corresponding deployment descriptors so that WebLogic Server can detect the application type correctly.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101396: Either the urlPatterns or the value attribute in the WebServlet annotation MUST be present: {0}.

Cause: As per the Servlet 3.0 specification, section 8.1.1, neither the value attribute nor the urlPatterns attribute was detected in the WebServlet annotation.

Action: Use either the value attribute or urlPatterns attribute, but not both at a same time in the same annotation.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101397: The urlPatterns attribute, servletNames attribute, or value attribute of the WebFilter annotation MUST be specified: {0}.

Cause: As per the Servlet 3.0 specification, section 8.1.2, neither the urlPatterns attribute, servletNames attribute, nor value attribute was detected in the WebFilter annotation.

Action: Use either the urlPatterns, servletNames, or value attribute in the annotation. Do not use both the urlPatterns and value attributes at a same time in the same annotation.
Level: 1

Type: ERROR

Impact: HTTP

BEA-110000: Transaction log record class name encoding error [{0}]: {1}

Cause: An internal error occurred while writing a record to the transaction log.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: JTA

BEA-110001: Transaction log record encoding error [{0}]: {1}

Cause: An internal error occurred.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: JTA

BEA-110003: onError() callback exception: {0}

Cause: An internal error occurred while writing a record to the transaction log.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: JTA

BEA-110004: Unable to read transaction log record checksum.

Cause: The transaction log file is corrupted, possibly due to a crash or file system error. If this error occurs only once per system reboot, a crash caused the transaction being logged at that time to be rolled back.

Action: No action is required. Recovery is automatic.
Level: 1

Type: WARNING

Impact: JTA

BEA-110005: Transaction log record checksum failure [{0}].

Cause: A record in the transaction log file is corrupted, possibly due to a crash or file system error. If this error occurs only once per system re-boot, a crash caused the transaction being logged at that time to be rolled back.

Action: No action is required. Recovery is automatic.
Level: 1

Type: WARNING

Impact: JTA

BEA-110007: Log record class instantiation problem [{0}]: {1}

Cause: An internal error occurred. This may have also occurred due to crash recovery processing of a new transaction log file performed by an older WebLogic Server software version.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JTA

BEA-110008: Log record class readExternal problem [{0}]: {1}

Cause: An internal error occurred. This may have also occurred due to crash recovery processing of a new transaction log file performed by an older WebLogic Server software version.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JTA

BEA-110011: onRecovery() callback exception: {0}.

Cause: This is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: JTA

BEA-110013: An error occurred while writing transaction log: {0}.

Cause: The file system is full or permission problems exist.

Action: Verify the transaction log file location and locate any file system problems.
Level: 1

Type: ERROR

Impact: JTA

BEA-110015: A version error occurred while reading the transaction log header file.

Cause: File corruption exists. A new transaction log file may have been given to an older version of WebLogic Server.

Action: The system will automatically create an empty transaction log.
Level: 1

Type: ERROR

Impact: JTA

BEA-110020: Error reading transaction log file [{0}]: {1}

Cause: There are file system or permission problems, or possible corruption of the transaction log.

Action: Verify the transaction log file location and check for file system problems. Crash recovery processing continues as best it can.
Level: 1

Type: ERROR

Impact: JTA

BEA-110021: Format error [{0}] occurred while reading transaction log file [{1}]

Cause: The transaction log file was possibly corrupted.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JTA

BEA-110022: Format error [{0}] occurred while reading transaction log file [{1}]: {2}

Cause: The transaction log file is possibly corrupted.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JTA

BEA-110023: Transaction log record checksum failure [{0}]: {1}.

Cause: A record in the transaction log file is corrupted, possibly due to a crash or file system error. If this error occurs only once per system reboot, a crash caused the transaction being logged at that time to be rolled back.

Action: No action is required. Recovery is automatic.
Level: 1

Type: WARNING

Impact: JTA

BEA-110026: Missing transaction log file [{0}]

Cause: File system or permission problems exist, or the transaction log might be corrupted. The file might also have been manually deleted.

Action: Verify the transaction log file location and check for file system problems. Crash recovery processing will continue.
Level: 1

Type: ERROR

Impact: JTA

BEA-110028: The transaction manager did not call XA.forget() for transaction [{1}] on resource [{0}], which reported a heuristic decision during commit.

Cause: See the message details for probable cause.

Action: After correcting any data inconsistencies due to the heuristic outcome, use the resource manager administrative commands to instruct the resource to ignore the transaction.
Level: 1

Type: NOTIFICATION

Impact: JTA

BEA-110029: The transaction manager did not call XA.forget() for transaction [{1}] on resource [{0}], which reported a heuristic decision during rollback.

Cause: See the message details for the probable cause.

Action: After correcting any data inconsistencies due to the heuristic outcome, use the resource manager administrative commands to instruct the resource to ignore the transaction.
Level: 1

Type: NOTIFICATION

Impact: JTA

BEA-110030: XA resource [{0}] has not responded in the last {1} second(s).

Cause: The resource is unavailable (possibly the resource is down, or network problems exist).

Action: Check the resource manager and network condition. When the resource is available again, take the following actions to inform the Transaction Manager: For JDBC connection pools, refresh the connection pool. You can also enable the auto-refresh feature of the connection pool to do this automatically. For other third-party XA resources, the resource provider should re-register the resource by calling weblogic.transaction.TransactionManager.unregisterResource(), followed by weblogic.transaction.TransactionManager.registerStaticResource() or weblogic.transaction.TransactionManager.registerDynamicResource().
Level: 1

Type: WARNING

Impact: JTA

BEA-110033: Recovered transaction log header file from backup location [{0}].

Cause: This error is probably caused by a crash that occurred when the the transaction log header file was being rewritten.

Action: No action is required. Recovery is automatic.
Level: 1

Type: ERROR

Impact: JTA

BEA-110101: No license exists for two-phase commit (2PC) processing.

Cause: The 2PC license is not present.

Action: Contact an Oracle sales representative to obtain a 2PC license.
Level: 1

Type: NOTIFICATION

Impact: JTA

BEA-110102: A transaction with multiple resources was rolled back due to an invalid two-phase commit (2PC) license.

Cause: The 2PC license is not present.

Action: Contact an Oracle sales representative to obtain a 2PC license.
Level: 1

Type: WARNING

Impact: JTA

BEA-110200: User [{0}] is not authorized to invoke startCommit on a transaction branch.

Cause: This might be a symptom of a potential security attack or, alternately, a problem with the "system" security identity of the server.

Action: Verify that the client software is not directly invoking an internal WebLogic Server system object.
Level: 1

Type: ERROR

Impact: JTA

BEA-110201: User [{0}] is not authorized to invoke startRollback on a transaction branch.

Cause: This might be a symptom of a potential security attack or, alternatively, a problem with the "system" security identity of the server.

Action: Verify that client software is not directly invoking an internal WebLogic system object.
Level: 1

Type: ERROR

Impact: JTA

BEA-110202: User [{0}] is not authorized to invoke rollback on a transaction branch.

Cause: This might be a symptom of a potential security attack, or alternately, a problem with the "system" security identity of the server.

Action: Verify that client software is not directly invoking an internal WebLogic system object.
Level: 1

Type: ERROR

Impact: JTA

BEA-110204: XA resource [{0}] returns XAER_RMFAIL and is unavailable.

Cause: The resource is unavailable because is down or network problems exist.

Action: Check the resource manager and network conditions. When the resource is available again, take the following actions to inform the Transaction Manager: For JDBC connection pools, refresh the connection pool. You can also enable the auto-refresh feature of the connection pool to do this automatically. For other third-party XA resources, the resource provider should re-register the resource by calling weblogic.transaction.TransactionManager.unregisterResource(), followed by weblogic.transaction.TransactionManager.registerStaticResource() or weblogic.transaction.TransactionManager.registerDynamicResource().
Level: 1

Type: WARNING

Impact: JTA

BEA-110207: A previously unavailable XA resource [{0}] is now available.

Cause: The previously unavailable resource is now available. It is possible that the resource has recovered from earlier failures or that previous network problems were cleared.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JTA

BEA-110208: Unregistration of Transaction Recovery Service for server [{0}] failed.

Cause: This is an internal error.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JTA

BEA-110209: Registration of Transaction Recovery Service for server [{0}] failed.

Cause: This is an internal error.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JTA

BEA-110210: Failback of Transaction Recovery Service for server [{0}] failed.

Cause: This is an internal error.

Action: Examine the migration errors and perform manual migration of the Transaction Recovery Service back to server [{0}].
Level: 1

Type: WARNING

Impact: JTA

BEA-110211: Failback retry of Transaction Recovery Service for server [{0}] failed.

Cause: This is an internal error.

Action: Examine the migration errors and perform manual migration of the Transaction Recovery Service back to server [{0}].
Level: 1

Type: WARNING

Impact: JTA

BEA-110212: An attempt was made to manually migrate the Transaction Recovery Service of the current server away from the server while it is still active.

Cause: An attempt was made to manually migrate the current Transaction Recovery Service away from the server while it is still active.

Action: For controlled migration, suspend or shut down the current server first before manually migrating it to a backup server.
Level: 1

Type: WARNING

Impact: JTA

BEA-110213: The activation of Transaction Recovery Service for server [{0}] failed.

Cause: This is an internal error.

Action: Examine the error details, correct the error conditions, and perform the necessary manual migration again if possible. If unsuccessful, My Oracle Support.
Level: 1

Type: WARNING

Impact: JTA

BEA-110400: An error occurred while unregistering Resource Runtime MBean: {0}

Cause: The MBean may have been unregistered previously or there may be an issue with the JMX Administration Server.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JTA

BEA-110401: Ignoring error in afterCompletion. Object={0}, Exception={1}

Cause: The application-defined javax.transaction.Synchronization callback may have caused an exception.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JTA

BEA-110402: Unknown state in getStatus(): {0}.

Cause: This is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: JTA

BEA-110403: An unexpected exception occurred while processing a transaction during a transaction manager timer event. Exception={0}.

Cause: Refer to the exception information found in the error message.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JTA

BEA-110405: Resource {0} was not assigned to any of these servers: {1}

Cause: The transaction coordinator maintains information regarding where resources are registered among all the servers that are known to the coordinator. The participating resource may have been unregistered or became unavailable prior to attempting the operation. This condition may also occur if the cache belonging to the coordinator was out of date or has not completed initialization at the time the operation was invoked.

Action: Verify the state of resource managers participating in the transaction and retry the operation.
Level: 1

Type: WARNING

Impact: JTA

BEA-110406: Internal error interpreting heuristic status. Expected={0}, Actual={1}

Cause: This is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: JTA

BEA-110407: Unknown state in getStatus(): {0}

Cause: This is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: JTA

BEA-110408: An attempt to add a duplicate transaction to the transaction manager list was ignored.

Cause: This is an internal error.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JTA

BEA-110409: Unable to advertise resource {0}: {1}

Cause: A problem may exist with the JNDI provider, or another object is already bound to this context.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JTA

BEA-110410: Unable to create resource runtime MBean for resource {0}: {1}

Cause: There may be a problem with the JMX Administration Server, or another MBean with this name is already registered with the Administration Server.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JTA

BEA-110411: Failed to construct local ServerCoordinatorDescriptor: {0}.

Cause: This is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JTA

BEA-110412: {0} completed heuristically: {1}.

Cause: The resource manager may have failed, timed out, or detected locking conflicts that prompted it to commit or roll back work for the transaction branch. If the heuristic error was due to a resource manager failure, the resource may not be able to determine if work for the transaction branch was committed, aborted, or both. In this case, the condition is considered a HAZARD or MIXED heuristic.

Action: Check the participants of the transaction should be checked for possible data corruption. The resource manager reporting the heuristic may maintain state information related to the updates involved in the heuristic error. If the JTA ForgetHeuristics configuration parameter is set to false, this information may be preserved in the resource manager. This information might be useful in correcting any data inconsistencies.
Level: 1

Type: ERROR

Impact: JTA

BEA-110414: Illegal State (expected: Prepared or Committing): {0}

Cause: This is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JTA

BEA-110415: Illegal state. Proceeding with rollback anyway. {0}

Cause: This is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JTA

BEA-110419: An attempt was made to add an incompatible object as a transaction property: keys must be strings and values must be serializable.

Cause: An attempt was made to add an incompatible object as a transaction property (the class of the key object must be a string and the class of the value object must be serializable).

Action: Change the application to assign the transaction property using a String key and a serializable value.
Level: 1

Type: ERROR

Impact: JTA

BEA-110420: An attempt was made to add an incompatible object as a local transaction property: keys must be String.

Cause: An attempt was made to add an incompatible object as a local transaction property (the key object must be of the class String).

Action: Change the application to add the local property with a String key.
Level: 1

Type: ERROR

Impact: JTA

BEA-110421: Internal error (possibly harmless): Timer method was called on committed transaction {0}.

Cause: This is an internal error, possibly due to a race condition.

Action: No action is required.
Level: 1

Type: ERROR

Impact: JTA

BEA-110422: Forcibly aborting a transaction found in an unexpected internal state. Details={0}

Cause: This is an internal error.

Action: Check for any data inconsistencies among participating resources. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JTA

BEA-110423: Abandoning transaction after {0} seconds: {1}

Cause: A resource or participating server may have been unavailable for the duration of the AbandonTimeoutSeconds period.

Action: Check participating resources for heuristic completions and correct any data inconsistencies.
Level: 1

Type: ERROR

Impact: JTA

BEA-110424: An unexpected exception was caught during begin: {0}

Cause: Check the exception detail portion of the log message.

Action: Correct the condition described in the exception detail portion of the log message.
Level: 1

Type: ERROR

Impact: JTA

BEA-110425: Error advertising TransactionManager object: {0}

Cause: There may be a problem with the JNDI provider or another object is already bound to this context.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JTA

BEA-110426: An error occurred while advertising UserTransaction object: {0}

Cause: There may be a problem with the JNDI provider, or another object is already bound to this context.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JTA

BEA-110427: An error occurred while advertising Coordinator object: {0}

Cause: There may be a problem with the JNDI provider, or another object is already bound to this context.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JTA

BEA-110428: An error occurred while exporting Coordinator object ID: {0}

Cause: Another remote object may be bound to this object ID.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JTA

BEA-110429: Error advertising SubCoordinator object: {0}.

Cause: There may be a problem with the JNDI provider, or another object is already bound to this context.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JTA

BEA-110433: Unable to obtain ownership of the transaction log.

Cause: The Transaction Recovery Service associated with the current server is currently owned by other servers.

Action: Migrate the Transaction Recovery Migratable Service back to the current server before restarting it.
Level: 1

Type: ERROR

Impact: JTA

BEA-110442: An administrative request was made to locally roll back the transaction associated with Xid {0}

Cause: The forced local rollback operation was initiated by an administrative application.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JTA

BEA-110443: An administrative request was made to locally commit the transaction associated with Xid {0}

Cause: The forced local commit operation was initiated by an administrative application.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JTA

BEA-110444: An administrative request was made to globally commit the transaction associated with Xid {0}.

Cause: A forced global rollback operation was initiated by an administrative application.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JTA

BEA-110445: An administrative request was made to globally commit the transaction associated with Xid {0}.

Cause: A forced global commit operation was initiated by an administrative application.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JTA

BEA-110446: The administrative request to locally roll back the transaction associated with Xid {0} failed because the transaction does not exist.

Cause: The transaction may have completed before the administrative request was made.

Action: No action is required.
Level: 1

Type: ERROR

Impact: JTA

BEA-110447: The administrative request to locally commit the transaction associated with Xid {0} failed because the transaction does not exist.

Cause: The transaction may have completed before the administrative request was made.

Action: No action is required.
Level: 1

Type: ERROR

Impact: JTA

BEA-110448: The administrative request to globally roll back the transaction associated with Xid {0} failed because the transaction does not exist.

Cause: The transaction may have completed before the administrative request was made.

Action: No action is required.
Level: 1

Type: ERROR

Impact: JTA

BEA-110449: The administrative request to globally commit the transaction associated with Xid {0} failed because the transaction does not exist

Cause: The transaction may have completed before the administrative request was made.

Action: No action is required.
Level: 1

Type: ERROR

Impact: JTA

BEA-110450: The administrative request to locally roll back the transaction {0} encountered an error {1}.

Cause: Refer to the exception information in the error message.

Action: Check to see if the transaction still exists. The operation may have resolved the transaction. If the problem persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JTA

BEA-110451: The administrative request to globally roll back the transaction {0} encountered an error {1}.

Cause: Refer to the exception information in the error message.

Action: Check to see if the transaction still exists; the operation may have resolved the transaction. If the problem persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JTA

BEA-110452: The administrative request to locally commit the transaction {0} encountered an error {1}.

Cause: Refer to the exception information in the error message.

Action: Check to see if the transaction still exists. The operation may have resolved the transaction. If the problem persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JTA

BEA-110453: The administrative request to globally commit the transaction {0} encountered an error {1}.

Cause: Refer to the exception information in the error message.

Action: Check to see if the transaction still exists. The operation may have resolved the transaction. If the problem persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JTA

BEA-110454: The administrative request to locally roll back the transaction {0} failed because the transaction is in an invalid state. {1}

Cause: The administrative request is invalid.

Action: Issue a forced commit operation instead to resolve the transaction.
Level: 1

Type: ERROR

Impact: JTA

BEA-110455: The administrative request to globally roll back the transaction {0} failed because the transaction is in an invalid state. {1}

Cause: The administrative request is invalid.

Action: Issue a forced commit operation instead to resolve the transaction.
Level: 1

Type: ERROR

Impact: JTA

BEA-110456: The administrative request to locally commit the transaction {0} failed because the transaction is in an invalid state. {1}

Cause: The administrative request is invalid.

Action: Issue a forced rollback operation instead to resolve the transaction.
Level: 1

Type: ERROR

Impact: JTA

BEA-110458: The administrative request to globally roll back the transaction {0} failed, because the coordinator {1} could not be contacted. {2}

Cause: The coordinating server for the transaction is either not running or is unreachable.

Action: Verify that the coordinating server is available and retry the operation. Alternatively, perform local operations to resolve the transaction.
Level: 1

Type: ERROR

Impact: JTA

BEA-110459: The administrative request to globally commit the transaction {0} failed, because the coordinator at {1} could not be contacted. {2}

Cause: The coordinating server for the transaction is either not running or is unreachable.

Action: Verify that the coordinating server is available and retry the operation. Alternatively, perform local operations to resolve the transaction.
Level: 1

Type: ERROR

Impact: JTA

BEA-110460: The administrative request to globally rollback the transaction {0} failed, because the coordinator does not support manual transaction resolution.

Cause: The coordinating server is an older version of WebLogic Server that does not support manual transaction resolution.

Action: Perform local commit operations on all participants that support manual transaction resolution.
Level: 1

Type: ERROR

Impact: JTA

BEA-110462: The administrative request to locally commit the transaction {0} failed, because the transaction has been marked for rollback.

Cause: The transaction has been marked for rollback by an application component.

Action: Attempt to resolve the transaction by using a forced rollback operation instead.
Level: 1

Type: ERROR

Impact: JTA

BEA-110464: The forced commit operation for transaction {0} on resource {1} was not performed, because the resource is busy.

Cause: There may be a blocked resource operation for this transaction. The resource may be experiencing problems or it may be slow to respond.

Action: Attempt to retry the commit operation. The associated resource changes for the transaction may need to be manually resolved using a resource-specific utility.
Level: 1

Type: ERROR

Impact: JTA

BEA-110465: The forced rollback operation for transaction {0} on resource {1} was not performed, because the resource is busy

Cause: There may be a blocked resource operation for this transaction. The resource may be experiencing problems or it may be slow to respond.

Action: Attempt to retry the commit operation. The associated resource changes for the transaction may need to be manually resolved using a resource-specific utility.
Level: 1

Type: ERROR

Impact: JTA

BEA-110466: The forced commit operation for transaction {0} on resource {1} was not performed because the resource has already been committed.

Cause: The transaction may have completed before the administrative client invoked the commit operation.

Action: No action is required. The transaction has been resolved.
Level: 1

Type: NOTIFICATION

Impact: JTA

BEA-110467: The forced rollback operation for transaction {0} on resource {1} was not performed because the resource has already been rolled back.

Cause: The transaction may have completed before the administrative client invoked the rollback operation.

Action: No action is required. The transaction has been resolved.
Level: 1

Type: NOTIFICATION

Impact: JTA

BEA-110468: The forced commit operation for transaction {0} on resource {1} encountered an error. {2}

Cause: Refer to the resource exception in the error message and any appropriate resource-specific error logs.

Action: Determine if administrative operations are required in the resource to resolve the transaction branch.
Level: 1

Type: ERROR

Impact: JTA

BEA-110469: The forced rollback operation for transaction {0} on resource {1} encountered an error. {2}

Cause: Refer to the resource exception in the error message and any appropriate resource-specific error logs.

Action: Determine if administrative operations are required in the resource to resolve the transaction branch.
Level: 1

Type: ERROR

Impact: JTA

BEA-110470: User [{0}] is not authorized to invoke a forced global rollback.

Cause: The authenticated principal making the request does not have adequate privileges to perform a forced rollback operation on the transaction.

Action: Authenticate using an identity with adequate privileges prior to invoking the operation.
Level: 1

Type: ERROR

Impact: JTA

BEA-110471: User [{0}] is not authorized to invoke a forced global commit.

Cause: The authenticated principal making the request does not have adequate privileges to perform a forced commit operation on the transaction.

Action: Authenticate using an identity with adequate privileges prior to invoking the operation.
Level: 1

Type: ERROR

Impact: JTA

BEA-110472: User [{0}] is not authorized to invoke a forced local rollback.

Cause: The authenticated principal making the request does not have adequate privileges to perform a forced rollback operation on the transaction.

Action: Authenticate using an identity with adequate privileges prior to invoking the operation.
Level: 1

Type: ERROR

Impact: JTA

BEA-110473: User [{0}] is not authorized to invoke a forced local commit.

Cause: The authenticated principal making the request does not have adequate privileges to perform a forced commit operation on the transaction.

Action: Authenticate using an identity with adequate privileges prior to invoking the operation.
Level: 1

Type: ERROR

Impact: JTA

BEA-110474: Unable to advertise non-XA resource {0}: {1}

Cause: There may be a problem with the JNDI provider, or another object is already bound to this context.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JTA

BEA-110475: User [{0}] is not authorized to invoke commit on a non-XA resource transaction branch.

Cause: This might be a symptom of a potential security attack or, alternatively, a problem with the "system" security identity of the server.

Action: Verify that client software is not directly invoking an internal WebLogic Server system object.
Level: 1

Type: ERROR

Impact: JTA

BEA-110476: The server has detected pending transactions during graceful shutdown. The server will wait for the pending transactions to complete before suspending the RMI service. A forced shutdown command can be issued to shut down the server immediately.

Cause: The server has detected pending transactions during graceful shutdown.

Action: No action is required. Use a forced shutdown command to ignore inflight work and shut down the server immediately.
Level: 1

Type: NOTIFICATION

Impact: JTA

BEA-110477: The unregisterResource operation for resource {0} timed out after {1} seconds.

Cause: It was requested that the specified resource be unregistered from the transaction manager and transactions that refer to the resource still exist on the server.

Action: Monitor inflight transactions to determine if there are still active transactions that depend on the unregistered resource. Options include using the Administration Console to manually resolve dependent transactions, or the resource may be redeployed for a sufficient period to allow the dependent transactions to complete.
Level: 1

Type: NOTIFICATION

Impact: JTA

BEA-110478: One-phase transaction [{1}] is in an unknown state for logging resource [{0}]. The transaction operations either all rolled back, or all committed, or are blocked. Transaction detail: [{2}]. Root cause: [{3}].

Cause: If the logging last resource is a database, there are a number of possible root causes. Among them are: the database may have shut down or crashed during the call to local commit, the database connection may have failed, the database local transaction may have timed out, or the database may have detected a potential deadlock condition introduced by application operations within the local commit.

Action: Examine the exception caused by the LLR resource to determine the root cause of the problem.
Level: 1

Type: WARNING

Impact: JTA

BEA-110479: Two-phase transaction [{1}], with logging resource [{0}], is an unknown state. The transaction manager will periodically retry determining the state of the transaction every [{3}] seconds. When the state is determined, the remaining resources in the transaction will be either rolled back or committed accordingly. Transaction detail: [{2}]. Root cause: [{4}].

Cause: If the logging last resource is a database, there are a number of possible root causes. Among them are: the database may have shutdown or crashed during the call to local commit, the database connection may have failed, the database local transaction may have timed out, or the database may have detected a potention dead-lock condition introduced by application operations within the local commit.

Action: Examine the exception caused by the LLR resource to determine the root cause of the problem. Note that no action may be required as the transaction manager will periodically retry the transaction until it can automatically rollback or commit accordingly.
Level: 1

Type: WARNING

Impact: JTA

BEA-110480: The transaction manager is completing logging resource [{0}] transaction [{1}]. The transaction, which was previously in an unknown state, is now resolved and in the [{2,choice,0#rollback|1#commit}] state.

Cause: See previous log messages for the same transaction to determine the root cause.

Action: See previous log messages for the same transaction to determine the root cause.
Level: 1

Type: NOTIFICATION

Impact: JTA

BEA-110482: A logging last resource (LLR) failed during initialization. The server cannot boot unless all configured LLRs initialize. Failing reason: {0}

Cause: If the logging last resource is a JDBC LLR connection, there are a number of possible root causes. Among them are: the database may have shut down or crashed, the database connection may have failed during boot, or the database connection may have incorrect database permissions.

Action: Examine the root exception thrown by the LLR to determine the root cause of the problem.
Level: 1

Type: INTERNAL_ERROR

Impact: JTA

BEA-110483: The JTA health state has changed from {0} to {1}.

Cause: An internal event has caused the JTA health state to transition to the normal state. Refer to previous health log entries for the conditions that have been corrected to trigger the state change.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JTA

BEA-110484: The JTA health state has changed from {0} to {1} with reason codes: {2}.

Cause: Refer to the message body for information regarding the events that caused the health change.

Action: Refer to the message body for the cause of the JTA state change and take the appropriate action to correct the exception condition.
Level: 1

Type: WARNING

Impact: JTA

BEA-110485: The JTA health state has changed from {0} to {1} with reason codes: {2}.

Cause: Refer to the message body for information regarding the events that caused the health change.

Action: Refer to the message body for the cause of the JTA state change and take the appropriate action to correct the exception condition.
Level: 1

Type: ERROR

Impact: JTA

BEA-110486: Transaction {0} cannot complete commit processing because resource [{1}] is unavailable. The transaction will be abandoned after {2} seconds unless all resources acknowledge the commit decision.

Cause: The resource may have been undeployed or is unresponsive and declared unavailable.

Action: Check for related server log messages that may provide additional details regarding the state of the resource. If the resource is undeployed, deploy the resource or the application module if the resource is application scoped. If a problem exists with the resource manager, correct the problem and redeploy the resource.
Level: 1

Type: WARNING

Impact: JTA

BEA-110487: Transaction {0} cannot complete rollback processing because the pending resource [{1}] is unavailable. The transaction will be abandoned after {2} seconds unless all resources acknowledge the rollback decision.

Cause: The resource may have been undeployed or is unresponsive and declared unavailable.

Action: Check for related server log messages that may provide additional detail regarding the state of the resource. If the resource is undeployed, deploy the resource or the application module if the resource is application scoped. If a problem exists with the resource manager, correct the problem and redeploy the resource.
Level: 1

Type: WARNING

Impact: JTA

BEA-110488: The LLR resource(s) {0} are not available and may contain transaction commit records required for recovery processing. Recovery of XA resources will not occur until these resources are deployed.

Cause: Prior to server restart, one or more global transactions were processed that had a LLR participant and may not have completed before the server was restarted. This potentially left a commit record in a LLR resource and prepared resource transaction branches that are awaiting a commit or rollback decision from the coordinator.

Action: Redeploy the specified LLR resources, wait for all in progress transactions to complete, and shut down the server gracefully.
Level: 1

Type: WARNING

Impact: JTA

BEA-110490: User [{0}] is not authorized to invoke Commit on a Coordinator.

Cause: This might be a symptom of a potential security attack, or alternately, a problem with the "system" security identity of the server.

Action: Verify that the client software is not directly invoking an internal WebLogic Server system object.
Level: 1

Type: ERROR

Impact: JTA

BEA-110491: User [{0}] is not authorized to invoke AckPrePrepare on a Coordinator.

Cause: This might be a symptom of a potential security attack or, alternatively, a problem with the "system" security identity of the server.

Action: Verify that the client software is not directly invoking an internal WebLogic Server system object.
Level: 1

Type: ERROR

Impact: JTA

BEA-110492: User [{0}] is not authorized to invoke CheckStatus on a Coordinator.

Cause: This might be a symptom of a potential security attack or, alternatively, a problem with the "system" security identity of the server.

Action: Verify that the client software is not directly invoking an internal WebLogic Server system object.
Level: 1

Type: ERROR

Impact: JTA

BEA-110493: User [{0}] is not authorized to invoke AckCommit on a Coordinator.

Cause: This might be a symptom of a potential security attack or, alternatively, a problem with the "system" security identity of the server.

Action: Verify that the client software is not directly invoking an internal WebLogic Server system object.
Level: 1

Type: ERROR

Impact: JTA

BEA-110494: User [{0}] is not authorized to invoke NakCommit on a Coordinator.

Cause: This might be a symptom of a potential security attack or, alternatively, a problem with the "system" security identity of the server.

Action: Verify that the client software is not directly invoking an internal WebLogic Server system object.
Level: 1

Type: ERROR

Impact: JTA

BEA-110495: User [{0}] is not authorized to invoke AckRollback on a Coordinator.

Cause: This might be a symptom of a potential security attack or, alternatively, a problem with the "system" security identity of the server.

Action: Verify that the client software is not directly invoking an internal WebLogic Server system object.
Level: 1

Type: ERROR

Impact: JTA

BEA-110496: User [{0}] is not authorized to invoke NakRollback on a Coordinator.

Cause: This might be a symptom of a potential security attack or, alternatively, a problem with the "system" security identity of the server.

Action: Verify that the client software is not directly invoking an internal WebLogic Server system object.
Level: 1

Type: ERROR

Impact: JTA

BEA-110500: User [{0}] is not authorized to invoke GetSubCoordinatorInfo on a SubCoordinator.

Cause: This might be a symptom of a potential security attack or, alternatively, a problem with the "system" security identity of the server.

Action: Verify that the client software is not directly invoking an internal WebLogic Server system object.
Level: 1

Type: ERROR

Impact: JTA

BEA-110501: User [{0}] is not authorized to invoke GetProperties on a SubCoordinator.

Cause: This might be a symptom of a potential security attack or, alternatively, a problem with the "system" security identity of the server.

Action: Verify that the client software is not directly invoking an internal WebLogic Server system object.
Level: 1

Type: ERROR

Impact: JTA

BEA-110502: User [{0}] is not authorized to invoke Recover on a SubCoordinator.

Cause: This might be a symptom of a potential security attack or, alternatively, a problem with the "system" security identity of the server.

Action: Verify that the client software is not directly invoking an internal WebLogic Server system object.
Level: 1

Type: ERROR

Impact: JTA

BEA-110503: The migrator (the Administration Server for manual JTA migration policy or the Singleton Master for automatic JTA migration policy) is not available. Will skip JTA TRS failback because isStrictOwnershipCheck is [false]. This may lead to potencial TLOG corruption if the TRS of {0} has been migrated to a backup server and the backup server is accessing the TLOG of {0}. More safety can be achieved by setting isStrictOwnershipCheck to [true].

Cause: The Administration Server or Singleton Master is not running or cannot be reached.

Action: Start Administration Server or Singleton Master before starting any Managed Server in the cluster.
Level: 1

Type: WARNING

Impact: JTA

BEA-110504: There was an error advertising TransactionSynchronizationRegistry object: {0}.

Cause: There may be a problem with the JNDI provider or another object is already bound to this context.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JTA

BEA-110505: An attempt was made to set an invalid TRANSACTION_COMPLETION_TIMEOUT_SECONDS_PROPERTY_KEY for transaction property: keys must be number and values must be between -1 and max value of integer.

Cause: See the message detail.

Action: Change the application to assign the proper TRANSACTION_COMPLETION_TIMEOUT_SECONDS_PROPERTY_KEY property value.
Level: 1

Type: ERROR

Impact: JTA

BEA-111001: The Transaction Manager is being started in standalone mode and will not be able to participate in distributed transactions.

Cause: There are no suitable RMI or JNDI providers configured.

Action: Configure the appropriate RMI and JNDI context providers.
Level: 1

Type: NOTIFICATION

Impact: JTA

BEA-111002: The Transaction Manager is being started in distributed mode.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: JTA

BEA-111003: An error occurred while creating the transaction log persistent store: {1}.

Cause: Refer to the associated exception.

Action:
Level: 1

Type: NOTIFICATION

Impact: JTA

BEA-111004: Transaction could not set CoordinatorURL to use AdminChannel downgrading {0}.

Cause: This is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: JTA

BEA-111005: An in-progress XA operation for transaction {0} on resource {1} could not complete within {2} seconds, or was interrupted. Allowing subsequent calls to proceed.

Cause: The call to the resource manager may have been affected by a server or network problem and could have been interrupted.

Action: Verify that the resource manager is functioning properly and accessible.
Level: 1

Type: NOTIFICATION

Impact: JTA

BEA-111006: Transaction could not set CoordinatorURL to use SSL URL downgrading {0}

Cause: This is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: JTA

BEA-111007: The commit operation for one-phase transaction {0} on resource {1} encountered an error. {2}

Cause: Refer to the resource exception in the error message and any appropriate resource-specific error logs.

Action: Determine if administrative operations are required in the resource to resolve the transaction branch.
Level: 1

Type: ERROR

Impact: JTA

BEA-111008: Transaction Log failed during initialization. The server cannot boot unless Transaction Log initialize. Failing reason: {0}

Cause: An internal error occurred.

Action: Determine the root cause of the problem.
Level: 1

Type: INTERNAL_ERROR

Impact: JTA

BEA-111009: activateDeployments failed during initialization. Failing reason: {0}

Cause: An internal error occurred.

Action: Contact My Oracle Support.
Level: 1

Type: INTERNAL_ERROR

Impact: JTA

BEA-111010: SetPrimaryStore failed. Failing reason: {0}

Cause: An internal error occurred.

Action: Contact My Oracle Support.
Level: 1

Type: INTERNAL_ERROR

Impact: JTA

BEA-111011: A Transaction Log PrimaryStore failed during initialization. The server cannot boot unless configured Transaction Log Primary Store initialize. Failing reason: {0}

Cause: An internal error occurred.

Action: Examine the root exception thrown by the Transaction Log Primary Store to determine the root cause of the problem.
Level: 1

Type: INTERNAL_ERROR

Impact: JTA

BEA-111012: SetPrimaryStore close failed when retry. Failing reason: {0}

Cause: An internal error occurred.

Action: Contact My Oracle Support.
Level: 1

Type: INTERNAL_ERROR

Impact: JTA

BEA-111013: Recover JDBCStore init store exception: {0}

Cause: An internal error occurred.

Action: Contact My Oracle Support.
Level: 1

Type: INTERNAL_ERROR

Impact: JTA

BEA-111014: There is a naming conflict for resource = [{0}]. This resource is being registered by this server and has already been registered in: [{1}].

Cause: This resource is trying to be registered as a NonXAResource but was already registered as an XAResource.

Action: Correct the configuration either by making the resource name unique or by making the resource consistently either an XAResource or a NonXAResource.
Level: 1

Type: ERROR

Impact: JTA

BEA-114089: User [{0}] is not authorized to invoke ackPrepare on a Coordinator.

Cause: This might be a symptom of a potential security attack or, alternatively, a problem with the "system" security identity of the server.

Action: Verify that the client software is not directly invoking an internal WebLogic Server system object.
Level: 1

Type: ERROR

Impact: JTA

BEA-119000: One-phase transaction [{1}] for logging last resource [{0}] is in an unknown state.

Cause: If the LLR is a database, there are a number of possible root causes. Among them are: the database may have shut down or crashed during the call to local commit, the database connection may have failed, the database local transaction may have timed out, or the database may have detected a potential deadlock condition introduced by application operations within the local commit.

Action: Examine the root exception generated by the LLR to determine the root cause of the problem.
Level: 1

Type: WARNING

Impact: JTAExceptions

BEA-119001: Two-phase transaction [{1}] for logging last resource [{0}] is in an unknown state.

Cause: If the LLR is a database, there are a number of possible root causes. Among them are: the database may have shut down or crashed during the call to local commit, the database connection may have failed, the database local transaction may have timed out, or the database may have detected a potential deadlock condition introduced by application operations within the local commit.

Action: Examine the root exception generated by the LLR resource to determine the root cause of the problem.
Level: 1

Type: WARNING

Impact: JTAExceptions

BEA-119002: A LLR failed during initialization. The server cannot boot unless all configured LLRs initialize. Failing reason: {0}

Cause: If the LLR is a JDBC LLR connection, there are a number of possible root causes. Among them are: the database may have shut down or crashed, the database connection may have failed during boot, or the database connection may have incorrect database permissions.

Action: Examine the root exception generated by the LLR resource to determine the root cause of the problem.
Level: 1

Type: INTERNAL_ERROR

Impact: JTAExceptions

BEA-119003: LLR [{0}] failed during initialization, as one of its records is corrupted. Failure reason: {1}

Cause: The cause is unknown, but could be possible disk corruption.

Action: Examine the root exception generated by the LLR to determine the root cause of the problem. Possible solutions are: restore LLR resource tables from backup, delete the failing LLR table (which risks producing heuristic hazards), or contact My Oracle Support.
Level: 1

Type: INTERNAL_ERROR

Impact: JTAExceptions

BEA-119004: The user-preferred server of JTAMigratableTargetMBean [{0}] cannot be set to [{1}].

Cause: The value of the user-preferred server is invalid. It must be [{0}].

Action: Change the value of the user-preferred server of JTAMigratableTargetMBean [{0}] from [{1}] to [{0}].
Level: 1

Type: ERROR

Impact: JTAExceptions

BEA-119005: JTA subsystem failed. A forced shutdown of the server was done because the server is in automatic JTA migration mode.

Cause: The JTA subsystem failed.

Action: JTA Transaction Recovery Service will be automatically migrated to back up the server.
Level: 1

Type: ERROR

Impact: JTAExceptions

BEA-119006: A Transaction Log Primary Store failed during initialization. The server cannot boot unless the configured Transaction Log Primary Store initialize. Failing reason: {0}

Cause: This is an internal error.

Action: Examine the root exception generated by the Transaction Log Primary Store to determine the root cause of the problem.
Level: 1

Type: INTERNAL_ERROR

Impact: JTAExceptions

BEA-130000: Insertion of {0} into XML entity cache rejected. Entity size, {1}, exceeded cache size, {2}.

Cause: The cache may be too small or a specific item might be very large. The worst case is that this indicates a denial of service attack.

Action: No action is required. However, performance will be best if items are cached.
Level: 1

Type: WARNING

Impact: XML

BEA-130001: Entity cache appears to be broken. This impacts the performance of XML parsing.

Cause: Unknown

Action: No action is required. However, performance will increase if items are cached. Also the cache provides a backup in the case of a network failure. While the cache is not operating, this backup is not in effect.
Level: 1

Type: WARNING

Impact: XML

BEA-130002: The entity that was just put in the cache cannot be retrieved: "{0}". Timeout may be too short.

Cause: Usually this indicates that the entity timeout was set to a very small value. Otherwise, there is some unknown problem with the cache module itself.

Action: No action is required, but XML parse performance will be impacted. Also, there is no cached copy to act as a backup in the event of a network failure.
Level: 1

Type: WARNING

Impact: XML

BEA-130003: Could not instantiate the specified factory class. {0}.

Cause: The class name of the factory was not correct or it was not in the CLASSPATH.

Action: Check the CLASSPATH or verify the Administration Console entry or MBean value.
Level: 1

Type: ERROR

Impact: XML

BEA-130006: XML cache warning for registry {0}: entry rejection due to entry being larger than the cache memory size. entry: {1} Entry memory size: {2}

Cause: The entry is larger than the cache.

Action: No action is required unless the item should be cached next time. If so, increase the cache memory size.
Level: 1

Type: WARNING

Impact: XML

BEA-130007: XML cache event: memory purge of {0} entries of combined size {1}. Current memory usage is {2} bytes.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: XML

BEA-130008: XML cache event: disk purge of {0} entries of combined size {1}. Current disk usage is {2} bytes.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: XML

BEA-130009: XML cache warning for registry {0}: entry persist attempt rejected due to entry being larger than the cache disk size. Status changed to transient. entry: {1} entry disk size: {2}

Cause: The size of the entry on the disk exceeds the allocated disk space.

Action: No action is required. If the entry should be persisted next time, increase the disk size of the cache.
Level: 1

Type: WARNING

Impact: XML

BEA-130010: XML cache event for registry {0}: entry added. entry: {1}, entry memory size: {2}, storage type: {3}, current memory usage (bytes): {4}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: XML

BEA-130011: XML cache event for registry {0}: entry deleted. entry: {1}, entry memory size: {2}, entry disk size: {3}, current memory usage (bytes): {4}, current disk usage (bytes): {5}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: XML

BEA-130012: XML cache event for registry {0}: entry persisted. entry: {1}, entry disk size: {2}, current disk usage (bytes): {3}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: XML

BEA-130013: XML cache event for registry {0}: entry loaded. entry: {1}, entry memory size: {2}, current memory usage (bytes): {3}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: XML

BEA-130014: XML cache event: statistics checkpointed.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: XML

BEA-130015: XML cache event: cache created. current memory usage (bytes): {0}, current disk usage (bytes): {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: XML

BEA-130016: XML cache event: cache loaded. Current memory usage (bytes): {0}, current disk usage (bytes): {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: XML

BEA-130017: XML cache event: cache closed. current disk usage (bytes): {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: XML

BEA-130018: XML cache error: cache file {0} is corrupted. Creating new cache from scratch.

Cause: The cache file was corrupted. This normally does not occur.

Action: The server should be restarted. If a backup of the cache files exists, restore the cache files, and then restart the server.
Level: 1

Type: ERROR

Impact: XML

BEA-130019: XML cache error for registry {0}: entry file {1} is corrupted. Removing from cache. entry: {2}

Cause: The cache file was corrupted. This normally does not occur.

Action: The server should be restarted. The entry will be re-cached on the next access of the server.
Level: 1

Type: ERROR

Impact: XML

BEA-130020: XML cache error: statistics file {0} is corrupted, reinitializing. Previous statistics are lost.

Cause: The cache file was corrupted. This normally does not occur.

Action: The server should be restarted.
Level: 1

Type: ERROR

Impact: XML

BEA-130021: XML cache error for registry {0}: entry file {1} cannot be written. Status changed to transient. entry: {2}

Cause: This is often a file protection issue.

Action: Determine why the file cannot be saved and make the appropriate adjustments.
Level: 1

Type: ERROR

Impact: XML

BEA-130022: XML cache error: cache file {0} cannot be written.

Cause: This is often a file protection issue.

Action: Determine why the file cannot be saved and make the appropriate adjustments.
Level: 1

Type: ERROR

Impact: XML

BEA-130023: XML cache error: statistics file {0} cannot be written. There are no futher cache statistics for this session.

Cause: This is often a file protection issue.

Action: Determine why the file cannot be saved and make the appropriate adjustments.
Level: 1

Type: ERROR

Impact: XML

BEA-130024: XML cache error for registry {0}: out of memory loading entry. Entry removed from cache. entry: {1}, file: {2}

Cause: The entry might be unusually large or perhaps the JVM heap size is too small.

Action: Check the size of the rejected entry. If entries of that size need to be handled, increase the heap size.
Level: 1

Type: ERROR

Impact: XML

BEA-130025: XML cache error: out of memory loading cache. Cache not opened. file: {0}

Cause: The cache file is not large, so memory usage is almost full.

Action: Increase the JVM heap size.
Level: 1

Type: ERROR

Impact: XML

BEA-130026: XML cache error: out of memory loading statistics. File: {0}

Cause: The cache file is not large, so memory usage is almost full.

Action: Increase the JVM heap size.
Level: 1

Type: ERROR

Impact: XML

BEA-130027: XML cache warning: the requested memory size of the XML cache, {0}, exceeds the available memory, {1}.

Cause: Either the provided parameters are not in sync with the usage, or a lot of the available memory is being used.

Action: Reduce the cache size or increase the JVM heap size. If there should be more available memory, determine what is using all of the available memory.
Level: 1

Type: WARNING

Impact: XML

BEA-130028: XML cache warning: the requested memory size of the XML cache, {0}, is a large percentage of the available memory, {1}.

Cause: Either the provided parameters are not in sync with the usage, or something is using a lot of the available memory.

Action: Reduce the cache size or increase the JVM heap size. If there should be more available memory, determine what is using all of the available memory.
Level: 1

Type: WARNING

Impact: XML

BEA-130029: XML cache error: an unexpected error occurred in the XML cache. {0}

Cause: The cause is unknown.

Action: Refer to the associated text at the end of the message and contact My Oracle Support for help resolving the error.
Level: 1

Type: ERROR

Impact: XML

BEA-130030: XML cache error for registry {0}: the file, {1}, representing entry {2} cannot be read.

Cause: The file is read-protected.

Action: Check the access rights of the file and make the appropriate changes.
Level: 1

Type: ERROR

Impact: XML

BEA-130031: XML cache error: the cache file, {0}, cannot be read.

Cause: The file is read-protected.

Action: Check the access rights of the file and make the appropriate changes.
Level: 1

Type: ERROR

Impact: XML

BEA-130032: XML cache error: statistics file {0} cannot be read.

Cause: The file is read-protected.

Action: Check the access rights of the file and make the appropriate changes.
Level: 1

Type: ERROR

Impact: XML

BEA-130033: Parser or DocumentBuilder cannot be created to satisfy the configuration requested. {0}

Cause: The configuration was invalid.

Action: Verify that the factory that creates the parser and the properties or features set on this parser are configured properly.
Level: 1

Type: ERROR

Impact: XML

BEA-130034: Failed to parse the given XML document. {0}

Cause: An error occurred in the structure of the XML document.

Action: Verify the XML syntax of the document.
Level: 1

Type: ERROR

Impact: XML

BEA-130035: Failed to open XML document. {0}

Cause: The file does not exist.

Action: Check the file name, the file location and its associated permissions.
Level: 1

Type: ERROR

Impact: XML

BEA-130036: Initializing XMLRegistry

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: XML

BEA-130037: The stack trace associated with message {0} follows:

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: XML

BEA-140008: Internal error. Failed to save configuration changes to the configuration repository - {0}.

Cause: The config.xml file is either write-protected, or the user that started the server is not authorized to write to this file or directory.

Action: Ensure that the operating system user who starts the server has authorization to write to the config.xml file and that the config.xml file is not write-protected.
Level: 1

Type: ERROR

Impact: Management

BEA-140013: {0}

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141009: Error occurred in the file distribution servlet while processing the request type "{0}", {1}.

Cause: Refer to the embedded exception information for more details as to the probable cause of this error.

Action: Take action based upon the provided exception details.
Level: 1

Type: ERROR

Impact: Management

BEA-141010: Error occurred in the file distribution servlet and received an unacceptable request of type "{0}".

Cause: An invalid request was made to the file distribution servlet.

Action: This is an internal error. No action is required.
Level: 1

Type: ERROR

Impact: Management

BEA-141011: The file distribution servlet failed to distribute the security properties file, because the file was not found at the configured location: {0}.

Cause: The identified file was not available to the Administration Server.

Action: Verify the configuration of this file.
Level: 1

Type: ERROR

Impact: Management

BEA-141021: The cluster property {0} was ignored because the server is not part of a cluster.

Cause: A non-applicable cluster property was specified at server startup.

Action: Modify the configuration to identify that this Managed Server is, in fact, a member of a cluster, or eliminate the specification of the cluster property from the start command.
Level: 1

Type: WARNING

Impact: Management

BEA-141023: An error occurred while setting the attribute value in the MBean proxy {0}, method {1} with value {2} ({3}).

Cause: An invalid attribute value was specified.

Action: Verify that the provided attribute value (specified either in the configuration or through a dynamic setting) is correct.
Level: 1

Type: ERROR

Impact: Management

BEA-141051: The operation failed with message: {0}.

Cause: Refer to the embedded exception information for more details as to the probable cause of this error.

Action: Take action based upon the details of the provided error message.
Level: 1

Type: ERROR

Impact: Management

BEA-141052: The auto deployment poller has started.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141053: The auto deployment poller has not started for the production server.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141062: The user does not have permission to perform {1} operation on MBean {0}. Method = {3}, attribute = {2}

Cause: No access control list (ACL) permissions are defined for the user to complete this operation.

Action: The system administrator must add ACL permissions in order for the user to perform this operation.
Level: 1

Type: ERROR

Impact: Management

BEA-141063: The user does not have permission to perform {1} operation on MBean {0}. Method: {2}.

Cause: The user has no defined access control list (ACL) to perform this MBean operation.

Action: The system administrator must define permissions in order for the user to perform this MBean operation.
Level: 1

Type: ERROR

Impact: Management

BEA-141071: The file distribution servlet failed to distribute the embedded LDAP initial replica data file because the file was not found at the configured location: {0}.

Cause: This is an internal error that should not occur during normal operation.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Management

BEA-141073: Migration task ({0}) - {1}

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141076: No module with URI ({1}) was found in ({0}).

Cause: The application is potentially misconfigured relative to this module.

Action: Verify that the application archive and its descriptors are correctly configured.
Level: 1

Type: ERROR

Impact: Management

BEA-141077: An error occurred during the parsing of descriptors for {0}. Exception {1} occurred.

Cause: Refer to the exception details for the exact cause of this parsing error.

Action: Take action based upon provided exception details to either correct the identified component or its descriptors.
Level: 1

Type: ERROR

Impact: Management

BEA-141078: A descriptor initialization error occurred for module {0} in EAR file {1}. Creation of the temporary file {2} failed.

Cause: The extraction of the EAR file failed due to an I/O error. See the logged for details.

Action: Ensure that the file referred to in the exception can be created, and there is no directory by the same name.
Level: 1

Type: ERROR

Impact: Management

BEA-141081: The file distribution servlet failed to distribute the embedded LDAP initial replica data file due to the following error: {0}.

Cause: Refer to the embedded exception information for more details as to the probable cause of this error.

Action: Take action based upon the provided exception details.
Level: 1

Type: INTERNAL_ERROR

Impact: Management

BEA-141086: An error occurred while setting a value for {0}.

Cause: The specified command line property provided an invalid value for attribute {0}.

Action: Verify that the specified command line property provides a valid attribute value.
Level: 1

Type: ERROR

Impact: Management

BEA-141087: Property: {0} is not a recognized MBean attribute or special property used for management. It is most likely being used by subsystems and will continue to work as expected if it is a supported option.

Cause: An unrecognized property has been specified on the start command.

Action: Eliminate the invalid properties from the start command.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141089: Starting the server based on the WebLogic Server 6.x configuration directory structure.

Cause: The startup directory does not contain the config.xml configuration file. The file was located in the config/domain directory.

Action: Start the server from the directory that contains the domain configuration file.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141102: Subject: {0} does not have access to perform {1} actions.

Cause: Either the named subject is not allowed to perform this action and is appropriately being denied this access, or the named subject should be allowed to perform this action and the role membership of the subject is not properly configured.

Action: Contact the system administrator to modify role definitions.
Level: 1

Type: ERROR

Impact: Management

BEA-141107: Version: {0}

Cause: This is normal system initialization processing.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141124: An invalid system property was specified while booting the server {0}.

Cause: The server might have been started using an invalid system property. For example, starting the server using java -D weblogic.Server will generate this exception.

Action: Correct the invalid system property.
Level: 1

Type: ERROR

Impact: Management

BEA-141126: The configuration file {0} is read-only.

Cause: This occurs when the write permissions on the file are not set to allow the user that booted the server to write to the config.xml file. Write access is often intentionally denied in production environments.

Action: In many cases, write access is intentionally denied. In such cases, this is just an informational message. If the file needs to be writable, change the permissions on the file or ask the system administrator to do so.
Level: 1

Type: WARNING

Impact: Management

BEA-141133: The Name attribute cannot be modified after the MBean {0} has been created.

Cause: The Name attribute is being modified by a setName operation.

Action: Specify the name of the MBean during creation.
Level: 1

Type: ERROR

Impact: Management

BEA-141145: An attempt was made to connect to the Administration Server without credentials.

Cause: The requirement to supply credentials on all requests was added in version 8.1 of the product. It is most likely that an old version of a utility is being used that is not properly supplying these credentials. It is also possible that this represents an attempt to compromise the server.

Action: Determine the source of the request. If it is a legitimate request, ensure that updated software is being used which properly supplies the credentials. It is also important to restrict access to the Administration Server. Refer to the WebLogic Server documentation to ensure that all of the proper security precautions have been taken.
Level: 1

Type: ERROR

Impact: Management

BEA-141146: An attempt was made to connect to the Administration Server by the user {0} and a password which does not match.

Cause: The requirement to supply credentials on all requests was added in version 8.1 of the product. In this case, the password is not valid for the specified user. This may be the result of supplying an improper user name and password when using the deployment utilities.

Action: Determine the source of the request. If it is a legitimate request, ensure that updated software which properly supplies the credentials is in use. It is also important to restrict access to the Administration Server. Refer to the WebLogic Server documentation to ensure that all of the proper security precautions have been taken.
Level: 1

Type: ERROR

Impact: Management

BEA-141147: An attempt was made to upload a file to the Administration Server by the unauthorized user {0}.

Cause: The requirement to supply credentials on all requests was added in version 8.1 of the product. In this case, the user specified is not configured with the authorization to upload files.

Action: To enable the user to upload files to the Administration Server, it is necessary that the user be added to the administrator or deployer role. Alternatively, it is possible to authorize a user specifically for "FileUpload". Consult the WebLogic Server documentation for instructions on how to do this.
Level: 1

Type: ERROR

Impact: Management

BEA-141148: An invalid attempt was made to download a {1} resource from the Administration Server by the unauthorized user {0}.

Cause: The requirement to supply credentials on all requests was added in version 8.1 of the product. In this case, the credentials of the user that is being used to boot the Managed Server are used to authorize the request. That user is not authorized to access files of the type {1}.

Action: Ensure that the proper credentials are being used to initiate the connection. In most cases, this involves ensuring that the credentials being used to boot the Managed Server are properly authorized on the Administration Server.
Level: 1

Type: ERROR

Impact: Management

BEA-141149: An invalid attempt was made to connect to the Administration Server with a salt of {0} and a signature of {1}, likely due to private key mismatch.

Cause: The requirement to supply credentials on all requests was added in version 8.1 of the product. In this case, the password is not valid for the specified user. This may be the result of supplying an improper user name and password when using the deployment utilities.

Action: Determine the source of the request and ensure that the Managed Server and the Administration Server share the same security credential. That credential is stored in the domain configuration and distributed at server startup. In this case, where the Managed Server is booted using a configuration that is different from that of the Administration Server, perhaps in Managed Server independence mode. Refer to the WebLogic Server documentation to ensure that all of the proper security precautions have been taken.
Level: 1

Type: ERROR

Impact: Management

BEA-141151: The Administration Server could not be reached at {0}.

Cause: The Administration Server is not available at the specified URL or the URL is not specified in the correct format, such as http://myhost:7001.

Action: Ensure that the Administration Server is running at the specified host and port. Check that the URL is specified in the correct format. The URL is specified by the protocol://host:port, for example http://myhost:7001.
Level: 1

Type: INTERNAL_ERROR

Impact: Management

BEA-141187: Java system properties are defined as follows: {0}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141190: The commit phase of the configuration update failed with an exception.

Cause: An exception occurred during the commit of the update.

Action: Retry the activate. Take action based upon the provided exception details.
Level: 1

Type: INTERNAL_ERROR

Impact: Management

BEA-141191: The prepare phase of the configuration update failed with an exception.

Cause: An exception occurred during the prepare of the update.

Action: Ensure that the update is valid. Take action based upon the provided exception details, make any required changes, change the changes, and retry the activate.
Level: 1

Type: WARNING

Impact: Management

BEA-141192: The read of the edit lock file failed with an exception.

Cause: An exception occurred during the read of the edit lock file.

Action: Take action based upon the provided exception details. Try to get the edit lock again.
Level: 1

Type: ERROR

Impact: Management

BEA-141193: The write of the edit lock file failed with an exception.

Cause: An exception occurred during the write of the edit lock file.

Action: Take action based upon the provided exception details. Try to get the edit lock again.
Level: 1

Type: ERROR

Impact: Management

BEA-141194: The registration of the configuration subsystem with the deployment subsystem failed with an exception.

Cause: An exception occurred during the registration of the configuration subsystem.

Action: Take action based upon the provided exception details. Restart the server.
Level: 1

Type: ERROR

Impact: Management

BEA-141196: The Managed Server could not update the configuration files during the registration with the deployment service. The update failed due to an exception.

Cause: An exception occurred during the update of configuration files.

Action: Take action based upon the provided exception details, make any required changes, and try to restart the Managed Server.
Level: 1

Type: ERROR

Impact: Management

BEA-141197: The deployment of {0} failed.

Cause: An exception occurred during a resource deployment.

Action: Take action based upon the provided exception details, make any required changes, and try to restart the Managed Server.
Level: 1

Type: WARNING

Impact: Management

BEA-141198: The undeployment of {0} failed.

Cause: An exception occurred during a resource undeployment.

Action: Take action based upon the provided exception details, make any required changes, and try to restart the Managed Server.
Level: 1

Type: WARNING

Impact: Management

BEA-141199: In the compatibility MBean server, the operation {1} on the MBean {0} modified the configuration without starting an edit session and activating the changes.

Cause: The impact information was incorrect for the MBean operation.

Action: Contact My Oracle Support as this is an internal coding error that should not occur.
Level: 1

Type: INTERNAL_ERROR

Impact: Management

BEA-141200: Detected a domain that was created from an earlier release of WebLogic Server. The domain will be upgraded to the current {0} release.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141201: Unable to modify the configuration using the compatibility MBean server, as other changes are pending. Activate the pending changes before modifying the configuration with the compatibility MBean server.

Cause: The configuration was not modified because pending changes were present.

Action: Activate the changes before using the compatibility server.
Level: 1

Type: ERROR

Impact: Management

BEA-141202: The addition of the bean {0} failed during the activate phase because of {1}

Cause: See the exception message for more information.

Action: Check the exception message for more detail.
Level: 1

Type: WARNING

Impact: Management

BEA-141203: The addition of the bean {0} failed during the activate phase because of {1}

Cause: See the exception message for more information.

Action: Check the exception message for more detail.
Level: 1

Type: WARNING

Impact: Management

BEA-141204: The addition of the bean {0} failed during the activate phase because of {1}

Cause: See the exception message for more information.

Action: Check the exception message for more detail.
Level: 1

Type: WARNING

Impact: Management

BEA-141205: The removal of the bean {0} failed during the activate phase because of {1}

Cause: See the exception message for more information.

Action: Check the exception message for more detail.
Level: 1

Type: WARNING

Impact: Management

BEA-141206: The removal of the bean {0} failed during the activate phase because of {1}

Cause: See the exception message for more information.

Action: Check the exception message for more detail.
Level: 1

Type: WARNING

Impact: Management

BEA-141207: The removal of the bean {0} failed during the activate phase because of {1}

Cause: See the exception message for more information.

Action: Check the exception message for more detail.
Level: 1

Type: WARNING

Impact: Management

BEA-141208: The modification of the property {0} failed during the activate phase because of {1}

Cause: See the exception message for more information.

Action: Check the exception message for more detail.
Level: 1

Type: WARNING

Impact: Management

BEA-141209: The modification of the property {0} failed during the activate phase because of {1}

Cause: See the exception message for more information.

Action: Check the exception message for more detail.
Level: 1

Type: WARNING

Impact: Management

BEA-141210: The modification of the property {0} failed during the activate phase because of {1}

Cause: See the exception message for more information.

Action: Check the exception message for more detail.
Level: 1

Type: WARNING

Impact: Management

BEA-141211: An attempt to initialize the property {0} failed because of {1}

Cause: See the exception message for more information on the cause of this error.

Action: The exception message may have more information about the action to take.
Level: 1

Type: ERROR

Impact: Management

BEA-141212: An attempt to initialize the property {0} failed because of {1}

Cause: See the exception message for more information on the cause of this error.

Action: The exception message may have more information about the action to take.
Level: 1

Type: ERROR

Impact: Management

BEA-141213: An attempt to initialize the property {0} failed because of {1}

Cause: See the exception message for more information on the cause of this error.

Action: The exception message may have more information about the action to take.
Level: 1

Type: ERROR

Impact: Management

BEA-141214: The add of the bean {0} failed. The encountered exception was {1}

Cause: See the exception message for more information on the cause of this error.

Action: The exception message may have more information about the action to take.
Level: 1

Type: ERROR

Impact: Management

BEA-141215: The add of the bean {0} failed. The encountered exception was {1}

Cause: See the exception message for more information on the cause of this error.

Action: The exception message may have more information about the action to take.
Level: 1

Type: ERROR

Impact: Management

BEA-141216: The add of the bean {0} failed. The encountered exception was {1}

Cause: See the exception message for more information on the cause of this error.

Action: The exception message may have more information about the action to take.
Level: 1

Type: ERROR

Impact: Management

BEA-141217: The removal of the bean {0} failed. The encountered exception was {1}

Cause: See the exception message for more information on the cause of this error.

Action: The exception message may have more information about the action to take.
Level: 1

Type: ERROR

Impact: Management

BEA-141218: The removal of the bean {0} failed. The encountered exception was {1}

Cause: See the exception message for more information on the cause of this error.

Action: The exception message may have more information about the action to take.
Level: 1

Type: ERROR

Impact: Management

BEA-141219: The removal of the bean {0} failed. The encountered exception was {1}

Cause: See the exception message for more information on the cause of this error.

Action: The exception message may have more information about the action to take.
Level: 1

Type: ERROR

Impact: Management

BEA-141220: A required class was not found while upgrading the domain. This could be possible if the security provider JAR files were not upgraded to conform with WebLogic Server version 9.0. Upgrade these providers using java weblogic.Upgrade -type securityproviders.

Cause: The security provider JAR files were not upgraded to conform with new WebLogic Server 9.0 classes.

Action: Run the upgrade tool to upgrade the provider.
Level: 1

Type: INTERNAL_ERROR

Impact: Management

BEA-141221: An error occurred while performing an undo of unactivated changes in the compatibility MBean server: {0}.

Cause: See the exception message for more information.

Action: Check the exception message for more detail.
Level: 1

Type: ERROR

Impact: Management

BEA-141223: The server name {0} specified with -Dweblogic.Name does not exist. The configuration includes the following servers {1}.

Cause: The -Dweblogic.Name command line property specifies a server that does not exist in the configuration.

Action: Check the configuration for the list of configured servers.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141224: The Administration Server is not reachable.

Cause: This could be a network issue.

Action: Check the status of the Administration Server.
Level: 1

Type: WARNING

Impact: Management

BEA-141225: The delete of pending directory file {0} failed.

Cause: An error occurred while deleting the file.

Action: Ensure that no processes have the file open for write.
Level: 1

Type: ERROR

Impact: Management

BEA-141226: An invalid deployment service prepare callback with ID {0} was received.

Cause: This indicates an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: Management

BEA-141227: Making a backup copy of the configuration at {0}.

Cause: This happens during certain server lifecycle transitions and during configuration changes.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141228: An attempt to back up the configuration to {0} failed with {1}.

Cause: See the message text for the exception message.

Action: Check the exception information included in the message text.
Level: 1

Type: ERROR

Impact: Management

BEA-141229: The upgrade process has been canceled by the user. The server process will not be started.

Cause: The server startup cannot proceed without upgrading the domain.

Action: Upgrade the domain, and then start the server.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141230: Could not locate the descriptor file for System Resource: {0}.

Cause: The descriptor file could not be located in the specified path.

Action: Ensure that the descriptor file is in the appropriate location.
Level: 1

Type: WARNING

Impact: Management

BEA-141231: Could not register the JSR object: {0}.

Cause: There are many possible causes for this warning.

Action: Look at the stack trace and take appropriate action.
Level: 1

Type: WARNING

Impact: Management

BEA-141232: Could not decrypt the {1} attribute value of {2} from the file {0}. The edit session has been canceled. The decryption failed with the exception {3}.

Cause: An invalid encrypted value was found in the edit lock file.

Action: Start a new edit session.
Level: 1

Type: ERROR

Impact: Management

BEA-141233: Could not decrypt the edit lock file {0}. The edit session has been canceled. The decryption failed with the exception {1}.

Cause: An exception occurred when decrypting the edit lock file.

Action: Start a new edit session.
Level: 1

Type: ERROR

Impact: Management

BEA-141234: A rollback of a dynamic change failed. The message for the failure is "{0}". The cause of the exception is "{1}".

Cause: See the message body for the cause.

Action: Look at the possible causes of this error. The cause may give some indication of the possible actions to take.
Level: 1

Type: WARNING

Impact: Management

BEA-141237: Extraneous text found in the config.xml file: {0}.

Cause: This is generally caused by mistakes in hand-edited config.xml files. The config.xml file is a valid XML document, however, the extraneous text is not related to any MBean attributes.

Action: Review the config.xml file for mistakes, such as extra delimeters near the text listed in the error message.
Level: 1

Type: WARNING

Impact: Management

BEA-141238: A non-dynamic change has been made which affects the server {0}. This server must be rebooted in order to consume this change.

Cause: This happens when one or more of the changes made to the configuration affect non-dynamic settings. When this occurs, the affected Managed Servers are determined, and those servers are not updated when the change is activated. In order to consume the change, these servers must be rebooted.

Action: Reboot the named server.
Level: 1

Type: WARNING

Impact: Management

BEA-141239: The non-dynamic attribute {1} on {0} has been changed. This may require redeploying or rebooting configured entities.

Cause: This happens when one or more of the changes made to the configuration affect non-dynamic settings.

Action: The required action, if any, will be indicated in a later log message.
Level: 1

Type: WARNING

Impact: Management

BEA-141240: Found a version {0} config.cml file, but expected a version 9 or higher config.xml file. This could happen if an attempt to boot was made from the config directory rather than the domain root.

Cause: This could happen if an attempt was made to boot from the config directory rather than the domain root. Otherwise, the configuration could be corrupted.

Action: Ensure that the config.xml file is not corrupted and that the boot is attempted from the domain root.
Level: 1

Type: ERROR

Impact: Management

BEA-141241: Found a version {0} config.xml file, but expected a pre-version 9 config.xml file. This could happen if an attempt was made to boot from the config directory rather than the domain root.

Cause: This could happen if a 9.x config.xml file was put in the top level, rather than in the config directory.

Action: Ensure that the config.xml file is in the correct location in the domain.
Level: 1

Type: ERROR

Impact: Management

BEA-141242: Invalid configuration version found at {1} version = {0}.

Cause: WebLogic Server found a config.xml file with a version that does not match any known version of the product.

Action: Ensure that the version string in the config.xml file is valid.
Level: 1

Type: ERROR

Impact: Management

BEA-141243: The property {0} in element {1} has been deprecated in version {2} - {3}.

Cause: The config.xml file contained elements that have been deprecated.

Action: Replace or remove the deprecated configuration artifacts.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141244: Schema validation errors while parsing {0} - {1}.

Cause: The WebLogic Server configuration files are defined by a schema. When parsing these files, they are validated against the schema. This warning indicates that there were problems found during validation. The problems may or may not be fatal, depending on the setting of the system property weblogic.configuration.schemaValidationEnabled.

Action: See the error details for more information on the validation problem.
Level: 1

Type: ERROR

Impact: Management

BEA-141245: Schema validation error in {0}. See the log for details. Schema validation can be disabled by starting the server with the command line option: {1}.

Cause: The WebLogic Server configuration files are defined by a schema. When parsing these files, they are validated against the schema. This warning indicates that there were problems found during validation. The problems may or may not be fatal, depending on the setting of the system property weblogic.configuration.schemaValidationEnabled.

Action: See the error details for more information on the validation problem.
Level: 1

Type: ERROR

Impact: Management

BEA-141246: The configuration directory {0} does not exist.

Cause: The server was booted from a directory that does not contain a configuration directory.

Action: Ensure that the server is booted from a valid domain directory.
Level: 1

Type: ERROR

Impact: Management

BEA-141247: The configuration directory {0} does not exist, and the Administration Server is not available.

Cause: The configuration directory is missing and the Administration Server is not available to download a copy. In this case, the Managed Server cannot boot.

Action: Ensure that either the server is booted from a valid domain directory or that the Administration Server is available.
Level: 1

Type: ERROR

Impact: Management

BEA-141248: The configuration directory {0} is missing the file {1}.

Cause: The server was booted from a directory that does not contain a valid domain configuration.

Action: Ensure that the server is booted from a valid domain directory.
Level: 1

Type: ERROR

Impact: Management

BEA-141249: The configuration directory {0} is missing the file {1}, and the Administration Server is not available to download it.

Cause: The server was booted from a directory that does not contain a valid configuration, and the Administration Server is unavailable to download the current configuration files.

Action: Ensure that either the server is booted from a valid domain directory or that the Administration Server is available.
Level: 1

Type: ERROR

Impact: Management

BEA-141251: The attribute {1} from the element {0} was introduced in version 9.0.0.0 or later and is not valid in a pre-9.0 config.xml file.

Cause: An attribute that was introduced in release 9.0 or later was found in a pre-9.0 config.xml file.

Action: Verify that the upgrade process correctly handles the named elements by reviewing the upgraded configuration files.
Level: 1

Type: WARNING

Impact: Management

BEA-141252: The domain version {0} is greater than the release version {1} of this server.

Cause: The DomainVersion in the configuration used by the Administration Server is not compatible with the release version of this Managed Server.

Action: Update the WebLogic Server installation for this server.
Level: 1

Type: ERROR

Impact: Management

BEA-141253: An error occurred while loading the configuration translator {0} : {1}.

Cause: The message includes the specific cause.

Action: Repair or remove the configuration translator.
Level: 1

Type: WARNING

Impact: Management

BEA-141254: Generating new domain directory in {0}.

Cause: There was no domain directory at the specified location. Either a command line option or user input specified creation of the domain, so generation of the domain is commencing.

Action: No action is required. The domain directory will be generated, and the server will continue to boot normally.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141255: Domain generation completed in {0} milliseconds.

Cause: A new domain has been generated.

Action: No action is required. The server will continue to boot normally.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141256: A RuntimeException occurred while adding or removing a configuration element: {0}.

Cause: See the exception text for details.

Action: The message includes information on the root cause. Review this message to determine the appropriate action.
Level: 1

Type: ERROR

Impact: Management

BEA-141257: An exception occurred while translating a configuration file: {0}.

Cause: See the exception text for details.

Action: The message includes information on the root cause. Review this message to determine the appropriate action.
Level: 1

Type: ERROR

Impact: Management

BEA-141258: An exception occurred while constructing an ObjectName: {0}.

Cause: See the exception text for details.

Action: The message includes information on the root cause. Review this message to determine the appropriate action.
Level: 1

Type: ERROR

Impact: Management

BEA-141259: An exception occurred while sending a Notification: {0}.

Cause: See the exception text for details.

Action: The message includes information on the root cause. Review this message to determine the appropriate action.
Level: 1

Type: ERROR

Impact: Management

BEA-141260: An exception occurred while removing a Notification: {0}.

Cause: See the exception text for details.

Action: The message includes information on the root cause. Review this message to determine the appropriate action.
Level: 1

Type: ERROR

Impact: Management

BEA-141261: An exception occurred while unregistering a Notification: {0}.

Cause: See the exception text for details.

Action: The message includes information on the root cause. Review this message to determine the appropriate action.
Level: 1

Type: ERROR

Impact: Management

BEA-141262: An exception occurred while adding a Filter: {0}.

Cause: See the exception text for details.

Action: The message includes information on the root cause. Review this message to determine the appropriate action.
Level: 1

Type: ERROR

Impact: Management

BEA-141263: An exception occurred in an MBean customizer: {0}.

Cause: See the exception text for details.

Action: The message includes information on the root cause. Review this message to determine the appropriate action.
Level: 1

Type: ERROR

Impact: Management

BEA-141264: An exception occurred in an MBeanProxy: {0}.

Cause: See the exception text for details.

Action: The message includes information on the root cause. Review this message to determine the appropriate action.
Level: 1

Type: ERROR

Impact: Management

BEA-141265: Could not get the configuration lock used to serialize access to the configuration files.

Cause: The lock could not be obtained before the specified timeout period had elasped.

Action: Verify the configuration files and ensure that no server has hung, thereby not releasing the lock.
Level: 1

Type: ERROR

Impact: Management

BEA-141266: Parsing failure in {0}: {1}.

Cause: This error occurs when the configuration file has invalid XML syntax or other errors.

Action: Validate the contents of the configuration file.
Level: 1

Type: ERROR

Impact: Management

BEA-141267: Parsing failure in {0} on line {1}: {2}.

Cause: This error occurs when the configuration file has invalid XML syntax or other errors.

Action: Validate the contents of the configuration file.
Level: 1

Type: ERROR

Impact: Management

BEA-141268: Parsing failure in {0} on line {1}, column {2}: {3}.

Cause: This error occurs when the configuration file has invalid XML syntax or other errors.

Action: Validate the contents of the configuration file.
Level: 1

Type: ERROR

Impact: Management

BEA-141269: The temporary bean tree {0} was allocated for an undo, get, or activate operation, but has not been garbage collected.

Cause: The temporary bean tree has not been garbage collected.

Action: Repeat the specified operation and determine if memory usage in the server is increasing.
Level: 1

Type: WARNING

Impact: Management

BEA-141270: Could not get the configuration lock used to serialize access to configuration files. Retrying for another {0} seconds.

Cause: Another server was reading or writing to the configuration files, and the lock could not be obtained before the specified timeout period had elasped.

Action: No action is required. If the configuration subsystem fails to get the lock, and the number of retries is exhausted, a different message with error severity will be displayed.
Level: 1

Type: WARNING

Impact: Management

BEA-141271: An IOException occurred while recording setAttribute {1} on MBean {0}. Exception: {2}.

Cause: Refer to the embedded exception information for more details as to the probable cause of this error.

Action: Take action based upon the provided exception details.
Level: 1

Type: ERROR

Impact: Management

BEA-141272: An IOException occurred while recording invoke {1} on MBean {0}. Exception: {2}.

Cause: Refer to the embedded exception information for more details as to the probable cause of this error.

Action: Take action based upon the provided exception details.
Level: 1

Type: ERROR

Impact: Management

BEA-141273: An upgrade framework class was not found. Exception: {0}. The configuration and upgrade framework component may not have been installed.

Cause: The configuration and upgrade framwork component may not have been installed.

Action: Install the Configuration Wizard and pgrade framework component by running the installer again.
Level: 1

Type: ERROR

Impact: Management

BEA-141274: Production mode has been specified at the command line using the the weblogic.ProductionModeEnabled system property. This system property overrides the development mode setting contained in the config.xml file. However, the Administration Console and WLST show the attribute values and defaults that correspond to the development mode specified in the config.xml file.

Cause: The command line overrides are not persisted to the config.xml file.

Action: If the Administration Console or WLST should display production mode defaults for attributes, then enable production mode in the Administration Console or WLST and activate the changes.
Level: 1

Type: WARNING

Impact: Management

BEA-141275: Development mode has been specified at the command line by setting the weblogic.ProductionModeEnabled system property to false. This system property overrides the production mode setting contained in the config.xml file. However, the Administration Console and WLST show the attribute values and defaults that correspond to the production mode specified in the config.xml file.

Cause: The command line overrides are not persisted to the config.xml file.

Action: If the Administration Console or WLST should display development mode defaults for attributes, then enable development mode in the Administration Console or WLST and activate the changes.
Level: 1

Type: WARNING

Impact: Management

BEA-141276: An exception occurred while obtaining the class for interface {0}. The exception is: {1}

Cause: A resource or classloader issue caused the class lookup to fail.

Action: See the underlying exception to troubleshoot further.
Level: 1

Type: WARNING

Impact: Management

BEA-141277: The JMX MBean PlatformMBeanServerUsed attribute is true, but the Platform MBeanServer was created without the hooks for the WebLogic Server security infrastructure. The Platform MBeanServer will not be used and Platform MBeans will not be available using the WebLogic Server Runtime or Domain Runtime MBeanServers. This can occur if Platform MBeanServer system properties or JVM options (-Dcom.sun.management.jmxremote or JRockit -XManagement) were defined. To allow the Platform MBeanServer to be used, either remove the system properties and JVM options or start WebLogic Server with the following system property: -Djavax.management.builder.initial=weblogic.management.jmx.mbeanserver.WLSMBeanServerBuilder To eliminate this log error if Platform MBeans do not need to be available when using WebLogic Server, set the PlatformMBeanUsed attribute in the JMXMBean to false.

Cause: A system property was specified that caused the Platform MBeanServer to be created before the WebLogic Server Runtime MBeanServer.

Action: Remove the system properties or start WebLogic Server with the following system property: -Djavax.management.builder.initial=weblogic.management.jmx.mbeanserver.WLSMBeanServerBuilder.
Level: 1

Type: WARNING

Impact: Management

BEA-141278: Java entropy configuration is: {0}.

Cause: This message is informational and is printed every time WebLogic Server starts.

Action: Change your jave entropy configuration, if needed.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141279: Detected BLOCKING java entropy configuration. This is the most secure setting, but may cause performance issues on machines with few sources of entropy.

Cause: This message is informational and is printed every time WebLogic Server starts.

Action: Change your jave entropy configuration, if needed.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141280: Detected NON-BLOCKING java entropy configuration. This setting will provide the best performance on machines with few sources of entropy, but is less secure than a blocking entropy configuration.

Cause: This message is informational and is printed every time WebLogic Server starts.

Action: Change your jave entropy configuration, if needed.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141281: A ForeignJNDIProvider named {0} has two child ForeignJNDILinks named {1} and {2}, which both have the same LocalJNDIName {3}. This duplication of LocalJNDIName is invalid.

Cause: Two links cannot share the same LocalJNDIName because it would be unclear as to which remote JNDI name to link to.

Action: Change the LocalJNDIName of one of the ForeignJNDILinks.
Level: 1

Type: ERROR

Impact: Management

BEA-141282: Server name {0} not found in domain {1}.

Cause: A managed server is started with -Dweblogic.Name with a value that is not configured in the domain.

Action: Specify the correct value of the param -Dweblogic.Name.
Level: 1

Type: ERROR

Impact: Management

BEA-141283: Server name could not be determined.

Cause: Either the name is not specified or the specified name does not exist in the config.xml file.

Action: Specify the correct value of the -Dweblogic.Name parameter.
Level: 1

Type: ERROR

Impact: Management

BEA-141284: A deprecated MBean for {0} has been removed from the current version of WebLogic Server but still exists in an application configuration file.

Cause: A deprecated MBean for {0} has been removed from the current version of WebLogic Server but still exists in an application configuration file.

Action: Update the configuration file to remove the deprecated MBean.
Level: 1

Type: INTERNAL_ERROR

Impact: Management

BEA-141285: The network access point property {0} was ignored because the specified network access point name was not found.

Cause: The specified network access point does not exist in the configuration.

Action: Modify the system property, and specify a valid network access point name.
Level: 1

Type: WARNING

Impact: Management

BEA-141286: The creation of the dynamic server failed with an exception.

Cause: An exception occurred during the creation of the dynamic server.

Action: Take action based upon the provided exception details, make any required changes, and retry the operation.
Level: 1

Type: WARNING

Impact: Management

BEA-141287: No matching machines were found based on the MachineNameMatchPrefix property. No machine has been calculated for servers from dynamic servers {0}.

Cause: The MachineNameMatchPrefix did not match any of the existing machines in the domain.

Action: Set the MachineNameMatchPrefix property so it matches the machine names in the domain.
Level: 1

Type: WARNING

Impact: Management

BEA-141288: Unable to obtain file lock but will retry.

Cause: This is an informational message only.

Action: If WebLogic Server fails to start because it was unable to obtain the file lock, then the lock files need to be removed manually before restarting WebLogic Server.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141289: Upgrade of 8.1 or prior domains is no longer supported. Convert the {1} from version {0} to 10.x format using weblogic.Upgrade.

Cause: WebLogic Server found a config.xml file with a version that is no longer supported.

Action: Upgrade the config.xml file to a newer version using weblogic.Upgrade from a 10.3 or lower version of the product.
Level: 1

Type: ERROR

Impact: Management

BEA-141290: Configuration plug-in not found for component type "{0}" in location "{1}"

Cause: The plug-in JAR file was not found.

Action: Verify the installation to ensure that the plug-in was installed correctly.
Level: 1

Type: ERROR

Impact: Management

BEA-141291: A system component for component type "{0}" was not defined in config.xml. The file "{1}" will not be distributed to the external server.

Cause: The system component is not defined in config.xml

Action: Define the corresponding system component in config.xml.
Level: 1

Type: WARNING

Impact: Management

BEA-141292: A machine was not specified in the system component "{0}" in config.xml. The file "{1}" will not be distributed to the external server.

Cause: The machine for the system component is not defined in config.xml

Action: Define the corresponding machine in the system component in config.xml.
Level: 1

Type: WARNING

Impact: Management

BEA-141293: Bad CAM replication exclusive file {0} : {1}.

Cause: See the error message for details.

Action: Correct the error in the CAM replication exclusive file.
Level: 1

Type: WARNING

Impact: Management

BEA-141294: Found invalid entries in CAM replication exclusive file {0}: {1}.

Cause: There are invalid entries in the file.

Action: Correct the invalid entries in the file.
Level: 1

Type: WARNING

Impact: Management

BEA-141295: Unable to contact Node Manager on "{1}". Activation for system component "{0}" is deferred until "{1}" becomes available.

Cause: Contact with Node Manager on "{1}" could not be made.

Action: No action is required.
Level: 1

Type: WARNING

Impact: Management

BEA-141296: Unable to contact Node Manager on "{1}". Activation for system component "{0}" is deferred until "{1}" becomes available.

Cause: Contact with Node Manager on "{1}" could not be made.

Action: No action is required.
Level: 1

Type: WARNING

Impact: Management

BEA-141297: Could not get the server file lock. Ensure that another server is not running in the same directory. Retrying for another {0} seconds.

Cause: Another server is running and still has the server lock.

Action: Check to see if another server is running.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141298: Could not register with the Administration Server: {0}

Cause: A network connection failed or an IO exception occurred.

Action: Check the underlying exception and determine why the managed server could not connect to the Administration Server.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-149000: Unable to create DeployerRuntimeMBean.

Cause: This may occur if an error at the JMX level exists.

Action: Report this problem to My Oracle Support.
Level: 1

Type: INTERNAL_ERROR

Impact: Deployer

BEA-149001: No application named "{0}" exists for operation {1}

Cause: The application name was likely misspelled.

Action: Verify that the application is correctly named.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149002: The source file was not provided for activation of application: "{0}".

Cause: Source files do not exist for the application to be deployed.

Action: Make source files available for the application to be deployed in the said path.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149003: Unable to access application source information in "{0}" for application "{1}". The specific error is: {2}.

Cause: Source files for the application to be deployed are not accessible.

Action: Ensure that no other process is using the source file(s).
Level: 1

Type: WARNING

Impact: Deployer

BEA-149004: Failures were detected while initiating {1} task for application "{0}".

Cause: Task creation can fail for many reasons.

Action: Check the error message and take appropriate action.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149007: New source location, "{0}", cannot be deployed to the configured application, "{1}". The application source is at "{2}". Changing the source location is not allowed for a previously attempted deployment. Try deploying without specifying the source.

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

Action: Deploy the application with the same source location that was configured in the application.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149011: Some of the targets in the deployment request are not configured in this domain. The named targets are: "{0}".

Cause: This error occurs when a deployment request is made to a target that is not configured.

Action: Ensure that the target list in the request is correct.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149013: Application "{0}" does not define the module, "{1}". {2} are the known valid module(s) for this application.

Cause: Incorrect deployment information was provided in the activate request.

Action: Ensure that the module information in the request is accurate. If adding modules, ensure that the source file is specified again so that it is reloaded and any new modules are deployed.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149014: Target "{0}" is not defined.

Cause: Incorrect deployment information was provided in the activate request.

Action: Ensure that the target information in the request is accurate.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149015: Unable to add "{0}" to component "{1}".

Cause: The component is already targeted to the server, cluster, or virtual host.

Action: Check the target list.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149021: Rejecting {2} request for application "{1}". The specified ID, {0}, is already being used.

Cause: A {1} request included an ID provided by a user that is already assigned to another task.

Action: Choose a different ID or allow the system to allocate an ID for the request.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149025: An invalid attempt was made to target a non-Web application component, "{1}", in application "{0}" to a virtual host, "{2}".

Cause: An invalid attempt was made to target a non-Web application to virtual hosts.

Action: Correct the target list.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149026: {2} application {0} on {1}.

Cause: This is an informational message about the task description.

Action: This is an informational message about the task description.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149027: Unable to activate the application "{1}" from source "{0}". Reason: {2}

Cause: The application was improperly defined.

Action: Define the application properly.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149028: An invalid path, "{1}", was specified for the application "{0}".

Cause: The configured path for this application does not exist.

Action: Provide the application files in the specified location.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149031: The staging mode of "{0}" is invalid. The legal values are "stage" or "nostage".

Cause: An invalid staging mode has been specified.

Action: Specify a valid staging mode for the deployment request.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149032: An attempt to restart a task has been rejected. The task has already been started.

Cause: This error results if start is called on a task that has already been started.

Action: Do not call start on a task that has already been started.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149033: {2} application {0} on {1}.

Cause: An application-level deployment notification has been reported.

Action: No action is required. This is an informational log message.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149034: An exception occurred for task {0}: {1}.

Cause: An error occurred while reporting the application status.

Action: The error may be due to server instability. Check the health of the server.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149035: Module {0} reported error: {1}.

Cause: The deployment request failed.

Action: Check the exception log and take appropriate action.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149038: Initiating task for {1} : {0}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149040: An attempt to change the staging mode for the application "{0}" has been rejected.

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

Action: The staging mode cannot be changed once it is set. Try deploying again without changing the staging mode.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149043: The staging mode cannot be changed for an application that has already been configured. The staging mode change has been rejected for application "{0}" from {1} to {2}.

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

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

Type: ERROR

Impact: Deployer

BEA-149045: An attempt to add cluster target "{0}" was rejected, since cluster member "{1}" is also targeted by module "{2}". Targeting to a cluster member results in different behaviors than targeting to the entire cluster.

Cause: A cluster member is already in the target list of the module.

Action: Remove the cluster member from the target list, or re-target the cluster member rather than the cluster itself.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149048: An attempt to add server target "{1}" to module "{2}" has been rejected. This is because its parent cluster, "{0}", is also targeted by the module.

Cause: The module is already targeted to a cluster that contains the server.

Action: Remove the cluster from the target list or remove the cluster member from the target list.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149054: An attempt to add a virtual host target "{0}" to a non-Web application module "{1}" has been rejected.

Cause: An EJB or connector was attempting to target a virtual host.

Action: Remove the host from target list.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149055: Adding server {1} of cluster {0} as a target for module {3}. This module also includes server {2} that belongs to this cluster as one of its additional targets. Having multiple individual servers of a cluster as targets instead of having the entire cluster as the target can result in non-optimal load balancing and scalability. Therefore, this is not usually recommended.

Cause: The module is already targeted to a different cluster member.

Action: Target the entire cluster to the module.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149058: Distribute can only have stage as its staging mode. Application "{0}" has {1} as its staging mode.

Cause: This is an unexpected error.

Action: Specify a valid staging name.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149059: Module {1} of application {0} is transitioning from {2} to {3} on server {4}.

Cause: A module is being deployed.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149060: Module {1} of application {0} successfully transitioned from {2} to {3} on server {4}.

Cause: A module is being deployed.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149061: Module {1} of application {0} failed to transition from {2} to {3} on server {4}.

Cause: An error was encountered during a module deployment.

Action: Details of the specific failure are documented in the associated log entries. Take appropriate action.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149062: The task containing ID {0} cannot be canceled, since it has already completed execution.

Cause: An attempt has been made to cancel a deployment task that has completed execution.

Action: Do not attempt this operation on a completed task.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149066: Unable to deploy application "{0}", because module "{1}" does not provide a valid URI.

Cause: The application is incorrectly configured.

Action: Provide a URI for the module, or remove the application from the configuration.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149068: This is an unexpected exception.

Cause: This is an internal error.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149069: Deploying {0} using a deprecated protocol.

Cause: The application is configured with TwoPhase=false or is not a recognized type of application. For example, an application that is not an EAR file (no application.xml) but has multiple modules will not be deployed with the two-phase protocol.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149073: The application "{0}" has no configured modules.

Cause: The application is improperly configured.

Action: The application will be marked as undeployable. After resolving configuration issues with the application, the administrator can retry the deployment.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149074: Successfully completed deployment task: {0}.

Cause: A deployment operation was requested.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149078: Stack trace for message {0}

Cause: A deployment failure occurred.

Action: No action is required.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149080: A partial update of an archived application is not allowed. Application "{0}" cannot be redeployed.

Cause: There was an attempt to partially redeploy an archived application.

Action: Try deploying the entire application.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149081: Cannot {2} application, "{0}", with version "{1}". The application was previously deployed without a version.

Cause: An attempt was made to {2} a versioned application when it was previously deployed without a version.

Action: Try {2} without a version.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149082: Cannot {2} application "{0}" without a version. The application was previously deployed with version "{1}".

Cause: An attempt was made to {2} an application without a version when it was previously deployed with a version.

Action: Try {2} with a version.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149083: An attempt was made to activate the application "{0}" when stop was in progress.

Cause: An attempt was made to activate the application "{0}" when stop was in progress.

Action: Try to activate the application "{0}" again after the stop is done. If it is a graceful stop, stop the application forcefully to end the graceful stop immediately.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149085: No application version was specified for application "{0}". The {2} operation will be performed against the currently active version "{1}".

Cause: No application version was specified for the operation.

Action: Verify that the currently active version is the desired version for the operation. If not, perform the operation again with the -app_version operation to specify a particular version.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149086: The application {0} is being retired gracefully.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149087: The application {0} will be retired after {1} seconds.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149088: The retirement for application {0}, which was scheduled to happen after {1} seconds, is canceled.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149089: An attempt was made to activate the application "{0}" when retirement was in progress.

Cause: An attempt was made to activate the application "{0}" when retirement was in progress.

Action: Try to activate the application "{0}" again after the retirement is done. If it is a graceful retirement, undeploy the application to end the graceful retirement immediately.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149091: An attempt was made to deploy application "{0}" with specified archive version "{1}". However, the application archive, as specified in the source, has version "{2}".

Cause: This error occurs when an attempt is made to specify a version that is different from the manifest version of the application archive in the source location.

Action: Perform the deployment again without specifying the version, or specify version "{2}" instead of "{1}".
Level: 1

Type: ERROR

Impact: Deployer

BEA-149092: The source is not specified for the deployment operation of application "{0}", and the expected version is "{1}". However, the application archive at the source location for a previous deployment of version "{1}" now has version "{2}".

Cause: The source is not specified for the deployment operation of application "{0}", and the expected version is either explicitly specified or the currently active version. However, the application archive at the previously configured source location of the expected version has a different manifest version.

Action: Perform deployment again specifying either the source location or version "{2}".
Level: 1

Type: ERROR

Impact: Deployer

BEA-149093: No version specified for the versioned application named "{0}" for operation {1}, and no active version is available.

Cause: The version was not specified for the operation when no currently active version was available.

Action: Specify the version of the application for the operation.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149094: New version "{1}" of application "{0}" cannot be deployed to the source location, "{2}". The source location is the same as the nostage source location of a previously deployed application version "{3}".

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

Action: Deploy the new application version with a different source location. Also ensure that the old application source is still available at the old nostage source location.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149095: The application {0} is being retired now.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149096: Operation {1} is deprecated and cannot be applied to versioned application "{0}". Use operation {2} instead.

Cause: An attempt was made to perform the deprecated operation {1} on a versioned application. Use operation {2} instead.

Action: Use operation {2} instead.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149097: The retirement for application "{0}" failed.

Cause: This may happen due to a problem in accessing the persistent store or an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149098: An attempt was made to gracefully undeploy the application "{0}" when retirement was in progress.

Cause: An attempt was made to gracefully undeploy the application "{0}" when retirement was in progress.

Action: To stop the graceful retirement, force the application to undeploy.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149099: Unexpected errors occurred while sending deployment event {1} on behalf of application "{0}".

Cause: Deployment event listeners that are registered to receive a deployment event generated unexpected exceptions when processing the deployment event {1} on behalf of application "{0}".

Action: Report this problem to My Oracle Support.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149100: Unexpected errors occurred while sending a vetoable deployment event on behalf of application "{0}".

Cause: Deployment event listeners registered to receive a vetoable deployment event generated unexpected exceptions when processing the deployment event {1} on behalf of application "{0}".

Action: Report this problem to My Oracle Support.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149101: Application "{0}" is not deployed on target "{1}". Therefore, it cannot be undeployed or removed. The requested operation {2} is valid only on the deployed targets of the application.

Cause: Incorrect target information was provided in the {2} operation request.

Action: Ensure that the target information in the request is accurate.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149102: Production redeployment is not supported for application "{0}", which is of module type {1}. Production redeployment is supported for the following module types only: {2}. If not attempting to perform production redeployment, try deploying without a version.

Cause: Attempt was made to perform production redeployment for an unsupported module type.

Action: Ensure that the module type is supported before performing production redeployment. Or, try deploying again without a version.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149103: An exception occurred while executing task {0} for application "{1}": {2}.

Cause: An exception occurred while executing the deployment task for the application.

Action: If it is an application error, correct it if possible. If it is a system error, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149104: Update request for "{0}" does not specify any descriptors to be updated

Cause: The deployment plan does not include any module overrides.

Action: Ensure that the deployment plan is properly constructed.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149105: An attempt was made to deploy a library located at "{2}" with name "{0}", which is different from the one specified in the manifest of the library: "{1}".

Cause: This error occurs when an attempt is made to specify a name that is different from the one in the manifest of the library in the source location.

Action: Perform deployment again without specifying the name of the library.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149106: An attempt was made to deploy a library located at "{0}" without specifying a name, and the library does not have "Extension-Name" specified in its manifest.

Cause: This error occurs when an attempt is made to deploy a library without specifying a name, and the library module does not have "Extension-Name" specified in its manifest.

Action: Perform deployment again specifying the name of the library either during deployment or in the manifest of the library, using the "Extension-Name" attribute.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149107: An attempt was made to deploy library "{0}" with specified specification version "{1}" and implementation version "{2}". However, the library manifest has specification version "{3}" and implementation version "{4}".

Cause: This error occurs when an attempt is made to specify a version that is different from the manifest version of the library.

Action: Perform deployment again without specifying the version or after specifying the same version as specified in the manifest.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149108: Failures were detected while initiating {0} task.

Cause: Task creation can fail for many reasons.

Action: Check the error message and take appropriate action.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149110: An exception occurred while processing the completion of the task {0}, {1}. The active application version state may not have been updated.

Cause: This is an internal error.

Action: Report this problem to My Oracle Support.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149111: Application "{0}" is non-versioned, and an attempt was made to redeploy application "{0}" with the source. Redeploying with the source is only allowed when redeploying a new version of a versioned application. Try redeploying again without specifying the source.

Cause: An attempt was made to redeploy with the source specified for a non-versioned application "{0}". Redeploy again without specifying the source.

Action: Try redeploying again without specifying the source.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149112: Application "{0}" is already deployed, and the attempt was made to redeploy application "{0}" again with source. Redeploying with the source is only allowed when redeploying a new version of the application. Try redeploying again without specifying the source or with a new version.

Cause: An attempt was made to redeploy with the source specified for application "{0}", but application "{0}" was already deployed. Redeploy again without specifying the source or with a new version.

Action: Try redeploying again without specifying the source or redeploy with a new version.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149113: Cannot deploy or redeploy application "{0}" because the maximum number of application versions ({2}) for application "{1}" has been exceeded. Currently deployed versions are: "{3}".

Cause: An attempt was made to deploy or redeploy application "{0}" when the maximum number of application versions ("{2}") for application "{1}" has been exceeded.

Action: Try undeploying the existing application version(s) before deploying or redeploying the new version(s).
Level: 1

Type: ERROR

Impact: Deployer

BEA-149114: Cannot deploy or redeploy application "{0}" with version identifier "{1}" because the maximum length of the version identifier ({2}) has been exceeded.

Cause: An attempt was made to deploy or redeploy application "{0}" with version identifier "{1}" that exceeded the maximum length ({2}).

Action: Try reducing the version identifier length when deploying or redeploying the application version.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149115: Cannot deploy or redeploy application "{0}" with invalid version identifier "{1}". Version identifiers may only contain alphanumerics, period, underscore, and hyphen and must be less than 215 characters in length.

Cause: An attempt was made to deploy or redeploy application "{0}" with invalid version identifier "{1}".

Action: Try changing the version identifier to a valid one when deploying or redeploying the application version. Version identifiers can only consist of alphanumeric, period, underscore, or hyphen characters and must not be "." or "..".
Level: 1

Type: ERROR

Impact: Deployer

BEA-149116: Cannot obtain the deployment configuration.

Cause: This is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149117: {2} library {0} on {1}.

Cause: This is an informational message about the task description.

Action: This is an informational message about the task description.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149118: "{1}" is not targeted to "{0}".

Cause: An attempt was made to undeploy the application from a target where it is not deployed.

Action: Correct the target list for the operation.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149119: Different targets cannot be specified when deploying a new version "{1}" of application "{0}". The targets specified, "{3}", are different from those of the previous version, "{2}".

Cause: An attempt was made to deploy a new application version with targets that are different from that of the previous version.

Action: Try deploying again without specifying targets, or specify the exact same target as the previous version.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149120: The plan version "{1}" cannot be specified when deploying a non-versioned application "{0}".

Cause: An attempt was made to deploy a non-versioned application with a plan version.

Action: Try deploying again with an application version or without the plan version.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149121: Rejecting {1} request for application {0} because the deployment service is not started.

Cause: A deployment operation was attempted when the server was starting or shutting down.

Action: Perform the deployment operation again after the server has started or before the server has shut down.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149122: Deployment perations on internal application "{0}" are not permitted;.

Cause: Deployment operations are not permitted on internal applications.

Action: Do not attempt any deployment operations on internal applications.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149123: The application "{0}" currently has security model "{1}", and an attempt was made to redeploy the application again with a different security model "{2}". The specified security model will be ignored for the current deployment operation. To change the security model, undeploy the application and deploy it again with the new security model.

Cause: An attempt was made to redeploy the same application with a different security model.

Action: Undeploy the application and deploy it again with the new security model.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149124: Failures were detected while initiating {1} task for application "{0}". Error is: "{2}"

Cause: Task creation can fail for many reasons.

Action: Check the error message and take appropriate action.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149125: No application version was specified for the {0} operation of application "{1}". The {0} operation will be performed against the retired application version "{2}".

Cause: This is an informational message only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149126: No application version was specified for the {0} operation of application "{1}". The application version "{2}" will not be removed as its retirement is still in progress. Oracle recommends that the application version "{2}" be undeployed explicitly after the retirement is done. An explicit undeploy of the application version can also be performed before retirement is done; however, exercise caution as this may interrupt inflight work.

Cause: No application version was specified for the {0} operation of application "{1}".

Action: No action is required.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149127: Failures were detected while initiating "{0}" task. Error is: "{1}"

Cause: Task creation can fail for many reasons.

Action: Check the error message and take appropriate actions.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149128: The "{1}" option was specified for the {0} operation of application "{2}". The {0} operation will be performed against the retired application version "{3}".

Cause: This is an informational message only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149129: The "{1}" option was specified for the {0} operation of application "{2}". The {0} operation will be performed against the retiring application version "{3}". Note that retirement is still in progress for version "{3}" and any inflight work will be interrupted.

Cause: This is an informational message only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149130: The "{1}" option was specified for the {0} operation of application "{2}". The {0} operation will be performed against the currently active version "{3}".

Cause: This is an informational message only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149131: Cannot perform operation {2} because application "{0}" is in state {1}

Cause: The application is no longer active.

Action: Ensure that the application is active. Deploy again if needed.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149132: Split directory application {0} can only be deployed on the Administration Server.

Cause: An attempt was made to perform the deployment operation on the split directory application on a server other than the Administration Server.

Action: For split directory application {0}, perform deployment operations on the Administration Server alone.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149133: Auto-deployed application {0} can only be deployed on the Administration Server.

Cause: An attempt was made to perform the deployment operation on the auto-deployed application on a server other than the Administration Server.

Action: For auto-deployed application {0}, perform deployment operations on the Administration Server alone.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149134: A redeploy was performed without specifying -source for the archived versioned application "{0}". Partial update of an archived application is not allowed. To perform production redeployment of versioned applications, specify -source with the redeploy operation.

Cause: An attempt was made to partially redeploy an archived application.

Action: Specify -source for production redeployment, or redeploy the entire application.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149135: Operation {2} cannot be performed since application "{0}" is not deployed on the target "{1}".

Cause: Operation {2} could not be performed because the application was not deployed on the provided target.

Action: Rery with a valid target.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149137: {0} is an invalid path for partial redeployment. The URI of the file or directory to be redeployed should be relative to {1}, the root of the enterprise application, or to the standalone module being redeployed.

Cause: The file could not be located in the application.

Action: Use a valid specification for the file.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149138: A subset of the originally configured targets for the application "{0}" was specified. This can potentially lead to out-of-sync applications between the different server targets. The targets specified, "{2}", are different from those of the previous version, "{1}".

Cause: A deployment operation was performed on an existing application with a subset of the originally configured targets.

Action: If the application content has changed since the last operation, Ensure that all configured targets are updated. To do so, repeat the operation without specifying targets in order to automatically use the configured targets.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149139: Application "{0}" is targeted to cluster "{1}", and provided the target for {3} operation is "{2}". The {3} operation on a subset of the targeted clustered servers is not supported.

Cause: The {3} operation was attempted on one or more servers in the targeted cluster.

Action: Retry with the targeted cluster, or undeploy from the cluster and deploy to the desired individual servers.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149140: The task cannot be processed further until the current edit session is activated. When this occurs, task processing will continue. The user can exit the deployer tool without affecting the task.

Cause: The user is the current owner of the domain configuration edit lock.

Action: Activate (or cancel) the edit session. The user can exit the deployer tool without affecting the task.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149141: The AppDeploymentMBean already exists for application "{0}".

Cause: The AppDeploymentMBean already exists for application "{0}".

Action: Ensure that different applications do not have the same name.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149142: Cluster target "{0}" is configured with no servers, and therefore configuration is updated.

Cause: A deployment to a cluster target was attempted, but the cluster contains no servers.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149143: Submodule targets in an application must be specified with the correct module name.

Cause: A submodule target was specified incorrectly.

Action: Ensure that the submodule target was specified with the correct syntax and with the correct module name.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149145: Unable to contact "{0}". Deployment is deferred until "{0}" becomes available.

Cause: Contact with "{0}" could not be made. Deployment is deferred until "{0}" becomes available.

Action: No action is necessary.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149146: Attempt to reach the Administration Server with alternate URL: "{0}" failed.

Cause: The attempt to reach the Administration Server with the alternate URL: "{0}" failed.

Action: See the exception cause and check the preceding conflict start message in the logs. Try to avoid the conflict by following one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149147: Could not reach the Administration Server through any of its URLs: "{0}".

Cause: The Administration Server could not be reached through any of its URLs: "{0}".

Action: See the exception cause and check the preceding conflict start message in the logs. Try to avoid the conflict by following one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149148: Exception occurred while receiving a message on loopback.

Cause: An exception occurred while receiving a message on loopback.

Action: See the exception cause and check the preceding conflict start message in the logs. Try to avoid the conflict by following one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149149: Malformed URL: "{0}".

Cause: The URL: "{0}" was malformed.

Action: See the exception cause and check the preceding conflict start message in the logs. Try to avoid the conflict by following one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149150: An IOException occurred while reading the input.

Cause: An IOException occurred while reading the input.

Action: See the exception cause and check the preceding conflict start message in the logs. Try to avoid the conflict by following one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149151: Could not find a registered DeploymentReceiver to handle requests for "{0}".

Cause: A registered DeploymentReceiver could not be found to handle requests for "{0}".

Action: Check the preceding conflict start message in the logs. Try to avoid the conflict by following one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149152: No deployment request for which to set up the context.

Cause: No deployment request for which to set up the context.

Action: Check the preceding conflict start message in the logs. Try to avoid the conflict by following one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149153: A "prepare" message was received for ID "{0}" that has already been completed or canceled.

Cause: A "prepare" message was received for ID "{0}" that has already been completed or canceled.

Action: Check the preceding conflict start message in the logs. Try to avoid the conflict by following one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149154: A "get deployments response" message was received for ID "{0}" that has no request. It may have already been completed or may have been canceled.

Cause: A "get deployments response" message was received for ID "{0}" that has no request. It may have already been completed or may have been canceled.

Action: Check the preceding conflict start message in the logs. Try to avoid the conflict by following one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149155: Received "get deployments response" message "{0}" while already handling one. Ignoring the second request.

Cause: A "get deployments response" message "{0}" was received while another was being handled. The second request was ignored.

Action: Check the preceding conflict start message in the logs. Try to avoid the conflict by following one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149156: Illegal state for operation start: "{0}".

Cause: The start operation was called on an application that either had an update pending or was used with the administration mode flag.

Action: To move the application from active to administration mode, use the stop operation.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149157: There is nothing to do for task "{0}".

Cause: There is nothing to do for task "{0}".

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149158: No application files exist at "{0}".

Cause: No application files exist at "{0}".

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149159: There was an attempt to create a staging directory that is null.

Cause: There was an attempt to create a staging directory that is null.

Action: Ensure that the staging directory is properly configured. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149160: There was an attempt to create a staging directory for a null application name.

Cause: There was an attempt to create a staging directory for a null application name.

Action: Ensure that the application name is properly configured. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149161: This operation requires that a target be specified.

Cause: This operation requires that a target be specified.

Action: Ensure that the deployment request is complete and contains the required targeting information.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149162: This operation requires that a deployment plan be specified.

Cause: This operation requires that a deployment plan be specified.

Action: Ensure that the deployment request is complete and contains the required deployment plan information.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149163: The domain edit lock is owned by another session in non-exclusive mode. This deployment operation requires exclusive access to the edit lock and therefore cannot proceed. If using "Automatically Aquire Lock and Activate Changes" in the Administration Console, then the lock will expire shortly, so retry this operation.

Cause: The domain edit lock is owned by another session in non-exclusive mode. This deployment operation requires exclusive access to the edit lock and therefore cannot proceed.

Action: Ensure that the domain edit lock is available, and try again. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149164: The domain edit lock is owned by another session in exclusive mode. Therefore, this deployment operation cannot proceed.

Cause: The domain edit lock is owned by another session in exclusive mode. Therefore, this deployment operation cannot proceed.

Action: Ensure that the domain edit lock is available, and try again. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149165: Invalid target specified.

Cause: An invalid target was specified.

Action: See the exception cause and check the preceding conflict start message in the logs. Try to avoid the conflict by following one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149166: Deployments cannot be triggered through configuration updates and through the Deployment APIs simultaneously.

Cause: Deployments cannot be triggered through configuration updates and through the Deployment APIs simultaneously.

Action: Ensure that the domain edit lock is available, and try again. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149167: No action was needed to commit the request for "{0}" on "{1}".

Cause: No action was needed to commit the request for "{0}" on "{1}".

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149168: Request "{0}" has already been completed or was canceled.

Cause: The request "{0}" has already been completed or was canceled.

Action: Check the preceding conflict start message in the logs. Try to avoid the conflict by following one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149169: Requires server restart for completion.

Cause: In order to complete the action, the server must be restarted.

Action: Restart the required servers.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149170: Invalid targeting was specified for this operation. Module and submodule targets cannot both be specified for this type of request.

Cause: The operation specified both module and submodule targeting, which is invalid for this operation.

Action: Perform the operation separately for both module and submodule targets.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149171: Deferred deployment task: {0}

Cause: A deployment operation was requested with targets that were unreachable.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149172: Deployment request {0} is affecting the system resource {1}, which involves a non-dynamic property {2} in {3}. Therefore, a restart of the resource or the appropriate server targets is required for the changes to be active.

Cause: This is an informational message indicating that deployment involves a non-dynamic property.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149178: Application "{0}" is targeted to cluster "{1}", and the provided target for {3} operation is "{2}". This can potentially lead to client request problems on the cluster.

Cause: An operation was performed on a subset of a cluster for an application targeted to the cluster.

Action: Ensure that the cluster properly serves requests by performing operations on the cluster rather then on individual servers within the cluster.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149181: Deployment service encountered an error while aborting the edit session before start. Initiator for this edit session is "{0}". Error is "{1}".

Cause: See the reported error.

Action: Take appropriate action based on the reported error.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149182: An invalid alternate descriptor was specified for the redeploy operation. Alternate descriptors cannot be changed during a redeploy operation.

Cause: An invalid alternate descriptor was specified for the redeploy operation. Alternate descriptors cannot be changed during a redeploy operation.

Action: Repeat the redeploy operation without the alternate descriptor.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149183: An invalid retiretimeout option was specified for the deploy operation. The retiretimeout option was specified as "{2}" for the initial deployment of application "{0}". Retirement policies must be set during the deploy or redeploy of the next version in order to apply to version "{1}" of "{0}".

Cause: An invalid retiretimeout option was specified for the deploy operation.

Action: Specify the retiretimeout option during the deploy or redeploy of subsequent versions in order for the retirement to occur correctly at that time.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149184: The application "{0}" was autodeployed and may only be redeployed by touching the REDEPLOY file in the domain autodeploy directory for the respected application.

Cause: Autodeployed applications cannot be redeployed through tools.

Action: See the WebLogic Server documentation on autodeployed applications for more information.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149185: The application "{0}" was autodeployed and may only be deleted by removing the files from the domain autodeploy directory.

Cause: Autodeployed application cannot be undeployed through tools.

Action: See the WebLogic Server documentation on autodeployed applications for more information.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149186: The application "{0}" was autodeployed and cannot be redistributed.

Cause: Autodeployed application cannot be redistributed.

Action: See the WebLogic Server documentation on autodeployed applications for more information.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149187: An unexpected error occurred when specifying configuration information for the application "{0}" due to {1}.

Cause: Application configuration upgrade requires targeting information.

Action: Inspect the problematic application parts and deploy the application.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149188: No application named "{0}" exists for operation {1}. Operation cannot be performed until the server is restarted.

Cause: The application was created after non-dynamic changes were activated. The server needed to be restarted.

Action: Restart the server and then start the application. In the future, start the application before making non-dynamic changes to the configuration.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149189: An attempt was made to execute the "{0}" operation on an application named "{1}" that is not currently available. The application may have been created after non-dynamic configuration changes were activated. If so, the operation cannot be performed until the server is restarted so that the application will be available.

Cause: The application may have been created after non-dynamic changes were activated. The server needed to be restarted.

Action: Restart the server and then perform the operation on the application.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149190: Changes are pending from another session whose lock has expired. This deployment operation will not activate changes from another edit session and therefore cannot proceed. Either cancel the edit lock or activate the pending changes using the Administration Console or WLST.

Cause: Changes were made with an edit session that has now expired.

Action: Cancel the edit lock or activate the pending changes using the Administration Console or WebLogic Scripting Tool (WLST).
Level: 1

Type: WARNING

Impact: Deployer

BEA-149191: Operation "{0}" on application "{1}" is initializing on "{2}".

Cause: This is an informational message indicating deployment status change.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149192: Operation "{0}" on application "{1}" is in progress on "{2}".

Cause: This is an informational message indicating deployment status change.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149193: Operation "{0}" on application "{1}" has failed on "{2}".

Cause: This is an informational message indicating deployment status change.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149194: Operation "{0}" on application "{1}" has succeeded on "{2}".

Cause: This is an informational message indicating deployment status change.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149195: Operation "{0}" on application "{1}" has been deferred since "{2}" is unavailable.

Cause: This is an informational message indicating deployment status change.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149196: Rejecting {1} request for application {0} because {2} request is running for the application.

Cause: A second operation for an application was requested when an operation for the application was runnning.

Action: Perform the operation again when the operation that is running is completed.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149197: Cannot perform operation {2} because application "{0}" is in state {1}

Cause: The application is in the wrong state for the operation.

Action: Ensure that the application is in the correct state before attempting the operation.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149198: Cannot rename directory "{0}" to {1}.

Cause: The rename operation failed since the source directory is not present or there is a privilege issue.

Action: Check that the source directory is present and has the required permissions.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149199: Security permissions declared in the "{0}" deployment descriptor are not allowed due to the server's configuration.

Cause: The server is configured not to allow Java security permissions to be declared in the Weblogic deployment descriptors.

Action: Remove Java security permissions from the deployment descriptor before re-deployment.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149202: Encountered an exception while attempting to commit the {0} task for the application "{1}".

Cause: The cause of this error is likely in the application or the application subsystem for that application type.

Action: Review the exception and attempt to repair the application level. Then re-initiate the deployment request.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149205: Failed to initialize the application "{0}" due to error {1}

Cause: The cause of this error is likely in the application or the application subsystem for that application type.

Action: Review the exception and attempt to repair the application level. Then reinitiate the deployment request.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149209: The Slave Deployer is resuming.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149229: Server "{0}" in cluster "{1}" is unable to initialize due to failed deployments.

Cause: This problem occurred due to failed deployments, which are already logged.

Action: Correct the deployment problem, and restart the server in the cluster.
Level: 1

Type: INTERNAL_ERROR

Impact: Deployer

BEA-149231: Unable to set the activation state to {1} for the application "{0}".

Cause: An unexpected error occurred.

Action: Report this error to My Oracle Support.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149233: An unexpected error occurred during the deployment process.

Cause: There was a problem with the internal implementation that was not anticipated.

Action: Report the error and any useful information needed to reproduce the problem to My Oracle Support.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149239: Application deployment failures were detected during startup of the Administration Server, "{0}", member of cluster "{1}".

Cause: One or more applications could not be deployed during the startup of the Administration Server.

Action: Oracle recommends that the Administration Server not be part of a cluster. One response to this warning is to remove it from the cluster and restart the Administration Server. Alternatively, review the Administration Server log to understand why the deployment failed, fix the problem, and redeploy the application.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149243: The internal application "{0}" could not be deployed. An attempt will be made to retry deploying this application after synchronizing the application files again.

Cause: It is likely that the internal staged directory was corrupt or there was a failure when deploying the staged application.

Action: No action is necessary if the retry succeeds. Otherwise, the nature of the failure should provide an indication of the problem and its resolution. If this is not clear, contact My Oracle Support with the relevant logs and configuration files.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149245: The deployment plan at "{0}" for application "{1}" does not define a valid deployment plan.

Cause: The application is configured with an incorrect deployment plan document.

Action: Deploy the application using a valid deployment plan.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149246: The security realm "{0}" does not support application versioning. Deployment of application "{1}" failed.

Cause: The security realm "{0}" does not support application versioning. The deployment of the application version failed.

Action: Deploy the application using a security realm that supports application versioning.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149247: Failed to transition the application "{0}" to running mode due to error {1}

Cause: The cause of this error is likely in the application or the application subsystem for that application type.

Action: Review the exception and attempt to repair the application level. Then reinitiate the deployment request.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149248: Failed to transition the application "{0}" to administration mode due to error {1}.

Cause: The cause of this error is likely in the application or the application subsystem for that application type.

Action: Review the exception and attempt to repair the application level. Then reinitiate the deployment request.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149250: Unable to unprepare the application "{0}".

Cause: This was an unexpected error.

Action: Report this error to My Oracle Support.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149251: Operation {0} failed for application "{1}". Error: {2}

Cause: See the exception in the message body.

Action: Typically, no action is required.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149252: No deployment "{1}" found for operation {0}.

Cause: See the message body.

Action: No action is required.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149256: Failed to find deployment for application "{0}".

Cause: The cause of this error is likely that the deployment was not properly created, possibly because it may not have proper descriptors.

Action: Review the exception and attempt to repair the application level. Then reinitiate the deployment request.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149257: Rejecting the attempt to distribute application "{0}" while the application is running.

Cause: The application was not stopped.

Action: Stop the application or redeploy the application.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149258: The server failed to completely remove the staged files "{1}" for application "{0}". Check the directory and ensure that no other application is using this directory. This will result in inappropriate results when this server is partitioned and tries to deploy this application.

Cause: Another application might be using the files under a staging directory.

Action: Delete the appropriate staged files manually.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149259: Server "{0}" in cluster "{1}" is being brought up in administration state due to failed deployments.

Cause: This problem occurred due to failed deployments, which are already logged.

Action: Correct the cause of the deployment errors, redeploy the failed deployments, and resume or restart the server in the cluster.
Level: 1

Type: INTERNAL_ERROR

Impact: Deployer

BEA-149260: A failure occurred during application startup.

Cause: Check the error stack trace for details of the failure.

Action: Correct the cause of the application failure, if possible, and redeploy the application or restart the server. If it is an Oracle internal application, report it to My Oracle Support.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149264: Invalid redeploy attempt on application "{0}". There was an attempt to redeploy the application when the application was not running.

Cause: The application was stopped.

Action: Start the application.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149265: Failure occurred in the execution of deployment request with ID "{0}" for task "{1}". Error is: "{2}"

Cause: See the reported error in the message body.

Action: Start the application.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149266: Illegal state for operation deploy: "{0}".

Cause: The deploy operation was called on an application that was not new.

Action: Verify that the specified application name and operation are correct.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149267: Cancel operation on deployment task "{0}" on server "{1}" failed.

Cause: See the underlying exception.

Action: Take action based on the underlying exception.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149268: Static deployment of non-versioned application "{0}" failed due to a version being defined in its manifest file.

Cause: The manifest file was modified with a version for a non-versioned application.

Action: Remove the application and redeploy it with a version.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149269: Static file redeployment and module level redeployment cannot be in the same deployment task. Check the usage.

Cause: The server cannot determine which type of redeployment should be processed.

Action: Correct the deployment option.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149400: Activating application: {0}

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Application Poller

BEA-149401: Removing application: {0}

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Application Poller

BEA-149403: Application {0} deployed from the applications directory has components that are deployed on servers other than the Administration Server. Refresh of static content (such as JSPs and HTML pages) will not be automatically propagated to the Managed Servers. To propagate your changes to the Managed Servers, you must redeploy the application by touching the REDEPLOY file.

Cause: This is a warning message only.

Action: Touch the REDEPLOY file to properly redeploy the application. The REDEPLOY file is located in the same directory as the deployment descriptor. For EAR files, it is located in META-INF/REDEPLOY.
Level: 1

Type: WARNING

Impact: Application Poller

BEA-149407: An error occurred while undeploying application {0} : {1}.

Cause: Undeployment can fail for many reasons.

Action: Review the error message and take corrective action.
Level: 1

Type: ERROR

Impact: Application Poller

BEA-149408: An exception occurred while deploying an application {0}: {1}.

Cause: Deployment of an application can fail for many reasons. Refer to the exception details.

Action: Review the exception. To redeploy the application after correcting the error condition, touch the file called REDEPLOY in the META-INF or WEB-INF directory of the exploded application.
Level: 1

Type: ERROR

Impact: Application Poller

BEA-149409: Caught exception while starting the applications poller on server start {0}.

Cause: A misconfigured application may be present in the applications directory.

Action: Review the exception message in the server log.
Level: 1

Type: ERROR

Impact: Application Poller

BEA-149410: Runtime deployment error while deploying - {0}.

Cause: The cause of this error is unknown.

Action: Refer to the runtime error in the message.
Level: 1

Type: ERROR

Impact: Application Poller

BEA-149411: I/O exception was encountered {0}.

Cause: An I/O exception can occur during file read/write while deploying an application.

Action: Take corrective action based on the exception message details.
Level: 1

Type: ERROR

Impact: Application Poller

BEA-149412: Application "{0}" is being redeployed, because it changed since the previous server run.

Cause: This application is deployed using auto-deployment. The application was modified while the server was down, hence it will be redeployed by the auto-deployment poller. Another possible cause is that the internal file used by the poller was removed or moved from disk. In that case, it assumes applications have changed.

Action: No action is required. This is an informational message to explain why this deployment was redeployed after its deployment at startup.
Level: 1

Type: NOTIFICATION

Impact: Application Poller

BEA-149414: Could not create directory for autodeployed applications: {0}

Cause: This may be an error on the local file system of the Administration Server.

Action: Correct the error by creating the directory or making sure read/write permissions exist.
Level: 1

Type: WARNING

Impact: Application Poller

BEA-149415: An exception was encountered while migrating application poller applications {0}.

Cause: An exception occurred while modifying application's path.

Action: Report this error to My Oracle Support.
Level: 1

Type: ERROR

Impact: Application Poller

BEA-149416: Application migrated {0} - {1}

Cause: This is informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Application Poller

BEA-149417: Another process is using the file "{0}". The server will attempt to deploy the application once it is unlocked by the other process.

Cause: Another process has a lock on the file that is in the hot deploy directory. The application could still be in the process of being copied.

Action: Ensure that no other process is attempting to lock part or all of this application file. If the copy is ongoing, then no action should be necessary.
Level: 1

Type: WARNING

Impact: Application Poller

BEA-149500: An exception occurred while registering the MBean {0}.

Cause: Refer to the embedded exception information for more details as to the probable cause of this error.

Action: This is an internal error and should be reported as a bug to My Oracle Support.
Level: 1

Type: ERROR

Impact: JMX

BEA-149501: An exception occurred while registering the MBean {0} at property {1}.

Cause: Refer to the embedded exception information for more details as to the probable cause of this error.

Action: This is an internal error and should be reported as a bug to My Oracle Support.
Level: 1

Type: ERROR

Impact: JMX

BEA-149502: An exception occurred while unregistering the MBean {0}.

Cause: Refer to the embedded exception information for more details as to the probable cause of this error.

Action: This is an internal error and should be reported as a bug to My Oracle Support.
Level: 1

Type: ERROR

Impact: JMX

BEA-149503: An exception occurred while unregistering the MBean {0} at property {1}.

Cause: Refer to the embedded exception information for more details as to the probable cause of this error.

Action: This is an internal error and should be reported as a bug to My Oracle Support.
Level: 1

Type: ERROR

Impact: JMX

BEA-149504: The Administration Server was unable to establish JMX Connectivity with the {0} at the JMX Service URL of {1}.

Cause: This is likely due to a misconfiguration of the Managed Server. Often this is associated with the use of the administration channel.

Action: Ensure that the Managed Server adminstration ports are properly configured. It may be helpful to review the documentation on the administration channel configuration.
Level: 1

Type: WARNING

Impact: JMX

BEA-149505: The Administration Server was unable to establish JMX Connectivity with the {0} at the JMX Service URL of {1}.

Cause: This is likely because the Managed Server is simply not running. It may indicated that the administration channels are not properly configured.

Action: Ensure that the Managed Server administration ports are properly configured. It may be helpful to review the documentation on the administration channel configuration.
Level: 1

Type: NOTIFICATION

Impact: JMX

BEA-149506: Established JMX Connectivity with {0} at the JMX Service URL of {1}.

Cause: This is a normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMX

BEA-149507: JMX Connectivity has been discontinued with the Managed Server {0}.

Cause: This message is logged whenever a Managed Server is shut down.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMX

BEA-149508: Unable to establish JMX Connectivity with the Administration Server.

Cause: This may have occurred because the Administration Server is not currently available or it may indicate a misconfiguration of the administrative channels.

Action: If the Administration Server is currently running, the administrator should consult the documentation on the administration channel configuration.
Level: 1

Type: WARNING

Impact: JMX

BEA-149509: Unable to establish JMX connectivity with the Administration Server {0} at {1}.

Cause: This may have occurred because the Administration Server is not currently available or it may indicate a misconfiguration of the administrative channels.

Action: If the Administration Server is currently running, the administrator should consult the documentation on the administration channel configuration.
Level: 1

Type: WARNING

Impact: JMX

BEA-149510: Unable to establish JMX Connectivity with the Administration Server {0} at {1}.

Cause: This may have occurred because the Administration Server is not currently available or it may indicate a misconfiguration of the administrative channels.

Action: If the Administration Server is currently running, the administrator should consult the documentation on the administration channel configuration.
Level: 1

Type: WARNING

Impact: JMX

BEA-149511: Established JMX Connectivity with the Administration Server {0} at {1}.

Cause: This is a normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMX

BEA-149512: JMX Connector Server started at {0}.

Cause: This is a normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMX

BEA-149513: JMX Connector Server stopped at {0}.

Cause: This is a normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMX

BEA-149515: An error was encountered getting the attribute {1} on the MBean {0} during a call to getAttributes.

Cause: This problem is the result of an internal error in the WebLogic Server JMX implementation.

Action: Report this message to My Oracle Support.
Level: 1

Type: WARNING

Impact: JMX

BEA-149516: An error was encountered when setting the attribute {1} on the MBean {0} during a call to setAttributes.

Cause: This problem is the result of an internal error in the WebLogic Server JMX implementation.

Action: Report this message to My Oracle Support.
Level: 1

Type: WARNING

Impact: JMX

BEA-149518: An attempt was made to unregister the {0} WebLogic Server MBean through JMX.

Cause: Avoid using the JMX API to unregister a WebLogic Server MBean.

Action: Use the WebLogic Server APIs to control the configuration of the server environment.
Level: 1

Type: WARNING

Impact: JMX

BEA-149519: The JMX Service URL {1} for Managed Server {0} was malformed.

Cause: The URL used to contact a Managed Server was malformed.

Action: See the exception included with this message to determine the proper action.
Level: 1

Type: NOTIFICATION

Impact: JMX

BEA-149520: An attempt was made to register an MBean with ObjectName {0} ObjectName in com.bea domain.

Cause: An attempt was made to register an MBean with the com.bea domain name.

Action: Register your MBeans with another domain name.
Level: 1

Type: ERROR

Impact: JMX

BEA-149521: An exception occurred during the processing of JMX Connectivity with the Administration Server: {0}

Cause: Refer to the embedded exception information for more details as to the probable cause of this error.

Action: Refer to the embedded exception information for more details and troubleshoot based on that information.
Level: 1

Type: WARNING

Impact: JMX

BEA-149522: No credentials were provided.

Cause: Credentials are required when connecting through Remote MAnagement Interface (RMI).

Action: Retry the connection, supplying a username and password.
Level: 1

Type: ERROR

Impact: JMX

BEA-149523: RmiServerManager not found.

Cause: This problem is the result of an internal error in the WebLogic Server JMX implementation.

Action: Report this message to My Oracle Support.
Level: 1

Type: ERROR

Impact: JMX

BEA-149524: JMX Connector Server started at "{0}".

Cause: This is a normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMX

BEA-149525: JMX Connector Server stopped at "{0}".

Cause: This is a normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMX

BEA-149601: The deployment framework was unable to resume accepting requests.

Cause: This is an internal server error.

Action: Report the error to My Oracle Support.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149603: The deployment framework was unable to cleanly shut down.

Cause: This is an internal error.

Action: Report this error to My Oracle Support.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149605: Failed to create App/Comp MBeans for AppDeploymentMBean {0}. Error - {1}.

Cause: An error was found in the AppDeploymentMBean.

Action: Reconfigure the AppDeploymentMBean.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149606: Failed to configure deployment MBean for {0}.

Cause: An error was found while configuring a deployment MBean.

Action: Review the application and reconfigure it.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149607: Failed to persist state for deployment with name {0}. {1}

Cause: See the exception for more details on the cause of this problem.

Action: See the exception. Undeploy and deploy after correcting the problem.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149608: Unknown type of deployable: "{0}"

Cause: The type of deployable: "{0}" is unknown.

Action: See the exception and check for preceding messages in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149609: AppRuntimeStateRuntime only available on the Administration Server.

Cause: AppRuntimeStateRuntime only available on the Administration Server.

Action: Ensure that the Administration Server is running and check for preceding messages in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149610: Problems were encountered while creating the persistent store.

Cause: An exception occurred: {0}

Action: See the exception and check for preceding messages in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149611: Problems were encountered while creating the persistent store.

Cause: An exception occurred: {0}

Action: See the exception and check for preceding messages in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149612: Problems were encountered while saving to the persistent store for "{0}".

Cause: {1}

Action: See the exception and check for preceding messages in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149613: Problems were encountered while deleting from the persistent store for "{0}".

Cause: {1}

Action: Check for preceding messages in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149614: There were problems during the server disconnect for listener "{0}". {1}

Cause: {1}

Action: Check for preceding messages in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149615: Unrecognized type: "{0}".

Cause: There was an unrecognized type: "{0}".

Action: Check for preceding messages in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149616: A critical internal application {0} was not deployed. Error: {1}

Cause: The cause of this error is unknown.

Action: Check for preceding conflict start message in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149617: Non-critical internal application {0} was not deployed. Error: {1}

Cause: An internal application may not have been installed.

Action: Install the WebLogic Server internal application by running the WebLogic Server installer and choosing the relevant option.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149618: Unable to deploy an internal management Web application - {0}. Managed Servers may be unable to start.

Cause: WebLogic Server was unable to find the relevant WAR files in RootDirectory/lib. This might also be an internal failure. See the exception stack trace for more details.

Action: If you are not running the server from the directory where WebLogic Server was installed, ensure that the value of the provided RootDirectory matches the directory where the WebLogic Server product was installed. Verify that a file with the application name in the log message (with a .war extension) is present in RootDirectory/lib. If not, contact My Oracle Support.
Level: 1

Type: INTERNAL_ERROR

Impact: Deployer

BEA-149619: The deletion of configuration file {0} failed.

Cause: An error occurred while deleting the file.

Action: Ensure that no processes have the file open for write. Ensure that the permissions on the directory allow for delete of this file.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149621: An error occurred while the Administration Server was performing configuration recovery. Error is : "{0}".

Cause: See the exception details for the cause.

Action: Stop the server and do configuration recovery manually.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149622: Could not get file lock used to serialize access to configuration files.

Cause: The lock could not be obtained before the specified timeout period has elapsed.

Action: Verify the configuration files and ensure no server has hung, thereby not releasing the lock.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149623: Unable to create DeploymentManagerMBean.

Cause: This may occur if an error at the JMX level exists.

Action: Report this problem to Oracle Customer Support.
Level: 1

Type: INTERNAL_ERROR

Impact: Deployer

BEA-150000: An error occurred while establishing a connection back to the Adminstration Server {0} during startup. Since bootstrap succeeded, check that {0} uniquely identifies the Administration Server.

Cause: An improper Administration Server URL has been specified, or the Administration Server is not available at the specified URL. Commonly this is because the Managed Server shares an adminstration URL with the Administration Server. Another possibility is that the host identified by {0}, or the local host, is not configured properly. For instance, an /etc/hosts or DNS lookup on the hostname results in a loopback address.

Action: Verify that the URL specified for the Administration Server is valid, unique and that the Administration Server is available and listening at the specified URL. A common problem is that the administration port is enabled and both the Administration Server and Managed Server are running on the same machine. In this instance a different administration port should be selected for the Managed Server. Another possibility is that the host identified by {0}, or the local host, is not configured properly. For instance, an /etc/hosts or DNS lookup on the hostname results in a loopback address.
Level: 1

Type: ERROR

Impact: Configuration Management

BEA-150001: An error occurred while connecting to the Administration Server to bootstrap through the URL: {0}, user: {1}.

Cause: The Administration Server might currently be unavailable or the specified URL: {0} or username: {1} might be invalid.

Action: Confirm that the designated Administration Server is running and that the specified URL: {0} and username: {1} are valid for this configuration.
Level: 1

Type: ERROR

Impact: Configuration Management

BEA-150014: The Managed Server Independence feature is disabled for this server ({0}).

Cause: The specified Administration Server is either incorrect or not reachable on the network.

Action: Ensure that the Administration Server is running and reachable by this server, or set the ManagedServerIndependenceEnabled attribute on this server to true.
Level: 1

Type: INTERNAL_ERROR

Impact: Configuration Management

BEA-150018: This server is being started in Managed Server independence mode in the absence of the Administration Server.

Cause: The Managed Server was unable to communicate with the Adminstration Server at the provided URL because the specified Administration Server either was not running or was partitioned.

Action: Restart the Administration Server with Managed Server discovery enabled so that the running Managed Server can synchronize its configuration with the Administration Server and become centrally managed.
Level: 1

Type: NOTIFICATION

Impact: Configuration Management

BEA-150020: The Managed Server could not reach the Administration Server at {0}.

Cause: The Managed Server was given a URL on which the Administration Server could not be contacted.

Action: Inspect the Administration Server address:port provided to the Managed Server that is being started. This address should be changed to point to the Administration Server rather than resolving locally on the Managed Server.
Level: 1

Type: ERROR

Impact: Configuration Management

BEA-150021: The Administration Server failed to authenticate the identity of the user {0} starting the Managed Server. The reason for the error is {1}.

Cause: The username and password combination was not correct.

Action: Inspect the username and password of the user starting the Managed Server and supply the correct credentials. The username and password are specified on startup with -Dweblogic.management.username and -Dweblogic.management.password command line options to the java weblogic.Server command.
Level: 1

Type: ERROR

Impact: Configuration Management

BEA-150024: The server name {0} is being started again as a Managed Server.

Cause: The Administration Server is being started as the Managed Server.

Action: Specify a different server name to start.
Level: 1

Type: ERROR

Impact: Configuration Management

BEA-150026: The server {0} being started is at an invalid release level {1} with respect to the Administration Server {2}. The major version of the Administration Server must be less than or equal to the major version of the Managed Server.

Cause: A Managed Server of a different major release is attempting to start from the Administration Server.

Action: Point the Managed Server to an Administration Server at the correct release level.
Level: 1

Type: ERROR

Impact: Configuration Management

BEA-150027: Server name {0} not found in domain {1}.

Cause: A Managed Server is started with -Dweblogic.Name with a value that was not configured in the domain.

Action: Specify the correct value of the parameter -Dweblogic.Name.
Level: 1

Type: ERROR

Impact: Configuration Management

BEA-150028: A security failure or an exception occurred when retrieving the bootstrap information for the Managed Server.

Cause: An invalid username and password might have been supplied while starting the Managed Server.

Action: Supply the correct credentials. Take corrective action based on the exception details.
Level: 1

Type: ERROR

Impact: Configuration Management

BEA-150032: The Managed Server did not provide any version details at initial contact.

Cause: A Managed Server of a different major and minor release is attempting to start from the Administration Server.

Action: Point the Managed Server to an Administration Server at the correct release level.
Level: 1

Type: ERROR

Impact: Configuration Management

BEA-150034: An attempt was made to download the configuration for the server {0} without the required credentials.

Cause: This should not happen during normal operations and may represent an attempt to compromise the server.

Action: Identify the server from which the connection was made and ensure that the username and password are being properly specified.
Level: 1

Type: ERROR

Impact: Configuration Management

BEA-150035: An attempt was made to download the configuration for the server {0} by the user {1} with an invalid password.

Cause: This should not happen during normal operations and may represent an attempt to compromise the server.

Action: Identify the server from which the connection was made and ensure that the username and password are being properly specified.
Level: 1

Type: ERROR

Impact: Configuration Management

BEA-150036: An attempt was made to download the configuration for the server {0} by the unauthorized user {1}.

Cause: This should not happen during normal operations and may represent an attempt to compromise the server.

Action: Identify the server from which the connection was made and ensure that the username and password are being properly specified.
Level: 1

Type: ERROR

Impact: Configuration Management

BEA-150038: A configuration file was found in the parent directory {0}, but the root directory is empty.

Cause: This message indicates that a configuration file exists in the parent of the root directory.

Action: If the specified root directory is not correct, then take appropriate action. Otherwise, this message may be ignored.
Level: 1

Type: WARNING

Impact: Configuration Management

BEA-150039: The server name could not be determined.

Cause: The name was not specified or the specified name does not exist in the config.xml file.

Action: Specify the correct value of the parameter -Dweblogic.Name.
Level: 1

Type: ERROR

Impact: Configuration Management

BEA-150041: The server name {0} is unknown to the Administration Server. Check if restart is required.

Cause: The -Dweblogic.Name command line property specifies a server that does not exist in the configuration that is active on the Administration Server. This can occur if the Managed Server was added to the configuration along with non-dynamic changes that affect the Administration Server. In this case, the Administration Server must be restarted.

Action: Check to see if the Administration Server is marked as needing a restart. If it is, then restart the Administration Server before trying to start this Managed Server. Check the configuration for the list of configured servers.
Level: 1

Type: ERROR

Impact: Configuration Management

BEA-150042: The -Dweblogic.management.server value of {0} does not specify a port that has administrator privileges. Change the startup command to specify a -Dweblogic.management.server value of {1}. This server will remain in Managed Server independence mode until it is started with a port that has administrator privileges.

Cause: The specified Administration Server port does not support the administrator traffic required to allow the Managed Server to communicate with the Administration server.

Action: Change the -Dweblogic.management.server property to specify a port that has administator privileges.
Level: 1

Type: INTERNAL_ERROR

Impact: Configuration Management

BEA-150043: Cannot delete server {0} in domain {1} while the server is running. Please shut down the server in order to delete the server.

Cause: An attempt was made to delete a static or dynamic Managed Server while it was still running.

Action: Shut down the server and retry the change that deleted the server.
Level: 1

Type: ERROR

Impact: Configuration Management

BEA-159900: USER {0} CREATED {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration Audit

BEA-159901: USER {0} CREATE {1} FAILED {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration Audit

BEA-159902: USER {0} REMOVED {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration Audit

BEA-159903: USER {0} REMOVE {1} FAILED {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration Audit

BEA-159904: USER {0} MODIFIED {1} ATTRIBUTE {2} FROM {3} TO {4}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration Audit

BEA-159905: USER {0} MODIFY {1} ATTRIBUTE {2} FROM {3} TO {4} FAILED {5}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration Audit

BEA-159907: USER {0} INVOKED ON {1} METHOD {2} PARAMS {3}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration Audit

BEA-159908: USER {0} INVOKED ON {1} METHOD {2} PARAMS {3} FAILED {4}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration Audit

BEA-159909: USER {0}, configuration auditing is enabled.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration Audit

BEA-159910: USER {0}, configuration auditing is disabled.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration Audit

BEA-159911: Invalid number {0} was found while encrypting clear text passwords.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration Audit

BEA-160001: Error deploying {0}: {1}

Cause: The application is misconfigured. See the logged exception for more details.

Action: Check the config.xml to ensure that the component MBean is wrapped in a valid application MBean and that it has a valid URI and target attribute. Check the server log for errors.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160032: Unable to create mbean Name: {0} Type: {1} Exception: {2}

Cause: See message body.

Action: See exception message logged.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160039: Failed to undeploy a mail session.

Cause: There was a JNDI unbind error.

Action: Check the error that is reported in the exception.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160040: Deployed MailSession named {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: J2EE

BEA-160041: Undeployed MailSession named {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: J2EE

BEA-160069: Error while looking for Web services files: {0}

Cause: An IOException occurred while accessing Web services files.

Action: See the stack trace for details.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160083: Error: The ejb-link "{0}" declared in the ejb-ref or ejb-local-ref "{1}" for EJB "{2}" in the module "{3}" could not be resolved. The ejb-jar file "{4}" could not be found in this EAR file.

Cause: The path to the target EJB does not exist in the application.

Action: The ejb-link must be fixed to point to the module containing the target EJB.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160084: Error: The ejb-link "{0}" declared in the ejb-ref or ejb-local-ref "{1}" in the module "{2}" could not be resolved. The ejb-jar file "{3}" could not be found in this ear file.

Cause: The path to the target EJB does not exist in the application.

Action: The ejb-link must be fixed to point to the module containing the target EJB.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160085: Error: The ejb-link "{0}" declared in the ejb-ref or ejb-local-ref "{1}" for EJB "{2}" in the module "{3}" could not be resolved. The EAR module "{4}" does not contain an EJB with the name "{5}".

Cause: The specified EJB does not exist in the module.

Action: The ejb-link must be fixed to point to a valid EJB.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160086: Error: The ejb-link "{0}" declared in the ejb-ref or ejb-local-ref "{1}" in the module "{2}" could not be resolved. The EAR module "{3}" does not contain an EJB with the name "{4}".

Cause: The specified EJB does not exist in the module.

Action: The ejb-link must be fixed to point to a valid EJB.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160087: Error: The ejb-link "{0}" declared in the ejb-ref or ejb-local-ref "{1}" for EJB "{2}" in the module "{3}" did not resolve to a bean with component interfaces. Ensure that the link is correct.

Cause: The link did not resolve to a valid EJB.

Action: The ejb-link must be fixed to point to a valid EJB.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160088: Error: The ejb-link "{0}" declared in the ejb-ref or ejb-local-ref "{1}" in the module "{2}" did not resolve to a bean with component interfaces. Ensure that the link is correct.

Cause: The link did not resolve to a valid EJB.

Action: The ejb-link must be fixed to point to a valid EJB.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160089: Error: The ejb-link "{0}" declared in the ejb-ref or ejb-local-ref "{1}" for EJB "{2}" in the module "{3}" could not be resolved. No EJB named "{0}" with component interfaces exists in the application. Ensure that the link is correct.

Cause: The specified EJB does not exist in the module.

Action: The ejb-link must be fixed to point to a valid EJB.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160090: Error: The ejb-link "{0}" declared in the ejb-ref or ejb-local-ref "{1}" in the module "{2}" could not be resolved. No EJB named "{0}" with component interfaces exists in the application. Ensure that the link is correct.

Cause: The specified EJB does not exist in the module.

Action: The ejb-link must be fixed to point to a valid EJB.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160091: Error: The ejb-link "{0}" declared in the ejb-ref or ejb-local-ref "{1}" for EJB "{2}" in the module "{3}" is ambiguous. The following list of application modules contain an EJB with the name "{0}": {4}. Qualify this ejb-link to remove the ambiguity.

Cause: The ejb-link is unqualified and resolves to multiple EJBs in the application.

Action: The ejb-link must be fixed to point to a single EJB.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160092: Error: The ejb-link "{0}" declared in the ejb-ref or ejb-local-ref "{1}" in the module "{2}" is ambiguous. The following list of application modules contain an EJB with the name "{0}": {3}. Qualify this ejb-link to remove the ambiguity.

Cause: The ejb-link is unqualified and resolves to multiple EJBs in the application.

Action: The ejb-link must be fixed to point to a single EJB.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160093: Error: The ejb-link "{0}" declared in the {1} "{2}" for EJB "{3}" in the module "{4}" could not be established. The target of the ejb-link does not have {5} interfaces. Ensure that the link is correct.

Cause: The ejb-link resolves to an EJB which does not expose interfaces compatible with the ref type.

Action: Ensure that the target of the ejb-link is correct. If it is, either add component interfaces to this EJB that are compatible with the ref type or change the ref type to be compatible with the interfaces exposed by the target EJB.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160094: Error: The ejb-link "{0}" declared in the {1} "{2}" in the module "{3}" could not be established. The target of the ejb-link does not have {4} interfaces. Ensure that the link is correct.

Cause: The ejb-link resolves to an EJB which does not expose interfaces compatible with the ref type.

Action: Ensure that the target of the ejb-link is correct. If it is, either add component interfaces to this EJB that are compatible with the ref type or change the ref type to be compatible with the interfaces exposed by the target EJB.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160095: Warning: The {0} "{1}" for EJB "{2}" in the module "{3}" has an invalid {4} element value "{5}". The target bean does not declare that {4} interface. Ensure that the values are correct.

Cause: The home or component interface name in the ejb-ref or ejb-local-ref does not match the home or component interface name of the target EJB.

Action: Ensure that the target of the ejb-link is correct. If it is, fix the ejb-ref or ejb-local-ref so that the names of the home and component interfaces match the names of the home and component interfaces of the target EJB.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160096: Warning: The {0} "{1}" in the module "{2}" has an invalid {3} element value "{4}". The target bean does not declare that {3} interface. Ensure that the values are correct.

Cause: The home or component interface name in the ejb-ref or ejb-local-ref does not match the home, component or business interface name of the target EJB.

Action: Ensure that the target of the ejb-link is correct. If it is, fix the ejb-ref or ejb-local-ref so that the names of the home and component interfaces match the names of the home and component interfaces of the target EJB.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160098: Unable to parse the file "{0}" because it uses an invalid encoding name, "{1}". All deployment descriptors must use an IANA or Java encoding name. Change the encoding of the descriptor to be a supported encoding.

Cause: The encoding name used by the deployment descriptor is not supported.

Action: Change the encoding name of the deployment descriptor to an IANA or Java encoding name.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160100: Could not deploy role: {0} for application: {1}.

Cause: The application could not deploy the role defined in application.xml.

Action: Ensure that the security is configured properly in the server. Also, check the stack trace for the exact cause.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160101: Error: The ejb-link "{0}" declared in the ejb-ref or ejb-local-ref "{1}" in the application module "{2}" could not be resolved. The target EJB for the ejb-ref could not be found. Ensure that the link is correct.

Cause: The target of the ejb-link could not be found in the application.

Action: Fix the ejb-link to point to a valid EJB.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160104: Invalid local reference in application {0}. A local reference from module {1} to {2} is not allowed because the referencing module does not have visibility to the classes of the referenced module.

Cause: The current module does not have visibility to the classloader of the EJB being referenced.

Action: Look at the classloader organization defined by the classloader-structure element in weblogic-application.xml and ensure that the calling module is either using the same classloader as the module containing the referenced EJB or that the calling module is using a classloader that is an offspring of the classloader of the EJB module.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160106: ERROR: The source file, "{0}", could not be found.

Cause: The source file could not be found.

Action: Ensure that the specified source file exists and try again.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160108: ERROR: Error accessing input file "{0}": {1}

Cause: The source file could not be accessed.

Action: Ensure that the source file is accessible and try again.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160109: ERROR: Error copying files to the directory "{0}": {1}

Cause: The compiler was unable to extract the source archive to a directory. This can be caused by a lack of permission to write to the directory or a lack of disk space.

Action: Ensure that the directory is writable and that there is enough free disk space to extract the archive. Alternatively, manually extract the archive to a directory and specify the directory name as the appc argument instead of the archive.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160110: ERROR: appc could not create the working directory, "{0}". Ensure that this directory can be created and try again.

Cause: A directory was specified in the appc command and it could not be created. appc will not be able to finish compiling the application because of this.

Action: Ensure that the directory can be created and try again.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160111: ERROR: appc can not write to the working directory, "{0}". Ensure that you have write permission for this directory and try again.

Cause: The specified directory is not writable.

Action: Ensure that the directory is writable and try again.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160112: Error: The directory, "{0}", does not contain a valid module. If the directory represents an EAR file, it must contain a META-INF/application.xml file. If the directory represents an ejb-jar file, it must contain a META-INF/ejb-jar.xml file. If the directory represents a WAR file, it must contain a WEB-INF/web.xml file. Ensure that the source directory is a valid module and try again.

Cause: The specified directory does not contain a valid module to compile.

Action: Ensure that the specified source directory contains a valid module and try again.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160113: Error: The source file, "{0}", is not a valid ejb-jar file. To be valid, it must contain a META-INF/ejb-jar.xml file.

Cause: The specified source file is not a valid ejb-jar file.

Action: Ensure that the specified source file is a valid ejb-jar file and try again.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160114: Error: The source file, "{0}", is not a valid WAR file. To be valid, it must contain a WEB-INF/web.xml file.

Cause: The specified source file is not a valid WAR file.

Action: Ensure that the specified source file is a valid WAR file and try again.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160115: Error: The source file, "{0}", is not a valid EAR file. To be valid, it must contain a META-INF/application.xml file.

Cause: The specified source file is not a valid EAR file.

Action: Ensure that the specified source file is a valid EAR file and try again.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160117: appc is unable to continue processing file "{0}": {1}

Cause: An error occurred while processing the specified source file.

Action: Find the cause of the exception and take any necessary steps to remedy it.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160118: appc is unable to continue processing the file "{0}". The following error occurred while accessing it: {1}

Cause: An error occurred while processing the specified source file.

Action: Find the cause of the exception and take any necessary steps to remedy it.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160119: appc is unable to process the file "{0}". The following error occurred: {1}

Cause: An error occurred while processing the specified source file.

Action: Find the cause of the exception and take any necessary steps to remedy it.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160120: Error: The module, "{0}", is declared either in the application.xml or in the weblogic-application.xml descriptor but cannot be found in the EAR file.

Cause: The specified module cannot be found in the EAR file.

Action: Ensure that either the application.xml or the weblogic-application.xml declaration is correct.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160121: Errors encountered while compiling module "{0}": {1}

Cause: Errors were encountered while compiling the specified module.

Action: Investigate the specific errors and take any recommended actions.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160122: Errors validating EAR file: {0}

Cause: Errors were encountered while validating the EAR file.

Action: Investigate the specific errors and take any recommended actions.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160123: ERROR: Could not create output archive, "{0}", restoring previous archive. The error was: {1}

Cause: An error occurred while creating the output archive.

Action: Investigate the specific error and take any necessary actions.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160124: ERROR: Could not create output archive "{0}". The error was: {1}

Cause: An error occurred while creating the output archive.

Action: Investigate the specific error and take any necessary actions.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160125: ERROR: Could not delete old backup file: {0}.

Cause: An old backup file could not be removed.

Action: Determine why the old backup file could not be deleted and remedy the problem. Manually deleting the old backup file prior to running appc should fix this issue.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160126: ERROR: Could not create backup file "{0}". The error was: {1}

Cause: The specified backup file could not be created.

Action: Determine why the backup file could not be created and remedy the problem. In particular, ensure that you have write permission to the specified file and that the disk is not full.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160127: ERROR: Could not delete previous archive: {0}

Cause: The specified archive could not be removed.

Action: Determine why the archive could not be deleted and remedy the problem. In particular, ensure that you have permission to modify the specified file.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160128: ERROR: Incorrect appc command. Too many arguments were given. The appc command only takes a single argument, the source file, in addition to the supported options.

Cause: Too many arguments were specified in the appc command.

Action: Correct the command and try again.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160129: ERROR: The alt-dd "{0}", specified for application module "{1}", could not be found. Remove the alt-dd entry from the application.xml descriptor or ensure that it points to a valid deployment descriptor.

Cause: The specified alt-dd could not be found.

Action: Remove the invalid alt-dd entry from application.xml or ensure that it points to a valid deployment descriptor.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160130: ERROR: The application level alt-dd "{0}", specified in the appc command, could not be found. Ensure that the alt-dd points to a valid deployment descriptor or remove it from the command line.

Cause: The specified alt-dd could not be found.

Action: Correct or remove the invalid alt-dd setting in the appc command.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160132: Warning: The {0} "{1}" for EJB "{2}" in the module "{3}" has an ejb-ref-type of {4} but the ejb-link does not resolve to an EJB of that type. Ensure that the ejb-link and ejb-ref-type are correct.

Cause: The ejb-ref or ejb-local-ref resolves to an EJB of a different type than is declared in the ejb-ref.

Action: Ensure that the ejb-ref or ejb-local-ref resolves to the correct EJB. Once this is verified, ensure that the ejb-ref-type declared in the ejb-ref corresponds to the type of EJB being referred to.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160133: Warning: The {0} "{1}" in the module "{2}" has an ejb-ref-type of {3} but the ejb-link does not resolve to an EJB of that type. Ensure that the ejb-link and ejb-ref-type are correct.

Cause: The ejb-ref or ejb-local-ref resolves to an EJB of a different type than is declared in the ejb-ref.

Action: Ensure that the ejb-ref or ejb-local-ref resolves to the correct EJB. Once this is verified, ensure that the ejb-ref-type declared in the ejb-ref corresponds to the type of EJB being referred to.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160134: Error: The EJB with the name "{0}" in ear module "{1}" has an entity-cache-ref with the name "{2}" in its weblogic-ejb-jar.xml descriptor but no application level entity cache with that name is defined in the weblogic-application.xml descriptor for the application.

Cause: The entity-cache referred to by the EJB could not be found.

Action: Ensure that the entity-cache-ref is correct in the weblogic-ejb-jar.xml descriptor for the EJB. Also, ensure that an entity-cache with the same name is declared in the weblogic-application.xml descriptor for the application.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160137: Error: The message-destination-link "{0}" declared in the message-destination-ref "{1}" in the application module "{2}" could not be resolved. The target message-destination for the message-destination-ref could not be found. Ensure that the link is correct.

Cause: The target of the message-destination-link could not be found in the application.

Action: Fix the message-destination-link to point to a valid message-destination.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160138: Could not set active version state for application: {0}.

Cause: This is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160139: The following library reference has "context-path" set, which has no effect when referencing a {1} library: {0}.

Cause: The library reference has "context-path" set, but is not referencing a WAR library.

Action: Remove "context-path" from the library reference.
Level: 1

Type: NOTIFICATION

Impact: J2EE

BEA-160140: Unresolved optional package references (in META-INF/MANIFEST.MF): {0}. Ensure that the referenced optional package has been deployed as a library.

Cause: One or more MANIFEST.MF files contain references to optional packages (using the Extension-List attribute). One or more of the referenced optional packages are not available.

Action: Register the required optional packages or remove the reference(s) from the manifest(s).
Level: 1

Type: WARNING

Impact: J2EE

BEA-160141: Could not initialize the library {0}. Ensure that the deployment unit is a valid library type (WAR, EJB, EAR, plain JAR). {1}

Cause: Refer to the exception in the message body.

Action: Examine the stack trace.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160142: The library at {0} has an illegal Specification-Version: {1}. The Specification-Version must be a valid version string: int(.int)*, int >=0; for example: 2.1.1

Cause: The Specification-Version for the library at {0} cannot be parsed.

Action: Fix the library Specification-Version to conform to the required version string syntax.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160143: Library {0} has an illegal Specification-Version: {1}. The Specification-Version must be a valid version string: int(.int)*, int >=0. For example: 2.1.1.

Cause: The library cannot be statically deployed because its MBean has an invalid Specification-Version.

Action: Undeploy the library and deploy it again with a correct Specification-Version.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160144: Failed to register library {0}: {1}

Cause: The error is: {1}

Action: Examine the error message.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160145: Failed to deploy library {0}, because of conflicting library Manifest values, and library information registered with the server: {1}. Check the library MANIFEST.MF file and correct version information there to match server settings, or undeploy the misconfigured library.

Cause: Conflict between library manifest values and library settings in the LibraryMBean.

Action: Check the library MANIFEST.MF file and correct the version information there to match server settings, or undeploy the misconfigured library.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160146: Failed to process library at {0}, because of conflicting library manifest values and the library information provided on the appc command line: {1}.

Cause: There was a conflict between the library manifest values and the library information provided on the appc command line.

Action: Avoid setting the library name and version information on the appc command line if its already set in the manifest or remove values from the manifest and set them on the appc command line.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160147: One or more libraries could not be processed. See error above.

Cause: See error above.

Action: See error above.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160148: These libraries were not referenced by the compiled application: {0}.

Cause: The compiled application did not reference the libraries that were passed to appc.

Action: These libraries do not need to be passed to appc to compile this particular application.
Level: 1

Type: NOTIFICATION

Impact: J2EE

BEA-160149: Error while processing library references. {0}

Cause: The application has library references that do not resolve.

Action: Ensure that the library references are accurate and that the required libraries are available.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160150: A library reference in weblogic-application.xml has an illegal Specification-Version: {0}. The Specification-Version must be a valid version string: int(.int)*, int >=0; example: 2.1.1

Cause: The Specification-Version of a library reference in weblogic-application.xml cannot be parsed.

Action: Fix the library Specification-Version in weblogic-application.xml to conform to the required version string syntax.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160151: Registered library {0}.

Cause: Library registration was successful.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: J2EE

BEA-160152: The library at {0} was not recognized as a valid library type.

Cause: The library at {0} was not recognized as a valid library type.

Action: Ensure that the library is one of the supported library types.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160153: Error while cleaning up library {0}: {1}

Cause: Error while cleaning up library {0}: {1}

Action: Examine the stack trace.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160154: Error while cleaning up library: {0}. {1}

Cause: Error while cleaning up library: {0}. {1}

Action: Examine the stack trace.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160155: Cannot find library at: {0}.

Cause: {0} is not a file.

Action: Fix the path to the library.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160156: Cannot process libdir: {0} is not a directory.

Cause: {0} is not a directory.

Action: Fix the path to libdir.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160157: The referenced library, {0}, is not a supported application library.

Cause: {0} is not a supported application library.

Action: Remove the reference to library {0} from weblogic-application.xml.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160158: Ignoring Extension-List reference {0}, because the manifest does not have an entry for {0}-Extension-Name. The manifest is at {1}/META-INF/MANIFEST.MF

Cause: A declared Extension-List name does not have the required Extension-Name entry.

Action: Remove {0} from the Extension-List or add {0}-Extension-Name entry into the manifest.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160159: Bad optional package reference in manifest at {2}/META-INF/MANIFEST.MF, for optional package with Extension-Name: {0}. Illegal Specification-Version: {1}. The Specification-Version must be a valid version string: int(.int)*, int >=0; example: 2.1.1. Ignoring this Optional Package reference.

Cause: Cannot parse the Specification-Version of an optional package reference.

Action: Change the optional package reference Specification-Version to the required version string syntax.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160161: Error while parsing the application descriptors for {0}: {1}.

Cause: The cause is {1}

Action: Examine the error message.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160162: No META-INF/application.xml was found in the EAR at {0}.

Cause: The application.xml file could not be found.

Action: Ensure that the path to the EAR file is correct and add the missing application.xml.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160163: No modules were found in application.xml for EAR: {0}. Nothing to do.

Cause: There are no modules in this EAR's application.xml

Action: Add module entries to the EAR's application.xml.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160164: Error while importing library {0}: {1}

Cause: See the exception: {1}.

Action: Examine the stack trace.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160165: The EAR library at {0} is organized using the splitdir directory structure. splitdir is not supported for libraries.

Cause: splitdir is not supported for EAR libraries.

Action: Archive this library. If a build file was generated using BuildXMLGen, run the EAR target in that file.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160166: References were found in the deployment plan for module "{0}" with URI, "{1}". The plan was merged.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: J2EE

BEA-160167: The module {1} in application {0} uses ejb-links but no EJB modules were found for this application.

Cause: The ejb-links must correspond to an EJB module deployed within the same application.

Action: Ensure that the EJB modules to which you intended to link exist and have been configured properly.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160168: An error occurred while merging descriptors: {0}

Cause: An error occurred while merging descriptors. Check the stack trace.

Action: Check the stack trace.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160169: An error occurred while parsing descriptors: {0}

Cause: An error occurred while parsing descriptors.

Action: Check the stack trace.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160170: Imported library {0} for Application {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: J2EE

BEA-160171: ERROR: The plan file, "{0}", could not be found.

Cause: The plan file could not be found.

Action: Ensure that the specified plan file exists and try again.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160172: ERROR: To run appc, specify a plan file ending with the suffix .xml.

Cause: The plan file type is not supported.

Action: Correct the plan argument and try again.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160173: ERROR: Error accessing input file "{0}": {1}

Cause: The plan file could not be accessed.

Action: Ensure that the plan file is accessible and try again.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160174: ERROR: Failed to parse deployment plan "{0}": {1}

Cause: The plan file could not be parsed.

Action: Resolve parse errors in the plan and retry.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160175: ERROR: Could not find JMS module of name "{2}" specified in the resource-link named "{3}" in the "{1}" component named "{0}".

Cause: The JMS module used in the resource-link cannot be found in the application package.

Action: Package the missing JMS module as part of this application and retry.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160176: ERROR: Could not find the JMS resource named "{4}" of type "{5}" inside the JMS module "{2}" that is specified in the resource-link named "{3}" in the "{1}" component named "{0}".

Cause: The JMS resource used in th resource-link was not found in the application package.

Action: Create the missing JMS resource in the corresponding JMS module and retry.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160177: The application at "{0}" was not recognized as a valid application type. If this is an EAR file, please ensure the META-INF/application.xml exists. EJB-JARs should have a META-INF/ejb-jar.xml or corresponding annotations exist. If this is an exploded WAR, the name of directory must be end with ".war". RARs require a META-INF/ra.xml. A JMS deployment should be an XML file whose name ends with "-jms.xml". A JDBC deployment should be an XML file whose name ends with "-jdbc.xml". For other application types, consult the WebLogic Server documentation.

Cause: The application was not a valid J2EE application.

Action: Correct the application and try again.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160180: An error was encountered and ignored while rolling back an update to application {0}. The error was: {1}

Cause: See the included error message.

Action: Correct the application based on the reported error.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160181: An error was encountered and ignored during undeployment. The error was: {0}

Cause: See the included error message.

Action: Correct the application based on the reported error.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160182: An error was encountered and ignored during transition to administration mode. The error was: {0}

Cause: See the included error message.

Action: Correct the application based on the reported error.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160183: Unable to find the jar-uri: {1} specified for the ApplicationLifecycleListener, Startup, or Shutdown class in the weblogic-application.xml of application: {0}.

Cause: The JAR URI is incorrect or the file does not exist or cannot be read.

Action: Correct the application based on the reported error.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160184: ERROR: Could not find JDBC module of name "{2}" specified in the resource-link named "{3}" in the "{1}" component named "{0}".

Cause: The JDBC module used in the resource-link was not found in the application package.

Action: Package the missing JDBC module as part of this application and retry.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160185: ERROR: Could not find the JDBC resource named "{4}" of type "{5}" inside the JDBC module "{2}" that is specified in the resource-link named "{3}" in the "{1}" component named "{0}".

Cause: The JDBC resource used in the resource-link was not found in the application package.

Action: Create the missing JDBC resource in the corresponding JDBC module and retry.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160186: Compiling EAR module "{0}"

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: J2EE

BEA-160187: weblogic.appc failed to compile the application. Recompile with the -verbose option for more details about the issue.

Cause: Compilation can fail for many reasons. See the specific error message for details.

Action: Use the provided error message to track down and fix the problem. If you believe the error is due to a bug in WebLogic Server, please contact My Oracle Support.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160188: {0}.

Cause: The application has library references that do not resolve.

Action: Ensure that the library references are accurate and that the required libraries are available.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160189: There are no modules in the application that match URIs: {0}. Note that for Web applications, you should specify the context-root rather than the web-uri.

Cause: The specified URIs were not found in the running application.

Action: Specify the correct URIs which are typically found in your application's META-INF/application.xml.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160191: While upgrading weblogic.xml, the server encountered "{1}" parameter "{0}". This parameter has been deprecated and will be removed

Cause: This is a deprecated parameter.

Action: Remove the deprecated parameter from the weblogic.xml deployment descriptor.
Level: 1

Type: NOTIFICATION

Impact: J2EE

BEA-160192: While upgrading weblogic.xml, the server encountered "{1}" parameter "{0}". This parameter is unknown and will be removed

Cause: The parameter is not defined in the schema.

Action: Check the weblogic.xml deployment descriptor and remove the parameter.
Level: 1

Type: NOTIFICATION

Impact: J2EE

BEA-160193: Error: The source file, ''{0}'', is not a valid RAR file. To be valid, it must contain a META-INF/ra.xml file.

Cause: The specified source file is not a valid RAR file.

Action: Ensure that the specified source file is a valid RAR file and try again.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160194: The following modules cannot be started because they are already running: {0}.

Cause: The specified modules are already running.

Action: Remove the specified modules from the list of modules to partially stop.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160195: The application version lifecycle event listener {1} is ignored because the application {0} is not versioned.

Cause: The application is not a versioned application.

Action: If the application is deployed as a non-versioned application in error, undeploy the current application and deploy it as a versioned application. If the application version lifecycle listener is specified in error, remove it from the application or specify a non-versioned application lifecycle listener.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160196: Unable to find the jar-uri: {1} specified for the Singleton class in the weblogic-application.xml of application: {0}

Cause: The JAR URI is incorrect or the file does not exist or cannot be read.

Action: Correct the application based on the reported error.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160197: Unable to load descriptor {1} of module {0}. The error is {2}.

Cause: The descriptor is not valid.

Action: Correct the descriptor based on the reported error.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160198: Error: The ejb-ref "{3}" configured via an @EJB annotation in the module "{0}" is linked to the EJB "{1}". However, the EJB "{1}" does not declare the interface "{2}", as specified by the @EJB annotation. Ensure that the ejb-ref is linked to the correct bean and that the target bean declares the interface specified by the ejb-ref.

Cause: The @EJB has an incorrect beanName (ejb-link) attribute or the target bean must implement the interface declared by the @EJB annotation.

Action: Ensure that the ejb-ref is linked to the correct bean and that the target bean declares the interface specified by the ejb-ref.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160199: Error resolving ejb-ref "{0}" from module "{1}" of application "{2}". The ejb-ref does not have an ejb-link and the JNDI name of the target Bean has not been specified.

Cause: Attempts to automatically link the ejb-ref to its target Bean failed because multiple EJBs in the application were found to implement the "{3}" interface, including {4}.

Action: Specify a qualified ejb-link for this ejb-ref to indicate which EJB is the target of this ejb-ref.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160200: Error resolving ejb-ref "{0}" from module "{1}" of application "{2}". The ejb-ref does not have an ejb-link and the JNDI name of the target bean has not been specified. Attempts to automatically link the ejb-ref to its target bean failed because no EJBs in the application were found to implement the "{3}" interface. Link or map this ejb-ref to its target EJB and ensure the interfaces declared in the ejb-ref are correct.

Cause: See the error message for details.

Action: Link or map this ejb-ref to its target EJB and ensure the interfaces declared in the ejb-ref are correct.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160201: Error resolving ejb-ref "{0}" from module "{1}" of application "{2}". The ejb-ref specifies an ejb-link but the target bean does not implement the interface "{3}" as specified in the ejb-ref declaration. Ensure that the ejb-link and interface name(s) declared in the ejb-ref are correct.

Cause: See the error message for details.

Action: Ensure that the ejb-link and interface name(s) declared in the ejb-ref are correct.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160202: You have specified a {1} setting in your configuration for persistence unit {0}. This setting will be ignored and all log messages will be sent to the WebLogic Server logging subsystem. Trace-level logging is controlled by the various JPA-specific debug settings in config.xml, or through the WebLogic Server Administration Console.

Cause: Persistence unit configuration specifies logging information, but WebLogic Server will ignore this information.

Action: Remove the {1} setting from persistence unit {0}.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160203: You have specified a {1} setting in your configuration for persistence unit {0}. This value will be replaced with {1}.

Cause: The persistence unit configuration specifies ID information, but WebLogic Server will ignore this information.

Action: Remove the {1} setting from persistence unit {0}.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160204: The ApplicationLifecycleListener "{1}" of application "{0}" has a run-as user configured with the principal name "{2}" but a principal of that name could not be found. Ensure that a user with that name exists.

Cause: The run-as principal configured for this ApplicationLifecycleListener does not exist in the security realm.

Action: Ensure that the user exists or choose another principal for the run-as configuration.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160205: The ApplicationLifecycleListener "{1}" of application "{0}" has a run-as user configured with the principal name "{2}" but a principal of that name has higher privileges than the user performing the deployment. As a result, this deployment user cannot perform the current deployment action. Try the deployment action with an administrative privileged user.

Cause: Higher run-as privileges are needed to deploy an ApplicationLifecycleListener in this situation.

Action: Try the deployment action with an administrative privileged user.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160207: Error autowiring ejb-ref "{0}" from module "{1}" of application "{2}". The ejb-ref does not specify an interfaceName but multiple interfaces on the target bean were found. Specify a beanInterface to indicate which EJB is the target for ejb-ref "{0}".

Cause: There was a problem resolving the target of the specified ejb-ref.

Action: Specify a beanInterface to indicate which EJB is the target.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160210: ERROR: The moduleUri, "{0}", could not be found.

Cause: The moduleUri could not be found.

Action: Ensure that the specified moduleUri exists and try again.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160211: Waiting for ExecuteQueue {0} to finish {1} pending requests

Cause: The server found pending requests in one of the execute queues while suspending. The server will wait for the requests to complete.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: J2EE

BEA-160212: This is an unexpected exception.

Cause: This is an internal error.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160213: * This directory contains internal files used by the deployment system. * Contents of this directory should never be removed while the corresponding server is running. * Removing sub-directories when the server is down will slow down the subsequent deployment of the corresponding applications because these sub-directories need to be created again. * The individual sub-directories are removed when the corresponding application is undeployed.

Cause: TBD

Action: TBD
Level: 1

Type: NOTIFICATION

Impact: J2EE

BEA-160214: Output location exists {0}

Cause: The file pointed to by the output location already exists,

Action: No action is required.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160215: ERROR: The moduleUri, "{0}", is not Web module.

Cause: The moduleUri is not valid Web module.

Action: Ensure that the specified moduleUri is a valid Web module and try again.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160216: Unexpected errors occurred while sending deployment event {1} on behalf of application ''{0}''.

Cause: The deployment event listener(s) registered to receive deployment event caused unexpected exceptions when processing deployment event {1} on behalf of application ''{0}''.

Action: Report this problem to My Oracle Support.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160217: Unexpected errors occurred while sending a vetoable deployment event on behalf of application ''{0}''.

Cause: The deployment event listener(s) registered to receive vetoable deployment events caused unexpected exception(s) when processing deployment event {1} on behalf of application ''{0}''.

Action: Report this problem to My Oracle Support.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160218: Filtering classloader configuration ignored for module {1} of application {0}

Cause: Filtering classloader configuration is only supported in descriptors at the main level of the deployment (for example, in enterprise applications or standalone Web applications). Such configuration is not supported in modules of an enterprise application.

Action: Remove the filtering classloader configuration from the deployment descriptor of module {1} of application {0}.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160219: The JPA persistence unit {0} will use the following configured default persistence provider: {1}

Cause: No provider element was specified in the associated persistence.xml file.

Action: No action is required unless you want a different JPA provider to be used for the given persistence unit, in which case you can specify the provider in the persistence.xml file or change the default provider for the domain.
Level: 1

Type: NOTIFICATION

Impact: J2EE

BEA-160220: Compilation completed successfully.

Cause: The compilation task has completed successfully.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: J2EE

BEA-160221: env-entry for type java.lang.Character had length = 0.

Cause: See the error message body.

Action: See the error message body.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160222: Could not create a new JMS ConnectionFactory for the application: {0}.

Cause: See the error message body.

Action: See the error message body.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160223: The resource-env-ref ''{0}'' declared in the standard descriptor or annotation has no JNDI name mapped to it. The resource-env-ref must be mapped to a JNDI name using the resource-env-description element of the weblogic proprietary descriptor or corresponding annotation.

Cause: See the error message body.

Action: See the error message body.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160224: Encountered an error cleaning up references for application: ${0} - ${1}

Cause: See the error message body.

Action: See the error message body.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160225: JPA 2.0 API methods cannot be invoked on JPA 1.0 persistence provider. Update the application to use a JPA 2.0 compliant provider, such as EclipseLink, or ensure that the application does not attempt to invoke JPA 2.0 methods.

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

Action: Update your application to use a JPA 2.0 compliant persistence provider, such as EclipseLink, or modify the application to ensure that only JPA 1.0 API methods are invoked.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160226: Ignoring the configuration file [{0}: {1}]. Only applications that use Kodo as the JPA provider can be configured with this file.

Cause: This file can configure only persistence units that use Kodo.

Action: Remove the configuration file or specify the information in persistence.xml; otherwise, one or more persistence units in this application use Kodo.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160227: The persistence unit "{0}" in "{1}" does not use Kodo as a JPA provider. Ignoring the configuration for this persistence unit found in persistence-configuration.xml.

Cause: The persistence-configuration.xml file cannot configure persistence units that do not use Kodo.

Action: Remove the persistence unit from the persistence-configuration.xml file or specify in persistence.xml, or otherwise, that the persistence unit uses Kodo.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160228: AppMerge failed to merge your application. If you are running AppMerge on the command-line, merge again with the -verbose option for more details. See the error message(s) below.

Cause: AppMerge can fail for many reasons. See the specific error message for details.

Action: Use the provided error message to track down and fix the problem. If you believe the error is due to a bug in WebLogic Server, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160229: Ignoring plan file {0} as does not exist.

Cause: Either the plan specified is not a file or the plan file does not exist.

Action: Use the provided error message to track down and fix the problem. If you believe the error is due to a bug in WebLogic Server, contact My Oracle Support.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160230: Created working directory: {0}

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: J2EE

BEA-160231: Unable to identify application type for {0}

Cause: The source file type may not be supported.

Action: Use the provided error message to track down and fix the problem. If you believe the error is due to a bug in WebLogic Server, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160232: Unable to identify module type for {0}

Cause: The module specified in the application descriptor may not be supported.

Action: Use the provided error message to track down and fix the problem. If you believe the error is due to a bug in WebLogic Server, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160233: Unable to identify module type

Cause: A module specified in the application descriptor may not be supported.

Action: Use the provided error message to track down and fix the problem. If you believe the error is due to a bug in WebLogic Server, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160238: The message-destination {0} declared in the deployment descriptor or by annotation does not have a corresponding message-destination-descriptor element in the weblogic deployment descriptor or corresponding annotation. Alternatively, mapped-name or lookup-name of message-destination can be specified for the destination.

Cause: A declared message-destination is not mapped correctly.

Action: Map the declared message-destination to the actual message destination using the message-destination-descriptor element in the weblogic deployment descriptor, or specify mapped-name or lookup-name of message-destination.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160239: Conflicting environment entry {0}, name is {1}.

Cause: They have same environment entry name, but have different value.

Action: Make sure they have different environment entries names. Or have same names with identical values.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160240: The resource-ref ''{0}'' declared in the standard descriptor or annotation has no JNDI name mapped to it. The resource-ref must be mapped to a JNDI name using the resource-description element of the weblogic proprietary descriptor or corresponding annotation.

Cause: See the error message body.

Action: See the error message body.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160241: Error: There are environment entries conflict in module {0}. Multiple environment entries are defined with the same name but different values. {1}

Cause: With an EJB in WAR files, it is possible that environment entries names may clash. Care must be taken by the deployer or application assembler to avoid these name collisions, as they can cause the application to fail.

Action: Make sure they have different environment entries names. Or have same names with identical values.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160242: Warning: Data source definition {0} in interceptor {1} may have been overwritten by EJB component in module {2}, ignored.

Cause: EJB component may overwrite data source definitions in its interceptors. In this case, data source definitions in interceptors will be ignored.

Action:
Level: 1

Type: WARNING

Impact: J2EE

BEA-169800: A PooledConnectionFactory object with an invalid external version of {0} was found.

Cause: The version of WebLogic Server that stored the PooledConnectionFactory object is not compatible with the version that is retrieving it.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSPool

BEA-169801: The JMS method {0} may not be called inside an EJB or servlet.

Cause: The application code has violated the J2EE specifications.

Action: Change the code to avoid calling the specified method.
Level: 1

Type: ERROR

Impact: JMSPool

BEA-169802: Cannot create a wrapped JMS connection using a username and password when the res-auth element is set to Container.

Cause: The application code is not using the J2EE APIs properly.

Action: Either remove the username and password, or set the res-auth element to Application.
Level: 1

Type: ERROR

Impact: JMSPool

BEA-169803: JNDI lookup of the JMS connection factory {0} failed

Cause: The remote JNDI server or JMS server is not available, or the name was incorrectly specified.

Action: Check that the server is running, and check the name in the deployment descriptor XML files.
Level: 1

Type: ERROR

Impact: JMSPool

BEA-169804: Cannot use a JMS connection factory because the object is of the wrong type.

Cause: Either the name of the connection factory in the deployment descriptor XML files is wrong, or the wrong object was bound into JNDI.

Action: Check the name in the XML files against what is actually registered in JNDI.
Level: 1

Type: ERROR

Impact: JMSPool

BEA-169805: A pooled JMS connection is being closed because an error was detected on the connection: {0}

Cause: The JMS server is unavailable or there is some other problem with it that makes it impossible to send or receive messages.

Action: Check the configuration parameters for the JMS server, and check that it is available on the network.
Level: 1

Type: ERROR

Impact: JMSPool

BEA-169806: Cannot use a JMS destination because the object is of the wrong type.

Cause: Change the application to use a valid destination type.

Action: Change the application to use a valid destination type.
Level: 1

Type: ERROR

Impact: JMSPool

BEA-169807: There was an error while making the initial connection to the JMS resource named {0} from within an EJB or a servlet. The server will attempt the connection again later. The error was {1}

Cause: See the error message from the JMS provider.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JMSPool

BEA-169808: There was an error while making the initial connection to the JMS resource named {0} from the EJB "{1}" inside application "{2}". The server will attempt the connection again later. The error was {3}

Cause: See the error message from the JMS provider.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JMSPool

BEA-169809: An error occurred while registering the JMS connection with JTA.

Cause: The JMS connection factory specified does not properly support XA or something is wrong with the transaction system.

Action: Check the linked exception and verify that the JMS provider properly supports XA.
Level: 1

Type: ERROR

Impact: JMSPool

BEA-169810: An error occurred while committing or rolling back a JTA transaction used for a JMS operation by the J2EE container

Cause: There was a problem with the transaction system.

Action: See the linked exception for more information.
Level: 1

Type: ERROR

Impact: JMSPool

BEA-169811: The JMS object may not be used because it has been closed.

Cause: The object has been closed.

Action: Fix the programming error.
Level: 1

Type: ERROR

Impact: JMSPool

BEA-169812: The pooled JMS session is enlisted in another transaction and may not be used elsewhere.

Cause: Check the application code to ensure that a pooled JMS session (retrieved from the JNDI java:comp/env/jms context) is not kept between transactions. It should be closed so that it is returned to the pool.

Action: Check the application code.
Level: 1

Type: ERROR

Impact: JMSPool

BEA-169813: There was an error while closing a JMS session pool or a pooled JMS connection: {0} The pool or object was forcibly closed.

Cause: See the linked exception for more information.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JMSPool

BEA-169814: The JMS session pool has been disabled.

Cause: An administrative action was taken.

Action: Re-enable the session pool.
Level: 1

Type: ERROR

Impact: JMSPool

BEA-169815: A JMS session pool could not be created because the {0} property was not specified.

Cause: If the JMSSessionPool class is not being used directly by the user, then this is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSPool

BEA-169816: The JMS session pool is shutting down.

Cause: The pool is being shut down, possibly because of an error.

Action: Check for other errors that indicate why the pool is being shut down and retry the operation.
Level: 1

Type: ERROR

Impact: JMSPool

BEA-169817: The JMS connection factory resource {0} declared in the EJB "{1}" as part of application "{2}" does not support XA. It cannot be used inside a transaction context.

Cause: If the specified JMS connection factory is intended to be used inside a transaction context, then the EJB was configured improperly.

Action: If the specified JMS connection factory is intended for use inside a transaction context, then the connection factory used by the EJB must be changed so that it supports XA, or the EJB descriptor must be changed to point to a different connection factory. However, if the connection factory will never be used inside a transaction context, then no action is necessary.
Level: 1

Type: WARNING

Impact: JMSPool

BEA-169818: The JMS connection pool named "{0}" has a configured connection factory JNDI name of "{1}". However, an object that is not a javax.jms.ConnectionFactory is bound to that JNDI name. The object bound to that JNDI name has type "{2}".

Cause: An object other than a ConnectionFactory is bound to the configured JNDI name of the connection pool.

Action: Either change the JNDI name of the JMS connection pool property or change the JNDI name of the object that is currently bound into JNDI.
Level: 1

Type: WARNING

Impact: JMSPool

BEA-169819: There was an error with a resource pool used to pool JMS sessions

Cause: There is a problem with the resource pool.

Action: See the linked exception for details.
Level: 1

Type: ERROR

Impact: JMSPool

BEA-169820: A JMS message consumer could not be created using a temporary queue or topic that was created using another connection.

Cause: This is an application programming error.

Action: Change the application code.
Level: 1

Type: ERROR

Impact: JMSPool

BEA-169821: Error creating or instantiating a wrapper for class {0}

Cause: There may be an error with the classpath or with the underlying JMS provider's code.

Action: Check the classpath. If this does not fix the problem, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSPool

BEA-169822: Unable to use a wrapped JMS session in the transaction because two-phase commit is not available.

Cause: The JMS connection factory specified does not support two-phase commit.

Action: For WebLogic Server JMS, two-phase commit may be enabled by setting the "UserTransactionsEnabled" flag on the JMS connection factory. For other JMS providers, you must specify a JMS connection factory that supports XA.
Level: 1

Type: ERROR

Impact: JMSPool

BEA-169823: Failure occured on createQueueConnection. Unexpected return type.

Cause: Probable cause is the JMS 1.1 ConnectionFactory with the JMS 1.0.2 createQueueConnection() API. Some JMS providers do not support backward compatibility.

Action: Either change the API call to createConnection() or change the connection factory type to QueueConnectionFactory.
Level: 1

Type: ERROR

Impact: JMSPool

BEA-169824: Failure occured on createTopicConnection. Unexpected return type.

Cause: Probable cause is the JMS 1.1 ConnectionFactory with the JMS 1.0.2 createTopicConnection() API. Some JMS providers do not support backward compatibility.

Action: Either change the API call to createConnection() or change the connection factory type to TopicConnectionFactory.
Level: 1

Type: ERROR

Impact: JMSPool

BEA-170003: The DomainLogfile Handler is unable to open the domain logfile {0}. The domain logfile is disabled.

Cause: The filepath specified for the domain log is invalid or the server process cannot write to the domain log file.

Action: Specify a valid filepath for the domain log file.
Level: 1

Type: INTERNAL_ERROR

Impact: Log Management

BEA-170011: The LogBroadcaster on this server failed to broadcast log messages to the Administration Server. The Administration Server may not be running. Message broadcasts to the Administration Server will be disabled.

Cause: The Managed Server may not be able to reach the Administration Server. One of the possible causes could be that the Administration Server is shut down.

Action: To fix this problem, inspect the exception stack trace, and correct the problem. If the Administration Server is shut down, restart it to resume normal log broadcasting to the domain.
Level: 1

Type: WARNING

Impact: Log Management

BEA-170019: The server log file {0} is opened. All server side log events will be written to this file.

Cause: This message is for informational purposes.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: Log Management

BEA-170020: The server log file {0} could not be opened successfully.

Cause: The filepath configured for the server's log file is not valid.

Action: Please specify a valid filepath for the server's log file.
Level: 1

Type: ERROR

Impact: Log Management

BEA-170022: Log4j failed to initialize for {0}. The default JDK Logging implementation will be used.

Cause: The Log4j libraries may not be in the server CLASSPATH.

Action: Take corrective action based on the stack trace details.
Level: 1

Type: ERROR

Impact: Log Management

BEA-170023: The Server Logging is initialized with Java Logging API implementation.

Cause: This message is for informational purposes.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: Log Management

BEA-170024: The Server Logging is initialized with Apache's Log4j Logging API implementation.

Cause: This message is only for informational purposes.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: Log Management

BEA-170025: Initialized Domain Logging. Domain log events will be written to {0}.

Cause: This message is for informational purposes.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: Log Management

BEA-170027: The server has successfully established a connection with the Domain level Diagnostic Service.

Cause: The server has successfully established contact with the Domain Diagnostic Service.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: Log Management

BEA-170028: The remote handler is not available, so the trap notification information can not be sent.

Cause: The Managed Server may not be able to reach the Administration Server. One of the possible causes could be that the Administration Server is shut down.

Action: If the Administration Server is shut down, restart it to resume normal communication for the domain.
Level: 1

Type: ERROR

Impact: Log Management

BEA-170029: The data gathering handler could not be initialized.

Cause: An error occurred while initializing the data gathering handler.

Action: Review the nested exception details for the cause.
Level: 1

Type: WARNING

Impact: Log Management

BEA-170030: There was an error initializing the global Log4j configuration.

Cause: The error could be due to incorrect configuration parameters in the log4j configuration file.

Action: Review the nested exception details for the cause.
Level: 1

Type: ERROR

Impact: Log Management

BEA-170031: The default Server Logging bridge has been initialized successfully.

Cause: This message is logged for informational purpose only.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: Log Management

BEA-171500: The embedded LDAP configuration file: {0} was not found, and the embedded LDAP server has not been started. To resolve the problem, ensure that weblogic.home is defined correctly (it should have a lib subdirectory that contains this file).

Cause: The embedded LDAP server cannot find the specified file. This file is installed as part of the installation process. Most likely, the default directory is not the server root directory and the lib subdirectory cannot be found.

Action: Set the default directory to the server root directory, or use the weblogic.EmbeddedLDAPConfigDirectory system property to set the location of the embedded LDAP server configuration files.
Level: 1

Type: ERROR

Impact: EmbeddedLDAP

BEA-171503: The listen address for the Administration Server is obtained from either the Server MBean, the ServerRuntime MBean, or the URL specified by the weblogic.management.server command line property. None of these returned a listen address.

Cause: The listen address was null.

Action: Check if the listen address for the Administration Server is defined in either the Server MBean, the ServerRuntime MBean, or the URL specified by the weblogic.management.server command line property.
Level: 1

Type: ERROR

Impact: EmbeddedLDAP

BEA-171507: The embedded LDAP replica file: {0} could not be written. The underlying exception was {1}.

Cause: An exception occurred when saving the replica properties to the replicas file.

Action: Verify that the file {1} can be written. Read the exception text for more information in diagnosing the problem.
Level: 1

Type: ERROR

Impact: EmbeddedLDAP

BEA-171512: When attempting to clean up after a failed embedded LDAP replica initialization, the file {0} could not be deleted. The {1} directory and all its files must be deleted manually.

Cause: It is not always possible to delete files that are open by a process.

Action: Delete the {1} directory and all its files manually using the appropriate command for the operating system on which WebLogic Server runs.
Level: 1

Type: INTERNAL_ERROR

Impact: EmbeddedLDAP

BEA-171513: Could not schedule the trigger used for embedded LDAP timer activities. The underlying exception was {0}.

Cause: A TimeTrigger exception occurred when scheduling the trigger.

Action: See the exception text in {0} for more information on diagnosing the problem.
Level: 1

Type: INTERNAL_ERROR

Impact: EmbeddedLDAP

BEA-171517: An error occurred while attempting to obtain exclusive access to the embedded LDAP data files directory: {0}. The exception that occurred is {1}.

Cause: An exclusive lock for the directory {0} could not be obtained because an exception occurred.

Action: Investigate the associated exception to determine why the exclusive lock failed.
Level: 1

Type: INTERNAL_ERROR

Impact: EmbeddedLDAP

BEA-171518: The following exception has occurred:

Cause: An error condition has occurred.

Action: Read the associated exception in the log. In general, a stack trace will help when debugging an existing problem.
Level: 1

Type: NOTIFICATION

Impact: EmbeddedLDAP

BEA-171519: Could not obtain an exclusive lock to the embedded LDAP data files directory: {0} because another WebLogic Server instance is already using this directory. Ensure that the first WebLogic Server instance is completely shut down and restart the server.

Cause: An exclusive lock for the directory {0} could not be obtained because another WebLogic Server is already using this directory.

Action: Ensure that the first WebLogic Server instance is shut down and try restarting the server.
Level: 1

Type: ERROR

Impact: EmbeddedLDAP

BEA-171520: Could not obtain an exclusive lock for directory: {0}. Waiting for {1} seconds and then retrying in case the existing WebLogic Server instance is still shutting down.

Cause: An exclusive lock for the directory {0} could not be obtained because another WebLogic Server is already using this directory.

Action: If the server eventually boots, ignore this warning as the lock was obtained. If the server fails to boot, ensure that the first WebLogic Server is shut down and try restarting the server.
Level: 1

Type: WARNING

Impact: EmbeddedLDAP

BEA-171521: An error occurred while initializing the embedded LDAP server. The exception that occurred is {0}. This may indicate a problem with the data files for the embedded LDAP server. This Managed Server has a replica of the data contained on the master embedded LDAP server in the Administration Server. This replica has been marked invalid and will be refreshed on the next boot of the Managed Server. Try to reboot this server.

Cause: There may be a problem with either the embedded LDAP server configuration files or the data files.

Action: Investigate the associated exception to determine why the exception occurred. Try to reboot the server and see if the refresh of the replica data files solves the problem.
Level: 1

Type: INTERNAL_ERROR

Impact: EmbeddedLDAP

BEA-171522: An error occurred while initializing the embedded LDAP server. The exception that occurred is {1}. This may indicate a problem with the data files for the embedded LDAP server. If the problem is with the data files, and it cannot be corrected, backups of previous versions of the data files exist in {0}.

Cause: There may be a problem with either the embedded LDAP server configuration files or the data files.

Action: Investigate the associated exception to determine why the exception occurred. Try to reboot the server.
Level: 1

Type: INTERNAL_ERROR

Impact: EmbeddedLDAP

BEA-171523: Embedded LDAP server Credential unavailable: a credential value must be supplied for the embedded LDAP configuration.

Cause: The Credential attribute is invalid.

Action: Set the Credential attribute for the embedded LDAP server configuration.
Level: 1

Type: ERROR

Impact: EmbeddedLDAP

BEA-171524: Cannot determine the listen address for the Administration Server. The Administration Server URI {0}, obtained from either the Server MBean, the ServerRuntime MBean, or the URL specified by the weblogic.management.server command line property, has invalid syntax.

Cause: The Administration Server URI has invalid syntax.

Action: Ensure that a valid listen address for the Administration Server is defined in either the Server MBean, the ServerRuntime MBean, or the URL specified by the weblogic.management.server command line property.
Level: 1

Type: ERROR

Impact: EmbeddedLDAP

BEA-171525: Error loading initial replica file. Check the EmbeddedLDAP log for more details.

Cause: An error occurred during the loading of the initial replica file.

Action: Check the EmbeddedLDAP log for more details.
Level: 1

Type: ERROR

Impact: EmbeddedLDAP

BEA-171526: Error loading the initial replica file, attempting to reload.

Cause: An error occurred during the loading of the initial replica file.

Action: No action is required. The initial replica file will be loaded again.
Level: 1

Type: NOTIFICATION

Impact: EmbeddedLDAP

BEA-171527: Added all LDAP entries successfully for the initial replica.

Cause: An error occurred during the initial loading of the replica file.

Action: No action is required. The reload of the initial replica file was successful.
Level: 1

Type: NOTIFICATION

Impact: EmbeddedLDAP

BEA-180000: Start parsing the configuration MBean information.

Cause: All other initialization has completed, and this method is now ready to begin reading its own configuration information.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WTC

BEA-180001: WTC finished parsing the configuration MBean information.

Cause: All WTC configuration MBeans were parsed without any problems.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WTC

BEA-180002: Invalid attributes exception occurred while trying to create subcontext: {0}

Cause: An attempt was made to add an attribute set that has been specified incompletely or incorrectly.

Action: This is an internal error. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: WTC

BEA-180003: Naming exception error: {0}

Cause: The specified name could not be resolved.

Action: This is an internal error. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: WTC

BEA-180004: Name already bound error: {0}

Cause: The name used by the Tuxedo connection factory or Tuxedo CORBA connection factory already bonded to another object.

Action: Do not use the same name as the Tuxedo or Tuxedo CORBA connection factory.
Level: 1

Type: ERROR

Impact: WTC

BEA-180005: Invalid attributes exception when binding connection factory: {0}

Cause: An attempt was made to add an attribute set that has been specified incompletely or incorrectly.

Action: This is an internal error. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: WTC

BEA-180006: Naming exception error: {0}

Cause: The specified name could not be resolved.

Action: This is an internal error. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: WTC

BEA-180007: Unable to register the resource with transaction manager: {0}.

Cause: WebLogic Tuxedo Connector (WTC) was not running with the server transaction manager.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: WTC

BEA-180008: A transaction identifier exists for a non-existent domain {0}.

Cause: The remote Tuxedo domain involved in the transaction is no longer in the WebLogic Tuxedo Connector (WTC) configuration.

Action: Manually correct the transaction. If the removal of the remote Tuxedo domain is intentional, temporarily add the remote Tuxedo domain back to the configuration and wait for the transaction to complete. Otherwise, add the Tuxedo domain back to the configuration.
Level: 1

Type: ERROR

Impact: WTC

BEA-180009: Could not complete the execution for the MBean named: {0}.

Cause: The definition contains input information that is not consistent with the usage model.

Action: Check the MBean definition to see if the individual attributes are consistent with the rest of the MBean definitions.
Level: 1

Type: ERROR

Impact: WTC

BEA-180010: Could not create a TDMLocalTDomain {0}.

Cause: The AccessPoint attribute definition for the WTCLocalTuxDom MBean was invalid.

Action: Check the AccessPoint attribute of the WTCLocalTuxDom MBean.
Level: 1

Type: ERROR

Impact: WTC

BEA-180011: Could not create a TDMRemoteTDomain {0}.

Cause: The AccessPoint attribute definition for the WTCRemoteTuxDom MBean was invalid.

Action: Check the AccessPoint attribute of the WTCRemoteTuxDom MBean.
Level: 1

Type: ERROR

Impact: WTC

BEA-180012: The LocalTDomain {0} is unknown.

Cause: The LocalAccessPoint attribute for the WTCRemoteTuxDom MBean is not a valid name for a LocalTDomain.

Action: Verify that the WTCRemoteTuxDom MBean definition has a valid name for the LocalAccessPoint attribute.
Level: 1

Type: ERROR

Impact: WTC

BEA-180013: The LocalTDomain {0} is unknown.

Cause: The LocalAccessPoint attribute for the WTCExport MBean is not a valid name for a LocalTDomain.

Action: Verify that the WTCExport MBean definition has a valid name for the LocalAccessPoint attribute.
Level: 1

Type: ERROR

Impact: WTC

BEA-180014: Could not create a TDMExport {0}.

Cause: The ResourceName attribute definition for the WTCExport MBean is invalid or the LocalTDomain is not usable.

Action: Check the ResourceName attribute of the WTCExport MBean.
Level: 1

Type: ERROR

Impact: WTC

BEA-180015: The LocalTDomain {0} is not known.

Cause: The LocalAccessPoint attribute for the WTCImport MBean is not a valid name for a LocalTDomain.

Action: Confirm that the WTCImport MBean definition has a valid name for the LocalAccessPoint Attribute.
Level: 1

Type: ERROR

Impact: WTC

BEA-180016: The RemoteTDomain {0} is unknown.

Cause: The RemoteAccessPointList attribute for the WTCImport MBean does not contain a valid name for a RemoteTDomain.

Action: Verify that the WTCImport MBean definition has valid names in a comma-separated list defined in the RemoteAccessPointList attribute.
Level: 1

Type: ERROR

Impact: WTC

BEA-180017: Could not create a TDMImport {0}.

Cause: The ResourceName attribute definition for the WTCImport MBean is invalid. The LocalTDomain or the RemoteTDomains are not usable.

Action: Check the ResourceName attribute of the WTCImport MBean.
Level: 1

Type: ERROR

Impact: WTC

BEA-180018: Missing {0} Password or PasswordIV information.

Cause: The Password or PasswordIV attribute is not set.

Action: Verify that the Password and PasswordIV attributes are valid.
Level: 1

Type: ERROR

Impact: WTC

BEA-180019: The LocalTDomain {0} is unknown.

Cause: The LocalAccessPoint attribute for the WTCPassword MBean is not a valid name for a LocalTDomain.

Action: Verify that the WTCPassword MBean definition has a valid name for the LocalAccessPoint attribute.
Level: 1

Type: ERROR

Impact: WTC

BEA-180020: The RemoteTDomain {0} is unknown.

Cause: The RemoteAccessPoint attribute for the WTCPassword MBean is not a valid name for a RemoteTDomain.

Action: Verify that the WTCPassword MBean definition has a valid name for the RemoteAccessPoint attribute.
Level: 1

Type: ERROR

Impact: WTC

BEA-180021: Could not create a TDMPasswd {0}.

Cause: The LocalTDomain or the RemoteTDomain is not usable.

Action: Check the LocalAccessPoint and RemoteAccessPoint attributes of the WTCPassword MBean.
Level: 1

Type: ERROR

Impact: WTC

BEA-180022: Could not set up the field table information for TDMResources: {0}.

Cause: The fully qualified name for any field table may be incorrect or could not be found.

Action: Check the FldTblClass definitions of the WTCResources MBean and verify that the fully qualified name is correct, that it is consistent with the current CLASSPATH usage, and that the system is able to access it.
Level: 1

Type: ERROR

Impact: WTC

BEA-180023: Commit of Xid failed with status {0}.

Cause: The transaction became a heuristic hazard, or the resource manager encountered an error.

Action: Correct the transaction manually if it became a heuristic hazard, or correct the resource manager problem.
Level: 1

Type: ERROR

Impact: WTC

BEA-180024: Unable to reply to unknown transaction with exception: {0}.

Cause: The connection to the remote Tuxedo domain was already terminated or an IOException occurred while writing to the network.

Action: If the TPException is TPEPROTO, try to reboot the remote Tuxedo domain. If the TPException is TPESYSTEM, check the network connection.
Level: 1

Type: ERROR

Impact: WTC

BEA-180025: Unknown field type requested {0}.

Cause: TypedFML32 data is possibly being used instead of TypedFML.

Action: Verify that the type of input data is correct.
Level: 1

Type: ERROR

Impact: WTC

BEA-180026: While trying to use FML data, this Ferror exception occurred: {0}

Cause: The data was not created correctly.

Action: Check the data that was passed into this method.
Level: 1

Type: ERROR

Impact: WTC

BEA-180027: While trying to use FML data, an Unknown exception occurred: {0}

Cause: The data was not created correctly.

Action: Check the data that was passed into this method.
Level: 1

Type: ERROR

Impact: WTC

BEA-180028: Unknown field type requested {0}.

Cause: Possibly, TypedFML data is being used instead of TypedFML32.

Action: Verify that the type of input data was correct.
Level: 1

Type: ERROR

Impact: WTC

BEA-180029: The Ferror exception: {0} occurred. Additional exception information found: {1}.

Cause: The data was not created correctly.

Action: Check the data that was passed into this method.
Level: 1

Type: ERROR

Impact: WTC

BEA-180030: While trying to use FML32 data, an Unknown exception occurred: {0}

Cause: The data was not created correctly.

Action: Check the data that was passed into this method.
Level: 1

Type: ERROR

Impact: WTC

BEA-180031: XML argument is null.

Cause: The argument that was passed in was not initialized.

Action: Check the XML argument that was passed in.
Level: 1

Type: ERROR

Impact: WTC

BEA-180032: The FldTbl[] input argument is null or an empty array.

Cause: The argument that was passed in was not initialized.

Action: Check the FldTbl[] argument that was passed in.
Level: 1

Type: ERROR

Impact: WTC

BEA-180033: TypedFML argument is null.

Cause: The argument that was passed in was not initialized.

Action: Check the TypedFML argument that was passed in.
Level: 1

Type: ERROR

Impact: WTC

BEA-180034: An error occurred while searching {0} for the document root element.

Cause: The input XML string was not formatted correctly.

Action: Check for other listed errors that should indicate what was unacceptable about the XML input.
Level: 1

Type: ERROR

Impact: WTC

BEA-180035: TypedFML32 argument is null.

Cause: The argument that was passed in was not initialized.

Action: Check the TypedFML32 argument that was passed in.
Level: 1

Type: ERROR

Impact: WTC

BEA-180036: XML input {0} caused the SAX parser exception {1}

Cause: The Document Object Model (DOM) parser did not accept the XML string that it received.

Action: Check the SAX exception information that was returned and the XML string that was entered.
Level: 1

Type: ERROR

Impact: WTC

BEA-180037: XML input {0} caused IOException {1}.

Cause: The XML string was not convertible to an InputSource() class.

Action: Check the IOException information that was returned and the XML string that was entered.
Level: 1

Type: ERROR

Impact: WTC

BEA-180038: XML input {0} caused an unknown exception {1}.

Cause: The XML string was not able to be parsed.

Action: Check the exception information that was returned and the XML string that was entered.
Level: 1

Type: ERROR

Impact: WTC

BEA-180039: The DOM parser returned a null value for input {0}.

Cause: The input may not be a valid XML string.

Action: Check the string that was passed to the parser.
Level: 1

Type: ERROR

Impact: WTC

BEA-180040: Could not obtain a top document element from input {0}.

Cause: The XML input did not have any elements defined.

Action: Verify that the input string has a proper definition for a root element.
Level: 1

Type: ERROR

Impact: WTC

BEA-180041: Could not obtain a tag name for the root element in XML input {0}.

Cause: The XML input does not have a tag name for the root element.

Action: Verify that the root element has a proper definition.
Level: 1

Type: ERROR

Impact: WTC

BEA-180042: Internal TypedFML data is null.

Cause: The internal data that is using the XMLtoFML() API was not initialized.

Action: Use XMLtoFML to initialize the internal data.
Level: 1

Type: ERROR

Impact: WTC

BEA-180043: XML element name is null.

Cause: The XML element information was not properly defined.

Action: Check the XML element definition.
Level: 1

Type: ERROR

Impact: WTC

BEA-180044: XML element value is null for the element name {0}.

Cause: The XML element information was not properly defined.

Action: Check the XML element definition.
Level: 1

Type: ERROR

Impact: WTC

BEA-180045: Internal TypedFML32 data is null.

Cause: The internal data that was using the XMLtoFML32() API was not initialized.

Action: Use XMLtoFML32 to initialize the internal data.
Level: 1

Type: ERROR

Impact: WTC

BEA-180047: The tBridge must have at least one redirect command.

Cause: The tBridge was not configured properly.

Action: At least one redirect command must be configured in the WTC_CONFIG for the tBridge section.
Level: 1

Type: ERROR

Impact: WTC

BEA-180048: The tBridge cannot find the TuxedoConnectionFactory.

Cause: The WebLogic Tuxedo Connector (WTC) was not properly configured.

Action: Review the WTC documentation and restart the WTC.
Level: 1

Type: ERROR

Impact: WTC

BEA-180049: The tBridge cannot locate the WLXT option for translation.

Cause: The WLXT package might not be loaded or might be in the proper CLASSPATH.

Action: Install the WLXT and properly configure the translator option.
Level: 1

Type: ERROR

Impact: WTC

BEA-180050: The tBridge internal FML-to-XML conversion failed.

Cause: The syntax of the incoming message could not be understood.

Action: Correct the message syntax and retry.
Level: 1

Type: ERROR

Impact: WTC

BEA-180052: Unable to cancel ON_STARTUP connection retry due to: {0}.

Cause: The timer service object for the ON_STARTUP connection policy could not be deleted during connection termination.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: WTC

BEA-180053: Failure occurred during the token creating token: {0}.

Cause: This is an internal error.

Action: Contact My Oracle Support to report this problem with the token type information found in the log message.
Level: 1

Type: ERROR

Impact: WTC

BEA-180054: Failure occurred while reading the received domain security token: {0}.

Cause: This is an internal error.

Action: Contact My Oracle Support to report this problem with the token type information found in the log message.
Level: 1

Type: ERROR

Impact: WTC

BEA-180055: Received an unexpected token type, error information({0}, {1}, {2}).

Cause: The cause could be that WTC communicates with a newer version of the TDomain protocol or an unknown alien protocol, or a breach of security attempt was detected.

Action: Verify who is trying to connect to this WTC and determine whether there is a security violation or a need to upgrade WTC to a newer version.
Level: 1

Type: ERROR

Impact: WTC

BEA-180056: atntd(1) crypto error: {0}

Cause: There was not enough free memory space to continue, or an internal error occurred.

Action: Try to force garbage collection, and remove some services to reduce memory usage. If the problem persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: WTC

BEA-180057: Invalid return challenge

Cause: This is caused by an incorrect configuration and mismatched password.

Action: Correct the configuration and the password.
Level: 1

Type: ERROR

Impact: WTC

BEA-180058: atntd(3) I/O error: {0}

Cause: This is an internal system error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: WTC

BEA-180059: atntd(2) crypto error: {0}

Cause: There is not enough free memory space to continue, or an internal error occurred.

Action: Try to force garbage collection, and remove some services to reduce memory usage. If the problem persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: WTC

BEA-180063: Invalid handler address length: {0}.

Cause: The client did not talk to a valid listener.

Action: Check the listener address and correct the configuration.
Level: 1

Type: ERROR

Impact: WTC

BEA-180067: WSRPCRQ discriminator {0} is invalid.

Cause: The client is not talking to a valid handler.

Action: Check the configuration and correct the error.
Level: 1

Type: ERROR

Impact: WTC

BEA-180068: Invalid WSRPCRQ type {0}.

Cause: The client is not talking to a valid handler.

Action: Check the configuration and correct it.
Level: 1

Type: ERROR

Impact: WTC

BEA-180069: Unable to read {0}. The following exception occurred: {1}.

Cause: A general I/O exception occurred.

Action: Read the exception description to determine the actual cause and act accordingly.
Level: 1

Type: ERROR

Impact: WTC

BEA-180070: TypeFML32 received a pointer of unknown type {0}. Will replace with null.

Cause: The application was incorrectly written with an unknown data type.

Action: Correct the data type in the application.
Level: 1

Type: WARNING

Impact: WTC

BEA-180071: Invalid typed FML32 field {0}. Equals null.

Cause: The embedded FML32 buffer was incorrectly constructed in the FML32 buffer.

Action: Check the source of the embedded FML32 buffer, and correct the problem.
Level: 1

Type: WARNING

Impact: WTC

BEA-180074: The tpinit buffer was not received.

Cause: The server is likely talking to an invalid handler.

Action: Check the configuration and correct the problem.
Level: 1

Type: ERROR

Impact: WTC

BEA-180075: Invalid receive size {0}

Cause: The remote tuxedo domain gateway is not valid.

Action: Check the configuration of the remote Tuxedo domain and correct the error.
Level: 1

Type: ERROR

Impact: WTC

BEA-180076: Unable to format password. The following exception occurred: {0}.

Cause: An I/O error occurred.

Action: Check for system memory usage and see if force garbage collection is possible. If the problem persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: WTC

BEA-180077: Unable to close the domain socket. The following exception occurred: {0}.

Cause: An I/O error occurred while closing the socket.

Action: Check the network and system environment. If the problem persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: WTC

BEA-180078: Dropping OWS_AREPLY on ground.

Cause: The ACALL request already timed out.

Action: No action is required. This message is informational only.
Level: 1

Type: WARNING

Impact: WTC

BEA-180079: rsession.run read_tfmh failed.

Cause: The received message header is not properly formatted or it failed to decompress the data.

Action: Check the configuration of the remote Tuxedo domain and correct any problem in the configuration. Ensure that a supported version of the remote Tuxedo domain is being used. Also, check the network for possible network dropping of the packet. If the problem persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: WTC

BEA-180080: rsession.run tmmsg.ws was not provided.

Cause: There is no connection with a valid remote Tuxedo domain.

Action: Check the remote Tuxedo domain configuration and correct the problem.
Level: 1

Type: ERROR

Impact: WTC

BEA-180081: Unexpected close on rsession socket. The following exception occurred: {0}

Cause: An I/O error occurred while reading the message header from the input stream.

Action: Check the system memory usage and force garbage collection. If the problem persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: WTC

BEA-180082: Unable to close the WSH socket. The following exception occurred: {0}.

Cause: An I/O error occurred.

Action: Check the network and system configuration.
Level: 1

Type: ERROR

Impact: WTC

BEA-180083: An unknown TCM type was received: {0}.

Cause: WebLogic Tuxedo Connector (WTC) is communicating with an unsupported Tuxedo version.

Action: Check the configuration and correct the error.
Level: 1

Type: ERROR

Impact: WTC

BEA-180084: Unable to write TCM. The following exception occurred: {0}.

Cause: An I/O error occurred.

Action: Check the system memory usage and force garbage collection.
Level: 1

Type: ERROR

Impact: WTC

BEA-180085: Unable to send an unsolicited acknowledgment. The following exception occurred: {0}.

Cause: An I/O error occurred.

Action: Check the system memory usage.
Level: 1

Type: ERROR

Impact: WTC

BEA-180086: Accepted connection from the remote domain {0}.

Cause: The connection request was received from a remote domain.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WTC

BEA-180087: Established a connection to a remote domain {0}.

Cause: The connection request to a remote domain was initiated.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WTC

BEA-180088: Error occurred while building {0} message.

Cause: This is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: WTC

BEA-180089: Error occurred while decoding {0} message.

Cause: This is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: WTC

BEA-180090: Remote domain {0} rejected the connection request.

Cause: An error exists in the configuration.

Action: Check both sides of the configuration, including the password, to see whether a mismatch exists in the configuration.
Level: 1

Type: ERROR

Impact: WTC

BEA-180091: Rejected remote domain {0} connection request.

Cause: An error exists in the configuration.

Action: Check both sides of the configuration, including the password, to see whether a mismatch exists in the configuration.
Level: 1

Type: ERROR

Impact: WTC

BEA-180092: Failed security validation with remote domain {0}.

Cause: An error exists in the configuraiton, resulting in unauthorized access.

Action: Check both sides of the configuration, including the password, to see if a mismatch exists in the configuration.
Level: 1

Type: ERROR

Impact: WTC

BEA-180093: Naming exception occurred during the lookup of the administrator name: {0}.

Cause: The specified name could not be resolved.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: WTC

BEA-180094: The tBridge failed to initialize the JMS targetName queue.

Cause: The JMS targetName queue does not exist or the JMS server was not running on the system.

Action: Correct the JMS problem and restart the WebLogic Tuxedo Connector (WTC) tBridge.
Level: 1

Type: ERROR

Impact: WTC

BEA-180095: The tBridge could not initialize the JMS sourceName queue.

Cause: The sourceName queue cannot exist in JMS or the JMS server was not started.

Action: Correct the JMS problem and restart the WebLogic Tuxedo Connector (WTC) tBridge.
Level: 1

Type: ERROR

Impact: WTC

BEA-180096: The tBridge could not initialize the wlsErrorDestination JMS queue.

Cause: The JMS wlsErrorDestination queue may not be properly configured in WebLogic Server.

Action: Correct the JMS problem and restart the WebLogic Tuxedo Connector (WTC) tBridge.
Level: 1

Type: ERROR

Impact: WTC

BEA-180097: Due to a translation error, the tBridge has redirected the message to the wlsErrorDestination.

Cause: A translation error was detected from XML-to-FML or from FML-to-XML.

Action: Correct the message structure and resend the message.
Level: 1

Type: ERROR

Impact: WTC

BEA-180098: The tBridge failed to send the message to wlsErrorDestination.

Cause: The JMS wlsErrorDestination could be full or paused.

Action: Recover the message from the sourceName JMS queue and resend.
Level: 1

Type: ERROR

Impact: WTC

BEA-180099: The MinEncryptionBits is greater then the MaxEncryptionBits in {0} domain {1}.

Cause: There is a configuration error.

Action: Use the WebLogic Server Administration Console to modify the WebLogic Tuxedo Connector (WTC) configuration so that it will use the correct values for the MinEncryptionBits and MaxEncryptionBits.
Level: 1

Type: ERROR

Impact: WTC

BEA-180100: Configuration error: {0}

Cause: There is a configuration error.

Action: Use the WebLogic Server Administration Console to modify the WebLogic Tuxedo Connector (WTC) configuration so that it will use the correct values for the corresponding error.
Level: 1

Type: ERROR

Impact: WTC

BEA-180102: Duplicated local domain ID {0} found.

Cause: Two local domains have the same ID.

Action: Use the WebLogic Server Administration Console to modify the WebLogic Tuxedo Connector (WTC) configuration to use a unique ID for the local domain.
Level: 1

Type: ERROR

Impact: WTC

BEA-180103: There are two remote domains {0} with the same local domain {1}.

Cause: Two remote domains have the same local domain.

Action: Use the WebLogic Server Administration Console to modify the WebLogic Tuxedo Connector (WTC) configuration to remove the redundant entry or correct the configuration information.
Level: 1

Type: ERROR

Impact: WTC

BEA-180104: Unsupported JMS message type

Cause: A JMS Stream or Mapped message type was sent to the tBridge.

Action: Correct the JMS message type and resend.
Level: 1

Type: ERROR

Impact: WTC

BEA-180105: A message has been dropped.

Cause: The most common cause of this failure is that an unrecognized buffer type has been received by the WTC gateway.

Action: Modify the application to ensure that unknown buffer types are not sent to the WTC gateway.
Level: 1

Type: WARNING

Impact: WTC

BEA-180106: Unable to find a transaction manager. Transaction recovery will not continue.

Cause: A transaction manager could not be found.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: WTC

BEA-180107: While attempting to recover transactions, the recover method failed.

Cause: The recover method on the WebLogic Server XA sesource generated an exception.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: WTC

BEA-180108: WebLogic Server rollback had a failure: {0}.

Cause: The rollback method on the WebLogic Server XA resource generated an exception.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: WTC

BEA-180109: Internal FML to XML conversion failed.

Cause: The FML buffer that was received from Tuxedo contained field buffer names that were not provided to WebLogic Tuxedo Connector (WTC). Therefore, the name translation failed.

Action: Verify that the field tables have been properly transfered as described in the WTC documentation.
Level: 1

Type: ERROR

Impact: WTC

BEA-180110: Internal FML32-to-XML conversion failed.

Cause: The FML32 buffer that was received from Tuxedo contained field buffer names that were not provided to the WebLogic Tuxedo Connector (WTC). Therefore, the name translation failed.

Action: Verify that the field tables have been properly transferred as described in the WTC documentation.
Level: 1

Type: ERROR

Impact: WTC

BEA-180111: Internal FML to XML conversion failed.

Cause: The FML buffer that was received from Tuxedo contained field buffer names that were not provided to the WebLogic Tuxedo Connector (WTC). Therefore, the name translation failed.

Action: Verify that the field tables have been properly transferred as described in the WTC documentation.
Level: 1

Type: ERROR

Impact: WTC

BEA-180112: Internal FML32 to XML conversion failed.

Cause: The FML32 buffer that was received from Tuxedo contained field buffer names that were not provided to the WebLogic Tuxedo Connector (WTC). Therefore, the name translation failed.

Action: Verify the field tables have been properly transferred as described in the WTC documentation.
Level: 1

Type: ERROR

Impact: WTC

BEA-180115: The tBridge cannot parse the configuration MBeans: {0}.

Cause: The MBeans for the tBridge contain invalid attributes.

Action: Correct the attribute definitions for the tBridge MBeans.
Level: 1

Type: ERROR

Impact: WTC

BEA-180116: The specified field table type {0} is incorrect.

Cause: The WTCStartup.getFldTbls() method was called with an invalid argument.

Action: Verify that the Type argument for this is either fml16 or fml32.
Level: 1

Type: ERROR

Impact: WTC

BEA-180117: The encoding {0} is not supported. JVM default encoding is used.

Cause: Specified encoding name is not supported.

Action: Correct the encoding name and restart WebLogic Server.
Level: 1

Type: ERROR

Impact: WTC

BEA-180118: Failed to find TPUSR file: {0}.

Cause: The specified file TPUSR file does not exist.

Action: Correct the configuration by specifying the correct TPUSR file or create it before using the file.
Level: 1

Type: ERROR

Impact: WTC

BEA-180119: The specified filename is not a valid file: {0}.

Cause: The WebLogic Tuxedo Connector (WTC) had the incorrect configuration.

Action: Correct the WTC TPUSR file configuration.
Level: 1

Type: ERROR

Impact: WTC

BEA-180120: The file {0} is not readable.

Cause: The user does not have the read permission to read the configured TPUSR file.

Action: Change the permissions of the TPUSR file.
Level: 1

Type: ERROR

Impact: WTC

BEA-180121: Cannot find file {0}.

Cause: The configured WebLogic Tuxedo Connector (WTC) TPUSR file does not exist.

Action: Correct the WTC TPUSR file configuration or create the file.
Level: 1

Type: ERROR

Impact: WTC

BEA-180122: No permission to read the file {0}.

Cause: The user does not have the read permission to read the configured TPUSR file.

Action: Change the permissions of the TPUSR file.
Level: 1

Type: ERROR

Impact: WTC

BEA-180123: File I/O error for file {0}, reason: {1}.

Cause: The file was corrupted or deleted.

Action: Correct the file corruption or use a new TPUSR file.
Level: 1

Type: ERROR

Impact: WTC

BEA-180124: The specified number is not in a valid number format: {0}.

Cause: The configured cache size was not in a valid number format.

Action: Correct the configuration in the WebLogic Tuxedo Connector (WTC) TpUsrFile.
Level: 1

Type: ERROR

Impact: WTC

BEA-180132: Custom AppKey generator class {0} not found.

Cause: The configured custom AppKey class full path name was incorrect.

Action: Ensure that the configuration is correct and that the custom class exists.
Level: 1

Type: ERROR

Impact: WTC

BEA-180133: AppKey plug-in initialization failed. Reason: {0}

Cause: The most likely reason is that the user database was not available or the initialization parameter was incorrect.

Action: Ensure that the user database is available and that the configuration is correct.
Level: 1

Type: ERROR

Impact: WTC

BEA-180134: Create new AppKey class {0} instance failed.

Cause: Either the class is not accessible, there is no permission to create a new instance of this class, or the class is not valid.

Action: Ensure that the class is accessible with the correct permission. Also, the class must be based on the weblogic.wtc.jatmi.AppKey interface.
Level: 1

Type: ERROR

Impact: WTC

BEA-180136: The {0} attribute on the {1} MBean is undefined but required.

Cause: The attribute value must be defined, but it was not defined.

Action: Check that the MBean attribute is set correctly.
Level: 1

Type: ERROR

Impact: WTC

BEA-180137: The {0} attribute on the {1} MBean is set incorrectly.

Cause: The attribute was defined improperly.

Action: Check that the MBean attribute is set correctly.
Level: 1

Type: ERROR

Impact: WTC

BEA-180138: The {0} MBean appears to contain previously defined import service information.

Cause: The attributes defined on this MBean have already been used to define and import a service.

Action: Check that the Resourcename,RemoteAccessPointList, and LocalAccessPoint attributes are not all duplicated in another import MBean.
Level: 1

Type: ERROR

Impact: WTC

BEA-180139: A {0} type MBean is not defined, but it is required to be defined.

Cause: An MBean was not defined, but it is required to be defined.

Action: Check that the MBean type specified is defined in the configuration.
Level: 1

Type: ERROR

Impact: WTC

BEA-180141: Message header contains an invalid magic number, connection closed.

Cause: Either an invalid TDOMAIN protocol data unit was received, or the remote domain gateway did not have network encoding enabled.

Action: Ensure that the local access point is configured with the correct port number, and that the remote gateway does not have the same MTYPE configured for this TDOMAIN session.
Level: 1

Type: ERROR

Impact: WTC

BEA-180142: Local domain {0} in use and cannot be deleted.

Cause: The local domain was in use by another resource.

Action: Check for remote domains, imported or exported services, or passwords that use this local domain.
Level: 1

Type: ERROR

Impact: WTC

BEA-180143: Cannot find local domain {0}.

Cause: The local domain could not be found.

Action: Check the access point name.
Level: 1

Type: ERROR

Impact: WTC

BEA-180144: Duplicate remote domain {0}. Cannot add.

Cause: The access point name was duplicated.

Action: Check the access points and access point IDs for existing domains.
Level: 1

Type: ERROR

Impact: WTC

BEA-180145: Remote domain {0} in use. Cannot delete.

Cause: The remote domain is referenced by another resource or has an active connection.

Action: Shut down the connection to this remote domain. Check other resources that may reference this domain.
Level: 1

Type: ERROR

Impact: WTC

BEA-180146: Remote domain {0} cannot be found.

Cause: The specified remote domain cannot be found.

Action: Check the access point name for the remote domain.
Level: 1

Type: ERROR

Impact: WTC

BEA-180147: Cannot find imported service {0}.

Cause: The specified imported service could not be found.

Action: Check the name of the imported service.
Level: 1

Type: ERROR

Impact: WTC

BEA-180148: Cannot find exported service {0}.

Cause: The specified exported service could not be found.

Action: Check the name of the exported service.
Level: 1

Type: ERROR

Impact: WTC

BEA-180149: Cannot find password entry {0}.

Cause: The specified password entry could not be found.

Action: Check the local and remote access point names.
Level: 1

Type: ERROR

Impact: WTC

BEA-180150: Connection policy for {0} is INCOMING_ONLY.

Cause: The connection policy specified INCOMING_ONLY, so an outbound connection could not be started.

Action: Check the access point ID for the remote domain.
Level: 1

Type: ERROR

Impact: WTC

BEA-180151: Cannot modify resource {0} because it may be in use.

Cause: There is an active connection that may use this resource.

Action: Stop connections associated with this resource before attempting to delete the resource.
Level: 1

Type: INTERNAL_ERROR

Impact: WTC

BEA-180152: Registration of notification listeners for the configured MBeans has failed.

Cause: This is an internal system error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: WTC

BEA-180153: No valid host Internet address for WTC remote access point {0}.

Cause: This is a configuration error.

Action: Correct the WTC remote access point's network address list.
Level: 1

Type: WARNING

Impact: WTC

BEA-180154: No valid listening address configured for local access point {0}.

Cause: This is an internal system error.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: WTC

BEA-180155: No valid network address for TDomain session ({0}, {1}) to try to connect to.

Cause: Either there is a configuration error or the remote access point was not available and cannot be accessed using the configured information.

Action: Correct the configuration, or boot the remote access point.
Level: 1

Type: WARNING

Impact: WTC

BEA-180156: Failed to connect to remote access point(//{0}:{1}), try next address.

Cause: Either a configuration error exists or the remote access point was not available at the address specified.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WTC

BEA-180157: Failed to connect to remote access point(//{0}:{1}), no more address to try.

Cause: Either a configuration error exists or the remote access point was not available at the address specified.

Action: Correct the configuration or make the remote access point available.
Level: 1

Type: WARNING

Impact: WTC

BEA-180158: No more valid network addresses for the local access point {0} to listen.

Cause: There is a configuration error.

Action: Correct the configuration.
Level: 1

Type: WARNING

Impact: WTC

BEA-180159: Failed to listen for local access point {0} on address (//{1}:{2}), try next address.

Cause: Either a configuration error exists or this was intended.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WTC

BEA-180160: Failed to create listening endpoint for local access point {0} on address (//{1}:{2}), no more addresses to try.

Cause: There is a configuration error.

Action: Correct the configuration.
Level: 1

Type: WARNING

Impact: WTC

BEA-180161: Failed to find the imported service for QSpace {0}, so the tBridge has redirected the message to the wlsErrorDestination.

Cause: The WebLogic Tuxedo Connector (WTC) import was incorrectly configured.

Action: Correct the configuration.
Level: 1

Type: ERROR

Impact: WTC

BEA-180162: Cannot find imported service {0}, so the tBridge has redirected the message to the wlsErrorDestination.

Cause: There is a configuration error.

Action: Correct the configuration.
Level: 1

Type: ERROR

Impact: WTC

BEA-180163: The received Tuxedo reply uses the unsupported buffer type {0}, so the tBridge has redirected the message to the wlsErrorDestination.

Cause: The Tuxedo server returned a reply with an unsupported buffer type.

Action: Modify the Tuxedo server to return the reply with a WebLogic Tuxedo Connector (WTC) supported buffer type.
Level: 1

Type: ERROR

Impact: WTC

BEA-180164: Failed to send message to JMS, so the tBridge has redirected the message to the WLSErrorDestination.

Cause: The JMS replyQ is configured incorrectly.

Action: Correct the configuration of the JMS queue to be used for the tBridge reply queue.
Level: 1

Type: ERROR

Impact: WTC

BEA-180165: TDomain session ({0}, {1}) disconnected because no keep alive acknowledgement was received.

Cause: A network outage may have occurred.

Action: Check the network connection between the two gateways to determine if it is connected.
Level: 1

Type: NOTIFICATION

Impact: WTC

BEA-180166: The remote gateway does not support application level keep alive. This feature is disabled for the TDomain session ({0}, {1}).

Cause: The remote gateway does not support this application level keep alive feature.

Action: Update the remote gateway to a version of Tuxedo that supports the TDomain application level keep alive feature.
Level: 1

Type: WARNING

Impact: WTC

BEA-180167: The imported resource {0} uses a TDomain session ({1}, {2}) that does not exist.

Cause: The imported resource was not configured properly.

Action: Correct the configuration for the imported service.
Level: 1

Type: ERROR

Impact: WTC

BEA-180168: A connection cannot be established between local domain {0} and remote domain {1} due to a problem with the local or remote password used to authenticate the connections between these domains.

Cause: The domain passwords were not configured properly.

Action: Encrypt the correct local and remote passwords for the connection using the weblogic.wtc.gwt.genpasswd utility and use the results to configure a WTCPasswordMBean.
Level: 1

Type: ERROR

Impact: WTC

BEA-180169: XA.end() failed: {0}

Cause: The transaction may have been marked as ROLLBACK_ONLY.

Action: Inspect the application logic to determine the cause of the error.
Level: 1

Type: ERROR

Impact: WTC

BEA-180170: Unexpected exception while converting View {0} to XML: {1}

Cause: Refer to the exception details.

Action: Refer to the exception details.
Level: 1

Type: ERROR

Impact: WTC

BEA-180171: SSL null ciphers are not enabled and will be upgraded to the minimum 56 bits.

Cause: The null cipher suites were disabled by SSL configuration.

Action: This can be ignored because stronger encryption strength is allowed by WTC configuration and is also available by SSL. However, WTC configuration can be corrected to use only 56 bits and stronger cipher suites or SSL null ciphers can be enabled, if desired.
Level: 1

Type: WARNING

Impact: WTC

BEA-180172: SSL null ciphers are not enabled.

Cause: The null cipher suites were disabled by SSL configuration.

Action: Either the SSL null cipher suites must be explicitly enabled, or the WTC configuration must be updated to use stronger encryption cipher suites.
Level: 1

Type: ERROR

Impact: WTC

BEA-180173: Invalid private key for identity alias {0} from key store {1}, detected by {2}.

Cause: An invalid key store or the private key alias configuration does not exist in the key store, or an incorrect private key store passphrase was configured.

Action: Correct the key store or private key alias information in the configuration.
Level: 1

Type: ERROR

Impact: WTC

BEA-180174: Invalid private key store {0}, detected by {1}

Cause: The private key store configured does not exist or is corrupted.

Action: Correct the private key store configuration information.
Level: 1

Type: ERROR

Impact: WTC

BEA-180175: Invalid trust certificate store {0}, detected by {1}

Cause: The private key store configured does not exist or is corrupted.

Action: Correct the private key store configuration information.
Level: 1

Type: ERROR

Impact: WTC

BEA-180176: An error occurred while retrieving the trusted certificate from trust store {0}, detected by {1}.

Cause: The configured trust certificate was corrupted or an incorrect passphrase was configured.

Action: Correct the trust certificate store configuration information.
Level: 1

Type: ERROR

Impact: WTC

BEA-180177: An error occurred while retrieving trusted certificates from WebLogic Server, detected by {0}.

Cause: The configured trust certificate was corrupted or an incorrect passphrase was configured.

Action: Correct the trust certificate store configuration information.
Level: 1

Type: ERROR

Impact: WTC

BEA-180178: The requested encryption strength of 256 bits of local access point {0} is not supported by LLE. Downgrade to 128 bits.

Cause: The configured encryption strength is not supported by LLE.

Action: Either change the encryption strength to the LLE supported strength or use SSL for connection privacy. LLE supports 0, 40, 56, and 128 bits encryption strength. SSL supports 0, 56, 128, and 256 bits encryption strength.
Level: 1

Type: NOTIFICATION

Impact: WTC

BEA-180179: When enabling access point {0} to support SDP, the SSL support setting for this access point was ignored.

Cause: When SDP is configured, SSL is not supported.

Action: No action is required if SDP support is expected. Otherwise, update the configuration to disable SDP support.
Level: 1

Type: WARNING

Impact: WTC

BEA-180180: An error occurred while trying to open class com.oracle.net.Sdp when WTC support for SDP was enabled.

Cause: The current JRE does not support SDP.

Action: Use the JRockit version of the JRE provided with this release of WebLogic Server.
Level: 1

Type: ERROR

Impact: WTC

BEA-190000: Initializing J2EE Connector Service.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-190001: J2EE Connector Service initialized successfully.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-190004: ConnectionFactory not found for jndiName {0}.

Cause: This warning can occur upon viewing the JNDI tree for the Managed Server on the Administration Console. The other likely cause for this error is that an incorrect JNDI name was specified for the desired resource adapter or that the resource adapter is not deployed.

Action: Ignore the warning if it occurs while viewing the JNDI tree of a Managed Server. Otherwise, check the deployed connectors in the Administration Console and verify the name that was used to access it.
Level: 1

Type: WARNING

Impact: Connector

BEA-190005: An error occurred while creating a connection factory for ManagedConnectionFactory with jndiName {0}.

Cause: The cause is unknown. Consult the resource adapter vendor documentation.

Action: Examine the exception in the log for more information about how to correct the problem. You may need to refer to the resource adapter vendor documentation to determine an appropriate course of action.
Level: 1

Type: ERROR

Impact: Connector

BEA-190008: An error occurred while {2} the connection instance {1} for {0} resource adapter. Exception is: {3}

Cause: This error occurs as the result of an attempt to call cleanup() or destroy() on a resource adapter managed connection. The resource adapter can generate a ResourceException if the operation fails. It can also generate an IllegalStateException if, for example, an attempt was made to clean up a connection when a transaction was in progress. A ResourceAdapterInternalException may be generated if an internal error condition is detected in the resource adapter.

Action: Examine the log for the exact type of exception that was generated. In the case of an IllegalStateException, report the error to My Oracle Support. In the case of a ResourceAdapterInternalException, report the error to the resource adapter vendor.
Level: 1

Type: ERROR

Impact: Connector

BEA-190009: No ConnectionRequestInfo was provided for Application Managed Security Context.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-190010: Unable to determine resource principal for the container-managed security context.

Cause: Improper security principal map configuration for resource adapter.

Action: Check the resource adapter configuration.
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-190012: Component using JNDIName: {0} has {1} managed security.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-190013: An error occurred while processing context: java:/comp/env/wls-connector-resref.

Cause: This is an internal WebLogic Server error.

Action: Report this error to My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-190019: < {0} > An error occurred when opening the log file {1} for the resource adapter.

Cause: The log file is either a directory rather than a regular file, or it could not be opened for some other reason.

Action: Check the log-filename configuration parameter in weblogic-ra.xml.
Level: 1

Type: ERROR

Impact: Connector

BEA-190020: < {0} > An error occurred while setting the log file to the resource adapter.

Cause: An error occurred when WebLogic Server called the resource adapter's ManagedConnectionFactory.setLogWriter() method.

Action: Contact your resource adapter supplier about the ManagedConnectionFactory.setLogWriter() method.
Level: 1

Type: ERROR

Impact: Connector

BEA-190023: < {0} > Error invoking the ManagedConnectionFactory "set" method for the configuration property "{1}". Reason: {2}

Cause: The method required for setting the config-property could not be properly invoked.

Action: Check the config-property of the ra.xml file in the resource adapter and ensure that the indicated property is specified correctly.
Level: 1

Type: ERROR

Impact: Connector

BEA-190024: < {0} > Error making initial connections for pool. Reason: {1}

Cause: The backend system to which the resource adapter connects may be down, or the resource adapter may be misconfigured.

Action: Check the availability of the backend system, then confirm the correct configuration of the resource adapter.
Level: 1

Type: WARNING

Impact: Connector

BEA-190032: < {0} > ResourceAllocationException generated by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "{1} "

Cause: The cause should be evident from the exception. One likely cause is a misconfigured weblogic-ra.xml or ra.xml. The property(ies) specifying the connection information may not be correct.

Action: Check the exception to determine the cause and attempt to remedy the indicated problem. You may need to consult the configuration for the resource adapter or the resource adapter documentation. You might also consult the resource adapter vendor support information or organization.
Level: 1

Type: WARNING

Impact: Connector

BEA-190033: < {0} > createManagedConnection returned a null ManagedConnection.

Cause: This generally is a resource adapter error. A resource adapter should never return a null managed connection.

Action: Check the exception to determine the cause and attempt to remedy the indicated problem. You may need to consult the configuration for the resource adapter or the resource adapter documentation, or consult the resource adapter vendor support information or organization
Level: 1

Type: ERROR

Impact: Connector

BEA-190049: The connector service failed to initialize. ServiceMBean initialization error: {0}

Cause: This error should not occur under normal operations. Possible causes of this error could be low memory, file corruption, or machine instability.

Action: Try rebooting the machine and restarting the server again. If the problem persists, note the error details and contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-190050: An error occurred in the connector service shutdown. Error: {0}

Cause: The error occurred as a result of shutting down a connection pool or unregistering the ServiceMBean.

Action: Report the error to My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-190051: An error occurred while shutting down the connection pool with pool name: {0}. Reason: {1}

Cause: An error occurred while shutting down the connection pool. The error occurred while unregistering the ConnectionPoolRuntimeMBean. pool name:{0}. Reason: {1}

Action: Report the error to My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-190052: An error occurred while creating a connection pool Runtime MBean with pool name: {0}. Reason: {1}

Cause: An error occurred while creating a connection pool Runtime MBean. The error occurred while initializing the ConnectionPoolRuntimeMBean. pool name:{0}. Reason: {1}

Action: Report the error to My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-190053: An error occurred while creating a resource for a connection pool {0}. Reason: {1}

Cause: Error occurred while instantiating a ConnectionRuntimeMBean for the connection being created. Pool name: {0}. Reason: {1}

Action: Report the error to My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-190054: An error occurred while destroying a resource for a connection pool {0}. Reason: {1}

Cause: An error occurred while unregistering a ConnectionRuntimeMBean for the connection being destroyed. Pool name: {0}, Reason: {1}

Action: Report the error to My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-190056: An error occurred while reserving a resource from a connection pool {0}. Reason: {1}

Cause: An error occurred while registering an XAResource for the connection being reserved with the transaction manager. Pool name:{0}. Reason: {1}

Action: Report the error to My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-190064: Access has been denied to {0}, Application: {1}, Module: {2}, EIS Type: {3}, while reserving a connection.

Cause: The entitlement check did not pass for the connection request to the connection pool with name: {0}.

Action: Check your entitlement configuration in the Administration Console.
Level: 1

Type: WARNING

Impact: Connector

BEA-190075: The resource adapter returned a null connection factory when createConnectionFactory was called for "{0}".

Cause: The resource adapter is not functioning according to the specification.

Action: Contact the resource adapter vendor.
Level: 1

Type: ERROR

Impact: Connector

BEA-190079: The descriptor element {0} has been replaced by {1}.

Cause: A deprecated descriptor element has been detected.

Action: Convert the old descriptor element to the replacement element.
Level: 1

Type: WARNING

Impact: Connector

BEA-190080: An inactive deprecated descriptor element {0} has been detected.

Cause: An inactive deprecated descriptor element has been detected.

Action: Refer to the connector documentation for more information.
Level: 1

Type: WARNING

Impact: Connector

BEA-190081: Testing resource adapter "{0}" for viability of connection proxies.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-190082: Proxy test passed. WebLogic Server will use connection proxies for resource adapter "{0}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-190084: Unable to complete connection proxy test for "{0}" due to the following exception. WebLogic Server will attempt to use connection proxies for resource adapter "{0}" as usual.

Cause: WebLogic Server attempted to pose as an application component to determine whether a generated proxy class is compatible with a resource adapter (to support late transaction enlistment and leak and idle detection of connections). The connection proxy test failed.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Connector

BEA-190085: The linkref RAR {0} has been marked for late deployment since its base has not been deployed.

Cause: The base RAR that the linkref points to has not been deployed yet.

Action: Do not use the linkref until its base has been deployed.
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-190088: Trying to deploy a connector with a JNDI name that already exists {0}.

Cause: Trying to deploy a connector with a JNDI name that already exists {0}.

Action: Use a unique JNDI name while deploying the connector.
Level: 1

Type: ERROR

Impact: Connector

BEA-190089: Unexpected error occurred while processing a resource adapter JAR file.

Cause: The cause is unknown.

Action: Examine the stack trace for the cause and action.
Level: 1

Type: ERROR

Impact: Connector

BEA-190090: Call to implementation of ManagedConnection.getLocalTransaction in resource adapter with jndiName = {1} failed: {0}

Cause: Refer to the error message for more information.

Action: See the error message for more information. If it is still unclear, contact the resource adapter vendor or My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-190091: Call to implementation of ManagedConnection.getXAResource in resource adapter with jndiName = {1} failed: {0}

Cause: Refer to the error message for more information.

Action: Refer to the error message for more information. If still unclear, contact the resource adapter vendor or My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-190092: An error occurred while reserving a resource from a connection pool {0}. Reason: {1}

Cause: An error occurred while registering a non-XAResource for the connection being reserved with the transaction manager. pool name:{0}. Reason: {1}

Action: Report this error to My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-190097: Unable to complete the connection proxy test for "{0}" due to an exception. WebLogic Server will attempt to use connection proxies for resource adapter "{0}" as usual. Exception: {1}

Cause: WebLogic Server attempted to pose as an application component to determine whether a generated proxy class is compatible with a resource adapter (to support late transaction enlistment and leak and idle detection of connections). The connection proxy test failed.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-190098: Trying to release a resource that has already been released for {0}.

Cause: Trying to release a resource that has already been released for {0}. It is possible that the connection was already released due to an error that occurred with the connection.

Action: No action is required.
Level: 1

Type: WARNING

Impact: Connector

BEA-190099: Attempting to close a connection that has already been closed for {0}.

Cause: An attempt was made to close a connection that has already been closed for {0}.

Action: No action is required.
Level: 1

Type: WARNING

Impact: Connector

BEA-190100: A close() method was not found on the connection handle while testing for the viability for connection proxies : {0}

Cause: A close() method was not found on the connection handle while testing for the viability for connection proxies : {0}. As per the 1.0 specification, a close() method is required on the connection handle.

Action: Implement a close() method for the connection handle.
Level: 1

Type: ERROR

Impact: Connector

BEA-190101: Linkrefs are deprecated for 1.0 resource adapters: {0}

Cause: Linkrefs are deprecated for 1.0 resource adapters.

Action: No action is required.
Level: 1

Type: WARNING

Impact: Connector

BEA-190102: Failed to unregister the Diagnostic Image for the Connector Service.

Cause: This is a WebLogic Server internal error.

Action: See the stack trace and report the error to My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-190103: Failed to register the Diagnostic Image for the Connector Service.

Cause: This is a WebLogic Server internal error.

Action: See the stack trace and report the error to My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-190104: While configuring an object of type: {0} of Resource Adapter {1}, the following errors/omissions were found: {2}

Cause: Properties have been specified in a resource adapter deployment descriptor which are inconsistent with those defined by the resource adapter code. There may be properties specified in the descriptor that do no exist in the object or are of the wrong type.

Action: Check that the specified properties are spelled properly. Check with the resource adapter documentation or the vendor to determine whether or not these warnings can be ignored.
Level: 1

Type: WARNING

Impact: Connector

BEA-190105: Failed to initialize the AnonymousSubject.

Cause: This is a WebLogic Server internal error.

Action: See the stack trace and report the error to My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-190106: Failed to find the RuntimeMBean for the module: {0}

Cause: This is a WebLogic Server internal error.

Action: See the stack trace and report the error to My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-190107: Failed to unregister the RuntimeMBean for the module: {0}

Cause: This is a WebLogic Server internal error.

Action: See the stack trace and report the error to My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-190108: Failed to initialize the Jndi Subcontexts for the adapter: appId = {0}, {1}

Cause: This is a WebLogic Server internal error.

Action: See the stack trace and report the error to My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-190109: Extracting file {0} to {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-190110: Resource adapter is calling BootstrapContext.createTimer() and allocating a Timer Thread that is not managed by WebLogic Server. This may adversely impact the performance or operation of WebLogic Server.

Cause: A resource adapter is calling BootstrapContext.createTimer() and allocating a Timer Thread that is not managed by WebLogic Server.

Action: Contact the resource adapter vendor and notify them of this warning condition.
Level: 1

Type: WARNING

Impact: Connector

BEA-190111: InvalidDyeException was generated: Module Name = {0}, {1}.

Cause: This is a WebLogic Server internal error.

Action: See the stack trace and report the error to My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-190112: Failed to register the XAResource to be used for recovery: {0}

Cause: See the error description in the message body.

Action: See the stack trace and report the error to My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-190113: Failed to Unregister the XAResource used for recovery: {0}

Cause: See the error description in the message body.

Action: See the stack trace and report the error to My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-190114: Failed to apply dynamic pool changes: {0}

Cause: See the error description in the message body.

Action: See the error description in the message body.
Level: 1

Type: ERROR

Impact: Connector

BEA-190115: The ManagedConnectionFactory class does not implement the ResourceAdapterAssociation interface: {0}

Cause: See the error in the message body for information.

Action: Please contact the resource adapter vendor and notify them of this error condition.
Level: 1

Type: ERROR

Impact: Connector

BEA-190116: An invalid event was triggered on the XAResource used for recovery: {0}

Cause: This is a WebLogic Server internal error.

Action: Report the error to My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-190117: Invocation of ManagedConnection.cleanup() failed: {0}

Cause: See the error in the message body for information.

Action: Examine the stack trace and error message for more information.
Level: 1

Type: ERROR

Impact: Connector

BEA-190118: ConnectionErrorOccurred event was triggered: {0}

Cause: The adapter has indicated an error occurred on the exception.

Action: Examine the stack trace and error message for more information.
Level: 1

Type: ERROR

Impact: Connector

BEA-190119: Invocation of ManagedConnection.destroy() failed: {0}

Cause: The implementation of the resource adapter's cleanup() method threw an exception.

Action: Examine the stack trace and error message for more information.
Level: 1

Type: ERROR

Impact: Connector

BEA-190120: Invocation of ManagedConnection.getXAResource() returned null.

Cause: The implementation of the resource adapter's getXAResource() returned null.

Action: Please contact the resource adapter vendor to determine why getXAResource() returned null.
Level: 1

Type: ERROR

Impact: Connector

BEA-190121: Failed to dissociate the Connection Handles from a ManagedConnection: Adapter JndiName = {0}, {1}

Cause: See the message body and stack trace for more details.

Action: See the message body and stack trace for more details.
Level: 1

Type: ERROR

Impact: Connector

BEA-190122: The resource adapter passed a null ManagedConnection into WebLogic Server's implementation of ConnectionManager.lazyEnlist().

Cause: The resource adapter's implementation passed a null ManagedConnection into the lazyEnlist() method.

Action: Please notify the resource adapter's vendor about this error.
Level: 1

Type: ERROR

Impact: Connector

BEA-190123: Outbound adapter for jndiName = {0}, is using sharing scope = {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-190124: Failed to deploy LinkRef Adapter, moduleName = {0}, baseRA = {1}, Exception: {2}

Cause: Refer to the message body and exception message for more information.

Action: Refer to the message body and exception message for more information.
Level: 1

Type: ERROR

Impact: Connector

BEA-190125: Internal error occurred, assertion failed: {0}

Cause: An internal consistency check failed, indicating a software defect.

Action: Please note the circumstances of the error, as well as any related log messages, and contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-190126: anonymous

Cause: This message is used only for localization (internationalization) purposes.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Connector

BEA-190127: CloseCount

Cause: This message is used only for localization (internationalization) purposes.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Connector

BEA-190128: CreateCount

Cause: This message is used only for localization (internationalization) purposes.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Connector

BEA-190129: FreePoolSize

Cause: This message is used only for localization (internationalization) purposes.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Connector

BEA-190130: PoolSize

Cause: This message is used only for localization (internationalization) purposes.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Connector

BEA-190131: WaitingThreadCount

Cause: This message is used only for localization (internationalization) purposes.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Connector

BEA-190133: Number of times create was called on the connection pool

Cause: This message is used only for localization (internationalization) purposes.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Connector

BEA-190134: Number of connections in the pool that are free for use

Cause: This message is used only for localization (internationalization) purposes.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Connector

BEA-190135: Size of the connection pool

Cause: This message is used only for localization (internationalization) purposes.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Connector

BEA-190136: Number of threads in the waiting state

Cause: This message is used only for localization (internationalization) purposes.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Connector

BEA-190137: Never

Cause: This message is used only for localization (internationalization) purposes.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Connector

BEA-190138: <Unavailable>

Cause: This message is used only for localization (internationalization) purposes.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Connector

BEA-190139: Running

Cause: This message is used only for localization (internationalization) purposes.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Connector

BEA-190140: Suspended

Cause: This message is used only for localization (internationalization) purposes.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Connector

BEA-190141: New

Cause: This message is used only for localization (internationalization) purposes.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Connector

BEA-190142: Initialized

Cause: This message is used only for localization (internationalization) purposes.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Connector

BEA-190143: Prepared

Cause: This message is used only for localization (internationalization) purposes.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Connector

BEA-190144: Activated

Cause: This message is used only for localization (internationalization) purposes.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Connector

BEA-190145: Unknown

Cause: This message is used only for localization (internationalization) purposes.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Connector

BEA-190146: An error occurred while setting the log file to the resource adapter's ManagedConnectionFactory: {0}. The exception was "{1}" with cause "{2}".

Cause: An error occurred when WebLogic Server called the resource adapter's ManagedConnectionFactory.setLogWriter() method.

Action: Examine the message and cause, or contact the resource adapter provider, or both.
Level: 1

Type: ERROR

Impact: Connector

BEA-190147: Profiling Record for Pool: PoolName = "{0}", Type = "{1}", Timestamp = "{2}", Properties : {3}

Cause: This message is informational. The Harvester logged this Profiling Record for debug purposes.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-190148: The attempt to set the property "{1}" of type "{2}" of object "{0}" to value "{3}" failed with a PropertyVetoException generated by the resource adapter. The veto message was "{4}".

Cause: See the veto message for more information.

Action: See the veto message for more information. Contact the resource adapter provider if more assistance is needed.
Level: 1

Type: WARNING

Impact: Connector

BEA-190149: No JNDI Name has been specified for the resource adapter in module {0} of application {1}. Since this is an inbound resource adapter, <jndi-name> must also be specified in weblogic-ra.xml for endpoint activation by a message endpoint MDB to work.

Cause: There is a missing <jndi-name> element in weblogic-ra.xml.

Action: Specify the <jndi-name> in weblogic-ra.xml that corresponds to the JNDI name expected by the MDB that is using this inbound resource adapter.
Level: 1

Type: WARNING

Impact: Connector

BEA-190150: The process of creating the Connector Diagnostic Image has been timed out by the Diagnostic Framework. The resulting image may be incomplete.

Cause: The process of creating the Connector Diagnostic Image has been timed out by the Diagnostic Framework.

Action: Please investigate the contents of the log and Diagnostic Images for more information.
Level: 1

Type: WARNING

Impact: Connector

BEA-190151: Parsing error, buildOutboundResourceAdapter() error in parsing ra.xml. While looking for connectionfactory-interface, failed to find: "{0}"

Cause: There is an error in the XML configuration for this adapter.

Action: Please contact the vendor to obtain a resource adapter with a valid configuration.
Level: 1

Type: ERROR

Impact: Connector

BEA-190152: Failed to create a new ConnectorInboundRuntimeMBeanImpl for "{0}", {1}

Cause: See the error in the logged message for more information.

Action: See the error in the logged message for more information.
Level: 1

Type: ERROR

Impact: Connector

BEA-190153: Failed to close the logging stream for pool: "{0}", {1}

Cause: See the error in the logged message for more information.

Action: See the error in the logged message for more information.
Level: 1

Type: WARNING

Impact: Connector

BEA-190154: Failed to create the logging stream for pool: "{0}", {1}

Cause: See the error in the logged message for more information.

Action: See the error in the logged message for more information.
Level: 1

Type: WARNING

Impact: Connector

BEA-190155: Compliance checking and validation of the resource adapter {0} resulted in the following warnings: {1}

Cause: The specified resource adapter failed to pass compliance and validity checking as indicated by the listed warnings and errors.

Action: Correct the ra.xml, weblogic-ra.xml or the resource adapter archive.
Level: 1

Type: WARNING

Impact: Connector

BEA-190156: There were no compliance or validation errors found in the resource adapter {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-190157: There were {1} critical compliance or validation error(s), {2} non-critical compliance or validation error(s), and {3} warning(s) found in the resource adapter {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-190158: This is a link ref resource adapter for {0}. No validation can be done at this time.

Cause: Since there is no ra.xml in this resource adapter, validation of the adapter cannot be performed until it and the base adapter are deployed.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-190159: Connection Pool {0} has been reset.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-190160: Connection pool {0} is in use and cannot be reset. Try forceReset instead.

Cause: Since there are connections reservered from connection pool {0}, reset of the pool cannot be performed.

Action: Try forceReset instead.
Level: 1

Type: WARNING

Impact: Connector

BEA-190161: Failed to extract adapter {0} to server temporary directory due to exception {1}.

Cause: Extraction of the adapter {0} to server temporary directory failed due to the exception.

Action: Check the permissions on the server temporary directory or check the exception.
Level: 1

Type: ERROR

Impact: Connector

BEA-190162: Failed to create server temporary directory {1} while extracting adapter {0}.

Cause: Creation of the server temporary directory {1} failed while extracting the adapter {0}.

Action: Check the permissions on the server temporary directory.
Level: 1

Type: ERROR

Impact: Connector

BEA-199000: Only positive values are allowed for initial-capacity unless initial and max capacity are equal.

Cause: Refer to the message body and exception for more information.

Action: Refer to the message body and exception for more information.
Level: 1

Type: ERROR

Impact: Connector

BEA-199001: Zero value for max-capacity is allowed only for link-ref adapters.

Cause: The max-capacity is zero.

Action: Check the max-capacity and update it.
Level: 1

Type: ERROR

Impact: Connector

BEA-199002: Negative values are not allowed for max-capacity.

Cause: The max-capacity is negative.

Action: Check the max-capacity and update it.
Level: 1

Type: ERROR

Impact: Connector

BEA-199003: max-capacity should be greater than or equal to initial-capacity. {0}

Cause: The max-capacity is less than initial-capacity.

Action: Check the max-capacity and update it.
Level: 1

Type: ERROR

Impact: Connector

BEA-199004: Only positive values are allowed for capacity-increment.

Cause: The capacity-increment is zero or negative.

Action: Check the capacity-increment and update it.
Level: 1

Type: ERROR

Impact: Connector

BEA-199005: capacity-increment should be less than or equal to ( max_capacity-initial_capacity ). {0}

Cause: The capacity-increment is greater than max_capacity-initial_capacity.

Action: Check the capacity-increment and update it.
Level: 1

Type: ERROR

Impact: Connector

BEA-199006: Only positive values are allowed for shrink-frequency-seconds.

Cause: The shrink-frequency-seconds is zero or negative.

Action: Check the shrink-frequency-seconds.
Level: 1

Type: ERROR

Impact: Connector

BEA-199007: Only values greater than or equal to 0 are allowed for inactive-connection-timeout-seconds.

Cause: The value of inactive-connection-timeout-seconds must be positive.

Action: Please check the inactive-connection-timeout-seconds.
Level: 1

Type: ERROR

Impact: Connector

BEA-199010: No ra.xml or weblogic-ra.xml has been specified. The RAR is null and there is no alternate descriptor.

Cause: The deployment descriptor for this adapter cannot be found.

Action: Define the deployment descriptor in ra.xml or weblogic-ra.xml or an annotation.
Level: 1

Type: ERROR

Impact: Connector

BEA-199011: No ra.xml or weblogic-ra.xml has been specified.

Cause: The deployment descriptor for this adapter could not be found.

Action: Define the deployment descriptor in ra.xml or weblogic-ra.xml.
Level: 1

Type: ERROR

Impact: Connector

BEA-199012: Unable to find the schema.

Cause: The schema could not be found.

Action: Check the location of the schema for the XML file.
Level: 1

Type: ERROR

Impact: Connector

BEA-199013: Application {0} does not have any components in it.

Cause: The application does not contain any components.

Action: Add components in the application and define them in the deployment descriptor.
Level: 1

Type: ERROR

Impact: Connector

BEA-199014: Application {0} is a RAR file, but it contains more than 1 component.

Cause: The application contains multiple adapter components.

Action: Check the deployment descriptor or the annotation.
Level: 1

Type: ERROR

Impact: Connector

BEA-199015: Error occurred while trying to rollback the module: {0}

Cause: The module cannot be rolled back. See the reported error for the cause.

Action: Examine the exception in the log for more information about how to correct the problem.
Level: 1

Type: ERROR

Impact: Connector

BEA-199016: Unable to create runtime MBean for connector: Module "{0}", {1}

Cause: The runtime MBean cannot be created. See the reported error for the cause.

Action: Examine the exception in the log for more information about how to correct the problem.
Level: 1

Type: ERROR

Impact: Connector

BEA-199017: Error closing virtual JAR file for {0}, {1}

Cause: The virtual JAR file cannot be closed. See the reported error for the cause.

Action: Examine the exception in the log for more information about how to correct the problem.
Level: 1

Type: ERROR

Impact: Connector

BEA-199018: Error creating virtual JAR file for {0}, {1}

Cause: The virtual JAR file cannot be created. See the reported error for the cause.

Action: Examine the exception in the log for more information about how to correct the problem.
Level: 1

Type: ERROR

Impact: Connector

BEA-199019: Failed to initialize the connector-specific JNDI sub-contexts for the application, {0}, {1}

Cause: The connector-specific JNDI sub-contexts cannot be initialized. See the reported error for the cause.

Action: Examine the exception in the log for more information about how to correct the problem.
Level: 1

Type: ERROR

Impact: Connector

BEA-199020: Failed to prepare changes for dynamic update, {0}, {1}

Cause: Changes for dynamic update cannot be prepared. See the reported error for the cause.

Action: Examine the exception in the log for more information about how to correct the problem.
Level: 1

Type: ERROR

Impact: Connector

BEA-199021: JNDI name is null or empty.

Cause: The JNDI name must contain characters that are not spaces.

Action: Check the JNDI name.
Level: 1

Type: ERROR

Impact: Connector

BEA-199022: Unable to get InitialContext while attempting to verify JNDI name of a resource adapter object.

Cause: Failed to create the InitialContext.

Action: Check the environment properties of the InitialContext.
Level: 1

Type: ERROR

Impact: Connector

BEA-199023: ResourceLink is null or empty.

Cause: ResourceLink is null or empty.

Action: Check the ResourceLink.
Level: 1

Type: ERROR

Impact: Connector

BEA-199024: Unable to get InitialContext while attempting to verify resource link of resource adapter.

Cause: The InitialContext cannot be created.

Action: Check the environment properties of the InitialContext.
Level: 1

Type: ERROR

Impact: Connector

BEA-199028: Resource Adapter with JNDIName: {0} already deployed.

Cause: Multiple apdaters are deployed with the same JNDI name.

Action: Change the adapter's JNDI name in deployment descriptor.
Level: 1

Type: ERROR

Impact: Connector

BEA-199029: Bind operation failed: {0}, {1}

Cause: The JNDI name cannot be bound. See the reported error for the cause.

Action: Examine the exception in the log for more information about how to correct the problem.
Level: 1

Type: ERROR

Impact: Connector

BEA-199031: Failed to unbind the ConnectionFactory, {0}, {1}

Cause: The ConnectionFactory cannot be unbound. See the reported error for the cause.

Action: Examine the exception in the log for more information about how to correct the problem.
Level: 1

Type: ERROR

Impact: Connector

BEA-199032: Unable to getInitialContext() during unbindConnectionFactory, {0}

Cause: The getInitialContext() method cannot be called. See the reported exception for the cause.

Action: Examine the exception in the log for more information about how to correct the problem.
Level: 1

Type: ERROR

Impact: Connector

BEA-199036: ResourceLink: {0} already bound into application-scoped JNDI tree.

Cause: The ResourceLink has been bound into the JNDI tree.

Action: Change the JNDI name of ResourceLink.
Level: 1

Type: ERROR

Impact: Connector

BEA-199037: Unable to bind to the app-scoped jndi tree: {0}#{1} : {2}

Cause: The ResourceLink cannot be bound. See the reported error for the cause.

Action: Examine the exception in the log for more information about how to correct the problem.
Level: 1

Type: ERROR

Impact: Connector

BEA-199038: NamingException while trying to unbind references during unbindAdminObject of resource adapter, {0}

Cause: AdminObjects cannot be unbound. See the reported error for the cause.

Action: Examine the exception in the log for more information about how to correct the problem.
Level: 1

Type: ERROR

Impact: Connector

BEA-199039: Unable to get the connection factory for {0}. Verify that the resource adapter has been deployed.

Cause: The connection factory cannot be found.

Action: Verify that the resource adapter has been deployed.
Level: 1

Type: ERROR

Impact: Connector

BEA-199041: An exception occurred while calling newInstance in the Resource Adapter, classname = {0}, Exception = {1}.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199042: An exception occurred while trying to create the Connector Diagnostic Image, Exception = {0}.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199043: Trying to prepare a resource adapter that has not been initialized.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199044: Trying to activate a resource adapter that has not been prepared. Current state : {0}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199045: Trying to rollback an RA that is in the ACTIVATED state

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199046: Unable to create the native lib directory.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199047: Bad resource adapter class specification for class "{0}": {1}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199048: Trying to version a resource adapter that is not versionable.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199049: Unable to populate the Work Manager during resource adapter initialization.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199050: Caught exception while starting the resource adapter : {0}, {1}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199051: Caught exception while creating the BootstrapContext : {0}, {1}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199052: Unable to version the resource adapter.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199053: Unable to set up the work runtimer.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199054: Unable to introspect the object that was passed in. {0}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199055: Unable to get the setter method for the key: {0}.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199056: Unable to invoke the setter method for the key: {0}.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199065: An invalid type {0} has been specified for a key.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199066: For property "{0}", the type and value do not match. Type = {1}, Value = {2}, Exception: {3}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action accordingly.
Level: 1

Type: ERROR

Impact: Connector

BEA-199067: LoginException while trying to establish security identity for user "{0}" in weblogic-ra.xml element {2}: {1}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199068: No deployed ResourceAdapter with adapter JNDI name = "{0}" was found.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199071: Unable to initialize ActivationSpec {0}. Cause unknown.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199072: Failed to instantiate class {0}, {1}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199073: {0} passed {1} of "{2}".

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199074: Required Configuration Properties Missing in ActivationSpec: {0}.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199075: Located a resource adapter with JNDI name = "{0}", but that adapter is not yet fully deployed and active.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199076: Could not locate a resource adapter with JNDI name = "{0}".

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199077: The resource adapter with JNDI name = "{0}" does not have a <messagelistener> element with a <messagelistener-type> of "{1}".

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199089: The resource adapter does not have a <inbound-resourceadapter> element in ra.xml.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199090: The resource adapter does not have a <messageadapter> element in ra.xml.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199091: The resource adapter does not have any <messagelistener> elements in ra.xml.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199092: Internal error occurred, Assertion Failed: {0}

Cause: An internal consistency check failed indicating a software defect.

Action: Please note the circumstances of the error as well as any related log messages and contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-199093: setDyeBits failed because diagnostic contexts are not enabled.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199094: Invalid dye value specified, {0}. Value must be between 0 and 15 in order to fit within a 4-bit space.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199095: getDyeBits failed, moduleName = {0}: {1}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199096: setDyeBits failed: Failed to obtain Diagnostic Context. ModuleName = {0}.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199097: getDyeBits failed because Diagnostic Contexts are not enabled.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199098: This connection does not meet the criteria for manual deletion.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199099: Failed to setup the Resource Adapter Connection for enlistment in the transaction, Pool = "{0}", {1}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199100: Resource Adapter threw Non-ResourceException from its implementation of ManagedConnection.getLocalTransaction(), Pool = "{0}", {1}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199101: Resource Adapter returned null from its implementation of ManagedConnection.getLocalTransaction(), Pool = "{0}".

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199102: Unable to register NonXAResource, {0}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199103: Commit Failed: {0}, Stack Trace: {1}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199104: Rollback Failed: {0}, Stack Trace: {1}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199105: Resource Adapter returned null from ManagedConnection.getXAResource() while trying to obtain XAResource for recovery.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199106: Resource Adapter threw non-ResourceException in call to ManagedConnection.getXAResource(): {0}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199107: Resource Adapter returned null from ManagedConnectionFactory.createManagedConnection() while trying to create ManagedConnection for recovery.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199108: Failed to initialize ManagedConnection for recovery: {0}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199109: Connector Internal Error: Illegal type found during enlistResource.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199110: Connector Internal Error: Invalid type found in registerResource: {0}.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199111: Attempt to start an XA Transaction inside a Resource Adapter's Local Transaction is illegal.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199112: Failed to create managed connection: {0}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199113: Failed to setup the ManagedConnection with WLS after successfully getting it from a call to the Resource Adapter's ManagedConnectionFactory.createManagedConnection method.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199114: Internal WLS Connector Error: Object Id is null.

Cause: Check the logs for the cause of this exception.

Action: Please contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-199116: Resource Adapter Error: getConnection method returned null from the adapter's ManagedConnection implementation in class "{0}".

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199117: The resource adaptor has returned the same connection handle that was returned on a prior call to getConnection(). A new connection handle must be returned with every call to getConnection() as per the JCA specification.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199118: While testing connection, the adapter's implementation of getInvalidConnections() threw ResourceException: {0}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199119: While testing connection, the adapter's implementation of getInvalidConnections() threw non-ResourceException: {0}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199120: Connections should not be tested for a ManagedConnectionFactory that does not implement ValidatingManagedConnectionFactory.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199121: The ResourceAdapter with pool = "{0}" passed a null value to the Application Server's implementation of the lazyEnlist method for the ConnectionManager class.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199122: Access to resource adapter, with pool = "{0}", has been denied.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199123: Unable to get a connection for pool = "{0}", {1}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199124: Pool "{0}" is disabled, cannot allocate resources to applications.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199125: The resource adapter's implementation of ManagedConnectionFactory returned null from the createConnectionFactory() method.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199126: Stack trace at connection create:

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199127: Local Transaction not supported for this Resource Adapter.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199128: The connection handle has not been set for the connection closed event as per the JCA specification.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199129: Error preparing the pool with key : "{0}", {1}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199130: Unable to resume the pool, {0}.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199131: Unable to bind to the jndi tree : "{0}", {1}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199132: Key = {0}, Message = {1}, Exception = {2}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199133: Unable to shut down the pool : Key = "{0}", Message = {1}, Exception = {2}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199134: Attempting to create a connection factory with a JNDI name that already exists: "{0}".

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199135: Attempting to create a connection factory with a resource link that already exists: "{0}".

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199136: There was a problem verifying the JNDI name of the outbound connection: {0}, {1}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199137: The ManagedConnectionFactory class implementation "{0}" does not implement the ResourceAdapterAssociation interface and does not implement setResourceAdapter() and/or getResourceAdapter().

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199138: Unable to set the ResourceAdapter class for the mcf "{0}", {1}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199139: Unexpected exception thrown by resource adapter's ManagedConnectionFactory implementation "{0}", {1}.

Cause: Check the logs for the cause of this exception.

Action: Take appropriate action based on the cause reported in the logs.
Level: 1

Type: ERROR

Impact: Connector

BEA-199140: Could not find the managed connection factory class "{0}", {1}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199141: Failed to instantiate the resource adapter's implementation of the ManagedConnectionFactory class "{0}," {1}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199142: Unable to access the Resource Adapter' implementation of the ManagedConnectionFactoryClass "{0}", {1}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199143: Internal WebLogic Server Connector Error: Failed to get the connection pool for jndiName: "{0}".

Cause: Check the logs for the cause of this exception.

Action: Please contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-199144: A resource adapter may only be accessed from within the same application from which it was deployed.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199145: Operation is not supported, {0}, {1}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199146: If only a weblogic-ra.xml has been specified for the resource adapter, it must be a linkref.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199147: The resource adapter only has a weblogic-ra.xml specified. It also needs the ra.xml.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199148: Error Creating Native Lib Directory: {0}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199149: FileNotFoundException when creating native lib dir for {0}.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199150: Failure while creating native library directory for {0}, {1}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199151: An error occurred while starting the pool: {0}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199152: test-frequency-seconds is set to non-zero.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199153: Connection testing cannot be enabled for a pool when the ManagedConnectionFactory does not implement ValidatingManagedConnectionFactory. The following invalid settings have been detected:

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199154: Work instance passed in to the Work Manager is null.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199155: The Work Manager is currently not accepting doWork() calls.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199156: The Work Manager is currently suspended. New work is not being accepted.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199157: Unable to establish Execution Context or enlist work in imported transaction, {0}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199158: Global tx id "{0}" not associated with specified Work instance.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199159: Global tx id "{0}" not registered with the Work Manager.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199160: The <security-principal-map> element was deprecated in WebLogic Server 7.0 and is no longer supported. Please remove the element from the weblogic-ra.xml for the Resource Adapter.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199161: Work instance with global tx id "{0}" already active; conncurrent work disallowed.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199162: Bad ManagedConnectionFactory class specification for class "{0}" : {1}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199164: Unable to activate the pool, {0}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199165: test-connections-on-create is set to true.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199166: test-connections-on-release is set to true.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199167: test-connections-on-reserve is set to true.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199168: Unable to force log rotation: The connection pool for "{0}" is configured to use the server log.

Cause: Log rotation cannot be forced for pools that are configured to use the server log.

Action: Change the pool's logging parameters to use a different log other than the server log.
Level: 1

Type: ERROR

Impact: Connector

BEA-199169: Failed to get the Connection Factory for the pool "{0}", {1}

Cause: See the details of the error message for more information.

Action: See the details of the error message for more information.
Level: 1

Type: ERROR

Impact: Connector

BEA-199170: For the setting {0}: "{1}" has higher privileges than the deployment user: "{2}".

Cause: The deployment user does not have the privileges to perform the current deployment action.

Action: Try the deployment action with a user account that has administrator privileges.
Level: 1

Type: ERROR

Impact: Connector

BEA-199171: The security-principal-map is not a valid element.

Cause: The security-principal-map is not a valid element. You will need to define the mapping using the Administration Console.

Action: Define the mapping using the Administration Console.
Level: 1

Type: ERROR

Impact: Connector

BEA-199172: The following error occurred in the ra.xml: {0}

Cause: Refer to the text of the message for the description of the problem and the likely cause.

Action: Correct the problem in the ra.xml file.
Level: 1

Type: ERROR

Impact: Connector

BEA-199173: The following error occurred in the weblogic-ra.xml file: {0}

Cause: Refer to the text of the message for the description of the problem and the likely cause.

Action: Correct the problem in the weblogic-ra.xml file.
Level: 1

Type: ERROR

Impact: Connector

BEA-199174: The resource adapter (RA) was deactivated previously when it was in "Suspended" state. The RA cannot be activated again since this will lead to inconsistent state. Redeploy the RA to bring it back to a normal state. Current state: {0}.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199175: This ManagedConnection is managed by a container for its transactional behavior and has been enlisted to a JTA transaction by a container; application/adapter must not call the local transaction begin/commit/rollback API. Reject event {0} from adapter.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199176: Unable to execute {1} on ConnectionManager. A stale Connection Factory or Connection Handle may be used. The connection pool associated with it has already been destroyed. Try to perform another lookup of the Connection Factory {0} from JNDI and get a new Connection Handle.

Cause: A stale Connection Factory or Connection Handle was used.

Action: Perform another lookup of the Connection Factory from JNDI and get a new Connection Handle.
Level: 1

Type: ERROR

Impact: Connector

BEA-199177: Trying to deserialize an obsolete ConnectionManager.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199178: Deploy side-by-side versioning of resource adapter with JNDI name {0}; old version: {1}; new version: {2}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-199179: This adapter will not be deployed as side-by-side versioning since there is no old version adapter instance deployed.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-199180: This application EAR is not deployed in side-by-side versioning style.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-199181: Waiting complete callback from Side-by-side versioning adapter {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-199182: The resource adapter with module name {0} version {1} called ExtendedBootstrapContext.complete() to indicate it is safe to undeploy.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-199183: HintsContext: Ignore unknown hint name [{0}] and its value [{1}].

Cause: An unknown hint was used.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: WARNING

Impact: Connector

BEA-199184: ManagedConnectionFactory of connection pool [{0}] implements javax.resource.spi.TransactionSupport interface. Will use runtime TransactionSupport value [{2}] and igore the value [{1}] configured in DD or annotation.

Cause: A new feature was used, see Section 7.13 of the Connector 1.6 specification.

Action: No action is required if this behavior is expected.
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-199185: There is no META-INF/validation.xml file in the adapter archive {0}. The default Bean Validation configuration will be used.

Cause: No META-INF/validation.xml file was found in the RAR archive.

Action: No action is required if this behavior is expected.
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-199186: Found META-INF/validation.xml in adapter archive {0}.

Cause: A META-INF/validation.xml file was found in the RAR archive.

Action: No action is required if this behavior is expected.
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-199187: Found {2} constraint violation error(s) for {0} on instance [{1}]: {3}

Cause: Bean Validation failed and got constraint violation errors.

Action: Check the adapter configuration.
Level: 1

Type: WARNING

Impact: Connector

BEA-199188: Bean validation failed when validating for {0} on bean instance [{1}]. Exception: {2}

Cause: Bean validation failed.

Action: Check the adapter configuration and exception details.
Level: 1

Type: WARNING

Impact: Connector

BEA-199189: A long-running work submission has been rejected because the count of current active long-running work requests has reached the MaxConcurrentLongRunningRequests limit {0}.

Cause: A long-running work submission was rejected because the count of current active long-running work requests has reached the MaxConcurrentLongRunningRequests limit {0}.

Action: Check the adapter configuration and increase MaxConcurrentLongRunningRequests if necessary.
Level: 1

Type: WARNING

Impact: Connector

BEA-199190: The max-concurrent-long-running-requests limit was changed from {0} to {1}.

Cause: The configuration was changed or initialized.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-199191: Warning: Caller application {2} defines a shareable resource reference {1} to outbound connection pool {0}, but the pool does not support share by its design since its ManagedConnectionFactory class has @Unshareable annotation. Will treat as unshareable.

Cause: An invalid resource reference definition was made to an unshareable ConnectionFactory.

Action: Change the SharingScope of the resource reference definition to Unshareable.
Level: 1

Type: WARNING

Impact: Connector

BEA-199192: Warning: Caller application {2} defines a resource reference {1} to outbound connection pool {0} without define SharingScope explicitly. The pool does not support share by its design since its ManagedConnectionFactory class has @Unshareable annotation. Will treat as unshareable.

Cause: An invalid resource reference definition was made to an unshareable ConnectionFactory.

Action: Change the SharingScope of the resource reference definition to Unshareable.
Level: 1

Type: WARNING

Impact: Connector

BEA-199193: ManagedConnection {0} of connectionInfo {1} in Connection Pool {2} has been destroyed already. Previous destroy stacktrace: {3} New destroy stacktrace: {4}

Cause: The ManagedConnection was destroyed again.

Action: Check the server log.
Level: 1

Type: WARNING

Impact: Connector

BEA-199194: Resource adapter generated unexpected exception during work event notification for event {0}. Ignored. Exception: {1}

Cause: The resource adapter generated an unexpected exception during work event notification.

Action: Check the work event processing codes of the resource adapter.
Level: 1

Type: WARNING

Impact: Connector

BEA-199195: Connector annotation scan: Ignored unexpected error [{2}] when processing annotations on {0} while {1}.

Cause: Check the error message and stacktrace to determine the cause.

Action: Check error message and stacktrace to determine the appropriate action to take.
Level: 1

Type: WARNING

Impact: Connector

BEA-199196: Ignore @javax.resource.Connector annotation on class {0} since ResourceAdapter Bean {1} is already specifed in ra.xml.

Cause: ra.xml already specifies the ResourceAdapter bean to use.

Action: No action is required if this behavior is expected.
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-199197: An exception occurred when removing admin object {0}. Exception is: {1}

Cause: This exception occurs as the result of an attempt to unbind the admin object from JNDI.

Action: Examine the log for the exact exception. Report the error to My Oracle Support.
Level: 1

Type: WARNING

Impact: Connector

BEA-199198: An exception occurred when invoking preDestroy on {0}: {1}. Exception is: {1}

Cause: This exception occurs as the result of the CDI container calling the preDestroy method.

Action: Examine the log for the exact exception. You may need to report the error the resource adapter vendor.
Level: 1

Type: WARNING

Impact: Connector

BEA-199199: The work was rejected because it has expired before WorkManager executed it.

Cause: The time value for the startTimeout argument is too short. The WorkManager cannot start the work within the specified time period.

Action: Increase the time value for the startTimeout argument and ensure that it is big enough for WarkManager to start the work.
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-199200: Annotation scan/process of the resource adapter {0} resulted in the following {1} warnings: {2}

Cause: The specified resource adapter failed to pass the annotation scan/process as indicated by the listed warnings.

Action: Check warning messages and fix the annotations that are involved.
Level: 1

Type: WARNING

Impact: Connector

BEA-199201: Failed to merge resource adapter {0} when processing annotations due to {1} error(s) found.

Cause: Failed to merge resource adapter {0} when processing annotations due to {1} error(s) found.

Action: Check the errors and fix them.
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-199202: Ignored unexpected exception [{1}] when unregistering runtime mbean {0}.

Cause: Check error message and stack trace to figure out the cause.

Action: Take appropriate action based on the cause determined from the reported error message and stack trace.
Level: 1

Type: WARNING

Impact: Connector

BEA-199211: Compliance checking and validation of the resource adapter {0} resulted in the following non-critical errors: {1}

Cause: The specified resource adapter failed to pass compliance and validity checking as indicated by the listed warnings and errors.

Action: Correct the ra.xml or weblogic-ra.xml files, or check the resource adapter archive.
Level: 1

Type: WARNING

Impact: Connector

BEA-199212: Failed to create connection pool [{0}] due to error: {1}

Cause: Check the reported error message and stack trace to determine the cause.

Action: Take appropriate action based on the cause determined from the reported error message and stack trace.
Level: 1

Type: ERROR

Impact: Connector

BEA-199213: A new error occurred when trying to destroy a connection pool [{0}] that was previously in a failed state : the following new error will be ignored: {1}

Cause: Check the error message and stack trace to determine the cause.

Action: Take appropriate action based on the cause determined from the reported error message and stack trace.
Level: 1

Type: WARNING

Impact: Connector

BEA-199214: The connection pool [{0}] was in a HEALTH_CRITICL state already, therefore this method call is not allowed.

Cause: Check the error message and stack trace to determine the cause.

Action: Take appropriate action based on the cause determined from the reported error message and stack trace.
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-199215: The connection pool [{0}] will move to a HEALTH_CRITICAL state because the adapter is not in deploy-as-a-whole mode. This pool failed due to errors: {1}

Cause: Check the error message and stack trace to determine the cause.

Action: Take appropriate action based on the cause determined from the reported error message and stack trace.
Level: 1

Type: WARNING

Impact: Connector

BEA-199216: An error occurred when performing action {2} on connection pool [{0}]. The following error will be ignored: {1}

Cause: Check the error message and stack trace to determine the cause.

Action: Take appropriate action based on the cause determined from the reported error message and stack trace.
Level: 1

Type: WARNING

Impact: Connector

BEA-199217: Connection pool [{0}] has validation errors and cannot be reset. Try to fix all validation errors and then do a dynamic update or redeploy this adapter.

Cause: Check the error message and stack trace to determine the cause.

Action: Try to fix all validation errors and then do a dynamic update or redeploy this adapter.
Level: 1

Type: WARNING

Impact: Connector

BEA-199218: Unable to determine whether properties were changed for Connection pool [{0}]. If there are changed properties, they may be ignored during a dynamic update: {1}

Cause: Check the error message and stack trace to determine the cause.

Action: Try to fix all validation errors and then do a dynamic update or redeploy this adapter.
Level: 1

Type: WARNING

Impact: Connector

BEA-200000: Failed to initialize the messaging bridge service.

Cause: Most of the time, this results from configuration errors.

Action: Check the configuration file and reboot the system.
Level: 1

Type: ERROR

Impact: MessagingBridge

BEA-200001: The messaging bridge service has successfully shut down.

Cause: This message indicates that the messaging bridge service has been shut down, either at the request of the administrator or due to errors.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MessagingBridge

BEA-200002: Failed to deploy the messaging bridge "{0}" because the messaging bridge service is shut down.

Cause: This message indicates that the messaging bridge service has been shut down, either at the request of the administrator or due to errors.

Action: Reboot the system.
Level: 1

Type: ERROR

Impact: MessagingBridge

BEA-200003: Failed to deploy the messaging bridge "{0}" due to error: {1}.

Cause: This is likely due to configuration errors or an internal error as indicated in the message body.

Action: Check the configuration file, and reboot the server.
Level: 1

Type: ERROR

Impact: MessagingBridge

BEA-200004: The messaging bridge "{0}" has been successfully deployed.

Cause: This message indicates that the messaging bridge has been successfully deployed.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MessagingBridge

BEA-200005: Failed to start messaging bridge "{0}" due to error: {1}

Cause: This is likely due to configuration errors or an internal error, as indicated in the message body.

Action: Check the configuration file, and reboot the server.
Level: 1

Type: ERROR

Impact: MessagingBridge

BEA-200008: Bridge "{0}" does not have a configured source destination.

Cause: This is likely due to configuration errors.

Action: Update the configuration, and restart the server.
Level: 1

Type: ERROR

Impact: MessagingBridge

BEA-200009: Bridge "{0}" does not have a configured target destination.

Cause: This is likely due to configuration errors.

Action: Update the configuration, and restart the server.
Level: 1

Type: ERROR

Impact: MessagingBridge

BEA-200011: The bridge "{0}" failed to find the adapter "{1}". The bridge will periodically retry to look up the adapter. If this message stops reappearing, it means that the bridge has finally successfully found the adapter.

Cause: One of the adapters was not deployed.

Action: Deploy the required adapters.
Level: 1

Type: WARNING

Impact: MessagingBridge

BEA-200012: Bridge "{0}" successfully found the adapters that are configured for it.

Cause: This message indicates that the bridge successfully found the adapters.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MessagingBridge

BEA-200013: Invalid properties are defined for the source destination of bridge "{0}".

Cause: The configuration was invalid.

Action: Update the configuration, and restart the server.
Level: 1

Type: ERROR

Impact: MessagingBridge

BEA-200014: Invalid properties are defined for the target destination of bridge "{0}".

Cause: The configuration was invalid.

Action: Update the configuration, and restart the server.
Level: 1

Type: ERROR

Impact: MessagingBridge

BEA-200015: An error occurred in bridge "{0}" during the transfer of messages ({1}).

Cause: An error occurred on one of the bridge destinations.

Action: Check the system on both the source and target sides, and restart the server.
Level: 1

Type: ERROR

Impact: MessagingBridge

BEA-200020: Bridge "{0}" is stopped.

Cause: This message indicates that the messaging bridge has stopped.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MessagingBridge

BEA-200021: Bridge "{0}" failed to get one of the adapters from JNDI ({1}).

Cause: At least one adapter was not deployed when the bridge started. It is also possible that the JNDI names configured in the bridge destinations do not match the ones in the adapter deployment descriptor file.

Action: Check to see if the adapter(s) required by the source and target destinations are deployed on the server where the bridge is configured. Ensure that the JNDI name in the adapter deployment descriptor file matches the one in the configuration of the bridge destinations. Otherwise, no action is required. The bridge will automatically try again later.
Level: 1

Type: NOTIFICATION

Impact: MessagingBridge

BEA-200022: Bridge "{0}" failed to obtain adapter metadata ({1}).

Cause: This is an internal error that should not occur.

Action: No action is required.
Level: 1

Type: ERROR

Impact: MessagingBridge

BEA-200024: Bridge "{0}" refused to obtain connections and transfer any messages, because it has been stopped, suspended, or is shutting down.

Cause: The administrator has shut down or stopped the bridge, or the bridge is suspended for migration.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MessagingBridge

BEA-200025: Bridge "{0}" failed to start because the quality of service configured ({1}) is unreachable. This is likely due to an invalid configuration or adapter limitations.

Cause: The configuration does not match the ability of the adapters and underlying systems.

Action: Change the configuration of the bridge with a reachable quality of service, or turn on the QOSDegrationAllowed boolean.
Level: 1

Type: ERROR

Impact: MessagingBridge

BEA-200026: Bridge "{0}" encountered problems in one of its adapters or underlying systems. It stopped transferring messages and will try to reconnect to the adapters shortly. (The exception that occurred was {1})

Cause: There was a problem in receiving or sending messages to one of the sides of the bridge.

Action: No action is required.
Level: 1

Type: WARNING

Impact: MessagingBridge

BEA-200027: Bridge "{0}" works in asynchronous mode and has not received messages for the predefined maximum idle time. The connections to the adapters will be interrupted and reestablished.

Cause: This may occur because the source destination is empty or because the connection to the source was stale and needs to be reestablished.

Action: Check the source system.
Level: 1

Type: NOTIFICATION

Impact: MessagingBridge

BEA-200028: The bridge "{0}" has started transferring messages.

Cause: This message indicates that the bridge has just started transferring messages.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MessagingBridge

BEA-200030: Bridge "{0}" is configured to work in "{1}" mode, but it is actually working in "{2}" mode.

Cause: This message reveals what quality of service the bridge is actually providing.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MessagingBridge

BEA-200031: Bridge "{0}" is configured to allow degradation of its quality of service in cases where the configured quality of service cannot be reached.

Cause: This message indicates that the quality of service of this bridge is allowed to be downgraded if the required one is unreachable.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MessagingBridge

BEA-200032: Bridge "{0}" is configured to disallow degradation of its quality of service in cases where the configured quality of service is unreachable.

Cause: This message indicates that the quality of service of the bridge is not allowed to be downgraded.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MessagingBridge

BEA-200033: Bridge "{0}" is obtaining connections to the two adapters.

Cause: This message indicates that the messaging bridge is obtaining connections to the two adapters.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MessagingBridge

BEA-200034: Bridge "{0}" is shut down.

Cause: This message indicates that the messaging bridge is shut down.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MessagingBridge

BEA-200035: Bridge "{0}" has been started from the stopped mode.

Cause: This message indicates that the bridge was in stopped mode and has just been restarted.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MessagingBridge

BEA-200036: The started attribute of bridge "{0}" has been changed from "{1}" to "{2}".

Cause: This is due to a configuration change.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MessagingBridge

BEA-200037: The "{1}" attribute of bridge "{0}" has been changed from "{2}" to "{3}".

Cause: This is due to a configuration change.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MessagingBridge

BEA-200038: Bridge "{0}" is inactive because it is configured to be stopped.

Cause: The bridge is configured to be stopped.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MessagingBridge

BEA-200039: Bridge "{0}" has the same destination as its source and target.

Cause: This is due to a configuration error.

Action: Update the configuration.
Level: 1

Type: ERROR

Impact: MessagingBridge

BEA-200040: Bridge destination {0}: connection URL cannot be null if the initial context factory is not weblogic.jndi.WLInitialContextFactory.

Cause: This is due to a configuration error.

Action: Update the configuration.
Level: 1

Type: ERROR

Impact: MessagingBridge

BEA-200041: Bridge destination {0}: a bridge destination for JMS must have a connection factory JNDI name and a destination JNDI name configured.

Cause: This is due to a configuration error.

Action: Update the configuration.
Level: 1

Type: ERROR

Impact: MessagingBridge

BEA-200042: Bridge {0} failed to connect to the source destination and will try again in {2} seconds. This could be a temporary condition unless the messages repeat several times. ({1})

Cause: An error occurred on the source destination of the bridge. The error may occur because the source destination does not exist or has not been active yet.

Action: Check the source system and its configuration. Ensure that the destination is configured in the system and the system is running.
Level: 1

Type: NOTIFICATION

Impact: MessagingBridge

BEA-200043: Bridge "{0}" failed to connect to the target destination and will try again in {2} seconds. This could be a temporary condition unless the messages repeat several times. ({1})

Cause: The error occurred on the target destination of the bridge. The error may occur because the target destination does not exist or has not been active yet.

Action: Check the target system and its configuration. Ensure that the destination is configured in the system and the system is running.
Level: 1

Type: NOTIFICATION

Impact: MessagingBridge

BEA-200044: The following exception has occurred:

Cause: An error condition has occurred.

Action: Look for the associated exception in the log or the program to see the results. In general, this stack trace will help in debugging an existing problem.
Level: 1

Type: ERROR

Impact: MessagingBridge

BEA-200045: Bridge "{0}" failed to start because it has been suspended or is shutting down.

Cause: The administrator has shut down the bridge, or the bridge is suspended for migration.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MessagingBridge

BEA-200046: The "{1}" attribute of bridge "{0}" has been changed from "{2}" to "{3}".

Cause: This is due to a configuration change.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MessagingBridge

BEA-200047: Bridge "{0}" failed to start because its migratable target has not been activated for this server.

Cause: The bridge is targeted to a migrable target that has not yet been activated on this server.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MessagingBridge

BEA-220000: Web services startup

Cause: This is a normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220001: The server at {0} did not provide a valid HTTP response: {1}

Cause: The server may not be properly configured.

Action: Verify the server configuration and retry the request.
Level: 1

Type: INTERNAL_ERROR

Impact: WebService

BEA-220002: The server at {0} did not provide a valid HTTP response: {1}

Cause: The HTTP header status length does not agree.

Action: Verify the server configuration and retry the request.
Level: 1

Type: INTERNAL_ERROR

Impact: WebService

BEA-220003: The server at {0} did not provide a valid HTTP response: {1}

Cause: The server is not providing HTTP V1.0 or V1.1 protocol.

Action: Verify the server configuration and retry the request.
Level: 1

Type: INTERNAL_ERROR

Impact: WebService

BEA-220004: The server at {0} did not provide a valid HTTP response: {1}

Cause: The returned server status code was not recognized.

Action: Verify the server configuration and retry the request.
Level: 1

Type: INTERNAL_ERROR

Impact: WebService

BEA-220005: The server at {0} did not provide a valid HTTP response: {1}.

Cause: The server status code was given.

Action: Verify the server configuration and retry the request.
Level: 1

Type: INTERNAL_ERROR

Impact: WebService

BEA-220006: Content-length was specified but no value was provided.

Cause: The content-length field must contain a value.

Action: Verify the server configuration and retry the request.
Level: 1

Type: INTERNAL_ERROR

Impact: WebService

BEA-220007: The specified content-length {0} is invalid.

Cause: The provided content-length field is invalid.

Action: Verify the server configuration and retry the request.
Level: 1

Type: INTERNAL_ERROR

Impact: WebService

BEA-220008: HTTP keep-alive was specified, but the content-length was not set.

Cause: The provided content-length field is invalid.

Action: Verify the server configuration and retry the request.
Level: 1

Type: INTERNAL_ERROR

Impact: WebService

BEA-220009: Received EOF before reading the entire message from the server.

Cause: The server sent an EOF (end-of-file) before the entire message was received.

Action: Verify the server configuration and retry the request.
Level: 1

Type: INTERNAL_ERROR

Impact: WebService

BEA-220010: A MIME-encoded SOAP response must include a content-type mime header specifying the MIME start and boundary.

Cause: The content-length was zero or the content-type was null. An attachment, however, was provided.

Action: Verify the server configuration and retry the request.
Level: 1

Type: INTERNAL_ERROR

Impact: WebService

BEA-220011: A bad value was provided for {0} : {1}. The default value will be used: {2}.

Cause: The value was not correctly provided.

Action: Correct the system configuration and retry the request.
Level: 1

Type: WARNING

Impact: WebService

BEA-220012: The ID may not be null.

Cause: The XML stream may be corrupted.

Action: Check the content of the XML stream and retry the message.
Level: 1

Type: INTERNAL_ERROR

Impact: WebService

BEA-220013: The ID referenced by {0} is unknown.

Cause: The XML stream is invalid or corrupted.

Action: The unknown ID must be resolved and the action retried.
Level: 1

Type: INTERNAL_ERROR

Impact: WebService

BEA-220014: Incorrect XML stream open. Use open(XMLNode node) to open this stream.

Cause: The module was incorrectly called.

Action: Correct the program to use XMLNode. After doing so, retry the action.
Level: 1

Type: INTERNAL_ERROR

Impact: WebService

BEA-220015: Incorrect XML stream open. Use open(XMLNode node) to open this stream.

Cause: The module was incorrectly called.

Action: Correct the program to use XMLNode. After doing so, retry the action.
Level: 1

Type: INTERNAL_ERROR

Impact: WebService

BEA-220016: The start element was not found.

Cause: The XML stream is corrupted.

Action: Correct the XML stream and retry the task.
Level: 1

Type: INTERNAL_ERROR

Impact: WebService

BEA-220017: Element {0} is not a start element.

Cause: The XML stream is corrupted.

Action: Correct the XML stream and retry the task.
Level: 1

Type: INTERNAL_ERROR

Impact: WebService

BEA-220018: The handler class:{0} issued an exception from its destroy method. This exception is ignored. The exception was: {1}.

Cause: A handler class issued an exception from its destroy method.

Action: Correct the handler Handler.destroy implementation.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220019: The Web services server responded with an empty HTTP response. The content-length of the response was 0.

Cause: The HTTP response had a content-length of 0.

Action:
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220020: The Web services call to {0}://{1}:{2} received an unexpected end of file (EOF) after reading {3} bytes.

Cause: The HTTP response had an unexpected EOF.

Action:
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220021: The Web services call to {0} received an unexpected HTTP version {1}.{2} in the response:{3}.

Cause: The HTTP response had an unexpected version.

Action:
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220022: Error reading the response from: {0}. Please ensure that this is a valid SOAP response. The message was: {1}

Cause: The HTTP response had an unexpected version.

Action:
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220023: Ignoring an exception in destroy() from Handler: {0}. The exception was: {1}.

Cause: An exception occurred in the handler destroy() method.

Action:
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220024: Handler {0} issued an exception from its handleRequest method. The exception was: {1}.

Cause: An exception occurred in the handler handleRequest() method.

Action:
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220025: Handler {0} issued an exception from its handleResponse method. The exception was: {1}.

Cause: An exception occurred in the handler handleResponse() method.

Action:
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220026: Handler {0} issued an exception from its handleFault method. The exception was: {1}.

Cause: An exception occurred in the handler handleFault() method.

Action:
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220027: Web services reliable agents have been started on the server.

Cause: Web services reliable agents have been started on the server.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220028: Web services reliable agents are suspended.

Cause: Web services reliable agents are suspended.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220029: Web services reliable agents are shut down.

Cause: Web services reliable agents are shut down.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220030: Failed to create Web services reliable agents. {0}.

Cause: There is a configuration error Administration Server failure.

Action: Check the configuration.
Level: 1

Type: ERROR

Impact: WebService

BEA-220031: The server does not support reliable SOAP messaging.

Cause: The server does not support reliable SOAP messaging.

Action: Check the configuration.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220032: Failed to create MessageContext after a SOAP message was recovered from the storage. {0}.

Cause: There was an invalid format from the store or an error accessing the store.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: WebService

BEA-220033: Failed to access the store for reliable delivery. {0}.

Cause: There was a failure accessing JMS.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: WebService

BEA-220034: A stack trace associated with message {0} follows:

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220035: A naming exception occurred while obtaining the initial context.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220036: An exception occurred while obtaining the JMS connection factory.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220037: An exception occurred while obtaining the JMS initial context.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220038: An exception was issued from the onMessage JMS.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220039: A naming exception was issued from the JMS send message.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220040: An exception was issued from JMS while obtaining the initial factory.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220041: An exception was issued from JMS when sending to the destination.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220042: A naming exception was issued from JMS for this queue.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220043: An exception was issued from JMS obtaining the factory.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220044: An exception was issued from JMS locating this queue.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220045: An exception was issued getting the conversational state.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220046: A remote exception was issued when getting the conversational state.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220047: An exception was issued from callReceive in the Client Dispatcher.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220048: An exception was issued from the client handler sending a JAXM message.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220049: A SOAP exception was issued from the client conversation handler.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220050: A SOAP exception was issued from the server conversation handler.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220051: A SOAP exception was issued from the Invoke handler.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220052: The target endpoint is a malformed URL.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220053: An unexpected exception was caught in the SOAP Envelope InputStream.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220054: An unexpected exception was caught in the SOAP Envelope Reader.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220055: A parse exception was caught in the SOAP Message content.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220056: A parse exception was caught in the get SOAP Message content.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220057: A messaging exception was caught while processing MIME SOAP Message content.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220058: A messaging exception was caught writing MIME SOAP Message content.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220059: A SOAP header exception was caught in setMustUnderstand.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220060: A SOAP header exception was caught in setActor.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220061: A Naming Exception was caught in the deployment descriptor verify.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220062: A Message Exception was caught in the Image Encoding Codec.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220063: A IO Exception was caught in the Image Encoding Codec.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220064: A Message Exception was caught in the XML Source Encoding Codec.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220065: A IO Exception was caught in the XML Source Encoding Codec.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220066: An InvalidAttributeValue Exception was caught trying to create the JMS Queue.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220067: A JMS Exception was caught when the listener was being closed.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220068: An exception was caught when introspecting the component.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220069: A Naming Exception was caught trying to locate the JMS transport.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220070: A JMS Exception was caught trying to create the JMS queue.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220071: A SOAPException was caught in the onMessage listening to the JMS queue.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220072: An IOException was caught in the onMessage listening to the JMS queue.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220073: A SOAPException was caught in the servlet base unable to invoke the service.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220074: A SOAPException was caught in the servlet base unable to send to the client.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220075: A SOAPException was caught in the servlet base unauthorized to send to the client.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220076: An exception was caught in the Web services servlet initialization.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220077: An exception was caught while processing the Web services deployment descriptor.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220078: An exception was caught when configuring the Web services servlet.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220079: An Interrupt exception was caught while waiting to send mail from the queue.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220080: An error was reported from the SMTP gateway.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220081: An IOException was reported from the SMTP quit command.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220082: An IOException was reported from the SMTP process read command.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220083: An IOException was reported from the SMTP process close command.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220084: A Binding exception was issued while trying to generate the implementation class.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220085: A JAXRPC exception was issued while trying to generate the implementation class.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220086: A IOException was issued while trying to generate the implementation class.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220087: A Binding exception was issued while trying to generate the EJB implementation.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220088: A JAXRPC exception was issued while trying to generate the EJB implementation.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220089: An IOException was issued while trying to generate the EJB implementation.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220090: A Binding exception was issued while trying to generate the client implementation.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220091: A JAXRPC exception was issued while trying to generate the client implementation.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220092: An IOException was issued while trying to generate the client implementation.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220093: A naming exception was issued while trying to check compliance of the given EJB.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220094: An IOException was issued while trying to access the WSDL at the given URL.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220095: An IOException was issued while converting the file to a string.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220096: A naming exception was issued from JMS for this queue.

Cause: An error condition was reported.

Action: Make sure that the queue can be accessed from this server.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220097: An exception was issued from JMS while obtaining the factory.

Cause: An error condition was reported.

Action: Make sure that the queue can be accessed from this server.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220099: Web service for Web application named {0} contextPath {1} with Web services {2} has been initialized.

Cause: This indicates a successful Web service deployment.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220100: An error occurred while registering this Web service for monitoring. Although this does not affect the Web service itself, monitoring information about it may be unavailable. The specific error was {0}.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: WARNING

Impact: WebService

BEA-220101: An error occurred while loading class {1} from handler-chain {0} in global handler configuration. Error is: {2}

Cause: The configured class is not present in the classpath.

Action: Check the classpath and try again.
Level: 1

Type: ERROR

Impact: WebService

BEA-220102: An error occurred while loading global handler chain. Error is: {0}

Cause: An error may have occurred while parsing the server-handler-chain.xml file.

Action: Check the server-handler-chain.xml file and ensure that the syntax is correct.
Level: 1

Type: ERROR

Impact: WebService

BEA-220103: Async Web service support is not fully configured. The async response Web service {0} for this server was not fully deployed because the JMS reliability queue was not defined/deployed: {1}. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async Web service applications. To completely disable async Web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.

Cause: The JMS queue JNDI name specified in the WebservicesMBean (or allowed to default) was not found on this server. The async response service requires this JMS queue in order to operate. To avoid obscure errors while processing Web service async responses, this service was not fully deployed. Not having this JMS queue available can indicate that Web services have not been configured/enabled for this domain. The server will periodically retry deploying the service, so there is no need to restart the server once the JMS queue is made available.

Action: If you do not intend to use async Web services in this domain, no action is required. To avoid seeing this message and completely disable async Web service support, set -Dweblogic.wsee.skip.async.response=true. If you intend to use async Web services in this domain, define a non-distributed JMS queue with the local JNDI name given in WebservicesMBean (which has a default value), and after a short delay, the async response service will be fully deployed to use the newly defined queue. Oracle recommends that the JMS queue be located on a JMS server that is targeted to the same server as the Web service. Note that you can easily add async response Web services support to an existing domain by extending your domain with the Configuration Wizard and applying the wls_webservice.jar extension template. For more information, see the WebLogic Server online documentation in the 'Web Services->Get Started Using JAX-RPC' section.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220104: Web services async response service {0} for this server was just deployed because the reliability queue was found: {1}

Cause: The queue specified in the WebservicesMBean (or allowed to default) was recently deployed to this server. The async response service requiring this queue is now deployed.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220105: Web services async/reliable invocations for service {0} are NOT available because the async/reliability queue was not found: {1}

Cause: You have deployed a Web service that indicates it can use async/reliable features, but the queue for async/reliable invocations (specified in WebservicesMBean, @Buffer or @ReliabilityBuffer annotations, or allowed to default) is not deployed to the local server. Therefore, async and reliable invocations will fail if attempted. Standard synchronous invocations will still work correctly despite this problem.

Action: Remove any async or reliable features from the Web service (e.g. @AsyncResponse, @Buffer, @ReliabilityBuffer annotations or @Policy annotations specifying reliable policy) or properly configure this server for async/reliable invocations. See the WebLogic Server online documentation in the 'Web Services->Get Started Using JAX-RPC' section for help on fixing this configuration problem. Once you have defined the proper async/reliable resources, you must redeploy your application.
Level: 1

Type: WARNING

Impact: WebService

BEA-220106: OWSM Security requires that a WSDL be associated with the Web service.

Cause: You have deployed a Web service that does not have a WSDL associated with it.

Action: Associate a WSDL with the Web service. For example you can add a wsdlLocation attribute to a WebService or WebServiceProvider annotation.
Level: 1

Type: ERROR

Impact: WebService

BEA-220500: An unexpected error occurred: {0}

Cause: Unknown

Action: Contact Oracle support
Level: 1

Type: ERROR

Impact: WebService

BEA-220501: The service port {1} bound to https transport in service {0} is NOT available, the https address cannot be resolved because SSL is not enabled for the server. The service port definition will be removed from WSDL that is being accessed through {2}.

Cause: While a WSDL is being retrieved through http protocol, the server requires replacing the service port address in WSDL with the actual address for the server. For any web service which defines one or more service ports bound to https transport, if the domain does not enable SSL functionality then the service port address could not be replaced correctly because https address for the server cannot be resolved.

Action: Enable SSL functionality for the server.
Level: 1

Type: WARNING

Impact: WebService

BEA-220502: The Wsee Service is starting

Cause: This is an info message. No cause is needed

Action: No action required. This is an info message.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220503: The Wsee Service is stopping

Cause: This is an info message. No cause is needed

Action: No action required. This is an info message.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220504: The Wsee Service is halting

Cause: This is an info message. No cause is needed

Action: No action required. This is an info message.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220505: Implicit/generated Client Identity {0} has been used in multiple calls to Service.getPort()/createDispatch() where these calls have used different services and/or sets of features. Monitoring statistics for this client will include all these different usages. Validation failures were: {1}

Cause: WebLogic JAX-WS web service clients are assigned a unique identity that is intended to represent the business purpose of that client. This identity can be specified directly using weblogic.jws.jaxws.client.ClientIdentityFeature or it can be allowed to be implicit. Implicit identity is generated automatically based on environmental information at the point where a Port/Dispatch instance is created. Your code has received an implicit client identity that is getting used (again implicitly) across multiple services or sets of features. All statistics gathered for a given client instance are rolled up under the client instance's client identity. If client instances using different services and/or feature sets contribute statistics to the same client identity, this can be confusing. It is even possible for clients to behave incorrectly when more advanced web service features are used.

Action: Best practice is to create a specific client identity (with a name representing a logical business purpose) for the client and denote this identity by passing weblogic.jws.jaxws.client.ClientIdentityFeature to the call to Service.getPort/createDispatch. Further, it is recommended that you pass a single/global set of web service feature objects to that call (e.g. Create WebServiceFeature instances as static class members or in a method annotated with @PostConstruct for containers compatible with this annotation). The actual call to Service.getPort()/createDispatch() should still be made in any way that makes sense for your uses (e.g. calling getPort on demand in a web service method, with Service created as a static class member).
Level: 1

Type: WARNING

Impact: WebService

BEA-225010: Error starting the JMS listener {0} {1}

Cause: A connection to the JMS replyToQueue could not be made.

Action: Verify that the proper queue name is being used, and check the status of JMS queue.
Level: 1

Type: WARNING

Impact: WebService

BEA-225011: Error closing JMS connection {0} {1}

Cause: The JMS queue connection could not be closed.

Action: No action is required.
Level: 1

Type: WARNING

Impact: WebService

BEA-225012: JMS onMessage exception {0} {1}

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: WARNING

Impact: WebService

BEA-240001: {0}

Cause: The Administration Console logs informational messages about console usage.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Console

BEA-240002: {0}

Cause: The Administration Console encountered an error that is potentially harmful.

Action: Review the warning message text to determine the appropriate action.
Level: 1

Type: NOTIFICATION

Impact: Console

BEA-240003: Administration Console encountered the following error: {0}

Cause: The Administration Console encountered an error, but the console may continue to run.

Action: Review the error message text to determine the appropriate action.
Level: 1

Type: ERROR

Impact: Console

BEA-240004: The Administration Console encountered the following error: {0}

Cause: The Administration Console encountered a critical error.

Action: Review the message text to determine the appropriate action.
Level: 1

Type: INTERNAL_ERROR

Impact: Console

BEA-240005: A Cross-site Request Forgery (CSRF) has been detected. Task={0}, address={1}, user={2}

Cause: The Administration Console encountered a CSRF.

Action: Take action based upon the provided exception details.
Level: 1

Type: INTERNAL_ERROR

Impact: Console

BEA-260000: WebLogic Local Deployment Manager

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: J2EE Deployment SPI

BEA-260001: "{0}" does not identify a known Deployment Manager. The URI must be of the form: deployer:WebLogic:host:port. The host and port are required if attempting to acquire a connected Deployment Manager.

Cause: An invalid URI was provided when allocating a Deployment Manager.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260002: "{0}" is not a valid URI. The URI must be of the form: "deployer:WebLogic:protocol://host:port". The host and port are required if attempting to acquire a connected Deployment Manager. The protocol should be a well-known IP protocol.

Cause: Incorrect host/port used when attempting to allocate a Deployment Manager.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260003: Feature not available when in disconnected mode.

Cause: A deployment tool allocated a disconnected Deployment Manager or released it.

Action: Allocate a connected Deployment Manager.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260004: Locale, "{0}", is not supported.

Cause: The locale was incorrectly specified.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260008: J2EE version {0} not supported by this Deployment Manager.

Cause: An invalid argument was used.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260009: Exception caught for class "{0}" while attempting to create Deployment Manager: {1}

Cause: This is an internal error.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260010: Unable to connect to "{0}" as user, "{1}". Error received: {2}

Cause: Authorization failed.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260012: No configured targets match provided target with name, "{0}", and type, "{1}"

Cause: An invalid argument was used.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260013: The target array passed to Deployment Manager was null or empty.

Cause: An invalid argument was used.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260015: The "{0}" operation is not supported.

Cause: An invalid request was made; the operation is not supported.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260016: "{0}" does not exist.

Cause: An invalid argument was used.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260017: Unable to locate deployment task, "{0}"

Cause: The task was removed from the system.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260020: Module {1} of application {0} successfully transitioned from {2} to {3} on server {4}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: J2EE Deployment SPI

BEA-260021: Module {1} of application {0} failed to transition from {2} to {3} on server {4}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: J2EE Deployment SPI

BEA-260022: {2} application {0} on server {1}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: J2EE Deployment SPI

BEA-260023: Deployment task does not exist for ProgressObject

Cause: The deployment task was removed from the system.

Action: No action is required.
Level: 1

Type: WARNING

Impact: J2EE Deployment SPI

BEA-260024: Connection errors occurred while reporting a progress event. The event was from application, {0}, module, {1}, on server {2}. The event was {3}. The error was {4}.

Cause: There was a deployment failure.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: J2EE Deployment SPI

BEA-260026: Task failed for unknown reason. Task description is {0}

Cause: The cause is unknown.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260027: Non-root module, "{1}", is not supported for {0} operations. All modules must represent root modules.

Cause: All modules must represent root modules. This operation does not support embedded modules.

Action: Use DeploymentManager.enableModuleTargeting.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260028: No targeting information was provided for {0} operation.

Cause: An invalid argument was used.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260029: "{1}" is not part of application, "{2}". Only one application allowed for {0} operation.

Cause: Multiple applications were specified in the same operation. An invalid argument was used.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260030: Module, "{0}", is not part of any application.

Cause: An invalid argument was used.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260031: No action performed or required for {0} request.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: J2EE Deployment SPI

BEA-260036: Module type, "{0}", is not supported.

Cause: The operation is unsupported.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260037: Encountered unexpected descriptor for module "{0}".

Cause: An invalid application descriptor was used in the EAR file.

Action: Fix the application descriptor.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260040: No files provided in {0} request.

Cause: At least one file must be specified for update.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260041: Unable to upload "{1}" to "{0}"

Cause: Check the log for further details. Requested files need to be uploaded to a remote Administration Server.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260050: "{0}" does not implement weblogic.deploy.api.spi.WebLogicDConfigBeanRoot, or cannot be instantiated: {1}.

Cause: This is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260052: null DConfigBeanRoot.

Cause: An invalid argument was used.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260055: Unable to parse deployment plan: "{0}".

Cause: The document is invalid and could not be read or parsed during a deployment operation.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260056: MBean must be for Application or Component: "{0}".

Cause: An invalid argument was used.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260061: Unable to recognize DDBean with xpath, "{0}".

Cause: Unable to restore configuration from an invalid descriptor; an invalid argument was used.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260067: Restored configuration for module, {0}

Cause: DeploymentConfiguration.restoreDConfigBean was invoked

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: J2EE Deployment SPI

BEA-260068: Removed configuration for module, {0}

Cause: DeploymentConfiguration.removeDConfigBean was invoked.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: J2EE Deployment SPI

BEA-260070: Saved configuration for module, {0}

Cause: DeploymentConfiguration.saveDConfigBean was invoked.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: J2EE Deployment SPI

BEA-260071: Restored configuration for application, {0}

Cause: DeploymentConfiguration.restore was invoked.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: J2EE Deployment SPI

BEA-260072: Saved configuration for application, {0}

Cause: DeploymentConfiguration.save was invoked.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: J2EE Deployment SPI

BEA-260073: Unable to introspect on bean, "{0}".

Cause: This is an internal error.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260078: No DConfigBean is available for invalid module, "{0}": {1}.

Cause: Check the error message for the specific problem.

Action: No action is required.
Level: 1

Type: WARNING

Impact: J2EE Deployment SPI

BEA-260080: Unable to define the application install directory at "{0}". Directory could not be created or is a file.

Cause: The directory could not be created or is a file.

Action: Specify a valid directory.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260081: The descriptor at "{0}" could not be parsed.

Cause: The descriptor contains syntax errors and is invalid.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260082: A required descriptor, {0}, for a CMP bean is missing.

Cause: A descriptor file is missing.

Action: Place the necessary descriptor file in the archive file or its external configuration area.
Level: 1

Type: WARNING

Impact: J2EE Deployment SPI

BEA-260083: No plan document at "{0}"

Cause: The path for the plan may have been incorrectly specified. If this is the first time the application is being configured; this may not be a problem; the plan will be created.

Action: Specify the correct plan location as necessary.
Level: 1

Type: WARNING

Impact: J2EE Deployment SPI

BEA-260085: The configuration descriptor for "{0}" already exists ( {1} ), or was not modified ( {2} ), and will not be saved.

Cause: The descriptors do not need to be saved.

Action: No action is required.
Level: 1

Type: WARNING

Impact: J2EE Deployment SPI

BEA-260086: The descriptor information at {0} was saved to the configuration area.

Cause: The configuration was saved.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: J2EE Deployment SPI

BEA-260087: The descriptor at "{0}" is missing the required {1} element for custom module with URI, "{2}", and provider, "{3}".

Cause: The named element is missing from the weblogic-extensions.xml descriptor.

Action: Correct the errors in the weblogic-extensions.xml descriptor.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260088: The {1} descriptor at "{0}" is missing.

Cause: The referenced JMS/JDBC descriptor is not present in the archive.

Action: Ensure that all of the descriptors are in place.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260091: Errors were detected when reading "{0}": {1}

Cause: Check the error message to determine the probable cause.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260094: Registering config module descriptor support with base URI, {0}, and configuration URI, {1}.

Cause: The weblogic-extensions descriptor specified custom configuration descriptor support.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: J2EE Deployment SPI

BEA-260095: Unable to create archive for "{0}"

Cause: An attempt to name a file with the appropriate extension failed.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260096: Unable to determine type of application for "{0}".

Cause: The archive does not contain standard descriptors.

Action: Ensure that the correct file was passed into the deployment operation.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260097: Unable to understand DDBeanRoot provided by deployer tool: "{0}".

Cause: The model API is not providing the expected information

Action: Resolve API problems in the class that implements javax.enterprise.deploy.model.DDBeanRoot.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260098: No descriptor type is registered for modules of type, {0}

Cause: The module type is not registered with a configurable descriptor.

Action: Register non-standard descriptors using the weblogic-extension.xml descriptor.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260099: No root element in {0} descriptor, {1} at {2}.

Cause: An invalid deployment descriptor was provided for the module.

Action: Either the wrong descriptor was specified or the module type is incorrect; take the appropriate actions to fix the problem.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260100: Invalid value for Security Model, {0}; Should be one of {1}.

Cause: An unrecognized security model was requested.

Action: Use a valid security model
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260101: Parameter "{0}" may not be null.

Cause: A null parameter was passed to the method.

Action: Resolve the client programming error.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260102: Type parameter, "{0}", provided to export method is invalid

Cause: An invalid export type parameter was used.

Action: Use a valid export type.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260103: The provided bean is not part of this configuration: "{0}".

Cause: An attempt was made to export bean properties against the wrong DConfigBeanRoot object

Action: Invoke export on the correct DConfigBeanRoot.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260104: {0} is not a changable property

Cause: One of the properties is not changeable.

Action: Remove the property that is not changeable from the list.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260106: Failed to parse descriptor at "{1}" for module "{0}": {2}.

Cause: The descriptor is not valid

Action: Ensure that the application is accessible and contains valid descriptors.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260107: Failed to write descriptor for module "{0}" configuration: {1}.

Cause: Either an I/O error prevented the save operation or the descriptor is missing some required elements.

Action: Depends on the specific error. See the error message for details.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260108: Failed to restore descriptors: {0}.

Cause: An I/O or parse error prevented the restore operation.

Action: The course of action depends on the specific error. See the error message for details.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260109: Failed to write deployment plan: {0}.

Cause: Either an I/O error prevented the save operation or the plan is missing some required elements.

Action: The course of action depends on the specific error; see the error message for details.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260110: Failed to create configuration for module: {0}

Cause: The configuration artifacts for the application could not be processed. This could result from simple access errors, descriptor parsing failures, or basic application architecture problems.

Action: The course of action depends on the specific error. See the error message for details.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260111: Errors were detected while attempting to communicate with the Administration Server.

Cause: Depends on the specific error. The associated exception will contain the root exception.

Action: The course of action depends on the specific error. See the exception.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260112: Unable to determine application name from null or empty TargetModuleID list.

Cause: No TargetModuleID objects were provided.

Action: Resolve the client programming error by providing a list of TargetModuleID objects.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260113: Plan at "{0}" is a directory. A deployment plan is always an XML document.

Cause: Plan at "{0}" is a directory, not an XML document.

Action: Resolve the client programming error.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260114: Application root at "{0}" is not a directory.

Cause: An invalid root directory was specified.

Action: Resolve the client programming error.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260115: Must specify application to configure.

Cause: No application was specified for the configuration.

Action: Resolve the client programming error.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260116: Configuration is not initialized

Cause: SessionHelper.initialize() was not yet invoked.

Action: Resolve the client programming error.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260117: Unable to load factory, "{0}"

Cause: The factory is not in the classpath.

Action: Ensure that the factory is in the classpath.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260118: A null target was included in a deployment request.

Cause: The target list is invalid.

Action: Resolve the client programming error.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260119: The path provided, "{0}", does not represent a directory.

Cause: The first argument must be a directory.

Action: Resolve the client programming error.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260121: Initiating {0} operation for application, {1} [archive: {2}], to {3}.

Cause: A deployment operation is starting.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: J2EE Deployment SPI

BEA-260122: Initiating {0} operation for application, {1}, from stream to {2}.

Cause: A deployment operation is starting.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: J2EE Deployment SPI

BEA-260123: Unable to determine targets for deployment request on application, {0}

Cause: No targets were specified for the new deployment.

Action: Specify the targets to which you want to deploy the application.
Level: 1

Type: NOTIFICATION

Impact: J2EE Deployment SPI

BEA-260124: configured targets

Cause: No targets were specified.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: J2EE Deployment SPI

BEA-260125: Errors were detected when attempting to communicate with Administration Server: {0}

Cause: Depends on the specific error. The associated exception will contain the root exception.

Action: The course of action depends on the specific error. See the exception.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260126: Cannot override plan version, "{0}", with version from options, "{1}".

Cause: A plan version was specified in the deployment options, but the plan defines its own version.

Action: Avoid specifying the plan version.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260128: Changes not allowed to DTD based descriptors. The attempt to modify property "{0}" in {1} for module "{2}" will be vetoed if possible. The change will not be persisted in either case.

Cause: A property in a DTD based descriptor was modified.

Action: Upgrade the application with schema based descriptors.
Level: 1

Type: WARNING

Impact: J2EE Deployment SPI

BEA-260129: Export not allowed on DTD based descriptors. No properties for the {0} descriptor in module, "{1}", will be exported.

Cause: An attempt was made to export a DTD based descriptor.

Action: Upgrade the application with schema based descriptors.
Level: 1

Type: WARNING

Impact: J2EE Deployment SPI

BEA-260130: Shutting down Deployment Manager connection due to an internal error.

Cause: An internal error occurred.

Action: Allocate a new Deployment Manager.
Level: 1

Type: WARNING

Impact: J2EE Deployment SPI

BEA-260131: No URI was provided.

Cause: An attempt was made to create a Deployment Manager without providing an appropriate deployer URI.

Action: Provide an appropriate deployer URI.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260132: "{0}" is not a child of "{1}".

Cause: "{0}" is not a child of "{1}".

Action: Check for a preceding conflict start message in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260133: The descriptor at "{0}" could not be parsed due to error: {1}.

Cause: The named descriptor is invalid.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260134: Unable to identify application for {0} operation.

Cause: Insufficient information was provided to identify which application to deploy.

Action: Resolve the client programming error.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260137: Failures were detected while restoring the original plan file {0}. The current plan may not reflect the accurate state of the application. Either attempt to update the application again with the current plan, or make use of the backup plan "{1}".

Cause: Failures were detected while restoring the original plan file {0}. The current plan may not reflect the accurate state of the application.

Action: Either attempt to update the application again with the current plan or make use of the backup plan "{1}".
Level: 1

Type: WARNING

Impact: J2EE Deployment SPI

BEA-260138: Failures were detected while trying to create a backup plan.xml file at "{1}" {0}.

Cause: Failures were detected while trying to create a backup plan.xml file at "{1}" {0}.

Action: Failures were detected while trying to create a backup plan.xml file at "{1}" {0}.
Level: 1

Type: WARNING

Impact: J2EE Deployment SPI

BEA-260139: Unchanged plan.xml was restored due to problems updating new plan {0}.

Cause: Unchanged plan.xml was restored due to problems updating new plan {0}.

Action: Unchanged plan.xml was restored due to problems updating new plan {0}.
Level: 1

Type: NOTIFICATION

Impact: J2EE Deployment SPI

BEA-260140: Unable to remove descriptor bean {0} due to "{1}". The remover should first check to see if the bean is removable in the deployment plan prior to removing it.

Cause: Unable to remove descriptor bean {0} due to {1}.

Action: The remover should first check to see if the bean is removable in the deployment plan prior to removing it.
Level: 1

Type: NOTIFICATION

Impact: J2EE Deployment SPI

BEA-260141: An attempt to reinitialize this object by calling either inspect() or initializeConfiguration() was made without first calling close(). This SessionHelper object is stateful and must be properly closed by calling close().

Cause: An attempt to reinitialize this object by calling either inspect() or initializeConfiguration() was made without first calling close(). This SessionHelper object is stateful and must be properly closed by calling close().

Action: Call close() on the SessionHelper instance, and avoid reusing the same instance.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260142: The descriptor at "{0}" in module "{1}" is not recognized, and could not be parsed.

Cause: The descriptor was not recognized and could not be parsed.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-280008: Opening the persistent file store "{0}" for recovery: directory={1} requestedWritePolicy="{2}" fileLockingEnabled={3} driver="{4}".

Cause: Informational message.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280009: The persistent file store "{0}" ({1}) has been opened: blockSize={2} actualWritePolicy="{3}" explicitIOEnforced={4} records={5}.

Cause: Informational message.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280012: Recovery is not yet complete.

Cause: This was caused by a programming error.

Action: Check the code and try again.
Level: 1

Type: ERROR

Impact: Store

BEA-280013: The specified file store record is longer than the maximum length of {0} bytes.

Cause: This was caused by a programming error.

Action: Either change the code or increase the size of the record.
Level: 1

Type: ERROR

Impact: Store

BEA-280019: There was an error while writing to a file store file.

Cause: See the detail message for the cause.

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

Type: ERROR

Impact: Store

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

Cause: See the detail message for the cause.

Action: Ensure that the hardware and operating system are functioning properly and that all the persistent store files are available online.
Level: 1

Type: ERROR

Impact: Store

BEA-280021: There was an error while opening the file store file "{0}".

Cause: Either the specified file does not exist, the server does not have permissions to open the file, or there is a hardware or operating system problem.

Action: Ensure that the file exists and that the directory name was specified correctly.
Level: 1

Type: ERROR

Impact: Store

BEA-280024: There was an error while creating a new file named "{0}" for the file store.

Cause: See the detail message. The disk may be full, or there may be a hardware or operating system problem.

Action: Ensure that there is enough disk space and that the hardware and operating system are working properly.
Level: 1

Type: ERROR

Impact: Store

BEA-280026: The primary or cache file "{0}" is not both readable and writeable.

Cause: The file permissions are incorrect, or the server is running under the wrong user ID.

Action: Fix the file permissions or run the server under the correct user ID.
Level: 1

Type: ERROR

Impact: Store

BEA-280029: The persistent store record {0} could not be found.

Cause: This is caused by a programming error.

Action: Ensure that the correct record ID was specified.
Level: 1

Type: ERROR

Impact: Store

BEA-280031: The persistent store named "{0}" has not yet been opened.

Cause: This is a programming error.

Action: Fix the code and try again.
Level: 1

Type: ERROR

Impact: Store

BEA-280032: The persistent store suffered a fatal error and it must be reopened.

Cause: A fatal error occurred previously.

Action: Restart the server.
Level: 1

Type: ERROR

Impact: Store

BEA-280035: Unable to access the file store directory "{0}".

Cause: See the detail message.

Action: Check that the specified path name is correct, that it exists, and that the directory is readable and writeable by the server's user ID.
Level: 1

Type: ERROR

Impact: Store

BEA-280036: Missing the file store file "{0}" in the directory "{1}".

Cause: The file has been accidentially deleted or moved, or the wrong directory name was specified, or the server process does not have permissions to read and write the file.

Action: Ensure that the directory name is correct and that the server process has permissions to read and write the files. If necessary, create an empty file with the same name.
Level: 1

Type: ERROR

Impact: Store

BEA-280037: The file store has reached the maximum number of {0} files and no more files can be created.

Cause: There are too many records in the store.

Action: Delete data from the store and try again.
Level: 1

Type: ERROR

Impact: Store

BEA-280038: An error occurred while flushing the contents of a file store file.

Cause: See the detail message.

Action: See the detail message.
Level: 1

Type: ERROR

Impact: Store

BEA-280039: The persistent store handle {0} is not valid.

Cause: This is caused by a programming error.

Action: Fix the code and try again.
Level: 1

Type: ERROR

Impact: Store

BEA-280040: An invalid record was found in the file store: Code={0}.

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

Action: Change the DirectIOMode or restore from backup if the problem persists.
Level: 1

Type: ERROR

Impact: Store

BEA-280041: A record was found in the file store with an invalid version of {0}

Cause: The file store may have been used with an incompatible version of WebLogic Server.

Action: Restore from backup.
Level: 1

Type: ERROR

Impact: Store

BEA-280042: The file store primary or cache file "{0}" cannot be opened because it is actually a directory.

Cause: A directory was accidentially created in the file store's own main or cache directory, or the specified path is incorrect.

Action: Check that the file store path is correct.
Level: 1

Type: ERROR

Impact: Store

BEA-280044: The file store directory "{0}" does not exist.

Cause: The directory has not yet been created, or its filesystem is not available.

Action: Check that the directory path has been correctly specified, and create the directory if necessary.
Level: 1

Type: ERROR

Impact: Store

BEA-280045: The file store primary or cache directory "{0}" is not a directory.

Cause: The directory has not yet been created, or its filesystem is not available.

Action: Check that the directory path has been correctly specified, remove any file or directory that already exists in its place, and create the directory if necessary.
Level: 1

Type: ERROR

Impact: Store

BEA-280046: The directory "{0}" is not both readable and writeable.

Cause: The file permissions are incorrect, or the server is running under the wrong user ID.

Action: Fix the file permissions or run the server under the correct user ID.
Level: 1

Type: ERROR

Impact: Store

BEA-280051: The persistent store was not able to create a new record.

Cause: This is an internal Error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Store

BEA-280052: The persistent store was not able to read a record.

Cause: This is an internal Error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Store

BEA-280055: Invalid name for store write policy: "{0}".

Cause: This is an internal Error.

Action: Contact My Oracle Support..
Level: 1

Type: ERROR

Impact: Store

BEA-280056: A persistent store error occurred: {0}

Cause: See the description of the underlying exception.

Action: See the description of the underlying exception
Level: 1

Type: ERROR

Impact: Store

BEA-280057: The persistent store named "{0}" is already open.

Cause: This is a programming error.

Action: Fix the code and try again.
Level: 1

Type: ERROR

Impact: Store

BEA-280059: "{0}" is not a valid store connection name.

Cause: This is a programming error.

Action: Fix the code and try again.
Level: 1

Type: ERROR

Impact: Store

BEA-280060: The persistent store "{0}" encountered a fatal error, and it must be shut down: {1}

Cause: There was a serious I/O error, either with file I/O or the JDBC connection to the database.

Action: Restart the server.
Level: 1

Type: INTERNAL_ERROR

Impact: Store

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

Cause: See he detail message.

Action: See the detail message.
Level: 1

Type: ERROR

Impact: Store

BEA-280062: The persistent store "{0}" could not be shut down: {1}

Cause: See the detail message.

Action: See the detail message.
Level: 1

Type: WARNING

Impact: Store

BEA-280063: The "{0}" field value "{1}" in table reference "{2}" (format [[[catalog.]schema.]table) is too long. The database supports a maximum length of "{3}" for this field.

Cause: This is a configuration error.

Action: When configuring a table name, choose a shorter name for the indicated field. Note that JDBC stores automatically append "WLStore" to the table name.
Level: 1

Type: ERROR

Impact: Store

BEA-280064: {0} (server="{1}" store="{2}" table="{3}")

Cause: See the exception text, and linked exception (if one exists).

Action: See the exception text, and linked exception (if one exists).
Level: 1

Type: ERROR

Impact: Store

BEA-280065: {0} (server="{1}" store="{2}" table="{3}"):(Linked Cause, "{4}")

Cause: See the exception text and linked exception text.

Action: See the exception text and linked exception text.
Level: 1

Type: ERROR

Impact: Store

BEA-280066: Empty field value in table reference "{0}" (format [[[catalog.]schema.]table).

Cause: This is a configuration error.

Action: Ensure that the entire table reference is blank, or that the table field is not blank. If there is no schema, make sure there are no periods "." in the table reference. Do not start the table reference with a period ".". Note that JDBC stores automatically append "WLStore" to table references.
Level: 1

Type: ERROR

Impact: Store

BEA-280067: JDBC store "{0}" did not find a database table at "{1}", so it created one using the commands in file "{2}".

Cause: The JDBC store did not find its backing table, so it created one.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280068: JDBC store failed to initialize. It did not find its database table and failed trying to create a new empty table using the commands in file "{0}".

Cause: See the linked exception text and linked exception stack trace.

Action: See the linked exception text and linked exception stack trace.
Level: 1

Type: ERROR

Impact: Store

BEA-280069: JDBC store failed to initialize. It did not find an already existing database table and failed to create a new empty table because the JDBC driver is unknown and/or unsupported. To force table creation with an unknown and/or unsupported driver, see the JDBC store "CreateTableDDLFile" configuration attribute. Driver information: database product name = "{0}", driver name = "{1}".

Cause: See the exception text and exception stack trace.

Action: See the text exception text and exception stack trace.
Level: 1

Type: ERROR

Impact: Store

BEA-280070: JDBC store failed to initialize. It did not find an already existing database table and failed to create a new empty table because it could not locate the configured DDL file "{0}".

Cause: The configured file is located in the server file path.

Action: For supported databases, consider the option of not configuring a custom DDL file. There is usually no need to configure a custom DDL file unless custom database-specific tuning commands have been added to the file. If a DDL file must be configured (perhaps because it is for an unsupported database), ensure that the configured file is located either in the server file path or server class path.
Level: 1

Type: ERROR

Impact: Store

BEA-280071: JDBC store "{0}" opened table "{1}" and loaded {2,choice,0#0 records|1#1 record|2#{0} records}. For additional JDBC store information, use the diagnostics framework while the JDBC store is open.

Cause: A JDBC store booted.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280072: JDBC store "{0}" failed to open table "{1}".

Cause: See the linked exception.

Action: See the linked exception.
Level: 1

Type: ERROR

Impact: Store

BEA-280073: The file store "{0}" could not be opened because it contained a file with an invalid version {1}. A file of version {2} was expected.

Cause: The file store has not been properly upgraded from a previous version of WebLogic Server, or the file has been corrupted on the disk.

Action: Ensure that the file store was upgraded using the weblogic.Upgrade tool.
Level: 1

Type: ERROR

Impact: Store

BEA-280074: The persistent store "{0}" encountered an unresolvable failure while processing transaction "{1}". Shut down and restart to resolve this transaction. {2}

Cause: There was a serious I/O error, either with file I/O or the JDBC connection to the database, or an unexpected exception occurred while processing a transaction.

Action: Restart the server.
Level: 1

Type: ERROR

Impact: Store

BEA-280075: JDBC store "{0}" failed to retain ownership of database table "{1}", either due to database access problems or due to concurrent accessors of the table. See the linked exception for more information.

Cause: Some other WebLogic server process or JDBC store has taken over ownership of the database table, or some database access error prevented this JDBC store from renewing ownership of the database table.

Action: The error message has information to identify potential owners in conflict.
Level: 1

Type: ERROR

Impact: Store

BEA-280076: Database table "{1}" for store "{0}" is currently owned by "{2}". Trying to wait for ownership.

Cause: Some other WebLogic Server process or JDBC store has ownership of the database table.

Action: The warning message has information to identify the current owner of the database table. If the current owner does not yield ownership within some time, this server will not be able to open the JDBC store and will log an error.
Level: 1

Type: WARNING

Impact: Store

BEA-280077: JDBC store "{0}" in this server is not the owner of database table "{1}". Unexpected current owner is "{2}", expected current owner is "{3}".

Cause: Some other WebLogic Server process or JDBC store has ownership of the database table.

Action: The error message has information to identify and resolve the owners in conflict.
Level: 1

Type: ERROR

Impact: Store

BEA-280078: The handle that was passed was created from a different store connection.

Cause: This is a programming error.

Action: Ensure that the correct connection was used.
Level: 1

Type: ERROR

Impact: Store

BEA-280079: An instance of the mSA PersistentStore

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280080: Number of create requests issued by this store.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280081: Number of read requests issued by this store.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280082: Number of update requests issued by this store

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280083: Number of delete requests issued by this store

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280084: Number of objects contained in the store

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280085: Number of times the store flushed its data to durable storage

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280086: An instance of an mSA PersistentStoreConnection

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280087: Number of create requests issued by this store connection

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280088: Number of read requests issued by this store connection

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280089: Number of update requests issued by this store connection

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280090: Number of delete requests issued by this store connection

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280091: Number of objects contained in the store connection

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280092: Specified value "{1}" of the property "{0}" is not a valid Integer system property. Using default value "{2}" instead.

Cause:

Action: Check the Javadoc for the valid formats of Integer system properties: http://java.sun.com/j2se/1.5.0/docs/api/java/lang/Integer.html#decode(java.lang.String).
Level: 1

Type: WARNING

Impact: Store

BEA-280093: Block size "{1}" specified by the property {0} is outside the valid range from {2} to {3}. Using default value "{2}" instead.

Cause:

Action: Refer to the JMS chapter of the Performance and Tuning for Oracle WebLogic Server guide for details of this setting.
Level: 1

Type: WARNING

Impact: Store

BEA-280094: The size "{1}" specified by the property {0} is not power of 2. Rounding down to "{2}" instead.

Cause:

Action: Refer to the JMS chapter of the Performance and Tuning for Oracle WebLogic Server guide for details of this setting.
Level: 1

Type: WARNING

Impact: Store

BEA-280095: Opening existing file store "{1}". The block size value specified by the property {0} is ignored because the block size of preexisting files cannot change.

Cause:

Action: Refer to the JMS chapter of the Performance and Tuning for Oracle WebLogic Server guide for details of this setting.
Level: 1

Type: WARNING

Impact: Store

BEA-280096: Opening existing file store "{2}". The direct IO mode "{1}" specified by the property "{0}" is invalid and will be ignored. Using the default value "{3}"

Cause:

Action: Use a valid direct I/O mode. The valid values are: "read-buffered", "single-handle-unbuffered", and "single-handle-buffered".
Level: 1

Type: WARNING

Impact: Store

BEA-280097: A file store failed to open file "{0}" in the Direct-Write read-buffered/write-unbuffered mode and is instead opening the file in a purely unbuffered mode. When there are high request loads, this may reduce file store performance. However, the store is still operating in a transactionally safe synchronous mode.

Cause:

Action: To fix this problem, configure a different synchronous write policy, or if using the Direct-Write policy, force the store into read-write-buffered mode using the AvoidDirectIO command line property documented in the store chapter of the Performance and Tuning Guide.
Level: 1

Type: WARNING

Impact: Store

BEA-280101: The persistent file store "{0}" is forced to use buffered I/O because the Operating System or hardware environment does not support unbuffered I/O. The store is still operating in a transactionally safe synchronous mode. See store open log messages for the final write policy.

Cause: See the message body.

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

Type: NOTIFICATION

Impact: Store

BEA-280102: The perisistent file store "{0}" must reinitialize its cache: recovery may take longer than usual. The signature in the cache file "{1}" for the persistent store file "{0}" could not be verified, or the cache file is missing. Ignore this Warning if this is the first time the store has ever booted. Possible causes include: first boot of store (potentially after using a write policy different from Direct-Write-With-Cache), store migration, unclean shutdown, off-line store compression, and manual removal of cache files.

Cause: The cache file is missing, or the signature stored in the cache file does not match the signature of the primary file.

Action: Make sure that the configuration is correct, do not delete cache files, and ensure a clean shutdown.
Level: 1

Type: WARNING

Impact: Store

BEA-280103: The persistent file store "{0}" will cache in {1}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280104: The persistent file store "{0}" will use buffered writes instead of direct IO because the configured block size "{2}" is not a multiple of the environment's direct IO alignment "{1}". When there are high request loads, this may reduce file store performance. The store is still operating in a transactionally safe synchronous mode.

Cause: Direct I/O requires the block size to be a multiple of directIO granularity.

Action: Reconfigure the store with a block size that is a multiple of the direct I/O alignment for your environment. If the store is not empty and contains useful data, use the store admin compact utility to change block size, otherwise make sure that all store files are removed before starting WebLogic Server again.
Level: 1

Type: WARNING

Impact: Store

BEA-280105: The persistent file store "{0}" cannot open file {1}.

Cause: An IOException occurred.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Store

BEA-280106: The persistent file store "{0}" cannot memory-map the locked file "{1}" and has to downgrade to explicit buffered IO. For example, in some NFS environments memory-mapping and locking are not compatible. Consider configuring a local cache directory.

Cause: See the message body.

Action: Consult your storage vendor and operating system documentation.
Level: 1

Type: ERROR

Impact: Store

BEA-280107: The persistent store record {0}, connection "{1}", in the store named "{2}" does not exist because it has been deleted.

Cause: This was caused by a programming error.

Action: Ensure that the correct record ID was specified.
Level: 1

Type: ERROR

Impact: Store

BEA-280108: The persistent store record {0}, connection "{1}" already exists in the store named "{2}".

Cause: This was caused by a programming error.

Action: Ensure that the correct record ID was specified.
Level: 1

Type: ERROR

Impact: Store

BEA-280109: Unable to load the native wlfileio library for the persistent file store "{0}". The store will use buffered I/O. The store is still operating in a transactionally safe synchronous mode. See store open log messages for the requested and final write policies.

Cause: See message body.

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

Type: WARNING

Impact: Store

BEA-280110: The "{1}" attribute of Persistent Store "{0}" has been changed from "{2}" to "{3}".

Cause: This is due to a configuration change.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280111: The "{1}" attribute of Persistent Store "{0}" has been changed from "{2}" to "{3}".

Cause: This is due to a configuration change.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280112: [StoreBootOnError] "{0}" Ignoring AssertionError on bootHandle: record type: {1}, handle:{2}, row: {3}

Cause: There is some corruption of the JDBC store.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: Store

BEA-280113: The JDBC store "{0}" is initially pointing to RAC instance "{1}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280114: The JDBC store "{0}" is configured with worker count as "{1}" but only started "{2}" workers as it is not able to acquire enough JDBC connections for the configured worker count.

Cause: The JDBC store was not able to acquire enough JDBC connections for the configured worker count.

Action: Modify the data source configuration.
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-281002: The SAF service has been started.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SAFService

BEA-281003: The SAF service has been initialized.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SAFService

BEA-281004: The SAF service has been suspended.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SAFService

BEA-281005: The SAF service has been shut down.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SAFService

BEA-281006: FailedMessage for store-and-forward: MessageId={0} > </FailedMessage.

Cause: A message expired before it was successfully forwarded by an SAF agent, and there is no error handling policy configured for the endpoint. The message ID was logged.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SAFService

BEA-281007: SAF Agent "{0}" has been successfully prepared.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SAFService

BEA-281008: SAF Agent "{0}" has been successfully activated.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SAFService

BEA-281009: SAF Agent "{0}" has been deactivated.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SAFService

BEA-281010: SAF Agent "{0}" has been unprepared.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SAFService

BEA-281011: SAF Agent "{0}" failed to be prepared because of exception "{1}".

Cause: There was either an error in the configuration or an internal error.

Action: Check the agent's configuration and contact My Oracle Support.
Level: 1

Type: ERROR

Impact: SAFService

BEA-281012: SAF Agent "{0}" failed to be started because of exception "{1}".

Cause: There was either an error in the configuration or an internal error.

Action: Check the agent's configuration and contact My Oracle Support.
Level: 1

Type: ERROR

Impact: SAFService

BEA-281016: SAFAgent "{0}" byte threshold for the agent has been exceeded.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: INTERNAL_ERROR

Impact: SAFService

BEA-281017: SAFAgent "{0}" byte threshold for agent has cleared.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: INTERNAL_ERROR

Impact: SAFService

BEA-281018: SAFAgent "{0}" message threshold for the agent has been exceeded.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: INTERNAL_ERROR

Impact: SAFService

BEA-281019: SAFAgent "{0}" message threshold for the agent has cleared.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: INTERNAL_ERROR

Impact: SAFService

BEA-281020: SAF service has successfully connected to the remote endpoint "{0}".

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SAFService

BEA-281021: SAF service failed to connect to the remote endpoint "{0}", because of {1}.

Cause: This is either due to a configuration error or a network failure, or the remote endpoint is temporarily unavailable.

Action: Check the configuration, the network connection, or the remote endpoint.
Level: 1

Type: NOTIFICATION

Impact: SAFService

BEA-281022: SAF Agent "{0}" failed to resume because of exception "{1}".

Cause: There was either an error in the configuration or an internal error.

Action: Check the agent's configuration and contact My Oracle Support.
Level: 1

Type: ERROR

Impact: SAFService

BEA-281025: SAFAgent "{0}" has been paused for incoming messages.

Cause: An Incoming Message Pause request was issued for the specified SAFAgent.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SAFService

BEA-281026: SAFAgent "{0}" has been resumed for new incoming messages.

Cause: An Incoming Message Resume request was issued for the specified SAFAgent.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SAFService

BEA-281027: SAFAgent "{0}" has been paused for forwarding

Cause: A Forwarding Pause request was issued for the specified SAFAgent.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SAFService

BEA-281028: SAFAgent "{0}" has been resumed for forwarding.

Cause: A Forwarding Resume request was issued for the specified SAFAgent.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SAFService

BEA-281029: RemoteEndpoint "{0}" has been paused for new incoming messages.

Cause: An Incoming Pause Request was issued for the specified remote endpoint.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SAFService

BEA-281030: RemoteEndpoint "{0}" has been resumed for new incoming messages.

Cause: An Incoming Resume Request was issued for the specified remote endpoint.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SAFService

BEA-281031: RemoteEndpoint "{0}" has been paused for forwarding.

Cause: A Forwarding Pause Request was issued for the specified remote endpoint.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SAFService

BEA-281032: RemoteEndpoint "{0}" has been resumed for forwarding.

Cause: A Forwarding Resume request was issued for the specified remote endpoint.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SAFService

BEA-282000: Unsupported class version {0}. Expected a value between {1} and {2} inclusive.

Cause: While attempting to interoperate between different releases or service packs, an error occurred while attempting to serialize or deserialize an object. The version number of the object was not in the expected range. If {0} is larger than {2}, then it is possible an attempt was made to access a newer version than the current version. Otherwise, a possible attempt has been made to interoperate with an unsupported older version.

Action: Ensure that the versions of Oracle products that are interoperating are supported. If the versions need to be supported, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Messaging

BEA-282001: The messaging kernel {0} is beginning recovery of its persistent state.

Cause: This is normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Messaging

BEA-282002: The messaging kernel {0} has recovered {1} persistent messages.

Cause: This is normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Messaging

BEA-282003: The messaging kernel {0} will use up to {1} bytes of memory before paging begins.

Cause: This is normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Messaging

BEA-282004: Message redirection has failed in a non-recoverable way for the messaging kernel {0}. Restart the server in order to restart message redirection.

Cause: See the previous error messages, which should explain the cause.

Action: Restart the WebLogic Server.
Level: 1

Type: ERROR

Impact: Messaging

BEA-282005: An error occurred while redirecting a message for the messaging kernel {0}: {1}.

Cause: See the attached detail message.

Action: No action is required.
Level: 1

Type: WARNING

Impact: Messaging

BEA-282006: An error occurred while deleting an expired message for the messaging kernel {0}: {1}.

Cause: See the attached detail message.

Action: No action is required.
Level: 1

Type: WARNING

Impact: Messaging

BEA-282007: An error occurred in the transaction prepare phase of a message send operation for the messaging kernel {0}.

Cause: See the attached stack trace.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Messaging

BEA-282008: A message send transaction for the messaging kernel {0} could not be committed because the kernel has been shut down.

Cause: A server was shut down or a destination was removed while a transaction was in progress.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Messaging

BEA-282009: A message receive transaction for the messaging kernel {0} could not be committed because the kernel has been shut down.

Cause: A server was shut down or a destination was removed while a transaction was in progress.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Messaging

BEA-282010: A sequence number update transaction for the messaging kernel {0} could not be committed because the kernel has been shut down.

Cause: A server was shut down or a destination was removed while a transaction was in progress.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Messaging

BEA-282011: There was an error making a message visible after a delivery delay: {0}.

Cause: Most likely, a transient I/O error occurred.

Action: Consider restarting the server if the error persists. The message will not be lost.
Level: 1

Type: WARNING

Impact: Messaging

BEA-282012: There was a failure while performing paging I/O.

Cause: Either a transient I/O error occurred, or the server did not have enough memory to complete the paging I/O request.

Action: Consider restarting the server if the error persists.
Level: 1

Type: WARNING

Impact: Messaging

BEA-282013: Skipping unexpected null message encountered on store boot, {0}.

Cause: Message data corruption has occurred. The corrupted message will be skipped to allow data recovery on other non-corrupted messages.

Action: Report this issue to My Oracle Support.
Level: 1

Type: WARNING

Impact: Messaging

BEA-282014: [StoreBootOnError] "{0}" Ignoring 2PC record for sequence={1}, queue={2}, type={3}, id={4}, xid={5}; message reference element cannot be found.

Cause: Potential message data corruption has occurred. A 2PC record was found in the store without an associated message reference element. The 2PC record will be ignored.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: Messaging

BEA-283002: Path Service has been started on server {0} with jndiName {1} with store {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: PathService

BEA-290001: Error occurred in the deployment service servlet. It received an unacceptable request of type "{0}" with content type "{1}".

Cause: An invalid request was made to the deployment service servlet.

Action: This is an internal error. No action is required. If the problem persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: DeploymentService

BEA-290003: Deployment service servlet encountered an exception while handling request of type "{0}". Exception is: "{1}".

Cause: Error occurred while handling the deployment servlet request.

Action: This is an internal error. Refer to the exception message and determine if the exception can be corrected. If the problem persists, contact My Oracle Support.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290006: Deployment service servlet received a request of type "{0}" with no application name.

Cause: An invalid deployment service servlet request was made.

Action: This is an internal error. No action is required. If the problem persists, contact My Oracle Support.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290007: Deployment service servlet unable to find upload directory while handling request of type "{0}" for application "{1}".

Cause: The servlet was unable to find the upload directory.

Action: This is an internal error. No action is required. If the problem persists, contact My Oracle Support.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290008: Deployment service servlet encountered an error while extracting uploaded file to directory "{0}". Exception is: "{1}".

Cause: An exception occurred while extracting the uploaded file.

Action: This is an internal error. Refer to the exception message and determine if the exception can be corrected. If the problem persists, contact My Oracle Support.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290009: Deployment service servlet failed to get initialized due to unavailable security service.

Cause: The WebLogic Server security service is not present in the installation files.

Action: This is an internal error. No action is required. If the problem persists, contact My Oracle Support.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290010: Deployment service servlet failed to get initialized due to privileged action violation. Exception is: "{0}".

Cause: An exception occurred while initializing the deployment service servlet.

Action: This is an internal error. Refer to the exception message and determine if the exception can be corrected. If the problem persists, contact My Oracle Support.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290011: Unauthorized request of type "{0}" for user "{1}"

Cause: The user is unauthorized for downloading files.

Action: Check the user and try again with an authorized user.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290012: Deployment service servlet received jspRefresh request with no upload file name.

Cause: The request parameter upload file name was null.

Action: This is an internal error. No action is required. If the problem persists, contact My Oracle Support.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290013: No user name or password provided for the request.

Cause: The user name or password in the request were null.

Action: This is an internal error. No action is required. If the problem persists, contact My Oracle Support.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290014: Invalid user name or password.

Cause: The request contained an invalid user name or password.

Action: Try again with a valid user name and password.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290015: Domain wide secret mismatch

Cause: Thee was an invalid signature between the Administration Server and Managed Servers.

Action: This is an internal error. Verify that the Administration Server and Managed Servers have the same SerializedSystemIni.dat file.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290016: Access not allowed for server "{0}" on boot.

Cause: The user does not have boot permission for the specified server.

Action: This is an internal error. No action is required. If the problem persists, contact My Oracle Support.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290020: Exceptions encountered while invoking application lifecycle listeners

Cause: A registered lifecycle listener detected an error and generated an exception.

Action: Refer to the exception message from the lifecycle listener and determine if the error can be corrected.
Level: 1

Type: ERROR

Impact: DeploymentService

BEA-290021: {0} does not exist.

Cause: The file does not exist on the Administration Server.

Action: This is an internal error. No action is required.
Level: 1

Type: ERROR

Impact: DeploymentService

BEA-290022: This request needs to be initiated through a start control.

Cause: This is an internal protocol error.

Action: This is an internal error. No action is required. If the problem persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: DeploymentService

BEA-290024: Deployment type {0} has already been registered with the DeploymentService.

Cause: More than one deployment handler was registered for this deployment type.

Action: This is an internal error. No action is required. If the problem persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: DeploymentService

BEA-290025: Cannot call "start()" when DeploymentRequest has already been started.

Cause: The start method was called more than once.

Action: This is an internal error. No action is required.
Level: 1

Type: ERROR

Impact: DeploymentService

BEA-290026: Request "{0}" is in "{1}" state - request has already been cancelled.

Cause: More than one cancel request was received.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: DeploymentService

BEA-290027: Request "{0}" is in "{1}" state - it is too late to attempt cancelling it.

Cause: A cancel request was received while the request was being committed.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: DeploymentService

BEA-290028: Deployment "{0}" has been cancelled.

Cause: The request was already cancelled.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: DeploymentService

BEA-290029: Deployment "{0}" timed out on Administration Server.

Cause: The request has timed out.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: DeploymentService

BEA-290030: No data handler registered for type "{0}".

Cause: A handler was not registered for the specified type.

Action: This is an internal error. No action is required.
Level: 1

Type: ERROR

Impact: DeploymentService

BEA-290031: No tasks associated with this deployment request that can be cancelled.

Cause: Tasks have already completed.

Action: No action is required.
Level: 1

Type: ERROR

Impact: DeploymentService

BEA-290032: Data Transfer Handler exists for handler type: "{0}".

Cause: The handler type is already registered

Action: This is an internal error. No action is required.
Level: 1

Type: ERROR

Impact: DeploymentService

BEA-290036: Deployment for request id "{0}" is deferred since target "{1}" is disconnected.

Cause: Target server "{1}" is disconnected.

Action: No action is required. When the server reconnects, the deployment will be performed.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290039: Unrecognized callback

Cause: The callback was not a supported type.

Action: This is an internal error. No action is required. If the problem persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: DeploymentService

BEA-290040: The cancel call cannot be completed at this point because the deployment request "{0}" has already been partially committed.

Cause: A cancel was requested on a committed deployment task.

Action: Wait until the deployment task has completed and then perform the necessary actions to restore the application to the desired state.
Level: 1

Type: ERROR

Impact: DeploymentService

BEA-290041: Commit failed message received for id: "{0}" that has no request. It may be completed or cancelled. Sending commit succeeded message anyway.

Cause: No corresponding request was found for the commit failure message.

Action: Check for a preceding conflict start message in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290042: Received a commit message call without a corresponding request. It may have been completed or cancelled. Sending commit failed message.

Cause: No corresponding request was found for the commit message.

Action: Check for a preceding conflict start message in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290043: Cancel failure encountered when attempting to cancel "{0}" due to optimistic concurrency violation.

Cause: A failure occurred during the cancel of the request.

Action: Wait until the deployment task has completed and then perform the necessary actions to restore the application to the desired state.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290044: {0} delivery

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: DeploymentService

BEA-290045: prepare

Cause: Not applicable.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: DeploymentService

BEA-290046: commit

Cause: Not applicable.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: DeploymentService

BEA-290047: cancel

Cause: Not applicable.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: DeploymentService

BEA-290048: Request with id "{0}" timed out.

Cause: The request timed out.

Action: Try increasing the deployment timeout value. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: DeploymentService

BEA-290049: Deploy failed for id "{0}" since no targets are reachable.

Cause: No targets were reachable.

Action: Ensure targeted servers are alive and available from the Administration Server.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290050: Failed to deliver commit message to the following targets "{0}".

Cause: An exception occurred while committing the deployment request.

Action: Ensure that targeted servers are alive and available from the Administration Server. Check for a preceding conflict start message in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: DeploymentService

BEA-290051: The commit message for the deployment "{0}" could not be completed because the deployment timed out.

Cause: The deployment timed out.

Action: Try increasing the deployment timeout value. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: DeploymentService

BEA-290052: {0} timeout

Cause: Not applicable.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: DeploymentService

BEA-290053: Request with id "{0}" timed out on the Administration Server.

Cause: The request timed out on the Administration Server.

Action: Try increasing the deployment timeout value. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: DeploymentService

BEA-290054: Deployment request "{0}" was explicitely cancelled.

Cause: Not applicable.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: DeploymentService

BEA-290055: Deployment request "{0}" timed out on the Administration Server during "{1}".

Cause: The deployment request timed out.

Action: Try increasing the deployment timeout value. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290056: indeterminate

Cause: Not applicable

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: DeploymentService

BEA-290057: Invalid DeploymentRequest: the object returned by the DeploymentService has been modified in an incompatible way.

Cause: The deployment request is not of the expected type.

Action: Check for a preceding conflict start message in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: NOTIFICATION

Impact: DeploymentService

BEA-290058: There is no request corresponding to request ID "{0}" currently being processed. The request will be cancelled if it is received in the future.

Cause: The specified request ID is not active.

Action: Check that your task ID is the task that you would like to cancel.
Level: 1

Type: ERROR

Impact: DeploymentService

BEA-290059: Operation "{0}" is not one of the supported types when creating a Change Descriptor.

Cause: An invalid change descriptor type was specified.

Action: This is an internal error. If the problem persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: DeploymentService

BEA-290060: Duplicate registration for "{0}".

Cause: Two different deployment instances were registered for the same type.

Action: This is an internal error. If the problem persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: DeploymentService

BEA-290061: UnrecognizedTypes: "{0}", "{1}"

Cause: A deployment type is invalid.

Action: This is an internal error. If the problem persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: DeploymentService

BEA-290062: The server configuration is out of date with the domain configuration and an attempt to synchronize with the Administration Server failed. This server needs to be restarted to enable it to synchronize with the domain configuration.

Cause: An attempt to synchronize with the Administration Server failed.

Action: Restart the server and if that does not resolve the problem, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: DeploymentService

BEA-290063: Commit for request "{0}" will not proceed further since its requires restart flag is set.

Cause: The changes in the deployment request require a restart.

Action: Restart either the server or the system resource that is part of the request.
Level: 1

Type: NOTIFICATION

Impact: DeploymentService

BEA-290064: Deployment service servlet encountered an exception while handling the deployment service message for request id "{0}" from server "{1}". Exception is: "{2}".

Cause: Error occurred while handling the deployment service message request.

Action: This is an internal error. Refer to the underlying error message and determine if the error can be corrected. Verify that there are no network connection issues between the administration and managed servers.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290065: Deployment service servlet encountered an Exception while handling the deployment datatransfer message for request id "{0}" from server "{1}". Exception is: "{2}".

Cause: Error occurred while handling the deployment datatransfer request.

Action: This is an internal error. Refer to the underlying error message and determine if the error can be corrected. Verify that there are no network connection issues between the administration and managed servers.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290066: Error occurred while downloading files from Administration Server for deployment request "{0}". Underlying error is: "{1}"

Cause: The connection used for the file download received an error.

Action: Refer to the underlying error message and determine if the error can be corrected. Verify that there are no network connection issues between the administration and managed servers.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290067: Deployment request ''{0}'' was cancelled because servers: ''{1}'' were unreachable and the domain has cluster-constraints-enabled is set to true. To deploy to this cluster, either start the unreachable servers or remove the unreachable servers from the cluster, then reattempt the deployment. If this behaviour is not intended, set cluster-constraints-enabled on the domain to false and restart the Administration Server. This allows you to deploy the application only to those servers that can be reached.

Cause: Not all the servers in the cluster are running and cluster-constraints-enabled is set to true.

Action: Start all the servers in the cluster and try deployment again, or if this behaviour is not intended, set cluster-constraints-enabled on the domain to false and restart the Administration Server.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290068: A deployment service request has been received by this Managed Server that was intended for the Administration Server. The source of the request is "{0}".

Cause: The source Managed Server was started with a URL for the Administration Server that incorrectly identified this server.

Action: Start the source Managed Server with the correct URL for the Administration Server.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290069: Commit failed message received for id: "{0}", but exception details cannot be transported. Please look at target server log file for more details.

Cause: The send of the commit message failed.

Action: Check the exception details in the server log and determine if the failure can be corrected.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290070: Deployment service servlet encountered an exception while parsing the multipart/form-data request:"{0}". Exception is: "{1}".

Cause: The request is not an RFC 1867-compliant multipart/form-data request.

Action: This is an internal error. No action is required.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290071: Deployment service servlet failed when parsing the request or uploading the file.

Cause: The request is not an RFC 1867-compliant multipart/form-data stream.

Action: The request should comply with RFC 1867. Verify that the Administration Server and Managed Servers are running versions that interoperate.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-300001: Could not execute command {0} for the Managed Server through the NodeManager, because the server name is not set.

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

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

Type: ERROR

Impact: NodeManager

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

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

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

Type: ERROR

Impact: NodeManager

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

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

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

Type: ERROR

Impact: NodeManager

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

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

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

Type: ERROR

Impact: NodeManager

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

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

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

Type: ERROR

Impact: NodeManager

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

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

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

Type: ERROR

Impact: NodeManager

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

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

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

Type: ERROR

Impact: NodeManager

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

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

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

Type: ERROR

Impact: NodeManager

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

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

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

Type: ERROR

Impact: NodeManager

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

Cause: This is an internal error.

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

Type: ERROR

Impact: NodeManager

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

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

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

Type: ERROR

Impact: NodeManager

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

Cause: The NodeManager address has not been set.

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

Type: ERROR

Impact: NodeManager

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

Cause: The NodeManager port has not been set.

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

Type: ERROR

Impact: NodeManager

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

Cause: The remote start configuration is missing.

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

Type: ERROR

Impact: NodeManager

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

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

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

Type: ERROR

Impact: NodeManager

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

Cause: The server listen address has not been set.

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

Type: ERROR

Impact: NodeManager

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

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

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

Type: ERROR

Impact: NodeManager

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

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

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

Type: ERROR

Impact: NodeManager

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

Cause: The specified log file could not be created.

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

Type: ERROR

Impact: NodeManager

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

Cause: This is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: NodeManager

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

Cause: This is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: NodeManager

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

Cause: This is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: NodeManager

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

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

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

Type: ERROR

Impact: NodeManager

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

Cause: This is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: NodeManager

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

Cause: This is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: NodeManager

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

Cause: The specified log file could not be created.

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

Type: ERROR

Impact: NodeManager

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

Cause: The NodeManager command execution failed.

Action: No action is required.
Level: 1

Type: ERROR

Impact: NodeManager

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

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

Action: No action is required.
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300035: Warning : {0}

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

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

Type: WARNING

Impact: NodeManager

BEA-300036: Error :{0}

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

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

Type: ERROR

Impact: NodeManager

BEA-300037: The NodeManager at host {0} and port {1} seems to be down. Start the NodeManager and rerun the command.

Cause: The NodeManager is not running.

Action: Start the NodeManager and rerun the command.
Level: 1

Type: WARNING

Impact: NodeManager

BEA-300038: The NodeManager is unable to monitor this server. Could not create an SSL connection to the NodeManager. Reason : {0}

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

Action: Check the message for details.
Level: 1

Type: WARNING

Impact: NodeManager

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

Cause: See the message for details.

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

Type: ERROR

Impact: NodeManager

BEA-300040: An I/O error occurred while writing a NodeManager status change message.

Cause: Possible causes are that the standard output stream has been closed or the NodeManager stopped monitoring.

Action: If this server requires monitoring, restart the server.
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300041: Failed to register for startup mode change notification. Reason : {0}

Cause: Check the message for details.

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

Type: ERROR

Impact: NodeManager

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

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

Action: Shut down the server gracefully.
Level: 1

Type: WARNING

Impact: NodeManager

BEA-300043: NodeManager native library not found - server process ID not saved.

Cause: The NodeManager native library is not in the library search path or is unavailable on this platform.

Action: Ensure that the NodeManager native library is available and in the library search path.
Level: 1

Type: WARNING

Impact: NodeManager

BEA-300044: An I/O error occurred while writing the server PID file: "{0}".

Cause: The server PID file might be write protected.

Action: Ensure that the server PID file is not write protected. Also, check to see if the parent directory exists (should have been created by the NodeManager server before starting the server).
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300045: An I/O error occurred while executing command "{0}" on the NodeManager.

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

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

Type: WARNING

Impact: NodeManager

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

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

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

Type: WARNING

Impact: NodeManager

BEA-300048: Unable to start the server {0} : {1}

Cause: The most likely cause is a configuration error in the Shell/SSH/RSH NodeManager configuration.

Action: Ensure that you can access the remote NodeManager. This may require setting up SSH permissions for the SSH-based NodeManager. Also, ensure that the default PATH settings for the remote NodeManager are correct. See the NodeManager documentation for more information.
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300049: An I/O error occurred while writing the server URL file: "{0}".

Cause: The server URL file might be write protected.

Action: Ensure that the server URL file is not write protected. Also, check to see if the parent directory exists (should have been created by the NodeManager server before starting the server).
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300051: An I/O error occurred while updating the startup properties for "{0}". This probably occured because the NodeManager is unreachable. This could mean that the servers boot.properties or startup.properties file is out of date, and the next time NodeManager attempts to automatically restart the server on a failure, it will use out of date properties. To resolve this issue, either ensure that the NodeManager is able to receive the updates and reset the properties, or restart the server.

Cause: An I/O error occurred while updating the startup properties for "{0}". This probably occured because the NodeManager is unreachable.

Action: Either ensure that the NodeManager is able to receive the updates and reset the properties, or restart the server.
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300052: The specified script path, "{0}", contains improper characters. The script path must be a valid path that exists within the NodeManager script execution directory.

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

Action: Ensure that the script path is a be a valid path that exists within the NodeManager script execution directory.
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300053: A migratable server was not found to contain any specified IP address in the ServerMBean or custom network channels for migration. No IPs will be passed to NodeManager and no IPs will be migrated. The server may not start without an available address, or may not be accessible throughout migration without a consistent IP. Configure an appropriate floating listen address for the server.

Cause: A migratable server was not found to contain any specified IP address in the ServerMBean or custom network channels for migration. No IPs will be passed to NodeManager and no IPs will be migrated. The server may not start without an available address, or may not be accessible throughout migration without a consistent IP.

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

Type: ERROR

Impact: NodeManager

BEA-300054: Could not find appropriate IP for ListenAddress "{0}" specified for a migratable server. Reason: "{1}". The NodeManager may not be able to bind the address specified and the server may not start without the available address. Configure an appropriate floating listen address for the server.

Cause: No appropriate IP was found for a migratable server's listen address. The NodeManager may not be able to bind the address specified and the server may not start without the available address. Configure an appropriate floating listen address for the server.

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

Type: ERROR

Impact: NodeManager

BEA-309999: {0}

Cause: Debugging - please do not change.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: NodeManager

BEA-310001: Subsystem {0} has failed. Setting server state to FAILED.

Cause: One of the critical subsystems of the server has failed.

Action: Check the server log to determine the cause of the subsystem failure.
Level: 1

Type: ERROR

Impact: Health

BEA-310002: {0}% of the total memory in the server is free.

Cause: The percentage of free memory in the server has changed.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Health

BEA-310003: Free memory in the server is {0} bytes. There is danger of receiving an OutOfMemoryError.

Cause: Free memory in the server is very low.

Action: Analyze heap memory usage for possible memory leak. Contact Oracle Support if the leak is in WebLogic server. If no memory leak is found, consider restarting server with a larger maximum heap size.
Level: 1

Type: WARNING

Impact: Health

BEA-310006: Critical subsystem {0} has failed. Setting server state to FAILED. Reason: {1}

Cause: One of the critical subsystems of the server has failed.

Action: Check the server log to determine the cause of the subsystem failure.
Level: 1

Type: INTERNAL_ERROR

Impact: Health

BEA-310007: Subsystem {0} has failed because of: {1} However, notification did not occur because {0} was not registered with the HealthMonitorService.

Cause: One of the subsystems of the server has failed.

Action: Check the server log to determine the cause of the subsystem failure. MigratableTargets may need to be manually moved, since the automatic migration subsystem requires HealthMonitor notification to work properly.
Level: 1

Type: WARNING

Impact: Health

BEA-310008: Non-critical subsystem {0} has failed. Reason: {1}

Cause: One of the non-critical subsystems of the server has failed.

Action: Check the server log to determine the cause of the subsystem failure.
Level: 1

Type: INTERNAL_ERROR

Impact: Health

BEA-320000: The Diagnostics subsystem is initializing on Server {0}.

Cause: This message is for informational purposes only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320001: The ServerDebug service initialized successfully.

Cause: This message is for informational purposes only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320002: The Diagnostics subsystem is stopping on Server {0}.

Cause: This message is for informational purposes only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320004: The following unexpected exception was thrown: {0}

Cause: An exception was thrown unexpectedly.

Action: Take appropriate action based on the unexpected exception message.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320005: Diagnostic monitor of unknown type {1} used in instrumentation scope {0}.

Cause: The Diagnostic Monitor library is probably out of date.

Action: Update the Diagnostic Monitor library.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320008: Error occurred while collecting diagnostic metrics:

Cause: An error occurred while constructing a Harvester instance.

Action: Ensure that all harvester configuration parameters are set appropriately.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320009: The elapsed time of the last snapshot of diagnostic metrics exceeded the configured sample period by the following number of milliseconds: {0}.

Cause: Harvested MBeans and/or DataSources are taking too long to return sampled attribute values.

Action: Increase the sample period window.
Level: 1

Type: WARNING

Impact: Diagnostics

BEA-320010: An error occurred while generating a diagnostic image: {0}

Cause: Permissions were abruptly changed on the zip/directory. The file system does not have sufficient disk space to continue writing the image.

Action: Allocate sufficient disk space and provide the proper permissions to create the image zip file.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320011: The following diagnostic image destination directory could not be created: {0}

Cause: You have not given write permissions to the absolute path for the default directory, or you have not allocated sufficient disk space for the directory to be created.

Action: You must give write permissions to the absolute path for the default directory if no configured destination directory is specified. You must also allocate sufficient disk space for the default directory to be created if no destination directory is specified.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320012: The following destination directory for diagnostic images could not be read/written: {0}.

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

Action: Create the destination directory with the appropriate read/write permissions.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320013: Diagnostic image capture was attempted during a lockout period.

Cause: The ImageManager has locked image captures for a specified number of minutes.

Action: The lockout period must expire before a new image capture request is accepted.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320014: Lockout of {0} above allowed maximum lockout minutes for image captures.

Cause: The specified a number of minutes exceeds the maximum allowed lockout minutes.

Action: Specify a lockout period between the minimum and maximum.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320015: Lockout of {0} below allowed minimum lockout minutes for image captures.

Cause: The specified a number of minutes falls below the minimum allowed lockout minutes.

Action: Specify a lockout period between the minimum and maximum.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320016: Creating diagnostic image in {0} with a lockout minute period of {1}.

Cause: A FirstFailure has occurred, a diagnostic image notification handler was configured, or a capture image method was explicitly invoked on ImageManager.

Action: No action is required. The diagnostic image capture request will be scheduled and executed.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320018: Instrumentation engine configuration {0} could not be parsed due to: {1}

Cause: The instrumentation engine configuration is possibly malformed.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320019: Code generator class {1} for standard monitor {0} could not be found.

Cause: The standard monitor code generator was not on the class path.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320020: Code generator {1} for standard monitor {0} could not be instantiated.

Cause: The standard monitor code generator is missing the default constructor.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320021: The code generator {1} could not be accessed for standard monitor {0}.

Cause: The standard monitor code generator implementation has problems.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320022: An error was encountered while creating SerialVersionUID for class {0}.

Cause: This is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320023: File {0} does not contain a valid Java class

Cause: The file does not contain a valid Java class.

Action: Make sure that the file being instrumented is a valid Java class file.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320024: Class in file {0} could not be instrumented.

Cause: This can happen when the input file or output file cannot be read from or written to.

Action: Check the file permissions and disk space.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320025: Input file {0} for instrumentation engine cannot be found.

Cause: The input class file does not exist.

Action: Provide the correct path to the input class file.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320026: Monitor {0} could not be found in instrumentation engine configuration.

Cause: The monitor name may be misspelled.

Action: Specify the correct monitor name on the command line.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320030: Delegating monitor {1} in scope {0} allows using action of type {2}, which does not exist.

Cause: A delegating monitor was not properly configured in the instrumentation engine configuration.

Action: Contact My Oracle support.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320031: An attempt to add a monitor of type {1} to instrumentation scope {0} failed because the monitor already exists in the scope.

Cause: Instrumentation configuration was incorrect.

Action: Remove multiple monitor entries with same types from the instrumentation scope configuration.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320032: Attempt to add duplicate action {2} to monitor {1} in scope {0} failed.

Cause: Instrumentation scope configuration is incorrect. It has duplicate actions attached to the same monitor.

Action: Remove duplicate actions attached to the same monitor.
Level: 1

Type: WARNING

Impact: Diagnostics

BEA-320033: Attempt to attach incompatible action of type {2} to a delegating monitor of type {1} in scope {0}.

Cause: Instrumentation configuration is incorect.

Action: Make sure that only compatible actions are used with delegating monitors.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320034: Instrumentation engine configuration {0} could not be parsed. {1}

Cause: The instrumentation configuration is malformed.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320035: Instrumentation configuration {0} could not be read.

Cause: The instrumentation configuration is missing or invalid.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320036: Instrumented method {1}{2} in class {0} exceeds size limit. Original method is preserved.

Cause: The original method is too large to begin with. The class to which it belongs is probably generated by a generator program.

Action: If possible, split the method into multiple methods. Exclude the class from instrumentation to speed up the instrumentation process.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320037: Class bytes for {0} do not conform to class format.

Cause: The class file is corrupt.

Action: Make sure that the class file is not corrupt.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320038: Could not instrument class {0}

Cause: This is a general instrumentation failure.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320039: Invalid class inclusion pattern(s) for instrumentation engine/scope {0}. Disabling instrumentation in scope {0}.

Cause: Inclusion patterns are malformed.

Action: Specify inclusion patterns in the correct format.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320040: Invalid class exclusion pattern(s) for instrumentation engine/scope {0}. Disabling instrumentation in scope {0}.

Cause: One or more exclusion patterns are malformed.

Action: Specify exclusion patterns in the correct format.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320041: Invalid lockout minutes {0} specified in image notification. Image capture was not performed.

Cause: The value is invalid.

Action: Recreate the notification with a valid lockout minutes value.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320042: Invalid diagnostic image location {0} specified in notification, exception message is {1}. Image capture was not performed.

Cause: The value is not a valid directory or file name.

Action: Recreate the notification with a valid image location. Take appropriate action based on the exception message.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320043: Image notification was not performed because the image capture was attempted before the lockout time expired. The exception message is {0}

Cause: An image capture was attempted before the lockout period expired.

Action: Recreate the image notification with a smaller value for lockout minutes. Optionally, use the watch alarm feature to ensure that the notification does not occur again before the lockout period has expired.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320044: Error occurred while performing a watch notification:

Cause: An error occurred while performing the operations required for the notification.

Action: Take appropriate action based on the unexpected exception message.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320047: Mail notification has not been sent due to an error that occurred while creating or sending a mail message:

Cause: An error occurred while performing the mail operations required for the notification.

Action: Verify the MailSession properties and email destination. Take appropriate action based on the Messaging exception message.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320048: JMS notification message has not been sent due to an error that occurred while creating a JMS map message:

Cause: An error occurred while performing the JMS operation.

Action: Verify the JMS queue and connection factory configuration settings in the JMS notification. Take appropriate action based on the JMS exception message.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320049: Exception occurred sending JMS notification message. Reinitializing JMS objects and retrying.

Cause: An error occurred while sending the JMS message.

Action: Look for additional error messages in the log from the reinitialization or resend of the message.
Level: 1

Type: WARNING

Impact: Diagnostics

BEA-320052: Error occurred while initializing a SMTP notification:

Cause: The mail session is incorrectly configured or not available.

Action: Ensure that the mail session JNDI name is correct. Ensure that the mail session MBean properties are valid. Take appropriate action based on the exception message.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320053: The SNMP Agent is not configured. The trap for the SNMP Watch notification cannot be sent.

Cause: The SNMP Agent is not enabled.

Action: Enable the SNMP Agent using the console.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320054: Error occurred while sending a SNMP notification:

Cause: An exception occurred in the SNMP Agent when sending the SNMP trap to the configured trap destinations.

Action: Ensure that the trap destinations are configured correctly. Take appropriate action based on the exception message.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320055: Could not read or create index on log file {0}

Cause: Disk may be full or directory is not writable

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

Type: ERROR

Impact: Diagnostics

BEA-320056: Log index file {0} has invalid magic number.

Cause: The index file is corrupt or invalid.

Action: Delete the corrupt index file.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320057: Log index file {0} contents are inconsistent with its header.

Cause: The index file is corrupt or truncated.

Action: Delete the index file.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320058: Could not parse log record: {0}

Cause: The log record is malformed.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320063: An attempt to add watch {0} failed because the watch has already been defined.

Cause: Two different watch definitions have the same name.

Action: Remove one of the watch entries that has the same name.
Level: 1

Type: WARNING

Impact: Diagnostics

BEA-320064: Watch {0} could not be created due to the following unexpected exception: {1}

Cause: An exception occurred unexpectedly.

Action: Take appropriate action based on the unexpected exception message.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320066: An attempt to add notification {0} failed because the notification has already been defined.

Cause: Two different notification definitions have the same name.

Action: Remove one of the notification entries with the same name.
Level: 1

Type: WARNING

Impact: Diagnostics

BEA-320068: Watch "{0}" in module "{1}" with severity "{2}" on server "{3}" has triggered at {4}. Notification details: {5}

Cause: Configured watch evaluated to true and triggered.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320069: Watch {0} contains an invalid notification {1} that is not defined.

Cause: The notification does not exist.

Action: Define the notification or remove the notification from the watch.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320070: Error occurred while performing notification {1} for watch {0}. Notification may not have completed.

Cause: An exception occurred while performing the notification.

Action: Validate the definition for the specified watch and notification. Take appropriate action based on the error message.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320071: Error occurred while creating watch notification {0}. Notifications may not have completed for this watch.

Cause: An exception occurred while creating the watch notification.

Action: Validate the definition for the specified watch and notification. Take appropriate action based on the error message.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320073: Error while locating a record for timestamp {0} in the archive

Cause: There is a misconfigured or missing data archive for harvested data.

Action: Check that the harvested data archive exists.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320074: Error while executing query.

Cause: Internal error

Action: Contact Oracle Support
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320075: Error while reading a record from the archive

Cause: The harvested data archive may be corrupt due to internal error.

Action: Reconfigure the harvested data archive. Contact My Oracle Support to report this problem.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320076: Could not initialize index information for harvester data archive.

Cause: The harvested data archive may be corrupt due to an internal error.

Action: Reconfigure the harvested data archive. Contact My Oracle Support to report this problem.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320077: Initialized the Diagnostic Accessor Service.

Cause: This is a normal operation.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320078: Could not initialize the Diagnostic Accessor Service Runtime during server startup.

Cause: The exception message includes the details about the cause of this problem.

Action: Take corrective action based on the exception stack trace. Contact My Oracle Support if this problem persists.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320079: Watch "{0}" rule expression evaluation failed with an exception. No notifications will be performed for this watch. The exception is:

Cause: An exception occurred during rule evaluation.

Action: Verify that the rule expression is valid. Take appropriate action based on the exception message.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320080: The log type {0} is unknown. Unable to lookup the DiagnosticDataAccessRuntimeMBean instance.

Cause: This message indicates that the logical name that was specified to look up the DiagnosticDataAccessRuntimeMBean is not correct.

Action: Verify that the log type is valid. Take appropriate action based on the exception message.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320082: Configuration for diagnostic monitor {0} in instrumentation scope {1} has errors. The exception is:

Cause: An exception occurred while reading the configuration of a diagnostic monitor in a scope.

Action: Verify that the configuration for the diagnostic monitor is valid.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320083: Custom diagnostic monitor {0} in instrumentation scope {1} has missing or invalid location attribute.

Cause: There is a missing or invalid value of the "location" attribute of a custom diagnostic monitor.

Action: Verify that the "location" attribute of the custom monitor has a correct value.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320084: The user {0} does not have authorization to view the logs.

Cause: A user with insufficient authorization attempted to access the server logs.

Action: Ensure that the right users are granted access to view the logs.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320085: The diagnostic data is accessible only through https in Production mode.

Cause: An attempt to access the diagnostic data was made over a non-secure protocol in Production mode.

Action: Ensure that the SSL is enabled in Production mode and that the servlet is accessed only over a secure protocol.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320086: The monitor type {1} in scope {0} contains unacceptable characters.

Cause: The monitor type contains unacceptable characters. It must start with an alphabetic character, followed by alphanumeric or underscore characters.

Action: Fix the assigned monitor type, which must start with an alphabetic character, optionally followed by alphanumeric or underscore characters.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320087: The cursor {0} has timed out and is being removed from the registry of open cursors.

Cause: This message is emitted when a cursor has not been invoked and is being removed to free up the associated resources.

Action: Ensure that fetch is not called anymore on the closed cursor.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320088: The cursor with name {0} does not exist.

Cause: The cursor could have timed out or been closed by the user explicitly. Otherwise, or an invalid name has been provided.

Action: Invoke the fetch method with the name of a valid cursor.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320091: Attempt to use unknown action {1} in action group {0}

Cause: This is due to an incorrect or incomplete instrumentation engine configuration.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320092: Monitor {0} used empty or non-existent action group {1}

Cause: This is due to an incorrect or incomplete instrumentation engine configuration.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320093: Encountered problem while reading attributes of monitor {0}. Attributes: {1}

Cause: Possibly invalid attribute names were specified with the diagnostic monitor.

Action: Specify correct attributes for the diagnostic monitor.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320094: Could not initialize server instrumentation scope.

Cause: Internal error

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320096: Cannot create custom monitor {0} in server instrumentation scope.

Cause: Custom monitors can not be defined in the server instrumentation scope.

Action: Remove the custom monitor definition from the server instrumentation scope.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320097: Monitor {0} can be created only in an application instrumentation scope. It cannot be created in server instrumentation scope.

Cause: An attempt was made to create a monitor in the server scope, but it can only be created in the application scope.

Action: Remove the monitor definition from the server instrumentation scope.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320098: Monitor {0} can be created only in server instrumentation scope. It can not be created in application instrumentation scope {1}.

Cause: An attempt was made to create a monitor in the application scope, but it can only be created in the server scope.

Action: Remove the monitor definition from the application instrumentation scope.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320100: Configuration for JDBC-based diagnostic archives is invalid or incomplete. Using file based diagnostic archive.

Cause: The configuration for JDBC-based diagnostic archives is invalid or incomplete.

Action: Fix the configuration for JDBC-based diagnostic archives.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320101: Attempt to target more than one WLDFSystemResource to server {0}.

Cause: This error indicates that an invalid targeting was specified for a WLDFSystemResource.

Action: Ensure that only one WLDFSystemResource is targeted to a server.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320102: An error occcurred when trying to access the diagnostic data while executing the query expression {0}.

Cause: The query was not specified properly.

Action: Ensure that the query is valid.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320103: An error occurred while creating the DiagnosticDataRuntimeMBean instance with the given logical name {0}.

Cause: The logical name is not a valid parameter or an error occurred while reading the diagnostic data.

Action: Ensure that the logical name is valid and take corrective action based on the reported error.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320104: An error occurrred when invoking the log4j operation while activating/deactivating log watch rules.

Cause: The log4j libraries may not be in the CLASSPATH.

Action: Ensure that the log4j libraries are available when using Log watch rules with Log4j enabled.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320105: The watch rule expression {0} is not valid.

Cause: The watch rule expression does not conform to the correct syntax.

Action: Specify a valid watch rule expression.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320106: The watch notification configuration already contains a notification with the given name {0}.

Cause: The name for the WLDFNotification you are adding is not unique.

Action: Specify a unique name for the notification.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320111: The elapsed time since the last Harvester cycle ({0} milliseconds) is unacceptably short. Skipping this cycle in order to smooth out the responses.

Cause: The previous Harvesting process consumed a large percentage of the sample period. This can happen for 3 reasons: 1) you requested that a very large amount of data be harvested, 2) the system is consistently slow for some reason, 3) an intermittent service caused the process to slow down temporarily (for example, for garbage collection).

Action: No action is required. The Harvester will compensate by skipping cycles that occur too soon. If this happens consistently, either because you are harvesting a large amount of data, or the Harvester is running on a slow system, you can either increase the samplePeriod or increase system resources.
Level: 1

Type: WARNING

Impact: Diagnostics

BEA-320113: The type {0} is no longer being harvested.

Cause: This is caused by an earlier problem. Sufficient log messages should have been issued at the point of failure to allow the problem to be debugged. Note that the type will remain deleted until the Harvester configuration is reloaded. At that time, if the problem is not yet resolved, this message may be issued again.

Action: No action is required. Typically, this type of error will cause some of the requested data to not be harvested. It is advisable to fix the issue.
Level: 1

Type: WARNING

Impact: Diagnostics

BEA-320114: Initializing the Diagnostics Harvester.

Cause: This message is for informational purposes only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320115: The Harvester is configured to be disabled.

Cause: This message is for informational purposes only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320116: Harvester type {0} is configured to be disabled. No harvesting will occur for this type.

Cause: This message is for informational purposes only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320117: The Harvester is being disabled because there are no valid Harvestable types configured.

Cause: This may occur because you did not provide any type specifications, or, if type specifications were provided, none of the specified types were harvestable.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320118: The Harvester timer has been initiated for an interval of {0} milliseconds.

Cause: This message is for informational purposes only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320119: The Harvester is now in a {0} state.

Cause: This message is for informational purposes only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320122: Unable to harvest attribute {0} on item {1} due to errors. This attribute will no longer be harvested.

Cause: The actual problem occurred at a previous point in time. Sufficient messages should have been issued at the point of failure to facilitate debugging the problem.

Action: No action is required. Typically, this type of error will cause some of the requested data to not be Harvested. It is advisable to fix the issue.
Level: 1

Type: WARNING

Impact: Diagnostics

BEA-320123: Could not add MBean instance {0} to the harvested instance list for type {1}: {2}.

Cause: The actual problem occurred at a previous point in time. Sufficient messages should have been issued at the point of failure to facilitate debugging the problem.

Action: No action is required. Typically, this type of error will cause some of the requested data to not be Harvested. It is advisable to fix the issue.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320124: The harvester has discovered a new instance of harvested type {1} named {0}.

Cause: This message is for informational purposes only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320125: Attention: {0}

Cause: This indicates a system error, not a user error. Further investigation is required to determine the cause.

Action: The user should contact Oracle support to debug this problem. It is often possible to turn on Harvester debug to obtain additional information.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320126: Reinitializing the Diagnostics Harvester.

Cause: This message is for informational purposes only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320127: An error occurred while generating Image Source {0} as part of the diagnostic image zip file:

Cause: An unexpected error occurred while the subsystem was collecting or persisting the diagnostic image source information.

Action: Take appropriate action based on the unexpected exception message.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320128: The WLDFResourceBean is not found for the WLDFSystemResource {0}.

Cause: This error is caused by either a deleted or corrupt WLDF descriptor file.

Action: Ensure that the descriptor file exists for the WLDFSytemResource and that it conforms to the expected schema.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320129: Instrumentation module {0} created.

Cause: This message is for informational purposes only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320130: Instrumentation module {0} is disabled.

Cause: This instrumentation module for server or application is disabled.

Action: No action is required.
Level: 1

Type: WARNING

Impact: Diagnostics

BEA-320131: Instrumentation module {0} is configured, but disabled because a WLDF system resource is not targeted to the server, or its instrumentation component is not enabled.

Cause: There is no WLDF system resource targeted to the server, or its instrumentation component is disabled.

Action: Check if there is a WLDF system resource targeted to the server and its instrumentation component is enabled.
Level: 1

Type: WARNING

Impact: Diagnostics

BEA-320132: Updating classes within scope {0} since its instrumentation configuration has changed.

Cause: This message is for informational purposes only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320133: Could not instantiate one of the known accessors during server startup.

Cause: The exception message includes the details about the cause of this problem.

Action: Take corrective action based on the exception stack trace. Contact My Oracle Support if this problem persists.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320134: An internal error occurred while creating a domain log handler: {0}.

Cause: Refer to the embedded exception information for more details as to the probable cause of this error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320135: JDBC-based {0} archive could not be created. Falling back on persistent store based archive.

Cause: This happens when the JDBC data source to be used with the archive is misconfigured or unavailable, or database tables are not available.

Action: Ensure that the JDBC data source is correctly configured and available, and that database tables have been created prior to use.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320136: Class {0} could not be instrumented, due to reason: "{1}".

Cause: This can happen because the class may contain constructs that are unsafe to transform, for example, custom attributes.

Action: Ensure that class does not have custom attributes or other such constructs.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320137: Invalid class inclusion pattern(s) for instrumentation monitor {1} in scope {0}. Disabling instrumentation in scope {0}.

Cause: There are malformed inclusion patterns in the instrumentation monitor.

Action: Specify inclusion patterns in the instrumentation monitor using the correct format.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320138: Invalid class exclusion pattern(s) for instrumentation monitor {1} in scope {0}. Disabling instrumentation in scope {0}.

Cause: There are malformed exclusion patterns in the instrumentation monitor.

Action: Specify exclusion patterns in the instrumentation monitor using the correct format.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320139: Archive {0} is not found during a data retirement operation.

Cause: Data retirement may be configured for a custom archive that does not yet exist.

Action: Ensure that the custom archive is created, or disable or remove this retirement configuration.
Level: 1

Type: WARNING

Impact: Diagnostics

BEA-320140: Scheduling data retirement tasks as per configuration.

Cause: This is a normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320141: An error was encountered while performing age-based data retirement on archive {0}.

Cause: An error was encountered while performing age-based data retirement on the indicated archive.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320142: An error was encountered while performing size-based data retirement on archive {0}.

Cause: An error was encountered while performing size-based data retirement on the indicated archive.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320143: Scheduled {0} data retirement tasks as per configuration.

Cause: Finished processing the data retirement configuration.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320144: {0} operation started on archive {1}.

Cause: This is a normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320145: {0} operation completed on archive {1}. Retired {2} records in {3} ms.

Cause: This is a normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320146: Failed to register dye {0} at index {1}.

Cause: A dye with the same name or index already exists.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320147: Instrumentation system is disabled because the instrumentation library is invalid.

Cause: The instrumentation engine configuration is corrupt or a required DyeInjection monitor cannot be found.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320148: Required diagnostic monitor {0} is missing from the instrumentation library.

Cause: The instrumentation engine configuration is corrupt.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320149: The DomainRuntime MBeanServer was not available for harvesting.

Cause: The DomainRuntime MBeanServer could not be loaded by the Harvester.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320151: The instance name {0} in the Watch configuration {1} is invalid.

Cause: The instance name or instance-name pattern was not a valid JMX ObjectName or instance name pattern supported by the WLDF Watch and Notifications framework.

Action: Check that the instance name is a valid ObjectName, or an instance-name pattern as specified in the WLDF Watch and Notifications framework documentation.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320152: An unexpected exception occurred while removing the set of watched metrics "{0}" from the harvester: {1}

Cause: An attempt was made to delete a set of watched metrics from the harvester that has already been removed, or one that was never activated within the harvester.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320153: Instrumentation configuration for application "{0}" has changed. However, it will take effect only after redeploying the application, since hot-swap is not enabled.

Cause: Hot-swap is not enabled.

Action: Redeploy the application, or restart the server with the diagnostic agent on the command line to enable hot-swap.
Level: 1

Type: WARNING

Impact: Diagnostics

BEA-320154: Class redefinition failed after instrumentation configuration was changed for application "{0}" : {1}

Cause: An unexpected exception occurred while redefining classes after the instrumentation configuration was updated.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320155: Inconsistent instrumentation handling information was specified in the same pointcut definition for {0} : {1} : {2}.

Cause: The instrumentation configuration contains a pointcut definition that specifies conflicting information for the method.

Action: Review the pointcuts that specify the method listed in the error, and verify that there are not multiple definitions for the methods with which they conflict. For example, one indicating an argument is not-sensitive while another indicates it is.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320156: The renderer class {0} could not be loaded due to {1}, the following renderer will be used instead: {2}.

Cause: The instrumentation configuration specified a renderer class that either was not found, is not accessible, or is not a renderer.

Action: Verify that the renderer class is correctly specified in the instrumentation configuration and that it is available to the server classloader.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320157: An error occurred when registering the log4j for data gathering operations.

Cause: The log4j libraries may not be in the CLASSPATH.

Action: Ensure that the log4j libraries are available when using Log watch rules with Log4j enabled.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320158: An error was detected while capturing the flight recorder image.

Cause: The specified exception provides details on the error that was encountered.

Action: Review the provided exception information to determine the cause and action to take.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320159: An error was detected while initializing the flight recording.

Cause: The specified exception provides details on the error that was encountered.

Action: Review the provided exception information to determine the cause and action to take.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320160: The type-based renderer class {0} for type {1} could not be loaded due to {1}, that type-based renderer will not be used.

Cause: The instrumentation configuration specified a type-based renderer class that either was not found, is not accessible, or is not a renderer. It may also be that the type itself was not found or loadable.

Action: Verify that the type-based renderer class and type class are correctly specified in the instrumentation configuration and that they are available to the server classloader.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320161: Legacy Spring instrumentation API was called for an unknown method {0}.

Cause: A legacy Spring instrumentation API was called for an unknown method {0}.

Action: Instrument Spring using the tools in the current release.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320162: Legacy Spring instrumentation API was called.

Cause: A legacy Spring instrumentation API was called.

Action: Legacy Spring features should function normally, but you should instrument Spring using the tools in the current release.
Level: 1

Type: WARNING

Impact: Diagnostics

BEA-320163: Wildcarded types are not allowed to be marked as being insensitive with %

Cause: A % character was specified for a wildcarded type, such as an asterisk or ellipses. This is not allowed, as it could lead to inadvertantly exposing a type that should be treated as being sensitive.

Action: Review the pointcuts that specify the % character to ensure that it is not supplied for any types that are wildcarded using an asterisk or ellipses.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320164: Circular class load detected during stackmap frame computation for {0}.

Cause: An attempt was made to class load the class currently being instrumented. This is not supported.

Action: Do not instrument the class that encountered the cycle.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320300: The WLS ServerRuntime MBeanServer was not available for harvesting; custom MBean harvesting will not be available.

Cause: This could be the result of a serious error in the OA&M infrastructure. Check for other error messages in the log in that area.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: DiagnosticsHarvester

BEA-320301: The WLDF Harvester could not activate the Watch and Notifications framework due to an exception: {0}

Cause: During server startup, the Watch and Notifications activation is deferred until the WLDF Harvester is fully activated. The deferred activation encountered an unexpected exception, potentially impairing the Watch and Notifications functionality.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: DiagnosticsHarvester

BEA-320303: The namespace {1} for the harvested type specification {0} can not be serviced by a Managed Server instance; it is valid only when targed to an Administration Server.

Cause: A harvested type specifying the DomainRuntime namespace was targeted to a Managed Server. A Managed Server can only service the ServerRuntime namespace.

Action: Correct the namespace declaration of the harvested type, or retarget the WLDF configuration to an Administration Server in order to service this type.
Level: 1

Type: WARNING

Impact: DiagnosticsHarvester

BEA-320304: The following errors were reported during the validation of the metrics for watched values {0}: {1}

Cause: Some of the configured harvested types may have errors, resulting in the harvester being unable to process them for collection.

Action: Correct any issues with the harvested type configuration.
Level: 1

Type: WARNING

Impact: DiagnosticsHarvester

BEA-320305: The instance name {0} is not a valid ObjectName or instance name pattern.

Cause: The instance name must be a valid JMX ObjectName, or a pattern conforming to the syntax supported by the WebLogic Diagnostics Framework.

Action: Correct the instance name in the harvested type.
Level: 1

Type: ERROR

Impact: DiagnosticsHarvester

BEA-320400: The log file {0} will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms, such as Windows.

Cause: This event happens whenever the log file is about to be rotated based on either size or time rotation criterion.

Action: On certain platforms, if some application is tailing the log, the rotation fails. Stop the application tailing and reopen the tail after the rotation is complete.
Level: 1

Type: NOTIFICATION

Impact: LoggingService

BEA-320401: The log file has been rotated to {1}. Log messages will continue to be logged in {0}.

Cause: This event happens after the log file is rotated based on either size or time rotation criterion.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: LoggingService

BEA-320450: The DebugScope name {0} is not valid.

Cause: The DebugScope with the given name is not defined in the ServerDebugMBean interface.

Action: Configure the debug scope with a valid name.
Level: 1

Type: ERROR

Impact: DebugModule

BEA-320451: An error occurred while applying the DebugScopes configuration.

Cause: This may be due to an I/O error while reading the DebugScopes from the disk.

Action: Take action based on the error stack trace.
Level: 1

Type: ERROR

Impact: DebugModule

BEA-320500: The built-in WebLogic Diagnostics Framework resource descriptor ${0} for the selected level &quot;{1}&quot; could not be found; setting built-in resource to ${2}.

Cause: The WebLogic Diagnostics Framework resource descriptor for the desired built-in monitoring state could not be loaded due to either an issue with the WebLogic Server kit installation or an environmental issue in the domain configuration.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: DiagnosticsRuntimeControl

BEA-320800: Failed to cache the instrumentation engine configuration at {0} with exception {1}

Cause: The destination file may not be writable or some other I/O error occurred.

Action: Check to see if the destination file is writable.
Level: 1

Type: ERROR

Impact: DiagnosticsInstrumentor

BEA-320801: Failed to load instrumentation engine configuration {0}.

Cause: The instrumentation engine configuraion may be missing or corrupt.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: DiagnosticsInstrumentor

BEA-320802: Missing the name attribute for the instrumentation engine configuration at {0}.

Cause: The engine configuration does not have the required name attribute.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: DiagnosticsInstrumentor

BEA-320803: Duplicate instrumentation engine configuration {0} found.

Cause: A duplicate instrumentation engine configuration was found.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: DiagnosticsInstrumentor

BEA-320804: Invalid parent "{1}" for instrumentation engine configuration "{0}".

Cause: The instrumentation engine configuration has an incorrect parent configuration.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: DiagnosticsInstrumentor

BEA-320805: Required root instrumentation engine configuration was not found.

Cause: The required root instrumentation engine configuration was not found.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: DiagnosticsInstrumentor

BEA-320806: Found circular dependency with instrumentation engine configurations: {0}

Cause: The instrumentation engine configurations are invalid.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: DiagnosticsInstrumentor

BEA-320807: Parent "{0}" for instrumentation engine configurations {1}.

Cause: The parent configuration for an instrumentation engine configuration cannot be located.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: DiagnosticsInstrumentor

BEA-320900: Agent will be unable to proxy for the agents specified due to Proxy initialization error.

Cause: Refer to exception message for cause of initialization failure.

Action: Take appropriate action based upon the specified exception message.
Level: 1

Type: ERROR

Impact: SNMP

BEA-320913: Failed to register Attribute Change listener {0} for MBean type {1} on server {2}.

Cause: This may be due to a misconfigured SNMPAttributeChange entry specification in config.xml. Please refer to the exception message for more specific cause information.

Action: Modify configuration of the SNMPAttributeChange entry or take appropriate action based upon the specific exception message.
Level: 1

Type: ERROR

Impact: SNMP

BEA-320918: Failed to add NotificationListener to logBroadcaster for SNMPLogFilter {0}.

Cause: Please refer to the exception message for more specific cause information.

Action: Take appropriate action based upon the specific exception message.
Level: 1

Type: ERROR

Impact: SNMP

BEA-320923: Error creating JMX Monitor {0} of type {1} for MBean {2}.

Cause: This may be due to a misconfigured Monitor entry specification. Please refer to the exception message for more specific cause information.

Action: Modify the configuration of the SNMPJMXMonitorMBean entry or take appropriate action based upon the specific exception message.
Level: 1

Type: ERROR

Impact: SNMP

BEA-320925: Failed to send Monitor trap for server {0} for type {1} for object {2}.

Cause: Please refer to the exception message for more specific cause information.

Action: Take appropriate action based upon the specific exception message.
Level: 1

Type: ERROR

Impact: SNMP

BEA-320927: SNMP agent is initializing.

Cause: This message is for informational purposes only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SNMP

BEA-320928: SNMP Agent initialization failed while accessing server information for the configured Domain.

Cause: Refer to earlier SNMP error log information for specific information on the cause of the problem.

Action: Take appropriate action based upon the specific exception message.
Level: 1

Type: ERROR

Impact: SNMP

BEA-320929: SNMP agent initialization completed successfully.

Cause: This message is for informational purposes only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SNMP

BEA-320930: SNMP Agent Generic coldStart trap sent.

Cause: This message is for informational purposes only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SNMP

BEA-320931: The SNMP trap version is {0}.

Cause: This message is for informational purposes only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SNMP

BEA-320937: Exception occurred sending SNMP message, {0}.

Cause: This is an internal error that occurred during the sending of an SNMP message using the TCP transport provider.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: SNMP

BEA-320938: SNMP Agent does not support setting values for MBean attributes through SNMP.

Cause: You attempted to set an MBean attribute using SNMP.

Action: Use JMX APIs to update the WLS configuration MBeans.
Level: 1

Type: ERROR

Impact: SNMP

BEA-320939: An error occurred while adding a row to the SNMP table for MBean {1} of type {0}.

Cause: This could be due to a row already existing in the SNMP Agent for the MBean or an error condition in the SNMP Agent.

Action: Take appropriate action based on additional information in the error stack trace.
Level: 1

Type: ERROR

Impact: SNMP

BEA-320940: An error occurred while deleting the row from the SNMP table for MBean {0}.

Cause: The specified MBean instance was not registered in SNMP or it could be due to an error condition in the SNMP Agent.

Action: Take appropriate action based on additional information in the error stack trace.
Level: 1

Type: ERROR

Impact: SNMP

BEA-320941: An SNMP message was received over the default channel instead of the dedicated SNMP channel.

Cause: This occurs when a dedicated Network Access Point for SNMP traffic has been configured and activated and an SNMP request is received over the default server channel.

Action: Direct the SNMP request to the configured channel.
Level: 1

Type: ERROR

Impact: SNMP

BEA-320942: The specified type name {0} is invalid.

Cause: The specified name is not recognized as a valid WebLogic Server MBean type.

Action: Please specify the correct name for a WebLogic Server Configuration or Runtime MBean type.
Level: 1

Type: ERROR

Impact: SNMP

BEA-320943: The specified attribute name {1} is not valid for the given type {0}.

Cause: The specified attribute name that is not valid was specified as part of the configuration.

Action: Please specify the correct attribute name for the WebLogic Server Configuration or Runtime MBean type.
Level: 1

Type: ERROR

Impact: SNMP

BEA-320944: The SecurityName attribute is not specified for the SNMPTrapDestination {0}.

Cause: The SNMP Agent's trap version is set to V3 and the SecurityName is not specified for the given SNMPTrapDestination.

Action: Please specify the SecurityName attribute for which the SNMP Agent will issue V3 traps.
Level: 1

Type: ERROR

Impact: SNMP

BEA-320945: The SNMP Agent's TrapVersion needs to be V2 or higher to be able to send INFORM notifications.

Cause: The SNMPAgentMBean's SNMPTrapVersion attribute is set to V1.

Action: Set the SNMPTrapVersion to V2 or higher in the configuration.
Level: 1

Type: ERROR

Impact: SNMP

BEA-320946: The SNMP Agent {0} is already deployed to server {1}.

Cause: An attempt was made to target multiple SNMPAgentDeploymentMBeans to the same WebLogic Server instance.

Action: Ensure that only one SNMPAgentDeploymentMBean is targeted to any Server in the domain.
Level: 1

Type: ERROR

Impact: SNMP

BEA-320947: The AuthenticationProtocol for SNMP Agent {0} cannot be noAuth when PrivacyProtocol {1} is specified.

Cause: An invalid combination of authentication and privacy protocols was configured.

Action: Specify either MD5 or DES as the AuthenticationProtocol in combination with Privacy.
Level: 1

Type: ERROR

Impact: SNMP

BEA-320948: The SNMPTrapDestinationMBean {0} has a higher SecurityLevel {1} than the SNMPAgent's SecurityLevel {2}.

Cause: An invalid combination of authentication and privacy protocols on the SNMPAgentMBean and security level on the SNMPTrapDestinationMBean has been configured.

Action: Specify the valid security level for the users and the trap destinations.
Level: 1

Type: ERROR

Impact: SNMP

BEA-320949: SNMPAgent {0} is configured with a security level of {1}; the security level of {3} for proxy {2} must not exceed that of the SNMP agent.

Cause: A security level on the SNMP proxy was configured that exceeds the security level of the SNMP agent that corresponds to its configured authentication and privacy protocols.

Action: Configure a level of security on the proxy that is lower than the security level of the SNMP agent. For example, if the SNMP agent is configured with authentication but no privacy, configure the security level of NOAUTH_NOPRIV or AUTH_NOPRIV on the proxy.
Level: 1

Type: ERROR

Impact: SNMP

BEA-320950: Failed to start the SNMP agent. If it failed to bind to the port, check if the port is available or the process has permission to bind to the port.

Cause: Binding to specified UDP and agentX ports is a common problem. The ports to which the agent binds may not be available. Also, on UNIX platforms, ports up to 1023 are protected and can be bound only by processes owned by root.

Action: Check whether the specified ports are available. On UNIX, the default UDP port (161) and master AgentX port (705) are protected to be used by processes owned by root. In that case, either start the server as root, or configure the SNMP agent to use port numbers higher than 1023.
Level: 1

Type: ERROR

Impact: SNMP

BEA-320951: Failed to initalize the SNMP AgentX master subagent. One possible cause is the failure to bind the Master agentX port. If this is the case, check to see if the specified AgentX port is available, or ensure that the process has permissions to bind to the desired port.

Cause: A common problem is with binding to the specified agentX port. The port to which the agent binds may not be available. Also, on UNIX platforms, ports up to 1023 are protected and can be bound only by processes owned by root.

Action: Check whether the specified port is available. On UNIX, the default master AgentX port (705) is protected to be used by processes owned by root. In that case, either start the server as root, or configure the SNMP agent to use port numbers higher than 1023.
Level: 1

Type: ERROR

Impact: SNMP

BEA-320952: Failed to send the SNMP trap or inform notification for trap OID {2}. Number of send attempts = {0}. Number of errors encountered = {1}. The detailed error message from the SNMP toolkit is {3}.

Cause: The SNMPTrapDestination(s) could be incorrectly configured or the SNMP Manager might not be running at the configured location.

Action: Ensure that the SNMP Manager is available at the configured SNMP TrapDestinations.
Level: 1

Type: ERROR

Impact: SNMP

BEA-320953: The SNMP Agent has been started on port {0}.

Cause: The SNMP Agent tries to bind to the configured port. If this port is not available due to another SNMP Agent being deployed to the same machine on another WebLogic Server instance then the SNMP Agent tries to find the nearest port and binds to it.

Action: No action is needed. The port number is also reflected in the UDPListenPort attribute of the SNMPAgentRuntimeMBean interface on this Server.
Level: 1

Type: NOTIFICATION

Impact: SNMP

BEA-320954: The SNMP Agent encountered an error while discovering Extensions {0}.

Cause: The SNMPAgent Extension provider implementations could not be loaded successfully.

Action: Take corrective action based on the exception details.
Level: 1

Type: ERROR

Impact: SNMP

BEA-320955: SNMP agent has been shut down.

Cause: This message is for informational purposes only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SNMP

BEA-320956: Error registering trap destination {0} for address {1}:{2}.

Cause: The host name specified in the SNMPTrapDestination configuraiton is not valid.

Action: Correct the configuration and start the SNMP agent again.
Level: 1

Type: ERROR

Impact: SNMP

BEA-340450: Descriptor {1} has no configuration-support in the weblogic-extension.xml file for application module {0}. JSR-88 updates will not be supported.

Cause: The configuration-support stanza was missing or has XML errors.

Action: Correct the weblogic-extension.xml file and redeploy the application.
Level: 1

Type: WARNING

Impact: CustomModule

BEA-340451: URI mismatch for base-URI ({2}) in the weblogic-extension.xml file for descriptor {1} in module {0}. Unpredictable results from JSR-88 updates are likely.

Cause: The custom-module URI does not match the configuration-support base-URI.

Action: Correct the base-URI in the configuration-support stanza of the weblogic-extension.xml file to match the custom-module URI and redeploy the application.
Level: 1

Type: ERROR

Impact: CustomModule

BEA-340452: Prepare to deploy descriptor {1} in application module {0}.

Cause: This is normal behavior.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: CustomModule

BEA-340454: Prepare update for descriptor {1} in application module {0}.

Cause: This is normal behavior.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: CustomModule

BEA-400000: Initializing message interception service.

Cause: WebLogic Server starts the message interception service.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: messaging.interception

BEA-400200: Incorrect arguments. Expects 2 arguments.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade-SecurityProviders

BEA-400201: Migrating old security provider JARS from {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade-SecurityProviders

BEA-400204: No security provider JARs have been upgraded.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade-SecurityProviders

BEA-400205: Copying the upgraded security provider JAR to {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade-SecurityProviders

BEA-400206: Completed upgrading of {0} old security provider JARs.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade-SecurityProviders

BEA-400207: Skipped converting {0} since it is a security provider JAR built with 9.0.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade-SecurityProviders

BEA-400208: No MDFs (.xmls) found in the old security provider JAR with name {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade-SecurityProviders

BEA-400209: Created new security provider JAR {0} from {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade-SecurityProviders

BEA-400210: The XML file {0} is not a valid MDF, hence the upgrade tool will ignore this file.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade-SecurityProviders

BEA-400211: Not upgrading {0} because either this is an out-of-the-box Oracle security provider JAR or this security provider JAR is already upgraded or this is not a valid archive file (may not be a .jar).

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade-SecurityProviders

BEA-400212: Now processing {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade-SecurityProviders

BEA-400213: Could not convert from MDF {0}. This file may not be a valid MDF file; verify.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade-SecurityProviders

BEA-400214: Running the first phase of Security Provider Upgrade process on {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade-SecurityProviders

BEA-400215: First phase successful, now running the second and last phase of security provider upgrade process on {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade-SecurityProviders

BEA-420000: The message interception service cannot bind "{0}" to the local JNDI.

Cause: The JNDI name was already used.

Action: Avoid using JNDI names starting with weblogic. Correct this problem then try again.
Level: 1

Type: WARNING

Impact: MIExceptions

BEA-420002: The addAssociation method encountered an input error due to "{0}".

Cause: There was an illegal usage of the addAssociation API.

Action: If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420003: The addAssociation method encounters some usage error due to "{0}".

Cause: The interception point type is unknown either due to typo or the registerInterceptionPointNameDescription method didn't register the expected interception point type first.

Action: If this is caused by an external application then fix the related code. Otherwise, contact the customer support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420004: The removeAssociation method encountered an input error due to "{0}".

Cause: There was an illegal usage of the removeAssociation API.

Action: If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420005: The registerInterceptionPointNameDescription method encountered an input error due to "{0}".

Cause: There was an llegal usage of the registerInterceptionPointNameDescription API.

Action: If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420006: The registerInterceptionPoint method encountered an input error due to "{0}".

Cause: There was an illegal usage of the registerInterceptionPoint API.

Action: If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420007: The registerInterceptionPoint method encountered a usage error due to "{0}".

Cause: The interception point type is unknown either due to a typo or the registerInterceptionPointNameDescription method did not register the expected interception point type first.

Action: If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420008: The unRegisterInterceptionPoint method encountered an input error due to "{0}".

Cause: There was an illegal usage of the unRegisterInterceptionPoint API.

Action: If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420009: The registerProcessorType method encountered an input error due to "{0}".

Cause: There was an illegal usage of the registerProcessorType API.

Action: If this is caused by an external application, then fix the related code; Otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420010: The addProcessor method encountered an input error due to "{0}".

Cause: There was an illegal usage of the addProcessor API.

Action: If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420011: The addProcessor method encountered a usage error due to "{0}".

Cause: The processor type is unknown either due to a typo or the registerProcessorType method did not register the expected processor type first.

Action: If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420012: The removeProcessor method encountered an input error due to "{0}".

Cause: There was an illegal usage of the removeProcessor API.

Action: If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420013: The getAssociationHandle method encountered an input error due to "{0}".

Cause: There was an illegal usage of getAssociationHandle API.

Action: If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420014: The getProcessorHandles method encountered an input error due to "{0}".

Cause: There was an illegal usage of the getProcessorHandles API.

Action: If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420015: The getProcessorHandle method encountered an input error due to "{0}".

Cause: There was an illegal usage of the getProcessorHandle API.

Action: If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420016: The registerInterceptionPointNameDescriptionListener method encountered an input error due to "{0}".

Cause: There was an illegal usage of the registerInterceptionPointNameDescriptionListener API.

Action: If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420017: The removeAssociation method encountered an input error due to "{0}".

Cause: There was an illegal usage of the removeAssociation API.

Action: If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420019: The process method encountered a usage error due to "{0}".

Cause: The required processor for the given association was not created at the time. To send a message to a target that has the given association defined, the processor specified in the association needs to be added beforehand.

Action: If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420020: The process method encountered a usage error due to "{0}".

Cause: The processor generated an illegal error.

Action: If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420021: The process method encountered a usage error due to "{0}".

Cause: The processor generated an illegal runtime exception.

Action: If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420025: The addAssociation method encountered a usage error due to "{0}".

Cause: The added association already exists.

Action: If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420026: The unregisterInterceptionPoint method encountered a usage error due to "{0}".

Cause: The interception point has already been removed.

Action: If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420027: The interception point name argument is invalid due to "{0}".

Cause: The interception point name argument is invalid for several possible reasons. For example, the total number of name element differs from what is being registered with the interception service or one name element is invalid by itself.

Action: If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420028: The removeProcessor method encountered a usage error due to "{0}".

Cause: The processor has been removed.

Action: If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420029: The registerProcessorType method encountered a usage error due to "{0}".

Cause: The processor factory class cannot be instantiated.

Action: If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420030: The registerProcessorType method encountered a usage error due to "{0}".

Cause: The processor factory class cannot be instantiated.

Action: If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420031: The process method encountered a usage error due to "{0}".

Cause: The processor is currently processing more intercepted messages than that the association's depth allows.

Action: Increase the depth on the association using the association handle object.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-1000000: The object to be used for reflection while looking up setter "{0}" is null.

Cause: The user may have passed null in as the object upon which to reflect.

Action: Contact BEA Customer Support.
Level: 1

Type: WARNING

Impact: ServiceHelper

BEA-1000001: While attempting to find a setter on object "{0}", the name of the setter is null.

Cause: The user may have passed null in as the name of the setter.

Action: Contact BEA Customer Support.
Level: 1

Type: WARNING

Impact: ServiceHelper

BEA-1000002: While attempting to find a setter on object "{0}", the type of the setter was null.

Cause: The user may have passed null in as the type of the setter.

Action: Contact BEA Customer Support.
Level: 1

Type: WARNING

Impact: ServiceHelper

BEA-1000003: The filter passed into the registerDependencyWithFilter method is null.

Cause: The user passed null in as the filter to the method registerDependencyWithFilter.

Action: Modify the code such that it does not pass null in as the filter to the method registerDependencyWithFilter.
Level: 1

Type: WARNING

Impact: ServiceHelper

BEA-1000004: The filter passed into the registerDependencyWithFilter method is null.

Cause: The user passed null in as the filter to the method registerDependency.

Action: Modify the code such that it does not pass null in as the filter to the method registerDependency.
Level: 1

Type: WARNING

Impact: ServiceHelper

BEA-1000005: The ServiceHelper service has been closed.

Cause: While waiting for a service object the ServiceHelper was closed.

Action: Do not close the ServiceHelper while waiting for a service object.
Level: 1

Type: WARNING

Impact: ServiceHelper

BEA-1000006: The timer expired while waiting for a service object with filter "{0}".

Cause: The service object corresponding to the given filter was not available within the specified timeout.

Action: Ensure the service is available in the timeout period.
Level: 1

Type: WARNING

Impact: ServiceHelper

BEA-1000007: Not yet implemented.

Cause: Using an unimplemented API.

Action: Contact BEA Customer Support.
Level: 1

Type: WARNING

Impact: ServiceHelper

BEA-1000008: Could not find a setter named "{0}" for type "{1}" on an object of type "{2}".

Cause: There was no method of the given name of the given type on the given class.

Action: Ensure the setter name is correct. Ensure the object upon which it is looking for such a method has the method.
Level: 1

Type: WARNING

Impact: ServiceHelper

BEA-2004000: An error occurred while loading the Kodo-Oracle message dictionary.

Cause: This can happen if the Kodo-Oracle message dictionary is not available. This dictionary should be located at {0}.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: Kodo Integration

BEA-2004001: The Kodo-Oracle message dictionary was not found.

Cause: This can happen if the Kodo-Oracle message dictionary is not available. This dictionary should be located at {0}.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: Kodo Integration

BEA-2004003: Kodo localization key {0} has already been registered in the Kodo-Oracle message ID dictionary. Original value: {1}. New value: {2}. New definition from URL: {3}. The original value will be used.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Kodo Integration

BEA-2011000: The bundle {0} has started successfully.

Cause: This is a normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HarvesterAPI

BEA-2011099: The bundle {0} has been successfully stopped.

Cause: This is a normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HarvesterAPI

BEA-2011100: The bundle {0} has successfully started.

Cause: This is a normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HarvesterJMX

BEA-2011101: An unexpected Exception occurred in harvester {0}. Logging it here and continuing processing... Context: {1}, Exception: {2}

Cause: An unexpected exception occurred during the harvesting process.

Action: You should attempt to uncover the reason for the underlying Exception.
Level: 1

Type: WARNING

Impact: HarvesterJMX

BEA-2011102: An unexpected condition was encountered in harvester {0}. Logging it here and continuing processing... Context: {1}

Cause: An unexpected condition occurred during the harvesting process.

Action: The user should attempt to uncover the reason for the problem.
Level: 1

Type: WARNING

Impact: HarvesterJMX

BEA-2011103: Service with name: {0} has been prepared.

Cause: This is a normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HarvesterJMX

BEA-2011104: Service with name: {0} has been acivated.

Cause: This is a normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HarvesterJMX

BEA-2011105: Service with name: {0} has been deactivated.

Cause: This is a normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HarvesterJMX

BEA-2011199: The bundle {0} has successfully been stopped.

Cause: This is a normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HarvesterJMX

BEA-2011300: The bundle {0} has successfully started.

Cause: This is a normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HarvesterUtils

BEA-2011399: The bundle {0} has successfully been stopped.

Cause: This is a normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HarvesterUtils

BEA-2012300: The bundle {0} has successfully started.

Cause: This is a normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MBeanTypingUtil

BEA-2012301: Processing {0} MBeans.

Cause: This is a normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MBeanTypingUtil

BEA-2012302: Processed {1} MBeans for MBean utility {0}.

Cause: This is a normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MBeanTypingUtil

BEA-2012303: The MBeanTypeUtil cannot process an MBean instance due to excp {0} on MBeanServer: {1} and MBean: {2} stack trace: {3} --- Retrying once...

Cause: This is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MBeanTypingUtil

BEA-2012304: The MBeanTypeUtil failed for a second time to process an MBean instance due to excp: {0} on MBeanServer: {1} and MBean: {2} stack trace: {3} --- Skipping this MBean...

Cause: This ia an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MBeanTypingUtil

BEA-2012305: The MBeanTypeUtil failed to process two distinct MBeans in a row. The most recent problem was on MBeanServer: {0} and MBean: {1} stack trace: {2} --- No further MBeans will be processed.

Cause: This is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MBeanTypingUtil

BEA-2012306: {1} Unable to process the {2} of MBean: {0} due to internal errors. The managed process might be shutting down. Stack trace: {3}

Cause: The process is most likely shutting down, so it is safe to ignore this.

Action: If the process is known to be active, contact My Oracle Support to determine why the MBean cannot be processed. Setting the module debug flag will cause stack traces to be printed.
Level: 1

Type: ERROR

Impact: MBeanTypingUtil

BEA-2012307: {1} Unable to process the {2} of MBean: {0} due to internal errors. The managed process appears to be shutting down. Stack trace: {3}

Cause: The process is most likely shutting down, so it is safe to ignore this.

Action: If the process is known to be active, contact My Oracle Support to determine why the MBean cannot be processed. Setting the module debug flag will cause stack traces to be printed.
Level: 1

Type: WARNING

Impact: MBeanTypingUtil

BEA-2012308: An uexpected error occurred while scheduling work for MBeanTypeUtil instance {0} with work manager {1}: {2}

Cause: Possibly no work manager was set, or the work manager was unable to queue the request.

Action: If the problem persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MBeanTypingUtil

BEA-2012309: An uexpected error occurred while communicating with the MBeanServer: {0}

Cause: The MBeanServer or host process may no longer be available. If the MBeanServer is remote, there may be network issues.

Action: If the problem persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MBeanTypingUtil

BEA-2012399: The bundle {0} has been successfully stopped.

Cause: This is a normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MBeanTypingUtil

BEA-2150001: Validation of weblogic-pubsub.xml descriptor file failed. The error is {0}

Cause: There are errors in the weblogic-pubsub.xml descriptor file.

Action: Correct the error in weblogic-pubsub.xml according to the schema.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150002: No permission on channel operation: User {0} has no permission to create channel {1}

Cause: There are not sufficient privileges to create a channel.

Action: Check the PubSub server configuration security settings.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150003: No permission on channel operation: User {0} has no permission to delete channel {1}

Cause: There are not sufficient privileges to delete a channel.

Action: Check the PubSub server configuration security settings.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150005: Invalid persistent-client-timeout-secs: {0}.

Cause: The persistent-client-timeout-secs must be greater than the timeout-secs.

Action: Check the persistent-client-timeout in the PubSub server configuration
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150006: Invalid transport type: {0}

Cause: An invalid transport type was configured in the PubSub server configuration.

Action: Check the PubSub server configuration.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150007: Cannot find configuration for referenced message filter {0}; check message-filter in the PubSub server configuration.

Cause: There is a mismatch between the message filter name referenced in the channel setting and the message-filter setting.

Action: Check the PubSub server configuration.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150008: There is no message filter configured in the PubSub server configuration, but there is a message filter named {0} referenced in the channel setting.

Cause: The channel setting is requesting a message filter but the message filter was not specified in the PubSub server.

Action: Either specify the message-filter setting or remove the message-filter reference from the channel setting.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150009: Invalid message-filter configured: message-filter {0} is configured in PubSub server configuration, but its associated class {1} cannot be initialized correctly.

Cause: Class {1} associated with message filter {0} is incorrect.

Action: Check the message-filter-name and message-filter-class in the PubSub server configuration.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150011: Action {1} on channel {0} is not allowed for any client.

Cause: The PubSub server configuration constraints do not allow this action on this channel. This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP Pubsub Server

BEA-2150012: Client {0} is an anonymous user but channel {1} requests login.

Cause: Login is requested to perform this action. This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP Pubsub Server

BEA-2150013: Client {0} is not allowed to perform action {2} on channel {1}.

Cause: The PubSub server configuration does not allow this action on this channel. This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP Pubsub Server

BEA-2150014: Client {0} is allowed to perform action {2} on channel {1}

Cause: The PubSub server configuration is allowing this action to be performed on this channel. This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP Pubsub Server

BEA-2150015: Client {0} has no permission to subscribe channel {1}

Cause: Client {0} has no permission to subscribe channel {1}, either because the client configuration does not allow the client to access the channel, or the client is anonymous and the channel configuration only allows specific clients to access the channel.

Action: Check the PubSub server security constraint configuration.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150016: Client {0} has no permission to publish on channel {1}

Cause: The client is not configured to publish on the channel or the client is anonymous and the channel is configured to only allow access to specific clients.

Action: Check the PubSub server security constraint configuration.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150017: Failed to register MBean for Channel {0}

Cause: An exception occurred while registering the ChannelRuntimeMBean.

Action: Check the stack trace for more detailed information.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150018: Failed to unregister MBean for Channel {0}

Cause: An exception occurred while unregistering the ChannelRuntimeMBean.

Action: Check the stack trace for more detailed information.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150019: Initialize PubSub server {0}

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP Pubsub Server

BEA-2150020: Duplicate initialize PubSub server {0}

Cause: There are multiple servlet and servlet-mapping definitions for com.bea.httppubsub.servlet.ControllerServlet in the web.xml file.

Action: Check the web.xml file.
Level: 1

Type: WARNING

Impact: HTTP Pubsub Server

BEA-2150021: Cannot initialize service channel {0}

Cause: An exception occurred when initializing the service channel.

Action: Check the PubSub server configuration.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150024: Unknown meta channel found from Bayeux message: {0}

Cause: An incoming message specifies a channel other than /meta/handshake, /meta/connect, /meta/reconnect, /meta/disconnect, /meta/subscribe, or /meta/unsubscribe.

Action: Check the Bayeux client and the incoming Bayeux message.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150025: System property {0} is not set to specify an MBeanManagerFactory implementation.

Cause: System property {0} is not set.

Action: Ensure that runtime MBeans are not necessary; otherwise, set system property {0} to a proper implementation of MBeanManagerFactory.
Level: 1

Type: WARNING

Impact: HTTP Pubsub Server

BEA-2150026: Can not initialize instance of MBeanManagerFactory with class {0}

Cause: An exception occurred while initializing MBeanManagerFactory.

Action: Check the stack trace for more detailed information.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150027: Failed to register WebPubSubRuntimeMBean for PubSub server; the ContextPath is {0}

Cause: An exception occurred while registering WebPubSubRuntimeMBean.

Action: Check the stack trace for more detailed information.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150028: Failed to unregister WebPubSubRuntimeMBean for PubSub server; the ContextPath is {0}

Cause: An exception occurred while unregistering WebPubSubRuntimeMBean.

Action: Check the stack trace for more detailed information.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150029: ControllerServlet initialization failed: {0}

Cause: An exception occurred when ControllerServlet was initialized.

Action: Check the exception stack trace for details.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150030: Cannot fetch JSON message from incoming request

Cause: For long-polling request messages, messages are sent to the server as the body of a POST, encoded either as "application/x-www-form-urlencoded" or as "text/json". If sent as form encoded, the Bayeux messages are sent as the "message" parameter. For callback-polling request messages, messages are sent to the server either using POST requests as per long-polling transport or as the "message" URL parameter of a GET request.

Action: Check the incoming HTTP request and the Bayeux protocol specification.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150031: Cannot load properties from {0} in classpath.

Cause: The property file does not exist in the classpath.

Action: Check the classpath.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150032: Cannot find persistent store {0} specified to channel {1}; will use the default store.

Cause: The persistent store may not be configured properly.

Action: Check the configuration of the persistent store.
Level: 1

Type: WARNING

Impact: HTTP Pubsub Server

BEA-2150033: Invalid client-timeout-secs: {0}.

Cause: Either a negative or a zero value was set for client-timeout-secs.

Action: Check the PubSub server configuration.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150034: Invalid interval-millisecs: {0}.

Cause: A negative value was set for interval-millisecs.

Action: Check the PubSub server configuration.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150035: Invalid multi-frame-interval-millisecs: {0}.

Cause: A negative value wass set for multi-frame-interval-millisecs.

Action: Check tue PubSub server configuration.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150036: Invalid persistent-client-timeout-secs: {0}.

Cause: Either a negative value or zero was set for persistent-client-timeout-secs.

Action: Check the PubSub server configuration.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150037: Invalid max-persistent-message-duration-secs: {0}.

Cause: Either a negative value or zero was set for max-persistent-message-duration-secs.

Action: Check the PubSub server configuration.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150038: Initializing channel authorization manager: {0}

Cause: This channel authorization manager will be used for authorizing channel actions.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP Pubsub Server

BEA-2150039: Error initializing channel authorization manager.

Cause: The initialization of channel authorization manager failed.

Action: See the exception stack trace for details.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150041: Invalid channel {0}, cause is {1}.

Cause: An invalid channel field was found.

Action: Check the Bayeux client.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150042: A role {0} is being deployed implicitly without a pricipal mapping in the corresponding weblogic.xml.

Cause: There is no security-role-assignment for role {0}

Action: Create a security-role-assignment in weblogic.xml for role {0}
Level: 1

Type: WARNING

Impact: HTTP Pubsub Server

BEA-2150043: Security authorization has been disabled for the PubSub server.

Cause: PubSub server security has been disabled by an undocumented system property.

Action: If this property has not been set deliberately, verify all the system properties that begin with com.bea.httppubsub.security.
Level: 1

Type: WARNING

Impact: HTTP Pubsub Server

BEA-2150044: Invalid connection-timeout-secs: {0}.

Cause: Either a negative or a zero value was set for connection-timeout-secs.

Action: Check the PubSub server configuration.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150045: Incoming Bayeux message does not contain 'channel' field.

Cause: Incoming Bayeux message did not contain the 'channel' field.

Action: Turn on Bayeux message debug flag to check the Bayeux message sent by the client.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150046: Invalid JSON format of a Bayeux message

Cause: A Bayeux message could not be recognized by the JSON parser.

Action: Turn on the Bayeux message debug flag to check the Bayeux message and exception for details.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2152001: Cannot create a default JmsProviderFactory instance.

Cause: The class loader could not find the default JmsProviderFactory class in the classpath or the default JmsProviderFactory class has no public non-argument constructor.

Action: No action is required.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server JMS support

BEA-2152002: Cannot create JmsProviderFactory instance for given class name [{0}].

Cause: The class loader could not find {0} in the classpath or {0} has no public no-argument constructor.

Action: Ensure that the correct JmsProviderFactory class name is used.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server JMS support

BEA-2152003: JmsProviderFactory [{0}] registered.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP Pubsub Server JMS support

BEA-2152021: Try to initialize JmsProvider using the following configurations: JmsProviderUrl -> [{0}]; ConnectionFactoryJndiName -> [{1}]; TopicJndiName -> [{2}].

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP Pubsub Server JMS support

BEA-2152022: Cannot retrieve ConnectionFactory or topic.

Cause: There were incorrect JMSHandler configurations in the weblogic-pubsub.xml file.

Action: Check the JMSHandler configurations in the weblogic-pubsub.xml file.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server JMS support

BEA-2152041: Channel-Handler mapping: [{0}] -> [{1}]

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP Pubsub Server JMS support

BEA-2152042: No ChannelBeans are configured in the descriptor file, ignore JMS channel mapping initialization.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP Pubsub Server JMS support

BEA-2152043: Total [{0}] JMS handler mapping configuration(s) found.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP Pubsub Server JMS support

BEA-2152044: JMS handler mapping: [{0}] -> [{1}]

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP Pubsub Server JMS support

BEA-2152061: Cannot initialize JMS channel [{0}].

Cause: A JMS-related exception occurred.

Action: Ensure that the JMS configurations are correct and that the JMS server has been started.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server JMS support

BEA-2152081: Cannot publish message to JMS topic.

Cause: A JMS-related exception occurred.

Action: No action is required.
Level: 1

Type: WARNING

Impact: HTTP Pubsub Server JMS support

BEA-2152082: Cannot initialize publish functionality for JMS channel.

Cause: A JMS-related exception occurred.

Action: Check the configuration for the JMS connection factory and topic.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server JMS support

BEA-2152101: No permission to publish to channel {0}.

Cause: The security permission was not configured properly.

Action: Check the security configuration in the weblogic-pubsub.xml file.
Level: 1

Type: WARNING

Impact: HTTP Pubsub Server JMS support

BEA-2152102: Cannot initialize topic listener for JMS channel.

Cause: A JMS-related exception occurred.

Action: Check the configuration for the JMS connection factory and topic.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server JMS support

BEA-2152103: Error occurs when retrieving a message from the JMS topic.

Cause: A JMS-related exception occurred.

Action: Check the messages published to the JMS topic, and enable the JMS log for analysis.
Level: 1

Type: WARNING

Impact: HTTP Pubsub Server JMS support

BEA-2154000: Enabling FastSwap on application "{0}".

Cause: This message is for informational purposes only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: FastSwap

BEA-2154001: Starting FastSwap operation on application "{0}".

Cause: This message is for informational purposes only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: FastSwap

BEA-2154002: Finished FastSwap operation on application "{0}" with status {1}.

Cause: This message is for informational purposes only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: FastSwap

BEA-2154003: FastSwap operation on application "{0}" failed: {1}.

Cause: One or more classes could not be redefined.

Action: Redeploy the application for updates to classes to take effect.
Level: 1

Type: ERROR

Impact: FastSwap

BEA-2156001: "config-root" {0} is not a directory.

Cause: The "config-root" may not have been set properly.

Action: Verify that the "config-root" is correct.
Level: 1

Type: WARNING

Impact: WebLogicDescriptorWL

BEA-2156002: Attribute "{0}": duration value "{1}" is not valid: {2}

Cause: The provided duration value was not a valid duration lexical representation.

Action: See the lexical rules for a javax.datatype.Duration, and ensure that the provided duration value is valid according to these rules.
Level: 1

Type: ERROR

Impact: WebLogicDescriptorWL

BEA-2156003: Attribute "{0}": logical store name value "{1}" is not valid.

Cause: The provided logical store name value was not a valid name. Logical store names must be valid Java identifiers.

Action: See the lexical rules for a Java identifier, and ensure that the logical store name follows these rules.
Level: 1

Type: ERROR

Impact: WebLogicDescriptorWL

BEA-2156004: Attribute "{0}": JNDI name value "{1}" is not valid.

Cause: The provided JNDI name value was not a valid name. JNDI names must be non-null and non-empty and meet the rules of the J2EE platform's JNDI implementation.

Action: See the lexical rules for a JNDI name, and ensure that the JNDI name follows these rules.
Level: 1

Type: ERROR

Impact: WebLogicDescriptorWL

BEA-2156200: Unable to load descriptor {1} of module {0}. The error is {2}.

Cause: The descriptor is not valid.

Action: Correct the descriptor.
Level: 1

Type: ERROR

Impact: Munger

BEA-2156201: An error occurred while parsing descriptors: {0}.

Cause: Check the stack trace.

Action: Check the stack trace.
Level: 1

Type: ERROR

Impact: Munger

BEA-2156202: References were found in the deployment plan for module "{0}" with URI, "{1}". The plan was merged.

Cause: The plan contained variable overrides.

Action: No action is required. This is an informational message.
Level: 1

Type: NOTIFICATION

Impact: Munger

BEA-2156203: A version attribute was not found in element "{0}" in the deployment descriptor {1}. A version attribute is required, but this version of the WebLogic Server will assume that the latest version is used. Future versions of WebLogic Server will reject descriptors that do not specify the Java EE version. To eliminate this warning, add an appropriate "version=" to element "{0}" in the deployment descriptor.

Cause: The required version attribute was missing.

Action: Add the version attribute with the appropriate JEE version value.
Level: 1

Type: WARNING

Impact: Munger

BEA-2156204: The root element {0} is missing in the descriptor file {1}.

Cause: The required root element was missing in the descriptor file.

Action: Add the root element to the descriptor file.
Level: 1

Type: ERROR

Impact: Munger

BEA-2156205: Updating the configuration with the deployment plan overrides for module "{0}" with URI, "{1}".

Cause: A deployment plan was specified for the application.

Action: No action is required. This is an informational message.
Level: 1

Type: NOTIFICATION

Impact: Munger

BEA-2156206: No module overrides were found in the deployment plan for module "{0}" with URI, "{1}". If overrides were expected for this module, verify the deployment plan.

Cause: The plan contained no matching variable overrides.

Action: No action is required. This is an informational message. It may be an expected action.
Level: 1

Type: NOTIFICATION

Impact: Munger

BEA-2156207: The variable assignment from the deployment plan with variable name "{0}" and XPath "{1}" will be included when overriding the deployment configuration.

Cause: The plan contained matching variable overrides.

Action: No action is required. This is an informational message used to troubleshoot deployment plan overrides.
Level: 1

Type: NOTIFICATION

Impact: Munger

BEA-2156208: The variable assignment from the deployment plan with variable name "{0}" and XPath "{1}" will be included when overriding the deployment configuration.

Cause: The plan contained matching variable overrides.

Action: No action is required. This is an informational message used to troubleshoot deployment plan overrides.
Level: 1

Type: NOTIFICATION

Impact: Munger

BEA-2156209: Applying the overrides from the deployment plan for module "{0}" with URI, "{1}".

Cause: A deployment plan was specified for the application.

Action: No action is required. This is an informational message.
Level: 1

Type: NOTIFICATION

Impact: Munger

BEA-2156210: Applying the override for variable "{0}" with XPath "{1}" and operation "{2}".

Cause: A deployment plan was specified for the application.

Action: No action is required. This is an informational message.
Level: 1

Type: NOTIFICATION

Impact: Munger

BEA-2156211: After applying the overrides from the deployment plan, the descriptor "{0}" is: "{1}".

Cause: A deployment plan was specified for the application. The descriptor was updated.

Action: No action is required. This is an informational message.
Level: 1

Type: NOTIFICATION

Impact: Munger

BEA-2156212: An error occurred while parsing the specifed XPath "{0}" : {1}.

Cause: The specified XPath value was invalid.

Action: Check the associated exception to determine the cause, and correct the XPath value.
Level: 1

Type: ERROR

Impact: Munger

BEA-2156213: An error occurred while parsing the specifed XPath "{0}" : {1}.

Cause: The specified XPath value was invalid.

Action: Check the associated exception to determine the cause, and correct the XPath value.
Level: 1

Type: ERROR

Impact: Munger

BEA-2156214: The XPath "{0}" specifies a key selection but the bean "{1}" does not have any keys defined.

Cause: The specified XPath value was invalid because no keys were defined for this element.

Action: Check the associated schema, and ensure that the element has the corresponding key.
Level: 1

Type: ERROR

Impact: Munger

BEA-2156215: Removed the value matched by the deployment plan variable "{0}" with element name "{1}".

Cause: A deployment plan was specified for the application, and an element has been removed.

Action: No action is required. This is an informational message.
Level: 1

Type: NOTIFICATION

Impact: Munger

BEA-2156216: The deployment plan operation failed because there was no method named "{0}" on the bean "{1}" corresponding to the element "{2}".

Cause: A deployment plan operation requires a corresponding destroy, remove, or set method. This method was not present.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Munger

BEA-2156217: An error occurred while performing the plan operation for variable "{0}" with element name "{1}" : {2}.

Cause: An unexpected exception occurred during the deployment plan operation.

Action: Check the associated exception to determine the cause, and correct the issue.
Level: 1

Type: ERROR

Impact: Munger

BEA-2156218: Updated the element matched by the deployment plan variable "{0}" with element name "{1}" to have value "{2}".

Cause: A deployment plan was specified for the application, and a matching element has been updated.

Action: No action is required. This is an informational message.
Level: 1

Type: NOTIFICATION

Impact: Munger

BEA-2156219: Created the element matched by the deployment plan variable "{0}" with element name "{1}".

Cause: A deployment plan was specified for the application, and a matching element has been created.

Action: No action is required. This is an informational message.
Level: 1

Type: NOTIFICATION

Impact: Munger

BEA-2156220: Created the element matched by the deployment plan variable "{0}" with element name "{1}" to have name "{2}".

Cause: A deployment plan was specified for the application, and a matching element has been created.

Action: No action is required. This is an informational message.
Level: 1

Type: NOTIFICATION

Impact: Munger

BEA-2156221: The remove operation for the deployment plan variable "{0}" with element name "{1}" specified an array index of "{2}" but the array was smaller, so no elements were removed.

Cause: The specified array index was larger than the size of the array.

Action: No action is required. This is an informational message.
Level: 1

Type: NOTIFICATION

Impact: Munger

BEA-2156222: The variable "{0}" specifies a property "{1}" that is a primitive array but no index is specified in the XPath.

Cause: The specified XPath value was invalid since no array index was defined for this element.

Action: Check the XPath, and specify an index.
Level: 1

Type: ERROR

Impact: Munger

BEA-2156223: The variable "{0}" for the add operation does not specify a property in the XPath "{1}". This variable assignment has been ignored.

Cause: The specified XPath value was invalid since no property was specified for the add operation.

Action: Check the XPath, and specify a property.
Level: 1

Type: WARNING

Impact: Munger

BEA-2156224: Added the element matched by the deployment plan variable "{0}" with element name "{1}" with value "{2}".

Cause: A deployment plan was specified for the application, and a matching element has been added.

Action: No action is required. This is an informational message.
Level: 1

Type: NOTIFICATION

Impact: Munger

BEA-2156225: The XPath "{0}" contains a trailing invalid "/". It has been ignored. Remove it from the XPath expression.

Cause: The specified XPath value was invalid because it contained a trailing slash.

Action: Remove the trailing slash.
Level: 1

Type: WARNING

Impact: Munger

BEA-2156226: Skipping the override for the deployment plan variable "{0}" and XPath "{1}" since the value is not set in the deployment plan.

Cause: A deployment plan did not contain a value for the variable.

Action: Add a variable value if one is desired, or remove the variable assignment if it is not needed.
Level: 1

Type: NOTIFICATION

Impact: Munger

BEA-2156250: The value {1} is illegal for {0}. Legal value for this attribute is >= -1. Although the current release of WebLogic Server is accepting this value, future releases may reject the configuration.

Cause: The current WebLogic Server version accepts this value to support prior releases that allowed arbitrary negative values.

Action: Fix the configuration to specify a value for this parameter in the valid legal range.
Level: 1

Type: WARNING

Impact: WebLogicJavaEEDescriptorValidator

BEA-2156300: Coherence JAR is in the system classpath and there are more than one CoherenceClusterSystemResourceMBean defined using {0}

Cause: Multiple CoherenceClusterSystemResourceMBean were targeted.

Action: When the Coherence JAR is in the system classpath, only one CoherenceClusterSystemResourceMBean should be targeted to the server.
Level: 1

Type: NOTIFICATION

Impact: CacheProvider

BEA-2156301: Failed to shut down application {0} due to {1}

Cause: Failed to shut down application {0} due to {1}

Action: Examine the exception details and take corrective actions.
Level: 1

Type: ERROR

Impact: CacheProvider

BEA-2156400: The validation.xml file, located at {0}, does not conform to the JSR 303 specifications.

Cause: The file does not conform to the JSR 303 specification. This maybe because the file is intended to configure another validation framework or because of a typo in the file.

Action: JSR 303 specifies the location of the validator descriptor as either WEB-INF for web application or META-INF for all other cases. A validation.xml file at that location should only be used for the purpose of configuring javax.validation. If the purpose of the file is to configure another validation framework, consider using a different name or placing the file in a different location.
Level: 1

Type: WARNING

Impact: Weblogic-Validation

BEA-2156401: Invalid URL, {0}, because {1}.

Cause: Internal Error

Action: Contact Oracle Support for assistance.
Level: 1

Type: ERROR

Impact: Weblogic-Validation

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

Cause: Internal Error

Action: Contact Oracle Support for assistance.
Level: 1

Type: ERROR

Impact: Weblogic-Validation

BEA-2156403: Unable to process URL, {0}, because {1}.

Cause: The cause of the error is contained in the error message.

Action: Carefully examine the error message to determine the cause of the error and determine the best way to fix it.
Level: 1

Type: ERROR

Impact: Weblogic-Validation

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

Cause: Internal Error

Action: Contact Oracle Support for assistance.
Level: 1

Type: ERROR

Impact: Weblogic-Validation

BEA-2156405: Unable to read resource, {0}, because {1}

Cause: An IOException has occurred.

Action: Insure that the resource is available for read.
Level: 1

Type: ERROR

Impact: Weblogic-Validation

BEA-2159000: An exception occurred while the listener {1} processed event {0}. The error is {1}.

Cause: Refer to the embedded exception information for more details as to the probable cause of this error.

Action: Fix the issue related to the embedded root exception. If the listener associated with the exception is an Oracle class, contact My Oracle Support.
Level: 1

Type: WARNING

Impact: InternalEventBus

BEA-2159001: An exception occurred while initializing WLS internal event bus {0}. The error is {1}.

Cause: Refer to the embedded exception information for more details as to the probable cause of this error.

Action: This is an internal error and should be reported as a bug to My Oracle Support.
Level: 1

Type: ERROR

Impact: InternalEventBus

BEA-2159002: An exception occurred while loading the listener class {0}. The error is {1}. This listener will not be registered.

Cause: Refer to the embedded exception information for more details as to the probable cause of this error.

Action: Fix the issue related to the embedded root exception. If the listener associated with the exception is an Oracle class, contact My Oracle Support.
Level: 1

Type: WARNING

Impact: InternalEventBus

BEA-2159003: An exception occurred while instantiating an instance of listener class {0}. The error is {1}. This listener will not be registered.

Cause: Refer to the embedded exception information for more details as to the probable cause of this error.

Action: Fix the issue related to the embedded root exception. If the listener associated with the exception is an Oracle class, contact My Oracle Support.
Level: 1

Type: WARNING

Impact: InternalEventBus

BEA-2159004: An exception occurred while registering listeners defined as resources. The error is {1}.

Cause: Refer to the embedded exception information for more details as to the probable cause of this error.

Action: Fix the issue related to the embedded root exception. If the listeners associated with the exception are Oracle listeners, contact My Oracle Support.
Level: 1

Type: WARNING

Impact: InternalEventBus

BEA-2159005: An error occurred while processing the WebLogic internal events "{0}". The error is {1}.

Cause: See the embedded root exception.

Action: Fix the issue related to the embedded root exception.
Level: 1

Type: WARNING

Impact: InternalEventBus

BEA-2160000: Context "{0}" is not a web context. Spring runtime MBeans cannot be created.

Cause: The WeblogicSpringApplicationListener bean was added to (or registered as a listener on) an ApplicationContext that is not a web application context.

Action: Use WeblogicSpringApplicationListener only with a WebApplicationContext.
Level: 1

Type: WARNING

Impact: WeblogicSpring

BEA-2160001: WebAppComponentRuntimeMBean not found. Spring runtime MBeans cannot be created.

Cause: This is an internal error.

Action: Contact My Oracle Support. Please capture errors and send the server log files to support.
Level: 1

Type: WARNING

Impact: WeblogicSpring

BEA-2160002: "{0}" is not a registered scope name.

Cause: The scope name supplied to a runtime mbean operation is not registered.

Action: Supply a registered scope name to the runtime mbean operation.
Level: 1

Type: WARNING

Impact: WeblogicSpring

BEA-2162200: No Main-Class defined in the manifest file of Java Module: {0}. This module will be treated as a utility JAR and subsequent initialization steps will be skipped.

Cause: See the message body.

Action: No action is required unless you believe that this should be a Java client module. In this case, you should specify Main_Class for this module in MANIFEST.MF.
Level: 1

Type: WARNING

Impact: Application Client

BEA-2162206: Warning: Could not find an entry for javax.transaction.UserTransaction in the root context.

Cause: There is no entry for javax.transaction.UserTransaction in the root context.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: Application Client

BEA-2162210: No persistence unit named '{0}' is available in scope.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Application Client

BEA-2162224: No {0} was specified in your client-jar file: {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Application Client

BEA-2162500: Class, {0}, was compiled with an incompatible version of Java. Make sure that all the classes needed by the application have been compiled with a compatible java version. {1}

Cause: Class compiled with an incompatible Java compiler version.

Action: Insure that this and other classes are compiled with a compiler that is compatible with the JVM used by the application server.
Level: 1

Type: ERROR

Impact: Class Loaders

BEA-2162501: Class bytes found, but couldn't define class, '{0}' due to the following error: {1}

Cause: Unknown.

Action: Contact Oracle Support for assistance.
Level: 1

Type: ERROR

Impact: Class Loaders

BEA-2163000: OSGi system {2} could not install bundle from file {0} due to {1}

Cause: The OSGi system failed to install a bundle from a file.

Action: Fix the problem that is indicated in the error message and then restart the server.
Level: 1

Type: WARNING

Impact: OSGi

BEA-2163001: OSGi system {2} could not advertise data source {0} due to {1}

Cause: The OSGi system failed to advertise a data source.

Action: Fix the problem that is indicated in the error message and then restart the server.
Level: 1

Type: WARNING

Impact: OSGi

BEA-2163002: OSGi system {0} could not install bundles from $WL_HOME/server/osgi-lib.

Cause: At least one bundle from the $WL_HOME/server/osgi-lib directory could not be installed.

Action: Examine the bundles that failed to install, fix them, and then restart the server.
Level: 1

Type: ERROR

Impact: OSGi

BEA-2163003: Started OSGi system {0}.

Cause: An OSGi system has started.

Action: Write modular code and deploy it onto your OSGi system.
Level: 1

Type: NOTIFICATION

Impact: OSGi

BEA-2163004: OSGi system {2} could not advertise work manager {0} due to {1}

Cause: The OSGi system failed to advertise a work manager

Action: Fix the problem that is indicated in the error message and then restart the server.
Level: 1

Type: WARNING

Impact: OSGi

BEA-2163005: An application could not be deployed because it had conflicting OSGi framework names in its metadata. The OSGi framework names {0} and {1} were found.

Cause: More than one OSGi system was referenced in the application metadata files.

Action: Modify the metadata files of the application such that the application references only one framework.
Level: 1

Type: ERROR

Impact: OSGi

BEA-2163006: An application could not be deployed because it had conflicting OSGi bundle symbolic names in its metadata. The bundle symbolic names {0} and {1} were found.

Cause: More than one OSGi bundle was referenced in the application metadata files.

Action: Modify the metadata files of the application such that the application references only one bundle.
Level: 1

Type: ERROR

Impact: OSGi

12 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-00001: Loaded dispatcher configuration from preferences store: ChunkSize = {0} EngineEndpointUrl = {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

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-00008: DispatcherSettings node name = {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

BDSS-00009: DispatcherSettings absolute path = {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

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-00013: {0} users were successfully sent to engines for synchronization!

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

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 is unable to write an error message to the database for a particular PIM Map Record. In particular, the Sync-Engine detected an exception when invoking method SyncConfig::updatePimMapRecordError.

Action: Examine the Sync-Engine log to find the underlying exception message. Ensure that the BDSS database is accessible. Check configuration of the hub components and consider restarting the hub components.
Level: 1

Type: ERROR

Impact: Data

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.

BDSS-20011: The data from the Hub record is not available.

Cause:

Action:
Level: 1

Type: NOTIFICATION

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-20025: The calculated sync direction is {0} for the specified user, domain and connector.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

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-20034: A conflict between a deleted record and an updated record has been detected and resolved. The updated record event will be dropped and the deleted record event will propagate to the target PIM. Information about the two record events follow: \tDeleted Record: \t\tConnector = {0} \t\tPIM user = {1} \t\tPIM record identifier = {2} \tUpdated Record: \t\tConnector = {3} \t\tPIM user = {4} \t\tPIM record identifier = {5} {6}

Cause:

Action:
Level: 1

Type: NOTIFICATION

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-20051: BDSS Engine ExtractResponse servlet end point URL = {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

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-30008: Loaded engine configuration from preferences store: ExtractResponseTimeout = {0} MessageTimeToLive = {1} EngineEndPointURL = {2} RuntimeLibraryURL = {3}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

BDSS-30009: EngineSettings absolute path = {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

BDSS-30010: EngineSettings node name = {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

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-35056: Successfully created a Connector user with a login of {0} and mapped it to the hub user {1}. The user sync level for all domains is set to Full.

Cause:

Action:
Level: 1

Type: NOTIFICATION

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-35058: Successfully deleted hub user with the login {0} and the associated Connector users.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

BDSS-35059: Cannot find a hub user with the name {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

BDSS-35060: Successfully created a hub user with a login of {0} and mapped it to the Connector user ID {1}. The user is not sync enabled.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

BDSS-35061: Successfully changed Connector user sync level to {0} for Connector user {1} on domain {2} for the Connector named {3}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

BDSS-35062: Successfully changed hub user sync enabled flag to {0} for hub user with the name {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

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-35076: Cannot find the Connector {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

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: A generic connector method method failed with the specified result.

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

Type: ERROR

Impact: Other

Cause: The underlying cause may be due to a failure in the hub RuntimeLibrary.

Action: It may be useful to examine the hub log for a log message from the RuntimeLibrary component.

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.

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-60015: A PIM echo record has been detected. It will not be in an ExtractResponse sent to the hub.

Cause: A PIM Transport has provided an echo record as part of its extract response to the generic connector component.

Action: No action is needed as this is not an error. It is just a notification.
Level: 32

Type: TRACE

Impact: Data

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-60017: ExtractResponse content: Delete record count = {0}, UpsertRecord count: = {1}.

Cause:

Action:
Level: 32

Type: TRACE

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-60026: Field Name

Cause:

Action:
Level: 32

Type: TRACE

Impact: Logging

BDSS-60027: Field Value

Cause:

Action:
Level: 32

Type: TRACE

Impact: Logging

BDSS-60028: Field value is null.

Cause:

Action:
Level: 32

Type: TRACE

Impact: Logging

BDSS-60029: Begin PIM record description

Cause:

Action:
Level: 32

Type: TRACE

Impact: Logging

BDSS-60030: End PIM record description

Cause:

Action:
Level: 32

Type: TRACE

Impact: Logging

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

Cause: Synchronizing user does not have an Exchange mailbox account.

Action: Create a mailbox for the synchronizing user and attempt to synchronize again.
Level: 1

Type: ERROR

Impact: Configuration

Cause: Credentials used for Auto Discovery are invalid.

Action: Verify the domain, username and password configured for auto discovery are correct.

Cause: Service Connection Points could not be accessed.

Action: Verify the Service Connection Points URLs are configured correctly and accessible in Active Directory. If optional Service Connection Point URLs are configured in the BDSS data store, verify the URLs are correct and accessible.

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.

BDSS-65002: Attempting to discover Exchange account information for user {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

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

Cause: The specified configuration does not exist in the BDSS data store.

Action: Add the configuration to the BDSS data store and restart BDSS.
Level: 1

Type: ERROR

Impact: Configuration

Cause: The configuration is case sensitive.

Action: Verify the case of each configuration entry is correct and restart BDSS.

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.

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-65008: <Not Available>

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

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: Folder information for the user is not obtainable.

Action: Verify the domain target for the user has been configured correctly.
Level: 1

Type: ERROR

Impact: Configuration

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.

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

Cause: One or more of the following schema XML element attributes is undefined or has an invalid value in the XSD file: FolderClass, PimDomainId, DisposalType, ConflictResolutionType, targetNamespace.

Action: Verify the XSD contains the attributes and each attribute has a valid value. Restart BDSS.
Level: 1

Type: ERROR

Impact: Configuration

Cause: The XSD does not define a root element name.

Action: Add a XSD element node at the top level of the XSD and give it a name that describes the Pim domain. For example, <xsd:element name='ExchangeTaskDomain'>. Restart BDSS.

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

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

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

Cause: The field name is not spelled correctly in the XSD file for the domain.

Action: Verify the field name spelling and ensure it is of the correct case.
Level: 1

Type: ERROR

Impact: Data

Cause: The field name does not map to any of the Exchange Web Service built-in methods for the domain or has a invalid extended field definition.

Action: Verify the field name spelling and ensure it is of the correct case. Verify the field name maps to a Exchagne Web Service built-in method by name. For example, for the task domain, StartDate in the XSD maps to getStartDate of a Exchange Web Service TaskItem. If the field is defined as an extended field ensure the field is defined correctly in the XSD. If it is a non-named field, the PropertyName

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.

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

Cause: The field name is not spelled correctly in the XSD file for the domain.

Action: Verify the field name spelling and ensure it is of the correct case.
Level: 1

Type: ERROR

Impact: Data

Cause: The field name does not map to any of the Exchange Web Service built-in methods for the domain or has a invalid extended field definition.

Action: Verify the field name spelling and ensure it is of the correct case. Verify the field name maps to a Exchagne Web Service built-in method by name. For example, for the task domain, StartDate in the XSD maps to getStartDate of a Exchange Web Service TaskItem. If the field is defined as an extended field ensure the field is defined correctly in the XSD. If it is a non-named field, the PropertyName

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.

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: The domain targets could not be added to a folder management session.

Action: Verify the user has a valid domain target configured for each domain that is synchronized and reattempt synchronization.
Level: 1

Type: ERROR

Impact: Data

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.

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 is typically caused when the connector cannot discover the Exchange Web Service URL that it should use when synchronizing the user.

Action: Verify the user has an Exchange 2007 account and that the account is discoverable via the Microsoft Auto Discover service. Refer to Microsoft documentation for more information about the Auto Discovery service.
Level: 1

Type: ERROR

Impact: Data

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.

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 domain target for the user is invalid.

Action: Fix the domain target configuration for the user. If using the default folder of the domain, specify a value of 'Root'. If using sub-folders of the default domain folder, specify the directory path (i.e. 'Root\\SubFolderName1\\SubFolderName2\\etc...')
Level: 1

Type: ERROR

Impact: Configuration

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.

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-65034: Successfully initialized the Exchange 2007 Pim Transport

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

BDSS-65035: The users Exchange server is {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Data

BDSS-65036: Successfully initialized a synchronization session for the user.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Data

BDSS-65037: Successfully extracted {0} records from the domain.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Data

BDSS-65038: Successfully created the Exchange record.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Data

BDSS-65039: Successfully updated the Exchange record.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Data

BDSS-65040: Successfully deleted the Exchange record.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Data

BDSS-65041: Successfully ended the synchronization of the domain for the current synchronization session.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Data

BDSS-65042: Successfully ended the synchronization session for the user.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Data

BDSS-65043: Successfully shutdown the Exchange 2007 Pim Transport.

Cause:

Action:
Level: 1

Type: TRACE

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-65049: Attempting to discover user account information using Service Connection Point URL {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Data

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

Cause: The LDAP URL is specified incorrectly.

Action: Verify the LDAP URL is correct and accessible.
Level: 1

Type: WARNING

Impact: Configuration

Cause: The user whose credentials are used to access Active Directory has insuffient priviledges.

Action: Specify a user name and password that the connector should use when querying Active Directory. The security Map name must be exchange2007pimtransport and the security Key name must be activeDirectoryAdminCredential.

Cause: Active Directory does not have a 'configurationNamingContext' container object.

Action: Consult with the Active Directory administrator to resolve the issue. Note that if multiple Active Directory servers are configured, this error can be ignored if other Active Directory servers are configured correctly.

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.

BDSS-65051: Could not locate user account information using Service Connection Point URL {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Data

BDSS-65052: Found Service Connection Point URL {0}.

Cause:

Action:
Level: 16

Type: TRACE

Impact: Data

BDSS-65053: Removed domain from SCP URL. Original Url = {0}, new Url = {1}.

Cause:

Action:
Level: 16

Type: TRACE

Impact: Data

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-65055: Found configuration container. LDAP Url = {0}, Configuration Containger = {1}.

Cause:

Action:
Level: 16

Type: TRACE

Impact: Data

BDSS-65056: Could not find the configuration container using LDAP Url = {0}.

Cause:

Action:
Level: 16

Type: TRACE

Impact: Data

BDSS-65057: Received the following autodiscovery result: {0}.

Cause:

Action:
Level: 16

Type: TRACE

Impact: Data

BDSS-65058: Failed to connect to Service Connection Point Url or parse the autodiscovery results. Url = {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Data

BDSS-65059: Discovered the user using Service Connection Point {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Data

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 unindexed field definition in the XSD is configured incorrectly.

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

Type: ERROR

Impact: Configuration

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

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

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.

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-65081: Calling the Exchange Web Service method {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

BDSS-65082: Returned from the Exchange Web Service call to method {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

BDSS-65083: Failed to connect to Service Connection Point Url. Url = {0}. Http Status Code = {1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Data

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-65085: Successfully cached the following configuration option: Profile = {0}, Section = {1}, Parameter = {2}, Value = {3}.

Cause:

Action:
Level: 16

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 record may have been deleted.

Action: Resynchronize the user.
Level: 1

Type: ERROR

Impact: Data

Cause: The Exchange server may have not be available.

Action: Resynchronize the user.

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: An unexpected error occurred in the Hub.

Action: Examine the Hub log file to determine the root cause of the exception.
Level: 1

Type: ERROR

Impact: Data

Cause: A network error occurred.

Action: Attempt to synchronize the user again.

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-65095: Could not obtain record associated data from the BDSS Hub for the following Pim record identifiers because the records are not in the BDSS store: {0}

Cause:

Action:
Level: 1

Type: TRACE

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-65098: Failed to close a data output stream.

Cause:

Action:
Level: 16

Type: TRACE

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-65101: Received a subscription notification for the specified user and domain.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

BDSS-65102: Successfully established a subscription for the specified user and domain.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

BDSS-65103: Received a unsubscribe notification for the specified user and domain.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

BDSS-65104: Successfully ended a subscription for the specified user and domain.

Cause:

Action:
Level: 1

Type: NOTIFICATION

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: The domain filter XML file is invalid.

Action: Fix the domain filter XML file and redploy the Exchange connector.
Level: 1

Type: ERROR

Impact: Data

Cause: Internal programming error.

Action: Contact Oracle Support Services.

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: The domain filter XML file is invalid.

Action: Fix the domain filter XML file and redploy the Exchange connector.
Level: 1

Type: ERROR

Impact: Configuration

Cause: Internal programming error.

Action: Contact Oracle Support Services.

BDSS-65114: Expected a {0} expression. Actual expression was {1}.

Cause: The domain filter XML file is invalid.

Action: Fix the domain filter XML file and redploy the Exchange connector.
Level: 1

Type: ERROR

Impact: Configuration

Cause: Internal programming error.

Action: Contact Oracle Support Services.

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: The domain filter XML has a invalid LogicalExpression.

Action: Fix the domain filter XML file and redploy the Exchange connector.
Level: 1

Type: ERROR

Impact: Configuration

Cause: Internal programming error.

Action: Contact Oracle Support Services.

BDSS-65118: There is no expression to negate.

Cause: The domain filter XML has a invalid NotExpression element.

Action: Fix the domain filter XML file and redploy the Exchange connector.
Level: 1

Type: ERROR

Impact: Configuration

Cause: Internal programming error.

Action: Contact Oracle Support Services.

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-65120: The FieldUri child elements do not exist or are invalid.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

BDSS-65121: A FieldUri element must be embedded in an ComparisonExpression or ExistsExpression.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

BDSS-65122: A LogicalExpression is not completed after joining expressions.

Cause: The domain filter XML may be invalid.

Action: Fix the domain filter XML file and redploy the Exchange connector.
Level: 1

Type: ERROR

Impact: Configuration

Cause: Internal programming error.

Action: Contact Oracle Support Services.

BDSS-65123: Unable to build a NotExpression.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

BDSS-65124: Unable to apply a LogicalOperator to a LogicalExpression or as a operator joining two other expressions.

Cause:

Action:
Level: 1

Type: NOTIFICATION

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: The domain filter XML may be invalid.

Action: Fix the domain filter XML file and redploy the Exchange connector.
Level: 1

Type: ERROR

Impact: Data

Cause: Internal programming error.

Action: Contact Oracle Support Services.

BDSS-65127: There is no domain filter defined for the {0} domain.

Cause:

Action:
Level: 16

Type: NOTIFICATION

Impact: Configuration

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 by Exchange is invalid.

Action: Identify and fix the record in Exchange and resynchronize the user.
Level: 1

Type: ERROR

Impact: Data

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.

BDSS-65130: Could not update or delete an Exchange record because it has already been deleted.

Cause:

Action:
Level: 16

Type: NOTIFICATION

Impact: Data

BDSS-65131: Failed to find the identifier of an occurrence of a recurring calendar record. Occurrence date: {0}

Cause: The occurrence was deleted by the user before an update or delete could occur.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Data

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.

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

13 BI-DCBEANS-00001 to BI-DCBEANS-00017

BI-DCBEANS-00001: The Discoverer service is stopped.

Cause: The Discoverer service was stopped.

Action: Start the Discoverer service.
Level: 1

Type: ERROR

Impact: Process

BI-DCBEANS-00002: The Discoverer Viewer service is disabled.

Cause: The Discoverer Viewer service was stopped.

Action: Start the Discoverer Viewer service.
Level: 1

Type: ERROR

Impact: Process

BI-DCBEANS-00003: The Discoverer Plus service is disabled.

Cause: The Discoverer Plus service was stopped.

Action: Start the Discoverer Plus service.
Level: 1

Type: ERROR

Impact: Process

BI-DCBEANS-00004: The request is not supported. The argument {0} must be single-valued.

Cause: The user provided an argument that was not single-valued.

Action: Provide a single-valued argument.
Level: 1

Type: ERROR

Impact: Process

BI-DCBEANS-00005: The request is not supported. Version {0} must be an integer.

Cause: The argument provided by the user was not an integer.

Action: Provide an integer argument.
Level: 1

Type: ERROR

Impact: Process

BI-DCBEANS-00006: The request is not supported. Compatible version number {0} must be an integer.

Cause: The version number provided by the user was not an integer.

Action: Provide an integer version number.
Level: 1

Type: ERROR

Impact: Process

BI-DCBEANS-00007: The request requires API version {0}. This installation can accept only version {1}.

Cause: The API version requested was incompatible with the installation.

Action: Provide a compatible version number.
Level: 1

Type: ERROR

Impact: Process

BI-DCBEANS-00008: Refresh argument must be an integer number.

Cause: The user provided a refresh argument was not an integer.

Action: Provide an integer refresh argument.
Level: 1

Type: ERROR

Impact: Process

BI-DCBEANS-00009: cannot specify non-XML formats without a page number

Cause: The user did not provide the page number required for a non-XML format.

Action: Specify a valid page number.
Level: 1

Type: ERROR

Impact: Process

BI-DCBEANS-00010: cannot specify worksheet without workbook

Cause: The workbook could not be found.

Action: Refer log file for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCBEANS-00011: cannot specify workbook without connection parameters

Cause: The user did not provide the necessary connection parameters, or the supplied connection parameters were invalid.

Action: Specify valid connection parameters.
Level: 1

Type: ERROR

Impact: Process

BI-DCBEANS-00012: missing connection user

Cause: The specified connection user was not found.

Action: Specify a valid connection user.
Level: 1

Type: ERROR

Impact: Process

BI-DCBEANS-00013: Parameter {0} must be an ordered parameter.

Cause: The specified parameter was not an ordered parameter.

Action: Specify an ordered parameter.
Level: 1

Type: ERROR

Impact: Process

BI-DCBEANS-00014: The requested URL contains expired bookmarked edits to the worksheet.

Cause: The bookmarked edits for the worksheet have expired.

Action: Use a recent URL for the worksheet.
Level: 1

Type: ERROR

Impact: Process

BI-DCBEANS-00015: Discoverer Plus cannot be accessed via the Discoverer Viewer URL.

Cause: Discoverer Plus could not be accessed.

Action: Refer log file for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCBEANS-00016: Discoverer Plus is not supported. RMI server initialization failed.

Cause: Discoverer Plus was disabled because the RMI server initialization failed.

Action: Check the RMI server status in the Discoverer configuration.
Level: 1

Type: ERROR

Impact: Process

BI-DCBEANS-00017: Discoverer Plus is not supported. The RMI server is disabled in the Discoverer configuration.

Cause: Discoverer Plus was disabled because the RMI server was disabled.

Action: Enable the RMI server in the Discoverer configuration.
Level: 1

Type: ERROR

Impact: Process

14 BI-DCWBSVC-05001 to BI-DCWBSVC-05079

BI-DCWBSVC-05001: Error in connection list retrieval.

Cause: An error occurred during connection list retrieval.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05002: The connection does not exist in the connection store. Invalid connectionkey :{0}.

Cause: The connection list did not exist in connection store or invalid connection key :{0}.

Action: See the logs for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05003: The OLAP connection has an invalid dbname string. Use format host:port:sid.

Cause: The OLAP connection has an invalid dbname string.

Action: Use format is host:port:sid.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05004: Error retriving connection details.

Cause: An error occurred during connection details retrieval.

Action: Check whether the connection key is valid
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05005: Maximum sessions are in use. Unable to create new sessions.

Cause: Reached maximum sessions. Unable to create new sessions.

Action: Contact your Administrator.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05006: The OracleAS Single Sign-On user name is not set.

Cause: The OracleAS Single Sign-On user name was not set.

Action: Set the OracleAS Single Sign-On user name
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05007: The connection key is not set.

Cause: No connection key was not set.

Action: Set the connection key.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05008: The workbook is not set.

Cause: No workbook was set.

Action: Set the workbook.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05009: The worksheet is not set.

Cause: No worksheet was set.

Action: Set the worksheet.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05010: Error in setting the connection Key.

Cause: An error occurred while setting the Connection Key.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05011: Error resetting the connection Key.

Cause: An error occurred while resetting the Connection Key.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05012: attempting to perform operation with invalid data. The globally unique identifier (GUID) is null.

Cause: An attempt was made to perform an operation with invalid data. The globally unique identifier (GUID) is null.

Action: See whether you are an Oracle AS Single Sign-On user name.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05013: Error creating the Discoverer session.

Cause: An error occurred while creating the Discoverer session.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05014: error creating session for connectionKey :{0}

Cause: An errored while creating session for connection Key :{0}.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05015: authentication error in making a connection with connection key :{0}.

Cause: an authentication error occurred while making a connection with connection key :{0}.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05016: The password is missing.

Cause: No password was provided.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05017: An error occurrs while creating the BISession.

Cause: An error occurred while creating the BISession.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05018: An error in establishing the connection.

Cause: An error occurred while establishing the connection.This could be due to invalid connection details, EUL db is down.

Action: Check whether the connection details are correct and the EUL Database is up.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05019: Folder type is unsupported.

Cause: Unsupported folder type was used.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05020: Configuration file is not found :{0}.

Cause: Configuration file was not found :{0}.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05021: Configuration directory is not found :{0}.

Cause: Configuration directory was not found :{0}.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05022: XSD file {0} is not found.

Cause: XSD file {0} was not found.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05023: An error occurred while reading the XMLPublisher XSD file.

Cause: An error occurred while reading the BI Publisher XSD file.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05024: Error reading maxsession value from the configuration file.

Cause: An error occurred while reading the maxsession value file.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05025: Error reading WebServices status from the configuration file.

Cause: An error occurred while reading WebServices Status from the configuration file.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05026: Parameter type used is not supported.

Cause: Unsupported parameter type was used.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05027: Error getting the requested worksheet.

Cause: An error occurred while getting the requested worksheet.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05028: Error retrieving parameters of worksheet :{0}.

Cause: An error occurred while retrieving parameters of worksheet :{0}.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05029: Error retrieving parameter values for the worksheet :{0}.

Cause: An error occurred while retrieving parameter values for the worksheet :{0}.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05030: The worksheet does not exist :{0}.

Cause: Worksheet did not exist :{0}.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05031: Error opening the worksheet.

Cause: An error occurred while opening the worksheet.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05032: Parameter values are not set.

Cause: An I/O error occurred while exporting a data cell.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05033: The selected list contains null parameter.

Cause: Parameter values were not set.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05034: Error in OracleAS Single Sign-On Username or globally unique identifier(GUID) lookup.

Cause: An error occurred during OracleAS Single Sign-On User name/globally unique identifier (GUID) lookup.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05035: Invalid credentials.

Cause: Invalid credentials were provided.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05036: Access is denied for the user.

Cause: Access was denied for the user.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05037: Account is inactive for the user.

Cause: Account was inactive for the user.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05038: Account is diabled for the user.

Cause: Account was disabled for the user.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05039: Account is locked for the user.

Cause: Account was locked for the user.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05040: Authentication fails for the user.

Cause: Authentication failed for the user.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05041: Subscriber is not found for the user.

Cause: No subscriber was found for the user.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05042: unsupported result type :{0}.

Cause: Unsupported result Type :{0} was provided.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05043: invalid worksheet state

Cause: Invalid worksheet state

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05044: An error in rowset XML generation.

Cause: An error occurred during Rowset XML generation.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05045: No data is available for export.

Cause: No data was available for export.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05046: The export operation fails.

Cause: The export operation failed.

Action: See the application log or other errors on the screen for more details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05047: An error occurred during generation.

Cause: An error occurred during generation.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05048: No data is available for export.

Cause: This could be due to an issue within Oracle BI Discoverer.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05049: error during controller creation

Cause: An error had occurred during controller creation.

Action: See the log for details
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05050: error creating WSModel object

Cause: An error occurred while creating WSModel object.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05051: unable to lookup workbook :{0}

Cause: Lookup for workbook :{0} failed

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05052: unable to lookup worksheet :{0}

Cause: Worksheet :{0} lookup failed

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05053: Unable to look up parameters.

Cause: No parameters found.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05054: Connection to BI Discoverer Server is lost.

Cause: Connection to BI Discoverer Server was lost.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05055: BI Discoverer server session is closed.

Cause: BI Discoverer server session was closed.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05056: Error performing folder lookup for the folderpath :{0}.

Cause: An error occurred while performing folder lookup for the folderpath :{0}

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05057: Error clearing workbook cache.

Cause: An error occurred while clearing workbook cache.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05058: invalid session key :{0}.

Cause: Invalid session key :{0} was provided.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05059: Invalid query Key :{0}.

Cause: Query Key :{0} is not valid.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05060: Query identified by query key {0} is not complete.

Cause: Incomplete query was identified by query key {0}.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05061: The exported file is not found.

Cause: The exported file was not found.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05062: Nothing to print. Crosstab, table, or graph must be selected to print.

Cause: Nothing was selected to print.

Action: Either the crosstab, table, or graph must be selected in order to print.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05063: unable to generate PDF using the current settings.

Cause: PDF generation failed using the current settings.

Action: Change the settings by choosing the \"Printable page\" link in the actions section of the open worksheet.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05064: The visible option is not set to ALL or DISPLAYED.

Cause: The visible option was not set to ALL or DISPLAYED.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05065: WebServices cannot generate the PDF output as requested.

Cause: WebService was unable to generate the PDF output as requested.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05066: Oracle BI Discoverer is unable to determine if the worksheet contains page items.

Cause: Oracle BI Discoverer was unable to determine if the worksheet contains page items.

Action: See the other error messages for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05067: The measurement unit for printing is invalid.

Cause: The measurement unit for printing was invalid.

Action: Change the value and try again.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05068: Specified locale string is invalid.

Cause: An invalid locale string was specified.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05069: Oracle BI Discoverer Viewer is unable to scroll the graph to its proper position.

Cause: Oracle BI Discoverer Viewer was unable to scroll the graph to its proper position.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05070: Margin value is illegal.

Cause: An illegal margin value was supplied.

Action: Correct the value and try again.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05071: Selected orientation is illegal.

Cause: An illegal page orientation was selected.

Action: Try a different value.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05072: The selected paper size is illegal.

Cause: An illegal paper size was selected.

Action: Contact your OracleAS administrator.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05073: Oracle BI Discoverer is unable to generate PDF documents.

Cause: The PDF printing pool was no longer valid.

Action: Restart the application and try again.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05074: An illegal value is supplied for the selection of when to print the title, footnote, or page items.

Cause: An illegal value was supplied for the selection of when to print the title, footnote, or page items.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05075: An illegal scaling value.

Cause: An illegal scaling value was supplied.

Action: Try a different value.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05076: The PDF generator unable to calculate the column widths.

Cause: The PDF generator was unable to calculate the column widths.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05077: Invalid width specified for column at position {0}.

Cause: An invalid width was specified for the column at position {0}.

Action: See the logs for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05078: The specified worksheet layout is invalid.

Cause: An invalid worksheet layout was specified.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-DCWBSVC-05079: Webservice is disabled.

Cause: Webservice wasdisabled.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

15 BI-EUL-00001 to BI-EUL-00002

BI-EUL-00001: Error creating EUL

Cause: The user lacked sufficient privileges for EUL creation.

Action: Grant the privileges required to create an End User Layer.
Level: 1

Type: ERROR

Impact: Process

BI-EUL-00002: Error deleting EUL

Cause: The user lacked sufficient privileges for End User Layer deletion.

Action: Grant the privileges required to delete an End User Layer.
Level: 1

Type: ERROR

Impact: Process

16 BI-PDFRDR-02001 to BI-PDFRDR-02047

BI-PDFRDR-02001: I/O error during data cell export

Cause: An I/O error occurred while exporting a data cell.

Action: See the Discoverer log for details.
Level: 1

Type: ERROR

Impact: Process

BI-PDFRDR-02002: I/O error during crosstab export

Cause: An I/O error occurred while exporting a crosstab.

Action: See the Discoverer log for details.
Level: 1

Type: ERROR

Impact: Process

BI-PDFRDR-02003: An edge is out of range during crosstab export.

Cause: An edge was out of range while exporting a crosstab.

Action: Provide an edge value within the range specified.
Level: 1

Type: ERROR

Impact: Process

BI-PDFRDR-02004: A layer is out of range during crosstab export.

Cause: A layer was out of range while exporting a crosstab.

Action: Provide a layer value within the range specified.
Level: 1

Type: ERROR

Impact: Process

BI-PDFRDR-02005: A slice is out of range during crosstab export.

Cause: A slice was out of range while exporting a crosstab.

Action: Provide a slice value within the range.
Level: 1

Type: ERROR

Impact: Process

BI-PDFRDR-02006: A column is out of range during crosstab export.

Cause: A column was out of range while exporting a crosstab.

Action: Provide a column value within the range.
Level: 1

Type: ERROR

Impact: Process

BI-PDFRDR-02007: A row is out of range during crosstab export.

Cause: A row was out of range while exporting a crosstab.

Action: Provide a row value within the range.
Level: 1

Type: ERROR

Impact: Process

BI-PDFRDR-02008: An I/O error occurred during table export.

Cause: An I/O error occurred while exporting a table.

Action: See the Discoverer log for details.
Level: 1

Type: ERROR

Impact: Process

BI-PDFRDR-02009: An edge was out of range during table export.

Cause: An edge was out of range while exporting a table.

Action: Provide an edge value within the range specified.
Level: 1

Type: ERROR

Impact: Process

BI-PDFRDR-02010: A layer was out of range during table export.

Cause: A layer was out of range while exporting a table.

Action: Provide a layer value within the range specified.
Level: 1

Type: ERROR

Impact: Process

BI-PDFRDR-02011: A slice was out of range during table export.

Cause: A slice was out of range while exporting a table.

Action: Provide a slice value within the range.
Level: 1

Type: ERROR

Impact: Process

BI-PDFRDR-02012: A column was out of range during table export.

Cause: A column was out of range while exporting a table.

Action: Provide a column value within the range.
Level: 1

Type: ERROR

Impact: Process

BI-PDFRDR-02013: A row was out of range during table export.

Cause: A row was out of range while exporting a table.

Action: Provide a row value within the range.
Level: 1

Type: ERROR

Impact: Process

BI-PDFRDR-02014: An I/O error occurred during graph export.

Cause: An I/O error occurred while exporting a graph.

Action: See the Discoverer log for details.
Level: 1

Type: ERROR

Impact: Process

BI-PDFRDR-02015: I/O error while streaming to the XDO PDF processor

Cause: An I/O error occurred while streaming to the XDO PDF processor.

Action: See the Discoverer log for details.
Level: 1

Type: ERROR

Impact: Process

BI-PDFRDR-02016: The encoding supplied to XDO is not supported.

Cause: The encoding supplied to XDO was not supported.

Action: See the Discoverer log for details.
Level: 1

Type: ERROR

Impact: Process

BI-PDFRDR-02017: The PDF generator is already running.

Cause: The PDF generator was already running.

Action: See the Discoverer log for details.
Level: 1

Type: ERROR

Impact: Process

BI-PDFRDR-02018: A locale must be provided to print a PDF.

Cause: No local was provided.

Action: Povide a locale.
Level: 1

Type: ERROR

Impact: Process

BI-PDFRDR-02019: A PDFGraphLayout must be provided in the PDFWorksheet.

Cause: The required PDFGraphLayout was not provided in the PDFWorksheet.

Action: Provide a PDFGraphLayout.
Level: 1

Type: ERROR

Impact: Process

BI-PDFRDR-02020: As the graph layout is set to NONE, a grid view must be present in the PDFWorksheet.

Cause: The graph layout was set to NONE, so there must be a graph view present in the PDFWorksheet.

Action: See the Discoverer log for details.
Level: 1

Type: ERROR

Impact: Process

BI-PDFRDR-02021: As the graph layout is set to ONLY, a graph view must be present in the PDFWorksheet.

Cause: The graph layout was set to ONLY, so there must be a graph view present in the PDFWorksheet.

Action: Provide a worksheet which has a graph.
Level: 1

Type: ERROR

Impact: Process

BI-PDFRDR-02022: As the graph layout is set to a position, a graph view must be present in the PDFWorksheet.

Cause: The Graph Layout was set to a position, so there must be a graph view present in the PDFWorksheet.

Action: Provide a worksheet which has a graph.
Level: 1

Type: ERROR

Impact: Process

BI-PDFRDR-02023: As the graph layout is set to a position, a grid view must be present in the PDFWorksheet.

Cause: The graph layout was set to a position, so there must be a grid view present in the PDFWorksheet.

Action: Provide a worksheet with a grid view present.
Level: 1

Type: ERROR

Impact: Process

BI-PDFRDR-02024: No data is available.

Cause: Either the query was not run or no data was available in the worksheet.

Action: Rerun the query and see the Discoverer log for details.
Level: 1

Type: ERROR

Impact: Process

BI-PDFRDR-02025: The left and right margins are too big or the page width is too small.

Cause: Incompatible values were provided for side margins or page width.

Action: Change the margin size or page width.
Level: 1

Type: ERROR

Impact: Process

BI-PDFRDR-02026: The top and bottom margins are too big or the page height is too small.

Cause: Incompatible values were provided for the top and bottom margins and page width.

Action: Change the margin size or page width.
Level: 1

Type: ERROR

Impact: Process

BI-PDFRDR-02027: A single column width is not greater than (pixels): {0}

Cause: A single column width was not greater than the specified width, as required.

Action: "Increase the column width.
Level: 1

Type: ERROR

Impact: Process

BI-PDFRDR-02028: The total width of the row headers when added is not smaller that the page width minus the right and left margins.

Cause: The supplied row headers were too wide for the page size.

Action: Change the width of the row headers.
Level: 1

Type: ERROR

Impact: Process

BI-PDFRDR-02029: A single column plus the total width of the row headers when added is not smaller than the page width minus the left and right margins.

Cause: >The supplied row headers were too wide for the page size.

Action: Change the width of row headers.
Level: 1

Type: ERROR

Impact: Process

BI-PDFRDR-02030: The graph height is not smaller than the page height minus the top and bottom margins, as required.

Cause: The supplied graph height was too large for the page.

Action: Reset the height and width values.
Level: 1

Type: ERROR

Impact: Process

BI-PDFRDR-02031: The graph width is not smaller than the page width minus the left and right margins, as required.

Cause: The graph width must be smaller than the page width minus the left and right margins.

Action: Reset the height and width values.
Level: 1

Type: ERROR

Impact: Process

BI-PDFRDR-02032: The graph height is not greater than one pixel, as required.

Cause: A graph height was provided that was not greater than one pixel.

Action: Change the graph height and make it bigger than one pixel.
Level: 1

Type: ERROR

Impact: Process

BI-PDFRDR-02033: The graph width is not greater than one pixel, as required.

Cause: A graph width was provided that was less than or equal to one pixel.

Action: Change the graph width and make it bigger than one pixel.
Level: 1

Type: ERROR

Impact: Process

BI-PDFRDR-02034: unable to validate page, margin, or column sizes

Cause: Invalid values for page, margin or column sizes.

Action: Provide a valid page, margin or column sizes
Level: 1

Type: ERROR

Impact: Process

BI-PDFRDR-02035: The PDF generator is unable to generate a section start or end.

Cause: The PDF generator was unable to generate a section start or end.

Action: See the Discoverer log for details.
Level: 1

Type: ERROR

Impact: Process

BI-PDFRDR-02036: The PDF generator is unable to generate the header or footer.

Cause: The PDF generator was unable to generate the header or footer.

Action: See the Discoverer log for details.
Level: 1

Type: ERROR

Impact: Process

BI-PDFRDR-02037: The PDF generator is unable to generate the title or text area.

Cause: The PDF generator was unable to generate the title or text area.

Action: See the Discoverer log for details.
Level: 1

Type: ERROR

Impact: Process

BI-PDFRDR-02038: The PDF generator is unable to generate the page items area.

Cause: The PDF generator was unable to generate the page items area.

Action: See the Discoverer log for details.
Level: 1

Type: ERROR

Impact: Process

BI-PDFRDR-02039: The PDF generator is unable to generate all combinations of page items.

Cause: The PDF generator was unable to generate all combinations of page items.

Action: See the Discoverer log for details.
Level: 1

Type: ERROR

Impact: Process

BI-PDFRDR-02040: unable to determine if the grid contains page items

Cause: The PDF generator was unable to determine if the grid contains page items.

Action: See the Discoverer log for details.
Level: 1

Type: ERROR

Impact: Process

BI-PDFRDR-02041: unable to determine if the graph contains page items

Cause: The PDF generatore was unable to determine if the graph contains page items.

Action: Check if the graph contains page items.
Level: 1

Type: ERROR

Impact: Process

BI-PDFRDR-02042: The grid type is not one of the following: a ThinTable, a Table, a ThinCrosstab, or a Crosstab, as required.

Cause: The grid type must be one of the following: a ThinTable, a Table, a ThinCrosstab, or a Crosstab.

Action: Check the grid type.
Level: 1

Type: ERROR

Impact: Process

BI-PDFRDR-02043: The units type is not inches, centimeters, or points, as required.

Cause: An invalid type was provide for the units value.

Action: Change the units type to INCHES, CENTIMETER, or POINTS.
Level: 1

Type: ERROR

Impact: Process

BI-PDFRDR-02044: The visible only option is only supported for thin crosstabs and tables.

Cause: The visible only option was specified for an unsupported use.

Action: Change the visible option data.
Level: 1

Type: ERROR

Impact: Process

BI-PDFRDR-02045: unable to complete the query to fetch data related to a page item combination

Cause: The query to fetch data related to a page item combination did not complete successfully.

Action: See the Discoverer log for details.
Level: 1

Type: ERROR

Impact: Process

BI-PDFRDR-02046: The page width and height are not greater than 0.

Cause: The page width and height must be greater than 0.

Action: Change the page width value and the page height value.
Level: 1

Type: ERROR

Impact: Process

BI-PDFRDR-02047: The PDF generator cannot support the specified data access instance.

Cause: A data access instance was specified that the PDF generator could not support. The PDF generator supports only data access instances that implement the DataAccess2 interface.

Action: See the Discoverer log for details.
Level: 1

Type: ERROR

Impact: Process

17 BI-PLUS-00001 to BI-PLUS-00050

BI-PLUS-00001: Could not set the selected LookAndFeel: {0}

Cause: The selected LookAndFeel was not set.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-PLUS-00002: The crosstab cannot be sorted because it does not contain any items.

Cause: The crosstab did not contain any items.

Action: Add items to the crosstab.
Level: 1

Type: ERROR

Impact: Process

BI-PLUS-00003: The crosstab cannot be sorted because it currently contains no data.

Cause: The crosstab did not contain any data.

Action: Add data to the crosstab.
Level: 1

Type: ERROR

Impact: Process

BI-PLUS-00004: The condition cannot be applied because it is unrelated to the items in the current sheet.

Cause: The specified condition was unrelated to the items in the sheet.

Action: Select a condition that applies to the items in the sheet.
Level: 1

Type: ERROR

Impact: Process

BI-PLUS-00005: The formula of this condition is invalid.

Cause: There was a syntax error in the formula for this condition.

Action: Check the syntax of the formula for this condition.
Level: 1

Type: ERROR

Impact: Process

BI-PLUS-00006: Error in condition name.

Cause: The user supplied an invalid condition name.

Action: Use only alphabetic characters for the condition name.
Level: 1

Type: ERROR

Impact: Process

BI-PLUS-00007: Another condition with that name already exists. Please type a different name.

Cause: The user supplied an invalid condition name.

Action: Enter a different condition name.
Level: 1

Type: ERROR

Impact: Process

BI-PLUS-00008: This condition cannot be viewed or edited in this version of Discoverer Plus because it contains a subquery. You may still activate and deactivate the condition.

Cause: An attempt was made to view or edit a condition that contained a subquery, but the version of Oracle Business Intelligence Discover Plus was unable to handle the subquery.

Action: Check the log file for details.
Level: 1

Type: ERROR

Impact: Process

BI-PLUS-00009: One of the function arguments has an incorrect datatype: {0}

Cause: An incorrect data type was found in a function argument.

Action: Ensure that all data types in the function arguments are correct.
Level: 1

Type: ERROR

Impact: Process

BI-PLUS-00010: You cannot create a condition because there are no items or calculations in this worksheet.

Cause: The worksheet did not contain any items or calculations.

Action: Add some items or calculations to this worksheet.
Level: 1

Type: ERROR

Impact: Process

BI-PLUS-00011: No matching close quote found in string.

Cause: The string had an opening quotation mark but no closing quotation mark.

Action: Supply the missing closing quotation mark in the condition.
Level: 1

Type: ERROR

Impact: Process

BI-PLUS-00012: Invalid quote in string.

Cause: The string contained an invalid quotation mark.

Action: Supply the proper quotation mark for the condition.
Level: 1

Type: ERROR

Impact: Process

BI-PLUS-00013: Badly placed quote in string.

Cause: The string contained a misplaced quotation mark.

Action: Ensure that quotation marks are correctly placed in the condition.
Level: 1

Type: ERROR

Impact: Process

BI-PLUS-00014: {0} cannot be included in the worksheet because the database that you are connected to does not support these kinds of advanced conditions.

Cause: The database to which the user was connected could not support the advanced condition.

Action: Check the log file for details.
Level: 1

Type: ERROR

Impact: Process

BI-PLUS-00015: The calculation cannot be displayed because it is unrelated to the items in the current sheet.

Cause: The calculation was unrelated to the items in the worksheet.

Action: Use a calculation that is related to items in the current sheet.
Level: 1

Type: ERROR

Impact: Process

BI-PLUS-00016: Cannot combine a detail data point with an aggregate data point.

Cause: A calculation syntax error occurred.

Action: Use a detail data point only with other detail data points in a calculation.
Level: 1

Type: ERROR

Impact: Process

BI-PLUS-00017: Error in formula.

Cause: A calculation syntax error occurred.

Action: Check the formula.
Level: 1

Type: ERROR

Impact: Process

BI-PLUS-00018: Error in calculation name.

Cause: The user supplied an invalid calculation name.

Action: Use only alphabetic characters for the calculation name.
Level: 1

Type: ERROR

Impact: Process

BI-PLUS-00019: Another Calculation or Percentage with that name already exists. Please type a different name.

Cause: A calculation name conflict occurred.

Action: Use another name for this calculation.
Level: 1

Type: ERROR

Impact: Process

BI-PLUS-00020: {0} cannot be included in the worksheet because the database that you are connected to does not support these kinds of advanced calculations.

Cause: The database to which the user was connected could not support the advanced calculations.

Action: Check the log file for details.
Level: 1

Type: ERROR

Impact: Process

BI-PLUS-00021: The query failed. Do you want to restore the previous data in your sheet? - Click Yes to undo your changes. - Click No to continue, but your sheet will be empty.

Cause: Query failed.

Action: Check the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-PLUS-00022: Could not obtain list of drill items from server.

Cause: Could not obtain list of drill items from server.

Action: Check the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-PLUS-00023: Invalid default value: {0}

Cause: An invalid default value was specified for the parameter.

Action: Choose a default value for this parameter from the list of values.
Level: 1

Type: ERROR

Impact: Process

BI-PLUS-00024: A parameter named \"{0}\" already exists. Please type in a different name.

Cause: A parameter name conflict occurred.

Action: Enter another name for this parameter.
Level: 1

Type: ERROR

Impact: Process

BI-PLUS-00025: Export Failed.

Cause: The attempted export operation failed.

Action: Check the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-PLUS-00026: An error occurred writing to the export file. Check adequate space is available.

Cause: The attempted export operation failed due to insufficient disk space.

Action: Ensure that adequate disk space is available and try again.
Level: 1

Type: ERROR

Impact: Process

BI-PLUS-00027: You cannot export the graph because it does not contain any data.

Cause: The export operation failed because the graph did not contain any data.

Action: Add some data to the graph.
Level: 1

Type: ERROR

Impact: Process

BI-PLUS-00028: Connection Error

Cause: The connection failed.

Action: Check the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-PLUS-00029: {0} The graph for the worksheet cannot be printed.

Cause: A graph printing error occurred.

Action: Check the log file for details.
Level: 1

Type: ERROR

Impact: Process

BI-PLUS-00030: {0} The graph for worksheet {1} cannot be printed.

Cause: A graph printing error occurred.

Action: Check the log file for details.
Level: 1

Type: ERROR

Impact: Process

BI-PLUS-00031: The graph for the worksheet cannot be printed.

Cause: A graph printing error occurred.

Action: Check the log file for details.
Level: 1

Type: ERROR

Impact: Process

BI-PLUS-00032: The graph for worksheet {0} cannot be printed.

Cause: A graph printing error occurred.

Action: Check the log file for details.
Level: 1

Type: ERROR

Impact: Process

BI-PLUS-00033: Printing Failed.

Cause: A printing error occurred.

Action: Check the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-PLUS-00034: At least one view must be printed.

Cause: No view was chosen to be printed.

Action: Print at least one view.
Level: 1

Type: ERROR

Impact: Process

BI-PLUS-00035: The title of the worksheet could not be printed with the graph.

Cause: An attempt was made to print the graph and title together.

Action: Print the graph without the title.
Level: 1

Type: ERROR

Impact: Process

BI-PLUS-00036: The title of worksheet {0} could not be printed with the graph.

Cause: An attempt was made to print the graph and title together.

Action: Print the graph without the title.
Level: 1

Type: ERROR

Impact: Process

BI-PLUS-00037: The title of the {0} worksheet is too long to fit on the printed page. The title will therefore be truncated.

Cause: The worksheet title was too long to print.

Action: The title will be printed in truncated form. No action is needed.
Level: 1

Type: ERROR

Impact: Process

BI-PLUS-00038: The text area of the {0} worksheet is too long to fit on the printed page. The text area will therefore be truncated.

Cause: The worksheet text area is too long to print.

Action: The text area will be printed in truncated form. No action is needed.
Level: 1

Type: ERROR

Impact: Process

BI-PLUS-00039: You cannot print the graph because it does not contain any data.

Cause: A printing error occurred because the graph did not contain any data.

Action: Add some data to the graph to be printed.
Level: 1

Type: ERROR

Impact: Process

BI-PLUS-00040: The worksheet cannot be printed because the margins are too large.

Cause: A printing error occurred because the worksheet margins were too large.

Action: Reduce the margins in the worksheet.
Level: 1

Type: ERROR

Impact: Process

BI-PLUS-00041: Select at least {0} or graph for export.

Cause: The export operation failed because nothing was selected for export.

Action: Select an object to be exported.
Level: 1

Type: ERROR

Impact: Process

BI-PLUS-00042: The exported graph may not be identical to the graph seen in Discoverer. There was an error in setting the graph properties

Cause: Export failed. Graph properties could not be set.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-PLUS-00043: Export incomplete. The user chose not to overwrite an existing file

Cause: The user chose not to overwrite an existing file.

Action: Export the file that was not exported.
Level: 1

Type: ERROR

Impact: Process

BI-PLUS-00044: The current operation was canceled at the users request

Cause: The export operation failed.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-PLUS-00045: Graph cannot be exported because the worksheet has no rows

Cause: The export operation failed because the worksheet has no rows.

Action: Ensure that rows exist in the worksheet that is to be exported.
Level: 1

Type: ERROR

Impact: Process

BI-PLUS-00046: Only positive data values are plotted on the graph. This graph type does not support data values that are negative, null, or zero.

Cause: The data values provided for the graph contained negative, null or zero

Action: Use only positive values for plotting the graph.
Level: 1

Type: ERROR

Impact: Process

BI-PLUS-00047: A graph cannot be plotted because all of the data values are negative, null, or zero.

Cause: The data values provided for the graph were negative, null, or zero.

Action: Provide positive values for plotting the graph.
Level: 1

Type: ERROR

Impact: Process

BI-PLUS-00048: Scheduling Error

Cause: Scheduling did not occur.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-PLUS-00049: Find operation failed

Cause: The Find operation failed.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

BI-PLUS-00050: An error occured while executing the Find operation.

Cause: The Find operation failed.

Action: See the log for details.
Level: 1

Type: ERROR

Impact: Process

18 BI-POPVD-00001 to BI-POPVD-00053

BI-POPVD-00001: No worksheet is selected. Select a worksheet

Cause: No worksheet was selected.

Action: Select a worksheet.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00002: An error occurs while externalizing the model state.

Cause: An error occurred while externalizing the model state.

Action: Contact the Oracle Business Intelligence Discoverer administrator.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00003: An error occurs while reconstituting the model state.

Cause: An error occurred while reconstituting the model state.

Action: Contact the Oracle Business Intelligence Discoverer administrator.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00004: An error occurs while handling the request in the controller.

Cause: An error occurred while handling the request in the controller.

Action: Contact the Oracle Business Intelligence Discoverer administrator.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00005: The selected crosstab has data points on the page axis. This layout is not supported by the Discoverer Gauges portlet.

Cause: A crosstab was selected that had data points on the page axis. This layout is not supported by the Discoverer Gauges portlet.

Action: Please choose a different crosstab for Discoverer to display gauges portlet.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00006: There is no measure data source selected. Select row items and column items.

Cause: No measure data source was selected.

Action: Select row items and column items.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00007: There are no workbooks selected for building the List of Worksheets.

Cause: No workbooks were selected for building the List of Worksheets.

Action: Select workbooks.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00008: There are no worksheets selected for building the List of Worksheets.

Cause: No worksheets were selected for building the List of Worksheets.

Action: Select worksheets.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00009: Only the owner of this portlet can edit the defaults.

Cause: The portlet owner can only edit the defaults.

Action: Log in as the owner to edit this portlet.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00010: An error occurs while handling the BIBean event.

Cause: An error occurred while handling the BIBean event.

Action: Contact the Oracle Business Intelligence Discoverer administrator.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00011: An error occurs while parsing the event.

Cause: An error occurred while parsing the event.

Action: Contact the Oracle Business Intelligence Discoverer administrator.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00012: An error occurs while initializing the graph renderer.

Cause: An error occurred while initializing the graph renderer.

Action: Contact the Oracle Business Intelligence Discoverer administrator.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00013: The graph renderer is already initialized.

Cause: The graph renderer was already initialized.

Action: Contact the Oracle Business Intelligence Discoverer administrator.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00014: The graph renderer is not initialized.

Cause: The graph renderer was not initialized.

Action: Contact the Oracle Business Intelligence Discoverer administrator.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00015: An error occurs while rendering the graph.

Cause: An error occurred while rendering the graph.

Action: Contact the Oracle Business Intelligence Discoverer administrator.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00016: The length of one or more parameter values exceeds the defined limit of 3000 characters

Cause: The length of one or more parameter values exceeded the defined limit of 3000 characters

Action: Shorten the parameter values to less than 3000 characters.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00017: The session pool is at maximum capacity.

Cause: The session pool was at maximum capacity.

Action: Contact the Oracle Business Intelligence Discoverer administrator.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00018: unsupported presentation type for view

Cause: Unsupported presentation type for view.

Action: Contact the Oracle Business Intelligence Discoverer administrator.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00019: unsupported presentation type for graph

Cause: Unsupported presentation type for graph.

Action: Contact the Oracle Business Intelligence Discoverer administrator.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00020: An error occurs while reading the cached portlet content for the view.

Cause: An error occurred while reading the cached portlet content for the view.

Action: Contact the Oracle Business Intelligence Discoverer administrator.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00021: An error occurs while reading the cached portlet content for the graph.

Cause: An error occurred while reading the cached portlet content for the graph.

Action: Contact the Oracle Business Intelligence Discoverer administrator.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00022: An error occurs while reading the cached result.

Cause: An error occurred while reading the cached result.

Action: Contact the Oracle Business Intelligence Discoverer administrator.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00023: The selected worksheet is not a valid crosstab worksheet for Discoverer Gauges portlet.

Cause: Not a valid crosstab worksheet selected for Discoverer Gauges portlet.

Action: Choose a valid crosstab worksheet.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00024: This portlet is refreshing.

Cause: An attempt was made to access a portlet while its data was being refreshed

Action: Wait till the portlet refreshes.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00025: An error occurs while refreshing this portlet.

Cause: An error occurred while refreshing this portlet.

Action: Contact the Oracle Business Intelligence Discoverer administrator.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00026: An error occurs while setting the refresh options for this portlet.

Cause: An error occurred while setting the refresh options for this portlet.

Action: Contact the Oracle Business Intelligence Discoverer administrator.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00027: An error occurs while reading the refresh options for this portlet.

Cause: An error occurred while reading the refresh options for this portlet.

Action: Contact the Oracle Business Intelligence Discoverer administrator.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00028: An error occurs while trying to detect the last refresh date for this portlet.

Cause: An error occurred while trying to detect the last refresh date for this portlet.

Action: Contact the Oracle Business Intelligence Discoverer administrator.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00029: An error occurs while trying to ensure persistence of the portlet defaults.

Cause: An error occurred while trying to ensure persistence of the portlet defaults.

Action: Contact the Oracle Business Intelligence Discoverer administrator.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00030: An error occurs while trying to ensure persistence of the portlet customization.

Cause: An error occurred while trying to ensure persistence of the portlet customization.

Action: Contact the Oracle Business Intelligence Discoverer administrator.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00031: An error occurs while trying to read the refresh options from the state string.

Cause: An error occurred while trying to read the refresh options from the state string.

Action: Contact the Oracle Business Intelligence Discoverer administrator.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00032: An error occurs while trying to parse the refresh date and time.

Cause: An error occurred while trying to parse the refresh date and time.

Action: Contact the Oracle Business Intelligence Discoverer administrator.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00033: The default cached result is null.

Cause: An error occurred while refreshing this portlet.

Action: Contact the Oracle Business Intelligence Discoverer administrator.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00034: An error occurs while attempting to update the portlet cache from the Single Worksheet Viewer.

Cause: An error occurred while attempting to update the portlet cache from the Single Worksheet Viewer.

Action: Contact the Oracle Business Intelligence Discoverer administrator.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00035: An error occurs while trying to determine if the user cache was updated.

Cause: An error occurred while trying to determine if the user cache was updated.

Action: Contact the Oracle Business Intelligence Discoverer administrator.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00036: An error occurs while trying to determine if the default cache was updated.

Cause: An error occurred while trying to determine if the default cache was updated.

Action: Contact the Oracle Business Intelligence Discoverer administrator.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00037: Connection to portlet is not available to unauthenticated users.

Cause: A user connection for unauthenticated users was requested for a Portlet that is not displayed to unauthenticated users.

Action: Log in as an authenticated user.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00038: The user connection is null for displaying the List of Worksheets.

Cause: The user connection was null to display the List of Worksheets.

Action: Contact the Oracle Business Intelligence Discoverer administrator.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00039: The publisher connection is null for displaying the List of Worksheets.

Cause: The publisher connection was null to display the List of Worksheets.

Action: Contact the Oracle Business Intelligence Discoverer administrator.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00040: An error occurs while retrieving the view information.

Cause: An error occurred while retrieving the view information.

Action: Contact the Oracle Business Intelligence Discoverer administrator.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00041: The last scheduled refresh failed.

Cause: The last scheduled refresh failed.

Action: Click for details.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00042: Refresh Fails.

Cause: An attempt to refresh the data in the portlet failed.

Action: Contact the Oracle Business Intelligence Discoverer administrator.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00043: The publisher's Connection list is empty.

Cause: The publisher's Connection list was empty.

Action: Create one or more publisher's connections.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00044: No connections are available for the current user to view this portlet. Contact the publisher of this Portal page or the Oracle Business Intelligence Discoverer administrator.

Cause: No connections were available for the user to view this portlet.

Action: Contact the publisher of this Portal page or the Oracle Business Intelligence Discoverer administrator.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00045: The publisher's connection is not found in the list of available connections. Select a connection from the list.

Cause: The publisher's connection was not found in the list of available connections.

Action: Select a connection from the list.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00046: The connection selected for logged in users is not found in the list of available connections. Select a connection from the list.

Cause: The connection selected for logged in users was not found in the list of available connections.

Action: Select a connection from the list.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00047: The connection selected for not logged in users is not found in the list of available connections.

Cause: The connection selected for not logged in users was not found in the list of available connections.

Action: Select a connection from the list.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00048: An error occurs while trying to get a list of worksheets.

Cause: An error occurred while trying to get a list of worksheets.

Action: Contact the Oracle Business Intelligence Discoverer administrator.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00049: An error occurs while trying to get portlet data limits.

Cause: An error occurred while trying to get portlet data limits.

Action: Contact the Oracle Business Intelligence Discoverer administrator.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00050: An error occurs while trying to create a cached bean from a live bean.

Cause: An error occurred while trying to create a cached bean from a live bean.

Action: Contact the Oracle Business Intelligence Discoverer administrator.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00051: {0} must be a number

Cause: Not a valid number

Action: Enter valid number.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00052: not enough memory, gauge set size too big

Cause: gauge set size was too big.

Action: Enter appropriate gauges size.
Level: 1

Type: ERROR

Impact: Process

BI-POPVD-00053: The gauge data point is not found.

Cause: The gauge data point was not found.

Action: Select a different data point.
Level: 1

Type: ERROR

Impact: Process

19 BI-SVR-00300 to BI-SVR-03964

BI-SVR-00300: Error in formula.

Cause: The formula entered does not follow the SQL expression syntax.

Action: Re-enter the formula following SQL syntax conventions. See the Oracle SQL Language Reference Manual for a description.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-00709: Inconsistent datatypes in condition.

Cause: The data types of items used in this condition are mismatched.

Action: Check the formula to correct the error or change the data type of the items by using TO_CHAR, TO_DATE or TO_NUMBER functions.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-00720: Invalid join configuration - includes a master with two separately joined detail folders.

Cause: An attempt was made to join a master folder with two detail folders at the same time. The resulting Cartesian product would give potentially confusing or incorrect results from the database. This combination of joins is not allowed within Oracle Business Intelligence Discoverer.

Action: Construct the join so that the folder specified as the master actually contains the master key and the folders specified as detail actually contain the detail keys. If the join configuration includes a master with two separately joined detail folders then create a complex folder to hide one of the joins. This is normally only the case where the relationship between the folders is one-to-one, and there is no actual master folder.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-01251: Failed to create summaries - automated summary management is not available

Cause: The summary creation failed, because automatic summary management was not available.

Action: Contact the system administrator for further details.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03141: You do not have access to any End User Layer tables

Cause: The user did not have privileges to access any of the End User Layers.

Action: Create an End User Layer for the user or grant access to at least one End User Layer using Oracle Business Intelligence Discoverer Administrator.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03142: You do not have access to any Business Areas

Cause: The user did not have privileges to access any of the Business Areas.

Action: Create a business area for the user or grant access to a business area using Oracle Business Intelligence Discoverer Administrator.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03146: Insufficient privilege to run Discoverer Administrator

Cause: A user with sufficient privileges tried to access Oracle Business Intelligence Discoverer Administrator.

Action: Grant sufficient privileges to the user to access Oracle Business Intelligence Discoverer Administrator.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03150: This item is used in a filter or a hierarchy and cannot be hidden

Cause: The user attempted to hide an item used in a filter or hierarchy.

Action: Remove the item from the hierarchy or filter where it is used. Then try hiding it.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03199: %1!s %2!s referenced in the export was not found in this End User Layer

Cause: An attempt was made to export items not found in the End User Layer.

Action: Export only items that are found in the End User Layer.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03200: %1!s %2!s was not loaded because of a missing dependency

Cause: An attempt was made to export items not found in the End User Layer.

Action: Export only items that are found in the End User Layer.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03206: Failed to connect to database

Cause: An attempt was made to connect to the database with an invalid username and password or with an incorrect connect string.

Action: Ensure that the username and password and the connect string are correct.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03207: Internal EUL Error: InvalidId - Failed to find EUL element by id

Cause: No element exists in EUL for the given element Id

Action: TBD
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03208: Internal EUL Error: ExprParseNodeType - Invalid type in canonical formula

Cause: Invalid argument in the expression

Action: Correct the expression with valid arguments.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03209: Internal EUL Error: ExprParseBracketErr - No bracket found in canonical formula

Cause: Missing bracket in expression

Action: Check expression has proper brackets.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03210: Invalid formula

Cause: An invalid expression was entered.

Action: Enter a valid expression.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03211: Invalid number of arguments

Cause: The expression contained an invalid number of arguments.

Action: Enter a valid number of arguments in the expression.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03212: Invalid operator in formula

Cause: The expression contained an invalid operator.

Action: Remove the invalid operator from the expression.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03213: Internal EUL Error: TransError - Unexpected transaction error

Cause: The EUL transaction failed to execute

Action: TBD
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03220: Internal EUL Error: UniqueKeyViolation - internal id is used by another EUL element

Cause: An internal error has occurred in Oracle Business Intelligence Discoverer. User might be able to continue working, but the current operation may not have been performed correctly.

Action: Report the actions that immediately preceded this error to Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03221: Internal EUL Error: ObjectNotFound - Can't find EUL element

Cause: An internal error has occurred in Oracle Business Intelligence Discoverer. User might be able to continue working, but the current operation may not have been performed correctly.

Action: Report the actions that immediately preceded this error to Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03222: Internal EUL Error: PrivilegeNotFound - No privilege record found for this user

Cause: An internal error has occurred in Oracle Business Intelligence Discoverer. User might be able to continue working, but the current operation may not have been performed correctly.

Action: Report the actions that immediately preceded this error to Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03223: No joins found where required

Cause: An operation was attempted where a join is required to another folder, and no join was found.

Action: Determine which joins are required to support the operation and enter the joins first.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03224: Invalid join configuration - includes a master with two separately joined detail folders

Cause: An attempt was made to join a master folder with two detail folders at the same time. The resulting Cartesian product would give potentially confusing or incorrect results from the database. This combination of joins is not allowed within Oracle Business Intelligence Discoverer.

Action: Construct the join so that the folder specified as the master actually contains the master key and the folders specified as detail actually contain the detail keys. If the join configuration includes a master with two separately joined detail folders then create a complex folder to hide one of the joins. This is normally only the case where the relationship between the folders is one-to-one, and there is no actual master folder.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03228: Internal EUL Error: NoTransaction - there is no current transaction

Cause: An internal error has occurred in Oracle Business Intelligence Discoverer. User might be able to continue working, but the current operation may not have been performed correctly.

Action: Report the actions that immediately preceded this error to Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03229: Internal EUL Error: DataError = Invalid function type

Cause: An internal error has occurred in Oracle Business Intelligence Discoverer. User might be able to continue working, but the current operation may not have been performed correctly.

Action: Report the actions that immediately preceded this error to Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03234: Internal EUL Error: DrillFromItemNotInQR - Item drilled on is not in the Query Request

Cause: An internal error has occurred in Oracle Business Intelligence Discoverer. User might be able to continue working, but the current operation may not have been performed correctly.

Action: Report the actions that immediately preceded this error to Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03235: Internal EUL Error: InvalidDrillOption - Invalid drill option requested

Cause: An internal error has occurred in Oracle Business Intelligence Discoverer. User might be able to continue working, but the current operation may not have been performed correctly.

Action: Report the actions that immediately preceded this error to Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03237: Internal EUL Error: InvalidItem - Item is not valid in this context

Cause: An internal error has occurred in Oracle Business Intelligence Discoverer. User might be able to continue working, but the current operation may not have been performed correctly.

Action: Report the actions that immediately preceded this error to Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03238: Internal EUL Error: InvalidString - String or string length is not valid

Cause: An internal error has occurred in Oracle Business Intelligence Discoverer. User might be able to continue working, but the current operation may not have been performed correctly.

Action: Report the actions that immediately preceded this error to Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03239: Internal EUL Error: InvalidStringLength - String length is not valid

Cause: An internal error has occurred in Oracle Business Intelligence Discoverer. User might be able to continue working, but the current operation may not have been performed correctly.

Action: Report the actions that immediately preceded this error to Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03240: Internal EUL Error: InvalidRollupOnQR - Rollup item is not in the Query Request

Cause: An internal error has occurred in Oracle Business Intelligence Discoverer. User might be able to continue working, but the current operation may not have been performed correctly.

Action: Report the actions that immediately preceded this error to Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03241: Internal EUL Error: RollupValueMismatch - filter does not contain rollup value

Cause: An internal error has occurred in Oracle Business Intelligence Discoverer. User might be able to continue working, but the current operation may not have been performed correctly.

Action: Report the actions that immediately preceded this error to Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03242: Internal EUL Error: TokenStreamError - Error tokenising input stream

Cause: An internal error has occurred in Oracle Business Intelligence Discoverer. User might be able to continue working, but the current operation may not have been performed correctly.

Action: Report the actions that immediately preceded this error to Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03243: Error in formula - uncategorized error

Cause: An unspecified error was found in the formula.

Action: Check the formula and correct the error. See the Oracle SQL Language Reference Manual for formula syntax conventions.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03244: Error in formula - unexpected end of formula

Cause: The formula ends unexpectedly.

Action: The formula was unfinished, possibly ending in an operator or function name.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03245: Error in formula - unrecognized item name or missing quotes around value

Cause: The formula contains some text that was not recognized as an item name.

Action: Change the item name to a valid item name and retry.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03246: Error in formula - ambiguous or duplicate item names

Cause: The supplied formula contains unqualified item names that appeared in multiple folders.

Action: Qualify item names with the folder name (for example, Employee.Name).
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03256: Internal EUL Error: InvalidSummaryTableDef - The specified server table is invalid

Cause: An internal error has occurred in Oracle Business Intelligence Discoverer. User might be able to continue working, but the current operation may not have been performed correctly.

Action: Report the actions that immediately preceded this error to Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03257: Internal EUL Error: InvalidRefreshSetType - Invalid summary refresh set type

Cause: An internal error has occurred in Oracle Business Intelligence Discoverer. User might be able to continue working, but the current operation may not have been performed correctly.

Action: Report the actions that immediately preceded this error to Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03258: Internal EUL Error: ItemNotInServerObject - Column specified does not exist

Cause: An internal error has occurred in Oracle Business Intelligence Discoverer. User might be able to continue working, but the current operation may not have been performed correctly.

Action: Report the actions that immediately preceded this error to Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03266: Internal EUL Error: Failed to get summary status from the server

Cause: An internal error has occurred in Oracle Business Intelligence Discoverer. User might be able to continue working, but the current operation may not have been performed correctly.

Action: Report the actions that immediately preceded this error to Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03267: Error in Formula - unknown function name

Cause: The formula contains a function that is not registered in the End User Layer.

Action: Edit the formula correct function name and retry.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03268: Error in formula - mismatched ( ) 's

Cause: Mismatched parentheses were found in the formula.

Action: Check the formula to determine if the function name is wrong and if so, correct it. If the function named in the formula is the correct function, then choose Register PL/SQL Function in the Tools menu to register the function in the End User Layer. Retry the formula with the registered function name.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03269: Error in formula - Nested aggregate functions are not allowed

Cause: The formula contained unsupported content. Oracle Business Intelligence Discoverer does not directly support the use of nested aggregates, such as AVG(SUM(SAL)).

Action: Remove the nested aggregate.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03271: Error in formula - item is not in scope of the folders available for this formula

Cause: The formula contained an item that was not in the folders that this formula can reference.

Action: Correct the item name and retry.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03272: Error in formula - circular recursive expression detected

Cause: The formula contained a reference to an item whose formula references this formula.

Action: Modify the formula to remove the circular reference and retry.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03273: Internal EUL Error: InvalidConstructOpt - Invalid handle constructor option

Cause: An internal error has occurred in Oracle Business Intelligence Discoverer. User might be able to continue working, but the current operation may not have been performed correctly.

Action: Report the actions that immediately preceded this error to Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03280: Internal EUL Error: MapInsertFailed - insert failed in PrivateAddObjectToMap

Cause: An internal error has occurred in Oracle Business Intelligence Discoverer. User might be able to continue working, but the current operation might not have been performed correctly.

Action: Report the actions that immediately preceded this error to Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03281: Internal EUL Error: ExportIdAlreadyExists - Object has already reserved this id

Cause: An internal error has occurred in Oracle Business Intelligence Discoverer. User might be able to continue working, but the current operation may not have been performed correctly.

Action: Report the actions that immediately preceded this error to Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03282: Internal EUL Error: ExportInvalidCType

Cause: An internal error has occurred in Oracle Business Intelligence Discoverer. User might be able to continue working, but the current operation might not have been performed correctly.

Action: Report the actions that immediately preceded this error to Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03283: Error in End User Layer import file - ParseError

Cause: The End User Layer import file was corrupted or was not a valid import file.

Action: Export the business area into an new file and import it again. Retry the operation that failed.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03284: Error in End User Layer import file - NoTypeFound

Cause: The End User Layer import file was corrupted or was not a valid import file.

Action: Export the business area into an new file and import it again. Retry the operation that failed.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03285: Invalid End User Layer import file

Cause: The End User Layer import file was corrupted or was not a valid import file.

Action: Export the End User Layer into an new file and import it again.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03286: Error in End User Layer import file - InvalidClass

Cause: The End User Layer import file was corrupted or was not a valid import file.

Action: Export the business area into an new file and import it again. Retry the operation that failed.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03291: Internal EUL Error: InvalidDQ4Query - error importing DQ4 query

Cause: An internal error has occurred in Oracle Business Intelligence Discoverer. User might be able to continue working, but the current operation might not have been performed correctly.

Action: Report the actions that immediately preceded this error to Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03295: Internal EUL Error: HierarchyNodeNotConnected - this hierarchy node is not connected

Cause: An internal error has occurred in Oracle Business Intelligence Discoverer. User might be able to continue working, but the current operation may not have been performed correctly.

Action: Report the actions that immediately preceded this error to Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03296: Internal EUL Error: HierarchyNodeNotConnected.

Cause: An internal error has occurred in Oracle Business Intelligence Discoverer. User might be able to continue working, but the current operation may not have been performed correctly.

Action: Report the actions that immediately preceded this error to Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03297: Internal EUL Error: HierarchySegNotConnected.

Cause: An internal error has occurred in Oracle Business Intelligence Discoverer. User might be able to continue working, but the current operation may not have been performed correctly.

Action: Report the actions that immediately preceded this error to Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03298: Internal EUL Error: InvalidSegInHierarchy - Invalid segment found in hierarchy

Cause: An internal error has occurred in Oracle Business Intelligence Discoverer. User might be able to continue working, but the current operation may not have been performed correctly.

Action: Report the actions that immediately preceded this error to Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03299: Internal EUL Error: InvalidNode - Invalid Hierarchy Node

Cause: An internal error has occurred in Oracle Business Intelligence Discoverer. User might be able to continue working, but the current operation may not have been performed correctly.

Action: Report the actions that immediately preceded this error to Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03301: Internal EUL Error: ItemNotInNode - The item to be removed is not in this hierarchy node

Cause: An internal error has occurred in Oracle Business Intelligence Discoverer. User might be able to continue working, but the current operation may not have been performed correctly.

Action: Report the actions that immediately preceded this error to Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03305: Internal EUL Error: LXInitializationFailure - lxlinit failed to allocate memory

Cause: An internal error has occurred in Oracle Business Intelligence Discoverer. User might be able to continue working, but the current operation may not have been performed correctly.

Action: Report the actions that immediately preceded this error to Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03308: Internal EUL Error: NotSimpleFilter - complex element found in simple filter

Cause: An internal error has occurred in Oracle Business Intelligence Discoverer. User might be able to continue working, but the current operation may not have been performed correctly.

Action: Report the actions that immediately preceded this error to Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03309: Internal EUL Error: DestroyFailure - failed to destroy EUL element

Cause: An internal error has occurred in Oracle Business Intelligence Discoverer. User might be able to continue working, but the current operation may not have been performed correctly.

Action: Report the actions that immediately preceded this error to Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03311: Invalid date format

Cause: An invalid date or time format was entered.

Action: Reenter a date or time that complies with the date format MM/DD/YY and the time format HH:MM.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03314: Error found parsing SQL statement

Cause: An unspecified error was detected when parsing an SQL statement. The SQL statement might contain an error, or the type of SQL query might not be currently supported by the Oracle Business Intelligence Discoverer import parser.

Action: Check the SQL statement for errors. Correct the error and retry.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03315: This item is used in a hierarchy and cannot be hidden

Cause: An attempt was made to hide an item used in a filter or hierarchy.

Action: Remove the item from the hierarchy or filter where it is used. Then try hiding it.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03351: This user does not have sufficient privileges to create a procedure

Cause: An attempt was made to create or edit procedures in the server, but the user did not have the database privileges required.

Action: Ask your system administrator to grant you the CREATE PROCEDURE privilege using SQL*Plus.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03352: This user does not have sufficient privileges to create a view

Cause: An attempt was made to create or edit views in the server, but the user did not have the database privileges required.

Action: Ask the system administrator to grant user the CREATE VIEW privilege using SQL*Plus.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03353: This user does not have sufficient privileges to create a table

Cause: An attempt was made to create table in the server, but the user did not have the database privileges required.

Action: Ask your system administrator to grant you the CREATE TABLE privilege using SQL*Plus and ensure that the user has quota and privileges necessary.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03359: This user does not have sufficient privileges to insert into specified table

Cause: An attempt was made to insert into a table in the server, but the user did not have the database privileges required.

Action: Ask the system administrator to grant user the INSERT privilege on specified table using SQL*Plus and to ensure that the user has quota and privileges necessary.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03360: This user does not have sufficient privileges to delete from specified table

Cause: An attempt was made to delete from a specified table in the server, but the user did not have the database privileges required.

Action: Ask the system administrator to grant user the DELETE privilege on the specified table using SQL*Plus.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03361: This user does not have sufficient privileges to update specified table

Cause: An attempt was made to update a specified table in the server, but the user did not have the database privileges required.

Action: Ask the system administrator to grant the user UPDATE privilege on the specified table using SQL*Plus.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03362: This user does not have sufficient privileges to select from specified table

Cause: An attempt was made to select from a specified table in the server, but the user did not have the database privileges required.

Action: Ask the system administrator to grant the user the SELECT privilege on specified table using SQL*Plus.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03363: This operation will cause some summaries to be disabled

Cause: The user lacked the database privileges required to create or edit tables in the server.

Action: Ask the system administrator to grant the user the CREATE TABLE privilege using SQL*Plus and to ensure that the user has sufficient privileges create tables in a tablespace.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03373: Unsupported date arithmetic requested

Cause: An attempt was made to use DATE type items in a formula in an invalid combination.Typically this is caused by trying by add, subtract, multiply, or divide two dates.

Action: See the Oracle SQL Language Reference Manual for information about date arithmetic syntax.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03899: The custom SQL entered contains enhanced aggregation and is therefore invalid.

Cause: A custom SQL query was entered that contained enhanced aggregations such as GROUPING SETS.

Action: Remove the enhanced agggregation constructs from the custom SQL query.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03900: Internal EUL Error: Unable to generate query

Cause: An internal error has occurred in Oracle Business Intelligence Discoverer. User might be able to continue working, but the current operation may not have been performed correctly.

Action: Report the actions that immediately preceded this error to Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03901: Internal EUL Error: Unable to generate query

Cause: An internal error has occurred in Oracle Business Intelligence Discoverer. User might be able to continue working, but the current operation may not have been performed correctly.

Action: Report the actions that immediately preceded this error to Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03959: No joins found between component folders of complex folder with %1!s '%2!s'.

Cause: An attempt was made to connect database not supported by Discoverer.

Action: Try connecting to database, whose version is supported by Oracle Business Intelligence Discoverer.
Level: 1

Type: ERROR

Impact: Process

BI-SVR-03964: Connection to 8i Database not supported

Cause: An attempt was made to connect to a database that is not supported by Oracle Business Intelligence Oracle Business Intelligence Discoverer.

Action: Connect to a database whose version is supported by Oracle Business Intelligence Discoverer.
Level: 1

Type: ERROR

Impact: Process

20 BI-VIEWER-00001 to BI-VIEWER-01245

BI-VIEWER-00001: Empty input (or null input) is not allowed.

Cause: Empty input (or null input) is not allowed.

Action: Input a non-null value.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-00002: Length of supplied value is too long.

Cause: Supplied value length was too long.

Action: Shorten the length of the supplied value.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-00003: The following character is not valid: {0}

Cause: An invalid character was supplied.

Action: Enter a valid character.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-00004: The following character is required: {0}

Cause: Specified character is required.

Action: Enter data with the specified character.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-00005: Zero length and null strings are not allowed.

Cause: Zero length and null strings are not allowed.

Action: Enter nonzero length or non-null strings.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-00006: Negative values are not allowed.

Cause: Negative values were not allowed.

Action: Enter nonnegative values.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-00007: The numerical value entered is too low.

Cause: The numerical value entered was too low than allowed.

Action: Enter a higher value.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-00008: The numerical value entered is too high.

Cause: The numerical value entered was too high than allowed.

Action: Enter a lower value.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-00009: An error occurs while constructing cached Thin Bean for Portlet Provider.

Cause: An error occurred while constructing cached Thin Bean for Portlet Provider.

Action: Contact the Oracle Business Intelligence Discoverer administrator.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-00010: Oracle BI Discoverer is unable to read the configuration file. The following expression is invalid: {0}.

Cause: Oracle BI Discoverer was unable to read the configuration file. provided expression was invalid.

Action: Enter a valid expression.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-00011: Oracle BI Discoverer is unable to read the configuration file. A number could not be derived from the following expression: {0}.

Cause: Oracle BI Discoverer was unable to read the configuration file. A number could not be derived from the specified expression.

Action: Check the configuration file so that a number could be derived from the specified expression.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-00012: Oracle BI Discoverer is unable to read the configuration file. A value is required for the following expression: {0}.

Cause: Oracle BI Discoverer was unable to read the configuration file . Value provided for the specified expression might be wrong.

Action: Revise the configuration file to provide a value for the specified expression.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-00013: Oracle BI Discoverer is unable to read the configuration file. The configuration file must be local.

Cause: Oracle BI Discoverer was unable to read the configuration file. The configuration file must be local.

Action: Ensure that if the configuration file is local. If not, please make it local.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-00014: OracleAS Single Sign-On is not enabled for Oracle BI Discoverer. The customizations displayed here are default customizations, including the connection. To enable user customizations and the ability to save to Portal, enable OracleAS Single Sign-On for Oracle BI Discoverer.

Cause: OracleAS Single Sign-On was not enabled for Oracle BI Discoverer. The customizations displayed were default customizations, including the connection.

Action: To enable user customizations and the ability to save to Oracle Portal, enable OracleAS Single Sign-On for Oracle BI Discoverer.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-00015: Attempting to launch Viewer using a private connection with OracleAS Single Sign-On disabled Oracle BI Discoverer application. This is not supported.

Cause: An attempt was made to launch Viewer using a private connection with OracleAS Single Sign-On not enabled for Oracle BI Discoverer.

Action: Enable OracleAS Single Sign-On for Oracle BI Discoverer and retry.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-00016: No Default Connection details are found for this Viewer Request because OracleAS Single Sign-On is not enabled and this portlet is not displayed to unauthenticated users.

Cause: OracleAS Single Sign-On was not enabled and this portlet is not displayed to unauthenticated users.

Action: Enable OracleAS Single Sign-On for Discoverer and retry.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01001: A irrecoverable application error has occurred. Review the Oracle BI Discoverer application log file and consult with the Oracle Fusion Middleware administrator.

Cause: A irrecoverable application error has occurred.

Action: Review the Oracle BI Discoverer application log file and consult with the Oracle Fusion Middleware administrator.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01002: An error occurred while handling the event. See the application log for more details. {0}

Cause: An error occurred while handling the event.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01003: The event requested is not supported. {0}

Cause: The event requested is not supported.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01004: The application cannot find a method with the appropriate signature, invalid method or invalid return type: {0}.

Cause: The application could not find a method with the appropriate signature. The method or return type was invalid.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01005: The application cannot find the mapping requested: {0}.

Cause: The application could not find the mapping requested.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01006: The application cannot find the required event parameter.

Cause: The application could not find the required event parameter.

Action: Enter the event parameter again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01007: The application encounters an invalid state. {0}.

Cause: The application encountered an invalid state.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01008: The link contains an invalid state string.

Cause: The link contained an invalid state string.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01009: No state matches the state identifier provided. This can happen if user session timed out. Start the operation again.

Cause: The session might have timed out.

Action: Start the operation again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01010: The specified state identifier is invalid. This can happen if you have mistakenly tried to type parameters on the URL.

Cause: The user might have mistakenly tried to type parameters on the URL.

Action: Edit the URL. Check discoverer application guide for valid URL parameters.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01011: The configuration file was not found at the specified location or the location was invalid.

Cause: The configuration file was not found at the specified location or the location was invalid.

Action: Provide a valid location, check discoverer configuration guide for the configuration file location.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01012: illegal access error, check the Discoverer application log for more details.

Cause: An illegal access error occurred.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01013: Oracle BI Discoverer is unable to obtain a class instance. Check the Discoverer application log for more details.

Cause: Oracle BI Discoverer was unable to get a class instance.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01014: Oracle BI Discoverer is unable to find a required class. Check the Discoverer application log for more details.

Cause: Oracle BI Discoverer was unable to find a required class.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01015: Oracle BI Discoverer is unable to find a method with the required signature. Check the Discoverer application log for more details.

Cause: Oracle BI Discoverer was unable to find a method with the required signature.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01016: Empty input is not allowed.

Cause: Null value was not allowed for the specified input.

Action: Enter non empty value.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01017: The following character is not valid: {0}.

Cause: An invalid character was specified.

Action: Specify a valid character.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01018: The following character is required: {0}.

Cause: A required character was not specified.

Action: Enter the required character.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01019: Negative values are not allowed.

Cause: One or more negative values were specified.

Action: Enter only positive values.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01020: The numerical value entered is too low.

Cause: The numerical value entered was too low.

Action: Enter a higher value.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01021: illegal format for pair string

Cause: Format of the pair string was illegal.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01022: A state string key is missing. (There was an odd number of values in the state string.)

Cause: A state string key did not have an associated value. (There might be an odd number of values in the state string.)

Action: Provide an even number of values.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01023: The state string is missing a required key value pair: {0}.

Cause: The state string did not contain a required key value pair.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01024: unexpected error during state string decompression

Cause: An unexpected error occurred during state string decompression.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01025: The requested print options page does not exist.

Cause: The requested print options page does not exist.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01026: Start from the connections page to create or edit a connection. Try again.

Cause: An attempt was made to create or edit a connection.

Action: Try again, this time from the connections page.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01027: The remote user is different. Log out and reenter this application.

Cause: The remote user has changed.

Action: Log out and reenter this application.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01028: The error handler supplied is not the correct type.

Cause: The error handler supplied was not the correct type.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01029: Query execution is unsuccessful.

Cause: Query execution was not successful.

Action: Try executing the query again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01030: The workbook or worksheet search fails.

Cause: The workbook or worksheet search failed.

Action: Check whether the worksheet or workbook exists. If it does not, then specify another worksheet or workbook.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01031: Oracle BI Discoverer is unable to find the requested worksheet.

Cause: Oracle BI Discoverer was unable to find the worksheet that was requested.

Action: Ensure that the worksheet exists, or specify worksheet workbook.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01032: Oracle BI Discoverer is unable to find the workbook.

Cause: Oracle BI Discoverer was unable to find the workbook.

Action: Ensure that the workbook exists, or specify another workbook.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01033: cannot restore the worksheet state. Check the Discoverer application log for more details.

Cause: Unable to restore the worksheet state.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01034: Oracle BI Discoverer is unable to restore the application state specified on the URL. Check the Discoverer application log for more details.

Cause: Oracle BI Discoverer was unable to restore the application state specified on the URL.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01035: The specified connection type is invalid.

Cause: An invalid connection type was specified.

Action: Specify a valid connection type.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01036: The specified preferences return page is invalid.

Cause: An invalid preferences return page was specified.

Action: Specify a valid preferences return page.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01037: The specified locale string is invalid.

Cause: An invalid locale string was specified.

Action: Specify a valid locale String.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01038: The connection store is in an invalid state.

Cause: The connection store is in an invalid state.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01039: The connection list is currently unavailable.

Cause: The connection list was unavailable.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01040: unable to create a new connection because user-defined connections are not enabled or connection management is currently disabled

Cause: User-defined connections were not enabled or connection management was disabled.

Action: Enable user-defined connections and connection management.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01041: A connection does not exist for the given connection key.

Cause: A connection did not exist for the given connection key.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01042: Oracle BI Discoverer is unable to connect. Check the Discoverer application log for more details.

Cause: Oracle BI Discoverer was unable to connect.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01043: The specified connection type {0} is invalid.

Cause: The specified connection type is invalid.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01044: The specified summary option is invalid.

Cause: An invalid summary option was specified.

Action: Provide a valid summary option.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01045: The specified workbook type {0} is invalid.

Cause: An invalid workbook type was specified.

Action: Change workbook type.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01046: The specified catalog type {0} is invalid.

Cause: An invalid catalog type was specified.

Action: Change the catalog type.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01047: The specified Oracle Discoverer Beans connection type is invalid.

Cause: An invalid Oracle Discoverer Beans connection type was specified.

Action: Provide a valid connection Type.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01048: The specified role is invalid.

Cause: An invalid role was specified.

Action: Provide a valid role.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01049: The specified EUL is invalid.

Cause: An invalid end user layer was specified.

Action: Provide a valid end user layer.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01050: The Oracle BI Discoverer Beans connection fails. Check the Discoverer application log for more details.

Cause: The Oracle BI Discoverer Beans connection failed.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01051: The Oracle BI Discoverer Beans authentication fails. Check the Discoverer application log for more details.

Cause: The Oracle BI Discoverer Beans authentication failed.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01052: No EULs are available for the given connection details.

Cause: No end user layers (EULs) were available for the given connection details.

Action: Try another connection.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01053: No responsibilities are available for the given connection details.

Cause: No responsibilities were available for the provided connection details.

Action: Try another connection.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01054: An unknown error occurred.

Cause: An unknown error occurred.

Action: Reconnect, or Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01055: No data is available for export.

Cause: Work sheet export failed as no data was available for export.

Action: Check the worksheet data and try exporting again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01056: The document requested is no longer available. This can happen if user session times out or user log out and returns to the page using back or forward in the browser. Perform the export operation again.

Cause: The requested document was not available. This can happen if the session times out or if the user logs out and returns to the page using back or forward in the browser.

Action: Perform export operation again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01057: No data is available for export. This is due to an issue within Oracle BI Discoverer. Contact Oracle Support Services.

Cause: No data was available for export, due to an issue within Oracle BI Discoverer.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

BI-VIEWER-01058: The specified export type is invalid. Choose a different export type.

Cause: An invalid export type was submitted.

Action: Specify a valid export type.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01059: Parameters are not supported for OLAP data sources.

Cause: Parameters were supplied for OLAP data sources, which are not supported.

Action: Use parameters for relational data sources.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01060: The state string key already exists. This is due to an issue within Oracle BI Discoverer. Contact Oracle Support Services.

Cause: An attempt was made to provide a state string key that already exists, due to an issue within Oracle BI Discoverer.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

BI-VIEWER-01061: A gradient is set on a series item that does not exist.

Cause: A gradient was set on a series item that does not exist.

Action: Reset the gradient on a series item that exists.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01062: The specified margin value is illegal.

Cause: An illegal margin value was supplied.

Action: Try with a different value.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01063: The selected page orientation is illegal. Try with a different value.

Cause: An illegal page orientation was selected.

Action: Try with a different value.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01064: The selected paper size is illegal. Contact the OracleAS Discoverer administrator.

Cause: An illegal paper size was selected.

Action: Try with a different value.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01065: The value supplied for the selection of when to print the title, footnote, or page items is invalid.

Cause: An illegal value was supplied for the selection of when to print the title, footnote, or page items.

Action: Try with different value.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01066: The specified scaling value is illegal. Try with a different value.

Cause: An illegal scaling value was supplied.

Action: Try with a different value.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01067: The specified URL is invalid.

Cause: The URL supplied was invalid.

Action: Specify a valid URL.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01068: The deferred event is invalid. Start the operation from the beginning.

Cause: The deferred event was invalid.

Action: Start the operation from the beginning.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01069: The deferred request is malformed. The request cannot be processed.

Cause: Because the deferred request was malformed, the request could not be processed.

Action: Try again with a different request.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01070: The specified attachment permission is invalid. It should be either "server" or "client".

Cause: An invalid attachment permission was specified.

Action: Specify either "server" or "client"
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01071: The specified client type is invalid. A client type should be either "Viewer" or "Plus".

Cause: An invalid client type was specified.

Action: Specify either "Viewer" or "Plus" .
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01072: An error occurs while removing security-sensitive parameters from the URL {0}.

Cause: An error occurred while removing security-sensitive parameters from the URL

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01073: An invalid encoding type is found during string encoding.

Cause: Invalid encoding type was found during string encoding.

Action: Change the encoding type to a valid one.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01074: An invalid encoding type is found during string decoding.

Cause: Invalid encoding type was found during string decoding.

Action: Change the decoding type to a valid one.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01075: The specified sort direction {0} is invalid.

Cause: An invalid sort direction was specified.

Action: Change the sort direction to a valid one.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01076: The requested page requires a connection that no longer exists.Select a connection from the list below and use the links provided in subsequent pages to navigate to the desired location.

Cause: A page was requested that required a connection that no longer exists.

Action: Select a connection from the list provided, and use the links in subsequent pages to navigate to the desired location.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01077: A connection error. {0}

Cause: A connection error has occurred.

Action: Check the Discoverer application log for more details
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01078: An error occurs while logging out. {0}

Cause: An error occurred while logging out.

Action: Try again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01079: The worksheet name does not exist as a parameter on the URL. The request is invalid.

Cause: The worksheet name did not exist as a parameter on the URL.

Action: Provide valid URL with work sheet name in URL parameter.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01080: The specified worksheet name or workbook name is invalid. The following character is invalid: {0}. Change the name and try again.

Cause: An invalid worksheet or workbook name was specified.

Action: Change the name and try again
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01081: The specified user name is invalid. Change the user name and try again.

Cause: An invalid user name was specified.

Action: Change the user name and try again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01082: The specified password is invalid. Change the password and try again.

Cause: An invalid password was specified.

Action: Change the password name and try again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01083: The specified database is invalid. Change the database and try again.

Cause: An invalid database was specified.

Action: Change the database and try again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01084: The specified end user layer (EUL) is invalid. Change the end user layer and try again.

Cause: An invalid end user layer was specified.

Action: Change the end user layer and try again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01085: The specified connection name is invalid. Change the connection name and try again.

Cause: An invalid connection name was specified.

Action: Change the connection name and try again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01086: The specified description is invalid. Change the description and try again.

Cause: An invalid description was specified.

Action: Change the description and try again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01087: The specified sender is invalid. Change the sender and try again.

Cause: An invalid sender was specified.

Action: Change the sender and try again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01088: The specified recipient is invalid. Change the recipient and try again.

Cause: An invalid recipient was specified.

Action: Change the recipient and try again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01089: The specified carbon copy (CC) is invalid. Change the CC and try again.

Cause: An invalid carbon copy (CC) was specified.

Action: Change the CC and try again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01090: The specified blind carbon copy (BCC) is invalid. Change the BCC and try again.

Cause: An invalid blind carbon copy (BCC) was specified

Action: Change the BCC and try again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01091: The specified subject is invalid. Change the subject and try again.

Cause: An invalid subject was specified.

Action: Change the subject and try again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01092: The specified body is invalid. Change the body and try again.

Cause: An invalid body was specified.

Action: Change the body and try again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01093: The specified connection key is invalid. Correct the connection key and try again.

Cause: An invalid connection key was specified.

Action: Correct the connection key and try again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01094: The specified row or column value is invalid. The values specified must be greater than zero. Press "Back" button, change the values, and submit them again.

Cause: The specified row or column value was not greater than zero, as required.

Action: Press "Back" button, change the values, and submit them again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01095: The specified graph height is invalid. Change the graph height and try again.

Cause: An invalid graph height was specified.

Action: Change the graph height and try again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01096: The specified graph width is invalid. Change the graph width and try again.

Cause: An invalid graph width was specified.

Action: Change the graph width and try again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01097: The specified page orientation is invalid. Change the page orientation and try again.

Cause: An invalid page orientation was specified.

Action: Change the page orientation and try again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01098: The specified paper size is invalid. Change the paper size and try again.

Cause: An invalid paper size was specified.

Action: Change the paper size and try again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01099: The specified right margin is invalid. Change the right margin and try again.

Cause: An invalid right margin was specified.

Action: Change the right margin and try again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01100: The specified left margin is invalid. Change the left margin and try again.

Cause: An invalid left margin was specified.

Action: Change the left margin and try again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01101: The specified bottom margin is invalid. Change the bottom margin and try again.

Cause: An invalid bottom margin was specified.

Action: Change the bottom margin and try again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01102: The specified top margin is invalid. Change the top margin and try again.

Cause: An invalid top margin was specified.

Action: Change the top margin and try again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01103: The specified scaling is invalid. Change the scaling and try again.

Cause: An invalid scaling was specified.

Action: Change the scaling and try again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01104: Oracle BI Discoverer Viewer cannot find a connection for the given connection key.

Cause: Oracle BI Discoverer Viewer was unable to find a connection for the given connection key.

Action: Try again with different connection, and check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01105: Oracle BI Discoverer Viewer cannot retrieve the connection type for the specified connection.

Cause: Oracle BI Discoverer Viewer was unable to retrieve the connection type for the specified connection.

Action: Try again with different connection, and check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01106: unable to retrieve connection list

Cause: Unable to retrieve connection list.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01107: The locale specified is not available on this system. Choose a different locale.

Cause: An unavailable locale was specified.

Action: Choose a different locale.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01108: error while creating the session, check for other errors.

Cause: An error occurred while creating the session.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01109: cannot find the exported file, try again.

Cause: The exported file was not found.

Action: Try to export again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01110: Oracle BI Discoverer Viewer is unable to scroll the graph to its proper position.

Cause: Oracle BI Discoverer Viewer was unable to scroll the graph to its proper position.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01111: trying to validate the connection, but password is missing.

Cause: The password was missing while trying to validate the connection.

Action: Provide a password.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01112: Oracle BI Discoverer Viewer cannot update the connection.Check for other errors.

Cause: Oracle BI Discoverer Viewer was unable to update the connection.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01113: Oracle BI Discoverer Viewer cannot save the connection. Check for other errors.

Cause: Oracle BI Discoverer Viewer was unable to save the connection.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01114: Nothing is selected to print. Either the crosstab, table, or graph must be selected in order to print.

Cause: Nothing was selected to print.

Action: Select the crosstab, table, or graph to print.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01115: An error occurs while trying to perform the export. Try again.

Cause: An error occurred while trying to perform the export.

Action: Try to export again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01116: The PDF generator cannot calculate the column widths.

Cause: The PDF generator was unable to calculate the column widths.

Action: Specify the column widths and Check the log file for details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01117: Oracle BI Discoverer Viewer cannot create the view toolbar.

Cause: Oracle BI Discoverer Viewer was unable to create the view toolbar.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01118: The view tool event specified is not supported. {0}

Cause: An unsupported view tool event was specified.

Action: Use another tool.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01119: The specified worksheet layout is invalid.

Cause: An invalid worksheet layout was specified.

Action: Change to a valid worksheet layout.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01120: A worksheet must be open before performing this event.

Cause: An attempt was made to perform an event, but the worksheet was not open.

Action: Open the worksheet, and try again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01121: Oracle BI Discoverer Viewer did not have the open connection required to perform this event.

Cause: Oracle BI Discoverer Viewer must have an open connection before performing this event.

Action: Open a connection.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01122: Oracle BI Discoverer Viewer cannot create the URL event with the supplied URL parameters. Correct the parameters and try again.

Cause: Oracle BI Discoverer Viewer was unable to create the URL event in response to the supplied URL parameters.

Action: Correct the parameters, and try again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01123: The URL API parameter {0} is invalid. Correct the parameter, and try again.

Cause: An invalid URL API parameter was specified.

Action: Correct the parameter, and try again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01124: Oracle BI Discoverer Viewer cannot find the data necessary to display the results of this event. Correct any errors, and try again.

Cause: Oracle BI Discoverer Viewer was unable to find the necessary data for displaying the results of this event.

Action: Correct any errors, and try again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01125: Oracle BI Discoverer Viewer was unable to locate the definition file necessary to construct the results of this event. Contact the Oracle Fusion Middleware administrator.

Cause: Oracle BI Discoverer Viewer was unable to locate the definition file necessary to construct the results of this event.

Action: Contact the Oracle Fusion Middleware administrator.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01126: Oracle BI Discoverer Viewer cannot access the definition file necessary to construct the results of this event. Contact the Oracle Fusion Middleware administrator.

Cause: Oracle BI Discoverer Viewer was unable to access the definition file necessary to construct the results of this event.

Action: Contact the Oracle Fusion Middleware administrator.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01127: unable to generate a PDF using the current settings, change the settings by choosing the "Printable page" link in the actions section of the open worksheet

Cause: Unable to generate a PDF using the current settings.

Action: Change the settings by choosing the "Printable page" link in the actions section of the open worksheet.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01128: Oracle BI Discoverer Viewer cannot find the warning type in the warning message. Contact the Oracle Fusion Middleware administrator.

Cause: There was a warning message, but Oracle BI Discoverer Viewer was unable to find the warning type.

Action: Contact the Oracle Fusion Middleware administrator.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01129: A workbook already exists with the name specified, and it is owned by another user. Specify a different name and try again.

Cause: A workbook name was specified but could not be used, because it is owned by another user.

Action: Specify a different name and try again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01130: Changed preferences might affect the data. Rerun the query to enable these preferences in the currently open worksheet.

Cause: Some preferences have changed that might affect the data in the open worksheet.

Action: Rerun the query so that these preferences can take effect in the currently open worksheet.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01131: Oracle BI Discoverer Viewer is unable to reconstitute to a different state while there is a deferred request. Use the back button in your browser to go back several pages and try again.

Cause: Oracle BI Discoverer Viewer is unable to reconstitute to a different state while there is a deferred request.

Action: Use the back button in your browser to go back several pages, and try again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01132: Oracle BI Discoverer is unable to read the configuration file. A number cannot be derived from the following expression: {0}.

Cause: Oracle BI Discoverer was unable to read the configuration file. A number could not be derived from the expression.

Action: Specify the number again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01133: Oracle BI Discoverer is unable to read the configuration file. A value is required for the following expression: {0}

Cause: Oracle BI Discoverer was unable to read the configuration file. A value is required for the expression.

Action: Specify the value again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01134: Oracle BI Discoverer is unable to read the configuration file. The configuration file must be local.

Cause: Oracle BI Discoverer was unable to read the configuration file. The configuration file must be local

Action: Provide the valid location again, check Discoverer configuration guide for configuration file location.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01135: error with the e-mail server message is not sent.

Cause: The e-mail message was not sent due to an error with the e-mail server.

Action: Correct any errors pertaining to the server, and try again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01136: The outgoing e-mail server cannot be found. Contact the Oracle Fusion Middleware administrator.

Cause: The outgoing e-mail server could not be found.

Action: Contact the Oracle Fusion Middleware administrator.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01137: Oracle BI Discoverer times out while sending your e-mail. The e-mail may be sent anyway.

Cause: Oracle BI Discoverer timed out while sending your e-mail.

Action: E-mail may have been sent, if not sent it again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01138: Oracle BI Discoverer is unable to create an e-mail session. Ensure that the e-mail server is accessible.

Cause: Oracle BI Discoverer was unable to create an e-mail session.

Action: Ensure that the e-mail server is accessible.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01139: The e-mail attachment file size is too large. The size must be less than (KB): {0}.

Cause: The e-mail attachment file size was too large.

Action: Reduce the file size.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01140: User lacks appropriate permissions to send server-side e-mail attachments.

Cause: The user did not have the appropriate permissions to sent server-side e-mail attachments.

Action: Obtain the permissions necessary to send server-side e-mail attachments.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01141: The e-mail cannot be sent successfully. Check the Discoverer application log for more details.

Cause: The e-mail was not sent successfully.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01142: deleting the e-mail attachment, click on the Send as e-mail link to send again.

Cause: The e-mail attachment has been deleted.

Action: Click on the Send as e-mail link to send again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01144: unexpected error during state string compression.

Cause: An unexpected error occurred during state string compression.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01143: The character encoding specified during message assembly is invalid.

Cause: The character encoding that was used during message assembly was invalid.

Action: Attach and send mail again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01145: Oracle BI Discoverer cannot generate the PDF requested.

Cause: Oracle BI Discoverer was unable to generate the PDF requested.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01146: The PDF printing status is invalid. Check the Discoverer application log for more details.

Cause: The PDF printing status was invalid.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01147: The width specified for the column at position {0} is invalid.

Cause: An invalid width was specified for the column.

Action: Change the column width specified.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01148: unable to open the worksheet requested: {0}

Cause: Unable to open the worksheet requested.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01149: BI Beans cannot handle the event: {0}.

Cause: The BI Bean was unable to handle the event.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01150: Query scheduling fails; the request cannot be processed.

Cause: Query scheduling failed.

Action: Try to reschedule query and check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01151: unable to cancel query

Cause: Unable to cancel query.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01152: Creation of the parameters component fails.

Cause: Creation of the parameters component failed.

Action: Try creating the component again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01153: Creation of the list of values component fails. {0}

Cause: Creation of the list of values component failed.

Action: Try creating the component again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01154: Cannot find a required parameter: {0}

Cause: Could not find a required parameter.

Action: Specify the parameter again
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01155: The specified form class {0} is invalid.

Cause: An invalid form class was specified.

Action: Specify a valid form class.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01156: The worksheet must be open to run a query.

Cause: The worksheet was not open when the user tried to run a query.

Action: Open the worksheet.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01157: The initial setup is incorrect; the query cannot be run.

Cause: The initial setup was not performed properly.

Action: Perform the initial setup again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01158: unable to fetch query estimate {0}

Cause: Failed to fetch the query estimate.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01159: Oracle BI Discoverer is encountering a query state that was not expected. {0}

Cause: Oracle BI Discoverer encountered a query state that was not expected.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01160: unable to apply selected parameters, check the Discoverer application log for more details

Cause: Unable to apply selected parameters.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01161: The old password is invalid.

Cause: The old password was entered incorrectly.

Action: Type the old password again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01162: new password or verification password are invalid

Cause: Invalid new password or verification password.

Action: Type the new password and verification password again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01163: New passwords do not match

Cause: The new password entered for verification did not match the new password.

Action: Type the new password and verification password again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01164: The specified workbook and worksheet {0} are invalid.

Cause: An invalid workbook and worksheet were specified.

Action: Specify a valid worksheet and a valid workbook.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01165: The specified workbook {0} is invalid.

Cause: An invalid workbook was specified.

Action: Specify a valid workbook.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01166: The specified worksheet {0} is invalid.

Cause: An invalid worksheet was specified.

Action: Specify a valid worksheet.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01167: Oracle BI Discoverer is unable to retrieve the connection when opening the requested worksheet.

Cause: Unable to retrieve the connection when opening the requested worksheet.

Action: Try to connect again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01168: Oracle BI Discoverer is unable to retrieve the end user layer when opening the requested worksheet.

Cause: Unable to retrieve the EUL when opening the requested worksheet.

Action: Try to connect again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01169: Oracle BI Discoverer is unable to retrieve the workbook when opening the requested worksheet.

Cause: Unable to retrieve the connection when opening the requested workbook.

Action: Try to connect again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01170: Oracle BI Discoverer is unable to retrieve the requested worksheet.

Cause: Unable to retrieve the requested worksheet.

Action: Try to connect again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01171: The link contains an invalid state string. None of the expected connection details are found.

Cause: None of the expected connection details are found.

Action: Provide the connection details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01172: The link contains an invalid state string. None of the expected workbook details are found.

Cause: None of the expected workbook details are found.

Action: Provide the workbook details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01173: Oracle BI Discoverer is unable to restore the explorer state.

Cause: The explorer state was invalid.

Action: Open the worksheet or work book , and try again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01174: Oracle BI Discoverer is unable to export the graph. Check the Discoverer application log for more details.

Cause: Oracle BI Discoverer was unable to export the graph

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01175: Oracle BI Discoverer is unable to export the Web query file. Check the Discoverer application log for more details.

Cause: Oracle BI Discoverer was unable to export the Web query file.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01176: The export operation fails, check the Discoverer application log or other errors on the screen for more details.

Cause: Export operation failed.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01177: The provided information must be in the form of <host>:<port>:<sid>.

Cause: An invalid host port SID was specified.

Action: Resubmit the information in <host>:<port>:<sid> form.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01178: Oracle BI Discoverer cannot determine the connection type.

Cause: Oracle BI Discoverer was unable to determine the connection type.

Action: Specify the correct connection type and try again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01179: Oracle BI Discoverer is unable to complete the connection initialization.

Cause: A connection initialization problem occurred.

Action: Initialize the connection again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01180: Oracle BI Discoverer is unable to complete the session initialization.

Cause: A session initialization problem occurred.

Action: Initialize the session again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01181: Oracle BI Discoverer is unable to completely close the session.

Cause: Oracle BI Discoverer was unable to completely close the session.

Action: Try again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01182: Oracle BI Discoverer is unable to authenticate using the password provided. This can happen due to an invalid password or because the password was lost while using back, forward, or refresh in your browser. Enter the password again to continue.

Cause: Either the password was invalid, or the password was lost while using back, forward or refresh in the browser.

Action: Provide a valid password.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01183: Session hijacking is not supported for OLAP connections.

Cause: An unsupported action was attempted.

Action: Do not try session hijacking for OLAP Connections.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01184: An error occurs while setting options. Check the Discoverer application log for more details.

Cause: Options were not set appropriately.

Action: Reset the options. Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01185: An error occurs while setting page items. Check the Discoverer application log for more details.

Cause: Page items were not set appropriately]

Action: Set page items correctly. Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01186: Cannot retrieve connection list . Check the Discoverer application log for more details.

Cause: Connection list could not be retrieved.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01187: Cannot retrieve connection details. Check the Discoverer application log for more details.

Cause: Connection details could not be retrieved.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01188: Oracle BI Discoverer cannot find the workbook owner. Check the Discoverer application log for more details.

Cause: Oracle BI Discoverer could not find the workbook owner.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01189: Oracle BI Discoverer cannot determine if the worksheet contains page items. Check the Discoverer application log for more details.

Cause: Oracle BI Discoverer was unable to determine if the worksheet contains page items.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01190: Oracle BI Discoverer cannot create the sort customize page. Check the Discoverer application log for more details.

Cause: Oracle BI Discoverer was unable to create the sort customize page.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01191: Oracle BI Discoverer cannot create the format customize page. Check the Discoverer application log for more details.

Cause: Oracle BI Discoverer was unable to create the format customize page.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01192: Oracle BI Discoverer cannot create the layout customize page. Check the Discoverer application log for more details.

Cause: Oracle BI Discoverer was unable to create the layout customize page.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01193: Oracle BI Discoverer cannot create the drill page. Check the Discoverer application log for more details.

Cause: Oracle BI Discoverer was unable to create the drill page.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01194: Oracle BI Discoverer cannot create the save as dialog. Check the Discoverer application log for more details.

Cause: Oracle BI Discoverer was unable to create the save as dialog.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01195: An error occurs while linking or unlinking the layout. Check the Discoverer application log for more details.

Cause: An error occurred while linking or unlinking the layout.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01196: Oracle BI Discoverer is unable to save the workbook.

Cause: Oracle BI Discoverer was unable to save the workbook.

Action: Verify that the necessary saving permissions are assigned; if not, try save as.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01197: The specified drill-out URL is invalid. Correct the URL and try again.

Cause: The drill-out URL specified was invalid.

Action: Correct the URL and try again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01198: Error while processing the specified link. Check the Discoverer application log for more details.

Cause: An error occurred while processing the specified link.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01199: Invalid or unsupported protocol {0}

Cause: An invalid or unsupported protocol was supplied.

Action: Change the protocol.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01200: Oracle BI Discoverer is unable to open the last saved version of the workbook or worksheet requested.

Cause: Oracle BI Discoverer was unable to open the last saved version of the workbook or worksheet requested.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01201: unable to open workbook because item "{0}" is missing

Cause: Unable to open workbook because item is missing.

Action: Specify the missing item.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01202: Form field validation fails. Fix the error and try again.

Cause: The form field validation failed.

Action: Correct the form fields, and try again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01203: The destination for the preferences page is invalid.

Cause: An invalid destination was found for the preferences page.

Action: Try again with a valid destination.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01204: The query prediction warning value is invalid. Change the value and try again.

Cause: An invalid query prediction warning value was specified.

Action: Provide a valid value, and try again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01205: The query time limit value is invalid. Change the value and try again.

Cause: An invalid query time limit was specified.

Action: Provide a valid query time limit value.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01206: The query maximum rows limit value is invalid. Change the value and try again.

Cause: An invalid query maximum rows limit was specified.

Action: Provide a valid query maximum rows limit value.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01207: The query incremental fetch value is invalid. Change the value and try again.

Cause: An invalid query incremental fetch valid was specified.

Action: Provide a valid query incremental fetch value.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01208: The LOV time limit value is invalid. Change the value and try again.

Cause: An invalid LOV time limit value was specified.

Action: Provide a valid LOV time limit value.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01209: The specified measurement unit for printing is invalid. Change the value and try again.

Cause: An invalid measurement unit was specified for printing.

Action: Provide a valid measurement unit value used for printing, and try again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01210: The specified axis label type value is invalid. Change the value and try again.

Cause: An invalid axis label type value was specified.

Action: Provide a valid axis label value, and try again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01211: The specified rows per page value is invalid. Change the value and try again.

Cause: An invalid rows per page value was specified.

Action: Specify a valid rows per page value.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01212: The specified columns per page value is invalid. Change the value and try again.

Cause: An invalid columns per page value was specified.

Action: Specify a valid columns per page value.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01213: The specified summary data value is invalid. Change the value and try again.

Cause: An invalid summary data value was specified.

Action: Specify a valid summary data value.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01214: The specified locale is invalid. Change the value and try again.

Cause: An invalid locale was specified.

Action: Specify a valid locale.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01215: The integer value must be between the following two values: {0}

Cause: An invalid integer was specified.

Action: Specify a value between the two given values.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01216: The visible option must be set to ALL or DISPLAYED.

Cause: The visible option was not set to ALL or DISPLAYED.

Action: Set the visible option to ALL or DISPLAYED.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01217: Oracle BI Discoverer is unable to generate PDF documents as the PDF printing pool is no longer valid. Restart the application and try again.

Cause: The PDF printing pool was no longer valid.

Action: Restart Application.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01218: The specified graph position is invalid. Contact the Oracle Fusion Middleware administrator.

Cause: An invalid graph position was specified.

Action: Contact the Oracle Fusion Middleware administrator.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01219: The Oracle BI Discoverer Plus plugin URL is invalid. Contact the Oracle Fusion Middleware administrator.

Cause: An invalid Oracle BI Discoverer Plus plugin URL was specified.

Action: Contact the Oracle Fusion Middleware administrator.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01220: No page sizes are configured for printing, add at least one page size to the list of available page sizes.

Cause: No page size configured for printing.

Action: Configure the page size for printing.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01222: An attribute is missing or is invalid.

Cause: An attribute was missing or was invalid.

Action: Provide a valid attribute.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01221: The workbook no longer exists.

Cause: The workbook has been deleted.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01223: A calculation is missing or is invalid.

Cause: A calculation was missing or was invalid.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01224: A dimension is missing or is invalid.

Cause: A dimension was missing or was invalid.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01225: A hierarchy is missing or is invalid.

Cause: A hierarchy was missing or was invalid.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01226: A level is missing or is invalid.

Cause: A level was missing or was invalid.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01227: A measure is missing or is invalid.

Cause: A measure was missing or was invalid.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01228: invalid query definition; cannot load the query.

Cause: An invalid query definition was supplied.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01229: A saved selection is missing or is invalid.

Cause: A saved selection was missing or was invalid.

Action: See the application log for details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01231: Removing the worksheet to allow work to continue. Edit the worksheet using Oracle BI Discoverer Plus for OLAP to correct the problem.

Cause: Worksheet has been removed to allow user to continue.

Action: Edit the worksheet using Oracle BI Discoverer Plus for OLAP to correct the problem.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01232: This worksheet may not display data correctly. Edit this worksheet using Oracle BI Discoverer Plus for OLAP to correct the problem.

Cause: Worksheet may not display data correctly.

Action: Edit the worksheet using Oracle BI Discoverer Plus for OLAP.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01233: The developer key is not unique.

Cause: The developer key was not unique.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01234: The workbook already exists.

Cause: The workbook has been modified by another user.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01235: The workbook content is altered by another user.

Cause: The workbook has been modified by another user.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01236: unable to open workbook

Cause: Unable to open workbook.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01237: unable to save the workbook

Cause: Unable to save the workbook.

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01238: The specified developer key is illegal.

Cause: An illegal developer key was specified.

Action: Specify a legal developer key.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01239: The specified name is invalid.

Cause: An invalid name was specified.

Action: Specify a valid name.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01240: insufficient database privileges to save this workbook

Cause: The user did not have the necessary privileges to save workbook.

Action: Obtain the necessary privileges to save the workbook. Contact the OracleAS Discoverer administrator to obtain this.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01241: insufficient query privileges to save this workbook

Cause: The user did not have the necessary privileges to save workbook.

Action: Obtain the necessary privileges to save the workbook. Contact the OracleAS Discoverer administrator to obtain this.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01243: Zero length and null strings are not allowed.

Cause: Illegal string values were supplied.

Action: Enter proper string values.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01242: The workbook was not found.

Cause: The workbook was not found

Action: Check the Discoverer application log for more details.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01244: The PDF document requested is no longer available. This can happen if user session times out or user log out and come back to the page using back or forward in the browser. Perform the PDF generation again.

Cause: The session timed out, or the user logged out and returned to this page using back or forward in the browser.

Action: Perform the PDF generation again.
Level: 1

Type: ERROR

Impact: Process

BI-VIEWER-01245: Oracle BI Discoverer cannot read the configuration file. The following expression is invalid: {0}.

Cause: Oracle BI Discoverer was unable to read the configuration file might be a wrong expression specified in it.

Action: Check the configuration file location and specified invalid expression again.
Level: 1

Type: ERROR

Impact: Process

21 BIACM-00007 to BIACM-00082

BIACM-00007: Import initialization error, no data

Cause: An error occurred while reading data from the file provided

Action: Ensure the file to be imported has data in the proper format
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00008: File not found

Cause: No file present at the given location

Action: Ensure the file location and filename are proper
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00009: Not a directory

Cause: Given input was not of directory type

Action: Ensure that only directory is supplied as the input
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00010: Concurrent migrations going on

Cause: Another import/export detected in some other session

Action: Please wait for ongoing import/export to complete
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00011: Error while validating data source number, non-numeric type

Cause: An error occurred while validating the data source number value

Action: Ensure whether the input value is numeric
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00013: No data server selected

Cause: No selection of any data server for the data source to be registered

Action: Please check at least one data server for the data source to be registered
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00014: Error registering the data source

Cause: An error while registering the source system entered

Action: Modify the actionListener for registering the source system to handle the error
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00015: Error editing the data source

Cause: An error occurred while editing the source system entered

Action: Modify the actionListener for editing the source system to handle the error
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00016: Missing target domain

Cause: Target domain not specified in domain mapping pair task parameter

Action: Please specify target domain
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00017: Missing source domain

Cause: Source domain not specified in domain mapping pair task parameter

Action:
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00018: Missing domain mapping pair

Cause: No source to target domain mappings specified in task parameter

Action:
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00019: No valid task parameter received

Cause: Received invalid task parameters. Parameters list is empty or contains invalid values

Action: Unexpected error. Please contact customer support
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00051: Error adding new conformed domain member

Cause: Attempted to add a new conformed domain member {0}. "{0}" member code already exists

Action: Enter a new conformed domain member code
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00052: Error adding new conformed domain member

Cause: Attempted to add a new conformed domain member {0}. "{0}" member code already exists and is a reserved domain member

Action: Enter a new domain member code
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00053: Invalid data source

Cause: Invalid data source num id: {0}

Action: Ensure selected data source is valid
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00054: Error modifying domain member map

Cause: Could not find existing row with key "{0}"

Action: Unexpected exception. Please contact customer support
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00055: Unspecified view object

Cause: View object was not specified

Action: Unexpected exception. Please contact customer support
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00056: Unsupported operation

Cause: Adding new member map for non-range domain is not supported

Action: Verify that source domain's member type is a range. If not, it's a defect as operation is not supported
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00057: Error locating conformed domain code

Cause: The selected conformed domain code {0} was not found

Action: Unexpected exception. Please contact customer support
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00058: Invalid source instance

Cause: Unexpected source instance, selected index "{0}" was not valid

Action: Please verify and re-select a source instance
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00059: Invalid source instance

Cause: Source Instance was not specified

Action: Please specify a source instance
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00060: Invalid source domain member type

Cause: Invalid source domain member type: {0} was found

Action: Unexpected domain member type. Ensure that domain has valid member type: CODE, CODE_MULTI_COL, NUM_RANGE, or ALNUM_RANGE
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00061: Invalid member maps

Cause: Invalid member map(s) found for domain mapping {0} \u27A1 {1}:

Action:
Level: 1

Type: WARNING

Impact: Configuration

BIACM-00062: Invalid member maps

Cause: One or more range value is invalid

Action: Please review and correct the invalid map(s)
Level: 1

Type: WARNING

Impact: Configuration

BIACM-00063: Invalid member maps

Cause: Range start/end was empty

Action: Both start and end range values are required. Please enter both values
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00064: Invalid member range values

Cause: [{0}, {1}]: range end must be greater than range start

Action: Please check and correct the range value to ensure that it is valid
Level: 1

Type: WARNING

Impact: Configuration

BIACM-00065: Invalid member range values

Cause: A gap or overlap between {0} and {1} ranges is not allowed for numeric ranges

Action: Please correct and verify that start value is smaller than end value in a range
Level: 1

Type: WARNING

Impact: Configuration

BIACM-00066: Empty range members

Cause: [{0} \u27A1 {1}]: empty start/end range was not allowed

Action: Please specify both start and end range
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00067: Invalid member range values

Cause: Range start value of {0} range must be greater than range end of {1} range

Action: Please check and correct the range value to ensure that it is valid
Level: 1

Type: WARNING

Impact: Configuration

BIACM-00068: You are updating the value of parameter {0} at a global level. The values of parameters with the same name associated with the Fact Groups or Dimension Groups shown below will also be updated

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

BIACM-00069: You are attempting to update the parameter value of a parameter that is defined as read only. Edit operation is not supported for this parameter

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

BIACM-00070: You are updating the value of parameter {0}. The value of this parameter must be the same for all parameters of the same name associated with the Fact Groups or Dimension Groups shown below. The value of each parameter associated with the Fact Groups or Dimension Groups shown below will be updated

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

BIACM-00071: Domain Code Not Found

Cause: Unexpected null domain code

Action: Check to ensure that current domain code is set internally
Level: 1

Type: WARNING

Impact: Configuration

BIACM-00072: For NUMBER Parameter Data Type (LIST Value Type)\: 1,2,3 For VARCHAR2 Parameter Data Type(LIST Value Type)\: abc,xyx,pqr For VARCHAR2 Parameter Data Type(SINGLE Value Type)\: abc

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

BIACM-00073: Free Form Entry. For Multi Value (List Type) Parameters seperate them with commas. e.g. 1,2,3 (NUMBER data type) and a,b,c (VARCHAR2 data type)

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

BIACM-00074: Enter Numeric Value only

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

BIACM-00075: Free Form Entry

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

BIACM-00076: A change of the Parameter Value requires a restart of the BI Server for the value to become effective

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

BIACM-00077: For NUMBER Parameter Data Type (LIST Value Type)\: 1,2,3 For VARCHAR2 Parameter Data Type(LIST Value Type)\: abc,xyx,pqr For VARCHAR2 Parameter Data Type(SINGLE Value Type)\: abc

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00078: The data source ID number you have entered is already in use by another data source

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00079: Invalid Sign In

Cause: Invalid user ID or password

Action: Try again using correct user ID and password. Letters in user ID and password must be typed using the correct case
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00080: Authorization Error

Cause: Access denied. You do not have permission to access Oracle BI Applications Configuration Manager

Action: Contact your help desk or system administrator to obtain authorization to access this application
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00081: Batch edit error

Cause: no row is selected for batch editing

Action: Please select at least a row and retry
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00082: Sync To Source warning

Cause: Sync To Source will perform the following actions to the target member {0}: insert new target members from the source domain and auto generate 1-1 member maps.

Action: Click OK to continue
Level: 1

Type: WARNING

Impact: Configuration

22 BPM-09708 to BPM-40011

NOTE: Some errors are shared between SOA and BPM, and their prefix may be "BPM" instead of the correct prefix "ORABPEL". However, the error number is always accurate. If you cannot locate a particular error in this file -- if the prefix does not match with the error number, then consider the error number while searching for a solution.

BPM-09708: Error while querying workflow task {0}

Cause: Error while querying workflow task {0}

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-09713: Invalid logical operator in predicate

Cause: An invalid logical operator was used in the predicate.

Action: Specify a valid logical operator (AND or OR) for the predicate.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-09714: Invalid predicate operator

Cause: Invalid predicate operator {0}

Action: Specify a valid logical operator for the predicate.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-09715: Invalid predicate operator for list values

Cause: Invalid predicate opertor for list values. List values are only supported for IN and NOT_IN operator

Action: Use appropriate operator in the predicate for list values.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-09716: Invalid value type for predicate

Cause: Invalid value type {0} for predicate column type {1}

Action: Provide a valid value type for the predicate specified. Refer to TableConstants for data types
Level: 1

Type: ERROR

Impact: Programmatic

BPM-09717: Predicate values are null

Cause: Predicate values are null for operator {0}

Action: Provide a valid predicate value for the predicate.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-09719: Trying to update a deleted task {0}

Cause: The task {0} was already deleted.

Action: Execute the query to fetch new tasks.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-09732: Persistency service internal error

Cause: Persistency service internal error

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10000: Dynamic Exception Test Case.

Cause: Dynamic Exception Test Case thrown: {0}

Action: This error happens in dynamic exception test case sceanrios. Refer to the soainfra log files for details and contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10101: Error while updating task

Cause: Error while updating task {0}

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10107: Error in withdrawing task

Cause: Error while withdrawing task {0}.

Action: Check the error stack and fix the cause of the error. Contact Oracle Support Services if the error persists.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10129: Notification for task could not be processed

Cause: Notification for task {2} could not be processed.

Action: Make sure that the notification configuration is correct and the messages are specified correctly.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10197: Error in computing workflow auto release duration

Cause: Error in computing workflow auto release duration for task "{0}".

Action: Make sure that the auto release configuration is correct.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10199: Error in computing the next workflow reminder time

Cause: Error in computing the next workflow reminder time for task "{0}".

Action: Make sure that the notification reminder configuration is correct.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10200: Error in workflow reminder configuration

Cause: Error in workflow reminder configuration for task "{0}". Reminders are configured in the routing slip XML file.

Action: Verify that the routing slip file is valid and conforms to its schema. The common errors are invalid RECCURENCE integer value, invalid RELATIVE value, invalid DURATION value.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10206: Error in retrieving task metadata

Cause: Error in retrieving task metadata because the task is no longer valid.

Action: Only valid tasks can by looked up.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10207: Error in retrieving task metadata

Cause: Error in retrieving task metadata because because business process "{1}" version "{2}" that created the task is either undeployed or turned off in the domain "{0}".

Action: If the process is undeployed, the task is no longer valid. If the process was turned off, the task metadata can be retrieved when the process state is turned on.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10301: Email account does not exist

Cause: Email Account {0} does not exist

Action: Check Workflow Notification Configuration. Verify that email account is configured
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10302: Email account already exists

Cause: Email account {0} already exists

Action: Check Workflow Notification Configuration. Ensure that each account has unique name
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10303: Fax cover page details does not exist

Cause: Fax cover page details for cover page {0} does not exist

Action: Check Workflow Notification Configuration. Verify that fax cover page exists
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10304: Fax cover page details already exist

Cause: Fax cover page details for cover page {0} already exists

Action: Check Workflow Notification Configuration. Ensure that a page detail is not entered twice
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10305: Illegal Argument

Cause: name cannot be null

Action: Check Workflow Notification Configuration. Configuration name cannot be null
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10306: Illegal Argument

Cause: Old name or new name cannot be null

Action: Check Workflow Notification Configuration. Configuration name cannot be null
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10307: Illegal Argument

Cause: name, file location or mimetype cannot be null

Action: Check Workflow Notification Configuration. name, file location or mimetype cannot be null
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10310: xml parsing error in configuration file

Cause: Error in parsing notification service configuration file {}

Action: Internal Error. Check Workflow Notification Configuration.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10311: Email protocol not supported

Cause: Email protocol {0} is not supported

Action: Check Workflow Notification Configuration. Change Email protocol.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10312: Invalid Post Read Operation

Cause: Invalid Post Read Operation

Action: Protocol specified does not support Post Read Operation. Modify Workflow Notification Configuration.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10313: No Outgoing e-mail settings

Cause: E-mail account {0} does not have outgoing e-mail settings

Action: Check Workflow Notification Configuration. Configure outgoing e-mail settings
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10314: No General e-mail settings

Cause: E-mail account {0} does not have general e-mail settings

Action: Check Workflow Notification Configuration. Configure general e-mail settings
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10315: No Incoming e-mail settings

Cause: E-mail account {0} does not have incoming e-mail settings

Action: Check Workflow Notification Configuration. Configure Incoming e-mail settings
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10316: E-mail Receiver already associated

Cause: An e-mail receiver is already associated with {0} e-mail account

Action: Internal Error. Ensure that only one receiver is registered for an e-mail account.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10317: E-mail folder does not exist

Cause: E-mail folder {0} does not exist

Action: Check Workflow Notification Configuration. Verify folder name in Incoming e-mail settings
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10318: Cannot connect to iAS Wireless notification webservice

Cause: Cannot connect to iAS wireless notification webservice running at {0}

Action: Check Workflow Notification Configuration. Configure IAS Wireless settings
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10319: iAS Wireless notification error

Cause: iAS Wireless notification error

Action: Check IAS Wireless settings in Notification Configuration
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10320: iAS Wireless settings not configured

Cause: iAS Wireless settings not configured

Action: Check IAS Wireless settings in Notification Configuration
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10321: Notification Channel not supported

Cause: Notification Channel {0} is not supported

Action: IAS Wireless does not support requested channel.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10322: Illegal Argument

Cause: Folder Name cannot be null

Action: Check Workflow Notification Configuration. Folder Name for Post Read Operation cannot be null.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10323: Internal Error

Cause: Cannot create {0} object

Action: Refer to the log file that is configured for oracle.soa.services.notification for more details on this error and contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10324: Cannot read fax cover page file

Cause: Cannot read fax cover page from file {0}

Action: Check Workflow Notification Configuration. Ensure that the FAX cover page exists as specified in configuration.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10325: Mime-Type not supported

Cause: mime-type {0} is not supported for channel {1}

Action: Internal Error. Ensure that payload content's mime type is one of supported types.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10326: Illegal Argument

Cause: From account is not set in e-mail payload

Action: Check Workflow Notification Configuration. From account is not set in payload.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10327: From Account is not configured

Cause: From account {0} is not configured

Action: Check Workflow Notification Configuration.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10328: Error in sending e-mail message

Cause: Error in sending e-mail message

Action: Check Workflow Notification Configuration. Ensure that the Email Server could be connected.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10329: user-id not set

Cause: user-id field is not set in the user payload

Action: Internal Error. Payload does not contain user id
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10330: group-id is not set

Cause: group-id field is not set in the group payload

Action: Internal Error. Payload does not contain group id
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10331: Could not send notification to user

Cause: Could not send notification to user {0}

Action: Check Workflow Notification Configuration. Ensure that underlying channels are configured.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10332: Error in post-read operation

Cause: Error while doing post-read operation on e-mail account {0}

Action: Check Workflow Notification Configuration. Check folder name and post read operation for incoming setting.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10333: Error in reading e-mail message

Cause: Error in reading e-mail message from account {0}

Action: Check Workflow Notification Configuration. Ensure that the Email Server could be connected.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10334: Error in closing e-mail folder

Cause: Error in closing e-mail folder {0}

Action: Check Workflow Notification Configuration. Verify folder name in incoming setting.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10335: Error in notification service initialization

Cause: Error in notification service initialization

Action: Internal Error. Ensure that the Notification Configuration file is valid and could be loaded.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10336: Invalid recipient address

Cause: Recipient address specified for {0} notification is invalid : {1}

Action: Check Workflow Notification Configuration. Ensure that Email/IM recipient address is valid.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10337: Invalid entry in workflow-notification-config.xml

Cause: Invalid configuration specified for {0}

Action: Please ensure that notification component is configured correctly
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10338: Incoming message could not be processed

Cause: Incoming message could not be processed

Action: Ensure that the incoming response message is not corrupted.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10339: Error while sending auto reply

Cause: Could not send {0} auto reply

Action: Internal Error. Ensure that the message being replied to is not corrupted.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10340: Error while Receiving response

Cause: Could not process received message

Action: Ensure that incoming accounts in human workflow Mailer and Email Driver match and are configured correctly.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10341: Error while Sending test notification

Cause: Could not send test notification

Action: Ensure that human workflow mailer and underlying driver are configured correctly.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10342: Could not send notification

Cause: Error while sending {0} notification

Action: Check configuration of underlying Channel specific driver.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10343: Error while creating notification content

Cause: Could not create notification content

Action: Ensure that the files being used for attachment exist and not corrupted.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10344: Could not send notification

Cause: Could not send {0} notification, since notification mode is set to {1}

Action: Ensure that Notification Mode in workflow-notification-config is set to either EMAIL or ALL to send email notifications. For rest of the channels it should be set to ALL
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10345: Error in Notification Service startup

Cause: Could not start notification service

Action: Failed to start notification service. This is a system error.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10346: Error in Notification Service shutdown

Cause: Could not shutdown notification service correctly

Action: Errors while notification service shutdown. This is a system error.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10347: Cannot send Notification to specified address

Cause: Cannot send {0} notification to {1} address. The address is being marked as 'invalid' and no further notification would be sent to this address.

Action: Make sure that : the address specified is correct; the Email/Gateway server is up and running. Once the problem is corrected, please remove the address from invalid address list using EM.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10348: Incoming message content is invalid

Cause: Incoming message could not be processed due to invalid content

Action: Please ensure that the response message is not corrupted; Actionable notifications should be responded from the same email account to which it was sent.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10349: No NID Placeholder

Cause: Incoming message content does not contain Notification ID placeholders

Action: Please ensure that the response message is not corrupted
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10350: Incoming message could not be processed

Cause: Incoming message {0} could not be processed

Action: Please ensure that Human-Workflow Mailer is correctly configured also ensure that the response message is not corrupted
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10351: Underlying SDPMESSAGING layer could not send notification.

Cause: Underlying SDPMESSAGING layer could not send {0} Notification(MessageId:{1}) to {2}.

Action: Possible causes : SDPMessaging Driver not configured; Invalid 'To' Address; Email server/Messaging gateway is down; using IP address as part of email id insted of domain name;
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10352: Actionable Email has been responded from a different account.

Cause: Actionable Email had been sent to {0}, but received response from {1}.

Action: Actionable notifications should be responded from the same email account to which it was sent.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10353: Could not register/un register/fetch spam sources

Cause: Could not register/un register/fetch spam sources: {0}

Action: Possible cause : Invalid address is being registered/unregistered
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10500: Illegal Action name

Cause: Illegal Action name "{0}"

Action: Unsupported action by name "{0}"
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10501: Illegal argument

Cause: Illegal argument

Action: This is because an unexpected value, possibly null, was passed as an argument. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10502: Could not get Application role grantees

Cause: Failed to get Grantees to Application role "{0}" for application identified by "{1}"

Action: Check if the application role exists and has grantees in the repository associated with the application. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10503: Could not get granted roles to Application role

Cause: Failed to get Granted roles to Application role "{0}" for application identified by "{1}"

Action: Check if the application role exists and has granted roles in the repository associated with the application. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10504: Identity "{0}" membership in group "{1}" in configuration "{2}" could not be checked.

Cause: Error in checking membership of identity "{0}" in group "{1}" in configuration "{2}".

Action: Please make sure that both the identity name and group name are valid and exist in the repository. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10505: Service "{0}" in configuration "{1}" could not be initialized.

Cause: Error in initializing service "{0}" in configuration "{1}".

Action: Please make sure that identity service configuration is well formed and correct. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10506: Cannot get roles

Cause: Cannot get roles for identity "{0}" through configuration "{1}"

Action: The underlying APIs threw an exception. Check if the repository is configured properly and available. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10507: Only SSO authentication allowed.

Cause: Only SSO based authentication is allowed.

Action: Refer workflow configurations to change this policy. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10508: Error invoking remote service method.

Cause: Error occurred while invoking the remote position service method "{0}" for id "{1}"

Action: Ensure that a remote position service provider is configured correctly, the service is accessible and is active. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10509: User not found

Cause: User "{0}" is not found in configuration "{1}"

Action: Check if the user exists in the repository specified by the configurations. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10510: Application role not found

Cause: Application role "{0}" could not be found for application identified by "{1}"

Action: Check if the application role exists in the repository associated with the application. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10511: Group not found

Cause: Group "{0}" is not found in configuration "{1}"

Action: Check if the group exists in the repository specified by the configurations. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10512: Cannot get application role "{0}" for application identified by "{1}"

Cause: Cannot get role "{0}" from configuration "{1}"

Action: Check if the application role exists in the repository associated with the application. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10513: Cannot get application roles from application identified by "{0}"

Cause: An error occured while getting application roles from application identified by "{0}"

Action: The underlying APIs threw an exception. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10514: Cannot get group

Cause: Cannot get group "{0}" for configuration "{1}"

Action: The underlying APIs threw an exception. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10515: Cannot get groups

Cause: An error occured while getting groups from configuration "{0}"

Action: The underlying APIs threw an exception. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10516: Cannot find user

Cause: An error occured while getting user "{0}" from configuration "{1}"

Action: Check if the user exists in the repository specified by the configurations. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10517: Cannot get users

Cause: An error occured while getting users from configuration "{0}"

Action: The underlying APIs threw an exception. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10518: Failed to load Identity Service Configuration

Cause: An error occured while loading configurations from "{0}"

Action: Ensure that the identity service configurations are well formed and correct. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10520: Invalid application role name

Cause: Invalid application role name "{0}"

Action: Specify a valid application role name. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10521: Invalid group name

Cause: Invalid group name "{0}"

Action: Specify a valid role name. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10522: Manager with title "{0}" not found.

Cause: No manager with title "{0}" in management chain for user "{1}" in configuration "{2}"

Action: Given title "{0}" was not found among management chain for specified user "{1}" in configuration "{2}"
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10523: Hierarchy Provider "{0}" could not be loaded correctly.

Cause: Error occured while loading configured hierarhcy provider "{0}", in the identity service configuration.

Action: Check the log file for erros, check hierarchy service provider "{0}" configurations and make sure provider service is accessible and functional.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10528: Identity Service Authentication failure

Cause: Identity Service Authentication failure

Action: Either the user name or password are incorrect. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10536: Identity service provider not found

Cause: Identity service provider not found

Action: Ensure that a provider corresponding to the operation being performed is configured. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10537: user locale not found

Cause: user locale not found

Action: Ensure that the user locale is passed while calling the operation. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10540: Cannot find specified user in management chain

Cause: Cannot find specified user "{0}" in management chain for user "{1}" in configuration "{2}"

Action: User "{0}" is not in management chain for user "{1}" in configuration "{2}".
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10541: Cannot find context "{0}" in JPS configuration

Cause: Cannot find context "{0}" in JPS configuration

Action: Ensure that the JPS configuration file is well formed and has the specified context. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10542: Cannot set context "{0}".

Cause: Cannot set context "{0}".

Action: Ensure that the JPS configuration file is well formed and has the specified context. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10543: Unsupported filter

Cause: Specified search filter is unsupported or contains error.

Action: Correct the search filter. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10546: Unsupported attribute

Cause: Attribute "{0}" is not supported

Action: Ensure that the attribute is not null. Refer to the documentation for supported attributes. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10551: Custom Identity Service class cannot be loaded

Cause: Identity Service cannot load "{0}" class

Action: Check whether the file "{0}" in the classpath. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10555: Identity Service Configuration error

Cause: Identity Service Configuration has error

Action: Please refer to the identity service configuration guidlines and correct the Identity Service configurations. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10557: Error in identity service XPath extension function ora:getManager

Cause: Error in executing identity service XPath extension function ora:getManager for user name "{0}" in configuration "{1}".

Action: Please make sure that the user name is valid and exists in the repository and is associated with a manager. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10558: Error in identity service XPath extension function ora:getUserProperty

Cause: Error in executing identity service XPath extension function ora:getUserProperty for property "{0}" for user name "{1}" for configuration "{2}".

Action: Please make sure that the user name is valid and exists in the repository. Also ensure that the property has been defined for the user. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10559: Error in identity service XPath extension function ora:getGroupProperty

Cause: Error in executing identity service XPath extension function ora:getGroupProperty for property "{0}" for group name "{1}" for configuration "{2}".

Action: Please make sure that the group name is valid and exists in the repository. Also ensure that the property has been defined for the group. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10560: Error in identity service XPath extension function ora:lookupUser

Cause: Error in executing identity service XPath extension function ora:lookupUser for user name "{0}" in configuration "{1}".

Action: Please make sure that the user name is valid and exists in the repository. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10561: Error in identity service XPath extension function ora:lookupGroup

Cause: Error in executing identity service XPath extension function ora:lookupGroup for group name "{0}" in configuration "{1}".

Action: Please make sure that the group name is valid and exists in the repository. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10562: Error in identity service XPath extension function ora:isUserInRole

Cause: Error in executing identity service XPath extension function ora:isUserInRole for user "{0}" and group "{1}" in configuration "{2}".

Action: Please make sure that both the user name and group name are valid and exist in the repository. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10563: Error in identity service XPath extension function ora:getReportees

Cause: Error in executing identity service XPath extension function ora:getReportees for user name "{0}" for configuration "{1}".

Action: Please make sure that the user name is valid and exists in the repository. Also ensure that reportees to this user exist. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10564: Error in identity service XPath extension function ora:getUsersInGroup

Cause: Error in executing identity service XPath extension function ora:getUsersInGroup for group name "{0}" in configuration "{1}".

Action: Please make sure that the group name is valid and exists in the repository. Also ensure that users have been enlisted as participants to this group. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10565: Error in identity service XPath extension function ora:getUserRoles

Cause: Error in executing identity service XPath extension function ora:getUserRoles for user name "{0}" in configuration "{1}".

Action: Please make sure that the user name is valid and exists in the repository. Also ensure that roles have been granted to this user. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10566: Error in identity service XPath extension function ora:getDefaultRealmName

Cause: Error in executing identity service XPath extension function ora:getDefaultRealmName.

Action: Ensure that a default configuration exists. Irrespective of the number of configurations, one must be defined as default. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10567: Error in identity service XPath extension function ora:getSupportedRealms

Cause: Error in executing identity service XPath extension function ora:getDefaultRealmName.

Action: Ensure that the configurations are correct. Please check the exception stack trace for the reasons. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10575: Provider is not defined in configuration.

Cause: Provider "{0}" is not defined in configuration "{1}".

Action: Configure provider in configuration file. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10576: Configuration already exists

Cause: Configuration "{0}" already exists.

Action: Two or more configurations have the same name. Specify a different name for the configurations. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10577: Default configuration is not defined

Cause: Default configuration is not defined in configuration file "{0}".

Action: Specify default configuration in the file "{0}". Irrespective of the number of configurations, one should always be marked as default. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10578: More than one default configurations are defined

Cause: More than default configurations are defined in configuration file "{0}".

Action: There can be only one dafault. Specify only one default configuration in configuration file "{0}". Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10579: Name is not defined for one of configurations

Cause: Name is not specified for one of configurations in configuration file "{0}".

Action: Specify name for each configuration if few configurations are defined in configuration file "{0}". Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10580: Identity Service Extension name is already defined earlier in the identity service configuration

Cause: Identity Service Extension name "{0}" is already defined earlier in the identity service configuration.

Action: Make sure the extension name is unique and defined only once in the identity service configuration file. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10581: Service Provider {0} invocation error

Cause: Service Provider name "{0}" could not invoke method {1}.

Action: This errors occurs when service provider {0} is not avalable or not configured in the identity configuration file.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10584: Identity Service wsif error.

Cause: {0} has wsif error in method {1} for soap message: "{2}".

Action: Ensure that the soap message is properly formed and has all necessary attributes and elements. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10585: Service error.

Cause: Internal Error; Service error occurs in {0} in method {1}.

Action: Refer to the log file that is configured for oracle.soa.services.identity for more details on this error and contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10586: Could not get grantees for "{0}" in configuration "{1}".

Cause: Error in getting grantees for "{0}" in configuration "{1}".

Action: Ensure that a group with the given name exists and has grantees. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10587: Error in getting owners for "{0}" in configuration "{1}".

Cause: Error occured in getting owners for "{0}" in configuration "{1}".

Action: Ensure that the group name is valid and has associated owners. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10588: Error in getting owned groups for "{0}" in configuration "{1}".

Cause: Error occured in getting owned groups for "{0}" in configuration "{1}".

Action: Ensure that the identity name is valid and owns groups. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10589: Manager "{0}" not found for user "{1}" in configuration "{2}".

Cause: Manager with name "{0}" was not found for user "{1}" in configuration "{2}".

Action: Ensure that a user with the given name exists and is a manager for the given user. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10590: Manager name could not be resolved for "{0}" in configuration "{1}".

Cause: Error in resolving manager name for user "{0}" in configuration "{1}".

Action: Ensure that a user with the given name exists and has a manager. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10591: Could not get reportees for "{0}" in configuration "{1}".

Cause: Error in getting reportees for "{0}" in configuration "{1}".

Action: Ensure that a user with the given name exists and has reportees. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10592: Identity Service soap error.

Cause: {0} encountered soap error in method {1} for with fault "{2}".

Action: Ensure that the soap message is properly formed and has all necessary attributes and elements. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10593: Cannot find application "{0}".

Cause: Cannot find specified application name "{0}" in policy store.

Action: Check if the specified application "{0}" exists in policy store. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10597: Attempt to execute privileged action.

Cause: An attempt to execute a privileged action was made.

Action: Ensure that the codebase being used has the necessary permissions and privileges. If not, grant the same in the application's policy file. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10598: Identity "{0}" in configuration "{1}" is not of a supported type.

Cause: Unsupported identity type for identity "{0}" in configuration "{1}".

Action: Ensure that a identity with the given name exists and is of a supported type. Refer to the documnentation for all supported identity types. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10599: Role name "{0}" in configuration "{1}" could not be resolved.

Cause: Error in resolving role name "{0}" in configuration "{1}".

Action: Ensure that a role with the given name exists. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10600: Reports Error.

Cause: A problem occurred while processing reports data. {0}

Action: Please examine the log file to determine the problem.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10601: JMS connection factory lookup failed

Cause: The JMS connection factory lookup failed. The related reporting data will not be published Please ensure the JNDI name {0) is valid.

Action: Please verify the JMS configuration.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10602: JMS connection setup failed

Cause: A problem occurred while setting up a connection to the JMS Destination {0} using the connection factory {1}.

Action: Please verify the JMS configuration as well as the error to determine the problem.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10603: JMS publish failed

Cause: An error occurred while publishing reporting data to the JMS destination "{0}".

Action: Please verify the JMS destination is valid.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10604: JMS destination lookup failed

Cause: The JMS destination lookup failed. The related reporting data will not be published Please ensure the JNDI name {0) is valid.

Action: Please configure the JMS Destination or correct its JNDI name.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10605: Data Publisher failed.

Cause: The Reporting Data Publisher {0} of type {1} failed.

Action: Please examine the log file for more details.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10606: Invalid Variable Target.

Cause: The variable target {0} used in sensor {1} is invalid.

Action: Please make sure the variable target is correct by validating the variable name as well as the part and xpath query if any was provided.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10607: Sensor Initialization Error.

Cause: An error occurred while initializing the {0} sensor.

Action: Please correct the problem and reinitialize the business process.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10608: Sensor Data Capture Error.

Cause: An error occurred while gathering data for the {0} sensor. The related reporting data might not have been published.

Action: Please examine the log file and correct the problem.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10609: Invalid Adapter Namespace.

Cause: An error occurred while gathering reporting data for the {0} adapter sensor. The {1} namespace is not a recognized adapter namespace.

Action: Please provide a valid header variable that is defined in the appropriate namespace.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10610: Invalid Adapter Header Variable.

Cause: An error occurred while gathering reporting data for the {0} adapter sensor. The header variable {1} could not be found in the BPEL process definition.

Action: Please ensure the header variable provided in the sensor definition file exists in the BPEL process.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10611: JMS connection cleanup failed

Cause: A problem occurred while releasing the JNDI resources used to publish to the destination {0}.

Action: Please verify the JMS configuration as well as the error to determine the problem.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10612: Data Router failed.

Cause: The Reporting Data Publisher {0} of type {1} failed.

Action: Please examine the log file for more details.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10613: Creation of Sensor Registry failed.

Cause: Creation of the Sensor Registry failed.

Action: Please examine the log file for more details.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10614: Creation of Reports Schema Publisher failed.

Cause: Creation of the Reports Schema Publisherfailed.

Action: Please examine the log file for more details.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10615: Load of sensors into Sensor Registry failed.

Cause: The Sensor Registry failed to load sensors for process {0}-{1}.

Action: Please check the sensor definitions and examine the log file for more details.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10616: Import of sensors failed.

Cause: The Sensor Registry failed to import sensors for process {0}-{1}.

Action: Please check the sensor definitions and examine the log file for more details.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10617: Import of sensor actons failed.

Cause: The Sensor Registry failed to import sensor actions for process {0}-{1}.

Action: Please check the sensor action definitions and examine the log file for more details.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10618: Import of SLA's failed.

Cause: The Sensor Registry failed to import SLA's for process {0}-{1}.

Action: Please check the SLA properties in the deployment descriptor and examine the log file for more details.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10619: Sensor validation failed.

Cause: The Sensor Registry failed to validate the sensor {2} for process {0}-{1}.

Action: Please revisit the definition of the sensor and examine the log file for more details.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10620: Sensor Action validation failed.

Cause: The Sensor Registry failed to validate the sensor action {2} for process {0}-{1}.

Action: Please revisit the definition of the sensor action and examine the log file for more details.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10621: Data publisher creation failed.

Cause: The Sensor Agency encountered an error while trying to instantiate {0}.

Action: Please ensure the specified Data Publisher class and all of its dependencies exist in the system or process classpath.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10622: Sensors not supported.

Cause: Sensors are not supported on this application server platform.

Action: If sensor functionality is required, please switch to a supported platform.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10623: Sensors not supported.

Cause: Sensors are not supported on this database platform.

Action: If sensor functionality is required, please switch to a supported platform.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10700: Infrastructure services not enabled

Cause: The infrastructure feature for the domain has not been enabled.

Action: This is an irrecoverable error with installation.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10701: Server connection failure

Cause: Failed to connect to the PCBPEL server.

Action: Please check that the PCBPEL server is running.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10702: PCBPEL Server domain authentication enabled.

Cause: PCBPEL Server domain authentication has been enabled, need to turn it off.

Action: Please check if PCBPEL server has domain authentication enabled. Please look for property "domain-auth-enabled" in the file collaxa-config.xml and turn it off.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10703: BPEL Archive could not be found at the specified location.

Cause: BPEL Archive name or location is incorrect.

Action: Please check the name of the BPEL archive and its location.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10704: jndi.properties could not be found in the classpath.

Cause: jndi.properties could not be found in the classpath.

Action: Please ensure that jndi.properties is in the classpath.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10705: Authentication failure.

Cause: The user name password combination is not authenticated for deployment.{0}

Action: Please ensure that the password is correct and user has deployment previleges.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10706: Server Internal Error.

Cause: Server error.{0}

Action: Please report this error to the administrator.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10707: Connection to server refused

Cause: Server connection refused.

Action: Please ensure that the server is up and running.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10708: Problem with Network Connection to server

Cause: The network connection to the server is slow. The request has already been sent to the server. Please check the console to see if the process is already deployed.

Action: The request was sent to the server. The response from server is taking longer than expected. Please check the console to see if the process is already deployed.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-10709: Error while deploying payload jsp

Cause: Deploying payload jsp on paltform {0} not supported

Action: Please ensure that server platform is supported
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30001: Error in reading routing slip

Cause: Error while reading routing slip {0}. This routing slip is used by workflow {1}

Action: Make sure that the routing slip is available at the specified URL.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30002: Error in evaluating routing slip

Cause: Error while evaluating the routing slip {0}. This routing slip is used by workflow {1}

Action: Check the underlying exception and correct the error in the routing slip.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30003: Invalid routing slip

Cause: The routing slip at {0} does not conform to the routing slip XML schema definition. The errors are {1}

Action: Make sure that the routing slip conforms to the routing slip XML schema definition.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30004: Error in validating routing slip

Cause: The routing slip at {0} could not be validated against the routing slip XML schema definition

Action: Make sure that the routing slip is available at the specified URL.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30005: Error in setting task attributes

Cause: The task attribute {2} could not be set for the task {0}. The task belongs to the workflow {1}

Action: This error is likely because of invalid user/group being set as {2}. Make sure that the user/group is valid.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30006: Error in getting manager of user

Cause: The manager of user {2} could not be retrieved for the task {0}. The task belongs to the workflow {1}

Action: Make sure that user {2} is valid and that the manager for user {2} is defined in the user directory.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30007: Error in creating task from WSIF Java Web Services message

Cause: The task object could not be created from the message passed to Web Services

Action: Check the Web Service input for correctness. The input could also be validated against XML schema definition that describes the operation input.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30008: Error in creating parameters from WSIF Java Web Services message

Cause: The {0} could not be created because expected element {1} is not be found in the element {2} in the parameter passed to Web Services

Action: Check the Web Service input for correctness. The input could also be validated against XML schema definition that describes the operation input.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30009: Parameters in Web Services message is invalid

Cause: The parameter {0} is invalid as expected type is {1}, but received value {2} in the parameter passed to WSIF Java Web Services

Action: Check the Web Service input for correctness. The input could also be validated against XML schema definition that describes the operation input.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30010: Error in creating reply message for Web Services

Cause: Error in creating reply message for Web Services

Action: The Web Service input could be invalid causing this exception. Check the Web Service input for correctness. The input could also be validated against XML schema definition that describes the operation input. It being valid, this is a system error.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30011: Invalid workflow configuration

Cause: The workflow configuration at {0} could not be read. The workflow configuration is associated with workflow {1}

Action: Make sure that the workflow configuration is available at the specified URL and that it is a valid XML document.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30012: Invalid workflow configuration

Cause: The workflow configuration at {0} does not conform to the workflow configuration XML schema definition. The workflow configuration is associated with workflow {1}. The errors are {2}

Action: Make sure that the workflow configuration conforms to the workflow configuration XML schema definition.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30013: Error in validating workflow configuration

Cause: The workflow configuration at {0} could not be validated against the workflow configuration XML schema definition. The workflow configuration is associated with workflow {1}

Action: Make sure that the workflow configuration is available at the specified URL. If available check the underlying exception and correct the error.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30014: Error in retrieving previous approvers of task

Cause: The previous approvers of task {0} could not be retrieved. The task is associated with workflow {1}

Action: Make sure that the task for which the previous approvers are retreived is valid. It being valid, this is a system error.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30015: Error in posting message to BPEL process instance

Cause: Error in posting message to BPEL process instance {1} for callback operation {2}. The task is associated with workflow {0}

Action: This could be caused if the BPEL instance is terminated. It is is not, this is possibly a system error.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30016: Error in invoking routing slip callbacks

Cause: Error in invoking routing slip Java callback {3} for task {1}. The task is associated with workflow {0}

Action: Make sure that the routing slip callback class is specified correctly without any errors. The class name should be fully qualified. Also make sure that the class and its dependencies are available in the classpath.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30017: Invalid task definition

Cause: The task definition at {0} could not be read. The task definition is associated with workflow {1}

Action: Make sure that the task definition is available at the specified URL and that it is a valid XML document.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30018: Invalid task definition

Cause: The task definition at {0} does not conform to the task definition XML schema definition. The task definition is associated with workflow {1}. The errors are {2}

Action: Make sure that the task definition conforms to the task definition XML schema definition.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30019: Error in validating task definition

Cause: The task definition at {0} could not be validated against the task definition XML schema definition. The task definition is associated with workflow {1}

Action: Make sure that the task definition is available at the specified URL and that it is a valid XML document.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30020: Invalid workflow task display configuration

Cause: The workflow task display configuration at {0} could not be read. The workflow task display configuration is associated with workflow {1}

Action: Make sure that the workflow task display configuration is available at the specified URL and that it is a valid XML document.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30021: Invalid workflow task display configuration

Cause: The workflow task display configuration at {0} does not conform to the workflow task display configuration XML schema definition. The workflow task display configuration is associated with workflow {1}. The errors are {2}

Action: Make sure that the workflow task display configuration conforms to the workflow task display configuration XML schema definition.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30022: Error in validating workflow task display configuration

Cause: The workflow task display configuration at {0} could not be validated against the workflow task display configuration XML schema definition. The workflow task display configuration is associated with workflow {1}

Action: Make sure that the workflow task display configuration is available at {1} and that it conforms to the workflow task display configuration XML schema definition.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30023: Internal workflow error

Cause: An internal workflow error occured

Action: Refer to the log file that is configured for oracle.soa.services.workflow.* for more details on this error and contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30024: The task is already modified

Cause: The task was modified before the current action could be performed.

Action: Refresh the task and perform the action again if the action is still relevant on the refreshed task.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30025: Error unmarshalling from org.w3c.dom.Element to JAXB.

Cause: Internal Error : Attempt to unmarshall element {0} using JAXB context {1} resulted in error: {2}

Action: Refer to the log file that is configured for oracle.soa.services.workflow.* for more details on this error and contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30026: Error creating soap message.

Cause: Error in creating soap message during Web service invocation of operation {1} in {0}

Action: Refer to the log file that is configured for oracle.soa.services.workflow.* for more details on this error and contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30028: Invalid configuration file workflow-config.xml

Cause: The configuration file workflow-config.xml not be read.

Action: Make sure that the configuration file workflow-config.xml is available and is a valid XML document.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30029: Error in invoking task service

Cause: An client side error occured in invoking the task service.

Action: Verify that the connection information of the server is correct.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30030: Error in invoking task service

Cause: An client side error occured in invoking the task service operation {0}.

Action: Verify that the connection information of the server is correct.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30031: Failed to query flexfield mappings

Cause: Task metadata service was unable to query flexfield mappings for task definition: {0}

Action: Check the underlying error. Verify that the workflow datasource is correctly configured, and that database server is available.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30032: Invalid task definition lookup

Cause: There is no task definition associated with the task definition ID {0}

Action: Verify the that the task definition ID is vaild.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30033: Invalid task metadata service invocation

Cause: Task metadata service operation was invoked with empty task definition ID.

Action: Make sure that the operation is invoked with a valid task definition ID
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30034: Invalid task display region parameter value

Cause: The task display region parameter value {0} is invalid when applied to task {1}.

Action: Make sure that the task display region parameter value is correct if it is an XPath expression
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30035: Push back not supported

Cause: Push back is not supported for the task {0} as there are no more users to push back the task to.

Action: This is an invalid operation on the task.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30036: Invalid action on workflow task or user does not have privilege to perform this action

Cause: Action {0} on task {1} cannot be performed by {2}

Action: Make sure that the action is valid with respect to the current state of the task or ensure that the user has privilege to perform this action on the workflow task
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30037: Error in invoking task metadata service

Cause: An client side error occured in invoking the task metadata service.

Action: Verify that the connection information of the server is correct.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30038: Error in evaluating task service XPath extension function

Cause: Error in evaluating task service XPath extension function {1} against task {1}

Action: It is possible that the extension function is not valid against the particular task. Check the error to correct the problem.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30039: Error in routing slip

Cause: The type of the first participant in the routing slip is expected to be Participant, but it is {1}. The routing slip is associated with task {0}

Action: Check the routing slip and correct the error.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30040: Error in routing slip

Cause: Adhoc routing can be performed only when the isAdhocSupported flag is set to true in the routing slip participants or the current participant is adhoc, but it is {1}. The routing slip is associated with task {0}

Action: Adhoc routing is an invalid action at the current state of the task.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30043: Error in evaluating workflow service XPath extension function

Cause: Error in evaluating task service XPath extension function {1}

Action: Check the error stack and fix the cause of the error.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30044: Error in workflow service Web service operation invocation

Cause: Error in workflow service Web service operation invocation. The error is {0}.

Action: Verify that the SOAP connection information for the server is correct.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30045: Error in invoking workflow state machine decision service.

Cause: Error occured when invoking workflow routing state machine decisions service {0}. The error is {1}.

Action: Check the error underlying error. Verfiy that the composite and workflow componentType are correctly configured, and that the correct decisionServiceComponentName is specified in the workflow definition.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30046: Error in routing slip

Cause: The expiration specified in the routing slip could not be evaluated. The error is {0}. The routing slip is associated with the task definition {1}

Action: Make sure that the expiration duration is specified correctly. The value should conform to XML duration specifications
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30047: Error in routing slip

Cause: Error in evaluating parameter {0} in the routing slip. The error is {1}. The routing slip is associated with the task definition {2}

Action: Make sure that the parameter {0} is specified correctly.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30048: Error in routing slip

Cause: An error occured during evaluating escalation policy in the routing slip. The error is {0}. The routing slip is associated with the task definition {1}

Action: Make sure that the escalation policy is specified correctly.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30049: Error in routing slip

Cause: The task is assigned to an invalid user {0} in realm {1}. The routing slip is associated with the task definition {2}

Action: Verify that the user is specified correctly in the routing slip in the task definition
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30050: Error in routing slip

Cause: The task is assigned to an invalid group {0} in realm {1}. The routing slip is associated with the task definition {2}

Action: Verify that the group is specified correctly in the routing slip in the task definition
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30051: Error in routing slip

Cause: An error occured during evaluating renewal policy in the routing slip. The error is {0}. The routing slip is associated with the task definition {1}

Action: Make sure that the renewal policy is specified correctly.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30052: Error in routing slip

Cause: An error occured in evaluating the assignees of the task from the routing slip for participant {0}. The error is {1}. The routing slip is associated with the task definition {2}

Action: Check the routing slip in the task definition and correct the error.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30053: System error in evaluating routing slip

Cause: A system error occured in evaluating the routing slip. The error is {0}. The routing slip is associated with the task definition {1}

Action: Refer to the log file that is configured for oracle.soa.services.workflow.task for more details on this error and contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30054: Error in evaluating assignment service in routing slip

Cause: Cannot instantiate assignment service {0}. The error is {1}. The assignment service is used in the routing slip that is associated with the task definition {2}

Action: Check the routing slip and correct the error. Make sure that the assignment service is available in the classpath of the soa-infra application.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30055: Error in evaluating assignment service in routing slip

Cause: Cannot create property bag for assignment service. The error is {0}. The assignment service is used in the routing slip that is associated with the task definition {1}

Action: Check the routing slip and correct the error in specifying the properties for the assignment service.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30056: Error in escalating the task on expiration

Cause: The task has expired and the system could not compute the management chain from user {0} upto levels {1} upto title {2} to identify the next user to escalate the task to

Action: Make sure that the escalation policy is specified correctly. Also verify that the users are seeded correctly to compute the management chain.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30057: Error in evaluating management chain participant

Cause: Could not compute the management chain from user {0} upto levels {1} upto title {2}. The management chian is used in the routing slip that is associated with the task definition {3}

Action: Verify that the users are seeded correctly to compute the management chain.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30058: Error in state machine rules return parameter

Cause: The forwarding rule specifies goto, but does not specify the logical name of the participant to goto. The task is associated with the task definition {0}

Action: Check the state machine rule definitions. Ensure that the rules are setting a participant logical name in the GOTO action.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30059: Error in forwarding rules return parameter

Cause: The forwarding rule specifies goto, but the logical name of the participant {0} to goto is not a valid name. The task is associated with the task definition {0}

Action: Check the state machine rule definitions. Ensure that the rules aare stting a valid logical participant name in the GOTO action.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30060: Error in task assignment rules evaluation

Cause: Error in task assignment rules evaluation for user {0}. The error is {1}

Action: Make sure that the rules specified for user {0} are valid.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30061: Cyclic assignment during task assignment rules evaluation

Cause: During task assignment rules evaluation, there is a cyclic assignment involving user {0}.

Action: Correct the assignment rules to avoid this error.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30062: Error in task assignment rules evaluation

Cause: Error in task assignment rules evaluation for group {0}. The error is {1}

Action: Make sure that the rules specified for group {0} are valid.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30063: Cyclic assignment during task assignment rules evaluation

Cause: During task assignment rules evaluation, there is a cyclic assignment involving group {0}.

Action: Correct the assignment rules to avoid this error.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30064: Error in routing slip

Cause: The task is assigned to an invalid application role {0} in application context {1}. The routing slip is associated with the task definition {2}

Action: Verify that the application role is specified correctly in the routing slip in the task definition
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30065: Error in task definition

Cause: Error in evaluating parameter {0} in the task definition. The error is {1}. The task definition {2}

Action: Make sure that the parameter {0} is specified correctly in the task definition.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30066: Invalid arguments to requestInfoForTask operation

Cause: Invalid arguments to requestInfoForTask operation. The reapproval assignees parameter must contain one or more valid user, group or role.

Action: Correct the error in the client usage.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30067: Invalid access to task

Cause: The user does not have access to the task.

Action: Check that the task is being accessed in an authenticated context and that you are involved in this task in some manner.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30068: Invalid task definition ID or namespace

Cause: There is no task definition with the provided ID {0}. This ID is either the ID of the task definition or the namespace of the task definition

Action: Verify the that the task definition ID is vaild.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30069: Task definition not found using namespace

Cause: There is no active SCA composite with the referenced task definition. The provided task definition namespace is {0}

Action: Verify the that the composite containing the task definition is active.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30070: Assignee Time Distribution Statistic Service Internal error.

Cause: An internal error occurred in the Assignee Time Distribution Statistic Service. Task assignment statistic is not recorded for {0} for the operation {1}. This may lead to loss of some Task assignment statistic data

Action: Check the underlying exception and correct the error. Contact Oracle Support Services if the error persists.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30071: No workflow admin user seeded

Cause: There must be atleast one workflow admin user seeded in the system.

Action: Seed an workflow admin user or grant the workflow admin role to an existing user.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30072: Task owner user not seeded

Cause: Task owner {0} is not found in realm {1}. This task is associated with task definition {2}

Action: Either set a seeded owner or seed this owner who is not found.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30073: Task owner group not seeded

Cause: Task owner {0} is not found in realm {1}. This task is associated with task definition {2}

Action: Either set a seeded owner or seed this owner who is not found.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30074: There is no user to escalate the task to

Cause: There is no user to escalate the task to. The task is assigned to user {0}. This task is associated with task definition {1}

Action: Ensure that this user has a manager to escalate the task to.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30075: Invalid task attachment name

Cause: The task attachment {0} does not exist

Action: Ensure that the task attachment name is valid.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30076: ToDo task cannot be created as a sub task for a task that is not in the assigned state

Cause: Parent task {0} is not assigned. ToDo task cannot be created as a sub task for a task that is not in the assigned state.

Action: Ensure that the ToDo task is created for an assigned task.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30077: Error in invoking Notification callbacks

Cause: Error in invoking routing slip Java callback {3} for task {1}. The task is associated with workflow {0}

Action: Make sure that the Notification callback class is specified correctly without any errors. The class name should be fully qualified. Also make sure that the class and its dependencies are available in the classpath.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30078: Error in evaluating the restricted assignment service in routing slip

Cause: Cannot instantiate restricted assignment service {0}. The error is {1}. The restricted assignment service is used in the routing slip that is associated with the task definition {2}

Action: Check the routing slip and correct the error. Make sure that the restricted assignment service is available in the classpath of the soa-infra application.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30079: Attempt to reassign/route to an invalid assignee.

Cause: The assignee {0} in realm {1} for task definition {2} is not permitted as per the restricted assignment callback configured by the administrator.}

Action: Check the routing slip and correct the error. Make sure that restricted assignees are not used in the task definition.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30080: Task owner role not seeded

Cause: Task owner {0} is not found in application {1} and realm {2}. This task is associated with task definition {3}

Action: Either set a seeded owner or seed this owner who is not found.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30081: Workflow Service Engine callback to SOA mesh failed.

Cause: Callback operation {0} from {1} to {2} failed with error: {3}

Action: Check the underlying exception. Ensure that the SOA composite is configured correctly.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30082: WorkflowServiceEngine request to another component failed.

Cause: Request operation {0} from {1} to {2} failed with Business Fault: {3}

Action: Check the underlying fault. Check target SOA component for cause.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30083: WorkflowServiceEngine request to SOA mesh failed.

Cause: Request operation {0} from {1} to {2} failed with error: {3}

Action: Check the underlying exception. Ensure that the SOA composite is configured correctly.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30085: Missing task metadata identifiers in task object.

Cause: Task metadata corresponding to a task is identified by either the taskDefinitionId or taskDefinitionURI (deprecated in 11). Atleast one of those task elements should be set.

Action: Set either the taskDefinitionId or taskDefinitionURI in the task instance.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30086: No duration specified.

Cause: Invalid task duration: {0}.

Action: Specify a valid duration.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30087: Operation not supported in disconnected mode.

Cause: The attempted operation cannot be performed whilst disconnected from the server.

Action: Connect to the server before attempting the operation.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30088: No task definitions found matching specified namespace and version.

Cause: No task definitions found with task definition namespace {0} and composite version {1}.

Action: Check that the specified task definition namespace and composite version are correct.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30089: No active composite found corresponding to specified namespace.

Cause: No active composite found containing a task component with definition namespace of {0}.

Action: Specify a composite version to query by, or make a composite version active.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30090: Can not compute management chain list.

Cause: The management chain can not be completely computed because the starting point in the management chain is not a single user. Management chain can not be computed from group(s), application role(s) and/or list of users. This exception is related to task definition {0}.

Action: Correct the errors in workflow process modeling or the rule that returned the management chain list parameters.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30091: Can not restart the task

Cause: Can not restart the task {0} in {1} state either because it is not a root task or the state is invalid for restart

Action: Check the error stack and fix the cause of the error. Contact Oracle Support Services if error the error persists.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30092: Error in invoking attachment callback

Cause: Error in invoking attachment callback {2} for task {1}. The task is associated with workflow {0}

Action: Make sure that the attachment callback class is specified correctly without any errors. The class name should be fully qualified. Also make sure that the class and its dependencies are available in the classpath.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30093: Error in invoking comment callback

Cause: Error in invoking comment callback {2} for task {1}. The task is associated with workflow {0}

Action: Make sure that the comment callback class is specified correctly without any errors. The class name should be fully qualified. Also make sure that the class and its dependencies are available in the classpath.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30094: Bulk update is not allowed for this Task.

Cause: This task expects the user to view task details before acting on it.

Action: Make sure that the task is approved/rejected from task details page. Also ensure that TaskService API which takes task Object as input is used instead of the API which takes taskID as input.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30095: User comments are expected for this Task.

Cause: This task expects the user to provide comments while acting on it.

Action: Make sure that the comments are provided while acting on this task.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30096: Can not reevaluate the task.

Cause: This task {0} does not belongs to a sequential or parallel participant.

Action: Check the error stack and fix the cause of the error. Contact Oracle Support Services if the error persists.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30097: Routing slip can not be reevaluated.

Cause: Current routing slip participant for the task {0} is not generated by a list builder.

Action: This task can not be reevaluated. Make sure the participant is generated using List builder.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30098: Error in task action validation

Cause: Error in validation task action {2} for task {1}.The task definition is associated with workflow {0}. The error(s) is/are: {3}

Action: Make sure the validation errors are corrected before invoking the task action.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30099: Error in invoking task validation callbacks

Cause: Error in invoking task validation Java callback {2} for task {1}. The task is associated with workflow {0}

Action: Make sure that the task validation callback class is specified correctly without any errors. The class name should be fully qualified. Also make sure that the class and its dependencies are available in the classpath.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30100: Error in setting Task Sequence Changes

Cause: Task has been modified. Mismatch on saving ad hoc changes for task with correlation Id {0}

Action: Refresh list to get current list of assignees and redo the changes.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30101: Invalid attribute label for flexfield mapping defined in task definition.

Cause: No attribute label named {0} for flexfield attribute {1} exists.

Action: Create an appropriate attribute label, or specify a different label in the task definition.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30102: Error in routing slip

Cause: The task is assigned to an invalid position {0} in application context {1}. The routing slip is associated with the task definition {2}

Action: Verify that the position is specified correctly in the routing slip in the task definition
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30103: Ruleset didn't return any results.

Cause: Ruleset {0} didn't return any results.

Action: Model the ruleset so that it returns a list builder specification.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30104: Ruleset returned different types of list builders.

Cause: Ruleset {0} returned different types of list builders.

Action: Ruleset results should all be of the same list builder type. Correct the ruleset.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30105: Ruleset returned unexpected list builder type.

Cause: Ruleset {0} returned list builder of type {2} when list builder of type {1} was expected.

Action: Correct the ruleset.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30106: Error setting starting point implicitly.

Cause: Starting Point not specified and Task Creator is same as UptoApprover: {0}

Action: Set the starting point explicitly to some one below the Upto Approver.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30107: Error fetching manager list using Hierarchy Provider.

Cause: Failed to walk up the hierarchy for principal: {0}

Action: Check Starting Point/Task Creator and Upto Approver values and Hierarchy Provider setup.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30108: Error NULL Hierarchy Principal provided.

Cause: Failed to fetch jobLevel for principal: NULL

Action: Check Hierarchy Provider setup.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30109: Error fetching jobLevel using Hierarchy Provider.

Cause: Failed to fetch jobLevel for principal: {0}

Action: Check Hierarchy Provider setup.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30110: Error walking up Hierarchy.

Cause: Failed to fetch upto approver for principal: {0}

Action: Check UptoApprover value in List Builder Specifications.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30111: Invalid user.

Cause: The task is assigned to an invalid user {0} in realm {1}.

Action: Assign to a valid user.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30112: Invalid group.

Cause: The task is assigned to an invalid group {0} in realm {1}

Action: Assign to a valid group.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30113: Invalid application role.

Cause: The task is assigned to an invalid application role {0} in application context {1}.

Action: Assign to a valid application role.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30114: Invalid position.

Cause: The task is assigned to an invalid application role {0} in application context {1}.

Action: Assign to a valid position.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30115: Error in invoking document callback

Cause: Error in invoking document callback {2} for task {1}. The task is associated with workflow {0}

Action: Make sure that the document callback class is specified correctly without any errors. The class name should be fully qualified. Also make sure that the class and its dependencies are available in the classpath.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30116: Invalid value of Levels.

Cause: The levels constraint for the Supervisory List Builder is not a postive integer: {0}

Action: Assign to a positive number for the levels parameter in the Supervisory List Builder Specification.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30117: Invalid value of Levels.

Cause: Both AtLeast and AtMost constraints for Job Level List Builder are not postive integers:, At Least {0}, At Most: {1}

Action: Assign positive integer values to one or both as required.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30118: Invalid value of Levels.

Cause: Both AtLeast and AtMost constraints for Position List Builder are not postive integers:, At Least {0}, At Most: {1}

Action: Assign positive integer values to one or both as required.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30119: Partial task update is not allowed

Cause: The task being updated is a partial task that was retrieved using query APIs. Such partial tasks cannot be directly used for update.

Action: Obtain the complete tasks using getTaskDetailsById before updating it.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30120: Invalid task document name

Cause: The task document {0} does not exist

Action: Ensure that the task document name is valid.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30121: Error in invoking document callback

Cause: Error in invoking document callback {2} for task {1}. The task is associated with workflow {0}

Action: Make sure that the document callback class is specified correctly without any errors. The class name should be fully qualified. Also make sure that the class and its dependencies are available in the classpath.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30122: Error while querying task document

Cause: Error while querying task document {0} for task {1} with version{2}

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30123: Error while deploying task metadata.

Cause: The task namespace {0} is already used as a template namespace.

Action: Check if the project you are deploying now is a template project. Please avoid deploying template projects.Please use a different namespace for the task definition to fix the problem or set the suffixNamespace flag to true.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30124: Error while deploying task metadata.

Cause: the template namespace {0} is already in use as a task namespace

Action: Check if a template project with namespace {0} was deployed earlier. Please avoid deploying template projects. Please use a different namespace for the current task definition to fix the problem.The task flow associated with the template project will not work with this project anymore if the namespace is changed.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30125: Attachment already exists.

Cause: Process attachment names are unique. Please delete the existing attachment with the same name and then try to add it.

Action: To add the attachment with the same name, delete the existing attachment and upload again
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30126: Position provider invalid or cont available.

Cause: Position provider could not be loaded, position list builder could not be used.

Action: Unable to load the position provider, please check the position provider configuration and make sure it is valid. Position list builder uses provider to get the hierarchy.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30251: Error while querying workflow task display

Cause: Error while querying workflow task display based on task metadata and application name

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30252: Error while inserting workflow task display

Cause: Error while inserting workflow task display

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30253: Error while updating workflow task display

Cause: Error while updating workflow task display.

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30254: Error while deleting workflow task display

Cause: Error while deleting workflow task display.

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30257: Error while Querying workflow task metadata

Cause: Error while Querying workflow task metadata

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30258: Error while inserting workflow task metadata

Cause: Error while inserting workflow task metadata

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30259: Error while updating workflow task metadata

Cause: Error while updating workflow task metadata {0}

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30260: Error while deleting workflow task metadata

Cause: Error while deleting workflow task metadata {0}

Action: Check the underlying exception and the database connection information.If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30261: The task namespace {0} is already in use by the task component {1}.

Cause: Task component target namespaces must be unique.

Action: Specify a different target namespace for this task component.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30265: Error while querying users which are on vacation

Cause: Error while querying users which are on vacation

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30266: Error while querying user vacation information

Cause: Error while querying user {0} vacation information

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30267: Error while inserting user vacation information

Cause: Error while inserting user {0} vacation information

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30268: Error while updating user vacation information

Cause: Error while updating user {0} vacation information

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30269: Error while deleting user vacation information

Cause: Error while deleting user {0} vacation information

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30274: Error while querying workflow message attributes

Cause: Error while querying workflow message attributes for task {0} with version {1}

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30275: Error while querying workflow task history

Cause: Error while querying workflow task history for task {0} with version{1}

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30276: Error while querying workflow task history

Cause: Error while querying workflow task history for task {0} with version{1}

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30277: Error while querying task attachment

Cause: Error while querying task attachment {0} for task {1} with version{2}

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30278: Error while inserting task

Cause: Error while inserting task {0}

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30279: Error while locking the task during update

Cause: Error while locking the task {0} during update

Action: The task is being updated by another user, merge and update the task later
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30280: Error while inserting task payload

Cause: Error while inserting task payload {0} for task {1}

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30281: Error while updating task payload

Cause: Error while updating task payload {0} for task {1}

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30282: Error while deleting data

Cause: Error while deleting data from table {0}

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30283: Error while querying task user comments

Cause: Error while querying task user comments for task {0} with version{1}

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30284: Error while querying task composite created time

Cause: Error while querying task composite created time for task {0}

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30291: Error while inserting task routing slip

Cause: Error while inserting task {1} routing slip

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30292: Error while locking the routing slip during update

Cause: Error while locking the routing slip during updateof routing slip for task {0}

Action: The task is being updated by another user, merge and update the task later
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30293: Attempt to update already deleted routing slip

Cause: Attempt to update already deleted routing slip for task {0}

Action: Refresh the task list by a new query.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30294: Error while updating routing slip

Cause: Error while updating routing slip for task {0}

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30295: Error while querying routing slip

Cause: Error while querying routing slip for task {0}

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30296: Error while deleting routing slip

Cause: Error while deleting routing slip for task {0}

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30297: Error while initializing persistency service

Cause: Error while initializing persistency service

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30298: Error during persistency service commit

Cause: Error during persistency service commit

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30299: Error during persistency service rollback

Cause: Error during persistency service rollback

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30300: Error while closing persistency service

Cause: Error while closing persistency service

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30301: Error while creating prepared statement in persistency service

Cause: Error while creating prepared statement for {0} in persistency service

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30302: Invalid join operator

Cause: Invalid join operator {0}

Action: Change the operator in the given predicate.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30303: Predicate join columns are null

Cause: Predicate join columns are null

Action: Specify valid, non null, join columns for the given prediate.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30304: Error while joining columns of different types in predicate

Cause: Error while joining columns of different types in predicate

Action: Joined columns are of different type, verify the types of columns in the predicate.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30305: Invalid value type in predicate

Cause: Invalid value type {0} in predicate

Action: Unrecognized value type specified in the predicate, pass the appropriate value type for the column.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30306: Transaction is open

Cause: Transaction is open

Action: Close the current transaction and then open a new one.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30307: Transaction is open

Cause: Transaction is open

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30308: Transaction is close

Cause: Transaction is close

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30312: Error while creating attribute label map

Cause: Error while creating attribute label map

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30313: Error while updating attribute label map

Cause: Error while updating attribute label map for {0}

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30314: Error while deleting attribute label map

Cause: Error while deleting attribute label map for {0}

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30315: Error while querying attribute label map

Cause: Error while querying attribute label map

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30316: Error while creating attribute usages

Cause: Error while creating attribute label usages for AttributeLabel type {0}

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30317: Error while deleting attribute usages

Cause: Error while deleting attribute label usages for AttributeLabel type {0}

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30318: Error while querying attribute usages

Cause: Error while querying attribute label usages

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30319: Error while inserting workflow task timer

Cause: Error while inserting workflow task timer {0}

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30320: Error while querying workflow task timer

Cause: Error while querying workflow task timer based on task metadata and application name

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30321: Error while deleting workflow task timer

Cause: Error while deleting workflow task timer {0}.

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30322: Error while querying workflow task

Cause: Error while querying workflow task {0}.

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30323: Error while inserting workflow task

Cause: Error while inserting workflow task {0}.

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30324: Error while updating workflow task

Cause: Error while deleting workflow task {0}.

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30325: Error while deleting workflow task

Cause: Error while updating workflow task timer {0}.

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30326: Current user does not have the WRITE privilege on task attribute: {1}

Cause: Current user {0} does not have WRITE privilege for {1} on task with taskId {2}

Action: Grant the WRITE access for the current user/role. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30327: Current user does not have the ADD privilege on task attribute: {1}

Cause: Current user {0} does not have ADD privilege for {1} on task with taskId {2}

Action: Grant the ADD access for the current user/role. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30328: Current user does not have the READ privilege on task attribute: {1}

Cause: Current user {0} does not have READ privilege for {1} on task with taskId {2}

Action: Grant the READ access for the current user/role. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30329: Error while querying workflow task assignment statistic

Cause: Error while querying workflow task assignment statistic {0}.

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30330: Error while inserting workflow task assignment statistic

Cause: Error while inserting workflow task assignment statistic {0}.

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30331: Error while updating workflow task assignment statistic

Cause: Error while deleting workflow task assignment statistic {0}.

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30332: Error while deleting workflow task

Cause: Error while updating workflow task timer {0}.

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30333: Error while Inserting Evidence

Cause: Insertion of task evidence : {0}, resulted in error : {1}

Action: Check Application server data source properties for BPEL-Workflow connections. Check schema and verify database connections. Ensure that a valid Evidence is being inserted by the worklist application.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30334: Error while Updating Evidence

Cause: Updation of task evidence : {0}, resulted in error : {1}

Action: Check Application server data source properties for BPEL-Workflow connections. Check schema and verify database connections
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30335: Error while Fetching Evidence

Cause: Querying for task evidence matching {0} condition, resulted in error : {1}

Action: Check Application server data source properties for BPEL-Workflow connections. Check schema and verify database connections
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30336: Error while Inserting Evidence Service data

Cause: Inserting into {0} table, resulted in error : {1}

Action: Check Application server data source properties for BPEL-Workflow connections. Check schema and verify database connections
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30337: Error while Updating Evidence Service data

Cause: Updating record(s) of {0} table, resulted in error : {1}

Action: Check Application server data source properties for BPEL-Workflow connections. Check schema and verify database connections
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30338: Error while Deleting Evidence Service data

Cause: Deleting record(s) from {0} table, resulted in error : {1}

Action: Check Application server data source properties for BPEL-Workflow connections. Check schema and verify database connections
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30339: Error while Fetching Evidence Service data

Cause: Fetching records from {0} table, resulted in error : {1}

Action: Check Application server data source properties for BPEL-Workflow connections. Check schema and verify database connections
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30340: Error while Inserting header properties data

Cause: Inserting into {0} table, resulted in error : {1}

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30341: Error while Deleting header properties data

Cause: Deleting from {0} table, resulted in error : {1}

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30342: Error while Fetching header properties data

Cause: Fetching records from {0} table, resulted in error : {1}

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30343: Error while Inserting rule dictionary data.

Cause: Inserting into {0} table, with dictionary {1}, package {2} resulted in error: {3}

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30344: Error while Deleting rule dictionary data.

Cause: Deleting from {0} table, with dictionary {1}, package {2} resulted in error: {3}

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30345: Error while Updating rule dictionary data.

Cause: Updating {0} table, with dictionary {1}, package {2} resulted in error: {3}

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30346: Error while Fectching rule dictionary data.

Cause: Fetching records from {0} table, with dictionary {1}, package {2} resulted in error: {3}

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30347: Cannot write dictionary with outstanding updates.

Cause: Dictionary {0}, package {1} has outstanding updates that must be committed.

Action: Commit all dictionary edits by calling update method on RuleDictionary before writing to database.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30348: Cannot update a read-only dictionary.

Cause: Dictionary {0}, package {1} is marked as 'read only' and cannot be updated in the database.

Action: Dictionaries can be marked as read-only or otherwise using the WFRuleDictionaryFinder class.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30349: Rule Dictionary name conflict.

Cause: A dictionary with the name {0} and package {1} already exists in the database.

Action: Specify a different name and/or package for the dictionary.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30350: Error while inserting approval group.

Cause: Inserting approval group {0} resulted in error: {1}.

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30351: Error while updating approval group.

Cause: Updating approval group {0} resulted in error: {1}.

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30352: Error while deleting approval group.

Cause: Deleting approval group {0} resulted in error: {1}.

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30353: Error while getting approval group.

Cause: Getting approval group {0} resulted in error: {1}.

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30354: Error while getting approval groups.

Cause: Getting approval groups with search string {0} and search type {1} resulted in error: {2}.

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30360: Error while inserting approval record.

Cause: Inserting approval record with task Id {0} and record ID {1} resulted in error: {2}.

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30361: Error while updating approval record.

Cause: Updating approval record with task Id {0}, subtask ID {1}, history version {2}, dimension instance ID {3}, and stage instance ID {4} resulted in error: {5}.

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30362: Error while deleting approval record.

Cause: Deleting approval record with task Id {0} resulted in error: {1}.

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30363: Error while getting approval record.

Cause: Getting approval record with task Id {0} and version {1} resulted in error: {2}.

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30370: Error while inserting approval instance.

Cause: Inserting approval instance {0} resulted in error: {1}.

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30371: Error while updating approval instance.

Cause: Updating approval instance {0} with task Id {1}, instance type {2}, and entity name {3} resulted in error: {4}.

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30372: Error while deleting approval instance.

Cause: Deleting approval instance with task Id equals {0} resulted in error: {1}.

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30373: Error while getting approval instance.

Cause: Getting approval instance with approval instance Id {0} resulted in error: {1}.

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30374: Error while getting approval instances.

Cause: Getting approval instance with approval task Id {0} resulted in error: {1}.

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30380: Error while inserting approval record reason.

Cause: Inserting approval record reason with reason Id {0}, reason code {1}, and reason type {2} resulted in error: {3}.

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30381: Error while updating approval record reason.

Cause: Updating approval record reason with reason Id {0}, reason code {1}, and reason type {2} resulted in error: {3}.

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30382: Error while deleting approval record reason.

Cause: Deleting approval record reason with reason Id {0} and sequence {1} resulted in error: {2}.

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30383: Error while getting approval record reason.

Cause: Getting approval record reason with reason Id {0} and sequence {1} resulted in error: {2}.

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30385: Error while inserting task sequence change.

Cause: Inserting task sequence change with correlation Id {0}, anchor chain {1}, change type {2} resulted in error: {3}.

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30386: Error while updating task sequence change.

Cause: Updating task sequence change with correlation Id {0} resulted in error: {1}.

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30387: Error while deleting task sequence change.

Cause: Deleting task sequence change with correlation Id {0} resulted in error: {1}.

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30388: Error while getting task sequence change.

Cause: Getting task sequence change with correlation Id {0} resulted in error: {1}.

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30390: Error during update.

Cause: No matching row found while updating {0} with parameter {1}.

Action: Verify that the row is available during update.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30391: Error while querying task payload collection targets

Cause: Error while querying task payload collection targets for task {1} with version{2}

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30392: Error while performing {0} operation related to task aggregation

Cause: Error while performing {0} operation related to task aggregation

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30400: Error occured while inserting a task attachment record.

Cause: Error occured whilst inserting attachment {0} for task {1}.

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30401: Error occured while versioning a task attachment record.

Cause: Error occured whilst versioning attachment {0} for task {1}, version {2}.

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30402: Error occured while generating a new Task Number.

Cause: Generation of a new Task Number failed with the error: {0}

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30403: Error occured while creating a new task history entry.

Cause: Creation of task history entry for task id {0} failed with the error: {1}

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30404: Error occured while writing task translation data.

Cause: Write of task translation data for task id {0} failed with the error: {1}

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30405: Failed to query task number for task.

Cause: Attempt to query task number for task id {0} failed.

Action: Check the task id is correct, and that the task has not been deleted. Check any underlying exception, and the database connection.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30406: Unsupported database type for human workflow persistency.

Cause: The databse type {0} is not supported by human workflow services persistency.

Action: Check your installation settings, and ensure that RCU install completed correctly.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30407: Error querying the process instances based on the logged in user.

Cause: Error in querying process instances based on the logged in user {0}

Action: Check your installation settings, and ensure that RCU install completed correctly.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30408: Eror in querying instance stake holder for logged in user.

Cause: Error in querying instance stake holder for logged in user {0}.

Action: Check your installation settings, and ensure that RCU install completed correctly.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30409: Error in deleting process instance attachment

Cause: Error in deleting process instance {0} attachment {1}.

Action: Check your installation settings, and ensure that RCU install completed correctly.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30410: Error while deleting workflow task metadata

Cause: Error while deleting workflow task metadata {0}

Action: Check the underlying exception and the database connection information.If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30411: Error occured while inserting a pre-initiated task attachment record.

Cause: Error occured while inserting attachment {0} for task correlationId {1}.

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30412: Error occured updating attachment record to add pre-initiated task attachment to the task

Cause: Error occured while updating attachment records for correlationId {0} to add it to task {1}

Action: Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30450: JAXB-Toplink conversion failed.

Cause: Conversion of {0} to {1} failed with error {2}

Action: Check the underlying exception.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30451: Persistency not supported for this object type.

Cause: The class {0} does not suppot persistency of objects of type {1}.

Action: Check the type of object and the class being used to persist it.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30501: Error in authenticating user

Cause: Error in authenticating and creating a workflow context for user {0}

Action: Verify that the user credentials and identity service configurations are correct.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30502: Error in Verification Service when creating Context

Cause: Error in Verification Service when creating Context. {0}

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30503: Invalid Token Error in Verification Service

Cause: Invalid Token Error in Verification Service. Received invalid token in {0}

Action: Verify that correct token is passed.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30504: Internal Error in Verification Service

Cause: Internal Error in Verification Service for user {0}. {1}

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30506: Runtime error in Task Query Service

Cause: Runtime error in Task Query Service. {0}

Action: Verify that the parameters passed are correct.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30507: Runtime error in Task Report Service

Cause: Runtime error in Task Report Service. {0}

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30508: Error while inoking URL to display the content

Cause: Error while invoking URL. {0}

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30509: Insufficient privileges to authenticate on-behalf of another user.

Cause: User {0} cannot authenticate on-behalf of user {1} without admin privileges.

Action: Only users with admin privileges can authenticate on-behalf of another user.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30513: Insufficient privileges to access the task info for this task

Cause: User {0} cannot access the task info for task: {1}

Action: Ensure that the user has been granted appropriate privileges to access the task info for this task.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30514: Session timed out

Cause: Session has timed out, because it was inactive for {0} minutes and {1} seconds.

Action: Relogin in to the application.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30515: Access to internal workflow context is denied

Cause: Requested access to internal workflow context is not allowed according to security policy

Action: Ensure that correct security policy is used. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30516: Token decryption failed

Cause: Could not extract infromation from Workflow context token

Action: Ensure that the Workflow context is not corrupted and it was generated from one of the nodes in the same cluster.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30701: Insufficient privileges to access metadata for another user.

Cause: User {0} attempted to access metadata for user {1} without having appropriate admininstrator privileges.

Action: Ensure that the appropriate privileges have been granted before attempting to access metadata belonging to another user.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30704: Failed to instantiate workflow rule repository service

Cause: Could not create repository service for workflow rule dictionary {1}, package {2}

Action: Check underlying exception. Ensure dictionary name and package are valid.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30705: Failed to get workflow rules

Cause: Could not get workflow rules for {0}

Action: Check underlying exception. Ensure user or group name is correct.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30706: Rule tests for task payload cannot be defined in this release

Cause: Definition of rules with tests that check the task payload is not supported in this release.

Action: Remove any payload tests from the rule definition.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30707: Invalid workflow rule action.

Cause: Action type {0} is not a valid rule action type.

Action: Specify a valid rule action type.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30708: Failed to update rule dictionary.

Cause: Update of dictionary {0} failed with error: {1}

Action: Check underlying exception. Ensure that workflow rules dictionary name is valid.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30709: Failed to load ruleset.

Cause: Failed to load ruleset from dictionary {0} for rule with ID {1}.

Action: Check underlying exception. Ensure dictionary name and rule ID are valid.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30710: Failed to create ruleset.

Cause: Failed to create ruleset in dictionary {0}.

Action: Check underlying exception. Ensure dictionary name is valid.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30711: Invalid authentication context.

Cause: Invalid authentication context has been passed to user metadata service.

Action: Ensure valid authentication context is passed.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30712: Failed to execute workflow ruleset.

Cause: Rules engine reported error when executing workflow ruleset in dictionary {0}.

Action: Check underlying exception. Ensure rules are correctly defined in ruleset.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30713: Failed to parse workflow ruleset.

Cause: Rules repository reported error when generating RuleLanguage for workflow ruleset in dictionary {0}.

Action: Check underlying exception. Ensure rules are correctly defined in ruleset.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30714: Missing date in date range.

Cause: Both start date and end date must be specified.

Action: Specify both a start date and an end date.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30715: End date is before start date.

Cause: End date cannot occur before the start date.

Action: Specify an end date that occurs after the start date.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30716: Invalid workflow rule test attribute

Cause: Workflow rule test {0} uses an invalid task attribute: {1}.

Action: Specify valid task attributes when defining workflow rules.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30717: Invalid operator in workflow rule test expression.

Cause: The workflow rule test {0} uses the invalid operator {1}.

Action: Ensure that a valid operator is specified and that it is appopriate for the datatype of the attribute.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30718: Cannot specify null value in workflow rule test expression.

Cause: The workflow rule test {0} compares the task attribute to null.

Action: A valid value must be specified for the test expression.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30719: Cannot define a rule test for a Duration attribute.

Cause: The workflow rule test {0} is for an attribute of type Duration.

Action: Rule tests for Duration attribute types are not supported. Select another attribute.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30720: Error in invoking user metadata service.

Cause: A client side error occured in invoking the user metadata service.

Action: Verify that the connection information for the server is correct, and that the server hosting the user metadata service is available.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30721: Error in invoking user metadata service operation.

Cause: An client side error occured in invoking the user metadata service operation {0}.

Action: Verify that the connection information for the server is correct, and that the server hosting the user metadata service is available.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30722: Fault reported by user metadata Web service.

Cause: The user metadata service returned a fault for the following error: {0}

Action: Refer to the error reported by the fault.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30723: User does not exist.

Cause: There is no such user as {0}.

Action: Enter a valid user name.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30724: Group does not exist.

Cause: There is no such group as {0}.

Action: Enter a valid group name.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30725: Cannot reassign to user or group.

Cause: {0} does not have the neccessary permissions to assign tasks to {1}

Action: Select a different user or group.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30726: Rule name is not unique.

Cause: A rule named {0} already exists for {1}.

Action: Specify a different name.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30727: Cannot update GrantedTaskView grant type.

Cause: Updates to UserTaskView grants cannot change grant type.

Action: Do not change the grant type when updating UserTaskView ViewGrants.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30728: Invalid ViewGrant type.

Cause: Invalid View Grant type of {0} was specified for grant of view {1} to {2}.

Action: Valid ViewGrant types are SHARE_DATA and SHARE_DEFINITION.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30729: Invalid UserTaskView type.

Cause: {0} is not a valid value for view type.

Action: Valid UserTaskView types are VIEW and STANDARD_VIEW.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30730: Public UserTaskView access error.

Cause: User {0} does not have permission to manage views of type STANDARD_VIEW.

Action: Only users with workflow administrator privilege can create, update or delete UserTaskViews of type PUBLIC_VIEW.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30731: View for update does not exist.

Cause: Cannot update view {0}. No view exists with ID {1}.

Action: Check that the view ID is correct, and that another user has not deleted the view being updated.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30732: Invalid OptionalInfo value specified.

Cause: {0} specifies an invalid OptionalInfo value of {1}.

Action: Specify a valid OptionalInfo value.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30733: Invalid column specified for ordering clause.

Cause: {0} specifies an invalid ordering column name of {1}.

Action: Specify a valid Task column name in the ordering clause.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30734: Invalid sort order specified for ordering clause.

Cause: {0} specifies and invalid sort order of {1} for the column {2}.

Action: Specify a valid sort order in the ordering clause.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30735: Invalid column specified for view chart group by column.

Cause: The view {0} specifies an invalid chart group by column name of {1}.

Action: Specify a valid Task column name.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30736: Rules cannot be associated with 'TODO' tasks.

Cause: The rule {0} illegally specifies the 'TODO' task type {1}.

Action: Assocatiate the rule with a different task type, or with no task type.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30737: Application role does not exist.

Cause: There is no such role as {0} in application {1}.

Action: Specify a valid role and application name.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30738: Invalid Participant type.

Cause: Participant named {0} specifies an invalid type of {1}.

Action: Specify a valid ParticipantType. Valid types are USER, GROUP, APPROLE.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30739: Invalid Arguments specified.

Cause: Atleast one among {0} , {1} and {2} seems to be invalid .

Action: Specify valid arguments.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30740: Policy Object already exists.

Cause: Policy object {0} already exists in the policy store.

Action: .
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30741: Policy Store error.

Cause: Failed to perform the desired operation.

Action: See the exception log for the reason behind the failure to fix the issue.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30742: Attempt to execute privileged action.

Cause: An attempt to execute a privileged action was made.

Action: Ensure that the codebase being used has the necessary permissions and privileges. If not, grant the same in the application's policy file. Contact oracle support if error is not fixable.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30743: Application Role in use.

Cause: Application Role named {0} is in use, the desired operation cannot be performed.

Action: Clear all the dependencies on the app role {0} before performing this operation.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30744: Policy Object not found.

Cause: Atleast one policy object among {0},{1} not found in the policy store.

Action: Provide valid arguments
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30745: Invalid Application type.

Cause: Application named {0} specifies an invalid type.

Action: Specify a valid Application Type. Valid types are soa-infra, OracleBPM, OracleBPMComposer.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30746: Invalid User type.

Cause: User {0} does not have administrator privileges.

Action: Login as an adminitrator to perform this operation.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30747: UserApplicationData not found.

Cause: No UserApplicationData found with the id {0}

Action: Check the id is correct. The UserApplicationData may have been deleted.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30748: Presentation not found.

Cause: No Presentation found with the id {0}

Action: Check the id is correct. The Presentation may have been deleted.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30749: Invalid PresentationDataType.

Cause: The presentation {0} specifies an invalid PresentationDataType of {1}. Valid values are: {2}.

Action: Specify a valid PresentationDataType.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30750: Presentation type mismatches View type.

Cause: The view {0} is associated with Presentation {1}, which is of type {2}, instead of the expected type {3}.

Action: Views must be associated with Presentations of matching type. Associate the view with a Presentation of the appropriate type.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30751: Dynamic Assignment Framework function {0} experienced error querying the workflow schema: {1}

Cause: A Dynamic Assignment Function experienced an error whilst attempting to query data from the workflow schema.

Action: Check the underlying error. Verify that the workflow datasource is correctly configured, and that database server is available. If this is a custom dynamic assignment fuction, ensure that the SQL being executed is valid.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30752: Group {0} not found by Authorization Service

Cause: The Dynamic Assignment Framework was unable to locate a group named {0} using the Authorization Service.

Action: Check that the group name is correct. If the group name is correct, check that the Authorization Service is configured correctly, and that the directory it uses contains the specified group.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30753: Dynamic Assignment Framework experienced error invoking Authorization Service: {0}

Cause: The Dynamic Assignment Framework experienced an error whilst attempting to invoke the Authorization Service.

Action: Check the underlying error, and verify that the identity service is configured correctly.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30755: No such Dynamic Assignment Function as {0}

Cause: There is no such function as {0} registered with the Dynamic Assignment Framework. Specify a valid function name

Action: Check that a correct function name is specified. If this is a correct function name, ensure that the function is registered in the workflow configuration file.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30756: Dynamic Assignment Function {0} does not support user assignment.

Cause: The Dynamic Assignment Function {0} does not allow dynamic assignment to users. Only assignment to groups is supported.

Action: Only use this function for group assignments. To enable user assignment, the java class that implements this function must be modified to implement the IDynamicUserAssignment interface.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30757: Dynamic Assignment Function {0} does not support group assignment.

Cause: The Dynamic Assignment Function {0} does not allow dynamic assignment to groups. Only assignment to users is supported.

Action: Only use this function for user assignments. To enable group assignment, the java class that implements this function must be modified to implement the IDynamicGroupAssignment interface.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30758: Could not locate Dynamic Assignment Function implementation class: {0}

Cause: The Dynamic Assignment Framework could not locate function implementation class: {0} Either the class name is incorrect, or the class is not in the classpath

Action: Check that the specified class is located in the classpath. Check that the correct classname is specified in the workflow configuration file.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30759: Dynamic Assignment Function class interface implementation error.

Cause: Dynamic Assignment Function class Classes that implement {0} does not implement IDynamicUserAssignmentFunction or IDynamicGroupAssignmentFunction.

Action: Dynamic Assignment Functions must implement at least one of the interfaces IDyanmicUserAssignmentFunction or IDynamicGroupAssignmentFunction. Check the specified class and ensure it implements one of the interfaces.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30760: Failed to instantiate instance of Dynamic Assignment Function class.

Cause: The Dynamic Assignment Framework could not instantiate the Dynamic Assignment Function class: {0} because it is not a concrete class.

Action: Ensure that the class {0} is not an interface or abstract class.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30761: Dynamic Assignment Function class constructor error.

Cause: The Dynamic Assignment Framework could not instantiate an instance of {0} becuase there is no accessible no-argument constructor.

Action: Ensure that the class {0} is public, and procides a public, no-argument constructor.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30762: Dynamic Assignment Function class does not implement IDynamicAssignmentFunction.

Cause: Dynamic Assignment Function class {0} must implement the interface IDynamicAssignmentFunction.

Action: Check the specified class and ensure it implements the interface IDynamicAssignmentFunction.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30801: Error selecting user metadata from repository.

Cause: An attempt to select data from table {0} resulted in the error: {1}

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30802: Error inserting user metadata into repository.

Cause: An attempt to insert user data into table {0} resulted in the error: {1}

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30803: Error updating user metadata in repository.

Cause: An attempt to update user data in table {0} resulted in the error: {1}

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30804: Error deleting user metadata from repository.

Cause: An attempt to delete user data from table {0} resulted in the error: {1}

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30805: Operation not supported for this column type.

Cause: The operator {0} is not supported for columns of type {1}.

Action: Use a different operator when specifying predicate conditions for this column.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30851: User has insufficient privileges to update workflow runtime configuration data.

Cause: User {0} attempted to update runtime configuration data without having the required {1} privilege.

Action: Ensure that the user has been granted the appropriate workflow privileges before updating runtime configuration data.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30852: Invalid task message attribute specified in attribute label.

Cause: The flexfield label {0} uses the invalid task flexfield column name {1}.

Action: Specify a valid task flexfield column name.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30853: Workflow definition does not exist.

Cause: No workflow definition found with ID {0}.

Action: Specify a valid workflow defintion ID.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30854: Failed to retreive list of Dynamic Assignment Functions.

Cause: Could not get list of Dynamic Assignment Functions.

Action: Check underlying exception. Ensure Dynamic Assignment Functions are configured correctly in the workflow configuration file.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30855: Flexfield mappings for complex payload attributes must specify an xpath expression.

Cause: Payload attribute {0} is a complex type. Mappings must provide an xpath to a simple type property.

Action: Provide a valid xpath expression that maps to a simple-type property of the complex type.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30856: Payload attribute type does not match flexfield label type.

Cause: Payload attribute {0} has a type that does not match the type for flexfield label {1}.

Action: Use a flexfield label of the appropriate type.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30857: Workflow payload attribute not found.

Cause: Workflow task type {0} does not have a payload attribute named {1}.

Action: Ensure that workflow task type and payload attribute name are correct.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30858: Error in invoking runtime config service.

Cause: A client side error occured in invoking the runtime config service.

Action: Verify that the connection information for the server is correct, and that the server hosting the runtime config service is available.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30859: Error in invoking runtime config service operation

Cause: An client side error occured in invoking the runtime config service operation {0}.

Action: Verify that the connection information for the server is correct, and that the server hosting the runtime config service is available.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30860: Fault reported by runtime config service

Cause: The runtime config service returned a fault for the following error: {0}

Action: Refer to the error reported by the fault.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30861: Label name is already in use.

Cause: A label with the name {0} already exists.

Action: Specify a different name for the label.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30862: Workflow definition does not exist.

Cause: No workflow definition found with task definition namespace {0}.

Action: Specify a valid workflow definition namespace.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30863: Cannot delete an attribute label for which payload mappings exist.

Cause: Payload mappings exist for the attribute label {0}.

Action: Remove all payload mappings before deleting the attribute label.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30864: Label is already in use by this task component definition.

Cause: The attribute label {0} is already being used by this workflow definition.

Action: Specify a different label.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30865: Invalid attribute type.

Cause: An invalid attribute type of {0} was specified.

Action: Specify a valid attribute type.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30866: Flexfield is already in use by this task component definition.

Cause: The flexfield {0} is already being used by this workflow definition in a mapping to the label {1}.

Action: Specify another label that uses a different flexfield.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30890: Approval Group already exists

Cause: An Approval Group with this name already exists:{0}

Action: Use a different name for the Approval Group or use updateApprovalGroup method if referring to this Approval Group .
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30891: Approval Group not found.

Cause: Approval Group with the given name doesnot exist: {0}

Action: Verify that the Approval Group name is correct and whether it has been correctly created.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30892: Approval Group not deleted.

Cause: The specified Approval Group could not be deleted: {0}

Action: Verify that the Approval Group name is correct and whether it had been correctly created.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30893: Approval Group member not in list.

Cause: The specified Approval Group member was not found in the member list for the given Approval Group: {0}

Action: Verify that the Approval Group name is correct and that the specified member had been correctly created in the group.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30894: Approval Group member not created.

Cause: The specified member could not be added to the given Approval Group: {0}

Action: Verify that the Approval Group name is correct and that the member is valid.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30895: Approval Group member not updated.

Cause: The specified member could not be updated in the given Approval Group: {0}

Action: Verify that the Approval Group name is correct and that the member had been correctly created.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30897: Approval Group member not deleted.

Cause: The specified member could not be deleted from the given Approval Group: {0}

Action: Verify that the Approval Group name is correct and whether the member had been correctly created.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30898: Approval Group member already exists.

Cause: The specified member already exists in the given Approval Group: {0}

Action: Use the updateInGroup api instead.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30899: No matching Approval Group found.

Cause: There are no Approval Groups matching the given search condition: {0}

Action: Verify the search condition and search type specified.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30900: Unable to log adhoc approver insertion .

Cause: There was an error trying to log the adhoc approver insertion information in the AMX Change table: {0}

Action: Verify that the stage name and task ID provided are valid.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30901: Task Evidence does not exist.

Cause: No Evidence found in the repository.

Action: Ensure that an evidence corresponding to the operation exists in the repository.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30902: Task Evidence JAXB Model is malformed.

Cause: This could either be because the XML data for the model does not confirm to the schema or there was an internal JAXB error.

Action: Ensure that the XML data being passed confirms to the Task Evidence Service schema.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30903: Certificate does not exist.

Cause: A certificate with Serial Number {0} and Issuer DN {1} was not found.

Action: Upload the certificate before proceeding. Also ensure that the CA and the URL have been uploaded.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30904: The evidence is not valid.

Cause: All required parmaters are not set.

Action: Ensure that all required parameters are set into the evidence object.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30905: The certificate with Serial Number {0} and Issuer DN {1} is not valid.

Cause: The certificate could have expired. The certificate could also be in an unsupported format or malformed.

Action: Ensure that the certificate is as supplied by the certificate authority.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30906: The signature is not valid.

Cause: The signature does not confirm to the content and certificate. The signature may also be in an unsupported format or malformed.

Action: Ensure that the signature is not modified once it is created.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30907: Internal Error.

Cause: The underlying Security APIs have thrown an exception.

Action: Look at the exception trace for more information.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30908: CRL validation error for certificate Id {0} and CA name {1}.

Cause: The CRL could not be validated.

Action: Ensure that the CA URL exists and is correct.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30909: Certificate cannot be uploaded.

Cause: The certificate could not be uploaded. Only X.509 certificates are supported.

Action: Ensure that the file or string contains a X.509 certificate in a supported format. Also, ensure that the certificate or any other certificate in the chain do not exist in the system. All those certificate which did not exist in the system would have been uploaded.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30910: Invalid Access Error.

Cause: User {0} does not have permission to perform {1}.

Action: Ensure the user has been granted appropriate privileges.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30911: Unable to initialize the queue connection factory for queue {0}

Cause: Unable to initialize the queue connection factory for queue {0}

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30912: Error in invoking task evidence service

Cause: A client side error occured in invoking the task evidence service.

Action: The service could be down. Check the exception error stack to identify the error. If the error persists, contact Oracle Support Services..
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30913: Error in task evidence SOAP service

Cause: An error occured in invoking the task evidence service over SOAP.

Action: Ensure that soap messages are proper and well formed. Check the exception error stack to identify the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30951: Invalid view ID.

Cause: The view ID: {0} does not match any view stored in the repository.

Action: Ensure that a correct view ID is being passed.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30952: Invalid display column.

Cause: The display column {0} is not a valid Task column.

Action: Specify a valid column name.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30953: User has insufficient privileges to use given filter.

Cause: The user {0} in identity context {1} does not have sufficient privileges to query tasks with {2} filter.

Action: Ensure that proper privileges are granted to the user.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30954: Invalid assignment filter value specified for predicate.

Cause: The predicate specifies an invalid AssignmentFilter value of {0}.

Action: Specify a valid AssignmentFilter value.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30955: Invalid column name used in predicate.

Cause: The predicate specifies a column named {0} which does not exist on the table {1}.

Action: Specify a valid column and table in the predicate.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30956: Invalid logical operator used in predicate.

Cause: The predicate uses an invalid logical operator of {0}.

Action: Use a valid logical operator. Valid values are AND and OR.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30957: Invalid operator used in predicate.

Cause: The predicate uses an invalid operator value of {0} with column {1}.

Action: Specify a valid operator value.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30958: Predicate specifies an invalid operator for a null value.

Cause: The operator {0} cannot be used with a value of null.

Action: Specify a value, or use the EQ, NEQ, IS_NULL or IS_NOT_NULL operators.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30959: Predicate clause with ValueListType must use IN or NOT_IN operator.

Cause: The operator {0} cannot be used with a value list.

Action: Use the IN or NOT_IN operators when using a value list.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30960: Invalid value specified for N_DAYS operator in predicate clause.

Cause: The predicate value {0} is not valid for the operator {1}.

Action: Specify an integer value.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30961: Invalid value specified in predicate clause.

Cause: The value {0} for column {1} is invalid for the column's datatype.

Action: Specify a value that is of the correct type, or is another column with a matching datatype.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30962: Invalid Presentation type.

Cause: The specified Presentation {0} is of type {1}, but the required type is {2}.

Action: Specify a different Presentation of the correct type.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-30963: Invalid View type.

Cause: The specified View {0} is of type {1}, which is not valid for querying tasks.

Action: Specify a different View of a correct type (VIEW or STANDARD_VIEW).
Level: 1

Type: ERROR

Impact: Programmatic

BPM-31002: Error while publishing message to notification queue

Cause: Error while publishing message to notification queue

Action: Check Application server data source properties for BPEL-Workflow connections. Check schema and verify database connections.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-31003: Unable to initialize the queue connection factory for queye {0}

Cause: Unable to initialize the queue connection factory for queye {0}

Action: Check Application server data source properties for BPEL-Workflow connections. Check schema and verify database connections.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-31004: Error while querying notification from repository for ID {0}

Cause: Error while querying notification from repository for ID {0}

Action: Check Application server data source properties for BPEL-Workflow connections. Check schema and verify database connections.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-31005: Error while inserting notification in repository

Cause: Error while inserting notification in repository

Action: Check Application server data source properties for BPEL-Workflow connections. Check schema and verify database connections.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-31006: Error while updating notification in repository for ID {0}

Cause: Error while updating notification in repository for ID {0}

Action: Check Application server data source properties for BPEL-Workflow connections. Check schema and verify database connections.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-31007: Error while deleting notification in repository for ID {0}

Cause: Error while deleting notification in repository for ID {0}

Action: Check Application server data source properties for BPEL-Workflow connections. Check schema and verify database connections.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-31008: Incoming message could not be processed

Cause: Incoming message could not be processed

Action: Ensure that the response message is not corrupted
Level: 1

Type: ERROR

Impact: Programmatic

BPM-31009: Incoming message content is invalid

Cause: Incoming message could not be processed due to invalid content

Action: Ensure that the response message is not corrupted: The encrypted response should begin and end with '[[NID]]'
Level: 1

Type: ERROR

Impact: Programmatic

BPM-31010: No NID Placeholder

Cause: Incoming message content does not contain Notification ID placeholders

Action: Ensure that the response message is not corrupted
Level: 1

Type: ERROR

Impact: Programmatic

BPM-31011: Error while updating table

Cause: Error while updating {0} table

Action: Check Application server data source properties for BPEL-Workflow connections. Check schema and verify database connections.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-31012: Error while inserting into table

Cause: Error while inserting into {0} table

Action: Check Application server data source properties for BPEL-Workflow connections. Check schema and verify database connections.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-31013: Error while deleteing from table

Cause: Error while deleting from {0} table

Action: Check Application server data source properties for BPEL-Workflow connections. Check schema and verify database connections.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-31014: Error while selecting from table

Cause: Error while selecting from {0} table

Action: Check Application server data source properties for BPEL-Workflow connections. Check schema and verify database connections.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-31015: Error while sending notification

Cause: Error while sending notification to {0}

Action: Check the underlying exception and fix it.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-31016: Error while receiving notification response

Cause: Error while receiving response from {0} at {1}; for message {2}

Action: Ensure that response message is not corrupted; User should respond to actionable notifications from the same email account to which it was sent; Task status has not changed
Level: 1

Type: ERROR

Impact: Programmatic

BPM-31017: Cannot create notification object

Cause: Error while creating {0} object

Action: Internal Error; Cannot create Notification Object
Level: 1

Type: ERROR

Impact: Programmatic

BPM-31018: Incorrect Notification Configuration

Cause: Incorrect Configuration : {0}

Action: NotificationMode in workflow-notification-config.xml should be either EMAIL or ALL to send Email notifications; It should be ALL to send any other type of notifications
Level: 1

Type: ERROR

Impact: Programmatic

BPM-31019: MimeType not supported

Cause: MimeType {0} is not suppored for channel type{1}

Action: In the application, Use only supported mime types for sending notifications
Level: 1

Type: ERROR

Impact: Programmatic

BPM-31020: Auto Reply Error

Cause: Error while sending auto reply on {0} channel

Action: Internal Error. Ensure that the message being replied to is not corrupted
Level: 1

Type: ERROR

Impact: Programmatic

BPM-31021: Invalid Parameters

Cause: Invalid parameters supplied for Notification : {0}

Action: Provide valid notification inputs like recipient Address, Channel type etc
Level: 1

Type: ERROR

Impact: Programmatic

BPM-31022: Could not register/un register/fetch spam sources

Cause: Could not register/un register/fetch spam sources: {0}

Action: Possible cause : Invalid address is being registered/unregistered
Level: 1

Type: ERROR

Impact: Programmatic

BPM-31023: Cannot send Notification to specified address

Cause: Cannot send {0} notification to {1} address. The address is being marked as 'invalid' and no further notification would be sent to this address.

Action: Make sure that : the address specified is correct; the Email/Gateway server is up and running. Once the problem is corrected, remove the address from invalid address list using EM.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-31024: Invalid recipient address

Cause: Recipient address specified for {0} notification is invalid : {1}

Action: Check Workflow Notification Configuration; Ensure that Email/IM recipient address is valid.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-31025: Actionable Email/IM has been responded from a different account.

Cause: Actionable {2} had been sent to {0}, but received response from {1}.

Action: Actionable notifications should be responded from the same account to which it was sent.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-31026: user-ID not set

Cause: user-ID field is not set in the user payload

Action: Ensure that the payload contains user ID
Level: 1

Type: ERROR

Impact: Programmatic

BPM-31027: group-ID is not set

Cause: group-ID field is not set in the group payload

Action: Ensure that Payload contains group ID
Level: 1

Type: ERROR

Impact: Programmatic

BPM-31028: Could not send notification to user

Cause: Could not send notification to user {0}

Action: Check Workflow Notification Configuration. Ensure that underlying channels are configured.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-31029: Notification Channel not supported

Cause: Notification Channel {0} is not supported

Action: Requested channel is not supported.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-31030: Error while creating notification content

Cause: Could not create notification content

Action: Ensure that the files being used for attachment exist and not corrupted.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-31031: Incorrect incoming Notification Configuration

Cause: Incorrect Incoming Configuration : {0}

Action: The AccountName in workflow-config.xml should be one of the names used in workflow-notification-config.xml
Level: 1

Type: ERROR

Impact: Programmatic

BPM-31032: Error status received from UMS.

Cause: Status detail : Status type : {0}, Status Content : {1}, Addressed to : {2}, UMS Driver : {3}, UMS Message Id : {4}, Gateway message Id : {5}, Status Received at : {6}

Action: Check status details and fix the underlying reason, which caused error
Level: 1

Type: ERROR

Impact: Programmatic

BPM-32001: Error in Identity Service

Cause: Error occurs while using Identity Service

Action: Check underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-32002: Error in create parameters from WSIF Java Web Services message

Cause: The {0} could not be created because expected element {1} is not be found in the element {2} in the parameter passed to WSIF Java Web Services

Action: Check the message passed to the Web service. Also check underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-35001: Configuration file {0} not found.

Cause: Could not locate configuration file with the path: {0}

Action: Ensure that the path is correct, and that there is a configuration file at the specified path.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-35002: Configuration file format error whilst parsing file {0}: {1}

Cause: Could not parse the configuration file {0} because of the error: {1}

Action: Check the underlying error, and ensure that the configuration file is formatted correctly.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-35003: Error saving configuration file {0}: {1}

Cause: Failed to save the configuration file to {0} because of the error: {1}

Action: Check the underlying error. Ensure that the path {0} is correct, and that if the file already exists that it is in a writeable state.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-35004: Workflow deployment is not supported

Cause: Workflow deployment is not supported in platform {0}

Action: Check the underlying error. Ensure that the platform {0} is correct
Level: 1

Type: ERROR

Impact: Programmatic

BPM-35005: Unable to deploy workflow files

Cause: Unable to deploy workflow files

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-35006: Unable to undeploy workflow files/metadata

Cause: Unable to undeploy workflow files/metadata

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-35007: Unable to load service client configuration file

Cause: Unable to load service client configuration file {0}.

Action: Check if service client configuration file {0} exists in the classpath. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-35008: Unable to find service definision in client configuration file

Cause: Unable to find service {0} definision in client configuration file {1}

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-35009: Unable to obtain scheduler to schedule workflow service timers

Cause: Unable to obtain scheduler to schedule workflow service timers

Action: Retry the action if possible. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-35010: Unable to Encrypt data

Cause: Unable to Encrypt data

Action: Check installation/post-installation steps for errors. Check for errors during SOA server startup.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-35011: Unable to Decrypt data

Cause: Unable to Decrypt data

Action: Check for corrupted encrypted data. Check installation/post-installation steps for errors. Check for errors during SOA server startup.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-35012: Unable to fetch/generate encryption key

Cause: Unable to fetch/generate encryption key

Action: Check installation/post-installation steps for errors. Check for errors during SOA server startup.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36001: Internal error.

Cause: An internal error occurred in the Decision Service, info code {0}

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36011: Error while initializing decision service.

Cause: Error while initializing decision service.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36012: Error creating a JAXB marshaller for the decision service.

Cause: Error while creating a JAXB marshaller for the decision service.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36013: Error creating a JAXB unmarshaller for the decision service.

Cause: Error while creating a JAXB unmarshaller for the decision service.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36050: Error in decision service interaction pattern.

Cause: An error occurred in interpreting the interaction pattern {0}.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36051: Error while executing interaction pattern Assert.

Cause: Error while executing interaction pattern Assert for path {0}.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36052: Error while executing interaction pattern AssertExecute.

Cause: Error while executing interaction pattern AssertExceute for path {0}.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36053: Error while executing interaction pattern Watch.

Cause: Error while executing interaction pattern Watch for path {0}.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36054: Error while executing interaction pattern AssertExceuteWatchStateless.

Cause: Error while executing interaction pattern AssertExceuteWatchStateless for path {0}.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36055: Error while executing interaction pattern AssertExceuteWatchStateful.

Cause: Error while executing interaction pattern AssertExceuteWatchStateful for path {0}.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36056: Error while executing interaction pattern CallFunctionStateless.

Cause: Error while executing interaction pattern CallFunctionStateless for path {0}.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36057: Error while executing interaction pattern CallFunctionStateful.

Cause: Error while executing interaction pattern CallFunctionStateful for path {0}.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36101: Error while initializing the decision service cache.

Cause: Error while initializing the decision service cache.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36102: Error reading configuration file.

Cause: Error while trying to read the configuration file {0}.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36103: Error creating the payload.

Cause: Error while trying to create the payload for element {0}, namespace {1}.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36104: Error creating the decision document.

Cause: Error while trying to create the decision document for {0}.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36105: Error creating the decision service error SOAP element.

Cause: Error while trying to create the decision service error SOAP element for service {0}, pattern {1}.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36106: Error creating the SOAP element from decision.

Cause: Error while trying to create the SOAP element from the decision of service {0}.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36107: Error unmarshalling the decide context.

Cause: Error while trying to unmarshal the payload for pattern {0}.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36108: Decision Service metadata not in cache.

Cause: Cannot find metadata in path {0} for {1}.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36109: Error caching the Decision Services metadata.

Cause: Error caching the decision services metadata for path {0}.

Action: Check the underlying exception and correct the error. This is most likely due to a rule modeling isssue. Validate the rule dictionary in rule designer and fix any errors and warnings. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36110: Error unmarshalling decision services configuration.

Cause: Error while trying to unmarshal decision services configuration from URL {0}.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36111: Error validating the decision service request.

Cause: The request for path {0}, service {1} pattern {2} is not valid.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36112: A Decision Service of the given name doesn't exist.

Cause: The component {1} in composite {0} does not expose a service {2}

Action: Check the services that are exposed by component {1}. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36150: Decision Service configuration not available.

Cause: No configuration information available for service {0}.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36151: Error while creating deployment directory.

Cause: Error while creating deployment directory {0} for service {1}.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36152: Error while creating WSDL for backend decision service.

Cause: Error while creating the WSDL for the backend decision service {0}.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36153: Error while creating service configuration file for backend decision service.

Cause: Error while creating the service configuration file for the backend decision service {0}.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36154: Error while copying supporting XSD files for decision service.

Cause: Error while copying supporting XSD files for decision service {0}.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36155: Error while generating JAXB classes for decision service.

Cause: Error while generating JAXB classes from {0} for the backend decision service {1}.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36156: Error while creating deployment descriptor for decision service.

Cause: Error while creating deployment descriptor {0} for the backend decision service {1}.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36157: Error while copy rule repository file to deployment directory.

Cause: Error while copy the file {0} to {1} for decision service {2}.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36158: Error while creating partnerlink WSDL.

Cause: Error while creating partnerlink WSDL for {0} in {1}.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36159: Error compiling fact classes.

Cause: Error while compiling fact classes for service {0}.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36160: Error copying decision service configuration file.

Cause: Error copying decision service configuration file to {0}.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36161: Error copying decision service files.

Cause: The target directory {0} does not exist.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36162: Rule engine not found.

Cause: Unable to find rule engine provider {1} for {0}.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36163: XML schema type not found.

Cause: Unable to find XML schema type for {0}.

Action: Check the rule model and decision service interaction. Make sure that all the required XSD schema files are part of the project.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36164: Type not supported.

Cause: Unable to create XML schema element for type {0}.

Action: Check the rule model and decision service interaction. Make sure that all the required XSD schema files are part of the project.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36200: Error while initializing the rule engine factory.

Cause: Error while initializing the rule engine factory.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36201: Error while loading a rule engine.

Cause: Error while loading a rule engine for {0}.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36202: Error while loading a fact context.

Cause: Error while loading a fact context for {0}.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36203: Error while creating a rule engine.

Cause: Error while creating rule engine for provider {0}.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36204: Error while creating the fact context.

Cause: Error while creating the fact context for {0}.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36205: Error while creating a rule engine.

Cause: No rule engine class loaded for provider {0}.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36206: Error while creating the fact context.

Cause: No fact context class loaded for fact context {0}.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36207: JAXB context not available for fact.

Cause: No JAXB fact context available for fact {0}.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36208: The type is not supported by decision service.

Cause: The type {0} is not supported by decision service.

Action: Remodel rules and decision service interaction to use supported types.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36311: Unknown rule repository type.

Cause: The rule repository type {0} is unknown or unsupported in this context.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36312: Error while initializing the rule repository.

Cause: The rule repository cannot be initialized.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36313: Error while loading the rule catalog.

Cause: The rule catalog cannot be loaded.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36314: Error while trying to close the rule engine.

Cause: The rule engine cannot be closed.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36321: Error while loading the rule set.

Cause: The rule set cannot be loaded.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36322: A rule catalog could not be found.

Cause: The catalog {1} in package {0} could not be found.

Action: Make sure that the rule catalog {0}.{1} exists in the path {2}. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36331: Error while initializing the rule session.

Cause: The rule session {0} failed to initialize.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36332: Error while resetting the rule session.

Cause: The rule session {0} reset failed.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36333: Error while executing the rule session.

Cause: The rule session {0} failed to execute.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36334: Error while executing a rule session unit of work.

Cause: The rule session {0} failed to execute step {1} {2}

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36335: Fact not found in the rule engine working memory, rule session execution failed.

Cause: The rule session {0} failed because an instance of the fact {1} could not be found in the working memory of the rule session.

Action: This is most likely a rule modeling error. The decision service interaction expects the fact instance to exist in the working memory of the rule session. Check the rule actions in rule designer and make sure that a fact of the expected type is being asserted. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36336: Error while executing a rule session unit of work, duplicate fact instances found.

Cause: The rule session {0} failed because more than one fact instance of the fact {1} exists in the rule session working memory. The decision service cannot identify which one to take.

Action: This is most likely due to a rule modeling issue. Make sure that the fact of the given type is asserted only once. One common issue is that the rule conditions are not mutually exclusive and as a result of that more than one rule action is executed. In case the rule action has a assert new statement of the given fact type then multiple fact instances are created in the rule session working memory and the decision service is not able to identify the one that should be returned as the result of the decision service interaction. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36337: Number of facts requested does not match number of facts retrieved from rule engine.

Cause: There are {0} facts requested but the rule engine returned {1} facts.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36338: Wrong fact from rule engine.

Cause: The requested fact name is {0} whereas the onegiven by the rule engine is {1}.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36341: Rule session pool object does not exist.

Cause: The requested rule session pool object for path {0} and key {1} does not exist.

Action: Check the underlying exception and correct the error. This is most likely due to a rules validation error. Validate the rule dictionary in Rule Designer and correct the validation error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36351: Error loading fact types into the datamodel.

Cause: The data model failed to load fact types.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36352: Error loading functions into the datamodel.

Cause: The data model failed to load functions.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36353: URL error while reading XSD.

Cause: The data model failed to read the XSD {0} because of an URL error.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36354: Error building the XML schema for a XSD.

Cause: The data model failed to build the XML schema from XSD {0}.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36355: Element not found in XML-Schema file.

Cause: The element for fact type {0} could not be found in XML Schema file {1}.

Action: Make sure that the element {0} exists in the schema file {1} or in one of the schema files that is imported by {1}. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36356: Element not unique in XML-Schema file.

Cause: The element for fact type {0} could not be identified in XML Schema file {1}. There exists multiple elements that could define the fact type {0}: {2}

Action: Make sure that the element for fact type {0} is unique in the schema file {1} or in one of the schema files that is imported by {1}. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36357: The function doesn't exist in the datamodel .

Cause: The requested function {0} does not exist in the rule dictionary data model of decision service {1}.

Action: Check the rule dictionary of decision service {1}. Make sure that the function {0} exists and has correct parameter and package name settings. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36358: The XML-Schema file for the fact {0} could not be found in the composite.

Cause: The XML-Schema file {2} could not be found in the composite. The XML fact {0} of target namespace {1} assumes the existence of the schema file in the composite.

Action: Check the composite for the schema {2} and make sure it has target namespace {1}. The schema is expeccted in the project xsd or businessCatalog folder. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36610: No rule engine provider implementation found for Ilog JRules.

Cause: Rule Engine provider implementation for Ilog JRules not found.

Action: Check the configuration file DecisionServicesConfiguration.xml. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36611: Error communicating with Rule Execution Server.

Cause: Rule Execution Server communication error, {0}.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services..
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36612: Unsupported Ilog JRules session provider class

Cause: The rule session provider class {0} is unsupported or does not exist.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36615: Error reading Rule Application Archive.

Cause: Failed to read rule application archive {0} because of {1}.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36616: Error creating unmarshaller.

Cause: Failed to create an unmarshaller for {1}.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36617: Error unmarshalling metadata from the rule application.

Cause: Failed to unmarshal metadata from {0}.

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36620: Creation of rule session failed.

Cause: Failed to create a rule session for {0} {1}

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36621: Error in rule execution.

Cause: Failed to execute rule session {0} {1}

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36622: Error in rule execution, issue with remote connection to Rule Execution Server

Cause: Failed to execute rule session {0} because of a remote error. {1}

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36623: Error resetting rule session.

Cause: Failed to reset rule session {0} {1}

Action: Check the underlying exception and correct the error. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36801: Error initializing the Rule Management Service Factory.

Cause: Attempt to initialize the Rule Management Service Factory failed because of a JAXB error

Action: Refer to the soainfra log files for details and contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36820: Error {0} in Oracle Business Rules.

Cause: Eror {0} occurred in the backend rule engine. The error message is {1}

Action: Fix the error and try again.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36841: Error unmarshalling from org.w3c.dom.Element to JAXB.

Cause: Attempt to unmarshall element {0} using JAXB context {1} resulted in error: {2}

Action: Refer to the soainfra log files for details and contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-36842: Error in rule management service Web service operation invocation

Cause: Error in rule management service Web service operation invocation. The error is {0}.

Action: Verify that the SOAP connection information for the server is correct.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-37001: Error adding List Builder property.

Cause: Failed to add property: {0}

Action: Verify validity of list builder properties.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-37002: Error setting starting point implicitly.

Cause: Failed to walk up the hierarchy as requestor or requestor role is already top approver: {0}

Action: Set the starting point explicitly to some one below the top Approver.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-37003: Error setting hierarchy provider instance in list builder.

Cause: Failed to set hierarchy provider instance {0} in list builder.

Action: Set the valid hierarchy provider instance in the list builder.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-37012: Approval Group is empty.

Cause: The specified Approval Group is empty: {0}

Action: Set the ALLOW_EMPTY_GROUP property to true or populate the Approval Group with members.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-37013: Dynamic Approval Group expansion error.

Cause: Couldnot retrieve approvers from the dynamic Approval Group: {0}

Action: Ensure that the Dynamic Approval Group has been correctly implemented.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-37014: Approval Group could not be expanded.

Cause: The specified Approval Group could not be expanded to retrieve approvers: {0}

Action: Verify the contents and member list of the Approval Group.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-37051: Invalid preference for the list builder.

Cause: Invalid preference set for the list builder: {0}

Action: Set the preference to a value greater than 0.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-37052: No voting regime i set for the list builder.

Cause: No voting regime is set for the list builder: {0}

Action: Set the voting regime to a valid value.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-37053: Constraint is not set.

Cause: No constraint is set.

Action: Set the constraint to a valid value.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-37054: Constraint Level is not valid.

Cause: Constraint Level is not valid.

Action: Set the level to a value greater than 0.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-37055: Approval Group name is empty.

Cause: Approval Group name is empty.

Action: Populate the Approval Group name.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-37056: Identification key is not found.

Cause: Identification key is not found in the Task object.

Action: Populate the Identification key.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-37057: Invalid approver list builder map value.

Cause: The approver list builder map value {0} is invalid.

Action: Verify that the approver list builder map value is correct in the task definition.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-37058: Invalid value for xpath expression.

Cause: The xpath expression {0} is invalid for the task.

Action: Verify that the xpath expression is valid for the task data.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-37059: Invalid approver list builder constraint value.

Cause: The approver list builder constraint value {0} is invalid.

Action: Verify that the approver list builder constraint value is correct in the task definition.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-37100: List Builder had unfulfilled constraints

Cause: The following constraints were unfulfilled: {0}

Action: Verify validity of input properties.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-37101: List Builder failed to initialize principal hierarchy

Cause: List Builder could not initialize principal hierarchy service.

Action: Verify availability of user hierarchy service.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-37102: List Builder failed while crawling principal hierarchy

Cause: List Builder failed while crawling principal hierarchy.

Action: Verify availability of user hierarchy service and validity of user data.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-37103: Service provider failed to initialize.

Cause: Service provider {0} initialization failed.

Action: This error occurs due to error in service provider configuration or if it is not found in config file. Please check configuration for service provider {0} and verify that it is accessible. Please checkactual exception below for more details.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-37104: Service provider invocation error.

Cause: Failed to invoke web method on Service provider {0} .

Action: This error occurs when service provider is unavailable, unreachable, or if error in configuration.This error may occurs during invocation of web methods of the provider due to above reason. Please check the log file for more specific exception and actual cause of the error.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-37105: Service provider class definition error.

Cause: Failed to load the class required for the provider {0} .

Action: This error occurs when a service provider class is not specified correctly in the configuration file. Check the documentation for correct class name for provider {0}.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-37106: Service provider could not be loaded.

Cause: Service provider {0} load failed.

Action: This exception occurs when service provider could not be loaded or used as defined in the configurations and the flag mustUseSpecifiedProvider is set to true. Please check configuration for service provider {0} and verify that it is accessible. Please checkactual exception in the log for more details.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-37150: Approval Management Decision Handler Error - Missing required parameter.

Cause: Missing one or more of the required parameter(s) - {0}.

Action: Make sure parameter is passed properly.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-37151: Error while calling Approval Management Prescription Action.

Cause: Calling Approval Management Prescription Action with decision point name {0}, stage name {1}, and rule name {2} result in error {3}.

Action: Verify underlying exception(s) for details.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-37152: Error while calling Approval Management Decision Service.

Cause: Calling Approval Management Decision Service result in error {0}.

Action: Verify underlying exception(s) for details.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-37153: Error in invoking the approval management Service.

Cause: Approval management service evaluates the rule in the routing slip corresponding to the task definition {0}. During evaluation of this rule, there was an error. See the underlying exception for details.

Action: See the underlying exception(s) for details.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-37154: Payload Error in Approval Management Service.

Cause: Mandatory payload element {0} missing.

Action: Populate the element {0} in the payload.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-37155: No Rule Error in Approval Management Service.

Cause: No valid rule could be found.

Action: Verify the rule setup is correct.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-38001: Error in invoking activity guide metadata service

Cause: An client side error occured in invoking the activity guide metadata service.

Action: Verify that the connection information of the server is correct.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-38002: Error in invoking activity guide query service

Cause: An client side error occured in invoking the activity guide query service.

Action: Verify that the connection information of the server is correct.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-38003: Insufficient privileges to access the activity guide.

Cause: User {0} cannot access the activity guide with ciKey: {1}

Action: Ensure that the user has been granted appropriate privileges to access the activity guide info.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-38004: Insufficient privileges to use the ADMIN assignment filter.

Cause: User {0} does not have the activity guide administration privilege required for the using of the ADMIN assignment filter.

Action: Only users with activity guide administrator privilege can use the ADMIN assignment filter when invoking the activity guide query service.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-38005: Error while querying activity guide instance {0}

Cause: Error while querying activity guide instance {0}

Action: Verify that the parameters passed are correct.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-38006: Runtime error in AG Query Service

Cause: Runtime error in AG Query Service. {0}

Action:
Level: 1

Type: ERROR

Impact: Programmatic

BPM-38007: Invalid input AG display column.

Cause: The column name, {0}, specified in the AG display column list does not map to a valid AG field.

Action: Refer to the AG query service javadoc to find a list of valid AG columns, and make sure that the input AG columns are in the list.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-38101: Activity Guide instance {0} not found in registration cache.

Cause: The Activity Guide instance is not found in the registration cache.

Action: Re-register the activity guide instance.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-38201: Messaging Service cannot create JNDI initial context.

Cause: Messaging service cannot create JNDI context.

Action: Contact your system Administator.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-38202: Messaging Service time out occured on a receive.

Cause: Messaging service receive timed out while waiting on JMS topic.

Action: Confirm that message producer is functioning and message consumer is listening on correct topic.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-38203: Messaging service fail to lookup JMS object {0} in JNDI.

Cause: Messaging service cannot create JNDI object.

Action: Check if the JMS object {0} is configured in JNDI.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-39001: Unauthorized user

Cause: User, {0}, is not authorized to finish this operation

Action: Login with appropriate user
Level: 1

Type: ERROR

Impact: Programmatic

BPM-39002: MDS is not supporting versioning

Cause: Configured MDS is not supporting versioning.

Action: Check soa-infra MDS configuration and configure it to point to a store that supports versioning. Ex: database
Level: 1

Type: ERROR

Impact: Programmatic

BPM-39003: Generic MDS Error

Cause: Error occured while performing MDS operation. Error: {0}

Action: Contact system administrator
Level: 1

Type: ERROR

Impact: Programmatic

BPM-39004: SOAP Element conversion error

Cause: Error occured while converting the result object into SOAP message

Action: Contact system administrator
Level: 1

Type: ERROR

Impact: Programmatic

BPM-39005: Empty sandbox name

Cause: Sandbox name cannot be empty

Action: Specify a valid name for the sand box
Level: 1

Type: ERROR

Impact: Programmatic

BPM-39501: Configuration error

Cause: Clients are not configured

Action: Specify a FederatedClient in configuration
Level: 1

Type: ERROR

Impact: Programmatic

BPM-39502: No server name in client configuration

Cause: Client configuration doesn't contain proper server name

Action: Specify a srver name in client configuration
Level: 1

Type: ERROR

Impact: Programmatic

BPM-39504: Duplicate server name in client configuration

Cause: Client configuration contain duplicate names {0}

Action: Specify a correct server name in client configuration
Level: 1

Type: ERROR

Impact: Programmatic

BPM-39505: Client configuration error

Cause: Client configuration error for server {0}

Action: Review server information in client configuration
Level: 1

Type: ERROR

Impact: Programmatic

BPM-39506: Requested client type isn't supported

Cause: Requested client type for server {0} isn't supported

Action: Specify a correct client type for server {0} in client configuration
Level: 1

Type: ERROR

Impact: Programmatic

BPM-39507: No connection to servers

Cause: Either client arn't configured, or there is an issue with the existing client configuration.

Action: Verify that at least one client connection is configured for this application, and that no unresolved ''ConfigurationExceptions'' exceptions are logged.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-39508: More items not currently available

Cause: Date are not available from some servers

Action: Check failed servers and client configuration
Level: 1

Type: ERROR

Impact: Programmatic

BPM-39509: Information not currently available

Cause: Information not currently available for all servers

Action: Check failed servers and client configuration
Level: 1

Type: ERROR

Impact: Programmatic

BPM-39510: Server has more data

Cause: Only the first {0} tasks display for this server

Action: Specify a correct client type in client configuration
Level: 1

Type: ERROR

Impact: Programmatic

BPM-39511: Several servers have more data

Cause: Only the first {0} tasks display for these servers

Action: Specify a correct client type in client configuration
Level: 1

Type: ERROR

Impact: Programmatic

BPM-39512: No default server in client configuration

Cause: Confuration needs to have one default server

Action: Specify a correct default server in client configuration
Level: 1

Type: ERROR

Impact: Programmatic

BPM-39513: Duplicate default server in client configuration

Cause: Confuration needs to have only one default server in client configuration

Action: Specify one default server in client configuration
Level: 1

Type: ERROR

Impact: Programmatic

BPM-39514: Cannot find client configuration

Cause: Cannot find client configuration for server {0}

Action: Specify correct server name which can found in client configuration
Level: 1

Type: ERROR

Impact: Programmatic

BPM-39515: Not defined client type

Cause: Request does not specify client type

Action: Specify correct client type
Level: 1

Type: ERROR

Impact: Programmatic

BPM-39516: Encryption issue in client configuration file.

Cause: Encryption failed in client configuration file.

Action: Please verify if the encryption algorithm {0} is supported.Also check if the key is valid and of correct length.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-39517: Decryption issue in client configuration file.

Cause: Decryption failed in client configuration file.

Action: Please verify if the decryption algorithm {0} is supported.Also check if the key is valid and of correct length.
Level: 1

Type: ERROR

Impact: Programmatic

BPM-40001: Calendar not defined

Cause: The calendar with id {0} is not defined

Action: Specify an existing calendar
Level: 1

Type: ERROR

Impact: Programmatic

BPM-40002: OrganizationalUnit not defined

Cause: The OrganizationalUnit with id {0} is not defined

Action: Specify an existing OrganizationalUnit
Level: 1

Type: ERROR

Impact: Programmatic

BPM-40003: Parent OrganizationalUnit not defined

Cause: The Parent OrganizationalUnit with id {0} is not defined

Action: Specify an existing OrganizationalUnit as a parent OrganizationalUnit
Level: 1

Type: ERROR

Impact: Programmatic

BPM-40004: OrganizationalUnit name not specified

Cause: The OrganizationalUnit name for the OrganizationalUnit with id {0} is not specified

Action: Specify the OrganizationalUnit name
Level: 1

Type: ERROR

Impact: Programmatic

BPM-40005: OrganizationalUnit Id not specified

Cause: The Id for OrganizationalUnit is not specified

Action: Specify the OrganizationalUnit Id
Level: 1

Type: ERROR

Impact: Programmatic

BPM-40006: Id for the association between ApplicationRole, OrganizationalUnit, and CalendarRule not specified

Cause: Id for the association between ApplicationRole, OrganizationalUnit, and CalendarRule not specified

Action: Specify the association Id
Level: 1

Type: ERROR

Impact: Programmatic

BPM-40007: CalendarRule for the association between ApplicationRole, OrganizationalUnit, and CalendarRule not specified

Cause: The CalendarRule Id for the association between ApplicationRole, OrganizationalUnit, and CalendarRule not specified

Action: Specify the CalendarRule Id
Level: 1

Type: ERROR

Impact: Programmatic

BPM-40008: OrganizationalUnit for the association between ApplicationRole, OrganizationalUnit, and CalendarRule not specified

Cause: The OrganizationalUnit Id for the association between ApplicationRole, OrganizationalUnit, and CalendarRule not specified

Action: Specify the OrganizationalUnit Id
Level: 1

Type: ERROR

Impact: Programmatic

BPM-40009: Association between ApplicationRole, OrganizationalUnit, and CalendarRule is not defined

Cause: The association between ApplicationRole, OrganizationalUnit, and CalendarRule with Id {0} is not defined

Action: Specify an existing association between ApplicationRole, OrganizationalUnit, and CalendarRule
Level: 1

Type: ERROR

Impact: Programmatic

BPM-40010: OrganizationalUnit with Id {0} exists

Cause: The OrganizationalUnit with the specified Id exists

Action: Specify a unique Id for the OrganizationalUnit
Level: 1

Type: ERROR

Impact: Programmatic

BPM-40011: Association between ApplicationRole, OrganizationalUnit, and CalendarRule with Id {0} exists

Cause: The association between ApplicationRole, OrganizationalUnit, and CalendarRule with the specified Id exists

Action: Specify a unique Id for the association between ApplicationRole, OrganizationalUnit, and CalendarRule
Level: 1

Type: ERROR

Impact: Programmatic

23 BRW-15000 to BRW-16976

BRW-15000: Internal error in Query Builder error handler

Cause: Error handler could not be started.

Action: Contact support.
Level: 1

Type: ERROR

Impact: Other

BRW-15001: {1}

Cause: Message not found

Action: Check Query Builder directory in Oracle Home for message file.
Level: 1

Type: ERROR

Impact: Other

BRW-15002: Out of memory!

Cause: Out of memory.

Action: Save documents and restart Query Builder.
Level: 1

Type: ERROR

Impact: Other

BRW-15003: Invalid file name: {1}

Cause: User entered an invalid file name (for example, too many characters).

Action: Enter a new, valid file name.
Level: 1

Type: ERROR

Impact: Other

BRW-15004: Internal error ({1}:{2})

Cause: Internal Error Occurred -- Query Builder is in an unreliable state.

Action: Contact support.
Level: 1

Type: ERROR

Impact: Other

BRW-15005: No file name specified

Cause: User did not enter a filename in the Export Data Dialog.

Action: Enter a filename.
Level: 1

Type: ERROR

Impact: Other

BRW-15006: Unable to DESCRIBE data table

Cause: Internal message.

Action: Contact support.
Level: 1

Type: ERROR

Impact: Data

BRW-15007: SQL statement is too complex to display.

Cause: Exceeded the edit buffer size on MSWINDOWS.

Action: Exclude some columns from the query to reduce the SQL statement size.
Level: 1

Type: ERROR

Impact: Other

BRW-15009: Insufficient privileges to login through Query Builder

Cause: Connect privileges are disabled in the SYSTEM.BROWSER_PROFILE table.

Action: Contact your DBA.
Level: 1

Type: ERROR

Impact: Other

BRW-15010: Insufficient privileges to edit schema through Query Builder

Cause: Schema Editing privileges are not enabled in the SYSTEM.BROWSER_PROFILE table.

Action: Contact your DBA.
Level: 1

Type: ERROR

Impact: Other

BRW-15011: Insufficient privileges to edit data through Query Builder

Cause: Data Editing privileges are not enabled in the SYSTEM.BROWSER_PROFILE table.

Action: Contact your DBA.
Level: 1

Type: ERROR

Impact: Data

BRW-15012: Cannot edit schema with DICTIONARY=ENDUSER command-line option

Cause: Query Builder cannot invoke the Schema Builder when DICTIONARY=ENDUSER.

Action: Run Query Builder with the DICTIONARY=NATIVE command line option.
Level: 1

Type: ERROR

Impact: Other

BRW-15013: Insufficient privileges to edit End User Layer through Query Builder

Cause: Meta-data Editing privileges are not enabled in the SYSTEM.BROWSER_PROFILE table.

Action: Contact your DBA.
Level: 1

Type: ERROR

Impact: Other

BRW-15025: Unable to load list of database roles

Cause: Schema internal error in loading list of database roles.

Action: Contact support if this is not expected.
Level: 1

Type: ERROR

Impact: Other

BRW-15065: Syntax error

Cause: User typed a formula incorrectly.

Action: Re-type the expression.
Level: 1

Type: ERROR

Impact: Other

BRW-15066: Expression is too complex

Cause: Expression is too complex.

Action: Simplify the expression.
Level: 1

Type: ERROR

Impact: Other

BRW-15068: Invalid function: {1}

Cause: User entered an invalid function name.

Action: Specify a valid function.
Level: 1

Type: ERROR

Impact: Other

BRW-15069: Invalid column: {1}

Cause: User entered an invalid column name.

Action: Enter a valid column name.
Level: 1

Type: ERROR

Impact: Other

BRW-15070: Invalid table: {1}

Cause: User entered an invalid table name.

Action: Enter a valid table name.
Level: 1

Type: ERROR

Impact: Other

BRW-15071: Invalid owner: {1}

Cause: User entered an invalid user or business area name.

Action: Enter a valid user or business area name.
Level: 1

Type: ERROR

Impact: Other

BRW-15072: Invalid condition

Cause: User entered an invalid condition.

Action: Delete the condition and enter a valid condition.
Level: 1

Type: ERROR

Impact: Other

BRW-15073: Invalid expression

Cause: User entered an invalid expression (usually blank).

Action: Enter a valid expression.
Level: 1

Type: ERROR

Impact: Other

BRW-15074: Invalid use of reserved word {1}

Cause: User used a reserved word as an identifier.

Action: Identifiers cannot be reserved words. Refer to the help or documentation for details.
Level: 1

Type: ERROR

Impact: Other

BRW-15075: Invalid number of arguments to function {1}

Cause: User entered too few or too many arguments for the given function.

Action: Enter the appropriate arguments. Refer to the help or documentation for details.
Level: 1

Type: ERROR

Impact: Other

BRW-15077: Ambiguous name: {1}

Cause: User entered an ambiguous column name.

Action: Enter a specific column name, include any qualifiers.
Level: 1

Type: ERROR

Impact: Other

BRW-15078: Redefinition of name: {1}

Cause: User redefined a column or data table using a name that already exists.

Action: Define the column or table using a new name.
Level: 1

Type: ERROR

Impact: Other

BRW-15079: No columns selected in query

Cause: Query was either built or entered with no displayed columns.

Action: Select columns before re-executing the query.
Level: 1

Type: ERROR

Impact: Other

BRW-15080: No tables specified in query

Cause: User entered a query without specifying any tables.

Action: Select tables before re-executing the query.
Level: 1

Type: ERROR

Impact: Other

BRW-15081: START WITH requires CONNECT BY

Cause: SQL statement contained a START WITH clause without a CONNECT BY clause.

Action: Specify a CONNECT BY clause if using START WITH.
Level: 1

Type: ERROR

Impact: Other

BRW-15082: PRIOR requires CONNECT BY

Cause: SQL statement contained a PRIOR clause without a CONNECT BY clause.

Action: Specify a CONNECT BY clause if using PRIOR.
Level: 1

Type: ERROR

Impact: Other

BRW-15083: Bad argument type to function {1}

Cause: User entered the wrong argument type for the function.

Action: Enter the correct argument type.
Level: 1

Type: ERROR

Impact: Other

BRW-15084: Unterminated comment

Cause: Buffer being read in has an unterminated C-type comment in it.

Action: Edit the file (see that it terminates correctly), and reopen from Query Builder.
Level: 1

Type: ERROR

Impact: Other

BRW-15085: Circular reference detected in defined column

Cause: Modification of a defined column has led to a circular reference.

Action: Redefine the column so that it does not refer to itself in its own definition.
Level: 1

Type: ERROR

Impact: Other

BRW-15086: Arguments to a correlated subquery function must be columns

Cause: A complex argument was given, such as avg (sal, deptno*2).

Action: Specify only valid columns, not expressions, in the subquery.
Level: 1

Type: ERROR

Impact: Other

BRW-15087: Invalid location: {1}

Cause: User entered an invalid database location for a table.

Action: Enter a valid database location.
Level: 1

Type: ERROR

Impact: Other

BRW-15088: Ambiguous table: {1}

Cause: User entered an ambiguous data table name (more than one table uses this name).

Action: User must further qualify the data table. Refer to the help or
Level: 1

Type: ERROR

Impact: Other

BRW-15089: Only one PRIOR operator allowed on an expression

Cause: User typed 2 or more PRIOR clauses in an expression.

Action: Remove one of the PRIOR clauses.
Level: 1

Type: ERROR

Impact: Other

BRW-15090: The name {1} is already in use

Cause: User entered a name that was already being used.

Action: Enter a new name.
Level: 1

Type: ERROR

Impact: Other

BRW-15091: Invalid name: {1}

Cause: User entered an invalid name (with spaces or unprintable chars).

Action: Enter a new name.
Level: 1

Type: ERROR

Impact: Other

BRW-15092: Bad usage of outer relationship

Cause: User specified an outer relationship on a non-column element.

Action: Outer relationships are only valid for columns.
Level: 1

Type: ERROR

Impact: Other

BRW-15093: Invalid number of elements in corresponding record

Cause: User entered two records with different numbers of elements.

Action: Reenter the condition.
Level: 1

Type: ERROR

Impact: Other

BRW-15094: Group function is nested too deeply

Cause: User entered a double(triple) aggregate condition(expression).

Action: Simplify aggregate condition/expression.
Level: 1

Type: ERROR

Impact: Other

BRW-15096: Table name conflicts with {1}, renamed to {2}

Cause: When opening a query, a table alias name conflicts with a new column.

Action: ---
Level: 1

Type: ERROR

Impact: Other

BRW-15097: Name conflicts with {1}, renamed to {2}

Cause: When loading a saved query, an alias name conflicts with a new column.

Action: ---
Level: 1

Type: ERROR

Impact: Other

BRW-15098: Duplicate table {1} in FROM clause

Cause: Data table appears more than once in FROM clause (without an alias).

Action: Remove the duplicate data tables in the FROM clause.
Level: 1

Type: ERROR

Impact: Other

BRW-15099: Subquery returns incorrect number of values

Cause: Subquery returns either too many or too few values.

Action: Reenter condition.
Level: 1

Type: ERROR

Impact: Other

BRW-15100: Correlated expressions are not allowed here

Cause: User entered a correlated expression outside a condition.

Action: Reenter the condition/expression.
Level: 1

Type: ERROR

Impact: Other

BRW-15101: Table alias cannot be reused in the same FROM clause: {1}

Cause: User tried to use an alias in the same FROM clause it was defined in.

Action: Remove the reference to the alias.
Level: 1

Type: ERROR

Impact: Other

BRW-15102: Too many elements in record

Cause: User entered a record with more than 254 elements.

Action: Reduce the number of elements--split the condition into an OR.
Level: 1

Type: ERROR

Impact: Other

BRW-15103: Unnamed SELECT statement in FROM clause

Cause: SQL contained a query in the FROM clause without name.

Action: Add the query name and reparse.
Level: 1

Type: ERROR

Impact: Other

BRW-15110: Invalid number or precision exceeded: {1}

Cause: Non-numeric input or the number exceeded this column's precision.

Action: Re-enter a valid number and precision.
Level: 1

Type: ERROR

Impact: Other

BRW-15111: Invalid date: {1}

Cause: Could not format using the columns format mask or either default mask.

Action: Re-enter a valid format mask.
Level: 1

Type: ERROR

Impact: Other

BRW-15112: Entry exceeds the size limit for this column: {1}

Cause: User entered a string longer than the limit for this column.

Action: Enter a shorter string.
Level: 1

Type: ERROR

Impact: Other

BRW-15113: Not all parameters have been specified

Cause: User attempted to execute a query without defining all parameters

Action: Specify parameters or exclude parameterized expressions and retry.
Level: 1

Type: ERROR

Impact: Other

BRW-15114: Parameters can only be constant expressions

Cause: User attempted to enter a parameter value that depended on a column value.

Action: Specify a valid parameter, one that does not depend on the value in a column.
Level: 1

Type: ERROR

Impact: Other

BRW-15115: Bad usage of parameter {1}

Cause: User entered a parameter name for a column or table.

Action: Specify a valid parameter.
Level: 1

Type: ERROR

Impact: Other

BRW-15116: Invalid parameter name {1}

Cause: User entered an invalid parameter name.

Action: Specify a valid parameter name.
Level: 1

Type: ERROR

Impact: Other

BRW-15117: Invalid parameter {1}

Cause: User entered an invalid parameter.

Action: Specify valid parameter.
Level: 1

Type: ERROR

Impact: Other

BRW-15128: Parser internal error: {1}

Cause: Internal error in the parser/scanner.

Action: Contact support.
Level: 1

Type: ERROR

Impact: Other

BRW-15129: Defined column {1} cannot be used in correlated subquery function

Cause: Use of derived columns (DQ4) in correlated subquery.

Action: Remove that argument from the correlated subquery.
Level: 1

Type: ERROR

Impact: Other

BRW-15130: Query execution failed

Cause: Database access error.

Action: Check database error and rerun query.
Level: 1

Type: ERROR

Impact: Other

BRW-15131: Invalid relational operator

Cause: User applied an invalid operator to a condition.

Action: Enter a valid operator.
Level: 1

Type: ERROR

Impact: Other

BRW-15132: FROM clause was not found where expected

Cause: Encountered no FROM clause or GROUP/HAVING clause before a FROM clause.

Action: Edit SQL statement.
Level: 1

Type: ERROR

Impact: Other

BRW-15133: FROM clause was found without corresponding SELECT clause

Cause: Encountered FROM clause before SELECT clause.

Action: Edit SQL statement.
Level: 1

Type: ERROR

Impact: Other

BRW-15135: Condition cannot be changed

Cause: user attempted to change the top condition in Schema Builder.

Action: Perform the operation on the children conditions.
Level: 1

Type: ERROR

Impact: Other

BRW-15136: SQL contains set operators

Cause: Set operations are not supported.

Action: Run the query in SQLPlus.
Level: 1

Type: ERROR

Impact: Other

BRW-15137: Unable to generate names for complex expressions

Cause: Encountered expressions without names when opening a SQL file.

Action: Define Names for columns in the .sql file.
Level: 1

Type: ERROR

Impact: Other

BRW-15138: CONNECT BY clause existed, and was ignored

Cause: Connect By is not supported at this (top) level.

Action: Run the query in SQLPlus, if results of CONNECT BY were desired.
Level: 1

Type: ERROR

Impact: Other

BRW-15139: Cannot ungroup condition

Cause: Attempt to ungroup top condition.

Action: This operation is not supported.
Level: 1

Type: ERROR

Impact: Other

BRW-15141: Query table cannot contain parameters

Cause: Encountered one or more parameters when creating a view.

Action: Exclude parameters from query or ignore.
Level: 1

Type: ERROR

Impact: Other

BRW-15142: Two or more columns have the same name: {1}

Cause: Encountered duplicate column names when creating view.

Action: Use the Define command to rename duplicate columns.
Level: 1

Type: ERROR

Impact: Other

BRW-15143: {1} is already a display column

Cause: User tried to specify a duplicate display column.

Action: If duplicate column is desired, define a new name for it and re-display it.
Level: 1

Type: ERROR

Impact: Other

BRW-15144: {1} is already a sort column

Cause: User tried to specify a duplicate sort column.

Action: If duplicate column is desired, define a new name for it and re-sort.
Level: 1

Type: ERROR

Impact: Other

BRW-15145: {1} is already a group column

Cause: user tried to specify a duplicate group column.

Action: If duplicate column is desired, define a new name for it and re-group.
Level: 1

Type: ERROR

Impact: Other

BRW-15146: Internal error in opening query

Cause: Internal error in opening query.

Action: Contact support.
Level: 1

Type: ERROR

Impact: Other

BRW-15147: Internal error in saving query

Cause: Internal error in saving query.

Action: Contact support.
Level: 1

Type: ERROR

Impact: Other

BRW-15148: Relationship must be between compatible data types/size

Cause: User tried to relate two columns with incompatible data types.

Action: Relate only compatible datatypes. Refer to the help or documentation for details.
Level: 1

Type: ERROR

Impact: Data

BRW-15150: Cannot define a self-relationship

Cause: User tried to define a relationship within a data table.

Action: Alias the data table and then define the relationship.
Level: 1

Type: ERROR

Impact: Other

BRW-15151: User-defined relationship already exists

Cause: User tried to define a relationship that already exists.

Action: No action required.
Level: 1

Type: ERROR

Impact: Other

BRW-15152: Illegal column in defined relationship

Cause: User specified an illegal expression when defining a relationship.

Action: Retype in a new column.
Level: 1

Type: ERROR

Impact: Other

BRW-15153: Table alias name cannot end with _A<number>

Cause: Illegal alias name.

Action: Input a new name that does not end with _A&lt;number&gt;.
Level: 1

Type: ERROR

Impact: Other

BRW-15154: Cannot remove database relationship

Cause: User tried to remove data dictionary relationship.

Action: Only user-defined relationships can be deleted.
Level: 1

Type: ERROR

Impact: Other

BRW-15155: The following documents may have been affected:{1}

Cause: A saved query was being used as a data table in other query documents.

Action: If you change or delete this query, you will affect these other queries.
Level: 1

Type: ERROR

Impact: Other

BRW-15156: Cannot include table with the same name as the query

Cause: User attempted to include data table D in query document D.

Action: Rename the query before including this table.
Level: 1

Type: ERROR

Impact: Other

BRW-15157: Cannot sort, group, or break on LONG columns

Cause: Trying to sort, group or break on LONG column type.

Action: Cancel the operation. Oracle does not support this.
Level: 1

Type: ERROR

Impact: Other

BRW-15158: Cannot sort, group, or break on RAW columns

Cause: Trying to sort, group or break on RAW column type.

Action: Cancel the operation. Oracle does not support this.
Level: 1

Type: ERROR

Impact: Other

BRW-15159: Cannot display LONG columns from remote databases

Cause: Trying to include LONG column type from remote database data table.

Action: Cancel the operation. Oracle does not support this.
Level: 1

Type: ERROR

Impact: Other

BRW-15160: Maximum number ({1}) of columns exceeded

Cause: User exceeded maximum number of display/group/sort columns supported.

Action: Delete some unwanted columns, then re-include what you need.
Level: 1

Type: ERROR

Impact: Other

BRW-15161: Error in opening {1} display column(s)

Cause: Unable to open DISPLAY column because database has changed since save.

Action: This column may have changed or no longer exist in the database.
Level: 1

Type: ERROR

Impact: Other

BRW-15162: Error in opening {1} sort column(s)

Cause: Unable to open SORT column because database has changed since save.

Action: This column may have changed or no longer exist in the database.
Level: 1

Type: ERROR

Impact: Other

BRW-15163: Error in opening {1} group column(s)

Cause: Unable to open GROUP column because database has changed since save.

Action: This column may have changed or no longer exist in the database.
Level: 1

Type: ERROR

Impact: Other

BRW-15164: Error in opening {1} break column(s)

Cause: Unable to open BREAK column because database has changed since save.

Action: This column may have changed or no longer exist in the database.
Level: 1

Type: ERROR

Impact: Other

BRW-15165: Maximum number ({1}) of break columns exceeded

Cause: User exceeded the maximum number of break columns supported.

Action: Delete some unwanted break columns, then re-include what you need.
Level: 1

Type: ERROR

Impact: Other

BRW-15166: Error in opening {1} condition(s)

Cause: Unable to open conditions because database has changed since save.

Action: Tables or columns used in this condition may no longer exist in the database.
Level: 1

Type: ERROR

Impact: Other

BRW-15167: Alias must be {1} bytes or less: {2}

Cause: alias name too long.

Action: Try typing in an alias less than or equal to 30 bytes long.
Level: 1

Type: ERROR

Impact: Other

BRW-15168: Cannot group on aggregate expression

Cause: Tried to group on an aggregate expression.

Action: Group on another expression.
Level: 1

Type: ERROR

Impact: Other

BRW-15169: {1} has already been included as a break column

Cause: User tried to specify a duplicate break column.

Action: If duplicate column is desired, define a new name for it and re-break.
Level: 1

Type: ERROR

Impact: Other

BRW-15170: Invalid Constraint for table {1}

Cause: User entered an invalid constraint for the selected table.

Action: Reenter constraint.
Level: 1

Type: ERROR

Impact: Other

BRW-15171: Invalid Constraint for table column {1}

Cause: User entered an invalid constraint for the selected column.

Action: Reenter constraint.
Level: 1

Type: ERROR

Impact: Other

BRW-15172: Subqueries are not allowed in Constraints

Cause: User entered an invalid constraint.

Action: Reenter constraint.
Level: 1

Type: ERROR

Impact: Other

BRW-15173: Aggregate conditions are not allowed in Constraints

Cause: User entered an invalid constraint.

Action: Reenter constraint.
Level: 1

Type: ERROR

Impact: Other

BRW-15174: Constraints can only be on one table

Cause: User entered an invalid constraint.

Action: Reenter constraint.
Level: 1

Type: ERROR

Impact: Other

BRW-15175: Table not loaded because all columns are hidden

Cause: All columns are hidden. At least one column needs to be displayed.

Action: Use the Browser Administrator Utility to display hidden columns.
Level: 1

Type: ERROR

Impact: Other

BRW-15188: Query returns 1 row

Cause: Status message for 1-row Query Count.

Action: No action required.
Level: 1

Type: ERROR

Impact: Other

BRW-15189: Query returns {1} rows

Cause: Status message for n-row Query Count.

Action: No action required.
Level: 1

Type: ERROR

Impact: Other

BRW-15190: Unable to count without executing; Query returns <= {1} row(s)

Cause: Status message for n-row Query Count Distinct.

Action: No action required.
Level: 1

Type: ERROR

Impact: Other

BRW-15192: Illegal format '{1}' for column '{2}'

Cause: User typed an unrecognizable format for a display column.

Action: Try another format.
Level: 1

Type: ERROR

Impact: Other

BRW-15193: Illegal format

Cause: User typed an unrecognizable format for a display column

Action: Try another format.
Level: 1

Type: ERROR

Impact: Other

BRW-15195: Incompatible column type in relationship: {1}

Cause: Trying to create illegal relationship.

Action: Column types are incompatible. Refer to the help or documentation for details.
Level: 1

Type: ERROR

Impact: Other

BRW-15196: Error in opening {1} table(s)

Cause: Unable to open data tables because database was modified or object does not exist.

Action: Check your connect string (or contact your DBA).
Level: 1

Type: ERROR

Impact: Other

BRW-15197: Error in restoring position for {1} column(s)

Cause: Unable to reposition column because database was modified or object does not exist.

Action: Check your connect string (or contact your DBA).
Level: 1

Type: ERROR

Impact: Other

BRW-15198: Error in restoring join: {1}

Cause: Unable to restore link during open because database was modified or object does not exist.

Action: Check your connect string (or contact your DBA).
Level: 1

Type: ERROR

Impact: Other

BRW-15199: Error in restoring inclusion state for join: {1}

Cause: Unable to set the inclusion state during open because database was modified or object does not exist.

Action: Check your connect string (or contact your DBA).
Level: 1

Type: ERROR

Impact: Other

BRW-15200: Error in restoring outer join state for join: {1}

Cause: Unable to set the outer join during open because database was modified or object does not exist.

Action: Check your connect string (or contact your DBA).
Level: 1

Type: ERROR

Impact: Other

BRW-15258: Invalid document name: {1}

Cause: User entered an invalid document name.

Action: Enter a valid document name.
Level: 1

Type: ERROR

Impact: Other

BRW-15259: Document exceeds 64K size limit

Cause: User attempted to save/open a document larger than 64K.

Action: Reduce size of document.
Level: 1

Type: ERROR

Impact: Other

BRW-15260: Document {1} does not exist

Cause: User specified a nonexistent document.

Action: Specify another document.
Level: 1

Type: ERROR

Impact: Other

BRW-15261: Document {1} already exists

Cause: User tried to save under the name of an existing document.

Action: Specify another document name or delete the existing document.
Level: 1

Type: ERROR

Impact: Other

BRW-15262: Multiple documents named {1}

Cause: Multiple documents with same name exist.

Action: Delete all but one.
Level: 1

Type: ERROR

Impact: Other

BRW-15263: Database object {1} already exists

Cause: User tried to save under the name of an existing object.

Action: Specify another document name.
Level: 1

Type: ERROR

Impact: Other

BRW-15264: Table {1} does not exist

Cause: Data Table view corresponding to a saved document has been removed.

Action: Re-save the document (it no longer exists as a query view).
Level: 1

Type: ERROR

Impact: Other

BRW-15265: Table {1} has been removed or modified

Cause: Data Table view corresponding to a saved document has been modified.

Action: Re-save the document.
Level: 1

Type: ERROR

Impact: Other

BRW-15266: File {1} does not exist

Cause: User specified a nonexistent file.

Action: Specify another file.
Level: 1

Type: ERROR

Impact: Other

BRW-15267: File {1} already exists

Cause: User tried to save under the name of an existing file.

Action: Specify another file name.
Level: 1

Type: ERROR

Impact: Other

BRW-15268: Unable to open file {1}

Cause: I/O core was unable to open a file.

Action: Specify another file.
Level: 1

Type: ERROR

Impact: Other

BRW-15269: Unable to lock file {1}

Cause: I/O core was unable to lock a file.

Action: Specify another file.
Level: 1

Type: ERROR

Impact: Other

BRW-15270: Error reading file {1}

Cause: Operating system error or file was not of the correct format.

Action: Specify another file.
Level: 1

Type: ERROR

Impact: Other

BRW-15271: Error writing file {1}

Cause: Operating system error or I/O core error.

Action: Retry operation.
Level: 1

Type: ERROR

Impact: Other

BRW-15272: Obsolete Query Builder document {1}

Cause: User attempted to open an old unsupported document.

Action: Specify another document.
Level: 1

Type: ERROR

Impact: Other

BRW-15273: File {1} is not a Query Builder file

Cause: User attempted to open a non-Browser file.

Action: Specify another file to open.
Level: 1

Type: ERROR

Impact: Other

BRW-15274: File {1} is not a valid SQL file

Cause: User attempted to import an invalid SQL file.

Action: Specify another file to import.
Level: 1

Type: ERROR

Impact: Other

BRW-15275: No data to export or print

Cause: User attempted to export or print a query (or region) with no data.

Action: Specify another region; execute query; change query.
Level: 1

Type: ERROR

Impact: Data

BRW-15277: Unable to overwrite current table {1}

Cause: Error in trying to delete/rename old data table in save.

Action: Fix problem with data table and re-save.
Level: 1

Type: ERROR

Impact: Other

BRW-15278: Document saved, but view {1} could not be created

Cause: The query is not a valid view. It has been saved, but not as a database view.

Action: Redefine query as a valid view, or ignore (query will be saved, but not as a view).
Level: 1

Type: ERROR

Impact: Other

BRW-15279: '{1}' is not a recognized SQL literal

Cause: User attempted to import a non-SQLPlus file.

Action: Specify another file to import.
Level: 1

Type: ERROR

Impact: Other

BRW-15320: Internal I/O core error ({1}, line {2})

Cause: Internal State is invalid.

Action: Contact support.
Level: 1

Type: ERROR

Impact: Other

BRW-15321: Resource not found ({1}).

Cause: Resource names do not match Browser code (or file is corrupted).

Action: Get a correct version of the Browser resource file.
Level: 1

Type: ERROR

Impact: Other

BRW-15322: Resource file not found.

Cause: directory structure incorrect, or file is missing for some reason.

Action: Locate the resource file (check NLS_LANG file name).
Level: 1

Type: ERROR

Impact: Other

BRW-15323: Query already open in current application ({1})

Cause: User attempted to open multiple queries with the same name.

Action: Specify another file.
Level: 1

Type: ERROR

Impact: Other

BRW-15324: Unable to start up windowing system

Cause: Incorrect/missing environment variables (for example, DISPLAY, APIPATH).

Action: All required environment variables must be set correctly.
Level: 1

Type: ERROR

Impact: Other

BRW-15337: Maximum columns in index is {1}

Cause: Maximum columns in index reached.

Action: Create/modify index with less columns.
Level: 1

Type: ERROR

Impact: Other

BRW-15338: Cannot remove/modify index used to enforce unique/primary key

Cause: User tried to remove/modify the index used to enforce unique/primary key.

Action: First remove/modify primary key or unique key.
Level: 1

Type: ERROR

Impact: Other

BRW-15339: Cannot create, modify, or remove index on synonyms

Cause: User tried to create, modify, or remove the index for a synonym

Action: Create, modify, or remove index from base table instead.
Level: 1

Type: ERROR

Impact: Other

BRW-15340: Cannot modify constraints for a synonym.

Cause: Modifying constraints of a synonym is not allowed.

Action: Modify constraint of base data table instead.
Level: 1

Type: ERROR

Impact: Other

BRW-15341: Base table can only be modified after committing duplicated table

Cause: User tried to modify a base data table that has been duplicated.

Action: Commit the duplicated table first.
Level: 1

Type: ERROR

Impact: Other

BRW-15342: Unable to find snapshot information

Cause: This database does not support snapshots (or database error).

Action: Check that you have a snapshot dictionary table.
Level: 1

Type: ERROR

Impact: Other

BRW-15343: Insufficient privileges to use DICTIONARY=NATIVE

Cause: You do not have access privileges to use the NATIVE dictionary.

Action: Use DICTIONARY=ENDUSER instead. This can be specified on the command line.
Level: 1

Type: ERROR

Impact: Other

BRW-15344: Insufficient privileges to use DICTIONARY=ENDUSER

Cause: You do not have access privileges to use the ENDUSER dictionary

Action: Use DICTIONARY=NATIVE instead. This can be specified on the command line.
Level: 1

Type: ERROR

Impact: Other

BRW-15345: Cannot load MVIEW$_ or SNAP$_ tables. Load snapshot instead.

Cause: Trying to import sql which uses MVIEW$_ or SNAP$_ of snapshot.

Action: Load the snapshot itself instead.
Level: 1

Type: ERROR

Impact: Other

BRW-15346: Cannot REVOKE privileges you did not grant

Cause: User trying to revoke privileges that he/she did not grant.

Action: The user who grants the privileges should revoke those privileges.
Level: 1

Type: ERROR

Impact: Other

BRW-15347: Cannot grant EXECUTE privilege on tables

Cause: Trying to grant EXECUTE privilege on tables.

Action: EXECUTE privilege is only allowed on packages.
Level: 1

Type: ERROR

Impact: Other

BRW-15348: ALTER, INDEX, REFERENCES, or EXECUTE privileges not allowed on views

Cause: Trying to grant ALTER, INDEX, REFERENCES, or EXECUTE on views.

Action: This is not allowed.
Level: 1

Type: ERROR

Impact: Other

BRW-15349: Only SELECT privilege is allowed on snapshots

Cause: SELECT privilege is only allowed for snapshots.

Action: Grant only SELECT privilege on snapshots.
Level: 1

Type: ERROR

Impact: Other

BRW-15350: No privileges is allowed for synonyms

Cause: Trying to grant privileges on synonyms.

Action: This is not allowed.
Level: 1

Type: ERROR

Impact: Other

BRW-15351: Insufficient privileges. Operation denied.

Cause: User try to perform an operation without sufficient privileges.

Action: Try again after obtaining proper privileges from your DBA.
Level: 1

Type: ERROR

Impact: Other

BRW-15352: Cannot remove existing table columns

Cause: Trying to remove an existing table column.

Action: This operation is not supported by the database.
Level: 1

Type: ERROR

Impact: Other

BRW-15354: Cannot rename existing table columns

Cause: Trying to rename an existing data table column.

Action: This action is not supported by the database.
Level: 1

Type: ERROR

Impact: Other

BRW-15355: Cannot change indexed column datatype to LONG

Cause: Trying to change an indexed column type to a LONG datatype.

Action: This action is not supported by the database.
Level: 1

Type: ERROR

Impact: Other

BRW-15356: Removed tables cause referenced synonyms to be removed

Cause: User removed some data tables that have synonyms refer to them.

Action: None. This is a warning that synonyms are removed automatically.
Level: 1

Type: ERROR

Impact: Other

BRW-15357: Error in removing constraint {1}

Cause: Error in removing constraint.

Action: Try again.
Level: 1

Type: ERROR

Impact: Other

BRW-15358: Error in enabling/disabling constraints for {1}

Cause: Error in enabling/disabling constraints.

Action: Try again.
Level: 1

Type: ERROR

Impact: Other

BRW-15359: Cannot disable a key referred by a newly created FOREIGN key

Cause: Trying to disable a primary or unique key that a foreign key depends upon.

Action: Commit the foreign key first, then disable.
Level: 1

Type: ERROR

Impact: Other

BRW-15360: Foreign key refers to disabled PRIMARY/UNIQUE key {1}

Cause: Foreign key refers to a disabled primary key.

Action: Enable primary key for the foreign key to be created successfully.
Level: 1

Type: ERROR

Impact: Other

BRW-15361: Error in creating PRIMARY/UNIQUE constraints for {1}

Cause: Error in creating PRIMARY/UNIQUE constraints.

Action: Try again.
Level: 1

Type: ERROR

Impact: Other

BRW-15362: Error in creating FOREIGN constraints for {1}

Cause: Error in creating FOREIGN constraints.

Action: Try again.
Level: 1

Type: ERROR

Impact: Other

BRW-15363: Error in creating CHECK constraints for {1}

Cause: Error in creating CHECK constraints.

Action: Try again.
Level: 1

Type: ERROR

Impact: Other

BRW-15364: Length of VARCHAR2 column must be between {1} and {2}

Cause: Illegal range for length of VARCHAR2 column.

Action: Specify a legal length parameter.
Level: 1

Type: ERROR

Impact: Other

BRW-15365: Non-unique INDEX column cannot have PRIMARY/UNIQUE constraint

Cause: User tried to create PRIMARY/UNIQUE constraints on a non-unique index.

Action: Remove the index, and recreate as a unique index.
Level: 1

Type: ERROR

Impact: Other

BRW-15366: PRIMARY/UNIQUE column cannot have non-unique index

Cause: Trying to create a non-unique index with PRIMARY/UNIQUE columns.

Action: Set the index to UNIQUE. Remove and recreate.
Level: 1

Type: ERROR

Impact: Other

BRW-15367: Cannot rename snapshots

Cause: User tried to rename a snapshot

Action: This is not allowed.
Level: 1

Type: ERROR

Impact: Other

BRW-15368: Error in altering snapshot {1}

Cause: Internal error.

Action: Try again.
Level: 1

Type: ERROR

Impact: Other

BRW-15369: Error in creating snapshot {1}

Cause: Internal error.

Action: Try again.
Level: 1

Type: ERROR

Impact: Other

BRW-15370: Cannot add columns to a table duplicated with data

Cause: Trying to add columns to an uncommitted data table (duplicated with data).

Action: Commit first, then add columns
Level: 1

Type: ERROR

Impact: Data

BRW-15371: Comment too long (max {1} bytes)

Cause: The comment specified for the data table or column is too long.

Action: Shorten the comment.
Level: 1

Type: ERROR

Impact: Other

BRW-15372: Cannot set comment for synonym

Cause: User tried to create a comment for a synonym.

Action: Create the comment on the table or view instead.
Level: 1

Type: ERROR

Impact: Other

BRW-15373: Cannot create primary, unique, foreign key, or index on LONG columns

Cause: These operations cannot be performed on LONG columns.

Action: Do not attempt to perform this operation.
Level: 1

Type: ERROR

Impact: Other

BRW-15374: Cannot remove tables that are referenced

Cause: User tried to remove a table with primary or unique keys that are referenced.

Action: Remove referencing table first.
Level: 1

Type: ERROR

Impact: Other

BRW-15375: Cannot create index through database link

Cause: User tried to create an index through a database link.

Action: Login directly then create index.
Level: 1

Type: ERROR

Impact: Other

BRW-15376: Cannot create constraint through database link

Cause: User tried to create a constraint through a database link.

Action: Login directly then create constraint.
Level: 1

Type: ERROR

Impact: Other

BRW-15377: Create or remove constraint is only for table

Cause: User tried to create or remove a constraint on non-table database object.

Action: This action is not supported.
Level: 1

Type: ERROR

Impact: Other

BRW-15378: Table already removed. Create/remove on constraint ignored

Cause: User tried to create or remove a constraint on an already removed table.

Action: Revert table before further modifying it.
Level: 1

Type: ERROR

Impact: Other

BRW-15379: Primary or unique already exists

Cause: Duplicate primary or unique key.

Action: No action required.
Level: 1

Type: ERROR

Impact: Other

BRW-15380: Foreign key must reference primary or unique key

Cause: The specified foreign key does not reference a primary or unique key.

Action: Make sure the foreign key references a primary or unique key.
Level: 1

Type: ERROR

Impact: Other

BRW-15381: Number of columns mismatch between foreign and primary/unique key

Cause: The foreign key does not match the number of columns in the primary or unique key.

Action: Make sure the number of columns are the same.
Level: 1

Type: ERROR

Impact: Other

BRW-15382: Foreign key already exists

Cause: Foreign key already exists.

Action: No action required.
Level: 1

Type: ERROR

Impact: Other

BRW-15383: A table can only have one primary key

Cause: User tried to specify more than one primary key per table.

Action: Remove the old primary key and recreate it.
Level: 1

Type: ERROR

Impact: Other

BRW-15384: Cannot remove or modify a keys referenced by foreign keys

Cause: Primary or unique key is referenced by foreign keys.

Action: Remove foreign keys first then remove primary/unique keys.
Level: 1

Type: ERROR

Impact: Other

BRW-15385: Cannot duplicate view from PUBLIC database link as a view

Cause: Unable to read SQL statement (LONG column) from PUBLIC database link.

Action: This action is not supported.
Level: 1

Type: ERROR

Impact: Other

BRW-15386: Circular reference detected in synonym {1}

Cause: The synonym has a circular reference in the data dictionary.

Action: Do not include the particular synonym.
Level: 1

Type: ERROR

Impact: Other

BRW-15387: Login failed

Cause: Database or SQLNet error occurred.

Action: Check the login information and try again.
Level: 1

Type: ERROR

Impact: Other

BRW-15388: Unable to load database relationships

Cause: Schema internal error in loading database relationships.

Action: Contact support if this is not expected.
Level: 1

Type: ERROR

Impact: Other

BRW-15389: Unable to load list of accessible owners

Cause: Schema internal error in loading list of accessible owners.

Action: Contact support if this is not expected.
Level: 1

Type: ERROR

Impact: Other

BRW-15390: Unable to load list of accessible tables

Cause: Schema internal error in loading list of data tables.

Action: Contact support if this is not expected.
Level: 1

Type: ERROR

Impact: Other

BRW-15391: Unable to load table

Cause: Schema internal error in loading data table.

Action: Contact support if this is not expected.
Level: 1

Type: ERROR

Impact: Other

BRW-15392: Unable to load table

Cause: Schema internal error in loading table.

Action: Contact support if this is not expected.
Level: 1

Type: ERROR

Impact: Other

BRW-15393: Unable to load synonym

Cause: Schema internal error in loading synonym.

Action: Contact support if this is not expected.
Level: 1

Type: ERROR

Impact: Other

BRW-15394: Unable to load query

Cause: Schema internal error in loading query.

Action: Contact support if this is not expected.
Level: 1

Type: ERROR

Impact: Other

BRW-15395: Unable to load table column information

Cause: Schema internal error in loading column information.

Action: Contact support if this is not expected.
Level: 1

Type: ERROR

Impact: Other

BRW-15396: Unable to load synonym column information

Cause: Schema internal error in loading synonym column information.

Action: Contact support if this is not expected.
Level: 1

Type: ERROR

Impact: Other

BRW-15397: Unable to load constraints

Cause: Schema internal error in loading constraints.

Action: Contact support if this is not expected.
Level: 1

Type: ERROR

Impact: Other

BRW-15398: Unable to find primary key information

Cause: Schema internal error in finding primary keys.

Action: Contact support if this is not expected.
Level: 1

Type: ERROR

Impact: Other

BRW-15399: Unable to find foreign key information

Cause: Schema internal error in finding foreign keys.

Action: Contact support if this is not expected.
Level: 1

Type: ERROR

Impact: Other

BRW-15400: Unable to load table and column comments

Cause: Schema internal error in getting comments.

Action: Contact support if this is not expected.
Level: 1

Type: ERROR

Impact: Other

BRW-15401: Error in loading database link {1}

Cause: Schema internal error in loading database link.

Action: Refer to accompanying error messages for more information.
Level: 1

Type: ERROR

Impact: Other

BRW-15402: Error in loading owner {1}

Cause: Schema internal error in loading database link.

Action: Refer to accompanying error messages for more information.
Level: 1

Type: ERROR

Impact: Other

BRW-15403: Error in loading table {1}

Cause: Schema internal error in loading data table.

Action: Refer to accompanying error messages for more information.
Level: 1

Type: ERROR

Impact: Other

BRW-15404: Error in loading primary key constraint for {1} ({2})

Cause: Schema internal error in loading primary constraint.

Action: Refer to accompanying error messages for more information.
Level: 1

Type: ERROR

Impact: Other

BRW-15405: Error in loading foreign key constraint {1}

Cause: Schema internal error in loading foreign constraint.

Action: Refer to accompanying error messages for more information.
Level: 1

Type: ERROR

Impact: Other

BRW-15406: Error in loading synonym {1}

Cause: Schema internal error in loading primary constraint.

Action: Refer to accompanying error messages for more information.
Level: 1

Type: ERROR

Impact: Other

BRW-15407: Table referred to by synonym {1} no longer exists

Cause: User tried to create a synonym for a nonexistent data table.

Action: Recreate the synonym.
Level: 1

Type: ERROR

Impact: Other

BRW-15408: Error in loading column information for {1}

Cause: Oracle error or the data table has been removed.

Action: Recreate the data table.
Level: 1

Type: ERROR

Impact: Other

BRW-15409: Error in loading constraint information for {1} ({2})

Cause: Oracle error.

Action: Try it again.
Level: 1

Type: ERROR

Impact: Other

BRW-15410: Table that foreign key {1} ({2}) refers to is inaccessible

Cause: The table that the foreign key refers to is inaccessible.

Action: Grant the table to the current user.
Level: 1

Type: ERROR

Impact: Other

BRW-15411: Logout failed

Cause: Internal error in logging out.

Action: Exit or close the document.
Level: 1

Type: ERROR

Impact: Other

BRW-15412: Table of query {1} was modified. Query loaded as view.

Cause: The view that the query depends on has been modified after the last save.

Action: Open the query and save it again to use it as a data table.
Level: 1

Type: ERROR

Impact: Other

BRW-15413: Table of query {1} was removed. Query will not be loaded.

Cause: The view that the query depends on has been removed.

Action: Open the query, and save it again to use it as a data table.
Level: 1

Type: ERROR

Impact: Other

BRW-15414: Table {1} no longer exists

Cause: This data table no longer exists in the database.

Action: Contact system administrator if you need this table.
Level: 1

Type: ERROR

Impact: Other

BRW-15415: Maximum number (254) of table columns exceeded

Cause: User tried to load a data table that has more than 254 columns.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

BRW-15416: Maximum number (8192) of tables per user exceeded

Cause: User owns too many data tables.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

BRW-15417: Maximum number (1024) of owners and databases exceeded

Cause: User tried to load too many user, owner, and database links.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

BRW-15418: Unable to find database link information

Cause: This database does not support database link, or database error.

Action: Try again later if this is unexpected.
Level: 1

Type: ERROR

Impact: Other

BRW-15419: Unable to find synonym information

Cause: This database does not support synonyms, or database error.

Action: Try again later if this is unexpected.
Level: 1

Type: ERROR

Impact: Other

BRW-15420: Unable to find constraint information

Cause: This database does not support constraints, or database error.

Action: Try again later if this is unexpected.
Level: 1

Type: ERROR

Impact: Other

BRW-15421: Unable to find table comment table

Cause: This database does not support comments on table, or database error.

Action: Try again later if this is unexpected.
Level: 1

Type: ERROR

Impact: Other

BRW-15422: Unable to find table Column comments table

Cause: This database does not support comments on column, or database error.

Action: Try again later if this is unexpected.
Level: 1

Type: ERROR

Impact: Other

BRW-15423: Synonym to SEQUENCE is not currently supported

Cause: User tried to load a synonym that refers to a sequence.

Action: This action is not supported.
Level: 1

Type: ERROR

Impact: Other

BRW-15424: Maximum number of login attempts (3) exceeded

Cause: User tried to login too many times.

Action: Contact system administrator for correct username, password, and connect strings.
Level: 1

Type: ERROR

Impact: Other

BRW-15425: End User Layer dictionary not installed

Cause: The End User Layer meta-data dictionary was not found.

Action: Install the End User Layer dictionary or run with DICTIONARY=NATIVE option.
Level: 1

Type: ERROR

Impact: Other

BRW-15430: Index information not loaded

Cause: Cannot find index table.

Action: This is a non-Oracle database; try an ODBC driver.
Level: 1

Type: ERROR

Impact: Other

BRW-15433: Create snapshot with only {1} maximum columns.

Cause: User tried to create more than the maximum number of allowed columns in a snapshot.

Action: Create fewer columns.
Level: 1

Type: ERROR

Impact: Other

BRW-15434: Maximum columns in table is {1}

Cause: User tried to create more than the maximum number of allowed columns in a table.

Action: Create fewer columns.
Level: 1

Type: ERROR

Impact: Other

BRW-15435: DBA privilege is needed to perform this operation

Cause: Need DBA privileges.

Action: Ask your system administrator to grant you DBA privilege.
Level: 1

Type: ERROR

Impact: Other

BRW-15437: Index already exists

Cause: User tried to create an index that is the same as an already existing index.

Action: No action required.
Level: 1

Type: ERROR

Impact: Other

BRW-15438: Index must be on columns from the same table

Cause: user tried to create an index on columns from different tables.

Action: Create the index on columns from the same table.
Level: 1

Type: ERROR

Impact: Other

BRW-15439: Cannot create new tables through database links

Cause: User tried to create data tables through database links.

Action: This operation is not allowed. Login directly then create.
Level: 1

Type: ERROR

Impact: Other

BRW-15440: New columns cannot be created through database links

Cause: User tried to create columns through database links.

Action: This operation is not allowed. Login directly and create.
Level: 1

Type: ERROR

Impact: Other

BRW-15441: User has no CREATE INDEX privilege

Cause: User tried to create an index on data table without proper privileges

Action: Obtain CREATE INDEX privilege on this data table.
Level: 1

Type: ERROR

Impact: Other

BRW-15444: Adding columns is only supported for tables

Cause: User tried to add columns to a view, snapshot, synonym, or query.

Action: This operation is not allowed.
Level: 1

Type: ERROR

Impact: Other

BRW-15445: Cannot remove columns of synonyms, duplicated views or snapshots

Cause: User tried to remove columns from a view, snapshot, synonym, or query.

Action: This operation is not allowed.
Level: 1

Type: ERROR

Impact: Other

BRW-15446: Unable to copy constraints for {1}

Cause: Error duplicating constraints.

Action: No action required.
Level: 1

Type: ERROR

Impact: Other

BRW-15447: Cannot remove Query. Use File Delete... from Query window

Cause: User tried to remove a query.

Action: This is not legal from the Schema Builder. Use the Query window instead.
Level: 1

Type: ERROR

Impact: Other

BRW-15448: Cannot copy Query. Use File Save As... from Query window

Cause: User tried to copy a query.

Action: This is not legal from the Schema Builder. Use the Query window instead.
Level: 1

Type: ERROR

Impact: Other

BRW-15449: Cannot copy with data from table with only LONG columns

Cause: User tried to copy a table with a LONG column.

Action: Database does not support this.
Level: 1

Type: ERROR

Impact: Data

BRW-15450: Operation not allowed on removed table

Cause: User tried to do something to a removed data table.

Action: Undo the remove first.
Level: 1

Type: ERROR

Impact: Other

BRW-15451: Operation not allowed on removed column

Cause: User tried to do something to a removed column.

Action: Undo the remove first.
Level: 1

Type: ERROR

Impact: Other

BRW-15452: Cannot rename another owner's table

Cause: User tried to set the name of a granted data table.

Action: This is not allowed. Ask the owner to do it for you.
Level: 1

Type: ERROR

Impact: Other

BRW-15453: Cannot rename table at database link

Cause: User tried to set the name on a data table at a database link.

Action: Ask the owner to do this for you.
Level: 1

Type: ERROR

Impact: Other

BRW-15454: Renaming columns is only supported on table and view columns

Cause: User tried to set column name for a snapshot, synonym, or query.

Action: This is not allowed.
Level: 1

Type: ERROR

Impact: Other

BRW-15455: Setting column type is only supported on table columns

Cause: User tried to set column type for a view, snapshot, synonym, or query.

Action: This is not allowed.
Level: 1

Type: ERROR

Impact: Other

BRW-15456: Cannot change column type of an existing column

Cause: User tried to change column type of an existing column.

Action: This is not allowed.
Level: 1

Type: ERROR

Impact: Other

BRW-15457: Default values are allowed only on table columns

Cause: User tried to set default for a synonym, snapshot, view, or query.

Action: This is not allowed.
Level: 1

Type: ERROR

Impact: Other

BRW-15458: Setting length is supported only on table columns

Cause: User tried to set length for a synonym, snapshot, view, or query.

Action: This is not allowed.
Level: 1

Type: ERROR

Impact: Other

BRW-15459: Cannot set length for DATE, LONG, or ROWID datatypes

Cause: User tried to set the length for DATE, LONG, or ROWID datatypes.

Action: This is not allowed.
Level: 1

Type: ERROR

Impact: Other

BRW-15460: Setting scale is allowed only on table columns

Cause: User tried to set scale for synonym, snapshot, view, or query columns.

Action: This is not allowed.
Level: 1

Type: ERROR

Impact: Other

BRW-15461: Cannot set scale for DATE, LONG, or ROWID datatypes

Cause: User tried to set scale for DATE, LONG, or ROWID columns.

Action: This is not allowed.
Level: 1

Type: ERROR

Impact: Other

BRW-15462: Setting precision is allowed only on table columns

Cause: User tried to set precision for synonym, snapshot, view, or query columns.

Action: This is not allowed.
Level: 1

Type: ERROR

Impact: Other

BRW-15463: Setting precision is allowed only on NUMBER datatype

Cause: User tried to set precision on columns other than NUMBER.

Action: This is not allowed.
Level: 1

Type: ERROR

Impact: Other

BRW-15464: Altering column position is allowed only on table columns

Cause: User tried to set column position on non-table database objects.

Action: This is not allowed.
Level: 1

Type: ERROR

Impact: Other

BRW-15465: Cannot change the position of existing column.

Cause: User tried to change column position of existing table.

Action: This is not allowed.
Level: 1

Type: ERROR

Impact: Other

BRW-15466: Table name too long (Max {1} bytes)

Cause: Data Table name to long.

Action: Shorten the name and try again.
Level: 1

Type: ERROR

Impact: Other

BRW-15467: Name already in use. Please choose another name.

Cause: Name already in use.

Action: Choose another name.
Level: 1

Type: ERROR

Impact: Other

BRW-15468: Column name too long (Max {1} bytes)

Cause: Column name too long.

Action: Shorten the name and try again.
Level: 1

Type: ERROR

Impact: Other

BRW-15469: Length of NUMBER column must be between {1} and {2}

Cause: Illegal range for length of NUMBER column.

Action: Specify a legal length parameter.
Level: 1

Type: ERROR

Impact: Other

BRW-15470: Length of CHAR or RAW column must be between {1} and {2}

Cause: Illegal range for length of CHAR column.

Action: Specify a legal length parameter.
Level: 1

Type: ERROR

Impact: Other

BRW-15471: Precision must be between {1} and {2}

Cause: Illegal range for precision.

Action: Specify a legal length parameter.
Level: 1

Type: ERROR

Impact: Other

BRW-15472: Cannot decrease length of existing column

Cause: User tried to decrease the length of an existing column.

Action: This is not allowed.
Level: 1

Type: ERROR

Impact: Other

BRW-15473: Cannot decrease scale of existing column

Cause: User tried to decrease scale of an existing column.

Action: This is not allowed.
Level: 1

Type: ERROR

Impact: Other

BRW-15474: Cannot decrease precision of existing column

Cause: User tried to decrease precision of an existing column.

Action: This is not allowed.
Level: 1

Type: ERROR

Impact: Other

BRW-15475: Table can have at most one LONG column

Cause: User tried to create more than one LONG or RAW column per table.

Action: This is not allowed.
Level: 1

Type: ERROR

Impact: Other

BRW-15476: Error in loading index for {1}

Cause: Internal error.

Action: Contact support.
Level: 1

Type: ERROR

Impact: Other

BRW-15477: Error in creating table {1}

Cause: Internal error.

Action: Contact support.
Level: 1

Type: ERROR

Impact: Other

BRW-15478: Error in creating view {1}

Cause: Internal error.

Action: Contact support.
Level: 1

Type: ERROR

Impact: Other

BRW-15479: Error in creating synonym {1}

Cause: Internal error.

Action: Contact support.
Level: 1

Type: ERROR

Impact: Other

BRW-15480: Error in creating index {1}

Cause: Internal error.

Action: Contact support.
Level: 1

Type: ERROR

Impact: Other

BRW-15481: Error in dropping {1}

Cause: Internal error.

Action: Contact support.
Level: 1

Type: ERROR

Impact: Other

BRW-15482: Error in dropping table {1}

Cause: Internal error.

Action: Contact support.
Level: 1

Type: ERROR

Impact: Other

BRW-15483: Error in dropping view {1}

Cause: Internal error.

Action: Contact support.
Level: 1

Type: ERROR

Impact: Other

BRW-15484: Error in dropping synonym {1}

Cause: Internal error.

Action: Contact support.
Level: 1

Type: ERROR

Impact: Other

BRW-15485: Error in dropping index {1}

Cause: Internal error.

Action: Contact support.
Level: 1

Type: ERROR

Impact: Other

BRW-15486: Error in renaming {1}

Cause: Internal error.

Action: Contact support.
Level: 1

Type: ERROR

Impact: Other

BRW-15487: Error in setting comment for table {1}

Cause: Internal error.

Action: Contact support.
Level: 1

Type: ERROR

Impact: Other

BRW-15488: Error in setting comment for column {1}

Cause: Internal error.

Action: Contact support.
Level: 1

Type: ERROR

Impact: Other

BRW-15489: Error in loading index {1} for {2}

Cause: Internal error.

Action: Contact support.
Level: 1

Type: ERROR

Impact: Other

BRW-15490: Error in loading table privilege for {1}

Cause: Internal error.

Action: Contact support.
Level: 1

Type: ERROR

Impact: Other

BRW-15491: Error in loading column privilege for {1}

Cause: Internal error.

Action: Contact support.
Level: 1

Type: ERROR

Impact: Other

BRW-15492: Error in altering table {1}

Cause: Internal error.

Action: Contact support.
Level: 1

Type: ERROR

Impact: Other

BRW-15493: Operation currently not supported

Cause: Internal error.

Action: Contact support.
Level: 1

Type: ERROR

Impact: Other

BRW-15494: Error in loading SQL text of views

Cause: Internal error.

Action: Contact support.
Level: 1

Type: ERROR

Impact: Other

BRW-15495: Error in loading SQL text for view {1}

Cause: Internal error.

Action: Contact support.
Level: 1

Type: ERROR

Impact: Other

BRW-15496: Scale must be between {1} and {2}

Cause: Illegal value for scale.

Action: Input legal value for scale.
Level: 1

Type: ERROR

Impact: Other

BRW-15497: Index can only be created on TABLE columns

Cause: User tried to create index on a database object other than a TABLE.

Action: Create index on TABLE columns only.
Level: 1

Type: ERROR

Impact: Other

BRW-15498: Cannot modify a query

Cause: It is not legal to modify a query.

Action: Open the query and modify it as a Browser document.
Level: 1

Type: ERROR

Impact: Other

BRW-15499: Cannot set column attributes of table duplicated with data

Cause: User tried to set the column type of a table duplicated with data.

Action: First commit the table then try again.
Level: 1

Type: ERROR

Impact: Data

BRW-15500: {1}

Cause: Oracle error

Action: None.
Level: 1

Type: ERROR

Impact: Other

BRW-15501: No more application virtual memory

Cause: No more disk space or system memory for Virtual Memory Manager.

Action: Close a document or make some room on your disk.
Level: 1

Type: ERROR

Impact: Memory

BRW-15502: Can only have {1} rows per document

Cause: Exceeded self-imposed, compile-time row maximum.

Action: Consider adding conditions to the query.
Level: 1

Type: ERROR

Impact: Other

BRW-15504: Unable to determine database character set

Cause: There was a problem with SELECT USERENV('LANGUAGE') FROM DUAL.

Action: Non-Oracle database--not supported.
Level: 1

Type: ERROR

Impact: Other

BRW-15505: Unable to open virtual memory file

Cause: No write permission or file system full.

Action: Change permission on directory or delete some files.
Level: 1

Type: ERROR

Impact: Memory

BRW-15506: Unable to close virtual memory file

Cause: Operating system error.

Action: Ask system administrator for assistance.
Level: 1

Type: ERROR

Impact: Memory

BRW-15507: Unable to read from virtual memory file

Cause: Virtual memory file does not exist.

Action: Make sure the virtual memory file is opened.
Level: 1

Type: ERROR

Impact: Memory

BRW-15508: Unable to write to virtual memory file

Cause: File system is full, or virtual memory file was not opened.

Action: Delete some files. Make sure virtual memory file is opened.
Level: 1

Type: ERROR

Impact: Memory

BRW-15509: Unable to create virtual memory manager

Cause: Internal error, or out of memory.

Action: Ask system administrator for assistance.
Level: 1

Type: ERROR

Impact: Memory

BRW-15511: Maximum virtual memory size exceeded

Cause: User input is too big for virtual memory size.

Action: Try again.
Level: 1

Type: ERROR

Impact: Memory

BRW-15513: Null value in command '{1}'

Cause: User entered &lt;command&gt;= on the command line with no option selected.

Action: Add a value for &lt;command&gt;.
Level: 1

Type: ERROR

Impact: Other

BRW-15514: Null command in command line

Cause: User entered =&lt;value&gt; at command line but did not specify a command.

Action: Add the command.
Level: 1

Type: ERROR

Impact: Other

BRW-15515: Unrecognized command '{1}' in command line

Cause: User entered an illegal command at command line.

Action: Change command.
Level: 1

Type: ERROR

Impact: Other

BRW-15516: Command '{1}' specified twice in command line

Cause: User entered a command twice at command line.

Action: Remove one.
Level: 1

Type: ERROR

Impact: Other

BRW-15517: Incompatible commands '{1}' and '{2}' specified

Cause: User entered 2 incompatible commands at command line.

Action: Remove one.
Level: 1

Type: ERROR

Impact: Other

BRW-15518: Invalid option '{1}' in command '{2}'

Cause: User entered an illegal option to a command at command line.

Action: Change option.
Level: 1

Type: ERROR

Impact: Other

BRW-15519: Multiple login specifications in command line

Cause: User entered 2 login specifications at command line.

Action: Remove one.
Level: 1

Type: ERROR

Impact: Other

BRW-15520: Invalid document name '{1}' in command line

Cause: User entered an illegal document name at command line.

Action: Change document name.
Level: 1

Type: ERROR

Impact: Other

BRW-15521: '{1}' command specified without a document

Cause: User entered a command without specifying a document at command line.

Action: Add missing document.
Level: 1

Type: ERROR

Impact: Other

BRW-15522: '{1}' command specified without '{2}'

Cause: User entered a command without another required command.

Action: Add missing command.
Level: 1

Type: ERROR

Impact: Other

BRW-15523: Mismatched parentheses in '{1}' command

Cause: User entered mismatched parentheses in the command line.

Action: Correct mismatched parentheses.
Level: 1

Type: ERROR

Impact: Other

BRW-15530: Cannot edit a deleted row

Cause: User tried to edit a row which is marked for deletion.

Action: Undelete the row first.
Level: 1

Type: ERROR

Impact: Other

BRW-15531: Row has been deleted from the database

Cause: Another user deleted this row since you last ran the query.

Action: Contact support. This should never happen.
Level: 1

Type: ERROR

Impact: Other

BRW-15532: Row has been modified by another user. Requery.

Cause: Another user updated this row since you last ran the query.

Action: Try again.
Level: 1

Type: ERROR

Impact: Other

BRW-15533: Row is currently locked by another user.

Cause: Someone else is editing this row.

Action: Try again later.
Level: 1

Type: ERROR

Impact: Other

BRW-15539: Error in inserting {1} row(s)

Cause: One or more rows in input file failed on insert.

Action: Modify input file or ignore.
Level: 1

Type: ERROR

Impact: Other

BRW-15540: Operation not allowed on data of this type

Cause: User tried to edit a cell with data of an uneditable type.

Action: Unknown.
Level: 1

Type: ERROR

Impact: Data

BRW-15541: Too many edited rows. Please select Commit

Cause: Too many pending INSERTS, UPDATES or DELETES in a document.

Action: Select Commit or Revert.
Level: 1

Type: ERROR

Impact: Other

BRW-15545: Error in reading QXF file. Parsing halted.

Cause: Syntax error in reading QXF file.

Action: Fix QXF file.
Level: 1

Type: ERROR

Impact: Other

BRW-15546: Parse Error: Line {1}

Cause: Syntax at that particular line.

Action: Debug that line.
Level: 1

Type: ERROR

Impact: Other

BRW-15547: Operator unspecified in relationship block.

Cause: Operator unspecified in relationship block in QXF File.

Action: Specify an operator field within the block.
Level: 1

Type: ERROR

Impact: Other

BRW-15548: Error: Argument missing in {1} of relationship block.

Cause: No argument in a column field in a relationship block. No argument in the CONDITION_TEXT field within condition block.

Action: Specify the column name in that field. Specify the CONDITION_TEXT field.
Level: 1

Type: ERROR

Impact: Other

BRW-15550: Illegal INCLUSION_ORDER value ({1}) in expression {2}.

Cause: Illegal INCLUSION_ORDER value in expression.

Action: Correct INCLUSION_ORDER value.
Level: 1

Type: ERROR

Impact: Other

BRW-15551: Expression {1} included but INCLUSION_ORDER unspecified.

Cause: The INCLUSION_ORDER unspecified for an included expression block.

Action: Specify the INCLUSION_ORDER field.
Level: 1

Type: ERROR

Impact: Other

BRW-15552: Expression {1} not included but INCLUSION_ORDER is non-null

Cause: Expression is not included (INCLUDED = FALSE) but INCLUSION_ORDER is non-null.

Action: Correct the values in these fields.
Level: 1

Type: ERROR

Impact: Other

BRW-15553: Error: Empty TEXT string in expression {1}.

Cause: The TEXT string is unspecified within a QXF expression block.

Action: Specify the TEXT string.
Level: 1

Type: ERROR

Impact: Other

BRW-15554: Error: SORT_PRIORITY unspecified for sorted expression {1}.

Cause: SORT_PRIORITY unspecified for sorted expression.

Action: Specify the SORT_PRIORITY.
Level: 1

Type: ERROR

Impact: Other

BRW-15555: Illegal INCLUSION_ORDER value for field {1}in table {2}.

Cause: Illegal INCLUSION_ORDER value for field.

Action: Correct the INCLUSION_ORDER value.
Level: 1

Type: ERROR

Impact: Other

BRW-15556: Field {1} in table {2} included but INCLUSION_ORDER is null.

Cause: Field is included (INCLUDED = FALSE) but INCLUSION_ORDER is unspecified.

Action: Correct the values in these fields.
Level: 1

Type: ERROR

Impact: Other

BRW-15557: Field {1} (table {2}) excluded but INCLUSION_ORDER exists.

Cause: The field in specified data table is not included but the INCLUSION_ORDER is non-null.

Action: Correct the values in these fields.
Level: 1

Type: ERROR

Impact: Other

BRW-15558: SORT_PRIORITY unspecified for sorted field {1} in table {2}.

Cause: SORT_PRIORITY unspecified for a sorted field.

Action: Specify the SORT_PRIORITY for that field.
Level: 1

Type: ERROR

Impact: Other

BRW-15559: Error: Illegal value ({1}) for INCLUSION_ORDER in table {2}.

Cause: A negative value in inclusion order.

Action: Correct that value.
Level: 1

Type: ERROR

Impact: Other

BRW-15560: Table {1} included but INCLUSION_ORDER unspecified.

Cause: Data Table included (INCLUDED = TRUE) but INCLUSION_ORDER is unspecified.

Action: Correct the values in these fields.
Level: 1

Type: ERROR

Impact: Other

BRW-15561: Table {1} is excluded but INCLUSION_ORDER is non-null.

Cause: Data Table not included (INCLUDED = FALSE) but INCLUSION_ORDER is non-null.

Action: Correct the values in these fields.
Level: 1

Type: ERROR

Impact: Other

BRW-15562: Error: There should be no more than one main condition block.

Cause: There are more than one main (root) condition blocks.

Action: Eliminate some condition blocks, or use a conjunction.
Level: 1

Type: ERROR

Impact: Other

BRW-15563: Error: QXF file version 1.0 expected.

Cause: Illegal version number specified in VERSION field.

Action: Modify the version.
Level: 1

Type: ERROR

Impact: Other

BRW-15564: Parse Error: Line {1}: Invalid font style {2}.

Cause: Invalid font style.

Action: Check font style and correct it.
Level: 1

Type: ERROR

Impact: Other

BRW-15565: Parse Error: Line {1}: Invalid font style argument.

Cause: Invalid font style argument.

Action: Check font style strings and correct them.
Level: 1

Type: ERROR

Impact: Other

BRW-15566: Parse Error: Line {1}: Invalid aggregate function {2}

Cause: Invalid aggregate function name.

Action: Correct the function name.
Level: 1

Type: ERROR

Impact: Other

BRW-15567: Parse Error: Line {1}: Invalid summarize argument.

Cause: Invalid summarize field argument.

Action: Correct the field argument.
Level: 1

Type: ERROR

Impact: Other

BRW-15568: Parse Error: Line {1}: Invalid field argument.

Cause: Invalid field argument.

Action: Correct field argument.
Level: 1

Type: ERROR

Impact: Other

BRW-15569: Warning: QXF file is only partially loaded because of error.

Cause: Error in loading QXF file.

Action: Correct those errors.
Level: 1

Type: ERROR

Impact: Other

BRW-15570: Parse Error: Line {1}: Invalid operator {2} in relationship block.

Cause: Invalid Operator within relationship block.

Action: Check operator and correct it.
Level: 1

Type: ERROR

Impact: Other

BRW-15571: Parse Error: Line {1}: Invalid operator field argument.

Cause: Invalid Object ID within Derived Item Expression.

Action: Correct Object ID in dictionary.
Level: 1

Type: ERROR

Impact: Other

BRW-15572: Inconsistent object IDs in derived item expression.

Cause: Invalid operator field argument within relationship block.

Action: Check operator strings and correct them.
Level: 1

Type: ERROR

Impact: Other

BRW-15580: Unable to load list of accessible business areas

Cause: End User Layer is missing business area tables.

Action: Reinstall End User Layer. Ask system administrator for assistance.
Level: 1

Type: ERROR

Impact: Other

BRW-15581: Cannot add columns to table created with duplicate data

Cause: User tried to add columns to a table created with duplicate table data.

Action: Commit the duplicated table then try again.
Level: 1

Type: ERROR

Impact: Data

BRW-15582: New or duplicate table is only allowed on existing table.

Cause: Create new table on another new/duplicate/modified table.

Action: Commit the new/duplicate/modified table first.
Level: 1

Type: ERROR

Impact: Other

BRW-15583: Index requires at least one column

Cause: User tried to remove the last column of an index.

Action: Add other columns then remove.
Level: 1

Type: ERROR

Impact: Other

BRW-15584: Column {1} is of type LONG and will not be copied

Cause: Cannot copy a LONG column when creating a snapshot.

Action: Column cannot be copied.
Level: 1

Type: ERROR

Impact: Other

BRW-15600: Syntax not supported

Cause: Attempted to parse unsupported syntax

Action: Use alternate Oracle 8 syntax.
Level: 1

Type: ERROR

Impact: Other

BRW-15601: Invalid Oracle 8 SQL syntax

Cause: Cannot use Oracle 8 language syntax

Action: Use Oracle 7 SQL.
Level: 1

Type: ERROR

Impact: Other

BRW-15602: Type Constructor in Oracle 8 SQL is not supported

Cause: Oracle 8 SQL's type contructors are not supported.

Action: Revert to Oracle 7.
Level: 1

Type: ERROR

Impact: Other

BRW-15603: REF in Oracle 8 SQL is not supported

Cause: Oracle 8 SQL's REF is not supported.

Action: Use Oracle 7 instead.
Level: 1

Type: ERROR

Impact: Other

BRW-15604: CAST in Oracle 8 SQL is not supported

Cause: Oracle 8 SQL's CAST is not supported.

Action: Use Oracle 7 instead.
Level: 1

Type: ERROR

Impact: Other

BRW-15605: MULTISET in Oracle 8 SQL is not supported

Cause: Oracle 8 SQL's MULTISET is not supported.

Action: Use Oracle 7 intsead.
Level: 1

Type: ERROR

Impact: Other

BRW-15606: METHODS in Oracle 8 SQL is not supported

Cause: Oracle 8 SQL's METHODS is not supported.

Action: Use Oracle 7 instead.
Level: 1

Type: ERROR

Impact: Other

BRW-15607: THE subquery in Oracle 8 SQL is not supported

Cause: Oracle 8 SQL's THE subquery is not supported.

Action: Use Oracle 7 instead.
Level: 1

Type: ERROR

Impact: Other

BRW-15608: PARTITION of tables in Oracle 8 SQL is not supported

Cause: Oracle 8 SQL's PARTITION of tables is not supported.

Action: Use Oracle 7 instead.
Level: 1

Type: ERROR

Impact: Other

BRW-15609: The TABLE keyword in a subquery in Oracle 8 SQL is not supported

Cause: TABLE in subquery is not supported.

Action: Use Oracle 7 instead.
Level: 1

Type: ERROR

Impact: Other

BRW-15610: Rename the Table as a Table Alias

Cause: Attempt to use a table instead of a table alias

Action: Rename the table with a table alias.
Level: 1

Type: ERROR

Impact: Other

BRW-15641: Help system initialization failed. Help will be unavailable.

Cause: Unable to locate help document or help resource file.

Action: User may continue but help menu is unavailable. Use online or paper documentation.
Level: 1

Type: ERROR

Impact: Other

BRW-15643: Resource file not found ({1}), trying default resource file.

Cause: NLS_LANG set but file not found.

Action: Try to open the resource file using the default language.
Level: 1

Type: ERROR

Impact: Other

BRW-15644: Unable to locate help document ({1}), trying default help document.

Cause: NLS_LANG set but file not found.

Action: Try to open the help doc using the default language.
Level: 1

Type: ERROR

Impact: Other

BRW-15647: Unable to locate help document

Cause: Could not find help file in correct directory with correct language.

Action: Check Browser directory structure. Make sure NLS_LANG is set correctly.
Level: 1

Type: ERROR

Impact: Other

BRW-15648: Help system creation error

Cause: Help system could not start up.

Action: Browser could not find the help resource file, or NLS_LANG is not set, or memory is low.
Level: 1

Type: ERROR

Impact: Other

BRW-15649: Input for {1} was too low. Minimum valid number is {2}.

Cause: The value input was too low.

Action: Try again with a higher value.
Level: 1

Type: ERROR

Impact: Other

BRW-15650: Input for {1} was too high. Maximum valid number is {2}.

Cause: The value input was too high.

Action: Try again with a lower value.
Level: 1

Type: ERROR

Impact: Other

BRW-15651: Input for {1} was out of range. Must be between {2} and {3}.

Cause: The value input was out of the valid range.

Action: Try again with a valid number.
Level: 1

Type: ERROR

Impact: Other

BRW-15652: Value was reset to {1}.

Cause: The value input was changed because it was out of the valid range.

Action: Try again with a valid number or Browser will use the value shown.
Level: 1

Type: ERROR

Impact: Other

BRW-15653: Pref file error: Value {1} was too low. Minimum valid number is {2}.

Cause: The value input was too low.

Action: Try again with a higher value.
Level: 1

Type: ERROR

Impact: Other

BRW-15654: Pref file error: Value {1} was too high. Maximum valid number is {2}.

Cause: The value input was too high.

Action: Try again with a lower value.
Level: 1

Type: ERROR

Impact: Other

BRW-15655: Pref file error: Value {1} out of range. Must be between {2} and {3}.

Cause: The value input was out of the valid range.

Action: Try again with a valid number.
Level: 1

Type: ERROR

Impact: Other

BRW-15656: Pref file error: Value for {1} not recognized

Cause: The value set in the preference file was invalid.

Action: Try again with a valid number.
Level: 1

Type: ERROR

Impact: Other

BRW-15657: Value for OWNERLIST=NAME must contain at least one name

Cause: The value for OWNERLIST=NAME was NULL.

Action: Try again with a valid name
Level: 1

Type: ERROR

Impact: Other

BRW-15900: Unable to find time period information

Cause: This database does not support time periods, or database error.

Action: Try again later if this is unexpected.
Level: 1

Type: ERROR

Impact: Other

BRW-15901: Data source {1} referred to by object {2} no longer exists

Cause: Base data source of object has been removed.

Action: Refresh/delete object.
Level: 1

Type: ERROR

Impact: Data

BRW-15902: Table referred to by object {1} no longer exists

Cause: Base data source of object has been removed.

Action: Refresh/delete object.
Level: 1

Type: ERROR

Impact: Other

BRW-15903: Opposite table {1} is not in a business area. Join info inaccessible.

Cause: Relationship: Opposite data table/object not in any group.

Action: Grant that object to a group.
Level: 1

Type: ERROR

Impact: Other

BRW-15904: Relationship name cannot be longer than {1} bytes

Cause: Relationship Name longer than limit.

Action: Use a shorter name.
Level: 1

Type: ERROR

Impact: Other

BRW-15905: Column heading cannot be longer than {1} bytes

Cause: Item Heading longer than limit.

Action: Use a shorter heading.
Level: 1

Type: ERROR

Impact: Other

BRW-15906: Column format cannot be longer than {1} bytes

Cause: Item Format longer than limit.

Action: Use a shorter format.
Level: 1

Type: ERROR

Impact: Other

BRW-15907: Column display width cannot have more than {1} digits

Cause: Item Display Width Precision longer than limit.

Action: Use Shorter Display width.
Level: 1

Type: ERROR

Impact: Other

BRW-15908: Time period name cannot be longer than {1} bytes

Cause: Time Period Name too long.

Action: Use a shorter time period name.
Level: 1

Type: ERROR

Impact: Other

BRW-15909: Period column and sequence column of time period are the same

Cause: Period and sequence columns of time period set to the same column.

Action: make sure period and sequence columns are different.
Level: 1

Type: ERROR

Impact: Other

BRW-15910: Unable to load time period {1}

Cause: Schema internal error in loading time period.

Action: Refer to accompanying error messages for more information.
Level: 1

Type: ERROR

Impact: Other

BRW-15911: Time period {1} already exists

Cause: Time period name must be unique.

Action: Create time period under a different name.
Level: 1

Type: ERROR

Impact: Other

BRW-15912: Illegal display width value.

Cause: Illegal display width value.

Action: Re-enter a legal value.
Level: 1

Type: ERROR

Impact: Other

BRW-15913: {1} key text cannot be empty.

Cause: Foreign or Primary Key text is empty.

Action: Enter text for primary or foreign key.
Level: 1

Type: ERROR

Impact: Other

BRW-15914: Relationship name cannot be empty.

Cause: Relationship name is null.

Action: Enter relationship name.
Level: 1

Type: ERROR

Impact: Other

BRW-15924: Business area name cannot be empty

Cause: Business area name is empty or contains only spaces.

Action: Enter a new name.
Level: 1

Type: ERROR

Impact: Other

BRW-15925: Table {1} has already been imported as {2}

Cause: Table can only be imported once with a given name.

Action: Import table under a different name.
Level: 1

Type: ERROR

Impact: Other

BRW-15926: Business area {1} already exists

Cause: Business area name must be unique.

Action: Create business area under a different name.
Level: 1

Type: ERROR

Impact: Other

BRW-15927: Business area {1} already contains a table named {2}

Cause: Table name must be unique within a business area.

Action: Rename/reimport table and add to business area.
Level: 1

Type: ERROR

Impact: Other

BRW-15928: Business area name too long (Max {1} bytes)

Cause: Business area name too long.

Action: Shorten the name and try again.
Level: 1

Type: ERROR

Impact: Other

BRW-15929: Business area description too long (Max {1} bytes)

Cause: Business area description too long.

Action: Shorten the description and try again.
Level: 1

Type: ERROR

Impact: Other

BRW-15930: Error committing table {1}

Cause: Error occurred while committing table.

Action: Try again.
Level: 1

Type: ERROR

Impact: Other

BRW-15931: Error committing business area {1}

Cause: Error occurred while committing business area.

Action: Try again.
Level: 1

Type: ERROR

Impact: Other

BRW-15932: Error committing time period {1}

Cause: Error occurred while committing time period.

Action: Try again.
Level: 1

Type: ERROR

Impact: Other

BRW-15933: Error committing relationship {1}

Cause: Error occurred while committing relationship

Action: Try again.
Level: 1

Type: ERROR

Impact: Other

BRW-15937: Error generating SQL for table {1}

Cause: Error occurred while generating SQL for a table.

Action: Try again.
Level: 1

Type: ERROR

Impact: Other

BRW-15938: Error generating SQL for business area {1}

Cause: Error occurred while generating SQL for a business area.

Action: Try again.
Level: 1

Type: ERROR

Impact: Other

BRW-15939: Error generating SQL for time period {1}

Cause: Error occurred while generating SQL for a time period.

Action: Try again.
Level: 1

Type: ERROR

Impact: Other

BRW-15940: Error generating SQL for relationship {1}

Cause: Error occurred while generating SQL for relationship.

Action: Try again.
Level: 1

Type: ERROR

Impact: Other

BRW-15950: No Query Builder tables--Database open/save is disabled

Cause: There is no Query Builder system query table in the database.

Action: Create a system query table (run the Query Builder install script).
Level: 1

Type: ERROR

Impact: Other

BRW-15951: Product user profile information not loaded

Cause: Cannot load the user profile table.

Action: Ask system administrator to create one.
Level: 1

Type: ERROR

Impact: Other

BRW-15952: User privilege table not loaded

Cause: Missing USER_USERS table (Non Oracle or oracle V7 database).

Action: None available.
Level: 1

Type: ERROR

Impact: Other

BRW-15953: Table privilege table not loaded

Cause: Cannot find Privilege table.

Action: Non-Oracle database or Oracle V7 database.
Level: 1

Type: ERROR

Impact: Other

BRW-15954: Oracle Query Builder 2.5 tables are missing or not installed properly

Cause: No BROWSER_DOCS_SQL table.

Action: Re-install Query Builder 2.5 tables.
Level: 1

Type: ERROR

Impact: Other

BRW-15955: Query returned zero rows

Cause: Query returned no rows.

Action: Modify the query so that it requests data that exists in the database.
Level: 1

Type: ERROR

Impact: Other

BRW-16000: Document saved using End User Layer, not Native dictionary. Continue?

Cause: User tried to open in Native mode a document saved using the End User Layer.

Action: Run with DICTIONARY=ENDUSER or End User Layer objects will be inaccessible.
Level: 1

Type: ERROR

Impact: Other

BRW-16001: Document saved using Native dictionary, not End User Layer. Continue?

Cause: User tried to open in ENDUSER mode a document saved using the Native dictionary.

Action: Run with DICTIONARY=NATIVE or some database objects may be inaccessible.
Level: 1

Type: ERROR

Impact: Other

BRW-16250: Document already exists. Do you want to overwrite?

Cause: User tried to Save As over an existing document.

Action: User may overwrite or cancel.
Level: 1

Type: ERROR

Impact: Other

BRW-16251: Table has been modified. Continue?

Cause: View was removed and recreated; may be inconsistent with document.

Action: Either continue or abort save.
Level: 1

Type: ERROR

Impact: Other

BRW-16500: Memory not available for local sort. Re-execute?

Cause: All rows not yet fetched for local sort.

Action: Re-execute query now or later.
Level: 1

Type: ERROR

Impact: Memory

BRW-16503: Data not available for local sort. Re-execute?

Cause: All rows not yet fetched for local sort.

Action: Re-execute query now or later.
Level: 1

Type: ERROR

Impact: Data

BRW-16504: Data not available for local break. Re-execute?

Cause: All rows not yet fetched for local break.

Action: Re-execute query now or later.
Level: 1

Type: ERROR

Impact: Data

BRW-16525: Query may require a Cartesian product. Continue?

Cause: Query combines results of unrelated tables.

Action: Ignore message or relate tables before executing. Refer to help or documentation for details.
Level: 1

Type: ERROR

Impact: Other

BRW-16531: Redefine parameter {1}?

Cause: User entered previously deleted parameter in expression or condition.

Action: Press OK if this is what you intended.
Level: 1

Type: ERROR

Impact: Other

BRW-16532: Parameter {1} does not exist. Define?

Cause: User entered new parameter in expression or condition.

Action: Press OK if this is what you intended.
Level: 1

Type: ERROR

Impact: Other

BRW-16549: Revert will undo all changes on these tables. Revert anyway?

Cause: Confirmation before reverting data tables.

Action: Select OK to revert all selected data tables, Cancel to cancel the operation.
Level: 1

Type: ERROR

Impact: Other

BRW-16550: Table %s has primary/unique keys that are referenced. Remove?

Cause: Table contains constraints.

Action: Select OK to remove the data table, Cancel to cancel the operation.
Level: 1

Type: ERROR

Impact: Other

BRW-16551: Column has primary/unique keys or indexes. Remove anyway?

Cause: Column is used by constraints or indexes.

Action: Select OK to remove the column, Cancel to cancel the operation.
Level: 1

Type: ERROR

Impact: Other

BRW-16552: Disable all constraints?

Cause: Message to confirm that all constraints should be disabled.

Action: User may confirm or cancel.
Level: 1

Type: ERROR

Impact: Other

BRW-16553: Enable all constraints?

Cause: Message to confirm that all constraints should be enabled.

Action: User may confirm or cancel.
Level: 1

Type: ERROR

Impact: Other

BRW-16575: There are uncommitted edits which will be lost. Commit?

Cause: User has tried to exit the Data Editor without committing changes.

Action: Select Commit or lose changes.
Level: 1

Type: ERROR

Impact: Other

BRW-16576: Defined Column, Summary or Break values may not be current. Re-execute?

Cause: Values edited while displaying breaks, summaries, or defined columns.

Action: Execute query to update values.
Level: 1

Type: ERROR

Impact: Other

BRW-16620: Save changes to query document '%s'?

Cause: Message to prompt user to save changes when closing/quitting.

Action: User may save or abort changes, or cancel.
Level: 1

Type: ERROR

Impact: Other

BRW-16621: Revert to previously saved version of document '%s'?

Cause: Message to prompt user to revert to older document version.

Action: User may continue or cancel operation.
Level: 1

Type: ERROR

Impact: Other

BRW-16622: File %s already exists. Do you want to overwrite?

Cause: Message for overwrite alert in export data.

Action: User may overwrite file or cancel.
Level: 1

Type: ERROR

Impact: Other

BRW-16623: There is no data available for this operation.

Cause: Alert message if number of rows or columns available to print is zero.

Action: User should try re-executing the query, or include some columns.
Level: 1

Type: ERROR

Impact: Data

BRW-16624: Query definition has changed. Data may not be current. Continue?

Cause: Query document has changed since last execute.

Action: Either re-execute the query, continue export, or cancel.
Level: 1

Type: ERROR

Impact: Data

BRW-16625: The printer does not support all fonts needed. Substitute fonts?

Cause: The font or some style or weight does not exist for the selected printer.

Action: User may continue with font substitution or cancel.
Level: 1

Type: ERROR

Impact: Other

BRW-16626: Not enough memory for Print Preview.

Cause: Unable to create bitmap for print preview.

Action: No action required.
Level: 1

Type: ERROR

Impact: Memory

BRW-16627: There is no data available for this operation. Execute query?

Cause: Alert message if export data called with empty worksheet.

Action: User should try executing the query or cancel.
Level: 1

Type: ERROR

Impact: Data

BRW-16628: Unable to get printer device. Printing will be unavailable. Continue?

Cause: Error creating a toolkit printer surface with uiprc().

Action: User may continue with no printing or cancel.
Level: 1

Type: ERROR

Impact: Other

BRW-16629: Do you want to update the container before exiting?

Cause: Message to prompt user to save changes when closing/quitting OLE doc.

Action: User may save or abort changes, or cancel.
Level: 1

Type: ERROR

Impact: Other

BRW-16632: No SQL is available because no columns were selected. Quit?

Cause: Message to alert user that so sql statement was created.

Action: User may exit or continue in query builder.
Level: 1

Type: ERROR

Impact: Other

BRW-16650: The printer does not support all fonts needed. Substitute fonts?

Cause: The font or some style or weight does not exist for the selected printer.

Action: User may continue with font substitution or cancel.
Level: 1

Type: ERROR

Impact: Other

BRW-16651: No printer has been chosen. Use Default?

Cause: The user has not explicitly named a printer to use.

Action: User may continue with the system default printer or cancel.
Level: 1

Type: ERROR

Impact: Other

BRW-16652: Margins for this document are too wide and must be reset.

Cause: The user has set the margins to be too large leaving no content.

Action: User must reset the margins.
Level: 1

Type: ERROR

Impact: Other

BRW-16653: No printer has been chosen. Use Default?

Cause: The user has not explicitly named a printer to use.

Action: User may continue with the system default printer or cancel.
Level: 1

Type: ERROR

Impact: Other

BRW-16654: No pages printed.

Cause: User has set copies to 0 or the start/end page outside the range.

Action: Reset page range.
Level: 1

Type: ERROR

Impact: Other

BRW-16660: Query definition has changed. Data may not be current. Re-execute?

Cause: Query document has changed since last DDE update.

Action: Re-execute the query before DDE update, or update without executing.
Level: 1

Type: ERROR

Impact: Data

BRW-16661: Commit changes to %s?

Cause: Message to prompt user to commit changes when closing Schema Builder.

Action: User may commit or abort changes, or cancel.
Level: 1

Type: ERROR

Impact: Other

BRW-16767: Abandon current parameter settings and cancel query?

Cause: In parameters dialog, ask user before cancelling settings.

Action: User may continue the cancel or return to the dialog.
Level: 1

Type: ERROR

Impact: Other

BRW-16776: Apply settings before closing dialog?

Cause: Asks user if settings changes should be committed before close.

Action: User may apply the changes or exit without committing those changes.
Level: 1

Type: ERROR

Impact: Other

BRW-16780: Cannot paste condition on LONG column.

Cause: Cannot paste a condition on a long column from the find dialog.

Action: This action is not supported.
Level: 1

Type: ERROR

Impact: Other

BRW-16807: Accept the definition for the new business area?

Cause: Business Area Define - validate Complete NEW business area

Action: Accept or cancel
Level: 1

Type: ERROR

Impact: Other

BRW-16808: Cancel the incomplete definition for the new business area?

Cause: Business Area Define - validate Incomplete NEW business area

Action: Confirm or cancel
Level: 1

Type: ERROR

Impact: Other

BRW-16809: Accept the modified business area definition?

Cause: Business Area Define - validate MODified business area

Action: Confirm or cancel
Level: 1

Type: ERROR

Impact: Other

BRW-16810: Accept the definition for the new column?

Cause: Data Table Expressions - validate Complete NEW expression

Action: Confirm or cancel
Level: 1

Type: ERROR

Impact: Other

BRW-16811: Cancel the incomplete definition for the new column?

Cause: Data Table Expressions - validate Incomplete NEW expression

Action: Confirm or cancel
Level: 1

Type: ERROR

Impact: Other

BRW-16812: Accept the modified column definition?

Cause: Data Table Expressions - validate MODified expression

Action: Confirm or cancel
Level: 1

Type: ERROR

Impact: Other

BRW-16813: Accept the definition for the new relationship?

Cause: Data Table Relationships - validate Complete NEW relationship

Action: Confirm or cancel
Level: 1

Type: ERROR

Impact: Other

BRW-16816: Accept the changes to the column's format options?

Cause: Data Table Format - validate MODified format options

Action: Confirm or cancel
Level: 1

Type: ERROR

Impact: Other

BRW-16817: Commit changes?

Cause: User tries to quit with uncommitted changes

Action: Confirm or cancel
Level: 1

Type: ERROR

Impact: Other

BRW-16833: Rollback all changes?

Cause: Confirmation before rollback

Action: OK to rollback all changes. Cancel to cancel operation.
Level: 1

Type: ERROR

Impact: Other

BRW-16837: Business area description cannot be empty.

Cause: Business area description is null.

Action: Enter a description.
Level: 1

Type: ERROR

Impact: Other

BRW-16840: Business area name cannot be empty.

Cause: Business area name is null.

Action: enter a name
Level: 1

Type: ERROR

Impact: Other

BRW-16841: Time period definition is incomplete.

Cause: Some time period attributes have not been specified.

Action: Complete the time period definition.
Level: 1

Type: ERROR

Impact: Other

BRW-16852: User is already imported. Reimport?

Cause: User has already been imported.

Action: Confirm or cancel reimport.
Level: 1

Type: ERROR

Impact: Other

BRW-16961: Document '%s' has unsaved publishers.

Cause: Message (1 of 2) to prompt user to save changes on close/quit.

Action: User may save or abort changes, or cancel.
Level: 1

Type: ERROR

Impact: Other

BRW-16962: They will be lost unless the document is saved.

Cause: Message (2 of 2) to prompt user to save changes on close/quit

Action: User may save or abort changes, or cancel.
Level: 1

Type: ERROR

Impact: Other

BRW-16965: Memory is low. Close open documents or restart with more memory.

Cause: Low memory (&lt;1MB)

Action: Close extra documents, restart with more memory
Level: 1

Type: ERROR

Impact: Memory

BRW-16966: Out of memory. Restart application with a larger memory size.

Cause: No memory

Action: Close extra documents, restart with more memory
Level: 1

Type: ERROR

Impact: Memory

BRW-16967: This application requires System 7.0 or higher.

Cause: Operating System version is lower than 7.0

Action: Upgrade operating system and restart
Level: 1

Type: ERROR

Impact: Other

BRW-16975: Cannot resolve data table '{1}'. Select a new data table?

Cause: Query Choose Table

Action: Confirm or cancel
Level: 1

Type: ERROR

Impact: Data

BRW-16976: Cannot resolve column '{1}' in data table '{2}'. Select a new column?

Cause: Query Choose Column

Action: Confirm or cancel
Level: 1

Type: ERROR

Impact: Data

24 CFGFWK-20300 to CFGFWK-69510

CFGFWK-20300: No validation error detected.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-20665: Database Load Successful! For details see log located at:

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-20668: Test Successful!

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-20836: Test Successful!

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-20839: Database Load Successful!

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-20840: PointBase Server Started...

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-20841: PointBase Server Stopped...

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-20842: NOTE: The PointBase Server instance has been started in the background on port

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-20843: Clicking Next, Previous, or Exit will cause the server to be stopped.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-20850: Test Successful!

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-20851: Test Cancelled!

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-24001: Test Successful!

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-24002: Test Cancelled!

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-24010: Selecting template {0}:{1} and all its prerequisites.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-24011: Added template {0}:{1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-24012: Loaded cell configuration.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-24013: This config wrapper object from a previous session has been invalidated.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-24014: Currently selected templates are {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-24015: Successfully registered Oracle Homes

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-24016: Successfully assigned {0}:{1} to {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-24017: Successfully unassigned {0}:{1} from {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-24018: Successfully saved changes to WebSphere configuration.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-24019: The assign of {0}:{1} to {2} failed

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-24020: The unassign of {0}:{1} from {2} failed

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-24021: OracleHelp loaded.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-24022: For information on Oracle modules enter 'print OracleHelp.help()'

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-24023: Previously applied templates:

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-24024: Currently selected templates:

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-40005: The driver classes listed below were not found in the product installation. {0} A test will not be performed for any database connections using these drivers.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40006: The driver class listed below was not found in the product installation. {0} A test will not be performed for any database connections using this driver.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40850: The JDBC configuration test did not fully complete or completed with errors. Click Cancel and select data sources to test or Click OK to bypass testing.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40851: There are no data sources selected.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40865: This file has been modified in the editor, discard changes?

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40866: Discard previously saved changes?

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40867: Edited file has been modified, discard changes?

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40905: A template already exists in that location. Do you want to overwrite it?

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40915: At least one JMS system resource has been selected for conversion to a Uniform Distributed Destination (UDD). This conversion will take place only if the JMS system resource is assigned to a cluster.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-42001: The following duplicate elements exist in a configuration, discarding new elements from a incoming template.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-44001: The JDBC configuration test did not fully complete or completed with errors. Click Cancel and select data sources to test or Click OK to bypass testing.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-44002: There are no data sources selected.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-44003: No Oracle Products found in WebSphere profile

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-44004: Application server node not found in Deployment manager profile

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-44005: The driver classes listed below were not found in the product installation. {0} A test will not be performed for any database connections using these drivers.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-44006: The driver class listed below was not found in the product installation. {0} A test will not be performed for any database connections using this driver.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-44007: Duplicate Server listen ports exist in your cell configuration.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-44008: Server listen ports in your cell configuration conflict with ports in use by active processes on this host.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-44009: Duplicate datasource JNDI names exist in the same scope: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-44010: The following duplicate elements exist in a configuration, discarding new elements from a incoming template.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-60001: The user name must not contain commas, tabs, or any of the following characters: <>#|&?(){}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60002: The string must have a minimum length of {0} characters

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60003: The value {0} is greater than the maximum allowable value of {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60004: The value {0} is less than the minimum allowable value of {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60005: WebLogic domain requires the password to be minimum 8 characters

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60006: The value must be one of the following: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60050: Property "{0}" of {1} "{2}" is invalid.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60051: Property "{0}" of {1} with original name "{2}" is invalid.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60052: Space characters are not allowed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60053: The string cannot be converted.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60054: The property value is required.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60055: The property value is duplicated.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60056: The property is disabled.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60057: The property is not supported.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60058: The class name must have the format "xxx.xxx.xxx.xxx".

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60059: The properties string must contain fields formatted as "name=value" separated by ";".

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60060: The known definition of property "{0}" cannot be changed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60061: The additional property "{0}" must be defined.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60062: If "All Local Addresses" is selected, no additional address should be provided.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60063: The list of address is empty.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60064: The confirmed password does not match the entered one.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60065: Invalid input

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60066: The returned row set is null.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60100: At most {0} entries can be created.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60101: At most 1 entry can be created.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60102: At least {0} entries must be provided.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60103: At least 1 entry must be provided.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60150: The server has the same combination of listen address and port as other server.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60151: The server has the same combination of listen address and SSL port as other server.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60152: The server has the same combination of listen address and port as admin server.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60153: The server has the same combination of listen address and SSL port as admin server.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60154: The server has the same port and SSL port.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60155: Listen port cannot be empty.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60156: The IP address must have the proper v6 format like "xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx" or "xxxx:xxxx:xxxx:xxx:xxx.xxx.xxx.xxx" or other supported format.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60157: The IP address must have the format "xxx.xxx.xxx.xxx".

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60158: Each segment of the IP address must contain an integer in the range of 0 to 255.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60159: Each segment of the IP address must contain an integer in the range of 0 to 255.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60160: The IP multicast address must be in the range of 224.0.0.1 to 239.255.255.255.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60161: The host name does not allow leading or trailing dot (.).

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60162: The host name does not allow multiple dots (.).

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60163: No member of the hostname may begin or end with a dash (-).

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60164: The entered value is not a valid hostname. Please use only alphanumeric characters and dot (.) and dash (-).

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60165: The right most domain label can never start with a digit.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60166: Each entry must be expressed as <hostname> or <hostname>:<port>.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60167: The port number must be an integer.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60168: The port number must be an integer in the range of 1 to 65535.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60200: The targets of the distributed destination should cover all the servers that host the members.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60201: The distributed topic "{0}" that distributed topic member "{1}" belongs to is not deployed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60202: The JMS Server "{0}" that topic "{1}" belongs to is not deployed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60203: The distributed queue "{0}" that distributed queue member "{1}" belongs to is not deployed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60204: The JMS Server "{0}" that queue "{1}" belongs to is not deployed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60205: Group(s) assigned to "Admin" role must contain at least one user.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60206: Admin role must be assigned at least one group or one user.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60207: The JDBC (Tx) DataSource specifies a nonexistent JDBC Connection Pool.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60208: The JDBC Multi Pool specifies a nonexistent JDBC Connection Pool.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60209: The JDBCConnectionPool "{0}" could not be undeployed from target "{1}", because it is used by the JMSJDBCStore "{2}", which is used by the deployed JMSServer "{3}".

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60250: The JNDI name is duplicated in JMS server "{0}"

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60300: You must specify a WebLogic domain name.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60301: The name of the WebLogic domain and the server/cluster names within it must be unique. A server/cluster already exists with the WebLogic domain name you specified.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60302: A domain with an identical name exists at the location you have selected. Change the domain name or location.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60303: The domain directory you specified contains files. You may only create a domain in an empty directory.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60304: The applications directory you specified contains files. Applications may only be written to an empty directory.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60305: The specified domain name must include only alphanumeric characters, hyphens ('-') or underscore characters ('_'). The domain name must contain at least one letter or digit.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60306: The domain location must not contain spaces.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60307: The domain location must be specified.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60308: The domain location must have write permission.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60309: The application location must not contain spaces.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60310: The application location must be specified.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60311: The application location must have write permission.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60312: You must specify a Template Jar Name to Create.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60313: The specified template name must include only alphanumeric characters, hyphens ('-') or underscore characters ('_'). The template name must contain at least one letter or digit.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60314: The template location must not contain spaces.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60315: The template location must be specified.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60316: The template location must have write permission.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60317: The "Servers, Clusters and Machines" configuration in your domain is invalid. Try to resolve the issue by clicking Cancel and returning to this section in the wizard. If you cannot resolve the issue, either click Cancel and exit the wizard, or click OK to continue. If continuing, you may want to start the server in the domain and review the messages to identify the invalid configuration.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60318: The "JDBC" configuration in your domain is invalid. Try to resolve the issue by clicking Cancel and returning to this section in the wizard. If you cannot resolve the issue, either click Cancel and exit the wizard, or click OK to continue. If continuing, you may want to start the server in the domain and review the messages to identify the invalid configuration.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60319: The "JMS" configuration in your domain is invalid. Try to resolve the issue by clicking Cancel and returning to this section in the wizard. If you cannot resolve the issue, either click Cancel and exit the wizard, or click OK to continue. If continuing, you may want to start the server in the domain and review the messages to identify the invalid configuration.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60320: The "Security" configuration in your domain is invalid. Try to resolve the issue by clicking Cancel and returning to this section in the wizard. If you cannot resolve the issue, either click Cancel and exit the wizard, or click OK to continue. If continuing, you may want to start the server in the domain and review the messages to identify the invalid configuration.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60321: Duplicate Server listen ports exist in your domain configuration.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60322: Server listen ports in your domain configuration conflict with ports in use by active processes on this host.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60323: An unknown section of your configuration is invalid. Either click Cancel and exit the wizard or click OK to continue. If you continue, you may want to start the server in the domain and review the messages to identify the invalid configuration.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60324: The domain location is not a directory.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60325: The directory location is invalid.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60326: Directory names must include only alphanumeric characters, hyphens ('-') or underscore characters ('_') and must contain at least one letter or digit.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60327: A directory name cannot be null.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60328: The application location is not a directory.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60329: The following templates require entry of a KeyStore password:

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60330: Use the storeKeyStorePassword(template_location, password) command for each template listed above to enter required KeyStore passwords. The command must be entered after adding templates and before updating the domain.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60367: The "Servers, Clusters and Machines" configuration in your domain is invalid. Try to resolve the issue by entering Previous and returning to this section in the wizard. If you cannot resolve the issue, either Exit the wizard now, or enter Next to continue. If continuing, you may want to start the server in the domain and review the messages to identify the invalid configuration.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60368: The "JDBC" configuration in your domain is invalid. Try to resolve the issue by entering Previous and returning to this section in the wizard. If you cannot resolve the issue, either Exit the wizard now, or enter Next to continue. If continuing, you may want to start the server in the domain and review the messages to identify the invalid configuration.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60369: The "JMS" configuration in your domain is invalid. Try to resolve the issue by entering Previous and returning to this section in the wizard. If you cannot resolve the issue, either Exit the wizard now, or enter Next to continue. If continuing, you may want to start the server in the domain and review the messages to identify the invalid configuration.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60370: The "Security" configuration in your domain is invalid. Try to resolve the issue by entering Previous and returning to this section in the wizard. If you cannot resolve the issue, either Exit the wizard now, or enter Next to continue. If continuing, you may want to start the server in the domain and review the messages to identify the invalid configuration.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60371: Duplicate Server listen ports exist in your domain configuration.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60372: Server listen ports in your domain configuration conflict with ports in use by active processes on this host.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60373: An unknown section of your configuration is invalid. You can either Exit the wizard now or enter Next to continue. If you continue, you may want to start the server in the domain and review the messages to identify the invalid configuration.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60417: The "Servers, Clusters and Machines" configuration in your domain is invalid. Try to resolve the issue by reviewing your script. The wizard will continue, but you may want to start the server in the domain and review the messages to identify the invalid configuration.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60418: The "JDBC" configuration in your domain is invalid. Try to resolve the issue by reviewing your script. The wizard will continue, but you may want to start the server in the domain and review the messages to identify the invalid configuration.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60419: The "JMS" configuration in your domain is invalid. Try to resolve the issue by reviewing your script. The wizard will continue, but you may want to start the server in the domain and review the messages to identify the invalid configuration.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60420: The "Security" configuration in your domain is invalid. Try to resolve the issue by reviewing your script. The wizard will continue, but you may want to start the server in the domain and review the messages to identify the invalid configuration.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60421: Duplicate Server listen ports exist in your domain configuration.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60422: Server listen ports in your domain configuration conflict with ports in use by active processes on this host.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60423: An unknown section of your configuration is invalid. Try to resolve the issue by reviewing your script. The wizard will continue, but you may want to start the server in the domain and review the messages to identify the invalid configuration.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60450: The default admin user could not be deleted.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60451: Cannot add built-in groups "everyone" or "users".

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60452: Built-in roles "Admin" and "Anonymous" must be provided.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60453: The supplied user password for "{0}" is too short

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60454: The supplied user name for "{0}" is not in required format.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60455: The password must be at least 8 alphanumeric characters with at least one number or special character.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60500: The {0} must be specified.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60501: The following must be specified:

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60502: The {0} and {1} do not match.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60503: The {0} must be an integer.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60504: The selected data sources do not share any common database drivers. The wizard will deselect data sources to allow selection of compatible drivers.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60505: The selected component schemas do not share any common database drivers. The wizard will deselect component schemas to allow selection of compatible drivers.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60550: Script execution aborted. The script may contain an error.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60551: Details in the log file:

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60600: Before booting this domain, it is necessary to run the SQL file located at {0} in order to initialize a domain security admin user in the database.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60601: Unable to add template: Required component not found.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60650: The location does not exist.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60651: Select another directory location

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60655: The location does not exist or not a directory.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60656: No domains found under selected directory.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60660: The location is invalid.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60665: Error getting connection info!

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60666: Database Load Failed! Check the log located at:

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60667: There are no files available to load into the database.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60668: Test Failed!

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60675: The template you selected can't be applied because the following dependencies have not been satisfied:

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60676: Select an available template from the list

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60677: Selection does not contain a domain template.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60678: Fatal error

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60679: Select a valid domain template

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60680: Unable to add application template

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60685: The path specified was invalid.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60686: No template exists at

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60687: The template you selected can't be applied because the following dependencies have not been satisfied:

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60688: Unable to load template.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60689: Selection does not contain a domain template.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60690: Select a valid domain template

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60691: Some of the application templates you have selected are incompatible with each other due to conflicting application and/or service names.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60692: Unable to add application template

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60695: User password does not match confirmed password.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60700: Unable to determine if the directory you selected contains a valid JDK. Do you want to proceed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60701: You must specify a JDK location.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60705: Some of the configuration extensions you have selected are incompatible with each other due to conflicting application and/or service names.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60706: The Configuration Template Builder is not supported in console mode.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60707: The template is already selected.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60800: There is a problem with the template!

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60801: No template was selected!

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60802: Select a specific domain.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60803: This is not a valid configuration! Correct the following error in config.xml:

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60804: The Configuration Wizard encountered problems attempting to load the configuration you selected. Would you like to generate a log file which will be located at

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60805: The domain in this directory is not a supported version.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60806: The Configuration Wizard was unable to generate the log file located at

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60807: Failed to create busMember {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60808: No bus members defined for bus {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60809: Datasource provider was not found for {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60810: There is a problem with the template!

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60811: There were no standard components found in your installation. Browse to a custom component

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60812: Some of the extension templates you have selected are incompatible with each other due to conflicting application and/or service names.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60813: The extension template you selected can't be applied because the following dependency has not been satisfied:

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60814: The template you selected can't be applied because the following dependencies have not been satisfied:

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60815: The configuration extension listed below contains a component that is already defined in the existing domain. Indicate how to resolve this conflict.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60816: Select a valid domain template

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60817: The config.xml is invalid or missing in the template selected.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60818: The selected template is designed to extend an existing domain. It is defined as an extension template and does not express a dependency on a domain template. Select another template or choose one of the above checkbox selections.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60819: Select an available template from the list or select an existing template below

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60820: Specify valid template path.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60821: Specified template does not exist.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60825: Unable to create HTTP proxy application(s)

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60826: You have chosen a managed server which is already a proxy for a cluster. It is recommended that a managed server only proxy a single cluster. Click OK to keep your assignment and continue, otherwise click Cancel to change it.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60827: The managed server chosen as a HTTP proxy for a cluster is invalid. Its Listen Address should be a valid host name or an IP address.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60828: The Listen Address for all servers in a cluster with an HTTP proxy should be a valid host name or an IP address.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60830: There must be files to load.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60831: You must select a file first.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60832: You must select a file first.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60833: You must select a file first.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60834: The URL entered may not end with forward slash ("/").

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60835: The URL entered was malformed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60837: Test Failed!

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60838: Error getting connection information!

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60839: Database Load Failed!

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60840: Error encountered starting PointBase server or the server process was killed!

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60841: For possible information regarding the error check the log located at:

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60842: Error encountered stopping the PointBase server! Check log file:

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60843: Error Writing Log File:

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60850: Test Failed!

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60851: Error getting connection information!

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60852: The jdbc connection data for data source {0} is incomplete. Fix the data before testing.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60853: A connection was established to the database but no rows were returned from the test SQL statement.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60855: Name cannot be empty. Re-enter.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60856: Version cannot be empty. Re-enter.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60857: Version should be in the format N.N.N.N where N is a positive number. Re-enter.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60860: Link Name and Program fields must be specified.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60865: This file type is not editable

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60870: Path cannot start or end with a path separator.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60875: The selected directory is a representation of a location that will be selected by the user when using this configuration and cannot be removed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60876: You cannot remove the files in red or their parent directories because they comprise this configuration's applications.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60877: You must first select a file to remove.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60878: You must select a source file or directory on the left.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60879: You must select a destination location on the right.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60880: The selected directory is a representation of a location that will be selected by the user when using this configuration and files cannot be added.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60881: The selected file cannot be added to your domain directory because it is a reserved file. This usually means that the file will be auto-generated by the configuration wizard and does not need to be added.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60885: Error encountered preparing template from jar.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60890: Unable to determine if the selected directory contains a valid JDK. Do you want to proceed?

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60891: Unable to determine if the specified directory contains a valid JDK. Do you want to proceed?

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60892: The specified directory does not exist. Enter a valid JDK directory.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60893: The selected JDK version doesn't match the jdk version pattern. Click Cancel and select a different jdk or Click OK to proceed with same jdk.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60894: The recommended minimum JDK version doesn't match the jdk version pattern.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60895: The selected jdk version is lower than recommended minimum version. Click Cancel and select a different jdk or Click OK to proceed with same jdk.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60900: You must select a file first

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60901: You must select a file first

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60905: Password does not match

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60906: The field {0} cannot be empty.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60907: The field {0} must be an integer.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60908: The password/confirm password field is empty.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60909: The password entered should match the confirm password field.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64001: The value must be one of the following: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64010: Property "{0}" of {1} "{2}" is invalid.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64011: Property "{0}" of {1} with original name "{2}" is invalid.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64012: Space characters are not allowed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64013: The string cannot be converted.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64014: The property value is required.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64015: The property value is duplicated.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64016: The property is disabled.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64017: The property is not supported.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64018: The confirmed password does not match the entered one.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64019: Invalid input

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64020: Property "{0}" of {1} with the new name "{2}" is invalid.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64025: At most {0} entries can be created.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64026: At most 1 entry can be created.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64027: At least {0} entries must be provided.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64028: At least 1 entry must be provided.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64029: Disabled entry may not be removed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64035: The {0} "{1}" could not be assigned to the target "{2}" since each target can have only one {0} assigned.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64040: The template you selected can't be applied because the following dependencies have not been satisfied:

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64041: Select an available template from the list

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64042: Selection does not contain a domain template.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64043: Fatal error

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64044: Select a valid domain template

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64045: Unable to add application template

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64050: No template was selected!

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64051: Select a specific domain.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64052: This is not a valid configuration! Correct the following error in config.xml:

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64053: The Configuration Wizard encountered problems attempting to load the configuration you selected. Would you like to generate a log file which will be located at

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64054: The domain in this directory is not a supported version.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64055: The Configuration Wizard was unable to generate the log file located at

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64056: There is a problem with the template!

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64057: There were no standard components found in your installation. Browse to a custom component

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64058: Some of the extension templates you have selected are incompatible with each other due to conflicting application and/or service names.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64059: The extension template you selected can't be applied because the following dependency has not been satisfied:

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64060: The template you selected can't be applied because the following dependencies have not been satisfied:

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64061: The configuration extension listed below contains a component that is already defined in the existing domain. Indicate how to resolve this conflict.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64062: Select a valid domain template

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64063: The config.xml is invalid or missing in the template selected.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64064: The selected template is designed to extend an existing domain. It is defined as an extension template and does not express a dependency on a domain template. Select another template or choose one of the above checkbox selections.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64065: Select an available template from the list or select an existing template below

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64066: Specify valid template path.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64067: Specified template does not exist.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64068: There is a problem with the template {0}!

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64069: The following prerequisites were found to be missing:

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64070: The following templates are both prerequisites and conflicts for the current selection:

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64071: The selection conflicts with templates already installed in the domain:

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64072: One of the following needs to be selected:

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64073: The template is not selectable in the current mode

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64074: Given template is not present

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64075: The template is already installed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64076: The template is already selected

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64077: The template is not selected

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64100: No such help topic exists

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64101: Help is not configured

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64102: Invalid help type

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64103: Errors occurred while loading Help. Check log for details.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64104: Value of console width is too low! Please set higher value.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64150: Internal Error: panel does not support help.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64151: Configuration Error: no help URI configured.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64152: Configuration Error: invalid help URI.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64153: Unable to open help: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68001: Duplicate Server listen ports exist in your cell configuration.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68010: The password must be at least 8 alphanumeric characters with at least one number or special character.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68020: The {0} must be specified.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68021: The following must be specified:

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68022: The {0} and {1} do not match.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68023: The {0} must be an integer.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68024: The selected data sources do not share any common database drivers. The wizard will deselect data sources to allow selection of compatible drivers.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68025: The selected component schemas do not share any common database drivers. The wizard will deselect component schemas to allow selection of compatible drivers.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68026: Unable to encrypt password:

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68028: The port value {0} must be in range of 0 to 65535.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68029: The port value {0} must be integer.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68030: Initialization error: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68031: The system wasn't initialized properly.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68032: The python interpreter is not set.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68033: Unable to create template catalog.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68034: Found no templates with {0} name and {1} version.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68035: Found {2} templates with {0} name and {1} version.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68036: Unable to load template from [{0}].

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68037: Unable to load cell configuration.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68038: The template is already selected.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68039: The following previously selected templates conflict with the new selection:

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68040: The selected templates are not compatible with each other.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68041: Unable to add template with {0} name and {1} version: {2}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68042: Unable to save configuration.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68043: Unknown scope defined: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68044: Unable to copy : {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68045: Cell configuration not loaded.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68046: Unable to register Oracle home information : {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68047: No templates were selected!

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68048: The name or type {1}:{0} can not be null.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68049: The requested type {0} is not supported.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68050: The {0}:{1} was not found in a requested scope {2}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68051: Duplicate Server listen ports exist in your cell configuration.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68052: Server listen ports in your cell configuration conflict with ports in use by active processes on this host.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68053: The property {0} is not allowed to be modified; use listAttributes() for supported types.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68054: The {0} with name {1} was not found.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68055: The property {0} is not a supported type; use listTypes() for supported types.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68056: The property {0} is not a supported attributes; use listAttributes() for supported types.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68057: The property {0} is not valid; use listAttributes() or listTypes() for supported attributes and types.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68058: Unsupported profile type; select a deployment manager profile or a remotely federated custom profile : {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68059: The requested {0}:{1} could not be deleted.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68060: The specified property {0} is read-only.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68061: The requested operation is not allowed here.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68062: The specified value {0} is not supported or is invalid!

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68063: Specify path to deployment manager profile.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68064: The specified value {0} for {1} is of incompatible type or out of range.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68065: JDBC datasource validation failed:

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68066: The specified type is read-only.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68067: The specified operation {0}:{1} is not supported for WebSphere STANDALONE Cell.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68068: validation failed for : {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68069: {0} assignment not supported.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68070: Test Failed!

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68071: Error getting connection information!

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68072: A connection was established to the database but no rows were returned from the test SQL statement.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68073: The value of attribute {0} is not allowed to be read.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68074: Run OracleMWConfig.dumpStack() to view the full Exception

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68075: Required attribute not specified: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68076: Source : {0} already assigned to Destination : {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68077: Source : {0} not assigned to Destination : {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68078: Destination not found : {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68079: Could not complete {0} to {1} assignment. {2}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68080: The options map of {0} may not be null.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68081: "{0}" is a required option of {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68082: The IP address must have the proper v6 format like "xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx" or "xxxx:xxxx:xxxx:xxx:xxx.xxx.xxx.xxx" or other supported format.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68083: The IP address must have the format "xxx.xxx.xxx.xxx".

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68084: Each segment of the IP address must contain an integer in the range of 0 to 255.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68085: Each segment of the IP address must contain an integer in the range of 0 to 255.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68086: The IP multicast address must be in the range of 224.0.0.1 to 239.255.255.255.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68087: The host name does not allow leading or trailing dot (.).

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68088: The host name does not allow multiple dots (.).

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68089: No member of the hostname may begin or end with a dash (-).

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68090: The entered value is not a valid hostname. Please use only alphanumeric characters and dot (.) and dash (-).

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68091: The right most domain label can never start with a digit.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68100: Errors occurred while loading OracleHelp. Check log for details.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68110: Error obtaining key from properties file

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68111: Invalid prefix obtained from properties file

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-69500: Attempt to execute command "{0}" in invalid state: {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-69501: The method "{0}" is not available.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-69502: Assignment Target not found for type: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-69503: Could not find {0} : {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-69504: Invalid Target : {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-69510: Fatal internal error

Cause: An unexpected internal condition was detected. The wizard cannot continue.

Action: Check the logs for more information.
Level: 1

Type: ERROR

Impact: Configuration

25 CLONE-20200 to CLONE-53030

CLONE-20200: The clone option or argument is invalid.

Cause: The option or argument "{0}" was not supported by cloning.

Action: Provide a valid option or argument. Use the "-help" option for more information about cloning options and arguments.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20201: The value for the argument is missing.

Cause: The argument "{0}" was provided, but its value was not provided.

Action: Provide the corresponding value.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20202: The archive location is invalid.

Cause: There are five possible causes for an invalid path {0}: 1. The path was not provided. 2. The path was not an absolute path. 3. The path already existed. 4. The parent path did not exist. 5. The parent path did not have write permission.

Action: Provide an absolute path to a directory that does not exist and make sure that its parent location exists and has write permission.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20203: Invalid archive location.

Cause: There are six possible causes: 1. Archive path was not provided. 2. Archive path was not an absolute path. 3. Archive path did not exist. 4. Archive path did not point to a file. 5. Archive path did not have read permission. 6. Archive was a zero size file.

Action: Provide the absolute path of a valid archive file.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20204: Insufficient parameters for copyConfig.

Cause: Neither "-sourceMWHomeLoc", "-sourceInstanceHomeLoc and -sourceComponentName" nor "-sourceMWHomeLoc and -sourceDomainLoc" nor "-sourceNMHomeLoc" were provided.

Action: Provide either "-sourceMWHomeLoc", "-sourceInstanceHomeLoc and -sourceComponentName" or "-sourceMWHomeLoc and -sourceDomainLoc" or "-sourceNMHomeLoc".
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20205: Arguments combination is invalid.

Cause: The -sourceInstanceHomeLoc and/or -sourceComponentName was provided along with -sourceMWHomeLoc.

Action: Provide either -sourceInstanceHomeLoc and/or -sourceComponentName or sourceMWHomeLoc.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20206: Invalid value for "{0}" option.

Cause: The provided value was not a Boolean value.

Action: Supported Boolean values are "true" or "false".
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20207: The clone option is not supported.

Cause: The option or argument "{0}" was not supported by {1} operation.

Action: Provide a valid option or argument. Use the "-help" option for more information about cloning options and arguments.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20208: Insufficient parameters.

Cause: At least one argument from these arguments "{0}", was not provided.

Action: Provide all the arguments.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20209: Unable to unregister all instances(which were present in source domain) from target domain.

Cause: An internal operation failed.

Action: Check the clone log and error file for more detail and unregister instances from target domain through admin console.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20210: The archive file is invalid.

Cause: The archive file failed an internal consistency check.

Action: Make sure that the archive file is created using T2P operation.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20211: Unable to update JRE_LOCATION in Oracle Home.

Cause: Unable to determine JRE_LOCATION.

Action: Update JRE_LOCATION attribute in {0} file present under Oracle Home.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20212: Target location is not provided.

Cause: Archive had Middleware Home and/or Oracle Home.

Action: Provide the target location.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20213: Parameters are missing for component pasteConfig.

Cause: There are two possible causes: 1. Target component name was empty. 2. If target instance did not exist, then either target instance name or Oracle Home was empty or Oracle Home was not a directory.

Action: Provide a nonexistent component name and a target instance location. If the instance does not exist, provide the instance name and an existing Oracle Home.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20214: T2P of asinstance is not possible.

Cause: No movable component was found under the instance home.

Action: Make sure that the instance home has at least one movable component.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20215: T2P of asinstance failed.

Cause: Unable to archive all the movable components.

Action: Provide the clone log and error file for investigation.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20216: Instance home location "{0}" is invalid.

Cause: There are two possible causes: 1. Instance did not have the required configuration files. 2. Instance was not associated with a valid Oracle Home.

Action: Provide a valid instance home location.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20217: Component does not exist.

Cause: The component "{0}" did not exist under the instance "{1}".

Action: Provide an existing component.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20218: Cloning is not successful.

Cause: An internal operation failed.

Action: Provide the clone log and error file for investigation.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20219: Clone type is invalid.

Cause: Clone type was either empty or not supported.

Action: The clone type is either "{0}" or "{1}" or "{2}".
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20220: Parameters are missing.

Cause: Either archiveLocation or cloneType was empty. The values provided were archiveLocation : "{0}" cloneType : "{1}".

Action: Make sure that the correct values are provided.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20221: Invalid clone type.

Cause: The clone type "{0}" did not match "{1}" or "{2}".

Action: The clone type should be either "{0}" or "{1}".
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20222: Parameters validation has failed.

Cause: Primary parameters validation for "{0}" failed.

Action: Check the clone log and error file and provide correct value.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20223: Invalid Oracle Home.

Cause: There are four possible causes for an invalid Oracle Home "{0}": 1. It did not exist. 2. It was an empty directory. 3. It had invalid inventory pointer file (if operating system is other than Windows). 4. It had no top component or invalid top component version.

Action: Provide a valid Oracle Home.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20224: T2P operation failed.

Cause: Unable to restore all movable components.

Action: Check the clone log and error file.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20225: Invalid number of sourceid(s) and their restore locations.

Cause: There was a mismatch between the count of sourceids and restore locations specified in the command line. The number of sourceids was "{0}" and number of restore locations was "{1}".

Action: Provide the same number of sourceids and their corresponding restore locations.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20226: Duplicate target location.

Cause: An attempt was made to restore same or different sourceid at same location multiple times.

Action: Provide unique target location for each sourceid.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20227: Invalid target location for Oracle Home.

Cause: Two Oracle Homes target location "{0}" and "{1}" were either equal or a parent or child of one another.

Action: Oracle Home(s) target location(s) should not be either equal or parent or child of one another.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20228: Invalid target location for Middleware Home.

Cause: Two Middleware Homes target locations "{0}" and "{1}" were either equal or the parent or child of one another.

Action: Middleware Home(s) target location(s) should not be either equal or a parent or child of each other.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20229: The archive file is invalid.

Cause: Internal id was absent in the archive.

Action: Make sure that the archive file is valid.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20230: Primary validation prior to clone operation has failed for {0}.

Cause: Parameter(s) were missing or some validation(s) failed.

Action: Check the clone log and error file for information about which parameter is missing or why validation failed.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20231: Middleware Home archive creation has failed.

Cause: The command "{0}" was not run successfully. The possible causes are: 1. All WebLogic product directories (like WebLogic Server, Coherence) were not installed inside this Middleware Home. 2. In case of Windows, some Java or WebLogic processes were running from this Middleware Home.

Action: Make sure all WebLogic products are installed inside, no process is running from the Middleware Home (in case of Windows), and check the clone log, clone error and "WebLogic error file at current location" for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20232: Oracle Home configuration has failed.

Cause: Exception occurred while configuring Oracle Home.

Action: Check the installer log and cloneAction log in the inventory for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20233: Restoring Middleware Home for sourceid "{0}" has failed.

Cause: An internal operation failed.

Action: Check the clone log and error file for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20234: Unable to find Oracle Home "{0}" from inventory.

Cause: Missing entry for Oracle Home in the inventory.

Action: Make sure that the Oracle Inventory has an entry for this Oracle Home.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20235: Adding "{0}" to the archive has failed.

Cause: An internal operation failed.

Action: Check the clone log and error file for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20236: Archive creation has failed.

Cause: An internal operation failed.

Action: Check the clone log and error file for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20237: Restoring the sourceid "{0}" has failed.

Cause: An internal operation failed.

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

Type: ERROR

Impact: Cloning

CLONE-20238: Component name is invalid.

Cause: The instance "{0}" was already configured with component name "{1}".

Action: Provide a unique component name.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20239: Invalid archive file.

Cause: Either archive did not have sourceid file, or a sourceid was a zero size file.

Action: Make sure the correct archive file is provided, and check the extracted sourceid file whose path is "{0}".
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20240: Invalid archive file.

Cause: Either archive did not have "{0}" file, or archive was not created through copyConfig operation.

Action: Make sure that the correct archive file is provided.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20241: Moveplan is invalid.

Cause: There was a mismatch between number of components specified in the moveplan and number of components present in the archive.

Action: Make sure that no component is removed from the moveplan.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20242: Moveplan contains an invalid component type.

Cause: There are two possible causes :1. The component type was empty.2. The component type from moveplan "{0}" was not matching with the component type "{1}" present in the the archive.

Action: Make sure that component type is not changed in the moveplan.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20243: Moveplan contains an invalid component name.

Cause: There are three possible causes for the component name {0} being invalid:1. It was empty.2. Length of the component name was either too short or too large.3. Component name had contained unsupported characters.

Action: Provide a valid component name in the moveplan.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20244: Moveplan is invalid.

Cause: The component names were not unique in the moveplan.

Action: Provide unique component names in the moveplan.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20245: Unable to include permission file to the archive.

Cause: Permission file creation failed.

Action: Check the clone log and error file.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20246: Oracle Home is invalid.

Cause: Size of the Oracle Home "{0}" was zero.

Action: Uninstall the invalid Oracle Home and execute copyBinary again.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20247: Not all file permission operations are successful.

Cause: Some files were missing from the Oracle Home {0}.

Action: Check the clone log file and permission restore log file {0} for more details about the missing files.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20248: Execution of system prerequisites have failed.

Cause: The following system prerequisites failed : {0}.

Action: Check clone log for more details on prerequisites output and result.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20249: Execution of system prerequisites have completed with warnings.

Cause: The following system prerequisites completed with warnings : {0}.

Action: Check clone log for more details on prerequisites output and result.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20250: Execution of system prerequisites has completed without verifying some of the prerequisites.

Cause: The following system prerequisites were not verified : {0}.

Action: Check clone log for more details on prerequisites output and result.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20251: Execution of system prerequisites failed for some or all of the Oracle Homes.

Cause: Some of the system prerequisites were not completed successfully.

Action: Check the clone logs for more details on the prerequisite output and results. Re-execute the pasteBinary command after either fixing the failing prerequisites or by adding the '-executeSysPrereqs false' parameter to the command line.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20252: Invalid T2P action type.

Cause: The provided action type was "{0}". This action type was either empty or unsupported.

Action: The supported action types are "{0}".
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20254: Invalid target location.

Cause: There are four possible causes for invalid location {0}: 1. The target location was not provided. 2. The target file path was not an absolute path. 3. The target file path did not exist. 4. The target file path did not have write permission.

Action: Provide an absolute path of an existing target location.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20255: Invalid Middleware Home.

Cause: The "{0}" was not a valid Middleware Home.

Action: Make sure that it is a valid Middleware Home.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20256: Unable to capture permission of all the files present under the Oracle Home.

Cause: Some of the files did not have proper permission.

Action: Check clone log file for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20261: Invalid Oracle Inventory.

Cause: There are six possible causes for an invalid inventory pointer file "{0}": 1. File did not exist. 2. File did not have read permission. 3. It was a zero size file. 4. File did not have any pointer to OraInventory. 5. Oracle Inventory found from file was not absolute. 6. Oracle Inventory specified in the inventory pointer file did not have write permission.

Action: Provide a valid Oracle Inventory.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20262: Cloning is not possible.

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

Action: Either provide a different inventory location or provide a different location for the new Oracle Home.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20263: Invalid Oracle Inventory.

Cause: There are two possible causes for an invalid OraInventory "{0}". 1. Inventory was empty. 2. It did not have valid inventory.xml file.

Action: Provide a valid Oracle Inventory.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20264: Default inventory pointer location file is invalid.

Cause: There are two possible causes for an invalid default invPtrLoc file "{0}": 1. The file did not exist. 2. It was a zero size file.

Action: Ensure that the default oraInst.loc file at "default location" is valid or provide a different, valid Inventory Pointer file using the -invPtrLoc argument.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20265: Invalid argument.

Cause: Either argument was an empty string or "null".

Action: Provide a valid argument.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20269: Setting Java library path has failed.

Cause: There are four possible causes: 1. The OUI library path {0} was empty. 2. Unable to find OUI library directory name. 3. The oraInstaller library path {1} was empty. 4. The oraInstaller library path {1} was corrupted.

Action: Make sure that OUI and the oraInstaller library are available.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20270: Java home of the Middleware Home is invalid.

Cause: There are two possible causes: 1. Did not find either JAVA_HOME or JAVAHOME property in product.properties of WebLogic Server home. 2. The Java home did not exist.

Action: Make sure that the Middleware Home is installed with a valid Java home.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20271: Invalid characters.

Cause: Command-line input {0} had some unsupported characters.

Action: Supported characters are "{0}" but these three characters "_.-" are not allowed in the beginning of a string.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20272: Invalid path.

Cause: Path "{0}" was either not absolute or did not have valid characters.

Action: Supported characters are "{0}" but these three characters "_.-" are not allowed in the beginning of a string.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20273: Invalid instance location.

Cause: Path "{0}" was not absolute or did not exist or was an empty directory.

Action: Provide a valid absolute path.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20274: Invalid Oracle Home.

Cause: Top component version validation failed.

Action: Make sure that the Oracle Home is valid.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20275: Insufficient space to create {0}.

Cause: Minimum required space was at least "{0}" MB, but only "{1}" MB was available for use.

Action: Make sure that the minimum required space is available for use.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20276: Extracting is unsuccessful.

Cause: Some files were missing.

Action: Check the clone log or error file for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20277: Some files are missing.

Cause: After configuration, some files were removed.

Action: Check the clone log or error file for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20278: Oracle Home configuration is unsuccessful.

Cause: Some symbolic link(s) were either mismatching or were not present.

Action: Check the clone log or error file for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20279: Oracle Home configuration is unsuccessful.

Cause: Inventory was not updated properly.

Action: Check the clone log or error file for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20280: Oracle Home is not cloneable.

Cause: Some component(s) under the Oracle Home {0} were not cloneable.

Action: Make sure that all components in the Oracle Home are cloneable.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20281: Moveplan has incorrect SSL information for the asinstance

Cause: There were following causes: {0}

Action: The actions are: {0}
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20282: Parameter validation for component pasteConfig has failed.

Cause: Instance existed, but the provided instance name "{0}" was different from the instance name "{1}" found from the instance home.

Action: Either provide a valid instance name or do not provide a name.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20283: Mismatch between domain parameters and Moveplan.

Cause: The provided admin port "{0}" correspond to non ssl port where as moveplan had SSL information.

Action: Provide ssl port.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20284: Parameter validation for component pasteConfig has failed.

Cause: Instance existed, but the provided Oracle Home "{0}" was different from the Oracle Home "{1}" used by the existing instance home.

Action: Either provide a valid Oracle Home or do not provide an Oracle Home.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20285: Unable to update WebLogic monitoring credential in EM agent.

Cause: Some internal operation failed.

Action: Check the clone log file and work around is : {0}
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20287: Domain connection validation has failed.

Cause: The possible causes were: 1. The domain details were not correct. 2. The domain was down. 3. If the port was ssl port, then moveplan did not have right ssl parameters.

Action: Make sure that the domain details are correctly provided and domain is running in the same admin port.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20291: Invalid target instance location.

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

Action: Provide an absolute path for the target instance.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20292: Inventory pointer location file is not valid.

Cause: The inventory {0} found from the invPtrLoc File {1} was not absolute.

Action: Make sure that the inventory pointer location file is valid.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20293: Oracle Home configuration is unsuccessful.

Cause: The OraInventory {0} from invPtrLoc file {1} did not match with OraInventory {2} from reference invPtrLoc file {3}.

Action: Check the clone log or error file and install CloneAction file for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20294: Oracle Home configuration is unsuccessful.

Cause: Unable to find Oracle Home name from the inventory.xml file.

Action: Check the clone log or error file for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20296: Invalid instance location for an existing instance name in the domain.

Cause: There are two possible causes for an invalid instance location {0}: 1. The instance location did not match the registered instance. 2. The instance home did not exist or was not valid.

Action: Provide correct instance name and location.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20297: Invalid instance name for an existing instance location in the domain.

Cause: There are two possible causes for an invalid instance name {0}: 1. The instance name did not match the registered instance. 2. The instance home did not exist or was not valid.

Action: Provide correct instance name and location.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20298: Invalid target location.

Cause: An attempt was made to restore multiple {0} Oracle Homes under same Middleware Home {1}.

Action: There can be only one SOA/WEBCENTER Oracle Home in a Middleware Home.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20299: Oracle Home configuration is unsuccessful.

Cause: Some "no read permission" files were not present.

Action: Check the clone log or error file for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20300: Instance name is already registered with the domain.

Cause: Instance name was already registered with domain but no instance location was associated with it.

Action: Provide another instance name which is not registered with domain.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20301: Jre location update has failed.

Cause: Was unable to find the Java home from the Middleware Home "{0}".

Action: Make sure that the Middleware Home is installed properly.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20302: Invalid Java home.

Cause: The Java home {0} found from System property was not pointing to the Java home. It was pointing to the jre home and its parent was not Java home.

Action: Provide -javaHome <java home path> as command-line parameter to cloningclient.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20303: Invalid Java home.

Cause: The Java home {0} did not have the required files.

Action: Provide a correct Java home.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20304: Invalid Java home.

Cause: Path {0} either was not absolute or did not exist.

Action: Provide an absolute path for the Java home.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20306: Middleware Home cloning is not possible.

Cause: There are three possible causes for the failure of cloning this Middleware Home {0}: 1. WebLogic Server install path {1} was outside of Middleware Home. 2. Cloning script {2} was not present. 3. Cloning script {3} was not present.

Action: Make sure that cloning script is present and WebLogic Server is installed inside Middleware Home.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20307: Invalid path.

Cause: Path {0} was either not absolute or did not exist.

Action: Provide an absolute path.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20312: Oracle instance name is invalid.

Cause: The instance name is already registered with domain.

Action: Provide an instance name which is not registered with domain.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20315: Unable to access Oracle Inventory.

Cause: An attempt was made to execute in silent mode. It was not possible to access the Oracle Inventory.

Action: Provide a valid Oracle Inventory pointer location.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20316: Oracle Home(s) under the Middleware Home have not been included.

Cause: Oracle Home(s) registered with the Oracle Inventory were not present inside the Middleware Home.

Action: Ensure that the Oracle Home(s) present inside the Middleware Home are registered with the Oracle Inventory or provide the correct custom inventory.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20317: Oracle Home(s) under the Middleware Home have not been included.

Cause: Unable to find the Oracle Home(s) registered with the Oracle Inventory.

Action: Ensure that the Oracle Home(s) present inside the Middleware Home are registered with the Oracle Inventory or provide the correct custom Inventory.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20318: Missing argument: {0}.

Cause: Required argument was not provided at command line or in the argument file.

Action: Provide a valid argument.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20319: Invalid Oracle instance home location: {0}.

Cause: Either the directory location does not exist or it is corrupt.

Action: Provide a valid Oracle instance location.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20320: The specified instance name "{0}" does not match calculated instance name "{1}".

Cause: The specified instance name did not match the instance name found from the specified instance home.

Action: Provide correct instance name.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20321: Invalid Oracle Home location: {0}.

Cause: Either the directory location does not exist or it is corrupt.

Action: Provide a valid Oracle Home location.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20322: The specified instance home "{0}" is not associated with specified Oracle Home, but associated with another Oracle Home "{1}".

Cause: The specified Oracle Home "{0}" was not matching with the Oracle Home used by the specified instance.

Action: Provide a correct Oracle Home location.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20324: Unsupported character sequence.

Cause: Input value "{0}" had some unsupported characters.

Action: Name must begin with an alphanumeric character; may only contain alphanumeric characters, or the underscore (_) or hyphen (-) characters; and must be 4 to 30 characters long.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20325: Unsupported Instance home path length.

Cause: Length of Instance home path {0} was equal to {1} and it was exceeding the limit.

Action: Length of instance home path must be less than or equal to {0}
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20326: Domain parameters are missing.

Cause: Target instance did not exist; all domain parameters were not provided.

Action: Provide either all domain parameters or none.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20327: Invalid password file.

Cause: The {0} password file {1} did not exist or first line did not contain password.

Action: Provide a valid password file.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20328: Invalid domain port.

Cause: The domain port was invalid.

Action: Provide a valid port.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20329: Unable to archive Oracle Home {0} and the dependent Oracle Home {1}.

Cause: The Oracle Home {1} was not clonable.

Action: Make sure that the dependent Oracle Home {1} is valid and clonable.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20330: Unsupported Middleware Home cloning.

Cause: Oracle Home {0} was associated with the Middleware Home {1}, but the Middleware Home was not cloneable.

Action: Provide a valid Middleware Home.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20331: Invalid Middleware Home.

Cause: Specified Middleware Home had neither clonable Weblogic binaries nor Oracle Homes.

Action: Provide a valid Middleware Home.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20332: Invalid Middleware Home location.

Cause: Path "{0}" was not absolute or did not exist or an empty directory.

Action: Provide a valid absolute path.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20333: Invalid Domain home location.

Cause: Path "{0}" was not absolute or did not exist or an empty directory.

Action: Provide a valid absolute path.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20334: Invalid Domain home location.

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

Action: Provide valid absolute writable path.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20335: The move plan location is invalid.

Cause: There are five possible causes: 1. The path was not provided. 2. The path was not an absolute path. 3. The path already existed. 4. The parent path did not exist. 5. The parent path did not have write permission.

Action: Provide an absolute path to a directory that does not exist and make sure that its parent location exists and has write permission.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20336: The move plan location is invalid.

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

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

Type: ERROR

Impact: Cloning

CLONE-20337: Unable to persist the move plan.

Cause: Make sure that the move plan location is writable. {0}

Action: Check the logs for details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20338: Error in examining Adapters.

Cause: Adapter examination failed.

Action: Make sure that all the specified values are correct and the domain configuration is valid.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20339: Error in deploying adapters.

Cause: Adapter deployment failed.

Action: Make sure that all the specified values are correct and the domain configuration is valid.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20340: The Plan Directory location is invalid.

Cause: There are four possible causes: 1. The path was not an absolute path. 2. The path already existed. 3. The parent path did not exist. 4. The parent path did not have write permission.

Action: Provide an absolute path to a directory that does not exist and make sure that its parent location exists and has write permission.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20341: Error in copyConfig.

Cause: The AdminServer is down.

Action: Make sure that the AdminServer of the specified domain is started.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20342: Error in deploying Adapters.

Cause: Adapter deployment failed.

Action: Make sure that the deployment plan for {0} is valid or that it exists in the archive.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20343: Error in validating "SERVER_CONFIG".

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

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

Type: ERROR

Impact: Cloning

CLONE-20344: Error in validating "SERVER_CONFIG".

Cause: Specified server {0} does not exist in the source domain.

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

Type: ERROR

Impact: Cloning

CLONE-20345: Error in validating "SERVER_CONFIG".

Cause: Specified port is not valid.

Action: Make sure that valid port numbers are specified in the move plan.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20346: Error in validating "SERVER_CONFIG".

Cause: Specified {0} {1} is not valid.

Action: Make sure that valid port numbers are specified in the move plan.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20347: Error in validating "DATASOURCE".

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

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

Type: ERROR

Impact: Cloning

CLONE-20348: Error in validating "DATASOURCE".

Cause: Specified data source {0} does not exist in the source domain.

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

Type: ERROR

Impact: Cloning

CLONE-20349: Error in validating "DATASOURCE".

Cause: Some of the required parameters of data source {0} are missing in the move plan.

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

Type: ERROR

Impact: Cloning

CLONE-20350: Error in validating "MACHINE_CONFIG".

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

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

Type: ERROR

Impact: Cloning

CLONE-20351: Error in validating "MACHINE_CONFIG".

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

Action: Make sure that no new machines are added to the move plan and also make sure that "configProperty" id is not modified.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20352: Error in validating "MACHINE_CONFIG".

Cause: Specified port {0} is not valid.

Action: Make sure that valid port numbers are specified in the move plan.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20353: Error in exporting metadata.

Cause: MDS Metadata export failed.

Action: Make sure all the servers are started in the specified domain.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20354: Server start failed.

Cause: MDS Metadata import failed. Could not start the server {0}

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

Type: ERROR

Impact: Cloning

CLONE-20355: Error in importing metadata.

Cause: MDS Metadata import failed.

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

Type: ERROR

Impact: Cloning

CLONE-20357: Command-line parameters did not match the script.

Cause: The parameters used for this command were invoked by the wrong script.

Action: Use the '-help' option to see the allowed parameters.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20358: Duplicate instance name.

Cause: Service for the given instance name {0} already existed.

Action: Choose a different instance name.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20359: Values for all mandatory parameters are not provided.

Cause: {0} is empty.

Action: Provide a valid value for {0}
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20360: Could not connect to the AdminServer.

Cause: Specified AdminServer is down or the domain credentials are not correct.

Action: Make sure that specified AdminServer is started and the domain host, domain port, domain user and domain password values are correct.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20361: Error in executing WebLogic script for configuring adapter and application deployments.

Cause: Either the values specified in the moveplan are not correct or the end points are not configured correctly in adapter or application deployment plans.

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

Type: ERROR

Impact: Cloning

CLONE-20362: Connection to AdminServer failed.

Cause: AdminServer start failed. Make sure that AdminServer parameters specified in the move plan are correct.

Action: Check the AdminServer logs.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20363: Adapter deployment failed.

Cause: Adapter redeployment failed. Make sure that all values are specified correctly in the move plans and "READ_ONLY" properties are not changed.

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

Type: ERROR

Impact: Cloning

CLONE-20364: OPSS data {0} failed.

Cause: OPSS data migration script execution failed.

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

Type: ERROR

Impact: Cloning

CLONE-20365: Error in executing WebLogic script for configuring server, cluster , datasource and authenticator.

Cause: Either the values specified in the move plan are not correct or some "READ_ONLY" properties in the move plans are modified or some internal error happened.

Action: Check the t2p logs for more details. Make sure that values in the move plans are correct.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20366: Domain unpack failed.

Cause: Make sure that values specified are correct.

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

Type: ERROR

Impact: Cloning

CLONE-20367: Move plan parsing failed.

Cause: Specified file is not a valid move plan or the move plan is corrupted.

Action: Make sure that the move plan is a valid xml file.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20368: Domain pack failed.

Cause: Make sure that values specified are correct.

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

Type: ERROR

Impact: Cloning

CLONE-20369: Invalid domain application directory.

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

Action: Provide valid absolute writable path and make sure that the user executing the tool and the owner of the domain home directory is the same, for UNIX.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20370: Invalid domain application directory.

Cause: Directory "{0}" is not empty.

Action: Provide a valid non-existing or an empty directory.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20371: Invalid domain location.

Cause: Directory "{0}" is not empty.

Action: Provide a valid non-existing or an empty directory.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20372: Server port validation failed.

Cause: Ports of following servers - {0} - are not available.

Action: Provide valid free ports.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20373: The system temporary directory is inaccessible.

Cause: The system temporary directory "{0}" did not have write permission.

Action: Make sure that system temporary directory has write permission.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20375: Invalid Oracle Home.

Cause: Required files needed for cloning were not found in the Oracle Home {0}.

Action: Make sure that the Oracle Home has the required files for cloning.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20376: T2P operation is not possible.

Cause: T2P-specific binaries were missing from Oracle Home {0}.

Action: Make sure that the Oracle Home has the required files for cloning.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20377: Error in stopping {0} managed server.

Cause: Either the credentials were not correct or the managed server was not running.

Action: Check the server logs for details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20378: Invalid value entered.

Cause: The value of the parameter {0} was invalid.

Action: Provide a valid value for {0}.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20379: Target component information was missing for pasteConfig.

Cause: Either provide "targetComponentName(tcn)" or "targetDomainLoc(tdl)" or "targetNMHomeLoc(tnh)"parameter.

Action: Provide target component information.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20380: Invalid target Middleware Home location.

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

Action: Provide an absolute path for the target Middleware Home.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20381: Target component information was ambiguous.

Cause: Either provide "targetComponentName(tcn)" or "targetDomainLoc(tdl)" parameter.

Action: Provide target component information.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20382: Invalid domain home location.

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

Action: Provide an absolute path for the target domain home.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20383: Invalid move plan directory location.

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

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

Type: ERROR

Impact: Cloning

CLONE-20384: Mandatory parameter missing.

Cause: Parameter "planDirLoc(pdl)" missing for the extractMovePlan command.

Action: Provide parameter "planDirLoc(pdl)" for the extractMovePlan command.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20385: Error in validating "MACHINE_CONFIG".

Cause: Specified name {0} for machine {1} is not valid.

Action: Provide valid machine name.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20386: Oracle Home is not cloneable.

Cause: Install.properties file from Oracle Home {0} did not have correct entries for cloning.

Action: Make sure that the install.properties has correct entries.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20387: Error in validating "CLUSTER_CONFIG".

Cause: Specified move plan had more clusters than in source domain.

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

Type: ERROR

Impact: Cloning

CLONE-20388: Error in validating "CLUSTER_CONFIG".

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

Action: Make sure that no new clusters are added to the move plan and "READ_ONLY" properties are not changed..
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20389: Error in validating "CLUSTER_CONFIG".

Cause: Specified name {0} for cluster was not valid.

Action: Provide valid machine name.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20390: Error in validating "CLUSTER_CONFIG".

Cause: Specified cluster type "{0}" for cluster {1} was not valid.

Action: Valid values are "unicast" and "multicast".
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20391: Error in validating "CLUSTER_CONFIG".

Cause: Specified port {0} was not valid.

Action: Make sure that valid port numbers are specified in the move plan.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20392: Oracle Home is not cloneable.

Cause: There are three possible causes for not being able to clone Oracle Home {0}: 1. Some component(s) were not cloneable. 2. Install.properties file did not have correct entries for cloning. 3. Required files needed for cloning were missing.

Action: Make sure that the Oracle Home is valid.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20393: Error in validating command-line parameter "{0}".

Cause: Path {0} was either not absolute or did not exist.

Action: Provide an absolute path for the command-line parameter "{0}"
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20394: Invalid Domain home location.

Cause: Path "{0}" was not absolute or an empty directory.

Action: Provide a valid absolute path.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20395: Invalid Domain home location.

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

Action: Provide a valid absolute path.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20396: Invalid Domain home location.

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

Action: Provide a valid absolute path. For UNIX systems, make sure that the user executing the script is the same as the user who created the domain.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20397: Error in validating "RDBMS Security Store".

Cause: RDBMS Security Store was not enabled in source domain

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

Type: ERROR

Impact: Cloning

CLONE-20398: Error in validating "RDBMS Security Store".

Cause: {0} for RDBMS Security Store was not valid.

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

Type: ERROR

Impact: Cloning

CLONE-20399: Error in examining OWSM policies.

Cause: OWSM policy examination failed.

Action: Make sure that all the specified values are correct and domain configuration is valid. Check managed server logs and clone logs for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20400: OWSM policy migration failed.

Cause: Either the managed servers targeted to OWSM application were down or the application was not in active state.

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

Type: ERROR

Impact: Cloning

CLONE-20401: Error in examining OWSM policies.

Cause: OWSM policy examination failed.

Action: Make sure that all the specified values are correct and domain configuration is valid. Check managed server logs and clone logs for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20402: The move plan file is invalid.

Cause: The xml file was not a valid multi archive moveplan.

Action: Provide a valid xml file for multi archive moveplan.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20403: Unable to complete application deployment plan export.

Cause: Error in examining applications for custom deployment plan.

Action: Check logs for details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20404: Error in deploying applications with custom deployment plan.

Cause: Application deployment failed.

Action: Make sure that the deployment plan for {0} is valid or exists in archive.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20405: Application deployment failed.

Cause: Application redeployment failed. Make sure that all values are specified correctly in the move plans and "READ_ONLY" properties are not changed.

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

Type: ERROR

Impact: Cloning

CLONE-20406: Invalid move plan directory location.

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

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

Type: ERROR

Impact: Cloning

CLONE-20407: Invalid move plan directory location.

Cause: Move plan directory location was empty.

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

Type: ERROR

Impact: Cloning

CLONE-20409: OPSS Configuration failed.

Cause: Specified LDAP details were either wrong or LDAP was not running.

Action: Make sure that LDAP details are correct and LDAP is up and running.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20410: The move plan file is invalid.

Cause: The provided file was not a valid xml moveplan file.

Action: Provide a valid xml moveplan file.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20411: Unable to update WebLogic monitoring credential in EM agent.

Cause: An internal operation failed.

Action: Check the clone log file for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20412: Insufficient arguments.

Cause: An attempt was made to perform "{0}" operation. No argument was provided from the following supported arguments : "{1}".

Action: Provide valid arguments.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20413: Unsupported command argument(s).

Cause: An attempt was made to perform "{0}" operation. Some of the arguments are not supported by this operation on this OS platform. The supported arguments are: "{1}".

Action: Provide valid arguments.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20414: Unsupported command argument(s).

Cause: An attempt was made to perform "{0}" operation of "{1}". Some of the arguments are not supported by this operation. The supported arguments are :"{2}".

Action: Provide valid arguments.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20415: Insufficient arguments.

Cause: An attempt was made to perform "{0}" operation of "{1}". Following required arguments were missing: "{2}".

Action: Provide required arguments.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20416: Arguments combination is invalid.

Cause: An attempt was made to perform "{0}" operation of "{1}" type.

Action: Provide valid arguments for a particular type.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20417: Insufficient arguments to decide exact operation.

Cause: An attempt was made to perform "{0}" operation. Unable to decide type of operation from provided arguments. The supported arguments for this operation are: "{1}".

Action: Provide valid arguments.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20418: Invalid path.

Cause: The value provided for argument "{0}" was "{1}". There are five possible causes: 1. The path was not an absolute path. 2. The path did not exist. 3. The path did not represent a file. 4. The file did not have read permission. 5. The file size was zero.

Action: Provide a valid path.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20419: Invalid path.

Cause: The value provided for argument "{0}" was "{1}". There are six possible causes: 1. The path was not an absolute path. 2. The path did not exist. 3. The path did not represent a directory. 4. It was an empty directory. 5. The directory represented by the path did not have read permission. 6. If environment is UNIX, the directory represented by the path did not have executable permission.

Action: Provide a valid path.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20420: Invalid path.

Cause: The value provided for argument "{0}" was "{1}". There are four possible causes: 1. The path was not an absolute path. 2. The path was already existing. 3. The parent directory did not have write permission. 4. If environment is UNIX, there was no executable permission on the existing directory.

Action: Provide absolute path and make sure that it does not exist and its parent directoy is writable.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20421: Invalid integer value.

Cause: The value provided for argument "{0}" was "{1}" and it was not a valid positive integer.

Action: Provide a valid positive integer.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20422: Invalid boolean value.

Cause: The value provided for argument "{0}" was "{1}" and it was not a boolean value.

Action: Provide either "true" or "false".
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20423: Invalid password file.

Cause: The value provided for argument "{0}" was "{1}". There are six possible causes: 1. The path was not an absolute path. 2. The path did not exist. 3. The path did not represent a file. 4. The file did not have read permission. 5. The file size was zero. 6. The file did not carry first line as password.

Action: Provide a valid password file.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20424: Invalid path.

Cause: The value provided for argument "{0}" was "{1}". There are five possible causes: 1. The path was not an absolute path. 2. The path was existing. It was not an empty directory. 3. The path was not existing. Unable to create all the non existing directories. 4. The path was existing. It did not have write permission. 5. If environment is UNIX, there was no executable permission on the existing directory.

Action: Provide absolute path of either a non existing or an existing empty directory and make sure that it is writable
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20425: Archive file is not provided.

Cause: An attempt was made to perform "{0}" operation. Archive file is a mandatory argument.

Action: Provide valid archive file.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20426: Archive file is invalid.

Cause: This file was invalid for "{0}" operation. This archive was not created using T2P "{1}" operation.

Action: Provide valid archive file.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20427: Required arguments are not provided.

Cause: An attempt was made to run pasteConfig operation by providing an non existing instance home. The following required arguments were missing :"{0}".

Action: Provide required arguments.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20428: Instance home location is invalid.

Cause: An attempt was made to run pasteConfig operation for the component by providing an existing instance home. There are two possible causes: 1. Instance did not have the required configuration files. 2. Instance was not associated with a valid Oracle Home.

Action: Provide a valid instance home location.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20429: Middleware Home is invalid.

Cause: An attempt was made to run "{0}" operation of "{1}". The Middleware Home "{2}" was invalid.

Action: Provide a valid Middleware Home location.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20430: Invalid string value.

Cause: The value provided for argument "{0}" was "{1}" and it was not a valid string value.

Action: Provide a non-empty value.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20431: Component name in invalid.

Cause: The instance "{0}" was already configured with component name "{1}".

Action: Provide a unique component name.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20432: Invalid path.

Cause: The value provided for argument "{0}" was "{1}". There are five possible causes: 1. The path was not an absolute path. 2. The path was existing. It was not a directory. 3. The path was not existing. Unable to create all the directories. 4. The path was existing. It did not have write permission. 5. If environment is UNIX, there was no executable permission on the existing directory.

Action: Provide absolute path of a directory and make sure that it is writable.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20434: Invalid component name.

Cause: There are two possible causes for the component name {0}:1. Length of the component name was either too short or too large.2. Component name had contained unsupported characters.

Action: Provide valid component name.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20435: Some of the Oracle Homes are excluded during copy operation.

Cause: The following Oracle Homes will be excluded during copy operation. {0} and possible causes are:1. The Oracle Homes are registered with different inventory.2. The Oracle Homes are not clonable.

Action: Check the clone log and error file for more information.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20436: Moveplan is not correct.

Cause: The instance was registered with a non ssl domain where as moveplan had ssl information.

Action: Remove {0} config group from the moveplan and execute pasteConfig operation again.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20437: Moveplan is not correct.

Cause: The instance was registered with a ssl domain where as moveplan did not have ssl information.

Action: Provide a correct moveplan having ssl information.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20438: Instance does not have valid wls.connect.properties file.

Cause: There are two possible causes :1. Either file did not exist.2. File did not have correct entries to find out weblogic.home , keystore type and keystore location.

Action: Make sure that the wls.connect.properties file present at "{0}" is proper.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20439: MovePlan is not correct.

Cause: The config group {0} didn't have correct values for some or all of the following config properties {1}.

Action: Make sure that the moveplan has correct entry.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20440: MovePlan is not correct.

Cause: There was a mismatch betweeen moveplan and wls.connect.properties. The value of config property {0} was {1} where the corresponding value in wls.connect.properties was {2}.

Action: Make sure that the moveplan has correct entry.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20441: MovePlan is not correct.

Cause: The wls.connect.properties had no password where as moveplan's config property {0} had password or vice versa.

Action: The moveplan should have value for the password property if and only if wls.connect.properties has corresponding property.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20442: MovePlan is not correct.

Cause: The password from file mentioned in moveplan's config property {0} is not matching with the password mentioned in wls.connect.properties

Action: Make sue that the both passwords are same.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20443: Domain admin password is missing.

Cause: An attempt was made to execute pasteConfig operation in silent mode without providing domain password.

Action: In silent mode, provide domain password in command line argument.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20444: Mismatch between archive file and multi archive moveplan.

Cause: The archive file used during this pasteConfig operation was not provided during execution of extractMovePlan command.

Action: Execute extractMovePlan command again by providing the archive file {0} along with other archive files created during copyConfig process.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20500: Arguments combination is invalid.

Cause: The -sourceNMHomeLoc was provided along with -sourceMWHomeLoc.

Action: Provide either -sourceNMHomeLoc or -sourceMWHomeLoc.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20501: Arguments combination is invalid.

Cause: The -sourceInstanceHomeLoc and/or -sourceComponentName was provided along with -sourceNMHomeLoc.

Action: Provide either -sourceInstanceHomeLoc and/or -sourceComponentName or -sourceNMHomeLoc.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20502: Arguments combination is invalid.

Cause: The -sourceDomainLoc was provided along with -sourceNMHomeLoc.

Action: Provide either -sourceDomainLoc or -sourceNMHomeLoc.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20503: Unable to resolve source Node Manager home.

Cause: The path provided with -sourceNMHomeLoc either did not exist or was not absolute.

Action: Provide an existing and absolute path with -sourceNMHomeLoc.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20504: Invalid Node Manager Home Location.

Cause: Path "{0}" was not absolute or did not exist or an empty directory.

Action: Provide a valid absolute path.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20505: Target component information was ambiguous.

Cause: Either provide "targetComponentName(tcn)" or "targetNMHomeLoc(tnh)" parameter.

Action: Provide target component information.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20506: Target component information was ambiguous.

Cause: Either provide "targetDomainLoc(tdl)" or "targetNMHomeLoc(tnh)" parameter.

Action: Provide target component information.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20507: Invalid target Node Manager home location.

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

Action: Provide an absolute path for the target Node Manager home.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20508: Invalid target Node Manager home location.

Cause: Path {0} exists but is not a directory.

Action: Provide an empty or non-existing directory location for the target Node Manager home.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20509: Invalid target Node Manager home location.

Cause: Path {0} exists but is not an empty directory.

Action: Provide an empty or non-existing directory location for the target Node Manager home.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20510: Move Plan does not contain any domain information.

Cause: Source Node Manager may not have been registered with any domain.

Action: Register source Node Manager with the available domains on the machine and run the t2p utility again.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20511: Unable to retrieve AdminServer Password for domain{0}.

Cause: Either the password file {0} did not exist, or the AdminServer password was empty.

Action: Provide a valid password file for AdminServer Password.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20512: Unable to determine AdminServer credentials for domain {0} from Move Plan.

Cause: Either one of AdminServer Listen Address, AdminServer Listen Port, AdminServer User Name or AdminServer Password for domain {0} was not provided in the MovePlan.

Action: Provide valid AdminServer credentials in the Move Plan and run the t2p utility again.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20513: Unable to determine NodeManager credentials for domain {0} from Move Plan.

Cause: Either one of NodeManager User Name or NodeManager Password for domain {0} was not provided in the MovePlan.

Action: Provide valid NodeManager credentials in the Move Plan and run the t2p utility again.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20514: Unable to retrieve NodeManager Password for domain{0}.

Cause: Either the password file {0} did not exist, or the NodeManager password was empty.

Action: Provide a valid password file for NodeManager Password.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20515: Unable to connect to AdminServer for domain(s) {0}.

Cause: The AdminServer for domains(s) {0} was not running.

Action: Bring up the AdminServer for each domain before running the t2p utility.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20516: Error while checking the available port for Node Manager.

Cause: The port {0} was not available for the Node Manager.

Action: Provide an available port for Node Manager in nodemanager.properties.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20517: Error while trying to start the Node Manager.

Cause: Operation timed out while trying to start the Node Manager.

Action: Check the nodemanager.log file for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20518: Error in trying to read password from file {0} .

Cause: File {0} does not exists.

Action: Provide an existing password file in which the first line is the password.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20519: Error in retrieving password from file {0} .

Cause: The first line of file {0} does not contain a valid password.

Action: Provide an existing password file in which the first line is the password.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20600: Unable to derive value of all config properties.

Cause: Could not derive values for some properties that had reference to other config properties.

Action: Check clone log file for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20601: Unable to derive frontend host.

Cause: The Listen address from OHS was not in proper format.

Action: The frontend host can be updated later from Weblogic console.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20602: Unable to derive frontend port.

Cause: The Listen address from OHS was not in proper format.

Action: The frontend port can be updated later from Weblogic console.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20603: Error in validating "SERVER_CONFIG".

Cause: Specified "{0}" file for server "{1}" was not valid.

Action: Make sure that "{0}" file is valid.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20604: Error in validating command line parameters.

Cause: Some command line arguments may be missing or invalid or the archive provided may not be proper or valid

Action: Make sure that valid values are provided for all the required arguments and the archive is valid.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20605: Invalid target domain directory name.

Cause: Provided target domain directory name "{0}" did not match with source domain directory name "{1}".

Action: Make sure target domain directory name is not changed.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20606: Error in validating source environment.

Cause: All managed servers were down in the provided source environment. The "copyConfig" operation requires all the managed servers to be up and running.

Action: Make sure that all managed servers are up and running.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20607: Error validating source environment.

Cause: Provided source domain is in edit mode.

Action: Activate all unsaved changes in source domain and re-run "copyConfig".
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20608: Error reading composites.

Cause: Composite configuration plan "{0}" could not be read.

Action: Make sure that the file exists and has read permission.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20609: Error updating composites.

Cause: Composite configuration plan "{0}" could not be updated.

Action: Make sure that the file exists and has write permission.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20610: Error validating source NodeManager Home.

Cause: Specified source NodeManager Home location is not valid. "nodemanager.properties" file is not present under NodeManager Home location.

Action: Make sure that source NodeManager Home location is correct and all required files are present.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20611: Error validating source NodeManager Home.

Cause: Specified source NodeManager Home location is not valid. "nodemanager.domains" file is not present under NodeManager Home location.

Action: Make sure that source NodeManager Home location is correct and all required files are present.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20612: Error in executing wlst script.

Cause: {0} did not exist.

Action: Make sure that specified Middleware Home and all Oracle Homes inside Middleware Home are valid.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20613: Listen port validation failed.

Cause: Specified port, {0} is either not valid or not available.

Action: Provide valid free port.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20614: NodeManager listen address validation failed.

Cause: Specified listen address was not configured on a local network interface.

Action: Provide a valid local listen address on which the NodeManager should come up.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20615: Source middleware home location validation failed.

Cause: Specified domain is not registered with the source middleware home.

Action: Make sure that specified domain home is registered in "domain-registry.xml" of source middleware home.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20616: Domain credentials validation failed.

Cause: Specified domain credentials were not of the source domain location.

Action: Make sure that specified source domain location and domain credentials are valid.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20617: Error reading MDM URL Resolver configuration.

Cause: MDM URL Resolver configuration file "{0}" could not be read.

Action: Make sure that the file exists and has read permission.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20618: Error updating MDM URL Resolver configuration.

Cause: MDM URL Resolver configuration file "{0}" could not be updated.

Action: Make sure that the file exists and has write permission.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20619: OPSS reassociation failed.

Cause: Execution of reassociateSecurityStore to target environment failed.

Action: Check the T2P logs for details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20620: AdminServer restart failed.

Cause: Could not restart AdminServer.

Action: Check the T2P logs and AdminServer logs for details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20621: Data source creation failed.

Cause: Error in creating OPSS datasource.

Action: Check T2P logs for details. Make sure values provided in moveplan for "OPSS_CONFIG" are correct.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20622: OPSS Store is not migrated.

Cause: OPSS store is not migrated to target LDAP.

Action: Move LDAP data from source to target before running "pasteConfig".
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20623: OPSS store configuration failed.

Cause: Modification of bootstrap credential failed.

Action: Check clone log file for error details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20624: Unable to find any registered oracle home(s) in the provided middleware home.

Cause: Inventory might be corrupted or deleted.

Action: Make sure that the inventory with which the middleware home is registered is proper.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20635: OPSS data {0} failed.

Cause: Unable to find "{0} / {1} / {2}" at "{3}".

Action: Make sure these files exist and are accessible.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20636: OPSS data import failed.

Cause: Unable to seed the schema.

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

Type: ERROR

Impact: Cloning

CLONE-20637: OPSS data import failed.

Cause: Unable to add ldap container.

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

Type: ERROR

Impact: Cloning

CLONE-20638: OPSS data {0} failed.

Cause: Unable to update {0}.

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

Type: ERROR

Impact: Cloning

CLONE-20639: Connection to {0} failed.

Cause: There are two possible causes: 1. Server might be down. 2. Credentials provided might be wrong.

Action: Make sure server is running and credentials are valid.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20640: OPSS data {0} failed.

Cause: Unable to find "{0}" at "{1}".

Action: Make sure this file exist and is accessible.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20641: An internal operation failed.

Cause: Component registration xml, {0} is not a valid xml file.

Action: Make sure that {0} is a valid component registration xml file and is not corrupted.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20642: Additional parameter format not valid. The value provided for argument "{0}" was "{1}"

Cause: There are three possible causes: 1. Parameter value may be null. 2. Parameter value is not a key-value pair. 3. If more than one key-value pair is passed, they may have not been seperated using ,(comma).

Action: Make sure additional parameter is following a proper syntax. Syntax : -additionalParams property1=value1,property2=value2 Example: -additionalParams server=orclSv1,port=8888 Note:','(comma) and '='(equal) characters cannot be directly used within the key or value. They can be used by replacing them with the escape character as mentioned below ','(comma) -> %2C '='(equal) -> %3D Example: -additionalParams server=srv1%2CfailoverServer%3Dsrv2,ports=8888%2C8881
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20643: Move plan comparison failed.

Cause: The move plan xml passed in the argument does not contain the same meta data as the one present in archiveMeta data property "{0}" from argument move plan is "{1}" Meta data property "{0}" from archive move plan is "{2}"

Action: Make sure the move plan is actually generated from the archive passed in the argument.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20644: Invalid passphrase file.

Cause: The {0} passphrase file {1} did not exist or first line did not contain passphrase.

Action: Provide a valid passphrase file.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20645: Invalid value.

Cause: The {0} value is empty.

Action: Provide a valid value for {0} property.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20901: Unable to restore permission of a few files of the Oracle Home {0}. Check the log file {1} for details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20902: An attempt was made to execute system prerequisites, but unable to load prerequisites jars.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20903: An attempt was made to execute system prerequisites, but unable to load OUI and engine jars.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20904: Error happened while shutting down the managed servers. Check the t2p logs for details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20905: OPSS store reassociation from {0} to {1} is not supported. OPSS store will not be reassociated to {2}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20906: OPSS store reassociation values are not provided. Source Domain OPSS store will be used for unpacked domain.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20907: {0} Details provided for OPSS configuration is same as source domain. Reassociation will not be executed.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20908: Deployment plan ({0}) specified for {1} does not exist. {2} will not be added to the move plan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20909: Application deployment plan ({0}) specified for {1} does not exist. {2} will not be added to the move plan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20910: Default Authenticator data export failed.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20911: Default Authenticator data import failed.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20912: WebLogic Server home is not valid. Make sure that Middleware Home location is valid.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20913: {0} is not a valid configProperty for {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20914: Exception caught while creating Move Plan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20915: Exception occurred while trying to write FMWClonerBean to File.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20916: Exception occurred while trying to write CopyArgBean to File.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20917: Exception occurred while deserializing FMWClonerBean from File.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20918: Exception occurred while deserializing CopyArgumentBean from File.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20919: Error in enrolling NodeManager with domain {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20920: NodeManager default startup script {0} does not exists.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20921: Unable to start the Node Manager.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20922: Error in starting the Node Manager.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20923: Error in examining OWSM targets. Verify that OWSM targeting is fine post paste config.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20924: Unable to establish a connection to the MBean server to verify an active edit session. Make sure that an edit session is not active in the domain.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20925: Error in validating RDBMS security store properties. Could not establish connection to the RDBMS security store.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20928: OPSS policies are not migrated to target LDAP. Domain start might fail.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20929: Unable to find any valid plug-in(s) in the provided middleware home.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20930: Error occurred while adding default realm data to archive.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20931: Error occurred while extracting default realm data from archive.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20932: optimizationHints argument is required during extract move plan for multi archive mode. Use -optimizationHints (-opth) option to specify optimization hints.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20933: At least one valid optimization flag has to be specified. Flag(s) provided are : {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21001: As -sourceOracleHomeLoc has been provided, only the Oracle Home(s) specified along with this parameter will be honored.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21002: The sourceid was not provided, proceeding with default sourceid "{0}" to restore the archive.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21003: Unable to find Oracle Home(s), as inventory is not accessible.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21004: Some files are missing. Check clone log file to see all the missing files.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21005: Cloning operation completed with warning.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21006: Total time taken by T2P process was {0} seconds.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21007: Cloning operation completed successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21008: As "{0}" file does not exist, this Middleware Home will not be archived.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21009: The Middleware Home that will be included in the archive is {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21010: The Oracle Home "{0}" will be excluded as it is mentioned in exclude pattern.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21011: The archive will contain only Oracle Home(s) {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21012: The archive will be restored fully at {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21013: Trying to find Oracle Home(s) present under Middleware Home {0}...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21014: Adding specific files from Oracle Home {0} that will be required to execute system prerequisites during pasteBinary ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21015: Adding all required files for execution of system prerequisites finished.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21016: Adding Oracle Home "{0}" to the archive started ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21017: Adding Oracle Home {0} to the archive finished.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21018: Extracting at "{1}" location started ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21019: Extracting at "{1}" location finished.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21020: Configuration for Oracle Home {0} is in progress ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21021: Configuration for Oracle Home {0} completed successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21022: Applying permission for {0} started ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21023: Applying permission for {0} finished. Operation complete in "{1}" seconds.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21024: A configuration script needs to be run as root at the end of clone operation. Run "{0}/oracleRoot.sh" as root.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21025: Restoring Middleware Home at "{0}" from archive "{2}" started ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21026: Restoring Middleware Home at "{0}" from archive "{2}" finished.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21027: Provided invPtrLoc was empty.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21028: Unable to find component detail from Oracle Home.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21029: Unable to find top component detail from Oracle Home.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21030: Adding "{0}" to the archive is successful.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21031: Time taken to add all the cloners to archive was "{0}" seconds.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21032: Archive created successfully at {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21033: Unable to find any Middleware Home or Oracle Home for archiving.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21034: The archive will contain only the Middleware Home {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21035: Restoring the home finished successfully at {1}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21036: Restoring the component finished successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21037: Time taken to restore all cloners from archive was "{0}" seconds.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21038: The archive will contain both Middleware Home {0} and Oracle Home(s) {1}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21039: Gathering all sourceid(s) present in the archive.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21040: Oracle Home archive # {0}, home location {2}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21041: Middleware Home archive # {0}, home location {2}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21042: Component archive # {0}, instanceName@componentName {1}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21043: J2EE component archive # {0}, sourceid {1}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21044: Unable to find JRockit JAVA HOME from registry.xml file.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21045: Permission file created successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21046: Permission file creation failed.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21047: Permission for new Oracle Home {0} is not set properly, and permissionFilePath relative to Oracle Home is {1}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21048: Adding all required files to the main archive started ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21049: Canonical path of the following files did not exist, and their absolute path is:

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21050: List of files without read permission:

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21051: Adding permission file to the archive started ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21052: Adding permission file to the archive finished. Operation completed in "{0}" milliseconds.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21053: Total size of the file(s), to be included in the main jar from source location {0}={1} GB.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21054: Unable to read "{0}" file while adding files to the jar file.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21055: In {1} seconds, {0}% has completed.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21056: Time taken for adding files to archive was {0} milliseconds.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21057: Execution of system prerequisites for Oracle Home {0} started ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21058: Execution of system prerequisites finished.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21059: Output of the process can be checked in the file {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21060: No system prerequisites will be executed for the Oracle Home {0} as it is set to false.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21061: No system prerequisites will be executed for the Oracle Home {0} as no system prerequisites files are available for this Oracle Home.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21062: The Java home {0} found from the system property was not pointing to a Java home, it might pointing to jre home, trying to check if its parent is a Java home

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21063: The {0} is not a valid Java home.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21064: Updating Oracle Home information for Oracle Home {0} ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21065: Updating Oracle Home information completed for Oracle Home {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21066: Updating Oracle Home information failed for Oracle Home {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21067: Unregistering all instances(which were present in source domain) from target domain...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21068: Trying to unregister instances {0} from domain...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21069: All the instances are unregistered from domain successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21070: Unable to unregister following instances {0} from domain.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21071: Permission file created with warnings.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21072: Unregisteration of all instances(which were present in source domain) from target domain completed successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21073: INSTANCE archive # {0}, sourceid {1}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21074: Trying to retrieve domain name ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21075: Domain name is {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21076: Trying to check whether Weblogic monitoring Credential for EM is already set in domain or not ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21077: Weblogic monitoring Credential for EM is already set.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21078: WLS credential is not set in EM, trying to set it ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21079: Updating Weblogic monitoring Credential for EM in the domain ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21080: Weblogic monitoring Credential is updated successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21081: Parsing moveplan to get component name and component type ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21082: Parsing multi archive moveplan ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21083: Creating updated moveplan for component name "{0}" and component type "{1}".

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21084: Checking whether any config property has still reference to other config property or not.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21085: Updating component specific moveplan from multi archive moveplan ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21086: Updating component specific moveplan from multi archive moveplan for "{0}" ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21087: No config property has any reference to other config property.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21088: ASInstance {0} is configured with following components: {1}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21089: Oracle Home {0} has following t2p plugins : {1}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21090: Provide invPtrLoc:

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21091: Usage: <path to java> -jar <path to cloningclient.jar> <command> <command>: <Clone command> <Clone command>:

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21092: For help on a particular command, use [ <path to java> -jar <path to cloningclient.jar> -help <command>]

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21093: To proceed enter "yes", or any other text to abort:

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21094: Clone operation was aborted.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21095: Create archive for {0} started ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21096: Process complete in {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21097: Addition of the Oracle Home {0} to the archive started ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21098: Enter domain Administrator password:

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21099: From instance {0}, the type and name of the components on which T2P will be performed are :{1}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21100: From instance {0}, the name of the components on which T2P will be performed are :{1}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21101: Under instance {0}, there are no movable components.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21102: T2P cannot be performed on all components present under instance {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21103: Log path "{0}" should be absolute and existing directory has write permission. This condition was not satisfied.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21104: The number of Oracle Homes and Middleware Homes present in the archive is {0} and {1} respectively.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21105: Archive is invalid as it has home(s) and component(s).

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21106: Execution of system prerequisites has completed with warnings and/or to be verified. To proceed enter "yes", or any other text to abort:

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21107: T2P cannot be performed on all components present under instance {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21108: Archiving movable components ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21109: Archiving of movable components completed successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21110: As the archive has only one Middleware Home and no Oracle Home, targetLocation should not exist, and its parent should exist.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21111: As the archive has no Middleware Home and one or more Oracle Home(s), targetLocation should exist, so that all the Oracle Home(s) will be restored under it.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21113: As the number of Oracle Home(s) {0} and Middleware Home {1}, the Middleware Home will be restored at nonexistent targetLocation, and all the Oracle Home(s) will be restored under it.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21114: Unable to find JDK JAVA Home from registry.xml file.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21115: Trying to find JRockit JAVA Home from registry.xml file.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21116: JAVA Home found from Middleware Home is {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21117: Path {0} is invalid. Either it is not absolute or does not have valid characters. The supported characters are "{1}" These three characters "_.-" are not allowed in the beginning.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21118: Adding symbolic link files detail to the archive started ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21119: Adding symbolic link files detail to the archive finished. Operation complete in "{0}" milliseconds.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21120: Adding all files detail to the archive started ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21121: Adding all files detail to the archive finished. Operation complete in "{0}" milliseconds.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21122: File "{0}" is missing.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21123: Symbolic link file is not present or not properly linked, where absolute path should be "{0}" and canonical path should be "{1}", but canonical path found is "{2}".

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21124: Oracle Inventory has updated successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21125: All the symbolic link files are present in the Oracle Home.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21126: Operation is {0}% complete, in "{1}" seconds.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21127: Oracle Home pasteBinary post validation, inventory validation started ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21128: Oracle Home pasteBinary post validation, symbolic link validation started ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21129: Under Middleware Home {0}, one {1} Oracle Home is already present and the Oracle Home path is {2}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21130: The component {0} under Oracle Home {1} is not cloneable.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21131: Updating Windows shortcut for Oracle Home {0} started ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21132: Updating Windows shortcut for Oracle Home {0} finished.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21133: To archive only the Middleware Home provide "-excludeOracleHomes true" as command-line argument.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21134: Creating cloner objects for components ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21135: Cloner objects are created for components.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21136: Creating and starting ASInstance ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21137: ASInstance created and started successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21138: Executing all component cloner objects ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21139: Execution of all component cloner objects completed successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21141: CloningClient build label is "{0}".

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21142: CloningClient version is "{0}".

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21143: Log File: "{0}". Error File: "{1}".

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21144: Unable to create log directory {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21145: The message id "{0}" is invalid for message type {1}, It did not start with "CLONE", or it did not end with "-INFO" where message type=INFO or it did not end with "-TRC" where message type=TRACE or it did not end with "-SVR" where message type=SEVERE or it did not end with "-ERR" or "-CAUSE" or "-ACTION" where message type=ERROR or its length was not be equal to "{2}".

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21146: Oracle Home {0} is registered with the Oracle Inventory {1}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21147: Oracle Home {0} is registered by the name {1} with the Oracle Inventory.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21148: Oracle Home {0} passed post validation.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21149: Oracle Home {0} failed post validation.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21150: Shortcut name "{0}" will be used.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21151: Shortcut name "{0}" is already present.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21152: New Oracle Home folder name in shortcut will be "{0}".

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21154: Checking free space availability for copyBinary operation.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21155: Required free space is available for copyBinary operation.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21156: Extracting all the homes from the archive file. Extraction time will vary depending upon the archive size ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21157: The size of the all homes are {0} GB.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21161: In the domain the available instance name(s) and their corresponding location(s) are {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21163: Adding details regarding files without read permission to the archive, started ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21164: Adding details regarding files without read permission to the archive, finished. Operation complete in "{0}" milliseconds.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21165: In the source Oracle Home, some files have no read permission. Those files are not present in the cloned Oracle Home.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21166: Addition of the Middleware Home {0} to the archive started ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21167: Creating archive of Middleware Home {0} started ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21168: Creating archive of Middleware Home {0} finished.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21169: Adding archive of Middleware Home {0} to the main jar file started ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21170: Adding archive of Middleware Home {0} to the main jar file finished.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21171: Extracting Middleware Home jar file from main jar ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21172: Extracting Middleware Home jar to the target location {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21178: The source Middleware Home was not installed with JDK or JRockit.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21179: The new Middleware Home will be restored using Java home {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21181: The instance is registered with the domain with following details: domainHost={0}, domainPort={1}, domainAdminUser={2} and protocol={3}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21182: Ignoring ssl information mentioned in the moveplan as either domain details were not provided in command line or instance was existing and not registered with the domain.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21183: Will try to use domainHost {0}, domainPort {1}, domainAdminUser {2} as used by instance.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21184: ASInstance will be configured without domain.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21185: ASInstance will be configured with domain.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21186: Validating domain connection.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21187: Connection obtained successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21188: Component will be configured without domain.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21189: Component will be configured with domain.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21190: Instance {0} is not registered with any domain, so the domain parameters are ignored.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21191: Instance "Create & Start" step failed.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21192: Target Instance Directory: {0} already exists. Skipping Instance Creation Step.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21193: Error while parsing "{0}" password file: "{1}" for password.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21194: Starting Instance Failed.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21196: The port "{0}" is free for use.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21197: The port "{0}" is not free for use.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21198: Trying to use source port "{0}".

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21199: Trying to get a new port between lower port {0} and higher port {1}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21200: Unable to calculate new port.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21201: New value for port "{0}".

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21202: Oracle Common home "{0}" exists, and is valid.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21203: The {0} password file: "{1}", either does not exist or is zero size.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21204: ERROR

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21205: CAUSE

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21206: ACTION

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21207: There is an existing component with the same name: {0} under the instance: {1}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21208: Setting the component name to: {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21209: Creating instance where the instance home location is {0} and the instance name is {1}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21210: Instance {0} created and started successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21211: Registering instance with the domain where the host is {0} and the port is {1}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21212: Instance is registered with domain successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21213: EMAgent creation started ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21214: EMAgent creation finished.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21215: Middleware Home "{0}" has non clonable Weblogic binaries. Checking for Oracle Homes ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21216: Performing post operation, if any ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21217: Post operation completed.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21218: Post operation failed.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21219: Validating whether service for the given instance name "{0}" already exists or not.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21220: Service for the given instance name "{0}" does not exist.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21221: SEVERE

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21222: System prerequisite specific files are not present in the Oracle Home, continuing...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21223: Deleting half-created archive file...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21224: Starting Oracle instance {0}...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21225: Oracle instance {0} started successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21226: Creating Move Plan...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21227: Extracting move plan and configplan(s) from archive(s)...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21228: Extracting plans from archive {0} under {1}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21229: Creating move plan by merging move plan(s)...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21230: Trying to derive OHS configuration from J2EE configuration...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21231: Trying to derive WebLogicCluster of OHS from J2EE configuration...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21232: Trying to derive OHS configuration within itself...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21233: Trying to find out component name and component type from archive ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21234: Laying down move plan(s) and other plan(s) from archive...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21235: Updating location of composite, MDM url resolver and adapter in move plan, if any...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21236: Move plan created successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21237: Creating component specific updated move plan from move plan {0}...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21238: Trying to derive nodemanager configuration properties...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21239: Optimizing J2EE domain configuration ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21240: Optimizing J2EE domain configuration for {0} ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21241: Optimizing J2EE domain configuration for DataSource driverclass, jdbc url, schema name and password for all DB schema based on optimization hints ssn={0} ssp={1} sdt={2}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21242: Flag {0} is provided to perform more optimization.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21243: No {0} config property will be populated in moveplan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21244: Only unique {0} config property will be populated in moveplan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21245: Source domain had file based OPSS_SECURITY configuration.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21246: Trying to find out whether user has changed OPSS configuration from file based to LDAP or DB based in move plan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21247: User has updated the OPSS configuration from file based to LDAP or DB based.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21248: User has not changed the OPSS file based configuration, so OPSS configuration will be same as source.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21249: IN the archive, component name is "{0}" and component type is "{1}".

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21250: Updating composite configuration plans ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21251: ERROR: There is a reference for host and port to tpid "{0}", but unable to find values for these tpid.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21252: ERROR: Config property having tpid "{0}" and value "{1}" is not in host:port pattern, but some other config properties depends upon it.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21253: ERROR: There is a reference to tpid "{0}", but unable to find values for these tpid.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21254: ERROR: There is a reference for host to tpid "{0}" and for port to tpid "{1}", but unable to find values for these tpid.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21255: ERROR: The reference tpid "{0}" is not in proper format.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21256: ERROR: Config property having tpid "{0}" and value "{1}" has no domain name, but some other config properties depends upon it.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21257: Unable to derive value for T2P unique id "{0}"

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21258: Updating application deployment plans ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21259: Unable to optimize host port value in composite configuration plan "{0}". Update this file before pasteConfig operation.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21260: All the host port values present in composite configuration plans of all the domains are optimized.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21261: Unable to optimize host port value in MDM URL Resolver file "{0}". Update this file before pasteConfig operation.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21262: All the host port values present in MDM URL Resolver file of all the domains are optimized.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21263: Updating MDM URL Resolver configuration ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21264: OPSS configuration complete. AdminServer will now be restarted.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21265: Stopping AdminServer...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21266: {0} does not appear to contain an obfuscated password. Assuming plaintext...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21272: {0} OPSS data...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21273: Warning: optimizationHints argument is not required during extract move plan for single archive mode. Ignoring the argument.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21274: Warning: The following optimizationHints flag are not supported and hence ignoring - {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21275: Warning: -domainAdminPassword argument has been deprecated. Use -domainAdminPasswordFile instead.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21290: Validating WLS connection and SSL information present in the moveplan ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21291: Validating SSL information present in the moveplan, if any ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-22001: CreateClonerInfo object should not be empty at this point.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22002: Source type "{0}" was either empty or was not supported.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22003: The provided cloneType="{0}", is not matching with required clone type "{1}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22004: ApplyClonerInfo object should not be empty at this point.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22005: Either cloneType="{0}" or visible sourceid="{1}" or actual sourceid="{2}" is empty.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22006: As sourceMWHomeLoc and sourceOracleHomeLoc are empty, archive will not have any Middleware Home and Oracle Home.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22008: During apply cloner object(s) build, all the sourceid(s) in the archive are {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22009: Middleware Home and/or Oracle Home unarchive location and user visible sourceid map: "{0}"

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22010: The archive entry point in the jar is="{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22011: Execution of the command "{0}" started at "{1}" and it will take approximately 4 minutes.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22012: Time taken to execute the command "{0}"="{1}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22013: Adding Middleware Home jar {0} to final jar with archive entry point={1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22014: Restoring Middleware Home using command "{0}" started ...

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22015: Restoring Middleware Home using command "{0}" finished.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22016: The javahome from Middleware Home is "{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22017: No cloner object was found.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22018: Setting actual sourceid for all cloner objects.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22019: Adding all sourceid(s) to the jar file started ...

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22020: Adding all sourceid(s) to the jar file finished.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22025: The content of the sourceid file is {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22031: Was unable to determine top component name from Oracle Home "{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22032: Parent of Oracle Home {0} is not a valid Middleware Home.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22038: The java home found from Middleware Home is={0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22039: The Weblogic server home found from Middleware Home is={0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22040: The jar file path={0} is invalid.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22041: Path represented by "{0}" was not a directory.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22042: Path represented by "{0}" did not exist.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22043: Path is empty.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22044: Unable to create file "{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22045: Directory {0} was not empty.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22046: File object is empty.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22047: The specified path "{0}" is not a file.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22048: The file "{0}" is of zero size.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22049: The file "{0}" is not a directory.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22052: Target location {0} is empty.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22053: The jar output stream is empty.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22054: The exclude pattern of the files which will not be included in archive={0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22055: Generating exclude file pattern list, if any pattern is provided.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22057: Generating list of files to be included.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22058: The statistics of the files are: Total number of files={0}. Non-readable files={1}. symbolic link files={2}. Exclude pattern={3}. Exclude pattern actual={4}. Included files only={5}. Included empty folders only={6}. Nonempty folders={7}. Invalid absolute path whose canonical path does not exist={8}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22059: Number of entries (each file and folder) that will be included in the archive is={0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22060: Number of entries whose permission could be handled in permission file={0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22061: The archive entry point={0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22062: Counter={0}, and excluded file through file pattern is {1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22063: The time taken for unarchiving the entry from main jar={0} milliseconds.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22064: Either jar file path or entryNameToBeExtracted or target location is empty.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22065: The statistics of files whose permission will be handled:

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22066: The number of files with root privilege={0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22067: The number of symbolic link files={0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22068: The number of files whose permissions are written to permission file={0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22069: The root privilege files are:

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22070: Unable to set permission of the following files.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22071: File permission is invalid where visible permission is={0} and its calculated permission is={1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22072: Permission file {0} was already existing, so it will be deleted.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22073: The command "ls -alR" is executed properly, and temporary file was {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22074: The command "ls -alR" is not executed properly, and temporary file was {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22075: Unable to generate document object from the xml file {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22076: The domainHost={0}, domainPort={1}, domainAdminUserName={2}, domainAdminPassword={3}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22077: The Weblogic home "{0}" was invalid.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22078: The Weblogic jar "{0}" was invalid.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22079: The Middleware Home "{0}" was invalid.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22080: The Middleware Home "{0}" was either dummy or invalid as the file {1} was invalid.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22085: No parameter(s) should be empty.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22088: The jmx_connector is valid.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22089: Connection obtained successfully.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22090: Unable to get server connection.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22091: Either instanceHomeLocation or componentName or both are empty.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22092: The name and location of asinstances registered with the domain are={0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22093: The componentType is empty.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22094: Under instance home {0}, the components present are {1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22095: The instanceHomeLocation {0} was not valid.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22096: The search string is empty.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22097: The instance.properties file {0} is invalid.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22098: While finding componentType for a componentName, all components found are: {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22099: Either componentName or componentType or instanceHomeLocation is empty.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22100: The specified parameters for component copyConfig are: componentName={0}, componentType {1}, instanceHomeLocation={2} and instanceName={3}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22110: As instanceHomeLoc is existing, and user has not provided instance name, so setting instance name to {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22112: As instanceHomeLoc is existing, and user has not provided Oracle Home, so setting Oracle Home to {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22117: Any one parameter from domainHost,domainPort,domainAdminUserName was not provided.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22118: The domain parameters are: domainHost={0}, domainPort={1}, domainAdminUserName={2}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22119: Setting domain detail as domainHost={0}, domainPort={1}, domainAdminUserName={2} found from instance home.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22125: The domain password was empty.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22140: Parameter validation is complete. Sourceid is set to : "{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22141: Parameter validation is complete. TargetLocation is set to : "{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22142: Parameter validation is complete. Sourceid map is set to : "{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22143: Parameter validation is complete. User visible sourceid is set to : "{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22144: Parameter validation is complete. Setting exclude Oracle Home to "{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22145: Unable to decide restore choice for default sourceid.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22146: In the archive, number of Middleware Home(s)={0} and number of Oracle Home(s)={1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22147: For sourceid {0}, the restore location {0} was either empty or already used by other sourceid. So existing restore location and sourceid map is={2}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22149: No of sourceid(s)="{0}" and correspond targetlocation(s)="{1}" are not same, but it should be same.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22152: path_upto_Scripts="{0}", path_upto_oui="{1}", libDir_for_oui="{2}", platform_for_prereq="{3}", oui_lib_dir="{4}", sPrereqDir="{5}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22153: Before setting system environment property, prereq_bootstrap_dir="{0}", bootstrap_dir="{1}", prereq_config_loc="{2}", prereq_log_dir="{3}", oracle_install_scratch_path="{4}", oracle_install_lib_loc="{5}", oracle_install_engine_mode="{6}", java_lib_path="{7}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22154: To run prerequisites, oui lib directory is "{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22155: After setting system environment property the environment values are: prereq_bootstrap_dir="{0}", bootstrap_dir="{1}", prereq_config_loc="{2}", prereq_log_dir="{3}", oracle_install_scratch_path="{4}", oracle_install_lib_loc="{5}", oracle_install_engine_mode="{6}", java_lib_path="{7}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22156: To run prerequisites, platform_directory under Scripts/prereq/ is "{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22157: Operating system name="{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22158: No jar will be added to system class loader as jarlist is empty.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22159: Checking whether the following classes are already available in classpath or not. {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22160: Status of the availability of all above classes in classpath is "{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22161: The following jars will be added to System class loader. {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22162: All jars added to System class loader successfully.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22163: All jars added to System class loader failed.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22164: After loading jars to classpath, checking whether the following classes are available or not {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22165: Adding engine jars to system classloader from Oracle Home {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22166: Status of adding engine jars to system classloader from Oracle Home {0} is="{1}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22167: Adding oui jars to system classloader from Oracle Home {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22168: Status of adding oui jars to system classloader from Oracle Home {0} is="{1}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22169: Adding both engine and oui jars to system classloader.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22170: Status of adding both engine and oui jars to system classloader is="{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22171: Adding oui jars from Oracle Home {0} to system class loader to know Oracle Home details.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22172: Trying to retrieve the top component name from Oracle Home {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22173: Trying to validate Oracle Home {0} by validating its top component name and version.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22174: Extracting prerequisites jars under {0} location.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22175: Invoking engine prerequisites launcher.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22176: Status of parsing command-line argument="{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22177: Status of first validation of command-line argument="{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22178: Status of second validation of command-line argument="{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22179: Extracting Middleware Home jar file from main jar under {0} location.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22180: Extracting Middleware Home jar {0} to the target location {1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22181: Before executing restore script, either javapath {0} or jrepath {1} did not exist.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22183: Invalid entry for inventory_loc in inventory pointer file, and entry was {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22184: List of all valid symbolic link files is as follows.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22185: In file description "{0}", the first character is not "l", but has String "->"; assume it is symbolic link file.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22186: Invoking runConfigure for Oracle Home {0} with invPtrLoc "{1}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22188: Adding jars from {0} to system class loader.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22189: Status of adding jars from {0} to system class loader is "{1}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22190: Taking backup of oraparam.ini where source path was {0} and new path was {1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22191: Restoring oraparam.ini where source path was {0} and new path was {1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22192: To update "JRE_LOCATION", Java home found from Middleware Home {0} is {1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22193: Updating file {0} where key={1} and value={2}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22194: Status of updating file {0} where key={1} and value={2}, is {3}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22195: All inputs from command-line are: {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22197: Middleware Home install location is:{0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22198: Number of files from jar file entries for permission carrying: {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22199: List of all symbolic link files is as follows.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22200: Setting invPtrLoc with InventoryManager with user input value {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22201: The oracle.installer.invPtrLoc after running prerequisites={0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22204: OraInstaller library path={0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22205: The oracle.installer.invPtrLoc before running runConfigure={0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22206: Size of the home {0}={1} byte or "{2}" MB.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22207: For location {0}, free space required="{1}" MB, and the available free usable space="{2}" MB.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22208: Required space is available for copyConfig operation.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22209: Number of entries in the file, which will contain all valid symbolic link files detail={0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22210: Number of entries in the file, which will contain all file paths={0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22211: Validating existence of symbolic link file by checking absolute path and canonical path.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22212: The command "{0}" is not executed properly, and temporary file was {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22215: Oracle Home {0} is valid as its top component name {1} and version {2} are valid.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22216: Source Oracle Home location was={0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22217: {0}, file "{1}" is missing.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22218: During file existence check, number of files present={0} and number of file absent={1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22224: For sourceid="{0}", the target location="{1}", and space required="{2}" MB.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22233: For Oracle Home {0}, the name found from the inventory is={1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22234: Removing Oracle Home entry from shortcut list where folder Name="{0}" and item Name="{1}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22235: Source Oracle Home folder name in shortcut was="{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22236: Modified Oracle Home folder name pattern is="{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22238: Rename status of source file {0} to target file {1} is {2}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22239: Delete status for file {0} is {1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22240: Before updating file, sourcefile="{0}", old value="{1}", new value="{2}" and temporary file="{3}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22241: Trying to overwrite the content of source file "{0}" into the target file "{1}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22242: All the Oracle Home location and corresponding name present in the inventory {0} is as follows: {1}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22243: Restoring oraparam.ini where source path was {0} and new path was {1} status is={2}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22244: Directory "{0}" was empty.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22245: Prereq execution result as follows: AllPrereqChecksCount ="{0}", prereqSuccessCount ="{1}", prereqFailedCount ="{2}", WarningsCount ="{3}", UserVerifyCount ="{4}", List of All Checks ="{5}", List of checks passed ="{6}", List of checks failed ="{7}", List of Warning checks ="{8}", List of checks to verify="{9}", List of checks to Retry ="{10}", Prereq Summery ="{11}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22247: Number of files with "no read access permission"={0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22248: The file "{0}" was non-readable in the source Oracle Home, and now it is available in the cloned Oracle Home.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22249: ERROR, for the symbolic link path "{0}", the required canonical file {1} is not present.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22250: ERROR, the symbolic link path "{0}", did not exist.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22251: ERROR, for the symbolic link path "{0}", the absolute path {1} and canonical path {2} are same, which is incorrect.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22252: ERROR, for the symbolic link path "{0}", the canonical path {1} and required canonical path {2} are different, but should be same.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22253: Counter={0}, absolute path="{1}" and required canonical path="{2}"

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22254: The input from the user was="{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22256: Source jdk or jrockit home path {0} was not started with source Middleware Home path {1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22257: Unable to set the permission of the file {0} to {1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22260: Executing following command: {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22261: The final sourceid(s) "{0}" and their corresponding targetlocation(s) "{1}" will be taken care.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22262: Primary validation prior to clone operation is successful for {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22263: Restoring for the sourceid "{0}" started at {1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22264: Time taken to restore sourceid "{0}" is "{1}" milliseconds.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22265: Adding cloningclient.jar to Archive.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22266: "StartupMode" is not set in move plan. Assuming PRODUCTION Mode.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22267: Extracted MDS metadata to {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22268: No MDS data found in archive. Skipping metadata import.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22269: Adapter deployment plan location is {0}. Make sure that configurable parameters specified in {1} deployment plan are correct.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22270: Commented OPSS_SECURITY "configGroup".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22271: OPSS_SECURITY "configGroup" commenting failed.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22272: Could not copy modified move plan with commented OPSS_SECURITY "configGroup" .

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22273: Listen Address of {0} Managed Server is {1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22274: Setting Listen Address of {0} to localhost to start it locally.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22275: Setting Listen Address of {0} to {1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22276: Checking whether Oracle Home {0} can be archived or not.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22277: Removing frond end url setting for {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22278: Setting frond end url setting for {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22279: Failed to remove frontend host and port settings for {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22280: Failed to set frontend host and port settings for {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22281: {0} start failed. Checked managed server logs for details.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22282: {0} start failed due to time out. Try again.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22283: Application deployment plan location is {0}. Make sure that configurable parameters specified in {1} deployment plan are correct.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22284: Adding Default Authenticator data to archive.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22285: Adding Node Manager files to archive.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22286: Derived WebLogic Server home to be {0} and Java Home to be {1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22287: Loading Jar {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22288: Move Plan has no Node Manager movable component.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22289: Number of Node Manager Movable Components is {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22290: Mismatch in number of Movable Components of node manager from derived and visible.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22291: Deriving node manager properties of {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22292: Retargeting owsm application and data sources.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22293: Detected CommonDomain. Exporting Fusion Apps Global Partition MDS docs..

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22294: Not detected as CommonDomain. Fusion Apps Global Partition MDS docs will not be exported..

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22295: Detected CommonDomain. Exporting ESS Global Partition MDS docs..

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22296: Not detected as CommonDomain. ESS Global Partition MDS docs will not be exported..

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22297: Detected CommonDomain. Exporting ESS Internal Partition MDS docs..

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22298: Not detected as CommonDomain. ESS Internal Partition MDS docs will not be exported..

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22299: Export location for embedded LDAP data = {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-23001: Archive location

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23002: Inventory location

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23003: Flag to ignore free space check. Default value is false.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23005: Existing log directory location

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23006: Source instance home location

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23007: Source component name

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23008: Options(alias)

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23009: To create archive

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23010: Absolute path of archive location.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23011: Path should not exist and should have right privilege to create the file.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23013: Absolute path of Middleware Home location.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23014: Absolute path of inventory pointer (oraInst.loc file ) location to discover Oracle Homes present under the Middleware Home. This flag is supported in UNIX platforms only.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23020: Absolute path of a directory location with right privilege to create cloning log and error file. Default location is system temporary location.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23021: Flag to run the T2P operation in a non-interactive mode. Default value is false.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23022: Parameters for copyConfig of a component

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23023: Name of the existing component which will be archived.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23024: Absolute path of an existing instance which contains the component.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23025: Description:

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23027: Example:

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23028: Assumption:

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23029: Middleware Home

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23030: Oracle Home

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23031: Oracle inventory pointer location

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23032: Instance home location

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23033: Component name

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23034: To create an archive of a Middleware Home.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23035: This archive will contain the Middleware Home and all the Oracle Home(s) under it, that is the archive will have

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23036: No Oracle Home is installed under this Middleware Home

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23037: This archive will contain only the Middleware Home as no Oracle Home is installed under it, that is the archive will have only

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23042: To create archive of oid1

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23043: To create archive of ovd1

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23044: Requirement

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23045: The movement scripts require a minimum of Java version of 1.6. However, for the exact JRE version certified for the product, please refer to the System Requirements and Supported Platforms document, which is located at http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23046: NOTE:

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23047: The parameter {0} will accept only one Middleware Home.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23050: The parameter {0} can be accompanied with the {1} parameter only.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23055: CopyBinary of Middleware Home, Oracle Home and component at same time is not possible.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23057: In Windows, before creating archive of Middleware Home, make sure that no java or Weblogic processes are running from that Middleware Home.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23059: Copyright (c) 2004, 2013, Oracle and/or its affiliates. All rights reserved.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23060: Before creating archive of Middleware Home, make sure that the Weblogic product directories(like Weblogic server, coherence) are installed inside that Middleware Home.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23061: If Operating System is {0}, then provide {1} as argument to Java.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23062: The target Middleware Home location cannot be inside another Middleware Home.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23063: <Component specific>

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23064: Source Middleware Home location

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23101: Absolute path of target location.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23102: Extra session variables for OUI runInstaller.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23103: Java home path.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23104: Absolute path of inventory pointer location.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23105: New name for the component to be restored.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23106: Absolute path of instance home under which component will be restored.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23107: Name of the instance under which component will be restored.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23108: Absolute path of Oracle Home associated with instance home.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23109: Extra session variables to OUI runInstaller can be passed as key=value pairs. Multiple session variables can be passed as comma separated pairs.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23110: To restore from archive

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23111: Absolute path of the archive location. Make sure that the location exists.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23112: detail

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23113: Absolute path to restore Middleware Home. This absolute path can be either a non-existing or an existing empty directory.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23114: Flag to execute system prerequisites before restoring the Oracle Home(s). Default value is true.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23115: Absolute path of inventory pointer (oraInst.loc file ) location to register Oracle Homes with the central inventory. This flag is supported in UNIX platforms only.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23117: Java home to configure Middleware Home in the case when the archived Middleware Home does not contain a JDK or JRockit.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23118: New name for the component to be restored

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23119: Absolute path of instance home under which component will be restored. If instance does not exist, path can be either a non existing or an existing empty directory.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23120: Name of the instance under which component will be restored

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23121: Absolute path of the Oracle Home that will be used to configure the component.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23122: Absolute path of instance home under which component will be restored. Path can be either a non-existing or an existing empty directory.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23123: Domain host name

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23124: Domain port number

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23125: Domain Admin user name

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23126: Domain Admin password file

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23127: Database host name

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23128: Database listener port

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23129: Database service name

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23130: ODS schema password file

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23131: ODSSM schema password file

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23132: Namespace

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23133: OID admin password file

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23134: OID non SSL port

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23135: OID SSL port

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23140: OVD admin port

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23141: OVD http port for default listener

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23142: OVD ldap non ssl port default listener

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23143: OVD ldap ssl port default listener

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23144: To restore the full archive. To know the entities present in the archive, Execute "{0}" command.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23145: Middleware Home, Oracle Home pasteBinary

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23146: Archive has Weblogic binary and one or more Oracle Home. Restore full archive

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23147: Command:

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23148: Archive has one Middleware Home and two Oracle Homes(let {0} and {1})

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23149: Here {0} need to be either a non existing or an existing empty directory. {1} and {2} will be restored under {0}. Oracle Home folder name cannot be changed

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23150: Archive will be restored as follows: {0} {1} {2}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23151: Absolute path of the Oracle Home that will be used to configure the instance home.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23161: Archive has only one Middleware Home but no Oracle Home. Restore full archive

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23162: Here {0} need to be either a non existing or an existing empty directory.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23168: 1. All the entities present in the archive will be restored during pasteBinary operation. 2. When Oracle Home(s) is restored, make sure that the Oracle inventory has no entry for that target Oracle Home. 3. If targetInstanceHomeLoc exists, then targetInstanceName and targetOracleHomeLoc are optional. 4. If targetInstanceHomeLoc is already registered with domain, then domainHostName, domainPortNum and domainAdminUserName are optional.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23169: OID Specific NOTE: 1.If source and target database are different (if either host or port or service name is different) a) Then source oid and target oid name should be the same. b) Target database should have footprint of source OID Component. 2.If source and target database are same. a) Then source oid and target oid name should be different.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23201: List contents of an archive.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23202: List content of archive, that is, list all the entities present in the archive.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23203: Output:

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23204: Usage: <path to java> {0} <path to cloningclient.jar> <command> <command>:=<Clone command> <Clone command>:= | {1} | {2} | {3} For help on a particular command, use [ <path to java> {0} <path to cloningclient.jar> {4} <command>]

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23205: Usecase-{0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23206: <path to java> {0} <path to cloningclient.jar>

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23207: is inside

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23209: Middleware Home archive # {0}, home location={1}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23210: Oracle home archive # {0}, home location={1}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23211: For Component, if instance name is {0}, and component name is {1}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23212: Component archive # {0}, instance name@component name={1}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23213: Oracle Home path

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23214: Domain location

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23215: Absolute path of the source Oracle Home.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23216: Absolute path of the source Domain.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23217: Parameters for copyConfig of J2EE component.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23218: Absolute path of the Target domain.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23220: <J2EE Component specific>

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23221: To create archive of a soa domain

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23222: To restore an OID component

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23223: To restore an OVD component

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23224: To restore a SOA domain

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23225: Absolute path of the Target Oracle Home.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23226: Oracle Process Manager ({0})

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23230: Absolute location of java home

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23235: To create archive of a Middleware Home (and all valid Oracle Home(s) under it).

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23240: To restore the full archive containing Middleware Home.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23245: 1. All the entities present in the archive will be restored during paste binary operation. 2. When Oracle Home(s) is restored, make sure that the Oracle inventory has no entry for that target Oracle Home.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23250: To create the archive of an Oracle system component or a WebLogic J2EE Domain or a Node Manager.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23255: To restore the full archive containing an Oracle system component or a WebLogic J2EE Domain or a Node Manager.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23260: 1. If targetInstanceHomeLoc exists, then targetInstanceName and targetOracleHomeLoc are optional. 2. If targetInstanceHomeLoc is already registered with domain, then domainHostName, domainPortNum and domainAdminUserName are optional.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23265: Use the "-help" option for more information about cloning options and arguments.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23267: Pack Domain - {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23268: Adding Packed Domain to archive

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23269: Error in examining J2EE Domain. Check the logs for more details

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23270: Connecting to domain runtime...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23271: Trying to connect to {0}:{1}...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23272: Successfully connected to the Domain Runtime ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23273: Examining Servers.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23274: Examining Machines.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23275: Examining Clusters.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23276: Examining Datasources.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23277: Examining Security Policy.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23278: Examining all J2EE plugin implementations.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23279: Credential and Policy Store is LDAP type.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23280: Credential and Policy Store is File based.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23281: Extract the packed domain from archive to temp location.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

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

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23283: Unpack Domain.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23284: Starting AdminServer and pasting security policy configuration changes...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23285: Find all J2EE plugin PasteConfig implementations and apply the configuration.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23286: Pasting security policy configuration changes....

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23287: Paste Server Configuration.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23288: Paste Cluster Configuration.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23289: Paste DataSource Configuration.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23290: Paste Machine Configuration.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23291: Paste Security Policy Configuration.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23292: Examining Adapters.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23293: Examining Resource Adapters. The Resource Adapters with deployment plan will be added to move plan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

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

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23295: Warning: Found invalid attribute in Adapter "ConfigGroup". Valid Attributes are "Name" and "Deployment Plan".

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23296: Paste Adapter Configuration.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23297: Warning: Neither LDAP nor DB details are specified in move plan for the OPSS Security Store. Default Store will be used at the target.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23298: Re-associate security store with provided LDAP : {0}, {1}, {2}, {3}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23299: Migrating Policy and Credential store.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23300: Configplans have been extracted at "{0}".

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23301: ExtractMovePlan operation completed successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23302: Serialize and write bean to a temp file, then add that temp file to jar.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23303: Write archive file list to a temp file , then add that temp file to jar.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23304: ****************** PACK ******************

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23305: Details for Packing Domain...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23306: Oracle Home Source Location: {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23307: Source Domain Location: {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23308: Packed jar Location: {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23309: Command to execute for pack: {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23311: SEVERE: Specified adapter deployment plan {0} is not a valid file. Using the default plan from archive.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23312: Examining LDAP Authenticators.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23313: Paste LDAP Authenticator Configuration

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23314: Exporting metadata of applications. Make sure that all managed servers in the specified domain are started.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23315: Importing metadata of applications.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23316: Starting {0} to import MDS data.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23317: Importing metadata of application {0} from archive.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23318: Absolute path to directory where moveplan is to be extracted

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23319: Exporting metadata may take several minutes. Check the logs for monitoring the progress....

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23320: Absolute path to a non-existing directory where the t2p move plan will be extracted along with other J2EE Configuration Plans.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23321: To extract t2p move plan along with other J2EE Configuration Plans.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23322: Note: The t2p moveplan or multi archive moveplan contains the endpoint configuration for J2EE and System Component configuration. For details on how to modify the t2p moveplan or multi archive moveplan, refer to the Chapter "Cloning Oracle Fusion Middleware" of Fusion Middleware Guide

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23323: Source WebLogic Domain location

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23324: Middleware Home location

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23325: Source Domain Admin Server Host Name

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23326: Source Domain Admin Server Port

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23327: Source Domain Admin Server User Name

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23328: Source Domain Admin Server User Password File location

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23329: Absolute path of Source J2EE Domain.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23330: Absolute path of Middleware Home location.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23331: Source Domain Admin Server Host Name.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23332: Source Domain Admin Server Port.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23333: Source Domain Admin Server User Name.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23334: Absolute Path to the file containing Domain Admin Server User Password.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23335: To create archive of ohs1

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23336: To create archive of WebLogic J2EE domain

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23337: Absolute path of target J2EE Domain. Path can be either a non existing or an existing empty directory.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23338: Absolute path of existing target Middleware Home location.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23339: Absolute path to the T2P Move Plan xml document extracted during extract plan operation. Refer to the Chapter "Cloning Oracle Fusion Middleware" of Fusion Middleware Guide for more details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23340: Target WebLogic Domain location

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23341: Target Middleware Home location

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23342: Absolute path to the T2P Move Plan

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23343: Oracle System component specific parameters

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23344: WebLogic J2EE domain specific parameters

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23345: WebLogic domain location

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23346: Source Middleware Home

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23347: Domain Admin Server Host Name where the system component will be registered

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23348: Domain Admin Server Port

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23349: Domain Admin Server User Name

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23350: Domain Admin Server User Password File location

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23351: MDS data export flag is set to false. Skipping MDS configurations.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23352: [Deprecated - As of release 11.1.1.7.0, replaced by "-mdsDataExport|-mde"] Flag to execute MDS export/import. Default value is true.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23353: Error in validating "pasteConfig" parameters.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23354: Target WebLogic Application Directory

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23355: Absolute path of target J2EE domain application directory. Path can be either a non existing or an existing empty directory.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23356: Error in validating "SERVER_CONFIG" parameters in "moveplan".

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23357: {0} is already running on port {1}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23358: Stopping all managed servers.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23359: Credential and Policy Store is database based.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23360: Values for re-associating and migrating "OPSS_SECURITY" are not provided. Assuming File store for OPSS.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23361: Re-associate security store to database : {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23362: Examining RDBMS Security Store.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23363: Paste RDBMS Security Store Configuration

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23364: Archive(s) location

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23365: Absolute path to directory where moveplan is to be extracted

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23366: Absolute path of the archive(s) location. Make sure that the location(s) exist(s). If multiple archives are provided, provide them as a comma separated list. (In Windows, provide the comma separated list within double quotes)

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23367: Absolute path of either a non existing or an existing empty directory where the moveplan and/or multi archive moveplan will be extracted along with other J2EE Configuration Plans.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23368: To extract moveplan or multi archive moveplan along with other J2EE configuration plans.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23369: Exporting OWSM policies...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23370: OWSM policies are not exported during "copyConfig". OWSM policies will not be migrated.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23371: Error in importing OWSM policies to target domain.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23372: Adding OWSM policies to archive.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23373: Importing OWSM policies...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23374: Examining applications with custom deployment plans.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23375: Examining applications with custom deployment plans. The applications with a deployment plan will be added to the move plan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

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

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23377: Pasting application deployment plan configuration.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23378: Warning: Found invalid attribute in DEPLOYMENT_PLAN_CONFIG "ConfigGroup". Valid attributes are "Application Name" and "Deployment Plan".

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23379: SEVERE: Specified application deployment plan {0} is not a valid file. Using the default plan from archive.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23380: Exporting Default Authenticator data.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23381: Importing Default Authenticator data.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23382: MDS export of some applications failed. Check the logs for details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23383: MDS import of some applications deployed on {0} failed. Check the logs for details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23384: Stopping {0}...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23385: Flag for optimization while creating multi archive moveplan

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23386: Provide the flags as a comma separated list. (In Windows, provide the comma separated list within double quotes) The supported values are :{0} Based on flag, specific optimization of multi archive moveplan will take place. Flag description: fusionapps (fa) : You need to provide this hint always. This simplifies the move plan for Oracle Fusion Applications. sameSchemaNameSinglePassword (ssnsp) : The same password is used for all schemas associated with a particular database specified in DATASOURCE section of the moveplan. However, the passwords for APPID users are different. You are prompted to provide the password only once for each database. Therefore, you need to pass a separate password for each of the APPID users. rpdDataSource (rpdds) : The same password is used for all schemas associated with a particular database specified in RPD_CONFIG section of the moveplan. If ssnsp flag is provided, then automatically this flag will be set to true.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23387: Oracle ASInstance specific parameters

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23388: To create archive of asinstance

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23389: Flag to execute OPSS data export/import. Default value is true.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23500: Error while archiving Node Manager. Check log for more details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23501: Unable to create the directory {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23502: Unarchiving Node Manager files at location {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23503: Target Middleware Home location is either null or an empty string.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23504: Unable to derive target WebLogic Server Home from the Middleware Home.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23505: Unable to derive Java Home from the target Middleware Home .

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23506: The file {0} does not exist.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23507: Updating file {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23508: Examining each domain to enroll Node Manager.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23509: Unable to retrieve properties of the domain from Move Plan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23510: Domain Name is either null or an empty string in the Move Plan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23511: Domain Location is either null or an empty string in the Move Plan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23512: Incorrect format of AdminServer Listen Port for domain {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23513: Checking if the AdminServer for domain {0} is up...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23514: Could not connect to AdminServer for domain {0}. Make sure values provided are correct in moveplan. If "AdminServer Listen Port" is SSL port, provide value of "Custom Trust KeyStore File" of the domain if domain keystore type is Custom Trust.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23515: Enrolling NodeManager with domain {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23516: Successfully enrolled NodeManager with domain {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23517: WebLogic Server Home value is either null or empty string.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23518: Starting Node Manager from location {0}...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23519: Node Manager ListenPort mentioned in nodemanager.properties is not valid.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23520: Checking if port {0} is available for Node Manager...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23521: Port is available.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23522: -targetNMHomeLoc is either null or an empty string.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23523: Node Manager specific parameters

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23524: Source nodemanager home location

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23525: Absolute path of Source Node Manager home.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23526: To create archive of Node Manager

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23527: Target Node Manager Home location

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23528: Absolute path of target Node Manager home location. Path can be either a non existing or an existing empty directory.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23529: Additional parameters required for product specific operations. The additional parameters should be passed as key=value pairs. Multiple parameters may be passed by separating each key=value pair by a comma. i.e key1=value1,key2=value2,key3=value3

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23530: Re-associating security store...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23531: Flag to execute MDS export/import. Default value is true.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23532: Custom Trust KeyStore File location

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23533: Absolute path of Custom Trust KeyStore File location. Specify this property to specify the "CustomKeyStore" if SSL port is specified for AdminServer.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23534: The move plan - {0} was not extracted using the archive - {1}. Please extract the move plan once again using the archive - {1} and re-run the script.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23535: Warning: Starting of {0} is taking longer than expected. Check the server logs to make sure {1} start is in progress.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23536: Warning: Stopping of {0} is taking longer than expected. Check the server logs to make sure {1} shutdown is in progress.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23537: [Deprecated - As of release 11.1.1.7.0, replaced by"-domainAdminPasswordFile"]

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23538: Warning: Valid values are not provided for Custom Identity KeyStore configuration. Source configuration will be retained in the target.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24005: OVD cloning has failed.

Cause: OVD component pasteConfig parameter validation failed.

Action: Check the clone log file for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-24006: OVD cloning has failed.

Cause: JPS file of the source OVD component is not available.

Action: Check the clone log file for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-24007: OVD cloning has failed.

Cause: OVD creation failed.

Action: Check the clone log file for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-24009: OVD cloning has failed.

Cause: Ports were not updated successfully.

Action: Check the clone log file for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-24010: Port validation has failed.

Cause: Unable to assign port for {0}.

Action: Make sure that some ports are free.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-24011: Oracle Home does not have supported binaries.

Cause: An attempt was made to use an incompatible top component based Oracle Home.

Action: Provide a valid Oracle Home.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-24012: Oracle Home does not have supported binaries.

Cause: An attempt was made to use an incompatible component based Oracle Home.

Action: Provide a valid Oracle Home.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-24301: Source OVD component listeners were configured with following details. {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24302: Listener {0} will be configured with port {1}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24303: Updating configuration files.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24304: Updating configuration files completed.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24307: Validating OVD Admin port.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24308: Validating OVD LDAP port.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24309: Validating OVD LDAP SSL port.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24310: Validating OVD HTTP port.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24312: Creating OVD component.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24313: OVD component created successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24314: Stopping OVD component.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24315: OVD component stopped successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24316: Password file is either not provided or invalid for the adapter "{0}". Nothing will be changed for this adapter configuration.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24317: Null parameter(s) found during OVD parameters validation.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24318: Starting OVD component.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24319: OVD component started successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24320: Updating OVD component registration with admin server started...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24321: OVD component registration with admin server completed successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24322: Exporting OVD component server certificate into EMAGENT started...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24323: Exporting OVD component server certificate into EMAGENT completed successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24324: Restarting EMAGENT...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24325: EMAGENT restarted successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24326: Updating OVD certificate during cloning started...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24327: Updating OVD certificate during cloning completed successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24328: Stopping Oracle instance {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24329: Starting Oracle instance {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24330: Collecting OVD adapter information, if any ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24331: Performing OVD adapter parameter validation ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24332: Updating OVD adapters ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24333: Setting OVD server certificate in EMAGENT started ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-24601: Before updating listener_os.xml file {0}, the listener port details are : {1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-24602: Updating listeners_os.xml file {0}...

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-24603: Updating listeners_os.xml file is finished.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-24604: Updating ovd-logging.xml file {0}...

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-24605: Updating ovd-logging.xml file is finished.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-24606: Building OracleASComponent object for OVD Component.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-24607: OracleASComponent object for OVD Component is built successfully.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-24608: Building OracleASComponentProperties object for OVD Component.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-24609: OracleASComponentProperties object for OVD Component is built successfully.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-24612: Source OVD component port information : {0} and instance information : {1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-24613: Source OVD component version information : {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-24614: Nothing to do in doPostCreateClone for OVD component during copyConfig operation.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-24615: All ports detailed information from xml file {0} is : {1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-24616: OVD parameters for pasteConfig : {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-24617: The {0} component version : {1}, but it should be within {2} and {3}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-24618: The {0} component passed the version verification.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-25001: Invalid component name.

Cause: Because source and target database are different, then target OID component name {0} should be the same as source OID component name {1}.

Action: Provide same component name as that of source OID component name.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-25002: Invalid Oracle directory server schema password.

Cause: Oracle directory server schema password was empty.

Action: Provide a valid Oracle directory server schema password.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-25003: Invalid ODSSM schema password.

Cause: Schema password for ODSSM was empty.

Action: Provide valid ODSSM schema password.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-25004: Invalid Oracle Internet Directory admin password.

Cause: Oracle Internet Directory admin password was empty.

Action: Provide valid Oracle Internet Directory admin password.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-25005: Database parameters validation has failed.

Cause: Either database host, port, or service name was incorrect.

Action: Provide correct database host, port, and service name.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-25006: Oracle directory server schema validation has failed.

Cause: Either database connection string or Oracle directory server schema username or password was not correct.

Action: Provide correct database connection string and Oracle directory server schema username or password.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-25007: Schema validation for ODSSM has failed.

Cause: Either database connection string or ODSSM schema username or password was not correct.

Action: Provide correct database connection string and ODSSM schema username and password.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-25008: Namespace value is missing.

Cause: The namespace value was empty.

Action: Provide namespace value.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-25009: OID cloning has failed.

Cause: Wallet file of the source OID component is not available.

Action: Check the clone log file for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-25010: Database connection has failed.

Cause: Either host name, port number, SID, Service Name, schema user, or schema password was empty.

Action: Make sure that all the parameters are valid.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-25012: Invalid OID instance name.

Cause: An OID instance is already running with the same name.

Action: Provide different database details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-25013: Invalid database.

Cause: The postStart is not performed in the database.

Action: Make sure that the database is already configured with an OID.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-25014: Invalid target component name for OID.

Cause: Database is already configured with the name, "{0}".

Action: Provide different name.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-25015: Invalid target component name for OID.

Cause: During T2P scenario, database must contain the same OID entry, i.e. "{0}".

Action: Make sure that the database already has source information.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-25016: Oracle directory server schema password missing.

Cause: An attempt was made to clone OID component in silent mode without providing valid ODS schema password.

Action: Provide ODS schema password in a secured file.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-25017: ODSSM schema password missing.

Cause: An attempt was made to clone OID component in silent mode without providing a valid ODSSM schema password.

Action: Provide ODSSM schema password in a secured file.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-25018: OID admin password missing.

Cause: An attempt was made to clone OID component in silent mode without providing valid OID admin password.

Action: Provide OID admin password in a secured file.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-25019: Oracle Home does not contain the supported binaries.

Cause: An attempt was made to use an incompatible top component based Oracle Home.

Action: Provide a valid Oracle Home.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-25020: Oracle Home does not contain the supported binaries.

Cause: An attempt was made to use an incompatible component based Oracle Home.

Action: Provide a valid Oracle Home.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-25301: Enter ODS schema password :

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25302: Enter ODSSM schema password :

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25303: Enter OID Admin password :

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25304: Database parameter(s) are empty.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25305: Database details from tnsfile is empty and provided database detail(s) are also empty.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25306: Database details from tnsfile is not empty but provided database detail(s) is empty.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25307: Database details from tnsfile and provided database details are different.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25308: Setting database details as follows: DB_HOST {0}, DB_PORT {1}, DB_SERVICE {2}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25309: Source OID was configured with following database details, database host {0}, database port {1}, database service name {2}. To use the same database, provide these values as argument.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25310: The postStart has already been performed in the database.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25312: Source OID component was configured with following details. non-SSL port {0}, SSL port {1}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25313: Validating Oracle Internet Directory ldapSSLPort.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25314: Validating Oracle Internet Directory nonSSLPort.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25315: Source OID {0} was associated with database host {1} and service name {2}, and port number {3}. An attempt is made to associate target OID with same database and service name. The target OID component name is the same as the source OID component name. So source OID will not work properly but target OID will work. If you provide a unique name (database should not be configured with this name) for target OID component, then other installed OIDs will work properly.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25316: Starting OID component...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25317: OID component started successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25318: Stopping OID component.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25319: OID component stopped successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25320: Null parameter(s) found during OID parameters validation.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25321: Creating OID component...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25322: OID component created successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25323: The port "{0}" is free for use.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25324: The port "{0}" is not free for use.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25325: The provided port "{0}" was either empty or not free, trying to use port "{1}".

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25326: Trying to get a new port between lower port {0} and higher port {1}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25327: Unable to calculate new port.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25328: New value for port is "{0}".

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25330: Database is already configured with following OID instance(s) {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25331: Post-create configuration for OID component started...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25332: Post-create configuration for OID component completed successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25333: ODS schema validation completed successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25334: ODSSM schema validation completed successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-25601: Source OID component port information : {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-25602: Source OID component version information : {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-25603: Nothing to do in doPostCreateClone for OID component during copyConfig operation.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-25604: OID parameters for pasteconfig : {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-25605: Building OracleASComponent object for OID component.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-25606: OracleASComponent object for OID component is built successfully.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-25607: Building OracleASComponentProperties object for OID component.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-25608: OracleASComponentProperties object for OID component it built successfully.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-25609: The {0} component version is : {1}, but it should be within {2} and {3}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-25610: The {0} component passed the version verification.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-26001: OHS T2P property file is invalid.

Cause: Either property file did not exist or had invalid inputs.

Action: Make sure that the property file {0} has a valid entry.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-26002: OHS cloning has failed.

Cause: OHS creation failed.

Action: Check the clone log file for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-26003: Error in validating listen host and port.

Cause: The causes were:{0}

Action: Make sure the listen host and port values provided are correct and the ports are free on the corresponding host.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-26004: Unable to obfuscate plsql database password.

Cause: An internal operation failed.

Action: Check the clone log file for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-26005: Unable to update and obfuscate oradav password.

Cause: An internal operation failed.

Action: Check the clone log file for more details and update and obfuscate oradav password.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-26007: Unable to update webgate configuration.

Cause: Update of webgate configuration details in webgate conf file failed.

Action: Check the clone log file for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-26008: Primary OAM server update has not happened.

Cause: Unable to calculate httpd.conf file path.

Action: Update primary OAM server details webgate configuration file.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-26009: OHS T2P failed.

Cause: Unable to start OS component.

Action: Check clone log and error file and ohs log file {0} for root cause.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-26101: Null parameter(s) are found during OHS parameters validation.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26102: Creating OHS component...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26103: OHS component created successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26104: Stopping OHS component...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26105: OHS component stopped successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26106: Capturing WebGate configuration, if any ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26107: Webgate install directory updated successfully in configuration files.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26108: Starting OHS component...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26109: OHS component started successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26110: Validating config properties of config group {0}...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26111: Config properties of config group {0} are validated and updated.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26113: Virtual port {0} is not in listen port list.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26114: Setting virtual port to {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26115: Virtual port is not in the new listen port list. Leaving this virtual host port as it is.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26116: Updating webgate specific configuration, if any ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26117: The port {0} is not free. Assigning new port {1}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26118: Archive of {0} files started, if any...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26119: Archive of {0} files finished.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26120: Restoring {0} files from the archive started ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26121: Restoring {0} files from the archive completed.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26122: Updating instance location, component name and Oracle Home ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26123: Instance location, component name and Oracle Home updated successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26124: Updating directive and container...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26125: Directive and container are updated successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26127: Trying to validate move plan and updating, if required...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26128: Updating all xml files under {0}...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26129: All xml files under {0} are updated successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26130: Updating all configuration files ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26131: All configuration files are updated successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26133: Configuration file {0} does not exist. Unable to run file fixer.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26134: In source environment, configuration file {0} was outside of the instance home. In target environment, trying to restore to same location.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26135: An attempt was made to restore configuration file at {0}, but this path already exists. So configuration file will not be restored again.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26136: Extracting configuration file under {0}...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26137: Configuration file {0} is restored successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26138: An attempt was made to restore {0} directive at {1}, but this path already exists. So directive will not be restored again.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26139: Extracting directive files under {0}...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26143: Obfuscating PLSQL database password, if exists.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26144: No configuration file carries PLSQL database password.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26145: Obfuscation of PLSQL database password did not happen.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26146: Configuration file {0} was not restored from the archive. Obfuscate will not be performed.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26147: Configuration file {0} does not exist. Obfuscate will not be performed.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26148: Updating password field in the configuration file {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26149: Unable to retrieve password for {0} from file {1}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26150: Unable to update password field in the configuration file {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26151: Password field is updated in the configuration file {0} successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26152: Obfuscating PLSQL database password...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26153: PLSQL database password obfuscated successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26154: Unable to obfuscate PLSQL database password.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26155: Restoring permission of configuration files...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26156: Permission of configuration files are restored successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26157: Unable to restore permission of configuration files.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26158: Unable to update password field in the configuration file {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26159: Validating move plan...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26160: From move plan, the name of the property is {0}, and its value is empty. Value cannot be empty.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26161: From move plan, the name of the property is {0}, and its value {1} is not a valid integer. It should be a valid integer.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26162: Updating oradav configuration file, if exists ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26163: Updating oradav configuration file ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26164: Obfuscating oradav password...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26165: Oradav password is obfuscated successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26166: Unable to obfuscate oradav password.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26167: Oradav configuration file is updated successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26168: Unable to update oradav configuration file.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26169: Updating webgate install directory, if present ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26170: Webgate install directory is updated successfully in configuration files.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26171: Validating config properties of config group {0}...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26172: Config properties of config group {0} are validated.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26301: Building OracleASComponent object for OHS component...

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-26302: OracleASComponent object is created successfully.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-26303: Building OracleASComponentProperties object for OHS component ...

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-26304: OracleASComponentProperties object is created successfully.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-26305: OHS parameters for pasteConfig operation are : {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-26306: Printing {0} move plan ...

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-26307: Updating configuration file {0} through file fixer ...

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-32000: No ADF Connection MBeans were detected in the source domain, and therefore no ADF Connection information will be included in the moveplan.xml.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

CLONE-32010: 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-32020: 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-32100: 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-32110: No ADF Domain Config MBeans were detected in the source domain, and therefore no ADF domain config information will be included in your move Plan.

Cause: ADF domain does not have ADF domain config MBeans.

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

Type: TRACE

Impact: Other

CLONE-32500: 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-33000: 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-33010: Start to run T2P ADF Connection Plugins.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

CLONE-33020: Finish running T2P ADF Connection Plugins.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

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

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

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

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

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

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

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

Cause: OBJECT_NAME_PROPERTY field for mbean object name might be changed accidently.

Action: Use the value of OBJECT_NAME_PROPERTY from other attributes under the same ADF Connection MBean in Move Plan to correct the wrong one.
Level: 1

Type: WARNING

Impact: Other

CLONE-33500: Successfully saved ADF Connection MBean attributes update for application {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

CLONE-33600: No ADF Connection MBean attributes changed for application {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

CLONE-33700: MBean attribute {0} old value {1} new value {2} changed? {3}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

CLONE-51000: Is SOA Domain = {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51001: Executing "Post-Copy Configuration" operation of the SOA plugin.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51002: Executing "copyConfig Validation" operation of the SOA plugin.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51003: Executing "Copy Configuration" operation of the SOA plugin.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51004: SOA Oracle Home Location is {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51005: Not valid SOA Domain. Skipping SOA-specific copy configuration steps.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51006: Exporting {0} composite to {1}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51007: Exporting Human WorkFlow Attribute Labels Info.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51008: Exporting Human WorkFlow TPFF Attributes.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51009: Exporting Human WorkFlow Approval Groups.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51010: Exporting Human WorkFlow Rules for Users.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51011: Exporting Human WorkFlow Rules for Groups.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51012: Exporting Human WorkFlow Views for Users.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51013: Exporting Human WorkFlow Standard Views.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51014: Exporting SOA Composites.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51015: No SOA Composite found in the specified domain. Composite details will not be added to the move plan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51016: Exporting B2B Channel Info.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51017: No B2B Channels found in the specified domain. B2B details will not be added to the move plan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51018: Adding B2B export file {0} to archive.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51019: Adding B2B Channel {0} to the move plan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51020: Adding Composite {0} to the move plan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51023: Exporting OWSM Policies...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51024: Executing "Post-Paste Configuration" operation of the SOA plugin.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51025: Executing "pasteConfig Validation" operation of the SOA plugin.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51026: Executing "Pre-Paste Configuration" operation of the SOA plugin.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51027: Executing "Paste Configuration" operation of the SOA plugin.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51028: Extracting soat2p folder from archive.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51029: Importing OWSM Policies to target domain.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51030: Error in importing OWSM Policies to target domain.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51031: Importing Human WorkFlow Migration XML to target domain.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51032: Importing Human WorkFlow Attribute Labels Info.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51033: Importing Human WorkFlow TPFF Attributes.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51034: Importing Human WorkFlow Approval Groups.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51035: Importing Human WorkFlow Rules for Users.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51036: Importing Human WorkFlow Rules for Groups.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51037: Importing Human WorkFlow Views for Users.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51038: Importing Human WorkFlow Standard Views.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51039: Importing B2B Delivery Channels to target domain.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51040: Importing SOA Composites to target domain.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51041: Composite information is not available in the move plan. No Composites will be deployed to the target domain.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51042: B2B Information is not available in the move plan. No B2B channel details will be applied to the target domain.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51044: SEVERE: Specified composite config plan {0} is not a valid file. Using the default composite from archive.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51045: Adding OWSM policies to archive.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51046: "dataImport" is set as false. Skipping SOA import configurations.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51047: "mdsDataExport" flag is set to false. Skipping MDS migration for B2B, Human WorkFlow and OWSM

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51048: OWSM Policies are not exported during "copyConfig". OWSM policies will not be migrated.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51049: Human WorkFlow MDS data is not exported during "copyConfig".Human WorkFlow data will not be migrated.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51050: B2B data is not exported during "copyConfig".B2B MDS data will not be migrated.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51051: Exporting BPM Organizations and Dashboard data.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51052: Importing BPM Organizations and Dashboard data.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51053: BPM data migration file is not present in archive, skipping BPM import.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51054: Is BPM Domain {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51055: Exporting BPM Organizations.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51056: Exporting Dashboard data of users.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51057: Importing BPM Organizations.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51058: Importing Dashboard data of users.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51059: BPM data not exported during "copyConfig".BPM data will not be migrated.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51060: Export of {0} composite failed.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51061: Exporting SOA configuration from MDS.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51062: MDS export for "soa-infra" application failed.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51063: Importing SOA configuration from MDS.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-51064: MDS import for "soa-infra" application failed.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-52000: "soa-infra" is targeted to AdminServer.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-52001: "OracleBPMWorkspace" is targeted to AdminServer.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-52002: Not valid BPM Domain. Skipping BPM specific copy configuration steps .

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-52003: Determining if SOA platform is available...

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-53000: Error in finding SOA Oracle Home.

Cause: Specified Middleware Home did not have a valid SOA Oracle Home. Skipping SOA-specific configurations.

Action: Make sure that a valid SOA Oracle Home is present in the specified Middleware Home
Level: 1

Type: ERROR

Impact: Cloning

CLONE-53001: Error in connecting to SOA Managed Server.

Cause: SOA Managed Server was down.

Action: Make sure that all managed servers in the specified domain are started.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-53002: Error in examining Composites.

Cause: Composite examination failed.

Action: Make sure that all the specified values are correct. Check managed server logs and clone logs for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-53003: Error in examining B2B.

Cause: B2B examination failed.

Action: Make sure that all the specified values are correct and domain configuration is valid. Check managed server logs and clone logs for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-53004: Error in examining Human WorkFlow.

Cause: Human WorkFlow examination failed.

Action: Make sure that all the specified values are correct and domain configuration is valid. Check managed server logs and clone logs for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-53005: Error in examining OWSM Policies.

Cause: OWSM Policy examination failed.

Action: Make sure that all the specified values are correct and domain configuration is valid. Check managed server logs and clone logs for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-53007: Error in generating composite config plans.

Cause: Composite examination failed.

Action: Make sure that all the specified values are correct and domain configuration is valid.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-53008: Error in importing Human Workflow migration data.

Cause: Human WorkFlow migration failed.

Action: Make sure that all the specified values in the move plan are correct and the archive is valid.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-53009: Error in parsing move plan.

Cause: Specified move plan was not valid.

Action: Make sure that all the specified values in the move plan are correct.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-53010: Error in deploying adapters.

Cause: Adapter deployment failed.

Action: Make sure that all the specified values are correct and domain configuration is valid.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-53011: Error in deploying Composites.

Cause: Composite deployment failed.

Action: Make sure that the config plan for {0} is valid or exists in archive.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-53012: "soa-infra" is down.

Cause: Application "soa-infra" was not in active state. SOA specific "Paste Configuration" operations cannot be executed.

Action: Make sure that all the specified values in the move plan are correct.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-53013: SOA Plugin examination failed.

Cause: Execution of "Copy Configuration" of SOA failed.

Action: Make sure that the SOA managed server is started and all the applications targeted to the SOA managed server are in active state.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-53014: Plugin "Pre-Paste Configuration" execution failed.

Cause: Execution of "Paste Configuration" of SOA failed.

Action: Check the clone logs and SOA managed server logs. Make sure that all the specified values in the move plan are correct and none of the "READ_ONLY" properties are modified.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-53015: Error in deploying Composites.

Cause: Composite deployment failed.

Action: Make sure that the config plans are valid and end points are configured correctly in composite config plans.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-53016: Error in stopping SOA managed server.

Cause: Could not stop SOA managed server.

Action: Check the managed server logs for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-53017: Error in examining B2B delivery channels from the move plan.

Cause: B2B delivery channel configuration failed.

Action: Make sure that values specified in the move plan are correct and none of the "READ_ONLY" properties are modified.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-53018: Error in deploying Composites.

Cause: Composite deployment failed.

Action: Make sure that the config plans are configured correctly. Check managed server and t2p logs for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-53019: OWSM Policy migration failed.

Cause: Make sure that the SOA managed server is started and applications targeted to the SOA managed server are in active state.

Action: Check the clone logs for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-53020: Error in connecting to BPM Managed Server.

Cause: BPM Managed Server was down.

Action: Make sure that all managed servers in specified domain are started.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-53021: SOA Plugin examination failed.

Cause: Execution of "Copy Configuration" of SOA failed.

Action: Make sure that the BPM managed server is started and all the applications targeted to the BPM managed server are in active state.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-53022: Error in examining BPM.

Cause: BPM examination failed.

Action: Make sure that all the specified values are correct and domain configuration is valid. Check managed server logs and clone logs for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-53023: Error in importing B2B Application data.

Cause: B2B Application data migration failed.

Action: Make sure that all the specified values in the move plan are correct and archive is valid.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-53024: Error in importing BPM Application data.

Cause: BPM Application data migration failed.

Action: Make sure that all the specified values in the move plan are correct and archive is valid.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-53025: Error in validating SOA domain.

Cause: The domain is not ready for deploying composites.

Action: Make sure that all the specified values in the move plan are correct. Check server logs for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-53026: Error copying the MDM URL Resolver configuration file.

Cause: Unable to copy the updated "{0}" file to "{1}".

Action: Make sure that the file exists and has the required permissions.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-53027: Error in importing MDS data.

Cause: MDS import for "soa-infra" application failed.

Action: Check SOA server logs for details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-53028: Invalid password file.

Cause: The {0} password file {1} did not exist or first line did not contain password.

Action: Provide a valid password file.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-53029: An internal error occurred.

Cause: Could not create the B2B Callout Directory, {0}.

Action: Move the B2B Callout Directory from source to target post "pasteConfig" operation.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-53030: An internal error occurred.

Cause: Could not create the B2B Large Payload Directory, {0}.

Action: Move the B2B Large Payload Directory from source to target post "pasteConfig" operation.
Level: 1

Type: ERROR

Impact: Cloning

26 CONF-30000 to CONF-35141

CONF-30000: Error creating Management Admin Server.

Cause: Oracle Instance directory {0} already exists.

Action: Provide a valid instance home path.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30001: Error creating Management Admin Server.

Cause: {0}

Action: See the log for more information.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30002: Error creating AS Component {0} of type {1}.

Cause: {0}

Action: See the log for more information.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30003: Error creating AS Component {0} of type {1}.

Cause: {0}

Action: See the log for more information.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30004: Error creating routing relationship to provider.

Cause: An internal error has occurred.

Action: See the log for more information.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30005: Error creating routing relationship to provider. Relation {0} already exists.

Cause: An internal error has occurred.

Action: See the log for more information.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30006: Timed out while waiting for Management Admin Server to start.

Cause: The process is taking more time or not listening at this time.

Action: See the log for more information.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30007: Management Admin Server appears to be unavailable.

Cause: {0}

Action: Make sure that the admin server is running and try again.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30008: Error creating routing relationship. Invalid user or provider components. User:{0}. Provider:{1}.

Cause: The user or provider components are not valid.

Action: Make sure that the user and providers are valid components.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30009: Cannot create Application Server. OracleInstance directory {0} already exists.

Cause: The oracle instance home exists

Action: Choose a different oracle instance home
Level: 1

Type: ERROR

Impact: Configuration

CONF-30010: An error occurred while provisioning an AS Instance (oracleInstance:{0} instanceName:{1}).

Cause: {0}

Action: See log for more information.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30011: Unable to access the Process Control Service.

Cause: Process Control Service is not available

Action: Try again after the process control service is available
Level: 1

Type: ERROR

Impact: Configuration

CONF-30012: Error occurred while starting {0} of type {1} in AS Instance {2}. See internal exception for details.

Cause: Internal error has happened.

Action: See log for more details
Level: 1

Type: ERROR

Impact: Configuration

CONF-30013: Error occurred while stopping {0} of type {1} in AS Instance {2}. See internal exception for details.

Cause: Some internal error has happened

Action: See error logs for more options
Level: 1

Type: ERROR

Impact: Configuration

CONF-30014: An unknown exception was generated while executing the configuration workflow. See internal exception for more details.

Cause: Workflow internal exception

Action: See logs for more information
Level: 1

Type: ERROR

Impact: Configuration

CONF-30015: Operation to provision an AS Instance (Instance Name:{0} Instance Home: {1}) timed out.

Cause: Timeout exception has happened

Action: See logs for more information
Level: 1

Type: ERROR

Impact: Configuration

CONF-30016: Failed to start an AS Instance (oracle instance:{0}, oracle home:{1}).

Cause: {0}

Action: See logs for more details
Level: 1

Type: ERROR

Impact: Configuration

CONF-30017: Error creating routing relationship. Relationship details { User:{0} Provider:{1} RelationshipName:{2} }.

Cause: {0}

Action: See logs for more details
Level: 1

Type: ERROR

Impact: Configuration

CONF-30018: Error creating AccessPoint {0}.

Cause: {0}

Action: See logs for more details
Level: 1

Type: ERROR

Impact: Configuration

CONF-30019: Unable to obtain the DeploymentManager. Deployment URI:{0}

Cause: Connected Deployment manager could not be found.

Action: See logs for more details
Level: 1

Type: ERROR

Impact: Configuration

CONF-30020: Error deploying a J2EE Application. See internal exception for details.

Cause: Internal Exception

Action: See logs for more details
Level: 1

Type: ERROR

Impact: Configuration

CONF-30021: Unable to locate the target for deployment.Target: {0}

Cause: The deployment target does not exist

Action: Make sure that the target exists
Level: 1

Type: ERROR

Impact: Configuration

CONF-30022: Error creating UnmanagedNetworkDevice {0}.

Cause: {0}

Action: See logs for more details
Level: 1

Type: ERROR

Impact: Configuration

CONF-30023: Error updating metric rule {0}.

Cause: {0}

Action: See logs for more details
Level: 1

Type: ERROR

Impact: Configuration

CONF-30024: Error Executing asctl command through ASconfig: {0}.

Cause: {0}

Action: See logs for more details
Level: 1

Type: ERROR

Impact: Configuration

CONF-30025: Unable to locate the endpoint - {0}.

Cause: The specified end point does not exist

Action: Specify a valid end point
Level: 1

Type: ERROR

Impact: Configuration

CONF-30026: Failed to start a MAS Transaction.

Cause: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30027: Failed to commit a MAS Transaction.

Cause: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30028: Failed to roll back a MAS Transaction.

Cause: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30029: Failed to register an LDAP Server as an unmanaged topology node. LDAP Server name:{0} LDAP Server type:{1}

Cause: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30030: Invalid LDAP Server Name. Specify a valid LDAP server name and try again.

Cause: Invalid LDAP server

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30031: Failed to register an LDAP Server as an unmanaged topology node.

Cause: Invalid LDAP Server Type {0}.

Action: Specify one of the following valid supported LDAP Server Types: \'UnmanagedLDAPServer\', \'UnmanagedOIDComponent\', \'UnmanagedActiveDirectory\'
Level: 1

Type: ERROR

Impact: Configuration

CONF-30032: Error while registering database schema {0} to MAS .

Cause: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30033: Error while calling configuration assistant {0}

Cause: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30034: Error occurred while trying restart {0} of type {1} in AS Instance {2}. See internal exception for details.

Cause: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30035: Failed to create a routing relationship to provider.

Cause: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30036: Error generating Provisioning workflow

Cause: Invalid FarmName

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30037: Error updating Bootstrap Credentials for IDStore

Cause: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30038: Error updating Bootstrap Credentials for IDStore

Cause: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30039: Error creating a Synchronized Group {0}.

Cause: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30051: Error locating the ASInstance in the Farm with the given canonical path {0}

Cause: {0}

Action: Provide the correct canonical path for the ASInstance
Level: 1

Type: ERROR

Impact: Configuration

CONF-30052: Error locating the ASJ2EEApplication in the Farm with the given canonical path {0}

Cause: {0}

Action: Provide the correct canonical path for the ASJ2EEApplication
Level: 1

Type: ERROR

Impact: Configuration

CONF-30053: Error locating the SystemComponent in the Farm with the given canonical path {0}

Cause: {0}

Action: Provide the correct canonical path for the SystemComponent
Level: 1

Type: ERROR

Impact: Configuration

CONF-30054: Error obtaining InstanceHome location for {0}

Cause: {0}

Action: See logs for more details
Level: 1

Type: ERROR

Impact: Configuration

CONF-30055: Error obtaining the OracleHome associated with {}

Cause: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30056: TopologyNode {0} does not exist in farm.

Cause: Invalid canonical path

Action: Provide a valid canonical path
Level: 1

Type: ERROR

Impact: Configuration

CONF-30057: An exception was generated while executing the provisioning workflow.

Cause: {0}

Action: See logs for more details
Level: 1

Type: ERROR

Impact: Configuration

CONF-30060: Error while calling validation assistant {0}

Cause: {0}

Action: See log for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30090: The given node is not a valid MDS schema. {0}

Cause: Invalid MDS schema

Action: Provide a valid MDS Schema.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30091: Error deploying a J2EE Application. {0}

Cause: Internal Exception

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30092: The process has been interrupted

Cause: The process has been interrupted

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30093: The application archive could not be loaded as a deployable object

Cause: Some deployment Exception has happened

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30094: File not found. The specified file {0} is not found.

Cause: File is not present

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30095: Configuration Exception happened. See the embedded exception for more details.

Cause: Internal Exception

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30096: Unable to get the deployment configuration.

Cause: The application archive {0} is a invalid archive.

Action: Check the archive and try again.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30097: Unable to locate application archive. "{0}"

Cause: The location to archive is not correct.

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30098: Unable to obtain the DeploymentManager. Deployment URI:{0}

Cause: Internal Exception

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30099: Unable to locate the target for deployment. Target: {0}

Cause: Invalid deployment target

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30100: Error creating an Oracle Load Balancer {0}.

Cause: {0}

Action: See logs for more details
Level: 1

Type: ERROR

Impact: Configuration

CONF-30101: Error associating ASInstance(s) with an Oracle Load Balancer {0}.

Cause: {0}

Action: Specify valid ASInstances.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30111: Error while registering unmanaged SSO Server to MAS .

Cause: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30112: Failed to stop an AS Instance (oracle instance:{0}).

Cause: {0}

Action: See logs for more details
Level: 1

Type: ERROR

Impact: Configuration

CONF-30113: See logs for more details.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CONF-30114: See logs for more details.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CONF-30115: Error storing entries in Credential Store

Cause: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30116: Error retrieving entries from Credential Store

Cause: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30117: Error deleting entries from Credential Store

Cause: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30121: Error assigning AccessPoint {0} to {1}

Cause: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35001: Invalid host value provided to config framework.

Cause: Invalid host value provided to config framework.

Action: Provide a valid host value to config framework
Level: 1

Type: ERROR

Impact: Configuration

CONF-35002: Invalid port value provided to config framework.

Cause: Invalid port value provided to config framework.

Action: Provide a valid port value to config framework
Level: 1

Type: ERROR

Impact: Configuration

CONF-35003: Error while creating the domain.

Cause: An internal operation has failed.

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35004: Error while creating Managed Server.

Cause: An internal operation has failed: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35005: Error while starting the domain.

Cause: An internal WLST operation has failed.

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35006: Unable to connect to the AdminServer.

Cause: An internal operation has failed:{0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35007: Error while setting control flag {0}.

Cause: An internal operation has failed: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35009: Error while stopping the domain.

Cause: An internal operation has failed: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35010: Error while deploying the Application {0} .

Cause: An internal operation has failed: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35011: Error while starting the Application {0} .

Cause: An internal operation has failed: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35012: Error while stopping the Application {0} .

Cause: An internal operation has failed: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35015: Error while creating Group {0} .

Cause: An internal operation has failed: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35020: Error while creating DataSource {0} .

Cause: An internal operation has failed: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35025: Error while creating JMSResource {0}.

Cause: An internal operation has failed: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35030: Error while creating Authenticator {0}.

Cause: An internal operation has failed: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35035: Error while executing WLS script located at {0}.

Cause: An internal operation has failed: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35040: Error while creating Network Channel {0}.

Cause: An internal operation has failed: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35075: Error creating ASInstance {0}.

Cause: An internal operation has failed: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35076: Error creating ASComponent {0}.

Cause: An internal operation has failed: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35080: Error Applying template.

Cause: A WLST Error occurred: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35081: Error Applying template.

Cause: Domain Home cannot be empty.

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35082: Error creating Domain {0}.

Cause: A WLST Error occurred.

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35085: Error creating Cluster {0}.

Cause: See logs for more details.

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35090: Error while starting the domain.

Cause: Starting the Admin_Server timed out.

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35091: Error while starting the domain.

Cause: An error occurred while starting the domain.

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35092: Error Setting target for Startup class {0}.

Cause: An internal error has occurred.

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35095: Error setting target for Shutdown class {0}.

Cause: An internal error has occurred.

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35100: Error starting and enrolling Node Manager

Cause: An internal operation has failed.

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35105: Error Creating Multi Data Source {0}

Cause: An internal operation has failed

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35110: Error Extending Targets With JRF Template.

Cause: WLST Error. {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35111: Error Extending Targets With JRF Template.

Cause: Domain Home cannot be empty.

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35115: Error Setting target to Managed Server {0}.

Cause: Check the logs for details.

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35120: Error Starting Managed Server {0}.

Cause: An internal error has occurred : {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35122: Number Format Exception thrown when trying to get nodemanager port.

Cause: The Nodemanager Listen port entry is not present in the nodemanager.properties file or it is not set to numeric value.

Action: Add the Nodemanager port (for example, ListenPort=5556) to the nodemanager.properties file and press Retry button to continue the configuration.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35124: Stage Modes 'EXTERNAL_STAGE' and 'NOSTAGE' cannot be set simultaniously.

Cause: Both stage modes 'EXTERNAL_STAGE' and 'NOSTAGE' have been set.

Action: Use only 'EXTERNAL_STAGE' or 'NOSTAGE' mode for deployment
Level: 1

Type: ERROR

Impact: Configuration

CONF-35126: Node Manager Listen Port is set to a negative number.

Cause: Node Manager Listen Port is set to a negative number.

Action: Add the Nodemanager port(Eg: ListenPort=5556) to the nodemanager.properties file and press Retry button to continue the configuration.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35128: Unable to set Attribute 'StartScriptEnabled'.

Cause: Unable to set Attribute 'StartScriptEnabled' since the NodeManager is already running.The installer needs to set it to 'true'

Action: Stop the Node Manager and retry the installer.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35130: Unable to set Attribute 'StartScriptEnabled'.

Cause: Unable to set Attribute 'StartScriptEnabled' since the NodeManager is already running.The installer needs to set it to 'true'

Action: Stop the Node Manager and retry the installer.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35132: Unable to set Attribute 'NativeVersionEnabled'.

Cause: Unable to set Attribute 'NativeVersionEnabled' since the NodeManager is already running.The installer needs to set it to 'true'

Action: Stop the Node Manager and retry the installer.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35134: Unable to set Attribute 'NativeVersionEnabled'.

Cause: Unable to set Attribute 'NativeVersionEnabled' since the NodeManager is already running.The installer needs to set it to 'true'

Action: Stop the Node Manager and retry the installer.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35136: Error while starting the Managed Server.

Cause: An interanal WLST operation has failed.

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35137: Managed Server {0} started in FAILED state.

Cause: An internal error has occured : {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35140: Managed Server shutdown command Failed.

Cause: An internal error has occured : {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35141: Managed Server {0} shutdown timed out.

Cause: An internal error has occured : {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

27 DFW-40004 to DFW-40204

DFW-40004: The requested diagnostic dump {0} is unknown.

Cause: The diagnostic dump {0} has either not been registered or the given name is incorrect.

Action: Ensure that a valid dump name is specified.
Level: 1

Type: WARNING

Impact: Configuration

DFW-40005: The mandatory dump argument {0} is not specified.

Cause: A request to execute a dump was made without specifying all mandatory arguments.

Action: Ensure that all mandatory arguments are specified.
Level: 1

Type: WARNING

Impact: Programmatic

DFW-40006: ignoring dump argument {0} as it is not defined for diagnostic dump {1}

Cause: The dump does not accept the specified argument.

Action: Ensure that only arguments defined by the dump are specified.
Level: 1

Type: NOTIFICATION

Impact: Programmatic

DFW-40007: The diagnostic dump argument {0} should be of type {1}.

Cause: The specified argument is of the wrong type.

Action: Ensure that arguments are of the correct type.
Level: 1

Type: WARNING

Impact: Programmatic

DFW-40008: failed to execute diagnostic dump {0}

Cause: An error occurred during the execution of the dump.

Action: Check process logs for more information.
Level: 1

Type: WARNING

Impact: Process

DFW-40009: failure creating dump file

Cause: An error occurred creaing a dump file

Action: See base error for root cause and check process logs for more information.
Level: 1

Type: WARNING

Impact: Process

DFW-40010: failure registering JRockit Flight Recorder diagnostic dump

Cause: This could be due to JRockit not being used as the JVM.

Action: See the reported Exception for more information.
Level: 1

Type: WARNING

Impact: Other

DFW-40100: failed to create ADR Base directory {0}

Cause: An error occurred whilst attempting to create the ADR Base directory required to store captured diagnostics data. This may be due to file or process permissions.

Action: Check that the process has permission to create the directory.
Level: 1

Type: ERROR

Impact: Operating System

DFW-40102: failure during incident rule processing of incident {0}

Cause: During the processing of the incident rules an error occurred.

Action: See base error for root cause and check process logs for more information.
Level: 1

Type: WARNING

Impact: Other

DFW-40103: failed to execute dump during creation of incident {0}

Cause: An error occurred during the execution of a diagnostic dump.

Action: See base error for root cause and check process logs for more information.
Level: 1

Type: WARNING

Impact: Other

DFW-40105: failed to execute dump {0} during creation of incident {1}

Cause: An error occurred during the execution of the dump.

Action: See base error for root cause and check process logs for more information.
Level: 1

Type: WARNING

Impact: Process

DFW-40106: failed to load diagnostic rules schema {0}

Cause: The diagnostic rules schema could not be loaded.

Action: Check that the specified schema exists and is readable.
Level: 1

Type: WARNING

Impact: Process

DFW-40107: failed to parse diagnostic rules

Cause: The diagnostic rules do not conform to the schema.

Action: Fix the diagnostic rules XML to make the rules valid.
Level: 1

Type: WARNING

Impact: Process

DFW-40108: invalid diagnostic rules document

Cause: The diagnostic rules document has invalid content.

Action: See base error for root cause and check process logs for more information.
Level: 1

Type: WARNING

Impact: Configuration

DFW-40109: failed to write and register incident {0} readme file with ADR

Cause: An issue occurred during the registration of the readme file. This does not impact the associated diagnostic dump data.

Action: Check that the process writing the readme file has sufficient privileges.
Level: 1

Type: NOTIFICATION

Impact: Process

DFW-40110: failure parsing ADRCI XML output

Cause: The XML returned by the ADRCI show incidents command could not be parsed.

Action: Check the process logs for more information.
Level: 1

Type: NOTIFICATION

Impact: Other

DFW-40111: failed to determine incident id and path from adrci output "{0}"

Cause: There was an error executing the command to create an incident using ADRCI.

Action: Ensure that command line tool "adrci" can be executed from the command line.
Level: 1

Type: ERROR

Impact: Data

DFW-40112: failed to execute the adrci commands "{0}"

Cause: There was an error executing adrci commands; the following errors have been found "{0}"

Action: Ensure that command line tool "adrci" can be executed from the command line.
Level: 1

Type: ERROR

Impact: Other

DFW-40113: failed to execute adrci commands; adrci returned "{0}"

Cause: There was an error executing adrci commands.

Action: Ensure that command line tool "adrci" can be executed from the command line.
Level: 1

Type: ERROR

Impact: Other

DFW-40114: The ADR Product ID exceeds the maximum length {0}.

Cause: The given ADR Product ID is too long.

Action: The ADR Product ID will automatically be truncated. No further action is required.
Level: 1

Type: WARNING

Impact: Files

DFW-40115: The ADR Instance ID exceeds the maximum length {0}.

Cause: The given ADR Instance ID is too long.

Action: The ADR Instance ID will automatically be truncated. No further action is required.
Level: 1

Type: WARNING

Impact: Files

DFW-40116: failure creating incident

Cause: An error occurred during the creation of an incident.

Action: See base error for root cause anc check process logs for more information.
Level: 1

Type: WARNING

Impact: Process

DFW-40118: ADR incident creation is disabled; incident not created.

Cause: Diagnostics Framework was unable to initialize ADR, resulting in ADR creation being disabled.

Action: Check the process logs for more information on why ADR could not be initialized.
Level: 1

Type: NOTIFICATION

Impact: Process

DFW-40119: file {0} cannot be added to incident {1} as it exceeds the maximum filename length of {2} characters

Cause: The specified filename length exceeds the maximum allowed by ADR.

Action: Specify a filename whose length does not exceed the maximum alloweed length.
Level: 1

Type: WARNING

Impact: Files

DFW-40121: failure creating incident from WLDF notification

Cause: An error occurred whilst attempting to create an incident.

Action: See the base exception for details, and check the process logs for more information.
Level: 1

Type: WARNING

Impact: Process

DFW-40123: file {0} is not registered with incident {1}

Cause: The specified filename is not associated with the incident

Action: Specify the name of a file that is registered with the incident
Level: 1

Type: NOTIFICATION

Impact: Programmatic

DFW-40125: incident flood controlled with Problem Key "{0}"

Cause: The specified Problem Key is under flood control, due to the volume of incidents with that Problem Key exceeding the maximum incident count.

Action: Inspect the reason for the creation of incidents with the specified Problem Key and resolve the issue.
Level: 1

Type: WARNING

Impact: Other

DFW-40126: incident with Problem Key "{0}" could not be created due to lack of available disk space for incidents; configured maximum is {1} bytes and used is {2} bytes

Cause: The incident with the specified Problem Key could not be created due to lack of available disk space allocated for incidents.

Action: Purge old incidents or increase the maximum allowed disk space for incidents in dfw_config.xml.
Level: 1

Type: WARNING

Impact: Other

DFW-40127: incident filtered with Problem Key "{0}"

Cause: The specified Problem Key is configured to be filtered.

Action: If the problem key should not be filtered modify the DFW configuration to remove the appropriate filter.
Level: 1

Type: WARNING

Impact: Other

DFW-40128: invalid Problem Key filter pattern "{0}"

Cause: The specified Problem Key filter pattern is invalid.

Action: See the base error for the specific error and fix the pattern
Level: 1

Type: WARNING

Impact: Other

DFW-40200: failed to load diagnostics configuration schema {0}

Cause: The diagnostics configuration schema could not be loaded. See base exception for root cause

Action: Check that the specified schema exists and is readable.
Level: 1

Type: WARNING

Impact: Configuration

DFW-40201: failed to parse diagnostics configuration

Cause: The diagnostics configuration document does not conform to the schema.

Action: Fix the diagnostic configuration XML to make the configuration valid.
Level: 1

Type: WARNING

Impact: Process

DFW-40203: failure initializing diagnostics security context

Cause: An error occurred initializing the internal Diagnostic Framework security context.

Action: See the base exception for details, and check the process logs for more information.
Level: 1

Type: WARNING

Impact: Process

DFW-40204: invalid ADR Home path {0}

Cause: The specified ADR Home is not a valid path.

Action: Specify a valid ADR Home path of the form diag/<productType>/<productId>/<instanceId>
Level: 1

Type: WARNING

Impact: Programmatic

28 DIP-00003 to DIP-87002

DIP-00003: Error in closing Oracle Internet Directory server connection.

Cause: An unexpected error occured in closing of Oracle Internet Directory connection.

Action: Make sure Oracle Internet Directory host, port, user, password values are correct or server is running.
Level: 1

Type: ERROR

Impact: Installation

DIP-00004: Error in connecting to Oracle Internet Directory Server.

Cause: Could not connect to Oracle Internet Directory server.

Action: Contact oracle support.
Level: 1

Type: ERROR

Impact: Network

DIP-00006: Error while DIP schema creation.

Cause: Failed to create DIP schema due to invalid file content.

Action: Contact oracle support.
Level: 1

Type: ERROR

Impact: Files

DIP-00007: Error while creating RootOracleContext.

Cause: Failed to create DIP root oracle context with invalid file or invalid file content.

Action: Contact oracle support.
Level: 1

Type: ERROR

Impact: Files

DIP-00009: Error while creating template profiles.

Cause: Failed to create DIP template sync profiles due to invalid file content.

Action: Contact oracle support.
Level: 1

Type: ERROR

Impact: Configuration

DIP-00010: Error in modifying attributes.

Cause: Update of attribute {0} of {1} by LDAP operation.

Action: Contact oracle support.
Level: 1

Type: ERROR

Impact: Data

DIP-00013: Error in reading DIP Schema details.

Cause: Invalid query for container DN {0} from DIP schema.

Action: Contact oracle support.
Level: 1

Type: ERROR

Impact: Data

DIP-00014: Error in setting DIP password.

Cause: Failed to set DIP password in CSF

Action: Contact oracle support.
Level: 1

Type: ERROR

Impact: Data

DIP-00019: Errors occured while performing LDAP operation

Cause: User has no access rights to modify particular Distinguished Name or attribute to modify does not exists.

Action: Contact oracle support.
Level: 1

Type: ERROR

Impact: Data

DIP-00020: obtaining LDAP connection failed in attempt number :{0} - Retrying

Cause:

Action:
Level: 1

Type: WARNING

Impact: Network

DIP-00021: maximum LDAP connection retry count reached.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Network

DIP-00022: Connection to LDAP server failed.

Cause: Directory Integration Platform Server was not able to connect to the LDAP server.

Action: Contact oracle support.
Level: 1

Type: ERROR

Impact: Network

DIP-10004: Error in closing newly created context.

Cause: Unable to close the connection with the directory Server.

Action: Check the server is running properly.
Level: 1

Type: ERROR

Impact: Network

DIP-10006: Error in executing reconciler : {0}

Cause: Execution of reconciliation failed in agent thread

Action: Check the log file and if required contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Threads

DIP-10008: error in mapping engine {0} .

Cause: Errors occured in map engine it might have caused by errors in map rule.

Action: Validate the profile to confirm that the map rules are correct.
Level: 1

Type: ERROR

Impact: Data

DIP-10009: error in proxy connection through the profile.

Cause: Failed to connect to Oracle Internet Directory through the proxy.

Action: Check if profile (the proxy) is running properly
Level: 1

Type: ERROR

Impact: Network

DIP-10010: error in setting legacy ldap control

Cause: Failed to set up the legacy ldap control

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Network

DIP-10011: error in updating the status of profile execution.

Cause: Failed to connect to Oracle Internet Directory or update or metrics data.

Action: Check if odip group has permissions to update the container 'cn=subscriber profile,cn=changelog subscriber,cn=Oracle Internet Directory'.
Level: 1

Type: ERROR

Impact: Data

DIP-10013: Exception

Cause: Unknow errors occured in execution.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-10017: Directories are in a inconsistent state,entry reconcile {0} is inconsistent.

Cause: Tried to add-delete or add-modify operation for same entry.

Action: Start the reconciler or delete that entry from the connected directory so that it gets synchronized properly at the next interval.
Level: 1

Type: ERROR

Impact: Data

DIP-10025: reader initialization failed.

Cause: Failed connect to the source directory during synchronization.

Action: Check the connection details of the source directory for synchronization profile.
Level: 1

Type: ERROR

Impact: Data

DIP-10028: Interrupted while waiting to retry the profile execution.

Cause: Another job has interrupted during retry proocess.

Action: Restart the Directory Integration Platform server.
Level: 1

Type: ERROR

Impact: Threads

DIP-10030: Target directory is unable to process this entry: {0}.

Cause: Failed to make change in the directory, might have caused by error in the entry.

Action: Check the log file for details.
Level: 1

Type: ERROR

Impact: Data

DIP-10038: Incorrect Format: first Line after TAG should be an <attribute:value> pair.

Cause: Config file is not in proper format.

Action: Correct the format of config file.
Level: 1

Type: ERROR

Impact: Data

DIP-10045: FATAL ERROR:Connect Information Format {0} is Incorrect!!

Cause: Wrong format of connection information

Action: Give the connection information in proper format
Level: 1

Type: ERROR

Impact: Network

DIP-10046: Error in opening logFile: {0}.

Cause: Failed to create a log file.

Action: Check permissions of the directory and the file path specified in j2ee-logging.xml file is valid.
Level: 1

Type: ERROR

Impact: Files

DIP-10047: Error Reading : {0} : For Mode : {1} : Exception : {2}.

Cause: Failed to initialize the last applied change key.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-10048: exception in reading netdescription String.

Cause: Failed to initialize destination connector.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-10066: scheduling interval not specified.

Cause: Scheduler interval was not specified in the properties file while creating a profile.

Action: Specify the scheduling interval in the profile.
Level: 1

Type: ERROR

Impact: Data

DIP-10072: Unknown interface Type specified - {0}.

Cause: Interface type specified in the config file was not valid.

Action: Specify the supported interface type.
Level: 1

Type: ERROR

Impact: Data

DIP-10074: Class Not Found: {0}

Cause: Failed to load the class specified in the synchronization profile configuration.

Action: Check the class name specified in the synchronization profile configuration.
Level: 1

Type: ERROR

Impact: Data

DIP-10075: Error in reading mapping.

Cause: Exceptions thrown while reading mapping information.

Action: Confirm that the mapping rules are correctly specified in the profile. validate the profile mapping rules using the manageSyncProfile command.
Level: 1

Type: ERROR

Impact: Data

DIP-10076: Error in reading reconciler information.

Cause: Exceptions occured while reading reconciliation information.

Action: Confirm that the reconciler information is correctly specified along with mapping rules and reconciliation attributes are properly specified in the profile. Check the documentation for details.
Level: 1

Type: ERROR

Impact: Data

DIP-10077: Exception encountered in forming agent execution command.

Cause: Exception is thrown while initializing execution command.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

DIP-10078: Exception in initializing profile.

Cause: failed to initialize the profile.

Action: Check if the contents of the profile are correct in properties file.
Level: 1

Type: ERROR

Impact: Data

DIP-10079: Exception in reading profile attributes.

Cause: Failed to read profile information

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-10090: Invalid reduceFilterTime default reduceFilterTime will be 0.

Cause: Invalid reduce filter time parameter specified in profile.

Action: reduceFilterTime attribute should have integer value. Modify the profile with proper value for the additional config attribute.
Level: 1

Type: ERROR

Impact: Data

DIP-10091: Not able to get reduceFilterTime default reduceFilterTime will be 0.

Cause: Reduce filter time parameter is not specified in the additional config parameter.

Action: reduceFilterTime attribute should have integer value. Modify the profile with proper value for the additional config attribute.
Level: 1

Type: ERROR

Impact: Configuration

DIP-10100: Could not add version 1.0 Profile. Initialization failure : {0}.

Cause: Failed to add version 1.0 profile in the provisioning list.

Action: Check the value of all properties in the properties file.
Level: 1

Type: ERROR

Impact: Data

DIP-10101: Could not add version 2.0 Profile. Initialization failure : {0}.

Cause: Failed to add version 2.0 profile in the provisioning list.

Action: Check the value of all properties in the properties file.
Level: 1

Type: ERROR

Impact: Data

DIP-10103: Error in getting last change number from Oracle Internet Directory.

Cause: Exceptions thrown while reading last change number from Oracle Internet Directory.

Action: Check the exception trace and confirm that change log has been enabled in Oracle Internet Directory.
Level: 1

Type: ERROR

Impact: Data

DIP-10104: Error reading reconcilation profile.

Cause: Details for reconciliation could not be read properly from the profile.

Action: Check the reconciliation information specified in the profile.
Level: 1

Type: ERROR

Impact: Data

DIP-10105: Error in refreshing the Profile : {0}

Cause: Exception thrown while refreshing the profile.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-10106: Error in scheduler initialization.

Cause: Exceptions thrown while initializing the scheduler

Action: Check the server config parameters for details check the log file.
Level: 1

Type: ERROR

Impact: Threads

DIP-10107: Error while setting the privacy control in ldap context.

Cause: Exceptions thrown while setting the control in the directory server in the scheduler

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

DIP-10108: Exception in adding version 2 profile.

Cause: Failed to add version 2 profile in the prov list

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-10109: Exception in adding provisioning profile.

Cause: Failed to add provisioning profile for scheduling

Action: Check that the profile is not already scheduled else check the log file.
Level: 1

Type: ERROR

Impact: Data

DIP-10110: Exception encountered in reconnecting to Oracle Internet Directory.

Cause: Failed to connect to Oracle Internet Directory

Action: Check OID host and port details in server configuration and also verify that OID server is running properly
Level: 1

Type: ERROR

Impact: Network

DIP-10116: Not able to add version 1 profile.

Cause: Failed to add version 1 profile in the provisioning job list.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Threads

DIP-10117: Security encryption algorithm not supported in the library.

Cause: Given security encryption algorithm not supported.

Action: Check the encryption algorithm is given properly.
Level: 1

Type: ERROR

Impact: Security

DIP-10122: Scheduler error.

Cause: Exceptions thrown in synchronization profile scheduler.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Threads

DIP-10123: Scheduler interrupted

Cause: Scheduler was interrupted by another running thread.

Action: Try restarting the DIP server.
Level: 1

Type: ERROR

Impact: Threads

DIP-10124: Error reading profiles for scheduling.

Cause: Exceptions thrown while reading the profile information.

Action: Check that the profile specified is indeed present in the Oracle Internet Directory server.
Level: 1

Type: ERROR

Impact: Data

DIP-10132: Exception in adding profile

Cause: Exceptions thrown while adding profile in the list.

Action: Check that profile is not already scheduled.
Level: 1

Type: ERROR

Impact: Data

DIP-10133: Exception encountered in reconnecting to Oracle Internet Directory.

Cause: Exception is thrown while connecting to OID

Action: Check Oracle Internet Directory host and port details and it is running properly
Level: 1

Type: ERROR

Impact: Network

DIP-10139: Error in schedulling.

Cause: Generic exception was thrown while scheduling provisioning profiles.

Action: Check if profile is valid or not.
Level: 1

Type: ERROR

Impact: Threads

DIP-10145: Error in configuring logging.

Cause: Invalid debug level specified in DIP server configuration set.

Action: Correct the debug level specified in DIP server configuration.
Level: 1

Type: ERROR

Impact: Logging

DIP-10146: Connection to directory server failed, will retry after {0} ms.

Cause: Failed to connect to directory server.

Action: Check the host and port of directory server and also check it is running.
Level: 1

Type: ERROR

Impact: Network

DIP-10184: Error reading entrydn {0}.

Cause: Failed to read the target dn entry.

Action: Check if the entry exists in Target Directory Server.
Level: 1

Type: ERROR

Impact: Data

DIP-10185: Error reading ObjectGUID.

Cause: Error occurred while reading Object GUID of target dn.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-10187: Error in adding user to domain admin group.

Cause: Exceptions thrown while adding user to a group.

Action: Check log file for details.
Level: 1

Type: ERROR

Impact: Data

DIP-10188: Failed to read useraccountcontrol value.

Cause: Exception thrown while reading user account control attribute.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-10191: Error in getting the GUID of the entry. Skipping

Cause: Errors occured while reading GUID of the entry.

Action: Check log file for more details.
Level: 1

Type: ERROR

Impact: Data

DIP-10192: Error in updating the status for user with GUID : {0}.

Cause: Errors occured while while updating the user entry with GUID.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-10193: NoSuchElementException in getting next entry.

Cause: Errors occured while getting the next item

Action: No action required.
Level: 1

Type: ERROR

Impact: Data

DIP-10194: Unknown exception

Cause: Unknown exception

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-10195: Unable to obtain local host name.

Cause: Failed to get the host name and ip address.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Network

DIP-10196: Error in parsing the modifytimestamp.

Cause: Errors occured while reading modifytimestamp attribute

Action: Check the modifytimestamp is in proper format for the profile.
Level: 1

Type: ERROR

Impact: Data

DIP-10200: Error in getting the local Hostname : {0}.

Cause: Failed to get the host name and ip address.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Network

DIP-10201: Directory Context Exception:

Cause: Exception is thrown while searching on the directory context

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

DIP-10202: LDAP Context Exception:

Cause: Exception is thrown while searching on the ldap context

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

DIP-10203: LDAP CommuncationException.

Cause: Communication failure with directory server.

Action: Check the host and port detail of directory server and it is running.
Level: 1

Type: ERROR

Impact: Network

DIP-10205: NamingException.

Cause: Errors occured while connecting to directory server.

Action: Check log file for details.
Level: 1

Type: ERROR

Impact: Data

DIP-10206: LDAP AuthenticationException.

Cause: Failed to bind to directory server

Action: Check the credential information of directory server.
Level: 1

Type: ERROR

Impact: Security

DIP-10218: Exception in calculating new DN during MODDN operation.

Cause: Errors occured while performing modRDN operation.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-10219: Exception creating entry : {0}.

Cause: Failed to create an entry in the directory server.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-10220: Exception while performing delete operation for entry : {0}.

Cause: Failed while performing delete operation.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-10221: Exception deleting entry : {0}.

Cause: Exception is thrown while deleting an entry

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-10223: Exception in looking for: {0}.

Cause: Exception is thrown while searching for an entry.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-10224: Exception while performing modify operation for entry : {0}.

Cause: Exception is thrown while performing modify operation.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-10225: Exception modifying entry : {0}.

Cause: Exception is thrown while modifying an entry

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-10226: Exception doing ModRDN operation for entry : {0}.

Cause: Exception is thrown while performing mod RDN operation on an entry

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-10238: Error in enumerating LDAP search result.

Cause: Failed whiled iterating over the search records.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-10239: Error initializing last applied timestamp.

Cause: Failed to apply last applied timestamp.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-10240: Create change record error.

Cause: Failed while creating a change record.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-10241: Error in LDAP search operation.

Cause: Search operation caused errors.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-10242: Error get next change.

Cause: Errors occured in retrieving next change record.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-10246: MAPPING: exception in B64 Decoding.

Cause: Failed while decoding attribute value

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

DIP-10247: Not able to construct DN.

Cause: DIP Server was not able to construct the destination DN.

Action: Check the domain level mapping rules.
Level: 1

Type: WARNING

Impact: Data

DIP-10249: MAPPING: Mapping Domain Failed - DstChangeRecord : {0}

Cause: Failed while trying to map to the destination change record

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-10250: MAPPING: Mapping Domain Failed - setting DstChangeRecord to null.

Cause: DIP Server was not able to map the source domain to the destination domain.

Action: Check the domain level mapping rules.
Level: 1

Type: ERROR

Impact: Data

DIP-10253: Destination directory connection failed, retry count= {0}.

Cause: Failed to connect to directory server.

Action: Check the host and port details of the directory server and check the directory server is running properly.
Level: 1

Type: ERROR

Impact: Network

DIP-10257: Exception in reconcile() in source subset criteria : {0}.

Cause: Exception was thrown while searching for deleted entries.

Action: Check log files for details.
Level: 1

Type: ERROR

Impact: Data

DIP-10265: Source directory connection failed, retry count= {0}

Cause: Failed to connect to source directory

Action: Check the host and port details of source directory and it is running properly
Level: 1

Type: ERROR

Impact: Network

DIP-10266: Unable to check the entry in Source Directory.

Cause: Failed to read entries in the source directory.

Action: Check the source directory server is running properly and also check its host and port details.
Level: 1

Type: ERROR

Impact: Data

DIP-10267: Unable to delete the entry : {0}.

Cause: Failed to delete entry from the directory server

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-10268: Unable to do the search in destination directory.

Cause: Failed while searching for entries in the destination directory.

Action: Check destination directory is running properly.
Level: 1

Type: ERROR

Impact: Data

DIP-10269: Unable to do the search in source directory due to exception.

Cause: Failed while searching for entries in the source directory server.

Action: Check source directory server is running properly.
Level: 1

Type: ERROR

Impact: Data

DIP-10270: CommunicationException in PagedSearch.

Cause: communication failure in Paged search.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Network

DIP-10271: Exception in getSearchResults().

Cause: Search for entries caused exceptions.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-10274: Unable to parse the source subset criteria {0} due to exception.

Cause: DIP is failing while parsing the source subset criteria.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

DIP-10275: Unable to parse the target subset criteria due to exception.

Cause: Failed while parsing the target subset criteria.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

DIP-10277: Unable to delete the entry : {0} as the binddn does not have permission to delete it.

Cause: Failed Delete of an entry from the connected directory server.

Action: Check the permission of bind dn and password.
Level: 1

Type: ERROR

Impact: Data

DIP-10284: Unable to check the Page Control Search support.

Cause: Exception thrown while checking for the Page Control Search support.

Action: Check the exception trace or Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-10285: Unable to get the Page Size Limit.

Cause: Exception thrown while getting the Page Size Limit.

Action: Check the exception trace or or Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-10501: Unable to add version 1.0 provisioning profile {0}.

Cause: Directory Integration Platform was not able to add version 1.0 provisioning profile.

Action: Check the Directory Integration Server logs.
Level: 1

Type: ERROR

Impact: Data

DIP-10502: Exception in adding version 2.0 profile : {0}

Cause: Directory Integration Platform was not able to add version 2.0 provisioning profile.

Action: Check the server log.
Level: 1

Type: ERROR

Impact: Data

DIP-10503: Exception in adding version 3.0 profile : {0}

Cause: Directory Integration Platform was not able to add version 3.0 provisioning profile.

Action: Check the server log.
Level: 1

Type: ERROR

Impact: Data

DIP-10504: Ignoring invalid profile

Cause: Directory Integration Platform was not able to add it as the profile entry was invalid.

Action: Check the profile entry for Version 3.0.
Level: 1

Type: ERROR

Impact: Data

DIP-10505: Scheduler: unable to add profile {0}, refer to log file.

Cause: Directory Integration Platform tried to add a profile {0} but was not able to add it.

Action: Check the profile entry {0}.
Level: 1

Type: ERROR

Impact: Threads

DIP-10506: Unable to retrieve update timestamp attribute.

Cause: Directory Integration Platform was not successful in retrieving update timestamp attribute for one iteration of provisioning profile.

Action: Check the update timestamp attributes.
Level: 1

Type: ERROR

Impact: Data

DIP-10507: Unable to instantiate the schema for Directory Integration Platform.

Cause: The Directory Integration Platform schema was either invalid or not found.

Action: Check the Directory Integration Platform schema entry in Oracle Internet Directory.
Level: 1

Type: ERROR

Impact: Configuration

DIP-10508: Unable to get the update attributes for the provisioning profile {0}.

Cause: Directory Integration Platform was not successful in retrieving the attribute of the provisioning profile - {0}.

Action: Check the profile entry in Oracle Internet Directory.
Level: 1

Type: ERROR

Impact: Data

DIP-10509: Error in executing provisioning profile.

Cause: Directory Integration Platform was not successful in provisioning all the data during this iteration for profile.

Action: Check the log files for the error.
Level: 1

Type: ERROR

Impact: Process

DIP-10510: Error in updating profile status.

Cause: Directory Integration Platform was not successful in updating the profile status.

Action: Check the log files for the error.
Level: 1

Type: ERROR

Impact: Data

DIP-10511: Error in initializing the classes for the provisioning profiles.

Cause: Directory Integration Platform was not successful in initializing the classes for the prov profiles.

Action: Check the log files for the error.
Level: 1

Type: ERROR

Impact: Configuration

DIP-10512: Error in making a remote call to provisioning bean : {0}

Cause: Directory Integration Platform was not successful making remote call to initialize provisioning bean.

Action: Check whether Directory Integration Platform Prov Bean is up in the Enterprise Manager.
Level: 1

Type: ERROR

Impact: Requests/Responses

DIP-10513: Error while initializing the classes for enterprise scheduler : {0}

Cause: Directory Integration Platform was not successful in initializing the classes for the enterprise scheduler.

Action: Check the Enterprise Scheduler Service runtime and metadata Enterprise Java Beans in the Enterprise Manager.
Level: 1

Type: ERROR

Impact: Requests/Responses

DIP-10515: Enterprise Scheduler Service was not able to schedule all the jobs successfully {0}

Cause: An error occurred while scheduling jobs in the ESS.

Action: Refer to the Enterprise Scheduler Service stack trace.
Level: 1

Type: ERROR

Impact: Requests/Responses

DIP-10516: Exception occured in adding provisioning profiles.

Cause: Directory Integration Platform was not successful in adding provisioning profiles.

Action: Check the log files.
Level: 1

Type: ERROR

Impact: Requests/Responses

DIP-10517: Scheduler is not able to connect to Oracle Internet Directory, tried {0} times.

Cause: Directory Integration Platform was not able to connect to Oracle Internet Directory.

Action: Check the Oracle Internet Directory server status and configuration in Enterprise Manager.
Level: 1

Type: ERROR

Impact: Network

DIP-10518: Oracle Internet Directory version {0} is not supported.

Cause: Server was not started as the version was not valid.

Action: Check the Directory Integration Platform server current version and the valid versions in documentation.
Level: 1

Type: ERROR

Impact: Process

DIP-10519: Exception : during Directory Integration Platform startup.

Cause: Failed to retrieve the version attribute of Directory Integration Platform registration.

Action: Check if the Directory Integration Platform registration was successful.
Level: 1

Type: ERROR

Impact: Process

DIP-10520: ODI server instance registration failure

Cause: Some other Directory Integration Platform instance with same config set is already running.

Action: Start the Directory Integration Platform in another configset.
Level: 1

Type: ERROR

Impact: Process

DIP-10521: Directory Integration Platform server was not able to locate the current configset.

Cause: Directory Integration Platform Server was not able to locate the current configset {0}.

Action: Check the configset entry in Oracle Internet Directory or MBEAN.
Level: 1

Type: ERROR

Impact: Data

DIP-10523: Directory Integration Platform was not able to retrieve latest changenumber.

Cause: An error occurred when Directory Integration Platform tried to get the last changenumber from Oracle Internet Directory.

Action: Refer to server log.
Level: 1

Type: ERROR

Impact: Data

DIP-10524: Error in parsing last update change number.

Cause: Directory Integration Platform Server was not able to initialize Scheduler Service components.

Action: Refer to server log.
Level: 1

Type: ERROR

Impact: Data

DIP-10526: Error in update operation of current groups

Cause: Directory Integration Platform Server was not able to update the group changes successfully.

Action: Refer to server log.
Level: 1

Type: ERROR

Impact: Data

DIP-10527: Unable to update the changes made in synchronization profile.

Cause: An error occurred while DIP was trying to update the profile job.

Action: Refer to server log.
Level: 1

Type: ERROR

Impact: Data

DIP-10528: Secheduler exception in refreshing profiles {0}

Cause: Directory Integration Platform Server could not refresh provisioning profiles of version 1.0 and 2.0.

Action: Refer to server log.
Level: 1

Type: ERROR

Impact: Data

DIP-10530: Error in deleting profile {0}.

Cause: Directory Integration Platform server was not able to delete profile job.

Action: Refer to server log.
Level: 1

Type: ERROR

Impact: Requests/Responses

DIP-10531: Error in locating the Directory Integration Platform provisioning class.

Cause: Directory Integration Platform Server was not able to look up the provisioning class.

Action: Check if the Directory Integration Platform status of Mbean is up in the Enterprise Manager.
Level: 1

Type: ERROR

Impact: Data

DIP-10532: Error in completing one iteration of provisioning profile.

Cause: Directory Integration Platform Server was not able to comlete execution of provisioning profile.

Action: Refer to server log.
Level: 1

Type: ERROR

Impact: Process

DIP-10533: Error in locating Directory Integration Platform synchronization class.

Cause: Directory Integration Platform Server was not able to look up the synchronization class.

Action: Check if the Directory Integration Platform ProvBean is up in the Enterprise Manager.
Level: 1

Type: ERROR

Impact: Data

DIP-10534: Error in completing one iteration of synchronization profile.

Cause: Directory Integration Platform Server was not able to complete one iteration of synchronization profile.

Action: Refer to server log.
Level: 1

Type: ERROR

Impact: Process

DIP-10544: Scheduler is not able to parse reconciliation time interval : {0}.

Cause: The reconciliation time was in wrong format.

Action: Refer to Directory Integration Platform documentation for required date format.
Level: 1

Type: ERROR

Impact: Data

DIP-10545: Unable to process the profile : {0}.

Cause: The profile entry in the profilestore Oracle Internet Directory has been modified using unauthorized tools.

Action: Set the profile status to enable or disable using the manageSyncProfiles command.
Level: 1

Type: ERROR

Impact: Data

DIP-10546: Scheduler is not able to read profile : {0}.

Cause: The profile has a different version number other than what is supported.

Action: Delete the profile and recreate the profile using the manageSyncProfiles command.
Level: 1

Type: ERROR

Impact: Data

DIP-10547: Error in merging profile attributes {0}.

Cause: The provisioning profile entries were handled using unauthorized tools.

Action: Delete the profile and recreate the profile using the oidProvtool.
Level: 1

Type: ERROR

Impact: Data

DIP-10548: Exception in propagating event : {0}.

Cause: Directory Integration Platform Server was not able to propagate the event successfully.

Action: Refer to server log.
Level: 1

Type: ERROR

Impact: Data

DIP-10549: Directory Integration Platform Server was not able to update the changes made to provisioning profile : {0}.

Cause: An error occurred when Directory Integration Platform was trying to update the profile job.

Action: Refer to server log.
Level: 1

Type: ERROR

Impact: Data

DIP-10550: Error in completing one iteration of reconciliation.

Cause: Directory Integration Platform Server was not able to complete one iteration of reconciliation.

Action: Refer to server log.
Level: 1

Type: ERROR

Impact: Process

DIP-10567: Error in closing scheduler service: {0}.

Cause: Directory Integration Platform Server was not able to close scheduler handles.

Action: Refer to server log.
Level: 1

Type: ERROR

Impact: Configuration

DIP-10568: Profile version not supported {0} : {1}

Cause: Directory Integration Platform Server does not support profile version.

Action: Refer to Directory Integration Platform documentation for valid profile versions.
Level: 1

Type: ERROR

Impact: Data

DIP-10570: Connection to LDAP server failed - Check configuration of DIP server.

Cause: Directory Integration Platform Server was not able to connect to the LDAP server.

Action: Check the Oracle Internet Directory server.
Level: 1

Type: ERROR

Impact: Network

DIP-10581: Directory Integration Platform is not able to get the context with the given details : {0}.

Cause: Error occured in getting the LDAP context.

Action: Check if the registration is proper and Oracle Internet Directory is up and running.
Level: 1

Type: ERROR

Impact: Network

DIP-10585: Directory Integration Platform was not able to execute mapping plugin function : {0}.

Cause: Illegal syntax used while calling mapping plugin function.

Action: Check the mapping rules and correct the syntax of plugin function.
Level: 1

Type: ERROR

Impact: Data

DIP-10586: Error in loading mapping plugin - class not found : {0}.

Cause: Mapping plugin class was not found.

Action: Check the mapping plugin name and check if the mapping plugin class is copied to appropriate location.
Level: 1

Type: ERROR

Impact: Data

DIP-10587: Error in loading mapping plugin : {0}.

Cause: Mapping plugin instantiation has failed.

Action: Check the mapping plugin implementation.
Level: 1

Type: ERROR

Impact: Data

DIP-10588: exception in executing mapping plugin : {0}

Cause: Plugin implementation is not handling the exceptions.

Action: Check the mapping plugin Implementation is having correct entries.
Level: 1

Type: ERROR

Impact: Data

DIP-10599: Errors encountered while starting Directory Integration Platform Scheduler : {0}

Cause: The configset and the group entries could not be retrieved.

Action: Check the configset and profile group entries in Oracle Internet Directory.
Level: 1

Type: ERROR

Impact: Network

DIP-10600: Exception encountered while reconnecting to Oracle Internet Directory.

Cause: Due to some failure in connection to Oracle Internet Directory, the connection was retried. The attempt to reconnect has failed.

Action: No action required.
Level: 1

Type: ERROR

Impact: Network

DIP-10606: Error occurred while shutting down scheduler

Cause: Directory Integration Platform Server was not able to stop the scheduled jobs.

Action: Refer to server log.
Level: 1

Type: ERROR

Impact: Configuration

DIP-10608: error occurred while shutting down scheduler

Cause: Directory Integration Platform Server was not able to write to audit.

Action: Refer to audit logger.
Level: 1

Type: ERROR

Impact: Data

DIP-10622: Key store location not updated or key store not readable.

Cause: Directory Integration Platform Server was not able to locate or read key store.

Action: Make sure key store location is updated and key store is readable.
Level: 1

Type: ERROR

Impact: Data

DIP-10623: Key store password not found in credential store.

Cause: Directory Integration Platform Server was not able to retrive key store password.

Action: Make sure key store password is updated.
Level: 1

Type: ERROR

Impact: Data

DIP-11018: Initialization of the LDIF {0} connector - {0} failed

Cause: The LDIF connector "{0}" could not be initialized.

Action: Check the stack trace or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Files

DIP-11019: Initialization of the Directory Server source connector - {0} to read - {1} failed

Cause: The Directory Server source connector could not be initialized.

Action: Check the stack trace or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Network

DIP-11020: Initialization of the Directory Server source connector {0} failed

Cause: The Directory Server destination connector could not be initialized.

Action: Check the stack trace or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Network

DIP-11021: Error occurred while applying the filter {0}. Ignoring - {1}

Cause: Could not apply the filter.

Action: Check the stack trace or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-11022: Error occurred while reading {0}

Cause: Could not read the entry.

Action: Check the stack trace or contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

DIP-11023: Error occurred while mapping {0}. Ignoring {1}

Cause: Could not map the entry

Action: Check the stack trace or contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Data

DIP-11024: Error occurred while loading {0}. Ignoring {1}

Cause: Could not load the entry

Action: Check the stack trace or contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Data

DIP-11025: Error occurred while writing {0}.

Cause: Could not write the entry

Action: Check the stack trace or contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

DIP-11041: Error in adding user to group

Cause: During bootstrap adding a user to a group that is handled by a plugin fails.

Action: Check the ACI policies in the directory that is bootstrapped.
Level: 1

Type: ERROR

Impact: Data

DIP-11042: Mandatory parameter missing - {0}

Cause: A mandatory attribute is not specified

Action: Specify the following attribute - {0}
Level: 1

Type: ERROR

Impact: Data

DIP-11043: Application name is not specified in the configuration.

Cause: The application name was not specified

Action: Provide an application name
Level: 1

Type: ERROR

Impact: Data

DIP-11044: Error loading the {0} class

Cause: Could not load the class

Action: Check the stack trace for more details
Level: 1

Type: ERROR

Impact: Data

DIP-11045: Error while reading the configuration file

Cause: Could not read the configuration file

Action: Check the stack trace for more details
Level: 1

Type: ERROR

Impact: Files

DIP-11046: Error while cleaning up

Cause: Could not cleanup

Action: Check the stack trace for more details
Level: 1

Type: ERROR

Impact: Data

DIP-11047: Error while connecting to OID

Cause: Could not create the context

Action: Check the stack trace for more details
Level: 1

Type: ERROR

Impact: Network

DIP-20001: Unable to update the status.

Cause: Directory Integration Platform could not update the status as profile name or mode or version is null.

Action: Specify the value for profile name, mode and version.
Level: 1

Type: ERROR

Impact: Data

DIP-20002: Application Distinguished Name is missing from v3 profile.

Cause: Application Distinguished Name was not specified in the profile.

Action: Specify Distinguished Name in the provisioning profile.
Level: 1

Type: ERROR

Impact: Configuration

DIP-20003: Application Globally Unique Identifier(GUID) is missing.

Cause: Application GUID was not specified in the Provisioning Profile.

Action: Specify GUID in provisioning profile.
Level: 1

Type: ERROR

Impact: Configuration

DIP-20004: Organization Globally Unique Identifier(GUID) is missing.

Cause: Organization GUID was not specified in the provisioning profile

Action: Specify Organization GUID in profile
Level: 1

Type: ERROR

Impact: Configuration

DIP-20006: Error occurs while initializing the plugin.

Cause: Exception was thrown while initializing the plugin.

Action: Check the exception trace or Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

DIP-20008: Profile not found while updating the profile status.

Cause: Exception was thrown while updating the profile status.

Action: Check the exception trace or Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Data

DIP-20009: Failed to update the status.

Cause: Directory Integration Platform failed to update the profile Status.

Action: Check the exception trace or Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Data

DIP-20010: Error occurs while initializing the provisioning profile.

Cause: Exception was thrown while initializing the provisioning profile.

Action: Check the exception trace or Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Data

DIP-20033: ProvScheduler is interrupted.

Cause: ProvScheduler is interrupted by another thread.

Action: No action
Level: 1

Type: ERROR

Impact: Threads

DIP-20039: Error occurs while updating profile status.

Cause: Exception thrown while updating profile status.

Action: Check the exception trace or Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Data

DIP-20052: Exception on connecting to DB.

Cause: Directory Integration Platform failed while connecting to database.

Action: Check the database is running properly on the given host and port.
Level: 1

Type: ERROR

Impact: Network

DIP-20053: Exception connecting to DB using service name.

Cause: Directory Integration Platform failed while connecting to DB using the given service name.

Action: Check the service name is proper and it is running or Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Network

DIP-20061: Database configuration information is missing.

Cause: Directory Integration Platform was not able to find the configuration information.

Action: Check if the Database configuration information is provided.
Level: 1

Type: ERROR

Impact: Configuration

DIP-20065: Error occurs while binding arguments for the prepared statement.

Cause: Exception thrown while binding for the prepared statement.

Action: Check the exception trace or Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Requests/Responses

DIP-20066: Error occurs while fetching the next row from the resultset.

Cause: Exception thrown while getting the next row.

Action: Check the exception trace or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Requests/Responses

DIP-20067: Exception occurs while configuring SQL operation.

Cause: Exception thrown while configuring SQL operation.

Action: Check the exception trace or Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Requests/Responses

DIP-20068: Exception occurs while initializing DB reader.

Cause: Exception thrown while initializing DB reader

Action: Check the exception trace or Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

DIP-20069: Exception occurs while forming new change record.

Cause: Exception thrown while forming new change record.

Action: Check the exception trace or Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Data

DIP-20070: Exception occurs while getting column count.

Cause: Exception thrown while reading column count

Action: Check the exception trace or Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Requests/Responses

DIP-20071: Exception occurs while getting query metadata.

Cause: Exception thrown while getting query metadata.

Action: Check the exception trace or Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Data

DIP-20072: Exception while preparing the SQL statement.

Cause: Exception thrown while preparing the SQL statement.

Action: Check the exception trace or Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Requests/Responses

DIP-20073: Exception occurs during query execution.

Cause: Exception thrown while executing a auery.

Action: Check the exception trace or Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Data

DIP-20074: Could not find the key {0} in key array.

Cause: Corruption in the profile attribute that stores the last ChangeKey for sync from DB.

Action: Look at the last ChangeKey value in the profile using the Profile Manager and set it to the timestamp from when the changes need to be synchronized.
Level: 1

Type: ERROR

Impact: Requests/Responses

DIP-20080: Key values are not compliant with keys.

Cause: Key value was not compliant with key.

Action: Check the key value or Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Data

DIP-20084: Missing attribute list in MapInfo

Cause: Attribute list is missing in MapInfo.

Action: Check the mapping information
Level: 1

Type: ERROR

Impact: Data

DIP-20085: ChangeKey attribute is not found in profile.

Cause: Directory Integration Platform was not able to find ChangeKey attribute value in profile.

Action: Check the ChangeKey attribute is present in the Profile.
Level: 1

Type: ERROR

Impact: Configuration

DIP-20086: ChangeKey attribute value is not found in profile.

Cause: DIP was not able to find the changekey attribute value in profile.

Action: Check the ChangeKey attribute value present in profile.
Level: 1

Type: ERROR

Impact: Configuration

DIP-20094: Error occurs while getting the bind variables.

Cause: Exception was thrown while getting the bind attributes.

Action: Check the exception trace or Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Data

DIP-20095: Error while creating statement object.

Cause: Exception thrown while creating statement object

Action: Check the exception trace or Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Data

DIP-20096: Database Driver or Source Error Code : {0}

Cause: Exception thrown while getting driver information.

Action: Check the exception trace or Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Network

DIP-20097: Error occurs while deleting from the table : {0}.

Cause: Directory Integration Platform failed when it tries to delete from the table.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Data

DIP-20101: Invalid argument format for attribute: {0}.

Cause: Attribute {0} was not in proper format.

Action: Give attribute argument format in proper format.
Level: 1

Type: ERROR

Impact: Data

DIP-20102: Operation type {0} is not valid.

Cause: An invalid operation type was specified.

Action: Specify a valid operation type.
Level: 1

Type: ERROR

Impact: Data

DIP-20110: Value for attribute: {0} not found in change record.

Cause: Value of attribute {0} was not found in the change record.

Action: Check the attribute value is present or Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Data

DIP-20123: Failed to open file for writing : {0}

Cause: Directory Integration Platform (DIP) failed to create a file for writing.

Action: Check DIP has permission to create a file or enough disk space for file.
Level: 1

Type: ERROR

Impact: Files

DIP-20127: Error while creating callable statement object.

Cause: Exception thrown while creating callable statement object.

Action: Check the exception trace or Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Requests/Responses

DIP-20128: Events received ( {0} ), and Event Status events being sent back ( {1} ) are not same. Errors are encountered.

Cause: Event index and number of events were not same.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Data

DIP-20130: Error occurs while propagating event status.

Cause: Exception thrown while propagating event status.

Action: Check the exception trace or Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Data

DIP-20138: Error occurs while reading an event.

Cause: Exception thrown while reading an event.

Action: Check the exception trace or Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Data

DIP-20139: Error occurs while searching for more events.

Cause: Exception thrown while searching for more events.

Action: Check the exception trace or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-20141: Error occurs while fetching the next Change Record.

Cause: Exception is thrown while fetching the next Change Record.

Action: Check the exception trace or Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Data

DIP-20161: Error occurs while creating event from change.

Cause: Exception thrown while creating event from change.

Action: Check the exception trace or Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Data

DIP-20162: Error occurs while propagating events.

Cause: Exception thrown while propagating events.

Action: Check the exception trace or Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Requests/Responses

DIP-20166: Exception occurs while adding or sending an event.

Cause: Exception thrown while sending or adding an event.

Action: Check the exception trace or Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Requests/Responses

DIP-20186: Insufficient privileges to read application user information.

Cause: Directory Integration Platform (DIP) does not have permission to read application user information.

Action: Check that Directory Integration Platform has permission to read the application user information.
Level: 1

Type: ERROR

Impact: Security

DIP-20193: Error occurs while propagating event {0} for ObjectGUID {1} for ObjectName {2}.

Cause: Exception thrown while propagating event.

Action: Check the exception trace or Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Data

DIP-20194: Not able to delete the user.

Cause: Directory Integration Platform (DIP) failed while deleting the user.

Action: Check that DIP has permission to delete a user or Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Data

DIP-20199: SQLException : {0} {1}

Cause: Exception thrown while performing SQL operation.

Action: Check the exception trace or Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Data

DIP-20200: Error occurs while preparing status update.

Cause: Exception thrown while preparing status update.

Action: Check the exception trace or Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Data

DIP-20225: Error retrieving user create base from mappings.

Cause: User create base was not specified.

Action: Check if user create base is specified.
Level: 1

Type: ERROR

Impact: Data

DIP-20226: Error occurs while modifying identity.

Cause: Exception thrown while modifying identity.

Action: Check the exception trace or Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Data

DIP-20227: Exception occurs while creating identity ( {0} ).

Cause: Exception thrown while creating identity.

Action: Check the exception trace or Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Data

DIP-20228: Exception occurs while processing event.

Cause: Exception thrown while processing event.

Action: Check the exception trace or Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Data

DIP-20229: Exception in setting up subscription information.

Cause: Exception thrown while setting up subscription information.

Action: Check the exception trace or contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Data

DIP-20230: Event type {0} is unknown.

Cause: Event type was unknown.

Action: Check the event type.
Level: 1

Type: ERROR

Impact: Data

DIP-20231: Event ID and Status Event ID mismatches

Cause: Event ID and Event Status ID were not same.

Action: Contact Oracle Support Services
Level: 1

Type: INTERNAL_ERROR

Impact: Data

DIP-20232: Util Exception occurs while searching identity : {0}.

Cause: Exception thrown while searching for identity.

Action: Check the exception trace or Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Data

DIP-20259: Insufficient privileges to read the base user information.

Cause: Insufficient Privileges to read the base user information.

Action: The application user defined in the 'applicationdn' of the profile doesn't have privileges to read the users in the 'usersearchbase'. Set the privileges accordingly.
Level: 1

Type: ERROR

Impact: Data

DIP-20262: Failed to add rule : {0}.

Cause: Directory Integration Platform Server was not able to parse the event mapping rules for the provisioning profile.

Action: Correct the event mapping rules for the provisioning profile.
Level: 1

Type: ERROR

Impact: Data

DIP-20264: Event is null.

Cause: The event to which the status needs to be set found null.

Action: No action required. If the status is not set for a event, the provisioning action will be retried.
Level: 1

Type: ERROR

Impact: Data

DIP-20265: Exception while processing the event.

Cause: Exception thrown while processing event.

Action: Check the exception trace or Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Data

DIP-20274: Error occurs while initializing ProvAppToOIDSync.

Cause: Exception thrown while initializing ProvAppToOIDSync.

Action: Check the exception trace or Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Data

DIP-20307: Exception in filter processing

Cause: Exception was thrown while processing the filter.

Action: Check the exception trace for more information or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-20318: Exception in filter processing

Cause: Exception was thrown while processing filter.

Action: Check the exception trace for more information or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-20323: Error while processing next change From Oracle Internet Directory

Cause: Exception was thrown while processing the next change from Oracle Internet Directory.

Action: Check the exception trace for more information or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-20324: Error while reading next change from Oracle Internet Directory

Cause: Exception was thrown while reading next change from Oracle Internet Directory.

Action: Check the exception trace for more information or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-20325: Error while processing ADD operation

Cause: Directory Integration Platform was failing while adding an entry.

Action: Check if the entry is in proper format.
Level: 1

Type: ERROR

Impact: Data

DIP-20326: Error while processing MODIFY operation

Cause: Directory Integration Platform was failing while modifying an entry

Action: Check the entry is in proper format
Level: 1

Type: ERROR

Impact: Data

DIP-20343: Error while fetching next change.

Cause: Reading the change for provisioning has failed.

Action: The change will be read during next iteration.
Level: 1

Type: ERROR

Impact: Data

DIP-20344: Error while adding provisioning event for sending

Cause: Exception was thrown while adding provisioning event.

Action: Check the exception trace for more information or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-20345: Error while initializing ProvPLSQLWriter

Cause: Exception was thrown while initializing ProvPLSQLWriter.

Action: Check the exception trace for more information or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

DIP-20348: Error while searching tombstone

Cause: Directory Integration Platform has failed while searching Tombstone in ProvReader.

Action: Check the exception trace for more information or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-20349: Exception in getting change from Oracle Internet Direcotory

Cause: Exception was thrown while getting change from Oracle Internet Direcotory in ProvReader.

Action: Check the exception trace for more information or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-20350: Exception in next change from Oracle Internet Directory

Cause: ODI Exception was thrown while getting next change from Oracle Internet Directory.

Action: Check the exception trace for more information or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-20361: Error while notifying event

Cause: Exception was thrown while notifying event.

Action: Check the exception trace for more information or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Requests/Responses

DIP-20362: Exception in event notification

Cause: Exception was thrown while notifying an event.

Action: Check the exception trace for more information or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Requests/Responses

DIP-20363: Exception in initialization

Cause: Exception is thrown while initializing the ProvWriter.

Action: Check the exception trace for more information or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

DIP-20364: Exception in user group lookup or event propagation

Cause: Exception was thrown while looking up for user or group.

Action: Check the exception trace for more information or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-20365: Unsupported interface type : {0}

Cause: Given interface type is not supported by Directory Integration Platform.

Action: Check if the interface type is specified properly.
Level: 1

Type: ERROR

Impact: Data

DIP-20375: Exception creating group

Cause: Directory Integration Platform failed while creating a group.

Action: Check the exception trace for more information or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-20376: Exception while creating identity ( {0} )

Cause: Directory Integration Platform has failed while creating the identity.

Action: Check the exception trace for more information or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-20378: Exception getting user attributes

Cause: Directory Integration Platform has failed while trying to access user attributes.

Action: Check the exception trace for more information or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-20379: Exception during MODRDN operation

Cause: Directory Integration Platform has failed while performing modRDN operation.

Action: Check the exception trace for more information or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-20380: Exception sending event

Cause: Exception was thrown while sending event.

Action: Check if the application is running properly.
Level: 1

Type: ERROR

Impact: Requests/Responses

DIP-20381: Exception subscribing identity ( {0} ) {1}

Cause: Exception was thrown when Directory Integration Platform subscribed to the identity.

Action: Check the exception trace for more information or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-20382: Exception un-subscribing identity ( {0} ) {1}

Cause: Exception was thrown when Directory Integration Platform tried to un-subscribe the identity.

Action: Check the exception trace for more information or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-20383: Exception sending event

Cause: ODI exception is thrown while sending the event.

Action: Check if the application is running properly or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Requests/Responses

DIP-20384: Exception creating group ( {0} ) : {1}

Cause: Util exception was thrown while creating the group.

Action: Check the exception trace for more information or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-20385: Exception deleting identity : {0}

Cause: Util exception was thrown while deleting the identity.

Action: Check the exception trace for more information or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-20386: Exception deleting identity :

Cause: Util exception was thrown while deleting the identity.

Action: Check the exception trace for more information or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-20387: Exception deleting group

Cause: Util exception was thrown while deleting the group.

Action: Check the exception trace for more information or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-20388: Exception modifying identity : {0}

Cause: Util exception was thrown while modifying the identity.

Action: Check the exception trace for more information or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-20389: Exception modifying group

Cause: Util exception was thrown while modifying the group.

Action: Check the exception trace for more information or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-20390: Exception searching group : {0}

Cause: Util exception was thrown when searching for the group {0}.

Action: Check the exception trace for more information or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-20391: Exception subscribing to identity : {0}

Cause: Util exception was thrown when subscribing to the identity.

Action: Check the exception trace for more information or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-20392: Exception un-subscribing identity : {0}

Cause: Util exception was thrown when un-subscribing the identity.

Action: Check the exception trace for more information or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-20394: Error modifying identity - identity not found : {0}

Cause: Directory Integration Platform tried to modify an identity that did not exist.

Action: Verify that the identity exists. If it does not, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-20408: error deleting Identity : {0}

Cause: Exception was thrown while deleting an identity.

Action: Check the exception trace for more information or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-20409: error subscribing identity - identity to be subscribed not found : {0}

Cause: Exception was thrown while subscribing identity.

Action: Check the exception trace for more information or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-20412: error un-subscribing identity - identity to be un-subscribed not found : {0}

Cause: Exception was thrown while un-subscribing identity

Action: Verify that the identity exists or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-20421: ignoring invalid {0} : {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Data

DIP-20422: ignoring GROUP_ADD event with no attributes

Cause: Invalid group add event was sent by the application.

Action: Check the application event generation mechanism.
Level: 1

Type: ERROR

Impact: Data

DIP-20425: error modifying group - group not found : {0}

Cause: Directory Integration Platform tried to modify a group which did not exist.

Action: Check if group exists. If not, then contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Data

DIP-20430: exception modifying group

Cause: Directory Integration Platform fails when it tried to modify a group.

Action: Check the exception trace for more information or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-20431: error deleting group - group not found : {0}

Cause: Directory Integration Platform tried to delete a group that did not exist.

Action: Verify that the group exists or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-20433: error deleting group

Cause: Exception was thrown while deleting a group.

Action: Check the exception trace for more information or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-20447: error initializing ProvOIDToAppSync

Cause: Exception was thrown while initializing ProvOIDToAppSync.

Action: Check the exception trace for more information or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-20453: obtaining LDAP connection failed in attempt number :{0} - Retrying

Cause:

Action:
Level: 1

Type: WARNING

Impact:

DIP-20454: maximum LDAP connection retry count reached

Cause:

Action:
Level: 1

Type: WARNING

Impact:

DIP-20455: an error occured while retrieving the changenumber

Cause: An error occurred when DIP tried to get the last changenumber from Oracle Internet Directory.

Action: Refer to server log and trace files.
Level: 1

Type: ERROR

Impact:

DIP-20456: an error occured in opening the Control file

Cause: An error occurred while opening the control file.

Action: Ensure that the file is available and that no other applications are using the same.
Level: 1

Type: ERROR

Impact:

DIP-20457: an error occured in reading the Control file

Cause: An error occurred while opening the control file.

Action: Ensure that the file is available and that no other applications are using the same.
Level: 1

Type: ERROR

Impact:

DIP-20458: The DN does not exist in the connected directory.

Cause: The DN being processed was not found in the connected directory.

Action: Verify that the data is in a consistent state.
Level: 1

Type: ERROR

Impact:

DIP-20459: The Event Plugin was not initialized properly.

Cause: The Event Plugin configuration might be incorrect.

Action: Verify that the profile and plugin are compatible.
Level: 1

Type: ERROR

Impact:

DIP-20460: An Error occured while setting LDAP host :{0}, port :{1}.

Cause: The LDAP host and port could not be set.

Action: Check the host and port setting and LDAP availability.
Level: 1

Type: ERROR

Impact:

DIP-20462: Directory Integration Platform MBean Registration has failed

Cause: The Application server did not initialize itself correctly or the Directory Integration Platform configuration is incorrect.

Action: Check the Application server and Directory Integration Platform logs.
Level: 1

Type: ERROR

Impact:

DIP-20463: Directory Integration Platform Runtime MBean Registration has failed

Cause: The Application server did not initialize itself correctly or the DIP configuration is incorrect.

Action: Check the Application server and Directory Integration Platform logs.
Level: 1

Type: ERROR

Impact:

DIP-30001: Exception while removing unwanted attributes.

Cause: Exception is thrown while removing attribute from the attribute list after checking that attribute is required or not

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-30003: Exception while printing attributes.

Cause: Exception is thrown while printing attributes and its value

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-30004: Nickname attribute is not found Default nickname attribute = uid

Cause: Nick name attribute is not found

Action: Setting it to default value
Level: 1

Type: ERROR

Impact: Data

DIP-30013: Exception in getting event

Cause: Exception is thrown while reading the event

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-30028: Exception while setting Provisioning policies.

Cause: Exception is thrown while adding rule in the set of event rule

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-30044: Exception while searching in Tombstone.

Cause: Exception is thrown while searching entries in Tombstone.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-30048: Error in updating the entry status

Cause: Exception is thrown while updating the event status

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-30056: Exception in filtering the entry

Cause: Exception is thrown while filtering out the events

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-52706: Key store file is not existing or it is not readable.

Cause: Directory Integration Platform Server was not able to locate or read key store.

Action: Make sure key store file is existing and readable.
Level: 1

Type: ERROR

Impact: Data

DIP-60001: The Sensor {0} was not found.

Cause: The DIP tried to access a Metrics sensor that doesn't exist.

Action: Create a Bug against DIP.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

DIP-60002: The following DMS Noun could not be created: {0}.

Cause: The DIP tried to create a Metrics Noun but the provided Noun Path is invalid.

Action: Create a Bug against DIP.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

DIP-60003: The following DMS Noun was not found in DMS: {0}

Cause: The DIP tried to access a Metrics Noun that doesn't exist.

Action: Create a Bug against DIP.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

DIP-60004: The Default Sensor Array is invalid.

Cause: The DIP tried to create the default Metrics sensors, but failed. The Metrics default array is invalid.

Action: Create a Bug against DIP.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

DIP-60005: The following DMS Sensor failed to create: {0}

Cause: The DIP failed to create a Metrics sensor, probably because of a wrong Noun Path.

Action: Create a Bug against DIP.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

DIP-60006: Failed to delete/destroy the Sensor hierarchy for profile: {0}

Cause: The DIP tried to delete several Metrics sensors but failed, probably because of invalid Noun Paths.

Action: Create a Bug against DIP.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

DIP-80001: Exception while connecting to directory server.

Cause: Directory Integration Platform tried to get a connection to the directory server, but failed.

Action: Check the connection details and credentials, also check whether the directory server is running.
Level: 1

Type: ERROR

Impact: Network

DIP-80002: Exception while populating the server config: {0}.

Cause: Directory Integration Platform tried to access a server configset, but failed.

Action: Specify a correct server configset number.
Level: 1

Type: ERROR

Impact: Data

DIP-80003: Exception while retrieving server configset.

Cause: Directory Integration Platform tried to get all server configset, but failed.

Action: Contact administrator or Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-80004: Exception while storing configset: {0}.

Cause: Directory Integration Platform tried to store the server configset, but failed.

Action: Contact administrator or Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-80005: Exception while creating configset: {0}.

Cause: Directory Integration Platform tried to create a new server configset, but failed.

Action: Contact administrator or Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-80006: Exception while deleting configset: {0}.

Cause: Directory Integration Platform tried to delete a server configset, probably because of wrong configset number.

Action: Contact administrator or Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-80007: Exception while retrieving configset: {0}.

Cause: Directory Integration Platform tried to locate a server configset, probably because of wrong configset.

Action: Contact administrator or Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-80008: Exception while deleting a profile group {1} from configset {0}.

Cause: Directory Integration Platform tried to delete a profile group, but failed.

Action: Contact administrator or Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-80009: Exception while retrieving default configset.

Cause: Directory Integration Platform tried to get default server configset, but failed.

Action: Contact administrator or Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-80010: Exception while updating default configset.

Cause: Directory Integration Platform tried to set default server configset, but failed.

Action: Contact administrator or Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-80101: Directory meta data does not exists in persistent data store.

Cause: Directory Integration Platform tried to populate a directory meta data which does not exist.

Action: Specify a correct directory name.
Level: 1

Type: ERROR

Impact: Data

DIP-80102: Exception while retrieving directory meta data.

Cause: Directory Integration Platform tried to populate a directory meta data, but failed.

Action: Contact administrator or Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-80103: Exception while retrieving operational or special attributes.

Cause: Directory Integration Platform tried to get operational or special attributes, but failed.

Action: Contact administrator or Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-80104: Exception while adding operational attributes.

Cause: Directory Integration Platform tried to add operational attributes, probably because wrong directory name has specified.

Action: Contact administrator or Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-80105: Exception while checking whether an attribute is operational or not.

Cause: Directory Integration Platform tried to check whether an attribute is operational or not, probably because wrong directory name has specified.

Action: Contact administrator or Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-80106: Exception while deleting operational attribute from persistent data store.

Cause: Directory Integration Platform tried to delete an operational attributes, but failed.

Action: Contact administrator or Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-80107: Exception while deleting operational attribute from persistent data store.

Cause: Directory Integration Platform tried to delete an operational attributes which does not exists in specified directory meta -data.

Action: Specify a correct attribute name.
Level: 1

Type: ERROR

Impact: Data

DIP-80201: failed to connect to directory server

Cause: Directory Integration Platform failed to connect directory server with given details.

Action: Check the directory server connection details.
Level: 1

Type: ERROR

Impact: Network

DIP-80202: Error in reading provisioning profiles.

Cause: Directory Integration Platform failed to search the directory server for provisioning profiles.

Action: Check the directory server connection details and the provisioning profile containers.
Level: 1

Type: ERROR

Impact: Data

DIP-80203: Error in reading attributes of provisioning profile {0}.

Cause: Directory Integration Platform failed to find provisioning profile in directory server.

Action: Check the directory server connection details and the provisioning profile.
Level: 1

Type: ERROR

Impact: Data

DIP-80204: Error in reading attribute {0} of provisioning profile {1}.

Cause: Directory Integration Platform failed to find attribute.

Action: Check the directory server connection details and the provisioning profile.
Level: 1

Type: ERROR

Impact: Data

DIP-80205: Exception while deleting provisioning profile {0}.

Cause: Directory Integration Platform failed to delete the provisioning profile either for insufficient access or invalid profile name or invalid connection details.

Action: Check the directory server connection details and the provisioning profile.
Level: 1

Type: ERROR

Impact: Data

DIP-80206: Exception while modifying provisioning profile {0}.

Cause: Directory Integration Platform failed to modify the provisioning profile either for insufficient access or invalid profile name or invalid connection details.

Action: Check the directory server connection details and the provisioning profile.
Level: 1

Type: ERROR

Impact: Data

DIP-80207: Failed to modify provisioning profile {0}. Modifying the attribute {1} is not supported for provisioning profile {0} with version {2}.

Cause: Modifying the attribute is not supported for this version of provisioning profile.

Action: Check for provisioning profile version.
Level: 1

Type: ERROR

Impact: Data

DIP-80208: Filename is mandatory parameter for bulkprov :{0}.

Cause: Filename was found missing for bulkprov operation.

Action: Provide a valid ldif file for bulkprov operation.
Level: 1

Type: ERROR

Impact: Data

DIP-81001: Exception while adding connector group in directory server {0}.

Cause: Directory Integration Platform tried to add a new connector group but failed, probably because this connector group already exists.

Action: Specify a correct connector group.
Level: 1

Type: ERROR

Impact: Data

DIP-81002: Exception while renaming connector group {0} to {1}.

Cause: Directory Integration Platform tried to rename a connector group but failed, probably because this connector group does not exist.

Action: Specify a correct connector group or check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Data

DIP-81003: Exception while deleting connector group in directory server {0}.

Cause: Directory Integration Platform tried to delete a connector group but failed, probably because this connector group does not exist.

Action: Specify a correct connector group.
Level: 1

Type: ERROR

Impact: Data

DIP-81004: Exception while retrieving connector group from profile.

Cause: Directory Integration Platform tried to get all the connector groups from Oracle Internet Directory but failed.

Action: Contact administrator or Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-81008: Exception while retrieving list of all unassociated profiles.

Cause: Directory Integration Platform tried to get the list of unassociated profiles from Oracle Internet Directory, but failed

Action: Contact administrator or Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-81012: Exception while retrieving profile Distinguished Name.

Cause: Directory Integration Platform tried to get profile DN, but failed.

Action: Contact administrator or Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-81013: Exception while retrieving profile container.

Cause: Directory Integration Platform tried to get profile container, but failed

Action: Contact administrator or Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-85001: Error connecting to the directory server.

Cause: Directory Integration Platform tried to connect to the directory server, but failed.

Action: Check the connection details and the credentials. Also check if the directory server is running.
Level: 1

Type: ERROR

Impact: Network

DIP-85002: Exception while retrieving profile name {0}.

Cause: Directory Integration Platform failed to find the profile in Oracle Internet Directory.

Action: Check if the profile name is correct and the profile exists.
Level: 1

Type: ERROR

Impact: Data

DIP-85003: Error retrieving attributes from the directory server.

Cause: Directory Integration Platform failed to retrieve the profile attributes from the directory server.

Action: Check the stack trace for the exact error.
Level: 1

Type: ERROR

Impact: Data

DIP-85004: Error occurred while writing the attribute to the directory server

Cause: Directory Integration Platform failed to save the attribute value.

Action: Check the stack trace for the exact error.
Level: 1

Type: ERROR

Impact: Data

DIP-85008: The profile {0} already exists.

Cause: A profile with the same name as the profile being created already exists.

Action: Delete the existing profile or select a different name for the new profile.
Level: 1

Type: ERROR

Impact: Data

DIP-85009: The profile name is invalid.

Cause: The DN formed for the profile was not valid.

Action: Contact administrator or Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-85010: Exception while creating the synchronization profile.

Cause: Directory Integration Platform failed to create the synchronization profile.

Action: Contact administrator or Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-85011: Exception while deleting the profile.

Cause: Directory Integration Platform failed to delete the profile.

Action: Contact administrator or Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-85012: cannot retrieve value for attribute {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Data

DIP-85013: cannot construct DN for the profile

Cause:

Action:
Level: 1

Type: WARNING

Impact: Data

DIP-85014: Exception while updating the profile last applied change number.

Cause: Directory Integration Platform failed to update last applied change number for the profile.

Action: Contact administrator or Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-85015: Exception while retrieving bootstrap attributes.

Cause: Directory Integration Platform failed to get bootstrap attributes.

Action: Contact administrator or Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-85016: profile already associated to ODIP group

Cause:

Action:
Level: 1

Type: WARNING

Impact: Data

DIP-85019: Exception while performing bootstrap operation.

Cause: Directory Integration Platform failed to perfrom the bootstrap operation.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Data

DIP-85031: Exception while creating subset criteria.

Cause: Directory Integration Platform failed to create the subset criteria.

Action: Contact administrator or Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-85032: Exception while updating bootstrap status.

Cause: Directory Integration Platform failed to update the bootstrap status.

Action: Contact administrator or Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-85033: The profile is not valid.

Cause: The validation of the profile indicated invalid values for some attributes.

Action: Update the profile with proper values.
Level: 1

Type: ERROR

Impact: Data

DIP-85034: Exception while setting up the external authentication plug-in.

Cause: Directory Integration Platform failed to set up the external authentication plug-in.

Action: Check the stack trace for more details
Level: 1

Type: ERROR

Impact: Configuration

DIP-85035: Exception while setting up credential store key for pre 4.0 profiles.

Cause: Directory Integration Platform failed to set a credential store key for a pre-4.0 profile.

Action: Set the user account and the password in the profile.
Level: 1

Type: ERROR

Impact: Configuration

DIP-85036: Exception while retrieving credential store key for pre 4.0 profiles.

Cause: Directory Integration Platform failed to retrive a credential store key from a pre-4.0 profile.

Action: Get the user account and the password from the profile.
Level: 1

Type: ERROR

Impact: Configuration

DIP-85041: Incorrect type of external directory specified.

Cause: The specified directory was not supported.

Action: Specify supported directory.
Level: 1

Type: ERROR

Impact: Data

DIP-85042: Exception while updating the directory server.

Cause: Directory Integration Platform failed to update the directory server.

Action: Contact administrator or Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-85044: Exception while retrieving plugin configuration entries.

Cause: Directory Integration Platform failed to find the plugin configuration entries.

Action: Check the stack trace for more details or contact the LDAP administrator
Level: 1

Type: ERROR

Impact: Configuration

DIP-85045: Unrecognized property - {0}.

Cause: The specified property was not supported.

Action: Specify a valid property to be set or modified.
Level: 1

Type: ERROR

Impact: Data

DIP-85046: Exception while deleting invalid profile - {0}.

Cause: The profile is invalid and was created in directory server, but could not be deleted from after validation.

Action: Manually delete the invalid profile and try creating it again.
Level: 1

Type: ERROR

Impact: Data

DIP-85047: Exception while retrieving synchronization profile container.

Cause: Directory Integration Platform tried to get sync profile container, but failed.

Action: Check the exception stack trace for more details.
Level: 1

Type: ERROR

Impact: Data

DIP-85048: The value for property '{0}' cannot be null.

Cause: An attribute was being set with a null value.

Action: Specify a non null legal value when setting an attribute.
Level: 1

Type: ERROR

Impact: Data

DIP-85049: An unexpected exception encountered.

Cause: Directory Integration Platform failed to perform the operation.

Action: Contact administrator or Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-85050: No value found in profile {0} for attribute "{1}".

Cause: The value for required attribute was not set.

Action: Set a value for the missing attribute.
Level: 1

Type: ERROR

Impact: Data

DIP-85051: Incorrect associated profile name {0} provided.

Cause: This profile cannot be set as associated profile for the current profile.

Action: Use profile with proper synchronization mode and connected directory type.
Level: 1

Type: ERROR

Impact: Data

DIP-85052: Exception while retrieving profile.

Cause: Either profile name is incorrect or profile does not exists in the directory server.

Action: Contact administrator or Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-85085: The property {0} cannot be updated using this operation, and will be ignored.

Cause: A property which is cannot be updated was passed to the operation.

Action: Look at the docs to see how this property can be modified.
Level: 1

Type: ERROR

Impact: Data

DIP-85086: Invalid value specified for provisioning profile attribute "orclodipinterfaceconnectinformation".

Cause: The provisioning profile attribute "orclodipinterfaceaccountinformation" was specified with incorrect syntax.

Action: Make sure that the profiles conform to the syntax specified.
Level: 1

Type: ERROR

Impact: Data

DIP-85089: Authentication fails for user {0}.

Cause: Authentication failed for user {0}.

Action: Check the user credentials.
Level: 1

Type: ERROR

Impact: Data

DIP-85090: Access denied for java key store.

Cause: Directory Integration Platform failed to access java key store for insufficient permissions.

Action: Check for java key store permissions.
Level: 1

Type: ERROR

Impact: Data

DIP-85091: Directory service unavailable at {0}:{1}

Cause: Service was unavailable at {0}:{1}

Action: Check for given host and port details.
Level: 1

Type: ERROR

Impact: Data

DIP-85092: update Change number may not have succeeded on profile creation

Cause: The connected directory server may have been down.

Action: Check the connected directory server, and try again using manageSyncProfiles updatechgnum opertaion.
Level: 1

Type: ERROR

Impact: Data

DIP-85093: profile store operation encountered some exceptions, check logs.

Cause: The profile have encountered validation or other issues while being stored.

Action: Check the logs and profile for more details.
Level: 1

Type: ERROR

Impact: Data

DIP-85094: validation of the profile indicated invalid values for some attributes

Cause: The validation of the profile indicated invalid values for some attributes.

Action: Check the values of the attributes and update the profile with correct values before activating it.
Level: 1

Type: ERROR

Impact: Data

DIP-85095: validation of the profile indicated invalid values for mapping rules or some other attributes.

Cause: The validation of the profile indicated invalid values for mapping rules or some other attributes.

Action: Update the profile with correct mapping rules and/or correct values of the attributes before activating it.
Level: 1

Type: ERROR

Impact: Data

DIP-85096: cannot connect directory server at {0} : {1}

Cause: Directory Integration Platform failed to connect the directory server at {0} : {1}

Action: Check the server host and port details.
Level: 1

Type: ERROR

Impact: Data

DIP-85097: unable to connect to Oracle Internet Directory.

Cause: Directory Integration Platform failed to connect to Oracle Internet Directory.

Action: Check the Oracle Internet Directory server details.
Level: 1

Type: ERROR

Impact: Data

DIP-85102: Mandatory profile property "{0}" missing.

Cause: Directory Integration Platform failed to find mandatory profile property.

Action: Provide required profile property.
Level: 1

Type: ERROR

Impact: Data

DIP-85103: Error while parsing map rules for exclusion rules.

Cause: Directory Integration Platform failed to parse map exclusion rules.

Action: Contact administrator or Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

DIP-85104: The username value entered is invalid.

Cause: The username value entered is invalid.

Action: Ensure that it does not contain white spaces.
Level: 1

Type: ERROR

Impact: Data

DIP-85105: The password value entered is invalid.

Cause: The password value entered was invalid.

Action: Provide a legal value for password.
Level: 1

Type: ERROR

Impact: Data

DIP-85106: The SSL setting value entered is invalid.

Cause: The SSL setting value entered is invalid.

Action: Ensure that it is an integer less than or equals 2.
Level: 1

Type: ERROR

Impact: Data

DIP-85107: The profile {0} is associated to other profile(s).

Cause: Directory Integration Platform failed to delete the profile because it is associated to other profile(s).

Action: Dissociate the profile to other profile(s) to deregister.
Level: 1

Type: ERROR

Impact: Data

DIP-85108: Key store location not updated or key store not readable.

Cause: Directory Integration Platform Server was not able to locate or read key store.

Action: Make sure key store location is updated and key store is readable.
Level: 1

Type: ERROR

Impact: Data

DIP-85109: Key store password not found in credential store.

Cause: Directory Integration Platform Server was not able to retrive key store password.

Action: Make sure key store password is updated.
Level: 1

Type: ERROR

Impact: Data

DIP-85110: Profile {0} is already activated. Hence the profile is not scheduled for test.

Cause: Directory Integration Platform failed to schedule the profile for test because it is already activated.

Action: Deactivate the profile to schedule the profile for test.
Level: 1

Type: ERROR

Impact: Data

DIP-86000: all arguments passed is null

Cause: No arguments passed.

Action: Pass all the required arguments.
Level: 1

Type: ERROR

Impact: Data

DIP-86001: parameter passed is null

Cause: Argument or their values passed were null.

Action: Arguments passed cannot be null, pass the required values.
Level: 1

Type: ERROR

Impact: Data

DIP-86002: failed to setup the destination host

Cause: Directory Integration Platform failed to setup the destination host.

Action: Check the destination host and port settings.
Level: 1

Type: ERROR

Impact: Network

DIP-86003: invalid credentials or, host and port settings

Cause: Directory Integration Platform failed to connect destination with given connection details.

Action: Check the credentials for destination connection details.
Level: 1

Type: ERROR

Impact: Network

DIP-86004: invalid credentials or host-port details for connected directory

Cause: Required connected directory details are not provided.

Action: Make sure you provide proper details for connected directory.
Level: 1

Type: ERROR

Impact: Network

DIP-86005: cannot find the default container

Cause: Directory Integration Platform failed to find default {0} container.

Action: Check if the default container exists or create the default container.
Level: 1

Type: ERROR

Impact: Data

DIP-86006: cannot find the value of default container

Cause: Directory Integration Platform failed to find value for default {0} container.

Action: Check the value for default container.
Level: 1

Type: ERROR

Impact: Data

DIP-86007: parameter value is null

Cause: The value for attribute {0} was missing.

Action: Check value for the parameter, it cannot be null.
Level: 1

Type: ERROR

Impact: Data

DIP-86008: parameter name not found

Cause: Directory Integration Platform failed to find the parameter {0}.

Action: Check the parameter name.
Level: 1

Type: ERROR

Impact: Data

DIP-86009: cannot create a profile from template profile

Cause: Directory Integration Platform failed to create the profile from the template profile.

Action: Check if template profile exists
Level: 1

Type: ERROR

Impact: Data

DIP-86010: cannot associate profile with the profile group

Cause: Directory Integration Platform failed to associate profile with group.

Action: Check the profile group name to which the profile will be added exists.
Level: 1

Type: ERROR

Impact: Data

DIP-87000: cannot initialize the schema

Cause: Directory Integration Platform encountered an exception while initializing the schema.

Action: Check the stack trace for more details
Level: 1

Type: ERROR

Impact: Data

DIP-87001: cannot get the directory server context

Cause: Directory Integration Platform encountered an exception while getting the directory server context.

Action: Check the stack trace for more details
Level: 1

Type: ERROR

Impact: Network

DIP-87002: Exception while getting the connected directory context.

Cause: Directory Integration Platform failed to obtain the connected directory context.

Action: Check the stack trace for more details
Level: 1

Type: ERROR

Impact: Network

29 DISCMAN-00100 to DISCMAN-90001

DISCMAN-00100: Invalid input parameter.

Cause: Error encountered while processing input parameter.

Action: Check if input parameter is correct.
Level: 32

Type: ERROR

Impact:

DISCMAN-00101: Invalid {0} input parameter.

Cause: Error encountered while processing input parameter.

Action: Check if input parameter is correct.
Level: 32

Type: ERROR

Impact:

DISCMAN-10001: ODL message for id ={0} isn't found. "ODL" is "Oracle Diagnostic Logging"

Cause: Failed to get error message by id.

Action: Update client version.
Level: 32

Type: ERROR

Impact:

DISCMAN-10003: Full mapping fact is not found, id={0}

Cause: Selected item is inconsistent.

Action: Reload client and try again.
Level: 32

Type: ERROR

Impact:

DISCMAN-10004: Instance Preview (US GAAP taxonomy used: {0}; Use SEC viewer: {1}) {0}, {1} are true or false values; "US GAAP" is "Generally Accepted Accounting Principles (United States)", "SEC" is "Securities and Exchange Commission"

Cause: Showing XBRL report.

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10005: Creating US GAAP Instance Transformer (instance path: {0}; taxonomy path: {1}) "US GAAP" is "Generally Accepted Accounting Principles (United States)"

Cause: Initialization US GAAP viewer.

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10006: Creating Generic Viewer transformer (instance path: {0}; generic report path: {1})

Cause: Initialization generic viewer.

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10007: Creating XBRL transformer (instance path: {0}) "Xbrl" is "eXtensible Business Reporting Language"

Cause: Initialization XBRL report viewer.

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10008: Error occurred when retrieving doclet range. Ranges count is not equal to 1: ({0})

Cause: Selected doclet is inconsistent.

Action: Reload client and try again.
Level: 32

Type: ERROR

Impact:

DISCMAN-10009: Web Service failed to remove mapping with id={0}

Cause: Failed to remove mapping on server side.

Action: Check if mapping exists, probably it was removed by another user.
Level: 32

Type: ERROR

Impact:

DISCMAN-10010: Mapping to concept '{0}' failed. Document is associated with taxonomy '{1}' but concept belongs to taxonomy '{2}'

Cause: Failed to create mapping for other taxonomy.

Action: Change taxonomy for document.
Level: 32

Type: ERROR

Impact:

DISCMAN-10011: Could not create mapping object. Unknown mapping object type {0}.

Cause: Failed to create mapping object for this type.

Action: Update client version.
Level: 32

Type: ERROR

Impact:

DISCMAN-10012: Could not create web service. Unknown web service type {0}.

Cause: Failed to create web service.

Action: Update client version.
Level: 32

Type: ERROR

Impact:

DISCMAN-10013: Exception occurred when querying document mappings, {0}. {0} is occurred exception

Cause: Failed to call MappingTool web service (method QueryDocumentMappings).

Action: Check if the MappingTool Web Service is configured correctly.
Level: 32

Type: ERROR

Impact:

DISCMAN-10014: Exception occurred when querying grid mappings, {0}. {0} is occurred exception

Cause: Failed to call MappingTool web service (method QueryGridMappings).

Action: Check if the MappingTool Web Service is configured correctly.
Level: 32

Type: ERROR

Impact:

DISCMAN-10015: Exception occurred when generating instance, {0}. {0} is occurred exception

Cause: Failed to call MappingTool web service (method Generate).

Action: Check if the MappingTool Web Service is configured correctly.
Level: 32

Type: ERROR

Impact:

DISCMAN-10016: Exception occurred when removing mapping, {0}. {0} is occurred exception

Cause: Failed to call MappingTool web service (method RemoveMapping).

Action: Check if the MappingTool Web Service is configured correctly.
Level: 32

Type: ERROR

Impact:

DISCMAN-10017: Exception occurred when changing mappings taxonomy, {0}. {0} is occurred exception

Cause: Failed to call MappingTool web service (method ChangeMappingsTaxonomy).

Action: Check if the MappingTool Web Service is configured correctly.
Level: 32

Type: ERROR

Impact:

DISCMAN-10018: Updating tuple information failed.

Cause: Failed to update TupleInfos.

Action: Reload client and try again.
Level: 32

Type: WARN

Impact:

DISCMAN-10019: Try to map abstract element "{0}:{1}."

Cause: You cannot map abstract element.

Action: Select not abstract element.
Level: 32

Type: WARN

Impact:

DISCMAN-10020: Adding dimension failed.

Cause: Failed to call MappingToolView (method documentMap.addXbrlDimension).

Action: Reload client and try again.
Level: 32

Type: WARN

Impact:

DISCMAN-10021: Updating review information failed.

Cause: Failed to call MappingToolView (method registerDocumentMaps).

Action: Reload client and try again.
Level: 32

Type: WARN

Impact:

DISCMAN-10022: Updating contexts failed.

Cause: Failed to call MappingToolView (method setContexts).

Action: Reload client and try again.
Level: 32

Type: WARN

Impact:

DISCMAN-10023: Updating tuples information failed.

Cause: Failed to call MappingToolView (method SetTupleInstanceContext).

Action: Reload client and try again.
Level: 32

Type: WARN

Impact:

DISCMAN-10024: Updating virtual contexts failed.

Cause: Failed to call MappingToolView (method setVirtualContexts).

Action: Reload client and try again.
Level: 32

Type: WARN

Impact:

DISCMAN-10025: Updating units failed.

Cause: Failed to call MappingToolView (method setUnits).

Action: Reload client and try again.
Level: 32

Type: WARN

Impact:

DISCMAN-10026: Updating footnotes failed.

Cause: Failed to call MappingToolView (method setFootnotes).

Action: Reload client and try again.
Level: 32

Type: WARN

Impact:

DISCMAN-10027: Disclosure Management main menu item was not created.

Cause: Client initialization failed (main menu item is not created).

Action: Update client version.
Level: 32

Type: ERROR

Impact:

DISCMAN-10029: Could not create document UI: unknown native document type.

Cause: Document initialization failed (unknown native document type).

Action: Select other document.
Level: 32

Type: ERROR

Impact:

DISCMAN-10030: Document is not a standalone Disclosure Management document.

Cause: You need standalone DiscMan Document for this operation.

Action: Select other document.
Level: 32

Type: ERROR

Impact:

DISCMAN-10031: Only Word Document can be converted to Master Document.

Cause: You need MS Word Document for this operation.

Action: Select MS Word document.
Level: 32

Type: ERROR

Impact:

DISCMAN-10032: Failed to convert to Master document. Could not connect to security service.

Cause: Failed to connect to security web service (creating Master Document).

Action: Check if Authorization system is configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10033: Expected resources not found. The following files are required: {0}, {1}, {2}.

Cause: Failed to get resource from server.

Action: Check server-side configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10034: Failed to generate instance preview. Path to SEC viewer source files is invalid. "SEC" is "Securities and Exchange Commission"

Cause: SEC View path is not defined.

Action: Open client Options and configure SEC View path.
Level: 32

Type: ERROR

Impact:

DISCMAN-10035: {0}

Cause: Error SEC View module.

Action: Check SEC View configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10036: Global template is not installed. Customization will work with Normal.dot.

Cause: Client initialization failed (cannot created global template).

Action: Check MS Office configuration.
Level: 32

Type: WARN

Impact:

DISCMAN-10037: DiscManDocument.CheckMappingDocumentId: generated new MappingDocumentId value = \"{0}\".

Cause:

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10038: Doclet storage is already initialized.

Cause: Client initialization failed (doclet storage is already initialized).

Action: Restart client.
Level: 32

Type: ERROR

Impact:

DISCMAN-10039: Publishing excel doclet failed. Worksheet name is not defined.

Cause: Worksheet name is not defined.

Action: Select correct worksheet before operation.
Level: 32

Type: ERROR

Impact:

DISCMAN-10040: Error occurred when retrieving doclet subdocument.

Cause: Document initialization failed (subdocument not found).

Action: Reopen document.
Level: 32

Type: ERROR

Impact:

DISCMAN-10041: A primary item mapping must exist prior to domain or member mapping.

Cause: Cannot create dimension mapping without concept mapping.

Action: Create concept mapping before dimension mapping.
Level: 32

Type: ERROR

Impact:

DISCMAN-10042: Highlight is impossible in locked document.

Cause: Cannot highlight mapping inside read only Doclet.

Action: Open Doclet separately.
Level: 32

Type: ERROR

Impact:

DISCMAN-10043: Unrecognized Office Application {0}

Cause: Unsupported MS Office application.

Action: See documentation for supported MS Office applications.
Level: 32

Type: ERROR

Impact:

DISCMAN-10044: Version: {0}

Cause: Client version.

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10045: Expected Smart View Version: {0} (Build {1}) or higher.

Cause: SmartView version.

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10046: Disclosure Management Smart View Extension is shut down.

Cause: Client shutdown.

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10047: Disclosure Management Smart View Extension is started up.

Cause: Client startup.

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10048: Cannot get id for message={0}.

Cause: Failed to parse message id.

Action: Update client version.
Level: 32

Type: ERROR

Impact:

DISCMAN-10049: Failed to replace new page section break with the section break in new doclet. Exception: {0}

Cause: Resources leak.

Action: Restart workstation.
Level: 32

Type: ERROR

Impact:

DISCMAN-10050: Failed to align table to left. Exception: {0}

Cause: Resources leak.

Action: Restart workstation.
Level: 32

Type: ERROR

Impact:

DISCMAN-10051: Failed to add a subdocument to the document. Exception: {0}

Cause: A document of a part of the document is read-only.

Action: Choose the right place in the document for doclet adding.
Level: 32

Type: ERROR

Impact:

DISCMAN-10052: Error occurred when connecting to the mapping tool web service. Please check your settings or server state.

Cause: Failed to connect to mapping tool web service.

Action: Check your settings and server state.
Level: 32

Type: ERROR

Impact:

DISCMAN-10053: Updating review information failed. Exception: {0}

Cause: Failed to call MappingToolView (method registerDocumentMaps).

Action: Reload client and try again.
Level: 32

Type: ERROR

Impact:

DISCMAN-10054: Web Service failed to remove mapping with id={0}. Exception: {1}

Cause: Failed to remove mapping on server side.

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-10055: Failed to keep alive session. Exception: {0}

Cause: Failed to update session.

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-10056: Repository: {0} failed. Exception: {1} {0} is method's name which generated exception

Cause: Failed to call repository session.

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-10057: Excel's Doclet publish failed. Exception: {0}

Cause: Failed to publish Excel's Doclet.

Action: Restart workstation and try again.
Level: 32

Type: ERROR

Impact:

DISCMAN-10058: Failed to change mappings taxonomy {0}. Exception: {1}

Cause: Failed to update server-side information.

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-10059: Common View is not initialized.

Cause: Client initialization failed.

Action: Update client version.
Level: 32

Type: ERROR

Impact:

DISCMAN-10060: Mapping Tool Web Service initialization failed (URL={0}). Exception: {1}

Cause: Failed to create mapping tool web service.

Action: Check your settings and server state.
Level: 32

Type: ERROR

Impact:

DISCMAN-10061: Unpacking Instance Package failed. Exception: {0}

Cause: Failed to extract data from package.

Action: Reload client and try again.
Level: 32

Type: ERROR

Impact:

DISCMAN-10062: Validation failed. Exception: {0}

Cause: Failed to validate report.

Action: Reload client and try again.
Level: 32

Type: ERROR

Impact:

DISCMAN-10063: Deletion of {0} failed. Exception: {1} {0} is mapping document name

Cause: Failed to delete file.

Action: Reload client and try again.
Level: 32

Type: ERROR

Impact:

DISCMAN-10064: Writing of {0} failed. Exception: {1} {0} is report name

Cause: Failed to write file.

Action: Reload client and try again.
Level: 32

Type: ERROR

Impact:

DISCMAN-10065: Export failed. Exception: {0}

Cause: Failed to export report.

Action: Reload client and try again.
Level: 32

Type: ERROR

Impact:

DISCMAN-10066: Failed to query document mappings (DocumentId={0}). Exception: {1}

Cause: Failed to get server-side mappings.

Action: Check your settings and server state.
Level: 32

Type: ERROR

Impact:

DISCMAN-10067: URL is inconsistent. Exception: {0}

Cause: Failed to create url.

Action: Check your settings and try again.
Level: 32

Type: ERROR

Impact:

DISCMAN-10068: Report Web Service initialization failed (URL={0}). Exception: {1}

Cause: Failed to create report web service.

Action: Check your settings and server state.
Level: 32

Type: ERROR

Impact:

DISCMAN-10069: Create Doclet failed. Exception: {0}

Cause: Failed to create doclet on server side.

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-10070: Create Report failed. Exception: {0}

Cause: Failed to create report on server side.

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-10071: Repository Web Service initialization failed (URL={0}). Exception: {1}

Cause: Failed to create repository web service.

Action: Check your settings and server state.
Level: 32

Type: ERROR

Impact:

DISCMAN-10072: Security: {0} failed. Exception: {1} {0} is processing operation

Cause: Failed to call security service.

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-10073: Failed to create US GAAP report. Exception: {0} "US GAAP" is "Generally Accepted Accounting Principles (United States)"

Cause: Error SEC View module.

Action: Check SEC View configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10074: Word Add-In cannot work with user selection.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-10075: Logon failed. {0} {0} is occurred exception

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-10076: Mapping {0} contains unsupportable characters and was reduced to '{1}'. {1} is new string without unsupportable characters

Cause: Mapping data contains unsupportable characters.

Action: Remove unsupportable characters.
Level: 32

Type: WARN

Impact:

DISCMAN-10077: Query View converted. Server: '{0}' App: '{1}' Base: '{2}' Provider: '{3}'.

Cause: Query View converted from Smart View format to Disclosure Management format.

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10078: Provider id mapped from value: '{0}' to value: '{1}'.

Cause: Data source provider id was found in mapping table and converted.

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10079: Full mapping fact with the same id already exists: {0} ({1}:{2}).

Cause: Error at loading review information.

Action: Update client version.
Level: 32

Type: ERROR

Impact:

DISCMAN-10080: SmartView Data Point (col={0}, row={1}, POV={2}, value='{3}', custom data='{4}') does not have view's object. "POV" is "Point Of View"

Cause: SmartView data contains unconsistent record.

Action:
Level: 32

Type: WARN

Impact:

DISCMAN-10081: Trying to get a session using a token from connection URL: {0}.

Cause: Trying to get a session using a token.

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10082: SSO authentication failed. URL: {0}.

Cause: Failed to get a session using a token.

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10083: SSO authentication succeded. URL: {0}.

Cause: Succeded to get a session using a token.

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10084: New data source connection established. URL: {0}. Last connection: {1}.

Cause: New data source connection established.

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10085: Data source connection is broken. URL: {0}. Last connection: {1}.

Cause: Data source connection breaked.

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10086: Last successful Disclosure Management connection: {0}.

Cause: Last successful Disclosure Management connection is changed.

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10087: Word doclet publish failed. Exception: {0}.

Cause: Failed to publish Word Doclet.

Action: Restart workstation and try again.
Level: 32

Type: ERROR

Impact:

DISCMAN-10088: Doclet post publish steps failed. Exception: {0}.

Cause: Failed to run post publish steps during a doclet adding.

Action: Restart workstation and try again.
Level: 32

Type: ERROR

Impact:

DISCMAN-10089: Copying variables from doclet failed. Exception: {0}.

Cause: Failed to copy variables from a doclet to a master document.

Action: Restart workstation and try again.
Level: 32

Type: ERROR

Impact:

DISCMAN-10090: Doclets subdirectory {0} could not be created. Exception: {1}.

Cause: Failed to create a subdirectory.

Action: Check a user's permitions and the new directory parameters.
Level: 32

Type: ERROR

Impact:

DISCMAN-10091: Failed to copy the file {0} to destination path {1}. Exception: {2}.

Cause: Failed to copy a file.

Action: Check a user's permitions and the new path value.
Level: 32

Type: ERROR

Impact:

DISCMAN-10092: Unexpected error occurred during the duplication of the report. Exception: {0}.

Cause: Unexpected error during the report cloning.

Action: Restart the client application and try again.
Level: 32

Type: ERROR

Impact:

DISCMAN-10093: Doclets copies subdirectory {0} could not be created. Exception: {1}.

Cause: Failed to create a subdirectory.

Action: Check a user's permitions and the new directory parameters.
Level: 32

Type: ERROR

Impact:

DISCMAN-10094: Failed to duplicate a report with id {0} on the server. Exception: {1}.

Cause: Report service failed to duplicate a report.

Action: Check a report service configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10095: Failed to link mapping {0} with range '{1}', it already linked with range '{2}'. {0} is mapping id; {1}, {2} range's information

Cause: Document contains inconsistent mapping information.

Action: Update client version.
Level: 32

Type: ERROR

Impact:

DISCMAN-10096: Report Service failed to add a unit. Report Id: {0}. Unit properties: {1}. Exception: {2}.

Cause: Report service failed to add a unit.

Action: Check a report service configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10097: Report Service failed to remove a unit. Report Id: {0}. Unit Id: {1}. Exception: {2}.

Cause: Report service failed to remove a unit.

Action: Check a report service configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10098: Report Service failed to update a unit. Report Id: {0}. Unit properties: {1}. Exception: {2}.

Cause: Report service failed to update a unit.

Action: Check a report service configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10099: Report Service failed to get units. Report Id: {0}. Exception {1}.

Cause: Report service failed to get units.

Action: Check a report service configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10100: Report Service failed to add a context. Report Id: {0}. Context properties: {1}. Exception: {2}.

Cause: Report service failed to add a context.

Action: Check a report service configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10101: Report Service failed to remove a context. Report Id: {0}. Context Id: {1}. Exception: {2}.

Cause: Report service failed to remove a context.

Action: Check a report service configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10102: Report Service failed to update a context. Report Id: {0}. Context properties: {1}. Exception: {2}.

Cause: Report service failed to update a context.

Action: Check a report service configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10103: Report Service failed to get contexts. Report Id: {0}. Exception {1}.

Cause: Report service failed to get contexts.

Action: Check a report service configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10104: Migration process failed to create a backup of a document {0} to {1}. Exception: {2}

Cause: Migration process failed to create a backup of a document.

Action: Check a user's permitions.
Level: 32

Type: ERROR

Impact:

DISCMAN-10105: Failed to clone mappings on the server. Old document id: {0}. New document Id: {1}. Application id: {2}. New report name: {3}. Exception: {4}.

Cause: Failed to clone mappings on the server.

Action: Check a mapping tool service configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10106: Mapping Tool web service failed to generate XBRL data. Exception: {0}.

Cause: Mapping Tool web service failed to generate XBRL data.

Action: Check a mapping tool service configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10107: Mapping Tool web service failed to generate IXBRL data. Exception: {0}.

Cause: Mapping Tool web service failed to generate IXBRL data.

Action: Check a mapping tool service configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10108: Doclet publish process failed to copy the file {0} to destination path {1}. Exception: {2}.

Cause: Failed to copy a file during a doclet publishing.

Action: Check a user's permitions and the new path value.
Level: 32

Type: ERROR

Impact:

DISCMAN-10109: Doclet publish process failed to delete the file {0}. Exception: {1}.

Cause: Failed to delete a file during a doclet publishing.

Action: Check a user's permitions and the path value.
Level: 32

Type: ERROR

Impact:

DISCMAN-10110: Failed to update a report with id {0} on the server. Exception: {1}.

Cause: Report service failed to update a report.

Action: Check a report service configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10111: Detailed Tagging turns off (MS Office 2003 Standard Edition doesn't support it).

Cause: MS Office 2003 Standart Edition doesn't support detailed tagging.

Action: Use MS Office 2007 or MS Office 2003 Professional Edition.
Level: 32

Type: WARN

Impact:

DISCMAN-10112: Overlapped cells have been detected. Cannot process XBRL mappings in row {0} of worksheet {1}.

Cause: Excel's doclet contains not properly formated rows with mappings.

Action: Set Wrap Text property for corresponding cells or use Merge for reformatting row.
Level: 32

Type: ERROR

Impact:

DISCMAN-10113: Exception occurred when geting a taxonomy list {0}. {0} is occurred exception

Cause: Failed to call MappingTool web service (method getTaxonomyList).

Action: Check if the MappingTool Web Service is configured correctly.
Level: 32

Type: ERROR

Impact:

DISCMAN-10114: Exception occurred when previewing a data source mappings duplication. Exception: {0}. {0} is occurred exception

Cause: Failed to call MappingTool web service (method previewDSMappings).

Action: Check if the MappingTool Web Service is configured correctly.
Level: 32

Type: ERROR

Impact:

DISCMAN-10115: Exception occurred when duplication data source mappings. Exception: {0}. {0} is occurred exception

Cause: Failed to call MappingTool web service (method cloneDSMappings).

Action: Check if the MappingTool Web Service is configured correctly.
Level: 32

Type: ERROR

Impact:

DISCMAN-10116: Change taxonomy failed. Exception: {0}

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-10117: GetTuples for Report Id: {0} tuple descriptor '{1}' failed. Exception: {2}

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-20201: Failed to parse doclet mapping storage XML.

Cause: Failed to parse doclet mapping storage XML.

Action: Check if doclet storage XML is well formed.
Level: 32

Type: ERROR

Impact:

DISCMAN-20202: Failed to read doclet mapping storage file.

Cause: Error encountered during reading doclet mapping storage file.

Action: Check if mapping storage file is exixts and accessible.
Level: 32

Type: ERROR

Impact:

DISCMAN-20203: Doclet mapping storage file must be writable.

Cause: Error encountered during writing doclet mapping storage file.

Action: Check if mapping storage file is exixts and accessible.
Level: 32

Type: ERROR

Impact:

DISCMAN-20204: Failed to save doclet mapping.

Cause: Error encountered during writing doclet mapping storage file.

Action: Check if mapping storage file is exixts and accessible.
Level: 32

Type: ERROR

Impact:

DISCMAN-20210: Failed to generate doclet local identifier.

Cause: Error encountered during generating doclet identifier.

Action: Check if database is up.
Level: 32

Type: ERROR

Impact:

DISCMAN-20211: Specified doclet has not been found.

Cause: Error encountered during checkOut doclet.

Action: Check if database is up and if doclet is created.
Level: 32

Type: ERROR

Impact:

DISCMAN-20212: Failed to check in doclet.

Cause: Error encountered during checkIn doclet.

Action: Check if database is up and if doclet is created.
Level: 32

Type: ERROR

Impact:

DISCMAN-20213: Cannot check in doclet. It must be checked out first.

Cause: Error encountered during checkIn doclet.

Action: Check if report is shecked out.
Level: 32

Type: ERROR

Impact:

DISCMAN-20214: Checking in user has to be same user who checked out the doclet.

Cause: Error encountered during checkIn doclet.

Action: Check if user are allowed to check in.
Level: 32

Type: ERROR

Impact:

DISCMAN-20215: Failed to check out doclet.

Cause: Error encountered during checkOut doclet.

Action: Check if repository is up.
Level: 32

Type: ERROR

Impact:

DISCMAN-20216: The doclet has never been checked in. There is no corresponding content in the repository.

Cause: Error encountered during getting doclet content.

Action: Check if repository is up and if doclet is created.
Level: 32

Type: ERROR

Impact:

DISCMAN-20217: The doclet has already been checked out.

Cause: Error encountered during checkOut doclet.

Action: Check if doclet is already checked out.
Level: 32

Type: ERROR

Impact:

DISCMAN-20218: Failed to get content of doclet.

Cause: Error encountered during getting doclet content.

Action: Check if repository is up.
Level: 32

Type: ERROR

Impact:

DISCMAN-20219: Bad doclet id.

Cause: Error encountered during getting doclet content. Doclet id is invalid or null.

Action: Web service client error. Should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-20220: Bad unit id.

Cause: Passed unit or report id is invalid or null.

Action: Web service client error. Should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-20221: Bad context id.

Cause: Passed context or report id is invalid or null.

Action: Web service client error. Should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-20222: Specified context has not been found.

Cause: Error encountered during checkout context.

Action: Check if database is up and if context is created.
Level: 32

Type: ERROR

Impact:

DISCMAN-20223: Specified unit has not been found.

Cause: Error encountered during checkout unit.

Action: Check if database is up and if unit is created.
Level: 32

Type: ERROR

Impact:

DISCMAN-30201: Failed to parse report storage XML.

Cause: Error encountered during parsing report storage XML.

Action: Check if report storage XML is well formed.
Level: 32

Type: ERROR

Impact:

DISCMAN-30202: Failed to read report storage file.

Cause: Error encountered during reading report storage XML.

Action: Check if report storage XML is well formed.
Level: 32

Type: ERROR

Impact:

DISCMAN-30203: Report storage file must be writable.

Cause: Error encountered during writing report storage XML.

Action: Check if report storage XML has writable permisssion.
Level: 32

Type: ERROR

Impact:

DISCMAN-30204: Failed to save report.

Cause: Error encountered during saving report.

Action: Check if Repository Web Service is up.
Level: 32

Type: ERROR

Impact:

DISCMAN-30206: Report with the specified id has not been found.

Cause: Error encountered during creating master document.

Action: Check if database is up and if report is created.
Level: 32

Type: ERROR

Impact:

DISCMAN-30207: Failed to log audit record.

Cause: Error encountered during auditing.

Action: Check if Audit Web Service is up.
Level: 32

Type: INFO

Impact:

DISCMAN-30208: Bad report id.

Cause: Report id is in bad format or is not specified.

Action: The error is in the web service client. It should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-30209: Disclosure Management reports: database access error.

Cause: Disclosure Management reports: database access error.

Action: Check database configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-30210: Context name for given report already exists

Cause: Disclosure Management reports: duplicate context name.

Action: Client should choose another name.
Level: 32

Type: ERROR

Impact:

DISCMAN-30211: Unit name for given report already exists

Cause: Disclosure Management reports: duplicate unit name.

Action: Client should choose another name.
Level: 32

Type: ERROR

Impact:

DISCMAN-30212: Context name does not comply xbrl standard

Cause: Disclosure Management reports: context name violation.

Action: Client should choose another name.
Level: 32

Type: ERROR

Impact:

DISCMAN-30213: Unit name does not comply xbrl standard

Cause: Disclosure Management reports: wrong unit name violation.

Action: Client should choose another name.
Level: 32

Type: ERROR

Impact:

DISCMAN-30214: Footnote name does not comply xbrl standard

Cause: Disclosure Management reports: wrong footnote name violation.

Action: Client should choose another name.
Level: 32

Type: ERROR

Impact:

DISCMAN-30215: Footnote name must be unique

Cause: Disclosure Management: footnote name violation.

Action: Client should choose another name.
Level: 32

Type: ERROR

Impact:

DISCMAN-30216: Failed to get mappings for report

Cause: Report Service: failed to process mappings for report.

Action: Web service client error. Should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-30217: Failed to encode report object

Cause: Report Service: failed to encode information for report.

Action: Web service client error. Should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-30218: Failed to decode report object

Cause: Report Service: failed to decode information for report.

Action: Web service client error. Should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-30219: Specified counter has not been found

Cause: Report Service: passed counter id is invalid or null.

Action: Web service client error. Should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-30220: Specified application id could not be null

Cause: Report Service: Specified application id could not be null.

Action: Web service client error. Should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-30221: Specified category has not been found

Cause: Report Service: passed category id is invalid or null.

Action: Web service client error. Should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-30222: Passed report should have only one doclet

Cause: Report Service: Passed report should have only one doclet.

Action: Web service client error. Should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-30223: Specified doclet part has not been found

Cause: Report Service: Specified doclet part has not been found.

Action: Web service client error. Should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-30224: Bad doclet part id

Cause: Report Service: Bad doclet part id.

Action: Web service client error. Should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-30225: Failed to change taxonomy

Cause: Report Service: Failed to change taxonomy.

Action: Web service client error. Should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-30226: Failed to clone tuples

Cause: Report Service: Failed to clone tuples.

Action: Web service client error. Should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-40201: Authentication system is unavailable.

Cause: Error encountered during Authentication system configuration.

Action: Check if Authentication system is configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-40202: No session state with given id was found.

Cause: Error encountered during Authentication system configuration.

Action: Check if Authentication system is configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-40210: The user name or password is incorrect.

Cause: Error encountered during login.

Action: Check if CSS is up and if input parameter credentials is correct.
Level: 32

Type: ERROR

Impact:

DISCMAN-40220: Authorization failed. You have no or limited access to Disclosure Management application.

Cause: Error encountered during authorization.

Action: Check if Authorization system is configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-40301: No session state with given id was found.

Cause: No state with given id was found.

Action: Web service client error. Should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-40302: Disclosure Management state service: database access error.

Cause: Database access error.

Action: Check database configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-40303: Disclosure Management state service: failed to get session from database.

Cause: Failed to get session from database.

Action: Check database configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-40304: Disclosure Management state service: failed to get role from database.

Cause: Failed to get role from database.

Action: Check database configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-40305: Session was expired.

Cause: Session was expired.

Action: Login again.
Level: 32

Type: ERROR

Impact:

DISCMAN-50000: Failed to initialize XBRL Processor.

Cause: XBR not initialized properly.

Action: Check if resources are present for the XBRL Processing Engine.
Level: 32

Type: ERROR

Impact:

DISCMAN-50001: Failed to shut down XBRL Processor.

Cause: Failed to close the xbrl instance.

Action: Shut down the processor externally.
Level: 32

Type: ERROR

Impact:

DISCMAN-50002: Failed to load the taxonomy.

Cause: Failed to load taxonomy.

Action: Check processing engine configured properly and taxonomy file is also valid.
Level: 32

Type: ERROR

Impact:

DISCMAN-50003: Failed to generate the tree structure for this taxonomy.

Cause: Failed to walk the node.

Action: Check taxonomy concept is valid.
Level: 32

Type: ERROR

Impact:

DISCMAN-50004: Failed to get the tree node detail information.

Cause: Failed to load detail information for node.

Action: Check processing engine configured properly and taxonomy file is also valid.
Level: 32

Type: ERROR

Impact:

DISCMAN-50005: Failed to build ADF tree model.

Cause: Failed build the tree model for taxonomy.

Action: Check taxonomy structure.
Level: 32

Type: ERROR

Impact:

DISCMAN-50006: Failed to get all links for taxonomy.

Cause: Failed to get all Links for taxonomy.

Action: Check taxonomy all Link definition is valid.
Level: 32

Type: ERROR

Impact:

DISCMAN-50007: Failed to get tree node information for this taxonomy.

Cause: Failed to get dimension member for taxonomy.

Action: Check taxonomy dimension data is valid.
Level: 32

Type: ERROR

Impact:

DISCMAN-50008: Error occurred executing request for mapping tool. See Error logs for details.

Cause: Error occurred executing request for mapping tool.

Action: Check app server running properly.
Level: 32

Type: ERROR

Impact:

DISCMAN-50009: Failed to load property file mappingtool.properties.

Cause: Cannot find property file.

Action: Check if mappingtool.properties is exist.
Level: 32

Type: ERROR

Impact:

DISCMAN-50010: Set up DISCMAN_HOME in server first.

Cause: DISCMAN_HOME doesn't exist.

Action: Please specify setting for DISCMAN_HOME.
Level: 32

Type: ERROR

Impact:

DISCMAN-50011: Incorrect number of parameters was passed. Expecting {0}, found {1}.

Cause: Incorrect number of parameters was passed.

Action: Please check number of parameters.
Level: 32

Type: ERROR

Impact:

DISCMAN-50012: Error occurred in generating XBRL instance. Check server logs for details.

Cause: Error occurred in generating XBRL instance.

Action: Check app server running properly.
Level: 32

Type: ERROR

Impact:

DISCMAN-50013: Invalid date argument was passed.

Cause: Invalid date argument was passed.

Action: Specify correct arguments.
Level: 32

Type: ERROR

Impact:

DISCMAN-50015: Error occurred in parsing the XML.

Cause: Error occurred in parsing the XML.

Action: Check XML structure.
Level: 32

Type: ERROR

Impact:

DISCMAN-50016: Invalid argument was passed in the generation of XBRL Instance. The taxonomy name is null or empty.

Cause: The client passed an invalid parameter.

Action: Check if the document has mappings.
Level: 32

Type: ERROR

Impact:

DISCMAN-50017: Error was encountered in the querying of Grid mappings.

Cause: Error encountered while searching for context.

Action: Check if the database server is up or the database connection. Check if the XML query is correct.
Level: 32

Type: ERROR

Impact:

DISCMAN-50018: Error was encountered in the querying of Document mappings.

Cause: Error encountered while searching for context.

Action: Check if the database server is up or the database connection. Check if the XML query is correct.
Level: 32

Type: ERROR

Impact:

DISCMAN-50019: Invalid Argument was passed when retrieving the taxonomy concept.

Cause: Invalid Argument was passed.

Action: Check if Argument is correct.
Level: 32

Type: ERROR

Impact:

DISCMAN-50020: Unknown application id was passed.

Cause: Unknown application id was passed.

Action: Check if applicationID is correct.
Level: 32

Type: ERROR

Impact:

DISCMAN-50021: No reference was specified in the context.

Cause: No reference was specified in the context.

Action: Check context.
Level: 32

Type: ERROR

Impact:

DISCMAN-50022: No entity was specified in the context.

Cause: No entity was specified in the context.

Action: Check context.
Level: 32

Type: ERROR

Impact:

DISCMAN-50023: Failed to generate the dimension member tree for selected primary item.

Cause: XBRL Processing Error.

Action: Check app server running properly.
Level: 32

Type: ERROR

Impact:

DISCMAN-50024: Failed to generate the tuple group tree.

Cause: Failed to create the empty tuple instance tree model.

Action: Check app server running properly.
Level: 32

Type: ERROR

Impact:

DISCMAN-50025: Unable to create explicit dimension mapping for dimension name {0} with dimension value {1}.

Cause: Unable to create explicit dimension mapping.

Action: Check app server running properly.
Level: 32

Type: ERROR

Impact:

DISCMAN-50026: Unable to create typed dimension mapping for dimension name {0} with dimension value {1}.

Cause: Unable to create typed dimension mapping.

Action: Check app server running properly.
Level: 32

Type: ERROR

Impact:

DISCMAN-50028: No XBRL concept mappings was found. Cannot generate XBRL instance.

Cause: No mapping was passed to the instance generator.

Action: Make sure at least one mapping is present when generating an instance.
Level: 32

Type: ERROR

Impact:

DISCMAN-50030: Failed to load the taxonomy file list.

Cause: Failed to read the taxonomy file list.

Action: Check to make sure property file exist.
Level: 32

Type: ERROR

Impact:

DISCMAN-50032: Failed to create UBMatrixTaxoAdapter object.

Cause: Failed create ubmatrixAdapter object.

Action: Check to see if process engine configured properly.
Level: 32

Type: ERROR

Impact:

DISCMAN-50033: Failed to close XBRL Processor.

Cause: Failed to close the xbrl instance.

Action: Close the processor externally.
Level: 32

Type: ERROR

Impact:

DISCMAN-50034: Failed to build the XBRL Query.

Cause: Failed to building XBRL Query.

Action: Check taxonomy file is valid..
Level: 32

Type: ERROR

Impact:

DISCMAN-50035: Failed to get the concept label.

Cause: Failed to get label for concept.

Action: Check taxonomy concept is valid.
Level: 32

Type: ERROR

Impact:

DISCMAN-50036: Failed to get the concept.

Cause: Failed to get concept from fullName.

Action: Check taxonomy concept is valid.
Level: 32

Type: ERROR

Impact:

DISCMAN-50039: Failed to validate instance document

Cause: Failed to validate instance document.

Action: Check processing engine configured properly and taxonomy file is also valid.
Level: 32

Type: ERROR

Impact:

DISCMAN-50040: Failed to execute DTS query.

Cause: Failed to generate HTML instance report from instance document.

Action: Check that instance document is proper and valid one.
Level: 32

Type: ERROR

Impact:

DISCMAN-50041: Failed to generate HTML instance report from DTS object.

Cause: Failed to generate HTML instance report from DTS object.

Action: Check that DTS object is proper and valid one.
Level: 32

Type: ERROR

Impact:

DISCMAN-50042: Failed to generate HTML instance report from instance file.

Cause: Failed to execute DTS query.

Action: Check the query syntax and other details passed.
Level: 32

Type: ERROR

Impact:

DISCMAN-50043: No mappings with specified id were found.

Cause: No mappings with specified id were found.

Action: Check the query syntax and other details passed.
Level: 32

Type: ERROR

Impact:

DISCMAN-50045: Target taxonomy cannot be found.

Cause: Target taxonomy cannot be found.

Action: Check app server running properly.
Level: 32

Type: ERROR

Impact:

DISCMAN-50046: Failed to change taxonomy.

Cause: Failed to change taxonomy.

Action: Check app server running properly.
Level: 32

Type: ERROR

Impact:

DISCMAN-50047: Error was encountered when registering the Document mappings.

Cause: Error was encountered when registering the Document mappings.

Action: Check app server running properly.
Level: 32

Type: ERROR

Impact:

DISCMAN-50048: Mapping already exists.

Cause: Mapping already exists.

Action: Choose another one.
Level: 32

Type: ERROR

Impact:

DISCMAN-50049: Unable to create mapping.

Cause: Unable to create mapping.

Action: Check your document state.
Level: 32

Type: ERROR

Impact:

DISCMAN-50050: Failed to obtain data type of cache from DTS: {0} for concept: {1}.

Cause: General failure while trying to find if the concept is numeric.

Action: Check if taxonomies are correctly configured. Restart Server.
Level: 32

Type: ERROR

Impact:

DISCMAN-50051: Data type of cache is 'null' for DTS: {0} and concept: {1}.

Cause: Data type cache is unavailable for the Discoverable Taxonomy Set.

Action: Check if taxonomies are correctly configured. Restart Server.
Level: 32

Type: ERROR

Impact:

DISCMAN-50052: Data type of concept:{1} not found in DTS: {0}.

Cause: Can't find type for the concept.

Action: Check if taxonomies are correctly configured. Restart Server.
Level: 32

Type: ERROR

Impact:

DISCMAN-50053: Invalid data type was passed (null) when checking inheritance for base type {0}.

Cause: Data Type for the concept can not be categorized.

Action: Check if taxonomies are correctly configured. Restart Server.
Level: 32

Type: ERROR

Impact:

DISCMAN-50054: Failed to find an XBRL Domain object for the concept: {0}.

Cause: Concept cannot be found in the taxonomy.

Action: Check if taxonomies are correctly configured. Restart Server.
Level: 32

Type: ERROR

Impact:

DISCMAN-50055: Failed to check if data type:{1} from DTS: {0} is inherited from data type: {2}.

Cause: Failed to execute DTS query.

Action: Check app server running properly.
Level: 32

Type: ERROR

Impact:

DISCMAN-50056: Failed to get XBRL Domain object for data type: {1} from DTS {0}.

Cause: Failed to get XBRL Domain object.

Action: Check app server running properly.
Level: 32

Type: ERROR

Impact:

DISCMAN-50057: Failed to find fact in the instance document for mapping: {0}

Cause: Failed to find fact in the instance document.

Action: Check app server running properly.
Level: 32

Type: ERROR

Impact:

DISCMAN-50058: Failed to get value for XBRL unit's measure: {0}

Cause: Failed to get value for XBRL unit's measure.

Action: Check app server running properly.
Level: 32

Type: ERROR

Impact:

DISCMAN-50059: Failed to find namespace URI for measure prefix: {0}

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50060: Failed to extract 'period' element for XBRL context: {0}

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50061: Failed to extract 'end-date' element for XBRL context: {0}

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50062: Failed to get dates values for XBRL context: {0}

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50063: 'identifier' element has not been found for XBRL context: {0}

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50064: Failed to extract identification information from XBRL context: {0}

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50065: Failed to get prefixes for dimension/member pair: {0}/{1}

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50066: Failed to execute DTS query: {0}

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50067: XBRL fact {0} has no 'id' attribute. Skipped.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50068: Failed to create temporary directories.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50069: Failed to deflate source archive to the temporary directory: {0}.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50070: Inline XBRL entry point file has not been found: {0}.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50071: Failed to initialize XML processor.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50072: Failed to parse XML file: {0}.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50073: Failed to get content of the directory: {0}.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50074: Failed to copy file from {0} to {1}.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50075: Failed to create archive for directory: {0}.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50076: Failed to open XML file for writing: {0}

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50077: Failed to save XML file: {0}

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50078: Failed to close XML file after content has been written: {0}

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50079: Custom date transformation is required for value {0}, but no custom pattern has been specified.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50080: Custom numeric transformation is required for value {0}, but no custom parameters have been specified.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50081: 'dash-to-zero' transformation required for value {0} is applicable only for value: \'-\'.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50082: Failed to parse numeric value {0}.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50083: Failed to parse date value {0}.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50084: Due to failure of parsing original value will be used: {0}.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50085: The mapping for Inline XBRL has not been found: {0}

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50086: The fact for Inline XBRL has not been found in instance document: {0}

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50087: xhtml:body element has not been found in the main document. The ix:header won't be generated.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50088: Unknown DMHTML element found in Inline XBRL template (only "http://oracle/discman/ixbrl:mapping" and "http://oracle/discman/ixbrl:footnote" are expected).

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50089: Mapping id has not been specified for mapping in Inline XBRL template.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50090: Can't get extension for file: {0}

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50091: Can't find MIME type for file: {0}. Content can't be embedded.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50092: Can't encode file: {0}. Content can't be embedded.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50093: The path: {0} has to be relative.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50094: The file: {0} has to be within directory: {1}.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50095: The file: {0} does not exist or cannot be read.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50096: Can't set schema reference in generated XBRL instance document.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50097: Null DTS Instance was detected.

Cause: Null DTS Instance was detected.

Action: Check server config settings.
Level: 32

Type: ERROR

Impact:

DISCMAN-50098: Null DTS Taxonomy was detected.

Cause: Null DTS Taxonomy was detected.

Action: Check server config settings.
Level: 32

Type: ERROR

Impact:

DISCMAN-50099: Errors detected while initializing XBRL.

Cause: Errors detected while initializing XBRL.

Action: Enable debug level and do the use case again. Check server logs after that.
Level: 32

Type: ERROR

Impact:

DISCMAN-50100: Failed to create xml query for datasource mappings.

Cause: Failed to create xml query for datasource mappings.

Action: Enable debug level and do the use case again. Check server logs after that.
Level: 32

Type: ERROR

Impact:

DISCMAN-50101: Failed to clone datasource mappings.

Cause: Failed to clone datasource mappings.

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-50102: Failed to query report level mappings.

Cause: Failed to query report level mappings.

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-50103: Failed to delete report level mappings.

Cause: Failed to delete report level mappings.

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-50104: Failed to save XBRL Context.

Cause: Failed to save XBRL Context.

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-50105: No calculation trace done because of duplicate errors. Duplicate count is {0}. Duplicate count but not equal is {1}.

Cause: No calculation trace done because of duplicate errors.

Action: Fix duplicate mappings first so that calculation trace can be done.
Level: 32

Type: ERROR

Impact:

DISCMAN-53001: Failed initiate the taxonomy cache cleaner

Cause: Failed initiate the taxonomy cache cleaner

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-53002: Error was encountered when working with mapping storage

Cause: Error was encountered when working with mapping storage

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-53003: Error was encountered when working with annotation storage

Cause: Error was encountered when working with annotation storage

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-53004: Failed to get concept from taxonomy

Cause: Failed to get concept from taxonomy

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-53005: Error was encountered when trying to suppress explicit fact

Cause: Error was encountered when trying to suppress explicit fact

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-53006: Passed parameter {0} can't be null

Cause: Passed parameter can't be null

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-53007: Concept id in tuple and concept id itself should be equals

Cause: Concept id in tuple and concept id itself should be equals

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-53008: Can not get namespace for taxonomy

Cause: Can not get namespace for taxonomy

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-53009: The concept {0} from taxonomy {1} has already been associated with the selected data point.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-56001: Passed parameter {0} can't be null

Cause: Passed parameter can't be null

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-56002: Can't find {0} with id {1}

Cause: Can't find item with passed id

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-56003: Mapping Storage: database access error

Cause: Database access error

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-70200: Error occurred in the Audit Web Service.

Cause: Error encountered while working with Audit Web Service.

Action: Check if the Audit Web Service is configured correctly.
Level: 32

Type: ERROR

Impact:

DISCMAN-70209: Disclosure Management audit: database access error.

Cause: Disclosure Management audit: database access error.

Action: Check database configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-70210: Error occurred when operating with storage.

Cause: Error encountered while operating with storage.

Action: Check if the storage server is up or the storage connection.
Level: 32

Type: ERROR

Impact:

DISCMAN-80200: Error occurred in the Repository Web Service.

Cause: Error encountered while working with Repository Web Service.

Action: Check if the Repository Web Service is configured correctly.
Level: 32

Type: ERROR

Impact:

DISCMAN-80210: Error occurred when operating with storage.

Cause: Error encountered while operating with storage.

Action: Check if the storage server is up or the storage connection.
Level: 32

Type: ERROR

Impact:

DISCMAN-80211: Error occurred when connecting to the repository.

Cause: Error encountered while connecting to the repository.

Action: Check user credetials.
Level: 32

Type: ERROR

Impact:

DISCMAN-80212: Repository item does not exist at the specified path.

Cause: Error encountered while getting item from the repository.

Action: Check if item exists.
Level: 32

Type: ERROR

Impact:

DISCMAN-80213: Error occurred when reading input content.

Cause: Error encountered while reading input content.

Action: Check if input content is correct.
Level: 32

Type: ERROR

Impact:

DISCMAN-90001: Error occurred when extracting error message.

Cause: Can't find error message

Action: Add error message
Level: 32

Type: ERROR

Impact:

30 DMS-50700 to DMS-58073

DMS-50700: initialization error

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: ERROR

Impact: Configuration

DMS-50701: security error

Cause: (See message)

Action: Review the exception chain in log files for the cause and make sure that the appropriate permission has been granted.
Level: 1

Type: ERROR

Impact: Security

DMS-50702: The DMS Java class "{0}" could not be found.

Cause: (See message)

Action: Review the classpath of the application and ensure that the class is available in a jar file or directory listed therein.
Level: 1

Type: ERROR

Impact: Configuration

DMS-50703: The LogWriter name "{0}" is reserved.

Cause: (See message)

Action: Use a different name.
Level: 1

Type: ERROR

Impact: Logging

DMS-50704: unable to create a new LogWriter: {0}

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: ERROR

Impact: Logging

DMS-50705: attempting to create a concrete LogWriter instance with an invalid class ({0})

Cause: (See message)

Action: Correct the declaration for the LogWriter to use a valid class.
Level: 1

Type: ERROR

Impact: Logging

DMS-50706: invalid configuration property: name = "{0}", value = "{1}"

Cause: (See message)

Action: Remove the property or correct its name or value to comply with the set of supported property names. If the property value is at fault then reviewing the base exception may provide more information on the manner of the fault (e.g. missing class, invalid directory name).
Level: 1

Type: WARNING

Impact: Configuration

DMS-50707: unable to load configuration file "{0}"

Cause: (See message)

Action: Review the exception chain in log files for the cause and make sure that the configuration file exists and the permissions on the file permit it to be read.
Level: 1

Type: ERROR

Impact: Configuration

DMS-50708: unable to parse metric rule document

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: WARNING

Impact: Configuration

DMS-50709: The metric rule resource {0} could not be read. Aggregation is off.

Cause: (See message)

Action: Check that the resource is available and if necessary correct the content of the classpath.
Level: 1

Type: WARNING

Impact: Files

DMS-50710: duplicated table "{1}" in metric table "{0}"

Cause: (See message)

Action: Remove the <Union> or <Select> table from the metric table (it is already in use therein).
Level: 1

Type: WARNING

Impact: Other

DMS-50711: Value "{1}" is invalid for attribute "{0}".

Cause: (See message)

Action: Review the documentation for the correct use of the specific attribute.
Level: 1

Type: WARNING

Impact: Other

DMS-50713: invalid metric rule syntax

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to the metric rule documentation.
Level: 1

Type: WARNING

Impact: Other

DMS-50714: no DMS Archiver found

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: ERROR

Impact: Configuration

DMS-50715: no ONS found

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: ERROR

Impact: Configuration

DMS-50716: unable to create DMS ONS RPC server

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: WARNING

Impact: Other

DMS-50717: unable to create DMS Publisher "{0}"

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: WARNING

Impact: Other

DMS-50719: unable to connect to the server and retrieve metrics at "{0}"

Cause: (See message)

Action: Review the exception chain in log files for the cause and make sure that the server starts up.
Level: 1

Type: WARNING

Impact: Requests/Responses

DMS-50720: unable to retrieve DMS metrics

Cause: The HTTP server failed to handle the metric request.

Action: Make sure the HTTP server is able to handle metric requests.
Level: 1

Type: WARNING

Impact: Other

DMS-50722: unable to parse DMS metric document

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: WARNING

Impact: Other

DMS-50723: The reference to table {0} for aggregating DMS metrics is invalid.

Cause: Columns from tables created by select and union elements are not valid in this context.

Action: Correct the aggregation statement in the metric rules.
Level: 1

Type: WARNING

Impact: Other

DMS-50725: unable to bind to port "{0}"

Cause: (See message)

Action: Review the exception chain in log files for the cause and make sure port is free.
Level: 1

Type: ERROR

Impact: Ports

DMS-50726: The metric configuration resource {0} could not be read.

Cause: (See message)

Action: Check that the resource is available and if necessary correct the content of the classpath.
Level: 1

Type: ERROR

Impact: Configuration

DMS-50727: invalid metric configuration syntax

Cause: (See message)

Action: Refer to XML schema "metric_config.xsd" and correct the configuration.
Level: 1

Type: ERROR

Impact: Configuration

DMS-50728: No writable metric repository directory "{0}" is available. The default metric archiving is off.

Cause: (See message)

Action: Make sure that a writable metric repository exists.
Level: 1

Type: WARNING

Impact: Files

DMS-50730: The repository directory "{0}" is not readable.

Cause: (See message)

Action: Make sure that a readable metric repository exists.
Level: 1

Type: WARNING

Impact: Files

DMS-50731: invalid value type "{0}" for column "{1}"

Cause: (See message)

Action: Refer to the metric rule documentation for valid value types.
Level: 1

Type: WARNING

Impact: Configuration

DMS-50732: invalid value type for "Concat" operation: should be string

Cause: (See message)

Action: Refer to the metric rule documentation for valid value types.
Level: 1

Type: WARNING

Impact: Configuration

DMS-50733: Arithmetic expression cannot be string type.

Cause: (See message)

Action: Refer to the metric rule documentation for details of defining metrics.
Level: 1

Type: WARNING

Impact: Configuration

DMS-50734: missing value type for column <{0} Name="{1}">

Cause: (See message)

Action: Refer to the metric rule documentation and add an explicit value type to the column.
Level: 1

Type: WARNING

Impact: Configuration

DMS-50735: invalid system function <Function Name="{0}">

Cause: (See message)

Action: Refer to the metric rule documentation for a list of valid system functions.
Level: 1

Type: WARNING

Impact: Configuration

DMS-50736: missing an argument in <Expression> for column "{0}"

Cause: (See message)

Action: Refer to the metric rule documentation and add an argument for the expresstion.
Level: 1

Type: WARNING

Impact: Configuration

DMS-50737: circular dependency found on aggregated metric tables {0}

Cause: (See message)

Action: Remove circular dependency among aggregated tables.
Level: 1

Type: WARNING

Impact: Configuration

DMS-50738: invalid operation "{0}"

Cause: (See message)

Action: Refer to the metric rule documentation for a list of valid operations.
Level: 1

Type: WARNING

Impact: Configuration

DMS-50742: Exception occurred while performing individual refresh operation for metric "{0}".

Cause: (See message)

Action: Refer to log files for the cause and, if possible, correct the problem.
Level: 1

Type: WARNING

Impact: Configuration

DMS-50743: Exception occurred while performing group refresh operation for metric "{0}". This failed refresh may have affected other metrics too.

Cause: (See message)

Action: Refer to log files for the cause and, if possible, correct the problem.
Level: 1

Type: WARNING

Impact: Configuration

DMS-50744: illegal argument values passed to method: {0}

Cause: This is in internal error: a set of arguments have been passed to a method within the DMS component that are not appropriate for that method. This state should not have occurred and is indicative of a series of conditions that were not anticipated during development.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

DMS-50745: illegal program state detected: {0}

Cause: This is in internal error: a program state has been detected within the DMS component that is unexpected or contradictory.

Action: Refer to log files for the cause and, if possible, correct the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

DMS-50747: attempt to read an older metric rule document "{0}"

Cause: Metric rule document "{0}" was older than the one currently used in the system.

Action: Make sure the version of the metric rules is equal to or higher than the one currently used in the system.
Level: 1

Type: WARNING

Impact: Configuration

DMS-50748: attempt to read an metric rule document "{0}" that is equal to or older than the one currently used in the system

Cause: The version of the metric rule document "{0}" was equal to or older than the one currently used in the system.

Action: Make sure the version of the metric rules is higher than the one currently used in the system.
Level: 1

Type: WARNING

Impact: Configuration

DMS-50749: OPMN is down.

Cause: (See message)

Action: Start OPMN.
Level: 1

Type: WARNING

Impact: Requests/Responses

DMS-50750: Metric parameter is null.

Cause: (See message)

Action: Pass in a non-null metric.
Level: 1

Type: WARNING

Impact: Data

DMS-50751: Metric "{0}" passed in does not belong to "{1}".

Cause: (See message)

Action: Pass in an appropriate metric.
Level: 1

Type: WARNING

Impact: Data

DMS-50752: One of the parameters for "{0}" is null or empty: {1}

Cause: (See message)

Action: Do not pass in null or empty parameters.
Level: 1

Type: WARNING

Impact: Data

DMS-50753: wrong value type

Cause: (See message)

Action: Pass in value with appropriate type.
Level: 1

Type: WARNING

Impact: Data

DMS-50754: One of the parameters for "{0}" has unexpected value "{1}".

Cause: (See message)

Action: Pass in correct values.
Level: 1

Type: WARNING

Impact: Data

DMS-50755: server unavailable: {0}

Cause: (See message)

Action: Specify valid server or cluster names.
Level: 1

Type: WARNING

Impact: Data

DMS-50756: invalid value for property "{0}": "{1}"

Cause: (See message)

Action: Specify a valid property value.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50757: Property "{0}" cannot have null or empty value.

Cause: (See message)

Action: Specify a valid property value.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50758: Invalid configuration value for metric caching: "{0}"

Cause: (See message)

Action: Specify a valid configuration value.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50759: invalid property: "{0}"

Cause: (See message)

Action: Specify a valid property.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50760: DMS startup class is not started. DMS runs with reduced functionality.

Cause: (See message)

Action: Make sure to start DMS startup class.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50903: Metric aggregation is off due to errors.

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50904: unable to parse metric rule document: {0}

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Other

DMS-50905: missing name for metric table

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50906: conflicting table space for metric table: {0}

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50907: Metric table "{0}" will not be built due to exception.

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50908: Name attribute is invalid in <ColumnDef> for metric table "{0}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50909: duplicated <ColumnDef Name="{1}"> for metric table "{0}"

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50910: Type attribute is invalid in <ColumnDef Name="{1}"> for metric table "{0}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50911: Duplicated metric table. Metric table {0} will be ignored.

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50915: wrong value type "{2}" for column "{1}" in metric table "{0}". Expect value type "{3}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50916: Column "{0}" is missing in table "{1}" for metric table "{2}".

Cause: (See message)

Action: Make sure to match <ColumnDef> with <Column>.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50917: Name attribute is empty in <ColumnGroup>.

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50918: Type attribute is invalid in <ColumnGroup Name="{1}">.

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50919: empty group member in <ColumnGroup Name="{1}">

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50920: Attribute "{3}" of <{0}> is invalid in table "{1}" for metric table "{2}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50921: Column "{0}" is not defined in table "{1}" for metric table "{2}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50922: Attribute "{4}" of <{3} Name="{0}"> is invalid in table "{1}" for metric table "{2}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50923: Number of arguments for column "{3}" in <Expression> is "{0}" in table "{1}" for metric table "{2}", which is less that expected.

Cause: (See message)

Action: Make sure to have at least two arguments.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50924: Arguments for column "{2}" in <Expression> are missing in table "{0}" for metric table "{1}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50925: unexpected <Aggregation> in <Where> in table "{0}" for metric table "{1}"

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50926: Metric table "{2}" should not reference column "{0}" defined in table "{1}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50927: duplicated <{0}> in table "{1}" for metric table "{2}"

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50928: missing <{0}> in table "{1}" for metric table "{2}"

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50929: unexpected <{0}> in <Union Name="{1}"> for metric table "{2}"

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50930: unable to resolve column "{2}" in table "{0}" for metric table "{1}"

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50932: The value of attribute "{0}", "{1}", is less then the minimum "{2}".

Cause: (See message)

Action: Review the documentation for the correct use of the specific attribute and give a valid value.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50933: unable to convert the value of attribute "{0}", "{1}", to a number

Cause: (See message)

Action: Review the documentation for the correct use of the specific attribute and give a valid value.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50934: Sampling is not enabled for metric table "{0}".

Cause: (See message)

Action: Refer to log files for the cause and, if possible, correct the problem.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50935: unable to convert value "{0}" to a number

Cause: (See message)

Action: Refer to log files for the cause and, if possible, correct the problem.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50938: duplicated <{3} Name="{0}"> in table "{1}" for metric table "{2}"

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50940: The value of Attribute "Name" for <OrderBy> fails to match one of column names in table "{0}" for metric table "{1}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50941: unable to convert the value of <RowRetained>, "{0}", in table "{1}" to a number for metric table "{2}"

Cause: (See message)

Action: Review the documentation for the correct use of the specific element and give a valid value.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50942: Only two tables can be referred to in outer join in table "{0}" for metric table "{1}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50943: Some of the values of <Column Name="{0}"> from metric table "{1}" contained by <Select Name="{2}"> inside <Table Name="{3}"> will be lost after aggregation. It is recommended to use <Aggregation Name="{0}"> or <GroupBy Name="{0}">.

Cause: (See message)

Action: It is recommended to use <Aggregation Name="{0}"> or <GroupBy Name="{0}">.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50944: Some of the values of <Column Name="{0}"> from metric table "{1}" contained inside <Having> by <Select Name="{2}"> inside <Table Name="{3}"> will be lost after aggregation. It is recommended to use <Aggregation Name="{0}"> or <GroupBy Name="{0}">.

Cause: (See message)

Action: It is recommended to use <Aggregation Name="{0}"> or <GroupBy Name="{0}">.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50945: missing <And>, <Or>, <Not>, or <Condition> in table "{0}" for metric table "{1}"

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50946: invalid <{0}> in table "{1}" for metric table "{2}"

Cause: (See message)

Action: Specify one of <And>, <Or>, <Not>, or <Condition>.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50947: Number of arguments for condition is "{0}" in table "{1}" for metric table "{2}", which is less that expected.

Cause: (See message)

Action: Make sure to have at least two arguments.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50948: missing condition argument in table "{0}" for metric table "{1}"

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50949: <Null> is not valid when operator is "{0}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50950: Exception occurred while retrieving metrics from metric repository.

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50951: wrong number of tokens in auto aggregation table name "{0}"

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50952: invalid auto aggregation table name "{0}"

Cause: (See message)

Action: Make sure that auto aggregation table names follow the patterns of <prefix>/<opcode>//<table_name> or <prefix>/<opcode>/groupby/<column_name1>/.../<column_nameN>//<table_name>.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50953: invalid aggregation operation "{1}" in auto aggregation table name "{0}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50954: invalid metric cache size "{0}"

Cause: (See message)

Action: Make sure to give a valid value for the metric cache size in megabytes.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50955: invalid metric prefetch interval "{0}"

Cause: (See message)

Action: Make sure to give a valid value for the metric prefetch interval in seconds.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50956: invalid metric prefetch removal cycle "{0}"

Cause: (See message)

Action: Make sure to give a valid value for the metric prefetch removal cycle.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50957: Value of column "{1}" in table "{0}" is not a number.

Cause: (See message)

Action: Review the documentation for the correct use of the specific element and make sure to give valid value.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50960: Column <{2}> should not be type "{3}" in table "{0}" for metric table "{1}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50961: Operation "{2}" should be type "{3}" in table "{0}" for metric table "{1}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50962: Arithmetic expression should not be String type in table "{0}" for metric table "{1}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50963: Column "{0}" expects a number.

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50964: Column <{2} Name="{3}"> is missing value type in table "{0}" for metric table "{1}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50965: <Function Name="{0}"> has invalid function name in table "{1}" for metric table "{2}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50966: Metric table "{0}" has no key column. It will not be collected.

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50973: Caught Exception.

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50976: The use of one or more of the following deprecated properties [{0}] has been detected.

Cause: (See message)

Action: Cease use of the deprecated properties and use one or more of these properties [{1}] instead.
Level: 1

Type: WARNING

Impact: Configuration

DMS-50977: a potentially conflicting use of properties. The use of one or more of the following deprecated properties [{0}] has been detected.

Cause: (See message)

Action: Cease use of the deprecated properties and use one or more of these properties [{1}] instead. The deprecated properties will be ignored.
Level: 1

Type: WARNING

Impact: Configuration

DMS-50978: Exception occurred while registering metric rules "{0}"

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50980: Exception occurred while looking up runtime mbean server by JNDI name "{0}".

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50981: Exception occurred while reading metric rules "{0}".

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: NOTIFICATION

Impact: Other

DMS-50983: Exception occurred while reading metric configuration file "{0}".

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: NOTIFICATION

Impact: Other

DMS-50985: Exception occurred while retrieving metrics from address "{0}" with query string "{1}".

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: NOTIFICATION

Impact: Other

DMS-50989: Exception occurred while retrieving metrics from address "{0}".

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: NOTIFICATION

Impact: Other

DMS-50990: Unable to register MBean "{0}"

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: NOTIFICATION

Impact: Other

DMS-50991: metric rule file "{0}" has the following XML parsing error: {1}

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50992: Invalid Java system property "{0}"

Cause: (See message)

Action: Specify a valid Java system property "{0}".
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50993: invalid metric dump interval "{0}"

Cause: (See message)

Action: Make sure to give a valid metric dump interval in seconds.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50994: invalid maximum size for the metric dump "{0}"

Cause: (See message)

Action: Make sure to give a valid maximum size in megabytes for the metric dump.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-57003: Failed to process the wrapped DMS execution context {0} sent by {1} (user-agent: {2}) when requesting the resource {3}.

Cause: By scrutinizing the incoming HTTP request DMS has attempted to detect and, if appropriate, make use of a wrapped execution context. That process has failed. This should not affect the processing of the servlet handling the request, but the ability to correlate the processing of this request with others to which it may related will have been adversely affected. A DMS execution context is an object that contains context information about the piece of work being performed at a particular moment in time. The type of context information carried by the DMS execution context may include the URL of the http request, the unique correlation key (ECID) assigned to that piece of work, etc - information that is useful for tracking requests though the system. The execution context does not carry user names, passwords or general application parameters. The DMS execution context should not be confused with application specific context objects, such as ADF-context or Faces-context, which are vital to the accurate execution of the application concerned.

Action: Contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

DMS-57004: Failed to initialize the DMS trace to be associated with DMS execution context {0}, that itself is associated with a request of resource {1}.

Cause: A problem has occurred in the initialization of the trace system for this request. This should not affect the processing of the servlet handling the request but will be a problem if the trace (aggregate, debug or triggered) data was of value to the system's administrator.

Action: If the trace of this request was important, and has been affected by this error, then contact Oracle Support Services
Level: 1

Type: WARNING

Impact: Other

DMS-57005: Failed to terminate the DMS trace associated with DMS execution context {0}, that itself is associated with a request of resource {1}.

Cause: A problem has occurred in the finalization of the trace system for this request. This should not affect the processing of the servlet handling the request but will be a problem if the trace (aggregate, debug or triggered) data was of value to the system's administrator.

Action: If the trace of this request was important, and has been affected by this error, then contact Oracle Support Services
Level: 1

Type: WARNING

Impact: Other

DMS-57006: Failed to deactivate the DMS execution context, {0}, associated with a request of resource {1}.

Cause: A problem has occurred in the termination of the DMS execution context in place during the processing of the HTTP request. This should not affect the servlet handling the request, but may result in an invalid execution context being in place for the processing of future requests and possibly prevent accurate trace data from being gathered.

Action: Contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

DMS-57007: Failed to url-decode a wrapped execution context ({0}) due to a problem in the decoding process itself: {1}

Cause: A problem has occurred while trying to url-decode a wrapped execution context found as a url-parameter. The consequence is that the execution context being passed from client to server can not be used. A failure in the DMS execution context feature does not generally result in a complete failure of the system or application making use of it, but it can result in misleading trace output or misleading correlation keys (ECID) in log messages: generally only the administrator will be aware of such changes in the behavior of an affected application.

Action: Determine if there is any code in the system that integrates with the Oracle DMS Context API (java package oracle.dms.context) but was not produced by Oracle. If there is no such code then contact Oracle Support Services. Otherwise scrutinize and test the non-Oracle code, and if necessary contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

DMS-57008: The execution context put in place at the start of the request, {0}, is not the execution context in place at the end of the request, {1}. The request is as follows: {2}

Cause: When enabled to do so DMS associates an execution context with the resources (typically a thread) assigned to process an incoming request. In this case the context that DMS assigned at the start of the processing is not the one in place at the end of the processing. At some point during the processing the context has been changed. This could result in the loss of the ability to correlate the work performed across the complete request lifecycle for this request. A failure in the DMS execution context feature does not generally result in a complete failure of the system or application making use of it, but it can result in misleading trace output or misleading correlation keys (ECID) in log messages: generally only the administrator will be aware of such changes in the behavior of an affected application.

Action: Determine if there is any code in the system that integrates with the Oracle DMS Context API (java package oracle.dms.context) but was not produced by Oracle. If there is no such code then contact Oracle Support Services. Otherwise scrutinize and test the non-Oracle code, and if necessary contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

DMS-57009: An error prevented selection of an appropriate execution context implementation for this environment - the feature will be disabled.

Cause: At the point of initialization DMS needs to determine the environment in which it is operating in order to select the most appropriate implementation of the execution context feature. An unexpected error has occurred during that process. The DMS execution context feature will be disabled.

Action: Review the error to see if it can be resolved and then restart the server.
Level: 1

Type: ERROR

Impact: Other

DMS-58002: Could not create trace output directory ({0}) - Disabling {1} traces.

Cause: An attempt to create a file system directory, into which trace files were to be written, has failed. Consequently no trace information can be saved and therefore, to save unnecessary burden on the system, trace information will not be collected.

Action: Check that the system user that owns the process has permissions to create such a directory. Check that the system has sufficient disk space to create a new directory.
Level: 1

Type: WARNING

Impact: Files

DMS-58005: ignoring exception: {0}

Cause: An unanticipated problem has occurred for which the runtime code can not take automatic remedial action.

Action: Refer to the base exception to see if there is a problem with the system that can be addressed (e.g. run low in disk space, run out of memory, etc).
Level: 1

Type: WARNING

Impact: Other

DMS-58006: Problem encountered while removing old files from trace output directories.

Cause: DMS was attempting to remove old files from the trace output directories but for some reason (see base exception) has failed.

Action: The system is unlikely to fail as a consequence of this error, but disk space will be used that would otherwise have been released. Refer to the base exception to see if the problem can be addressed, and consider deleting unrequired files manually (DMS no longer needs these old files so any or all of them can be removed).
Level: 1

Type: WARNING

Impact: Files

DMS-58007: Problem encountered when closing file and associated streams.

Cause: As part of the termination of a normal read or write operation on a file the file could not be closed.

Action: If a file can not be properly closed then the operating system's file-handle associated with that file may not be properly released. An operating system can manage only a finite number of file-handles and if they are not released then new file-handles can not be created. One consequence of a depletion of file-handles is that file input/outpt on the machine concerned may be forced to come to a stop. It is more likely, however, that this is a one-off problem and that Java will tidy up the file-handle internally. This type of problem suggests a problem with either the JVM, the operating system or the state of the machine on which they are running. Review the base exception to see if the issue can be resolved (e.g. memory issues, disk space issues, file access issues, etc.). In order to understand the scale of the problem continue to monitor the system for similar or related issues. If necessary stop and start the product to fully reinitialize the JVM on which it runs.
Level: 1

Type: WARNING

Impact: Files

DMS-58008: error writing trace data to disk

Cause: DMS has failed to create or use the objects required to write trace output to disk. The output intended to be written will be discarded.

Action: This type of problem suggests a problem with either the JVM, the operating system or the state of the machine on which they are running. Review the base exception to see if the issue can be resolved (e.g. memory issues, disk space issues, file access issues, etc.). In order to understand the scale of the problem continue to monitor the system for similar or related issues. If necessary stop and start the product to fully reinitialize the JVM on which it runs.
Level: 1

Type: WARNING

Impact: Other

DMS-58013: Problem encountered aggregating trace: {0}.

Cause: DMS has failed to perform the aggregation process on the trace data collected during the handling of this particular task or servlet request. A DMS trace is composed of a series of DMS trace events that represent an operation performed within DMS. Examples of trace events are: a sensor update, the start and end of an HTTP request. An aggregate trace is the result of aggregating trace data for tasks (typically HTTP requests) associated with the same URI. Failure to perform the aggregation processing for this task will mean that the summary data for the URI concerned will not be accurate.

Action: Review exception details and the log for any seemingly related messages. If the problem has come from the JVM itself: This type of problem suggests a problem with either the JVM, the operating system or the state of the machine on which they are running. Review the base exception to see if the issue can be resolved (e.g. memory issues, disk space issues, file access issues, etc.). In order to understand the scale of the problem continue to monitor the system for similar or related issues. If necessary stop and start the product to fully reinitialize the JVM on which it runs. Otherwise the problem is with the code written to run on the JVM: Determine if there is any code in the system that that integrates with the Oracle DMS Trace API (java package oracle.dms.trace) but was not produced by Oracle. If there is no such code then contact Oracle Support Services. Otherwise scrutinize and test the non-Oracle code in order to isolate the problem.
Level: 1

Type: WARNING

Impact: Other

DMS-58014: Failed to handle REQUEST_BEGIN for {0}. The trace will not be aggregated.

Cause: DMS did not find the trace event that marks the start of the series of trace events to be associated with an HTTP request. Without that particular trace event DMS can not be sure that the set of collected trace events will accurately represent the actions performed during that HTTP request and consequently will not process them further. Failure to perform the aggregation processing for this task will mean that the summary data for the URI concerned will not be accurate.

Action: Review exception details and the log for any seemingly related messages. If the problem has come from the JVM itself: This type of problem suggests a problem with either the JVM, the operating system or the state of the machine on which they are running. Review the base exception to see if the issue can be resolved (e.g. memory issues, disk space issues, file access issues, etc.). In order to understand the scale of the problem continue to monitor the system for similar or related issues. If necessary stop and start the product to fully reinitialize the JVM on which it runs. Otherwise the problem is with the code written to run on the JVM: Determine if there is any code in the system that that integrates with the Oracle DMS Trace API (java package oracle.dms.trace) but was not produced by Oracle. If there is no such code then contact Oracle Support Services. Otherwise scrutinize and test the non-Oracle code in order to isolate the problem.
Level: 1

Type: WARNING

Impact: Other

DMS-58015: Can not get the current task's execution context and therefore the trace events that occurred during this task's lifecycle can not be used to contribute to the aggregate trace associated with the task's URL.

Cause: In order to perform the process of trace aggregation for a completed task the execution context for that task is required. In this case the execution context could not be found; without the execution context object the trace aggregation process can not be performed. A DMS trace is composed of a series of DMS trace events that represent an operation performed within DMS. Examples of trace events are: a sensor update, the start and end of an HTTP request. An aggregate trace is the result of aggregating trace data for tasks (typically HTTP requests) associated with the same URI. Failure to perform the aggregation processing for this task will mean that the summary data for the URI concerned will not be accurate.

Action: Determine if there is any code in the system that that integrates with the Oracle DMS Trace API (java package oracle.dms.trace) but was not produced by Oracle. If there is no such code then contact Oracle Support Services. Otherwise scrutinize and test the non-Oracle code in order to isolate the problem.
Level: 1

Type: WARNING

Impact: Other

DMS-58016: Can not get the URI associated with the current thread's recent activities.

Cause: In order to perform the process of trace aggregation for a completed task the URI associated with that task is required. In this case the URI could not be found; without the URI the trace information collected cannot be aggregated. A DMS trace is composed of a series of DMS trace events that represent an operation performed within DMS. Examples of trace events are: a sensor update, the start and end of an HTTP request. An aggregate trace is the result of aggregating trace data for tasks (typically HTTP requests) associated with the same URI. Failure to perform the aggregation processing for this task will mean that the summary data for the URI concerned will not be accurate.

Action: Determine if there is any code in the system that that integrates with the Oracle DMS Trace API (java package oracle.dms.trace) but was not produced by Oracle. If there is no such code then contact Oracle Support Services. Otherwise scrutinize and test the non-Oracle code in order to isolate the problem.
Level: 1

Type: WARNING

Impact: Other

DMS-58017: The maximum number of allowed aggregates has already been reached. Traces referring to URLs not already being aggregated will not contribute to aggregate information.

Cause: In order to prevent too much memory being consumed by the DMS trace system the current request will not be added to the aggregate trace set because the maximum number of URIs for which trace data will be aggregated has already been reached. A DMS trace is composed of a series of DMS trace events that represent an operation performed within DMS. Examples of trace events are: a sensor update, the start and end of an HTTP request. An aggregate trace is the result of aggregating trace data for tasks (typically HTTP requests) associated with the same URI.

Action: If aggregate trace information is not required for this request there is no action required. Otherwise please review the value of the system property oracle.dms.trace.maxAggregates.
Level: 1

Type: WARNING

Impact: Other

DMS-58018: Cannot delete old trace file: {0}.

Cause: An attempt to delete a file system file has failed (the deletion attempt was intended to keep files organized and their number manageable). The system is unlikely to fail as a consequence of this error, but disk space will be used that would otherwise have been released.

Action: This type of problem suggests a problem with either the JVM, the operating system or the state of the machine on which they are running. Review the base exception to see if the issue can be resolved (e.g. memory issues, disk space issues, file access issues, etc.). In order to understand the scale of the problem continue to monitor the system for similar or related issues. If necessary stop and start the product to fully reinitialize the JVM on which it runs.
Level: 1

Type: WARNING

Impact: Files

DMS-58019: Cannot generate aggregate trace data because the trace system failed initialization.

Cause: (See message)

Action: Review the log files for reports of other problems relating to initialization failure. Where possible correct those other problems and restart the system. Failure of the trace subsystem should not affect the ability of the system to execute, but will prevent traces from being produced.
Level: 1

Type: WARNING

Impact: Other

DMS-58020: failure writing DMS configuration file {0}

Cause: An error occurred attempting to save the DMS configuration file.

Action: Check that the process has permission to write the configuration file. Review log files for more information on this issue.
Level: 1

Type: WARNING

Impact: Files

DMS-58021: failure loading DMS configuration file {0}

Cause: An error occurred attempting to load the DMS configuration file.

Action: Check that the process has permission to read the configuration file, and the file exists. Review log files for more information on this issue.
Level: 1

Type: WARNING

Impact: Files

DMS-58022: failure registering DMS configuration MBean {0}

Cause: An error occurred attempting to register the DMS configuration MBean.

Action: Check that the J2EE container is up. Review log files for more information.
Level: 1

Type: WARNING

Impact: Configuration

DMS-58023: There has been a failure activating the DMS configuration. Failed to close the event configuration file for server "{0}".

Cause: An error occurred attempting to activate the DMS configuration.

Action: Review the log files for more information.
Level: 1

Type: WARNING

Impact: Configuration

DMS-58024: cannot create a condition for filter {0}

Cause: A condition could not be created for the condition filter at runtime.

Action: Check that the filter has been configured correctly.
Level: 1

Type: WARNING

Impact: Configuration

DMS-58025: cannot instantiate class {0} for destination with id = {1}

Cause: A Destination could not be created at runtime.

Action: Check that the Destination has been configured correctly.
Level: 1

Type: WARNING

Impact: Configuration

DMS-58026: cannot not set property {0} on an instance of class {1} for destination with id = {2}

Cause: The configuration of a destination specified one or more properties to be set on the destination before the destination was used. A problem was encountered trying to set the property listed in the message the precise details of which are also shown in the message.

Action: Verify that the property exists on the class being instantiated as the destination, and that the value is legal for that property.
Level: 1

Type: WARNING

Impact: Configuration

DMS-58028: will not associate filter {0} and destination {1} - one or both are null or have null IDs.

Cause: (See message)

Action: Check the configuration of the filter and destination, and search the log file for other messages that may report problems creating instances of the filter or destination.
Level: 1

Type: WARNING

Impact: Configuration

DMS-58033: Can not associate a destination, id={0}, with a filter, id={1} if the filter declares that it will not pass any events.

Cause: An instance of a filter should declare the set of event types in which it has an interest. In this particular case the set is empty and thus the filter is apparently interested in no events at all. Such a filter serves no sensible purpose and therefore will be ignored.

Action: Check the log file for other error relating to this filter to see if there were problems in its construction. Also verify the configuration of the filter and its associated destination (some filters are created implicitly to cooperate with a destination, so the configuration may only specify details of the destination).
Level: 1

Type: WARNING

Impact: Configuration

DMS-58035: The required JRockit Flight Recorder classes can not be found. The JFRDestination can not function without them.

Cause: The JRockit Flight Recorder classes are only available on Oracle JRockit.

Action: Check that the system is running using JRockit or disable the JFRDestination declared within dms_config.xml
Level: 1

Type: WARNING

Impact: Other

DMS-58040: The JRockit FlightRecorder class is declaring that it is not the JRockit native implementation and thus DMS can not use it.

Cause: DMS only makes use of the JRockit FlightRecorder implementation that is native to JRockit. The FlightRecorder class available to DMS is apparently not a native implementation and will therefore not be used by DMS.

Action: This situation will not affect the runtime operation of the system, but in order to avoid the message being reported again either switch to using the JRockit JVM or remove eventRoutes from dms_config.xml that involve the JFRDestination.
Level: 1

Type: WARNING

Impact: Other

DMS-58041: The JRockit FlightRecorder class is declaring that it is not active and so DMS can not use it.

Cause: DMS can only make use of the JRockit FlightRecorder class if it is active. The FlightRecorder class is declaring that it is not active and therefore DMS will not make use of it.

Action: This situation will not affect the runtime operation of the system, but in order to avoid the message being reported again either switch to using the JRockit JVM or remove eventRoutes from dms_config.xml that involve the JFRDestination.
Level: 1

Type: WARNING

Impact: Other

DMS-58042: The DMS configuration file is invalid, and may not be viewed. No updates are allowed until the file has been fixed manually.

Cause: The DMS configuration file is invalid. No updates are allowed until the file has been fixed.

Action: Review the log files for more information, and correct the problem in the configuration file
Level: 1

Type: WARNING

Impact: Configuration

DMS-58045: DMS classic tracing will not be performed because the DMS context manager is disabled.

Cause: The classic trace features of DMS are dependent upon the DMS context manager being enabled. The DMS context manager is not enabled, and therefore the classic trace features can not operate.

Action: Review the java startup parameters to see if the DMS context manager has been disabled (check for properties with a prefix of 'oracle.dms.context')
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-58052: An instance of the {0} is already being used. It is not permitted to use more than one instance at a time.

Cause: (See message)

Action: Remove the current instance before attempting to put in place the new instance.
Level: 1

Type: WARNING

Impact: Configuration

DMS-58055: A failure has occurred updating the condition. Context value "{0}" is not of type "{1}".

Cause: An attempt was made to specify a data type that is not legal for the existing context value.

Action: Execute the command again, using a different data type.
Level: 1

Type: WARNING

Impact: Configuration

DMS-58056: Unable to create an event element.

Cause: There has been a problem parsing the element from the configuration.

Action: Contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Configuration

DMS-58057: There has been an error during activation.

Cause: There has been a problem activating the current configuration in the JVM.

Action: Review the cause(s) and action(s) of the nested error(s).
Level: 1

Type: ERROR

Impact: Configuration

DMS-58058: A failure has occurred parsing condition "{0}" when adding filter "{1}"

Cause: There has been a problem with the filter condition.

Action: Correct the syntax for the condition.
Level: 1

Type: WARNING

Impact: Configuration

DMS-58059: An event route exists using destinationID="{0}" and filter(s) "{1}". The destination cannot be removed.

Cause: An event route already exists using destinationID="{0}".

Action: Remove the event route(s) first, before removing the destination.
Level: 1

Type: WARNING

Impact: Configuration

DMS-58060: An event route exists using filterID="{0}" and destination(s) "{1}". The filter cannot be removed.

Cause: An event route already exists using filterID="{0}".

Action: Remove the event route(s) first, before removing the filter.
Level: 1

Type: WARNING

Impact: Configuration

DMS-58061: The class name "{0}" in destination "{1}" does not exist.

Cause: A class name has been specified for the destination, but the class cannot be found.

Action: Check the class name is spelled correctly.
Level: 1

Type: WARNING

Impact: Configuration

DMS-58062: The mandatory property "{0}" is not present in destination "{1}" for class "{2}".

Cause: The destination expected a mandatory property, but that property was not specified.

Action: Execute the command again, specifying the mandatory property, or change the destination class.
Level: 1

Type: WARNING

Impact: Configuration

DMS-58063: The class "{0}", used by destination "{1}", implements FilterProvider. Instances of "{0}" need not, and cannot be associated with user defined filters.

Cause: The class specified may not be used with a user defined filter.

Action: Specify a different class name in the destination.
Level: 1

Type: WARNING

Impact: Configuration

DMS-58064: The DMS event configuration document has failed to parse. The configuration is null.

Cause: There has been a problem generating the configuration from the configuration file.

Action: Check the dms_config.xml configuration file exists, has the correct permissions, and valid XML syntax. Consider reverting to a backup of the configuration file.
Level: 1

Type: ERROR

Impact: Configuration

DMS-58065: Either no condition, or no element, or no document has been passed to buildConditionElement(). Condition="{0}", Element="{1}".

Cause: There has been a problem extracting the condition from the filter.

Action: Check the condition, element and document passed to buildConditionElement are not null.
Level: 1

Type: WARNING

Impact: Configuration

DMS-58066: A null DMS configuration cannot be saved.

Cause: The configuration was null when attempting to activate it in the runtime.

Action: Review the server log, and check the server started successfully.
Level: 1

Type: WARNING

Impact: Configuration

DMS-58067: There are invalid arguments; filter ID="{0}". Check the id, event types and condition are valid for server "{1}".

Cause: One or more of the arguments passed are invalid, or have not been specified where required.

Action: Examine the syntax used for the command, identify the issue, and try again using the correct syntax.
Level: 1

Type: WARNING

Impact: Configuration

DMS-58068: No runtime configuration exists.

Cause: A problem occurred loading the runtime configuration from the dms_config.xml configuration file

Action: Review the server log, and check the server started successfully.
Level: 1

Type: WARNING

Impact: Configuration

DMS-58069: The configuration is invalid for server "{0}".

Cause: An invalid configuration has been detected.

Action: The dms_config.xml configuration file must be corrected manually before configuration changes are allowed.
Level: 1

Type: WARNING

Impact: Configuration

DMS-58070: The destination "{0}" is only valid on the Weblogic platform using the Oracle Corporation (JRocket) VM. The actual platform is "{1}" and VM is "{2}".

Cause: Either the platform is not Weblogic, or the VM is not the Oracle Corporation (JRocket) VM, or both.

Action: No action is required. The destination will be ignored and may be removed from the configuration file during the next update.
Level: 1

Type: WARNING

Impact: Configuration

DMS-58071: The following properties are not supported for destination {0}: {1}. The set of supported properties is: {2}.

Cause: The configuration for a destination specifies properties that the destination does not support.

Action: Correct the configuration by either removing the unsupported properties or correcting their names to match one of the supported properties.
Level: 1

Type: WARNING

Impact: Configuration

DMS-58072: Unable to instantiate DiagnosticsFramework. The DMSTraceProvider will not be able to add traced data to incidents.

Cause: A problem with the DiagnosticsFramework has prevented it from being used.

Action: Check log files for any reference to failures or errors in the DiagnosticsFramework, and if possible correct them.
Level: 1

Type: WARNING

Impact: Other

DMS-58073: Failed to create a logger to which DMS trace events can be logged.

Cause: A problem has been encountered creating a logger that is required by the DMSTraceProvider.

Action: Review the exception that prevented the logger from being created, and if possible correct it.
Level: 1

Type: WARNING

Impact: Other

31 DVT-02012 to DVT-26021

DVT-02012: Column {0} exceeds boundary {1}.

Cause: The specified column number was greater than the total number of columns.

Action: Get the total number of columns, by calling the getColumnCount method of the graph or of the column header in the pivot table. Then specify a column that does not exceed the total number of columns.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-02013: Row {0} exceeds boundary {1}.

Cause: The specified row number was greater than the total number of rows.

Action: Get the total number of rows, by calling the getRowCount method of the graph or of the column header in the pivot table. Then specify a row that does not exceed the total number of rows.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-02015: Slice {0} exceeds boundary {1}.

Cause: The specified slice number was greater than the total number of slices.

Action: Specify a slice that does not exceed the total number of slices.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-02016: Layer {0} exceeds boundary {1}.

Cause: The specified layer was greater than the total number of layers that are available on the given edge.

Action: Specify a layer that does not exceed the total number of layers.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-02017: Series {0} exceeds boundary {1}.

Cause: The specified series was greater than the total series that is available in the graph.

Action: Specify a zero-based series index that does not exceed the total series. The Graph.getDisplaySeries method should provide the number of series that are displayed in the graph. Or, if Graph.isDataRowShownAsASeries returns true, then Graph.getRowCount returns the number of series that can be displayed. If Graph.isDataRowShownAsASeries returns false, then Graph.getColumnCount returns the total number of series that can be displayed.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-02018: Edge {0} exceeds boundary {1}.

Cause: The specified edge was greater than the total number of edges that are available on the given edge. Valid edges for methods that require an edge are: DataDirector.COLUMN_EDGE, DataDirector.ROW_EDGE, and DataDirector.PAGE_EDGE.

Action: Specify a valid edge constant.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-02019: Current DataSource does not support required type: {0}.{1}.

Cause: The DataSource did not support the required type of data in its DataMap. For example, the view requested DataMap.DATA_GROUPSORT information, and the DataSource that the view uses did not supply group sort information.

Action: Request support for the required data types in the DataSource, or use a different DataSource.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-02020: DTD file cannot be found.

Cause: The specified DTD could not be found. The XML parser needed the DTD in order to validate XML files.

Action: Ensure that the specified DTD file exists, or disable XML validation. DTDs for Data Visualization components are in their respective packages. To turn off validation, call Dataview.setXMLValidated(false);.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-03000: No Mergeable object is provided.

Cause: No default Mergeable object was provided to resolve rules.

Action: Provide at least one default Mergeable object, so that rules can be resolved. For more information about Mergeable objects, see the Javadoc for the oracle.dss.rules.Mergeable interface.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-03001: attempt to call merge(Mergeable) on an incompatible Mergeable class

Cause: An attempt was made to merge incompatible Mergeable classes. Only Mergeable objects of the same class can be merged. For example, ViewStyle objects can be merged, but a ViewStyle cannot be merged with a ViewFormat.

Action: Merge two classes that are compatible. For more information, see the Javadoc for the oracle.dss.rules.RuleBundle class.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-06000: unexpected data error from Pivot Table data model

Cause: An unexpected exception was thrown by the Pivot Table's data model.

Action: Log a bug against the application. Verify that the Pivot Table's data model is configured properly.
Level: 1

Type: ERROR

Impact: Data

DVT-06001: no Converter for data type {0} during Pivot Table text formatting

Cause: The application could not create a Converter for a specific data type. The most likely reason was that a Converter was not registered for that data type.

Action: Log a bug against the application. Verify that the application can create a default Converter for all data types rendered by the Pivot Table.
Level: 1

Type: TRACE

Impact: Configuration

DVT-07001: cannot create Graph image

Cause: Under heavy loads, there was not enough memory to create the BufferedImage, or the Graphics instance from the BufferedImage. Therefore, the generated image file is empty.

Action: Reduce the memory load; for example, reduce the image size or allocate more memory to the JVM.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-08000: unexpected data error from Data Model

Cause: An invalid operation was performed by Data Model.

Action: Log a bug against the application. Verify that the Data model is configured properly.
Level: 1

Type: ERROR

Impact: Data

DVT-09006: cannot copy event: {0}

Cause: An error occurred while trying to copy the specified event.

Action: Invoke the printStackTrace method on the exception object to display the full error stack and to identify the root cause of the problem.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-09007: Measure argument must not be null in initCubeQuery.

Cause: A null measure list was passed to the initCubeQuery method.

Action: Pass in a valid list of measures to the initCubeQuery method.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-09008: Dimensions and measures arguments must not both be null in initQuery.

Cause: Arguments for dimensions and a measure list were both null when passed to the initQuery method.

Action: Pass in a valid value for either one or both of these arguments when calling the initQuery method.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-09011: Dimension is out of range in metadata cursor for edge and dimension: {0} and {1}.

Cause: The specified dimension was out of range in the method that was called for the specified edge and dimension arguments.

Action: Ensure that the dimension is valid when calling the method.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-09013: cannot create new instance of QueryManager or subclass when cloning

Cause: Application code could not call the constructor that takes a QueryManagerObject parameter when trying to clone an instance of QueryManager or a subclass of QueryManager.

Action: If the actual object is a subclass of QueryManager, then examine the subclass constructors for failure in the code that extends QueryManager.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-09016: cannot find property

Cause: The persistent XML file was not compatible with this object.

Action: Re-create the object.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-09017: cannot redo

Cause: There were no more operations on the stack to redo.

Action: No action is necessary.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-09032: The specified measure {0} is invalid.

Cause: A measure name was specified that cannot be found in the database.

Action: Ensure that all named measures exist in the database.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-09036: cannot undo

Cause: There were no more operations on the stack to undo.

Action: No action is necessary.
Level: 1

Type: ERROR

Impact: Programmatic

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-09044: illegal DataDirector type request

Cause: A relational DataDirector was requested for a nontabular query.

Action: Either call createCubeDataDirector, or set the QueryConstants.PROPERTY_TABULAR_QUERY property to true before requesting a relational data director.
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-10100: Cannot connect to the database. (Reason: See error {0})

Cause: There are a variety of possible reasons why the connection was not made.

Action: Check the cause and action text for the DVT error message that is specified after "Reason:".
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-22004: cannot create Gauge image

Cause: Under heavy loads, there was not enough memory to create the BufferedImage, or the Graphics instance from the BufferedImage. Therefore, the generated image file is empty.

Action: Reduce the memory load; for example, reduce the image size or allocate more memory to the JVM.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-23000: End date cannot be earlier than start date.

Cause: The end date specified for the Gantt chart was earlier than the specified start date.

Action: Specify a correct start date and end date for the Gantt chart.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-23001: The time unit in the major axis must be greater than the time unit in the minor axis.

Cause: The time unit specified in the major axis was not greater than the time unit specified in the minor axis. For example, if "days" was specified as the time unit for the minor axis, then the time unit specified in the major time axis must be greater than "days", such as "months", and not anything less, such as "hours".

Action: Ensure that the time unit in the major axis is greater than the time unit in the minor axis.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-23002: An invalid time scale is specified.

Cause: The specified time scale in the major or minor axis was not recognized.

Action: Specify a valid time scale for the axis.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-23003: End date of a task cannot be earlier than its start date. Start date: {0}, End date: {1}

Cause: The end date specified for the task was earlier than its start date.

Action: Check the data to ensure that the start date and end date are loaded correctly.
Level: 1

Type: WARNING

Impact: Data

DVT-23004: No tooltip keys or labels are specified.

Cause: No tooltip keys or labels were specified in the Gantt tag.

Action: Specify keys and labels for the tooltip to ensure that the tooltip is not empty.
Level: 1

Type: WARNING

Impact: Programmatic

DVT-23005: No legend keys or labels are specified.

Cause: No legend keys or labels were specified in the Gantt tag.

Action: Specify keys and labels for the legend to ensure that the legend is not empty.
Level: 1

Type: WARNING

Impact: Programmatic

DVT-23006: The number of tooltip keys does not match the number of tooltip labels.

Cause: The number of tooltip keys did not match the number of tooltip labels specified in the Gantt tag.

Action: Ensure that the number of tooltip keys specified in the Gantt tag (tooltipKeys attribute) matches the tooltip labels specified in the Gantt tag (tooltipLabels attribute).
Level: 1

Type: WARNING

Impact: Programmatic

DVT-23007: The number of legend keys does not match the number of legend labels.

Cause: The number of legend keys did not match the number of legend labels specified in the Gantt tag.

Action: Ensure that the number of legend keys specified in the Gantt tag (legendKeys attribute) matches the legend labels specified in the Gantt tag (legendKeyLabels attribute).
Level: 1

Type: WARNING

Impact: Programmatic

DVT-23008: The start date of the task is out of range. Value: {0}

Cause: The start and end date of a task was outside of the time range specified for the Gantt chart.

Action: No action necessary, if it is okay not to show the task. Otherwise, verify data is correct or specify a wider time range for the Gantt chart (using the startTime and endTime attributes)
Level: 1

Type: WARNING

Impact: Data

DVT-23009: cannot find format for type {0}; skipping task: {1}

Cause: No format for type {0} was registered.

Action: Register a TaskbarFormat with the TaskbarFormatManager for the type indicated.
Level: 1

Type: WARNING

Impact: Programmatic

DVT-23010: The specified day of the week is invalid. Value: {0}

Cause: The day of the week specified was not recognized.

Action: Specify a value for the day of the week that is one of these seven constants from the java.util.Calendar class: Calendar.SUNDAY, Calendar.MONDAY, Calendar.TUESDAY, Calendar.WEDNESDAY, Calendar.THURSDAY, Calendar.FRIDAY, Calendar.SATURDAY.
Level: 1

Type: WARNING

Impact: Programmatic

DVT-23011: The value specified for alignment is invalid. Task ID: {0}

Cause: The alignment value specified for the label or icon was invalid.

Action: Specify a value for alignment that is one of these three constants from the oracle.adf.view.faces.bi.component.gantt.GanttConstants class: GanttConstants.LEFT, GanttConstants.RIGHT, GanttConstants.INSIDE.
Level: 1

Type: WARNING

Impact: Programmatic

DVT-23012: GanttDropTarget can only be attached to a Gantt component.

Cause: The GanttDropTarget tag was added as a child of a non-Gantt component.

Action: Ensure that the GanttDropTarget tag is a child tag of either a Project Gantt or Scheduling Gantt component.
Level: 1

Type: WARNING

Impact: Programmatic

DVT-23013: The start date of a task is null.

Cause: The start date of a task was null.

Action: Check the data to ensure that the start date is not null.
Level: 1

Type: WARNING

Impact: Data

DVT-23014: The task ID is null.

Cause: The task ID or split task ID was null.

Action: Check the data to ensure that the task ID or split task ID is not null.
Level: 1

Type: WARNING

Impact: Data

DVT-23015: The next date cannot be earlier than the previous date.

Cause: The next date returned by custom timescale was earlier than the previous date.

Action: Specify a correct next date.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-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

32 ECSF-10001 to ECSF-13310

ECSF-10001: Error: {0}

Cause: An error occurred.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

ECSF-10002: unexpected error. Cmd {0} fails.

Cause: An unexpected error occurred.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10003: I/O error when reading input.

Cause: An I/O error occurred.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10004: cannot access system.console to obtain password securely

Cause: System.console was not available.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10005: invalid command; cannot connect

Cause: An invalid command was specified.

Action: Specify a valid command.
Level: 1

Type: ERROR

Impact: Process

ECSF-10006: not connected; cannot execute command

Cause: A command was issued before a connection was made.

Action: Issue the CONNECT command before proceeding.
Level: 1

Type: ERROR

Impact: Process

ECSF-10007: Command {0} is invalid.

Cause: An invalid command was specified.

Action: Specify a valid command.
Level: 1

Type: ERROR

Impact: Process

ECSF-10008: invalid command syntax

Cause: A command with invalid syntax was issued.

Action: Specify the command using the correct syntax.
Level: 1

Type: ERROR

Impact: Process

ECSF-10009: already connected; cannot execute command

Cause: User was already connected.

Action: Disconnect before attempting to reconnect.
Level: 1

Type: ERROR

Impact: Process

ECSF-10010: already disconnected; cannot execute command

Cause: User was already disconnected.

Action: Reconnect before attempting to disconnect.
Level: 1

Type: ERROR

Impact: Process

ECSF-10011: already managing an instance; cannot execute command

Cause: The command was issued while an instance was already being managed.

Action: Specify a valid command.
Level: 1

Type: ERROR

Impact: Process

ECSF-10012: Invalid ID passed in for {0}. ID value must be a number.

Cause: The ID specified was not a number.

Action: Specify a valid ID.
Level: 1

Type: ERROR

Impact: Process

ECSF-10013: command not issued in an engine instance context; cannot execute command

Cause: The command was not issued from within an engine instance context.

Action: Manage an instance with the MANAGE command before proceeding.
Level: 1

Type: ERROR

Impact: Process

ECSF-10014: command not initialized; cannot execute command

Cause: An invalid command was issued.

Action: Specify a valid command.
Level: 1

Type: ERROR

Impact: Process

ECSF-10015: searchable object {0} already active; cannot execute command

Cause: Activate command was issued while searchable object was already activated.

Action: Specify a valid command.
Level: 1

Type: ERROR

Impact: Process

ECSF-10016: searchable object {0} already inactive; cannot execute command

Cause: Deactivate was issued while searchable object was already deactivated.

Action: Specify a valid command.
Level: 1

Type: ERROR

Impact: Process

ECSF-10017: searchable object {0} not deployed; cannot execute command

Cause: Requested command could not be performed.

Action: Specify a valid command.
Level: 1

Type: ERROR

Impact: Process

ECSF-10018: searchable object {0} already deployed; cannot execute command

Cause: The command was issued while searchable object was already deployed.

Action: Specify a valid command.
Level: 1

Type: ERROR

Impact: Process

ECSF-10019: cannot set up context

Cause: An error occurred while setting up the context.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10020: {0} {1} is currently deployed and cannot be deleted.

Cause: The requested command could not be performed.

Action: Specify a valid command.
Level: 1

Type: ERROR

Impact: Process

ECSF-10021: {0} {1} is currently deployed and cannot be updated.

Cause: The requested command could not be performed.

Action: Specify a valid command.
Level: 1

Type: ERROR

Impact: Process

ECSF-10022: The searchable object with id {0} cannot be removed from search category {1}, which is currently deployed.

Cause: The command was issued on a deployed search category.

Action: Undeploy the search category before you remove the searchable object from it.
Level: 1

Type: ERROR

Impact: Process

ECSF-10023: The searchable object with id {0} cannot be added to search category {1}, which is currently deployed.

Cause: The command was issued on a deployed search category.

Action: Undeploy the search category before you add the searchable object to it.
Level: 1

Type: ERROR

Impact: Process

ECSF-10024: cannot find {0} with ID {1}

Cause: The requested command could not be performed.

Action: Specify a valid object.
Level: 1

Type: ERROR

Impact: Process

ECSF-10025: {0} is invalid parameter; cannot execute command

Cause: An invalid parameter was specified.

Action: Specify a valid parameter.
Level: 1

Type: ERROR

Impact: Process

ECSF-10026: the searchable object with id {0} already associated with schedule {1}; cannot execute command

Cause: The command was issued while the searchable object was already associated to a schedule.

Action: Object can only be associated with one schedule.
Level: 1

Type: ERROR

Impact: Process

ECSF-10027: the searchable object with id {0} is not associated with an instance; cannot execute command

Cause: The command was issued while the searchable object was not associated with an instance.

Action: Associate the searchable object with an instance before proceeding.
Level: 1

Type: ERROR

Impact: Process

ECSF-10028: the searchable object with id {0} is not associated with category id {1}; cannot execute command

Cause: The command was issued while the searchable object was not associated with the category.

Action: Associate the searchable object with a category before proceeding.
Level: 1

Type: ERROR

Impact: Process

ECSF-10029: the searchable object {0} is not deployed; cannot execute command

Cause: An attempt was made to associate an undeployed searchable object.

Action: Deploy the searchable object to SES before proceeding.
Level: 1

Type: ERROR

Impact: Process

ECSF-10030: searchable object {0} activated; cannot execute command

Cause: An attempt was made to undeploy the searchable object while it was activated.

Action: Deactivate the searchable object before proceeding.
Level: 1

Type: ERROR

Impact: Process

ECSF-10031: index schedule {0} not deployed; cannot execute command

Cause: An attempt was made to start the index schedule before it was deployed.

Action: Deploy the index schedule before proceeding.
Level: 1

Type: ERROR

Impact: Process

ECSF-10032: searchable objects not associated with {0} {1}; cannot execute command

Cause: An attempt was made to deploy without associated searchable objects.

Action: Associate one or more searchable objects before proceeding.
Level: 1

Type: ERROR

Impact: Process

ECSF-10033: the searchable object {0} is not associated with the instance {1}

Cause: An attempt was made to remove the searchable object from an instance that it is not associated with.

Action: Specify a valid command.
Level: 1

Type: ERROR

Impact: Process

ECSF-10034: invalid value {0} passed in for field {1}, value must be of type {2}

Cause: Invalid values were entered.

Action: Specify a valid value.
Level: 1

Type: ERROR

Impact: Process

ECSF-10035: Valid value for {0} should be of type {1}.

Cause: An invalid value was entered.

Action: Specify a valid value.
Level: 1

Type: ERROR

Impact: Process

ECSF-10036: Valid values for {0} are {1} or {2}.

Cause: Invalid values were entered.

Action: Specify a valid value.
Level: 1

Type: ERROR

Impact: Process

ECSF-10037: {0} is not a valid LOV value for field {1}.

Cause: An invalid value was entered.

Action: Specify a valid value.
Level: 1

Type: ERROR

Impact: Process

ECSF-10038: The value entered is too long for field {0}. The value must be less than {1} characters.

Cause: An invalid value was entered.

Action: Specify a valid value.
Level: 1

Type: ERROR

Impact: Process

ECSF-10039: invalid field name. {0} does not exist in {1}.

Cause: An invalid field name was entered.

Action: Specify a valid field name.
Level: 1

Type: ERROR

Impact: Process

ECSF-10040: field {0} in {1} not updatable

Cause: An attempt was made to update a non-updatable field.

Action: Do not attempt to update this field.
Level: 1

Type: ERROR

Impact: Process

ECSF-10041: cannot set field {0} in {1} during {2}

Cause: An attempt was made to set a field when this action was not allowed.

Action: Specify a valid command.
Level: 1

Type: ERROR

Impact: Process

ECSF-10042: The following required fields must contain values.

Cause: Values were not set for all the required fields.

Action: Set values for all the required fields before proceeding.
Level: 1

Type: ERROR

Impact: Process

ECSF-10043: Instance {0} is being managed; Use UNMANAGE before deleting the instance.

Cause: An attempt was made to delete a managed instance.

Action: Unmanage the instance before deleting it.
Level: 1

Type: ERROR

Impact: Process

ECSF-10044: {0} are not found.

Cause: The object was not found.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10045: scope {LOCAL | GLOBAL} not found

Cause: The scope was not found.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10046: searchable object not activated

Cause: The requested command could not be performed.

Action: Specify a valid command.
Level: 1

Type: ERROR

Impact: Process

ECSF-10047: the searchable object has not been associated

Cause: The requested command could not be performed.

Action: Specify a valid command.
Level: 1

Type: ERROR

Impact: Process

ECSF-10048: cannot connect. Use CONNECT command to try again.

Cause: The requested command could not be performed.

Action: Specify a valid command.
Level: 1

Type: ERROR

Impact: Process

ECSF-10049: object not created

Cause: The requested command could not be performed.

Action: Specify a valid command.
Level: 1

Type: ERROR

Impact: Process

ECSF-10050: searchable object not deactivated

Cause: The requested command could not be performed.

Action: Specify a valid command.
Level: 1

Type: ERROR

Impact: Process

ECSF-10051: object not deleted

Cause: The requested command could not be performed.

Action: Specify a valid command.
Level: 1

Type: ERROR

Impact: Process

ECSF-10052: object not deployed

Cause: The requested command could not be performed.

Action: Specify a valid command.
Level: 1

Type: ERROR

Impact: Process

ECSF-10053: cannot disconnect

Cause: The requested command could not be performed.

Action: Specify a valid command.
Level: 1

Type: ERROR

Impact: Process

ECSF-10054: cannot import

Cause: The requested command could not be performed.

Action: Specify a valid command.
Level: 1

Type: ERROR

Impact: Process

ECSF-10055: context for instance not created

Cause: The requested command could not be performed.

Action: Specify a valid command.
Level: 1

Type: ERROR

Impact: Process

ECSF-10056: {0} not registered.

Cause: The requested command could not be performed.

Action: Specify a valid command.
Level: 1

Type: ERROR

Impact: Process

ECSF-10057: searchable object not disassociated

Cause: The requested command could not be performed.

Action: Specify a valid command.
Level: 1

Type: ERROR

Impact: Process

ECSF-10058: parameter not updated

Cause: The requested command could not be performed.

Action: Specify a valid command.
Level: 1

Type: ERROR

Impact: Process

ECSF-10059: schedule not started

Cause: The requested command could not be performed.

Action: Specify a valid command.
Level: 1

Type: ERROR

Impact: Process

ECSF-10060: schedule not stopped

Cause: The requested command could not be performed.

Action: Specify a valid command.
Level: 1

Type: ERROR

Impact: Process

ECSF-10061: object not undeployed

Cause: The requested command could not be performed.

Action: Specify a valid command.
Level: 1

Type: ERROR

Impact: Process

ECSF-10062: instance context not reset

Cause: The requested command could not be performed.

Action: Specify a valid command.
Level: 1

Type: ERROR

Impact: Process

ECSF-10063: object not updated

Cause: The requested command could not be performed.

Action: Specify a valid command.
Level: 1

Type: ERROR

Impact: Process

ECSF-10064: cannot find file {0}; automation aborted

Cause: The file could not be found.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10065: cannot load database driver

Cause: The database driver could not be found.

Action: Ensure that the database driver is available in the class path.
Level: 1

Type: ERROR

Impact: Process

ECSF-10066: cannot connect to database

Cause: The database connection could not be established.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10067: database connection not released

Cause: The database connection could not be released.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10068: Frequency Type cannot be null.

Cause: A null value was entered for Frequency Type.

Action: Set Frequency Type to a non-null value.
Level: 1

Type: ERROR

Impact: Data

ECSF-10069: invalid Time Between Launches value for hourly schedule; valid values are from 1 to 23.

Cause: An invalid Time Between Launches value was entered for the hourly schedule.

Action: Enter a Time Between Launches value from 1 to 23 for the hourly schedule.
Level: 1

Type: ERROR

Impact: Data

ECSF-10070: invalid Time Between Launches value for daily schedule; valid values are from 1 to 99.

Cause: An invalid Time Between Launches value was entered for the daily schedule.

Action: Enter a Time Between Launches value from 1 to 99 for the daily schedule.
Level: 1

Type: ERROR

Impact: Data

ECSF-10071: invalid Time Between Launches value for the weekly/monthly schedule; valid values are from 1 to 12.

Cause: An invalid Time Between Launches value was entered for the weekly/monthly schedule.

Action: Enter a Time Between Launches value from 1 to 12 for the weekly/monthly schedule.
Level: 1

Type: ERROR

Impact: Data

ECSF-10072: invalid Schedule Launch Day value for weekly schedule; valid values are from Monday to Sunday.

Cause: An invalid Schedule Launch Day value was entered for the weekly schedule.

Action: Enter a Schedule Launch Day value from Monday to Sunday for the weekly schedule.
Level: 1

Type: ERROR

Impact: Data

ECSF-10073: invalid Schedule Launch Day value for monthly schedule; valid values are from 1 to 31.

Cause: An invalid Schedule Launch Day value was entered for the monthly schedule.

Action: Enter a Schedule Launch Day value from 1 to 31.
Level: 1

Type: ERROR

Impact: Data

ECSF-10074: invalid Schedule Launch Time value; valid values are from 1:00 AM to 12:00 AM.

Cause: An invalid Schedule Launch Time value was entered.

Action: Enter a Schedule Launch Time value from 1:00 AM to 12:00 AM.
Level: 1

Type: ERROR

Impact: Data

ECSF-10076: the searchable object with id {0} is not associated with a schedule; cannot execute command

Cause: The command was issued while the searchable object was not associated with a schedule.

Action: Associate the searchable object with a schedule before proceeding.
Level: 1

Type: ERROR

Impact: Process

ECSF-10077: The searchable object with id {0} cannot be removed from schedule {1}, which is currently deployed.

Cause: The command was issued on a deployed index schedule.

Action: Undeploy the schedule before removing the searchable object.
Level: 1

Type: ERROR

Impact: Process

ECSF-10078: The searchable object with id {0} cannot be added to schedule {1}, which is currently deployed.

Cause: The command was issued on a deployed index schedule.

Action: Undeploy the schedule before adding the searchable object.
Level: 1

Type: ERROR

Impact: Process

ECSF-10079: The searchable object {0} is not associated with the schedule {1}

Cause: An attempt was made to remove the searchable object from a schedule that it is not associated with.

Action: Specify a valid command.
Level: 1

Type: ERROR

Impact: Process

ECSF-10080: the searchable object with id {0} is already associated with category {1}; cannot execute command

Cause: The command was issued while the searchable object was already associated to a category.

Action: Object can only be associated with one category.
Level: 1

Type: ERROR

Impact: Process

ECSF-10081: schedule {0} already deployed; cannot execute command

Cause: The command was issued while schedule was already deployed.

Action: Specify a valid command.
Level: 1

Type: ERROR

Impact: Process

ECSF-10082: category {0} already deployed; cannot execute command

Cause: The command was issued while category was already deployed.

Action: Specify a valid command.
Level: 1

Type: ERROR

Impact: Process

ECSF-10101: Searchable object {0} cannot be found; cannot deploy searchable object.

Cause: An invalid searchable object was specified.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10102: Search category {0} cannot be found; cannot deploy search category.

Cause: An invalid search category was specified.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10103: Searchable object {0} cannot be found; cannot undeploy searchable object.

Cause: An invalid searchable object was specified.

Action: Ensure that the searchable object is valid.
Level: 1

Type: ERROR

Impact: Process

ECSF-10104: Search category {0} cannot be found; cannot undeploy search category.

Cause: An invalid search category was specified.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10105: cannot deploy searchable object {0} to SES

Cause: An attempt was made to deploy a searchable object to SES. This is not allowed.

Action: Check the exception message for more information.
Level: 1

Type: ERROR

Impact: Process

ECSF-10106: cannot deploy search category {0} to SES

Cause: An attempt was made to deploy a search category to SES. This is not allowed.

Action: Check the exception message for more information.
Level: 1

Type: ERROR

Impact: Process

ECSF-10107: Search category {0} contains no searchable objects; cannot deploy search category.

Cause: An attempt was made to deploy a search category containing no searchable objects.

Action: Ensure that one or more searchable objects are associated with the search category before deploying it.
Level: 1

Type: ERROR

Impact: Process

ECSF-10108: cannot deploy index schedule {0}

Cause: An error occurred while deploying the index schedule.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10109: cannot undeploy searchable object {0}

Cause: Searchable object did not exist in SES.

Action: Check the exception message for more information.
Level: 1

Type: ERROR

Impact: Process

ECSF-10110: cannot undeploy search category {0}

Cause: Search category did not exist in SES.

Action: Check the exception message for more information.
Level: 1

Type: ERROR

Impact: Process

ECSF-10111: cannot undeploy index schedule {0}

Cause: Index schedule did not exist in SES.

Action: Check the exception message for more information.
Level: 1

Type: ERROR

Impact: Process

ECSF-10112: Searchable object {0} is deployed, but LastTimeCrawled cannot be set.

Cause: LastTimeCrawled could not be set for the searchable object in the database.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10113: cannot register identity plug-in to SES for user {0}

Cause: An error occurred while registering the identity plug-in.

Action: Check the exception message for more information.
Level: 1

Type: ERROR

Impact: Process

ECSF-10114: cannot start schedule {0} on engine instance {1}; schedule cannot be started in its current state: {2}

Cause: An attempt was made to start a schedule with status Launching or Executing or Stopping.

Action: Ensure that the schedule is not in a Launching, Executing, or Stopping state.
Level: 1

Type: ERROR

Impact: Process

ECSF-10115: cannot stop schedule {0} on engine {1}; schedule cannot be stopped in its current state: {2}

Cause: An attempt was made to stop a schedule with status Failed or Scheduled or Stopping.

Action: Ensure that the schedule is not in a Failed, Scheduled, or Stopping state.
Level: 1

Type: ERROR

Impact: Process

ECSF-10116: cannot start schedule {0} on engine instance {1}

Cause: An error occurred while starting the schedule.

Action: Check the exception message for more information.
Level: 1

Type: ERROR

Impact: Process

ECSF-10117: cannot stop schedule {0} on engine instance {1}

Cause: An error occurred while stopping the schedule.

Action: Check the exception message for more information.
Level: 1

Type: ERROR

Impact: Process

ECSF-10118: cannot get search categories from SES; SES_QUERY_SERVICE parameter for the engine instance cannot be null.

Cause: The proxy URL for the engine instance was missing.

Action: Ensure that the SES_QUERY_SERVICE parameter is set for the engine instance.
Level: 1

Type: ERROR

Impact: Process

ECSF-10119: cannot get search categories from SES

Cause: An error occurred while getting the search categories from the SES.

Action: Check the exception message for more information.
Level: 1

Type: ERROR

Impact: Process

ECSF-10120: cannot get SES session for engine {0}

Cause: An error occurred while getting the SES session.

Action: Check the exception message for more information.
Level: 1

Type: ERROR

Impact: Process

ECSF-10121: cannot get status for schedule {0} on engine instance {1}

Cause: An error occurred while getting this schedule status from the SES.

Action: Check the exception message for more information.
Level: 1

Type: ERROR

Impact: Data

ECSF-10122: cannot get schedules for engine instance {0}

Cause: An error occurred while getting the schedules from the SES.

Action: Check the exception message for more information.
Level: 1

Type: ERROR

Impact: Data

ECSF-10123: cannot get schedule {0} on engine instance {1}

Cause: An error occurred while getting this schedule from the SES.

Action: Check the exception message for more information.
Level: 1

Type: ERROR

Impact: Data

ECSF-10124: The {0} parameter for the engine instance cannot be null.

Cause: One of the service URL parameter value was null or invalid.

Action: Ensure that all service URL parameters are set in the engine instance.
Level: 1

Type: ERROR

Impact: Process

ECSF-10125: cannot initialize deployment manager

Cause: An error occurred during initialization of deployment manager.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10126: cannot find security plug-in class for searchable object {0}

Cause: No security plug-in class was defined for the searchable object.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10127: cannot release proxy session

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

ECSF-10128: invalid repetitive interval for the index schedule

Cause: Valid schedule interval was not specified.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10129: cannot log on to the SES server

Cause: Invalid login credentials were entered.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Security

ECSF-10130: cannot find view object {0}

Cause: The view object did not exist in the deployed application.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10131: cannot log out of SES session

Cause: An error occurred during SES proxy service logout operation.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Security

ECSF-10132: cannot find SES reference for search category {0}

Cause: One or more of the search categories bound to this query did not exist on the SES instance.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10133: The access URL length is greater than max 740 characters allowed by SES. Truncating the access URL by excluding stored attributes. Action: {0} in SO: {1}.

Cause: The access URL exceeded 740 characters in length.

Action: Ensure that the SearchAction definition is properly configured.
Level: 1

Type: WARNING

Impact: Data

ECSF-10134: cannot convert date {0} for attribute {1} in searchable object {2} to format: EEE MMM dd HH:mm:ss z yyyy

Cause: The date in the attribute was formatted incorrectly.

Action: Ensure that the attribute values are in the correct format.
Level: 1

Type: ERROR

Impact: Process

ECSF-10135: cannot convert number {0} to BigDecimal format

Cause: The number in the attribute was formatted incorrectly.

Action: Ensure that the attribute values are in the correct format.
Level: 1

Type: ERROR

Impact: Process

ECSF-10136: cannot find data groups on SES instance {0}

Cause: Data groups were not found on this SES instance.

Action: Ensure that valid data groups are created on the SES instance.
Level: 1

Type: ERROR

Impact: Data

ECSF-10137: Field {0} does not exist on the search category used for this query.

Cause: A nonexistent field was used in the query.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10138: cannot generate redirect URL for action {0}

Cause: Null values were specified for the primary keys.

Action: Ensure that the values for the primary keys are not null.
Level: 1

Type: ERROR

Impact: Process

ECSF-10139: unexpected ECSF Query Error: {0}

Cause: An unexpected query error occurred.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10140: cannot log in to SES at {2} with proxy name {0} for user {1}

Cause: An error occurred during SES proxy service login operation.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Security

ECSF-10141: Security service is not responding; cannot execute query.

Cause: The security service was not responding.

Action: Retry the query. If the same problem occurs, then contact the system administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10142: cannot re-query SES after session reset

Cause: The security service was not running on the ECSF server.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10143: cannot update searchable object {0} in SES

Cause: Searchable object could not be updated in the SES.

Action: Check the exception message for more information.
Level: 1

Type: ERROR

Impact: Process

ECSF-10144: cannot update spelling correction flag in SES

Cause: An error occurred while setting the spelling correction flag.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10145: cannot retrieve query configuration from SES

Cause: An error occurred while retrieving the query configuration.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10146: The source attribute in {0} with name {1} and type {2} conflicts with the attributes defined in these sources: {3}

Cause: An error occurred while deploying the searchable object.

Action: Change the name of the conflicting source attribute.
Level: 1

Type: ERROR

Impact: Process

ECSF-10147: The source attribute in {0} with name {1} and type {2} conflicts with the attribute defined in ses with type {3}. This attribute is not being used by any sources.

Cause: An error occurred while deploying the searchable object.

Action: Change the name of the conflicting source attribute or manually delete the orphaned source attribute.
Level: 1

Type: ERROR

Impact: Process

ECSF-10148: The ECSF Property 'oracle.ecsf.recent.search.max.num' is set to an invalid value: {0}. Recent Search will be disabled.

Cause: The ECSF Property oracle.ecsf.recent.search.max.num has an invalid value.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10149: Recent Search is disabled, this operation is currently unsupported.

Cause: Recent Search has been disabled.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10201: cannot create {0} {1}

Cause: An error occurred while creating a new record in the database.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10202: cannot update {0} {1}

Cause: An error occurred while updating the record in the database.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10203: cannot delete {0} {1}

Cause: An error occurred while deleting the record from the database.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10204: cannot select {0} {1}

Cause: An error occurred while executing the SELECT statement against the database.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10205: The global parameters can not be listed.

Cause: An error occurred while executing the SELECT statement against the database.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10206: cannot remove searchable object {0} from search category {1}

Cause: An error occurred while deleting the record from the ECSF_SIO_SIG_INT table.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10207: cannot associate searchable object {0} to search category {1}

Cause: An error occurred while associating the searchable object to the search category.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10208: cannot commit current transaction

Cause: An error occurred while committing the current transaction.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10209: cannot roll back current transaction

Cause: An error occurred during roll back operation.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10210: {0} of {1} does not result in a single row in the database for ID {2} {3} - rows {4}.

Cause: The return value of the executeUpdate SQL operation was not equal to one.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10212: Searchable Object {1} is deployed in SES server; cannot delete search engine instance {0}.

Cause: An attempt was made to delete the search engine instance while a searchable object associated with the instance was deployed on the SES server.

Action: Undeploy the searchable object before deleting the search engine instance.
Level: 1

Type: ERROR

Impact: Process

ECSF-10213: Search category {1} is deployed in SES server; cannot delete search Engine Instance {0}.

Cause: An attempt was made to delete the search engine instance while a search category associated with the instance was deployed on the SES server.

Action: Undeploy the search category before deleting the search engine instance.
Level: 1

Type: ERROR

Impact: Process

ECSF-10214: Index schedule {1} is deployed on SES server; cannot delete search engine instance {0}.

Cause: An attempt was made to delete the search engine instance while an index schedule associated with the instance was deployed on the SES server.

Action: Undeploy the index schedule before deleting the search engine instance.
Level: 1

Type: ERROR

Impact: Process

ECSF-10215: No searchable objects are associated with index schedule {0}; cannot deploy.

Cause: An attempt was made to deploy an index schedule that had no searchable objects associated with it.

Action: Associate one or more searchable objects with the index schedule before deploying it.
Level: 1

Type: ERROR

Impact: Process

ECSF-10216: cannot list global parameters

Cause: An error occurred while retrieving the global parameters from the database.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10217: cannot update the parameter

Cause: An error occurred while updating the parameter in the database.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10218: cannot list search engine instances

Cause: An error occurred while retrieving the search engine instances from the database.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10219: cannot update the search engine instance

Cause: An error occurred while updating the search engine instance record in the database.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10220: cannot create the search engine instance

Cause: An error occurred while creating the search engine instance record in the database.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10221: cannot delete the search engine instance

Cause: An error occurred while deleting the search engine instance record from the database.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10222: cannot register the identity plug-in on this SES instance

Cause: An error occurred while registering the identity plug-in on the SES instance.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10223: cannot list search engine types

Cause: An error occurred while retrieving the search engine types from the database.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10224: cannot create the searchable object

Cause: A record in the ECSF_SEARCH_INDEX_OBJECT table in the database could not be created.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10225: cannot delete the searchable object

Cause: A record from the ECSF_SEARCH_INDEX_OBJECT table in the database could not be deleted.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10226: cannot update the searchable object

Cause: A record in the ECSF_SEARCH_INDEX_OBJECT table in the database could not be updated.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10227: cannot list searchable objects that are not associated with any engine instance

Cause: An attempt was made to get a list of searchable objects that were not associated with any engine instances.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10228: cannot deploy the searchable object to SES

Cause: There was an error deploying this searchable object to SES.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10229: cannot undeploy the searchable object from SES

Cause: There was an error undeploying this searchable object from SES.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10230: cannot create a search category

Cause: A record in the ECSF_SEARCH_INDEX_GROUP table in the database could not be created.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10231: cannot delete the search category

Cause: A record from the ECSF_SEARCH_INDEX_GROUP table in the database could not be deleted.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10232: cannot update the search category

Cause: A record in the ECSF_SEARCH_INDEX_GROUP table in the database could not be updated.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10233: cannot associate searchable object to a search category

Cause: A record in the ECSF_SIO_SIG_INT table in the database could not be created to associate the searchable object with the search category.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10234: cannot remove searchable object from a search category

Cause: A record from the ECSF_SIO_SIG_INT table in the database could not be deleted.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10235: cannot deploy the search category

Cause: There was an error deploying this search category to SES.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10236: cannot undeploy the search category

Cause: There was an error undeploying this search category from SES.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10237: cannot import external search categories

Cause: There was an error importing external categories from SES.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10238: cannot create the index schedule

Cause: A record in the ECSF_INDEX_SCHEDULE table in the database could not be created.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10239: cannot update the index schedule

Cause: A record in the ECSF_INDEX_SCHEDULE table in the database could not be updated.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10240: cannot delete the index schedule

Cause: A record from the ECSF_INDEX_SCHEDULE table in the database could not be deleted.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10241: cannot deploy the index schedule

Cause: There was an error deploying this index schedule to SES.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10242: cannot undeploy the index schedule

Cause: There was an error undeploying this index schedule from SES.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10243: cannot start the index schedule

Cause: There was an error while attempting to start the schedule operation.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10244: cannot stop the index schedule

Cause: There was an error while attempting to stop the schedule operation.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10245: cannot localize the connection

Cause: An error occurred while localizing the connection.

Action: Contact the database administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10246: cannot save the password to the credential store

Cause: The password for the given user on the engine instance could not be saved.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10247: unknown error while validating a customized field

Cause: An unknown error occurred during validation of a customized field expression.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10248: cannot validate the customized title

Cause: The customized title expression was not valid.

Action: Use a valid expression for the customized title.
Level: 1

Type: ERROR

Impact: Data

ECSF-10249: cannot validate the customized body

Cause: The customized body expression was not valid.

Action: Use a valid expression for the customized body.
Level: 1

Type: ERROR

Impact: Data

ECSF-10250: cannot validate the customized keywords

Cause: The customized keywords expression was not valid.

Action: Use a valid expression for the customized keywords.
Level: 1

Type: ERROR

Impact: Data

ECSF-10251: cannot validate customized default action title

Cause: The customized default action title expression was not valid.

Action: Use a valid expression for the customized default action title.
Level: 1

Type: ERROR

Impact: Data

ECSF-10252: The engine types cannot be listed.

Cause: An error occurred while executing the SELECT statement against the database.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10253: Engine instances for engine type {0} cannot be listed

Cause: An error occurred while executing the SELECT statement against the database.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10254: The searchable objects cannot be listed.

Cause: An error occurred while executing the SELECT statement against the database.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10255: The searchable objects for schedule {0} cannot be listed.

Cause: An error occurred while executing the SELECT statement against the database.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10256: The search categories for instance {0} cannot be listed.

Cause: An error occurred while executing the SELECT statement against the database.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10257: The external categories for instance {0} cannot be listed.

Cause: An error occurred while executing the SELECT statement against the database.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10258: Index schedules for instance {0} cannot be listed.

Cause: An error occurred while executing the SELECT statement against the database.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10259: Searchable objects for instance {0} cannot be listed.

Cause: An error occurred while executing the SELECT statement against the database.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10260: SQL statement {0} cannot be executed for id {1}

Cause: An error occurred while executing the SELECT statement against the database.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10261: cannot retrieve external search categories

Cause: There was an error retrieving external categories from SES.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10301: cannot convert the given ROWID to String

Cause: An invalid ROWID value was provided.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10302: cannot delete the change log records for range {0} to {1}

Cause: An error occurred while attempting to delete the change log records.

Action: Check the database.
Level: 1

Type: ERROR

Impact: Data

ECSF-10303: cannot close the prepared statement

Cause: An error occurred while attempting to close the prepared statement.

Action: Check the database.
Level: 1

Type: ERROR

Impact: Data

ECSF-10304: cannot construct an attachment

Cause: An error occurred during the construction of the attachment.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10305: cannot link {0} with predicate {1}; error message: {2}

Cause: An error occurred during the crawl for child documents.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10306: cannot create child documents

Cause: An error occurred during the crawl for child documents.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10307: cannot create {0}

Cause: An error occurred during the creation of the crawlable factory.

Action: Check the configuration.
Level: 1

Type: ERROR

Impact: Programmatic

ECSF-10308: cannot handle custom incremental crawl

Cause: An error occurred during the start of an initial or incremental crawl operation.

Action: Check the configuration.
Level: 1

Type: ERROR

Impact: Programmatic

ECSF-10309: No searchable object is specified; cannot start data crawl.

Cause: An attempt was made to start the data crawl when no searchable object was specified.

Action: Check the configuration.
Level: 1

Type: ERROR

Impact: Programmatic

ECSF-10310: cannot set status

Cause: An error occurred at the end of an initial or incremental crawl operation.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10311: cannot execute getAcl(SearchContext, IndexableDocument) {0}

Cause: An error occurred while crawling a secure document.

Action: Check the configuration.
Level: 1

Type: ERROR

Impact: Security

ECSF-10312: cannot split table

Cause: An error occurred while starting the RowIdSplitter operation.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10313: cannot get number of blocks

Cause: An error occurred during the get number of blocks operation.

Action: Check the database.
Level: 1

Type: ERROR

Impact: Data

ECSF-10314: cannot get number of records during EnvInfoProvider initialization

Cause: An error occurred during EnvInfoProvider initialization.

Action: Check the database.
Level: 1

Type: ERROR

Impact: Data

ECSF-10315: cannot load properties from properties file

Cause: An error occurred during EnvInfoProvider initialization.

Action: Check the configuration.
Level: 1

Type: ERROR

Impact: Other

ECSF-10316: cannot set up search context; searchable object is null.

Cause: Searchable object was null.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

ECSF-10317: CreateCrawlable returns null; cannot start crawler

Cause: CreateCrawlable returned null.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10318: cannot start crawler

Cause: An error occurred while attempting to create the control feed.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10319: The crawler is not started.

Cause: An error occurred while attempting to start the crawler.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10320: cannot close indexer

Cause: An error occurred while closing the indexer.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10321: cannot index the documents

Cause: An error occurred while indexing the documents.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10322: cannot start crawler

Cause: An error occurred while starting the crawler.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10323: cannot close resultset to complete the crawl

Cause: An error occurred while attempting to close the resultset.

Action: Check the database.
Level: 1

Type: ERROR

Impact: Data

ECSF-10324: cannot close statement to complete the crawl

Cause: An error occurred while attempting to close the statement.

Action: Check the database.
Level: 1

Type: ERROR

Impact: Data

ECSF-10325: cannot get predicate for workunit

Cause: An error occurred while getting a predicate for the workunit.

Action: Check the configuration.
Level: 1

Type: ERROR

Impact: Data

ECSF-10326: cannot index documents due to indexing error

Cause: An error occurred while indexing the documents.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10327: cannot create indexed document

Cause: An error occurred while attempting to create the indexed document.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10328: cannot evaluate the expression for {0} of {1}

Cause: An error occurred while processing the expression fields.

Action: Check the configuration.
Level: 1

Type: ERROR

Impact: Programmatic

ECSF-10329: cannot start crawler due to failed connection

Cause: A connection was not made.

Action: Check the database.
Level: 1

Type: ERROR

Impact: Data

ECSF-10330: cannot close indexer

Cause: An error occurred while closing the indexer.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10331: cannot split ECSF change log table

Cause: An error occurred during the CREATE CHANGE LOG WORK UNITS operation.

Action: Check the database.
Level: 1

Type: ERROR

Impact: Data

ECSF-10332: cannot process date range

Cause: An error occurred during the incremental crawl operation.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10333: Last crawl time of {0} is null.

Cause: An error occurred during the incremental crawl operation.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10334: cannot create child documents

Cause: An error occurred during the extract operation.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10335: cannot release the connection

Cause: An error occurred during the release of the connection.

Action: Check the database.
Level: 1

Type: ERROR

Impact: Data

ECSF-10336: cannot load the display name for the search category

Cause: An error occurred during the get display name operation.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

ECSF-10337: cannot load the display name for the searchable object

Cause: An error occurred during the get display name operation.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

ECSF-10338: cannot read searchable object

Cause: An error occurred while the searchable object was loading.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

ECSF-10339: cannot create facet entries for {0} on {1}

Cause: An error occurred while creating the FacetDef object.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

ECSF-10340: cannot load engine parameters

Cause: An error occurred during engine instance loading.

Action: Check the configuration.
Level: 1

Type: ERROR

Impact: Other

ECSF-10341: Facets are not supported for this searchable object.

Cause: An attempt was made to load facets for this searchable object that does not support facets.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

ECSF-10342: cannot get search engine

Cause: An error occurred while attempting to get the search engine.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

ECSF-10343: cannot create configuration file {0}

Cause: An error occurred during the get configuration file operation.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

ECSF-10344: The SES_QUERY_SERVICE parameter is missing for the engine instance; cannot get search categories from SES.

Cause: The SES_QUERY_SERVICE parameter value for this engine instance was missing from the ECSF_PARAMETER table in the database.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10345: cannot get search categories from SES

Cause: Search categories could not be obtained from SES.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10346: cannot load searchable object {0} for category {1} in engine instance {2}

Cause: The searchable object defined in the database was not properly configured.

Action: Ensure that the searchable object defined in the database is properly configured.
Level: 1

Type: ERROR

Impact: Process

ECSF-10347: failed DBMS_PARALLEL_EXECUTE_EXTENTS view check

Cause: An error occurred while attempting to find a view.

Action: Check the database.
Level: 1

Type: ERROR

Impact: Data

ECSF-10348: cannot find the DBMS_PARALLEL_EXECUTE_EXTENTS view; will use ECSF_AD_EXTENTS view instead

Cause: The specified database version was incorrect.

Action: Check the database.
Level: 1

Type: ERROR

Impact: Data

ECSF-10365: cannot index documents due to security error

Cause: A security error occurred during indexing.

Action: Check the configuration.
Level: 1

Type: ERROR

Impact: Security

ECSF-10366: cannot create NUM type workunit because VO contains no key fields

Cause: An error occurred while attempting to create the NUM workunit.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10367: cannot create NUM type workunit because VO contains more than one key field

Cause: An error occurred while attempting to create the NUM workunit.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10368: cannot use NUM Splitter because VO contains no key fields

Cause: An error occurred while attempting to use the NUM Splitter.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10369: cannot use NUM Splitter because VO contains more than one key field

Cause: An error occurred while attempting to use the NUM Splitter.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10370: data type {1} of field {2} is not supported for NUM Splitter

Cause: An error occurred while attempting to use the NUM Splitter.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10401: cannot get GUID for user {0}

Cause: An error occurred during the get user GUID operation.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Security

ECSF-10402: The specified permission is denied for user {0}.

Cause: The user was not granted with the specified permission for the current security context.

Action: Check the security configuration to make sure that the user is provisioned with the proper security permissions.
Level: 1

Type: ERROR

Impact: Security

ECSF-10403: cannot assert user {0}

Cause: An error occurred during the user assertion operation.

Action: Check the user.
Level: 1

Type: ERROR

Impact: Security

ECSF-10404: cannot encode URL in UTF-8

Cause: An error occurred during URL encoding.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10405: cannot decode URL in UTF-8

Cause: An error occurred during URL decoding.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

ECSF-10406: cannot provision engine instances

Cause: An error occurred during the provisioning of engine instances.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

ECSF-10407: cannot create security service

Cause: An error occurred during security service creation.

Action: Check the configuration.
Level: 1

Type: ERROR

Impact: Programmatic

ECSF-10408: cannot retrieve application ID from topology

Cause: An error occurred during Application ID retrieval from Topology.

Action: Check the configuration.
Level: 1

Type: ERROR

Impact: Other

ECSF-10409: cannot retrieve application ID from EJB properties

Cause: An error occurred during Application ID retrieval from EJB properties.

Action: Check the configuration.
Level: 1

Type: ERROR

Impact: Other

ECSF-10410: cannot read attachment for attached document

Cause: An error occurred while attempting to read the attachment.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10411: cannot retrieve business event connection factory to raise event using Fabric

Cause: An attempt was made to raise an event when BusinessEventConnectionFactory was not configured properly.

Action: Ensure that the Business Events are configured properly.
Level: 1

Type: ERROR

Impact: Process

ECSF-10412: cannot create business event connection to raise event using Fabric

Cause: Raise event using Fabric failed because BusinessEventConnection could not be created.

Action: Ensure that the Business Events are configured properly.
Level: 1

Type: ERROR

Impact: Process

ECSF-10413: cannot raise event using SQL

Cause: An attempt was made to raise events using SQL when the event could not be written to the ECSF_SEARCHABLE_CHANGE_LOG table in the database.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10414: invalid business event connection

Cause: An attempt was made to raise an event while BusinessEventConnectionFactory was invalid.

Action: Ensure that the Business Events are configured properly.
Level: 1

Type: ERROR

Impact: Other

ECSF-10415: invalid SearchContext; user not bound to it

Cause: A user was not bound to SearchContext.

Action: Bind a user to the SearchContext before performing any search related actions.
Level: 1

Type: ERROR

Impact: Process

ECSF-10416: password not available in credential store; cannot get password for user {0}

Cause: Password was not available in the credential store.

Action: Update passwords in credential store using ECSF Admin Utility.
Level: 1

Type: ERROR

Impact: Security

ECSF-10417: cannot retrieve Application IDs for the ECSF component

Cause: Topology and ECSF Application Id override returned no Application Ids.

Action: Check Topology and/or ECSF Application Id override configuration.
Level: 1

Type: WARNING

Impact: Other

ECSF-10418: invalid Plugin ID in properties file; the ID must be a number.

Cause: An invalid Plugin ID specified in the Properties file.

Action: Check the properties file.
Level: 1

Type: ERROR

Impact: Other

ECSF-10419: cannot provision ID Plugin

Cause: An error occurred while provisioning the ID plugin.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

ECSF-10420: cannot check permission for user {0}

Cause: An error occured while checking permission.

Action: Check the configuration.
Level: 1

Type: ERROR

Impact: Security

ECSF-10451: cannot set encoding format on HTTP request

Cause: An unexpected error occurred.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

ECSF-10452: invalid request parameters

Cause: An error occurred during the doPost operation.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

ECSF-10453: cannot authenticate user

Cause: An error occurred during the doPost operation.

Action: Check the user.
Level: 1

Type: ERROR

Impact: Data

ECSF-10454: cannot construct error response

Cause: An error occurred during the doPost operation.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Security

ECSF-10456: Forcing feedType = Error. Cannot parse ErrorFeed content for {0}

Cause: An unexpected error occurred.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

ECSF-10457: Error status received for {0} ControlFeed; lastCrawlDate is not updated in database.

Cause: An unexpected error occurred.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

ECSF-10458: Error status received for {0} DataFeed; calling cf.reset().

Cause: An unexpected error occurred.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

ECSF-10459: Error status received for {0} DataFeed; cannot call cf.reset().

Cause: An unexpected error occurred.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

ECSF-10460: cannot invoke search servlet {0} because: {1}. See log for more details.

Cause: An unexpected error occurred.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

ECSF-10461: password for the user {0} cannot be null

Cause: An error occurred during the doPost operation.

Action: Check the user
Level: 1

Type: ERROR

Impact: Data

ECSF-10464: attachment stream for attachment with ATTACHED_DOCUMENT_ID={0} is null

Cause: An error occurred during the FusionAttachmentImpl.read operation.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10501: cannot authenticate user {0}

Cause: An error occurred while authenticating the user.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10502: the searchContext is null.

Cause: The search context was null.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Security

ECSF-10503: Username is null or empty.

Cause: There was no username.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Security

ECSF-10504: cannot authenticate user {0}

Cause: An error occurred while authenticating the user.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Security

ECSF-10505: Identity Storage Service is not configured: {0}

Cause: A JPS Security configuration error occurred.

Action: Configure an Identity Store Service in the application security configuration.
Level: 1

Type: ERROR

Impact: Security

ECSF-10506: cannot validate user {0}

Cause: An error occurred while validating the user.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Security

ECSF-10507: cannot find searchable object {0}

Cause: The searchable object was not found.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10508: Searchable object {0} is not active.

Cause: The searchable object was not active.

Action: Activate the searchable object.
Level: 1

Type: ERROR

Impact: Security

ECSF-10509: {0} is not an instance of Securable.

Cause: A search plug-in not of type Securable was specified for the searchable object.

Action: Use a search plug-in that is of type Securable.
Level: 1

Type: ERROR

Impact: Security

ECSF-10510: cannot get security keys for {0} on {1}

Cause: A JPS error occurred.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Security

ECSF-10511: User {0} is invalid.

Cause: An invalid user was specified.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Security

ECSF-10512: The number of keys {0} exceeds 200.

Cause: The number of security keys specified exceeded the maximum limit of 200.

Action: Specify 200 or fewer keys for the search plug-in.
Level: 1

Type: ERROR

Impact: Security

ECSF-10513: invalid security request

Cause: The security request was null.

Action: Pass in a valid security request.
Level: 1

Type: ERROR

Impact: Security

ECSF-10514: security service error: {0}

Cause: A security service error occurred.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Security

ECSF-10515: unsupported SecurityService request

Cause: The security request entered was invalid.

Action: Enter a valid security request.
Level: 1

Type: ERROR

Impact: Security

ECSF-10517: cannot authorize user {0}

Cause: There was an error authorizing the user.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10518: cannot get login context

Cause: There was an error getting the login context.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10519: UserId format {0} is not supported.

Cause: The UserId format specified was not supported by the search plug-in.

Action: Specify a supported UserId format for the search plug-in.
Level: 1

Type: ERROR

Impact: Security

ECSF-10520: UserId format is not specified in the security request. Defaulting to FND format.

Cause: No UserId format was specified.

Action: Specify a valid UserId format.
Level: 1

Type: ERROR

Impact: Security

ECSF-10521: {0} keys found for {1} on {2} {3} - plugin name {4}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Security

ECSF-10522: cannot convert username for {0} of format {1}

Cause: Invalid id format

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Security

ECSF-10530: Saved Search Details creation failed

Cause: An error occurred while creating the search details record.

Action: Contact the System Administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10531: Failed to retrieve searches for user {0} and context {1}

Cause: An error occurred while getting the search records

Action: Contact the System Administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10532: Failed to retrieve saved search with name {0} + for user {1}

Cause: An error occurred while getting the search record

Action: Contact the System Administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10533: Failed to create {0} search in the database

Cause: An error occurred while creating the search record

Action: Contact the System Administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10534: {0} Search with name {1} already exists in the database

Cause: An error occurred while creating the search record

Action: Contact the System Administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10535: Saved Search with name {0} does not contain a valid query string.

Cause: Saved Search does not contain a valid query string

Action: Contact the System Administrator.
Level: 1

Type: WARNING

Impact: Process

ECSF-10536: Creation of {0} search did not result in a row being inserted into the database.

Cause: Search record creation failed.

Action: Contact the System Administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10537: Error in saved search queryMetaData.

Cause: Error in saved search queryMetaData.

Action: Contact the System Administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10538: Saved Search Details updated failed for {0} search with name {1}

Cause: Saved Search Details record updated failed.

Action: Contact the System Administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10539: Update of {0} search did not result in a row being updated in the database.

Cause: Update of search failed.

Action: Contact the System Administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10540: Error while deleting {0} search records in database.

Cause: Delete of search record failed.

Action: Contact the System Administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10541: Creation of saved search details did not result in a row being inserted into the database.

Cause: Search details record creation failed.

Action: Contact the System Administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10542: Failed to get database connection.

Cause: Failed to get database connection.

Action: Contact the System Administrator.
Level: 1

Type: WARNING

Impact: Process

ECSF-10543: Failed to roll back data in database connection.

Cause: Failed to roll back data in database connection.

Action: Contact the System Administrator.
Level: 1

Type: WARNING

Impact: Process

ECSF-10544: Failed to retrieve saved search details

Cause: An error occurred while getting the search details record

Action: Contact the System Administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10545: Saved Search with name {1} already exists in one of the pillars.

Cause: Saved Search with name already exists in one of the pillars

Action: Contact the System Administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10546: Saved Search with name {1} was not found in any of the pillars.

Cause: Saved Search was not found in one of the pillars

Action: Contact the System Administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10601: cannot run query for search category {0}

Cause: An attempt was made to run the query on an invalid search category.

Action: Ensure that the search category/categories used in this query is valid.
Level: 1

Type: ERROR

Impact: Data

ECSF-10602: cannot run query without a query string

Cause: The QueryMetaData object used in this query did not contain a search string.

Action: Ensure that the search string is bound to the QueryMetaData before executing the query.
Level: 1

Type: ERROR

Impact: Process

ECSF-10603: cannot run query without search categories

Cause: The QueryMetaData object used in this query did not contain a search category.

Action: Ensure that the search category is bound to the QueryMetaData before executing the query.
Level: 1

Type: ERROR

Impact: Process

ECSF-10604: cannot delete saved search {0}

Cause: The saved search could not be deleted from the ECSF_SVSEARCH and ECSF_SVSEARCH_DETAILS tables in the database.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10605: cannot save search {0}

Cause: The saved search could not be saved to the ECSF_SVSEARCH and ECSF_SVSEARCH_DETAILS tables in the database.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Data

ECSF-10606: cannot get DisplayName for runtime object {0}

Cause: The get display name operation failed for this runtime object.

Action: Check ECSF component server logs for details.
Level: 1

Type: ERROR

Impact: Data

ECSF-10607: cannot find ECSF_QUERY_SERVICE_REF_NAME parameter for this ECSF component

Cause: The ECSF_QUERY_SERVICE_REF_NAME parameter was not set correctly.

Action: Contact the database administrator to check that the ECSF_QUERY_SERVICE_REF_NAME parameter is set correctly for this ECSF component in the ECSF_PARAMETER table.
Level: 1

Type: ERROR

Impact: Process

ECSF-10608: cannot execute federation query for {0}

Cause: The query execution failed.

Action: For global context, check ECSF component server logs for details. For local context, check the exception message.
Level: 1

Type: ERROR

Impact: Process

ECSF-10609: cannot get engine instances from the ECSF components

Cause: An error occurred while getting the engine instances from the ECSF components.

Action: Check the ECSF component server logs for details.
Level: 1

Type: ERROR

Impact: Data

ECSF-10610: cannot get global saved searches from the ECSF components

Cause: Could not get saved searches from the ECSF components.

Action: Check the ECSF component server logs for details.
Level: 1

Type: ERROR

Impact: Data

ECSF-10611: thread error while calling ECSF component

Cause: An exception occurred with one of the threads while calling the ECSF components.

Action: Check the ECSF component server logs for details.
Level: 1

Type: ERROR

Impact: Threads

ECSF-10612: cannot serialize QueryMetaData to ByteArrayOutputStream

Cause: An I/O error occurred while reading the input stream.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10613: cannot deserialize QueryMetaData

Cause: An I/O error occurred while reading the input stream.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Process

ECSF-10614: cannot deserialize QueryMetaData

Cause: The class of a serialized object could not be found.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

ECSF-10615: cannot get SavedSearch details

Cause: Could not get SavedSearch details.

Action: For global context, check the ECSF component server logs. For local context, check the exception message.
Level: 1

Type: ERROR

Impact: Data

ECSF-10616: cannot serialize the SearchException stacktrace.

Cause: The exception stacktrace on this ECSF component could not be written to XML.

Action: Contact the system administrator.
Level: 1

Type: WARNING

Impact: Process

ECSF-10617: The application ID for global Search Group {0} is not set in the database.

Cause: The Search Group was missing the application ID.

Action: Contact the database administrator.
Level: 1

Type: WARNING

Impact: Process

ECSF-10618: Action {0} cannot be evaluated for searchable object {1}.

Cause: An exception occurred while evaluating actions for this searchable object.

Action: Check the ECSF component server logs for details.
Level: 1

Type: ERROR

Impact: Process

ECSF-11001: Warning: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

ECSF-11301: cannot reset workunit with eventId

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ECSF-11302: unknown attachment data type {0} default to text/plain

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ECSF-11303: exception in finish(SearchContext ctx)

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ECSF-11304: exception in reset(SearchContext ctx)

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ECSF-11306: unknown change type {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ECSF-11307: error with file

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ECSF-11308: Invalid document language code {0} received. Defaulting to {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ECSF-11309: exception in processDeletedRecords(SearchContext)

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ECSF-11311: cannot encode primarykey

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ECSF-11312: cannot load searchable object itself {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ECSF-11313: Searchable object must have a default constructor -

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

ECSF-11314: cannot create instance of

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

ECSF-11315: Class must extend oracle.ecsf.meta.SearchableObject {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

ECSF-11316: There is no view object or class defined with name {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

ECSF-11317: cannot load category with name {0} in engine instance ID {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ECSF-11318: cannot find object {0} in engine instance with ID {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ECSF-11319: Loading searchable object {0} as java class

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ECSF-11320: cannot find the Java class for

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

ECSF-11321: Deep-level VOs not supported. VO is: {0} Level: {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ECSF-11322: cannot release session for {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ECSF-11323: cannot close connection for applsession

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ECSF-11324: cannot format a date with format {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Data

ECSF-11325: cannot initialize session with null or empty username

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ECSF-11326: cannot initialize application session for {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ECSF-11327: FusionAppExtension: Terminating user session {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ECSF-11401: ConfigFeed: Received forceInitialCrawl parameter for {0}. Resetting lastCrawlDate to null, and removing crawlState.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ECSF-11402: ControlFeed: Unknown status {0} received for {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ECSF-11403: DataFeed: Unknown status {0} received for {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ECSF-11404: cannot retrieve the attributes of the searchable object

Cause: The searchable object could not be found or was invalid.

Action: Ensure a valid searchable object is deployed to the ECSF server.
Level: 1

Type: ERROR

Impact: Data

ECSF-11405: cannot retrieve the customized fields of the searchable object

Cause: The searchable object could not be found or was invalid.

Action: Ensure that a valid searchable object is deployed to the ECSF server.
Level: 1

Type: ERROR

Impact: Data

ECSF-11601: Cannot perform federation, active ECSF components were not found.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

ECSF-13310: cannot evaluate expression

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

33 EM-00251 to EM-02804

EM-00251: No connection to the WebLogic managed server {0}.

Cause: The WebLogic managed server was down.

Action: Verify that the managed server is up and running.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00252: Error in accessing proxy MBean for this system component in WebLogic managed server {0}

Cause: Component was down

Action: Start the component, or verify that the component has been deployed on the managed server.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00268: Error in querying ports configuration for system component {0}

Cause: Component was down

Action: Start the component.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00301: Error in fetching data from target application.

Cause: Target application is down.

Action: Ensure target application is running.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00302: Error fetching data from target server in the Oracle WebLogic Server domain.

Cause: The target WebLogic server is down.

Action: Make sure the target server is up and running.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00303: Error in discovering web service endpoints for target application.

Cause: Target application is down.

Action: Ensure target application is running.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00351: Unable to connect to Oracle WSM Policy Manager.

Cause: The Oracle WSM Policy Manager was down or not accessible.

Action: Make sure Oracle WSM Policy Manager (wsm-pm application) is up and accessible. Also, ensure you have right roles to access the Service.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00360: Unable to parse WSDL from {0}

Cause: Either the URL did not refer to a valid address, or the WSDL document did not contain valid Web services definition.

Action: Make sure that the given WSDL URL is accessible and ensure the WSDL contains valid WS definition.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00426: Unable to save changes to registered service

Cause: The service repository is unavailable.

Action: Ensure that the service repository is up and running.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00428: Unable to delete registered service

Cause: The service is no longer valid.

Action: Ensure that the service is valid and is registered. Make sure the endpoint and WSDL for the service are accessible.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00430: Unable to register service due to duplicate service name

Cause: The service name is already registered.

Action: Ensure that the service name is unique.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00432: Invalid WSIL URL

Cause: The WSIL URL is invalid. The URL is unreachable or doesn't contain a valid WSIL.

Action: Ensure that the WSIL URL is valid and available.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00434: Invalid WSIL File

Cause: The WSIL file is invalid. The file is not a valid WSIL document.

Action: Ensure that the uploaded file is a valid WSIL document.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00440: Service repository operation failed

Cause: Service repository is unavailable.

Action: Ensure that the service repository is up and running.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00449: Unexpected error occurred

Cause: Unkown

Action: Unknown. Please contact Oracle Support for further guidance.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00451: Failed to access WSDL

Cause: Invalid WSDL location or WSDL is not accessible

Action: Make sure you provide a valid WSDL location. If the location is valid, make sure it is accessible. Also, make sure you have proper privileges to access the WSDL with username and password.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00452: Failed to parse WSDL file

Cause: Invalid WSDL content

Action: Ensure that the WSDL is syntactically and semantically correct.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00453: Failed to invoke operation

Cause: Invalid input arguments

Action: Make sure you provide the required input argument values, and that the values are the proper type (for example, integer, string, and so on).
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00454: Failed to invoke operation

Cause: Unable to read SOAP action for selected operation

Action: Make sure right SOAP Action value is set.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00455: Failed to change view from 'XML View' to 'Tree View'

Cause: Invalid payload contents in XML format

Action: Make sure you provide a valid payload to parse and check if any required tag is missing or broken.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00456: Failed to change view from 'XML View' to 'Tree View'

Cause: Invalid input argument

Action: Make sure you provide the required input argument values, and that the values are the proper type (for example, integer, string, and so on).
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00457: Failed to load key aliases from the keystore

Cause: Invalid keystore information

Action: Make sure you provide a valid keystore location and password.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00458: Failed to get compatible client policies from the WSDL

Cause: The WSDL is not accessible or you do not have the privilege to get policies.

Action: Make sure you have the privilege to get the client policies.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00501: TopLink Sessions were not found

Cause: TopLink MBeans were not found

Action: Ensure that the application has been accessed to register the MBeans. Make sure that "-Declipselink.register.dev.mbean=true" and "-Declipselink.register.run.mbean=true" are part of $JAVA_OPTIONS
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00601: Error in getting WSDL for Web service client.

Cause: Target web service application is down.

Action: Ensure target web service application is running.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00602: Error in attaching/detaching policies.

Cause: Target application or Oracle WSM Policy Manager is down.

Action: Ensure target application and Oracle WSM Policy Manager is running.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00603: Error in getting policy subject from target application.

Cause: Target web service application is down.

Action: Ensure target Web service application is running.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-01052: Error in querying OPSS application policy MBean object name.

Cause: The WebLogic managed server was down.

Action: Verify that the managed server is up and running.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-01053: Application stripe entry {0} does not exist in policy store.

Cause: Application stripe ID used to access policies from policy store did not have any data.

Action: Check the application stripe ID data provided in configuring Fusion MiddleWare control application deployment wizard security task.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-01055: Error in querying OPSS system policy MBean object name.

Cause: The WebLogic managed server was down.

Action: Verify that the managed server is up and running.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-01061: Error in querying OPSS credential store MBean object name.

Cause: The WebLogic managed server was down.

Action: Verify that the managed server is up and running.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-01321: Cannot obtain application information

Cause: The application is not active

Action: Make sure that the application is active or running
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-01322: Cannot obtain MDS information for selected application

Cause: MDS is not properly configured for the application

Action: Make sure that MDS config mbean is accessible on the mbean server. If it is not, verify that appropriate MDS configuration file (web.xml) contains ADFConfigRuntimeLifeCycleCallBack listener to register MDS config mbean and MDS is configured properly in adf-config.xml.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-01323: Error while performing MDS runtime (import, export or purge) operation

Cause: MDS runtime mbean is not found on runtime mbean server

Action: Make sure that the MDS runtime mbean is accessible on runtime mbean server. If it is not, verify that appropriate MDS configuration file (weblogic-application.xml) contains WLLifecycleListener listener to register MDS runtime mbean.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-01324: Error while retrieving data from page cache

Cause: JavaBean stored in the session has expired or was destroyed

Action: Start a fresh session by logging into EM again.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-01325: Cannot obtain MDS target repository information

Cause: MDS target repository is not configured

Action: Verify the MDS configuration by checking the contents of the configuration files (for example, adf-config.xml and mds-config.xml).
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-01951: Error connecting to soa-infra runtime.

Cause: The soa-infra application is down or not started completely.

Action: Verify that the soa-infra application is up and running, and verify that the database where the SOA schemas are installed is up and running.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-01952: Error getting composite details.

Cause: The SOA composite application was undeployed or not discovered by Enterprise Manager.

Action: Select Refresh Farm from the Farm menu.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-01953: Error getting composite runtime details.

Cause: The SOA composite application was not loaded.

Action: View the log files and review any errors reported by the soa-infra application.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02006: Error retrieving Configuration MBeans for ADFConnectionMBeans {0}.

Cause: The ADF Connection and Configuration MBean is not available or accessible.

Action: Configuration options currently unavailable. The application might be down, did not start properly, or is incorrectly packaged. Check the log files for further details.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02056: Error getting DAD MBean.

Cause: The DAD MBean is not available or accessible.

Action: Configuration options currently unavailable. The application might be down, did not start-up properly, or is incorrectly packaged. Check the log files for further detail.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02057: Error getting Cache MBean Object Name.

Cause: The Cache MBean is not available or accessible.

Action: Configuration options currently unavailable. The application might be down, did not start-up properly, or is incorrectly packaged. Check the log files for further detail.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02058: Error getting Middle Tier MBean Object Name.

Cause: The Middle Tier MBean is not available or accessible.

Action: Configuration options currently unavailable. The application might be down, did not start-up properly, or is incorrectly packaged. Check the log files for further detail.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02063: Error getting Portal site URL.

Cause: Wiring MBean Could not connect to the Portal repository.

Action: The Portal Database maybe down or the Portal DAD has incorrect username, password or connect string information. Check the log files for further detail.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02201: Error connecting to the admin server.

Cause: The admin server was down.

Action: Ensure the target admin server is running.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02202: Error getting the list of folders from the credential store

Cause: There were issues with the JPS credential store MBean.

Action: Ensure the JPS credential store MBean is registered and working properly through the System MBean Browser.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02251: Error connecting to Forms Config MBeans

Cause: The managed server that hosts the Forms application was down, or the Forms application was down or not deployed on this server.

Action: Depending on the specific cause, start the managed server if it is down, start the Forms application if it is down, or deploy the Forms application on this domain if haven't been deployed already.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02451: cannot initialize the home page

Cause: The Homepage PageModel bean was not instantiated.

Action: [1.] Check the .jspx code for correct reference usage. [2.] Check if the Homepage Page Model bean class is in the emai_ecsf.jar file. [3.] Check the ADFc configuration file emai-ecsf.xml for correct class association.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02452: cannot initialize the home page

Cause: The Homepage Model bean was not instantiated.

Action: [1.] Check if the Homepage Model bean class is in the emai_ecsf.jar file. [2.] Check the ADFc configuration file emai-ecsf.xml for correct class association. [3.] Contact your Administrator to see if you have the correct admin or operator privileges to view this page
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02453: cannot initialize the admin page

Cause: The Admin PageModel bean was not instantiated.

Action: [1.] Check the .jspx code for correct reference usage. [2.] Check if the Admin Page Model bean class is in the emai_ecsf.jar file. [3.] Check the emai-ecsf.xml configuration file for correct class association.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02454: cannot initialize the admin page

Cause: The Admin Model bean was not instantiated.

Action: [1.] Check if the Admin Model bean class is in the emai_ecsf.jar file. [2.] Check the emai-ecsf.xml configuration file for correct class association.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02455: cannot create the new engine instance

Cause: The ECSF mbean was not found, the name specified for the search engine instance was not unique, a duplicate record was created, a search engine with the default name already existed, or no search engine instance was selected.

Action: Check the logging messages on the ECSF runtime server, and make the necessary corrections.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02456: cannot create the new search category

Cause: The ECSF mbean was not found, the name specified for the search category was not unique, a duplicate record was created, a search category with the default name already existed, or no search engine instance was selected.

Action: Check the logging messages on the ECSF runtime server, and make the necessary corrections.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02457: cannot create the new index schedule

Cause: The ECSF mbean was not found, the name specified for the index schedule was not unique, a duplicate record was created, an index schedule with the default name already existed, or no search engine instance was selected.

Action: Check the logging messages on the ECSF runtime server, and make the necessary corrections.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02458: cannot update the record

Cause: The ECSF mbean was not found, the name for the record was not unique, a duplicate record was created, a search engine instance parameter with the same name already existed, or no search engine instance was selected.

Action: Check the logging messages on the ECSF runtime server, and make the necessary corrections.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02459: cannot delete the search engine instance

Cause: The ECSF mbean was not found, or the search engine instance was not deleted in the database.

Action: Check the logging messages on the ECSF runtime server, and make the necessary corrections.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02460: cannot deploy the selected artifact

Cause: The ECSF mbean was not found, the artifact was not available on the ECSF runtime server, or the search engine failed to deploy the artifact.

Action: Check the logging messages on the ECSF runtime server, and make the necessary corrections.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02461: cannot undeploy the selected artifact

Cause: The ECSF mbean was not found, the artifact was not available on the ECSF runtime server, or the search engine failed to undeploy the artifact.

Action: Check the logging messages on the ECSF runtime server, and make the necessary corrections.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02462: cannot activate the searchable object

Cause: The ECSF mbean was not found, or the searchable object was not updated in the database.

Action: Check the logging messages on the ECSF runtime server, and make the necessary corrections.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02463: cannot deactivate the searchable object

Cause: The ECSF mbean was not found, or the searchable object was not updated in the database.

Action: Check the logging messages on the ECSF runtime server, and make the necessary corrections.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02464: cannot start the index operation

Cause: The ECSF mbean was not found, or the search engine failed to crawl the data incrementally.

Action: Check the logging messages on the ECSF runtime server, and make the necessary corrections.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02465: cannot stop the index operation

Cause: The ECSF mbean was not found, or the search engine failed to stop the crawling.

Action: Check the logging messages on the ECSF runtime server, and make necessary corrections.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02466: cannot start the full index operation

Cause: The ECSF mbean was not found, or the search engine failed to fully crawl the data.

Action: Check the logging messages on the ECSF runtime server, and make the necessary corrections.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02467: cannot deploy the searchable object

Cause: No search engine instance was selected.

Action: Select a search engine instance before you click the deploy button.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02468: cannot deploy the searchable object

Cause: No searchable object was selected.

Action: Select a searchable object before you click the deploy button.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02469: cannot deploy the searchable object

Cause: No parameters were defined, or parameters were defined incorrectly for the selected search engine instance.

Action: Add parameters to the selected search engine instance before you deploy the searchable object.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02470: cannot register the search engine instance

Cause: No parameters were defined, or parameters were defined incorrectly for the selected search engine instance.

Action: Add parameters to the selected search engine instance before you register it.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02471: cannot import the external search groups

Cause: The ECSF mbean was not found, or the search engine failed to import the external search categories.

Action: Check the logging messages on the ECSF runtime server, and make the necessary corrections.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02472: cannot proceed with the operation

Cause: No record was selected.

Action: Select a record.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02473: cannot proceed with the operation

Cause: A value for the Name field of the selected record was not specified.

Action: Specify a value for the Name field of the selected record.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02474: cannot register the searchable object

Cause: The ECSF mbean was not found, the name for the record was not unique, or the searchable object was invalid.

Action: Check the logging messages on the ECSF runtime server, and make the necessary corrections.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02475: cannot initialize unregister searchable object page

Cause: The unregister searchable object bean was not instantiated.

Action: [1.] Check the .jspx code for correct reference usage. [2.] Check if the Page Model bean class is in the emai_ecsf.jar file. [3.] Check emai-ecsf.xml configuration file for correct class association.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02476: cannot unregister the searchable object

Cause: The ECSF mbean was not found, the name for the record was not unique, or the searchable object is invalid.

Action: Check the logging messages on the ECSF runtime server and make the necessary corrections.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02477: Deployment of instance parameters failed

Cause: The ECSF mbean server was not found, or the index schedule corresponding to this object is running, or the searchable object is invalid.

Action: Check the logging messages on the ECSF runtime server and make the necessary corrections.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02478: Deployment of instance parameters for certain objects failed.

Cause: The ECSF mbean server was not found, or the index schedule corresponding to a deployed searchable object is running

Action: Check the searchable object tab and redeploy the updates for the failed objects individually.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02479: cannot validate the input string

Cause: The ECSF mbean server was not found, or the input string is invalid.

Action: Check the error log and modify the input string accordingly.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02480: cannot retrieve the search attributes of the selected searchable object

Cause: The ECSF mbean server was not found, or the ECSF runtime server failed to retrieve the attributes.

Action: Check the logging messages on the ECSF runtime server and make the necessary corrections.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02481: cannot retrieve the available external search groups

Cause: The ECSF mbean was not found, or the search server failed to return the external search categories.

Action: Check the logging messages on the ECSF runtime server, and make the necessary corrections.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02652: error while initializing data for the BI Instance {0}

Cause: The server for Fusion Middleware Control failed to correctly communicate with the server for the BI Instance.

Action: Ensure that the server for the BI Instance is running.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02653: error while initializing data for the BI Instance {0}

Cause: The server for Fusion Middleware Control failed to correctly communicate with the server for the BI Instance.

Action: Ensure that the server for the BI Instance is running.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02658: The {1} operation can not be performed on the {0} component.

Cause: The specified Oracle Business Intelligence component failed to respond to the operation.

Action: See the log files for the Oracle Business Intelligence component to determine the cause of the error.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02668: The configuration for BI Instance can not be locked.

Cause: The BI Instance was already locked by another user.

Action: Determine which user has locked the BI Instance and request that it be released.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02669: The changes to the BI Instance can not be committed.

Cause: The BI Instance failed to commit all recent changes.

Action: See the log files for the BI Instance to determine the cause of the error.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02670: The changes to the BI Instance can not be reverted.

Cause: The BI Instance failed to revert all recent changes.

Action: See the log files for the BI Instance to determine the cause of the error.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02672: The BI Instance can not be started.

Cause: The BI Instance could not respond correctly to the start command.

Action: See the log files for the BI Instance to determine the cause of the error.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02673: The BI Instance can not be stopped.

Cause: The BI Instance could not respond correctly to the stop command.

Action: See the log files for the BI Instance to determine the cause of the error.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02674: The BI Instance can not be restarted.

Cause: The BI Instance could not respond correctly to the restart command.

Action: See the log files for the BI Instance to determine the cause of the error.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02701: Error occurred while initializing the Essbase Server component.

Cause: The Essbase Server MBean was not found or there was an error in the object name specified for the Essbase Server MBean.

Action: [1.] Check the home model code for correct object name of the Essbase Server MBean. [2.] Check if Essbase Server MBean is registered properly in the MBean Server.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02702: Error occurred while fetching applications from Essbase Server.

Cause: Could not connect to Essbase Server or there was an error fetching information from Essbase Server.

Action: [1.] Check the connectivity with Essbase Server. [2.] Check if the Essbase credentials provided are correct.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02703: Error occurred while fetching credentials from Essbase Server.

Cause: Could not read/write credentials from the Credential Store.

Action: [1.] Check access privileges for the Essbase component. [2.] Check the Access Control Settings.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02704: Error occurred while resetting credentials in Essbase Server.

Cause: Could not read/write credentials from the Credential Store.

Action: [1.] Check access privileges for the Essbase component. [2.] Check the Access Control Settings if it provides read/write access to Essbase component.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02705: Error occurred while initializing the Essbase Application Component.

Cause: The Essbase Application MBean was not found or there was an error in the object name specified for the Essbase Application MBean.

Action: [1.] Check the home model code for correct object name of the Essbase Application MBean. [2.] Check if Essbase Application MBean is registered properly in the MBean Server.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02706: Error occurred while fetching cubes from Essbase Application.

Cause: Could not connect to Essbase Server or there was an error fetching information from Essbase Server.

Action: [1.] Check the connectivity with Essbase Server. [2.] Check if the Essbase credentials provided are correct.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02707: Error occurred while initializing the Essbase Application Metric Component.

Cause: The Essbase Application Metric MBean was not found or there was an error in the object name specified for the Essbase Application Metric MBean.

Action: [1.] Check the home model code for correct object Name of the Essbase Application Metric MBean. [2.] Check if Essbase Application Metric MBean is registered properly in the MBean Server.
Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02801: Problem getting general metric information while rendering home page for target {0}.

Cause: Admin server down, unreachable, or credential problems.

Action: Ensure the admin server is up, reachable, and that the login credentials are correct.
Level: 1

Type: WARNING

Impact: Requests/Responses

EM-02802: Problem getting graph metric information while rendering home page for target {0}.

Cause: Admin server down, unreachable, or credential problems.

Action: Ensure the admin server is up, reachable, and that the login credentials are correct.
Level: 1

Type: WARNING

Impact: Requests/Responses

EM-02803: Problem getting metric information while rendering configure page for target {0}.

Cause: Admin server down, unreachable, or credential problems.

Action: Ensure the admin server is up, reachable, and that the login credentials are correct.
Level: 1

Type: WARNING

Impact: Requests/Responses

EM-02804: Problem accessing mbean attributes while rendering configure page for target {0}.

Cause: Admin server down, unreachable, or credential problems.

Action: Ensure the admin server is up, reachable, and that the login credentials are correct.
Level: 1

Type: WARNING

Impact: Requests/Responses

34 ENS-00000 to ENS-00213

ENS-00000: listener thread create (%s)

Cause: An error occured while creating the listener thread.

Action: *Define: ONS_LISTENER_THREAD_CREATE_ERROR
Level:

Type:

Impact: Other

ENS-00001: Connection %s unknown message type: %s

Cause: The connection message type is unknown. This may be a malicious attack on the specified ONS port.

Action: *Define: ONS_HTTP_UNKNOWN_MSGTYPE
Level:

Type:

Impact: Other

ENS-00002: Connection %s '%s' not found in message%s

Cause: The message does not contain the notification type.

Action: *Define: ONS_INTERNAL_EVENTTYPE_NOTFOUND
Level:

Type:

Impact: Other

ENS-00003: Connection %s register is missing %s

Cause: The register message is missing subscriber id.

Action: *Define: ONS_INTERNAL_REGISTER_MISSING_SUBSCRIBERID
Level:

Type:

Impact: Other

ENS-00004: Connection %s register invalid subscriber ID: %s

Cause: The register message has an invalid subscriber id.

Action: *Define: ONS_INTERNAL_REGISTER_INVALID_SUBSCRIBERID
Level:

Type:

Impact: Other

ENS-00005: Connection %s register missing: %s

Cause: The register message is missing a register id.

Action: *Define: ONS_INTERNAL_REGISTER_MISSING_REGISTERID
Level:

Type:

Impact: Other

ENS-00006: Connection %s register duplicate ID: %s

Cause: A duplicate ID in the connection register.

Action: *Define: ONS_INTERNAL_REGISTER_DUPLICATEID
Level:

Type:

Impact: Other

ENS-00007: Connection %s register bad subscriber ID: %d

Cause: The register has a bad subscriber ID.

Action: *Define: ONS_INTERNAL_REGISTER_BAD_SUBSCRIBER_ID
Level:

Type:

Impact: Other

ENS-00008: Connection %s register subscriber ID %d already registered

Cause: The subscriber ID is already registered.

Action: *Define: ONS_INTERNAL_SUBSCRIBER_ALREADY_REGISTERED
Level:

Type:

Impact: Other

ENS-00009: Connection %s unregister missing: %s

Cause: The unregister message is missing the register id.

Action: *Define: ONS_INTERNAL_UNREGISTER_MISSING_REGISTERID
Level:

Type:

Impact: Other

ENS-00010: SELECT (%s)

Cause: The listener thread encountered an error in the select system call while listening for incoming connections.

Action: *Define: ONS_LISTENER_SELECT_ERROR
Level:

Type:

Impact: Other

ENS-00011: %s: ACCEPT (%s)

Cause: The listener thread encountered an error in the accept system call while accepting an incoming connection.

Action: *Define: ONS_LISTENER_ACCEPT_ERROR
Level:

Type:

Impact: Other

ENS-00012: Could not get address information for %s %s.

Cause: The listener could not obtain address information for the given host or ip and port specification.

Action: *Define: ONS_LISTENER_GETINFO_ERROR
Level:

Type:

Impact: Other

ENS-00013: Listener thread terminated

Cause: The listener thread has terminated.

Action: *Define: ONS_LISTENER_TERMINATED
Level:

Type:

Impact: Other

ENS-00014: %s: received invalid discovery announcement (%d bytes).

Cause: The listener received an invalid discovery message.

Action: *Define: ONS_LISTENER_INVALID_DISCOVER
Level:

Type:

Impact: Other

ENS-00015: %s: SOCKET (%s)

Cause: In initializing the network for the listener thread, a socket error was encountered.

Action: *Define: ONS_LISTENER_SOCKET_ERROR
Level:

Type:

Impact: Other

ENS-00016: %s: SETSOCKOPT %s (%s)

Cause: In initializing the network for the listener thread, a socket option error was encountered.

Action: *Define: ONS_LISTENER_SETSOCKOPT_ERROR
Level:

Type:

Impact: Other

ENS-00017: %s: BIND (%s)

Cause: In initializing the network for the listener thread, an error was encountered in the bind system call.

Action: *Define: ONS_LISTENER_BIND_ERROR
Level:

Type:

Impact: Other

ENS-00018: %s: LISTEN (%s)

Cause: An error was encountered in the listen system call while initializing the network for the listener thread.

Action: *Define: ONS_LISTENER_LISTEN_ERROR
Level:

Type:

Impact: Other

ENS-00019: Connection %s Subscribe missing %s

Cause: The subscription message is missing a subscribe id.

Action: *Define: ONS_SUBSCRIPTION_SUBSCRIBE_MISSING_SUBSCRIBEID
Level:

Type:

Impact: Other

ENS-00020: Connection %s Subscribe invalid %s%s

Cause: The subscription message has an invalid subscriber id.

Action: *Define: ONS_SUBSCRIPTION_SUBSCRIBE_INVALID_SUBSCRIBEID
Level:

Type:

Impact: Other

ENS-00021: Connection %s Duplicate subscriber id %d

Cause: The subscription message has a duplicate subscriber id.

Action: *Define: ONS_SUBSCRIPTION_DUPLICATE_SUBSCRIBEID
Level:

Type:

Impact: Other

ENS-00022: Connection %s Subscribe missing %s

Cause: The subscription message is missing the subscription string.

Action: *Define: ONS_SUBSCRIPTION_SUBSCRIBE_MISSING_SUBSCRIPTION
Level:

Type:

Impact: Other

ENS-00023: RMD %s missing name

Cause: The RMD element is missing the name attribute.

Action: *Define: OPMN_RMD_MISSING_NAME
Level:

Type:

Impact: Other

ENS-00024: Connection %s Subscriber %d subscription error%s

Cause: There was a subscription error.

Action: *Define: ONS_SUBSCRIPTION_ERROR
Level:

Type:

Impact: Other

ENS-00025: Connection %s Unsubscribe missing %s

Cause: A subscriber from this connection's list sent an unsubscribe message. The message is missing a subscriber ID.

Action: *Define: ONS_SUBSCRIPTION_UNSUBSCRIBE_MISSING_SUBSCRIBEID
Level:

Type:

Impact: Other

ENS-00026: Connection %s Unsubscribe invalid %s%s

Cause: This connection received an invalid subscriber ID in the unsubscribe message.

Action: *Define: ONS_SUBSCRIPTION_UNSUBSCRIBE_INVALID_SUBSCRIBEID
Level:

Type:

Impact: Other

ENS-00027: RMD %s invalid interval

Cause: The RMD interval attribute value is <= 0.

Action: *Define: OPMN_RMD_INVALID_INTERVAL
Level:

Type:

Impact: Other

ENS-00028: Connection %s Subscriber %d not found

Cause: The subscriber with the subscriber ID in the unsubscribe message was not found.

Action: *Define: ONS_SUBSCRIPTION_SUBSCRIBER_NOTFOUND
Level:

Type:

Impact: Other

ENS-00029: Connection %s Subscriber %d\t%s

Cause: An error was encountered in parsing the subscription.

Action: *Define: ONS_SUBSCRIPTION_SUBSCRIBER_ERR
Level:

Type:

Impact: Other

ENS-00030: %s dlopen failed:%s

Cause: Failed to open the specified shared library.

Action: *Define: ONS_SYSTEM_DLOPEN_FAILED
Level:

Type:

Impact: Other

ENS-00031: %s: symbol not found

Cause: Attempted to get the address of the symbol with the given name. However, could not find the symbol.

Action: *Define: ONS_SYSTEM_DLSYM_FAILED
Level:

Type:

Impact: Other

ENS-00032: %s LoadLibrary failed: %d

Cause: Could not load the shared library with the given file name.

Action: *Define: ONS_SYSTEM_LOADLIB_FAILED
Level:

Type:

Impact: Other

ENS-00033: worker thread create (%s)

Cause: An error occured while creating the worker thread.

Action: *Define: ONS_WORKER_THREAD_CREATE_ERR
Level:

Type:

Impact: Other

ENS-00034: Read failed from %s (%s) [%d/%d]

Cause: The server failed to read from the form factor file.

Action: *Define: ONS_SERVER_FORMFACTORFILE_READ_ERR
Level:

Type:

Impact: Other

ENS-00035: Worker Thread %d SND error [%d:%d] (%s): connection %s

Cause: The worker thread got an error while sending a block of data to the connection.

Action: *Define: ONS_WORKER_SND_ERROR
Level:

Type:

Impact: Other

ENS-00036: %s: received invalid announcement addr (%u bytes).

Cause: The listener received a discovery message with an invalid addr string length.

Action: *Define: ONS_LISTENER_INVALID_ANNOUNCE
Level:

Type:

Impact: Other

ENS-00037: %s: ons_subscriber_create() failed: %s

Cause: Creation of a dedicated subscriber failed during initialization of the pm ons broadcast interface.

Action: *Define: ONS_PM_DEDICATED_SUBSCRIBER_CREATE_FAILED
Level:

Type:

Impact: Other

ENS-00038: %s: ons_publisher_create() failed

Cause: Creation of a dedicated publisher failed during initialization of the pm ons broadcast interface.

Action: *Define: ONS_PM_DEDICATED_PUBLISHER_CREATE_FAILED
Level:

Type:

Impact: Other

ENS-00039: ons_init_pm: responseThread create failed (errno=%d)

Cause: Creation of response processing thread failed during initialization of the pm ons broadcast interface.

Action: *Define: ONS_PM_RESP_PROCESSING_THR_CREATE_FAILED
Level:

Type:

Impact: Other

ENS-00040: %s: request %u broadcast failed

Cause: In order to get information from remote PMs, a broadcast was attempted, which failed.

Action: *Define: ONS_PM_REQ_BROADCAST_FAILED
Level:

Type:

Impact: Other

ENS-00041: %s: ons_notification_create() failed (register)

Cause: The Register command notification creation failed.

Action: *Define: ONS_PM_NOTIFICATION_CREATE_FAILED
Level:

Type:

Impact: Other

ENS-00042: %s: register: unexpected response: %s

Cause: Got an unexpected response to a register notification.

Action: *Define: ONS_PM_REGISTER_UNEXPECTED_RESP
Level:

Type:

Impact: Other

ENS-00043: %s: register: bad status: %s (%s)

Cause: Got a bad status in response to a register notification.

Action: *Define: ONS_PM_REGISTER_BAD_STATUS
Level:

Type:

Impact: Other

ENS-00044: %s: ons_notification_create() failed (broadcast)

Cause: Creation of a broadcast notification failed.

Action: *Define: ONS_PM_BROADCAST_NOTIF_CR_FAILED
Level:

Type:

Impact: Other

ENS-00045: %s: ons_subscriber_receive() failed

Cause: The response thread could not receive an incoming notification.

Action: *Define: ONS_PM_SUBSCRIBER_RECV_FAILED
Level:

Type:

Impact: Other

ENS-00046: ons_init_pm: processBroadcastThread create failed (errno=%d)

Cause: The response thread failed to create a process broadcast thread.

Action: *Define: ONS_PM_BROADCAST_THR_CR_FAILED
Level:

Type:

Impact: Other

ENS-00047: %s: unknown response type: %s

Cause: The response thread received an unknown notification type.

Action: *Define: ONS_PM_UNKNOWN_EVENT_TYPE
Level:

Type:

Impact: Other

ENS-00048: %s: no response type

Cause: The response thread received a null notification type.

Action: *Define: ONS_PM_NULLEVENT_TYPE
Level:

Type:

Impact: Other

ENS-00049: %s: response thread terminated

Cause: The response thread has terminated.

Action: *Define: ONS_PM_RESP_THR_TERMINATED
Level:

Type:

Impact: Other

ENS-00050: %s: no data!

Cause: The incoming data notification contained no data body.

Action: *Define: ONS_PM_NO_DATA_IN_DATA_EVENT
Level:

Type:

Impact: Other

ENS-00051: %s: dest = 0x%x, stamp = 0x%x, route = 0x%x

Cause: The dest, stamp or route field in an incoming data query notification is missing.

Action: *Define: ONS_PM_DATAQUERY_DATA_MISSING
Level:

Type:

Impact: Other

ENS-00052: %s: ons_notification_create() failed (reply to broadcast)

Cause: Creation of a reply to a data query notification failed.

Action: *Define: ONS_PM_REPLY_TO_BROADCAST_FAILED
Level:

Type:

Impact: Other

ENS-00053: %s: missing %s

Cause: The notification is missing the server down identifier.

Action: *Define: ONS_PM_MISSING_SERVER_DOWN_IDENTIFIER
Level:

Type:

Impact: Other

ENS-00054: %s: %s not set in broadcast reply

Cause: ID not found in broadcast reply.

Action: *Define: ONS_PM_ID_NOTFOUND
Level:

Type:

Impact: Other

ENS-00055: %s: getServerAddr: address error: %s

Cause: cannot scan adress from the given data stream

Action: *Define: ONS_PM_ADDRESS_ERROR
Level:

Type:

Impact: Other

ENS-00056: Connection thread create %s (%s)

Cause: The dedicated connection thread could not be created.

Action: *Define: ONS_CONN_THREAD_CREATE_ERR
Level:

Type:

Impact: Other

ENS-00057: Closing active connection %s

Cause: The active connection is being stopped.

Action: *Define: ONS_CONN_ACTIVE_CLOSE
Level:

Type:

Impact: Other

ENS-00058: Passive connection %s missing connect

Cause: In a passive connection, the first message must be a connect. This may be a malicious attack on the specified ONS port.

Action: *Define: ONS_CONN_MISSING_CONNECT
Level:

Type:

Impact: Other

ENS-00059: Local connection %s missing form factor%s

Cause: The local passive connection must contain the current form factor. This message is logged when it does not, which is caused either by an OPMN managed process started as a different user than OPMN, or an attempt is being made to issue an OPMN request as a user other than the one that started OPMN.

Action: Check if an OPMN managed process was manually started as a different user than OPMN (and stop it). Check if requests to OPMN are being issued by the wrong user. *Define: ONS_CONN_MISSING_FORMFACTOR
Level:

Type:

Impact: Other

ENS-00060: Local connection %s invalid form factor%s

Cause: The local connection contains an invalid form factor. This is caused either by an old application left running from an alternate ORACLE_HOME with the same notification-server local port as the current OPMN, or the local port was changed in opmn.xml without first shutting down OPMN.

Action: Check if an OPMN managed process was started from a different ORACLE_HOME than the current running OPMN (and stop it). Check if the notification-server local port in opmn.xml was changed without shutting OPMN down first (stop this OPMN). *Define: ONS_CONN_INVALID_FORMFACTOR
Level:

Type:

Impact: Other

ENS-00061: Request connection %s invalid connect message

Cause: The request port received an invalid connect message. This may be a malicious attack on the OPMN request port.

Action: *Define: ONS_CONN_REQPORT_INVALIDFORMAT
Level:

Type:

Impact: Other

ENS-00062: Passive connection %s send reply failed

Cause: The server tried to send a reply to a connect and failed.

Action: *Define: ONS_CONN_PASSIVECONNECT_REPLY_FAILED
Level:

Type:

Impact: Other

ENS-00063: Server connection %s not on remote port

Cause: The server connection is not on remote port. This may be a malicious attack on the specified ONS port.

Action: *Define: ONS_CONN_NOTON_REMOTEPORT
Level:

Type:

Impact: Other

ENS-00064: Failed to create connection manager thread

Cause: The server failed to create the connection manager thread.

Action: *Define: ONS_CONN_MANAGER_THR_CREATE_ERR
Level:

Type:

Impact: Other

ENS-00065: Passive connection %d %s overrides Active %d %s

Cause: The passive connection overrides the active connection and will be used for communication with the remote server.

Action: *Define: ONS_CONN_USE_PASSIVE_CONN
Level:

Type:

Impact: Other

ENS-00066: Passive connection %s yields to Active %s

Cause: The active connection to the remote server will be used. The passive connection will be terminated.

Action: *Define: ONS_CONN_USE_ACTIVE_CONN
Level:

Type:

Impact: Other

ENS-00067: Connection %s connect reply failed

Cause: The server attempted to send a success reply for a connection to the remote server and failed.

Action: *Define: ONS_CONN_REPLYFAILED
Level:

Type:

Impact: Other

ENS-00068: Shared connection %s send reply (success) failed

Cause: The server attempted to send a reply to the connect message and failed.

Action: *Define: ONS_CONN_SHAREDCONN_REPLYFAILED1
Level:

Type:

Impact: Other

ENS-00069: Connection %s status reply for connect failed

Cause: The server attempted to send a reply in response to the connect message and failed.

Action: *Define: ONS_CONN_STATUS_REPLY_FAILED
Level:

Type:

Impact: Other

ENS-00070: Connection %s header RCV failed (%s) coFlags=%x

Cause: The server tried to read a message from a socket and got a RCV error.

Action: *Define: ONS_CONN_HEADER_RCV_FAILED
Level:

Type:

Impact: Other

ENS-00071: RMD %s duplicate entry

Cause: The same name has been specified for more than one RMD in a block.

Action: *Define: OPMN_RMD_DUPLICATE_NAME
Level:

Type:

Impact: Other

ENS-00072: %s: SNDTO failed (%s)

Cause: The listener encountered an error when sending a discovery message.

Action: *Define: ONS_LISTENER_SNDTO_ERROR
Level:

Type:

Impact: Other

ENS-00073: %s: RCVFROM failed (%s)

Cause: The listener encountered an error when receiving a discovery message.

Action: *Define: ONS_LISTENER_RCVFROM_ERROR
Level:

Type:

Impact: Other

ENS-00074: Connection %s SOCKET (%s)

Cause: The socket system call returned an error during creation of an active connection.

Action: *Define: ONS_CONN_SOCKET_ERR
Level:

Type:

Impact: Other

ENS-00075: Connection %s connect (%s)

Cause: The connect system call returned an error during creation of an active connection.

Action: *Define: ONS_CONN_SOCK_CONNECT_ERR
Level:

Type:

Impact: Other

ENS-00076: Connection %s SND connect (%s)

Cause:

Action: *Define: ONS_CONN_SOCK_WRITE_ERR
Level:

Type:

Impact: Other

ENS-00077: Active connection %s missing status

Cause: The status reply on an active connection is missing.

Action: *Define: ONS_CONN_GETMSGERR
Level:

Type:

Impact: Other

ENS-00078: Connection %s connect status: bad format:%s

Cause: The status message from an active connection has a badly formatted header.

Action: *Define: ONS_CONN_BADFORMAT_HEADER
Level:

Type:

Impact: Other

ENS-00079: Connection %s connect status: failed: %s

Cause: The active connection failed.

Action: *Define: ONS_CONN_FAILED
Level:

Type:

Impact: Other

ENS-00080: Connection %s body RCV failed (%s) coFlags=%x

Cause: The server tried to read a message from a socket and got a RCV error.

Action: *Define: ONS_CONN_BODY_RCV_FAILED
Level:

Type:

Impact: Other

ENS-00081: Connection %s invalid notification header length: %u.

Cause: A notification been received with a header longer than the maximum allowable size.

Action: *Define: ONS_CONN_HEADER_MAX
Level:

Type:

Impact: Other

ENS-00082: Connection %s socket data stream is out of sync

Cause: The data stream between the local connection and the remote connection is out of sync.

Action: *Define: ONS_CONN_OUT_OF_SYNC
Level:

Type:

Impact: Other

ENS-00083: Connection %s: could not resolve IP for configured host name (%s)

Cause: IP could not be resolved.

Action: *Define: ONS_CONN_COULD_NOT_RESOLVE_IP
Level:

Type:

Impact: Other

ENS-00084: Connection %s invalid notification header:%s

Cause: The connection received an invalid notification header. This may be a malicious attack on the specified ONS port.

Action: *Define: ONS_CONN_INVALID_HEADER
Level:

Type:

Impact: Other

ENS-00085: Failed to create ons monitor thread

Cause: The server failed to create the ons monitor thread.

Action: *Define: ONS_SERVER_PERF_THR_CREATE_ERR
Level:

Type:

Impact: Other

ENS-00086: Failed to initialize network layer

Cause: The server failed to initialize the network layer.

Action: *Define: ONS_SERVER_NETWORK_INIT_FAILED
Level:

Type:

Impact: Other

ENS-00087: Connection %s notification missing origin:%s

Cause: The connection received a notification that is missing the origin field in the header.

Action: *Define: ONS_CONN_MISSING_ORIGIN
Level:

Type:

Impact: Other

ENS-00088: Connection %s notification invalid origin:%s

Cause: The connection received a notification with an invalid origin field in the header.

Action: *Define: ONS_CONN_INVALID_ORIGIN
Level:

Type:

Impact: Other

ENS-00089: Failed to get host name (%s)

Cause: The server failed to get a host name.

Action: *Define: ONS_SERVER_GETHOSTNAME_FAILED
Level:

Type:

Impact: Other

ENS-00090: ONS server initiated

Cause: The multi-threaded ONS server has been initiated!

Action: *Define: ONS_SERVER_INITIATED
Level:

Type:

Impact: Other

ENS-00091: worker thread creation error (%d)

Cause: During the process of worker threads' creation, the server encountered a failure. This is a fatal error.

Action: *Define: ONS_SERVER_WORKERTHREAD_CREATE_ERROR
Level:

Type:

Impact: Other

ENS-00092: Could not open %s (%s)

Cause: The server could not open or create the form factor file.

Action: *Define: ONS_SERVER_FORMFACTORFILE_CREATE_ERR
Level:

Type:

Impact: Other

ENS-00093: Write failed to %s (%s) [%d/%d]

Cause: The server failed to write to the form factor file.

Action: *Define: ONS_SERVER_FORMFACTORFILE_WRITE_ERR
Level:

Type:

Impact: Other

ENS-00094: topology syntax error: invalid discover syntax:\"%s\"

Cause: unable to parse the discover entry

Action: *Define: ONS_SERVER_INVALID_DISCOVER_FORMAT
Level:

Type:

Impact: Other

ENS-00095: Connection %s notification missing stamp:%s

Cause: The connection received a notification that is missing the stamp field in the header.

Action: *Define: ONS_CONN_MISSING_STAMP
Level:

Type:

Impact: Other

ENS-00096: Connection %s notification invalid stamp:%s

Cause: The connection received a notification with an invalid stamp field in the header.

Action: *Define: ONS_CONN_INVALID_STAMP
Level:

Type:

Impact: Other

ENS-00097: Connection %s notification missing content-length:%s

Cause: The connection received a notification that is missing the content-length field in the header.

Action: *Define: ONS_CONN_MISSING_CONTENT_LENGTH
Level:

Type:

Impact: Other

ENS-00098: topology syntax error: invalid hostname:port syntax\"%s\"

Cause: unable to parse the hostname:port

Action: *Define: ONS_SERVER_INVALID_HOSTNAME_PORT_FORMAT
Level:

Type:

Impact: Other

ENS-00099: XML parse: %s:\tunknown process-set %s.

Cause: An invalid process-set was specified for the dependency in opmn.xml.

Action: *Define: OPMN_NLS_MSG_00162
Level:

Type:

Impact: Other

ENS-00100: XML parse: %s:\tunknown process-type %s.

Cause: An invalid process-type was specified for the dependency in opmn.xml.

Action: *Define: OPMN_NLS_MSG_00163
Level:

Type:

Impact: Other

ENS-00101: XML parse: %s:\tunknown component %s.

Cause: An invalid component was specified for the dependency in opmn.xml.

Action: *Define: OPMN_NLS_MSG_00164
Level:

Type:

Impact: Other

ENS-00102: XML parse: %s\tunknown ias instance %s\tAssuming remote dependency.

Cause: An unknown ias instance was specified for the dependency in opmn.xml -- this dependency will be assumed to be for a managed process-set on a remote OPMN server.

Action: *Define: OPMN_NLS_MSG_00165
Level:

Type:

Impact: Other

ENS-00103: XML parse: circular managed process dependency:%s

Cause: A managed process dependency has been configured in opmn.xml that eventually leads to a dependency upon itself.

Action: *Define: OPMN_NLS_MSG_00166
Level:

Type:

Impact: Other

ENS-00104: %s: Proc %u:%u could not schedule %s (%s)

Cause: The specified job could not be scheduled for the process referenced by the given dependency for autostop or autorestart.

Action: *Define: OPMN_NLS_MSG_00167
Level:

Type:

Impact: Other

ENS-00105: XML parser init: character set initialization failed.

Cause: The XML parser failed its character set initialization.

Action: *Define: OPMN_NLS_MSG_00175
Level:

Type:

Impact: Other

ENS-00106: Connection %s notification excessive content-length %u

Cause: The connection received a notification with an content-length that exceeds the maximum allowed value.

Action: *Define: ONS_CONN_INVALID_CONTENT_LENGTH
Level:

Type:

Impact: Other

ENS-00107: XML parser init: error %d.

Cause: The XML parser encountered the given error during init.

Action: *Define: OPMN_NLS_MSG_00177
Level:

Type:

Impact: Other

ENS-00108: XML parse failed: error %d.

Cause: The XML parser encountered the given error while parsing opmn.xml.

Action: *Define: OPMN_NLS_MSG_00179
Level:

Type:

Impact: Other

ENS-00109: XML: no root element.

Cause: opmn.xml does not have a root element.

Action: Verify that $ORACLE_HOME/conf/opmn.xml is correct. *Define: OPMN_NLS_MSG_00180
Level:

Type:

Impact: Other

ENS-00110: XML schema validation failed: error %d.

Cause: The schema validation for opmn.xml failed.

Action: Verify that $ORACLE_HOME/conf/opmn.xml is correct. *Define: OPMN_NLS_MSG_00181
Level:

Type:

Impact: Other

ENS-00111: XML parser terminate failed: error %d.

Cause: The XML parser encountered the given error while terminating.

Action: *Define: OPMN_NLS_MSG_00182
Level:

Type:

Impact: Other

ENS-00112: XML parse: notification-server is missing.

Cause: The notification-server section is missing from opmn.xml.

Action: Verify that $ORACLE_HOME/conf/opmn.xml is correct. *Define: OPMN_NLS_MSG_00183
Level:

Type:

Impact: Other

ENS-00113: XML parse: notification-server ports are missing.

Cause: The notification-server ports element is missing from opmn.xml.

Action: Verify that $ORACLE_HOME/conf/opmn.xml is correct. *Define: OPMN_NLS_MSG_00184
Level:

Type:

Impact: Other

ENS-00114: XML parse: notification-server local port is missing.

Cause: The notification-server local port is not configured.

Action: At a minimum the local port for the notification server must be configured. *Define: OPMN_NLS_MSG_00185
Level:

Type:

Impact: Other

ENS-00115: XML parse: process-manager is missing.

Cause: The process-manager section is missing from opmn.xml.

Action: Verify that $ORACLE_HOME/conf/opmn.xml is correct. *Define: OPMN_NLS_MSG_00186
Level:

Type:

Impact: Other

ENS-00116: XML parse: no ias instance is configured.

Cause: At least one ias instance must be configured in opmn.xml.

Action: Verify that $ORACLE_HOME/conf/opmn.xml is correct. *Define: OPMN_NLS_MSG_00187
Level:

Type:

Impact: Other

ENS-00117: XML parse: process module is missing path.

Cause: A process module configured in opmn.xml does not have a specified path.

Action: Verify that $ORACLE_HOME/conf/opmn.xml is correct. *Define: OPMN_NLS_MSG_00188
Level:

Type:

Impact: Other

ENS-00118: XML parse: module %s unknown status: %s.

Cause: The given module is configured with an invalid status.

Action: Verify that $ORACLE_HOME/conf/opmn.xml is correct. *Define: OPMN_NLS_MSG_00189
Level:

Type:

Impact: Other

ENS-00119: XML parse: module %s module-id is missing id.

Cause: The given module is configured without an id attribute.

Action: Verify that $ORACLE_HOME/conf/opmn.xml is correct. *Define: OPMN_NLS_MSG_00190
Level:

Type:

Impact: Other

ENS-00120: XML parse: ias instance is missing config home.

Cause: If multiple ias instances are configured, a config-home value must be specified.

Action: Verify that $ORACLE_HOME/conf/opmn.xml is correct. *Define: OPMN_NLS_MSG_00191
Level:

Type:

Impact: Other

ENS-00121: XML parse: duplicate ias instance config home (%s).

Cause: Multiple ias instances are configured with the same config-home.

Action: Verify that $ORACLE_HOME/conf/opmn.xml is correct. *Define: OPMN_NLS_MSG_00192
Level:

Type:

Impact: Other

ENS-00122: XML parse: %s: ias component is missing id.

Cause: The given ias component is missing the id attribute.

Action: *Define: OPMN_NLS_MSG_00193
Level:

Type:

Impact: Other

ENS-00123: XML parse: %s: component %s unknown status: %s.

Cause: The given component is configured with an invalid status.

Action: *Define: OPMN_NLS_MSG_00194
Level:

Type:

Impact: Other

ENS-00124: XML parse: %s: duplicate component (%s).

Cause: More than one component with the same id has been configured for the same ias instance.

Action: *Define: OPMN_NLS_MSG_00195
Level:

Type:

Impact: Other

ENS-00125: XML parse: %s: process-type is missing id.

Cause: The given process-type is missing the id attribute.

Action: *Define: OPMN_NLS_MSG_00196
Level:

Type:

Impact: Other

ENS-00126: XML parse: %s: process-type %s unknown status: %s.

Cause: The given process-type is configured with an invalid status.

Action: *Define: OPMN_NLS_MSG_00197
Level:

Type:

Impact: Other

ENS-00127: XML parse: %s: duplicate process-type (%s).

Cause: More than one process-type with the same id has been configured for the same component.

Action: *Define: OPMN_NLS_MSG_00198
Level:

Type:

Impact: Other

ENS-00128: XML parse: %s: process-type %s is missing module-id.

Cause: The given process-type is missing the module-id attribute.

Action: *Define: OPMN_NLS_MSG_00199
Level:

Type:

Impact: Other

ENS-00129: XML parse: %s: No module for process-type (%s).

Cause: The module-id specified for the given process-type has no associated module.

Action: *Define: OPMN_NLS_MSG_00200
Level:

Type:

Impact: Other

ENS-00130: XML parse: %s: process-set is missing id.

Cause: The given process-set is missing the id attribute.

Action: *Define: OPMN_NLS_MSG_00201
Level:

Type:

Impact: Other

ENS-00131: XML parse: %s: process-set %s unknown status: %s.

Cause: The given process-set is configured with an invalid status.

Action: *Define: OPMN_NLS_MSG_00202
Level:

Type:

Impact: Other

ENS-00132: XML parse: %s: duplicate process-set (%s).

Cause: More than one process-set with the same id has been configured for the same process-type.

Action: *Define: OPMN_NLS_MSG_00203
Level:

Type:

Impact: Other

ENS-00133: XML parse: %s: Invalid numprocs (%s) for %s.

Cause: A non-numeric invalid value has been specified for numprocs.

Action: *Define: OPMN_NLS_MSG_00204
Level:

Type:

Impact: Other

ENS-00134: XML parse: %s: Invalid minprocs (%s) for %s.

Cause: A non-numeric invalid value has been specified for minprocs.

Action: *Define: OPMN_NLS_MSG_00205
Level:

Type:

Impact: Other

ENS-00135: XML parse: %s: Invalid maxprocs (%s) for %s.

Cause: A non-numeric invalid value has been specified for maxprocs.

Action: *Define: OPMN_NLS_MSG_00206
Level:

Type:

Impact: Other

ENS-00136: XML parse: %s: numprocs used with min/maxprocs for %s.

Cause: numprocs may not be specified with minprocs and maxprocs.

Action: *Define: OPMN_NLS_MSG_00207
Level:

Type:

Impact: Other

ENS-00137: XML parse: %s: numprocs or both min/maxprocs must be set for %s.

Cause: numprocs or both minprocs and maxprocs must be configured.

Action: *Define: OPMN_NLS_MSG_00208
Level:

Type:

Impact: Other

ENS-00138: XML parse: %s: maxprocs <= minprocs for %s.

Cause: maxprocs must be greater than minprocs.

Action: *Define: OPMN_NLS_MSG_00209
Level:

Type:

Impact: Other

ENS-00139: XML parse: %s: port is missing id.

Cause: The port element is missing the id attribute.

Action: *Define: OPMN_NLS_MSG_00210
Level:

Type:

Impact: Other

ENS-00140: XML parse: %s: duplicate port id (%s).

Cause: A duplicate port id was specified for the same process-type.

Action: *Define: OPMN_NLS_MSG_00211
Level:

Type:

Impact: Other

ENS-00141: XML parse: %s: port %s is missing range.

Cause: The port element is missing the range attribute.

Action: *Define: OPMN_NLS_MSG_00212
Level:

Type:

Impact: Other

ENS-00142: XML parse: %s: invalid port range for %s.

Cause: The port element has an invalid port range.

Action: *Define: OPMN_NLS_MSG_00213
Level:

Type:

Impact: Other

ENS-00143: XML parse: %s: invalid port value for %s.

Cause: THe port element has an invalid port value.

Action: *Define: OPMN_NLS_MSG_00214
Level:

Type:

Impact: Other

ENS-00144: XML parse: %s: high port value < low for %s.

Cause: The high port value in a port range must be greater than or equal to the low port value.

Action: *Define: OPMN_NLS_MSG_00215
Level:

Type:

Impact: Other

ENS-00145: XML parse: %s: invalid retry value for %s.

Cause: An invalid retry value was specified.

Action: *Define: OPMN_NLS_MSG_00216
Level:

Type:

Impact: Other

ENS-00146: XML parse: %s: invalid interval value for %s.

Cause: An invalid interval value was specified.

Action: *Define: OPMN_NLS_MSG_00217
Level:

Type:

Impact: Other

ENS-00147: XML parse: %s: invalid timeout value for %s.

Cause: An invalid timeout value was specified.

Action: *Define: OPMN_NLS_MSG_00218
Level:

Type:

Impact: Other

ENS-00148: Connection %s: notification missing generating node%s

Cause: The connection received a notification missing the generating node field in the header.

Action: *Define: ONS_CONN_MISSING_GNODE
Level:

Type:

Impact: Other

ENS-00149: XML parse: %s: DB dependency is missing db-connect-info.

Cause: A database dependency configuration is missing the db-connect-info attribute.

Action: *Define: OPMN_NLS_MSG_00220
Level:

Type:

Impact: Other

ENS-00150: XML parse: %s: OID dependency is missing address.

Cause: An OID dependency configuration is missing the address attribute.

Action: *Define: OPMN_NLS_MSG_00221
Level:

Type:

Impact: Other

ENS-00151: XML parse: %s: OSSO dependency is missing host.

Cause: An OSSO dependency configuration is missing the host attribute.

Action: *Define: OPMN_NLS_MSG_00222
Level:

Type:

Impact: Other

ENS-00152: XML parse: %s: OSSO dependency is missing port.

Cause: An OSSO dependency configuration is missing the port attribute.

Action: *Define: OPMN_NLS_MSG_00223
Level:

Type:

Impact: Other

ENS-00153: XML parse: %s: OSSO dependency is missing URI.

Cause: An OSSO dependency configuration is missing the URI attribute.

Action: *Define: OPMN_NLS_MSG_00224
Level:

Type:

Impact: Other

ENS-00154: XML parse: %s: Managed process dependency is missing component.

Cause: A managed process dependency configuration is missing the component attribute.

Action: *Define: OPMN_NLS_MSG_00225
Level:

Type:

Impact: Other

ENS-00155: XML parse: %s: Managed process dependency is missing process-type.

Cause: A managed process dependency configuration is missing the process-type attribute.

Action: *Define: OPMN_NLS_MSG_00226
Level:

Type:

Impact: Other

ENS-00156: XML parse: %s: Managed process dependency is missing process-set.

Cause: A managed process dependency configuration is missing the process-set attribute.

Action: *Define: OPMN_NLS_MSG_00227
Level:

Type:

Impact: Other

ENS-00157: XML parse: %s: data category is missing id.

Cause: The data-category id attribute is missing.

Action: *Define: OPMN_NLS_MSG_00228
Level:

Type:

Impact: Other

ENS-00158: XML parse: %s: environment is missing id.

Cause: The environment id attribute is missing.

Action: *Define: OPMN_NLS_MSG_00229
Level:

Type:

Impact: Other

ENS-00159: XML parse: %s: environment %s is missing value.

Cause: The given environment configuration is missing the value attribute.

Action: *Define: OPMN_NLS_MSG_00230
Level:

Type:

Impact: Other

ENS-00160: XML parse: %s: missing log-file.

Cause: The log-file element is missing.

Action: *Define: OPMN_NLS_MSG_00231
Level:

Type:

Impact: Other

ENS-00161: XML parse: %s: duplicate launch-target id.

Cause: A duplicate launch id was configured in opmn.xml.

Action: *Define: OPMN_XML_PARSE_DUP_LAUNCH_TARGET
Level:

Type:

Impact: Other

ENS-00162: XML parse: %s: missing or invalid comp attribute -- %s

Cause: The log or debug element is missing the comp attribute, or the specified string is invalid.

Action: *Define: OPMN_NLS_MSG_00233
Level:

Type:

Impact: Other

ENS-00163: XML parse: %s: minimum log rotation-size is %d.

Cause: rotation-size is configured below the minimum value -- the minimum value will be used.

Action: *Define: OPMN_NLS_MSG_00234
Level:

Type:

Impact: Other

ENS-00164: Connection %s notification missing cluster id%s

Cause: The connection received a notification missing the cluster id field in the header.

Action: *Define: ONS_CONN_MISSING_CLUSTER_ID
Level:

Type:

Impact: Other

ENS-00165: Connection %s notification missing cluster name%s

Cause: The connection received a notification missing the cluster name field in the header.

Action: *Define: ONS_CONN_MISSING_CLUSTER_NAME
Level:

Type:

Impact: Other

ENS-00166: Connection %s notification missing instance id%s

Cause: The connection received a notification missing the instance id field in the header.

Action: *Define: ONS_CONN_MISSING_INSTANCE_ID
Level:

Type:

Impact: Other

ENS-00167: XML parse: %s: circular environment variable definition for %s.

Cause: The environment variable references another environment variable that eventually leads to a reference to this environment variable.

Action: *Define: OPMN_NLS_MSG_00238
Level:

Type:

Impact: Other

ENS-00168: XML parse: ONS topology %s missing list attribute

Cause: The given topology element is missing the list attribute.

Action: *Define: OPMN_ONS_TOPO_MISSING_LIST
Level:

Type:

Impact: Other

ENS-00169: XML parse: unknown ONS topology element: %s

Cause: The given ONS topology element is unknown.

Action: *Define: OPMN_ONS_TOPO_UNKNOWN
Level:

Type:

Impact: Other

ENS-00170: XML parse: missing instance id attribute

Cause: The the ias-instance id was not configured.

Action: *Define: OPMN_INST_NO_ID
Level:

Type:

Impact: Other

ENS-00171: XML parse: missing instance name attribute -- using instance id

Cause: The the ias-instance name attributwe was not configured -- using the id attribute value.

Action: *Define: OPMN_INST_NO_NAME
Level:

Type:

Impact: Other

ENS-00172: Failed to retrieve the path of the windows directory: %d

Cause: Windows system error: GetWindowsDirectory() call failed.

Action: *Define: OPMN_NLS_MSG_00243
Level:

Type:

Impact: Other

ENS-00173: Failed to retrieve the path of the system directory: %d

Cause: Windows system error: GetSystemDirectory() call failed.

Action: *Define: OPMN_NLS_MSG_00244
Level:

Type:

Impact: Other

ENS-00174: XML parse: %s: %s dependency is missing wallet-file while ssl is enabled

Cause: The wallet-file attribute is missing from ssl configuration for dependency check

Action: *Define: OPMN_NLS_MSG_00257
Level:

Type:

Impact: Other

ENS-00175: topology syntax error: invalid gateway syntax:\"%s\"

Cause: unable to parse the gateway entry

Action: *Define: ONS_SERVER_INVALID_GATEWAY_FORMAT
Level:

Type:

Impact: Other

ENS-00176: XML parse: %s: number of procs can not be specified for %s.

Cause: The module for the given process-set dynamically sets the value for numprocs, and so numprocs, minprocs and maxprocs must not be configured.

Action: *Define: OPMN_NLS_PARSE_AUTONUMPROCS
Level:

Type:

Impact: Other

ENS-00177: Connection %s notification missing instance name%s

Cause: The connection received a notification missing the instance name field in the header.

Action: *Define: ONS_CONN_MISSING_INSTANCE_NAME
Level:

Type:

Impact: Other

ENS-00178: %s: missing request field

Cause: The request field in an incoming data query notification is missing.

Action: *Define: ONS_PM_DATAQUERY_REQ_MISSING
Level:

Type:

Impact: Other

ENS-00179: Can not resolve %s for interface %s

Cause: The given host or ip could not be resolved within the specified ip interface.

Action: *Define: ONS_UNRESOLVED_INTERFACE
Level:

Type:

Impact: Other

ENS-00180: getaddrinfo(%s, %s, %d) failed (%s): %s

Cause: The given hostInternal, port and type could not be resolved.

Action: *Define: ONS_UNRESOLVED_ADDRINFO
Level:

Type:

Impact: Other

ENS-00181: XML parse: %s: unsupported ip interface

Cause: The specified IP interface is not supported on this system.

Action: *Define: OPMN_XML_PARSE_UNSUPPORTED_INTERFACE
Level:

Type:

Impact: Other

ENS-00182: XML parse: %s: unknown ip interface

Cause: The specified IP interface is unknown.

Action: *Define: OPMN_XML_PARSE_UNKNOWN_INTERFACE
Level:

Type:

Impact: Other

ENS-00183: Unresolved discovery multicast address and port: %s, %s

Cause: The given hostInternal, and port for multicast discovery cannot be resolved.

Action: *Define: ONS_UNRESOLVED_DISCOVER_INFO
Level:

Type:

Impact: Other

ENS-00184: Unable to resolve address for host: %s. %s

Cause: The call to gethostbyname for the hostname failed

Action: *Define: ONS_SERVER_GETHOSTBYNAME_FAILED
Level:

Type:

Impact: Other

ENS-00185: Invalid protocol to host: %s.

Cause: Invalid protocol returned for the host

Action: *Define: ONS_CONN_INVALID_PROTOCOL_TYPE
Level:

Type:

Impact: Other

ENS-00186: XML parse: %s libraries are configured with %s SSL layer.

Cause: The SSL layer configured does not match the loadbale library configuration.

Action: *Define: OPMN_NLS_XML_SSL_LIBRARY_MISMATCH
Level:

Type:

Impact: Other

ENS-00187: Connection %s: invalid ONS version (%d).

Cause: An OPMN server or client program using a depricated version of the ONS protocol attempted to connect with this OPMN server

Action: *Define: ONS_CONN_INVALID_ONS_VERSION
Level:

Type:

Impact: Other

ENS-00188: Connection %s: invalid ONS v3 connect header\t%s: %s.

Cause: An OPMN server attempted to connect with this OPMN server using an invalid header

Action: *Define: ONS_CONN_INVALID_HEADER_V3
Level:

Type:

Impact: Other

ENS-00189: XML parse: %s: service fail-over process type may only have one process-set (%s).

Cause: A process set configured with service-failover=true can have only one process-set, but this process-type is configured with two.

Action: *Define: OPMN_PARSE_SERVICE_SINGLE_PSET
Level:

Type:

Impact: Other

ENS-00190: XML parse: %s: service-weight must be >= 1.

Cause: The service-weight attribute was configured with a value < 1.

Action: *Define: OPMN_PARSE_SERVICE_INVALID_WEIGHT
Level:

Type:

Impact: Other

ENS-00191: XML parse: %s: service-weight may only be specified when service-failover=true.

Cause: The service-weight attribute may only be specified when service-failover=true.

Action: *Define: OPMN_PARSE_SERVICE_IMPROPER_WEIGHT
Level:

Type:

Impact: Other

ENS-00192: XML parse: %s: %s may not be specified when service-failover=true.

Cause: The numprocs attribute may not be specified for service failover types.

Action: *Define: OPMN_PARSE_SERVICE_EXCLUSION
Level:

Type:

Impact: Other

ENS-00193: Failed to create connection status thread.

Cause: The server failed to create the connection status thread.

Action: *Define: ONS_CONN_STATUS_THR_CREATE_ERR
Level:

Type:

Impact: Other

ENS-00194: Failed to initialize remote pm interface.

Cause: Internal error while initializing module interface.

Action: *Define: OPMN_ONS_PM_INIT_FAILED
Level:

Type:

Impact: Other

ENS-00195: Connection %s missing join.

Cause: Server connections must exchange join messages when they connect, but the remote server did not send one when expected.

Action: *Define: ONS_CONN_MISSING_JOIN
Level:

Type:

Impact: Other

ENS-00196: Connection %s: join message missing field %s.

Cause: The join message from the remote server was missing the expected field.

Action: *Define: ONS_CONN_JOIN_INCOMPLETE
Level:

Type:

Impact: Other

ENS-00197: Connection %s: io timeout (%u).

Cause: IO for the connection timed out.

Action: *Define: ONS_CONN_TIMEOUT
Level:

Type:

Impact: Other

ENS-00198: RMD %s conditional missing value attribute

Cause: The conditional is missing the value attribute.

Action: *Define: OPMN_RMD_COND_NOVALUE
Level:

Type:

Impact: Other

ENS-00199: RMD %s action missing value attribute

Cause: The action is missing the value attribute.

Action: *Define: OPMN_RMD_ACTION_NOVALUE
Level:

Type:

Impact: Other

ENS-00200: RMD %s exception missing value attribute

Cause: The exception is missing the value attribute.

Action: *Define: OPMN_RMD_EXCEPTION_NOVALUE
Level:

Type:

Impact: Other

ENS-00201: RMD %s unknown element

Cause: The RMD has an unknown element type declared.

Action: *Define: OPMN_RMD_UNKNOWN_ELT
Level:

Type:

Impact: Other

ENS-00202: RMD %s duplicate conditional

Cause: The RMD has more than one conditional defined.

Action: *Define: OPMN_RMD_COND_DUP
Level:

Type:

Impact: Other

ENS-00203: RMD %s missing conditional

Cause: The RMD is missing the conditional element.

Action: *Define: OPMN_RMD_NO_COND
Level:

Type:

Impact: Other

ENS-00204: RMD %s missing action

Cause: The RMD is missing an action element.

Action: *Define: OPMN_RMD_NO_ACTION
Level:

Type:

Impact: Other

ENS-00205: RMD %s action or exception referenced element outside of conditional scope

Cause: An action or exception for the RMD referenced an element outside the scope of the conditional.

Action: *Define: OPMN_RMD_BAD_LEVEL
Level:

Type:

Impact: Other

ENS-00206: RMD %s conditional parse error: %s

Cause: The conditional syntax is invalid.

Action: *Define: OPMN_RMD_COND_PARSE
Level:

Type:

Impact: Other

ENS-00207: RMD %s invalid conditional %s operand

Cause: A conditional operand is invald.

Action: *Define: OPMN_RMD_COND_INVALID_OPERAND
Level:

Type:

Impact: Other

ENS-00208: RMD %s invalid action or exception timeout: %s

Cause: An action or exception has a timeout value <= 0.

Action: *Define: OPMN_RMD_ACTION_INVALID_TIMEOUT
Level:

Type:

Impact: Other

ENS-00209: RMD %s invalid action or exception syntax: %s

Cause: An action or exception has an invalid value string.

Action: *Define: OPMN_RMD_ACTION_INVALID_SYNTAX
Level:

Type:

Impact: Other

ENS-00210: RMD %s unknown action or exception type: %s

Cause: An action or exception has an invalid value string.

Action: *Define: OPMN_RMD_ACTION_UNKNOWN
Level:

Type:

Impact: Other

ENS-00211: RMD %s invalid action or exception argument count: %s

Cause: An action or exception has an invalid number of arguments.

Action: *Define: OPMN_RMD_ACTION_INVALID_ARGCOUNT
Level:

Type:

Impact: Other

ENS-00212: XML parse: %s: process-type %s status: %s, ias-component status is phantom.

Cause: The process-type status must be "phantom" if the ias-component status is "phantom".

Action: *Define: OPMN_NLS_PTYPE_NOT_PHANTOM
Level:

Type:

Impact: Other

ENS-00213: XML parse: %s: process-set %s status: %s, process-type status is phantom.

Cause: The process-set status must be "phantom" if the process-type status is "phantom".

Action: *Define: OPMN_NLS_PSET_NOT_PHANTOM
Level:

Type:

Impact: Other

35 EPMBPMUI-00101 to EPMBPMUI-01804

EPMBPMUI-00101: Initializing configuration factory

Cause: The application is initializing its configuration factory at application startup.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00102: Terminating configuration factory

Cause: The application is shutting down its configuration factory at application shutdown.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00201: Parameter "{0}" has value "{1}"

Cause: Reports the value of a configuration factory parameter during startup.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00204: Failed to initialize the class {0} with its default constructor.

Cause: The configuration factory could not create a configuration class.

Action: Consult the application configuration log for further details.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00205: Failed to instantiate the class {0}

Cause: The configuration factory could not create a configuration class.

Action: Consult the application configuration log for further details.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00206: Failed to initialize the configuration class.

Cause: The configuration factory could create, but could not initialize, a configuration class.

Action: Consult the application configuration log for further details.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00207: Failed to resolve the class {0}

Cause: The configuration factory could not find a named class definition to create.

Action: Consult the application configuration log for further details.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00208: Failed to initialize the configuration class.

Cause: The configuration factory could create, but could not initialize, a configuration class.

Action: Consult the application configuration log for further details.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00209: Configuration class application parameter "{0}" was not specified in web.xml

Cause: A required parameter for the configuration factory was not specified in the application configuration.

Action: Verify that the named parameter is present in the file web.xml, and that any customizations of this file did not remove it.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00210: The configuration Factory's configuration instance was null. There was an initialization error during application startup.

Cause: Due to previous errors, the configuration factory was not able to create a configuration instance.

Action: Consult the application configuration logs for previous errors.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00211: There was an error during configuration instance termination.

Cause: The configuration factory was unable to terminate a configuration instance.

Action: This error is not immediately fatal, but may result in a memory leak over time if repeated.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00212: The Configuration instance was not initialized. Ensure the context parameter "{0}" is set correctly, and check for errors during application startup.

Cause: The configuration factory could not initialize its configuration instance due to a missing parameter in web.xml.

Action: Verify that the named parameter is present in the file web.xml, and that any customizations of this file did not remove it.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00402: There was an error getting the context configuration parameter: {0}.

Cause: The application was unable to load the path to its context configuration from the configuration parameter BpmContextConfig.

Action: Verify that application configuration completed successfully, and that any customizations to this application did not remove this parameter.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00403: There was an error getting the common install version number.

Cause: The application was unable to determine the version number of the common installer.

Action: Verify that the file EPM_ORACLE_HOME/common/config/11.1.2.0/installer_version.xml exists, is accessible, and is a valid XML file.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00501: Failed to load and parse {0}

Cause: The configuration class failed to load the named file.

Action: Consult the application configuration log for further errors.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00502: Failed to initialize the authentication helper

Cause: The configuration class could not initialize the security system due to previous errors.

Action: Consult the application security log for previous errors.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00503: The property "{0}" has value "{1}"

Cause: Reports the named property and value.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00601: Loaded properties from {0}

Cause: Reports that the configuration class loaded its application properties from the named EPM Registry component.

Action: No action is requred.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00602: Failed to load properties from {0}

Cause: The configuration class could not load its configuration properties from the named EPM Registry component.

Action: Verify connection to the EPM Registry and EPM Registry contents.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00603: Loaded properties from {0}[{1}={2}]

Cause: Reports that the configuration class loaded its application properties from the named EPM Registry component.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00701: There was an error during authentication.

Cause: Reports a generic error during authentication. This message is a generic message for the user interface which obscured the actual security system error.

Action: Consult the application security log for the full error details.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00702: Intercepting request for authentication: {0}

Cause: The security system is intercepting the named request for an authentication check.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00703: Intercepting with static logon page: {0}

Cause: The security system is using the named logon page to prompt for user credentials.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00801: Redirecting request for authentication: {0}

Cause: The security system is redirecting the named request to the main application logon page.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00901: Logon bean class name was not specified in web.xml.

Cause: The name of a security class implementation was not found in the application configuration.

Action: This is not a fatal error; a default implementation will be used.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00902: Using the default logon bean implementation.

Cause: The security system will use a default security class implementation.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00903: There was an error instantiating the logon bean.

Cause: The security system was unable to instantiate the security class implementation.

Action: Consult the application security log for previous errors from the security API
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00904: The Logon bean class does not have a default public constructor.

Cause: The security class implementation does not have a required constructor.

Action: Verify that the application deployment is not damaged and that all service fixes were applied properly.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00905: Logon bean Java class is not resolvable.

Cause: The security system could not resolve the class name of the security class implementation.

Action: Verify that any customizations to web.xml did not remove or damage this parameter.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00906: Failed to initialize the logon bean.

Cause: The security system could not initialize the security class implementation.

Action: Consult the application security log for prior errors from the security API.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00907: There was an error during logon bean initialization.

Cause: The security system could not initialize the security class implementation.

Action: Consult the application security log for prior errors from the security API.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01001: Blocking request: {0}

Cause: The named request has been blocked by the security system.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01201: The CSS mode is: {0}

Cause: Reports the deployment mode of the security system.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01202: Failed to determine CSS mode. Will use EPM mode.

Cause: Indicates that the security system could not determine its deployment mode and is using the default mode.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01203: Initializing security framework

Cause: Indicates that the security class is initializing the security API/

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01204: Security framework was initialized successfully.

Cause: Indicates that the security class initialized the security API without error.

Action: No action was required.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01205: There was an error initializing security framework.

Cause: Indicates that the security class failed to initialize the security API.

Action: Consult the application security logs for prior error messages.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01207: This session will be invalidated.

Cause: Indicates that an already-extant session is being invalidated during logon to be replaced with a new session.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01208: Logging on user {0} at {1}

Cause: Records a successful user logon for the named user at the given time.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01210: There was an error determining if direct logon is permitted. Direct logons will be denied.

Cause: The security system was unable to determine if direct logons are permitted even if an SSO agent is enabled. Such logons will be disallowed.

Action: Verify that the application was deployed correctly and that any customization to its configuration did not remove any parameters.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01211: User's password is about to expire.

Cause: Informative message at logon indicating the the current user's password will soon expire.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01212: Failed to store user in session

Cause: The security system failed to create a session for an authenticated user.

Action: Consult the application security log for further details.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01213: Failed to retrieve user from session

Cause: The security system could not verify a user from an existing sesison.

Action: Consult the application security log for further details.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01214: Terminating session for user: {0}

Cause: Indicates that a user session is terminated.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01216: Session created at: {0}

Cause: Gives the creation time of a terminated user session.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01217: There was an error during Fusion logon:

Cause: Reports an error from the Fusion Middleware logon system.

Action: Consult the application security log for further details.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01301: Attempt to create a J2EE session on an unauthorized request path. The attempt was blocked. The request path was: {0}

Cause: An unauthorized request attempted to create an application session and was blocked in the attempt.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01501: read parameter name: {0} value: {1}

Cause: Indicates a preferences system configuration value read during startup.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01502: There was an error during preferences system initialization.

Cause: Reports an error during preferences initialization.

Action: Consult the application preferences log for further details.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01503: Preferences servlet initialized

Cause: Indicates that the preferences servlet is initialized.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01504: There was an error saving preferences.

Cause: Indicates an error saving preferences for a given user.

Action: Consult both the application security and applicaion preferences logs for more details.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01505: There was an error saving preferences for multiple users.

Cause: Indicates an error saving preferences for multiple users.

Action: Consult both the application security and applicaion preferences logs for more details.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01506: Ther was an error during preferences system shutdown.

Cause: Reports an error during preference system shutdown during application shutdown.

Action: The application has shut down, so no action is possible.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01801: There was an error checking the client debug setting: all requests blocked.

Cause: The security system was unable to determine if client debugging requests are permitted; these requests will be blocked by default.

Action: Verify that application configuration completed successfully, and that any customizations to this application did not remove this parameter.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01802: Permitting request: {0}

Cause: The security system is permitting the named client debugging request.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01803: Blocking request: {0}

Cause: The security system is blocking the named client debugging request.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01804: You do not have access to see this page because client debugging is disabled. Contact your system administrator.

Cause: This message indicates that the request was blocked because client debugging is enabled. A system administrator must enable this setting for the application.

Action: Contact your system administrator.
Level: 32

Type: ERROR

Impact:

36 EPMFR-00001 to EPMFR-00356

EPMFR-00001: Duplicate arc exists in the linkbase. From: ({0}) to: ({1})

Cause: Duplicate arc nodes were provided for a linkbase.

Action: Ensure that the taxonomy does not use duplicate arc nodes.
Level: 32

Type: ERROR

Impact:

EPMFR-00002: Error while trying to get content at URL: ({0}). Trying path: ({1}) instead.

Cause: The taxonomy's relative path was used instead of the URL location.

Action: Ensure that the taxonomy's URL location is properly formed.
Level: 32

Type: WARNING

Impact:

EPMFR-00003: URL: ({0}) missing

Cause: The URL for the taxonomy was not found.

Action: Ensure that the taxonomy exists at the given location. Also ensure that the given taxonomy's URL is properly formed.
Level: 32

Type: WARNING

Impact:

EPMFR-00004: {0} <element> attribute: {1} will not be processed. It is not recognized by the parser.

Cause: An unrecognized taxonomy element attribute was found by the taxonomy parser. It will be ignored.

Action: Ensure that the taxonomy being parsed does not use unrecognized element attributes.
Level: 32

Type: ERROR

Impact:

EPMFR-00005: {0} <schema> attribute: {1} will not be processed. It is not recognized by the parser.

Cause: An unrecognized schema attribute was found by the taxonomy parser. It will be ignored.

Action: Ensure that the taxonomy being parsed does not use unrecognized schema attributes.
Level: 32

Type: WARNING

Impact:

EPMFR-00006: Linkbase:{0} <linkbaseRef> attribute: {1} will not be processed. It is not recognized by the parser.

Cause: An unrecognized linkbase attribute was found by the taxonomy parser. It will be ignored.

Action: Ensure that the taxonomy being parsed does not use unrecognized linkbase attributes.
Level: 32

Type: WARNING

Impact:

EPMFR-00007: processImportAttributes:{0} <import> attribute: {1} will not be processed. It is not recognized by the parser.

Cause: An unrecognized import attribute was found by the taxonomy parser. It will be ignored.

Action: Ensure that the taxonomy being parsed does not use unrecognized import attributes.
Level: 32

Type: WARNING

Impact:

EPMFR-00008: {0} <include> attribute: {1} will not be processed. It is not recognized by the parser.

Cause: An unrecognized include attribute was found by the taxonomy parser. It will be ignored.

Action: Ensure that the taxonomy being parsed does not use unrecognized include attributes.
Level: 32

Type: WARNING

Impact:

EPMFR-00009: Error writing binary data to file: ({0})

Cause: Write permissions to file may be denied due to user permission settings or disk space limitations.

Action: Ensure that the user has write permissions to the file and there is enough disk space.
Level: 32

Type: ERROR

Impact:

EPMFR-00010: Error reading binary data from file: ({0})

Cause: File is missing or not accessible at this time.

Action: Verify that the file exists and is available, or try later.
Level: 32

Type: ERROR

Impact:

EPMFR-00011: Cannot load bursting file: {0}. Internal unique identifier of this file is: [{1}].

Cause: The file that was accessed does not exist.

Action: Select a file that exists and rerun.
Level: 32

Type: ERROR

Impact:

EPMFR-00012: Cannot load bursting file: {0}. Internal unique identifier of this file is: [{1}].

Cause: The file that was accessed does not exist.

Action: Select a file that exists and rerun.
Level: 32

Type: ERROR

Impact:

EPMFR-00013: GIF no longer supported

Cause: An unsupported Graphic Interchange Format (GIF) file was encountered as a report image.

Action: Convert the GIF file to a Bitmap (BMP) file and reload.
Level: 32

Type: WARNING

Impact:

EPMFR-00014: GIF no longer supported

Cause: An unsupported Graphic Interchange Format (GIF) file was encountered as a report image.

Action: Convert the GIF file to a Bitmap (BMP) file and reload.
Level: 32

Type: WARNING

Impact:

EPMFR-00015: GIF no longer supported

Cause: An unsupported Graphic Interchange Format (GIF) file was encountered as a report image.

Action: Convert the GIF file to a Bitmap (BMP) file and reload.
Level: 32

Type: WARNING

Impact:

EPMFR-00016: Batches run successfully will be cleaned up after {0} milliseconds.

Cause: The batches were run successfully and will be cleaned up.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00017: The thread which cleans up scheduled batches will wake up every {0} milliseconds.

Cause: The thread that cleaned the scheduled batches occurs every number of milliseconds.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00019: Cannot not find binary file: {0}

Cause: The reported file could not be found and may result in missing data, text, or images.

Action: Ensure that the selected .BES file is correct and corresponds to the loaded .DES file.
Level: 32

Type: ERROR

Impact:

EPMFR-00021: Attempted to cancel job, but could not find JobId: {0}

Cause: The selected job no longer exists.

Action: Check if the job already completed or was removed by another user.
Level: 32

Type: ERROR

Impact:

EPMFR-00022: Unable to open connection to data source. Failure result: {0}.

Cause: Either a connection to the data source was not established, or the user credentials for the data source were incorrect.

Action: Verify that the connectivity to the data source and verify that the user credentials for the data source are accurate.
Level: 32

Type: ERROR

Impact:

EPMFR-00023: Cannot find job definition {0}

Cause: The selected batch job was not found.

Action: Refresh the display and verify that the requested batch exists, then try again.
Level: 32

Type: WARNING

Impact:

EPMFR-00026: Key '{0}' already exists for {1}

Cause: The given extended link was not added to the element because it already exists.

Action: Ensure that the taxonomy does not attempt to add duplicate extended links to the same element.
Level: 32

Type: WARNING

Impact:

EPMFR-00027: Unable to load error message for key: {0}

Cause: The resource for the error message was not found.

Action: An error message or translated message is missing from the resource file. Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact:

EPMFR-00028: Unable to load error message for key: {0}

Cause: The resource for the error message was not found.

Action: An error message or translated message is missing from the resource file. Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact:

EPMFR-00029: Unable to load error message for key: {0}

Cause: The resource for the error message was not found.

Action: An error message or translated message is missing from the resource file. Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact:

EPMFR-00030: Unable to load error message for key: {0}

Cause: The resource for the error message was not found.

Action: An error message or translated message is missing from the resource file. Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact:

EPMFR-00031: Class '{0}' must extend from the ReportAddOn class

Cause: This is custom code in which the AddOn class did not extend the ReportAddOn class.

Action: The Java class in the Reports AddOn needs to extend the ReportAddOn class.
Level: 32

Type: ERROR

Impact:

EPMFR-00032: Error executing batch: {0}

Cause: The Reports Web Server was not available, the report to be run was not located, or there were no correct user credentials supplied for the batch routine.

Action: Verify the availability of the Reports Web Server, that the report in the batch exists, and that the user credentials for the batch routine are correct.
Level: 32

Type: ERROR

Impact:

EPMFR-00033: Type {0} of a service on {1} is shutting down.

Cause: A service on the noted server was shut down and removed from the registry.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00034: Type {0} of a service on {1} is started.

Cause: A service on the noted server was started and added to the registry.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00035: Initializing Financial Reporting Analytic Data Model Service

Cause: The Financial Reporting Analytic Data Model Service was about to initialize.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00036: Failure to initialize Financial Reporting Analytic Data Model Service

Cause: There was most likely an installation or configuration error that caused the initialization error.

Action: Check the installation and configuration logs for more information.
Level: 32

Type: ERROR

Impact:

EPMFR-00037: Stopping Financial Reporting Analytic Data Model Service

Cause: The Financial Reporting Analytic Data Model Service was stopping.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00038: Failure to stop Financial Reporting Analytic Data Model service

Cause: There most likely was a memory issue on the system.

Action: Check the system hardware for memory usage issues.
Level: 32

Type: ERROR

Impact:

EPMFR-00039: Initializing Financial Reporting Printing Service

Cause: The Financial Reporting Printing Service was initializing.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00040: Failure to start Financial Reporting Printing Service

Cause: The Financial Reporting Printing Service failed to initialize.

Action: Look at the installation and configuration logs for possible errors; check the system for memory errors, disk space, or other system related issues.
Level: 32

Type: ERROR

Impact:

EPMFR-00041: Stopping Financial Reporting Printing Service

Cause: The Financial Reporting Printing Service Service stopped.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00042: Failure to stop Financial Reporting Printing Service

Cause: The Financial Reporting Printing Service failed to stop.

Action: Check the logs for print jobs running. Also, check the system for memory errors or other system-related issues.
Level: 32

Type: ERROR

Impact:

EPMFR-00043: Initializing and starting Financial Reporting Reporting Service

Cause: The Financial Reporting Reporting Service initialized.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00044: Failure to start Financial Reporting Reporting Service

Cause: The Financial Reporting Reporting Service failed to initialize due to one of a few possible reasons.

Action: Look at the installation and configuration logs for possible errors; check the system for memory errors, disk space, or other system related issues.
Level: 32

Type: ERROR

Impact:

EPMFR-00045: Stopping Financial Reporting Reporting Service

Cause: The Financial Reporting Reporting Service has stopped.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00046: Failure to stop Financial Reporting Reporting Service

Cause: The Financial Reporting Reporting Service failed to stop.

Action: Check the logs for running reports, batch jobs, or any other running report process. Also, check the system for memory errors or other system-related issues.
Level: 32

Type: ERROR

Impact:

EPMFR-00047: Financial Reporting Scheduler Service initialized

Cause: The Financial Reporting Scheduler Service was initializing.

Action: No action is required
Level: 32

Type: INFORMATION

Impact:

EPMFR-00048: Failure to start Financial Reporting Scheduler Service

Cause: The Financial Reporting Scheduler Service failed to initialize.

Action: Look at the installation and configuration logs for possible errors; check the system for memory errors, disk space, or other system-related issues.
Level: 32

Type: ERROR

Impact:

EPMFR-00049: The Financial Reporting Scheduler Service stopped

Cause: The Financial Reporting Scheduler Service has stopping.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00050: Failure to stop Financial Reporting Scheduler Service

Cause: The Financial Reporting Scheduler Service failed to initialize.

Action: Check the logs for scheduled jobs that may have failed. Also, check the system for memory errors or other system-related issues.
Level: 32

Type: ERROR

Impact:

EPMFR-00051: Returning HsServer from machine {0}

Cause: The Reports server was successfully selected from the registry.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00052: Cannot get Report Server object

Cause: Failed to get the Report Server object from the registry. There may be an access or connectivity issue.

Action: Verify that the registry, RMI, and Reports Servers are all operational and that there are no network issues. Also verify all user credentials. Contact Oracle Support Services if this issue cannot be resolved.
Level: 32

Type: ERROR

Impact:

EPMFR-00053: Unable to find Print Server

Cause: Failed to get the print server object from the registry; possible access or connectivity issue.

Action: Verify that the registry, RMI, and Reports Servers are all operational and that there are no network issues. Also verify all user credentials. Contact Oracle Support Services if this issue cannot be resolved.
Level: 32

Type: ERROR

Impact:

EPMFR-00054: Cannot connect to server on {0}

Cause: Failure to connect to the specified server is most likely due to an RMI (Remote Method Invocation) issue.

Action: Verify that the RMI (Remote Method Invocation) service is running without errors. Also look for possible network issues. Contact Oracle Support Services if additional assistance is needed.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00055: Could not connect to server on {0}

Cause: Failed to connect to the specified server most likely due to an RMI issue.

Action: Verify the RMI (Remote Method Invocation) service is running without errors. Also look for possible network issues. Contact Oracle Support Services if additional assistance is needed.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00056: Cannot obtain report server list from server.

Cause: Failed to get a report server list because the Hyperion Registry is not accessible.

Action: Verify that the Hyperion Registry is running without errors. Also look for possible network issues. Contact Oracle Support Services if additional assistance is needed.
Level: 32

Type: ERROR

Impact:

EPMFR-00057: Cannot obtain print server list from server

Cause: Failed to get a print server list because the Hyperion Registry is not accessible.

Action: Verify that the Hyperion Registry is running without errors. Also look for possible network issues. Contact Oracle Support Services if additional assistance is needed.
Level: 32

Type: ERROR

Impact:

EPMFR-00058: Cannot obtain scheduler server from server

Cause: Failed to get a scheduler server list because the Hyperion Registry is not accessible.

Action: Verify that the Hyperion Registry is running without errors. Also look for possible network issues. Contact Oracle Support Services if additional assistance is needed.
Level: 32

Type: ERROR

Impact:

EPMFR-00059: Invalid login: ({0})

Cause: The login security credentials for a given data source were invalid.

Action: Provide data source credentials to view the portlet content.
Level: 32

Type: ERROR

Impact:

EPMFR-00060: Invalid report: ({0})

Cause: The specified Financial Reports report failed to be generated by the portlet.

Action: Ensure that the specified report exists or can be run using the Financial Reports Web preview.
Level: 32

Type: ERROR

Impact:

EPMFR-00061: Cannot retrieve Row & Column Template [{0}] into Grid '{1}'. The template may have been moved, renamed or deleted from the repository.

Cause: A reference to a Row and Column template was not found in the repository.

Action: Ensure that the template exists in the expected folder within the repository. It could have been renamed, moved, or deleted. But it needs to exist in the specified path.
Level: 32

Type: ERROR

Impact:

EPMFR-00062: Error adding incompatible Row & Column template [{0}] to Grid '{1}'. The template and/or grid may have been modified such that they are no longer compatible. The insert error code is {2}.

Cause: Dimensions on row or column have changed making the Row & Column template invalid for the grid.

Action: No action is required. The invalid Row & Column template was removed.
Level: 32

Type: ERROR

Impact:

EPMFR-00063: The maximum calculation limit of {0} has been reached. Further processing of this cell calculation will not occur

Cause: The report contained unevaluated cells due to reaching the maximum calculations limit.

Action: Update the MaximumCalculationIterations setting. Refer to the documentation for instructions.
Level: 32

Type: ERROR

Impact:

EPMFR-00064: Error while opening connection for user: {0} to the datas source: {1}:{2}

Cause: An error occurred when attempting to establish a connection with a selected data source.

Action: Ensure that the data source exists and is available. Also, verify user credentials to selected data source are accurate.
Level: 32

Type: ERROR

Impact:

EPMFR-00065: Financial Management server {0} is not responding

Cause: A connection could not be made to the Financial Management server. The Financial Management server is either offline or has been reconfigured.

Action: Verify the Financial Management connection information and ensure that the server or cluster is online.
Level: 32

Type: ERROR

Impact:

EPMFR-00066: Attempting to cancel Essbase report script for ID: {0}

Cause: User issued a cancel request for the essbase report script.

Action: No action is required. The Essbase report script will be canceled if possible.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00067: Canceling run for job with instanceId: {0}

Cause: The job with the associated ID was canceled.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00068: Invalid attempt to access controlled file: {0}

Cause: The file path was incorrect.

Action: Enter the correct file location and try again.
Level: 32

Type: ERROR

Impact:

EPMFR-00069: START: JobId: {0}; User: {1}; Name: {2}

Cause: The START time of the associated job with the given ID was marked.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00070: END: JobId: {0}

Cause: The END time of the associated job with the given ID was marked.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00071: Custom Socket Factories loaded successfully

Cause: The sockets connecting to the RMI server were successfully established.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00072: Unable to establish port within established range

Cause: The established range of ports selected to access the RMI server were unavailable.

Action: Either reestablish a different range with available ports, or, stop nonessential processes that are occupying the port range, and then retry.
Level: 32

Type: FATAL

Impact:

EPMFR-00073: User preferences or ReportServer object are not properly initialized. Unable to save User Preferences.

Cause: The connection to the server possibly was disrupted.

Action: Log out and try again.
Level: 32

Type: ERROR

Impact:

EPMFR-00074: User preferences or ReportServer object are not properly initialized. Unable to save User Preferences.

Cause: The connection to the server possibly was disrupted.

Action: Log out and try again.
Level: 32

Type: ERROR

Impact:

EPMFR-00075: Cannot connect to Related Content destination. status = {0}.

Cause: The Related Content destination was not available.

Action: Verify that the Related Content destination exists and that the calling object has it set correctly.
Level: 32

Type: ERROR

Impact:

EPMFR-00076: Substituting related content attributes. Reference String is: [{0}]

Cause: The related content attributes were substituted.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00077: Error exporting file: {0}

Cause: The file may have been deleted.

Action: Refresh the browser and try the operation again.
Level: 32

Type: ERROR

Impact:

EPMFR-00078: Error exporting file: {0}

Cause: The file may have been deleted.

Action: Refresh the browser and try the operation again.
Level: 32

Type: ERROR

Impact:

EPMFR-00079: Error getting folder: {0}

Cause: The folder may have been deleted.

Action: Refresh the browser and retry the operation.
Level: 32

Type: ERROR

Impact:

EPMFR-00080: Error retrieving report or snapshot: {0}

Cause: The book contains a report or snapshot that was not found.

Action: Ensure that the report or snapshot exists in the book.
Level: 32

Type: ERROR

Impact:

EPMFR-00081: Connected to server: {0}

Cause: A successful connection was made to the Report Server.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00082: Unable to stop job {0}

Cause: The selected data source was not responding to the cancel request.

Action: Verify that the selected data source is accessible and operating. Check the logs of the data source for any other issues.
Level: 32

Type: ERROR

Impact:

EPMFR-00083: Unable to delete job: {0}

Cause: The Report Server could not be accessed.

Action: Verify that the Report Server is running and verify that the user has permissions to delete the scheduled job.
Level: 32

Type: ERROR

Impact:

EPMFR-00084: Error executing member selection: [{0}]

Cause: Either the member selection was not valid or the data source connection failed.

Action: Check connection to the data source.
Level: 32

Type: ERROR

Impact:

EPMFR-00085: Error executing member selection: [{0}]

Cause: Either the member selection was not valid or the data source connection failed.

Action: Check the connection to the data source.
Level: 32

Type: ERROR

Impact:

EPMFR-00086: HFM (Hyperion Financial Management) indicates that either data or metada has changed.

Cause: HFM (Hyperion Financial Management) indicates that either data or metada had changed.

Action: The current connection needs to be discarded and a new connection acquired, then rerun the book or report.
Level: 32

Type: WARNING

Impact:

EPMFR-00087: Error in setting up the 'Org By Period Filter'

Cause: Either the member selection was not valid or the data source connection failed.

Action: Check connection to the data source.
Level: 32

Type: ERROR

Impact:

EPMFR-00088: External authentication successful for user: [{0}] succeeded in {1} ms.

Cause: The user logon was successful in the associated time in milliseconds.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00089: user [{0}] has no access to Financial Reporting.

Cause: A user without any Financial Reporting roles tried to access Financial Reporting.

Action: Review the user's credentials for security purposes.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00090: Failure to initialize ADM

Cause: The Financial Reporting Server did not initialize the ADM component for data source communication.

Action: A configuration issue is the likely cause, so verify that the ADM is specified within the classpath or path.
Level: 32

Type: ERROR

Impact:

EPMFR-00091: Starting Report Server and modules

Cause: The Report Server and associated modules were started.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00092: Error starting Report Server

Cause: The report server did not start.

Action: Check a variety of possible failures including: Port conflicts or other configuration issues, system hostname incorrectly configured, and that the RMI registry is available.
Level: 32

Type: ERROR

Impact:

EPMFR-00093: Successful start for Financial Reporting Authentication, Repository and Reports modules.

Cause: The Financial Reporting Authentication, Repository and Reports modules started successfully.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00094: Error during datasource connection cleanup

Cause: Another request to close the datasource connections may have been issued previous to the current request.

Action: Check the list of active sessions and retry, closing any existing sessions.
Level: 32

Type: ERROR

Impact:

EPMFR-00095: Invalid command line parameters

Cause: The number of command line parameters was incorrect.

Action: Ensure that the correct number of parameters are entered when starting from the command line.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00096: Error while writing the binary data of the report object to file: ({0})

Cause: An error occurred while writing the binary data of the report object to the specified file.

Action: Verify that the user has permission to write to the file and ensure that there is enough disk space.
Level: 32

Type: ERROR

Impact:

EPMFR-00097: Removing annotation on existing snapshot as duplicate annotation is generated: {0}

Cause: The annotation on the existing snapshot was a duplicate and was removed.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00098: Retrieving annotations from repository: {0}

Cause: Annotations were retrieved from the repository

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00099: In method Instance.createDuplicateAnnotationsForSnapshot() annotation count: {0}

Cause: In method Instance.createDuplicateAnnotationsForSnapshot() annotation count: {0}

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00100: Creation of duplicate annotations for snapshot successful: {0}

Cause: Duplicate annotations for snapshot were completed: {0}

Action: No Action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00101: Not expecting Context Value; Finding: {0}; Expected: {1}

Cause: An invalid Context Value was received and might not exist in the repository.

Action: Verify that the instance exists in the repository.
Level: 32

Type: ERROR

Impact:

EPMFR-00102: Error in sending e-mail: {0}

Cause: An error occurred while sending an e-mail and can be caused by network issues or invalid information.

Action: Verify the e-mail address and check if mail server is available.
Level: 32

Type: ERROR

Impact:

EPMFR-00103: Error while getting dimension: {0}

Cause: The datasource connection was either lost or not established. Otherwise an internal error in the data source occurred.

Action: Verify that the data source is running and accessible, and then retry. Otherwise, check the data source logs for any data access issues.
Level: 32

Type: ERROR

Impact:

EPMFR-00104: Error while getting dimension: {0}

Cause: The datasource connection was either lost or not established. Otherwise an internal error in the data source occurred.

Action: Verify that the data source is running and accessible, and then retry. Otherwise check the datasource logs for any data access issues.
Level: 32

Type: ERROR

Impact:

EPMFR-00105: Error while getting member selections

Cause: The datasource connection was either lost or not established. Otherwise an internal error in the data source occurred.

Action: Verify that the data source is running and accesible, and then retry. Otherwise check the datasource logs for any data access issues.
Level: 32

Type: ERROR

Impact:

EPMFR-00106: Failure in exporting user session for use in static HTML generation

Cause: Access to the Report Server connection might have been lost.

Action: Verify the Remote Method Invocation (RMI) service is operational and the same with the Report Server. Ensure that all communication routes between the services are also available. Contact Oracle Support Services if all services and comunication routes are operational.
Level: 32

Type: ERROR

Impact:

EPMFR-00107: Error while storing PDF with the instance: {0}

Cause: The PDF file was not stored, likely due to: The central repository was not available or access was revoked, an invalid file name was specified, or the print server was not available.

Action: Verify that the central repository is accessible and that everything is configured with the correct credentials. Also, ensure that the print server is available and that the file name to be saved has a valid file name.
Level: 32

Type: ERROR

Impact:

EPMFR-00108: Error while storing PDF with the instance: {0}

Cause: The PDF file was not stored, likely due to: The central repository was not available or access was revoked, an invalid file name was specified, or the print server was not available.

Action: Verify that the central repository is accessible and that everything is configured with the correct credentials. Also, ensure that the print server is available and that the file name to be saved has a valid file name.
Level: 32

Type: ERROR

Impact:

EPMFR-00109: Error while storing PDF with the instance: {0}

Cause: The PDF file was not stored, likely due to: The central repository was not available or access was revoked, an invalid file name was specified, or the print server was not available.

Action: Verify that the central repository is accessible and that everything is configured with the correct credentials. Also, ensure that the print server is available and that the file name to be saved has a valid file name.
Level: 32

Type: ERROR

Impact:

EPMFR-00110: Error while storing PDF with the instance: {0}

Cause: The PDF file was not stored, likely due to: The central repository was not available or access was revoked, an invalid file name was specified, or the print server was not available.

Action: Verify that the central repository is accessible and that everything is configured with the correct credentials. Also, ensure that the print server is available and that the file name to be saved has a valid file name.
Level: 32

Type: ERROR

Impact:

EPMFR-00111: Error while storing PDF with the instance: {0}

Cause: The PDF file was not stored, likely due to: The central repository was not available or access was revoked, an invalid file name was specified, or the print server was not available.

Action: Verify that the central repository is accessible and that everything is configured with the correct credentials. Also, ensure that the print server is available and that the file name to be saved has a valid file name.
Level: 32

Type: ERROR

Impact:

EPMFR-00112: Error while storing PDF with the instance: {0}

Cause: The PDF file was not stored, likely due to: The central repository was not available or access was revoked, an invalid file name was specified, or the print server was not available.

Action: Verify that the central repository is accessible and that everything is configured with the correct credentials. Also, ensure that the print server is available and that the file name to be saved has a valid file name.
Level: 32

Type: ERROR

Impact:

EPMFR-00113: Cannot find the static book template root directory

Cause: The static book template root directory within the scheduler properties was not found.

Action: Check if there are any product configuration issues within the config logs. Check if the SchedulerTemplate is defined in fr_scheduler.properties.
Level: 32

Type: ERROR

Impact:

EPMFR-00114: Error creating zip file. File does not exist: {0}.

Cause: The specified file and path did not exist.

Action: Verify that the file and path specified exist.
Level: 32

Type: WARNING

Impact:

EPMFR-00115: Data source names to validate: {0}

Cause: A status message lists the data sources that were validated.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00116: Data source names to validate: {0}

Cause: A status message that lists the data sources that were validated.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00117: Connecting to Report Server: {0}

Cause: The Report Server was connected for validation.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00118: Users to validate: {0}

Cause: Users were validated.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00119: Users to validate: {0}

Cause: User were validated.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00120: Finding {0} match(es).

Cause: A status message was provided with the data source information from the user's point of view.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00121: This action will delete {0} POVs

Cause: A status message was provided that stated the number of POVs that were deleted.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00122: Not finding POVs

Cause: A status message was provided that stated that no POVs were found.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00123: User POV import LoginID = {0}

Cause: A status message was provided that listed the user ID while importing a user POV.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00124: Not finding user: {0}

Cause: There was an unforseen condition where user information could not be extracted from security.

Action: Generally this error should not happen. An extreme condition where this may occur is if security were to intermittently fail. Check the foundation services and the network for possible issues. Contact Oracle Support Services if unable to be resolved.
Level: 32

Type: WARNING

Impact:

EPMFR-00125: Member missing: {0}

Cause: The member name was not found within the data source because it either did not exist or could not be seen by the current user. It will not be imported.

Action: By default, the member name is skipped. However, if the member name is needed, then it must be made available either by adjusting the datasource security access for the user, or by entering the member name into the data source.
Level: 32

Type: WARNING

Impact:

EPMFR-00126: No DATASOURCE_NAME in XML file

Cause: The XML file being imported for user POV information was missing a datasource name.

Action: Supply a valid datasource name in the XML file.
Level: 32

Type: ERROR

Impact:

EPMFR-00127: Error loading config file: {0}

Cause: The specified config file did not exist or was not accessible.

Action: Supply a valid and accessible file name as a parameter.
Level: 32

Type: ERROR

Impact:

EPMFR-00128: Missing AdminUser

Cause: The configuration file did not have an administrative user (AdminUser) specified.

Action: In the configuration file, specify a user (AdminUser) with Administrator access.
Level: 32

Type: ERROR

Impact:

EPMFR-00129: No AdminPassword

Cause: The configuration file did not have an administrator password (AdminPassword) specified.

Action: In the configuration file, specify an administrator password (AdminPassword) for the user.
Level: 32

Type: ERROR

Impact:

EPMFR-00130: No ImportFileName

Cause: The configuration file did not have a user POV import file name (ImportFileName).

Action: Specify a valid import file name (ImportFileName) when running in import mode.
Level: 32

Type: ERROR

Impact:

EPMFR-00131: ImportFileName missing: {0}

Cause: The specified user POV import file name (ImportFileName) was invalid.

Action: Specify a valid import file name (ImportFileName)when running in import mode.
Level: 32

Type: ERROR

Impact:

EPMFR-00132: Error while reading the ImportFile

Cause: An error occurred while reading the import file. This could be caused by a file access issue or any other error while processing the import file.

Action: Verify that the file is still accessible and readable to the user. Look for other issues within both the Report Server and connecting data sources for other possible causes. Contact Oracle Support Services for additional assistance.
Level: 32

Type: ERROR

Impact:

EPMFR-00133: Error while reading the ImportFile

Cause: An error occurred while reading the import file. This could be caused by a file access issue or any other error while processing the import file.

Action: Verify that the file is still accessible and readable to the user. Look for other issues within both the Report Server and connecting data sources for other possible causes. Contact Oracle Support Services for additional assistance.
Level: 32

Type: ERROR

Impact:

EPMFR-00134: No ExportFileName

Cause: The user POV export file name (ExportFileName) was not specified.

Action: Specify a valid user POV export file name (ExportFileName).
Level: 32

Type: ERROR

Impact:

EPMFR-00135: No ReportServer

Cause: A valid and working Report Server (ReportServer) was not specified.

Action: Specify a valid and working Report Server (ReportServer).
Level: 32

Type: ERROR

Impact:

EPMFR-00136: Starting Hyperion Financial Reporting ManageUserPOV Utility at: {0}

Cause: A status message indicating the ManageUserPOV utility has started and accompanied by a time stamp to monitor the time lapse.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00137: Ending Hyperion Financial Reporting ManageUserPOV Utility at: {0}

Cause: The ManageUserPOV utility was ended and accompanied by a time stamp to mark the end of the time lapse.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00138: Usage: ManageUserPov Mode ConfigFile\tMode = import | export | delete\tConfigFile = configuration file name such as ManageUserPov.properties

Cause: An instruction about how to use the ManageUserPov utility was provided.

Action: Follow the instructions of the message.
Level: 32

Type: ERROR

Impact:

EPMFR-00139: Data source does not exist: {0}, A new one will be created.

Cause: The data source was not previously configured but the utility attempted to create a connection with the specified data source automatically.

Action: No action is required unless a new data source cannot be created automatically.
Level: 32

Type: WARNING

Impact:

EPMFR-00140: Creating data source: {0}

Cause: The data source was created successfully.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00141: Exception: {0} in loading locale strings for locale: {1}

Cause: The file that contains the translated messages either was not found or the file contained errors.

Action: Look at the installation and configuration logs for possible errors. Contact Oracle Support Services for additional assistance.
Level: 32

Type: ERROR

Impact:

EPMFR-00142: Error while storing PDF

Cause: The PDF file was not stored properly, likely due to: The central repository was not available or access was revoked, an invalid file name was specified, The print server was not available.

Action: Verify that the central repository is accessible and that everything is configured with the correct credentials. Also, ensure that the print server is available and that the file name to be saved has a valid file name.
Level: 32

Type: ERROR

Impact:

EPMFR-00143: Error while storing PDF

Cause: The PDF file was not stored properly, likely due to: The central repository was not available or access was revoked, An invalid file name was specified, The print server was not available.

Action: Verify that the central repository is accessible and that everything is configured with the correct credentials. Also, ensure that the print server is available and that the file name to be saved has a valid file name.
Level: 32

Type: ERROR

Impact:

EPMFR-00144: Error while storing PDF

Cause: The PDF file was not stored properly, likely due to: The central repository was not available or access was revoked, An invalid file name was specified, The print server was not available.

Action: Verify that the central repository is accessible and that everything is configured with the correct credentials. Also, ensure that the print server is available and that the file name to be saved has a valid file name.
Level: 32

Type: ERROR

Impact:

EPMFR-00145: Error while storing PDF

Cause: The PDF file was not stored properly, likely due to: The central repository was not available or access was revoked, An invalid file name was specified, The print server was not available.

Action: Verify that the central repository is accessible and that everything is configured with the correct credentials. Also, ensure that the print server is available and that the file name to be saved has a valid file name.
Level: 32

Type: ERROR

Impact:

EPMFR-00146: Error storing PDF

Cause: The PDF file was not stored properly, likely due to: The central repository was not available or access was revoked, An invalid file name was specified, The print server was not available.

Action: Verify that the central repository is accessible and that everything is configured with the correct credentials. Also, ensure that the print server is available and that the file name to be saved has a valid file name.
Level: 32

Type: ERROR

Impact:

EPMFR-00147: Error storing PDF.

Cause: The PDF file was was not stord properly, likely due to: The central repository was not available or access was revoked, An invalid file name was specified, The print server was not available.

Action: Verify that the central repository is accessible and that everything is configured with the correct credentials. Also, ensure that the print server is available and that the file name to be saved has a valid file name.
Level: 32

Type: ERROR

Impact:

EPMFR-00148: Start of print server job

Cause: print server job, like printing of report or book, was started.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00149: Completed printing of book or report

Cause: The book or report printing was completed.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00150: Cannot get page number count for instance '{0}'. Continuous page numbers may not be correct.

Cause: There was no page count for instance '{0}'. Continuous page numbers may be applied incorrectly.

Action: Verify that the print server is installed correctly.
Level: 32

Type: ERROR

Impact:

EPMFR-00152: Cannot find BookTOCPrintTemplate {0} entry in properties file. Cannot generate Book TOC.

Cause: The specified BookTOCPrintTemplate entry was not found in the properties file. The Book TOC was not generated.

Action: Verify that the print server is installed correctly.
Level: 32

Type: ERROR

Impact:

EPMFR-00153: Cannot print report '{0}' within Book '{1}'

Cause: The specified report was not printed within the specified book.

Action: Ensure that all external object links in the book are correct, that the book is valid, and that the report exists in the repository.
Level: 32

Type: ERROR

Impact:

EPMFR-00157: Cannot obtain page count from file '{0}'. The file type is not supported for printing.

Cause: The page count was not obtained from the specified file. The file type is not supported for printing.

Action: Verify that all the external links are satisfied and the instance runs correctly in HTML.
Level: 32

Type: ERROR

Impact:

EPMFR-00160: Cannot retrieve the document file: '{0}'

Cause: The specified document file was not retrieved.

Action: Verify that the PDF output location is correct in the property file.
Level: 32

Type: ERROR

Impact:

EPMFR-00161: Error generating print for report instance '{0}'. Return code: {1}

Cause: There was an error when trying to generate a printing of the specified report instance.

Action: Verify that the instance runs correctly in HTML and if it has attachments, that the links are valid.
Level: 32

Type: ERROR

Impact:

EPMFR-00162: Start of run for {0} job {1}

Cause: The specified print job was started.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00163: End of run for {0} end

Cause: The specified print job ended.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00164: Cannot print using printer '{0}'. The printer is either not available to the Print Server or not configured for the host computer's services.

Cause: The specified printer was not used because either it was not available to the print server, or it was not configured for the host computer's services.

Action: Ensure that the print server is installed correctly.
Level: 32

Type: ERROR

Impact:

EPMFR-00165: Error when printing an instance

Cause: There was an error generated when the instance was printing.

Action: Verify that the instance runs correctly in HTML and if it has attachments, that the links are valid.
Level: 32

Type: ERROR

Impact:

EPMFR-00166: No page count for the table of contents in book '{0}'

Cause: The page count for the table of contents in the specified book was not obtained.

Action: Verify that all external object links in the book are correct and that the book is valid.
Level: 32

Type: ERROR

Impact:

EPMFR-00167: No table of contents in book '{0}'

Cause: The table of contents in the book was not produced.

Action: Verify that all external object links in the book are correct and that the book is valid.
Level: 32

Type: ERROR

Impact:

EPMFR-00168: Cannot merge PDF file '{0}'. The file does not exist.

Cause: The specified PDF file was not merged because the file did not exist.

Action: Verify that the print server is installed correctly and Ghostscript is there.
Level: 32

Type: ERROR

Impact:

EPMFR-00169: Error in merging PDF file ({0})

Cause: The attempt to merge the specified PDF file generated an error.

Action: Verify that the print server is installed correctly and that Ghostscript is there.
Level: 32

Type: ERROR

Impact:

EPMFR-00170: Cannot get page number count for instance '{0}'. Continuous page numbers may not be correct.

Cause: There was no page count or continues page numbers because the print server might be installed incorrectly.

Action: Verify that all external object links in the book are correct and that the book is valid.
Level: 32

Type: ERROR

Impact:

EPMFR-00171: Cannot print instance: '{0}'. The PostScript file for the instance does not exist.

Cause: The specified instance was not printed. The PostScript file for the instance did not exist.

Action: Ensure that Ghostscript is installed.
Level: 32

Type: ERROR

Impact:

EPMFR-00172: Cannot print instance: '{0}'. The PostScript file for the instance does not exist.

Cause: The specified instance was not printed. The PostScript file for the instance did not exist.

Action: Ensure that Ghostscript is installed.
Level: 32

Type: ERROR

Impact:

EPMFR-00173: Error generating the bookmark outline for '{0}'

Cause: The bookmark outline for the specified PDF file generated an error.

Action: Ensure that the iText version is correct.
Level: 32

Type: ERROR

Impact:

EPMFR-00174: Error generating the book table of contents for '{0}'

Cause: The book table of contents for the specified PDF file generated an error.

Action: Verify that the iText version is correct.
Level: 32

Type: ERROR

Impact:

EPMFR-00175: Cannot print document file: '{0}' \tError code: {1}, Last Error: {2}

Cause: The specified document file was not printed.

Action: Verify that the external document link is correct.
Level: 32

Type: ERROR

Impact:

EPMFR-00176: Cannot print document file: '{0}' \tError code: {1}, Last Error: {2}

Cause: The specified document file was not printed.

Action: Verify that the external document link is correct.
Level: 32

Type: ERROR

Impact:

EPMFR-00177: Cannot obtain page count from file '{0}'. The file type is not supported for printing.

Cause: The page count was not obtained from the specified file. The file type is not supported for printing.

Action: Ensure that the file type is supported by print server.
Level: 32

Type: ERROR

Impact:

EPMFR-00178: Error writing external file '{0}'. It will not be included in the PDF output.

Cause: There was an error when writing the specified external file.

Action: Verify that the PDF output location is correct in the property file.
Level: 32

Type: ERROR

Impact:

EPMFR-00179: Error reading external PDF file '{0}'. It will not be included in the PDF output.

Cause: There was an error when reading the specified external PDF file.

Action: Verify that iText has the correct version.
Level: 32

Type: ERROR

Impact:

EPMFR-00180: Cannot retrieve the document file: '{0}' The returned error code is: {1}, Last error: {2}

Cause: The specified document files was not retrieved.

Action: Verify that the external object's link is correct.
Level: 32

Type: ERROR

Impact:

EPMFR-00181: Cannot produce the PDF output for the external document '{0}'

Cause: The specified external document file did not produce PDF output.

Action: Verify that external link in the print object is correct.
Level: 32

Type: ERROR

Impact:

EPMFR-00182: Cannot produce the PDF output for the book or instance '{0}'. The returned error code is: {1}, Last error: {2}

Cause: The specified book or instance did not produce PDF output.

Action: Ensure that the HRDocumentPrinting.dll file is installed correctly.
Level: 32

Type: ERROR

Impact:

EPMFR-00183: Cannot print instance or book: '{0}'. The print file is not produced.

Cause: The specified instance or book was not printed. The print file was not produced.

Action: Verify that Ghostscript is installed correctly.
Level: 32

Type: ERROR

Impact:

EPMFR-00184: Cannot send output to system printer. No printer specification.

Cause: Because no printer was specified, the output was not sent to the system printer.

Action: Verify that the physical printer is correct.
Level: 32

Type: ERROR

Impact:

EPMFR-00185: Cannot send instance output to system printer ('{0}'). No instance retrieval.

Cause: The instance was not retrieved because the instance output was not sent to the system printer.

Action: Ensure that the server which has the repository is up and the object is running.
Level: 32

Type: ERROR

Impact:

EPMFR-00186: Cannot send book output to system printer ('{0}'). No book retrieval.

Cause: The book was not retrieved because the book output was not sent to the system printed.

Action: Ensure that the server which has the repository is up and the book is running.
Level: 32

Type: ERROR

Impact:

EPMFR-00187: Invalid object type '{0}'. Cannot send output to system printer('{1}')

Cause: Due to an invalid file type, the output was not sent to the specified system printer.

Action: Verify that the file type is supported by the print server.
Level: 32

Type: ERROR

Impact:

EPMFR-00188: Successful printing '{0}' on system printer '{1}'

Cause: The specified document was successfully printed on the specified system printer.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00189: FRExecute has invalid cell reference '{0}'

Cause: FRExecute referenced an invalid cell.

Action: Verify that the FRExecute function's parameters are valid.
Level: 32

Type: ERROR

Impact:

EPMFR-00190: FRExecute cannot generate an image for component '{0}'

Cause: FRExecute could not generate an image for the specified component.

Action: Verify that the FRExecute function's parameters are valid.
Level: 32

Type: ERROR

Impact:

EPMFR-00191: Cannot replace FRExecute function with the result.

Cause: The FRExecute function could not be replaced with the result.

Action: Verify that Microsoft Word is installed on the machine where the print server is located.
Level: 32

Type: ERROR

Impact:

EPMFR-00192: Cannot load Ghostscript or Distiller.

Cause: Ghostscript or Distiller could not be loaded.

Action: Ensure that a supported version of Ghostscript or Distiller is properly installed on the print server.
Level: 32

Type: ERROR

Impact:

EPMFR-00193: Error by Ghostscript in converting to PostScript.

Cause: A supported vesion of Ghostscipt may not be installed on the print server.

Action: Ensure that a supported version of Ghostscript is installed on the print server. If the problem persists, please contact Oracle Support Services.
Level: 32

Type: ERROR

Impact:

EPMFR-00194: PDF root directory is {0}

Cause: The cited directory name was the root directory of the PDF file.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00195: The report: [{0}] not cancelling

Cause: The specified report failed to cancel.

Action: Verify that the Print Server or Network is not down.
Level: 32

Type: ERROR

Impact:

EPMFR-00196: Printer {0} not accessible on print server: {1}

Cause: Printer {{0}} was not accessible on print server: {1}.

Action: Verify that the print server is running and that the printer is available.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00198: ERROR: duplicate member in a prompt. Duplicate member will be removed.

Cause: A duplicate member was found during member selection from the data source.

Action: No action is required. A duplicate member was removed from the member selection display.
Level: 32

Type: ERROR

Impact:

EPMFR-00199: Over 50 dimensions in the data source. Removing the following dimensions which are set to the default member:

Cause: An SAP data source with more then 50 dimensions was found. The SAP BAPI driver does not support accessing a data source with more then 50 dimensions.

Action: Reduce the number of dimensions in the data source or use a different data source.
Level: 32

Type: ERROR

Impact:

EPMFR-00200: Error while setting POV:

Cause: There was probably a connection error with the data source while setting the POV.

Action: Verify that the selected data source is available, access credentials are correct, or review the logs from the data source for other possible issues.
Level: 32

Type: WARNING

Impact:

EPMFR-00201: Exception while getting dimension {0}

Cause: There were datasource access issues or an internal error in the data source.

Action: Verify that the selected data source is available, access credentials are correct, or review the logs from the data source for other possible issues.
Level: 32

Type: ERROR

Impact:

EPMFR-00202: Exception while getting dimension {0}

Cause: There were datasource access issues or an internal error in the data source.

Action: Verify that the selected data source is available, access credentials are correct, or review the logs from the data source for other possible issues.
Level: 32

Type: ERROR

Impact:

EPMFR-00203: Using Enterprise Scheduling Services for scheduling

Cause: The Enterprise Scheduling Service was used.

Action: No is action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00205: Scheduler not ready to publish itself. Retry in {0} minutes.

Cause: No Report servers were running.

Action: Ensure that the Report Server is running. Retry in the specified minutes.
Level: 32

Type: WARNING

Impact:

EPMFR-00206: Successful start of Scheduler Server

Cause: The Scheduler Server was started successfully.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00207: Scheduler cannot contact any Report Server. Exiting.

Cause: The Scheduler did not start because it did not contact any Report Server.

Action: Check on the availablilty of configured Reports Servers.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00208: Cannot start scheduler service:

Cause: An unexpected error occurred while the Scheduler Service was binding to the Report Server.

Action: Contact Oracle Support Services for assistance.
Level: 32

Type: ERROR

Impact:

EPMFR-00210: Scheduler Server stopped

Cause: The Scheduler Server was stopped.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00213: Batch Job file: {0} not found. Error reported:

Cause: The specified scheduled batch job file was not found. The file may have been deleted or moved to another location.

Action: Verify that the specified file exists in the expected location and rerun the job.
Level: 32

Type: ERROR

Impact:

EPMFR-00215: Schema '{0}' missing. Attempting to create a new one.

Cause: The given schema was not previously loaded. An attempt to load it occurred.

Action: Ensure that the given schema is valid and can be loaded. Look for additional warnings.
Level: 32

Type: WARNING

Impact:

EPMFR-00216: Error while parsing a new schema:{0}

Cause: The given error was produced while attempting to parse a schema.

Action: Ensure that the schema is valid and complies with the XBRL 2.1 specification.
Level: 32

Type: ERROR

Impact:

EPMFR-00217: Schema: '{0}' missing. Cannot delete it.

Cause: The given schema was not found.

Action: Ensure that the given schema exists and can be removed from the file system.
Level: 32

Type: WARNING

Impact:

EPMFR-00218: Schema: '{0}' missing. Cannot delete it.

Cause: The given schema was not found.

Action: Ensure that the given schema exists and can be removed from the file system.
Level: 32

Type: WARNING

Impact:

EPMFR-00219: Error during the auto-update of Schemas:{0}

Cause: The error occurred while attempting to auto-update the schemas in the file system.

Action: Ensure that the schema exists, is valid and complies to the XBRL 2.1 specification.
Level: 32

Type: ERROR

Impact:

EPMFR-00220: Error attempting to create a row and column template

Cause: An unexpected error occurred while attempting to add a row and column template into a grid.

Action: Review the Report Server log file for details on the error.
Level: 32

Type: ERROR

Impact:

EPMFR-00221: Error attempting to add a row or column from a template.

Cause: An unexpected error occurred while attempting to add a row or column from a template into a grid.

Action: Review the Report Server log file for details on the error.
Level: 32

Type: ERROR

Impact:

EPMFR-00233: Error while getting content at: ({0}). Trying ({1}/{2}) instead.

Cause: The path for the taxonomy was not found.

Action: Ensure that the taxonomy exists for the given path.
Level: 32

Type: WARNING

Impact:

EPMFR-00234: Unknown linkbase role: {0} found. Linkbase will not be included.

Cause: The given linkbase could not be added as a reference from a taxonomy.

Action: Ensure that the given linkbase is valid and can be added as a reference to a taxonomy.
Level: 32

Type: ERROR

Impact:

EPMFR-00235: The presentation linkbase '{0}' is empty. A flat taxonomy tree may display.

Cause: The taxonomy's presentation linkbase was empty, which typically causes a flat taxonomy tree to be rendered.

Action: Provide a presentation linkbase for the given taxonomy.
Level: 32

Type: WARNING

Impact:

EPMFR-00236: TaxonomyElement: {0} not found.

Cause: The presentation linkbase had a reference to a taxonomy element that could not be found.

Action: Ensure that the presentation linkbase has references to valid taxonomy elements.
Level: 32

Type: WARNING

Impact:

EPMFR-00237: Taxonomy Element Node: {0} not found

Cause: A taxonomy element node could not be obtained referenced by the given element ID.

Action: Ensure that the taxonomy element exists with the taxonomy.
Level: 32

Type: WARNING

Impact:

EPMFR-00238: Taxonomy element '{0}' already exists.

Cause: The given taxonomy element had already been processed. The taxonomy seemed to have a duplicate element declaration.

Action: Ensure that the taxonomy does not contain duplicate taxonomy element declarations.
Level: 32

Type: WARNING

Impact:

EPMFR-00239: The taxonomy element {0} was not mapped, as it is an abstract type.

Cause: The given element could not exist within an instance document. Typically, this is because an abstract element was mapped.

Action: Ensure that only mappable taxonomy elements are mapped within a report. Do not map abstract elements.
Level: 32

Type: WARNING

Impact:

EPMFR-00240: Element specified in the locator: {0} {1} not found

Cause: The given taxonomy element could not be found from the given locator.

Action: Ensure that the taxonomy's locators have valid references to taxonomy elements.
Level: 32

Type: WARNING

Impact:

EPMFR-00241: Element specified in the locator: {0} {1} not found

Cause: The given taxonomy element could not be located from the given locator.

Action: Ensure that the taxonomy's locators have valid references to taxonomy elements.
Level: 32

Type: WARNING

Impact:

EPMFR-00242: Error in TextCell {0} Col {1} Row {2} Formula: '{3}'\t Error: {4}

Cause: There was a syntax error in the function.

Action: Fix the syntax error that is described in the error message.
Level: 32

Type: ERROR

Impact:

EPMFR-00243: Error in TextObject Formula: '{0}'\t Error: {1}

Cause: There was a syntax error in the function.

Action: Fix the syntax error that is described in the error message.
Level: 32

Type: ERROR

Impact:

EPMFR-00244: Report Server Initializing

Cause: The Report Server initialized.

Action: No action is required
Level: 32

Type: INFORMATION

Impact:

EPMFR-00245: Report Server started

Cause: The Report Server initialized and started successfully.

Action: No action is required
Level: 32

Type: INFORMATION

Impact:

EPMFR-00246: Error while starting the Report Server

Cause: The Report Server failed to initialize.

Action: Check a variety of possible failures including: Port conflicts or other configuration issues, incorrect system hostname configuration, and availability of the Remote Method Invocation (RM0).
Level: 32

Type: ERROR

Impact:

EPMFR-00247: Hyperion Financial Management reports that either Metadata or Data has changed. Discarding the current connection and reconnecting.

Cause: Possible metadata or data load was performed on the Hyperion Finacial Management (HFM) server.

Action: Rerun the book or report.
Level: 32

Type: WARNING

Impact:

EPMFR-00248: Book contains reports not found: {0}

Cause: The book contained reports which could not be found.

Action: Ensure that the contained report(s) exists.
Level: 32

Type: ERROR

Impact:

EPMFR-00249: Cannot find data source ID: {0} {1}. Attempting to find data source with same name.

Cause: A connection to the data source could not be made by using the stored data source ID.

Action: Verify that the data source is started or restored, and the credentials are correct.
Level: 32

Type: WARNING

Impact:

EPMFR-00250: Could not find data source ID: {0} {1}. Creating a new data source.

Cause: A connection to the data source could not be made by using the stored data source name.

Action: Verify that data source is started or restored, and the credentials are correct.
Level: 32

Type: WARNING

Impact:

EPMFR-00251: Cannot not find data source ID: {0} {1}. Failed to create a new data source for it.

Cause: A connection to the data source could not be made by using the stored data source ID or name, and failed to create a new data source automatically for it.

Action: Verify that the data source is started or restored, and the credentials are correct.
Level: 32

Type: ERROR

Impact:

EPMFR-00252: Cannot find data source ID: {0} {1}. Attempting to find data source with same name.

Cause: A connection to the data source could not be made by using the stored data source ID.

Action: Verify that the data source is started or restored, and the credentials are correct.
Level: 32

Type: ERROR

Impact:

EPMFR-00253: Cannot find data source ID: {0} {1}. Attempting to find data source with same name.

Cause: A connection to the data source could not be made by using the stored data source ID.

Action: Verify that the data source is started or restored, and the credentials are correct.
Level: 32

Type: ERROR

Impact:

EPMFR-00254: Cannot not find data source ID: {0} {1}. Creating a new data source.

Cause: A connection to the data source could not be made by using the stored data source name.

Action: Verify that the data source is started or restored, and the credentials are correct.
Level: 32

Type: ERROR

Impact:

EPMFR-00255: Cannot find data source ID: {0} {1}. Creating a new data source.

Cause: A connection to the data source could not be made by using the stored data source name.

Action: Verify that the data source is started or restored, and the credentials are correct.
Level: 32

Type: ERROR

Impact:

EPMFR-00256: Cannot find data source ID: {0} {1}. Failed to create a new data source for it.

Cause: Could not make a connection to the data source by using the stored data source ID or name, and failed to create a new data source automatically for it.

Action: Verify that the data source is started or restored, and the credentials are correct.
Level: 32

Type: ERROR

Impact:

EPMFR-00257: Could not find data source ID: {0} {1}. Attempting to find data source with same name.

Cause: A connection to the data source could not be made by using the stored data source ID.

Action: Verify that the data source is started or restored, and the credentials are correct.
Level: 32

Type: ERROR

Impact:

EPMFR-00258: Could not find data source ID: {0} {1}. Attempting to find data source with same name.

Cause: A connection to the data source could not be made by using the stored data source ID.

Action: Verify that the data source is started or restored, and the credentials are correct.
Level: 32

Type: WARNING

Impact:

EPMFR-00259: Could not find data source ID: {0} {1}. Creating a new data source.

Cause: A connection to the data source could not be made by using the stored data source ID.

Action: Verify that the data source is started or restored, and the credentials are correct.
Level: 32

Type: ERROR

Impact:

EPMFR-00260: Could not find data source ID: {0} {1}. Creating a new data source.

Cause: A connection to the data source could not be made by using the stored data source ID.

Action: Verify that the data source is started or restored, and the credentials are correct.
Level: 32

Type: WARNING

Impact:

EPMFR-00261: Could not find data source ID: {0} {1}. Failed to create a new data source for it.

Cause: A connection to the data source could not be made by using the stored data source ID or name, and failed to create a new data source automatically for it.

Action: Verify that the data source is started or restored, and the credentials are correct.
Level: 32

Type: ERROR

Impact:

EPMFR-00262: Schema '{0}' not found. Attempting to create a new one.

Cause: The given schema was not previously loaded. An attempt to load it occurred.

Action: Ensure that the given schema is valid and can be loaded. Look for additional subsequent warnings.
Level: 32

Type: WARNING

Impact:

EPMFR-00263: XBRL Schema Manager not properly initialized

Cause: The XBRL Schema Manager was not properly configured.

Action: Reconfigure the XBRL Schema Manager.
Level: 32

Type: ERROR

Impact:

EPMFR-00264: XBRL Schema Manager not properly initialized

Cause: The XBRL Schema Manager was not properly configured.

Action: Reconfigure the XBRL Schema Manager.
Level: 32

Type: ERROR

Impact:

EPMFR-00265: Schema {0} was not found attempting to create a new one

Cause: The given schema was not previously loaded. An attempt to load it occurred.

Action: Make sure the given schema is valid and can be loaded. Look for subsequent warnings.
Level: 32

Type: WARNING

Impact:

EPMFR-00266: Taxonomy '{0}' does not have any namespace

Cause: The given taxonomy did not declare a namespace and was not be processed.

Action: Ensure that the given taxonomy declares a valid namespace.
Level: 32

Type: WARNING

Impact:

EPMFR-00267: Taxonomy '{0}' does not have any namespace

Cause: The given taxonomy did not declare a namespace and was not processed.

Action: Ensure that the given taxonomy declares a valid namespace.
Level: 32

Type: ERROR

Impact:

EPMFR-00268: Error while creating directories for emails:

Cause: The Schedule Server attempted to create a directory for e-mails but failed, most likely due to a system disk access issue.

Action: Verify that the disk is not full and that the user has both read and write access to the drive.
Level: 32

Type: ERROR

Impact:

EPMFR-00269: XBRL Footnote error retrieving report value. Report: {0}. Invalid Row ({1}) and Column ({2})

Cause: An error occurred while retrieving the report value. Invalid row and/or column reference were given.

Action: Ensure that the mapped footnote has valid row and column references to a grid.
Level: 32

Type: ERROR

Impact:

EPMFR-00270: XBRL No language definition in footnote

Cause: A footnote in the report did not provide a valid language definition.

Action: Assign a language to every footnote.
Level: 32

Type: ERROR

Impact:

EPMFR-00271: Report using unsupported version of XBRL. XBRL data is ignored.

Cause: The report had embedded XBRL data. However the version was unrecognized and could not be processed.

Action: Ensure that the XBRL data in the report definition is saved with the proper Financial Reports version.
Level: 32

Type: ERROR

Impact:

EPMFR-00272: Instance generation failed. File name specified: {0} is invalid.

Cause: The specified filename for the instance report was null or invalid. The instance document was not generated.

Action: Provide a valid file name for the instance document.
Level: 32

Type: ERROR

Impact:

EPMFR-00273: XBRL Footnote for '{0}' not properly set up

Cause: The XBRL footnote had a reference to an invalid report object.

Action: Ensure that all XBRL footnotes have valid references to a report object (grid or text).
Level: 32

Type: ERROR

Impact:

EPMFR-00274: Taxonomy element '{0}' is linked to an unregistered taxonomy '{1}'

Cause: The given taxonomy element belongs to an unregistered taxonomy.

Action: Ensure that the taxonomy used within a report is registered in the taxonomy repository.
Level: 32

Type: ERROR

Impact:

EPMFR-00275: Taxonomy element '{0}' has no context defined. It will not be persisted in the instance document.

Cause: A taxonomy element was mapped to data in a report, but there was no XBRL context associated with it. The element was ignored and not added to the instance document.

Action: Ensure that all mapped taxonomy elements in a report have a corresponding mapped context.
Level: 32

Type: ERROR

Impact:

EPMFR-00276: Taxonomy element '{0}' has no associated report object. It will not be persisted in the instance document.

Cause: A mapped taxonomy element was mapped to an invalid report object (grid or text).

Action: Ensure that all taxonomy elements are mapped to a valid report object.
Level: 32

Type: ERROR

Impact:

EPMFR-00277: Taxonomy element '{0}' has an unregistered taxonomy ('{1}'). It will not be persisted in the instance document.

Cause: A mapped taxonomy element belonged to an unregistered taxonomy. The element was ignored and not added to the instance document.

Action: Ensure that all mapped taxonomy elements in a report belong to a taxonomy that is registered in the Financial Reports system.
Level: 32

Type: ERROR

Impact:

EPMFR-00278: Cannot connect to server on {0}

Cause: Connection to the specified server failed, most likely due to an Remote Method Invocation (RMI) issue.

Action: Verify that the Remote Method Invocation (RMI) service is running without errors. Also look for possible network issues. Contact Oracle Support Services if additional assistance is needed.
Level: 32

Type: ERROR

Impact:

EPMFR-00279: Unable to find appropriate Service at {0}

Cause: Connection to the specified server failed, most likely due to an Remote Method Invocation (RMI) issue.

Action: Verify that the Remote Method Invocation (RMI) service is running without errors. Also look for possible network issues. Contact Oracle Service Support if additional assistance is needed.
Level: 32

Type: ERROR

Impact:

EPMFR-00280: Large imported file denied by the annotation UI

Cause: A file exceeding the AttachedFileMaxSize property limit was loaded.

Action: Reduce the file size or increase the AttachedFileMaxSize property.
Level: 32

Type: ERROR

Impact:

EPMFR-00281: Cannot create a Remote Method Invocation (RMI) registry on port: {0}

Cause: Another Remote Method Invocation (RMI) registry was running at the specified port number.

Action: Verify the configuration for the Remote Method Invocation (RMI) registry to avoid conflicts.
Level: 32

Type: ERROR

Impact:

EPMFR-00282: RMI (Remote Method Invocation) registry created on port: {0}

Cause: The Remote Method Invocation (RMI) regsitry was created on the specified port.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00283: Unable to create registry

Cause: An error occurred while attempting to establish a connection with the Remote Method Invocation (RMI) registry.

Action: Verify the configuration of the Remote Method Invocation (RMI) registry and ensure that it is running without errors.
Level: 32

Type: ERROR

Impact:

EPMFR-00284: Financial Reporting Print Server started

Cause: The print server started successfully.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00285: Print server not started

Cause: An error occurred while attempting to establish a connection with the Remote Method Invocation (RMI) registry.

Action: Verify the configuration of the Remote Method Invocation (RMI) registry and ensure that it is running without errors.
Level: 32

Type: ERROR

Impact:

EPMFR-00292: Element specified in the locator: {0} {1} not found.

Cause: The given taxonomy element could not be located from the given locator.

Action: Ensure that the taxonomy's locators have valid references to taxonomy elements.
Level: 32

Type: WARNING

Impact:

EPMFR-00293: Cannot initialize XBRL Schema Collection

Cause: Most likely, there were no schemas in the specified XBRL Location.

Action: This message is harmless if you do not intend to use XBRL. If you do, ensure that you have created the appropriate schemas in the specified location.
Level: 32

Type: WARNING

Impact:

EPMFR-00294: Invalid attempt accessing server controlled properties

Cause: The client side code tried to access a server-only controlled property.

Action: No action needed.
Level: 32

Type: ERROR

Impact:

EPMFR-00295: Unable to extract OBIEE session

Cause: Attempt to get administration level session failed.

Action: Verify the administrator user configuration in OBIEE.
Level: 32

Type: ERROR

Impact:

EPMFR-00297: Initialization of CredentialStore failed

Cause: The credential store could not be located or could not be initialized.

Action: Ensure that the credential store is properly configured.
Level: 32

Type: ERROR

Impact:

EPMFR-00298: Failed obtaining credentials from security store for {0}

Cause: Expected credentials could not be retrieved from credential store.

Action: Verify the credentials stored in credential store.
Level: 32

Type: ERROR

Impact:

EPMFR-00299: Failed obtaining credentials from security store for {0}

Cause: Expected credentials could not be retrieved from credential store.

Action: Verify credentials stored in credential store.
Level: 32

Type: ERROR

Impact:

EPMFR-00300: Attempt to get an undefined configuration property ({0})

Cause: A property was not defined or set. A default property was not available.

Action: Contact Oracle Support Services to obtain the correct default property value and instructions to configure it.
Level: 32

Type: ERROR

Impact:

EPMFR-00301: Attempt to get undefined configuration property ({0})

Cause: A property was not defined or set. A default property was not available.

Action: Contact Oracle Support Services to obtain the correct default property value and instructions to configure it.
Level: 32

Type: ERROR

Impact:

EPMFR-00303: Invalid attempt to authenticate with elevated user credentials

Cause: The configured elevated user credentials caused exception when trying to authenticate.

Action: Check the configured elevated user credentials.
Level: 32

Type: ERROR

Impact:

EPMFR-00304: Error while setting the POV for data source ID: {0}

Cause: There was a problem storing the current POV.

Action: Verify access to the repository.
Level: 32

Type: ERROR

Impact:

EPMFR-00305: PDFRootDirectory {0} not created. PDFs not generated.

Cause: The folder required to create the PDF files could not be created.

Action: Create the requird folder on the Print Server.
Level: 32

Type: FATAL

Impact:

EPMFR-00306: getObjectsById:Objects requested={0}, but objects returned is {1}

Cause: Some of the objects were not accessible.

Action: No action is required.
Level: 32

Type: WARNING

Impact:

EPMFR-00307: Cannot print using printer '{0}'. The printer is either not available to the Print Server or not configured for the host computer's services.

Cause: The specified printer was not used because either it was not available to the print server, or it was not configured for the host computer's services.

Action: Ensure that the print server is installed correctly.
Level: 32

Type: ERROR

Impact:

EPMFR-00308: Cannot print document file: '{0}' \tError code: {1}, Last Error: {2}

Cause: The specified document file was not printed.

Action: Verify that the external document link is correct.
Level: 32

Type: ERROR

Impact:

EPMFR-00309: Cannot print document file: '{0}' \tError code: {1}, Last Error: {2}

Cause: The specified document file was not printed.

Action: Verify that the external document link is correct.
Level: 32

Type: ERROR

Impact:

EPMFR-00310: Error writing external file '{0}'. It will not be included in the PDF output.

Cause: There was an error when writing the specified external file.

Action: Verify that the PDF output location is correct in the property file.
Level: 32

Type: ERROR

Impact:

EPMFR-00312: Invalid attempt accessing server controlled properties

Cause: The client side code tried to access a server-only controlled property.

Action: No action needed.
Level: 32

Type: ERROR

Impact:

EPMFR-00313: Invalid attempt to authenticate with elevated user credentials

Cause: The configured elevated user credentials caused exception when trying to authenticate.

Action: Check the configured elevated user credentials.
Level: 32

Type: ERROR

Impact:

EPMFR-00314: Financial Reports is configured to use Classic Print Engine. Please start the Print Server separately

Cause: This is a status message stating that the Financial Reporting Printing Service is configured to use the Classic Print Engine.

Action: Start the Print Server separately.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00315: Invalid user defined prefered date format ({1})

Cause: User defined date format contains Invalid date format characters

Action: Update user preferences with valid a date format
Level: 32

Type: ERROR

Impact:

EPMFR-00316: Custom Socket Factories loaded successfully

Cause: A status message stating that the sockets connecting to the RMI Server has successfully been established.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00317: Unable to establish port within established range

Cause: The established range of ports selected to access the RMI server are all unavailable.

Action: Either reestablish a different range with available ports, or, stop nonessencial processes that are occupying the port range and then retry.
Level: 32

Type: FATAL

Impact:

EPMFR-00318: Custom Socket Factories could not be loaded

Cause: The configured socket factory classes could not be loaded.

Action: Check the configuration for the Socket classes and ensure the entries are correct.
Level: 32

Type: FATAL

Impact:

EPMFR-00319: Book contains reports not found: {0}

Cause: Book contains reports which could not be found.

Action: Ensure that the contained report(s) exists.
Level: 32

Type: ERROR

Impact:

EPMFR-00323: FRExecute has invalid cell reference '{0}'

Cause: FRExecute referenced an invalid cell.

Action: Verify that the FRExecute function's parameters are valid.
Level: 32

Type: ERROR

Impact:

EPMFR-00324: FRExecute cannot generate an image for component '{0}'

Cause: FRExecute could not generate an image for the specified component.

Action: Verify that the FRExecute function's parameters are valid.
Level: 32

Type: ERROR

Impact:

EPMFR-00325: FRExecute cannot generate an image for component '{0}'

Cause: FRExecute could not generate an image for the specified component.

Action: Verify that the FRExecute function's parameters are valid.
Level: 32

Type: ERROR

Impact:

EPMFR-00326: FRExecute cannot generate an image for component '{0}'

Cause: FRExecute could not generate an image for the specified component.

Action: Verify that the FRExecute function's parameters are valid.
Level: 32

Type: ERROR

Impact:

EPMFR-00327: Cannot replace FRExecute function with the result.

Cause: The FRExecute function could not be replaced with the result.

Action: Verify that Microsoft Word is installed on the machine where the print server is located.
Level: 32

Type: ERROR

Impact:

EPMFR-00329: Error writing external file '{0}'. It will not be included in the PDF output.

Cause: There was an error when writing the specified external file.

Action: Verify that the PDF output location is correct in the property file.
Level: 32

Type: ERROR

Impact:

EPMFR-00330: Error writing external file '{0}'. It will not be included in the PDF output.

Cause: Error writing the specified external file. It will not be included in the PDF output.

Action: Verify that the pdf output location is correct in property file.
Level: 32

Type: ERROR

Impact:

EPMFR-00331: Cannot print document file: '{0}' \tError code: {1}, Last Error was: {2}

Cause: The specified document file was not printed.

Action: Verify that the external document link is correct.
Level: 32

Type: ERROR

Impact:

EPMFR-00332: Cannot print document file: '{0}' \tError code: {1}, Last Error was: {2}

Cause: The specified document file was not printed.

Action: Verify that the external document link is correct.
Level: 32

Type: ERROR

Impact:

EPMFR-00333: Cannot print report '{0}' within Book '{1}'. Make sure the report exists in the repository.

Cause: The specified report was not printed within the specified book.

Action: Ensure that all external object links in book are correct, that the book is valid, and that the report exists in the repository.
Level: 32

Type: ERROR

Impact:

EPMFR-00334: Cannot print report '{0}' within Book '{1}'. Make sure the report exists in the repository.

Cause: The specified report was not printed within the specified book..

Action: Ensure that all external object links in book are correct, that the book is valid, and that the report exists in the repository.
Level: 32

Type: ERROR

Impact:

EPMFR-00336: Could not find data source ID: {0} {1}. Attempting to find data source with same name.

Cause: A connection to the data source could not be made by using the stored data source ID.

Action: Verify that the data source is started or restored, and the credentials are correct.
Level: 32

Type: WARNING

Impact:

EPMFR-00337: Could not find data source ID: {0} {1}. Creating a new data source.

Cause: A connection to the data source could not be made by using the stored data source ID.

Action: Verify that the data source is started or restored, and the credentials are correct.
Level: 32

Type: WARNING

Impact:

EPMFR-00338: Could not find data source ID: {0} {1}. Failed to create a new data source for it.

Cause: A connection to the data source could not be made by using the stored data source ID or name, and failed to create a new data source automatically for it.

Action: Verify that the data source is started or restored, and the credentials are correct.
Level: 32

Type: ERROR

Impact:

EPMFR-00339: Usage: ManageUserPov Mode ConfigFile\tMode = import | export | delete\tConfigFile = configuration file name such as ManageUserPov.properties

Cause: An instruction about how to use the ManageUserPov utility was provided.

Action: Follow the instructions of the message.
Level: 32

Type: ERROR

Impact:

EPMFR-00340: Error loading config file: {0}

Cause: The specified config file did not exist or was not accessible.

Action: Supply a valid and accessible file name as a parameter.
Level: 32

Type: ERROR

Impact:

EPMFR-00341: Missing AdminUser

Cause: The configuration file did not have an administrative user (AdminUser) specified.

Action: In the configuration file, specify a user (AdminUser) with Administrator access.
Level: 32

Type: ERROR

Impact:

EPMFR-00342: Cannot print document file: '{0}' \tError code: {1}, Last Error: {2}

Cause: The specified document file was not printed.

Action: Verify that the external document link is correct.
Level: 32

Type: ERROR

Impact:

EPMFR-00343: Financial Reporting server is set to use embedded Print Server. Remote print servers will not register with the Financial Reporting server.

Cause: Financial Reporting server is set to use embedded printing

Action: If you would like to use this external print server, please disable embedded printing in the Financial Reporting server
Level: 32

Type: ERROR

Impact:

EPMFR-00344: Setting BaseWebApp in HIT registry to: "

Cause:

Action:
Level: 32

Type: INFORMATION

Impact:

EPMFR-00345: Setting BaseWebApp in HIT registry to: "

Cause:

Action:
Level: 32

Type: INFORMATION

Impact:

EPMFR-00346: Could not get version information from file system

Cause: version.xml could not be loaded or error parsing the file

Action: Make sure version.xml exists under common/epmstatic/wspace/SmartView/ on server
Level: 32

Type: INFORMATION

Impact:

EPMFR-00347: The system cannot access the Print Server at this time. Try again later or confirm the print server name.

Cause: The specified Print Server is not accessible

Action: Check the configuration for the correct Print Server name, if the Print Server is running, and if the connection to the Print Server is accessible
Level: 32

Type: WARNING

Impact:

EPMFR-00348: The system cannot access the Print Server at this time. Try again later or confirm the print server name.

Cause: The specified Print Server is not accessible

Action: Check the configuration for the correct Print Server name, if the Print Server is running, and if the connection to the Print Server is accessible
Level: 32

Type: WARNING

Impact:

EPMFR-00349: The system cannot access the Print Server at this time. Try again later or confirm the print server name.

Cause: The specified Print Server is not accessible

Action: Check the configuration for the correct Print Server name, if the Print Server is running, and if the connection to the Print Server is accessible
Level: 32

Type: WARNING

Impact:

EPMFR-00350: The system cannot access the Print Server at this time. Try again later or confirm the print server name.

Cause: The specified Print Server is not accessible

Action: Check the configuration for the correct Print Server name, if the Print Server is running, and if the connection to the Print Server is accessible
Level: 32

Type: WARNING

Impact:

EPMFR-00351: The system cannot access the Print Server at this time. Try again later or confirm the print server name.

Cause: The specified Print Server is not accessible

Action: Check the configuration for the correct Print Server name, if the Print Server is running, and if the connection to the Print Server is accessible
Level: 32

Type: WARNING

Impact:

EPMFR-00352: The system cannot access the Print Server at this time. Try again later or confirm the print server name.

Cause: The specified Print Server is not accessible

Action: Check the configuration for the correct Print Server name, if the Print Server is running, and if the connection to the Print Server is accessible
Level: 32

Type: WARNING

Impact:

EPMFR-00353: The system cannot access the Print Server at this time. Try again later or confirm the print server name.

Cause: The specified Print Server is not accessible

Action: Check the configuration for the correct Print Server name, if the Print Server is running, and if the connection to the Print Server is accessible
Level: 32

Type: WARNING

Impact:

EPMFR-00354: The system cannot access the Print Server at this time. Try again later or confirm the print server name.

Cause: The specified Print Server is not accessible

Action: Check the configuration for the correct Print Server name, if the Print Server is running, and if the connection to the Print Server is accessible
Level: 32

Type: WARNING

Impact:

EPMFR-00355: The system cannot access the Print Server at this time. Try again later or confirm the print server name.

Cause: The specified Print Server is not accessible

Action: Check the configuration for the correct Print Server name, if the Print Server is running, and if the connection to the Print Server is accessible
Level: 32

Type: WARNING

Impact:

EPMFR-00356: The system cannot access the Print Server at this time. Try again later or confirm the print server name.

Cause: The specified Print Server is not accessible

Action: Check the configuration for the correct Print Server name, if the Print Server is running, and if the connection to the Print Server is accessible
Level: 32

Type: WARNING

Impact:

37 EPMWKSP-00101 to EPMWKSP-02508

EPMWKSP-00101: Found application registration with ID "{0}" and name "{1}".

Cause: Indicates the application registration which was found and is recognized by Workspace.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00102: Failed to generate context XML.

Cause: Context information is invalid or could not be retrieved from the registry.

Action: Verify products have been properly configured by running Config Tool.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00103: Initializing Workspace Configuration.

Cause: Workspace is initializing the system using information from the registry.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00104: There is an error detecting application ID for role checking.

Cause: An application ID could not be retrieved for CSS role checking.

Action: Verify in the registry that all registered products have a valid value for property applicationId.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00105: Default Application ID for role checking is {0}.

Cause: Indicates the application ID that will be used for CSS role checking.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00106: There was an error determining the URL.

Cause: The logical webapp URL could not be obtained or is invalid.

Action: Verify that the logical webapp URLs specified in the registry for all registered products are valid.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00107: There was an error determining the context.

Cause: The logical webapp context could not be obtained or is invalid.

Action: Verify that the logical webapp context specified in the registry for all registered products are valid.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00108: There was an error parsing file {0}.

Cause: The xml in WSProducts.xml could not be parsed or is invalid.

Action: Verify the file exists and that the xml is valid.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00109: There was an error initializing system registry: {0}.

Cause: The system registry was not properly installed or configured.

Action: Verify connection to the registry is valid and re-run the config tool.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00110: Registry default properties: failed to check and set property {0}.

Cause: The default properties could not be set.

Action: Verify the default registry properties file exists and that the values are valid.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00111: There was an error loading product configuration data: {0}

Cause: The configuration file for at least one product could not be loaded.

Action: Check the Workspace configuration log for further error details.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00112: Failed to initialize the BPMUI authentication class: {0}

Cause: The class could not be found or initialization failed.

Action: Verify that the class is accessible and the entry in web.xml is valid.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00113: There was an error loading product configuration data: {0}

Cause: The configuration file for at least one product could not be loaded.

Action: Check the Workspace configuration log for further error details.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00114: Workspace initialization complete.

Cause: Workspace has initialized and processed the information from the registry.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00115: Workspace is running normally.

Cause: No errors were detected during initialization.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00116: Parsing the product file generated the following warnings:

Cause: Indicates the start of the list of possible issues encountered while parsing Workspace's Product file.

Action: Verify the Workspace's Products file exists and that the entries are valid.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00117: Workspace may not function properly unless these are fixed: {0} {1}

Cause: Indicates the xml may not comply with the dtd.

Action: Resolve the issue specified in the warning.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00118: End of warning messages.

Cause: Indicates the end of the list of possible issues encountered while parsing Workspace's Product file.

Action: Verify all warnings are resolved or inconsequential.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00119: Product file parsed without errors.

Cause: The Workspace's Product file was successfully processed.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00120: Attempting registry connection using:{0}{1}{2}{3}

Cause: Indicates the registry information is being obtained to initialize Workspace.

Action: No action required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00122: Looking for the Workspace Product component (type: {0})

Cause: Indicates the Product that is currently being validated and processed as one of the installed products in Workspace.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00123: Found component object: {0}

Cause: Indicates the Workspace component that was discovered in the EPM Registry.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00124: Could not find the Workspace Product component. Check Registry connection and content.

Cause: The registry connection or content may be invalid.

Action: Check Registry connection and content.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00125: Looking for Workspace Logical Webapp (child of Workspace Product, type: {0})

Cause: Indicates that Workspace is searching the EPM Registry for its Logical Webapp.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00126: Could not find the Workspace logical webapp. Check Registry contents.

Cause: The registry connection or content may be invalid.

Action: Check Registry contents.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00127: Could not find the Workspace Web Server component.

Cause: Workspace was not configured properly.

Action: Check the web server is running and configured. Run config tool.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00128: Could not find the logical webapp as a child of the Workspace product node. Check Registry contents.

Cause: Workspace was not properly registered.

Action: Check Registry contents. Run config tool.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00129: Workspace product node has multiple logical webapps. Check Registry contents.

Cause: Workspace should have exactly one component of type LOGICAL_WEB_APP in the EPM Registry.

Action: Verify Registry contents and check configuration tool logs for deployment errors.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00130: Could not find the Workspace Web Server component as a child of the Workspace product node.

Cause: Workspace was not properly configured.

Action: Check Registry contents. Run config tool.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00131: Found {0} webapps plugged in to the HTTP proxy at {1}:{2}

Cause: Indicates the webapps using the HTTP proxy.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00132: Found webapp: {0}

Cause: Indicates the webapp that is under the HTTP proxy.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00133: Web application type: {0}

Cause: Indicates the type of a webapp found while scanning the EPM Registry for products.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00134: This is the web application for EPM Workspace.

Cause: Indicates that a webapp discovered during a registry scan is EPM Workspace.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00135: Checking for Workspace configuration file(s)

Cause: Indicates if Workspace configuration file(s) were found.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00136: Checking for configuration file named: {0}

Cause: Indicates the specific configuration file being located.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00137: Found configuration file.

Cause: Indicates that the configuration file is found and accessible.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00138: ERROR: configuration file does not declare sharedServicesId. Product cannot be identified or loaded from product file.

Cause: The configuration file does not contain a node with sharedServicesId as an attribute.

Action: Verify that the product file being loaded is valid and has shreadServicesId declared.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00139: Loaded product with name {0}

Cause: Indicates the product was successfully loaded.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00140: Static file configuration matches version {0}; discarding registry file.

Cause: Indicates that Workspace's Product file has a configuration which matches a configuration in the registry and the configuration found in the Workspace's Product file will be used.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00141: Product not in static configuration file, initializing.

Cause: Indicates that a product's configuration information is being loaded from the registry.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00142: Static file configuration is for version(s): {0} but registered product version is {1}

Cause: Indicates that there is a different version of a configuration for the same registered product specified in Workspace's product file.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00143: Discarding static configuration.

Cause: Indicates that the product configuration from the registry will be used instead of the one found in Workspace's product file.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00144: NOTE: Product version for display is {0}

Cause: Indicates the product version to display in the Help->About.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00145: Skipping integration for this product.

Cause: The version for the product failed the version test.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00146: Product file configuration matches version {0}

Cause: Allow integration of product since it passes the version test.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00147: NOTE: Product version for display is {0}

Cause: The product version was found in the product configuration information.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00148: Skipping integration for this product.

Cause: The product configuration information could not be found in registry or in the Workspace's product file.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00149: Product not in static configuration file. Initializing product.

Cause: The product's configuration information was found in the registry but not in the Workspace's product file. Product will be configured with information from the registry.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00150: Product file configuration matches version {0}

Cause: Indicate the supported version.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00151: Product file configuration is for version(s): {0} but registered product version is {1}

Cause: Versions between product file configuration version and registered product version are mismatched.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00152: Discarding old configuration.

Cause: A more recent configuration was found and used.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00153: Setting product to use external configuration.

Cause: Indcates that a product does not have a configuration loaded from Workspace's static configuration files, and that the product configuration will be loaded from the EPM Registry.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00154: NOTE: Product version for display is {0}

Cause: Indicates the product version that is displayed in Workspace.

Action: No action is required.
Level: 32

Type:

Impact:

EPMWKSP-00155: Product {0}-{1} was not registered. Deactivating product.

Cause: The product may be not supported with the current Workspace version.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00156: Product {0} has been explicitly disabled. Deactivating product.

Cause: The products configuration has specified the disabled attribute.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00157: Product {0} was forcibly enabled and set at version {1}, but the internal configuration is valid for versions {2}.

Cause: The products configuration has the forceEnabled attribute set but the versions set may not be compatible with the current Workspace version.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00159: Setting product to use external configuration.

Cause: Indcates that a product does not have a configuration loaded from Workspace's static configuration files, and that the product configuration will be loaded from the EPM Registry.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00162: There was an error building the sorted product list.

Cause: Workspace was unable to determine the correct order in which to display integrated products.

Action: Consult Workspace logs for preceeding error messages. This is likely a consequence of prior errors while scanning the registry.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00163: There was an error refreshing display version for product {0} {1}.

Cause: Workspace could not determine a version number for a product.

Action: This error is not fatal, but product version numbers will be incorrect. Consult Workspace configuration log for further error messages.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00164: Read {0} bytes from the registry.

Cause: Indicates the number of bytes of data successfully processed from the registry.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00165: Missing product context {0}

Cause: The products context configuration information may be missing or invalid.

Action: Verify the products registration file is valid or run the config tool.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00166: Found and loaded context for {0}

Cause: A product's context was successfully loaded.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00167: Could not find product context for {0}. This product will not load.

Cause: A product's context could not be loaded.

Action: Verify the products configuration has a valid context configuration or run the config tool.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00168: Failed to parse HSS response for product {0}

Cause: The response may contain an invalid content type or the xml may be invalid.

Action: Verify the response is xml content type and that the xml is valid.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00169: Failed to connect and retrieve info for product {0}

Cause: The product's webapp may not be started, the url to the config xml may be invalid or the config xml is returning an invalid response.

Action: Verify the product's webapp is running, is properly configured and is returning a valid response.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00170: Failed to connect and retrieve info for product {0}

Cause: The product's webapp may not be started, the url to the config xml may be invalid or the config xml is returning an invalid response.

Action: Verify the product's webapp is running, is properly configured and is returning a valid response.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00171: Product file reports the following parse problems.

Cause: The xml is invalid and cannot be parsed.

Action: Try to resolve the reported parse problems.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00172: Workspace may not function properly unless these are fixed:{0} {1}

Cause: The xml couuld not be parsed.

Action: Try to resolve the reported issues.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00173: End of warning messages.

Cause: Indicates the end of the warning messages that needs attention.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00174: Product file parsed without errors.

Cause: Indicates the product file was valid.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00175: Checking HSS with product code {0}

Cause: Information is being retrieved from HSS for this product.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00176: Recovered {0} bytes from HSS.

Cause: The query to HSS was successful.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00177: Failed to recover configuration from HSS.

Cause: Information on this product could not be retrieved from HSS.

Action: Verify HSS connection is valid and the product is properly configured.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00178: There was an error loading default registry properties.

Cause: File was not found or could not be accessed.

Action: Verify file exists and is accessible.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00179: Parsing product file: {0}

Cause: Product file is parsed.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00180: Looking for Workspace Web Server (child of Workspace product with type: {0})

Cause: Indicates the Workspace Web Server.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00181: Found {0} HTTP proxy instance(s).

Cause: Indicates the number of HTTP proxy instances discovered when scanning the EPM Registry.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00182: File not found. Ending search.

Cause: Indicates that a product did not have a Workspace configuration file in the EPM Registry.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00183: EPM System Common Install Version: {0}

Cause: Indicates the version of the Common Installer.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00184: Checking product version numbers:

Cause: Product versions numbers must be compatible.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00185: Version number mismatch between the Workspace and BPMUI components detected. All version numbers must be at the same patchset level (first four parts of the the version number).

Cause: Workspace and BPMUI versions are mismatched.

Action: Locate a patch that is compatible with the current version.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00186: All versions are at the same patchset level.

Cause: System was patched correctly.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00187: Version number check skipped due to missing version numbers.

Cause: The version number was not specified in the configuration information.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00188: Checking Registry version numbers:

Cause: Indicate the current registry version numbers.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00189: Compiled against Registry version: {0}

Cause: Indicates the version of the EPM Registry API against which Workspace was compiled.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00190: WORKSPACE component version: {0}

Cause: Indicates the Workspace build number.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00191: LOGICAL_WEB_APP component version: {0}

Cause: Indicates the component version of Workspace's Logical Webapp component in the EPM Registry.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00192: WEB_SERVER component version: {0}

Cause: Indicates the component version of Workspace's Web Server component in the EPM Registry.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00193: Version number mismatch between the Workspace and registry components detected. All version numbers must be at the same release level (first three parts of the the version number).

Cause: Workspace and registry components are not on the same release level.

Action: Install and configure the matching Workspace and registry components.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00194: All version numbers are at the same release level.

Cause: Version numbers are from the same release.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00195: WARNING: Product registry version does not match Workspace registry version. Skipping integration for this product.

Cause: Product failed the version test.

Action: No action is required as it may be the product configuration is left over from an upgrade.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00196: Product {0} has at least one string bundle that is not statically loaded. Deactivating product.

Cause: The product's webapp is not running or the files are not there.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00197: BPMUI Java: {0}

Cause: Reports the version number of the BPMUI Java library.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00198: BPMUI Web: {0}

Cause: Reports the version number of the BPMUI shared web application.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00199: Workspace Java: {0}

Cause: Reports the version number of the Workspace Java library.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00201: Property "{0}" is not in the Registry. Default value is used.

Cause: Mentioned property is absent in the Registry.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00202: Message cache was cleared by admin request.

Cause: Admin user has changed server settings related to messaging system.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00203: Message cache expired. The message will be reread from the Registry.

Cause: Time of cache expiration has passed

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00204: Empty message is stored in the Registry.

Cause: No message is stored in the Registry.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00205: Can't find the file with name "{0}" in the Registry.

Cause: No message is stored in the Registry.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00206: There was an error reading message from the Registry.

Cause: Unexpected error occurred during reading message from the Registry.

Action: Verify HSS connection.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00301: Product "{0}" has been excluded from the list of SmartView providers.

Cause: Product is in list of excluded products.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00302: There was an error loading the list of products excluded from the list of SmartView providers.

Cause: The file with list of excluded products is corrupted or absent.

Action: Verify the file with list of excluded products.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00401: Error getting Workspace configuration instance.

Cause: System is not properly initialized.

Action: Verify system is properly initialized.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00402: There was an error during authentication.

Cause: User has entered wrong credentials.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00403: No credentials provided in the SmartView request.

Cause: User has not entered credentials.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00404: There was an error during processing:

Cause: Unexpected error occurred.

Action: Verify system is properly initialized.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00405: There was an error parsing the request.

Cause: Invalid request was sent

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00406: There was an error building handshake response.

Cause: Unexpected error occurred.

Action: Check log details and verify that system is properly initialized.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00408: There was an error building response.

Cause: Unexpected error occurred.

Action: Check log details and verify that system is properly initialized.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00507: There was an error determining the instanced product list.

Cause: Workspace was unable to determine the list of products that use per-instance provisioning.

Action: This is usually caused by an error when loading product configuration info. Check the Workspace configuration logs for other errors.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00508: There was an error determining the provisioned application list.

Cause: Workspace was unable to determine the list of applications for which the current user is provisioned.

Action: Check the Workspace security log for detailed errors from the security API.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00509: There was an error fetching an application registration

Cause: Workspace cannot fetch an application registration from Hyperion Shared Services and/or the EPM Registry.

Action: The Workspace configuration or security logs will contain further errors. Verify the registration of the product and application in Hyperion Shared Services.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00510: Fetching registration for product {0} application {1}

Cause: Indicates the product registration for an application is being retrieved.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00511: Fetched {0} bytes from HSS.

Cause: Indicates that the product registration information for an application has been retrieved from HSS successfully.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00512: Parsing the instance file caused the following warnings:

Cause: Indicates a list of warnings generated when parsing the application's registration file.

Action: These issues may cause the application to not function properly in Workspace. Verify the product registration in Shared Services.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00513: Instance may not function properly unless these are fixed:{0}{1}

Cause: Indicates a list of warnings generated when parsing the application's registration file.

Action: These issues may cause the application to not function properly in Workspace. Verify the product registration in Shared Services.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00514: End of warning messages.

Cause: Indicates all the warning messages has been listed.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00515: Instance file parsed without errors.

Cause: An application instance file was successfully processed by Workspace.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00601: Log on failed: error while checking user roles.

Cause: The user attempting to log on does not have the necessary role requirements for log on.

Action: Verify the user is properly provisioned to log on.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00602: Log on failed: error while checking user preferences.

Cause: The user preferences repository could not be accessed.

Action: Verify the connection to the user preferences repository is valid.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00603: There was an error while creating the Reporting and Analysis security token.

Cause: Workspace could not obtain a Reporting and Analysis security token.

Action: Verify the Reporting and Analysis webapp and services is running.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00604: There was an error determining user accessibility settings.

Cause: Obtaining accessibility mode setting from request parameter, CSS Session (Fusion), User Preference (EPM) or extant cookie may have failed.

Action: Verify accessibility mode settings is valid and in request parameter, CSS Session (Fusion), User Preference (EPM) or extant cookie.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00605: There was an error determining user theme settings.

Cause: Obtaining theme settings from request parameter, CSS Session (Fusion), User Preference (EPM) or extant cookie may have failed.

Action: Verify theme settings is valid and in request parameter, CSS Session (Fusion), User Preference (EPM) or extant cookie.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00606: There was an error determining user locale settings.

Cause: There was an error obtaining the locale from the CSS session or request parameter.

Action: Verify the local is valid and in the CSS session or request parameter.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00607: There was an error validating user theme selection.

Cause: The theme selection does not match one of the supported themes.

Action: Verify the user theme selection is one of the supported themes.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01301: Could not resolve role: {0}

Cause: Workspace was unable to verify the existence of the named role.

Action: Verify the user provisioning and product registration in Shared Services. The named role will not be used by Workspace.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01302: Exception while checking user roles

Cause: Workspace was unable to check a user's provisioned roles.

Action: Check the Workspace security log for further errors from the security API
Level: 32

Type: ERROR

Impact:

EPMWKSP-01401: There was an error while parsing {0}

Cause: Workspace was unable to parse its own role definition file.

Action: Verify that the Workspace deployment has not been corrupted. Contact technical support for further guidance.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01402: Mapping role name {0} to role ID {1}

Cause: Indicates that a role has been successfully matched to a Shared Services LDAP ID or a Reporting and Analaysis GUID.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01501: Searching for users matching '{0}' as user {1}

Cause: Indicates a search request for users conducted by an administrator.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01502: Found {0} result(s).

Cause: Indicates the number of users found by an administrative search for users.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01503: Invalid user/group search filter '{0}' specified.

Cause: Indicates that an administrative search for users included an invalid search specification.

Action: Use a valid search string. Search strings for user names are Unicode alphabet character strings preceeded or followed with '*' as a wildcard.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01601: The value for parameter "{0}" was invalid.

Cause: Specified parameter's value is invalid.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01602: Validating parameter "{0}" with value "{1}".

Cause: Parameter is being validated

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01603: Loading list of supported locales from default configuration.

Cause: Default list of supported locales is loaded

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01604: There was an error loading default list of supported locales.

Cause: System is not properly initialized.

Action: Verify system is properly initialized.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01701: There was an error evaluating product-level Constraints for {0}. Deactivating product.

Cause: There was an issue with one of the product-level constraints.

Action: Verify the product-level constraints are valid.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01702: There was an error generating product path

Cause: The direct-access URL, non-proxied path to the product could not be obtained.

Action: Verify the product's webapp is running and correctly configured.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01801: Redirecting From Url: {0}

Cause: This is the URL before the redirect.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01802: Redirecting To Url: {0}

Cause: This is the URL after the redirect.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01803: Get Logical WebApp Info.

Cause: This is the information retrieved on the logical webapp.

Action: Registration may have failed. Try re-registering the products by running the configuration tool.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01804: Get Logical WebApp Info for workspace failed, using default.

Cause: The logical webapp information for Workspace could not be retrieved. Assuming the context is /workspace.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01805: Current Context Path: {0}

Cause: Indicates the current context path before the redirect.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01806: Redirect Context Path: /{0}

Cause: Indicates the context path after the redirect.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01807: Form Post Redirect

Cause: Indicates that redirect was handled by performing a form post.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01808: Send Redirect with Cookie {0}: {1}

Cause: Indicates the redirect was handled by a send redirect. Cookies are included in the redirect.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01809: The servlet failed, invalid token or url.

Cause: Indicates the URL or token may be invalide which caused the redirect to fail.

Action: Verify the URL is valid and user is properly provisioned.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01810: The servlet failed, bad redirect url or token: {0}

Cause: User is not authenticated.

Action: Verify the user is properly provisioned.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01811: Processed {0} urls to redirect using form post.

Cause: Indicates the URLs that must be redirected using a form post.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01812: The servlet failed to initialize the form post list: {0}

Cause: An error was encountered while attempting to retrieve information on the URLs.

Action: Verify in the web.xml under the redirect servlet node that the entries for FormPostList are valid.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01813: Processed {0} parameters to omit from redirect.

Cause: Indicates the number of parameters that were found and should be omitted from the redirect.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01814: The servlet failed to initialize the param omit list: {0}

Cause: An error was encountered while attempting to retrieve the list of parameters to omit from the redirect.

Action: Verify in the web.xml under the redirect servlet node that the entries for ParamOmitList are valid.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01815: isFormPostUrl: {0} in {1} {2}

Cause: Indicates if the current URL should be redirected with a form post.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01816: isParamOmit: {0}

Cause: Indicates if the current parameter should be omitted from the redirect.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01901: The "{0}" persistence unit is already open

Cause: Indicates that while attempting to initialize the persistence, a previous attempt to terminate failed.

Action: This unexpected state should be reported, although the code will continue on and not attempt to initialize the persistence.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01902: Initializing persistence with the connection configured in "{0}"

Cause: Indicates that an attempt is being made to initialize the persistence with the connection information in the specified file.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01903: Loading the "{0}" persistence unit

Cause: Indicates that an attempt is being made to load the specified persistence unit.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01904: Unloading the "{0}" persistence unit

Cause: Indicates that an attempt is being made to unload the specified persistence unit.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01905: The "{0}" persistence unit is not open

Cause: Indicates that while attempting to terminate the persistence, a previous attempt to initialize failed.

Action: This unexpected state should be reported, although the code will continue on and not attempt to terminate the persistence.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01906: Started the migration

Cause: Indicates that the migration has started.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01907: Ended the migration

Cause: Indicates that the migration has ended.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01908: Started the migration initialization

Cause: Indicates that the migration initialization has started.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01909: Ended the migration initialization

Cause: Indicates that the migration initialization has ended.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01910: Started the migration termination

Cause: Indicates that the migration termination has started.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01911: Ended the migration termination

Cause: Indicates that the migration termination has ended.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01912: Started the migration to Talleyrand

Cause: Indicates that the migration to the Talleyrand release has started.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01913: Couldn't find the user with identity "{0}"

Cause: Indicates that the identity of an existing user could not be located in the security system.

Action: The specified identity should be recorded to see why they are no longer in the security system (such as leaving the company, or a name change that affects the identity).
Level: 32

Type: ERROR

Impact:

EPMWKSP-01914: User={0}, Properties={1}

Cause: Indicates a user and their properties that are being migrated

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01915: Ended the migration to Talleyrand

Cause: Indicates that the migration to the Talleyrand release has ended.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01916: Started the connection acquisition for component type "{0}"

Cause: Indicates that the connection acquisition for the specified component type has started.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01917: JdbcDriver={0}

Cause: Indicates the JDBC driver that is being used for the connection acquisition.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01918: JdbcUrl={0}

Cause: Indicates the JDBC URL that is being used for the connection acquisition.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01919: JdbcUserName={0}

Cause: Indicates the JDBC username that is being used for the connection acquisition.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01920: JdbcPassword={0}

Cause: Indicates the JDBC password that is being used for the connection acquisition.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01921: JdbcDataSourceName={0}

Cause: Indicates the JDBC data source name that is being used for the connection acquisition.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01922: JndiName={0}

Cause: Indicates the JNDI name that is being used for the connection acquisition.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01923: Ended the connection acquisition for component type "{0}"

Cause: Indicates that the connection acquisition for the specified component type has started.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02101: An empty search term was passed into Dynamic Help. The client search pages filter for this, so the submission may be from a source other than the search form.

Cause: An empty search term was passed in.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02102: No topics matched the search criteria.

Cause: Indicates that no topics matched the user's search criteria.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02103: Exact phrase search - add quotes to set term string as {0}

Cause: Indicates the user specified an exact phrase search.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02104: query string: {0}

Cause: Logs the search query string.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02105: parsed query: {0}

Cause: Logs the parsed query.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02106: Dynamic Help could not create the Lucene query parser:

Cause: Unknown cause.

Action: Verify that the Lucene search engine .jars are available.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02107: Version number not returned from Workspace. The path to the Lucene index thus cannot be resolved for module: {0}

Cause: Could not obtain the product's version number from the Workspace Registry for an unknown reason.

Action: Try the search again. If the same issue occurs, validate that the product is correctly registered with Workspace.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02108: adding Lucene index path {0}

Cause: Logging the search engine index location for the product.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02109: The Lucene index for the {0} module was not found in {1}

Cause: The search engine index for the product and locale may be missing, or the EPM_ORACLE_HOME system variable may not be properly set.

Action: If the logged index path begins with null, the EPM_ORACLE_HOME system variable is not set; if so, set it. Otherwise, check whether the search index for the product and locale is installed in the specified location.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02110: The Lucene search index could not be found, so no search was conducted.

Cause: No search engine indices were found.

Action: Check whether the search index for the product and locale is installed in the specified location. Also, make sure the EPM_ORACLE_HOME system variable is correctly set.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02111: parsed CJK query: {0}

Cause: Logging the parsed query for an Asian locale.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02112: Dynamic Help could not create the Lucene CJK query parser:

Cause: Unknown cause.

Action: Verify that the Lucene search engine .jars are available.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02113: I18N QueryFilter: {0}

Cause: Logging the query filter for an Asian locale.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02114: internationalized query: {0}

Cause: Logging the query for searches on multiple locales.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02115: Dynamic Help could not execute search

Cause: Search cannot be executed for an unknown reason.

Action: Try searching again. If the same issue occurs, a component help depends upon may be mis-configured or unavailable.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02201: Error in setting tools context ID data.

Cause: Could not obtain data from the Workspace Registry for the Reporting and Analysis Framework products' help.

Action: Validate that the Registry entries for the Reporting and Analysis Framework products are correctly defined.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02202: Error in setting IR help path.

Cause: Unknown cause.

Action: Make sure that the Workspace Registry Dynamic Help entries for the tools context are correctly defined.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02203: Error in setting SQR help path.

Cause: Unknown cause.

Action: Make sure that the Workspace Registry Dynamic Help entries for the tools context are correctly defined.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02204: Error in adding IR help paths:

Cause: Unknown cause.

Action: Make sure that the Workspace Registry Dynamic Help entries for the tools context are correctly defined.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02205: Error in adding SQR help paths:

Cause: Unknown cause.

Action: Make sure that the Workspace Registry Dynamic Help entries for the tools context are correctly defined.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02206: Error in adding IR launch pages:

Cause: Unknown cause.

Action: No action is required; minor issue.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02207: Error in adding SQR launch pages:

Cause: Unknown cause.

Action: No action is required; minor issue.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02208: Workspace Registry returned no name for the product code {0}. Dynamic Help will display the product code as a fallback.

Cause: The product's displayName Workspace Registry attribute may not be set.

Action: Set the displayName attribute.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02301: UPK URL is an empty string.

Cause: The UPK URI obtained from Workspace is an empty string.

Action: Make sure that a valid UPK URI is set in the Workspace Server Settings dialog.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02302: UPK URL is null.

Cause: Workspace is indicating that UPK should be displayed, but the UPK URI value is not available.

Action: Make sure that a valid UPK URI is set in the Workspace Server Settings dialog.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02303: Exception trying to redirect to UPK:

Cause: For an unknown reason, an error occurred when forwarding to UPK.

Action: Verify that a valid UPK URI is set in the Workspace Server Settings dialog, then try accessing UPK again. If that does not work, as a workaround try accessing UPK through the UPK toolbar icon in help.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02401: Error testing for string in array:

Cause: Unknown cause.

Action: If help is not displaying in the correct locale, try accessing help again.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02501: There was an error getting version number for module {0}.

Cause: Could not obtain the product's version number from the Workspace Registry.

Action: Validate the product's Workspace Registry entry.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02502: There was an error in getting the product name for product {0}.

Cause: An Exception occurred for unknown reasons when help tried to obtain a product name from the Workspace Registry.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02503: The help system path is: {0}

Cause: Logging the path to the help system.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02504: There was an error setting the help system path for module: {0} guide: {1} locale: {2}

Cause: Unknown cause.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02505: There was an error retrieving registered Workspace products.

Cause: Unknown cause.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02506: Dynamic help could not create array of products and guides.

Cause: Unknown cause.

Action: Validate that the products' Workspace Registry entries are correctly defined.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02507: There was an error getting the launch page.

Cause: Unknown cause.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02508: There was an error getting the language for the help guide. Using English.

Cause: Unknown cause.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

38 ESS-00001 to ESS-09408

ESS-00001: Internal error. {0}

Cause: Internal error occurred.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-00002: Constraint error for property {0} with value {1}.

Cause: An attempt was made to create an object that already exists.

Action: Specifiy an identifier for the object that is not currently in use.
Level: 1

Type: ERROR

Impact: Other

Cause: An attempt was made to change the value of an object thatis read-only.

Action: Retry the operation without changing the value of the object.

ESS-00003: Failed to find resource {0}. {1}

Cause: A JNDI lookup of the given resource failed.

Action: Ensure the resource is deployed properly and is available via jndi lookup.
Level: 1

Type: ERROR

Impact: Other

ESS-00004: Incorrect timestamp format: {0}. {1}

Cause: An invalid value was specified for a timestamp.

Action: Specify a correct value for the parameter.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-00005: SQL bind operation not supported for parameter data type: {0}

Cause: A value being used for an SQL bind parameter has a data type that is not suitable for the SQL Statement.

Action: Specify a parameter value having an appropriate data type.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-00006: Enterprise Scheduler configuration is not initialized.

Cause: An operation attempted to access Enterprise Scheduler configuration information before the configuration was initialized.

Action: Re-try the operation at a later time.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-00007: Operation intended for group, {0}. Configured group is {1}.

Cause: An Enterprise Scheduler instance received an event, message, or other data that was intended for an instance of a different group.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

ESS-00100: Install plan is not present for application {0}.

Cause: The install plan is not present for the application being deployed.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Installation

ESS-00101: Global data source, {0}, could not be created.

Cause: The global data source could not be created.

Action: Check the underlying cause for details.
Level: 1

Type: ERROR

Impact: Installation

ESS-00102: Dependent component, {0}, has not been deployed.

Cause: A dependent component of this component has not been deployed. An error may have occurred when deploying dependent component.

Action: Check log for errors in deploying dependent component.
Level: 1

Type: ERROR

Impact: Installation

ESS-00103: Error finding application {0}.

Cause: An error occurred while attempting to find the specified application.

Action: Perform the action specified in the chained exception.
Level: 1

Type: WARNING

Impact: Installation

ESS-00104: Cannot find object {0} for archive {1}.

Cause: The attempt to access the specified object failed.

Action: None
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-00120: Invalid value for dispatcher poll interval.

Cause: Attempted to configure an invalid value for the dispatcher minimum or maximum poll interval.

Action: Retry the operation with a non-negative numeric value.
Level: 1

Type: ERROR

Impact: Other

ESS-00121: Dispatcher poll interval minimum value cannot exceed maximum value.

Cause: Attempted to configure a value for the dispatcher minimum poll interval that is greater than the maximum value.

Action: Retry the operation with a value that is less than or equal to the maximum value.
Level: 1

Type: ERROR

Impact: Other

Cause: Attempted to configure a value for the dispatcher maximum poll interval that is less than the minimum value.

Action: Retry the operation with a value that is equal to or greater than the minimum value.

ESS-00122: Invalid value for processor threads.

Cause: Attempted to configure an invalid value for the processor maximum threads.

Action: Retry the operation with a non-negative numeric value.
Level: 1

Type: ERROR

Impact: Other

ESS-00123: Invalid value for processor starvation threshold.

Cause: Attempted to configure an invalid value for the processor starvation threshold.

Action: Retry the operation with a non-negative numeric value.
Level: 1

Type: ERROR

Impact: Other

ESS-00124: Unable to validate metadata for work assignment {0}.

Cause: Attempted to add or remove bindings for an work assignment.

Action: Retry the operation with a valid work assignment name.
Level: 1

Type: ERROR

Impact: Other

ESS-00300: Invalid value ({0}) for {1} argument.

Cause: The value specified for an argument is not valid.

Action: Retry the operation using a valid value.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-00301: TopologyNodeType, {0}, is not supported for this operation.

Cause: The operation is not supported on the specified topology node type.

Action: Retry the operation on OC4JComponent or Group.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-00310: Work assignment, {0}, already exists.

Cause: Attempted an operation using a work assignment that already exists.

Action: Retry the operation with an assignment that does not exist.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-00311: Work assignment, {0}, does not exist.

Cause: Attempted an operation using a work assignment that does not exist.

Action: Retry the operation with an assignment that exists.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-00312: Group, {0}, does not exist.

Cause: Attempted an operation using a group that does not exist.

Action: Retry the operation with a group that exists.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-00313: Failed to read the configuration document.

Cause: Failed to read the configuration document.

Action: Check the underlying cause for details.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-00314: Failed to write the configuration document.

Cause: Failed to write the configuration document.

Action: Check the underlying cause for details.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-00315: Invalid Wait Queue polling interval; minimum ({0}) > maximum ({1}).

Cause: Invalid Wait Queue polling interval.

Action: Provide a valid polling interval.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-00316: Invalid minimum Wait Queue polling interval ({0}).

Cause: Invalid minimum Wait Queue polling interval.

Action: Provide a valid polling interval.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-00317: Invalid maximum Wait Queue polling interval ({0}).

Cause: Invalid maximum Wait Queue polling interval.

Action: Provide a valid polling interval.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-00318: Invalid threshold ({0}) for processing low priority jobs.

Cause: Threshold is invalid.

Action: Correct the threshold value.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-00319: Invalid value ({0}) for threads to be available for request processing.

Cause: Threads used for request processing are invalid.

Action: Call Oracle Support.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-00400: Insufficient information to execute the command.

Cause: A valid command was specified but the supplied information was not adequate to execute the command, possibly due to missing command switches or keywords.

Action: Review the help and syntax for the command. Retry the operation with additional information.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-00401: Error attempting to execute the "{0}" operation. {1}

Cause: Encountered an error while trying to execute the specified operation.

Action: Review the error information to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-00402: Invalid work assignment mode ({0}).

Cause: Value specified for a work assignment mode is not valid.

Action: Retry the operation with a valid value; "primary" or "secondary".
Level: 1

Type: ERROR

Impact: Programmatic

ESS-00403: Work assignment is required.

Cause: A work assignment is required for the operation but none was specified.

Action: Retry the operation with at least one work assignment.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-00404: Invalid topoNode "{0}".

Cause: Invalid topoNode

Action: Provide a valid topoNode value and make usre the Config MBean is registered with ESSAPP
Level: 1

Type: ERROR

Impact: Programmatic

ESS-00405: The Config MBean "{0}" is not registered with the ESSAPP.

Cause: Config MBean is not registered with the ESSAPP

Action: Make sure the Config MBean is registered with ESSAPP and then retry
Level: 1

Type: ERROR

Impact: Programmatic

ESS-00500: Failed to create metadata service handle.

Cause: An error occurred while starting a Metadata session.

Action: See the base exception for details.
Level: 1

Type: WARNING

Impact: Other

ESS-00501: Failed to close metadata service handle.

Cause: An error occurred while closing a Metadata session.

Action: See the base exception for details.
Level: 1

Type: WARNING

Impact: Other

ESS-00502: The metadata object type must be specified

Cause: The metadata type was not specified when creating the metadata object

Action: Specify a valid value for the metadata object type
Level: 1

Type: WARNING

Impact: Other

ESS-01000: Failed to open runtime service. {0}

Cause: An error occurred opening the RuntimeService handle

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01001: Failed to close runtime service handle. {0}

Cause: An error occurred closing the RuntimeService handle

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01002: Illegal attempt to validate request, {0}, when current state, {1}, is not PENDING_VALIDATION.

Cause: A request is in an illegal state for validation.

Action: None
Level: 1

Type: ERROR

Impact: Other

ESS-01003: Illegal operation for an unvalidated request {0}.

Cause: The operation is not supported for an unvalidated request.

Action: Do not attempt this operation unless the request is validated.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01004: Illegal attempt to set state of request, {0}, to VALIDATION_FAILED when current state, {1}, is not PENDING_VALIDATION.

Cause: An internal error occurred.

Action: None
Level: 1

Type: ERROR

Impact: Other

ESS-01005: Parameter {0} does not exist for request {1}.

Cause: The given parameter name does not exist for this request.

Action: Specify an existing parameter.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01006: RuntimeServiceHandle is marked for rollback only.

Cause: The ESS runtime service handle has been marked for rollback only.

Action: Close the ESS runtime service session. Another session may be created for further operations.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01007: RuntimeServiceHandle is null.

Cause: The ESS runtime service handle is null.

Action: Specify a valid ESS runtime service handle.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01008: Value for parameter, {0}, has an invalid data type: {1}.

Cause: The value for a parameter has an unsupported data type.

Action: Specify a value which has a supported data type for the parameter.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01009: Value for parameter, {0}, is not valid.

Cause: The value for a parameter is not valid.

Action: Specify a valid value for the parameter.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01010: Value for parameter, {0}, must not be null.

Cause: The given parameter does not support a null value, or empty string for string parameter.

Action: Specify a non-null value for the parameter.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01011: Parameter, {0}, is required but was not specified.

Cause: The given parameter is required but was not specified.

Action: Specify the required parameter.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01012: Request {0} not found.

Cause: A request that was the target of a RuntimeService operation was not found in the runtime store.

Action: Specify a valid request identifier.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01013: Failed to lock request {0}. Request not found.

Cause: Attemped to lock a request that was not found in the runtime store.

Action: Specify a valid request identifier.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01014: Error occurred attempting to lock request {0}.

Cause: An error occurred attempting to lock a request in the runtime store.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-01015: Failed to generate a request identifier.

Cause: An error occurred attempting to generate a new request identifier.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-01016: Failed to generate a request handle.

Cause: An error occurred attempting to generate a new request handle.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-01017: Error attempting to access information for request {0}.

Cause: An error occurred attempting to access information for a request.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-01018: Error attempting to update information for request {0}.

Cause: An error occurred attempting to update information for a request.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-01019: Request {0} is not in {1} state. Current state is {2}.

Cause: An operation was attempted when the request was not in an expected state.

Action: Retry the operation when the request is the correct state.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01022: Error occurred retrieving summary data. {0}

Cause: An error occurred attempting to retrieve request or application summary information.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-01023: Parameter {0} for request {1} is read-only.

Cause: Attempted to modify the value for a request parameter that is read-only.

Action: None
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01024: This operation is illegal for this request. {0}

Cause: The invoked operation is not legal for this request.

Action: None
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01025: The request does not have a schedule. {0}

Cause: This operation can only be applied to a request with a schedule.

Action: None
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01026: Schedule for request {0} cannot be changed when in state {1}

Cause: The schedule for this request cannot be replaced in the current state.

Action: None
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01027: Failed to convert schedule to string

Cause: The schedule cannot be converted to a string.

Action: None
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01028: Request submission or validation failed. {0}

Cause: An error occurred during request submission or validation.

Action: None
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01029: Failed to create child request for parent request {0}.

Cause: An error occurred while attempting to create a child request for a parent that was submitted with a Schedule or Trigger.

Action: None
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01030: Failed to create JobSet step request for parent request {0}, step {1}.

Cause: An error occurred while attempting to create a request for a JobSet step.

Action: None
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01031: Application {0} was not found.

Cause: Attempted to submit a request for an application associated with a logical name but no such application was found.

Action: Deploy the application
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01032: Application {0} was found in more than one process group.

Cause: Attempted to submit a request for an application that is deployed to multiple process groups. Unable to determine correct group to use.

Action: Application should be deployed to only one group.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01033: Application {0} was not found for process group {1}.

Cause: Attempted to submit a request for an application that is deployed to multiple process groups. Unable to determine correct group to use.

Action: Application should be deployed to only one group.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01034: Unable to determine the deployed application name for logical application {0}.

Cause: Unable to determine the name of the deployed application for the specified logical name.

Action: Check for deployment errors.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01035: Unable to determine a logical application name for new request.

Cause: Unable to determine the logical application that should be used for a submitted request.

Action: Specify a value for the SystemProperty.EFFECTIVE_APPLICATION parameter in the metatadata for the JobDefinition or JobSet.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01036: Unable to determine a process group for new request.

Cause: Unable to determine the process group that should be used for a submitted request.

Action: None
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01037: Job definition is required for a non-Adhoc request submission.

Cause: A submit operation was attempted for a non-adhoc job but no metadata id for a JobDefinition or JobSet was given.

Action: Retry the submit operation and specify a job defintion.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01038: Read-Only violation for request parameter {0}.

Cause: The given parameter is marked as read-only and was specified as a request parameter.

Action: Retry the operation without the parameter.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01039: Parameter, {0}, is not allowed in request submission parameters.

Cause: The given parameter is not allowed to be included as a request parameter for a submit operation. Usually such paramters can be set only via a metadata parameter.

Action: Retry the operation without the given parameter.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01040: Invalid parameter {0}. Scoped parameters are only supported for JobSet.

Cause: A scoped parameter was included in the request parameters specified for the request submisssion of a JobDefinition. Scoped parameters are supported only for a JobSet.

Action: Retry the submit operation without the scoped parameter.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01041: Parameter, {0}, is not allowed as a scoped request parameter for JobSet step {1}.

Cause: The request parameters for a JobSet submission include a scoped parameter that is not allowed to be specified as a scoped parameter for a JobSet step.

Action: Retry the submit operation without the scoped parameter.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01042: Metadata type, {0}, is not supported for a sub-request.Only JobDefinition is supported.

Cause: Attempted to submit a sub-request for an unsupported definition type. Subrequest supported only for a JobDefinition.

Action: Retry the operation using a valid defintion type.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01043: Failed to get XML for an adhoc Schedule.

Cause: Error occurred creating XML representation of an adhoc Schedule.

Action: Fix the adhoc Schedule and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01044: Failed to get XML for an adhoc Trigger.

Cause: Error occurred creating XML representation of an adhoc Trigger.

Action: Fix the adhoc Trigger and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01045: Failed to validate Trigger expression against the schema.

Cause: Error occurred validating the XML for a Trigger expression.

Action: Fix the Trigger expression and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01046: Start time must be before the end time.

Cause: Attempted to submit a request where the start time is after the end time.

Action: Retry the operation with valid start and end times.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01047: End time must be after the current time.

Cause: Attempted to submit a request where the end time is before the current time.

Action: Retry the operation with value end time.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01048: Schedule has expired and no executions are possible.

Cause: Attempted to submit a request with a Schedule that has expired.

Action: Retry the operation with a different Schedule.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01049: No executions are possible before the given end date.

Cause: Attempted to submit a request with a Schedule for which there no executions prior to the end date.

Action: Retry the operation with a different Schedule.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01050: One or more requests are currently pending for definition: {0}

Cause: The SystemProperty.ALLOW_MULT_PENDING property is disabled for the request being submitted. Execution is already pending for one or more requests with the same job definition.

Action: None
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01051: Incompatible with parent request {0} due to Incompatibility definition: {1}

Cause: Attempted to submit a sub-request that is incompatible with its parent request due to an Incompatibility definition

Action: None
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01052: Request handle is not valid for the current execution context of parent request {0}.

Cause: The SystemProperty.ALLOW_MULT_PENDING property is disabled for the request being submitted. Execution is already pending for one or more requests with the same job definition.

Action: None
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01053: Cannot cancel request {0}. Current state is {1}.

Cause: Attempted to cancel a request whose current state does not allow the operation to be performed.

Action: None
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01054: Cannot hold request {0}. Current state is {1}.

Cause: Attempted to hold a request whose current state does not allow the operation to be performed.

Action: None
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01055: Cannot release request {0}. Current state is {1}.

Cause: Attempted to release a request whose current state does not allow the operation to be performed.

Action: None
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01056: Cannot delete request {0}. Current state is {1}, process phase is {2}.

Cause: Attempted to delete a request whose current state or process phase does not allow the operation to be performed.

Action: Retry the operation at a later time.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01057: Cannot purge request {0}. Current state is {1}, process phase is {2}.

Cause: Attempted to purge a request whose current state or process phase does not allow the operation to be performed.

Action: Retry the operation at a later time.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01058: Cannot change priority for request {0}. Current state is {1}.

Cause: Attempted to change the priority for a request whose current state does not allow the operation to be performed.

Action: None
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01059: Delete failed for request {0}. This operation is not supported for a sub-request or JobSet step.

Cause: Attempted to perform a delete operation on a child request. Only an absolute parent or instance parent can be the target of a delete operation.

Action: None
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01060: Purge failed for request {0}. This operation not supported for a sub-request or JobSet step.

Cause: Attempted to perform a purge operation on a child request. Only an absolute parent or instance parent can be the target of a purge operation.

Action: None
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01061: Failed to purge request {0}.

Cause: An error occurred attempting to purge a request.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01062: Invalid priority value. Valid range is {0} to {1}.

Cause: An invalid value for request priority is specified.

Action: Specify a value in the indicated range.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01063: Failed to retrieve Schedule for request {0}.

Cause: Failed to retrieve the Schedule associated with the given request.

Action: None
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01064: Failed to retrieve Trigger for request {0}.

Cause: Failed to retrieve the Trigger associated with the given request.

Action: None
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01065: Cannot recover request {0} with incomplete child requests.

Cause: An attempt was made to manually recover a request with at least one child not in ProcessPhase.Complete.

Action: Wait for the incomplete child to complete or recover.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01066: Request state {0} not allowed for manual recovery. State should be canceling or terminal. {1}

Cause: An attempt was made to manually recover a request that was in an illegal state.

Action: Cancel the request.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01067: Error occurred mapping Filter to CompositeData.

Cause: Error occurred mapping Filter to CompositeData.

Action: Correct the invalid CompositeData instance.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01068: Unexpected type, {0}, for Filter value {1}.

Cause: Unexpected Filter type for Filter value.

Action: Correct the invalid Filter type.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01069: Invalid Null input for a Filter {0}.

Cause: Unexpected null input for a filter.

Action: Provider a non null value.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01070: Cannot change start time or end time for request of type {0}

Cause: The start and end times cannot be updated for a request this type.

Action: None
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01071: Schedule for request {0} cannot be for a retry attempt

Cause: The schedule for this request cannot be replaced during a retry.

Action: None
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01072: Metadata schedule and adhoc schedule were specified. Only one schedule can be used.

Cause: A metadata schedule and an adhoc schedule were specified for an operation. Only one schedule should be specified.

Action: Retry the operation with only one schedule
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01073: Failed to open runtime service: {0}. {1}

Cause: An error occurred opening the RuntimeService handle

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01074: Failed to open runtime service due to resource error. {0}

Cause: A resource error occurred opening the RuntimeService handle.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01075: Cannot delete execution group, {0}, because active instances exist.

Cause: A execution group must not be deleted when active instances exist in its cluster.

Action: Use only when the cluster associated with the execution group no longer exists.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01076: Execution group {0} is already being deleted.

Cause: The execution group is already being deleted.

Action: Wait for first deletion to complete.
Level: 1

Type: WARNING

Impact: Programmatic

ESS-01077: Failed to get async request information for message {0}.

Cause: Failed to retrieve information for web service asynchronous callback.

Action: Check the logs.
Level: 1

Type: WARNING

Impact: Other

ESS-01078: Request {0} is required to be asynchronous for this operation.

Cause: This operation cannot be executed on a synchronous request.

Action: Do not invoke the operation on this request.
Level: 1

Type: WARNING

Impact: Other

ESS-01079: Error attempting to access request information.

Cause: An error occurred attempting to access request information.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-01080: Failed to persist request information.

Cause: An error occurred attempting to persist request information to the runtime store.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-01081: Failed to persist request parameter {0}, scope {1}.

Cause: An error occurred attempting to store a request parameter.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-01082: Failed to persist read-only constraint for parameter {0}.

Cause: An error occurred attempting to store parameter read-only constraint.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-01083: Error attempting to retrieve parameters for request {0}.

Cause: An error occurred attempting to retrieve request parameters.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-01084: Error attempting to update parameter, {0}, for request {1}.

Cause: An error occurred attempting to update a request parameter.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-01085: Failed to add parameter {0}, scope {1}, for request {2}.

Cause: An error occurred attempting to add a request parameter.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-01086: Operation not supported for scoped parameter, {0}.

Cause: A scoped parameter was specified for an operation that is not supported for scoped parameter.

Action: None
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01087: Failed to convert Document to byte sequence.

Cause: An error occurred converting a Document to byte sequence.

Action: None
Level: 1

Type: ERROR

Impact: Other

ESS-01088: Failed to convert byte sequence to Document.

Cause: An error occurred converting a byte sequence to a Document.

Action: None
Level: 1

Type: ERROR

Impact: Other

ESS-01089: Failed to get storable value for parameter, {0}.

Cause: An error occurred converting a parameter value to its stored representation.

Action: None
Level: 1

Type: ERROR

Impact: Other

ESS-01090: Failed to get typed value for parameter, {0}, data type, {1}.

Cause: An error occurred converting a parameter value from its stored representation to a typed value.

Action: None
Level: 1

Type: ERROR

Impact: Other

ESS-01091: Unable to obtain incompatibility value for property, {0}.

Cause: Unable to materialize an incompatibility value for the specified property.

Action: Review the causeBy exception chain to determine the specific failure.
Level: 1

Type: WARNING

Impact: Programmatic

ESS-01092: Incompatibility conflict detected between request {0} and parent request {1} for incompatibility {2}.

Cause: Incompatibility conflict detected between a JobSet step request and a JobSet request of its parent chain. An incompatibility lock for that incompatibility will not be acquired for the step request.

Action: None
Level: 1

Type: WARNING

Impact: Other

ESS-01093: Number of acquired request incompatibilities ({0}) does not match number of incompatibility locks ({1}) for request {2}.

Cause: Runtime service system failure.

Action: Review the log file for underlying causes.
Level: 1

Type: ERROR

Impact: Other

ESS-01094: Error attempting to process getCompletionStatus call since another getCompletionStatus call with message id {0} is pending for reply.

Cause: An error occured attempting to process getCompletionStatus call since another getCompletionStatus call with messageid {0} is pending for reply.

Action: Attach different ws message id or wait for the previous call finished before submit getCompletionStatus call.
Level: 1

Type: ERROR

Impact: Other

ESS-01095: Unable to find ess hosting app with logical application name {0}.

Cause: Unable to find ess hosting app with logical application name {0}.

Action: Specify a correct parameter of application or deploy the ess hosting app with expected logical application name.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01096: Query result handle is null.

Cause: The value of the query result handle argument is null.

Action: Specify an argument value that is not null.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01097: Request, {0}, is not of expected type, {1}.

Cause: The request was found in ESS runtime storage but was not of the expected execution type.

Action: Specify a request identifier for a request of the correct execution type.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01098: No request is found for id {0} {1}

Cause: A request was not found in ESS runtime storage corresponding to the indicated request identifier.

Action: Specify a request identifier for an existing request.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01099: An error occured invoking the RuntimeService MBean. {0}

Cause: An error occurred invoking the RuntimeService MBean.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01100: Error retrieving details about Oracle Scheduler job {0} for request {1}.

Cause: An error occurred while trying to retrieve details about the Oracle Scheduler job associated with an ESS request identifier.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01101: Error retrieving the OUTPUT_LIST for parallel children of request {0}.

Cause: An error occurred while trying to retrieve the OUTPUT_LIST for parallel child requests for an ESS request identifier.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01102: Failed to register application, {0}, with instance {1}. {2}

Cause: Application registration failed with ESS.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

ESS-01103: Failed to unregister all applications for instance {0}. {1}

Cause: Application deregistration failed with ESS.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

ESS-01104: Failed to unregister application, {0}, for instance {1}. {2}

Cause: Application deregistration failed with ESS.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

ESS-01105: Failed to check in instance {0}. {1}

Cause: Registration update of ESS instance failed.

Action: Check that database is running and data source is correct.
Level: 1

Type: ERROR

Impact: Other

ESS-01106: Failed to clear checkin entry for instance {0}. {1}

Cause: Unregistration of ESS instance failed.

Action: Check that database is running and data source is correct.
Level: 1

Type: ERROR

Impact: Other

ESS-01107: Failed to remove timed out instance registrations. {0}

Cause: Unregistration of ESS timed-out instances failed.

Action: Check that database is running and data source is correct.
Level: 1

Type: ERROR

Impact: Other

ESS-01108: Failed to fetch elements from wait queue. {0}.

Cause: An error occurred attempting to fetch elements from the wait queue.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-01109: Failed to access wait queue element for request {0}. {1}

Cause: An error occurred attempting to access a wait queue element.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-01110: Failed to lock wait queue element for request {0}. {1}

Cause: Failed to obtain a lock on the wait queue element for a request.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-01111: Failed to insert wait queue element for request {0}. {1}

Cause: An error occurred while attempting to add an element to the wait queue.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-01112: Failed to delete wait queue element for request {0}. {1}

Cause: An error occurred while attempting to remove an element from the wait queue.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-01113: Failed to hold wait queue element for request {0}. {1}

Cause: An error occurred attempting to hold the wait queue element for a request.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-01114: Failed to release wait queue element for request {0}. {1}

Cause: An error occurred attempting to release the wait queue element for a request.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-01115: Failed to undefer wait queue element for request {0}. {1}

Cause: An error occurred attempting to undefer the wait queue element for a request.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-01116: Query field name, {0}, is not a valid name.

Cause: A query filter was specified with an unknown query field.

Action: Remove that query field from the filter, or specify a known name for the query field.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01117: Value for query field, {0}, has an unsupported data type: {1}

Cause: A query filter was specified in which the value for a query field has an unsupported data type.

Action: Specify a query value whose data type is a supported type.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01118: Query field, {0}, has a null value which is not supported for the {1} operator.

Cause: A query filter was specified with a field that has a null value and a comparator that does not support a null value. A null query value requires an EQUALS or NOT_EQUALS comparator.

Action: Specify a non-null value for that query field, or specify an EQUALS or NOT_EQUALS comparator.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01119: Query field, {0}, has a value with a data type, {1}, that is not supported for the {2} comparator.

Cause: A query filter was specified with a field that has a value whose data type is not supported for the specified comparator.

Action: Specify a query value whose data type is supported by the comparator being used.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01120: Query field, {0}, does not support the {1} comparator.

Cause: A query filter was specified with a field that does not support the specified comparator.

Action: Specify a comparator that is supported by that query field.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01121: Failed to retrieve field {0}.

Cause: A failure occurred while retrieving the specified field.

Action: Check that database is running and data source is correct.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01122: Error attempting to access information for incompatibility {0} for request {1}.

Cause: An error occurred attempting to access request incompatibility information.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01123: Error attempting to update information for incompatibility {0} for request {1}.

Cause: An error occurred attempting to update request incompatibility information.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01124: Error attempting to add information for incompatibility {0} for request {1}.

Cause: An error occurred attempting to add request incompatibility information.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01125: Size of request parameter {0} used for incompatibility {1} is too large.

Cause: The value for a request parameter that would be used for an Incompatibility is too large.

Action: Use a smaller value for the parameter value.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01126: Application {0} is active in more than one group.

Cause: An application with the same name is already a member of another ESS group.

Action: Redeploy the current application with a unique deployment name.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01127: Application {0} is not active in any ESS instance.

Cause: The application could not be found in the current ESS group.

Action: Ensure the application is deployed and running in the correct ESS group.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01128: Application with deployed name {0} exists with multiple logical names.

Cause: An application with the same deployment name but different logical name is already a member of this ESS group.

Action: Redploy this application with a unique deployment name. If this application is the same application as the conflicting app, then change the logical name to match.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01129: Application with logical name {0} was not found.

Cause: The application is not a member of this ESS group.

Action: Ensure the application is deployed and running in the correct ESS group.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01130: Application with logical name {0} exists with multiple deployed names.

Cause: An application with the same logical name but different deployment name is already a member of this ESS group.

Action: Redploy this application with a unique logical application name. If this application is the same application as the conflicting app, then change the deployment name to match.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01131: Application with deployed name {0} was not found.

Cause: The application is not a member of this ESS group.

Action: Ensure the application is deployed and running in the correct ESS group.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01132: Unable to access processor bindings. {0}

Cause: Processor bindings in the runtime store could not be accessed.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-01133: Processor binding {0} could not be found.

Cause: Processor binding could not be found.

Action: Check that you specified the correct binding name.
Level: 1

Type: ERROR

Impact: Other

ESS-01134: Processor binding {0} already exists.

Cause: Processor binding already exists.

Action: Change the name of the binding.
Level: 1

Type: ERROR

Impact: Other

ESS-01135: Unable to notify server of processor bindings change. {0}

Cause: Unable to notify server of bindings change.

Action: Check that database is running and data source is correct.
Level: 1

Type: ERROR

Impact: Other

ESS-01136: Unable to access processor bindings change notification. {0}

Cause: Unable to access bindings change notification.

Action: Check that database is running and data source is correct.
Level: 1

Type: ERROR

Impact: Other

ESS-01137: Unable to notify server to refresh selector. {0}

Cause: Unable to notify server to refresh selector.

Action: Check that database is running and data source is correct.
Level: 1

Type: ERROR

Impact: Other

ESS-01138: Unable to access refresh selector notification. {0}

Cause: Unable to access refresh selector notification.

Action: Check that database is running and data source is correct.
Level: 1

Type: ERROR

Impact: Other

ESS-01139: Value, {1}, for query field, {0}, is invalid.

Cause: A query filter was specified in which the value for a query field was invalid.

Action: Specify a valid query value.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01140: Error accessing async throttle information for ({0}, {1}). {2}

Cause: An error occurred while accessing runtime async throttle information.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-01141: Async throttle already exists for Workshift = {0}. {1}

Cause: The throttle is already configured for the Workshift.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-01142: Async throttle not found for Workshift = {0}.

Cause: The throttle was not found for the Workshift.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-01143: Failed to process filter {0}.

Cause: Filter evaluation failed.

Action: Correct the invalid Filter.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01144: Failed to retrieve timed out instance registrations. {0}

Cause: Query of ESS timed out registrationsinstance failed.

Action: Check that database is running and data source is correct.
Level: 1

Type: WARNING

Impact: Other

ESS-01145: Failed to lock instance {0}. {1}

Cause: Locking the ESS instance registration failed.

Action: Check that database is running and data source is correct.
Level: 1

Type: WARNING

Impact: Other

ESS-01146: Error accessing runtime async throttle information. {0}

Cause: An error occurred while accessing the throttle configuration.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-01147: Failed to get DiagnosticState for instance {0}. {1}

Cause: Failed to get DiagnosticState for the instance.

Action: None
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-01148: Failed to clear registrations for execution group {0}, isolation group {1}. {2}

Cause: Failed to clear registrations for execution group.

Action: None. Registrations will be automatically retried
Level: 1

Type: WARNING

Impact: Other

ESS-01149: Error accessing unthrottled work assignments ({0}). {1}

Cause: An error occurred while accessing the unthrottled work assignments.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-01150: Unable to delete workshift with outstanding async workers: {0}

Cause: A workshift that has outstanding async workers not be deleted.

Action: Wait until all async workers have completed and then delete the workshift.
Level: 1

Type: WARNING

Impact: Other

ESS-01151: Error accessing async limit information for workshift = {0}. {1}

Cause: An error occurred while accessing runtime async limit information.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-01152: Error accessing async allocation information for work assignment = {0}. {2}

Cause: An error occurred accessing runtime async allocation information.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-01153: Failed to add incompatibility lock {0}.

Cause: An error occurred attempting to add incompatibility lock information.

Action: Review the causeBy exception chain to determine the specific failure.
Level: 1

Type: WARNING

Impact: Programmatic

ESS-01154: Failed to delete incompatibility lock {0}.

Cause: An error occurred attempting to delete incompatibility lock information.

Action: Review the causeBy exception chain to determine the specific failure.
Level: 1

Type: WARNING

Impact: Programmatic

ESS-01155: Failed to lock incompatibility lock {0}.

Cause: An error occurred attempting to delete incompatibility lock information.

Action: Review the causeBy exception chain to determine the specific failure.
Level: 1

Type: WARNING

Impact: Programmatic

ESS-01156: Failed to update reference count for incompatibility lock {0}.

Cause: An error occurred attempting to delete incompatibility lock information.

Action: Review the causeBy exception chain to determine the specific failure.
Level: 1

Type: WARNING

Impact: Programmatic

ESS-01157: Failed to retrieve incompatibility locks for request {0}.

Cause: An error occurred attempting to retrieve incompatibility locks held by a request.

Action: Review the causeBy exception chain to determine the specific failure.
Level: 1

Type: WARNING

Impact: Programmatic

ESS-01158: Failed to lock incompatibility locks for request {0}.

Cause: An error occurred attempting to lock any incompatibility locks held by a request.

Action: Review the causeBy exception chain to determine the specific failure.
Level: 1

Type: WARNING

Impact: Programmatic

ESS-01159: Failed to retrieve request incompatibility for request {0}.

Cause: An error occurred attempting to retrieve request incompatibility information.

Action: Review the causeBy exception chain to determine the specific failure.
Level: 1

Type: WARNING

Impact: Programmatic

ESS-01160: Failed to lock request incompatibility for request {0}.

Cause: An error occurred attempting to lock request incompatibility information.

Action: Review the causeBy exception chain to determine the specific failure.
Level: 1

Type: WARNING

Impact: Programmatic

ESS-01161: Failed to retrieve request incompatibility.

Cause: An error occurred attempting to retrieve request incompatibility information.

Action: Review the causeBy exception chain to determine the specific failure.
Level: 1

Type: WARNING

Impact: Programmatic

ESS-01162: Failed to lock request incompatibility.

Cause: An error occurred attempting to lock request incompatibility information.

Action: Review the causeBy exception chain to determine the specific failure.
Level: 1

Type: WARNING

Impact: Programmatic

ESS-01163: Failed to add reference for incompatibility {0}, job definition {1}, request {2}.

Cause: An error occurred attempting to add job incompatibility reference.

Action: Review the causeBy exception chain to determine the specific failure.
Level: 1

Type: WARNING

Impact: Programmatic

ESS-01164: Reference already exists for incompatibility {0}, job definition {1}, request {2}.

Cause: Job incompatibility reference already exists.

Action: None
Level: 1

Type: WARNING

Impact: Programmatic

ESS-01165: Failed to retrieve incompatibility metadata from runtime store for job definition {0}, request {1}.

Cause: An error occurred attempting to retrieve incompatibility metadata from runtime store for a job definition.

Action: Review the causeBy exception chain to determine the specific failure.
Level: 1

Type: WARNING

Impact: Programmatic

ESS-01166: Failed to query registration table.

Cause: An error occurred while querying the registration table.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

ESS-01167: Failed to cache metadata in runtime store for request {0}. {1}.

Cause: An error occurred while saving metadata in the ESS runtime store.

Action: Review the log file to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-01168: Binding mode conflict for {0}

Cause: Binding mode conflict. Work assignment may be bound in either standard or exclusive mode, but not in both modes on two different servers in the same processing group.

Action: Use the correct binding mode.
Level: 1

Type: WARNING

Impact: Other

ESS-01169: Workshift does not exist {0}

Cause: The workshift does not exist.

Action: Ensure you are using the correct workshift name, and that the workshift exists.
Level: 1

Type: WARNING

Impact: Other

ESS-01196: Unable to get the current time from the database.

Cause: Unable to get the current time from the database.

Action: Review the log file for possible underlying causes.
Level: 1

Type: WARNING

Impact: Programmatic

ESS-01197: Unable to release incompatibility locks for request {0}.

Cause: Unable to release one or more incompatibility locks for the request at this time.

Action: Review the log file for possible underlying causes.
Level: 1

Type: WARNING

Impact: Programmatic

ESS-01198: Unable to obtain configuration information for application {0}.

Cause: Unable to retrieve configuration information for application.

Action: None
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01199: JobSet steps would have mixed request modes: {0}

Cause: The steps for a JobSet are not homogeneous in regard to the resolved request mode.

Action: None
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01200: Error attempting to insert {0} work unit for request {1}.

Cause: An error occurred inserting a work unit into the persistent store.

Action: Review the log file to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-01201: Error attempting to insert {0} work unit.

Cause: An error occurred inserting a work unit into the persistent store.

Action: Review the log file to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-01202: Failed to update work stage for work {0}.

Cause: An error occurred updating the work stage of a work unit.

Action: Review the log file to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-01203: Failed to delete work for request {0}.

Cause: An error occurred deleting work units.

Action: Review the log file to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-01204: Failed to delete work {0} for request {1}.

Cause: An error occurred deleting work units.

Action: Review the log file to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-01205: Failed to delete work unit {0}.

Cause: An error occurred deleting work units.

Action: Review the log file to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-01206: Failed to check in work unit {0} for request {1}.

Cause: An error occurred checking in work units.

Action: Review the log file to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-01207: Failed to check in work unit {0}.

Cause: An error occurred checking in work units.

Action: Review the log file to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-01208: Failed to undefer DeleteProcessGroup work for execution group {0}.

Cause: An error occurred undeferring a DeleteProcessGroupEvent.

Action: Review the log file to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-01209: Failed to update information for work {0} for request {1}.

Cause: An error occurred updating a work unit.

Action: Review the log file to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-01210: Failed to undefer work for request {0}.

Cause: An error occurred undeferring a work unit.

Action: Review the log file to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-01211: Failed to check in work for instance {0}.

Cause: An error occurred checking in all the work units for an ESS instance.

Action: Review the log file to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-01212: Error retrieving available work units.

Cause: Error occurred while retrieving work units to process.

Action: Review the log file for runtime cause.
Level: 1

Type: WARNING

Impact: Other

ESS-01213: Failed to retrieve work unit {0}.

Cause: Error occurred while retrieving a work unit to process.

Action: Review the log file for runtime cause.
Level: 1

Type: WARNING

Impact: Other

ESS-01214: Failed to determine if work {0} is checked out to instance {1}.

Cause: Failed to determine if the work is checked out to this instance.

Action: Review the log file for runtime cause.
Level: 1

Type: WARNING

Impact: Other

ESS-01215: Error occurred querying check out work units for instance {0}.

Cause: Failed to determine the work units checked out to the instance.

Action: Review the log file for runtime cause.
Level: 1

Type: WARNING

Impact: Other

ESS-01216: Failed to access work unit {0}.

Cause: Error occurred attempting to access work unit.

Action: Review the log file for runtime cause.
Level: 1

Type: WARNING

Impact: Other

ESS-01217: Error waiting for work.

Cause: Error occurred while waiting for new work.

Action: Review the log file for runtime cause.
Level: 1

Type: WARNING

Impact: Other

ESS-01218: Error waiting for work. Operation returned: {0}.

Cause: Operation used to work for new work returned the specified result.

Action: Review the log file for runtime cause.
Level: 1

Type: WARNING

Impact: Other

ESS-01219: Work unit {0} is not checked out to instance {1}.

Cause: The work unit is not checked out to the specified instance.

Action: None
Level: 1

Type: WARNING

Impact: Other

ESS-01220: Failed to lock work unit {0} by instance {1}.

Cause: Failed to lock the work unit by the specified instance.

Action: None
Level: 1

Type: WARNING

Impact: Other

ESS-01250: Error retrieving available event work.

Cause: Error occurred while retrieving event work to process.

Action: Review the log file for runtime cause.
Level: 1

Type: WARNING

Impact: Other

ESS-01251: Failed to access event work {0}.

Cause: Error occurred attempting to access event work.

Action: Review the log file for runtime cause.
Level: 1

Type: WARNING

Impact: Other

ESS-01252: Failed to update event work {0}.

Cause: Error occurred attempting to update event work.

Action: Review the log file for runtime cause.
Level: 1

Type: WARNING

Impact: Other

ESS-01253: Failed to delete event work {0}.

Cause: Error occurred attempting to delete event work.

Action: Review the log file for runtime cause.
Level: 1

Type: WARNING

Impact: Other

ESS-01254: Failed to delete event work for request {0}.

Cause: Error occurred attempting to delete event work for a request.

Action: Review the log file for runtime cause.
Level: 1

Type: WARNING

Impact: Other

ESS-01255: Failed to check in event work {0}.

Cause: Error occurred attempting to check in event work.

Action: Review the log file for runtime cause.
Level: 1

Type: WARNING

Impact: Other

ESS-01256: Failed to check in event work for instance {0}.

Cause: Error occurred attempting to check in event work for an instance.

Action: Review the log file for runtime cause.
Level: 1

Type: WARNING

Impact: Other

ESS-01257: Failed to add event. Event name: {0}, request: {1}.

Cause: Error occurred attempting to insert event work.

Action: Review the log file for runtime cause.
Level: 1

Type: WARNING

Impact: Other

ESS-01258: Event work not found: {0}.

Cause: The specified event work was not found.

Action: None
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-01259: Error waiting for event work.

Cause: Error occurred while waiting for new event work.

Action: Review the log file for runtime cause.
Level: 1

Type: WARNING

Impact: Other

ESS-01260: Error waiting for event work. Operation returned: {0}.

Cause: Operation used to work for new event work returned the specified result.

Action: Review the log file for runtime cause.
Level: 1

Type: WARNING

Impact: Other

ESS-01262: Event work {0} is not checked out to instance {1}.

Cause: The event work is not checked out to a specific instance.

Action: None
Level: 1

Type: WARNING

Impact: Other

ESS-01263: Invalid event listener class, {0}.

Cause: The class name configured for the request listener is not a valid event listener class.

Action: None
Level: 1

Type: WARNING

Impact: Other

ESS-01264: Unable to instantiate event listener for class, {0}.

Cause: Unable to instantiate an instance of an event listener class name.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-01265: Unable to retrieve information needed to dispatch an event for request {0}.

Cause: Failed to retrieve information needed to dispatch an event.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-01266: Failed to lock event work {0} by instance {1}.

Cause: Failed to lock the event work by the specified instance.

Action: None
Level: 1

Type: WARNING

Impact: Other

ESS-01300: Unable to access content store for request {0}, file {1}. {2}.

Cause: Failed to access the content store.

Action: Review the log file for runtime cause.
Level: 1

Type: WARNING

Impact: Other

ESS-01301: Failed to create content for request {0}, content name {1}. {2}.

Cause: Failed to create content for the request.

Action: Review the log file for runtime cause.
Level: 1

Type: WARNING

Impact: Other

ESS-01302: Failed to update content for request {0}, content name {1}. {2}.

Cause: Failed to update content for the request.

Action: Review the log file for runtime cause.
Level: 1

Type: WARNING

Impact: Other

ESS-01303: Failed to import file to content store for request {0}, file {1}. {2}.

Cause: Failed to import file to the content store for the request.

Action: Review the log file for runtime cause.
Level: 1

Type: WARNING

Impact: Other

ESS-01304: Failed to export content for request {0}, content name {1}. {2}.

Cause: Failed to export content for the request.

Action: Review the log file for runtime cause.
Level: 1

Type: WARNING

Impact: Other

ESS-01305: Failed to delete content for request {0}, content name {1}. {2}.

Cause: Failed to delete content for the request.

Action: Review the log file for runtime cause.
Level: 1

Type: WARNING

Impact: Other

ESS-01306: Failed to delete all content for request {0}. {1}.

Cause: Failed to delete all content for the request.

Action: Review the log file for runtime cause.
Level: 1

Type: WARNING

Impact: Other

ESS-01307: Invalid write to output content for request {0}, content name {1}.

Cause: Invalid write to content due to incorrect content type.

Action: Ensure the type of data you are writing is compatible with the content type.
Level: 1

Type: WARNING

Impact: Other

ESS-01308: The content does not exist for request {0}, content name {1}.

Cause: The content does not exist for the request.

Action: Ensure you are using the correct content name.
Level: 1

Type: WARNING

Impact: Other

ESS-01309: Invalid content handle.

Cause: The content handle is invalid.

Action: Re-open the content and use the valid handle.
Level: 1

Type: WARNING

Impact: Other

ESS-01310: The file does not exist for request {0}, file name {1}.

Cause: The file does not exist for the request.

Action: Ensure you are using the correct file name.
Level: 1

Type: WARNING

Impact: Other

ESS-01312: Failed to close the output file for request {0}, file name {1}. {2}.

Cause: Failed to close the output file for the request.

Action: Review the log file for runtime cause.
Level: 1

Type: WARNING

Impact: Other

ESS-01313: Invalid directory for request {0}, directory {1}.

Cause: The directory is invalid for the request.

Action: Ensure you are using the correct file name.
Level: 1

Type: WARNING

Impact: Other

ESS-01314: Incompatible content operation for request {0}, content name {1}.

Cause: The operation is incompatible with the existing content type.

Action: It is not allowed to export output content that was not imported. Updating existing output content using the API requires using the same content type.
Level: 1

Type: WARNING

Impact: Other

ESS-01315: Error creating directory for request {0}, directory {1}.

Cause: Failed to create the request directory.

Action: Ensure that RequestFileDirectory is configured correctly for the application and that the directory is writeable.
Level: 1

Type: WARNING

Impact: Other

ESS-01316: Error exporting output content for request {0}, status {1}.

Cause: Failed to export output content to the request output directory.

Action: Ensure that RequestFileDirectory is configured correctly for the application and that the directory is writeable. Check the log for errors.
Level: 1

Type: WARNING

Impact: Other

ESS-01317: Error importing output content for request {0}, status {1}, directory {2}. {3}

Cause: Failed to import output files from the request output directory.

Action: Check the log for errors.
Level: 1

Type: WARNING

Impact: Other

ESS-01318: Failed to import the log for request {0}, log file {1}. {2}.

Cause: Failed to import the request log.

Action: Review the log file for runtime cause.
Level: 1

Type: WARNING

Impact: Other

ESS-01319: Invalid content handle mode for request {0}, content {1}.

Cause: The content handle is opened in the wrong mode for the operation being performed. The content must be opened in read for fetching and write for importing.

Action: Re-open the content in the correct mode for the operation being performed.
Level: 1

Type: WARNING

Impact: Other

ESS-01320: Invalid RequestFileDirectory {0} for application {1}.

Cause: The application has an invalid RequestFileDirectory configured.

Action: Configure a valid RequestFileDirectory for the application.
Level: 1

Type: ERROR

Impact: Other

ESS-01321: Error deleting files for request {0}, directory {1}.

Cause: Failed to delete files from the request work directory.

Action: Manually delete the files from the file system.
Level: 1

Type: WARNING

Impact: Other

ESS-01322: Error preserving log or output files for request {0}. {1}

Cause: Failed to preserve log or output files from the request work directory. This may be due to a problem with the directory or a previous version of the output file may already exist.

Action: No action. The files have been removed.
Level: 1

Type: WARNING

Impact: Other

ESS-01500: Dispatcher cannot be started while in {0} state.

Cause: Attempted to start the dispatcher when it is in a state for which the operation is not allowed.

Action: Retry the operation when the dispatcher state is STOPPED.
Level: 1

Type: ERROR

Impact: Other

ESS-01501: Dispatcher cannot be stopped while in {0} state.

Cause: Attempted to stop the dispatcher when it is in a state for which the operation is not allowed.

Action: Retry the operation when the dispatcher state is STARTING or RUNNING.
Level: 1

Type: ERROR

Impact: Other

ESS-01502: Processor cannot be started while in {0} state.

Cause: Attempted to start the processor when it is in a state for which the operation is not allowed.

Action: Retry the operation when the processor state is STOPPED.
Level: 1

Type: ERROR

Impact: Other

ESS-01503: Processor cannot be stopped while in {0} state.

Cause: Attempted to stop the processor when it is in a state for which the operation is not allowed.

Action: Retry the operation when the processor state is STARTING or RUNNING.
Level: 1

Type: ERROR

Impact: Other

ESS-01504: Cannot add endpoint {0} for application {1} because endpoint {2} already exists for application {3}.

Cause: The endpoint to add conflicts with an already existing endpoint.

Action: Modify the endpoint name.
Level: 1

Type: ERROR

Impact: Deployment

ESS-01505: Failed to retrieve information for request {0}.

Cause: Failed to retrieve runtime information for a request.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-01506: Unable to create diagnostic incident. {0}

Cause: Failed to create diagnostic incident.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-01507: Unable to register diagnostic dumps or rules. {0}

Cause: Failed to register diagnostic dumps or rules.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-01508: Unable to unregister diagnostic dumps or rules. {0}

Cause: Failed to unregister diagnostic dumps or rules.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-01509: Unable to create the diagnostic dump {0}. {1}

Cause: Failed to create the diagnostic dump.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-01601: JobSet request {0} completed with an invalid final state {1}.

Cause: A JobSet request has been marked as completed, but has an unexpected final state.

Action: Review the log file for errors pertaining to the request.
Level: 1

Type: ERROR

Impact: Other

ESS-01602: First step is not defined in serial JobSet: {0}.

Cause: Cannot process a JobSet request due to invalid JobSet definition. The first step of a serial JobSet is not defined.

Action: None
Level: 1

Type: ERROR

Impact: Other

ESS-01603: Error dispatching subrequests for parent request {0}.

Cause: An error occurred while attempting to dispatch subrequests for a parent request in PAUSED state.

Action: Review the log file to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-01604: Failed to create {0} work unit for request {1}.

Cause: Unable to create the specified work unit for a request.

Action: Review the log file to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-01605: Failed to create event, {0}, for request {1}.

Cause: An error occurred while attempting to create an event for a request.

Action: Review the log file to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-01606: Failed to mark request {0} as completed.

Cause: An error prevented the request from being marked completed

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-01607: Request {0} cannot be marked complete. State is {1}, process phase is {2}.

Cause: The request state and/or process phase prevents a request from being completed.

Action: None
Level: 1

Type: WARNING

Impact: Other

ESS-01700: Unrecognized request type : {0}.

Cause: The job type used for the request is not supported.

Action: Correct the job type definition.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01701: Unable to instantiate executable wrapper for execution type {0}.

Cause: Unable to instantiate wrapper class used to process the request.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Installation

ESS-01702: Unable to instantiate pre-process callback handler for request {0} using class name, {1}.

Cause: Failed to instantiate an object for the pre-process callback handler class associated with a request.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01703: Unable to instantiate post-process callback handler for request {0} using class name, {1}.

Cause: Failed to instantiate an object for the post-process callback handler class associated with a request.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01704: Error occurred at initiate stage during execution of request {0}. {1}

Cause: An error occurred during the initiate stage of a request execution.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01705: Error occurred at finalize stage during execution of request {0}. {1}

Cause: An error occurred during the finalize stage of a request execution.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01706: Invalid execution result code, {0}, for request {1}.

Cause: A REQUEST_FINALIZATION event contained an unknown result code.

Action: This indicates an internal error. Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01707: Unable to instantiate Executable for Java request {0} using class name, {1}.

Cause: Failed to instantiate Executable object for a Java request.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01708: Database job for request {0} ended with error: {1}.

Cause: Execution of a SQL request has ended with a error.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01709: Database job for request {0} ended with warning: {1}.

Cause: Execution of a SQL request has ended with a warning.

Action: None.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01710: Database job for request {0} was cancelled.

Cause: Execution of a SQL request has been cancelled.

Action: None.
Level: 1

Type: NOTIFICATION

Impact: Programmatic

ESS-01711: Database job for request {0} was paused. Paused state value: {1}.

Cause: Execution of a SQL job request has been paused to allow one or more sub-requests to execute.

Action: None. The execution of the paused request will be resumed once the sub-requests have completed.
Level: 1

Type: NOTIFICATION

Impact: Programmatic

ESS-01712: Failed to create database job for request {0}.

Cause: An error occurred trying to create an Oracle Scheduler job used to execute a SQL job request.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-01713: Error cancelling database job for request {0}.

Cause: An error occurred during post-execution clean tasks for an Oracle Scheduler job used to execute a SQL job request.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-01714: Database job for request {0} ended with business error: {1}.

Cause: Execution of a SQL request has ended with a biz error.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01715: Failed to create database job for request {0} using Oracle Scheduler job class {1}.

Cause: An error occurred trying to create an Oracle Scheduler job used to execute a SQL job request with the given Oracle Scheduler job class.

Action: Verify the EXECUTE privilege on the Oracle Scheduler job class has been granted to the ESS schema user. Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-01716: Unable to process JobSet request {0}. JobSet definition has no steps: {1}

Cause: The JobSet definition associated with a JobSet request has no steps.

Action: Review the metadata of the JobSet definition for the specified metadata id.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01900: Error constructing ESS command {0}. {1}

Cause: An error is present in the command format.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

ESS-01901: Unsupported value, {0}, for attribute {1}.

Cause: An unknown value was specified for a parameter.

Action: Specify a valid attribute value.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-01903: Unknown command type {0}. {1}

Cause: An unknown command type was submitted.

Action: None
Level: 1

Type: ERROR

Impact: Other

ESS-01904: Document is not valid for work {0}.

Cause: The command document is invalid for this Enterprise Scheduler server

Action: None. The command will be deferred.
Level: 1

Type: WARNING

Impact: Other

ESS-01905: Attribute {0} value {1} from command document does not match value {2} from command creation.

Cause: The internal command state is inconsistent for the given attribute.

Action: Contact administrator.
Level: 1

Type: WARNING

Impact: Other

ESS-01906: Error retrieving available command work.

Cause: Error occurred while retrieving command work to process.

Action: Review the log file for runtime cause.
Level: 1

Type: WARNING

Impact: Other

ESS-01907: Failed to access command work {0}.

Cause: Error occurred attempting to access command work.

Action: Review the log file for runtime cause.
Level: 1

Type: WARNING

Impact: Other

ESS-01908: Failed to update command work {0}.

Cause: Error occurred attempting to update command work.

Action: Review the log file for runtime cause.
Level: 1

Type: WARNING

Impact: Other

ESS-01909: Failed to delete command work {0}.

Cause: Error occurred attempting to delete command work.

Action: Review the log file for runtime cause.
Level: 1

Type: WARNING

Impact: Other

ESS-01910: Failed to delete command work for request {0}.

Cause: Error occurred attempting to delete command work for a request.

Action: Review the log file for runtime cause.
Level: 1

Type: WARNING

Impact: Other

ESS-01911: Failed to check in command work {0}.

Cause: Error occurred attempting to check in command work.

Action: Review the log file for runtime cause.
Level: 1

Type: WARNING

Impact: Other

ESS-01912: Failed to check in command work for instance {0}.

Cause: Error occurred attempting to check in command work for an instance.

Action: Review the log file for runtime cause.
Level: 1

Type: WARNING

Impact: Other

ESS-01913: Command work not found: {0}.

Cause: The specified command work was not found.

Action: None
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-01914: Command work {0} is not checked out to instance {1}.

Cause: The command work is not checked out to a specific instance.

Action: None
Level: 1

Type: WARNING

Impact: Other

ESS-01915: Failed to lock command work {0} by instance {1}.

Cause: Failed to lock the command work by the specified instance.

Action: None
Level: 1

Type: WARNING

Impact: Other

ESS-01980: Batch delete initialization failed.

Cause: An error occurred during initialization of batch delete support.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-01981: Failed to delete request {0}. Reason: {1}

Cause: An error occurred attempting to delete a request.

Action: None
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-01982: Insufficient privileges to delete request {0}.

Cause: Execution user of a batch delete job does not have sufficient privileges to delete the request.

Action: Batch delete job should be submitted only by ESS administrator
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-01983: Error determining requests for batch delete.

Cause: An error occurred attempting to determine requests to delete.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-01984: Error occurred while executing batch delete request {0}. Cause: {1}

Cause: An error occurred during request execution.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-01985: Execution of request {0} was cancelled.

Cause: Request execution was canceled.

Action: None
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-01987: Runtime store error during batch delete.

Cause: Runtime store error occurred during batch delete opearation.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-01988: Failed to lock request for batch delete.

Cause: Unable to lock one or more requests during batch delete operation

Action: None
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-01989: Batch delete request {0} failed to delete request {1}. Reason: {2}

Cause: Batch delete job failed to delete the specified request.

Action: Review log file to determine the reason.
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-02001: User {0} does not have execute permission on metadata object {1}. Request {2} execution is aborted.

Cause: User {0} does not have execute permission on metadata object {1}. Request {2} execution is aborted.

Action: Check the policy assignment..
Level: 1

Type: ERROR

Impact: Other

ESS-02002: User {0} does not have sufficient privilege to perform operation {1}.

Cause: User {0} does not have sufficient privilege to perform operation {1}.

Action: Grant the policy to the user {0}..
Level: 1

Type: ERROR

Impact: Other

ESS-02003: User {0} does not have sufficient privilege to perform operation {1} on request {2}.

Cause: User {0} does not have sufficient privilege to perform operation {1} on request {2}.

Action: Grant the policy to the user {0}..
Level: 1

Type: ERROR

Impact: Other

ESS-02004: User or appid {0} is not a valid entry in the idstore configured in jps-config.xml.

Cause: {0} can not be authenticated.

Action: Check the user settting.
Level: 1

Type: ERROR

Impact: Other

ESS-02005: User {0} does not have {1} privilege on metadata object {2}. Request {3} validation failed.

Cause: User {0} does not have {1} privilege on metadata object {2}. Request {3} validation failed.

Action: Check the policy assignment..
Level: 1

Type: ERROR

Impact: Other

ESS-02006: User {0} does not have sufficient privilege to perform operation {1} on job set {2}, failed steps are {3}.

Cause: User {0} does not have sufficient privilege to perform operation {1} on jobset {2}, failed steps are {3}.

Action: Grant the policy to the user {0}..
Level: 1

Type: ERROR

Impact: Other

ESS-02007: User or appid {0} whom job {1} runs is not a valid entry in the idstore configured in jps-config.xml.

Cause: The user or appid {0} is not a valid identity or can not be authenticated.

Action: Check your metadata definition.
Level: 1

Type: ERROR

Impact: Other

ESS-02200: Mismatched request handles for request {0}.

Cause: The request may have been retried.

Action: Update with request execution context from new execution if desired.
Level: 1

Type: ERROR

Impact: Other

ESS-02220: Failed to deliver web service callback for message {0} for request {1}.

Cause: The web service asynchronous callback message could not be delivered.

Action: The action may be retried. Check the log files.
Level: 1

Type: WARNING

Impact: Other

ESS-05000: Error occurred. {0}

Cause: Enterprise Scheduler Service encountered an error.

Action: Review the log file for indications of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-05010: Request {0} not found.

Cause: Request with the given request id can not be found in the database.

Action: None
Level: 1

Type: ERROR

Impact: Other

ESS-05011: Request {0} set to {1} state.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-05012: Request {0} set to {2} state. Previous state was {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-05013: Request {0}. Process phase {1} not in valid phases {2}.

Cause: The process phase of the request is inconsistent with its current status.

Action: None
Level: 1

Type: ERROR

Impact: Other

ESS-05021: Failed to begin transaction.

Cause: Being of a user transaction failed.

Action: Review the log file for runtime cause.
Level: 1

Type: WARNING

Impact: Other

ESS-05022: Failed to commit transaction.

Cause: Failed to commit the transaction.

Action: Review the log file for runtime cause.
Level: 1

Type: WARNING

Impact: Other

ESS-05023: Failed to rollback transaction.

Cause: Failed to rollback the transaction.

Action: Review the log file for runtime cause.
Level: 1

Type: ERROR

Impact: Other

ESS-05024: Failed to set transaction timeout.

Cause: Failed to set transaction timeout.

Action: Review the log file for runtime cause.
Level: 1

Type: WARNING

Impact: Other

ESS-05038: Failed to find JNDI resource for {0}.

Cause: Failed to perform a JNDI lookup for a given resource name.

Action: Verify the configuration for the resource.
Level: 1

Type: ERROR

Impact: Configuration

ESS-05039: Error occurred closing JNDI naming context.

Cause: An error occurred while trying to close a JNDI naming context.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-05043: Failed to commit SQL transaction.

Cause: An error occurred trying to commit database transaction.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-05044: Failed to rollback SQL transaction.

Cause: An error occurred trying to rollback database transaction.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-05045: Error using SQL ResultSet. {0}

Cause: An error occurred while using an SQL ResultSet.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-05046: Failed to close an SQL ResultSet.

Cause: An error occurred trying to close an SQL ResultSet.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-05047: Failed to close an SQL Statement.

Cause: An error occurred trying to close an SQL Statement.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-05048: Failed to obtain a database connection.

Cause: An error occurred trying to obtain a database connection.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-05049: Failed to close a database connection.

Cause: An error occurred trying to close a database connection.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-05053: Failed to map object of type {0} to CompositeData.

Cause: An error occurred converting an ESS object to a javax.management.openmbean.CompositeData object

Action: Contact Oracle Support Services
Level: 32

Type: INCIDENT_ERROR

Impact: Other

ESS-05054: Failed to map CompositeData object to {0}.

Cause: An error occurred converting a javax.management.openmbean.CompositeData object to an ESS object

Action: Contact Oracle Support Services
Level: 32

Type: INCIDENT_ERROR

Impact: Other

ESS-05055: Illegal state transition from {0} to {1} for request {2}.

Cause: An update event's timing may have tried to change the state after the request has begun a transition to a terminal state.

Action: This warning can be ignored.
Level: 1

Type: ERROR

Impact: Other

ESS-05100: Operator {1} is invalid with query field {0}. Valid operators are: {2}.

Cause: Operator is invalid for the given query field.

Action: Use a valid operator.
Level: 1

Type: WARNING

Impact: Other

ESS-05101: Comparator {1} is invalid with query field {0}. Valid comparators are: {2}.

Cause: Comparator is invalid for the given query field.

Action: Use a valid comparator.
Level: 1

Type: WARNING

Impact: Other

ESS-05102: Value of type {1} is invalid with query field {0}. Valid value types are: {2}.

Cause: Value type is invalid for the given query field.

Action: Use a valid value type.
Level: 1

Type: WARNING

Impact: Other

ESS-05103: Value of type null is invalid with query field {0}.

Cause: Null value type is invalid for the given query field.

Action: Use a valid non-null value type.
Level: 1

Type: WARNING

Impact: Other

ESS-05104: Failed to check in {0} work unit {1} for request {2}. {3}

Cause: The work unit for the given request could not be checked in or deleted.

Action: The work unit operation should be automatically retried, so no action is necessary.
Level: 1

Type: WARNING

Impact: Other

ESS-05105: Metadata of type {0} cannot be customized. Only metadata of the following types can be customized: {1}.

Cause: An invalid metadata type was provided.

Action: Provide a valid customizable metadata type.
Level: 1

Type: WARNING

Impact: Other

ESS-05106: Property {0} cannot be assigned a value of type {1}. Values for property {0} can only have the following types: {2}.

Cause: The data type of the provided property is not valid.

Action: Provide a value with the correct data type.
Level: 1

Type: WARNING

Impact: Other

ESS-05107: An error occurred while parsing the metadata object id string: {0}

Cause: An error occurred while parsing a metadata object id string.

Action: See base exception for detailed underlying cause.
Level: 1

Type: WARNING

Impact: Other

ESS-05108: The user provided metadata type of {0} does not match the metadata type of {1} in the metadata object id string

Cause: The metadata type specified by the user does not match the metadata type specified by the metadata object id string.

Action: Check the metadata repository to ensure the metadata is correct or specify the correct type and try again.
Level: 1

Type: WARNING

Impact: Other

ESS-05109: While performing a metadata query, the following problem was detected with one of the query results: {1} The query will continue but exclude the piece of metadata with name {0}. This may affect the expected query results.

Cause: A problem occurred while processing a result of the metadata query.

Action: Check the piece of metadata causing the problem for any issues and check the health of the metadata respository.
Level: 1

Type: ERROR

Impact: Other

ESS-05110: An error occurred while retrieving the metadata object with name {0} of type {1}.

Cause: A problem occurred while retrieving a piece of metadata.

Action: See the base exception for the cause then check the piece of metadata causing the problem for any issues and check the health of the metadata respository.
Level: 1

Type: ERROR

Impact: Other

ESS-05202: ESS connections.xml {0} property lookup returns null. Please verify adf-domain-config for ESS is set up and configured.

Cause: ESS connections.xml property lookup returns NULL.

Action: Verify adf-domain-config for ESS is set up and configured.
Level: 1

Type: WARNING

Impact: Other

ESS-05203: ESS connections.xml {0} property lookup returns Unresolved EL Expression. Please verify adf-domain-config for ESS is set up and configured.

Cause: ESS connections.xml property lookup returns Unresolved EL Expression.

Action: Verify adf-domain-config for ESS is set up and configured.
Level: 1

Type: WARNING

Impact: Other

ESS-05204: NamingException looking up EssConnection {0}.

Cause: NamingException looking up EssConnection.

Action: Review the log file for attached exceptions to determine the cause.
Level: 1

Type: ERROR

Impact: Other

ESS-05205: Error reading EssConnection Tokens from adf-domain-config.

Cause: Error reading EssConnection Tokens from adf-domain-config.

Action: Review the log file for attached exceptions to determine the cause.
Level: 1

Type: ERROR

Impact: Other

ESS-05206: Error writing EssConnection Tokens to adf-domain-config.

Cause: Error writing EssConnection Tokens to adf-domain-config.

Action: Review the log file for attached exceptions to determine the cause.
Level: 1

Type: ERROR

Impact: Other

ESS-05490: Service MBeans registration failed.

Cause: Service MBeans registration failed.

Action: Review the log file for underlying causes.
Level: 1

Type: WARNING

Impact: Other

ESS-05700: Failed to obtain a metadata service instance. {0}

Cause: Failed to obtain a metadata service instance.

Action: Review the log file for underlying causes.
Level: 1

Type: ERROR

Impact: Other

ESS-05704: An error occured invoking the MetadataService MBean. {0}

Cause: An error occurred invoking the RuntimeService MBean.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-05705: Failed to save the {0} with name {1} in application {2}.

Cause: Failed to save the metadata object.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-05706: {0} with name {1} does not exist in application {2}.

Cause: Unable to find the metadata object.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-05707: {0} with name {1} already exists in application {2}.

Cause: The metadata object already exists.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-05708: Failed to delete the {0} with name {1} in application {2}.

Cause: Unable to delete the metadata object

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-05709: Metadata parameter {0} starts with {1} which is a reserved parameter keyword.

Cause: A property defined by the metadata object contains a reserved keyword.

Action: Remove the reserved keyword from the property name.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-05710: A validation error occurred while validating JobSet step {0}.

Cause: A JobSet step failed validation.

Action: See the base validation exception for the original validation error.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-05711: A null value cannot be used when querying the {0} field.

Cause: A value of null was used as the query value.

Action: Provide a non-null argument.
Level: 1

Type: WARNING

Impact: Other

ESS-05712: The metadata object with id {0} cannot be deleted because it belongs to one of the following restricted packages: {1}. However, metadata in the custom namespace, {2}, can be deleted.

Cause: The metadata object to be deleted resides in a read-only package.

Action: This metadata object cannot be deleted by end users.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-05713: The metadata object with id {0} cannot be updated because it belongs to one of the following restricted packages: {1}. However, metadata in the customer namespace, {2}, can be updated.

Cause: The metadata object to be updated resides in a read-only package.

Action: This metadata object cannot be updated by end users.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-05714: The metadata object with id {0} cannot be customized. Only metadata in the following packages can be customized: {1}. However, metadata in the customer namespace, {2}, cannot be customized.

Cause: The metadata object to be customized does not reside in a package that allows customization.

Action: This metadata object cannot be customized by end users.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-05715: Metadata parameter {0} cannot have value {1} because {1} is a reserved value.

Cause: The value of a property defined by the metadata object contains a reserved keyword.

Action: Change the value of the property.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-05716: Metadata parameter {0} cannot have an empty or null value.

Cause: The value of a property defined by the metadata object was empty or null.

Action: Change the value of the property.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-06000: Failed to obtain a runtime service instance. {0}

Cause: Failed to obtain a runtime service instance.

Action: Review log file for underlying cause.
Level: 1

Type: ERROR

Impact: Other

ESS-06002: Failed to close runtime service handle. {0}

Cause: Failed to close runtime service handle.

Action: Review the log file for underlying causes.
Level: 1

Type: ERROR

Impact: Other

ESS-06003: Runtime service system failure. {0}

Cause: Runtime service system failure.

Action: Review the log file for underlying causes.
Level: 1

Type: ERROR

Impact: Other

ESS-06100: No request found for the given id {0}.

Cause: A request was not found in ESS runtime storage corresponding to the indicated request identifier.

Action: Specify a request identifier for an existing request.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-06102: An error occured invoking the RuntimeService MBean.

Cause: An error occurred invoking the RuntimeService MBean.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-06500: Starting ESS resource adapter.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06501: Stopping ESS resource adapter.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06502: Endpoint activation for {0}.

Cause:

Action:
Level: 16

Type: NOTIFICATION

Impact: Other

ESS-06503: Endpoint deactivation for {0}.

Cause:

Action:
Level: 16

Type: NOTIFICATION

Impact: Other

ESS-06510: Registering application, {0}, via ClassLoader: {1}

Cause:

Action:
Level: 16

Type: NOTIFICATION

Impact: Other

ESS-06511: Registered application: {0} adfConfigUrl: {1} connUrl: {2}

Cause:

Action:
Level: 16

Type: NOTIFICATION

Impact: Other

ESS-06512: Removed registered configuration for application {0}.

Cause:

Action:
Level: 16

Type: NOTIFICATION

Impact: Other

ESS-06514: Application {0} is already registered.

Cause:

Action:
Level: 16

Type: NOTIFICATION

Impact: Other

ESS-06515: The logical name of this application, {0}, is already in use by the following deployed applications (possibly in different domains): {1}.

Cause: The logical name of this application is already in use by other applications using a different deployed name as this application.

Action: If this is the same application as one of the above applications then its deployed name should be changed to match. Otherwise, select a unique logical name for this application.
Level: 16

Type: NOTIFICATION

Impact: Other

ESS-06516: The deployed name of this application, {0}, is already in use by the following logical applications (possibly in different domains): {1}.

Cause: The deployed name of the application is already in use by other applications using a different logical name as this application.

Action: If this is the same application as one of the above applications then its logical name should be changed to match. Otherwise, select a unique deployed name for this application.
Level: 16

Type: NOTIFICATION

Impact: Other

ESS-06517: Logical application name {0} is a reserved keyword.

Cause: The specified logical application name is a reserved keyword.

Action: Change the name of the logical application.
Level: 16

Type: NOTIFICATION

Impact: Other

ESS-06521: Failed to start request dispatcher.

Cause: An error occurred while trying to start the request dispatcher.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-06522: Failed to start request processor.

Cause: An error occurred while trying to start the request processor.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-06523: Failed to start system event service.

Cause: An error occurred while trying to start the system event service.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-06524: Failed to start application event service.

Cause: An error occurred while trying to start the application event service.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-06525: Failed to start heartbeat monitor.

Cause: An error occurred while trying to start the heartbeat monitor.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-06526: Failed to update configuration information.

Cause: An error occurred while trying to update configuration information.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-06527: Failed to start deferred monitor.

Cause: An error occurred while trying to start the deferred monitor.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-06528: Failed to start work unit worker.

Cause: An error occurred while trying to start the work unit worker.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-06529: Failed to start change event service.

Cause: An error occurred while trying to start the change event service.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-06530: Dispatcher cannot be started when it is in the {0} state.

Cause: Dispatcher cannot be started when it is in the specified state.

Action: Start the dispatcher when it is in STOPPED state.
Level: 1

Type: WARNING

Impact: Other

ESS-06531: Dispatcher cannot be stopped when it is in the {0} state.

Cause: Dispatcher cannot be stopped when it is in the specified state.

Action: Stop the dispatcher when it is in STARTING or RUNNING state.
Level: 1

Type: WARNING

Impact: Other

ESS-06532: Processor cannot be started when it is in the {0} state.

Cause: Processor cannot be started when it is in the specified state.

Action: Start the processor when it is in STOPPED state.
Level: 1

Type: WARNING

Impact: Other

ESS-06533: Processor cannot be stopped when it is in the {0} state.

Cause: Processor cannot be stopped when it is in the specified state.

Action: Stop the processor when it is in STARTING or RUNNING state.
Level: 1

Type: WARNING

Impact: Other

ESS-06538: No endpoint is available for {0}.

Cause: An application using the specified endpoint application name is not deployed.

Action: Review the log file for underlying causes.
Level: 1

Type: ERROR

Impact: Other

ESS-06539: Could not create endpoint for {0}.

Cause: An error occurred creating an application endpoint.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-06540: Failed to get an endpoint to run dispatcher for application {0}.

Cause: Dispatch monitor was unable to obtain an application endpoint. This may happen when the system is busy and does not necessary indicate a problem.

Action: Review the log file for indications of a problem if this persists.
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06541: Error during dispatch for application {0}.

Cause: Error during dispatch for application.

Action: Review the log for underlying causes.
Level: 1

Type: WARNING

Impact: Other

ESS-06542: Error getting applications to dispatch.

Cause: Error getting applications for dispatch.

Action: Review the log for underlying causes.
Level: 1

Type: WARNING

Impact: Other

ESS-06543: Failed to deactivate endpoint for application {0}.

Cause: An error occurred while removing an application endpoint.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-06551: Failed processing trigger for {0} event.

Cause: Failed processing event trigger.

Action: Review the log for underlying causes.
Level: 1

Type: ERROR

Impact: Other

ESS-06552: Failed processing trigger for {0} event for request {1}.

Cause: Failed processing event trigger.

Action: Review the log for underlying causes.
Level: 1

Type: ERROR

Impact: Other

ESS-06553: Failed processing lifecycle for {0} event for request {1}.

Cause: Failed processing lifecycle event for a request.

Action: Review the log for underlying causes.
Level: 1

Type: ERROR

Impact: Other

ESS-06557: Failed to start heartbeat worker {0}.

Cause: ESS heart beat monitor failed to start due to a system failure.

Action: Check the causeBy clause of this exception to find more details.
Level: 1

Type: WARNING

Impact: Other

ESS-06558: Failed to get an endpoint to run a heartbeat for application {0}.

Cause: Heartbeat monitor was unable to obtain an application endpoint. This may happen when the system is busy and does not necessary indicate a problem.

Action: Review the log file for indications of a problem if this persists.
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06560: Error encountered by event worker.

Cause: Error encountered by event worker.

Action: Review the log for underlying causes.
Level: 1

Type: ERROR

Impact: Other

ESS-06570: Failed to get metadata for work assignment {0}.

Cause: Unable to retrieve work assignment metadata when analyzing work assignment bindings. The work assignment is ignored.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-06571: Failed to get workshift metadata ({0}) for work assignment {1}.

Cause: Unable to retrieve workshift metadata when analyzing a work assignment binding. The work assignment processing will ignore the workshift.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-06572: Failed to get schedule metadata ({0}) for work assignment {1}.

Cause: Unable to retrieve schedule metadata when analyzing a work assignment binding. The work assignment processing will ignore the workshift associated with the schedule.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-06573: Failed to start work assignment {0}.

Cause: Unable to start the first worker for the work assignment. The start will be retried in a short time.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-06574: Failed to start starvation thread for work assignment {0}.

Cause: Unable to start the starvation worker for the work assignment. The work assignment will be activated without the starvation worker.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-06575: Skipping inactive work assignment {0}.

Cause: The work assignment is defined as inactive and is being skipped.

Action: If the work assignment should be active, change it to active and reload work assignment metadata.
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06576: Binding default work assignment.

Cause: The default work assignment is being bound because no user-defined work assignments were bound.

Action: No action is necessary.
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06577: Skipping inactive workshift {0} for work assignment {1}.

Cause: The workshift is being skipped because it is inactive. It may have an allocation of 0 or a duration of 0.

Action: No action is necessary.
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06578: Started work assignment {0}.

Cause: Started the work assignment.

Action: No action is necessary.
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06579: Stopped work assignment {0}.

Cause: Stopped the work assignment.

Action: No action is necessary.
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06580: Skipping invalid work assignment {0}.

Cause: The work assignment is being ignored because it is invalid.

Action: Check the work assignment and correct the problem. Ensure the work assignment has at least one workshift defined.
Level: 1

Type: ERROR

Impact: Other

ESS-06581: Skipping invalid work assignment binding {0}.

Cause: The work assignment is being ignored because the binding is invalid.

Action: Check the work assignment binding mode and correct the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-06582: Skipping completed work assignment {0}.

Cause: The work assignment has completed and will never again become active. It is being skipped.

Action: If the work assignment should not be completed, check the workshift schedules to ensure they are correct and reload work assignment metadata.
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06583: Cannot delete bound work assignment {0}.

Cause: A work assignment that is bound may not be deleted.

Action: Unbind the work assignment and then delete it.
Level: 1

Type: WARNING

Impact: Other

ESS-06584: Reloading metadata for work assignment {0}.

Cause: Reloaded the work assignment metadata.

Action: No action is necessary.
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06585: Unable to bind work assignment {0} due to invalid workshift {1}.

Cause: In order to bind a work assignment, each of its workshifts must have an allocation of at least one. If the workshift has a schedule, the schedule must be unexpired, and the workshift duration must be > 0.

Action: Fix the workshift and try again to bind the work assignment.
Level: 1

Type: WARNING

Impact: Other

ESS-06586: Work assignment must include at least one workshift to be bound, {0}.

Cause: To be bound, a work assignment must have at least one workshift and be active.

Action: Fix the work assignment and try again to bind it.
Level: 1

Type: WARNING

Impact: Other

ESS-06587: Invalid update of a bound work assignment {0}.

Cause: A work assignment that is bound must have at least one workshift.

Action: Add at least one workshift to the work assignment and retry the update.
Level: 1

Type: WARNING

Impact: Other

ESS-06588: Failed to bind the ESS internal work assignment. {0}.

Cause: Unable to bind the ESS internal work assignment. The server will be started without the binding, and the default work assignment will be used.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-06589: Binding the ESS internal work assignment.

Cause: The ESS internal work assignment is being bound for a new server.

Action: No action is necessary.
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06590: Error encountered by the worker for work assignment {0}.

Cause: Error encountered by worker for work assignment.

Action: Review the log file for underlying causes.
Level: 1

Type: WARNING

Impact: Other

ESS-06592: Error while processing request {0} for application {1}.

Cause: Error while processing request for application

Action: Review the log file for underlying causes.
Level: 1

Type: ERROR

Impact: Other

ESS-06593: Required property, {0}, is not present in message received for work assignment {1}.

Cause: Required property is not present in message received for work assignment.

Action: Add the required request property for work assignment.
Level: 1

Type: ERROR

Impact: Other

ESS-06594: Failed to schedule additional work for work assignment {0}. {1}

Cause: Failed to schedule additional work for work assignment.

Action: Review the log file for underlying causes.
Level: 1

Type: WARNING

Impact: Other

ESS-06595: Failed to update request history for request {0}.

Cause: Failed to update request history for request.

Action: Review the log file for underlying causes.
Level: 1

Type: ERROR

Impact: Other

ESS-06610: Failed processing request {0}, {1} stage.

Cause: Failed processing request.

Action: Review the log file for underlying causes.
Level: 1

Type: WARNING

Impact: Other

ESS-06617: Failed to extract event information for event name {0}.

Cause: Failed to extract event information for event name.

Action: Review the log file for underlying causes.
Level: 1

Type: ERROR

Impact: Other

ESS-06618: Error while dispatching event {0}, request {1}, to request listeners.

Cause: Error while dispatching event to request listeners.

Action: Review the log file for underlying causes.
Level: 1

Type: ERROR

Impact: Other

ESS-06619: Error during trigger processing of event {0}, application {1}.

Cause: Error during trigger processing of event for the application.

Action: Review the log file for underlying causes.
Level: 1

Type: ERROR

Impact: Other

ESS-06620: Failed to get an endpoint for application {0}.

Cause: Failed to get an endpoint for application. Endpoint not available for processing.

Action: Make sure endpoint application is available for processing.
Level: 1

Type: WARNING

Impact: Other

ESS-06621: Error while calling endpoint for application {0}.

Cause: Failure encountered while calling endpoint for application.

Action: Ensure application is deployed and running.
Level: 1

Type: ERROR

Impact: Other

ESS-06622: Error while calling endpoint for application {0}, method {1}.

Cause: Error occured while calling endpoint for application.

Action: Ensure application is deployed and running.
Level: 1

Type: ERROR

Impact: Other

ESS-06640: Error encountered by worker.

Cause: Error encountered by worker.

Action: Review the log file for underlying causes.
Level: 1

Type: WARNING

Impact: Other

ESS-06641: Failed to schedule additional work. {0}

Cause: Failed to schedule additional work.

Action: Review the log file for underlying causes.
Level: 1

Type: WARNING

Impact: Other

ESS-06645: Specialization is incorrectly formed and invalid for work assignment {0}. {1}

Cause: The work assignment specialization is incorrectly formed and invalid.

Action: Fix the work assignment specialization and try again.
Level: 1

Type: WARNING

Impact: Other

ESS-06646: Exclusive binding requires non-empty specialization, work assignment {0}.

Cause: Exclusive binding requires the work assignment specialization is non-empty.

Action: Define a specialization for the work assignment and try binding it again.
Level: 1

Type: WARNING

Impact: Other

ESS-06700: Failed to check in event work {0} for {1} event, request {2}.

Cause: The event work for the given event could not be checked in or deleted.

Action: The event work operation should be automatically retried, so no action is necessary.
Level: 1

Type: WARNING

Impact: Other

ESS-06701: Failed to publish request listener event during processing of work {0}. Event: {1}, request: {2}.

Cause: An error occurred during an attempt to publish an event to be sent to the event listener of a request.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-06710: Unable to dispatch event {0} for request {1} to event listener.

Cause: The event work is not checked out to a specific instance.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-06711: Error invoking event listener for request {0}. Event name: {1}, event request: {2}

Cause: Event listener was invoked and failed with an error.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-06712: Event listener action for event {0}, request {1}. Status: [{2}], Message: [{3}]

Cause: Information from EventListenerAction returned by the listener.

Action: None
Level: 1

Type: WARNING

Impact: Other

ESS-06713: Delivery limit reached for event {0}, request {1}. No further delivery attempts will be made.

Cause: The event has been delivered to the event listener the maximum allowed times.

Action: None
Level: 1

Type: WARNING

Impact: Other

ESS-06714: Failed to authenticate user {0}. Dispatch event {1} for request {2} as an unprivileged call. Error: [{3}]

Cause: Failed to authenticate user. Event listener will be invoked in an unprivileged block.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-06800: Error handling {0} event for request {1} by request dispatcher.

Cause: Error handling event for request by request dispatcher.

Action: Review the log for underlying causes.
Level: 1

Type: WARNING

Impact: Other

ESS-06802: Request {0} is in {1} state. Skipping the processing.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06803: Request {0} is in {1} state. Skipping processing and deleting from wait queue.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06804: Request {0} has EXPIRED. Skipping processing and deleting from wait queue.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06805: Request {0} is in illegal state {1} ({2}). Skipping processing and deleting from wait queue.

Cause: Request is in illegal state. Skipping processing and deleting from wait queue.

Action: Review the log for underlying causes.
Level: 1

Type: WARNING

Impact: Other

ESS-06806: Request {0} not found in runtime store. Skipping processing and deleting from wait queue.

Cause: Request not found in runtime store. Skipping processing and deleting from wait queue.

Action: No Action is necessary.
Level: 1

Type: WARNING

Impact: Other

ESS-06807: Error occurred while dispatching requests.

Cause: An error occurred while attempting to dispatch one or more requests.

Action: Review the log file to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-06816: Error processing request {0} by request dispatcher.

Cause: An error occurred during the request dispatching process for the given request.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-06817: No subrequests exist for paused request {0}. Request execution will be resumed.

Cause: No sub-requests are active for this paused request.

Action: None
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-06820: Failed to retrieve Schedule for request {1}.

Cause: Failed to retrieve Schedule needed to determine the next schedule execution time.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-06821: Failed to update error information for request {0}. {1}

Cause: Failed to update the error information for a request.

Action: Review the log file for to determine the nature of the problem.
Level: 1

Type: ERROR

Impact: Other

ESS-06830: Error occurred processing post-execution work for request {0}. WorkId: {1}

Cause: An error occurred while processing a post-execution work unit.

Action: Review the log file to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-06831: Cannot process post-execution work for request {0}. State is {1}, process phase is {2}. WorkId: {3}

Cause: The request state and/or process phase prevents a post-execution work unit for a request from being processed. The work will be discarded.

Action: None
Level: 1

Type: WARNING

Impact: Other

ESS-06832: Failed to publish the metadata change event for {0}, appName={1}. {2}

Cause: Failed to publish the change event for the metadata change notification.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-06833: Unrecognized metadata change type {0}, appName={1}, metaId={2}, origServer={3}

Cause: Unrecognized metadata change type in metadata change event.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-06834: Ignoring change event as metadata cannot be found: {0}, appName={1}. {2}

Cause: Received metadata change event and metadata does not exist; it may have been deleted since the change happened.

Action: Review the log file for attached exceptions to determine the nature of the problem, if any.
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-07000: Error handling {0} event for request {1} by request processor.

Cause: Error handling event for request by request processor.

Action: Review the log file for underlying causes.
Level: 1

Type: ERROR

Impact: Other

ESS-07001: Error processing request {0}.

Cause: Error processing request.

Action: Review the log file for underlying causes.
Level: 1

Type: ERROR

Impact: Other

ESS-07002: Failed to obtain system executable wrapper for request {0}.

Cause: Possible causes include unknown job type, user login error, classloading issues...

Action: Review the causeBy exception clause to determine the specific failure.
Level: 1

Type: ERROR

Impact: Installation

ESS-07003: Execution warning for request {0}. Reason: {1}

Cause: Execution error warning for request.

Action: Review the log file for underlying causes.
Level: 1

Type: ERROR

Impact: Other

ESS-07004: Execution error for request {0}. Reason: {1}

Cause: Execution error for request.

Action: Review the log file for underlying causes.
Level: 1

Type: ERROR

Impact: Other

ESS-07005: Execution cancelled for request {0}. Reason: {1}

Cause: The job execution has been cancelled.

Action: Check the cause for the exception. If the cause is not given, you can adjust logging level to fine and retry it.
Level: 1

Type: WARNING

Impact: Other

ESS-07006: Failed to cancel request {0}.

Cause: Failed to cancel request.

Action: Review the log file for underlying causes.
Level: 1

Type: WARNING

Impact: Other

ESS-07012: Invalid action ({0}) returned from pre-process callout for request {1}. Setting to {2} state.

Cause: Invalid action returned from pre-process callout for the request.

Action: Review the log for underlying causes.
Level: 1

Type: ERROR

Impact: Other

ESS-07013: Invalid action ({0}) returned from post-process callout for request {1}. Setting to {2} state.

Cause: Invalid action returned from pre-process callout for the request.

Action: Review the log for underlying causes.
Level: 1

Type: ERROR

Impact: Other

ESS-07014: Delaying processing of request {0} by {1} minutes.

Cause: The pre-process callback return value indicated that request processing should be delayed.

Action: No action required. The request will be retried after the delay.
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-07015: Error occurred during cleanup of database job for request {0}.

Cause: An error occurred while performing post-execution clean tasks for an Oracle Scheduler job used to execute a SQL job request.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-07016: Failed processing update event for request {0}.

Cause: An error occurred processing an update event.

Action: Contact Oracle Support Services
Level: 1

Type: WARNING

Impact: Other

ESS-07017: Cannot process update event for request {0} in state {1}.

Cause: The request is in an illegal state for an update event.

Action: None
Level: 1

Type: WARNING

Impact: Other

ESS-07018: Cannot process update event for request {0} in state {1}.

Cause: The request is in an illegal state for an update event.

Action: None
Level: 1

Type: ERROR

Impact: Other

ESS-07019: Error processing request {0}. {1}

Cause: Error processing request.

Action: Review the log file for underlying causes.
Level: 1

Type: ERROR

Impact: Other

ESS-07020: Failed get an endpoint for application {0}.

Cause: Failed get an endpoint for application.

Action: No action is necessary.
Level: 1

Type: WARNING

Impact: Other

ESS-07021: Invalid work unit action for request {0}, work unit {1}, action {2}.

Cause: Invalid work unit action for request.

Action: Report the failure to Oracle support as it could be a bug in ESS.
Level: 1

Type: ERROR

Impact: Other

ESS-07022: Invalid endpoint action for request {0}, stage {1}, action {2}.

Cause: Invalid endpoint action for request.

Action: Report the failure to oracle support.
Level: 1

Type: ERROR

Impact: Other

ESS-07023: Error processing timed out requests. {0}.

Cause: An error occurred attempting to process a timed out request.

Action: None
Level: 1

Type: ERROR

Impact: Other

ESS-07024: Rejecting update event for request {0}. {1}. Result status = {2}. Result message = {3}. Message body = {4}.

Cause: The request is in an illegal state for an update event.

Action: None
Level: 1

Type: WARNING

Impact: Other

ESS-07025: Failed to allocate an asynchronous worker for request {0}. ({1}, {2}). ExecutionType = {3}.

Cause: Failed to allocate an asynchronous worker.

Action: None
Level: 1

Type: ERROR

Impact: Other

ESS-07026: Failed to release an asynchronous worker for request {0}. ({1}, {2}). ExecutionType = {3}.

Cause: Failed to release an asynchronous worker.

Action: None
Level: 1

Type: ERROR

Impact: Other

ESS-07027: Failed to terminate request {0}.

Cause: Failed to terminate request.

Action: Review the log file for underlying causes.n
Level: 1

Type: WARNING

Impact: Other

ESS-07028: Error invoking or executing application endpoint for request {0}. Check application status of logical application {1}.

Cause: An error occurred invoking a method on the endpoint of this application.

Action: Check that the application is deployed and running successfully.
Level: 1

Type: ERROR

Impact: Other

ESS-07029: Asynchronous throttle configuration does not exist for Workshift = {0}.

Cause: The async throttle configuration does not exist for the workshift.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

ESS-07030: Recovering update work unit {0} for request {1} that may have been executing. There is a possibility of redelivery.

Cause: An update event is being recovered from a stage where redelivery is possible.

Action: None
Level: 1

Type: WARNING

Impact: Other

ESS-07031: Error in transaction processing for request {0}. The transaction is eligible to be retried

Cause: A recoverable SQL error was encountered

Action: None
Level: 1

Type: WARNING

Impact: Other

ESS-07032: Work unit execution attempt, {0}, does not match request execution attempt, {1}, for request {2}.

Cause: The current work unit is for an older request execution attempt

Action: None
Level: 1

Type: WARNING

Impact: Other

ESS-07033: Job logic indicated a system error occurred while executing an asynchronous java job for request {0}. Job error is: {1}.

Cause: The job indicated that an error occurred

Action: Examine the innermost exception, if present, for the cause
Level: 1

Type: ERROR

Impact: Other

ESS-07034: Job logic indicated a business error occurred while executing an asynchronous java job for request {0}. Job error is: {1}.

Cause: The job indicated that a business error occurred

Action: Examine the innermost exception, if present, for the cause
Level: 1

Type: ERROR

Impact: Other

ESS-07035: Job logic indicated a warning occurred while executing an asynchronous java job for request {0}. Job warning is: {1}.

Cause: The job indicated that a warning occurred

Action: Examine the innermost exception, if present, for the cause
Level: 1

Type: WARNING

Impact: Other

ESS-07036: There was a system error while processing request {0} from which it cannot be recovered. Please check the server logs. (Process phase = {1}).

Cause: The request needed to be recovered because of a system error, but cannot be recovered safely

Action: None
Level: 1

Type: ERROR

Impact: Other

ESS-07037: Error performing substitutions for request {0}

Cause: An error occurred while performing substitution in a request parameter or other user input. This may be for process type job command line or environment variable.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-07038: Failed to initialize job context extensions for request {0} at stage {1}

Cause: An error occurred while initializing job context extensions.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-07039: Failed to cleanup job context for request {0} at stage {1}

Cause: An error occurred while cleaning job context extensions.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-07040: Failed to terminate job context for request {0}

Cause: An error occurred while terminating job context extensions.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-07041: Failed to retrieve alternate environment for application {0}

Cause: An error occurred while retrieving alternate application environment properties.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-07042: Expected class {0} not available for request mode {1}

Cause: An error instantiating an extensions class.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-07043: Failed to get platform request file directory for request {0}

Cause: An error occurred discovering the platform request file directory.

Action: Review the log file for attached exceptions to determine the nature of the problem.
Level: 1

Type: WARNING

Impact: Other

ESS-07050: Refreshing runtime incompatibilities for request {0}.

Cause: Refreshing runtime incompatibilities for the request.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-07200: Invalid workDirectory specified for spawned job request {0}: {1} does not exist.

Cause: Invalid workDirectory specified for spawned job request {0}: {1} does not exist.

Action: Ensure requestFileDirectory configured and a valid workDirectory specified for request.
Level: 1

Type: ERROR

Impact: Other

ESS-07201: Error launching spawnAgent for spawned job request {0}.

Cause: Error launching spawnAgent for spawned job request {0}.

Action: Review log file for nested IOexception and resolve the issue.
Level: 1

Type: ERROR

Impact: Other

ESS-07202: Error opening Output stream to spawnAgent for spawned job request {0}.

Cause: Error opening Output stream to spawnAgent for spawned job request {0}.

Action: Review log file for nested IOexception and resolve the issue.
Level: 1

Type: ERROR

Impact: Other

ESS-07203: spawnAgent terminated at launch for spawned job request {0}.

Cause: spawnAgent terminated at launch for spawned job request {0}.

Action: Enable Agent log to find cause and resolve.
Level: 1

Type: ERROR

Impact: Other

ESS-07204: spawnAgent cannot spawn process for spawned job request {0} with command line: {1}. Cause={2}

Cause: spawnAgent cannot spawn process for spawned job request {0} with cmdline: {1}. Cause={2}.

Action: Check error cause and update spawned job definition.
Level: 1

Type: ERROR

Impact: Other

ESS-07205: spawnAgent terminated before completion of spawned process for spawned job request {0} with command line: {1}.

Cause: spawnAgent terminated before completion of spawned process for spawned job request {0} with cmdline {1}.

Action: Enable Agent log to find cause and resolve.
Level: 1

Type: ERROR

Impact: Other

ESS-07206: Error waiting for completion of spawned job request {0} with command line: {1}.

Cause: Error waiting for completion of spawned job request {0} with cmdline: {1}.

Action: Review log file for nested IOexception and resolve the issue.
Level: 1

Type: ERROR

Impact: Other

ESS-07207: Invalid Exit Code returned by spawned process for spawned job request {0} with command line: {1}.

Cause: Invalid Exit Code returned by spawned process for spawned job request {0} with cmdline: {1}.

Action: Enable Agent log to find cause and resolve.
Level: 1

Type: ERROR

Impact: Other

ESS-07208: Error during post-completion cleanup for spawned job request {0} with command line: {1}.

Cause: Error during post-completion cleanup for spawned job request {0} with cmdline: {1}.

Action: Review log file for nested exception and resolve.
Level: 1

Type: ERROR

Impact: Other

ESS-07209: Error retrieving DomainConfigDirectory using JRF ServerPlatformSupportFactory API.

Cause: Error retrieving DomainConfigDirectory using JRF ServerPlatformSupportFactory API.

Action: Review log file for nested exception and resolve.
Level: 1

Type: ERROR

Impact: Other

ESS-07210: Error registering shutdown hook for spawned job request {0}.

Cause: Error registering shutdown hook for spawned job request {0}.

Action: Review log file for nested exception and resolve.
Level: 1

Type: ERROR

Impact: Other

ESS-07211: Error deregistering shutdown hook for spawned job request {0}.

Cause: Error deregistering shutdown hook for spawned job request {0}.

Action: Review log file for nested exception and resolve.
Level: 1

Type: WARNING

Impact: Other

ESS-07212: Error updating processId for spawned job request {0}.

Cause: Error updating processId for spawned job request {0}.

Action: Review log file for nested exception and resolve.
Level: 1

Type: WARNING

Impact: Other

ESS-07213: Using Perl SpawnAgent {1} with perl interpreter at {2} for spawned job request {0}.

Cause: Using Perl SpawnAgent {1} with perl interpreter at {2} for spawned job request {0}.

Action: None
Level: 1

Type: NOTIFICATION

Impact: Other

ESS-07214: Error locating Perl spawnAgent script for spawned job request {0}.

Cause: Error locating Perl SpawnAgent script for spawned job request {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

ESS-07215: Error locating Perl interpreter for spawned job request {0}.

Cause: Error locating Perl interpreter for spawned job request {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

ESS-07217: Error retrieving SpawnAgent configuration.

Cause: Error retrieving SpawnAgent configuration.

Action: Review log file for nested exception. Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

ESS-07218: Unable to locate Perl interpreter from FusionApps WebTier location.

Cause: Unable to locate Perl interpreter from FusionApps WebTier location.

Action: None
Level: 1

Type: WARNING

Impact: Other

ESS-07500: Error parsing attribute {0}. {1}

Cause: An error is present in a command attribute format.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

ESS-07501: Error starting command worker. {0}

Cause: An error occurred starting a command worker.

Action: None
Level: 1

Type: WARNING

Impact: Other

ESS-07502: Failed to set request state to VALIDATION_FAILED for request {0}. {1}

Cause: An error occurred while setting the state of the request to VALIDATION_FAILED.

Action: None
Level: 1

Type: ERROR

Impact: Other

ESS-07503: Document conversion failed for command work {0}. Command type: {1}, request: {2}.

Cause: Failed converting DOC Document for command work.

Action: None
Level: 1

Type: ERROR

Impact: Other

ESS-07505: Validation of request {0} failed.

Cause: Validation of the request has failed.

Action: Check logs and error information for details.
Level: 1

Type: ERROR

Impact: Other

ESS-07506: Failed to check in command work {0} for {1} command, request {2}.

Cause: The work for the given command could not be checked in or deleted.

Action: The command work operation should be automatically retried, so no action is necessary.
Level: 1

Type: WARNING

Impact: Other

ESS-07507: Unknown command type, {0}, for command work {1}.

Cause: The command work has an unknown commad type.

Action: None
Level: 1

Type: ERROR

Impact: Other

ESS-07508: Error calling endpoint for application {0} during processing of {1} command for request {2}.

Cause: The command work has an unknown commad type.

Action: None
Level: 1

Type: ERROR

Impact: Other

ESS-07509: Failed to execute command {0} for request {1} for command work {2}.

Cause: An error occurred executing the command.

Action: Review the log file for the cause.
Level: 1

Type: WARNING

Impact: Other

ESS-07510: Failed to update command {0} for request {1} for command work {2}.

Cause: An error occurred updating the command.

Action: Review the log file for the cause.
Level: 1

Type: WARNING

Impact: Other

ESS-07540: Failed to complete request {0} during group cleanup for execution group {1}, isolation group {2}.

Cause: Clean up of request failed during execution group removal.

Action: None. The action will be automatically retried.
Level: 1

Type: WARNING

Impact: Other

ESS-07541: Failed to get list of incomplete requests for execution group {0}, isolation group {1}.

Cause: Retrieving requests during execution group removal failed.

Action: None. The action will be automatically retried.
Level: 1

Type: WARNING

Impact: Other

ESS-07542: Failed to remove registrations for execution group {0}, isolationGroup{1}.

Cause: Removing instance or application registrations failed during execution group removal.

Action: None. The action will be automatically retried.
Level: 1

Type: WARNING

Impact: Other

ESS-07543: Failed to lock recovery delete table.

Cause: Failed to lock the recovery delete table.

Action: None. The action will be automatically retried.
Level: 1

Type: WARNING

Impact: Other

ESS-07544: Failed to insert row for process group {0}, isolationGroup {1}, action {2}.

Cause: Failed to insert the entry into recovery delete table.

Action: None. The action will be automatically retried.
Level: 1

Type: WARNING

Impact: Other

ESS-07545: Failed to delete row for process group {0}, isolationGroup {1}, action {2}.

Cause: Failed to delete the entry from recovery delete table.

Action: None. The action will be automatically retried.
Level: 1

Type: WARNING

Impact: Other

ESS-07546: Failed to query row for process group {0}, isolationGroup {1}, action {2}.

Cause: Failed to query for the entry from recovery delete table.

Action: None. The action will be automatically retried.
Level: 1

Type: WARNING

Impact: Other

ESS-07547: Failed to insert essconfig for process group {0}, isolationGroup {1}, appname {2}.

Cause: Failed to insert the entry from essconfig table.

Action: None.
Level: 1

Type: WARNING

Impact: Other

ESS-07548: Failed to delete essconfig for process group {0}, isolationGroup {1}, appname {2}.

Cause: Failed to delete the entry from essconfig table.

Action: None.
Level: 1

Type: WARNING

Impact: Other

ESS-07549: Failed to update essconfig customization for process group {0}, isolationGroup {1}, appname {2}.

Cause: Failed to update the entry from essconfig table.

Action: None.
Level: 1

Type: WARNING

Impact: Other

ESS-07550: Failed to query essconfig or customization for process group {0}, isolationGroup {1}, appname {2}.

Cause: Failed to query the entry from essconfig table.

Action: None.
Level: 1

Type: WARNING

Impact: Other

ESS-07551: Failed to find essconfig entry for process group {0}, isolationGroup {1}, appname {2}.

Cause: Could not find the entry from essconfig table.

Action: Please give correct processgroup and logical application name.
Level: 1

Type: WARNING

Impact: Other

ESS-08000: The value of filter is null.

Cause: The value of filter is null

Action: Provide the correct privilege name.
Level: 1

Type: ERROR

Impact: Other

ESS-08001: Invalid sec filter comparator.

Cause: Invalid sec filter comparator.

Action: Choose correct comparator, GRANTED.
Level: 1

Type: ERROR

Impact: Other

ESS-09000: Translation service with resource bundles {0} for Locale {1} can not be performed due to runtime error.

Cause: ESS runtime encountered a failure for the given translation request.

Action: Correct the bundle id, make sure it exists in the application environement.
Level: 1

Type: TRACE

Impact: Programmatic

ESS-09001: Message with requested key {0} is not found in the associated resource bundles.

Cause: Message with the requested key is not found in the resource bundle.

Action: Make sure the key is entered correctly.
Level: 1

Type: TRACE

Impact: Programmatic

ESS-09002: {0} is not a valid {1} implementation.

Cause: The implementation class is not of expected interface type.

Action: Make sure the implementation class implements the proper interface.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-09003: Failed to instantiate the translation service factory implementation {0}.

Cause: Error while instantiating an instance of translation service factory.

Action: Check the log to find exception details.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-09004: Failed to retrieve a valid instance of underlying oracle.javatools ResourceBundleManager. Design time metadata translation is not supported.

Cause: Error while instantiating an instance of oracle.javatools.resourcebundle.ResourceBundleManager.

Action: None
Level: 1

Type: ERROR

Impact: Programmatic

ESS-09005: Encountered MDS exception while performing MDS operations.

Cause: Encountered MDS exception.

Action: Check the exception for details.
Level: 1

Type: TRACE

Impact: Programmatic

ESS-09400: Encountered an execution context exception.

Cause: Encountered exception while invoking DMS execution context API(s).

Action: Check exception stack trace for details.
Level: 1

Type: WARNING

Impact: Programmatic

ESS-09402: Failed to compile recurrence expression.

Cause: Failed to compile recurrence expression

Action: Correct the invalid recurrence expression.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-09403: Schedule list limit must be a non-negative integer.

Cause: Schedule List limit is invalid.

Action: List limit must be a non-negative integer.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-09404: Schedule list begin date cannot be null.

Cause: Invalid Null Schedule Begin date.

Action: Provide a non-null begin date for the schedule.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-09405: Schedule begin date can not be after end date.

Cause: Begin Date for the schedule is after the end date.

Action: Correct the invalid begin date or end date.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-09406: Parsing exception. Only one day type recurrence field may be specified.

Cause: More than one of BYDAY, BYMONTHDAY, BYYEARDAY was specified

Action: Correct the invalid recurrence.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-09407: Parsing exception. An occurrence by week number can only be used with a yearly frequency.

Cause: A BYWEEKNO clause was specified with a frequency other than YEARLY

Action: Correct the invalid recurrence.
Level: 1

Type: ERROR

Impact: Programmatic

ESS-09408: Parsing exception. An occurrence by week number cannot be used with an occurrence by month.

Cause: More than one of BYWEEKNO, BYMONTH was specified

Action: Correct the invalid recurrence.
Level: 1

Type: ERROR

Impact: Programmatic

39 FED-10104 to FED-18084

FED-10104: A name identifier update using protocol version {0} cannot be performed on a federation created with protocol version {1}

Cause: Unable to perform a name identifier update with the current version.

Action: Try using a different protocol version.
Level: 1

Type: ERROR

Impact: Configuration

FED-10105: Attribute Service location not found in provider metadata for {0}

Cause: Attribute service location was not in the provider metadata.

Action: Verify that the provider metadata contains the attribute service location.
Level: 1

Type: ERROR

Impact: Configuration

FED-10106: AssertionID service location not found in provider metadata for {0}

Cause: AssertionID service location was not in the provider metadata.

Action: Verify that the provider metadata contains the AssertionID service location.
Level: 1

Type: ERROR

Impact: Configuration

FED-10108: Cannot create federation with opaque name identifier: invalid data store

Cause: An opaque name identifier was used without a federation data store.

Action: Use a federation data store when an opaque identifier is used or configure Oracle Identity Federation to use a non-opaque Name ID.
Level: 1

Type: ERROR

Impact: Configuration

FED-10109: The nameid user store attribute has not been set for partner {0}.

Cause: Assertion to user record via NameId is enabled but no user attribute was specified.

Action: Specify a userstore attribute to which the name identifier value should be mapped.
Level: 1

Type: ERROR

Impact: Configuration

FED-10110: Cannot find service provider metadata for Affiliation={0};affiliationID type={1}

Cause: The federation did not contain a service provider that is part of the affiliation.

Action: Import the metadata of a service provider that is a member of the affiliation.
Level: 1

Type: ERROR

Impact: Configuration

FED-10111: Cannot find provider metadata for providerID={0}; providerID type={1}

Cause: There was no metadata available for the provider with the given ID.

Action: Verify that the provider ID is correct or that the provider is included in the federation.
Level: 1

Type: ERROR

Impact: Configuration

FED-10112: No default identity provider was set for the single sign-on operation.

Cause: The default single sign-on identity provider configuration property was not set.

Action: Set the default single sign-on identity provider in the Oracle Identity Federation configuration.
Level: 1

Type: ERROR

Impact: Configuration

FED-10113: Federation termination protocol not enabled

Cause: The federation termination protocol was not enabled.

Action: Verify that the federation termination protocol is enabled.
Level: 1

Type: ERROR

Impact: Configuration

FED-10114: NameIDPolicy not supported: {0}

Cause: The NameIDPolicy requested is not supported or not enabled.

Action: Check that the requested name identifier format is supported and enabled.
Level: 1

Type: ERROR

Impact: Configuration

FED-10115: Cannot find the AssertionConsumerServiceURL in the requester metadata.

Cause: Could not find the AssertionConsumerServiceURL in the requester's provider metadata.

Action: Verify that the AssertionConsumerServiceURL is present in the provider metadata.
Level: 1

Type: ERROR

Impact: Configuration

FED-10117: Provider is not enabled: {0}

Cause: The peer provider is not enabled in the federation.

Action: Verify that the provider is enabled.
Level: 1

Type: ERROR

Impact: Configuration

FED-10118: Single sign-on binding unknown: {0}

Cause: The single sign-on binding is not one of the known bindings.

Action: Verify that the single sign-on binding is one of the bindings known by Oracle Identity Federation.
Level: 1

Type: ERROR

Impact: Configuration

FED-10119: The specified binding ({0}) for single sign-on with {1} is not supported by the peer provider.

Cause: The binding specified is not one of the bindings supported by the peer provider.

Action: Verify that the binding specified is supported by the peer provider.
Level: 1

Type: ERROR

Impact: Configuration

FED-10120: Unable to find a suitable binding to send the request.

Cause: Oracle Identity Federation could not find a binding to send the request.

Action: Verify that Oracle Identity Federation and the remote providers have a common binding for the profile.
Level: 1

Type: ERROR

Impact: Configuration

FED-10121: Unable to start identity provider-initiated single sign-on: Unknown metadata version.

Cause: The service provider metadata version was not recognized.

Action: Verify that the metadata version is one of the versions supported by the identity provider.
Level: 1

Type: ERROR

Impact: Configuration

FED-10122: Unable to start identity provider-initiated single sign-on: SP {0} does not belong to affiliation {1}.

Cause: The target service provider was not part of the affiliation.

Action: Check the provider federation to verify that the target service provider is in the affiliation.
Level: 1

Type: ERROR

Impact: Configuration

FED-10123: Unknown NameIDPolicy {0}

Cause: The NameIDPolicy is not one of the known policies.

Action: Verify that the NameIDPolicy is one of the policies that is accepted by Oracle Identity Federation.
Level: 1

Type: ERROR

Impact: Configuration

FED-10124: User cannot be located for federation with provider ID {0} name identifier {1} and message: {2}

Cause: Federation does not exist between the user, Oracle Identity Federation and the given peer provider.

Action: Verify that the federation exists, or configure the server to create one.
Level: 1

Type: ERROR

Impact: Configuration

FED-10125: AssertionID responder functionality is not enabled.

Cause: The AssertionID responder functionality has been disabled in the Oracle Identity Federation configuration.

Action: Enable the AssertionID responder functionality.
Level: 1

Type: ERROR

Impact: Configuration

FED-10126: Attribute Query requester functionality is not enabled.

Cause: The Attribute Query requester functionality has been disabled in the Oracle Identity Federation configuration.

Action: Enable the AttributeQuery requester functionality.
Level: 1

Type: ERROR

Impact: Configuration

FED-10127: AssertionID requester functionality is not enabled.

Cause: The AssertionID requester functionality has been disabled in the Oracle Identity Federation configuration.

Action: Enable the AssertionID requester functionality.
Level: 1

Type: ERROR

Impact: Configuration

FED-10128: Attribute Query responder functionalities are not enabled.

Cause: The Attribute Query responder functionality has been disabled in the Oracle Identity Federation configuration.

Action: Verify that the Attribute Query responder functionality is enabled.
Level: 1

Type: ERROR

Impact: Configuration

FED-10129: Authentication Query responder functionalities are not enabled.

Cause: The Authentication Query responder functionality has been disabled in the Oracle Identity Federation configuration.

Action: Verify that the Authentication Query requester functionality is enabled.
Level: 1

Type: ERROR

Impact: Configuration

FED-10130: No metadata exists for protocol {0} used by provider {1}

Cause: Metadata for this provider was not found.

Action: Load metadata for the provider.
Level: 1

Type: ERROR

Impact: Configuration

FED-10131: Unknown service provider: {0}

Cause: The service provider is not in the federation.

Action: Verify the trusted provider federation configuration.
Level: 1

Type: ERROR

Impact: Configuration

FED-10132: Single sign-on functionality is not enabled

Cause: The single sign-on functionality has been disabled in the Oracle Identity Federation configuration.

Action: Verify that the single sign-on functionality is enabled.
Level: 1

Type: ERROR

Impact: Configuration

FED-10133: Identity provider functionality is not enabled.

Cause: The identity provider functionality has been disabled in the Oracle Identity Federation configuration.

Action: Verify that the identity provider functionality is enabled.
Level: 1

Type: ERROR

Impact: Configuration

FED-10134: Incoming authentication request uses a protocol profile which is not enabled: {0}

Cause: Protocol profile has not been enabled in the Oracle Identity Federation configuration.

Action: Verify that the profile used for the authentication request is enabled.
Level: 1

Type: ERROR

Impact: Configuration

FED-10135: Incoming request uses a protocol profile which is not enabled: {0}

Cause: Protocol profile has not been enabled in the Oracle Identity Federation configuration.

Action: Verify that profile used for the incoming request is enabled.
Level: 1

Type: ERROR

Impact: Configuration

FED-10136: Incoming assertion uses a protocol profile which is not enabled: {0}

Cause: Protocol profile has not been enabled in the Oracle Identity Federation configuration.

Action: Verify that the profile used in the assertion is enabled.
Level: 1

Type: ERROR

Impact: Configuration

FED-10139: Register Name Identifier protocol is disabled.

Cause: The Register Name Identifier protocol has been disabled in the Oracle Identity Federation configuration.

Action: Verify that the Register Name IdentifierProtocol is enabled.
Level: 1

Type: ERROR

Impact: Configuration

FED-10140: SAML 1.0 protocol functionality is not enabled.

Cause: The SAML version 1.0 protocol has been disabled in the Oracle Identity Federation configuration.

Action: Verify that the SAML version 1.0 protocol is enabled.
Level: 1

Type: ERROR

Impact: Configuration

FED-10141: SAML 1.1 protocol functionality is not enabled.

Cause: The SAML version 1.1 protocol has been disabled in the Oracle Identity Federation configuration.

Action: Verify that the SAML version 1.1 protocol is enabled.
Level: 1

Type: ERROR

Impact: Configuration

FED-10142: SAML 2.0 protocol functionality is not enabled.

Cause: The SAML version 2.0 protocol has been disabled in the Oracle Identity Federation configuration.

Action: Verify that the SAML version 2.0 protocol is enabled.
Level: 1

Type: ERROR

Impact: Configuration

FED-10143: Service provider functionality is not enabled

Cause: Service provider functionality has been disabled in the Oracle Identity Federation configuration

Action: Verify that service provider functionality is enabled.
Level: 1

Type: ERROR

Impact: Configuration

FED-10169: EventFactory was not found for {0}.

Cause: EventFactory for this class was not registered.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

FED-10178: Metadata version parameter unknown: {0}

Cause: The metadata version parameter is unknown.

Action: Check that the metadata version parameter is correct.
Level: 1

Type: ERROR

Impact: Configuration

FED-10187: Logout configuration error: webContext (={0}) and/or relativePath (={1}) for logout are incorrect.

Cause: The webContext and/or relativePath for logout were incorrectly configured.

Action: Verify that the webContext and relativePath for logout are correctly configured.
Level: 1

Type: ERROR

Impact: Configuration

FED-10188: Invalid name identifier format

Cause: The name identifier format is invalid, or custom name ID format is disabled.

Action: Verify that the name identifier format is valid, or that customizable name ID format is enabled.
Level: 1

Type: ERROR

Impact: Configuration

FED-10189: Attribute authority does not support any appropriate name identifier formats.

Cause: The attribute authority does not support the requested subject name identifier format.

Action: Either use a subject format other than "userid", or use a different attribute authority.
Level: 1

Type: ERROR

Impact: Configuration

FED-10191: The service provider integration module is not enabled: {0}.

Cause: The service provider integraton module is disabled in the Oracle Identity Federation configuration.

Action: Enable the appropriate service provider integration module.
Level: 1

Type: ERROR

Impact: Configuration

FED-10195: Authentication engine configuration error: WebContext={0} ; RelativePath={1}

Cause: The Web Context and/or the Relative Path properties of the authentication engine configuration were not set.

Action: Check that the authentication engine configuration defines the required web context and relative path.
Level: 1

Type: ERROR

Impact: Configuration

FED-10196: Service provider integration module configuration error: WebContext={0} ; RelativePath={1}

Cause: The Web Context and/or the Relative Path properties of the service provider integration module configuration were not set.

Action: Check that the service provider integration module configuration defines the required web context and relative path.
Level: 1

Type: ERROR

Impact: Configuration

FED-10197: The service provider anonymous user ID was not set.

Cause: The Oracle Identity Federation server needed to create a session of type anonymous but the Anonymous User ID is not set in the configuration.

Action: Set the Anonymous User ID in the Oracle Identity Federation configuration.
Level: 1

Type: ERROR

Impact: Configuration

FED-10198: The Pre/Post Custom Engine is not enabled.

Cause: The Pre/Post Custom Engine is disabled in the Oracle Identity Federation configuration.

Action: Enable the appropriate Pre/Post Custom Engine.
Level: 1

Type: ERROR

Impact: Configuration

FED-10199: Pre/Post Custom Engine configuration error: WebContext={0} ; RelativePath={1}

Cause: The Web Context and/or the Relative Path properties of the Pre/Post Custom Engine configuration were not set.

Action: Check that the Pre/Post Custom Engine configuration defines the required web context and relative path.
Level: 1

Type: ERROR

Impact: Configuration

FED-10205: OpenID 2.0 protocol functionality is not enabled.

Cause: The OpenID version 2.0 protocol has been disabled in the Oracle Identity Federation configuration.

Action: Verify that the OpenID version 2.0 protocol is enabled.
Level: 1

Type: ERROR

Impact: Configuration

FED-10206: OAuth 2.0 protocol functionality is not enabled.

Cause: The OAuth version 2.0 protocol has been disabled in the Oracle Identity Federation configuration.

Action: Verify that the OAuth version 2.0 protocol is enabled.
Level: 1

Type: ERROR

Impact: Configuration

FED-11002: Cannot retrieve the unique user federation ID from the federation record.

Cause: Could not retrieve the unique user federation ID from the federation record.

Action: Verify that the federation record is correctly formatted.
Level: 1

Type: ERROR

Impact: Data

FED-12006: Unsupported attribute value type Object {0}

Cause: Attribute value object received from the peer provider was not of a supported type.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: WARNING

Impact: Other

FED-12016: Message Creation Exception: unable to create the message: {0}

Cause: Could not create the protocol message.

Action: Check the Oracle Identity Federation logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FED-12020: Translation Exception: unable to translate message: {0}.

Cause: There was a problem marshalling or unmarshalling the message.

Action: Check the Oracle Identity Federation logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FED-12037: SAML Artifact Exception: {0}

Cause: An error occurred while creating or parsing a SAML Artifact.

Action: Check the Oracle Identity Federation logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FED-12038: SAML Protocol Exception: {0}

Cause: An error occurred while creating or parsing a SAML Protocol message.

Action: Check the Oracle Identity Federation logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FED-12042: Error while generating Oracle Identity Federation provider metadata.

Cause: An error occurred while creating the Oracle Identity Federation provider metadata.

Action: Check logs and configuration, or contact Oracle Support Services to rectify the issue.
Level: 1

Type: ERROR

Impact: Other

FED-12081: Error while generating Oracle Identity Federation XRDS metadata.

Cause: An error occurred while creating the Oracle Identity Federation XRDS metadata.

Action: Check logs and configuration, or contact Oracle Support Services to rectify the issue.
Level: 1

Type: ERROR

Impact: Other

FED-12085: Identity Provider Discovery service page disabled

Cause: The IdP Discovery service page is disabled

Action: Update the configuration to enable that service if needed
Level: 1

Type: ERROR

Impact: Other

FED-12086: The credentials provided during the registration data retrieval operation could not be validated

Cause: The credentials provided by the requesting client could not be valited

Action: Ensure that the client is sending the correct credentials
Level: 1

Type: ERROR

Impact: Other

FED-13000: Cannot complete the logout process.

Cause: Oracle Identity Federation could not complete the logout process, due to a lack of profile support from the service providers.

Action: Perform the logout process using another binding or check that the various peer providers support approriate logout profiles.
Level: 1

Type: ERROR

Impact: Programmatic

FED-13008: Cannot create temporary federations.

Cause: Temporary federation store is unavailable.

Action: Check configuration of data store. Make sure the data store is up and has space available.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

FED-13018: Cannot create a permanent federation record with a transient data store.

Cause: Could not create a permanent federation due to the store being unavailable.

Action: Check configuration of data store. Make sure the data store is up and has space available.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

FED-13019: The Authentication Engine ID and Service Provider Engine ID are null.

Cause: The engine did not return an authentication engine ID or a service provider engine ID.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: ERROR

Impact: Programmatic

FED-13020: Both the Authentication Engine ID and Service Provider Engine ID are set.

Cause: The engine returned both an authentication engine ID and an service provider engine ID, where only one should be set.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: ERROR

Impact: Programmatic

FED-13021: Cannot retrieve session during logout flow.

Cause: The session could not be retrieved.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: WARNING

Impact: Programmatic

FED-15005: Name identifier registration is already in progress.

Cause: A name identifier registration was in progress when a new registration was initiated.

Action: Wait until the name identifier registration finishes.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15006: The single sign-on Assertion has been marked as logged out: {0}.

Cause: A non-expired logout request containing the Assertion SessionIndex invalidated the single sign-on assertion.

Action: Perform single sign-on again.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15007: The single sign-on Assertion has been marked as logged out: {0}.

Cause: A non-expired logout request with no SessionIndex invalidated the single sign-on Assertion.

Action: Perform single sign-on again.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15008: A SAML 2.0 name identifier update cannot be performed on a non-SAML 2.0 federation record.

Cause: Tried to perform a SAML 2.0 name identifier update.

Action: Try a different protocol version.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15009: An error occurred while dereferencing the SAML 2.0 Artifact: {0} - {1}

Cause: A problem occurred with the SAML 2.0 Artifact.

Action: Verify the contents of the SAML 2.0 Artifact.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15010: Artifact not present

Cause: The artifact was not present in the request.

Action: Verify that the artifact is set in the request
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15011: Cannot find the authentication request associated with the assertion: {0}.

Cause: The Oracle Identity Federation server could not retrieve the saved AuthnRequest corresponding to the incoming assertion.

Action: Check that the single sign-on operation was performed using fully qualified hostname, and that the same Oracle Identity Federation server was used for the operation in load balanced mode.
Level: 1

Type: ERROR

Impact: Requests/Responses

Cause: The assertion was replayed.

Action: Verify that the assertion has not been replayed.

FED-15012: Cannot select the binding to use to send the request.

Cause: Either the profile was not supported by the remote server, or could not agree with the Oracle Identity Federation server on a common binding.

Action: Verify that the remote server and the Oracle Identity Federation server have a common binding.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15013: Cannot select the binding to use to send the response.

Cause: Either the profile was not supported by the remote server, or could not agree with the Oracle Identity Federation server on a common binding.

Action: Verify that the remote server and the Oracle Identity Federation server have a common binding.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15015: Error encountered while parsing XML element {0}, child of {1} in incoming XML message.

Cause: Could not parse an XML element from the incoming XML message.

Action: Verify that the incoming XML message is valid and correctly formatted.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15018: Error while decoding the authentication result: user ID missing.

Cause: The user ID was missing in the result returned by the authentication process.

Action: Verify that the user ID is valid.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15020: Name identifier format not supported or missing for attribute responder: {0}

Cause: The name identifier format for the attribute responder was unknown or not accepted.

Action: Verify that the name identifier format is one of the formats that is accepted by Oracle Identity Federation.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15021: Name identifier format not supported or missing for authentication responder: {0}

Cause: The name identifier format for the authentication responder was unknown or not accepted.

Action: Verify that the name identifier format is one of the formats that is accepted by Oracle Identity Federation.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15022: Error processing response message.

Cause: Was unable to process the response message.

Action: Check the Oracle Identity Federation logs for more specific information.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15024: Query received is not an Attribute Query.

Cause: Internal server error; expected an AttributeQuery message, but received a different message.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15025: Query received is not an Authentication Query.

Cause: Internal server error; expected an AuthenticationQuery message, but received a different message.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15026: Issuer is not set in the incoming assertion request message: the provider is unknown

Cause: The issuer attribute was not set in the assertion request message.

Action: Verify that the issuer attribute is set in the assertion request message.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15027: Issuer is not set in the incoming attribute query message: the provider is unknown

Cause: The issuer attribute was not set in the attribute query message.

Action: Verify that the issuer attribute is set in the attribute query message.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15028: Issuer is not set in the incoming authentication query message: the provider is unknown

Cause: The issuer attribute was not set in the authentication query message.

Action: Verify that the issuer attribute is set in the authentication query message.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15032: No service provider federation found for provider {0} and name identifier format {1} and name identifier value {2}

Cause: Unable to find the service provider federation corresponding to this provider and name identifier in the federation data store.

Action: Check the federation data store to verify that a user identity federation exists with the provider ID and name identifier submitted in the query.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15033: Outgoing assertion protocol profile is not supported or not enabled: {0}

Cause: The outgoing assertion protocol profile was not supported, or enabled.

Action: Verify that the assertion protocol profile is supported by Oracle Identity Federation.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15034: Profile is unknown: {0}

Cause: The profile was unknown.

Action: Verify that the profile version is correct.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15035: Provider ID is missing from the authentication request

Cause: The provider ID was missing from the authentication request.

Action: Verify that the provider ID is present in the authentication request.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15037: Request destination is invalid

Cause: The request destination was not a valid URL.

Action: Verify that the request destination is a valid URL and correspond to the URL where the request was posted.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15038: Response destination is invalid

Cause: The response destination was not a valid URL.

Action: Verify that the response destination is a valid URL and correspond to the URL where the response was posted.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15039: Response does not correspond to any requests

Cause: The Oracle Identity Federation server could not locate the request corresponding to the incoming response.

Action: Verify that the incoming response is valid and corresponds to a request, or perform the operation again.
Level: 1

Type: ERROR

Impact: Requests/Responses

Cause: The response was replayed

Action: verify that the response is not replayed

FED-15041: Cannot process the incoming request

Cause: Single sign-on is required with peer provider in order to fulfill the current request.

Action: Perform single sign-on before attempting to execute the protocol operation.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15042: The InResponseTo header does not correspond to a ManageNameID request.

Cause: The InResponseTo pointed to a message other than ManageNameID.

Action: Check with the peer provider.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15043: The received assertion does not contain an AuthenticationStatement: {0}

Cause: The assertion did not contain an authentication statement.

Action: Contact the peer provider for more details on why the assertion does not contain an authentication statement, and examine the assertion for possible information.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15044: The response does not contain any assertions: {0}

Cause: The identity provider did not include any assertions in the response.

Action: Check that the identity provider includes an assertion with the response.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15055: Invalid version format in the active identity provider federation entry: {0}

Cause: The version format was incorrect.

Action: Verify that the version parameter is in a valid format.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15061: Unknown message: {0}

Cause: A protocol message was sent on the incorrect service URL.

Action: Verify that the message sent to the service URL is of correct type.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15062: Authentication request destination is invalid

Cause: The authentication request destination was not a valid URL.

Action: Verify that the authentication responder functionalities are enabled.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15063: Authentication request is expired.

Cause: The authentication request has expired or is not yet valid.

Action: Verify the time settings between this server and the peer provider are synchronized. Alternatively the server clock drift can be increased in the Oracle Identity Federation configuration.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15064: Destination URL cannot be validated: {0}

Cause: Destination URL could not be validated.

Action: Verify that the URL is correct.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15065: The destination field ({0}) from the SAML 2.0 message does not match the actual request URL {1}

Cause: The message was submitted on a URL that is different from the URL that was specified by the remote provider in the destination field.

Action: Contact remote provider.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15067: Invalid response.

Cause: Protocol response was corrupt.

Action: Verify that an XML message is well-formed and correct.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15070: The response cannot be validated.

Cause: Message does not follow the configuration requirements.

Action: Check previous error messages for more information.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15071: The server is not included in the AudienceRestrictionCondition.

Cause: The value of the provider ID entry in the federations for the identity provider was incorrect.

Action: Verify that the federations entry corresponding to the assertion consumer is correct.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15072: Unknown version in factory request.

Cause: The protocol version sent back from the peer provider is not valid.

Action: Verify that the peer provider is configured to the correct protocol version.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15073: The profile is not supported.

Cause: The profile is not supported or is not enabled.

Action: Verify that the profile is supported by Oracle Identity Federation.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15074: The user authenticated at identity provider is different from the user specified in the request message.

Cause: For security reasons, the user authenticated at the identity provider must be the same user that was specified in the request.

Action: Verify that the user authenticated at the identity provider is the same user as indicated in the request.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15075: User from existing session ({0}) is different from user received in single sign-on assertion ({1}) for message: {2}.

Cause: The user from the existing session was different than the user in the assertion.

Action: Action is not allowed.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15076: Cannot validate the SubjectConfirmation's InResponseTo field with the authentication request for message {0}

Cause: The value of the InResponseTo field did not correspond to an authentication request.

Action: Contact administrator, remote server, or Oracle Support Services.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15078: Unsupported protocol.

Cause: Protocols supported are Liberty 1.x, SAML1.x/2.0 and WS-Federation.

Action: Ensure the protocol used is either Liberty 1.x or SAML1.x/2.0 or WS-Federation.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15080: The user previously performed a single sign-on operation with a protocol version ({0}) different from SAML2.0.

Cause: The federation was created with a single sign-on of different protocol version.

Action: Single sign-on can only be performed with same protocol version for the particular service provider
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15081: User tried to initiate protocol with a federation belonging to another user.

Cause: User tried to initiate protocol with a federation belonging to another user.

Action: Cannot initiate protocol as another user.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15086: Multiple users are found during attribute responder operation for name identifier: {0} and name identifier format = {1}.

Cause: Multiple users were present in the user data store which satisfies the search criteria of name identifier value.

Action: Check the data store and correct any errors.
Level: 1

Type: WARNING

Impact: Requests/Responses

FED-15088: Multiple users are found during automatic account linking for name identifier: {0} name identifier format: {1} and message: {2}.

Cause: Multiple users were present in the user data store which satisfies the search criteria of name identifier value.

Action: Check the data store and correct any errors.
Level: 1

Type: WARNING

Impact: Requests/Responses

FED-15089: User was not found during attribute responder operation for name identifier: {0} and name identifier format = {1}.

Cause: User was not present in the user data store which satisfies the search criteria of name identifier value.

Action: Check the data store and correct any errors.
Level: 1

Type: WARNING

Impact: Requests/Responses

FED-15091: User was not found during automatic account linking for name identifier: {0} name identifier format: {1} and message: {2}.

Cause: User was not present in the user data store which satisfies the search criteria of name identifier value.

Action: Check the data store and correct any errors.
Level: 1

Type: WARNING

Impact: Requests/Responses

FED-15092: RegisterNameIdentifier was not successful.

Cause: Status of RegisterNameIdentifier response was in error.

Action: Check global name identifier format of this Oracle Identity Federation server or with the uploaded peer provider metadata.
Level: 1

Type: WARNING

Impact: Requests/Responses

FED-15093: A federation for this user does not exist locally: {0}.

Cause: The identity provider sent a federation name identifier, but the federation was not found locally.

Action: Enable auto account linking property for SAML20 protocol to create the federation for this user. Enable allow federation creation property to create the federation for this user.
Level: 1

Type: WARNING

Impact: Requests/Responses

FED-15097: The identity provider sent an assertion with version 2.0 different from the existing single sign-on version: {0} with message: {1}.

Cause: Existing session was not of the single sign-on version 2.0.

Action: Logout the user to delete the existing session.
Level: 1

Type: WARNING

Impact: Requests/Responses

FED-15099: The wtrealm parameter is empty.

Cause: A WS-Federation signin request was received with an empty wtrealm parameter.

Action: Verify that the wtrealm parameter is not empty.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15100: There is no assertion consumer URL in the requester's configuration.

Cause: There was no assertion consumer URL in the requester configuration.

Action: Enter the assertion consumer URL of the requester in the Oracle Identity Federation configuration.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15101: WS-Federation protocol is not enabled.

Cause: The WS-Federation protocol was not enabled in the Oracle Identity Federation configuration.

Action: Enable the WS-Federation protocol in the Oracle Identity Federation configuration.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15102: Default name identifier format for SAML 1.x assertion cannot be processed: {0}

Cause: The default name identifier format cannot be processed.

Action: Verify that the default name identifier format is correct in the Oracle Identity Federation configuration.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15103: Default name identifier format for SAML 1.1 assertion cannot be processed: {0}

Cause: The default name identifier format cannot be processed.

Action: Verify that the default name identifier format is correct in the Oracle Identity Federation configuration.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15104: The user previously performed a single sign-on operation with a protocol version ({0}) different from WS-Fed 1.1.

Cause: The user previously performed a single sign-on operation with a protocol version other than WS-Federation 1.1

Action: No action.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15105: The identity provider sent an assertion with WS-Fed version 1.1 different from the existing single sign-on version: {0}.

Cause: The single sign-on version in the assertion was different than the existing single sign-on version.

Action: Verify that the peer provider is configured to the correct protocol version.
Level: 1

Type: WARNING

Impact: Requests/Responses

FED-15106: Multiple users were found during attribute based authentication using NameID mapping for name identifier: {0} name identifier format: {1} and message: {2}.

Cause: Multiple users were present in the user data store which satisfies the search criteria of name identifier value.

Action: Check the data store and correct any errors.
Level: 1

Type: WARNING

Impact: Requests/Responses

FED-15107: Multiple users were found during attribute based authentication using Attribute mapping for name identifier: {0} name identifier format: {1} and message: {2}.

Cause: Multiple users were present in the user data store which satisfies the search criteria of attribute values.

Action: Check the data store and correct any errors.
Level: 1

Type: WARNING

Impact: Requests/Responses

FED-15108: User was not found during attribute based authentication using NameID mapping for name identifier: {0} name identifier format : {1} and message : {2}.

Cause: User was not present in the user data store which satisfies the search criteria of name identifier value.

Action: Check the data store and correct any errors.
Level: 1

Type: WARNING

Impact: Requests/Responses

FED-15109: User was not found during attribute based authentication using Attribute Mapping for name identifier: {0} and name identifier format : {1} and message : {2}.

Cause: User was not present in the user data store which satisfies the search criteria of attribute values.

Action: Check the data store and correct any errors.
Level: 1

Type: WARNING

Impact: Requests/Responses

FED-15110: User mapping based on name identifier and attribute features are not enabled for attribute based authentication for name identifier: {0} name identifier format: {1} and message: {2}.

Cause: User mapping based on name identifier and attribute features were not enabled for attribute based authentication.

Action: Verify that user mapping based on NameID and attribute features are enabled for attribute based authentication.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15111: The message is not a request security token response: {0}.

Cause: The message received from the identity provider was not a Request Security Token Response.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15112: The message contains an assertion with an empty issuer attribute: {0}.

Cause: The message contained an assertion with an empty issuer attribute.

Action: Verify that the peer provider is configured to use the correct provider ID for the issuer.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15113: The action parameter (wa={0}) is not one of the actions currently recognized by the identity provider.

Cause: The value of the action parameter was not one of the values recognized by Oracle Identity Federation.

Action: Verify that the peer provider is using the correct version of the WS-Federation protocol.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15114: Unknown WS-Federation request message: {0}

Cause: The WS-Federation Request message contained in the wreq parameter is unknown or incorrect.

Action: Contact remote provider.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15115: Error while interacting with remote providers via SOAP protocol.

Cause: An error occurred while sending or receiving a SOAP message to a remote provider.

Action: Check with the peer provider.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15116: The identity provider discovery service returned an empty string as the identity provider.

Cause: The discovery service returned the empty string as the identity provider's provider ID.

Action: The identity provider's providerID parameter should either be missing or contain a value. Check with the discovery service
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15117: The identity provider discovery service returned an empty or null refid.

Cause: The discovery service did not include the required refID parameter.

Action: Check with the discovery service
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15118: Could not find provider ID for issuer of request.

Cause: Oracle Identity Federation cannot identify the SOAP requester as it did not authenticate via HTTP Basic/SSL Client.

Action: Configure OHS so that it protects the SAML 1.x SOAP URL to require HTTP basic authentication or SSL client authentication
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15119: Incoming message does not contain a SAML 1.x Request.

Cause: The incoming SOAP Request does not contain a SAML 1.x request and Oracle Identity Federation was expecting one.

Action: Verify that the SOAP Requestor is sending a SAML 1.x Request; verify that the SOAP Requestor is not sending a non SAML 1.x message to the SAML 1.x SOAP URL
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15120: UserID was not sent from user provisioning system.

Cause: Request from user provisioning system does not contain UserID attribute.

Action: Verify that request from user provisioning system contains UserID attribute
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15121: Attribute response is malformed.

Cause: The attribute response was malformed.

Action: Verify that the attribute response is not malformed.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15122: Unknown identity provider: {0}

Cause: The identity provider is unknown.

Action: Verify that the identity provider is in the federations configuration.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15123: Invalid subject format for protocol version SAML 1.x

Cause: The subject format was invalid.

Action: Verify that the peer provider is using the correct subject format.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15124: Provider federation does not exist for userID: {0}.

Cause: Provider federation has been deleted or the userID is not valid.

Action: Check the request or retry.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15125: Single sign-on response was not signed.

Cause: The single sign-on response signature requirements were not met.

Action: Verify that a signature was present in the single sign-on response and that Oracle Identity Federation is using the correct certificate for signature validation.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15128: An internal error occurred while processing the credentials

Cause: The authentication engine did not return the required refID parameter.

Action: Check that the authentication flow correctly sent the refID parameter to the Oracle Identity Federation server
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15130: AssertionID parameter not present

Cause: The AssertionID was not present in the request.

Action: Verify that the AssertionID is set in the request
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15132: Unknown refID

Cause: Event was already processed.

Action: Check user actions.
Level: 1

Type: ERROR

Impact: Requests/Responses

Cause: Oracle Identity Federation is in High Availability mode and the event data is stored in another server.

Action: Enable session replication between WLS servers or use sticky sessions at the load balancer to force the user to come to the same Oracle Identity Federation server.

Cause: User previously accessed the Oracle Identity Federation server with a different host name than the one in the current request and cookies were not transmitted.

Action: Use the same hostname and fully qualified domain URL to access the Oracle Identity Federation server.

FED-15133: Unknown FedID: {0}

Cause: No federation record exists with specified fedID in the configured federation data store.

Action: Check federation data store configuration and verify that federation record with specified fedID exists in data store.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15134: The service provider could not map the identity provider response to a user

Cause: The Oracle Identity Federation service provider was not able to map the response from the identity provider to a user record.

Action: Check the message sent from the identity provider and error logs in the service provider.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15135: "Unknown Identity Provider; SuccinctID:{0}"

Cause: The identity provider is unknown.

Action: Verify that the identity provider is in the federations configuration.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15136: Unsolicited OpenID Response: {0}

Cause: The OpenID Response received was already processed

Action: Verify the user flow, as the response should only be presented once
Level: 1

Type: ERROR

Impact: Requests/Responses

Cause: The OpenID Response received is unsolicited and the OP could not be determined

Action: Be sure that the OP Endpoint URL is defined in the configuration for this trusted partner

Cause: The OpenID Response received is unsolicited and the OP is not trusted

Action: Contact the OP as the Oracle Identity Federation Server does not support unsolicited responses

FED-15137: Nonce missing from Response

Cause: The Response did not contain a Nonce element

Action: Contact the OP
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15138: The OP sent an authentication response with version OpenID 2.0 different from the existing SSO version: {0} for message: {1}

Cause: Existing session was not of the single sign-on version OpenID 2.0

Action: Logout the user to delete the existing session.
Level: 1

Type: WARNING

Impact: Requests/Responses

FED-15139: OpenID Association Failed with ProviderID: {0}

Cause: The OpenID Association operation failed.

Action: Check the logs for more detailed error messages, and correct the problem related to the error.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15140: OpenID Signature Verification Failed with ProviderID: {0}

Cause: The Signature Verification of the OpenID Message failed

Action: Check the logs for more detailed error messages, and contact the OP
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15141: OpenID Direct Message Verification Failed with ProviderID: {0}

Cause: The OpenID Direct Verification operation failed while validating a response

Action: Check the logs for more detailed error messages, and contact the OP
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15142: OpenID XRDS processing failed with ProviderID: {0}

Cause: The XRDS document is invalid

Action: Check the logs for more detailed error messages, and contact the OP
Level: 1

Type: ERROR

Impact: Requests/Responses

Cause: The XRDS document could not be retrieved

Action: Check the logs for more detailed error messages, and contact the OP

FED-15143: OpenID ClaimedID verification failed against the OP XRDS document for message: {0}

Cause: The XRDS document downloaded from the ClaimedID location does not match the OP's information

Action: Check the logs for more detailed error messages, and contact the OP
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15144: The OpenID RP is unknown

Cause: The OpenID RP is not a known partner: either the RP was not provisioned or Oracle Identity Federation IdP is not configured to interact with Generic OpenID RPs

Action: Add the OpenID RP or the configure Oracle Identity Federation IdP to interact with Generic OpenID RPs if needed
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15145: The Federation SSO operation with the Identity Provider partner {0} failed with the following status: top status={1} secondary status={2} and message={3}

Cause: The Federation SSO operation failed to complete.

Action: Check the message sent from the identity provider and error logs in the service provider.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15146: OAuth Access Token Request operation failed with partner {0} for the Access Token URL {1}

Cause: The Access Token message exchange failed

Action: Check the logs for more detailed error messages and contact the partner
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15147: OAuth Access Token Request operation failed with partner {0} for the resource {1}

Cause: An error occurred while retrieving user data from the partner resource

Action: Check the logs for more detailed error messages and contact the partner
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15148: The OAuth Partner sent an authentication response with version OAuth 2.0 different from the existing SSO version: {0} for message: {1}

Cause: Existing session was not of the single sign-on version OAuth 2.0

Action: Logout the user to delete the existing session.
Level: 1

Type: WARNING

Impact: Requests/Responses

FED-15149: The partner did not return a success response: {0}

Cause: The federation partner returned an error.

Action: Check the message and contact if necessary the partner.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15150: The identity provider sent an assertion with version 1.1 different from the existing single sign-on version: {0} with message: {1}.

Cause: Existing session was not of the single sign-on version 1.1.

Action: Logout the user to delete the existing session.
Level: 1

Type: WARNING

Impact: Requests/Responses

FED-15151: Unsolicited OAuth Response: {0}

Cause: The OAuth Response received was already processed

Action: Verify the user flow, as the response should only be presented once
Level: 1

Type: ERROR

Impact: Requests/Responses

Cause: The OAuth Response received is unsolicited and the IdP could not be determined

Action: Be sure that the IdP Endpoint URL is defined in the configuration for this trusted partner

Cause: The OAuth Response received is unsolicited and the IdP is not trusted

Action: Contact the IdP as the Oracle Identity Federation Server does not support unsolicited responses

FED-18002: The assertion has already been processed: {0}

Cause: The assertion has been replayed.

Action: Verify that the assertion is not replayed.
Level: 1

Type: ERROR

Impact: Security

FED-18004: Attribute authority is not trusted.

Cause: The attribute authority is not marked as trusted in the federations.

Action: Configure the peer provider as a trusted provider to enable protocol exchanges.
Level: 1

Type: ERROR

Impact: Security

FED-18005: Identity provider is not trusted: {0}

Cause: The identity provider is not marked as trusted in the federations.

Action: Verify configuration of the provider in the federations settings of the Oracle Identity Federation configuration.
Level: 1

Type: ERROR

Impact: Security

FED-18006: Message cannot be validated : {0}.

Cause: Incoming message is invalid.

Action: Please check previous log entries for more specific information.
Level: 1

Type: ERROR

Impact: Security

FED-18007: Message has expired or is not yet valid.

Cause: The message validity period has expired.

Action: Verify the time settings between this server and the peer provider are synchronized. Alternatively, the server clock drift can be increased in the Oracle Identity Federation configuration.
Level: 1

Type: ERROR

Impact: Security

FED-18008: Message is not signed.

Cause: The message was not signed.

Action: Verify that the message is signed.
Level: 1

Type: ERROR

Impact: Security

FED-18010: The service provider is not part of the affiliation.

Cause: The provider is not part of the affiliation.

Action: Verify that the provider is part of the affiliation in the federations
Level: 1

Type: ERROR

Impact: Security

FED-18011: Service provider is not trusted.

Cause: Service provider is not in the federations configuration.

Action: Verify configuration of the federations
Level: 1

Type: ERROR

Impact: Security

FED-18012: Assertion cannot be validated: {0}.

Cause: Assertion could not be validated.

Action: Check the message to verify that the assertion is valid, and after check with the peer provider that sent the assertion.
Level: 1

Type: ERROR

Impact: Security

FED-18013: Assertion cannot be validated; confirmation method is missing for message: {0}.

Cause: The confirmation method was missing from the assertion.

Action: Check the message to verify that the assertion is valid, and after check with the peer provider that sent the assertion.
Level: 1

Type: ERROR

Impact: Security

FED-18014: Assertion cannot be validated; InResponseTo is missing for message: {0}.

Cause: The InResponseTo attribute was missing from the assertion.

Action: Check the message to verify that the assertion is valid, and after check with the peer provider that sent the assertion.
Level: 1

Type: ERROR

Impact: Security

FED-18015: Assertion cannot be validated; recipient is missing for message: {0}.

Cause: The recipient was missing from the assertion.

Action: Check the message to verify that the assertion is valid, and after check with the peer provider that sent the assertion.
Level: 1

Type: ERROR

Impact: Security

FED-18016: Assertion cannot be validated; validity time is missing for message {0}.

Cause: The validity time was missing from the assertion.

Action: Check the message to verify that the assertion is valid, and after check with the peer provider that sent the assertion.
Level: 1

Type: ERROR

Impact: Security

FED-18017: The AssertionConsumerServiceURL found in the authentication request message cannot be validated.

Cause: The message was not signed.

Action: Verify that the message was signed.
Level: 1

Type: ERROR

Impact: Security

Cause: URL was not one of the assertion consumer support URL found in the metadata.

Action: Verify that the URL is correct.

FED-18018: Assertion has expired or is not yet valid: {0} for message: {1}

Cause: The assertion validity period has expired.

Action: Verify the time settings between this server and the peer provider are synchronized. Alternatively, the server clock drift can be increased in the admin console.
Level: 1

Type: ERROR

Impact: Security

FED-18020: Authentication request is not signed.

Cause: Authentication request was not signed.

Action: Authentication request needs to be signed.
Level: 1

Type: ERROR

Impact: Security

FED-18027: Evaluation of the assertion's conditions failed.

Cause: Assertion conditions were not valid.

Action: Check logs for more detailed error messages.
Level: 1

Type: ERROR

Impact: Security

FED-18035: URL query signature verification failed.

Cause: The certificate from the remote provider might need to be updated.

Action: Contact remote provider for updated certificate.
Level: 1

Type: ERROR

Impact: Security

Cause: The message or signature may have been tampered with.

Action: Contact administrator to investigate transport error or possible security incident.

FED-18038: Signature verification failed.

Cause: The certificate from the remote provider might need to be updated.

Action: Contact remote provider to update certificate.
Level: 1

Type: ERROR

Impact: Security

Cause: The message or signature may have been tampered with.

Action: Contact administrator to investigate transport error or possible security incident.

FED-18040: Cannot locate temporary federations.

Cause: The temporary federation did not exist, possibly expired.

Action: No Action.
Level: 1

Type: ERROR

Impact: Security

FED-18043: Unexpected recipient: {0} for message: {1}

Cause: The recipient in the assertion did not match the configured provider.

Action: Contact remote provider to verify the provider information.
Level: 1

Type: ERROR

Impact: Security

FED-18045: Unsupported liberty version: {0}

Cause: The version of liberty was not supported.

Action: The supported versions of liberty are 1.1 and 1.2.
Level: 1

Type: ERROR

Impact: Security

FED-18046: Unknown descriptor type: {0}

Cause: Unknown descriptor type .

Action: Contact remote provider for verifying the metadata.
Level: 1

Type: ERROR

Impact: Security

FED-18051: Authentication instant was not sent from the authentication engine.

Cause: The authentication engine did not send an authentication instant.

Action: Check the authentication engine implementation.
Level: 1

Type: WARNING

Impact: Security

FED-18052: Authentication mechanism was not sent from the authentication engine.

Cause: The authentication engine did not send an authentication mechanism.

Action: Check the authentication engine implementation.
Level: 1

Type: WARNING

Impact: Security

FED-18056: Authentication error, the authentication mechanism is not enabled: {0}

Cause: The authentication mechanism used to authenticate the user is disabled.

Action: Enable the authentication mechanism.
Level: 1

Type: ERROR

Impact: Security

Cause: The Authentication Mechanism used to authenticate the user is disabled.

Action: A user tried to use a disabled authentication mechanism/engine to login.

FED-18057: Authentication error, the authentication engine is not enabled: {0}

Cause: The authentication engine used to authenticate the user is disabled.

Action: Enable the authentication engine.
Level: 1

Type: ERROR

Impact: Security

Cause: The Authentication Engine used to authenticate the user is disabled.

Action: A user tried to use a disabled authentication mechanism/engine to login.

FED-18058: Service provider engine error, the service provider engine is not enabled: {0}

Cause: The service provider engine used to integrate with the AAA server is disabled.

Action: Enable the service provider engine.
Level: 1

Type: ERROR

Impact: Security

FED-18059: User from existing session ({0}) is different from user locally authenticated ({1})

Cause: A user already authenticated in Oracle Identity Federation re-authenticated but with a different user ID.

Action: Check the user's activity and session status, and report a possible security incident to the administrator.
Level: 1

Type: ERROR

Impact: Security

FED-18060: User has already existing session with SessionID={0} and the authentication engine specified a different SessionID={1}

Cause: A user already authenticated in Oracle Identity Federation with a SessionID that is different from the one specified by the authentication engine

Action: Check the authentication engine implementation to be sure that it returns the correct SessionID.
Level: 1

Type: ERROR

Impact: Security

FED-18082: Authentication failed: requested authentication method could not be fulfilled by Identity Provider

Cause: The authentication mechanism needs to be set to fulfill the requested authentication method by Service Provider.

Action: Contact the Service provider and set the authentication mechanisms in the Oracle Identity Federation configuration for IdP.
Level: 1

Type: ERROR

Impact: Security

FED-18083: Authentication failed: unknown user attribute for Oracle Access Manager 11g authentication engine: {0}

Cause: The Oracle Identity Federation configuration specifies an unknown HTTP Header containing the UserID.

Action: Check the Oracle Identity Federation configuration for which HTTP Header used by Oracle Access Manager 11g to hold the UserID is specified.
Level: 1

Type: ERROR

Impact: Security

FED-18084: The Partner is not configured to use the Test SP Engine: {0}

Cause: The partner has not been configured to be used with the Test SP Engine.

Action: Configure the Partner.
Level: 1

Type: ERROR

Impact: Security

40 FEDSTS-10102 to FEDSTS-20100

FEDSTS-10102: The LDAP connection settings have not been configured.

Cause: The configuration properties for LDAP connection have not been set.

Action: Enter the LDAP connection settings in the Oracle Identity Federation / Oracle Secure Token Service Data Stores configuration..
Level: 1

Type: ERROR

Impact: Configuration

FEDSTS-10107: Federation does not exist: cannot complete the requested operation

Cause: Federation does not exist for the user with the peer provider.

Action: Verify that the federation exists, or configure the server to create one.
Level: 1

Type: ERROR

Impact: Configuration

FEDSTS-10146: Could not locate the X.509 certificate for {0}, for use {1}

Cause: The X.509 certificate for the given provider and for the specified use was not found.

Action: Check the metadata and the configuration for the given provider.
Level: 1

Type: ERROR

Impact: Configuration

FEDSTS-10152: LDAP BindDN or password is incorrect.

Cause: The LDAP BindDN or password was configured incorrectly.

Action: Check the LDAP configuration entry for BindDN and bind password.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

FEDSTS-10158: Unable to find the exception handler mapping for the exception {0}.

Cause: ExceptionHandler mapping for this exception was missing in the configuration file.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

FEDSTS-10159: Unable to find the request handler mapping for this URL {0}.

Cause: RequestHandler mapping for this URL was missing in the configuration file.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

FEDSTS-10160: Unable to find the response handler mapping for this event response {0}.

Cause: ResponseHandler mapping for this EventResponse cannot be found in configuration file.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

FEDSTS-10161: Unable to locate a mapping for {0}.

Cause: Mapping for this class could not be located.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

FEDSTS-10164: Invalid peer provider configuration for: {0}

Cause: Metadata for this peer provider is invalid.

Action: Load metadata for this peer provider.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

FEDSTS-10168: DiscoveryProvider was not found for {0}.

Cause: A DiscoveryProvider for this type of provider is not configured.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

FEDSTS-10170: Handler was not found for URL: {0}.

Cause: Handler for this response is missing from configuration file.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

FEDSTS-10174: Property was not found: {0}.

Cause: Property is not set in configuration file.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

FEDSTS-10175: First package-search-order is used as default package search order.

Cause: Group of package-search-order was found in configuration file.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: WARNING

Impact: Configuration

FEDSTS-10179: Mapping was not defined for action {0}

Cause: Mapping for the specified action was not defined in the configuration.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: ERROR

Impact: Configuration

FEDSTS-10180: Business Processing Plugin error: {0} does not implement OperationListener

Cause: Business Processing Plugin configuration is incorrect.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

FEDSTS-10181: Property is not type of Boolean: {0}

Cause: Property was not correctly set in configuration file.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

FEDSTS-10182: Property is not of type Long: {0}

Cause: Property was not correctly set in configuration file.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

FEDSTS-10183: Property is not of type Set: {0}

Cause: Property was not correctly set in configuration file.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

FEDSTS-10184: Property is not of type List: {0}

Cause: Property was not correctly set in configuration file.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

FEDSTS-10185: Property is not of type Map: {0}

Cause: Property was not correctly set in configuration file.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

FEDSTS-10186: Property is not of type String: {0}

Cause: Property was not correctly set in configuration file.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

FEDSTS-10203: Property could not be retrieved from the Credential Store Framework: {0}

Cause: The credentials or properties are missing from the credential store.

Action: Enter the properties from Enterprise Manager console, so that it will set them in the Credential Store Framework.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

Cause: The Credential Store Framework did not refresh.

Action: Set the credentials again using Enterprise Manager or restart the WLS Managed Server where Oracle Identity Federation / Oracle Secure Token Service is running.

FEDSTS-10208: Namespace missing in Attribute: {0}

Cause: Namespace missing in Attribute configuration.

Action: Enter the namespace for the attribute in Attribute mapping
Level: 1

Type: WARNING

Impact: Configuration

FEDSTS-10503: The load of configuration for instance{0} failed for element {1} :{2}

Cause: The configuration file may be invalid or the instance and element may not be present

Action: Check the configuration file for validity and make sure the instance and the element exist
Level: 1

Type: ERROR

Impact: Configuration

FEDSTS-10508: Oracle Identity Federation / Oracle Secure Token Service is disabled

Cause: The Oracle Identity Federation / Oracle Secure Token Service is disabled

Action: Check the configuration and enable Oracle Identity Federation / Oracle Secure Token Service if required
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

FEDSTS-11005: Error while deserializing data, mismatched classes while reading database records: expected {0}, got {1}

Cause: The data could not be deserialized.

Action: Check that the entry contains valid data.
Level: 1

Type: ERROR

Impact: Data

FEDSTS-11008: RequestHandlerMapping {0} already exists.

Cause: RequestHandlerMapping was already present.

Action: No Action.
Level: 1

Type: WARNING

Impact: Data

FEDSTS-11009: ResponseHandlerMapping {0} already exists.

Cause: ResponseHandlerMapping was already present.

Action: No Action.
Level: 1

Type: WARNING

Impact: Data

FEDSTS-11010: Replacement RequestHandlerMapping is: {0}.

Cause: RequestHandlerMapping was replaced with the new RequestHandlerMapping.

Action: No Action.
Level: 1

Type: WARNING

Impact: Data

FEDSTS-11011: Replacement ResponseHandlerMapping is: {0}.

Cause: ResponseHandlerMapping was replaced with the new ResponseHandlerMapping.

Action: No Action.
Level: 1

Type: WARNING

Impact: Data

FEDSTS-11013: SQL error while interacting with the database.

Cause: SQL query may not have been properly formed.

Action: Check log entries and database connection configuration.
Level: 1

Type: ERROR

Impact: Data

FEDSTS-11014: Could not add an SQL operation to the Batch Queue

Cause: The SQL operation could not be added because the batch queue might be full

Action: Tune the RBDMS, the JDBC Datasource and the queue settings
Level: 1

Type: ERROR

Impact: Data

FEDSTS-11700: Cannot connect to the LDAP server.

Cause: The LDAP credentials were incorrect.

Action: Verify the LDAP credentials in the Oracle Identity Federation / Oracle Secure Token Service configuration.
Level: 1

Type: ERROR

Impact: Network

FEDSTS-11703: Exception while trying to connect to LDAP server.

Cause: Oracle Identity Federation / Oracle Secure Token Service could not open a connection to the LDAP server.

Action: Verify the connection settings in the Oracle Identity Federation / Oracle Secure Token Service configuration and that LDAP server is up.
Level: 1

Type: ERROR

Impact: Network

FEDSTS-11704: Cannot close LDAP connection.

Cause: Problem while closing the LDAP connection.

Action: Check the LDAP server logs.
Level: 1

Type: WARNING

Impact: Network

FEDSTS-12000: XML time value is empty.

Cause: An empty string was passed in as an XML time value attribute.

Action: Verify that none of the time value attributes are empty.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12003: Unsupported handler parameter type: {0}

Cause: Parameter type was not supported.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

FEDSTS-12007: Data Object {0} is no longer valid.

Cause: Object was destroyed.

Action: No Action.
Level: 1

Type: WARNING

Impact: Other

FEDSTS-12009: Multiple certificates are found for the public key, attempting to select a valid one.

Cause: Multiple certificates were present in the certificate store.

Action: No Action.
Level: 1

Type: WARNING

Impact: Other

FEDSTS-12010: Previous RequestHandlerMapping is replaced with the new RequestHandlerMapping for URL {0}.

Cause: New RequestHandlerMapping was found for this URL.

Action: No Action.
Level: 1

Type: WARNING

Impact: Other

FEDSTS-12011: Previous ResponseHandlerMapping is replaced with the new ResponseHandlerMapping for URL {0}.

Cause: New ResponseHandlerMapping was found for this URL.

Action: No Action.
Level: 1

Type: WARNING

Impact: Other

FEDSTS-12012: Unsupported type for attribute value {0}, type={1}

Cause: One of the retrieved values for the attribute was of an unsupported type.

Action: No Action.
Level: 1

Type: WARNING

Impact: Other

FEDSTS-12013: Discovery Create Exception: unable to create object in the repository: {0}

Cause: Unable to create a data object in the repository.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12014: Discovery Finder Exception: unable to locate object in the repository: {0}

Cause: Unable to locate a data object in the repository.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12015: Federation Exception: error while accessing or creating the federation record of a user: {0}

Cause: An error occured while accessing or creating the federation record of a user.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12017: Communication Exception: unable to communicate with directory or naming service: {0}

Cause: Could not communicate with directory or naming service.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12018: Duplicate Entry Exception: duplicate entry in the data store: {0}

Cause: There was a duplicate entry in the data store.

Action: Check the data store for duplicate entries.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12026: No Such Algorithm Exception: cryptographic algorithm was not recognized: {0}

Cause: An unsupported cryptographic algorithm was specified.

Action: Check to make sure the requested algorithm is correct.
Level: 1

Type: ERROR

Impact: Other

Cause: JCE provider was incorrectly configured.

Action: Check that the JCE provider is configured correctly.

FEDSTS-12028: Notification Processing Exception: could not call the notifier: {0}.

Cause: Could not process the notification.

Action: Please check any plugins or listeners, or contact Oracle Support Services to rectify the issue.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12029: Attribute Processing Exception: error when processing attributes for mapping and filtering: {0}

Cause: Could not process attributes for mapping and filtering.

Action: Check the configuration for assertion attribute mapping and filtering.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12030: IOException: {0}

Cause: There was an error during Input/Output an operation.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12031: NamingException: error while interacting with an LDAP server or JNDI module

Cause: There was an error during interaction with an LDAP or JNDI module

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12032: InterruptedException: thread interrupt occurred during sleep() {0}

Cause: Thread interrupt occurred during sleep() method.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: WARNING

Impact: Other

FEDSTS-12033: Invocation Target Exception: error while invoking method {0}

Cause: There was an error while invoking a method.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12034: No Such Method Exception: a particular method could not be found {0}

Cause: There was an error while finding a method.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12036: Persistence Exception: error while creating or modifying data in the backend store {0}

Cause: Could not create or modify data in the backend store.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12040: Unsupported Encoding Exception: {0}

Cause: The specified character encoding was not supported.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12041: Unknown Provider Exception: {0}

Cause: The specified peer provider was not known.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12043: Discovery Registration Exception: {0}

Cause: An error occurred while registering a Discovery Provider.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12044: No Such Discovery Provider Exception: {0}

Cause: Could not find the specified Discovery Provider.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12045: Parser Configuration Exception: {0}

Cause: An error occurred while parsing an XML document.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12046: Parser Configuration Exception: {0}

Cause: An error occurred while parsing.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12047: SAX Exception: {0}

Cause: An error occurred while handling XML documents.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12048: SOAP Exception: {0}

Cause: An error occurred while handling SOAP messages.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12049: Event Exception: {0}

Cause: An error occurred while processing an Event.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12050: Action Listener Init Exception: {0}

Cause: An error occurred during Action Listener initialization.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12051: Mapping Exception: {0}

Cause: An error occurred while accessing handler mappings.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12052: No Such Target Exception: {0}

Cause: An error occurred while setting up handler mappings.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12053: SAX Parse Exception: {0}

Cause: An error occurred while parsing an XML document.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12054: Malformed URL Exception: {0}

Cause: Either no legal protocol could be found in a specification string or the string could not be parsed.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12055: No Such Mapping Exception: {0}

Cause: Could not find the handler mapping.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12056: Class Not Found Exception: {0}

Cause: Tried to load class with specified name but could not find definition for such class.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12057: Instantiation Exception: {0}

Cause: Tried to load an interface or an abstract class.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12058: Illegal Access Exception: {0}

Cause: Tried to use a field, method, or constructor using reflection, whose definition is not accessible.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12059: Action Registry Exception: {0}

Cause: An error occurred while registering Action Listener.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12060: Service Locator Exception: {0}

Cause: Could not allocate Service Locator.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12061: Algorithm Identifier Exception: {0}

Cause: Inappropriate or unsupported parameters were provided to an algorithm, or an unknown algorithm was requested.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12062: Audit Exception: {0}

Cause: An error occurred while auditing an event.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12063: OPSS Exception: {0}

Cause: An error occurred while using Oracle Platform Security Services libraries.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12064: Exception: {0}

Cause: An error occurred.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12065: Target Exception: {0}

Cause: An error occurred while handling the Target of a Servlet handler.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12066: Servlet Exception: {0}

Cause: An error occurred while initializing or using Servlet.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12067: An HTTP error occurred during SOAP Exchange.

Cause: An HTTP error occurred in SOAP Exchange.

Action: Check Oracle Identity Federation / Oracle Secure Token Service logs for HTTP error code.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12069: Length of input exceeds maximum.

Cause: Length of input exceeds maximum allowed length.

Action: Check that the incoming request is correctly formatted.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12070: No HTTP Message Sender Created

Cause: Could not create the http message sender.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information. Check that http client jar is in the classpath.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12071: A Directory error occurred

Cause: An error occurred while interacting with the Identity Provider module

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12074: PrivilegedActionException: {0}

Cause: PrivilegedExceptionAction while validating Kerberos Token

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12075: LoginException: {0}

Cause: A LoginException occurred while validating kerberos token

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12076: SmeSessionTimeOutException: {0}

Cause: SME session timed out

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12077: Illegal Argument Exception: {0}

Cause: The specified object argument is illegal

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12078: Library Exception: {0}

Cause: An exception occurred while creating library instance

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12079: ResponseHandlerException: {0}

Cause: An exception occurred for the response handler in the library instance

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12080: RequestHandlerException: {0}

Cause: An exception occurred for the request handler in the library instance

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12082: Error while initializing session and user attribute value providers.

Cause: Unknown error while initializing attribute value providers

Action: Check logs and take appropriate action.
Level: 1

Type: WARNING

Impact: Other

FEDSTS-12083: Error while tokenizing attribute value expression.

Cause: Invalid attribute value expression.

Action: Fix the attribute value expression to contain valid tokens.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12084: Error while translating attribute value expression.

Cause: Invalid attribute value expression.

Action: Fix the attribute value expression to contain valid tokens.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12503: Certificate Exception: {0}.

Cause: A certificate exception occurred, indicating a problem with one of the certificates.

Action: Check logs and exception message for more information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12523: Crypto Exception: {0}.

Cause: A crypto exception has occurred during token issuance.

Action: Check logs and exception message for more information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-13003: Remove operation not supported.

Cause: The Iterator method remove() was invoked, but is not supported by the implementation.

Action: Replace the remove operation with alternate remove option.
Level: 1

Type: ERROR

Impact: Programmatic

FEDSTS-13004: EntrySet operation not supported.

Cause: The SoftHashMap method entrySet() was invoked, but is not supported by the implementation.

Action: Replace the call to entrySet() with alternate option.
Level: 1

Type: ERROR

Impact: Programmatic

FEDSTS-13006: Internal Error: Unable to register {0} as a provider for {1}

Cause: Unable to register Discovery Provider.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Programmatic

FEDSTS-13009: Cannot have an empty response name.

Cause: Response name was empty.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

FEDSTS-13010: Cannot locate class with root name of {0}

Cause: Could not locate class.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

FEDSTS-13011: Deregistering object failed.

Cause: Deregistered object does not match expected object.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

FEDSTS-13013: Internal Server Error

Cause: Internal Server Error

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

FEDSTS-13014: Servlet cannot be configured.

Cause: Servlet configuration failed.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

FEDSTS-13017: Initializing {0}

Cause: An internal error has occurred.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

FEDSTS-13022: Metric End event occured for event {0} before respective event start

Cause: End/Abort event occurred before respective start event

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: NOTIFICATION

Impact: Programmatic

FEDSTS-15002: Cannot find User for UserID {0} in User Data Store.

Cause: The user ID was incorrect or the user record does not exist.

Action: Verify that the user ID is correct.
Level: 1

Type: ERROR

Impact: Requests/Responses

FEDSTS-15003: No value in user record for NameIDPolicy requested: {0}

Cause: There was no value for the requested name identifier type.

Action: Verify that name identifier is correct and that the attribute for the requested name identifier exists.
Level: 1

Type: ERROR

Impact: Requests/Responses

FEDSTS-15040: SSL client certificate required to access SOAP service URL

Cause: No SSL Certificate was presented when accessing the SOAP service.

Action: Contact the client to notify that an SSL Certificate is required when accessing the SOAP service.
Level: 1

Type: ERROR

Impact: Requests/Responses

FEDSTS-15046: Unexpected confirmation method: {0} for message: {1}

Cause: Oracle Identity Federation / Oracle Secure Token Service did not recognize the specified confirmation.

Action: Check that the confirmation method included in the Assertion is valid.
Level: 1

Type: ERROR

Impact: Requests/Responses

FEDSTS-15048: Unknown condition in assertion: {0}.

Cause: Oracle Identity Federation / Oracle Secure Token Service did not recognize the specified condition.

Action: Check that the condition included in the assertion is valid.
Level: 1

Type: ERROR

Impact: Requests/Responses

FEDSTS-15049: The contents of the SOAP request body are null. Closing the connection.

Cause: The Oracle Identity Federation / Oracle Secure Token Service server encountered an error while trying to deserialize the incoming message.

Action: Check that the message is correctly formatted.
Level: 1

Type: ERROR

Impact: Requests/Responses

FEDSTS-15052: A time value is invalid

Cause: A string was passed in as a time value that was in an invalid format.

Action: Verify that all of the time value attributes are in the correct format.
Level: 1

Type: ERROR

Impact: Requests/Responses

FEDSTS-15056: Invalid version number: {0}

Cause: The version format was incorrect.

Action: Verify that the version format is correct. Version should consist of a major part and a minor part separated by a period.
Level: 1

Type: ERROR

Impact: Requests/Responses

FEDSTS-15057: Invalid version: {0}, majorVersion={1}, minorVersion={2}

Cause: Either the major or the minor version was negative.

Action: Verify that both the major and minor versions are non-negative.
Level: 1

Type: ERROR

Impact: Requests/Responses

FEDSTS-15058: Error while processing the SOAP envelope.

Cause: Oracle Identity Federation / Oracle Secure Token Service could not process the incoming SOAP envelope.

Action: Check that the SOAP envelope format is correct.
Level: 1

Type: ERROR

Impact: Requests/Responses

FEDSTS-15060: Unknown message parameter: {0}

Cause: One of the message parameters was not recognized.

Action: Verify that all of the message parameter names are recognized by Oracle Identity Federation / Oracle Secure Token Service.
Level: 1

Type: ERROR

Impact: Requests/Responses

FEDSTS-15083: There is no value for a parameter.

Cause: Parameter was sent without a value.

Action: Ensure that the parameters are passed with valid value.
Level: 1

Type: INCIDENT_ERROR

Impact: Requests/Responses

FEDSTS-15084: The response handler expects an event response that implements Target.

Cause: EventResponse object was not of the type Target.

Action: Pass EventResponse object of the type Target to the response handler.
Level: 1

Type: INCIDENT_ERROR

Impact: Requests/Responses

FEDSTS-15085: Throwing a runtime exception.

Cause: An internal error has occurred.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: INCIDENT_ERROR

Impact: Requests/Responses

FEDSTS-15098: Unknown condition ignored: {0}.

Cause: Peer provider sent a message which contains unknown conditions in the message.

Action: Check with the peer provider.
Level: 1

Type: WARNING

Impact: Requests/Responses

FEDSTS-15131: Certificate was missing when trying to verify digital signature.

Cause: Certificate missing when trying to verify incoming signature.

Action: Verify that the requester specified its identity when making the request, either in the message or by authenticating to the Oracle Identity Federation / Oracle Secure Token Service server via SSL or HTTP Basic Authentication
Level: 1

Type: ERROR

Impact: Requests/Responses

FEDSTS-15536: Certificate Validation failed for certificate {0}

Cause: The certificate could not be validated

Action: Check the certificate and/or add the necessary Trust Anchor
Level: 1

Type: ERROR

Impact: Requests/Responses

FEDSTS-15539: The partner identified by {0} is unknown

Cause: The referenced entity is not a partner

Action: Create a partner entry if necessary
Level: 1

Type: ERROR

Impact: Requests/Responses

FEDSTS-15540: The partner is not trusted: {0}

Cause: The partner is not marked as trusted

Action: Verify the configuration of the partner
Level: 1

Type: ERROR

Impact: Requests/Responses

FEDSTS-15542: The mapping of the AppliesTo element from the WS-Trust Request to a Relying Party Partner failed: could not map {0}

Cause: The location referenced in the AppliesTo element could not be mapped to Resource URL of one of the Relying Party Partners defined in Oracle Identity Federation / Oracle Secure Token Service

Action: If the location referenced in the AppliesTo element should have been mapped to a Relying Party Partner then verify that the Resource URLs defined for this Partner in Oracle Identity Federation / Oracle Secure Token Service are correct.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

FEDSTS-18003: Assertion is not signed.

Cause: The assertion was not signed.

Action: Verify that the assertion was signed.
Level: 1

Type: ERROR

Impact: Security

FEDSTS-18009: Provider is unknown: {0}

Cause: The provider is not known.

Action: Verify that the provider exists in the list of federations
Level: 1

Type: ERROR

Impact: Security

FEDSTS-18026: Error while reading the client SSL certificate

Cause: Client SSL certificate is corrupt.

Action: Obtain a new client SSL certificate.
Level: 1

Type: ERROR

Impact: Security

FEDSTS-18034: Untrusted server certificate chain.

Cause: Certificate Authority certification keystore in JRE did not contain the Certificate Authority certificate.

Action: Add the Certificate Authority certificate of the LDAP server to the Certificate Authority certs keystore of the JRE.
Level: 1

Type: ERROR

Impact: Security

FEDSTS-18041: Illegal UTF encoding

Cause: The UTF encoding was not supported.

Action: Verify the UTF encoding to be a valid one.
Level: 1

Type: ERROR

Impact: Security

FEDSTS-18047: Certificate {0} is replaced with the certificate {1}.

Cause: Old certificate was replaced with the newer one.

Action: Ensure correct certificate is uploaded for normal functioning of the Oracle federation server.
Level: 1

Type: WARNING

Impact: Security

FEDSTS-18048: The certificate corresponding to the private key is expired: {0}

Cause: The certificate was expired.

Action: Use the certificate with the correct validity period.
Level: 1

Type: WARNING

Impact: Security

FEDSTS-18049: Public key algorithm is not known:{0}.

Cause: Public key algorithm was unknown.

Action: Use the correct certificate with the correct public key algorithm.
Level: 1

Type: WARNING

Impact: Security

FEDSTS-18050: User is not authenticated.

Cause: User was not authenticated.

Action: Login to the server using the correct user.
Level: 1

Type: WARNING

Impact: Security

FEDSTS-18055: Unknown pseudo-random number generator configured. Using Java default.

Cause: Default pseudo-random number generator configured is unknown.

Action: No Action.
Level: 1

Type: NOTIFICATION

Impact: Security

FEDSTS-18066: Authentication failed

Cause: The authentication process failed, the credentials could not be validated.

Action: Check that the user entered the correct credentials.
Level: 1

Type: WARNING

Impact: Security

Cause: The authentication process failed, the credentials could not be validated.

Action: Check the connection settings.

FEDSTS-18073: An error occurred during a cryptographic operation: {0}

Cause: The Oracle Identity Federation / Oracle Secure Token Service encountered an error while invoking the crypto engine for signature creation/verification, encryption/decryption operations.

Action: Check the logs for more detailed error messages, and correct the problem related to the error.
Level: 1

Type: ERROR

Impact: Security

FEDSTS-18074: Signature verification failed for provider ID {0}

Cause: The certificate from the remote provider might need to be updated.

Action: Contact remote provider to update certificate.
Level: 1

Type: ERROR

Impact: Security

Cause: The signature might be have been spoofed.

Action: Contact Administrator to verify

FEDSTS-18075: Decryption operation failed for message sent by provider ID {0}

Cause: The Oracle Identity Federation / Oracle Secure Token Service metadata at the remote provider could be outdated.

Action: Contact remote provider to uptake the latest Oracle Identity Federation / Oracle Secure Token Service metadata containing the latest encryption certificate
Level: 1

Type: ERROR

Impact: Security

Cause: The message is not intended for Oracle Identity Federation / Oracle Secure Token Service.

Action: Contact Administrator to verify

FEDSTS-18076: Security services exception: {0}

Cause: An error occurred while verifying/signing/encrypting/decrypting a message.

Action: Please check previous log entries for more specific information.
Level: 1

Type: ERROR

Impact: Security

FEDSTS-18077: XML decryption error: EncryptedData element not found

Cause: The XML EncryptedData element was not found when trying to decrypt the incoming data.

Action: Check the message and contact the remote server administrator if necessary.
Level: 1

Type: ERROR

Impact: Security

FEDSTS-18078: XML decryption error: could not get the decryption secret key

Cause: The key to decrypt the EncryptedData element could not be retrieved.

Action: Check the message and contact the remote server administrator if necessary.
Level: 1

Type: ERROR

Impact: Security

FEDSTS-18079: The return URL could not be validated: {0}

Cause: The specified return URL could not be validated against the list of approved hostnames/domains.

Action: Check if the return URL points to a valid host name/domain, and update if necessary the list of approved host names/domains. If the return URL is not recognized or invalid, do not update the list of approved host names/domains.
Level: 1

Type: ERROR

Impact: Security

FEDSTS-18080: Could not retrieve key from the key store. Please verify that the key password is equal to the key store password.

Cause: Invalid key or key password is not equal to the key store password.

Action: Verify that the key is valid and the key password is equal to the key store password.
Level: 1

Type: ERROR

Impact: Security

FEDSTS-18081: Authentication Failed - HTTP Header not set in order to authenticate the user

Cause: The HTTP Header was not set in order to authenticate the user.

Action: Check the User's browser, Agent used in the deployment, the Oracle Identity Federation / Oracle Secure Token Service configuration and whether or not the user was authenticated by the Web Access Management
Level: 1

Type: ERROR

Impact: Security

FEDSTS-20000: Cannot open the key store.

Cause: Invalid or unsupported key store, or incorrect password. During installation, this error is expected.

Action: Verify that password is correct and the store is a valid PKCS #12 PFX wallet or Java KeyStore file. During installation, this error can be ignored.
Level: 1

Type: ERROR

Impact: Session

FEDSTS-20100: The Oracle Identity Federation / Oracle Secure Token Service transient data store cleanup process was unexpectedly terminated.

Cause: The cleanup process could not connect the Oracle Identity Federation / Oracle Secure Token Service transient data store, or an error occurred while destroying expired entries.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service transient data store.
Level: 1

Type: ERROR

Impact: Threads

41 FRC-60000 to FRC-60107

FRC-60000: fatal error configuring FRCommon component

Cause: FRCommon component provisioning failed.

Action: Examine the stack trace that accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

FRC-60001: fatal error removing FRCommon component

Cause: FRCommon component deprovisioning failed.

Action: Examine the stack trace that accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

FRC-60002: failed to load the registration document {0}

Cause: An error occurred while reading the FRCommon component registration document.

Action: Do one of the following: 1. Make sure that the registration document is valid. 2. If the registration document is accidentally deleted or modified then reinstall ORACLE_HOME.
Level: 1

Type: ERROR

Impact: Configuration

FRC-60003: error reading ORACLE_HOME registry file {0}

Cause: An error occurred while reading the ORACLE_HOME registry file.

Action: Do one of the following: 1. Make sure that the ORACLE_HOME registry file exists. 2. If the ORACLE_HOME registry file is accidentally deleted or modified then reinstall ORACLE_HOME.
Level: 1

Type: ERROR

Impact: Configuration

FRC-60004: I/O error reading CA preferences file {0}

Cause: An I/O error occurred while reading the CA preferences file.

Action: Examine the stack trace that accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

FRC-60101: error converting the configuration object to the relevant CompositeType

Cause: Failed to convert the configuration object to the relevant CompositeType.

Action: Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

FRC-60102: error converting the configuration object to the relevant CompositeData

Cause: Failed to convert the configuration object to the relevant CompositeData.

Action: Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

FRC-60103: error registering child config mbean for the application section {0}

Cause: Failed to register the child config mbean for the given application section.

Action: Examine the stack trace which accompanies this message for the possible cause of failures and correct it.
Level: 1

Type: ERROR

Impact: Configuration

FRC-60104: error deregistering child config mbean for the application section {0}

Cause: Failed to deregister the child config mbean for the given application section.

Action: Examine the stack trace which accompanies this message for the possible cause of failures and correct it.
Level: 1

Type: ERROR

Impact: Configuration

FRC-60105: error deleting application section {0}

Cause: An attempt was made to delete the default application section or a section that does not exist.

Action: Choose the correct section name.
Level: 1

Type: ERROR

Impact: Configuration

FRC-60106: error creating application section {0}

Cause: An attempt was made to create an application section that already exists or has an invalid section name.

Action: Choose an alternative name for the section.
Level: 1

Type: ERROR

Impact: Configuration

FRC-60107: error duplicating application section {0} to {1}

Cause: Failed to duplicate an application section because of one of the following reasons: 1. An attempt was made to duplicate an invalid application section. 2. An attempt was made to create an application section that already exists.

Action: Do one of the following: 1. Choose a correct section name for the duplicated application section. 2. Choose an alternative name for the newly created application section.
Level: 1

Type: ERROR

Impact: Configuration

42 FRM-41838 to FRM-99999

FRM-41838: runtime process unable to open temporary record buffer file {0}

Cause: The runtime process was unable to open the file used as the temporary record buffer.

Action: Verify that the file system or directory in which the file resides exists and that the runtime process has permissions to read and write to the file system or directory.
Level: 1

Type: ERROR

Impact: Files

FRM-41839: runtime process: disk I/O error on temporary record buffer file {0}

Cause: An I/O error occurred while the runtime process was attempting to read or write a record to the temporary record buffer file.

Action: Verify that the file system or directory in which the file resides exists, and that the runtime process has permissions to read and write to the file system or directory, and that the file system contains sufficient space.
Level: 1

Type: ERROR

Impact: Files

FRM-60000: fatal error configuring Forms component

Cause: Forms component provisioning failed.

Action: Examine the stack trace that accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

FRM-60001: fatal error removing Forms component

Cause: Forms component deprovisioning failed.

Action: Examine the stack trace that accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

FRM-60002: error reading Forms component registration document {0}

Cause: An error occurred while reading the Forms component registration document.

Action: Do one of the following: 1. Make sure that the registration document is valid. 2. If the registration document is accidentally deleted or modified then reinstall ORACLE_HOME.
Level: 1

Type: ERROR

Impact: Configuration

FRM-60003: error reading ORACLE_HOME registry file {0}

Cause: An error occurred while reading the ORACLE_HOME registry file.

Action: Do one of the following: 1. Make sure that the ORACLE_HOME registry file exists. 2. If ORACLE_HOME registry file is accidentally deleted or modified then reinstall ORACLE_HOME.
Level: 1

Type: ERROR

Impact: Configuration

FRM-60004: error obtaining text contents of the configuration file {0}

Cause: Failed to read the text contents of the configuration file.

Action: Examine the stack trace which accompanies this message for the possible cause of failures and correct it.
Level: 1

Type: ERROR

Impact: Configuration

FRM-60005: Directory {0} exists; renaming it to {1}.

Cause: The subdirectory under the Oracle Instance directory already exists and the provisioning process renamed the existing subdirectory.

Action: No action is required.
Level: 1

Type: WARNING

Impact: Configuration

FRM-60101: error registering Forms J2EE application mbeans during the application startup

Cause: An error occurred while registering the Forms J2EE application runtime mbean or custom configuration files mbeans.

Action: Examine the stack trace that accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

FRM-60102: error deregistering Forms J2EE application mbeans during the application shutdown

Cause: An error occurred while deregistering the Forms J2EE application runtime mbean or custom configuration files mbeans.

Action: Examine the stack trace that accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

FRM-60103: invalid or missing ODL configuration file {0}

Cause: A fatal error occurred while reading the logging configuration file.

Action: Do one of the following: 1. Make sure that the ODL configuration file exists and it does not have any syntax errors caused by accidental modification. 2. Make sure that the domain is updated with the JRF template. 3. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

FRM-60104: Forms is not configured under Oracle Instance {0}. Aborting deployment of Forms J2EE application {1}.

Cause: An attempt was made to deploy the Forms J2EE application without configuring the Forms component under Oracle Instance.

Action: Provision the Forms component before deploying the Forms J2EE application.
Level: 1

Type: ERROR

Impact: Configuration

FRM-60105: Forms is configured in non-sso mode.

Cause: The user configured Forms in non-sso mode.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

FRM-60106: Forms is configured in non-sso mode: No install plan provided during deployment.

Cause: The user deployed the Forms J2EE application using WLST or WLS admin console.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

FRM-60107: error reading the install plan {0}

Cause: An error occurred reading the install plan due to one of the following reasons: 1. Invalid entries in the install plan. 2. Inadequate privilege to access the install plan.

Action: Examine the stack trace that accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

FRM-60108: error creating Forms J2EE application handler entry in the ODL configuration file {0}

Cause: An error occurred while creating the Forms J2EE application handler entry in the ODL configuration file.

Action: Examine the stack trace that accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

FRM-60109: error reading the ODL configuration file {0}

Cause: An error occurred reading the ODL configuration file.

Action: Examine the stack trace that accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

FRM-60110: error writing to the ODL configuration file {0}

Cause: An error occurred writing to the ODL configuration file.

Action: Examine the stack trace that accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

FRM-60111: error removing Forms J2EE application handler entry from the ODL configuration file {0}

Cause: An error occurred while removing the Forms J2EE application handler entry from the ODL configuration file.

Action: Examine the stack trace that accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

FRM-60112: error registering Forms J2EE application with the Forms Component MBean

Cause: An error occurred while registering the Forms J2EE application with the Forms Component MBean.

Action: Examine the stack trace that accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

FRM-60113: error deregistering Forms J2EE application with the Forms Component MBean

Cause: An error occurred while deregistering the Forms J2EE application with the Forms Component MBean.

Action: Examine the stack trace that accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

FRM-60114: error reading default configuration path

Cause: An error occurred while obtaining the default configuration location using JMX Framework.

Action: Examine the stack trace that accompanies this message. If the stack trace indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

FRM-60201: error reading OID properties file {0}

Cause: An error occurred while reading the OID properties file.

Action: Examine the stack trace that accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

FRM-60202: Forms J2EE application {0} is already registered with OID host {1} under the container {2}. Deregistering it.

Cause: An attempt was made to re-create an existing Forms J2EE application footprint in OID. This may occur when the same Forms J2EE application is redeployed to the domain.

Action: No action is required.
Level: 1

Type: WARNING

Impact: Configuration

FRM-60203: error creating Forms J2EE application {0} footprint in OID host {1}

Cause: The Forms application footprint in OID failed to be created due to one of the following causes: 1. OID was not accessible. 2. The Forms J2EE application footprint password failed to be seeded in CSF on the mid-tier. 3. An I/O error occurred during storing of OID information from the Forms OID properties file.

Action: Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

FRM-60204: error deregistering Forms J2EE application {0} footprint in OID host {1}

Cause: An error status was returned while deregistering the Forms J2EE application with OID.

Action: Do one of the following: 1. Examine the stack trace which accompanies this message, look for status of the IM tier and resolve the issue. 2. If using Fusion Middleware Control, make sure that information passed to deregister the Forms J2EE application with OID host is valid. 3. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

FRM-60205: error removing the Forms J2EE application {0} footprint from OID host {1}

Cause: Failed to remove the Forms J2EE application footprint from OID due to one of the following causes: 1. OID was not accessible. 2. An error status was returned while deregistering the Forms J2EE application footprint with OID. 3. Failed to fetch the Forms J2EE application footprint password from CSF on the mid-tier. 4. An I/O error occurred while cleaning OID information from the Forms OID properties file.

Action: Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

FRM-60207: error storing credentials to CSF

Cause: Failed to store the credentials to CSF.

Action: Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

FRM-60208: error deleting credentials from CSF

Cause: Failed to delete the credentials from CSF.

Action: Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

FRM-60209: error obtaining credentials from CSF

Cause: Failed to get the credentials from CSF.

Action: Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

FRM-60210: error obtaining MBean Server connection

Cause: Failed to connect to the MBean Server.

Action: Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

FRM-60301: invalid character in the file name argument {0}

Cause: An error occurred due to an invalid character in the file name.

Action: Remove the invalid charecter from the file name and execute the operation again.
Level: 1

Type: ERROR

Impact: Configuration

FRM-60302: error duplicating the configuration file {0} to {1}

Cause: An error occurred duplicating the configuration file due to one of the following causes: 1. MBean registration failed. 2. Failure to create a new file on the file system.

Action: Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

FRM-60303: error duplicating the configuration file {0}: invalid document type {1}

Cause: Invalid document type argument passed to operation.

Action: Invoke the 'duplicate file' operation only on the supported valid document types (Type_default.env).
Level: 1

Type: ERROR

Impact: Configuration

FRM-60304: error duplicating configuration file {0}: invalid argument {1} are passed to 'duplicate file' operation

Cause: The file the user tried to create already exists.

Action: Pass a different file name for the new file that has to be created.
Level: 1

Type: ERROR

Impact: Configuration

FRM-60305: error deleting the configuration file {0}

Cause: An error occurred deleting the configuration file due to one of the following causes: 1. MBean deregistration failed. 2. Failure to delete the file from the file system.

Action: Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

FRM-60306: error deleting the configuration file {0}: invalid document type {1}

Cause: An invalid document type argument was passed to the operation.

Action: Invoke the 'duplicate file' operation only on the supported valid document types (Type_default.env).
Level: 1

Type: ERROR

Impact: Configuration

FRM-60307: error converting the configuration object to the relevant CompositeType

Cause: Failed to convert the configuration object to the relevant CompositeType.

Action: Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

FRM-60308: error converting the configuration object to the relevant CompositeData

Cause: Failed to convert the configuration object to the relevant CompositeData.

Action: Examine the stack trace which accompanies this message for the possible cause of failures and correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

FRM-60309: error registering child config mbean for the application section {0}

Cause: Failed to register the child config mbean for the given application section.

Action: Examine the stack trace which accompanies this message for the possible cause of failures and correct it.
Level: 1

Type: ERROR

Impact: Configuration

FRM-60310: error deregistering child config mbean for the application section {0}

Cause: Failed to deregister the child config mbean for the given application section.

Action: Examine the stack trace which accompanies this message for the possible cause of failures and correct it.
Level: 1

Type: ERROR

Impact: Configuration

FRM-60311: error deleting application section {0}

Cause: An attempt was made to delete the default application section or a section that does not exist.

Action: Choose the correct section name.
Level: 1

Type: ERROR

Impact: Configuration

FRM-60312: error creating application section {0}

Cause: An attempt was made to create an application section that already exists or has an invalid section name.

Action: Choose an alternative name for the section.
Level: 1

Type: ERROR

Impact: Configuration

FRM-60313: error duplicating application section {0} to {1}

Cause: Failed to duplicate an application section because of one of the following reasons: 1. An attempt was made to duplicate an invalid application section. 2. An attempt was made to create an application section that already exists.

Action: Do one of the following: 1. Choose a correct section name for the duplicated application section. 2. Choose an alternative name for the newly created application section.
Level: 1

Type: ERROR

Impact: Configuration

FRM-91108: internal error in runtime process: unable to initialize PL/SQL

Cause: An unexpected error occurred while the runtime process was attempting to initialize PL/SQL.

Action: If the problem persists, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

FRM-91109: internal error in runtime process: application startup failure

Cause: An unexpected error occurred while the runtime process was attempting to start the Toolkit component.

Action: If the problem persists, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

FRM-91111: internal error in runtime process: window system startup failure

Cause: An unexpected error occurred while the runtime process was attempting to start the window system.

Action: If the problem persists, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

FRM-91112: internal error in runtime process: resource manager startup failure

Cause: An unexpected error occurred while the runtime process was attempting to start the Toolkit Resource Manager.

Action: If the problem persists, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

FRM-91116: internal error in runtime process: Oracle*Image startup failure

Cause: An unexpected error occurred while the runtime process was attempting to start Oracle*Image.

Action: If the problem persists, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

FRM-91119: internal error in runtime process: Oracle*VGS startup failure

Cause: An unexpected error occurred while the runtime process was attempting to start Oracle*VGS.

Action: If the problem persists, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

FRM-91124: fatal error in runtime process: {0} specified for FORMS_DECIMAL_PREFIX. Should be zero or the empty string

Cause: An invalid value was specified for the environment variable FORMS_DECIMAL_PREFIX.

Action: Do one of the following: 1. Specify FORMS_DECIMAL_PREFIX as '0' to force a zero before a leading decimal point in any number displayed without a format mask in the application. 2. Specify FORMS_DECIMAL_PREFIX as '' (the empty string).
Level: 1

Type: ERROR

Impact: Configuration

FRM-91126: fatal error in runtime process: invalid value {0} specified for environment variable {1}

Cause: An invalid environment variable value was specified. An example would be an invalid timezone for an environment variable that specifies a timezone.

Action: Correct the environment variable value.
Level: 1

Type: ERROR

Impact: Configuration

FRM-91127: fatal error in runtime process: invalid directory name specified for environment variable {0}

Cause: An invalid value was specified for an environment variable that represents the name of a directory. Specifically, the value is too long: either it is itself longer than a system-imposed maximum, or a subdirectory name that Forms needs to construct would be longer than the system-imposed maximum.

Action: Correct the environment variable value.
Level: 1

Type: ERROR

Impact: Configuration

FRM-91128: runtime process warning: invalid value {0} specified for environment variable {1}; using default %s

Cause: An invalid environment variable value was specified. The indicated default value was used, and processing continued.

Action: Correct the environment variable value.
Level: 1

Type: WARNING

Impact: Configuration

FRM-91129: fatal error in runtime process: no value specified for required environment variable {0}

Cause: A required environment variable was not set or was set to the empty string.

Action: Set the environment variable to a non-empty value.
Level: 1

Type: ERROR

Impact: Configuration

FRM-91130: fatal error in runtime process: timezone file {0} is missing

Cause: The timezone file (specified by the environment variable FORMS_TZFILE) was not found.

Action: Correct the FORMS_TZFILE environment variable value. It should specify $ORACLE_HOME/oracore/zoneinfo/timezone.dat or $ORACLE_HOME/oracore/zoneinfo/timezlrg.dat.
Level: 1

Type: ERROR

Impact: Configuration

FRM-91131: fatal error in runtime process: timezone file {0} not loaded - required memory unavailable

Cause: The timezone file (specified by the environment variable FORMS_TZFILE) could not be loaded. This probably indicates insufficient swap space.

Action: Increase the size of the swap file.
Level: 1

Type: ERROR

Impact: Configuration

FRM-91132: fatal error in runtime process: invalid data in timezone file {0}

Cause: The timezone file (specified by the environment variable FORMS_TZFILE) was found to contain invalid data.

Action: Correct the FORMS_TZFILE environment variable value. It should specify $ORACLE_HOME/oracore/zoneinfo/timezone.dat or $ORACLE_HOME/oracore/zoneinfo/timezlrg.dat.
Level: 1

Type: ERROR

Impact: Configuration

FRM-91135: fatal error in runtime process: message file {0} is missing

Cause: The specified message file was not found.

Action: Verify that the file has not been moved or deleted. If necessary, reinstall it.
Level: 1

Type: ERROR

Impact: Configuration

FRM-91143: internal error in runtime process: unable to create runform global context

Cause: An unexpected error occurred while the runtime process was attempting to create the runform global context.

Action: If the problem persists, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

FRM-91144: internal error in runtime process: unable to parse user name

Cause: An unexpected error occurred while the runtime process was attempting to parse the user name.

Action: If the problem persists, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

FRM-91150: internal error in runtime process: unable to initialize Oracore program manager

Cause: An unexpected error occurred while the runtime process was attempting to initialize the Oracore program manager.

Action: If the problem persists, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

FRM-91151: internal error in runtime process: unable to initialize Oracle NLS

Cause: An unexpected error occurred while the runtime process was attempting to initialize Oracle NLS.

Action: If the problem persists, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

FRM-91152: internal error in runtime process: unable to set environment variable {0}

Cause: An unexpected error occurred while the runtime process was attempting to set an environment variable to a new value.

Action: If the problem persists, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

FRM-91153: internal error in runtime process: unable to initialize Common Area component

Cause: An unexpected error occurred while the runtime process was attempting to initialize the Common Area component.

Action: If the problem persists, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

FRM-91154: internal error in runtime process: unable to initialize Oracore date component

Cause: An unexpected error occurred while the runtime process was attempting to initialize the Oracore date component.

Action: If the problem persists, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

FRM-91157: internal error in runtime process: unable to redirect stderr to stdout

Cause: An unexpected error occurred while the runtime process was attempting to redirect stderr to stdout. This error should never occur at a customer site.

Action: If the problem persists, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

FRM-91170: runtime process: JVM exiting with code {0}

Cause: The runtime process had started a JVM (in order to run Oracle Reports or the Forms debugger, or to update a password in Oracle Internet Directory). That JVM started exiting.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Process

FRM-91171: runtime process: JVM aborting

Cause: The runtime process had started a JVM (in order to run Oracle Reports or the Forms debugger, or to update a password in Oracle Internet Directory). That JVM started aborting.

Action: No action is required. However, if there appear to be problems running Oracle Reports or the Forms debugger, or updating a password in Oracle Internet Directory, this message may help to indicate the cause.
Level: 1

Type: NOTIFICATION

Impact: Process

FRM-91190: fatal error in runtime process: unable to allocate {0} bytes of memory

Cause: A critical memory allocation request failed. This may indicate insufficient swap space. Execution of the runtime process was terminated.

Action: Increase the size of the swap file.
Level: 1

Type: ERROR

Impact: Memory

FRM-91191: runtime process: unable to allocate {0} bytes of memory; attempting to continue execution

Cause: A memory allocation request failed. This may indicate insufficient swap space. Execution continued, but the current operation (e.g. the loading of a form) failed. And a subsequent critical memory allocation may have failed, thereby terminating the runtime process.

Action: Increase the size of the swap file.
Level: 1

Type: ERROR

Impact: Memory

FRM-91193: runtime process: unable to memory-map {0} bytes of memory; attempting to continue execution

Cause: A memory-map request failed. This probably indicates insufficient swap space. Execution continued, but the current operation (e.g. the loading of a form) failed. And a subsequent critical memory allocation may have failed, thereby terminating the runtime process.

Action: Increase the size of the swap file.
Level: 1

Type: ERROR

Impact: Memory

FRM-91199: internal error in runtime process: assertion failure: file {0}, line {1}

Cause: An assertion failed in code that the runtime process was executing.

Action: If the problem persists, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

FRM-91200: fatal error in runtime process: error reading HTTP header

Cause: A fatal error occurred while attempting to read an HTTP header.

Action: Check for problems on the network that connects the Forms Java Client with the Forms Listener Servlet and the runtime process.
Level: 1

Type: ERROR

Impact: Network

FRM-91210: fatal error in runtime process: error reading HTTP data

Cause: A fatal error occurred while attempting to read HTTP data.

Action: Check for problems on the network that connects the Forms Java Client with the Forms Listener Servlet and the runtime process.
Level: 1

Type: ERROR

Impact: Network

FRM-91220: fatal error in runtime process: error writing HTTP data

Cause: A fatal error occurred while attempting to write HTTP data.

Action: Check for problems on the network that connects the Forms Java Client with the Forms Listener Servlet and the runtime process.
Level: 1

Type: ERROR

Impact: Network

FRM-91230: fatal error in runtime process: timeout on connection to Java client

Cause: The runtime process was waiting for a message from the Java client, but none appeared within the timeout interval. (This interval defaults to 15 minutes, but can be overridden by the FORMS_TIMEOUT environment variable.)

Action: Check for problems on the network that connects the Forms Java Client with the Forms Listener Servlet and the runtime process. Also check to see if the Forms applet on the Java client experienced a fatal error.
Level: 1

Type: ERROR

Impact: Network

FRM-91260: internal error in runtime process: unable to initialize the Winsock DLL

Cause: An unexpected error occurred while the runtime process was attempting to initialize the Winsock DLL.

Action: If the problem persists, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

FRM-91270: runtime process unable to allocate socket for protocol {0}: {1}

Cause: The runtime process was unable to allocate a socket for the indicated protocol (IPv4 or IPv6). The error message from the operating system is displayed. NOTE: If this error was detected for an IPv4 socket, the runtime process continued execution (and subsequently attempted to configure an IPv6 socket). If this error was detected for an IPv6 socket and an IPv4 socket was not successfully configured, then the runtime process was terminated.

Action: If the error message from the operating system indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

FRM-91272: runtime process unable to set close-on-exec on socket for protocol {0}: {1}

Cause: The runtime process was unable to configure the socket that it allocated for the indicated protocol (IPv4 or IPv6), to set close-on-exec. The error message from the operating system is displayed. The runtime process attempted to continue execution.

Action: If the error message from the operating system indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Process

FRM-91273: runtime process unable to enable local address reuse on socket for protocol {0}: {1}

Cause: The runtime process was unable to configure the socket that it allocated for the indicated protocol (IPv4 or IPv6), to enable local address reuse. The error message from the operating system is displayed. NOTE: If this error was detected for an IPv4 socket, the runtime process continued execution (and subsequently attempted to configure an IPv6 socket). If this error was detected for an IPv6 socket and an IPv4 socket was not successfully configured, then the runtime process was terminated.

Action: If the error message from the operating system indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

FRM-91274: runtime process unable to translate hostname ({0}) to an address for protocol {1}: {2}

Cause: The runtime process was unable to configure the socket that it allocated for the indicated protocol (IPv4 or IPv6) correctly, because the hostname could not be translated to an address. The error message from the operating system is displayed. NOTE: If this error was detected for an IPv4 socket, the runtime process continued execution (and subsequently attempted to configure an IPv6 socket). If this error was detected for an IPv6 socket and an IPv4 socket was not successfully configured, then the runtime process was terminated.

Action: If the error message from the operating system indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

FRM-91275: runtime process unable to bind socket address for port {0} to socket for protocol {1}: {2}

Cause: The runtime process was unable to configure the socket that it allocated for the indicated protocol (IPv4 or IPv6), to bind the socket address for the indicated port to it. The error message from the operating system is displayed. NOTE: If this error was detected for an IPv4 socket, the runtime process continued execution (and subsequently attempted to configure an IPv6 socket). If this error was detected for an IPv6 socket and an IPv4 socket was not successfully configured, then the runtime process was terminated.

Action: If the error message from the operating system indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

FRM-91276: runtime process unable to obtain port number of socket for protocol {0}: {1}

Cause: The runtime process was unable to obtain the port number of the socket that it allocated for the indicated protocol (IPv4 or IPv6). The error message from the operating system is displayed. This error should never occur at a customer site.

Action: If the problem persists, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

FRM-91277: internal error in runtime process: unable to write port and process ID information to stderr

Cause: An unexpected error occurred while the runtime process was attempting to write port and process ID information to standard error. This error should never occur at a customer site.

Action: If the problem persists, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

FRM-91278: runtime process unable to listen for connections on socket for protocol {0}: {1}

Cause: The runtime process was unable to configure the socket that it allocated for the indicated protocol (IPv4 or IPv6), to listen for connections. The error message from the operating system is displayed. NOTE: If this error was detected for an IPv4 socket, the runtime process continued execution (and subsequently attempted to configure an IPv6 socket). If this error was detected for an IPv6 socket and an IPv4 socket was not successfully configured, then the runtime process was terminated.

Action: If the error message from the operating system indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

FRM-91280: runtime process unable to set non-blocking I/O on socket for protocol {0}: {1}

Cause: The runtime process was unable to set non-blocking I/O on the socket that it allocated for the indicated protocol (IPv4 or IPv6). The error message from the operating system is displayed. The runtime process attempted to continue execution.

Action: If the error message from the operating system indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Process

FRM-91292: internal error in runtime process: invalid initial message from Java client

Cause: The initial message from the Java client to the runtime process was not in the expected format.

Action: If the problem persists, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

FRM-91293: internal error in runtime process: invalid initial message from servlet

Cause: The initial message from the servlet to the runtime process was not in the expected format.

Action: If the problem persists, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

FRM-91299: fatal error in runtime process: unable to create a connection to the Java client

Cause: An unexpected error occurred while the runtime process was attempting to create a connection to the Java client. Usually, a previous message provides more detail.

Action: If a previous error message indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

FRM-93100: Initializing the Forms Servlet. Initialization parameters are:{0}

Cause: The Forms Servlet was being initialized.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

FRM-93110: No Forms Servlet configuration file is specified.

Cause: The configFileName initialization parameter was not specified.

Action: Specify the full name in the servlet parameter configFileName, the system property oracle.forms.configFileName, or the servlet context parameter configFileName.
Level: 1

Type: ERROR

Impact: Configuration

FRM-93111: Cannot find Forms Servlet configuration file {0}.

Cause: The Forms Servlet configuration file (specified by the configFileName initialization parameter) was not found.

Action: Verify that the configFileName initialization parameter specifies the correct value. (The value is taken from the servlet parameter configFileName, the system property oracle.forms.configFileName, or the servlet context parameter configFileName.) Create the file if necessary.
Level: 1

Type: ERROR

Impact: Configuration

FRM-93112: error reading Forms Servlet configuration file {0}

Cause: An I/O error occurred while reading the specified file.

Action: If the error persists, determine if the file has been damaged. Re-create the file if necessary.
Level: 1

Type: ERROR

Impact: Files

FRM-93113: syntax error at line {0} in configuration file {1}: invalid section name "{2}"

Cause: The specified configuration file contained an invalid section name.

Action: Provide a valid section name.
Level: 1

Type: ERROR

Impact: Configuration

FRM-93114: Forms Servlet configuration file {0} contains invalid data.

Cause: A syntax error was detected while parsing the specified file.

Action: A preceding FRM-93113 or FRM-93142 error message will provide more information. Take the action indicated for the FRM-93113 or FRM-93142 message.
Level: 1

Type: ERROR

Impact: Configuration

FRM-93115: error reading configuration file FormsOIDConfig.xml via Forms Servlet.

Cause: An I/O error occurred while reading configuration file FormsOIDConfig.xml.

Action: Check if file exists in configuration directory.
Level: 1

Type: ERROR

Impact: Files

FRM-93121: Cannot find environment variable configuration file {0}.

Cause: One of the following occurred. (The first is by far the most likely.) Note that an envFile parameter may specify a relative path; if it was not found in the current directory, Forms will search for it in the directory that contains the Forms Servlet configuration file. 1. The envFile configuration parameter for this application specified a nonexistent file. A preceding FRM-93141 error message provides details. 2. The envFile configuration parameter for this application specified a file that existed when the Forms Servlet extracted the parameter, but the file subsequently disappeared. 3. No envFile configuration parameter that would apply to this application was specified, and the envFile servlet parameter specified a nonexistent file.

Action: Take action depending on the cause. 1. Take action indicated for the preceding FRM-93141 error message. 2. Re-create the file, or correct the envFile configuration parameter. 3. Verify that the envFile servlet parameter specifies the correct value. Create the file if necessary.
Level: 1

Type: ERROR

Impact: Configuration

FRM-93122: error reading environment variable configuration file {0}

Cause: An I/O error occurred while reading the specified file.

Action: If the error persists, determine if the file has been damaged. Re-create the file if necessary.
Level: 1

Type: ERROR

Impact: Files

FRM-93124: Environment variable configuration file {0} contains invalid data.

Cause: The specified configuration file contained an invalid section name.

Action: Provide a valid section name.
Level: 1

Type: ERROR

Impact: Configuration

FRM-93130: No base HTML file is specified.

Cause: The basehtml configuration parameter was not specified, nor was the basehtmljpi configuration parameter, where relevant. (See Oracle Fusion Middleware Forms Services Deployment Guide for details about which configuration parameter is appropriate.) The FRM-93140 error message provides details about which configuration sections were searched. (Note that the error message will always refer to the basehtml configuration parameter, not the basehtmljpi configuration parameter.)

Action: Specify the appropriate configuration parameter.
Level: 1

Type: ERROR

Impact: Configuration

FRM-93131: Cannot find base HTML file {0}.

Cause: The specified file was not found. This file is typically specified by the basehtml configuration parameter, but in certain cases may be specified by the basehtmljpi configuration parameter. The FRM-93141 error message provides details. Note that the parameter may specify a relative path; if the file is not found in the current directory, Forms will search for the file in the directory that contains the Forms Servlet configuration file.

Action: Verify that the parameter specifies the correct file. Create the file if necessary.
Level: 1

Type: ERROR

Impact: Configuration

FRM-93132: error reading base HTML file {0}

Cause: An I/O error occurred while reading the specified file.

Action: If the error persists, determine if the file has been damaged. Re-create the file if necessary.
Level: 1

Type: ERROR

Impact: Files

FRM-93140: Section [{0}] of Forms Servlet configuration file {1} does not specify (or inherit) a value for the required parameter {2}.

Cause: A required configuration parameter was not specified in the indicated configuration section or in a parent section.

Action: Specify the parameter value in the indicated section, or in a parent section. (See Oracle Fusion Middleware Forms Services Deployment Guide for details about what values are expected.)
Level: 1

Type: ERROR

Impact: Configuration

FRM-93141: Section [{0}] of Forms Servlet configuration file {1} specifies the nonexistent file {2} for parameter {3}.

Cause: A configuration parameter in the indicated configuration section specified the name of a nonexistent file.

Action: Verify that the parameter specifies the correct file. Create the file if necessary.
Level: 1

Type: ERROR

Impact: Configuration

FRM-93142: Section [{0}] of Forms Servlet configuration file {1} specifies the invalid value "{2}" for parameter {3}.

Cause: An invalid configuration parameter value was specified in the indicated configuration section. Note that invalid values for certain crucial parameters (such as HTMLdelimiter) will cause a subsequent error, FRM-93114.

Action: Correct the parameter value. (See Oracle Fusion Middleware Forms Services Deployment Guide for details about what values are expected.)
Level: 1

Type: ERROR

Impact: Configuration

FRM-93153: New connections to this Forms Servlet are not being allowed. Attempting to redirect connection attempt to {0}.

Cause: The allowNewConnections configuration parameter was false, and a value was specified for the connectionDisallowedURL configuration parameter. Redirection will be attempted to that URL.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

FRM-93154: The Forms Servlet is not allowing new connections.

Cause: The allowNewConnections configuration parameter was false, and either no value was specified for the connectionDisallowedURL configuration parameter, or else redirection to the specified URL failed.

Action: If a value is specified for the connectionDisallowedURL configuration parameter (as indicated in error message FRM-93153), check to see if the specified URL is malformed; if so, correct the URL. Otherwise, no action is required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

FRM-93156: The Forms Servlet is unable to contact the Forms Load Balancing Server at {0}:{1}.

Cause: The Forms Servlet was unable to contact the indicated Forms Load Balancing Server, and the MetricsServerErrorURL configuration parameter was not specified.

Action: Do one or both of the following. 1. Determine why the server is unavailable, and correct the condition. 2. Specify a value for the MetricsServerErrorURL parameter in the Forms Servlet configuration file.
Level: 1

Type: ERROR

Impact: Configuration

FRM-93160: unexpected error while obtaining the JVM pid

Cause: An Exception was encountered while obtaining the JVM process ID.

Action: Examine the stack trace that accompanies this message. If the stack trace indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

FRM-93176: Command "{0}" is using default ORACLE_HOME setting: {1}.

Cause: A test command has retrieved the specified value for the ORACLE_HOME environment variable, from the environment variable configuration file specified by the envFile parameter in the default section of the Forms Servlet configuration file.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

FRM-93180: Initializing ListenerServlet. Initialization parameters are: {0}

Cause: The Forms Listener Servlet was being initialized.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

FRM-93196: Process list file {0} does not exist or is not writable; process list disabled.

Cause: When a runtime process was started or stopped, an attempt was made to write an updated list of runtime processes to the specified file, but it did not exist or was not writable. Note that the name of the process list file is obtained from the em_process_file parameter in the URL, the Forms Servlet configuration file, or the environment variable configuration file.

Action: Verify that the em_process_file parameter specifies the correct file. If necessary, create the file or make it writable, or both.
Level: 1

Type: WARNING

Impact: Configuration

FRM-93197: unexpected error while obtaining the application name from JRF

Cause: An Exception was encountered while obtaining the application name from JRF.

Action: Examine the stack trace that accompanies this message. If the stack trace indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

FRM-93211: error decoding query string using {0} encoding. Spaces generated from "+" in the value of otherparams may be converted to "%20".

Cause: There was a mismatch between the way that the browser encoded multibyte characters and the way that the Forms Servlet decoded them. This could indicate an invalid value for the defaultcharset parameter in the configuration file, or possibly a problem in either the browser or Oracle software.

Action: If the site uses the otherparams parameter in any URLs, verify that the defaultcharset parameter in the configuration file is correct; if the defaultcharset parameter is correct, contact Oracle Support Services. Otherwise, no action is required.
Level: 1

Type: WARNING

Impact: Configuration

FRM-93214: internal buffer ({0} bytes) not big enough to read request content ({1} bytes)

Cause: An internal buffer was not big enough to read the content of a request from the Java client. The FRM-93214 error message provides supplemental detail for the FRM-93218 error message.

Action: If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Requests/Responses

FRM-93217: unable to read whole request from client: expected {0}, got {1}

Cause: A fatal error occurred while reading the content of a request from the Java client. The FRM-93217 error message provides supplemental detail for the FRM-93218 error message.

Action: Check for problems on the network that connects the Forms Java Client with the Forms Listener Servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

FRM-93218: fatal error reading client request content

Cause: A fatal error occurred while attempting to read the content of a request from the Java client. A preceding FRM-93214 or FRM-93217 error message might provide more detail.

Action: Check for problems on the network that connects the Forms Java Client with the Forms Listener Servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

FRM-93228: fatal error writing response to client

Cause: A fatal error occurred while writing a response to the Forms Java client.

Action: Check for problems on the network that connects the Forms Java Client with the Forms Listener Servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

FRM-93230: fatal error creating the HTTP session

Cause: An unexpected Exception was encountered while attempting to create and initialize the HTTP session for the Forms application. Typically, a session initialization error would cause a more specific message.

Action: Examine the stack trace that accompanies this message. If the stack trace indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Session

FRM-93240: Multiple Forms applications cannot share an HTTP session.

Cause: A Forms application was launched in such a way that it attempted to share an HTTP session with an already running Forms application. This might result from one of the following:1. The user selected File, then New, then Browser Window (or Ctrl+N) in Internet Explorer while the servlet session was being tracked using cookies (that is, session cookies were enabled). In this case Forms does not support creating a new session for the second window.2. An application attempted to launch multiple Forms applications, and cookies were enabled in the Forms application.3. An application attempted to launch multiple Forms applications using POST, cookies were disabled in the Forms application, and the launching application specified the same cookie name as did the Forms application.

Action: Take action depending on the cause.1. No action is required.2. Disable cookies in the Forms application.3. Change the cookie name in the launching application or the Forms application. This can be accomplished via <cookie-name> under <session-descriptor> in the weblogic.xml deployment descriptor.
Level: 1

Type: NOTIFICATION

Impact: Session

FRM-93250: Forms session started.

Cause: This message was generated on the initial request from the browser to the Forms Servlet, before an HTTP session was created.

Action: No action is required.
Level: 16

Type: NOTIFICATION

Impact: Session

FRM-93251: Runtime session started for client {0} (IP address {1}).

Cause: This message was generated when the runtime process was created (typically just after the HTTP session was created). If performance monitoring was requested, it started at this point.

Action: No action is required.
Level: 16

Type: NOTIFICATION

Impact: Session

FRM-93252: Forms session ended.

Cause: This message was generated when the runtime process was terminated. If performance monitoring was requested, it stopped at this point.

Action: No action is required.
Level: 16

Type: NOTIFICATION

Impact: Session

FRM-93301: Fatal authentication error: Unable to connect to Oracle Internet Directory.

Cause: A NamingException occurred while attempting to connect to Oracle Internet Directory.

Action: Verify that the Oracle Internet Directory is up.
Level: 1

Type: ERROR

Impact: Security

FRM-93304: No resource information found for key {0}.

Cause: No resource information was found for the specified key in Oracle Internet Directory. This message might be followed by error message FRM-93330 or FRM-93318.

Action: If a subsequent error message appears, take the action indicated for that error. Otherwise, no action is required.
Level: 1

Type: WARNING

Impact: Security

FRM-93306: Encountered {0} while attempting to retrieve database credentials from Oracle Internet Directory.

Cause: A UtilException was encountered while attempting to retrieve database credentials from Oracle Internet Directory. This message might be followed by error message FRM-93330, FRM-93316, or FRM-93318.

Action: If a subsequent error message appears, take the action indicated for that error. Otherwise, no action is required.
Level: 1

Type: WARNING

Impact: Security

FRM-93310: Encountered {0} while attempting to decode headers from mod_osso.

Cause: An Exception was encountered while attempting to decode headers from mod_osso.

Action: If a subsequent error message appears, take the action indicated for that error. Otherwise, no action is required.
Level: 1

Type: WARNING

Impact: Security

FRM-93316: Encountered {0} while attempting to obtain user credentials. Redirecting to Delegated Administration Services.

Cause: A NoPermissionException occurred while attempting to obtain credentials. The user will be redirected to Delegated Administration Services.

Action: If a subsequent error message appears, take the action indicated for that error. Otherwise, no action is required.
Level: 1

Type: WARNING

Impact: Security

FRM-93318: Encountered {0} while attempting to obtain user credentials. Redirecting to Delegated Administration Services or to the SSO error URL.

Cause: A NamingException that is not a NoPermissionException occurred while attempting to obtain user credentials.

Action: If a subsequent error message appears, take the action indicated for that error. Otherwise, no action is required.
Level: 1

Type: WARNING

Impact: Security

FRM-93320: unable to obtain application entity credential from CSF

Cause: The Forms servlet could not retrieve application credential from CSF to connect to OID. One of the following was true: 1. The Forms application did not have privileges to connect to CSF. 2. CSF alias and key values were invalid.

Action: Check whether credentials exist and are valid.
Level: 1

Type: ERROR

Impact: Security

FRM-93322: unable to obtain user credentials; redirecting to Delegated Administration Services

Cause: User credentials were not obtained, and either the symptom was a NoPermissionException, or the ssoDynamicResourceCreate configuration parameter was true.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

FRM-93324: Encountered {0} while attempting to obtain the Delegated Administration Services URL.

Cause: A UtilException was encountered while attempting to obtain the Delegated Administration Services URL.

Action: Verify that Delegated Administration Services is up.
Level: 1

Type: ERROR

Impact: Security

FRM-93326: Delegated Administration Services URL generated: {0}

Cause: The Forms application was running in SSO mode, the user did not have proper credentials configured in Oracle Internet Directory, and redirection to Delegated Administration Services was requested. This message provides the URL for Delegated Administration Services.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

FRM-93328: User credentials not obtained; redirecting to the SSO error URL.

Cause: User credentials were not obtained. The error was not due to a NoPermissionException. The ssoDynamicResourceCreate configuration parameter was not true. If the ssoErrorURL configuration parameter was not defined, this message will be followed by error message FRM-93140, which will provide details.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

FRM-93330: Fatal authentication error: User does not have proper credentials configured in Oracle Internet Directory.

Cause: The user did not have proper credentials configured in Oracle Internet Directory, and one of the following was true: 1. The ssoDynamicResourceCreate configuration parameter was true, or the user did not have the necessary permissions to access Oracle Internet Directory. The Delegated Administration Services URL could not be generated. The preceding FRM-93324 error message provides more detail. 2. The ssoDynamicResourceCreate configuration parameter was not true, and the user had the necessary permissions to access Oracle Internet Directory. The ssoErrorURL configuration parameter was not defined. The preceding FRM-93140 error message provides more detail.

Action: Add the user credentials to Oracle Internet Directory, if appropriate. Alternatively, define the ssoErrorURL configuration parameter. Alternatively, ensure that the Delegated Administration Services URL can be generated.
Level: 1

Type: ERROR

Impact: Security

FRM-93340: Session requires SSO user authentication.

Cause: The session was not SSO-authenticated or had expired.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

FRM-93350: failure in SSO user validation

Cause: The Listener Servlet decoded a request's SSO headers, but the values did not match the values from the Forms Servlet. The user was prompted to log in again.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

FRM-93360: This session is in SSO mode.

Cause: The ssoMode parameter was specified as true in the base configuration file, and the servlet supported authentication.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

FRM-93362: unable to update password in Oracle Internet Directory

Cause: The user did not have proper credentials configured in Oracle Internet Directory to update entries.

Action: Check with the Oracle Internet Directory administrator to see if the user has permissions to update entries in Oracle Internet Directory.
Level: 1

Type: ERROR

Impact: Security

FRM-93364: Cannot dynamically create resource in Oracle Internet Directory: URL specifies invalid value "{0}" for the config parameter.

Cause: The Forms application was running in SSO mode, the user did not have proper credentials configured in Oracle Internet Directory, and SSO dynamic resource creation was enabled. However, dynamic resource creation requires a valid configuration section in the base configuration file, but the user specified a nonexistent configuration section.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

FRM-93365: error running Forms in SSO mode

Cause: Forms is not configured to run in SSO mode.

Action: Configure Forms to run in SSO mode.
Level: 1

Type: ERROR

Impact: Files

FRM-93410: unexpected error while prestarting runtime processes

Cause: An unchecked Exception or Error was encountered while prestarting runtime processes. The prestarting of runtime processes might not have occurred at all, or it might have been partially completed.

Action: Examine the stack trace that accompanies this message. If the stack trace indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

FRM-93412: There are {0} prestarted runtime processes in the runtime process pool for configuration section [{1}].

Cause: During runtime process pool initialization, the indicated number of runtime processes were prestarted for the indicated configuration section, because the configuration section specified a value of true for the prestartRuntimes parameter. (The number of runtime processes is derived from the prestartInit parameter.)

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Process

FRM-93421: starting the timer for the runtime process pool for configuration section [{0}]

Cause: During runtime process pool initialization, a timer task was started for the indicated configuration section, because the configuration section specified a positive value for the prestartTimeOut parameter.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Process

FRM-93423: adding {0} runtime processes to the runtime process pool for configuration section [{1}] because the pool has gone below the minimum

Cause: A prestarted runtime process was removed from the runtime process pool for the indicated configuration section, in order to start a new Forms application. This caused the number of prestarted runtime processes to fall below the value specified by the prestartMin parameter. As a result, the indicated number of prestarted runtime processes (derived from the prestartIncrement parameter) were added to the pool.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Process

FRM-93424: removing the prestarted runtime processes for configuration section [{0}]

Cause: The servlet was being shut down, or the prestarting of runtime processes timed out (as indicated by message FRM-93425). As a result, prestarted processes were removed from the pool.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Process

FRM-93425: The prestarting of runtime processes for configuration section [{0}] has timed out.

Cause: The thread that was filling the runtime process pool for the indicated configuration section timed out, after running for the number of minutes specified by the prestartTimeOut parameter for the indicated configuration section. Any prestarted processes in the pool were subsequently removed.

Action: Determine why prestarting was taking an unexpectedly long time, or increase the value of the prestartTimeOut parameter.
Level: 1

Type: NOTIFICATION

Impact: Process

FRM-93426: The prestarting of runtime processes for configuration section [{0}] is terminated.

Cause: A concurrent process removed the indicated configuration section's entry in the PoolManager while its runtime process pool was being filled. Any prestarted processes in the pool were subsequently removed.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Process

FRM-93500: unexpected error while attempting to create the runtime process

Cause: An unchecked Exception or Error was encountered while attempting to create the runtime process. Typically, a runtime process creation error would cause a more specific message.

Action: Examine the stack trace that accompanies this message. If the stack trace indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

FRM-93520: Runtime process not created: Maximum permissible number of runtime processes is exceeded.

Cause: The maxRuntimeProcesses configuration parameter specified a positive decimal number, and there appeared to be that many runtime processes already executing.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

FRM-93530: unable to switch to working directory {0}

Cause: The specified file did not exist or was not a directory. Note that the name of the working directory is obtained from one of the following: 1. The workingDirectory parameter in the Forms Servlet configuration file. 2. The workingDirectory servlet parameter. 3. <oracle_home>/forms, where <oracle_home> is derived from the ORACLE_HOME parameter in the environment variable configuration file. 4. <oracle_home>/forms, where <oracle_home> is derived from the ORACLE_HOME environment variable.

Action: For cases 1 and 2, verify that the workingDirectory parameter specifies the correct directory. For cases 3 and 4, verify that the ORACLE_HOME parameter or environment variable specifies the correct directory. If necessary, create the directory.
Level: 1

Type: ERROR

Impact: Configuration

FRM-93531: cannot create runtime process: unable to switch to working directory

Cause: Refer to error message FRM-93530 (which always precedes this message). The FRM-93530 message provides the name of the directory.

Action: Refer to error message FRM-93530.
Level: 1

Type: ERROR

Impact: Configuration

FRM-93534: unable to execute startup command {0}

Cause: The specified command (which was intended to start the runtime process) threw an Exception. The command was retried with <oracle_home>/bin prefixed, but that too threw an Exception. A stack trace accompanies the following FRM-93535 error message. This error should never occur at a customer site. Note that <oracle_home> is derived from one of the following:1. The ORACLE_HOME parameter in the environment variable configuration file.2. The ORACLE_HOME environment variable.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

FRM-93535: cannot create runtime process: unable to execute startup command

Cause: Refer to error message FRM-93534 (which always precedes this message). The FRM-93534 error message specifies the command. This error should never occur at a customer site.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

FRM-93536: cannot create runtime process: unable to create temporary logging file

Cause: An IOException occurred while trying to create a temporary logging file to capture the standard output and standard error streams of the newly created runtime process.

Action: Verify that the Forms Listener Servlet has the necessary permissions and disk space to create a temporary file.
Level: 1

Type: ERROR

Impact: Files

FRM-93543: cannot connect to runtime process: unable to get I/O streams from newly created runtime process

Cause: The Forms Listener Servlet encountered an Exception when attempting to obtain a BufferedInputStream for the standard output or standard error streams produced by the newly created runtime process. This error should never occur at a customer site.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

FRM-93546: external message from runtime process: {0}

Cause: The runtime process wrote the specified message to stderr or stdout, but the message does not appear to have been written by the frmweb exeutable. It typically will be an O/S message identifying an error that occurred while attempting to load the executable. In such a case, this message will be followed immediately by FRM-93552.

Action: Examine the external message. If it identifies a fatal error, correct it, if possible. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

FRM-93548: Runtime process ID is {0}.

Cause: The newly created runtime process sent its process ID back to the Forms Listener Servlet.

Action: No action is required.
Level: 16

Type: NOTIFICATION

Impact: Process

FRM-93550: cannot connect to runtime process: no response from newly created runtime process

Cause: The Forms Listener Servlet waited several times (for a total of roughly 4 minutes) for the initial response from the newly created runtime process, but no response arrived.

Action: If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

FRM-93552: cannot connect to runtime process: Newly created runtime process has terminated abnormally.

Cause: The Forms Listener Servlet created the runtime process, but the process terminated abnormally. The preceding error message provides more detail.

Action: Take the action indicated for the preceding error message.
Level: 1

Type: ERROR

Impact: Process

FRM-93553: cannot connect to runtime process: unable to establish a socket connection to newly created runtime process

Cause: The Forms Listener Servlet created the runtime process, but was unable to establish a socket connection to the process.

Action: If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

FRM-93558: cannot connect to runtime process: error reading data from newly created runtime process

Cause: The Forms Listener Servlet encountered an IOException while attempting to receive data from the newly created runtime process.

Action: Examine the stack trace that accompanies this message. If the stack trace indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

FRM-93566: unexpected error while attempting to stop runtime process

Cause: An unchecked Exception or Error was encountered while attempting to stop the runtime process. Processing continued. However, the runtime process might have been left in existence (thereby consuming resources), and messages from the runtime process might not have been written to the Oracle Diagnostic Log.

Action: Examine the stack trace that accompanies this message. If the stack trace indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Process

FRM-93572: error reading messages from runtime process

Cause: An I/O error occurred while reading the temporary file to which messages from the runtime process were written. Processing continued. However, messages from the runtime process were not written to the Oracle Diagnostic Log.

Action: Examine the stack trace that accompanies this message. If the stack trace indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Files

FRM-93574: Application server does not support Oracle character set {0}.

Cause: The runtime process used the specified Oracle character set when it wrote messages for the Oracle Diagnostic Log, but the application server did not support that character set. Processing continued, using the ISO-8859-1 Java character set. However, some multibyte characters (those in variable arguments) in messages from the runtime process might have been displayed incorrectly in the Oracle Diagnostic Log.

Action: Verify that the environment variable configuration file specifies the correct value for NLS_LANG (specifically, the correct character set). If the problem persists, contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Configuration

FRM-93600: unexpected error while attempting to communicate with the client or the runtime process

Cause: An unchecked Exception or Error was encountered while attempting to communicate with the client or the runtime process. Typically, a communication error would cause a more specific message.

Action: Examine the stack trace that accompanies this message. If the stack trace indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

FRM-93614: invalid or absent Content-Length from runtime process

Cause: This message provides more detail for the following FRM-93618 error message.

Action: Refer to error message FRM-93618.
Level: 1

Type: ERROR

Impact: Process

FRM-93618: fatal error reading data from runtime process

Cause: The runtime process was still running, but the Forms Listener Servlet encountered an IOException while attempting to receive data from the process. A preceding message might provide more detail. The accompanying stack trace represents the state of the process when the previous detail message was logged.

Action: Examine the stack trace that accompanies this message. If the stack trace indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

FRM-93624: internal buffer ({0} bytes) not big enough to hold header ({1} bytes) for message from servlet to runtime process

Cause: An internal buffer was not big enough to hold the header for a message from the servlet to the runtime process. The FRM-93624 error message provides supplemental detail for the FRM-93628 error message.

Action: If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Requests/Responses

FRM-93625: internal buffer ({0} bytes) not big enough to generate initial message from servlet to runtime process

Cause: An internal buffer was not big enough to generate the initial message from the servlet to the runtime process. The FRM-93625 error message provides supplemental detail for the FRM-93628 error message.

Action: If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Requests/Responses

FRM-93628: fatal error writing data to runtime process

Cause: The runtime process was still running, but the Forms Listener Servlet encountered a fatal error while attempting to write data to the process. A preceding FRM-93624 or FRM-93625 error message might provide more detail.

Action: Examine the stack trace that accompanies this message. If the stack trace indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

FRM-93652: The runtime process has terminated abnormally.

Cause: The Forms Listener Servlet attempted to communicate with the runtime process, but the process had terminated prematurely. The preceding error message provides more detail.

Action: Take the action indicated for the preceding error message.
Level: 1

Type: ERROR

Impact: Process

FRM-93654: Runtime process {0} is terminating due to external action.

Cause: The runtime process was running on a UNIX platform, and received a signal 9 (SIGKILL) or 15 (SIGTERM), or the runtime process was running on a Windows platform, and exited with exit code 1. Presumably the runtime process was terminated explicitly, either via the Enterprise Manager, or via a 'kill' command (UNIX) or the task manager (Windows). As a result, the runtime process terminated abnormally. This message provides more detail for a following FRM-93552 or FRM-93652 error message.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Process

FRM-93656: Runtime process {0} is terminating due to signal {1}.

Cause: The runtime process was running on a UNIX platform, and received a signal other than 9 (SIGKILL) or 15 (SIGTERM). The signal caused the runtime process to terminate abnormally. This message provides more detail for a following FRM-93552 or FRM-93652 error message. If the FORMS_CATCHTERM environment variable was not set to a value that is equivalent to FALSE, there will typically be a stack trace. If the FORMS_C_STACK_TRACE_TO_FILE environment variable was set to a value that is equivalent to FALSE, the stack trace will accompany this message; otherwise, the stack trace will appear in a file named frmweb_dump_<pid> in the Forms trace directory, where <pid> is the process ID. If the FORMS_CATCHTERM environment variable was set to a value that is equivalent to FALSE, there may be a core file that contains a stack trace.

Action: Examine the stack trace for the runtime process. If the stack trace indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

FRM-93657: Runtime process {0} is terminating due to exception {1}.

Cause: The runtime process was running on a Windows platform, and encountered an exception (which is displayed as 8 hexadecimal digits in the error message, in some cases followed by a descriptive phrase). The exception caused the runtime process to terminate abnormally. This message provides more detail for a following FRM-93552 or FRM-93652 error message. If the FORMS_CATCHTERM environment variable was not set to a value that is equivalent to FALSE, there will typically be a stack trace. If the FORMS_C_STACK_TRACE_TO_FILE environment variable was set to a value that is equivalent to FALSE, the stack trace will accompany this message; otherwise, the stack trace will appear in a file named frmweb_dump_<pid> in the Forms trace directory, where <pid> is the process ID.

Action: Examine the stack trace for the runtime process. If the stack trace indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

FRM-93658: Stack trace for runtime process {0} is being written to file {1}.

Cause: The runtime process encountered a signal or an exception (identified by the preceding "FRM-93656" or "FRM-93657" message), and the FORMS_C_STACK_TRACE_TO_FILE environment variable was not set to a value that is equivalent to FALSE.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Process

FRM-93659: Stack trace for runtime process {0} cannot be written to file {1}.

Cause: The runtime process encountered a signal or an exception (identified by the preceding "FRM-93656" or "FRM-93657" message), and the FORMS_C_STACK_TRACE_TO_FILE environment variable was not set to a value that is equivalent to FALSE. However, the stack trace file could not be created.

Action: Ensure that the FORMS_TRACE_DIR environment variable (if set) and the ORACLE_INSTANCE environment variable each specify a valid directory with write permissions and adequate space.
Level: 1

Type: WARNING

Impact: Process

FRM-93700: Request duration is {0} seconds. Request size is {1} bytes; response size is {2} bytes.

Cause: Performance monitoring at the request level was requested.

Action: No action is required.
Level: 16

Type: TRACE

Impact: Performance

FRM-93710: Total duration of network exchanges is {0}. Total number of network exchanges is {1} ({2} long ones over {3} sec). Average time for one network exchange (excluding long ones) is {4}. Total number of bytes sent is {5}. Total number of bytes received is {6}.

Cause: Performance monitoring at the session level was requested.

Action: No action is required.
Level: 1

Type: TRACE

Impact: Performance

FRM-93840: Proctest: Warning: nProcs configuration parameter is nonnumeric - using 1.

Cause: A nonnumeric value was specifed for the nProcs parameter in the base configuration file. The value will default to 1.

Action: Correct the nProcs configuration parameter.
Level: 1

Type: WARNING

Impact: Configuration

FRM-93841: Proctest: Process test starting with {0} processes.

Cause: The Proctest command started.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Process

FRM-93842: Proctest: Creating process {0}.

Cause: The Proctest command started creating a runtime process.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Process

FRM-93843: Proctest: Failure to create process {0} - aborting test.

Cause: An Exception occurred while attempting to create a runtime process. The preceding error message identifies the problem, and includes a stack trace.

Action: Refer to the preceding error message.
Level: 1

Type: ERROR

Impact: Process

FRM-93844: Proctest: Connecting to process {0}.

Cause: The Proctest command started connecting to a newly created runtime process.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Process

FRM-93845: Proctest: Failure to connect to process {0} - aborting test.

Cause: An Exception occurred while attempting to connect to a newly created runtime process. The preceding error message identifies the problem, and includes a stack trace.

Action: Refer to the preceding error message.
Level: 1

Type: ERROR

Impact: Process

FRM-93846: Proctest: unexpected error in process test

Cause: This message precedes error message FRM-93843 or FRM-93845 if the problem was an Error or an unchecked Exception that was not caught by Forms code. A stack trace is included.

Action: Examine the stack trace that accompanies this message. If the stack trace indicates a possible cause, correct it. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

FRM-93847: Proctest: Number of processes started and connected to is {0}.

Cause: The Proctest command created the requested number of runtime processes, and successfully connected to them.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Process

FRM-93848: Proctest: Stopping the {0} runtime processes.

Cause: The Proctest command reached the point in its processing where it was about to stop the runtime processes that it had previously created.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Process

FRM-93849: Proctest: Process test complete.

Cause: The Proctest command completed.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Process

FRM-93880: Testsession: Successful creation of new servlet session.

Cause: The Testsession command successfully created a new servlet session.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Session

FRM-93881: Testsession: Attempting to establish session tracking using cookies. Sending redirect to {0}.

Cause: The Testsession command started to establish session tracking using cookies.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Session

FRM-93882: Testsession: Failure to establish session tracking using cookies; attempting URL rewriting. Sending redirect to {0}.

Cause: The Testsession command failed to establish session tracking using cookies.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Session

FRM-93884: error in Testsession command

Cause: An internal error occurred. Probable cause: an attempt to invoke the HttpServletRequest.isRequestedSessionIdFromUrl method caused a NoSuchMethodError. This probably indicates that the JDK does not support the deprecated spelling. (The supported spelling is "isRequestedSessionIdFromURL", but JServ / Servlet API 2.0 supports only the deprecated spelling.)

Action: If the problem persists, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Session

FRM-94170: File {0} is missing from the current directory, looking in {1}.

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.
Level: 32

Type: TRACE

Impact: Other

FRM-94171: File is missing from {0}.

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.
Level: 32

Type: TRACE

Impact: Other

FRM-94172: Environment variable configuration file is {0}.

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.
Level: 32

Type: TRACE

Impact: Other

FRM-94178: Enterprise Manager configuration details: {0}

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.
Level: 32

Type: TRACE

Impact: Other

FRM-94200: FormsServlet receiving {0} request. Details: {1}

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.
Level: 32

Type: TRACE

Impact: Other

FRM-94201: ListenerServlet receiving {0} request. Details: {1}

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.
Level: 32

Type: TRACE

Impact: Other

FRM-94202: HTTP request headers: {0}

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.
Level: 32

Type: TRACE

Impact: Other

FRM-94212: Unable to get the Sequence Number from Pragma Header (Mac Client). Obtaining the seqNumber from the Accept header instead.

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.
Level: 32

Type: TRACE

Impact: Other

FRM-94213: forwarding 0 length request to runtime in response to request to close Forms session

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.
Level: 32

Type: TRACE

Impact: Other

FRM-94231: starting new servlet session

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.
Level: 32

Type: TRACE

Impact: Other

FRM-94232: FormsServlet: encodeUrl() has no effect.

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.
Level: 32

Type: TRACE

Impact: Other

FRM-94233: Server URL is rewritten. Details:{0}

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.
Level: 32

Type: TRACE

Impact: Other

FRM-94241: ListenerServlet: encodeUrl() has no effect.

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.
Level: 32

Type: TRACE

Impact: Other

FRM-94252: Servlet session is invalidated.

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.
Level: 32

Type: TRACE

Impact: Other

FRM-94281: No current servlet session ID.

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.
Level: 32

Type: TRACE

Impact: Other

FRM-94282: Existing servlet session, ID = {0}

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.
Level: 32

Type: TRACE

Impact: Other

FRM-94283: No current servlet session.

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.
Level: 32

Type: TRACE

Impact: Other

FRM-94284: requesting a servlet session with invalid session ID = {0}

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.
Level: 32

Type: TRACE

Impact: Other

FRM-94285: Session ID is from cookie.

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.
Level: 32

Type: TRACE

Impact: Other

FRM-94286: Session ID is not from cookie.

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.
Level: 32

Type: TRACE

Impact: Other

FRM-94302: Encountering {0} while attempting to proxy the Oracle Internet Directory connection to the SSO user.

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.
Level: 32

Type: TRACE

Impact: Other

FRM-94332: Starting session in SSO mode. Details: {0}

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.
Level: 32

Type: TRACE

Impact: Other

FRM-94334: User name from Oracle Internet Directory: {0}

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.
Level: 32

Type: TRACE

Impact: Other

FRM-94430: Trying to get a prestarted process.

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.
Level: 32

Type: TRACE

Impact: Other

FRM-94431: Prestarted process is available and selected.

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.
Level: 32

Type: TRACE

Impact: Other

FRM-94432: Prestarted process is not available.

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.
Level: 32

Type: TRACE

Impact: Other

FRM-94522: Creating new runtime process using default executable.

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.
Level: 32

Type: TRACE

Impact: Other

FRM-94523: Creating new runtime process using executable "{0}".

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.
Level: 32

Type: TRACE

Impact: Other

FRM-94532: RunformProcess.startProcess(): executing {0}

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.
Level: 32

Type: TRACE

Impact: Other

FRM-94533: RunformProcess.startProcess(): execution failure, trying again using {0}

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.
Level: 32

Type: TRACE

Impact: Other

FRM-94538: successful creation of new runtime process

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.
Level: 32

Type: TRACE

Impact: Other

FRM-94542: Getting stderr of child process.

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.
Level: 32

Type: TRACE

Impact: Other

FRM-94547: port number from message: {0}

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.
Level: 32

Type: TRACE

Impact: Other

FRM-94554: successful connection to runtime process after {0} attempts

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.
Level: 32

Type: TRACE

Impact: Other

FRM-94556: successful connection to runtime process at port {0}

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.
Level: 32

Type: TRACE

Impact: Other

FRM-94562: RunformSession.valueUnbound(): stopping runtime process.

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.
Level: 32

Type: TRACE

Impact: Other

FRM-94610: Read timeout. Sending Response Pending with retry time = {0}.

Cause: This message is intended primarily for Oracle Support Services.

Action: No action is required.
Level: 32

Type: TRACE

Impact: Other

FRM-99999: Error {0}: See the release notes file (relnotes) for information about this error.

Cause: See the release notes.

Action: Take action as documented in the release notes.
Level: 1

Type: ERROR

Impact: Configuration

43 FTS-40001 to FTS-40006

FTS-40001: Service Error {0} {1} {2}

Cause: Service failed to return a success response.

Action: See service error code.
Level: 1

Type: ERROR

Impact: Other

FTS-40002: Configuration for connector missing.

Cause: The connector configuration was not found.

Action: Add connector configuration.
Level: 1

Type: ERROR

Impact: Configuration

FTS-40003: Configuration parameter {0} missing.

Cause: Configuration parameter was not found.

Action: Add the parameter and its value indicated in the error message.
Level: 1

Type: ERROR

Impact: Configuration

FTS-40004: Invalid value {0} for configuration parameter {1}

Cause: The value specified for the configuration parameter is invalid.

Action: Specify a valid value for the configuration parameter.
Level: 1

Type: ERROR

Impact: Configuration

FTS-40005: Stale data presented for update.

Cause: The data presented for update is stale.

Action: Refresh the data to get the latest version.
Level: 1

Type: ERROR

Impact: Other

FTS-40006: Failed to transform PIM xml: {0}

Cause: The PIM xml retrieved could not be transformed to hub xml format.

Action: Correct the PIM data and retry the operation.
Level: 1

Type: ERROR

Impact: Other

44 HELP-00001 to HELP-40001

HELP-00001: Error when creating HelpXmlPullParser due to XmlPullParserException for location: {0}

Cause: An XmlPullParserException was thrown while running _processDocument in the HelpXmlPullParser contructor.

Action: Verify that the location of the JavaHelp-format file exists.
Level: 1

Type: WARNING

Impact: Logging

HELP-00002: Error when creating HelpXmlPullParser due to IOException for location: {0}

Cause: An IOException was thrown when running Process Document in the HelpXmlPullParser contructor.

Action: Verify that the location of the JavaHelp-format file exists
Level: 1

Type: WARNING

Impact: Logging

HELP-00003: Error when executing search in SearchModel.

Cause: SearchModel threw a SearchException when starting the search.

Action: Log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

HELP-00004: View passed to SearchModel does not contain data in QueryHandler format.

Cause: The view object passed to SearchModel did not contain data in the expected QueryHandler format.

Action: Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

HELP-00005: Unexpected exception occurring in Help Share.

Cause: An unexpected exception occurred in the code.

Action: Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

HELP-00006: Error when parsing document using XML parser

Cause: An XMLParseException was thrown when processing the XML document.

Action: Log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

HELP-10001: Unexpected exception occurring in OHW Share.

Cause: An unexpected exception occurred in the code.

Action: Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

HELP-10002: Adding book {0} to library fails because of LibraryException.

Cause: A LibraryException was thrown.

Action: Log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

HELP-10003: encountering severe exception when parsing locale from file

Cause: A ConfigParseException was thrown when creating PerLocaleInfo from file.

Action: Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

HELP-10004: class name attribute is required on [localeFromProvider]

Cause: The class attribute was missing for the localeFromProvider tag.

Action: Add the class name attribute.
Level: 1

Type: ERROR

Impact: Logging

HELP-10005: error in loading per locale provider {0}

Cause: An unexpected exception was caught when loading the per locale provider.

Action: Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

HELP-10006: unrecognized tag {0} in {1} section

Cause: There was an unrecognized tag in the configuration section.

Action: Check the configuration file for unrecognized tags in the configuration section.
Level: 1

Type: ERROR

Impact: Logging

HELP-10007: no [locale] section in [locales]

Cause: The required [locale] section was missing in [locales].

Action: Check the help configuration file to ensure that [locales] has at least one child [locale].
Level: 1

Type: ERROR

Impact: Logging

HELP-10008: error in loading custom protocol class: {0}

Cause: An unexpected exception was caught when loading the Custom Protocol class.

Action: Verify that the Custom Protocol class is valid.
Level: 1

Type: ERROR

Impact: Logging

HELP-10009: error in loading branding provider: {0}

Cause: An unexpected exception was caught when loading the Branding Provider class.

Action: Verify that the Branding Provider class is valid.
Level: 1

Type: ERROR

Impact: Logging

HELP-10010: configuration file is empty

Cause: The Help configuration file was empty.

Action: Verify that the Help configuration file exists and contains content.
Level: 1

Type: ERROR

Impact: Logging

HELP-10011: {0} attribute is required on [helpConfiguration]

Cause: The version attribute was not available on the [helpConfiguration] section.

Action: Add the version attribute to the [helpConfiguration] section of the Help configuration file.
Level: 1

Type: ERROR

Impact: Logging

HELP-10012: Version {0} is not a recognized version. Accepted versions are: {1}

Cause: The version provided was not recognized as an accepted version.

Action: Verify that an accepted version is used in the Help configuration file.
Level: 1

Type: ERROR

Impact: Logging

HELP-10013: duplicate {0} section in the Help configuration file

Cause: There was a duplicate section in the Help configuration file.

Action: Check the Help configuration file for duplicate sections and remove them.
Level: 1

Type: ERROR

Impact: Logging

HELP-10014: tag {0} is not recognized

Cause: Unrecognized tags were found in the Help configuration file.

Action: Remove all unrecognized tags from the Help configuration file.
Level: 1

Type: ERROR

Impact: Logging

HELP-10015: no {0} section found

Cause: A required section was not found in the Help configuration file.

Action: Add the required section to the Help configuration file.
Level: 1

Type: ERROR

Impact: Logging

HELP-10016: Expecting: {0}. Finding: {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Logging

HELP-10017: The {0} attribute is missing in [customProtocol].

Cause: The attribute was missing in the Custom Protocol definition.

Action: Add the required attribute to the Custom Protocol definition.
Level: 1

Type: ERROR

Impact: Logging

HELP-10018: The attribute {0} is missing in [alias].

Cause: The required attribute was missing from the navigator alias definition.

Action: Add the required attribute to the navigator alias definition.
Level: 1

Type: ERROR

Impact: Logging

HELP-10019: Text or image source attribute is required in [branding].

Cause: The text or image attribute was missing from the [branding] section of the Help configuration file.

Action: Ensure that the text or image attribute is non-empty and points to a valid location.
Level: 1

Type: ERROR

Impact: Logging

HELP-10020: The {0} attribute on the [branding] tag cannot be empty.

Cause: The required attribute was missing from the [branding] section.

Action: Add the required attribute to the [branding] section.
Level: 1

Type: ERROR

Impact: Logging

HELP-10021: Text key or image source key attribute is required in [brandingFromResource].

Cause: The text key or image source attribute was missing from [brandingFromResource].

Action: Ensure that the text or image attribute is non-empty and points to a valid location.
Level: 1

Type: ERROR

Impact: Logging

HELP-10022: The {0} attribute is required on [brandingFromResource].

Cause: The required attribute was missing from the [brandingFromResource] section.

Action: Add the required attribute to the [brandingFromResource] section.
Level: 1

Type: ERROR

Impact: Logging

HELP-10023: The {0} attribute is required on [brandingFromProvider]

Cause: The required attribute was missing from the [brandingFromProvider] section.

Action: Add the required attribute to the [brandingFromProvider] section.
Level: 1

Type: ERROR

Impact: Logging

HELP-10024: error finding configuration file at: {0}

Cause: The configuration file was not found at the specified location.

Action: Verify that the location of the configuration file is valid.
Level: 1

Type: ERROR

Impact: Logging

HELP-10025: The view {0} with base path {1} passed to the SearchDispatcher does not contain a valid QueryHandler.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Logging

HELP-10026: trying to access site with invalid path: {0}

Cause: There was an attempt to access a file through an invalid path.

Action: Verify that the file path is correct.
Level: 1

Type: ERROR

Impact: Logging

HELP-10027: missing or empty {0} attribute in [localeFromFile]

Cause: A required attribute was missing or empty in the [localeFromFile] section.

Action: Add the required attribute to the Help configuartion file.
Level: 1

Type: ERROR

Impact: Logging

HELP-10028: Location of locale file is not valid.

Cause: The location of the locale file was not valid.

Action: Supply a valid location for the locale file in the Help configuration file.
Level: 1

Type: ERROR

Impact: Logging

HELP-10029: Locale file is empty.

Cause: The locale file has no content.

Action: Supply a valid locale file.
Level: 1

Type: ERROR

Impact: Logging

HELP-10030: The locale file cannot be found.

Cause: The locale file was not available at the location specified in the Help configuration file.

Action: Verify that the locale file exists at the location specified in the Help configuration file.
Level: 1

Type: ERROR

Impact: Logging

HELP-10031: The {0} locale is not allowed without a corresponding country section.

Cause: The locale was used without an accompanying country section.

Action: Add a country section for this locale.
Level: 1

Type: ERROR

Impact: Logging

HELP-10032: unrecognized book: {0}

Cause: An unrecognized book tag was found in the Help configuration file.

Action: Check the Help configuartion file for helpSet or helpBook tags and remove or correct the unrecognized book tag.
Level: 1

Type: ERROR

Impact: Logging

HELP-10033: no books in [books] section

Cause: There was no book child in the books parent tag in the Help configuration file.

Action: Add a book child element to the books parent tag.
Level: 1

Type: ERROR

Impact: Logging

HELP-10034: Attribute {0} is missing in helpSet.

Cause: The required attribute was missing from the helpSet tag.

Action: Add the required attribute to the helpSet tag.
Level: 1

Type: ERROR

Impact: Logging

HELP-10035: duplicate helpSet or helpBook {0} : {1}

Cause: A duplicate helpSet or helpBook attribute was encountered.

Action: Remove the duplicate entry from the helpset configuartion file.
Level: 1

Type: ERROR

Impact: Logging

HELP-10036: Location of {0} is not valid.

Cause: The location of the file was not valid.

Action: Ensure that the location of the file is valid.
Level: 1

Type: ERROR

Impact: Logging

HELP-10037: Attribute {0} is missing in helpBook.

Cause: The required attribute was missing from the helpBook tag.

Action: Add the required attribute to the helpBook tag in the Help configuration file.
Level: 1

Type: ERROR

Impact: Logging

HELP-10038: Attribute {0} is missing in contentLocation tag.

Cause: The required attribute was missing from the contentLocation tag.

Action: Add the required attribute to the contentLocation tag in the Help configuration file.
Level: 1

Type: ERROR

Impact: Logging

HELP-10039: Content location is not valid.

Cause: The content location path was invalid.

Action: Ensure that the Help configuration file contains a valid content location base URI.
Level: 1

Type: ERROR

Impact: Logging

HELP-10040: duplicate {0} attribute {1} for content location

Cause: There was a duplicate attribute for the content location.

Action: Remove the duplicate entry from the Help configuration file.
Level: 1

Type: ERROR

Impact: Logging

HELP-10041: Content location is missing or malformed.

Cause: The content location was missing or malformed

Action: Verify that the content location path exists, and that it is a valid path.
Level: 1

Type: ERROR

Impact: Logging

HELP-10042: no known locales

Cause: There was no known locale information available.

Action: Verify that the Help configuration file contains a known locale.
Level: 1

Type: ERROR

Impact: Logging

HELP-10043: CustomProtocolName and converter must not be null.

Cause: The custom protocol name and the converter were not valid.

Action: Verify that the custom protocol name and the converter are not null in the Help configuration file.
Level: 1

Type: ERROR

Impact: Logging

HELP-10044: PerLocaleConfiguration cannot be used in unloaded state.

Cause: The PerLocaleConfiguration was not loaded into memory before an attempt was made to use it.

Action: Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

HELP-10045: error creating book information for id: {0}

Cause: There was an error while creating the book information.

Action: Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

HELP-10046: passed null per locale configuration

Cause: A null PerLocaleConfiguartion object was passed.

Action: Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

HELP-10047: calling init method for a second time in navigator manager

Cause: The init method was called a second time in AbstractNavigatorManager.

Action: Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

HELP-10048: FastMessageFormat supports only numeric arguments.

Cause: The FastMessageFormat method was passed non-numeric arguments.

Action: Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

HELP-10049: end of pattern symbol not found

Cause: The end of pattern symbol was not found.

Action: Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

HELP-10050: FastMessageFormat: empty argument - {}.

Cause: An empty argument was passed to FastMessageFormat.

Action: Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

HELP-10051: The operation {0} is not supported.

Cause: The execution of this method was not supported.

Action: Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

HELP-10052: Search for {0} yielding {1} number of results.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Logging

HELP-10053: Search for {0} yields no results.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Logging

HELP-10054: invalid topic id link: {0} reported from {1}

Cause: An invalid topic id was found.

Action: Review the help topic map file and the topic content file and correct the invalid topic id.
Level: 1

Type: WARNING

Impact: Logging

HELP-10055: trying to access invalid topic id {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Logging

HELP-10056: Topic {0} does not have a target that can be followed.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Logging

HELP-10057: discovery of a null topic in the Help files

Cause:

Action:
Level: 1

Type: WARNING

Impact: Logging

HELP-10058: (Debug Mode: {0} Missing Helpsets)

Cause:

Action:
Level: 1

Type: WARNING

Impact: Logging

HELP-20001: cannot find global configuration with URL: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Logging

HELP-20002: cannot find required servlet context parameter: {0}

Cause: The required servlet context parameter was not found.

Action: Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

HELP-20003: critical error in OHW configuration

Cause: There was a critical error in the Help configuration file.

Action: Verify the correctness of the Help configuration file.
Level: 1

Type: ERROR

Impact: Logging

HELP-20004: unrecognized view type {0} is ignored

Cause:

Action:
Level: 1

Type: WARNING

Impact: Logging

HELP-20005: cannot instantiate navigator of type: {0}

Cause: The navigator could not be instantiated.

Action: Verify the correctness of this navigator type in the Help configuration file.
Level: 1

Type: ERROR

Impact: Logging

HELP-20006: cannot update auto sync component

Cause: There was a failure when updating the auto sync UI component.

Action: Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

HELP-20007: no topic id or topic file for linkHelp=false

Cause:

Action:
Level: 1

Type: WARNING

Impact: Logging

HELP-20008: failure when creating tree model in Rich TOC Navigator

Cause:

Action:
Level: 1

Type: WARNING

Impact: Logging

HELP-20009: failure when trying to index tree model for TOC navigator

Cause:

Action:
Level: 1

Type: WARNING

Impact: Logging

HELP-20010: cannot find required ohwConfigFileURL

Cause: OHW Help Provider requires an OHW configuration file, but this file was not found.

Action: Ensure that the path points to a valid OHW configuration file.
Level: 1

Type: ERROR

Impact: Logging

HELP-20011: unable to create global configuration

Cause: The global configuration object could not be created.

Action: Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

HELP-20012: unexpected exception when trying to get embedded content for Rich Help Provider

Cause: An unexpected exception was caught when trying to get the embedded content for Rich Help Provider.

Action: Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

HELP-20013: The file protocol suggests that the OHW Config file is not located on local file system.

Cause: OHW Config file is not located on local file system.

Action: Please make sure that the OHW Config file is located on local file system.
Level: 1

Type: WARNING

Impact: Logging

HELP-30001: cannot find required servlet init parameter {0}

Cause: The required init parameter for the Help servlet was not found.

Action: Check the Help servlet definition in the web.xml file of the application.
Level: 1

Type: ERROR

Impact: Logging

HELP-30002: critical error in OHW configuration: {0}

Cause: There was a critical error in the OHW configuration file that caused a MalformedURLException.

Action: Correct the OHW configuration file.
Level: 1

Type: ERROR

Impact: Logging

HELP-30003: Critical error in OHW configuration. Config URL: {0}

Cause: There was a critical error in the OHW configuration file.

Action: Correct the OHW configuration file.
Level: 1

Type: ERROR

Impact: Logging

HELP-30004: failing to load UIX file

Cause: There was a failure when loading the UIX file.

Action: Ensure that the UIX file is valid.
Level: 1

Type: ERROR

Impact: Logging

HELP-30005: failure to parse {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Logging

HELP-30006: cannot find UIX path {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Logging

HELP-30007: OHW is encountering an unexpected error.

Cause: There was an unexpected error in OHW-UIX.

Action: Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

HELP-30008: cannot instantiate navigator of type {0}

Cause: The specified navigator could not be instantiated.

Action: Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

HELP-30009: cannot load class alias of type {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Logging

HELP-40001: error when loading icon: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Logging

45 IAU-01023 to IAU-62023

IAU-01023: Invalid filter preset. The Valid choices are {0}

Cause: The given audit level(filter preset) is invalid.

Action: Give a valid audit level(filter preset) like Low,Medium,None,Custom.
Level: 1

Type: ERROR

Impact: Other

IAU-01024: Max Dir Size should be atleast double that of min File Size and min File Size should be 4K

Cause: Error in setting the maximum directory size or file size for audit logs.

Action: Give a valid value for maximum directory and file size.
Level: 1

Type: ERROR

Impact: Other

IAU-01025: Unknown componentType {0} at character position:{1}

Cause: The component type given in custom event expression is invalid.

Action: Enter valid component type. listAuditEvents() command gives a list of component types.
Level: 1

Type: ERROR

Impact: Other

IAU-01026: Invalid Event Name: {0}

Cause: The event name in custom event expression is invalid.

Action: Enter valid event name. listAuditEvents() command gives a list of all the events for a given component.
Level: 1

Type: ERROR

Impact: Other

IAU-01027: Invalid component Type: {0}

Cause: The component type given in custom event expression is invalid.

Action: Give valid component type.listAuditEvents() command gives a list of component types.
Level: 1

Type: ERROR

Impact: Other

IAU-01028: Can't read components_dir {0}

Cause: Install is possibly corrupted.

Action: Check your install and contact Oracle Customer Support.
Level: 1

Type: ERROR

Impact: Other

IAU-01029: User {0} not found

Cause: The user to be removed is not in the list of special users(users to always audit).

Action: Check for the list of special users(users to always audit)already present using getAuditPolicy() command.
Level: 1

Type: ERROR

Impact: Other

IAU-01030: Unknown construct . expecting eventName at character position:{0}

Cause: Invalid syntax in custom event expression.

Action: Event name is expected at that position.
Level: 1

Type: ERROR

Impact: Other

IAU-01031: Unknown event {0} at character position:{1}

Cause: Invalid event in custom event expression.

Action: Enter a valid event name. listAuditEvents() command gives a list of all the events for a given component.
Level: 1

Type: ERROR

Impact: Other

IAU-01032: Expecting SUCCESSESONLY or FAILURESONLY after the dot at charcter position:{0}

Cause: Invalid syntax in custom event expression.

Action: The events name should be qualified with either SUCCESSONLY or FAILURESONLY after the dot.
Level: 1

Type: ERROR

Impact: Other

IAU-01033: Unknown construct . expecting componentType at character position {0}

Cause: componentType is expected at that position.

Action: Enter valid component type.listAuditEvents() command gives a list of component types.
Level: 1

Type: ERROR

Impact: Other

IAU-01034: Component type {0} is repeated at character position:{1}

Cause: Invalid syntax in custom event expression.

Action: Specify a component exactly once giving the list of all events to be added or removed.
Level: 1

Type: ERROR

Impact: Other

IAU-01035: Missing character after backslash at character position:{0}

Cause: The string at the specified position is invalid.

Action: Remove the trailing backslash.
Level: 1

Type: ERROR

Impact: Other

IAU-01036: Unterminated quoted string at character position:{0}

Cause: No matching end quote in the string.

Action: Check the specified string and add the matching end quote.
Level: 1

Type: ERROR

Impact: Other

IAU-01037: custom events can only be specified for custom filter preset

Cause: Custom events are added when the audit level(filter preset) is not Custom.

Action: Change the audit level(filter preset) to Custom.
Level: 1

Type: ERROR

Impact: Other

IAU-01038: Unexpected token {0} found at character position {1}

Cause: Invalid syntax in custom events expression.

Action: Check the custom events expression given.
Level: 1

Type: ERROR

Impact: Other

IAU-01039: Unfinished string that started at position {0}

Cause: Custom event expression string is not terminated.

Action: Check the string and terminate it.
Level: 1

Type: ERROR

Impact: Other

IAU-01040: Unrecognized token at position {0}

Cause: Invalid syntax in custom events expression.

Action: Check for the syntax of custom events expression.
Level: 1

Type: ERROR

Impact: Other

IAU-01041: Expecting RHS for the boolean operator {0} at position {1}

Cause: Invalid syntax in custom event expression.

Action: Give a RHS value for the boolean operator to evaluate.
Level: 1

Type: ERROR

Impact: Other

IAU-01042: Unexpected token {0} found. Expecting -and or -or or ')' at position {1}

Cause: Invalid syntax in custom events expression.

Action: Check for the syntax of custom events expression.
Level: 1

Type: ERROR

Impact: Other

IAU-01043: Expecting ')' corresponding to '(' at {0}

Cause: There is no matching end brace in custom events expression string.

Action: Check the expression and add a closing brace at the end to match with the beginning brace.
Level: 1

Type: ERROR

Impact: Other

IAU-01044: Expecting a relation expression at position {0}

Cause: Invalid syntax in custom events expression.

Action: Check for the syntax of custom events expression.
Level: 1

Type: ERROR

Impact: Other

IAU-01045: Operator {0} is not applicable for an attribute of type {1} at position {2}

Cause: Invalid operator given for an attribute in custom events expression.

Action: Use an operator that is allowed to be used with the attribute.
Level: 1

Type: ERROR

Impact: Other

IAU-01046: Invalid boolean operator {0}

Cause: Invalid syntax in custom events expression.

Action: Give a valid boolean operator.
Level: 1

Type: ERROR

Impact: Other

IAU-01047: Attribute {0} needs a string at position {1}

Cause: The value given for the attribute is not a string.

Action: Give a string value in double quotes.
Level: 1

Type: ERROR

Impact: Other

IAU-01048: Attribute {0} needs a boolean at position {1}

Cause: The value given for the attribute in custom events expression is of a different type.

Action: Give a boolean value(true or false) for this attribute.
Level: 1

Type: ERROR

Impact: Other

IAU-01049: Attribute {0} needs a number at position {1}

Cause: The value given for the attribute in custom events expression is of a different type.

Action: Give a number value for this attribute.
Level: 1

Type: ERROR

Impact: Other

IAU-01050: Attribute {0} needs a date at position {1}

Cause: The value given for the attribute in custom events expression is of a different type.

Action: Give a date value for this attribute.
Level: 1

Type: ERROR

Impact: Other

IAU-01051: Cannot parse {0} into a date. Error {1} at {2}

Cause: Date value entered is invalid.

Action: Give a valid date value.
Level: 1

Type: ERROR

Impact: Other

IAU-01052: Unparseable date {0} at position {1}

Cause: Date value entered is invalid.

Action: Give a valid date value.
Level: 1

Type: ERROR

Impact: Other

IAU-01053: Unparseable time {0} at position {1}

Cause: Invalid time given in the custom events expression.

Action: Enter valid time format.
Level: 1

Type: ERROR

Impact: Other

IAU-01054: Error in expression: unknown operator

Cause: Invalid operator given in a custom events expression.

Action: Give a valid operator.
Level: 1

Type: ERROR

Impact: Other

IAU-01055: Expecting a Boolean value for attrib:{0}

Cause: The value given for the attribute in custom events expression is of a different type.

Action: Give a boolean value for the attribute.
Level: 1

Type: ERROR

Impact: Other

IAU-01056: Expecting a Number value for attrib:{0}

Cause: The value given for the attribute in custom events expression is of a different type.

Action: Give a number value for the attribute.
Level: 1

Type: ERROR

Impact: Other

IAU-01057: No relational expressions allowed for Binary operator

Cause: Binary attribute is present in the custom events expression.

Action: Remove binary attribute from the custom events expression.
Level: 1

Type: ERROR

Impact: Other

IAU-01058: Expecting a Date value for attrib:{0}

Cause: A non-date value is given to the date attribute.

Action: Give a date value for the attribute.
Level: 1

Type: ERROR

Impact: Other

IAU-01059: trailing backslash in special users

Cause: Invalid special users(Users to always audit) string.

Action: Remove the trailing back slash in special users(Users to always audit)string.
Level: 1

Type: ERROR

Impact: Other

IAU-01060: Invalid config file

Cause: Config file given in importAuditConfig() command is possibly corrupted.

Action: Contact Oracle Customer Support.
Level: 1

Type: ERROR

Impact: Other

IAU-05011: Audit Loader initialization failed. The Audit loader is disabled. Caught Exception {0}

Cause: An error prevented the Audit Loader from starting.

Action: Check the diagnostic logs and contact Oracle Customer Support.
Level: 1

Type: ERROR

Impact: Other

IAU-05042: Error in reading component definition from {0}

Cause: Install might be corrupted.

Action: Check the install and contact Oracle Customer Support.
Level: 1

Type: ERROR

Impact: Other

IAU-05043: Cannot create directory for saving AuditLoader state {0}

Cause: OS error in creating directory.

Action: Check file permissions and disk space.
Level: 1

Type: ERROR

Impact: Other

IAU-05044: Cannot save AuditLoader state to file {0}

Cause: OS error in writing to state file.

Action: Check file permissions and disk space.
Level: 1

Type: ERROR

Impact: Other

IAU-05045: Cannot read AuditLoader state from file {0}

Cause: OS error in reading state file.

Action: Check file permissions or the file is possibly corrupted.
Level: 1

Type: ERROR

Impact: Other

IAU-05046: Stopping AuditLoader, caught exception: {0}

Cause: An error prevented Audit Loader from continuing.

Action: Check the diagnostic logs and contact Oracle Customer Support.
Level: 1

Type: ERROR

Impact: Other

IAU-05047: Problem in transferring audit record from file:{0} position:{1} will retry in next cycle. caught exception {2}

Cause: The database containing Audit store is probably down.

Action: Check the database availability. Restart the database if required.
Level: 1

Type: ERROR

Impact: Other

IAU-05048: Problem in transferring audit record to Repository {0}. Please verify your Repository Configuration

Cause: The database configuration is invalid or the database is down.

Action: Check Audit Store configuration and bring up the database if it is down.
Level: 1

Type: ERROR

Impact: Other

IAU-06001: Error in reading audit configuration file from {0}.

Cause: Install might be corrupted.

Action: Check the install and contact Oracle Customer Support.
Level: 1

Type: ERROR

Impact: Other

IAU-06002: Invalid {0} directory: {1}.

Cause: Invalid directory path.

Action: Check that the directory path is valid and the directory is writable.
Level: 1

Type: ERROR

Impact: Other

IAU-06003: Cannot create directory: {0}.

Cause: Unable to create directory.

Action: Check the directory path is valid and the directory is writable.
Level: 1

Type: ERROR

Impact: Other

IAU-06004: Cannot write to {0}: {1}.

Cause: Unable to create directory.

Action: Check the directory path is valid and the directory is writable.
Level: 1

Type: ERROR

Impact: Other

IAU-06005: Denied access to log directory: {0}.

Cause: Unable to read/write from/to directory

Action: Check the directory path is valid and the directory is writable.
Level: 1

Type: ERROR

Impact: Other

IAU-06006: Error in parsing audit component events definition from {0}.

Cause: Audit configuration file is possibly corrupted.

Action: Check the diagnostic logs and contact Oracle Customer Support.
Level: 1

Type: ERROR

Impact: Other

IAU-06007: Failed while reloading audit configuration.

Cause: Audit configuration file is possibly corrupted.

Action: Check the diagnostic logs and contact Oracle Customer Support.
Level: 1

Type: ERROR

Impact: Other

IAU-06008: Error while evaluating event auditability.

Cause: Audit configuration file is possibly corrupted.

Action: Check the diagnostic logs and contact Oracle Customer Support.
Level: 1

Type: ERROR

Impact: Other

IAU-06009: Failed to log audit event.

Cause: Error in loading audit configuration or writing to audit logs.

Action: Check the diagnostic logs and contact Oracle Customer Support.
Level: 1

Type: ERROR

Impact: Other

IAU-62000: auditor initialization failed

Cause: The auditor structure passed to the initialize audit function was NULL.

Action: Check the diagnostic logs and contact Oracle Customer Support.
Level: 1

Type: INTERNAL_ERROR

Impact: Other

IAU-62001: audit context initialization failed

Cause: Initialization of the audit context had failed.

Action: Check the diagnostic logs and contact Oracle Customer Support.
Level: 1

Type: INTERNAL_ERROR

Impact: Other

IAU-62002: initialization of the xml context failed

Cause: The creation of the xml context used for parsing the xml files had failed.

Action: Check the diagnostic logs and contact Oracle Customer Support.
Level: 1

Type: INTERNAL_ERROR

Impact: Other

IAU-62003: parsing of component_events.xml file failed

Cause: Install is possibly corrupted.

Action: Check the install. Contact Oracle Customer Support if needed.
Level: 1

Type: ERROR

Impact: Other

IAU-62004: parsing of auditconfig.xml file failed

Cause: Install is possibly corrupted.

Action: Check the install. Contact Oracle Customer Support if needed.
Level: 1

Type: ERROR

Impact: Other

IAU-62005: parsing of generic_events.xml file failed

Cause: Install is possibly corrupted.

Action: Check the install. Contact Oracle Customer Support if needed.
Level: 1

Type: ERROR

Impact: Other

IAU-62006: ORACLE_HOME environment variable not set

Cause: The environment variable ORACLE_HOME was not set.

Action: Set the ORACLE_HOME environment variable.
Level: 1

Type: ERROR

Impact: Other

IAU-62007: COMPONENT_CONFIG_PATH environment variable not set

Cause: The environment variable COMPONENT_CONFIG_PATH was not set.

Action: Set the COMPONENT_CONFIG_PATH to point to the location of the auditconfig.xml file.
Level: 1

Type: ERROR

Impact: Other

IAU-62008: ORACLE_INSTANCE environment variable not set

Cause: The environment variable ORACLE_INSTANCE was not set.

Action: Set the ORACLE_INSTANCE environment variable.
Level: 1

Type: Error

Impact: Other

IAU-62009: COMPONENT_NAME environment variable not set

Cause: The COMPONENT_NAME environment variable was neither set nor was the component_events.xml file present in the expected default location.

Action: Check if the component_events.xml file is present in the expected default location or set the COMPONENT_NAME environment variable to point to the correct component name.
Level: 1

Type: Error

Impact: Other

IAU-62010: COMPONENT_TYPE environment variable was not set

Cause: The COMPONENT_TYPE environment variable was neither set nor was the component_events.xml file present in the expected default location.

Action: Check if the component_events.xml file is present in the expected default location or set the COMPONENT_TYPE environment variable to point to the correct component type.
Level: 1

Type: Error

Impact: Other

IAU-62011: auditor event failure

Cause: NLL audit event structure was passed.

Action: Check the diagnostic logs and contact Oracle Customer Support.
Level: 1

Type: INTERNAL_ERROR

Impact: Other

IAU-62012: audit event creation failed

Cause: The creation of the audit event failed.

Action: Contact Oracle Customer Support.
Level: 1

Type: ERROR

Impact: Other

IAU-62013: audit event name not set

Cause: The audit event name was not set.

Action: Contact Oracle Customer Support.
Level: 1

Type: INTERNAL_ERROR

Impact: Other

IAU-62014: audit event category not set

Cause: The audit event category name was not set.

Action: Contact Oracle Customer Support.
Level: 1

Type: INTERNAL_ERROR

Impact: Other

IAU-62015: audit custom expression parsing failed

Cause: Parsing of the custom expression had failed.

Action: Check if the custom expression used in the audit configuration is valid.
Level: 1

Type: Error

Impact: Other

IAU-62016: audit log file creation failed

Cause: OS error in creating the file.

Action: Check file permissions and disk space.
Level: 1

Type: Error

Impact: Other

IAU-62017: logging of audit data failed

Cause: Error in loading audit configuration or writing to the audit logs.

Action: Check the diagnostic logs for more info. Contact Oracle Customer Support if needed.
Level: 1

Type: INTERNAL_ERROR

Impact: Other

IAU-62018: timestamp error

Cause: There was a problem with getting the current date and time.

Action: Check the diagnostic logs and contact Oracle Customer Support.
Level: 1

Type: ERROR

Impact: Other

IAU-62019: audit enabled check failed

Cause: Invalid values assgined to audit event attributes.

Action: Check the diagnostic logs and contact Oracle Customer Support.
Level: 1

Type: ERROR

Impact: Other

IAU-62020: busstop initialization failed

Cause: The initialization of the busstop structure failed.

Action: Contact Oracle Customer Support.
Level: 1

Type: INTERNAL_ERROR

Impact: Other

IAU-62021: busstop open failed

Cause: OS error in creating or opening the bus-stop file.

Action: Check the file permissions and disk space.
Level: 1

Type: ERROR

Impact: Other

IAU-62023: audit config reload failed

Cause: There was a problem in reloading the audit config data that has been modified.

Action: Check the diagnostic logs and contact Oracle Customer Support.
Level: 1

Type: ERROR

Impact: Other

46 IFS-47010 to IFS-47091

IFS-47010: Argument ''{0}'' cannot be null.

Cause: Data error.

Action: Enter a non-null value for the argument.
Level: 1

Type: ERROR

Impact: Configuration

IFS-47011: Argument ''{0}'' must be a String value.

Cause: Data error.

Action: Enter a String value for the argument.
Level: 1

Type: ERROR

Impact: Configuration

IFS-47012: Argument ''{0}'' must be a String value or a sequence of String values.

Cause: Data error.

Action: Enter a String value or a sequence of String values for the argument.
Level: 1

Type: ERROR

Impact: Configuration

IFS-47020: {0} is not an Integer value.

Cause: Data error.

Action: Enter an Integer value.
Level: 1

Type: ERROR

Impact: Configuration

IFS-47021: {0} is not a Long value.

Cause: Data error.

Action: Enter a Long value.
Level: 1

Type: ERROR

Impact: Configuration

IFS-47022: {0} is not a Double value.

Cause: Data error.

Action: Enter a Double value.
Level: 1

Type: ERROR

Impact: Configuration

IFS-47023: {0} is not a Boolean value.

Cause: Data error.

Action: Enter a Boolean value.
Level: 1

Type: ERROR

Impact: Configuration

IFS-47024: {0} is not a String value.

Cause: Data error.

Action: Enter a String value.
Level: 1

Type: ERROR

Impact: Configuration

IFS-47025: {0} is not a String array value.

Cause: Data error.

Action: Enter a String array value.
Level: 1

Type: ERROR

Impact: Configuration

IFS-47026: Data type ''{0}'' is not supported for scalar values.

Cause: Data error.

Action: Choose one of the supported data types for scalar values: INTEGER, LONG, DOUBLE, BOOLEAN, or STRING.
Level: 1

Type: ERROR

Impact: Configuration

IFS-47027: Data type ''{0}'' is not supported for list values.

Cause: Data error.

Action: Choose the supported data type for list values: STRING_ARRAY.
Level: 1

Type: ERROR

Impact: Configuration

IFS-47030: Could not find any MBean for Oracle UOA domain properties.

Cause: Access error for Oracle UOA domain property MBeans.

Action: Make sure that the Oracle UOA domain property MBeans are available, and retry the command.
Level: 1

Type: ERROR

Impact: Configuration

IFS-47031: Could not list Oracle UOA domain properties - {0}.

Cause: Access error for Oracle UOA domain property MBeans.

Action: Make sure that the Oracle UOA domain property MBeans are available, and retry the command.
Level: 1

Type: ERROR

Impact: Configuration

IFS-47032: Could not update Oracle UOA domain properties - {0}.

Cause: Access error for Oracle UOA domain property MBeans.

Action: Make sure that the Oracle UOA domain property MBeans are available, and retry the command.
Level: 1

Type: ERROR

Impact: Configuration

IFS-47040: Could not find any MBean for Oracle UOA node configurations.

Cause: Access error for Oracle UOA node configuration MBeans.

Action: Make sure that the Oracle UOA node configuration MBeans are available, and retry the command.
Level: 1

Type: ERROR

Impact: Configuration

IFS-47041: Could not find these node configurations: {0}.

Cause: Data error.

Action: Specify a valid node configuration.
Level: 1

Type: ERROR

Impact: Configuration

IFS-47042: Could not find a node configuration named ''{0}''.

Cause: Data error.

Action: Specify a valid node configuration.
Level: 1

Type: ERROR

Impact: Configuration

IFS-47043: Could not list Oracle UOA node configurations - {0}.

Cause: Access error for Oracle UOA node configuration MBeans.

Action: Make sure that the Oracle UOA node configuration MBeans are available, and retry the command.
Level: 1

Type: ERROR

Impact: Configuration

IFS-47044: Could not update Oracle UOA node configurations - {0}.

Cause: Access error for Oracle UOA node configuration MBeans.

Action: Make sure that the Oracle UOA node configuration MBeans are available, and retry the command.
Level: 1

Type: ERROR

Impact: Configuration

IFS-47050: Could not find any MBean for Oracle UOA server configurations.

Cause: Access error for Oracle UOA server configuration MBeans.

Action: Make sure that the Oracle UOA server configuration MBeans are available, and retry the command.
Level: 1

Type: ERROR

Impact: Configuration

IFS-47051: Could not find these server configurations: {0}.

Cause: Data error.

Action: Specify a valid server configuration.
Level: 1

Type: ERROR

Impact: Configuration

IFS-47052: Could not find a server configuration named ''{0}''.

Cause: Data error.

Action: Specify a valid server configuration.
Level: 1

Type: ERROR

Impact: Configuration

IFS-47053: Could not list Oracle UOA server configurations - {0}.

Cause: Access error for Oracle UOA server configuration MBeans.

Action: Make sure that the Oracle UOA server configuration MBeans are available, and retry the command.
Level: 1

Type: ERROR

Impact: Configuration

IFS-47054: Could not update Oracle UOA server configurations - {0}.

Cause: Access error for Oracle UOA server configuration MBeans.

Action: Make sure that the Oracle UOA server configuration MBeans are available, and retry the command.
Level: 1

Type: ERROR

Impact: Configuration

IFS-47060: Could not find any MBean for Oracle UOA service configurations.

Cause: Access error for Oracle UOA service configuration MBeans.

Action: Make sure that the Oracle UOA service configuration MBeans are available, and retry the command.
Level: 1

Type: ERROR

Impact: Configuration

IFS-47061: Could not find these service configurations: {0}.

Cause: Data error.

Action: Specify a valid service configuration.
Level: 1

Type: ERROR

Impact: Configuration

IFS-47062: Could not find a service configuration named ''{0}''.

Cause: Data error.

Action: Specify a valid service configuration.
Level: 1

Type: ERROR

Impact: Configuration

IFS-47063: Could not list Oracle UOA service configurations - {0}.

Cause: Access error for Oracle UOA service configuration MBeans.

Action: Make sure that the Oracle UOA service configuration MBeans are available, and retry the command.
Level: 1

Type: ERROR

Impact: Configuration

IFS-47064: Could not update Oracle UOA service configurations - {0}.

Cause: Access error for Oracle UOA service configuration MBeans.

Action: Make sure that the Oracle UOA service configuration MBeans are available, and retry the command.
Level: 1

Type: ERROR

Impact: Configuration

IFS-47070: Could not find any MBean for the Oracle UOA node.

Cause: Access error for Oracle UOA node MBeans.

Action: Make sure that the Oracle UOA node MBean is available, and retry the command.
Level: 1

Type: ERROR

Impact: Configuration

IFS-47071: Could not find any MBean for the Oracle UOA node on this WebLogic server.

Cause: Access error for Oracle UOA node MBeans.

Action: Make sure that the Oracle UOA node MBean is available, and retry the command.
Level: 1

Type: ERROR

Impact: Configuration

IFS-47072: Could not find these Oracle UOA nodes: {0}.

Cause: Data error.

Action: Specify a valid Oracle UOA node.
Level: 1

Type: ERROR

Impact: Configuration

IFS-47073: Could not find an Oracle UOA node named ''{0}''.

Cause: Data error.

Action: Specify a valid Oracle UOA node.
Level: 1

Type: ERROR

Impact: Configuration

IFS-47074: Could not find these Oracle UOA servers on node ''{0}'': {1}.

Cause: Data error.

Action: Specify valid Oracle UOA servers.
Level: 1

Type: ERROR

Impact: Configuration

IFS-47075: Could not list Oracle UOA servers - {0}.

Cause: Access error for Oracle UOA server MBeans.

Action: Make sure that the Oracle UOA server MBeans are available, and retry the command.
Level: 1

Type: ERROR

Impact: Configuration

IFS-47080: ''{0}'' is not a supported operation on Oracle UOA servers.

Cause: Data error.

Action: Specify one of the operations supported on Oracle UOA servers: start, stop, restart, suspend, or resume.
Level: 1

Type: ERROR

Impact: Configuration

IFS-47081: Could not perform operation ''{0}'' on Oracle UOA server ''{1}'' - {2}.

Cause: Operation error for Oracle UOA server MBeans.

Action: Make sure that the Oracle UOA server MBeans are available, and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

IFS-47082: Could not manage Oracle UOA servers - {0}.

Cause: Operation error for Oracle UOA server MBeans.

Action: Make sure that the Oracle UOA server MBeans are available, and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

IFS-47090: Could not create Oracle UOA server ''{0}'' - {1}.

Cause: Operation error for Oracle UOA node MBeans.

Action: Make sure that the Oracle UOA node MBean is available, and retry the creation.
Level: 1

Type: ERROR

Impact: Configuration

IFS-47091: Could not delete Oracle UOA server ''{0}'' - {1}.

Cause: Operation error for Oracle UOA node MBeans.

Action: Make sure that the Oracle UOA node MBean is available, and retry the deletion.
Level: 1

Type: ERROR

Impact: Configuration

47 INST-01000 to INST-10117

INST-01000: Internal Error: Undefined module found: {0}.

Cause: The module {0} present in engineConfig.xml is undefined.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01001: Abnormal Program Termination.

Cause: The program has experienced an error for some internal or unexpected reason.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01002: Error: Undefined flag: {0}.

Cause: The flag {0} specified on the command line is not supported.

Action: Refer to the usage: setup.exe -help
Level: 1

Type: ERROR

Impact: Installation

INST-01003: Error: Response file not specified.

Cause: A response file must be provided when installing in the {0} mode.

Action: Specify a valid response file. Usage: setup.exe -s -response <Full path to response file>
Level: 1

Type: ERROR

Impact: Installation

INST-01004: Internal Error: File not found: {0}.

Cause: Page data definition {0} for page {1} not found.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01005: Internal Error: Multiple pages found with "{0}" attribute set to true.

Cause: There can be only one page with {0} attribute set to true.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01006: Internal Error: No page found with the "{0}" attribute set to true.

Cause: At least one page must have the "{0}" attribute set to true.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01007: Error: Invalid input: "{0}"

Cause: This error is caused due to invalid input on the command line

Action: Refer to the command line usage.
Level: 1

Type: ERROR

Impact: Installation

INST-01008: Internal Error: Operation not specified

Cause: Engine did not find an operation to run in this configuration.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01009: Error: Invalid flags specified for operation "{0}": "{1}"

Cause: Flags specified by the user on the command line are not supported for this operation:{0}

Action: Refer to the command line usage.
Level: 1

Type: ERROR

Impact: Installation

INST-01010: Internal Error: Parse error:{0}

Cause: A parse error occurred. The file:"{0}" is not in proper format.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01011: Internal Error: More than one incompatible operation specified: "{0}", "{1}"

Cause: Incompatible operation specified

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01012: Internal Error: More than one incompatible mode is specified at a time: "{0}", "{1}"

Cause: Incompatible modes specified

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01013: Internal Error: Default mode not specified for operation:{0}

Cause: Default mode not specified

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01014: Internal Error: Default Operation not specified.

Cause: Default Operation not specified

Action: Contact Oracle Support Services with these log files {0}{1}.
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01015: Internal Error: Found cyclic references to page: "{0}". Verify file: "{1}".

Cause: Cyclic references to other pages were found in the page data file: {0}

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01016: Internal Error: Multiple references of page: "{0}" found in the "{1}" section for page: "{2}"

Cause: Multiple next page references are not supported by the Oracle Install Engine.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01017: Internal Error: The following pages do not have a default next page specified: "{0}"

Cause: Default Next Page is mandatory for each page.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01018: Internal Error: Duplicate definition found for pages: "{0}".

Cause: Duplicate definition of pages detected.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01019: Internal Error: Next page sequence not specified for the following pages: "{0}".

Cause: In cases where multiple next pages follow this page, next page sequence is mandatory to define the page flow.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01020: Internal Error: Page definition not found for: "{0}".

Cause: Each Page should be accompanied by its page definition in the page data file.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01021: Internal Error: Page name not specified for file: "{0}".

Cause: Page name not specified

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01022: Internal Error: Page name mismatch. Names specified: "{0}" and "{1}".

Cause: Page name mismatch

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01023: Internal Error: Unable to provide usage

Cause: No usage available for this option: {0}. For more help refer this to Oracle Support Services.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01024: Invalid checkpoint file: {0}.

Cause: The existing checkpoint file is not in the correct format.

Action: Delete the invalid checkpoint file:{0}
Level: 1

Type: WARNING

Impact: Installation

INST-01025: Invalid checkpoint file: {0}. The release and/or version of the product in the checkpoint does not match the current product. {1}.

Cause: Not a valid checkpoint file for the current release/version.

Action: Delete the invalid checkpoint file
Level: 1

Type: WARNING

Impact: Installation

INST-01026: Response File parse error at Line no: {0} - {1}

Cause: The response file may be corrupted or has errors

Action: Correct the errors in the response file and try the install operation again.Check if you have missed specifying square brackets around the section names
Level: 1

Type: ERROR

Impact: Installation

INST-01027: Section name cannot be empty and should be enclosed in square brackets.

Cause: The Response File is not a valid response file. The Section Name is not specified or is not specified properly.

Action: The Response Files are organized into 4 sections namely ENGINE, GENERIC, SYSTEM AND APPLICATIONS. Each Section Should be enclosed in square brackets and appropriate entries should be specified under them (Example: [Generic]). Check the Section Names.
Level: 1

Type: ERROR

Impact: Installation

INST-01028: Error: No Section defined.

Cause: The Response File does not have any valid sections specified. The Response File is organized into 4 sections namely ENGINE, GENERIC, SYSTEM and APPLICATIONS.All Section Names are specified within square brackets.

Action: Verify the Specified Response Files for valid Section Names and Syntaxes
Level: 1

Type: ERROR

Impact: Installation

INST-01029: Response File Parse Error : No Equal Symbol "=" was found

Cause: The Format of specifying the value for a variable inside the response file is as VARIABLE_NAME=VALUE. The Equal Symbol "=" was missed

Action: Correct the Response File to specify the value for a variable as VARIABLE_NAME=VALUE. Insert the Equal Symbol "=" in appropriate position to correct the same
Level: 1

Type: ERROR

Impact: Installation

INST-01030: Response File Parse Error

Cause: The Variable {0} was not Found in the Response File

Action: Specify the Variable in the Response File. The Syntax of specifying a variable is as VARIABLE_NAME=VALUE
Level: 1

Type: ERROR

Impact: Installation

INST-01031: Response File Parse Warning. No value found. Ignoring.

Cause: The Variable {0} was found in the Response File with no value assigned to it and hence it was ignored while the Response File was Parsed.

Action: Specify the corresponding value.
Level: 1

Type: WARNING

Impact: Installation

INST-01032: Internal Error: Unable to create the Configuration Manager.

Cause: Configuration Files are not proper:{0}

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01033: Internal Error: Fatal Error Occurred while loading Configuration Actions.

Cause: Configuration Action Locations specified are incorrect:{0}

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01034: Internal Error: Fatal Error Occurred while publishing Configuration Actions.

Cause: Configuration Actions are improper:{0}

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01035: Internal Error: Fatal Error Occurred while loading Configuration Actions.

Cause: Configuration Actions are improper:{0}

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01036: Internal Error: Fatal Error Occurred while setting data for Configuration Actions.

Cause: Variable: {0} required by Action: {1} not found.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01037: Internal Error: Fatal Error Occurred while initializing data for Configuration Action.

Cause: Variable: {0} required by Action: {1} not initialized.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01038: Internal Error: Fatal Error Occurred while loading Configuration Action:{0}.

Cause: Class: {0} not found.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01039: Internal Error: Fatal Error Occurred while running lifecycle methods for Configuration Actions.

Cause: Lifecycle Error

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01040: Internal Error: There was an error while copying files to this location: {0}. Installation cannot continue.

Cause: Error in copying files

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01041: Response File Location:{0} is not readable.

Cause: Response File does not exist or does not have read permission. Response File path contains special characters.

Action: Ensure that the response file exists and is readable. The response file path must not contain any special characters.Only Alphanumeric, _, dot, and space characters are allowed.
Level: 1

Type: ERROR

Impact: Installation

INST-01042: An error occurred while reading the response file.

Cause: Response File does not exist at the specified location. Response file is not in the correct format.

Action: Ensure that the response file exists. Ensure that the Response File is in the correct format. The Response Files are organized into 4 sections namely ENGINE, GENERIC, SYSTEM AND APPLICATIONS.Each Section Should be enclosed in square brackets and appropriate entries should be specified under them.
Level: 1

Type: ERROR

Impact: Installation

INST-01043: Internal Error: Response File location not defined.

Cause: The file location provided to the writer is empty.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01044: Response File Location: {0} is not writable.

Cause: The specified file already exists or user does not have write permission in the given location. Response File path contains special characters.

Action: Ensure that the response file location is writable. The response file path must not contain any special characters.Only Alphanumeric,_,dot and space characters are allowed.
Level: 1

Type: ERROR

Impact: Installation

INST-01045: Response File Parse Error: Section Name "{0}" is invalid.

Cause: Section "{0}" does not exist.

Action: Ensure that the Section name is one of the following 1. ENGINE 2. GENERIC 3. SYSTEM 4. APPLICATIONS
Level: 1

Type: WARNING

Impact: Installation

INST-01046: Internal Error: Invalid Install Session.

Cause: Data Model is empty.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01047: Silent Install cannot continue, error {0}.

Cause: Data provided in the response file is insufficient to complete this installation. Data provided in the response file is incorrect and did not pass all the validations.

Action: Fill the indicated information in the response file and restart installation. Verify and change the indicated values specified in the response file and restart installation.
Level: 1

Type: ERROR

Impact: Installation

INST-01048: Internal Error: Aborting Silent Install.

Cause: Error while running silent install

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01049: There was a problem in creating the page sequence. Response File Data is incomplete.Error: {0}

Cause: Data provided in the response file is insufficient to complete this installation.

Action: Fill the indicated information in the response file and restart installation.
Level: 1

Type: ERROR

Impact: Installation

INST-01050: Some required prerequisites for this installation have failed. Installation cannot continue

Cause: Response File does not exist at the specified location. Response file is not in the correct format.

Action: Ensure that the response file exists. Ensure that the Response File is in the correct format. The Response Files are organized into 4 sections namely ENGINE, GENERIC, SYSTEM AND APPLICATIONS.Each Section Should be enclosed in square brackets and appropriate entries should be specified under them.
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01051: Some required prerequisites for this installation have failed. Installation cannot continue

Cause: Failed Prerequisite: {0}

Action: Take a look at the failed prerequisites and fix the necessary items. Restart the installation after you are done.
Level: 1

Type: NOTIFICATION

Impact: Installation

INST-01052: Error: Property: {0} does not belong to the Section: {1}. It will be ignored.

Cause: All variables in the response files are associated with a valid section. The variable specified in the response file does not belong to the section it appears in.

Action: Check if the variable is actually a valid property name and is present in the appropriate section.
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01053: [CONFIG]:: ACTION: {0} running.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Installation

INST-01054: [CONFIG]:: STEP {0} running.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Installation

INST-01055: Configuration Directory:{0} does not exist.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Installation

INST-01056: The file:{0} cannot be loaded as a configuration action.

Cause: The Configuration framework loads the configuration actions from jars or xml files. This file does not represent a configuration action.

Action: Correct the file and retry
Level: 1

Type: WARNING

Impact: Installation

INST-01057: Invalid Log level: {0} specified.

Cause: Log levels that can be specified on the command line can be: INFO, ERROR, DEBUG

Action: Specify a valid log level.
Level: 1

Type: WARNING

Impact: Installation

INST-01058: Log level changed to: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Installation

INST-01059: Following checks will be retried by the Prerequisites checker:{0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Installation

INST-01060: Error: Prerequisite check: {0} has failed.

Cause: Prerequisite check: {0} has failed

Action: Correct the failed prerequisite and retry
Level: 1

Type: NOTIFICATION

Impact: Installation

INST-01061: Warning: An optional Prerequisite check: {0} has failed.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Installation

INST-01062: Invalid Inventory Pointer location: {0} specified on the command line.

Cause: Inventory pointer file does not exist. Directory specified for the inventory cannot be created.

Action: Create a valid inventory pointer file at the location which is specified on the command line. Inventory pointer file is a property file containing two entriesinventory_loc=<Directory where new inventory is present or to be created>GROUP=<group of the installing user>
Level: 1

Type: ERROR

Impact: Installation

INST-01063: Invalid inventory location:{0}.

Cause: Directory specified for the inventory cannot be created.

Action: Provide a writable directory for the inventory.
Level: 1

Type: ERROR

Impact: Installation

INST-01064: Oracle home value was not set by the Installer.

Cause: Required Oracle home value not set

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01065: Library: {0} required for Action: {1} not found.

Cause: Required library not found

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01066: Configuration Data Store not found.

Cause: Required Configuration Data Store not found

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01067: Error while loading Configuration Actions from file: {0}

Cause: Problem while loading the configuration actions

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01068: No configurations defined for this installation.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Installation

INST-01069: Internal Error: Unable to load Configuration Action: {0}

Cause: Class not found: {0}

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-01070: Internal Error: Entry Point for Configuration Not Found.

Cause: Entry point not found

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-03000: Error: ClassName is blank in roadmap file for page: {0}

Cause: The ClassName provided for the page named {0} is either null or blank or the class is nonexistent.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: ERROR

Impact: Installation

INST-03001: Error: ClassName is null or not provided in roadmap file for page: {0}

Cause: The ClassName provided for the page named {0} is either null or blank or the class is nonexistent.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: ERROR

Impact: Installation

INST-03002: Error: Class {0} is not found.

Cause: Either Class {0} is not present or it has an invalid format or it has been compiled with a different version of java compiler.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: ERROR

Impact: Installation

INST-03003: Internal Error: Runtime error occurred while loading page : {0}

Cause: Error occurred while loading the class for page {0}

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-03004: Internal Error: The Resource Key name provided is blank

Cause: Resource Key name provided is blank

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-03005: Internal Error: Exception occurred while constructing the Navigation Tree

Cause: Error while constructing the Navigation Tree

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-03006: Internal Error: Exception occurred while preparing the Action Queue

Cause: Error occurred while preparing the Action Queue

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-03007: Internal Error: Exception occurred while loading the help files.

Cause: The help files are corrupt or the help files are not present.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-03008: Internal Error: Exception occurred while parsing the displayConfig.xml file

Cause: The format of displayConfig.xml is corrupt.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-03009: Internal Error: Exception occurred launching the welcome window.

Cause: Error occurred launching the welcome window

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-03010: Internal Error: Exception occurred launching the Wizard.

Cause: Error occurred launching the Wizard

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-03011: Internal Error: Exception occurred while setting the UI default properties.

Cause: Error occurred while setting the UI default properties

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-03012: Internal Error: Unknown Exception occurred.

Cause: Unknown exception occurred during installation

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-03013: Internal Error: Exception while creating the Wizard Sequence

Cause: The sequence provided in roadmap.xml is not proper.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-03014: Internal Error: Exception occurred while creating the validation tree

Cause: Error occurred while creating the validation tree

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-03015: Internal Error: Exception occurred while selecting the next page.

Cause: Error occurred while selecting the next page

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-03016: Internal Error: Exception occurred while updating the data model with user-specified data

Cause: Error occurred while updating the data model with user-specified data

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-03017: Internal Error: Exception occurred while restoring the data from checkpoint.

Cause: The checkpoint data is corrupted.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-03018: Internal Error: Exception occurred while shrinking the image.

Cause: Either the image is corrupted or the machine has not enough memory to perform the operation.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-03019: Internal Error: Error while fetching the image.

Cause: Either the image is not present or the image is corrupted.

Action: Provide the following files to Oracle Support Services: "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-03020: Error in connecting to the Database. Connect string is missing

Cause: Connect String is missing

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-03021: Error in connecting to the Database

Cause: Unable to connect to the Database with the given credentials

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct. Enter a valid user name with DBA privileges
Level: 1

Type: ERROR

Impact: Installation

INST-03022: Error in validating Database details. Schema Type is missing

Cause: Schema Type is missing

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-03023: Error in validating Database details

Cause: Unable to connect to the Database with the given credentials. Listener could be down

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct. Enter a valid user name with DBA privileges
Level: 1

Type: ERROR

Impact: Installation

INST-03024: Error in validating Database details

Cause: Unable to connect to the Database with the given credentials. Invalid user name/password

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct. Enter a valid user name with DBA privileges
Level: 1

Type: ERROR

Impact: Installation

INST-03025: Error in validating Database details

Cause: Unable to connect to the Database with the given credentials. User is not a SYSDBA

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct. Enter a valid user name with DBA privileges
Level: 1

Type: ERROR

Impact: Installation

INST-03026: Error in validating Database details

Cause: Unable to connect to the Database with the given credentials. Database could be down

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct. Enter a valid user name with DBA privileges
Level: 1

Type: ERROR

Impact: Installation

INST-03027: Error in validating Database details

Cause: Unable to connect to the Database with the given credentials. Invalid service id

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct. Enter a valid user name with DBA privileges
Level: 1

Type: ERROR

Impact: Installation

INST-03028: Error in validating Database details

Cause: Unable to connect to the Database with the given credentials. Invalid service name

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct. Enter a valid user name with DBA privileges
Level: 1

Type: ERROR

Impact: Installation

INST-03029: Error in validating Database details

Cause: Could not find {0} type Schema in the Database

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct. Enter a valid user name with DBA privileges
Level: 1

Type: ERROR

Impact: Installation

INST-05100: Error in obtaining default DN Value

Cause: Error in processing the handler

Action: No default DN provided
Level: 1

Type: ERROR

Impact: Installation

INST-05115: Error in selection of component configuration.

Cause: At least one component needs to be selected for configuration

Action: Select at least one of Oracle Directory Integration Platform, Oracle Internet Directory, Oracle Virtual Directory or Oracle Directory Service Manager component to configure.
Level: 1

Type: ERROR

Impact: Installation

INST-05116: Error in obtaining Schema names.

Cause: One or more of the Database Connection parameters is missing.

Action: Enter all the fields in the screen.
Level: 1

Type: ERROR

Impact: Installation

INST-05117: Error in obtaining Schema names.

Cause: The format of Database Host field value is improper.

Action: Enter Database Host field in proper format.
Level: 1

Type: ERROR

Impact: Installation

INST-05118: The specified username does not have Database Administrator privileges.

Cause: Username {0} does not have Database Administrator privileges.

Action: Enter the username with Database Administrator privileges.
Level: 1

Type: ERROR

Impact: Installation

INST-05119: Error in retrieving schema details for component {0}.

Cause: The Schema for corresponding component is not loaded in the Database

Action: Make sure that the Database is loaded with the schema {0} or unselect the component {1} from Applications To Configure Screen.
Level: 1

Type: ERROR

Impact: Installation

INST-05120: Error in retrieving schema version.

Cause: Schema version for component {0} is missing.

Action: Check the values. Make sure the Database is loaded with required schemas.
Level: 1

Type: ERROR

Impact: Installation

INST-05121: An unsupported schema is detected.

Cause: The Schema Version for component {0} is less than 10.1.2.0.0

Action: This is an unsupported schema version. Upload the newer schema to continue installation.
Level: 1

Type: ERROR

Impact: Installation

INST-05122: Upgrade Scenario Detected

Cause: The Schema Version for component Oracle Internet Directory is {0}.

Action: The database you selected is associated with a previous version of Oracle Application Server. After the installation is complete, you must run the Oracle Fusion Middleware Upgrade Assistant. Choose YES to continue or NO to go back to the same screen and specify different database details.
Level: 1

Type: ERROR

Impact: Installation

INST-05123: Error while retrieving the schema Name.

Cause: The Schema Name for component {0} is missing.

Action: Enter valid Database details.
Level: 1

Type: ERROR

Impact: Installation

INST-05124: Error in connecting to the Database.

Cause: Could not connect to the Database with the given credentials

Action: Check the values. Make sure the Database is up and running and connect string, username and password are correct.
Level: 1

Type: ERROR

Impact: Installation

INST-05125: Error in retrieving schema details.

Cause: Database schemas were not found in the Database

Action: Run Oracle Metadata Repository Creation Utility and load the schemas.
Level: 1

Type: ERROR

Impact: Installation

INST-05126: Error in connecting to the LDAP.

Cause: One or more of LDAP Connection parameters is missing

Action: Enter all the fields in the screen.
Level: 1

Type: ERROR

Impact: Installation

INST-05127: Error in connecting to the LDAP.

Cause: Could not connect to the LDAP with the given credentials on SSL port

Action: Check the values of LDAP Connect parameters. Make sure LDAP HostName and SSL Port are in proper format.
Level: 1

Type: ERROR

Impact: Installation

INST-05128: Error while retrieving {0} password from LDAP.

Cause: The {0} password retrieved from LDAP is empty

Action: Check the values. Make sure the LDAP details are correct.
Level: 1

Type: ERROR

Impact: Installation

INST-05129: Error in connecting to the LDAP.

Cause: Could not connect to the LDAP with the given credentials on SSL port.

Action: Check the values. Make sure the LDAP is up and running on SSL port and LDAP Connect String, username and password are correct.
Level: 1

Type: ERROR

Impact: Installation

INST-05131: Error in component selection for Oracle Identity Management installation.

Cause: No components selected for Oracle Identity Management installation.

Action: Select at least one component for installation.
Level: 1

Type: ERROR

Impact: Installation

INST-05135: Error in retrieving default JPS attributes from LDAP.

Cause: The LDAP hostname is missing.

Action: Specify a valid Oracle Database eligible for OID upgrade.
Level: 1

Type: ERROR

Impact: Installation

INST-05136: Error in retrieving default JPS attributes from LDAP.

Cause: The LDAP port number is missing.

Action: Specify a valid Oracle Database eligible for OID upgrade.
Level: 1

Type: ERROR

Impact: Installation

INST-05137: Error in retrieving Oracle Internet Directory Details from the database

Cause: The Oracle Internet Directory Details in the database are not available.

Action: Check the repository mentioned for Oracle Single Sign On upgrade.
Level: 1

Type: ERROR

Impact: Installation

INST-05138: Error in retrieving Oracle Internet Directory Details from the database

Cause: Exception thrown while retrieving Oracle Internet Directory Details from the repository

Action: Check the repository mentioned for Oracle Single Sign On upgrade.
Level: 1

Type: ERROR

Impact: Installation

INST-05139: Upgrade Scenario Detected

Cause: The Schema Version for component Oracle Single Sign On is {0}

Action: The database you selected is associated with a previous version of Oracle Application Server. After the installation is complete, you must run the Oracle Fusion Middleware Upgrade Assistant. Choose YES to continue or NO to go back to the same screen and specify different database details.
Level: 1

Type: ERROR

Impact: Installation

INST-05141: Missing Schema Detected

Cause: The {0} component schema is not loaded.

Action: One or more component schemas are not loaded in the specified database. Choose YES to continue or NO to go back to the same screen and specify different database details.
Level: 1

Type: ERROR

Impact: Installation

INST-05142: Missing Schema Detected

Cause: The {0} component schema is not loaded.

Action: One or more component schemas are not loaded in the specified database. Choose YES to continue or NO to go back to the same screen and specify different database details.
Level: 1

Type: ERROR

Impact: Installation

INST-05145: Error in checking for second OID installation against same database.

Cause: Exception thrown during second OID installation check.

Action: Choose valid ODS schema in the screen. Make sure that OID is up and running.
Level: 1

Type: ERROR

Impact: Installation

INST-05146: ODS Schema in use

Cause: ODS Schema is in use.

Action: The ODS schema chosen is already being used by an existing OID. Hence, the new OID being configured would reuse the same schema. Choose YES to continue or NO to choose a different ODS schema.
Level: 1

Type: ERROR

Impact: Installation

INST-05147: Missing Schemas Detected

Cause: The {0} component schemas are not loaded.

Action: One or more component schemas are not loaded in the specified database. Choose YES to continue or NO to go back to the same screen and specify different database details.
Level: 1

Type: ERROR

Impact: Installation

INST-05149: Error in selection of component configuration.

Cause: Selecting DIP only is not allowed for create domain scenario.

Action: Select OID also whenever DIP is selected.
Level: 1

Type: ERROR

Impact: Installation

INST-05150: Error in selection of component configuration.

Cause: None of the components are selected for configuration.

Action: Select at least one component for configuration.
Level: 1

Type: ERROR

Impact: Installation

INST-05151: Error in retrieving default JPS attributes from LDAP.

Cause: One or more of LDAP Connection parameters is missing

Action: Check the values. Make sure the LDAP details are correct.
Level: 1

Type: ERROR

Impact: Installation

INST-05152: Error in validating LDAP Attributes.

Cause: Error in validating LDAP Attributes.

Action: Check the values. Make sure the LDAP details are correct.
Level: 1

Type: ERROR

Impact: Installation

INST-05155: Error in JPS Attributes validation.

Cause: The value entered in the {0} field is incorrect.

Action: Check the value. Make sure the value is present in LDAP.
Level: 1

Type: ERROR

Impact: Installation

INST-05156: Error in connecting to LDAP.

Cause: Could not connect to the LDAP with the given credentials.

Action: Check the values. Make sure the LDAP is up and running.
Level: 1

Type: ERROR

Impact: Installation

INST-05159: Partial Schema Detected.

Cause: Partial Schema Detected.

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-05162: Error in connecting to LDAP.

Cause: The value entered for OID Administrator Password is incorrect.

Action: Check the value. Make sure you have entered a valid value for OID Administrator Password.
Level: 1

Type: ERROR

Impact: Installation

INST-05163: Error in connecting to LDAP.

Cause: Error in connecting to LDAP.

Action: The LDAP is not up and running. Choose YES to continue or NO to choose a different ODS schema.
Level: 1

Type: ERROR

Impact: Installation

INST-05164: {0} is missing.

Cause: {0} is missing.

Action: Enter valid value for {0}.
Level: 1

Type: ERROR

Impact: Installation

INST-05165: {0} is not valid.

Cause: Error in validating {0}.

Action: Enter valid value for {0}.
Level: 1

Type: ERROR

Impact: Installation

INST-05166: An unsupported database version is detected.

Cause: The Database version {0} is not supported.

Action: Enter Database with version equal to or higher than 10.2.0.4.0 in 10g or version equal to higher than 11.1.0.6.0 in 11g.
Level: 1

Type: ERROR

Impact: Installation

INST-05167: Database Initialization Parameter Warning

Cause: The Database initialization parameter 'processes' has a value less than 500.

Action: Recommended value for Database initialization parameter 'processes' is 500. Choose YES to continue or NO to go back to the same screen and specify different database details.
Level: 1

Type: ERROR

Impact: Installation

INST-05168: Prereqs Error

Cause: Prerequisites requirement check failed. The value of session_cached_cursors is less than 100.

Action: Required value of session_cached_cursors is 100. Specify another Database details.
Level: 1

Type: ERROR

Impact: Installation

INST-05169: Validation of Host name failed. Invalid Host

Cause: The host name entered is not valid

Action: Provide a valid host name in format host:port
Level: 1

Type: ERROR

Impact: Installation

INST-05170: Validation of Host URL failed. Invalid Host URL

Cause: The host URL entered is not valid

Action: Provide a valid host URL in format ldap://host:port or ldaps://host:port
Level: 1

Type: ERROR

Impact: Installation

INST-05171: Error in validating LDAP Credentials

Cause: Specified LDAP Type ( {0} ) is not valid

Action: Valid values are "{0}". Enter a valid LDAP Type
Level: 1

Type: ERROR

Impact: Installation

INST-05172: Cannot connect. Specified schema account is locked

Cause: Specified {0} schema account is locked

Action: Unlock the {0} schema account.
Level: 1

Type: ERROR

Impact: Installation

INST-05173: Multilingual Support Warning

Cause: Multilingual Support Warning

Action: The database you are connecting is with non-AL32UTF8 character set. Oracle strongly recommends using AL32UTF8 as the database character set. Choose YES to continue or NO to go back to the same screen and specify different database details.
Level: 1

Type: ERROR

Impact: Installation

INST-05174: Schemas existing in Database

Cause: Required schemas are already loaded in the specified database.

Action: Specify another database details or select the Use Existing Schema option.
Level: 1

Type: ERROR

Impact: Installation

INST-05175: Validation of LDAP Type failed. Invalid LDAP Type

Cause: The LDAP type entered is not valid

Action: Provide a valid LDAP type.
Level: 1

Type: ERROR

Impact: Installation

INST-05176: Validation of Host URL failed. Invalid Host URL

Cause: The host URL entered is not valid.

Action: Provide a valid SSL LDAP connection URL of the format ldaps://host:port
Level: 1

Type: ERROR

Impact: Installation

INST-05177: Invalid Oracle Identity Federation schema

Cause: The username entered is not a valid Oracle Identity Federation schema.

Action: Provide a valid Oracle Identity Federation schema name.
Level: 1

Type: ERROR

Impact: Installation

INST-05178: Error in connecting to LDAP.

Cause: Could not connect to the LDAP in SSL mode with the given credentials.

Action: Check the values. Make sure the LDAP is up and running. Provide valid SSL LDAP connection details.
Level: 1

Type: ERROR

Impact: Installation

INST-05179: Error in validating Database details

Cause: Unable to connect to the Database with the given credentials. Invalid service id

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct.
Level: 1

Type: ERROR

Impact: Installation

INST-05180: Error in validating Database details

Cause: Unable to connect to the Database with the given credentials. Invalid service name

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct.
Level: 1

Type: ERROR

Impact: Installation

INST-05181: Error in validating Database details

Cause: Unable to connect to the Database with the given credentials for {0}. Listener could be down

Action: Check the values. Make sure the Database is up and running and connect string, user name and password for {0} are correct.
Level: 1

Type: ERROR

Impact: Installation

INST-05182: Error in validating Database details

Cause: Unable to connect to the Database with the given credentials. Invalid user name/password

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct.
Level: 1

Type: ERROR

Impact: Installation

INST-05183: Error in validating Database details

Cause: Unable to connect to the Database with the given credentials. User is not a SYSDBA

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct.
Level: 1

Type: ERROR

Impact: Installation

INST-05184: Error in validating Database details

Cause: Unable to connect to the Database with the given credentials. Database could be down

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct.
Level: 1

Type: ERROR

Impact: Installation

INST-05185: Error in validating login table

Cause: The Login Table is not valid.

Action: Enter valid Login Table name.
Level: 1

Type: ERROR

Impact: Installation

INST-05186: Error in validating user id attribute

Cause: The User ID Attribute is not valid.

Action: Enter valid User ID Attribute value.
Level: 1

Type: ERROR

Impact: Installation

INST-05187: Error in validating user id attribute

Cause: The User Description Attribute is not valid.

Action: Enter valid User Description Attribute value.
Level: 1

Type: ERROR

Impact: Installation

INST-05188: Error in validating Oracle Identity Federation User Store RDBMS Attributes

Cause: The Oracle Identity Federation User Store RDBMS Attributes are not valid.

Action: Enter valid values for Login Table, User ID Attribute and User Description Attribute.
Level: 1

Type: ERROR

Impact: Installation

INST-05189: An unsupported database version is detected.

Cause: The Database version {0} is not supported for upgrade scenario.

Action: Enter Database with version equal to or higher than 10.2.0.3.0 or 11.1.0.6.0.
Level: 1

Type: ERROR

Impact: Installation

INST-05190: Unable to connect to Oracle WebLogic Middleware Administration Server. Host name is missing.

Cause: Unable to connect to Oracle WebLogic Middleware Administration Server. Host name is missing.

Action: Enter a valid host name
Level: 1

Type: ERROR

Impact: Installation

INST-05191: Error in obtaining connection with Oracle WebLogic Middleware Administration Server

Cause: Unable to connect to Oracle WebLogic Middleware Administration Server. Credentials entered are empty or contain invalid characters

Action: Make sure the Middleware Administration Server is up and host name, port, user name and administration password are correct
Level: 1

Type: ERROR

Impact: Installation

INST-05192: Unable to connect to Oracle WebLogic Middleware Administration Server. Port number is missing.

Cause: Unable to connect to Oracle WebLogic Middleware Administration Server. Port number is missing.

Action: Enter a valid port
Level: 1

Type: ERROR

Impact: Installation

INST-05193: Unable to connect Oracle WebLogic Middleware Administration Server. Admin User name is missing.

Cause: Unable to connect Oracle WebLogic Middleware Administration Server. Admin User name is missing.

Action: Enter a valid admin user name
Level: 1

Type: ERROR

Impact: Installation

INST-05194: Error in obtaining connection with Oracle WebLogic Middleware Administration Server

Cause: Unable to connect to Oracle WebLogic Middleware Administration Server.

Action: Make sure the Oracle Middleware Administration Server is up and host name, port, user name and administration password are correct
Level: 1

Type: ERROR

Impact: Installation

INST-05195: Error in installing DIP/ODSM in two different machines.

Cause: Unable to install DIP/ODSM in two different machines.

Action: Make sure DIP and ODSM are configured on the same machine.
Level: 1

Type: ERROR

Impact: Installation

INST-05196: Error in getting the IP address for the localhost.

Cause: Unable to get the IP Address for the localhost.

Action: Make sure that the security manager existing on the system allows access to the IP Address.
Level: 1

Type: ERROR

Impact: Installation

INST-05197: Error in validating LDAP Attributes.

Cause: Error in validating Domain Name.

Action: Check the values. Make sure the Domain Name is correct.
Level: 1

Type: ERROR

Impact: Installation

INST-05198: Specified Oracle Identity Federation schema is not empty.

Cause: Error in validating Oracle Identity Federation schema.

Action: Check the values. Make sure the Oracle Identity Federation schema is not loaded with Oracle Identity Federation configuration data.
Level: 1

Type: ERROR

Impact: Installation

INST-05199: Error in validating {0}.

Cause: Unable to validate the field {0}.

Action: Check the values. Make sure the value for {0} is correct.
Level: 1

Type: ERROR

Impact: Installation

INST-05200: Error in validating {0} home location

Cause: Enter a valid value for {0} home location

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-05201: Error in validating {0} home location

Cause: Specified {0} home location does not exist

Action: Provide an exisiting {0} home location
Level: 1

Type: ERROR

Impact: Installation

INST-05202: Error in validating {0} home location

Cause: Specified {0} home location does not have read/write permissions

Action: Provide read/write permissions for the {0} home location
Level: 1

Type: ERROR

Impact: Installation

INST-05203: Error in validating {0} home location

Cause: Specified {0} home location is either not valid or empty

Action: Enter a valid {0} home location
Level: 1

Type: ERROR

Impact: Installation

INST-05204: Error in validating {0} home location

Cause: Specified {0} home location is not a valid location

Action: Enter a valid {0} home location
Level: 1

Type: ERROR

Impact: Installation

INST-05205: Error in validating {0} home location

Cause: An unexpected error occurred during the validation of {0} home location

Action: Check the values
Level: 1

Type: ERROR

Impact: Installation

INST-05206: Error in validating Database block size.

Cause: The Database block size is less than 8KB.

Action: Make sure that the Database block size is greater than 8KB.
Level: 1

Type: ERROR

Impact: Installation

INST-05207: Error in connecting to OID.

Cause: Unable to connect to OID with the given credentials.

Action: Make sure that the OID is up and running.
Level: 1

Type: ERROR

Impact: Installation

INST-05208: Missing Schema Detected

Cause: The {0} component schema is not loaded.

Action: One or more component schemas are not loaded in the specified database.
Level: 1

Type: ERROR

Impact: Installation

INST-05209: Unable to configure DIP and ODSM in two different machines.

Cause: Installer has detected that DIP is already configured on a different machine in the domain, unable to configure ODSM on this machine.

Action: Make sure that DIP and ODSM are configured on the same machine.
Level: 1

Type: ERROR

Impact: Installation

INST-05210: Unable to configure DIP and ODSM in two different machines.

Cause: Installer has detected that ODSM is already configured on a different machine in the domain, unable to configure DIP on this machine.

Action: Make sure that DIP and ODSM are configured on the same machine.
Level: 1

Type: ERROR

Impact: Installation

INST-05211: Error in selection of component configuration.

Cause: The values entered for the components to configure are either not valid or empty.

Action: Provide valid values for the components to configure.
Level: 1

Type: ERROR

Impact: Installation

INST-05212: Error in selection of component configuration.

Cause: Select DIP or ODSM or OIF for configuration in expand cluster flow.

Action: Make sure that at least one cluster is selected for configuration.
Level: 1

Type: ERROR

Impact: Installation

INST-05213: Warning

Cause: The Database version {0} is not supported.

Action: Enter Database with version equal to or higher than 10.2.0.4.0 in 10g or version equal to higher than 11.1.0.7.0 in 11g. Refer to the certification matrix for supported database versions.
Level: 1

Type: ERROR

Impact: Installation

INST-05214: Error in providing cluster connection information.

Cause: The values entered to connect the cluster are either not valid or empty.

Action: Provide valid values to connect the cluster.
Level: 1

Type: ERROR

Impact: Installation

INST-05215: Error in finding cluster.

Cause: Could not find a cluster of Identity Management Components in the domain.

Action: Make sure to configure at least one cluster in the domain.
Level: 1

Type: ERROR

Impact: Installation

INST-05216: Error in obtaining connection with Oracle WebLogic Middleware Administration Server

Cause: Unable to connect to Oracle WebLogic Middleware Administration Server.

Action: Make sure the Oracle Middleware Administration Server is up and hostname, port, user name and administration password are correct
Level: 1

Type: ERROR

Impact: Installation

INST-05217: Error in detecting machine platform or JVM bits.

Cause: Unable to detect machine platform or JVM bits.

Action: Make sure machine platform and JVM are supported.
Level: 1

Type: ERROR

Impact: Installation

INST-05218: Cannot install or configure IDM on a 32-bit JVM on a 64-bit machine.

Cause: Unable to install or configure IDM on a 32-bit JVM on a 64-bit machine.

Action: Make sure to install and configure IDM in supported modes.
Level: 1

Type: ERROR

Impact: Installation

INST-05219: Error in providing OID with compatible version.

Cause: OID version is incompatible.

Action: Provide OID with compatible version.
Level: 1

Type: ERROR

Impact: Installation

INST-05223: Error in validating Domain.

Cause: Specified domain is not a valid IDM Domain.

Action: Provide valid IDM domain details.
Level: 1

Type: ERROR

Impact: Installation

INST-07000: Error in validating {0} location

Cause: {0} location specified is null or contains invalid characters

Action: The directory name may only contain alphanumeric, underscore (_), hyphen (-) , or dot (.) characters, and it must begin with an alphanumeric character. Provide a different directory name.
Level: 1

Type: ERROR

Impact: Installation

INST-07001: Validation of {0} location failed. Null Value

Cause: Provide a valid value for {0} location.

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07002: Validation of {0} location failed. String is too long.

Cause: Specified {0} location: {1} is too long

Action: Change the path to a value that is less than or equal to 128 characters
Level: 1

Type: ERROR

Impact: Installation

INST-07003: Validation of {0} location failed. Not Absolute.

Cause: {0} location is not absolute path

Action: Provide an absolute path
Level: 1

Type: ERROR

Impact: Installation

INST-07004: Validation of {0} location failed. Invalid Characters.

Cause: {0} location contains one or more invalid characters

Action: The directory name may only contain alphanumeric, tilde (~), underscore (_), hyphen (-) , or dot (.) characters and cannot contain spaces. Provide a different directory name or replace directory names with the tilde shortened version.
Level: 1

Type: ERROR

Impact: Installation

INST-07005: Validation of {0} location failed. Directory already Exists.

Cause: Validation of {0} location failed. The location specified already exists and is a nonempty directory

Action: Provide an empty or nonexistent directory location
Level: 1

Type: ERROR

Impact: Installation

INST-07006: Validation of {0} location failed. No read/write permission.

Cause: Validation of {0} location failed. The location specified does not have read/write permissions

Action: Provide a location with read/write permission
Level: 1

Type: ERROR

Impact: Installation

INST-07007: Validation of {0} location failed. Directory exists as a file.

Cause: Validation of {0} location failed. The location specified already exists and is a file

Action: Provide an empty or nonexistent directory location
Level: 1

Type: ERROR

Impact: Installation

INST-07008: Validation of {0} location failed. No create permission.

Cause: Validation of {0} location failed. User does not have permission to create home/instance location

Action: Make sure that you have the required permission to create the directory
Level: 1

Type: ERROR

Impact: Installation

INST-07009: Error in validating {0} location

Cause: An unexpected error occurred while validating {0} location

Action: Enter a valid directory
Level: 1

Type: ERROR

Impact: Installation

INST-07010: Error in validating the Front End URL

Cause: Front End URL value is null or contains invalid characters

Action: Provide a valid URL in [http://host.domainname:port] format
Level: 1

Type: ERROR

Impact: Installation

INST-07011: Validation of Front End URL failed. Null Value

Cause: Provide a valid value for Front End URL

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07012: Validation of Front End URL failed. Invalid Protocol

Cause: Validation of Front End URL failed. The protocol entered is not valid

Action: Provide a valid protocol. The valid protocol list is {0}
Level: 1

Type: ERROR

Impact: Installation

INST-07013: Validation of Hostname failed. Invalid Host

Cause: The hostname entered is not valid

Action: Provide a valid hostname
Level: 1

Type: ERROR

Impact: Installation

INST-07014: Validation of port value failed. Invalid port

Cause: The port entered is not valid

Action: Provide a valid port number
Level: 1

Type: ERROR

Impact: Installation

INST-07015: Validation of Front End URL failed. Invalid format

Cause: Validation of Front End URL failed. The front end URL entered is not valid

Action: Provide a valid URL in [http://host.domainname:port] format
Level: 1

Type: ERROR

Impact: Installation

INST-07016: Error in validating the Front End URL

Cause: An unexpected error occurred while validating the Front End URL

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07017: Error in obtaining free space

Cause: Error in obtaining free space. Value for drive name contains invalid characters

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07018: Error in obtaining free space. Null Value

Cause: Error in obtaining free space. Value for drive name is null

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07019: Error in obtaining free space

Cause: An unexpected error occurred while calculating available free space

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07020: Error in obtaining default {0} location

Cause: An unexpected error occurred while obtaining default home location

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07021: Error in obtaining available Oracle homes

Cause: An unexpected error occurred while obtaining available Oracle homes

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07033: Error in validating the {0} field value

Cause: {0} field value is null or contains invalid characters.

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07034: Error in validating the {0} field value

Cause: Provide a value for the field {0}

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07035: Error in validating the {0} field value. Length less than minimum length

Cause: {0} has less than {1} characters

Action: Length should be at least {0} characters
Level: 1

Type: ERROR

Impact: Installation

INST-07036: Error in validating the {0} field value. Length greater than maximum length

Cause: {0} has more than {1} characters

Action: Length should not be greater than {0} characters
Level: 1

Type: ERROR

Impact: Installation

INST-07037: Error in validating the {0} field value. Invalid characters

Cause: {0} field value contains one or more invalid characters or the value is not in proper format.

Action: Enter valid characters
Level: 1

Type: ERROR

Impact: Installation

INST-07038: Error in validating the {0} field value. Invalid Start character

Cause: {0} field value contains one or more invalid start characters

Action: Enter valid start character
Level: 1

Type: ERROR

Impact: Installation

INST-07039: Error in validating the {0} field value

Cause: An unexpected error occurred while validating {0} field value

Action: Enter a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07040: Error in Password Check

Cause: Passwords entered were null or contained invalid characters

Action: Provide valid values
Level: 1

Type: ERROR

Impact: Installation

INST-07041: Error in Password Check

Cause: An unexpected error occurred while processing the handler

Action: Enter passwords that match
Level: 1

Type: ERROR

Impact: Installation

INST-07042: Error in Password Check. Password value null

Cause: Password value is null

Action: Enter a valid value for password
Level: 1

Type: ERROR

Impact: Installation

INST-07043: Error in Password Check. Confirm password value null.

Cause: Confirm Password value is null

Action: Enter a valid value for confirm password
Level: 1

Type: ERROR

Impact: Installation

INST-07044: Error in Password Check. Passwords do not match

Cause: Passwords entered do not match

Action: Enter identical passwords
Level: 1

Type: ERROR

Impact: Installation

INST-07045: Error in validating the {0} field value

Cause: An unexpected error occurred while validating {0} field value

Action: Enter a valid number
Level: 1

Type: ERROR

Impact: Installation

INST-07046: Error in validating the {0} field value

Cause: Provide a valid value for {0}

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07047: Error in validating the {0} field value. Not a number

Cause: {0} field value is not a number

Action: Enter a valid number
Level: 1

Type: ERROR

Impact: Installation

INST-07048: Error in Validating {0} and {1}

Cause: Values specified are null or contain invalid characters

Action: Provide valid values
Level: 1

Type: ERROR

Impact: Installation

INST-07049: Error in Validating {0} and {1}

Cause: An unexpected error occurred while validating {0} and {1}

Action: Enter values that do not match
Level: 1

Type: ERROR

Impact: Installation

INST-07050: Error in Validating {0} and {1}. Null Value

Cause: Provide a valid value for {0}

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07051: Error in Validating {0} and {1}. Values do not match

Cause: {0} and {1} are different

Action: Enter same values
Level: 1

Type: ERROR

Impact: Installation

INST-07052: Error in Validating {0} and {1}. Values match

Cause: {0} and {1} are the same

Action: Enter different values
Level: 1

Type: ERROR

Impact: Installation

INST-07053: Error in validating the {0} field value

Cause: {0} field value is null or contains invalid characters

Action: Provide valid values
Level: 1

Type: ERROR

Impact: Installation

INST-07054: Error in validating the {0} field value

Cause: An unexpected error occurred while validating {0} field value

Action: Enter a valid host name
Level: 1

Type: ERROR

Impact: Installation

INST-07055: Error in validating the {0} field value. Host name value null

Cause: Provide a valid value for {0}

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07056: Error in validating the {0} field value. Invalid host name

Cause: {0} field value is not a valid host name

Action: Enter a valid value for host name
Level: 1

Type: ERROR

Impact: Installation

INST-07057: Error in validating the {0} field value. Host is not up and running

Cause: Error in validating the {0} field value. Entered host is not up and running

Action: Make sure that the host is up and running
Level: 1

Type: ERROR

Impact: Installation

INST-07058: Error in validating Oracle home location

Cause: An unexpected error occurred while validating Oracle home location

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07059: Error in validating Oracle home location

Cause: Oracle home location Specified is missing. Provide a valid Oracle home location

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07060: Error in validating Oracle home location

Cause: The Oracle home location specified is not a valid {0} home location

Action: Provide a valid {0} home location
Level: 1

Type: ERROR

Impact: Installation

INST-07061: Error in obtaining default port file location

Cause: An unexpected error occurred while obtaining default port file location

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07062: Error in connecting to the Database

Cause: An unexpected error occurred while trying to connect to the Database

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct. Enter a valid user name with DBA privileges
Level: 1

Type: ERROR

Impact: Installation

INST-07063: Error in connecting to the Database. Connect String is missing

Cause: Connect string is missing

Action: Provide a valid value for Connection String
Level: 1

Type: ERROR

Impact: Installation

INST-07064: Error in connecting to the Database

Cause: Unable to connect to the Database with the given credentials

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct. Enter a valid user name with DBA privileges
Level: 1

Type: ERROR

Impact: Installation

INST-07065: Error in validating Database details

Cause: An unexpected error occurred while trying to connect to the Database

Action: Try again and check the values. Make sure the Database is up and running and connect string, user name and password are correct. Enter a valid user name with DBA privileges
Level: 1

Type: ERROR

Impact: Installation

INST-07066: Error in validating Database details. Schema Type is missing

Cause: Schema type is missing

Action: Provide a valid value for Schema Type
Level: 1

Type: ERROR

Impact: Installation

INST-07067: Error in validating Database details. Schema name is missing

Cause: Schema is missing

Action: Provide a valid value for Schema Name
Level: 1

Type: ERROR

Impact: Installation

INST-07068: Error in validating Database details. Invalid Schema

Cause: Specified {0} schema does not exist in the given Database

Action: Check the schema name and the Database credentials
Level: 1

Type: ERROR

Impact: Installation

INST-07069: Validation of {0} location failed. Existing Oracle home

Cause: Validation of {0} location failed. The location specified is an existing Oracle home

Action: Provide an empty or nonexistent directory location
Level: 1

Type: ERROR

Impact: Installation

INST-07072: Error in validating Oracle home location

Cause: The Oracle home location specified is an existing Oracle home

Action: Provide an empty or nonexistent directory location
Level: 1

Type: ERROR

Impact: Installation

INST-07073: Error in validating Oracle home location

Cause: The Oracle home location specified is not a valid {0} home location

Action: Provide an empty or nonexistent directory location or a valid {0} home location
Level: 1

Type: ERROR

Impact: Installation

INST-07074: Error in validating Database details. Null Value

Cause: User name is missing

Action: Provide a valid user name with DBA privileges
Level: 1

Type: ERROR

Impact: Installation

INST-07075: Error in validating Database details. Invalid user

Cause: User does not have DBA privileges

Action: Provide a user with DBA privileges
Level: 1

Type: ERROR

Impact: Installation

INST-07076: Error in validating Database details

Cause: An unexpected error occurred while trying to connect to the Database

Action: Try again and check the values. Make sure the Database is up and running and connect string, user name and password are correct. Enter a valid user name with DBA privileges
Level: 1

Type: ERROR

Impact: Installation

INST-07077: Error in validating Oracle home and Oracle Instance home

Cause: Oracle home is inside the Oracle Instance home

Action: Enter a different location
Level: 1

Type: ERROR

Impact: Installation

INST-07078: Error in validating LDAP credentials

Cause: An unexpected error occurred while validating LDAP credentials

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07079: Error in validating LDAP credentials

Cause: Could not connect to LDAP with the given credentials.

Action: Verify the credentials. Make sure that hostname, port and password are correct
Level: 1

Type: ERROR

Impact: Installation

INST-07080: Error in validating available disk space

Cause: Space required is missing or not a valid value

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07081: Error in validating available disk space

Cause: Insufficient space to install the selected components

Action: Specify a different Oracle home or increase disk space.
Level: 1

Type: ERROR

Impact: Installation

INST-07082: Error in validating available disk space

Cause: An unexpected error occurred while validating available disk space

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07083: Error in validating port file

Cause: Specified port file location is missing

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07084: Error in validating port file

Cause: Specified port file is invalid

Action: Specify a valid file
Level: 1

Type: ERROR

Impact: Installation

INST-07085: Error in validating port file

Cause: Specified port file does not exist

Action: Specify a valid file
Level: 1

Type: ERROR

Impact: Installation

INST-07086: Error in validating port file

Cause: An unexpected error occurred while parsing the port file

Action: Verify the file. Check if the values are provided in the proper format. There should be at least one section in the file.
Level: 1

Type: ERROR

Impact: Installation

INST-07087: Error in validating port file

Cause: An unexpected error occurred while validating port file

Action: Provide a valid value. Check if the values are provided in the proper format. There should be at least one section in the file.
Level: 1

Type: ERROR

Impact: Installation

INST-07093: Error in validating port file

Cause: Keys {0} does not have proper values

Action: Provide valid values. Ensure that the port is free, valid and it is not used by any other Oracle home
Level: 1

Type: ERROR

Impact: Installation

INST-07094: Error in validating port file

Cause: Ports {0} are not free or not valid

Action: Ensure that the port is free, valid and it is not used by any other Oracle home. If ports are specified using a file, check if proper values are given for key.
Level: 1

Type: ERROR

Impact: Installation

INST-07095: Error in validating port file

Cause: Key {0} does not have proper value

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07096: Required component not found in Oracle home

Cause: One or more of the required components required for the install options selected may be missing from the Oracle home

Action: Specify a valid Oracle home with all required Components
Level: 1

Type: ERROR

Impact: Installation

INST-07097: Error in validating component name

Cause: Component name specified is not correct

Action: Provide a valid component name
Level: 1

Type: ERROR

Impact: Installation

INST-07098: Error in validating Oracle home location

Cause: Component {0} is not available in the Oracle home but selected for configuration.

Action: Deselect the above component for configuration
Level: 1

Type: ERROR

Impact: Installation

INST-07099: Error in validating Oracle home location

Cause: Components {0} are not available in the Oracle home but selected for configuration.

Action: Deselect the above components for configuration
Level: 1

Type: ERROR

Impact: Installation

INST-07100: Error in validating port file

Cause: Port {0} is duplicated

Action: Provide different ports
Level: 1

Type: ERROR

Impact: Installation

INST-07101: Error in validating port file

Cause: Ports {0} are duplicated

Action: Provide different ports
Level: 1

Type: ERROR

Impact: Installation

INST-07102: Error in validating port file

Cause: Port {0} is already used by existing Oracle homes

Action: Provide a port which is valid and free
Level: 1

Type: ERROR

Impact: Installation

INST-07103: Error in validating port file

Cause: Ports {0} are already used by existing Oracle homes

Action: Provide port values which are valid and free
Level: 1

Type: ERROR

Impact: Installation

INST-07104: Error in validating port file

Cause: Key {0} should not be specified as a range

Action: Provide a single port which is valid and free
Level: 1

Type: ERROR

Impact: Installation

INST-07105: Error in validating port file

Cause: Key {0} should not be specified as a range

Action: Provide single port values which are valid and free
Level: 1

Type: ERROR

Impact: Installation

INST-07106: Error in validating port file

Cause: Port {0} is not free or not valid

Action: Ensure that the port ( a number between 0 - 65535 ) is free and it is not used by any other Oracle home. If ports are specified using a file, check if proper values are given for key
Level: 1

Type: ERROR

Impact: Installation

INST-07107: Error in validating port value

Cause: An unexpected error occurred while validating port value

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07108: Error in validating components selected for configuration

Cause: An unexpected error occurred while processing the handler

Action: Select valid components
Level: 1

Type: ERROR

Impact: Installation

INST-07109: Error in validating components selected for configuration

Cause: At least one component should be selected for configuration

Action: Select at least one component for configuration
Level: 1

Type: ERROR

Impact: Installation

INST-07110: Error in validating Database details

Cause: Unable to connect to the Database with the given credentials. Invalid service id

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct. Enter a valid user name with DBA privileges
Level: 1

Type: ERROR

Impact: Installation

INST-07111: Error in validating Database details

Cause: Unable to connect to the Database with the given credentials. Invalid service name

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct. Enter a valid user name with DBA privileges
Level: 1

Type: ERROR

Impact: Installation

INST-07112: Error in obtaining schema details

Cause: An unexpected error occurred while trying to get schema details

Action: Try executing again and check the values. Make sure the Database is up and running and connect string, user name and password are correct. Enter a valid user name with DBA privileges
Level: 1

Type: ERROR

Impact: Installation

INST-07113: Error in obtaining schema details

Cause: Error in validating schema details. Could not fetch schema details from database

Action: Try executing again and check the values. Make sure the Database is up and running and connect string, user name and password are correct. Enter a valid user name with DBA privileges
Level: 1

Type: ERROR

Impact: Installation

INST-07114: Error in obtaining schema details

Cause: Error in validating schema details. Schema Registry table does not exist

Action: Provide a Database which has schemas loaded
Level: 1

Type: ERROR

Impact: Installation

INST-07115: Error in validating {0} schema details

Cause: An unexpected error occurred while validating {0} schema details

Action: Try again and check the values. Make sure the Database is up and running and connect string, user name and password are correct. Enter a valid user name with DBA privileges
Level: 1

Type: ERROR

Impact: Installation

INST-07119: Error in validating Database details

Cause: Unable to connect to the Database with the given credentials. Listener could be down

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct. Enter a valid user name with DBA privileges
Level: 1

Type: ERROR

Impact: Installation

INST-07120: Error in validating Database details

Cause: Unable to connect to the Database with the given credentials. Invalid user name/password

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct. Enter a valid user name with DBA privileges
Level: 1

Type: ERROR

Impact: Installation

INST-07121: Error in validating Database details

Cause: Unable to connect to the Database with the given credentials. User is not a SYSDBA

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct. Enter a valid user name with DBA privileges
Level: 1

Type: ERROR

Impact: Installation

INST-07122: Error in validating Database details

Cause: Unable to connect to the Database with the given credentials. Database could be down

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct. Enter a valid user name with DBA privileges
Level: 1

Type: ERROR

Impact: Installation

INST-07123: Error in validating port file

Cause: Specified file is empty or does not contain valid entries

Action: Provide a valid file
Level: 1

Type: ERROR

Impact: Installation

INST-07124: Error in validating Oracle home location

Cause: Component {0} is not available in the Oracle home but selected for installation.

Action: Deselect the above component
Level: 1

Type: ERROR

Impact: Installation

INST-07125: Error in validating Oracle home location

Cause: Components {0} are not available in the Oracle home but selected for installation.

Action: Deselect the above components
Level: 1

Type: ERROR

Impact: Installation

INST-07132: Error in validating jpsRootDN value

Cause: User(s) {0} are not present in the specified LDAP

Action: Users "fmwadmin" and "systemuser" must be present. The user must also have privileges to create users and groups
Level: 1

Type: ERROR

Impact: Installation

INST-07133: Error in obtaining LDAP bindpass

Cause: User {0} does not have permission to create {1}

Action: Users "fmwadmin" and "systemuser" must be present. The user must also have privileges to create users and groups
Level: 1

Type: ERROR

Impact: Installation

INST-07134: Error in validating Oracle Configuration Manager Service credentials

Cause: Customer Identification Number is missing or invalid

Action: Provide a valid value for Customer Identification Number
Level: 1

Type: ERROR

Impact: Installation

INST-07135: Error in validating Oracle Configuration Manager Service credentials

Cause:

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07136: Error in validating Oracle Configuration Manager Service credentials

Cause: Country Code value is incorrect

Action: Provide a valid value for Country Code
Level: 1

Type: ERROR

Impact: Installation

INST-07137: Error in validating Oracle Configuration Manager Service credentials

Cause: Could not connect Oracle Configuration Manager Service with the specified credentials

Action: Verify the values. Make sure the Customer Identification Number, My Oracle Support User Name and the Country code are correct
Level: 1

Type: ERROR

Impact: Installation

INST-07138: Error in validating Oracle Configuration Manager Service credentials

Cause: An unexpected error occurred while validating the Oracle Configuration Manager Service credentials

Action: Verify the values and try again
Level: 1

Type: ERROR

Impact: Installation

INST-07139: Error in validating Oracle Configuration Manager Service credentials

Cause: Provide a valid value for Customer Identification Number

Action: CSI number must contain numeric characters only
Level: 1

Type: ERROR

Impact: Installation

INST-07144: Error in validating LDAP Credentials

Cause: Specified LDAP Type ( {0} ) is not valid

Action: Valid values are "{0}". Enter a valid LDAP Type
Level: 1

Type: ERROR

Impact: Installation

INST-07150: Error in validating jpsRootDN value

Cause: Specified JPS Root DN value is not valid

Action: Provide a valid value. Make sure that the root DN provided is an empty container.
Level: 1

Type: ERROR

Impact: Installation

INST-07151: Error in validating jpsRootDN value

Cause: Provide a valid value for JPS Root DN

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07152: Error in obtaining LDAP Host

Cause: An unexpected error occurred while processing the handler

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07153: Error in obtaining LDAP Port

Cause: An unexpected error occurred while processing the handler

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07154: Error in obtaining LDAP binddn

Cause: An unexpected error occurred while processing the handler

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07155: Error in obtaining LDAP bindpass

Cause: An unexpected error occurred while processing the handler

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07156: Error in validating URL

Cause: Provide a valid value the URL

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07157: Error in validating URL

Cause: URL {0} is not valid

Action: Provide a valid URL in [hostname.domainname:port] format and make sure the given URL is accessible
Level: 1

Type: ERROR

Impact: Installation

INST-07158: Error in validating URL

Cause: URL {0} is not accessible.

Action: Provide a valid URL which is accessible.
Level: 1

Type: ERROR

Impact: Installation

INST-07159: Error in validating URL

Cause: An unexpected error occurred while validating the URL

Action: Verify the values and try again
Level: 1

Type: ERROR

Impact: Installation

INST-07169: Error in validating port file

Cause: Port range {0} is not valid. Start range is greater than end range

Action: Provide a valid port range
Level: 1

Type: ERROR

Impact: Installation

INST-07172: Error in validating port file

Cause: Key {0} is missing in the section [{1}]

Action: Provide a value for the key
Level: 1

Type: ERROR

Impact: Installation

INST-07173: Error in validating port file

Cause: Keys {0} are missing in the section [{1}]

Action: Provide valid value for the keys
Level: 1

Type: ERROR

Impact: Installation

INST-07174: Error in validating port file

Cause: Key {0} is not valid in the section [{1}]

Action: Valid keys for section [{0}] are {1}
Level: 1

Type: ERROR

Impact: Installation

INST-07175: Error in validating port file

Cause: Keys {0} were not valid in the section [{1}]

Action: Valid keys for section [{0}] are {1}
Level: 1

Type: ERROR

Impact: Installation

INST-07176: Error in validating port file

Cause: Key {0} is duplicated

Action: Remove duplicate entries
Level: 1

Type: ERROR

Impact: Installation

INST-07177: Error in validating port file

Cause: Keys {0} are duplicated

Action: Remove duplicate entries
Level: 1

Type: ERROR

Impact: Installation

INST-07179: Error in validating port file

Cause: Port range {0} are not valid. Start range is greater than end range

Action: Provide a valid port range
Level: 1

Type: ERROR

Impact: Installation

INST-07180: Error in validating port file

Cause: Specified Port range {0} does not have free port.

Action: Provide a different range. Check if the same range is mentioned more than once in the file.
Level: 1

Type: ERROR

Impact: Installation

INST-07181: Error while obtaining registry key value

Cause: An error occurred while obtaining a registry key value

Action: Provide a valid value for Registry Key
Level: 1

Type: ERROR

Impact: Installation

INST-07182: Error while obtaining registry key value

Cause: An error occurred while obtaining a registry key value

Action: Provide a valid value for Registry Sub Key
Level: 1

Type: ERROR

Impact: Installation

INST-07183: Error while obtaining registry key value

Cause: An error occurred while obtaining a registry key value

Action: Provide a valid value for Registry Property Name
Level: 1

Type: ERROR

Impact: Installation

INST-07184: Error while obtaining registry key value

Cause: An unexpected error occurred while obtaining registry key value

Action: Verify the values and try again
Level: 1

Type: ERROR

Impact: Installation

INST-07185: Error in validating proxy credentials

Cause: Provide a valid value for Proxy Server

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07186: Error in validating proxy credentials

Cause: Provide a valid value for Proxy Port

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07187: Error in validating proxy credentials

Cause: Specified Proxy port is not a valid value

Action: Provide a valid number for Proxy Port
Level: 1

Type: ERROR

Impact: Installation

INST-07188: Error in validating proxy credentials

Cause: Could not establish connection to the specified proxy credentials

Action: Verify the values. Make sure the proxy server, proxy port values are correct
Level: 1

Type: ERROR

Impact: Installation

INST-07189: Error in validating proxy credentials

Cause: An unexpected error occurred while obtaining registry key value

Action: Verify the values and try again
Level: 1

Type: ERROR

Impact: Installation

INST-07202: Error in validating container name

Cause: Provide a valid value for container name

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07203: Error in validating container name

Cause: Specified value is a reserved key word.

Action: Provide value other than {0}
Level: 1

Type: ERROR

Impact: Installation

INST-07204: Error in validating container name

Cause: An unexpected error occurred while validating the URL

Action: Verify the values and try again
Level: 1

Type: ERROR

Impact: Installation

INST-07205: Error in validating port file

Cause: Port {0} is duplicated for keys {1}

Action: Provide different ports
Level: 1

Type: ERROR

Impact: Installation

INST-07206: Error in validating port file

Cause: Port {0} (JMX Port No + 1 ) is not free

Action: JMX Port No + 1 will be used as Java Object Cache Local Port No. Specify a value for Java Object Cache Local Port No key or provide a JMX Port No which has also (JMX Port No + 1 ) free
Level: 1

Type: ERROR

Impact: Installation

INST-07207: Error in validating port file

Cause: Port {0} (JMX Port No + 2 ) is not free

Action: JMX Port No + 2 will be used as Java Object Cache Remote Port No. Specify a value for Java Object Cache Remote Port No key or provide a JMX Port No which has also (JMX Port No + 2 ) free
Level: 1

Type: ERROR

Impact: Installation

INST-07208: Error in validating port file

Cause: Reserved ports are not allowed under section [{0}]. Key(s) {1} have Operating System reserved port entries.

Action: Provide different port(s)
Level: 1

Type: ERROR

Impact: Installation

INST-07210: Error in obtaining 10g SSO information

Cause: An unexpected error occurred while obtaining 10g SSO information

Action: Verify the LDAP credentials. Make sure that hostname, port, binddn, password are correct
Level: 1

Type: ERROR

Impact: Installation

INST-07211: Error in obtaining Oracle Internet Directory version

Cause: An unexpected error occurred while processing the handler

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07212: Error in checking the version of Oracle Internet Directory

Cause: Version of the given Oracle Internet Directory is not {0}

Action: Provide an alternate Oracle Internet Directory location
Level: 1

Type: ERROR

Impact: Installation

INST-07213: Error in checking the version of Oracle Internet Directory

Cause: An unexpected error occurred while checking the version of Oracle Internet Directory

Action: Verify the LDAP credentials. Make sure that hostname, port, binddn, password are correct
Level: 1

Type: ERROR

Impact: Installation

INST-07214: Error in validating URL

Cause: Specified URL is not valid

Action: Provide a valid value for the URL
Level: 1

Type: ERROR

Impact: Installation

INST-07215: Error in validating URL

Cause: Specified URL is not correct format

Action: Provide a valid URL
Level: 1

Type: ERROR

Impact: Installation

INST-07216: Error in validating URL

Cause: Specified URL is not accessible

Action: Provide a valid URL
Level: 1

Type: ERROR

Impact: Installation

INST-07217: Error in validating URL

Cause: Specified URL is not accessible

Action: Provide a valid URL
Level: 1

Type: ERROR

Impact: Installation

INST-07221: Error in validating database details

Cause: Specified connect string is not in a valid format

Action: Provide the value in the following format. Format: hostname:port:servicename , For Real Application Cluster Database hostname1:port1^hostname2:port2@servicename
Level: 1

Type: ERROR

Impact: Installation

INST-07222: Error in validating database details

Cause: Specified connect string is not in a valid format

Action: Provide the value in the following format. Format: hostname:port:sid , For a Real Application Cluster Database, use hostname1:port1^hostname2:port2@servicename
Level: 1

Type: ERROR

Impact: Installation

INST-07223: Error in obtaining work repository details

Cause: Work repository table does not exist

Action: Provide a Database which has repositories loaded
Level: 1

Type: ERROR

Impact: Installation

INST-07224: Error in obtaining work repository details

Cause: Error in obtaining work repository details. Could not fetch repository details from database

Action: Try executing again and check the values. Make sure the Database is up and running and connect string, user name and password are correct.
Level: 1

Type: ERROR

Impact: Installation

INST-07225: Error in validating work repository details

Cause: An unexpected error occurred while validating work repository details

Action: Try again and check the values. Make sure the Database is up and running and connect string, user name and password are correct.
Level: 1

Type: ERROR

Impact: Installation

INST-07226: Error in validating Database details. Invalid Work Repository

Cause: Specified {0} repository does not exist in the given Database

Action: Check the {0} repository name and the Database credentials
Level: 1

Type: ERROR

Impact: Installation

INST-07227: Error in validating work repository details

Cause: Provide a valid {0} repository name

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07228: Error in connecting to the Database

Cause: Unable to connect to the Database with the given credentials

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct.
Level: 1

Type: ERROR

Impact: Installation

INST-07229: Error in validating Database details

Cause: Unable to connect to the Database with the given credentials. Listener could be down

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct
Level: 1

Type: ERROR

Impact: Installation

INST-07230: Error in validating Database details

Cause: Unable to connect to the Database with the given credentials. Invalid user name/password

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct
Level: 1

Type: ERROR

Impact: Installation

INST-07231: Error in validating Database details

Cause: Unable to connect to the Database with the given credentials. User is not a SYSDBA

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct
Level: 1

Type: ERROR

Impact: Installation

INST-07232: Error in validating Database details

Cause: Unable to connect to the Database with the given credentials. Database could be down

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct
Level: 1

Type: ERROR

Impact: Installation

INST-07233: Error in validating Database details

Cause: Unable to connect to the Database with the given credentials. Invalid service id

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct
Level: 1

Type: ERROR

Impact: Installation

INST-07234: Error in validating Database details

Cause: Unable to connect to the Database with the given credentials. Invalid service name

Action: Check the values. Make sure the Database is up and running and connect string, user name and password are correct
Level: 1

Type: ERROR

Impact: Installation

INST-07235: Error in validating the {0} field value

Cause: Please enter the {0} field value in the range {1} - {2}

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07236: Error in validating the agent name

Cause: Provide a valid value for the agent name

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07237: Error in validating the agent name

Cause: Agent name already exists. Provide a different value

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07238: Error in validating the agent name

Cause: Unable to verify the agent name

Action: Verify the values. Make sure the Master Database is up and running and connect string, user name, password, ODI supervisor username and ODI supervisor password are correct.
Level: 1

Type: ERROR

Impact: Installation

INST-07239: Error in validating Database details. Invalid Schema

Cause: Not able to connect to the specified {0} Schema

Action: Check the schema name and the Database credentials
Level: 1

Type: ERROR

Impact: Installation

INST-07240: Error in obtaining {0}components from Oracle WebLogic Administration Server.

Cause: Error in obtaining {0}components from Oracle WebLogic Administration Server.

Action: Check the given credentials. Make sure the Oracle WebLogic Administration Server is up and hostname, port, user name and administration password are correct.
Level: 1

Type: ERROR

Impact: Installation

INST-07241: Error in obtaining connection with Oracle WebLogic Administration Server

Cause: Unable to connect to Oracle WebLogic Administration Server. Credentials entered are null or contains invalid characters

Action: Make sure the Middleware Administration Server is up and hostname, port, user name and administration password are correct
Level: 1

Type: ERROR

Impact: Installation

INST-07242: Error in obtaining connection with Oracle WebLogic Administration Server

Cause: Unable to connect to Oracle WebLogic Administration Server.

Action: Make sure the Oracle Middleware Administration Server is up and hostname, port, user name and administration password are correct
Level: 1

Type: ERROR

Impact: Installation

INST-07243: Unable to connect to Oracle WebLogic Administration Server. Hostname is missing.

Cause: Unable to connect to Oracle WebLogic Administration Server. Hostname is missing.

Action: Enter a valid hostname
Level: 1

Type: ERROR

Impact: Installation

INST-07244: Unable to connect to Oracle WebLogic Administration Server. Port number is missing.

Cause: Unable to connect to Oracle WebLogic Administration Server. Port number is missing.

Action: Enter a valid port
Level: 1

Type: ERROR

Impact: Installation

INST-07245: Unable to connect Oracle WebLogic Administration Server. Admin User name is missing.

Cause: Unable to connect Oracle WebLogic Administration Server. Admin User name is missing.

Action: Enter a valid admin user name
Level: 1

Type: ERROR

Impact: Installation

INST-07246: Error in validating {0} home location

Cause: Enter a valid value for {0} home location

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07247: Error in validating {0} home location

Cause: Specified {0} home location is either not valid or missing

Action: Enter a valid {0} home location
Level: 1

Type: ERROR

Impact: Installation

INST-07248: Error in validating {0} home location

Cause: Specified {0} home location is not a valid location

Action: Enter a valid {0} home location
Level: 1

Type: ERROR

Impact: Installation

INST-07249: Error in validating {0} home location

Cause: An unexpected error occurred during the validation of {0} home location

Action: Check the values
Level: 1

Type: ERROR

Impact: Installation

INST-07250: Error in validating Middleware home and WebLogic home

Cause: Specified WebLogic home is not associated with the given Middleware home

Action: Enter a WebLogic home which is associated with the specified Oracle Middleware home
Level: 1

Type: ERROR

Impact: Installation

INST-07251: Error in validating Middleware home and WebLogic home

Cause: An unexpected error occurred during the validation of Oracle Middleware home and WebLogic home

Action: Check the values
Level: 1

Type: ERROR

Impact: Installation

INST-07252: Error while obtaining default Middleware home and WebLogic home directories

Cause: An unexpected error occurred while obtaining default Oracle Middleware home and WebLogic home directories

Action: Check the values
Level: 1

Type: ERROR

Impact: Installation

INST-07253: Error in validating instance name

Cause: Specified instance name is not a valid instance name

Action: Enter a valid instance name associated with the specified instance home
Level: 1

Type: ERROR

Impact: Installation

INST-07254: Error in validating instance name

Cause: An unexpected error occurred during the validation of instance name

Action: Check the values
Level: 1

Type: ERROR

Impact: Installation

INST-07255: Error in validating instance name

Cause: instance name is incorrect

Action: Enter a valid value for instance name
Level: 1

Type: ERROR

Impact: Installation

INST-07256: Error in validating {0} component name

Cause: Component type failed validation

Action: Enter a valid value for {0} component name
Level: 1

Type: ERROR

Impact: Installation

INST-07257: Error in validating component type

Cause: Component type failed validation

Action: Enter a valid value for component type
Level: 1

Type: ERROR

Impact: Installation

INST-07258: Error in validating component name

Cause: An unexpected error occurred during the validation of component name

Action: Verify the instance home location
Level: 1

Type: ERROR

Impact: Installation

INST-07259: Error in validating {0} component name

Cause: Specified value for {0} component name already exists

Action: Provide a different value
Level: 1

Type: ERROR

Impact: Installation

INST-07260: Error in validating {0} component name

Cause: Specified value for {0} component name is not valid. A directory with the same name already exists under INST_HOME/config/{0}

Action: Provide a different value
Level: 1

Type: ERROR

Impact: Installation

INST-07261: Error in validating component name

Cause: Specified component name is not a valid component name

Action: Enter a valid component name associated with the specified instance
Level: 1

Type: ERROR

Impact: Installation

INST-07262: Error in validating instance details in the domain

Cause: Specified instance details are not valid

Action: Enter a valid instance name available in the domain. Make sure the instance home entered is in conjunction with the instance name.
Level: 1

Type: ERROR

Impact: Installation

INST-07263: Error in validating instance name

Cause: Specified instance name is not valid

Action: Enter a valid instance name available in the domain.
Level: 1

Type: ERROR

Impact: Installation

INST-07264: Error in validating instance details in the domain

Cause: An unexpected error occurred during the validation of instance details

Action: Check the values. Verify the instance name and instance home location
Level: 1

Type: ERROR

Impact: Installation

INST-07265: Error in validating instance name

Cause: An unexpected error occurred during the validation of instance name

Action: Check the values. Verify the instance name
Level: 1

Type: ERROR

Impact: Installation

INST-07266: Error in validating component name in the domain

Cause: Specified {0} component name already exists in the domain

Action: Provide a different value
Level: 1

Type: ERROR

Impact: Installation

INST-07267: Error in validating component name in the domain

Cause: An unexpected error occurred during the validation of component name

Action: Check the values. Verify the component name
Level: 1

Type: ERROR

Impact: Installation

INST-07268: Error in validating component name in the domain

Cause: Specified {0} component name does not exist in the domain

Action: Enter an existing component name
Level: 1

Type: ERROR

Impact: Installation

INST-07269: Error while obtaining default values for instance name and instance location

Cause: An unexpected error occurred while obtaining default values for instance name and instance location

Action: Check the values and try again
Level: 1

Type: ERROR

Impact: Installation

INST-07270: Error in validating instance name in the domain

Cause: Specified instance name already exists in the domain

Action: Provide a different value
Level: 1

Type: ERROR

Impact: Installation

INST-07271: Error in validating instance name in the domain

Cause: An unexpected error occurred during the validation of instance name

Action: Check the values. Verify the instance name
Level: 1

Type: ERROR

Impact: Installation

INST-07272: Error while obtaining the component names from the instance home

Cause: An unexpected error occurred while obtaining the component names from the instance home

Action: Check the values. Verify the instance home location
Level: 1

Type: ERROR

Impact: Installation

INST-07273: Error while obtaining the component names of a given component type from the instance home

Cause: An unexpected error occurred while obtaining the component names of a given component type from the instance home

Action: Check the values. Verify the instance home location
Level: 1

Type: ERROR

Impact: Installation

INST-07274: Error in validating port value

Cause: Port {0} is not valid. Privileged ports are not allowed

Action: Provide a different value
Level: 1

Type: ERROR

Impact: Installation

INST-07275: Error in validating {0} home location

Cause: Specified {0} home location does not have read/write permissions

Action: Provide read/write permissions for the {0} home location
Level: 1

Type: ERROR

Impact: Installation

INST-07276: Error in validating {0} home location

Cause: Enter a valid value for {0} home location

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07277: Error in validating {0} name

Cause: Specified {0} name is either not valid or the location is not empty

Action: Enter a valid {0} name or ensure that the {0} directory is empty
Level: 1

Type: ERROR

Impact: Installation

INST-07278: Error in validating {0} home location

Cause: Specified {0} home location does not have Read/Write permissions

Action: Provide Read/Write permissions for the specified {0} home location
Level: 1

Type: ERROR

Impact: Installation

INST-07279: Error in validating {0} home location

Cause: An unexpected error occurred during the validation of {0} home location

Action: Check the values
Level: 1

Type: ERROR

Impact: Installation

INST-07280: Error in validating domain credentials

Cause:

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07281: Error in validating domain credentials

Cause: {0} is not set up in the specified domain

Action: Enter a domain which has {0} set up
Level: 1

Type: ERROR

Impact: Installation

INST-07282: Error in validating {0} home location

Cause: Specified {0} home location does not exist

Action: Provide an existing {0} home location
Level: 1

Type: ERROR

Impact: Installation

INST-07283: Error in validating My Oracle Support Details

Cause: Specified My Oracle Support Details are not proper

Action: Enter valid values
Level: 1

Type: ERROR

Impact: Installation

INST-07284: Error in validating My Oracle Support Details

Cause: An unexpected error occurred while validating My Oracle Support Details

Action: Check the values
Level: 1

Type: ERROR

Impact: Installation

INST-07285: Error in validating Database details. Invalid Schema

Cause: The schema name {0} and schema type {1} do not match

Action: Provide a valid schema name for {1}
Level: 1

Type: ERROR

Impact: Installation

INST-07286: Error in validating Middleware home location

Cause: Specified Oracle Middleware home location does not have minimum version {0} of WebLogic server. If the version is incorrect then configuring with the Weblogic server will fail.

Action: Provide a Oracle Middleware home location which contains WebLogic server with minimum version {0} or upgrade the Weblogic server to {0} or higher version and restart the install.
Level: 1

Type: ERROR

Impact: Installation

INST-07287: Error in obtaining connection with Oracle WebLogic Administration Server

Cause: Unable to connect to Oracle WebLogic Administration Server. Server is not running.

Action: Make sure the Middleware Administration Server is up
Level: 1

Type: ERROR

Impact: Installation

INST-07288: Error in obtaining connection with Oracle WebLogic Administration Server

Cause: Unable to connect to Oracle WebLogic Administration Server. Invalid username/password

Action: Enter a valid username and password
Level: 1

Type: ERROR

Impact: Installation

INST-07289: Error in validating WebLogic Server Directory

Cause: Specified WebLogic Server Directory is either not valid or empty

Action: Enter a valid WebLogic Server Directory
Level: 1

Type: ERROR

Impact: Installation

INST-07290: Error in validating Oracle home location

Cause: Specified Middleware home already has a {0} home. Only one {0} home location can reside under a Middleware home.

Action: Provide a different Middleware home location
Level: 1

Type: ERROR

Impact: Installation

INST-07291: Error in validating Oracle home location

Cause: Top Component name specified is null.

Action: Provide a valid component name
Level: 1

Type: ERROR

Impact: Installation

INST-07292: Error in validating Middleware home location

Cause: Middleware home location specified is not a valid location. Provide a valid Middleware home location

Action: Provide a valid Middleware home location.
Level: 1

Type: ERROR

Impact: Installation

INST-07293: Error in validating SSO credentials

Cause: Given OID does not have a proper SSO.

Action: Provide an OID with a 10g SSO.
Level: 1

Type: ERROR

Impact: Installation

INST-07294: Error in validating SSO credentials

Cause: Could not retrieve SSO information with the given credentials.

Action: Verify the credentials. Make sure that hostname, port and password are correct
Level: 1

Type: ERROR

Impact: Installation

INST-07295: Error in validating UCM Installer Location

Cause: Specified UCM Installer Location is not valid

Action: Provide a valid value for UCM Installer Location.
Level: 1

Type: ERROR

Impact: Installation

INST-07296: Error in validating UCM Installer Location

Cause: An unexpected error occurred while processing the handler

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07297: Error in validating Web Server HTTP Address

Cause: Webserver HTTP Address is missing

Action: Provide a valid value for Webserver HTTP Address
Level: 1

Type: ERROR

Impact: Installation

INST-07298: Error in validating Web Server HTTP Address

Cause: Specified Web Server HTTP Address is not valid

Action: The Web Server HTTP Address has to be in http(s)://[host]:[port]?/[webroot] format
Level: 1

Type: ERROR

Impact: Installation

INST-07299: Error in validating Web Server HTTP Address

Cause: An unexpected error occurred while processing the handler

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07300: Error in validating UCM Installer Location

Cause: UCM Installer Location is missing

Action: Provide a valid value for UCM Installer Location
Level: 1

Type: ERROR

Impact: Installation

INST-07301: Error in validating UCM Installer Location

Cause: Specified UCM Installer Location is empty

Action: Provide a valid value for UCM Installer Location.
Level: 1

Type: ERROR

Impact: Installation

INST-07302: Error in validating Domain

Cause: Specified domain cannot be used for Expand Cluster configuration

Action: Specify a domain which has clusters
Level: 1

Type: ERROR

Impact: Installation

INST-07303: Error in validating Domain

Cause: Specified domain cannot be used for Extend Domain configuration

Action: Specify a domain which has at least one component not configured
Level: 1

Type: ERROR

Impact: Installation

INST-07304: Validation of User Name failed. Invalid User Name

Cause: The user name entered is not valid

Action: Provide a valid user name
Level: 1

Type: ERROR

Impact: Installation

INST-07305: Validation of password value failed. Invalid password

Cause: The password entered is not valid

Action: Provide a valid password
Level: 1

Type: ERROR

Impact: Installation

INST-07306: Error in validating Database details. RAC Dabase is not supported

Cause: RAC Database is not supported for {0}

Action: {0}
Level: 1

Type: ERROR

Impact: Installation

INST-07307: Error in validating Oracle home location

Cause: Oracle home location specified is not inside Middleware home location. Provide a valid location for Oracle home.

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07308: Oracle Universal Content Management is already installed and configured at location {0}

Cause: Oracle Universal Content Management is already installed and configured at location {0}

Action: Either select not to configure again or uninstall Oracle Universal Content Management and then try to reconfigure
Level: 1

Type: ERROR

Impact: Installation

INST-07309: Error in validating master repository details

Cause: Specified Master Repository credentials are not valid.

Action: Verify the values. Make sure the Master Database is up and running and connect string, user name, password, ODI supervisor username and ODI supervisor password are correct.
Level: 1

Type: ERROR

Impact: Installation

INST-07310: Error in validating database details

Cause: Specified connect string is not in a valid format

Action: Provide the value in the following format. Format: hostname:port:servicename
Level: 1

Type: ERROR

Impact: Installation

INST-07311: Error in validating database details

Cause: Specified connect string is not in a valid format

Action: Provide the value in the following format. Format: hostname:port:sid
Level: 1

Type: ERROR

Impact: Installation

INST-07312: Error in validating database details

Cause: Specified connect string is not in a valid format

Action: Provide the value in the following format. Format: hostname:port:servicename , For Real Application Cluster Database hostname1:port1^hostname2:port2@servicename
Level: 1

Type: ERROR

Impact: Installation

INST-07313: Error in validating database details

Cause: Specified connect string is not in a valid format

Action: Provide the value in the following format. Format: hostname:port:sid , For a Real Application Cluster Database, use hostname1:port1^hostname2:port2@servicename
Level: 1

Type: ERROR

Impact: Installation

INST-07314: Error in validating port file

Cause: Port {0} is not valid

Action: Provide a valid port number ( a number between {0} )
Level: 1

Type: ERROR

Impact: Installation

INST-07315: Error in validating port value

Cause: An unexpected error occurred while validating port value

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07316: Error in validating port file

Cause: Port {0} is not free or not valid

Action: Ensure that the port ( a number between 1024 - 65535 ) is free and it is not used by any other Oracle home. If ports are specified using a file, check if proper values are given for key.
Level: 1

Type: ERROR

Impact: Installation

INST-07317: Validation of {0} location failed. Directory does not exist.

Cause: Validation of {0} location failed. The location specified does not exist.

Action: Enter a valid existing directory
Level: 1

Type: ERROR

Impact: Installation

INST-07318: Validation of {0} location failed. Directory s empty.

Cause: Validation of {0} location failed. The location specified is empty.

Action: Enter a nonempty directory
Level: 1

Type: ERROR

Impact: Installation

INST-07404: Error in validating Oracle home

Cause: Specified Oracle home value is null

Action: Specify the correct Oracle home name
Level: 1

Type: ERROR

Impact: Installation

INST-07405: Error in validating Oracle home

Cause: The specified Oracle home does not match with the Domain Oracle home

Action: Specify Oracle home name same as that of the Domain Oracle home
Level: 1

Type: ERROR

Impact: Installation

INST-07406: Error in validating {0} home location

Cause: Specified {0} home location is either not valid or is empty

Action: Enter a valid {0} home location
Level: 1

Type: ERROR

Impact: Installation

INST-07407: Error in detecting machine platform or JVM bits.

Cause: Unable to detect machine platform or JVM bits.

Action: Make sure machine platform and JVM are supported.
Level: 1

Type: ERROR

Impact: Installation

INST-07408: Cannot install or configure the product on a 32-bit JVM on a 64-bit machine.

Cause: Unable to install or configure the product on a 32-bit JVM on a 64-bit machine.

Action: Make sure to install and configure the product in supported modes.
Level: 1

Type: ERROR

Impact: Installation

INST-07409: Error in validating instance name

Cause: Unexpected error in validating instance name

Action: Make sure entered values are correct
Level: 1

Type: ERROR

Impact: Installation

INST-07410: Error in validating instance name

Cause: Specified instance name is not valid, a windows service with the specified instance name already exists

Action: Provide a different instance name
Level: 1

Type: ERROR

Impact: Installation

INST-07411: Error in validating oracle home

Cause: Provide valid value for Oracle Home Directory.

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07412: Error in validating oracle home

Cause: Oracle Home Directory name cannot be oracle_common.

Action: Provide a different value for Oracle Home Directory.
Level: 1

Type: ERROR

Impact: Installation

INST-07413: Error in validating oracle home

Cause: Unexpected error in validating Oracle Home Directory

Action: Make sure entered values are correct
Level: 1

Type: ERROR

Impact: Installation

INST-07414: Error in validating {0}

Cause: Specified {0} is not valid

Action: Provide a valid value {0}
Level: 1

Type: ERROR

Impact: Installation

INST-07415: Error in validating Home Type

Cause: Home Type Specified is not Correct

Action: Provide a valid a valid Home Type
Level: 1

Type: ERROR

Impact: Installation

INST-07416: Error in validating {0}

Cause: An unexpected error occurred while validating {0}

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07417: Error in validating the {0}

Cause: {0} has not been installed in the specified {1}. Provide a different Location

Action: Provide a different {0}
Level: 1

Type: ERROR

Impact: Installation

INST-07420: Error in validating oracle home

Cause: Oracle Home Directory name cannot be {0}.

Action: Provide a different value for Oracle Home Directory.
Level: 1

Type: ERROR

Impact: Installation

INST-07421: Error in executing the software update flow

Cause: An error occurred while validating the values for software updates

Action: Make sure entered values are correct
Level: 1

Type: ERROR

Impact: Installation

INST-07422: Error in validating library

Cause: The library {0} does not exists in the provided location

Action: Make sure the library {0} exists in the provided location
Level: 1

Type: ERROR

Impact: Installation

INST-07423: Error in validating library

Cause: The library {0} does not exists in the provided location

Action: Make sure the library {0} exists in the provided location
Level: 1

Type: ERROR

Impact: Installation

INST-07424: Error in validating library

Cause: The version of library at the provided location is not as expected

Action: Make sure the version of library at the provided location is correct
Level: 1

Type: ERROR

Impact: Installation

INST-07425: Error in verifying version of Application Server

Cause: Could not access versionInfo script under the Application Server Directory provided

Action: Make sure the the Application Server directory has versionInfo script under bin folder
Level: 1

Type: ERROR

Impact: Installation

INST-07426: Error in verifying version of Application Server

Cause: The version of Application Server is not valid

Action: Make sure the the version of Application Server is at least {0}
Level: 1

Type: ERROR

Impact: Installation

INST-07427: Error in verifying Application Server

Cause: The Application Server Directory does not refer to WebSphere Application Server

Action: Provide the directory location of WebSphere Application Server
Level: 1

Type: ERROR

Impact: Installation

INST-07428: Error in verifying version of Application Server

Cause: The version of Application Server is not supported

Action: The Application Server version detected is {0}. Please refer to the certification document and provide an Application Server Location corresponding to a certified version of the Application Server.
Level: 1

Type: ERROR

Impact: Installation

INST-07440: Error in validating Application Server Type

Cause: Validation of Application Server Type failed. Supported Application Server Types are WLS and WAS.

Action: Specify a valid Application Server Type. Supported Application Server Types are WLS and WAS.
Level: 1

Type: ERROR

Impact: Installation

INST-07441: Error in validating Application Server Type

Cause: Validation of Application Server Type failed. Specified Application Server Type does not match with the Application Server detected in the Middleware home.

Action: Specify a valid Application Server Type.
Level: 1

Type: ERROR

Impact: Installation

INST-07509: Error in validating master repository details

Cause: Specified Master Repository schema details are not valid.

Action: Verify the values. Make sure the Master Database schema version is correct and master repository is created with appropriate Repository Creation Utility.
Level: 1

Type: ERROR

Impact: Installation

INST-07519: {0} found in Oracle home

Cause: This Oracle home already contains a version of {0}.

Action: If you are updating an existing installation to the latest version, use the Install Software - Do Not Configure option on the Select Installation Type screen.
Level: 1

Type: ERROR

Impact: Installation

INST-07520: Error in validating {0} home location

Cause: Enter a valid value for {0} home location

Action:
Level: 1

Type: ERROR

Impact: Installation

INST-07521: Error in validating {0} home location

Cause: Specified {0} home location does not exist

Action: Provide an exisiting {0} home location
Level: 1

Type: ERROR

Impact: Installation

INST-07522: Error in validating {0} home location

Cause: Specified {0} home location does not have read/write permissions

Action: Provide read/write permissions for the {0} home location
Level: 1

Type: ERROR

Impact: Installation

INST-07523: Error in validating {0} home location

Cause: Specified {0} home location is either not valid or empty

Action: Enter a valid {0} home location
Level: 1

Type: ERROR

Impact: Installation

INST-07524: Error in validating {0} home location

Cause: Specified {0} home location is not a valid location

Action: Enter a valid {0} home location
Level: 1

Type: ERROR

Impact: Installation

INST-07525: Error in validating {0} home location

Cause: An unexpected error occurred during the validation of {0} home location

Action: Check the values
Level: 1

Type: ERROR

Impact: Installation

INST-07526: Error in validating {0} home location

Cause: Specified {0} home location is not a valid location

Action: Enter a valid {0} home location
Level: 1

Type: ERROR

Impact: Installation

INST-07527: Error in validating Middleware home location

Cause: Specified Oracle Middleware home location does not have appropriate version of WebLogic server

Action: Provide a Oracle Middleware home location which contains WebLogic server with a supported version
Level: 1

Type: ERROR

Impact: Installation

INST-07528: Validation of {0} location failed. Directory does not exist.

Cause: Validation of {0} location failed. The location specified does not exist.

Action: Enter a valid existing directory
Level: 1

Type: ERROR

Impact: Installation

INST-07529: Error in validating Farm Name

Cause: Farm Name cannot be {0}.

Action: Enter a different Farm Name.
Level: 1

Type: ERROR

Impact: Installation

INST-07530: Patchset component found in Oracle home

Cause: This Patchset has already been applied to the Oracle home

Action: Specify an Oracle home where the patchset has not already been applied.
Level: 1

Type: ERROR

Impact: Installation

INST-07531: Error in validating contents of Oracle home

Cause: The Oracle home provided does not contain {0}.

Action: In order to patch your existing version please provide an Oracle home that contains the product mentioned above. If you choose to continue, only the oracle_common directory and any components that both products have in common will be patched.
Level: 1

Type: ERROR

Impact: Installation

INST-07532: Error in validating contents of Oracle home

Cause: The Oracle home provided does not contain {0}.

Action: In order to patch your existing version please provide an Oracle home that contains the product mentioned above. If you choose to continue, only the oracle_common directory and any components that both products have in common will be patched.
Level: 1

Type: ERROR

Impact: Installation

INST-07533: Error in validating Middleware home location

Cause: Middleware home location specified is missing.

Action: Provide a valid Middleware home location
Level: 1

Type: ERROR

Impact: Installation

INST-07534: Error in validating Oracle home location

Cause: Oracle home location specified is not inside Middleware home location. Provide a directory name only for Oracle home.

Action: Provide a different Oracle home location which is inside Middleware home.
Level: 1

Type: ERROR

Impact: Installation

INST-07535: Error in obtaining hostname

Cause: An unexpected error occurred while retrieving hostname

Action: Provide a valid value
Level: 1

Type: ERROR

Impact: Installation

INST-07536: Error in validating Oracle home location

Cause: Middleware home location specified does not have the required Oracle homes installed in it. The Oracle homes for the following components are not installed: {0}.

Action: Provide a different Middleware home location or install the required Oracle Products and try the install again
Level: 1

Type: ERROR

Impact: Installation

INST-07537: The weblogic server processes are still running.

Cause: Unable to install while the weblogic processes are running.

Action: Make sure that the node manager and the weblogic servers are shutdown before the installation.
Level: 1

Type: ERROR

Impact: Installation

INST-07538: The OPMN processes are still running.

Cause: Unable to install while the OPMN processes are running.

Action: Make sure that opmnctl stopall is run before the installation.
Level: 1

Type: ERROR

Impact: Installation

INST-07539: {0} found in Oracle home

Cause: This Oracle home already contains a version of {0} which cannot be updated by this installation

Action: Specify either a new Oracle Home Directory or an Oracle Home which can be updated by this installer.
Level: 1

Type: ERROR

Impact: Installation

INST-07540: Error in validating Middleware home location

Cause: Patch {0} is not available in the Middleware home.

Action: Enter a valid Middleware home location
Level: 1

Type: ERROR

Impact: Installation

INST-07541: Error in validating Middleware home location

Cause: Patches {0} are not available in the Middleware home.

Action: Enter a valid Middleware home location
Level: 1

Type: ERROR

Impact: Installation

INST-08001: Validation of Middleware home location failed. Directory path invalid

Cause: Validation of Middleware home location failed. The location specified contains missing, mandatory directories

Action: Make sure that Oracle/Middleware is in the path
Level: 1

Type: ERROR

Impact: Installation

INST-08002: SSO Registration Failed.

Cause: IP Adress of this machine cannot be obtained.

Action: Check the network configuration of this machine
Level: 1

Type: ERROR

Impact: Installation

INST-08003: Internal Error: SSO Registration Failed.

Cause: There was an error while modifying the Oracle HTTP Server's configuration file.

Action: Provide the following files to Oracle Support : "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-08004: Internal Error: Installation of Oracle Web Cache failed.

Cause: An unexpected error occurred while trying to create Web Cache component

Action: Provide the following files to Oracle Support : "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-08005: Internal Error: Installation of Oracle HTTP Server failed.

Cause: An unexpected error occurred while trying to create Oracle HTTP Server component.

Action: Provide the following files to Oracle Support : "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-08006: Internal Error: Starting OPMN failed.

Cause: An exception occurred while trying to start OPMN

Action: Provide the following files to Oracle Support : "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-08007: Internal Error: Reload OPMN failed.

Cause: An exception occurred while trying to reload OPMN.

Action: Provide the following files to Oracle Support : "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-08008: Internal Error: Creation of ReportsServer Component failed.

Cause: An exception occurred while creating the ReportsServer Component

Action: Provide the following files to Oracle Support : "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-08009: Internal Error: Creation of ReportsTools Component failed.

Cause: An exception occurred while creating the ReportsTools Component

Action: Provide the following files to Oracle Support : "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-08010: An error occurred while registering the schema: {0} with the WebLogic Server.

Cause: Registering Schema failed with the exception: {0}

Action: Check if the Database: {0} is up and running.
Level: 1

Type: ERROR

Impact: Installation

INST-08011: Internal Error: Creation of Forms System Component failed.

Cause: An exception occurred while creating the Forms System Component

Action: Provide the following files to Oracle Support : "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-08012: Internal Error: Creation of FRSystemComponent failed.

Cause: An exception occurred while creating the FRSystemComponent

Action: Provide the following files to Oracle Support : "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-08013: Internal Error: Creation of Discoverer System Component failed.

Cause: An exception occurred while creating the Discoverer System Component

Action: Provide the following files to Oracle Support : "{0}""{1}"
Level: 1

Type: INTERNAL_ERROR

Impact: Installation

INST-08100: Error in validating component details

Cause: Selected components to upgrade do not match with the component list in existing Oracle Home

Action: The applications {0} selection status in Select Applications screen do not match the components in Oracle Home, please go back and select/deselect appropriate applications.
Level: 1

Type: ERROR

Impact: Installation

INST-08101: Error in validating component details

Cause: Error fetching input parameter

Action: Please provide correct input parameter
Level: 1

Type: ERROR

Impact: Installation

INST-10101: Error in validating {0} Base Image Location

Cause: {0} Base Image Location is null or blank.

Action: Provide a valid {0} Base Image Location
Level: 1

Type: ERROR

Impact: Installation

INST-10102: Error in validating {0} Base Image Location

Cause: The {0} Base Image Location provided is not existing or not a valid file

Action: Provide a valid {0} Base Image Location
Level: 1

Type: ERROR

Impact: Installation

INST-10103: Error in validating the {0} Base Image Location for Assembly Builder

Cause: An unexpected error occurred while validating the {0} Base Image Location for Assembly Builder

Action: Check the values
Level: 1

Type: ERROR

Impact: Installation

INST-10104: Error in validating {0} Base Image Location

Cause: The {0} Base Image File name must be {1}

Action: Provide a valid {0} Base Image Location
Level: 1

Type: ERROR

Impact: Installation

INST-10105: Error in validating {0} Base Image Virtual Machine configuration file Location

Cause: The {0} Base Image Virtual Machine configuration File (vm.cfg) is not existing

Action: The vm.cfg file must be present in same directory as the Base Image ({1}), provide a valid {0} Base Image Location
Level: 1

Type: ERROR

Impact: Installation

INST-10106: Error in validating Keystore

Cause: An unexpected error occurred while validating the {0} Keystore for Assembly Builder

Action: Check the values
Level: 1

Type: ERROR

Impact: Installation

INST-10107: The Keystore path must not be null or blank

Cause: The Keystore path must not be null or blank

Action: Provide a valid Keystore path
Level: 1

Type: ERROR

Impact: Installation

INST-10108: The Keystore password must not be null or blank

Cause: The Keystore password must not be null or blank

Action: Provide a valid Keystore password
Level: 1

Type: ERROR

Impact: Installation

INST-10109: Invalid keystore.

Cause: Failed to validate the Keystore.

Action: Provide a valid Keystore
Level: 1

Type: ERROR

Impact: Installation

INST-10110: The Key password must not be null or blank

Cause: The Key password must not be null or blank

Action: Provide a valid Key password
Level: 1

Type: ERROR

Impact: Installation

INST-10111: The Key alias must not be null or blank

Cause: The Key alias must not be null or blank

Action: Provide a valid Key alias
Level: 1

Type: ERROR

Impact: Installation

INST-10112: Invalid key alias

Cause: Invalid key alias and password combination.

Action: Provide a valid Key alias and password combination
Level: 1

Type: ERROR

Impact: Installation

INST-10113: Error in validating Component Version

Cause: Component Version is null or blank.

Action: Provide a valid Component Version.
Level: 1

Type: ERROR

Impact: Installation

INST-10114: Error in validating Component List

Cause: Component List is null or blank.

Action: Provide a valid Component List.
Level: 1

Type: ERROR

Impact: Installation

INST-10115: Error in validating Oracle Home

Cause: Oracle Home is null or blank.

Action: Provide a valid Oracle Home.
Level: 1

Type: ERROR

Impact: Installation

INST-10116: Installation of Studio and Deployer detected in the selected Oracle Home. Installing into an existing Oracle Home is done to either reinstall binaries or to upgrade an Oracle Home from one release to another

Cause: Installation of Studio and Deployer detected in the selected Oracle Home.

Action: Installing into an existing Oracle Home is done to either reinstall binaries or to upgrade an Oracle Home from one release to another.
Level: 1

Type: ERROR

Impact: Installation

INST-10117: Error in validating the installed component in {0} Oracle Home

Cause: An unexpected error occurred while validating the installed component in {0} Oracle Home

Action: An unexpected error occurred while validating the installed component in {0} Oracle Home
Level: 1

Type: ERROR

Impact: Installation

48 IRM-00001 to IRM-03012

IRM-00001: The class {0} cannot be found and cannot be unmarshalled by JAXB.

Cause: A class was specified in XML that could not be found.

Action: Verify that the class is available and on the class path.
Level: 1

Type: WARNING

Impact: Data

IRM-00002: The value {0} is not a valid UUID format and cannot be unmarshalled by JAXB.

Cause: A UUID was specified in XML that could not be parsed.

Action: Verify the format of the UUID.
Level: 1

Type: WARNING

Impact: Data

IRM-00003: Creating a field value resulted in an exception.

Cause: Creating a field value resulted in an exception.

Action: Review the exception cause for further information.
Level: 1

Type: WARNING

Impact: data

IRM-00501: The offline store cannot be accessed. It will be recreated.

Cause: The offline store is not from this instance.

Action: This is a notification and no action is required.
Level: 16

Type: NOTIFICATION

Impact: data

IRM-01001: The context identified with UUID {0} does not exist.

Cause: A context was specified that does not exist.

Action: Ensure that the context UUID value corresponds to a context stored in the server and retry the operation.
Level: 32

Type: TRACE

Impact: Data

IRM-01002: The test content identified by the name {0} does not exist.

Cause: Test content was specified that does not exist.

Action: Each piece of test content is identified by an unique name. Ensure that the provided test content name is correct.
Level: 32

Type: TRACE

Impact: Data

IRM-01003: There has been an error using a cryptography algorithm.

Cause: An error was encountered while using a cryptography algorithm.

Action: Most cryptography exceptions are caused by an exception from the cryptography algorithm implementation. Refer to the exception cause to further diagnose the error. Typical examples of a cryptography exception include attempting to generate a key for a key size that is not supported, or a failure to decrypt due to corrupt data.
Level: 1

Type: ERROR

Impact: Security

IRM-01004: Unknown or unsupported cryptography schema {0}.

Cause: The cryptographic schema is not known to the system.

Action: Ensure that the provided cryptographic schema identity value is supported by the system.
Level: 1

Type: ERROR

Impact: Security

IRM-01005: The cryptography schema \"{0}\" is unsupported on this platform or configuration.

Cause: An operation was attempted that would have caused a mix of FIPS and non-FIPS key sets to be present in the system.

Action: When a key set is created, the cryptography schema details are recorded with the key set. The server is unable to deliver a mix of FIPS and non-FIPS key sets to the desktop. Ensure that the cryptography schema used is compatible with the cryptography schemas already in use by the system.
Level: 1

Type: ERROR

Impact: Security

IRM-01006: The key set identified with UUID {0} already exists.

Cause: A key set was specified that already exists.

Action: Generate a new UUID for the key set and retry the operation.
Level: 32

Type: TRACE

Impact: Programmatic

IRM-01007: The key set identified with UUID {0} does not exist.

Cause: A key set was specified that does not exist.

Action: Ensure that the key set specified exists and retry the operation.
Level: 16

Type: TRACE

Impact: Data

IRM-01008: The {0} wrapping key algorithm is not supported.

Cause: An unsupported key type was supplied for the wrapping key.

Action: Ensure that the wrapping key stored in the key store uses a supported algorithm. The supported key types are AES, DESede, and RSA.
Level: 1

Type: ERROR

Impact: Security

IRM-01010: An exception occurred parsing sealed content: {0}.

Cause: Sealed content was provided that has been corrupted.

Action: Obtain a non-corrupted copy of the sealed content. The exception reason will provide more details of what part of the sealed content is corrupt.
Level: 16

Type: TRACE

Impact: Data

IRM-01011: The sealing process requires non-empty content.

Cause: Content was provided for sealing that was empty.

Action: Provide non-empty data to the sealing operation.
Level: 32

Type: TRACE

Impact: Data

IRM-01012: There has been an error using the key store.

Cause: An error was reported loading or accessing a key store.

Action: Examine the exception cause to diagnose the problem further. Typical reasons for this exception include the key store file not being in the configured location and incorrect passwords.
Level: 1

Type: ERROR

Impact: Data

IRM-01013: The key {0} does not exist in the key store {1}.

Cause: A key alias was provided that identified a key that does not exist in the key store.

Action: Use tools such as keytool to ensure that the contents of the key store include the key with the specified key alias.
Level: 16

Type: TRACE

Impact: Programmatic

IRM-01014: The MIME type {0} is syntactically invalid.

Cause: A MIME type was specified that is syntactically invalid.

Action: Correct the MIME type value. The MIME type should consist of a type and subtype (for example, text/plain).
Level: 16

Type: TRACE

Impact: Data

IRM-01015: Unknown content type/format.

Cause: The content format could not be determined as the content-type HTTP header was missing.

Action: Ensure the web service correctly specifies the content type in the HTTP response.
Level: 16

Type: TRACE

Impact: Programmatic

IRM-01016: Unsupported content type: {0}.

Cause: An unsupported content type was provided for sealing.

Action: None. Sealing cannot be performed on a format that is not supported.
Level: 16

Type: TRACE

Impact: Programmatic

IRM-01017: Group accounts are not supported. The group {0} cannot be used in this context.

Cause: A group account was provided to an operation that does not support the use of group accounts.

Action: Specify a user and retry the operation.
Level: 16

Type: TRACE

Impact: Programmatic

IRM-01018: An error has occurred accessing user or group information.

Cause: An internal exception occurred when accessing the user and group repository (for example LDAP).

Action: Refer to the exception cause to further diagnose the error.
Level: 1

Type: WARNING

Impact: Data

IRM-01019: The account identified by {0} is unknown.

Cause: An unknown account was specified.

Action: Correct the account UUID or name and retry the operation.
Level: 16

Type: TRACE

Impact: Data

IRM-01020: The classification is unknown to the system. The classification may have been deleted, may have never existed, or the classification details may be incorrect.

Cause: The classification is unknown to the system. The classification may have been deleted, may have never existed, or the classification details may be incorrect.

Action: Correct the classification details and retry the operation.
Level: 16

Type: TRACE

Impact: Data

IRM-01021: The classification system {0} is not supported.

Cause: A classification system was specified that the server does not support.

Action: Check with the server administrator and ensure that the classification system is supported.
Level: 16

Type: TRACE

Impact: Data

IRM-01022: The configuration setting {0} is not specified, is invalid, or cannot be read.

Cause: A required configuration setting is missing from the configuration, is invalid, or could not be read.

Action: Correct the configuration settings.
Level: 1

Type: ERROR

Impact: Configuration

IRM-01023: The desktop is repudiated.

Cause: A user's desktop software has been repudiated and can no longer contact the server.

Action: Ensure that the client has the appropriate software installed.
Level: 16

Type: NOTIFICATION

Impact: Security

IRM-01024: The feature with id {0} is not present in the list of available features.

Cause: A feature was specified that is not present in the list of available features.

Action: Correct the feature id and retry the operation.
Level: 32

Type: TRACE

Impact: Programmatic

IRM-01025: Licenses are available, but are on the following device(s): {0}.

Cause: A license was requested but all licenses available were in use on other devices.

Action: Check in licenses from the listed devices and retry opening content. If licenses must be used on multiple devices at the same time increase the server device count configuration setting.
Level: 1

Type: TRACE

Impact: Other

IRM-01026: An exception occurred processing a desktop SOAP message: {0}.

Cause: An error occurred while processing a desktop SOAP request or response message.

Action: Review the reason property of the exception for further details. This exception typically means that a corrupt or incorrect message was sent to the server.
Level: 1

Type: ERROR

Impact: Security

IRM-01027: Unsupported protocol version {0}. The required protocol version is {1}.

Cause: A desktop protocol version was provided that the server does not support.

Action: Use a lower protocol version and retry the request. The valid range of protocol versions will be specified in the exception details.
Level: 16

Type: NOTIFICATION

Impact: Requests/Responses

IRM-01028: A new version ({0}) of the desktop is available.

Cause: An upgrade was available for a client's desktop software.

Action: Upgrade the desktop software on the client.
Level: 1

Type: TRACE

Impact: Requests/Responses

IRM-01029: The account \"{0}\" has already been assigned an administrator role.

Cause: An account could not be assigned the administrator role because it is already assigned.

Action: No action is required.
Level: 32

Type: TRACE

Impact: Programmatic

IRM-01030: The account \"{0}\" has already been assigned the role \"{1}\".

Cause: An account could not be assigned the specified role because it is already assigned.

Action: No action is required.
Level: 16

Type: TRACE

Impact: Programmatic

IRM-01031: The account \"{0}\" has already been assigned an inspector role.

Cause: An account could not be assigned the inspector role because it is already assigned.

Action: No action is required.
Level: 16

Type: TRACE

Impact: Programmatic

IRM-01032: The account \"{0}\" has already been assigned a manager role.

Cause: An account could not be assigned the manager role because it is already assigned.

Action: No action is required.
Level: 16

Type: TRACE

Impact: Programmatic

IRM-01033: The specified accounts cannot be removed as this action would remove all administrators.

Cause: The specified accounts could not be removed because there must be at least one administrator for a Domain.

Action: Ensure that an administrator will remain following the request and then retry the operation.
Level: 16

Type: TRACE

Impact: Programmatic

IRM-01034: The context \"{0}\" cannot be deleted as there are rights assigned within this context.

Cause: A context could not be deleted because there are rights assigned with the context.

Action: Remove all rights assigned with the context and retry the operation.
Level: 16

Type: TRACE

Impact: Programmatic

IRM-01035: The context template \"{0}\" cannot be deleted.

Cause: A context template could not be deleted because there are context instances that refer to it.

Action: Remove all context instances that refer to the template and retry the operation.
Level: 16

Type: TRACE

Impact: Programmatic

IRM-01036: The document role \"{0}\" cannot be deleted as there are rights assigned to this role.

Cause: A document role could not be deleted because there are rights assigned to the role.

Action: Remove all rights assigned to the role and retry the operation.
Level: 16

Type: TRACE

Impact: Programmatic

IRM-01037: The specified accounts cannot be removed as this action would remove all managers.

Cause: An account could not be removed because there must be at least one manager for a Domain.

Action: Ensure that a manager will remain following the request and then retry the operation.
Level: 16

Type: TRACE

Impact: Programmatic

IRM-01038: A context with \"{0}\" already exists.

Cause: A context instance UUID was specified that already exists.

Action: Use a different context UUID.
Level: 16

Type: TRACE

Impact: Programmatic

IRM-01039: The context template \"{0}\" already exists.

Cause: A context template UUID was specified that already exists.

Action: Use a different context template UUID. A context template UUID must be unique within the same domain.
Level: 16

Type: TRACE

Impact: Programmatic

IRM-01040: The document role \"{0}\" already exists.

Cause: A document role UUID was specified that already exists within the domain.

Action: Use a different document role UUID. A role UUID must be unique within the same domain.
Level: 16

Type: TRACE

Impact: Programmatic

IRM-01041: The domain \"{0}\" already exists.

Cause: A domain UUID was specified that already exists.

Action: Use a different UUID.
Level: 16

Type: TRACE

Impact: Programmatic

IRM-01042: There are no domains created in the system.

Cause: No domains were available in the system.

Action: Create at least one domain in the system.
Level: 16

Type: TRACE

Impact: Programmatic

IRM-01043: The context template \"{0}\" is inactive and cannot be used to create contexts.

Cause: An inactive context template was specified.

Action: Activate the context template and retry the operation.
Level: 16

Type: TRACE

Impact: Programmatic

IRM-01044: The role \"{0}\" cannot be used with template \"{1}\" as their domains do not match.

Cause: An attempt was made to add a role to a template that does not belong to the same domain.

Action: Specify a role from the same domain as the template.
Level: 16

Type: TRACE

Impact: Programmatic

IRM-01045: The \"{0}\" role must have at least one primary feature.

Cause: A specified document role did not have a primary feature.

Action: Add at least one primary feature to the role.
Level: 16

Type: TRACE

Impact: Programmatic

IRM-01046: The \"{0}\" role must have a refresh period greater that one minute.

Cause: A document role specified an invalid time period.

Action: Provide a refresh period greater than one minute.
Level: 16

Type: TRACE

Impact: Programmatic

IRM-01047: The context template with UUID \"{0}\" on domain \"{1}\" does not exist.

Cause: An unknown context template was specified.

Action: Correct the context template UUID and retry the operation.
Level: 16

Type: TRACE

Impact: Programmatic

IRM-01048: The right with UUID \"{0}\" does not exist.

Cause: An unknown right was specified.

Action: Ensure that the UUID corresponds to a right.
Level: 16

Type: TRACE

Impact: Programmatic

IRM-01049: The document role with UUID \"{0}\" on domain \"{1}\" does not exist.

Cause: An unknown document role was specified.

Action: Ensure that the UUID corresponds to a document role.
Level: 16

Type: TRACE

Impact: Programmatic

IRM-01050: The domain with UUID \"{0}\" does not exist.

Cause: An unknown domain was specified.

Action: Ensure that the UUID corresponds to a domain.
Level: 16

Type: TRACE

Impact: Programmatic

IRM-01051: The context \"{1}\" does not support role \"{0}\".

Cause: A role was assigned to a account which was not supported by the context.

Action: Add the role to the related context template.
Level: 16

Type: TRACE

Impact: Programmatic

IRM-01052: A dynamic class contains either two stubs or head slices. The duplicate slice class is {0}.

Cause: A dynamic class contained either more than one stub slice or more than one head slice.

Action: Alter the dynamic class configuration such that it has at most one stub and one head slice.
Level: 1

Type: WARNING

Impact: Programmatic

IRM-01053: The dynamic class {0} [{1}] does not contain any implementation slices.

Cause: A dynamic class did not contain any implementation slices.

Action: Alter the dynamic class configuration such that it has at least one implementation slice.
Level: 1

Type: WARNING

Impact: Programmatic

IRM-01054: An error occurred during injection of the {1} on class {0}.

Cause: Injected data was provided for a dynamic class and an error occurred injecting that data.

Action: Ensure that the injected data is valid for the dynamic class.
Level: 1

Type: WARNING

Impact: Programmatic

IRM-01055: Injection data cannot be found for the mandatory injected field {1} on class {0}.

Cause: Injected data was not provided for a dynamic class that required it.

Action: Ensure that all mandatory injected data is provided for the dynamic class.
Level: 1

Type: WARNING

Impact: Programmatic

IRM-01056: The class {0} cannot be used as a slice.

Cause: A dynamic class contained a class that could not be used as a slice.

Action: Ensure that the class is derived from the appropriate slice class.
Level: 1

Type: WARNING

Impact: Programmatic

IRM-01057: The method {1} is not a supported method on the {0} class.

Cause: A slice class provided a list of implemented methods that contained a method not supported by the slice class.

Action: Ensure that all implemented methods in the definition are supported by the slice class.
Level: 1

Type: WARNING

Impact: Programmatic

IRM-01058: The class {0} must implement all the slice methods.

Cause: A dynamic class definition included a stub class that did not implement all of the methods available.

Action: Correct the definition of the stub class.
Level: 1

Type: WARNING

Impact: Programmatic

IRM-01059: The slice purpose annotation on class {0} is not specified.

Cause: A slice class did not specify its purpose using the aspect annotation.

Action: Add an appropriate aspect annotation to the slice class implementation.
Level: 1

Type: WARNING

Impact: Programmatic

IRM-01060: The dynamic class definition file {1} for {0} cannot be loaded.

Cause: The definition for a dynamic class could not be found.

Action: Correct the resource path specified for the dynamic class.
Level: 1

Type: WARNING

Impact: Programmatic

IRM-01061: Not authorized to perform this operation.

Cause: A sealed content operation was attempted which was not authorized.

Action: Ensure that the authenticated user has the appropriate license to perform the sealing, resealing, peeking, or unsealing operation. Check that the classification key set is valid. Check the the classification URL is correct. Check that the licenses are not checked out to a different device.
Level: 1

Type: NOTIFICATION

Impact: Security

IRM-01062: A duplicate {0} element is supplied where a duplicate is not allowed or expected.

Cause: A duplicate element was provided where a duplicate is not allowed/expected.

Action: Ensure that the input data does not contain duplicates.
Level: 16

Type: TRACE

Impact: Programmatic

IRM-01063: The parameter {1} passed into {0} has an illegal value.

Cause: An illegal value was passed as a method argument.

Action: Correct the invalid value and retry the operation.
Level: 16

Type: TRACE

Impact: Programmatic

IRM-01064: The {0} {1} property cannot exceed {4} characters in length. The invalid value provided was {2}, which has {3} characters.

Cause: A value was used as a property which exceeded the maximum permitted length.

Action: Correct the invalid property and retry the operation.
Level: 16

Type: TRACE

Impact: Programmatic

IRM-01065: The {0} {1} property has an illegal value.

Cause: An illegal value was specified for a property.

Action: Correct the invalid value and retry the operation.
Level: 16

Type: TRACE

Impact: Programmatic

IRM-01066: The {0} {1} is immutable and cannot be modified.

Cause: An attempt was made to alter a property that is read-only or immutable.

Action: Make a copy of the property to make changes.
Level: 16

Type: TRACE

Impact: Programmatic

IRM-01067: An unexpected error has occurred. If this exception does not include details of the cause, then examine the diagnostic logs for more details.

Cause: An unexpected error occurred.

Action: Review the exception cause for further details.
Level: 1

Type: WARNING

Impact: Other

IRM-01068: The parameter {1} passed into {0} is mandatory.

Cause: A mandatory argument was not specified.

Action: Provide the value and retry the operation.
Level: 16

Type: TRACE

Impact: Programmatic

IRM-01069: The {0} {1} property is mandatory.

Cause: A mandatory property was not specified.

Action: Provide the value and retry the operation.
Level: 16

Type: TRACE

Impact: Programmatic

IRM-01070: The enumeration value {0} is unsupported in this context.

Cause: An unsupported enumeration value was provided.

Action: Correct the value and retry the operation.
Level: 16

Type: TRACE

Impact: Programmatic

IRM-01071: A response could not be found for method {0} on class %Class%.

Cause: A method invocation required a fixed response and one could not be found.

Action: Correct the fixed responses provided to the response slice.
Level: 1

Type: TRACE

Impact: Programmatic

IRM-01072: The transaction has been rolled back. If this exception does not include details of the cause then examine the diagnostic logs for more details.

Cause: A transaction commit failed.

Action: Review the exception cause for further information.
Level: 1

Type: TRACE

Impact: Data

IRM-01073: The response or method {0} is unsupported by class {1}.

Cause: A response or the method provided to a response slice is not supported.

Action: Correct the fixed responses provided to the response slice.
Level: 1

Type: TRACE

Impact: Programmatic

IRM-01074: The web service endpoint address for the service {0} is missing.

Cause: A web service endpoint address was not specified.

Action: Provide the endpoint address for the endpoint.
Level: 1

Type: WARNING

Impact: Configuration

IRM-01075: The credentials for the web service could not be determined.

Cause: Web service credentials were not provided.

Action: Provide the credentials in the IRM credential store using the web service address as the key.
Level: 1

Type: WARNING

Impact: Configuration

IRM-01076: Status page redirected to URI.

Cause: A status page request has been redirected to another system.

Action: This is not an error and no action is required by the system administrator.
Level: 16

Type: TRACE

Impact: Requests/Responses

IRM-01076: The item constraints for role \"{0}\" cannot be altered as the role has been assigned to a user or group.

Cause: An attempt has been made to alter the role item constraints for a role that has been assigned to a user or group.

Action: Unassign the users and groups that are using the role.
Level: 16

Type: TRACE

Impact: Programmatic

IRM-01077: The encrypted content block size must be a direct multiple of the cipher block size. The cipher block size is {0}, but the encrypted content block size has been set as {1}.

Cause: An illegal encrypted content block size was provided during sealing.

Action: Use a block size that is a direct multiple of the cipher block size. Block sizes are typically multiples of 16.
Level: 32

Type: TRACE

Impact: Programmatic

IRM-01078: The public header cannot exceed {1} bytes in length. The current public header when written as XML has a length of {0} bytes. Reduce the amount of data provided in the custom data or classification cookie.

Cause: A public header exceeded the maximum length.

Action: Reduce the amount of data provided in the classification labels or custom data.
Level: 16

Type: TRACE

Impact: Programmatic

IRM-01079: The parameter {1} passed into {0} cannot exceed {4} characters in length. The invalid value provided was {2} which has {3} characters.

Cause: A value was passed as a method argument which exceeded the permitted length.

Action: Correct the invalid value and retry the operation.
Level: 16

Type: TRACE

Impact: Programmatic

IRM-01080: Licenses are available, but they cannot be used for the following reasons: {0}.

Cause: A license was available to the user but could not be used for the specified classification.

Action: Check the exception for the list of licenses and associated availability status. The availability will provide the reason why the license cannot be used. For example, the license may not support the requested feature or the license may have time constraints that disallow use of the license at the time of the license request.
Level: 1

Type: TRACE

Impact: Other

IRM-01081: A wrapping key {1} bits in size is insufficient to wrap a {0} bit key.

Cause: A wrapping key could not be used to wrap a key as it was of insufficient size.

Action: Increase the size of the wrapping key used or reduce the size of the key being wrapped.
Level: 1

Type: ERROR

Impact: Security

IRM-01081: The expected size of the unsealed content was {0} bytes in length. The actual number of bytes read from the input stream was {1}.

Cause: The unsealed content size does not match the amount of data read from a stream.

Action: Ensure the unsealed content size matches the amount of data provided in the input stream.
Level: 16

Type: TRACE

Impact: Data

IRM-03001: An exception occurred retrieving the rights for the context.

Cause: An exception occurred retrieving the rights for a context.

Action: Review the exception cause for further information.
Level: 1

Type: ERROR

Impact: Data

IRM-03002: An exception occurred retrieving the context managers.

Cause: An exception occurred retrieving context managers.

Action: Review the exception cause for further information.
Level: 1

Type: ERROR

Impact: Data

IRM-03003: An exception occurred reading the uploaded file - {0}.

Cause: An exception occurred reading an uploaded file.

Action: Review the exception cause for further information.
Level: 1

Type: WARNING

Impact: Data

IRM-03004: An exception occurred retrieving the refresh periods.

Cause: An exception occurred retrieving refresh periods.

Action: Review the exception cause for further information.
Level: 1

Type: SEVERE

Impact: Data

IRM-03005: An exception occurred retrieving the global features.

Cause: An exception occurred retrieving the global features.

Action: Review the exception cause for further information.
Level: 1

Type: SEVERE

Impact: Data

IRM-03006: An exception occurred retrieving the primary features.

Cause: An exception occurred retrieving the primary features.

Action: Review the exception cause for further information.
Level: 1

Type: SEVERE

Impact: Data

IRM-03007: An exception occurred retrieving the feature labels.

Cause: An exception occurred retrieving the feature labels.

Action: Review the exception cause for further information.
Level: 1

Type: SEVERE

Impact: Data

IRM-03008: An exception occurred determining the available locales.

Cause: An exception occurred determining the available locales.

Action: Review the exception cause for further information.
Level: 1

Type: WARNING

Impact: Data

IRM-03009: IRM EJBs are not deployed.

Cause: The IRM EJBs could not be found by the management console.

Action: Ensure that the IRM EJBs are deployed and accessible by the web application.
Level: 1

Type: SEVERE

Impact: Installation

IRM-03010: Domain is not seeded.

Cause: No domain was found.

Action: Log in to the management console to trigger seeding of the initial domain.
Level: 1

Type: SEVERE

Impact: Configuration

IRM-03011: User has no role.

Cause: No role could be found for a user.

Action: Assign an appropriate role to the user.
Level: 32

Type: TRACE

Impact: Configuration

IRM-03012: An exception occurred retrieving user details.

Cause: An exception occurred retrieving user details.

Action: Review the exception cause for further information.
Level: 1

Type: WARNING

Impact: Data

49 J2EE HTTPC-00004 to J2EE HTTPC-12011

J2EE HTTPC-00004: Unable to parse header value: name={0}, value="{1}".

Cause:

Action:
Level: 16

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-00015: Unable to read response for method={0}, path+query="{1}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-00016: Unable to read response for input stream hashcode={0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-00017: Socks: V4 request failure: {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-01000: Unable to register built-in AuthenticationScheme {0}.

Cause:

Action:
Level: 16

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-01001: Unable to register AuthenticationScheme {0} for scheme name {1}.

Cause:

Action:
Level: 16

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-01002: Unable to add NTLM credentials. The AuthorizationHandler does not implement the AuthenticationSchemeRegistryHolder interface.

Cause:

Action:
Level: 16

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-01004: Unable to add NTLM credentials. NTLM AuthenticationScheme was not found in the AuthorizationHandler''s AuthenticationSchemeRegistry.

Cause:

Action:
Level: 16

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-01010: AuthM: Handling deferred authorization challenge.

Cause:

Action:
Level: 32

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-01011: AuthM: Sending request with Authorization = "{0}".

Cause:

Action:
Level: 32

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-01012: AuthM: Sending request with Proxy-Authorization = "{0}".

Cause:

Action:
Level: 32

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-01013: AuthM: Preemptively sending Proxy-Authorization "{0}".

Cause:

Action:
Level: 32

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-01014: AuthM: Preemptively sending Authorization "{0}".

Cause:

Action:
Level: 32

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-01015: AuthM: Server refused the given Authorization info {0} times, aborting request.

Cause:

Action:
Level: 32

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-01016: AuthM: Status {0} not handling - request has an output stream.

Cause:

Action:
Level: 32

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-01017: AuthM: Deferring handling of status {0} due to use of an output stream.

Cause:

Action:
Level: 32

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-01018: AuthM: Handling status: {0} "{1}".

Cause:

Action:
Level: 32

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-01019: AuthM: Resending request with Authorization "{0}".

Cause:

Action:
Level: 32

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-01020: AuthM: Resending request with Proxy-Authorization "{0}".

Cause:

Action:
Level: 32

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-01021: AuthM: Not handling status {0} because finding no Authorization information.

Cause:

Action:
Level: 32

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-01022: AuthM: Parsing {0} challenges:

Cause:

Action:
Level: 32

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-01023: AuthM: Challenge {0}

Cause:

Action:
Level: 32

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-02001: ContentEncMod: pushing gzip-input-stream

Cause:

Action:
Level: 32

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-02002: ContentEncMod: pushing inflater-input-stream

Cause:

Action:
Level: 32

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-02003: ContentEncMod: pushing uncompress-input-stream

Cause:

Action:
Level: 32

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-02004: ContentEncMod: ignoring "identity" token

Cause:

Action:
Level: 32

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-02005: ContentEncMod: Unknown content encoding "{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-03000: ContentMD5Mod: Received digest: "{0}" - pushing md5-check-stream

Cause:

Action:
Level: 32

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-03001: ContentMD5Mod: Expecting digest in trailer - pushing md5-check-stream

Cause:

Action:
Level: 32

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-03003: ContentMD5Mod: successfully verifying hash

Cause:

Action:
Level: 32

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-04006: Cookie: Bad Set-Cookie header: "{0}". Finding no equal sign(=) for token starting at position {1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-04007: Cookie: Ignoring cookie: {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-04008: Cookie: Bad Set-Cookie header: "{0}", invalid date "{1}"

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-04009: Bad Set-Cookie header: ''{0}'', Max-Age ''{1}'' is negative.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-04011: Cookie: Bad Set-Cookie header: "{0}", domain is empty - ignoring domain.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-04012: Cookie: Bad Set-Cookie header: "{0}", current domain "{1}" does not match given parsed "{2}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-04013: Cookie: Bad Set-Cookie header: "{0}", domain attribute "{1}" is not .local and does not have at least two dots.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-04014: Cookie: Bad Set-Cookie header: "{0}", domain attribute "{1}" is more than one level below current domain {2}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-04015: Cookie2: Bad Set-Cookie2 header: "{0}", path "{1}" is not a prefix of the request URI "{2}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-04016: Cookie2: Bad Set-Cookie2 header: "{0}", domain "{1}" is not ".local" and does not contain two "."s.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-04017: Cookie2: Bad Set-Cookie2 header: "{0}", domain "{1}" does not match current host "{2}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-04018: Cookie2: Bad Set-Cookie2 header: "{0}", domain "{1}" is more than one dot(.) away from host "{2}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-04019: Cookie2: Bad Set-Cookie2 header: "{0}", port list does not include current port {1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-04020: Cookie: TLD, "{0}", does not start with ".", so it was removed from extendedTLDs.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-05000: Not handling status {0} {1} because exceeding maximum number of retries.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-05001: IOE closing InputStream for status 411: {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-09000: HTTPConnection instance {0} has chunking enabled: {1}.

Cause:

Action:
Level: 32

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-09001: HTTPConnection instance {0} has chunk size set to {1}.

Cause:

Action:
Level: 32

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-12000: Setting Maximum Authorization retries to {0}.

Cause:

Action:
Level: 16

Type: NOTIFICATION

Impact: Requests/Responses

J2EE HTTPC-12001: ''{0}'' is enabled

Cause:

Action:
Level: 16

Type: NOTIFICATION

Impact: Requests/Responses

J2EE HTTPC-12002: ''{0}'' is disabled

Cause:

Action:
Level: 16

Type: NOTIFICATION

Impact: Requests/Responses

J2EE HTTPC-12003: Version: {0}

Cause:

Action:
Level: 16

Type: NOTIFICATION

Impact: Requests/Responses

J2EE HTTPC-12004: Enabling deferred handling of responses to streamed requests.

Cause:

Action:
Level: 16

Type: NOTIFICATION

Impact: Requests/Responses

J2EE HTTPC-12005: Setting Socket Idle Timeout to {0} seconds.

Cause:

Action:
Level: 16

Type: NOTIFICATION

Impact: Requests/Responses

J2EE HTTPC-12006: Adding module {0}.

Cause:

Action:
Level: 16

Type: NOTIFICATION

Impact: Requests/Responses

J2EE HTTPC-12007: Adding module {0} to {1} list.

Cause:

Action:
Level: 16

Type: NOTIFICATION

Impact: Requests/Responses

J2EE HTTPC-12008: Removing module {0} from {1} list.

Cause:

Action:
Level: 16

Type: NOTIFICATION

Impact: Requests/Responses

J2EE HTTPC-12009: Default HTTP proxy set to {0}:{1,number,0}.

Cause:

Action:
Level: 16

Type: NOTIFICATION

Impact: Requests/Responses

J2EE HTTPC-12010: Setting Socket Connection Timeout to {0} milliseconds

Cause:

Action:
Level: 16

Type: NOTIFICATION

Impact: Requests/Responses

J2EE HTTPC-12011: Setting Socket Read Timeout to {0} milliseconds

Cause:

Action:
Level: 16

Type: NOTIFICATION

Impact: Requests/Responses

50 J2EE JMX-46000 to J2EE JMX-47006

J2EE JMX-46000: It is not possible to start a state-manageable instance while it is being stopped.

Cause: A resource that was being stopped was asked to start.

Action: Wait until the resource is fully stopped before attempting to restart it.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46001: A state-manageable object is not started. The reason is "{0}".

Cause: A resource could not be started.

Action: Correct the root cause cited in the generated message.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46002: It is not possible to stop a state-manageable instance while it is being started.

Cause: A resource that was being started was asked to stop.

Action: Wait until the resource is fully started before attempting to stop it.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46003: A state-manageable object is not stopped. The reason is "{0}".

Cause: A resource could not be stopped.

Action: Correct the root cause cited in the generated message.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46004: The Notifications and Notification annotations cannot be used together.

Cause: An MBean interface was annotated with both the @Notification and @Notifications annotations.

Action: Use either @Notification or @Notifications to annotate the MBean interface, but not both.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46005: The Notifications and Notification annotations cannot be used on both the management and implementation classes.

Cause: The @Notification or @Notifications annotation was used on both the MBean interface and MBean implementation class. Only the MBean interface should be annotated with @Notification or @Notifications.

Action: Remove the conflicting annotation from the implementation class.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46006: Could not find MBean operation "{0}" for MBean registered under "{1}" and implemented by "{2}"

Cause: Operation signature might not match

Action: Verify operation signature against MBean metadata or MBean implementation class
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46007: Error getting MBeanServer for Config MBean "{0}" implemented by "{1}"

Cause: Internal error.

Action: No action is required. The default MBeanServer association will be used.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46008: Error initializing the JMX FRamework SPI "{0}"

Cause: Internal error. See nested exception.

Action: Based on nested exception root cause.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46009: Error loading the JMX FRamework SPI "{0}"

Cause: Internal error. See nested exception.

Action: Based on nested exception root cause.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46010: JMX Portable Framework initialized with platform SPI "{0}"

Cause: The message is informational only.

Action: No action is required.
Level: 1

Type: TRACE

Impact: Programmatic

J2EE JMX-46011: The @Inject annotation can be used only on a method that exposes a single parameter whose type is the type of the resource to be injected.

Cause: The JMX MBean @Inject annotation was used on a method that did not have a single parameter with the proper type.

Action: Change the associated MBean method to have a single parameter with the proper type or replace the @Inject annotation.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46012: Error registering MBean whose ObjectName is "{0}" and implementation class is "{1}"

Cause: See nested exception.

Action: Based on nested exception root cause.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46013: The {0} argument cannot be null.

Cause: An argument was passed a null value, which is invalid. The name of the argument is specified as part of the generated message.

Action: Change the argument value to be a valid non-null value.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46014: A notification listener for MBean "{0}" cannot be added.

Cause: The MBean did not declare that it sends notifications.

Action: Change the MBean code to declare that it sends notifications or remove the code that attempts to register a notification listener for the MBean.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46015: The resource with key "{0}" and bundle "{1}" declared in the Description annotation on attribute "{2}" of MBean "{3}" cannot be found.

Cause: The resource defined by the Description annotation that was associated with an MBean attribute was missing. The generated message specified the MBean, attribute, resource key and resource bundle.

Action: Ensure that the Description annotation includes the correct resourceBundleBaseName key and that the default resource bundle exists.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46016: The resource with key "{0}" and bundle "{1}" declared in the Description annotation on operation "{2}" of MBean "{3}" cannot be found.

Cause: The resource defined by a Description annotation that was associated with an MBean operation was missing. The generated message specified the MBean, operation, resource key and resource bundle.

Action: Ensure that the Description annotation includes the correct resourceBundleBaseName key and that the default resource bundle exists.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46017: The resource with key "{0}" and bundle "{1}" declared in the Description annotation on parameter "{2}" of operation "{3}" of MBean "{4}" cannot be found.

Cause: The resource defined by a Description annotation that was associated with an MBean operation parameter was missing. The generated message specified the MBean, operation, parameter name, resource key and resource bundle.

Action: Ensure that the Description annotation includes the correct resourceBundleBaseName and that the default resource bundle exists.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46018: The resource with key "{0}" and bundle "{1}" declared in the Description annotation on MBean "{2}" cannot be found.

Cause: The resource defined by a Description annotation that was associated with an MBean interface was missing. The generated message specified the MBean, resource key and resource bundle.

Action: Ensure that the Description annotation includes the correct resourceBundleBaseName key and that the default resource bundle exists.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46019: The resource with key "{0}" and bundle "{1}" declared in the Description annotation on feature "{2}" of MBean "{3}" cannot be found.

Cause: A resource that was defined in one of the MBean descriptors properties (descriptionResourceKey or descriptionResourceBundleBaseName) was missing. The generated message specified the MBean, resource key and resource bundle.

Action: Add the resource or change the MBean descriptor property.
Level: 1

Type: WARNING

Impact: Configuration

J2EE JMX-46020: No PersistenceManager is declared for MBean "{0}".

Cause: The PersistenceManagers were missing.

Action: When PMCompositeConfigMBeanSupport is used, specify a shared PersistenceManager or specify individual PersistenceManagers for the two config files (use injection-name 'file1' and 'file2' in mbeans.xml).
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46021: The Persistable for MBean "{0}" is not defined.

Cause: The expected Persistable for the MBean was missing.

Action: Provide the Persistable for the MBean.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46022: A resource bundle name must be specified in order to use message localization methods.

Cause: The resource bundle name was missing.

Action: Define the resource bundle name.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46023: A shared PersistenceManager and an individual PersistenceManager cannot both be declared for MBean "{0}".

Cause: Both a shared and an individual PersistenceManager were declared for the MBean.

Action: When PMCompositeConfigMBeanSupport is used, specify either one shared persistence manager with no injection name, or two persistence managers with injection names "file1" and "file2", in mbeans.xml.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46024: At least one configuration object used by MBean "{0}" for type "{1}" is not registered.

Cause: At least one of the configuration objects used by a Composite ConfigMBean was not registered.

Action: Register the appropriate configuration object.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46025: The type "{1}" used for MBean "{0}" is not valid for either configuration object "{2}" or "{3}".

Cause: The type used for a configuration object for the MBean was not valid.

Action: Use the correct type for the configuration object.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46026: The configuration file with injection name "{1}" for MBean "{0}" cannot be found.

Cause: The configuration file is missing or the injection name is incorrect.

Action: Verify that the injection name and the configuration file path are properly specified.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46027: The configuration at URI "{0}" cannot be loaded.

Cause: The value for location in the configuration file was invalid.

Action: Verify that the value of location in the configuration file is properly specified.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46028: MBean "{0}" cannot be registered,

Cause: An MBean was already registered with the same name. It should have been removed when the application was either stopped or undeployed.

Action: Examine and correct the errors that resulted when the application was stopped or undeployed, and repeat the stop or undeployment operation.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46029: The configuration file "{0}" for MBean "{1}" cannot be found.

Cause: The value for location in the configuration file was invalid.

Action: Verify that the value of location in the configuration file is properly specified.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46030: failure to register MBean "{0}" during application initialization.

Cause: Registering the MBean during application initialization caused an error.

Action: Use the information from the exception stack trace to determine the cause of the error.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46031: failure to unregister MBean "{0}" during application shutdown.

Cause: Unregistering the MBean during application shutdown caused an error.

Action: Use the information from the exception stack trace to determine the cause of the error.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46032: The RequiredApplicationPermission or RequiredSystemPermission annotation is incorrect.

Cause: The RequiredApplicationPermission or RequiredSystemPermission annotation did not specify a nonempty action array.

Action: Specify a nonempty action array.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46033: The Description annotation on method "{0}" of class "{1}" is incorrect.

Cause: The Description annotation resourceKey was null.

Action: Ensure that the resourceKey for the Description annotation is not null for the method cited in the error message.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46034: No annotation should be put on attribute mutator parameter "{0}".

Cause: The mutator parameter for an attribute has an annotation.

Action: Remove all annotation from the attribute's mutator parameter.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46035: The Description annotations on the mutator and accessor of attribute "{0}" are in conflict.

Cause: Both the mutator and the accessor were annotated. Ideally, only the mutator should be annotated. The message key and the message bundle were not identical on both the mutator and the accessor, and must be if both are annotated.

Action: Either remove the annotation on the accessor or ensure that the message key and the message bundle are identical on both the accessor and the mutator.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46036: OpenType "{0}" cannot be converted to a Class<?> instance.

Cause: The OpenType was not an instance of Class or ParameterizedType or GenericArrayType, and it must be.

Action: Ensure that the OpenType is an instance of Class or ParameterizedType or GenericArrayType.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46037: The class "{0}" cannot be converted to OpenType.

Cause: The custom type was wrong.

Action: Use a custom type that can be converted to OpenType.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46038: There is an OpenType conversion error "{0}".

Cause: An OpenType conversion resulted in an error.

Action: See the information cited within the error message for details about the error.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46039: The ModelMBeanInfo for class "{0}" does not have a Descriptor.

Cause: The ModelMBeanInfo did not have a Descriptor.

Action: Add a Descriptor to the ModelMBeanInfo.
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46040: A key for the resource bundle "{0}" cannot be null.

Cause: The key for the message was null.

Action: Provide a resource bundle key that is not null.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46041: The resource for bundle "{0}" with key "{1}" cannot be found.

Cause: There was no resource found in the resource bundle for the given key.

Action: Add the key to the resource bundle.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46042: The resource in bundle "{0}" for key "{1}" is not a String.

Cause: The resource found for the given key was not a String.

Action: Ensure that the resource is a String.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46043: The JMX Config Session instance passed to the Config MBean Factory is null.

Cause: The JMX Config Session instance passed to the Config MBean Factory was null.

Action: Associate the MBean creation with a valid JMX Config Session instance.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46044: Resource bundle "{0}" cannot be found.

Cause: The resource bundlle was missing.

Action: Provide the resource bundle.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46045: An error occurred while processing MBeanInfo for MBean "{0}".

Cause: The MBeanInfo was not correct.

Action: Use the error information to correct the MBeanInfo.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46046: The ConfigMBean PersistenceManager is not of type DualDataSourcePersistenceManager.

Cause: The PersistenceManager was not of type DualDataSourcePersistenceManager.

Action: Correct the type of the PersistenceManager.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46047: The method "{0}" required by DualDataSourcePersistenceManager cannot be found.

Cause: The required method was missing.

Action: Add the method to the MBean.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46200: federation error: "{0}"

Cause: A federation operation resulted in an error from the federated target.

Action: See the remote exception cited within the error message for details on the error.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46201: The federation namespace "{0}" cannot be found.

Cause: A Namespace that did not exist was specified during a federation operation.

Action: Use a valid federated namespace name.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46202: The domain of ObjectName "{0}" does not start with "{1}".

Cause: An improper domain was used during federation ObjectName processing.

Action: Use the expected federation domain: oracle.as.jmx.federation
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46203: federation namespace handler registration error: "{0}".

Cause: An error occurred while registering a new federation namespace handler.

Action: See the base exception information cited within the error message for details on the error.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46204: namespace handler unregistration error: "{0}".

Cause: An error occurred while unregistering a federation namespace handler.

Action: See the base exception information cited within the error message for details on the error.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46205: error closing connection for "{0}": "{1}".

Cause: An error occurred while closing a federation JMX connector.

Action: See the base exception information cited within the error message for details on the error.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46206: The "{0}" parameter cannot be null.

Cause: A required method parameter was null.

Action: Provide a non-null parameter to the method.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46207: Removing the federation namespace from "{0}" results in an invalid ObjectName.

Cause: Removing the federation prefix resulted in an invalid ObjectName.

Action: Correct the specified ObjectName.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46208: A federated object is not serializable.

Cause: A nonserializable object was encountered during federation serialization.

Action: Make the object serializable.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46209: A federated object is not serializable because a class cannot be found: "{0}".

Cause: A class needed by federation serialization cannot be found.

Action: Verify that the class can be found using the class path.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46210: The object that is being federated is not serializable: "{0}".

Cause: A nonserializable object was encountered during federation serialization.

Action: Make the object serializable.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46211: The FederationMBeanServerImpl constructor is being called incorrectly.

Cause: The constructor for FederationMBeanServerImpl was called more than once, which is not allowed.

Action: Call the constructor for FederationMBeanServerImpl only once.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46212: The operation "{0}" is not supported for namespace "{1}".

Cause: The operation that was invoked is not supported by the namespace.

Action: Change the calling code so that the operation is not invoked.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46213: The remote namespace handler constructor is being called incorrectly.

Cause: The connection information for the remote MBean server was not correct.

Action: Correct the connection information.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46214: Namespace "{0}" cannot be found.

Cause: A namespace that did not exist was specified during a federation operation.

Action: Use a valid federated namespace name.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46215: ObjectName "{0}" is invalid.

Cause: An ObjectName was created with an invalid constructor argument.

Action: Correct the ObjectName constructor argument.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46216: Error unregistering MBean whose ObjectName is "{0}" and implementation class is "{1}"

Cause: See nested exception.

Action: Based on nested exception root cause.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46218: An error occurred while persisting the state for the Config MBean registered under "{0}" and implemented by "{1}"

Cause: See associated exception

Action: Fix issue described by the associated exception
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46219: No registered mapper can convert: "{0}" to an Open MBean Type

Cause: Needed mapper could not be found

Action: Add the required mapper
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46220: Cannot map nongeneric collections to Open MBean Type: "{0}"

Cause: Cannot map nongeneric collections to Open MBean Type

Action: Fix collection type
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46221: JMXFrameworkStateFactory is not initialized. JMXStateFactoryImpl.init() should have been called prior to calling this method

Cause: JMXFrameworkStateFactory in not initialized.

Action: JMXStateFactoryImpl.init() should have been called prior to calling this method.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46222: No such property "{0}" in "{1}"

Cause: Attempted to set a nonexistent property.

Action: Check the name of the property begin set.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46223: Failed to set property "{0}" to value "{1}".

Cause: Could not set the given property.

Action: Check the exception.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46224: No setter for property.

Cause: Could not find the necessary setter method.

Action: Add the needed setter method.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46225: #params for setter != 1.

Cause: Invalid number of parameter for setter method.

Action: Correct the parameter list of the setter call.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46226: Conversion to type "{0}" failed.

Cause: Type conversion failed.

Action: Check the exception.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46227: Cannot find the Config MBeans declaration file {0} in the application.

Cause: The required META-INF/mbeans.xml file is missing from the application.

Action: Add the META-INF/mbeans.xml in the application
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46228: Error processing MBeans associated with mbeans.xml located at: "{0}"

Cause: Format issue, or missing class

Action: Check the exception.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46229: Only one of two security annotations OperationRequiredGlobalSecurityRole and OperationRequiredCustomSecurityGroup can be applied to MBean operation {0}.{1}

Cause: Two security annotations on the MBean operation

Action: Apply only one or none security annotation the the MBean operation
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46230: The following security Annotation(s) cannot be applied to MBean operation {0}.{1}: {2}

Cause: Invalid security annotation(s) on MBean operation

Action: Remove invalid security annotation(s)
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46231: Only one of two security annotations AttributeGetterRequiredGlobalSecurityRole and AttributeGetterRequiredCustomSecurityGroup can be applied to MBean Attribute Getter {0}.{1}

Cause: Two security annotations on the MBean attribute getter

Action: Apply only one or none security annotations to the MBean attribute getter.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46232: The following security Annotation(s) cannot be applied to MBean attribute getter {0}.{1}: {2}

Cause: Invalid security annotation(s) on MBean attribute getter

Action: Remove invalid security annotation(s)
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46233: Only one of two security annotations AttributeSetterRequiredGlobalSecurityRole and AttributeSetterRequiredCustomSecurityGroup can be applied to MBean Attribute Setter {0}.{1}

Cause: Two security annotations on the MBean attribute setter

Action: Apply only one or none security annotations to the MBean attribute setter.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46234: The following security Annotation(s) cannot be applied to MBean attribute setter {0}.{1}: {2}

Cause: Invalid security annotation(s) on MBean attribute setter

Action: Remove invalid security annotation(s)
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46235: Only one of two security annotations MBeanRequiredGlobalSecurityRole and MBeanRequiredCustomSecurityGroup can be applied to MBean interface {0}

Cause: Two security annotations on the MBean interface

Action: Apply only one or none security annotations to the MBean interface.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46236: Do not know how to map nonserializable type: "{0}" to Open MBean Type.

Cause: A type that does not implement Serializable cannot be mapped by the jmx framework

Action: Implement Serializable
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46237: Error while executing ServletContextListener initialization

Cause: See embedded root exception

Action: Fix issue related with embedded root exception
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46238: Cannot map nonserializable type "{0}" to Open MBean Type for mbean interface {1}, attribute {2}.

Cause: A type that does not implement Serializable cannot be mapped by the jmx framework

Action: Implement Serializable
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46239: Cannot map nonserializable type "{0}" to Open MBean Type for mbean interface {1}, the return type of operation {2} .

Cause: A type that does not implement Serializable cannot be mapped by the jmx framework

Action: Implement Serializable
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46240: Cannot map nonserializable type "{0}" to Open MBean Type for mbean interface {1}, parameter {2} of operation {3}.

Cause: A type that does not implement Serializable cannot be mapped by the jmx framework

Action: Implement Serializable
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46241: Error while delivering JMX notification "{0}" to listener "{1}"

Cause: See embedded root exception

Action: Fix issue related with embedded root exception
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46242: Cannot load class "{0}" for MBean operation "{1}" using ClassLoader "{2}"

Cause: See embedded root exception

Action: Fix issue related with embedded root exception
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46243: Cannot find method "{0}" for attribute "{1}"

Cause: See embedded root exception

Action: Fix issue related with embedded root exception
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46244: Error converting annotation "{0}" to descriptor. Could not get value for "{1}"

Cause: See embedded root exception

Action: Fix issue related with embedded root exception
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46245: Error creating ConstraintValidator "{0}" with ClassLoader "{1}"

Cause: See embedded root exception

Action: Fix issue related with embedded root exception
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46246: Error mapping java array or collection of type "{0}" to open type array. Individual element mapping resolved to "{1}"

Cause: See embedded root exception

Action: Fix issue related with embedded root exception
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46247: Cannot load class "{0}" using ClassLoader "{1}"

Cause: See embedded root exception

Action: Fix issue related with embedded root exception
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46248: Error mapping java Map of type "{0}" to open type TabularData. Key mapping resolved to "{1}", and Value mapping resolved to "{2}"

Cause: See embedded root exception

Action: Fix issue related with embedded root exception
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46249: Error mapping java Map entry of TabularType "{0}". Mapped Key instance is {1}", and mapped Value istance is "{2}"

Cause: See embedded root exception

Action: Fix issue related with embedded root exception
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46250: Internal error: the setPersistable() invoked twice on config mbean

Cause: internal error

Action: Contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Programmatic

J2EE JMX-46251: The MBean is no longer registered so no notification is delivered.

Cause: The mbean has been unregistered.

Action: The notification is no longer delivered.
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46252: Error during {0} for MBean {1}

Cause: See nested exception for root cause.

Action: Fix root cause, to ensure that the MBean gets registered.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46300: Class "{0}" is not compatible with the annotation on method "{1}" of class "{2}".

Cause: When a MinValue, MaxValue or LegalValues annotation was used, the class that the annotation applied to did not have either a public static valueOf(String) method or a public constructor with only a String parameter.

Action: Change the class that the MinValue, MaxValue or LegalValues annotation applies to so that it either has a public static valueOf(String) method or a public constructor with only a String parameter.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46301: An object cannot be obtained for the minimum value for "{0}" for method "{1}" of class "{2}".

Cause: An instance of the class that a MinValue annotation applied to was not constructed. The associated IllegalArgumentException indicates the reason.

Action: Examine the associated IllegalArgumentException information to determine what action to take.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46302: An object cannot be obtained for the maximum value for "{0}" for method "{1}" of class "{2}".

Cause: An instance of the class that a MaxValue annotation applied to was not constructed. The associated IllegalArgumentException indicates the reason.

Action: Examine the associated IllegalArgumentException information to determine what action to take.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46303: An object cannot be obtained for the valid value "{0}" for method "{1}" of class "{2}".

Cause: An instance of the class that a LegalValues annotation applied to was not be constructed. The associated IllegalArgumentException indicates the reason.

Action: Examine the associated IllegalArgumentException information to determine what action to take.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46304: The parameters being validated for method "{0}" of class "{1}" based on annotations do not match the method parameter types.

Cause: A constraint declared using the MinValue, MaxValue or LegalValues annotation was being enforced, but the number of arguments passed to the method was wrong.

Action: Change the code that has the call to the method to have the correct number of arguments.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46305: Parameter "{0}" of method "{1}" of class "{2}" is less than the MinValue.

Cause: The value for an attribute or parameter that was annotated with the MinValue annotation failed the minimum value constraint test.

Action: Change the value so that it does not fail the minimum value constraint test or change the annotation.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46306: Parameter "{0}" of method "{1}" of class "{2}" is greater than the MaxValue.

Cause: The value for an attribute or parameter that was annotated with the MaxValue annotation failed the maximum value constraint test.

Action: Change the value so that it does not fail the maximum value constraint test or change the annotation.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46307: Parameter "{0}" of method "{1}" of class "{2}" cannot be compared to the MinValue annotation value.

Cause: The class to which the MinValue annotation applied did not implement the Comparable interface.

Action: Use a different class that implements the Comparable interface or modify the existing class so that it implements the Comparable interface.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46308: Parameter "{0}" of method "{1}" of class "{2}" cannot be compared to the MaxValue annotation value.

Cause: The class to which the MaxValue annotation applied did not implement the Comparable interface.

Action: Use a different class that implements the Comparable interface or modify the existing class so that it implements the Comparable interface.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46309: Parameter "{0}" of method "{1}" of class "{2}" does not match any value in the LegalValues annotation.

Cause: The value for an attribute or parameter that was annotated with the LegalValues annotation did not match any valid value.

Action: Change the value so that it is one of the valid values, or change the annotation.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46310: Parameter "{0}" of method "{1}" of class "{2}" violates the constraint that the LegalValues annotation cannot be used with a MinValue or MaxValue annotation.

Cause: The LegalValues annotation was used at the same location with either a MaxValue or MinValue annotation.

Action: Either use the LegalValues annotation, or use the MaxValue or MinValue annotation.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46311: The value of the MinValue annotation is greater than the value of the MaxValue annotation for parameter "{0}" of method "{1}" of class "{2}".

Cause: The value used for the MinValue annotation was greater than the value used for the MaxValue annotation.

Action: Change the annotations so that the value used for MinValue annotation is less than the value used for the MaxValue annotation.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46312: The type used for parameter "{0}" of method "{1}" of class "{2}" is improper.

Cause: The value passed to an attribute or method parameter that was annotated with the MinValue or MaxValue annotation was not compared with an instance of the class used for the annotation because the type of the value was incorrect.

Action: Use the correct value for the attribute or method call, or change the annotation type.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46313: The delegate MBeanServerConnection cannot be null.

Cause: A PatternBaseDelegationHandler was being constructed without the required MBeanServerConnection argument.

Action: Change the code to supply the required MBeanServerConnection argument.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46314: No handler for ObjectName "{0}" is registered.

Cause: No handler existed for the object name being used.

Action: Register a handler that is appropriate for the object name that is used, or use a different object name.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46315: There is no registered handler to instantiate class "{0}".

Cause: No handler was found to instantiate the class for the object name being used.

Action: Register a handler that is appropriate for the object name that is used, or use a different object name.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46318: An error occurs when registering an MBean with the ObjectName "{0}" and the implementation class "{1}".

Cause: An error occurred when the MBean was being registered.

Action: See the associated Throwable exception information cited within the error message for details on the error.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46319: An error occurs when unregistering an MBean with the ObjectName "{0}" and implementation class "{1}".

Cause: An error occurred when the MBean was being unregistered.

Action: See the associated Throwable exception information cited within the error message for details on the error.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46320: An error occurs when parsing an mbeans.xml file.

Cause: The mbeans.xml file had incorrect XML syntax.

Action: Correct the XML syntax in the mbeans.xml file.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46324: The MBeanServer object parameter for the MBeanServerForwarder is null, or it is equal to the MBeanServerForwarder, or an MBeanServer object is already set.

Cause: The MBeanServer argument was not valid.

Action: Correct the MBeanServer argument.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46329: Error when parsing {0}.

Cause: The META-INF/mbeans.xml is empty or has syntax error.

Action: Correct the META-INF/mbeans.xml with the correct syntax.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46330: Cannot find any jmx config mbeans in parsed mbeans.xml file

Cause: No config mbeans declared in META-INF/mbeans.xml in the application.

Action: Declare the config mbeans class, interface, config files in META-INF/mbeans.xml.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46331: The numbers of configuration files and persistence managers for the mbean {0} in mbeans.xml do not match

Cause: The injectNames for configuration files and persistence managers in mbeans.xml is inconsistent.

Action: Update the mbeans.xml to use correct configuration files and persistence managers.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46332: MBean "{0}" cannot be registered.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46333: Cannot find config file {0} in the application for mbean {1}

Cause: The location of config file is not correct or the config file is missing in the application.

Action: Fix the application.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46334: This helper class "{0}" only supports a single config file per MBean. However the MBean "{1}" specifed "{2}" config files.

Cause: Only one confile file par MBean is supported from this helper class

Action: Fix the calling code
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46335: MBean attribute access denied. MBean: {0} {1} for attribute {2} Detail: {3}

Cause: Security check failed.

Action: Access the MBean attribute with the user in right role or group.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46336: MBean operation access denied. MBean: {0} Operation: {1} Detail: {2}

Cause: Security check failed.

Action: Access the MBean operation with the user in right role or group.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46337: RegisterMBean denied: MBean: {0} Detail: {1}

Cause: Security check failed.

Action: RegisterMBean is allowed to the user ADMIN role.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46338: DeregisterMBean denied: MBean: {0} Detail: {1}

Cause: Security check failed.

Action: DeegisterMBean is allowed to the user ADMIN role.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46339: Cannot find any jmx runtime mbeans in parsed mbeans.xml file

Cause: No runtime mbeans declared in META-INF/mbeans.xml in the application.

Action: Declare the config mbeans class, interface, config files in META-INF/mbeans.xml.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46340: EntityResolver "{0}" failed to retrieve mbeans.xml xsd "{1}"

Cause: Either XSD is invalid, or proper Java Security Permissions have not been granted to JMX Framework jars if Security Manager is turned on.

Action: Verify xsd in mbeans.xml file, and ensure proper Security Permissions are granted to JMX Framework jars if Security Manager is turned on.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46341: Failed to create application stripe Id. Missing key: {0}, MBean: {1}

Cause: The key is missing from MBean ObjectName.

Action: Check MBean interface security annotation, make sure the key is available.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46342: Failed to remove old backup of config file {0}

Cause: unknown.

Action: regular backup config directory may help in this case.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46343: Failed to rename old config file {0} to backup file {1}

Cause: unknown.

Action: regular backup config directory may help in this case.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46344: Access denied. Current subject: {0}; Required app roles: {1}

Cause: Current user is not member of any required application roles.

Action: Try again with the user that is member of any of required application roles.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46345: Internal error: invalid security object. type {0}, value {1}

Cause: unknown.

Action: Contact support.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46346: EntityResolver "{0}" failed to retrieve the JMX Framework configuration xsd "{1}"

Cause: Either XSD is invalid, or proper Java Security Permissions have not been granted to JMX Framework jars if Security Manager is turned on.

Action: Verify xsd in JMX Framework configuration file, and ensure proper Security Permissions are granted to JMX Framework jars if Security Manager is turned on.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46347: An error occurs when parsing the JMX Framework configuration file.

Cause: The JMX Framework configuration file had incorrect XML syntax.

Action: Correct the JMX Framework configuration file XML syntax.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46348: Unexpected xml tag {0}, when parsing the JMX framework configuration file.

Cause: Invalid JMX Framework configuration file.

Action: Make sure your JMX Framework Configuration file is valid.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46349: Missing JMX Framework configuration file

Cause: Cannot find the JMX Framework configuration file.

Action: Ensure that you either specify a valid configuration location, or that the default configuration is included in jmxspi.jar under the META-INF directory
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46350: Error parsing JMX Framework Configuration. Invalid value "{0}" for attribute "{1}" defined in XML element "{2}".

Cause: The value for the attribute is not valid

Action: Please correct the value in the JMX Framework configuration file.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46351: Invalid ID "{0}". No internal MBean interceptor is associated with that ID.

Cause: The wrong value was specified.

Action: Please correct the value in the JMX Framework configuration file.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46352: Invalid URL for custom MBean interceptor "{0}" jar location "{1}"

Cause: The wrong value was specified in the JMX Framework configuration file for the MBean interceptor jar location.

Action: Please correct the value in the JMX Framework configuration file.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46353: Custom MBean interceptor "{0}" jar file cannot be found at the specified location "{1}"

Cause: Missing jar file, or incorrect location specified in the JMX Framework configuration file.

Action: Please correct the value in the JMX Framework configuration file, or make sure the jar file is present
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46354: An error was raised while instantiating the JMX Framework MBean interceptor chain.

Cause: See root exception.

Action: Please correct the issue associated with the root exception.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46355: An error occured while initializing the JMX Framework MBean level logging interceptor.

Cause: See root exception.

Action: Please correct the issue associated with the root exception.
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46356: Logging prior to call getAttribute for MBean "{0}" and attribute "{1}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46357: Call to getAttribute for MBean "{0}" and attribute "{1}" was successful and returned "{2}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46358: Error while calling getAttribute for MBean "{0}" and attribute "{1}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46359: Call to preRegister for MBean "{0}" was successful. Original MBean name was "{1}". MBean was registered in MBeanServer "{2}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46360: Call to postRegister for MBean "{0}" was successful. Registration status was "{1}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46361: Error while calling preRegister for MBean "{0}" and MBeanServer "{1}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46362: Calling postDeregister for MBean "{0}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46363: Error while calling preDeregister for MBean "{0}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46364: Call to preDeregister for MBean "{0}" was successful.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46365: Error while calling postRegister for MBean "{0}" with registration status "{1}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46366: Error while calling postDeregister for MBean "{0}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46367: Logging prior to call getAttributes for MBean "{0}" and attributes "{1}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46368: Call to getAttributes for MBean "{0}" and attributes "{1}" was successful and returned "{2}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46369: Error while calling getAttributes for MBean "{0}" and attributes "{1}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46370: Logging prior to call setAttribute for MBean "{0}" and attribute "{1}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46371: Call to setAttribute for MBean "{0}" and attribute "{1}" was successful.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46372: Error while calling setAttribute for MBean "{0}" and attribute "{1}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46373: Logging prior to call setAttributes for MBean "{0}" and attributes "{1}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46374: Call to setAttributes for MBean "{0}" and attributes "{1}" was successful and returned "{2}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46375: Error while calling setAttributes for MBean "{0}" and attributes "{1}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46376: Logging prior to calling operation "{0}" for MBean "{1}" and parameters "{2}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46377: Call to operation "{0}" for MBean "{1}" and parameters "{2}" was successful and returned "{3}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46378: Error while calling operation "{0}" for MBean "{1}" and parameters "{2}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46379: Logging prior to calling getMBeanInfo for MBean "{0}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46380: Call to getMBeanInfo for MBean "{0}" was successful and returned "{1}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46381: Error while calling getMBeanInfo for MBean "{0}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46382: JMX Framework MBean Logging interceptor intialized with log level "{0}", MBean pattern "{1}", call trace set to "{2}" and dump MBeanInfo set to "{3}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46383: Error while merging configuration for files "{0}" and "{1}" with ConfigMerger instance {2}.

Cause: See nested exception for root cause.

Action: Fix root cause.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46400: The Config MBean jar file "{0}" does not exist.

Cause: The configuration MBeans jar file specified in the "location" attribute of the "config-mbeans" tag did not exist

Action: Correct the path to the configuration MBeans jar file.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46401: Attribute "{0}" is unexpected.

Cause: An unexpected attribute was encountered in the MBeans XML file.

Action: Remove the unexpected attribute.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46402: Tag "{0}" is unexpected.

Cause: An unexpected tag was encountered in the MBeans XML file.

Action: Remove the unexpected tag.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46403: Tag "{0}" is missing the required attribute "{1}"

Cause: A required attribute was missing from the MBeans XML file.

Action: Add the missing attribute.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46404: Tag "{0}" is missing the required tag "{1}"

Cause: A required tag is missing from the MBeans XML file.

Action: Add the missing tag.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46406: Class "{0}" does not exist.

Cause: A jmx-config-mbean class or management-interface specified in the MBeans XML file did not exist.

Action: Correct the class reference.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46407: Multiple persistence managers are not allowed for single configuration file.

Cause: Multiple persistence managers were specified for a single configuration file.

Action: Specifiy only one persistence manager.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46408: An invalid location is defined in mbeans.xml for the config file: "{0}"

Cause: An invalid jmx-config-mbean config-file path was encountered in the MBeans XML file.

Action: Correct the path to the configuration file.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46409: The Runtime MBean jar file "{0}" does not exist.

Cause: The Runtime MBeans jar file specified in the "location" attribute of the "runtime-mbeans" tag did not exist

Action: Correct the path to the Runtime MBeans jar file.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46410: When specifying multiple "{0}" elements, the injection-name attribute is required

Cause: Your MBean must include a name as part of the @Injection annotations to match resources defined in mbeans.xml

Action: Correct the @Inject annotations in your MBean to reference resources defined in your mbeans.xml
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46502: internal session error: "{0}".

Cause: A session operation resulted in an error.

Action: See the base exception information cited within the error message for details on the error.
Level: 1

Type: WARNING

Impact: Other

J2EE JMX-46503: The "{0}" call to the MBean with ObjectName "{1}" is not made in the context of a JMX configuration session.

Cause: The call that was made needed to be made in the context of a JMX configuration session.

Action: Create a JMX configuration session and then make the call.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46504: A call to commit or roll back the sesssion is not made by the owner of the JMX configuration session.

Cause: The call was not made by the owner of the JMX configuration session.

Action: This call must be made by the owner of the JMX configuration session.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46505: The Config MBean implementation object "{0}" for ObjectName "{1}" does not implement MBeanServerSupport.

Cause: The Config MBean implementation did not implement MBeanServerSupport.

Action: Correct the Config MBean implementation so that it implements MBeanServerSupport.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46506: The parent MBean for "{0}" cannot be found.

Cause: The MBean specified a parent MBean that was missing.

Action: Correct the MBean implementation so that it specifies the correct parent.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46507: The ObjectName "{0}" is specified when adding or removing a notification listener in a JMX configuration session.

Cause: Specifying ObjectName when adding or removing a notification listener is not supported in a JMX configuration session.

Action: Add or remove the notification listener without specifying ObjectName.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46508: The createMBean method is called for the ObjectName "{0}".

Cause: An attempt was made to create a ConfigMBean using the createMBean method.

Action: Use the registerMBean method.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46509: MBean custom persistence method error for ObjectName"{0}": "{1}"

Cause: An MBean custom persistence operation resulted in an error.

Action: See the base exception information cited within the error message for details on the error.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46510: JAXB persistence method error: "{0}"

Cause: An MBean JAXB Persistence operation resulted in an error.

Action: See the base exception information cited within the error message for details on the error.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46511: MBean validation error prior to committing for ObjectName"{0}": "{1}"

Cause: An error occurred during validation of an MBean before committing it.

Action: See the base exception information cited within the error message for details on the error.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46512: MBean session life-cycle callback error for ObjectName "{0}": "{1}"

Cause: This error occurred when the MBean session life-cycle callback was called.

Action: See the base exception information cited within the error message for details on the error.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46513: unexpected error: "{0}"

Cause: An unexpected error occurred.

Action: See the base exception information cited within the error message for details on the error.
Level: 1

Type: WARNING

Impact: Other

J2EE JMX-46514: An MBean of type "{0}" implements Persistable directly or implements an unknown subclass of Persistable.

Cause: The MBean must not implement Persistable directly and must not implement an unknown subclass of Persistable.

Action: Remove the use of Persistable.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46515: A configuration session already exists.

Cause: A configuration session was started when one was already active.

Action: Do not attempt to start a second configuration session. Use the prevously started configuration session.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46516: configuration session start error: "{0}".

Cause: There was a failure to start the JMX configuration session due to an error.

Action: See the base exception information cited within the error message for details on the error.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46517: configuration session commit error: "{0}".

Cause: There was a failure to commit the JMX configuration session due to an error.

Action: See the base exception information cited within the error message for details on the error.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46518: configuration session roll back error: "{0}".

Cause: There was a failure to roll back the JMX configuration session due to an error.

Action: See the base exception information cited within the error message for details on the error.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46519: cannot lock MBean: "{0}"

Cause: The MBean was in special domain oracle.as.jmx or was a delegate MBean.

Action: Provide an MBean whose object name is not in the special domain oracle.as.jmx and is not a delegate MBean.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46520: MBean "{0}" cannot be found in the session MBean server.

Cause: The MBean was not registered in the session MBean server.

Action: Register the MBean.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46600: The groupby attribute "{0}" is invalid.

Cause: The groupby attribute or property specified did not exist.

Action: Ensure that the groupby attribute specified refers to an MBean attribute or property.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46601: An aggregation attribute or property such as groupbyAttrs, aggOps, or aggAttrs is null.

Cause: An aggregation attribute or property was null.

Action: Ensure that the specified aggregation attribute or property exists.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46602: The aggregation operation "{0}" is invalid.

Cause: An invalid aggregation operator was specified.

Action: Verify that the aggregation operator specified is among OPERATION_AVG through OPERATION_GROUPBY defined in oracle.as.jmx.framework.bulkoperations.BulkOperationsMBean.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46603: The groupby key "{0}" cannot be used for aggregation.

Cause: Aggregation was incorrectly specified on a groupby attribute or property.

Action: Specify either aggregation key or groupby key, but not both, on the attribute or property.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46604: BulkOperationsMBean NamespaceHelper instance creation error: "{0}"

Cause: The provided MBean server is invalid.

Action: Correct the MBean server that is being provided. See the base exception information cited within the error message for details on the error.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46605: Parameter count ("{0}") does not match mbean count ("{1}")

Cause: The number of parameter arrays passed in does not match the number of mbeans that should be invoked

Action: Ensure that the correct number of parameter arrays are being passed.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46606: non-numeric attribute {0} in aggregation

Cause: BukpOperationMBean Aggregation operation requires all attributes to have numeric values

Action: Do not use attributes with non-numeric values when using the aggregation operation provided by the BulkOperationMBean
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46607: In BukpOperationMBean Aggregation operation, aggOps and aggAttrs need to be the same length

Cause: In BukpOperationMBean Aggregation operation, aggOps and aggAttrs need to be the same length

Action: Ensure that aggOps and aggAttrs are the same length
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46608: A "null" value was passed to a BulkOperationsMBean method as part of an ObjectName[] parameter. We will ignore that value, as it would cause all MBeans to be selected. If this is the intended behavior use new ObjectName("*:*") in place of null

Cause: This could be due to some user code logic error, and not intended.

Action: If this is the intended behavior use new ObjectName("*:*") in place of null
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-47000: Property "{0}" is not set.

Cause: The expected property was not set.

Action: Add the expected property to the mbeans.xml file.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-47001: A JAXB error occurred during unmarshalling.

Cause: Some data in the xml file is invalid.

Action: Use the JAXB error information to correct the xml file.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-47002: A JAXB error occurred during marshalling of "{0}".

Cause: Some data to be marshalled is invalid.

Action: Correct the data to be marshalled.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-47003: An error occurred during initializion of the JAXB context using the contextpath "{0}"

Cause: The contextpath in the mbeans.xml file is invalid.

Action: Correct the contextpath.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-47004: The JAXB Object "{0}" has been loaded

Cause:

Action:
Level: 16

Type: TRACE

Impact: Programmatic

J2EE JMX-47005: THE JAXB Object "{0}" has been persisted.

Cause:

Action:
Level: 16

Type: TRACE

Impact: Programmatic

J2EE JMX-47006: Persistance manager "{0}" does not implement "{1}".

Cause: Persistance manager implementation inheritance incorrect.

Action: Correct the persistance manager implementation.
Level: 1

Type: WARNING

Impact: Programmatic

51 J2EE JOC-00001 to J2EE JOC-00859

J2EE JOC-00001: exception caught in the load callback

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00002: exception caught in the verify callback

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00003: internal error in the cache

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00004: error in the disk cache

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00005: error locking the disk cache

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00006: The metadata file for the disk cache is corrupted.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00007: incorrect object ID

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00008: invalid handle

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00009: invalid object

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00010: negative number

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00011: negative reference count

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00012: A group cannot belong to itself.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00013: cannot find loader object

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00014: An exception occurred while waiting for a condition.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00015: The specified event is not supported.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00016: The SSL configuration is invalid, either keystore or storepass cannot be found.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Security

J2EE JOC-00017: The cache is full.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00018: The region is full.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00019: The cache is not available.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00020: The named cache is not available.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00021: The disk cache is not available.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00022: The caller must have ownership of the object before executing this method.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00023: An inconsistency in the use of a group is detected.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00024: One of the specified arguments is not valid.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00025: The specified group is not valid.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00026: The handle being used is not valid.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00027: The object accessed is not valid.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00028: A loading conflict is occurring, such as trying to update an object while it is being loaded.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00029: The cache message system is offline.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00030: The object is not a pool.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00031: There are currently no objects available from the pool.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00032: The object cannot be retrieved.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00033: This functionality is not implemented.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00034: The current object is null.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00035: The object name or group name is null.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00036: An object already exists with the same name.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00037: cannot find the following object

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00038: the object or group is not synchronized:

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00039: cannot find region

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00040: cannot find group

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00041: A failure is occurring during the requested operation at a remote cache.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00042: The object or file cannot be created.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Requests/Responses

J2EE JOC-00043: base exception:

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00044: An exception is occurring in the method.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00045: The following object is already defined:

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00046: A DiskObject cannot be updated.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00047: This object is synchronized, getOwnership must be called before executing this method on:

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00048: This synchronized object has been destroyed. This operation is no longer valid for:

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00049: This object already exists in the cache as a distributed disk object. It cannot be redefined as a local object:

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00050: The following remote cache cannot be found:

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00051: unable to destroy named cache

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00052: A named cache name cannot contain a region separator.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00053: cannot add index

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00054: cannot remove index

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00055: The index MessageKeys.EXPression is null.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00056: The index name is null.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00057: error evaluating index MessageKeys.EXPression

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00058: distributed cache initialization failure

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00600: group communication internal error

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00601: invalid destination address

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00602: group communication exception, base exception:

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00603: invalid channel state

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00604: The view information is empty.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00605: The view is null.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00606: The local host address cannot be found.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00607: The configured network port is in use.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Ports

J2EE JOC-00608: The socket cannot be initialized.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00609: invalid parameter

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00610: null pointer

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00611: empty reply information

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Requests/Responses

J2EE JOC-00612: no network connection to

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00613: invalid view information

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00614: Group communication layer is terminated or not initialized properly.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00615: Transferring files is not supported in object stream mode, switch to HTTP transfer mode and try again.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00616: The InputStream is not valid.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00617: The HTTP request is not valid.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Requests/Responses

J2EE JOC-00618: The socket input stream is closed.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00619: unable to instantiate SSL provider:

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Security

J2EE JOC-00620: cannot find SSL provider:

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Security

J2EE JOC-00621: is not an instance of java.security.Provider.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Security

J2EE JOC-00622: invalid SSL Configuration information

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Security

J2EE JOC-00623: SSLServerSocket creation failure

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Security

J2EE JOC-00624: SSLSocket creation failure

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Security

J2EE JOC-00700: The file name cannot be null.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Files

J2EE JOC-00701: The file does not exist.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Files

J2EE JOC-00702: invalid parameters passed in

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Files

J2EE JOC-00703: This operation is not allowed.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Files

J2EE JOC-00704: internal error

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Files

J2EE JOC-00800: The maximum group communication initialization retry limit is being exceeded: {0}

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00801: group communication client initialization error

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00802: unable to generate a global unique ID for a group communication member

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00803: unexpected EOF during read

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00804: timeout while registering a new client: {0} seconds

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00805: no connection for member: {0}

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00806: unable to parse network address

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00807: unable to create a new view

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00808: unable to serialize object: {0}

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00809: failure during packet processing

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Requests/Responses

J2EE JOC-00810: distributor initialization timeout: {0}

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00811: unexpected interrupt while waiting for a read/write lock

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00812: timeout after waiting for a packet delivery confirmation for {0} seconds

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00813: invalid SSL provider, name: {0}

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Security

J2EE JOC-00814: unable to create SSL provider, name: {0}

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Security

J2EE JOC-00815: unknown SSL provider, name: {0}

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Security

J2EE JOC-00816: unable to create SSL server socket on port: {0}

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Security

J2EE JOC-00817: unable to initialize SSL Manager

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Security

J2EE JOC-00818: invalid SSL configuration file

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Security

J2EE JOC-00819: The SSL configuration file is malformed. {0}

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Security

J2EE JOC-00820: Group communication has been terminated or is not available.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00821: The delivery cannot be confirmed due to a distributor failover scenario.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00822: The specified instance name: {0} is in use.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00823: unable to contact the packet-distributor at {0}

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00824: unable to join group at {0} due to unexpected I/O problems

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00825: no response from the packet-distributor at {0}

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00826: invalid group communication member, ID: {0}

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00827: receiving an invalid group view, unable to join group

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00828: unable to serialize an outgoing message

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00829: unable to send a packet to the packet-distributor at {0} after {1} retries

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00830: The delivery cannot be confirmed due to an unexpected I/O error.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00831: unable to process an incoming packet: {0}

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Requests/Responses

J2EE JOC-00832: Group communication service is terminated unexpectedly while waiting for a packet delivery confirmation

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00833: unexpected interruption while waiting for a packet delivery confirmation

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00834: unable to restore a sequence token for handling total-order delivery

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00835: no listener for the packet-distributor is defined in the group communication configuration

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00836: unable to contact the group coordinator at {0} due to unexpected error

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00837: unable to run as a dedicated group coordinator

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00838: unable to initialize an EndPointConnection due to unexpected I/O error

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00839: The specified group member alias or ID: {0} does not exist in view {1}.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00840: unable to automatically assign a listener address for the packet-distributor

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00841: An HTTP handler cannot be created. The I/O stream is invalid.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Requests/Responses

J2EE JOC-00842: The size of an incoming HTTP packet has exceeded the default maximum limit of {0}.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Requests/Responses

J2EE JOC-00843: The HTTP header is shorter than the specified length: {0}.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Requests/Responses

J2EE JOC-00844: The header length is missing from an incoming HTTP packet.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Requests/Responses

J2EE JOC-00845: The file length from an incoming HTTP packet is shorter than expected.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Requests/Responses

J2EE JOC-00846: The file length from an incoming HTTP packet is {0} bytes shorter than expected.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Requests/Responses

J2EE JOC-00847: invalid HTTP header

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Requests/Responses

J2EE JOC-00848: The packet-distributor is unable to open a server socket at {0}.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00849: unable to initialize an UDP multicast channel at {0}

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00850: invalid group communication packet type: {0}

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Requests/Responses

J2EE JOC-00851: unable to deserialize a group communication packet

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Data

J2EE JOC-00852: unable to create a receipt holder for tracking confirmation

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00853: unable to parse a sequence token for handling total-order delivery

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00854: unexpected group view management error

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00855: missing mandatory packet-distributor address for client-mode configuration

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00856: Neither the listener address nor the packet-distributor location is defined with the label {0}.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00857: No packet-distributor listener address is defined with the label {0}.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00858: The connection is being closed.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Network

J2EE JOC-00859: The port {0} is unavailable, the packet-distributor cannot be started.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Ports

52 J2EE JSP-00002 to J2EE JSP-00302

J2EE JSP-00002: an internal JSP error occurred. Additional information follows: {0}.

Cause: JSP encountered an unexpected situation. This may be a bug in the JSP servlet.

Action: Contact Oracle Support Services. Oracle Support Services may recommend increasing the log level to FINER to help understand the situation.
Level: 1

Type: WARNING

Impact: Requests/Responses

J2EE JSP-00003: unable to fully process the TLD cache for the following reason: {0}.

Cause: An error occured while the Tag Library Descriptor cache was created or accessed.

Action: Check the TLD for validity and fix the TLD, or remove it if it is not used in the application. If the logging level is set to FINER more information should be available in the exception contained in the error message.
Level: 1

Type: WARNING

Impact: Deployment

J2EE JSP-00005: unable to send the following error in the response. Response code: {0} Error message: {1}.

Cause: An exception occurred that prevented the error status from being sent in the response.

Action: See the exception cited in the error message. It may be necessary to increase the logging level to FINER to see the exception.
Level: 1

Type: WARNING

Impact: Requests/Responses

J2EE JSP-00006: unable to prepare or access an auxiliary object: {0} {1}.

Cause: The auxiliary object required for tracking JSP page dependencies was not read in or created.

Action: Recompile the page after checking factors that impact file reading such as disk corruption, permissions, and file handles.
Level: 1

Type: NOTIFICATION

Impact: Files

J2EE JSP-00007: cannot find the message resource file, {0}, in the server to report error messages.

Cause: Due to a missing error message resource bundle, the underlying error message was not presented.

Action: Contact Oracle Support Services.
Level: 1

Type: NOTIFICATION

Impact: Installation

J2EE JSP-00008: unable to dispatch JSP page: {0}.

Cause: An error prevented the dispatching of the JSP page.

Action: Correct the error described in this logged message.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

J2EE JSP-00009: unable to return the following error in the response: {0}.

Cause: An input-output error occurred while trying to write an error message to the servlet response stream.

Action: The logged message contains the error message that could not be returned in the response, and the associated exception. It may be necessary to increase the logging level to FINER to see the exception. Scan the log files for additional error messages that may reveal the root cause of this problem.
Level: 1

Type: WARNING

Impact: Files

J2EE JSP-00010: building the cache named {0}.

Cause: Started building the Tag Library Descriptor persistent cache.

Action: none
Level: 1

Type: NOTIFICATION

Impact: Deployment

J2EE JSP-00011: Invalid JSP tag library location. {0} does not exist or is not a directory.

Cause: An invalid or nonexistent directory name was supplied as a tag library location.

Action: Correct the directory name and insure that it is available.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JSP-00012: obtaining application resources.

Cause: Finished obtaining current Tag Library Descriptors for this application.

Action: none
Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00013: the initialization of TLD cache is complete.

Cause: Initialization of the Tag Library Descriptor persistent cache is completed.

Action: none
Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00014: the number of listeners in TLDs visible to this application is {0}

Cause: The number of listener elements found in the Tag Library Descriptors visible to the applications was reported.

Action: none
Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00015: starting to read the persistent TLD cache named {0}.

Cause: The Tag Library Descriptor persistent cache was read.

Action: none
Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00016: completing cache update

Cause: Updating the Tag Library Descriptor persistent cache was completed.

Action: See error message.
Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00017: inserting TLD at: {0}

Cause: The TLD at the given URL was inserted into the TLD persistent cache.

Action: none
Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00018: applying update to TLD at: {0}

Cause: The TLD at the given URL was updated in the TLD persistent cache.

Action: none
Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00019: completing processing of TLD persistent cache

Cause: The processing of this TLD persistent cache is finished.

Action: none
Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00020: writing TLD persistent cache to file system

Cause: Finished writing out the Tag Library Descriptor Persistent Cache.

Action: See error message.
Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00021: URL for entry is {0}.

Cause: Processed a TLD at the following given URL.

Action: none
Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00022: loading external TLD with uri element, {0}, from JAR {1}.

Cause: Loaded TLD from the location external to the application given in the message text.

Action: none
Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00023: loading application TLD with uri element, {0}, from location {1}.

Cause: Loaded TLD from the application location given in the message text.

Action: See error message.
Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00024: loading TLD accessible via the name, {0}, from {1}

Cause: Loaded tag library descriptor at the following location for access via file or jar name.

Action: See error message.
Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00025: finding listener, {0}, in TLD

Cause: The name of a listener element found in a Tag Library Descriptor visible to the application is supplied.

Action: none
Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00026: missing required uri element in external TLD: {0}

Cause: Encountered a Tag Library Descriptor with an invalid or missing uri-element where one is required. For example, global tag libraries and those extrenal to the application must have URI elements.

Action: Supply the URI element in the TLD file or move the tag library to the application level.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JSP-00027: unable to parse TLD file: {0}

Cause: The TLD at the given location could not be parsed.

Action: Check for invalid XML syntax, especially unbalanced angle brackets or start and end tags.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JSP-00028: duplicate URI element, {0}, in TLD, {1}, and TLD, {2}

Cause: More than one tag library descriptor encountered using the same URI element. URI elements visible to the application must be unique.

Action: Change one of the uri element values or exclude one of the tag libraries from the this application.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JSP-00029: unable to obtain cache key: {0}

Cause: A corrupted cache key was encountered in the TLD cache.

Action: Stop the server, delete the TLD cache files from the application's persistence directory and from the global directory, tldcache and restart the application server. Contact Oracle Support Services if this problem persists.
Level: 1

Type: WARNING

Impact: Deployment

J2EE JSP-00030: unable to obtain the JSP parameters

Cause: A unknown problem was encountered when attempting to initialize JSP configuration parameters.

Action: Verify the XML syntax in orion-web.xml, especially in the attributes of ojsp-init element if used. Verify the syntax of any init-parameters supplied to the JspServlet in web.xml or global-web-applications.xml. Then redeploy the application. If that fails, or if errors were found in the global-web-applciation.xml, restart the server. If the problem persists contact Oracle Support Services
Level: 1

Type: WARNING

Impact: Configuration

J2EE JSP-00031: refreshing the cache named {0}.

Cause: Started refreshing the Tag Library Descriptor cache.

Action: none
Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00032: looking for global resource at {0}.

Cause: The global Tag Library Descriptors were sought in the location or locations cited in the error message.

Action: none
Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00033: unable to process an invalid or unsupported TLD version: {0}

Cause: An invalid or unsupported value of the taglib element's attribute, version, element was supplied.

Action: The taglib element is the root element for all TLD's. The element's attribute, version, must be either 2.0 or 2.1.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JSP-00034: loading cachedConfigTable from persistent cache

Cause: The internal configuration data structure was loaded from the persistent Tag Libary Descriptor cache.

Action: none
Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00035: unable to load changeAwareClassLoader class. Shared libraries from web-app and enclosing app will not be scanned for TLDs

Cause: Loading of ChangeAwareClassLoader failed

Action: none
Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00036: unbable to obtain Tag Library listeners: {0}

Cause: An error was encountered while obtaining Tag Library listeners during the parsing of Tag Library Descriptors.

Action: Verify that classes given in the listener-classes element are available in the application's class path. Check for general XML syntax (i.e., unmatched quotes or start/end tags) in the application's TLD's.
Level: 1

Type: WARNING

Impact: Deployment

J2EE JSP-00037: cannot load tag library {0} specified in web.xml

Cause: A tag library defined in the application's web.xml file was not loaded.

Action: Verify that the taglib-uri and taglib-location are correctly formatted and point to valid values, and that the tag library implementations classes are available to the application.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JSP-00038: error preparing dependency file for tag file:

Cause: An error was encountered while writing or preparing the dependency file for a tag file.

Action: Recompile the page that accesses the tag file after checking factors that impact file writing such as disk space, permissions, and file handles.
Level: 1

Type: WARNING

Impact: Files

J2EE JSP-00039: invalid tag file: {0}. File must end with .tag or .tagx and start with /WEB-INF/tags or /META-INF/tags.

Cause: Encountered a tag file path that is an invalid or non-existent location.

Action: Correct the tagfile-path element value by ensuring that it ends with either .tag or .tagx, and starts with either /WEB-INF/tags or /META-INF/tags.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JSP-00040: duplicate tag name : {0}. TLD is invalid

Cause: A tag name that was used in more than one Tag Library Descriptor was visible to the application and caused an error.

Action: Tag names must be unique. Change the duplicate name in that tag or tag file element.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JSP-00041: The value {0} is invalid for main mode.

Cause: An invalid value for the main mode was detected.

Action: Valid values for the main mode are recompile, reload and justrun.
Level: 1

Type: WARNING

Impact: Configuration

J2EE JSP-00042: The value {0} is invalid for debug.

Cause: An invalid JSR45 debug parameter was specified.

Action: Valid values for debug are none, file and class.
Level: 1

Type: WARNING

Impact: Configuration

J2EE JSP-00043: The value {0} is invalid for tags reuse.

Cause: An invalid tags reuse parameter was specified.

Action: Valid values for tag resuse are compiletime, compiletime-with-release and none.
Level: 1

Type: WARNING

Impact: Configuration

J2EE JSP-00044: error invoking the following JSP tag life-cycle method: {0}

Cause: An internal error occured. The JSP runtime failed to execute a method provided by the Oracle JSF Injection Provider. The JSP page in which the error occured will not be serviced.

Action: Contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JSP-00045: unable to scan annotation for tag {0}: {1}

Cause: The tag implementation class given in the error text could not be scanned for annotations.

Action: See the error cited in the error message to determine what action is required.
Level: 1

Type: WARNING

Impact: Files

J2EE JSP-00046: Unable to load class {0} while scanning for annotated JSP tags.

Cause: The tag class for annotations cited in the error message was not scanned. The class appeared to be missing, or was unloadable.

Action: Make sure that the missing class is available in the application class path. Verify that the class file was generated with a jdk version that supports annotations.
Level: 1

Type: WARNING

Impact: Files

J2EE JSP-00047: unable to scan annotation {0}. It is not a JSP tag.

Cause: The class to be scanned does not implement the JspTag interface or cannot be loaded.

Action: Make sure the class is available in the application classpath and that it implements the javax.servlet.jsp.tagext.JspTag interface.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JSP-00048: annotation scanning is incomplete: {0}

Cause: Scanning for annotations in the Tag Library Descriptors, visible to the application, was not completed.

Action: Verify that the class is availble in the applications classpath. If so, check application server log files for problems such as out of memory, file permissions, network access.
Level: 1

Type: WARNING

Impact: Files

J2EE JSP-00049: reading implicit.tld file at {0}

Cause:

Action:
Level: 16

Type: TRACE

Impact: Files

J2EE JSP-00050: Parameter {0} is no longer supported as of Oracle Containers for J2EE 11g. The parameter is ignored.

Cause: An application attempted to use the parameter cited in the error message that was desupported as of release 11G.

Action: You can avoid this message by removing the given parameter.
Level: 1

Type: WARNING

Impact: Configuration

J2EE JSP-00051: unable to write an auxiliary object during the page compilation: {0} {1}.

Cause: The auxiliary object required for tracking the JSP page dependencies could not be written to a file.

Action: Recompile the page after investigating the factors that impact file writing such as disk space, permissions, and file handles.
Level: 1

Type: NOTIFICATION

Impact: Files

J2EE JSP-00052: Using the ProviderURI {0} that is returned from custom provider for processing requests.

Cause: An application-specific provider was registered and used.

Action: none
Level: 1

Type: TRACE

Impact: Configuration

J2EE JSP-00053: The value {0} is an invalid value for generic servlet mode.

Cause: An invalid parameter for the generic servlet mode was specified.

Action: Use a valid parameter value. They include shared, single, none, and single_and_persist.
Level: 1

Type: WARNING

Impact: Configuration

J2EE JSP-00054: Unable to retrieve HttpApp object through ThreadState.

Cause: An application that did not use the default OC4J HttpApplication object failed to supply its own application context object.

Action: Supply the application context or allow the use of the default one.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JSP-00055: Setting JSP:Config parameter {0} = {1}

Cause: The JSP:Config parameter cited in the message was set.

Action: none
Level: 32

Type: TRACE

Impact: Configuration

J2EE JSP-00056: The web.xml at {0} is version 2.3 but has a <jsp-config> element. Ignoring <jsp-config> element.

Cause: Web.xml version 2.3 does not include support for <jsp-config>

Action: Either remove the <jsp-config> element or upgrade the web.xml to version 2.4 or higher
Level: 1

Type: WARNING

Impact: Other

J2EE JSP-00057: unable to determined the last-modified date of the file at path, {0}.

Cause: This is usually caused by an IO error. However this error may related to something that happened before this instanceof OC4J started. This has been known to happen if at some point two processes attempted to write to the same file at the same time. This error can also occur if the file was last modified within one second of EPOCH (at 0 hour on January 1, 1970), in this case it should be ignored.

Action: Verify that the file is not corrupted. If it is not, this error can be ignored. You may use the touch command, in unix, to update the last modified date of the file to prevent subsequent logging of this error. If the file is corrupted attempt to determine the cause of the corruption and fix it, or Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

J2EE JSP-00058: error attemping to parse web.xml at {0}.

Cause: Error parsing the web.xml file located at the path location listed in the log message.

Action: Attempt to fix the error in the web.xml file base on the information contained in the log message.
Level: 1

Type: WARNING

Impact: Deployment

J2EE JSP-00059: unable to inject a resource.

Cause: The exception cited in the error message occurred when the JSP page was processed.

Action: Read the exception cited in the error message to understand the cause. If no exception is shown, increase the log level to FINER.
Level: 16

Type: TRACE

Impact: Requests/Responses

J2EE JSP-00060: unable to parse the tld with the following url: {0}. Error details follow: {1}.

Cause: Failed to parse the tag specified in the error message.

Action: Read the error details cited in the error message and attempt to fix the offending tag, or remove it is it is not needed.
Level: 16

Type: TRACE

Impact: Requests/Responses

J2EE JSP-00061: there is a JSP error in file {0} at line {1}. The error is: {2}, in {3}.

Cause: A JspParse Exception was encountered.

Action: Examine the content of the error message which indicates the nature and location of the error. Then fix the error.
Level: 16

Type: TRACE

Impact: Requests/Responses

J2EE JSP-00062: unable to get the TLD document associated to file {0} at line {1}. The error is: {3}.

Cause: Internal error. Inconsistent gathering of performance statistics

Action: Examine the content of the error message which indicates the nature and location of the error. Attempt to fix the error. If that does not work, contact Oracle Support Services and give them the full error message.
Level: 16

Type: TRACE

Impact: Requests/Responses

J2EE JSP-00063: unable to read the jar file named {0}.

Cause: An input-ouput exception occured while attempting to read the jar file specified in the message.

Action: Examine the content of the error message which indicates the nature and location of the error. Attempt to fix the error. If that does not work, contact Oracle Support Services and give them the full error message.
Level: 16

Type: TRACE

Impact: Requests/Responses

J2EE JSP-00064: unable to obtain URI because of an XML parsing exception in file, {0} at element, {1}.

Cause: An exception occured in the XML parser while parsing for a URI.

Action: Examine the content of the error message which contains at least the name of the relevant file and most likely the name of the relevant XML element. Attempt to fix the error. If that does not work, contact Oracle Support Services and give them the full error message.
Level: 16

Type: TRACE

Impact: Requests/Responses

J2EE JSP-00065: unable to process the file at {0} due to an input-ouput exception.

Cause: An input-output exception prevented the processing of the file named in the log message.

Action: Examine the content of the error message which indicates the nature of the error as well as the location of the file involved. Attempt to fix the error. If that does not work, contact Oracle Support Services and give them the full error message.
Level: 16

Type: TRACE

Impact: Requests/Responses

J2EE JSP-00066: unable to find class named {0} in resource {1}.

Cause: The JSP runtime could not find the class specified in the message in the resource also specified in the message.

Action: Verify the resource in question and attempt to fix the error. If that does not work, contact Oracle Support Services and give them the full error message.
Level: 16

Type: TRACE

Impact: Requests/Responses

J2EE JSP-00067: unable to read optional data.

Cause: The JSP runtime encountered a java.io.OptionalDataException.

Action: Read the full error message and consult the Javadoc on OptionalDataException to understand the problem and attempt to fix it. If that does not work, contact Oracle Support Services and give them the full error message.
Level: 16

Type: TRACE

Impact: Requests/Responses

J2EE JSP-00068: invalid taglib uri: {0}, unless non taglib namespace was intended in a JSP document.

Cause: An invalid taglib uri was specified.

Action: Fix the taglib attributes in your jsp.
Level: 1

Type: NOTIFICATION

Impact: Configuration

J2EE JSP-00069: Name space, {0}, also known as {1} will override name space {2}

Cause: The namespace definition in the last tld defining the namespace overrided any previous definition of that namespace.

Action: See error message.
Level: 1

Type: WARNING

Impact: Other

J2EE JSP-00070: an unlikely, but generally harmless, situation has been detected. Additional information follows: {0}.

Cause: JSP encountered an rare situation. This should not cause any adverse effect on yor application.

Action: If this occurs in the absence of other errors, this is most likely a benign situation, if accompanied by other error messages, this may held diagnose the root cause of the problem reported by the other error messages. You may Contact Oracle Support Services to help us improve the product in future releases. Oracle Support Services may recommend increasing the log level to FINER to help understand the situation.
Level: 1

Type: WARNING

Impact: Requests/Responses

J2EE JSP-00101: Inconsistent use of the DMS (statistics aggregation) framework. The problem occured in application, {0}, for this uri: {1}. {2}

Cause: Internal error. Inconsistent gathering of performance statistics

Action: Examine the error message to determine which statistics are inconsistent; those statistics should not be trusted. Contact Oracle Support Services and give them the full error message.
Level: 1

Type: ERROR

Impact: Performance

J2EE JSP-00111: the Oracle DMS framework is unavailable.

Cause: The JSP servlet could not find the Oracle DMS classes.

Action: If using a third-party application server, the DMS functionality will simply not be available. If using an Oracle Application Server, this message indicates that there is something wrong with the installation. In that case, contact Oracle Support Services and give them the full error message.
Level: 1

Type: WARNING

Impact: Installation

J2EE JSP-00300: unable to access osgi.syspath, {0}, even though it exists.

Cause: There is a problem with the path corresponding to System property osgi.sypath.

Action: Check that the path is valid, unlocked, and that WebSphere has read/write permissions for it.
Level: 1

Type: ERROR

Impact: Files

J2EE JSP-00301: unable to extract the local classpath field.

Cause: There is a problem extracting the local class path from the WebSphere class loader.

Action: Contact Oracle Support Services and ask for a patch if this prevents ojsp.next from functioning normally.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JSP-00302: unable to determine the osgi pluggin classpath.

Cause: There is a problem assembling the osgi plugin class path.

Action: Contact Oracle Support Services and ask for a patch if this prevents ojsp.next from functioning normally.
Level: 1

Type: ERROR

Impact: Programmatic

53 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-25091: View object {0} has no primary entity

Cause: An attempt was made to get the primary post state of a view row that has no entity usages.

Action: Only call this method on a view row with one or more entity usages
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25092: Programmatically accessible view object definition {0} is not found.

Cause: An attempt has been made to find a view definition using a short name and no corresponding custom or standard object can be found.

Action: Use a shortname that corresponds to the name of a custom object in a registered custom object base package or elsethe name of a standard object that has been registered to be programmatically accessible.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25150: The method {1} on class {0} is not permitted.

Cause: An attempt was made within an untrusted expression to call a method not on the list of allowed methods.

Action: Add the method to the list of allowed methods in adf-config.xml
Level: 1

Type: ERROR

Impact: Security

JBO-25151: Accessing the {1} property on class {0} is not permitted.

Cause: An attempt was made within an untrusted expression to access a property not allowed by methods on the list.

Action: Add the get and set methods corresponding to the property to the list of allowed methods in adf-config.xml
Level: 1

Type: ERROR

Impact: Security

JBO-25152: Calling the constructor for class {0} is not permitted.

Cause: An attempt was made within an untrusted expression to call a constructor not on the list of allowed constructors.

Action: Add the constructor to the list of allowed constructors in adf-config.xml.
Level: 1

Type: ERROR

Impact: Security

JBO-25153: Calling the {1} method on class {0} is not permitted.

Cause: An attempt was made within an untrusted expression to call a constructor not on the list of allowed constructors.

Action: Use an alternate method.
Level: 1

Type: ERROR

Impact: Security

JBO-25154: Calling the {1} function is not permitted.

Cause: An attempt was made within an untrusted expression to call a method which is on the list of blacklisted methods on scripts.

Action: Rename the method, or call it from a trusted context.
Level: 1

Type: ERROR

Impact: Security

JBO-25155: Defining an additional method is not permitted.

Cause: An attempt was made within an untrusted expression to define an additional method.

Action: Create the same logic without the use of an embedded method, or mark the script as trusted.
Level: 1

Type: ERROR

Impact: Security

JBO-25156: Defining an additional class is not permitted.

Cause: An attempt was made within an untrusted expression to define an additional class.

Action: Create the same logic without the use of an embedded class, or mark the script as trusted.
Level: 1

Type: ERROR

Impact: Security

JBO-25157: Calling the {1} method on class {0} is not permitted when used in a static context.

Cause: An attempt was made within an untrusted expression to call a method which is blacklisted when used in a static context.

Action: Instead use the method on an instance of the class.
Level: 1

Type: ERROR

Impact: Security

JBO-25158: Accessing the {1} property is not permitted.

Cause: An attempt was made within an untrusted expression to use a property on the list of blacklisted properties.

Action: Instead access the property with an allowed method.
Level: 1

Type: ERROR

Impact: Security

JBO-25159: Accessing the {1} property, when used in a static context on class {0}, is not permitted.

Cause: An attempt was made within an untrusted expression to use a property in a static context on the list of blacklisted properties.

Action: Instead access the property with an allowed method, or use in an instance context.
Level: 1

Type: ERROR

Impact: Security

JBO-25160: Defining a method pointer is not permitted.

Cause: An attempt was made within an untrusted expression to define a method pointer.

Action: Create the same logic without the use of a method pointer, or mark the script as trusted.
Level: 1

Type: ERROR

Impact: Security

JBO-25161: Calling the {1} function is not permitted.

Cause: An attempt was made within an untrusted expression to call a method which is not allowed on scripts.

Action: Rename the method, or call it from a trusted context.
Level: 1

Type: ERROR

Impact: Security

JBO-25162: Using the Java field operator (.@) is not permitted.

Cause: An attempt was made within an untrusted expression to directly access a Java field via '.@'.

Action: Create the same logic without the use of the '.@' operator, or mark the script as trusted.
Level: 1

Type: ERROR

Impact: Security

JBO-25170: Expression timed out.

Cause: An untrusted expression exceeded the maximum time allotted for a run.

Action: Break the task up into multiple tasks, increase the timeout value, or mark the script as trusted.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25171: Expression exceeded the maximum number of new view instances ({0}).

Cause: An untrusted expression exceeded an allowed use of resources.

Action: Change your expression to use fewer resources.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25180: Exception in expression "{0}" expression {1} : {2}

Cause: An exception has occurred within a Transient Expression.

Action: Examine the details to find the root cause, and modify the expression to avoid the root exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25181: Exception in expression "{0}" recalc expression {1} : {2}

Cause: An exception has occurred within a Recalc Expression.

Action: Examine the details to find the root cause, and modify the Expression to avoid the root exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25182: Exception in expression "{0}" validation rule {1} : {2}

Cause: An exception has occurred within a Validation Rule expression.

Action: Examine the details to find the root cause, and modify the expression to avoid the root exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25183: Exception in expression "{0}" trigger {1} : {2}

Cause: An exception has occurred within a Trigger expression.

Action: Examine the details to find the root cause, and modify the expression to avoid the root exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25184: Exception in expression "{0}" object function {1} : {2}

Cause: An exception has occurred within an Object Fucntion.

Action: Examine the details to find the root cause, and modify the function to avoid the root exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25185: Exception in expression "{0}" global function {1} : {2}

Cause: An exception has occurred within an Object Fucntion.

Action: Examine the details to find the root cause, and modify the function to avoid the root exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25186: Exception in expression "{0}" of unknown type {1} : {2}

Cause: An exception has occurred within an expression of unknown type.

Action: Examine the details to find the root cause, and modify the expression to avoid the root exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-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: Assocation 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 assocation. 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 assocation 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 assocation.
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-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 'availabale' 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 non empty 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-56008: Mapped value for name {0} not found in viewobject {1} attribute {2}.

Cause: Can't find mapped value for one given name.

Action: Add neccessary name/value to PropertySet.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-56009: Mapped name for value {0} not found in viewobject {1} attribute {2}.

Cause: Can't find mapped value for one given value.

Action: Add neccessary name/value to PropertySet.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-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

54 JPS-00001 to JPS-90642

JPS-00001: The method {0} is not supported.

Cause: An unsupported method was used.

Action: This operation is not supported. It cannot be used.
Level: 1

Type: WARNING

Impact: Requests/Responses

JPS-00003: The HTTP response callback is null.

Cause: HTTP response callback was null.

Action: Check the log files and provide a valid HTTP response callback.
Level: 1

Type: ERROR

Impact: Session

JPS-00004: The HTTP response is null.

Cause: HTTP response was null.

Action: Check the log files and provide a valid HTTP response.
Level: 1

Type: ERROR

Impact: Session

JPS-00005: HTTP request callback is null.

Cause: HTTP request callback was null.

Action: Check the log files and provide a valid HTTP request callback.
Level: 1

Type: ERROR

Impact: Session

JPS-00006: The HTTP request is null.

Cause: HTTP request was null.

Action: Check the log files and provide a valid HTTP request.
Level: 1

Type: ERROR

Impact: Session

JPS-00007: Cannot find an application ID.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Session

JPS-00008: The application ID {0} is invalid.

Cause: Application ID was NULL.

Action: Provide a valid application ID.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00009: The subject is read-only, and it cannot modified.

Cause: Attempted to modify a read-only subject.

Action: A read-only subject cannot be modified.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-00010: A JPS context is not available in the callback handler.

Cause: A context was not available from callback handler.

Action: Check configuration in jps-config.xml.
Level: 1

Type: ERROR

Impact: Session

JPS-00011: The service instance {0} already exists.

Cause: The named service instance was already in use.

Action: Use a different name for this service instance.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00012: The service instance {0} is missing.

Cause: The service instance with the name {0} was not found.

Action: Ensure the service instance name is present in the file jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00013: The login module {0} already exists.

Cause: The login module with the name {0} was already present.

Action: Ensure the login module name is correct.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00014: The login module with {0} is missing.

Cause: The login module with the name {0} did not exist.

Action: Ensure the login module name is correct.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00015: All available service instance names are already in use.

Cause: All service instance names were in use.

Action: Remove unwanted service instances from jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00016: All available service provider names are already in use.

Cause: All service provider names were in use.

Action: Remove unwanted service providers form jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00017: The LDAP type is invalid.

Cause: An invalid LDAP type was specified.

Action: Provide a valid LDAP type. Valid types are XML, OID, ACTIVE_DIRECTORY, IPLANET and OVD. See the documentation for details.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00018: The keystore path {0} is null or invalid.

Cause: Keystore path was null.

Action: Provide a valid keystore path.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00019: The key type {0} is not supported.

Cause: Invalid key type was provided.

Action: Provide a valid key type.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00020: LDAP URL {0} is null or invalid.

Cause: Invalid or null LDAP URL was provided.

Action: Provide a valid LDAP URL.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00021: An Object named {0} does not exist.

Cause: Object with the name {0} did not exist.

Action: Verify that the object name is valid and exists.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00022: Callback handler missing for this login module request.

Cause: The callback handler was null.

Action: Provide an appropriate callback handler to invoke this login module.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-00023: The callback used for this operation has no HTTP request value.

Cause: The callback did not have a request method.

Action: Verify that the callback is initialized with the correct HTTP request value.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-00024: The callback used for this operation has no digest response object value.

Cause: The callback did not have any digest response object.

Action: Verify that the callback is initialized with the correct digest response value.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-00025: The {0} subscriber {1} from the HTTP header is different from the subscriber configured by the identity store as {2}.

Cause: Found a subscriber mismatch.

Action: Check the identity store subscriber configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00026: The value {0} is invalid for the application {1}.

Cause: An invalid value was provided for this application.

Action: Provide the correct value for the application.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-00027: internal error {0}

Cause: Internal system error was found.

Action: See the log files or contact the system administrator.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-00028: The property runas.mode is deprecated and supported only for backward compatibility.

Cause: The property runas.mode has been deprecated.

Action: Use instead the oracle.security.jps.jaas.mode property in jps-config.xml.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

JPS-00029: The audit service initialization failed for the application {0}. Reason {1}.

Cause: Audit service failed.

Action: Check the audit service configuration in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00030: Cannot complete exist operation.

Cause: Could not find entity.

Action: Verify that the entity exist.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00031: Cannot load the required class {0}. Reason {1}.

Cause: Could not load a class.

Action: Ensure the class is in the class path.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-00032: The migration cannot write directly to the specified LDAP identity store; specify an alternate LDIF file to create.

Cause: Could not perform a direct LDAP write operation.

Action: See the log files for details.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-00033: The direct policy store should be XML-based, and it can be specified as an XML file or as an input stream.

Cause: The policy store specification was invalid.

Action: Check the policy store specification.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-00034: Cannot find the application context.

Cause: A context was not available for the application.

Action: Check the jps-config.xml configuration.
Level: 1

Type: ERROR

Impact: Session

JPS-00035: The WSS digest value {0} is invalid.

Cause: Found missing WSS digest value in callback.

Action: Verify that the callback has a valid WSS digest value.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-00036: The WSS digest nonce {0} is invalid.

Cause: Found missing WSS digest nonce in callback.

Action: Verify that the callback has a valid WSS digest nonce.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-00037: The WSS digest created {0} is invalid.

Cause: Found missing WSS digest created in callback.

Action: Verify that the callback has a valid WSS digest created.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-00038: Cannot create or retrieve a ContextFactory.

Cause: Cannot retrieve or create a JPS ContextFactory.

Action: Check jps-config.xml for correctness.
Level: 1

Type: ERROR

Impact: Other

JPS-00039: The service instance with provider {0} and name {1} is missing.

Cause: A service instance configuration was missing.

Action: Check the service instance configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00040: The JPS audit component events file {0} is missing or invalid.

Cause: Cannot find the audit component events file.

Action: Make sure the audit component events file is available and valid.
Level: 1

Type: ERROR

Impact: Other

JPS-00041: Cannot load the JpsAdminService class.

Cause: The class JpsAdminService or a dependent class could not be loaded.

Action: Review the cause to resolve the error.
Level: 1

Type: ERROR

Impact: Other

JPS-00042: The LDAP connection pool provider {0} is not valid; the supported providers are JNDI or IDM. If unspecified, it defaults to UCP/JNDI provider.

Cause: The connection.pool.provider.type property value was invalid.

Action: Configure a supported connection.pool.provider.type value, or use the default provider by not setting the connection.pool.provider.type property.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00043: Cannot establish an LDAP connection after {0} attempts.

Cause: The connection could not be established.

Action: Check the LDAP configuration.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-00044: The LDAP URL format must be ldap://<host>:<port> or ldaps://<host>:<port>; but found {0}.

Cause: Invalid LDAP URL format was found.

Action: The format of the LDAP URL must be ldap://<host>:<port> or ldaps://<host>:<port> format.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00045: The LDAP principal {0} is invalid.

Cause: The LDAP principal was invalid.

Action: Provide a correct value for principal.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00046: The LDAP credential is invalid.

Cause: The LDAP credential was invalid.

Action: Provide the correct credential value.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00047: The Subject parameter cannot be null.

Cause: The supplied parameter was null.

Action: Check the Subject parameter supplied in the method call.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-00048: Principals are missing in the Subject.

Cause: No principals were not found in the Subject.

Action: Verify that the supplied Subject contains principals.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-00049: The authenticated user principal is missing in the Subject.

Cause: Authenticated user principal was not found in the Subject.

Action: Verify that the supplied Subject contains an authenticated user principal.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-00050: Invalid Subject parameter supplied.

Cause: The Subject contained an anonymous user principal and an authenticated user principal.

Action: Ensure that the Subject does not contain the anonymous user principal.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-00051: The oracle.security.jps.config property not set.

Cause: The oracle.security.jps.config property was not set.

Action: Set the oracle.security.jps.config property to an appropriate value.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-00052: Failed to Refresh Audit Service with new configuration.

Cause: Failed to reload the audit configuration.

Action: Check the audit configuration file to see if the lastest changes are valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00053: Component events file is missing for {0} at {1}.

Cause: The component events file for the given component type was missing.

Action: Verify that the properties set for the component files are correct in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00054: Failed to create the auditor for {0}.

Cause: Failed to create the auditor object.

Action: Ensure that the component events file is not missing or corrupt and check the log files additional errors.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00055: Bootstrap credential store service is not initialized for the service configurator.

Cause: The bootstrap credetial store service was not initialised.

Action: Make sure the bootstrap credetial store service is initialized before any other services.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-00056: Failed to create identity store service instance {0}. Reason: {1}.

Cause: Failed to create identity store service instance {0}. Cause: {1}.

Action: Check the log files to resolve the error.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00057: Failed to set OutputProperty for indent or XML encoding. Reason {0}.

Cause: Failed to setOutputProperty for indent or XML encoding. Cause: {0}

Action: Check the XML Transformer implementation.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00058: Failed to set XML output encoding to UTF-8 in OutputStreamWriter. Reason {0}.

Cause: Failed to set XML output encoding to UTF-8 in OutputStreamWriter. Cause: {0}

Action: Check the JDK OutputStreamWriter supported encodings.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00059: The specified enterprise identity is null or invalid.

Cause: An enterprise identity provided was null or invalid

Action: Provide a valid enterprise identity value.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00060: The specified enterprise identity {0} is not found in identity store.

Cause: The specified enterprise identity {0} was not found in the identity store.

Action: Provide a valid enterprise identity value.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00061: No platform specific factory is found to create the platform principals. Check errors in the log files.

Cause: No platform specific factory was found to create platform principals.

Action: Check the log files for the errors.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00062: No identity store associate with policy store found.

Cause: No identity store associate with policy store found

Action: Contact system administrator
Level: 1

Type: ERROR

Impact: Configuration

JPS-00063: Jps servlet filter creation failed. Reason: {0}.

Cause: Jps Servlet Filter creation failed

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Configuration

JPS-00064: Jps ejb interceptor creation failed. Reason: {0}.

Cause: Jps EJB Interceptor creation failed

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Configuration

JPS-00065: Jps platform factory creation failed. Reason: {0}.

Cause: Jps Platform Factory creation failed

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Configuration

JPS-00066: Jps property value retrieval failed. Reason: {0}.

Cause: Jps property value retrieval failed

Action: Check the property values in jps configuration files
Level: 1

Type: ERROR

Impact: Configuration

JPS-00068: Ldap security checking failed. The LDAP url should start with ldaps and oracle.ldap.wltloc system property should be set. Reason : {0}.

Cause: Is LDAP secure failed

Action: Contact system administrator
Level: 1

Type: ERROR

Impact: Security

JPS-00069: Ldap credential store provider missing.

Cause: LDAP credential provider missed

Action: Ensure ldap credential store provider is configured
Level: 1

Type: ERROR

Impact: Security

JPS-00070: Ldap policy store provider missing.

Cause: LDAP policy store provider missing

Action: Ensure ldap policy store is configured
Level: 1

Type: ERROR

Impact: Security

JPS-00071: Ldap bootstrap credential retrieval failed. Reason:{0}.

Cause: Retrieval of bootstrap credential failed

Action: Check the credential store configuration for credential types, maps and key
Level: 1

Type: ERROR

Impact: Security

JPS-00072: Policy schema upgrade not required. Store Schema version {0} is compatible to the seed schema version {1}

Cause: Comparison of policy schema version in the store against to seed schema version.

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00073: Policy store schema version not found

Cause: Trying to determine version of the policy schema in the store

Action: Contact Oracle Support Services.
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00074: Policy store schema version {0} is less than the latest schema version {1}, upgraded the Policy store schema to latest version.

Cause: Comparison of the Policy schema version in the store against the schema to seed

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00075: Unable to query Policy store schema version under "{0}", Cause {1}

Cause: Query of Policy schema from the store failed

Action: Confirm the Policy store schema containers are present in the store
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00076: Policy schema version set to {0}

Cause: Version of the policy schema has been set in the store

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00077: Setting version of policy schema in the store failed. Cause {0}

Cause: Unexpected error occurred while setting the version of the Policy schema in the store

Action: Confirm the container is present in the store and caller has sufficient privileges to perform this operation
Level: 1

Type: ERROR

Impact: Configuration

JPS-00078: Credential store schema upgrade not required. Store Schema version {0} is compatible to the seed schema version {1}

Cause: Comparison of Credential schema version in the store against the seed schema version.

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00079: Credential store schema version not found

Cause: Check if the DN exists, or if the Credential Store schema version attribute is present at the specificied location

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00080: Credential store schema version {0} is less than the latest schema version {1}, upgraded the Credential store schema to latest version.

Cause: Comparison of the Credential schema version in the store against the schema to seed

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00081: Unable to query Credential store schema version under "{0}", Cause {1}

Cause: Query of Credential schema from store store failed

Action: Confirm the Credential store schema container in the store is present
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00082: Credential schema version set to {0}

Cause: Version of the credential schema has been set in the store

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00083: Setting version of credential schema in the store failed. Cause {0}

Cause: Unexpected error occurred while setting the version of the credential schema in the store

Action: Confirm the container is present in the store and caller has sufficient privileges to perform this operation
Level: 1

Type: ERROR

Impact: Configuration

JPS-00084: IOException raised from FileLocker {0}.

Cause: Closing IO objects in FileLocker

Action: Check the file system for access privileges and disk space availability.
Level: 1

Type: WARNING

Impact: Other

JPS-00085: OID version is unavailable.

Cause: OID version is unavalable

Action: Check the ldap url against the server type passed.
Level: 1

Type: WARNING

Impact: Other

JPS-00086: Error while encoding search string: {0} to UTF-8 encoding

Cause: Unable to encode user string to UTF-8 encoding

Action: Check the search string.
Level: 1

Type: WARNING

Impact: Other

JPS-00087: The subject parameter is null.

Cause: The subject parameter is null

Action: Make sure the subject parameter is not null
Level: 1

Type: ERROR

Impact: Security

JPS-00088: The user name parameter is null.

Cause: The user name parameter is null

Action: Make sure the user name parameter is not null
Level: 1

Type: ERROR

Impact: Security

JPS-00089: The subject from the current AccessControlContext is null.

Cause: No subject is associated with the current AccessControlContext.

Action: Ensure that the subject is associated with the current AccessControlContext.
Level: 1

Type: ERROR

Impact: Security

JPS-00090: Failed to create policy store service instance {0}. Cause: {1}.

Cause: Failed to create policy store service instance {0}. Cause: {1}.

Action: Check the log files to resolve the error.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00091: No {0} available.

Cause: No {0} available.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-00092: The ldap service was null.

Cause: The ldap service was null.

Action: Ensure the ldap service is not null.
Level: 1

Type: ERROR

Impact: Security

JPS-00093: Class {0} was not type of {1}.

Cause: Class {0} was not type of {1}.

Action: Ensure class name is correct.
Level: 1

Type: ERROR

Impact: Security

JPS-00094: Failed to parse digest response.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

JPS-00095: {0} system properties not set.

Cause: System properties {0} not set.

Action: Set the system properties.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00096: No {0} defined for {1}.

Cause: No {0} defined for {1}.

Action: Defined the specified object.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00097: {0} missing in message : {1}.

Cause: {0} missing in message : {1}.

Action: Check the input.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00098: Duplicate error message.

Cause: Duplicate error message.

Action: Check the input.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00099: {0} already exists.

Cause: {0} already exists.

Action: Check the input.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00100: Failed to instantiate {0}.

Cause: Failed to instantiate {0}.

Action: Check the object type.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00101: {0} not match {1}.

Cause: {0} not match with {1}.

Action: Check the object type.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00102: Unhandled entry {0}

Cause: Unhandled entry {0}.

Action: Check the entry.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00103: Invalid login module type {0}.

Cause: Invalid login module type {0}.

Action: Use valid login module type.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00104: System policy does not exist.

Cause: System policy does not exist.

Action: Ensure system policy exist.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00105: Failed to create temp dir {0}.

Cause: Failed to create temp dir {0}.

Action: Check the log for more details.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00106: InputStream has no more data to read.

Cause: InputStream had no more data to read.

Action: Check the log for more details.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00107: {0} invoked.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-00108: Event {0} was ignored.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-00109: Overwriting credentials is allowed at application credential store migration with Weblogic server running in {0} and system property {1} set to {2}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-00110: Failed to decode {0}. Reason {1}.

Cause: Failed to decode {0}. Reason: {1}.

Action: Check log for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-00111: Current timer interval ({0} seconds) is too short.

Cause: Current timer interval ({0} seconds) is too short.

Action: Please set a longer interval in the configuration file.
Level: 1

Type: WARNING

Impact: Security

JPS-00112: Set property {0} to value {1}.

Cause: Set property {0} to value {1}.

Action: Check log for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-00113: Failed to parse condition {0}. Reason {1}.

Cause: Failed to arse condition {0}. Reason {1}.

Action: Check log for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-00114: Failed to load data file {0}.

Cause: Failed to load data file {0}.

Action: Please check file location.
Level: 1

Type: WARNING

Impact: Security

JPS-00115: Failed to modify JPS Schema.

Cause: Failed to modify JPS Schema.

Action: Check log for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-00116: Failed to read JPS Schema.

Cause: Failed to read JPS Schema.

Action: Check log for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-00117: Failed to delete System Policy name {0}. Reason {1}.

Cause: Failed to delete System Policy name {0}. Reason {1}.

Action: Check log for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-00118: {0} not found.

Cause: {0} not found.

Action: Check log for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-00119: Failed to create ResourceEntry name: {0}, action: {1}, cause: {2}.

Cause: Failed to create ResourceEntry name: {0}, action: {1}, cause: {2}.

Action: Check log for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-00120: Failed to seed attribute {0}, ldap object class {1}.

Cause: Failed to seed attribute {0}, ldap object class {1}.

Action: Check the LDAP configuration to resolve the error.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00121: Failed to parse LDIF record {0}. Reason: {1}.

Cause: Failed to parse LDIF record {0}. Reason: {1}.

Action: Check the LDAP configuration to resolve the error.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00122: Farm DN {0} does not exist.

Cause: Farm DN {0} does not exist.

Action: Ensure farm DN is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00123: RDN {0} not found under farm {1}.

Cause: RDN {0} not found under farm {1}.

Action: Check LDAP server type.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00124: {0} was not supported.

Cause: {0} was not supported.

Action: Use a valid type.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00125: Property {0} was null.

Cause: Property {0} was null.

Action: Ensure property is not null.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-00126: Overwriting credentials is not allowed at application credential store migration with Weblogic server running in {0} and system property {1} set to {2}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-00127: Failed to create igf service instance {0}. Reason: {1}.

Cause: Failed to create igf service instance {0}. Cause: {1}.

Action: Check the log files to resolve the error.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00128: Keystore schema upgrade not required. Store Schema version {0} is compatible to the seed schema version {1}

Cause: Comparison of Keystore schema version in the store against the seed schema version.

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00129: Keystore schema version not found

Cause: Check if the DN exists, or if the Keystore schema version attribute is present at the specificied location

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00130: Keystore schema version {0} is less than the latest schema version {1}, upgraded the Keystore schema to latest version.

Cause: Comparison of the Keystore schema version in the store against the schema to seed

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00131: Unable to query Keystore schema version under "{0}", Cause {1}

Cause: Query of Keystore schema from store store failed

Action: Confirm the Keystore schema container in the store is present
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00132: Keystore schema version set to {0}

Cause: Version of the keystore schema has been set in the store

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00133: Setting version of keystore schema in the store failed. Cause {0}

Cause: Unexpected error occurred while setting the version of the keystore schema in the store

Action: Confirm the container is present in the store and caller has sufficient privileges to perform this operation
Level: 1

Type: ERROR

Impact: Configuration

JPS-00134: The offline deployment staging directory {0} does not exist.

Cause: The cause may be that the product was installed inproperly.

Action: Install the product properly.
Level: 1

Type: ERROR

Impact: Deployment

JPS-00135: Exception occurs on saving ear file {0}.

Cause: The cause may be due to bad ear file or insufficient permission.

Action: Check the ear file and the file system permissiion.
Level: 1

Type: ERROR

Impact: Deployment

JPS-00136: Exception occurs on saving offline deployment property file in application directory {0}.

Cause: The cause may be due to insufficient permission.

Action: Check the file system permissiion.
Level: 1

Type: ERROR

Impact: Deployment

JPS-00137: Found offline deployed app {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

JPS-00138: Exception occurs on opening the staging application in {0}.

Cause: This may be caused by bad .ear file on the disk.

Action: Check the .ear file on the disk.
Level: 1

Type: ERROR

Impact: Deployment

JPS-00139: Exception occurs on loading the property file of the staging application in {0}.

Cause: Failed to open the property file.

Action: Check the property file on the disk.
Level: 1

Type: ERROR

Impact: Deployment

JPS-00140: Failed to delete the staging app {0}. Migration flag file created.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

JPS-00141: Cannot handle offline deployed application due to the required system property {0} is not set.

Cause: The cause may be that the product was installed inproperly.

Action: Install the product properly.
Level: 1

Type: ERROR

Impact: Deployment

JPS-00142: No opss-application.xml found.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

JPS-00143: Error on migrating security artifacts.

Cause: Error on migrating security artifacts.

Action: Check security related files in your application, such as opss-application.xml, jazn-data.xml, cwallet.sso, etc.
Level: 1

Type: ERROR

Impact: Deployment

JPS-00144: Error on opening ear file {0}.

Cause: Error on opening ear file.

Action: Check the ear file.
Level: 1

Type: ERROR

Impact: Deployment

JPS-00145: Found no installed application at {0}.

Cause: Found no installed application at {0}.

Action: Check the installed application at {0}.
Level: 1

Type: WARNING

Impact: Deployment

JPS-00146: Failed to create identity store service instance {0}. Reason: the service does not enable the virtualize flag, but references other service instance.

Cause: Failed to create identity store service instance {0}. Cause: the service does not enable the virtualize flag, but references other service instance.

Action: Either make the virtualize flag true, or directly define the ldap configuration instead of using service reference
Level: 1

Type: WARNING

Impact: Configuration

JPS-00147: Keystore re-association not supported.

Cause: Configuration of key store was not suitable for re-association.

Action: Confirm the key store configuration is updated.
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00148: Jps JBoss signing key seeded.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-00149: Jps JBoss signing key already exists. Seeding ignored.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-00150: Key 1 and Key 2 are no longer supported for system parameter -Djps.subject.cache.key, please use key 4 (default), 3, or 5 (fastest).

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-00151: Audit store instantiation failure, type: {0} reason: {1}

Cause: Audit metadata store failed to be instantiated, type: {0}, reason: {1}

Action: Check the audit service configuration in jps-config.xml.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00152: Component not registered, name: {0}

Cause: Component {0} not registered and no audit configuration found.

Action: Register component with audit service.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00153: The principal {0} is invalid.

Cause: The principal is invalid.

Action: Provide a correct value for principal.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00154: The rule condition {0} is invalid.

Cause: The rule condition function is invalid.

Action: Provide a correct value for rule condition function.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00155: Audit metadata store is not instantiated in audit service.

Cause: Audit metadata store is not instantiated.

Action: Verify that the audit store properties for audit service are correct in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00156: Audit metadata store type {0} is invalid

Cause: Audit metadata store type {0} is invalid

Action: Check the audit service configuration in jps-config.xml.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00157: The DN {0} is invalid

Cause: The DN {0} is invalid

Action: Check the given DN value.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00158: Audit store schema upgrade not required. Store Schema version {0} is compatible to the seed schema version {1}

Cause: Comparison of Audit schema version in the store against the seed schema version.

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00159: Audit store schema version not found

Cause: Check if the DN exists, or if the Audit Store schema version attribute is present at the specificied location

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00160: Audit store schema version {0} is less than the latest schema version {1}, upgraded the Credential store schema to latest version.

Cause: Comparison of the Audit schema version in the store against the schema to seed

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00161: Unable to query Audit store schema version under "{0}", Cause {1}

Cause: Query of Audit schema from store store failed

Action: Confirm the Audit store schema container in the store is present
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00162: Audit schema version set to {0}

Cause: Version of the audit schema has been set in the store

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00163: Setting version of audit schema in the store failed. Cause {0}

Cause: Unexpected error occurred while setting the version of the audit schema in the store

Action: Confirm the container is present in the store and caller has sufficient privileges to perform this operation
Level: 1

Type: ERROR

Impact: Configuration

JPS-00164: Audit store re-association not supported.

Cause: Configuration of audit store was not suitable for re-association.

Action: Confirm the audit store configuration is updated.
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00165: Failed to reload component {0} runtime policy with error message {1}.

Cause: Failed to reload component runtime policy.

Action: Check component run policy and custom fitler preset definition.
Level: 1

Type: ERROR

Impact: Other

JPS-00167: Failed to validate the xml content. {0} Location: {1}.

Cause: Failed to validate the xml content. {0} Location: {1}.

Action: Fix the invalid xml elements according to the xsd schema definition.
Level: 1

Type: WARNING

Impact: Security

JPS-00168: OID server version {0} is not supported

Cause: OID server version {0} is not supported

Action: Check the support matrix.
Level: 1

Type: ERROR

Impact: Other

JPS-00169: Failed to get server log directory. Reason: {0}.

Cause: Failed to get server log directory. Reason: {0}.

Action: Check server configuration.
Level: 1

Type: WARNING

Impact: Security

JPS-01000: The credential map {0} is invalid.

Cause: The specified credential map name was invalid.

Action: Ensure the credential map name is valid.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01001: The credential key {0} is invalid.

Cause: The specified credential key name was invalid.

Action: Ensure the credential key name is valid.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01002: The value {0} is invalid in this password credential.

Cause: The specified password credential was invalid.

Action: Use only a supported credential type. The supported types are {0}.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01003: The value of name {0}, url {1}, of port {2} is invalid in this datasource credential.

Cause: The specified datasource credential was invalid.

Action: Use only a supported credential type. The supported types are {0}.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01004: The value {0} is invalid in this generic credential.

Cause: The specified generic credential was invalid.

Action: Use only a supported credential type. The supported types are {0}.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01005: The credential type {0} is not supported.

Cause: The specified credential type was invalid.

Action: Use only a supported credential type. The supported types are {0}.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01006: The credential expired on {0}.

Cause: This credential expired on {0}.

Action: Create a new credential.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01007: The credential with map {0} and key {1} already exists.

Cause: This credential already existed.

Action: Use a credential with different map name or key.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01008: The credential map name {0} already exists.

Cause: This credential map name already existed.

Action: Use a different map name.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01009: The credential with map {0} and key {1} does not exist.

Cause: This credential did not exist.

Action: Check the credential map name and key.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01010: The credential map {0} does not exist.

Cause: This credential map name did not exist.

Action: Check the credential map name.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01011: The credential store location property {0} is not configured, or the configured value {1} is invalid.

Cause: The credential store location was not specified.

Action: Check the value of the location attribute.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01012: The credential property {0} is invalid or not defined.

Cause: The credential property {0} was invalid or not defined.

Action: Check the configuration of this property.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01013: The credential store DN {0} is missing in the store; the target DN must be pre-configured.

Cause: The expected credential store DN {0} was missing.

Action: Configure this DN during the bootstrap process.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01014: The credential {0} is invalid.

Cause: This credential was invalid.

Action: Use only a supported credential type. The supported types are password or generic.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01015: Cannot retrieve credential {0}.

Cause: This credential was invalid.

Action: Use only a supported credential type. The supported types are password or generic.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01016: A password credential is expected; instead found {0} for alias {1} and key {2} at location {3}.

Cause: Wrong credential type was found.

Action: Use the password credential type. Expecting password credential but found {0} for alias {1} and key {2} at location {3}.
Level: 1

Type: WARNING

Impact: Other

JPS-01017: A generic credential is expected; instead found {0}.

Cause: Wrong credential type was found.

Action: Use the generic credential type. Expecting generic credential but found {0}.
Level: 1

Type: WARNING

Impact: Other

JPS-01018: A password credential is missing in the credential store.

Cause: The password credential was not found in the credential store.

Action: Ensure that the credential is present in the credential store.
Level: 1

Type: ERROR

Impact: Session

JPS-01019: The credential store {0} has been moved or deleted.

Cause: The specified credential store did not exist.

Action: Ensure that the credential store location is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01020: Cannot create store {0}.

Cause: Could not create the credential store.

Action: Verify the store location, that sufficient permissions are in place, and that sufficient disk space is available.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01021: The generic credential {0} is not serializable.

Cause: This generic credential was not serializable.

Action: Make this credential serializable.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01022: The expiration time {0} is invalid: the expiration time must be later than the creation time.

Cause: Invalid credential expiration time.

Action: Set the expiration time to a time later than the credential creation time.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01023: Store does not contain all expected maps. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01024: Store contains all expected maps. Result {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01025: Store does not contain all expected credentials. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01026: Store contains all expected credentials. Result {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01027: Cannot get credential map. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01028: successful getting of credential map

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01029: successful getting of credential

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01030: Cannot get credential. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01031: Cannot retrieve map names. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01032: successful setting of credential

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01033: Cannot set credential. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01034: successful resetting of credential

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01035: Cannot reset credential. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01036: successful setting of credential map

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01037: Cannot set credential map. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01038: successful resetting of credential map

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01039: Cannot reset credential map. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01040: successful deletion of credential

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01041: Cannot delete credential. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01042: successful deletion of credential map

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01043: Cannot delete credential map. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01044: successful deletion of all credentials from the store

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01045: Cannot delete all credentials from the store. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01046: successful retrieving of map names; mapNameSet {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01047: Cannot persist the wallet. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01048: Modifying of credential failed. Reason {0}

Cause: Modification of credential failed

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-01049: Reading all credentials from the store failed. Reason {0}

Cause: Read of all credentials failed

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-01050: Opening of wallet based credential store failed. Reason {0}

Cause: Credential wallet could not be opened

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-01051: Credential audit events cannot be logged. Reason {0}

Cause: Credential store audit events logging not enabled

Action: Check the audit configuration to ensure auditing enabled
Level: 1

Type: WARNING

Impact: Compliance

JPS-01052: Credential audit event logging failed. Reason {0}

Cause: Credential audit event logging failed

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-01053: Creation of new credential map failed. Reason {0}

Cause: Creation of new credential map failed

Action: Ensure all jps libraries are in setup properly in the runtime
Level: 1

Type: WARNING

Impact: Compliance

JPS-01054: Refresh of credential wallet failed. Reason {0}

Cause: Refresh of credstore wallet failed

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-01055: Could not create credential store instance. Reason {0}

Cause: Could not create credential store instance

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-01056: The credential store location {0} was invalid. It should be a directory or full path to cwallet.sso file.

Cause: The credential store location {0} was invalid. It should be a directory or full path to cwallet.sso file.

Action: Check the value of the location property
Level: 1

Type: ERROR

Impact: Configuration

JPS-01057: The credential map was invalid. Reason {0}

Cause: The credential map was null.

Action: Check the value of the credential map
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01058: The credential dn {0} was invalid.

Cause: The credential dn was invalid.

Action: Ensure the credential dn is valid.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01059: The credential store instance {0} was not fully initialized.

Cause: The credential store was not fully initialized until data source is available.

Action: Wait and retry later
Level: 1

Type: ERROR

Impact: Configuration

JPS-01060: The credential store instance does not have the property ldap url/JDBC url/datasource JNDI name defined.

Cause: The credential store property ldap.url or jdbc.url or datasource.jndi.name was not defined.

Action: Check the configuration for this property.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01500: The anonymous service configuration is missing.

Cause: The anonymous service configuration was missing in jps-config.xml.

Action: Configure the anonymous service in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01501: The anonymous identity store provider instance {0} is not found.

Cause: The anonymous identity store provider configuration was invalid.

Action: Check the anonymous identity store provider configuration in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01502: The LDAP identity store provider instance {0} is not found.

Cause: Invalid or missing LDAP identity store provider configuration.

Action: Check LDAP identity store provider configuration in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01503: The XML identity store provider instance {0} is not found.

Cause: Invalid or missing XML identity store provider configuration.

Action: Check the XML identity store provider configuration in jps-config.xml.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01504: The secret store provider for provider {0} and instance {1} does not exist.

Cause: The credential provider was missing.

Action: Check the configuration of the credential store provider in jps-config.xml.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01505: The key store provider {0} is missing or not configured.

Cause: The keystore provider configuration was missing in jps-config.xml.

Action: Configure a keystore provider in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01506: Invalid context name.

Cause: Invalid context name found.

Action: Check the configurations of contexts in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01507: Invalid login module name.

Cause: Invalid login module name found.

Action: Check the login module configurations in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01508: Invalid login module descriptor.

Cause: Invalid login module descriptor found.

Action: Check the login module instance configurations in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01509: Invalid login module class name.

Cause: Invalid login module class name found.

Action: Check the loginModuleClassName property in the login module instance configuration in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01510: Invalid login module entries.

Cause: Invalid login module entries found.

Action: The expected login module to be invoked is not present or misconfigured. Check the login module instance configurations in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01511: Invalid login module entry.

Cause: The login module entries were not valid in the jps-config.xml file.

Action: Correct the login module entries in service instances and service providers.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01512: Missing login module entry.

Cause: The login module entries were missing in the jps-config.xml file.

Action: Add the appropriate login module entries in service instances and service providers.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01513: The configuration of the JAAS login provider {0} and the service instance {1} are missing.

Cause: The login module provider was missing.

Action: Ensure that a login module provider is configured in the jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01514: The default context is missing in jps-config.xml.

Cause: Default context was missing in jps-config.xml.

Action: Add a default context to jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01515: A context named anonymous is missing in jps-config.xml.

Cause: Context named anonymous was missing in jps-config.xml.

Action: Add a context named anonymous in jps-config.xml file with an anonymous service instance reference.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01516: The default credential store service is missing in default jps-config.xml.

Cause: The default credential store service was missing in the default context in jps-config.xml.

Action: There must be at least one credential store service configured in the default context.
Level: 1

Type: ERROR

Impact: Other

JPS-01517: The generic identity store provider is missing.

Cause: Invalid or missing generic identity store provider configuration.

Action: Check the generic identity store provider configuration in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01518: The anonymous service is not available in the application context.

Cause: The anonymous service was not available in context.

Action: Check the context in jps-config.xml.
Level: 1

Type: ERROR

Impact: Session

JPS-01519: The default context configuration is missing in jps-config.xml.

Cause: The default context configuration was not available in jps-config.xml.

Action: Ensure that the default context is present in jps-config.xml.
Level: 1

Type: WARNING

Impact: Session

JPS-01520: Cannot initialize identity store, cause: {0}.

Cause: Could not initialize identity store.

Action: Correct the identity store configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01521: Identity store file path is invalid.

Cause: Identity store file path was invalid or null.

Action: Ensure that the path configured with the property ADF_IM_FILE_PATH is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01522: The Jps configuration is invalid.

Cause: JPS configuration was null or invalid.

Action: Verify configuration in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01523: The service instance {0} is invalid or not configured in jps-config.xml.

Cause: A service instance configuration was not valid.

Action: Verify that the instance is correctly configured in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01524: The service instance {0} is invalid or not configured in jps-config.xml.

Cause: A service provider configuration was invalid.

Action: Veirfy that the provider is correctly configured in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01525: The identity store service is not properly configured.

Cause: Found invalid identity store service configuration in jps-config.xml.

Action: Ensure a valid identity store configuration in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01526: Configured identity store, user manager, or role manager is invalid. The error is {0}.

Cause: Found null value for configured identity store, user manager, or role manager.

Action: Correct the identity store configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01527: The identity store factory name is not configured.

Cause: Could not find identity store factory name.

Action: Use the property ADF_IM_FACTORY_CLASS to specify the factory class.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01528: Idm identity store is invalid.

Cause: The identity store was not configured correctly.

Action: Correct the configuration of the identity store in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01529: The context {0} contains multiple services of type {1}.

Cause: The context {0} contains multiple services of type {0}.

Action: Check jps-config.xml for correctness.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01530: The anonymous service is already configured in the context {0}.

Cause: The anonymous service is already configured in the context {0}.

Action: Check jps-config.xml for correctness.
Level: 1

Type: WARNING

Impact: Configuration

JPS-01531: Configuration location {0} is a directory. File name expected.

Cause: Configuration location {0} is a directory. File name expected.

Action: Provide a valid configuration file location, including a file name.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01532: The service instance location {0} is invalid or not configured in jps-config.xml.

Cause: A service instance configuration was invalid.

Action: Verify that the location of the instance is correctly configured in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01533: Failed to create service instance {0} for application {1}.

Cause: Failed to create service instance {0} for application {1}.

Action: Check the log files to resolve the error.
Level: 1

Type: WARNING

Impact: Configuration

JPS-01534: Failed to get identity store configuration.

Cause: Failed to get identity store configuration.

Action: Ensure the configuration is available.
Level: 1

Type: ERROR

Impact: Security

JPS-01535: Failed to get configuration name {0}.

Cause: Failed to get configuration name {0}.

Action: Check the log files to resolve the error.
Level: 1

Type: WARNING

Impact: Configuration

JPS-01536: Failed to evaluate XML expression on Object {0}.

Cause: Failed to evaluate XML expression on Object {0}.

Action: Check the log files to resolve the error.
Level: 1

Type: WARNING

Impact: Configuration

JPS-01537: Failed to handle config location {0}. Reason {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Security

JPS-01538: The default policy provider was not found.

Cause: The default policy provider was not found.

Action: Ensure policy provider configuration is correct.
Level: 1

Type: ERROR

Impact: Security

JPS-01539: The Ovd IGF service provider instance {0} is not found.

Cause: Invalid or missing Ovd IGF service provider configuration.

Action: Check Ovd IGF service provider configuration in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01543: The value of {0} is invalid. It must be an integer.

Cause: attribute.expire.time.seconds is not an integer.

Action: Ensure attribute.expire.time.seconds is a valid integer.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02000: The authentication of user {0} succeeded.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02001: The authentication of user {0} failed.

Cause: User authentication failed.

Action: Ensure the user exists in the identity store. Check the user credentials that are being sent for authentication.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02003: Authentication failed.

Cause: Could not authenticate user.

Action: Ensure that authentication uses valid user name and password.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02004: Cannot authenticate user {0}.

Cause: Could not authenticate user.

Action: Ensure that the credentials provided for authentication are correct.
Level: 1

Type: ERROR

Impact: Security

JPS-02005: Cannot login user {0} because {1}. Check the log files for more details.

Cause: Encountered an error while authenticating user.

Action: Contact the domain administrator.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02008: Authenticated role name is invalid: property {0} is invalid or not configured.

Cause: Found invalid or undefined authentication role name property.

Action: Ensure that authentication role name properties are valid in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02009: SAML trusted assertion issuer is not configured: property set {0} is not configured.

Cause: Could not find configuration for SAML trusted assertion issuer.

Action: Set the property saml.trusted.issuers in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02010: Cannot verify SAML assertion.

Cause: Found invalid assertion; SAML trusted assertion issuer was not configured.

Action: Check assertion and set the property saml.trusted.issuers in jps-config.xml.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02011: SAML assertion is missing name identifier.

Cause: Found invalid assertion: name identifier was missing.

Action: Ensure the use of a valid assertion.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02012: SAML assertion subject name is invalid.

Cause: Found invalid assertion: subject name was null.

Action: Ensure the use of a valid assertion.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02013: SAML assertion issuer name is invalid.

Cause: Found invalid assertion: issuer name was invalid.

Action: Ensure the use of a valid assertion.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02014: SAML assertion is invalid.

Cause: Found invalid assertion.

Action: Ensure the use of a valid assertion.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02015: SAML assertion has missing subject.

Cause: Found invalid assertion: subject statement was missing.

Action: Ensure the use of a valid assertion.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02016: SAML assertion is missing conditions.

Cause: Found invalid assertion: condition statement was missing.

Action: Ensure the use of a valid assertion.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02017: Found invalid condition "not before" in SAML assertion. Current Time:{0}, {1} milli seconds, {2} Time:{3}.

Cause: Found invalid condition "not before" in SAML assertion. Current Time:{0}, {1} milli seconds, {2} Time:{3}.

Action: Verify that the condition "not before" in the SAML assertion is set to a date earlier than or equal to today's date.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02018: Found invalid condition "on or after" in SAML assertion. Current Time:{0}, {1} milli seconds, {2} Time:{3}.

Cause: Found invalid condition "on or after" in SAML assertion. Current Time:{0}, {1} milli seconds, {2} Time:{3}.

Action: Verify that the condition "on or after" in the SAML assertion is set to a valid date.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02019: SAML assertion is missing assertion issuers signature.

Cause: Found invalid assertion: assertion issuers signature was missing.

Action: Ensure the use of a valid assertion.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02020: Signature for SAML assertion issuer is invalid.

Cause: Found invalid signature in SAML assertion issuer.

Action: Ensure the use of a valid assertion.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02021: Signature certificate (X509 Data) for SAML assertion issuer is invalid.

Cause: Found invalid signature certificate (X509 Data) in SAML assertion.

Action: Ensure the use of a valid assertion.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02022: Cannot verify signature for SAML assertion.

Cause: Failed to verify issuers signature in assertion.

Action: Check the assertion and set the property saml.trusted.issuers in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02023: Cannot verify SAML assertion signature certificate path.

Cause: Found invalid assertion signature.

Action: Check the assertion and set the property saml.trusted.issuers in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02024: Cannot retrieve trusted CA policy for issuer {0}.

Cause: Found invalid assertion.

Action: Check the assertion and set the property saml.trusted.issuers in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02025: Cannot modify read-only Subject.

Cause: Could not modify a read-only subject.

Action: Ensure the program logic is correct and that the program does not attempt to modify a read-only subject.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02026: X509 certificate is invalid.

Cause: The X509 certificate passed to the callback handler was null or invalid.

Action: Ensure that the callback handler uses a valid X509 certificate.
Level: 1

Type: ERROR

Impact: Other

JPS-02027: The property set {0} is missing in jps-config.xml.

Cause: Could not find property set in jps-config.xml.

Action: Configure the property set in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02028: The extended property set {0} is missing in jps-config.xml.

Cause: Could not find extended property set in jps-config.xml.

Action: Configure the extended property set in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02029: The default realm is not configured in identity store service {0}.

Cause: Could not find the default realm in the identity store service.

Action: Configure the default realm property in the identity store service.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02030: The default realm configured in identity store service {0} is empty or null.

Cause: Found null default realm configured in identity store service.

Action: Configure the default realm property in the identity store service.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02031: The invalid realm name property {0} is configured in identity store service {1}.

Cause: Found invalid realm name property in identity store service.

Action: Configure the correct realm name property in the identity store service.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02032: The duplicate realm name {0} is configured in identity store service {1}.

Cause: Found duplicate realm in identity store service.

Action: Remove duplicate realm configuration from the identity store service.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02033: The realm name {0} passed for authentication is invalid. Was expecting {1}, but found {0}.

Cause: Found invalid realm name {0}. Was expecting {1}, but found {0}.

Action: Check the realm name passed to the authentication of user name.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02034: Realm name is missing in user name for authentication in multi-realm configuration.

Cause: The realm name was not supplied for authentication of multi-realm configuration.

Action: Ensure that the realm name value is passed in the user name when authenticating a multi-realm configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02035: Cannot properly initialize the Kerberos authenticator.

Cause: Could not initialize the Kerberos authenticator.

Action: Check the log files for errors and contact the domain administrator.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02036: Browser does not support Kerberos authentication.

Cause: Could not find support for Kerberos authentication, or it was not configured correctly.

Action: Verify that the browser is set to allow Kerberos authentication.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02037: The SAML assertion issuer {0} certificate is missing from the keystore.

Cause: Could not find SAML assertion certificate in keystore.

Action: Store the SAML assertion issuer's certificate in the keystore, and configure the trustpoint alias in JpsSAMLLoginModuule.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02038: The SAML assertion {0} is missing a signature.

Cause: Could not find expected signature in assertion.

Action: Check that the assertion sent has a valid signature.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02039: Cannot assert certificate. Reason {0}.

Cause: Found invalid certificate, or could not find corresponding user in identity store.

Action: Make sure that the assertion is valid.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02040: Both user identity and token were provided for assertion. Either user identity or token should be provided, not both.

Cause: Both user identity and token were provided for assertion.

Action: Provide either user identity or a token for assertion, not both.
Level: 1

Type: ERROR

Impact: Other

JPS-02041: Assertor class was configured as {0}, but does not implement {1}.

Cause: Assertor class was configured as {0}, but does not implement {1}.

Action: Provide an Assertor that implements {1}.
Level: 1

Type: ERROR

Impact: Other

JPS-02042: Token assertion failed.

Cause: Token assertion failed.

Action: Check detailed logs for more information.
Level: 1

Type: ERROR

Impact: Other

JPS-02043: User name cannot be null or empty.

Cause: User name cannot be null or empty.

Action: Check that the user name is not null or empty.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02044: Found invalid attesting entity in SAML assertion. Attesting entity: {0}.

Cause: Found invalid attesting entity in SAML assertion. Attesting entity: {0}.

Action: Check that the attesting entity for the SAML assertion is valid.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02045: Audience URI for SAML assertion is invalid.

Cause: SAML assertion audience URI is invalid.

Action: Check that the audience URI for the SAML assertion is valid.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02046: Cannot get the user name from SAML assertion name identifier: {0}.

Cause: Cannot get the user name from SAML assertion name identifier: {0}.

Action: Check that the name identifier for the SAML assertion is valid.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02047: SAMLNameIdentifierMapper class was configured as {0}, but does not implement oracle.security.jps.internal.jaas.module.saml.SAMLNameIdentifierMapper.

Cause: SAMLNameIdentifierMapper class was configured as {0}, but does not implement oracle.security.jps.internal.jaas.module.saml.SAMLNameIdentifierMapper.

Action: Provide an SAMLNameIdentifierMapper that implements oracle.security.jps.internal.jaas.module.saml.SAMLNameIdentifierMapper.
Level: 1

Type: ERROR

Impact: Other

JPS-02048: Incorrect password was provided.

Cause: Incorrect password was provided.

Action: Ensure that authentication uses correct password.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02049: Null or empty password was provided.

Cause: Null or empty password was provided.

Action: Ensure that authentication uses correct password.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02050: Signature verification failed. Principal: {0}

Cause: Signature verification failed.

Action: This error is unlikely to occur. Contact technical support when necessary.
Level: 1

Type: ERROR

Impact: Security

JPS-02500: The principal name is invalid.

Cause: Found null principal name.

Action: Check the principal name.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02501: The principal type {0} is invalid.

Cause: Found invalid principal type.

Action: Check the principal type.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02502: The password {0} is invalid.

Cause: Found invalid password.

Action: Check the password passed to create user account.
Level: 1

Type: ERROR

Impact: Data

JPS-02503: The user name {0} is invalid.

Cause: Found invalid user name.

Action: Ensure that the user name used to create, fetch, or remove the account is valid.
Level: 1

Type: ERROR

Impact: Data

JPS-02504: The user range starting at {0} and ending at {1} is not a valid range.

Cause: The user range was invalid.

Action: Check the start and end range. The start range cannot be less than 0, and the end range cannot be less than start range.
Level: 1

Type: ERROR

Impact: Data

JPS-02505: The group {0} is invalid.

Cause: Group name was invalid.

Action: Check the group name that is being sent for creating/fetching/removing group.
Level: 1

Type: ERROR

Impact: Data

JPS-02506: The group range starting at {0} and ending at {1} is not valid range.

Cause: The JPSUserManager.getGroups() method was invoked with invalid start or end range.

Action: Check the start and end range. The start range cannot be less than 0, and the end range cannot be less than start range.
Level: 1

Type: ERROR

Impact: Data

JPS-02507: The anonymous user is not found.

Cause: The anonymous user was not found.

Action: Ensure that a valid anonymous user is configured.
Level: 1

Type: ERROR

Impact: Session

JPS-02508: The anonymous user name is invalid; property {0} is invalid or not defined.

Cause: The anonymous.user.name property was not configured in the anonymous service configuration.

Action: Configure the anonymous.user.name property to a valid user name in the identity store while configuring the Anonymous Service.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02509: The user {0} already exists in the store; choose a different user name.

Cause: The specified user name already existed in the store.

Action: Provide a different user name.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02510: The group {0} already exists in the store; choose a different group name.

Cause: The specified group name already existed in the store.

Action: Provide a different group name.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02511: The role for group {0} is invalid.

Cause: Found null role in group.

Action: Check the group's name.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02512: Cannot create a new user {0}.

Cause: Could not create user.

Action: Ensure that the user name is valid and distinct from any other existing user name.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02513: Cannot drop user {0}.

Cause: Could not drop the user.

Action: Ensure this user already exists.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02514: Cannot retrieve user profile.

Cause: Could not get profile for user.

Action: Ensure that the user exists.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02515: Cannot update user profile.

Cause: Could not set profile for user.

Action: Ensure that the user exists.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02516: Cannot retrieve role profile.

Cause: Could not get role profile.

Action: Ensure that the role exists.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02517: Cannot update role profile.

Cause: Could not set role profile.

Action: Ensure that the role exists.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02518: Cannot create role {0}.

Cause: Could not create role.

Action: Ensure that the role exists.
Level: 1

Type: ERROR

Impact: Security

JPS-02519: Cannot drop role {0}.

Cause: Could not drop role.

Action: Ensure that the role exists.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02520: Cannot grant role to the principal.

Cause: Could not grant permission to role.

Action: Ensure that the permission is set for the role.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02521: Cannot revoke role from principal.

Cause: Could not revoke role.

Action: Check that the correct permission to revoke the role is set.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02522: Cannot add user to role owners.

Cause: Could not add owner to role.

Action: Check log files and correct the appropriate configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02523: Cannot remove user from role owners.

Cause: Could not remove owner from role.

Action: Check log files and correct the appropriate configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02524: Cannot retrieve role owners.

Cause: Could not get role owners.

Action: Check log files and correct the appropriate configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02525: Cannot retrieve role grantees.

Cause: Could not get role grantees.

Action: Check log files and correct the appropriate configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02526: Cannot retrieve the roles granted to principal.

Cause: Could not get granted roles.

Action: Check log files and correct the appropriate configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02527: Cannot close identity store.

Cause: Could not close identity store.

Action: Check log files and correct the appropriate configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02528: Cannot obtain a handle for role manager MBean.

Cause: Could not get role manager object name.

Action: Check log files and correct the appropriate configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02529: Cannot obtain a handle for user manager MBean.

Cause: Could not get user manager object name.

Action: Check log files and correct the appropriate configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02530: Cannot get a list of searchable attributes.

Cause: Could not get searchable attributes.

Action: Check log files and correct the appropriate configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02531: Cannot get list of user property names.

Cause: Could not get user property names.

Action: Check log files and correct the appropriate configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02532: Cannot parse principals of role.

Cause: Could not parse role principals.

Action: Check log files and correct the appropriate configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02533: Cannot parse principals of user.

Cause: Could not parse user principals.

Action: Check log files and correct the appropriate configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02534: Cannot find role {0}.

Cause: Could not completer search role operation.

Action: Correct the role name and, if necessary, contact the domain administrator.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02535: Cannot complete search for roles.

Cause: Could not complete search for multiple roles.

Action: Correct role names and, if necessary, contact the domain administrator.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02536: Cannot complete search for user {0}.

Cause: Could not completer user search.

Action: Correct user name and, if necessary, contact the domain administrator.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02537: Cannot complete search for users.

Cause: Could not complete search for multiple users.

Action: Correct user names and, if necessary, contact the domain administrator.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02538: Cannot complete search operation.

Cause: Failed to complete search.

Action: Correct the search query.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02539: Cannot change password of user {0}.

Cause: Could not change password.

Action: Contact the domain administrator.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02540: User {0} not found in the identity store.

Cause: User {0} not found in the identity store.

Action: Ensure user is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02541: Identity store has an invalid configured subscriber name.

Cause: Found invalid subscriber name.

Action: Correct the configuration of property subscriber.name.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02542: unknown identity store service type {0}.

Cause: Found unknown identity store service type {0}.

Action: Correct the identity store configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02543: Search type {0} is invalid.

Cause: Found invalid search type {0}.

Action: Correct the type passed for the search.
Level: 1

Type: ERROR

Impact: Other

JPS-02544: Operation type {0} is invalid.

Cause: Found invalid operation type {0}.

Action: Correct the type passed for the operation.
Level: 1

Type: ERROR

Impact: Other

JPS-02545: Search filter type {0} is invalid.

Cause: Found invalid search filter type {0}.

Action: Correct the type passed for the search filter.
Level: 1

Type: ERROR

Impact: Other

JPS-02546: Scope type is invalid {0}.

Cause: Found invalid scope type {0}.

Action: Correct the type passed for the scope.
Level: 1

Type: ERROR

Impact: Other

JPS-02547: Cannot create realm {0}.

Cause: Could not created realm.

Action: Check log files for error details.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02548: Cannot delete realm {0}.

Cause: Could not delete realm.

Action: Check log files for error details.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02549: A realm with the specified name already exists.

Cause: A realm with the specified name already exists.

Action: Choose a different realm name.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02550: The realm {0} does not exist.

Cause: Could not find realm with the name {0}.

Action: Correct the supplied realm name.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02551: Cannot perform an unsupported operation on a serialized object.

Cause: Could not perform operation on serialized object.

Action: Check log files for error details.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02552: Cannot add a duplicate owner.

Cause: Attempted to add already present owner.

Action: Correct the owner's name.
Level: 1

Type: TRACE

Impact: Data

JPS-02553: Cannot remove an owner that is not present.

Cause: Attempted to remove a non existing owner.

Action: Correct the owner's name.
Level: 1

Type: TRACE

Impact: Data

JPS-02554: Cannot add a duplicate member.

Cause: Attempted to add already present member.

Action: Correct the member's name.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02555: Cannot complete identity store operation. The error is {0}.

Cause: Could not perform identity store operation.

Action: Check error log files for details.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02556: Run into error {0} while using identity store.

Cause: Run into an internal identity store error.

Action: Check error log files for details.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02557: The group {0} is invalid.

Cause: Found null or invalid group.

Action: Correct the group's name.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02558: Operation isOwnedBy failed.

Cause: Could not perform operation isOwnedBy.

Action: Correct the owner's name.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02559: Operation isManagedBy failed.

Cause: Could not perform operation isManagedBy.

Action: Correct the name.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02560: Cannot update role.

Cause: Could not update role.

Action: Verify that the role name is correct and, if necessary, contact the domain administrator.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02561: The realm entry {0} is missing in the identity store XML file.

Cause: Could not find realm entry {0} in XML-based identity store.

Action: Ensure that the realm name is present in the XML-based identity store.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02562: Identity store entry is missing in the identity store XML file.

Cause: Could not find identity store entry in XML-based identity store.

Action: Ensure that entry is present in the XML-based identity store.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02563: Length of the name attribute should be more than {0}.

Cause: Found attribute name with less than {0} characters.

Action: Ensure that the length of the attribute name is at least the minimum length.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02564: Length of the name attribute should be less than {0}.

Cause: Found attribute name with more than {0} characters.

Action: Ensure that the length of the attribute name is at most the maximum length.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02565: Name attribute contains invalid characters.

Cause: Found invalid characters in attribute name.

Action: Ensure that attribute names have characters in the following sets only: [a-z], [A-Z], [0-9], ['.', '-', '_'].
Level: 1

Type: ERROR

Impact: Configuration

JPS-02566: The identity store config property {0} with value {1} is invalid.

Cause: Found invalid identity store configuration property.

Action: Correct the configuration of the identity store property.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02567: The credential with map {0} and key {1} does not exist.

Cause: Could not find credential with map and key names provided.

Action: Ensure that a credential with given map and key is present in the credential store.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02568: The password credential with map {0} and key {1} is invalid.

Cause: Found invalid user name or password.

Action: Ensure that the user name and password in the credential store are correct.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02569: Cannot find the XML file {0}.

Cause: Could not find XML file for XML-based identity store {0}.

Action: Check the path of the XML file specified for the identity store.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02570: XML file is unspecified.

Cause: Could not determine XML file.

Action: Specify the XML file for the XML-based repository.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02571: The algorithm {0} to encode passwords is not supported.

Cause: Found invalid password encoding algorithm.

Action: Specify a valid algorithm for password encoding.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02572: Caller does not have IdentityAssertion permission to execute this operation. Reason {0}.

Cause: Caller did not have IdentityAssertion permission.

Action: Make sure the caller has IdentityAssertion permission to execute this operation.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02573: Cannot grant a role to itself.

Cause: Attempted to grant a role to itself.

Action: Verify that no role is being granted to itself.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02574: Cannot delete default realm.

Cause: Could not delete default realm.

Action: The default realm cannot be deleted: assign another realm as the default realm before deleting this one.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02575: A user with the specified name does not exist.

Cause: Could not find user with the specified name.

Action: Check the user name.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02576: A role with the specified name already exists.

Cause: Role with the specified name already existed.

Action: Use a different role name.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02577: A role with the specified name does not exist.

Cause: Could not find role with the specified name.

Action: Check the role name.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02578: The principal type {0} is invalid for the identity store type {1}.

Cause: Found unsupported principal type {0} for identity store type {1}.

Action: Verify that principals have supported types.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02579: Identity store type for application {0} is null or empty.

Cause: Found null identity store type configured in identity store.

Action: Pass one of the following identity store types: XML, OID, ACTIVE_DIRECTORY, IPLANET, EDIRECTORY, OPEN_LDAP, COREID, OVD, or CUSTOM.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02580: Cannot grant role {0} to {1} because it would lead to a cyclic dependency.

Cause: Could not grant role {0} to {1}, because it would lead to a cyclic dependency.

Action: Revoke the grant which would create the cyclic dependency, and try again.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02582: LDAP user or group search base is invalid.

Cause: Found invalid LDAP user or group search base.

Action: Check that the user and group search base properties are valid.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

JPS-02583: JPS principal "{0}" with identity store type "{1}" cannot be created.

Cause: JPS principal "{0}" with identity store type "{1}" cannot be created.

Action: Ensure the principal value is valid.
Level: 1

Type: ERROR

Impact: Security

JPS-02584: JPS user name "{0}", principal type "{1}" with identity store type "{2}" cannot be created.

Cause: JPS user name "{0}", principal type "{1}" with identity store type "{2}" cannot be created.

Action: Ensure the user value is valid.
Level: 1

Type: ERROR

Impact: Security

JPS-02585: JPS enterprise role name "{0}", principal type "{1}" with identity store type "{2}" cannot be created.

Cause: JPS enterprise role name "{0}", principal type "{1}" with identity store type "{2}" cannot be created.

Action: Ensure the enterprise role value is valid.
Level: 1

Type: ERROR

Impact: Security

JPS-02586: JPS application role name "{0}", principal type "{1}" cannot be created.

Cause: JPS application role name "{0}", principal type "{1}" cannot be created.

Action: Ensure the application role value is valid.
Level: 1

Type: ERROR

Impact: Security

JPS-02587: Principal class "{0}", name "{1}" cannot be created.

Cause: Principal class "{0}", name "{1}" cannot be created.

Action: Ensure the principal value is valid.
Level: 1

Type: ERROR

Impact: Security

JPS-02588: Enterprise user principal "{0}" cannot be created.

Cause: Enterprise user principal "{0}" cannot be created.

Action: Ensure the user principal value is valid.
Level: 1

Type: ERROR

Impact: Security

JPS-02589: Enterprise role principal "{0}" cannot be created.

Cause: Enterprise role principal "{0}" cannot be created.

Action: Ensure the role principal value is valid.
Level: 1

Type: ERROR

Impact: Security

JPS-02590: Token type {0} cannot be supported. Supported types are: {1}.

Cause: Token type {0} cannot be supported. Supported types are: {1}.

Action: Use the Supported types.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02591: Guid {0} is assigned to principal {1}.

Cause: Guid {0} is assigned to principal {1}.

Action: Check log for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-02592: Failed to push ldap config data to libOvd for service instance "{0}" in JPS context "{1}", cause: {2}

Cause: Failed to push ldap config data to libOvd for service instance "{0}" in JPS context "{1}", cause: {2}

Action: Check libOvd log for more details.
Level: 1

Type: ERROR

Impact: Security

JPS-02593: Failed to get IGF UserManager or RoleManager instance from IGF API, cause: {0}

Cause: Failed to get IGF UserManager or RoleManager instance from IGF API, cause: {0}

Action: Check IGF API or libOvd log for more details.
Level: 1

Type: ERROR

Impact: Security

JPS-02594: The service instance "{0}" in JPS context "{1}" has no LDAP instance configured

Cause: The service instance "{0}" in JPS context "{1}" has no LDAP instance configured

Action: Check jps-config.xml to make sure the IGF service has either the IDStore instance defined, or use the WlsLdapIdStoreConfigProvider to get LDAP config from WLS Authentication providers.
Level: 1

Type: ERROR

Impact: Security

JPS-02595: The IGFService specified ldap "{0}" is not defined in the JPS service instances

Cause: The IGFService specified ldap "{0}" is not defined in the JPS service instances

Action: Check jps-config.xml to make sure the specified ldap is defined as a JPS service instance.
Level: 1

Type: ERROR

Impact: Security

JPS-02596: The provider class type for the specified ldap instance "{0}" is configured as "{1}", which not the expected type of "oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider"

Cause: The provider class type for the specified ldap instance "{0}" is configured as "{1}", which not the expected type of "oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider"

Action: Check jps-config.xml to make sure the provider type class for ldap instance is "oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider".
Level: 1

Type: ERROR

Impact: Security

JPS-02597: You configured a custom Authentication Provider or WLS generic LDAPAuthenticator, which the libOvd can not recognize. Supply the idstore.type property in jps-config.xml file, or use a specific WLS LDAP Authentication provider that matches your LDAP server instead of a generic one.

Cause: You configured a custom Authentication Provider or WLS generic LDAPAuthenticator, which is a custom type and not supported by libOvd

Action: The "idstore.type" property must be specified in jps-config.xml file as specific type such as OID, OVD etc. Alternatively, select a specific WLS LDAP Authentication provider that matches your LDAP server.
Level: 1

Type: ERROR

Impact: Security

JPS-02598: Pushed ldap name and types info to libOvd. Ldaps : {0}.

Cause: libOvd is enabled so Ldap configuration info is passed to libOvd

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-02599: The configured Identity Store provider "{0}" is not supported by IDM IdentityDirectory

Cause: The configured Identity Store provider "{0}" is not supported by IDM IdentityDirectory

Action: Use supported Identity Store provider for the IdentiyStoreService
Level: 1

Type: ERROR

Impact: Security

JPS-02600: libOvd required system parameter of "common.components.home" is not supplied in the JVM command line

Cause: libOvd required system parameter of "common.components.home" is not supplied in the JVM command line

Action: Supply the system flag of "-Dcommon.components.home" and point it to the oracle_common folder
Level: 1

Type: ERROR

Impact: Security

JPS-03000: Cannot instantiate permission class "{0}", target "{1}", or actions "{2}" as defined in the application policy context "{3}". Cause {4}

Cause: Could not load a permission class.

Action: Ensure that the class name is correct and available in the current class loader.
Level: 1

Type: WARNING

Impact: Security

JPS-03001: Cannot instantiate permission class "{0}", target "{1}", or actions "{2}" as defined in the system policy context. Cause {3}

Cause: Could not load a class.

Action: Ensure that the class name is correct and is available in the current class loader.
Level: 1

Type: WARNING

Impact: Security

JPS-03004: Cannot log check authorization event to the audit service.

Cause: Could not log check authorization events to the audit service.

Action: Ensure that auditing is configured correctly in your environment and application.
Level: 1

Type: WARNING

Impact: Security

JPS-03005: LDAP policy store contains invalid configuration parameters.

Cause: Found invalid parameters in LDAP policy store configuration.

Action: Check the configuration of the LDAP policy store.
Level: 1

Type: WARNING

Impact: Security

JPS-03006: The name "{0}" of application role "{1}" is missing or invalid.

Cause: Found missing or invalid name in application role.

Action: The internal identifier generated by the policy store seems malformed, due to an internal policy store error; contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Security

JPS-03007: Authorization check permission succeeded.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03008: Authorization check permission failed.

Cause: Current Subject or source code did not have required permissions

Action: Provide the required permissions.
Level: 1

Type: WARNING

Impact: Security

JPS-03009: Executing privileged action in {0} mode as subject {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03010: Policy store cleanup thread started.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03011: Policy store cleanup thread stopped.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03012: Error occurred when computing application roles in application context {0} for subject {1}. Exception: {2}

Cause: Error occurred when computing application roles in application context {0} for subject {1}. Exception: {2}

Action: Refer to the base exception in logs to resolve the issue.
Level: 1

Type: WARNING

Impact: Security

JPS-03013: Unsupported API method call.

Cause: Unsupported API method call.

Action: Check the policy provider.
Level: 1

Type: WARNING

Impact: Security

JPS-03014: Failed to distribute policy by timer.

Cause: Failed to distribute policy by timer.

Action: Check the log for more details or contact the administator.
Level: 1

Type: ERROR

Impact: Configuration

JPS-03015: Resource-Actions '{0}' will be skipped in bulk authorization evaluation for Application: '{1}'.

Cause: Application name not set in the resource-actions.

Action: Set the Application name in the resource-actions
Level: 1

Type: WARNING

Impact: Configuration

JPS-03016: Resource-Actions '{0}' will be skipped in bulk authorization. Reason: '{1}'

Cause: Failed to convert the Resource-Actions into a Permission instance.

Action: Check the logs for more information to resolve the error.
Level: 1

Type: WARNING

Impact: Configuration

JPS-03017: Failed to compute Application roles for Subject '{0}'. Reason '{1}'

Cause: Unable to get the ApplicationRoles granted to a principal.

Action: Check the logs for more information to resolve the error.
Level: 1

Type: WARNING

Impact: Configuration

JPS-03018: The authorization result is ignoring policies from application {0} as the application is not available

Cause: The application is not available at runtime, or the application is not defined in the policystore.

Action: Check if the application is provisioned in the policystore.
Level: 1

Type: WARNING

Impact: Configuration

JPS-03019: Policy evaluation in the application {0} failed. Reason: {1}

Cause: Error occurred while evaluating policies.

Action: Refer to the logs to rectify the problem.
Level: 1

Type: WARNING

Impact: Configuration

JPS-03020: Policy evaluation in the system policy failed. Reason: {0}

Cause: Error occurred while evaluating system policies.

Action: Refer to the logs to rectify the problem.
Level: 1

Type: WARNING

Impact: Configuration

JPS-03021: Admin Policy evaluation in the application {0} failed. Reason: {1}

Cause: Error occurred while evaluating administrative policies.

Action: Refer to the logs to rectify the problem.
Level: 1

Type: WARNING

Impact: Configuration

JPS-03022: Failed to initialize PolicyStore for Discovery mode. Reason: {0}

Cause: Failed to initialize PolicyStore for Discovery mode. Reason: {0}

Action: Refer to the logs to rectify the problem.
Level: 1

Type: ERROR

Impact: Configuration

JPS-03023: Discovered policy directory either not exist or can not write, isExist={0},isDirectory={1},canWrite={2}

Cause: Discovered policy directory either not exist or can not write, isExist={0},isDirectory={1},canWrite={2}

Action: Make sure directory for writing discovered policy exist, is directory and can write.
Level: 1

Type: ERROR

Impact: Configuration

JPS-03024: Failed to write policy information during discovery. Reason: {0}

Cause: Failed to dump policy objects in discovery mode. Reason: {0}

Action: Refer to the logs to rectify the problem.
Level: 1

Type: WARNING

Impact: Configuration

JPS-03025: Input permission is null when getPermissions is called for application name= {0}

Cause: Input permission is null when getPermissions is called. application name= {0}

Action: Refer to the logs to rectify the problem.
Level: 1

Type: WARNING

Impact: Configuration

JPS-03026: PDPService and PolicyStore Service instance not found in default context. Reason: {0}

Cause: PolicyStore service instance and PDPService service instance not found in the default JpsContext in an uncontrolled mode.

Action: Configure a PDPService service instance in the default JpsContext, or if running in an uncontroled mode, a PolicyStore Service.
Level: 1

Type: ERROR

Impact: Configuration

JPS-03027: PDPService service instance failed during initialization due to lack of grant. If you are seeing this error after a new installation, make sure you have updated weblogic.policy as installation step suggested

Cause: PDPService service instance failed during initialization because of lack of grant.

Action: check codebase grant like weblogic.policy to see if proper grant set for all codebase of PDP service.
Level: 1

Type: ERROR

Impact: Configuration

JPS-03028: Unable to convert to a permission entry to resource-actions entry. Reason: {0}

Cause: Unable to convert to a permission entry to resource-actions entry.

Action: Check the logs for more information to resolve the error.
Level: 1

Type: WARNING

Impact: Configuration

JPS-03150: Error during setting the field of a provider MBean. {0}

Cause: Error during setting the field of a provider MBean. {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03151: getSecurityService returning null for requested service type of {0} for realm {1}

Cause: getSecurityService returning null for requested service type of {0} for realm {1}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-03152: Query Atz Cache specified but no response collector supplied

Cause: Query Atz Cache specified but no response collector supplied.

Action: Supply the response collector in the request.
Level: 1

Type: ERROR

Impact: Security

JPS-03153: Error parsing atz. cache flush time.

Cause: Error parsing atz. cache flush time.

Action: Verify that the value is an integer.
Level: 1

Type: ERROR

Impact: Security

JPS-03154: Authorization cache has been flushed. Time={0}

Cause: Authorization cache has been flushed. Time={0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03155: Cannot locate class: {0}

Cause: Cannot locate class: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03156: The exception has been thrown by ARME. The authorization result is set to deny.

Cause: The exception has been thrown by ARME. The authorization result is set to deny.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03157: Error during initialization of the security framework.

Cause: Error during initialization of the security framework.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03158: Failed to parse resource cache size: {0}

Cause: Failed to parse resource cache size: {0}

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03159: Invalid built in type in Value object: {0}

Cause: Invalid built in type in Value object: {0}

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03160: Attempt to {0} a {1} value for type: {2}

Cause: Attempt to {0} a {1} value for type: {2}

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03161: identifier not found in symbol table: {0}

Cause: Identifier not found in symbol table: {0}

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03162: ERROR: PARSE: reason:==>

Cause: ERROR: PARSE: reason:==>

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03163: Invalid Declaration type received by setDeclType

Cause: Invalid Declaration type received by setDeclType.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03164: Got exception

Cause: Got exception.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03165: Invalid declaration type found: {0}

Cause: Invalid declaration type found: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03166: Unexpected PolicyParserTokenType: {0}

Cause: Unexpected PolicyParserTokenType: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03167: Invalid attribute type: {0}

Cause: Invalid attribute type: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-03168: Invalid attribute value type: {0}

Cause: Invalid attribute value type: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-03169: Invalid configuration

Cause: Invalid configuration.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03170: Try to get {0}, but JPS Policy tree is not available.

Cause: Try to get {0}, but JPS Policy tree is not available.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03171: Unable to update policy: unable to get {0} instance

Cause: Unable to update policy: unable to get {0} instance.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03172: Unspecified error in {0}

Cause: Unspecified error in {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03173: Commit error: {0}

Cause: Commit error: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03174: ARME can not find state.chk file.

Cause: ARME can not find state.chk file.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03175: !!!>>>Invalid mac found in write check, rewrite policies and mac

Cause: !!!>>>Invalid mac found in write check, rewrite policies and mac

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03176: Failed to write check file.

Cause: Failed to write check file.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03177: Failed to close check file writer

Cause: Failed to close check file writer.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03178: Failed to write mac, which will cause Mac verification error in the future.

Cause: Failed to write mac, which will cause Mac verification error in the future.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03179: Prepare request in invalid state for update

Cause: Prepare request in invalid state for update.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03180: Error happens: {0}

Cause: Error happened: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03181: ArmeRuntimeException happens

Cause: ArmeRuntimeException happened.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03182: Cannot get AppGuardInstance, so cannot get information to request policy update from PD.

Cause: Cannot get AppGuardInstanceii, so cannot get information to request policy update from PD.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03183: Internal error. The local PD registration is required but LocalPdPort object has not been set. The registration process cannot be completed.

Cause: Internal error. The local PD registration is required but LocalPdPort object has not been set. The registration process cannot be completed.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03184: No host specified in the ARME configuration, attempting to determine host address...

Cause: No host specified in the ARME configuration, attempting to determine host address...

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03185: No {0} found in the ARME configuration. Cannot contact PD

Cause: No {0} found in the ARME configuration. Cannot contact PD.

Action: Verify configuration.
Level: 1

Type: ERROR

Impact: Security

JPS-03186: InstanceName not found in ARME configuration, using LocalName and host

Cause: InstanceName not found in arme configuration, using LocalName and host.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03187: No {0} from ARME, unable to contact PD

Cause: No {0} from ARME, unable to contact PD.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03188: Exception initializing SSL. Unable to contact PD

Cause: Exception initializing SSL. Unable to contact PD.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03189: Error getting attribute: {0}

Cause: Error getting attribute: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03190: Failed to close File reader while reading salt.

Cause: Failed to close File reader while reading salt.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03191: Could not obtain digest algorithm {0}

Cause: Could not obtain digest algorithm '{0}'.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03192: Index of ListValue is wrong

Cause: Index of ListValue is wrong.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03193: PBEService is not initialized

Cause: PBEService is not initialized.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03194: Port is not number type

Cause: Port is not number type.

Action: Verify that the port value is an integer.
Level: 1

Type: ERROR

Impact: Security

JPS-03195: Can not get host IP information, using default IP address: {0}

Cause: Cannot get host IP information, use default IP address: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03196: Can not get host IP information.

Cause: Cannot get host IP information.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03197: ARME shutdown failed: {0}

Cause: ARME shutdown failed: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03198: Can not get enablePerfStats from ARME config file

Cause: Cannot get enablePerfStats from arme config file.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03199: Configuration file is [{0}]

Cause: Configuration file is [{0}].

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03200: getDebugStore: IOException caught.

Cause: getDebugStore: IOException happens.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03201: Privilege name error: {0}

Cause: privilege name error: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03202: Resource name or application name invalid.

Cause: Resource name or application name invalid.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03203: Resource name is wrong according to ALES naming logic

Cause: Pesource name is wrong according to ALES naming logic.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03204: Invalid object name

Cause: Invalid object name.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03205: Logical name {0} is invalid

Cause: Logical name {0} is invalid.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03206: Logical name {0} is undefined

Cause: Logical name {0} is undefined.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03207: IOException occurred when storing logical names {0}

Cause: ioexception occured when storing logical names {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03208: Logical names record is not correct

Cause: Logical names record is not correct.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03209: objectTree is initialized properly

Cause: ObjectTree is initialized properly.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03210: Can not close data files: {0}

Cause: Cannot close data files: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03211: Blocking queue is broken

Cause: Blocking queue is broken.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03212: Session data could not be loaded. Session abandoned

Cause: Session data could not be loaded. Session abandoned.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03213: args value is null or wrong type

Cause: Args value is null or wrong type.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03214: Could not add attribute(s) to cache

Cause: Could not add attribute(s) to cache.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-03215: Caught BadParameterException during get attribute: {0}

Cause: Caught BadParameterException while getting attribute: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03216: Installing custom retriever: {0}

Cause: Installing custom retriever: {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03217: Caught exception while retrieving attribute from context: {0} Continue retrieving static attribute value.

Cause: Caught exception while retrieving attribute from context: {0} Continue retrieving static attribute value.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03218: Failed to transport AttributeValue to AttributeElement, caught {0}: {1}

Cause: Failed to transport AttributeValue to AttributeElement, caught {0}: {1}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03219: AttributeValue type error, not single and list, return null

Cause: AttributeValue type error, not single and list, return null.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03220: Exception from the LDAP/DB server, code: {0}, trying alternate connection

Cause: Exception from the LDAP/DB server, code: {0}, trying alternate connection.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-03221: Alternate LDAP/DB connection failed, code: {0}

Cause: Alternate LDAP/DB connection failed, code: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03222: Null extendedContext is passed to attribute retriever, cannot look for value.

Cause: Null extendedContext is passed to attribute retriever, cannot look for value.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-03223: Caught exception while retrieving attribute: {0}

Cause: Caught exception while retrieving attribute: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03224: Parameter value is null or wrong type.

Cause: Parameter value is null or wrong type.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03225: Calling RBACEvals:{0}

Cause: Calling RBACEvals:{0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03226: Empty Application name or Obligation name is passed to report_obligation function.

Cause: Empty Application name or Obligation name is passed to report_obligation function.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03227: Unexpected error: invalid parameter instances.

Cause: Unexpected error: invalid parameter instances.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03228: The value of args is null

Cause: args is null.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03229: Error during initialization of RetrieverConfiguration.

Cause: Error during initialization of RetrieverConfiguration.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03230: args value type is null or wrong type value

Cause: args value type is null or wrong type value.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03231: {0} supplied to subject_in_group is not a qualified group, will qualify

Cause: {0} supplied to subject_in_group is not a qualified group, will qualify.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03232: Qualified group is {0}

Cause: qualified group is {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03233: Type of args should be String[]

Cause: args should be String[].

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03234: No value is passed to {0}

Cause: No value is passed to {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03235: No attribute name is passed to sys_obj_exists

Cause: No attribute name is passed to sys_obj_exists.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03236: Failed to get attribute {0} for eval function {0}

Cause: Failed to get attribute {0} for eval function {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03237: Value passed to {0} is not valid, {1}

Cause: Value passed to {0} is not valid, {1}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03238: {0} is not a valid value for {1}

Cause: {0} is not a valid value for {1}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03239: valid_timeval called for unexpected eval function {0}

Cause: valid_timeval called for unexpected eval function {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03240: Unknown eval function {0} used in valid_until_timeofday

Cause: Unknown eval function {0} used in valid_until_timeofday.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03241: Disabling extended performance data...

Cause: Disabling extended performance data...

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03242: The extended performance data have been retrieved. The total number of attributes is {0}, the total number of functions is {1}.

Cause: The extended performance data have been retrieved. The total number of attributes is {0}, the total number of functions is {1}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03243: Unexpected MBean attribute get method: {0}

Cause: Unexpected mbean attribute get method: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03244: {0} specified but no response collector supplied

Cause: {0} specified but no response collector supplied.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03245: Received {0} in isProtectedResource

Cause: Received {0} in isProtectedResource.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03246: Role object passed into wles atz provider is null, ignoring

Cause: Null role object passed into wles atz provider, ignoring.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03247: A SecurityRole object passed to the authorization engine has role name equal to null. The object will be ignored. The string representation of the object is {0}.

Cause: A SecurityRole object passed to the authorization engine has role name equal to null. The object will be ignored. The string representation of the object is {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03248: Error {0}

Cause: Error {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03249: ASI shutdown failed

Cause: ASI shutdown failed.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03250: getInstance: Warning: The parent classloaders are different.

Cause: getInstance: Warning: The parent classloaders are different.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03251: addClassJars: {0}

Cause: addClassJars: {0}.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-03252: Missing JAR file: {0}

Cause: Missing JAR file: {0}.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-03253: Error initializing URLs in classloader. Vector: {0}

Cause: Error initializing URLs in classloader. Vector: {0}.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-03254: lazy getRoles failed with error {0}

Cause: lazy getRoles failed with error {0}.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-03255: null value returned in roles list, ignoring

Cause: null value returned in roles list, ignoring.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-03256: Internal error. Method queryRoles has returned role {0} that starts with an incorrect prefix for a role. The role will be ignored.

Cause: Internal error. Method queryRoles has returned role {0} that starts with an incorrect prefix for a role. The role will be ignored.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-03257: Passed an non URLResource, in getAttributeValue

Cause: Passed a non URLResource, in getAttributeValue.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-03258: Initializing UserUtils; {0}

Cause: Initializing UserUtils; {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03259: Invalid built in type received

Cause: Invalid built in type received.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-03260: Attempt to {0} when CRED is wrong type

Cause: Attempt to {0} when CRED is wrong type.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-03261: No locally defined evaluator found for function {0}.

Cause: No locally defined evaluator found for function {0}.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-03262: DiscoveryModeRoleMap does not support this operation

Cause: DiscoveryModeRoleMap does not support this operation

Action: Do not call method not supported
Level: 1

Type: WARNING

Impact: Configuration

JPS-03263: DiscoveryModeRoleMap never contains data

Cause: DiscoveryModeRoleMap never contains data

Action: Do not try to get data from DiscoveryModeRoleMap.
Level: 1

Type: WARNING

Impact: Configuration

JPS-03264: The attribute dependency leads to a dead loop, {1} depends on {0} already.

Cause: The attribute dependency leads to a dead loop, {1} depends on {0} already.

Action: Please check the configuration.
Level: 1

Type: ERROR

Impact: Security

JPS-03265: Data source based DB query failed, try again.

Cause: Data source based DB query failed, try again.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-03266: Failed to retrieve connection for url {0} due to following exception {1}.

Cause: Failed to retrieve connection for {0}.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-03267: Ignoring credential variable exception in computeObligation for {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03268: In Policy {0}, an invalid Resource Name Expression {1} was encountered. The Policy will not participate in the runtime authorization evaluation. Reason: {2}

Cause: Resource name expression in policy is invalid

Action: Correct the reource name expression.
Level: 1

Type: ERROR

Impact: Security

JPS-03269: Size of bag provided for type-one-and-only function is not one.

Cause: Size of bag provided to type one and only function is not one.

Action: Provide correct function.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-03270: Invalid value of year {0} or month {1} in yearMonthDuration .Must be between max and min values for integer.

Cause: Value provided for year or month is outside the supported integer range on this JVM.

Action: Provide a valid integer value.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-03271: Function name passed to evaluator is null.

Cause: Function name is null.

Action: Provide a valid function name.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-03272: No arguments passed to function {0}.

Cause: No arguments passed to function.

Action: Provide a valid function arguments.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-04000: Cannot get the default policy store.

Cause: Could not find to the default policy store.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04001: Cannot read the default policy store.

Cause: Could not read the default policy store.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04002: Cannot get application policy for application "{0}".

Cause: Encountered a policy store internal error.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04003: Duplicate principal present "{0}"in a grant request.

Cause: Found that list of principals in the grantee for the grant contains duplicate

Action: Correct the list of principals in the grantee.
Level: 1

Type: WARNING

Impact: Security

JPS-04004: Duplicate permission present "{0}" in a grant request.

Cause: Found that list of permissions in the grant contains duplicate.

Action: Correct the list of permissions in the grant.
Level: 1

Type: WARNING

Impact: Security

JPS-04005: More than one result found for given Application Name:{0}, Query:{1}, Actual results:{2}.

Cause: More than one results found for application name.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04021: Cannot create application policy context "{0}".

Cause: Encountered two application policy contexts with identical names.

Action: Modify an application policy context to have a distinct name.
Level: 1

Type: WARNING

Impact: Security

JPS-04022: Cannot create application policy context "{0}".

Cause: Failed to complete persist operation while creating an application policy.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04026: Cannot delete application policy context "{0}".

Cause: Could not find a policy context with the provided name.

Action: Verify that a context with the provided name exists.
Level: 1

Type: WARNING

Impact: Security

JPS-04027: Role with name "{0}" does not exist.

Cause: Could not find a role with name {0}.

Action: Verify that a role with the provided name exists.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04028: Application with name "{0}" does not exist.

Cause: Could not find application with name {0}.

Action: Verify that an application with the provided name exists.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04029: Cannot create principal with class name "{0}".

Cause: Could not create principal with class name {0}.

Action: Verify that the provided class name is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04030: Cannot delete application policy context "{0}".

Cause: Failed to complete persist operation while deleting an application policy.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04031: Parameter "{0}" is null.

Cause: Supplied parameter {0} was null.

Action: Verify that the supplied parameter is non-null. If it is of type String, ensure that its length is positive.
Level: 1

Type: WARNING

Impact: Security

JPS-04032: Parameter "{0}" supplied is not the instance of "{1}".

Cause: Parameter {0} supplied is not the instance of {1}.

Action: Ensure parameter is of correct datatype.
Level: 1

Type: WARNING

Impact: Security

JPS-04033: Parameter "{0}" supplied is not of the type "{1}" (as expected).

Cause: Parameter {0} supplied is not of the type {1} (as expected).

Action: Ensure parameter is of correct datatype.
Level: 1

Type: WARNING

Impact: Security

JPS-04034: Failed to modify properties for Application "{0}".

Cause: Cannot modify application policy.

Action: Check the logs for errors.
Level: 1

Type: WARNING

Impact: Security

JPS-04035: AttributeName {0} supplied should start with alphabet or an underscore. Name cannot contain characters other than alphanumeric and/or underscores.

Cause: AttributeName {0} supplied should start with alphabet or an underscore. Name cannot contain characters contain other than alphanumeric and/or underscores.

Action: Ensure attribute name is of correct datatype.
Level: 1

Type: WARNING

Impact: Security

JPS-04036: Function Name {0} supplied should start with alphabet or an underscore. Name cannot contain characters other than alphanumeric and/or underscores.

Cause: Function Name {0} supplied should start with alphabet or an underscore. Name cannot contain characters contain other than alphanumeric and/or underscores.

Action: Ensure function name is of correct datatype.
Level: 1

Type: WARNING

Impact: Security

JPS-04037: Name '{0}' starts or ends with whitespace.

Cause: Object name should not start with or end with whitespace.

Action: Ensure object name has no whitespace in the beginning and end.
Level: 1

Type: WARNING

Impact: Security

JPS-04038: Object name only contains whitespace.

Cause: Object name should not only contain whitespace.

Action: Ensure object name doesn't only contain whitespace.
Level: 1

Type: WARNING

Impact: Security

JPS-04039: Application "{0}", Deleting {1} entries under "{2}", Maximum remaining re-tries {3}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-04080: Scanning of system policy failed. Reason {0}

Cause: Scan of system policy failed.

Action: Check the system policy setup and the provider setup.
Level: 1

Type: WARNING

Impact: Security

JPS-04081: Policy store purge thread interrupted. Reason {0}.

Cause: Purge thread interrupted in policy caching.

Action: Check the policy setup and the provider setup
Level: 1

Type: WARNING

Impact: Security

JPS-04082: Deletion of system policy failed. Reason {0}

Cause: Deletion of system policy failed.

Action: Provide legal non empty values for policy name
Level: 1

Type: WARNING

Impact: Security

JPS-04083: Creation of system policy failed. Reason {0}

Cause: Creation of system policy failed.

Action: Provide legal non empty values for policy name
Level: 1

Type: WARNING

Impact: Security

JPS-04084: Migration of application policy failed. Reason: {0}.

Cause: Exception in migration of application policy

Action: Check application policy setup or contact system administrator
Level: 1

Type: WARNING

Impact: Security

JPS-04085: Migration of codebase policy failed. Reason: {0}.

Cause: Exception in migration of codebase policy

Action: Check codebase policy setup or contact system administrator
Level: 1

Type: WARNING

Impact: Security

JPS-04086: Could not perform isPolicyModified. Reason {0}

Cause: Is policy modification check failed.

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Security

JPS-04089: Could not get policy cache count. Reason {0}

Cause: Could not retrieve policy cache count.

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Security

JPS-04090: The policy store property {0} is invalid or not defined.

Cause: The policy store property {0} was invalid or not defined.

Action: Check the configuration of this property.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04091: Application {0} is being deployed with policy migration option set to {1}, start policy migration.

Cause: Start application policy migration

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-04092: Application {0} is being deployed with policy migration option set to neither OVERWRITE nor MERGE, skip policy migration.

Cause: Skip application policy migration

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-04093: Application policy migration for application {0} is completed successfully.

Cause: Complete application policy migration

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-04094: Start removing application policies for Application {0}.

Cause: Start application policy removal

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-04095: Application policy removal for application {0} is completed successfully.

Cause: Complete application policy removal

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-04096: Application policies for application {0} was NOT removed in application undeployment with jps.policystore.removal set to OFF.

Cause: Skip application policy removal

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-04097: Application {0} is being deployed without existing application policies found in static deployment, start policy migration.

Cause: Start application policy migration in static deployment

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-04098: Start codebase policy migration for application {0}.

Cause: Start codebase policy migration

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-04099: Codebase policy migration for {0} is completed successfully.

Cause: Complete codebase policy migration

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-04100: Cannot create application role "{0}".

Cause: Encountered two roles with identical names.

Action: Modify a role to have a distinct name.
Level: 1

Type: WARNING

Impact: Security

JPS-04101: Cannot create application role "{0}".

Cause: Failed to complete persist operation while creating an application role.

Action: Refer to the base exception in logs to resolve the issue.
Level: 1

Type: WARNING

Impact: Security

JPS-04102: Cannot create application role. Cause: Invalid Argument -- Multiple role categories supplied for single application role

Cause: Persist operation failed because more than one role category supplied for create role

Action: Ensure supplied parameters are correct.
Level: 1

Type: WARNING

Impact: Security

JPS-04110: Cannot delete application role "{0}". Cause: Application role not found.

Cause: Could not find an application role in the application policy.

Action: Check the name of the application role.
Level: 1

Type: WARNING

Impact: Security

JPS-04111: Cannot delete application role "{0}".

Cause: Could not remove application role from policy store.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04112: Cannot delete application role "{0}".

Cause: Could not remove application role "{0}" because it may be in use; this role is a member of one or more other application roles (nested role hierarchy).

Action: Flatten the nested role hierarchy, and then remove the desired role. Alternatively, remove the application role using the option force set to true.
Level: 1

Type: WARNING

Impact: Security

JPS-04113: Cannot delete application role "{0}".

Cause: Could not remove application role "{0}" because it may be in use, or contains enterprise groups or enterprise users.

Action: Remove the enterprise groups and enterprise users from the application role, or remove the application role using the option force set to true.
Level: 1

Type: WARNING

Impact: Security

JPS-04114: Cannot delete application role "{0}".

Cause: Could not remove application role "{0}" because it may be in use; this role has one or more permissions granted to it.

Action: Revoke the permission(s) from the application role, and then remove the role. Alternatively, remove the application role using the option force set to true.
Level: 1

Type: WARNING

Impact: Security

JPS-04120: Cannot add principal to application role.

Cause: Encountered an internal policy store error.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04121: Cannot add principal to application role.

Cause: Could not find application role in the application policy context.

Action: Ensure the application role is present in the application policy.
Level: 1

Type: WARNING

Impact: Security

JPS-04122: Cannot add principal to application role.

Cause: Found that principal {0} is already a member of the application role {1}.

Action: Correct the principal name.
Level: 1

Type: WARNING

Impact: Security

JPS-04123: Cannot add principal to the application role.

Cause: Attempted to insert an application role as a member of itself.

Action: Correct the application role principal name. The containment in the role hierarchy must be cycle-free.
Level: 1

Type: WARNING

Impact: Security

JPS-04124: The application role {0} added to {1} has no GUID defined.

Cause: The application role {0} added to {1} has no GUID defined.

Action: Ensure the application role has GUID before adding it as a member of an application role.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04125: Application Role {0} granted to role category {1} cannot be found in application {2}

Cause: Application Role {0} granted to role category {1} cannot be found in application {2}

Action: Ensure application role exists before assigning it to a role category
Level: 1

Type: WARNING

Impact: Security

JPS-04130: Cannot remove principal from application role.

Cause: Encountered an internal policy store error.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04131: Cannot remove principal from application role; cannot find application role "{0}" in application policy context.

Cause: Could not find the specified application role in the application policy context.

Action: Correct the application role name.
Level: 1

Type: WARNING

Impact: Security

JPS-04132: Cannot remove principal from application role; principal "{0}" is not member of application role "{1}".

Cause: See error message.

Action: Correct the principal role name.
Level: 1

Type: WARNING

Impact: Security

JPS-04140: Cannot complete application role search because search expression "{0}" is incorrect.

Cause: Found an invalid search pattern.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04141: Cannot complete application role search because of internal error {0}.

Cause: Encountered an internal policy store error while searching the policy store.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04142: Cannot complete application role search because search role attribute "{0}" is incorrect.

Cause: Could not complete the search because the application role attribute {0} was invalid.

Action: Supply a valid role attribute name.
Level: 1

Type: WARNING

Impact: Security

JPS-04143: Cannot find application role "{0}".

Cause: Could not find application role in the application policy context.

Action: Supply the name of an existing application role name.
Level: 1

Type: WARNING

Impact: Security

JPS-04144: Cannot get granted application role for principal "{0}".

Cause: Encountered an internal policy store error.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04145: Cannot get all application roles for application "{0}".

Cause: Encountered an internal policy store error.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04146: Cannot complete application role search because search role attribute name is null.

Cause: Could not complete the search because the role attribute name was NULL.

Action: Provide a non-null role attribute name.
Level: 1

Type: WARNING

Impact: Security

JPS-04147: Cannot get members of application role "{0}".

Cause: Could not find application role in the application policy context.

Action: Supply the name of an existing application role name.
Level: 1

Type: WARNING

Impact: Security

JPS-04148: Exception when converting "{0}" to number, msg is "{1}".

Cause: Exception when converting {0} to number, msg is {1}

Action: Only number is allowed
Level: 1

Type: WARNING

Impact: Security

JPS-04150: Cannot alter application role {0} since multiple entries found for the application name:{1} query: {2} and actual result is {3}.

Cause: Encountered the policy store error {0}.

Action: Check the error details to resolve the issue.
Level: 1

Type: WARNING

Impact: Security

JPS-04151: Cannot alter application role.

Cause: Could not find application role {0} in the application policy context.

Action: Provide an existing application role name.
Level: 1

Type: WARNING

Impact: Security

JPS-04153: In Domain {0}, Application {1} is not present.

Cause: Application not found in the policystore

Action: Check the name of the application in the policystore.
Level: 1

Type: WARNING

Impact: Security

JPS-04154: Refresh of application policy failed. Reason {0}

Cause: Refresh of application policy failed.

Action: Check the application policy setup and the provider setup
Level: 1

Type: WARNING

Impact: Security

JPS-04155: Scanning of application policy failed. Reason {0}

Cause: Scan of application policy failed.

Action: Check the application policy setup and the provider setup
Level: 1

Type: WARNING

Impact: Security

JPS-04156: RoleCategory modification attribute "{0}" is invalid.

Cause: Invalid RoleCategory modify attribute

Action: Check whether the attribute you are trying to modify is valid or not.
Level: 1

Type: WARNING

Impact: Security

JPS-04157: RoleCategory {0} already exists.

Cause: The role category already exists.

Action: Supply a different role category name.
Level: 1

Type: WARNING

Impact: Security

JPS-04158: RoleCategory {0} does not exists

Cause: The role category does not exist.

Action: Supply a different role category name.
Level: 1

Type: WARNING

Impact: Security

JPS-04159: Role category search value: {0}, is invalid for matcher type: {1}

Cause: The role category search query has invalid parameter value

Action: Modify the search query and supply correct parameter value.
Level: 1

Type: WARNING

Impact: Security

JPS-04160: Cannot find PermissionSet {0}.

Cause: Could not find PermissionSet in policy store.

Action: Provide the name of a valid PermissionSet.
Level: 1

Type: WARNING

Impact: Security

JPS-04161: Search for PermissionSet {0} by name yielded more than one result.

Cause: Found a duplicate PermissionSet name in search context.

Action: Ensure that all PermissionSet names in the current search context are distinct.
Level: 1

Type: WARNING

Impact: Security

JPS-04162: PermissionSet {0} already exists in policy store.

Cause: Permission Set already exists.

Action: Create a PermissionSet with a different name.
Level: 1

Type: WARNING

Impact: Security

JPS-04163: PermissionSet {0} cannot have empty ResourceActions.

Cause: PermissionSet {0} has empty ResourceActions.

Action: Ensure PermissionSet has ResourceActions.
Level: 1

Type: WARNING

Impact: Security

JPS-04164: Resource {0} referenced by MemberResources not found in application {1}.

Cause: Resource {0} referenced by MemberResources not found in application {1}.

Action: Ensure the Resource exists in the PolicyStore.
Level: 1

Type: WARNING

Impact: Security

JPS-04165: ResourceType {0} referenced by MemberResource {1} not found in application {2}.

Cause: ResourceType {0} referenced by MemberResource {1} not found in application {2}.

Action: Ensure the ResourceType exists in the PolicyStore.
Level: 1

Type: WARNING

Impact: Security

JPS-04166: MemberResource {0} of type {1} does not have actions defined.

Cause: MemberResource {0} of type {1} does not have actions defined.

Action: Ensure the MemberResource has valid actions.
Level: 1

Type: WARNING

Impact: Security

JPS-04167: MemberResource {0} of type {1} has actions defined.

Cause: MemberResource {0} of type {1} has actions defined.

Action: Ensure the MemberResource does not have actions.
Level: 1

Type: WARNING

Impact: Security

JPS-04168: PermissionSet {0} cannot be created without ResourceActions.

Cause: PermissionSet {0} cannot be created without ResourceActions.

Action: Create a PermissionSet with ResourceActions.
Level: 1

Type: WARNING

Impact: Security

JPS-04169: ResourceAction {0} used to modify PermissionSet {1} has invalid actions for ResourceType {2}.

Cause: ResourceAction {0} used to modify PermissionSet {1} has invalid actions for ResourceType {2}.

Action: Modify PermissionSet using a ResourceAction that has valid actions.
Level: 1

Type: WARNING

Impact: Security

JPS-04173: The resource type {0} is not found in store

Cause: Unsupported Resource Type {0}.

Action: Check Resource Type.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04179: The resource type reference for resource {0} is not found in the application {1}. Hence using the first occurrence

Cause: The resource type reference for resource {0} is not found in the application {1}. Hence using the first occurrence.

Action: Ensure the ResourceType reference exists for every resource.
Level: 1

Type: WARNING

Impact: Security

JPS-04190: Cannot find resource.

Cause: Could not find resource in the resource store.

Action: Modify your search query.
Level: 1

Type: WARNING

Impact: Security

JPS-04191: Cannot find unregistered resource finder for resource type "{0}".

Cause: Could not find a registered resource finder for the resource type.

Action: Provide a resource finder implementation for the resource type, and register it with JPS.
Level: 1

Type: WARNING

Impact: Security

JPS-04192: Cannot load resource finder with provider name "{0}".

Cause: Found an incorrect implementation: argumentless public constructor is missing.

Action: Revisit the implementation to provide an argumentless public constructor.
Level: 1

Type: WARNING

Impact: Security

JPS-04193: Cannot load resource finder with provider name "{0}" and class "{1}".

Cause: Could not load resource finder class: error encountered while reading a registered class file for resource finder.

Action: Check the configuration of the class property in jps-config.xml.
Level: 1

Type: WARNING

Impact: Security

JPS-04194: Cannot initialize resource finder with provider name "{0}" and class name "{1}".

Cause: Found an error while initializing a registered class for resource finder.

Action: Check the configuration of the class property in jps-config.xml.
Level: 1

Type: WARNING

Impact: Security

JPS-04195: Cannot load the resource finder with provider "{0}".

Cause: Found an error in external resource finder configuration: a required property was missing.

Action: Check the configuration of the class property in jps-config.xml.
Level: 1

Type: WARNING

Impact: Security

JPS-04198: Resource name = {0} in application = {1} has a non existing resource type = {2} ignoring this resource.

Cause: Resource name = {0} in application = {1} has a non existing resource type = {2} ignoring this resource.

Action: Ensure the ResourceType exists for every resource.
Level: 1

Type: WARNING

Impact: Security

JPS-04200: Cannot grant policy due to a policy store internal error.

Cause: Encountered a policy store error.

Action: Check the error details to resolve the issue.
Level: 1

Type: WARNING

Impact: Security

JPS-04201: Cannot grant permission(s). Grant already exists for grantee {0}.

Cause: Permissions already granted to grantee.

Action: Grant a different set of permissions.
Level: 1

Type: WARNING

Impact: Security

JPS-04202: Cannot revoke policy.

Cause: Encountered an internal policy store error while revoking a policy.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04203: Cannot revoke permission.

Cause: Found that a permission has not been granted.

Action: Provide the appropriate permission to the grantee.
Level: 1

Type: WARNING

Impact: Security

JPS-04204: Cannot revoke permissions.

Cause: Found that permissions have not been granted.

Action: Provide the appropriate permissions to the grantee.
Level: 1

Type: WARNING

Impact: Security

JPS-04205: Cannot revoke permissions.

Cause: Found that permissions have not been granted to principals.

Action: Provide the appropriate permissions to principals.
Level: 1

Type: WARNING

Impact: Security

JPS-04206: Cannot revoke permissions.

Cause: Found that permissions have not been granted to code source.

Action: Correct the code source grantee.
Level: 1

Type: WARNING

Impact: Security

JPS-04207: Matching Grantee not found: {0}.

Cause: Found that permissions have not been granted to principals or code source.

Action: Correct the list of principals and code source in the grantee, or revoke permissions granted to this grantee.
Level: 1

Type: WARNING

Impact: Security

JPS-04208: Cannot modify policy due to a policy store internal error.

Cause: Encountered an internal policy store error while modifying the policy store.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04209: Cannot modify property {0}.

Cause: Could not modify a property.

Action: Supply the name of a property that can be modified.
Level: 1

Type: WARNING

Impact: Security

JPS-04210: Modification code {0} is invalid.

Cause: Found an unsupported modification code.

Action: Ensure that the modification code is ADD, REMOVE, or REPLACE.
Level: 1

Type: WARNING

Impact: Security

JPS-04211: Cannot query, update, or delete Object with type "{0}" and name "{1}".

Cause: Attempted to query, update, or delete an invalid policy store object.

Action: Ensure that the object to be queried, updated, or deleted belongs to the appropriate policy domain
Level: 1

Type: WARNING

Impact: Security

JPS-04212: PermissionSet "{0}" is in use, cannot delete.

Cause: Permission set already existed.

Action: Permission set with the same name cannot be created. Use different name.
Level: 1

Type: WARNING

Impact: Security

JPS-04213: Cannot modify a grant with an empty permission entry.

Cause: Encountered empty permission entry list while modifying a grant

Action: Pass a non empty permission entry list while modifying a grant
Level: 1

Type: WARNING

Impact: Security

JPS-04216: Cannot grant/revoke permissions because type "{0} " is not known.

Cause: Resource type validation for Permission set failed

Action: Check whether the grant's permission's resourcetype is provisioned in the policystore.
Level: 1

Type: WARNING

Impact: Security

JPS-04217: Grant/revoke failed for grantee "{0}", permission class "{1}", resource name "{2}", permission actions "{3}", resource type "{4}". Reason: permission actions is not a subset of resource type actions " {5}".

Cause: Resource type validation for Permission set failed

Action: Check whether the actions in the Permission are valid actions for the resource type provisioned in the policy store.
Level: 1

Type: WARNING

Impact: Security

JPS-04218: Grant/revoke failed for grantee "{0}", permission class "{1}", resource Name "{2}", permission actions "{3}", resource type "{4}". Reason: permission class is not equal to resource type matcher class " {5}".

Cause: Resource type validation for Permission set failed

Action: Check whether the matcher class in the Permission is valid for the resource type provisioned in the policy store.
Level: 1

Type: WARNING

Impact: Security

JPS-04219: The action {0} is invalid for resource type {1}.

Cause: The action {0} is invalid for resource type {1}.

Action: Check the ResourceActionsEntry parameter.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04220: Cannot search because the search query "{0}" was empty (has no child query).

Cause: The search query {0} was empty (has no child query).

Action: Provide a non-empty search query in.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04221: Cannot search because the grant search query "{0}" has illegal object type for search property "{1}".

Cause: The grant search query {0} has wrong object type in search value for search property {1}.

Action: Provide an object type corresponding to the search property.
Level: 1

Type: WARNING

Impact: Security

JPS-04222: Cannot search because the search query was null for "{0}" .

Cause: The search query was null for {0} .

Action: Provide a non-null search query .
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04227: The object name {0} is invalid.

Cause: The object name {0} is invalid.

Action: Pass a correct object name in.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04300: Cannot save policy.

Cause: Could not save policy. Cause {0}.

Action: Check the log files and resolve the error.
Level: 1

Type: ERROR

Impact: Security

JPS-04301: Cannot read from policy store. Reason is {0}, {1}

Cause: Could not read from the policy store.

Action: Check the log files and resolve the error.
Level: 1

Type: ERROR

Impact: Security

JPS-04302: Cannot read from policy store.

Cause: Could not find the location property {1} in instance {0}.

Action: Ensure the location is set to a valid policy store file.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04303: Cannot read from policy store.

Cause: Could not find value for system property '{0}' or for location property '{2}' in instance '{1}'.

Action: Ensure the location is set to a valid policy store file.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04304: Policy store instance descriptor {0}, location value {1} is ignored.

Cause: Could not find value for the system property '{0}', which overrides the descriptor property {1} in the policy store service instance.

Action: Unset the system property so that the location is picked up from configuration in jps-config.xml.
Level: 1

Type: WARNING

Impact: Configuration

JPS-04410: Cannot create JACC module policy context "{0}" for application {1}.

Cause: Could not create application policy because found two application module contexts with identical names.

Action: Ensure that all application module context names are distinct.
Level: 1

Type: WARNING

Impact: Security

JPS-04411: Cannot create application "{0}" JACC module policy context "{1}".

Cause: Could not create application module policy; persist operation failed.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04412: Cannot delete JACC module "{0}".

Cause: Could not find JACC policy context to delete.

Action: Check the JACC policy context name.
Level: 1

Type: WARNING

Impact: Security

JPS-04413: Cannot delete JACC module policy context "{0}".

Cause: Could not delete JACC policy; persist operation failed.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04420: Application policy context name is missing from application role {0}.

Cause: Could not find application policy context in the application role principal.

Action: Ensure that the application role principal has an application context.
Level: 1

Type: WARNING

Impact: Security

JPS-04421: Administrator role name is invalid.

Cause: Found an invalid administrator role name.

Action: Correct the name of the administrator role.
Level: 1

Type: WARNING

Impact: Security

JPS-04422: Policy is malformed.

Cause: Found system policy that granted permissions to application role(s).

Action: Grants to application roles are not allowed in a system policy. Remove such grants.
Level: 1

Type: WARNING

Impact: Security

JPS-04423: Application role name "{0}" is invalid.

Cause: Found invalid application role name {0}.

Action: Verify that the application role name conforms with the role name syntax.
Level: 1

Type: WARNING

Impact: Security

JPS-04502: Java SSO Login

Cause: This was JSSO page title.

Action: No action needed.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-04503: Enter your single sign-on username and password.

Cause: User name and password were required for logging into JSSO.

Action: Enter a valid user name and password.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-04504: Username

Cause: This was JSSO login user name.

Action: No action needed.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-04505: Password

Cause: This was JSSO login user password.

Action: No action needed.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-04506: Login

Cause: Submit button.

Action: Press submit.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-04507: Cancel

Cause: Cancel button.

Action: Press cancel to abort login.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-04508: Failed.

Cause: JSSO login failed.

Action: Check user name and password used for login.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04509: The maximum number of login attempts is exceeded. Contact the application administrator, or retry after {0} minutes.

Cause: Maximum login attempts was exceeded.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04510: Incorrect username or password.

Cause: User name or password was invalid.

Action: Check the user name and password used for login.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04511: Java SSO Application Error.

Cause: Encountered and internal error.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04512: application error

Cause: Encountered and internal error.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04513: The Java SSO application is not properly configured.

Cause: The Java SSO application was not correctly configured.

Action: Reconfigure the application.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04514: Configuration error: {0}.

Cause: The Java SSO application was not correctly configured.

Action: Reconfigure the application.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04515: Usage arguments:

Cause: Defines the keytool usage.

Action: See error message.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-04516: No key type for algorithm.

Cause: The algorithm key type was not specified.

Action: Configure the algorithm key type.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04517: Key does not match any known algorithm.

Cause: The given key did not match the corresponding algorithm.

Action: Reconfigure the algorithm key type.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04518: The number of JSSO cookies is zero or invalid.

Cause: Could not find JSSO cookie in header.

Action: Login again or contact the system administrator.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-04519: The number of Oracle Access Manager cookies is zero or invalid.

Cause: Could not find Oracle Access Manager cookie in header.

Action: Login again or contact the system administrator.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-04520: Token type is invalid: expected type is COOKIE_TOKEN, but found {0}.

Cause: The token type configured was invalid: it should be COOKIE_TOKEN.

Action: Reconfigure the token type to a valid value.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04521: The JSSO property {0} is not set.

Cause: JSSO property was not correctly configured.

Action: Reconfigure the property to a correct value.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04522: The authentication type {0} is invalid.

Cause: JSSO did not support this authentication type.

Action: Reconfigure the type to a supported type.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04523: Token is no longer valid.

Cause: The incoming token was no longer valid.

Action: Login again.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04524: Cannot create token from JSSO cookie.

Cause: Could not create token from the JSSO cookie; cookie may have expired.

Action: Login again.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04525: The number of cookies is zero or the invalid number {0}.

Cause: Could not find at least one cookie in the request.

Action: Login again.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04526: Token has invalid version number.

Cause: Token had invalid version number.

Action: Login again.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04527: Token has an invalid format.

Cause: Token was corrupted or had invalid format.

Action: Login again.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04528: An error occurred while encoding JSSO token.

Cause: Could not encode JSSO token.

Action: Specify a valid, supported encoding.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04529: Cannot verify signature in the JSSO token.

Cause: Could not verify signature: the token was tampered with, or the signature algorithm was invalid.

Action: Specify a supported signature algorithm.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04530: Algorithm is unsupported.

Cause: Specified algorithm was unsupported.

Action: Check documentation for the list of supported algorithms.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04531: Error creating cipher.

Cause: Could not create cipher.

Action: Check documentation for the list of supported cipher algorithms.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04532: JSSO logout URL is not configured.

Cause: The logout URL was not configured or invalid.

Action: Check the logout URL configuration properties, and reconfigure it to a valid URL.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04533: JSSO has encountered an unexpected error.

Cause: An internal error occurred.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04534: JSSO symmetric key is missing.

Cause: The symmetric key configuration was missing.

Action: Ensure that the properties "custom.sso.cred.key" and "custom.sso.cred.alias" are configured in the service instance, and that the symmetric key is present in the credential store.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04535: Identity name is invalid.

Cause: User identity was invalid or missing.

Action: Provide a valid user identity.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04536: The token name {0} is missing in request object.

Cause: Token name was missing in the request object.

Action: Ensure that the token name is present in the request object.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04537: No token name is specified for token collector {0}.

Cause: Token collector was invalid or missing.

Action: Configure a valid token collector with the property "idm.token.collector.class".
Level: 1

Type: ERROR

Impact: Configuration

JPS-04538: The request object class is invalid.

Cause: The request object class was invalid.

Action: Ensure that the request object is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04539: Token collector is not properly initialized.

Cause: Could not initialize the token collector.

Action: Ensure that the token collector is correctly configured and initialized.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04540: The token asserter is not properly initialized.

Cause: Could not initialize the token asserter.

Action: Ensure that the token asserter is correctly configured and initialized.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04541: Cannot find authenticated identity.

Cause: Authentication failed.

Action: Provide a valid identity.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04542: The token collector class {0} is not properly configured in the configuration file.

Cause: Token collector class was missing.

Action: Configure a valid token collector class with the property "idm.token.collector.class".
Level: 1

Type: ERROR

Impact: Configuration

JPS-04543: No login module is configured for application.

Cause: Could not find configured login module.

Action: Configure a login module in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04544: The subject of the identity is invalid.

Cause: Subject was missing.

Action: Ensure that the valid Subject is present.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04545: Cannot verify the Subject {0}.

Cause: Could not verify Subject.

Action: Check the user credentials.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04546: The configuration (idm.subject.loginmodule.disabled=true) specifies that the Subject is populated by the token asserter.

Cause: Could not find Subject asserter.

Action: Configure an asserter to use a login module that returns a valid Subject.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04547: The token type {0} is not properly configured in the configuration file.

Cause: Could not find token type configuration.

Action: Configure a token type in the service instance with the property "idm.token.type property".
Level: 1

Type: ERROR

Impact: Configuration

JPS-04548: The token asserter class {0} is not properly configured in the configuration file.

Cause: Could not find token asserter class configuration.

Action: Configure a token asseter class in the service instance with the property "idm.token.asserter.class".
Level: 1

Type: ERROR

Impact: Configuration

JPS-04549: Token is no longer valid.

Cause: Found invalid or expired token.

Action: Check that the token is valid and has not expired.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04550: Token type is invalid: expected type is HEADER_TOKEN, but found {0}.

Cause: Token type was invalid: it should be HEADER_TOKEN.

Action: Reconfigure the token type to a valid type.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04551: The number of OSSO headers is zero or an invalid number.

Cause: Could not find OSSO header in HTTP request.

Action: Login again, or contact the system administrator.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04552: The required Oracle Access Manager property {0} is missing or invalid.

Cause: A required Oracle Access Manager property was missing or invalid.

Action: Configure the property "access.sdk.install.path" in the service instance in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04553: The user identity {0} for Oracle Access Manager is invalid.

Cause: The user identity for Oracle Access Manager was invalid.

Action: Login again.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04554: The user password for Oracle Access Manager is invalid.

Cause: The user password for Oracle Access Manager was invalid.

Action: Login again.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04555: The user {0} is not logged in to Oracle Access Manager. The error is {1}.

Cause: The user was not logged in Oracle Access Manager.

Action: Login again.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04556: The user {0} is not authorized to access a resource type authentication in Oracle Access Manager.

Cause: The user was not logged in Oracle Access Manager.

Action: Login again.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04557: Invalid parameter {0} supplied. Cannot be null or empty.

Cause: Invalid parameter {0} supplied. Cannot be null or empty.

Action: Ensure the parameter is not null or empty.
Level: 1

Type: WARNING

Impact: Requests/Responses

JPS-04558: The SSO service is not properly configured: {0}.

Cause: The SSO service is not properly configured: {0}.

Action: Check the SSO Service configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04559: Failed to create the {0} token. Cause: {1}.

Cause: Failed to create the {0} token. Cause: {1}.

Action: Re-login.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04560: SSO provider cannot initiate SSO process: {0}.

Cause: SSO provider cannot initiate SSO process: {0}.

Action: Check the SSO Service configuration.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04561: Invalid parameter {0} supplied. Cannot be null.

Cause: Invalid parameter {0} supplied. Cannot be null.

Action: Ensure the parameter is not null.
Level: 1

Type: WARNING

Impact: Requests/Responses

JPS-04601: Cannot obtain audit service for policy store.

Cause: Could not query audit service about audit logging level for policy store messages.

Action: Ensure that auditing is configured correctly.
Level: 1

Type: WARNING

Impact: Security

JPS-04602: Cannot log policy management event to the audit service.

Cause: Could not log policy management audit messages to the audit service.

Action: Ensure that auditing is configured correctly in your environment and application.
Level: 1

Type: WARNING

Impact: Security

JPS-05500: Cannot create the user manager MBean.

Cause: Could not create the user manager MBean.

Action: Check errors in log files and contact the domain administrator.
Level: 1

Type: ERROR

Impact: Configuration

JPS-05501: Cannot create the role manager MBean.

Cause: Could not create the role manager MBean.

Action: Check the log files for errors and contact domain administrator.
Level: 1

Type: ERROR

Impact: Configuration

JPS-05502: Cannot create the identity store MBean.

Cause: Could not create the identity store MBean.

Action: Check log files and contact the domain administrator.
Level: 1

Type: ERROR

Impact: Configuration

JPS-05513: Failed to determine realms to migrate file {0}. Reason {1}.

Cause: Failed determine realms to migrate file {0}. Reason {1}.

Action: Check log files and try again.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-05521: Invalid jaas.login.controlFlag {0} found for {1} service instance. Valid values should be {2}.

Cause: Invalid jaas.login.controlFlag {0} found for {1} service instance. Valid values should be {2}.

Action: Use a valid value.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-05542: Bootstrap credential store context missing

Cause: Could not find bootstrap credstore context

Action: Contact aystem administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-05546: Bootstrap credential store service missing

Cause: Could not find bootstrap credstore service

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-05626: Bootstrap credential already present in store

Cause: Credential already present in the store

Action: use different map name or key name for the credential
Level: 1

Type: WARNING

Impact: Compliance

JPS-06000: The source context {0} is missing in jps-config.xml.

Cause: While migrating a security store, found that the context, specified as source {0}, did not exist in jps-config.xml.

Action: Provide a context for source that is present in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-06001: The destination context {0} is missing in jps-config.xml.

Cause: While migration of a security store, found that the context, specified as destination {0}, did not exist in jps-config.xml.

Action: Provide a context for destination that is present in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-06002: Cannot clean the destination credential store. Reason {0}.

Cause: A codebase grant was found without the required permissions.

Action: Set the right permissions to the codebase grant.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06003: Cannot migrate credential folder/key {0}/{1}.Reason {2}.

Cause: Cannot migrate this credential.

Action: Verify that the credential is correctly specified.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06004: Cannot migrate an unknown user. Reason {0}.

Cause: Cannot migrate this user.

Action: Verify that the user is correctly specified.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06005: Cannot get password of user {0}. Reason {1}.

Cause: Cannot get this user password.

Action: Verify that the password is correctly specified.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06006: Cannot migrate user {0}. Reason {1}.

Cause: Cannot migrate this user name.

Action: Verify that the user name is correctly specified.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06007: Cannot migrate an unknown role. Reason {0}.

Cause: Cannot migrate this role.

Action: Verify that the role is correctly specified.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06008: Cannot migrate role {0}. Reason {1}.

Cause: Cannot migrate this role name.

Action: Verify that the role name is correctly specified.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06009: Cannot migrate any member of role {0}. Reason {1}.

Cause: Cannot migrate members.

Action: Verify that the members are correctly specified.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06010: Cannot migrate an unknown member of role {0}. Reason {1}.

Cause: Cannot migrate this member.

Action: Verify that the member is correctly specified.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06011: Cannot migrate member {0} of role: {1}. Reason {2}.

Cause: Cannot migrate this member name.

Action: Verify that the member name is correctly specified.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06012: cannot migrate a global grant. Reason {0}.

Cause: Could not migrate a global grant. Reason {0}.

Action: Verify that the grant is correctly specified.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06013: cannot migrate an application grant. Reason {0}.

Cause: Could not migrate an application grant. Reason {0}.

Action: Verify that the application grant is correctly specified.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06014: Cannot migrate an indirect password for {0}. Reason {1}.

Cause: Could not migrate an indirect password due to an exception.

Action: Verify that the indirect password is correctly specified.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06015: Cannot migrate an indirect password for {0} because the specified realm is null.

Cause: Could not migrate an indirect password because the given realm was null.

Action: Provide a non-null realm.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06016: Cannot migrate an indirect password for {0} because the specified user name is null.

Cause: Could not migrate an indirect password because the given user name was null.

Action: Provide a non-null user name.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06017: Cannot migrate an indirect password for {0} because the specified realm does not exist.

Cause: Could not migrate an indirect password because the input realm does not exist.

Action: Provide an existing realm.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06018: Cannot migrate an indirect password for {0} because the specified user does not exist.

Cause: Could not migrate an indirect password because the input user does not exist.

Action: Provide an existing user.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06019: The identity store associated with context {0} is missing in jps-config.xml.

Cause: While migration of a policy store, found that the context, specified as containing the associated identity store {0}, did not exist in jps-config.xml.

Action: Provide a context to associate identity store that is present in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-06020: The principal class {0} specified in the source policy store cannot be loaded. Reason {1}.

Cause: Could not load a class. Reason {0}.

Action: Ensure the class is in the class path.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06021: Cannot migrate the credentials in the folder {0}. Reason: {1}.

Cause: Cannot migrate the credentials in this folder.

Action: Check the folder in the source credential store.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06022: Cannot determine the folder to be migrated.

Cause: The credential store has more than one folder and the folder to be migrated was not defined.

Action: Specify the folder to be migrated.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06023: The input file {0} specified for migration or upgrade is not valid.

Cause: The file {0} was non-readable, empty, or did not exist.

Action: Provide a valid file.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06024: Cannot initialize the destination identity store.

Cause: One or more required configuration properties were not be properly defined.

Action: Check the configuration of the destination identity store.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06025: There are undefined credential properties for the destination identity store.

Cause: One or more required configuration properties for credentials were not defined.

Action: Check the configuration of the destination identity store.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06026: Cannot get credentials for the destination identity store from the domain credential store.

Cause: Credentials were not found in the domain credential store.

Action: Ensure that the domain credential store has the appropriate credentials.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06027: Cannot migrate the specified realm.

Cause: The specified realm was not found in the source store.

Action: Specify a valid realm name.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06028: The required identity store property {0} required for migration is undefined.

Cause: A property required for migration was not configured in the identity store.

Action: Specify the missing configuration property.
Level: 1

Type: ERROR

Impact: Other

JPS-06029: JAZN properties cannot be read from config file {0}.

Cause: JAZN properties could not be read from config file {0}.

Action: Check the configuration file and try again.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06030: The required JAZN property {0} could not be read.

Cause: A required JAZN property {0} could not be read.

Action: Check the configuration file and try again.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06031: No application is configured in the source policy store.

Cause: No application was configured in the source policy store.

Action: Check the source policy store.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06032: Unable to determine the application policy to migrate.

Cause: More than one application was configured in the source policy store.

Action: Check the source policy store.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06033: The source credential store contains no credentials.

Cause: The requested credential was not found in the credential store.

Action: Ensure that the credential store has the requested credential.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06034: The folder {0} is missing in the credential store.

Cause: The requested map name was not found in the credential store.

Action: Ensure that the credential store contains the requested map name.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06035: The destination file {0} already exists; the existing LDIF file will not be appended or overwritten.

Cause: The destination file is already present.

Action: Delete the destination file, or provide the name of a non-existing file.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06036: Cannot determine the default realm to migrate file {0}. Reason {1}.

Cause: An internal error occurred while determining the default realm.

Action: Check log files and try again.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-06037: Cannot initialize the source credential store.

Cause: The configuration for the credential store was invalid.

Action: Verify that the credential store configuration is correct and try again.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06038: Cannot initialize the destination credential store.

Cause: The configuration for the credential store was invalid.

Action: Verify that the credential store configuration is correct and try again.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06039: Cannot migrate property {0} of user {1}. Reason {2}.

Cause: Cannot migrate property {0} for user {1}. Reason {2}.

Action: Check the log files and retry migrating.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06040: Cannot migrate property {0} of role {1}. Reason {2}.

Cause: Cannot migrate property {0} for role {1}. Reason {2}.

Action: Check the log files and retry migrating.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06041: The switch or keyword " {0} " is not applicable to " {1} = {2} ".

Cause: One or more optional switches or keywords were invalid.

Action: Refer to the command documentation for the correct usage.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06042: Invalid scope for migration.

Cause: Value of scope keyword was invalid.

Action: Enter only one of the defined values/alias of scope as a value for the keyword scope.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06043: The source application is undefined but required to migrate application-specific policies.

Cause: Optional keyword srcApp was not defined.

Action: Specify, in the parameter srcApp, the value of the application whose policies are to be migrated.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06044: Cannot create the temporary file {0}.

Cause: Could not write the XML file.

Action: Check permissions or disk space in the java.io.tmpdir directory.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-06045: Cannot parse the file {0}.

Cause: Could not parse the XML file.

Action: Check that the file is present in the java.io.tmpdir directory, and that it contains well-formed XML.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-06046: Cannot delete the file {0}.

Cause: The temp file could not be deleted.

Action: Check that the file is not being accessed by other applications.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-06047: Cannot migrate user credentials of user {0}.

Cause: The source identity store was configured not to give cleartext password.

Action: Configure the source identity store to obfuscate password.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06048: Null values passed in for username or application stripes.

Cause: The user name or the application stripe was null.

Action: The user name must not be null. The list of application names must be null if only global policies are to be extracted.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-06049: Application list is empty. Only global policies will be extracted.

Cause: The list of applications was empty.

Action: Only global policies are collected.
Level: 1

Type: NOTIFICATION

Impact: Programmatic

JPS-06050: file {0} was not found

Cause: The xml file was not found.

Action: Check if the file is present in the java.io.tmpdir directory.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-06051: Processing of privilege roles is supported only when migrating an XML Policy store to an LDAP Policy Store.

Cause: Processing of privilege roles was supported only when migrating an XML policy store to an LDAP policy store.

Action: Make sure that the source store is XML-based and the destination store is LDAP-based.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06052: Error while processing a PermissionSet grant.

Cause: Error encountered while processing permissionSet grant.

Action: Check log files for details.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06053: Processing privilege roles failed. Cause {0}

Cause: The processing of privilege roles failed.

Action: Check log files for detials.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06054: Error in creating resourceTypes in destination store. Cause {0}

Cause: Error encountered while creating resourceTypes in destination store.

Action: Check log files for detials.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06055: Location of the ldif file containing resourceType definitions cannot be null.

Cause: Location of the LDIF file containing resourceType definitions was null or not found.

Action: Provide the absolute path for the resource file.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06056: Error while reading resource type file {0}.

Cause: Error encountered while reading the resource type file {0}.

Action: Ensure that the file exists and that it has the expected format.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06057: Resource type name or matcher class cannot be null.

Cause: Resource type name or matcher class was null.

Action: Provide a valid name and matcher class for the resource type.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06058: Permission class {0} with more than one matching resource type found.

Cause: Permission class had more than one matching resource type.

Action: Ensure that the a permission class has just one matching resource type.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06059: A grant entry containing {0} as one of principals has multiple principal entries. This entry cannot be processed.

Cause: A grant for a privilege role had multiple principals.

Action: Ensure that the privilege role grant has a single principal.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06060: The resource type definition file is missing.

Cause: The resource type definition file was not found.

Action: Provide the absolute path location for the resource definition file in LDIF format when using the option procPrivOption.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06061: The switch or keyword " {0} " is not defined for " {1} = {2} ".

Cause: One or more optional switches or keywords were invalid.

Action: Refer to the command documentation for the correct usage.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06062: Application role {0} corresponding to a member application role not defined.

Cause: Application role not defined.

Action: Check logs for detials.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06063: No Matching resource type definition found for permission class {0}.

Cause: Permission class representing resource granted to a privilleged role does not have corresponding resource type definition.

Action: Make sure a permission class has one matching resource type.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06064: Error getting the application role {0} from the source policy store

Cause: The application role was either not present or defined multiple times.

Action: Check the source policy store and make sure that the application role is uniquely defined.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06065: Report generation failed

Cause: .

Action: .
Level: 1

Type: ERROR

Impact: Configuration

JPS-06066: Invalid value for mode.

Cause: Invalid value for mode

Action: Make sure the value for mode is valid
Level: 1

Type: ERROR

Impact: Security

JPS-06067: {0} config file either not found or not a valid file.

Cause: {0} config file either not found or not a valid file

Action: Make sure to provide a valid config file
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06068: Unable to read configurations from jazn config file : {0}.

Cause: Unable to read configurations from jazn data file : {0}.

Action: Check the jazn data file.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06069: Provider referred from jazn config file {0} is of type XML and not LDAP.

Cause: Provider referred from jps-config file {0} is of type XML and not LDAP.

Action: Refer to a provider of type LDAP.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06070: Unable to read policies from policy store.

Cause: Unable to read policies from policy store.

Action: Check the policy store.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06071: Unable to read global policies from policy store.

Cause: Unable to read global policies from policy store.

Action: Check the policy store.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06072: Unable to read permissions for grantee {0} from policy store.

Cause: Unable to read permissions for grantee {0} from policy store.

Action: Check the policy store.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06073: Unable to read realm policies from policy store.

Cause: Unable to read realm policies from policy store.

Action: Check the policy store.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06074: Unable to read realm policies from realm {0} from policy store.

Cause: Unable to read realm policies from realm {0} from policy store.

Action: Check the policy store.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06075: Unsupported resource type file format. Use either an ldif file or a jazn-data with only resource type definitions.

Cause: Unsupported resource type file format.

Action: Use either an ldif file or a jazn-data with only resource type definitions.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06076: A Resource Type referred by {0} is expected to have a matching class {1} but has {2}.

Cause: A Resource Type referred by a Permission is expected to have the same matching class as defined in the Permission

Action: Make sure a permission class has one matching resource type with the same class name.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06077: A Resource Type referred by {0} is not defined.

Cause: A Resource Type referred by a Permission is not defined.

Action: Make sure a permission class has one matching resource type.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06078: Cannot migrate keystore/stripe {0}/{1}.Reason {2}.

Cause: Cannot migrate the keystore in this stripe.

Action: Check the keystore and stripe in the source keystore service.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06079: Cannot determine the stripe to be migrated.

Cause: The keystore service has more than one stripes and the stripe to be migrated was not defined.

Action: Specify the stripe to be migrated.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06080: The source keystore service contains no keystore within the given application stripe.

Cause: The requested keystore was not found in the keystore service.

Action: Ensure that the keystore service has the requested keystore.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06082: Cannot initialize the source keystore service.

Cause: The configuration for the keystore service was invalid.

Action: Verify that the keystore service configuration is correct and try again.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06083: Cannot initialize the destination keystore service.

Cause: The configuration for the keystore service was invalid.

Action: Verify that the keystore service configuration is correct and try again.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06084: Cannot clean the destination keystore service. Reason {0}.

Cause: A codebase grant was found without the required permissions.

Action: Set the right permissions to the codebase grant.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06085: Resource types not defined for the application {0}.

Cause: Resource Types not found for the application {0}.

Action: Define the resource types for the application {0}.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06086: Cannot upgrade policies for application {0}.

Cause: Exception during policy upgradation.

Action: Check the Causing exception and fix the error.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06087: Duplicate permissions: {0} present in grant in source.

Cause: Duplicate permissions are present in a grant in source.

Action: See error message.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06088: Duplicates principals:{0} present in grant in source.

Cause: Duplicates principals are present in a grant in source.

Action: See error message.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06089: Duplicate grant {0} present in source.

Cause: Duplicate grants are present in source.

Action: See error message.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06090: Duplicate app-role {0} present in source.

Cause: Duplicate app-roles are present in source.

Action: See error message.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06091: Duplicate member {0} present in an app-role in source.

Cause: Duplicate members are present in an app-role in source.

Action: See error message.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06100: Policy Store version {0} and Oracle Platform Security Services Version {1} are not compatible.

Cause: The policy store version and the version of Oracle Platform Security Services does not match

Action: Upgrade your binaries or your policy store.
Level: 1

Type: ERROR

Impact: Security

JPS-06101: Cannot initialize the source auditstore service.

Cause: The configuration for the audit store was invalid.

Action: Verify that the audit store configuration is correct and try again.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06102: Cannot initialize the destination auditstore service.

Cause: The configuration for the audit store was invalid.

Action: Verify that the audit store configuration is correct and try again.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06103: Default Admin Role {0} not found in the policy domain {1} in the destination policy store

Cause: The destination policy store may not conform to latest version and need to be upgraded

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-06104: Default Admin Role {0} not found in the application {1} in the destination policy store

Cause: The destination policy store may not conform to latest version and need to be upgraded

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-06105: Default system Admin Role {0} not found in the destination policy store

Cause: The destination policy store may not conform to latest version and need to be upgraded

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-06106: Instantiation of bootstrap credential store specified in file {0} failed. Reason {1}

Cause: The configuration provided is not valid.

Action: Provide a valid configuration file which has configuration for bootstrap credential.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06107: Instantiation of credential store at path {0} failed. Reason: {1}

Cause: An underlying exception prevented initialization of credentials file.

Action: Check the cause of the exception and fix it.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06108: Import/Export of keys failed. Reason: {0}

Cause: An underlying exception prevented exporting/importing of key.

Action: Check the cause of the exception and fix it.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06109: Cannot read key from key file in Directory {0}. Reason {1}.

Cause: An underlying exception prevented reading of key.

Action: Check the cause of the exception and fix it.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06110: Key file Directory {0} does not have write permissions.

Cause: Key file directory not writable.

Action: Change the permissions of the directory.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06111: Key file Directory {0} does not have read permissions.

Cause: Key file directory is not readable.

Action: Change the permissions of the directory.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06112: Key file Directory {0} does not exist.

Cause: The path specified either donnot exist or is not a directory.

Action: Provide a valid directory.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06113: Configuration file {0} is not valid. It is either not present or does not have read permissions.}

Cause: The file is either not present or is not readable.

Action: Provide a valid file.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06114: Key is not present in the key file in Directory {0}.

Cause: Export might have not completed successfully.

Action: Provide key file that has key in it.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06115: Empty DB username information. Please make sure to provide the correct jdbcUser info.

Cause: Empty DB username information.

Action: Please make sure to provide the correct jdbcUser info.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06116: Empty DB password information. Please make sure to provide the correct jdbcPassword info.

Cause: Empty DB password information.

Action: Please make sure to provide the correct jdbcPassword info.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06117: Empty JDBC host and port information. Please make sure to provide the correct jdbcUrl info.

Cause: Empty DB host and port information.

Action: Please make sure to provide the correct jdbcUrl info.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06118: Empty JDBC Driver information. Please make sure to provide the correct jdbcDriver info.

Cause: Empty JDBC Driver information.

Action: Please make sure to provide the correct jdbcDriver info.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06119: Recovery failed. Key backup not Found.

Cause: No import was performed or import was not sucessfull.

Action: import the key(s) again.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06500: Alias already exists in the keystore

Cause: The specified alias name already existed in the keystore.

Action: Specify a unique alias name.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06501: Keystore {0} in stripe {1} already exists

Cause: Keystore with the given name already existed.

Action: Specify a unique keystore name.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06502: Failed to read keystore

Cause: Could not read the keystore.

Action: Verify the keystore location and that sufficient permissions are in place.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06503: Failed to write keystore

Cause: Could not read the keystore.

Action: Verify the keystore location, that sufficient permissions are in place and that sufficient disk space is available.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06504: Failed to perform cryptographic operation

Cause: The java provider did not support this cryptographic operation.

Action: Verify that a provider that supports this algorithm/padding/key is configured.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06505: Failed to generate certificate request

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06506: Key generation algorithm not supported

Cause: An unsupported key-pair generation algorithm was used.

Action: Specify a supported key-pair generation algorithm.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06507: Root CA import failed.

Cause: The root CA certificate and/or key file was malformed.

Action: Verify that the root CA certificate and/or key files is valid.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06508: Failed to generate CA signed certificate.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06509: The keystore has been moved or deleted.

Cause: The keystore did not exist at this location.

Action: Verify that the location of keystore is correct.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06510: The keystore location property is not configured, or the configured value {0} is invalid.

Cause: The keystore location was not specified.

Action: Check the value of the location attribute.
Level: 1

Type: ERROR

Impact: Configuration

JPS-06511: Cannot create keystore at {0}.

Cause: Could not create the keystore.

Action: Verify the store location, that sufficient permissions are in place, and that sufficient disk space is available.
Level: 1

Type: ERROR

Impact: Configuration

JPS-06513: Failed to save keystore. Reason {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06514: Opening of file based keystore failed.

Cause: Keystore could not be opened

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-06515: Refreshing of file based keystore failed. Reason {0}

Cause: Refresh of keystore failed

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-06516: Failed to get credential store. Reason {0}

Cause: Could not get credential store.

Action: Verify credential store is correctly configured and initialized.
Level: 1

Type: WARNING

Impact: Compliance

JPS-06517: Failed to create the keystore {0} in stripe {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06518: Keystore {0} in stripe {1} does not exist.

Cause: Could not perform this operation since the keystore did not exist.

Action: Specify an existing keystore name for this operation.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06519: Failed to get/set credential in credstore. Reason {0}

Cause: Credential store was not available or permissions were not in place.

Action: Verify credential store is correctly configured and permissions are granted.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06520: Failed to encode/decode certificate or public key.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06521: Invalid admin password, operation not permitted

Cause: Invalid admin password was specified.

Action: Specify the correct admin password to perform this operation.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06522: Failed to roll over keystore master key.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06523: Failed to reset keystore administrator password.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06524: Failed to read certificates from keystore.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06525: Failed to list/renew expiring certificates.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06526: Failed to list policy violations in keystore.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06527: Invalid keystore name {0}

Cause: Invalid keystore name was specified.

Action: Specify a keystore name that is not null or empty and contains only alphanumeric characters.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06528: Invalid alias value {0}

Cause: Invalid alias value was specified.

Action: Specify an alias value that is not null or empty and contains only alphanumeric characters.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06529: Passwords must not be null or empty.

Cause: Password was specified as null or empty.

Action: Specify a non null or non empty password for a keystore protected by password.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06530: Invalid stripe value {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06531: Operation failed, keystore password does not match

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06532: Failed to delete the keystore {0} in stripe {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06533: Algorithm {0} not supported

Cause: The algorithm was not supported by keystore.

Action: Check the list of supported algorithms and specify one of them.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06534: Keystore master key roll-over failed.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06535: Failed to generate secret key with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06536: Failed to import secret key for keystore {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06537: Failed to change password for keystore {0} in stripe {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06538: Cannot set password for trusted certificate entry.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06539: Operation failed, key password does not match

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06540: Failed to change password for key with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06541: Invalid keystore entry type {0}

Cause: The keystore entry type was invalid for this operation.

Action: Check the list of supported keystore entry types from documentation.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06542: Failed to list aliases for keystore {0} in stripe {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06543: Invalid Distinguished Name {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06544: Failed to generate key pair for alias {0} keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06545: The expected keystore entry with alias "{0}" does not exist for keystore "{1}" in stripe "{2}".

Cause: The alias value either did not exist or did not point to the specified keystore entry type.

Action: Specify a valid alias value that points to the specified keystore entry type.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06546: Failed to get secret key with alias {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06547: Failed to get certificate(s) with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06548: Failed to export certificate request for key with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06549: No corresponding key pair found for this certificate

Cause: The alias value did not point to the matching key pair for this certificate

Action: Specify a valid alias value that points to a key pair whose public key matches that of the certificate.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06550: Failed to parse the certificate chain

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06551: Failed to import the key store entry with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06552: Failed to delete the key store entry with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06553: Cannot perform this operation on domain trust store

Cause: The operation was not supported for domain trust store.

Action: Check product documentation to see the operations permitted on domain trust store.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06554: Cannot perform this operation on demo CA keystore

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06555: Mismatch between the values of key aliases and key passwords

Cause: There should be equal number of entries for key aliases and key passwords

Action: Ensure that key aliases and key passwords are equal in number.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06556: Keystore to be imported is not valid

Cause: The keystore file being imported was either empty or of invalid format.

Action: Ensure that the keystore being imported is of valid format.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06557: Mismatch between the values of CSF maps and keys

Cause: There should be equal number of entries for CSF maps and CSF keys

Action: Ensure that CSF maps and keys are either both null, or are equal in number.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06558: Mismatch between the values of key alias/password and CSF map/key

Cause: There should be equal number of entries for key alias/password and CSF map/key

Action: Ensure that key alias/password and CSF map/key are equal in number.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06559: Keystore type {0} not supported

Cause: The keystore type was not supported.

Action: Check the list of supported keystore types and specify one of them.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06560: Failed to import the keystore {0} in stripe {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06561: Failed to export the keystore {0} in stripe {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06562: Failed to load the keystore.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06563: Failed to save the keystore.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06564: Method not implemented

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06565: Invalid keystore protection parameter

Cause: The specified keystore protection type was not supported.

Action: Ensure that the keystore protection type is a password.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06566: No trusted certificate found with this alias

Cause: The specified alias did not refer to a trusted certificate.

Action: Ensure that the alias refers to a trusted certificate in the keystore.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06567: Unsupported key type

Cause: The key type was not supported.

Action: Ensure that key is either private key or secret key.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06568: Insufficient permissions for this operation

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06569: Keystore {0} in app stripe {1} does not exist

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06570: Failed to set keystore policy

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06571: Failed to delete keystore policy

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06572: Null policy name/value not allowed

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06573: Failed to list keystore policies

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06574: Invalid key parameters

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06575: Certificate import failed.

Cause: The public key in the certificate does not match the one in the keystore.

Action: Ensure that the certificate is imported into the alias used for generating certificate request.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06576: Failed to read {0} with alias {1}.

Cause: Failed to read {0} with alias {1}.

Action: Contact the administrator.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06577: Failed to create private key {0}.

Cause: Failed to create private key {0}.

Action: Contact the administrator.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06578: Cert with alias {0} was invalid.

Cause: Cert with alias {0} was invalid.

Action: Contact the administrator.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06579: Failed to read keystore data.

Cause: Failed to read keystore data.

Action: Contact the administrator.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06580: Failed to check keystore integrity.

Cause: Failed to check keystore integrity.

Action: Contact the administrator.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06581: Failed to load certificates from the keystore.

Cause: Failed to load certificates from the keystore.

Action: Contact the administrator.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06582: Failed to get trusted certs.

Cause: Failed to get trusted certs

Action: Contact the administrator.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06583: Failed to check if audit is enabled.

Cause: Keystore audit events logging was not enabled.

Action: Check the audit configuration to ensure auditing enabled.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06584: Failed to log audit record.

Cause: Keystore audit event logging failed.

Action: Contact the administrator.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06585: Created keystore {0} in stripe {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06586: Deleted keystore {0} in stripe {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06587: Successfully listed keystores in stripe {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06588: Failed to list keystores in stripe {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06589: Successfully got the handle to keystore {0} in stripe {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06590: Failed to get the handle to keystore {0} in stripe {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06591: Successfully changed the password of keystore {0} in stripe {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06592: Successfully generated key pair with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06593: Successfully generated secret key with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06594: Successfully changed password for key with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06595: Successfully listed aliases for keystore {0} in stripe {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06596: Successfully listed properties for secret key with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06597: Failed to list properties for secret key with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06598: Successfully got certificate(s) with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06599: Successfully exported certificate request for key with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06600: Failed to export certificate(s) with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06601: Successfully exported certificate(s) with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06602: Successfully imported the key store entry with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06603: Successfully deleted the key store entry with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06604: Successfully imported the keystore {0} in stripe {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06605: Successfully exported the keystore {0} in stripe {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06606: Could not create keystore service instance. Reason {0}

Cause: Could not create keystore service instance

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-06607: The keystore service DN {0} is missing in the store; the target DN must be pre-configured.

Cause: The expected keystore DN {0} was missing.

Action: Configure this DN during the bootstrap process.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06608: The farm DN property {0} is invalid or not defined.

Cause: The farm name property {0} was invalid or not defined.

Action: Check the configuration of this property.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06609: The keystore is not initialized.

Cause: The keystore was not loaded.

Action: Load the keystore before trying this operation.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06610: Keystore {0} did not exist.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06611: The keystore service instance {0} was not initialized.

Cause: Keystore service was not completely initialized.

Action: Wait until data source is available and try again later.
Level: 1

Type: ERROR

Impact: Configuration

JPS-06612: The properties for keystore {0} in stripe {1} were read successfully

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06613: Supported key sizes could not be determined for this algorithm.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06614: Failed to delete key store {0} in stripe {1}.

Cause: Deletion of domain trust store or the demo CA key store was not permitted.

Action: Choose a different key store.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06615: Failed to delete alias {0} in key store {1} in stripe {2}.

Cause: Deletion of demo CA key was not permitted.

Action: Choose a different key alias.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06616: Missing certificate chain.

Cause: Certificate chain was null.

Action: Specify a valid certificate chain.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06617: Successfully retrieved the attribute {0} from the keystore {1} in stripe {2}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06618: Failed to retrieve attribute {0} from the keystore {1} in stripe {2}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06619: Key store file keystores.xml integrity check failed.

Cause: File keystore.xml has been manually edited.

Action: Restore the keystore file to the last working backup and try again.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06620: Key store file integrity checker initialization failed. Reason {0}

Cause: Problem using the bootstrap credential store service.

Action: Check the bootstrap credential store configuration.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06621: Cannot change password of a permission protected key store

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06622: Cannot change key password of a permission protected key store

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-07000: Provide a valid jps configuration file.

Cause: The jps configuration file was invalid.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-07001: Provide a valid application name.

Cause: Application ID was invalid.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-07002: Provide a valid jazn-data file. .

Cause: The jazn-data file was invalid.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-07003: Provide a valid folder name.

Cause: The patch delta folder was invalid.

Action: Provide a valid folder for generating patch delta files.
Level: 1

Type: ERROR

Impact: Security

JPS-07004: ApplicationPolicy object is null/empty.

Cause: ApplicationPolicy object was null

Action: Make sure to create a not null ApplicationPolicy object
Level: 1

Type: ERROR

Impact: Security

JPS-07005: The "{0} " jazn data file does not exists.

Cause: Jazn data file does not exists.

Action: Make sure to provide an existing jazn-data file.
Level: 1

Type: ERROR

Impact: Security

JPS-07006: "{0}" Not a folder. Please provide a valid folder.

Cause: Not a folder.

Action: Make sure to provide a valid folder.
Level: 1

Type: ERROR

Impact: Security

JPS-07007: "{0}" folder does not exists

Cause: The folder does not exists.

Action: Make sure to provide an existing folder.
Level: 1

Type: ERROR

Impact: Security

JPS-07008: The {0} jps configuration file does not exist.

Cause: The jps configuration file does not exists.

Action: Make sure to provide an existing jps configuration file.
Level: 1

Type: ERROR

Impact: Security

JPS-07009: The "{0}" folder for generating patch delta files does not exist.

Cause: The folder to generate the patch delta files does not exists.

Action: Make sure to provide an existing folder.
Level: 1

Type: ERROR

Impact: Security

JPS-07010: The AppRole "{0}" cannot be created. Cause {1} .

Cause: The approle could not be created.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-07011: The AppRole object is null while persisting to Addition Safe Changes.

Cause: The required parameter was null.

Action: Ensure to provide a valid AppRole Object.
Level: 1

Type: ERROR

Impact: Security

JPS-07012: The ResourceType object is null while persisting to Addition Safe Changes.

Cause: The required parameter was null.

Action: Enusre to provide a valid ResourceType Object.
Level: 1

Type: ERROR

Impact: Security

JPS-07013: The AppRole list is null/empty while persisting to Addition Safe Changes.

Cause: The required parameter was null.

Action: Ensure to provide a valid AppRole List.
Level: 1

Type: ERROR

Impact: Security

JPS-07014: The Resource object is null while persisting to Addition Safe Changes.

Cause: The required parameter was null.

Action: Ensure to pass a valid Resource object.
Level: 1

Type: ERROR

Impact: Security

JPS-07015: The PermissionSet object is null while persisting to Addition Safe Changes.

Cause: The required parameter was null.

Action: Ensure to provide a valid PermissionSet object.
Level: 1

Type: ERROR

Impact: Security

JPS-07016: The Association object is null while persisting to Addition Safe Changes.

Cause: The required parameter was null.

Action: Ensure to provide a valid Association object.
Level: 1

Type: ERROR

Impact: Security

JPS-07017: Internal Error.

Cause: That was an internal error.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-07018: Application Role: "{0}" cannot be added. Reason {1} .

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07019: Permission Set: "{0}" cannot be added. Reason {1}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07020: Resource: "{0}" cannot be added. Reason {1}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07021: Resource Type "{0}" cannot be added. Reason {1}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07022: Member: name "{0}" ,class "{1}" cannot be granted an application role: "{2}". Reason {3}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07023: Resource Actions: name "{0}", actions "{1}" cannot be added in permission set: "{2}". Reason {3}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07024: Permission: "{0}" cannot be granted to grantee "{1}". Reason {2}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07025: Permission set: "{0}" cannot be granted to grantee "{1}". Reason {2}

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07026: Application Role: "{0}" cannot be modified. Reason {1}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07027: Permission Set: "{0}" cannot be modified. Reason {1}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07028: Resource: "{0}" cannot be modified. Reason {1}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07029: Resource Type: "{0}" cannot be modified. Reason {1}

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07030: Application Role: "{0}" cannot be deleted. Reason {1}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07031: Permission Set: "{0}" cannot be deleted. Reason {1}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07032: Resource: "{0}" cannot be deleted. Reason {1}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07033: Resource Type: "{0}" cannot be deleted. Reason {1}

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07034: Member: name "{0}", class "{1}" cannot be revoked from application role: "{2}". reason {3}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07035: Resource Actions: name "{0}", actions "{1}" cannot be deleted from permission set: "{2}". Reason {3}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07036: Permission: "{0}" cannot be revoked from grantee: "{1}". Reason {2}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07037: Permission set: "{0}" cannot be revoked from grantee: "{1}". Reason {2}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07038: Additions cannot be read. Reason {0}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07039: Deletions cannot be read. Reason {0}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07040: Modifications cannot be read. Reason {0}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07041: The argument "{0}" is not applicable for phase "{1}".

Cause: Extra argument provided

Action: Please provide only relavent parameters
Level: 1

Type: ERROR

Impact: Security

JPS-07042: Illegal value provided for argument "{0}".

Cause: Illegal value provided for an argument

Action: Please provide a legal value for the argument.
Level: 1

Type: ERROR

Impact: Security

JPS-07043: Cannot find application policy {0}.

Cause: Could not find application policy {0}.

Action: Check the application name passed.
Level: 1

Type: ERROR

Impact: Security

JPS-07044: Cannot retrieve newline application policy.

Cause: Could not retrieve newline application policy.

Action: Check the application name passed.
Level: 1

Type: ERROR

Impact: Security

JPS-07045: Cannot retrieve baseline application policy.

Cause: Could not retrieve baseline application policy.

Action: Check the application name passed.
Level: 1

Type: ERROR

Impact: Security

JPS-07046: Cannot retrieve customer application policy.

Cause: Could not retrieve customer application policy.

Action: Check the application name passed.
Level: 1

Type: ERROR

Impact: Security

JPS-07047: This artifact is newly added in patch version.

Cause: The required parameter was null.

Action: Enusre to provide a valid RoleCategory Object.
Level: 1

Type: ERROR

Impact: Security

JPS-07056: Addition conflicts initialization failed.

Cause: Internal Error occured when attempting to load Addition Conflicts from Patch Delta.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Security

JPS-07057: Modification conflicts initialization failed.

Cause: Internal Error occured when attempting to load Modification Conflicts from Patch Delta.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Security

JPS-07058: Deletion conflicts initialization failed.

Cause: Internal Error occured when attempting to load Deletion Conflicts from Patch Delta.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Security

JPS-07059: Conflicting addition changes in the patch have been identified. Silent Apply process halted. Resolve the conflicts and Apply the patch.

Cause: Addition conflicts are not resolved.

Action: Resolve addition conflicts.
Level: 1

Type: ERROR

Impact: Security

JPS-07060: Conflicting modification changes in the patch have been identified. Silent Apply process halted. Resolve the conflicts and Apply the patch.

Cause: Modification conflicts are not resolved.

Action: Resolve modification conflicts.
Level: 1

Type: ERROR

Impact: Security

JPS-07061: Conflicting deletion changes in the patch have been identified. Silent Apply process halted. Resolve the conflicts and Apply the patch.

Cause: Deletion conflicts are not resolved.

Action: Resolve deletion conflicts.
Level: 1

Type: ERROR

Impact: Security

JPS-07062: Additions Writer initialization failed for resolve.

Cause: Additions Writer initialization failed for resolve.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Security

JPS-07063: Deletions Writer initialization failed for resolve.

Cause: Additions Writer initialization failed for resolve.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Security

JPS-07064: Modifications Writer initialization failed for resolve.

Cause: Modification Writer initialization failed for resolve.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Security

JPS-07065: Dependency artifact {0} is not resolved for artifact {1}.

Cause: Dependency artifact {0} is not resolved for artifact {1}.

Action: Check the resolutions.
Level: 1

Type: ERROR

Impact: Security

JPS-07066: Dependency artifact {0} resolution is not valid for artifact {1}.

Cause: Dependency artifact {0} resolution is not valid for artifact {1}.

Action: Check the resolutions.
Level: 1

Type: ERROR

Impact: Security

JPS-07067: Artifact not resolved {0}.

Cause: Artifact not resolved {0}.

Action: Check the resolutions.
Level: 1

Type: ERROR

Impact: Security

JPS-07069: Deletion of member {0} of permission set {1} renders the permission set empty.

Cause: Deletion of member will render Permission set empty

Action: Check the resolutions.
Level: 1

Type: ERROR

Impact: Security

JPS-07070: The argument {0} is not passed

Cause: The required argument is not passed.

Action: Provide the required argument.
Level: 1

Type: ERROR

Impact: Security

JPS-07071: Deletion Changes in the patch have been identified. Applying the changes will permanently delete policy store artifacts. Silent Apply process halted. Review the changes and Apply the patch.

Cause: Deletion conflicts are not resolved.

Action: Resolve deletion conflicts.
Level: 1

Type: ERROR

Impact: Security

JPS-07077: Cannot generate report. Reason {0}

Cause: Report generation failed.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Security

JPS-07078: Report file {0} path is invalid.

Cause: Report file specified is not a valid file path.

Action: Specify a valid file path.
Level: 1

Type: ERROR

Impact: Security

JPS-07079: Report file {0} cannot be created in the given directory.

Cause: The directory doesn't have write permission.

Action: Specify a directory which has write permission.
Level: 1

Type: ERROR

Impact: Security

JPS-07080: Report file {0} already exists.

Cause: Report file exists.

Action: Specify a non existing file.
Level: 1

Type: ERROR

Impact: Security

JPS-07500: Trust protocol {0} is not supported.

Cause: Requested trust protocol is not supported

Action: Provide correct trust protocol
Level: 1

Type: ERROR

Impact: Security

JPS-07501: Token context is invalid.

Cause: Token context object is empty or does not contain required parameters

Action: Check token context object contains required parameter
Level: 1

Type: ERROR

Impact: Security

JPS-07502: Trust Service token provider {0} is not found.

Cause: Token provider not configured in the jps-config.xml file

Action: Check jps-config.xml file and verify that requested token provider is correctly configured
Level: 1

Type: ERROR

Impact: Security

JPS-07503: Trust Service token provider class name {0}.

Cause: Token provider class loading

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07504: Trust Service Keystore initialization failed.

Cause: Keystore is is missing or not configured correctly

Action: Check the keystore and ensure that necessary certificates and keys are present
Level: 1

Type: ERROR

Impact: Security

JPS-07505: Trust service provider protocol {0}

Cause: Trust Service provider protocol information

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07506: Token context creation failed.

Cause: Incorrct protocol or associated provider configuration.

Action: Check protocol and associated provider configuration
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07507: Token issue operation

Cause: Trust service token issue opertion.

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07508: Token issue operation failed.

Cause: Trust service token issue opertion failed.

Action: Check provider configuration
Level: 1

Type: ERROR

Impact: Security

JPS-07509: Invalid token operation

Cause: Invalid Trust Service token opertion.

Action: Check invoked operation name
Level: 1

Type: ERROR

Impact: Security

JPS-07510: Token validate operation.

Cause: Trust Service validate token opertion.

Action: No action required
Level: 1

Type: ERROR

Impact: Security

JPS-07511: Validate operation failed.

Cause: Trust service token validate opertion failed.

Action: Check provider configuration
Level: 1

Type: ERROR

Impact: Security

JPS-07512: Missing token issuer identity.

Cause: Token issuer identity missing.

Action: Provide token issuer identity
Level: 1

Type: ERROR

Impact: Security

JPS-07513: Invalid subject confirmation method.

Cause: Invalid subject confirmation method.

Action: Provide correct subject confirmation method
Level: 1

Type: ERROR

Impact: Security

JPS-07514: Token audience restriction condition check failed.

Cause: Invalid token audience condition.

Action: Check the audience condition
Level: 1

Type: ERROR

Impact: Security

JPS-07515: Token signature validation failed.

Cause: Invalid token signature.

Action: Check token integrity and verify signature using correct certificate
Level: 1

Type: ERROR

Impact: Security

JPS-07516: Invalid token.

Cause: Invalid token.

Action: Check token integrity.
Level: 1

Type: ERROR

Impact: Security

JPS-07517: Input token is not an instance of GenericToken class.

Cause: Input token is not an instance of GenericToken class.

Action: Check the token object class
Level: 1

Type: ERROR

Impact: Security

JPS-07518: Input token is not an instance of UsernameToken class

Cause: Input token is not an instance of UsernameToken class.

Action: Check the token object class
Level: 1

Type: ERROR

Impact: Security

JPS-07519: Setting subject conformation method failed.

Cause: Invalid token object.

Action: Check the token object
Level: 1

Type: ERROR

Impact: Security

JPS-07520: Token signing failed.

Cause: Token signing key is unavailable.

Action: Check the keystore and verify that signing key is present
Level: 1

Type: ERROR

Impact: Security

JPS-07521: Token signature is not available.

Cause: Unsigned token.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07522: Token is not valid yet {0}

Cause: Token is not valid yet.

Action: Check the token validity start date.
Level: 1

Type: ERROR

Impact: Security

JPS-07523: Token has expired {0}

Cause: Token has expired.

Action: Check the token validity end date.
Level: 1

Type: ERROR

Impact: Security

JPS-07524: Certificate is unavailable {0}

Cause: Certificate is not available.

Action: Check the keystore and ensure that the certificate is present.
Level: 1

Type: ERROR

Impact: Security

JPS-07525: Private key is unavailable

Cause: Private key is not available.

Action: Check the keystore and ensure that the private key is present.
Level: 1

Type: ERROR

Impact: Security

JPS-07526: Initializing provider

Cause: Provider is initiliazing.

Action: None
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07527: Shutting down provider

Cause: Provider is shutting down.

Action: None
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07528: Received unknown token type {0}

Cause: Received token type is unknown.

Action: Check the provided token.
Level: 1

Type: WARNING

Impact: Security

JPS-07529: Received unknown token class {0}

Cause: Token class is unknown.

Action: Check the token class.
Level: 1

Type: WARNING

Impact: Security

JPS-07530: Invalid token type or token not found

Cause: Invalid token authentication type specified.

Action: Check the token authentication type.
Level: 1

Type: WARNING

Impact: Security

JPS-07531: Input token is not an instance of {0}

Cause: Specified insance is not correct.

Action: Check the instance type validity.
Level: 1

Type: WARNING

Impact: Security

JPS-07532: Instance of {0} is invalid

Cause: Specified instance is invalid.

Action: Check the specified instance and ensure that it is correct
Level: 1

Type: WARNING

Impact: Security

JPS-07533: Received empty token byte array

Cause: Given token is empty.

Action: Check the token content and ensure that it is not empty.
Level: 1

Type: ERROR

Impact: Security

JPS-07534: Trust service configuration is not valid

Cause: Invalid configuration parameters.

Action: Check the configuration parameters.
Level: 1

Type: WARNING

Impact: Security

JPS-07535: Using {0} Trust service configuration

Cause: Configuration type used by Trust Service

Action: None
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07536: Token credential missing

Cause: Token signing or validation credential missing.

Action: Provide correct credential.
Level: 1

Type: ERROR

Impact: Security

JPS-07537: Token signature missing

Cause: Token signature missing.

Action: Check the token for integrity.
Level: 1

Type: ERROR

Impact: Security

JPS-07538: The input token is not specified

Cause: Input token not provided.

Action: Check if the token has been provided.
Level: 1

Type: ERROR

Impact: Security

JPS-07539: Token signing method is not specified

Cause: Token signing algorithm parameter missing.

Action: Check the token signing algorithm parameter.
Level: 1

Type: ERROR

Impact: Security

JPS-07540: Token signing method is invalid

Cause: Token signing algorithm parameter invalid

Action: Check the specified token signing algorithm.
Level: 1

Type: ERROR

Impact: Security

JPS-07541: Token signing private key is not specified

Cause: Token signing private key missing.

Action: Check the token signing private key parameter.
Level: 1

Type: ERROR

Impact: Security

JPS-07542: Token signing certificate is not specified

Cause: Token signing certificate missing.

Action: Check the token signing certificate parameter.
Level: 1

Type: ERROR

Impact: Security

JPS-07543: Token signing credential is not specified

Cause: Token signing credential missing.

Action: Check the token signing credential parameter.
Level: 1

Type: ERROR

Impact: Security

JPS-07544: The specified token type is invalid

Cause: The token type is not supported.

Action: Check the token type parameter.
Level: 1

Type: ERROR

Impact: Security

JPS-07601: Complete staging offline deployment for application {0} in {1}

Cause: Complete staging offline deployment for application {0} in {1}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07602: Removal of application policy failed. Reason: {0}.

Cause: Exception in removing application policy

Action: Check application policy setup or contact system administrator
Level: 1

Type: WARNING

Impact: Security

JPS-08000: Subject object {0} is not supported.

Cause: Specified Object type is not supported by the provider for Subject.

Action: Check the document for supported object types.
Level: 1

Type: ERROR

Impact: Security

JPS-08001: Action object {0} is not supported.

Cause: Specified Object type is not supported by the provider for Action.

Action: Check the document for supported object types.
Level: 1

Type: ERROR

Impact: Security

JPS-08002: Resource object {0} is not supported.

Cause: Specified Object type is not supported by the provider for Resource.

Action: Check the document for supported object types.
Level: 1

Type: ERROR

Impact: Security

JPS-08003: Environment object {0} is not supported.

Cause: Specified Object type is not supported by the provider for Environment.

Action: Check the document for supported object types.
Level: 1

Type: ERROR

Impact: Security

JPS-08004: Invalid resource string: {0}.

Cause: The resource string is invalid.

Action: Check the document for the resource string format.
Level: 1

Type: ERROR

Impact: Security

JPS-08005: Subject cannot be null.

Cause: The subject is null.

Action: Use a valid subject.
Level: 1

Type: ERROR

Impact: Security

JPS-08006: Action cannot be null.

Cause: The action is null.

Action: Use a valid action.
Level: 1

Type: ERROR

Impact: Security

JPS-08007: Resource cannot be null.

Cause: The resource is null.

Action: Use a valid resource.
Level: 1

Type: ERROR

Impact: Security

JPS-08008: Action list cannot be null or empty.

Cause: The action list is null or empty.

Action: Use a valid action list.
Level: 1

Type: ERROR

Impact: Security

JPS-08009: Resource list cannot be null or empty.

Cause: The resource list is null or empty.

Action: Use a valid resource list.
Level: 1

Type: ERROR

Impact: Security

JPS-08010: The size of action list and resource list is different.

Cause: The size of action list and resource list is different.

Action: The size of action list should be identical to the size of resource list.
Level: 1

Type: ERROR

Impact: Security

JPS-08011: Subject object {0} is not a valid subject on platform {1}.

Cause: The subject object is not a valid subject on current platform.

Action: Use a valid subject.
Level: 1

Type: ERROR

Impact: Security

JPS-08012: Scope cannot be null or empty.

Cause: Scope is null or empty.

Action: Use a valid scope.
Level: 1

Type: ERROR

Impact: Security

JPS-08013: Query Type cannot be null.

Cause: Query Type is null.

Action: Use a valid Query Type.
Level: 1

Type: ERROR

Impact: Security

JPS-08014: Invalid scope string: {0}.

Cause: The scope string is invalid.

Action: Check the document for the scope string format.
Level: 1

Type: ERROR

Impact: Security

JPS-08015: Invalid search scope string: {0}.

Cause: The search scope in scope string is invalid.

Action: Check the document for the scope string format.
Level: 1

Type: ERROR

Impact: Security

JPS-08016: An error has occurred while processing the PepResponse result.

Cause: An error has occurred while processing the PepResponse results.

Action: Check the policy setup and client code.
Level: 1

Type: ERROR

Impact: Security

JPS-08017: Invalid resource string: {0}. Please provide a fully qualified resource string.

Cause: Fully qualified resource string is required.

Action: Please specify application ID, resource type and resource name.
Level: 1

Type: ERROR

Impact: Security

JPS-08018: The configured policy provider {0} does not implement AzPolicy interface.

Cause: The configured policy provider does not implement AzPolicy interface.

Action: You must configure policy provider that implements AzPolicy interface, e.g. by calling Policy.setPolicy().
Level: 1

Type: ERROR

Impact: Security

JPS-08500: Component audit definition {0} already exists.

Cause: Component audit definition {0} already exists.

Action: Check given component type.
Level: 1

Type: WARNING

Impact: Security

JPS-08501: Failed to create component audit definition {0}. Reason: {1}.

Cause: Failed to create component audit definition {0}. Reason: {1}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08502: Failed to search database mapping table for component {0}. Reason: {1}.

Cause: Failed to search database mapping table for component {0}. Reason: {1}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08503: Failed to search audit definition for component {0}. Reason: {1}.

Cause: Failed to search audit definition for component {0}. Reason: {1}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08504: Failed to search generic attribute groups. Reason: {0}.

Cause: Failed to search generic attribute groups. Reason: {0}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08505: Failed to create database mapping table for component {0}. Reason: {1}.

Cause: Failed to create database mapping table for component {0}. Reason: {1}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08506: Failed to create filter config for component {0}. Reason: {1}.

Cause: Failed to create filter config for component {0}. Reason: {1}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08507: Component audit definition {0} does not exist.

Cause: Component audit definition {0} does not exist.

Action: Check given component type.
Level: 1

Type: WARNING

Impact: Security

JPS-08508: Failed to search filter config for component {0}. Reason: {1}.

Cause: Failed to search filter config for component {0}. Reason: {1}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08509: Failed to update filter config for component {0}. Reason: {1}.

Cause: Failed to update filter config for component {0}. Reason: {1}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08510: The expected audit store DN {0} was missing.

Cause: The expected audit store DN {0} was missing.

Action: Configure this DN during the bootstrap process.
Level: 1

Type: WARNING

Impact: Security

JPS-08511: Audit store was not fully initialized until data source is available.

Cause: Audit store was not fully initialized until data source is available.

Action: Wait and retry later.
Level: 1

Type: WARNING

Impact: Security

JPS-08512: Failed to retrieve value. Reason: {0}.

Cause: Failed to retrieve value. Reason: {0}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08513: Failed to search component types. Reason: {0}.

Cause: Failed to search component types. Reason: {0}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08514: Failed to search system XLF. Reason: {0}.

Cause: Failed to search system XLF. Reason: {0}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08515: Failed to search XLF for component {0}. Reason: {1}.

Cause: Failed to search XLF for component {0}. Reason: {1}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08516: Failed to search system definition. Reason: {0}.

Cause: Failed to search system definition. Reason: {0}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08517: System audit definition already exists.

Cause: System audit definition already exists.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08518: Failed to create system audit definition. Reason: {0}.

Cause: Failed to create system audit definition. Reason: {0}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08519: Error in creating filter tree. Reason: {0}.

Cause: Error in creating filter tree. Reason: {0}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08520: Audit definition {0} is invalid.

Cause: Audit definition {0} is invalid.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08521: Attribute mapping table {0} for component type {1} is invalid.

Cause: Attribute mapping table {0} for component type {1} is invalid.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08522: Filter config {0} for component type {1} is invalid.

Cause: Filter config {0} for component type {1} is invalid.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08523: Component type value {0} is invalid.

Cause: Component type value {0} is invalid.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08524: System definition {0} is invalid.

Cause: System definition {0} is invalid.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08525: Audit definition for component type {0} not found.

Cause: Audit definition for component type {0} not found.

Action: See error message.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-08526: XLF for component type {0} not found.

Cause: XLF for component type {0} not found.

Action: See error message.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-08527: Attribute mapping table for component type {0} not found.

Cause: Attribute mapping table for component type {0} not found.

Action: See error message.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-08528: Filter config for component type {0} not found.

Cause: Filter config for component type {0} not found.

Action: See error message.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-08529: Generic attribute groups not found.

Cause: Generic attribute groups not found.

Action: See error message.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-08530: Failed to search audit definition in audit store. Reason: {0}.

Cause: Failed to search audit definition in audit store. Reason: {0}.

Action: Ensure that the audit store configuration for audit service are correct in jps-config.xml.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08531: Failed to create audit metadata in audit store. Reason: {0}.

Cause: Failed to create audit metadata in audit store. Reason: {0}.

Action: Ensure that the audit store configuration for audit service are correct in jps-config.xml.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08532: Audit definition "{0}" in destination store does not match the one in source store.

Cause: Audit definition "{0}" in destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08533: Component XLF for audit definition "{0}" in destination store does not match the one in source store.

Cause: Component XLF for audit definition "{0}" in destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08534: Generic attribute groups in destination store do not match those in source store.

Cause: Generic attribute groups in destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08535: Attribute group "{0}" in destination store does not match the one in source store.

Cause: Attribute group "{0}" in destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08536: Audit filter config for audit definition "{0}" in destination store does not match the one in source store.

Cause: Audit filter config for audit definition "{0}" in destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08537: Attribute mapping table for audit definition "{0}" in destination store does not match the one in source store.

Cause: Attribute mapping table for audit definition "{0}" in destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08538: Event definitions for audit definition "{0}" in destination store does not match the one in source store.

Cause: Event definitions for audit definition "{0}" in destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08539: Event category "{0}" in destination store does not match the one in source store.

Cause: Event category "{0}" in destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08540: Level list for audit definition "{0}" in destination store does not match the one in source store.

Cause: Level list for audit definition "{0}" in destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08541: Filter preset definition list for audit definition "{0}" in destination store does not match the one in source store.

Cause: Filter preset definition list for audit definition "{0}" in destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08542: Attribute "{0}" in attribute group "{1}" in the destination store does not match the one in source store.

Cause: Attribute "{0}" in attribute group "{1}" in the destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08543: Custom filter preset definition in filter config of audit definition "{0}" in the destination store does not match the one in source store.

Cause: Custom filter preset definition in filter config of audit definition "{0}" in the destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08544: Failed to remove component definition "{0}". Reason: {1}.

Cause: Failed to remove component definition "{0}". Reason: {1}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08545: Failed to update component definition "{0}". Reason: {1}.

Cause: Failed to update component definition "{0}". Reason: {1}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08546: Filter preset definition "{0}" in filter config of audit definition "{1}" in the destination store does not match the one in source store.

Cause: Filter preset definition "{0}" in filter config of audit definition "{1}" in the destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08547: Filter category "{0}" of filter preset definition "{1}" in filter config of audit definition "{2}" in the destination store does not match the one in source store.

Cause: Filter category "{0}" of filter preset definition "{1}" in filter config of audit definition "{2}" in the destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08548: Failed to register to audit service for component "{0}".

Cause: Failed to register component definition "{0}" to audit service. Reason {1}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08549: Audit registration service not available.

Cause: Audit registration service not available.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08550: Audit loader startup failed. Cause: "{0}".

Cause: Audit loader startup failed.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08551: Failed to upgrade audit event definition due to incompatible data mapping. Component type: "{0}".

Cause: Failed to upgrade audit event definition due to incompatible data mapping. Component type: "{0}".

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08552: Upgrade audit event definition with incompatible data mapping. Component type: "{0}".

Cause: Upgrade audit event definition with incompatible data mapping. Component type: "{0}".

Action: See error message.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-08553: Failed to load opss_audit_registration.xml. Reason "{0}".

Cause: Failed to load opss_audit_registration.xml, Reason "{0}".

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-09000: Resource type {0} already in use for {1}.

Cause: Resource type was already in use.

Action: Use a different resource type name.
Level: 1

Type: WARNING

Impact: Security

JPS-09001: Resource matching class name is missing. A subtype must not have its own matching algorithm.

Cause: Resource matching class name was missing.

Action: A subtype must not have its own matching algorithm.
Level: 1

Type: WARNING

Impact: Security

JPS-09002: The parameter {0} of type {1} does not exist.

Cause: This parameter did not exist.

Action: See the log files for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-09003: For the parameter {0} more than expected values found for the Application name:{1}, Policy Domain:{2}, Query Parameter:{3}, Actual results: {4}

Cause: More then expected values for given parameter found.

Action: See the log files for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-09004: For type {0} the modification is not allowed for {1}.

Cause: Modify operation was not allowed.

Action: See the log files for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-09005: For the parameter {0} the given value {1} is invalid.

Cause: The value for the given parameter was invalid.

Action: Provide the valid value for the given paramter.
Level: 1

Type: WARNING

Impact: Security

JPS-09006: Resource {0} already in use for {1}.

Cause: Resource was already in use.

Action: Use a different resource name.
Level: 1

Type: WARNING

Impact: Security

JPS-09007: RoleCategory {0} cannot be deleted

Cause: The role category is referenced by one or more application roles.

Action: Modify the application role(s) definition that reference this role category by removing the role category for the application role.
Level: 1

Type: WARNING

Impact: Security

JPS-09008: Application policy for application {0} does not exist.

Cause: Application policy did not exist.

Action: The application policy must exist. Check the policy store.
Level: 1

Type: WARNING

Impact: Security

JPS-09009: Only limited set of properties are supported for resource action search. See the documentation for more details.

Cause: The property user to search resource action was invalid.

Action: Only limited set of properties are supported for resource action search. See the documentation for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-09010: Cannot create permission set {0} with a non existent resource type {1}.

Cause: Permission set could not be created without resource type.

Action: Resource type must be pre-defined to create the permission set.
Level: 1

Type: WARNING

Impact: Security

JPS-09011: Cannot create permission set {0} with a non existent resource {1}.

Cause: Permission set could not be created without resource.

Action: Resource must be pre-defined to create the permission set.
Level: 1

Type: WARNING

Impact: Security

JPS-09012: Search value cannot be null. It can be null only if MATCHER is ANY.

Cause: Search value was null. It could be null only if MATCHER is ANY.

Action: Verify the search value for the given query.
Level: 1

Type: WARNING

Impact: Security

JPS-09013: This application roles {0} does not belong to this application {1}.

Cause: This application role did not belong to this application.

Action: Ensure this application role belongs to this application.
Level: 1

Type: WARNING

Impact: Security

JPS-09014: The application role {0} cannot have null name or unique name for the application {1}.

Cause: The name or unique name of this application role was null or invalid.

Action: Ensure the name or unique name of this application role is valid.
Level: 1

Type: WARNING

Impact: Security

JPS-09015: Application role does not exist in current application.

Cause: Application role was not found in current application.

Action: Ensure the application role belongs to this application.
Level: 1

Type: WARNING

Impact: Security

JPS-09016: Unknown policy store service type {0}.

Cause: Unknown policy store service type {0}.

Action: Correct the policy store configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09017: Policy entry {0} cannot be found.

Cause: Policy entry {0} cannot be found.

Action: Correct the policy entry.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09018: Policy object {0} cannot be found.

Cause: Policy object {0} cannot be found.

Action: Correct the policy object.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09019: {0} could not be cached.

Cause: {0} did not be cached.

Action: Ensure the Resource has valid actions.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09020: Principal entry class "{0}", name "{1}" cannot be created.

Cause: Principal entry class "{0}", name "{1}" cannot be created.

Action: Ensure that the principal entry class is correct and entry value is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09021: Permission entry class "{0}", target "{1}", action "{2}" cannot be created.

Cause: Permission entry class "{0}", target "{1}", action "{2}" cannot be created.

Action: Ensure that the permission entry class is correct and entry value is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09022: Resource entry type "{0}", resource "{1}" cannot be created.

Cause: Resource entry type "{0}", resource "{1}" cannot be created.

Action: Ensure that the resource entry class is correct and entry value is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09023: Resource type entry name "{0}", matcher class "{1}", provider "{2}" cannot be created.

Cause: Resource type entry name "{0}", matcher class "{1}", provider "{2}" cannot be created.

Action: Ensure that the resource type entry class is correct and entry value is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09024: Resource action entry type "{0}", name "{1}" cannot be created.

Cause: Resource action entry type "{0}", name "{1}" cannot be created.

Action: Ensure that the resource action entry class is correct and entry value is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09025: Permission set entry (name: "{0}", actions: "{1}") cannot be created.

Cause: Permissionset entry name "{0}", actions "{1}" cannot be created.

Action: Ensure that the permissionset entry class is correct and entry value is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09026: Role category entry name "{0}" cannot be created.

Cause: Role category entry name "{0}" cannot be created.

Action: Ensure that the role category entry class is correct and entry value is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09027: Grantee DN was missing for principal {0}.

Cause: Grantee DN was missing for principal {0}.

Action: Check principal value.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09028: Failed to get permission for principal {0}. Reason: {1}.

Cause: Failed to get permission for principal {0}. Reason: {1}.

Action: Check principal value.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09029: Total Time to getPermissions in the Application {0} with {1} number of Grantees is: {2} ms.

Cause: Total Time to getPermissions in the Application {0} with {1} number of Grantees is: {2} ms.

Action: Check log for details.
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-09030: Code signer data {0} cannot be migrated due to limitation in the destination policy store.

Cause: Code signer data {0} cannot be migrated due to limitation in the destination policy store.

Action: Check log for details.
Level: 1

Type: WARNING

Impact: Configuration

JPS-09031: Failed to read java policies for Application: {0}. Reason: {1}.

Cause: Failed to read java policies for Application: {0}. Reason: {1}.

Action: Check log for details.
Level: 1

Type: WARNING

Impact: Configuration

JPS-09032: Only one of permission array {0} and permission entry list {1} can be null or non-null.

Cause: Only one of permission array {0} and permission entry list {1} can be null/non-null.

Action: Ensure one of permission array or permission entry list values is null or non-null.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09033: No grantee found for grantee entry {0}.

Cause: No grantee found for grantee entry {0}.

Action: Ensure the grantee exist in the policy store.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09034: Modification on single-value attribute {0} but contains multiple attribute values.

Cause: Modification on single-value attribute {0} but contains multiple attribute values.

Action: Check modification details.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09035: Failed to create DN for {0}. Reason: {1}.

Cause: Failed to create DN for {0}. Reason: {1}.

Action: Check DN name.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09036: Failed to read JACC policy {0}. Reason: {0}.

Cause: Failed to read JACC policy {0}. Reason: {0}.

Action: Check LDAP configuration to resolve this error.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09037: No application DN found for name {0} under farm {1}.

Cause: No application DN found for name {0} under farm {1}.

Action: Check DN name.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09038: Resource type {0} does not exist for resource {1}

Cause: This resource type does not exist.

Action: Provide a valid resource type.
Level: 1

Type: WARNING

Impact: Security

JPS-09041: Expression component provided for RuleExpressionEntry must not be null.

Cause: Expression component provided for RuleExpressionEntry must not be null.

Action: Check value of ExpressionComponent.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-09042: Invalid expression component provided to RuleExpressionEntry.

Cause: Invalid expression component provided to RuleExpressionEntry.

Action: Check value of ExpressionComponent.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-09043: Function entry for an expression must not be null.

Cause: Function entry for an expression must not be null.

Action: Check value of FunctionEntry.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-09044: Expression component of type {0} not supported.

Cause: Expression component of type {0} not supported.

Action: Check value of ExpressionComponent.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-09045: Minimum number of input parameters must be less than or equal to maximum number of input parameters

Cause: Minimum number of input parameters must be less than or equal to maximum number of input parameters

Action: Check parameters to constructor of VarArgsInfo.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-09046: The Matcher {0} in the search query is invalid

Cause: The matcher in the search query is invalid

Action: Provide a valid Search Matcher in the query.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-09047: The Property {0} in the search query is invalid

Cause: The search property in the query is invalid

Action: Provide a valid Search property in the query.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-09048: The search value is invalid

Cause: The search value in the query is invalid

Action: Provide a valid Search value in the query.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-09049: Null value provided for {0}

Cause: Invalid value provided to DataType object.

Action: Provide a non-null value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09050: Host name {0} is invalid for DNS name

Cause: Invalid value provided as DNS host.

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09051: Invalid data. Lower DNS port {0} is greater than higher port {1}.

Cause: Lower port is greater than upper range.

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09052: Unknown format, can not parse valid date from string {0}.

Cause: Unknown format for date string.

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09053: Invalid string {0} for fractional seconds.

Cause: Invalid string for fractional seconds.

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09054: Invalid string {0} for hour offset.

Cause: Invalid string for hour offset.

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09055: Invalid string {0} for minute offset.

Cause: Invalid string for minute offset.

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09056: Negative value {0} not allowed.

Cause: Negative value not aloowed.

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09057: Invalid string {0} for dayTimeDuration. Cannot parse.

Cause: Invalid string format for dayTimeDuration

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09058: Invalid string {0} for RFC822 name.

Cause: RFC822Name cannot end with @.

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09059: Invalid string {0} for RFC822 domain.

Cause: Invvalid RFC822 domain name.

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09060: Invalid string {0} for yearMonthDuration.

Cause: Invalid string format for yearMonthDuration

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09061: Invalid string {0} for OpssTime, must be a number.

Cause: Invalid string for time field, must be a number.

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09062: Invalid value {0}, must be between lower range {1} and upper range {2}.

Cause: Value provided for data type not in required range.

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09063: Invalid inputed Hex Binary value {0}.

Cause: Invalid value provided for OpssHexBinary data type.

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09400: Attribute key cannot be null.

Cause: Attribute key was null.

Action: Provide a valid attribute key.
Level: 1

Type: WARNING

Impact: Requests/Responses

JPS-09401: Name of attribute key cannot be null.

Cause: Name of attribute key was null.

Action: Provide a valid name of attribute key.
Level: 1

Type: WARNING

Impact: Requests/Responses

JPS-09402: Attribute service instance not found in the default context.

Cause: Attribute service instance not found in the default JpsContext.

Action: Configure an attribute service instance in the default JpsContext.
Level: 1

Type: WARNING

Impact: Configuration

JPS-10000: There was an internal error in the policy store.

Cause: The opearion is not allowed for multivalued attribute.

Action: The opearion is not allowed for multivalued attribute.Supply a valid opearion
Level: 1

Type: WARNING

Impact: Security

JPS-10001: Exception happened while decoding value: {0}.

Cause: The encoding format is not correct.

Action: Check encoding format of String value.
Level: 1

Type: WARNING

Impact: Security

JPS-10050: The application {0} cannot be found at runtime due to {1}.

Cause: Corresponding runtime application does not exist.

Action: Check if policy is properly distributed.
Level: 1

Type: ERROR

Impact: Security

JPS-10051: Policy object {0} already exists in application policy {1}.

Cause: Policy object with same name exists in this application policy.

Action: Try a different name.
Level: 1

Type: ERROR

Impact: Security

JPS-10052: The list of runtime events is NULL.

Cause: The list of runtime events is NULL

Action: Please contact the security administrator.
Level: 1

Type: ERROR

Impact: Security

JPS-10053: The runtime events is NULL.

Cause: The runtime event is NULL

Action: Please contact the security administrator.
Level: 1

Type: ERROR

Impact: Security

JPS-10100: The policy domain, {0}, does not exist.

Cause: The policy domain does not exist

Action: Check the policy domain name.
Level: 1

Type: WARNING

Impact: Security

JPS-10102: The policy domain, {0}, already exists.

Cause: The policy domain exists

Action: Create a policy domain with a different name.
Level: 1

Type: WARNING

Impact: Security

JPS-10151: Application role {0} does not exist

Cause: The application role does not exist.

Action: Provide correct application role.
Level: 1

Type: WARNING

Impact: Security

JPS-10152: Application Role {0} is used.

Cause: Application Role is used.

Action: Remove the objects which use this application role.
Level: 1

Type: WARNING

Impact: Security

JPS-10153: Application role {0} does not belong to current application.

Cause: Application role does not belong to current application policy.

Action: Modify the application role with application role manager from correct application policy.
Level: 1

Type: WARNING

Impact: Security

JPS-10154: Class {0} is not supported.

Cause: The principal class specified is not supported.

Action: Provide correct principal class.
Level: 1

Type: WARNING

Impact: Security

JPS-10155: The application role attribute {0} is not supported for app role search.

Cause: The application role attribute specified is not supported.

Action: Provide supported attribute.
Level: 1

Type: WARNING

Impact: Security

JPS-10156: Error occurred while fetching the application role {0}.

Cause: The internal error occured while fetching the application role.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-10157: More than one results found for given Application role:{0}, Application name {1}, query:{2} and Actual result: {3}.

Cause: More than one results found for application name.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-10158: Invalid parameter.

Cause: Invalid parameter value.

Action: Please check the values are of required type.
Level: 1

Type: WARNING

Impact: Security

JPS-10159: Application Role {0} has an invalid unique name

Cause: Application role has an invalid unique name

Action: See the log files for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-10160: The Application role {0} does not belong to application. The application role dn {1} and unique name {2} are not matching.

Cause: The Application role does not belong to application contex.

Action: See the log files for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-10161: Internal error- More than one grantee entries found.

Cause: Internal error- More than one grantee entries found.

Action: See the log files for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-10162: Grantee DN was missing

Cause: Grantee DN was missing

Action: See the log files for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-10163: Internal error while revoking the permissions. Number of permissions to revoke (or delete) {0} : though only {1} permission(s) would be revoked (or deleted) if this operation were to proceed

Cause: Internal error while revoking the permissions.

Action: See the log files for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-10164: Only one of permission list and permission entry list can be null/non-null.

Cause: Only one of permission list and permission entry list can be null/non-null

Action: See the log files for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-10165: MATCHER.ANY not allowed for this kind of search operation

Cause: MATCHER.ANY not allowed for this kind of search operation

Action: Search is not allowed for the MATCHER.ANY
Level: 1

Type: WARNING

Impact: Security

JPS-10166: Error occurred during performing the operation {0}.

Cause: Error occured during performing the operation.

Action: See the log files for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-10167: Obligation does not exist for the policy domain {0}.

Cause: Obligation does not exist for the policy domain {0}.

Action: See the log files for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-10200: Administration role {0} already exists

Cause: Cannot have two administration roles with the same name.

Action: Provide a new name to the administration role.
Level: 1

Type: WARNING

Impact: Security

JPS-10201: Administration role {0} does not exist

Cause: Administration role is not found.

Action: Check the administration role name.
Level: 1

Type: WARNING

Impact: Security

JPS-10202: Administration role {0} is used

Cause: Administration role is used.

Action: Remove administration role members first.
Level: 1

Type: WARNING

Impact: Security

JPS-10203: Administration role {0} does not belong to current context

Cause: Administration role does not belong to current context.

Action: Use it in correct context.
Level: 1

Type: WARNING

Impact: Security

JPS-10204: Cannot create admin role with default name {0}

Cause: Cannot create admin role with reserved name.

Action: Use another name for admin role.
Level: 1

Type: WARNING

Impact: Security

JPS-10205: Cannot delete default admin role {0}

Cause: Cannot delete default admin role.

Action: Check the admin role name for deletion.
Level: 1

Type: WARNING

Impact: Security

JPS-10206: Cannot grant {0}, {1} to admin role because its super admin role has no such privilege

Cause: Cannot grant privileges to admin role whose super role has not.

Action: Check the admin resource action to grant.
Level: 1

Type: WARNING

Impact: Security

JPS-10207: Admin resource {0} is not for this scope {1}

Cause: This admin resource is not for this scope

Action: Check the admin resource to grant.
Level: 1

Type: WARNING

Impact: Security

JPS-10208: Cannot change rights of default admin role {0}

Cause: Cannot change righs of default admin role for a scope

Action: Check the admin role name.
Level: 1

Type: WARNING

Impact: Security

JPS-10209: The value for the SEARCH_PROPERTY.PRINCIPAL does implement the java.security.Principal interface. It is of type '{0}'.

Cause: The search by value is not an instance of java.security.Principal

Action: Supply an object of type java.security.Principal
Level: 1

Type: WARNING

Impact: Security

JPS-10210: The value for the SEARCH_PROPERTY.PRINCIPAL_NAME is not of type java.lang.String. It is of type '{0}'.

Cause: The search by value is not an instance of java.lang.String

Action: Supply an object of type java.lang.String
Level: 1

Type: WARNING

Impact: Security

JPS-10211: Administration role cannot have more than one grantee for parameter Application:{0}, policy Domain:{1}, Query Parameter:{2}, Actual results:{3}.

Cause: The admin role cannot have more than one grantee entry.

Action: Check only one grantee entry available to admin role.
Level: 1

Type: WARNING

Impact: Security

JPS-10250: Resource type reference should not be null.

Cause: The parameter resource type reference is null.

Action: Use a valid object.
Level: 1

Type: WARNING

Impact: Security

JPS-10251: The resource type reference is invalid.

Cause: The current resource type reference is invalid.

Action: Use a valid resource type reference.
Level: 1

Type: WARNING

Impact: Security

JPS-10252: The resource type {0} already exists.

Cause: The resource type has existed.

Action: Make sure the resource type does not exist.
Level: 1

Type: WARNING

Impact: Security

JPS-10253: The super resource type {0} does not exist.

Cause: The resource type is referring an invalid super resource type.

Action: Make sure the super resource type exist.
Level: 1

Type: WARNING

Impact: Security

JPS-10254: The resource type {0} should not have its own matcher since it has super type.

Cause: The resource type has both its own matching algorithm and super type.

Action: Remove matching algorithm if the resource type should have super type. Otherwise, remove super type.
Level: 1

Type: WARNING

Impact: Security

JPS-10255: Resource type search context should not be null.

Cause: The resource type context could not be gotten.

Action: Make sure the application policy is available.
Level: 1

Type: WARNING

Impact: Security

JPS-10256: Could not get an available data manager.

Cause: The data manager is invalid.

Action: Make sure policy store and related configuration are correct.
Level: 1

Type: WARNING

Impact: Security

JPS-10257: The modification operator {0} is invalid.

Cause: The operator in ModificationItem is invalid.

Action: Make sure the operation is one of DirContext.ADD_ATTRIBUTE, DirContext.REPLACE_ATTRIBUTE and DirContext.REMOVE_ATTRIBUTE.
Level: 1

Type: WARNING

Impact: Security

JPS-10258: The property name {0} is unknown.

Cause: The attribute ID in ModificationItem is undefined.

Action: Make sure the attribute ID is a valid one.
Level: 1

Type: WARNING

Impact: Security

JPS-10259: The name of resource type could not be modified.

Cause: Resource type name could not be modified.

Action: Do not put resource type name in ModificationItem.
Level: 1

Type: WARNING

Impact: Security

JPS-10260: The super type of resource type could not be modified.

Cause: The super type of resource type could not be modified.

Action: Do not put super type in ModificationItem.
Level: 1

Type: WARNING

Impact: Security

JPS-10261: The matching algorithm of resource type could not be modified.

Cause: The matching algorithm of resource type could not be modified.

Action: Do not put matching algorithm in ModificationItem
Level: 1

Type: WARNING

Impact: Security

JPS-10262: The action delimiter of resource type could not be modified.

Cause: The action delimiter of resource type could not be modified.

Action: Do not put action delimiter in ModificationItem.
Level: 1

Type: WARNING

Impact: Security

JPS-10263: The operation REPLACE_ATTRIBUTE could not be used to the allowed actions of resource type.

Cause: The operation REPLACE_ATTRIBUTE could not be used to the allowed actions of resource type.

Action: Use REMOVE_ATTRIBUTE and ADD_ATTRIBUTE in ModificationItem.
Level: 1

Type: WARNING

Impact: Security

JPS-10264: The property {0} of resource type is single, could not have more than one value.

Cause: The property could not have more than one value.

Action: First remove the existing value before adding new one.
Level: 1

Type: WARNING

Impact: Security

JPS-10265: Could not add or replace the property {0} since there is no value provided.

Cause: There is no value provided when trying to add or replace an property.

Action: Provide the new value.
Level: 1

Type: WARNING

Impact: Security

JPS-10266: The value data type of property {0} should be String.

Cause: The value data type of property is not String.

Action: Use a String object as value.
Level: 1

Type: WARNING

Impact: Security

JPS-10267: The resource type {0} does not exist.

Cause: The resource type does not exist.

Action: Make sure the resource type exist.
Level: 1

Type: WARNING

Impact: Security

JPS-10268: The resource type {0} is in use, could not be deleted.

Cause: The resource type could not be deleted without cascade since it is in use.

Action: Cascade delete it or first remove all referring objects.
Level: 1

Type: WARNING

Impact: Security

JPS-10269: The operation REPLACE_ATTRIBUTE could not be used to the resource type attribute

Cause: The operation REPLACE_ATTRIBUTE could not be used to the resource type attribute

Action: Use REMOVE_ATTRIBUTE and ADD_ATTRIBUTE in ModificationItem.
Level: 1

Type: WARNING

Impact: Security

JPS-10270: The resource type attribute {0} is used in policy(-ies) and can not be deleted.

Cause: The resource type attribute being deleted was used in one or morepolicies and could not be deleted.

Action: Before deleting the resource attribute, make sure it is not used.
Level: 1

Type: WARNING

Impact: Security

JPS-10271: The resource matcher class of resource type {0} could not be modified to {1}.

Cause: The resource type matcher class was changed while modifying.

Action: Keep matcher class unchanged.
Level: 1

Type: WARNING

Impact: Security

JPS-10272: Permission Class not found in the classpath: {0}

Cause: The permission class was not found in the class path.

Action: Make sure that the permission class is part of the class path for the program.
Level: 1

Type: WARNING

Impact: Security

JPS-10273: Permission class expected to be either oracle.security.jps.ResourcePermission or extending oracle.security.jps.AbstractTypedPermission but found {0} Resource Type: {1} is sharing permission class with Resource Type: {2}

Cause: The Permission class is not either ResourcePermission or Abstracted Permission

Action: The Permission class for the resource type must be a Resource permission
Level: 1

Type: WARNING

Impact: Security

JPS-10274: Permission should be associated with a Resource Type. Permission Name: {0}

Cause: The permission should have a resource type associated with it

Action: Make sure that the permission has a resource type associated with it
Level: 1

Type: WARNING

Impact: Security

JPS-10275: Resource Type Matcher Class and Permissions do not match. {0} and {1} do not match

Cause: Resource Type Matcher Class and Permissions do not match.

Action: Make sure that the Matcher Class and Permissions match.
Level: 1

Type: WARNING

Impact: Security

JPS-10276: Cannot determine the Resource Type from the permission {0}

Cause: Cannot determine the Resource Type from the permission.

Action: Make sure that there is a resource type associated with the permission class
Level: 1

Type: WARNING

Impact: Security

JPS-10277: Allowed attributes can not be modified.

Cause: Allowed attributes can not be modified.

Action: Make sure not modifying allowed attributes
Level: 1

Type: WARNING

Impact: Security

JPS-10278: Requested modification to the resource type {0} is not allowed.

Cause: Requested modification to the resource type is not allowed.

Action: Make sure not to make certain type of changes to the resource type when it is used by resources
Level: 1

Type: WARNING

Impact: Security

JPS-10279: The custom resource matcher class of resource type {0} could not be modified to {1}.

Cause: The custom resource matcher class was changed while modifying the resource type.

Action: Keep custom resource matcher class unchanged.
Level: 1

Type: WARNING

Impact: Security

JPS-10400: Resource reference should not be null.

Cause: The parameter resource reference is null.

Action: Use a valid object.
Level: 1

Type: WARNING

Impact: Security

JPS-10401: The resource reference is invalid.

Cause: The current resource reference is invalid.

Action: Use a valid resource reference.
Level: 1

Type: WARNING

Impact: Security

JPS-10402: The resource {0} does not exist.

Cause: The resource does not exist.

Action: Make sure the resource exist.
Level: 1

Type: WARNING

Impact: Security

JPS-10403: Could not get an available data manager.

Cause: The data manager is invalid.

Action: Make sure policy store and related configuration are correct.
Level: 1

Type: WARNING

Impact: Security

JPS-10404: The resource type {0} does not exist.

Cause: The resource type does not exist.

Action: Make sure the resource type exist.
Level: 1

Type: WARNING

Impact: Security

JPS-10405: The resource {0} with type {1} already exists in current application policy.

Cause: The resource to be created has existed.

Action: Make sure the resource does not exist.
Level: 1

Type: WARNING

Impact: Security

JPS-10406: The modification operator {0} is invalid.

Cause: The operator in ModificationItem is invalid.

Action: Make sure the operation is one of DirContext.ADD_ATTRIBUTE, DirContext.REPLACE_ATTRIBUTE and DirContext.REMOVE_ATTRIBUTE.
Level: 1

Type: WARNING

Impact: Security

JPS-10407: The property name {0} is unknown.

Cause: The attribute ID in ModificationItem is undefined.

Action: Make sure the attribute ID is a valid one.
Level: 1

Type: WARNING

Impact: Security

JPS-10408: The name and type of resource could not be modified.

Cause: The name and type of resource could not be modified.

Action: Do not put resource name and type in ModificationItem.
Level: 1

Type: WARNING

Impact: Security

JPS-10409: The property {0} of resource is single, could not have more than one value.

Cause: The property could not have more than one value.

Action: First remove the existing value before adding new one.
Level: 1

Type: WARNING

Impact: Security

JPS-10410: Could not add or replace the property {0} since there is no value provided.

Cause: There is no value provided when trying to add or replace an property.

Action: Provide the new value.
Level: 1

Type: WARNING

Impact: Security

JPS-10411: The resource {0} is in use, could not be deleted.

Cause: The resource could not be deleted without cascade since it is in use.

Action: Cascade delete it or first remove all referring objects.
Level: 1

Type: WARNING

Impact: Security

JPS-10412: The resource attribute {0} already exists in the current entry.

Cause: The resource attribute could not be added since it already exists.

Action: Remove duplicate resource attributes.
Level: 1

Type: WARNING

Impact: Security

JPS-10413: The resource action {0} already exists in the current entry.

Cause: The resource action could not be added since it already exists.

Action: Remove duplicate resource actions
Level: 1

Type: WARNING

Impact: Security

JPS-10414: The resource attribute {0} could not be deleted since it does not exist.

Cause: The resource attribute could not be deleted since it does not exist.

Action: Check if the resource attribute exists.
Level: 1

Type: WARNING

Impact: Security

JPS-10415: The resource action {0} could not be deleted since it does not exist.

Cause: The resource action could not be deleted since it does not exist.

Action: Check if the resource action exists
Level: 1

Type: WARNING

Impact: Security

JPS-10416: Resource {0} does not belong to the context.

Cause: The resource does not belong to current context

Action: Pass in correct resource.
Level: 1

Type: WARNING

Impact: Security

JPS-10417: Resource query across different resource type is not allowed.

Cause: Resource query across different resource type is not allowed

Action: Pass in correct query parameter.
Level: 1

Type: WARNING

Impact: Security

JPS-10418: Cannot delete a resource that has one more child resources.

Cause: Can not detele a resource that has one or more child resources

Action: Delete all child resources and then try again.
Level: 1

Type: WARNING

Impact: Security

JPS-10419: Resource hierarchy type change is not allowed.

Cause: Resource hierarchy type change is not allowed.

Action: Check the resource hierarchy type
Level: 1

Type: WARNING

Impact: Security

JPS-10420: Resource name must begin with the resource name delimiter.

Cause: Resource name must begin with the resource name delimiter

Action: Add resource name delimiter in the begining of the resource name.
Level: 1

Type: WARNING

Impact: Security

JPS-10421: The given all action value already exists.

Cause: The given all action value already exists

Action: Check the input all action value and check for duplicate values.
Level: 1

Type: WARNING

Impact: Security

JPS-10422: The resource attribute {0} is used in policy(-ies) and can not be deleted.

Cause: The resource attribute is used in policy(-ies) and can not be deleted.

Action: Before deleting the resource attribute, make sure it is not used.
Level: 1

Type: WARNING

Impact: Security

JPS-10423: The action {0} is used by the permissionSet/permission and can not be deleted.

Cause: The action is used by the permissionSet/permission and can not be deleted.

Action: Check if the action is used in any PermissionSet/Permission before deleting.
Level: 1

Type: WARNING

Impact: Security

JPS-10424: The resourceType {0} of hierarchy type is invalid as its parent is null.

Cause: The heirarical resourcetype's parent is null.

Action: Make sure to provide a valid name for the heirarical resourcetype
Level: 1

Type: ERROR

Impact: Security

JPS-10425: The resource attribute {0} already contains the value {1}.

Cause: The resource attribute already contains this value.

Action: Remove duplicate resource attributes values.
Level: 1

Type: WARNING

Impact: Security

JPS-10426: Cannot set all actions keyword for resource type with non-null matcher class.

Cause: All actions keyword cannot be set to resource type with matcher class

Action: Do not set all actions keyword for a resource type with a matcher class.
Level: 1

Type: WARNING

Impact: Security

JPS-10427: The resource name expression "{0}" is not a valid Java regular expression.

Cause: Regular expression provided for resource name expression is invalid.

Action: Check that the resource name expression is a valid Java regular expression.
Level: 1

Type: WARNING

Impact: Security

JPS-10428: The resource {0} of type {1} does not exist.

Cause: The resource of the resource type does not exist.

Action: Make sure the resource of the resource type exists.
Level: 1

Type: WARNING

Impact: Security

JPS-10429: The value data type of property {0} should be String and not {1}.

Cause: The value data type of property is not String.

Action: Use a String object as value.
Level: 1

Type: WARNING

Impact: Security

JPS-10451: Permission set {0} does not belong to the context.

Cause: The permission set does not belong to current context

Action: Pass in correct permission set.
Level: 1

Type: WARNING

Impact: Security

JPS-10452: Permission set {0} has ResourceActionsEntry with null ResourceEntry and null ResourceNameExpression.

Cause: Both ResourceEntry and Resource name expression of ResourceActionsEntry is null

Action: Pass in correct ResourceActionsEntry.
Level: 1

Type: WARNING

Impact: Security

JPS-10454: No resources or actions have been identified by the permission set.

Cause: No resources or actions have been identified by the permissionset.

Action: Ensure that the permission set is created with valid resource actions.
Level: 1

Type: WARNING

Impact: Security

JPS-10455: Resource is not protected by a Java Permission.

Cause: Resource is not protected by a Java Permission.

Action: Ensure that the permission set is created with valid resource object.
Level: 1

Type: WARNING

Impact: Security

JPS-10456: ResourceExpression and ResourceAction cannot be specified at the same time.

Cause: ResourceExpression and ResourceAction cannot be specified at the same time.

Action: PermissionSet ResourceAction should contain either Resource expression or ResoruceEntry.
Level: 1

Type: WARNING

Impact: Security

JPS-10457: Not able to perform operation due to invalid parameter. Cause: "{0}".

Cause: Not able to perform operation due to invalid parameter. Cause: {0}.

Action: Ensure that the operation is called with valid parameters.
Level: 1

Type: WARNING

Impact: Security

JPS-10458: ResourceExpression and ResourceAction cannot be null at the same time.

Cause: ResourceExpression and ResourceAction cannot be null at the same time.

Action: PermissionSet ResourceAction should contain either Resource expression or ResoruceEntry.
Level: 1

Type: WARNING

Impact: Security

JPS-10459: The modified permission set {0} contains resources of multiple resource types. It is not permitted as there is policy(-ies) that references that permission set and uses resource attributes.

Cause: The modified permission set contained resources of multiple resource types. It was not permitted if there was a policy that referenced that permission set and used resource attributes.

Action: Fix the permission set or modify the policy(-ies).
Level: 1

Type: WARNING

Impact: Security

JPS-10460: The permission set search query {0} is not supported

Cause: The permission set search query is not supported.

Action: Use supported query scenario.
Level: 1

Type: WARNING

Impact: Security

JPS-10463: Requested actions: " {0} " are not a subset of valid actions: " {1}" for the given resource: " {2} " and type: " {3} ".

Cause: Invalid resource actions for the given resource.

Action: Ensure that the actions in the resource-actions are a valid subset of the actions defined by the resource type.
Level: 1

Type: WARNING

Impact: Security

JPS-10464: Error occurred while getting the permission set entry for permission set search query {0}.

Cause: Error occured while getting the permission set entry for permission set search query.

Action: See the log files for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-10465: Permission set {0} has ResourceActionsEntry with null expression in ResourceNameExpression.

Cause: Expression in ResourceNameExpression of ResourceActionsEntry is null

Action: Pass in correct ResourceActionsEntry with non-null Resource name expression.
Level: 1

Type: WARNING

Impact: Security

JPS-10466: Resource {0} has no Resource Actions, but Resource Type {1} has resource actions.

Cause: Empty resource actions for the given Resource, but Resource type has actions.

Action: Ensure that the actions in the resource-actions are not null or empty since the resource type has actions.
Level: 1

Type: WARNING

Impact: Security

JPS-10467: Permission set {0} has ResourceActionsEntry with null expression in ResourceNameExpression.

Cause: Expression in ResourceNameExpression of ResourceActionsEntry is null

Action: Pass in correct ResourceActionsEntry with non-null Resource name expression.
Level: 1

Type: WARNING

Impact: Security

JPS-10468: Duplicate permission " {0} " in policy store.

Cause: Duplicate permission in policy store.

Action: Check the policy store and ensure that there is no duplicate permission.
Level: 1

Type: WARNING

Impact: Security

JPS-10470: The resource type name "{0}", does not match the resourceType in the encoded target name: "{1}". Permission class is "{2}"

Cause: Invalid resource type in permission target.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10471: Resource type is missing in the target name: "{0}", for permission: "{1}"

Cause: Resource type missing in permission target.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10472: Target "{0}" is missing the prefix '=resourceName='. Unable to determine the resource name for permission: "{1}"

Cause: Target name missing in permission target.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10473: The target name "{0}" is invalid. Should start with "{1}"

Cause: Target name encoding is not correct.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10474: The parameter: "{0}", value: "{1}" cannot be null

Cause: Permission target is null.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10475: The permission actions: "{0}" are not a subset of valid actions defined in resource type: "{1}"

Cause: Permission actions do not match with valid resource type actions.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10500: The target policy, {0}, does not exist.

Cause: The policy object does not exist.

Action: Check if the target policy exists.
Level: 1

Type: WARNING

Impact: Security

JPS-10501: Policy query contains unrecognizable information.

Cause: Policy query contains unrecognizable information.

Action: Check the policy query object.
Level: 1

Type: WARNING

Impact: Security

JPS-10502: Policy rule information is missing.

Cause: Policy rule information is missing.

Action: Check if policy rule information exists in policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10503: Obligation information is missing.

Cause: Obligation information is missing.

Action: Check if obligation information exists in policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10504: Permission set information is missing.

Cause: Permission set information is missing.

Action: Check if permission set information exists in policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10505: Grantee information is missing.

Cause: Grantee information is missing.

Action: Check if grantee information exists in policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10506: The policy rule, {0}, does not exist.

Cause: The policy rule does not exist.

Action: Check the policy rule name passed in.
Level: 1

Type: WARNING

Impact: Security

JPS-10507: The condition string is in wrong format, {0}.

Cause: Condition string is in wrong format.

Action: Check condition string in policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10508: Policy condition contains an unknown function, {0}.

Cause: Policy condition contains an unknown function.

Action: Check condition string in policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10509: Policy condition parsing error.

Cause: Policy condition parsing error.

Action: Check condition string in policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10510: The expression, {0}, is unknown.

Cause: The policy expression is unknown.

Action: Check condition string in policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10511: The data type, {0}, is unknown.

Cause: The data type is unknown

Action: Check condition string in policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10512: A ResourceActionsEntry should contain either resource entry or resource name expression.

Cause: The ResourceActionsEntry object does not contain resource infomation.

Action: Check ResourceActionsEntry passed in.
Level: 1

Type: WARNING

Impact: Security

JPS-10513: The search value type {0} is not supported for {1}.

Cause: Query criteria type does not support.

Action: Pass in a correct query value.
Level: 1

Type: WARNING

Impact: Security

JPS-10514: Cannot add PermissionSet to PolicyEntry if it has ResourceType.

Cause: Resource type is already defined in PolicyEntry.

Action: clear resource type of PolicyEntry before adding PermissionSetEntry.
Level: 1

Type: WARNING

Impact: Security

JPS-10515: Cannot set ResourceType to PolicyEntry if it has PermissionSet.

Cause: Permission Set is already defined in PolicyEntry.

Action: clear Permission Set of PolicyEntry before setting Resource Type.
Level: 1

Type: WARNING

Impact: Security

JPS-10516: Cannot add Rule if there is rule already in PolicyEntry

Cause: Add rule to policy when the policy already has rule.

Action: Delete existing rule before adding new rule to policy.
Level: 1

Type: WARNING

Impact: Security

JPS-10517: Delete rule not existing in PolicyEntry

Cause: rule does not belong to the PolicyEntry.

Action: Check the rule before deleting rule from PolicyEntry.
Level: 1

Type: WARNING

Impact: Security

JPS-10518: Delete permission set not existing in PolicyEntry

Cause: permission set does not belong to the PolicyEntry.

Action: Check the permission set before deleting permission set from PolicyEntry.
Level: 1

Type: WARNING

Impact: Security

JPS-10519: Delete obligation not existing in PolicyEntry

Cause: obligation does not belong to the PolicyEntry.

Action: Check the obligation before deleting obligation from PolicyEntry.
Level: 1

Type: WARNING

Impact: Security

JPS-10520: Delete Principal not existing in PolicyEntry

Cause: principal does not belong to the PolicyEntry.

Action: Check the principal before deleting principal from PolicyEntry.
Level: 1

Type: WARNING

Impact: Security

JPS-10521: The obligation {0} already exists.

Cause: The obligation already exists in the policy entry.

Action: Check ObligationEntry passed in.
Level: 1

Type: WARNING

Impact: Security

JPS-10522: The parameters passed in is invalid, we expect {0}, but {1} is passed in.

Cause: The parameter passed in the function is not valid.

Action: Pass in correct parameters.
Level: 1

Type: WARNING

Impact: Security

JPS-10523: The function return type is invalid, we expect OpssBoolean, but {0} is passed in.

Cause: The return type of the function is not valid.

Action: Pass in a function with OpssBoolean return type.
Level: 1

Type: WARNING

Impact: Security

JPS-10524: The query with search property {0}, comparator type {1} and matcher {2} is not supported.

Cause: Such query is not supported.

Action: Pass in a supported query value.
Level: 1

Type: WARNING

Impact: Security

JPS-10525: The attribute assignment {0} could not be added since it already exists.

Cause: The attribute assignment could not be added since it already exists.

Action: Remove duplicate attribute assignments.
Level: 1

Type: WARNING

Impact: Security

JPS-10526: The permission set {0} could not be added since it already exists.

Cause: The permission set could not be added since it already exists.

Action: Remove duplicate permission sets.
Level: 1

Type: WARNING

Impact: Security

JPS-10527: The principal {0} could not be added since it already exists.

Cause: The principal could not be added since it already exists.

Action: Remove duplicate principals.
Level: 1

Type: WARNING

Impact: Security

JPS-10528: The Policy {0} referenced multiple resource types and resource attribute is used in policy condition or obligation.

Cause: Policies that used resource attributes in their conditions or obligations could not refrence one or more permission sets that contain resources of multiple types.

Action: Split the policy to reference only one resource type in each policy.
Level: 1

Type: WARNING

Impact: Security

JPS-10529: The resource attribute {0} used in policy condition or obligation is invalid resource attribute of type {1}.

Cause: The resource attribute used in policy condition was invalid for the referenced resource type

Action: Fix the policy condition to use only valid attributes for the given resource type.
Level: 1

Type: WARNING

Impact: Security

JPS-10530: Cannot create a policy {0} with AdminRole(s) {1}.

Cause: Cannot create a policy with AdminRoleEntry(s).

Action: Remove the AdminRole principals from the principal list.
Level: 1

Type: WARNING

Impact: Security

JPS-10531: Cannot grant permission to AdminRole(s) {0}.

Cause: Cannot grant permission to AdminRoleEntry(s).

Action: Remove the AdminRole principals from the principal list.
Level: 1

Type: WARNING

Impact: Security

JPS-10532: Cannot grant AdminRole {0} to another AdminRole {1}.

Cause: Cannot grant AdminRole to another AdminRole.

Action: Change to grant AdminRole to either enterprise role or user.
Level: 1

Type: WARNING

Impact: Security

JPS-10533: Cannot revoke AdminRole {0} from another AdminRole {1}.

Cause: Cannot revoke AdminRole from another AdminRole.

Action: Change to revoke AdminRole from either enterprise role or user.
Level: 1

Type: WARNING

Impact: Security

JPS-10534: Cannot grant AdminRole {0} to an AppRole {1}.

Cause: Cannot grant AdminRole to an AppRole.

Action: Change to grant AdminRole to either enterprise role or user.
Level: 1

Type: WARNING

Impact: Security

JPS-10535: Cannot revoke AdminRole {0} from an AppRole {1}.

Cause: Cannot revoke AdminRole from an AppRole.

Action: Change to revoke AdminRole from either enterprise role or user.
Level: 1

Type: WARNING

Impact: Security

JPS-10536: AdminRole {0} cannot be managed outside of the AdminManager.

Cause: AdminRole cannot be managed outside of AdminManager.

Action: Use AdminManager for all AdminRole related administrative tasks.
Level: 1

Type: WARNING

Impact: Security

JPS-10537: Cannot modify grant permission to AdminRole(s) {0}.

Cause: Cannot modify grant permission to AdminRoleEntry(s).

Action: Remove the AdminRole principals from the principal list.
Level: 1

Type: WARNING

Impact: Security

JPS-10538: Cannot revoke permission from AdminRole(s) {0}.

Cause: Cannot revoke permission from AdminRoleEntry(s).

Action: Remove the AdminRole principals from the principal list.
Level: 1

Type: WARNING

Impact: Security

JPS-10539: Basic policy cannot have {0} information.

Cause: Basic policy cannot have {0} information.

Action: Remove the information from basic policy.
Level: 1

Type: WARNING

Impact: Security

JPS-10540: Basic policy cannot have ResourceActionsEntry without ResourceEntry.

Cause: Basic policy cannot have ResourceActionsEntry without ResourceEntry.

Action: Use ResourceActionsEntry with ResourceEntry for basic policy.
Level: 1

Type: WARNING

Impact: Security

JPS-10541: Basic policy cannot use Resource {0} without Resource Matcher Class.

Cause: Basic policy cannot use Resource {0} without Resource Matcher Class.

Action: Use Resource with Resource Matcher Class for basic policy.
Level: 1

Type: WARNING

Impact: Security

JPS-10542: Default TransformerFactory cannot be located.

Cause: The TransformerFactory cannot be loaded

Action: Check the environment
Level: 1

Type: WARNING

Impact: Security

JPS-10543: Failed to retrieve Transformer.

Cause: The TransformerFactory cannot generate a Transformer.

Action: Check the environment
Level: 1

Type: WARNING

Impact: Security

JPS-10544: The policy, {0}, exists.

Cause: The role policy object exists.

Action: Create a role policy with a different name.
Level: 1

Type: WARNING

Impact: Security

JPS-10545: The application role {0} could not be added since it already exists.

Cause: The application role could not be added since it already exists.

Action: Remove duplicate application role.
Level: 1

Type: WARNING

Impact: Security

JPS-10546: The resource {0}, {1} could not be added since it already exists.

Cause: The resource could not be added since it already exists.

Action: Remove duplicate resource.
Level: 1

Type: WARNING

Impact: Security

JPS-10547: The resource name expression {0}, {1} could not be added since it already exists.

Cause: The resource name expression could not be added since it already exists.

Action: Remove duplicate resource name expression.
Level: 1

Type: WARNING

Impact: Security

JPS-10548: The policy rule {0} already exists.

Cause: The policy rule already exists.

Action: Create policy rule with different name.
Level: 1

Type: WARNING

Impact: Security

JPS-10550: Attribute {0} already exists

Cause: Cannot have two attributes with the same name.

Action: Provide a new name to the attribute.
Level: 1

Type: WARNING

Impact: Security

JPS-10551: Attribute {0} does not exist

Cause: Attribute not found.

Action: Check the attribute name.
Level: 1

Type: WARNING

Impact: Security

JPS-10552: Attribute {0} is used.

Cause: Attribute is already used.

Action: Remove the objects which use this attribute.
Level: 1

Type: WARNING

Impact: Security

JPS-10553: Attribute {0} does not belong to current application.

Cause: Attribute does not belong to current application policy.

Action: Modify the attribute with extension manager from correct application policy.
Level: 1

Type: WARNING

Impact: Security

JPS-10554: The name of Attribute in policy repository is missing

Cause: Attribute in policy store has no name.

Action: Check the underline policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10555: The type of Attribute in policy repository is missing

Cause: Attribute in policy store has no type.

Action: Check the underline policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10556: The category of Attribute in policy repository is missing

Cause: Attribute in policy store has no category.

Action: Check the underline policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10557: Cannot overwrite a built-in attribute, {0}.

Cause: Try to overwrite a built-in attribute.

Action: Do not overwrite a built-in function.
Level: 1

Type: WARNING

Impact: Security

JPS-10558: Cannot modify a built-in attribute, {0}.

Cause: Try to modify a built-in attribute.

Action: Do not modify a built-in attribute.
Level: 1

Type: WARNING

Impact: Security

JPS-10559: Cannot delete a built-in attribute, {0}.

Cause: Try to delete a built-in attribute.

Action: Do not delete a built-in attribute.
Level: 1

Type: WARNING

Impact: Security

JPS-10581: Cannot overwrite a built-in function, {0}.

Cause: Try to overwrite a built-in function.

Action: Do not overwrite a built-in function.
Level: 1

Type: WARNING

Impact: Security

JPS-10582: The function does not exist, {0}.

Cause: The function does not exist.

Action: Check the function name passed in.
Level: 1

Type: WARNING

Impact: Security

JPS-10583: The function is in use, {0}.

Cause: The function is in use.

Action: Cannot delete a function in use.
Level: 1

Type: WARNING

Impact: Security

JPS-10584: The function is used in some policies, your changes on return type may lead to unpredictable issues.

Cause: The function is in use.

Action: Cannot change return type of a function in use.
Level: 1

Type: WARNING

Impact: Security

JPS-10585: The function is used in some policies, your changes on parameter types may lead to unpredictable issues.

Cause: The function is in use.

Action: Cannot change parameter types of a function in use.
Level: 1

Type: WARNING

Impact: Security

JPS-10586: Cannot modify a built-in function, {0}.

Cause: Try to modify a built-in function.

Action: Do not modify a built-in function.
Level: 1

Type: WARNING

Impact: Security

JPS-10587: Cannot delete a built-in function, {0}.

Cause: Try to delete a built-in function.

Action: Do not delete a built-in function.
Level: 1

Type: WARNING

Impact: Security

JPS-10588: The function already exists, {0}.

Cause: The function exists.

Action: Create a function with a different name.
Level: 1

Type: WARNING

Impact: Security

JPS-10589: Cascade delete is not supported.

Cause: Cascade delete not supported.

Action: Set the cascade delete parameter to false.
Level: 1

Type: WARNING

Impact: Security

JPS-10590: Cannot find the function entry for function name {0}.

Cause: Cannot find the function entry for function name.

Action: Check function entry in policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10591: Cannot find the expression type for expression {0}.

Cause: Cannot find the expression type for the expression.

Action: Check expression in policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10592: Operation {1} is not allowed for multi valued attribute {0}

Cause: The category of Attribute is Invalid.

Action: The category of Attribute is Invalid. Supply a valid Attribute category
Level: 1

Type: WARNING

Impact: Security

JPS-10600: Failed to initialize PD instance.

Cause: Failed to initialize PD instance.

Action: Refer to the base exception in logs to resolve the issue.
Level: 1

Type: WARNING

Impact: Security

JPS-10601: Failed to initialize PolicyDistributionManager instance.

Cause: Failed to initialize PolicyDistributionManager instance.

Action: Refer to the base exception in logs to resolve the issue.
Level: 1

Type: WARNING

Impact: Security

JPS-10602: PD has not been initialized.

Cause: PD has not been initialized.

Action: Check if OPSS policy store provider has been initialized successfully.
Level: 1

Type: WARNING

Impact: Security

JPS-10603: FAILURE: Retry {0} failed after {1} times retries.

Cause: PD operation failed to retry.

Action: Check connectivity to backend repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10604: The operation is not allowed for non-controlled mode application {0}.

Cause: Can not distribute policy for non-controlled policy distribution mode application

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10605: Failed to distribute policy for catch exception.

Cause: Distribute policy failed for catch exception

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10606: Failed to distribute policy to PDP {0} for catch exception {1}.

Cause: Failed to distribute policy to pdp for catch exception

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10607: Invalid cache key {0} in {1} cache.

Cause: Invalid cache key

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10608: Failed to copy files from active directory {0} to update directory {1}.

Cause: Failed to copy cache file from active directory to update directory

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10609: Failed to write state.chk file.

Cause: Failed to write state.chk file

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10610: Failed to update local cache since distributed payload for application {0} is empty.

Cause: Failed to update local cache since distributed payload is empty

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10611: Invalid distribution state {0} in step {1}.

Cause: Invalid distribution state

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10612: Local cache file verification failed, so redistribute all binding applications

Cause: Failed to verify local cache file, so need to redistribution all binding applications

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10613: Failed to parse PD port number, do not start PD registration web service.

Cause: Failed to parse PD port number, do not start PD registration web service.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10614: Failed to start PD registration web service for catch exception.

Cause: Failed to start PD registration web service for catch exception.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10615: Catch exception.

Cause: Catch interrupt exception in start registration service thread.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10616: Failed to find local host name, do not start PD registration web service.

Cause: Failed to find local host name, do not start PD registration web service.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10617: Failed to start PD push policy web service for catch exception.

Cause: Failed to start PD registration web service for catch exception.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10618: Invalid SSL configuration.

Cause: Invalid SSL configuration, please check log for details

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10619: Failed to initialize cipher {0} for local cache encryption/decryption.

Cause: Failed to initialize cipher for local cache encryption/decryption.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10620: Exception reported in registration thread.

Cause: Catch interrupt exception in start registration service thread.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10621: PD Lock not found

Cause: PD Lock node not found.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10622: Invalid PD Lock update time {0}.

Cause: Invalid PD Lock update time stamp.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10623: PD is running in another Admin, please distribute policy after the process finished.

Cause: PD is running in another Admin, please distribute policy after the process finished.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10624: Failed to connect primary server, try secondary server.

Cause: Failed to connect primary server, try secondary server.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10625: Failed to read from the local cache. The cache will be removed. Reason: {0}

Cause: Failed to read from the local cache. The cache will be removed.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10626: Encryption/Decryption of the local cache file using the algorithm {0} is not supported.

Cause: The specified algorithm for local cache encryption/decryption is not supported.

Action: Please check PDP service configuration in jps-config.xml file.
Level: 1

Type: ERROR

Impact: Security

JPS-10627: The key length used to initialize cipher {0} is not valid. Expected key length is {1} bits, but raw key length is {2} bits.

Cause: The key length used to initialize cipher is not valid.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10700: The value of attribute {0} should be unique

Cause: The unique attribute has duplicated values.

Action: Keep attribute value unique.
Level: 1

Type: WARNING

Impact: Security

JPS-10701: Data Source lookup failure. It is safe to ignore the warning during Websphere server starts up. If you still get the warning after WebSphere server starts up, check your configuration.

Cause: Websphere data source lookup failure.

Action: Safe to ignore during WebSphere starts up.
Level: 1

Type: ERROR

Impact: Security

JPS-10702: The datasource {0} is not found.

Cause: Given datasource jndi name is not found.

Action: Check datasource jndi name.
Level: 1

Type: ERROR

Impact: Security

JPS-10750: Application Policy unique name: "{0}" is invalid

Cause: The application policy unique name is invalid

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10751: The version number of Application policy : "{0}" is invalid

Cause: The application policy version number is invalid

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10752: The policy entry unique name: "{0}" is invalid

Cause: The policy entry unique name is invalid

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10800: The role policy object does not exist for {0}.

Cause: The role policy object does not exist.

Action: Check if the target role policy exists.
Level: 1

Type: WARNING

Impact: Security

JPS-10801: The role policy object already exists for {0}.

Cause: The policy object exists.

Action: Create a policy with a different name.
Level: 1

Type: WARNING

Impact: Security

JPS-10802: Application role hierarchy cannot participate in a role mapping policy.

Cause: One or more principals in the role mapping policy are of type: ApplicationRole or AnonymousRole or AuthenticatedRole or and AdminRole.

Action: Identify the principal type in the incomming principals, and ensure only a user or group principal type is supplied.
Level: 1

Type: WARNING

Impact: Security

JPS-10803: At least one of the Resource(s)/Resource Name Expression(s) used in Role Policy are permission based. This is not allowed.

Cause: At least one of the Resource(s)/Resource Name Expression(s) used in Role Policy are permission based. This is not allowed.

Action: Ensure that resource(s)/resource name expression(s) are not permission based.
Level: 1

Type: WARNING

Impact: Security

JPS-10850: The SM Config Tool is used to configure the Security Modules for Oracle Entitlements Server Here are the various options that it will accept -smType <java, wls, ws, rmi, was, jboss> -smConfigId <config id of sm is always required> -serverLocation <in case of was, wls, jboss, this is the location of the server> -pdServer OES Admin Server hostName -pdPort SSL Port for OES Admin Server -pdClientPort SSL Port for WLS SM client -serverNodeName - server node name of websphere -serverName - server instance name of websphere -serverUserName - user name of application server -serverPassword - password of application server -prpFileName - path for the prp file used.

Cause: When help is asked for

Action: Help message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10851: Please enter a value for {0}:

Cause: Prompt Message

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10852: Configuring for PDP proxy mode

Cause: Prompt Message

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10853: Configuring for Controlled Policy Distribution Mode

Cause: Prompt Message

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10854: Configuring for Direct Connection to the Database Policy Store

Cause: Prompt Message

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10855: Configuring for Direct Connection to the Ldap Policy Store

Cause: Prompt Message

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10856: Configuring for Direct Connection to the Derby Policy Store

Cause: Prompt Message

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10857: Value is missing or corrupt {0}. Please supply an appropriate value.

Cause: Error Message

Action: Please supply the required parameters as specified in the message.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10858: Security Module configuration is created at: {0}

Cause: Prompt Message

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10859: Please re-enter a value for {0}:

Cause: Prompt Message

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10890: sys_obj_q

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10891: Full qualified resource name on which the query is performed: /foo/bar

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10900: TBD

Cause: Enrollment response is truncated.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10901: TBD

Cause: Keystore {0} does not exist.

Action: Check the file system.
Level: 1

Type: ERROR

Impact: Security

JPS-10902: TBD

Cause: Enrollment server error.

Action: Check enrollment server status.
Level: 1

Type: ERROR

Impact: Security

JPS-10903: TBD

Cause: Enrollment is proceeded successfully.

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10904: TBD

Cause: Enrollment is not proceeded successfully.

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10905: TBD

Cause: The program works in console mode only.

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10906: Enter password for {0}:

Cause: Enter password for {0}:

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10907: Enter password for {0} again:

Cause: Enter password for {0} again:

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10908: The passwords you inputted do not match.

Cause: The passwords you inputted do not match.

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10909: Passwords are saved in credential store.

Cause: Passwords are saved in credential store.

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10910: TBD

Cause: Passwords are not saved in credential store.

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10911: TBD

Cause: {0} is not set.

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10912: TBD

Cause: Keystores are initialized successfully.

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10913: TBD

Cause: Keystores are not initialized successfully.

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10914: TBD

Cause: Enter username for {0}:

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10915: Enter credential map name:

Cause: Enter credential map name:

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10916: Enter credential key name:

Cause: Enter credential key name:

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10917: Input password can not be null.

Cause: The passwords you inputted can not be null.

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10920: function: urn:oasis:names:tc:xacml:1.0:function:integer-equal The function returns true if the LHS (left-hand side) matches RHS (right-hand side); If LHS or RHS is a multiple value attribute and the other side is single value attribute, the function returns false; If both LHS and RHS are multiple value attribute, they have the same number of elements and for each element from the list on the left, there exists an element from the list on the right, the function returns true.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10921: function: urn:oasis:names:tc:xacml:1.0:function:date-equal The function returns true if the LHS (left-hand side) matches RHS (right-hand side); If LHS or RHS is a multiple value attribute and the other side is single value attribute, the function returns false; If both LHS and RHS are multiple value attribute, they have the same number of elements and for each element from the list on the left, there exists an element from the list on the right, the function returns true.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10922: function: urn:oasis:names:tc:xacml:1.0:function:time-equal The function returns true if the LHS (left-hand side) matches RHS (right-hand side); If LHS or RHS is a multiple value attribute and the other side is single value attribute, the function returns false; If both LHS and RHS are multiple value attribute, they have the same number of elements and for each element from the list on the left, there exists an element from the list on the right, the function returns true.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10923: function: urn:oasis:names:tc:xacml:1.0:function:string-is-in The function returns true if the LHS (left-hand side) matches one of the values in RHS (right-hand side); LHS should be single-valued. RHS can be single or multi-valued.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10924: function: urn:oasis:names:tc:xacml:1.0:function:integer-is-in The function returns true if the LHS (left-hand side) matches one of the values in RHS (right-hand side); LHS should be single-valued. RHS can be single or multi-valued.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10925: function: urn:oasis:names:tc:xacml:1.0:function:date-is-in The function returns true if the LHS (left-hand side) matches one of the values in RHS (right-hand side); LHS should be single-valued. RHS can be single or multi-valued.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10926: function: urn:oasis:names:tc:xacml:1.0:function:time-is-in The function returns true if the LHS (left-hand side) matches one of the values in RHS (right-hand side); LHS should be single-valued. RHS can be single or multi-valued.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10927: function: urn:oasis:names:tc:xacml:1.0:function:integer-greater-than The function returns true if the value of LHS is greater than RHS. Both LHS and RHS should be single value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10928: function: urn:oasis:names:tc:xacml:1.0:function:integer-greater-than-or-equal The function returns true if the value of LHS is greater than or equals to RHS. Both LHS and RHS should be single value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10929: function: urn:oasis:names:tc:xacml:1.0:function:integer-less-than The function returns true if the value of LHS is less than RHS. Both LHS and RHS should be single value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10930: function: urn:oasis:names:tc:xacml:1.0:function:integer-less-than-or-equal The function returns true if the value of LHS is less than or equals to RHS. Both LHS and RHS should be single value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10931: function: urn:oasis:names:tc:xacml:1.0:function:time-greater-than The function returns true if the value of LHS is greater than RHS. Both LHS and RHS should be single value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10932: function: urn:oasis:names:tc:xacml:1.0:function:time-greater-than-or-equal The function returns true if the value of LHS is greater than or equals to RHS. Both LHS and RHS should be single value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10933: function: urn:oasis:names:tc:xacml:1.0:function:time-less-than The function returns true if the value of LHS is less than RHS. Both LHS and RHS should be single value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10934: function: urn:oasis:names:tc:xacml:1.0:function:time-less-than-or-equal The function returns true if the value of LHS is less than or equals to RHS. Both LHS and RHS should be single value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10935: function: urn:oasis:names:tc:xacml:1.0:function:date-greater-than The function returns true if the value of LHS is greater than RHS. Both LHS and RHS should be single value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10936: function: urn:oasis:names:tc:xacml:1.0:function:date-greater-than-or-equal The function returns true if the value of LHS is greater than or equals to RHS. Both LHS and RHS should be single value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10937: function: urn:oasis:names:tc:xacml:1.0:function:date-less-than The function returns true if the value of LHS is less than RHS. Both LHS and RHS should be single value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10938: function: urn:oasis:names:tc:xacml:1.0:function:date-less-than-or-equal The function returns true if the value of LHS is less than or equals to RHS. Both LHS and RHS should be single value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10939: function: urn:oasis:names:tc:xacml:1.0:function:string-regexp-match The LHS should be a single-value string type attribute/value. The RHS should be a single value string which complies with Java Regular Expression.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10940: function: urn:oasis:names:tc:xacml:1.0:function:or The function stands for an OR operation between two single-value boolean expressions/values.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10941: function: urn:oasis:names:tc:xacml:1.0:function:and The function stands for an AND operation between two single-value boolean expressions/values.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10942: function: urn:oasis:names:tc:xacml:1.0:function:not The function stands for a NOT operation on a single-value boolean expression/value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10943: function: valid_for_mseconds The function accepts a single integer value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10944: function: valid_for_seconds The function accepts a single integer value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10945: function: valid_for_minutes The function accepts a single integer value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10946: function: valid_for_hours The function accepts a single integer value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10947: function: valid_until_time The function accepts a single time value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10948: function: valid_until_date The function accepts a single date value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10949: function: sys_defined The function accepts a single string value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10950: current_gmt_time

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10951: current_gmt_date

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10952: sys_subjectgroups

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10953: sys_user

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10954: sys_app

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10955: sys_obj_type

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10956: sys_obj

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10957: sys_privilege

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10958: boolean_equal

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10959: string_equal

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10960: integer_equal

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10961: date_equal

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10962: time_equal

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10963: string_is_in

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10964: integer_is_in

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10965: date_is_in

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10966: time_is_in

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10967: integer_greater_than

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10968: integer_greater_than_or_equal

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10969: integer_less_than

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10970: integer_less_than_or_equal

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10971: time_greater_than

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10972: time_greater_than_or_equal

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10973: time_less_than

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10974: time_less_than_or_equal

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10975: date_greater_than

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10976: date_greater_than_or_equal

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10977: date_less_than

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10978: date_less_than_or_equal

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10979: string_regexp_match

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10980: or

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10981: and

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10982: not

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10983: valid_for_mseconds

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10984: valid_for_seconds

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10985: valid_for_minutes

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10986: valid_for_hours

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10987: valid_until_time

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10988: valid_until_date

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10989: attribute_has_value

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10990: The attribute will be assigned current time value during evaluation

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10991: The attribute will be assigned current date value during evaluation

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10992: List of unqualified group names to which user belongs: ["admin", "managers"]

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10993: Current user: unqualified form: system

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10994: Unqualified name of the binding resource for the resource on which the query is performed: admin

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10995: ResourceType on which the query is performed: LibraryResourceType

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10996: Resource on which the query is performed: bar

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10997: Unqualified name of the action on which the resource is being queried.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10998: function: urn:oasis:names:tc:xacml:1.0:function:boolean-equal The function returns true if the LHS (left-hand side) matches RHS (right-hand side);If LHS or RHS is a multiple value attribute and the other side is single value attribute,the function returns false;If both LHS and RHS are multiple value attribute, they have the same number of elements and for each element from the list on the left, there exists an element from the list on the right, the function returns true.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10999: function: urn:oasis:names:tc:xacml:1.0:function:string-equal The function returns true if the LHS (left-hand side) matches RHS (right-hand side); If LHS or RHS is a multiple value attribute and the other side is single value attribute, the function returns false; If both LHS and RHS are multiple value attribute, they have the same number of elements and for each element from the list on the left, there exists an element from the list on the right, the function returns true.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-20000: GlobalPolicy can not be created by MAPI methods

Cause: GlobalPolicy can not be created by MAPI methods.

Action: Set up policy store using reassociation or upgrading
Level: 1

Type: WARNING

Impact: Programmatic

JPS-20001: GlobalPolicy can not be deleted by MAPI methods.

Cause: GlobalPolicy can not be deleted by MAPI methods.

Action: GlobalPolicy is a built-in stripe, can not be deleted
Level: 1

Type: WARNING

Impact: Programmatic

JPS-20002: GlobalPolicy can not be returned from the method.

Cause: GlobalPolicy can not be returned from the method.

Action: Gets GlobalPolicy from the method getGlobalPolicy
Level: 1

Type: WARNING

Impact: Programmatic

JPS-20050: Combining algorithm {0} not found.

Cause: Combining algorithm not found.

Action: Make sure the used combining algorithm exists.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-20051: Exception in converting execution frequency {0}, message is {1}

Cause: Exception in converting value of algorithm execution frequency.

Action: Make sure the execution frequency is valid.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-20052: Exception in converting algorithm usage {0}, message is {1}

Cause: Exception in converting value of algorithm usage.

Action: Make sure the usage is valid.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-20053: A combining algorithm must be provided if policy is using more than one rule.

Cause: Policy uses multiple rules, but no combining algorithm provided.

Action: Provide a combining algorithm.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-20060: Number of input parameters to the function and provided value types for them are not of same size.

Cause: Number of input parameters to the function and provided value types for them are not of same size.

Action: Parameter value types, if provided, must be provided for all input parameters
Level: 1

Type: ERROR

Impact: Programmatic

JPS-20061: Value collection added to expression is null.

Cause: Value collection added to expression is null.

Action: Provide a non-nulll collection of values to expression.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-20062: Value collection passed to input parameter when a single object is expected.

Cause: Value collection passed to input parameter when a single object is expected.

Action: Provide a single object as input parameter.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-20063: Wrong type of collection passed as input parameter; expected type is {0}, provided {1}.

Cause: Wrong type of collection passed as input parameter; expected type is {0}, provided {1}.

Action: Provide correct type of collection as function input parameter.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-20064: Function {0} is unknown.

Cause: Function {0} is unknown.

Action: Provide correct function.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-20070: In mixed mode, PDP configuration id could not be null

Cause: PDP configuration id is missing.

Action: Specify the PDP configuration id
Level: 1

Type: WARNING

Impact: Programmatic

JPS-90600: Security Module with the configuration id {0} already exists.

Cause: Security Module with the configuration id {0} already exists.

Action: Provide a unique configuration id.
Level: 1

Type: WARNING

Impact: Security

JPS-90601: Failed to create Security Module with the configuration id {0}, with error {1}

Cause: Failed to create Security Module with the configuration id {0}, with error {1}

Action: Check error message for further details.
Level: 1

Type: WARNING

Impact: Security

JPS-90602: Security Module with the configuration id {0} not found.

Cause: Security Module with the configuration id {0} not found.

Action: Make sure the configuration id is valid.
Level: 1

Type: WARNING

Impact: Security

JPS-90603: AuditService is improperly configured.

Cause: Audit Service is not initializable.

Action: Configure an audit server for audit trails
Level: 1

Type: WARNING

Impact: Security

JPS-90604: Security Module with the configuration id {0} successfully created.

Cause: Security Module with the configuration id {0} successfully created.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90605: Security Module with the configuration id {0} successfully modified.

Cause: Security Module with the configuration id {0} successfully modified.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90606: Security Module with the configuration id {0} successfully deleted.

Cause: Security Module with the configuration id {0} successfully deleted.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90607: Security Module with the configuration id {0} successfully retrieved.

Cause: Security Module with the configuration id {0} successfully retrieved.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90608: Failed to modify Security Module with the configuration id {0}, with error {1}

Cause: Failed to modify PIP with the configuration id {0}, with error {1}

Action: Check error message for further details.
Level: 1

Type: WARNING

Impact: Security

JPS-90620: PIP with the configuration id {0} already exists.

Cause: PIP with the configuration id/name {0} already exists.

Action: Provide a unique configuration id/name.
Level: 1

Type: WARNING

Impact: Security

JPS-90621: Failed to create PIP with the configuration id {0}, with error {1}

Cause: Failed to create PIP with the configuration id {0}, with error {1}

Action: Check error message for further details.
Level: 1

Type: WARNING

Impact: Security

JPS-90622: PIP with the configuration id {0} not found.

Cause: PIP with the configuration id/name {0} not found.

Action: Make sure the configuration id/name is valid.
Level: 1

Type: WARNING

Impact: Security

JPS-90623: PIP with the configuration id {0} successfully created.

Cause: PIP with the configuration id {0} successfully created.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90624: PIP with the configuration id {0} successfully modified.

Cause: PIP with the configuration id {0} successfully modified.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90625: PIP with the configuration id {0} successfully deleted.

Cause: PIP with the configuration id {0} successfully deleted.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90626: PIP with the configuration id {0} successfully retrieved.

Cause: PIP with the configuration id {0} successfully retrieved.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90627: Failed to modify PIP with the configuration id {0}, with error {1}

Cause: Failed to modify PIP with the configuration id {0}, with error {1}

Action: Check error message for further details.
Level: 1

Type: WARNING

Impact: Security

JPS-90630: Application Policy with the configuration id {0} not found.

Cause: Application with the id {0} not found.

Action: Make sure the Appplication Policy is valid.
Level: 1

Type: WARNING

Impact: Security

JPS-90631: SM Binding with the configuration id {0} and application name {1} successfully retrieved.

Cause: SM Binding with the configuration id {0} and application name {1} successfully retrieved.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90632: SM with the configuration id {0} to application bindings retrieved.

Cause: SM with the configuration id {0} to application bindings retrieved.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90633: SM with the configuration id {0} and application name {1} successfully unbound.

Cause: SM with the configuration id {0} and application name {1} successfully unbound.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90634: PIP Binding with the configuration id {0} and application name {1} successfully retrieved.

Cause: PIP Binding with the configuration id {0} and application name {1} successfully retrieved.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90635: PIP with the configuration id {0} to application bindings retrieved.

Cause: PIP with the configuration id {0} to application bindings retrieved.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90636: PIP with the configuration id {0} and application name {1} successfully unbound.

Cause: PIP with the configuration id {0} and application name {1} successfully unbound.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90637: Failed to create SM binding with the configuration id {0}, with error {1}

Cause: Failed to create SM binding with the configuration id {0}, with error {1}

Action: Check error message for further details.
Level: 1

Type: WARNING

Impact: Security

JPS-90638: Failed to create PIP binding with the configuration id {0}, with error {1}

Cause: Failed to create PIP binding with the configuration id {0}, with error {1}

Action: Check error message for further details.
Level: 1

Type: WARNING

Impact: Security

JPS-90639: Application {0} already bound to configuration {1}

Cause: Application {0} already bound to configuration {1}

Action: No need to bind again
Level: 1

Type: WARNING

Impact: Security

JPS-90640: Failed to unbind SM configuration

Cause: Failed to unbind SM with the configuration id {0}, with error {1}

Action: Check error message for further details.
Level: 1

Type: WARNING

Impact: Security

JPS-90641: Failed to unbind PIP Configuration

Cause: Failed to unbind PIP with the configuration id {0}, with error {1}

Action: Check error message for further details.
Level: 1

Type: WARNING

Impact: Security

JPS-90642: The non-controlled policy distribution mode application {0} can not be bound to SM configuration

Cause: The non-controlled policy distribution mode application can not be bound to SM configuration

Action: Bind controlled policy distribution mode application
Level: 1

Type: ERROR

Impact: Security

55 JRF-10001 to JRF-20030

JRF-10001: Fail to retrieve the application identifier. The internal exception is: {0}.

Cause: The MBean server could not be accessed to retrieve the application name.

Action: Verify that the MBean server is running and accessible.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10002: Fail to retrieve the WebLogic domain adminser server name. The internal exception is: {0}.

Cause: The MBean server could not be accessed to retrieve the admin server name.

Action: Verify that the MBean server is running and accessible.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10003: Fail to retrieve the current server name. The internal exception is: {0}.

Cause: The MBean server could not be accessed to retrieve the server name based on the current thread.

Action: Verify that the MBean server is running and accessible.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10004: Fail to check if the current server is admin server. The internal exception is: {0}.

Cause: The MBean server could not be accessed to verify that the server in the current thread is the admin server.

Action: Verify that the MBean server is running and accessible.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10005: Fail to retrieve the server log path. The internal exception is: {0}.

Cause: The MBean server could not be accessed to retrieve the server log path.

Action: Verify that the MBean server is running and accessible.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10006: Fail to copy the config file from {0} to the server directory {1}. The internal exception is: {2}.

Cause: The server config directory could not be accessed.

Action: Use the applyJRF() wlst command to ensure that the server has been properly configured.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10007: Fail to retrieve the system property domain.home.

Cause: The system property domain.home was not specified during WebLogic server startup.

Action: Specify the system property domain.home when starting the WebLogic server.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10008: I/O exception occurs when aceessing to the JRF template at {0}.

Cause: The specified JRF template was not accessaible.

Action: Verify that the template jar from the template location is present and accessible.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10009: I/O exception occurs when parsing config/config.xml from the JRF template at {0}.

Cause: The config.xml might be missing from the JRF template or the JRF template jar might be corrupted.

Action: Verify that the JRF template is properly installed within the Oracle Home.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10010: The file config.xml under domain {0} does not exist.

Cause: The config.xml under domain config was missing or corrupted.

Action: Verify that the domain contains a valid config.xml file.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10011: Fail to parse the config.xml file from JRF template.

Cause: The domain config.xml might be missing or the JRF template jar might be corrupted.

Action: Verify that the JRF template is properly installed within the Oracle Home and that the domain contains a valid config.xml file.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10012: Fail to retrieve the property for the Common Components Home.

Cause: The Common Components Home property was not set.

Action: Set the Oracle Home property using the system property common.components.home or the environment variable COMMON_COMPONENTS_HOME.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10013: The specified Oracle Home directory {0} does not exist.

Cause: The Common Components Home directory did not exist.

Action: Verify that Common ComponentsHome, specified through the system property common.components.home or environment variable COMMON_COMPONENTS_HOME, is a valid directory.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10014: Fail to retrieve the current server name. The internal exception is: {0}.

Cause: The MBean server could not be accessed to retrieve the application server platform information.

Action: Verify that the MBean server is running and accessible.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10015: The specified application server platform {0} is not supported by JRF.

Cause: JRF does not support the specified platform.

Action: Contact Oracle Support Services for the JRF supported application server platforms.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10016: The initialization of the server config directory from the Oracle Home {0} with domain directory {1} for copying fails. The internal exception is: {2}.

Cause: Could not retrieve the servers from the domain config.xml file.

Action: Verify that the domain contains a valid config.xml file.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10017: Unable to invoke {0} because the domain {1} has not been extended with JRF template.

Cause: Domain has not been extended with JRF template.

Action: Apply JRF template to the domain.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10018: Server or cluster "{0}" is not found.

Cause: The server or cluster is not found.

Action: Create the server or cluster.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10019: Could not obtain edit lock on the domain

Cause: Domain is being edited by someone else

Action: Wait until the edit lock on the domain is released and retry.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10020: Could not load/instantiate a WebLogic server platform support instance.

Cause: Could not load/instantiate a WebLogic server platform support instance.

Action: Check if the server platform support class can be loaded/instantiated by the classloader.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10021: Could not load/instantiate a WebSphere server platform support instance.

Cause: Could not load/instantiate a WebSphere server platform support instance.

Action: Check if the server platform support class can be loaded/instantiated by the classloader.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10022: Could not load system property 'oracle.domain.config.dir'.

Cause: Could not load system property 'oracle.domain.config.dir'.

Action: Verify JRF is installed and provisioned properly and the system property 'oracle.domain.config.dir' is set.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10023: Could not load system property 'oracle.server.config.dir'.

Cause: Could not load system property 'oracle.server.config.dir'.

Action: Verify JRF is installed and provisioned properly and the system property 'oracle.server.config.dir' is set.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10024: JRF is unable to determine the current application server platform.

Cause: JRF is unable to determine the current platform.

Action: Contact Oracle Support Services for the JRF supported application server platforms.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10025: Could not load/instantiate a JBoss server platform support instance.

Cause: Could not load/instantiate a JBoss server platform support instance.

Action: Check if the server platform support class can be loaded/instantiated by the classloader.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10026: Failed to get application server edition

Cause: JRF Failed to retrieve application server edition

Action: Verify that the application server is installed and accessible.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10027: Operation is not supported on this application server edition

Cause: Operation is not supported on this platform edition.

Action: Verify it is the right application server edition.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10028: Invoke startup and shutdown class {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

JRF-10029: String {0} is in invalid format . Example of correct string format is {1}

Cause: String format is invalid.

Action: Correct the string format, see example of a correct string format in the exception message
Level: 1

Type: ERROR

Impact: Configuration

JRF-20001: Read domain {0} to applyJRF

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

JRF-20002: Update JRF changes to domain {0} in {1} mode

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

JRF-20003: Target JRF components to "{0}"

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

JRF-20004: Cannot copy {0} to {1}: "{2}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

JRF-20005: Environment variables {0} not set

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

JRF-20006: Copying JRF configuration files from {0} to {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

JRF-20007: Unable to add help for JRF commands: "{0}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

JRF-20008: No domain has been read

Cause: JRF detects that domain has not been read.

Action: Read the domain offline or connect online before invoke JRF WLST command.
Level: 1

Type: ERROR

Impact: Configuration

JRF-20009: JRF component or service with type "{0}" and name "{1}" is not found.

Cause: The WLST applyJRF command is out-of-sync with the template that is used to extend the domain, or domain has not been installed with JRF.

Action: Use the wlst.sh/cmd from the same Oracle Home that contains the JRF template, which was used to extend the domain; or extend the domain with JRF template if JRF is not installed
Level: 1

Type: ERROR

Impact: Configuration

JRF-20010: {0} is not found.

Cause: file not found

Action: Verify oraclehomeproperties.xml exist
Level: 1

Type: ERROR

Impact: Configuration

JRF-20011: Node GUID does not exist or node is empty in {0}.

Cause: node not found or no value

Action: Verify oraclehomeproperties.xml exist
Level: 1

Type: ERROR

Impact: Configuration

JRF-20012: System properties {0} not set

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

JRF-20013: Target does not exist or not valid : {0}.

Cause: target not found or not valid

Action: Verify target exists and valid
Level: 1

Type: ERROR

Impact: Configuration

JRF-20014: Failed to create library at : {0}.

Cause: Creating shared library failed

Action: Verify server connection
Level: 1

Type: ERROR

Impact: Configuration

JRF-20015: Failed to create custom service : {0}.

Cause: Creating custom service failed

Action: Verify server connection
Level: 1

Type: ERROR

Impact: Configuration

JRF-20016: JRF_FAILED_CREATE_URLPROVIDER : {0}.

Cause: Creating URL Provider failed

Action: Verify server connection
Level: 1

Type: ERROR

Impact: Configuration

JRF-20017: Failed to config jvm args for : {0}.

Cause: Config JVM memory arguments failed

Action: Verify server connection
Level: 1

Type: ERROR

Impact: Configuration

JRF-20018: Failed to add jvm system property for : {0}.

Cause: Adding system property failed

Action: Verify server connection
Level: 1

Type: ERROR

Impact: Configuration

JRF-20019: Failed to parse template: {0}.

Cause: Template has error

Action: Verify template
Level: 1

Type: ERROR

Impact: Configuration

JRF-20020: Failed to get variable {0} from {1}.

Cause: Get variable failed

Action: Verify variable.xml
Level: 1

Type: ERROR

Impact: Configuration

JRF-20021: Failed to update targets of application {0}.

Cause: Failed to update application target

Action: Verify application
Level: 1

Type: ERROR

Impact: Configuration

JRF-20022: Failed to update {0}.

Cause: Failed to update oracle jdbc driver path

Action: Verify server
Level: 1

Type: ERROR

Impact: Configuration

JRF-20023: Failed to install application {0}.

Cause: Failed to install application

Action: Verify application
Level: 1

Type: ERROR

Impact: Configuration

JRF-20024: Failed to create variable {0} for {1}.

Cause: Failed to create variable

Action: Verify server
Level: 1

Type: ERROR

Impact: Configuration

JRF-20025: Need to apply jrf template to cell.

Cause: Cell is not jrf enabled

Action: Apply jrf template to the cell since this cell is not jrf enabled
Level: 1

Type: ERROR

Impact: Configuration

JRF-20026: Could not load/instantiate {0} JRFService instance.

Cause: Could not load/instantiate a JRFService implementation class instance.

Action: Check if JRFService implementation class in the error message can be loaded/instantiated by the classloader.
Level: 1

Type: ERROR

Impact: Configuration

JRF-20028: JRFService not supported

Cause: JRFService is not supported.

Action: Check if the server has related JRFService available.
Level: 1

Type: ERROR

Impact: Configuration

JRF-20029: MapModulesToServers is disabled, cannot modify target of application {0}.

Cause: MapModulesToServers is disabled, cannot modify target of application.

Action: Enable MapModulesToServers task for this application
Level: 1

Type: ERROR

Impact: Configuration

JRF-20030: Enable StartupBeansService failed on server {0}.

Cause: Enable StartupBeansService failed

Action: Verify server connection
Level: 1

Type: ERROR

Impact: Configuration

56 MAPVIEWER-00001 to MAPVIEWER-06057

MAPVIEWER-00001: No 'xml_request' parameter found in the request.

Cause: The incoming HTTP request did not contain the mandatory parameter named 'xml_request'.

Action: Ensure the HTTP request for MapViewer contains the required parameter.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00002: Could not get a free MapMaker. Server is busy?

Cause: MapViewer could not obtain the necessary resource to process an incoming request.

Action: Try increasing the value of the "number_of_mappers" attribute in the definition of the involved data source.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00003: SQL error occurred while generating map.

Cause: MapViewer encountered an error while executing a SQL query.

Action: Check the MapViewer server logs for details about the SQL exception and take appropriate actions.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00004: Unable to add a predefined theme.

Cause: MapViewer could not add or load a predefined theme while processing the current map request.

Action: Ensure the predefined theme exists in the database or is accessible via the given data source.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00005: Error while compressing raw image data.

Cause: MapViewer could not successfully compress a generated map image into the requested file format.

Action: Check the MapViewer server logs for the actual stack trace and take appropriate actions.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00006: Location for saving map image files not specified.

Cause: MapViewer could not obtain the path information for saving generated map files.

Action: Check the MapViewer configuration file and make sure a path for saving image files is specified or the default path is a valid one.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00007: No map image generated.

Cause: MapViewer did not generate a map image.

Action: Check the MapViewer server logs for details/exceptions and take appropriate actions.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00008: Unable to add local theme(s).

Cause: MapViewer could not create a new local theme for the current map request.

Action: Check the MapViewer server logs for details/exceptions and take appropriate actions. Make sure the individual Geo-Features are in proper format.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00009: Unable to add JDBC theme(s).

Cause: MapViewer could not create a new JDBC (dynamic) theme for the current map request.

Action: Check the MapViewer server logs for details/exceptions and take appropriate actions. Make sure the data source information is correct, and characters in the user-supplied SQL query are properly escaped for XML.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00010: Error loading MapViewer configuration file.

Cause: MapViewer could not properly load its configuration file.

Action: Make sure the XML configuration file is in valid and well-formed format.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00011: Error creating a map data source.

Cause: MapViewer could not create a new data source.

Action: Make sure correct database connection information is supplied, including host name, database instance name/sid, listener port, and login user/password. Also make sure the host name or IP address is reachable by the host running the MapViewer server.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00012: Error obfuscating data source password in the config file.

Cause: MapViewer could not obfuscate the login password for a data source defined in its configuration file.

Action: Make sure the password is prefixed with an exclamation point (!).
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00013: Clear-text passwords in the config file must be prefixed with a '!' (exclamation mark).

Cause: Clear text password in the MapViewer configuration file was not prefixed with '!'.

Action: Make sure the database login password for any data source defined in the configuration file is prefixed with an exclamation point (!).
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00014: Error adding a MARKER style from an image URL.

Cause: MapViewer could not create a dynamic MARKER style that is based on a URL.

Action: Make sure the URL of the image is reachable from the host running the MapViewer server. If MapViewer is running behind a firewall, you may need to set up HTTP proxy information in MapViewer's configuration file, or via JVM run-time properties.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00015: Cannot fetch image from given URL

Cause: MapViewer could not fetch and load an image from a given URL.

Action: Make sure the URL of the image is reachable from the host running the MapViewer server. If MapViewer is running behind a firewall, you may need to set up HTTP proxy information in MapViewer's configuration file, or via JVM run-time properties.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00016: Error while attempting to clear a mapping metadata cache.

Cause: MapViewer could not clear the cached mapping metadata (style/theme/basemap definitions) for a given data source from memory.

Action: Make sure a correct data source name is specified. Also check MapViewer server logs for possible exceptions and stack traces.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00017: MapViewer is not ready. Please try again later.

Cause: MapViewer was still starting core services such as the mapping servlet. If this error still occurs 30 seconds after starting MapViewer, it may be stuck trying to connect to one or more database instances.

Action: Check and monitor MapViewer server logs to see which server has not been started yet. Check data source definitions in the configuration file and make sure all the database instances involved are up and running.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00018: Error parsing XML map request.

Cause: MapViewer encountered an error while parsing an XML map request.

Action: Make sure a well formed and valid XML map request is sent to the MapViewer server.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00019: Specified data source does not exist.

Cause: A specified data source did not exist or was not known by this MapViewer server.

Action: Make sure a correct data source name is supplied.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00020: Invalid general-purpose or admin XML request.

Cause: The incoming admin or non-map request was invalid or not supported.

Action: Make sure only valid and supported requests are sent to the MapViewer
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00021: No data source specified in the XML request.

Cause: The incoming request did not specify any data source name, and the MapViewer server has no default data source.

Action: Make sure a valid data source is specified as part of the request.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00101: XML map request: invalid 'geoFeature' element found.

Cause: The incoming map request contained an invalid 'geoFeature' element.

Action: Make sure all the 'geoFeature' elements have valid syntax.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00102: XML map request: invalid 'box' element found.

Cause: The incoming map request contained an invalid 'box' element.

Action: Make sure the 'box' element has valid syntax.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00103: XML map request: 'geoFeature' element must have a geometry defined.

Cause: The incoming map request contained one or more 'geoFeature' elements that do not contain any geometry data.

Action: Make sure all 'geoFeature' elements contain a geometry.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00104: XML map request: invalid geometry definition found.

Cause: A 'geoFeature' element with invalid geometry data was found in the XML map request.

Action: Make sure all 'geoFeature' elements contain a valid geometry.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00105: XML map request: 'geoFeature' does not support postal address.

Cause: A 'geoFeature' element with postal/street address was found in the XML map request.

Action: Currently 'geoFeature' elements could not use street address string to specify the location.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00106: XML map request: invalid JDBC theme definition.

Cause: The incoming map request contained an invalid JDBC theme.

Action: Make sure all JDBC themes have proper syntax.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00107: XML map request: 'center' element does not contain a 'geoFeature' sub-element.

Cause: The 'center' element of the incoming map request did not contain a 'geoFeature' sub-element.

Action: Ensure that the 'center' element has a 'geoFeature' sub-element that specifies a point geometry for the map center.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00108: XML map request: 'center' element must define either a 'size' or 'scale' attribute.

Cause: The 'center' element of the incoming map request did not contain any size or map-scale information.

Action: Ensure that the 'center' element has either a 'size' or 'scale' attribute that defines the map data window.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00109: XML map request: invalid map size or scale value.

Cause: The 'center' element of the incoming map request contained an invalid size or scale value.

Action: Make sure a proper value is specified for the 'size' or 'scale' attribute of the 'center' element in the XML map request.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00110: XML map request: invalid map height/width.

Cause: The incoming map request specified an invalid image width or height value.

Action: Make sure a proper value (positive integer) is specified for both the width and height attributes of the root 'map_request' element.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00111: XML map request: invalid theme (min/max) scale range.

Cause: Some theme(s) in the incoming map request contained an invalid min/max scale range specification.

Action: Make sure proper value scale ranges are set for all themes in the map request.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00112: XML map request: invalid WMS theme specified.

Cause: The incoming map request contained an invalid WMS theme.

Action: Make sure all WMS themes are properly defined in the XML map request.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00113: Permission denied for this operation.

Cause: The requested operation was not permitted by the MapViewer server.

Action: Make sure your operation is permitted by MapViewer. For example, the server may disallow JDBC themes in the map request, or disable direct INFO requests. You will need either to avoid performing these operations or to modify MapViewer configuration to allow these operations.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00114: Invalid type for dynamic binding parameter.

Cause: The incoming map request supplied invalid value(s) for a theme's binding variable.

Action: Make sure values for your theme's binding parameters are all of correct type.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00115: list_predefined_themes: No base map found for map tile layer.

Cause: The 'list_predefined_themes' request specified a map tile layer that is based on a nonexistent base map.

Action: Make sure the base map for the specified map tile layer exists in the database view.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00116: list_predefined_themes: Map tile layer not found.

Cause: The 'list_predefined_themes' request specified a map tile layer that is not found.

Action: Make sure the specified map tile layer exists in the database view.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01000: No themes to render.

Cause: The Map request had no base map or themes defined.

Action: Add a base map that contains a list of themes or define individual themes on your request.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01001: Cannot load base map.

Cause: A database error may have happened while reading the base map definition from the USER_SDO_MAPS view, or the requested base map was not defined.

Action: Make sure the base map exists in the database; also check the MapViewer log for database errors and additional details.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01002: Cannot load theme.

Cause: A database error may have happened while reading the theme definition from the USER_SDO_THEMES view, or the requested theme was not defined.

Action: Make sure the theme exists in the database; also check the MapViewer log for database errors and additional details.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01003: Cannot load style.

Cause: A database error may have happened while reading the style definition from the USER_SDO_STYLES view. Or the requested style was not defined.

Action: Make sure the style exists in the database; also check the MapViewer log for database errors and additional details.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01004: Bounding Themes returned null MBR. Themes were not rendered.

Cause: Bounding themes may have been used to define the query window for the map request, but it produced no spatial feature. The map request was aborted due to this condition.

Action: Change the bounding theme or themes definition, so the definition defines a select statement that returns one or more features. In Map Builder, this message can happen when previewing base maps with full extent (no center and size defined). Map Builder uses the first theme of the base map as the bounding theme when a full extent is applied. If this first theme returns no features for a full extent request, then you should remove it from the base map list of themes.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01005: No spatial data to render.

Cause: A full extent request (no center and size defined) returned no features.

Action: Change the theme or themes definition to select one or more features.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01006: Invalid style type for Point features.

Cause: The style type used could not be applied to render point features.

Action: Do not use AREA or LINE styles to render point features.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01007: Feature has no geometric representation.

Cause: The feature geometry was null.

Action: Check the feature geometry column in the database table.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01008: Cannot parse xml style string: missing closing "

Cause: The XML string was not correct and could not be parsed.

Action: Check for the missing closing character '"'.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01009: Invalid style class specified in xml style string.

Cause: Attribute class on the xml definition was undefined.

Action: Assign a valid value to attribute class (COLOR,LINE,TEXT,MARKER,AREA).
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01010: Style cannot be created from a xml string that does not define the style class.

Cause: Unknown style class type defined.

Action: Change the attribute class value to a known type (COLOR,LINE,TEXT,MARKER,AREA).
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01011: Cannot find a custom image renderer for format:

Cause: Image theme format was not supported and there was no custom image renderer defined for this format.

Action: Use a known image format (GIF,JPEG,PNG,TIFF) or implement a custom image renderer for this format.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01012: Cannot create image to render from byte array.

Cause: Image array of bytes may be null or corrupted.

Action: Check the image data source. If it comes from a database column, verify that the column content is not null. If the image content appears to be correct, then report the error to Oracle.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01013: Invalid base map definition.

Cause: The XML string for base map definition could not be parsed.

Action: Fix the XML string that defines the base map.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01014: Invalid styling rules definition.

Cause: The XML string for theme styling rules could not be parsed.

Action: Fix the XML string that defines the theme styling rules.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01015: Unable to retrieve theme definition.

Cause: The theme did not exist in USER_SDO_THEMES view.

Action: Add a theme definition to user themes view.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01016: Theme with undefined styling rules.

Cause: The styling rules section of theme XML definition was null.

Action: Ensure that a theme styling rules section is defined in the theme definition.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01017: Undefined image column attribute in image theme definition.

Cause: The image theme definition did not contain the image column attribute.

Action: Define attribute 'image_column' in the image theme definition.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01018: Undefined image format attribute in image theme definition.

Cause: The image theme definition did not contain the image format attribute.

Action: Define attribute 'image_format in the image theme definition.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01019: One or more attributes missing in image theme definition.

Cause: Some mandatory attributes were missing from the image theme definition.

Action: Attributes for defined image column ('image_column') and image format ('image_format') must be defined in the image theme definition.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01020: Undefined network name attribute in network theme definition.

Cause: The network theme definition did not contain the network name attribute.

Action: Define the attribute 'network_name' in the network theme definition.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01021: Undefined topology name attribute in topology theme definition.

Cause: The topology theme definition did not contain the topology name attribute.

Action: Define the attribute 'topology_name' in the topology theme definition.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01022: Undefined WFS service URL attribute in WFS theme definition.

Cause: The WFS theme definition did not contain the service URL attribute.

Action: Define the attribute 'service_url' in the WFS theme definition.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01023: Unable to find entry in ALL_SDO_GEOM_METADATA table for theme:

Cause: Theme base table and spatial column have not been registered in the user metadata view (USER_SDO_GEOM_METADATA).

Action: Register the theme base table and spatial column in the user metadata view, by inserting a row in the USER_SDO_GEOM_METATADA view.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01024: Unable to convert query window SRID to theme SRID.

Cause: Conversion of map request query window projection to theme projection has failed. The database procedure sdo_cs.transform was used to convert coordinates from one SRID to another SRID.

Action: Check the log for database errors.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01025: Cannot use ratio scale mode with theme that has unknown SRID.

Cause: A request with a ratio scale was attempted, but the data did not contain a valid Oracle SRID.

Action: Assign a valid SRID to the spatial data.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01026: Unable to get an instance of spatial provider.

Cause: A custom spatial provider was not be defined in MapViewer's configuration file, or the provider class path was not accessible.

Action: Check the spatial provider section in the MapViewer configuration file for the definition of the provider. If it is defined there, check the libary jar file path, and make sure it is part of the classpath definition for the application.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01027: Custom geometry theme must have a spatial data provider defined.

Cause: The custom geometry theme definition did not contain the spatial provider attribute.

Action: Define the attribute 'provider_id' in the custom theme definition.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01028: Custom spatial data provider is null.

Cause: The custom spatial data provider was not initialized and is null.

Action: Check if the provider name is defined in the theme definition, and also check if the provider class library is defined in the MapViewer configuration file and is part of the application classpath.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01029: Undefined geometry column for dynamic geometry theme.

Cause: A dynamic geometry theme definition did not contain the spatial column attribute.

Action: Define the attribute 'spatial_column' in the dynamic geometry theme definition.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01030: A set of four question marks separated by commas is required to define a geometry theme with a dynamic SDO_FILTER.

Cause: A set of questions marks was not used in the SDO_ORDINATE_ARRAY for a dynamic geometry theme with a SQL expression that also includes the spatial filter operator (SDO_FILTER). These question marks will be replaced with values based on the map request center and size.

Action: Use the following pattern for the ordinate array on the SOD_FILTER expression: SDO_ORDINATE_ARRAY(?,?,?,?).
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01031: Not enough binding parameters defined.

Cause: The theme definition contained binding parameters on its query expression, but the parameters were not provided inn the map request.

Action: Pass the theme binding parameters to your theme definition, using the methods provided by the JavaScript API (Oracle Maps), or by the Java API; or if issuing a direct XML request, define the binding parameters in the theme section.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01032: GeoRaster spatial extent is null.

Cause: The GeoRaster object contained a null geometry as its spatial extent.

Action: Update the GeoRaster spatial extent using the PLSQL procedure sdo_geor.generateSpatialExtent.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01033: Invalid image stretch low value.

Cause: The image stretch low value was not numeric and ranging from 0 to 256. The default value 0 is used if the number is out of this range.

Action: Define a numeric value within the specified range.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01034: Invalid image stretch high value.

Cause: The image stretch high value was not numeric and ranging from 0 to 256. The default value 100 is used if the number is out of this range.

Action: Define a numeric value within the specified range.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01035: Invalid brightness value.

Cause: The image brightness value was not numeric and ranging from 0 to 256. The default value 0 is used if the number is out of this range

Action: Define a numeric value within the specified range.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01036: Undefined brightness value for image processing.

Cause: The image brightness value was not defined, as required when a brightness operation is to be applied on a GeoRaster object.

Action: Define the parameter 'value' for brightness in the theme definition.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01037: Invalid contrast value.

Cause: The image contrast value was not numeric and ranging from 0 to 256. The default value 256 is used if the number is out of this range

Action: Define a numeric value within the specified range.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01038: Undefined contrast value for image processing.

Cause: The image contrast value was not defined, as required when a contrast operation is to be applied on a GeoRaster object.

Action: Define the parameter 'value' for contrast in the theme definition.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01039: Invalid threshold value.

Cause: The image threshold value was not numeric and ranging from 0 to 256. The default value 0 is used if the number is out of this range

Action: Define a numeric value within the specified range.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01040: Invalid low threshold value.

Cause: The image threshold low value was not numeric and ranging from 0 to 256. The default value 0 is used if the number is out of this range

Action: Define a numeric value within the specified range.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01041: Invalid high threshold value.

Cause: The image threshold high value was not numeric and ranging from 0 to 256. The default value 0 is used if the number is out of this range

Action: Define a numeric value within the specified range.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01042: Invalid image column type for image theme.

Cause: The image theme data was not stored in a column of type BLOB or ORDIMAGE.

Action: Assign a valid image column in the image theme definition.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01043: Network category is null.

Cause: The network model category information was null in the metadata view.

Action: Check the contents of column 'network_category' in the network metadata view USER_SDO_NETWORK_METADATA.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01044: Network geometry type is null.

Cause: The network model geometry type information was null in the metadata view.

Action: Check the contents of column 'geometry_type' in the network metadata view USER_SDO_NETWORK_METADATA.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01045: Undefined topology column for topology theme.

Cause: The topology theme definition did not contain the spatial column attribute.

Action: Define the attribute 'spatial_column' in the topology theme definition.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01046: WFS theme server URL is null.

Cause: The WFS server URL was not defined.

Action: Check if the WFS theme definition has a value for the attribute 'service_url'.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01047: WMS theme server URL is null.

Cause: The WMS server URL was not been defined.

Action: Check if the WMS theme definition has a value for attribute 'service_url'.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01048: Cannot load WMS map image.

Cause: The image could not be retrieved from the WMS server.

Action: Check if the WMS server URL defined in the theme definition is accessible. Change the timeout value in the theme definition if a timeout has happened.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01049: X or Y column not found in SQL query.

Cause: The SQL query string in a dynamic JDBC theme did not contain either x or y column.

Action: If your dynamic JDBC theme is using x and y columns to specify the location of a point theme (instead of an SDO_GEOMETRY column), make sure that both the x and y columns are present in the SQL query. Otherwise, check the query itself and make sure a proper SDO_GEOMETRY type column is selected.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02000: There is no database connection loaded.

Cause: Operation could not be performed unless a database connection has been added or loaded.

Action: Use Map Builder interface options to create or to add (load) a connection.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02001: Connection test failed.

Cause: The connection parameters were wrong, the database was down, or the listener was not running.

Action: Check the MapViewer log or console for database errors, and change connection parameters if necessary.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02002: Unable to register data source connection.

Cause: The connection parameters were wrong, the database was down, or the listener was not running.

Action: Check the MapViewer log or console for database errors. If the connection has been already added to Map Builder, check the connections parameters in the Map Builder preferences file (default file is oasmapbuilder.xml), and modify them if needed. Restart Map Builder to load the current preferences file. If it is a new connection being added, change the connection parameters and test the connection before trying to add it.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02050: Unable to save base map definition.

Cause: A database error may have happened while saving the base map in the USER_SDO_MAPS view.

Action: Check the MapViewer log for database errord.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02051: Unable to save style definition.

Cause: A database error may have happened while saving the style in the USER_SDO_STYLES view.

Action: Check the MapViewer log for database errors.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02052: Unable to save theme definition.

Cause: A database error may have happened while saving the theme in the USER_SDO_THEMES view.

Action: Check the MapViewer log for database errors.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02053: Unable to save tile layer definition.

Cause: A database error may have happened while saving the tile layer in the USER_SDO_CACHED_MAPS view.

Action: Check the MapViewer log for database errors.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02054: Unable to duplicate metadata.

Cause: A database error may have happened while saving a duplicate metadata.

Action: Make sure the new metadata name does not exist on the target database. Check the MapViewer log for database errors.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02055: Unable to delete metadata.

Cause: A database error may have happened while removing metadata from a database view.

Action: Check the MapViewer log for database errors.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02100: Invalid advanced style type.

Cause: The style XML definition contained an invalid or unknown advanced style type.

Action: Fix the style XML definition with an external tool, and refresh the connection in Map Builder.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02101: Unable to build theme definition.

Cause: A database error may have happened while reading theme parameters.

Action: Check the MapViewer log for database errors.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02102: Unable to parse hexadecimal value.

Cause: The string value was not recognized as a valid hexadecimal expression.

Action: Use the pattern #xxxxxx to represent the hexadecimal color value. Character # must be first followed by six digits or letters. Each x may be a digit between 0 and 9, or one of the letters "a,b,c,d,e,f".
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02103: Unable to parse style definition.

Cause: Database-related errors or SQL exceptions may have happened while reading style parameters.

Action: Check the MapViewer log for database-related errors or SQL exceptions.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02104: System will not be able to save this file.

Cause: The file path was not accessible to the system.

Action: Define a file name with a valid system path.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02105: Unable to save HTML file.

Cause: An IO error may have happened while saving file on disk.

Action: Check the MapViewer log for error details, and change file name if needed.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02200: Invalid raster block size.

Cause: The block size was nor a positive even number and power of two.

Action: Define a value that is positive and a power of two, such as 64 or 128.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02201: Unable to create GeoRaster table.

Cause: Database-related errors or SQL exceptions may have happened while creating a GeoRaster table.

Action: Check the MapViewer log for database-related errors or SQL exceptions.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02202: Unable to create GeoRaster raster data table.

Cause: Database-related errors or SQL exceptions may have happened while creating a GeoRaster raster data table. A raster data table name can not be repeated over cross schemas.

Action: Check the MapViewer log for database-related errors or SQL exceptions.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02203: Unable to insert GeoRaster record.

Cause: Database-related errors or SQL exceptions may have happened while creating a new GeoRaster record.

Action: Check the MapViewer log for database-related errors or SQL exceptions.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02204: Unable to import image file.

Cause: Database-related errors or SQL exceptions may have happened while importing image into a GeoRaster record.

Action: Check the MapViewer log for database-related errors or SQL exceptions.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02205: Unable to georeference GeoRaster object.

Cause: Database-related errors or SQL exceptions may have happened while georeferencing the GeoRaster object.

Action: Check the MapViewer log for database-related errors or SQL exceptions, and change georeferencing parameters if necessary.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02206: Unable to update spatial extent of GeoRaster object.

Cause: Database-related errors or SQL exceptions may have happened while updating the spatial extent of the GeoRaster object.

Action: Check the MapViewer log for database-related errors or SQL exceptions.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02207: Unable to generate pyramids for GeoRaster object.

Cause: Database-related errors or SQL exceptions may have happened while generating pyramids for the GeoRaster object. Map Builder uses resampling mode NN.

Action: Check the MapViewer log for database-related errors or SQL exceptions.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02208: Unable to retrieve GeoRaster object size.

Cause: Database-related errors or SQL exceptions may have happened while retrieving the GeoRaster size from the metadata.

Action: Check the MapViewer log for database-related errors or SQL exceptions.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02209: Unable to save GeoRaster metadata.

Cause: Database-related errors or SQL exceptions may have happened while registering the GeoRaster spatial extent in the USER_SDO_GEOM_METADATA view.

Action: Check the MapViewer log for database-related errors or SQL exceptions.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02210: Unable to create spatial indexes for GeoRaster table.

Cause: Database-related errors or SQL exceptions may have happened while creating spatial indexes on the GeoRaster SPATIALEXTENT attribute.

Action: Check the MapViewer log for database-related errors or SQL exceptions.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02300: Spatial data provider is not registered.

Cause: The list of registered spatial data providers did not contain the provider name.

Action: Check the Map Builder preferences file (default file is oasmapbuilder.xml) to see if it defines the provider parameters. Spatial providers are registered at Map Builder startup if they are defined in the preferences file.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02301: Unable to initialize spatial data provider.

Cause: Initialization parameters were missing or were not accepted by the spatial provider.

Action: Check the spatial provider documentation for information about initialization parameters.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02302: Unable to create an instance of spatial provider class.

Cause: The library jar file location may not have been accessible to the application.

Action: Check the spatial provider parameters in the preferences file (default file is oasmapbuilder.xml), and modify the jar file location if necessary.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-03001: MapViewer cannot process your map request. Check MapViewer log for details.

Cause: MapViewer could not process a map request sent by your Java application.

Action: Check the MapViewer server logs written when the error occurred. Correct any mistakes accordingly.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-03002: Cannot check the existance of

Cause: MapViewer could not find the specified mapping metadata or spatial data table.

Action: Make sure the mentioned item (metadata such as style/theme/basemap or spatial data table) exists in the data base.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-03003: Cannot add a datasource:

Cause: MapViewer could not add a new data source per your map request.

Action: Adding a data source on-the-fly using the Java client API is no longer allowed. Data sources should be defined in the configuration file or added using the admin web page.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-03004: cannot list pre-defined themes in:

Cause: MapViewer could not get the list of themes in the specified base map.

Action: Make sure the base map exists in the database and that it contains predefined themes.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-03005: invalid image format specified.

Cause: The image format (for the map response) specified was invalid or not supported.

Action: Make sure that only image formats specified in the API are used in your code.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-03006: Failed to establish HTTP connection to MapViewer service.

Cause: The client failed to connect to the MapViewer servlet.

Action: Make sure the networking configuration settings (such as proxy settings) are correct in the client. Also make sure the correct MapViewer URL is supplied.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-03007: Failed to locate image URL in the XML map response.

Cause: The XML map response from the server did not contain a map image URL.

Action: Check MapViewer server logs to see if there is any error when processing the map request.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05500: Oracle Maps client internal error.

Cause: Oracle Maps client encountered an internal error.

Action: Contact Oracle Support if the issue persists.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05501: Map tile layer not found. Check map tile layer name and/or data source name.

Cause: MapViewer server could not find the specified map tile layer.

Action: Make sure the map tile layer and data source do exist and their names are spelled correctly.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05502: Cannot get map tile layer config information.

Cause: The client could not get the map tile layer configuration information from the server.

Action: Make sure the map tile layer and data source do exist and their names are spelled correctly.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05503: FOI ID cannot be null.

Cause: The ID of the newly created FOI was null.

Action: Make sure the FOI ID is not null.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05504: MapViewer server base URL is not defined.

Cause: The MapViewer server base URL was not specified.

Action: Make sure the MapViewer server base URL is properly specified when creating the new MVMapView instance.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05505: Wrong map center point specified. It should be an MVSdoGeometry point.

Cause: The parameter passed as the map center into MVMapView.setCenter() or MVMapView.setCenterAndZoomLevel() was not a valid point MVSdoGeometry object.

Action: Make sure the map center parameter is specified as a valid point type MVSdoGeometry object.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05506: Invalid zoom level.

Cause: The specified zoom level was invalid.

Action: Make sure the zoom level value is not null and is within the predefined range.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05507: Map tile layer name cannot be null.

Cause: The map tile layer name was null.

Action: Make sure map tile layer name is not null.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05508: FOI Id is already used, please pick a new Id.

Cause: The ID of the newly created FOI was already used by another FOI.

Action: Choose a different ID for the new FOI.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05509: Theme-based FOI layer name is used, please pick a new name.

Cause: The name of the newly created theme-based FOI layer was already used by another theme-based FOI layer.

Action: Choose a different name for the new theme-based FOI layer.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05510: Cannot find theme-based FOI layer.

Cause: The client could not find the given theme-based FOI layer.

Action: Make sure the theme-based FOI layer has already been added to the MVMapView instance.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05511: Error occurred when sending request to MapViewer server.

Cause: An error occurred when the client sent the request to the MapViewer server.

Action: Make sure the MapViewer server is running and accessible from the client.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05512: Not enough points have been drawn.

Cause: Not enough points were drawn when calling MVRedline.generate().

Action: Make sure enough points have been drawn before calling MVRedline.generate().
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05513: Not a valid line or polygon type MVSdoGeometry.

Cause: getLength() or getArea() was called on a MVSdoGeometry object that is neither a polyline nor a polygon.

Action: Make sure these two methods are called on a polyline or polygon MVSdoGeometry object.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05514: Must have a filtering geometry when in high-light only mode.

Cause: A filtering geometry was not specified for a highlight-only theme-based FOI.

Action: Make sure the filtering geometry is specified.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05516: Synchronized remote call is not supported when using Oracle Maps' non-AJAX remoting.

Cause: An attempt was made to invoke a synchronized remote call when using the Oracle Maps non-AJAX remoting mechanism.

Action: Send an asynchronous remote call instead.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05517: Request string is too long for Oracle Maps' non-AJAX remoting.

Cause: The FOI request exceeded the length limit of the Oracle Maps non-AJAX remoting mechanism.

Action: Force the Oracle Maps client to use browser built-in AJAX remoting mechanism with MapViewer's built-in remoting proxy. Please refer to MVMapView.enableXMLHTTP for more information.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05518: Map tile layer hasn't been successfully added.

Cause: The map tile layer was not successfully added to the MVMapView instance.

Action: Make sure both of the following two conditions are met when adding a map tile layer to the MVMapView instance: 1. The MapViewer base URL is valid. 2. The map tile layer name and data source name are specified correctly.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05519: One or more parameter is missing or invalid.

Cause: One or more parametesr in the function call were missing or invalid.

Action: Make sure all required parameters are specified correctly.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05520: Geometry SRID is null.

Cause: The srid attribute of the MVSdoGeometry object was not specified.

Action: Make sure the srid is specified.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05521: Call back function cannot be null when browser's builtin XMLHttp/XMLHttpRequest is disabled.

Cause: The callback function was not specified when Oracle Maps' non-AJAX remoting mechanism was used.

Action: Specify a callback function.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05522: Client side coordinate system conversion not supported.

Cause: The client tried to invoke client-side coordinate system conversion that is not supported.

Action: Contact Oracle Support if the issue persists.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05523: Cannot process response from MapViewer server.

Cause: The client encountered an error when processing the response from the MapViewer server.

Action: Check the server response and server-side log file for the real cause.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05524: Theme feature highlighting is disabled for this theme.

Cause: The application tried to highlight or de-highlight a theme-based FOI layer that had theme feature highlighting disabled.

Action: Call MVThemeBasedFOI.enableHighlight to enable theme feature highlighting.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05525: Theme has not been added to a MVMapView instance.

Cause: The theme-based FOI layer had not been added to an MVMapView instance when the application invoked certain theme method.

Action: Make sure the theme method is invoked after the theme is added to an MVMapView instance.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06001: FOI width value is wrong.

Cause: MapViewer received an invalid width value for a FOI request.

Action: This typically indicates an application coding error. The two most common coding errors that may cause this error are: 1. The JavaScript function MVMapView.display() may have been invoked before the map container DIV object is fully materialized by the browser. 2. The map center X and Y coordinates were not specified as valid numbers. For cause 1, delay the execution of MVMapView.display() until the map container DIV object is fully materialized by the browser. For cause 2, make sure the map center X and Y coordinates are valid numbers.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06002: FOI height value is wrong.

Cause: MapViewer received an invalid height value for a FOI request.

Action: This typically indicates an application coding error. The two most common coding errors that may cause this error are: 1. The JavaScript function MVMapView.display() may have been invoked before the map container DIV object is fully materialized by the browser. 2. The map center X and Y coordinates were not specified as valid numbers. For cause 1, delay the execution of MVMapView.display() until the map container DIV object is fully materialized by the browser. For cause 2, make sure the map center X and Y coordinates are valid numbers.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06003: FOI ratX value is wrong.

Cause: MapViewer received an invalid ratX value for a FOI request.

Action: This typically indicates an application coding error. The two most common coding errors that may cause this error are: 1. The JavaScript function MVMapView.display() may have been invoked before the map container DIV object is fully materialized by the browser. 2. The map center X and Y coordinates were not specified as valid numbers. For cause 1, delay the execution of MVMapView.display() until the map container DIV object is fully materialized by the browser. For cause 2, make sure the map center X and Y coordinates are valid numbers.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06004: FOI ratY value is wrong.

Cause: MapViewer received an invalid ratY value for a FOI request.

Action: This typically indicates an application coding error. The two most common coding errors that may cause this error are: 1. The JavaScript function MVMapView.display() may have been invoked before the map container DIV object is fully materialized by the browser. 2. The map center X and Y coordinates were not specified as valid numbers. For cause 1, delay the execution of MVMapView.display() until the map container DIV object is fully materialized by the browser. For cause 2, make sure the map center X and Y coordinates are valid numbers.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06005: FOI bounding box value is wrong.

Cause: MapViewer received an invalid bounding box for a FOI request.

Action: This error should never happen. Contact Oracle Support if the issue persists.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06007: Error rendering a FIG.

Cause: MapViewer encountered an error while rendering a feature of interest (FOI) object.

Action: Check the MapViewer server-side log files for the actual cause.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06008: Error rendering a POI.

Cause: MapViewer encountered an error while rendering a point of interest (POI) image.

Action: Check the MapViewer server-side log files for the actual cause.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06009: Error processing an FOI request.

Cause: MapViewer encountered an error while processing a feature of interest (FOI) request.

Action: Check the MapViewer server-side log files for the actual cause.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06011: Unsupported FOI request type.

Cause: MapViewer encountered an unknown type of feature of interest (FOI) request.

Action: You should never see this error. Contact Oracle Support if the issue persists.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06013: Incorrect FIG 'gtype' number.

Cause: MapViewer encountered an invalid geometry type ('figgtype') in a FIG request.

Action: Contact Oracle Support if the issue persists.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06014: FOI style not found.

Cause: MapViewer could not find the style specified in the FOI request.

Action: Make sure the style specified in your individual FOI or theme-based FOI layer request exists.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06015: Map cache name is missing for bounding FOI theme.

Cause: MapViewer could not find the required map tile layer name in a bounding theme request.

Action: Make sure a map tile layer has been added to your map before issuing a bounding theme request.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06016: JDBC theme based FOI support is disabled for the given data source.

Cause: MapViewer was configured to disable JDBC theme-based FOI on the given data source.

Action: Enable JDBC theme-based FOI support in the data source definition.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06017: Create tile admin task: Map tile layer not found.

Cause: MapViewer could not find the map tile layer specified in a tile admin request.

Action: Make sure the map tile layer does exist and is correctly specified.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06018: Can not read from view USER_SDO_TILE_ADMIN_TASKS.

Cause: MapViewer could not read view USER_SDO_TILE_ADMIN_TASKS from the database connection.

Action: Make sure the SQL script mcsdefinition.sql is executed and the view USER_SDO_TILE_ADMIN_TASKS is created.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06019: Invalid SRS(spatial referencing system). This might be caused by invalid SRID or no database connection being available to retrieve SRS information

Cause: The SRID was not valid or no database connection was available to retrieve SRS information.

Action: Make sure the SRID is valid and MapViewer has a valid database connection (data source).
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06020: Invalid map tile layer name. "." is not allowed in map tile layer names.

Cause: The map tile layer name specified when creating a map tile layer contained '.' (period).

Action: Remove '.' from the map tile layer name.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06021: Map tile layer name is null. Cannot create map tile layer.

Cause: The map tile layer name specified when creating a map tile layer was empty.

Action: Make sure the map tile layer name is not empty.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06022: Cannot load the map source adapter class.

Cause: MapViewer could not load the map source adapter class.

Action: Make sure the path of the adapter class jar file is valid and it does contain the adapter class.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06023: Cannot update database map tile layer configuration.

Cause: MapViewer encountered an error when updating map tile layer configuration stored in the database view USER_SDO_CACHED_MAPS.

Action: Check the MapViewer server-side log files for the actual cause.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06024: Either <internal_map_source> clause or <external_map_source> clause must be defined

Cause: Neither the <internal_map_source> clause nor <external_map_source> clause was defined in the XML tile layer creation request.

Action: Make sure the clauses are properly specified.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06025: Zoom levels definition is missing.

Cause: Zoom levels definition was missing in the XML tile layer creation request.

Action: Make sure the <zoom_levels> element is properly specified.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06026: Coordinate system definition is missing.

Cause: The coordinate system definition was missing in the XML tile layer creation request.

Action: Make sure the <coordinate_system> element is properly specified.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06027: Map source adapter class is null.

Cause: The map source adapter class was not specified when creating an external map tile layer.

Action: Make sure the map source adapter class is specified.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06028: Property name is empty(null) and is ignored.

Cause: The 'name' attribute of the external map source adapter property was empty or null.

Action: Make sure the 'name' attribute of the property is not empty.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06029: Invalid tile image width/height definition

Cause: The tile image width and/or height were null or not valid numbers.

Action: Make sure tile image width and height are valid not null numbers.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06030: Wrong zoom levels definition.

Cause: The zoom levels definition in the XML tile layer creation request was wrong.

Action: Make sure the zoom levels definition is valid.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06031: Cannot parse coordinate definition.

Cause: MapViewer could not parse the coordinate system definition in the XML tile layer creation request.

Action: Make sure the syntax of the XML coordinate system definition is valid.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06032: Data source cannot be null.

Cause: A data source was not specified.

Action: Make sure a data source is specified.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06033: Base map cannot be null for a internal map source.

Cause: A base map was not specified for an internal map tile layer.

Action: Make sure a base map is specified.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06034: Data source does not exist.

Cause: MapViewer could not find the specified data source.

Action: Make sure the data source does exist and its name is spelled correctly.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06035: Base map does not exist.

Cause: MapViewer could not find the specified base map.

Action: Make sure the base map source does exist and its name is spelled correctly.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06036: MapTileServer is not ready. Please try again later.

Cause: The map tile server was still being initialized and was not ready.

Action: Wait until the tile server is ready.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06037: You must log in as admin user in order to perform this task.

Cause: The user did not have the admin privilege when trying to perform an admin task.

Action: Log in as the admin user before submitting the admin task.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06038: Not all scale, tile_width, tile_height definition can be empty.

Cause: None of scale, tile_width, and tile_height parameters was specified for a zoom level.

Action: Make sure at least one of parameters is specified.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06039: No map data unit conversion information is available. Cannot create mesh rules.

Cause: MapViewer could not find map data unit conversion parameters for the given coordinate system.

Action: Use tile_width instead of scale to specify zoom level definition.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06040: Map tile server is being shutdown!

Cause: The map tile server was being shutdown.

Action: Wait until MapViewer is restarted and the map tile server is ready.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06041: Invalid zoom level.

Cause: The zoom level was missing or invalid.

Action: Make sure the zoom level is not null and valid.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06042: MapViewer is not ready.

Cause: MapViewer was still being initialized and was not yet ready.

Action: Wait until MapViewer is ready.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06043: Cannot access map tile layer configuration in database.

Cause: MapViewer encountered error when trying to read the map tile layer configuration from the database.

Action: Check the MapViewer server-side log file for the real cause.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06044: The map tile is not correctly specified in the tile request.

Cause: The tx or ty parameter (or both) of the map tile request was not specified or was invalid.

Action: Make sure the tile tx and ty are properly specified.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06045: Cannot create directory.

Cause: MapViewer could not create the directory for tile storage.

Action: Make sure MapViewer can write to the file system and that the file system is not full.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06046: Cannot insert map tile layer configuration into database.

Cause: MapViewer could not insert the map tile layer configuration into the database view.

Action: Check the MapViewer server-side log file for the real cause.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06047: Cannot find map tile layer.

Cause: The specified map tile layer did not exist.

Action: Make sure the map tile layer does exist and its name is spelled correctly.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06048: Cannot load adapter jar file into database.

Cause: MapViewer encountered an error when writing the adapter jar file into the database.

Action: Check the MapViewer server-side log file for the real cause.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06049: <map_tile_server_admin_request> tag is missing from the request.

Cause: The <map_tile_server_admin_request> tag was missing in the XML tile server admin request.

Action: Make sure this tag is properly specified.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06050: Map tile layer definition is missing in the request.

Cause: <map_tile_layer> tag was missing in the XML tile layer creation/redefining request.

Action: Make sure <map_tile_layer> tag is properly specified.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06051: Unknow request type.

Cause: The tile admin request type was wrong.

Action: Make sure the tile admin request type is specified correctly.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06052: Error in parsing xml request.

Cause: MapViewer encountered error when parsing the XML tile admin request.

Action: Make sure the XML request is well formatted and free of syntax errors.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06053: Zoom level or scale is not specified or invalid.

Cause: The tile zoom level was not specified in the tile request.

Action: Make sure the tile zoom level is specified.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06054: Tile location definition is missing in the request. Either the tile mesh code or the tile location coordinates(tx,ty) must be specified.

Cause: The tx or ty parameter (or both) of the map tile request was not specified or was invalid.

Action: Make sure that the tile tx and ty are properly specified.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06055: Map location/size definition is missing in the request. Either the map bounding box(bbox) or the map center(cx,cy) and map size(width,height) must be specified.

Cause: Neither map bounding box nor map center and size was specified.

Action: Make sure either the map bounding box or the map center and size are specified.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06056: Invalid bounding box definition.

Cause: The bounding box definition was invalid.

Action: Make sure the bounding box definition is valid.
Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06057: A map tile layer with the same name already exists.

Cause: An already taken name was used to create a new map tile layer.

Action: Choose a different name for the tile layer.
Level: 1

Type: ERROR

Impact: Process

57 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-00015: Translation ignored in document "{0}": element with localRef "{1}" not found

Cause: A translation could not be applied because the underlying element to be translated was not found.

Action: If the element is expected, check the base document and any customizations to locate it.
Level: 1

Type: ERROR

Impact: Data

MDS-00016: Ignoring customization for instruction type "{0}" in metadata object "{1}" for customization layer "{2}"/"{3}": not finding element with local reference "{4}"

Cause: A customization was not applied because the underlying element to be customized was not found.

Action: If the element is expected, examine the base document and any customizations to locate the element.
Level: 1

Type: ERROR

Impact: Data

MDS-00017: Customization instruction generated for "{0}" uses local reference(s) : "{1}" which is not upgrade safe.

Cause: The customization instruction contained a local reference that was not deemed safe for an upgrade operation.

Action: Ensure that the local reference used in the customization instruction would be safe during an upgrade operation.
Level: 1

Type: ERROR

Impact: Data

MDS-00018: Fixed customization for instruction type "{0}" in metadata object "{1}" for customization layer "{2}"/"{3}": not able to find the referenced element with local reference "{4}", inserted the customized element at the best possible location.

Cause: A customization was fixed because the referenced element was not found.

Action: Correct the customized element's position if needed.
Level: 1

Type: ERROR

Impact: Data

MDS-00019: Customization document contains an invalid instruction "{0}".

Cause: A customization document that was being applied contained an unrecognized instruction.

Action: Retry the operation. If necessary, either remove the customization document, or edit it to correct or remove the offending instruction.
Level: 1

Type: ERROR

Impact: Data

MDS-00020: Layer value "{0}" contains an invalid character.

Cause: Using a layer value that has an invalid character.

Action: Layer value should conform to MDS naming standards.
Level: 1

Type: ERROR

Impact: Data

MDS-00029: Invalid namespace: The namespace "{0}" has not been registered with the MetadataManager.

Cause: An attempt was made to access a document in an unknown location or namespace.

Action: Ensure that the namespace reported is registered in the MDS configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00032: cannot parse the input file: {0}

Cause: An exception occurred while parsing the file.

Action: Record the accompanying error and contact the developers of the application.
Level: 1

Type: ERROR

Impact: Data

MDS-00033: cannot load the input file: {0}

Cause: An exception occurred while loading the file.

Action: Record the accompanying error and contact the developers of the application.
Level: 1

Type: ERROR

Impact: Files

MDS-00034: cannot write to the output file: {0}

Cause: An attempt to write to the output file failed.

Action: Record the accompanying error and contact the developers of the application.
Level: 1

Type: ERROR

Impact: Files

MDS-00035: cannot load the class: {0}.

Cause: The class file could not be loaded.

Action: Ensure the class is available on the classpath so that it can be loaded by the application.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00036: cannot instantiate the class: {0}

Cause: An exception occurred while instantiating a class.

Action: Record the accompanying error and contact the developers of the application.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00037: cannot access the class: {0}

Cause: An attempt was made to access an inaccessible class file.

Action: Record any accompanying errors and contact the developers of the application.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00039: error while attempting to parse the document {0} using SAX.

Cause: A SAX parsing exception occurred while trying to parse a document.

Action: Record the accompanying error and contact the developers of the application.
Level: 1

Type: ERROR

Impact: Data

MDS-00040: There are no namespaces registered.

Cause: The operation attempted requires at least one registered namespace.

Action: Correct the MDS configuration to include the required namespace schemas.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00041: invalid classpath entry "{0}"

Cause: An entry on the application's classpath did not exist or was invalid.

Action: Correct the application's classpath to remove the invalid entry.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00042: Classpath "{0}" does not contain any valid directories or jar files.

Cause: The application's classpath contained no valid entries.

Action: Correct the application's classpath.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00043: A name pattern mapping for path {0} already exists.

Cause: The MDS configuration had duplicate namespace mappings.

Action: The MDS configuration must be corrected to remove the duplicate namespace mappings.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00044: Metadata for MetadataObject with name {0} already exists in the configured store.

Cause: An attempt was made to create a new Metadata Object. However an object with the same MDSReference already existed.

Action: The name or location of one of the objects must be changed.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00047: Use the flushChanges method on the MDSSession to commit the changes.

Cause: Commit was disabled in the PTransaction that was being used.

Action: Use the flushChanges method on the MDSSession to commit the changes.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00054: The file to be loaded {0} does not exist.

Cause: An attempt was made to load a persistent document using a URL but the underlying document was not found in the store.

Action: Check that the document name is correct and that the store is correctly configured.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00058: Invalid Metadata Path: Metadata Path cannot be null.

Cause: The path used to create a FileMetadataStore was empty. It must point to a directory.

Action: Correct the metadata store definition in the application configuration to specify a metadata path.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00068: Unable to find a type definition for: namespace = {0}, local name = {1}, file location = {2}

Cause: A request was made to locate a definition that did not exist in the named schema.

Action: Ensure the document contains only elements which are defined in the schema for the indicated namespace.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00084: Parameter {0} is invalid.

Cause: The supplied parameter was not of the expected type.

Action: Ensure the parameter is of the expected type.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00085: Parameter {0} is missing.

Cause: The named parameter was not supplied.

Action: Ensure that the named parameter is supplied. If transferring documents ensure a parameter file name is supplied.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00089: Parameter {0} must have a value.

Cause: A required parameter was null.

Action: Ensure that the indicated parameter is not null when the method is called.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00090: Error in JNDI lookup operation on MDSInstance name {0}, JNDI name {1}: object found {2} is an instance of class {3} classloader {4}, expected an instance of class {5} classloader {6}.

Cause: An object of an unexpected type was found, and it was bound to the JNDI context as the MDSInstance.

Action: Make sure no user-written code is binding anything to the same JNDI name. If the error occurs again try restarting the application. If the error still occurs, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

MDS-00091: Unable to customize {0}, empty or null value for tip customization layer {1}

Cause: The customization layer configured as the tip, has a null or empty value.

Action: Ensure that a valid value is supplied for the tip customization layer.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00092: DuplicateNodeException. The same bean instance {0} already exists in document {1}.

Cause: An element was being added that already exists as the same bean instance within the document.

Action: Either create a new bean instance or remove the duplicate before attempting to insert in the document.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00093: List of values provided for customization layer {0} was empty or null.

Cause: The list of customization layer values was either empty or null.

Action: Ensure that a valid list of layer values for the customiizaton layer is provided.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00094: List of CustLayerUsage objects provided was empty or null.

Cause: The list of CustLayerUsage objects was either empty or null.

Action: Ensure that a valid list of CustLayerUsage objects is provided.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00095: The support to transfer customization documents based on the CustConfig and excluding customization documents of specific customization layers is not yet available.

Cause: CustOption is created to transfer customization documents based on the CustConfig and to exclude customization documents of specific customization layers which is not yet supported in MDS Transfer.

Action: Ensure CustOption is not created to use CustConfig and to exclude customization documents of specific sutomization layers.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00111: The value of the property {0} for the component {1} must be set to the default value.

Cause: The indicated component property did not have a default value.

Action: Ensure the component property is given a default value.
Level: 1

Type: ERROR

Impact: Data

MDS-00153: invalid value for indicator

Cause: The production of merged XML failed.

Action: Verify the validity of XML documents and any schemas. If necessary forward these on to Oracle Support Services with the exception message and stack trace.
Level: 1

Type: INCIDENT_ERROR

Impact: Data

MDS-00154: The ContentHandler {0} does not implement org.xml.sax.ext.LexicalHandler.

Cause: MergedXML was passed a ContentHandler that does not implement org.xml.sax.ext.LexicalHandler.

Action: Use a ContentHandler that implements org.xml.sax.ext.LexicalHandler.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00155: unable to create a JSP file for document {0}

Cause: Oracle MDS was unable to create a JSP source document.

Action: Examine the MDS base document, as well as any customizations and translations. If necessary, forward these to Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Files

MDS-00156: unable to create a JSP output directory {0}

Cause: MDS-JSP integration failed because a problem was encountered while creating a directory.

Action: Verify that you have permission to create this directory.
Level: 1

Type: ERROR

Impact: Files

MDS-00157: unable to write to JSP file {0}

Cause: MDS-JSP integration failed because a problem was encountered while trying to write to a file.

Action: Verify that you have permission to create this file.
Level: 1

Type: ERROR

Impact: Files

MDS-00158: invalid directory: {0}

Cause: MDS-JSP integration failed. An attempt was made to write to an invalid directory.

Action: Verify the value of the invalid directory.
Level: 1

Type: ERROR

Impact: Files

MDS-00159: Invalid value "{0}" for {1} attribute (type = "{2}") in document {4}.

Cause: An attempt was made to write an invalid value to an attribute.

Action: Double-check the value and attribute type.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00160: no local name has been specified for a resource

Cause: An attempt was made to create a resource without giving it a name.

Action: Verify that the resource that was created is given a local name.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00161: no local name has been specified

Cause: An attempt was made to create a resource without giving it a local name.

Action: Verify that the resource that was created is given a local name.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00162: invalid attribute value

Cause: An attempt was made to give to an invalid value to an attribute.

Action: Verify that the attribute has a valid value.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00163: property value missing from element

Cause: An element was missing a property value.

Action: Ensure that each parameter used to create the element has a property value.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00164: There is a concurrent "{1}" operation on the document "{0}".

Cause: The document on which modification was being attempted had been updated by another user after it was retrieved.

Action: Retrieve the document again.
Level: 1

Type: ERROR

Impact: Data

MDS-00165: metadata Object "{0}" has changed

Cause: The creation, updating, or renaming of a metadata object failed due to conflicting changes made by another user.

Action: Retrieve the document containing the metadata object again.
Level: 1

Type: ERROR

Impact: Data

MDS-00166: unable to locate the unique identifier, {0}:{1}, that has been configured for the element {2}

Cause: The element that required a unique identifier was created without one.

Action: Add a unique identifier attribute to the element.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00167: Invalid local name for mapping "{0}" - an empty string is not allowed.

Cause: A local name was given a null or empty value.

Action: Supply a valid local name.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00168: MDS object {0} is being used after it or its MDSInstance or PManager has been released.

Cause: An MDS object was used after it or its MDSInstance or PManager had been released

Action: Create a new MDSInstance and re-create the MDS object.
Level: 1

Type: ERROR

Impact: Session

MDS-00169: The MDS instance is not ready for use because metadata deployment is in progress (status is "{0}"). Deployment messages so far are: "{1}".

Cause: The MDS instance cannot be used until metadata deployment has finished.

Action: Try again later after metadata deployment has completed.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00170: The MDS instance is not usable because metadata deployment failed with status "{0}".

Cause: Metadata deployment failed with the given status.

Action: Please fix the error and redeploy the application's metadata using the importMAR operation on MDS Application Runtime MBean. Also, refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00171: Document "{0}" already has unsaved updates on another instance of this metadata object in this session.

Cause: An attempt was made to update metadata using more than one instance of the same metadata object at the same time in the same session.

Action: Save the changes on the metadata object that already has updates before attempting to update it via another metadata object, or make further modifications on the metadata object on which updates have already been made.
Level: 1

Type: ERROR

Impact: Data

MDS-00172: The value "{0}" of local unique attribute {1} on the {2} element that is being inserted or updated in document {3}, is already used by a sibling element.

Cause: An attempt was made to have two local unique attributes with the same value on elements that share the same parent.

Action: Use a different value for the local unique attribute on the element that is being inserted or updated.
Level: 1

Type: ERROR

Impact: Data

MDS-00173: Attribute {0} of element {1} in document {2} has a null value.

Cause: The value of the named attribute was null.

Action: Provide a non-null value for the attribute or remove the attribute.
Level: 1

Type: ERROR

Impact: Data

MDS-00174: A tenant scoped MDSInstance {0} is being requested with a null TenantId.

Cause: A tenant scoped MDSInstance was requested passing null for TenantId.

Action: Supply a non null TenantId or request an unscoped MDSInstance.
Level: 1

Type: ERROR

Impact: Session

MDS-00176: The operation on MDSInstance {0} cannot be performed as it is not tenant scoped.

Cause: The operation performed on the MDSInstance was invalid with a TenantId because it was not a tenant scoped MDSInstance.

Action: Perform the operation on an MDSInstance initialized for multitenant operation.
Level: 1

Type: ERROR

Impact: Session

MDS-00177: The operation on resource {0} cannot be performed as it is not configured to be owned by the current tenant scope.

Cause: The operation performed was illegal as the resource being created, updated or deleted has global scope and the current scope is tenant or the resource has tenant scope and the current tenant is global.

Action: Check that the configuration of the namespaces and CustomizationClasses is correct and that the correct customization class list is being used.
Level: 1

Type: ERROR

Impact: Session

MDS-00178: Multitenant MDSInstance {0} cannot be created with TenantId {1} when multitenant-capable in the persistence configuration = {2} and the JVM flag oracle.multitenant.enabled = {3}.

Cause: A valid TenantId was not provided appropriate to the configuration.

Action: Request an MDSInstance appropriate to the configuration.
Level: 1

Type: ERROR

Impact: Session

MDS-00179: The requested MDSInstance {0} cannot be returned for TenantId {1} as it was originally created with multitenant enabled = {2}.

Cause: The configuration at the time the MDS Instance was requested did not match with the configuration when it was originally created.

Action: Request an MDSinstance appropriate to the original configuration.
Level: 1

Type: ERROR

Impact: Session

MDS-00180: Only a single tenant cache configuration is allowed.

Cause: The number of TenantCacheConfigs was not 1.

Action: Pass a single tenant cache configuration object. Although the constructor for the TenantCacheConfigs class takes an array this is reserved for future use.
Level: 1

Type: ERROR

Impact: Session

MDS-00181: Only a single tenant document cache configuration is allowed.

Cause: The number of TenantDocumentCacheConfigs was not 1.

Action: Pass a single tenant document cache configuration object. Although the constructor for the TenantDocumentCacheConfigs class takes an array this is reserved for future use.
Level: 1

Type: ERROR

Impact: Session

MDS-00182: Tenant cache configuration information cannot be requested for the global tenant.

Cause: Tenant cache configuration information was being requested for the global tenant.

Action: Do not request the tenant cache configuration for the global tenant - use getCacheConfig directly from MDSConfig
Level: 1

Type: ERROR

Impact: Session

MDS-00183: Tenant document cache configuration information cannot be requested for the global tenant.

Cause: Multitenant document cache information was being requested for the global tenant.

Action: Do not request the tenant document cache configuration for the global tenant - use getDocumentCacheConfig from NamespaceConfig
Level: 1

Type: ERROR

Impact: Session

MDS-00184: The relationship from {0} to {1} is invalid because the latter is configured as a global resource and cannot be referenced from a tenant resource because the corresponding relationship is defined with cascade delete enabled.

Cause: Relationships with cascade delete enabled were spanning tenant boundaries.

Action: Reconfigure the relationship with cascade delete disabled or ensure the parent reference is within the same tenant scope.
Level: 1

Type: ERROR

Impact: Session

MDS-00185: The relationship from {0} to {1} is invalid because the latter is configured as a global resource and cannot be referenced from a tenant resource because the corresponding relationship is defined with enforced integrity.

Cause: Relationships with defined referential integrity were spanning tenant boundaries.

Action: Reconfigure the relationship without referential integrity or ensure the parent reference is within the same tenant scope.
Level: 1

Type: ERROR

Impact: Session

MDS-00186: A {0} element is already present in the parent {1} element in document {2}, but with the QNameLUID identification mechanism only one is allowed.

Cause: An attempt was made to have two or more elements with same QName under same parent while QNameLUID identification mechanism is used.

Action: Remove duplicate instances of elements with same QName
Level: 1

Type: ERROR

Impact: Data

MDS-00187: The existing {0} element in the parent {1} element in document {2} is automatically removed, and new customized {0} element of "{3}"/"{4}" customization layer is inserted since with the QNameLUID identification mechanism, only one is allowed.

Cause: An attempt was made to have two or more elements with same QName under same parent while QNameLUID identification mechanism is used.

Action: Removed duplicate instances of elements with same QName
Level: 1

Type: ERROR

Impact: Data

MDS-00189: The existing {0} element with unique id {1} in the parent {2} element in document {3} is automatically removed, and new customized {0} element with unique id {1} of "{4}"/"{5}" customization layer is inserted since {0} element is type-annotated to overwrite duplicates.

Cause: An attempt was made to have two or more elements with same QName under same parent having the same unique ID value while overwriteDuplicate mechanism is used.

Action: Removed duplicate instances of elements with same QName having the same unique ID value
Level: 1

Type: ERROR

Impact: Data

MDS-00190: A call to {0} on the current MDSSession does not specify the correct transaction key

Cause: The current MDS Session was created using a transaction key and the subsequent operation was either being attempted passing no key or a different one from that originally used.

Action: If the MDS Session is created using a transaction key, then use the MDSSession API's that take a transaction key and use the same key.
Level: 1

Type: ERROR

Impact: Session

MDS-00191: An exception occured in PChangeListener {0}

Cause: The MetadataStoreCommunicator was attempting to notify the listener when an exception ocurred.

Action: Check the HandlePChanges method of the listener.
Level: 1

Type: ERROR

Impact: Session

MDS-00193: Document with the MDSReference {0} contains an ID attribute with an invalid value: {1}

Cause: The value of the ID attribute is invalid according to the schema definition.

Action: Ensure that the ID conforms to the schema definition .
Level: 1

Type: NOTIFICATION

Impact: Data

MDS-00194: Auditing is disabled for component {0}.

Cause: There was an error registering the audit event definition(s) for the component.

Action: Ensure that the audit event definitions for the component are valid and that the audit service is functional.
Level: 1

Type: NOTIFICATION

Impact: Configuration

MDS-00195: The custom audit event of type "{0}" that was associated with "{1}" is not audited because the MDS object was unmodified since the last time the changes in the MDSSession were committed.

Cause: MDS object associated with the event was unmodified since the last time the changes in the MDSSession were committed. A custom audit event is discarded if the associated MDSObject is not modified.

Action: No action required.
Level: 1

Type: WARNING

Impact: Programmatic

MDS-00196: The MDSSession referenced by the audit component "{0}" is invalid.

Cause: The MDS audit support instance is being used even after the MDSSession that was used to created it is no longer referenced.

Action: Fetch the audit support instance from the MDSSession and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-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 the database sequence "MDS_DOCUMENT_ID_NN_S" is corrupt

Cause: The database sequence used for generating the unique document ID was corrupt.

Action: Retry the operation after deploying metadata to another MDS database repository partition.
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-00915: MDS repository is incompatible with the middle tier for dumping or restoring metadata.

Cause: The MDS repository was older than minimum version required by the middle tier to dump or restore metadata.

Action: Retry the operation after upgrading the MDS repository to newer version or use compatible middle tier to perform the operation.
Level: 1

Type: ERROR

Impact: Upgrade

MDS-00916: MetadataStore configured for {0} does not support deployment management.

Cause: The metadata store configured for the resource did not support deployment management.

Action: Deployment management is supported in MDS repository version 11.1.1.4.0 (11gR1 PS3 patchset) onwards. Upgrade the repository to this version or later.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00918: Connection details for the MDS repository are incomplete. The values for "{0}" are invalid

Cause: The MDS repository connection details were invalid or missing.

Action: Specify correct values for the MDS repository details in the configuration and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00919: Internal error: The database context for this repository appears to be corrupt.

Cause: The database context was invalid.

Action: Verify that the repository details are correct in the configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00922: The ConnectionManager "{0}" cannot be instantiated.

Cause: There was an error instantiating the ConnnectionManager class

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

MDS-00923: Unable to create sandbox "{0}"

Cause: An error occurred during creation of sandbox.

Action: Look in the error message log for the exact reason for the failure.
Level: 1

Type: ERROR

Impact: Data

MDS-00928: Invalid document reference, package "cust" should appear before package "trans" in the names of customization translation documents.

Cause: An internal MDS document (one in package mdssys) was found with an invalid name, or an attempt was made to create a name object with such an invalid name.

Action: Avoid using package or document names containing path element "mdssys" which is reserved for internal MDS use. If necessary, remove such invalid documents from the metadata store.
Level: 1

Type: ERROR

Impact: Data

MDS-00929: unable to look up name "{0}" in JNDI context

Cause: The implementation class to use for initial context was not found.

Action: Verify that environment properties are configured using system properties or application resources files.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00930: The JNDI location details for the registered datasource are incomplete.

Cause: JNDI location details were found to be incomplete.

Action: Provide complete JNDI location information in the configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00931: The database version is {0}.{1}, but MDS requires at least {2}.{3}.

Cause: The database version is older than the minimum database version required for hosting MDS repository.

Action: Upgrade the database to the minimum required version. Contact the database administrator for assistance.
Level: 1

Type: ERROR

Impact: Upgrade

MDS-00932: unknown database vendor {0}

Cause: The database vendor could not be identified.

Action: Verify that the MDS repository is hosted on supported database vendors.
Level: 1

Type: ERROR

Impact: Installation

MDS-00933: cannot create data source using URL "{0}"

Cause: An error occurred while creating the data source using the specified URL.

Action: Verify that the URL specified is correct and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00934: XDB is not supported on database platform {0}.

Cause: An attempt was made to store XML metadata in a non-XDB database.

Action: Verify that the correct MDS repository is being used.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00935: Unable to complete operation even after maximum connection retries ({0}).

Cause: An error occurred while performing operation.

Action: Ensure that the database is running. Retry the operation later.
Level: 1

Type: ERROR

Impact: High Availability

MDS-00936: Fast Connection Failover is not supported on the underlying database connection ({0}).

Cause: The underlying database connection did not support fast connection failover, and retry-connection was set to true in either the config file, or programmatically.

Action: Either stop and then restart the database connection and configure it to allow fast connection failover, or do not attempt to set retry-connection to true.
Level: 1

Type: ERROR

Impact: High Availability

MDS-00937: A local transaction operation like commit or rollback cannot be used in a global transaction on connection "{0}".

Cause: The database connection was configured for global transactions, but MDS was not configured to support global transactions.

Action: Reconfigure the database connection to use local transactions. Change "tx-level" attribute on the MDS datasource to "local".
Level: 1

Type: ERROR

Impact: Configuration

MDS-00938: Unable to get an ADF library class loader

Cause: MDS expects to retrieve a resource from an ADF library, but is unable to obtain an ADF library classloader.

Action: Consider whether the resource should be repackaged in an ADF library rather than an ordinary jar.
Level: 1

Type: ERROR

Impact: Data

MDS-01059: document with the name {0} missing in the source metadata store

Cause: The document to be transferred did not exist in the source metadata store.

Action: Verify that the document name is correct, and that it exists in the source metadata store.
Level: 1

Type: ERROR

Impact: Data

MDS-01061: Listener {0} cannot be instantiated.

Cause: The listener class did not exist.

Action: Verify that the name of the listener class is correct. Ensure that the class is available on the class path.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01104: finding no documents for processing that match the pattern provided

Cause: No documents were found on the source metadata store that matched the pattern provided, or that matched the document name.

Action: Provide another pattern or document name, or provide another metadata store in which to look for the documents.
Level: 1

Type: ERROR

Impact: Data

MDS-01105: invalid label {0}

Cause: The label specified for the source metadata store did not exist.

Action: Verify that the label name is correct, or provide a label that exists in the source metadata store.
Level: 1

Type: ERROR

Impact: Data

MDS-01106: The TransferTypeRestriction {0} can not be associated with given TransferType {1}.

Cause: The given TransferTypeRestriction can not be associated with the specified TransferType.

Action: Ensure that given TransferTypeRestriction is valid for the specified TransferType.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01107: Post transfer label cannot be created in target store.

Cause: Post transfer label cannot be created in the target store. Examine the cause exception messages to find the root cause of it.

Action: Examine any accompanying messages to decide if further action is required.
Level: 1

Type: ERROR

Impact: Data

MDS-01108: TransferType cannot be null for ExtendedTransferType.

Cause: TransferType provided to create ExtendedTransferType was null.

Action: Provide valid TransferType to create ExtendedTransferType.
Level: 1

Type: ERROR

Impact: Data

MDS-01109: The target archive configured in ArchiveMetadataStore already exists. Cannot export the documents into an existing archive file.

Cause: The target archive already exists. Exporting the documents into an existing archive is not allowed.

Action: Export the documents into a non existing archive file.
Level: 1

Type: ERROR

Impact: Data

MDS-01110: Sandbox export operation allowed only from a database metadata store to an archive metadata store.

Cause: Either source metadata store is not a database or the target metadata store is not an archive in sandbox export operation.

Action: Configure source metadata store to be a database and target metadata store to be an archive in sandbox export operation.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01111: Sandbox import operation allowed only from Archive Metadata Store to a Database Metadata store.

Cause: Either source metadata store is not an archive metadata store or the target metadata store is not a database in sandbox import operation.

Action: Configure source metadata store to be an archive metadata store and target metadata store to be a database in sandbox import operation.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01112: Transfer unit list in a Sandbox export/import operation should have atleast one transfer unit.

Cause: Transfer unit list in Sandbox export/import operation empty.

Action: Ensure that there is at least one transfer unit to be transferred in sandbox export/import operation.
Level: 1

Type: ERROR

Impact: Data

MDS-01113: Sandbox metadata file required for import to a new sandbox operation.

Cause: Sandbox metadata file missing in source Archive metadata store in import to a new sandbox operation.

Action: Import to a new sandbox only from an archive store whose contents were exported from a sandbox and contain sandbox metadata document.
Level: 1

Type: ERROR

Impact: Data

MDS-01114: Sandbox with same name as the one imported in a sandbox import operation exists on the target metadata store.

Cause: Sandbox with same name already exists on the target metadata store and the flag to force creation of sandbox is not set to true.

Action: Pass true for forceSBCreation to TransferParams.createForSandboxImport() or destroy sandbox already existing with same name on the target metadata store in sandbox import operation.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01115: Source sandbox in a sandbox export operation does not contain metadata.

Cause: Source sandbox in export operation was not created with metadata.

Action: Export from a Sandbox that was created with metadata.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01116: Existing target sandbox in import operation does not contain metadata.

Cause: Target sandbox in an import into an existing sandbox operation was not created with metadata.

Action: Import into an existing sandbox that was created with metadata.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01117: Sandbox archive imported into an existing sandbox.

Cause: The archive imported into an existing sandbox contains sandbox metadata.

Action: Import only regular archives(that do not contain sandbox metadata) into an existing sandbox.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01118: Sandbox export operation not supported because the source MDS database repository is of older version that does not support this feature.

Cause: Sandbox metadata is needed to transfer documents from sandbox. Source store being used does not support storing metadata for sandbox.

Action: Sandbox metadata is supported in MDS repository version 11.1.1.4.0 (11gR1 PS3 patchset) onwards. Upgrade the repository to this version or later.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01119: Sandbox import operation not supported because the target MDS database repository is of older version that does not support this feature.

Cause: Sandbox metadata is needed to transfer documents from sandbox. But target store being used does not support storing metadata for sandbox.

Action: Sandbox metadata is supported in MDS repository version 11.1.1.4.0 (11gR1 PS3 patchset) onwards. Upgrade the repository to this version or later.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01120: Sandbox transfer unit list creation not supported because the source MDS database repository is of older version that does not support this feature.

Cause: Sandbox metadata is needed to transfer documents from sandbox. Source store being used does not support storing metadata for sandbox.

Action: Sandbox metadata is supported in MDS repository version 11.1.1.4.0 (11gR1 PS3 patchset) onwards. Upgrade the repository to this version or later.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01121: Document "mds-transfer-config.xml" cannot be read by MDSTransfer.

Cause: The /meta-inf/mds-transfer-config.xml document cannot be read from source store. Refer to cause exception for more information on the actual reason for failure.

Action: Look for messages that describe the cause exception, and then take the appropriate action.
Level: 1

Type: ERROR

Impact: Data

MDS-01122: Metadata Object Name "{0}" specified in the mds-transfer-config.xml to preserve user updated documents in target repository is not a valid metadata object name.

Cause: Metadata object name specified in /meta-inf/mds-transfer-config.xml to preserve user updated documents in target repository is not a valid metadata object name.

Action: Make sure the document name specified in mds-transfer-config.xml is a valid metadata object name but not a speical document name.
Level: 1

Type: ERROR

Impact: Data

MDS-01123: The metadata path "{0}" specified in the mds-transfer-config.xml to preserve user updated documents in target repository is not a valid metadata path.

Cause: The metadata path specified in /meta-inf/mds-transfer-config.xml to preserve the user updated documents in target repository is not a valid metadata path.

Action: Make sure the metadata path specified in mds-transfer-config.xml is a valid metadata path.
Level: 1

Type: ERROR

Impact: Data

MDS-01150: Reference is null or empty.

Cause: A reference value was null or empty.

Action: Use a valid reference value that is not empty or null.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01151: Id/LocationPath reference is null or missing.

Cause: An Id/LocationPath reference value was null or empty.

Action: Use a valid Id/LocationPath reference value that is not empty or null.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01153: invalid LocationPath expression "{0}"

Cause: The LocationPath expression was invalid.

Action: Use a valid LocationPath format. The LocationPath expression should follow the format "/text()" or "/text()[x]", where 'x' is the index of "text block".
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01154: invalid LocationPath expression "{0}"

Cause: The node index in the LocationPath expression was invalid.

Action: Change the node index in the LocationPath expression to a number greater than or equal to 1.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01158: Expecting a base document. Reference "{0}" is a special document.

Cause: A base document was expected, but the reference was a special document.

Action: Use a valid base document.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01159: Expecting absolute document reference. Reference "{0}" has local element reference portion.

Cause: The supplied reference was not the expected type.

Action: Ensure the reference is of the expected type.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01160: Expecting absolute document reference. Reference "{0}" is a relative reference to the document.

Cause: The supplied reference was not the expected type.

Action: Ensure the reference is of the expected type.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01161: Reference "{0}" has an invalid character "{1}".

Cause: The supplied reference did not follow the MDS naming standard.

Action: Use valid characters for the reference.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01162: Reference "{0}" has an invalid XML attribute character.

Cause: The supplied reference did not follow the MDS naming standard.

Action: Use valid characters for the reference.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01163: invalid reference "{0}"

Cause: The supplied reference did not follow the MDS naming standard.

Action: Ensure that the reference follows the MDS naming standard.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01164: invalid reference "{0}" for a translation document

Cause: The supplied reference did not have the expected document extension (.xlf).

Action: Use the correct extension, .xlf, for the translation document.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01165: invalid reference "{0}" for a customization document

Cause: The supplied reference did not have the expected document extension (.xml).

Action: Use the correct extension, .xml, for the customization document.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01166: invalid reference "{0}" for a metadata extension document

Cause: The supplied reference did not have the expected document extension (.rdf).

Action: Use the correct extension, .rdf, for the metadata extension document.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01167: There is no namespace declaration for the prefix "{1}" used in LocationPath expression "{0}".

Cause: The LocationPath expression was incomplete.

Action: Use a valid LocationPath format.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01168: Partition name "{0}" starts or ends with character "{1}". Partition name cannot contain leading or trailing spaces, ".", "-"

Cause: The supplied partition name contained leading or trailing spaces, ".", "-".

Action: Ensure that the partition name follows the MDS naming standard for partitions.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01169: Partition name "{0}" has an invalid character "{1}".

Cause: The supplied partition name did not follow the MDS naming standard.

Action: Use valid characters for the partition name.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01170: Partition name is null or empty.

Cause: Partition name value was null or empty.

Action: Use a valid partition name that is not empty or null.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01171: The ID prefix generated by concatenating the layer name "{0}" and layer value "{1}" is not a valid MDS ID.

Cause: The ID prefix generated by concatenating the layer name with layer value did not follow the MDS ID naming standard.

Action: Ensure that the ID prefix generated by concatenating the layer name with layer value follows the MDS ID naming standard.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01200: This operation is not supported.

Cause: An MDS query operation was attempted, but this particular operation is not supported.

Action: Note the stack backtrace and context of the operation, and contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

MDS-01201: An invalid parameter cannot be used when constructing a query condition.

Cause: An invalid parameter was passed to the class ConditionFactory.

Action: Note the stack backtrace and context of the operation, and contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

MDS-01205: A SQL error is occurring when performing the query: "{0}" with binds {1}.

Cause: An MDS query on a database store led to a SQL error.

Action: Note the stack backtrace and context of the operation, including the reported SQL query and error, and contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

MDS-01206: The array size for the query must be greater than zero.

Cause: An MDS query specified a fetch unit size that was not positive.

Action: Note the stack backtrace and context of the operation and contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

MDS-01207: The namespace mapping for the prefix "{0}" specified in the location path, is missing.

Cause: During XPath evaluation, the namespace prefix was used, but the prefix was not mapped to a namespace.

Action: Note the stack backtrace and context of the operation and contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

MDS-01250: The file path "{0}" does not exist.

Cause: An invalid path was provided.

Action: Retry the operation with a valid file path.
Level: 1

Type: ERROR

Impact: Files

MDS-01251: The parameter file {0} has no namespace on the document element.

Cause: A namespace was missing from the parameter file provided.

Action: Provide a parameter file with valid namespace information.
Level: 1

Type: ERROR

Impact: Data

MDS-01252: The parameter file {0} must have either {1} or {2} definition.

Cause: No source stores or target stores information were provided in the parameter file.

Action: Check the parameter file to have source and target store information and retry.
Level: 1

Type: ERROR

Impact: Data

MDS-01253: The parameter file {0} must not have both {1} and {2} definitions.

Cause: An attempt was made to transfer from source directory to target directory. Both source and target as directories is not supported.

Action: Provide correct source and target definition. Either source or target should be a metadata store.
Level: 1

Type: ERROR

Impact: Data

MDS-01254: The parameter file {0} contains same store definition for sourceStore and targetStore.

Cause: An attempt was made to transfer from and to the same store. The definition for sourceStore cannot be the same as the definition for targetStore.

Action: Provide correct source and target information. Change either source or target store definition.
Level: 1

Type: ERROR

Impact: Data

MDS-01255: The property {0} has not been supplied.

Cause: The required property was missing from the parameter file.

Action: Check the parameter file and supply the required property. Refer to the MDS documentation for the correct syntax. A sample parameter file is also part of documentation.
Level: 1

Type: ERROR

Impact: Data

MDS-01258: The value {0} for property {1} is invalid.

Cause: An invalid property value was provided in the parameter file.

Action: Provide a valid property value. Refer to the MDS documentation for the correct syntax. A sample parameter file is also part of documentation.
Level: 1

Type: ERROR

Impact: Data

MDS-01259: The metadata store "{0}" cannot be instantiated.

Cause: An error occurred during the instantiation of the class for the metadata store.

Action: Verify that correct values are provided in the parameter file. Refer to the error messages in application logs that describe the cause exception for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Data

MDS-01260: failure to process command-line arguments

Cause: Invalid command-line parameters were provided.

Action: Provide valid command-line parameters, and retry the operation. Refer to the MDS documentation for syntax of the tool parameters, or run the tool without parameters in order to get the Help message.
Level: 1

Type: ERROR

Impact: Data

MDS-01262: failure of transfer operation on a read-only target metadata store

Cause: The target metadata store used for transfer was read-only, for example a classpath store.

Action: Provide a writable target metadata store.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01263: operation failure on the resource {0} because source metadata store is read-only

Cause: An attempt was made to delete, create, update or get a mutable metadata object from a read-only source metadata store.

Action: Provide a writable source metadata store.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01264: The given element must contain either "customization" or "translation" configuration.

Cause: A customization or a translation configuration was missing for an element.

Action: Examine the transfer parameter file for valid MDS configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01265: Invalid parameter file {0}. Reason: <{1}:{2}> {3}

Cause: Parameter file provided was not valid.

Action: Provide a valid parameter file. Refer to the MDS documentation for the correct syntax. A sample parameter file is also part of documentation. Refer to sample parameter for correct syntax.
Level: 1

Type: ERROR

Impact: Files

MDS-01266: The associated customization document is missing for a given customization class {0} for the given document name {1}.

Cause: The associated customization document for the given customization class did not exist.

Action: If the associated customization document was to be transferred, verify that it exists. Otherwise, no action is required.
Level: 1

Type: ERROR

Impact: Data

MDS-01267: The associated translation document is not found for a given locale {0} for the given document name {1}.

Cause: Associated translation document did not exist for the given locale.

Action: If the associated translation document was expected to be transferred, verify if it exists, otherwise, no action required.
Level: 1

Type: ERROR

Impact: Data

MDS-01268: The associated extended metadata document for the given document name {0} is missing.

Cause: No associated extended metadata document for the given document name existed.

Action: If the document was to be transferred, verify that the document exists. Otherwise, no action is required.
Level: 1

Type: ERROR

Impact: Data

MDS-01270: Opening and closing parentheses do not match.

Cause: Either an opening or closing parentheses was missing.

Action: Check and correct the namespace mappings provided. Each opening parentheses should have an equivalent closing parentheses and vice versa.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01271: Cannot get the dependency registry

Cause: An error occurred while getting the dependency registry.

Action: Retry the operation. If the problem persists, look for messages that describe the cause exception for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01272: unable to read mds-webapp-config.xml file

Cause: The mds-webapp-config.xml file was invalid.

Action: Confirm that the mds-webapp-config.xml file for the application is well formed, and valid.
Level: 1

Type: ERROR

Impact: Files

MDS-01273: The operation on the resource {0} failed because source metadata store mapped to the namespace {1} is read only.

Cause: An attempt was made to delete, create, update or get a mutable metadata object from a readonly source metadata store.

Action: Provide a writable source metadata store.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01301: Element "{1}", namespace "{0}" is not a valid child under parent "{3}", namespace "{2}".

Cause: An attempt was made to add, insert or replace a child element of the wrong type.

Action: Check the schema definition and ensure that the child element is the correct type.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01302: failure to load schema file "{0}"

Cause: An exception occurred in the XMLEF layer during processing of the schema definitions.

Action: Look for messages that describe the cause exception, and then take the appropriate action.
Level: 1

Type: ERROR

Impact: Data

MDS-01303: failure to register grammar from schema file "{0}"

Cause: An exception occurred in the XMLEF layer during addition of schema definitions.

Action: Look for messages that describe the cause exception, and then take the appropriate action.
Level: 1

Type: ERROR

Impact: Data

MDS-01305: failure to locate schema file "{0}".

Cause: The schema definition file was not found.

Action: Verify that the schema file name is correct, and that it is in the correct location.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01306: Grammar from a Web application can be added only once.

Cause: There were multiple method calls to add grammar from a web application.

Action: Verify that a grammar definition has already been added for the given MDSInstance and ServletContext. If it has then remove the calls to add it multiple times.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01307: no schema files for processing

Cause: No schema files were found against which beans can be generated.

Action: Pass an existing schema file to the bean generator.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01308: Event "{0}" is not supported.

Cause: An attempt was made to use event types that are not supported for the selected content model.

Action: Use only the event types that are allowed for the selected content model.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01309: ContentModelPipeline is empty.

Cause: The contentModelPipeline contained an empty or null builder list.

Action: A list of one or more valid builders must be available in the ContentModelPipeline.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01310: Invalid ContentModelPipeline. Missing {0}.

Cause: The expected builder was not available in builder list of the ContentModelPipeline.

Action: Valid builders must be supplied to the ContentModelPipeline.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01311: The DOM tree does not support the DOM event model.

Cause: This DOM Document did not implement EventTarget interface.

Action: Verify whether the Oracle XML Developer's Kit is used.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01312: Change-list transaction state is invalid.

Cause: The current change-list transaction state is invalid for the customization operation performed.

Action: Ensure Change-list to be in valid transaction state to perform the necessary customization operation.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01313: The argument for document cannot be null.

Cause: The argument for DocumentName was null.

Action: Provide a valid DocumentName.
Level: 1

Type: ERROR

Impact: Data

MDS-01314: TypeAnnotationProvider cannot be null.

Cause: The argument for TypeAnnotationProvider was null.

Action: Provide a valid TypeAnnotationProvider.
Level: 1

Type: ERROR

Impact: Data

MDS-01316: Support for XPath is not implemented yet.

Cause: Support for XPath has not been implemented yet.

Action: Provide a valid Configurable ID.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01319: JAXP support is not available. Falling back to using Oracle XML Developer's Kit for parsing the document {0}.

Cause: JAXP support was not available.

Action: None.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01320: Modifying the prefix declaration for {0} from "{1}" to "{2}" in document {3} through customizations is not supported.

Cause: An attempt was made to change an existing prefix declaration.

Action: Avoid attempts to change existing prefix declarations.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01321: Node type should be one of ImmutableModelNode.ELEMENT or ImmutableModelNode.TEXT or ImmutableModelNode.CDATA.

Cause: The node was not of the type ImmutableModelNode.ELEMENT or ImmutableModelNode.TEXT or ImmutableModelNode.CDATA.

Action: Ensure the node type is one of the following types: ImmutableModelNode.ELEMENT or ImmutableModelNode.TEXT or ImmutableModelNode.CDATA.
Level: 1

Type: ERROR

Impact: Data

MDS-01322: Value "{0}" does not satisfy "{1}" type.

Cause: The data type conversion failed.

Action: Verify that the expected XSD built-in simple data type and the passed-in string value are convertible.
Level: 1

Type: ERROR

Impact: Data

MDS-01323: Value "{0}" has an incorrect number of characters for a base64Binary.

Cause: The value did not represent a valid Base64Binary.

Action: Verify that the input value is valid.
Level: 1

Type: ERROR

Impact: Data

MDS-01324: Unknown XML schema built-in type "{0}"

Cause: An attempt was made to use an unknown XML schema built-in type.

Action: Use only valid XML schema built-in types.
Level: 1

Type: ERROR

Impact: Data

MDS-01325: unable to load type definition "{0}"

Cause: Could not load this type definition because the specified location did not exist.

Action: Ensure that the specified location for the type definition exists.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01326: Loading of type definition from element "{0}" is not supported.

Cause: An attempt was made to load a type definition from the specified element that is not supported in the MDS configuration.

Action: Examine the schema definition to ensure that the entry specified in type definition is correct.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01327: unable to load data from "{0}" into {1}

Cause: An error occurred while loading the content of this configuration element.

Action: Examine the schema definition to ensure that the content of this configuration element is correct.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01328: unable to load element "{0}" into {1}

Cause: An error occurred while loading this configuration element.

Action: Examine the schema definition to ensure this configuration element is correctly specified in the MDS configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01329: unable to load element "{0}"

Cause: An error occurred while loading this configuration element.

Action: Examine the schema definition to ensure this configuration element is correctly specified in the MDS configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01330: unable to load MDS configuration document

Cause: An I/O or parsing error occurred while loading the MDS configuration document.

Action: Verify that the URL is correct, and ensure that the document contains valid MDS configuration information.
Level: 1

Type: ERROR

Impact: Files

MDS-01331: unable to load MDS configuration document "{0}"

Cause: An error occurred in loading the content of MDS configuration document.

Action: Verify that the URL is correct, and ensure that the document contains valid MDS configuration information.
Level: 1

Type: ERROR

Impact: Files

MDS-01332: Class {0} is not a subclass or implementation of {1}.

Cause: The class specified in the configuration information did not extend the required class, or implement the required interface.

Action: Ensure that the class specified in the configuration information extends the correct class, or implements the correct interface.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01333: missing element "{0}"

Cause: This element was missing from the MDS configuration information.

Action: Ensure that the element is specified in the configuration information.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01334: missing element "{0}" in document "{1}"

Cause: This element was missing from the MDS configuration information.

Action: Ensure that this element is specified in the configuration document.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01335: namespace "{0}" mapped to metadata-store-usage "{1}" but its definition was not found in MDS configuration.

Cause: Metadata-store-usage element that was referenced by a namespace not found in MDS configuration.

Action: Ensure that this element is specified in MDS configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01336: No XML element is provided to create {0}.

Cause: A null XML element was passed to the constructor of this configuration object.

Action: Ensure that a valid XML element is provided to create a new instance of this configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01337: No URL is provided to create {0}.

Cause: A null URL was passed to the constructor of this configuration object.

Action: Ensure that a valid URL is provided to create a new instance of this configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01340: More than one metadata store can be resolved for the namespace "{0}".

Cause: There were multiple namespace to metadata store mappings in the persistence configuration that satisfied the request for the metadata store of a given namespace.

Action: Correct the namespace mapping in persistence configuration to ensure that the namespace is mapped to only one metadata store.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01341: Namespace mapping for "{0}" is overridden by namespace mapping for "{1}"; the first mapping is not used.

Cause: A conflicting mapping to this namespace has already been defined in the persistence configuration.

Action: Correct the namespace mapping in the persistence configuration to ensure that there is no conflicting mapping to this namespace.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01342: No metadata store is mapped to the namespace "{0}".

Cause: No namespace mapping could be found in the persistence configuration for the specified namespace.

Action: Ensure that a correct namespace is passed into the method concerned, or alter the application configuration to define the specified namespace.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01343: There is a duplicate file extension mapping for "{0}".

Cause: A mapping to this file extension has already been defined in the file type configuration.

Action: Remove the duplicate file extension mapping from the file type configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01344: cannot create {0} due to null parameter

Cause: A null parameter was passed to the constructor of this configuration object.

Action: Ensure that a valid parameter is provided to create a new instance of this configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01346: The given namespace path "{0}" is not a valid path.

Cause: An invalid path was provided to create a namespace.

Action: Ensure that a valid path is provided to create a namespace.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01347: Base restriction is supported only for classpath store or servlet context store: namespace "{0}" mapped to "{1}".

Cause: The base restriction was specified for a metadata store other than the classpath metadata store and servlet context store.

Action: Correct the namespace mapping in the configuration to ensure that the base restriction is specified only for the classpath store or servlet context store.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01348: unable to save configuration document to "{0}"

Cause: An I/O error occurred while writing the configuration to a file.

Action: Check the file system and ensure that the file location is writable.
Level: 1

Type: ERROR

Impact: Files

MDS-01349: unable to read existing configuration document "{0}" to be updated

Cause: An I/O or parsing error occurred while reading the configuration file.

Action: Ensure that the configuration file does exist and has valid contents.
Level: 1

Type: ERROR

Impact: Files

MDS-01350: Adding namespace "{0}" mapped to "{1}" conflicts with existing namespace "{2}" mapped to "{3}".

Cause: An attempt was made to add a new namespace that conflicted with an existing namespace because it mapped to a different repository.

Action: Ensure that the new namespace does not map to a different repository if the new namespace is a super-namespace or sub-namespace of existing namespaces.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01351: Adding namespace "{0}" with "{1}" restriction conflicts with existing namespace "{2}" with "{3}" restriction.

Cause: An attempt was made to add a new namespace that conflicted with an existing namespace in the namespace restriction.

Action: Ensure that the new namespace does not conflict with existing namespaces in the namespace restriction if the new namespace is a super-namespace or sub-namespace of existing namespaces.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01352: Customization configuration with granular mapping "{0}" is unsupported; only the slash, "/", is allowed.

Cause: An attempt was made to add an invalid namespace mapping of the customization configuration. Only one namespace to customization class list mapping is currently allowed, and that namespace has to be a slash (/).

Action: Ensure that only the slash (/) is specified in the namespace mapping of the customization configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01353: unable to retrieve customization layer values from "{0}"

Cause: An I/O or parsing error occurred while reading the specified file to retrieve customization layer values.

Action: Ensure that the file does exist and has valid contents.
Level: 1

Type: ERROR

Impact: Files

MDS-01355: Both TypeConfig parameters contain Grammar Providers. Only one Grammar Provider is allowed.

Cause: A Grammar Provider was specified in multiple type configuration sources.

Action: Ensure that only one Grammar Provider is specified in the type Configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01356: Both TypeConfig parameters contain Metadata Providers. Only one Metadata Provider is allowed.

Cause: A Metadata Provider was specified in multiple type configuration sources.

Action: Ensure that only one Metadata Provider is specified in the type Configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01357: MDS configuration is not compatible with JAXB 1.0.

Cause: JAXB 1.0 jar file (xml.jar) was found on the classpath before any JAXB 2.0 jar files.

Action: Ensure that JAXB 2.0 jar files appear on the classpath before JAXB 1.0 jar file (xml.jar).
Level: 1

Type: ERROR

Impact: Configuration

MDS-01358: Invalid MDS configuration. Configuring multiple metadata stores as the default repository for customizations.

Cause: Multiple metadata stores were configured as the default repository for customizations in the MDS configuration.

Action: Ensure that only a single metadata store is configured as the default repository for customizations.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01359: The namespace used (http://xmlns.oracle.com/mds/config_10_1_3_001) in the configuration document is deprecated. Update the configuration document to use "http://xmlns.oracle.com/mds/config" as the namespace.

Cause: The namespace used (http://xmlns.oracle.com/mds/config_10_1_3_001) in the configuration document is deprecated.

Action: Update the configuration document to use "http://xmlns.oracle.com/mds/config" as the namespace.
Level: 1

Type: WARNING

Impact: Configuration

MDS-01360: Invalid MDS configuration. The attribute file-type-extension on the file-type element is missing for file type configuration.

Cause: The attribute file-type-extension was not specified on the file-type element for file type configuration.

Action: Ensure that a valid file-type-extension attribute is specified for every file-type element.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01361: cannot add XSD grammar

Cause: An attempt was made to add XSD grammar made by passing in a SchemaGrammarProvider.

Action: Ensure that the grammar provider is obtained using oracle.jdeveloper.webapp.runtime.WebAppDesignContext.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01362: Failed to auto-purge MDS respository: "{0}".

Cause: MetadataStore was scheduled for auto-purge after the MDSInstance was released

Action: Try later and contact support if persists.
Level: 1

Type: WARNING

Impact: Other

MDS-01363: Failed to locate datasource with JNDI name "{0}" configured for the DBMetadataStore, defaulting to use ClassPathMetadataStore.

Cause: Application was configured with DBMetadataStore using JNDI datasource and JNDI lookup failed when running outside application server.

Action: No action required if defaulting to ClasspathMetadataStore is acceptable. Otherwise, use appropriate configuration such as FileMetadataStore.
Level: 1

Type: WARNING

Impact: Configuration

MDS-01365: Multiple metadata stores found with deploy-target attribute set to true, only one allowed per configuration.

Cause: Multiple metadata stores were configured as the deployment target.

Action: Ensure that only a single metadata store is configured for deployment.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01366: Cannot find a metadata store with deploy-target attribute set to true

Cause: A single metadata store must be configured as a deploy target. None was found.

Action: Ensure that a single metadata store is configured for deployment.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01367: Failed to create {0}. Invalid MDS configuration specified in: "{1}"

Cause: Declarative MDS configuration is invalid.

Action: Specify correct mds configuration information and try creating the configuration again.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01368: Variable "{0}" used in configuration document is not defined either as system property or as envrionment variable.

Cause: This variable was not defined.

Action: Ensure that this variable is defined before loading the configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01369: Variable declaration in "{0}" in configuration document is incorrect.

Cause: Variable did not either start with "${" or it did not end with "}".

Action: Ensure that the configuration variable is correctly declared in the form ${var}.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01370: MetadataStore configuration for metadata-store-usage "{0}" is invalid.

Cause: MetadataStore class or some of its properties were not valid.

Action: Ensure that the MetadataStore class exists and all required properties are valid. See message of the cause exception for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01371: ADF security is not configured in "{0}", password can not be securely processed.

Cause: ADF security configuration was not found in the config file.

Action: Set the password using JDeveloper to ensure required configuration is generated.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01373: unable to retrieve password.

Cause: unable to retrieve the password due to exception in security layer.

Action: See message of the cause exception for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01374: unable to save password.

Cause: unable to save the password due to exception in security layer.

Action: See message of the cause exception for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01375: No password defined for DBMetadataStore in configuration file or in the wallet file.

Cause: DBMetadataStore uses JDBC based configuration but no password specified.

Action: Set the password for the DBMetadataStore using JDeveloper.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01376: Unable to get database connection from data source "{1}" configured with JNDI name "{0}".

Cause: Failed to retrieve a database connection from the data source either because the data source is not configured correctly or the database details are not correct.

Action: Test the data source to check if it is correctly configured and if the database can be accessed. See message of the cause exception for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01377: Unable to get database connection from data source configured with JNDI name "{0}".

Cause: Failed to retrieve a database connection from the data source either because the data source is not configured correctly or the database details are not correct.

Action: Test the data source to check if it is correctly configured and if the database can be accessed. See message of the cause exception for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01378: metadata-store-usage attribute should not be set on namespace "{0}" defined in mds-config.xml.

Cause: metadata-store-usage attribute was set on the specified namespace in mds-component-config, but this namespace is always assumed to map to deploy-target metadata store.

Action: Ensure that the metadata-store-usage attribute is removed on specified namespace in mds-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01379: Tenant scope "{0}" is not valid for namespace "{1}" with namespace restriction "{2}".

Cause: Tenant scope configured for the namespace is not supported with the configured namespace restriction.

Action: Resolve the conflict between tenant scope and namespace-restriction in the application configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01380: Tenant scoped base metadata in package "{0}" can not have global customization layer "{1}".

Cause: Tenant scope GLOBAL on the specified customization layer conflicts with tenant scope TENANT on the base namespace.

Action: Resolve the conflicts between the tenant scope on the base namespace and that on the customization layer.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01381: Customization layer "{0}" has been configured more than once with the same tenant scope.

Cause: Duplicate configuration for the same customization layer was found.

Action: Remove the duplicate customization layer configuration from adf-config.xml of the application or component config (mds-config.xml) on classpath.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01382: Customization layer "{0}" has been configured more than once with conflicting tenant scopes.

Cause: Conflicting tenant scope configurations was found for the same customization layer.

Action: Remove the incorrect customization layer configuration from adf-config.xml of the application or component config (mds-config.xml) on classpath.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01383: Sandbox name should be provided for registering a sandbox change listener.

Cause: No sandbox name was provided for registering the sandbox change listener.

Action: Provide a valid sandbox name when registering the sandbox change listener.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01384: Sandbox change listener is not found when registering the lifecycle listener for sandbox {0}.

Cause: The SendboxChangeListener being registered was null.

Action: Provide a valid sandbox change listener when registering the lifecycle listener for the sandbox.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01385: Tenant scope "{0}" as base tenant scope is not valid for namespace "{1}".

Cause: The specified tenant scope type could not be configured as base tenant scope for the namespace.

Action: Use the correct base tenant scope parameter to create the namespace.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01386: Multitenant application can not be configured with metadata store "{0}" that does not support multitenancy.

Cause: A metadata store that does not support multitenancy was configured for a multitenant enabled application.

Action: Configure a metadata store such as DBMetadataStore that supports multitenancy.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01387: Tenant with id "{0}" is not allowed to change the autopurge settings; only the global admin can change this configuration.

Cause: A tenant cannot change the autopurge configuration..

Action: Only a global admin can change the autopurge configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01388: Unable to set cache size in Java Object Cache to {0} KiloBytes.

Cause: The cache size requested was invalid either becuase it was negative or it was too large for the Java Object Cache.

Action: Check that the specified size is >0 and within the limit of Java Object Cache for a Named Cache.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01389: ContentType can not be specified for Streamed documents.

Cause: Conflicting settings between ContentType and isStreamed were found in ContentConfig.

Action: Change ContentOptions to use either ContentType or isStreamed.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01390: An audit event name for component "{0}" is not specified.

Cause: An audit event was defined, but a name for the event was not specified.

Action: Give the audit event a valid name.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01391: "{0}" is not a valid audit event name.

Cause: An invalid audit event name was found. An audit event name should start with a letter and contain only letters and digits.

Action: Specify a valid name for the audit event.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01392: Conflicting definitions were found for the audit event with name "{0}" and audit-component "{1}".

Cause: Conflicting audit event definitions were found in audit-component element.

Action: Remove or modify one of the conflicting audit events.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01393: Multiple audit events named "{0}" are defined for component "{1}".

Cause: Duplicate audit events were found in audit-component element.

Action: Remove or modify one of the duplicate audit events.
Level: 1

Type: ERROR

Impact: Configuration

MDS-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-01800: Sandbox is not supported for {0} configured on {1}.

Cause: An underlying metadata store did not support the sandbox feature.

Action: Provide a metadata store that supports sandbox feature.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01801: Document name {0} should not refer to the raw sandbox resource name.

Cause: A resource name pointed directly to a resource in the sandbox component.

Action: Provide a logical document name to resolve the issue.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01802: A sandbox by name {0} already exists in the {1} store.

Cause: A sandbox with the same name already existed in the store.

Action: Use a different name or destroy the existing sandbox before reusing the same name.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01803: Sandbox Persistence manager cannot be constructed using an instance of SandboxPManager.

Cause: An attempt was made to construct an instance of sandbox persistence manager using an instance of SandboxPManager.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

MDS-01804: Sandbox {0} configured with {1} namespace, {2} store and {3} label from mainline is not compatible with {4} label created on {5} namespace.

Cause: A label was used that is different from the mainline label associated with the sandbox.

Action: Use a label that is compatible with the sandbox and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01805: Sandbox {0} missing in {1}.

Cause: The specified sandbox was not found in the underlying metadata store.

Action: Provide the name of an existing sandbox, or create a new sandbox if necessary.
Level: 1

Type: ERROR

Impact: Data

MDS-01806: failure to remove {0} from {1}, because it is not a valid document in the sandbox

Cause: The specified document to be removed was not found in the sandbox.

Action: Verify that the document exists in the sandbox.
Level: 1

Type: ERROR

Impact: Data

MDS-01807: failure to delete sandbox {0}

Cause: An error occurred while deleting the sandbox.

Action: Refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01808: SandboxUsage with the sandbox name set to {0} does not return any namespaces.

Cause: No namespaces were found on the SandboxUsage.

Action: Configure the SandboxUsage with namespaces that are associated with the sandbox.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01809: failure to list sandboxes matching {0}

Cause: An error occurred while listing or querying the sandboxes.

Action: Look for error messages to determine the actual cause of the failure.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01810: failure to refresh sandboxes to target label {0}

Cause: Target label is older than the current source label.

Action: Specify a target label which is later than current label.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01811: failure to list sandboxes matching customization for {0}, layer: {1}, value: {2}

Cause: An error occurred while listing or querying the sandboxes.

Action: Look for error messages to determine the actual cause of the failure.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01812: sandbox name {0} exceeds the maximum limit of {1} characters

Cause: Sandbox name is more than the supported size.

Action: Use a shorter sandbox name.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01813: sandbox metadata for {0} can not be saved because it is being updated by another user.

Cause: More than one user is updating the sandbox metadata at the same time.

Action: Get the sandbox metadata again and retry saving after making the changes.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01814: sandbox metadata for {0} cannot be changed because it is read only.

Cause: Sandbox metadata is read only and cannot be updated

Action: To update get an instance of sandbox and then get the sandbox metadata from the instance
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01815: store configured for sandbox {0} does not support sandbox metadata.

Cause: Sandbox metadata is not supported on the repository.

Action: Sandbox metadata is supported in MDS repository version 11.1.1.4.0 (11gR1 PS3 patchset) onwards. Upgrade the repository to this version or later to use this feature.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01816: {0} is not a valid name for a sandbox.

Cause: The specified sandbox name is either an MDS reserved package part name or contains invalid characters.

Action: Ensure that the specified sandbox name is neither an MDS reserved package part name nor does it contain invalid characters as per the MDS Resource name specification.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01817: sandbox {0} is either active or applied to mainline. The undo operation cannot continue.

Cause: The sandbox is either applied or is in the active state.

Action: Check that the sandbox is in the intermediary state
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01818: sandbox {0} is in applied_with_undo state. No further updates except finalized are allowed.

Cause: The sandbox is in applied_with_undo state and no further updates can be done to the sandbox.

Action: The only allowed operations in the intermediary state are: finalize and undo.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01819: Lock on sandbox {0} cannot be taken. A concurrent management operation may be in progress.

Cause: A management operation on the sandbox is in progress and has locked the sandbox.

Action: Retry the operation after a while.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01820: Metadata for sandbox {0} is not available. The sandbox management operation cannot proceed without sandbox metadata.

Cause: Sandbox was created without metadata.

Action: Use the management APIs that are available for sandboxes without metadata.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01821: Lifecycle change notifications for the sandbox {0} cannot be sent out because the change type is not defined.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

MDS-01900: None of the configured metadata stores support versioning.

Cause: The underlying metadata store did not support versioning.

Action: Configure a metadata store that supports versioning, and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01901: specifying multiple labels for a namespace not allowed

Cause: Multiple labels were provided for a namespace that pointed to a metadata store.

Action: Provide a single label to map to a namespace and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01902: Label or namespace is invalid.

Cause: Either the namespace or the label was invalid.

Action: Verify that the namespace and the label are correct, and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01903: Specified label {0} does not exist for {1} namespace.

Cause: The specified label did not exist in the metadata store mapped to the namespace.

Action: Verify that the label name is correct and that the label exists, and then retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01906: A label with same name {0} already exists.

Cause: An attempt was made to create a label that already existed.

Action: Create a label with a different name, and then retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01907: The label {1} is already configured for the store "{0}", so the same store cannot be configured with another label "{2}".

Cause: An attempt was made to map a label for a store when a label-to-store mapping already existed for that store.

Action: De-associate the existing label mapped to the store first, and then retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01908: failure to delete versions of the document {0}

Cause: An error had occurred while versions were being deleted.

Action: Refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01909: No namespaces are specified for creating label {0}.

Cause: No namespace information was found for creating a label.

Action: Provide a namespace for creating a label, and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01910: The namespace {0} is already registered with the label {1}, so the super/sub namespace {2} cannot be assigned with the label {3}.

Cause: An attempt was made to associate multiple labels with a namespace, or an attempt was made to associate multiple namespaces with a single label.

Action: Associate a single label with a single namespace, and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01911: failure of the metadata purge operation for the requested repository partition

Cause: An error occurred during a purge operation.

Action: Retry the operation. Also, refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01912: MetadataStore configured for {0} does not support versioning.

Cause: The metadata store configured for the resource did not support versioning.

Action: Configure a metadata store that supports versioning or verify that the resource name is correct.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01913: A deployment lineage with same application name "{0}" and deployment module name "{1}" already exists.

Cause: An attempt was made to create a lineage that already existed.

Action: Create a lineage with a different application or MAR name, and then retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01914: The application name and deployment module name cannot be null to create DeploymentInfo.

Cause: An attempt was made to create DeploymentInfo with null values.

Action: Make sure that the values for application name and deployment module name are non-null.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02024: Setting or modifying the unique identifier of an existing node through customizations is not supported.

Cause: An attempt was made to customize a configurable ID.

Action: Remove any customization that is attempting to modify the unique identifier of an XML element.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02025: The requested change is incompatible with changes already pending on the MDS session.

Cause: An attempt was made to perform a change operation on the MDS session which would update the same MetadataObject part as another change operation that has been done. For example, if you change a customization of a metadata object then attempt to delete all of its customizations, the latter operation will fail because it conflicts with the former. You must save the former change first before doing the second.

Action: Save the changes that have already been made on the session (by calling flushChanges), then retry the failed operation.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02100: Illegal permission target: "{0}" - must begin with {1}.

Cause: An attempt was made to create an MDS permission class with an incorrect syntax.

Action: Permission classes are usually created internally by MDS but may be created by the application directly. Contact the developers of the application to confirm that this is not an application error and if not contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

MDS-02101: Illegal permission action: "{0}" - unknown action.

Cause: An attempt was made to create an MDS permission class with an incorrect syntax.

Action: Permission classes are usually created internally by MDS but may be created by the application directly. Contact the developers of the application to confirm that this is not an application error and if not contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

MDS-02102: Illegal permission action: "{0}" - customize action takes 0 or 2 parameters.

Cause: An attempt was made to create an MDS permission class with an incorrect syntax.

Action: Permission classes are usually created internally by MDS but may be created by the application directly. Contact the developers of the application to confirm that this is not an application error and if not contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

MDS-02201: type validation failure for the metadata object "{0}"

Cause: The content of the metadata object was not valid against the registered XSDs.

Action: Ensure that the metadata object content is valid with respect to the registered XSDs.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02202: Content of the metadata object "{0}" is not valid.

Cause: The content was not valid either with respect to the registered XSDs or with the registered relationships.

Action: Check the content of the metadata object and correct the content as necessary to make it valid.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02203: type validation error for the metadata object "{0}" at the node "{1}"

Cause: A validation error occurred at the specified node.

Action: Check the content at the specified node for compliance with registered XSDs and relationships.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02204: type validation warning for the metadata object "{0}" at the node "{1}"

Cause: A validation warning occurred at the specified node.

Action: Check the content at the specified node for compliance with registered XSDs.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02301: The rename unit is invalid because either "{0}" or "{1}" is reused in the rename plan.

Cause: The resource name provided in the rename plan was used more than once.

Action: Provide distinct names for source and target names while renaming.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02302: subobjects "{1}" not found in metadata object "{0}"

Cause: The specified subobjects were not found in the metadata object.

Action: Look in the error message log for details.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02303: The given rename plan syntax is invalid

Cause: The rename plan syntax specified was invalid.

Action: Look in the error message log for details.
Level: 1

Type: ERROR

Impact: Configuration

MDS-02304: RenameOperation failed for StreamedObject "{0}" because subobjects were specified for this streamed object.

Cause: Streamed objects do not support subobjects.

Action: Remove the RenameObject that contains reference to the streamed object and subobject references from the RenamPlan.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02401: The operation {0} on the {1} node is not allowed.

Cause: An attempt was made to customize a node that was not customizable.

Action: If the attempted customization is valid, the customization restrictions need to be modified to provide this ability. The customization restrictions can be defined in: the XML schema definition, standalone XML file or an extended metadata file. Also check the customization policy for the MDS session in use and the customization configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-02402: The type definition for {1} does not allow customization of {0}.

Cause: An attempt was made to customize a node that was not customizable.

Action: If the attempted customization is valid, the customization restrictions need to be modified to provide this ability. The customization restrictions can be defined in: the XML schema definition, standalone XML file, tag library definition file, or an extended metadata file. Also check the customization policy for the MDS session in use and the customization configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-02404: The subelement {1} in the MDX document does not allow customization of {0}.

Cause: An attempt was made to customize a node that was not customizable.

Action: Check the customization restriction information which can be located in the schema definition, standalone xml file or an extended metadata file. Also check the customization policy for the MDSSession in use and the customization configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-02405: The attribute {2} in element {1} in the MDX document does not allow customization of {0}.

Cause: An attempt was made to customize a node that was not customizable.

Action: If the attempted customization is valid, the customization restrictions need to be modified to provide this ability. The customization restrictions can be defined in: the XML schema definition, standalone XML file or an extended metadata file. Also check the customization policy for the MDS session in use and the customization configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-02406: Customization of {0} is not allowed because it is not explicily allowed by any type definition nor any extended metadata entry.

Cause: An attempt was made to customize a node that was not customizable.

Action: If the attempted customization is valid, the customization restrictions need to be modified to provide this ability. The customization restrictions can be defined in: the XML schema definition, standalone XML file or an extended metadata file. Also check the customization policy for the MDS session in use and the customization configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-02407: Customization of {0} is not allowed because the local reference was not found in the document.

Cause: An enquiry about the customizability of a node supplied a local reference that wasn't found in the document.

Action: Ensure that the local reference applies to the document.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02408: The operation {0} on the {1} node is not allowed because the metadata object reference was not found in the change event.

Cause: A document change is not allowed because the metadata object reference was null.

Action: Ensure that the change document exists.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02500: Cannot find a valid MDSSession object for accessing the MDS document using ORAMDS URL

Cause: A valid MDSSession object was not set before accessing the document using the "oramds:///" protocol.

Action: Use the MDSURLHelper.setMDSSession() method to set a valid MDSSession object before accessing MDS documents using the oramds protocol.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02501: cannot load the ORAMDS URL "{0}" because MDS session could not be created or resolved

Cause: An error occurred while creating or resolving an MDS session object.

Action: Look for messages describing the cause exception in the error message log for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02600: configuration migration failure because the configuration document contains more than one mds-config element

Cause: The given configuration document contained more than one mds-config element.

Action: Correct the configuration document to contain a single mds-config element.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02601: configuration migration failure because it contains more than one persistence-config element

Cause: The configuration document contained more than one persistence-config element.

Action: Correct the configuration document to contain a valid persistence-config element.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02602: configuration migration failure because it contains more than one metadata-stores element

Cause: The configuration document contained more than one metadata-stores element

Action: Correct the configuration document to be a valid 10.1.3 configuration document.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02603: configuration migration failure because it contains an invalid metadata-store element

Cause: The configuration document contained an invalid metadata-store element.

Action: Correct the configuration document to be a valid 10.1.3 configuration document.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02700: The resource "{0}" cannot be updated by tenant "{1}".

Cause: The given resource could not be updated by the current tenant because it was not available in current tenant's scope.

Action: Verify that the resource is being updated in the same scope of the tenant who updates the resource.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02702: Tenant scoped PManager instance cannot be created for tenant {0} because given PManager instance does not have multitenancy enabled.

Cause: The PManager instance used here did not have multitenancy enabled but an attempt was made to create tenant scoped PManager instance.

Action: Verify that the PManager instance being passed has multitenancy support enabled.
Level: 1

Type: ERROR

Impact: Configuration

MDS-02703: Tenant scoped PManager cannot be created for tenant "null".

Cause: The PManager instance used here had multitenancy support enabled but an attempt was made to create tenant scoped PManager instance with "null" tenant.

Action: Create scoped PManager instance for valid tenant id.
Level: 1

Type: ERROR

Impact: Configuration

MDS-02704: Cannot create tenant scoped PManager instance using another tenant scoped PManager instance.

Cause: An attempt was made to create tenant scoped PManager using another scoped PManager instance.

Action: Create a tenant scoped PManager using an unscoped PManager instance.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02705: Cannot create PContext using an unscoped PManager instance.

Cause: Creating PContext using an unscoped PManager instance was not allowed.

Action: Use PManager instance that is scoped for a tenant to create PContext.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02706: Cannot create PTransaction using an unscoped PManager instance.

Cause: Creating PTransaction using an unscoped PManager instance was not allowed.

Action: Use PManager instance that is scoped for a tenant to create PTransaction.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02707: PContext with tenant id {0} cannot be used in scoped PManager with tenant id {1}.

Cause: Tenant id attached to PContext and the tenant id of tenant scoped PManager to which it was passed did not match.

Action: Create PContext from the tenant scoped PManager to which it is passed.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02708: PManager instance is being used after it has been released.

Cause: PManager instance was being used after it had been released.

Action: Create a new PManager.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02709: Configuration change operation "{0}" on scoped PManager is not allowed for the tenant {1}. Only global tenant is allowed to change the configuration settings in PManager.

Cause: A non global tenant attempted to change configurations in scoped PManager.

Action: Use global tenant scoped PManager to change the configuration settings.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02710: Operation "{0}" is not allowed in unscoped PManager.

Cause: A tenant aware operation was invoked in an unscoped PManager instance.

Action: Use a global or tenant scoped PManager to do the operation.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02711: No tenant operations are allowed on MetadataStoreConnection not associated with any tenant id.

Cause: A tenant aware operation was invoked in MetadataStoreConnection to database store which did not have any tenant id attached.

Action: Create a new MetadataStoreConnection with a valid tenant id.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02712: The operation {0} is not allowed in this MetadataStoreConnection to database store because the MetadataStoreConnection is not attached to any tenant id.

Cause: A tenant aware operation was invoked in MetadataStoreConnection to database store which did not have any tenant id attached.

Action: Create a new MetadataStoreConnection with a valid tenant id.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02713: PContext associated with tenant {0} cannot be used with MetadataStoreConnection associated with different tenant {1}. Operation {2} failure.

Cause: The tenant id attached to PContext and MetadataStoreConnection did not match.

Action: Use PContext with same tenant id as the one attached to metadata store connection.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02714: Creating metadata store connection for tenant {0} is not allowed in non multitenant application.

Cause: An attempt was made to create metadata store connection for non global tenant in non multitenant application.

Action: Use global tenant id to create metadata store connection.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02715: No tenant scoped PManager instances can be created on already released PManager instance.

Cause: An attempt was made to create a tenant scoped PManager instance on already released PManager instance.

Action: Create new PManager instance using a PConfig then try creating scoped PManager instance.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02716: PManager instance is created with multitenancy support.

Cause: PManager instance is created with multitenancy support.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

MDS-02717: PManager instance is created without multitenancy support as JVM flag "oracle.multitenant.enabled" is not set to enable multitenancy support.

Cause: PManager instance is created without multitenancy support becuase JVM flag to enable multitenancy support is not set.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

MDS-02718: PManager instance is created without multitenancy support becuase "isMultitenantCapable" property is not set in PConfig.

Cause: PManager instance is created without multitenancy support becuase isMultitenantCapable property is not set in PConfig..

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

MDS-02720: Cannot rename the document {0} to {1} as the new tenant scope does not match the original tenant scope.

Cause: The new name for the document was configured to a different tenant scope to the old document name.

Action: Provide a new valid document name that maps to the same tenant scope as the original document.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02721: PResource {0} for tenant {1} cannot be used with MetadataStoreConnection that is associated with different tenant {2}. Operation {3} failure.

Cause: The tenant ids of the PResource and the MetadataStoreConnection did not match.

Action: Use PResource with same tenant id of the one attached to metadata store connection.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02722: Mar Lineage can be created by global tenant only. Creating MAR lineage is not supported for tenant {0}.

Cause: A non-global tenant attempted to create MAR lineage which is not supported. MAR lineage creation is allowed only for global tenant currently.

Action: Create MAR lineage from global tenant context.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02723: Operation "{0}" is not supported in Sandbox currently.

Cause: Unsupported operation was invoked in Sandbox instance.

Action: This operation is not supported in Sandbox currently.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02724: The ResourceName that is attached to tenant scope {0} is not allowed in SandboxPTransaction that is attached to the different tenant scope {1}. Operation {2} failure.

Cause: Tenant scope for ResourceName and SandboxPTransaction did not match.

Action: Use ResourceName with same tenant scope of the one attached to SandboxPTransaction.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02725: The Label {0} that is attached to tenant {1} is not allowed in MetadataStoreConnection that is attached to different tenant {2}. Operation {3} failure.

Cause: Tenant id for Label and MetadataStoreConnection did not match.

Action: Use label with same tenant id of the one attached to MetadataStoreConnection.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02726: The tenant {0} that is attached to PDocument {1} is not allowed in SandboxPTransaction that is attached to different tenant {2}. Operation {3} failure.

Cause: Tenant id for PDocument and SandboxPTransaction did not match.

Action: Use PDocument with same tenant id of the one attached to SandboxTransaction.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02727: The tenant {0} that is attached to Label {1} is not allowed in SandboxPTransaction that is attached to different tenant {2}. Operation {3} failure.

Cause: Tenant id for Label and SandboxPTransaction did not match.

Action: Use label with same tenant id of the one attached to SandboxPTransaction.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02728: The tenant {0} that is attached to {1} {2} is not allowed in Sandbox that is attached to different tenant {3}. Operation {4} failure.

Cause: Tenant id attached and Sandbox did not match.

Action: Use tenant id same as the one attached to Sandbox.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02729: The tenant scope {0} that is attached to {1} is not allowed in Sandbox that is attached to the different tenant scope {2}. Operation {3} failure.

Cause: Tenant scope attached and Sandbox did not match.

Action: Use tenant scope same as the one attached to Sandbox.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02730: Error in deprovisioning the tenant {0}. Unable to delete the resources in {1}.

Cause: Tenant resources might be on read-only store.

Action: Verify that tenant resources exist on a writable store.
Level: 1

Type: ERROR

Impact: Configuration

MDS-02731: Tenant specific operations cannot be done in multitenant disabled environment for tenant {0}.

Cause: An attempt was made to do tenant specific operations in Multitenant disabled environment.

Action: Enable the multitenant feature.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02732: TenantId cannot be created for the value "{0}".

Cause: TenantId could not be created with negative values or a value with more than 18 digits.

Action: Use positive values with max of 18 digits in decimal format to create a valid TenantId object.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02733: Rename across multiple tenant stripes is not supported on this store.

Cause: The store does not support writing to multiple tenant stripes or multitenancy is not enabled.

Action: Enable the multitenant feature.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02800: The label "{0}" cannot be provided as null for label based transfer.

Cause: The label was provided as null for label based transfer.

Action: Provide valid label name for label based transfer.
Level: 1

Type: ERROR

Impact: Configuration

MDS-02801: Document {0} with scope {1} cannot be transferred by tenant {2}.

Cause: The given document could not be transferred from source store by current tenant because the document was not in the scope of current tenant.

Action: Ensure that document being transferred mapped to current tenant scope.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02802: Transfer is not supported for multitenant MDSInstance with file store.

Cause: Either source or target MDSInstance has multitenancy enabled and configured with file store.

Action: Use a non multitanant MDSInstance with file store.
Level: 1

Type: ERROR

Impact: Configuration

MDS-02803: List of patterns to select the MOs are either empty or null.

Cause: List of MOPatterns are empty or null.

Action: Ensure that valid list of MOPatterns are provided.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02804: Layer name "{0}" configured in CustLayerFilter to remove customizations, contains patterns.

Cause: Layer name contains patterns.

Action: Ensure that layer name doesn't contain any patterns.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-05786: Unable to deploy the metadata archive: {0}.

Cause: Metadata archive (MAR) is corrupt.

Action: Validate that the metadata archive (MAR) is valid and readable.
Level: 1

Type: ERROR

Impact: Configuration

MDS-05787: Partition name is not specified in adf-config.xml file.

Cause: A property with name partition-name was not found as a child of the metadata-store element.

Action: Specify the target partition as a child property of the metadata-store element in adf-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

MDS-05788: Unable to find the JNDI datasource in the file adf-config.xml.

Cause: A property with name jndi-datasource was not found as a child of the metadata-store element.

Action: Specify the JNDI datasource a child property of the metadata-store element in adf-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

MDS-05789: Unable to deploy the metadata archive.

Cause: Metadata archive (MAR) was not found.

Action: Ensure that the metadata archive (MAR) is packaged with the application.
Level: 1

Type: ERROR

Impact: Configuration

MDS-05790: The metadata store definition is either missing or incorrectly specified in the application configuration.

Cause: The metadata store definition is either missing or incorrectly configured in the file adf-config.xml.

Action: Ensure that the metadata store definition is present and contains the correct repository configuration
Level: 1

Type: ERROR

Impact: Configuration

MDS-05791: An error occurred during the deployment of the metadata archive (MAR) {0}.

Cause: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action.

Action: Ensure that the metadata store configuration is correct.
Level: 1

Type: ERROR

Impact: Configuration

MDS-05792: Unable to load MDS configuration from "{0}"

Cause: The MDS configuration is either not defined or incorrect.

Action: Ensure that the MDS configuration is correctly defined.
Level: 1

Type: ERROR

Impact: Configuration

MDS-05793: Metadata path {2} for partition {1} of MDS file repository {0} specified in adf-config.xml is either invalid or unreachable.

Cause: The metadata path named in the error message for the MDS file repository partition cited in the error message was either invalid or unreachable.

Action: Ensure that the MDS file repository named in the error message is registered and that the metadata partition cited in the error message is configured with a valid metadata path in adf-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

MDS-05794: Unable to load MDS persistence configuration from "{0}"

Cause: The MDS persistence configuration is either not defined or incorrect.

Action: Ensure that the MDS persistence configuration is correctly defined.
Level: 1

Type: ERROR

Impact: Configuration

MDS-05795: Invalid value "{0}" specified in the content-config of the application's configuration

Cause: Only restriction type CUSTOMIZATIONS is supported in content-config. It is only allowed with path "/" and no file extension.

Action: Ensure that the MDS persistence configuration is correctly defined.
Level: 1

Type: ERROR

Impact: Configuration

MDS-10001: Error:

Cause: An error occured. Details are usually given in the accompanying messages.

Action: Look for messages describing the cause and take the appropriate action.
Level: 1

Type: ERROR

Impact: Data

MDS-10003: The specified {0} argument is null or empty.

Cause: A required program argument was null or empty.

Action: Record any accompanying exception messages and contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

MDS-10009: The transfer of the document {0} is not successful.

Cause: Document transfer failed

Action: Examine any accompanying messages to decide if further action is required.
Level: 1

Type: WARNING

Impact: Data

MDS-10010: Deleting the document {0} is not successful.

Cause: Document deletion failed

Action: Examine any accompanying messages to decide if further action is required.
Level: 1

Type: WARNING

Impact: Data

MDS-10011: The operation on {0} has been rolled back. Total number of documents failed during the operation is {1}.

Cause: The transfer was rolled back

Action: Examine any accompanying messages to decide if further action is required.
Level: 1

Type: WARNING

Impact: Data

MDS-10012: The operation has failed.

Cause: The operation has failed.

Action: Examine any accompanying messages to decide if further action is required.
Level: 1

Type: WARNING

Impact: Data

MDS-10013: {0} operation started.

Cause: Transfer started.

Action: Transfer started, no action required.
Level: 1

Type: NOTIFICATION

Impact: Data

MDS-10014: {0} is completed. Total number of documents successfully processed : {1}, total number of documents failed : {2}.

Cause: Transfer complete.

Action: Check any accompanying messages to decide if any action is required.
Level: 1

Type: NOTIFICATION

Impact: Data

MDS-10015: Failure occurred while committing the {0} operation. The operation has been rolled back.

Cause: Failure occurred while committing the operation.

Action: Examine any accompanying messages to decide if further action is required.
Level: 1

Type: ERROR

Impact: Data

MDS-10016: The operation on {0} has been rolled back. The post transfer label {1} could not be created.

Cause: Failure occurred when creating the post transfer label.

Action: Examine any accompanying messages to decide if further action is required.
Level: 1

Type: ERROR

Impact: Data

MDS-10017: The target store does not support deployment management. Given application name "{0}" and deployment module name "{1}" could not be persisted as deployment information in store.

Cause: The target store does not support deployment management.

Action: No action required. The documents will be transferred without the deployment information attached. If you want to store deployment information as well, configure a metadata store that supports deployment management, typically a DB store.
Level: 1

Type: WARNING

Impact: Data

MDS-10018: The transfer restriction {0} is not supported in target store. All the documents will be transferred to target store.

Cause: Given transfer restriction is not supported in target store.

Action: No action required. The given restriction will not be applied to the transfer, all the documents will be transferred to target store.
Level: 1

Type: WARNING

Impact: Data

MDS-10019: The deployment information for application name "{0}" and module name "{1}" ignored since transfer operation is of type "{2}".

Cause: The deployment information will not be processed in transfer operation type other than "Deployment".

Action: No action required. Given deployment information will not be processed in the current transfer operation.
Level: 1

Type: WARNING

Impact: Data

MDS-10020: Querying checksum data from target repository to avoid transferring unchanged documents.

Cause: To apply transfer restriction CHANGED, transfer queries the target repository to check whether documents being transferred already exist with same content.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Data

MDS-10022: Query to get the checksum of the documents from target repository completed successfully.

Cause: To apply transfer restriction CHANGED, transfer queries the target repository to check whether documents being transferred already exist with same content.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Data

MDS-10023: No valid exclusion rules are specified in mds-transfer-config.xml to preserve documents in target store.

Cause: No valid namespaces or metadata object names specified in /meta-inf/mds-transfer-config.xml to preserve the documents in target store.

Action: No action required.
Level: 1

Type: WARNING

Impact: Data

MDS-10024: Preparing the list of documents to be excluded during transfer as per the configuration given in mds-transfer-config.xml.

Cause: To preserve the documents in target store as specified in the given /meta-inf/mds-transfer-config.xml, MDSTransfer prepares the list of documents to be excluded by looking at source and target stores.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Data

MDS-10025: Following metadata paths are configured in mds-transfer-config.xml to preserve existing documents under this metadata path in target repository. Configured metadata paths are as follows {0}:

Cause: Some metadata paths are configured in mds-transfer-config.xml to preserve existing documents in target repository.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Other

MDS-10026: Following Metadata object names are configured in mds-transfer-config.xml to preserve existing metadata objects with same name in target repository. Configured metadata object names are {0}:

Cause: Some metadata object names are configured in mds-transfer-config.xml to preserve existing documents in target repository.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Other

MDS-10027: To preserve documents in target store, the following documents from source store are marked as excluded by transfer {0}.

Cause: To preserve documents in target store, some documents from source store are marked as excluded by transfer.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Other

MDS-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-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-11026: Ignoring the duplicate MDS component configuration file URL "{0}" found on the classpath.

Cause: A duplicate URL for an MDS component configuration file was found on the classpath.

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

MDS-11027: Some metadata is configured to be stored as xml-stream. However it will be ignored because no metadata store configured for this application supports storing metadata in that form.

Cause: xml-stream content type was configured for some metadata content, but no metadataStore supports the feature.

Action: No action required if not using xml-stream content type is acceptable. Otherwise, to enhance MDS repository performance, ensure that the metadata store supports xml-stream feature.
Level: 1

Type: WARNING

Impact: Configuration

MDS-11028: Some metadata is configured to be stored as xml-stream. However it will be ignored because the corresponding metadata store, with class name: {0}, repository name: {1}, partition name: {2}, does not support storing metadata in that form.

Cause: xml-stream content type was configured for some metadata content, but the metadata store did not support the feature.

Action: No action required if not using xml-stream content type is acceptable. Otherwise, to enhance MDS repository performance, ensure that the metadata store supports xml-stream feature.
Level: 1

Type: WARNING

Impact: Configuration

MDS-11029: MetadataStore configuration for metadata-store-usage "{0}" is invalid. However the MetadataStore is ignored because it is not referenced by any namespace mapping.

Cause: MetadataStore class or some of its properties were not valid.

Action: Ensure that the MetadataStore class exists and all required properties are valid.
Level: 1

Type: NOTIFICATION

Impact: Configuration

MDS-11030: Registered grammar using remote schema "{0}". In design time environment, it is recommended to use local resources.

Cause: Remote schema has been referred with http URI. In design time environment, recommendation is to use local resources.

Action: Replace it with local copy of schema.
Level: 1

Type: WARNING

Impact: Configuration

MDS-11100: MetadataObject.getBaseMO() found a mismatched CacheAccess in the cache. [refNoGUID={0}, guidRef={1}, mdxLookupKey={2}, isLabelledRead={3}, baseDocLabel={4}, setSandboxName={5}, cacheAccess={6}, doc={7}, name={8}, GUID={9}].

Cause: CacheAcces does not match the the given MOReference/Guid combination. The metadata object will not be cached.

Action: Check the MOName and guid are correct and there are no duplicate Guids in the metadata store.
Level: 1

Type: WARNING

Impact: Other

MDS-11101: MetadataObject.getBaseMO() recursing too deep. [refNoGUID={0}, guidRef={1}, mdxLookupKey={2}, isLabelledRead={3}, baseDocLabel={4}, setSandboxName={5}, cacheAccess={6}, doc={7}].

Cause: CacheAcces does not match the the given MOReference/Guid combination. The metadata object will not be cached.

Action: Check the data in the metadata store to determine the cause.
Level: 1

Type: WARNING

Impact: Other

MDS-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}" aleady 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, IBMDB2, or MYSQL. "{0}" operation failure.

Cause: dbVendor value was not correct.

Action: Ensure the dbVendor value is one of ORACLE, MSSQL, IBMDB2, or MYSQL.
Level: 1

Type: ERROR

Impact: Data

MDS-91008: The "{0}" parameter is required. Provide a valid value and retry the operation.

Cause: Required parameter for the command was not given.

Action: Provide the required parameters for the command.
Level: 1

Type: ERROR

Impact: Data

MDS-91009: Operation "{0}" failure.

Cause: Exception occurred during the execution of the command.

Action: Provide the required parameters for the command.
Level: 1

Type: ERROR

Impact: Data

MDS-91010: The "adf-config" element is not available in the given archive file. "{0}" operation failure.

Cause: The "adf-config" element is not available in the given archive file.

Action: Ensure the "adf-config" element is available in the adf-config.xml of the given archive file.
Level: 1

Type: ERROR

Impact: Configuration

MDS-91011: No "mds-config" element exists in the adf-config.xml of the given archive. "{0}" operation failure.

Cause: No mds-config element existed in the adf-config.xml file of the archive file.

Action: Ensure the "mds-config" element is available in the adf-config.xml file.
Level: 1

Type: ERROR

Impact: Configuration

MDS-91012: Metadata repository connection type value should be either "File" or "DB". "{0}" operation failure.

Cause: Metadata repository connection type value is not correct.

Action: Ensure the metadata repository connection type value is either 'File' or 'DB'.
Level: 1

Type: ERROR

Impact: Data

MDS-91013: For the metadata repository''s DB connection type, JNDI location is a required parameter. "{0}" operation failure.

Cause: JNDI location not provided for DB connection type.

Action: Provide the JNDI location string while updating the repository connection to DB.
Level: 1

Type: ERROR

Impact: Data

MDS-91014: For the metadata repository''s File connection type, path location is a required parameter. "{0}" operation failure.

Cause: The path value was not provided for File connection type.

Action: Provide the path location string while updating the repository connection to File.
Level: 1

Type: ERROR

Impact: Data

MDS-91015: All parameters are required to update shared metadata repository configuration in adf-config.xml. At present, source archive has no connection details for the namespace "{0}". "{1}" operation failure.

Cause: Complete connection information was not provided to set the shared repository for the given namespace.

Action: Provide complete connection information in case the adf-config.xml file does not have any metadata repository connection information for the given namespace already.
Level: 1

Type: ERROR

Impact: Data

MDS-91016: All parameters are required to define new application metadata repository configuration in adf-config.xml. The source archive configuration does not contain any application metadata repository at present. "{0}" operation failure.

Cause: Complete connection information was not provided to set the application target repository.

Action: Provide complete connection information in case the adf-config.xml does not have any metadata repository connection information for the application target repository already.
Level: 1

Type: ERROR

Impact: Data

MDS-91017: The given namespace "{0}" to set the shared repository is not valid. Ensure that the namespace is available in the adf-config.xml file and it is not a sub-namespace of any other namespace. "{1}" operation failure.

Cause: The namespace provided to set the shared repository details is not valid.

Action: Ensure that the namespace is available in the adf-config.xml file and it is not a subnamespace of any other namespace in that file.
Level: 1

Type: ERROR

Impact: Data

MDS-91018: No namespaces are mapped to any shared repository in the source archive adf-config.xml configuration file. Shared repository details cannot be set. "{0}" operation failure.

Cause: No namespaces were mapped to any shared repository in the source archive adf-config.xml configuration file.

Action: To set the shared repository connections, ensure at least one namespace is mapped to shared repository in the source archive adf-config.xml file.
Level: 1

Type: ERROR

Impact: Configuration

MDS-91019: Multiple MDSAppRuntimeMBean exist for application "{0}". Ensure that the "application" "node" and "server" parameters are correct. "{1}" operation failure.

Cause: Multiple MDSAppRuntimeMBean for the application were found in the server.

Action: Ensure that the "application" "node" and "server" parameters are correct.
Level: 1

Type: ERROR

Impact: Configuration

MDS-91020: MDS Application runtime MBean for "{0}" is not available in server "{2}". Ensure server name and application name are correct. "{1}" operation failure.

Cause: MDS Application runtime MBean was not available in the server.

Action: Ensure the MDS Application runtime MBean for the application is available in the server. Ensure the server name and the application name are correct.
Level: 1

Type: ERROR

Impact: Configuration

MDS-91021: Multiple MDSAppRuntimeMBean exist for "{0}" in server "{2}". To execute the command, parameter "applicationVersion" is required. "{1}" operation failure.

Cause: Multiple MDSAppRuntimeMBean for the application were found in the server.

Action: Provide the 'applicationVersion' parameter.
Level: 1

Type: ERROR

Impact: Configuration

MDS-91022: Parameter "{0}" cannot be an empty string. "{1}" operation failure.

Cause: The parameter is not allowed to be an empty string.

Action: Ensure the parameter has a correct value.
Level: 1

Type: ERROR

Impact: Data

MDS-91023: Parameter "{0}" contains at least one empty element. "{1}" operation failure.

Cause: The parameter is not allowed to contain one or more empty elements.

Action: Ensure every element specified in the parameter is correct.
Level: 1

Type: ERROR

Impact: Data

58 MODPLSQL-00001 to MODPLSQL-00868

MODPLSQL-00001: mod_plsql: Out of memory

Cause: System has run out of memory

Action: Reduce memory usage in the system
Level: 1

Type: ERROR

Impact: Runtime

MODPLSQL-00010: mod_plsql: Out of memory

Cause: System has run out of memory

Action: Reduce memory usage in the system
Level: 1

Type: ERROR

Impact: Runtime

MODPLSQL-00102: mod_plsql: Wrong language, territory or charset in NLS_LANG value

Cause: Incorrect NLS_LANG value specified

Action: Refer to RDBMS and NLS documentation for the acceptable NLS_LANG value
Level: 1

Type: ALERT

Impact: Configuration

MODPLSQL-00350: mod_plsql: Bad Procedure/Argument name in the request

Cause: The procedure name and/or the argument is not a legal PL/SQL identifier

Action: Correct the procedure name and the arguments to be legal PL/SQL identifiers
Level: 1

Type: ERROR

Impact: Runtime

MODPLSQL-00367: mod_plsql: Illegal PLSQL identifer in input

Cause: The procedure name and/or the argument is not a legal PL/SQL identifier

Action: Correct the procedure name and the arguments to be legal PL/SQL identifiers
Level: 1

Type: ERROR

Impact: Runtime

MODPLSQL-00368: mod_plsql: No target procedure specified for invocation

Cause: The procedure name to invoke is not specified in the URL

Action: Specify a legal PL/SQL procedure to invoke
Level: 1

Type: ERROR

Impact: Runtime

MODPLSQL-00369: mod_plsql: Illegal procedure name, part exceeds 32 bytes

Cause: The procedure name specified exceeds the legal PLSQL identifier length

Action: Correct the procedure name to be a legal PL/SQL identifier
Level: 1

Type: ERROR

Impact: Runtime

MODPLSQL-00370: mod_plsql: Illegal procedure name, has an empty part

Cause: The procedure name is not a legal PLSQL identifier

Action: Correct the procedure name to be a legal PL/SQL identifier
Level: 1

Type: ERROR

Impact: Runtime

MODPLSQL-00371: mod_plsql: Illegal procedure name, too many parts

Cause: The procedure name is not a legal PLSQL identifier

Action: Correct the procedure name to be a legal PL/SQL identifier
Level: 1

Type: ERROR

Impact: Runtime

MODPLSQL-00868: mod_plsql: Failed to validate configuration parameters

Cause: Illegal configuration property specified in the mod_plsql configuration

Action: Refer to the logs for more details, and correct the offending configuration property
Level: 1

Type: ERROR

Impact: Configuration

59 OAAM-00000 to OAAM-94100

OAAM-00000: Invalid message.

Cause: Unable to find message definition.

Action: Report to administrator.
Level: 1

Type: ERROR

Impact: Process

OAAM-00001: A system internal error occurred. The system cannot complete the operation at this time.

Cause: A system internal error occurred. The error may be the result of a constraint or the unavailability of resources.

Action: Try again. If the problem remains unresolved, you may contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

OAAM-00002: The operation is not allowed.

Cause: The user may not have sufficient privileges.

Action: Report to the administrator about insufficient privileges.
Level: 1

Type: ERROR

Impact: Process

OAAM-00003: Database error.

Cause: The database may not be available.

Action: Try again. If the problem remains unresolved, you may contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

OAAM-00004: Insufficient context data. Required: {0}.

Cause: The expected context information is not provided.

Action: Report to the administrator about the insufficient context data.
Level: 1

Type: ERROR

Impact: Process

OAAM-00005: Database error. Exception message is {0}.

Cause: The error may have resulted from the unavailability of the database or a database querying exception.

Action: Report the database error message to the administrator.
Level: 1

Type: ERROR

Impact: Process

OAAM-01001: Property name is required.

Cause: The property name is missing from the data.

Action: Make sure that the property name is provided for the operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-01002: Property value is required.

Cause: The property value is missing from the data.

Action: Make sure the property value is provided for the operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-01003: Property with name {0} already exists.

Cause: The property with the name already exists.

Action: Use a different property name and try again.
Level: 1

Type: ERROR

Impact: Process

OAAM-01004: Property with name {0} does not exist.

Cause: The property with the name was not found in the system.

Action: Make sure the property name provided is correct and then retry the operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-01005: Property search query is required to search properties.

Cause: The property search query was not provided for the search.

Action: Make sure that the valid property search query is provided.
Level: 1

Type: ERROR

Impact: Process

OAAM-01006: Cannot delete property {0} because it is a {1} type of property.

Cause: Property cannot be deleted. System- and file-based properties cannot be deleted. Only properties saved in the database can be deleted.

Action: System-based properties cannot be deleted. Only properties saved in the database and files can be deleted.
Level: 1

Type: ERROR

Impact: Process

OAAM-01007: Cannot modify property {0} because it is a {1} type of property.

Cause: Property cannot be changed. System-based properties cannot be changed. Only properties saved in the database and files can be changed.

Action: System-based properties cannot be changed. Only properties saved in the database and files can be changed.
Level: 1

Type: ERROR

Impact: Process

OAAM-01101: Object type was not specified for finding usage.

Cause: The required object type was not specified for finding usage.

Action: The object type must be specified to find the usage information. Specify non-null integer value and retry this operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-01102: Object unique key was not specified for finding usage.

Cause: The required object unique key (primary key) was not specified for finding usage.

Action: The object unique (primary) key must be specified to find the usage. Specify a non-null long value and retry this operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-01103: Usage cannot be computed for object type {0}.

Cause: Usage API supports certain types of objects. The specified object is not specified by the Usage API.

Action: Specify the object type, which can be referenced by other objects in the system.
Level: 1

Type: ERROR

Impact: Process

OAAM-01104: Usage information for the primary object of type {0} with a unique ID of {1} cannot be determined.

Cause: Usage API is trying to find the usage of an object that does not exist.

Action: A unique ID of the object was provided, which was not found in the system. Make sure that the unique ID and the object are correct and retry this operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-10000: Valid Case ID is required.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Process

OAAM-10001: Case {0} not found

Cause:

Action:
Level: 1

Type: ERROR

Impact: Process

OAAM-10002: No user {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Process

OAAM-10004: User is blocked

Cause:

Action:
Level: 1

Type: ERROR

Impact: Process

OAAM-10005: No questions registered {0} {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Process

OAAM-10006: Invalid application {0} and login {1} combination.

Cause: Combination may be incorrect or user name is used in place of the login name.

Action: Report to administrator.
Level: 1

Type: ERROR

Impact: Process

OAAM-10007: Challenge questions are already reset.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Process

OAAM-10008: Challenge Question Set is already reset.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Process

OAAM-10009: End Date is required.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Process

OAAM-10010: End Date should be in future.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Process

OAAM-10011: Valid Application name or user group name is required.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Process

OAAM-10301: Note cannot be null or empty.

Cause: Note cannot be null or empty string.

Action: Provide a valid note.
Level: 1

Type: ERROR

Impact: Process

OAAM-10302: Closed case {0} cannot be escalated.

Cause: Closed case {0} cannot be escalated.

Action: Reopen the closed case before trying to escalate it.
Level: 1

Type: ERROR

Impact: Process

OAAM-10303: The Case {0} is not a CSR case; therefore, it cannot be escalated.

Cause: The Case {0} is not a CSR case; therefore, it cannot be escalated.

Action: The case type for case {0} should be changed to CSR for escalation.
Level: 1

Type: ERROR

Impact: Process

OAAM-10304: Query cannot be null.

Cause: Query cannot be null.

Action: Provide a valid query object.
Level: 1

Type: ERROR

Impact: Process

OAAM-10305: No query expression found.

Cause: No query expression found.

Action: Provide the required parameters for the query expression.
Level: 1

Type: ERROR

Impact: Process

OAAM-10306: No records found.

Cause: No records found.

Action: Change the criteria before performing the operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-10307: No linked sessions found.

Cause: No linked sessions found.

Action: For the given case, no linked sessions were found.
Level: 1

Type: ERROR

Impact: Process

OAAM-10308: No sessions to link.

Cause: No sessions to link.

Action: Provide sessions to link.
Level: 1

Type: ERROR

Impact: Process

OAAM-10309: No sessions to unlink.

Cause: No sessions to unlink.

Action: Provide sessions to unlink.
Level: 1

Type: ERROR

Impact: Process

OAAM-11111: User not authorized to access the method {0}.

Cause: User is not authorized to access the method {0}.

Action: Retry accessing the method {0} with valid authorization.
Level: 1

Type: ERROR

Impact: Process

OAAM-11112: Session ID of Admin users is required for case action.

Cause: Session ID was not provided for performing the case action.

Action: Retry the same case action and provide the valid Admin user Session ID for that API call.
Level: 1

Type: ERROR

Impact: Process

OAAM-11113: Choose the action template for creating action instance.

Cause: Action template was not provided for performing the action instance creation.

Action: Retry the same action instance creation by choosing valid action template.
Level: 1

Type: ERROR

Impact: Process

OAAM-11114: Subaction ID is required for case action.

Cause: Subaction was not provided for performing the case action.

Action: Retry the same case action and provide the valid Subaction ID for that API call. The Subaction ID is the case action enumeration.
Level: 1

Type: ERROR

Impact: Process

OAAM-11115: New status required for case change status action.

Cause: New status was not provided for performing the change status case action.

Action: Retry the same case action and provide the valid new status (Integer object) for that API call. New status is the case status enumeration.
Level: 1

Type: ERROR

Impact: Process

OAAM-11116: Reopen the closed case before trying to edit: Case ID {0}

Cause: The case is in the Closed state. In this state, the case disposition or expiration cannot change.

Action: The case is closed. In the Closed state, the disposition, severity, or expiration cannot be changed. To change these attributes, change the status of the case along with new severity, expiration time, or disposition
Level: 1

Type: ERROR

Impact: Process

OAAM-11117: Case with ID {0} is expired. It cannot be edited.

Cause: The case is in the Expired state. In this state, the case disposition or expiration date cannot be changed.

Action: The case is expired, and in the Expired state, its disposition, severity, or expiration cannot be changed. Reopen the case first and then try this operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-11120: Case reset action cannot be completed because: {0}.

Cause: Case reset action cannot be performed because of the reason provided by the error message.

Action: Retry the same case action after fixing the issue.
Level: 1

Type: ERROR

Impact: Process

OAAM-11121: Challenge question-related case action cannot be performed because: {0}.

Cause: Challenge question-related case action cannot be performed because of the reason provided by the error message.

Action: Retry the same case action after fixing the issue.
Level: 1

Type: ERROR

Impact: Process

OAAM-11122: The customer's registration profile is not active and hence cannot be reset.

Cause: The customer's registration profile have already been reset.

Action: Cannot reset customer's registration profile since they are not active.
Level: 1

Type: ERROR

Impact: Process

OAAM-11123: Cannot reset user's image, as it is not set.

Cause: User does not have the image set.

Action: Cannot reset the user's image because the user is not registered or the image is not active for the user.
Level: 1

Type: ERROR

Impact: Process

OAAM-11124: Cannot reset the user's phrase, as it is not set.

Cause: The user does not have a phrase set.

Action: Cannot reset the user's phrase because either the user is not registered or the phrase is not active for the user.
Level: 1

Type: ERROR

Impact: Process

OAAM-11125: OTP reset action cannot be performed with cases that are not CSR cases.

Cause: For OTP reset actions that are performed with cases, the case has to be a CSR case. OTP reset cannot be performed with a case of any other type.

Action: Create a CSR case for the user and then try to do the OTP-related resets.
Level: 1

Type: ERROR

Impact: Process

OAAM-11126: OTP reset action cannot be performed with case in an incorrect state.

Cause: For OTP reset actions that are performed with cases, the case has to be in the correct state. An OTP reset cannot be performed with a case in the Closed, Escalated, or Expired state.

Action: Change the state of the case to Open, New, or Pending and then retry the operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-11127: OTP reset profile attempted for user who does not have OTP profile enabled.

Cause: The user's OTP profile is not enabled. For such users, the OTP profile reset cannot be performed.

Action: Make changes to the user's preferences to register the OTP profile and then try this operation again.
Level: 1

Type: ERROR

Impact: Process

OAAM-11129: OTP reset keypad attempted for user who does not have OTP keypad enabled.

Cause: The user's OTP keypad is not enabled. For such users, the OTP keypad reset cannot be performed.

Action: Make the changes to the users preferences to register the OTP keypad and then try this operation again.
Level: 1

Type: ERROR

Impact: Process

OAAM-11130: Authentication pad is already reset.

Cause: Authentication pad is already reset.

Action: No action required to reset.
Level: 1

Type: ERROR

Impact: Process

OAAM-11131: OTP failure counter for user is already in reset state. It may be possible that the user does not OTP enabled.

Cause: The user's OTP failure counter is already at zero. It is already in reset state. For such users, an OTP failure counter reset cannot be performed.

Action: Make sure that the user is registered for OTP and that the OTP failure counter is not at zero.
Level: 1

Type: ERROR

Impact: Process

OAAM-11132: OTP reset cannot be performed at this time because of an error. Try the reset again.

Cause: The OTP reset operation experienced a system error. Try the operation again.

Action: The OTP reset encountered an error. Make sure the user is registered for OTP and try the operation again.
Level: 1

Type: ERROR

Impact: Process

OAAM-11133: Access to link specified sessions to case is denied.

Cause: Attempt was made to link the sessions of some users for which the agent does not have access.

Action: Add the administrative user to the user group in the security set up for the OAAM administrative application.
Level: 1

Type: ERROR

Impact: Process

OAAM-11134: User does not access to create a case for user belonging to user group {0}.

Cause: Attempt was made to create a case for user belonging to the user group for which the administrative user does not have access.

Action: Add the administrative user to the user group in the security set up for the OAAM administrative application.
Level: 1

Type: ERROR

Impact: Process

OAAM-15001: Enter Organization ID and User name, or only User ID.

Cause: A combination of Organization ID and User name or User ID are allowed.

Action: Enter Organization ID and User name, or User ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-15002: Organization ID is required.

Cause: Organization ID is not entered.

Action: Enter Organization ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-15100: An attempt was made to change the status of expired cases. Select an extension duration to continue.

Cause: The status of expired cases cannot be changed.

Action: Select an extension duration so that the cases are no longer expired. Then, change the status.
Level: 1

Type: ERROR

Impact: Process

OAAM-15101: An attempt was made to extend the expiration of a closed case. Select a status other than close to continue.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Process

OAAM-20000: Policy name cannot be null or empty.

Cause: Policy name cannot be null or empty.

Action: Provide a valid policy name.
Level: 1

Type: ERROR

Impact: Process

OAAM-20001: Policy weight must be between {0} and {1}.

Cause: Policy weight must be between {0} and {1}.

Action: Ensure that the policy weight is between {0} and {1}.
Level: 1

Type: ERROR

Impact: Process

OAAM-20002: Policy description cannot be null or empty.

Cause: Policy description cannot be null or empty.

Action: Provide a valid policy description.
Level: 1

Type: ERROR

Impact: Process

OAAM-20003: A policy with name {0} already exists.

Cause: A policy with name {0} already exists.

Action: A policy with name {0} exists. Use a different name.
Level: 1

Type: ERROR

Impact: Process

OAAM-20004: Policy ID cannot be null.

Cause: Policy ID cannot be null.

Action: Provide a non-null Policy ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-20005: Policy with Policy ID {0} does not exist.

Cause: Policy with Policy ID {0} does not exist.

Action: Provide a valid Policy ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-20009: Rule ID cannot be null.

Cause: Rule ID cannot be null.

Action: Provide a non-null Rule ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-20010: Rule with the given ID not found.

Cause: Rule with the given ID not found.

Action: Provide a valid Rule ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-20011: Profile rule map for the given Map ID not found.

Cause: Profile rule map for the given Map ID not found.

Action: Provide a valid profile rule Map ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-20012: Profile for the given Map ID not found.

Cause: Profile for the given Map ID not found.

Action: Provide a valid Map ID with profile.
Level: 1

Type: ERROR

Impact: Process

OAAM-20013: Profile Rule Map ID cannot be null.

Cause: Profile Rule Map ID cannot be null.

Action: Provide a non-null Profile Rule Map ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-20014: Rule Condition Map ID cannot be null.

Cause: Rule Condition Map ID cannot be null.

Action: Provide a non-null Rule Condition Map ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-20015: Rule parameter value not found.

Cause: Rule parameter value not found.

Action: Provide a valid Map ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-20016: Rule parameter not found.

Cause: Rule parameter not found.

Action: Provide a valid Map ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-20017: The following policies depend on some of the policies being deleted: {0}.

Cause: The following policies depend on some of the policies being deleted: {0}.

Action: Remove the dependency. The policies cannot be deleted until the dependency is removed.
Level: 1

Type: ERROR

Impact: Process

OAAM-20018: Rule parameter value was not found for the given rule parameter. The rule may not work as expected unless the error is fixed.

Cause: Rule parameter value was not found for the given rule parameter.

Action: When a rule is added to a policy, the value of each rule parameters is kept. The system was not able to find a corresponding value for the rule parameter in the policy data. Verify the rule and its details. Make sure the migration had no errors if this rule had been migrated from the previous release.
Level: 1

Type: ERROR

Impact: Process

OAAM-20019: Rule name cannot be null.

Cause: Rule name cannot be null.

Action: Provide a valid rule name.
Level: 1

Type: ERROR

Impact: Process

OAAM-20020: Rule description cannot be null.

Cause: Rule description cannot be null.

Action: Provide a valid rule description.
Level: 1

Type: ERROR

Impact: Process

OAAM-20021: Rule score must be between {0} and {1}.

Cause: Rule score must be between {0} and {1}.

Action: Provide a rule score value between {0} and {1}.
Level: 1

Type: ERROR

Impact: Process

OAAM-20022: Rule weight must be between {0} and {1}.

Cause: Rule weight must be between {0} and {1}.

Action: Provide a rule weight between {0} and {1}.
Level: 1

Type: ERROR

Impact: Process

OAAM-20023: Minimum device score must be between {0} and {1}.

Cause: The minimum device score must be between {0} and {1}.

Action: Provide a minimum device score between {0} and {1}.
Level: 1

Type: ERROR

Impact: Process

OAAM-20024: Maximum device score must be between {0} and {1}.

Cause: The maximum device score must be between {0} and {1}.

Action: Provide a maximum device score between {0} and {1}.
Level: 1

Type: ERROR

Impact: Process

OAAM-20025: Maximum device score must not be less than the minimum device score.

Cause: The maximum device score must not be less than the minimum device score.

Action: Provide a maximum device score that is more than or equal to the minimum device score.
Level: 1

Type: ERROR

Impact: Process

OAAM-20026: Minimum country score must be between {0} and {1}.

Cause: Minimum country score must be between {0} and {1}.

Action: Provide a minimum country score value between {0} and {1}.
Level: 1

Type: ERROR

Impact: Process

OAAM-20027: Maximum country score must be between {0} and {1}.

Cause: Maximum country score must be between {0} and {1}.

Action: Provide a maximum country score value between {0} and {1}.
Level: 1

Type: ERROR

Impact: Process

OAAM-20028: Maximum country score must not be less than minimum country score.

Cause: Maximum country score must not be less than minimum country score.

Action: Provide a maximum country score that is more than or equal to the minimum country score.
Level: 1

Type: ERROR

Impact: Process

OAAM-20029: Minimum state score must be between {0} and {1}.

Cause: Minimum state score must be between {0} and {1}.

Action: Provide a minimum state score value between {0} and {1}.
Level: 1

Type: ERROR

Impact: Process

OAAM-20030: Maximum state score must be between {0} and {1}.

Cause: Maximum state score must be between {0} and {1}.

Action: Provide a maximum state score value between {0} and {1}.
Level: 1

Type: ERROR

Impact: Process

OAAM-20031: Maximum state score must not be less than the minimum state score.

Cause: Maximum state score must not be less than the minimum state score.

Action: Provide a maximum state score that is more than or equal to the minimum state score.
Level: 1

Type: ERROR

Impact: Process

OAAM-20032: Minimum city score must be between {0} and {1}.

Cause: Minimum city score must be between {0} and {1}.

Action: Provide a minimum city score value between {0} and {1}.
Level: 1

Type: ERROR

Impact: Process

OAAM-20033: Maximum city score must be between {0} and {1}.

Cause: Maximum city score must be between {0} and {1}.

Action: Provide a maximum city score value between {0} and {1}.
Level: 1

Type: ERROR

Impact: Process

OAAM-20034: Maximum city score must not be less than the minimum city score.

Cause: Maximum city score must not be less than the minimum city score.

Action: Provide a maximum city score that is more than or equal to the minimum city score.
Level: 1

Type: ERROR

Impact: Process

OAAM-20035: A rule with name {0} already exists in this policy.

Cause: A rule with name {0} already exists in this policy.

Action: Provide a different rule name.
Level: 1

Type: ERROR

Impact: Process

OAAM-20036: Policy rule map with ID {0} does not exist.

Cause: Policy rule map with ID {0} does not exist.

Action: Create the appropriate policy-rule mapping.
Level: 1

Type: ERROR

Impact: Process

OAAM-20037: Condition ID cannot be null.

Cause: Condition ID cannot be null.

Action: Provide a valid Condition ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-20038: Condition with Condition ID {0} does not exist.

Cause: Condition with Condition ID {0} does not exist.

Action: Provide a valid Condition ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-20039: {0} is not a valid run mode.

Cause: {0} is not a valid run mode.

Action: Provide a valid run mode.
Level: 1

Type: ERROR

Impact: Process

OAAM-20040: {0} is not a valid policy type.

Cause: {0} is not a valid policy type.

Action: Provide a valid policy type.
Level: 1

Type: ERROR

Impact: Process

OAAM-20041: Select checkpoint.

Cause: Select checkpoint.

Action: Provide a valid checkpoint.
Level: 1

Type: ERROR

Impact: Process

OAAM-20042: Destination policy cannot be the same as the source policy.

Cause: The destination policy cannot be the same as the source policy.

Action: Provide a destination policy that is different from the source policy.
Level: 1

Type: ERROR

Impact: Process

OAAM-20043: Override with Override ID {0} does not exist.

Cause: Override with Override ID {0} does not exist.

Action: Provide a valid Override ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-20044: Override with Override ID {0} does not belong to Policy ID {1}.

Cause: Override with Override ID {0} does not belong to Policy ID {1}.

Action: Provide an Override ID that belongs to the specified policy.
Level: 1

Type: ERROR

Impact: Process

OAAM-20045: Override ID cannot be null or empty.

Cause: Override ID cannot be null or empty.

Action: Provide a valid Override ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-20046: Column ID cannot be null or empty.

Cause: Column ID cannot be null or empty.

Action: Provide a valid Column ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-20047: Rule set result with Column ID {0} does not belong to Policy ID {1}.

Cause: Rule set result with the Column ID {0} does not belong to the Policy ID {1}.

Action: Provide a Column ID that belongs to the specified policy.
Level: 1

Type: ERROR

Impact: Process

OAAM-20048: The provided overrides set is not complete for this policy.

Cause: The provided ordered Override IDs array does not contain all the Override IDs for the policy.

Action: Provide an array that has all the Override IDs for the policy.
Level: 1

Type: ERROR

Impact: Process

OAAM-20049: Override cannot be added for policy with Policy ID = {0} since no rules have been added to the policy.

Cause: Override cannot be added for policy with Policy ID = {0} since no rules have been added to the policy.

Action: For adding override the policy should have a rule.
Level: 1

Type: ERROR

Impact: Process

OAAM-20050: Condition ID list provided is null or empty.

Cause: Condition ID list provided is null or empty.

Action: Provide a non-null and non-empty list.
Level: 1

Type: ERROR

Impact: Process

OAAM-20051: Rule ID is null or rule for the given ID not found.

Cause: Rule ID is null or rule for the given ID not found.

Action: Provide a valid non-null rule.
Level: 1

Type: ERROR

Impact: Process

OAAM-20052: Rule condition for the given Rule Condition ID not found.

Cause: Rule condition for the given Rule Condition ID not found.

Action: Provide a valid and existing Rule Condition ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-20053: Policy Rule Map cannot be null.

Cause: Policy Rule Map cannot be null.

Action: Provide a non-null Policy Rule Map.
Level: 1

Type: ERROR

Impact: Process

OAAM-20054: Number of conditions does not match the number of conditions that exists.

Cause: Number of conditions does not match the number of conditions that exists.

Action: Provide the same number as the conditions available.
Level: 1

Type: ERROR

Impact: Process

OAAM-20055: Condition Map provided does not exist.

Cause: Condition Map provided does not exist.

Action: Provide a valid and existent Condition Map ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-20056: Group is already linked and cannot be linked again.

Cause: Group is already linked and cannot be linked again.

Action: Provide a valid and unlinked group for linking.
Level: 1

Type: ERROR

Impact: Process

OAAM-20057: Group ID cannot be null.

Cause: Group ID cannot be null.

Action: Provide a valid and non-null Group ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-20058: Some groups are not linked; therefore, they cannot be unlinked.

Cause: Some of the groups are not linked; therefore, they cannot be unlinked.

Action: Provide only linked groups for unlinking.
Level: 1

Type: ERROR

Impact: Process

OAAM-20059: The condition type for condition {0} is not compatible with the checkpoint for policy {1}.

Cause: The condition type for condition {0} is not compatible with the checkpoint for policy {1}.

Action: Provide a condition where the condition type is compatible with the checkpoint of the policy.
Level: 1

Type: ERROR

Impact: Process

OAAM-20060: The condition, {0}, being deleted is associated with one or more policies; therefore, it cannot be deleted.

Cause: The condition, {0}, being deleted is associated with one or more policies; therefore, it cannot be deleted.

Action: Remove the condition from the policies before deleting the condition.
Level: 1

Type: ERROR

Impact: Process

OAAM-20061: The policy type and checkpoint for the policy {0} do not match that of the parent policy {1}.

Cause: The policy type and checkpoint for the policy {0} do not match with that of the parent policy {1}.

Action: Ensure that the policy type and checkpoint for the child policy is the same as that of the parent policy.
Level: 1

Type: ERROR

Impact: Process

OAAM-20062: Score must be between {0} and {1}.

Cause: The score must be between {0} and {1}.

Action: Provide a score between {0} and {1}.
Level: 1

Type: ERROR

Impact: Process

OAAM-20063: {0} is not a valid result type.

Cause: {0} is not a valid result type.

Action: Provide a valid result type.
Level: 1

Type: ERROR

Impact: Process

OAAM-20064: {0} is not a valid rule result.

Cause: {0} is not a valid rule result.

Action: Provide a valid value for rule result.
Level: 1

Type: ERROR

Impact: Process

OAAM-20065: Rule results for columns {0} and {1} are the same.

Cause: Rule results for columns {0} and {1} are the same.

Action: Provide different rule results for each column.
Level: 1

Type: ERROR

Impact: Process

OAAM-20066: Filter key type was not provided for retrieving the filter key.

Cause: The filter key type must be provided as an Integer value. The error occurred because the value was not provided to get the correct filter based on the key type.

Action: Provide a non-null value for the filter key type and retry the operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-20067: Transaction Definition ID was not provided for retrieving the filter key.

Cause: The Transaction Definition ID provided must be a Long value. The error occurred because the value was not provided to get the correct filter based on the filter key type and transaction definition.

Action: Provide a non-null value for the Transaction Definition ID and retry this operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-20068: Transaction not found for the given Transaction Definition ID.

Cause: The Transaction Definition ID provided did not match with any of the transaction definitions in the system.

Action: Provide a valid Transaction Definition ID and retry this operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-20069: Filter condition key was not provided.

Cause: The filter condition lookup key provided was either null or empty.

Action: Provide a valid filter condition lookup key string and retry this operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-20070: Condition filter was not found based on filter condition key {0}.

Cause: The filter key provided does not match any condition filter.

Action: Provide a correct condition filter descriptor key and then retry this operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-20071: The provided filter key is invalid.

Cause: The filter key provided was either null or empty.

Action: Provide a valid lookup string. Also note that any spaces at the beginning and end of the lookup string will be ignored.
Level: 1

Type: ERROR

Impact: Process

OAAM-20072: No filter descriptor was found for key {0}.

Cause: There is no filter key descriptor that match the key provided.

Action: Provide a lookup string that matches one of the filter keys in the system. Make sure the format is right and there are no typographical errors.
Level: 1

Type: ERROR

Impact: Process

OAAM-20073: Number of rule set results is not equal to the number of rules in the policy.

Cause: Number of RuleSetResults is not equal to the number of rules in the policy.

Action: Number of RuleSetResults should be equal to the number of rules in the policy.
Level: 1

Type: ERROR

Impact: Process

OAAM-20074: Filter key descriptor is invalid.

Cause: The filter key provided was either null or empty.

Action: Provide a lookup string that is not null or empty. Also note that any spaces at the beginning and end of the lookup string will be ignored.
Level: 1

Type: ERROR

Impact: Process

OAAM-20075: A rule must have at least one condition. The current action tries to delete all conditions in this rule. Make sure at least one condition is not selected for deletion.

Cause: A rule must have at least one condition. The current action tries to delete all the conditions in this rule.

Action: Make sure at least one condition is not selected for deletion.
Level: 1

Type: ERROR

Impact: Process

OAAM-20076: Encryption is not supported for numeric data fields.

Cause: Attempt was made to set the numeric data field as encrypted. Encryption is not supported for numeric data fields.

Action: Make sure the data fields selected for encryption do not include numeric data fields. Unselect the numeric data fields and then try the encryption operation again.
Level: 1

Type: ERROR

Impact: Process

OAAM-30001: Group data is required to complete this operation.

Cause: The operation needs group data and that data was not provided.

Action: Provide valid group data and retry this operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-30002: A group with name {0} already exists.

Cause: Group by the name and value type already exists.

Action: Try a different group name for the given type of group.
Level: 1

Type: ERROR

Impact: Process

OAAM-30003: Group type {0} not found.

Cause: The group type provided for the operation was not correct.

Action: Try a different group type. Group types can be found in value.type.enum through the system enumerations user interface.
Level: 1

Type: ERROR

Impact: Process

OAAM-30004: Group name is incorrect.

Cause: The group name is incorrect. It is not a valid group name.

Action: Provide an alphanumeric string as the group name.
Level: 1

Type: ERROR

Impact: Process

OAAM-30005: Group description is incorrect.

Cause: The group description is incorrect. It is not a valid group description.

Action: Provide an alphanumeric string for the group description.
Level: 1

Type: ERROR

Impact: Process

OAAM-30006: Group cache type is incorrect.

Cause: The group cache type is incorrect. It is not a valid group cache type.

Action: Provide a correct cache type. Refer to cache type enumeration for possible values.
Level: 1

Type: ERROR

Impact: Process

OAAM-30007: Group with given information not found: {0}.

Cause: Group with given information not found.

Action: Provide the correct information so the group can be retrieved. You can search for the groups in the system.
Level: 1

Type: ERROR

Impact: Process

OAAM-30008: Group type cannot be changed.

Cause: The group type is part of the basic function in the way that the group is used in the system. The group type cannot be changed at this time.

Action: Create another group with the required value type and then use it.
Level: 1

Type: ERROR

Impact: Process

OAAM-30009: Group type {0} not found.

Cause: The group type provided for the operation was not correct.

Action: Try a different group type. Group types can be found in value.list.type.enum through the system enumerations user interface.
Level: 1

Type: ERROR

Impact: Process

OAAM-30010: Group type cannot be changed.

Cause: The group type is part of the basic function in the way that the group is used in the system. The group type cannot be changed at this time.

Action: Create another group with the required type and then use it.
Level: 1

Type: ERROR

Impact: Process

OAAM-30011: Group element {0} is invalid for this group.

Cause: The group element is null or the group element type is not compatible with the group type.

Action: Provide an element that is compatible with the group type.
Level: 1

Type: ERROR

Impact: Process

OAAM-30012: List of groups is required for this operation.

Cause: A list of groups required for this operation was found to be null.

Action: Provide a valid list of groups and then retry this operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-30013: List of groups has invalid group information.

Cause: A list of groups required for this operation contains some group-related information that is incorrect.

Action: Provide a valid list of groups with non-null Group IDs. Any duplicates in the list will be ignored.
Level: 1

Type: ERROR

Impact: Process

OAAM-30014: Query returned multiple groups from different group types.

Cause: The query returned multiple groups of mixed type.

Action: Use more specific search criteria to limit the number of groups returned.
Level: 1

Type: ERROR

Impact: Process

OAAM-30015: Group element with given information not found {0}.

Cause: Group element with given information not found.

Action: Provide correct information so the group element can be retrieved. You can use the searchGroupElements feature to find group elements in the system.
Level: 1

Type: ERROR

Impact: Process

OAAM-30016: Element {0} is not a member of group {1}.

Cause: Element is not a member of the group.

Action: Provide a correct combination of element and group.
Level: 1

Type: ERROR

Impact: Process

OAAM-30017: The group {0} cannot be deleted, because it is linked to the following policies {1}.

Cause: Policies are linked to this group; therefore, the group cannot be deleted.

Action: The group is linked to policies and might contain session and transaction data associated with this group. Hence this group cannot be deleted.
Level: 1

Type: ERROR

Impact: Process

OAAM-30018: The group {0} cannot be deleted, because it is used by rules.

Cause: Policies use this group as a parameter value in their rules; therefore, the group cannot be deleted.

Action: Remove the group name or ID as a value of the rule parameter(s) and then retry this operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-30019: The group {0} cannot be deleted, because it is used by user groups.

Cause: Some user groups use this group; therefore, the group cannot be deleted.

Action: Remove the group name or ID from those user groups and then retry this operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-30020: The IP Cluster object cannot be null.

Cause: The OARMIPCluster object cannot be null.

Action: Pass a non-null OARMIPCluster object.
Level: 1

Type: ERROR

Impact: Process

OAAM-30021: The label for IP cluster cannot be null.

Cause: The label for IP cluster cannot be null.

Action: Pass a non-null label for IP cluster.
Level: 1

Type: ERROR

Impact: Process

OAAM-30022: IP cluster with label {0} already exists.

Cause: IP cluster with label {0} already exists.

Action: Provide a different label for IP cluster.
Level: 1

Type: ERROR

Impact: Process

OAAM-30023: Invalid IP address range. From IP Address cannot be greater than To IP Address.

Cause: Invalid IP address range. From IP Address cannot be greater than To IP Address.

Action: Provide a From IP Address that is less than To IP Address.
Level: 1

Type: ERROR

Impact: Process

OAAM-30024: The IP address {0} is invalid.

Cause: The IP address {0} is invalid.

Action: Provide a valid IP address.
Level: 1

Type: ERROR

Impact: Process

OAAM-30025: The list of Cluster IDs cannot be null.

Cause: The list of Cluster IDs cannot be null.

Action: Provide a non-null list of Cluster IDs.
Level: 1

Type: ERROR

Impact: Process

OAAM-30026: The IP cluster with Cluster ID {0} does not exist.

Cause: The IP cluster with Cluster ID {0} does not exist.

Action: Provide a valid Cluster ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-30027: The IP cluster with Cluster ID {0} is being used by one or more groups and cannot be deleted.

Cause: The IP cluster with Cluster ID {0} is being used by one or more groups and cannot be deleted.

Action: Remove the IP cluster from the groups and then try to delete it.
Level: 1

Type: ERROR

Impact: Process

OAAM-30028: Duplicate element {0} cannot be added to group {1}.

Cause: The element is already present in the group. Duplicate elements cannot be added to the group.

Action: Add a different element to the group.
Level: 1

Type: ERROR

Impact: Process

OAAM-30029: The {0} group cannot be deleted because it is being used by one or more policies.

Cause: The group cannot be deleted because it is being used by one or more policies.

Action: The group cannot be deleted because it is neing used by one or more policies.
Level: 1

Type: ERROR

Impact: Process

OAAM-30030: The IP Range {0} cannot be created because a similar IP Range already exists.

Cause: IP Ranges being created have duplicate entries.

Action: Ensure to enter a unique IP Range.
Level: 1

Type: ERROR

Impact: Process

OAAM-30031: The user cannot be removed from the group(s) {0} because they are primary user groups.

Cause: The user cannot be removed from the groups because they are primary user groups.

Action: Select other groups and retry this operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-30032: The group {0} cannot be deleted, because it is used by policies.

Cause: Policies use this group as a parameter value in trigger combinations; therefore, the group cannot be deleted.

Action: Remove the group name or ID as a value from policy trigger combinations and then retry this operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-35001: {0} is a duplicate of enumeration {1}. Enter another {2}.

Cause: Enumeration already exists in the database. Duplicate enumerations cannot be added.

Action: Enter a unique enumeration and retry this operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-35002: Default Property cannot be deleted.

Cause: Default Property cannot be deleted.

Action: Select another property and retry this operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-40001: Import failed error: {0}.

Cause: Import failed error: {0}.

Action: Check the error logs. If the problem remains unresolved, you may contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

OAAM-40002: Invalid profile type: {0}.

Cause: Invalid profile type: {0}.

Action: Check the error logs. If the problem remains unresolved, you may contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

OAAM-40003: Invalid policy type: {0}.

Cause: Invalid policy type: {0}.

Action: Check the error logs. If the problem remains unresolved, you may contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

OAAM-40004: No policy data for policy: {0}.

Cause: No policy data for policy: {0}.

Action: Check the error logs. If the problem remains unresolved, you may contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

OAAM-40005: Policy already exists in the database with name {0}.

Cause: The policy already exists in the database with the name {0}.

Action: Check the error logs. If the problem remains unresolved, you may contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

OAAM-40006: Import failed, no group: {0}, rule instance: {1}.

Cause: Import failed, no group: {0}, rule instance: {1}.

Action: Check the error logs. If the problem remains unresolved, you may contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

OAAM-40007: Import failed. Unable to set Override action: {0}.

Cause: Import failed. Unable to set Override action: {0}.

Action: Check the error logs. If the problem remains unresolved, you may contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

OAAM-40008: Import failed. Unable to set Override alert: {0}.

Cause: Import failed. Unable to set Override alert: {0}.

Action: Check the error logs. If the problem remains unresolved, you may contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

OAAM-40009: Bad rule data, policy: {0}, Rule Global ID: {1}.

Cause: Bad rule data, policy: {0}, Rule Global ID: {1}.

Action: Check the error logs. If the problem remains unresolved, you may contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

OAAM-40010: Policy: {0} Rule Global ID: {1} not present.

Cause: Policy: {0} Rule Global ID: {1} not present.

Action: Check the error logs. If the problem remains unresolved, you may contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

OAAM-40011: Import failed. Unable to set Alert group: {0}, rule instance: {1}.

Cause: Import failed. Unable to set Alert group: {0}, rule instance: {1}.

Action: Check the error logs. If the problem remains unresolved, you may contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

OAAM-40012: Import failed. Unable to set Action group: {0}, rule instance: {1}.

Cause: Import failed. Unable to set Action group: {0}, rule instance: {1}.

Action: Check the error logs. If the problem remains unresolved, you may contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

OAAM-40013: Import failed. Unable to set Exclude group: {0}, rule instance: {1}.

Cause: Import failed. Unable to set Exclude group: {0}, rule instance: {1}.

Action: Check the error logs. If the problem remains unresolved, you may contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

OAAM-40014: Question category not found.

Cause: The question category was not found.

Action: Check the error logs. If the problem remains unresolved, you may contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

OAAM-40015: Validation not found.

Cause: The validation was not found.

Action: Check the error logs. If the problem remains unresolved, you may contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

OAAM-40016: Question locale not found.

Cause: The question locale was not found.

Action: Check the error logs. If the problem remains unresolved, you may contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

OAAM-40017: Question with Question ID {0} not found.

Cause: The question with the Question ID was not found.

Action: Provide a valid Question ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-40018: Configurable action with Action ID {0} not found.

Cause: The configurable action with the Action ID was not found.

Action: Provide a valid Action ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-40019: Transaction with Transaction ID {0} not found.

Cause: The transaction with the Transaction ID was not found.

Action: Provide a valid Transaction ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-40020: Pattern with Pattern ID {0} not found.

Cause: The pattern with the Pattern ID was not found.

Action: Provide a valid Pattern ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-40021: Entity with Entity ID {0} not found.

Cause: The entity with the Entity ID was not found.

Action: Provide a valid Entity ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-40022: Group with List ID {0} not found.

Cause: The group with the List ID was not found.

Action: Provide a valid List ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-40023: Policy set with Policy Set ID {0} not found.

Cause: The policy set with Policy Set ID was not found.

Action: Provide a valid Policy Set ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-40024: Answer hint with Answer Hint ID {0} not found.

Cause: The answer hint with the Answer Hint ID was not found.

Action: Provide a valid Answer Hint ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-40025: Validation with Validation ID {0} not found.

Cause: Validation with Validation ID not found.

Action: Provide a valid Validation ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-40026: Task group with Group ID {0} not found.

Cause: Task group with Group ID not found.

Action: Provide a valid Group ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-40027: A configurable action with the name {0} already exists.

Cause: A configurable action with the name already exists.

Action: Change the name of the existing configurable action.
Level: 1

Type: ERROR

Impact: Process

OAAM-40028: One or more files in the ZIP file are invalid XML files.

Cause: One or more files in the ZIP file are invalid XML files.

Action: One or more files in the ZIP file are invalid XML files.
Level: 1

Type: ERROR

Impact: Process

OAAM-40029: Import content has system properties. System properties are not imported as part of this Import action.

Cause: System properties are not imported as part of Import Properties. System type properties may exist in the import data; they are not imported as part of this Import action.

Action: This is not an error. It is only an informative message about the system properties. System properties are considered to be specific to the system or environment where the OAAM product runs. Such properties are not imported by other OAAM servers even when they are part of the data being imported. No user action is required.
Level: 1

Type: ERROR

Impact: Process

OAAM-40030: Import ignored the following system properties: {0}

Cause: System properties, which were not imported as part of import properties, are listed here.

Action: This is not an error. It is only an informative message about the system properties that were not imported. No user action is required.
Level: 1

Type: ERROR

Impact: Process

OAAM-40031: Export list has some properties that are system properties. System properties are not exported in this Export action.

Cause: System properties are not exported as part of Export Properties. There may be some system type properties in the export list. They are not exported as part of this export.

Action: This is not an error. It is only an informative message about the system properties. System properties are considered to be specific to the system or environment where OAAM product runs. Such properties are not exported by OAAM servers even when they are part of the list of properties being imported. No user action is required.
Level: 1

Type: ERROR

Impact: Process

OAAM-40032: Export has ignored the following system properties: {0}

Cause: System properties, which are not exported as part of Export Properties, are listed here.

Action: This is not an error. It is only an informative message about the system properties which are not exported. No user action is required.
Level: 1

Type: ERROR

Impact: Process

OAAM-40033: File provided does not appear to be correct for Import action.

Cause: The file provided for import may not be correct. The file may not be the one that was exported from OAAM, or it may contain data that cannot be imported into OAAM.

Action: Check that the file was obtained from another OAAM export. See if the file is not empty, and is readable and a valid ZIP file.
Level: 1

Type: ERROR

Impact: Process

OAAM-40034: File import error. Check the log for details.

Cause: A file import error occurred. Invalid import files were found in the ZIP file.

Action: Check whether the ZIP file contains valid import files.
Level: 1

Type: ERROR

Impact: Process

OAAM-40035: Unknown error during import operation. Check the log for details.

Cause: Invalid import files may exist in the ZIP file.

Action: Check if the ZIP file contains invalid import files.
Level: 1

Type: ERROR

Impact: Process

OAAM-40501: Snapshot name cannot be null or empty.

Cause: Snapshot name cannot be null or empty.

Action: Provide a snapshot name.
Level: 1

Type: ERROR

Impact: Process

OAAM-40502: Snapshot description cannot be null or empty.

Cause: Snapshot description cannot be null or empty.

Action: Provide a valid Snapshot description.
Level: 1

Type: ERROR

Impact: Process

OAAM-40503: Snapshot identifier cannot be null.

Cause: Snapshot identifier cannot be null. This API requires a valid snapshot identifier.

Action: Provide a valid snapshot identifier.
Level: 1

Type: ERROR

Impact: Process

OAAM-40504: Snapshot with snapshot identifier {0} does not exist.

Cause: Snapshot with given snapshot identifier does not exist.

Action: Ensure that you provide the correct snapshot identifier for this operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-40505: List of snapshots was not found.

Cause: List of snapshot identifiers was not found. The list is a mandatory parameter when performing this operation in the interface.

Action: Provide the correct list of snapshot identifiers and retry the operation. The list is a mandatory parameter and cannot be null.
Level: 1

Type: ERROR

Impact: Process

OAAM-40506: Snapshot data provided does not appear correct.

Cause: Snapshot data bytes do not appear correct.

Action: Ensure that the snapshot bytes array is not null and and that the array represents the correct snapshot data. Make sure the byte data from the saved snapshot ZIP file is represented, and then retry the operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-50001: The fully-qualified transaction key must be a valid string.

Cause: The transaction key supplied to look up the transaction definition is not correct. It should be a non-empty string.

Action: Verify that the transaction key provided is correct and a non-empty string.
Level: 1

Type: ERROR

Impact: Process

OAAM-50002: Transaction definition was not found for the key {0}.

Cause: The key provided does not match any transaction definition.

Action: Verify that the transaction key provided is correct and a non-empty string.
Level: 1

Type: ERROR

Impact: Process

OAAM-50003: Transaction Definition ID is null.

Cause: Transaction Definition ID is null.

Action: Provide a valid Transaction Definition ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50004: Transaction Definition ID is invalid or non-existent.

Cause: Transaction Definition ID is invalid or non-existent.

Action: Provide a valid and existent Transaction Definition ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50005: Transaction name is null or invalid.

Cause: Transaction name is null or invalid.

Action: Provide a valid transaction name.
Level: 1

Type: ERROR

Impact: Process

OAAM-50006: Transaction definition cannot be null.

Cause: Transaction definition cannot be null.

Action: Provide a valid transaction definition object.
Level: 1

Type: ERROR

Impact: Process

OAAM-50007: Transaction Definition ID is null.

Cause: Transaction Definition ID is null.

Action: Provide a non-null Transaction Definition ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50008: Transaction Definition ID is either invalid or does not exist.

Cause: Transaction Definition ID is either invalid or does not exist.

Action: Provide valid Transaction Definition ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50009: Transaction definition could not be updated.

Cause: Transaction definition could not be updated.

Action: Check error log for details.
Level: 1

Type: ERROR

Impact: Process

OAAM-50010: Transaction Definition ID list is null or empty.

Cause: Transaction Definition ID list is null or empty.

Action: Provide a valid Transaction Definition ID list.
Level: 1

Type: ERROR

Impact: Process

OAAM-50011: Transaction definition for the given transaction definition {0} not found.

Cause: Transaction definition for the given transaction definition {0} not found.

Action: Provide a valid Transaction Definition ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50012: Transaction input data mapping is missing for transaction {0}.

Cause: Transaction input data mapping is missing for transaction {0}.

Action: Provide transaction input data mapping to activate the transaction {0}.
Level: 1

Type: ERROR

Impact: Process

OAAM-50013: Transaction definition for the given transaction definition {0} not found.

Cause: Transaction definition for the given transaction definition {0} not found.

Action: Provide a valid transaction definition.
Level: 1

Type: ERROR

Impact: Process

OAAM-50014: Transaction input data mapping is missing for transaction {0}.

Cause: Transaction input data mapping is missing for transaction {0}.

Action: Provide transaction input data to activate the transaction {0}.
Level: 1

Type: ERROR

Impact: Process

OAAM-50015: Source data is missing for transaction {0}.

Cause: Source data is missing for transaction {0}.

Action: Provide the required source data to activate transaction {0}.
Level: 1

Type: ERROR

Impact: Process

OAAM-50016: Transaction data mapping is missing for transaction {0}.

Cause: Transaction data mapping is missing for transaction {0}.

Action: Provide transaction data mapping to activate transaction {0}.
Level: 1

Type: ERROR

Impact: Process

OAAM-50017: Transaction data mapping is missing for transaction {0}.

Cause: Transaction data mapping is missing for transaction {0}.

Action: Provide transaction data mapping to activate transaction {0}.
Level: 1

Type: ERROR

Impact: Process

OAAM-50018: Entity mapping could not be found for transaction {0}.

Cause: Entity mapping could not be found for transaction {0}.

Action: Make sure all entities are mapped before activating transaction {0}.
Level: 1

Type: ERROR

Impact: Process

OAAM-50019: Transaction and entity mapping is missing for transaction {0}.

Cause: Transaction and entity mapping is missing for transaction {0}.

Action: Provide transaction and entity mapping to activate transaction {0}.
Level: 1

Type: ERROR

Impact: Process

OAAM-50020: Transaction Entity Definition Map ID cannot be null.

Cause: Transaction Entity Definition Map ID cannot be null.

Action: Provide a valid Transaction Entity Definition Map ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50021: Transaction Definition ID missing while creating transaction entity map.

Cause: Transaction Definition ID missing while creating transaction entity map.

Action: Provide a valid Transaction Definition ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50022: Entity Definition ID missing while creating transaction entity map.

Cause: Entity Definition ID missing while creating transaction entity map.

Action: Provide a valid Entity Definition ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50023: Entity definition validation failed. Operation cannot be performed.

Cause: Entity definition validation failed. Operation cannot be performed.

Action: Provide a valid entity definition.
Level: 1

Type: ERROR

Impact: Process

OAAM-50024: Entity name validation failed.

Cause: Entity name validation failed.

Action: Provide a valid and unique entity name.
Level: 1

Type: ERROR

Impact: Process

OAAM-50025: Invalid entity relation.

Cause: Invalid entity relation.

Action: Provide a valid entity relation.
Level: 1

Type: ERROR

Impact: Process

OAAM-50026: Invalid display order.

Cause: Invalid display order.

Action: Provide a valid display order.
Level: 1

Type: ERROR

Impact: Process

OAAM-50027: Duplicate entity name.

Cause: Duplicate entity name.

Action: Provide a valid and unique entity name.
Level: 1

Type: ERROR

Impact: Process

OAAM-50028: Invalid and non-unique entity relation.

Cause: Invalid and non-unique entity relation.

Action: Provide a valid and unique entity relation.
Level: 1

Type: ERROR

Impact: Process

OAAM-50029: Invalid and non-unique display order.

Cause: Invalid and non-unique display order.

Action: Provide a valid and unique display order.
Level: 1

Type: ERROR

Impact: Process

OAAM-50030: Transaction Definition ID missing while updating transaction entity map.

Cause: Transaction Definition ID missing while updating transaction entity map.

Action: Provide a valid and non-null Transaction Definition ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50031: Entity Definition ID missing while updating transaction entity map.

Cause: Entity Definition ID missing while updating transaction entity map.

Action: Provide a valid and non-null Entity Definition ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50032: Transaction delete is not allowed.

Cause: Transaction delete is not allowed.

Action: Select a valid transaction for delete.
Level: 1

Type: ERROR

Impact: Process

OAAM-50033: Data element definition cannot be null.

Cause: Data element definition cannot be null.

Action: Provide a valid data element definition.
Level: 1

Type: ERROR

Impact: Process

OAAM-50034: Data element definition array cannot be null or empty.

Cause: Data element definition array cannot be null or empty.

Action: Provide a non-null and valid data element definition array.
Level: 1

Type: ERROR

Impact: Process

OAAM-50035: Attribute validation failed.

Cause: Attribute validation failed.

Action: Provide a valid attribute.
Level: 1

Type: ERROR

Impact: Process

OAAM-50036: Creating the attribute failed.

Cause: Creating the attribute failed.

Action: Provide the valid entry for creating the attribute.
Level: 1

Type: ERROR

Impact: Process

OAAM-50037: Attribute not found.

Cause: Attribute not found.

Action: Provide a valid and non-null attribute.
Level: 1

Type: ERROR

Impact: Process

OAAM-50038: Cannot find a matching data element definition.

Cause: Cannot find a matching data element definition.

Action: Provide a valid entry with a matching data element definition.
Level: 1

Type: ERROR

Impact: Process

OAAM-50039: No attribute found to delete.

Cause: No attribute found to delete.

Action: Provide a valid attribute to delete.
Level: 1

Type: ERROR

Impact: Process

OAAM-50040: Source validation failed.

Cause: Source validation failed.

Action: Provide valid source data.
Level: 1

Type: ERROR

Impact: Process

OAAM-50041: Cannot find a matching transaction data mapping.

Cause: Cannot find a matching Transaction Data Mapping ID.

Action: Provide a valid and matching Transaction Data Mapping ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50042: Transaction data mapping is null or empty.

Cause: Transaction data mapping IDs are null or empty.

Action: Provide a non-null or valid Transaction Data Mapping ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50043: No transaction mapping found to delete.

Cause: No transaction mapping found to delete.

Action: Transaction should have one or more mappings to delete.
Level: 1

Type: ERROR

Impact: Process

OAAM-50044: No entity mapping found to delete.

Cause: No entity mapping found to delete.

Action: Entity should have one or more mappings to delete.
Level: 1

Type: ERROR

Impact: Process

OAAM-50045: Transaction name is null or empty.

Cause: Transaction name is null or empty.

Action: Provide a valid and non-null transaction name.
Level: 1

Type: ERROR

Impact: Process

OAAM-50046: Transaction key is null or empty.

Cause: Transaction key is null or empty.

Action: Provide a valid and non-null transaction key.
Level: 1

Type: ERROR

Impact: Process

OAAM-50047: Transaction description is null or empty.

Cause: Transaction description is null or empty.

Action: Provide a valid and non-null transaction description.
Level: 1

Type: ERROR

Impact: Process

OAAM-50048: Duplicate transaction name or transaction key; validation failed.

Cause: Validation failed because of a duplicate transaction name or transaction key.

Action: Provide a valid and unique transaction name or transaction key.
Level: 1

Type: ERROR

Impact: Process

OAAM-50049: Transaction entity map for the ID {0} does not exist.

Cause: Transaction entity map for the ID does not exist.

Action: Provide a valid Transaction Entity Map ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50050: Transaction Entity Map ID cannot be null.

Cause: Transaction Entity Map ID cannot be null.

Action: Provide a valid and non-null Transaction Entity Map ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50102: Display/name scheme is not set for entity {0}.

Cause: Display/name scheme is not set for entity.

Action: Set the display/name scheme before activation.
Level: 1

Type: ERROR

Impact: Process

OAAM-50103: ID scheme is not set for entity {0}.

Cause: ID scheme is not set for entity.

Action: Set the ID scheme before activation.
Level: 1

Type: ERROR

Impact: Process

OAAM-50104: No data element definitions exist for entity {0}.

Cause: No data element definitions exist for entity.

Action: Add data element definitions before activating.
Level: 1

Type: ERROR

Impact: Process

OAAM-50105: Row and Column values are not unique/valid for data element {0} for entity {1}.

Cause: Row and Column values are not unique/valid for data element for entity.

Action: Provide unique Row and Column values for data elements within an entity.
Level: 1

Type: ERROR

Impact: Process

OAAM-50106: There is more than one data element with the same internal identifier, {0}, for entity {1}.

Cause: There is more than one data element with the same internal identifier for the same entity.

Action: Provide a unique internal identifiers for data element definitions within an entity.
Level: 1

Type: ERROR

Impact: Process

OAAM-50107: Index for numeric data elements is not between {0} and {1} for entity {2}.

Cause: Index for numeric data elements is not between {0} and {1} for entity {2}.

Action: Ensure that index for numeric data elements is between {0} and {1} for entity {2}.
Level: 1

Type: ERROR

Impact: Process

OAAM-50108: Index for non-numeric data elements is not between {0} and {1} for entity {2}.

Cause: Index for non-numeric data elements is not between {0} and {1} for entity {2}.

Action: Ensure that index for non-numeric data elements is between {0} and {1} for entity {2}.
Level: 1

Type: ERROR

Impact: Process

OAAM-50109: No display scheme elements are available for entity {0}.

Cause: No display scheme elements have been added for entity {0}.

Action: Add display scheme elements before activating.
Level: 1

Type: ERROR

Impact: Process

OAAM-50110: There is more than one display data element with the same internal ID, {0}, for entity {1}.

Cause: There is more than one display data element with the same internal ID, {0}, for entity {1}.

Action: Entity should not have more than one display data element with the same internal ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50111: There is more than one display data element with the same order, {0}, for entity {1}.

Cause: There is more than one display data element with the same order, {0}, for entity {1}.

Action: Correct the ordering for the display data elements for entity {1}.
Level: 1

Type: ERROR

Impact: Process

OAAM-50112: No ID scheme elements are available for entity {0}.

Cause: No ID scheme elements have been added for entity {0}.

Action: Add ID scheme elements before activating.
Level: 1

Type: ERROR

Impact: Process

OAAM-50113: There is more than one ID scheme data element with the same internal ID, {0}, for entity {1}.

Cause: There is more than one ID scheme data element with the same internal ID, {0}, for entity {1}.

Action: The entity should not have more than one ID scheme data element with the same internal ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50114: There is more than one ID scheme data element with the same order, {0}, for entity {1}.

Cause: There is more than one ID scheme data element with the same order, {0}, for entity {1}.

Action: The entity should not have more than one ID scheme data element with the same order.
Level: 1

Type: ERROR

Impact: Process

OAAM-50115: Database error.

Cause: Database error.

Action: Database error.
Level: 1

Type: ERROR

Impact: Process

OAAM-50116: Entity Name field cannot be blank.

Cause: Entity Name field cannot be blank.

Action: Provide an entity name for the Entity Name field.
Level: 1

Type: ERROR

Impact: Process

OAAM-50117: Entity Key field cannot be blank.

Cause: Entity Key field cannot be blank.

Action: Provide an entity key in the Key field.
Level: 1

Type: ERROR

Impact: Process

OAAM-50118: Entity Description field cannot be blank.

Cause: Entity Description field cannot be blank.

Action: Provide an entity description in the Description field.
Level: 1

Type: ERROR

Impact: Process

OAAM-50119: Another entity definition with the same name already exists.

Cause: Another entity definition with the same name already exists.

Action: Provide a unique name for the entity definition.
Level: 1

Type: ERROR

Impact: Process

OAAM-50120: Internal ID field of data elements cannot be blank.

Cause: Internal ID field of data elements cannot be blank.

Action: Provide an internal ID for data elements.
Level: 1

Type: ERROR

Impact: Process

OAAM-50121: Data Type field of the data elements of the entity cannot be blank.

Cause: Data Type field of the data elements of the entity cannot be blank.

Action: Provide a data type for data elements of the entity.
Level: 1

Type: ERROR

Impact: Process

OAAM-50122: Row number of the data elements of the entity cannot be less than zero.

Cause: Row number of the data elements of the entity cannot be less than zero.

Action: Provide positive integers as row numbers for the data elements of the entity.
Level: 1

Type: ERROR

Impact: Process

OAAM-50123: Column number of data elements of the entity cannot be less than zero.

Cause: Column number of data elements of the entity cannot be less than zero.

Action: Provide a positive integer as the column number for data elements of the entity.
Level: 1

Type: ERROR

Impact: Process

OAAM-50124: Internal ID of the data element of the entity should be unique.

Cause: Internal ID of data element of the entity should be unique.

Action: Ensure that the internal ID of the data element of the entity is unique.
Level: 1

Type: ERROR

Impact: Process

OAAM-50125: Name of data element of the entity should be unique.

Cause: Name of data element of the entity should be unique.

Action: Ensure that the name of the data element of the entity is unique.
Level: 1

Type: ERROR

Impact: Process

OAAM-50126: More than one data element definition exists with the same row and column.

Cause: More than one data element definition exists with the same row and column.

Action: Ensure that row and column values are unique for the data element definitions.
Level: 1

Type: ERROR

Impact: Process

OAAM-50127: Validation error: Data element definition identifier should not be set for creating a new data element definition.

Cause: Validation error: Data element definition identifier should not be set for creating a new data element definition. The identifier is generated by the system for the new data element.

Action: Validation error: Data element definition identifier should not be set for creating a new data element definition. The identifier is generated by the system for the new data element.
Level: 1

Type: ERROR

Impact: Process

OAAM-50128: Column value for numeric data elements should be between {0} and {1}.

Cause: Column value for numeric data elements should be between {0} and {1}.

Action: Column value for numeric data elements should be between {0} and {1}.
Level: 1

Type: ERROR

Impact: Process

OAAM-50129: Column value for non-numeric data elements should be between 1 and {0}.

Cause: Column value for non-numeric data elements should be between 1 and {0}.

Action: Column value for non-numeric data elements should be between 1 and {0}.
Level: 1

Type: ERROR

Impact: Process

OAAM-50130: The entity {0} cannot be disabled because it is used by one or more active transactions.

Cause: The entity {0} cannot be disabled because it is used by one or more active transactions.

Action: The entity {0} cannot be disabled because it is used by one or more active transactions.
Level: 1

Type: ERROR

Impact: Process

OAAM-50131: The entity {0} cannot be deleted because it is used by one or more active transactions.

Cause: The entity {0} cannot be deleted because it is used by one or more active transactions.

Action: The entity {0} cannot be deleted because it is used by one or more active transactions.
Level: 1

Type: ERROR

Impact: Process

OAAM-50132: Entity Definition ID cannot be null.

Cause: Entity Definition ID cannot be null.

Action: Entity Definition ID cannot be null.
Level: 1

Type: ERROR

Impact: Process

OAAM-50133: Data profile definition not found for the Entity Definition ID.

Cause: Data profile definition not found for the Entity Definition ID.

Action: Data profile definition not found for the Entity Definition ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50134: Data Definition ID does not match with Data Definition ID of the data profile.

Cause: Data Definition ID does not match with Data Definition ID of the data profile.

Action: Data Definition ID does not match with Data Definition ID of the data profile.
Level: 1

Type: ERROR

Impact: Process

OAAM-50135: Unable to create external ID data definition for the Entity Definition ID.

Cause: Unable to create external ID data definition for the Entity Definition ID.

Action: Unable to create external ID data definition for the Entity Definition ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50136: The element with Element ID {0} cannot be deleted because it is used by one or more active transactions.

Cause: The element with Element ID {0} cannot be deleted because it is used by one or more active transactions.

Action: The element with Element ID {0} cannot be deleted because it is used by one or more active transactions.
Level: 1

Type: ERROR

Impact: Process

OAAM-50137: Data element having Data Definition Element ID {0} does not exist.

Cause: Data element having Data Definition Element ID {0} does not exist.

Action: Data element having Data Definition Element ID {0} does not exist.
Level: 1

Type: ERROR

Impact: Process

OAAM-50138: Identification scheme cannot be null.

Cause: Identification scheme cannot be null.

Action: Identification scheme cannot be null.
Level: 1

Type: ERROR

Impact: Process

OAAM-50139: Data Definition Element ID cannot be null.

Cause: Data Definition Element ID cannot be null.

Action: Data Definition Element ID cannot be null.
Level: 1

Type: ERROR

Impact: Process

OAAM-50140: System error occurred while loading entities.

Cause: System error occurred while loading entities.

Action: System error occurred while loading entities.
Level: 1

Type: ERROR

Impact: Process

OAAM-50141: Error loading object {0} with primary key {1} from database. {2}.

Cause: Error loading object {0} with primary key {1} from database. {2}.

Action: Error loading object {0} with primary key {1} from database. {2}s.
Level: 1

Type: ERROR

Impact: Process

OAAM-50142: Error inserting object {0} to database.

Cause: Error inserting object to database. Database may not be available.

Action: Error inserting object to database. Try the operation again.
Level: 1

Type: ERROR

Impact: Process

OAAM-50200: Configurable Action ID provided is invalid or does not exist.

Cause: Configurable Action ID provided is invalid or does not exist.

Action: Provide a valid and existent Configurable Action ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50201: Configurable Action ID cannot be null.

Cause: Configurable Action ID cannot be null.

Action: Provide a non-null Configurable Action ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50202: Action parameters mismatch.

Cause: Action parameters mismatch.

Action: Provide a valid action parameter.
Level: 1

Type: ERROR

Impact: Process

OAAM-50203: Action name provided cannot be null.

Cause: Action name provided cannot be null.

Action: Provide a non-null action name.
Level: 1

Type: ERROR

Impact: Process

OAAM-50204: Java Class Name provided cannot be null.

Cause: Java Class Name provided cannot be null.

Action: Provide a non-null Java class name.
Level: 1

Type: ERROR

Impact: Process

OAAM-50205: Duplicate action.

Cause: Duplicate action.

Action: Provide a unique value to create a valid action.
Level: 1

Type: ERROR

Impact: Process

OAAM-50206: Configurable action cannot be deleted as it is currently used by one or more Action Instances.

Cause: Configurable action cannot be deleted as it is currently used by one or more Action Instances.

Action: Select a valid configurable action that is not in use.
Level: 1

Type: ERROR

Impact: Process

OAAM-50207: Invalid or non-existent Action ID.

Cause: Invalid or non-existent Action ID.

Action: Provide a valid and existent Action ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50208: Action ID list provided cannot be null or empty.

Cause: Action ID list provided cannot be null or empty.

Action: Provide a non-null and valid Action ID list.
Level: 1

Type: ERROR

Impact: Process

OAAM-50209: Action ID provided cannot be null.

Cause: Action ID provided cannot be null.

Action: Provide a non-null Action ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50210: Action Instance ID provided is invalid or non-existent.

Cause: Action Instance ID provided is invalid or non-existent.

Action: Provide a valid and existent Action Instance ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50211: Action Instance ID cannot be null.

Cause: Action Instance ID cannot be null.

Action: Provide a non-null Action Instance ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50212: Execution Order should be unique for synchronous actions.

Cause: Execution Order should be unique for synchronous actions.

Action: Provide unique execution order for each synchronous action.
Level: 1

Type: ERROR

Impact: Process

OAAM-50213: Action Instance name is a duplicate.

Cause: Action Instance name is a duplicate.

Action: Provide a unique action instance name.
Level: 1

Type: ERROR

Impact: Process

OAAM-50214: Action instance association is not allowed.

Cause: Action instance association is not allowed.

Action: Select the valid instance and parameters for the association.
Level: 1

Type: ERROR

Impact: Process

OAAM-50215: Invalid or non-existent Action Instance ID {0}.

Cause: Invalid or non-existent Action Instance ID {0}.

Action: Provide a valid and existing Action Instance ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50216: Value {1} provided for the parameter name {0} is not a valid Boolean value.

Cause: Value {1} provided for the parameter name {0} is not a valid Boolean value.

Action: Provide a valid Boolean value for the parameter name {0}. It can be true or false only.
Level: 1

Type: ERROR

Impact: Process

OAAM-50217: Value {1} provided for the parameter name {0} is not a valid Integer value.

Cause: Value {1} provided for the parameter name {0} is not a valid Integer value.

Action: Provide a valid Integer value for the parameter name {0}.
Level: 1

Type: ERROR

Impact: Process

OAAM-50218: Value {1} provided for the parameter name {0} is not a valid Long value.

Cause: Value {1} provided for the parameter name {0} is not a valid Long value.

Action: Provide a valid Long value for the parameter name {0}.
Level: 1

Type: ERROR

Impact: Process

OAAM-50219: Value {1} provided for the parameter name {0} is not a valid Date value.

Cause: Value {1} provided for the parameter name {0} is not a valid Date value.

Action: Provide a valid Date value for the parameter name {0}.
Level: 1

Type: ERROR

Impact: Process

OAAM-50220: Action parameter value validation failed.

Cause: The action parameter value validation failed.

Action: Verify all the parameter values for its data type are valid.
Level: 1

Type: ERROR

Impact: Process

OAAM-50221: Nonexistent or invalid Parameter ID {0} with the parameter name {1}.

Cause: Nonexistent or invalid Parameter ID {0} with the parameter name {1}.

Action: Provide a valid existing parameter and value.
Level: 1

Type: ERROR

Impact: Process

OAAM-50222: Unable to load configurable action class {0}. Ensure the class is made available in the class path.

Cause: Unable to load configurable action class {0}. Ensure the class is made available in the class path.

Action: Provide a valid class name with the class already in the class path.
Level: 1

Type: ERROR

Impact: Process

OAAM-60001: Pattern ID cannot be null.

Cause: Pattern ID cannot be null.

Action: Pattern ID cannot be null.
Level: 1

Type: ERROR

Impact: Process

OAAM-60002: Pattern with the name {0} already exists.

Cause: Pattern with the name {0} already exists.

Action: Pattern with the name {0} already exists.
Level: 1

Type: ERROR

Impact: Process

OAAM-60003: Comparison value is required.

Cause: Comparison value is required.

Action: Comparison value is required.
Level: 1

Type: ERROR

Impact: Process

OAAM-60004: The value {0} is invalid.

Cause: The value {0} is invalid.

Action: The value {0} is invalid.
Level: 1

Type: ERROR

Impact: Process

OAAM-60005: The value {0} is not a valid Integer value.

Cause: The value {0} is not a valid Integer value.

Action: The value {0} is not a valid Integer value.
Level: 1

Type: ERROR

Impact: Process

OAAM-60006: The value {0} is not a valid Long value.

Cause: The value {0} is not a valid Long value.

Action: The value {0} is not a valid Long value.
Level: 1

Type: ERROR

Impact: Process

OAAM-60007: The value {0} is not a valid Boolean value.

Cause: The value {0} is not a valid Boolean value.

Action: The value {0} is not a valid Boolean value.
Level: 1

Type: ERROR

Impact: Process

OAAM-60008: The value {0} is not a valid Float value.

Cause: The value {0} is not a valid Float value.

Action: The value {0} is not a valid Float value.
Level: 1

Type: ERROR

Impact: Process

OAAM-60009: The value {0} is not a valid Date value.

Cause: The value {0} is not a valid Date value.

Action: The value {0} is not a valid Date value.
Level: 1

Type: ERROR

Impact: Process

OAAM-60010: The value {0} is not a valid Double value.

Cause: The value {0} is not a valid Double value.

Action: The value {0} is not a valid Double value.
Level: 1

Type: ERROR

Impact: Process

OAAM-60011: Entered values overlaps with {0}-{1} range.

Cause: Entered values overlaps with {0}-{1} range.

Action: Entered values overlaps with {0}-{1} range.
Level: 1

Type: ERROR

Impact: Process

OAAM-60012: The attribute already exists.

Cause: The attribute already exists.

Action: The attribute already exists.
Level: 1

Type: ERROR

Impact: Process

OAAM-60013: Pattern parameter with Parameter ID {0} does not exist.

Cause: Pattern parameter with the Parameter ID {0} does not exist.

Action: Pattern parameter with the Parameter ID {0} does not exist.
Level: 1

Type: ERROR

Impact: Process

OAAM-60014: Parameter ID cannot be null.

Cause: Parameter ID cannot be null.

Action: Parameter ID cannot be null.
Level: 1

Type: ERROR

Impact: Process

OAAM-60015: Data has already been collected for this pattern. Changing this pattern will potentially render that data inaccurate.

Cause: Data has already been collected for this pattern. Changing this pattern will potentially render that data inaccurate.

Action: Data has already been collected for this pattern. Changing this pattern will potentially render that data inaccurate.
Level: 1

Type: ERROR

Impact: Process

OAAM-60016: Pattern is associated with active policies - {0}.

Cause: Pattern is associated to the active policies - {0}.

Action: Pattern is associated to the active policies - {0}.
Level: 1

Type: ERROR

Impact: Process

OAAM-65001: No policy set found.

Cause: No policy set found.

Action: No policy set found.
Level: 1

Type: ERROR

Impact: Process

OAAM-65002: The scoring type value {0} is invalid.

Cause: The scoring type value {0} is invalid.

Action: The scoring type value {0} is invalid.
Level: 1

Type: ERROR

Impact: Process

OAAM-65003: Action override with Block ID {0} does not exist.

Cause: Action override with Block ID {0} does not exist.

Action: Action override with Block ID {0} does not exist.
Level: 1

Type: ERROR

Impact: Process

OAAM-65004: Score action with Score Action ID {0} does not exist.

Cause: Score action with Score Action ID {0} does not exist.

Action: Score action with Score Action ID {0} does not exist.
Level: 1

Type: ERROR

Impact: Process

OAAM-65005: Score Action ID cannot be null.

Cause: Score Action ID cannot be null.

Action: Score Action ID cannot be null.
Level: 1

Type: ERROR

Impact: Process

OAAM-65006: Action Override ID cannot be null.

Cause: Action Override ID cannot be null.

Action: Action Override ID cannot be null.
Level: 1

Type: ERROR

Impact: Process

OAAM-65007: There is more than one action override with the Checkpoint-From Action values {0}.

Cause: There is more than one action override with the Checkpoint-From Action values {0}.

Action: There is more than one action override with the Checkpoint-From Action values {0}.
Level: 1

Type: ERROR

Impact: Process

OAAM-65008: For checkpoint {0}, the score override range {1} overlaps with the score override range {2}.

Cause: For checkpoint {0}, the score override range {1} overlaps with the score override range {2}.

Action: For checkpoint {0}, the score override range {1} overlaps with the score override range {2}.
Level: 1

Type: ERROR

Impact: Process

OAAM-65009: From Action and To Action are the same for checkpoint {0}.

Cause: From Action and To Action are the same for checkpoint {0}.

Action: From Action and To Action are the same for checkpoint {0}.
Level: 1

Type: ERROR

Impact: Process

OAAM-65010: Action Group required.

Cause: Action Group required.

Action: Action Group required.
Level: 1

Type: ERROR

Impact: Process

OAAM-65011: To Action required.

Cause: To Action required.

Action: To Action required.
Level: 1

Type: ERROR

Impact: Process

OAAM-70001: Question {0} cannot be deleted because it is linked to the user.

Cause: Question {0} cannot be deleted because it is linked to the user.

Action: Either unlink the user from this question or delete some other question.
Level: 1

Type: ERROR

Impact: Process

OAAM-70002: Selected Question ID cannot be updated to the given status.

Cause: Selected Question ID cannot be updated to the given status.

Action: Selected Question ID cannot be updated to the given status. Select a different question.
Level: 1

Type: ERROR

Impact: Process

OAAM-70003: IDs in the list cannot be null or empty.

Cause: IDs in the list cannot be null or empty.

Action: Provide a Valid ID list.
Level: 1

Type: ERROR

Impact: Process

OAAM-70004: Invalid status.

Cause: Invalid status.

Action: Provide a valid status: Active or Disabled.
Level: 1

Type: ERROR

Impact: Process

OAAM-70005: Invalid and non-existent Question ID.

Cause: Invalid and non-existent Question ID.

Action: Provide a valid and existent Question ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-70006: Question ID should not be null.

Cause: Question ID should not be null.

Action: Provide a valid Question ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-70007: Question name {0} already exist. Provide a unique question name.

Cause: Question name {0} already exist. Provide a unique question name.

Action: Provide a valid and unique question name.
Level: 1

Type: ERROR

Impact: Process

OAAM-70008: Category cannot be deleted because users have registered questions from this category.

Cause: Category cannot be deleted because users have registered questions from this category.

Action: Category cannot be deleted because users have registered questions from this category.
Level: 1

Type: ERROR

Impact: Process

OAAM-70009: Invalid category.

Cause: Invalid Category ID.

Action: Provide a valid Category ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-70010: Category cannot be null.

Cause: Category cannot be null.

Action: Provide a valid and non-null category.
Level: 1

Type: ERROR

Impact: Process

OAAM-70011: Name cannot be empty or null.

Cause: Name cannot be empty or null.

Action: Provide a valid and non-null name.
Level: 1

Type: ERROR

Impact: Process

OAAM-70012: Invalid or empty category name.

Cause: Invalid or empty category name.

Action: Provide a valid and non-null category name.
Level: 1

Type: ERROR

Impact: Process

OAAM-70013: Validation name {0} already exist. Provide a unique validation name.

Cause: Validation name {0} already exist. Provide a unique validation name.

Action: Provide a valid and unique validation name.
Level: 1

Type: ERROR

Impact: Process

OAAM-70014: Validation cannot be null.

Cause: Validation cannot be null.

Action: Provide a valid and non-null validation.
Level: 1

Type: ERROR

Impact: Process

OAAM-70015: Invalid Validation ID.

Cause: Invalid Validation ID.

Action: Provide a valid Validation ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-70016: Validations {0} are used in the KBA configuration and cannot be deleted.

Cause: Validations are linked and cannot be deleted.

Action: Select only the unlinked validations for deleting.
Level: 1

Type: ERROR

Impact: Process

OAAM-70017: Validation ID {0} is invalid and cannot be deleted.

Cause: Validation ID is invalid and cannot be deleted.

Action: Provide a valid and existent Validation ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-70018: Validation {0} has already been added as global validation.

Cause: Validation will not be added again as a global validation.

Action: Select a new Validation that is not part of the Global Validation list.
Level: 1

Type: ERROR

Impact: Process

OAAM-70019: Validation ID is not in the Global Validation list.

Cause: Validation ID is not found in the Global Validation list.

Action: Select a Validation ID which is part of the Global Validation list.
Level: 1

Type: ERROR

Impact: Process

OAAM-70020: No validation available in Global Validation list for delete.

Cause: No validation available in Global Validation list for delete.

Action: No validation available in Global Validation list for delete.
Level: 1

Type: ERROR

Impact: Process

OAAM-70021: Configuration value {0} is not a positive number.

Cause: Configuration value should be a positive number.

Action: Provide a positive number for the configuration value.
Level: 1

Type: ERROR

Impact: Process

OAAM-70022: Configuration value {0} cannot exceed the category count.

Cause: Configuration value cannot exceed the category count.

Action: Provide the configuration value within the allowed category count.
Level: 1

Type: ERROR

Impact: Process

OAAM-70023: No validation available in Global Validation list for delete.

Cause: No validation available in Global Validation list for delete.

Action: No validation available in Global Validation list for delete.
Level: 1

Type: ERROR

Impact: Process

OAAM-70024: Insufficient questions in the system for configuring {0} questions for each user with {1} questions per menu.

Cause: There are not enough questions in the system for each user to register for the number of questions per menu.

Action: Import/create more questions so that the number of questions that user needs to register multiplied by the questions per menu is less than the total number of questions available.
Level: 1

Type: ERROR

Impact: Process

OAAM-70025: Too few questions are being configured for users. Try to register at least {0} questions for the user.

Cause: You have tried to set the number of questions too low. This can lead to security vulnerability.

Action: For the best mix of security and usability, register at least three and at most five or so questions. These settings are dependent on your particular system implementation.
Level: 1

Type: ERROR

Impact: Process

OAAM-70026: Too many questions are being configured for users. Try to register at most {0} questions for user.

Cause: You have tried to set the number of questions too high. This can lead to usability issues.

Action: For the best mix of security and usability, register at least three and at most five questions. These settings are dependent on your particular system implementation.
Level: 1

Type: ERROR

Impact: Process

OAAM-70027: Selected category {0} cannot be updated to the given status.

Cause: Selected category {0} cannot be updated to the given status.

Action: Selected category {0} cannot be updated to the given status. Select a different category.
Level: 1

Type: ERROR

Impact: Process

OAAM-70028: Categories' status cannot be updated. This will lead to too few active categories.

Cause: Categories cannot be updated. This will result in very few categories being available for the registration logic.

Action: Make sure registration logic and available active categories are consistent with this change. One way to do this will be update the registration logic first and then try this operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-70029: Categories cannot be deleted. This will lead to too few active categories.

Cause: Categories cannot be deleted. This will result in very few categories being available for the registration logic.

Action: Make sure registration logic and available active categories are consistent with this change. One way to do this will be update the registration logic first and then try this operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-70030: Category name {0} already exist. Provide a unique category name.

Cause: Category name {0} already exist. Provide a unique category name.

Action: Provide a valid and unique category name.
Level: 1

Type: ERROR

Impact: Process

OAAM-70031: Failed to deactivate selected Categories.

Cause: Failed to deactivate selected Categories. When category is deactivated the questions belonging to that category are also impacted. Some questions cannot be updated to the given status.

Action: Make sure that the questions in selected categories can be updated to the given status.
Level: 1

Type: ERROR

Impact: Process

OAAM-70032: Failed to delete the selected groups. One or more of the groups are in use.

Cause: Failed to delete the selected groups. One or more of the groups are in use.

Action: Remove the usages of the group and delete it.
Level: 1

Type: ERROR

Impact: Process

OAAM-70033: Validation search query cannot be null.

Cause: Validation search query object passed is null.

Action: Make sure to pass non-null search query object.
Level: 1

Type: ERROR

Impact: Process

OAAM-70034: Validations marked for deletion {0} are also used being as global validations.

Cause: Validations marked for deletion are also used being as global validation.

Action: Manage global validations from Registration Logic page.
Level: 1

Type: ERROR

Impact: Process

OAAM-70035: Validation list for delete operation contains null value(s).

Cause: One or more of the validation IDs sent for deletion contain null values.

Action: Make sure no null values are sent in validation ID lists.
Level: 1

Type: ERROR

Impact: Process

OAAM-70036: Question {0} does not exist. It may have been deleted.

Cause: Question {0} does not exist. It may have been deleted.

Action: Question {0} does not exist.
Level: 1

Type: ERROR

Impact: Process

OAAM-70501: User ID cannot be null

Cause: User ID cannot be null

Action: User ID cannot be null
Level: 1

Type: ERROR

Impact: Process

OAAM-70502: User with User ID, {0}, does not exist

Cause: User with User ID, {0}, does not exist

Action: User with User ID, {0}, does not exist
Level: 1

Type: ERROR

Impact: Process

OAAM-70601: IP Address cannot be null

Cause: IP Address cannot be null

Action: IP Address cannot be null
Level: 1

Type: ERROR

Impact: Process

OAAM-70701: Device ID cannot be null

Cause: Device ID cannot be null

Action: Device ID cannot be null
Level: 1

Type: ERROR

Impact: Process

OAAM-70702: Device with Device ID, {0}, does not exist

Cause: Device with Device ID, {0}, does not exist

Action: Device with Device ID, {0}, does not exist
Level: 1

Type: ERROR

Impact: Process

OAAM-70801: Finger Print ID cannot be null

Cause: Finger Print ID cannot be null

Action: Finger Print ID cannot be null
Level: 1

Type: ERROR

Impact: Process

OAAM-70802: Finger Print with Finger Print ID, {0}, does not exist

Cause: Finger Print with Finger Print ID, {0}, does not exist

Action: Finger Print with Finger Print ID, {0}, does not exist
Level: 1

Type: ERROR

Impact: Process

OAAM-70901: Alert ID cannot be null

Cause: Alert ID cannot be null

Action: Alert ID cannot be null
Level: 1

Type: ERROR

Impact: Process

OAAM-70902: Alert with Alert ID, {0}, does not exist

Cause: Alert with Alert ID, {0}, does not exist

Action: Alert with Alert ID, {0}, does not exist
Level: 1

Type: ERROR

Impact: Process

OAAM-80001: Invalid IP address value {0}

Cause: Invalid IP address {0}. Validation failed.

Action: Enter a valid IP address; the value {0} is invalid
Level: 1

Type: ERROR

Impact: Process

OAAM-90001: Task name {0} already exist. Provide a unique task name.

Cause: Task name {0} already exist. Provide a unique task name.

Action: Provide a valid and unique task name.
Level: 1

Type: ERROR

Impact: Process

OAAM-90002: Task type {0} not found. Provide an existing task type.

Cause: Task type {0} not found. Provide an existing task type.

Action: Provide a valid and existing task type.
Level: 1

Type: ERROR

Impact: Process

OAAM-90003: Task status {0} not found. Provide an existing task status.

Cause: Task status {0} not found. Provide an existing task status.

Action: Provide a valid and existing task status.
Level: 1

Type: ERROR

Impact: Process

OAAM-90004: Task name {0} is not apha numeric. Provide an apha numeric task name.

Cause: Task name {0} is not apha numeric. Provide an apha numerictask name.

Action: Provide a valid and alpha numeric task name.
Level: 1

Type: ERROR

Impact: Process

OAAM-90005: Task priority {0} not found. Provide an existing task priority.

Cause: Task priority {0} not found. Provide an existing task priority.

Action: Provide a valid and existing task priority.
Level: 1

Type: ERROR

Impact: Process

OAAM-90006: Schedule type {0} is invalid. Type has to be either onetime or recurring.

Cause: Schedule type {0} is invalid. Type has to be either onetime or recurring.

Action: Provide a valid Schedule type and should be either onetime or recurring.
Level: 1

Type: ERROR

Impact: Process

OAAM-90007: Cancel duration type {0} not found. Provide an existing duration type.

Cause: Cancel duration type {0} not found. Provide an existing duration type.

Action: Provide a valid and existing duration type.
Level: 1

Type: ERROR

Impact: Process

OAAM-90008: Cancel duration unit {0} not found. Provide an existing duration unit.

Cause: Cancel duration unit {0} not found. Provide an existing duration unit.

Action: Provide a valid and existing duration unit.
Level: 1

Type: ERROR

Impact: Process

OAAM-90009: Start date is required for schedule.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Process

OAAM-90010: Start time is required for schedule.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Process

OAAM-90011: Recurrence type {0} not found. Provide an existing Recurrence type.

Cause: Recurrence type {0} not found. Provide an existing Recurrence type.

Action: Provide a valid and existing Recurrence type.
Level: 1

Type: ERROR

Impact: Process

OAAM-90012: Cutoff time {0} is invalid. Provide a value in the existing range.

Cause: Cutoff time {0} is invalid. Provide a value in the existing range.

Action: Provide a valid value in the cutoff time range.
Level: 1

Type: ERROR

Impact: Process

OAAM-90013: Custom loader {0} is invalid. Provide a valid custom loader.

Cause: Custom loader {0} is invalid. Provide a valid custom loader.

Action: Provide a valid custom loader.
Level: 1

Type: ERROR

Impact: Process

OAAM-90014: Custom run {0} is invalid. Provide a valid custom run.

Cause: Custom run {0} is invalid. Provide a valid custom run.

Action: Provide a valid custom run.
Level: 1

Type: ERROR

Impact: Process

OAAM-90015: From date is required for data filters.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Process

OAAM-90016: To time is required for data filters.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Process

OAAM-90017: From date should be before To date for data filters.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Process

OAAM-90018: Schedule cannot be null.

Cause: Schedule was not selected.

Action: Select a Schedule, and try again.
Level: 1

Type: ERROR

Impact: Process

OAAM-90019: Rollup unit {0} not found. Provide an existing rollup unit.

Cause: User specified an invalid rollup unit.

Action: Provide a valid and existing rollup unit.
Level: 1

Type: ERROR

Impact: Process

OAAM-90020: Job name cannot be null.

Cause: User did not specify a job name.

Action: Provide a job name.
Level: 1

Type: ERROR

Impact: Process

OAAM-92000: Job Instance ID's are required.

Cause: No Job Instances were selected.

Action: Select one or more Job Instances, and try again.
Level: 1

Type: ERROR

Impact: Process

OAAM-92001: Job Instance ID's cannot be null.

Cause: Job Instance was not selected.

Action: Select one or more Job Instances, and try again.
Level: 1

Type: ERROR

Impact: Process

OAAM-92002: Job Instance with Job instance ID {0}, does not exist.

Cause: Invalid Job Instance ID {0} was selected. It may have been deleted.

Action: Refresh the list of Job Instances, then select one or more valid Job Instances and try again.
Level: 1

Type: ERROR

Impact: Process

OAAM-92100: Job Instance named "{0}" cannot be paused. Current status is "{1}".

Cause: Job Instances in "{1}" status cannot be paused.

Action: Select another action.
Level: 1

Type: ERROR

Impact: Process

OAAM-92101: Job Instance named "{0}" cannot be resumed. Current status is "{1}".

Cause: Job Instances in "{1}" status cannot be resumed.

Action: Select another action.
Level: 1

Type: ERROR

Impact: Process

OAAM-92102: Job Instance named "{0}" cannot be canceled. Current status is "{1}".

Cause: Job Instances in "{1}" status cannot be canceled.

Action: Select another action.
Level: 1

Type: ERROR

Impact: Process

OAAM-93000: Job ID's are required.

Cause: No Job were selected.

Action: Select one or more Jobs, and try again.
Level: 1

Type: ERROR

Impact: Process

OAAM-93001: Job ID cannot be null.

Cause: Job was not selected.

Action: Select one or more Job, and try again.
Level: 1

Type: ERROR

Impact: Process

OAAM-93002: Job with Job ID {0}, does not exist.

Cause: Invalid Job ID {0} was selected. It may have been deleted.

Action: Refresh the list of Jobs, then select one or more valid Jobs and try again.
Level: 1

Type: ERROR

Impact: Process

OAAM-93003: Job named "{0}" cannot be processed now.

Cause: There exists Job of same type in Running status.

Action: Try after some time.
Level: 1

Type: ERROR

Impact: Process

OAAM-93100: Job named "{0}" cannot be enabled. Current status is "{1}".

Cause: Job in "{1}" status cannot be enabled.

Action: Select another action.
Level: 1

Type: ERROR

Impact: Process

OAAM-93101: Job named "{0}" cannot be disabled. Current status is "{1}".

Cause: Job in "{1}" status cannot be disabled.

Action: Select another action.
Level: 1

Type: ERROR

Impact: Process

OAAM-93102: Job named "{0}" cannot be deleted. Current status is "{1}".

Cause: Job in "{1}" status cannot be deleted.

Action: Select another action.
Level: 1

Type: ERROR

Impact: Process

OAAM-93103: Job with Job Name {0} cannot be deleted. The job has already Run.

Cause: Job {0} cannot be deleted.

Action: Try disabling the job instead of deleting.
Level: 1

Type: ERROR

Impact: Process

OAAM-94100: Job cannot be null.

Cause: Job was not selected.

Action: Select a Job, and try again.
Level: 1

Type: ERROR

Impact: Process

60 OAMAP-60501 to OAMAP-60521

OAMAP-60501: The Access Server entry was not specified in the required format: host:port

Cause: One or more Oracle Access Manager Access Server entries were not specified correctly.

Action: Contact your Oracle Access Manager administrator to ensure that Access Server entries are specified with host:port format. host is the DNS host name of the computer where the Access Server is installed and port is the Access Server port number.
Level: 1

Type: ERROR

Impact: Configuration

OAMAP-60502: No CallbackHandler was supplied to the Identity Asserter/Authenticator.

Cause: No CallbackHandler was found during Identity Asserter/Authenticator initialization.

Action: Contact your Oracle single sign-on administrator with exception/error information.
Level: 1

Type: ERROR

Impact: Internal Error

OAMAP-60503: A required callback was not found.

Cause: A required callback was not found by the Identity Authenticator.

Action: Contact your Oracle single sign-on administrator with exception/error information.
Level: 1

Type: ERROR

Impact: Internal Error

OAMAP-60504: Unable to read user input from the CallbackHandler.

Cause: The Identity Authenticator failed to read user input from the CallbackHandler.

Action: Ensure that you have entered the appropriate credentials.
Level: 1

Type: ERROR

Impact: Data

OAMAP-60505: Found an unsupported token type.

Cause: The Identity Asserter was invoked with an unsupported token type.

Action: Contact your Oracle single sign-on administrator with exception/error information.
Level: 1

Type: ERROR

Impact: Internal Error

OAMAP-60506: Found an unsupported token class.

Cause: The Identity Asserter received an unknown token class "{0}". Expected: a byte[].

Action: Contact your Oracle single sign-on administrator with exception/error information.
Level: 1

Type: ERROR

Impact: Internal Error

OAMAP-60507: Found an invalid SSO Token.

Cause: The Identity Asserter received an SSO token with no characters.

Action: Contact your Oracle single sign-on administrator with exception/error information.
Level: 1

Type: ERROR

Impact: Data

OAMAP-60508: Authentication failed. An invalid ObSSOCookie was found.

Cause: An invalid ObSSOCookie was received.

Action: Contact your Oracle Access Manager administrator to ensure that the ObSSOCookie is not corrupted or timedout before it is passed to the Identity Asserter.
Level: 1

Type: ERROR

Impact: Data

OAMAP-60509: The Identity Authenticator does not support NameCallback.

Cause: NameCallback was not found in the callback array.

Action: Contact your Oracle single sign-on administrator with exception/error information.
Level: 1

Type: ERROR

Impact: Internal Error

OAMAP-60510: The Identity Authenticator does not support PasswordCallback.

Cause: PasswordCallback was not found in the callback array.

Action: Contact your Oracle single sign-on administrator with exception/error information.
Level: 1

Type: ERROR

Impact: Internal Error

OAMAP-60511: Resource "{0}" is not protected by an Oracle Access Manager policy domain.

Cause: The Identity Asserter/Authenticator detected that resource "{0}" is not protected by an Oracle Access Manager policy domain.

Action: Contact your Oracle Access Manager administrator to ensure that the Resource type, Resource Name, and Resource operations are specified correctly for identity assertion, and that the resource specified by the Resource Name is protected by an Oracle Access Manager policy domain and access policies.
Level: 1

Type: ERROR

Impact: Configuration

OAMAP-60512: Unable to get the user name from Return Actions configured in the Oracle Access Manager policy domain.

Cause: The Identity Asserter/Authenticator didn't get any Return Action named uid from the Access Server.

Action: Contact your Oracle Access Manager administrator to ensure that the Return Action in the Oracle Access Manager policy domain is configured correctly to return the user's login name.
Level: 1

Type: ERROR

Impact: Configuration

OAMAP-60513: Required parameters are not configured for the Identity Asserter/Authenticator.

Cause: The Identity Asserter/Authenticator did not find one or more required parameters.

Action: Contact your Oracle Access Manager administrator to ensure that the AccessGate Name, AccessGate Password, Primary/Secondary Access Server Name parameters are specified correctly in the Access System Console.
Level: 1

Type: ERROR

Impact: Configuration

OAMAP-60514: Unable to get the user name.

Cause: No user name was found in NameCallback.

Action: Specify a user name when asked during the authentication challenge.
Level: 1

Type: ERROR

Impact: Data

OAMAP-60515: The AccessGate Name is not recognized by the Access Server.

Cause: An incorrect AccessGate name was found.

Action: Contact your Oracle Access Manager administrator to ensure that the AccessGate name configured for the Identity Asserter/Authenticator exists in a profile in the Access System Console.
Level: 1

Type: ERROR

Impact: Configuration

OAMAP-60516: Unable to create the AccessGate entry for identity assertion/authentication.

Cause: AccessGate instance creation failed.

Action: See the Identity Asserter/Authenticator log for details.
Level: 1

Type: ERROR

Impact: Configuration

OAMAP-60517: Failed to validate the SSO Token.

Cause: The Identity Asserter failed to validate the SSO token.

Action: See the Identity Asserter log for details.
Level: 1

Type: ERROR

Impact: Data

OAMAP-60518: Authentication failed.

Cause: The user could not be authenticated with the provided credentials.

Action: See the Identity Authenticator log for details.
Level: 1

Type: ERROR

Impact: Data

OAMAP-60519: Cannot find the SSO Token in the callback.

Cause: The SSO Token was not found in the CallbackHandler.

Action: Contact your Oracle single sign-on administrator with exception/error information.
Level: 1

Type: ERROR

Impact: Internal Error.

OAMAP-60520: Cannot get a logger instance.

Cause: Cannot create a logger instance.

Action: Contact your Oracle single sign-on administrator with exception/error information.
Level: 1

Type: ERROR

Impact: Internal Error.

OAMAP-60521: Found an invalid value for parameter "{0}".

Cause: The Identity Asserter/Authenticator parameter value contains a whitespace.

Action: Ensure that the value for Identity Asserter/Authenticator parameter doesn't contain any whitespaces.
Level: 1

Type: ERROR

Impact: Config

61 OAM-00001 to OAM-36105

OAM-00001: Cannot parse the session token.

Cause: The session token appears to be invalid.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-00002: Error occurred while handling the request.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-00003: Request-Response handler configuration is incomplete.

Cause: A request handler mapping was missing.

Action: Add the missing handler mapping to the configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-00004: Cannot initialize the Diagnostic Engine.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-00005: Cannot locate the custom login page.

Cause: The custom login page was not found.

Action: Verify the configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-00006: Cannot locate the configuration of the custom login page.

Cause: The custom custom login page was not specified in the configuration.

Action: Add the custom login page location to the configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-00007: Cannot edit the custom login page

Cause: The file permissions of the custom login page do not allow write access.

Action: Change the file permissions to allow write access.
Level: 15

Type: ERROR

Impact: Other

OAM-00008: Cannot close the custom login page

Cause: The source code of the custom login page does not support closing of the login page.

Action: Check the custom login page source code.
Level: 15

Type: ERROR

Impact: Other

OAM-00009: Unable to parse the redirection URL

Cause: An error occurred while parsing the redirect URL due to bad encoding or invalid format.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-000010: Cannot add query params to map for logout redirection

Cause: URLDecoder throwing UnsupportedEncodingException

Action: Check the AMLogoutResponseHandler - getQueryMap method code.
Level: 15

Type: ERROR

Impact: Other

OAM-000011: Cannot parse the request token sent from client with User Agent {0} and IP Address {1}.

Cause: The request token appears to be invalid.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-000012: Cannot construct the request token.

Cause: Could not create OAM request token.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-000013: Cannot construct OAM session token.

Cause: Could not create SSO Session token.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-000014: {0} set in {1} must be an integer greater-than or equal to zero.

Cause: SwitchGetToPostLimit was set incorrectly for the authentications scheme.

Action: Correct the SwitchGetToPostLimit challenge parameter within the authentication scheme.
Level: 15

Type: WARNING

Impact: Other

OAM-02001: Retrieve SSO session operation failed.

Cause: Cannot retrieve the SSO session from the request context. Session might have expired.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-02002: Error while processing the submitted credentials.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-02003: Error while processing credential collection.

Cause: An internal error occurred.

Action: Check the authentication scheme configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-02004: Error while processing authorization request.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-02005: Error while parsing the SSO session token.

Cause: Error while parsing the SSO session token. Wrong session token format.

Action: Retry. If the error persists verify the key roll-over configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-02006: Insufficient authentication level to access the resource.

Cause: An insufficient authentication level was used to access the resource.

Action: Step up the authentication level by re-authenticating to the required level.
Level: 15

Type: ERROR

Impact: Other

OAM-02007: Insufficient privileges. Authorization Denied.

Cause: Insufficient privileges.

Action: Check the authorization permissions.
Level: 15

Type: ERROR

Impact: Other

OAM-02008: Password expired. Authentication failed.

Cause: Insufficient privileges.

Action: Check the authorization permissions.
Level: 15

Type: ERROR

Impact: Other

OAM-02009: Password reset required. Authentication failed.

Cause: Insufficient privileges.

Action: Check the authorization permissions.
Level: 15

Type: ERROR

Impact: Other

OAM-02010: User account is locked. Authentication failed.

Cause: Insufficient privileges.

Action: Check the authorization permissions.
Level: 15

Type: ERROR

Impact: Other

OAM-02011: No user account found. Authentication failed.

Cause: Insufficient privileges.

Action: Check the authorization permissions.
Level: 15

Type: ERROR

Impact: Other

OAM-02012: No user name password combination found. Authentication failed.

Cause: Insufficient privileges.

Action: Check the authorization permissions.
Level: 15

Type: ERROR

Impact: Other

OAM-02013: Password Policy action not supported by the client. Authentication failed.

Cause: Insufficient privileges.

Action: Check the authorization permissions.
Level: 15

Type: ERROR

Impact: Other

OAM-02052: SME Adapter initialization Failed.

Cause: SME adapter initialization failed.

Action: Verify the SME configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-02053: Component {1} initialization Failed.

Cause: Component initialization failed.

Action: Verify the server configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-02054: SSO session creation failed.

Cause: Session Management Engine error.

Action: Check Session Management Engine error logs.
Level: 15

Type: ERROR

Impact: Other

OAM-02055: Retrieve SSO session operation failed.

Cause: Session might be expired.

Action: If the problem persists contact the administrator.
Level: 15

Type: ERROR

Impact: Other

OAM-02056: An error occurred while parsing the server token.

Cause: TPE token parsing failed.

Action: check Token Processing Engine logs.
Level: 15

Type: ERROR

Impact: Other

OAM-02057: Wrong Flow Controller configuration for {1}

Cause: Wrong Flow controller configuration

Action: Check flow controller class name and configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-02058: Event Flow goes in infinite loop.

Cause: Wrong configuration or too many allowed login attempts.

Action: Check event flow configuration and login attempt configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-02059: Flow Controller Cannot handle Event

Cause: Wrong Flow controller configuration

Action: Check error log more details.
Level: 15

Type: ERROR

Impact: Other

OAM-02060: Flow Controller :{0} Cannot handle Event :{1}

Cause: Wrong Flow controller configuration

Action: Check event to flow controller mapping.
Level: 15

Type: ERROR

Impact: Other

OAM-02061: Event Handler error.

Cause: Wrong event handler configuration

Action: Check error log more details.
Level: 15

Type: ERROR

Impact: Other

OAM-02062: Event Handler cannot handle the event.

Cause: Wrong event handler configuration

Action: Check event to event handler controller mapping.
Level: 15

Type: ERROR

Impact: Other

OAM-02063: Event Handler :{0} Cannot handle Event :{1}

Cause: Wrong event handler configuration

Action: Check event to event handler controller mapping.
Level: 15

Type: ERROR

Impact: Other

OAM-02064: Authentication Error during policy matching.

Cause: Authentication Error

Action: Check error log more details.
Level: 15

Type: ERROR

Impact: Other

OAM-02065: Configuration Service Adapter initialization Failed.

Cause: SConfiguration Service failed.

Action: Verify the system configuration file
Level: 15

Type: ERROR

Impact: Other

OAM-02066: Event Factory is not configured create the requested event.

Cause: Wrong event factory configuration

Action: Check error log more details.
Level: 15

Type: ERROR

Impact: Other

OAM-02067: Wrong event configuration. No event handler specified for event {0}.

Cause: Wrong event factory configuration

Action: Check error log more details.
Level: 15

Type: ERROR

Impact: Other

OAM-02068: Error occurred while configuring the request cache.

Cause: Wrong request cache handler class configuration.

Action: Check error log more details.
Level: 15

Type: ERROR

Impact: Other

OAM-02069: Error occurred while loading cache handler for class Name {0}

Cause: Wrong request cache handler class configuration.

Action: Check error log more details.
Level: 15

Type: ERROR

Impact: Other

OAM-02070: An error occurred while loading server aliases.

Cause: TPE token parsing failed.

Action: check system configuration if the aliases are set up properly logs.
Level: 15

Type: ERROR

Impact: Other

OAM-02071: No host configuration found for the alias {0}.

Cause: TPE token parsing failed.

Action: check system configuration if the aliases are set up properly logs.
Level: 15

Type: ERROR

Impact: Other

OAM-02072: Ignoring failure during Identity Store operation.

Cause: Operation to read or update user attribute in Identity Store resulted in exception.

Action: Check the availability of configured Identity Store.
Level: 15

Type: WARNING

Impact: Other

OAM-02073: Error while checking if the resource is protected or not.

Cause: TPE token parsing failed.

Action: check system configuration if the aliases are set up properly logs.
Level: 15

Type: ERROR

Impact: Other

OAM-02074: Error while checking if the resource {0} is protected or not.

Cause: TPE token parsing failed.

Action: check system configuration if the aliases are set up properly logs.
Level: 15

Type: ERROR

Impact: Other

OAM-02075: Component {0} initialized successfully.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-02076: {0} Engine initialized successfully.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-02077: SSO Engine initialized Successfully.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-02078: Processing Event {0}

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-02079: SSO session created with session ID {0} for request ({1})

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-02080: Cache data sync:{0} for request {1};

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-02081: Created {0} : {1}

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-02082: Diagnostic Engine Registration failed for Controller Collector.

Cause: Diagnostic Engine Registration failed.

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-02083: Diagnostic Engine Registration failed for Credential Collector Controller.

Cause: Diagnostic Engine Registration failed.

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-02084: Credential collection process success.

Cause:

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-02085: Successfully validated the submitted credentials.

Cause:

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-02086: {0}: processing Event:{1}.

Cause:

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-02087: Policy ID : {0}

Cause:

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-02088: Scheme result : {0}

Cause:

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-02089: Is Resource Protected status : {0}

Cause:

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-02090: Status : {0}

Cause:

Action: None
Level: 15

Type: ERROR

Impact: Other

OAM-02091: Challenge URL : {0}

Cause:

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-02092: Session Updation Failed

Cause:

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-02093: Session response name {0} is reserved for OAM Server. Value for this response will not be updated in session.

Cause: A session response is configured with name that is internally reserved for OAM Server

Action: Please change the name of the session response not to conflict with OAM Server reserved names
Level: 15

Type: WARNING

Impact: Other

OAM-02094: Assert credential process success.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-02095: Assert credential process failed.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-02096: An error occurred while building the DAP token {0}.

Cause: Constructing the outgoing DAP token failed.

Action: Check the key and parameters in token.
Level: 15

Type: ERROR

Impact: Other

OAM-02097: An error occurred while decrypting the DAP token {0}.

Cause: Decrypting the incoming DAP token failed.

Action: Check the key configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-02098: Cannot parse the DAP token.

Cause: Error occured while parsing the token.

Action: Check the configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-02099: {0}: Event processing finished :{1} with status {2}.

Cause:

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-02100: User account is disabled. Authentication failed.

Cause: Insufficient privileges.

Action: Check the authorization permissions.
Level: 15

Type: ERROR

Impact: Other

OAM-02101: An error occurred while creating impersonation session

Cause: Impersonation session creation failed

Action: Check the create impersonation session event
Level: 15

Type: ERROR

Impact: Other

OAM-02102: An error occurred in retrieving the grant

Cause: Unable to retrieve the grants

Action: Check the grant permissions
Level: 15

Type: ERROR

Impact: Other

OAM-02103: An error occurred in end impersonate session

Cause: Unable to do end impersonate session

Action: Check the end impersonate session event
Level: 15

Type: ERROR

Impact: Other

OAM-02104: An error occurred while creating subject for impersonatee

Cause: Authentication Exception thrown while creating subject for impersonatee

Action: Check the createSubject method in SSOEngineController
Level: 15

Type: ERROR

Impact: Other

OAM-02105: An error occurred in end impersonate session

Cause: Policy Manager Exception thrown while creating subject for impersonatee

Action: Check the createSubject method in SSOEngineController
Level: 15

Type: ERROR

Impact: Other

OAM-02106: An error occurred while terminating session

Cause: Unable to terminate session

Action: Check the terminate session event
Level: 15

Type: ERROR

Impact: Other

OAM-02107: An error occurred while enumerating session

Cause: Unable to enumerate session

Action: Check the enumerate sessions event
Level: 15

Type: ERROR

Impact: Other

OAM-02108: An error occurred while updating session attributes

Cause: Unable to update session

Action: Check the update session attributes event
Level: 15

Type: ERROR

Impact: Other

OAM-02109: An excluded resource is configured for OSSO agent.

Cause: Excluded resource configured for OSSO agents.

Action: Update the MOD OSSO configuration to include the excluded resource in the public list.
Level: 15

Type: WARNING

Impact: Other

OAM-02110: Event flow controller is executed in infinite loops.

Cause: Wrong configuration.

Action: Check event flow controller configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-04001: Configuration parameter type mismatch. Param {0}. Expected type {1}. Actual type {2}

Cause: The configuration parameter type was invalid.

Action: Validate the configuration parameter.
Level: 16

Type: NOTIFICATION

Impact: Other

OAM-04002: Unsupported value for config parameter. Parameter {0} . Value {1}. {2}

Cause: The specified configuration parameter was not valid.

Action: Validate the configuration parameter.
Level: 16

Type: NOTIFICATION

Impact: Other

OAM-04003: OAM proxy started. Listening on port {0}.

Cause: The OAM proxy has started listening on the specified port.

Action:
Level: 16

Type: NOTIFICATION

Impact: Other

OAM-04004: Read configuration parameter {0} = {1}.

Cause: The OAM proxy has loaded its configuration.

Action:
Level: 16

Type: NOTIFICATION

Impact: Other

OAM-04005: Client connection accepted.

Cause: A client TCP/IP connection was accepted.

Action:
Level: 16

Type: NOTIFICATION

Impact: Other

OAM-04006: Client connection closed. Connection id {0}.

Cause: A client TCP/IP connection was closed.

Action:
Level: 16

Type: NOTIFICATION

Impact: Other

OAM-04007: Message received from client. Message {0}, Host : {1} Port : {2}.

Cause: A message was received from a client on the NAP channel.

Action:
Level: 16

Type: NOTIFICATION

Impact: Other

OAM-04008: Message sent to client. Message {0}, Host : {1} Port : {2}.

Cause: A message was sent to a client on the NAP channel.

Action:
Level: 16

Type: NOTIFICATION

Impact: Other

OAM-04009: New Outbound connection created with OAM Access Server.

Cause: An outbound connection was created with an OAM 10g server.

Action:
Level: 16

Type: NOTIFICATION

Impact: Other

OAM-04010: Message received on outbound channel from OAM Access server. Message {0}, Host : {1} Port : {2}.

Cause: A message was received from an OAM 10g server.

Action:
Level: 16

Type: NOTIFICATION

Impact: Other

OAM-04011: Message sent on outbound channel to OAM 10g Access server. Message {0}, Host : {1} Port : {2}.

Cause: A message was sent to an OAM 10g server.

Action:
Level: 16

Type: NOTIFICATION

Impact: Other

OAM-04012: Outbound connection closed.

Cause: A connection with an OAM 10g server was closed.

Action:
Level: 16

Type: NOTIFICATION

Impact: Other

OAM-04013: Unexpected message received from client. Message {0}

Cause: An unexpected message was received when a simple mode handshake message from the client was expected.

Action: Check the NAP mode configuration of the WebGate and the Server.
Level: 1

Type: WARNING

Impact: Other

OAM-04014: Malformed message received from client. Details {0}

Cause: The length of message received from client was less than 0.

Action: Restart the WebGate if the message is being received repeatedly.
Level: 1

Type: WARNING

Impact: Other

OAM-04015: Outbound connection to Access Server not found.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 1

Type: WARNING

Impact: Other

OAM-04016: Session ID is missing in AmResponse

Cause: The session ID was not present in the OAM token.

Action: Retry the request.
Level: 1

Type: WARNING

Impact: Other

OAM-04017: OAM proxy end point activation failed. Exception:

Cause: The specified listening port is not available, or is aldready being used.

Action: Restart the server or contact the system administrator.
Level: 1

Type: SEVERE

Impact: Other

OAM-04018: Required configuration parameter missing. Required {0}

Cause: The required configuration parameters were missing.

Action: Verify the configuration.
Level: 1

Type: SEVERE

Impact: Other

OAM-04019: Work manager JNDI lookup failed. Exception:

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 1

Type: SEVERE

Impact: Other

OAM-04020: Exception encountered while processing the request message:

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 1

Type: SEVERE

Impact: Other

OAM-04021: NMP initialization failed.

Cause: The NAP handshake with the client failed or an unsupported application was trying to connect to the OAM proxy.

Action: Verify the client version.
Level: 1

Type: SEVERE

Impact: Other

OAM-04022: SSL configuration is not specified for SIMPLE or CERT mode

Cause: The SSL configuration was required but not supplied for the SIMPLE or CERT mode.

Action: Verify the SSL Configuration and rerun the operation.
Level: 1

Type: SEVERE

Impact: Other

OAM-04023: SSL handshake failed. Exception:

Cause: The NAP handshake with a client was not successful.

Action: Check the client configuration.
Level: 1

Type: SEVERE

Impact: Other

OAM-04024: Exception in outbound message processing. Cause {0} . Message details {1}

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 1

Type: SEVERE

Impact: Other

OAM-04025: Error in connecting to Access server. {0}

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 1

Type: SEVERE

Impact: Other

OAM-04026: Error in NAP handshake with AAA server {0}

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 1

Type: SEVERE

Impact: Other

OAM-04027: Cannot create Executor instance

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 1

Type: SEVERE

Impact: Other

OAM-04028: Outbound Resource Adapter initialization error. {0}

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 1

Type: SEVERE

Impact: Other

OAM-04029: Error in generating AMEvent. Details {0}

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 1

Type: SEVERE

Impact: Other

OAM-04030: Partner lookup failed. Partner id {0}

Cause: The retrieval of partner metadata during client authentication was not successful.

Action: Check if the partner is registered with the Access Server.
Level: 1

Type: SEVERE

Impact: Other

OAM-04031: NAP version mismatch during the NAP handshake. Client Message {0}

Cause: An unsupported NAP version was sent by the client.

Action: Check the client configuration and version. Older clients may need to be upgraded.
Level: 1

Type: SEVERE

Impact: Other

OAM-04032: PAT API error. Details {0}

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 1

Type: SEVERE

Impact: Other

OAM-04033: Error in retrieving secret information. {0} {1}

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 1

Type: SEVERE

Impact: Other

OAM-04034: Token Cache Enabled.

Cause: Information message indicating that the token cache is enabled.

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAM-04035: Error while reading token cache size from configuration.

Cause: The cache configuration was invalid.

Action: Fix cache configuration and rerun the operation.
Level: 15

Type: ERROR

Impact: Other

OAM-04036: Channel security mode is different as specified in configuration {0}

Cause: The agent tried to communicate in a mode different from its configuration.

Action: Check the agent mode. This may be a security issue if the configuration mode of agent is correct.
Level: 1

Type: SEVERE

Impact: Other

OAM-04037: Exception encountered while processing the HTTP message in OAM proxy:

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 1

Type: SEVERE

Impact: Other

OAM-04038: OAM proxy configuration parameter SSOOnlyMode is set to true. OAM proxy will skip authorization.

Cause: OAM proxy configuration parameter SSOOnlyMode is set to true.

Action:
Level: 16

Type: NOTIFICATION

Impact: Other

OAM-04039: Agent {0} not privileged to invoke OPCODE {1}

Cause: Agent is not privileged to invoke the operation.

Action: Check the agent configuration.
Level: 1

Type: WARNING

Impact: Other

OAM-04040: Target Resource is not as expected. Target Resource {0} WebGate resource {1}

Cause: Target resource is not as expected. This issue may occur in session scope operations.

Action: Runtime check failure. Check server logs.
Level: 1

Type: WARNING

Impact: Other

OAM-04041: Failed to retrieve valid session from OAM Identity Assertion. Assertion {0}

Cause: Either invalid assertion was specified or session corresponding to assertion is invalid.

Action: Please see logs for more details.
Level: 1

Type: WARNING

Impact: Other

OAM-04042: Failed to check token issuance policy. Resource: {0}. Requestor: {1}

Cause: Evaluation of Token Issuance Policy failed.

Action: Check Token Issuance Policy.
Level: 1

Type: WARNING

Impact: Other

OAM-04043: Request is not processed. Access management service is disabled.

Cause: Access management service is not enabled on server.

Action: Enable the access management service. Set oam proxy global parameter "10gCompatibleGetHostIdentifiersSupport" to true.
Level: 1

Type: WARNING

Impact: Other

OAM-06001: Cannot parse the session token.

Cause: The session token is invalid or the wrong decryption key is present in the configuration.

Action: Verify the key roll-over configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-10001: Cannot load the configuration file.

Cause: The configuration file location was invalid.

Action: Verify the location of the configuration file.
Level: 15

Type: ERROR

Impact: Other

OAM-10002: Cannot initialize the PAT Adapter.

Cause: The PAT configuration was invalid.

Action: Verify the PAT configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-10003: Cannot initialize the Cache Handlers.

Cause: The request cache handler configuration was invalid.

Action: Verify the request cache handler configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-10004: Cannot initialize the Controller.

Cause: The configuration for Controller events was invalid.

Action: Verify the Controller configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-10005: Cannot initialize the Controller.

Cause: The configuration for the Flow controllerd was invalid.

Action: Verify the Controller configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-10006: Cannot initialize the Controller.

Cause: The configuration for the Flow Mapping was invalid.

Action: Verify the Controller configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-10007: Cannot initialize the Controller.

Cause: The configuration for the Event Handlers was invalid.

Action: Verify the Controller configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-10008: Cannot initialize the Controller.

Cause: The configuration for the Event UI was invalid.

Action: Verify the Controller configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-10009: Cannot initialize the Controller.

Cause: The Event Handler configuration was invalid.

Action: Verify the Controller configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-10010: Cannot initialize the Controller.

Cause: The Event Factory configuration was invalid.

Action: Verify the Controller configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-10011: An invalid Cookie Domain

Cause: The cookie domain was invalid.

Action: Verify the configuration file.
Level: 15

Type: ERROR

Impact: Other

OAM-10012: Cannot load audit configuration.

Cause: The audit configuration was invalid.

Action: Verify the audit configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-10013: Cannot load audit configuration.

Cause: Mismatch between logger and resource configuration.

Action: Verify the audit configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-10014: Invalid done URL specified during logout - {0}.

Cause: Done URL specified during logout is not in proper URL format.

Action: Verify the done URL.
Level: 15

Type: ERROR

Impact: Other

OAM-10015: Cache Info :: operation="{0}" paramName="{1}", paramDetail="{2}".

Cause: Displayed when the cache is operating.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

OAM-10016: Cache entry expired.

Cause: Displayed on expiry of the cached element.

Action: None.
Level: 1

Type: NOTIFICATION

Impact: Other

OAM-10017: Cannot intialize the server key.

Cause: Unable to retrieve server key from configuration.

Action: Verify the configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-10018: No credcollect req resp handler specified

Cause: No credcollect req resp handler specified

Action: Verify configuration cred collect req resp handler
Level: 15

Type: ERROR

Impact: Other

OAM-12001: Cannot load audit configuration.

Cause: The specified configuration file does not exist, or the audit configuration is invalid.

Action: Check the server error logs.
Level: 15

Type: ERROR

Impact: Other

OAM-12002: User name value specified for special user is invalid.

Cause: The input value format is invalid, or exceeds 30 characters.

Action: Correct the input value.
Level: 15

Type: ERROR

Impact: Other

OAM-12003: Maximum directory size specified is invalid.

Cause: The input value format is invalid, is less than 1 or exceeds 1024.

Action: Correct the input value.
Level: 15

Type: ERROR

Impact: Other

OAM-12004: Maximum file size specified is invalid.

Cause: The input value format is invalid, is less than 1 or exceeds 1024.

Action: Correct the input value.
Level: 15

Type: ERROR

Impact: Other

OAM-12005: Map of audit events is invalid.

Cause: The audit event configuration is missing, or invalid.

Action: Verify the configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-12006: Invalid path for audit event definitions file.

Cause: The audit event definitions file location is incorrect.

Action: Verify the configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-12007: Invalid path for audit bustop directory.

Cause: The audit bustop location is missing, or invalid.

Action: Verify the configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-12501: Getting ServerTokenMapper for: {0}.

Cause: Getting ServerTokenMapper for {0}

Action: None
Level: 16

Type: NOTIFICATION

Impact: Other

OAM-12502: Server Token Not available in the Response.

Cause: Server Token Not available in the Response.

Action: None
Level: 16

Type: NOTIFICATION

Impact: Other

OAM-12503: 10g SSO_ID Token set {0} .

Cause: 10g SSO_ID Token set.

Action: None
Level: 16

Type: NOTIFICATION

Impact: Other

OAM-12504: 10g SSO_ID Decrypted successfully : {0}

Cause: 10g SSO_ID Decrypted successfully.

Action: None
Level: 16

Type: NOTIFICATION

Impact: Other

OAM-12505: Removing the SSO_ID Cookie at Logout.

Cause: Removing the SSO_ID Cookie at Logout.

Action: None
Level: 16

Type: NOTIFICATION

Impact: Other

OAM-12506: "Creating session token with values - " + "Domain: {0}, Version: {1}, Age: {2}, Secure: {3}, " + "Value: {4}";

Cause: Created Session Token with values

Action: None
Level: 16

Type: NOTIFICATION

Impact: Other

OAM-12507: Token Version not found.

Cause: Token Version not found.

Action: Validate the config to include the Token Version.
Level: 15

Type: ERROR

Impact: Other

OAM-12508: 10g SSO_ID Decryption failed.

Cause: 10g SSO_ID Decryption failed.

Action: Verify if the 10gSSO Server Key is present in the config
Level: 15

Type: ERROR

Impact: Other

OAM-12509: Could not get token mapper for token for {0}.

Cause: Could not get token mapper for token.

Action: Validate the config to include the Token Version.[v1.2, v1.4]
Level: 15

Type: ERROR

Impact: Other

OAM-12510: 10g SSO_ID Token NOT created.

Cause: 10g SSO_ID Token NOT created.

Action: Verify if the 10gSSO Server Key/Token Version is present in the config
Level: 15

Type: ERROR

Impact: Other

OAM-12511: Error while creating SSO Transport token.

Cause: Error while creating Transport Token

Action: Validate the config to check for the 10g SSO Server Key
Level: 15

Type: ERROR

Impact: Other

OAM-12512: Cannot retrieve the 10g SSO Key

Cause: Cannot retrieve the 10g SSO Key

Action: Validate the config to check for the 10g SSO Server Key
Level: 1

Type: SEVERE

Impact: Other

OAM-12513: Diagnostic Engine Failed to Start

Cause: Diagnostic Engine Failed

Action: None
Level: 16

Type: NOTIFICATION

Impact: Other

OAM-12514: Request Handling Error

Cause: Request Handling Error

Action: None
Level: 15

Type: ERROR

Impact: Other

OAM-12515: Session Token Not Found

Cause: Session Token Not Found

Action: None
Level: 15

Type: ERROR

Impact: Other

OAM-12516: 10g SSO Server Config Details Missing

Cause: 10g SSO Server Config Details Missing

Action: Add the Config details to oam-config.xml
Level: 15

Type: ERROR

Impact: Other

OAM-12517: OSSO 10g Server coexist token version configured does not match runtime token version

Cause: 10g SSO Server coexist token version and runtime token versions does not match.

Action: Update the OSSO 10g coexist token version to match the runtime version
Level: 15

Type: ERROR

Impact: Other

OAM-14001: Unregistration of OAM Management MBean failed.

Cause: An internal error occurred.

Action: Check the OAM Server logs.
Level: 15

Type: ERROR

Impact: Other

OAM-14002: OAM Server configuration update failed.

Cause: Failed to update OAM Policy or System Configuration.

Action: Check the OAM Server MBean logs.
Level: 15

Type: ERROR

Impact: Other

OAM-14003: Invalid HostIdentifier configuration for AppDomain {0} in OAM Policy.

Cause: Definition of HostIdentifier for application domain was invalid.

Action: Re-check Application Domain configuration in OAM Policy.
Level: 15

Type: ERROR

Impact: Other

OAM-14005: Validation of a input parameter failed.

Cause: One of the input parameter value was illegal.

Action: Check the OAM Server MBean logs.
Level: 15

Type: ERROR

Impact: Other

OAM-14007: Cannot retrieve OAM Server configuration for {0}.

Cause: Cannot retrieve data from OAM System configuration.

Action: Check the OAM Server MBean logs.
Level: 15

Type: ERROR

Impact: Other

OAM-14008: Partner configuration for {0} already exist in system config.

Cause: A partner is already configured.

Action: Delete existing partner or create partner with a different id.
Level: 15

Type: ERROR

Impact: Other

OAM-14009: Application Domain not found in OAM Policy {0}.

Cause: None

Action: None
Level: 15

Type: ERROR

Impact: Other

OAM-14100: Host Information is already registered in OAM HostIdentifier with host {0} and port {1}.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-14101: Starting Enable OIM Configuration.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-14102: Starting Disable OIM Configuration.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-14103: Completed OAM Server Policy Configuration update.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-14104: Completed OAM Server System Configuration update.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-14105: Completed OIM Configuration.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-14106: Completed validation of Input values.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-14107: Successfully updated OAM Partner data.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-14108: Successfully updated OAM Configuration.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-14109: Enables OIM Integration.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-14110: Disables OIM Integration.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-14111: Registration of OAM Management MBean failed.

Cause: An internal error occurred.

Action: Check the OAM Server logs.
Level: 15

Type: ERROR

Impact: Other

OAM-14112: Gets the manage server host, NAP port.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-14113: Updates OIM host and port.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-14114: Error in getting the OAM server info.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-14115: Create and configure OAM partner.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-16001: Cannot parse the session token.

Cause:

Action:
Level: 15

Type: ERROR

Impact: Other

OAM-18001: User Identity Store Configuration is not valid.

Cause: The user identity store configuration was missing, or was invalid.

Action: Verify the user identity store configuration.
Level: 1

Type: ERROR

Impact: Other

OAM-18002: Error while reading User Identity Store Configuration.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18003: Error while reading User Identity Store Configuration attribute "{0}".

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18004: User Identity Store name passsed as NULL during user identity store read operation.

Cause: User Identity Store name passsed to read operation was null.

Action: Rerun with actual object.
Level: 1

Type: ERROR

Impact: Other

OAM-18005: User Identity Store ID passsed as blank during user identity store read operation.

Cause: User Identity Store ID passsed to read operation was blank.

Action: Rerun with a valid ID.
Level: 1

Type: ERROR

Impact: Other

OAM-18006: Map of Properties passed as NULL during user identity store create operation.

Cause: Map of Properties passed to create operation was null.

Action: Rerun by passing Map of properties.
Level: 1

Type: ERROR

Impact: Other

OAM-18007: Empty Map of Properties passed during user identity store create operation.

Cause: Map of Properties passed to create operation was empty.

Action: Rerun by passing Map of properties.
Level: 1

Type: ERROR

Impact: Other

OAM-18008: NULL passed during user identity store modify operation.

Cause: Object passed to modify operation was null.

Action: Rerun with actual object.
Level: 1

Type: ERROR

Impact: Other

OAM-18009: Validation Failure - an User Identity Store named "{0}" already exists.

Cause: User Identity Store names must be unique.

Action: Choose a different name for this User Identity Store.
Level: 1

Type: ERROR

Impact: Other

OAM-18010: Exception while encrypting the credetial for User Identity Store.

Cause: Exception while encrypting the crendential for User Idenity Store.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18011: Validation Failure - User Identity Store "{0}" is referred in following authentication schemes : "{1}".

Cause: User Identity Store is referred in authentication schemes.

Action: Delete or change the reference of this User Identity Store from the authentication schemes that refer to it.
Level: 1

Type: ERROR

Impact: Other

OAM-18012: Exception while processing the User Identity Store properties.

Cause: An internal error occurred, Unknown type found while processing.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18013: Exception while processing the User Identity Store properties.

Cause: An internal error occurred, type found as NULL while processing.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18014: Validation Failure - NULL Value passed for property "{0}".

Cause: Value found as NULL for a property.

Action: Rerun with the value of property set.
Level: 1

Type: ERROR

Impact: Other

OAM-18015: Server Configuration is not valid.

Cause: The server configuration was missing, or was invalid.

Action: Verify the server configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-18016: Cannot initialize the Data Sources Manager.

Cause: Configuration store instance found null.

Action: For more details, start logging at the FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18017: Cannot initialize the Authentication Modules Manager.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18018: Cannot initialize the Server Manager.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18019: Create : {0} : paramList=[{1}].

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAM-18020: Created : {0} : {1}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAM-18021: Modify : {0} : Existing=[{1}] : New=[{2}].

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAM-18022: Modified to : {0} : {1}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAM-18023: Delete : {0} : name="{1}".

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAM-18024: Deleted : {0} : name="{1}".

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAM-18025: Read : {0} : name="{1}".

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAM-18026: After Read : {0} : {1}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAM-18027: Read All : {0}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAM-18028: After Read All : {0} : list is : {1}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAM-18029: Validation Failure : "{0}" attributes missing in User Identity Store.

Cause: The required attributes were not present in the user identity store.

Action: Add the attributes to the user identity store and rerun the operation.
Level: 1

Type: ERROR

Impact: Other

OAM-18030: Validation Failure : "{0}" attributes missing in OAM Server Instance.

Cause: The required attributes were not specified for the server instance.

Action: Add the attributes to the server instance and rerun the operation.
Level: 1

Type: ERROR

Impact: Other

OAM-18031: Validation Failure : "{0}" attributes missing in {1} Authentication Module.

Cause: The required attributes were not specified for the authentication module.

Action: Add the attributes to the authentication module and rerun the operation.
Level: 1

Type: ERROR

Impact: Other

OAM-18032: Validation Failure - Object not found for deletion.

Cause: The object supplied for deletion has been deleted, or does not exist.

Action: Use the correct data and rerun the operation.
Level: 1

Type: ERROR

Impact: Other

OAM-18033: Validation Failure : {0} Module cannot be deleted. (Referred in Scheme).

Cause: The module was being referred to in a scheme.

Action: Remove the reference from the scheme and then delete the module.
Level: 1

Type: ERROR

Impact: Other

OAM-18034: Authentication module configuration is not valid.

Cause: The authentication module configuration was missing, or was invalid.

Action: Verify the authentication module configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-18035: Validation Failure - a server Instance named "{0}" already exists.

Cause: Same name used for creating a new server instance.

Action:
Level: 15

Type: ERROR

Impact: Other

OAM-18036: OAM Server name passed as NULL during oam server update operation.

Cause: An internal error occurred.

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-18037: OAM Server id passed as NULL during oam server update operation.

Cause: User Identity Store name passed to read operation was null.

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-18038: The response cookie configuration for update is invalid.

Cause: Invalid OSSO Proxy configuration found during configuration update.

Action: Check the parameter passed during OSSO-Proxy configuration update.
Level: 1

Type: ERROR

Impact: Other

OAM-18039: The global response cookie configuration cannot be deleted.

Cause: The global OSSO response cookie configuration delete is not allowed.

Action: Check the parameter passed during OSSO-Proxy configuration update.
Level: 1

Type: ERROR

Impact: Other

OAM-18040: Error while reading {0} Authentication Module Configuration.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18041: Error while reading OAM Server Instance Configuration.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18042: The Unique ID for server is null.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18043: The OAM server is null.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18044: Error while reading {0} OAM Server Instance Configuration.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18045: OAM Server name passsed as NULL during server read operation.

Cause: User Identity Store name passsed to read operation was null.

Action: Rerun with actual object.
Level: 1

Type: ERROR

Impact: Other

OAM-18046: OAM Server ID passsed as blank during server read operation.

Cause: User Identity Store ID passsed to read operation was blank.

Action: Rerun with a valid ID.
Level: 1

Type: ERROR

Impact: Other

OAM-18047: Error while reading Kerberos Authentication Module Configuration.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18048: The Unique Authn module ID is null.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18049: The authn module is null.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18050: Error while reading LDAP Authentication Module Configuration.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18051: Error while reading X509 Authentication Module Configuration.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18052: Error while reading DAP Authentication Module Configuration.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18053: Internal error occurred while reading {0} Authentication module.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18054: An Authentication Module with name {0} already exists, please specify another name.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18055: Internal error occurred while reading OAM Server {0}.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18056: Internal error occurred while reading Load Balancing Settings.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18057: Internal error occurred while updating Load Balancing Settings.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18058: Internal error occurred while reading SSO Engine Settings.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18059: Internal error occurred while updating SSO Engine Settings.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18060: Internal error occurred while reading Coherence Settings.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18061: Internal error occurred while updating Coherence Settings.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18062: Internal error occurred while reading Session Settings.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18063: Internal error occurred while updating Session Settings.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18064: Internal error occurred while reading Access Protocol Settings.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18065: Internal error occurred while updating Access Protocol Settings.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18066: Internal error occurred while reading Policy Settings.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18067: Internal error occurred while updating Policy Settings.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18068: Invalid Orchestration Strategy.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18069: Error saving Custom Authentication Module.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18070: Custom Authentication module is unavailable.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18071: Error deleting Custom Authentication Module.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18072: Custom Authentication module already exists.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18073: The specified ID Store is not a System Store.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18074: Delete operation on System Identity Store is not allowed.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-20001: Deleted application domain {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20002: Duplicated application domain {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20003: Saved authentication scheme {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20004: Deleted authentication scheme {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20005: Duplicated authentication scheme {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20006: Button with id {0} is disabled {1}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20007: Set authentication scheme {0} as the default scheme.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20008: Set {0} as the default authentication scheme.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20009: Saved host identifier {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20010: Deleted host identifier {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20011: Duplicated host identifier{0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20012: Deleted host identifier entry with key {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20013: Saved resource {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20014: Deleted resource {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20015: Duplicated resource {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20016: Saved authentication policy {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20017: Deleted authentication policy {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20018: Duplicated authentication policy {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20019: Saved authorization policy {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20020: Deleted authorization policy {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20021: Duplicated authorization policy {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20022: Saving authentication policy response {0}, {1}, {2}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20023: Saved authentication policy response {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20024: Deleted authentication policy response row with key {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20025: Deleted authentication policy response {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20026: Saved authentication policy resource {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20027: Deleted authentication policy resource with key {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20028: Deleted authentication policy resource {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20029: Saving authorization policy response {0}, {1}, {2}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20030: Saved authorization policy response {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20031: Deleted authorization policy response with key {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20032: Deleted authorization policy response {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20033: Saved authorization policy resource {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20034: Deleted authorization policy resource with key {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20035: Deleted authorization policy resource {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20036: Added {0}:{1}:{2} constraint.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20037: Added constraint {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20038: Saved constraint {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20039: Deleted constraint with key {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20040: Deleted constraint {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20041: Fetching details for master constraint {0}:{1}:{2}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20042: Saved details for temporal constraint {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20043: Cancelled detail changes for temporal constraint {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20044: Saved details for ip4 constraint {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20045: Cancelled detail changes for ip4 constraint {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20046: Saved details for identity constraint {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20047: Cancelled detail changes for identity constraint {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20048: Added {0}:{1} under identity constraint.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20049: Deleted key {0}:{1} under identity constraint.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20050: Deleted {0}:{1} under identity constraint.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20051: Searching for {0}:{1}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20052: Saved component {0}:{1}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20053: Created component {0}:{1}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20054: Duplicated component {0}:{1}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20055: Deleted component {0}:{1}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20056: Recording action:{0}, child node:{1}, appdomain name:{2}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20057: Cancelled application domain {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20058: Cancelled authentication scheme {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20059: Cancelled host identifier {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20060: Cancelled resource {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20061: Cancelled authentication policy {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20062: Cancelled authorization policy {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20063: Successfully saved application domain {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20100: Cannot save application domain {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20101: Cannot delete application domain {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20102: Cannot duplicate application domain{0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20103: Cannot save authentication scheme {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20104: Cannot delete authentication scheme {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20105: Cannot duplicate authentication scheme {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20106: Cannot set {0} as the default authentication scheme.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20107: Cannot save host identifier {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20108: Cannot delete host identifier {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20109: Cannot duplicate host identifier {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20110: Cannot save resource {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20111: Cannot delete resource {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20112: Cannot duplicate resource {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20113: Cannot save authentication policy {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20114: Cannot duplicate authentication policy {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20115: Cannot delete authentication policy {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20116: Cannot save authorization policy {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20117: Cannot duplicate authorization policy {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20118: Cannot delete authorization policy {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20119: Cannot initialize authentication policy response.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20120: Cannot save authentication policy response {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20121: Cannot delete authentication policy response {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20122: Cannot save authentication policy resource {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20123: Cannot delete authentication policy resource {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20124: Cannot initialize authorization policy response.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20125: Cannot save authorization policy response {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20126: Cannot delete authorization policy response {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20127: Cannot save authorization policy resource {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20128: Cannot delete authorization policy resource {0}.

Cause: AuthzPolicyResource delete failed.

Action: AuthzPolicyResource delete failed.
Level: 15

Type: ERROR

Impact: Other

OAM-20129: Cannot save constraint {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20130: Cannot delete constraint {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20131: Cannot save details for temporal constraint {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: INFO

Impact: Other

OAM-20132: Cannot cancel detail changes for temporal constraint {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: INFO

Impact: Other

OAM-20133: Cannot save details for ip4 constraint {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: INFO

Impact: Other

OAM-20134: Cannot cancel detail changes for ip4 constraint {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: INFO

Impact: Other

OAM-20135: Cannot save details for identity constraint {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: INFO

Impact: Other

OAM-20136: Cannot cancel detail changes for identity constraint {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 1

Type: INFO

Impact: Other

OAM-20137: Cannot save details for identity constraint {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20138: Cannot delete details under identity constraint {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20139: Error occurred while searching for {0}:{1}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20140: Cannot save component {0}:{1}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20141: Cannot create component {0}:{1}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20142: Cannot duplicate component {0}:{1}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20143: Cannot delete component {0}:{1}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20144: Cannot cancel action for component {0}:{1}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20145: Cannot cancel application domain {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20146: Cannot cancel authentication scheme {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20147: Cannot cancel host identifier {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20148: Cannot cancel resource {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20149: Cannot cancel authentication policy {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20150: Cannot cancel authorization policy {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-21000: Create : {0} : paramList=[{1}].

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAM-21001: Created {0} : {1}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAM-21002: Modify : {0} : Existing=[{1}] : New=[{2}].

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAM-21003: Modified to : {0} : {1}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAM-21004: Exception encountered while parsing start date of OSSO Agent!

Cause: An internal exception occurred.

Action: For more details, start oam console logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-21005: NULL Refresh Call back.

Cause: Refresh Call back object for refreshing LHS tree found NULL.

Action: For more details, start oam console logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-21006: NULL Registration Server Controller.

Cause: Registration Server Controller found NULL.

Action: For more details, start oam console logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-22001: Error occured during cleanUpPolicy : {0}

Cause: Error occured during cleanUpPolicy.

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22002: Error occured during cleanUpApplicationDomains : {0}

Cause: Error occured during cleanUpApplicationDomains.

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22003: Error occured during initialization : {0}

Cause: Error occured during initialization.

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22004: Error occured during copying HostIdentifiers : {0}

Cause: Error occured during copying HostIdentifiers.

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22005: Error occured during copying policy changes : {0}

Cause: Error occured during copying policy changes.

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22006: Fetched partners from OAM server.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-22007: Applied partners to OAM server.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-22008: Switching off policy distribution.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-22009: Cleaned up policy file : {0}.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-22010: Copied policy changes to the intermediate file.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-22011: Switching on policy distribution.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-22012: Copied policy changes from the intermediate file.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-22013: Added host {0}:{1} to {2}.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-22014: Removed host {0}:{1} from {2}.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-22015: Removed resource {0} and policies using this resource from application domain {1}.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-22016: Error occured during creating application domain : {0}

Cause: Error occured during creating application domain.

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22017: Error occured during removing resource : {0}

Cause: Error occured during creating application domain.

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22018: Error occured during decrypting key : {0}

Cause: Error occured during decrypting key.

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22019: Error occured during encrypting key : {0}

Cause: Error occured during encrypting key.

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22020: Authentication module {0} is not present in the production system. Using the authentication module {1} to create the authentication scheme {2}

Cause: Authentication scheme cannot be created.

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22021: Intermediate OAM file was not found in the location {0}. Creating the intermediate file.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-22022: Error while creating the intermediate OAM policy file : {0}

Cause: Intermediate file cannot be created.

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22023: Error while setting the default authentication scheme: {0}

Cause: Default authentication scheme cannot be created.

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22024: Error while fetching the Partners: {0}

Cause: Error while fetching the Partners.

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22025: Error while writing Partners into a intermediate file: {0}

Cause: Error while writing Partners into a intermediate file.

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22026: Error while applying Partners: {0}

Cause: Error while applying Partners.

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22027: Error while exporting Partners: {0}

Cause: Error while exporting Partners.

Action: Check the OAM t2p logs.
Level: 1

Type: WARNING

Impact: Other

OAM-22028: Error while applying the Policy Configuration to PS1 instance

Cause: Intermediate file cannot be created.

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22029: Error while applying the System Configuration to PS1 instance

Cause: Intermediate file cannot be created.

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22030: Error while applying the KeyStore Configuration to PS1 instance

Cause: Intermediate file cannot be created.

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22031: Error while loading the given class dynamically for transformations

Cause: Error in loading the given class dynamically.

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22032: Loaded class is not the valid instance of a specific interface

Cause: Loaded class is not a valid instance of given interface

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22033: Transformation class is not found

Cause: Loaded class is not a valid instance of given interface

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22034: Error creating file ouput stream.

Cause: Could not create output stream.

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22035: Error creating/writing to object output stream.

Cause: Could not create object output stream.

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22036: Error closing output stream.

Cause: Could not close output stream.

Action: Check the OAM t2p logs.
Level: 15

Type: INFO

Impact: Other

OAM-22037: Error creating file input stream.

Cause: Could not open file input stream

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22038: Error creating object input stream.

Cause: could not open object input stream

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22039: Error deserializing object.

Cause: Could not de-serialize patrner object

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22040: Error reading from object Stream.

Cause: Could not read from object stream

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22041: Error occurred during partner re-registration

Cause: an error occurred during partner re-registration

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22042: Error while migrating partners information

Cause: Error while migrating partners

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22043: Error while getting migrating partners information

Cause: Error while getting migrating partners information

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22044: Error while writing migrating partners information

Cause: Error while writing migrating partners information

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22045: Error while certificate migration

Cause: Error while certificate migration

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22046: Export policy file with name {0} already exists.

Cause: A file already exists with the same name as policy export file.

Action: Ensure the no file exists with same name as policy export file.
Level: 15

Type: ERROR

Impact: Other

OAM-24001: Unable to execute the WLST Command

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24002: OSSO-Proxy configuration update operation failed.

Cause: The OSSO-Proxy configuration update in OAM system config failed.

Action: Enable detailed logging for details of the failure.
Level: 1

Type: ERROR

Impact: Other

OAM-24003: Given ID Store name doesn't exist

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24004: No properties file provided

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24005: Failed to create user id store in online mode

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24006: Unable to fetch LDAP Properties file

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24007: Value of Cookie passed is invalid

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24008: Error while closing the streams

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24009: Error while copying files

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24010: Error while wrapping and unwrapping files

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24011: Map retrieved from backend is null

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24012: One of the mandatory values is null

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24013: Unknown Version

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24014: LDAP Provider was invalid : {0}

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24015: Edit command parameter value is invalid

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24016: Unable to fetch the Server details

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24021: TAP Redirect URL is invalid, Registration failed.

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24022: Unable to contact the TAP Redirect URL, Registration failed.

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24023: TAP Redirect URL is null, Registration failed.

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24024: Exception fetching the authentication scheme, Registration failed.

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24025: TAP Key generation error.

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24026: TAP Key store generation error.

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24027: TAP Partner Registration Successful.

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24028: Error while retrieving keystore password using MBean connection.

Cause: Error while retrieving keystore password using MBean connection.

Action: Error while retrieving keystore password using MBean connection.
Level: 1

Type: ERROR

Impact: Other

OAM-24029: One of the mandatory values is null

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24030: Closing the stream failed.

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24031: Error in wrap and unwrap.

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24032: Osso proxy cookie value is empty.

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24033: Cannot find LdapProperties file

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24034: TAP Scheme not available to update TAPRedirect URL

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-25001: SSO only mode is not matching true.

Cause: Validation error

Action: Validation error
Level: 1

Type: WARNING

Impact: Other

OAM-25003: Wrong OAM Access Server host name.

Cause: Validation error

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25004: Wrong OAM Access Server port.

Cause: Validation error

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25005: Wrong OAM second access server host.

Cause: Validation error

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25006: Wrong OAM second access server port.

Cause: Validation error

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25007: Wrong OIM host name.

Cause: Validation error

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25008: Wrong OIM port.

Cause: Validation error

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25009: Wrong OIM URL Protocol.

Cause: Validation error

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25010: Wrong IDStore host name.

Cause: Validation error

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25011: Wrong IDStore port.

Cause: Validation error

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25012: Wrong IDSTore SSL flag true.

Cause: Validation error

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25013: Identity service not enabled.

Cause: Validation error

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25014: Identity service enabled.

Cause: Validation error

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25015: SSO only mode is not matching false.

Cause: Validation error

Action: Validation error
Level: 1

Type: WARNING

Impact: Other

OAM-25016: Wrong IDSTore SSL flag false.

Cause: Validation error

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25017: Invalid administrator user name.

Cause: Validation error

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25018: Invalid administrator user name/password. Login failed.

Cause: Validation error

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25019: Invalid administrator user roles.

Cause: Validation error

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25020: Error validating administrator user.

Cause: Validation error

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25021: Error in certificate validation of connecting url.

Cause: Validation error

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25022: Bad SSL Key from the contacting server.

Cause: Validation error

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25031: Invalid global WebGate pass phrase.

Cause: Validation error

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25051: Error in retrieving default authentication scheme.

Cause: Invalid Name

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25052: Class name is not passed.

Cause: Invalid Name

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25053: Class name not found in the server mapper.

Cause: Invalid Name

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25054: Error while executing method in test class.

Cause: Invalid Name

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25055: Mapper does not have method.

Cause: Invalid Name

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25056: Either cache service is down, or expected to find at least 2 cache nodes and did not. {0} cache nodes running.

Cause: Cache servers are not running.

Action: Restart the admin server.
Level: 1

Type: ERROR

Impact: Other

OAM-25058: User {0} is not authorized to invoke operation on the Oracle Access Management MBeans.

Cause: The user does not have the privileges to access the MBeans.

Action: Verify the System Identity Store configuration to ensure the correct privileges are set.
Level: 1

Type: ERROR

Impact: Other

OAM-30001: Invalid user credentials. Registration failed. Try again after providing valid credentials.

Cause: Username/password credentials provided are invalid.

Action: Try again after providing valid credentials.
Level: 1

Type: ERROR

Impact: Other

OAM-30002: User does not belong to the group that is authorized to perform registration. Registration failed. Try again after verifying the user's group.

Cause: User does not have a valid role to perform remote registration.

Action: Try again after verifying the user's role.
Level: 1

Type: ERROR

Impact: Other

OAM-30003: Agent name "{0}" already exists. Existing agent profile information from the server will be used to generate artifacts.

Cause: Agent name is not unique, it already exists.

Action:
Level: 1

Type: WARNING

Impact: Other

OAM-30004: Agent type is unrecognized or is invalid for the operation being performed: "{0}". Registration failed.

Cause: An internal error occurred due to unknown request type.

Action: For more details, start remote registration logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-30005: Output folder could not be created in the server domain home. Registration failed.

Cause: An internal error occurred as output folder could not be created in the server location.

Action: Verify permissions to create the folder.
Level: 1

Type: ERROR

Impact: Other

OAM-30006: Exception encountered while creating one or more of the output artifacts : {0}.

Cause: An internal error occurred while creating response file.

Action: For more details, start remote registration logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-30007: Exception encountered while validating using User/Role API : {0}. The exception trace is : {1}

Cause: An internal error occurred.

Action: Please verify credentials/role and try again.
Level: 1

Type: ERROR

Impact: Other

OAM-30008: User/Role API not available or could not be initialized. Registration failed.

Cause: An internal error occurred.

Action: For more details, start remote registration logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-30009: Application domain with the same name already exists. Registration failed. Try again after providing a unique application domain(agent name).

Cause: Application domain name is not unique.

Action: Try again after providing a unique application domain(agent name).
Level: 1

Type: ERROR

Impact: Other

OAM-30010: Anonymous authentication scheme does not exist so initial public authn policy cannot be created. Registration failed.

Cause: An internal error occurred as anonymous scheme does not exist.

Action: For more details, start remote registration logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-30011: The host:port is not unique. A different host identifier with name : "{0}" already exists for this host:port.

Cause: AgentBaseUrl specified is already registered under a different hostidentifier name.

Action: Try again after entering a unique agentBaseUrl value.
Level: 1

Type: ERROR

Impact: Other

OAM-30012: Error in encrypting the secret key. Registration failed.

Cause: An internal error occurred. Error in encrypting the secretkey.

Action: Try again after checking server configuration.
Level: 1

Type: ERROR

Impact: Other

OAM-30013: Error in generating the secret key. Registration failed: {0}

Cause: An internal error occurred. Error in creating the secretkey.

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30014: GlobalPassphrase retrieved from server configuration is null. Registration failed.

Cause: An internal error occurred. Error in retrieving globalPassphrase.

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30015: Error in decrypting the encrypted globalPassphrase. Registration failed.

Cause: An internal error occurred. Error in decrypting the retrieved globalPassphrase.

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30016: Error in obfuscating the decrypted globalPassphrase. Registration failed.

Cause: An internal error occurred. Error in obfuscating the decrypted globalPassphrase.

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30017: Internal error occurred. One of the mandatory response parameters is null. Registration failed.

Cause: An internal error occurred. One or more of the mandatory response fields is empty.

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30018: Internal error occurred. No response generated, due to either bad input or backend failure. See log file for details.

Cause: An internal error occurred. No response generated due to backend failure.

Action: See log file for details.
Level: 1

Type: ERROR

Impact: Other

OAM-30019: Exception encountered either while creating or writing to the native config file : {0}

Cause: An internal error occurred during creation of native config file

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30020: Exception encountered while writing to the output password file : {0}

Cause: An internal error occurred during creation of output password.xml file

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30021: Error in obfuscating the OSSO agent's output config file (osso.conf). Registration failed.

Cause: An internal error occurred. Error in obfuscating the created osso.conf config file.

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30022: Error in creating the credential store (wallet) : {0}

Cause: An internal error occurred. Error in creating the creating the credential store (wallet).

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30023: Error in storing the secretKey in the credential store (wallet): {0}

Cause: An internal error occurred. Error in storing the secretkey in the credential store (wallet).

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30024: Error occurred while parsing the XML file. Error message is : "{0}" at column number : "{1}" and at line number : "{2}"

Cause: The XML file provided is invalid or not well-formed.

Action: Try again after verifying syntax and well-formedness of the XML as per the schema.
Level: 1

Type: ERROR

Impact: Other

OAM-30025: Malformed registration request xml string : "{0}" - {1}

Cause: The XML request string generated is malformed.

Action: Internal error during parsing. Check the input request xml and try again.
Level: 15

Type: ERROR

Impact: Other

OAM-30026: {0}

Cause:

Action:
Level: 15

Type: ERROR

Impact: Other

OAM-30027: Error in unmarshalling operation : {0}

Cause: Error in unmarshalling the XML data.

Action: Try again after verifying syntax and well-formedness of the XML as per the schema.
Level: 1

Type: ERROR

Impact: Other

OAM-30028: Error in setting the validation schema : {0}

Cause: Error in setting the validation schema

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30029: Error in setting the validation event handler : {0}

Cause: Error in setting the validation event handler

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30030: Error in marshalling operation : {0}

Cause: Error in marshalling the data.

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30031: The character encoding being used is not supported : {0}

Cause: Internal error. Unsuppported character encoding being used.

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30032: Exception encountered while writing to the certificate file : "{0}". Error message is: {1}

Cause: An internal error occurred during creation of output password.xml file

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30033: Certificates could not be retrieved from the server location. Registration failed: {0}

Cause: An internal error occurred. Error in retrieving the certificates.

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30034: Error while reading the certificate file stream. Registration failed: {0}

Cause: An internal error occurred. Error in retrieving the certificates.

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30035: Server instance is not running for the security mode specified: "{0}".

Cause: Server instance not running for the security mode specified.

Action:
Level: 1

Type: WARNING

Impact: Other

OAM-30036: Internal server error. No server instances are running.

Cause: Internal server error occurred. No server instances exist.

Action:
Level: 1

Type: WARNING

Impact: Other

OAM-30037: Server instance is not running for the security mode specified: "{0}". Try again using a different security mode.

Cause: Server instance not running for the security mode specified

Action: Try again using a different security mode
Level: 1

Type: ERROR

Impact: Other

OAM-30038: Internal server error. There are no server instances running. Registration failed. Please try again later.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30039: Default security mode picked up for agent is: "{0}".

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAM-30040: Could not retrieve the timeout cookie name and timeout cookie key information from the server configuration. Registration failed.

Cause: An internal error occurred. Error in retrieving timeout cookie name and timeout cookie key for the agent.

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30041: Error while generating the cipher key or mask for the agent. Registration failed: {0}

Cause: An internal error occurred. Error in generating the cipher key or mask for the agent.

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30042: Error in decrypting the secret key while passing back in the response. Registration failed.

Cause: An internal error occurred. Error in decrypting the secretkey while passing back in the response.

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30043: Agent type in the request is either null or unidentified. Please try again after verifying the agent type.

Cause: Agent type that is passed in the request object is invalid.

Action: Try again after checking the agent type that is specified.
Level: 1

Type: ERROR

Impact: Other

OAM-30044: Internal error while encrypting/obfuscating the password. Registration failed: {0}

Cause: An internal error occurred. Error in encrypting/obfuscating the password.

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30045: The hostIdentifier string: "{0}" has already been added to an existing hostIdentifier called: "{1}". Try again after deleting the host entry from the existing hostIdentifier or registering with a new hostIdentifier name.

Cause: The hostIdentifier string specified is already registered under a different hostidentifier name.

Action: Try again after deleting the host entry from the existing hostIdentifier or registering with a new hostIdentifier name.
Level: 1

Type: ERROR

Impact: Other

OAM-30046: {0} mode failed. Agent does not exist.

Cause: Agent is not found.

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30047: Agent is found, but application domain does not exist. Agent could be in different application domain.

Cause: The Application Domain is not found.

Action: For validation, application domain name is agent name.
Level: 1

Type: ERROR

Impact: Other

OAM-30048: Url is not valid. Ensure that URL is of the format http://example.domain.com:port or https://example.domain.com:port, where port number is optional.

Cause: Url is not valid.

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30049: Exception encountered while creating the logout.html script file : {0}

Cause: An internal error occurred while creating the logout.html script file

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30050: In DELETEMODE, agent profile deleted successfully, however, artifacts output directory was not present or could not be deleted for the agent name: "{0}" at the output folder location: "{1}". Please delete the folder manually.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAM-30051: In DELETEMODE, agent profile and artifacts output directory was successfully deleted for the agent name: "{0}" at the server side output folder location: "{1}".

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAM-30052: Exception encountered while updating agent profile. Update of agent failed. {0}

Cause: An internal error occurred while updating agent profile

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30053: Application domain does not exist. Policy update failed.

Cause: The Application Domain is not found.

Action: Verify that the application domain you want to update exists and then try again.
Level: 1

Type: ERROR

Impact: Other

OAM-30054: Host identifier does not exist or is empty. {0} mode failed.

Cause: The Hostidentifier is not found.

Action: Verify that the hostidentifier you want to update exists and then try again.
Level: 1

Type: ERROR

Impact: Other

OAM-30055: The host: "{0}" and port: "{1}" is already present under the hostIdentifier: "{2}" and was not added again.

Cause: The hostPortVariation specified is already registered under an existing hostidentifier name, so it will not be added again.

Action:
Level: 1

Type: WARNING

Impact: Other

OAM-30056: Application domain already exists. policyCreate mode failed. Use policyUpdate mode to update existing application domains.

Cause: For policyCreate mode, application Domain already exists.

Action: Try again using policyUpdate mode to update existing application domains.
Level: 1

Type: ERROR

Impact: Other

OAM-30057: Create policy resource exception. {0} URI={1}

Cause: create resource failed. resouce/uri format is not valid.

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30058: Agent name {0} exceeds maximum allowed length of {1} characters.

Cause: The name of the agent being created was too long.

Action: Try again using a shorter name.
Level: 1

Type: ERROR

Impact: Other

OAM-30059: The user-specified managed server name/id: "{0}" does not exist. Registration failed. Please try again after specifying valid server name.

Cause: The user-specified managed server name/id is invalid.

Action: Try again after providing a valid server name.
Level: 1

Type: ERROR

Impact: Other

OAM-30060: Internal server error. The location "{0}" is invalid or does not exist in configuration. Registration failed.

Cause: Internal server error. The specified location in the config file is invalid or not existing.

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30061: isFusionAppRegistration flag was set to: "{0}" and SSOOnlyMode field was set to true.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAM-30062: isFusionAppRegistration flag was set to: "{0}" and denyOnNotProtected field was set to false(0).

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAM-30063: Agent type mismatch: Incoming agent request is of type: "{0}" , but the existing agent profile type in the server is: "{1}". Registration failed. Please try again after using agent name of the same type.

Cause: Incoming agent type does not match with the agent type already registered in the server.

Action: Verify that the agentName belongs to the same type and try again.
Level: 1

Type: ERROR

Impact: Other

OAM-30064: Agent version mismatch: Incoming agent request is of the correct type: "{0}" , but the version is: "{1}" , while the existing agent version in the server is: "{2}". Registration failed. Please try again after using agent name of the same version.

Cause: Incoming agent type is the same, however, does not match the agent version already registered in the server.

Action: Verify that the agentName belongs to the same version and try again.
Level: 1

Type: ERROR

Impact: Other

OAM-30065: Registration failed. Error in finding or reading the template file {0} for agent:{1} of type:{2}. - {3}

Cause: An internal error occurred: the template file was not found or could not be opened.

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30066: Warning: The host:port variation - {0}:{1} is not present under the hostIdentifier - {2} and so was not deleted.

Cause: The host:port variation is not present under the given hostIdentifier

Action: Verify that the host:port variation you are passing is actually present
Level: 1

Type: WARNING

Impact: Other

OAM-30067: Warning: HostIdentifier {0} cannot be empty, so added this host:port entry back to it - {1}:{2}

Cause: The hostIdentifier cannot be empty, so cannot delete all host:port entries under it

Action: Adds the last entry being deleted back to the hostIdentifier
Level: 1

Type: WARNING

Impact: Other

OAM-30068: Warning: None of the given host:port variations are present for the hostIdentifier- {0} , so nothing to delete.

Cause: None of the specified host:port variations are present under the hostIdentifier

Action: Check the host:port variations list being passed and try again
Level: 1

Type: WARNING

Impact: Other

OAM-30069: Notification: The initial protected authn policy is created.

Cause: The initial protected authn policy is created.

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAM-30070: Notification: The initial protected authz policy is created.

Cause: The initial protected authz policy is created.

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAM-30071: Notification: The public authn policy using Anonymous Scheme is created.

Cause: The public authn policy using Anonymous Scheme is created.

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAM-30072: Notification: The authn policy is updated.

Cause: The authn policy is updated.

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAM-30073: Notification: The authz policy is updated.

Cause: The authz policy is updated.

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAM-36001: Cannot obtain connection to domain MBean Server.

Cause: Console is not installed on the admin server.

Action: Check installation and configuration of the mbeans.
Level: 15

Type: ERROR

Impact: Other

OAM-36002: Cannot obtain MBean object.

Cause: MBean is not installed correctly.

Action: Check installation and configuration of the mbeans.
Level: 15

Type: ERROR

Impact: Other

OAM-36003: OAM service descriptor map: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36004: Result from remove crl: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36005: Result from getting all CRLs: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36006: Certificate validation configuration map: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36007: Deleting custom token: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36008: Result from deleting custom token: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36009: Error deleting custom token.

Cause: Error deleting custom token

Action: Check if managed server is up. Check server logs. Check if custom token was already deleted by another user.
Level: 15

Type: SEVERE

Impact: Other

OAM-36010: Setting custom token to: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36011: Result from setting custom token: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36012: Error setting custom token.

Cause: Error updating custom token

Action: Check if managed server is up. Check server logs. Check if custom token was deleted by another user.
Level: 15

Type: SEVERE

Impact: Other

OAM-36013: Creating custom token: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36014: Result from creating custom token: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36015: Error creating custom token.

Cause: Error creating custom token

Action: Check if managed server is up. Check server logs. Check if custom token of this name already exists.
Level: 15

Type: SEVERE

Impact: Other

OAM-36016: Get All custom tokens

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36017: Result from getting all custom tokens: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36018: Error getting custom tokens

Cause: Error getting custom tokens

Action: Check if managed server is up. Check server logs.
Level: 15

Type: SEVERE

Impact: Other

OAM-36019: Result from getting list of validation custom tokens: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36020: Result from getting list of issuance custom tokens: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36021: Result from getting all custom token names: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36022: Result from getting custom token by name: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36023: Result from geting all endpoints: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36024: Setting endpoint to: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36025: Result from setting endpoint: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36026: Result from getting all endpoint names: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36027: Error creating endpoint

Cause: Error creating endpoint

Action: Check if managed server is up. Check server logs. Check if endpoint of this name already exists.
Level: 15

Type: SEVERE

Impact: Other

OAM-36028: Creating endpoint with name {0} and properties {1}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36029: Result from getting endpoint {0} by name {1}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36030: Error deleting endpoint.

Cause: Error deleting endpoint

Action: Check if managed server is up. Check server logs. Check if endpoint was already deleted by another user.
Level: 15

Type: SEVERE

Impact: Other

OAM-36031: Deleting endpoint {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36032: Result from deleting endpoint {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36033: Result from getting keystore access template Names {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36034: Result from geting all keystore access templates {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36035: Result from setting keystore access template {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36036: Setting keystore access templates: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36037: Error setting keystore access template {0}

Cause: Error updating keystoreaccesstemplate

Action: Check if managed server is up. Check server logs. Check if template was deleted by another user.
Level: 15

Type: SEVERE

Impact: Other

OAM-36039: Result from setting keystore access template alias and pwd for alias {0} in csf: {1}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36040: Result from geting all keystore access template names {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36041: Setting security token service settings to {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36042: Result from after setting security token service settings {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36043: Error setting security token service settings.

Cause: Error setting security token service settings.

Action: Check if managed server is up. Check server logs.
Level: 15

Type: SEVERE

Impact: Other

OAM-36044: Result from getting security token service settings {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36045: Result from getting global configuration {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36046: Result from setting global configuration {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36047: Setting STS global configuration properties {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36048: Error setting STS global configuration.

Cause: Error setting STS Global Configuraiton

Action: Check if managed server is up. Check server logs.
Level: 15

Type: SEVERE

Impact: Other

OAM-36049: Error getting STS global configuration.

Cause: Error getting STS Global Configuration

Action: Check if managed server is up. Check server logs.
Level: 15

Type: SEVERE

Impact: Other

OAM-36050: Result from getting server configuration {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36051: Result from setting server configuration {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36052: Setting STS server configuration properties {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36053: Error setting STS server configuration.

Cause: Error setting STS server configuration

Action: Check if managed server is up. Check server logs.
Level: 15

Type: SEVERE

Impact: Other

OAM-36054: Error getting STS server configuration.

Cause: Error getting STS server configuration

Action: Check if managed server is up. Check server logs.
Level: 15

Type: SEVERE

Impact: Other

OAM-36055: Result from creating token template {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36056: Creating token of type {0} with template type {1} and properties {2}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36057: Error creating token template.

Cause: Error creating template

Action: Check if managed server is up. Check server logs. Check if template of this name already exists.
Level: 15

Type: SEVERE

Impact: Other

OAM-36058: Result from updating token template {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36059: Updating token of type {0} with template type {1} and properties {2}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36060: Error updating token template.

Cause: Error updating custom token

Action: Check if managed server is up. Check server logs. Check if template was deleted by another user.
Level: 15

Type: SEVERE

Impact: Other

OAM-36061: Result from deleting token template {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36062: Deleting token template {0} of type {1}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36063: Error deleting token template.

Cause: Error deleting template

Action: Check if managed server is up. Check server logs. Check if template was already deleted by another user.
Level: 15

Type: SEVERE

Impact: Other

OAM-36064: Result from getting all issuance templates {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36065: Result from getting all validation templates {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36066: Result from getting all issuance template names {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36067: Result from getting all validation template names {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36068: Result from getting issuance template {0} by name: {1}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36069: Result from getting validation template {0} by name: {1}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36070: Result from add CRL: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36071: Error adding CRL.

Cause: Error adding CRL

Action: Check if managed server is up. Check server logs. Check if CRL file is valid and if it already exists.
Level: 15

Type: SEVERE

Impact: Other

OAM-36072: Error deleting CRL.

Cause: Error deleting CRL

Action: Check if managed server is up. Check server logs. Check if CRL was already deleted by another user.
Level: 15

Type: SEVERE

Impact: Other

OAM-36073: Error getting all CRLs.

Cause: Error deleting custom token

Action: Check if managed server is up. Check server logs. Check if CRL was already deleted by another user.
Level: 15

Type: SEVERE

Impact: Other

OAM-36074: handle query parameters: page (start, end) = ({0}, {1}), OrderBy = {2}, paramMap={3}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36075: Query response is empty

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36076: Error query response: {0}

Cause: Error querying the server

Action: Check if managed server is up. Check server logs.
Level: 15

Type: SEVERE

Impact: Other

OAM-36077: query response: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36078: populating row with attribute values: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36079: doDML operation: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36080: isCreateLike: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36081: parameter {0} not found

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36082: null row data passed to populate attribute

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36083: Result from creating partner profile {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36084: Creating partner profile of type {0} with properties {1}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36085: Error creating partner profile

Cause: Error creating partner profile

Action: Check if managed server is up. Check server logs. Check if partner profile of this name already exists.
Level: 15

Type: SEVERE

Impact: Other

OAM-36086: Result from updating partner profile {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36087: Updating partner profile of type{0} with properties {1}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36088: Error updating partner profile

Cause: Error updating partner profile

Action: Check if managed server is up. Check server logs. Check if partner profile was deleted by another user.
Level: 15

Type: SEVERE

Impact: Other

OAM-36089: Result from deleting partner profile {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36090: Deleting partner profile {0} of type {1}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36091: Error deleting partner profile

Cause: Error deleting partner profile

Action: Check if managed server is up. Check server logs. Check if partner profile was already deleted by another user.
Level: 15

Type: SEVERE

Impact: Other

OAM-36092: Result from getting all partner profiles {0} of Type: {1}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36093: Result from creating partner {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36094: Creating partner of type {0} with properties {1}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36095: Error creating partner

Cause: Error creating partner

Action: Check if managed server is up. Check server logs. Check if partner of this name already exists.
Level: 15

Type: SEVERE

Impact: Other

OAM-36096: Result from updating partner {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36097: Updating partner of type {0} with properties {1}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36098: Error updating partner

Cause: Error updating partner

Action: Check if managed server is up. Check server logs. Check if this partner was deleted by another user.
Level: 15

Type: SEVERE

Impact: Other

OAM-36099: Result from deleting partner {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36100: Deleting partner {0} of type {1}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36101: Error deleting partner

Cause: Error deleting partner

Action: Check if managed server is up. Check server logs. Check if partner was already deleted by another user.
Level: 15

Type: SEVERE

Impact: Other

OAM-36102: Result from getting all partners {0} of Type: {1}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36103: Result from getting WSS validation template names {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36104: Result from getting partner profile: {0} by name: {1}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36105: Result from getting partner: {0} by name: {1}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

62 OAMCFG-60001 to OAMCFG-60085

OAMCFG-60001: Error in initializing logging.

Cause: System error

Action: Check Java system logger settings.
Level: 1

Type: ERROR

Impact: Logging

OAMCFG-60002: Unable to establish connection to directory server.

Cause: Incorrect input given for LDAP directory server parameters.

Action: Verify input values for the following parameters: ldap_host, ldap_port, ldap_userdn, and ldap_userpassword.
Level: 1

Type: ERROR

Impact: Network

OAMCFG-60003: Error in parsing command-line parameters.

Cause: One or more required parameters are missing.

Action: Provide all required parameters. Use -help option to see the list of parameters.
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60004: Cannot write LDIF to console.

Cause: A request was made to write LDIF output to the console.

Action: Specify a proper LDIF file name using the output_ldif_file parameter.
Level: 1

Type: ERROR

Impact: Files

OAMCFG-60005: The same file name cannot be used for the log file and the LDIF output file.

Cause: The same name was specified for output_ldif_file and log_file parameters.

Action: Specify different names for output_ldif_file and log_file parameters.
Level: 1

Type: ERROR

Impact: Files

OAMCFG-60006: In VALIDATE mode, the test_username parameter is mandatory

Cause: The test_username parameter was not specified during validation.

Action: Specify the test_username parameter during validation.
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60007: In VALIDATE mode, the test_userpassword is mandatory

Cause: The test_userpassword parameter was not specified during validation.

Action: Specify the test_userpassword parameter during validation.
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60008: Oracle Access Manager version {0} cannot be configured.

Cause: An unsupported version of Oracle Access Manager is specified on the command line.

Action: Specify the correct, supported Oracle Access Manager version.
Level: 1

Type: ERROR

Impact: Configuration

OAMCFG-60009: The app_domain parameter is mandatory

Cause: The app_domain parameter was not specified.

Action: Specify the app_domain parameter.
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60010: The specified LDAP port number is invalid

Cause: An invalid LDAP port was specified.

Action: Specify a valid LDAP port.
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60011: The ldap_userdn parameter is mandatory.

Cause: The ldap_userdn parameter was not specified.

Action: Specify the ldap_userdn parameter.
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60012: The specified Oracle Access Manager port number is invalid.

Cause: An invalid Oracle Access Manager port number was specified.

Action: Specify the correct Oracle Access Manager port number.
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60013: Found Oracle Access Manager version {0} which is incompatible.

Cause: The tool found an incompatible version of Oracle Access Manager configured in the directory.

Action: Use the tool with a compatible Oracle Access Manager version.
Level: 1

Type: ERROR

Impact: Configuration

OAMCFG-60014: Oracle Access Manager is not configured with this directory.

Cause: Oracle Access Manager is not configured for the specified directory.

Action: Contact your Oracle Access Manager administrator to configure Oracle Access Manager for the specified directory.
Level: 1

Type: ERROR

Impact: Configuration

OAMCFG-60015: Invalid value detected for oam_aaa_host or oam_aaa_port.

Cause: Cannot find the Access Server based on the specified host or port in configuration. Or check if oam_mode is correctly specified. Default is open mode

Action: Specify a valid Access Server host and port.
Level: 1

Type: ERROR

Impact: Configuration

OAMCFG-60016: Error in closing file handles.

Cause: An error occurred when closing file handles used by the tool.

Action: Check the file system for consistency.
Level: 1

Type: ERROR

Impact: Files

OAMCFG-60017: Cannot decode URI : {0} due to its length. Actual length: {1}

Cause: The URI in the directory is an illegal length. The encoded URI length must always be even.

Action: Contact your Oracle Access Manager administrator to correct or delete the URI in the directory.
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60018: Cannot decode URI :{0}

Cause: The URI was found to contain illegal hexadecimal characters.

Action: Contact your Oracle Access Manager administrator to correct or delete the URI in the directory.
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60019: Cannot send the cache flush request to server {0} running on port {1} in mode {2}.

Cause: The Access server is down.

Action: Contact your Oracle Access Manager administrator to ensure that the Access Server is running.
Level: 1

Type: ERROR

Impact: Network

OAMCFG-60020: A cache flush request cannot be sent using the desired transport security mode {0}.

Cause: The Access Server is not available with the specified transport security mode.

Action: Contact your Oracle Access Manager administrator to ensure that the Access Server is running in the desired transport security mode.
Level: 1

Type: ERROR

Impact: Configuration

OAMCFG-60021: Found multiple policy stores in the directory:: {0}.

Cause: Multiple Access Server Policy Stores are configured in the directory.

Action: Use the ldap_base parameter to specify the correct searchbase.
Level: 1

Type: ERROR

Impact: Configuration

OAMCFG-60022: Access Server is not configured in this directory.

Cause: The Access Server is not configured.

Action: Contact your Oracle Access Manager administrator to configure the Access Server.
Level: 1

Type: ERROR

Impact: Configuration

OAMCFG-60023: A problem occurred when communicating with the LDAP directory server.

Cause: The LDAP directory server is down.

Action: Contact your LDAP directory server administrator to ensure the directory is running.
Level: 1

Type: ERROR

Impact: Network

OAMCFG-60024: The LDAP operation failed.

Cause: Either incorrect configuration or invalid parameters and values were specified.

Action: Confirm that your parameters and values are correct.
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60025: A problem occurred while trying to fetch the Oracle Access Manager details from configuration.

Cause: An Oracle Access Manager instance matching the specified input could not be found.

Action: Confirm parameters oam_aaa_host and oam_aaa_port are correct.
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60026: Cannot get Global Sequence Number in the specified Oracle Access Manager policy store: {0}.

Cause: The configuration data in the LDAP directory server is missing Global Sequence Number information.

Action: Contact your Oracle Access Manager administrator to configure Oracle Access Manager with the LDAP directory.
Level: 1

Type: ERROR

Impact: Configuration

OAMCFG-60027: Found {0} entries that match the name: {1}.

Cause: Multiple names match the given name.

Action: Contact your Oracle Access Manager administrator.
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60028: Found no entries that match the specified name:{0} of type:{1}.

Cause: Entries matching the specified name cannot be found.

Action: Confirm the name.
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60029: Error while loading template:{0} to LDAP

Cause: Not all information could be loaded to LDAP directory.

Action: Contact your Oracle Access Manager administrator to validate that all data has been loaded.
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60030: The app_agent_password parameter is mandatory when creating a Web domain.

Cause: The app_agent_password parameter was not specified.

Action: Specify the app_agent_password when creating a Web domain.
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60031: The template file {0} cannot be located.

Cause: The specified template could not be found in either the file system or the Jar file.

Action: Obtain the Jar file again. If your template was customized, ensure it is in the expected file system location.
Level: 1

Type: ERROR

Impact: Files

OAMCFG-60032: The template file {0} cannot be read from file system.

Cause: The template file or file system (or both) might be corrupted.

Action: Ensure that the template file or file system error (or both) are corrected.
Level: 1

Type: ERROR

Impact: Files

OAMCFG-60033: Problem locating a template file in JAR file:{0}

Cause: The JAR file does not contain the required templates.

Action: Ensure that the correct JAR file is specified in the CLASSPATH.
Level: 1

Type: ERROR

Impact: Files

OAMCFG-60034: The specified LDAP SSL mode is invalid

Cause: An invalid LDAP SSL mode was specified.

Action: Specify a valid LDAP SSL mode: 1, 2 or 3.
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60035: The specified application domain, {0}, cannot be used.

Cause: The value provided for app_domain parameter contains illegal characters.

Action: Specify app_domain parameter with legal characters.
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60036: The specified web domain, {0}, cannot be used.

Cause: The value provided for web_domain parameter contains illegal characters.

Action: Specify web_domain parameter with legal characters.
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60037: ldap_userpassword is mandatory

Cause: The ldap_userpassword parameter was not specified.

Action: Specify the ldap_userpassword parameter.
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60038: The URIs file parameter should not be empty

Cause: The uris_file param is empty.

Action: If you are using the uris_file parameter, then specify an appropriate value. This value should list the full path to a file, containing protected and public uris
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60039: The specified uris_file, {0}, could not be found

Cause: The file specified by uris_file param does not exist.

Action: Make sure the path you have specified for the file containing uris is correct
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60040: uris_file, {0}, cannot be read

Cause: There is some issue in reading the file

Action: Contact your administrator
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60041: uris_file, {0}, could not be closed

Cause: The file could not be closed

Action: No action needs to be taken, if there are no other errors
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60042: uris_file, {0}, does not have protected uris

Cause: No Protected uris have been specified

Action: Contact the file owner
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60043: Protected URIs have already been listed in the uris file

Cause: Protected uris are being specified again

Action: Include the protected uris, specified in command line, in the uris file and do not pass the protected_uris parameter
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60044: Public URIs have already been listed in the uris file

Cause: Public uris are being specified again

Action: Include the public uris, specified in command line, in the uris file and do not pass the public_uris parameter
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60045: Invalid Authenticating Webgate URL

Cause: The Authenticating Webgate URL is not formatted correctly

Action: Ensure that the URL is of the form, 'http://host.example.com:port' or 'https://host.example.com:port'. Note that it is important to specify the URL with a FQDN, a domain in which your cookie would be valid.
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60046: LDAP_HOST parameter is mandatory

Cause: LDAP_HOST parameter is not specified

Action: Specify LDAP_HOST parameter in command line
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60047: OAM_AAA_HOST parameter is mandatory

Cause: OAM_AAA_HOST parameter is not specified

Action: Specify OAM_HOST parameter in command line
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60048: APP_DOMAIN, {0}, does not exist

Cause: APP_DOMAIN, {0}, does not exist

Action: Specify a APP_DOMAIN parameter that exists in OAM
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60049: URI, {0}, does not exist

Cause: URI, {0}, does not exist

Action: Specify a URI that exists in OAM
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60050: Authentication scheme, {0}, does not exist

Cause: Authentication scheme, {0}, does not exist

Action: Specify a valid Authentication Scheme
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60051: Webdomain, {0}, does not exist

Cause: Webdomain, {0}, does not exist

Action: Specify a valid Host Identifier as part of Web_domain
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60052: Simple Mode Passphrase is mandatory for Simple mode

Cause: Simple Mode Passphrase has not been provided

Action: Specify a Simple Mode Passphrase
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60053: OAM_AAA_PORT parameter is mandatory

Cause: OAM_AAA_PORT parameter is not specified

Action: Specify OAM_AAA_PORT parameter in command line
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60054: Specify protected or public uris either in command line or in a file

Cause: Both protected_uris and public_uris have not been specified for Create mode

Action: Specify protected or public uris either in command line or in a file
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60055: One of the default authentication schemes is in use and cannot be deleted

Cause: Some policies are using the default authentication schemes that you wish to delete

Action: First delete the policies that are using the authentication scheme specified
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60056: The default authentication scheme, OraDefaultAWGFormAuthNScheme, is in use and cannot be deleted

Cause: Some policies are using this authentication scheme that you wish to delete

Action: First delete the policies that are using the authentication scheme specified
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60057: The default authentication scheme, OraDefaultI18NFormAuthNScheme, is in use and cannot be deleted

Cause: Some policies are using this authentication scheme that you wish to delete

Action: First delete the policies that are using the authentication scheme specified
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60058: The web_domain specified, {0}, is in use and cannot be deleted

Cause: Some policies are using the web domain that you wish you delete

Action: First delete the policies that are using the web domain
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60059: Either app_domain or uris or web domain or authn schemes need to be provided. See help

Cause: Required parameters have not been specified for DELETE mode

Action: Specify whether app domain or uris or web domain or authn schemes need to be deleted
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60060: An error occurred while modifying the ldap attribute, {0}

Cause: An error occurred while modifying the ldap attribute, {0}

Action: Contact your OAM administrator
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60061: The Webgate with id, {0}, does not exist

Cause: The specified Webgate does not exist in OAM

Action: Specify the correct webgate id using the parameter, {0}
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60062: LogoutRedirectUrl has already been configured for the WebGate, {0}

Cause: LogoutRedirectUrl parameter is not empty for the specified WebGate

Action: You cannot reconfigure the parameter logoutRedirectUrl using the Config tool. Use OAM Policy Manager UI for this., {0}
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60063: The LogoutRedirectUrl element tag has been messed up in the attribute, 'obcompounddata' attribute for the WebGate, {0}

Cause: LogoutRedirectUrl element is not formatted correctly in the DS for the specified WebGate

Action: Contact the OAM Administrtor
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60064: The LogoutRedirectUrl param cannot be configured without AWG

Cause: authenticating_wg_url param is not specified

Action: Specify authenticating_wg_url param
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60065: The logouturi parameter is not a valid uri

Cause: The logouturi parameter needs to have an value beginning with '/'

Action: Specify a valid uri
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60066: An unexpected parameter has been passed to the tool, {0}

Cause: An unexpected parameter is present as part of the command line arguments

Action: Make sure that none of the parameters have been mispelled and that all the parameters specified are indeed valid
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60067: OimOhsHostPort needs to be specified if authenticating_wg_url parameter is mentioned

Cause: OimOhsHostPort has not been specified and authenticating_wg_url parameter is mentioned

Action: Specify OimOhsHostPort parameter
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60068: The Authentication Scheme specified by {0} would be given preference over the default i18n authentication scheme

Cause: The default i18n authentication scheme specified by usei18nlogin flag would not be used because of the parameter default_authn_scheme

Action: One of the two parameters should be specified
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60069: The Access Server Id, {0}, mentioned as part of the parameter, {1} is not present in OAM

Cause: This Access Server Id does not exist in OAM

Action: Make sure that the Access Server Id passed is present in OAM
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60070: The param, {0}, contains some values that are not valid. Check log for details

Cause: Some of the Access Server Id's mentioned are not valid

Action: Make sure that the Access Server Id's mentioned are all valid
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60071: The transport security mode of WebGate, {0}, differs from Access Server, {1}

Cause: There is a transport security mismatch

Action: Make sure the transport security mathes between the WebGate and Access Server
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60072: The Access Management Service mode of WebGate, {0}, differs from Access Server, {1}

Cause: There is a mismatch between Access Management Service modes

Action: Make sure the Access Management Service mathes between the WebGate and Access Server
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60073: {0} has been specified as part of both Primary and Secondary server params

Cause: Same value has been specified as part of both Primary and Secondary servers

Action: Make sure that you have unique values for both Primary and Secondary Servers
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60074: The value, {0}, has been specified more than once in a comma separated input parameter

Cause: Duplicate values have been provided in one of the input paramters

Action: Make sure that you have unique values specified as part of input params
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60075: The provided parameter, {0}, is not a valid integer

Cause: An invalid integer was passed

Action: Make sure the value provided is a valid integer
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60076: The URL for Impersonation Consent Form is mandatory

Cause: The URL for Impersonation Consent Form has not been passed

Action: Make sure you provide a URL for Impersonation Consent Form
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60077: The path to the Impersonation Authz Plugin is mandatory

Cause: The path to the Impersonation Authz Plugin has not been passed

Action: Make sure you provide a path to the Impersonation Authz Plugin
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60078: Impersonation Authz Scheme has not been configured and hence would not be used

Cause: Impersonation Authz Scheme has not been configured

Action: Configure the Impersonation Authn/Authz plugins, if required
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60079: The Authz rule, {0} already exists for this app domain, {1}

Cause: Authz rules already exists

Action: No action needs to be taken.
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60080: Authorization scheme, {0}, does not exist

Cause: Authorization scheme, {0}, does not exist

Action: Specify a valid Authorization Scheme
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60081: The user, {0} probably has write permission to the OAM Policy store since he matches the user, {1}, that was provisioned as the OAM runtime user

Cause: Not able to conclusively validate

Action: Ensure that the intended user has appropriate privileges
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60082: The user, {0} probably does not have write permission to the OAM Policy store since he does not match the user, {1}, that was provisioned as the OAM runtime user

Cause: Not able to conclusively validate

Action: Ensure that the intended user has appropriate privileges
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60083: OAM Configuration did not complete successfully. Refer log for details

Cause: An exception occurred

Action: Check the messages in the log for details
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60084: OAM server host, {0}, port, {1} is down

Cause: The server is down

Action: Make sure the specified server is up
Level: 1

Type: ERROR

Impact: Data

OAMCFG-60085: There could be an issue with cache flush. URL Prefix Mapper could not be setup

Cause: An exception occurred while constructing URL Prefix Map

Action: Verify any URLs that you may have created are protected. If not, restart WebServer and Access server
Level: 1

Type: ERROR

Impact: Data

63 OAMSSA-00001 to OAMSSA-22030

OAMSSA-00001: Service provider configuration {0} is not valid.

Cause: The service provider configuration in the system configuration was invalid.

Action: Verify the identity and registration service provider configuration.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-00002: Cannot instantiate service provider.

Cause: The service provider configuration was invalid.

Action: Verify the identity and registration service provider configuration.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-00003: Identity service configuration is not valid.

Cause: The identity service configuration was invalid.

Action: Verify the identity service configuration.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-00004: User self service configuration is not valid.

Cause: The user self service configuration was invalid.

Action: Verify the user self service configuration.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-00005: Identity Manager Integration is enabled {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAMSSA-00006: User Self Service is enabled {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAMSSA-00007: Policy Evaluation result {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAMSSA-00008: Constructed URL {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAMSSA-02001: Session not found for sessionid: {0}

Cause: Requested session object has expired, has been deleted, or does not exist.

Action: Verify that the session exists before making the call.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02002: Session not found for userid: {0} identity domain: {1} and sessionindex: {2}

Cause: The requested session object has expired, has been deleted, or does not exist.

Action: Verify that the session exists before making the call.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02003: Cannot find method {0} on class {1}

Cause: An attempt was made to access a method that does not exist.

Action: Verify that the method exists before making the call.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02004: Cannot to execute method {0} on class {1}

Cause: An attempt to execute a method that is not supported.

Action: Use a supported method.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02005: Cannot to get SessionManager for type: {0}

Cause: An invalid type was specified.

Action: Verify that the type is supported before making the call.
Level: 30

Type: ERROR

Impact: Other

OAMSSA-02006: SessionMananger type not present: {0}

Cause: The requested implementation was not specified in configuration files.

Action: Add the SessionManager type to the configuration files
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02007: Factory class does not have factory methods.

Cause: Factory class does not have factory methods.

Action: None.
Level: 15

Type: INFO

Impact: Other

OAMSSA-02008: Cannot instantiate the persistence access implementation for class {0}.

Cause: An attempt was made to instantiate an invalid persistence access implementation.

Action: Verify the settings in the configuration file.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02009: Cannot extract attribute for method {0}.

Cause: An incorrect method was used to extract an attribute value.

Action: Use the correct API call.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02010: UpdateProcessor is in invalid mode for entry {0}.

Cause: UpdateProcessor serialization failure.

Action: Verify the configuration files, and the deployment.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02011: Cannot update attribute for method {0}.

Cause: An incorrect method was used to update the attribute value.

Action: Use the correct API call.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02012: Session count for user {0} has reached the maximum session limit per user.

Cause: Session count for user has reached the maximum session limit per user.

Action: Log out of some of the sessions before attempting to create new sessions.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02013: SME expired session reaper thread not started.

Cause: Database configuration may be in correct

Action: Verify that the server started without errors.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-02014: Session {0} not deleted.

Cause: Database configuration may be in correct

Action: Verify Data Source Name and database configuration
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02015: Session attribute type {0} for key {1} is not supported. Attribute will be ignored.

Cause: Data in database is currupted due to unknown cause, or session is updated with unsupported data type properties.

Action: Correct the session client api usage.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02016: Session object for sessionid {0} was not loaded.

Cause: Database configuration may be in correct

Action: Verify Data Source Name and database configuration
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02017: Session object for sessionid {0} was not saved.

Cause: Database configuration may be incorrect

Action: Verify Data Source Name and database configuration
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02018: Session attribute value {0} for key {1} is not serializable. Attribute will be ignored.

Cause: Session attribute value is invalid.

Action: Correct the session client api usage.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02019: Session attribute key is null for userid {0} in session {1}.

Cause: Session attribute key is null.

Action: Correct the session client api usage.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02020: Grant for impersonation of user {0} by user {1} does not exist, or has expired.

Cause: Impersonation grant does not exist, or has expired.

Action: Verify impersonation grant information.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02021: Session exists for user {0} and sessionindex {1}.

Cause: Session object already exists.

Action: Use the existing session.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02022: Session {0} is not an impersonation session.

Cause: Session is not impersonation session.

Action: Ensure that impersonation operations are done on an impersonation session.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02023: Session {0} for user {1} index {2} is already impersonating. Further impersonations not allowed.

Cause: Impersonating sessions can not chain impersonation.

Action: Ensure that impersonation requests are done on non-impersonating sessions.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02024: Session {0} timed out.

Cause: Session is inactive

Action: Re-authenticate user.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02025: Session attribute domain definition {0} is not supported. Default domain value of {1} used.

Cause: Invalid configuration

Action: Correct the search attribute definition
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02026: QueryDescriptor has invalid value. {0} is {1}.

Cause: Invalid search input

Action: Correct the search attribute definition
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02027: Search request failed. {0}.

Cause: Search operation failed for provided cause.

Action: Correct the cause of the failure.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02028: Failed to transform the search request into a valid query.

Cause: The search request was not transformed into a search query.

Action: Correct the cause of the failure.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02029: Search request resulted in a null result object.

Cause: The search request failed with no results.

Action: Correct the cause of the failure.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02030: Selection list generation failed for extractor {0}.

Cause: Selection list transformation not supported for extractor or attribute.

Action: Verify supported attributes used in the session search
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02031: Where clause generation failed for extractor {0}.

Cause: Extractor transformation not supported for extractor or attribute.

Action: Verify supported attributes used in the session search
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02032: Selection list initialization failed for operation {0}.

Cause: Selection list transformation initialization failed.

Action: Verify supported selection initialization for failed operations.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02033: Initialization of search failed.

Cause: Initialization of search failed

Action: Verify libraries and jar versions.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02034: Conversion of database value to boolean failed. Defaulting {0} to {1}.

Cause: Database column mapping incorrect, or database column type incorrect.

Action: Verify database field configuration.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02035: Unsupported session store version detected. Required "{0}" but found "{1}".

Cause: The version of session store is not compatible with OAM version.

Action: Make sure OAM is configured to talk to correct version of session store.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02036: Ignoring declaration for invalid search attribute. {0}

Cause: Invalid attribute definition in configuration.

Action: Verify the configuration of the search attributes.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02037: The background delete thread has become unresponsive. Falling back to foreground session deletion.

Cause: The background delete thread has become unresponsive.

Action: Verify health of the JDBC data source connection.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02038: Failed to put session {0} on queue {1}.

Cause: Resource bounds exceeded.

Action: Correct cause of server overload.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02039: Session store write restored at wait queue size {0}. Current limit on queue size is {1}.

Cause: Load on background write queue has reduced.

Action: No action required.
Level: 15

Type: INFO

Impact: Other

OAMSSA-02040: Session store write disabled at wait queue size {0}. Current limit on queue size is {1}.

Cause: Load on background write queue has reached upper bound.

Action: Examine sources of loading.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-02041: Client lease for session {0} has expired.

Cause: Session update lease has expired.

Action: Examine use case of session update to eliminate updates using old session objects.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02042: Credentials for session {0} have expired.

Cause: Session credential has expired.

Action: Perform credential validation.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-02043: Session object expected. Null value found.

Cause: Invalid input.

Action: Invoke method with valid input.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02044: Session update context object expected. Null value found.

Cause: Invalid input.

Action: Invoke method with valid input.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02045: Request to encode {0} numbers exceed maximum limit of {1}.

Cause: Invalid input.

Action: Invoke method with valid input.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02046: Credential validation date cannot be null.

Cause: Invalid input.

Action: Invoke method with valid input.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04001: Operation {0} is not supported.

Cause: The requested operation was not supported.

Action: Use a supported operation.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04002: Incorrect number of parameters {0} passed for operation {1}

Cause: An incorrect number of parameters was passed to the expression builder.

Action: Pass the correct number of parameters required for the expression.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04003: Unable to get data store instance.

Cause: An invalid configuration file was supplied.

Action: Verify the configuration file.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04004: Cannot get extractor list from passed configuration.

Cause: An incorrect extractor list was supplied.

Action: Verify the supplied configuration.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04005: Data store established but data connection cannot be made.

Cause: Database connection information was invalid.

Action: Verify configuration files.
Level: 15

Type: INFO

Impact: Other

OAMSSA-04006: Cannot get connection from data source.

Cause: Data source configuration was invalid.

Action: Verify configuration files.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04007: Key is not unique: {0}

Cause: The key in the database was not unique.

Action: Verify data integrity.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04008: Data source definition not found. Store will be in-memory only.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAMSSA-04009: Invalid parameter type passed to construct {0}

Cause: The function parameter type was invalid.

Action: Verify client implementation.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04010: OAM Configuration for Coherence property {0} not found. Default configuration will be used.

Cause: No overrides were specified.

Action: None.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04011: Cannot resolve address for server instance {0}.

Cause: Server Instance listed in the Configuration is invalid.

Action: Correct the configuration and rerun the operation.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-04012: Cannot set local host values for this server instance.

Cause: Unable to set permissions for local host.

Action: Please verify the network configuration and rerun this operation.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-04013: Coherence property type update is not supported for property {0}. Supported types include String, Integer, Boolean.

Cause: An unsupported Coherence configuration property type was specified.

Action: Use a supported Coherence configuration property type.
Level: 15

Type: INFO

Impact: Other

OAMSSA-04014: Cannot set override properties for Coherence due to exception.

Cause: The supplied Coherence configuration properties are invalid.

Action: Correct the configuration.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04015: Datasource not found for provided name {0}.

Cause: The supplied Datasource name is invalid.

Action: Correct the configuration.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04016: Cannot store key {0} in data store.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04017: Cannot erase key {0} in data store.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04018: Cannot get Iterator of keys from data store.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04019: Cannot acquire distribution lock.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04020: Distribution version is {0}. Version requested for distribution is {1}.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04023: Cannot initialize configuration.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04024: Stale data exception encountered for config version {0}.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04032: Incorrect type of parameters {0} passed for operation {1}.

Cause: An invalid parameter type was passed to the expression builder.

Action: Pass the correct parameters required for the expression.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04033: Failed to get encryption key.

Cause: Shared Key for encryption not found.

Action: Verify that installation completed without errors.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04034: Invalid configuration map path {0}

Cause: Provided configuration map path is invalid.

Action: Ensure that the passed configuration map path is a valid path.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04035: Operation {0} supports {1} operand(s) only.

Cause: Number of operands supplied for operation is incorrect.

Action: Correct the API call with the required number of operands.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04036: Criterion type {0} does not support operation {1}.

Cause: Criterion does not support requested operation.

Action: Correct the API call with supported operand.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04037: Extraction of attribute {0} failed.

Cause: Extraction of attribute failed.

Action: Correct the API call with supported attribute extractor.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04038: The passed Criterion object type {0} is not supported by transformer type {1}.

Cause: Invalid parameter type.

Action: Correct the API call with supported criterion type.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04039: Transform for operation {0} not found.

Cause: Operation trasformation class not defined.

Action: Correct the transformation properties file.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04040: Criterion {0} does not contain operation.

Cause: Criterion does not contain operation.

Action: Correct the configuration to make the correct API call.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04041: Failed to read the operation to transforms mapping configuration.

Cause: Unable to read the operation to transforms mapping.

Action: Correct the configuration to make the correct API call.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04042: Invalid mapping {0} found for operation {1}.

Cause: Invalid operation to transform mapping.

Action: Correct the configuration to make the correct API call.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04043: Null parameter value not supported.

Cause: Invalid parameter provided

Action: Correct the API call invocation.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04044: Failed to sort on field {0}.

Cause: Invalid sort field.

Action: Invoke the search operation with Comparable sort fields
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04045: Failed to read the attribute to operations mapping configuration. Using defaults.

Cause: Unable to read the attribute to operations mapping properties file.

Action: Correct the configuration to make the correct API call.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04046: Invalid mapping {0} found for attribute type {1}.

Cause: Invalid attribute type to operations mapping.

Action: Correct the configuration to make the correct API call.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04047: Service {0} is not running.

Cause: Service has failed to start up or during operations.

Action: Attempt to restart server.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04048: Cache member joined: {0}, service: {1}.

Cause: Cache cluster member has joined the service.

Action: None
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-04049: Cache member leaving: {0}, service: {1}.

Cause: Cache cluster member is leaving the service.

Action: None
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-04050: Cache member left: {0}, service: {1}.

Cause: Cache cluster member has left the service.

Action: None
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-04051: Listener in {0}, Thread {1} before lock, dist version {2} config version {3}.

Cause:

Action: None
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-04052: File change listener in {0}, Thread {1} before lock, dist version {2} file version {3}.

Cause:

Action: None
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-04053: Exception on notification event {0} for listener {1}.

Cause:

Action: None
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04054: Failed to submit notification for {0}. Current queue size is {1}.

Cause:

Action: None
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04055: Failed to create mapstore statistics file.

Cause:

Action: Verify that the default output filesystem is writeable.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-04501: Exception on finalize of component {0}.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04502: Exception on bootstrap of component {0}.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04503: Distribution event of version {0} received for config of version {1}.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04504: Received null object as distribution event.

Cause: A null object was received as the distribution event.

Action: Verify the distributed data at the origin.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04505: Cannot handle distribution notification.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04506: Cannot acquire lock for configuration update.

Cause: Unable to acquire lock for configurable update.

Action: Identify source of contention and remove it.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04507: Cannot upload physical file change to configuration.

Cause: Unable to upload physical file change to configuration.

Action: Verify that the physical file is well formed.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04508: Mxbean attribute is null.

Cause: The Mxbean attribute was null.

Action: Size of document may be large causing this failure.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04509: Cannot handle config change notification.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04510: Starting upgrade from {0} to {1} ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-04511: Running {0} ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-04512: Finished upgrade from {0} to {1}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-04513: Source configuration path {0} is not specified, or is an invalid value.

Cause: Configuration path not specified for upgrade source, or is invalid value.

Action: Provide a valid configuration path.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04514: Destination configuration path {0} is not specified, or is an invalid value.

Cause: Configuration path not specified for upgrade destination, or is invalid value.

Action: Provide a valid configuration path.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04515: Configuration path {0} is not a valid file.

Cause: Provided path does not resolve into a valid file.

Action: Provide a path to a valid configuration file.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04516: Initialization of configuration copy failed {0}.

Cause: Configuration initialization failed.

Action: Verify the contents of the configuration file.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04517: configuration upgrade failed for component {0}.

Cause: Configuration upgrade failed.

Action: Rectify the cause of the failure.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04518: Failed to build configuration build settings.

Cause: Configuration setting for upgrade is not valid.

Action: Rectify the cause of the failure.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04519: Upgrade action request {0} is not valid.

Cause: Requested upgrade action invalid.

Action: Rectify the action request.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04520: Destination configuration does not support data type {0} requested at path {1}.

Cause: Provided configuration map value is not supported in destination configuration.

Action: Transform the map value to a supported data type.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04521: Destination configuration path {0} overwrites value {1} at element {2}.

Cause: Destination path will overwrite value.

Action: Change upgrade instructions to prevent path from overwriting values.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04522: Map destination path {0} will overwrite preserved path {1}.

Cause: Destination path will overwrite value.

Action: Change upgrade instructions to prevent path from overwriting values.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04523: Exception occured during write of configuration for examination.

Cause: Failure to write configuration for examination.

Action: Correct the cause of the associated exception.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04524: Failed to create path {0}.

Cause: Creation of folder or file specified by path failed.

Action: Verify that the path can be written to, and that sufficient disk space exists.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-05001: Unable to read configuration setting {0}, during Journal initialization.

Cause: An internal error occurred while initializing a Journal.

Action: For more details, start logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-05002: Invalid value {0} for parameter {1} was passed for Journal operation {2}, in instance {3}.

Cause: An invalid parameter value was passed to the Journal operation.

Action: For more details, start logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-05003: Unable to acquire lock on journal data for operation {0}, in instance {1}.

Cause: A lock might have already been acquired by another thread, or there was an internal failure.

Action: For more details, start logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-05004: Journal entry with version {0} already exists in instance {1}.

Cause: A journal entry with the version already exists.

Action: Use a different version for the journal entry.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-05005: Journal entry for version {0} does not exist in instance {1}.

Cause: A journal entry for the version doesn't exist.

Action: Check version of the journal entry.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-05006: Unable to read Journal implementation name for instance {0} , using default name {1} instead.

Cause: Journal implementation name is not set in journal config setting.

Action: For more details, start logging at FINE level.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-05007: Journal configuration setting for instance {0} , key = {1}, value = {2}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-05008: Journal data in instance {0}: type = {1}, value = {2}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-05009: Source is not a OAM11gR1 config file, version expected: "{0}", found: "{1}".

Cause: The source OAM config file does not belong to a OAM 11gR1 instance.

Action: Make sure config file from OAM 11gR1 instance is passed as source for upgrade.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-05501: Configuration for REST services not found.

Cause: Configuration file does not contain REST configuration

Action: Configure OAM for REST services.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-05502: Class declaration {0} is invalid.

Cause: REST class declaration is invalid.

Action: Correct the class declaration.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-06001: Policy Service: {0} : {1} : {2} : {3}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06002: Create : {0} : paramList=[{1}].

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06003: Created : {0} : {1}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06004: Modify : {0} : Existing=[{1}] : New=[{2}].

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06005: Modified to : {0} : {1}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06006: Delete : {0} : name="{1}".

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06007: Deleted : {0} : name="{1}".

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06008: Read : {0} : name="{1}".

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06009: After Read : {0} : {1}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06010: Read All : {0}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06011: After Read All : {0} : list is : {1}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06012: Initialize Parameter list is {0}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06013: PolicyRuntime :: paramName="{0}", paramDetail="{1}".

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06014: Unable to initialize Policy Runtime Provider.

Cause: An invalid configuration.

Action: Try again by setting proper configuration.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06015: Exception encountered while processing get authentication scheme request!

Cause: An internal exception occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06016: Unable to reload the policy data for runtime.

Cause: An internal exception occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06017: Exception encountered while creating runtime responses.

Cause: An internal exception occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06018: Unable to load cache.

Cause: An internal exception occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06019: Unable to load host identifiers from policy store.

Cause: An internal exception occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06020: Exception encountered while evaluating authentication policy.

Cause: An internal exception occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06021: Unable to obtain conditions from authorization policy.

Cause: No conditions were found.

Action: Check if policy has conditions and try again.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06022: Unable to obtain InetAddress from given IP Address.

Cause: An invalid IP Address was supplied.

Action: Check if the IP Address is valid (Only IP version 4 is supported). Try again with valid IP Address.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06023: Unable to determine the host identifier matching the request. Resource: {0}.

Cause: No host identifier was configured for incoming resource.

Action: Update the policy, add the host identifier to the given resource and try again.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06024: Unable to process Runtime Resource for getting URL path.

Cause: An invalid incoming resource URL.

Action: Correct the resource URL and try again.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06025: Exception encountered while adding to the bucket.

Cause: An internal exception occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06026: Object {0} with the name already exists.

Cause: That name has already been used to create an object.

Action: Modify the name and try to create the object once again.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06027: Error while creating input stream for the policy file.

Cause: An internal error occurred. One of the many cause can be policy file not found.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06028: Error while creating a new policy distributor instance.

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06029: ID of an element cannot be NULL.

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06030: Error while retrieving DATA SOURCE and RESPONSE TYPE values from policy.xml!

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06031: Error while retrieving the condition type.

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06032: Error while creating jaxb marshaller/unmarshaller.

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06033: Error while unmarshalling. Data may be corrupt in policy.xml

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06034: Policy data write failed with exception.

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06035: Error while creating input stream for policy file.

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06036: Cannot find the file "{0}" in the classpath or on the filesystem

Cause: The policy file was not in the classpath.

Action: Add policy file to the classpath and run the program again.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06037: XML data validation Error. Data in the input XML String maybe corrupt.

Cause: The policy file was invalid.

Action: Validate policy file against the schema and run the program again.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06038: Validation Error while unmarshalling. Data in the input XML String maybe corrupt.

Cause: The policy file was invalid.

Action: Validate policy file against the schema and run the program again.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06039: Cannot create temporal condition. Require either DayOfWeek or TimeOfDay.

Cause: The attribute required to create a temporal condition was not valid.

Action: Either DayOfWeek or TimeOfDay is missing. Add the required attribute and run the program again.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06040: Invalid condition type "{0}" found in the policy store.

Cause: An internal error occured.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06041: Unable to distribute policy changes.

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06042: Null passed during modify operation.

Cause: Object passed to modify operation was null.

Action: Rerun with actual object.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06043: Name cannot be null.

Cause: During object creation, name value was null.

Action: Rerun the operation with a valid name.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06044: Name {0} exceeds maximum allowed length of {1} characters.

Cause: During object creation, invalid name attribute was passed.

Action: Rerun the operation with a valid name attribute.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06045: An object of this type named "{0}" already exists.

Cause: Policy object names must be unique for each object type and scope (global or domain).

Action: Choose a different name for this object.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06046: Mandatory attribute "{0}" is missing.

Cause: A required attribute was missing during policy object creation.

Action: Rerun the operation with the required attribute. When authn-level is the required attribute, set a positive value and rerun the operation.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06047: "name" or "description" attribute missing in Module Property.

Cause: A name or description attribute was missing in a module property.

Action: Rerun the operation with required attribute set.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06048: Policy Object: {0} no longer exists.

Cause: Policy object requested for removal was not found in the store; likely it has already been removed by another administrator.

Action: None, the object has been removed.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06049: Module cannot be deleted. (Referred in Scheme).

Cause: Module is being referred to in the scheme.

Action: Remove the reference from the scheme and then delete the module.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06050: NULL passed during isDefaultAuthnScheme operation.

Cause: Null passed while performing the default authn scheme operation.

Action: Rerun the operation with the valid scheme.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06051: One of the challenge parameter key values is empty.

Cause: A challenge param key value was empty.

Action: Set the proper key value and then rerun the operation.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06052: Challenge Redirect URL is invalid.

Cause: An invalid Challenge Redirect URL was entered.

Action: Rerun the operation with valid challenge URL value.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06053: Challenge URL is null.

Cause: The URL entered is null.

Action: Re-run the operation with a valid URL value.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06054: Scheme referring to invalid authentication module.

Cause: The scheme was referring to an invalid authentication module.

Action: Rerun the operation after setting a valid authentication module.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06055: Scheme cannot be deleted. Referenced in an existing authentication policy.

Cause: The scheme is being referred to in a policy.

Action: Remove the reference from the policy and then delete the scheme.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06056: Default authentication scheme cannot be deleted.

Cause: An attempt was made to delete the default authentication scheme, which is not allowed.

Action: Rerun the operation with another authentication scheme.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06057: Invalid host format.

Cause: The host format was invalid.

Action: Rerun the operation with a valid host.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06058: Host "{0}" already exists under host identifier "{1}".

Cause: The host is already part of a host identifier.

Action: Remove the host from the other host identifier and then retry.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06059: Host Identifier cannot be deleted. (Referred to in a resource).

Cause: Host is being referred to in a resource.

Action: Remove the reference from the resource and then delete the host.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06060: Resource "{0}" does not exist in the application domain.

Cause: Resource does not exist in the application domain.

Action: Use a valid resource that exists in the application domain.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06061: Resource "{0}" cannot be added to this policy, as it is already referenced by {1} Policy "{2}".

Cause: A resource can only be associated with a single policy of a given type.

Action: Remove the resource from the named policy and try again.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06062: A resource type name cannot start with a number.

Cause: Resource type names must start with a letter.

Action: Remove the numeric characters from the start of the name.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06063: Invalid operation format.

Cause: The operation list was invalid.

Action: Rerun the operation with a valid operation list.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06064: HostIdentifier is null.

Cause: A null HostIdentifier was passed to the operation.

Action: Rerun the operation with a valid host identifier.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06065: Invalid HostIdentifier.

Cause: No HostIdentifier was found in the policy.

Action: Rerun the operation with a valid host identifier.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06066: Unable to fetch HostIdentifier manager.

Cause: An internal error occurred..

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06067: Resource URL format is not valid.

Cause: URL * was not followed by a .extension, or URL pattern (*any string) * was not followed by a character string, or URL * was preceeded by a string (e.g. checking*.jsp is invalid), or URL pattern was invalid (e.g. "..." pattern is only allowed once).

Action: Rerun the operation with a valid resource url.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06068: Cannot delete resource, as it is referenced by {0} Policy "{1}".

Cause: A resource currently in use cannot be deleted.

Action: Delete the resource from the named policy and try again.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06069: Token issuance policies can not contain responses.

Cause: Token issuance policies can not contain responses.

Action: Remove the responses.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06070: Unable to obtain policy manager for application domain id: "{0}"

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06071: Temporal condition validation failure for {0}.

Cause: Missing day of the week or time of the day required to create temporal condition, or no day selected in day of the week condition, or begin and end time not supplied for temporal condition, or end time is less than begin time.

Action: Rerun the operation with a valid Temporal condition.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06072: Identity condition validation failure for {0}.

Cause: User or group list was not supplied for identity condition creation, or users list was empty, or group list was empty.

Action: Rerun the operation with a valid Identity condition.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06073: IP4Range condition validation failure for {0}.

Cause: A null value was present in either start or end range.

Action: Rerun the operation with valid a IP4Range condition.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06074: {0} does not exist, id = {1}

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06075: Unable to obtain a host identifier for the input name : hostIdName = {0}.

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06076: Time of Day condition is not created as either begin time or end time is missing.

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06077: Cannot create condition object.

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06078: Error while creating condition of type: "{0}".

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06079: Error while reading response with name = "{0}".

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06080: Error while creating response from policy store object with name = "{0}".

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06081: Cannot open file.

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06082: Exception occurred while converting admin elements to runtime elements.

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06083: No Client IPAddress found in AccessContext Map.

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06084: Null Authentication Scheme Id.

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06085: Constraints not supported for Authentication Policy. Pass null during Constraint creation.

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06086: OAM Admin Provider class not found : "{0}".

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06087: Unable to instantiate OAM Provider class : "{0}".

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06088: OAM provider class in the configuration does not implement PolicyAdminProvider: "{0}".

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06089: OAM Runtime Provider class not found : "{0}".

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06090: Unable to instantiate OAM Runtime Provider class : "{0}".

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06091: OAM provider class in the configuration does not implement PolicyRuntimeProvider: "{0}".

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06092: Cache entry expired.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06093: Error while reading policy result cache size from configuration.

Cause: Cache configuration was invalid.

Action: Fix the cache configuration and the rerun the operation.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06094: Policy result cache is enabled.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06095: Registering PolicyDiagnosticConfigMediator.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06096: Successfully registered PolicyDiagnosticConfigMediator.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06097: Failed to register PolicyDiagnosticConfigMediator.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06098: Resource "{0}" already exists in policy "{1}".

Cause: The resource already exists as part of an Authentication/Authorization Policy.

Action: Rerun the operation using another resource.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06099: Response "{0}" already exists in policy "{1}".

Cause: The response already exists as part of an Authentication/Authorization Success/Failure List.

Action: Rerun the operation using another response.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06100: Condition "{0}" already exists in policy "{1}".

Cause: The condition already exists as part of an Authorization policy.

Action: Rerun the operation using another condition.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06101: Policy change record number: "{0}".

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06102: Unable to process policy change event for change record number: "{0}".

Cause: An internal exception occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06103: Unable to acquire write lock on the XML policy store file, for change record number: "{0}".

Cause: The XML policy store file is locked by another thread for more than the configured wait time.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06104: Success URL is invalid.

Cause: The success redirect URL was invalid..

Action: Rerun the operation with a valid URL.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06105: Failure URL is invalid.

Cause: The failure redirect URL was invalid.

Action: Rerun the operation with a valid URL.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06106: Resource URL is invalid.

Cause: The resource URL entered is invalid.

Action: Re-run the operation with valid resource URL value.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06107: Description for field {0} exceeds maximum allowed length of {1} characters.

Cause: During object creation, invalid description attribute is passed.

Action: Re-run the operation with valid description attribute.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06108: Operation list is empty.

Cause: During object creation, invalid operation list attribute is passed.

Action: Re-run the operation with valid operation list attribute.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06109: Resources belonging to a policy must be of the same type.

Cause: The policy already contains resources of another type.

Action: Apply the resource to a different policy.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06110: Resource type must not be null.

Cause: Resource type must not be null.

Action: Set the resource type.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06111: Unable to find HTTP resource type.

Cause: The required HTTP resource type does not exist.

Action: Create a new resource type with name "HTTP".
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06112: Application Domain should be empty before it is deleted.

Cause: Application Domain is not empty.

Action: Delete all resources and policies in an application domain before deleting the domain.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06113: The resource URL cannot contain a query string.

Cause: The resource URL cannot contain a query string.

Action: Remove the query string component from the resource URL.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06114: The requested method is not supported by this policy object type.

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06115: An unsupported operation was unexpectedly requested.

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06116: A host identifier or resource type named "{0}" already exists.

Cause: Names of host identifiers or resource types must be unique across both sets of objects.

Action: Choose a different name for this object.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06117: An unsupported operation was unexpectedly requested.

Cause: Exception while getting host identifier.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06118: Policy admin update event distribution setting : "{0}".

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06119: Policy admin update event distribution is disabled.

Cause: Policy admin update event distribution is disabled

Action: Check the policy configuration setting for policy admin update event distribution
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06120: Host identifier doesn't exist for the given host and port.

Cause: There is no host identifier associated with the given host and port.

Action: Check the input host and port information.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06121: Policy runtime change event distribution failure, invalid (NULL) Journal instance.

Cause: An internal exception occurred while distributing policy runtime change events.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06122: Policy runtime provider {0}, does not accept policy change events.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06123: Policy runtime provider {0}, accepts policy change events.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06124: Exception encountered while fetching current policy version from policy store.

Cause: An internal error occurred while fetching current policy version from policy store.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06125: Policy data refresh by policy runtime engine did not complete after {0} time, hence policy cache is not refreshed.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06126: Exception encountered while refreshing policy cache by policy runtime.

Cause: An internal error occurred while refreshing policy cache by policy runtime.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06127: Exception encountered while handling policy change event {0} by policy runtime.

Cause: An internal error occurred while handling policy change event by policy runtime.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06128: Policy data version in policy store is {0}

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06129: Issued policy data refresh to policy runtime engine

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06130: Skipping the addition of policy change record {0} to the Journal as policy admin provider returned the same version previously.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06131: Type "{0}" cannot be deleted, as one or more resources of this type exist.

Cause: Resources of the resource type to be deleted exist.

Action: Remove these resources, then try again.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06132: A runtime resource must contain a URL.

Cause: The resource asscociated with the runtime request did not contain a URL.

Action: Create the request with a valid resource.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06133: An HTTP runtime resource must contain a relative URL path. Resource: "{0}".

Cause: The resource URL associated with the runtime request was not relative.

Action: Ensure thst the resource URL is relative, starting with '/'.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06134: Unable to match a resource type for the requested resource: request="{0}".

Cause: No resource type was configured for the requested resource.

Action: Add the required resource type.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06135: Only querying policies from policy store ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06137: Where <properties-file> should contain the following properties:

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06138: policy-admin-provider-class=<provider-class-name>

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06139: policy-admin-provider-name=<provider-name>

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06140: <provider-name>.<provider-property-name>=<provider-property-value>

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06141: ... list of provider properties.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06142: Adding OAM policy objects ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06143: Disabled policy distribution for XML provider

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06144: Adding OAM WLS Agent policy objects ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06145: Input properties:

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06146: Adding OIM policy objects ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06147: Adding OAAM policy objects ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06148: Adding OIF policy objects ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06149: Adding Fusion Applications policy objects ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06150: Verifying OAM policy objects ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06151: Verifying IDM Domain Agent policy objects ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06152: Verifying OIM policy objects ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06153: Verifying OAAM policy objects ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06154: Verifying OIF policy objects ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06155: Verifying Fusion Applications policy objects ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06156: Done.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06157: Fetching "{0}" resource type ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06160: Checking to confirm "{0}" as default authentication scheme ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06161: "{0}" is the default authentication scheme.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06162: "{0}" instead of the expected "{1}" is the default authentication scheme!

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06166: Fetching "{0}" host identifier ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06167: Fetching "{0}" application domain ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06168: Fetching resources ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06169: Fetching authentication policies ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06170: Fetching authorization policies ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06171: Fetching OIMHostIdentifier host identifier ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06172: Fetching OIMScheme authentication scheme ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06173: Fetching OIM Integration application domain ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06174: Fetching OAAMBasic authentication scheme ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06175: Fetching OAAMAdvanced authentication scheme ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06176: Fetching OIFScheme authentication-scheme object ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06177: Fetching wl_authen resource type ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06178: Fetching Fusion Apps Integration application domain ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06179: Invalid usage!

Cause: Command line arguments passed were invalid.

Action: Rerun the command with correct arguments.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06180: Property file location argument is missing!

Cause: Property file location is invalid.

Action: Provide the correct property file location.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06181: Error! PolicyFile: "{0}" already exists! Remove this file before running the tool.

Cause: Policy file already exists.

Action: Remove this file before running the tool.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06182: Policy object not found!

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06183: Global default domain not yet setup!

Cause: Global default domain is not setup.

Action: Create global default domain.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06184: VM Property not set: "{0}"

Cause: Required JVM property was not set.

Action: Set the required JVM property.
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06185: Policy cannot make use of both specific and default schemes.

Cause: An authentication policy cannot use both a specific, named scheme and the default one.

Action: Ensure the policy uses either a specific scheme or the default one, not both.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06186: Unable to initialize PolicyRuntimeProviderImpl! : "{0}".

Cause: PolicyRuntime provider could not be initialized.

Action: Recheck the oes settings and modify accordingly.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06187: Invalid IP address on range check, IP address was: "{0}".

Cause: An IP address was provided out of range.

Action: Provide correct IP address.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06188: App Domain Manager not setup.

Cause: App domain manager was not set up.

Action: Setup domain manager.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06189: Extension manager not found.

Cause: Extension manager was not set up.

Action: Setup extension manager.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06190: The host: "{0}" occurs more than once in the host identifier: "{1}".

Cause: Same host entry is specified more than once in a host identifier.

Action: Ensure same host is not added more than once to a host identifier.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06191: The runtime request is null or contains no resource.

Cause: The runtime request, or the resource associated with the request, was null.

Action: Create the request with a proper resource.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06192: The runtime request contains no identity.

Cause: The identity associated with the runtime request was null.

Action: Create the request with a proper identity.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06193: Unable to process policy distribution event.

Cause: The policy admin provider failed to apply the changes contained in the event.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06194: Verifying OAM10g policy objects ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06195: Fetching OAM10gScheme authentication scheme ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06196: Adding OAM10g policy objects ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06197: Policy contains multiple constraints of class {0} and type {1}.

Cause: Each constraint class/type combination can appear at most once within a policy.

Action: Modify the policy to ensure that multiple constraints of the same class and type are not present.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06198: Authentication scheme {0} not found.

Cause: Authentication scheme not found in store

Action: Ensure that the authentication scheme has been created.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06199: Multiple resources exist for Authentication scheme {0}.

Cause: Authentication scheme is represented by multiple resources.

Action: Ensure that the data in the OES store is valid.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06200: Waiting for policy distribution ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06201: Waited {0} ms for policy distribution to complete ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06202: Distribution completed, total time taken was: {0}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06203: Distribution did not complete within the configured maximum wait time of {0} ms.

Cause: Policy distribution did not complete within maximum wait time alloted.

Action: Increase the maximum wait time for policy distribution in the config file.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-06204: Condition "{0}" is of a type which cannot be used in a token issuance policy.

Cause: Only some types of conditions can be used with a token issuance policy.

Action: Use only conditions of types which are compatible with this policy.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06205: Resource "{0}" is of a type which cannot be used in a token issuance policy.

Cause: Only some types of resources can be used with a token issuance policy.

Action: Use only resources of types which are compatible with this policy.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06206: The token requestor identity condition validation failed for {0}.

Cause: None of partner, user or group information was provided for condition creation.

Action: Provide at least one of partner, user or group information for condition creation.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06207: Only HTTP resources can have a protection level of Excluded.

Cause: An attempt was made to set the protection level of a non web resource to excluded.

Action: The protection level of non web resource can be either protected or unprotected.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06208: Excluded resource: {0}, cannot have a policy associated.

Cause: An attempt was made to associate a excluded resource with a policy.

Action: Change the protection level to either protected or unprotected to create a policy around this resource.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06209: Resource protection level is null.

Cause: Resource protection level was set to null.

Action: Resource protection level should be set to valid values.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06210: Unprotected resource {0} cannot be associated with this policy, as it uses a non-anonymous authentication scheme.

Cause: Unprotected resources cannot be associated with this policy, as it uses a non-anonymous authentication scheme.

Action: Change the protection level of the resource(s) to Protected before adding to the policy.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06211: Protected resource {0} cannot be associated with this policy, as it uses an anonymous authentication scheme.

Cause: Protected resources cannot be associated with this policy, as it uses an anonymous authentication scheme.

Action: Change the protection level of the resource(s) to Unprotected before adding to the policy.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06212: Invalid request: isTokenRequestAuthorized calls cannot be made for HTTP resources.

Cause: An attempt was made at runtime to evaluate token issuance policy for HTTP resource.

Action: Make sure that at runtime HTTP resource is not used when evaluating Token issuance policies.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06213: Could not find application domain for Id: {0}, name: {1}.

Cause: Provided Application domain was not found in the store.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06214: Could not find hostIdentifier for Id: {0}.

Cause: Provided host identifier was not found in the store.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06215: Could not find hostIdentifier for name: {0}.

Cause: Given host identifier name was not found in the store.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06216: Could not find store entry for application domain Id: {0}.

Cause: No entry was found in the store for the given application domain Id.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06217: Excluded resource: {0} is not associated with the exclusion policy.

Cause: An excluded resource in the store was not associated with the exclusion policy.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06218: Invalid store resource name {0}.

Cause: The store resource name entry was found to be invalid.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06219: Invalid operation name: {0}, operation name cannot end with string: {1}.

Cause: The resource type operation name is invalid.

Action: Modify the operation name for the resource type.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06221: Exception while decrypting OES credentials.

Cause: An exception occured while decrypting store credentials.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06222: Could not find the exclusion policy in the store from which to remove resource: {0}.

Cause: The exclusion policy was not found in the store from which the resource was requested to be removed.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06223: Creating authentication scheme: {0}...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06224: Creating resource type: {0}...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06225: Creating host identifier : {0}...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06226: Creating application domain : {0}...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06227: Creating custom resource : {0}...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06228: Creating web resource : {0}...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06229: Creating authentication policy: {0}...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06230: Creating authorization policy: {0}...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06231: Enter policy database password:

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06232: Authentication scheme "{0}" would be created.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06233: Host identifier "{0}" would be created.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06234: Resource type "{0}" would be created.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06235: Application domain "{0}" would be created.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06236: Default authentication scheme would be set to scheme {0}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06237: Skipping creation of scheme: {0} because the scheme already exists.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06238: Skipping creation of host identifier {0} because it already exists in the store.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06239: Skipping creation of resource type: {0} because the resource type already exists in the store.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06240: Skipping creation of application domain: {0} because the domain already exists in the store.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06241: Insufficient arguments: missing policy store location.

Cause: Policy Store file name and location is missing.

Action: Policy Store file name and location needs to be provided.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06242: Fetching "{0}" authentication scheme ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06243: Initializing database policy admin provider.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06244: Initializing database policy runtime provider.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06245: Ignoring host identifier: "{0}", since this has been renamed to: "{1}" in {2}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06246: Ignoring application domain: "{0}", since this has been renamed to: "{1}" in {2}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06247: Running in examine mode; simulating insertion of migrated policy objects into the live policy store.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06248: Adding TAP policy objects ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06249: Verifying TAP policy objects ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06250: Fetching TAPScheme authentication-scheme object ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06251: Unsupported policy store version detected. Required "{0}" but found "{1}".

Cause: The version of policy store is not compatible with OAM version.

Action: Make sure OAM is configured to talk to correct version of policy store.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06252: The policy store is not available; please see the log file for more details.

Cause: Policy store could not be instantiated. Database schema may be out of date

Action: In case of database schema errors schema needs to be updated.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06253: Database schema is not valid.

Cause: Database schema is missing or requires update.

Action: Update the database schema.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06254: Profiling started, strategy: {0}, amount: {1}, mechanism: {2}

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06255: Profiling report for {0}: {1} ops, {2}/{3}/{4} avg/min/max (ms)

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06256: Profiling ended.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06257: All hosts from R1 host identifier {0} would be migrated to PS1 host identifier {1}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06258: The authentication scheme of authentication policy {0} would be modified to {1}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06259: Extra resource(s) were found in R1 {1} Protected policy. The following will need to be recreated manually after the upgrade is complete: {0}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06260: The LDAP filter {0} match for user {1} and identity domain {2} failed.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06261: The LDAP filter search not executed because there was no DN for user {0}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06262: The LDAP filter {0} match for user {1} and identity domain {2] was successful.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06263: No user identity provider for domain {0} could be found.

Cause: No user identity provider could be found for the given domain.

Action: Check if the relevant userstore configuration was deleted.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06264: Error getting the user identity provider for domain {0}.

Cause: Unknown error while fetching the user identity provider for the given domain.

Action: Check the relevant userstore configuration
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06265: The IP4 Address {0} is not valid.

Cause: The IP4 address specified is invalid.

Action: Specify a valid IP4 address. This should be in the dotted decimal format xxx.xxx.xxx.xxx, where xxx is a number between 0 and 255.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06266: The "From" address {0} in the IP4 range is greater than the "To" address {1}.

Cause: The From address in the IP4 range is greater than the "To" address in the IP4 range.

Action: Update the IP4 range so that the "To" address is greater than the "From" address.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06267: Condition {0} does not contain any attributes.

Cause: Attribute list was not supplied for condition creation.

Action: Rerun the operation with a valid attribute list.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06268: Condition {0} contains an unset attribute name.

Cause: An attribute name was not supplied for condition.

Action: Rerun the operation with a valid attribute name.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06269: Condition {0} contains an unset attribute value.

Cause: An attribute value was not supplied for condition.

Action: Rerun the operation with a valid attribute value.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06270: Resource type {0} cannot be created as read-only, or modified if already read-only.

Cause: A policy admin cannot create/update/delete read-only resource type without permission to do so.

Action: Do not attempt to manipulate a read-only resource type.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06271: One or more operations cannot be created as read-only, or modified if already read-only.

Cause: A policy admin cannot create/update/delete read-only opertion(s) without permission to do so.

Action: Do not attempt to manipulate a read-only operation within a resource type.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06272: Operation {0} can not be used, because it does not exist for the type of this resource.

Cause: An invalid operation, one which does not exist for the resource's type, was used.

Action: Ensure that the operations added to a resource are a subset of those defined for its resource type.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06273: Policy contains more than one rule for rule effect "{0}".

Cause: More than the allowed single rule per rule effect was present..

Action: Create the policy using a single rule per rule effect.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06274: At least one of the policy rules must hold conditions selected for evaluation.

Cause: A policy using the simple rule mode needs one or more of the rules to contain conditions.

Action: Select conditions on at least one of the rules.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06275: Invalid condition name "{0}" specified in "{1}" rule.

Cause: A condition name was used within a rule, when no condition by that name exists.

Action: Use names of conditions which exist when creating rules.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06276: The same rule mode must be used across all rules contained in a policy.

Cause: More than one rule mode was used within the policy's rules.

Action: Use only one rule mode within a policy.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06277: Unable to process policy rule expression "{0}".

Cause: Policy rule expression processing failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06278: At least one of the policy rules must hold an expression for evaluation.

Cause: A policy using the expression rule mode needs one or more of the rules to contain expressions.

Action: Create a valid rule expression on at least one of the rules.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06279: Unexpected token "{0}" encountered at line "{1}", column "{2}" in the rule expression.

Cause: Rule expression contains invalid syntax.

Action: Use a valid rule expression in rules within a policy.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06280: Number of open and close braces do not match in the rule expression.

Cause: Rule expression contains invalid syntax.

Action: Use a valid rule expression in rules within a policy.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06281: Unable to escape special characters for condition name "{0}" to be used in rule expression.

Cause: Internal error encountered while processing condition name.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06282: Unable to remove previously escaped special characters for a condition name "{0}" that is used in the rule expression.

Cause: Internal error encountered while processing condition name.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06283: Condition name "{0}" used at line "{1}", column "{2}" in rule expression is not defined in the policy.

Cause: Rule expression refers to a condition which has not been defined within the policy.

Action: Use a valid rule expression in rules within a policy.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06284: Both a query string and query parameters are specified for the resource.

Cause: A resource can have a query string or parameters specified, but not both.

Action: Remove either the query string or the query parameters from the resou rce.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06285: Exception encountered during policy rule evaluation. Condition "{0}" does not exist in authorization policy.

Cause: Internal error encountered while evaluating policy rule.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06286: Rule expression token must have a type.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-06287: An HTTP runtime resource must contain a host name.

Cause: The resource associated with the runtime request did not contain a host name..

Action: Create the request with a valid resource.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06288: An HTTP runtime resource must contain a valid port number. Resource: "{0}".

Cause: The resource associated with the runtime request did not contain a valid port.

Action: Create the request with a valid port, between 0 and 65535 inclusive.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06289: This resource already exists, within domain "{0}".

Cause: Resources belong to different application domains, but must be globally unique.

Action: Either modify or remove the conflicting resource, or the elements of the one being created.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06301: Response tokenization failed for policy: "{0}" in domain: "{1}". Response details: "{2}".

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06302: Error thrown during response processing:

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06303: No provider registered to handle namespace: "{0}".

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06304: Provider failed to retrieve value for policy: "{0}" in domain: "{1}". Response details: "{2}".

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06305: Invoked provider for unsupported namespace: "{0}".

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06306: Invoked provider for unsupported variable name: "{0}".

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06307: Subject is missing from the request context.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06308: Expected user attribute not found.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06309: No attributes found in identity store for user: "{0}".

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06310: Provider registration requires a class instance and list of namespaces.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06311: Namespace must not be null.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06312: Provider already registered for namespace: "{0}".

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06313: Response token must have a type.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-06314: Variable namespace cannot be null.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06315: Session ID cannot be null or empty.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06316: Invalid session parameter name specified.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06317: Could not find session with id: "{0}".

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06318: Invalid variable reference: "{0}".

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06319: Variable name cannot be null: "{0}".

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06320: Invalid variable attribute reference: "{0}".

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06321: Expected session attribute not found.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06322: Cannot apply session response for policy: "{0}" in domain: "{1}". Response details: "{2}".

Cause: A session response could not be applied. The request was not made by an authenticated user, hence no session was associated with it.

Action: Do not set session responses on policies which are public, e.g. not requiring authentication.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06323: Adding Federation policy objects ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06324: Verifying Federation policy objects ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06325: Fetching Federation Scheme authentication-scheme objects ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06326: Adding TAP Response policy objects ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06327: Verifying TAP Response policy objects ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06328: Fetching TAP Response Scheme authentication-scheme objects ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06329: Policy store file with name {0} does not exist; creating it.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06330: An error occurred while writing to the policy store file: {0}.

Cause: Possible disk I/O error prevented creating or writing to policy store file.

Action: For more details, refer to log.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06331: Loading policy store file: {0}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-08001: Cannot get {0} value from configuration for key {1}. Object {2} found.

Cause: An attempt was made to access a configuration setting that does not exist.

Action: Verify configuration file.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08002: Cannot get wrapper class instance.

Cause: An attempt was made to access a wrapper class instance that does not exist.

Action: Verify configuration file.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08003: Type in configuration is not supported by utility for updates: {0}.

Cause: An invalid configuration type was specified.

Action: Verify configuration file.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08004: Implementation type {0} not present in path {1}.

Cause: The requested implementation was not specified in configuration file.

Action: Verify configuration files.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08005: Cannot get implementation for type {0}.

Cause: The requested implementation was not specified in configuration file.

Action: Verify configuration files.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08006: Factory methods not declared for type: {0}.

Cause: None.

Action: None.
Level: 15

Type: INFO

Impact: Other

OAMSSA-08007: Cannot find file {0} in the classpath or on the filesystem.

Cause: The configuration file was not found.

Action: Verify the configuration file location.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08008: No parameters are defined for method {0}.

Cause: An invalid configuration definition was supplied.

Action: Correct the configuration definition.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08009: Cannot retrieve method {0} from class {1} for setting {2}. Loading MethodObject instead.

Cause: An invalid configuration definition was supplied.

Action: Correct the configuration definition.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08010: Cannot notify listener of file {0}.

Cause: Notification error.

Action: Verify if notification listener is valid.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08011: Unknown file notification error.

Cause: File notifier error.

Action: Verify file change notification listeners.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08012: Stale data exception encountered for configuration version {0}.

Cause: File version is old.

Action: Refresh to the latest file version.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08013: Configuration update failed with errors.

Cause: Configuration update failed.

Action: Correct the cause of update failure.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08014: Configuration path is null.

Cause: Request path value is null.

Action: Provide the path parameter in method call.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08015: Configuration initial load failed for {0}.

Cause: Initial load of configuration failed.

Action: Verify that the configuration file exists and is valid.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08016: Configuration does not exist for path {0}.

Cause: Configuration for the path was null.

Action: Verify the path provided.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08017: Element {0} is not a map.

Cause: Configuration for the path was invalid.

Action: Verify the path.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08018: Instance identifier is null.

Cause: The input parameter was invalid.

Action: Validate the input parameter.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08019: Component at path {0} must contain Global, Profile, and Instance sections.

Cause: The configuration path was invalid.

Action: Validate the input parameter.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08020: File is locked for updates by context {0}.

Cause: An attempt was made to update a locked file.

Action: Release the lock before updating file from another context.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08021: Cannot acquire notification lock.

Cause: Lock is being held by other configuration service instances.

Action: Retry after a delay.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08022: Cannot apply compensating transaction on version:{0}.

Cause: Failure is due to a cause that does not allow restoration of original values.

Action: Verify file system.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08023: Instance at {0} does not specify a {1}.

Cause: Server instance definition incorrect.

Action: Correct the definition in the configuration file.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08024: Element type of xsd:string required at path {0}{1}{2}.

Cause: Server instance profile type should be of type string.

Action: Correct the definition in the configuration file.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08025: Profile {0} specified by {1} does not exist.

Cause: Server instance profile does not exist.

Action: Correct the definition in the configuration file.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08026: Profile {0} specified by {1} should be of type htf:map.

Cause: Server instance profile should be of type map.

Action: Correct the definition in the configuration file.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08027: Global section under {0} should be of type htf:map.

Cause: Server global section should be of type map.

Action: Correct the definition in the configuration file.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08028: Error parsing the configuration file {0}.

Cause: Error parsing the configuration file.

Action: Verify the configuration.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08029: Configuration file open error {0}.

Cause: An error occurred when opening the file.

Action: Verify the file location. Ensure that it is on the classpath or that its location is defined as a system property.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08030: Cannot get xml for configuration.

Cause: Cannot get xml for configuration.

Action: Correct the error indicated by the exception.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08031: Cannot load configuration from InputStream.

Cause: Cannot load configuration from InputStream.

Action: Correct the error indicated by the exception.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08032: Configuration event dispatch failed.

Cause: Dispatch of the configuration event failed.

Action: Correct the error indicated by the exception.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08033: Setting handler not found for type: {0}.

Cause: Configuration setting does not have a corresponding handler.

Action: Verify that the setting type is defined correctly.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08051: Configuration file is not loaded.

Cause: Configuration file was not loaded. See exception for cause.

Action: Correct the configuration file if it is badly formed.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08052: Configuration model is not found for object type {0}.

Cause: Configuration file was not loaded. See exception for cause.

Action: Correct the configuration file if it is badly formed.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-08053: Error during construction of configuration model instantiation.

Cause: Invalid configuration data.

Action: Verify the configuration data for correctness.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08054: Configuration file is not saved.

Cause: Configuration file was not saved. See exception for cause.

Action: Correct the configuration file if it is badly formed.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08055: Configuration file does not support List of Lists construct. Ignoring element {0}.

Cause: Configuration file has an unsupported data construct.

Action: Correct the configuration file if it is badly formed.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-08056: Path {0} and key set in the CompositeData {1} do not match.

Cause: Call made with inconsistent data.

Action: Correct the parameters of the call.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08057: Single valued data type found for multi-valued property on key {0}.

Cause: Call made on invalid data type

Action: Correct the parameters of the call.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08058: Multi-valued data type found for single valued property on key {0}.

Cause: Call made on invalid data type.

Action: Correct the parameters of the call.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08059: Operation returned type {0}. Expecting type {1}.

Cause: Property type accessed not found.

Action: Use the correct operation for the type.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08060: Cannot apply document to configuration. Exception message is {0}.

Cause: Document application failed.

Action: Use the correct operation for the type.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08061: Jar definitions provided for path {0} are invalid.

Cause: The path does not exist, or the jars are missing.

Action: Correct the configuration file with the right values.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08062: Jar definition {0} provided is invalid.

Cause: The path does not exist, or the jar is missing.

Action: Correct the configuration file with the right value.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08063: Distribution event of version {0} received for configuration of version {1}.

Cause: Distribution values are not updated with latest configuration settings.

Action: Restart the server to ensure that it is synchronized with other servers.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08064: Received null object as distribution event.

Cause: Some server has not placed the document on the distributor.

Action: Locate the server and restart it.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08065: Cannot handle distribution notification.

Cause: An unexpected failure.

Action: Diagnose the problem from the stacktrace and address it.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08066: Cannot find the map for key {0}

Cause: An attempt was made to add a value to a map that does not exist.

Action: Ensure that the map exists before adding the property for the map
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08067: Invalid data {0} provided for time interval

Cause: Invalid data provided for construction of time interval.

Action: Correct the data in the configuration file.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08068: Invalid data {0} provided for memory size.

Cause: Invalid data provided for construction of memory size.

Action: Correct the data in the configuration file.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08069: Configuration MBean not initialized.

Cause: Initialization failure during MBean startup.

Action: Verify the exceptions at startup and correct the cause of the error.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08070: Setting properties at path {0} not supported

Cause: path provided is invalid

Action: Correct the path provided.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08071: Unsupported configuration store version detected. Required "{0}" but found "{1}".

Cause: The version of config store is not compatible with OAM version.

Action: Make sure OAM is configured to talk to correct version of config store.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08072: Applying configuration update at path {0}. Current version of configuration {2}. Change initiated on this node: {1}

Cause:

Action: None
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-08073: Error occurred while accessing the System Identity Store.

Cause: Failure while processing the configuration or when accessing the System Identity Store.

Action: Verify the System Identity Store configuration and that the directory is up and running.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08074: User {0} is not authorized to invoke operation on the Oracle Access Management MBeans

Cause: The user does not have the privileges to access the MBeans.

Action: Verify the System Identity Store configuration to ensure the correct privileges are set.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-10001: SSO server token parsing failed.

Cause: The SSO server token was invalid.

Action: Verify the server token key size and algorithm configuration.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-10002: SSO server token Marshaling failed.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-10003: SSO Session is not valid.

Cause: The SSO session was missing, has been deleted, or has expired.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-10004: Initialization of the SME adapter failed.

Cause:

Action:
Level: 1

Type: INFO

Impact: Other

OAMSSA-10005: Initialization of the PAT Adapter failed.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAMSSA-10006: Initialization of the SSO Engine is complete.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAMSSA-10007: Created session with session Id {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAMSSA-10008: Retrieved session with session Id {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAMSSA-10009: SSO request token parsing failed.

Cause: The SSO request token was invalid.

Action: Verify the request token is invalid or truncated.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-10010: SSO request token Marshaling failed.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-12001: CSS Toolkit location {0} is invalid.

Cause: The CSS Toolkit location does not exist, or was not valid.

Action: Verify the CSS Toolkit location in the configuration.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-12002: CSS Configuration is not valid.

Cause: The CSS configuration in the configuration was invalid.

Action: Verify the CSS Toolkit location and configuration.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-12003: Cannot initialize CSS Authentication Module.

Cause: The CSS Authentication module configuration was invalid.

Action: Check the CSS Authentication module configuration. Verify the Identity store properties like DN, User and Search-bases.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-12004: Authentication using CSS Authentication Module failed.

Cause: An internal error occurred.

Action: Check the CSS Authentication module configuration. Verify the Identity store properties like DN, User and Search-bases.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-12005: Authentication Subject {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAMSSA-12006: Server Instance Name {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAMSSA-12101: Unable to register metrics for Authentication Engine with DMS.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-12102: Failed to initialize Authentication Engine Controller.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 1

Type: ERROR

Impact: Other

OAMSSA-12103: Unable to connect to User Identity Store.

Cause: The User Identity store was not running or the configuration was not valid.

Action: Verify that User Identity store is running and the configuration is valid.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-12104: Authentication Module Executor is unable to get configuration parameters.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

OAMSSA-12105: Cannot initialize authentication scheme executor.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

OAMSSA-12106: Authentication Failed.

Cause: The authentication was not successful.

Action: For more details, start logging at the FINE level.
Level: 1

Type: TRACE

Impact: Other

OAMSSA-12107: Invalid SPNEGO token in the request.

Cause: The SPNEGO token in the incoming request was either invalid or missing.

Action: For more details, start logging at the FINE level.
Level: 1

Type: SEVERE

Impact: Other

OAMSSA-12108: Invalid CallbackHandler in SPNEGO LoginModule.

Cause: The CallbackHandler was not initialized properly.

Action: Verify the configuration.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

OAMSSA-12109: Invalid Subject in SPNEGO LoginModule.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

OAMSSA-12110: Currently only value {0} is supported for parameter {1}.

Cause: An invalid value was supplied for a parameter.

Action: Rerun the operation with a valid parameter value.
Level: 1

Type: WARNING

Impact: Other

OAMSSA-12111: No user found in User Identity Store for the User certificate with certificate attribute {0} value {1}.

Cause: The mapping of the user certificate to an user entry was incorrectly configured.

Action: Verify the configuration.
Level: 1

Type: ERROR

Impact: Other

OAMSSA-12112: Cannot find the certificate of the OCSP server.

Cause: No OCSP server certificate was present in the keystore.

Action: Ensure that correct value is configured for the parameter OCSP_SERVER_CERT_ALIAS.
Level: 1

Type: ERROR

Impact: Other

OAMSSA-12113: Initialization of the X509ModuleExecutor failed.

Cause: The keystore file was missing, or could not be read.

Action: Verify the configuration.
Level: 1

Type: ERROR

Impact: Other

OAMSSA-12114: Initialization of the X509ModuleExecutor failed.

Cause: An internal error occurred.

Action: Verify the configuration setting for the CERTMAPPERCLASS parameter of X509 Authentication Module and ensure that the class is present in the classpath.
Level: 1

Type: ERROR

Impact: Other

OAMSSA-12115: Initialization of the X509ModuleExecutor failed.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 1

Type: ERROR

Impact: Other

OAMSSA-12116: Cannot find the user certificate.

Cause: An internal error occcurred.

Action: Verify the configuration and rerun this operation using a valid user certificate.
Level: 1

Type: WARNING

Impact: Other

OAMSSA-12117: Cannot validate the user certificate.

Cause: An internal error occurred.

Action: For more details, start loggin at the FINE level.
Level: 1

Type: ERROR

Impact: Other

OAMSSA-12118: Cannot load the configuration for authentication module {0}.

Cause: An internal error occurred.

Action: For more details, start loggin at the FINE level.Check the log file and correct the error.
Level: 1

Type: ERROR

Impact: Other

OAMSSA-12119: Multiple users found in User Identity Store for the User certificate with certificate attribute {0} value {1}.

Cause: The mapping of the user certificate to an user entry was incorrectly configured.

Action: Verify the configuration.
Level: 1

Type: ERROR

Impact: Other

OAMSSA-12120: Failed to map DN against identity store.

Cause: DN not found in Ldap store.

Action: Check DN and re-run the test.
Level: 1

Type: NOTIFICATION

Impact: Other

OAMSSA-12121: Failed to map GUID against identity store.

Cause: GUID not found in Ldap store.

Action: Check GUID and re-run the test.
Level: 1

Type: NOTIFICATION

Impact: Other

OAMSSA-12122: Unable to find the mapper class for DAPModuleExecutor.

Cause: Unable to find the mapper class.

Action: Check the DAP Module mapper class configuration
Level: 15

Type: ERROR

Impact: Other

OAMSSA-12123: Initialization of the DAPModuleExecutor failed.

Cause: DAPModule init failed.

Action: Check the DAP Module configuration.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-12124: No user found in User Identity Store for the DAP Token with username value {0}.

Cause: Username could not be found in the identity store.

Action: Check the incoming DAP assertion token.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-12125: No username found in DAP assertion token.

Cause: No username found in request.

Action: Check the incoming DAP assertion token.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-12126: Cannot assert the username from DAP token.

Cause: Cannot assert the username from DAP token

Action: Check the incoming DAP assertion token.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-12127: Retrieved Authentication Scheme {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAMSSA-12128: Runtime Authentication Scheme: {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAMSSA-12129: Authentication Scheme Id: {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAMSSA-12130: Result of Authentication Scheme Execution: {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAMSSA-12131: Configuration Property of Server Instance: {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAMSSA-12132: Failed to initialize the Policy Runtime.

Cause: The policy runtime configuration was invalid.

Action: Check the configuration.
Level: 1

Type: ERROR

Impact: Other

OAMSSA-12133: Failed to reload the authentication module.

Cause: The authentication module setting was invalid.

Action: Check the exception stack trace, update the configuration and try again.
Level: 1

Type: ERROR

Impact: Other

OAMSSA-12134: Failed to reload the authentication modules.

Cause: The authentication settings were invalid.

Action: Check the configuration.
Level: 1

Type: ERROR

Impact: Other

OAMSSA-12135: Authentication Module Factory Class: {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAMSSA-12136: Failed to initialize DAP Module during bootstrap.

Cause:

Action:
Level: 1

Type: NOTIFICATION.

Impact: Other

OAMSSA-12137: Failed to retrieve the encoded certificate bytes.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAMSSA-12138: Failed to Locate Server Instance with Configuration Property: {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAMSSA-14001: Authorization Engine :: paramName="{0}", paramValue="{1}".

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-14002: Unable to initialize authorization engine.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-14003: Policy runtime failed.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-16001: Token Processing Engine :: paramName="{0}", paramValue="{1}".

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-16002: Initialization of Module {0} failed.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-16003: Module {0} is null.

Cause: An internal error occurred.

Action: For more details, start loggin at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-16004: {0} was successful.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-16005: Configuration Entry is null.

Cause: No configuration was provided to initialize the token modules.

Action: Verify the configuration and rerun this operation.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-16006: Unable to instantiate/initialize {0} module. (class={1})

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-18001: Cert path validation failed.

Cause: The certificate is not valid.

Action: Check log message.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-18002: Error occurred when register trust store listener.

Cause: Misconfiguration

Action: Check certificate validation configuration.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-18003: Error occurred when unregister trust store listener.

Cause: Misconfiguration

Action: Check certificate validation configuration.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-18004: Error occurred when register Certificate Revocation List file listener.

Cause: Misconfiguration

Action: Check certificate validation configuration.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-18005: Error occurred when unregister Certificate Revocation List file listener.

Cause: Misconfiguration

Action: Check certificate validation configuration.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-18006: Error occurred when load trust store.

Cause: Trusted certificates key store doesn't exist or is in wrong format.

Action: Check trusted certificates key store.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-18007: Error occurred when load Certificate Revocation List file.

Cause: Certificate Revocation List file doesn't exit or is in wrong format.

Action: Check Certificate Revocation List file.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-19001: CRL JAR file does not exist.

Cause: CRL jar file is not configured at default location

Action: Make sure CRL jar file is configured at default location.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-19002: CRL Byte Array is null.

Cause:

Action: Make sure CRL jar file is not empty.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-19003: The CRL being added already exists.

Cause:

Action: Make sure CRL jar file is not empty.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-19004: The requested certificate type is not available in the default provider package or any of the other provider packages that were searched.

Cause:

Action: Enable logging to FINER level for more info.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-19005: Data in the input stream does not contain an inherent end-of-CRL marker (other than EOF) and there is trailing data after the CRL is parsed.

Cause:

Action: Check CRL jar file.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-19006: Information regarding CRL being removed is null.

Cause:

Action: Check CRL jar file.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-19007: Error occurred when trying to convert byte array to CRL object.

Cause:

Action: Enable logging to FINER level for more info.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-19008: The CRL to be removed does not match any of the existing CRL's.

Cause:

Action: Enable logging to FINER level for more info.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-20001: Initializing Oracle User Identity Provider.

Cause: Initialization of User Identity Provider called.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-20002: Diagnostic Engine Initialized.

Cause: Diagnostic Engine Initialized.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-20003: Initial Params : {0}.

Cause: Initialization called.

Action: None.
Level: 15

Type: FINE

Impact: Other

OAMSSA-20004: Registering Collectors.

Cause: Collector Registration called.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-20005: Error initializing User/Role API : {0}.

Cause: Initialization Error occurred.

Action: Check Initialization Parameters.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20006: Identity Provider Configuration not found for : {0}.

Cause: Id Store not found.

Action: Check configuration.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20007: Unable to connect to the User Store. User Store may not be initialized : {0}.

Cause: User Store not initialized.

Action: Check parameters.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20008: Oracle User Identity Provider Initialized.

Cause: User Id Store initialized.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-20009: Returning idStore : {0}.

Cause: Returned id store.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-20011: User not found : {0} : {1}.

Cause: User not found.

Action: Check entries in id store or configuration.
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-20012: Exception in getting user attributes for user : {0}

Cause: Get User Attributes call failed.

Action: Check configuration or id store entries.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20013: Returning with attribute values : {0}.

Cause: Get User Attributes Succeeded.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-20014: Failure getting users.

Cause: Get Users failed.

Action: None.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20015: Invalid start Index : {0}.

Cause: Invalid index provided for getting users.

Action: Check entries.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20016: Failure getting users by attribute : {0}, value : {1}.

Cause: Failed getting users by attribute.

Action: Check entries or configuration.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20017: Failure getting groups : {0}.

Cause: Could not retrieve groups.

Action: Check configuration or entries.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20018: Groups not found : {0}.

Cause: Groups not found.

Action: Check configuration or entries.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20019: Failure finding groups for user : {0} : {1}.

Cause: Failed finding groups for user.

Action: Check parameters, configuration, entries.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20020: Failed to create group : {0} : {1}.

Cause: Create Group call failed.

Action: None.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20021: Failed to assign user : {0} to group : {1} : {2}.

Cause: Failed to assign User to Group.

Action: Check configuration, parameters, LDAP entries.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20022: Failure getting principal : {0}.

Cause: Failed getting user principal.

Action: None.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20023: Authentication Failure for user : {0}.

Cause: Authentication failure occurred.

Action: None.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20024: Could not remove group : {0}.

Cause: Group removal failure occurred.

Action: Check configuration, entries, parameters.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20025: Failed to create user : {0}

Cause: Create User call failed.

Action: Check configuration, entries, parameters.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20026: Could not drop user : {0}.

Cause: Remove User failed.

Action: Check parameters, configuration, entries.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20027: Could not get user : {0}.

Cause: Get User failed.

Action: Check parameters, configuration, entries.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20028: Failure getting ECID : {0}.

Cause: getECID () failed.

Action: None.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-20029: ldapProviderStr is null. Hence defaulting to OID.

Cause: Configure Embedded LDAP Store called.

Action: None.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-20030: Invalid LDAP Provider specified: {0}, Supported providers : {1}.

Cause: Configure Id Store called.

Action: None.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20031: Invalid initialization parameters specified.

Cause: Configure Id Store called.

Action: None.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20032: Finished constructing mediator.

Cause: Diagnostic config mediator initialized.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-20033: Could not register IdentityProviderDiagnosticConfigMediator : {0}.

Cause: Failed adding idp mediator.

Action: None.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20034: Could not log metric : {0} and {1}.

Cause: Could not log metric.

Action: None.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20035: Could not log dynamic event for : {0}.

Cause: Could not log dynamic event.

Action: None.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20036: Could not log dynamic phase event : {0}.

Cause: Could not log dynamic phase event.

Action: None.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20037: Failed to check if user : {0}, is assigned to group : {1} : {2}.

Cause: Is User Assigned to Group call failed.

Action: None.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20038: Failed to test connection to : {0}.

Cause: Test Connection failed.

Action: None.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20039: Failed to re-initialize User Identity Provider : {0}.

Cause: User Identity Provider Re-initialization Failed.

Action: None.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20040: Could not modify user attribute for user : {0}, attribute : {1}, value : {2} .

Cause: Modify User Attribute call failed.

Action: None.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20041: Failed to get Role Mappings.

Cause: Get Role Mappings call failed.

Action: None.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20042: Error retrieving initial params : {0}.

Cause: getInitParams() failed.

Action: Check configuration.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20043: Error validating LDAP URL and credentials : {0}.

Cause: Test connection failed validation url and credentials.

Action: Check LDAP URL and credentials in provider configuration.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20044: Error validating User Search Base : {0}.

Cause: Test Connection failed validation of user search base.

Action: Check User Search Base in provider configuration.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20045: Error validating Group Search Base : {0}.

Cause: Test Connection failed validation of group search base.

Action: None.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20046: Group Search Base not found or has 0 elements or Role Security Admin is invalid.

Cause: Test Connection failed getting more than 0 entries in group search base.

Action: Check group search base in directory for entries, specifically OAM Role Security Admin.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20047: No entries were found under the User Search Base : {0} with attribute : {1}.

Cause: Test Connection failed getting more than 0 entries in user search base with the specified user name attribute.

Action: Check user search base in directory for entries or provide correct user name attribute.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20048: Invalid User Name Attribute : {0}.

Cause: User Name Attribute was invalid.

Action: Check if User Name Attribute is valid.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20049: Subscriber Name : {0} : has no entries.

Cause: Test Connection failed validation of Subscriber Name in directory.

Action: Check to see if the subscriber name attribute exists in directory.s
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20050: Subscriber Name not found or has 0 elements.

Cause: Test Connection failed getting more than 0 entries in subscriber name.

Action: Check subscriber name in directory for entries.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20051: Failure testing connection : {0}

Cause: Test Connection failed.

Action: Check parameters, entries, server.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20052: Authentication failed since user is locked in LDAP.

Cause: Authentication failure due to user locked in LDAP. Native attribute of LDAP is modified to lock the user.

Action: Contact LDAP Administrator to unlock the user in identity store.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20053: Failure matching parameters : {0}

Cause: Error matching config parameters to check if update is required.

Action: Check parameters, server.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20054: Invalid Role Security Admin : {0}

Cause: Invalid Role Security Admin specified.

Action: Check Role Security Admin parameter.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20055: IdentityProvider shutdown failure : {0}

Cause: Identity Provider shutdown failed.

Action: Check logs.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20056: Invalid canonical name : {0}

Cause: Invalid input parameter.

Action: Check logs.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20057: Invalid no. of elements in canonical name : {0}

Cause: Invalid canonical name input parameter.

Action: Check logs.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20058: Missing admin roles in role mappings : {0}

Cause: Some Admin Roles specified were missing.

Action: Check logs.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20059: Invalid Id Type in canonical name : {0}

Cause: Invalid Id type in canonical name.

Action: Check logs.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20060: Missing admin users in role mappings : {0}

Cause: Some Admin Users specified were missing.

Action: Check logs.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20061: Missing id in canonical name : {0}

Cause: Id missing in Canonical Name.

Action: Check logs.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20062: Exception occurred getting canonical name :

Cause: Exception occurred getting Canonical Name string.

Action: Check logs.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20063: Missing admin roles/users for system store

Cause: Admin users/roles not provided for system store.

Action: Provider Role Security Admin Groups/Users for id store.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20064: Failure getting users with search string: {0}

Cause: Failure getting users with the search string.

Action: Check supplied search string
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20065: Failure locating user : {0}

Cause: Failure locating specified user.

Action: Check configuration
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20066: Failure getting users with search string: {0}

Cause: Failure getting users with the search string.

Action: Check supplied search string
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20067: Failure getting users with search string: {0}

Cause: Failure getting users with the search string.

Action: Check supplied search string
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20068: Failure getting users with search string: {0}

Cause: Failure getting users with the search string.

Action: Check supplied search string
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20069: Failure locating user with search filter: {0} and arguments: {1}

Cause: Failure locating user with the search filter.

Action: Check supplied search filter and arguments.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20070: Failure locating user with search base: {0}. filter: {1} and arguments: {2}

Cause: Failure locating user with the search base and filter.

Action: Check supplied search base, filter and arguments.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20071: User {0} successfully authenticated - Password warning {1}

Cause: Password warning

Action: Check password expiration time.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-20072: Authentication failed since password is expired.

Cause: Authentication failure due to expired password.

Action: Contact LDAP Administrator to renew password in identity store.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20073: Principal object is not serializable; getGroups call will result in an extra LDAP call

Cause: Principal object is not serializable

Action: No action required; this error results in an extra LDAP call
Level: 15

Type: WARNING

Impact: Other

OAMSSA-20091: Embedded LDAP port configuration mismatch. Port {0} is defined for use, but this port is disabled.

Cause: The port for Embedded LDAP is disabled in application server configuration.

Action: Enable the port in server configuration.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-22001: Collectors Descriptions are null.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-22002: TraceFields Descriptions are null.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-22003: Specific Nouns class registered: "{0}".

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-22004: Collectors registered, from class: "{0}".

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-22005: Number of collectors registered: "{0}".

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-22006: Nouns Class registered: "{0}".

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-22007: Diagnostic Engine has been initialized.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-22008: Diagnostic Engine with rate metrics enabled, has been initialized.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-22009: Registering collector at runtime.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-22010: Collector: ["{0}":"{1}"], registered at runtime.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-22011: Diagnostic configuration changed.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-22012: Collection timer task restarted.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-22013: Persistence timer task restarted.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-22014: Rate calculation completed.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-22015: Timer Task interval is set to: "{0}".

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-22016: Persistence interval is set to: "{0}".

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-22017: Could not instantiate: "{0}", Exception is: "{1}".

Cause:

Action:
Level: 15

Type: WARNING

Impact: Other

OAMSSA-22018: Diagnostic Exception raised - "{0}".

Cause:

Action:
Level: 15

Type: WARNING

Impact: Other

OAMSSA-22019: Diagnostic Exception for Collector: "{0}".

Cause:

Action:
Level: 15

Type: WARNING

Impact: Other

OAMSSA-22020: DMS is not available, metrics won't be collected

Cause:

Action:
Level: 15

Type: WARNING

Impact: Other

OAMSSA-22021: Diagnostic Engine instance has been unset.

Cause:

Action:
Level: 15

Type: WARNING

Impact: Other

OAMSSA-22022: Collector of type: {0} and path: {1} already exists, reusing existing.

Cause:

Action:
Level: 15

Type: WARNING

Impact: Other

OAMSSA-22023: Rate calculation is disabled.

Cause:

Action:
Level: 15

Type: WARNING

Impact: Other

OAMSSA-22024: Metric persistence is disabled.

Cause:

Action:
Level: 15

Type: WARNING

Impact: Other

OAMSSA-22025: Persisting metrics.

Cause:

Action:
Level: 15

Type: WARNING

Impact: Other

OAMSSA-22026: Rate metrics disabled for Admin Server.

Cause:

Action:
Level: 15

Type: WARNING

Impact: Other

OAMSSA-22027: Collector already exists.

Cause: An attempt was made to register a already registered collector.

Action: Ensure same collector is not registered more than once.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-22028: Number of collectors requested to be registered are incorrect. Maximum "{0}" collectors are allowed.

Cause: More than the required number of collectors are being requested to be registered for a component.

Action: Make sure not more than the max allowed collectors are passed for each component.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-22029: Unsupported sensor type: "{0}".

Cause: Sensor type is not supported.

Action: Use the correct sensor type.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-22030: Config mediator is null.

Cause: Config mediator object is null.

Action: Ensure config mediator object is not null.
Level: 15

Type: WARNING

Impact: Other

64 OBI_OFFICE-00001 to OBI_OFFICE-00077

OBI_OFFICE-00001: Access denied for user

Cause: The user does not have permission to access the analysis

Action: Make sure the user has permisson to access the analysis
Level: 2

Type: Error

Impact: Programmatic

OBI_OFFICE-00002: Access denied to folder

Cause: The user does not have permission to access the folder

Action: Make sure the user has permisson to access the folder
Level: 2

Type: Error

Impact: Programmatic

OBI_OFFICE-00003: The connection name already exists. Please choose a different name.

Cause: A connection with this name already exists

Action: Choose a different name for the connection.
Level: 2

Type: Information

Impact: Programmatic

OBI_OFFICE-00004: Could not insert BI Object

Cause: An error occurred while inserting the view object

Action: Examine the log for details on the error.
Level: 2

Type: Error

Impact: Programmatic

OBI_OFFICE-00005: Could not save as a valid connection, please enter valid connection parameters.

Cause: Unable to save the invalid connection.

Action: Please provide the correct connection paramters and try again.
Level: 2

Type: Error

Impact: Network

OBI_OFFICE-00006: Empty result set. No rows will be displayed.

Cause: The server returned no data.

Action:
Level: 2

Type: Warning

Impact: Programmatic

OBI_OFFICE-00007: Empty result set. A blank chart will be displayed.

Cause: The server returned no data.

Action:
Level: 2

Type: Warning

Impact: Programmatic

OBI_OFFICE-00008: Empty result set. A default chart will be inserted.

Cause: The server returned no data.

Action:
Level: 2

Type: Warning

Impact: Programmatic

OBI_OFFICE-00009: Error while adding image:

Cause: Failed to insert title view image

Action: Examine the log for details on the error.
Level: 2

Type: Error

Impact: Programmatic

OBI_OFFICE-00010: Error during Oracle BI application creation:

Cause: Unable to load Oracle BI Office Addin.

Action: Examine the log for details on the error.
Level: 2

Type: Error

Impact: Programmatic

OBI_OFFICE-00011: Error while inserting Filter view:

Cause: Failed to insert filter view.

Action: Examine the log for details on the error.
Level: 2

Type: Error

Impact: Programmatic

OBI_OFFICE-00012: Error while inserting Title view:

Cause: Failed to insert title view.

Action: Examine the log for details on the error.
Level: 2

Type: Error

Impact: Programmatic

OBI_OFFICE-00013: Error while creating chart:

Cause: Error occurred while inserting chart view.

Action: Examine the log for details on the error.
Level: 2

Type: Error

Impact: Programmatic

OBI_OFFICE-00014: Error while creating chart: Error due to edit mode!

Cause: Error occurred while inserting chart view due to edit mode.

Action: Please unselect the chart and try again.
Level: 2

Type: Error

Impact: Programmatic

OBI_OFFICE-00015: Error while getting clipboard content:

Cause: Unable to access Clipboard contents

Action: Examine the log for details on the error.
Level: 2

Type: Error

Impact: Programmatic

OBI_OFFICE-00016: Error while initializing Oracle BI Add-in:

Cause: Error while initializing Oracle BI Office addin

Action: Examine the log for details on the error.
Level: 2

Type: Error

Impact: Programmatic

OBI_OFFICE-00017: Error while loading Oracle BI Add-in:

Cause: Error while loading the Oracle BI Office addin

Action: Examine the log for details on the error.
Level: 2

Type: Error

Impact: Programmatic

OBI_OFFICE-00018: Error while naming the sheet

Cause: A worksheet with the same name exists

Action: Examine the log for details on the error.
Level: 2

Type: Error

Impact: Programmatic

OBI_OFFICE-00019: Failed to connect to Server, please check the connection and try again.

Cause: Server connection has become unavailable.

Action: Please check the server connection and try again.
Level: 2

Type: Error

Impact: Programmatic

OBI_OFFICE-00020: Failed to get child items.

Cause: Unable to get Analysis/Views at this path.

Action: Please check the path in Answers.
Level: 2

Type: Error

Impact: Programmatic

OBI_OFFICE-00021: Failed to get child items. The folder maybe empty.

Cause: Unable to get Analysis/Views as the folder might be empty.

Action: Please check the folder at this path and make sure it is not empty, and the user has permission to access it.
Level: 2

Type: Error

Impact: Programmatic

OBI_OFFICE-00022: Failed to insert Oracle BI view.

Cause: Failed to insert the view.

Action: Examine the log for details on the error.
Level: 2

Type: Error

Impact: Programmatic

OBI_OFFICE-00023: Failed to insert Oracle BI view. Error due to edit mode!

Cause: Error occurred while inserting the view due to edit mode.

Action: Please unselect the view by pressing Esc key and try again.
Level: 2

Type: Error

Impact: Programmatic

OBI_OFFICE-00024: Filter view not inserted as it is empty.

Cause: Failed to insert filter view.

Action: Examine the log for details on the error.
Level: 2

Type: Error

Impact: Programmatic

OBI_OFFICE-00025: Filter view removed as it is empty.

Cause: The filterview inserted was empty and therefore has been removed.

Action: Please make sure the filter view is not empty.
Level: 2

Type: Error

Impact: Programmatic

OBI_OFFICE-00026: Insufficient space in worksheet.

Cause: The view is too large to fit into one worksheet.

Action: Consider using redesignign the Analysis so that it fits in one worksheet. You may also consider upgrading to Office 2007.
Level: 2

Type: Error

Impact: Programmatic

OBI_OFFICE-00027: Invalid Oracle BI Office server URL or network is not available. Working offline.

Cause: Network connection is not available.

Action: Please make sure the network connection is available and try again.
Level: 2

Type: Error

Impact: Network

OBI_OFFICE-00028: Invalid analysis defintion. Analysis must have at least one dimension and one measure

Cause: The analysis is invalid.

Action: Please make sure that the analysis contains at least one dimension and one measure.
Level: 2

Type: Error

Impact: Programmatic

OBI_OFFICE-00029: You must enter a $1 type for $2

Cause: A wrong type value has been entered for the defined prompt column.

Action: Please enter a numeric value for numeric data type, or a date or datetime for date and datetime types.
Level: 2

Type: Error

Impact: Programmatic

OBI_OFFICE-00030: Invalid URL. Please check your Oracle BI Office server name and port number.

Cause: The BI Office server connection is invalid.

Action: Please edit the connection to make sure that the connection parameters are correct. Test the connection and try again.
Level: 2

Type: Error

Impact: Network

OBI_OFFICE-00031: Login failed. Please check your username, password and Oracle BI Office server availability.

Cause: Either the username/password is incorrect, or the server is not available.

Action: Please make sure the username/password is correct and the server is available. Please check 'Test Connection' in connection details dialog under Preferences.
Level: 2

Type: Error

Impact: Programmatic

OBI_OFFICE-00032: You have no access right to Oracle BI from Microsoft Office.

Cause: You have no access right to Oracle BI from Microsoft Office.

Action: Please contact your administrator.
Level: 2

Type: Error

Impact: Programmatic

OBI_OFFICE-00033: No Oracle BI Office server connections found. Please add at least one server connection.

Cause: No connections have been entered so far.

Action: Please follow the instructions to enter a new BIOffice server connection. You can enter or modify the connection at any time by selecting 'Preferences' from the Oracle BI menu.
Level: 2

Type: Warning

Impact: Programmatic

OBI_OFFICE-00034: No Oracle BI view in clipboard.

Cause: The clipboard is either empty or does not have a BI view copied.

Action: Please go to Answers using your webbrowser and click on 'Copy' link displayed at the bottom on the view.
Level: 2

Type: Warning

Impact: Programmatic

OBI_OFFICE-00035: No prompts and/or levels defined.

Cause: No prompts and/or levels defined for this analysis.

Action:
Level: 2

Type: Warning

Impact: Programmatic

OBI_OFFICE-00036: Only one BI Object can be edited at a time.

Cause: Multiple BI views have been selected.

Action: Please make sure to select only one view, and then click on Edit Prompts and Levels.
Level: 2

Type: Warning

Impact: Programmatic

OBI_OFFICE-00037: Oracle BI view not found.

Cause: The view no lomger exists in Answers

Action: Please make sure that the view exists at that specified path on the server.
Level: 2

Type: Error

Impact: Programmatic

OBI_OFFICE-00038: Please enter a Office server name before test connection.

Cause: A name is not entered in the BI Office server name box.

Action: Please enter a valid name for the BI Office server.
Level: 2

Type: Error

Impact: Programmatic

OBI_OFFICE-00039: Please select a slide before inserting an Oracle BI view.

Cause: A slide has not been selected for the view to be inserted in.

Action: Please select a slide to insert the view into.
Level: 2

Type: Error

Impact: Programmatic

OBI_OFFICE-00040: Please select a slide to refresh.

Cause: A slide has not been selected to refresh.

Action: Please select a slide to refresh.
Level: 2

Type: Error

Impact: Programmatic

OBI_OFFICE-00041: Port numbers 9703 and 9706 are reserved by Oracle BI EE Server. Please verify your port number.

Cause: An invalid port number has been entered in the connection detail dialog.

Action: Please make sure that a valid port number (other than 9703 and 9706) have been enetred in the connection detail dialog.
Level: 2

Type: Error

Impact: Network

OBI_OFFICE-00042: Analysis not found.

Cause: An analysis has not been found at the specified path.

Action: Please make sure that the analysis exists at the specified path.
Level: 2

Type: Error

Impact: Programmatic

OBI_OFFICE-00043: Server configuration file has wrong host name.

Cause: BIOffice.xml file on the BI Office server has incorrect hostname specified in the SAWBASEURL parameter.

Action: Please make sure the URL specified in as the SAWBASEURL in bioffice.xml file is valid and reachable.
Level: 2

Type: Error

Impact: Network

OBI_OFFICE-00044: Server configuration file has wrong port number.

Cause: BIOffice.xml file on the BI Office server has incorrect port number in the SAWBASEURL parameter.

Action: Please make sure the URL specified in as the SAWBASEURL in bioffice.xml file is valid and reachable.
Level: 2

Type: Error

Impact: Network

OBI_OFFICE-00045: Server has wrong SSL configuration (SSL Handshake exception thrown).

Cause: BIOffice.xml file on the BI Office server has incorrect SSL URL in the SAWBASEURL parameter.

Action: Please make sure the URL specified in as the SAWBASEURL in bioffice.xml file is valid and reachable.
Level: 2

Type: Error

Impact: Network

OBI_OFFICE-00046: Server configuration file has wrong URL, or other runtime HTTP exception has been thrown. Please check server configuration and/or server log files for more information.

Cause: Server configuration file has wrong URL, or other runtime HTTP exception has been thrown.

Action: Please check server configuration and/or server log files for more information.
Level: 2

Type: Error

Impact: Network

OBI_OFFICE-00047: Selected view no longer exists on the Oracle BI server.

Cause: Selected view no longer exists on the Oracle BI server.

Action: Please make sure that the view exists at the specified path on the server.
Level: 2

Type: Error

Impact: Programmatic

OBI_OFFICE-00048: Edit Prompts/Levels is not supported for this type of view

Cause: Edit Prompts/Levels action is initiated on Title or Filter view

Action: Please make sure to select a view other than Title and Filter in order to Edit Prompts/Levels.
Level: 2

Type: Warning

Impact: Programmatic

OBI_OFFICE-00049: Selected object is not a valid BI Object

Cause: Object selected is not an Oracle BI View.

Action: Please make sure to select a valid BI view object.
Level: 2

Type: Warning

Impact: Programmatic

OBI_OFFICE-00050: Test connection failed.

Cause: Unable to test connectivity to the Oracle BI Office server.

Action: Please make sure the connection parameters for this connection are set correctly and try again.
Level: 2

Type: Error

Impact: Network

OBI_OFFICE-00051: The folder is empty.

Cause: The folder you are trying to access is empty.

Action: Please make sure to select a non-empty folder.
Level: 2

Type: Information

Impact: Programmatic

OBI_OFFICE-00052: These Oracle BI views are not supported so will not be pasted

Cause: Some of the copied views are not supported by the BI Office addin and therefore will not be pasted.

Action: Try pasting the unsupported views as images or flash(PowerPoint).
Level: 2

Type: Error

Impact: Programmatic

OBI_OFFICE-00053: This chart type is not supported.

Cause: The specified chart type is not supported by BI Office addin.

Action: Try inserting the chart as image or flash(Powerpoint)
Level: 2

Type: Error

Impact: Programmatic

OBI_OFFICE-00054: This Oracle BI view type is not supported.

Cause: The specified view type is not supported.

Action: Please make sure to insert a view that is supported by the addin.
Level: 2

Type: Error

Impact: Programmatic

OBI_OFFICE-00055: Title view not inserted as it is empty :

Cause: The title view is empty and therefore not inserted.

Action: Please make sure the titleview is not empty.
Level: 2

Type: Warning

Impact: Programmatic

OBI_OFFICE-00056: Unknown error occurred.

Cause: An unknown error occurred on BI Office server.

Action: Examine the logs on BI Office server to get more details.
Level: 2

Type: Error

Impact: Programmatic

OBI_OFFICE-00057: You must select an operator

Cause: An operator has not been selected in the prompt dialog.

Action: Please make sure you enter a valid operator in the prompt selection dialog.
Level: 2

Type: Error

Impact: Programmatic

OBI_OFFICE-00058: You must enter a connection name.

Cause: A connection name has not been entered in connection details dialog.

Action: Please make sure you enter a valid connection name in the prompt selection dialog.
Level: 2

Type: Error

Impact: Programmatic

OBI_OFFICE-00059: You must enter a date at row:

Cause: A valid date has not been entered in the prompt selection dialog.

Action: Please make sure you enter a valid date in the prompt selection dialog.
Level: 2

Type: Error

Impact: Programmatic

OBI_OFFICE-00060: You must enter office application name.

Cause: A BIOffice application name has not been entered in connection dialog.

Action: Please enter a valid application name for BI Office server connection. Default : bioffice
Level: 2

Type: Error

Impact: Programmatic

OBI_OFFICE-00061: You must enter a different value

Cause: Same date or datetime value has been entered in case of between operator.

Action: Please enter a different date or datetime for getting data in the specified time range.
Level: 2

Type: Error

Impact: Programmatic

OBI_OFFICE-00062: You must enter a number at row:

Cause: The value entered at the specified row is non-numeric.

Action: Please enter a numeric value at the specified row.
Level: 2

Type: Error

Impact: Programmatic

OBI_OFFICE-00063: You must enter a value for

Cause: Prompt value is not enetred for a prompt column that is defined as mandatory (cannot be skipped).

Action: Please enter or select value for the defined prompt column.
Level: 2

Type: Error

Impact: Programmatic

OBI_OFFICE-00064: You must login again for this change to take effect.

Cause: You have made changes to the connection information while being connected to the same connection.

Action: Please logout and login again.
Level: 2

Type: Error

Impact: Programmatic

OBI_OFFICE-00065: Please select at least one section to insert.

Cause: You have not selected one or more sections of the pivottableview to insert.

Action: Please select at least one section to insert in pivottable view.
Level: 2

Type: Error

Impact: Programmatic

OBI_OFFICE-00066: You must select at least one level

Cause: You have not selected one or more levels to insert in insert view dialog.

Action: Please select at least one level in the level selection tab of insert view dialog.
Level: 2

Type: Error

Impact: Programmatic

OBI_OFFICE-00067: The table being inserted contains more than $1 rows, insertion could be slow.

Cause: The table view or pivot table view being inserted has large number of rows.

Action: Select OK to proceed, or Cancel to stop the insertion.
Level: 2

Type: Information

Impact: Programmatic

OBI_OFFICE-00068: The table being inserted contains more than $1 rows, please wait until insertion is complete or Click Cancel to stop.

Cause: The table view or pivot table view being inserted has large number of rows.

Action: Select OK to proceed, or Cancel to stop the insertion.
Level: 2

Type: Information

Impact: Programmatic

OBI_OFFICE-00069: The table being inserted contains more than $1 columns, insertion could be slow.

Cause: The table view or pivot table view being inserted has large number of columns.

Action: Select OK to proceed, or Cancel to stop the insertion.
Level: 2

Type: Information

Impact: Programmatic

OBI_OFFICE-00070: The table being inserted contains more than $1 columns, please wait until insertion is complete or Click Cancel to stop.

Cause: The table view or pivot table view being inserted has large number of columns.

Action: Select OK to proceed, or Cancel to stop the insertion.
Level: 2

Type: Information

Impact: Programmatic

OBI_OFFICE-00071: This chart type $1 is not supported.

Cause: The chart type you have selected to insert is not supported by Oracle BI Office Addin.

Action: Select a different chart type to insert.
Level: 2

Type: Error

Impact: Programmatic

OBI_OFFICE-00072: Unknown server error has occured. Please check the server logs.

Cause: Unknown server error has occured.

Action: Please check the server logs.
Level: 2

Type: Error

Impact: Programmatic

OBI_OFFICE-00073: Error has occured when creating log file. Please check if the path exists.

Cause: The file can not be created at this path.

Action: Make sure the path the file is created exists.
Level: 2

Type: Error

Impact: Programmatic

OBI_OFFICE-00074: The BIOffice objects copied into office clipboard.

Cause: Copy BIOffice objects into office clipboard.

Action:
Level: 2

Type: Information

Impact: Programmatic

OBI_OFFICE-00075: You must at least select one column.

Cause: At least one column needs to be selected.

Action: Select at least one column.
Level: 2

Type: Warning

Impact: Programmatic

OBI_OFFICE-00076: You have tried to insert one or more views that are not supported by the Oracle BI Add-in. For a complete list of views not supported please refer to the documentation.

Cause: The 11g views are not supported.

Action: Do not include the views are not supported.
Level: 2

Type: Warning

Impact: Programmatic

OBI_OFFICE-00077: The Oracle BI Add-in does not support certain features available in views. These features will not be available in views inserted into Office documents via the Oracle BI Add-in. For a complete list of these unsupported features please refer to the documentation.

Cause: The 11g features are not supported.

Action: Do not create report with features are not supported.
Level: 2

Type: Warning

Impact: Programmatic

65 ODF-10000 to ODF-15222

ODF-10000: Unable to add incident file {0} for incident {1}.

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-10002: Encountered error during diagnostic test run

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-10004: An error occurred during looking up credentials from credential store.

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-10400: An error has occurred: {0} Please consult the Diagnostic engine log file for more details.

Cause: An error has occurred in the Diagnostics commandline utility.

Action: Check the diagnostics log for details on this error.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-10401: Invalid username or password.

Cause: The Diagnostics command line utility requires a userid and password

Action: Please supply a valid username and password or get your Adminstrator to create you new ones.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-10427: Found unexpected parameter "{0}" for command "{1}".

Cause: The specified command does not have the listed paramater.

Action: Run the specified command with no parameters for a list of supported parameters.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-10428: Found multiple values for parameter "{0}" for command "{1}".

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-10436: Unable to read required security configuration file "{0}".

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-10800: Unable to load class: {0}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-10801: Type mismatch for parameter "{0}". Expected type is {1} but found {2}.

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-10802: Unsupported type {0} for parameter "{1}"

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11200: An error occurred when loading diagnostics engine configuration from file {0}: {1}

Cause: Diagnostics engine configuration could not be loaded because the configuration file could not be opened.

Action: Please make sure the configuration file exists and has read permissions.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11201: An error occurred when loading diagnostics engine configuration from deployed resource {0}: {1}

Cause: Diagnostics engine configuration could not be loaded because the default configuration file inside DiagEngine.jar could not be opened.

Action: Please make sure the configuration properties file exists inside the DiagEngine.jar
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11202: Unable to locate configuration properties resource at {0}.

Cause: Diagnostics engine configuration could not be loaded because the default configuration file inside DiagEngine.jar could not be opened.

Action: Please make sure the configuration properties file exists inside the DiagEngine.jar
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11203: Values are not set for the following configuration properties: {0}

Cause: One or more required configuration properties for the Diagnostics Engine do not have values in the configuration file.

Action: Specify values for the required configuration properties in the configuration file.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11204: Unknown NLS Bundle: {0}

Cause: NLS Bundle specified by a Diagnostic Test cannot be loaded. This can normally happen if the NLS Bundle is a resource bundle that does not exist or cannot be loaded.

Action: Ensure that the NLS Bundle specified within the Diagnostic Test is a valid resource bundle class.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11205: Unable to create an external URL. linkURI is not specified.

Cause: A link to an external website could not be created in the diagnostic test report because the 'linkURI' attribute was not specified by the diagnostic test when adding the link to the report.

Action: Correct the diagnostic test to specify the 'linkURI' attribute required when adding external links to the test report.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11206: Unable to create an URL for Metalink note. Metalink document ID is not specified.

Cause: A link to a Metalink Document could not be created in the diagnostic test report because the document ID was not specified by the diagnostic test when adding the link to the report.

Action: Correct the diagnostic test to specify the document ID when adding links to Metalink documents to the test report.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11207: Unable to create an internal URL. functionName is not specified.

Cause: A link to an internal application page within the applications system could not be created in the diagnostic test report because the name for the page was not specified by the diagnostic test when adding the link to the report.

Action: Correct the diagnostic test to specify the page name / function name when adding internal links to the test report.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11208: Unable to load the FND Message Service due to an error: {0}

Cause: The Diagnostics Engine was unable to connect to the Message Service. This could happen if Message Service cannot connect to the applications database.

Action: Ensure that the applicatoins database datasource is configured correctly and that the database is running.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11209: Unable to get JPS context. Following exception is thrown : {0}

Cause: An error occurred when attempting to get the JpsContext from JpsContextFactory. This could happen if JPS is not configured properly in the server where diagnostics is running.

Action: Ensure that the JPS is properly configured on the server where diagnostics is running. Also check the managed server log files to determine the underlying root cause for the error.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11210: No privilige to get credentials with key : {0}

Cause: Diagnostics Engine does not have appropriate privilege to read from the credential store.

Action: Ensure that the DiagEngine.jar file is granted appropriate privilege to read from the credential store.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11211: Credential being set in credentials store is invalid. Please refer error message : {0}

Cause: Could not save credential to credential store because the credential was invalid.

Action: Ensure that valid credentials are specified when saving to the credential store.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11212: Unable to retrieve problems for ADR Home {0} on server {1}. Please refer error message : {2}

Cause: This can occur if the diagnostics engine is unable to establish connection with the underlying IncidentManagerProxy MXBean in the domain to retrieve problems.

Action: Ensure that the AdminServer for the domain is up and running. Also check the associated error message and the server log file for further information.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11213: Unable to retrieve incidents for a problem from ADR system. Please refer error message : {0}

Cause: This can occur if the diagnostics engine is unable to establish connection with the underlying IncidentManagerProxy MXBean in the domain to retrieve incidents.

Action: Ensure that the AdminServer for the domain is up and running. Also check the associated error message and the server log file for further information.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11214: Unable to register a diagnostics test run with incident in ADR system. Please refer error message : {0}

Cause: This can occur if the diagnostics engine is unable to establish connection with the underlying IncidentManagerProxy MXBean in the domain while adding a diagnostic test run to an incident in the ADR system.

Action: Ensure that the AdminServer for the domain is up and running. Also check the associated error message and the server log file for further information.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11215: Unable to close JMX connector. Please refer error message : {0}

Cause: Diagnostic Engine was able to perform the mbean operation but encountered an error when attempting to close the JMX connection.

Action: Check the associated error message and the server log file for further information.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11216: Unable to obtain connection provider.

Cause: Diagnostic Engine was unable to connect to the AdminServer.

Action: Ensure that the AdminServer is up and running. Also check the server log file for further information.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11217: Invalid Problem object passed for querying incidents.

Cause: Invalid or null Problem argument was passed when querying for incidents.

Action: Ensure that a valid Problem argument is passed when querying for incidents.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11218: Invalid incident or diagnostics test report provided.

Cause: One or more of the following parameters were not specified when attempting to add diagnostic test report to an incident in ADR: incident ID, test report file path, server name, ADR Home

Action: Ensure that valid parameters are specified when adding diagnostic test report to an incident in ADR.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11219: You do not have sufficient privileges to execute the test with name ''{0}''.

Cause: User did not have sufficient privileges to execute the diagnostic test.

Action: Ensure that the user belongs to an appropriate role with the execute test privilege required for executing diagnostic tests.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11220: You do not have sufficient privileges to view report details for this execution.

Cause: User does not have sufficient privileges to view a diagnostic test report.

Action: Ensure that the user belongs to an appropriate role with the view test report privilege required for viewing test reports.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11221: You do not have sufficient privileges to update the test with name ''{0}''.

Cause: User does not have sufficient privileges to update the definition of a diagnostic test.

Action: Ensure that the user belongs to an appropriate role with the update test privilege required for updating test definition.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11222: You do not have sufficient privileges to update the tag with name ''{0}''.

Cause: User does not have sufficient privileges to update the diagnostic tag.

Action: Ensure that the user belongs to an appropriate role with the update tag privilege required for updating diagnositc tags.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11223: You do not have sufficient privileges to delete the tag with name ''{0}''.

Cause: User does not have sufficient privileges to delete a tag.

Action: Ensure that the user belongs to an appropriate role with the delete tag privilege required for deleting diagnostic tags.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11224: Could not obtain the security subject of the currently logged in user.

Cause: Diagnostics Engine was unable to get the security subject for the current user.

Action: Ensure that JPS is configured properly.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11225: Could not obtain the user name of the currently logged in user, could not find the user principal matching class "{0}".

Cause: Diagnostics Engine was unable to determine username for the current user.

Action: Ensure that JPS is configured properly.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11226: Could not obtain the user name and or GUID of the currently logged in user.

Cause: Diagnostics Engine was unable to get the user name or the GUID of the current user.

Action: Ensure that JPS is configured properly. Check the underlying error trace in the server log file.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11227: Unable to obtain the module_id for the Diagnostics Logical Business Area (LBA).

Cause: An error occurred when querying the module_id for the Diagnostics LBA from the database.

Action: Ensure that the Diagnostics LBA seed data exists in the database and that the database is running. Also check for the underlying error trace in the server log file.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11228: Unable to obtain the menu_id for the FND menu with name ''{0}''.

Cause: An error occurred when querying the menu_id for a FND menu from the database.

Action: Ensure that the Diagnostics data security seed data exists in the database and that the database is running. Also check for the underlying error trace in the server log file.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11229: Unable to obtain the object_id for the FND object with name ''{0}''.

Cause: An error occurred when querying the object_id for an FND Object from the database.

Action: Ensure that the Diagnostics data security seed data exists in the database and that the database is running. Also check for the underlying error trace in the server log file.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11230: The execution of the PL/SQL procedure name validation method failed to return any values.

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11231: The execution of the PL/SQL procedure name validation method has failed.

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11233: Unable to create connection because one or more of the following properties are not specified: {0}

Cause: One or more properties required for creating a database connection were not specified.

Action: Specify the missing properties required for creating the database connection.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11234: Unable to load connection properties

Cause: No properties were loaded from the properties file specified using the APPCONNFILE system property.

Action: Ensure that the properties file specified using the APPCONNFILE system property exists and contains the required properties.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11235: System property "{0}" not specified.

Cause: A particular system property required for the Diagnostics Engine was not specified.

Action: Ensure that the system property referenced in the error message is specified using JVM arguments for the managed server or the command-line interface.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11236: Unable to read APPCONNFILE: {0}

Cause: Diagnostics engine was unable to read the file specified by the APPCONNFILE system property.

Action: Ensure that the properties file specified using the APPCONNFILE system property exists and has read permissions.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11237: Unable to load properties from APPCONNFILE: {0}

Cause: Configuration properties could not be loaded from the properties file specified using the APPCONNFILE system property.

Action: Ensure that the properties file specified using the APPCONNFILE system property exists, is readable, and contains the required properties.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11238: The session was not attached due to an error during FND Session initialize: {0}

Cause: An error occurred during initialization of the FND Session the database connection.

Action: Refer to the associated error message and the server log files for more information.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11239: The session was not detached due to an error during FND Session detach: {0}

Cause: An error occurred during detaching of the FND Session from the datbaase connection.

Action: Refer to the associated error message and the server log files for more information.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11240: Unable to lookup or obtain a connection from data source: {0}

Cause: This error generally occurs if the database does not exist or is not configured properly.

Action: Ensure that the datasource exists in the domain and is configured correctly.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11241: An error occurred while streaming contents from file {0} to incident {1} on server {2}: {3}

Cause: An error occurred while copying the contents of a file to an incident directory on a managed server.

Action: Refer to the associated error message and the server log files for more information.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11242: An error occurred while fetching value for profile option {0}: {1}

Cause: An error occurred while querying value of a profile option from the database.

Action: Refer to the associated error message and the server log files for more information.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11243: The profile option "{0}" is not set. Unable to compute report URL.

Cause: The Diagnostics Dashboard URL Profile Option is not set.

Action: Set the Diagnostics Dashboard URL Profile Option to point to your Diagnositcs Dashboard Application URL.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11244: The value "{0}" for profile option "{1}" is invalid. Unable to compute report URL.

Cause: The Diagnostics Dashboard URL Profile Option is set to an invalid value.

Action: Set the Diagnostics Dashboard URL Profile Option to point to your Diagnositcs Dashboard Application URL.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11245: Unable to evaluate value for expression: {0}

Cause: This generally occurs if the expression is invalid or if the system property specified in the expression is not set.

Action: Ensure that the expression is valid and the system property specified in the expresion is set.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11246: Null connection returned from ApplSessionUtil.

Cause: ApplicationDB data source returned a null connection.

Action: Ensure that the ApplicationDB data source is configured properly.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11247: Unable to access field : {0} in class: {1} with bundle name: {2}

Cause: Unable to access the field with the given name from the given resource bundle class.

Action: Ensure that the field exists in the given resource bundle class.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11251: Could not obtain the application roles for the currently logged in user.

Cause: Diagnostics Engine was unable to determine the aplication roles for the current user.

Action: Ensure that JPS is configured properly.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11252: An error occurred while attempting to retrieve the list of ADR Homes: {0}

Cause: This can occur if the diagnostics engine is unable to establish connection with the underlying IncidentManagerProxy MXBean in the domain to retrieve the list of ADR Homes.

Action: Ensure that the AdminServer for the domain is up and running. Also check the associated error message and the server log file for further information.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11253: You do not have sufficient privileges to execute this JMX API. Please ensure that the user ''{0}'' is a member of one of the Fusion Applications Diagnostics Application ID enterprise roles.

Cause: This can occur if the user attempting to invoke the JMX API is not a member of one of the required Diagnostics Application ID enterprise roles.

Action: Ensure that the user is a member of one or more of the Diagnostics Application ID enterprise roles.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11254: You do not have sufficient privileges to delete the test with name ''{0}''.

Cause: User does not have sufficient privileges to delete the definition of a diagnostic test.

Action: Ensure that the user belongs to an appropriate role with the delete test privilege required for deleting test definition.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11600: An error occurred when setting save point {0}: {1}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11601: An error occurred when saving definition for test {0}: {1}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11602: An error occurred when saving inputset {0} : {1}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11603: Invalid prerequisite entity for test '{0}'. A prerequisite for a test must have a test ID or a tag value ID.

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11604: An error occured while extracting or loading test definition for test id: {0}: {1}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11605: An error occured while extracting or loading test definition for test name {0} : {1}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11606: An error occured while fetching test id for test name: {0} : {1}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11607: An error occured while fetching test name for test id: {0} : {1}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11608: An error occured while fetching tag value data for tag value id: {0} : {1}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11609: An error occured while fetching tag value data for tag name, tag value: {0} : {1}.

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11610: An error occured while fetching tag data for tag id: {0} : {1}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11611: An error occured while fetching tag data for tag name: {0} : {1}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11612: An error occurred when saving definition for test stats {0}: {1}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11613: An error occurred while fetching test stats for test id: {0}: {1}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11614: An error occurred while getting test stats for testname: {0}: {1}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11615: A cycle has been detected between Source Id: Prereq Id - {0} : {1}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11616: An error occurred while executing SQL query: {0} with parameters: {1} {2}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11617: An error occurred when saving definition for tag {0}: {1}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11618: An error occurred when saving definition for tag {0} and value {1}: {2}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11619: An error occurred when associating tag {0} and value {1} with tests {2}: {3}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11620: An error occurred when removing tag {0} and value {1} from tests {2} : {3}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11621: An error occurred when removing tag value {0} : {1} : {2}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11622: An error occurred when removing tag {0} : {1}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11623: An error occurred when updating the params to inactive for test id: {0}.

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11624: An error occurred when updating the prereqs to inactive for test id: {0}.

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11625: An error occurred when updating the test tag value associations to inactive for test id: {0}.

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11626: Attempted rollback to savepoint: {0} failed.

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11627: An error occurred when freeing temporary clob: {0}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-11628: An error occurred when deleting test definition {0} : {1}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12000: Error when saving a test execution for run id {0} with execution id {1}: {2}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12001: Error when saving a test run for run id {0} : {1}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12002: Error when querying test execution id {0}: {1}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12003: Error when loading a test run id {0}: {1}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12004: Error when loading a test executions for run id {0}: {1}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12005: Error when loading nested child test executions for execution id {0}: {1}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12006: Error when fetching run id for run name {0}: {1}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12007: Cannot find run ID {0} to lock for update.

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12008: Cannot find execution ID {0} to lock for update.

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12009: Found unexpected status code {0} for run ID {1}. Expected status code was {2}. Aborted status update.

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12010: An error occurred when updating status for run ID {0} to {1}: {2}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12011: An error occurred when deleting run with run ID {0} : {1}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12408: Thread {0}: An error occurred while executing test: {1}: {2}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12409: Thread {0}: An error has occurred during execution of run command: {1}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12437: An error occurred fetching user/role information: {0}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12800: Unable to load XML: {0}

Cause: XML file not found or has invalid XML syntax.

Action: Locate the existance of XML file {0}. Correct the XML syntax errors.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12801: Encountered validation event while processing {0} at line {1}, column {2}: {3}

Cause: Encountered error at indicated Line in Syntax or missing objects

Action: Correct any syntax errors. Ensure objects indicated exist and are valid.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12802: Cannot load test metadata. Null or empty Java class name.

Cause: Java classname not provided

Action: Provide a classname that can be found in the system.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12803: Cannot load test metadata. Null or empty file path.

Cause: file path not found to load metadata

Action: Provide a file path that exists in the system for this metadata
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12804: Test file not found: {0}

Cause: Test file not found in current file system or jar

Action: Ensure test files exists in current file system or jar. Ensure test properties points to the correct jar for this system
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12805: Test file must be a xml file. Unsupported test file type: {0}

Cause: XML is the only supported file type for Tests in this release

Action: Provide an XML file type for this test.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12806: Found duplicate input parameter "{0}" in test "{1}".

Cause: Test metadata and/or input parameter has a duplicate definition

Action: Correct test definition. Provide different input parameters that does not have a duplicate input parameter
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12807: Found duplicate output parameter "{0}" in test "{1}".

Cause: Test metadata and/or output parameter has a duplicate definition

Action: Correct test definition. Provide a different output parameter that does not have a dpulicate output parameter
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12808: Found duplicate step "{0}" in test "{1}".

Cause: Test metatdata has a duplicate step definition

Action: Correct tests metadata so it doesn't has a duplicate step definition. Remove one of the steps.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12809: Found duplicate step definition "{0}" in test "{1}".

Cause: Test metatdata has a duplicate step name in the definition

Action: Correct tests metadata so it doesn't has a duplicate step definition name. Remove one of the steps.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12810: Corresponding step definitions not found for the following steps in test "{0}": {1}

Cause: Test step does not have a definition

Action: Add a step definition in this Test
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12811: Input parameter "{0}" in test "{1}" is required but does not have a default value.

Cause: Required Input parameter in this test has not been provided with a default value

Action: Provide a default Input value for this parameter in this test or remove required settings
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12812: Default value "{0}" for parameter "{1}" in test "{2}" cannot be converted to specified type "{3}".

Cause: The data type associated with the Default value for this parameter is not valid for type defined for the parameter

Action: Changed the Default value or change the Type on the Parameter definition
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12813: Value "{0}" for parameter "{1}" in test "{2}" cannot be converted to specified type "{3}".

Cause: The data type associated with the value for this parameter is not valid for type defined for the parameter

Action: Changed the value or change the Type on the Parameter definition
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12814: Value "{0}" for parameter "{1}" in test "{2}" is of type "{3}" and cannot be converted to expected type "{4}".

Cause: The data type associated with the value for this parameter is not valid for type defined for the parameter

Action: Changed the value or change the Type on the Parameter definition
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12815: Test "{0}" specifies default value for java.util.Date parameter "{1}" however the dateFormat attribute is not specified. Please specify a Java date format as value for the dateFormat attribute.

Cause: This parameter requires a date format and a non-date format was specified

Action: Provide an accepted date format. Check locale for date format.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12816: Default value "{0}" for parameter "{1}" in test "{2}" cannot be converted to specified type "{3}" using format "{4}".

Cause: This Default value requires a date format and a non-date format was specified

Action: Provide an accepted date format. Check locale for date format.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12817: Value "{0}" for parameter "{1}" in test "{2}" cannot be converted to specified type "{3}" using format "{4}".

Cause: This date value requires a date format and a non-date format was specified

Action: Provide an accepted date format. Check locale for date format.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12818: The following prerequisite tests for test "{0}" could not be located in the test repository: {1}

Cause: The test definition requires a prerequisite test(s) to be run which could not be found

Action: Ensure the test is located in the test repository or remove the prerequisite requirement from the test definition
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12819: The following tag name values for test "{0}" could not be located in the test repository: {1}

Cause: The test specified has tag name value defined for it that don't exist in the test repository

Action: Ensure the tag name value definitions exist in the repository by creating new ones or remove the tag name value from the specified test
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12820: The following referenced tests in steps for test "{0}" could not be located in the test repository: {1}

Cause: The specified test has steps that reference tests not found in the test repository

Action: Ensure the tests referred to in the steps are located in the test repository or remove the tests from the steps or remove the steps.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12821: The following prerequisite tag value IDs for test "{0}" could not be located in the test repository: {1}

Cause: The test definition requires prerequisite tag value IDs which could not be found

Action: Ensure the tag value IDs are located in the test repository or remove the prerequisite requirement from the test definition
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12822: The following tag value IDs for test "{0}" could not be located in the test repository: {1}

Cause: The test definition requires tag value IDs which could not be found

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12823: Invalid token "{0}" in binding for parameter "{1}" in step "{2}" in test "{3}". Must specify a parameter name.

Cause: Missing a parameter name for the listed step in this test.

Action: Provide the correct parameter name for this test step.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12824: Invalid parameter reference in token "{0}" in binding for parameter "{1}" in step "{2}" in test "{3}". Referenced parameter is not defined.

Cause: Parameter reference listed in not valid.

Action: Check the test step listed for the correct parameter definition.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12825: At least one of the following parameters must be specified for test registration: {0}

Cause: This test requires parameters for it to be registered.

Action: Check the test definition for the parameters that should be specified.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12826: The specified directory does not exist: {0}

Cause: The filesystem doesn't have the specified directory

Action: Specify a valid directory from the current filesystem
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12827: The specified directory is not a directory: {0}

Cause: The filesystem doesn't have the specified directory

Action: Specify a valid directory from the current filesystem. Don't specify a filename in this case
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12828: The specified file does not exist: {0}

Cause: The filesystem doesn't have the specified filename

Action: Specify a valid filename from the current filesystem.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12829: The test ID or test name must be set in order to fetch test definition.

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12830: The run ID or run name must be set in order to fetch test run information.

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12831: The run ID or run name must be set in order to cancel a test run.

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12832: The run ID or run name must be set in order to delete a test run.

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12833: The execution ID must be set in order to fetch test execution information.

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12834: The following cyclic test reference encountered : {0}

Cause: A cyclic test reference means the test is not runnable.

Action: A cyclic test reference can be caused by prerequsites or steps referring to tests in a non-sequential manner
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12835: An error occurred while validating nested test {0}: {1} with nested heirarchy {2}

Cause: This test has references to other tests in steps or prerequisites

Action: Remove the invalid nested test in this test definition
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12836: Current execution ID is not set.

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12837: Current step name is not set.

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12838: Value not set for required parameter: {0}.

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12839: Invalid value for parameter {0} : {1}. Value must be Y or N.

Cause: This is a boolean parameter value

Action: Change eht parameter value to Y or N
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12840: The following cyclic reference encountered for tag value id {0} : {1}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12841: Run name {0} already exists. Please specify a different run name.

Cause: Only unique run names can be used

Action: Change the run name or add a prefix or postfix that makes it unique
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12842: Invalid value for parameter {0} : {1}. Value must be an integer.

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12843: Invalid value for parameter {0} : {1}. Value must be a positive integer.

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12844: Invalid value for parameter {0} : {1}. Value must be less than {2}.

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12845: Value not set for parameter: {0}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12846: Invalid tag name value parameter: {0}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12847: Invalid input name value parameter: {0}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12848: Invalid test name : {0}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12849: Invalid module ID: {0}

Cause: The module ID is not a known value

Action: Use a module ID found from the Taxonomy tables
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12850: Invalid App product code: {0}

Cause: This App product code is not a known value

Action: Use an App code found from the Taxonomy tables.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12851: Invalid module key: {0}

Cause: The Module key is not a known value.

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12852: Invalid tag name value {0} : {1}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12853: The input parameters for test execution do not resolve to any registered test. Ensure at least one of the following parameters (in CLI or API) must be specified and not empty: {0}

Cause: This Test requires input parameters and none were found.

Action: Supply input parameters as defined by the Test definition and rerun the test.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12854: At least one of the following parameters must be specified: {0}

Cause: This test requires parameters that were not supplied with the tests

Action: Supply input parameters as defined by the Test definition and rerun the test.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12856: An unexpected error occured during test execution.

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12857: Exactly one of the following parameters must be specified: {0}. Values for more than one parameters were specified: {1}.

Cause: The test was run with the incorrect number of parameters

Action: Rerun this test with exactly one parameters as specified by the test definition
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12858: Invalid value "{0}" for parameter "{1}". Value must be one of the following: {2}

Cause: The test was run with invalid parameter values.

Action: Rerun this test with parameters values specified in the message
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12859: Test run with ID "{0}" not found in the repository.

Cause: Test run ID not found or has been deleted.

Action: Use a test run ID found in the repository
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12860: Test run with name "{0}" not found in the repository.

Cause: Test run name does not exist in the repository or was deleted.

Action: No further action required
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12861: Test execution with ID "{0}" not found in the repository.

Cause: Test execution ID does not exist in the repository or was deleted.

Action: No further action required
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12862: Unable to create destination directory "{0}". Please ensure that appropriate permissions are set to create this directory or specify a different destination directory using the "destdir" parameter.

Cause: A destination directory exists in a filesystem where write or create permission is not available for the current owner

Action: Change the write and create privileges for the parent directory.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12863: Unable to create a file under directory "{0}". Please ensure that appropriate permissions are set to create this directory or specify a different destination directory using the "destdir" parameter.

Cause: A file in a destination directory in the filesystem where write or create permission is not available for the current owner

Action: Change the write and create privileges for the parent directory.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12864: "{0}" already exists and is not a directory. Please specify a different destination directory using the "destdir" parameter.

Cause: The name specified already exists as a directory.

Action: Use a different name for this directory or remove the existing directory
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12865: "{0}" already exists. Attempt to rename it failed.

Cause: The name specified already exists as a directory.

Action: Use a different name for this directory or remove the existing directory
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12866: Failed to create directory "{0}".

Cause: Directory already exists or parent directory has no write and create permissions

Action: Remove the existing directory, change the permission on the parent directory or use a different directory name
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12867: Unable to perform translation. NLS Bundle is not specified.

Cause: Specify the correct NLS bundle name

Action: Specify the correct NLS bundle name
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12868: No value specified for parameter "{0}"

Cause: This Parameter requires a value which was not specified

Action: Provide a value for the specified parameter
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12869: Report not found for run ID "{0}"

Cause: Report was not generated because the Run had an error or the test didn't complete

Action: Check the report status and correct any errors. Rerun the test.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12870: Report not found for run name "{0}"

Cause: Report was not generated because the Run had an error or the test didn't complete

Action: Check the report status and correct any errors. Rerun the test.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12871: Report not found for execution ID "{0}"

Cause: Report was not generated because the Run had an error or the test didn't complete

Action: Check the report status and correct any errors. Rerun the test.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12872: An input set with name "{0}" already exists for test "{1}"

Cause: The input set name already exists in the repository.

Action: Specify a different name for the input set
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12873: Required parameter "{0}" does not have a value to run with.

Cause: Required must have values and the value is missing.

Action: Provide a value for the required parameter specified and rerun the test.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12874: Value "{0}" not in list of valid values for parameter "{1}".

Cause: This parameter is validated with an LOV that does not have the value specified.

Action: Provide a different value for the parameter specified.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12875: Validation error occurred for input value "{0}" for parameter "{1}": {2}

Cause: This parameter fails validation rules for the input value.

Action: Provide a different value for the parameter specified.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12885: Filter operator "{0}" is not supported for parameter "{1}"

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12886: Taxonomy module ID "{0}" not found.

Cause: A taxomony module ID was provided that does not exist in the taxonomy definitions

Action: Provide a different taxonomy module ID
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12887: Null or empty tag name.

Cause: A tag name is required in this context

Action: Provide a tag name.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12888: Null or empty module ID

Cause: A module ID is required in this context

Action: Require a module ID. Module IDs are found in Taxonomy tables
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12889: Tag with name "{0}" already exists.

Cause: Duplicate tag names are not supported

Action: Provide a different tag name
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12890: Null or empty tag value.

Cause: Tag values are required in this context

Action: Provide a tag value
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12891: Tag with name "{0}" does not exist.

Cause: A tag name was provided that was not created or was deleted

Action: Create the tag name first or use a different tag name
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12892: Tag with name "{0}" and value "{1}" already exists.

Cause: A tag name was provided that was not created or was deleted

Action: Create the tag name first or use a different tag name
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12893: At least one criteria must be specified.

Cause: Criteria are required in this context

Action: Supply criteria
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12894: Unable to delete Test Run(s). Cannot delete a test run {0} that is currently in progress.

Cause: A test is still running and can't be deleted

Action: Cancel the test run or wait for the test to complete before deleting it
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12895: Found one or more Runs with null Run ID.

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12896: Tag {0} with Value {1} does not exist.

Cause: Tag value was deleted or never created for this tag name

Action: Create the tag value for this tag name or use a tag value that already exists
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12897: Cannot remove tag {0} created by Oracle.

Cause: Oracle tags are seeded tags that can't be deleted

Action: No futher action required
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12898: Cannot remove tag name value {0}:{1} created by Oracle.

Cause: Oracle tag values are seeded tag values that can't be deleted

Action: No futher action required
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12899: Unable to register Executor Mbean for Web Application {0}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12900: Unable to unregister Executor Mbean for Web Application {0}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12901: Could not invoke test. Reasons could be because (a) The associated application {0} is not running (b) Credential Store and Permissions have not been set up correctly (c) The test is being invoked from outside the J2EE context.

Cause: See message for cause

Action: Setup and install credentials and permissons.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12902: Since "WEB_APP_NAME" tag is present, test must have attribute "requiresApplicationCode" set to "Y".

Cause: This test requires a specific application to run

Action: Set the requiresApplicationCode flag to Y or remove the WEB_APP_NAME tag
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12903: Since "requiresApplicationCode" is set to "Y", test must have a tag for "WEB_APP_NAME".

Cause: This test requires a specific application to run

Action: Remove the requiresApplicationCode flag or supply the WEB_APP_NAME tag with the application name
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12904: Could not connect to the Domain Runtime MBean Server. Reasons could be because (a) Credential Store and Permissions have not been set up correctly (b) The test is being invoked from outside the J2EE context.

Cause: See message for cause

Action: Setup and install credentials and permissons.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12905: Could not execute diagnostic test that requires application code.

Cause: This test requires code that exists in a specific application to run

Action: Ensure the specified application is also running when you run this test
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12906: Cannot invoke diagnostic test {0} from CLI since it requires application code. The Diagnostics UI can be used to run this type of test.

Cause: This test requires code that exists in a specific application to run

Action: Run this test from the Diagnostic Testing Dashboard. Ensure the specified application is also running when you run this test
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12907: Cannot start the web application because neither display-name nor "fusion.odf.metadata.webappname" context-param was found in web.xml. The context-param(recommended) or display-name is necessary when Diagnostics Tests requiring applications code are present.

Cause: This test requires code that exists in a specific application to run

Action: Action is specified in the message
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12908: Could not find the required attribute "{0}" in the user context object provided to the mbean invocation.

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12909: Could not find the user name of the currently logged in user.

Cause: User name not found

Action: Supply a different user name, or ensure the current user name is setup correctly for Diagnistics credentials
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12910: Could not establish a valid subject for user name "{0}". Please check to make sure all necessary code source permissions have been granted for the oracle.appltest.diagfwk.executor shared library.

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12911: Could not establish a valid subject for user name "{0}". Please check to make sure all necessary code source permissions have been granted for the Diagnostics-JmxApi application.

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12912: All nested tests that depend on a Web Application must use the same Web Application.

Cause: The Web Application is defined using the WEB_APP_NAME tag and is not pointing to the same app

Action: Add the app for these nested tests to the WEB_APP_NAME tag
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12913: A compound test that contains nested tests which depend on a Web Application must also be tagged to depend on the same Web Application.

Cause: The Web Application is defined using the WEB_APP_NAME tag and is not pointing to the same app

Action: Add the app for these nested tests to the WEB_APP_NAME tag
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12914: Only one value for the "WEB_APP_NAME" tag can be associated with a test.

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12915: The number of tag names does not match the number of tag values.

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12916: Unable to register MBean which provides access to diagnostics test execution

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12917: Unable to unregister MBean which provides access to diagnostics test execution

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12918: Error occured while initializing the context information for the PL/SQL Step: {0}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12919: Error occured during execution of the Init test procedure of the PL/SQL Step: {0}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12920: Error occured during execution of the RunTest test procedure of the PL/SQL Step: {0}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12921: Error occured during execution of the Cleanup test procedure of the PL/SQL Step: {0}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12922: Error occured while carrying out post-execution steps of the PL/SQL Step: {0}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12923: The PL/SQL procedure ''{0}'' is either not defined or is defined with one or more formal parameters when it should have none.

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12932: An error occurred while adding information about execution error to the report: {0}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12933: Failed to create a Diagnostic Test for class: {0}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12934: Found parameter ''{0}'' without parameter definition metadata.

Cause: Inconsistent Test metadata from the parameter definition

Action: Edit the test definition and add a parameter definition for the specified parameter or remove the parameter in the test definition
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12935: Threadpool still may have running threads. Attempting force shutdown.

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12936: Failed to delete touched file: {0}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12937: Invalid monitoring interval: {0} Will run with default: {1}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12938: An error occurred while saving status: {0}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12939: Monitoring interrupted for: {0}

Cause: This is an informative message

Action: No actions required
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12940: Diagnostics Engine skipping authentication because subject is empty and username or password null. Engine will execute as the anonymous user which makes having permission to run a test or view a report VERY UNLIKELY.

Cause: No userid provided for this session

Action: Login using a valid diagnostics userid and password
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-12962: Insufficient privileges to perform action {0}.

Cause: The login user does not have the security rights for this action

Action: Login using a userid with the appropriates rights or add those rights for this user
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-13200: Unable to load the annotated class file: ''{0}''

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-13201: Missing value. The annotation ''{0}'' must have a value.

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-13202: Unable to find the required annotation ''{0}''.

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-13203: Unable to find the Module ID for the Module Key ''{0}''

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-13600: Encountered an unrecognized PL/SQL report instruction: ''{0}''

Cause: The report could not be processed because of an invalid instruction

Action: Check the PL/SQL in the report for validity. Try the PL/SQL in a compiler first.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-13601: Some PL/SQL instruction set values are missing

Cause: This PL/SQL instruction set requires values.

Action: Check the documentation for this instruction set and it's required values.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-13602: Execution of the SQL query failed. SQL query was: ''{0}''

Cause: Invalid SQL causes this problem.

Action: Check the SQL syntax and make corrections before rerunning this test.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-13603: The report section was not found. The ''{0}'' procedure can only be called after a section is created via the FND_DIAG_SDK_API.START_REPORT_SECTION procedure.

Cause: The listed procedure doesn't have a start report section.

Action: Correct the PL/SQL report by adding a start report section before the listed procedure.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-14000: Unable to configure transformation for xsl: ''{0}''

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-14001: Unable to transform xml: ''{0}''

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-14002: Error printing html output

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-14003: XSL resource not found: {0}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-14400: Error in method {0} : {1}

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-14800: Failed to retrieve OS name. The following OS string returned from System.getProperty("os.name") is unknown: {0}

Cause: OS name is incorrect in properties or profile for this system.

Action: Correct the OS name in the property file or profile for this system.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-14801: Could not create URL for {0}.

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-14802: Could not retrieve domain name for current system.

Cause: Domain name is incorrect.

Action: Ensure the Domain was created correctly and is in properties correctly
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-14803: File does not exists {0}. Unable to retrieve owner/group owner for node.

Cause: Owner/Group is not valid for the server node

Action: Ensure the Owner/Group has been created for this installation
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-14804: Unable to stat file {0} for ownership details

Cause: There is a problem with the specified file

Action: Ensure the specified file exists and has the proper access rights.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-14805: Unable to stat file {0} for group ownership details

Cause: There is a problem with the specified file for this group owner

Action: Ensure the specified file exists and has the proper access rights for this group owner.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-15200: Unable to obtain connection to the EM Repository.

Cause: Unable to obtain connection to the EM Repository.

Action: Check the connection information or try again.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-15201: Unable to find required property ''{0}''.

Cause: The property could not be found.

Action: Make sure all required properties have been set.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-15202: Property ''{0}'' has an invalid type - expected ''{1}'', found ''{2}''.

Cause: The property's type is invalid.

Action: Check the property's type to make sure it conforms to expectations.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-15203: Property ''{0}'' cannot be converted to an integer.

Cause: The property could not be converted.

Action: Make sure the value of the property is an integer.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-15204: Unable to find required parameter ''{0}''.

Cause: The parameter could not be found.

Action: Make sure all required parameters have been provided.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-15205: Parameter ''{0}'' has an invalid type - expected ''{1}'', found ''{2}''.

Cause: The parameter's type is invalid.

Action: Check the parameter's type to make sure it conforms to expectations.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-15206: Parameter ''{0}'' cannot be converted to an integer.

Cause: The parameter could not be converted.

Action: Make sure the value of the parameter is an integer.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-15207: Property ''{0}'' cannot be converted to a long.

Cause: The property could not be converted.

Action: Make sure the value of the property is a long (integer).
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-15208: Parameter ''{0}'' cannot be converted to a long.

Cause: The parameter could not be converted.

Action: Make sure the value of the parameter is a long (integer).
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-15209: Required credentials missing for target name ''{0}'', type ''{1}''.

Cause: The required credentials for the operation could not be found.

Action: Make sure the required credentials have been provided.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-15210: Unexpected credential column ''{0}'' for target name ''{1}'', type ''{2}''.

Cause: An unexpected credential column was found.

Action: Make sure the credentials provided conform to the expected format.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-15211: Required credential column ''{0}'' missing for target name ''{1}'', type ''{2}''.

Cause: The required credential column could not be found.

Action: Make sure the required credentials have been provided.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-15212: Unable to obtain connection to the Apps Database for corresponding EM target name ''{0}'', type ''{1}''.

Cause: Unable to obtain connection to the Apps Database.

Action: Check the connection information or try again.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-15213: The operation cannot complete because a valid EM Target was not provided.

Cause: A valid EM Target was not provided.

Action: Make sure the EM Target provided is valid.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-15214: The requested operation requires {0} EM Targets, {1} were provided.

Cause: An unexpected number of EM Targets were provided.

Action: Make sure the EM Targets provided are appropriate for the operation.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-15220: Cannot load resource bundle for {0} with locale {1}.

Cause: The resource bundle could not be loaded.

Action: Make sure the resource bundle exists for the required locale.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-15221: Unexpected exception localizing bundle '{0}', key '{1}': {2}

Cause: An entry in the bundle could not be localized.

Action: Check the entry for the provided key as well as the exception details provided.
Level: 1

Type: ERROR

Impact: Application Diagnostics

ODF-15222: Key '{0}' not found in bundle '{1}'.

Cause: The required entry was not found in the resource bundle.

Action: Make sure the requested key exists in the resource bundle.
Level: 1

Type: ERROR

Impact: Application Diagnostics

66 ODI-01100 to ODI-40960

ODI-01100: Agent {0} successfully cleaned up {1} stale sessions from work repository {2}.

Cause: null

Action: null
Level: 16

Type: NOTIFICATION

Impact: Other

ODI-01101: Agent {0} successfully completed session {1} ({2}) (for scenario {3}) on {4} using context {5} with statistics: Rows {6} Inserts {7} Updates {8} Deletes {9} Errors {10}.

Cause: null

Action: null
Level: 16

Type: NOTIFICATION

Impact: Other

ODI-01102: Agent {0} successfully completed session {1} ({2}) on {3} using context {4} with statistics: Rows {5} Inserts {6} Updates {7} Deletes {8} Errors {9}.

Cause: null

Action: null
Level: 16

Type: NOTIFICATION

Impact: Other

ODI-01103: Agent {0} successfully completed step {1} in session {2}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01104: Agent {0} successfully connected to master repository using {1}.

Cause: null

Action: null
Level: 16

Type: TRACE

Impact: Other

ODI-01105: Agent {0} successfully connected to work repository {1} using {2}.

Cause: null

Action: null
Level: 16

Type: TRACE

Impact: Other

ODI-01106: Agent {0} created load plan {1}.

Cause: null

Action: null
Level: 16

Type: TRACE

Impact: Other

ODI-01107: Agent {0} created session {1} ({2}) in work repository {3}.

Cause: null

Action: null
Level: 16

Type: TRACE

Impact: Other

ODI-01108: Agent {0} created session {1} ({2}) from scenario {3} in work repository {4} using context {5}.

Cause: null

Action: null
Level: 16

Type: TRACE

Impact: Other

ODI-01109: Agent {0} is delegating session {1} on work repository {2} to agent {3}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01110: Agent {0} successfully retrieved {1} schedules from work repository {2} using {3}.

Cause: null

Action: null
Level: 16

Type: NOTIFICATION

Impact: Other

ODI-01111: Agent {0} started. Agent version: {1}. Port: {2}. JMX Port: {3}.

Cause: null

Action: null
Level: 1

Type: NOTIFICATION

Impact: Other

ODI-01112: Agent {0} received a request to recalculate its schedule on work repository {1}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01113: Agent {0} received a data server test request for {1}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01114: Agent {0} received a request to stop load plan instance {1} on work repository {2}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01115: Agent {0} received a ping request.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01116: Agent {0} received a request to retrieve its schedule on work repository {1}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01117: Agent {0} received a request to restart load plan instance ({1}) in work repository {2}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01118: Agent {0} received a request to start load plan {1} on work repository {2} using context {3}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01119: Agent {0} received a request to start scenario {1}.{2} on work repository {3} using context {4}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01120: Agent {0} received a request to restart session {1} on work repository {2} using context {3}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01121: Agent {0} received a request to stop session {1} on work repository {2}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01122: Agent {0} successfully restarted {1} queued sessions from work repository {2} using {3}.

Cause: null

Action: null
Level: 16

Type: NOTIFICATION

Impact: Other

ODI-01123: Agent {0} sent a request to agent {1}.

Cause: null

Action: null
Level: 16

Type: TRACE

Impact: Other

ODI-01124: Agent {0} started load plan {1}.

Cause: null

Action: null
Level: 16

Type: NOTIFICATION

Impact: Other

ODI-01125: Agent {0} started session {1} ({2}) from scenario {3} in work repository {4} using context {5}.

Cause: null

Action: null
Level: 16

Type: NOTIFICATION

Impact: Other

ODI-01126: Agent {0} started session {1} ({2}) in work repository {3} using context {4}.

Cause: null

Action: null
Level: 16

Type: NOTIFICATION

Impact: Other

ODI-01127: Agent {0} started step {1} in session {2}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01128: Agent {0} is starting. Container: {1}. Agent Version: {2}. Port: {3}. JMX Port: {4}.

Cause: null

Action: null
Level: 1

Type: NOTIFICATION

Impact: Other

ODI-01129: Agent {0} stopped.

Cause: null

Action: null
Level: 1

Type: NOTIFICATION

Impact: Other

ODI-01130: Agent {0} is stopping.

Cause: null

Action: null
Level: 1

Type: NOTIFICATION

Impact: Other

ODI-01131: Agent {0} encountered an error: {1}

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01132: Agent {0} encountered a warning: {1}

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Other

ODI-01133: Agent {0} detected that the work repository {1} went down.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01134: Agent {0} encountered an error: {1}

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Other

ODI-01135: Agent {0} detected that the master repository went down.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01136: Starting Schedulers on Agent {0}.

Cause: null

Action: null
Level: 1

Type: NOTIFICATION

Impact: Other

ODI-01137: Scheduler started for work repository {0} on Agent {1}.

Cause: null

Action: null
Level: 1

Type: NOTIFICATION

Impact: Other

ODI-01138: Migrating Schedulers for Agent {0}.

Cause: null

Action: null
Level: 1

Type: NOTIFICATION

Impact: Other

ODI-01139: The current task of the session ({0}) does not support stop immediate. This session will be stopped normally by the Agent ({1}) before next task begins.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Other

ODI-01140: Unable to stop session ({0}) immediately. This session will be stopped by the agent ({1}) before next task begins.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Other

ODI-01141: Agent {0} started load plan instance {1} ({2}), run {3} in work repository {4}.

Cause: null

Action: null
Level: 16

Type: NOTIFICATION

Impact: Other

ODI-01142: Agent {0} successfully completed load plan instance {1} ({2}), run {3} in work repository {4}.

Cause: null

Action: null
Level: 16

Type: NOTIFICATION

Impact: Other

ODI-01143: Agent {0} started computing next steps from step {5} of load plan instance {1} ({2}), run {3} in work repository {4}. Triggering session={6}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01144: Agent {0} completed computing next steps from step {5} of load plan instance {1} ({2}), run {3} in work repository {4}. Triggering session={6}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01145: Agent {0} not found when trying to stop session with id {1} in work repository {2}.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Other

ODI-01146: Agent {0} invocation error when trying to stop session with id {1} in work repository {2}: {3}

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Other

ODI-01147: Agent {0} stopped load plan instance {1} ({2}), run {3} in work repository {4}.

Cause: null

Action: null
Level: 1

Type: NOTIFICATION

Impact: Other

ODI-01148: Agent {0} executing load plan log purge for work repository {1} at {2}.

Cause: null

Action: null
Level: 1

Type: NOTIFICATION

Impact: Other

ODI-01151: Agent {0} cannot continue load plan instance {1} ({2}), run {3} in work repository {4}, because the instance has been deleted.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Other

ODI-01152: Agent {0} continuing processing for load plan instance {1} ({2}), run {3} in work repository {4}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01153: An exception occurred while processing scheduled job for scenario {0} and version {1}. The exception message is : {2}

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01154: An exception occurred while processing scheduled job for loadplan {0}. The exception message is : {1}

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01155: Invalid repetition interval {0} specified in scheduled job for scenario {1} {2}. The schedule would not be repeated.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Other

ODI-01156: Invalid repetition interval {0} specified in scheduled job for loadplan {1}. The schedule would not be repeated.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Other

ODI-01157: Coherence cluster property {0} is not found in the system properties for Agent {1}. Agent may connect to an unintended coherence cluster.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Other

ODI-01158: Agent {0} started invoking load plan exception handler {5} for failed step {6} of load plan instance {1} ({2}), run {3} in work repository {4}. Caused by: step {6}: {7}

Cause: null

Action: null
Level: 16

Type: NOTIFICATION

Impact: Other

ODI-01159: Agent {0} completed load plan exception handler {5} for failed step {6} of load plan instance {1} ({2}), run {3} in work repository {4}.

Cause: null

Action: null
Level: 16

Type: NOTIFICATION

Impact: Other

ODI-01160: Agent {0} started processing load plan step {5} of load plan instance {1} ({2}), run {3} in work repository {4}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01161: Agent {0} completed load plan step {5} (status={6}) of load plan instance {1} ({2}), run {3} in work repository {4}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01162: Scheduled task failed with id {0} of work repository {1} on Agent {2}.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01163: The load plan logs purge operation failed on Agent {0}: {1}

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01165: Client requires a repository with version {0} but the repository version found is {1}.

Cause: Incorrect repository version.

Action: Check repository configuration.
Level: 1

Type: ERROR

Impact: Other

ODI-01200: Session start failure: the request is incorrectly formed.

Cause: A malformed request was sent to the agent.

Action: Verify the request format and parameters sent to the agent.
Level: 1

Type: ERROR

Impact: Other

ODI-01201: Session start failure on agent {0}: JDBC connection error occurs while connecting to the master repository.

Cause: An incorrect connection was used for the master repository database, or repository database was down.

Action: Verify the master repository connection information and the status of the master repository database.
Level: 1

Type: ERROR

Impact: Other

ODI-01202: Session start failure on agent {0}: data source for master repository does not contain a master repository.

Cause: The master repository connection information pointed to a database schema that did not contain a master repository.

Action: Verify the master repository connection information.
Level: 1

Type: ERROR

Impact: Other

ODI-01203: Session start failure on agent {0}: the master repository is in an invalid state.

Cause: The master repository was in a state that did not allow connections. This is the case if an upgrade was being performed.

Action: Verify the state of the master repository.
Level: 1

Type: ERROR

Impact: Other

ODI-01204: Session start failure on agent {0}: the master repository version {1} is not compatible with the agent version {2}.

Cause: The master repository was upgraded but not this agent, or the agent was upgraded but not the master repository.

Action: Upgrade the master repository version or the agent version.
Level: 1

Type: ERROR

Impact: Other

ODI-01205: Session start failure on agent {0}: an authentication error occurred while connecting to the master repository.

Cause: An incorrect ODI user or password was specified for this master repository.

Action: Verify the ODI user and password used for connecting.
Level: 1

Type: ERROR

Impact: Other

ODI-01206: Session start failure on agent {0}: the agent is not defined in the topology for master repository.

Cause: The session was not found in the master repository.

Action: Verify that a session with this ID exists in the repository.
Level: 1

Type: ERROR

Impact: Other

ODI-01207: Session start failure on agent {0}: JDBC connection error occurs while connecting to the work repository {1}.

Cause: An incorrect connection was used for the work repository database, or repository database was down.

Action: Verify the work repository connection information and the status of the work repository database.
Level: 1

Type: ERROR

Impact: Other

ODI-01208: Session start failure on agent {0}: database schema {1} does not contain a work repository.

Cause: The work repository connection information pointed to a database schema that did not contain a work repository.

Action: Verify the work repository connection information.
Level: 1

Type: ERROR

Impact: Other

ODI-01209: Session start failure on agent {0}: work repository {1} is in an invalid state.

Cause: The work repository was in a state that did not allow connections. This is the case if an upgrade was being performed.

Action: Verify the state of the work repository.
Level: 1

Type: ERROR

Impact: Other

ODI-01210: Session start failure on agent {0}: work repository {1} version {2} is not compatible with the agent version {3}.

Cause: The work repository was upgraded but not this agent, or the agent was upgraded but not the work repository.

Action: Upgrade the work repository version or the agent version.
Level: 1

Type: ERROR

Impact: Other

ODI-01211: Session start failure on agent {0}: work repository {1} is not bound to the master repository.

Cause: The work repository specified in the request was not found in the list of work repositories attached to this master.

Action: Verify that work repository name matches an existing one.
Level: 1

Type: ERROR

Impact: Other

ODI-01212: Session preparation failure: scenario {0} does not exist in work repository {1}.

Cause: The session request was received, but the agent was unable to find the named scenario in the work repository.

Action: Verify that the scenario name matches an existing scenario name in the work repository.
Level: 1

Type: ERROR

Impact: Other

ODI-01213: Session preparation failure: scenario {0} version {1} does not exist in work repository {2}.

Cause: The session request was received, and the scenario existed in the work repository, but not with the specified version.

Action: Ensure that the scenario version matches an existing scenario version in the work repository.
Level: 1

Type: ERROR

Impact: Other

ODI-01214: Session preparation failure: context {0} does not exist in the master repository.

Cause: The session request was received, but the agent was unable to find the context in the master repository.

Action: Ensure that the context matches an existing context code in the Topology.
Level: 1

Type: ERROR

Impact: Other

ODI-01215: Session preparation failure: privileges are insufficient to run scenario {0}.{1} in repository {2}.

Cause: User privileges were not sufficient for running this scenario in this repository.

Action: Ensure that the user has sufficient privileges for this task.
Level: 1

Type: ERROR

Impact: Other

ODI-01216: Session preparation failure: insufficient privileges to use Context {0} ({1}).

Cause: User privileges were not sufficient for using this context.

Action: Ensure that the user has sufficient privileges for this task.
Level: 1

Type: ERROR

Impact: Other

ODI-01217: Session {0} ({1}) fails with return code {2}.

Cause: The session finished in an error state.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01218: Session preparation failure: database error occurs while connecting to the master repository.

Cause: The agent received a database error from the master repository while creating the session.

Action: Verify the state of the master repository database.
Level: 1

Type: ERROR

Impact: Other

ODI-01219: Session preparation failure: database error while connecting to work repository {0}.

Cause: The agent received a database error from the work repository while creating the session.

Action: Verify the state of the work repository database.
Level: 1

Type: ERROR

Impact: Other

ODI-01220: Session preparation failure: an unexpected exception occurred.

Cause: The remote agent faced an unexpected error while attempting to create the session.

Action: Contact Oracle Support Services. Provide the error message, a description of the action causing this fault, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Other

ODI-01221: Unable to restart session {0}: session is not found in work repository {1}.

Cause: The session to restart did not exist in the repository. This session may have been deleted, or an incorrect session ID or work repository was supplied.

Action: Verify that a session with this ID exists in the repository.
Level: 1

Type: ERROR

Impact: Other

ODI-01222: Session start failure on agent {0}: logical schema {1} cannot be found in the master repository.

Cause: The object to be executed referred to a logical schema not present in the master repository.

Action: Ensure that the logical schema configuration exists in your master repository.
Level: 1

Type: ERROR

Impact: Other

ODI-01223: Database error while connecting to the master repository.

Cause: The connection for the master repository database was incorrect, or the repository database was down.

Action: Verify the master repository connection information and the status of the master repository database.
Level: 1

Type: ERROR

Impact: Other

ODI-01224: Database error while connecting to work repository {0}

Cause: The connection for the work repository database was incorrect, or the repository database was down.

Action: Verify the work repository connection information and the status of the master repository database.
Level: 1

Type: ERROR

Impact: Other

ODI-01225: An unexpected exception occurred.

Cause: The agent faced an unexpected exception.

Action: Contact Oracle Support Services. Provide the error message, a description of the action causing this fault, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Other

ODI-01226: Step {0} fails after {1} attempt(s).

Cause: This is an execution warning. The session step failed to execute after the maximum number of retries. If step failure was not handled in the package design, the session finished in an error state.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: WARNING

Impact: Other

ODI-01227: Task {0} ({1}) fails on the source {2} connection {3}.

Cause: This is an execution warning. The command on the source for this task finished with an error.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: WARNING

Impact: Other

ODI-01228: Task {0} ({1}) fails on the target {2} connection {3}.

Cause: This is an execution warning. The command on the target for this task finished with an error.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: WARNING

Impact: Other

ODI-01229: An error occurred while performing a {0} operation on model code {1}.

Cause: This is an execution warning. The operation specified failed on the model.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: WARNING

Impact: Other

ODI-01231: An error occurred while performing a {0} operation on datastore {1}.

Cause: This is an execution warning. The operation specified failed on the datastore.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: WARNING

Impact: Other

ODI-01232: Procedure {0} execution fails.

Cause: This is an execution warning. The procedure execution failed.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: WARNING

Impact: Other

ODI-01233: Error while evaluating variable the following expression: {0} {1} {2}

Cause: This is an execution warning. The variable evaluation failed.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: WARNING

Impact: Other

ODI-01235: Error while incrementing variable {0} to value {1}

Cause: This is an execution warning. The variable increment failed.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: WARNING

Impact: Other

ODI-01236: Error while refreshing variable {0}.

Cause: This is an execution warning. The variable refresh failed.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: WARNING

Impact: Other

ODI-01237: Error while setting variable {0} to value {1}.

Cause: This is an execution warning. The set variable operation failed.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: WARNING

Impact: Other

ODI-01238: Flow {0} fails because the maximum number of allowed errors ({1} rows) is exceeded during the flow check. This flow loads target table {2}.

Cause: This is an execution warning. The interface failed because the number of errors detected in the flow exceeded the value defined in the interface.

Action: Review the session execution details in the Operator Navigator or Repository Explorer. Review the erroneous records for this interface in the error table.
Level: 1

Type: WARNING

Impact: Other

ODI-01239: Flow {0} fails because the maximum percentage of allowed errors ({1} %) is exceeded during the flow check. This flow loads target table {2}.

Cause: This is an execution warning. The interface failed because the percentage of errors detected in the flow exceeded the value defined in the interface.

Action: Review the session execution details in the Operator Navigator or Repository Explorer. Review the erroneous records for this interface in the error table.
Level: 1

Type: WARNING

Impact: Other

ODI-01240: Flow {0} fails while performing a {1} operation. This flow loads target table {2}.

Cause: This is an execution warning. The interface failed because one of the statements returned an error return code.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: WARNING

Impact: Other

ODI-01241: Oracle Data Integrator tool execution fails.

Cause: This is an execution warning. The tool execution failed.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: WARNING

Impact: Other

ODI-01242: Operating system command execution fails.

Cause: This is an execution warning. Execution of the operating system command failed.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: WARNING

Impact: Other

ODI-01243: Session {0} ({1}) fails because work repository {2} went down.

Cause: Work repository database went down while session was being executed.

Action: Verify the state of the work repository database. The session must be restarted.
Level: 1

Type: ERROR

Impact: Other

ODI-01244: Session {0} {1} was prepared successfully but fails because work repository {2} went down before execution could begin.

Cause: Work repository database went down while session was starting its execution.

Action: Verify the state of the work repository database. The session must be restarted.
Level: 1

Type: ERROR

Impact: Other

ODI-01245: Session preparation failure: work repository {0} went down during session preparation.

Cause: Work repository went down while session was being prepared.

Action: Verify the state of the work repository database. The session must be restarted.
Level: 1

Type: ERROR

Impact: Other

ODI-01246: The Logical Schema has not been set for {0}.

Cause: Because the logical schema had not been set, the object could not be executed.

Action: Verify the object that you are trying to execute, and set the logical schema for this object.
Level: 1

Type: ERROR

Impact: Other

ODI-01247: Session {0} {1} was prepared successfully but fails because master repository went down before execution could begin.

Cause: Master repository database went down while session was starting its execution.

Action: Verify the state of the master repository database. The session must be restarted.
Level: 1

Type: ERROR

Impact: Other

ODI-01248: Session preparation failure by Agent {0}: master repository went down during session preparation.

Cause: Master repository went down while session was being prepared.

Action: Verify the state of the master repository database. The session must be restarted.
Level: 1

Type: ERROR

Impact: Other

ODI-01249: Session {0} ({1}) fails because master repository went down.

Cause: Master repository database went down while session was being executed.

Action: Verify the state of the master repository database. The session must be restarted.
Level: 1

Type: ERROR

Impact: Other

ODI-01250: Session {0} ({1}) could not be stopped by Agent {2} because session {0} {1} already completed execution.

Cause: The session has already completed and cannot be stopped.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01251: Session ({0}) could not be stopped by Agent {1} because session ({0}) was not found in work repository {2}.

Cause: The session was not found in the work repository.

Action: Verify that a session with this ID exists in the repository.
Level: 1

Type: ERROR

Impact: Other

ODI-01252: Session ({0}) could not be stopped by Agent {1}: insufficient privileges to access session.

Cause: User privileges were not sufficient for accessing this session in this agent.

Action: Ensure that the user has sufficient privileges for this task.
Level: 1

Type: ERROR

Impact: Other

ODI-01253: Session {0} ({1}) could not be stopped by Agent {2}: an unknown error occurred.

Cause: An unexpected Exception occurred.

Action: Verify your Agent configuration and make sure other operations on Agent are working correctly.
Level: 1

Type: ERROR

Impact: Other

ODI-01254: Session {0} ({1}) could not be stopped by Agent {2}: a JDBC error occurred on work repository {3}.

Cause: The agent had incorrect connection for the work repository database, or repository database was down.

Action: Verify the work repository connection information and the status of the work repository database.
Level: 1

Type: ERROR

Impact: Other

ODI-01255: Session {0} ({1}) could not be stopped by Agent {2}: insufficient privileges to stop the session.

Cause: User privileges were not sufficient for stopping this session in this agent.

Action: Ensure that the user has sufficient privileges for this task.
Level: 1

Type: ERROR

Impact: Other

ODI-01256: Session {0} ({1}) stopped (Normal) by user {2}.

Cause: Session was stopped by the user.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01257: Session {0} ({1}) stopped (Immediate) by user {2}.

Cause: Session was stopped by the user.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01258: Session {0} ({1}) stopped (Abort) by user {2}.

Cause: Session was aborted by the user.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01259: Session Task {0} ({1}) stopped (Normal) by user {2}.

Cause: Task was stopped by the user.

Action: Review the task execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01260: Session Task {0} ({1}) stopped (Immediate) by user {2}.

Cause: Task was stopped by the user.

Action: Review the task execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01261: Session Task {0} ({1}) stopped (Abort) by user {2}.

Cause: Task was aborted by the user.

Action: Review the task execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01262: Session {0} ({1}) could not be stopped by Agent {2}: a JDBC error occurred on master repository.

Cause: The agent had incorrect connection for the master repository database, or repository database was down.

Action: Verify the master repository connection information and the status of the master repository database.
Level: 1

Type: ERROR

Impact: Other

ODI-01263: Step {0} stopped (Normal) by user {1}.

Cause: Step was stopped by the user.

Action: Review the step execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01264: Step {0} stopped (Immediate) by user {1}.

Cause: Step was stopped by the user.

Action: Review the step execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01265: Step {0} stopped (Abort) by user {1}.

Cause: Step was aborted by the user.

Action: Review the step execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01266: Agent {0} detected Session as stale session and set to error status.

Cause: The agent detected a stale session and the session status was set to error status.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01267: Session ({0}) could not be stopped by Agent {1} because stop type {2} provided in the request is an invalid stop type.

Cause: The agent attempted to stop a session with an invalid stop type.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01268: Agent {0} does not support stopping asynchronous child sessions.

Cause: The agent attempted to stop an asynchronous child session and this is not supported.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01269: Session {0} ({1}) could not be stopped by Agent {2}: session is being run by another Agent with the same name.

Cause: The agent attempted to stop a session that is being run by a different agent.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01270: Session {0} ({1}) could not be stopped by Agent {2}: session {0} ({1}) is being run by {3} Agent which is not a listener Agent.

Cause: The agent attempted to stop a session that is being run by the internal agent and this is not supported.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01271: The asynchronous jndi name cannot be null for asynchronous jobs. The ESS job status cannot be updated.

Cause: The agent attempted to set the status of the asynchronous ESS job and its jndi name was not set.

Action: Review the jndi name supplied to the Enterprise Scheduler job.
Level: 1

Type: WARNING

Impact: Other

ODI-01272: The Logical Schema has not been set on {0} for {1}.

Cause: The logical schema for this object has not been set.

Action: Verify that the logical schema has been set in the Topology.
Level: 1

Type: ERROR

Impact: Other

ODI-01273: The selected technology {0} is not supported on source for {1}.

Cause: The selected technology is not supported for this object.

Action: Verify that the object has a valid technology.
Level: 1

Type: ERROR

Impact: Other

ODI-01274: Agent Exception

Cause: An error was detected by the agent when performing an operation.

Action: Review the underlying exception for more details.
Level: 1

Type: ERROR

Impact: Other

ODI-01275: An error occurred while performing a {0} operation on submodel step {1} of the model code {2}.

Cause: This is an execution warning. The operation specified failed on the submodel operation.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: WARNING

Impact: Other

ODI-01276: An error occurred while executing the OnConnect command on JDBC connection created for data server {0} with transaction label {1}.

Cause: An error was occurred while executing the OnConnect command on the JDBC connection created to the data server.

Action: Review the underlying exception and update the OnConnect command definition configured for the data server.
Level: 1

Type: ERROR

Impact: Other

ODI-01277: An error occurred while executing the OnDisconnect command on JDBC connection created for data server {0} with transaction label {1}.

Cause: An error was occurred while executing the OnDisconnect command on the JDBC connection created to the data server.

Action: Review the underlying exception and update the OnDisconnect command definition configured for the data server.
Level: 1

Type: ERROR

Impact: Other

ODI-01278: Load plan instance {0}, run {1} does not exist in work repository {2}.

Cause: The Load Plan Instance run does not exist in the repository. This Load Plan Instance run may have been deleted, or an incorrect instance ID/run number or work repository was supplied.

Action: Verify that a load plan instance run with this instance ID and run number exists in the repository.
Level: 1

Type: ERROR

Impact: Other

ODI-01279: The Source Logical Schema {0} and Context {1} of the task {2} are not mapped to any Physical Schema.

Cause: The Logical Schema to Physical Schema Mapping is not defined for the Context used.

Action: For the Context used define the Logical Schema to Physical Schema Mapping in the Topology.
Level: 1

Type: ERROR

Impact: Other

ODI-01280: The Target Logical Schema {0} and Context {1} of the task {2} are not mapped to any Physical Schema.

Cause: The Logical Schema to Physical Schema Mapping is not defined for the Context used.

Action: For the Context used define the Logical Schema to Physical Schema Mapping in the Topology.
Level: 1

Type: ERROR

Impact: Other

ODI-01281: Source Technology {0} of task {1} is not of JDBC Type. When both Source and Target commands are specified, the Source Technology should be of JDBC type.

Cause: When Source and Target commands are specified, the Source Technology should always be of JDBC type.

Action: Make Sure that you modify your Procedure or KM to either use a JDBC Source Technology or edit your step to use only the Target command.
Level: 1

Type: ERROR

Impact: Other

ODI-01282: Invalid log level {0} is specified. A valid log level value is between {1} and {2}.

Cause: Invalid log level specified for scenario/session invocation or for session restart.

Action: Please specify a valid log level.
Level: 1

Type: ERROR

Impact: Other

ODI-01283: Owb preparation failure: Owb object {0} of type {1} in location {2} does not exist in Owb repository {3}.

Cause: The session request was received, but the agent was unable to find the named Owb object in the Owb repository.

Action: Verify that the Owb object name matches an existing Owb object in the location in the Owb repository.
Level: 1

Type: ERROR

Impact: Other

ODI-01284: Session {0} ({1}) with Owb audit Id {2} fails.

Cause: The session finished in an error state.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01285: Session {0} ({1}) Retreival of audit for auditId {2} failed in the {3} phase {4}. Please use OWB Design Client or Browser for further information.

Cause: An error was raised during the retreival of the Owb audit data.

Action: Review the session execution details in the Operator Navigator or Repository Explorer. Also please use OWB Design Client or Browser for further information.
Level: 1

Type: ERROR

Impact: Other

ODI-01286: Session {0} ({1}) could not find Owb job for this session.

Cause: The session being aborted is not an Owb Job.

Action: Review the session being aborted in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01287: Session {0} ({1}) with Owb audit Id {2} is in an invalid state to be aborted.

Cause: The session being aborted is not in a state that can be aborted.

Action: Review the session execution details in the Operator Navigator or Repository Explorer. Also please use OWB Design Client or Browser for further information.
Level: 1

Type: ERROR

Impact: Other

ODI-01288: Session {0} ({1}) with Owb audit Id {2} abort fails.

Cause: The session abort finished in an error state.

Action: Review the session execution details in the Operator Navigator or Repository Explorer. Also please use OWB Design Client or Browser for further information.
Level: 1

Type: ERROR

Impact: Other

ODI-01289: Agent {0} detected Session as stale session and set to error status. Please use OWB Design Client or Browser for further information.

Cause: The agent detected a stale OWB session and the session status was set to error status.

Action: Review the session execution details in the OWB Design Client or Browser.
Level: 1

Type: ERROR

Impact: Other

ODI-01290: Session {0} ({1}) Loading of audit for auditId {2} failed in the {3} phase {4}.

Cause: An error was raised during the loading of the Owb audit data.

Action: Review the session execution details in the Operator Navigator or Repository Explorer. Also please use OWB Design Client or Browser for further information.
Level: 1

Type: ERROR

Impact: Other

ODI-01291: Workspace {0} cannot be resolved to a physical workspace using context {1}.

Cause: The context does not contain a mapping for the logical workspace.

Action: Review the mappings defined in the context.
Level: 1

Type: ERROR

Impact: Other

ODI-01292: An execution context cannot be determined for this job.

Cause: An execution context cannot be determined for this job.

Action: Use the Context to provide an explicit context for this execution.
Level: 1

Type: ERROR

Impact: Other

ODI-01293: Exception occurred during spawning of ECID to child session.

Cause: Spawning of ECID from parent session to child session failed.

Action: Review the exception raised to get more detail.
Level: 1

Type: WARNING

Impact: Other

ODI-01294: Unwrapping of a wrapped ECID [{0}] failed.

Cause: Unwrapping of ECID failed.

Action: Review the exception raised and the format of wrapped ECID to get more detail on unwrap failure
Level: 1

Type: WARNING

Impact: Other

ODI-01295: Cleanup of Session {0} ({1}) raised the following {2} messages: {3}

Cause: Messages were raised during the Cleanup phase.

Action: Review the messages raised during the Cleanup and you may need to perform some manual cleanup.
Level: 1

Type: WARNING

Impact: Other

ODI-01296: The Cleanup Tool encountered the following {0} nested errors when executing the Cleanup tasks: {1}

Cause: Messages were raised during the Cleanup tool execution.

Action: Review the messages raised during the Cleanup and you may need to perform some manual cleanup.
Level: 1

Type: ERROR

Impact: Other

ODI-01297: Parallel task "{0}" failed; {1} child task(s) in error; Failed child tasks: {2}

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01298: Serial task "{0}" failed because child task "{1}" is in error.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01299: A task "{0}" from one of the parallel branches has failed. Hence aborting the current branch

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01300: ASYNC_JNDI_NAME cannot be null for async job.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01301: Unable to submit Job Definition: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01302: Logical Agent {0} must be mapped to a Physical Agent in the ContextCode {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01303: RuntimeSessionfactory must not be null.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01304: Unable to find request for ID {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01305: jobDefinitionId must not be null

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01306: scheduleDefinitionId must not be null

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01307: ContextCode is null, cannot lookup physical agent

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01308: SchedulingService object was created without an EntityManager, cannot lookup physical agent

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01309: Unable to find logical agent : {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01310: Unable to find context : {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01311: JobDefinition with name {0} already exists.

Cause: JobDefinition already exists.

Action: Check JobDefinition name.
Level: 32

Type: ERROR

Impact: Other

ODI-01312: Schedule with name {0} already exists.

Cause: Schedule already exists.

Action: Check Schedule name.
Level: 32

Type: ERROR

Impact: Other

ODI-01313: Unable to find job definition for ID {0}.

Cause: Wrong ID.

Action: Check ID.
Level: 32

Type: ERROR

Impact: Other

ODI-01314: Unable to find job definition with name {0}.

Cause: Wrong name.

Action: Check name.
Level: 32

Type: ERROR

Impact: Other

ODI-01315: Unable to update job definition.

Cause: Exception during updating.

Action: Check cause exception details.
Level: 32

Type: ERROR

Impact: Other

ODI-01316: Unable to remove job request.

Cause: Exception was thrown.

Action: Check cause exception details.
Level: 32

Type: ERROR

Impact: Other

ODI-01317: Unable to find scheduler definition with name {0}.

Cause: Wrong name.

Action: Check name.
Level: 32

Type: ERROR

Impact: Other

ODI-01318: jobDefnition is required to have a not null ID.

Cause: Metadata Object ID is null.

Action: Check job definition.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-01350: Credential map key ''{0}'' not found in credential map ''{1}''.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01351: An unexpected error was thrown during execution of the scenario ''{0} - {1}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01352: An unexpected error was thrown during job execution

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01353: RequestId={0} Scenario={1} : Agent URL must be specified. The Job Definition must include the LocalAgent or the job submission must include a physical agent url ({2}) parameter.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01354: Load plan must be asynchronous

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01355: username ''{0}'' from credential map ''{1}'' does not match currentSubjectName ''{2}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01356: Credential map key parameter ''{0}'' not found.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01357: Error resolving ADF connection for connectionId=''{0}''.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01400: Agent {0} start failure: JDBC connection error occurs while connecting to the master repository.

Cause: The master repository information was incorrect, or the repository database was down.

Action: Verify the master repository connection information and the status of the master repository database.
Level: 1

Type: ERROR

Impact: Other

ODI-01401: Agent {0} start failure: data source for master repository did not contain a master repository.

Cause: The master repository connection information pointed to a database schema that did not contain a master repository.

Action: Verify the master repository connection information.
Level: 1

Type: ERROR

Impact: Other

ODI-01402: Agent {0} start failure: the master repository is in an invalid state.

Cause: The master repository was in a state that did not allow connections. This is the case when an upgrade is being performed.

Action: Verify the state of the master repository.
Level: 1

Type: ERROR

Impact: Other

ODI-01403: Agent {0} start failure: the master repository version {1} is not compatible with the agent version {2}.

Cause: The master repository was upgraded but not this agent, or the agent was upgraded but not the master repository.

Action: Upgrade the master repository version or the agent version.
Level: 1

Type: ERROR

Impact: Other

ODI-01404: Agent {0} start failure: an authentication error occurred while connecting to the master repository.

Cause: An incorrect ODI user or password was specified for this master repository.

Action: Verify the ODI user and password used for connecting.
Level: 1

Type: ERROR

Impact: Other

ODI-01405: Agent {0} start failure: the agent is not defined in the topology for master repository.

Cause: This agent was not declared in the topology.

Action: Add this physical agent in the list of agents in the ODI topology.
Level: 1

Type: ERROR

Impact: Other

ODI-01406: Agent {0} started with warning: JDBC connection error occurs while connecting to the work repository {1}.

Cause: The work repository information was incorrect, or the repository database was down.

Action: Verify the work repository connection information and the status of the work repository database.
Level: 1

Type: ERROR

Impact: Other

ODI-01407: Agent {0} started with warning: connection details of {1} do not contain a work repository.

Cause: The work repository connection information pointed to a database schema that did not contain a work repository.

Action: Review the work repository connection information and revise it as necessary.
Level: 1

Type: ERROR

Impact: Other

ODI-01408: Agent {0} started with warning: work repository {1} is in an invalid state.

Cause: The work repository was in a state that did not allow connections. This is the case when an upgrade is being performed.

Action: Verify the state of the work repository.
Level: 1

Type: ERROR

Impact: Other

ODI-01409: Agent {0} started with warning: work repository {1} version {2} is not compatible with the agent version {3}.

Cause: The work repository was upgraded but not this agent, or the agent was upgraded but not the work repository.

Action: Upgrade the work repository version or the agent version.
Level: 1

Type: ERROR

Impact: Other

ODI-01410: Agent {0} started with warning: work repository {1} is not bound to the master repository.

Cause: The work repository specified in the request was not found in the list of work repositories attached to this master.

Action: Ensure that work repository name matches an existing one.
Level: 1

Type: ERROR

Impact: Other

ODI-01411: Agent {0} started with warning: a database error occurs while cleansing stale sessions.

Cause: The agent encountered a database error while attempting to close stale sessions.

Action: Review the status of the sessions for this agent, and manually remove the stale sessions.
Level: 1

Type: ERROR

Impact: Other

ODI-01412: Agent {0} started with warning: an unexpected error occurs while cleaning stale sessions.

Cause: The agent encountered an unexpected error while attempting to close stale sessions.

Action: Contact Oracle Support Services. Provide the error message, a description of the action causing this fault, and the exception stack trace in the log files (with the logging level set to debug mode). Verify the status of the sessions for this agent, and manually remove the stale sessions.
Level: 1

Type: ERROR

Impact: Other

ODI-01413: Request is incorrectly formed.

Cause: A malformed request was sent to the agent.

Action: Review the request format and parameters sent to the agent.
Level: 1

Type: ERROR

Impact: Other

ODI-01414: Error connecting to agent {0}: a JDBC error occurs while connecting to the master repository.

Cause: The remote agent had incorrect connection for the master repository database, or repository database was down.

Action: Verify the master repository connection information and the status of the master repository database.
Level: 1

Type: ERROR

Impact: Other

ODI-01415: Error connecting to agent {0}: data source for master repository did not contain a master repository.

Cause: The master repository connection information for the remote agent pointed to a database schema that did not contain a master repository.

Action: Review the master repository connection information and revise it as necessary.
Level: 1

Type: ERROR

Impact: Other

ODI-01416: Error connecting to agent {0}: the master repository is in an invalid state.

Cause: The master repository was in a state that did not allow connections from the remote agent. This is the case when an upgrade is being performed.

Action: Verify the state of the master repository.
Level: 1

Type: ERROR

Impact: Other

ODI-01417: Error connecting to agent {0}: the master repository version {1} is not compatible with the agent version {2}.

Cause: The master repository was upgraded but not the remote agent, or the remote agent was upgraded but not the master repository.

Action: Upgrade the master repository version or the agent version.
Level: 1

Type: ERROR

Impact: Other

ODI-01418: Error connecting to agent {0}: an authentication error occurs while connecting to the master repository.

Cause: An incorrect ODI user or password was specified for this master repository.

Action: Verify the ODI user and password used for connecting.
Level: 1

Type: ERROR

Impact: Other

ODI-01419: Warning connecting to Agent {0}: JDBC connection error occurs while connecting to the work repository {1}.

Cause: The remote agent had incorrect connection for the work repository database, or the repository database was down.

Action: Verify the work repository connection information and the status of the work repository database.
Level: 1

Type: ERROR

Impact: Other

ODI-01420: Warning connecting to Agent {0}: connection details of {1} do not contain a work repository.

Cause: The work repository connection information for the remote agent pointed to a database schema that did not contain a work repository.

Action: Verify the work repository connection information.
Level: 1

Type: ERROR

Impact: Other

ODI-01421: Warning connecting to Agent {0}: work repository {1} is in an invalid state.

Cause: The work repository was in a state that did not allow connections from the remote agent. This is the case when an upgrade is being performed.

Action: Verify the state of the work repository.
Level: 1

Type: ERROR

Impact: Other

ODI-01422: Warning connecting to Agent {0}: work repository {1} version {2} is not compatible with the agent version {3}.

Cause: The work repository was upgraded but not the remote agent, or the remote agent was upgraded but not the work repository.

Action: Upgrade the work repository version or the agent version.
Level: 1

Type: ERROR

Impact: Other

ODI-01423: Warning connecting to Agent {0}: work repository {1} is not bound to the master repository.

Cause: The work repository specified in the request was not found in the list of work repositories attached to the master.

Action: Verify that work repository name matches an existing one.
Level: 1

Type: ERROR

Impact: Other

ODI-01424: Agent host or port cannot be reached using {0}.

Cause: Incorrect host or port information was provided, or the agent was not started on the remote host.

Action: Correct the host or port information or start the agent.
Level: 1

Type: ERROR

Impact: Other

ODI-01425: Agent application cannot be reached using {0}.

Cause: An incorrect application name was provided for this agent, or the agent application was not started on the host.

Action: Correct the application name used in the URL or verify the agent status.
Level: 1

Type: ERROR

Impact: Other

ODI-01426: Agent {0} is not defined in the topology for the master repository.

Cause: This agent was not declared in the topology.

Action: Add this physical agent to the list of agents in the ODI topology.
Level: 1

Type: ERROR

Impact: Other

ODI-01427: invalid parameters

Cause: Invalid parameters were supplied in the request.

Action: Check the parameters that were supplied as part of the request. Ensure that parameter names and cases are correct.
Level: 1

Type: WARNING

Impact: Other

ODI-01428: internal error

Cause: An agent internal error occurred.

Action: Contact Oracle Support Services. Provide the error message, a description of the action causing this fault, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: FATAL

Impact: Other

ODI-01429: The user {0} is not authorized to perform request {1} on Agent {2}.

Cause: The user had insufficient privileges for performing this request against the remote agent.

Action: Amend the user privileges.
Level: 1

Type: ERROR

Impact: Other

ODI-01430: Agent {0} cannot clean the stale sessions in work repository {1} due to a database error.

Cause: The remote agent faced a database error while attempting to close stale sessions.

Action: Examine the status of the sessions for this agent, and manually remove the stale sessions.
Level: 1

Type: ERROR

Impact: Other

ODI-01431: Agent {0} cannot clean the stale sessions in work repository {1} because the work repository {1} is still down.

Cause: The remote agent was not able to connect to the work repository while attempting to close stale sessions.

Action: Determine the status of the repository. Once this repository is running, manually remove the stale sessions.
Level: 1

Type: ERROR

Impact: Other

ODI-01432: Agent {0} cannot clean the stale sessions in work repository {1} due to an unexpected error.

Cause: The remote agent faced an unexpected error while attempting to close stale sessions.

Action: Contact Oracle Support Services. Provide the error message, a description of the action causing this fault, and the exception stack trace in the log files (with the logging level set to debug mode). Determine the status of the sessions for this agent, and manually remove the stale sessions.
Level: 1

Type: ERROR

Impact: Other

ODI-01433: The Internal agent does not support cleaning stale sessions from multiple work repositories.

Cause: Empty string value was passed for the work repository name in the Clean Stale Sessions request sent to the Internal Agent.

Action: Specify a non-empty valid work repository name in the Clean Stale Sessions request sent to the Internal Agent. If you want to clean the stale sessions across the work repositories, perform this operation on a Remote physical Agent.
Level: 1

Type: ERROR

Impact: Other

ODI-01434: Agent {0} start failure: error while trying to use JMX Port {1}.

Cause: JMX Registry was unable to use the given port.

Action: Specify a different port by using the command-line parameter JMXPORT.
Level: 1

Type: ERROR

Impact: Other

ODI-01435: Storage space for the IDs of some object types is low in Repository {0}. When no storage space is available, it will not be possible to create obects of these types. Consider creating a new repository for the following object types (Object Type: Number Remaining) {1}.

Cause: Storage space was low for some IDs in this repository.

Action: Consider creating a new repository.
Level: 1

Type: WARNING

Impact: Other

ODI-01436: Error retrieving ID statistics for repository {0}.

Cause: The ID statistics for this repository could not be verified.

Action: Verify the statistics for this repository manually.
Level: 1

Type: WARNING

Impact: Other

ODI-01437: Error retrieving information from the credential store map.

Cause: Could not retrieve information from the credential store map.

Action: Verify that the credentials have been entered correctly into the credential store map.
Level: 1

Type: ERROR

Impact: Other

ODI-01438: Agent {0} cannot be stopped by user {1}: a JDBC error occurred on master repository {2}.

Cause: Some SQL Exception occurred on the Master Repository.

Action: Verify that other operations on the Agent are working correctly.
Level: 1

Type: ERROR

Impact: Other

ODI-01439: Agent {0} cannot be stopped by user {1}: a JDBC error occurred on work repository {2}.

Cause: Some SQL Exception occurred on the Work Repository.

Action: Verify that other operations on the Agent are working correctly.
Level: 1

Type: ERROR

Impact: Other

ODI-01440: Agent {0} cannot be stopped by user {1}: an unknown error occurred.

Cause: An unexpected Exception occurred.

Action: Verify your Agent configuration and make sure other operations on Agent are working correctly.
Level: 1

Type: ERROR

Impact: Other

ODI-01441: Unable to connect to the master repository at JBDC URL={0} with USER={1}.

Cause: An SQLException occurred while creating connection to the master repository with the given parameters.

Action: Verify your Agent configuration and make sure the master repository connection parameters are correct.
Level: 1

Type: ERROR

Impact: Other

ODI-01442: Unable to load JBDC Driver {0} configured for master repository connection.

Cause: ClassNotFoundException occurred while loading the driver class.

Action: Verify your Agent configuration and make sure the driver specified for master repository connection is correct and the corresponding jar is present under driver folder.
Level: 1

Type: ERROR

Impact: Other

ODI-01443: Error while starting agent : {0}

Cause: Error occurred while starting the embedded web container.

Action: Verify your Agent configuration and make sure that the specified ports are available.
Level: 1

Type: ERROR

Impact: Other

ODI-01444: The master repository signature specified by the client {0} does not match the master repository signature of the agent {1}.

Cause: The client and the agent are not using the same master repository

Action: Verify the client and the agent are using the same master repository. Verify that the client is calling the correct agent.
Level: 1

Type: ERROR

Impact: Other

ODI-01445: Invalid HTTP/S URL retrieved from the JRF utility : {0}

Cause: JRF utility has returned an invalid HTTP/S URL for the agent.

Action: Verify if ODI agent's dependent modules are successfully deployed on the container.
Level: 1

Type: ERROR

Impact: Other

ODI-01500: SQL Exception when accessing work repository {0} while executing load plan instance {1} - {2}

Cause: A SQLException was thrown when trying to update the work repository

Action: The same set of updates will be attempted later, potentially from a different agent
Level: 1

Type: ERROR

Impact: Other

ODI-01501: Cannot find variable "{0}" in the definition of load plan instance {1}.

Cause: The start/restart load plan request contained startup values for variables that are not defined in the load plan

Action: User error or problem in the IDE invocation code
Level: 1

Type: ERROR

Impact: Other

ODI-01502: Load plan instance {0} is in an inconsistent state: {1}

Cause: Indicates a problem in the ODI code, like a wrapped IllegalStateException

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01503: Load plan logs for instance {0}, run {1} are corrupted: {2}

Cause: Indicates a problem in the ODI code, it is a wrapped IllegalStateException

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01504: Trying to update variables during execution of step "{0}" (load plan instance {1}, run {2}), as part of the exception handler for step "{3}", but variable updates during exception handlers are not supported.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01505: Current value "{0}" of variable "{1}" (while evaluating When clause "{2}") is not a valid value of type {3} (load plan instance {4}, run {5}).

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01506: "Comparison value of step "{2}" ("{0}") is not a valid value of type {3} (load plan instance {4}, variable tested "{1}").

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01507: Load Plan Instance restart called for instance {0}, but no previous runs were found.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01508: Load Plan Instance start called for instance {0}, but previous runs have been found.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01509: Load Plan Instance {0} cannot be restarted because the previous run ({1}) status "{2}" is not in "{3}" status.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01510: The same load plan instance {0} simultaneously started by two agents.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01511: Step "{0}" should have already been marked as started before adding value for variable "{1}" (load plan instance {2}, run {3}).

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01512: Variable "{0}" is defined as having datatype "{1}" in Load Plan instance {2}, but as having type "{3}" in scenario "{4}" (version {5}), Load Plan instance step "{6}".

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01513: Error reading load plan information for session number {0}: "{1}"

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01514: Error trying to stop load plan, instance {0} not found.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01515: Load Plan instance {0} could not be stopped by agent {1} because stop type ({2}) provided in the request is invalid.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01516: Can not start load plan: load plan with name "{0}" does not exist in work repository {1}.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01517: Load Plan instance {0}, run {1} could not be stopped because that run is already completed (with status "{2}").

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01518: Parallel step "{0}" failed; {1} child step(s) in error, which is more than the maximum number of allowed errors ({3}) defined for the parallel step. Failed child steps: {2}

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01519: Serial step "{0}" failed because child step "{1}" is in error.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01520: Case-When/Else step "{0}" failed because child step "{1}" is in error.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01521: Case step "{0}" failed; the selected child "{1}" is in error.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01522: Run Scenario step failed during invocation. Error message was: {0}

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01523: Exception handler for step "{0}" failed, because the root exception serial step "{1}" is in error.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01524: Physical agent {0} could not be found.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01525: Physical agent not found for logical agent name "{0}" and context "{1}" while executing step "{2}".

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01526: Error encountered while trying to start scenario "{1}{2}" (step "{3}"): {0}

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01527: Error refreshing variable "{0}": the associated SQL query returned no results.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01528: Error refreshing variable "{0}": {1}

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01529: Refresh of variable "{0}" failed : {1} {2}

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01530: Load plan instance was stopped by user request.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01531: Timeout triggered while executing step "{0}".

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01532: Timeout triggered on a parent step "{0}" while executing step "{1}".

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01533: Error refreshing variable "{0}": could not get a connection to the logical schema "{1}" using context {2}.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01534: Could not get SQL query text for variable "{0}" while trying to refresh it.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01535: Can not continue load plan instance {0}, run {1}, because the instance has been deleted.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01536: Load plan instance {0}, run {1} failed to launch scenario: scenario {2} does not exist in work repository {3}.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01537: Load plan instance {0}, run {1} failed to launch scenario: Version {3} of scenario {2} does not exist in work repository {4}.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01538: Unexpected Exception occurred while executing Load plan instance {0}, run {1}.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01539: Agent {0} cannot continue load plan processing for instance {1}, run {2} on work repository {3}.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01540: Agent {0} start failure: error while trying to use Http Port {1}.

Cause: Http service was unable to use the given port.

Action: Specify a different port by using the command-line parameter PORT.
Level: 1

Type: ERROR

Impact: Other

ODI-01541: Load Plan start failure on agent {0}: ODI User and Password not specified.

Cause: ODI user and password are not set.

Action: Please specify ODI user and password.
Level: 1

Type: ERROR

Impact: Other

ODI-01542: Start Scenario failure on agent {0}: ODI User and Password not specified.

Cause: ODI User and password are not set.

Action: Please specify ODI user and password.
Level: 1

Type: ERROR

Impact: Other

ODI-01543: RuntimeAgent cannot be used inside an opened transaction, it must be used outside a TransactionTemplate

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01544: None of the agents in Load Balancing list is able to handle this execution ({0}).

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01545: Missing odi supervisor credentials in credential store map [{0}] with key [{1}].

Cause: Could not retrieve information from the credential store map.

Action: Verify that the credentials have been entered correctly into the credential store map.
Level: 1

Type: ERROR

Impact: Other

ODI-01546: The dbms_lock acquisition with lock handle {0} timed out.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01547: The Agent detected deadlock on dbms_lock acquisition with lock handle {0}.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01548: The dbms_lock acquisition failed with illegal lock handle {0}.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01549: The dbms_lock acquisition with lock handle {0} failed with illegal params error. The parameters are {1}.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01550: The dbms_lock acquisition with lock handle {0} failed with unknown return code {1}

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01551: The dbms_lock acquisition failed with a sql exception {0}. Please check if the work repository db user has EXECUTE privilege on DBMS_LOCK package.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01552: The dbms_lock release failed with illegal lock handle {0}.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01553: The dbms_lock release for lock handle {0} failed with invalid parameters.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01554: The dbms_lock release for lock handle {0} failed because you do not own the lock.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01555: The dbms_lock release for lock handle {0} failed with an unknown return code {1}.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01556: The lock acquisition failed. The lock is already locked by other connection object.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01557: Error refreshing variable "{0}": the associated SQL query returned a NULL value.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01558: The session {0} corresponding to the load plan step {1} of load plan instance {2}, run {3} is not found. We assume this step to be in error status.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01559: Load Plan Instance {0} cannot be restarted because the context {1} was not found in the work repository {2}.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01560: Load Plan {0} cannot be started because the context {1} was not found in the work repository {2}.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01561: Load Plan {0} cannot be started because the user {1} does not have view privileges to the execution context {2}.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01562: Load Plan Instance {0} cannot be restarted because the user {1} does not have view privileges to the execution context {2}.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01563: Load Plan {0} cannot be started because the user {1} does not have execute privileges to the Load Plan {0}.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01564: Load Plan Instance {0} cannot be restarted because the user {1} does not have restart privileges.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01565: Load Plan {0} cannot be started because an unknown exception occurred.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01566: Load Plan Instance {0} cannot be restarted because an unknown exception occurred.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01567: Load Plan {0} cannot be started because a SQL Exception occurred.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01568: Load Plan Instance {0} cannot be restarted because a SQL Exception occurred.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01569: Error trying to stop load plan, instance {0} run {1} not found.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01570: Load Plan Instance {0}, run {1} cannot be stopped by Agent {2} because User {3} does not have privileges to stop the Load Plan Instance.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01571: Load Plan Instance {0}, run {1} cannot be stopped by Agent {2} because User {3} does not have privileges to stop Sessions.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01572: Load Plan Instance {0}, run {1} cannot be stopped by Agent {2} because a SQL Exception occurred while accessing the Repository.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01573: Load Plan Instance {0}, run {1} cannot be stopped by Agent {2} because an Unknown error has occurred.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01574: Day of week is not specified for the schedule.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01575: Invalid value specified for the excluded days of month filter: {0}

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01576: LoadPlan Operation {0} on Agent {1} failed with the exception {2}.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01577: Parallel step error triggered on a parent step "{0}" while executing step "{1}".

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01578: Invalid load plan log level value specified: {0}. A valid load plan log value is between {1} and {2}.

Cause: Invalid load plan log level value was supplied in the request.

Action: Check that the load plan log level value supplied was valid (1 - 6) for the request.
Level: 1

Type: ERROR

Impact: Other

ODI-01579: Agent {0} start failure: data source for master repository did not contain a master repository using JDBC URL={1} with USER={2}.

Cause: The master repository connection information pointed to a database schema that did not contain a master repository.

Action: Verify the master repository connection information.
Level: 1

Type: ERROR

Impact: Other

ODI-01580: Unable to set the role OWB_USER for this user.

Cause: An attempt was made to set the role OWB_USER for the connected user.

Action: Check that the role exists and the connected user is an OWB user.
Level: 1

Type: ERROR

Impact: Other

ODI-01581: Unable to set the workspace {0} for this user.

Cause: An attempt was made to select the OWB workspace for the connected user.

Action: Check that the workspace exists and the connected user has got privilege to access it.
Level: 1

Type: ERROR

Impact: Other

ODI-01582: Unexpected error when connecting to Owb workspace {0}.

Cause: An unexpected error occurred when connecting to workspace.

Action: Verify that the Owb repository is up and running.
Level: 1

Type: ERROR

Impact: Other

ODI-01583: Owb workspace {0} does not contain components that enable execution from Odi.

Cause: A component that is required by ODI has not been found in this workspace.

Action: Verify that the Owb repository contains the correct patch for ODI.
Level: 1

Type: ERROR

Impact: Other

ODI-01584: Mandatory parameter {0} is missing for https protocol.

Cause: A parameter that is required to start ODI agent to enable https protocol is missing.

Action: Verify that the parameter is specified in odiparams.[sh|bat].
Level: 1

Type: ERROR

Impact: Other

ODI-01585: A Step with Id {0} does not exist in the Session {1}

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01586: A Task with Id {0} does not exist in the step {1} of the Session {2}

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01587: An execution context cannot be determined for OGG operation {0}.

Cause: An execution context cannot be determined for OGG operation.

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01588: The specified operation {0} provided is not supported by this tool.

Cause: The operation provided is not supported by this tool.

Action: Verify the parameters
Level: 1

Type: ERROR

Impact: Other

ODI-01589: The execution of the OdiOggCommand operation {0} failed.

Cause: The execution of the OdiOggCommand operation failed.

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01600: Unable to update Opmn Xml file.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-01601: Unable to parse Opmn xml file

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-01602: Please provide all arguments

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01603: Syntax: java DeleteAgentFromOpmn <Instance Home> <OracleOpmnHome> <Agent Name>

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01604: Unable to parse Opmns Snippet Xml

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01605: Component already exists in the file.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-01606: Please provide the value for {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01607: Error reading file

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-01608: No of values provided for component name and port number are not equal. Please provide the same no of values for both.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01609: No of values provided for component name and JMXport number are not equal. Please provide the same no of values for both.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01610: ODI environment variable {0} is not set and ODI Tool startcmd not launched from interactive console.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01611: Must provide username for {0} before obtaining password.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01612: Unknown parameter ignored: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01613: Unknown parameter value pair ignored: {0}={1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01614: session_number is a mandatory parameter

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01615: Usage: RestartSess <session_number> [<log_level>] ["-AGENT_URL=<agent_url>"]

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01650: -AGENT_URL=<agent_url> is a mandatory parameter

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01651: Error while executing:

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01652: Unknown parameter ignored: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01653: Unknown parameter value pair ignored: {0}={1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01654: load_plan_instance_id is a mandatory parameter

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01655: Usage: RestartLoadPlan <load_plan_instance_id> [<log_level>] "-AGENT_URL=<agent_url>" ["-SYNC=(no|yes)"] ["-POLLINT=<msec>"]

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01656: Load plan instance "{0}", run {1} has restarted

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01657: load_plan_name and context_code are mandatory parameters

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01658: Usage: StartLoadPlan <load_plan_name> <context_code> [<log_level>] "-AGENT_URL=<agent_url>" ["-SYNC=(no|yes)"] ["-POLLINT=<msec>"] ["-KEYWORDS=<keywords>"] ["<variable>=<value>"]*

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01659: Load plan "{0}", instance "{1}", run {2} has started

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01660: load_plan_instance_id is a mandatory parameter

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01661: Usage: StopLoadPlan <load_plan_instance_id> [<load_plan_run_count>] "-AGENT_URL=<agent_url>" [-STOP_LEVEL=<normal (default) | immediate>]

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01662: Load plan instance "{0}", run {1} has stopped ({2})

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01663: -STOP_LEVEL parameter value must be one of: {0}, {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01664: Waiting for completion of load plan execution.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01665: Load plan execution completed in {0} status.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01700: SessionId is not valid

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01701: The session was not found in the repository: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01702: This operation is not supported on this platform

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01800: Exception {0} has occurred as ESS-EM linking is disabled.

Cause: Unable to connect to master repository.

Action: Check if the master repository is accessible and up. This is not mandatory since master repositories can be down.
Level: 1

Type: ERROR

Impact: Configuration

ODI-01801: Agent target discovery mbean registration has failed due to {0}.

Cause: A runtime error has occurred.

Action: Check the log for details on the error and take corrective action.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01802: Agent target discovery mbean unregistration has failed due to {0}.

Cause: A runtime error has occurred.

Action: Check the log for details on the error and take corrective action.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01803: Error {0} has occurred during mbean registration.

Cause: A runtime error has occurred.

Action: Check the log for details on the error.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01804: Error {0} has occurred during mbean deregistration.

Cause: A runtime error has occurred.

Action: Check the log for details on the error.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01805: Error {0} has occurred during notification listener registration.

Cause: A runtime error has occurred.

Action: Check the log for details on the error.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01806: Error {0} has occurred during notification listener deregistration.

Cause: A runtime error has occurred.

Action: Check the log for details on the error.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01807: Error {0} has occurred during deregistration of ODI Service Mbean {1}.

Cause: A runtime error has occurred.

Action: Check the log for details on the error.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01808: Error {0} has occurred during registration of Agent Service Mbean.

Cause: A runtime error has occurred.

Action: Check the log for details on the error, fix the server and restart the OdiConsole application.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01809: Error {0} has occurred during registration of Master Repository Service Mbean.

Cause: A runtime error has occurred.

Action: Check the log for details on the error, fix the error and restart the OdiConsole application.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01810: Error {0} has occurred during registration of Work Repository Service Mbean.

Cause: A runtime error has occurred.

Action: Check the log for details on the error, fix the error and restart the OdiConsole application.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01811: Error {0} has occurred during registration of Session Service Mbean.

Cause: A runtime error has occurred.

Action: Check the log for details on the error, fix the error and restart the OdiConsole application.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01812: Error {0} has occurred during registration of Event Service Mbean.

Cause: A runtime error has occurred.

Action: Check the log for details on the error, fix the error and restart the OdiConsole application.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01813: Error {0} has occurred during registration of Session Search Service Mbean.

Cause: A runtime error has occurred.

Action: Check the log for details on the error, fix the error and restart the OdiConsole application.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01814: No repository definition found for work repository {0} in repositories.xml. Search will be disabled for this repository.

Cause: A configuration error has occurred.

Action: Add the jndi entries for all the work repositories for each of the master repositories in repositories.xml.
Level: 1

Type: ERROR

Impact: Configuration

ODI-01815: Exception {0} has occurred during Session Search by id.

Cause: A runtime error has occurred.

Action: No action is required. The session id mentioned for search is not available.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01816: Session status passed {0} is invalid.

Cause: A runtime error has occurred.

Action: Check the log for details on the error.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01817: Error {0} has occurred while fetching statistics for agents. Statistics shown might not be complete.

Cause: A runtime error has occurred.

Action: Check the log for details on the error.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01818: Agent Service Mbean is not initialized. Re-initialization of agents in tree is disabled.

Cause: A runtime error has occurred.

Action: Check the log for details on the error, fix the same and restart the OdiConsole application.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01819: Event Service Mbean is not initialized. Re-initialization of event notification listeners is disabled.

Cause: A runtime error has occurred.

Action: Check log for details on the error, fix the same and restart the OdiConsole application.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01820: Agent {0} is not up at {1} for reason {2}.

Cause: A runtime error has occurred.

Action: Check the log for details on the error.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03000: error in creating repository connection {0}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03001: error in updating repository connection {0}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03002: error in deleting repository connection {0}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03003: Failed to connect to the error table {0}. Check the connection details and retry.

Cause: The table might no longer exist or the structure of the table might not be correct.

Action: Check the connection details and retry.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03016: Creation of Work Repository failed because a previous Work repository was found, and the user had asked not to overwrite any existing repository.

Cause: Work repository already exists and overwriting of the repository was not chosen

Action: Select overwriting of Work Repository
Level: 1

Type: ERROR

Impact: Data

ODI-03017: Exception occurred while creating Work Repository at {0} failed. Failure reason {1}.

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03018: Test connection failed due to {0}.

Cause: Connection to DB failed

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Data

ODI-03019: Exception occurred while exporting Master Repository. Failure reason {0}.

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Data

ODI-03020: Only zip files can be uploaded , the {0} upload was unsuccessful.

Cause: A file with extension other than zip was uploaded.

Action: Make sure file uploaded has zip as extension
Level: 1

Type: ERROR

Impact: Data

ODI-03021: Exception occurred while importing Work Repository. Failure reason {0}.

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Data

ODI-03022: Attaching of Work Repository failed due to error: {2}

Cause: Errored out due to {2} and overwriting of the repository was not chosen

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03023: Attaching of Work Repository failed

Cause: An unexpected error occured and overwriting of the repository was not chosen

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03024: Exception occurred while attaching Work Repository at {0} failed. Failure reason {1}.

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03031: Creation of Master Repository failed at {0}.

Cause: Creation of Master Repository Failed

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Data

ODI-03032: Exception occurred while creating Master Repository at {0} failed. Failure reason {1}.

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03033: Supervisor Password and Confirm Supervisor Password fields should match.

Cause: Supervisor Password and Confirm Supervisor Password fields must match

Action: Input same passwords
Level: 1

Type: ERROR

Impact: Data

ODI-03034: Test connection failed due to {0}.

Cause: Testing of DB connection failed

Action: Check the logs
Level: 1

Type: ERROR

Impact: Data

ODI-03035: Supervisor Password and Confirm Supervisor Password fields should match and only zip files can be uploaded , the {0} upload was unsuccessful.

Cause: Both the password match and zip files to be uploaded conditions failed

Action: Make sure both the passwords are same and file uploaded is zip file
Level: 1

Type: ERROR

Impact: Data

ODI-03036: Only zip files can be uploaded , the {0} upload was unsuccessful.

Cause: zip files to be uploaded condition failed

Action: Make sure file uploaded is zip file
Level: 1

Type: ERROR

Impact: Data

ODI-03037: Exception occurred while exporting Master Repository. Failure reason {1}.

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03038: Exception occurred while exporting Physical Topology. Failure reason {1}.

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03039: Exception occurred while Importing Master Repository. Failure reason {1}.

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03040: Unable to connect to the Repository User. {0}

Cause: Testing of DB connection failed

Action: Check the logs
Level: 1

Type: ERROR

Impact: Data

ODI-03041: Unable to connect to the DBA User. {0}

Cause: Testing of DB connection failed

Action: Check the logs
Level: 1

Type: ERROR

Impact: Data

ODI-03046: unable to find the agent for given logical agent and context code

Cause: Physical Agent mapping was not defined for selected logical agent and context.

Action: A different set of credentials is required or the mapping needs to be defined.
Level: 1

Type: ERROR

Impact: Data

ODI-03047: exception while executing {0}. Failure reason {1}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03048: Only XML files can be uploaded: the {0} upload fails

Cause: File selected for import was not a XML file.

Action: Provide the XML file.
Level: 1

Type: ERROR

Impact: Data

ODI-03049: exception while importing {0}. Failure reason {1}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03050: failed to start scenario : {0} ? {1} in debug mode.

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03075: Error in purging Load Plans Executions/Sessions {0}

Cause: An exception has occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03076: exception while killing {0}. Failure reason {1}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03077: Selected Session {0} is in {1} State, and therefore cannot be killed.

Cause: The selected session was in Done, Error, or Warning state.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Data

ODI-03078: Selected Session {0} is in {1} State, and therefore cannot be restarted.

Cause: The selected session was not in Error state.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Data

ODI-03079: exception while restarting {0}. Failure reason {1}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03080: exception while clearing stalesessions. Failure reason {0}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03081: Error fetching records from error table {0}. The table might no more exist or the format of the table is not correct

Cause: The table might no longer exist or the structure of the table might not be correct

Action: Upgrade the CKM
Level: 1

Type: ERROR

Impact: DATA

ODI-03082: CKM SQL does not contain ODI_PK primary key column. Hence unable to delete the error records.

Cause: CKM SQL does not contain ODI_PK primary key column. Hence unable to delete the error records.

Action: Future release will have the ODI_PK primary key column incorporated in CKM SQL.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03083: Scenario "{0}" parent not found.

Cause: Trying to get the Odi Object which does not exist or has been deleted.

Action: Check the logs
Level: 1

Type: ERROR

Impact: Data

ODI-03090: failed to restart session : {0} in debug mode.

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03101: import of {1} from {0) failed

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03102: export of {1} to {0) failed

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03103: failed to stop a loadplan instance id : {0}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03104: failed to start a loadplan : {0}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03105: failed to start a scenario : {0} ? {1}

Cause: An unexpected error occured

Action: Check the logs1
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03106: failed to restart session : {0}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03107: failed to clean stale sessions for repository : {0}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03108: failed to stop session : {0}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03109: Creation of work runtime repository at {0} failed. Failure reason {1}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03110: Update of work runtime repository at {0} failed. Failure reason {1}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03111: failed to read config.properties

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03112: shared config dir path is not valid : {0}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03114: {0} not set

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03115: {0} is not correct

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03116: failed to read

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03117: datasource not located at {0}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03118: Could not get the service locator. JpsServiceLocator service is not configured.

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03119: JPS Exception {0} was thrown. Credential Store might not be configured.

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03120: Credential store could not be found.

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03121: Not populating any values in credential store

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03122: Exception in purging Session/Load Plan Executions

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03123: Exception occured while inserting usedInContext in Physical Schema

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03124: Exception occured while deleting usedInContext in Physical Schema

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03125: Exception occured while inserting usedInContext in Edit Physical Schema

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03126: Exception in adding an entity

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03127: Odi object not found

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03128: Exception in update

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03129: Unable to find odi object {0}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03130: Loading of entity failed

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03131: Unauthorized to delete entity of type

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03132: error occurred while executing method

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03133: no repository definition found for alias {0}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03134: login failed for user {0}=

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03135: version mismatch

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03136: unable to connect to repository with alias {0}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03137: Error occurred in EMIntegrationServlet.doOperation() - {0}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03138: failed to init jview diagrammer

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03139: repositories.xml path not set

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03140: {0} file does not exist at {1}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03141: failed to create RepositoryDefinitionRegistry

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03142: error logging out a user after session expired

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03143: Creation of work dev repository at {0} failed. Failure reason {1}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03144: Creation of Master Repository failed at {0}. Failure reason {1}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03146: ???

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03147: Delete operation failed

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03148: Maximum number of sessions should be in between 1 and 99999.

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03149: Port Number should not be non negative.

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03150: Invalid Context code. Context code cannot have lower case characters and white spaces. Though, it can contain '$' and '_' special characters.

Cause: A validation error occured

Action: Context code cannot have lower case characters and white spaces
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03184: Maximum Cache Entries cannot be less than zero.

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03185: Unused Blueprint Lifetime cannot be less than zero.

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03186: Maximum Threads Number cannot be less than Max Threads Per Session.

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03187: Max Threads Per Session cannot be less than zero.

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03188: Maximum Threads Number should be greater than zero.

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03189: Maximum Threads Number cannot be less than Maximum Session Number.

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03226: Parameter File could not be Loaded.

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Data

ODI-03260: Failed to apply settings for agent: {0}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03261: Exception while applying settings for agent: {0}. Failure reason: {1}

Cause: An unexpected error occurred

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03265: Exception occurred while creating Datasource. Failure reason {0}.

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03266: Data Source already exists for {0}.

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03267: No valid repository alias is found. Click on management link on top right corner to create one.

Cause: Either there were no repository connection aliases, or those that were created did not have a valid JNDI name

Action: Create a new repository connection alias.
Level: 1

Type: ERROR

Impact: Data

ODI-03276: Tab limit reached.Please close at least one tab.

Cause: Max limit on the number of tabs that can be open has been met.

Action: Close at least one tab
Level: 1

Type: ERROR

Impact: Data

ODI-03277: Object cannot be found.

Cause: The object might have been deleted.

Action: Refresh your view.
Level: 1

Type: ERROR

Impact: Data

ODI-03278: View operation fails with the following exception {0}. See the server log for details.

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Data

ODI-03279: Add operation failed with the following exception {0}. Please see the server log for details.

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Data

ODI-03280: Edit operation failed with the following exception {0}. Please see the server log for details.

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Data

ODI-03281: Delete operation failed with the following exception {0}. Please see the server log for details.

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Data

ODI-03290: You are not authorized to add a new entity of this type.

Cause: User doesn't have required privileges to add an new entity of a particular type

Action: No action
Level: 1

Type: ERROR

Impact: Data

ODI-03326: Please specify a valid search text

Cause: Invalid search text was specified

Action: Provide a valid search text
Level: 1

Type: ERROR

Impact: Data

ODI-03327: Please choose at least one model or project type.

Cause: No model or project type was selected

Action: Select at least one model or project type so that search criteria is valid
Level: 1

Type: ERROR

Impact: Data

ODI-03328: Please choose at least one topology type.

Cause: No topology type was selected

Action: Select at least one topology type so that search criteria is valid
Level: 1

Type: ERROR

Impact: Data

ODI-03329: Please choose at least one runtime type.

Cause: No runtime type was selected

Action: Select at least one runtime type so that search criteria is valid
Level: 1

Type: ERROR

Impact: Data

ODI-03330: Exception while importing attrbutes. Reason: {0}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03331: Exception while importing properties. Reason: {0}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03332: Exception while fetching attributes. Reason: {0}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03333: Exception while fetching properties. Reason: {0}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03334: Exception while importing propeties and expressions of attributes. Reason: {0}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03335: Exception while loading components. Reason: {0}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03336: Error in persisting user preferences {0}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03337: UserPref.xml path is not set

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03338: Failed to get User Preferences

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-10000: Method setObject class DwgObjectRepresentor does not support object class: {0}.

Cause: Java method was not found.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-10001: Action unauthorized for this license: {0}

Cause: Action was unauthorized for this license.

Action: Choose another license.
Level: 32

Type: ERROR

Impact: Security

ODI-10002: Only one local repository can be defined; {0} were found.

Cause: More than one local repository was found.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-10003: No connection set.

Cause: No connection was set.

Action: Set connection.
Level: 32

Type: ERROR

Impact: Other

ODI-10004: File already exists.

Cause: File already existed.

Action: Choose another file.
Level: 32

Type: ERROR

Impact: File

ODI-10005: Repository is expected to be a master repository.

Cause: Repository was expected to be a master repository.

Action: Choose master repository.
Level: 32

Type: ERROR

Impact: Other

ODI-10006: Repository is expected to be enterprise repository.

Cause: Repository was expected to be an enterprise repository.

Action: Choose enterprise repository.
Level: 32

Type: ERROR

Impact: Other

ODI-10007: Object must be in editable state before using set methods.

Cause: The object was not in editable state.

Action: Edit this object.
Level: 32

Type: ERROR

Impact: Other

ODI-10008: Object must be in consult mode before using methods get.

Cause: The object was not in consult mode.

Action: Consult the object.
Level: 32

Type: ERROR

Impact: Other

ODI-10009: Object does not exist in the repository.

Cause: The repository did not contains this object.

Action: Choose another object or create first this one.
Level: 32

Type: ERROR

Impact: Other

ODI-10010: This type of object cannot be updated.

Cause: Object could not be updated.

Action: Do not update this object.
Level: 32

Type: ERROR

Impact: Other

ODI-10011: Invalid object; it has been updated by another user.

Cause: Object was updated by another user.

Action: Refresh the object.
Level: 32

Type: ERROR

Impact: Other

ODI-10012: Object cannot be inserted

Cause: Object could not be inserted.

Action: Check object.
Level: 32

Type: ERROR

Impact: Other

ODI-10013: This import action has been cancelled because it could damage your repository. This is due to an {0} object that has object identifier {1} that is greater than that for the current {0} id sequence. Importing this object would lead to primary key violations in the future.

Cause: Import could damage your repository.

Action: Check identifier sequences.
Level: 32

Type: ERROR

Impact: Other

ODI-10014: Method must be redefined in derived classes. It cannot be called for DwgObject

Cause: Method must be redefined in derived classes.

Action: Call redefined method.
Level: 32

Type: ERROR

Impact: Other

ODI-10015: The work repository {0} is not declared in this master repository, the import process has been cancelled.

Cause: Work repository was not declared in this master repository.

Action: Declare work repository and try again.
Level: 32

Type: ERROR

Impact: Other

ODI-10016: Import aborted.

Cause: Import was aborted.

Action: Check objects and try again.
Level: 32

Type: ERROR

Impact: Other

ODI-10017: This import is forbidden: the text {0} has a different origin in the repository and in the import file.

Cause: The text has a different origin in the repository and in the import file.

Action: Check import file and try again.
Level: 32

Type: ERROR

Impact: Other

ODI-10018: The repository {0} is not coherent between the current repository and the import file.

Cause: The repository was not coherent between the current repository and the import file.

Action: Check import file.
Level: 32

Type: ERROR

Impact: Other

ODI-10019: Impossible to create the directory {0}.

Cause: I was not possible to create the directory.

Action: Check your system rights for creating directory; directory's path and name.
Level: 32

Type: ERROR

Impact: File

ODI-10020: Impossible to replace the file

Cause: It was not possible to replace the file.

Action: Check, if you have enough rights for this operation.
Level: 32

Type: ERROR

Impact: File

ODI-10021: Unspecified save directory.

Cause: Directory to save environment information was unspecified.

Action: Specify the directory for saving the environment information file.
Level: 32

Type: ERROR

Impact: Other

ODI-10022: You must specify all options.

Cause: Missed one or more options.

Action: Specify missed options.
Level: 32

Type: ERROR

Impact: Other

ODI-10023: Invalid license. This license is suitable for {0}.

Cause: Invalid license.

Action: Check license.
Level: 32

Type: ERROR

Impact: Security

ODI-10024: Your installation of Oracle Data Integrator is corrupted.

Cause: The technology description file contains errors.

Action: Reinstall Oracle Data Integrator.
Level: 32

Type: ERROR

Impact: Other

ODI-10025: Your installation of Oracle Data Integrator is corrupted.

Cause: The technology description file is missing.

Action: Reinstall Oracle Data Integrator.
Level: 32

Type: ERROR

Impact: Other

ODI-10026: Error while testing the Master Repository technology.

Cause: Error occurred while testing the Master Repository technology.

Action: Check parameters.
Level: 32

Type: ERROR

Impact: Other

ODI-10027: The import is canceled because at least one object is locked by another user.

Cause: At least one object was locked by another user.

Action: Check objects' locks.
Level: 32

Type: ERROR

Impact: Other

ODI-10028: It is forbidden to import a log into a repository having the same ID.

Cause: The log had the same ID as repository.

Action: Check log and/or repository id.
Level: 32

Type: ERROR

Impact: Other

ODI-10029: Version {0} for object {1} already exists.

Cause: Version already existed.

Action: Choose another version.
Level: 32

Type: ERROR

Impact: Other

ODI-10030: DwgBeanWrapper can only wrap DwgObjects

Cause: DwgBeanWrapper can only wrap DwgObjects

Action: Choose correct type of objects.
Level: 32

Type: ERROR

Impact: Other

ODI-10031: Object {0}: {1} is locked by user {2}

Cause: Object was locked by another user.

Action: Wait until object is unlocked.
Level: 32

Type: ERROR

Impact: Other

ODI-10032: You cannot import this object ({0}). A referenced object ({1}) does not exist in the repository.

Cause: A referenced object does not exist in the repository.

Action: Check import file.
Level: 32

Type: ERROR

Impact: Other

ODI-10033: You cannot delete this object because it is locked by another user ({0}).

Cause: This object was locked by another user.

Action: Wait until object is unlocked.
Level: 32

Type: ERROR

Impact: Other

ODI-10034: The technology hosting your master repository does not support Versioning.

Cause: The technology did not support versioning.

Action: Choose another repository or technology.
Level: 32

Type: ERROR

Impact: Other

ODI-10035: {0} : ''{1}'' violates alternate key constraint {2} {3} for values {4}

Cause: Object violated alternate key constraint.

Action: Check object properties and constraint's values.
Level: 32

Type: ERROR

Impact: Other

ODI-10036: Importing object {0} : {1} failed.

Cause: Import failed.

Action: Check import file and try again.
Level: 32

Type: ERROR

Impact: Other

ODI-10037: Import-replace for this node is supported for action groups only. The import file is invalid.

Cause: Import-replace for this node was supported for action groups only.

Action: Check import file.
Level: 32

Type: ERROR

Impact: Other

ODI-10038: The interface you are trying to use ({0}) is related to a logical schema ({1}) that no longer exists.

Cause: Logical schema was not found.

Action: Check interface.
Level: 32

Type: ERROR

Impact: Other

ODI-10039: Bad ID for an object representer

Cause: Bad ID for an object representer

Action: Check object`s ID.
Level: 32

Type: ERROR

Impact: Other

ODI-10040: Cannot create directory

Cause: Directory could not be created.

Action: Check directory path/name.
Level: 32

Type: ERROR

Impact: File

ODI-10041: Oracle Data Integrator Remote Object (SnpRemoteObject) must inherit from SnpsFunction.

Cause: Oracle Data Integrator Remote Object (SnpRemoteObject) did not inherit from SnpsFunction.

Action: Use SnpsFunction as parent.
Level: 32

Type: ERROR

Impact: Other

ODI-10042: SnpsQuery must be connected prior to execution

Cause: SnpsQuery was not connected.

Action: Set a connection.
Level: 32

Type: ERROR

Impact: Other

ODI-10043: Security token is a mandatory parameter

Cause: Security token was not specified.

Action: Check security parameters.
Level: 32

Type: ERROR

Impact: Security

ODI-10044: Unable to save the interface. Maximum number of source datastores exceeded.

Cause: Maximum number of source datastores was exceeded.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-10045: a2.getCargo() not instance of SAPSegment

Cause: a2.getCargo() not instance of SAPSegment

Action: Check SAP Tree.
Level: 32

Type: ERROR

Impact: Other

ODI-10046: No IDoc.

Cause: Missed IDoc.

Action: Check IDoc.
Level: 32

Type: ERROR

Impact: Other

ODI-10047: Repository is not a development work repository

Cause: Repository was not a development work repository.

Action: Choose development work repository.
Level: 32

Type: ERROR

Impact: Other

ODI-10048: No work repository found.

Cause: No work repository was found.

Action: Check your connection settings or database.
Level: 32

Type: ERROR

Impact: Other

ODI-10049: Missing parameter

Cause: Parameter was missing.

Action: Check all parameters.
Level: 32

Type: ERROR

Impact: Other

ODI-10050: Missing parameter at: {0} SQL: {1}

Cause: Parameter was missing.

Action: Check all parameters.
Level: 32

Type: ERROR

Impact: Other

ODI-10051: Some objects cannot be exported because they do not exist in the repository: {0} {1}

Cause: Objects did not exist in the repository.

Action: Check objects state.
Level: 32

Type: ERROR

Impact: Other

ODI-10052: A problem occurred in your repository.

Cause: A problem occurred in your repository.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-10053: Problem retrieving JCOFunction object. {0}

Cause: Problem occurred retrieving JCOFunction object.

Action: Check JCO Function object.
Level: 32

Type: ERROR

Impact: Other

ODI-10054: Unable to find the XML file corresponding to your technology.

Cause: XML file corresponding to your technology was not found.

Action: Check technology and/or XML file for the technology.
Level: 32

Type: ERROR

Impact: Other

ODI-10055: This ID is already in use in the repository

Cause: This ID was already in use in the repository.

Action: Change ID.
Level: 32

Type: ERROR

Impact: Other

ODI-10056: This repository ID already exists. This repository cannot be created.

Cause: Repository ID already existed.

Action: Change repository ID.
Level: 32

Type: ERROR

Impact: Other

ODI-10057: Unrecognized export type.

Cause: Export type was unrecognized.

Action: Check export type.
Level: 32

Type: ERROR

Impact: Other

ODI-10058: You are trying to import objects from a master repository of an older version into {0} version. This action is forbidden. Master repositories must be upgraded using the upgrade assistant, not using the export/import facility.

Cause: You tried to import objects from a master repository of an older version.

Action: Master repositories must be upgraded using the upgrade assistant, not using the export/import facility.
Level: 32

Type: ERROR

Impact: Other

ODI-10059: Repository is null

Cause: Repository was null.

Action: Check repository.
Level: 32

Type: ERROR

Impact: Other

ODI-10060: Saputil is mandatory.

Cause: Saputil was mandatory.

Action: Check Saputil
Level: 32

Type: ERROR

Impact: Other

ODI-10061: Empty XML Character Set

Cause: XML Character Set was empty.

Action: Fill XML Character Set.
Level: 32

Type: ERROR

Impact: Other

ODI-10062: Unable to find license key {0}. An exception {1} occurred with message: {2}

Cause: An exception occurred.

Action: Check license key.
Level: 32

Type: ERROR

Impact: Other

ODI-10063: Unable to check the license key. An exception {0} occurred with message: {1}

Cause: An exception occurred.

Action: Check license key.
Level: 32

Type: ERROR

Impact: Other

ODI-10064: The interface must have a JMS datastore as a source or target. Another license is required otherwise.

Cause: The interface must have a JMS datastore as a source or target.

Action: Check datastore type and/or license.
Level: 32

Type: ERROR

Impact: Other

ODI-10065: You license does not include these features. Please contact your reseller.

Cause: You license does not include these features.

Action: Please contact your reseller.
Level: 32

Type: ERROR

Impact: Other

ODI-10066: The interface is using a Datastore defined in Model "{0}" which is linked to a logical schema "{1}" that no longer exists.

Cause: Logical schema was not found.

Action: Correct interface.
Level: 32

Type: ERROR

Impact: Other

ODI-10067: Target file already exists.

Cause: Target file already existed.

Action: Choose another target file name.
Level: 32

Type: ERROR

Impact: File

ODI-10068: SnpsConnection: Isolation level not supported

Cause: Isolation level not supported.

Action: Check isolation level.
Level: 32

Type: ERROR

Impact: Other

ODI-10069: Unsupported XML Character Set: {0}

Cause: Unsupported XML Character Set.

Action: Check XML charset.
Level: 32

Type: ERROR

Impact: Other

ODI-10070: Cannot delete this object. It is being edited or viewed

Cause: Object was being edited or viewed.

Action: Stop edit or view object and try again.
Level: 32

Type: ERROR

Impact: Other

ODI-10071: Cannot delete this object

Cause: Could not delete this object.

Action: Check object state.
Level: 32

Type: ERROR

Impact: Other

ODI-10073: A repository already exists on this data server

Cause: A repository already existed on this data server.

Action: Choose another data server.
Level: 32

Type: ERROR

Impact: Other

ODI-10074: An object with the wrong type was given to an object representative

Cause: An object with the wrong type was given to an object representative

Action: Check object type.
Level: 32

Type: ERROR

Impact: Other

ODI-10075: An object is in an unidentified state {0}

Cause: An object is in an unidentified state.

Action: Check object state.
Level: 32

Type: ERROR

Impact: Other

ODI-10076: A collection object is the wrong class

Cause: A collection object is the wrong class.

Action: Check collection object's class
Level: 32

Type: ERROR

Impact: Other

ODI-10077: Undefined action performed on an object: {0}

Cause: An undefined action was performed on an object.

Action: Check action and object.
Level: 32

Type: ERROR

Impact: Other

ODI-10078: An object will be in an unidentified state (it is in the state "{0}" and "{1}" is currently being performed on it)

Cause: An object would have been in an unidentified state.

Action: Check object state.
Level: 32

Type: ERROR

Impact: Other

ODI-10080: Incorrect License ....

Cause: Incorrect License.

Action: Contact your seller.
Level: 32

Type: ERROR

Impact: Other

ODI-10081: You are not authorized to Insert the Object: {0}: {1} / {2}

Cause: You were not authorized to Insert the Object.

Action: Login with user with right privileges.
Level: 32

Type: ERROR

Impact: Security

ODI-10082: You are not authorized to View the Object: {0}: {1}

Cause: You were not authorized to View the Object.

Action: Login with user with right privileges.
Level: 32

Type: ERROR

Impact: Security

ODI-10083: You are not authorized to Delete the Object: {0}: {1} / {2}

Cause: You were not authorized to Delete the Object.

Action: Login with user with right privileges.
Level: 32

Type: ERROR

Impact: Security

ODI-10084: You are not authorized to Edit the Object: {0}: {1} / {2}

Cause: You were not authorized to Edit the Object.

Action: Login with user with right privileges.
Level: 32

Type: ERROR

Impact: Security

ODI-10085: You cannot consult this object

Cause: You could not consult this object.

Action: Login with user with right privileges.
Level: 32

Type: ERROR

Impact: Security

ODI-10086: You cannot edit this object

Cause: You could not edit this object.

Action: Login with user with right privileges.
Level: 32

Type: ERROR

Impact: Security

ODI-10087: You can only give Supervisor Access Privileges if you are a Supervisor.

Cause: You could only give Supervisor Access Privileges if you are a Supervisor.

Action: Login with user with right privileges.
Level: 32

Type: ERROR

Impact: Security

ODI-10088: Empty Java Character Set.

Cause: Java Character Set was empty.

Action: Fill Java charset.
Level: 32

Type: ERROR

Impact: Other

ODI-10089: You cannot modify another user''s password

Cause: You cannot modify another user''s password

Action: Login with user with right privileges.
Level: 32

Type: ERROR

Impact: Security

ODI-10090: Object {0} {1} is referenced by: {2}. Cannot remove.

Cause: Object was referenced by another one.

Action: Check object''s references.
Level: 32

Type: ERROR

Impact: Other

ODI-10091: not connected

Cause: not connected

Action: Check connection.
Level: 32

Type: ERROR

Impact: Other

ODI-10092: Some objects cannot be exported. They do not exist in the repository.

Cause: Objects did not exist in the repository.

Action: Check objects'' state.
Level: 32

Type: ERROR

Impact: Other

ODI-10093: You are importing an object from another repository with the same identifier. It is forbidden.

Cause: You tried to import an object from another repository with the same identifier.

Action: Change repository ID.
Level: 32

Type: ERROR

Impact: Other

ODI-10094: Problem while computing new name.

Cause: A problem occurred while computing new name.

Action: Try again.
Level: 32

Type: ERROR

Impact: Other

ODI-10095: Exception while getting the children list

Cause: Exception while getting the children list.

Action: Try again.
Level: 32

Type: ERROR

Impact: Other

ODI-10096: Error while parsing fields

Cause: Error occurred while parsing fields.

Action: Check fields value.
Level: 32

Type: ERROR

Impact: Other

ODI-10097: Impossible to find text with ID {0} in text list.

Cause: Text was not found.

Action: Check text ID
Level: 32

Type: ERROR

Impact: Other

ODI-10098: No connection available. Check connection parameters.

Cause: No connection was available.

Action: Check connection parameters.
Level: 32

Type: ERROR

Impact: Network

ODI-10099: Object cannot be exported because the file with name {0} could not be created.

Cause: Object could not be exported because the file could not be created.

Action: Check your system rights to write files and file name.
Level: 32

Type: ERROR

Impact: Other

ODI-10100: Empty XML Version

Cause: XML version was empty.

Action: Fill XML Version.
Level: 32

Type: ERROR

Impact: Other

ODI-10101: Invalid XML Version: {0}

Cause: XML Version was invalid.

Action: Check XML version.
Level: 32

Type: ERROR

Impact: Other

ODI-10102: Alias with the name {0} already exists.

Cause: Alias already exists.

Action: Change alias.
Level: 32

Type: ERROR

Impact: Other

ODI-10103: Alias with the name {0} does not exist.

Cause: Alias doesn't exit.

Action: Check alias name ant try again.
Level: 32

Type: Error

Impact: Other

ODI-10104: File {0} is not a Smart Export file and cannot be imported by Smart Import.

Cause: Smart Export file not specified for Smart Import.

Action: Specify a Smart Export file for importing via Smart Import.
Level: 32

Type: ERROR

Impact: Other

ODI-10105: Smart Import file name cannot be null.

Cause: Smart Export file name not specified for Smart Import.

Action: Specify a Smart Export file for importing via Smart Import.
Level: 32

Type: ERROR

Impact: Other

ODI-10106: Smart Import response file name cannot be null.

Cause: Smart import response file name not specified for Smart Import.

Action: Specify a Smart Import response file.
Level: 32

Type: ERROR

Impact: Other

ODI-10107: Smart Import file {0} not found.

Cause: File does not exist.

Action: Specify an existing Smart Export file for importing via Smart Import.
Level: 32

Type: ERROR

Impact: Other

ODI-10108: Smart Import response file {0} not found.

Cause: Response file does not exist.

Action: Specify an existing Smart Import response file.
Level: 32

Type: ERROR

Impact: Other

ODI-10109: File {0} is not a valid Smart Import Response file.

Cause: File is not a valid Smart Import response.

Action: Specify an existing Smart Import response file.
Level: 32

Type: ERROR

Impact: Other

ODI-10110: {0} with the same {1} exists.

Cause: An object with the same alternative key value(s) exists.

Action: Change the alternative key value to be unique.
Level: 32

Type: ERROR

Impact: Other

ODI-10111: {0} <{1}> referenced by {2} <{3}> is missing.

Cause: A referenced object does not exist.

Action: Either import the missing object or change to reference a different object.
Level: 32

Type: WARNING

Impact: Other

ODI-10112: Project code will be changed from <{0}> to <{1}>.

Cause: The import will make a change to an existing project code.

Action: Determine whether the change to project code is desired or not.
Level: 32

Type: WARNING

Impact: Other

ODI-10113: {0} with {1} <{2}> does not exist.

Cause: A referenced object does not exist.

Action: Either import the missing object or change to reference a different object.
Level: 32

Type: WARNING

Impact: Other

ODI-10114: {0} with {1} id <{2}> does not exist.

Cause: A referenced object does not exist.

Action: Either import the missing object or change to reference a different object.
Level: 32

Type: WARNING

Impact: Other

ODI-10115: {0} with the same name <{1}> already exists.

Cause: A different object with the same name already exists.

Action: Either change the name of the object being imported or use match by name to match to the already existing object with the same name.
Level: 32

Type: WARNING

Impact: Other

ODI-10116: Model code will be changed from <{0}> to <{1}>.

Cause: The import will make a change to an existing model code.

Action: Determine whether the change to model code is desired or not.
Level: 32

Type: WARNING

Impact: Other

ODI-10117: Sub-model code will be changed from <{0}> to <{1}>.

Cause: The import will make a change to an existing sub-model code.

Action: Determine whether the change to sub-model code is desired or not.
Level: 32

Type: WARNING

Impact: Other

ODI-10118: A different Physical Schema is already set as the default physical schema for the same data server.

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-10119: A different Context is already set as the default Context.

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-10120: Context code will be changed from <{0}> to <{1}>.

Cause: The import will make a change to an existing context code.

Action: Determine whether the change to context code is desired or not.
Level: 32

Type: WARNING

Impact: Other

ODI-10121: Logical schema name will be changed from <{0}> to <{1}>.

Cause: The import will make a change to an existing logical schema name.

Action: Determine whether the change to logical schema name is desired or not.
Level: 32

Type: WARNING

Impact: Other

ODI-10122: Logical agent name will be changed from <{0}> to <{1}>.

Cause: The import will make a change to an existing logical agent name.

Action: Determine whether the change to logical agent name is desired or not.
Level: 32

Type: WARNING

Impact: Other

ODI-10123: {0} with {1} <{2}> and {3} <{4}> does not exist.

Cause: A referenced object does not exist.

Action: Either import the missing object or change to reference a different object.
Level: 32

Type: WARNING

Impact: Other

ODI-10124: Smart import of file {0} cannot be run due to unfixed critical issues.

Cause: Critical issues exist for objects in the Smart Import.

Action: A fix must be provided for all critical issues before the Smart Import can be run.
Level: 32

Type: ERROR

Impact: Other

ODI-10125: Smart Export file name cannot be null.

Cause: Smart Export file name not specified for Smart Export.

Action: Specify a Smart Export file via Smart Export.
Level: 32

Type: ERROR

Impact: Other

ODI-10126: File {0} already exists.

Cause: The file already exists.

Action: Specify another file name.
Level: 32

Type: ERROR

Impact: Other

ODI-10127: Column position {0} is being used by another object <{1}>.

Cause: The position value is already in use.

Action: Specify a unique position value.
Level: 32

Type: ERROR

Impact: Other

ODI-10128: Multiple primary keys found. Only one primary key can be defined per datastore.

Cause: Multiple primary keys defined.

Action: Delete or match primary keys so that only one is defined.
Level: 32

Type: ERROR

Impact: Other

ODI-10129: Object with id {0} and type {1} is not a smart exportable object.

Cause: Smart Export does not support the type of object specified.

Action: Do not export this object.
Level: 32

Type: ERROR

Impact: Other

ODI-10130: Smart Import Response file {0} is not valid for Smart Export file {1}.

Cause: Smart Import Response file was not generated for the Smart Export file being imported.

Action: Specify a Smart Import response file that belongs to the Smart Export file being imported.
Level: 32

Type: ERROR

Impact: Other

ODI-10131: Entity of type {0} cannot be merged.

Cause: Wrong entity type.

Action: Check entity type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10132: Entity of type {0} cannot be removed.

Cause: Wrong entity type.

Action: Check entity type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10133: Cannot create a transaction against the extended persistent context [{0}].

Cause: Another persistence context is already bound to the current thread.

Action: Unbound persistence context from current thread.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10134: You don't have READ permission on at least one object from the collection/list.

Cause: Insufficient level of permissions.

Action: Check your permissions
Level: 32

Type: ERROR

Impact: Security

ODI-10135: Max value ({1}) reached for sequence {0} and reset is not allowed.

Cause: Reset is not allowed.

Action: Check configuration of sequence behaviour.
Level: 32

Type: ERROR

Impact: Other

ODI-10136: Illegal transaction state: transaction synchronization is active but entity manager is not synchronized within the transaction.

Cause: Entity manager is not synchronized within the transaction.

Action: Synchronize entity manager and try again.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10137: Your program needs to set authentication first.

Cause: There is no authentication set.

Action: Set authentication via odiInstance.getSecurityManager().setGlobalAuthentication(.) or odiInstance.getSecurityManager().setCurrentThreadAuthentication(.), see the SecurityManager API for more detail.
Level: 32

Type: ERROR

Impact: Security

ODI-10138: Unable to create DwgConnectConnection to {0} repository.

Cause: Exception during connection.

Action: Check repository configuration.
Level: 32

Type: ERROR

Impact: Other

ODI-10139: {0} must not be null or empty.

Cause: Parameter is null or empty.

Action: Check parameter name.
Level: 32

Type: ERROR

Impact: Configuration

ODI-10140: {0} must be greater or equal 0.

Cause: Parameter is negative.

Action: Check parameter value.
Level: 32

Type: ERROR

Impact: Configuration

ODI-10141: Unable to create datasource provider from class [{0}].

Cause: Exception during creation.

Action: Check configuration.
Level: 32

Type: ERROR

Impact: Configuration

ODI-10142: Active transaction is required to use the method {0} on the TransactionalOdiEntityManager.

Cause: Transaction isn't active.

Action: Check transaction state.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10143: Error while accessing the {0} repository.

Cause: Network problems.

Action: Check the network connection and the database status.
Level: 32

Type: ERROR

Impact: Network

ODI-10144: OdiInstance is closed.

Cause: OdiInstance is closed.

Action: Check OdiInstance status.
Level: 32

Type: ERROR

Impact: Other

ODI-10145: Limited persistence support.

Cause: Limited persistence support.

Action: Check OdiInstance configuration.
Level: 32

Type: ERROR

Impact: Other

ODI-10146: Cannot create JDBC DataSource for this type of DataServer.

Cause: Invalid connection provider.

Action: Check connection provider.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10147: Repository type mismatches.

Cause: Wrong repository type.

Action: Check repository type.
Level: 32

Type: ERROR

Impact: Configuration

ODI-10148: Repository is in error install/upgrade state and needs to be repaired. Connection has been disabled.

Cause: Repository install/upgrade did not complete successfully.

Action: Check install/upgrade log files and/or ODI user documentation for information on reparation process.
Level: 32

Type: ERROR

Impact: Configuration

ODI-10149: Local Repository table is empty.

Cause: Local Repository table is empty.

Action: Check repository configuration.
Level: 32

Type: ERROR

Impact: Configuration

ODI-10150: Work repository with ID {0} is not bound to master: Definition in master ID:{0}, Name:{1}, Timestamp:{2} Definition in work ID:{3}, Name:{4}, Timestamp:{5}.

Cause: Work repository with ID is not bound to master repository.

Action: Check work and master repositories configuration.
Level: 32

Type: ERROR

Impact: Configuration

ODI-10151: Unable to get ID for entity {0}.

Cause: Wrong entity ID.

Action: Check entity properties.
Level: 32

Type: ERROR

Impact: Security

ODI-10152: I_OBJECTS for entity class {0} is not found.

Cause: Entity type is not mapped to I_OBJECTS.

Action: Check entity class.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10153: {0} is denied.

Cause: Insufficient level of permissions.

Action: Check permissions.
Level: 32

Type: ERROR

Impact: Security

ODI-10154: {0} is denied for {1}.

Cause: Insufficient level of permissions.

Action: Check permissions.
Level: 32

Type: ERROR

Impact: Security

ODI-10155: You don't have {0} permission on at least one object from the collection/list.

Cause: Insufficient level of permissions.

Action: Check permissions.
Level: 32

Type: ERROR

Impact: Security

ODI-10156: Impossible to connect to JPS MBean Server.

Cause: Exception during connection.

Action: Check configuration.
Level: 32

Type: ERROR

Impact: Configuration

ODI-10157: {0}: must call preWebLogic() before postWebLogic().

Cause: Wrong API usage.

Action: Call preWebLogic() before postWebLogic().
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10158: The credential with map name {0} and key {1} already exists.

Cause: Wrong credential.

Action: Check credential configuration.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10159: The user {0} hasn't required CONNECT profile.

Cause: The user hasn't required profile.

Action: Grant the user CONNECT profile first.
Level: 32

Type: ERROR

Impact: Security

ODI-10160: Unable to load user.

Cause: Exception during user loading.

Action: Check repository connection.
Level: 32

Type: ERROR

Impact: Other

ODI-10162: This OPSS user ''{0}'' is not registered to Oracle Data Integrator.

Cause: The user is not registered to ODI.

Action: Check user name.
Level: 32

Type: ERROR

Impact: Configuration

ODI-10163: This OPSS user ''{0}'' has different GUID than the one found in Oracle Data Integrator repository.

Cause: OPSS user differs from ODI user in GUID.

Action: Check user GUID.
Level: 32

Type: ERROR

Impact: Security

ODI-10164: Only supervisor user can invoke this API.

Cause: Insufficient level of permissions.

Action: Check user role.
Level: 32

Type: ERROR

Impact: Security

ODI-10165: The RunAsUser {0} is not a valid user from external user identity store.

Cause: User isn't valid.

Action: Check user.
Level: 32

Type: ERROR

Impact: Security

ODI-10166: The RunAsUser: {0} has different GUID in ODI repository and external user identity store.

Cause: User from external user identity store differs from ODI user in GUID.

Action: Check user.
Level: 32

Type: ERROR

Impact: Security

ODI-10167: Authentication is missing.

Cause: Authentication is missing.

Action: Check authentication configuration.
Level: 32

Type: ERROR

Impact: Security

ODI-10168: There is already an Authentication bound to this thread.

Cause: There is already an Authentication bound to this thread.

Action: Check authentication configuration.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10169: Trying to set authentication object which is not created by this security manager.

Cause: Authentication object isn't created by this security manager.

Action: Check authentication configuration.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10170: There is currently no Authentication bound to this thread.

Cause: There is currently no Authentication bound to this thread.

Action: Check authentication configuration.
Level: 32

Type: ERROR

Impact: Security

ODI-10171: There is already an Authentication bound as global Authentication.

Cause: There is already an Authentication bound as global Authentication.

Action: Check authentication configuration.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10172: There is currently no global Authentication bound to this SecurityManager.

Cause: There is currently no global Authentication bound to this SecurityManager.

Action: Check authentication configuration.
Level: 32

Type: ERROR

Impact: Security

ODI-10173: You are not authorized to change the password for external user ''{0}''.

Cause: Insufficient level of permissions.

Action: Check permissions.
Level: 32

Type: ERROR

Impact: Security

ODI-10174: You are not authorized to change the password for user ''{0}''.

Cause: Insufficient level of permissions.

Action: Check permissions.
Level: 32

Type: ERROR

Impact: Security

ODI-10175: You are not authorized to change the password for external user.

Cause: Insufficient level of permissions.

Action: Check permissions.
Level: 32

Type: ERROR

Impact: Security

ODI-10176: Authentication is needed to change password.

Cause: Authentication is missed.

Action: Authenticate first.
Level: 32

Type: ERROR

Impact: Security

ODI-10177: ODI was not able to load the jdbc driver class "{0}" provided on {1}.

Cause: Wrong jdbc driver class.

Action: Check that the driver class name is correct and that this driver is available to ODI classloader.
Level: 32

Type: ERROR

Impact: Other

ODI-10178: The jdbc URL "{1}" was not accepted by the jdbc driver class "{0}" provided on {2}.

Cause: Insufficient jdbc URL.

Action: Check that the jdbc URL and the driver class name are matching.
Level: 32

Type: ERROR

Impact: Other

ODI-10179: Client requires a repository with version {0} but the repository version found is {1}.

Cause: Insufficient repository version.

Action: Check repository configuration.
Level: 32

Type: ERROR

Impact: Other

ODI-10180: ODI was not able to load the jdbc driver class {0} specified in ODI topology for work repository {1}.

Cause: Wrong jdbc driver class.

Action: Check that the driver class name is correct and that this driver is available to ODI classloader. If the driver class name is incorrect please connect to ODI topology to fix it.
Level: 32

Type: ERROR

Impact: Other

ODI-10181: Uncategorized configuration exception.

Cause: An unexpected error occurred.

Action: Check exception cause for details.
Level: 32

Type: ERROR

Impact: Configuration

ODI-10182: Uncategorized exception during repository access.

Cause: An unexpected error occurred.

Action: Check exception cause for details.
Level: 32

Type: ERROR

Impact: Other

ODI-10183: {0} is an invalid finder class.

Cause: Wrong finder class.

Action: Check finder class.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10184: Could not get ESS {0}.

Cause: Exception during session retrieving.

Action: Check configuration and try again.
Level: 32

Type: ERROR

Impact: Session

ODI-10185: Operation is not granted.

Cause: Current level of permission is not sufficient.

Action: Check your permissions.
Level: 32

Type: ERROR

Impact: Security

ODI-10186: User {0} is inactive.

Cause: There is no GUID defined for this User in ODI repository

Action: Check user GUID.
Level: 32

Type: ERROR

Impact: Security

ODI-10187: The authentication API is used in wrong way.

Cause: The authentication API is used in wrong way.

Action: Check usage of API.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10188: Error while login from OPSS.

Cause: Exception was thrown during login process.

Action: Make sure OPSS is configured correctly for this installation.
Level: 32

Type: ERROR

Impact: Other

ODI-10189: Password policy {0} is not matched.

Cause: Week password.

Action: Check password policy and correct password.
Level: 32

Type: ERROR

Impact: Security

ODI-10190: The user {0} has its account expired.

Cause: Account expired

Action: Request supervisor for account unlocking.
Level: 32

Type: ERROR

Impact: Security

ODI-10191: Unable to create datasource provider.

Cause: Exception during creation.

Action: Check configuration.
Level: 32

Type: ERROR

Impact: Configuration

ODI-10192: Unable to retrieve user GUID.

Cause: Exception during GUID retrieving.

Action: Check repository connection.
Level: 32

Type: ERROR

Impact: Other

ODI-10193: Unexpected null value in port.

Cause: JPS port value is null.

Action: Check JPS configuration.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10194: Uncategorized security exception.

Cause: An unexpected error occurred.

Action: Check exception cause for details.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10195: CsfAccessor is only available for CsfPasswordStorageConfiguration

Cause: Password storage configuration is internal.

Action: Check storage configuration.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10196: Error while accessing the repository.

Cause: Network problems.

Action: Check the network connection and the database status.
Level: 32

Type: ERROR

Impact: Network

ODI-10197: Instance is not connected to a work repository

Cause: Work datasource is null.

Action: Check work datasource.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10198: Context with code '{0}' wasn''t found.

Cause: Context wasn't found.

Action: Check context code.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10199: Incorrect ODI username or password.

Cause: Incorrect ODI username or password.

Action: Check username and password.
Level: 32

Type: ERROR

Impact: Security

ODI-10200: Work repository {0} wasn''t found.

Cause: Wrong repository name or repository isn't defined.

Action: Check repository name.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10201: The user {0} has its password expired.

Cause: Account expired

Action: Request supervisor for changing password.
Level: 32

Type: ERROR

Impact: Security

ODI-10202: Supervisor privilege is required to setup repository.

Cause: Insufficient level of permissions.

Action: User supervisor account for this operation.
Level: 32

Type: ERROR

Impact: Security

ODI-10203: Transaction state is illegal.

Cause: Transaction state is illegal.

Action: Check transaction state.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10204: Inappropriate usage of a ODI transaction API.

Cause: Inappropriate usage of a ODI transaction API.

Action: Check ODI transaction API.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10205: Unexpected rollback.

Cause: Attempt to commit a transaction resulted in an unexpected rollback.

Action: Check transaction.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10206: Transaction can't be created.

Cause: Exception was thrown during transaction creation.

Action: Check transaction.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10207: Uncategorized exception during transaction system usage.

Cause: An unexpected error occurred.

Action: Check exception cause for details.
Level: 32

Type: ERROR

Impact: Other

ODI-10208: Error when changing password for user {0}.

Cause: An unexpected error occurred.

Action: Check exception cause for details.
Level: 32

Type: ERROR

Impact: Other

ODI-10209: Cannot access a closed IOdiEntityManager.

Cause: IOdiEntityManager has been closed.

Action: Check IOdiEntityManager state.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10210: File {0} does not contain any objects to be imported by Smart Import.

Cause: Smart Export file specified for Smart Import is empty.

Action: Specify a Smart Export file with objects for importing via Smart Import.
Level: 32

Type: ERROR

Impact: Other

ODI-10211: Unsupported Java Character Set: {0}

Cause: Unsupported Java Character Set.

Action: Check Java charset.
Level: 32

Type: ERROR

Impact: Other

ODI-10212: Parent object {0}: ''{1}'' already has child {2}: ''{3}''. Technical details: {2} : ''{3}'' violates alternate key constraint {4} {5} for values {6}

Cause: Object violated alternate key constraint.

Action: Check object properties and constraint's values.
Level: 32

Type: ERROR

Impact: Other

ODI-10213: Fixed format file field {0} (starts at {1} ends at {2}) has a file position that overlaps with the file position of field {3} (starts at {4} ends at {5}).

Cause: Two fields from a fixed format file have overlapping file positions.

Action: Modify the file positions or remove a field if the overlapping file positions are not correct.
Level: 32

Type: ERROR

Impact: Other

ODI-10214: Fixed format file fields {0} (starts at {1} ends at {2}) and {3} (starts at {4} ends at {5}) have unused file positions between them.

Cause: Two fields from a fixed format file have unused file positions between them.

Action: Modify the file positions if having unused file positions is not correct.
Level: 32

Type: ERROR

Impact: Other

ODI-10215: It is forbidden to import a log into a repository using any other import mode except "Synonym Mode Insert".

Cause: Import mode is not "Synonym Mode Insert".

Action: Correct import mode.
Level: 32

Type: Error

Impact: Other

ODI-10216: Upgrade key cannot be null when importing objects from before ODI 12C.

Cause: Upgrade key is not set for import that must upgrade objects to have global ids.

Action: Specify the upgrade key to be used.
Level: 32

Type: Error

Impact: Other

ODI-10217: Permission check failed for instance object {0}.

Cause: Permission check failed for instance object.

Action: Need to grant initial permission for creator on object.
Level: 32

Type: NOTIFICATION

Impact: Other

ODI-10218: Invalid WAS_HOME ("{0}") set or WebSphere library jar ({1}) not found under WAS_HOME/plugins.

Cause: Wrong WAS_HOME set (or) WebSphere libraries (com.ibm.ws.admin.core.jar, com.ibm.ws.admin.services.jar, com.ibm.ws.runtime.jar) are moved

Action: Check that the environment-variable WAS_HOME is set properly to point to WebSphere Application Server root. Also, ensure the libraries exist under WAS_HOME/plugins.
Level: 32

Type: ERROR

Impact: Other

ODI-10219: ODI Library for WebSphere access ({0}) not found.

Cause: Library could be moved / deleted

Action: Check that the specified library present
Level: 32

Type: ERROR

Impact: Other

ODI-10220: ODI was unable to find the technology "{0}".

Cause: Missing technology.

Action: Check that this technology is defined in the repository. .
Level: 32

Type: ERROR

Impact: Other

ODI-10221: It's taken {0} second to synchronize Snp_Ent_Principal table content.

Cause:

Action:
Level: INFO

Type: NOTIFICATION

Impact: Other

ODI-10222: The compatible Mapping/ReusableMapping {0} can only be modified by 11g SDK.

Cause: An attempt was made to modify compatible Mapping using 12c SDK.

Action: Modify compatible Mapping using 11g Interface SDK.
Level: 32

Type: ERROR

Impact: Other

ODI-10223: A non-legacy compatible import source cannot be imported into a legacy compatible repository.

Cause: An attempt was made to import a non-legacy compatible import source into a legacy compatible repository.

Action: Import a legacy compatible import source or make repository not legacy compatible.
Level: 32

Type: Error

Impact: Other

ODI-10224: You are not authorized to create new user.

Cause: Only SUPERVISOR could create users.

Action: Check permissions.
Level: 32

Type: ERROR

Impact: Security

ODI-10225: Invalid wallet password: A valid password must have a minimum length of eight characters and contain alphabetic characters combined with numbers or special characters.

Cause: Invalid wallet password.

Action: Please choose a valid wallet password accordingly.
Level: 32

Type: ERROR

Impact: Security

ODI-10226: Wallet already exists.

Cause: Try to create a wallet which already exists.

Action: Please stop creating a wallet. Instead use the existing one.
Level: 32

Type: ERROR

Impact: Security

ODI-10227: Wallet new password is same as old password.

Cause: You provide a new wallet password which is the same as the old one.

Action: Please choose different wallet password than the old one.
Level: 32

Type: ERROR

Impact: Security

ODI-10228: Repository with id ''{0}'' or with name ''{1}'' has been already used in your master repository.

Cause: Master repository has already work repository with the same name or id.

Action: Check your master repository and work repository.
Level: 32

Type: ERROR

Impact: Configuration

ODI-10229: Repository with id ''{0}'' has been already used in your master repository.

Cause: Master repository has already work repository with the same id.

Action: Check your master repository and work repository.
Level: 32

Type: ERROR

Impact: Configuration

ODI-10230: Repository with name ''{0}'' has been already used in your master repository.

Cause: Master repository has already work repository with the same name.

Action: Check your master repository and work repository.
Level: 32

Type: ERROR

Impact: Configuration

ODI-10231: Interface {0} cannot be imported because source temporary interface / mapping {1} is not found.

Cause: An attempt was made to import an interface with a source temporary interface / mapping that cannot be found in the import source or target repository.

Action: Import the missing source temporary interface / mapping.
Level: 32

Type: Error

Impact: Other

ODI-13700: Unable to set the role OWB_USER for this user.

Cause: An attempt was made to set the role OWB_USER for the connected user.

Action: Check that the role exists and the connected user is an OWB user.
Level: 1

Type: ERROR

Impact: Other

ODI-13701: Unable to set the workspace {0} for this user.

Cause: An attempt was made to select the OWB workspace for the connected user.

Action: Check that the workspace exists and the connected user has got privilege to access it.
Level: 1

Type: ERROR

Impact: Other

ODI-13702: Unexpected error when connecting to OWB workspace {0}.

Cause: An unexpected error occurred when connecting to workspace.

Action: Verify that the Owb repository is up and running.
Level: 1

Type: ERROR

Impact: Other

ODI-13703: Unexpected error when locating object {0} in OWB workspace {1}.

Cause: An unexpected error occurred when locating an object in a workspace

Action: Verify that the Owb repository is up and running and the object exists.
Level: 1

Type: ERROR

Impact: Other

ODI-13704: Could not locate the physical schema associated with OWB workspace {0} in context {1}.

Cause: An error occurred when finding the schema related to an OWB workspace in a context.

Action: Verify that the OWB workspace is related to a physical schema in the context.
Level: 1

Type: ERROR

Impact: Other

ODI-13800: Cannot locate the monitor configuration file: {0} using JVM argument: {1}={2} or the environment variable: {3}={4}.

Cause:

Action:
Level: 32

Type: WARNING

Impact: Configuration

ODI-13801: Cannot locate the monitor configuration file at: {0}.

Cause:

Action:
Level: 32

Type: WARNING

Impact: Configuration

ODI-13802: Cannot access the monitor configuration file: {0}.

Cause:

Action:
Level: 32

Type: WARNING

Impact: Configuration

ODI-13803: The contents of the monitor configuration file: {0} are invalid.

Cause:

Action:
Level: 32

Type: WARNING

Impact: Configuration

ODI-13804: The runtime performance monitoring has been turned off due to invalid monitor configuration.

Cause:

Action:
Level: 32

Type: WARNING

Impact: Configuration

ODI-13805: An error occured while updating the monitor status for the Agent:{0}, Master repository external id:{1}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13806: An error occurred while starting the pre execution monitor for Agent={0}, Master repository external id={1}, Scenario={2}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13807: An error occurred while stopping the pre execution monitor for Agent={0}, Master repository external id={1}, Scenario={2}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13808: An error occurred while starting the request processing monitor for Agent={0}, Master repository external id={1}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13809: An error occurred while stopping the request processing monitor for Agent={0}, Master repository external id={1}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13810: An error occurred while starting the execution monitor for Agent={0}, Master repository external id={1}, Scenario={2}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13811: An error occurred while stopping the execution monitor for Agent={0}, Master repository external id={1}, Scenario={2}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13812: An error occurred while starting the post execution monitor for Agent={0}, Master repository external id={1}, Scenario={2}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13813: An error occurred while stopping the post execution monitor for Agent={0}, Master repository external id={1}, Scenario={2}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13814: An error occurred while starting the Scenario execution monitor for Agent={0}, Master repository external id={1}, Scenario={2}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13815: An error occurred while stopping the Scenario execution monitor for Agent={0}, Master repository external id={1}, Scenario={2}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13816: An error occurred while starting the Step execution monitor for Agent={0}, Scenario={1}, Step={2}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13817: An error occurred while stopping the Step execution monitor for Agent={0}, Scenario={1}, Step={2}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13818: An unexpected error occurred while starting the entity monitor for entity={0}, agent={1}, master repository external id={2}, session id={3}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13819: An unexpected error occurred while updating the entity monitor for entity={0}, agent={1}, master repository external id={2}, session id={3}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13820: An unexpected error occurred while starting the entity monitor for entity={0}, agent={1}, master repository external id={2}, session id={3}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13821: An error occurred while registering the Agent Discovery Mbean, mbeanName={0}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13822: An error occurred while de-registering the Agent Discovery Mbean, mbeanName={0}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13823: Could not find the Server MBean for server {0} on platform {1}.

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-14000: Importing Object

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14001: Importing Profile

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14002: Importing User

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14003: Importing InstObj

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14004: Importing Local Repository

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14005: Importing Techno

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14006: Importing Data Types

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14007: Importing Data Types Conversions

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14008: Importing Language

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14009: Importing Open Tools

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14010: Importing Pwd Policies

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14011: Importing Pwd Rule

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14012: Importing Connection

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14013: Importing Agent

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14014: Importing LBAgent

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14015: Importing Logical Agent

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14016: Importing Context

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14017: Importing Pschema

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14018: Importing Lschema

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14019: Importing Entity

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14020: Importing Link

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14021: Importing Field

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14022: Importing FieldLook Up

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14023: Importing Look Up

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14024: Importing Look Up Value

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14025: Importing Action

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14026: Importing Action Group

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14027: Importing Version

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14028: Importing Solutions

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14029: Cleaning connections

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14030: Importing:

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other{0}

ODI-14031: Importing Session

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14032: Importing Global Sequences

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14033: Importing Global Variables

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14034: Importing Global User Functions

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14035: Importing Global Group of States

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14036: Importing Model Folders

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14037: Importing Models

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14038: Importing Scenario folders

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14039: Importing Projects

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14040: Importing Scenario

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14041: Importing Folders

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14042: Importing Packages

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14043: Importing Interfaces

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14044: Importing Procedures

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14045: Importing Knowledge Modules

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14046: ODI Master Repository Upgrade: Upgrading Repository Structure...

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Upgrade

ODI-14047: ODI Master Repository Upgrade: Upgrading Repository Data...

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Upgrade

ODI-14048: ODI Master Repository Upgrade: Done.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Upgrade

ODI-14049: Master repository creation is successful.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14050: ODI Work Repository Attach: Attaching Repository...

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14051: ODI Work Repository Attach: Done.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14052: ODI Work Repository Upgrade: Upgrading Repository Structure...

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Upgrade

ODI-14053: ODI Work Repository Upgrade: Upgrading Repository Data...

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Upgrade

ODI-14054: ODI Work Repository Upgrade: Done.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Upgrade

ODI-14055: Work repository creation is successful.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14056: Importing SubModels

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14057: Importing Tables

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14058: End importing {1}. Import time (milliseconds): {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14059: End importing {1}. Import time (hh:mm:ss): {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14060: End importing {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14061: Master repository already up to date nothing to do.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14062: Upgrading master repository from {0} to {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14063: Applying DDL from file {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14064: Error while applying DDL from file {0}

Cause: Exception during execution of session.

Action: Check session.
Level: 32

Type: ERROR

Impact: Other

ODI-14065: Work repository already up to date. Nothing to do.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Upgrade

ODI-14066: upgrade error while executing {0} params = {1}

Cause: Wrong parameters at Sql query.

Action: Check parameters.
Level: 32

Type: ERROR

Impact: Upgrade

ODI-14067: Exporting {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14068: End exporting {1}. Export time (milliseconds): {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14069: End exporting {1}. Export time (hh:mm:ss): {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14070: Import failed. The parent object was not found in the repository.

Cause: The object was imported in a SYNONYM mode and the parent object was not found in the repository.

Action: Change the import mode or restore the parent object in the repository
Level: 32

Type: ERROR

Impact: Other

ODI-14071: Getting Dependencies

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14072: End getting dependencies. Time (milliseconds): {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14073: End getting dependencies. Time (hh:mm:ss): {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14074: Parent folder already has the release tag set.

Cause: Setting the release tag when the parent already has the release tag set.

Action: Set the release tag in parent.
Level: 32

Type: ERROR

Impact: Other

ODI-14075: Seed data for property missing.

Cause: Seed data for property {0} is missing.

Action: Contact Oracle Support Services
Level: 32

Type: ERROR

Impact: Other

ODI-14077: Importing Mappings/Reusable Mappings

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14078: Importing Mapping Component Types

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14079: Importing Enterprise Scheduler

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14080: Importing Enterprise Principals

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14081: User Function syntax is not unique.

Cause: Work repository already has User Function with the same syntax.

Action: Check your user function syntax.
Level: 32

Type: ERROR

Impact: Other

ODI-15000: BSF Not Present

Cause: Bean Scripting Framework manager cannot be found.

Action: Ensure that class org.apache.bsf.BSFManager is available in the classpath.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15001: No End Separator for the following text:

Cause: No end delimiter found for a delimited text in the expression.

Action: Add an end delimiter to the delimited text.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15002: The string to be transformed cannot be null.

Cause: Parsing failed for an expression reference tag.

Action: Fix the expression.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15003: Error during Code Interpretor creation

Cause: Code generator internal error.

Action: Contact Oracle support.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15005: The datatype "{0}" does not exist in technology: {1}.

Cause: The datatype for a column is not supported by the technology.

Action: Change the datatype or the technology of the execution location.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15006: The source datatype is null for the column: {0}, and the technology: {1}

Cause: The datatype for a column is null for the technology.

Action: Change the datatype or the technology of the execution location.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15007: Syntax not set for 'Create Table' for the datatype: {0} for the technology: {1}.

Cause: The execution location technology does not have any "Create Table" syntax set up.

Action: Edit the technology definition and add "Create Table" syntax.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15009: No text for the 'Writable Datatype Syntax' for the datatype: {0} in technology: {1}

Cause: The datatype does not have a "Writable Datatype Syntax" property value set up for the execution location technology.

Action: Edit the datatype in the technology to add a "Writable Datatype Syntax".
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15010: No conversion for the datatype {0}, for the source technology {1} and for the target technology {2}

Cause: No conversion is defined for the source technology datatype to the target technology datatype.

Action: Edit the source or target technology datatype to add a conversion from the source to the target datatype.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15011: The variable does not exist in the database.

Cause: A variable is being referenced but it does not exist in the repository.

Action: Create the variable in the repository.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15012: Sequence does not exist in database

Cause: A sequence is referenced but does not exist in the repository.

Action: Create the sequence in the repository.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15013: The table {0} has fatal errors.

Cause: The table cannot be processed.

Action: Check the table for inconsistencies.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15014: The referenced text does not exist in the database.

Cause: The text reference in the expression does not exist in the repository.

Action: Repository corruption has occurred, contact Oracle support.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15015: Too much recursion in this text resolution.

Cause: The expression text references other text recursively too many times.

Action: Review the expression and try to simplify.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15016: Commands Undefined.

Cause: KM is missing a block of lines.

Action: Check the KM.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15017: Table not selected (null).

Cause: Target table not found.

Action: Check interface for consistency.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15018: CKM not selected.

Cause: The CKM is not selected for the object.

Action: Select a CKM.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15019: Missing context

Cause: The context object cannot be found.

Action: Check the context selection.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15020: No JKM available

Cause: JKM has not been set or is not found.

Action: Set a valid JKM for the interface.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15021: Journalizing requires a Primary Key on the Table:

Cause: Journalizing is enabled, but the target table has no primary key.

Action: Add a primary key to the target table.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15022: No RKM Set.

Cause: RKM has not been set or is not found.

Action: Set a valid RKM for the object.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15023: Cannot perform standard reverse. Choose customized reverse and set RKM.

Cause: Standard reverse engineering is not supported for this object.

Action: Select customized reverse engineering for the object and select an RKM.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15025: The interface clause text does not exist.

Cause: The interface clause refers to text that does not exist.

Action: Check interface clauses for (join, filter, etc.) for consistency.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15026: Interface clauses are missing.

Cause: The code generator cannot find the clause collection for the interface.

Action: Check the interface for consistency.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15027: Interface source tables are missing.

Cause: The code generator cannot find the source table collection for the interface.

Action: Check the interface for consistency.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15028: Interface result collection is null.

Cause: Internal error.

Action: Contact Oracle support.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15029: Interface error clause collection is missing.

Cause: Internal error.

Action: Contact Oracle support.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15030: Interface is missing the integration work table collection.

Cause: Internal error.

Action: Contact Oracle support.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15031: Technology not selected.

Cause: No technology is selected for the interface target execution location.

Action: Check the technology selection for the interface target.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15032: Unknown object in interface source table collection

Cause: Internal Error.

Action: Contact Oracle support.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15033: The expression: {0} does not have an associated column.

Cause: The expression should represent a column, but no column is found for the name.

Action: Fix the expression.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15034: A scenario with the same name and the same number already exists. Please select other values.

Cause: Cannot create a duplicate scenario with the same name and version number as an existing scenario.

Action: Give the scenario a different name or version.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15036: Scenario''s name and/or number are missing.

Cause: A scenario must have a name and version, but the name or version is missing.

Action: Set values for name and version for the scenario.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15037: The interface {0} has fatal errors.

Cause: The interface has fatal errors.

Action: Check and fix interface issues.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15038: The scenario name substitution pattern {0} is not supported. Please check the user parameter for the scenario naming convention.

Cause: Invalid substitution pattern used for scenario name.

Action: Change the substitution pattern.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15039: The interface {0} use native sequence. Native sequence are not allowed for Derived Table (sub select statement)

Cause: Native sequence was used in a sub-select or derived interface.

Action: Remove the native sequence usage.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15040: Errors detected when building SQL clauses.

Cause: An error occurred when generating code for the SQL clauses.

Action: Fix the interface clauses.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15041: An aggregation function may not be used in a join condition. Please use a separate interface for the aggregation and join the result in this interface.

Cause: An aggregation function was used inside a join condition expression.

Action: Change the join condition to remove the aggregation function.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15042: Unable to regenerate this scenario. It references an package that does not exist.

Cause: The scenario must reference a package, but it doesn't.

Action: Delete the scenario and create a new one.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15043: Unable to regenerate this scenario from a Runtime repository.

Cause: The scenario must cannot be regenerated from the runtime repository.

Action: Delete the scenario and create a new one.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15044: Invalid pScenSource type when calling SnpGeneratorSQLCIT.mainGenScenSourceScenario

Cause: Internal error.

Action: Contact Oracle support.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15045: Invalid value for KM type.

Cause: An invalid value was specified for the KM type.

Action: Specify a valid value.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15046: The column cache is null during code generation.

Cause: Internal Error.

Action: Contact Oracle support.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15047: The cached column is null in the column cache during code generation.

Cause: Internal Error.

Action: Contact Oracle support.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15050: Flow Control not possible if no key is declared in your target datastore

Cause: Flow control is enabled for the interface, but the target datastore has no primary key defined.

Action: Define a primary key for the target datastore object, and re-add the target datastore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15051: Missing mapping instance for interface.

Cause: The target column does not have any mapping.

Action: Add a mapping expression for the target column.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15052: The interface is missing a dataset.

Cause: There is no dataset for the interface source.

Action: Check the interface for consistency.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15055: Character '']'' missing in: {0}.

Cause: A bracketed tag inside a KM line is missing a closing bracket ("]") character.

Action: Fix the KM line.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15057: Non-ordered outer join not supported for technology.

Cause: Non-ordered outer join syntax disabled for technology.

Action: Correct join.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15058: Variable scenario generation error: Logical schema is required.

Cause: Variable scenario cannot be generated if logical schema is not set.

Action: Set the logical schema.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15059: I_TXT is mandatory.

Cause: A call was made to SnpTxtCachedHashMap.getInstance, but the pITxt parameter was null.

Action: Contact Oracle support.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15060: The JKM line {0} uses an unsupported execution channel: {1}

Cause: A line in the JKM uses an execution channel that is not supported.

Action: Change the line in the JKM to use a supported channel.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15061: The JKM line {0} uses an unsupported commit type: {1}

Cause: A line in the JKM uses a commit type that is not supported.

Action: Change the line in the JKM to use a supported commit type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15062: Invalid commit type: {0}

Cause: An invalid commit type was passed to SnpServiceGenerator.convertCommitType

Action: Contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15063: The alternate key {0} is not unique.

Cause: An alternate key defined by the repository is found to be non-unique.

Action: Check the data or the alternate key definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15064: The primary key {0} is not unique.

Cause: A primary key defined by the repository is found to be non-unique.

Action: Check the data or primary key definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15065: Join error ({0}) between the table {1} and the table {2}.

Cause: A foreign key relationship is not found.

Action: A foreign key relationship between 2 tables defined in the repository is not valid.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15066: The column {0} cannot be null.

Cause: The column is marked in the repository as not nullable.

Action: Check the data, or change the not null value.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15067: The datatype value ''{0}'' is incorrect.

Cause: An invalid datatype has been found.

Action: The repository table contains an invalid datatype.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15068: Unknown flexfield code.

Cause: An undefined flex field code is being referenced

Action: Check the flex field references in the KM, and the flex field definitions
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15069: {0} Is not valid without session context.

Cause: A current session context does not exist.

Action: Check session definition.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15070: Unable to find method object: PythonInterpreter.initialize(Properties, Properties, String[]) method

Cause: The python method used by the script is not found.

Action: Check the KM step.
Level: 32

Type: ERROR

Impact: Other

ODI-15071: Error occurred

Cause: An exception was thrown while executing a python script in the KM step.

Action: Check the cause.
Level: 32

Type: ERROR

Impact: Other

ODI-15072: There is no PK constraint

Cause: There is a call to "getPK" in the KM, but no PK is found.

Action: Check the KM and the PK definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15073: There is no index

Cause: There is a call to "getIndex" in the KM, but no index is found.

Action: Check the KM and the index definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15076: no dataset

Cause: A KM line is calling "getDataSet", but no data set is found.

Action: Check the KM or the DataSet definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15077: No Current Model Set

Cause: There is a call to "getModel" in the KM, but no model is found.

Action: Check the KM and the model definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15078: There is no Not Null column

Cause: There is a call to "getNotNullCol" in the KM, but no not null column is found.

Action: Check the KM and the not null column definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15079: There is no current Pop.

Cause: There is a call to "getPop" in the KM, but no interface is found.

Action: Check the KM and the interface definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15080: There is no Step

Cause: There is a call to "getStep" in the KM, but no step is found.

Action: Check the KM and the step definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15081: There is no Target Table

Cause: There is a call to "getTargetTable" in the KM, but no target table is found.

Action: Check the KM and the interface target table definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15083: Multiple Primary Keys have been detected for {0} .

Cause: A repository table can only have one primary key defined, but multiple primary keys are defined.

Action: Edit the table's primary key definitions and remove all but one.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15084: There is no session

Cause: There is a call to "getSession" in the KM, but no session is found.

Action: Check the KM and the session definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15085: The value : ''({0})'' is unknown.

Cause: A KM line has a templated call which contains an unknown bracketed property.

Action: Fix the KM.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15086: There is no Temporary Index

Cause: There is a call to "getTemporaryIndex" in the KM, but no temporary index is found.

Action: Check the KM and the temporary index definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15087: There is no current execution context defined.

Cause: There is a call to "getContext" in the KM, but no context is found.

Action: Check the KM and the context definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15088: Not in designer mode

Cause: A KM line has a call to access design information, but the interpretation location is not set to designer.

Action: Make sure that the interpretation location is set to designer when this line is executed.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15089: asked '({0})' and available value are between 0 and ({1}).

Cause: A KM line is calling "getDataSet", but the specified index is out of range.

Action: Fix the KM or the DataSet definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15090: Table "{0}" not found on model "{1}", schema "{2}"

Cause: Attempt to initialize data services from a table that cannot be found

Action: Change data services reference or make sure that table exists
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15091: Impossible to connect to JPS MBean Server

Cause: Cannot connect to JPS MBean server.

Action: Internal Error.
Level: 32

Type: ERROR

Impact: Other

ODI-15092: Unable to generate data service - the column {0} does not exist in the database.

Cause: A data service references a column that does not exist

Action: Fix the data service reference or make sure that the column exists
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15093: Unable to regenerate this scenario. It references a null package.

Cause: The scenario must reference a package, but the package is null.

Action: Delete the scenario and create a new one.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15094: You must give a name for the published entity for each datastore.

Cause: A web services data store does not have a name.

Action: Give the data store a name.
Level: 32

Type: ERROR

Impact: Other

ODI-15095: Invalid entity for datastore: {0}

Cause: A web services data store has an invalid entity.

Action: Associate the data store with a valid entity.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15096: Property name must not be null.

Cause: The KM line is calling "isColAttrChanged", but the property value is null.

Action: Internal error, contact Oracle support.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15097: Unknown value {0} for property

Cause: The KM line is making a templated call, but the property value is unknown.

Action: Fix the KM.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15098: You must define a data source for the model.

Cause: The model used by a web service does not have any data source.

Action: Define a data source for the model.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15099: You must specify a JKM for the model.

Cause: The model used by a web service does not have an associated JKM.

Action: Define a JKM for the model.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15100: You must define a Java package for the model.

Cause: The model used by a web service does not have an associated Java package.

Action: Define a Java package for the model.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15101: Invalid Java package format: {0}

Cause: The Java package associated with a model has an invalid package format.

Action: Correct the package format for the model.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15102: You must specify an XML namespace for the model.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15103: Invalid namespace: {0}

Cause: A model namespace used by a web service is invalid.

Action: Correct the namespace for the model.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15104: You must specify an SKM for the model.

Cause: A model used by a web service does not have an associated SKM.

Action: Add an SKM to the model.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15105: You must specify which schema the model will be deployed to.

Cause: No web service deployment schema is specified for the model.

Action: Specify a schema to which the model will be deployed.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15106: You must specify a name for the Data Service for the model.

Cause: The data service for the model does not have a name.

Action: Set a valid name for the data service.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15107: Invalid model code: {0}. It should follow the Java identifiers naming conventions.

Cause: The web service model name does not follow the standard Java identifier naming convention.

Action: Set a valid name for the model.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15108: Invalid model Data Service name: {0}. It should follow the Java identifiers naming conventions.

Cause: The web service model Data Service name does not follow the standard Java identifier naming convention.

Action: Set a valid name for the model Data Service.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15109: Invalid web service name for datastore: {0}

Cause: The web service model data store has an invalid name.

Action: Set a valid name for the model data store.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15110: SKM is empty

Cause: The web service SKM has no valid lines.

Action: Add some lines to the SKM.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15111: Problem during deployment

Cause: Internal error.

Action: Contact Oracle support.
Level: 32

Type: SET_AT_RUNTIME

Impact: Deployment

ODI-15113: Reverse table {0} for model {1} already exists.

Cause: An attempt was made to reverse engineer a table, but it already exists in the model.

Action: Move or rename the data store in the model, or skip reverse engineering for the table.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15116: There is not enough data in the target file to proceed with the reverse-engineering. Please make sure the file has at least one non-empty line and number of rows to skip is correct.

Cause: An attempt was made to reverse engineer a target file that is empty, or the number of skipped rows is larger than the number of rows in the file.

Action: Set the number of skipped lines to a lower value, or add some data to the file.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15117: Not allowed (OLD and NEW are involved)

Cause: The KM line is calling "getColumn", but the ADH action origin is not ''NEW'' or ''OLD''.

Action: Change the ADH action origin.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15118: Invalid FTP URL

Cause: The URL given for a web services FTP connection is not correct.

Action: Check the URL for the FTP connection.
Level: 32

Type: SET_AT_RUNTIME

Impact: Network

ODI-15119: Column {0} has no Java datatype.

Cause: The column being processed has no java datatype.

Action: Internal Error: contact Oracle support.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-15120: Column {0} has no String datatype.

Cause: The column being processed has no string datatype.

Action: Internal Error: contact Oracle support.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-15121: Selector must be not null

Cause: The ADH selector value must not be null when "getColumn" is called from the KM line.

Action: Change the ADH selector value.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15122: Exception getPKColList

Cause: An exception was found when calling "getPKColList" during KM execution.

Action: Fix the KM or the PK definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15123: There is no AK constraint

Cause: There is a call to "getAK" in the KM, but no AK is found.

Action: Check the KM and the AK definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15125: Missing DataSet.

Cause: The interface is missing a dataset.

Action: Check interface for consistency.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15126: The sub-model must be set.

Cause: The sub-model is not set for the source or target.

Action: Check the interface for consistency.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15127: There is no CK constraint

Cause: There is a call to "getCK" in the KM, but no CK is found.

Action: Check the KM and the CK definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15128: There is no FK constraint

Cause: There is a call to "getFK" in the KM, but no FK is found.

Action: Check the KM and the FK definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15129: Selector value must be 'OLD' or 'NEW'

Cause: The ADH selector value must be 'OLD' or 'NEW' when "getColumn" is called from the KM line.

Action: Change the ADH selector value.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15130: Unknown object in interface source table list

Cause: Internal Error.

Action: Contact Oracle support.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15131: You must define the name of each web service to be generated for each datastore.

Cause: A web service associated with a data store has no name.

Action: Give a name to the web service.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15132: Exception getPK

Cause: An exception was found when calling "getPK" during KM execution.

Action: Fix the KM or the PK definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15135: There is no current index.

Cause: The current index can not be found for the property name.

Action: Check the reference.
Level: 32

Type: ERROR

Impact: Other

ODI-15140: Unable to regenerate the following scenario:

Cause: The scenario must reference a package, but it does not

Action: Delete the scenario and create a new one
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15141: Repository is not a development work repository

Cause: When getting a connection used to execute the KM, it was determined that the provided connection information does not point to a development work repository

Action: Fix the connection information
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15142: [PROPERTY: {0} not found.]

Cause: The bracketed property in the KM line (e.g. "[COL_NAME]") is not found.

Action: Fix the KM line to specify a correct property name.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15143: Invalid isolation level : {0}

Cause: An invalid isolation level value was passed to SnpServiceGenerator.convertIsolationLevel

Action: Contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15144: KM not encrypted since it is empty.

Cause: KM was not encrypted since it is empty.

Action: Skip encryption.
Level: 32

Type: ERROR

Impact: Other

ODI-15146: Data Type can't be null

Cause: null DataType passed.

Action: Pass non null DataType.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15147: The changes on this target column will be lost since it is not saved (it has no mapping text)

Cause: Target column will not be saved.

Action: Enter mapping text if the column requires to be saved.
Level: 32

Type: WARNING

Impact: Interface Issue

ODI-15148: The target datastore is not on the Oracle Technology: this interface cannot be used with the platform compiler

Cause: Target datastore is not on Oracle.

Action: Move target datastore to an Oracle schema.
Level: 32

Type: WARNING

Impact: Interface Issue

ODI-15149: The staging area is not on the Oracle Technology: this interface cannot be used with the platform compiler

Cause: Staging Area is not on Oracle.

Action: Move Staging Area to an Oracle schema.
Level: 32

Type: WARNING

Impact: Interface Issue

ODI-15150: The source datastore is not on the Oracle Technology: this interface cannot be used with the platform compiler

Cause: Source DataStore not on Oracle.

Action: Use only DataStores located on an Oracle technology.
Level: 32

Type: WARNING

Impact: Interface Issue

ODI-15151: Non ordered outer joins cannot be used with the platform compiler

Cause: An outer join is not ordered.

Action: Make the join ordered.
Level: 32

Type: WARNING

Impact: Interface Issue

ODI-15152: Unhandled Action {0}

Cause: This shouldn't happen. Programmer added an action in the enum and forgot to add it in switch.

Action: Add action in switch.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15153: The column is already the first column and cannot be moved up

Cause: Column already first and cannot be moved up.

Action: Do not try to move first column up.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15154: The column is already the last column and cannot be moved down

Cause: Column already last and cannot be moved down.

Action: Do not try to move last column down.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15155: Cannot move a target column to a position that is 0 or negative: {0}

Cause: Trying to move a column beyond the boundaries of column positions.

Action: Use a value between 1 and the number of columns.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15156: Cannot move a target column to a position beyond the size of the column list: {0} is greater than {1}

Cause: Trying to move a column beyond the boundaries of column positions.

Action: Use a value between 1 and the number of columns.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15157: Cannot remove the only dataset of interface {0}

Cause: Trying to remove the last dataset of an interface is not permitted.

Action: Make sure there are more than one dataset in the interface before deleting it.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15159: Cannot move target columns on a non temporary DataStore.

Cause: Trying to move columns on a non temporary DataStore.

Action: Make sure that the target DataStore is temporary before attempting to move target columns.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15160: Native Sequences may not be supported by the target technology after transforming with the Platform Compiler

Cause: Using Native Sequence and Platform Compiler Enabled User Param Set

Action: Make sure that all target technologies will support native sequences
Level: 32

Type: WARNING

Impact: Programmatic

ODI-15162: The interface {0} use native sequence. Native sequence are not allowed for Derived Table (sub select statement)

Cause: Using native sequence in derived sub interface

Action: Make sure that none sub interface using native sequence
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15200: Tried to retrieve an int with an {0} object

Cause: Attempted to read the column from RDB as an integer, but the column type is not integer

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15201: Tried to retrieve a short with an {0} object

Cause: Attempted to read the column from RDB as a short type, but the column type is not short

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15202: This resultset accepts only FETCHFORWARD requests

Cause: Attempted to set the fetch direction to something other than FETCH_FORWARD for a RDB result set read

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15203: This function is unsupported: the software you are using might not be compatible with this driver.

Cause: A jdbc call was made that is not supported by the currently loaded jdbc driver for RDB

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15204: The {0} call is not implemented in this result set class.

Cause: A result set call was made that is not implemented by the ODI RDB result set class

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15205: The call is not supported in this result set class.

Cause: A result set call was made that is not supported by the ODI RDB result set class

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15207: Unmanaged numeric type {0}

Cause: When selecting a parent row based on a primary key, multiple rows were returned

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15208: The PK column of the root table has an unknown type: {0}

Cause: When unloading data from the RDB, the PK column of the parent table has an unknown type

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15209: Unsupported technology (Driver: {0}, Url: {1})

Cause: The jdbc driver is not supported by the ODI RDB

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15210: Unsupported technology: HSQL cannot create FKs after the tables have been created

Cause: The Hypersonic SQL engine cannot create FK after the table is already created

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15211: Unsupported technology: HSQL cannot create PKs after the tables have been created

Cause: The Hypersonic SQL engine cannot create PK after the table is already created

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15212: Datatype NULL (0) unsupported

Cause: The Hypersonic SQL engine does not support the null datatype

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15213: JDBC Datatype '{0}' unsupported

Cause: The Hypersonic SQL engine does not support the datatype

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15214: JDBC Datatype '{0}' with length parameter unsupported

Cause: The Hypersonic SQL engine does not support the datatype with length

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15215: JDBC Datatype '{0}' with length and scale parameters unsupported

Cause: The Hypersonic SQL engine does not support the datatype with scale

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15216: JDBC Datatype '{0}' unsupported

Cause: The internal MS Sql Server database does not support the datatype

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15217: JDBC Datatype '{0}' with length parameter unsupported

Cause: The internal MS SQL Server database does not support the datatype with length

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15218: JDBC Datatype '{0}' with length and scale parameters unsupported

Cause: The internal MS SQL Server database engine does not support the datatype with length and scale

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15219: Please transform your URL into: {0};SelectMethod=cursor

Cause: The internal MS SQL Server database engine does not recognize the supplied URL

Action: Change the format of the connection URL
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15220: need length param

Cause: The internal Oracle database does not support the selected type without a length param

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15221: Datatype NULL (0) unsupported

Cause: The internal Oracle SQL engine does not support the null datatype

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15222: JDBC Datatype '{0}' unsupported

Cause: The internal Oracle database does not support the datatype

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15223: JDBC Datatype '{0}' with length parameter unsupported

Cause: The internal Oracle database does not support the datatype with length

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15224: JDBC Datatype '{0}' with length and scale parameters unsupported

Cause: The internal Oracle database engine does not support the datatype with length and scale

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15225: No key found on table {0}

Cause: The internal database table does not have a key

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15226: The root table {0} has no data

Cause: The internal database table does not have any data

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15227: Multiple keys found on table {0}

Cause: The internal database table has multiple keys

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15228: *** FATAL *** Table {0} could not be validated

Cause: The internal database cannot validate the table

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15229: *** FATAL *** Table {0} could not be found

Cause: The internal database cannot find the table

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15230: Could not convert object {0} to a {1}

Cause: The internal database cannot convert the datatype of the selected column

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15231: No '=' sign found on line {0} of bundle {1}

Cause: The internal database engine encountered a syntax error when reading the property file

Action: Fix the property file
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15232: The alias {0} for table {1} is already used by another table, when reading bundle {2}

Cause: The internal database found a duplicate table alias in a property file

Action: Fix the property file
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15233: Table {0} is used twice. Make sure that the table names and aliases do not conflict.

Cause: The internal database found a duplicate table name in the property bundle

Action: Fix the property file
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15234: Internal RDB database table {0} not found

Cause: The requested table cannot be found in the internal database

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15235: Internal RDB database key {0} not found

Cause: The requested key cannot be found in the internal database

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15236: Unknown table {0}

Cause: The requested table cannot be found in the internal database

Action: Correct the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15237: Duplicate table

Cause: The internal database table is a duplicate table

Action: Correct the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15238: Could not find table although we should have created it!

Cause: The newly created table cannot be found

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15239: Only SnpsRDBDiffActionImportDifference are supported for now.

Cause: When processing diff actions in a diff operation, an unsupported diff action class was found

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15240: Unknown key {0}

Cause: When processing diff actions in a diff operation, a nonexistent key was specified by the diff action

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15241: This type of difference is not managed for now: {0}

Cause: When processing diff actions in a diff operation, an unsupported diff action class was found

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15242: Unknown difference type: {0}

Cause: When processing diff actions in a diff operation, an unknown diff class was found

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15243: Bad model number: {0}

Cause: When processing diff actions in a diff operation, the 2 models that are being compared are internally numbered as model 1 and 2. A model number other than 1 or 2 was used internally in a call to getModel.

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15244: Could not add a key because {0} is not an ID key.

Cause: When building a model, the specified key class instance was not an id key

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15246: Unknown key type: {0}

Cause: When building a model, an unknown key class was found

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15247: The table {0} cannot be found. It is referenced by key: {1}.

Cause: When building a model, an table name is referenced by a key, but the table cannot be found

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15248: The column {0} in table {1} cannot be found. It is referenced by key: {2}.

Cause: When building a model, an column name is referenced by a key, but the column cannot be found

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15249: An {0} was caught while adding a key which is not an FK. Very strange.

Cause: When building a model, an column name is referenced by a key, but the column cannot be found

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15250: The key {0} referenced by table {1} cannot be found.

Cause: When building a model, a key name is referenced by a table, but the key cannot be found

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15251: A duplicate key was found: {0}

Cause: When dropping a model, a duplicate key was found in the model

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15252: Key already exists: {0}

Cause: When updating a model, a duplicate key was found in the model

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15253: Key not found: {0}

Cause: When updating a model, the key was not found

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15254: Could not find a constructor with a key name for class {0}

Cause: When creating a key class instance, the constructor could not be found

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15255: Could not instantiate an object of class {0}

Cause: Could not instantiate the key class

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15256: Could not create an object for class {0} for security reasons

Cause: Could not instantiate the key class, due to a security failure

Action: Check security settings
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15257: Could create an object for class {0} because a {1} occurred saying {2}

Cause: Could not instantiate the key class, due to an invocation target exception

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15258: Column {0} not found

Cause: The column could not be found

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15259: The key class {0} is not an ID key class.

Cause: The specified key class instance was not a SnpsRDBIdKey instance

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15260: Could not add column {0}: Unsupported datatype: {1}

Cause: Cannot add the column to the model because the datatype is not supported by the technology

Action: Correct the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15261: Unsupported action: {0}

Cause: The action class is not supported by the ODI RDB

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15262: Cannot drop column {0}. It is used in a foreign key!

Cause: An attempt was made to drop a column that participates in a foreign key

Action: Drop the key first, then the column
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15263: Cannot drop column {0}. It is used in a primary key!

Cause: An attempt was made to drop a column that participates in a primary key

Action: Drop the key first, then the column
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15264: Cannot modify this column. It is used in a foreign key!

Cause: An attempt was made to modify a column that participates in a foreign key

Action: Drop the key first, then modify the column
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15265: Cannot modify this column. It is used in a primary key!

Cause: An attempt was made to modify a column that participates in a primary key

Action: Drop the key first, then modify the column
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15268: Table not found: {0}

Cause: When attempting to drop a table during an update, the table name is not found

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15270: Key type {0} is not supported here.

Cause: The key type is not supported

Action: Correct the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15272: An error occurred while executing a RDB command: {0}

Cause: When executing a command action, an exception was thrown

Action: Check root cause
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15273: {0}: action is not accepted: {1}

Cause: Attempt to execute a command action, but it is not accepted

Action: Check root cause
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15274: Multiple PKs are not allowed on a table

Cause: When reverse engineering a primary key, multiple primary keys were found for the table

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15275: An exception ocurred while retrieving a table primary key: {0}

Cause: When reverse engineering a table, a primary key could not be retrieved

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15276: An exception occurred while retrieving the indexes of a table: {0}

Cause: When reverse engineering a table, the indexes could not be retrieved

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15277: An exception ocurred while retrieving a table foreign keys: {0}

Cause: When reverse engineering a table, the foreign keys could not be retrieved

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15278: An exception occurred while retrieving the check constraints of a table: {0}

Cause: When reverse engineering a table, the check constraints could not be retrieved

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15279: An exception occurred while retrieving the alternate keys of a table: {0}

Cause: When reverse engineering a table, the alternate keys could not be retrieved

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15280: *** FATAL *** Table {0} is duplicate as root

Cause: The table is duplicated as the root when determining the root tables of the model

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15281: *** FATAL ** Table {0} is unknown

Cause: The root table is unknown

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15282: Table {0} is unknown though it was reversed

Cause: The table cannot be found in the ODI model, although it was reversed

Action: Retry the reverse engineering
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15283: Duplicate declaration for table {0}

Cause: The model XML contains a duplicate table declaration

Action: Fix the XML
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15285: FK {0} references a table with no PK.

Cause: The model XML contains a foreign key that references a table with no defined primary key

Action: Fix the XML
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15286: Unknown PK table for foreign key {0}: please check the name and order of the tables and FK.

Cause: The model XML contains a foreign key that references an unknown primary key table

Action: Fix the XML
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15287: Unknown element: {0}

Cause: The model XML contains an unknown element

Action: Fix the XML
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15288: An {0} error occurred with the following message: {1}

Cause: An error occurred when writing the model to a file

Action: See root cause
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15290: Column {0} was not found in table {1}

Cause: The column was not found when building the columns from column names

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15291: *** FATAL *** Could not rename table {0} to {1}

Cause: Could not rename table

Action: Check permissions and security settings
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15292: *** FATAL *** Could not rename table {0} because it was not found in the model!

Cause: Could not rename table, because the table to be renamed does not exist

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15293: Unknown FK table for foreign key {0}: please check the name and order of the tables and FK.

Cause: The model XML contains a foreign key that references an unknown table

Action: Fix the XML
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15294: unknown element: {0}

Cause: The model XML contains an unknown XML element

Action: Fix the XML
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15295: Unsupported datatype: {0}

Cause: The datatype is unsupported when creating the column from attributes

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15300: A {0} occurred while creating the helper of class {1}. Error message: {2}

Cause: INTERNAL ERROR: A helper cannot be created.

Action: Internal error: contact Oracle support.
Level: 32

Type: ERROR

Impact: Other

ODI-15301: Choose: {0}

Cause: Choose one of the displayed options.

Action: Choose one of the displayed options.
Level: 32

Type: ERROR

Impact: Other

ODI-15302: FK is null: {0}

Cause: The FK is null, may indicate repository corruption.

Action: Internal error: contact Oracle support.
Level: 32

Type: ERROR

Impact: Other

ODI-15400: Error in generating data service

Cause: Exception thrown when creating the data service used for DDL generation and reverse engineering.

Action: Check the root cause.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15401: Unknown key {0}

Cause: Unknown key encountered when processing diff class instances during DDL generation.

Action: Check the model.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15402: Exception thrown in the DDL generation service: {0}

Cause: An exception was thrown while generating DDL.

Action: Check the root cause.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15403: The method is not supposed to sort something else than the expected actors. Attempting to sort class instances: {0}, {1}

Cause: While sorting action commands, the DDL generator service encountered an unknown class instance type.

Action: Internal Error: contact Oracle support.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15404: Scenario generation has not been implemented for this container.

Cause: During DDL generation, an attempt was made to generate a scenario for an object that does not support it.

Action: Internal Error: contact Oracle support.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15405: Scenario generation exception: {0}

Cause: An exception was thrown during scenario generation.

Action: Check root cause.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15500: Column {0} is executed on the target

Cause: Possible Cause

Action: Suggested Action
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15501: Cannot attach a data store to a target mapping because column {0} is not found.

Cause: The specified target column was not found.

Action: Verify that the correct column has been specified.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15502: Target mapping not found for column {0}

Cause: The specified column is not mapped.

Action: Map the specified column.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15503: Cannot set the attached datastore because the mapping is not executed on the SOURCE

Cause: The mapping has been configured for execution on the target.

Action: Configure the mapping for execution on the source.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15504: Unknown indicator type: {0}

Cause: An invalid indicator type has been specified.

Action: Specify one of the following indicator types from the IndicatorType enumeration: CHECK_NOT_NULL, INSERT, UPDATE, or UPDATE_KEY.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15505: Invalid UD number: {0}

Cause: An invalid UD number has been specified.

Action: Specify a UD number 1 to 10.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15506: The specified target column was not found: {0}

Cause: The specified target column was not found when attempting to remove a column from a temporary data store.

Action: Only remove columns which exist in the temporary target datastore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15507: Column {0} may not be removed. It is used in other mappings, join clauses, or filter clauses

Cause: The specified target column is used in other mappings, filters, or joins. This dependency prevents removal of the column.

Action: Only remove a column after mapping, filter, or join dependencies have been removed.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15508: Column {0} may not be removed because it is referenced in interface {1}.

Cause: The specified target column is referenced in a filter or join clause in another interface. This dependency prevents removal of the column.

Action: Only remove a column after other references have been removed.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15509: The specified target column was not found: {0}

Cause: The specified target column was not found.

Action: Verify the column name.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15510: A column was not found while updating the key

Cause: The update key contains a column that does not exist.

Action: Check the columns of the update key.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15511: The join must be attached to the datastore to expand a lookup.

Cause: The join is not attached to a datastore, so a valid lookup does not exist.

Action: Only use the lookup expansion, with a pCreateLookup parameter value of false, on valid lookups.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15512: Cannot transform a normal datastore into a normal lookup.

Cause: The data store is already a non-lookup data store.

Action: Do not use this transformation on a non-lookup data store. If the datastore and join are non-lookup, use a pCreateLookup parameter value of true to create a lookup from a normal join and normal datastore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15513: Cannot transform a normal, non-lookup join into a normal join.

Cause: The join is already a normal join, not a lookup join, so expansion to a normal, non-lookup join is not possible.

Action: Do not use this transformation on a normal join. If the datastore and join are non-lookup, use a pCreateLookup parameter value of true to create a lookup from a normal join and normal datastore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15514: Cannot transform a lookup datastore into a lookup.

Cause: The data store is already designated as a lookup, so transforming to a lookup is not possible.

Action: Do not use this transformation on a lookup. If the datastore and join are designated for lookup, use a pCreateLookup parameter value of false to expand a lookup to a normal join and normal datastore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15515: Cannot transform a lookup join into a lookup.

Cause: The join is already designated as a lookup, so transforming to a lookup is not possible.

Action: Do not use this transformation on a lookup. If the datastore and join are designated for lookup, use a pCreateLookup parameter value of false to expand a lookup to a normal join and normal datastore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15516: The join must be attached to the datastore to make a lookup.

Cause: The join is not properly attached to data sources, so transforming to a lookup is not possible.

Action: Designate data sources for the join.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15517: Cannot add a column with the same name as an existing target column: {0}.

Cause: The column being added already exists.

Action: Add a column with a unique name.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15518: A dataset is already assigned the order: {0}.

Cause: Another dataset has already been assigned the order that is being set.

Action: Assign a unique order to the dataset.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15519: The target datastore cannot be changed. Interface {0} is used in interface(s) {1} as a source datastore.

Cause: The interface is used as a source datastore of another interface, so the target datastore cannot be changed.

Action: Create a separate interface to avoid the source datastore dependency in the other interface.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15520: Temporary interface from another project is not allowed.

Cause: The interface is used as a source datastore of another interface, so the target datastore cannot be changed.

Action: Create a separate interface to avoid the source datastore dependency in the other interface.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15521: A source datastore with alias {0} already exists.

Cause: The datastore alias has already been used.

Action: Specify a unique alias.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15522: Cannot transform a join into a CrossJoin or natural join if it does not have both attached datastores set.

Cause: The join does not have datastores attached yet.

Action: Attach both join datastores before transforming to a cross join.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15523: LKM {0} not accepted for source set {1}

Cause:

Action:
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15524: LKM {0} not accepted for staging area to target

Cause:

Action:
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15525: CKM {0} not accepted for target technology

Cause:

Action:
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15526: IKM {0} not accepted for staging and target technology

Cause:

Action:
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15527: IKM {0} not accepted for target technology

Cause:

Action:
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15528: Mapping expression cannot be set because the target column {0} was not found.

Cause: The column was not found when setting the expression for a mapping.

Action: Specify a valid column for the expression.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15529: Action was not reversible.

Cause: The actions causing an impact are not reversible.

Action: Avoid the sequence of actions causing the impact.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15530: The interface does not have a source set.

Cause: The interface does not have a source set.

Action: Add a source set to the interface.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15531: The execution location parameter for the computeExpression method is invalid.

Cause: The execution location parameter for the computeExpression method is invalid.

Action: Specify an execution location parameter of ExecutionLocation.SOURCE, ExecutionLocation.WORK, or ExecutionLocation.TARGET.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15532: The pExecutableTextHolder parameter for the getLogicalSchemaForTextHolder method does not have a valid execution location.

Cause: The pExecutableTextHolder parameter for the getLogicalSchemaForTextHolder method does not have a valid execution location.

Action: Specify an execution location parameter of ExecutionLocation.SOURCE, ExecutionLocation.WORK, or ExecutionLocation.TARGET.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15533: The physical schema could not be mapped from logical schema {0} and context {1}.

Cause: The getPhysicalSchema method failed to map and logical schema and context to a physical schema.

Action: Ensure that logical to physical schema mappings are created or check the logical schema and context parameters.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15534: Sub interface must not be null.

Cause: The pSubInterface parameter passed to the checkSubInterfaceValid method is null.

Action: A non-null sub interface parameter is required for the checkSubInterfaceValid method.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15535: The technology {0} of the source temporary interface {1} used as a derived table does not support derived tables.

Cause: The pSubInterface parameter passed to the checkSubInterfaceValid method is null.

Action: A non-null sub interface parameter is required for the checkSubInterfaceValid method.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15536: Source temporary interface {0} cannot be used as a derived table. Its source datastore {1} defined in logical schema {2} has no associated physical schema in the optimization context {3}.

Cause: The temporary interface cannot be used because a physical schema has not been mapped to the logical schema for the source.

Action: Create a mapping between the logical schema, context, and physical schema for the source data store.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15537: Source temporary interface {0} cannot be used as a derived table. The logical schema of the target datastore {1} has no associated physical schema in context {2}.

Cause: The temporary interface cannot be used because a physical schema has not been mapped to the logical schema for the target.

Action: Create a mapping between the logical schema, context, and physical schema for the target data store.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15538: Source temporary interface {0} cannot be used as a derived table. The logical schema of the staging area {1} has no associated physical schema in the optimization context {2}.

Cause: The temporary interface cannot be used because a physical schema has not been mapped to the logical schema for the staging area.

Action: Create a mapping between the logical schema, context, and physical schema.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15539: Source temporary interface {0} cannot be used as a derived table. Source datastore {1} is not on the same data server as the target.

Cause: The temporary interface cannot be used because the source data store is not on the same data server as the target.

Action: Ensure that the source and target datastores are on the same data server.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15540: Source temporary interface {0} cannot be used as a derived table. Staging area and target datastores are not in the same data server. You may have forced the target context to a different context than the optimization context.

Cause: The temporary interface cannot be used because the staging data store is not on the same data server as the target.

Action: Ensure that the staging and target datastores are on the same data server.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15541: Source temporary interface {0} uses a journalized datastore and cannot be used as a derived table.

Cause: The temporary interface cannot be used because it uses a journalized datastore.

Action: Use only non journalized data stores in temporary interfaces.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15542: Source temporary interface {0} cannot be used as a derived table. All source datastores of this interface should be in the same data server as the target and should not be journalized.

Cause: The temporary interface cannot be used because it uses a journalized datastore.

Action: Use only non journalized data stores in temporary interfaces.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15543: Another interface with the same name already exists in this folder. Please choose a unique interface name.

Cause: Another interface with the same name already exists in this folder.

Action: Specify a unique interface name.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15544: The interface must have a name.

Cause: The interface does not have a name.

Action: Specify a unique interface name.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15545: Temporary target datastore has no name.

Cause: The temporary target datastore has no name

Action: Specify a unique datastore name.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15546: The interface must have a logical schema.

Cause: The interface does not have a logical schema.

Action: Specify a logical schema for the interface.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15547: Could not fix a missing reference correctly.

Cause: The interface is missing one or more references.

Action:
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15548: The source datastore has already been set.

Cause: The source datastore has already been set.

Action: Only invoke setSourceDataStore once.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15549: Cannot set the source filter because the source datastore is not set.

Cause: The source datastore has not been set prior to setting the filter.

Action: Set the source datastore prior to setting the filter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15550: The target datastore has already been set.

Cause: The source datastore has already been set.

Action: Only invoke setSourceDataStore once.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15551: Mappings on the target are not allowed in this helper.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15552: A source filter requires a source datastore.

Cause: The interface cannot be saved because it contains a filter without a source datastore.

Action: Create a source datastore before creating a source filter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15553: The target datastore must be set.

Cause: The target datastore for the interface has not been set.

Action: Set the target datastore before saving the interface.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15554: An LKM must be set on the source set.

Cause: A loading knowledge module has not been assigned to the source set.

Action: Set the LKM for the source set before saving the interface.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15555: Target IKM must be set on the target table.

Cause: An integration knowledge module has not been assigned to the target table.

Action: Set the IKM for the target before saving the interface.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15556: Unknown generic clause type: {0}

Cause: An unknown generic clause class was passed to the createSnpPopClauseFromGenericClause method.

Action: Pass only generic clause classes for join or filter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15557: Unknown execution location type: {0}

Cause: An unknown execution location enumeration was passed to the getStringExeDbFromExecutionLocation method.

Action: Pass only location enumerations of ExecutionLocation.SOURCE, ExecutionLocation.WORK, ExecutionLocation.TARGET.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15558: There is a conflict between physical schemas

Cause: There is a conflict between the various physical schemas used to obtain the data, such as multiple data stores in the same source set connected using different physical schemas.

Action: Ensure that physical schemas of a source set have consistent connection information.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15559: Unsupported component: {0}

Cause: An unsupported component was passed as a parameter to createDataAccessinfo.

Action: For the pInterfaceSubComponents parameter, supported components are SourceDataStore, ISourceColumn, TargetMapping, and GenericClause.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15560: Fatal interface condition: {0}

Cause: A fatal issue was discovered while saving or verifying an interface.

Action: Correct the interface issue before saving it.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15561: Could not find column {0} which choosing a mapping.

Cause: The MappingChooserFirst.chooseMapping method was called with an column name that does not exist.

Action: Check the column name passed to chooseMapping.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15562: Source sets cannot be computed because one execution area doesn't have a physical schema. Check the errors on the interface.

Cause: Source sets cannot be computed because one execution area doesn't have a physical schema.

Action: Check the errors on the interface.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15563: Source sets cannot be computed because the staging area is not properly defined. Check your target datastore and the staging area's physical schema in the Definition tab.

Cause: Source sets cannot be computed because the staging area is not properly defined.

Action: Check your target datastore and the staging area's physical schema in the Definition tab.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15564: There should be one source set on the interface.

Cause: The interface has more than one source set.

Action: Ensure that only one source set is defined.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15565: Column {0} not found while setting the update key.

Cause: A column specified for the update key does not exist.

Action: Recheck the column names used to define the update key.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15566: No target column was found while setting the target data store.

Cause: No target column was found while setting the target data store.

Action: Define columns before setting the target datastore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15567: Target column {0} was not found.

Cause: No specified target column was not found in the target data store.

Action: Check the column name parameter in the RealBasicInterfaceCreationHelper.getTargetColumn method call.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15568: Column {0} not found on datastore {1}.

Cause: A referenced column was not found in a source data store.

Action: Check the source datastore columns and references for a mismatch.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15569: Cannot create a data source.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15570: Cannot add a datastore of type {0} as source.

Cause: An invalid datastore type has been specified.

Action: Specify a datastore of type TargetDataStore, SourceDataStore, or OdiDataStore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15571: Unexpected join type {0}

Cause: An invalid join type has been specified when setting join properties.

Action: Specify a join type of INNER, CROSS, or NATURAL.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15572: Unexpected join state.

Cause: An invalid join state has been reached. The expected join type is CROSS or NATURAL.

Action: .
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15573: Failed to create an interface helper instance.

Cause: A general exception was encountered while constructing an interface helper.

Action:
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15574: General exception encountered in the interface helper while preparing to persist.

Cause: General exception encountered in the interface helper while preparing to persist.

Action:
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15575: Two journalized datastores have been found. There should be only one.

Cause: Two journalized datastores have been found. There should be only one.

Action:
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15576: Two journalized filters have been found. There should be only one.

Cause: Two journalized filters have been found. There should be only one.

Action:
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15577: Unmanaged type: {0}

Cause: An invalid element type was passed to the prepareSQLStatement method.

Action: Pass only valid element types such as GenericClause, SourceDataStore, TargetDataStore, ISourceColumn, TargetMapping, SourceSet, DataSet, or TargetColumn.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15578: No interface was found in the elements.

Cause: No interface could be traced to the elements passed to the prepareSQLStatement method.

Action: Create an interface.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15579: No dataset was found in the elements.

Cause: No data set could be traced to the elements passed to the prepareSQLStatement method.

Action: Ensure that a dataset has been created first.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15580: The target is a temporary table.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15581: Cannot build the query because the ordered joins are not correct.

Cause: The SQL clause cannot be generated because the ordered joins are not correct.

Action: Ensure that all joins are correct.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15582: This operation is not supported on joined file datastores.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15583: This operation is not supported on multiple file datastores.

Cause: More than one source datastore was found.

Action:
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15584: Elements are from different interfaces.

Cause: The components passed to prepareSQLStatement are from different interfaces.

Action:
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15585: Elements are from different datasets.

Cause: The components passed to prepareSQLStatement are from different data sets.

Action:
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15586: Unsupported component: {0}

Cause: An invalid component type was passed to connectionForData.

Action: Only pass components of type SourceDataStore, ISourceColumn, TargetMapping, TargetColumn, GenericClause, or TargetDataStore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15587: Journalization filter not found for the journalized table.

Cause: The journalized table does not have a filter.

Action: Define a journalizing filter for the table.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15588: The SQL join clause is not valid for a cross join.

Cause: A join clause has been specified for a cross join.

Action: Remove the join condition or change the join type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15589: Cannot change the ON_TARGET indicator on a temporary interface.

Cause: An attempt was made to set the ON_TARGET indicator for a temporary datastore.

Action: Do not change the ON_TARGET indicator for a temporary datastore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15590: Unknown indicator type: {0}

Cause: An unknown value was passed to the constructor for InterfaceActionOnStagingAreaSetIndicator.

Action: Use valid values of DISTINCT_ROW, ON_TARGET, or ON_USER_DATABASE_SCHEMA for the pIndicatorType parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15591: Staging Area is on the target and cannot be switched to another logical schema.

Cause: The staging area is on the target and uses the target schema. It cannot be switched.

Action: Do not attempt to switch the schema, or use a separate staging area.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15592: GenericClause is of unknown type: {0}

Cause: InterfaceActionRemoveGenericClause was constructed with an invalid generic clause.

Action: Use a generic clause type of JOIN or FILTER.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15593: Could not set LKM for object of type {0}

Cause: An LKM is being set for a TargetDataStore or some other invalid type.

Action: Only set an LKM for a SourceSet or StagingArea.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15594: Could not set the CKM for a holder of type {0}

Cause: A CKM is being set for a SourceSet, StagingArea, or some other invalid type.

Action: Only set a CKM for a TargetDataStore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15595: Could not set the IKM for a holder of type {0}

Cause: An IKM is being set for a SourceSet, StagingArea, or some other invalid type.

Action: Only set an IKM for a TargetDataStore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15596: Invalid KM type: {0}

Cause: An invalid object type is being used to set a KM.

Action: Only set a KM of type LKM, CKM, or IKM.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15597: Could not set the LKM option for a holder of type {0}

Cause: An LKM is being set for a TargetDataStore or some other invalid type.

Action: Only set an LKM option for a SourceSet or StagingArea.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15598: Could not set the CKM option for a holder of type {0}

Cause: A CKM option is being set for a SourceSet, StagingArea, or some other invalid KM holder type.

Action: Only set a CKM option for a KM holder of type TagetDataStore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15599: Could not set the IKM option for a holder of type {0}

Cause: An IKM option is being set for a SourceSet, StagingArea, or some other invalid KM holder type.

Action: Only set an IKM option for a KM holder of type TagetDataStore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15600: Dataset 1 was not found in the list of the interface datasets used with the interface.

Cause: The first dataset given as a parameter in the construction of the InterfaceActionSwitchDataSetOrders class is not used in the interface.

Action: Recheck the datasets being switched for this interface. Both datasets must be used in the interface.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15601: Dataset 2 was not found in the list of the datasets used with the interface.

Cause: The second dataset given as a parameter in the construction of the InterfaceActionSwitchDataSetOrders class is not used in the interface.

Action: Recheck the datasets being switched for this interface. Both datasets must be used in the interface.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15602: Dataset 2 was not found in the list of the datasets used with the interface.

Cause: An unimplemented method has been called. This is an ODI internal error.

Action: Do not call this method.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15603: Cannot create an alias for a datastore of type {0}

Cause: The method computeAliasForDataStore was called with an invalid datastore type.

Action: Only call computeAliasForDataStore for datastores of type TargetDataStore or OdiDataStore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15604: A non ordered clause was passed to the buildTreeSet method.

Cause: A non ordered clause is passed to the construction of ordered joins trees method.

Action: Use ordered join clauses with this method.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15605: Multiple ordered joins in this dataset use the same order number.

Cause: One or more join clauses uses the same order number in the call to buildTreeSet.

Action: Ensure that all clauses of an ordered join have unique order numbers.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15606: Join references the same table twice (directly or indirectly).

Cause: A join clause contains two references to the same table.

Action: Ensure that the join clause only references one table.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15607: Join references the same table twice through other joins.

Cause: A join clause contains two references to the same table.

Action: Ensure that the join clause only references one table.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15608: Subcomponent type of {0} is not supported.

Cause: An unsupported type was passed to getIssuesComputer.

Action: Only pass types of OdiInterface, DataSet, SourceDataStore, Filter, Join, StagingArea, TargetDataStore, SourceSet, TargetMapping, or TargetColumn.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15609: Invalid KM holder type: {0}

Cause: An invalid KM holder type was passed to InterfaceKMHolderFactory.getKMHolderFor

Action: Only pass KM holder types of SOURCE_SET_LKM, STAGING_AREA_LKM, TARGET_CKM, or TARGET_IKM.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15610: Component must be a source datastore or a source column.

Cause: ReferenceManagerAbstract.getReferencesTo was called with an invalid subcomponent.

Action: Only pass subcomponent types of SourceDataStore or ISourceColumn.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15611: Column not found from an xref.

Cause: A column referenced in an expression was not found in a datastore. It may have been deleted.

Action: Ensure that all columns referenced in the expression exist.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15612: Failed to attach an element of type {0} to a source set.

Cause: An invalid type of component was found when attaching elements to a source set.

Action: Elements being attached to a source set must be of type SourceDataStore, Join, Filter, or TargetMapping.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15613: Interface must have only one dataset.

Cause: This sourceset computer can only handle a single dataset, and more than one was found.

Action:
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15614: Interface must have only one source table.

Cause: This sourceset computer can only handle a single table, and more than one dataset was found.

Action:
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15615: Interface must not have joins.

Cause: This sourceset computer can only handle a single table, and the interface contains a join.

Action:
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15616: Source datastore must be a real table

Cause: This sourceset computer can only handle a single, real table.

Action:
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15617: Invalid type for a TextHolder: {0}

Cause: The method getExecutableTextHolderFor was called with an invalid TextHolder component type.

Action: Valid types are TargetMapping, TargetColumn, Filter, and Join.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15618: Cannot set a source set on a target column.

Cause: SetSourceSet was called for a target column, which is not a valid usage. This method is specified for the interface, but is not valid for this class.

Action: SetSourceSet should never be invoked for this class.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15619: Inconsistent filter with a clauseType of {0}

Cause: The Filter.getFilterType method was called, but the clause type was not a filter type.

Action: Ensure that the filter has a type of SnpPopClause.CLAUSE_TYPE_FILTER or SnpPopClause.CLAUSE_TYPE_JRN_FILTER.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15620: Execution location is null. Target technology cannot be determined

Cause: The execution filter for the location was not set.

Action: The execution location should be set in the Filter constructor or by invoking setExecutionLocation.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15621: Attached dataStore is null. Target technology cannot be determined

Cause: The attached datastore for the execution location was not set.

Action: The datastore should be set in the Filter constructor or by invoking setAttachedDataStore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15622: Staging area does not have a logical schema. Target technology cannot be determined

Cause: The attached datastore for the execution location was not set.

Action: The datastore should be set in the Filter constructor or by invoking setAttachedDataStore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15623: Invalid technology for the given index type

Cause: The technology of the clause and index type do not match.

Action: Ensure that the index type technology matches the clause technology.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15624: Inconsistent join with clauseType = {0} and joinType = {1}

Cause: The join clause type is invalid.

Action: This exception is thrown from a deprecated method. Use isCross or isOrdered methods instead.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15625: Cannot set OdiDataType on a journalized source column

Cause: The setDataType method has been invoked for a journalized source column, but the datatype cannot be set for journalized columns.

Action: Do not invoke this method for a journalized column.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15626: Cannot set the length on a journalized source column

Cause: The setLength method has been invoked for a journalized source column, but the length cannot be set for journalized columns.

Action: Do not invoke this method for a journalized column.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15627: Cannot set the scale on a journalized source column

Cause: The setScale method has been invoked for a journalized source column, but the scale cannot be set for journalized columns.

Action: Do not invoke this method for a journalized column.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15628: Cannot set the data type on a source column

Cause: The setDataType method has been invoked for a source column, but the datatype cannot be set for source columns.

Action: Do not invoke this method for a source column.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15629: Cannot set the length on a source column

Cause: The setLength method has been invoked for a source column, but the length cannot be set for source columns.

Action: Do not invoke this method for a source column.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15630: Cannot set the scale on a source column

Cause: The setScale method has been invoked for a source column, but the scale cannot be set for source columns.

Action: Do not invoke this method for a source column.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15631: Connection information is not available.

Cause: The physical schema has not been set.

Action: Define physical and logical schemas.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15632: Column {0} may not be removed because it is mapped in interface {1}.

Cause: The specified target column is mapped in another interface. This dependency prevents removal of the column.

Action: Only remove a column after mapping dependencies have been removed.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15633: Data Type must be set first.

Cause: Data Type is null.

Action: Set Data Type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15634: Length is not allowed for the current Data Type

Cause: Data Type doesn't support length.

Action: Check Data Type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15635: Scale is not allowed for the current Data Type.

Cause: Data Type doesn't support scale.

Action: Check Data Type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15636: Cannot change the column because it's not a temporary column.

Cause: Column isn't temporary.

Action: Check column state.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15637: Execution location must be either null or target.

Cause: Wrong Execution location state.

Action: Check Execution location.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15638: Scenario {0} contains invalid characters. Try {1}.

Cause: String contains invalid characters.

Action: Check scenario name.
Level: 32

Type: ERROR

Impact: Other

ODI-15639: Scenario version is not set.

Cause: Scenario version is not set.

Action: Set scenation version.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15640: No Scenario was found through the Tag : {0}.

Cause: No Scenario was found.

Action: Check tag.
Level: 32

Type: ERROR

Impact: Other

ODI-15641: The refresh SQL statement of a variable cannot contain sequence references when the variable is added to a load plan.

Cause: SQL statement contains sequence references.

Action: Check refresh SQL statement.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15642: Scenario name must be {0} characters long max.

Cause: Scenario name is too long.

Action: Check name length.
Level: 32

Type: ERROR

Impact: Other

ODI-15643: No Deployment Spec from Mapping: {0}.

Cause: Cannot find any Deployment Spec from Mapping.

Action: Check there is valid Deployment Spec.
Level: 32

Type: ERROR

Impact: Other

ODI-15644: The physical data server for the source code and for sequqnce(s) {0} is not the same, this may result in the same sequence value being used for each row.

Cause: The sequence may be remote so a single nextval is calculated and reused per row.

Action: Make sure the sequence and task have the same data server if you want the sequences to use distinct values per row.
Level: 32

Type: INFO

Impact: Other

ODI-15645: The physical data server for the target code and for sequence(s) {0} is not the same, this may result in the same sequence value being used for each row.

Cause: The sequence may be remote so a single nextval is calculated and reused per row.

Action: Make sure the sequence and task have the same data server if you want the sequences to use distinct values per row.
Level: 32

Type: INFO

Impact: Other

ODI-15700: Exception thrown in the Odi shortcut service: {0}

Cause: An exception was thrown while materializing a shortcut object.

Action: Check the root cause.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17500: Invalid old password.

Cause: Old password did not match current password.

Action: Provide the correct password.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17501: Temporary table has no column.

Cause: No column have been defined for the temporary table.

Action: Define a column mapping to the temporary table.
Level: 32

Type: ERROR

Impact: Other

ODI-17502: No next value returned.

Cause: No sequence next value was found for given context code.

Action: Verify sequence definition or context code.
Level: 32

Type: ERROR

Impact: Other

ODI-17503: Internal error: object ConnectConnection

Cause: Missed connection.

Action: Try reconnect.
Level: 32

Type: ERROR

Impact: Other

ODI-17504: An ordered join references the same table twice (directly or indirectly).

Cause: A same table was referenced twice by a join.

Action: Check interface definition.
Level: 32

Type: ERROR

Impact: Other

ODI-17505: An ordered join references the same table twice through another join.

Cause: A join was referencing the same table twice through another join.

Action: Check interface definition.
Level: 32

Type: ERROR

Impact: Other

ODI-17506: Variable has no value

Cause: Variable had no value.

Action: Provide value for variable.
Level: 32

Type: ERROR

Impact: Other

ODI-17507: Key does not exist

Cause: Key was unknown.

Action: Provide a known key.
Level: 32

Type: ERROR

Impact: Other

ODI-17508: No conversion for data type "{0}" from source technology "{1}" to destination technology "{2}"

Cause: No data type conversion between technology was found.

Action: Define corresponding data type conversion.
Level: 32

Type: ERROR

Impact: Other

ODI-17509: Query to access value for specific sequence {0} has failed. Query="{1}"

Cause: Query for sequence has failed.

Action: Check sequence definition.
Level: 32

Type: ERROR

Impact: Other

ODI-17510: Driver does not exist.

Cause: Driver was not found.

Action: Check repository.
Level: 32

Type: ERROR

Impact: Other

ODI-17511: No value to be set to variable ''{0}''.

Cause: No value was returned to be set to the variable.

Action: Check variable value.
Level: 32

Type: ERROR

Impact: Other

ODI-17512: Sequence is already locked

Cause: The sequence was already locked.

Action: Unlock the sequence.
Level: 32

Type: ERROR

Impact: Other

ODI-17513: Variable ''{0}'' does not exist.

Cause: Variable was not found.

Action: Check variable.
Level: 32

Type: ERROR

Impact: Other

ODI-17514: Unrecognized Oracle Data Integrator built-in function: {0}

Cause: Oracle Data Integrator built-in function was not recognized.

Action: Check function syntax.
Level: 32

Type: ERROR

Impact: Other

ODI-17515: Invalid loading command (INSERT,UPDATE...).

Cause: Loading command was invalid.

Action: Check loading command.
Level: 32

Type: ERROR

Impact: Other

ODI-17516: Internal error within the connection list

Cause: Internal error within the connection list.

Action: Try again.
Level: 32

Type: ERROR

Impact: Other

ODI-17517: Error during task interpretation. Task: {0} {1} Text: {2}.

Cause: A task interpretation error has occured.

Action: Check tasks and try again.
Level: 32

Type: ERROR

Impact: Other

ODI-17518: Error while interpreting the user name.

Cause: User name interpretation has failed.

Action: Check user name.
Level: 32

Type: ERROR

Impact: Other

ODI-17519: Error while interpreting the URL

Cause: URL interpretation has failed

Action: Check URL.
Level: 32

Type: ERROR

Impact: Other

ODI-17520: Error while interpreting the password

Cause: Password interpretation has failed.

Action: Check password.
Level: 32

Type: ERROR

Impact: Other

ODI-17521: Error while interpreting the driver

Cause: Driver interpretation has failed.

Action: Check driver.
Level: 32

Type: ERROR

Impact: Other

ODI-17522: Empty column name are not allowed

Cause: A empty column name was found.

Action: Fill column name.
Level: 32

Type: ERROR

Impact: Other

ODI-17523: There is no connection for this logical schema / context pair: {0} / {1}.

Cause: No connection was found for this logical schema / context pair.

Action: Check schema and context assignment.
Level: 32

Type: ERROR

Impact: Other

ODI-17524: Cannot set an empty alias for a source table.

Cause: Source table''s alias was empty.

Action: Fill alias of source table.
Level: 32

Type: ERROR

Impact: Other

ODI-17525: Cannot set an empty source set name.

Cause: Source set name was empty.

Action: Fill alias of a source table.
Level: 32

Type: ERROR

Impact: Other

ODI-17526: Cannot set Longc value in a PopCol having a column

Cause: Cannot set Longc value in a PopCol having a column.

Action: Check interface`s columns.
Level: 32

Type: ERROR

Impact: Other

ODI-17527: Cannot set SourceDt value in a PopCol having a column

Cause: Cannot set SourceDt value in a PopCol having a column.

Action: Check interface`s columns.
Level: 32

Type: ERROR

Impact: Other

ODI-17528: Cannot set Scalec value in a PopCol having a column

Cause: Cannot set Scalec value in a PopCol having a column.

Action: Check interface`s columns.
Level: 32

Type: ERROR

Impact: Other

ODI-17529: Reference check failure

Cause: Reference check has failed.

Action: Check control conditions.
Level: 32

Type: ERROR

Impact: Other

ODI-17530: Incomplete join may result in partial cross join

Cause: An incomplete join was found.

Action: Check joins.
Level: 32

Type: ERROR

Impact: Other

ODI-17531: KM already encrypted.

Cause: KM has been already encrypted.

Action: Skip encryption.
Level: 32

Type: ERROR

Impact: Other

ODI-17532: KM not encrypted.

Cause: KM was not encrypted.

Action: Check KM.
Level: 32

Type: ERROR

Impact: Other

ODI-17533: Clause set to cross join on a technology that does not support cross joins.

Cause: Technology did not support cross joins.

Action: Correct joins.
Level: 32

Type: ERROR

Impact: Other

ODI-17534: Clause set to full join on a technology that does not support full joins.

Cause: Technology did not support full joins.

Action: Correct joins.
Level: 32

Type: ERROR

Impact: Other

ODI-17535: Clause set to outer join on a technology that does not support left outer joins or right outer joins.

Cause: Technology did not support left outer joins.

Action: Correct joins.
Level: 32

Type: ERROR

Impact: Other

ODI-17536: Incomplete clause (Missing order number).

Cause: Order number was missing.

Action: Correct clause.
Level: 32

Type: ERROR

Impact: Other

ODI-17537: Incomplete clause (table1 and/or table2 must be set).

Cause: Table1 and/or table2 were undefined.

Action: Set clause''s table1 and/or table2 tables.
Level: 32

Type: ERROR

Impact: Other

ODI-17538: Filter is not properly set (The table must be defined)

Cause: The table must have been set.

Action: Set filter''s table.
Level: 32

Type: ERROR

Impact: Other

ODI-17539: Clause is ordered on a technology that does not support it

Cause: Technology did not support ordering.

Action: Remove ordering.
Level: 32

Type: ERROR

Impact: Other

ODI-17540: Connection is not set for this source set {0}.

Cause: Source set''s connection was not set.

Action: Set connection.
Level: 32

Type: ERROR

Impact: Other

ODI-17541: Method SnpTrt::getAllTrtOfTypeForTechnosAndProject requires not null parameters for technologies

Cause: Method requires not null parameters

Action: Specify correct parameters.
Level: 32

Type: ERROR

Impact: Other

ODI-17542: Sequence must be locked before using this function

Cause: Sequence was not locked.

Action: Lock sequence and try again.
Level: 32

Type: ERROR

Impact: Other

ODI-17543: Technology does not support joins

Cause: Technology did not support joins.

Action: Check technology and/or joins.
Level: 32

Type: ERROR

Impact: Other

ODI-17544: This Technology does not support the WHERE clause

Cause: Technology did not support the WHERE clause

Action: Check technology and/or clause.
Level: 32

Type: ERROR

Impact: Other

ODI-17545: Technology not set for this source set {0}

Cause: Source set''s technology was undefined.

Action: Set technology.
Level: 32

Type: ERROR

Impact: Other

ODI-17546: Specified variable not found in the Repository

Cause: Variable was not found in the Repository.

Action: Define variable and try again.
Level: 32

Type: ERROR

Impact: Other

ODI-17547: Data type "{0}" for the technology "{1}" does not exist.

Cause: Data type for the technology did not exist.

Action: Check data type and/or technology.
Level: 32

Type: ERROR

Impact: Other

ODI-17548: The file reverse-engineering is only possible for delimited files.

Cause: The file reverse-engineering was performed against a not delimited file.

Action: Use delimited files.
Level: 32

Type: ERROR

Impact: Other

ODI-17549: Source data type "{0}" for the technology "{1}" does not exist.

Cause: Source data type was not found.

Action: Check data type and/or technology.
Level: 32

Type: ERROR

Impact: Other

ODI-17550: Missing default Physical Schema for Data Server "{0}"

Cause: Default Physical Schema was undefined.

Action: Specify default Physical Schema.
Level: 32

Type: ERROR

Impact: Other

ODI-17551: Duplicate clause order numbers

Cause: Duplicated order numbers were found.

Action: Check clause definition.
Level: 32

Type: ERROR

Impact: Other

ODI-17552: Duplicate join order numbers

Cause: Duplicated join order numbers were found.

Action: Check join.
Level: 32

Type: ERROR

Impact: Other

ODI-17553: Exceeded the maximum number of errors allowed.

Cause: The maximum number of errors allowed were exceeded.

Action: Check maximum error numbers.
Level: 32

Type: ERROR

Impact: Other

ODI-17554: Agent "{0}" does not exist.

Cause: Agent was not found.

Action: Check agent definition.
Level: 32

Type: ERROR

Impact: Other

ODI-17555: You cannot unlock this object. Only the lock owners and Supervisors can unlock objects.

Cause: An attempt was made to unlock objects that were locked by another user.

Action: Login as Supervisor or as the lock owners and try again.
Level: 32

Type: ERROR

Impact: Other

ODI-17556: Error during decryption of text.

Cause: Text decryption has failed.

Action: Try again.
Level: 32

Type: ERROR

Impact: Other

ODI-17557: No condition defined for this rule.

Cause: No condition have been defined for this rule.

Action: Define conditions.
Level: 32

Type: ERROR

Impact: Other

ODI-17558: The field for this rule is not specified.

Cause: The field was unspecified.

Action: Specify field for this rule.
Level: 32

Type: ERROR

Impact: Other

ODI-17559: The operator for this rule is not specified.

Cause: The operator was unspecified.

Action: Specify operator for this rule.
Level: 32

Type: ERROR

Impact: Other

ODI-17560: The value to test is not defined.

Cause: The value to test was not defined.

Action: Specify value.
Level: 32

Type: ERROR

Impact: Other

ODI-17561: This operator is not supported.

Cause: This operator was not supported.

Action: Correct operator.
Level: 32

Type: ERROR

Impact: Other

ODI-17562: This operator cannot be used with this field.

Cause: The operator could not be used with the given field.

Action: Correct operator.
Level: 32

Type: ERROR

Impact: Other

ODI-17563: There is no work repository matching the name "{0}".

Cause: Work repository was not found.

Action: Check work repository with the given name exists.
Level: 32

Type: ERROR

Impact: Other

ODI-17564: More than one work repository found with the name "{0}" for this master repository.

Cause: More than one work repository with the specified name was found for this master repository.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-17565: Scenario has been already encrypted. No encryption was performed.

Cause: Scenario has been already encrypted.

Action: Decrypt and try again.
Level: 32

Type: ERROR

Impact: Other

ODI-17566: Scenario is not encrypted. No decryption was performed.

Cause: Scenario was not encrypted.

Action: Check Scenario.
Level: 32

Type: ERROR

Impact: Other

ODI-17567: A Scenario generated from a Variable cannot be encrypted or decrypted.

Cause: An attempt was made to encrypte or decrypte a Scenario generated from a Variable.

Action: Change Scenario'' source component.
Level: 32

Type: ERROR

Impact: Other

ODI-17568: Could not connect to the database referenced by the context and the logical schema

Cause: Connection to the database failed.

Action: Check context and logical schema.
Level: 32

Type: ERROR

Impact: Network

ODI-17569: Unable to update sequence''s next value.

Cause: Updating sequence was not possible.

Action: Check sequence definition.
Level: 32

Type: ERROR

Impact: Other

ODI-17570: Your text is too long. Please shorten it or choose the ''LONG TEXT'' datatype.

Cause: Text was too long.

Action: Shorten the text or choose the LONG TEXT data type.
Level: 32

Type: ERROR

Impact: Other

ODI-17571: Password does not respect the following rule: "{0}".

Cause: The password did not respect the rule.

Action: Choose another password.
Level: 32

Type: ERROR

Impact: Security

ODI-17572: This SnpFfValuee does not exist.

Cause: Value was not found.

Action: Check FlexField value.
Level: 32

Type: ERROR

Impact: Other

ODI-17573: This SnpFfValuem does not exist.

Cause: Value was not found.

Action: Check FlexField value.
Level: 32

Type: ERROR

Impact: Other

ODI-17574: This SnpFfValuew does not exist.

Cause: Value was not found.

Action: Check FlexField value.
Level: 32

Type: ERROR

Impact: Other

ODI-17575: SnpLicense does not exist.

Cause: SnpLicense was not found.

Action: Check License.
Level: 32

Type: ERROR

Impact: Other

ODI-17576: Unknown actual constraint type for an interface constraint.

Cause: Interface constraint type was unknown.

Action: Check constraint type.
Level: 32

Type: ERROR

Impact: Other

ODI-17577: Unknown variable data type.

Cause: Variable data type was unknown.

Action: Check variable data type.
Level: 32

Type: ERROR

Impact: Other

ODI-17578: Name "{0}" is already used.

Cause: Name was already used.

Action: Use another name or change mode of import.
Level: 32

Type: ERROR

Impact: Other

ODI-17579: Type of clause is not set.

Cause: Type of clause was not set.

Action: Set type of clause.
Level: 32

Type: ERROR

Impact: Other

ODI-17580: Type of join is not set.

Cause: Type of join was not set.

Action: Set type of join.
Level: 32

Type: ERROR

Impact: Other

ODI-17581: A non ordered clause is passed to the construction of ordered joins trees method.

Cause: A non ordered clause was passed to the construction of ordered joins trees method.

Action: Check clauses.
Level: 32

Type: ERROR

Impact: Other

ODI-17582: Missing order number for an ordered clause.

Cause: Clause order was not set.

Action: Set the clause order.
Level: 32

Type: ERROR

Impact: Other

ODI-17583: More than one unique constraint associated to an interface constraint.

Cause: More than one unique constraint associated to an interface constraint was found.

Action: Check constraints.
Level: 32

Type: ERROR

Impact: Other

ODI-17584: URL does not exist.

Cause: URL was not found.

Action: Check URL.
Level: 32

Type: ERROR

Impact: Other

ODI-17585: Key cannot be checked.

Cause: Key could not be checked.

Action: Check key definition.
Level: 32

Type: ERROR

Impact: Other

ODI-17586: Field separator is mandatory for a delimited file.

Cause: Field separator was missing.

Action: Check separator and/or file type.
Level: 32

Type: ERROR

Impact: Other

ODI-17587: Object name "{0}" is too long for the technology "{1}" (Logical schema : "{2}" ; Context Code : "{3}")

Cause: Object name was too long.

Action: Correct object name.
Level: 32

Type: ERROR

Impact: Other

ODI-17588: Unable to load work repository info.

Cause: Work repository was not found.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-17589: Logical schema has not been specified for sequence "{0}"

Cause: Logical schema was not specified.

Action: Specify logical schema.
Level: 32

Type: ERROR

Impact: Other

ODI-17590: Code {0} for model "{1}" is already used by another model.

Cause: An already used code was assigned.

Action: Change code for model.
Level: 32

Type: ERROR

Impact: Other

ODI-17591: Name "{0}" is already used.

Cause: A name already used was assigned.

Action: Change name.
Level: 32

Type: ERROR

Impact: Other

ODI-17592: Object is not in execution work repository.

Cause: Object was not in execution work repository.

Action: Check object and/or repository.
Level: 32

Type: ERROR

Impact: Other

ODI-17593: Maximum number or source/target technologies exceeded. Current limit is {0}.

Cause: Maximum number or source/target technologies was exceeded.

Action: Check limit and number of technologies.
Level: 32

Type: ERROR

Impact: Other

ODI-17594: Cannot encrypte already encrypted action.

Cause: This action has been already encrypted.

Action: Skip encryption.
Level: 32

Type: ERROR

Impact: Other

ODI-17595: This action is not encrypted.

Cause: This action was not encrypted.

Action: Check parameters and try again.
Level: 32

Type: ERROR

Impact: Other

ODI-17596: Query to retrieve value for native sequence "{0}" has failed Query="{1}"

Cause: Query has failed.

Action: Check query.
Level: 32

Type: ERROR

Impact: Other

ODI-17597: Cannot mix ordered and non-ordered join syntax within a dataset for technology.

Cause: Mixed join not allowed within a dataset.

Action: Change all joins in dataset to same join syntax (either ordered or non-ordered).
Level: 32

Type: ERROR

Impact: Other

ODI-17598: Non-ordered natural join is not supported.

Cause: Non-ordered natural join is not supported.

Action: Change natural join to use ordered syntax.
Level: 32

Type: ERROR

Impact: Other

ODI-17599: Ordered inner join is not supported.

Cause: Ordered inner join is disabled for technology.

Action: Change join type.
Level: 32

Type: ERROR

Impact: Other

ODI-17600: Ordered left outer join is not supported.

Cause: Ordered left outer join is disabled for technology.

Action: Change join type.
Level: 32

Type: ERROR

Impact: Other

ODI-17601: Ordered right outer join is not supported.

Cause: Ordered right outer join is disabled for technology.

Action: Change join type.
Level: 32

Type: ERROR

Impact: Other

ODI-17602: Non-ordered full outer join is not supported.

Cause: Non-ordered full outer join is not supported.

Action: Change full outer join to use ordered syntax.
Level: 32

Type: ERROR

Impact: Other

ODI-17603: Sql error checking a condition. {0}

Cause: Sql error checking a condition.

Action: Correct the Sql in the condition.
Level: 32

Type: ERROR

Impact: Other

ODI-17604: Reference column isn't associated with this instance of reference.

Cause: Reference column isn't associated with this instance of reference.

Action: Check reference column.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17605: Column is not associated to this datastore.

Cause: Datastore doesn't have this column.

Action: Check datastore and column.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17606: {0} already belongs to another OdiDataStore.

Cause: Object belongs to another datastore.

Action: Check object and datastore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17607: Parameter pReference is not an outbound reference for this OdiDataStore.

Cause: Parameter is not an outbound reference for OdiDataStore.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17608: Invalid technology for the given data type.

Cause: Invalid technology for the given data type.

Action: Check technology.
Level: 32

Type: ERROR

Impact: Other

ODI-17609: Invalid data type code.

Cause: Invalid data type code.

Action: Check data type code.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17610: Found NULL in STEP_TYPE.

Cause: Step type is null.

Action: Check step type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17611: STEP_TYPE is not valid.

Cause: Step type isn't valid.

Action: Check step type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17612: MultiConnectionSupported is not settable for {0}.

Cause: MultiConnectionSupported is not settable.

Action: Check knowledge module.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17613: Cannot handle {0} of type {1}.

Cause: Cannot handle object.

Action: Check object's type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17614: Unknown key type: {0}.

Cause: Unknown key type.

Action: Check key.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17615: The command is not an ODI Tool command.

Cause: Wrong command.

Action: Check command.
Level: 32

Type: ERROR

Impact: Other

ODI-17616: No WorkTextOrig was found for ID: {0}.

Cause: Invalid ID.

Action: Check ID.
Level: 32

Type: ERROR

Impact: Other

ODI-17617: Class descriptor for WorkTextOrig [ {0} ] is null.

Cause: Descriptor is null.

Action: Check class descriptors.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17618: Unable to deal with an AliasedColumnCrossRef with type {0}.

Cause: Incorrect column type.

Action: Check column type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17619: Unexpected CrossRef {0} type.

Cause: Incorrect CrossRef type.

Action: Check CrossRef.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17620: Object type is not valid.

Cause: Object type is not valid.

Action: Check object type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17621: Unable to manage crossRef for object from class [ {0} ].

Cause: Illegal object type.

Action: Check object type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17622: pSqlIndGroup is not a valid group type.

Cause: Invalid group type.

Action: Check type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17623: Too many parameters for function {0}, Object {1}, Language {2}.

Cause: Too many parameters.

Action: Check parameters count.
Level: 32

Type: ERROR

Impact: Other

ODI-17624: Missing parameter for function {0}, Object {1}, Language {2}.

Cause: Missing parameter.

Action: Check parameters count.
Level: 32

Type: ERROR

Impact: Other

ODI-17625: Only OdiColumns are currently supported for SnpsExpressionTag.

Cause: Wrong column type.

Action: Check column type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17626: Cannot reassign a DataType.

Cause: Technology has been assigned yet.

Action: Check DataType
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17627: Inconsistent connection settings.

Cause: Inconsistent connection settings.

Action: Check connection settings type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17628: Unknown IConnectionSettings implementation.

Cause: Unknown IConnectionSettings implementation.

Action: Check settings type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17629: Connection Settings for repository server must be instanceof JdbcSettings.

Cause: Wrong settings type.

Action: Check settings type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17630: Unknown OptionType.

Cause: Unknown OptionType.

Action: Check option type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17631: The given class has no matching OverridenOptionOrig.

Cause: The given class has no matching OverridenOptionOrig.

Action: Check class.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17632: Unexpected variable type.

Cause: Unexpected variable type.

Action: Check variable type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17633: {0} datatype is expected.

Cause: Wrong value datatype.

Action: Check value datatype.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17634: Parameter must have text; it must not be null or empty.

Cause: Wrong parameter value.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17635: Parameter must have text; it must not be null, empty, or blank.

Cause: Wrong parameter value.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17636: Parameter {0} must be false.

Cause: Wrong parameter value.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17637: Parameter must not be null.

Cause: Wrong parameter value.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17638: Parameter {0} must be null.

Cause: Wrong parameter value.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17639: Parameter must be null.

Cause: Wrong parameter value.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17640: Parameter {0} must have text; it must not be null or empty.

Cause: Wrong parameter value.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17641: No {0} matches this IObject: {1}.

Cause: IObject is not matched.

Action: Check class.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17642: No Entity Class matches this Snp Class: {0}.

Cause: No Entity Class matches Snp Class.

Action: Check Entity Class.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17643: No Snp Class matches this Entity Class: {0}.

Cause: No Snp Class matches Entity Class.

Action: Check Snp Class.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17644: Unknown FlexFieldType.

Cause: Unknown FlexFieldType.

Action: Check FlexFieldType type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17645: Parameter must be instance of {0}.

Cause: Wrong parameter type.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17646: It is forbidden to use a variable of one project in a package of another project.

Cause: Variable and package have different parents.

Action: Check variable and package.
Level: 32

Type: ERROR

Impact: Other

ODI-17647: Unable to create the expression element, Object {0}, Language {1}.

Cause: Unable to create the expression element.

Action: Check expression parameters.
Level: 32

Type: ERROR

Impact: Other

ODI-17648: A mapping cannot be on the target.

Cause: A mapping cannot be on the target.

Action: Check execution location.
Level: 32

Type: ERROR

Impact: Other

ODI-17649: Can't create join between 2 source datastore from different DataSet.

Cause: Source datastores are from different DataSet.

Action: Correct join.
Level: 32

Type: ERROR

Impact: Other

ODI-17650: A {0} was expected as value since {1} is {2}.

Cause: Wrong type.

Action: Check type.
Level: 32

Type: ERROR

Impact: Other

ODI-17651: Parameter {0} must be instance of [{1}].

Cause: Wrong parameter class.

Action: Check parameter class.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17652: Class {0} is not assignable to {1}.

Cause: Inconsistent classes.

Action: Check classes.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17653: {0} line isn't found.

Cause: Missed line.

Action: Check line count.
Level: 32

Type: ERROR

Impact: Other

ODI-17654: Parameter {0} must be not null.

Cause: Parameter must be not null.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17655: Parameter {0} must be {1} characters long max.

Cause: Parameter length is too long.

Action: Check parameter length.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17656: Can't define variable override for steps in exception tree.

Cause: Step is in exception tree.

Action: Check step and variable for consistency.
Level: 32

Type: ERROR

Impact: Other

ODI-17657: Cannot add a reference column to an OdiReference with type [{0}].

Cause: Reference type isn't ReferenceType.COMPLEX_REFERENCE.

Action: Check reference type.
Level: 32

Type: ERROR

Impact: Other

ODI-17658: Cannot change the target table because it's not a temporary datastore.

Cause: Datastore isn't temporary.

Action: Check target table and datastore.
Level: 32

Type: ERROR

Impact: Other

ODI-17659: Cannot get the journalized columns of a non-journalized datastore.

Cause: Datastore isn't journalized.

Action: Check datastore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17660: Cannot set a clause on the target.

Cause: Wrong execution location.

Action: Check execution location.
Level: 32

Type: ERROR

Impact: Other

ODI-17661: {0} is not supported for this Technology.

Cause: Object is not supported for this Technology.

Action: Check topology.
Level: 32

Type: ERROR

Impact: Other

ODI-17662: Parameter {0} must have text; it must not be null, empty, or blank.

Cause: Incorrect parameter.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17663: Parameter {0} must be uppercase.

Cause: Parameter is lower case.

Action: Check parameter case.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17664: Parameter {0} must not contain whitespaces.

Cause: Parameter contains whitespaces.

Action: Consider to replace whitespace with another symbold (e.g. underscore)
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17665: Column is not associated with this instance of OdiKey.

Cause: Column is not associated with instance of OdiKey.

Action: Check column and OdiKey.
Level: 32

Type: ERROR

Impact: Other

ODI-17666: Column is not present in the key.

Cause: Column is not present in the key.

Action: Check column and key.
Level: 32

Type: ERROR

Impact: Other

ODI-17667: Data type should be set before accessing value.

Cause: Illegal method usage.

Action: Set Data type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17668: Datastore already has a Primary Key.

Cause: Datastore already has a Primary Key.

Action: Remove the current primary key before adding a new one.
Level: 32

Type: ERROR

Impact: Other

ODI-17669: {0} must be set before calling method {1}.

Cause: Illegal method usage.

Action: Set actual value.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17670: Default implementation already exists.

Cause: Default implementation already exists.

Action: Check function implementation.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17671: {0} must not be negative.

Cause: Wrong parameter value.

Action: Set value to 0 or greater.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17672: FlexFields isn''t initialized.

Cause: FlexFields isn''t initialized.

Action: Call initFlexFields method first.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17673: Foreign key column''s datastore must be equals to this reference''s foreign datastore.

Cause: Inconsistent datastores.

Action: Check datastore.
Level: 32

Type: ERROR

Impact: Other

ODI-17674: IncrementValue is not set.

Cause: IncrementValue is not set.

Action: Set IncrementValue with setVariable method.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17675: Invalid step log's status.

Cause: Step status is not RUNNING.

Action: Check step status.
Level: 32

Type: ERROR

Impact: Other

ODI-17676: Invalid value type.

Cause: Invalid value type.

Action: Check value type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17677: Cycle could be defined in {0} hierarchy.

Cause: It is forbidden to define cycle in {0} hierarchy.

Action: Check hierarchy.
Level: 32

Type: ERROR

Impact: Other

ODI-17678: It is forbidden to fill a key with columns from another datastore.

Cause: It is forbidden to fill a key with columns from another datastore.

Action: Check datastore.
Level: 32

Type: ERROR

Impact: Other

ODI-17679: It is forbidden to link two steps from different packages.

Cause: Steps are from different packages.

Action: Check steps and packages.
Level: 32

Type: ERROR

Impact: Other

ODI-17680: Line wasn't found.

Cause: Line wasn't found.

Action: Check procedure lines.
Level: 32

Type: ERROR

Impact: Other

ODI-17681: Maximum number of sessions must be positive.

Cause: Wrong value.

Action: Check maximum number.
Level: 32

Type: ERROR

Impact: Other

ODI-17682: Method is not valid unless MultiConnectionSupported.

Cause: MultiConnectionSupported is true.

Action: Check procedure.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17683: Model must be in Customized mode.

Cause: Wrong model mode.

Action: Call setReverseType(ReverseType.CUSTOMIZED).
Level: 32

Type: ERROR

Impact: Other

ODI-17684: Name can't be set.

Cause: Name is computed.

Action: Check name.
Level: 32

Type: ERROR

Impact: Other

ODI-17685: No {0} is defined for this model.

Cause: Missed definition.

Action: Define CKM for model.
Level: 32

Type: ERROR

Impact: Other

ODI-17686: No valid {0} name was found from this qualified name.

Cause: Valid name wasn't found.

Action: Check qualified name.
Level: 32

Type: ERROR

Impact: Other

ODI-17687: No valid qualified name was provided.

Cause: Name is invalid.

Action: Check qualified name.
Level: 32

Type: ERROR

Impact: Other

ODI-17688: OdiScenario is undefined.

Cause: OdiScenario is undefined.

Action: Check OdiScenario definition.
Level: 32

Type: ERROR

Impact: Other

ODI-17689: Option must be in the same procedure as line.

Cause: Option procedure is inconsistent.

Action: Check option procedure.
Level: 32

Type: ERROR

Impact: Other

ODI-17690: Package and procedure must be owned by the same project.

Cause: Procedure parent is inconsistent.

Action: Check procedure parent.
Level: 32

Type: ERROR

Impact: Other

ODI-17691: Primary key column's datastore must be equals to this reference's primary datastore.

Cause: Column datastore is inconsistent.

Action: Check datastores.
Level: 32

Type: ERROR

Impact: Other

ODI-17692: Reference column doesn't belong to this reference.

Cause: Column is inconsistent.

Action: Check column.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17693: Reference's foreign datastore is not equal to this datastore.

Cause: Datastores are inconsistent.

Action: Check datastores.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17694: Steps can't be moved from one package to another.

Cause: Steps can't be moved from one package to another.

Action: Conside not to move steps.
Level: 32

Type: ERROR

Impact: Other

ODI-17695: The new position is not valid.

Cause: The new position is not valid.

Action: Check new position.
Level: 32

Type: ERROR

Impact: Other

ODI-17696: The option already exists.

Cause: The option already exists.

Action: Check option.
Level: 32

Type: ERROR

Impact: Other

ODI-17697: The option owner has already been set.

Cause: The option owner has already been set.

Action: Check option owner.
Level: 32

Type: ERROR

Impact: Other

ODI-17698: The reference type must be [ {0} ] in order to define a complex SQL expression.

Cause: Wrong reference type.

Action: Check reference type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17699: The reference type must be [ {0} ] in order to obtain the complex SQL expression.

Cause: Wrong reference type.

Action: Check reference type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17700: The string value length should not exceed MAX_SHORT_TEXT_LENGTH since FlexFieldType is SHORT_TEXT.

Cause: FlexFieldType is SHORT_TEXT.

Action: Check FlexFieldType and string value length.
Level: 32

Type: ERROR

Impact: Other

ODI-17701: This OdiLoadPlanInstanceRun is not ESS Job related.

Cause: OdiLoadPlanInstanceRun is not ESS Job related.

Action: Check OdiLoadPlanInstanceRun.
Level: 32

Type: ERROR

Impact: Other

ODI-17702: This session is not ESS Job related.

Cause: Session is not ESS Job related.

Action: Check session.
Level: 32

Type: ERROR

Impact: Other

ODI-17703: This OdiReference must be from type [{0}] in order to access the primary DataStore alias.

Cause: Wrong OdiReference type.

Action: Check OdiReference type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17704: This OdiReference must be from type [{0}] in order to set the primary DataStore alias.

Cause: Wrong OdiReference type.

Action: Check OdiReference type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17705: This file descriptor is not consistent with the parent model's technology.

Cause: File descriptor is not consistent.

Action: Check file descriptor and parent technology.
Level: 32

Type: ERROR

Impact: Other

ODI-17706: This setVariable is used for increment.

Cause: Increment value is set.

Action: Use method getIncrementValue().
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17707: Unable to add an alien main partition.

Cause: Main partition datastore is inconsistent.

Action: Check main partition.
Level: 32

Type: ERROR

Impact: Other

ODI-17708: Unable to compute name.

Cause: Name has been set on this physical schema.

Action: Do not compute name.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17709: Parameter must be false.

Cause: Wrong parameter value.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17710: Parameter {0} must be true.

Cause: Wrong parameter value.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17711: Undefined ODI work repository name.

Cause: Undefined repository name.

Action: Check repository name.
Level: 32

Type: ERROR

Impact: Other

ODI-17712: Variable and Step should be defined in the same Load Plan.

Cause: Variable and Step have different parent Load Plans.

Action: Define variable and step in the same Load Plan.
Level: 32

Type: ERROR

Impact: Other

ODI-17713: VariableDataType should be set before accessing DefaultValue.

Cause: VariableDataType is undefined.

Action: Set VariableDataType.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17714: You can only set KMs contained in the OdiProject containing of the OdiInterface.

Cause: KM has different parent project than OdiInterface.

Action: Check KM.
Level: 32

Type: ERROR

Impact: Other

ODI-17715: Can't add a null variable to load plan.

Cause: Variable is null.

Action: Check variable value.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17716: DataTypes must be consistent.

Cause: DataTypes is inconsistent.

Action: Check DataTypes.
Level: 32

Type: ERROR

Impact: Other

ODI-17717: Constraint is not a condition.

Cause: Inconsistent constraint type.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17718: Constraint is not a key.

Cause: Inconsistent constraint type.

Action: Check constraint.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17719: Option is not associated to this procedure.

Cause: Option is not associated to this procedure.

Action: Check option and procedure.
Level: 32

Type: ERROR

Impact: Other

ODI-17720: Constraint is not a reference.

Cause: Inconsistent constraint type.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17721: Parameter {0} already belongs to {1}.

Cause: Parameter has parent.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17722: Parameter {0} does not belong to this instance of {1}.

Cause: Parameter has different parent.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17723: Parameter {0} must belong to this {1}.

Cause: Parameter parent is inconsistent.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17724: Parameter {0} can't be moved to an other {1}.

Cause: Parameter can't be moved.

Action: Do not move parameter.
Level: 32

Type: ERROR

Impact: Other

ODI-17725: Parameter {0} must start with {1} prefix.

Cause: Parameter has wrong prefix.

Action: Check parameter prefix.
Level: 32

Type: ERROR

Impact: Other

ODI-17726: Logical Agent {0} must be mapped to a Physical Agent in the ContextCode {1}.

Cause: Agent is null.

Action: Check agents.
Level: 32

Type: ERROR

Impact: Other

ODI-17727: pDataServiceContainer is not a data service.

Cause: pDataServiceContainer is not a data service.

Action: Check pDataServiceContainer.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17728: Package and interface must be owned by the same project.

Cause: Package and interface have different parents.

Action: Check package and interface.
Level: 32

Type: ERROR

Impact: Other

ODI-17729: Parameter must be true.

Cause: Wrong parameter value.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17730: Not legal for shortcut.

Cause: Object is shortcut.

Action: Use getShortcutBaseObject() to access the real object.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17731: Not legal to construct a shortcut from a datastore in a model with a different technology.

Cause: Inconsistent technologies.

Action: Check model and datastore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17732: Odi object Must be shortcut after materialize.

Cause: Object isn't shortcut.

Action: Check object.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17733: Reference's primary datastore must be not null in order to define a ReferenceColumn.

Cause: Primary DataStore is null.

Action: Check DataStore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17734: pDataServiceContainer {0} has no technology defined.

Cause: Data Service Container has no technology defined.

Action: Define technology.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17735: Reference's foreign datastore is not equals to this datastore.

Cause: Reference's foreign datastore is not equals to this datastore.

Action: Check DataStores.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17736: You can only set global KMs or KMs contained in the OdiProject containing the OdiInterface.

Cause: Wrong KM.

Action: Check KM and project.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17737: StepLog and Variable don't belong to the same session.

Cause: Inconsistent session.

Action: Check Session value for StepLog and Variable.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17738: Unable to find '{0}' as variable used by the scenario '{1}' in version '{2}'.

Cause: Variable is null.

Action: Check variable name.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17739: Unable to override '{0}' variable for execution. It is marked as read-only for scenario '{1}' in version '{2}'.

Cause: Variable is read-only.

Action: Check variable.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17740: Error while connecting to the Application Server at URL {0}.

Cause: Exception was thrown during connection.

Action: Ensure that the Application Server is running and accepting requests.
Level: 32

Type: ERROR

Impact: Network

ODI-17741: Datastore isn't used as a lookup source.

Cause: Datastore isn't used as a lookup source.

Action: Check Datastore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17742: Parameter {0} must be greater or equal than {1} and less or equal than {2}.

Cause: Wrong parameter value

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17743: Variable should be related to the same {0}.

Cause: Wrong parent for variable.

Action: Check variable.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17744: The status can only be switched from ERROR to DONE or from DONE to ERROR.

Cause: Wrong status

Action: Check status.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17745: Parameter {0} must be greater or equal than {1}.

Cause: Wrong parameter value.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17746: Parameter {0} must be greater than {1}.

Cause: Wrong parameter value.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17747: Array {0} must not be empty.

Cause: Array length is 0.

Action: Check array.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17748: Parameter {0} is not relevant to this schedule.

Cause: Wrong parameter.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17749: Invalid value was specified. Cannot create {0} with the value {1}.

Cause: Invalid value was specified.

Action: Check value.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17750: Parent folder already has the release tag set.

Cause: Setting the release tag when the parent already has the release tag set.

Action: Set the release tag in parent.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17751: Shortcut and the base object are under same folder.

Cause: Cannot create shortcut {0} with the base object under same folder {1}.

Action: Create shortcut in different folder.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17752: Shortcut and the base object are in different projects.

Cause: Cannot create shortcut {0} in project {1} which is different from the project of the base object.

Action: Create shortcut in same project as the base object.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17753: Shortcut with same reference object in same folder.

Cause: There is other shortcut object with same reference object as {0} in the same folder.

Action: Create shortcut in different folder.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17754: Shortcut and the base object are under same model.

Cause: Cannot create shortcut {0} with the base object under same model {1}.

Action: Create shortcut in different model.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17755: Shortcut with same reference object in same model.

Cause: There is other shortcut object with same reference object as {0} in the same model.

Action: Create shortcut in different model.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17756: Scenario "{0}", which is referenced by RunScenario step "{1}", has variable "{2}" but LoadPlan does not have variable with the same name.

Cause: Missed variable in Load Plan

Action: Check Load Plan''s variables.
Level: 32

Type: WARNING

Impact: Programmatic

ODI-17757: Scenario "{0}", which is referenced by RunScenario step "{1}", has a newer version "{2}" in the repository

Cause: Scenario has newer version.

Action: Consider to use latest version.
Level: 32

Type: NOTIFICATION

Impact: Programmatic

ODI-17758: LoadPlan Variable "{0}" SQL is different than the design repository Variable "{1}" SQL.

Cause: Variable's SQL was redefined.

Action: Check LoadPlan's variable.
Level: 32

Type: NOTIFICATION

Impact: Programmatic

ODI-17759: LoadPlan Variable "{0}" LogicalSchema "{1}" is different than the design repository Variable "{2}" LogicalSchema "{3}".

Cause: Variable's Logical Schema was redefined.

Action: Check LoadPlan's variable.
Level: 32

Type: NOTIFICATION

Impact: Programmatic

ODI-17760: Exception "{0}" is not used in the Load Plan.

Cause: Exception is not used.

Action: Consider to delete or disable unused exception.
Level: 32

Type: NOTIFICATION

Impact: Programmatic

ODI-17761: LoadPlan Variable "{0}" is refreshed at step "{1}", but it has no SQL.

Cause: LoadPlan Variable doesn't have refresh SQL.

Action: Check variable''s SQL or disable variable refreshing.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17762: Context is specified on a step "{0}", but it''s no longer present in the topology.

Cause: Context was removed.

Action: Check step's context.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17763: Logical Agent is specified on a step "{0}", but it is no longer present in the topology

Cause: Logical Agent was removed.

Action: Check step's Logical Agent.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17764: Context "{0}" and Logical agent "{1}" on a step "{2}" does not map to any physical agent.

Cause: Physical Agent doesn''t exist.

Action: Check agents'' mapping.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17765: Scenario variable "{0}" type and LoadPlan variable "{1}" type mismatch.

Cause: Variables have different datatype.

Action: Check variables.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17766: Scenario "{0}" wasn''t found.

Cause: Scenario doesn''t exist

Action: Check scenario and Load Plan step.
Level: 32

Type: WARNING

Impact: Programmatic

ODI-17767: LoadPlan has variable "{0}", but repository doesn't have variable with the same name.

Cause: Variable was deleted.

Action: Check variables.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17768: LoadPlan Variable "{0}" has SQL, which could not be validated.

Cause: OdiVariableTextGeneratorException during validation.

Action: Check variable and variable text generator.
Level: 32

Type: WARNING

Impact: Programmatic

ODI-17769: OdiRef: Internal ID {0} of IObjects {1} is used when the repository is 12c mode.

Cause: Internal ID is used in 12c mode.

Action: Use Global Id instead of internal id.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17770: Profile {0} is not assigned to role {1}.

Cause: Profile is not assigned to role.

Action: Check role's profiles.
Level: 32

Type: ERROR

Impact: Security

ODI-17771: Enterprise principal with unique ID/name {0} is not mapped to role {1}.

Cause: Enterprise principal is not mapped to role.

Action: Check role's mapped enterprise principals.
Level: 32

Type: ERROR

Impact: Security

ODI-17772: Parameter {0} should be {1} or {2}.

Cause: Wrong parameter value.

Action: Check parameter value.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17773: Enterprise User or Role {0} does not exist.

Cause: Enterprise principla with such name could be found at LDAP server.

Action: Check principal name and LDAP server.
Level: 32

Type: ERROR

Impact: Security

ODI-17774: Maximum number of concurrent threads must be positive.

Cause: Wrong value.

Action: Check maximum number provided.
Level: 32

Type: ERROR

Impact: Other

ODI-17775: Maximum number of threads per session can not be negative.

Cause: Wrong value.

Action: Check maximum number provided.
Level: 32

Type: ERROR

Impact: Other

ODI-17776: Maximum number of concurrent threads must not be less than maximum session count.

Cause: Wrong value.

Action: Check maximum numbers provided.
Level: 32

Type: ERROR

Impact: Other

ODI-17777: Maximum number of threads per session must be not greater than maximum number of threads.

Cause: Wrong value.

Action: Check maximum numbers provided.
Level: 32

Type: ERROR

Impact: Other

ODI-17778: Maximum number of cache entries in Session Blueprint queue cannot be negative.

Cause: Wrong value.

Action: Check value.
Level: 32

Type: ERROR

Impact: Other

ODI-17779: Maximum idle time for Session Blueprint in cache cannot be negative.

Cause: Wrong value.

Action: Check value.
Level: 32

Type: ERROR

Impact: Other

ODI-17780: Package and mapping must be owned by the same project.

Cause: Package and mapping have different parents.

Action: Check package and mapping.
Level: 32

Type: ERROR

Impact: Other

ODI-17781: Deployment spec must be owned by the mapping.

Cause: Deployment Spec is not owned by mapping.

Action: Check mapping and deployment spec.
Level: 32

Type: ERROR

Impact: Other

ODI-17782: OdiRef: Internal ID is retrieved in method {0}.{1} for 12c repository.

Cause: Internal ID is retrieved in 12c mode.

Action: Retrieve Global Id instead of internal id.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17783: Mapping metadata version mismatch. Expected {0}, but was {1}.

Cause: Mapping metadata version mismatch.

Action: Check the expected and actual Mapping metadata version.
Level: 32

Type: ERROR

Impact: Other

ODI-17784: Reusable Mapping metadata version mismatch. Expected {0}, but was {1}.

Cause: Reusable Mapping metadata version mismatch.

Action: Check the expected and actual Reusable Mapping metadata version.
Level: 32

Type: ERROR

Impact: Other

ODI-17785: Option positions in knowledge module must be unique.

Cause: Option position undefined or multiple option in knowledge module has same position.

Action: Modify the position of options to be unique and not null.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17786: JKM is not Oracle Golden Gate JKM.

Cause: Model doesn't have JKM set or JKM is not Oracle Golden Gate JKM.

Action: Set Oracle Golden Gate JKM for the model.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17787: Extract and initial extract processes cannot be the same.

Cause: Extract and inital extract processes are the same.

Action: Choose another extract or initial expract process.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17788: Replicat and initial replicat processes cannot be the same.

Cause: Replicat and initial replicat processes are the same.

Action: Choose another replicat or initial replicat process.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-20001: ODI-20001: Cannot check the key because the Datastore does not exist in the database.

Cause: The Datastore referenced by this key did not exist in the database.

Action: Ensure the Datastore refers to an existing database table.
Level: 32

Type: ERROR

Impact: Other

ODI-20002: ODI-20002: The selected file is not a valid key file.

Cause: An invalid encryption key file was selected.

Action: Select a valid encryption key file.
Level: 32

Type: ERROR

Impact: Other

ODI-20003: ODI-20003: Cannot edit the condition

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20004: ODI-20004: Cannot edit the reference

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20005: ODI-20005: Cannot edit the variable

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20006: ODI-20006: Cannot display table's data. Data is probably already displayed.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20007: ODI-20007: Cannot display table's data.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20008: ODI-20008: You cannot Display this Column Data. Data is probably already displayed

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20009: ODI-20009: Cannot display data. The datastore resource name is {0} characters long which is longer than allowed by the technology ({1}). Please review the technology settings in Topology.

Cause: The datastore resource name exceeded the limit allowed by its technology.

Action: Ensure the maximum table name length setting in the corresponding technology is correct. Consider changing the datastore resource name to comply.
Level: 32

Type: ERROR

Impact: Other

ODI-20010: ODI-20010: Cannot display this Column Data

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20011: ODI-20011: Cannot perform this action: a Column of this Datastore is currently being edited

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20012: ODI-20012: Cannot perform this action: the Datastore containing this Column is currently being modified

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20013: ODI-20013: Unable to perform the action because the package is currently being modified

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20014: ODI-20014: Cannot encrypt the Procedure: it is currently being modified

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20015: ODI-20015: Cannot initialize the Flexfields values

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20016: ODI-20016: Unable to add project user functions

Cause: An unsupported action was attempted.

Action: No action required as Project user functions are not a valid selection to be added to a solution.
Level: 32

Type: ERROR

Impact: Other

ODI-20017: ODI-20017: Unable to add project sequences

Cause: An unsupported action was attempted.

Action: No action required as Project sequences are not a valid selection to be added to a solution.
Level: 32

Type: ERROR

Impact: Other

ODI-20018: ODI-20018: Unable to add project variables

Cause: An unsupported action was attempted.

Action: No action required as Project variables are not a valid selection to be added to a solution.
Level: 32

Type: ERROR

Impact: Other

ODI-20019: ODI-20019: Unable to get GBO object

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20020: ODI-20020: Cannot change CKM

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20021: ODI-20021: Cannot change the order of this Command because you do not have 'Edit' privileges on this Object

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20022: ODI-20022: Could not change the KM

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20023: ODI-20023: Cannot Duplicate a Command

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20024: ODI-20024: Cannot create the cross reference for the condition

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20025: ODI-20025: Cannot create the cross references for the reference

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20026: ODI-20026: Cannot view this Datastore: one of its Columns is currently being edited

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20027: ODI-20027: Cannot view this Column: its Datastore is currently being edited

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20028: ODI-20028: Cannot start execution.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20029: ODI-20029: Cannot move a line

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20030: ODI-20030: Cannot start the generation. The file is probably already open.

Cause: Attempt to open report file for output failed.

Action: Ensure the specified file is not currently open and the file permissions allow for write access before retrying the operation. Consider choosing a different file for output.
Level: 32

Type: ERROR

Impact: Other

ODI-20031: ODI-20031: Cannot Delete a Command being Edited.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20032: ODI-20032: Cannot Delete a Command

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20033: ODI-20033: Cannot find the KM description

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20034: ODI-20034: Cannot find the Options list for a Command

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20035: ODI-20035: Could not find a description for the KM

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20036: ODI-20036: Impossible to find the technology name, please check your privileges.

Cause: The ODI security permissions were insufficient to allow access to the specified technology.

Action: Ensure the ODI user security permissions are correct.
Level: 32

Type: ERROR

Impact: Other

ODI-20037: ODI-20037: Cannot find data transferred by the Drag'n'Drop

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20038: ODI-20038: Could not connect

Cause: A connection was not established to the selected Logical Schema.

Action: Ensure the connection data for the Physical Schema of the selected Logical Schema is valid.
Level: 32

Type: ERROR

Impact: Other

ODI-20039: ODI-20039: Incorrect context

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20040: ODI-20040: Problem encountered when determining the context

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20041: ODI-20041: No candidate datastore was found.

Cause: There were no datastores in the current model usable as candidates for generating OUT mappings.

Action: Consider creating an mapping to load data into a datastore of the current model.
Level: 32

Type: ERROR

Impact: Other

ODI-20042: ODI-20042: Property key is empty

Cause: The Property key for one of the specified Data Server's properties was not specified.

Action: Ensure a non-empty key value is supplied or remove the property with this key.
Level: 32

Type: ERROR

Impact: Other

ODI-20043: ODI-20043: Invalid property key entered. Property key maximum length is 250 characters

Cause: The Property key for one of the specified Data Server's properties had a length greater than 250 characters.

Action: Ensure a key value with the valid length is supplied or remove the property with this key.
Level: 32

Type: ERROR

Impact: Other

ODI-20044: ODI-20044: Invalid property value entered. Property value maximum length is 250 characters

Cause: The Property value for one of this Data Server's properties had a length greater than 250 characters.

Action: Ensure a value with the valid length is supplied or remove the property with this value.
Level: 32

Type: ERROR

Impact: Other

ODI-20046: ODI-20046: Unable to change an open object

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20047: ODI-20047: Unable to change Value

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20048: ODI-20048: Invalid Value entered. Value maximum length is 250 characters

Cause: The Value for one of this object's Flexfields had a length greater than 250 characters.

Action: Ensure the value supplied has a valid length.
Level: 32

Type: ERROR

Impact: Other

ODI-20049: ODI-20049: You cannot copy a folder into a folder belonging to another project.

Cause: An unsupported operation was attempted.

Action: Folders cannot be copied into hierarchy of another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20050: ODI-20050: You cannot copy a knowledge module into another project.

Cause: An unsupported operation was attempted.

Action: Knowledge modules cannot be copied into hierarchy of another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20051: ODI-20051: You cannot copy a package into a folder belonging to another project.

Cause: An unsupported operation was attempted.

Action: Packages cannot be copied into hierarchy of another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20052: ODI-20052: You cannot copy an interface into a folder belonging to another project.

Cause: An unsupported operation was attempted.

Action: Interfaces cannot be copied into hierarchy of another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20053: ODI-20053: You cannot copy a procedure into a folder belonging to another project.

Cause: An unsupported operation was attempted.

Action: Procedures cannot be copied into hierarchy of another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20054: ODI-20054: You cannot move a folder into a folder belonging to another project.

Cause: An unsupported operation was attempted.

Action: Folders cannot be moved into hierarchy of another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20055: ODI-20055: You cannot move a knowledge module into another project.

Cause: An unsupported operation was attempted.

Action: Knowledge modules cannot be moved into hierarchy of another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20056: ODI-20056: You cannot move a package into a folder belonging to another project.

Cause: An unsupported operation was attempted.

Action: Packages cannot be moved into hierarchy of another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20057: ODI-20057: You cannot move an interface into a folder belonging to another project.

Cause: An unsupported operation was attempted.

Action: Interfaces cannot be moved into hierarchy of another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20058: ODI-20058: You cannot move a procedure into a folder belonging to another project.

Cause: An unsupported operation was attempted.

Action: Procedures cannot be moved into hierarchy of another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20059: ODI-20059: You cannot copy a knowledge module into a package belonging to another project.

Cause: An unsupported operation was attempted.

Action: Knowledge modules cannot be copied into packages from another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20060: ODI-20060: You cannot copy an interface into a package belonging to another project.

Cause: An unsupported operation was attempted.

Action: Interfaces cannot be copied into packages from another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20061: ODI-20061: You cannot copy a procedure into a package belonging to another project.

Cause: An unsupported operation was attempted.

Action: Procedures cannot be copied into packages from another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20062: ODI-20062: You cannot move a knowledge module into a package belonging to another project.

Cause: An unsupported operation was attempted.

Action: Knowledge modules cannot be moved into packages from another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20063: ODI-20063: You cannot move an interface into a package belonging to another project.

Cause: An unsupported operation was attempted.

Action: Interfaces cannot be moved into packages from another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20064: ODI-20064: You cannot move a step into a package belonging to another project.

Cause: An unsupported operation was attempted.

Action: Package steps cannot be moved into packages from another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20065: ODI-20065: You cannot move a procedure into a package belonging to another project.

Cause: An unsupported operation was attempted.

Action: Procedures cannot be moved into packages from another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20066: ODI-20066: You cannot copy a folder into another project.

Cause: An unsupported operation was attempted.

Action: Folders cannot be copied into hierarchy of another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20067: ODI-20067: You cannot copy a procedure into another project.

Cause: An unsupported operation was attempted.

Action: Procedures cannot be copied into hierarchy of another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20068: ODI-20068: You cannot copy a variable into another project.

Cause: An unsupported operation was attempted.

Action: Variables cannot be copied into hierarchy of another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20069: ODI-20069: You cannot move a folder into another project.

Cause: An unsupported operation was attempted.

Action: Folders cannot be moved into hierarchy of another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20070: ODI-20070: You cannot move a sequence into another project. Copy the sequence instead.

Cause: An unsupported operation was attempted.

Action: Sequences cannot be moved into hierarchy of another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20071: ODI-20071: You cannot move a procedure into another project.

Cause: An unsupported operation was attempted.

Action: Procedures cannot be moved into hierarchy of another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20072: ODI-20072: You cannot move a variable into another project.

Cause: An unsupported operation was attempted.

Action: Variables cannot be moved into hierarchy of another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20073: ODI-20073: You cannot copy a schedule into a scenario belonging to another project.

Cause: An unsupported operation was attempted.

Action: Schedules cannot be copied into hierarchy of another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20074: ODI-20074: You cannot move a schedule into a scenario belonging to another project.

Cause: An unsupported operation was attempted.

Action: Schedules cannot be moved into hierarchy of another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20075: ODI-20075: You cannot move a folder into one of its subfolders.

Cause: An unsupported operation was attempted.

Action: Folders cannot be moved into their subfolders.
Level: 32

Type: ERROR

Impact: Other

ODI-20076: ODI-20076: You cannot copy a knowledge module into a package step belonging to another project.

Cause: An unsupported operation was attempted.

Action: Knowledge modules cannot be copied into package steps from another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20077: ODI-20077: You cannot copy an interface into a package step belonging to another project.

Cause: An unsupported operation was attempted.

Action: Interfaces cannot be copied into package steps from another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20078: ODI-20078: You cannot copy a procedure into a package step belonging to another project.

Cause: An unsupported operation was attempted.

Action: Procedures cannot be copied into package steps from another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20079: ODI-20079: You cannot move a knowledge module into a package step belonging to another project.

Cause: An unsupported operation was attempted.

Action: Knowledge modules cannot be moved into package steps from another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20080: ODI-20080: You cannot move an interface into a package step belonging to another project.

Cause: An unsupported operation was attempted.

Action: Interfaces cannot be moved into package steps from another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20081: ODI-20081: You cannot move a step into a package step belonging to another project.

Cause: An unsupported operation was attempted.

Action: Steps cannot be moved into package steps from another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20082: ODI-20082: You cannot move a procedure into a package step belonging to another project.

Cause: An unsupported operation was attempted.

Action: Procedures cannot be moved into package steps from another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20083: ODI-20083: Unable to perform the operation. {0} is being edited.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20084: ODI-20084: Only variables from the same project can be placed in a package.

Cause: An unsupported operation was attempted.

Action: Variables from another projects cannot be placed in packages.
Level: 32

Type: ERROR

Impact: Other

ODI-20085: ODI-20085: Only interfaces from the same project can be placed in a package.

Cause: An unsupported operation was attempted.

Action: Interfaces from another projects cannot be placed in packages.
Level: 32

Type: ERROR

Impact: Other

ODI-20086: ODI-20086: Only procedures from the same project can be placed in a package.

Cause: An unsupported operation was attempted.

Action: Procedures from another projects cannot be placed in packages.
Level: 32

Type: ERROR

Impact: Other

ODI-20087: ODI-20087: Error while duplicating

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20088: ODI-20088: Error while generating the scenario

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20089: ODI-20089: Error during parameter initialization

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20090: ODI-20090: Error while duplicating

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20091: ODI-20091: An unexpected error occurred.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20092: ODI-20092: An error occurred while replacing the version.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20093: ODI-20093: Scenario generation is not allowed for non-saved object

Cause: Scenario generation could not be performed because the source object was not saved.

Action: Ensure the source object is saved before attempting scenario generation for it.
Level: 32

Type: ERROR

Impact: Other

ODI-20094: ODI-20094: Specify the object name to generate Scenario

Cause: Scenario generation could not be performed because the source object's name was not specified.

Action: Ensure the source object's name is specified before attempting scenario generation for it.
Level: 32

Type: ERROR

Impact: Other

ODI-20095: ODI-20095: Marker Group save was cancelled

Cause: Marker group save was cancelled by a user.

Action: No action required.
Level: 32

Type: ERROR

Impact: Other

ODI-20096: ODI-20096: Unable to edit the action line.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20097: ODI-20097: The line Name is mandatory

Cause: A value for the Action Line Name field was not specified.

Action: Enter a non-empty value for the Action Line Name field.
Level: 32

Type: ERROR

Impact: Other

ODI-20098: ODI-20098: Some Datatype Conversions between current and new Technologies are absent

Cause: Changing the selected Model's Technology failed because the Physical Architecture did not provide datatype conversion rules for datatypes used by columns of datastores belonging to the selected model.

Action: Ensure datatype conversion rules exist for all datatypes used by columns of datastores belonging to the selected model or do not use datatypes that cannot be converted.
Level: 32

Type: ERROR

Impact: Other

ODI-20099: ODI-20099: Unable to create execution window

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20100: ODI-20100: Unable to access a join or a filter

Cause: Access to a join or filter failed due to insufficient ODI security permissions.

Action: Ensure the ODI user security permissions are correct for the join or filter object.
Level: 32

Type: ERROR

Impact: Other

ODI-20101: ODI-20101: Unable to find mapping alias

Cause: Access to the target mapping failed due to insufficient ODI security permissions.

Action: Ensure the ODI user security permissions are correct for the target mapping.
Level: 32

Type: ERROR

Impact: Other

ODI-20102: ODI-20102: Unable to find source table alias

Cause: Access to the source table failed due to insufficient ODI security permissions.

Action: Ensure the ODI user security permissions are correct for the source table.
Level: 32

Type: ERROR

Impact: Other

ODI-20103: ODI-20103: Unable to access a target column

Cause: Access to the target column failed due to insufficient ODI security permissions.

Action: Ensure the ODI user security permissions are correct for the target column.
Level: 32

Type: ERROR

Impact: Other

ODI-20105: ODI-20105: "Schema", "Table", "Column" and "Filter" are mandatory fields.

Cause: Values for the mandatory "Schema", "Table", "Column" and "Filter" fields were not supplied.

Action: Ensure values are supplied for these mandatory fields.
Level: 32

Type: ERROR

Impact: Other

ODI-20106: ODI-20106: Schema and Native sequence name are mandatory fields

Cause: Values for the mandatory Schema and Native sequence name fields were not supplied.

Action: Ensure values are supplied for these mandatory fields.
Level: 32

Type: ERROR

Impact: Other

ODI-20107: ODI-20107: A project sequence with the name "{0}" already exists in the project "{1}"

Cause: Saving the project sequence failed because the Sequence name was not unique within the Project.

Action: Ensure the sequence name entered is unique.
Level: 32

Type: ERROR

Impact: Other

ODI-20108: ODI-20108: A global sequence with the name "{0}" already exists

Cause: Saving the Global sequence failed because the Global Sequence name was not unique.

Action: Ensure the sequence name entered is unique.
Level: 32

Type: ERROR

Impact: Other

ODI-20109: ODI-20109: Error while restoring the version

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20110: ODI-20110: No version of this element exist.

Cause: The selected version of this object was not found in version repository.

Action: Create or restore the selected version of the object.
Level: 32

Type: ERROR

Impact: Other

ODI-20111: ODI-20111: Sub-model code cannot be empty.

Cause: A value of the mandatory Sub-model code field was not supplied.

Action: Enter a non-empty value for the Sub-model code field.
Level: 32

Type: ERROR

Impact: Other

ODI-20112: ODI-20112: The path defined in the logical schema is incorrect.

Cause: Incorrect path was specified in physical schema which is linked to the logical schema of this datastore in the current context.

Action: Ensure the path specified in physical schema is correct.
Level: 32

Type: ERROR

Impact: Other

ODI-20113: ODI-20113: The GUID that was supplied does not match the GUID for this user in the external identity store. Please retrieve the correct GUID before saving.

Cause: The supplied GUID did not match GUID from external identity store.

Action: Provide a valid GUID.
Level: 32

Type: ERROR

Impact: Other

ODI-20114: ODI-20114: Error while subscribing

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20115: ODI-20115: Error while stopping journalizing

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20116: ODI-20116: Aliases are specified and are not unique.

Cause: Duplicate Alises were detected.

Action: Change the name of the join key alias.
Level: 32

Type: ERROR

Impact: Other

ODI-20117: ODI-20117: Error while executing command line.

Cause: An unexpected error occurred while trying to open the Report.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20118: ODI-20118: Error while building the menu.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20119: ODI-20119: Error during generation.

Cause: An unexpected error occurred during the report generation.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20120: ODI-20120: Error while journalizing

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20121: ODI-20121: Error while saving the diagram

Cause: An unexpected error occurred during the saving the diagram.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20122: ODI-20122: Error while unsubscribing

Cause: An unexpected error occurred during the unsubscribing action.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20123: ODI-20123: Error while executing query

Cause:

Action: Check the error details for further actions.
Level: 32

Type: ERROR

Impact: Other

ODI-20124: ODI-20124: Operation cancelled by user.

Cause: Operation cancelled by user

Action: Review the other messages for further actions.
Level: 32

Type: WARNING

Impact: Other

ODI-20126: ODI-20126: TreeTableColumn cannot be added

Cause: TreeTableColumn with this order number already exists

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20127: ODI-20127: This TreeTableColumn cannot be removed.

Cause: TreeTableColumn does not exist.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20128: ODI-20128: Could not rollback.

Cause: An error occurred during rollback operation.

Action: Review other messages for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20129: ODI-20129: Exception occurred.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20130: ODI-20130: You must select a folder.

Cause: A folder was not selected.

Action: Select a folder before attempting this action.
Level: 32

Type: ERROR

Impact: Other

ODI-20131: ODI-20131: Cannot retrieve the table list

Cause: An error occured while trying to retrieve a list of tables.

Action: Review the message log for more information. If problem persists contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20132: ODI-20132: An interface cannot be moved to another project

Cause: An unsupported drag and drop operation was attempted.

Action: No action required.
Level: 32

Type: ERROR

Impact: Other

ODI-20133: ODI-20133: A procedure cannot be moved to another project

Cause: An unsupported drag and drop operation was attempted.

Action: No action required.
Level: 32

Type: ERROR

Impact: Other

ODI-20134: ODI-20134: A variable cannot be moved to another project

Cause: An unsupported drag and drop operation was attempted.

Action: No action required
Level: 32

Type: ERROR

Impact: Other

ODI-20135: ODI-20135: A step cannot be moved to another package

Cause: An unsupported drag and drop operation was attempted.

Action: No action required
Level: 32

Type: ERROR

Impact: Other

ODI-20138: ODI-20138: An error occured during: dragGesture

Cause: An unexpected error occurred while dragging an object.

Action: Review the message log for more information. If problem persists contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20139: ODI-20139: An error occured during: dragEnter

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20140: ODI-20140: An error occured during: Drop

Cause: An unexpected error occurred while dropping an object.

Action: Review the message log for more information. If problem persists contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20141: ODI-20141: Login Creation Error

Cause: An unexpected error occurred while creating a new Login.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20142: ODI-20142: Popup Menu Creation Error

Cause: An unexpected error occurred while creating a popup menu.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20144: ODI-20144: Error while Deleting

Cause: An unexpected error occurred while deleting a tree object.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20145: ODI-20145: Error while Opening splitframe.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20146: ODI-20146: Error occured during duplication

Cause: An unexpected error occurred while duplicating an object.

Action: Review the error details and message log for more information.
Level: 32

Type: ERROR

Impact: Other

ODI-20148: ODI-20148: An error occured during: drag over the object

Cause: An unexpected error occurred while dragging an object over another object.

Action: Review the error details and message log for more information.
Level: 32

Type: ERROR

Impact: Other

ODI-20149: ODI-20149: Logical schema can't be undefined

Cause: A Logical schema was not defined.

Action: Define a Logical schema.
Level: 32

Type: ERROR

Impact: Other

ODI-20150: ODI-20150: KM or Procedure already encrypted. No encryption was performed.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20151: ODI-20151: File is not found. Invalid file location

Cause: The specified file could not be located in the file system.

Action: Ensure file location specified is valid and accessible.
Level: 32

Type: ERROR

Impact: Other

ODI-20152: ODI-20152: Object cannot be deleted

Cause: The specified object could not be deleted.

Action: Ensure the specified object exists and the security permissions permit deletion.
Level: 32

Type: ERROR

Impact: Other

ODI-20153: ODI-20153: The following field is missing: Syntax

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20155: ODI-20155: Changing the Logical Schema may require a re-generation of your Interfaces. It may be better to modify the Topology information instead.

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-20158: ODI-20158: Datastores distribution failed.

Cause: An error occured during the datastore distribution process.

Action: Review the message details and message log for more information. If problem persists contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20159: ODI-20159: The Column {0} is used as a Reference

Cause: An attempt was made to delete a column referenced by another object.

Action: Delete the object which references this column then retry deleting this column.
Level: 32

Type: ERROR

Impact: Other

ODI-20160: ODI-20160: The table {0} does not exist.

Cause: An error occured while executing the SQL request

Action: Review the message details for more information. If problem persists contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20161: ODI-20161: Standard reverse-engineering failed.

Cause: An error occured during the standard reverse-engineering process.

Action: Ensure the technology or driver supports standard reverse-engineering. Otherwise choose Customized Reverse and select an appropriate RKM for the technology.
Level: 32

Type: ERROR

Impact: Other

ODI-20162: ODI-20162: The context is not valid.

Cause: A Context was not specified.

Action: Specify a Context.
Level: 32

Type: ERROR

Impact: Other

ODI-20163: ODI-20163: Unable to add object

Cause: An error occurred while dragging and dropping an object.

Action: Review the message details and message log for more information.
Level: 32

Type: ERROR

Impact: Other

ODI-20164: ODI-20164: The line Name is mandatory

Cause: A name was not specified.

Action: Specify a Line name.
Level: 32

Type: ERROR

Impact: Other

ODI-20165: ODI-20165: The project name {0} is a reserved word.

Cause: A reserved word was used as the name of a project.

Action: Enter a different project name.
Level: 32

Type: ERROR

Impact: Other

ODI-20166: ODI-20166: The project code {0} is a reserved word.

Cause: A reserved word was used as the project code.

Action: Enter a different project code.
Level: 32

Type: ERROR

Impact: Other

ODI-20167: ODI-20167: Logical schema is not set for the current context

Cause: A Logical schema was not set for the current context.

Action: Ensure the Logical Schema is not set to "Undefined" in the Context editor.
Level: 32

Type: ERROR

Impact: Other

ODI-20168: ODI-20168: Logical schema is not set for the current context

Cause: A Logical schema was not set for the current context.

Action: Ensure the Logical Schema is not set to "Undefined" in the Context editor.
Level: 32

Type: ERROR

Impact: Other

ODI-20169: ODI-20169: The field {0} is mandatory.

Cause: A mandatory field was not specified.

Action: Enter a value for this field.
Level: 32

Type: ERROR

Impact: Other

ODI-20170: ODI-20170: You are trying to insert this versioned object but the version was deleted. Please re-create a version for this object.

Cause: The requested version of the object did not exist in the repository.

Action: Recreate the required version of this object.
Level: 32

Type: ERROR

Impact: Other

ODI-20171: ODI-20171: The solution already contains a child of {0}. To add {1} to the solution, you should delete {2} {3}. It is advised to use the button "synchronize" later to check the solution's coherence.

Cause: The solution already contained the specified object as a child.

Action: Delete the child object from the solution before retrying the addition. Consider using the synchronize option to verify the solution's coherence.
Level: 32

Type: ERROR

Impact: Other

ODI-20172: ODI-20172: The solution already contains a parent of {0}. To add {1} to the solution, you should delete {2} {3}. It is advised to use the button "synchronize" later to check the solution's coherence.

Cause: The solution has already contained the specified object as a parent of {0}.

Action: Delete the parent object from the solution before retrying the addition. Consider using the synchronize option to verify the solution's coherence.
Level: 32

Type: ERROR

Impact: Other

ODI-20173: ODI-20173: An error occurred while generating the procedure

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20174: ODI-20174: Folder {0} already contains an mapping named {1}

Cause: An mapping of the same name already existed in the specified folder.

Action: Specify another name for the mapping.
Level: 32

Type: ERROR

Impact: Other

ODI-20175: ODI-20175: You cannot give an empty name to an mapping

Cause: The Mapping's name was not specified.

Action: Enter a non-empty value for the mapping's name.
Level: 32

Type: ERROR

Impact: Other

ODI-20176: ODI-20176: You cannot create multiple mappings with the same name

Cause: An mapping of the same name already existed.

Action: Specify a different name for the mapping.
Level: 32

Type: ERROR

Impact: Other

ODI-20177: ODI-20177: You must select a generation folder

Cause: The Generation folder was not selected.

Action: Select a generation folder.
Level: 32

Type: ERROR

Impact: Other

ODI-20180: ODI-20180: You cannot choose an expiration date in the past.

Cause: Entered expiration date was in the past.

Action: Enter valid expiration date.
Level: 32

Type: ERROR

Impact: Other

ODI-20181: ODI-20181: You cannot set an expiration date if there is no password.

Cause: No password was entered.

Action: Enter a password before setting an expiration date.
Level: 32

Type: ERROR

Impact: Other

ODI-20182: ODI-20182: Error while opening window

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20183: ODI-20183: Error while refreshing Solution

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20184: ODI-20184: The request to retrieve the sequence list has not been defined on the technology.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20185: ODI-20185: Error while opening window

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20186: ODI-20186: Error while saving

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20187: ODI-20187: Error while adding the marker

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20188: ODI-20188: This object is locked by another user. You cannot edit its markers.

Cause: The object was locked by another user.

Action: Wait until the object is unlocked. Consider contacting the user who has the object locked.
Level: 32

Type: ERROR

Impact: Other

ODI-20189: ODI-20189: You do not have the sufficient privileges to reverse-engineer a model

Cause: The model could not be reverse-engineered due to insufficient privileges.

Action: Ensure the SUPERVISOR or owner of model grants the appropriate permissions.
Level: 32

Type: ERROR

Impact: Other

ODI-20190: ODI-20190: You cannot reverse engineer a model in 'Standard' mode: the model technology assumes RKM to be selected.

Cause: No RKM was specified for this model.

Action: Select an RKM for this model.
Level: 32

Type: ERROR

Impact: Other

ODI-20191: ODI-20191: The model you want to reverse-engineer references a logical schema that no longer exists.

Cause: The referenced Logical Schema for the Model was not found.

Action: Ensure a valid Logical Schema is assigned for the Model.
Level: 32

Type: ERROR

Impact: Other

ODI-20192: ODI-20192: Error while replacing versioned object

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20193: ODI-20193: An error occurred during the versioning operation.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20194: ODI-20194: Your license does not allow Versioning operations.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20195: ODI-20195: Unable to unlock this object

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20196: ODI-20196: You must select an object version

Cause: No version selected for checkout.

Action: Select version for checkout.
Level: 32

Type: ERROR

Impact: Other

ODI-20197: ODI-20197: Your license does not allow Versioning operations.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20198: ODI-20198: Error while creating the version.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20199: ODI-20199: Your license does not allow Versioning operations.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20200: ODI-20200: An error happened while comparing the versions

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20201: ODI-20201: Error while refreshing.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20202: ODI-20202: Synchronisation was stopped by the user.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20203: ODI-20203: The current version for this object no longer exists. Please create a new version for this object.

Cause: The current version for this object was not found in the repository.

Action: Create a new version for this object.
Level: 32

Type: ERROR

Impact: Other

ODI-20205: ODI-20205: Could not delete object. This object is being used.

Cause: The object deletion failed because it was already in use.

Action: Remove the usage of the selected object before retrying the deletion.
Level: 32

Type: ERROR

Impact: Other

ODI-20206: ODI-20206: Could not delete object. This object is being displayed.

Cause: The object deletion failed because it was being displayed.

Action: Close object before retrying the deletion.
Level: 32

Type: ERROR

Impact: Other

ODI-20208: ODI-20208: A code was duplicated:

Cause: A Flex field with the same code already existed.

Action: Enter another Flex field code.
Level: 32

Type: ERROR

Impact: Other

ODI-20209: ODI-20209: An error occurred.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20210: ODI-20210: Error When Printing...

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20211: ODI-20211: Error When Displaying Node...

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20212: ODI-20212: An error occurred while checking errors

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20213: ODI-20213: An error occurred while recovering an object in a node

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20214: ODI-20214: An error occurred while deleting

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20216: ODI-20216: Error while deleting

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20217: ODI-20217: Error while executing the reverse-engineering

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20218: ODI-20218: Error during duplication ...

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20219: ODI-20219: Error while opening

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20220: ODI-20220: Error during data loading ....

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20221: ODI-20221: Error during execution ...

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20222: ODI-20222: Error during scenario creation ...

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20223: ODI-20223: Error When Purging Log

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20224: ODI-20224: An interface with the same name already exists in this folder. Please change the name of the new interface.

Cause: An interface with the same name already existed in this folder.

Action: Specify another name for the interface.
Level: 32

Type: ERROR

Impact: Other

ODI-20225: ODI-20225: Error while creating the popup menu

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20226: ODI-20226: Error while applying the changes

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20227: ODI-20227: You cannot copy this column. Column name already in use.

Cause: Column copy failed because the Datastore already contained a column with the same name.

Action: Select another column to drop to datastore.
Level: 32

Type: ERROR

Impact: Other

ODI-20228: ODI-20228: Error while creating the popup menu

Cause: Retrieval of the Available Methods for the column failed.

Action: Ensure the repository database connection is not broken and the ODI Security permissions are correct.
Level: 32

Type: ERROR

Impact: Other

ODI-20229: ODI-20229: Unable to create condition.

Cause: The editor for the Condition could not be opened.

Action: Ensure the repository database connection is not broken and the ODI Security permissions are correct.
Level: 32

Type: ERROR

Impact: Other

ODI-20230: ODI-20230: Error while creating the popup menu

Cause: Retrieval of the Available Methods for the Condition failed.

Action: Ensure the repository database connection is not broken and the ODI Security permissions are correct.
Level: 32

Type: ERROR

Impact: Other

ODI-20231: ODI-20231: Unable to create a synonym for this table.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20232: ODI-20232: Error while deleting columns

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20233: ODI-20233: Error during the drag-and-drop operation

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20234: ODI-20234: You do not have the sufficient privileges to add this object.

Cause: The operation failed due to insufficient ODI security on Column.

Action: Ensure the ODI user security permissions are correct specifically the Column Duplication setting.
Level: 32

Type: ERROR

Impact: Other

ODI-20235: ODI-20235: Error during the drag-and-drop operation

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20236: ODI-20236: You do not have the sufficient privileges to add this object.

Cause: The operation failed due to insufficient ODI security on Datastore.

Action: Ensure the ODI user security permissions are correct.
Level: 32

Type: ERROR

Impact: Other

ODI-20237: ODI-20237: Unable to duplicate the column.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20238: ODI-20238: Unable to duplicate the table.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20239: Error during the action

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20240: ODI-20240: Error while deleting

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20241: ODI-20241: Unable to apply changes.

Cause: The changes to the filter could not be applied.

Action: Save the object before retrying to apply the filter.
Level: 32

Type: ERROR

Impact: Other

ODI-20242: ODI-20242: Error while creating the popup menu

Cause: Retrieval of the Available Methods for the filter failed.

Action: Ensure the repository database connection is not broken and the ODI Security permissions are correct.
Level: 32

Type: ERROR

Impact: Other

ODI-20243: ODI-20243: Unable to add column.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20244: ODI-20244: Unable to add reference

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20245: ODI-20245: Unable to add table

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20246: ODI-20246: Error while applying the changes

Cause: The reference to the Model could not be created.

Action: Ensure the repository database connection is not broken and the ODI Security permissions are correct.
Level: 32

Type: ERROR

Impact: Other

ODI-20247: ODI-20247: Unable to add key.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20248: ODI-20248: Error while opening window

Cause: The editor could not be opened.

Action: Save the object before retrying the edit.
Level: 32

Type: ERROR

Impact: Other

ODI-20249: ODI-20249: Error while creating the popup menu

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20250: ODI-20250: Error while

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20251: ODI-20251: An unexpected error has occurred

Cause: Unable to acess the Security Authorization settings.

Action: Ensure the repository database connection is not broken and the ODI Security permissions are correct.
Level: 32

Type: ERROR

Impact: Other

ODI-20252: ODI-20252: Unable to apply changes.

Cause: Saving the model condition failed.

Action: Ensure the repository database connection is not broken and the ODI Security permissions are correct.
Level: 32

Type: ERROR

Impact: Other

ODI-20253: ODI-20253: The object was deleted by another user

Cause: The operation could not be performed because the specified object could not found.

Action: Refresh the view and retry the operation.
Level: 32

Type: ERROR

Impact: Other

ODI-20254: ODI-20254: The marker was deleted by another user

Cause: The operation could not be performed because the specified Marker object was in an Inconsistent state.

Action: Refresh the view and retry the operation.
Level: 32

Type: ERROR

Impact: Other

ODI-20255: ODI-20255: Marker name is mandatory

Cause: Marker could not be saved because the mandatory Name field was not entered.

Action: Enter a value in the Marker name field.
Level: 32

Type: ERROR

Impact: Other

ODI-20256: ODI-20256: You do not have the sufficient privileges to change the marker

Cause: Modification of the Marker failed due to insufficient ODI security privileges.

Action: Ensure the ODI user security permissions are correct.
Level: 32

Type: ERROR

Impact: Other

ODI-20257: ODI-20257: The Where text is mandatory when the Filter is active for a static control.

Cause: The WHERE clause was null or empty.

Action: Ensure the WHERE clause is valid.
Level: 32

Type: ERROR

Impact: Other

ODI-20258: ODI-20258: It is not possible to check the expression due to DBMS connection failure

Cause: Connection to the DBMS failed.

Action: Ensure the DBMS is available and the connection information to it is correctly specified.
Level: 32

Type: ERROR

Impact: Other

ODI-20259: ODI-20259: cannot show the data since the join points to different connections

Cause: Unable to retrieve data due to a conflict between the physical schemas involved.

Action: Ensure the Topology or Context settings are correct and multiple data stores in the same Source Set are not connected using different Physical Schemas.
Level: 32

Type: ERROR

Impact: Other

ODI-20260: ODI-20260: Name and Code columns of the FlexField cannot be empty.

Cause: FlexField name or code were found to be empty or null.

Action: Enter a name and a code for the FlexField.
Level: 32

Type: ERROR

Impact: Other

ODI-20261: ODI-20261: The "Procedure Name" is mandatory.

Cause: The "Procedure Name" field value was not specified.

Action: Enter a value for the "Procedure Name" field.
Level: 32

Type: ERROR

Impact: Other

ODI-20262: ODI-20262: Logical Schema is not selected.

Cause: There is no Logical Schema selected for this variable.

Action: Select a Logical Schema.
Level: 32

Type: ERROR

Impact: Other

ODI-20300: ODI-20300: Error while printing the diagram

Cause: An unexpected condition has occurred in the print system.

Action: Check the printer settings and physical printer.
Level: 32

Type: ERROR

Impact: Other

ODI-20301: ODI-20301: Error while saving the diagram

Cause: The save file could not be created.

Action: Check the destination folder is writable and that their is sufficient disk space.
Level: 32

Type: ERROR

Impact: Other

ODI-20310: Unsupported Flavor

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20311: ODI-20311: An unexpected exception occurred while reading or writing a text in a business object. Please contact Oracle technical support.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20312: ODI-20312: An error occurred while printing.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20313: ODI-20313: Could not double click

Cause: An unexpected error has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20315: ODI-20315: Invalid Password

Cause: The Password is incorrect.

Action: Correct the password and try again.
Level: 32

Type: ERROR

Impact: Other

ODI-20316: ODI-20316: A timeout occurred while trying to establish a connection.

Cause: A timeout error occurred while connecting to the database.

Action: Verify that the Database Connection details are correct and the database is available.
Level: 32

Type: ERROR

Impact: Other

ODI-20317: ODI-20317: The field "{0}" is mandatory.

Cause: A value has not been provided for a required field.

Action: Enter a value for the named field.
Level: 32

Type: ERROR

Impact: Other

ODI-20318: ODI-20318: The icon {0} cannot be found.

Cause: An unexpected error has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20319: ODI-20319: {0} is not a valid date for field {1}. The format is: {2}

Cause: The format of the date does not match the required format.

Action: Enter a valid date using the correct date format.
Level: 32

Type: ERROR

Impact: Other

ODI-20320: ODI-20320: Error when applying changes.

Cause: An unexpected error has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20321: ODI-20321: Error when initializing the panel.

Cause: An unexpected error has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20322: ODI-20322: Unable to add a Step.

Cause: An unexpected error has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20323: ODI-20323: Unable to execute the step

Cause: An unexpected error has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20324: ODI-20324: Cannot execute the Package

Cause: An unexpected error has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20325: ODI-20325: Unable to open the linked object.

Cause: An unexpected error has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20326: ODI-20326: Unable to edit the text

Cause: An unexpected error has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20327: ODI-20327: Unable to modify the value.

Cause: An unexpected error has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20328: ODI-20328: Unable to define the next Step.

Cause: An unexpected error has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20329: ODI-20329: Unable to delete Steps(s). You do not have Edit privileges.

Cause: An unexpected error has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20330: ODI-20330: Unable to delete Link(s). You do not have Edit privileges.

Cause: You must have Edit privilege on each steps of the link.

Action: Review the Security settings for the steps and ensure that you have the correct permissions.
Level: 32

Type: ERROR

Impact: Other

ODI-20331: ODI-20331: The Step diagram is not be accessible.

Cause: You do not have permission to access this step.

Action: Check the diagram security settings and verify that you have permission to access the diagram.
Level: 32

Type: ERROR

Impact: Other

ODI-20332: ODI-20332: Cannot change the position of this object

Cause: An unexpected error has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20333: ODI-20333: Cannot view this Step because the Package is being edited

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20335: ODI-20335: Printing Options not accessible.

Cause: An unexpected error has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20336: ODI-20336: Unknown event sent to the Package event manager.

Cause: An unexpected error has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20337: ODI-20337: A Knowledge Module cannot be added as a Step.

Cause: Only a DataStore,Model,Sub Model,Interface,Procedure or Variable can be added as a Step.

Action: Use a valid object type for your step creation.
Level: 32

Type: ERROR

Impact: Other

ODI-20338: ODI-20338: A starting Step must be defined.

Cause: A Starting step has been defined.

Action: Select the first step in the package and mark is the starting step.
Level: 32

Type: ERROR

Impact: Other

ODI-20339: ODI-20339: One or more Steps are not linked.

Cause: All steps must be linked.

Action: Ensure that all steps are linked .
Level: 32

Type: ERROR

Impact: Other

ODI-20340: ODI-20340: Only one starting Step can be defined.

Cause: A package must have one and only one starting steps.

Action: Ensure that you have only one starting step defined .
Level: 32

Type: ERROR

Impact: Other

ODI-20341: ODI-20341: You don't have the appropriate privileges.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20342: ODI-20342: Cannot open the Expression Editor

Cause: An unexpected error has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20343: ODI-20343: There are errors in your diagram

Cause: The diagram may contain objects that are not connected, or objects that are not completely defined.

Action: Check the diagram and ensure that all objects are connected and fully defined.
Level: 32

Type: ERROR

Impact: Other

ODI-20344: ODI-20344: Cannot launch the editor for this expression

Cause: An error occured while retrieving the language for the expression. This may be due to an unexpected exception, or the language may not be available for the schema's technology.

Action: Review the message log for additional errors. Ensure that the schema has a valid technology for which the language is set.
Level: 32

Type: ERROR

Impact: Other

ODI-20345: ODI-20345: Cannot change the clause position

Cause: An unexpected internal exception has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20346: ODI-20346: Cannot get the boolean value of an option

Cause: The boolean value of the option could not be retrieved due to a security error.

Action: Review the message log and contact Oracle Support Services for further assistance.
Level: 32

Type: ERROR

Impact: Other

ODI-20347: ODI-20347: Error during data transfer for drag and drop

Cause: An internal error occured while dropping the object into the diagram.

Action: Review the message log for additional information and contact Oracle Support Services for further assistance.
Level: 32

Type: ERROR

Impact: Other

ODI-20348: ODI-20348: An interface with the same name already exists in this folder. Please change the name of the new interface.

Cause: An interface with the specified name exists in the folder. The interface name must be unique within a folder.

Action: Enter a new interface name that is unique within the folder.
Level: 32

Type: ERROR

Impact: Other

ODI-20349: ODI-20349: Unknown event detected by the event manager. Please contact Oracle Support Services.

Cause: The Package Event Manager was called to action an unknown event.

Action: Contact Oracle Support Services for further assistance.
Level: 32

Type: ERROR

Impact: Other

ODI-20350: ODI-20350: Your diagram contains one or more FATAL/CRITICAL errors preventing display of the Flow Editor

Cause: The diagram is incomplete or contains errors that prevent the Flow Editor being displayed.

Action: Return to the diagram tab and review the error messages using the errors and warnings button in the toolbar. Fix the errors in order to access the Flow Editor.
Level: 32

Type: ERROR

Impact: Other

ODI-20351: ODI-20351: Error adding source to Quick Edit source table.

Cause: An internal error occured which prevented the source being added.

Action: Contact Oracle Support Services for further assistance.
Level: 32

Type: ERROR

Impact: Other

ODI-20352: ODI-20352: Error adding target datastore to Quick Edit mapping table.

Cause: An internal error occured which prevented the target being added.

Action: Contact Oracle Support Services for further assistance.
Level: 32

Type: ERROR

Impact: Other

ODI-20353: ODI-20353: Only a single column may be pasted into a Quick Edit table.

Cause: The clipboard contains multiple columns. Quick Edit only supports pasting a single cell into a table.

Action: Select the cells to be copied and paste them one at a time.
Level: 32

Type: ERROR

Impact: Other

ODI-20354: ODI-20354: Paste targets must be in the same column as the previous copy. This does not apply to Expression columns (Lookup Expression, Join Expression, Filter Expression, and Mapping Expression).

Cause: You have selected a value from one column, and tried to paste it into a different column. This is only supported for Expression Columns.

Action: Please enter the values into the cell manually.
Level: 32

Type: ERROR

Impact: Other

ODI-20355: ODI-20355: Duplicate value is not supported on this column.

Cause: The paste operation is not permitted in the Alias and Target Column Name fields as these fields must contain a unique value.

Action: Please enter the Alias or Name field manually.
Level: 32

Type: ERROR

Impact: Other

ODI-20356: ODI-20356: Can not perform paste into a read-only column.

Cause: The Paste operation is not permitted on read-only columns.

Action: You may not update this value in the table.
Level: 32

Type: ERROR

Impact: Other

ODI-20357: ODI-20357: Can not perform deletion because the target datastore is not temporary.

Cause: An attempt was made to delete a row in the target, but the target datastore is not a temporary table. Only rows in a temporary target table may be deleted.

Action: You cannot delete the row.
Level: 32

Type: ERROR

Impact: Other

ODI-20358: ODI-20358: Interface cannot be saved because it has a fatal error: {0}.

Cause: The Interface could not be saved because it contains a fatal error which must be resolved.

Action: Review the errors in the Diagram tab and resolve the fatal errors.
Level: 32

Type: ERROR

Impact: Other

ODI-20359: ODI-20359: Only one cell can be copied one at a time.

Cause: More than one cell was selected. Quick Edit only supports copying a single cell.

Action: Select and copy a single cell.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-20360: ODI-20360: Only Expression columns support Copy and Paste from other applications. For all other columns, please perform a copy first on that column before pasting.

Cause: Only values from other applications may be copied into Expression columns.

Action: For all other columns, perform a copy first on that column before pasting.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-20361: ODI-20361: Can not perform Copy and Paste across tables, except for Expression columns (Lookup Expression, Join Expression, Filter Expression, and Mapping Expression).

Cause: Values may not be copied between tables in Quick Edit, apart from between Expression columns.

Action: Please enter the values manually.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-20370: ODI-20370 : Shortcuts within a project can only refer to objects that belong to that same project

Cause: Shortcuts within a project can only refer to objects that belong to that same project

Action: =Try another folder destination
Level: 32

Type: ERROR

Impact: Other

ODI-20371: ODI-20371 : No two shortcut objects within a folder may refer to the same base object

Cause: No two shortcut objects within a folder may refer to the same base object

Action: Try another folder destination or fix folder contents
Level: 32

Type: ERROR

Impact: Other

ODI-20372: ODI-20372 : The source and destination models must be defined with the same Technology

Cause: The source and destination models must be defined with the same Technology

Action: Try another model destination or fix model properties.
Level: 32

Type: ERROR

Impact: Other

ODI-20373: ODI-20373 : No two shortcuts within a model may contain the same base object

Cause: No two shortcuts within a model may contain the same base object

Action: Try another folder destination or fix model contents.
Level: 32

Type: ERROR

Impact: Other

ODI-20374: ODI-20374 : A model cannot contain a datastore and a shortcut to another datastore with the same table name

Cause: A model cannot contain a datastore and a shortcut to another datastore with the same table name

Action: Try another folder destination or fix model contents.
Level: 32

Type: ERROR

Impact: Other

ODI-20701: ODI-20701: The Name field is mandatory.

Cause: The Name field was not entered.

Action: Enter a name for the Load Plan.
Level: 32

Type: ERROR

Impact: Other

ODI-20702: ODI-20702: The name given for the Load Plan is already used by another load plan. Please provide another name.

Cause: The name provided for the Load Plan was not unique.

Action: Enter a unique name for the Load Plan.
Level: 32

Type: ERROR

Impact: Other

ODI-20703: ODI-20703: Variable "{0}" is not found.

Cause: The variable could not be found.

Action: Provide another name for the variable.
Level: 32

Type: ERROR

Impact: Other

ODI-20704: ODI-20704: Datatype of variable "{0}" has been changed.

Cause: The datatype of the original variable is different to the datatype of the load plan variable.

Action: Verify the datatype of the variable and ensure that the types of the original and load plan variables match.
Level: 32

Type: ERROR

Impact: Other

ODI-20705: ODI-20705: This variable is used in one or more case steps. Removing it will trigger deletion of those case steps, and all of their child steps. Do you want to continue?

Cause: An attempt was made to remove a variable which is used in one or more case steps.

Action: To remove the variable and its associated case steps, click Yes. Otherwise, click No, and nothing will be removed.
Level: 32

Type: WARNING

Impact: Other

ODI-20706: ODI-20706: The Step Name is mandatory.

Cause: The Step Name field was not entered.

Action: Enter a name for the Step.
Level: 32

Type: ERROR

Impact: Other

ODI-20707: ODI-20707: The Variable is mandatory.

Cause: A Variable was not selected.

Action: Select a variable.
Level: 32

Type: ERROR

Impact: Other

ODI-20708: ODI-20708: The Scenario is mandatory.

Cause: A Scenario was not selected.

Action: Select a Scenario.
Level: 32

Type: ERROR

Impact: Other

ODI-20709: ODI-20709: The Value is mandatory.

Cause: A Value was not provided.

Action: Enter a Value.
Level: 32

Type: ERROR

Impact: Other

ODI-20710: ODI-20710: The Value format is not valid.

Cause: An incorrect format was given for the Value.

Action: Check the format of the Value and correct it.
Level: 32

Type: ERROR

Impact: Other

ODI-20711: ODI-20711: The Step Name is mandatory.

Cause: The Step Name field was not entered.

Action: Provide the name of the Step.
Level: 32

Type: ERROR

Impact: Other

ODI-20712: ODI-20712: The Variable is mandatory.

Cause: A Variable was not selected.

Action: Select a Variable.
Level: 32

Type: ERROR

Impact: Other

ODI-20713: ODI-20713: The Scenario is mandatory.

Cause: A Scenario was not selected.

Action: Select a Scenario.
Level: 32

Type: ERROR

Impact: Other

ODI-20714: ODI-20714: The Context is mandatory.

Cause: A Context was not selected for execution.

Action: Select an execution Context.
Level: 32

Type: ERROR

Impact: Other

ODI-20715: ODI-20715: The Logical Agent is mandatory.

Cause: A Logical Agent was not selected for execution.

Action: Select a Logical Agent.
Level: 32

Type: ERROR

Impact: Other

ODI-20716: ODI-20716: No Physical Agent is defined for the selected Logical Agent and Context. Edit Logical Agent "{0}", and define a Physical Agent for Context "{1}".

Cause: There was no Physical Agent associated with this Logical Agent in the specified context.

Action: Associate a Physical Agent with the Logical Agent in the selected context.
Level: 32

Type: ERROR

Impact: Other

ODI-20717: ODI-20717: No Physical Agents are running. A Physical Agent must be running in order to Restart a Load Plan.

Cause: There were no Physical Agents running.

Action: Start a Physical Agent before restarting the Load Plan.
Level: 32

Type: ERROR

Impact: Other

ODI-20718: ODI-20718: No Physical Agents are running. A Physical Agent must be running in order to Stop a Load Plan.

Cause: There were no Physical Agents running.

Action: Start the Agent before executing the Load Plan.
Level: 32

Type: ERROR

Impact: Other

ODI-20719: ODI-20719: Scenario "{0}" is not found.

Cause: The scenario was not found.

Action: Specify an existing scenario.
Level: 32

Type: ERROR

Impact: Other

ODI-20720: ODI-20720: Physical Agent "{0}" - which is defined in Logical Agent "{1}" to be used for Context "{2}" - is not responding. Verify that Physical Agent "{0}" has been started.

Cause: The Physical Agent was not reachable.

Action: Check the Physical Agent and start it.
Level: 32

Type: ERROR

Impact: Other

ODI-20721: ODI-20721: Interface contains one or more errors. You should correct the errors before attempting to execute it

Cause: The interface contains errors which prevent it from being executed.

Action: Review the errors shown in the interface editor and update the interface to fix the problems.
Level: 32

Type: ERROR

Impact: Other

ODI-20722: ODI-20722: Cannot display data. Source alias is {0} characters long which is longer than allowed by the technology ({1}). Please review the technology settings in Topology.

Cause: Source alias exceeded the limit allowed by its technology.

Action: Ensure the maximum table name length setting in the corresponding technology is correct. Consider changing source alias to comply.
Level: 32

Type: ERROR

Impact: Other

ODI-20723: ODI-20723: There is no any version of scenario {0} found. A scenario of the step {1} cannot be refreshed.

Cause: The scenario of step was not found.

Action: Check if specified scenario for this step is correct.
Level: 32

Type: WARNING

Impact: Other

ODI-20724: ODI-20724: Journalized data not found. Journal data view: {0}

Cause: Journal is not started or is stopped.

Action: Ensure the journal is started: select Changed Data Capture > Journal Data.
Level: 32

Type: ERROR

Impact: Other

ODI-20726: ODI-20726: The Step Name is mandatory.

Cause: The Step Name field was not entered.

Action: Enter a name for the Step.
Level: 32

Type: WARNING

Impact: Other

ODI-20727: ODI-20727: Scenario "{0}" parent is not found.

Cause: The Scenario source object does not exist.

Action: Check if the source object, from which the Scenario was generated, does exist.
Level: 32

Type: ERROR

Impact: Other

ODI-20728: ODI-20728: The column name is mandatory

Cause: The datastore column could not be saved because the mandatory Name field was not entered.

Action: Enter a value in the column name field.
Level: 32

Type: ERROR

Impact: Other

ODI-20729: ODI-20729: {0} is a dependant object of the following object(s) {1} and cannot be removed

Cause: Selected object for removal is a dependent object.

Action: Remove the dependent object first.
Level: 32

Type: ERROR

Impact: Other

ODI-20731: ODI-20731: The parent from which this scenario is generated does not exist anymore so the editor couldn't show the parent related information.

Cause: The editor couldn't show the parent related information because the scenario parent does not exist anymore. This could happen, for example, if you imported the scenario, but didn't import it's parent object.

Action: Try to figure out, why the scenario parent object does not exist. Try to restore the parent.
Level: 32

Type: ERROR

Impact: Other

ODI-20732: ODI-20732: You cannot move a submodel into another model.

Cause: An unsupported operation was attempted.

Action: Submodels cannot be moved into hierarchy of another models.
Level: 32

Type: ERROR

Impact: Other

ODI-20733: ODI-20733: You cannot copy a submodel into another model.

Cause: An unsupported operation was attempted.

Action: Submodels cannot be copied into hierarchy of another models.
Level: 32

Type: ERROR

Impact: Other

ODI-20734: ODI-20734: Changing the name of a user function only impacts the user function itself; it has no impact on objects referencing it.

Cause: The user function name has been updated

Action: It is the user's responsibility to determine where the user function is referenced and to manually change the name of the user function in those places
Level: 32

Type: WARNING

Impact: Other

ODI-20736: ODI-20736: The Name field is mandatory.

Cause: The value for the Name field was not specified.

Action: Enter a name for the Object.
Level: 32

Type: ERROR

Impact: Other

ODI-20737: Could not build WSDL Model.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20741: ODI-20741: This is not a valid Cobol Copybook.

Cause: The file chosen in the Reverse Engineering Cobol Copybook process is not a valid Cobol Copybook.

Action: Ensure the file is a valid Cobol Copybook.
Level: 32

Type: ERROR

Impact: Other

ODI-23001: ODI-23001: The import process failed

Cause: The work repository export file specified could not be imported.

Action: Ensure the specified file is readable and is a valid work repository export file.
Level: 32

Type: ERROR

Impact: Other

ODI-23006: ODI-23006: Agent Test failed

Cause: Agent could not be contacted using the specified connection details.

Action: Ensure the Agent connection details are correct and the Agent is running.
Level: 32

Type: ERROR

Impact: Other

ODI-23007: ODI-23007: Data Source already exists for "{0}".

Cause: The Data Source has already been associated with this Agent.

Action: No action is necessary as the Data Source is already associated with this Agent. Consider removing the Data Source from this Agent and retrying this action.
Level: 32

Type: ERROR

Impact: Other

ODI-23010: ODI-23010: Please enter first a name, an expression and a help text for this language element.

Cause: The Name, Expression or Help Text parameter values for this Language Element were not entered in the Definition panel. These are mandatory parameters.

Action: Return to the Definition panel and ensure the Name, Expression and Help Text parameters have valid values.
Level: 32

Type: ERROR

Impact: Other

ODI-23011: ODI-23011: Name is empty

Cause: A value for the Name parameter of the Language Element Implementation was not entered. This is a mandatory parameter.

Action: Enter a valid value for the Name parameter before saving this Language Element.
Level: 32

Type: ERROR

Impact: Other

ODI-23012: ODI-23012: Expression is empty

Cause: A value for the Expression parameter of the Language Element Implementation was not entered. This is a mandatory parameter.

Action: Enter a valid value for the Expression parameter before saving this Language Element.
Level: 32

Type: ERROR

Impact: Other

ODI-23013: ODI-23013: Help is undefined

Cause: A value for the Help Text parameter of the Language Element Implementation was not entered. This is a mandatory parameter.

Action: Enter a value for the Help Text parameter before saving this Language Element.
Level: 32

Type: ERROR

Impact: Other

ODI-23014: ODI-23014: Technology is undefined

Cause: A value for the Technology parameter of the Language Element Implementation was not entered. This is a mandatory parameter.

Action: Enter a value for the Technology parameter before saving this Language Element.
Level: 32

Type: ERROR

Impact: Other

ODI-23015: ODI-23015: Logical Schema {0} is already linked to a physical schema in context {1}.

Cause: A Physical Schema has already been defined for this Context and Logical Schema combination.

Action: Remove the Context and Logical Schema combination from the Context editor, then retry saving the Physical Schema.
Level: 32

Type: ERROR

Impact: Other

ODI-23016: ODI-23016: The context is either invalid or no longer exists in the database.

Cause: One of the Contexts used by the Physical Schema is invalid or no longer exists in the Master Repository.

Action: Ensure the Context for the Physical Schema is correct by either selecting a valid Context for the Physical Schema or recreating the missing Context.
Level: 32

Type: ERROR

Impact: Other

ODI-23017: ODI-23017: This Physical Schema already exists for this data server.

Cause: A Physical Schema referencing this Data Server has already been defined in the Master Repository.

Action: Specify the correct Physical Schema for this Data Server to use.
Level: 32

Type: ERROR

Impact: Other

ODI-23018: ODI-23018: Unable to connect to Work Repository

Cause: The Work Repository could not be accessed using the connection details defined for it. This may be due to the database or host not being available, or the password could have changed.

Action: Ensure the Work Repository host and database are active. Using the Work Repository editor, ensure the connection details for it are correct.
Level: 32

Type: ERROR

Impact: Other

ODI-23019: ODI-23019: Error Detected during Repository Installation. Invalid connection parameters.

Cause: The repository installation process was unable to connect to the repository database.

Action: Correct any errors identified in the installation log and retry the installation. If the problem persists then contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-23020: ODI-23020: Error Detected during Repository Installation. Invalid External Authentication credentials.

Cause: The ODI Supervisor credentials supplied did not match the credentials held in the External Password Store.

Action: Retry the installation, ensuring the Supervisor user name and password match those held in the external store.
Level: 32

Type: ERROR

Impact: Other

ODI-23021: ODI-23021: Error Detected during Repository Installation. Invalid External Authentication configuration.

Cause: A connection to the External Authentication Store could not be established.

Action: Ensure the External Authentication Store is available and the connection details specified in the JPS configuration file are valid.
Level: 32

Type: ERROR

Impact: Other

ODI-23022: ODI-23022: An error occurred during the generation of the Data Service.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-23023: ODI-23023: The Schema path ({0}) is not supported

Cause: The Model's Physical Schema attempted to define the Schema path using an unsupported protocol (ftp, http or file).

Action: Change the Physical Schema to not use ftp, http or file protocol to reference the file.
Level: 32

Type: ERROR

Impact: Other

ODI-23024: ODI-23024: The URL is mandatory.

Cause: The URL field has not been entered and is a mandatory parameter.

Action: Enter the URL parameter. A template chosen from the drop down list may help to ensure the syntax is correct.
Level: 32

Type: ERROR

Impact: Other

ODI-23025: ODI-23025: The ID is mandatory.

Cause: The Repository ID parameter has not been entered and is a mandatory parameter.

Action: Enter an integer value for the Repository ID parameter.
Level: 32

Type: ERROR

Impact: Other

ODI-23026: ODI-23026: The ID must be an integer value.

Cause: The value entered for the Repository ID is not a valid integer.

Action: Enter an integer value for the Repository ID parameter.
Level: 32

Type: ERROR

Impact: Other

ODI-23027: ODI-23027: The driver is mandatory.

Cause: A JDBC Driver was not specified and is a mandatory parameter.

Action: Select a JDBC Driver from the list of values.
Level: 32

Type: ERROR

Impact: Other

ODI-23028: ODI-23028: The password is mandatory.

Cause: The Supervisor user's Password parameter was not specified.

Action: Enter the Supervisor password.
Level: 32

Type: ERROR

Impact: Other

ODI-23029: ODI-23029: The confirm password is mandatory.

Cause: The Supervisor user's Confirm Password parameter was not specified.

Action: Enter the Supervisor user's password in the Confirm Password parameter.
Level: 32

Type: ERROR

Impact: Other

ODI-23030: ODI-23030: Password and Confirm Password are different

Cause: The Password and Confirm Password parameters are not the same.

Action: Ensure the same value is entered for both the Password and Confirm Password parameters.
Level: 32

Type: ERROR

Impact: Other

ODI-23031: ODI-23031: The Supervisor username is mandatory.

Cause: The Supervisor User parameter was not entered.

Action: Enter a value for the Supervisor User parameter ensuring it matches a user in the external enterprise identify store, or switch to ODI Authentication.
Level: 32

Type: ERROR

Impact: Other

ODI-23032: ODI-23032: Maximum number of sessions cannot be less or equal to 0.

Cause: The Maximum Number of Sessions parameter value was specified as 0.

Action: Change the Maximum Number of Sessions parameter in the Agent Definition tab to a value greater than 0.
Level: 32

Type: ERROR

Impact: Other

ODI-23033: ODI-23033: The file reverse-engineering is only possible for delimited files.

Cause: The file format for the specified file was not delimited.

Action: Select a delimited format file and retry the reverse-engineering action.
Level: 32

Type: ERROR

Impact: Other

ODI-23035: ODI-23035: Can not update the scheduling - This agent may not be running

Cause: The Update Scheduling action could not be performed because the ODI Client could not connect to the Agent.

Action: Check that the Agent connection details are correct and that the agent is running. Use the Agent Test button to check the connection details.
Level: 32

Type: ERROR

Impact: Other

ODI-23036: ODI-23036: Logical Schema not set for this Context

Cause: A Logical Schema entry in the Physical Schema's Context was specified as <Undefined>.

Action: Ensure none of the Logical Schemas on the Physical Schema's Context tab are set to <Undefined>.
Level: 32

Type: ERROR

Impact: Other

ODI-23037: ODI-23037: To use scheduling please associate a Logical Agent to a Physical Agent via the Logical Architecture Accordion in the Topology Navigator

Cause: There are no logical agents available to use for scheduling.

Action: Associate a logical agent with a physical agent using the Topology Navigator and then resubmit your schedule request.
Level: 32

Type: ERROR

Impact: Other

ODI-23038: ODI-23038: Cannot resolve the table name. Check the masks defined for this physical schema.

Cause: The table and schema format could not be calculated. This is because the object mask has not been set for the Physical Schema that contains this table.

Action: From the Topology Navigator edit the Physical Schema containing this table and ensure the Masks parameter value is valid for the schema based on its technology (for example "%SCHEMA.%OBJECT").
Level: 32

Type: ERROR

Impact: Other

ODI-23039: ODI-23039: You cannot carry out this type of export.

Cause: The export type specified is not supported.

Action: Retry the export. If the problem persists then contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-23040: ODI-23040: Import file "{0}" error

Cause: An error occured during the import file process.

Action: Correct any errors identified in the error log and retry the import process. If the problem persists then contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-23042: ODI-23042: An error occurred while changing the repository number.

Cause: An error occured while changing the repository number.

Action: Correct any errors identified in the message log and retry the action. If the problem persists then contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-23043: ODI-23043: The Repository ID must be numeric.

Cause: The value specified for the Repository ID parameter was not a valid numeric value.

Action: Enter a valid numeric value for the Repository ID parameter.
Level: 32

Type: ERROR

Impact: Other

ODI-23044: ODI-23044: The new ID you have chosen is already in use as a table "{0}" primary key. The renumbering has been aborted. No changes have been made.

Cause: The Repository ID specified is already used by an existing object.

Action: Enter a different value for the Repository ID parameter ensuring it is unique within the repository.
Level: 32

Type: ERROR

Impact: Other

ODI-23045: ODI-23045: You may not renumber a repository before version 11. Please upgrade your repository first.

Cause: The renumber functionality is not supported for ODI Repository versions prior to version 11.

Action: Upgrade the repository to version 11 (or higher) and then renumber it.
Level: 32

Type: ERROR

Impact: Other

ODI-23046: ODI-23046: An error was encountered during the test.

Cause: An attempt to connect a Work Repository failed.

Action: Correct any errors identified in the message log. Ensure the Work Repositories are available and the connection information is correctly specified in the Master Repository. Retry the test.
Level: 32

Type: ERROR

Impact: Other

ODI-23047: ODI-23047: Could not connect to the work repository. The renumbering process has been aborted. No changes have been made.

Cause: An attempt to connect a Work Repository failed.

Action: Correct any errors identified in the message log. Ensure the Work Repositories are available and the connection information is correctly specified in the Master Repository. Retry the test.
Level: 32

Type: ERROR

Impact: Other

ODI-23048: ODI-23048: Import report generation error

Cause: The import was performed, but there was an unexpected error while opening the Import Report.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-23049: ODI-23049: Error Detected during Repository Installation

Cause: An error occured during the creation or import of the Master Repository.

Action: Correct any errors described in the message log and retry the installation process. If the problem persists then contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-23050: ODI-23050: The password you entered doesn't match the actual password

Cause: The password you entered doesn't match the actual password

Action: Ensure that the password entered matches the actual password
Level: 32

Type: ERROR

Impact: Other

ODI-23052: ODI-20735: The name given for the Physical Agent is already used by another agent. Please provide another name

Cause: Values for maximum number of thread per session is not valid

Action: Enter valid value for maximum number of threads per session
Level: 32

Type: ERROR

Impact: Other

ODI-23053: ODI-23053: Maximum number of threads cannot be less than maximum number of thread per session.

Cause: Maximum number of threads less than maximum number of thread per session.

Action: Enter valid values for maximum number of threads and maximum number of thread per session
Level: 32

Type: ERROR

Impact: Other

ODI-23054: ODI-23054: Maximum number of cache entries cannot be less than zero.

Cause: Values for maximum number of cache entries is not valid

Action: Enter valid values for maximum number of cache entries
Level: 32

Type: ERROR

Impact: Other

ODI-23055: ODI-23055: Session Blueprint Lifetime cannot be less than zero.

Cause: Value for session blueprint lifetime is not valid

Action: Enter valid values forsession blueprint lifetime
Level: 32

Type: ERROR

Impact: Other

ODI-23056: ODI-23056: Syntax of condition "{0}" is not valid.

Cause: The entered condition has invalid syntax.

Action: Specify the valid condition expression.
Level: 32

Type: ERROR

Impact: Other

ODI-23058: ODI-23058: This Technology does not support multiple schemas.

Cause: Attempt to create multiple Physical Schemas for Technologies that support only one Schema.

Action: The solution for Technologies that do not support multiple Physical Schemas is to create separate Data Dervers from the Physical Schemas.
Level: 32

Type: ERROR

Impact: Other

ODI-24004: ODI-24004: There are no supervisor accounts in the ODI repository with matching entries in the identity store. Please provide a suitable supervisor account.

Cause: The ODI repository does not have any supervisor account that matches the entries in the identity store.

Action: Create a supervisor account in the ODI repository that matches an entry in the identify store.
Level: 32

Type: ERROR

Impact: Other

ODI-24005: ODI-24005: An error occurred while checking the status of the master repository.

Cause: An unexpected error occurred.

Action: Check the exception to see if it gives details about the error and contact Oracle Support Services for further assistance.
Level: 32

Type: ERROR

Impact: Other

ODI-24006: ODI-24006: An error occurred while switching the authentication mode for the master repository.

Cause: An unexpected error occurred.

Action: Check the exception to see if it gives details about the error and contact Oracle Support Services for further assistance.
Level: 32

Type: ERROR

Impact: Other

ODI-24007: ODI-24007: Rules should not have empty conditions.

Cause: Rules associated with policy have empty conditions.

Action: Create rules with conditions associated with them.
Level: 32

Type: ERROR

Impact: Other

ODI-25001: ODI-25001: Unable to input a larger element

Cause: The total length of all keywords exceeds the maximum length.

Action: Remove one or more of the keywords, or decrease their lengths.
Level: 32

Type: ERROR

Impact: Other

ODI-25002: ODI-25002: The end date cannot be before the start date.

Cause: The end date is before the start date.

Action: Set the end date to be after the start date.
Level: 32

Type: ERROR

Impact: Other

ODI-25003: ODI-25003: Error while starting session

Cause: An unexpected error occured while starting the session.

Action: Check the error details for further information and contact Oracle Support Services for further assistance.
Level: 32

Type: ERROR

Impact: Other

ODI-25004: ODI-25004: Date Format Not Valid

Cause: One of the Date fields is invalid. This may be the From or To Date.

Action: Click the button to the right of the field to invoke a dialog for entering a valid Time and Date.
Level: 32

Type: ERROR

Impact: Other

ODI-25005: ODI-25005: Incorrect date format . The format is {0}.

Cause: The date format is incorrect.

Action: Use the format that is presented in the error message.
Level: 32

Type: ERROR

Impact: Other

ODI-25006: ODI-25006: At least one agent must be selected.

Cause: Agent selection is mandatory.

Action: Select at least one agent to clean stale sessions.
Level: 32

Type: ERROR

Impact: Other

ODI-25007: ODI-25007: At least one work repository must be selected.

Cause: Work repository selection is mandatory.

Action: Select at least one work repository to clean stale sessions.
Level: 32

Type: ERROR

Impact: Other

ODI-26001: ODI-26001: Boolean does not correspond to the Field Update Object Layer.

Cause: The repository contained an invalid value of the Field Update property for a checkbox or radio group.

Action: Ensure the repository value is a boolean for checkbox or a valid action command for a radio group.
Level: 32

Type: ERROR

Impact: Other

ODI-26002: ODI-26002: This object is referenced by another object. View the details for more information. You may also see where this object is used in the hierarchy.

Cause: The specified object could not be used because it is referenced by another object.

Action: Remove references to this object. The "Uses" hierarchy may be useful in finding objects references.
Level: 32

Type: ERROR

Impact: Other

ODI-26003: ODI-26003: This object cannot be removed: it is referenced by another object.

Cause: The specified object could not be deleted because it is referenced by another object.

Action: Remove references to this object before deleting it. The "Uses" hierarchy may be useful in finding objects references.
Level: 32

Type: ERROR

Impact: Other

ODI-26004: ODI-26004: Action denied:

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26005: ODI-26005: You are importing an object from another repository with the same identifier. It is forbidden.

Cause: An object in the import file has an identifier which already exists in the repository.

Action: Consider manually changing the "com.sunopsis.dwg.dwgobj.SnpImportRep" object section of the import XML file to use a unique identifier.
Level: 32

Type: ERROR

Impact: Other

ODI-26006: ODI-26006: The specified encryption key is invalid.

Cause: The encryption key specified was found to be invalid during the decrypting phase.

Action: Ensure a valid encryption key is utilized.
Level: 32

Type: ERROR

Impact: Other

ODI-26007: ODI-26007: KM or Procedure not encrypted. No decryption was performed.

Cause: Decryption was requested for a non-encypted KM or Procedure.

Action: Do not attempt to decrypt a non-encrypted KM or Procedure.
Level: 32

Type: ERROR

Impact: Other

ODI-26008: ODI-26008: Scenario not encrypted. No decryption was performed.

Cause: Decryption was requested for a non-encypted Scenario.

Action: Do not attempt to decrypt a non-encrypted Scenario.
Level: 32

Type: ERROR

Impact: Other

ODI-26009: ODI-26009: Action not encrypted. No decryption was performed.

Cause: Decryption was requested for a non-encypted Action.

Action: Do not attempt to decrypt a non-encrypted Action.
Level: 32

Type: ERROR

Impact: Other

ODI-26010: ODI-26010: Incompatible key or encrypted data.

Cause: The data used for the key was invalid. It is likely the data decryption failed.

Action: Ensure the encrypted data is correct and the decryption key is correctly specified.
Level: 32

Type: ERROR

Impact: Other

ODI-26011: ODI-26011: unable to find specified encryption API

Cause: The specified cryptographic algorithm requested was not available in the environment.

Action: Ensure the environment can access the DES/ECB/PKCS5Padding algorithms and padding.
Level: 32

Type: ERROR

Impact: Other

ODI-26012: ODI-26012: invalid encrypted data.

Cause: The BASE64 content may be invalid or the zip file contents may be corrupted.

Action: Ensure the encrypted data is correct and the decryption key is correctly specified.
Level: 32

Type: ERROR

Impact: Other

ODI-26013: ODI-26013: Your security parameters are insufficient to perform this action.

Cause: The ODI user security parameters do not specifically permit the user to perform this particular action.

Action: Ensure this ODI user is granted the security access to perform this action.
Level: 32

Type: ERROR

Impact: Other

ODI-26014: ODI-26014: The code of your {0} is already used by another {1}. Please give another code to save this {2}.

Cause: The value entered for code must be unique for the entire work repository.

Action: Ensure the a unique value is entered.
Level: 32

Type: ERROR

Impact: Other

ODI-26015: ODI-26015: You do not have sufficient privileges to perform this operation.

Cause: The ODI user security parameters do not specifically permit the user to perform this particular operation.

Action: Ensure this ODI user is granted the security access to perform this operation.
Level: 32

Type: ERROR

Impact: Security

ODI-26016: ODI-26016: The requested operation cannot succeed. The object no longer exists.

Cause: The specified ODI object cannot be accessed because it no longer exists in the repository (it may have been deleted by another ODI user).

Action: Recreate the specified ODI object. Consider importing the object from a backup.
Level: 32

Type: ERROR

Impact: Other

ODI-26017: ODI-26017: Error.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26018: ODI-26018: Key Error.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26019: ODI-26019: Action Denied.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26020: ODI-26020: Retrieve method incorrect.

Cause: Retrieve method is incorrect. Must be "set" or "get".

Action: Please change the retrieve method to "set" or "get".
Level: 32

Type: ERROR

Impact: Other

ODI-26021: ODI-26021: Object initialization denied.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26022: ODI-26022: Unrecoverable error during object saving.

Cause: The object could not be saved. This is possibly due to a repository connection error, or inconsistent data values supplied. It's also possible that the object was modified by another user.

Action: Ensure the repository database is available and the data values supplied are valid. Try to save changed data, then refresh edited object and apply changed data again.
Level: 32

Type: ERROR

Impact: Other

ODI-26023: ODI-26023: Cannot create object.

Cause: An unexpected error occured during the object creation process.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-26024: ODI-26024: Cannot stop update operation.

Cause: An unexpected error occured during the update operation.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-26025: ODI-26025: Display Initialization denied.

Cause: An unexpected error occured during the display initialization process.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-26026: ODI-26026: Cannot refresh.

Cause: An unexpected error occured during the refresh process.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-26027: ODI-26027: Security not set for the instance. The instance will not be added to the tree.

Cause: Instance security permissions "By repository" were choosen but a concrete repository is not specified.

Action: Ensure a repository is specified.
Level: 32

Type: ERROR

Impact: Security

ODI-26028: ODI-26028: Cannot save your modifications.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26029: ODI-26029: Could not deploy the datasource automatically.

Cause: Weblogic Administration server is not up and running, the server connection parameters are wrong.

Action: Please check Weblogic Administration server connection parameters and the server state.
Level: 32

Type: ERROR

Impact: Other

ODI-26030: ODI-26030: The new password does not meet the password policy. Your change could not be saved.

Cause: The new password does not meet the password policy.

Action: Please verify that the new password meets the password policy (go to the "Security Navigator -> Password Policy...").
Level: 32

Type: ERROR

Impact: Other

ODI-26031: ODI-26031: You may not delete work repository {0} because you are connected to it. To delete this repository, reconnect to a different work repository or use a master repository only connection.

Cause: Deletion of a work repository which is currently connected is not supported.

Action: Disconnect from the repository and then connect utilizing a Master Repository Only connection or a different work repository before attempting to delete the specified work repository.
Level: 32

Type: ERROR

Impact: Other

ODI-26032: ODI-26032: This object was modified by {0} on {1} at {2}. Your changes cannot be saved.

Cause: The object was changed in the repository after the editor was opened for this object.

Action: Close the editor without saving changes. Open the editor again and reapply the edits and save. Note: consider using the lock object facility to disallow current modifications to an object.
Level: 32

Type: ERROR

Impact: Other

ODI-26033: ODI-26033: You cannot edit this object because it is locked by another user ({0}). You can only view it.

Cause: The ODI object opened for editing is locked by another user. Other ODI users can only view such objects.

Action: Try to edit the object later.
Level: 32

Type: ERROR

Impact: Other

ODI-26034: ODI-26034: An error occurred while deleting executions.

Cause: The specified executions could not be deleted. This is possibly caused by the repository database connection problems.

Action: Retry to delete the executions. If problem persists, contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-26035: ODI-26035: Error.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26036: ODI-26036: Error while encrypting.

Cause: A general error occured during the ecrypting process, possibly caused by caused by repository database access problems, lack of security permissions, or encryption engine failures,

Action: Retry the encrypt action again.
Level: 32

Type: ERROR

Impact: Other

ODI-26037: ODI-26037: Encryption key is not valid.

Cause: An invalid encryption key was entered causing an encryption engine failure.

Action: Enter a valid encryption key and retry the action.
Level: 32

Type: ERROR

Impact: Other

ODI-26038: ODI-26038: Unable to execute, the selected Logical Agent is not associated to a Physical Agent in the desired Context.

Cause: A Logical Agent was not associated with this Physical Agent in this Context.

Action: Ensure a valid "Logical Agent - Physical Agent" association exists in the desired Context.
Level: 32

Type: ERROR

Impact: Other

ODI-26039: ODI-26039: Connection failed.

Cause: The attempt to connect to the repository failed. This may be due to one or more of the following: invalid connection parameters specified, database problems, network problems.

Action: Ensure the repository database is available and acceccesible and the repository connection parameters are correct.
Level: 32

Type: ERROR

Impact: Other

ODI-26040: ODI-26040: error while updating

Cause: Failed to update the ODI logins file: snps_login_work.xml.

Action: Ensure write-access is granted to the ODI logins file: snps_login_work.xml.
Level: 32

Type: ERROR

Impact: Other

ODI-26041: ODI-26041: Error while attempting to get FieldData from ObjectDisplay.

Cause: An unexpected error occured obtaining FieldData from ObjectDisplay.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-26042: ODI-26042: Error while attempting to set FieldUpdate from ObjectUpdate.

Cause: An unexpected error occured updating FieldUpdate from ObjectUpdate.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-26043: ODI-26043: Window closing cancelled by the User.

Cause: User asked to close the parent window where child lines were modified.

Action: No action performed on that.
Level: 32

Type: ERROR

Impact: Other

ODI-26044: ODI-26044: Host Variable Not Found.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26045: ODI-26045: Unable to perform the drop operation.

Cause: Dropped entity is invalid.

Action: Check whether the dropped entity is valid and perform the drag-n-drop action again.
Level: 32

Type: ERROR

Impact: Other

ODI-26046: ODI-26046: MethodGetter was not found

Cause: An unexpected error occured obtaining the getter method.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-26047: ODI-26047: Object on method setObjectDisplay(Object pObjectDisplay) is not an array.

Cause: This is caused by programmatic error.

Action: ODI users should normally never see this message.
Level: 32

Type: ERROR

Impact: Other

ODI-26048: ODI-26048: Object on method setObjectDisplay(Object pObjectDisplay) is not a vector.

Cause: This is caused by programmatic error.

Action: ODI users should normally never see this message.
Level: 32

Type: ERROR

Impact: Other

ODI-26049: ODI-26049: Parameters not valid.

Cause: An unexpected error occured due to an invalid parameter value.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-26050: ODI-26050: Master repository not installed on this connection.

Cause: This is caused by programmatic error.

Action: ODI users should normally never see this message.
Level: 32

Type: ERROR

Impact: Other

ODI-26051: ODI-26051: XML Export Error.

Cause: An error occured during the creation of the XML Export file.

Action: Ensure the repository is accessible and the export file and its directory are writable.
Level: 32

Type: ERROR

Impact: Other

ODI-26052: ODI-26052: XML Import Error.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26053: ODI-26053: An error occurred during initialization.

Cause: Initialization failed possibly due a repository access failure or insufficient ODI security permissions.

Action: Ensure the repository database is available, and the ODI user security permissions permit connection.
Level: 32

Type: ERROR

Impact: Other

ODI-26054: ODI-26054: Page not available.

Cause: The selected page number was invalid.

Action: Ensure the page number entered is greater than 0 and less than the total number of pages.
Level: 32

Type: ERROR

Impact: Other

ODI-26055: ODI-26055: The password violates the following rule: "{0}". Select another password.

Cause: The password supplied was invalid.

Action: Enter a valid password.
Level: 32

Type: ERROR

Impact: Other

ODI-26056: ODI-26056: Error while disconnecting.

Cause: This error is occured while closing the repository database connection after "Test query" action completed.

Action: This error may be ignored.
Level: 32

Type: ERROR

Impact: Other

ODI-26057: ODI-26057: Unable to connect the agent. The agent is probably not started.

Cause: The connection request to the agent failed.

Action: Ensure the agent is started and available. Ensure the connection information is valid.
Level: 32

Type: ERROR

Impact: Other

ODI-26058: ODI-26058: Unable to connect the agent. The agent URL cannot be found.

Cause: The connection request to the agent failed using the given URL.

Action: Ensure the agent is started and available. Ensure the connection URL information is valid.
Level: 32

Type: ERROR

Impact: Other

ODI-26059: ODI-26059: Object on method setObjectDisplay(Object pObjectDisplay) is not a List.

Cause: An unexpected error occured setting ObjectData.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-26060: ODI-26060: The Password and Confirmation Password do not match.

Cause: The values entered for Password and Confirmation Password did not match.

Action: Enter the same value for Password and Confirmation Password.
Level: 32

Type: ERROR

Impact: Other

ODI-26061: ODI-26061: The minimum password length is {0} characters.

Cause: The length of the Password entered is less than specified in password policy rule.

Action: Enter a Password whose length is greater than or equal to the specified minimum length.
Level: 32

Type: ERROR

Impact: Other

ODI-26062: ODI-26062: The password violates the following rule: "{0}". Select another password.

Cause: The password supplied was invalid.

Action: Enter a valid password.
Level: 32

Type: ERROR

Impact: Other

ODI-26063: ODI-26063: Invalid password.

Cause: The password supplied was invalid.

Action: Enter a valid password.
Level: 32

Type: ERROR

Impact: Other

ODI-26064: ODI-26064: Error while exporting.

Cause: An error occured during the creation of the Export file.

Action: Ensure the repository is accessible and the export file and its directory are writable.
Level: 32

Type: ERROR

Impact: Other

ODI-26065: ODI-26065: You must specify all the options.

Cause: This is caused by programmatic error.

Action: ODI users should normally never see this message.
Level: 32

Type: ERROR

Impact: Other

ODI-26066: ODI-26066: An unexpected error has occurred.

Cause: An unexpected error occured this process.

Action: Retry action. If problem persists then contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-26067: ODI-26067: mandatory field "Java charset" not entered

Cause: A value for the "Java character set" field was not entered.

Action: Enter a value for the "Java character set" field.
Level: 32

Type: ERROR

Impact: Other

ODI-26068: ODI-26068: unable to load export list in the module: {0}

Cause: The contents of the export file list was not formatted correctly.

Action: Correct the format of the export list file specified.
Level: 32

Type: ERROR

Impact: Other

ODI-26069: ODI-26069: The specified export directory does not exist.

Cause: The specified export directory is invalid.

Action: Ensure the specified export directory exists and is writable.
Level: 32

Type: ERROR

Impact: Other

ODI-26070: ODI-26070: The Open Tool class name must not begin with "Snp" or "Odi".

Cause: The Open Tool class name begins with "Snp" or "Odi".

Action: Ensure the Open Tool class name does not begin with "Snp" or "Odi".
Level: 32

Type: ERROR

Impact: Other

ODI-26071: ODI-26071: Open Tool not activated. Your Open Tool references a class which not found.

Cause: The class name specified in this Open Tool was not found.

Action: Ensure the Open Tool class name specified is valid and available in the class path.
Level: 32

Type: ERROR

Impact: Other

ODI-26072: ODI-26072: Your Open Tool has been installed. You can now use it in a procedure or package.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26073: ODI-26073: Could not activate Open Tool. Check that it is in the "oracledi/userlib" directory.

Cause: The Open Tool references a class which was not found.

Action: Ensure the Open Tool class exists in the "oracledi/userlib" directory.
Level: 32

Type: ERROR

Impact: Other

ODI-26074: ODI-26074: Policy "Name" is a mandatory field.

Cause: A value for the Policy "Name" field value was not entered.

Action: Enter a value for the Policy "Name" field.
Level: 32

Type: ERROR

Impact: Other

ODI-26075: ODI-26075: Policy "Name" must be unique.

Cause: A Policy with the same name already exists.

Action: Enter a unique value in Policy "Name" field.
Level: 32

Type: ERROR

Impact: Other

ODI-26076: ODI-26076: You do not have enough memory to generate this report. Increase the maximum Java heap size value (-Xmx).

Cause: There was not enough memory allocated to generate the report.

Action: Increase the maximum Java heap size value by using the "-Xmx" JVM option.
Level: 32

Type: ERROR

Impact: Other

ODI-26077: ODI-26077: Target file name is not specified.

Cause: The Target file name is mandatory and was not specified.

Action: Enter a value for the target file name.
Level: 32

Type: ERROR

Impact: Other

ODI-26078: ODI-26078: Error while creating the version

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26079: ODI-26079: Version already exists, versioning aborted.

Cause: A version with the specified version number already exists.

Action: Enter a unique version number.
Level: 32

Type: ERROR

Impact: Other

ODI-26080: ODI-26080: Unable to delete version {0} for {1} {2}. It is referenced by solution {3}

Cause: Deletion of a version of an object referenced by a Solution was attempted.

Action: Delete the solution referencing the object version. Then retry deleting the object version.
Level: 32

Type: ERROR

Impact: Other

ODI-26081: ODI-26081: Unable to delete version {0} for {1} {2}. It is referenced by version {3} of solution {4}

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26082: ODI-26082: No difference found

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26083: ODI-26083: No difference found.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26084: ODI-26084: Could not compare versions of different objects.

Cause: Objects of different types were selected for comparison.

Action: Select objects of the same type before performing comparison.
Level: 32

Type: ERROR

Impact: Other

ODI-26085: ODI-26085: You cannot restore several versions of the same object.

Cause: Multiple versions were selected for restoring.

Action: Select a single version when performing this action.
Level: 32

Type: ERROR

Impact: Other

ODI-26086: ODI-26086: You cannot select more than one version at the same time.

Cause: Multiple version were selected for this action.

Action: Select a single version when performing this action.
Level: 32

Type: ERROR

Impact: Other

ODI-26087: ODI-26087: You must select a version.

Cause: A version was not selected.

Action: Select a version before performing this action.
Level: 32

Type: ERROR

Impact: Other

ODI-26088: ODI-26088: You must select the version to restore.

Cause: A version to restore was not selected.

Action: Select a version to restore.
Level: 32

Type: ERROR

Impact: Other

ODI-26089: ODI-26089: This object is currently locked by user: {0}. Version restoration cancelled.

Cause: The object selected for restoration was locked by another user.

Action: Ensure the selected object is not locked by another user before retrying the operation.
Level: 32

Type: ERROR

Impact: Other

ODI-26090: ODI-26090: Object version list is empty.

Cause: The object selected was not versioned.

Action: Select a versioned object before retrying the operation.
Level: 32

Type: ERROR

Impact: Other

ODI-26091: ODI-26091: An array with an invalid size was passed to SnpsObjectTableColumnTextIntrospectMapper.createMapFromArrayOfArrays.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26092: ODI-26092: Table Model must have at least one Column.

Cause: The Model for this Table did not contain any Columns.

Action: Add at least one Column to the Table's Model.
Level: 32

Type: ERROR

Impact: Other

ODI-26093: ODI-26093: Unable to open window.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26094: ODI-26094: Your license does not allow Changed Data Capture operations.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26095: ODI-26095: This object is locked by {0}. You cannot edit it unless it is unlocked.

Cause: Object could not be opened for write access because it was already locked by another user.

Action: Ensure the selected object is not locked by another user before retrying the operation.
Level: 32

Type: ERROR

Impact: Other

ODI-26096: ODI-26096: Replacement of object failed.

Cause: The file specified did not contain correctly formed XML.

Action: Ensure the XML in the specified file is valid before retrying the operation.
Level: 32

Type: ERROR

Impact: Other

ODI-26097: ODI-26097: Replace failed due to an SQL exception.

Cause: The file used to replace this object is not a valid XML format.

Action: Select a valid XML file format before performing this replace object action.
Level: 32

Type: ERROR

Impact: Other

ODI-26098: ODI-26098: You must specify an Export Path or File.

Cause: Either the Export Path or File was not specified.

Action: Specify a value for either the Export Path or File.
Level: 32

Type: ERROR

Impact: Other

ODI-26099: ODI-26099: You don't have the appropriate license to use this KM

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26100: ODI-26100: You don't have the appropriate privileges on Step objects.

Cause: Package Steps operation failed due to insufficient ODI security permissions.

Action: Ensure the ODI user security permissions are correct for the Package Steps object.
Level: 32

Type: ERROR

Impact: Other

ODI-26101: ODI-26101: The Data Check cannot be performed. A CKM is not selected on the Model.

Cause: No CKM was assigned to the Model.

Action: Enter a CKM for the Model before performing the Data Check. Consider using the Model editor to make this entry.
Level: 32

Type: ERROR

Impact: Other

ODI-26102: ODI-26102: The Service cannot be generated. An Application Server is not selected on the Model.

Cause: No Application Server was assigned to the Model.

Action: Enter an Application Server for the Model before performing Generate Service. Consider using the Model editor to make entry.
Level: 32

Type: ERROR

Impact: Other

ODI-26103: ODI-26103: You must specify a connection parameter

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26104: ODI-26104: You must specify a query parameter

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26105: ODI-26105: Test failed

Cause: The value of Schema, Table, Column or Filter was invalid.

Action: Ensure the Schema, Table, Column and Filter are valid. Consult the details for additional information.
Level: 32

Type: ERROR

Impact: Other

ODI-26106: ODI-26106: Decryption failed. Data has been restored.

Cause: The Decryption process failed.

Action: Consult the details for additional information.
Level: 32

Type: ERROR

Impact: Other

ODI-26107: ODI-26107: Cannot find this {0} icon

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26108: ODI-26108: The specified path is not valid.

Cause: The specified path was invalid or was not found on the file system.

Action: Ensure a valid file system path is entered.
Level: 32

Type: ERROR

Impact: Other

ODI-26109: ODI-26109: Error while reading the search criteria. Invalid file

Cause: The selected file did not contain search criteria in a valid format.

Action: Ensure the selected file is one exported from the ODI search UI and contains correctly formatted search criteria information.
Level: 32

Type: ERROR

Impact: Other

ODI-26110: ODI-26110: An error occurred while saving.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26111: ODI-26111: Error while accessing the file

Cause: The specified file could not be opened.

Action: Ensure the specified file exists and is accessible.
Level: 32

Type: ERROR

Impact: Other

ODI-26112: ODI-26112: Error while performing the search

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26113: ODI-26113: XML parser configuration error

Cause: The selected file is not a valid search criteria file format.

Action: Select a valid search criteria file exported from the ODI search UI.
Level: 32

Type: ERROR

Impact: Other

ODI-26114: ODI-26114: Host cannot be empty.

Cause: The Host field is mandatory and was not specified.

Action: Enter a valid Host name.
Level: 32

Type: ERROR

Impact: Other

ODI-26115: ODI-26115: Port number must be an integer between 1024 and 65535.

Cause: The value for Port Number was not valid.

Action: Enter a valid integer value between 1024 and 65535 for Port Number.
Level: 32

Type: ERROR

Impact: Other

ODI-26116: ODI-26116: User cannot be empty.

Cause: The User field is mandatory and was not supplied.

Action: Enter a valid User Name.
Level: 32

Type: ERROR

Impact: Other

ODI-26117: ODI-26117: Connection failed. Reason:

Cause: Could not connect to a repository with the specified connection details.

Action: Ensure the repository database is available and valid connection details are supplied.
Level: 32

Type: ERROR

Impact: Other

ODI-26118: ODI-26118: External password storage connection test failed.

Cause: Could not connect to the external password storage with the specified connection details.

Action: Ensure the external password storage is available and valid connection details are supplied.
Level: 32

Type: ERROR

Impact: Other

ODI-26119: ODI-26119: Exception when computing the value

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26120: ODI-26120: Fields compared are not the same

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26121: ODI-26121: Error while exploring version

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26122: ODI-26122: Exception when getting the children list

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26123: ODI-26123: Cannot connect to the repository with the provided login information.

Cause: Could not connect to a repository with the specified connection details.

Action: Ensure the repository database is available and valid connection details are supplied.
Level: 32

Type: ERROR

Impact: Other

ODI-26124: ODI-26124: Exception during connection to the repository with the provided login information:

Cause: Could not connect to a repository with the specified connection details.

Action: Ensure the repository database is available and valid connection details are supplied.
Level: 32

Type: ERROR

Impact: Other

ODI-26125: ODI-26125: The configured external password storage is still accessible. Instead, use the Password Storage Switch service to change the configuration.

Cause: Could not connect to the external password storage with the specified connection details.

Action: Ensure the external password storage is available and valid connection details are supplied. Consider using the Password Storage Switch service to change the configuration.
Level: 32

Type: ERROR

Impact: Other

ODI-26126: ODI-26126: Error while opening window.

Cause: An unexpected error occured while opening window.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-26127: ODI-26127: The selected master repository configured to use internal password storage. Recovery is possible only for external storages.

Cause: Recovery was attempted for a master repository configured to use internal password storage.

Action: Select a master repository not configured to use internal password storage.
Level: 32

Type: ERROR

Impact: Other

ODI-26128: ODI-26128: Unable to open Editor

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26129: ODI-26129: Unable to open Editor: Technology could not be opened twice

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26130: ODI-26130: Could not connect to repository

Cause: Could not connect to a repository with the specified connection details.

Action: Ensure the repository database is available and valid connection details are supplied.
Level: 32

Type: ERROR

Impact: Other

ODI-26131: ODI-26131: Specify Import Path

Cause: A value for Import Path is a mandatory and it was not supplied.

Action: Enter the correct value for the Import Path.
Level: 32

Type: ERROR

Impact: Other

ODI-26132: ODI-26132: Repository id {0} or Repository name {1} is already used in your master repository.

Cause: The ID or Name specified for the master repository were already used.

Action: Enter valid unique values for Repository ID and Repository name.
Level: 32

Type: ERROR

Impact: Other

ODI-26134: ODI-26134: Invalid number format for port number.

Cause: The value specified for Port Number was not in a valid format and number range.

Action: Enter a valid Port Number. See SQL*Net documentation for additional information regarding format and range.
Level: 32

Type: ERROR

Impact: Other

ODI-26135: ODI-26135: The Network Adapter could not establish the connection.

Cause: Connection via the Network Adapter could not be established.

Action: Ensure the network resource is available and the connection details in the Network Adapter are correct..
Level: 32

Type: ERROR

Impact: Other

ODI-26136: ODI-26136: The specified character set is not supported.

Cause: The specified character set was not supported.

Action: Select a supported character set.
Level: 32

Type: ERROR

Impact: Other

ODI-26137: ODI-26137: The context or type are incorrect.

Cause: The selected ODI context is invalid: it was probably removed from the repository database.

Action: Reopen Execution dialog again so that the list of ODI contexts will be reloaded.
Level: 32

Type: ERROR

Impact: Other

ODI-26150: ODI-26150: Incorrect Context.

Cause: A valid Context was not specified.

Action: Select a Context from the list. If none are available then create one from the Topology Navigator.
Level: 32

Type: ERROR

Impact: Other

ODI-26153: ODI-26153: Connection failed; JDBC Error

Cause: An unexpected JDBC error was encountered during the connection process.

Action: Ensure the resource referenced is available and the connection information is correct.
Level: 32

Type: ERROR

Impact: Other

ODI-26155: ODI-26155: No Master Repository on this connection

Cause: A connection to the Master Repository could not be established.

Action: Ensure the Master Repository is available and valid connection details are provided.
Level: 32

Type: ERROR

Impact: Other

ODI-26156: ODI-26156: Designer cannot connect to an Execution repository. The operation will be canceled.

Cause: Unable to establish a connection to the Execution repository.

Action: Ensure the Execution repository is available and the connection details are correct.
Level: 32

Type: ERROR

Impact: Other

ODI-26157: ODI-26157: Connection Error

Cause: A connection to the Master Repository could not be established.

Action: Ensure the Master Repository is available and valid connection details are provided.
Level: 32

Type: ERROR

Impact: Other

ODI-26158: ODI-26158: Work Repository Attachment Error

Cause: A connection to the Work Repository could not be established.

Action: Ensure the Work Repository is available and valid connection details are provided.
Level: 32

Type: ERROR

Impact: Other

ODI-26159: ODI-26159: Error while creating Work Repository

Cause: An unexpected error occurred while creating the Work Repository.

Action: Correct any issues described in the error details.
Level: 32

Type: ERROR

Impact: Other

ODI-26160: ODI-26160: URL not referenced in the list.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26161: ODI-26161: File Not Found

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26162: ODI-26162: Connection failure

Cause: A connection to the repository could not be established.

Action: Ensure the repository is available and valid connection details are provided.
Level: 32

Type: ERROR

Impact: Other

ODI-26163: ODI-26163: Access Denied

Cause: A connection to the repository could not be established because of insufficient user privilege.

Action: Ensure the ODI user has sufficient privilege to connect to the specified repository.
Level: 32

Type: ERROR

Impact: Other

ODI-26164: ODI-26164: The reverse cannot be executed. Your Model will be created.

Cause: The specified technology or driver did not support standard reverse-engineering.

Action: Ensure the technology or driver supports standard reverse-engineering. Otherwise choose Customized Reverse and select an appropriate RKM for the technology.
Level: 32

Type: ERROR

Impact: Other

ODI-26165: ODI-26165: This driver has no match in the URL list

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26166: ODI-26166: The template was not generated: {0}

Cause: The WLS Template could not be generated.

Action: Correct any errors identified in the error log and retry the operation.
Level: 32

Type: ERROR

Impact: Other

ODI-26167: ODI-26167: File System Error: {0}

Cause: Creation of the Server Template file failed due to an error detected by the file system.

Action: Correct any errors identified in the error log. Ensure the file system location is accessible and retry the operation.
Level: 32

Type: ERROR

Impact: Other

ODI-26168: ODI-26168: Client requires a repository with version {0} but the repository version found is {1}

Cause: Could not connect to the repository due to the old repository version.

Action: Update repository to the latest version.
Level: 32

Type: ERROR

Impact: Other

ODI-26169: ODI-26169: JDBC driver is mandatory.

Cause: JDBC driver was not entered.

Action: Provide JDBC driver for database connection.
Level: 32

Type: ERROR

Impact: Other

ODI-26170: ODI-26170: JDBC url is mandatory.

Cause: JDBC url was not entered.

Action: Provide JDBC url for database connection.
Level: 32

Type: ERROR

Impact: Other

ODI-26171: ODI-26171: User is mandatory.

Cause: User was not entered.

Action: Provide user for database connection.
Level: 32

Type: ERROR

Impact: Other

ODI-26172: ODI-26172: Id is mandatory.

Cause: Id was not entered.

Action: Provide work repository ID.
Level: 32

Type: ERROR

Impact: Other

ODI-26173: ODI-26173: Name is mandatory.

Cause: Name was not entered.

Action: Provide work repository name.
Level: 32

Type: ERROR

Impact: Other

ODI-26174: ODI-26174: Database connection is not available.

Cause: Connection error occurred while connecting to the database.

Action: Verify that the Database Connection details are correct and the database is available.
Level: 32

Type: ERROR

Impact: Other

ODI-26175: ODI-26175: Import folder does not exist or not a valid folder.

Cause: Non-existing or invalid folder was specified.

Action: Ensure the specified folder path is correct and refers to an existing folder.
Level: 32

Type: ERROR

Impact: Other

ODI-26176: ODI-26176: Import file does not exist or not a valid file.

Cause: Non-existing or invalid file was specified.

Action: Ensure the specified file path is correct and refers to an existing file.
Level: 32

Type: ERROR

Impact: Other

ODI-26177: ODI-26177: Unable to connect to the DBA user.

Cause: Unable to connect to the DBA account.

Action: Check that the DBA username and password are correct.
Level: 32

Type: ERROR

Impact: Other

ODI-26178: ODI-26178: Unable to connect to the Repository user.

Cause: Unable to connect to the Repository account.

Action: Check that the Repository connection details are correct.
Level: 32

Type: ERROR

Impact: Other

ODI-26179: ODI-26179: Invalid Date Format

Cause: An Invalid Date format was entered in the date filter.

Action: Ensure the date entered is of the required format.
Level: 32

Type: ERROR

Impact: Other

ODI-26180: ODI-26180: Changing the name of a sequence only impacts the sequence itself; it has no impact on objects referencing that sequence

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-26181: ODI-26181: Unable to add a Project knowledge module

Cause: An unsupported action was attempted.

Action: No action required as Project knowledge modules are not a valid selection to be added to a solution.
Level: 32

Type: ERROR

Impact: Other

ODI-26182: ODI-26182: Object was modified by another user and cannot be saved.

Cause: The object could not be saved. It's possible that the object was modified by another user.

Action: Try to save changed data, then refresh edited object and apply changed data again.
Level: 32

Type: ERROR

Impact: Other

ODI-26183: ODI-26183: The maximum password length is {0} characters.

Cause: The entered work repository password length is greater than allowed.

Action: Provide a shorter password.
Level: 32

Type: ERROR

Impact: Other

ODI-26184: ODI-26184: SQL error occurred. See error details for more information.

Cause: SQL error occurred while performing UI action.

Action: If this error is not expected, contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-26185: ODI-26185: File does not exist or cannot be created. See error details for more information.

Cause: UI action tried to open a file which did not exist, or create a file which could not be created due to some reasons.

Action: Make sure the file path is typed correctly. Make sure application has enough file system permissions in order to create a file at the specified path.
Level: 32

Type: ERROR

Impact: Other

ODI-26186: ODI-26186: Character set is not supported. See error details for more information.

Cause: UI action tried to use character encoding which is not supported.

Action: Make sure character set is typed correctly.
Level: 32

Type: ERROR

Impact: Other

ODI-26187: ODI-26187: Unexpected I/O error occurred. See error details for more information.

Cause: UI action caused unexpected I/O error.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-26188: ODI-26188: There is no enough memory to perform this UI action. Increase the maximum Java heap size value (-Xmx).

Cause: UI action requires more memory than available at the current moment.

Action: Increase the maximum Java heap size value by using the "-Xmx" JVM option.
Level: 32

Type: ERROR

Impact: Other

ODI-26189: ODI-26189: Unexpected report generation error occurred. See error details for more information.

Cause: UI action caused unexpected report generation error.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-26190: ODI-26190: A user with same name {0} already exists in ODI. Note: LDAP user name is case insensitive. You have to first drop that user prior to registering or changing this one.

Cause: Due to LDAP user name is case insensitive so ODI will follow same rule in external authenticaiton mode.

Action: Please drop the existing user with same name(ingoring case) first prior to registering this one.
Level: 32

Type: ERROR

Impact: Other

ODI-26191: ODI-26191: You cannot move this object because it is locked by another user ({0}).

Cause: This object was locked by another user.

Action: Wait until object is unlocked.
Level: 32

Type: ERROR

Impact: Other

ODI-26192: ODI-26192: You cannot drag & drop this object because it is locked by another user ({0}).

Cause: This object was locked by another user.

Action: Wait until object is unlocked .
Level: 32

Type: ERROR

Impact: Other

ODI-26193: ODI-26193: You are not allowed to delete master repository.

Cause: User attempt to delete master repository.

Action: Cancel deleting master repository.
Level: 32

Type: ERROR

Impact: Other

ODI-26194: ODI-26194: Database Connection User is mandatory.

Cause: Database Connection User was not entered.

Action: Provide Database Connection User.
Level: 32

Type: ERROR

Impact: Other

ODI-26195: ODI-26195: Database Connection Password is mandatory.

Cause: Database Connection Password was not entered.

Action: Provide Database Connection Password.
Level: 32

Type: ERROR

Impact: Other

ODI-26196: ODI-26196: Failed to migrate login information to new format.

Cause: ODI was not able to migrate login information from old format into the new format.

Action: Make sure that directory %ODI_HOME%/oracledi has write permissions. Try manually copying %ODI_HOME%/oracledi/snps_login_work.xml into %ODI_HOME%/oracledi/snps_login_work_12.xml file.
Level: 32

Type: ERROR

Impact: Other

ODI-26197: ODI-26197: Failed to delete old login information.

Cause: ODI was not able to delete old login information after migration from old format into the new format.

Action: Make sure that directory %ODI_HOME%/oracledi and file %ODI_HOME%/oracledi/snps_login_work.xml have write permissions. Try manually removing %ODI_HOME%/oracledi/snps_login_work.xml file.
Level: 32

Type: ERROR

Impact: Other

ODI-26198: ODI-26198: Passwords do not match.

Cause: Password confirmation doesn't match the entered password.

Action: Make sure that password and password confirmation are the same.
Level: 32

Type: ERROR

Impact: Other

ODI-30000: Error while parsing request file.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-30001: One of the following parameters: {0} or {1} must be defined.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Configuration

ODI-30002: Parameters {0} and {1} cannot be set at the same time.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Configuration

ODI-30003: OdiOSCommand not supported for this operating system. Use tool "OS Command".

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: OperatingSystem

ODI-30004: Agent unreachable

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Network

ODI-30005: One or more child sessions has failed

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30006: No table matches the specified pattern.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30007: No table matches the specified list.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30008: No variable with this name is used in the session.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30009: Can''t rename file: {0} to {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-30010: Can''t delete old file: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-30011: Parameter cannot be null:

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30012: This user does not have the privilege to execute this scenario

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Security

ODI-30013: Context not allowed for this user

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Security

ODI-30014: Cannot create directory

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-30016: Internal error: Invalid datatype

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30017: Unable to create persistence table

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30018: Unable to find the tables

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30019: The Object id is mandatory

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30020: The command is not valid

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30021: Value 0 is not allowed for -GLOBAL_ROWCOUNT.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30022: Version is mandatory ...

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30023: Scenario name is mandatory ...

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30024: File name is mandatory...

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30025: Agent name is mandatory ...

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30026: Either the "{0}" or the "{1}" parameter is mandatory ...

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30027: The parameter -LSCHEMA is mandatory.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30028: The parameter -SUBSCRIBER_NAME is mandatory.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30029: Parameter -RESUME_KEY_COL is mandatory when -RESUME_KEY_VAR is used

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30030: Please do not pass values for both "{0}" and "{1}" options together. These two options together are not supported

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30031: The parameter "{0}" is mandatory.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30032: Unrecognized ODI object type "{0}". Please check the value passed to the parameter "{1}".

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30033: The parameter "-CONTEXT" is mandatory when running from command line.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30034: Only positive integer values are valid for {0} parameter

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30035: Only non-negative integer values are valid for {0} parameter

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30036: This step cannot be executed in execution work repository because the model meta data does not exist

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30037: The specified marker does not exist

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30038: OS command returned {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30039: Parameter -RESUME_KEY_VAR is mandatory when -RESUME_KEY_COL is used

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30040: The -TABLE_NAME parameter is mandatory.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30041: LSCHEMA parameter is mandatory

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30042: SUBSCRIBER_NAME parameter is mandatory

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30043: You cannot use the OPTIMIZED_WAIT option with the current journalizing method.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30044: Invalid parameter

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30045: Impossible to find a valid name on this machine for the "{0}" file

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30046: Session stopped

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30047: You cannot select more than one source.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30048: Unable to find the object with type {0} and identifier {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30049: Version is mandatory ...

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30050: The same file cannot be used as the source and the target.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-30051: File does not exist.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-30052: No file found.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-30053: File name is mandatory ...

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-30054: It is not possible to delete sessions in the queue.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30055: Context is mandatory ...

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30056: Sequence name is mandatory

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30057: The position is a mandatory parameter.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30058: -SCEN_NAME parameter is mandatory.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30059: The number of child sessions in error state is greater or equal to the MAX_CHILD_ERROR parameter

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30060: The parent session "{0}" does not exist.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30061: "{0}" is not a correct value for -OBJECT_TYPE

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30062: There's no table matching the pattern in the database

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30063: -TABLE_NAME and -CDC_SET_NAME cannot be used simultaneously.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30064: You must specify -TABLE_NAME or -CDC_SET_NAME

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30065: Incorrect length at position :{0} for value : {1} expected max size of {2}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30066: All child sessions have failed

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30067: -UNIT_ROW_COUNT and -CDC_SET_NAME cannot be used simultaneously.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30068: Unable to find the table(s): {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30069: You must specify a Project

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30070: You have not specified the export scenarios location.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30071: You have not specified the export location.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30072: Unable to delete a running session

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30073: Unable to delete a waiting session

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30074: {0}: Illegal value

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30075: Cannot be specified at the same time: {0} and {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30076: Unable to save the line number sum

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30077: The variable in use is null.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30078: No message.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30079: Mandatory Parameter "{0}" is missing

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30080: Cannot copy a directory "{0}" to a regular file "{1}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-30081: The source directory file "{0}" does not exist

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-30082: The source directory file "{0}" is not a directory

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-30083: Invalid value "{0}" passed for parameter "{1}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30084: File "{0}" does not exist

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-30085: Cannot copy file with a regular expression to a regular file "{0}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-30086: The FROMDATE {0} should be earlier than the TODATE {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30087: Import failed. No work repository name was defined and the import failed in the master repository.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30088: Timed out. No result.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30089: Source file "{0}" does not exist

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-30090: Scenario name is mandatory ...

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30091: Invalid internal object transition

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30092: Cannot create directory

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-30093: PORT and NAME parameters can''t be used together.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30094: Log files can only be imported in synonym mode INSERT.

Cause: The value of parameter -IMPORT_MODE is invalid for this type of object.

Action: Modify the value of parameter -IMPORT_MODE to SYNONYM_INSERT
Level: 32

Type: ERROR

Impact: Other

ODI-30095: PROMPT option can only be used when ReverseManageShortcut tool is run from ODI UI and on a Local Agent.

Cause: The value of parameter -SHORTCUT_HANDLING_MODE is invalid for this mode of execution.

Action: Modify the value of parameter -SHORTCUT_HANDLING_MODE to ALWAYS_MATERIALIZE or ALWAYS_SKIP
Level: 32

Type: ERROR

Impact: Other

ODI-30096: Invalid shortcut handling mode.

Cause: The value of parameter -SHORTCUT_HANDLING_MODE is invalid.

Action: Modify the value of parameter -SHORTCUT_HANDLING_MODE to ALWAYS_MATERIALIZE or ALWAYS_SKIP or PROMPT.
Level: 32

Type: ERROR

Impact: Other

ODI-30097: -LOCATION parameter is mandatory.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30098: -OBJECT_NAME parameter is mandatory.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30099: -OBJECT_TYPE parameter is mandatory.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30100: -WORKSPACE parameter is mandatory.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30101: Enterprise Data Quality project {0} not found.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30102: Enterprise Data Quality Job {0} not found in Enterprise Data Quality project {1}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30103: Enterprise Data Quality matching query returned with empty or ambiguous result for {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30104: Model Internal ID is not supported when Legacy ID Compatible Mode is switched off.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30105: Internal ID is not supported for "{0}" when Legacy ID Compatible Mode is switched off. Only Global ID is supported.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30106: JAX-WS Dispatch proxy object could not be created. Check ODI Agent log for error messages.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30107: Upgrade key is required for pre-12.x object import.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30108: Target directory "{0}" does not exist

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-30109: Error while polling run status of load plan {0} (instance id {1}, run {2}) for execution completion. Last polled status value: {3}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30110: Execution of load plan {0} (instance id {1}, run {2}) ended in status "{3}" instead of "{4}". {5}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30111: Value for mandatory parameter {0} is missing.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30112: Invalid logical schema selected for PROCESS_LSCHEMA parameter. Oracle Golden Gate process logical schema is expected.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30113: Values for mandatory parameters PROCESS_LSCHEMA and OPERATION are missing.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30114: Oracle GoldenGate process logical schema with the name {0} does not exist.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30115: All selected load plan runs ({0}) have completed, with {1} in Error status.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30116: The number of load plan runs in error status ({0} in error out of {1} completed runs), is at or above the MAX_LP_ERROR limit of {2}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30117: The parent session "{0}" does not exist.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40100: Invalid JDBC URL {0} . No XSD or DTD was provided.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Configuration

ODI-40101: Not Supported

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40102: The parameter {0} has already been specified for {1}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40103: No value provided for JMS_DESTINATION

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40104: The URL {0} does not start with {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40105: Connecting to JMS using URL {0} failed

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40106: JNDI protocol not specified after the JMS XML protocol prefix : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40107: Path separator ":" after JNDI protocol not found {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40108: "//" after colon not found : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40109: Need more information than JNDI hostname. eg: port, provider : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40110: Could not find JNDI host, port, provider info : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40200: Cannot create the initial JNDI context. Check that the JNDI server is running, and that the following URL is correct ({0}).

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40201: Cannot create the initial JNDI context

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40202: Cannot find the target in JNDI ({0})

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40203: Cannot find the Connection Factory ({0}) in JNDI

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40204: The URL cannot be null

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Network

ODI-40205: No connection.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Network

ODI-40206: Problem with getInternalSession

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40207: You must specify the URL parameter

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Configuration

ODI-40208: This function has no effect for this connection

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40209: Unable to create the table

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40210: Unabled to drop the table

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40212: Missing file structure in the request

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40213: Error performing update

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40214: Error creating prepared statement

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40215: Error performing commit

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40216: Error performing update

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40217: Error closing resultset

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40218: Error getting next element in resultset

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40219: Error opening file for insert

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40220: Error creating prepared statement

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40221: Error writing

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40222: Error initialising

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40223: Error performing commit

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40224: Error obtaining connection

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40225: Error performing rollback

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40226: Error initialising

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40227: Error performing commit

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40228: Error obtaining connection

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40229: Error performing rollback

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40300: File is read-only.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40301: Invalid COL ALIAS "{0}" for column "{1}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40302: Invalid format description

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40400: Invalid format description

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40401: Mis-matched start/end delimiters

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40402: File metadata could not be obtained for {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40403: Unable to obtain row structure for file {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40404: Array must not be null

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40405: End must be greater than begin: {0} > {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40406: Bytes are too big for array

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40407: Begin interval must be >= 0: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40408: End interval must not go beyond the size of the pointed array: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40409: Array must not be null

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40410: End must be greater than begin: {0} > {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40411: Begin interval must be >= 0: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40412: End interval must not go beyond the size of the pointed array: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40413: Bytes are too long for array

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40414: Reader has been closed

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40415: File {0} already exists

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40416: Could not create file {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40417: An IOException was caught while creating the file saying {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40418: File not found: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40419: Could not delete file: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40420: Bad String size, hex Strings should have an even size

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40421: Cannot code String {0} into {1} bytes using the encoding {2}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40422: The array of bytes is not a valid number:

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40423: A bad number was found in a COMP3 format: {0} at position {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40424: Cannot code value {0} on {1} bytes.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40425: Bad number in a ZONED format: {0} at position {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40426: Url must start with {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40427: Unknown property: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40428: Could not write header rows to file: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40429: An IOException occured while writing a row saying: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40430: Unknown property

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40431: Could not close output file

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40432: File {0} is read-only

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40433: File {0} was not found

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40434: Could not clone a row of type {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40435: Could not transform data for column {0} value {1} because: {2}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40436: JVM 1.4 at least is required

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Compliance

ODI-40437: Number of bad rows actually detected: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40438: File not found: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40439: Could not read heading rows from file

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40440: Could not close file: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40441: Error reading file: {0} said {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40442: Could not translate value for column {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40443: Could not convert value of type {0} to BigDecimal

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40444: Column not found: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40445: Column {0} > {1}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40446: Column {0} negative or zero.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40447: This type is not valid datatype

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40448: File is read-only.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40449: File not found: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40450: An IOException occured saying: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40451: Column Not Found:

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40452: Missing file structure in the request

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40453: Missing JMS properties in the request

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40454: Missing host variable at index

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40455: Not a numeric value

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40456: A Number datatype was expected instead of :

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40457: Parsing error

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40458: Unknown column datatype

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40459: An IOException occurred saying {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40460: Could not transform the data: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40461: A Date datatype was expected instead of :

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40462: File already exists

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40463: Invalid cursor state

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40464: Invalid descriptor index

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40465: Data array must not be null

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40466: String is too long: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40467: Too many columns on this row

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40468: Row rejected because column {0} contains a bad value.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40469: Value was incorrect for column {0}: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40470: EOF reached but not expected

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40471: Tried to retrieve an int with an {0} object.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40472: Tried to retrieve a short with an {0} object.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40473: This resultset accepts only FETCHFORWARD requests

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40474: This function is unsupported: the software you are using might not be compatible with this driver.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40475: Invalid column name

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40476: Expected a comma.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40477: Cannot have a parameter inside a bare statement: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40478: Could not transform data.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40479: Unrecognized command.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40480: Malformed INSERT statement.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40481: Invalid COL ALIAS "{0}" for column "{1}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40482: Two selected columns have the same alias: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40483: Could not read value {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40484: Could not read null value

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40485: Not a ?

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40486: Could not read value {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40487: Unknown file format

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40488: Invalid COL ALIAS "{0}" for column "{1}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40489: Not Supported

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40490: Datatype {0} is not implemented for now

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40491: ResultSet already closed. Cannot call next() on it.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40500: Unknown parameter : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40501: Syntax: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40502: Can''t begin loading while loading another context

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40503: Creating a new element {0} from the object {1} in DN {2} which contains attributes {3}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40504: Found the key {0} for the element {1} in DN {2}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40505: Entry {0} in {1} has a key {2} which is different from the original key found: {3}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40506: Adding new attribute {0} for object {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40507: Model Builder

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40508: Not finished loading!

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40509: Can''t begin loading while loading another context

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40510: Not finished loading!

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40511: Bad element {0} while in level

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40512: Because an element {0} is not supposed to appear here. Please check your data model.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40513: Entry {0} in {1} has a key {2} which is different from the original key found: {3}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40514: Not implemented

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40515: Not implemented

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40516: Could not add table {0} because the model told us it''s a duplicate. Please try changing the grouping factor.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40517: Could not add table {0} because the model told us it''s a duplicate. Please try changing the grouping factor.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40518: The table {0} already exists in the model and could not be added

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40519: The table {0} is a duplicate root

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40520: The table {0} doesn''t exist

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40521: A NamingException occurred saying {0} because of {1} with the remaining name {2}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40522: Exception {0} occurred saying: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40523: Property {0} is invalid

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40524: Property {0} from the URL is invalid

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40525: Internal connection is null. This shouldn''t happen that way.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40526: A NamingException occured saying: {0} with this explanation: {1} and this remaining name: {2}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40527: Could not read alias bundle because an IOException occurred saying: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40528: A {0} occurred saying: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40529: Could not write alias bundle because an IOException occurred saying {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40530: The schema is now in a read only mode because the technology is not HSQL

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40531: Exception {0} occurred saying: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40532: Could not find the element for row of table {0}: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40533: Element {0} has no identifier so this row could not be updated.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40534: Exception getting original attributes of baseDN={0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40535: Key column {0} has a null value though it''s required

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40536: Deleting attribute {0} from Object {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40537: Deleting object {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40538: Creating attribute value {0} in attribute {1} from Object {2}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40539: Adding object {0} to the database from row {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40540: Modifying attribute value {0} to {1} in attribute {2} from Object {3}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40541: Adding attribute value {0} in attribute {1} from Object {2}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40542: This update is not permitted because it would move the element to another location in the hierarchy.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40543: This update is not permitted because it would move this attribute to another element.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40544: The attribute {0} cannot exist in an element of class {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40545: Modifying attribute value {0} to {1} in attribute {2} from Object {3}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40546: A user has not been provided

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40547: Not Supported

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40548: Parameter {0} has already been specified. Old value : {1} New value : {2}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40549: Invalid value specified for {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40700: Schema {0} cannot be dropped because it is referenced by one or more connections.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40701: Exception {0} occurred saying: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40702: XSD is required for processing flat files

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40703: Root element name is required for processing flat file

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40704: The schema {0} already exists. Use the "REPLACE" option to replace the schema

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40705: The schema parameter is required in the command SET SCHEMA

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40706: This schema doesn''t exist: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40707: No existing schema with this name: "{0}". Please verify that it is the same schema name than the one you specified in your URL connection.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40708: Error synchronizing automatically the schema

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40709: The xml file is required in a LOAD FILE command

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40710: The schema name is mandatory for the CREATE SCHEMA command

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40711: This schema has no DTD and cannot be saved to a XML file

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40712: This table doesn''t exist in the schema so it can''t be the root table: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40713: The file parameter is required to write a file

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40714: Could not find a file to verify: make sure you are on a schema associated with a file or use the "VALIDATE FILE <FileName>" syntax.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40715: Exception {0} occurred saying: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40716: Parameter {0} has been declared twice. Old value : {1} New value : {2}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40717: Unknown parameter : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40718: Could not read the input XML data

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40719: Could not read the XML data because a SAXException occurred saying: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40720: Could not read the XML data because the parser is not configured correctly: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40721: Could not read the XML data because an IOException occurred saying: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40722: The data has been altered: {0} !!!

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40723: XmlParser not validated.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40724: The same connection should have been returned but I got another one

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40725: Custom varchar column size was not correct: {0} instead of 300

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40726: Truncate did not truncate a table

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40727: Custom numeric column size was not correct: {0} instead of 12

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40728: Could not find the row with a pk=20

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40729: Error: Dropping of a schema that is referenced by another connection is allowed!

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40730: Standalone schema type is not compatible with external database storage

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40733: Creating a data inserter which uses prepared statements

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40734: An UnsupportedDatatypeException occurred

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40735: Model type not supported: {0}. Expecting one of dtd, xsd.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40736: IOException occurred

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40737: A parsing exception occurred

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40738: A SAXException was caught while reading the model saying: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40739: A ParserConfigurationException was caught while reading the model

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40740: A duplicate element was found in the DTD/XSD

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40741: A duplicate type was found in the DTD/XSD

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40742: An unknown element was found in the DTD/XSD

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40743: Namespace not found

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40744: Ambiguous name

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40745: Malformed QName

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40746: Unsupported model

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40747: Duplicate attribute

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40748: Duplicate reference to an element

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40749: Conflicting namespaces

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40750: The model generated by the model mapper was not accepted by a validator

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40751: An XMLUnsupportedException was caught

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40752: The DTD file "{0}" doesn''t exist: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40753: No DTD is associated to the file {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40754: File {0} is already locked by another instance of the XML driver.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40755: Could not lock file {0}: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40756: No DTD was found so no data was retrieved

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40757: An exception occurred while reading the file

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40758: Malformed qualified name in root properties: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40759: Both the schema "{0}" and the file "{1}" have been modified!

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40760: The root table ({0}) doesn''t exist!

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40761: Not enough memory to read the XML file

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40762: Cannot write the file because this schema is opened in a read-only mode.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40763: Invalid property definition: "{0}" in "{1}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40764: File {0} is not locked or cannot be unlocked.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40765: Cannot write to an URL.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40766: Could not delete existing file {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40767: Could not rename existing file {0} to make a backup

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40768: Could not save the file {0} because a {1} occurred and said: {2}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40769: Could not close the file. You should probably close your application: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40770: Could not delete the output file after an error occurred

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40771: Could not restore the original file after an error occurred

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40772: No DTD was found so no data was retrieved

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40773: Connection type not supported: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40774: No DTD was found so no data was retrieved

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40775: Should not occur for prefix generation

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40776: Could not free the file {0}. Verify that no .lck file is left.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40777: Found PCDATA in element {0} with values ({1})

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40778: Attribute {0} of element {1} doesn''t exist in the DTD.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40779: Root element was not found in the XML Model

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40780: Root element is ambiguous in the XML Model

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40781: Could not find the prefix {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40782: Could not find the namespace for the root element

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40783: Root element has a malformed name

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40784: Prefix {0} should exist

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40785: Malformed QName: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40786: Prefix not found: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40787: Ambiguous qname for an attribute: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40788: Element {0} is ambiguous and was found in more than one namespace: {1}, {2}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40789: Element {0} doesn''t match the DTD

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40790: Could not find parent element {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40791: Element {0} doesn''t match the DTD

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40792: Prefix not found: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40793: Malformed QName: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40794: Element {0} is ambiguous and was found in more than one namespace

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40795: Element {0} is ambiguous and was found in more than one namespace

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40796: Conflicting namespaces: {0} => {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40797: Namespace {0} was not declared in the model

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40798: Unknown type: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40799: Root element {0} doesn''t match the DTD

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40800: No root found!

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40801: Ambiguous name: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40802: Namespace not found for {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40803: Malformed qualified name {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40804: Empty table for multiple links in attribute {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40805: Unknown link type: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40806: Multiple roots found: {0} and {1}. Use the parameter 'root_elt' in the URL to choose the root element.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40807: No root found in the DTD file

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40808: Should not occur {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40809: Creating a RDB model from an XML model is currently not supported

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40810: Creating an XML model from a RDB model is currently not supported

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40811: No root on model

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40812: The table {0} which is linked to attribute {1} was not found

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40813: Unknown attribute: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40814: Unknown link type: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40815: Ambiguous name: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40816: Bad attribute: {0} in element

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40817: Namespace not found: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40818: Internal error: expected to find PCData in element {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40819: Malformed QName: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40820: *** FATAL *** A duplicate root has been found: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40821: *** FATAL *** The potential root is not in the model: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40822: Duplicate attribute: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40823: Type unsupported for PCDATA attribute of element

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40824: Two namespaces are in conflict and we cannot build aliases: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40825: *** FATAL *** Could not create a table because it already exists in the model.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40826: A Qualified name cannot begin with a colon

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40827: A Qualified name cannot end with a colon

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40828: SnpsXmlNamespaceNotFoundException occured: Should not occur while setting prefixes

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40829: This is a fixed namespace and elements cannot be added to it

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40830: The request type is different

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40831: The request command is different

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40832: A parameter is missing

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40833: A parameter has a bad value

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40834: This token was not expected anymore: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40835: Function not implemented yet: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40836: Cannot drop the default schema

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40837: An error occurred during the creation of the schema: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40838: An error occurred in the cleanup of the schema: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40839: InvalidTableException said: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40840: The table {0} already exists in the schema {1}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40841: Could not create schema with URL "{0}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40842: As no XML and no DTD were provided, the XML schema cannot be created

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40843: No DTD found and no XML file provided: the XML schema cannot be created

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40844: Could not generate the DTD because the file could not be created. Verify that you have write permission in the directory.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40845: While generating the DTD from the XML file, a "{0}" exception occurred saying: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40846: Could not close the file because an IOException occurred saying: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40847: An UnupportedDatatypeException occurred saying: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40848: Could not find the file called {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40849: IOException reading file called {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40850: Unsupported DB property "{0}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40851: Table {0} not found in schema {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40852: The default schema cannot be read/write

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40853: The schema {0} cannot be set read/write because it has no associated file

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40854: No file provided for synchronization. Use CREATE FILE <file> FROM <schema> command

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40855: Table {0} already exists but it doesn''t have the correct number of columns

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40856: Column {0} doesn''t exist in table {1}, it is required for this DTD

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40857: Expected one of auto, xml or xsd for parameter ns_prefix_generation

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40858: Found that the file references the DTD or XSD: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40859: Could not read the file to get its associated schema because an IOException occurred saying {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40860: Could not read the file to get its associated schema because a SAXException occurred saying {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40861: Could not read the file to get its associated schema because a ParserConfigurationException occurred saying {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40862: No DTD was provided and the property "generate_dtd" is set to no

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40863: The parameter generate_dtd has a bad value: {0} . One of 'AUTO', 'YES', 'NO' was expected

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40864: XSD {0} was found

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40865: No DTD named {0} was found so the XML schema could not be created

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40866: This schema is in a {0} state and cannot be opened in another state.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40867: Could not connect on schema because it is {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40868: The path {0} doesn''t exist

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40869: The path {0} is not a directory

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40870: You already have a schema opened on this file with another name: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40871: Duplicate attribute where no attribute should have been set yet.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40872: Unsupported exception saying {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40873: There are several root tables and the unload is not supported in this case

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40874: Expected to find attribute {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40875: Something unexpected occured. Expected to find datatype {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40876: Extension found in an object of type {0} is not permitted.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40877: Cannot merge types for element {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40878: Restriction violated : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40879: An IOException occured while including another schema saying {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40880: A ParserConfigurationException occured while including another schema saying {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40881: Unexpected element of type {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40882: Cannot add a restriction!: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40883: Cannot add a restriction on a non simple type or attribute

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40884: Extension found outside an element

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40885: Type {0} was not found

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40886: Cannot merge types for element "{0}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40887: Unexpected element of type {0} in hierarchy before simple type

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40888: Unexpected element of type {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40889: Could not affect complex type to object of type {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40890: Unexpected element of type {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40891: An element has no name and doesn''t refer to another element

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40892: Cannot add an element to an attributeGroup (wanting to add {0} to group {1} )

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40893: Cannot add an element to an object of type {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40894: Could not find namespace: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40895: Conflicting Namespace Error: Should not occur: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40896: Unknown prefix: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40897: Cannot handle type [{0}] as a simple type

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40898: Element {0} referenced in group {1} was not found

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40899: Attributes' group {0} not found in the file.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40900: Duplicate attribute: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40901: Unsupported exception: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40902: Element group {0} not found in the file.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40903: Duplicate reference while adding an element of a group: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40904: Unsupported exception while adding an element of a group: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40905: Namespace {0} for element {1} referenced in group {2} was not found.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40906: Element {0} referenced in group {1} has an ambiguous name

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40907: An object of one of these types was expected in the hierarchy: element, type, attribute, attribute group

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40908: No more pending objects left in hierarchy

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40909: An object of one of these types was expected in the hierarchy: element, type, attribute, attribute group

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40910: Cannot add element {0} to type {1} because it doesn''t handle references.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40911: One pending element was not found: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40912: Simple type {0} has a restriction on a type {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40913: The object of type {0} is missing type {1} but don't know how to deal with it.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40914: Element {0} is missing but is referenced

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40915: Type {0} is missing but is needed.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40916: Element {0} has no type.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40917: One pending element's namespace was not found: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40918: One pending element has an ambiguous name: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40919: Cannot add element {0} to type {1} because it doesn''t handle references.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40920: An attribute must have a simple type

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40921: Could not find the root element that we've just set.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40922: This qualified name is malformed: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40923: Inner type of element {0} is not defined or is not a complex type

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40924: Renamed column {0} to {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40925: Should not occur

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40926: Internal error

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40927: Not Supported

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40928: Not supported for XML driver commands

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40929: Property {0} has invalid value {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40930: Root element {0} specified by user not a global element in the NXSD

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40931: Unrecognised request type for {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40932: When using DTD you have to provide the root element name. Else use old parsing mode.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40933: Unable to build XSD from DTD.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40934: The schema {0} is not created using the appropriate compatibility mode.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40935: The schema {0} was created with correct compatibility mode, but has incorrect XML model type

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40936: Namespace URI for the prefix {0} was not found in the XSD/DTD or XML

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40937: Encountered one more close tag while no more open tags were found

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40938: Error splitting prefixed string {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40939: The XML construct "{0}" in element "{1}" from type "{2}" is not supported by XML JDBC driver

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40940: No global elements were found in the XSD

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40941: Requested root element {0} was not found in the XSD

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40942: Ending on "{0}" but needed to find "{1}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40945: XSD parser ecnountered error parsing XSD/DTD. Check validity.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40946: Error processing XSD/DTD

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40947: Unable to write xpath mapping information

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40948: Could not find namespace URI {0} in XML model for {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40949: Old object type found for namespace {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40951: Unable to find namespace URI : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40952: Element {0} of type {1} at xpath {2} appears to be same as element {3} of type {4} at xpath {5}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40953: Prefix "{0}" is already mapped to "{1}" in current XML scope. New uri : "{2}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40956: Root element {0} is substitutionGroup head. This is not allowed.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40957: Unable to resolve path of XSD "{0}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40958: Illegal state. Currently coalescing for "{0}".

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40959: Illegal state. Not coalescing yet.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40960: Unknown object "{0}" found

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

67 ODL-52001 to ODL-52807

ODL-52001: deleting log file: {0}, size: {1} bytes

Cause: A log file was deleted because of the rules defined in the current configuration.

Action: This is an information message, no action is needed.
Level: 16

Type: NOTIFICATION

Impact: Logging

ODL-52002: invalid value for parameter {0}: {1}. Value must be greater than zero.

Cause: An invalid value was assigned to a numeric parameter that require a positive value.

Action: Use a value that is greater than zero value for the parameter.
Level: 1

Type: ERROR

Impact: Logging

ODL-52003: invalid value for parameter maxLogSize: {0}. Value must be greater than the value of maxFileSize ({1}).

Cause: The value used for the maxLogSize parameter is smaller than the value used for the maxFileSize parameter, which is not valid.

Action: Enter a value for the maxLogSize parameter that is greater than the value of the maxFileSize parameter.
Level: 1

Type: ERROR

Impact: Logging

ODL-52004: invalid encoding: {0}

Cause: The value used for encoding parameter is not valid.

Action: Enter a valid encoding value.
Level: 1

Type: ERROR

Impact: Logging

ODL-52005: invalid path: {0}. This path is already being used by another log writer instance of a different type.

Cause: There was an attempt to create a log using a path that is already being used by another log, but the two logs are of different types.

Action: Contact Oracle support services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ODL-52006: Path cannot be null.

Cause: A null value was used for the log file path.

Action: Enter a non-null value for the path.
Level: 1

Type: ERROR

Impact: Logging

ODL-52007: The log path is not a directory: {0}.

Cause: The value used for the log path is not a directory. Some log types require that the log path be a directory, not a file, because the log file name is fixed.

Action: Enter a directory path instead of a file path.
Level: 1

Type: ERROR

Impact: Logging

ODL-52008: unable to create log directory: {0}

Cause: One or more directories that were used in the log path could not be created.

Action: Make sure that the process has permission to create the directories, or enter a different path. It may also be possible to create the directories manually.
Level: 1

Type: ERROR

Impact: Logging

ODL-52009: The log directory is not writable: {0}.

Cause: The process could not write to the log directory.

Action: Make sure that the process has permission to write to the log directory, or enter a different path.
Level: 1

Type: ERROR

Impact: Logging

ODL-52010: no permission to access log directory: {0}

Cause: The process could not access the log directory.

Action: Make sure that the process has permission to access the log directory, or enter a different path.
Level: 1

Type: ERROR

Impact: Logging

ODL-52011: attempting to operate on a closed LogWriter

Cause: There was an attempt to perform an operation on a log writer that is already closed.

Action: This is possible a programming error. Contact Oracle Support Services. If the problem occurs during process shut down, it is possible that some component is attempting to log a message after the logging system has already shut down.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ODL-52012: attempting to write to a closed LogWriter

Cause: There was an attempt to writea a message to a log writer that is already closed.

Action: This is possible a programming error. Contact Oracle Support Services. If the problem occurs during process shut down, it is possible that some component is attempting to log a message after the logging system has already shut down.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ODL-52013: attempting to flush a closed LogWriter.

Cause: There was an attempt to flush a log writer that is already closed.

Action: This is possible a programming error. Contact Oracle Support Services. If the problem occurs during process shut down, it is possible that some component is attempting to log a message after the logging system has already shut down.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ODL-52014: Maximum log size is reached.

Cause: The maximum size for the log defined in the configuration was reached and the current configuration does not enable automated removal of older log messages.

Action: Review the logging configuration. It may be necessary to increase the maxLogSize parameter, or enable a policy for the automatic removal of older messages.
Level: 1

Type: ERROR

Impact: Logging

ODL-52015: unable to delete old archived file

Cause: There was an attempt to delete an old log file, but the file could not be deleted.

Action: Check that the process has permission to delete the log file.
Level: 1

Type: ERROR

Impact: Logging

ODL-52016: failure to rotate log file: {0}

Cause: There was an attempt to rename a log file, but the operation failed.

Action: Check that the process has permission to rename files.
Level: 1

Type: ERROR

Impact: Logging

ODL-52017: out of log file names

Cause: There was an attempt to rename a log file, but there are no more names that can be used.

Action: Remove some or all of the archived files.
Level: 1

Type: ERROR

Impact: Logging

ODL-52018: unable to write to log ''{0}'': {1}

Cause: There was an error when writing messages to a log file.

Action: See the error message for the root cause.
Level: 1

Type: ERROR

Impact: Logging

ODL-52019: unable to close log ''{0}'': {1}

Cause: There was an error when closing a log file.

Action: See the error message for the root cause.
Level: 1

Type: ERROR

Impact: Logging

ODL-52020: failed to get a lock on file ''{0}'' after {1} milliseconds

Cause: A log file lock could not be acquired within the specified time period, and the log write operation has time-out.

Action: Check that other processes are not holding a lock to the log file.
Level: 1

Type: ERROR

Impact: Logging

ODL-52021: thread interrupted while waiting to lock file ''{0}''

Cause: The thread was interrupted while waiting to acquire a lock on a lock file.

Action: Check that other processes are not holding a lock to the log file.
Level: 1

Type: ERROR

Impact: Logging

ODL-52029: recursive logging detected that exceeds the recursion depth limit of {0}. The handler will not log the message.

Cause: The handler detect recursive logging calls that exceed that maximum configured recursion depth limit.

Action: Review the source code to eliminate logging calls within code that may be called while formatting a log message.
Level: 1

Type: ERROR

Impact: Logging

ODL-52030: invalid property name: {0}

Cause: An invalid property name was used in the logging configuration.

Action: Review the configuration and enter a valid property name.
Level: 1

Type: ERROR

Impact: Logging

ODL-52031: required property ''{0}'' is not found

Cause: A required property was not present in the configuration of a log handler.

Action: Review the configuration and add the required property.
Level: 1

Type: ERROR

Impact: Logging

ODL-52032: invalid format: {0}. Valid formats are: {1}.

Cause: An invalid value for the 'format' property was used in the configuration of an ODLHandler.

Action: Review the configuration and add a valid value for the format property.
Level: 1

Type: ERROR

Impact: Logging

ODL-52033: invalid value for property {0}: {1}.

Cause: An invalid value for used for an ODLHandler property.

Action: Review the configuration and add a valid value for the property.
Level: 1

Type: ERROR

Impact: Logging

ODL-52034: Configuration is invalid: {0} cannot be less than {1}.

Cause: An invalid value for used for a size property in an ODLHandler configuration.

Action: Review the configuration and make sure that the value of the 'maxFileSize' property is not greater than the value of the 'maxLogSize' property.
Level: 1

Type: ERROR

Impact: Logging

ODL-52035: failure to create ODLHandler: {0}

Cause: An ODLHandler instance could not be created.

Action: Check the error message for the root cause.
Level: 1

Type: ERROR

Impact: Logging

ODL-52036: invalid level: {0}. Check spelling and verify that the value is a valid ODL or Java level.

Cause: An invalid level was used in the configuration of a logger or handler.

Action: Review the configuration and enter a valid level.
Level: 1

Type: ERROR

Impact: Logging

ODL-52040: failure to initialize class {0}: property {1} must be defined.

Cause: A required system property was not defined.

Action: Review the process configuration and make sure that the required system property is defined.
Level: 1

Type: ERROR

Impact: Logging

ODL-52041: Use of {0} in logging configuration is deprecated; replacing it with {1}. (File: {2}).

Cause: A deprecated property was used in the logging configuration.

Action: Review the logging configuration and consider replacing the deprecated property. While the configuration may be valid, use of deprecated properties should be avoided.
Level: 1

Type: WARNING

Impact: Logging

ODL-52042: undefined property: {0}.

Cause: An undefined property was used in the logging configuration.

Action: Review the logging and process configuration and either replace the invalid property in the logging configuration, or define a value for the property.
Level: 1

Type: ERROR

Impact: Logging

ODL-52043: expecting one element of type ''{0}''

Cause: The logging configuration contained more than one XML element of a given type, when only one was expected.

Action: Review the logging configuration and remove the extra XML elements.
Level: 1

Type: ERROR

Impact: Logging

ODL-52044: cannot find handler: {0}

Cause: The logging configuration assigned a handler to one or more loggers, but the handler was not defined.

Action: Review the logging configuration and either add the missing handler, or remove any references to the handler.
Level: 1

Type: ERROR

Impact: Logging

ODL-52045: invalid class: {0}

Cause: The logging configuration defined an invalid class for a handler.

Action: Review the logging configuration and make sure that the handler class is valid. The handler class must be either a subclass of java.util.logging.Handler, or implement the oracle.core.ojdl.logging.HandlerFactory interface.
Level: 1

Type: ERROR

Impact: Logging

ODL-52046: cannot find class: {0}

Cause: The logging configuration defined a handler, filter, or error manager class, but that class could not be found.

Action: Review the logging and process configuration and make sure that the class is available in the system classpath, or that the class is visible to the classloader that loads the ODL configuration classes.
Level: 1

Type: ERROR

Impact: Logging

ODL-52047: cannot load or link class ''{0}'': {1}

Cause: The logging configuration defined a handler, filter, or error manager class, but that class could not be loaded due to a linkage error.

Action: Review the logging and process configuration and make sure that the class is available in the system classpath, or that the class is visible to the classloader that loads the ODL configuration classes, or that the correct version of the class is being used..
Level: 1

Type: ERROR

Impact: Logging

ODL-52048: Class ''{0}'' is not of expected type ''{1}''.

Cause: The logging configuration defined a handler, filter, or error manager class, but that class is not a handler, filter or error manager instance.

Action: Review the logging and process configuration and make sure that the class is of the correct type.
Level: 1

Type: ERROR

Impact: Logging

ODL-52049: cannot create instance of class ''{0}'': {1}

Cause: The logging configuration defined a handler, filter, or error manager class, but an instance of that class could not be created.

Action: Review the error message for the root cause.
Level: 1

Type: ERROR

Impact: Logging

ODL-52050: unable to process file ''{0}'', XML parse exception (line: {1}, column: {2}): {3}

Cause: The logging configuration could not be processed due to an XML error in the configuration file.

Action: Review the error message for a description of the XML error, and correct the problem in the configuration file.
Level: 1

Type: ERROR

Impact: Logging

ODL-52051: unable to process file ''{0}''; exception: {1}

Cause: The logging configuration could not be processed due to a unexpected XML parser error.

Action: Review the error message for a description of the root cause.
Level: 1

Type: ERROR

Impact: Logging

ODL-52052: unable to find resource: {0}

Cause: The logging configuration could not be processed due to a missing XML schema or DTD.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ODL-52053: unable to create handler instance using class ''{0}''; exception: {1}

Cause: The creation of a handler instance failed because the handler factory threw an exception.

Action: Review the error message for the root cause.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ODL-52054: The logger ''{0}'' is already defined.

Cause: There was an attempt to add a new logger to the configuration file, but the logger is already defined.

Action: Verify that the logger name is correct.
Level: 1

Type: ERROR

Impact: Logging

ODL-52055: The handler ''{0}'' is already defined.

Cause: There was an attempt to add a new handler to the configuration file, but a handler is already defined.

Action: Verify that the handler name is correct.
Level: 1

Type: ERROR

Impact: Logging

ODL-52056: The logger ''{0}'' is not defined.

Cause: There was an attempt to access a logger in the logging configuration but the logger is not defined.

Action: Verify if the logger name is correct.
Level: 1

Type: ERROR

Impact: Logging

ODL-52057: The handler ''{0}'' is not defined.

Cause: There was an attempt to access a handler in the logging configuration but the handler is not defined.

Action: Verify if the handler name is correct.
Level: 1

Type: ERROR

Impact: Logging

ODL-52058: The handler ''{0}'' cannot be removed because it is being used by logger ''{1}''.

Cause: There was an attempt to remove a handler from the logging configuration, but the handler could not be removed because it is being used by a logger.

Action: Verify that the handler name is correct, or remove the handler from all the loggers first before attempting to remove the handler.
Level: 1

Type: ERROR

Impact: Logging

ODL-52059: The logger ''{0}'' already has handler ''{1}''.

Cause: There was an attempt to add a handler to a logger but the logger already has the given handler.

Action: Verify if the logger and handler names are correct.
Level: 1

Type: ERROR

Impact: Logging

ODL-52060: The logger ''{0}'' does not have handler ''{1}''.

Cause: There was an attempt to remove a handler from a logger, but the logger does not contain the given handler.

Action: Verify if the logger and handler names are correct.
Level: 1

Type: ERROR

Impact: Logging

ODL-52061: The handler ''{0}'' does not have property ''{1}''.

Cause: There was an attempt to remove a property from a handler, but the handler does not have a property with the given name.

Action: Verify if the handler and property are correct.
Level: 1

Type: ERROR

Impact: Logging

ODL-52062: Illegal value for ''{0}'': {1}

Cause: There was an attempt to set a property for a handler or logger, but the value of the property is not valid.

Action: Verify if the handler or loggers properties are valid.
Level: 1

Type: ERROR

Impact: Logging

ODL-52063: Unable to load logging configuration from ''{0}''; exception: {1}

Cause: There was an error while loading the logging configuration file.

Action: Review the error message for the root cause.
Level: 1

Type: ERROR

Impact: Logging

ODL-52064: The handler ''{0}'' is already defined in the target logging configuration document.

Cause: There was an attempt to add a handler to a logging configuration file, but a handler with the given name already exists in the target file.

Action: Review the definition of the new handler.
Level: 1

Type: ERROR

Impact: Logging

ODL-52065: The logger ''{0}'' or a descendant is already defined in the target logging configuration document.

Cause: There was an attempt to add a logger to a logging configuration file, but the logger or one of its descendants is already defined in target logging configuration.

Action: Review the definition of the new logger.
Level: 1

Type: ERROR

Impact: Logging

ODL-52081: unable to read logging configuration from file ''{0}''; exception: {1}

Cause: There was an error reading the logging configuration from the given file.

Action: Review the error message for the root cause.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ODL-52083: unable to register log dump; exception: {0}

Cause: There was an error registering the log dump with the FMW Diagnostics Framework.

Action: Review the error message for the root cause. The system may still work, but the log dump will not be available.
Level: 1

Type: WARNING

Impact: Logging

ODL-52084: unable to initialize ODL; exception: {0}

Cause: There was an error initializing Oracle Diagnostic Logging (ODL).

Action: Review the error message for the root cause. Oracle Diagnostic Logging is not properly configured in this system.
Level: 1

Type: ERROR

Impact: Logging

ODL-52086: unable to reload logging configuration from file ''{0}''; exception: {1}

Cause: There was an error reloading the logging configuration from the given file.

Action: Review the error message for the root cause.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ODL-52087: suspicious logging configuration reload. The original configuration was read from file ''{0}'', but the new configuration is being read from ''{1}''.

Cause: The logging configuration is being reloaded, but the configuration file is different from the configuration file used for the initial configuration.

Action: This is probably an error, there should only be one configuration file.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ODL-52088: The java.util.logging configuration was reloaded.

Cause: The java.util.logging configuration was reloaded, probably via the invocation of LogManager.readConfiguration.

Action: The java.util.logging configuration should not be reloaded programmatically, as this can override the ODL configuration.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ODL-52501: Unable to get OPMN connection for instance ''{0}''; check that the instance name is valid and that OPMN is running.

Cause: There was an attempt to invoke an operation on a OPMN managed target, but a connection to that target could not be created.

Action: Check the target argument and make sure that the instance and component names are valid, and that OPMN is running.
Level: 1

Type: ERROR

Impact: Logging

ODL-52502: Invalid target. The server name ''{0}'' is not a valid server name, the server is not running, or JRF is not enabled on the server.

Cause: There was an attempt to invoke an operation on a Java EE server target, but the target does not exist or is not valid for the operation.

Action: Check the target argument and make sure that the server name is correct, the server is running, and that JRF is enabled on the server.
Level: 1

Type: ERROR

Impact: Logging

ODL-52801: There is already an active trace with ID ''{0}''. Use a different trace ID or stop the active trace first before starting a new trace with the same ID.

Cause: There was an attempt to start a trace using an ID value that is already being used by another active trace.

Action: Use a different trace ID or disable the existing active trace first before starting a new one with the same ID.
Level: 1

Type: ERROR

Impact: Logging

ODL-52802: There is already an active trace for attribute ''{0}'' with value ''{1}''. The existing active trace must be disabled first before a new one can be started for the same attribute value.

Cause: There was an attempt to start a trace using an attribute value that is already used by an active trace.

Action: Use a different attribute value or disable the existing active trace first before starting a new one with the same attribute value.
Level: 1

Type: ERROR

Impact: Logging

ODL-52803: Unable to complete the start tracing operation. The operation failed on target ''{0}''; cause: {1}

Cause: The start tracing operation cannot be completed because one or more servres are unable to complete the operation.

Action: See the error message for more information on the cause of the server failure.
Level: 1

Type: ERROR

Impact: Logging

ODL-52804: The start tracing operation failed for provider ''{0}''; cause: {1}

Cause: The start tracing operation cannot be completed because a trace provider is unable to complete the operation. See the error message for more information on the cause for the provider failure.

Action: See the error message for more information on the cause of the provider failure. You may try to disable the failing provider to obtain trace data from the other trace providers.
Level: 1

Type: ERROR

Impact: Logging

ODL-52805: Unable to complete the start tracing operation. The operation failed for one or more providers and could not be rolled back. The tracing configuration may be in an inconsistent state. Disable all active traces or restart the servers to reset the selective tracing configuration.

Cause: The start tracing operation failed for one or more providers or servers but could not be rolled back on all servers or providers.

Action: The tracing system may be on an inconsistent state. Disable all active traces or restart the servers to reset the selective tracing configuration.
Level: 1

Type: ERROR

Impact: Logging

ODL-52806: The stop tracing operation failed for provider ''{0}''; cause: {1}

Cause: The stop tracing operation cannot be completed because a trace provider is unable to complete the operation. See the error message for more information on the reason for the provider failure.

Action: See the error message for more information on the cause of the provider failure.
Level: 1

Type: ERROR

Impact: Logging

ODL-52807: Unable to create incident for trace with ID ''{0}''; cause: {1}

Cause: A trace was stopped but an incident could not be created for the trace data.

Action: See the error message for more information on the root causeof the incident creation failure.
Level: 1

Type: ERROR

Impact: Logging

68 ODSM-00001 to ODSM-01007

ODSM-00001: ODSM disconnected from OID server as the server is stopped.

Cause: OID server is stopped or ODSM is unable to contact OID server.

Action: Ensure that OID server is up and running. Refer OID server's log file to find out why it was stopped.
Level: 1

Type: ERROR

Impact: ODSM

ODSM-00002: Invalid Credentials.

Cause: Wrong username or password was provided.

Action: Provide valid username or password.
Level: 1

Type: ERROR

Impact: ODSM

ODSM-00003: Bind failed.

Cause: It may be due to wrong host name or port number or OID server may not be up. Refer exception for more details.

Action: Provide valid host name and port number and ensure that OID server is up and running.
Level: 1

Type: ERROR

Impact: ODSM

ODSM-00004: ODSM disconnected from OID server due to time out error.

Cause: ODSM to OID connection was idle for long time.

Action: ODSM will reestablish the connection. No action needed from the user.
Level: 1

Type: ERROR

Impact: ODSM

ODSM-00005: Size limit exceeded.

Cause: The number of search entries exceeds the size limit setting.

Action: Use the "Advanced Search" or "Configure Search Filter" options to retrieve the specific entries.
Level: 1

Type: ERROR

Impact: ODSM

ODSM-00006: Unable to load password policy entries.

Cause: Error occurred while retrieving password policy entries from OID server.

Action: Refer exception and OID server's log file to take further action.
Level: 1

Type: ERROR

Impact: ODSM

ODSM-00007: SSL connection failed.

Cause: You may not have provided valid SSL port number and host. Or ODSM may not be able to read its trust store or may not have access to Credential Store Framework. Refer exception to find actual cause.

Action: Ensure that you have provided valid SSL port number and host details. Ensure that ODSM has access to Credential Store Framework and is able to read its trust store.
Level: 1

Type: ERROR

Impact: ODSM

ODSM-00008: Certificate validation failed.

Cause: Certificate presented by the server is invalid. Refer exception for more details.

Action: Connect to a server that is authentic and has valid certificate.
Level: 1

Type: ERROR

Impact: ODSM

ODSM-00009: LDAP operation has failed.

Cause: OID server is unwilling to perform this operation. In case ODSM is connected to OID server in High Availability mode and if OID to which ODSM is connected has gone down, this error can occur.

Action: Refer OID server's log file to take appropriate action. In later case, ODSM will reestablish connection to other available OID server and no action is required from the user.
Level: 1

Type: ERROR

Impact: ODSM

ODSM-00010: Unable to load password verifier entries.

Cause: Error occurred while retrieving password verifier entries from OID server.

Action: Refer exception and OID server's log file to take further action.
Level: 1

Type: ERROR

Impact: ODSM

ODSM-00011: Unable to load access control policies.

Cause: Error occurred while searching OID for access control policies.

Action: Refer exception and OID server's log file to take further action.
Level: 1

Type: ERROR

Impact: ODSM

ODSM-00012: Posn: -1, Size: 0.

Cause: When JNDI is unable to handle error code returned by OID server, above error message is returned.

Action: Repeat your current action using command line tools supplied with OID server to find out actual error message returned by OID server and take appropriate action.
Level: 1

Type: ERROR

Impact: ODSM

ODSM-01000: Error connecting to OVD.

Cause: OVD server is not running or ODSM is unable to contact OVD server.

Action: Ensure that OVD server is up and running. Also check if the server is SSL enabled.
Level: 1

Type: ERROR

Impact: ODSM

ODSM-01001: Failed to save configuration to OVD server.

Cause: Configuration validation has failed. Refer exception for more details.

Action: Provide valid configuration.
Level: 1

Type: ERROR

Impact: ODSM

ODSM-01002: SSL connection failed.

Cause: SSL mode is not enabled in OVD server.

Action: Ensure that SSL mode is enabled in OVD server.
Level: 1

Type: ERROR

Impact: ODSM

ODSM-01003: Invalid host name.

Cause: Invalid host name is provided.

Action: Provide valid host name.
Level: 1

Type: ERROR

Impact: ODSM

ODSM-01004: Incorrect version error.

Cause: Configuration version number sent by ODSM does not match with that of OVD server.

Action: Refresh configuration from OVD server and redo the changes.
Level: 1

Type: ERROR

Impact: ODSM

ODSM-01005: Failed to save access control policies to OVD server.

Cause: Validation of access control policy has failed at OVD server.

Action: Provide valid access control policies.
Level: 1

Type: ERROR

Impact: ODSM

ODSM-01006: Failed to save adapter configuration to OVD server.

Cause: Validation of adapter configuration has failed at OVD server.

Action: Provide valid adapter configuration.
Level: 1

Type: ERROR

Impact: ODSM

ODSM-01007: Failed to retrieve mapping file from OVD server.

Cause: Request mapping file is not available. Refer exception and OVD server log file for more details.

Action: Provide valid mapping file.
Level: 1

Type: ERROR

Impact: ODSM

69 ODV-00000 to ODV-00172

ODV-00000: OraDAV: No extension. Apache processes GET.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

ODV-00001: OraDAV: Extension not in OraGetSource. Apache processes GET.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

ODV-00002: OraDAV: Extension in OraGetSource. mod_oradav processing GET.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

ODV-00003: OraDAV: Failed to query lock-null status for {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ODV-00004: OraDAV: PROPDUMP [dav_ora_cache_props][{0}]ctx->propfind_sortnum : {1}ctx->path : {2}ctx->parentpath : {3}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ODV-00005: OraDAV: caching property docid={0} namespace={1} tag={2} propv_type={3}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ODV-00006: OraDAV: fetching property docid={0} namespace={1} tag={2} propv_type={3}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ODV-00007: OraDAV: reading clob property docid={0} namespace={1} tag={2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ODV-00008: OraDAV: open lob for writing property lobhandle = {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ODV-00009: OraDAV: write lob for property lobhandle = {0} vsize = {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ODV-00010: OraDAV: close lob for property lobhandle = {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ODV-00011: OraDAV: OCI Error {0}/{1}: {2}

Cause: There was an unexpected error from an OCI call.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Network

ODV-00014: OraDAV dump: resource->info != ctx

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

ODV-00015: OraDAV dav_resource dump:\tURI: {0}\tExists: {1}\tCollection: {2}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

ODV-00016: OraDAV dump: ctx->rctx != rctx

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

ODV-00017: OraDAV dav_resource_private dump:\tPath: {0}\tParentPath: {1}\tMemberName: {2}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

ODV-00018: OraDAV dav_ora_req_ctx dump:\tURI: {0}\tFilename: {1}\tDepth: {2}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

ODV-00019: OraDAV: Stream {0} bytes/ms [{1} ms][{2}]

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ODV-00021: OraDAV: Improperly formatted EXTENDED_STATUS parameter: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ODV-00022: OraDAV: "extended_status" document element missing

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ODV-00023: OraDAV: "apache_log" element of EXTENDED_STATUS missing "level" attribute

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ODV-00024: OraDAV: "apache_log" element of EXTENDED_STATUS has invalid "level" attribute: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ODV-00025: OraDAV: "apache_log" element of EXTENDED_STATUS missing "#PCDATA" text

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ODV-00026: OraDAV: {0}

Cause:

Action:
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

ODV-00027: OraDAV: "http_header" element of EXTENDED_STATUS missing "name" attribute

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ODV-00028: OraDAV: "http_header" element of EXTENDED_STATUS missing "value" attribute

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ODV-00029: OraDAV: encountered multiple "http_status" elements in EXTENDED_STATUS

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ODV-00030: OraDAV: "http_status" element of EXTENDED_STATUS missing "code" attribute

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ODV-00031: OraDAV: encountered multiple "client_data" elements in EXTENDED_STATUS

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ODV-00032: OraDAV: "client_data" element of EXTENDED_STATUS missing "#PCDATA" text

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ODV-00033: OraDAV: Unrecognized EXTENDED_STATUS element: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ODV-00034: OraDAV: API [{0}]{1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ODV-00036: OraDAV: API [{0}][dbcon {1}][{2} ms][{3}]

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ODV-00037: OraDAV: Agent [{0}] User [{1}] ECID [{2}] URI [{3}] Method [{4}].

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ODV-00038: OraDAV: OCI [open lob][lobhandle = {0} status = {1}]

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ODV-00039: OraDAV: OCI [read lob][(streamed) lobhandle = {0} readbuffersize = {1} status = {2}]

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ODV-00040: OraDAV: OCI [close lob][closing lobhandle because of read error = {0} ]

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ODV-00041: OraDAV: OCI [close lob][lobhandle = {0} status = {1}]

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ODV-00042: OraDAV: blob2text translation={0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ODV-00043: OraDAV: Error purging cache: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ODV-00044: OraDAV: mutex not initialized

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ODV-00045: OraDAV: deleting dbmgr [{0}][pid {1}].

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ODV-00046: OraDAV: dbmgr deleted [{0}][pid {1}].

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ODV-00047: OraDAV: oradav_driver_info Name={0} Version={1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ODV-00048: OraDAV: Oracle DAVParam {0}, {1} or {2} needed

Cause: The OraDAV configuration is incorrect.

Action: Add connection information to the configuration.
Level: 1

Type: ERROR

Impact: Configuration

ODV-00049: OraDAV: Conversion of {0} to {1} as a service name failed

Cause: The OraDAV configuration is incorrect.

Action: Correct the database connection information.
Level: 1

Type: ERROR

Impact: Configuration

ODV-00051: OraDAV: Oracle DAVParam {0} missing

Cause: The OraDAV configuration is incorrect.

Action: Add the required DAVParam.
Level: 1

Type: ERROR

Impact: Configuration

ODV-00052: OraDAV: Oracle DAVParam {0}, {1}, or {2} missing

Cause: The OraDAV configuration is incorrect.

Action: Add a required DAVParam.
Level: 1

Type: WARNING

Impact: Other

ODV-00053: OraDAV: Oracle DAVParam {0} is invalid.

Cause: The OraDAV configuration is incorrect.

Action: Correct the value of the DAVParam.
Level: 1

Type: ERROR

Impact: Configuration

ODV-00055: OraDAV: Oracle DAVParam {0} not decoded

Cause: The OraDAV configuration is incorrect.

Action: Correct the value of the DAVParam.
Level: 1

Type: ERROR

Impact: Configuration

ODV-00057: OraDAV: Caching DAVParams are incorrect. Both {0} and {1} must be specified, or neither can be specified.

Cause: The OraDAV configuration is incorrect.

Action: Either specify both DAVParams or neither.
Level: 1

Type: ERROR

Impact: Configuration

ODV-00058: OraDAV: Caching DAVParams are incorrect. DAVParam {0} can only be specified if both {1} and {2} are specified.

Cause: The OraDAV configuration is incorrect.

Action: Specify both DAVParams.
Level: 1

Type: ERROR

Impact: Configuration

ODV-00059: OraDAV: Oracle Caching DAVParams are incorrect. DAVParam {0} must refer to an existing directory.

Cause: The OraDAV configuration is incorrect.

Action: Specify a valid directory.
Level: 1

Type: ERROR

Impact: Configuration

ODV-00060: OraDAV: Caching DAVParam is incorrect. The value {0} is invalid for DAVParam {1}. This must be a positive numeric value optionally followed by KB, MB, or GB.

Cause: The OraDAV configuration is incorrect.

Action: Specify a valid numeric value.
Level: 1

Type: ERROR

Impact: Configuration

ODV-00063: OraDAV: Caching DAVParam is incorrect. The value {0} is invalid for DAVParam {1}. The value must be an integer between 1 and 100 inclusive.

Cause: The OraDAV configuration is incorrect.

Action: Specify a valid numeric value.
Level: 1

Type: ERROR

Impact: Configuration

ODV-00064: OraDAV: Caching DAVParams are incorrect. The value given for {0} ({1}) is greater than the value given for {2} ({3}).

Cause: The OraDAV configuration is incorrect.

Action: Specify valid values for these DAVParams.
Level: 1

Type: WARNING

Impact: Other

ODV-00065: OraDAV: Failure connecting to Oracle service {0}

Cause: There was a communications error between the module and the repository database.

Action: Contact the system or database administrator to resolve the issue.
Level: 1

Type: ERROR

Impact: Network

ODV-00066: OraDAV: Invalid value ({0}) for DAVParam ORATRACELEVEL. Using {1} as the default.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ODV-00067: OraDAV: Failure to allocate dav_ora_driver_ctx

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ODV-00068: OraDAV: Failure in call to dav_ora_init_driver

Cause: The module was not able to contact the database driver.

Action: Check the database status and connections.
Level: 1

Type: ERROR

Impact: Network

ODV-00069: OraDAV driver API mismatch: Apache OraDAV range = ({0},{1}), {2} range = ({3},{4})

Cause: The module and driver versions are inconsistent.

Action: Upgrade either the module or the driver.
Level: 1

Type: ERROR

Impact: Installation

ODV-00070: OraDAV: Initializing {0} using API version {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ODV-00071: OraDAV: Failure in call to get_oradav_driver_info

Cause: The module was not able to connect to the database driver.

Action: Check the database status and connections.
Level: 1

Type: ERROR

Impact: Network

ODV-00072: OraDAV: Unable to read CLOB value returned in get_oradav_driver_info.

Cause: The module was not able to get the CLOB from the database driver.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Data

ODV-00073: OraDAV: Error parsing oradav_driver_info XML document.

Cause: The module was not able to read the driver information.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Data

ODV-00074: OraDAV: Error setting oradav_driver_info, {0}.

Cause: The module was not able to set the driver information.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Data

ODV-00079: OraDAV: Error: request context is missing database connection pointer.

Cause: The module could not connect the database for this request.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ODV-00080: OraDAV: Using dbcon ({0}), usage count = {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ODV-00081: OraDAV: PROPDUMP [dav_ora_get_resource]ctx->propfind_sortnum : {0}ctx->path : {1}ctx->parentpath : {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ODV-00082: OraDAV: Directory index forbidden by rule: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ODV-00083: OraDAV: Invalid Content-Length {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ODV-00085: OraDAV: Path name too long: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ODV-00086: OraDAV: Cache file size does not match resource content length.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ODV-00087: OraDAV: Unable to open cache usage file, {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ODV-00088: OraDAV: Unable to lock cache usage file, {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ODV-00089: OraDAV: Unable to read from cache usage file, {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ODV-00090: OraDAV: Disk cache is full. Initiating purge.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ODV-00091: OraDAV: Unable to open cache file, {0} for writing.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ODV-00092: OraDAV: Unable to write to cache usage file, {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ODV-00093: OraDAV: Unable to open cache usage file, {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ODV-00094: OraDAV: Unable to lock cache usage file, {0}, during cache purge.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ODV-00095: OraDAV: OCI [open_stream][(read streamed) lobhandle = {0}]

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ODV-00096: OraDAV: OCI [open stream][(write) lobhandle = {0} contentlength = {1}]

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ODV-00097: OraDAV: OCI [close stream] unable to close cache file

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ODV-00098: OraDAV: OCI [close stream][lobhandle = {0}]

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ODV-00099: OraDAV: OCI [read stream][(read streamed) lobhandle = {0} bufsize = {1}]

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ODV-00100: OraDAV: OCI [read stream][(read seekable) lobhandle = {0} bufsize = {1}]

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ODV-00101: OraDAV: read stream cache write failure

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ODV-00102: OraDAV: OCI [write stream][lobhandle = {0} bufsize = {1}]

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ODV-00103: OraDAV: OCI [commit][failed]

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ODV-00104: OraDAV: Ignoring propfind cursor since validate cursor is also active.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ODV-00105: OraDAV: PROPDUMP [dav_ora_cursor_walker]ctx->propfind_sortnum : {0}ctx->path : {1}ctx->parentpath : {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ODV-00106: OraDAV Walker: Starting the validate cursor for method {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ODV-00107: OraDAV: releasing connection [{0}], usage count = {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ODV-00108: OraDAV: version detection failure

Cause: The module and driver versions are inconsistent.

Action: Upgrade the database driver.
Level: 1

Type: ERROR

Impact: Installation

ODV-00110: OraDAV: OCI [commit][failed] - {0} - {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ODV-00111: OraDAV: OCI [commit][Succeeded]

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ODV-00112: OraDAV: OCI [rollback][Failed. Connection deleted.]

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ODV-00113: OraDAV: OCI [rollback][Succeeded]

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ODV-00114: OraDAV: Releasing connection [{0}], usage count = {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ODV-00115: OraDAV: dav_toutf16 conversion error {0}

Cause: There was an internationalization conversion error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ODV-00116: OraDAV: OCICharSetToUnicode conversion error {0}

Cause: There was an internationalization conversion error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ODV-00117: OraDAV: OCICharSetToUnicode conversion error {0}

Cause: There was an internationalization conversion error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ODV-00118: OraDAV: dav_toutf8 conversion error {0}

Cause: There was an internationalization conversion error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ODV-00119: OraDAV: An undefined namespace prefix was used.

Cause: The client has issued an invalid request.

Action: Correct the namespace prefix and reissue the request.
Level: 1

Type: ERROR

Impact: Data

ODV-00120: OraDAV: A namespace prefix was defined with an empty URI.

Cause: The client has issued an invalid request.

Action: Correct the setting for the URI and reissue the request.
Level: 1

Type: ERROR

Impact: Data

ODV-00121: OraDAV: There was an error within the XML request body.

Cause: The client has issued an invalid request.

Action: Correct the XML request body and reissue the request.
Level: 1

Type: ERROR

Impact: Data

ODV-00122: OraDAV: XML parser error code: {0} ({1}).

Cause: The client has issued an invalid request.

Action: Correct the XML request body and reissue the request.
Level: 1

Type: ERROR

Impact: Data

ODV-00123: OraDAV: DLL initialization failed, error creating mutex.

Cause: The module was not able to initialize.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Operating System

ODV-00124: OraDAV: "DAV Off" cannot be used to turn off a subtree of a DAV-enabled location.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

ODV-00125: OraDAV: A subtree cannot specify a different DAV provider than its parent.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

ODV-00126: OraDAV: Forcing HTTP_INTERNAL_SERVER_ERROR. NLS href conversion error while converting href {0} to a utf8 value.

Cause: There was an internationalization conversion error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ODV-00127: OraDAV: [DAVOraUseNLS On] UTF8 conversion of URLNative href value:\t{0}UTF8 href value:\t{1} (NLS_LANG={2})

Cause: There was an internationalization conversion error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ODV-00132: OraDAV: An invalid Depth header was specified.

Cause: The client has issued an invalid request.

Action: Correct the Depth header and reissue the request.
Level: 1

Type: ERROR

Impact: Data

ODV-00133: OraDAV: An invalid Overwrite header was specified.

Cause: The client has issued an invalid request.

Action: Correct the Overwrite header and reissue the request.
Level: 1

Type: WARNING

Impact: Data

ODV-00134: OraDAV: No {0} has been configured.

Cause: The OraDAV configuration is incorrect.

Action: Specify valid values in the configuration.
Level: 1

Type: ERROR

Impact: Configuration

ODV-00135: OraDAV: [HTTP GET request handled by mod_oradav (subrequest)]

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ODV-00136: OraDAV: [HTTP GET request handled by mod_oradav (direct read)]

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ODV-00137: OraDAV: Depth must be infinity for DELETE of a collection.

Cause: The client has issued an invalid request.

Action: Set the Depth to infinity and reissue the request.
Level: 1

Type: ERROR

Impact: Data

ODV-00138: OraDAV: Depth cannot be set to 1 for DELETE.

Cause: The client has issued an invalid request.

Action: Set the Depth to infinity and reissue the request.
Level: 1

Type: ERROR

Impact: Data

ODV-00140: OraDAV: The propfind element was not found.

Cause: The client has issued an invalid request.

Action: Provide a valid propfind element and reissue the request.
Level: 1

Type: ERROR

Impact: Data

ODV-00141: OraDAV: The propfind element does not contain one of the required child elements (the specific command).

Cause: The client has issued an invalid request.

Action: Provide a valid propfind element and reissue the request.
Level: 1

Type: ERROR

Impact: Data

ODV-00142: OraDAV: The request body does not contain a propertyupdate element.

Cause: The client has issued an invalid request.

Action: Provide a valid propertyupdate element and reissue the request.
Level: 1

Type: ERROR

Impact: Data

ODV-00143: OraDAV: A prop element is missing inside the propertyupdate command.

Cause: The client has issued an invalid request.

Action: Provide a valid propertyupdate element and reissue the request.
Level: 1

Type: ERROR

Impact: Data

ODV-00144: OraDAV: Unknown Transfer-Encoding {0}

Cause: The client has issued an unsupported request.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ODV-00145: OraDAV: Invalid Content-Length: {0}

Cause: The client has issued an unsupported request.

Action: Reissue the request with proper Content-Length.
Level: 1

Type: ERROR

Impact: Data

ODV-00146: OraDAV: The request is missing a Destination header.

Cause: The client has issued an unsupported request.

Action: Reissue the request with proper Content-Length.
Level: 1

Type: ERROR

Impact: Data

ODV-00149: OraDAV: Depth must be 0 or infinity for COPY or MOVE.

Cause: The client has issued an invalid request.

Action: Set Depth to 0 or infinity and reissue the request.
Level: 1

Type: ERROR

Impact: Data

ODV-00150: OraDAV: Depth must be infinity to MOVE a collection.

Cause: The client has issued an invalid request.

Action: Set Depth to infinity and reissue the request.
Level: 1

Type: ERROR

Impact: Data

ODV-00151: OraDAV: Depth must be 0 or infinity for LOCK.

Cause: The client has issued an invalid request.

Action: Set Depth to infinity and reissue the request.
Level: 1

Type: ERROR

Impact: Data

ODV-00152: OraDAV: Unlock failed for {0}. No Lock-Token was specified in the header.

Cause: The client has issued an invalid request.

Action: Provide a valid Lock-Token and reissue the request.
Level: 1

Type: ERROR

Impact: Data

ODV-00154: OraDAV: DAV [Begin Request {0}][{1}]

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ODV-00155: OraDAV: Request is from Web Cache (found Surrogate-Capability in request header)

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ODV-00156: OraDAV: DAV [Request total {0}][{1}][{2} ms]

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ODV-00157: OraDAV: Failed to initialize OCI environment.

Cause: The module was unable to initialize the OCI connection.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ODV-00158: OraDAV: Lost connectivity to database.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ODV-00159: OraDAV: Unable to end database session.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ODV-00160: OraDAV: Unable to detach from database.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ODV-00163: OraDAV: Unable to cancel a streamed LOB read operation.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ODV-00164: OraDAV: Unable to cancel a streamed LOB write operation.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ODV-00165: OraDAV: Error creating connection list mutex

Cause: OraDAV was not able to initialize the internal structures.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Operating System

ODV-00168: OraDAV: Error acquiring connection list mutex.

Cause: OraDAV was not able to initialize the internal structures.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Operating System

ODV-00169: OraDAV: Unable to release connection list mutex.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ODV-00170: OraDAV: Unable to destroy connection list mutex.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

ODV-00171: OraDAV: [DEBUGGING] Allocated {0} bytes ({1})

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

ODV-00172: OraDAV: [DEBUGGING] Free address {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

70 OID-03053 to OID-23737

OID-03053: Cannot add nonbase schema outside cn=subschemasubentry.

Cause: A schema addition was attempted outside cn=subschemasubentry.

Action: Ensure schema additions are made to cn=subschemasubentry.
Level: 16

Type: ERROR

Impact: Compliance

OID-05018: Cataloging for attr %s is already in progress.

Cause: A search request with an uncatalogued attribute was received. An analogous previous request has already triggered the OID server to catalog this attribute but the catalog creation is yet to complete.

Action: Allow the server at least ten minutes to complete the catalog creation and re-try the query.
Level: 16

Type: ERROR

Impact: Session

OID-05019: Cataloging for attr %s was not performed, as resource is busy.

Cause: A search request with an uncatalogued attribute was received. The OID server was unable to automatically catalog this attribute and respond to the query due to resource contention.

Action: Re-try the query after ten minutes.
Level: 16

Type: ERROR

Impact: Session

OID-12501: Password Policy Error :%d: %s : Your account is locked. Contact your OID administrator.

Cause: The configured maximum for consecutive bind failures allowed as the given user was exceeded.

Action: Set orclpwdaccountunlock on the user entry to 1. This action can be performed only by users with the appropriate privileges.
Level: 16

Type: ERROR

Impact: Security

OID-23001: OID is unable to come up using the configured port.

Cause: The port configured for use by OID was not available.

Action: Ensure that the port numbers used for OID are available.
Level: 16

Type: ERROR

Impact: Ports

OID-23002: Creating a new DB connection failed with ORA-%d.

Cause: OID server was unable to log in to the database.

Action: Verify the 'PROCESS' database parameter in the init.ora file.
Level: 16

Type: ERROR

Impact: Network

OID-23004: Unable to read replication configuration information

Cause: This error occurred because the replication server was unable to connect to OID, was unable to get the replication DN and password, or the replication system configuration was not present.

Action: The error message will be followed by other log messages indicating action to be taken.
Level: 16

Type: ERROR

Impact: Configuration

OID-23005: %s: No replication agreement to process

Cause: Replication agreements were not set up with other node(s).

Action: Set up the replication agreement with other node(s) before starting the replication server.
Level: 16

Type: ERROR

Impact: Configuration

OID-23006: In %s, failure to enqueue %s into queue=%s

Cause: The replication enqueue routine failed.

Action: This is an internal error. Use the oidcmprec tool to compare and reconcile this entry from the supplier to the consumer. For further help contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Session

OID-23007: In %s, failing to bind with the supplier on server=%s

Cause: Either the OID server was down or the replication password was incorrect.

Action: Ensure that the OID server on the supplier is running. If the password has changed restart the replication server.
Level: 16

Type: ERROR

Impact: Session

OID-23008: In %s, failing to read attribute values from change log entry, agreement=%s, operation=%s.

Cause: Change log entries may be corrupted or certain attributes in the change log entry were not found.

Action: Check the associated error messages and look for the entry that failed. Using oidcmprec tool, compare and reconcile this entry from supplier to consumer.
Level: 16

Type: ERROR

Impact: Data

OID-23009: In %s, error moving successfully applied change log items to purge queue, error=%s, changeNo=%d.

Cause: Failed to update the change log entry status.

Action: Resolve the associated errors logged in the Replication server log and the OID server log. For further help contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Data

OID-23010: Memory allocation failure in %s for %d bytes.

Cause: The replication server was unable to allocate the required memory space.

Action: Contact Oracle Support Services.
Level: 16

Type: ERROR

Impact: Memory

OID-23011: In %s, failure connecting to server, %s.

Cause: Either the OID server is down or the replication password is incorrect.

Action: Ensure that the OID server is running. If the replication password has changed restart the replication server.
Level: 16

Type: ERROR

Impact: Session

OID-23012: In %s, cannot bind to the consumer, server=%s

Cause: Either the OID server is down or the replication password is incorrect.

Action: Ensure that the OID server on the consumer is running. If the replication password has changed restart the replication server.
Level: 16

Type: ERROR

Impact: Session

OID-23013: In %s, failure reading replica state of supplier from server=%s, DN=%s.

Cause: The replica entry was either corrupt or not found.

Action: Using remtool, clean up the replication and set up the replication again. *{1} is the status of bootstraping stage, {2} is hostname and {3} is agreement id.
Level: 16

Type: ERROR

Impact: Data

OID-23014: Failure updating replica status to %s at server=%s for agreement id =%s.

Cause: Could not update the replication configuration entry for the replica.

Action: Look at the OID server log and resolve the corresponding errors reported in the log.
Level: 16

Type: ERROR

Impact: Session

OID-23015: In %s, failure initializing last changenumber for bootstrapping, agreement=%s, supplierChangeNo=%d, consChangeNo=%d, errorCode=%d.

Cause: Could not get the last change number from the replica or could not update the replication configuration entry with the change number.

Action: Look at the OID server log and resolve the corresponding errors reported in the log.
Level: 16

Type: ERROR

Impact: Data

OID-23016: In %s, failure beginning hash iteration for included namecontext. Server=%s, agreement=%s.

Cause: No naming context was included for the replication agreement.

Action: Add the naming context for the replication agreement. If this does not resolve the problem contact Oracle Support Services.
Level: 16

Type: ERROR

Impact: Configuration

OID-23017: In %s, failure when bootstrapping %d out of %d naming context(s) from the supplier, %s.

Cause: Indicated in the following associated error messages in the log file.

Action: More specific messages will accompany this message. Refer to those messages for the appropriate action.
Level: 16

Type: ERROR

Impact: Session

OID-23018: In %s, failing in subtree delete on DN=%s, server=%s, error=%s.

Cause: The ldap_delete operation failed.

Action: Check the OID server log and resolve the corresponding errors reported in the log. Contact Oracle Support Services for additional assistance.
Level: 8

Type: INTERNAL_ERROR

Impact: Session

OID-23019: In %s, failure enqueueing %s into queue=%s.

Cause: An internal error caused the enqueue routine to fail.

Action: Contact Oracle Support Services.
Level: 8

Type: INTERNAL_ERROR

Impact: Session

OID-23020: In %s, ldap_search failure against server=%s where basedn=%s, scope=%d, filter=%s, attrs=%s, error=%s.

Cause: Either the entry did not exist or this was an internal error where ldap_search failed.

Action: Examine the OID server logs and resolve the corresponding errors reported.
Level: 16

Type: ERROR

Impact: Session

OID-23021: In %s, ldap_result failure against server=%s where basedn=%s, scope=%s, filter=%s, attrs=%s, error=%s.

Cause: An internal error occurred where ldap_result could not process the records.

Action: Contact Oracle Support Services.
Level: 16

Type: ERROR

Impact: Session

OID-23022: In %s, failure parsing paging control response on server=%s, basedn=%s, scope=%s, filter=%s, attrs=%s, error=%s.

Cause: An internal error occurred where the paging control parsing failed.

Action: Contact Oracle Support Services.
Level: 16

Type: ERROR

Impact: Session

OID-23023: In %s, DIT synchronization failure for namingContext=%s where supplier=%s and consumer=%s.

Cause: See the following associated error messages for the actual cause

Action: More specific messages will accompany this message. Refer to the other messages for the appropriate action.
Level: 16

Type: ERROR

Impact: Session

OID-23024: In %s, NULL LDAPMod structure returned for DN=%s, agreement=%s.

Cause: An internal error occurred where the LDAPMod build routine returned NULL.

Action: Contact Oracle Support Services.
Level: 16

Type: ERROR

Impact: Data

OID-23025: In %s, during bootstrapping operation, synchronization of entry DN=%s failing as this entry does not exist at supplier. Supplier=%s, consumer=%s.

Cause: The entry might have been deleted at the supplier during the bootstrap process.

Action: Restart the bootstrap process.
Level: 16

Type: ERROR

Impact: Data

OID-23026: In %s, ldap_add failure for DN=%s where supplier=%s and consumer=%s with error=%s.

Cause: The target DN may have been added by some other process on the consumer node during the bootstrap process.

Action: Restart the bootstrap process.
Level: 16

Type: ERROR

Impact: Data

OID-23027: In %s, ldap_modify failure for DN=%s where supplier=%s and consumer=%s ith error=%s.

Cause: The target DN may have been deleted by some other process on the consumer node during the bootstrap process.

Action: Restart the bootstrap process.
Level: 16

Type: ERROR

Impact: Data

OID-23028: In %s, failure running DBMS_STATS.gather_schema_stats on server=%s.

Cause: Gathering of the schema statistics has failed.

Action: Manually run the job to gather the schema statistics.
Level: 16

Type: ERROR

Impact: Process

OID-23029: In %s, failure creating Hashtable. %s.

Cause: An internal error occurred where the Hashtable routine failed.

Action: Contact Oracle Support Services.
Level: 16

Type: ERROR

Impact: Memory

OID-23030: In %s, Hash Insert failure. %s.

Cause: An internal error occurred where the HashTable insert routine failed.

Action: Contact Oracle Support Services.
Level: 16

Type: ERROR

Impact: Data

OID-23031: In %s, ldap_search failed for ASR agreement on server=%s where basedn=%s, scope=%s, filter=%s, attrs=%s, error=%s.

Cause: For ASR replication, either the agreement DN was corrupt or not found.

Action: Using remtool, clean up the replication (asrcleanup) and set up the replication (asrsetup) again.
Level: 16

Type: ERROR

Impact: Session

OID-23032: In %s, failure inserting agreement for GroupDSA. Agreement=%s.

Cause: See the associated error messages for the actual cause.

Action: More specific messages will accompany this message. Refer to the other messages for the appropriate action.
Level: 16

Type: ERROR

Impact: Session

OID-23033: In %s, failure reading GroupDSA of Agreement: %s.

Cause: An internal error occurred where insert to DnList failed.

Action: Contact Oracle Support Services.
Level: 16

Type: ERROR

Impact: Session

OID-23034: In %s, failure reading attribute=%s from ASR replication agreement DN, %s.

Cause: ASR agreement DN was either corrupt or not set up properly.

Action: Using remtool, clean up the replication (asrcleanup) and set up the replication (asrsetup) again.
Level: 16

Type: ERROR

Impact: Data

OID-23035: In %s, unknown agreement protocol=%s under replication agreement DN, %s.

Cause: Wrong protocol attribute value under the agreement.

Action: Using remtool, clean up the replication and set up the replication again.
Level: 16

Type: ERROR

Impact: Data

OID-23036: In %s, failure getting current time. %s

Cause: An internal error occurred where the CurrentTime routine failed.

Action: Contact Oracle Support Services.
Level: 16

Type: ERROR

Impact: Operating System

OID-23037: In %s, failure initializing mutex for agreement DN=%s.

Cause: An internal error occurred where the mutex routine failed.

Action: Contact Oracle Support Services.
Level: 16

Type: ERROR

Impact: Memory

OID-23038: In %s, local replica context is NULL on server=%s, agreement=%s.

Cause: An internal error occurred where the local replica's context was not loaded.

Action: Contact Oracle Support Services.
Level: 16

Type: ERROR

Impact: Data

OID-23039: In %s, failure reading replication configuration on server=%s with basedn=%s, scope=%s, filter=%s, attrs=%s, error=%s.

Cause: The replication configuration entry (cn=Replication Configuration) was either corrupt or not found for the replica.

Action: Look at the OID server log and resolve the corresponding errors reported in the log. For further help contact Oracle Support Services.
Level: 16

Type: ERROR

Impact: Data

OID-23040: In %s, failure reading attribute=%s from LDAP replication agreement DN=%s on Server=%s.

Cause: LDAP agreement DN was either corrupt or not set up properly.

Action: Using remtool, delete the node and add the node with the right configuration.
Level: 16

Type: ERROR

Impact: Data

OID-23041: In %s, failure to get replica context,%s, from agreement,%s, on server=%s.

Cause: An internal error occurred where the replica context was not found in the list for an agreement.

Action: Contact Oracle Support Services.
Level: 16

Type: ERROR

Impact: Session

OID-23042: In %s, failure to load the LDAP agreement=%s for replica context=%s.

Cause: See the associated error messages for the actual cause

Action: More specific messages will accompany this message. Refer to the other messages for the appropriate action.
Level: 16

Type: ERROR

Impact: Session

OID-23043: In %s, failure initializing LDAP name context for agreement, %s.

Cause: See the associated error messages for the actual cause

Action: More specific messages will accompany this message. Refer to the other messages for the appropriate action.
Level: 16

Type: ERROR

Impact: Session

OID-23044: In %s, failure duplicating hash table. %s

Cause: An internal error occurred where the HashTable routine failed.

Action: Contact Oracle Support Services.
Level: 16

Type: ERROR

Impact: Memory

OID-23045: In %s, failure to get replication DN and password from the wallet where consumer=%s.

Cause: See the associated error messages for the actual cause

Action: More specific messages will accompany this message. Refer to the other messages for the appropriate action.
Level: 16

Type: ERROR

Impact: Session

OID-23046: In %s, failure getting the replication system configuration. Server=%s, Error=%s.

Cause: The entry "configset0" for replication does not exist

Action: Contact Oracle Support Services.
Level: 16

Type: ERROR

Impact: Session

OID-23047: In %s, failure to normalize naming context, %s. Server=%s, ErrorCode=%d.

Cause: An internal error occurred where the ldap routine failed.

Action: Contact Oracle Support Services.
Level: 16

Type: ERROR

Impact: Data

OID-23048: In %s, invalid replica DN entry under the replication configuration on server=%s.

Cause: Replication configuration subentry was either corrupt or not configured properly.

Action: Using remtool, clean up the replication and set up the replication again.
Level: 16

Type: ERROR

Impact: Data

OID-23049: In %s, failure to read attribute=%s from replicaDN=%s on server=%s.

Cause: Replica DN was either corrupt or not set up properly.

Action: Update this attribute with the correct value by using either ODSM or the command line. If this does not resolve the issue, use remtool to clean up replication, then set up replication again.
Level: 16

Type: ERROR

Impact: Data

OID-23050: In %s, failure to parse the URI value in replicaDN. %s.

Cause: Replica DN was either corrupt or not set up properly.

Action: Update this URI with the correct value by using either ODSM or the command line. If this does not resolve the issue, use remtool to clean up replication, then set up replication again.
Level: 16

Type: ERROR

Impact: Data

OID-23051: In %s, failure spawning thread. %s.

Cause: An internal error occurred where the spawning of a thread failed.

Action: Contact Oracle Support Services.
Level: 16

Type: ERROR

Impact: Threads

OID-23052: In %s, failure reading the replica id from replica DN=%s.

Cause: An internal error occurred where the DN parsing routine failed.

Action: Contact Oracle Support Services.
Level: 16

Type: ERROR

Impact: Data

OID-23053: In %s, failure creating the queue, %s. %s.

Cause: An internal error occurred where the Queue routine failed.

Action: Contact Oracle Support Services.
Level: 16

Type: ERROR

Impact: Session

OID-23054: In %s, failure getting the attribute=%s from the changeStatusEntry. Server=%s, agreement=%s, operation=%s.

Cause: Invalid changestatusentry DN.

Action: Contact Oracle Support Services.
Level: 16

Type: ERROR

Impact: Session

OID-23055: In %s, failure getting the attribute=%s from the root DSE. Server=%s, error=%d.

Cause: Either this attribute was corrupt or an internal error occurred in ldap_search.

Action: Look at the OID server log and resolve the corresponding errors reported in the log. For further help contact Oracle Support Services.
Level: 16

Type: ERROR

Impact: Data

OID-23056: In %s, Replica, %s is in offline mode.

Cause: Was unable to start the replication as the replica was in offline mode.

Action: Update the replica state to ONLINE and restart the replication server.
Level: 16

Type: ERROR

Impact: Session

OID-23057: In %s, failure beginning hash iteration for excluded namecontext. Server=%s, agreement=%s.

Cause: Either the agreement DN was corrupt or an internal error occurred in which the routine failed to get excluded namecontext.

Action: Using remtool, clean up the replication and set up the replication again. For further help contact Oracle Support Services.
Level: 16

Type: ERROR

Impact: Data

OID-23058: In %s, failure loading schema. Server=%s, error=%s.

Cause: An internal error occurred causing schema load to fail.

Action: Contact Oracle Support Services.
Level: 16

Type: ERROR

Impact: Data

OID-23059: In %s, failure finding %s in the schema. Server=%s.

Cause: An internal error occurred causing schema load to fail.

Action: Contact Oracle Support Services.
Level: 16

Type: ERROR

Impact: Data

OID-23060: In %s, error while loading %s from the schema. Server=%s.

Cause: An internal error occurred causing schema load to fail.

Action: Contact Oracle Support Services.
Level: 16

Type: ERROR

Impact: Data

OID-23061: In %s, failure binding to server. Server=%s, port=%d.

Cause: Either OID server was down or the replication password was incorrect.

Action: Ensure that the OID server is running. If the replication password has changed, restart the replication server.
Level: 16

Type: ERROR

Impact: Network

OID-23062: In %s, failure to initialize %s naming context checking rules. Server=%s, agreement=%s, error=%d.

Cause: An internal error occurred where initialization of the naming context checking rules failed.

Action: Contact Oracle Support Services.
Level: 16

Type: ERROR

Impact: Session

OID-23063: In %s, failure to initialize excluded attribute checking rules. Server=%s, agreement=%s, error=%s.

Cause: An internal error occurred where initialization of the excluded attribute checking rules failed.

Action: Contact Oracle Support Services.
Level: 16

Type: ERROR

Impact: Session

OID-23064: In %s, failure getting CORE context.

Cause: An internal error occurred where getCOREcontext failed.

Action: Contact Oracle Support Services.
Level: 16

Type: ERROR

Impact: Memory

OID-23065: In %s, failure beginning hash iteration. Server=%s, Error=%d.

Cause: An internal error occurred where the hash routine failed.

Action: Contact Oracle Support Services.
Level: 16

Type: ERROR

Impact: Memory

OID-23066: In %s, failure getting the error change log count.

Cause: See the associated error messages for the actual cause

Action: More specific messages will accompany this message. Refer to the other messages for the appropriate action.
Level: 16

Type: ERROR

Impact: Session

OID-23067: In %s, failure in comparing and reconciling schema of supplier, %s, and consumer, %s.

Cause: Comparison and reconciliation of attributes and objectclasses in the schema failed.

Action: Look at the replication server log and resolve the associated errors reported in the log. For futher help contact Oracle Support Services.
Level: 16

Type: ERROR

Impact: Data

OID-23068: In %s, failure to update changestatusEntry. Consumer=%s, supplier=%s, agreement=%s, changeno=%d.

Cause: See the associated error messages for the actual cause

Action: More specific messages will accompany this message. Refer to the other messages for the appropriate action.
Level: 16

Type: ERROR

Impact: Session

OID-23069: In %s, failure parsing count control response. Server=%s, agreement=%s, error=%s.

Cause: An internal error occurred where parse control failed.

Action: Contact Oracle Support Services.
Level: 16

Type: ERROR

Impact: Session

OID-23070: In %s, failure binding to server. Server=%s, port=%d.

Cause: Either OID server was down or the replication password was incorrect.

Action: Ensure that the OID server is running. If the replication password has changed restart the replication server.
Level: 16

Type: ERROR

Impact: Network

OID-23071: In %s, finding only one replica, %s, for the agreement, %s. Consumer=%s.

Cause: LDAP agreement was either corrupt or not set up properly.

Action: Using remtool, clean up the replication and set up the replication again.
Level: 1

Type: WARNING

Impact: Data

OID-23072: In %s, bootstrapping against non-leaf replica is not allowed. %s

Cause: Status of the replica was set to BOOTSTRAP, which is not allowed for non-leaf replica.

Action: Set the status to ONLINE for the replication to start, for this replica.
Level: 16

Type: ERROR

Impact: Data

OID-23073: In %s, bootstrap against master replica is not allowed. %s

Cause: Status of the replica was set to BOOTSTRAP, which is not allowed for master replica.

Action: Set the status to ONLINE for the replication to start, for this replica.
Level: 16

Type: ERROR

Impact: Configuration

OID-23075: In gslsbaAddEntry, orclpassword must not be in cleartext if the userpassword attribute is not present in the entry.

Cause: An attempt was made to add or modify the orclpassword attribute with a cleartext value while the userpassword attribute was not present in the entry.

Action: Ensure that the orclpassword attribute value is in a hash format.
Level: 16

Type: ERROR

Impact: Data

OID-23076: Trying to register more than the maximum number of plug-ins allowed.

Cause: There were 128 plug-ins configured in the OID. No more are allowed.

Action: Please check the existing plug-ins and make sure the total number of plug-ins is within the maximum limitation.
Level: 16

Type: ERROR

Impact: Configuration

OID-23077: In gslsbaUniqueCheck, objectclass is missing in the entry with DN %s.

Cause: The given entry was missing values for the objectclass attribute.

Action: Provide objectclass attributes with values in the entry being added.
Level: 16

Type: ERROR

Impact: Data

OID-23078: In gslsbpmCGetSubscriberpwdPolicy, unable to find root password policy.

Cause: The pwdpolicysubentry attribute in the root DSE was not populated, or the DN described in the pwdpolicysubentry attribute value did not exist.

Action: Ensure that the pwdpolicysubentry attribute is populated with the DN of a valid password policy entry.
Level: 16

Type: ERROR

Impact: Security

OID-23079: %s is not in UTC format. Unable to determine account validity for %s.

Cause: The orclactiveenddate or orclactivestartdate attribute in the entry associated with this message was not in UTC format.

Action: Ensure that orclactiveenddate and orclactivestartdate are always in UTC format.
Level: 16

Type: ERROR

Impact: Data

OID-23080: In gslbpvGenO3LogonVerifier, username is NULL.

Cause: When generating O3LogonVerifier, OID was unable to locate or construct a username (DN) by internal search or by user input.

Action: Ensure that the username (DN) is available.
Level: 16

Type: ERROR

Impact: Data

OID-23082: Encountering unsupported plug-in configuration.

Cause: An invalid plug-in configuration was found in OID.

Action: Examine all existing plug-in configurations and ensure all the plug-in conditions are specified correctly.
Level: 16

Type: ERROR

Impact: Configuration

OID-23083: Server with Process ID = %d is running but not responding.

Cause: The state of the server process with the specified PID was unstable and therefore the server did not respond.

Action: After the dispatcher process has retried checking status 1000 times, if the the server is still unresponsive, the dispatcher starts a new server process. Alternately, terminate the server process, which will result in a new server being launched automatically.
Level: 16

Type: ERROR

Impact: Process

OID-23084: ServerDispatcher: The new maximum instance specific concurrent connections setting is not immediately effective.

Cause: The new instance specific maximum concurrent connections limit was less than the total number of already established connections.

Action: The setting will automatically become effective when the number of established connections falls below the new limit. Alternatively, restart the instance for the new setting to be effective immediately.
Level: 16

Type: ERROR

Impact: Session

OID-23085: An invalid change log entry is being added to the shadow change log.

Cause: An internal error occurred.

Action: Contact Oracle Suppert Services.
Level: 16

Type: ERROR

Impact: Data

OID-23086: In gsldbb_AddAttrBVal, size of binary attribute to be added exceeds the max suported size.

Cause: Size of this binary attribute value exceeds max limit (4MB).

Action: Ensure that the binary attribute value's size is within max size limit and retry the operation.
Level: 16

Type: ERROR

Impact: Compliance

OID-23087: In gsldbb_AddAttrBVal, no value to add for binary attribute name.

Cause: The binary attribute value was empty.

Action: Ensure that the binary attribute value is not empty and then retry the operation.
Level: 16

Type: ERROR

Impact: Data

OID-23088: Detecting Illegal change log search condition %d.

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 16

Type: ERROR

Impact: Session

OID-23089: In gsldma_Modify, invalid value for attribute orclrefreshdgrmems.

Cause: Invalid value provided for dynamic group membership refresh attribute.

Action: Ensure that value of dynamic group membership refresh attribute - orclrefreshdgrmems - is either 0 or 1.
Level: 16

Type: ERROR

Impact: Compliance

OID-23090: In gslfadADoAdd, no value(s) provided for attribute %s.

Cause: No value(s) was given for this attribute in the ldapadd operation.

Action: Provide value(s) for the attribute and retry the ldapadd operation.
Level: 16

Type: ERROR

Impact: Data

OID-23091: In gslfbigciGetControlInfo, illegal format of control information.

Cause: The format of the control sent was invalid.

Action: Ensure that the format of the control sent is valid and retry the operation.
Level: 16

Type: ERROR

Impact: Requests/Responses

OID-23092: In gslfbigciGetControlInfo, illegal format of control Object ID.

Cause: The format of the sent control's OID is invalid.

Action: Ensure that the format of the sent control's OID is valid and retry the operation.
Level: 16

Type: ERROR

Impact: Requests/Responses

OID-23093: In gslfbirbiReadBindInfo, unsupported LDAP version %d.

Cause: Version of the client protocol used in the operation was not supported by the OID server.

Action: Ensure that client protocol version is supported.
Level: 16

Type: ERROR

Impact: Requests/Responses

OID-23094: In gslfbiSetAuthFromSSL, the certificate DN %s matches more than one entry in OID.

Cause: The client certificate does not uniquely identify an user entry in OID.

Action: Ensure that the certificate to DN mapping is n to 1 and retry the operation.
Level: 16

Type: ERROR

Impact: Security

OID-23095: In gslfblsafsSetAuthFromSSL, selected credential does not support client authentication.

Cause: The client did not send the client certificate credential required by the server.

Action: Check the client SSL crendential.
Level: 16

Type: ERROR

Impact: Security

OID-23096: In gslfblsafsSetAuthFromSSL, the certificate DN %s does not exist.

Cause: The client certificate contains a user DN that does not exist in the directory.

Action: Verify that the client certificate has a valid user DN in the directory and retry the operation.
Level: 16

Type: ERROR

Impact: Security

OID-23097: In gslfblsafsSetAuthFromSSL, illegal DN %s in the certificate.

Cause: The subject DN in the client certificate was invalid.

Action: Ensure that the subject DN in the client certificate is valid and retry the operation.
Level: 16

Type: ERROR

Impact: Security

OID-23098: In gslfdeADoDelete, Ldap v2 clients need to bind first.

Cause: Client was using protocol with LDAP version 2 and did not perform a ldapbind operation before issuing this LDAP operation.

Action: Ensure that if the client is using LDAP version 2, an ldapbind performed before any other LDAP operation.
Level: 16

Type: ERROR

Impact: Requests/Responses

OID-23099: In gslfseADoSearch, Ldap v2 clients need to bind first.

Cause: Client was using LDAP version 2 and did not perform an ldapbind operation before issuing this LDAP operation.

Action: Ensure that if the client is using LDAP version 2, an ldapbind is performed before any other LDAP operation.
Level: 16

Type: ERROR

Impact: Requests/Responses

OID-23100: In gslfseADoSearch, filter is invalid.

Cause: The search filter in the ldapsearch operation was not valid.

Action: Ensure that the search filter in the ldapsearch operation is valid.
Level: 16

Type: ERROR

Impact: Requests/Responses

OID-23101: In gslfseADoSearch, filter must be single AVA for user certificate binary for exact match.

Cause: In an exact match certificate search, the filter supplied was not a single attribute value assertion.

Action: Ensure that for the exact match certificate search, the filter supplied is a single attribute value assertion.
Level: 16

Type: ERROR

Impact: Requests/Responses

OID-23102: Unknown filter choice %d.

Cause: The filter choice in the ldapsearch operation was not valid.

Action: Ensure that the filter choice in the ldapsearch operation is valid.
Level: 16

Type: ERROR

Impact: Requests/Responses

OID-23103: In gsldbb_AddAttrBVal, failure retrieving certificate information from certificate (%d).

Cause: The certificate was not valid.

Action: Ensure the validity of the certificate.
Level: 16

Type: ERROR

Impact: Security

OID-23104: In gsldbb_AddAttrBVal, failure converting certificate serial number from binary to base 64-encoded string (%d).

Cause: Invalid certificate serial number.

Action: Check the serial number in the certificate.
Level: 16

Type: ERROR

Impact: Security

OID-23105: Line %d: missing < = > in (or value after) < %s > in to clause.

Cause: Attribute list was not provided in ACI directive clause governing attributes.

Action: Examine ACI syntax documentation and provide attribute list in required format.
Level: 16

Type: ERROR

Impact: Data

OID-23106: Line %d: erroneous attribute list < %s > in to clause.

Cause: The attribute list was incorrectly formatted.

Action: Examine ACI syntax documentation and reformat the ACI clause to adhere to the expected format.
Level: 16

Type: ERROR

Impact: Data

OID-23107: Attribute %s not defined in schema (entrydn=%s).

Cause: An attribute not defined in the directory schema was part of the ACI clause.

Action: Remove all attributes not defined in the directory schema from ACI directives.
Level: 16

Type: ERROR

Impact: Data

OID-23108: gslecLRU: Entry cache is full, could not free up size %u.

Cause: Entry Cache is FULL.

Action: Increase the Entry Cache size.
Level: 16

Type: ERROR

Impact: Memory

OID-23109: oidctl: instance parameter is missing.

Cause: Instance name is missing.

Action: Provide the instance name and retry.
Level: 16

Type: ERROR

Impact: Process

OID-23110: oidctl: Config set entry cn=configset%u,%s does not exist.

Cause: An attempt was made to bring up an instance with a nonexistent configset entry.

Action: Ensure that the configset entry exists and retry.
Level: 16

Type: ERROR

Impact: Data

OID-23111: oidctl: Invalid parameters passed in flags.

Cause: Parameters passed in flags were invalid.

Action: Ensure that parameters in flags are valid and retry.
Level: 16

Type: ERROR

Impact: Process

OID-23112: Key %s already in use.

Cause: Multiple realms may be pointing to the same usersearchbase.

Action: Ensure that usersearchbase definitions in realms do not collide.
Level: 16

Type: ERROR

Impact: Data

OID-23113: In %s, failure cleaning up the change logs from supplier, %s to consumer, %s.

Cause: See the associated error messages for the actual cause.

Action: More specific messages will accompany this message. Refer to the other messages for the appropriate action.
Level: 16

Type: ERROR

Impact: Data

OID-23116: %s : Memory allocation failed for %s.

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Memory

OID-23117: DispatcherController : OS : Error creating thread management queue.

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Threads

OID-23118: DispatcherController : OS : Error creating thread sync mutex.

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Threads

OID-23119: DispatcherController : Error in creating dispatcher process server queue.

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Process

OID-23120: OS %d : Failed to enqueue in %s.

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Operating System

OID-23121: Unable to register %s.

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Operating System

OID-23122: Polling port failed with error %d.

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Operating System

OID-23123: DispatcherController : OS %d : Opening of communication control port failed.

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Operating System

OID-23124: The server with Process ID = %d is not running.

Cause: The server process failed.

Action: Check the core dump or the stack trace and contact Oracle Support Services.
Level: 16

Type: ERROR

Impact: Process

OID-23125: The server with Process ID=%d is not responsive; restarting the server.

Cause: Server process is not responding because the system might be busy.

Action: The original unresponsive process will be killed.
Level: 16

Type: ERROR

Impact: Process

OID-23127: OS Error -(%d) :Error in polling.

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Operating System

OID-23128: In gslsflAcceptConnAndSend, OS %d : unable to accept new TCP connection.

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Operating System

OID-23130: %s : OS %d : Setting up/attaching of shared memory failed.

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Operating System

OID-23132: ServerController : OS : Error creating internal queues.

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Operating System

OID-23135: ServerController : OS : error initializing SM thread condition variable's mutex.

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Operating System

OID-23137: ServerController: hash table creation for user operations failed.

Cause: System resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Operating System

OID-23138: ServerController: error initializing r/w lock for user operations hash.

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Operating System

OID-23141: Signalling dispatcher thread failed.

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Operating System

OID-23142: No free connection available; dropping the connId = %d.

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Operating System

OID-23144: Exceeding maximum number of connections allowed. Num Conns = %d, Max Conns = %d, Closing the connection.

Cause: The number of LDAP connections to OID server exceeded the maximum limit.

Action: Check for applications or users with leaked or improperly prolonged LDAP connections and perform the appropriate corrective actions. In addition, if deemed necessary, relaunch the OID server instance with more server processes in order to achieve adequate connection handling capacity.
Level: 16

Type: ERROR

Impact: Programmatic

OID-23145: Socket fd=%d greater than system max=%d numconns=%d. Closing the connection.

Cause: The number of sockets or file descriptors to OID server have reached system maximum limit.

Action: Check for system maximum number of file decriptors. Check for applications with leaked or improperly prolonged LDAP connections and perform the appropriate corrective actions. In addition, if deemed necessary, relaunch the OID server instance with more server processes in order to achieve adequate connection handling capacity.
Level: 16

Type: ERROR

Impact: Operating System

OID-23147: ServerListener : OS %d : unable to contact dispatcher.

Cause: Either the dispatcher failed or the administrator is initiating a shutdown.

Action: Check the core dump or stack trace. For further assistance contact Oracle Support Services.
Level: 16

Type: ERROR

Impact: Operating System

OID-23148: ServerListener : Lost contact with dispatcher.

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Operating System

OID-23155: In gslsfliInitnzoscontext, nzos initialization failed with NZ %d.

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Operating System

OID-23157: In gslsfliInitnzoscontext, creation of nzos context failed.

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Operating System

OID-23158: In gslsfliInitnzoscontext, failure initializing the DML context.

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Operating System

OID-23159: In gslsfliInitnzoscontext, failure with NZ %d when opening wallet %s.

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Operating System

OID-23160: In gslsfliInitnzoscontext, failure setting credentials in nzos context.

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Operating System

OID-23161: In gslsfliInitnzoscontext, failure setting cipher choice in nzos context.

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Operating System

OID-23162: ServerWorker : OS : gslesioIBerAlloc failed.

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Operating System

OID-23163: Database connection is unavailable. Shutting down.

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Operating System

OID-23164: ServerWorker : OS : BER allocation failed.

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Operating System

OID-23165: ServerWorker : Received unknown operation tag.

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Operating System

OID-23166: In gslarswWorker, memory allocation of maxFiltSize = %d failed.

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Memory

OID-23167: Too many unique constraints: > %d.

Cause: The number of unique constraints was larger than the maximum allowed.

Action: Reduce the number of unique constraints.
Level: 16

Type: ERROR

Impact: Configuration

OID-23168: Database error in gslsbaAddEntry [gsldpoOperationComplete].

Cause: Commit or rollback failed.

Action: Check the database log and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Data

OID-23169: In gslsbaAddEntry, entry cache update failed after commit to database.

Cause: System Resource constraint.

Action: Check the database log and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Data

OID-23170: In gslsbaAddEntry, failure reallocating memory to modify subschema_subentries attribute in backend struct.

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply corrective measures.
Level: 16

Type: ERROR

Impact: Memory

OID-23171: In gslbDeleteEntry, failure to remove subschemasubentry DN from Root DSE because memory allocation failed.

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Memory

OID-23172: In gslsbmModify, schema hash search failed for attr %s.

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Memory

OID-23173: In gslsbmdModifyDN, update of dynamic group memberships failed.

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Memory

OID-23174: In gslsbmdModifyDN, update of dynamic group DNs in cache failed.

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Memory

OID-23175: In gslsbmdModifyDN, reload of password policy failed.

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Memory

OID-23176: In gslsbmdModifyDN, error in deleting component subschema-subentry DN from root DSE entry.

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Operating System

OID-23177: In gslsbmdModifyDN, error in adding component subschema-subentry DN to root DSE entry.

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Operating System

OID-23178: In gslsbmdModifyDN, database error [gsldpoOperationComplete].

Cause: Commit or roll back failed

Action: Check the database log and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Data

OID-23180: In gslsbmdModifyDN, error in orclacpgroup cache reload.

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Memory

OID-23183: In gsldazb_InsertAttrib, certificate hash generation failed (%d).

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Memory

OID-23184: In gsldasaDbInsUserStats, hash table pointer for user %s operation is NULL.

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Memory

OID-23185: In gsldasaDbInsUserStats, Op: %s lcvb2werr() returned invalid base error for Eid string %s. Setting dummy value %d for Eid.

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Data

OID-23186: In gsldasaDbInsUserStats, Op: %s * lcvb2werr() returned overflow error for Eid string %s. Setting dummy value %d for Eid.

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Data

OID-23187: In gsldasaDbInsUserStats, lcvb2werr() returned invalid input for Eid string %s. Setting dummy value %d for Eid.

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Data

OID-23188: In gsldasaDbInsUserStats, OpName: %s beginning of read-only iteration of 2nd level (comp obj) hash table has failed.

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Data

OID-23189: In gsldasaDbInsUserStats, ORA-%d occurred while inserting compare (detail) SM stats.

Cause: Database error occurred.

Action: Check the database log and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Data

OID-23190: In gsldasaDbInsUserStats, ORA-%d while inserting user stats.

Cause: Database error occurred.

Action: Check the database log and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Data

OID-23191: In gsldasaDbInsUserStats, ORA-%d while inserting user stats. Error = %s.

Cause: Database error occurred.

Action: Check the database log and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Data

OID-23192: In gsldbdDelAttrBVal, size of binary attribute to be deleted exceeds the max supported size.

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Compliance

OID-23193: In gsldbdDelAttrBVal, no value to delete for binary data.

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Data

OID-23194: In gsldbc_DelAttrBVal, failure retrieving certificate information (%d).

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Data

OID-23195: In gsldbc_DelAttrBVal, failure converting certificate serial number from binary to base 64 encoded string (%d).

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Memory

OID-23196: In gsldmf_BVal2StrCertHashList, error generating certificate hash.

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Memory

OID-23197: In gsldusaGetCtxNmSpcParVal, ORA-%d:%s encountered.

Cause: Database error occurred.

Action: Check the database log and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Data

OID-23198: In gslesrdBerGetNext, memory allocation failed len %d ber->ber_len %d.

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Memory

OID-23199: In gsleswrrwRawWrite %d, writing to network failed due to hard or unknown error.

Cause: Client is not responding after sending the operation request.

Action: Contact Oracle Support Services.
Level: 16

Type: ERROR

Impact: Network

OID-23201: OS %d : error spawning dispatcher thread.

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Operating System

OID-23202: In gslffiCGetSubstringFilter, substring filter is not supported for usercertificate binary attribute.

Cause: Unsupported substring filter was provided for usercertificate attribute search.

Action: Provide valid filter for usercertificate attribute search.
Level: 16

Type: ERROR

Impact: Requests/Responses

OID-23203: In gslffiGBldBinFltrSrchParam, either the separator is missing or the certificate match value in filter string %s is incomplete.

Cause: Filter provided for certificate match value for usercertificate attribute search was invalid.

Action: Provide valid certificate match value for filter in usercertificate attribute search.
Level: 16

Type: ERROR

Impact: Requests/Responses

OID-23204: Unsupported filter choice.

Cause: Filter provided for the search operation was not supported or was unknown.

Action: Provide valid filter for the search operation and retry.
Level: 16

Type: ERROR

Impact: Requests/Responses

OID-23205: In gslarswWorker, received HA down event. Requesting new DB connection.

Cause: The database has gone down.

Action: No user action needed, OID will handle database connection failover automatically.
Level: 16

Type: ERROR

Impact: High Availability

OID-23206: In gslarutbDequeueDBConnection, connection dequeued received HA down event. Creating new DB connection.

Cause: Database has gone down.

Action: No user action needed, OID will handle database connection failover automatically.
Level: 16

Type: ERROR

Impact: High Availability

OID-23207: In gsldhacHACallback, HA Callback Event Thread Id: %d Event type: %d HA Source: %s Host name: %s Database name: %s Instance name: %s Timestamp: %s Service name: %s HA status: %s

Cause: Database has come up or gone down.

Action: No user action needed, OID will handle database connection failover automatically.
Level: 16

Type: ERROR

Impact: High Availability

OID-23208: In gsluirsclLoadSchema, error in %s %s line %d in gsluirsclLoadSchema.

Cause: Incorrect definition in schema.

Action: Correct the definition in schema.
Level: 16

Type: ERROR

Impact: Data

OID-23209: In gslsfliInitnzoscontext, failure setting orclsslinteropmode flag in nzos context.

Cause: System Resource constraint.

Action: Check the system resource utilization on the machine and apply appropriate corrective measures.
Level: 16

Type: ERROR

Impact: Operating System

OID-23210: One or more of the required indexes (rp_dn, st_orclnormdn, ei_attrstore) are missing. Server will operate in READ-MODIFY mode.

Cause: bulkload index=true was not run.

Action: Run bulkload index=true to re-create the indexes.
Level: 16

Type: ERROR

Impact: Data

OID-23211: In %s, failure to parse entry count control response. Server=%s, basedn=%s, scope=%s, filter=%s, attrs=%s, error=%s.

Cause: An internal error occurred where the entry count control parsing failed.

Action: Contact Oracle Support Services.
Level: 16

Type: ERROR

Impact: Session

OID-23212: Failure accessing Oracle database (oracle errcode=%d).

Cause: A database connection was terminated.

Action: Check if the database was shut down or check the database alert log for further details.
Level: 16

Type: ERROR

Impact: Session

OID-23213: In %s, Bootstrapping is in error condition and ldapserver seems to be down, So shutting down the replication server.

Cause: Some of the naming contexts failed to bootstrap and orclreplicastate can not be set to BOOTSTRAP_ERROR mode

Action: Check if the ldap server was shut down. Once it is up, set the orclreplicastate appropriately and start the replication server.
Level: 16

Type: ERROR

Impact: Session

OID-23734: In %s, failure initializing synchronization lock, %s.

Cause: An internal error occurred where the lock routine failed.

Action: Contact Oracle Support Services.
Level: 16

Type: ERROR

Impact: Session

OID-23736: Replication DN password expired. Replication DN=%s and server=%s.

Cause: The replication user's account has expired.

Action: Reset the replication DN password.
Level: 16

Type: ERROR

Impact: Security

OID-23737: Replication DN account is locked. Replication DN=%s, Server=%s.

Cause: The configured maximum consecutive bind failures allowed for Replication DN was exceeded.

Action: Unlock the replication DN account.
Level: 16

Type: ERROR

Impact: Security

71 OHS-03501 to OHS-03813

OHS-03501: File copy failed because of {0} exception.

Cause:

Action: Check OHS Component provisioning files.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03502: {0} exception occurred while removing configuration files.

Cause:

Action: Check configuration files.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03503: {0} exception occurred while creating component.

Cause:

Action: See exception to identify problem.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03504: {0} exception occurred while registering the OHS content dir with BR Service.

Cause:

Action: See exception to identify problem.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03505: List KeyStore exception

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03506: OHS audit configuration load failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03507: OHS audit configuration save failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03508: Unable to set Custom Log configuration

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03509: CustomLog configuration is wrong

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03510: Exception while disabling OHS module

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03511: {0} exception occurred while trying to get configuration from configService.

Cause:

Action: See exception to identify problem.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03512: Configuration document not found.

Cause:

Action: Check for configuration document.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03513: {0} exception occured while trying to read document.

Cause:

Action: See exception to identify problem or check document.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03514: {0} exception occured while trying to write document.

Cause:

Action: See exception to identify problem.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03515: {0} exception occured while trying to read config segment.

Cause:

Action: See exception to identify problem.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03516: Null parameter(s) passed.

Cause:

Action: Pass non-null parameters.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03517: {0} exception occured while parsing directive.

Cause:

Action: See exception to identify problem.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03518: {0} exception occured while attempting to read httpd.conf.

Cause:

Action: See exception to identify problem or check the httpd.conf file.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03519: {0} exception occured while attempting to write httpd.conf.

Cause:

Action: See exception to identify problem or check the httpd.conf file.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03520: Nothing to save.

Cause:

Action: Create or load a file.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03521: {0} exception occured while attempting to write mod_osso.conf.

Cause:

Action: See exception to identify problem or check the mod_osso.conf file.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03522: VirtualServer {0} does not exist

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03523: {0} exception occured while attempting to write mod_oc4j.conf.

Cause:

Action: See exception to identify problem or check the mod_oc4j.conf file.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03524: Can not find IfModule mod_oc4j.c container in mod_oc4j.conf

Cause:

Action: Check the mod_oc4j.conf file.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03525: mod_oc4j.conf file not present

Cause:

Action: Check for the mod_oc4j.conf file.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03526: Failed to read file {0}, because of {1} exception.

Cause:

Action: Check file path or directory location.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03527: Failed to write file {0}, because of {1} exception.

Cause:

Action: Check file path or directory location.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03528: Can not find value for directive {0}.

Cause:

Action: Check file for directive if it is actually required.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03529: httpd.conf has not been loaded.

Cause:

Action: Check the httpd.conf file.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03530: failed to delete directive

Cause:

Action: See exception to identify problem.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03531: Object passed in is of an invalid class.

Cause:

Action: Pass an object of a valid class.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03532: mod_osso.conf has not been loaded.

Cause:

Action: Check the mod_osso.conf file.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03533: mod_oc4j.conf has not been loaded.

Cause:

Action: Check the mod_oc4j.conf file.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03534: Exception in getPropertiesFromBinaryFile: {0}

Cause:

Action: Check that the file has been created correctly.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03535: 902 format is not supported. Exception is {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03536: 902 format supported.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03537: Exception occured while obfuscating string contents. Exception is {0}.

Cause:

Action: See exception to identify problem.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03538: Exception occured while writing to osso.conf file. Exception is {0}.

Cause:

Action: See exception to identify problem.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03539: Exception in getOSSOConfFile: {0}

Cause:

Action: See exception to identify problem.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03540: Error reading configuration document: {0}

Cause:

Action: Check that the location of the document has been correctly specified.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03541: Input parameters are null.

Cause:

Action: Provide appropriate arguments when calling mod_osso registration code.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03542: SSO DB partner version received is null.

Cause:

Action: Check that SSO DB version is supplied when calling partner registration code.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03543: Partner application site ID received is null.

Cause:

Action: Check that partner site ID is supplied when calling partner registration code.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03544: Partner application site token received is null.

Cause:

Action: Check that partner site token is supplied when calling partner registration code.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03545: Partner application login URL received is null.

Cause:

Action: Check that login URL is supplied when calling partner registration code.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03546: Partner application logout URL received is null.

Cause:

Action: Check that logout URL is supplied when calling partner registration code.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03547: Partner application timeout cookie received is null.

Cause:

Action: Check that timeout cookie is supplied when calling partner registration code.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03548: Partner application timeout key received is null.

Cause:

Action: Check that timeout key is supplied when calling partner registration code.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03549: Partner application urlc version received is null.

Cause:

Action: Check that urlc version is supplied when calling partner registration code.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03550: Partner application preencryption mask received is null.

Cause:

Action: Check that preencryption mask is supplied when calling partner registration code.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03551: Partner application post-encryption mask received is null.

Cause:

Action: Check that post-encryption mask is supplied when calling partner registration code.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03552: Partner application cancel URL received is null.

Cause:

Action: Check that cancel URL is supplied when calling partner registration code.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03553: Partner application non-SSL SSO host received is null.

Cause:

Action: Check that non-SSL SSO host is supplied when calling partner registration code.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03554: Partner application OSSO configuration file path received is null.

Cause:

Action: Check that configuration file path is supplied when calling partner registration code.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03555: Exception occured during reading of input values. Error was: {0}

Cause:

Action: Check that all necessary inputs are correctly supplied to the partner registration tool.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03556: The osso.conf file was added successfully.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03557: Status: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03558: The osso.conf file was not added. Operation failed.

Cause:

Action: Check previous exception for additional information.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03559: The osso.conf file was retrieved successfully.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03560: The osso.conf file could not be retrieved. Operation failed.

Cause:

Action: Check previous exception for additional information.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03561: The osso.conf file was deleted successfully.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03562: The osso.conf file could not be deleted. Operation failed.

Cause:

Action: Check previous exception for additional information.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03563: Already enabled. Configuration document already exists.

Cause:

Action: Check name or select a diffent module.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03564: Null MAS configuration object encountered.

Cause:

Action: See exception to identify problem.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03565: ManagementException occurred reading {0}.

Cause:

Action: Check previous exception for additional information.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03566: IOException occurred reading {0}.

Cause:

Action: Check previous exception for additional information.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03567: failed to update file {0}.

Cause:

Action: Check previous exception for additional information.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03568: failed to update file due to invalid contents.

Cause:

Action: Check previous exception for additional information.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03569: Null exception reference encountered when attempting handling exception.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03570: ThreadLimit may not exceed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03571: ServerLimit may not exceed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03572: Max Clients exceeds range, raise ServerLimit.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03573: Max Clients exceeds range, raise ServerLimit or ThreadPerChild.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03574: mod_osso is not enabled. mod_osso must be enabled before modifying osso related directives.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03575: The value of ThreadLimit cannot be less than the value of ThreadsPerChild.

Cause:

Action: Use a larger value for ThreadLimit or lower the ThreadsPerChild value.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03576: The value of ThreadsPerChild cannot be greater than the value of ThreadLimit.

Cause:

Action: Use a smaller value for ThreadsPerChild or raise the value of ThreadLimit.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03577: The value of ServerLimit cannot be less than the value of MaxClients.

Cause:

Action: Use a larger value for ServerLimit or lower the value of MaxClients.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03578: The value of ServerLimit * ThreadsPerChild cannot be less than the value of MaxClients.

Cause:

Action: Use a larger value for ServerLimit and/or ThreadsPerChild, or lower the value of MaxClients.
Level: 1

Type: ERROR

Impact: Runtime

OHS-03579: Virtual Host Already Exists

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03580: Not a proper Virtual Host Name

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03581: Enable Module failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03582: Module is not installed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03583: Register child MBean api failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03584: Proxy Port MBean registration failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03585: Audit MBean registartion failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03586: Parsing error while loading MBeans

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03587: Exception occurred while loading MBeans

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03588: Virtual Host creation failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03589: Duplicate virtual host found

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03590: Base Virtual host creation failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03591: Configuration file parsing failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03592: OraDev config MBean registration failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03593: Unregister of Keystore MBean success

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03594: Unregister of configuration MBeans failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03595: Unable to get VH objects from root OHS MBean

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03596: Load wallets failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03597: Removal of Virtual Host failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03598: Removal of Listen failed while removing VH

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03599: Configuration Restore failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03600: Configuration validation failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03601: Load failed with IOException

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03602: Module Name is wrong

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03603: Unable to find the MPM Name, Setting it to default Worker

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03604: Unable to find Server Name, Setting it to default AdminServer

Cause:

Action:
Level: 1

Type: ERROR

Impact: Runtime

OHS-03701: Error log configuration not valid

Cause:

Action:
Level: 1

Type: WARNING

Impact: Runtime

OHS-03702: Saving wallet is null

Cause:

Action:
Level: 1

Type: WARNING

Impact: Runtime

OHS-03703: P12 Wallet is null; Possibly because the wallet is absent/not configured.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Runtime

OHS-03704: CWallet is null, not able to load cwallet

Cause:

Action:
Level: 1

Type: WARNING

Impact: Runtime

OHS-03705: Directive does not exist

Cause:

Action:
Level: 1

Type: WARNING

Impact: Runtime

OHS-03706: WLPort not configured; Illegal Usage

Cause:

Action:
Level: 1

Type: WARNING

Impact: Runtime

OHS-03707: WLHost not configured; Illegal Usage

Cause:

Action:
Level: 1

Type: WARNING

Impact: Runtime

OHS-03708: WLCluster not configured; Not allowed to call listWLCluster

Cause:

Action:
Level: 1

Type: WARNING

Impact: Runtime

OHS-03709: DynamicServerList is not configured ; Illegal Usage

Cause:

Action:
Level: 1

Type: WARNING

Impact: Runtime

OHS-03710: CertValidationPath is not configured

Cause:

Action:
Level: 1

Type: WARNING

Impact: Runtime

OHS-03711: CertValidation is not configured ; Illegal Usage

Cause:

Action:
Level: 1

Type: WARNING

Impact: Runtime

OHS-03712: SSLWallet is not configured ; Illegal Usage

Cause:

Action:
Level: 1

Type: WARNING

Impact: Runtime

OHS-03713: SSLAuthtype is not configured ; Illegal Usage

Cause:

Action:
Level: 1

Type: WARNING

Impact: Runtime

OHS-03714: SSLCiphers is not configured ; Illegal Usage

Cause:

Action:
Level: 1

Type: WARNING

Impact: Runtime

OHS-03715: SSLVersions is not configured

Cause:

Action:
Level: 1

Type: WARNING

Impact: Runtime

OHS-03716: SSLEnabled is not configured ; Illegal Usage

Cause:

Action:
Level: 1

Type: WARNING

Impact: Runtime

OHS-03801: Load Operation failed in VH SSLResource

Cause:

Action:
Level: 1

Type: INFORMATION

Impact: Runtime

OHS-03802: Load Operation finished in VH SSLResource

Cause:

Action:
Level: 1

Type: INFORMATION

Impact: Runtime

OHS-03803: Configuration file backup success

Cause:

Action:
Level: 1

Type: INFORMATION

Impact: Runtime

OHS-03804: Load operation success

Cause:

Action:
Level: 1

Type: INFORMATION

Impact: Runtime

OHS-03805: Module is already configured

Cause:

Action:
Level: 1

Type: INFORMATION

Impact: Runtime

OHS-03806: Unregistered all configuration MBeans

Cause:

Action:
Level: 1

Type: INFORMATION

Impact: Runtime

OHS-03807: Wildcard char, allow processing

Cause:

Action:
Level: 1

Type: INFORMATION

Impact: Runtime

OHS-03808: Error log configuration mode is not apache

Cause:

Action:
Level: 1

Type: INFORMATION

Impact: Runtime

OHS-03809: Error log Mode is apache

Cause:

Action:
Level: 1

Type: INFORMATION

Impact: Runtime

OHS-03810: Listen Directive not configured

Cause:

Action:
Level: 1

Type: INFORMATION

Impact: Runtime

OHS-03811: Listen Directive already exist for specified port

Cause:

Action:
Level: 1

Type: INFORMATION

Impact: Runtime

OHS-03812: Configuration Restore success

Cause:

Action:
Level: 1

Type: INFORMATION

Impact: Runtime

OHS-03813: OHS Validation successfull

Cause:

Action:
Level: 1

Type: INFORMATION

Impact: Runtime

72 OPM-00500 to OPM-00745

OPM-00500: Could not route request to specified scope.

Cause: The specified scope was not found in the local OPMN server's table.

Action: *Define: OPMN_NLS_UNRESOLVED_SCOPE
Level:

Type:

Impact: Other

OPM-00501: StartPset startpSet Proc %u:%u could not schedule new start (%s)

Cause: A new process could not be started as part of an autostart dependency requirement.

Action: *Define: OPMN_NLS_MSG_00115
Level:

Type:

Impact: Other

OPM-00502: Monitor Proc %u:%u invalid action: %d

Cause: An internal OPMN process action state had an invalid value

Action: *Define: OPMN_NLS_MSG_00116
Level:

Type:

Impact: Other

OPM-00503: DMS segment in the notification body has null element name or value.

Cause: Invalid DMS data reported by client process.

Action: *Define: OPMN_NLS_MSG_00117
Level:

Type:

Impact: Other

OPM-00504: Invalide DMS element name: %s

Cause: Invalid DMS element name reported by client process.

Action: *Define: OPMN_NLS_MSG_00118
Level:

Type:

Impact: Other

OPM-00505: module specific error

Cause: The process module encountered an error: see the associated text.

Action: *Define: OPMN_NLS_GENERIC_MODULE
Level:

Type:

Impact: Other

OPM-00506: RMD %s no duration for operator

Cause: A duration resource could not be found for the operator.

Action: *Define: OPMN_RMD_NO_DURATION
Level:

Type:

Impact: Other

OPM-00507: RMD %s conditional invalid time comparison

Cause: A conditional contains a comparison of time value against another operand type.

Action: *Define: OPMN_RMD_COND_TIME_COMPARE
Level:

Type:

Impact: Other

OPM-00508: RMD %s conditional invalid integer comparison

Cause: A conditional contains a comparison of an integer value against a non numerical value.

Action: *Define: OPMN_RMD_COND_INTEGER_COMPARE
Level:

Type:

Impact: Other

OPM-00509: Failed to create pm publisher.

Cause: Internal error while creating an ONS publisher.

Action: *Define: OPMN_NLS_MSG_00123
Level:

Type:

Impact: Other

OPM-00510: Failed to create pm monitor thread.

Cause: Internal error while creating monitor thread for processes.

Action: *Define: OPMN_NLS_MSG_00124
Level:

Type:

Impact: Other

OPM-00511: PROC_READY subscription failed.%s%s

Cause: Internal error while subscribing to client PROC_READY notifications.

Action: *Define: OPMN_NLS_MSG_00125
Level:

Type:

Impact: Other

OPM-00512: Module %s: library load error:%s

Cause: The shared library for the specified module could not be loaded.

Action: Check the path for the module in opmn.xml. *Define: OPMN_NLS_MSG_00126
Level:

Type:

Impact: Other

OPM-00513: Module %s: no initialization callback

Cause: The specified module does not have an initialization function.

Action: Check the path for the module in opmn.xml. *Define: OPMN_NLS_MSG_00127
Level:

Type:

Impact: Other

OPM-00514: XML parse: %s, process-type: %s, module: %s is mising start callback.

Cause: The module for the specified process type does not have an start function.

Action: Check the path for the module in opmn.xml. *Define: OPMN_NLS_MSG_00128
Level:

Type:

Impact: Other

OPM-00515: Module %s: cron interval configured but no cron function

Cause: A cron interval has been configured for the specified module, but the module library does not have a cron function.

Action: Check the path for the module in opmn.xml or remove the configured cron interval for the module in opmn.xml. *Define: OPMN_NLS_MSG_00129
Level:

Type:

Impact: Other

OPM-00516: Module %s: critical module initialization failed.

Cause: Initialization for a module configured as critical has failed.

Action: *Define: OPMN_NLS_MSG_00130
Level:

Type:

Impact: Other

OPM-00517: Module %s: initialization failed (base)

Cause: The module's initalization base call failed.

Action: *Define: OPMN_NLS_MSG_00131
Level:

Type:

Impact: Other

OPM-00518: Module %s: initialization failed (proc type %s)

Cause: The module's initalization process-type call failed.

Action: *Define: OPMN_NLS_MSG_00132
Level:

Type:

Impact: Other

OPM-00519: Module %s: initialization failed (proc set %s)

Cause: The module's initalization process-set call failed.

Action: *Define: OPMN_NLS_MSG_00133
Level:

Type:

Impact: Other

OPM-00520: Create pm state directory: %s

Cause: The OPMN state directory will be created.

Action: *Define: OPMN_NLS_MSG_00134
Level:

Type:

Impact: Other

OPM-00521: Failed to create pm state directory (%s): %s

Cause: The OPMN state directory could not be created.

Action: Check the directory permissions to $ORACLE_HOME/opmn/logs or the id of the user attempting to start OPMN. *Define: OPMN_NLS_MSG_00135
Level:

Type:

Impact: Other

OPM-00522: PM state directory exists: %s

Cause: The OPMN state directory already exists.

Action: *Define: OPMN_NLS_MSG_00136
Level:

Type:

Impact: Other

OPM-00523: Failed to create pm state file (%s): %s

Cause: The OPMN state file could not be created.

Action: Check the directory permissions to $ORACLE_HOME/opmn/logs/state or the id of the user who started OPMN. *Define: OPMN_NLS_MSG_00137
Level:

Type:

Impact: Other

OPM-00524: Failed to create static process state file (%s): %s

Cause: The OPMN process static state file could not be created.

Action: Check the directory permissions to $ORACLE_HOME/opmn/logs/state or the id of the user who started OPMN. *Define: OPMN_NLS_MSG_00138
Level:

Type:

Impact: Other

OPM-00525: Proc %u:%u rename (%s) %s to %s

Cause: The rename of the process static state file to the process specific state file failed.

Action: Check the directory permissions to $ORACLE_HOME/opmn/logs/state or the id of the user who started OPMN. *Define: OPMN_NLS_MSG_00139
Level:

Type:

Impact: Other

OPM-00526: PM state file does not exist: %s

Cause: The OPMN state file does not exist.

Action: *Define: OPMN_NLS_MSG_00140
Level:

Type:

Impact: Other

OPM-00527: Failed to open pm state directory (%s): %s

Cause: The OPMN state directory could not be opened.

Action: Check the directory permissions to $ORACLE_HOME/opmn/logs/state or the id of the user who started OPMN. *Define: OPMN_NLS_MSG_00141
Level:

Type:

Impact: Other

OPM-00528: Recovery: Proc %u:%u -- %s: line %d\tError on %s

Cause: An error was encountered at the given line of the process state file.

Action: *Define: OPMN_NLS_MSG_00143
Level:

Type:

Impact: Other

OPM-00529: Recovery: %s: %s

Cause: The process state file could not be accessed.

Action: Check the directory permissions to $ORACLE_HOME/opmn/logs/state or the id of the user who started OPMN. *Define: OPMN_NLS_MSG_00144
Level:

Type:

Impact: Other

OPM-00530: Recovery: Proc %u:%u -- process-set not found\t%s, %s, %s, %s

Cause: The given process-set for the given process is no longer configured.

Action: *Define: OPMN_NLS_MSG_00146
Level:

Type:

Impact: Other

OPM-00531: Recovery: Proc %u:%u configuration disabled -- stopping

Cause: The given process is being stopped as part of OPMN recovery.

Action: *Define: OPMN_NLS_MSG_00147
Level:

Type:

Impact: Other

OPM-00532: Recovery: Proc %u:%u port configuration conflict -- stopping

Cause: The given process' ports now conflict with what is configured in opmn.xml.

Action: *Define: OPMN_NLS_MSG_00148
Level:

Type:

Impact: Other

OPM-00533: Rename (%s) %s to %s

Cause: The rename of the process state file to a stale process state file failed.

Action: Check the directory permissions to $ORACLE_HOME/opmn/logs/state or the id of the user who started OPMN. *Define: OPMN_NLS_MSG_00149
Level:

Type:

Impact: Other

OPM-00534: Recovery: Proc %u:%u numprocs/maxprocs configuration exceeded -- stopping

Cause: The given process will be stopped because the configured number of processes for its process-set is now exceeded.

Action: *Define: OPMN_NLS_MSG_00150
Level:

Type:

Impact: Other

OPM-00535: Failed to create %s notification for %u

Cause: OPMN could not create a notification for the specified process event.

Action: *Define: OPMN_NLS_MSG_00151
Level:

Type:

Impact: Other

OPM-00536: Job %x %u result:%s

Cause: Log of an OPMN internal job result.

Action: *Define: OPMN_NLS_MSG_00152
Level:

Type:

Impact: Other

OPM-00537: Sched SyncExit: monitor timed out

Cause: Shutdown wait for monitor thread timed out.

Action: *Define: OPMN_NLS_MSG_00153
Level:

Type:

Impact: Other

OPM-00538: RMD %s conditional invalid floating point comparison

Cause: A conditional contains a comparison of a floating point value against a non numerical value.

Action: *Define: OPMN_RMD_COND_FLOAT_COMPARE
Level:

Type:

Impact: Other

OPM-00539: Pm/Ons confirm subscription failed: %sSubscription: %s

Cause: Creation of ONS subscription for ONS queue drain detection failed.

Action: *Define: OPMN_NLS_MSG_00155
Level:

Type:

Impact: Other

OPM-00540: Pm/Ons confirm notification create failed

Cause: Creation of ONS notification for ONS queue drain detection failed.

Action: *Define: OPMN_NLS_MSG_00156
Level:

Type:

Impact: Other

OPM-00541: Pm/Ons confirm notification timeout

Cause: Shutdown wait for ONS queue drain timed out.

Action: *Define: OPMN_NLS_MSG_00157
Level:

Type:

Impact: Other

OPM-00542: Request response socket send error: %s

Cause: ONS request response socket write failed.

Action: *Define: OPMN_NLS_MSG_00159
Level:

Type:

Impact: Other

OPM-00543: ONSpmInfoUtil: request %x timed out

Cause: The given remote request timed out.

Action: *Define: OPMN_NLS_MSG_00160
Level:

Type:

Impact: Other

OPM-00544: ONSpmInfoUtil: remote dependency instance name %s was not found

Cause: No OPMN server could be mapped to the given managed process dependency.

Action: The remote OPMN server may be down, or an invalid ias instance wass configured for the dependency in opmn.xml. *Define: OPMN_NLS_MSG_00161
Level:

Type:

Impact: Other

OPM-00545: RMD %s conditional invalid string operator

Cause: A conditional contains a string operand with a operator other than = or != .

Action: *Define: OPMN_RMD_COND_STRING_OPERATOR
Level:

Type:

Impact: Other

OPM-00546: RMD %s conditional invalid string comparison

Cause: A conditional contains a comparison of string value against another operand type.

Action: *Define: OPMN_RMD_COND_STRING_COMPARE
Level:

Type:

Impact: Other

OPM-00547: RMD %s exec failed (%s) for %s

Cause: The execution of an RMD action failed.

Action: *Define: OPMN_RMD_EXEC_FAILED
Level:

Type:

Impact: Other

OPM-00548: RMD %s exec error (%s) for %s

Cause: The execution of an RMD action encountered the given error.

Action: *Define: OPMN_RMD_EXEC_ERROR
Level:

Type:

Impact: Other

OPM-00549: RMD %s exec exited with non 0 status (%d) for %s

Cause: The execution of an RMD action exited with a non 0 code.

Action: *Define: OPMN_RMD_EXEC_STATUS
Level:

Type:

Impact: Other

OPM-00550:

Cause:

Action: *Define: OPMN_PM_UNUSED1
Level:

Type:

Impact: Other

OPM-00551:

Cause:

Action: *Define: OPMN_PM_UNUSED2
Level:

Type:

Impact: Other

OPM-00552: RMD %s could not create request thread for %s

Cause: A thread could not be created to execute the request.

Action: *Define: OPMN_RMD_REQ_THREAD
Level:

Type:

Impact: Other

OPM-00553: RMD %s request error code %d for %s

Cause: An action or exception request returned the given error code.

Action: *Define: OPMN_RMD_REQ_ERROR
Level:

Type:

Impact: Other

OPM-00554:

Cause:

Action: *Define: OPMN_PM_UNUSED3
Level:

Type:

Impact: Other

OPM-00555: Comp code contains invalid brace syntax

Cause: The comp parameter has invalid syntax for ons[] or pm[].

Action: *Define: OPMN_NLS_DEBUG_COMPOPEN
Level:

Type:

Impact: Other

OPM-00556: Debug \"all\" component code can not be negated

Cause: The "all" component code can not be negated.

Action: *Define: OPMN_NLS_DEBUG_NEGALL
Level:

Type:

Impact: Other

OPM-00557: invalid error code.

Cause: Internal request error code is set to an invalid value.

Action: *Define: OPMN_NLS_NONE
Level:

Type:

Impact: Other

OPM-00558: module specified no arguments for process creation

Cause: A module did not specify arguments for process creation.

Action: *Define: OPMN_NLS_NOSTARTARGS
Level:

Type:

Impact: Other

OPM-00559: working directory not set for an un-managed process

Cause: A module did not specify a working directory for process creation.

Action: *Define: OPMN_NLS_WORKDIR
Level:

Type:

Impact: Other

OPM-00560: can not use working directory

Cause: A module specified an invalid working directory for process creation.

Action: *Define: OPMN_NLS_BAD_WORKDIR
Level:

Type:

Impact: Other

OPM-00561: stdin descriptor can not be OpmnPathDefault

Cause: A module tried to specify the default io path as stdin for process creation.

Action: *Define: OPMN_NLS_STDIN
Level:

Type:

Impact: Other

OPM-00562: stdout descriptor can not be OpmnPathDefault for an un-managed process

Cause: A module tried to specify the default io path for an unmanaged process.

Action: *Define: OPMN_NLS_STDOUT
Level:

Type:

Impact: Other

OPM-00563: stderr descriptor can not be OpmnPathDefault for an un-managed process

Cause: A module tried to specify the default io path for an unmanaged process.

Action: *Define: OPMN_NLS_STDERR
Level:

Type:

Impact: Other

OPM-00564: file name is empty

Cause: A module specified a zero length file name for process creation.

Action: *Define: OPMN_NLS_FILENAME
Level:

Type:

Impact: Other

OPM-00565: time out while waiting for a process to exit

Cause: A time out occured while waiting for a child process to exit.

Action: *Define: OPMN_NLS_WAIT_TIMEOUT
Level:

Type:

Impact: Other

OPM-00566: no port available from the port range

Cause: No port was available from the configured port range.

Action: *Define: OPMN_NLS_PORT_NOT_FOUND
Level:

Type:

Impact: Other

OPM-00567: failed to set the process status to ProcStatusAlive

Cause: A module could not set a process status to Alive.

Action: *Define: OPMN_NLS_SET_ALIVE
Level:

Type:

Impact: Other

OPM-00568: failed to set the process status to ProcStatusBounce

Cause: A module could not set a process status to Bounce.

Action: *Define: OPMN_NLS_SET_BOUNCE
Level:

Type:

Impact: Other

OPM-00569: failed to set the process status to ProcStatusBounceFail

Cause: A module could not set a process status to Bounce Failed.

Action: *Define: OPMN_NLS_SET_BOUNCEFAIL
Level:

Type:

Impact: Other

OPM-00570: failed to set the process status to ProcStatusRestart

Cause: A module could not set a process status to Restart.

Action: *Define: OPMN_NLS_SET_RESTART
Level:

Type:

Impact: Other

OPM-00571: failed to set the process status to ProcStatusInitFail

Cause: A module could not set a process status to Init Failed.

Action: *Define: OPMN_NLS_SET_INITFAIL
Level:

Type:

Impact: Other

OPM-00572: Debug unknown ons component code

Cause: An unknown component code was specified within the ons[] field.

Action: *Define: OPMN_NLS_DEBUG_ONS_UNKNOWN
Level:

Type:

Impact: Other

OPM-00573: failed to schedule a start job for the managed process

Cause: A module could not schedule a start job for the managed process.

Action: *Define: OPMN_NLS_SCHED_START_JOB
Level:

Type:

Impact: Other

OPM-00574: failed to schedule a stop job for the managed process

Cause: A module could not schedule a stop job for the managed process.

Action: *Define: OPMN_NLS_SCHED_STOP_JOB
Level:

Type:

Impact: Other

OPM-00575: failed to schedule a restart job for the managed process

Cause: A module could not schedule a restart job for the managed process.

Action: *Define: OPMN_NLS_SCHED_RESTART_JOB
Level:

Type:

Impact: Other

OPM-00576: failed to start a managed process after the maximum retry limit

Cause: A managed process failed to start after the configured maximum number of retries was reached.

Action: *Define: OPMN_NLS_START_REACH_RETRY
Level:

Type:

Impact: Other

OPM-00577: time out while waiting for a managed process to start

Cause: A managed process failed to start within the configured time out period.

Action: *Define: OPMN_NLS_START_TIMEOUT
Level:

Type:

Impact: Other

OPM-00578: failed to restart a managed process after the maximum retry limit

Cause: A managed process failed to restart after the configured maximum number of retries was reached.

Action: *Define: OPMN_NLS_RESTART_REACH_RETRY
Level:

Type:

Impact: Other

OPM-00579: time out while waiting for a managed process to restart

Cause: A managed process failed to restart within the configured time out period.

Action: *Define: OPMN_NLS_RESTART_TIMEOUT
Level:

Type:

Impact: Other

OPM-00580: time out while waiting for a managed process to stop

Cause: A managed process failed to stop within the configured time out period.

Action: *Define: OPMN_NLS_STOP_TIMEOUT
Level:

Type:

Impact: Other

OPM-00581: unknown module parse error

Cause: A module specified an unknown error while parsing a request.

Action: *Define: OPMN_NLS_MOD_PARSE
Level:

Type:

Impact: Other

OPM-00582: no processes or applications matched this request

Cause: The request matched no managed processes or applications.

Action: *Define: OPMN_NLS_NO_MATCH_PROC
Level:

Type:

Impact: Other

OPM-00583: Unknown parameter for this request

Cause: The specified parameter for the request is not valid for the command.

Action: Check the request argument list for errors. *Define: OPMN_NLS_UNKNOWN_PARAMETER
Level:

Type:

Impact: Other

OPM-00584: not enabled

Cause: The specified feature is not enabled.

Action: *Define: OPMN_NLS_NOT_ENABLED
Level:

Type:

Impact: Other

OPM-00585: OPMN is terminating

Cause: The request was rejected because OPMN is terminating.

Action: *Define: OPMN_NLS_PM_TERMINATE
Level:

Type:

Impact: Other

OPM-00586: no enabled components for this request

Cause: A request was issued for an ias component, process type or process set that was not enabled.

Action: *Define: OPMN_NLS_NO_ENABLED_PROC
Level:

Type:

Impact: Other

OPM-00587: database dependency failed

Cause: A dependency check on a database failed.

Action: *Define: OPMN_NLS_DATABASE_DEPEND_FAILED
Level:

Type:

Impact: Other

OPM-00588: osso dependency failed

Cause: A dependency check on an OSSO server failed.

Action: *Define: OPMN_NLS_OSSO_DEPEND_FAILED
Level:

Type:

Impact: Other

OPM-00589: oid dependency failed

Cause: A dependency check on an OID server failed.

Action: *Define: OPMN_NLS_OID_DEPEND_FAILED
Level:

Type:

Impact: Other

OPM-00590: managed-process dependency failed

Cause: A dependency check on a managed process failed.

Action: *Define: OPMN_NLS_UNIT_DEPEND_FAILED
Level:

Type:

Impact: Other

OPM-00591: module dependency failed

Cause: A dependency check on a modulle failed.

Action: *Define: OPMN_NLS_MODULE_DEPEND_FAILED
Level:

Type:

Impact: Other

OPM-00592: dependency initiated stop

Cause: A stop of a managed process was initiated via a configured dependency with autostop.

Action: *Define: OPMN_NLS_DEPEND_STOP
Level:

Type:

Impact: Other

OPM-00593: dependency initiated restart

Cause: A restart of a managed process was initiated via a configured dependency with autorestart.

Action: *Define: OPMN_NLS_DEPEND_RESTART
Level:

Type:

Impact: Other

OPM-00594: Unknown remote ias instance.

Cause: A managed process dependency is configured with an ias instance not managed by this OPMN server nor any other OPMN server currently connected to this one.

Action: *Define: OPMN_NLS_DEPEND_UNKNOWN_REMOTE
Level:

Type:

Impact: Other

OPM-00595: Request command must begin with '/'.

Cause: The OPMN http request command must begin with a forward slash.

Action: *Define: OPMN_NLS_REQ_BEGINSYNTAX
Level:

Type:

Impact: Other

OPM-00596: Invalid ping syntax.

Cause: The OPMN ping request has invalid syntax.

Action: *Define: OPMN_NLS_REQ_PINGSYNTAX
Level:

Type:

Impact: Other

OPM-00597: Scope is invalid with ping request.

Cause: Request scope may not be configured with a ping request.

Action: *Define: OPMN_NLS_REQ_PINGSCOPE
Level:

Type:

Impact: Other

OPM-00598: Ping succeeded.

Cause: The ping request succeeded.

Action: *Define: OPMN_NLS_REQ_PINGSUCCESS
Level:

Type:

Impact: Other

OPM-00599: Command can only be: start, stop, restart, quiesc, ping, reload, shutdown, dump, set, query, module or debug.

Cause: Only the specified requests are supported by OPMN.

Action: *Define: OPMN_NLS_REQ_BADCOMMAND
Level:

Type:

Impact: Other

OPM-00600: Unknown command

Cause: The specified command is not supported bu OPMN.

Action: *Define: OPMN_NLS_REQ_UNKNOWNCOMMAND
Level:

Type:

Impact: Other

OPM-00601: Invalid parameter: %sParameters must be of the form 'key=value'

Cause: OPMN request parameters must be of the specified form.

Action: *Define: OPMN_NLS_REQ_INVALIDPARAM
Level:

Type:

Impact: Other

OPM-00602: Communication error with the OPMN server local port.Check the OPMN log files

Cause: The request client could not connect with the OPMN server, or lost connection with the OPMN server.

Action: Check that ORACLE_HOME is set correctly, or check the OPMN log files. *Define: OPMN_NLS_REQ_COMMERR
Level:

Type:

Impact: Other

OPM-00603: Format of parameters for this request is incorrect.

Cause: The format of the parameters for this request is incorrect.

Action: *Define: OPMN_NLS_REQ_PARAMFORMAT
Level:

Type:

Impact: Other

OPM-00604: No name for a parameter: syntax is name=value.

Cause: The parameter is missing the name field.

Action: *Define: OPMN_NLS_REQ_PARAMNONAME
Level:

Type:

Impact: Other

OPM-00605: Missing ']'.

Cause: The special name=[value] parameter syntax is missing the closing brace.

Action: *Define: OPMN_NLS_REQ_PARAMNOCLOSE
Level:

Type:

Impact: Other

OPM-00606: Bad format for name=[value] parameter.

Cause: The special name=[value] parameter syntax is invalid.

Action: *Define: OPMN_NLS_REQ_PARAMBADSQUARE
Level:

Type:

Impact: Other

OPM-00607: No value for a parameter: syntax is name=value.

Cause: The parameter is missing the value field.

Action: *Define: OPMN_NLS_REQ_PARAMNOVALUE
Level:

Type:

Impact: Other

OPM-00608: A duplicate dmsarg was specified.

Cause: Only one dmsarg option is allowed per request.

Action: *Define: OPMN_NLS_REQ_DUPDMSARG
Level:

Type:

Impact: Other

OPM-00609: Mode can only be: async or sync.

Cause: The request mode may only be async or sync.

Action: *Define: OPMN_NLS_REQ_BADMODE
Level:

Type:

Impact: Other

OPM-00610: Timeout must be >= 15.

Cause: The timeout value must be greater than or equal to 15.

Action: *Define: OPMN_NLS_REQ_BADTIMEOUT
Level:

Type:

Impact: Other

OPM-00611: Debug unknown pm component code

Cause: An unknown component code was specified within the pm[] field.

Action: *Define: OPMN_NLS_DEBUG_PM_UNKNOWN
Level:

Type:

Impact: Other

OPM-00612: Uniqueid must be > 0.

Cause: The uniqueid value must be greater than 0.

Action: *Define: OPMN_NLS_REQ_BADUID
Level:

Type:

Impact: Other

OPM-00613: Interval is only allowed for dump and debug.

Cause: The interval parameter is only allowed for dump and debug commands.

Action: *Define: OPMN_NLS_REQ_INTERVALUSAGE
Level:

Type:

Impact: Other

OPM-00614: Interval must be > 0.

Cause: The interval value must be greater than 0.

Action: *Define: OPMN_NLS_REQ_BADINTERVAL
Level:

Type:

Impact: Other

OPM-00615: Count is only allowed for dump and debug.

Cause: The count parameter is only allowed for dump and debug commands.

Action: *Define: OPMN_NLS_REQ_COUNTUSAGE
Level:

Type:

Impact: Other

OPM-00616: Count must be > 0.

Cause: The count value must be greater than 0.

Action: *Define: OPMN_NLS_REQ_BADCOUNT
Level:

Type:

Impact: Other

OPM-00617: Debug specific module negation with no modules selected.

Cause: A specific module or list of modules was negated without first selecting all modules.

Action: *Define: OPMN_NLS_DEBUG_PM_NEGMOD
Level:

Type:

Impact: Other

OPM-00618: Numprocs must be > 0.

Cause: The numprocs value must be greater than 0.

Action: *Define: OPMN_NLS_REQ_BADNUMPROCS
Level:

Type:

Impact: Other

OPM-00619: Unknown component code.

Cause: The comp parameter contains an unknown component code.

Action: *Define: OPMN_NLS_DEBUG_COMP
Level:

Type:

Impact: Other

OPM-00620: A uniqueid may not be specified with process scope parameters.

Cause: The uniqueid parameter may not be specified with other process scope parameters (such as process-set, for example).

Action: *Define: OPMN_NLS_REQ_UIDSCOPE
Level:

Type:

Impact: Other

OPM-00621: Both interval and count must be set or neither.

Cause: Both the interval and count parameters must be used together.

Action: *Define: OPMN_NLS_REQ_INTERVALCOUNT
Level:

Type:

Impact: Other

OPM-00622: A process set must be explicitly specified with numprocs.

Cause: For the numprocs parameter a process-set configured with min/max procs must be specified as part of the request.

Action: *Define: OPMN_NLS_REQ_FULLNUMPROCS
Level:

Type:

Impact: Other

OPM-00623: Unknown parameters for this request.

Cause: Unknown parameters were specified for this request.

Action: *Define: OPMN_NLS_REQ_PARAMUNKNOWN
Level:

Type:

Impact: Other

OPM-00624: Invalid request state.

Cause: The request state is invalid because the specified target can no longer be acted upon.

Action: *Define: OPMN_NLS_REQ_INVALIDSTATE
Level:

Type:

Impact: Other

OPM-00625: No process matched the given uniqueid.

Cause: The uniqueid value did not match a managed process.

Action: *Define: OPMN_NLS_REQ_UIDNOMATCH
Level:

Type:

Impact: Other

OPM-00626: No processes or applications match the specified configuration.

Cause: No managed processes or applications matched the request parameters.

Action: *Define: OPMN_NLS_REQ_NOPROC
Level:

Type:

Impact: Other

OPM-00627: Unknown server error

Cause: The server encountered an error while processing the request.

Action: *Define: OPMN_NLS_REQ_SERVERERRORUNKNOWN
Level:

Type:

Impact: Other

OPM-00628: Request timed-out

Cause: The request timed out in the server.

Action: *Define: OPMN_NLS_REQ_RESPTIMEOUT
Level:

Type:

Impact: Other

OPM-00629: Bad request

Cause: The request is bad.

Action: Check the request syntax, scope, command and parameters. *Define: OPMN_NLS_REQ_RESPBADREQ
Level:

Type:

Impact: Other

OPM-00630: Unacceptable request

Cause: The request can not be processed on the server.

Action: Either no processes or applications matched the request on the server, or the remote request was rejected for security reasons. *Define: OPMN_NLS_REQ_RESPUNACCREQ
Level:

Type:

Impact: Other

OPM-00631: Request partial success

Cause: Some of the managed processes responded successfully to the request.

Action: *Define: OPMN_NLS_REQ_RESPPARTSUCCESS
Level:

Type:

Impact: Other

OPM-00632: Request failure

Cause: None of the managed processes responded successfully to the request.

Action: *Define: OPMN_NLS_REQ_RESPFAILURE
Level:

Type:

Impact: Other

OPM-00633: Server error

Cause: An internal server error was encountered while processing the request.

Action: *Define: OPMN_NLS_REQ_RESPSERVERERROR
Level:

Type:

Impact: Other

OPM-00634: Mangled server response

Cause: The server request response is in an unknown format.

Action: *Define: OPMN_NLS_REQ_RESPMANGLEDSERVER
Level:

Type:

Impact: Other

OPM-00635: Debug specific module with all modules already selected.

Cause: A specific module or list of modules was selected after all modules were selected.

Action: *Define: OPMN_NLS_DEBUG_PM_DUPMOD
Level:

Type:

Impact: Other

OPM-00636: DMS is not enabled in OPMN.

Cause: DMS metrics are not enabled in this OPMN server.

Action: *Define: OPMN_NLS_DMS_DISABLED
Level:

Type:

Impact: Other

OPM-00637: : specified scope instance name not found.

Cause: The given instance name specified in the scope of the request was not found.

Action: *Define: OPMN_NLS_REQ_SCOPEINSTANCENOTFOUND
Level:

Type:

Impact: Other

OPM-00638: The specified option is not valid with this request type

Cause: A module specific option was given which is not supported by the request.

Action: *Define: OPMN_NLS_REQ_INVALIDACTION
Level:

Type:

Impact: Other

OPM-00639: Invalid scope instance list syntax.

Cause: The syntax of the instance list option for request scope is instance:<instance name>:<instance name>...

Action: *Define: OPMN_NLS_REQ_SCOPEINSTANCEBADFORMAT
Level:

Type:

Impact: Other

OPM-00640: Invalid combination of component target options

Cause: A module specific option was given that was mutually exclusive with the given process target options (ias-component, process-type, process-set, etc.).

Action: *Define: OPMN_NLS_REQ_INVALIDTARGETS
Level:

Type:

Impact: Other

OPM-00641: Scope must be instance, cluster or *.

Cause: The request scope must specify one of the given identifiers.

Action: *Define: OPMN_NLS_REQ_SCOPEINVALID
Level:

Type:

Impact: Other

OPM-00642: Remote request with weak authentication.

Cause: The request was run remotely, but the wallet file is not secure: it is either an example wallet file or does not have a password.

Action: Replace the wallet-file specification in opmn.xml with the path to a real, secure wallet file. *Define: OPMN_NLS_REQ_AUTH_WEAK
Level:

Type:

Impact: Other

OPM-00643: Oracle SSL/authentication libraries were not found

Cause: The Oracle core SSL/authentication libraries were not found.

Action: Make sure the core Oracle libraries have been installed. *Define: OPMN_NLS_SSL_NOLIBS
Level:

Type:

Impact: Other

OPM-00644: The connection SSL initialization failed

Cause: The connection SSL initialization failed.

Action: *Define: OPMN_NLS_SSL_INITFAILED
Level:

Type:

Impact: Other

OPM-00645: The connection authentication failed

Cause: The connection authentication failed.

Action: Check the configured wallet file path and password. *Define: OPMN_NLS_SSL_WALLETFAILED
Level:

Type:

Impact: Other

OPM-00646: The connection SSL/authentication handshake failed

Cause: The connection SSL/authentication handshake failed.

Action: *Define: OPMN_NLS_SSL_CONNECTFAILED
Level:

Type:

Impact: Other

OPM-00647: Remote request refused because authentication is not configured:%s

Cause: OPMN has not been configured to use athentication when connecting to other OPMN servers, and so remote requests for stop, restart, stop and shutdown are not allowed.

Action: *Define: OPMN_NLS_REQ_REFUSED
Level:

Type:

Impact: Other

OPM-00648: The connection send failed

Cause: The connection send failed.

Action: *Define: OPMN_NLS_SSL_SNDFAILED
Level:

Type:

Impact: Other

OPM-00649: The connection receive failed

Cause: The connection receive failed.

Action: *Define: OPMN_NLS_SSL_RCVFAILED
Level:

Type:

Impact: Other

OPM-00650: The connection send timed out

Cause: The connection send timed out.

Action: *Define: OPMN_NLS_SSL_SNDTIMEDOUT
Level:

Type:

Impact: Other

OPM-00651: The connection receive timed out

Cause: The connection receive timed out.

Action: *Define: OPMN_NLS_SSL_RCVTIMEDOUT
Level:

Type:

Impact: Other

OPM-00652: An IO request on a pipe timed out

Cause: An IO request on a pipe timed out.

Action: *Define: OPMN_NLS_PIPE_IOTIMEOUT
Level:

Type:

Impact: Other

OPM-00653: The event script is not executable

Cause: The event script does not have execute permission.

Action: *Define: OPMN_NLS_SCRIPT_NOEXEC
Level:

Type:

Impact: Other

OPM-00654: The event script timed out

Cause: The event script timed out.

Action: *Define: OPMN_NLS_SCRIPT_TIMEDOUT
Level:

Type:

Impact: Other

OPM-00655: failed to start a managed process because a dependency check failed

Cause: A managed process was not started because a dependency check failed.

Action: *Define: OPMN_NLS_START_DEPEND_FAIL
Level:

Type:

Impact: Other

OPM-00656: failed to start a managed process because the event-script failed

Cause: A managed process was not started because the event-script failed.

Action: *Define: OPMN_NLS_START_SCRIPT_FAIL
Level:

Type:

Impact: Other

OPM-00657: failed to restart a managed process because a dependency check failed

Cause: A managed process was not restarted because a dependency check failed.

Action: *Define: OPMN_NLS_RESTART_DEPEND_FAIL
Level:

Type:

Impact: Other

OPM-00658: failed to restart a managed process because an event-script failed

Cause: A managed process was not restarted because an event-script failed.

Action: *Define: OPMN_NLS_RESTART_SCRIPT_FAIL
Level:

Type:

Impact: Other

OPM-00659: failed to stop a managed process because the event-script failed

Cause: A managed process was not stopped because the event-script failed.

Action: *Define: OPMN_NLS_STOP_SCRIPT_FAIL
Level:

Type:

Impact: Other

OPM-00660: Process Crashed: %s~%s~%s~%u (%u:%u) - Restarting

Cause: Process no longer visible from the OS, will be restarted

Action: Examine console log associated with the process and examine logs maintained by the component. *Define: OPMN_NLS_MSG_00258
Level:

Type:

Impact: Other

OPM-00661: Process Crashed: %s~%s~%s~%u (%u:%u) - Not restarting

Cause: Process no longer visible from the OS, will not be restarted

Action: Examine console log associated with the process and examine logs maintained by the component. An explicit start request must be made to start the process. *Define: OPMN_NLS_MSG_00259
Level:

Type:

Impact: Other

OPM-00662: Starting Process: %s~%s~%s~%u (%u:0)

Cause: About to start a managed process

Action: No action. Informational use only. *Define: OPMN_NLS_MSG_00260
Level:

Type:

Impact: Other

OPM-00663: Stopping Process: %s~%s~%s~%u (%u:%u)

Cause: About to stop a managed process

Action: No action. Informational use only. *Define: OPMN_NLS_MSG_00261
Level:

Type:

Impact: Other

OPM-00664: Restarting Process: %s~%s~%s~%u (%u:%u)

Cause: About to restart a managed process

Action: No action. Informational use only. *Define: OPMN_NLS_MSG_00262
Level:

Type:

Impact: Other

OPM-00665: Process Alive: %s~%s~%s~%u (%u:%u)

Cause: Process started and initialization completed

Action: No action. Informational use only. *Define: OPMN_NLS_MSG_00263
Level:

Type:

Impact: Other

OPM-00666: Process Stopped: %s~%s~%s~%u (%u:%u)

Cause: Process stop operation completed.

Action: No action. Informational use only. *Define: OPMN_NLS_MSG_00264
Level:

Type:

Impact: Other

OPM-00667: Request %x Started. Command: %s

Cause: User request about to be handled by opmn.

Action: No action. Informational use only. *Define: OPMN_NLS_MSG_00265
Level:

Type:

Impact: Other

OPM-00668: Request %x Completed. Command: %s

Cause: Opmn finished handling user request, about to return response.

Action: No action. Informational use only. *Define: OPMN_NLS_MSG_00266
Level:

Type:

Impact: Other

OPM-00669: Invalid specified process configuration

Cause: You must specify either a list of OPMN configuration elements (all ias-components, all process-types or all process-sets) or a single configuration tree (one ias-component, process-type or process-set)

Action: Change the request to conform to the OPMN supported convention. *Define: OPMN_NLS_REQ_BAD_CONFIG
Level:

Type:

Impact: Other

OPM-00670: failed to get an IP for the hostname

Cause: The operating system could not find an IP address for the hostname.

Action: *Define: OPMN_NLS_GETIP_FAILED
Level:

Type:

Impact: Other

OPM-00671: Module %s initialization failed: disabled

Cause: The specified module has been disabled because module initialization failed.

Action: *Define: OPMN_NLS_MODULE_FAILED
Level:

Type:

Impact: Other

OPM-00672: Process skipped because module is disabled: %s~%s~%s~%u (%u:%u)

Cause: The specified process will not be monitored by OPMN because the module initialization failed.

Action: *Define: OPMN_NLS_PROC_SKIPPED
Level:

Type:

Impact: Other

OPM-00673: Process crashed during soft restart: %s~%s~%s~%u (%u:%u)

Cause: The process unexpectedly crashed during a soft restart request.

Action: Examine console log associated with the process and examine logs maintained by the component. *Define: OPMN_NLS_BOUNCE_FAIL
Level:

Type:

Impact: Other

OPM-00674: process crashed during restart

Cause: The process unexpectedly crashed during a soft restart request.

Action: Examine console log associated with the process and examine logs maintained by the component. *Define: OPMN_NLS_RESTART_DEATH
Level:

Type:

Impact: Other

OPM-00675: OPMN server ready. Request handling enabled.

Cause: Opmn server has been completely started. Requests sent to the opmn server prior to this point in time will not be handled.

Action: No action. Informational only. *Define: OPMN_NLS_MSG_OPMN_SERVER_STARTED
Level:

Type:

Impact: Other

OPM-00676: OPMN server stopped. Request handling disabled.

Cause: The opmn server received a request to either shutdown or reload. At this point in time the opmn server will abort all current requests and no new requests will be accepted.

Action: No action. Informational only. *Define: OPMN_NLS_MSG_OPMN_SERVER_STOPPED
Level:

Type:

Impact: Other

OPM-00677: Process Ping Failed: %s

Cause: A ping attempt could not be initiated or timed out. Where possible, the opmn server periodically makes an attempt to ping a process it is managing to determine if the process is reachable by a client. A ping attempt can fail during the connection attempt or if the connection is successful but the process does not respond within a configured number of seconds.

Action: If ping attempts are timing out it may be necessary to increase the ping timeout configured for the process in opmn.xml. *Define: OPMN_NLS_PROC_PING_FAIL
Level:

Type:

Impact: Other

OPM-00678: Process Unreachable: %s

Cause: Reached the maximum configured consecutive ping failures. Process declared unreachable. Process will be restarted.

Action: If this occurs frequently, determine if there is something wrong with this type of process by examining the logs associated with the component. If may be necessary to increase the ping timeout configured for the process in opmn.xml. *Define: OPMN_NLS_PROC_HUNG
Level:

Type:

Impact: Other

OPM-00679: Forcefully Terminating Process: %s

Cause: Process did not respond to stop request or request timed out.

Action: An initial attempt is made by the opmn server to stop a process by a graceful means. If the process does not respond within the configured time then the process will be stopped forcefully. It may be necessary to increase the configured stop timeout for the process to give it sufficient time to stop gracefully. *Define: OPMN_NLS_PROC_FORCEFUL_TERMINATE
Level:

Type:

Impact: Other

OPM-00680: Process Start Error: %s

Cause: An error occurred while attempting to start a process.

Action: May be caused by bad configuration or insufficient availability of system resources. *Define: OPMN_NLS_PROC_START_ERROR
Level:

Type:

Impact: Other

OPM-00681: Process Restart Error: %s

Cause: An error occurred while attempting to restart a process.

Action: May be caused by bad configuration or insufficient availability of system resources. *Define: OPMN_NLS_PROC_RESTART_ERROR
Level:

Type:

Impact: Other

OPM-00682: Process Stop Error: %s

Cause: An error occurred while attempting to stop a process.

Action: May be caused by bad configuration or insufficient availability of system resources. *Define: OPMN_NLS_PROC_STOP_ERROR
Level:

Type:

Impact: Other

OPM-00683: Process Reverse Ping Error: %s

Cause: An error occurred while consuming a reverse ping message sent from a process.

Action: May be caused by wrong or missing information in the contents of the reverse ping message. *Define: OPMN_NLS_PROC_REVPING_ERROR
Level:

Type:

Impact: Other

OPM-00684: Service fail over start failure

Cause: An error occurred while starting a service fail over

Action: *Define: OPMN_NLS_SERVICE_START_FAIL
Level:

Type:

Impact: Other

OPM-00685: Service fail over start timeout

Cause: A time out occurred while starting a service fail over

Action: *Define: OPMN_NLS_SERVICE_START_TIMEOUT
Level:

Type:

Impact: Other

OPM-00686: Service fail over stop failure

Cause: An error occurred while stopping a service fail over

Action: *Define: OPMN_NLS_SERVICE_STOP_FAIL
Level:

Type:

Impact: Other

OPM-00687: Service fail over stop timeout

Cause: A time out occurred while stopping a service fail over

Action: *Define: OPMN_NLS_SERVICE_STOP_TIMEOUT
Level:

Type:

Impact: Other

OPM-00688: Service fail over restart failure

Cause: An error occurred while restarting a service fail over

Action: *Define: OPMN_NLS_SERVICE_RESTART_FAIL
Level:

Type:

Impact: Other

OPM-00689: Service fail over restart timeout

Cause: A time out occurred while restarting a service fail over

Action: *Define: OPMN_NLS_SERVICE_RESTART_TIMEOUT
Level:

Type:

Impact: Other

OPM-00690: Could not create service manager thread

Cause: OPMN could not create the service failover manager thread

Action: *Define: OPMN_NLS_SERVICE_THREAD_CREATE
Level:

Type:

Impact: Other

OPM-00691: Service: bad participant id data: %s

Cause: The service failover manager encountered bad participant data.

Action: *Define: OPMN_NLS_SERVICE_BAD_PART_DATA
Level:

Type:

Impact: Other

OPM-00692: Service: could not start service process (%s)

Cause: The service failover process could not be started.

Action: *Define: OPMN_NLS_SERVICE_STARTPROC_FAIL
Level:

Type:

Impact: Other

OPM-00693: Service: could not stop service process (%s)

Cause: The service failover process could not be stopped.

Action: *Define: OPMN_NLS_SERVICE_STOPPROC_FAIL
Level:

Type:

Impact: Other

OPM-00694: Service: could not restart service process (%s)

Cause: The service failover process could not be restarted.

Action: *Define: OPMN_NLS_SERVICE_RESTARTPROC_FAIL
Level:

Type:

Impact: Other

OPM-00695: Debug specific module negation can not be used with specific module selection.

Cause: Specific modules may be listed for exclusion or inclusion but not both.

Action: *Define: OPMN_NLS_DEBUG_PM_CLASHMOD
Level:

Type:

Impact: Other

OPM-00696: Comp code argument contains invalid parentheses syntax

Cause: The comp argument has invalid syntax for modules().

Action: *Define: OPMN_NLS_DEBUG_ARGOPEN
Level:

Type:

Impact: Other

OPM-00697: Specific module id does not exist.

Cause: The comp argument specifies a specific module id that does not exist.

Action: *Define: OPMN_NLS_DEBUG_PM_NOMOD
Level:

Type:

Impact: Other

OPM-00698: A process-set specified in the request does not support min/max procs.

Cause: If numprocs is specified in the request, then only process-sets that are configured with min/max procs must be specified.

Action: *Define: OPMN_NLS_REQ_NOMINMAX
Level:

Type:

Impact: Other

OPM-00699: The request for the specified application is not supported by the process-module.

Cause: A request was issued for an application which the process-module for the owning process does not support.

Action: *Define: OPMN_NLS_REQ_APP_NOSUPPORT
Level:

Type:

Impact: Other

OPM-00700: The application must be specified for this request.

Cause: An application or list of applications must be specified with this request.

Action: *Define: OPMN_NLS_REQ_APP_ONLY
Level:

Type:

Impact: Other

OPM-00701: An application for this request was removed.

Cause: An application taking part in this request was removed from the process.

Action: *Define: OPMN_NLS_APP_REMOVE
Level:

Type:

Impact: Other

OPM-00702: The application process has terminated.

Cause: The process for an application taking part in this request has terminated.

Action: *Define: OPMN_NLS_APP_PROC_DEAD
Level:

Type:

Impact: Other

OPM-00703: The request failed for this application.

Cause: The request failed for this application.

Action: *Define: OPMN_NLS_APP_REQ_FAIL
Level:

Type:

Impact: Other

OPM-00704: The request timed-out for this application.

Cause: The request timed-out for this application.

Action: *Define: OPMN_NLS_APP_REQ_TIMEOUT
Level:

Type:

Impact: Other

OPM-00705: Duplicate target for set or query request.

Cause: The set or query request specifies more than one target.

Action: *Define: OPMN_NLS_SET_DUP_TARGET
Level:

Type:

Impact: Other

OPM-00706: Duplicate comp for set or query request.

Cause: The set or query request specifies more than one comp.

Action: *Define: OPMN_NLS_SET_DUP_COMP
Level:

Type:

Impact: Other

OPM-00707: No target for set or query request.

Cause: The set or query request does not specify a target.

Action: *Define: OPMN_NLS_SET_NO_TARGET
Level:

Type:

Impact: Other

OPM-00708: No comp for set request.

Cause: The set request does not specify a comp.

Action: *Define: OPMN_NLS_SET_NO_COMP
Level:

Type:

Impact: Other

OPM-00709: Invalid target for set or query request.

Cause: The set or query request specifies an invalid target.

Action: *Define: OPMN_NLS_SET_INVALID_TARGET
Level:

Type:

Impact: Other

OPM-00710: Comp code contains extra characters after the closing brace.

Cause: The component code has extra characters after the closing brace.

Action: *Define: OPMN_NLS_DEBUG_COMPCLOSE
Level:

Type:

Impact: Other

OPM-00711: Only one module may be specified for this request.

Cause: Multiple modules were specified for this request, which only allows one.

Action: *Define: OPMN_NLS_MODULE_MULTI
Level:

Type:

Impact: Other

OPM-00712: The specified module is not configured.

Cause: The specified module is not configured.

Action: *Define: OPMN_NLS_MODULE_UNKNOWN
Level:

Type:

Impact: Other

OPM-00713: The specified module does not support this request.

Cause: The specified module does not support this request.

Action: *Define: OPMN_NLS_MODULE_NOSUPPORT
Level:

Type:

Impact: Other

OPM-00714: No module was specified.

Cause: This request requires that a module be specified.

Action: *Define: OPMN_NLS_MODULE_NOMODULE
Level:

Type:

Impact: Other

OPM-00715: The specified module is disabled.

Cause: The specified module is disabled.

Action: *Define: OPMN_NLS_MODULE_DISABLED
Level:

Type:

Impact: Other

OPM-00716: No components matched this request.

Cause: No components matched the options specified for this request.

Action: *Define: OPMN_NLS_REQ_NOCOMPONENT
Level:

Type:

Impact: Other

OPM-00717: No addresses for the request.

Cause: There were no registered addresses for the request.

Action: *Define: OPMN_NLS_REQ_ADDRSNONE
Level:

Type:

Impact: Other

OPM-00718: No addresses matched the properties for the request.

Cause: No registered addresses matched the properties specified in the request.

Action: *Define: OPMN_NLS_REQ_ADDRSNOMATCH
Level:

Type:

Impact: Other

OPM-00719: Failed to initialize DMS publisher.

Cause: The server code not initialize the DMS publisher: OPMN metrics will not be available via the metric request.

Action: *Define: OPMN_NLS_DMS_PUBLISHER_FAIL
Level:

Type:

Impact: Other

OPM-00720: Failed to create RPC client.

Cause: The server code not create the ONS RPC client.

Action: *Define: OPMN_NLS_RPC_CLIENT_FAIL
Level:

Type:

Impact: Other

OPM-00721: Invalid operation for metric.

Cause: The op argument for the metric request must be set to query or list.

Action: *Define: OPMN_NLS_REQ_METRICOP
Level:

Type:

Impact: Other

OPM-00722: Scope is invalid with launch request.

Cause: Request scope may not be configured with a launch request.

Action: *Define: OPMN_NLS_REQ_LAUNCHSCOPE
Level:

Type:

Impact: Other

OPM-00723: No target specified for launch request.

Cause: A configured target must be specified with the launch request.

Action: *Define: OPMN_NLS_REQ_LAUNCHNOTARGET
Level:

Type:

Impact: Other

OPM-00724: Invalid target specified for launch request.

Cause: The target specified with the launch request is not configured.

Action: *Define: OPMN_NLS_REQ_LAUNCHINVALIDTARGET
Level:

Type:

Impact: Other

OPM-00725: Launch target at maximum concurrency.

Cause: The target specified with the launch request is at the configured maximum concurrency.

Action: *Define: OPMN_NLS_REQ_LAUNCHMAXCONCURR
Level:

Type:

Impact: Other

OPM-00726: Launch target process start error: %s %d %s (%s)

Cause: The process for the launch target failed to start.

Action: *Define: OPMN_NLS_REQ_LAUNCHPROCERROR
Level:

Type:

Impact: Other

OPM-00727: Launch target process pipe read error: %s %d (%s).

Cause: The server failed on a read from the launch target process pipe.

Action: *Define: OPMN_NLS_REQ_LAUNCHPROCPIPE
Level:

Type:

Impact: Other

OPM-00728: Launch target process hung: %s %d pid %u.

Cause: The process for the launch target failed to start. The process will be killed.

Action: *Define: OPMN_NLS_REQ_LAUNCHPROCHUNG
Level:

Type:

Impact: Other

OPM-00729: Launch target process sginal error: %s %d pid %u (%s).

Cause: The server could not send the hung launch target process a signal.

Action: *Define: OPMN_NLS_REQ_LAUNCHPROCSIG
Level:

Type:

Impact: Other

OPM-00730: Launch target request client send error: %s %d.

Cause: The server could not send the launch target process output to the request client.

Action: *Define: OPMN_NLS_REQ_LAUNCHSENDERROR
Level:

Type:

Impact: Other

OPM-00731: Scope is invalid with phantom request.

Cause: Request scope may not be configured with a phantom request.

Action: *Define: OPMN_NLS_REQ_PHANTOMSCOPE
Level:

Type:

Impact: Other

OPM-00732: Invalid pid specified with phantom request.

Cause: The pid must be an integer of value > 1.

Action: *Define: OPMN_NLS_REQ_PHANTOMINVALIDPID
Level:

Type:

Impact: Other

OPM-00733: Disabled ias-component for the phantom request.

Cause: The ias-component specified with the phantom request does not have a configuration status of enabled or phantom.

Action: *Define: OPMN_NLS_REQ_PHANTOMDISCOMP
Level:

Type:

Impact: Other

OPM-00734: Disabled process-type for the phantom request.

Cause: The process-type specified with the phantom request does not have a configuration status of enabled or phantom.

Action: *Define: OPMN_NLS_REQ_PHANTOMDISPTYPE
Level:

Type:

Impact: Other

OPM-00735: Disabled process-set for the phantom request.

Cause: The process-set specified with the phantom request does not have a configuration status of enabled or phantom.

Action: *Define: OPMN_NLS_REQ_PHANTOMDISPSET
Level:

Type:

Impact: Other

OPM-00736: No process-set for the phantom request.

Cause: No configured phantom process-set matched the phantom request.

Action: *Define: OPMN_NLS_REQ_PHANTOMNOPSET
Level:

Type:

Impact: Other

OPM-00737: Ambiguous process-set for the phantom request.

Cause: Multiple phantom process-sets matched the phantom request, but the request requires only one matching process-set.

Action: *Define: OPMN_NLS_REQ_PHANTOMAMBIGPSET
Level:

Type:

Impact: Other

OPM-00738: Invalid executable file path.

Cause: The path to the executable file is invalid: the path either does not exist or has incorrect permissions.

Action: Validate the path configured in opmn.xml for the specified failure and ensure it is correct, and permissions for the path are correct for the OPMN user to execute it. *Define: OPMN_NLS_EXECUTE_INVALID
Level:

Type:

Impact: Other

OPM-00739: Executable file does not have execute permission.

Cause: The executable file does not have system execute permissions for the OPMN user.

Action: Ensure the executable file has execute permissions set for the OPMN user. *Define: OPMN_NLS_EXECUTE_PERM
Level:

Type:

Impact: Other

OPM-00740: Missing operation for metric.

Cause: The op argument for the metric request must be specified and set to query or list.

Action: *Define: OPMN_NLS_REQ_NOMETRICOP
Level:

Type:

Impact: Other

OPM-00741: More than one address matched the properties for the request.

Cause: The properties specified in the request matched more than one registered address.

Action: *Define: OPMN_NLS_REQ_ADDRSNOTUNIQUE
Level:

Type:

Impact: Other

OPM-00742: Process is still alive -- check configuration.

Cause: An error occurred while attempting to access a process, but the process is still alive.

Action: Usually caused by bad component configuration. Check component log files. *Define: OPMN_NLS_PROC_ALIVE
Level:

Type:

Impact: Other

OPM-00743: Process terminated.

Cause: An error occurred while accessing a process, and the process terminated.

Action: May be caused by bad configuration or insufficient availability of system resources. Check component log files. *Define: OPMN_NLS_PROC_DEAD
Level:

Type:

Impact: Other

OPM-00744: Invalid process state.

Cause: An error occurred while accessing a process leaving the process in an invalid state.

Action: May be caused by bad configuration or insufficient availability of system resources. Check component log files. *Define: OPMN_NLS_PROC_INVALID_STATE
Level:

Type:

Impact: Other

OPM-00745: Process restart failed.

Cause: An error occurred while attempting to restart a process.

Action: May be caused by bad configuration or insufficient availability of system resources. Check component log files. *Define: OPMN_NLS_PROC_RESTART_FAIL
Level:

Type:

Impact: Other

73 ORABPEL-00006 to ORABPEL-20511

ORABPEL-00006: failure to load the JCE cipher "{0}"

Cause: The environment may not have been set correctly.

Action: JCE library files must be installed in the JRE installation as an extension. Copy the jar files from "{1}\install\java\jce1.2.2" directory to "(jdk_path)\jre\lib\ext" directory (where jdk_path is JDK installation directory).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00007: failure to decrypt cipher text with transformation "{0}"; exception reported is: {1}

Cause: This was an internal error. It may have been caused by an incorrect cipher state or an invalid padding size being specified.

Action: Contact Oracle Support Services. Provide the error message and the process that appeared to cause the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00008: failure to encrypt plain text with transformation "{0}"; exception reported is: {1}

Cause: This was an internal error. It may have been caused by an incorrect cipher state or an invalid padding size being specified.

Action: Contact Oracle Support Services. Provide the error message and the process that appeared to cause the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00015: failure to create jar file {0}

Cause: The Sun tools.jar may not have been installed on the local machine or included in the class path.

Action: Verify that tools.jar is installed on this machine and is included in the class path.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00016: failure to execute javac compiler on file(s) "{0}"; exception reported is: {1}

Cause: The Sun tools.jar may not have been installed on the local machine or included in the class path.

Action: Verify that tools.jar is installed on this machine and is included in the class path.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00017: failure to compile file(s) "{0}"; exception reported is: {1}

Cause: The generated Java class(es) had errors and/or all the required libraries to compile the class(es) were not available.

Action: Verify that the file named in the error message is valid Java file and that all required libraries are included in the class path.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00018: cannot find the Java source directory "{0}"

Cause: The specified Java source directory did not exist or it could not be written to.

Action: Create the source directory named in the error message and set the write permission accordingly.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00019: cannot create the Java destination directory "{0}"

Cause: The parent directory permissions prevented the creation of this directory.

Action: Verify that the parent directory for the directory named in the error message is writable.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00020: failure to write the Javadoc argument file "{0}"; exception reported is: "{2}"

Cause: The Javadoc file named in the error message was not written to the directory "{1}".

Action: Verify that the directory "{1}" can be written to.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00021: failure to execute Javadoc with the argument file "{0}"

Cause: The Javadoc executable was not found in the system path or was not executed.

Action: Verify that Javadoc is installed on this machine in the <JDK>\bin directory and that this directory is included in the machine system path.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00024: failure to schedule the "{0}" agent with the scheduler; exception reported is: {1}

Cause: The Quartz scheduler did not schedule the job named in the error message. This is typically an internal scheduler error.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00025: failure to unschedule the "{0}" agent with the scheduler; exception reported is: {1}

Cause: The Quartz scheduler did not unschedule the job named in the error message. This is typically an internal scheduler error.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00026: error while attempting to execute the job "{0}" for agent "{1}"; exception reported is: {2}

Cause: This error was a wrapper for an internal exception thrown by the underlying scheduler job.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00201: cannot return system authentication token for caller "{0}"

Cause: This was an internal error. The agent "{0}" was not added to the allowed callers list for the system token.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00209: The domain identifier "{0}" is not registered with the server.

Cause: All domain identifiers were kept in the domain table; this table may have been modified incorrectly.

Action: Restart the application server; if the domain directory is present, the identifier will be automatically registered again.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00210: domain ref "{0}" is not registered with the server.

Cause: All domain identifiers were kept in the domain table; this table may have been modified incorrectly.

Action: Restart the application server; if the domain directory is present, the identifier will be automatically registered again.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00214: The OraBPEL server has not finished initializing yet; the initialization process may be complete in a few moments.

Cause: A request was sent to the server before it finished initializing.

Action: Resubmit the request. If this does not solve the problem, check the logs (with logging level set to debug mode) for error messages.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00215: error while attempting to instantiate the JDK adapter class "{0}" for run-time version "{1}"; exception reported is: {2}

Cause: The JDK adapter class named in the error message was not in the system class path or there was an incompatibility with the JDK used to the compile the class and the current JVM version.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00216: JDK adapter class "{0}" for run-time version "{1}" does not implement the IJDKAdapter interface

Cause: This was an internal error. All JDK adapters registered with the system must conform to the IJDKAdapter interface.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00217: JDK version "{0}" is not supported by the OraBPEL run-time; currently only JDK versions 1.4 and 1.5 are supported

Cause: A JDK adapter was not specified for the JVM version with which the container was started.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00219: cannot instantiate an instance for the class "{0}"

Cause: The class "{1}" was not granted sufficient permissions by the JVM to instantiate the class "{0}".

Action: Verify that the OraBPEL run-time class "{1}" has the necessary security permissions to access the class specified in the error message.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00220: class "{0}" (for the platform adapter for platform "{1}") does not implement the IPlatformAdaptor interface

Cause: This was an internal error. All platform adapters registered with the system must conform to the IPlatformAdaptor interface.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00221: error while attempting to instantiate the class "{0}" as the adapter for platform "{1}"; exception reported is: {2}

Cause: The platform adapter class "{0}" was not in the system class path, or there was an incompatibility with the JDK used to compile the class and the current JVM version.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00222: class for platform adapter "{0}" (platform "{1}") cannot be found

Cause: The platform adapter class "{0}" was not in the system class path.

Action: Ensure that Oracle BPEL libraries are set correctly in the system class path.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00227: class "{0}" (for the database adapter for "{1}") does not implement the IDatabaseAdaptor interface

Cause: This was an internal error. All database adapters registered with the system must conform to the IDatabaseAdaptor interface.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00228: error while attempting to instantiate the class "{0}" as the database adapter, data source "{1}"; exception reported is: {3}

Cause: The database adapter class "{0}" was not in the system class path, or there was an incompatibility with the JDK used to compile the class and the current JVM version.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00229: database adapter class name for data source "{0}" has not been specified

Cause: The database adapter class "{0}" was not in the system class path.

Action: Ensure that the Oracle BPEL libraries are set correctly in the system class path. If the libraries are configured correctly, the adapter configuration files may have been modified incorrectly.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00230: adapter resource file "{0}" cannot be found in the current class path

Cause: The resource file named in the error message contained all the JNDI mappings required for the BPEL process domain to initialize.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00231: error while attempting to instantiate the class "{0}" as the adapter manifest for "{1}", data source "{2}"; exception reported is: {3}

Cause: The adapter manifest class "{0}" was not in the system class path, or there was an incompatibility with the JDK used to compile the class and the current JVM version.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00232: class "{0}" (for the adapter manifest for "{1}", data source "{2}") does not implement the IServerAdaptorManifest interface; all adapter manifests used by the OraBPEL server must implement this interface

Cause: This was an internal error. All adapter manifests registered with the system must conform to the IServerAdaptorManifest interface.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00233: adapter manifest class name for "{0}", data source "{1}" is not specified.

Cause: The adapter manifest class "{0}" was not in the system class path.

Action: Ensure that the Oracle BPEL libraries are set correctly in the system class path. If the libraries are configured correctly, the adapter configuration files may have been modified incorrectly.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00235: The component identifier "{0}" has not been registered with the server.

Cause: All component identifiers were kept in the "component" table; this table may have been modified incorrectly.

Action: Restart the application server; when the component is loaded, the identifier will be automatically registered again.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00236: The component reference "{0}" is not registered with the server.

Cause: All component references were kept in the "component" table; this table may have been modified incorrectly.

Action: Restart the application server; when the component is loaded, the reference will be automatically registered again.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00237: failure to create the component reference for "{0}"

Cause: The maximum number of components ({1}) were reached.

Action: Contact Oracle Support Services. At the current time, the maximum number of components has been set to 32767.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00238: exception while reading the component index from the data source; the exception reported is: {0}

Cause: There was a problem with connecting to the data source where the component index is stored.

Action: There are three things to verify. Verify that the machine hosting the data source is physically connected to the network. Verify that the connection pool properties as defined in the application server startup properties are valid. Verify that the database schema for the OraBPEL server has been installed in the data source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00239: exception while writing the component index (application_name "{0}", composite_name"{1}", revision "{2}", label "{3}", component_name "{4}") to the data source; the exception reported is: {5}

Cause: There was a problem with connecting to the data source where the component index is stored.

Action: There are three things to verify. Verify that the machine hosting the data source is physically connected to the network. Verify that the connection pool properties as defined in the application server startup properties are valid. Verify that the database schema for the OraBPEL server has been installed in the data source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00240: exception occurs while removing the component index (dn "{0}", ref "{1}") from the data source; the exception reported is: {2}

Cause: There was a problem with connecting to the data source where the component index is stored.

Action: There are three things to verify. Verify that the machine hosting the data source is physically connected to the network. Verify that the connection pool properties as defined in the application server startup properties are valid. Verify that the database schema for the OraBPEL server has been installed in the data source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-01005: failure to compile the generated BPEL classes for BPEL process "{0}" of composite "{1}"

Cause: The class path setting is incorrect.

Action: Ensure that the class path is set correctly. If this happens on the server side, verify that the custom classes or jars which this BPEL process is depending on are deployed correctly. Also verify that the run time is using the same release/version.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-01007: build directory "{0}" for the BPEL process "{1}" of composite "{2}" cannot be found or accessed

Cause: The compiler could not find or create the directory "{0}".

Action: Ensure that the parent directory of "{0}" is a valid directory and that it is not read-only.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-01010: failure to generate the BPEL process file "{0}".

Cause: Could not generate named BPEL process file. The exception reported was "{1}".

Action: Ensure that the file "{0}" is a valid file to be generated.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-01027: trying to manipulate the nonexistent part "{1}" in a message of type "{0}"

Cause: An invalid request was made to manipulate the invalid part "{1}".

Action: Ensure that the client request is correct.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-01028: cannot find propertyAlias definition that associates the BPEL correlation "{0}" of correlationSet "{1}" to messageType "{2}"

Cause: A propertyAlias must be defined to associate the BPEL correlation to a correlationSet. The run time could not find it.

Action: Ensure that the mentioned propertyAlias is in one of the WSDL files that are referenced by the composite. Redeploy the composite.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-01029: cannot find property definition for "{0}" in any of the WSDL files

Cause: The BPEL correlation property needs to be defined. But the run time could not find it.

Action: Define the mentioned BPEL property in one of the WSDL files referenced by the composite.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-01030: cannot generate debug model file "{0}"

Cause: The named BPEL debug model file was not generated. The exception reported was: "{1}".

Action: Correct the error reported by the error message.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-01032: specified process ID "{0}" is invalid

Cause: The specified process identifier did not follow the naming constraints.

Action: Valid process identifiers might start with a letter, a ''$'' or ''_'' character; process characters (other than the first character) include a letter, a digit, a ''$'', a ''_'' or ''-'' character. The max length permitted is 100. Ensure that the component name specified in the composite descriptor conforms to the above mentioned constraints.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02000: The class "{0}" for the block element "{1}" does not implement the ICubeBlock interface.

Cause: This was an internal error. All block elements contained within the process domain must implement this interface.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02001: error while attempting to instantiate the class "{1}" for the block element "{0}"; exception reported is: {2}

Cause: This was an internal error. The block class "{0}" was not in the composite class path, or there was an incompatibility with the JDK used to the compile the class and the current JVM version.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02002: block element "{0}" missing its class name; this element cannot be created without its class name

Cause: This was an internal error. The block element class "{0}" was not in the composite class path.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02003: A Cube element is missing its "ID" property. Every Cube element in the process domain is uniquely identified by its "ID" property.

Cause: This was an internal error. The element was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02005: The parent block element "{0}" specified by node or block element "{1}" is not defined in the service class map. All nodes or blocks contained in the map must be bound to a valid parent block element.

Cause: This was an internal error. The element was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02006: The node or block element "{0}" is missing a parent block identifier. All nodes or blocks contained in the service class map must be bound to a parent block element.

Cause: This was an internal error. The element was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02007: Multiple method block elements are specified in the service class map. A valid map can only contain one method block element.

Cause: This was an internal error. The element was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02008: No block elements are specified in the service class map. All valid maps must contain at least one block element (the root block).

Cause: This was an internal error. The block map was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02009: No node elements are specified in the service class map. All valid maps must contain at least one node element.

Cause: This was an internal error. The block map was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02010: No method block element is specified for the service class map. All valid maps must contain one method block element.

Cause: This was an internal error. The block map was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02011: The class "{0}" for the node element "{1}" does not implement the ICubeNode interface.

Cause: This was an internal error. All node elements contained within the process domain must implement this interface.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02012: error while attempting to instantiate the class "{1}" for the node element "{0}"; the exception reported is: {2}

Cause: This was an internal error. The node class "{0}" was not in the composite class path or there was an incompatibility with the JDK used to the compile the class and the current JVM version.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02013: The class "{0}" cannot be found in the current class path.

Cause: This was an internal error. The node element class "{0}" was not in the composite class path.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02014: The node element "{0}" is missing its class name; this element cannot be created without its class name.

Cause: This was an internal error. The node class name should be generated by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02015: The BPEL process "{0}" (revision "{1}") has been compiled with an older version of SCAC; current BPEL process domain cannot execute this process.

Cause: An attempt to deploy a process that was compiled with an older version of SCAC failed.

Action: Recompile the BPEL process using the SCAC tool bundled with the current process domain.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02016: The process "{0}" is not initializing because of the error: "{1}".

Cause: This error contained the exceptions thrown by the underlying process loading module.

Action: Check for possible cause in the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02017: cannot compress the data stream with GZIP algorithm; exception reported is: {0}

Cause: This error contained the exceptions thrown by the underlying compression layer.

Action: Check for possible cause in the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02018: cannot uncompress the data stream with GZIP algorithm; exception reported is: {0}

Cause: This error contained the exceptions thrown by the underlying compression layer.

Action: Check for possible cause in the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02019: cannot compute the md5 checksum; exception reported is: {0}

Cause: This error contained exceptions thrown by the underlying digest layer.

Action: Check for possible cause in the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02020: failure to serialize the audit trail for instance "{0}" to its binary representation; exception reported is: {1}

Cause: This was an internal error. This error contained the exceptions thrown by the underlying XML marshalling module.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02022: The value "{0}" for the tag "{1}" in the XML serialized text for the audit trail for instance "{2}" is not a numeric value.

Cause: The tag "{1}" did not contain a numeric value.

Action: Ensure that the value for tag "{1}" conforms to the expected numeric format.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02023: failure to activate the block "{0}" for the instance "{1}"; exception reported is: {2}

Cause: This error contained the exceptions thrown by the underlying routing system.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02024: failure to invoke the method "until" on the block "{0}" for the instance "{1}"; exception reported is: {2}

Cause: This error contained the exceptions thrown by the underlying routing system.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02025: failure of the block "{0}" to handle a business exception for the instance "{1}"; exception reported is: {2}

Cause: This error contained the exceptions thrown by the underlying routing system.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02026: failure to invoke the canActivate method on the block "{0}" for the instance "{1}"; exception reported is: {2}

Cause: This error contained the exceptions thrown by the underlying routing system.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02027: failure to deserialize the instance "{0}" from binary format; exception reported is: {1}

Cause: This error contained the exceptions thrown by the underlying serialization system.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02028: failure to serialize the instance "{0}" to binary format; exception reported is: {1}

Cause: This error contained the exceptions thrown by the underlying serialization system.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02029: The process domain cannot create the bean "{0}"; this bean is responsible for generating a unique key for a new instance. The exception reported is: "{1}".

Cause: The SOA application or class path was not configured correctly.

Action: Verify that the instance key generator bean has been properly deployed to the server and can be properly mounted from a java class.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02030: failure to marshall the instance "{0}" to XML format; exception reported is: {1}

Cause: This error contained the exceptions thrown by the underlying serialization system.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02031: The instance "{0}" is created from the domain "{1}"; the current domain is "{2}". A process can be loaded only from the domain from which it was created.

Cause: The instance was not accessed because it was created in a different domain.

Action: If this instance is being accessed from the API, try looking up the instance "{0}" from the "{1}" domain (change the domain ID parameter to the Locator initializer).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02032: The instance "{0}" is created with process guid "{1}"; the current guid for the process "{2}" (revision "{3}") is "{4}".

Cause: Whenever a process is deployed on top of an existing process with the same process ID and revision tag, all instances created from the previous process are marked as stale.

Action: If this instance is being accessed from the console, the browser may be referring to an out-of-date page; click the Instances tab to get the current list of active instances.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02033: failure to construct a valid instance key from the string "{0}"; exception reported is: {2}

Cause: The instance did not consist of a single integer value.

Action: If the instance key has not been constructed by the process domain, ensure that the key format is valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02037: exception while trying to create a context object; the exception reported is: {0}

Cause: This error contained the exceptions thrown by the underlying JNDI environment.

Action: Verify that the directory service on the application server has been configured correctly.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02038: The process domain is unable to look up the context object using the bind name "{0}"; the exception reported is: {1}

Cause: This error contained the exceptions thrown by the underlying JNDI environment.

Action: Verify that the JNDI identifier is valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02040: exception while trying to destroy a context object; the exception reported is: {0}

Cause: This error contained the exceptions thrown by the underlying JNDI environment.

Action: Verify that the directory service on the application server has been configured correctly.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02041: The action "{0}" cannot be performed on the instance "{1}" because of its current state ("{2}").

Cause: The current instance state did not allow the requested action to be performed.

Action: Consult the product documentation for a list of all the permissible actions that can be performed on an instance when it is in the "{2}" state.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02042: The action "{0}" cannot be performed on the work item "{1}" because of its current state ("{2}").

Cause: The current work item state did not allow the requested action to be performed.

Action: Consult the product documentation for a list of all the permissible actions that can be performed on a work item when it is in the "{2}" state.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02043: The action "{0}" cannot be performed on the scope "{1}" because of its current state ("{2}").

Cause: The current scope state did not allow the requested action to be performed.

Action: Consult the product documentation for a list of all the permissible actions that can be performed on a scope when it is in the "{2}" state.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02044: The process domain is failing to write the audit trail for instance "{0}"; the exception reported is: {1}

Cause: This error contained the exceptions thrown by the underlying persistence framework.

Action: Check the log for the underlying exception trace after setting the logging level to debug mode.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02046: The process domain is failing to write the debug trace for instance "{0}"; the exception reported is: {1}

Cause: This error contained the exceptions thrown by the underlying serialization layer.

Action: Check the log for the underlying exception trace after setting the logging level to debug mode.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02047: The process domain is failing to write the instance trace for instance "{0}"; the exception reported is: {1}

Cause: This error contained the exceptions thrown by the underlying serialization layer.

Action: Check the log for the underlying exception trace after setting the logging level to debug mode.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02048: The process domain is unable to handle the work item "{0}"; the exception reported is: {1}

Cause: This error contained the exceptions thrown by the underlying process execution layer.

Action: Check the log for the underlying exception trace after setting the logging level to debug mode.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02050: The invocation for method "{0}" on the instance "{1}", process "{2}" (revision "{3}") is cancelled. The return value for this method cannot be determined in this case.

Cause: The instance "{1}" was cancelled or aborted.

Action: Check the audit trail for instance "{1}" for more information.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02051: The invocation for method "{0}" on the instance "{1}", process "{2}" (revision "{3}") is not complete. The return value for this method cannot be fetched until the method has completed.

Cause: The instance "{1}" was not complete yet.

Action: Resubmit this request after several minutes. Note that the method may contain some asynchronous interactions that could take an indeterminate amount of time to complete.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02052: The BPEL domain "{0}" is missing.

Cause: The BPEL domain "{0}" may not have initialized properly.

Action: Check the log for the underlying exception trace after setting the logging level to debug mode.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02053: The BPEL domain "{0}" is not finished initializing yet.

Cause: The domain initialization procedure was not finished yet.

Action: Resubmit the request in few minutes. The initialization progress can be monitored in the server log; set the logging level to debug mode.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02054: The BPEL domain "{0}" is currently uninitializing; the domain may not be accessed.

Cause: The domain was uninitializing.

Action: Restart the application server. If the domain uninitialized due to an exception, check the server log for the underlying exception trace (be sure to set the logging level to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02055: failure to handle a fault thrown from a scope, by any blocks in the scope chain

Cause: This exception occurred because the fault thrown in the BPEL flow was not handled by any fault handlers and reached the top-level scope.

Action: A top-level fault handler should be added to the flow to handle faults not caught from within the flow.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02057: The block element "{0}" is not defined in the service class map.

Cause: This was an internal error. The flow was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02058: The node element "{0}" is not defined in the service class map.

Cause: This was an internal error. The flow was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02059: The process domain is unable to fetch the work item "{0}" from the memory repository.

Cause: This was an internal error. The work item was not correctly registered from the previous transaction.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02060: failure to activate the node "{0}" for the instance "{1}"; the exception reported is: {2}

Cause: An exception was thrown by the underlying routing subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the instance.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02061: failure to finalize the node "{0}" for the work item "{1}"; the exception reported is: {2}

Cause: An exception was thrown by the underlying routing subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the work item.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02062: failure to invoke the canActivate method on the node "{0}" for the instance "{1}"; the exception reported is: {2}

Cause: An exception was thrown by the underlying routing subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the instance.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02063: failure to deserialize the delivery callback messages for conversation "{0}", message "{1}" from the binary format; the exception reported is: {2}

Cause: An exception was thrown by the underlying delivery subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the conversation.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02064: failure to serialize the delivery callback messages for conversation "{0}", message "{1}" to the binary format; the exception reported is: {2}

Cause: An exception was thrown by the underlying delivery subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the conversation.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02065: failure to serialize the delivery properties for conversation "{0}" to the binary format; the exception reported is: {1}

Cause: An exception was thrown by the underlying delivery subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the conversation.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02066: failure to deserialize the delivery properties for conversation "{0}" from the binary format; the exception reported is: {1}

Cause: An exception was thrown by the underlying delivery subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the conversation.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02067: failure to marshall the delivery callback messages for conversation "{0}", message "{1}" to XML; the exception reported is: {2}

Cause: An exception was thrown by the underlying delivery subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the conversation.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02068: Failure to call method "{0}" of the delivery persistence service with parameter "{1}". This operation is not supported.

Cause: This was an internal error. Delivery persistence service does not support advanced persistence features such as lazy loading. The persistence manager should not have used those related operations.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02069: The delivery service fails to load the message content from the data store; the exception reported is: {0}

Cause: This was an internal error. Either the load() method was not working properly if the object type was imported into the process, or the delivery message content might have been edited manually in the data store.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02070: The delivery service fails to store the object "{0}" of type "{1}" to the data source. The exception reported is: {2}

Cause: This was an internal error. The save() method was not working properly if the object type was imported into the process.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02071: failure to copy the object "{0}" of type "{1}"; the exception reported is: {2}

Cause: An exception was thrown by the underlying persistence subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the object.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02072: failure to release the moniker "{0}"; the exception reported is: {1}

Cause: An attempt was made to remove the last reference to a moniker before the object referred to by the moniker had been loaded.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02073: failure to delete the object "{0}" of type "{1}"; the exception reported is: {2}

Cause: An exception was thrown by the underlying persistence subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the object.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02074: The target element with ID "{0}" cannot be located in the current XML document. The node "{1}" has a reference link to this element.

Cause: The document was corrupt; it might have been edited manually.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02075: The element "{0}" does not have an "xsi:type" attribute specifying the schema type of the underlying Java object. An XML fragment cannot be properly unmarshalled to its Java representation without this information.

Cause: The document was corrupt; it might have been edited manually.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02076: failure to deserialize an object from its moniker format; the exception reported is: {0}

Cause: An exception was thrown by the underlying persistence subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the deserialization failure.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02077: Assertion failure: object "{0}" has negative reference count "{1}".

Cause: This was an internal error. An object had a reference count less than zero because it fell out of scope and had its reference count decremented.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02078: failure to marshall the object "{0}" of type "{1}" to XML; the exception reported is: {2}

Cause: An exception was thrown by the underlying marshalling subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the object.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02079: failure to prepare the object "{0}" of type "{1}" for marshalling; the exception reported is: {2}

Cause: An exception was thrown by the underlying marshalling subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the object.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02080: failure to prepare the object "{0}" of type "{1}" for saving; the exception reported is: {2}

Cause: An exception was thrown by the underlying persistence subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the object.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02081: failure to read an object's moniker from the deserializer stream; the exception reported is: {0}

Cause: An exception was thrown by the underlying persistence subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02082: failure to save the object "{0}" of type "{1}"; the exception reported is: {2}

Cause: An exception was thrown by the underlying persistence subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the object.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02083: failure to unmarshall the object "{0}" of type "{1}" from XML; the exception reported is: {2}

Cause: An exception was thrown by the underlying marshalling subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the object.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02084: failure to write an object's moniker into the serializer stream; the exception reported is: {0}

Cause: An exception was thrown by the underlying persistence subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02085: The metadata for object "{0}" is not registered with the persistence service.

Cause: This was an internal error. Every Java object type in the scope must be registered.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the object.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02086: The metadata for object "{0}" does not contain an embedded moniker.

Cause: This was an internal error. One or more of the linked variants in the scope did not contain an embedded moniker that contained the actual bytes defining the object.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the object.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02087: The node "{0}" is missing its reference identifier.

Cause: This was an internal error. Any element with an "href" attribute did not contain a non-empty reference ID that could be resolved to another element in the document.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02088: An instance's root scope cannot be routed.

Cause: This was an internal error. The flow was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02089: failure to construct a valid scope activation key from the string "{0}".

Cause: This was an internal error. The expected format was: "param1-param2", where the two parameters were: instance ID (integer) and scope ID (string) respectively.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02090: failure to unmarshall the metadata for the scope tree of instance "{0}"; the exception reported is: {1}

Cause: This was an internal error. A variant's metadata did not contain "guid", "class name" and "ref-count" attributes; or the "ref-count" attribute was not an integral value while it should be.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02091: failure to release an instance's root scope from the scope tree.

Cause: This was an internal error. The flow was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02092: failure to unmarshall a scope for the instance "{0}" from an XML document; the exception reported is: {1}

Cause: An exception was thrown by the underlying marshalling subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the instance.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02093: The tag "{0}" is missing from the serialized XML text for the scope data for the instance "{1}".

Cause: This was an internal error. The XML document for this instance did not contain a value for the tag named in the error message.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02094: The scope "{0}" is not defined in the current instance.

Cause: This was an internal error. The scope was either closed or released, and it was not reachable.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02095: The scope associated with the block element "{0}" is not defined in the current instance.

Cause: This was an internal error. The scope metadata was corrupt.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02096: The value "{0}" for the tag "{1}" in the serialized XML text for instance "{2}" is not a parseable integral value.

Cause: This was an internal error. The value for tag named in the error message did not conform to the expected format.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02097: cannot read the XML model file for process "{0}" (revision "{1}"); the exception reported is: {2}

Cause: An exception was thrown by the underlying operating system.

Action: Verify that the BPEL archive for the process named in the error message (for the cited revision) has been deployed correctly.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02100: cannot find the content file "{0}" for process "{1}" (revision "{2}").

Cause: The content file named in the error message might not have been deployed with the process named in the error message.

Action: Verify that the path named in the error message is correct, and that it refers to a file that has been included as a part of the deployment archive.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02101: cannot read the content file "{0}" for process "{1}" (revision "{2}"); the exception reported is: {3}

Cause: The content file named in the error message might not have been deployed with the process named in the erorr message.

Action: Verify that the path named in the error message is correct, and that it refers to a file that has been included as a part of the deployment archive.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02102: Method "{0}" is missing.

Cause: This was an internal error. The flow was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02103: The map for node element "{0}" is not defined in the process class.

Cause: This was an internal error. The flow was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02104: New instances cannot be created when the process "{0}" is not active; existing instances are permitted to complete as usual.

Cause: The process named in the error message was not active and therefore could not create new instances.

Action: The process life cycle can be changed to active through the EM console.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02106: The process "{0}" has not been turned on. No operations can be performed on the process or any instance belonging to the process if the process is turned off.

Cause: The process named in the error message was not turned on; therefore it did not process any requests.

Action: Consult the administrator if this process has not been turned on.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02107: The process domain is unable to fetch the scope activation message with key "{0}" from the data source.

Cause: The scope activation message with the key named in the error message was not found in the data source.

Action: This row may have been manually removed from the data source; in which case the instance should be aborted.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02108: cannot create a copy of the scope "{0}"

Cause: This was an internal error. Scopes are not cloneable.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02109: The process domain is unable to deserialize the scope data for instance "{0}" from its binary representation; the exception reported is: {1}

Cause: An exception was thrown from the underlying serialization subsystem.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02110: failure to marshall the scope data for instance "{0}" into XML; the exception reported is: {1}

Cause: An exception was thrown from the underlying serialization subsystem.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02111: failure to serialize the scope data for instance "{0}" into a binary byte stream; the exception reported is: {1}

Cause: An exception was thrown from the underlying serialization subsystem.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02112: The absolute scope ID "{0}" does not conform to the expected format for a scope identifier.

Cause: This was an internal error. The expected scope ID format is (block id + relative scope id).

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02113: failure to fetch the return or header value from the root scope.

Cause: This was an internal error. Only top-level scopes can contain return or header values.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02114: The requested variant "{0}" is not a primitive variant type. Reference variants cannot be cast to a primitive type.

Cause: This was an internal error. The code accessing the variant named in the error message was assuming that that variant was a reference variant.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02115: The requested variant "{0}" is not a reference variant type. Primitive variants cannot be cast to a reference type.

Cause: This was an internal error. The code accessing the variant named in the error message was assuming that that variant was a primitive variant.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02116: The variant object associated with key "{0}" in the scope tree is neither a primitive nor a reference variant.

Cause: This was an internal error. The type of the declared variant "{0}" in the scope tree is not contained in the list of supported types (serializable and deserializable), including primitive (all Java primitive types) and reference (java.lang.String, java.util.Date, BPEL documents, EJB entity beans and one-dimensional arrays of any primitive or reference type).

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02117: A variable with key "{0}" is already declared in the current scope.

Cause: This was an internal error. The flow was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02118: The variable "{0}" is not declared in the current scope. All variables must be declared in the scope before being accessed.

Cause: This was an internal error. The flow was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02121: failure to marshall the object "{0}" of class "{1}" to XML; the exception reported is: {2}

Cause: An exception was thrown by the underlying marshalling subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the marshalling failure.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02122: The type class "{0}" is missing a "{1}" tag.

Cause: The XML fragment for this type was missing a required tag; the XML document might have been edited manually.

Action: Set the logging level to debug mode. Check the log for the any exception related to the type class.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02123: The value "{0}" of the tag "{1}" in the serialized XML text for the type class "{2}" is not a parseable integral value.

Cause: The value for the tag named in the error message did not conform to the expected format.

Action: Set the logging level to debug mode. Check the log for the any exception related to the type class.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02124: failure to deserialize the work item "{0}" from the binary format; the exception reported is: {1}

Cause: This error contained the exceptions thrown from the underlying serialization subsystem.

Action: Set the logging level to debug mode. Check the log for the any exception related to the work item.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02125: failure to serialize the work item "{0}" to the binary format; the exception reported is: {1}

Cause: An exception was thrown from the underlying serialization subsystem.

Action: Set the logging level to debug mode. Check the log for the any exception related to the work item.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02126: failure to deserialize the work items for instance "{0}" to the binary format; the exception reported is: {1}

Cause: An exception was thrown from the underlying serialization subsystem.

Action: Set the logging level to debug mode. Check the log for the any exception related to the instance.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02127: failure to serialize the work items for instance "{0}" to the binary format; the exception reported is: {1}

Cause: An exception was thrown from the underlying serialization subsystem.

Action: Set the logging level to debug mode. Check the log for the any exception related to the instance.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02128: failure to marshall the work item "{0}" to the XML format; the exception reported is: {1}

Cause: An exception was thrown from the underlying marshalling subsystem.

Action: Set the logging level to debug mode. Check the log for the any exception related to the work item.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02129: cannot construct a valid work item key from the string "{0}"

Cause: The string was of wrong format to construct a valid work item key. The expected key format is: "param1-param2-param3-param4", where the parameters are: instance ID (integer), node ID (string), scope ID (string) and count ID (integer) respectively.

Action: If the work item key string has not been constructed by the process domain, ensure that the key format is valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02130: The tag "{0}" is missing from the serialized XML text for work item "{1}".

Cause: The XML document for this instance was missing a value for the tag named in the error message.

Action: Set the logging level to debug mode. Check the log for the any exception related to the work item.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02131: The activity "{0}" is throwing a null exception.

Cause: This was an internal error. Exceptions thrown from the activity cannot be null.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02132: The value "{0}" for the tag "{1}" in the serialized XML text for work item "{2}" is not a parseable integral value.

Cause: The value for tag "{1}" was not an integer.

Action: If the work item XML has not been constructed by the process domain, ensure that the XML format is valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02133: error while attempting to expire the work item "{0}" (located at node "{1}"); the exception reported is: "{2}"

Cause: An exception was thrown from the underlying process execution subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the work item.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02134: error while attempting to extend the work item "{0}" (located at node "{1}"); the exception reported is: "{2}"

Cause: An exception was thrown from the underlying process execution subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the work item.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02135: error while attempting to execute the manage method on the work manager for node "{0}"; the exception reported is: "{1}"

Cause: An exception was thrown from the underlying process execution subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the node.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02136: error while attempting to resume the work item "{0}" (located at node "{1}"); the exception reported is: "{2}"

Cause: An exception was thrown from the underlying process execution subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the work item.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02137: error while attempting to suspend the work item "{0}" (located at node "{1}"); the exception reported is: "{2}"

Cause: An exception was thrown from the underlying process execution subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the work item.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02138: The method invocation "{0}" is returning an invalid number of callback arguments.

Cause: This was an internal error. More than one return value was returned. Currently, a maximum of one return value is permitted from a method invocation; the actual number of values returned for this invocation was "{1}".

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02139: The method invocation "{0}" is throwing an invalid exception object.

Cause: This was an internal error. The exception object did not extend the Throwable class. The object thrown was of class "{1}".

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02140: failure to invoke the method "{0}" on the performer "{1}"; the exception reported is: "{2}"

Cause: An exception was thrown while performing a callback to an activity.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the performer.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02141: error while attempting to execute the cancelPerform method on the work performer for node "{0}"; the exception reported is: "{1}"

Cause: An exception was thrown while canceling an activity.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the node.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02142: error while attempting to execute the perform method on the work performer for node "{0}"; the exception reported is: "{1}"

Cause: An exception was thrown while executing an activity.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the node.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02143: error while attempting to throw the exception "{0}" from the activity "{1}"; the exception reported is: "{2}"

Cause: An exception is thrown while throwing an exception from an activity.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the activity.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02149: The instance identifier "{0}" is missing its domain ID; this ID specifies the BPEL domain from which the instance is generated.

Cause: This was an internal error. The instance domain ID was not set upon creation and rehydration.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02150: The process domain is unable to fetch the activity "{0}" from the data source.

Cause: The activity key "{0}" did not refer to a valid activity, or the activity was removed from the data source.

Action: Check the work_item database table with the activity key; if the referred row cannot be found, check the audit trail for the instance.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02151: More than one activity from domain "{1}" is returned when querying with the key "{0}".

Cause: Multiple activities were bound to the custom key "{0}". Only one activity should be returned per key.

Action: If the key is a user-specified custom key, ensure that the key is unique.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02152: The process domain is unable to fetch the instance with key "{0}" from the data source.

Cause: The instance key "{0}" did not refer to a valid instance, or the instance was removed from the data source (this might have been the case if the BPEL global transaction was modified by an external source).

Action: Check the cube_instance database table with the instance key; if the referred row cannot be found, check the server logs for traces related to this instance key.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02154: Multiple instances are returned when querying with the key "{0}", while only one instance is expected.

Cause: Multiple instances of a business process were created with the key "{0}". Each instance should be uniquely identified by a key.

Action: If the key is a user-specified custom key, ensure that the key is unique.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02155: The process domain is unable to fetch the bytes for the business document "{0}" from the data source.

Cause: The document key "{0}" did not refer to a valid document, or the document was removed from the data source.

Action: Check the xml_document database table with the document key; if the referred row cannot be found, check the server logs for traces related to this document key.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02156: The process domain is unable to fetch the scope context data for the instance with key "{0}" from the data source.

Cause: The instance key "{0}" did not refer to a valid instance, or the instance was removed from the data source.

Action: Check the cube_scope database table with the instance key; if the referred row cannot be found, check the server logs for traces related to this instance key.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02157: failure to read the audit trail for instance "{0}"; the exception reported is: {1}

Cause: An exception was thrown while writing the audit trail bytes to the in-memory buffer after those bytes were read from the data store.

Action: Set the logging level to debug mode, check the log for the underlying exception stack trace related to this in-memory buffer writing problem.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02158: failure to create the scope deserializer object for instance "{0}"; the exception reported is: {1}

Cause: An exception was thrown while creating a deserializer from the scope bytes.

Action: Set the logging level to debug mode, check the log for the underlying exception stack trace related to this deserializer creation problem.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02159: The process domain is unable to fetch the invocation content for the message "{0}" from the data source.

Cause: The message key "{0}" did not refer to a valid invocation message, or the invocation message was removed from the data source (this might have been the case if the BPEL global transaction was modified by an external source).

Action: Check the invoke_message database table with the message key; if the referred row cannot be found, check the server logs for traces related to this message key.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02160: The process domain is unable to fetch the callback content for the message "{0}" from the data source.

Cause: The message key "{0}" did not refer to a valid callback message, or the callback message was removed from the data source (this might have been the case if the BPEL global transaction was modified by an external source).

Action: Check the dlv_message database table with the message key; if the referred row cannot be found, check the server logs for traces related to this message key.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02161: The process domain is unable to fetch the audit detail bytes for the instance "{0}", detail ID "{1}" from the data store.

Cause: The instance identifier "{0}" or detail identifier "{1}", or both, did not refer to a valid entry in the audit_details table; this row might have been manually removed from the table.

Action: Check the audit_details database table with the identifiers named in the error message; if the referred row cannot be found, check the server logs for traces related to these identifiers.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02162: The instance index "{0}" is not within the valid range.

Cause: The index "{0}" for instance "{1}" was out of range.

Action: Change the index value in the xpath function or the facade API call to conform to the valid index range. Try a value between 1 and {2} (inclusive).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02163: cannot access scope "{0}"; scope is already released

Cause: This was an internal error. An attempt was made to access a scope that has already been released.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02164: An unknown cache policy "{0}" is specified for property "{1}".

Cause: The cache policy "{0}" was not recognized. The list of valid cache policies is { lru, auto, soft-filo, soft-lru, hybrid }.

Action: Change the cache policy configuration property to one of the recognized values. The valid cache policies are lru, auto, soft-filo, soft-lru, and hybrid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02165: cannot initialize connection pool for connection factory "{0}"; the reason is {1}

Cause: An exception was thrown while initializing the JMS connection pool.

Action: Set the logging level to debug mode, check the log for the underlying exception stack trace.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02166: failure to finalize the compensation node "{0}" for the second time; the exception reported is: {1}

Cause: An exception was thrown while attempting to execute a compensation activity.

Action: Set the logging level to debug mode, check the log for the underlying exception stack trace.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02167: The process ("{1}", revision "{2}") for instance "{0}" is not loaded by the domain; the instance is marked as stale.

Cause: The archive for process "{1}" of revision "{2}" might have been deleted from the domain manually. In this case, the domain would not have been able to mark all instances that belonged to the process as being stale.

Action: Check if the process has been manually deleted from the domain.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02168: A problem occurs while reading the sensor file "{0}"; the exception reported is: {1}

Cause: An exception was thrown while trying to access the sensor file named in the error message.

Action: Ensure that the file exists. If it has been manually deleted, then redeploy the process.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02169: A problem occurs while reading the sensor action file "{0}"; the exception reported is: {1}

Cause: An exception was thrown while trying to access the sensor action file named in the error message.

Action: Ensure that the file exists. If the file has been manually deleted, then redeploy the process.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02171: A problem occurs while updating the label status "{0}" in instance "{1}".

Cause: This label was not detected during process compilation.

Action: Redeploy the process and try again. If the redeployment step does not work, then contact Oracle Support Services. Provide the error message, the composite source, and the exception trace in the server log files (with the logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02177: failure to create the data source "{0}"; the exception reported is: {1}

Cause: An exception was thrown while attempting to create a data source.

Action: Set the logging level to debug mode, check the log for the underlying exception trace related to this data source creation problem.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02178: the BPEL process "{0}" with revision "{1}" is not loaded.

Cause: The process was not initialized properly, or the process was disabled.

Action: Set the logging level to debug mode, check the log for the underlying exception trace related to this process loading problem.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02180: The current JTA transaction is aborting due to a user rollback fault being thrown.

Cause: This exception was caused by a bpelx:rollback fault being thrown or a ROLLBACK_ONLY FabricInvocationException being thrown. BPEL engine is directed to roll back the current JTA transaction.

Action: There is no action recommended.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02181: The current JTA transaction is marked as rollback-only when performing the activity "{0}".

Cause: The reason was {1}.

Action: Check on the activity which invokes a subprocess or downstream process that results in the JTA transaction being marked as rollback-only.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02182: catching unhandled fault "{0}" when processing instance "{1}" for process "{2}"

Cause: The exception was {3}.

Action: Check the error log file and the audit trail for instance "{1}" for more information. Try to use BPEL fault handlers to catch the faults in the BPEL process "{2}". If this is a system exception, please report this to the system administrator.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02183: bpel engine can not execute activities without an active transaction. please debug the invoked subsystem on why the tranasction is not in active status. the bpel instance id is "{0}".

Cause: The reason was {1}.

Action: Consult the system administrator regarding this error.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02184: The process domain was unable to serialize the activity guide milestone state data for instance "{0}" into a binary byte stream. The exception reported is: {1}

Cause: This error is a wrapper for exceptions thrown from the underlying serialization sub-system.

Action: Please contact Oracle support. Be sure to provide the error message, the composite source and the exception trace in the log files (with loggers set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02185: The process domain was unable to deserialize the activity guide milestone state data for instance "{0}" from its binary byte representation. The exception reported is: {1}

Cause: This error is a wrapper for exceptions thrown from the underlying serialization sub-system.

Action: Please contact Oracle support. Be sure to provide the error message, the composite source and the exception trace in the log files (with loggers set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02186: The process domain was unable to fetch the activity guide instance with key "{0}" from the datasource.

Cause: The instance key "{0}" does not refer to a valid activity guide instance, or the instance has been removed from the datasource (this may be case if the BPEL global transaction has been modified by an external source).

Action: Check the "ag_instance" database table; if the row cannot be found, check the server logs.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02187: Failed to load activity guide instance with key "{0}" from the datasource. The exception reported is: {1}

Cause: This error is a wrapper for exceptions thrown while loading activity guide instance from the datasource.

Action: Please check the log for the underlying exception trace. Be sure to set the logging level to debug mode.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02188: Failed to insert activity guide instance with key "{0}" to the datasource. The exception reported is: {1}

Cause: This error is a wrapper for exceptions thrown while inserting activity guide instance to the datasource.

Action: Please check the log for the underlying exception trace. Be sure to set the logging level to debug mode.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02189: Failed to update activity guide instance with key "{0}" in the datasource. The exception reported is: {1}

Cause: This error is a wrapper for exceptions thrown while updating activity guide instance to the datasource.

Action: Please check the log for the underlying exception trace. Be sure to set the logging level to debug mode.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02190: Failed to evaluate expression "{0}" in field "{1}" in activity guide instance with key "{2}". The exception reported is: "{3}"

Cause: The expression may not have been constructed correctly.

Action: Make sure that the expression is constructed correctly.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02191: The activity guide definition at "{0}" could not be read.

Cause: The activity guide definition either is missing or invalid.

Action: Make sure that the activity guide definition is available at the specified URL and that it is a valid XML document.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02192: The activity guide definition at "{0}" does not conform to the activity guide definition XML schema definition. The errors are "{1}"

Cause: The activity guide definition does not conform to the activity guide definition XML schema.

Action: Make sure that the activity guide definition conforms to the activity guide definition XML schema definition.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02193: The activity guide definition at "{0}" could not be validated against the activity guide definition XML schema definition.

Cause: The activity guide definition is missing.

Action: Make sure that the activity guide definition is available at the specified URL and that it is a valid XML document.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02194: The milestone instance with name "{0}" cannot be found in activity guide instance with ciKey "{1}".

Cause: This is an internal error. This may have been caused by some logical errors in the program.

Action: Please contact Oracle support. Be sure to provide the error message, the composite source and the exception trace in the log files (with loggers set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02195: The "{0}" operation on milestone "{1}" with status "{2}" in activity guide instance "{3}" is invalid. This operation can only be performed on milestones with status "{4}".

Cause: This is an internal error. This may have been caused by some logical errors in the program.

Action: Please contact Oracle support. Be sure to provide the error message, the composite source and the exception trace in the log files (with loggers set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02196: The "{0}" operation on activity guide instance "{1}" with status "{2}" is invalid. This operation can only be performed on activity guide instances with status "{3}".

Cause: This is an internal error. This may have been caused by some logical errors in the program.

Action: Please contact Oracle support. Be sure to provide the error message, the composite source and the exception trace in the log files (with loggers set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02197: The "{0}" operation on activity guide instance "{1}" for milestone "{2}" is invalid.

Cause: The milestone's expiration date is not set or milestone is configured to continue post expiration

Action: Please check configuration settings for the milestone "{2}") in BPEL designer.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02198: The current JTA transaction is aborting due to an user rollback fault being thrown. The upstream component should retry in a new JTA transaction upon catching this fault.

Cause: This exception was caused by a global retry fault being thrown from downstream component. The user had directed the BPEL engine to roll back the current JTA transaction and retry within new JTA transactions for the specified number of times and retry interval.

Action: There is no action recommended.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02199: The transaction became inactive when executing activity "{0}" for instance "{1}", bpel engine can not proceed further without an active transaction. please debug the invoked subsystem on why the transaction is not in active status. the transaction status is "{2}".

Cause: The reason was {3}.

Action: Consult the system administrator regarding this error.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02200: Master conversation ID is not available in context when executing work item "{0}" in component "{1}".

Cause: Master conversation ID was not supplied by the master process when initiating the call to the detail process.

Action: Make sure the master process's invoke activity to have bpelx:invokeAsDetail and bpelx:detailLabel attributes properly supplied.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02201: The process "{0}" has been suspended. No operations can be performed on the process or any instance belonging to the process if the process is suspended.

Cause: The process is suspended; therefore it did not process any requests.

Action: Consult the administrator if this process has been suspended.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02202: The process domain is unable to create Workitem for the activity "{0}"

Cause: Refer to cause

Action: Refer to cause for an action
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02203: Model.xml file not found for component "{0}"

Cause: Model.xml file was not generated for the component

Action: If component is BPEL 2.0, Model.xml file is not needed and thus does not get generated and this error is expected
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03001: The process domain is unable to determine the database type. The version table contains the vendor type for the current data source. The exception reported is: {0}

Cause: There was a problem with connecting to the data source where the version information was stored.

Action: Check all of the following to determine the location of the problem with connecting to the data source. Verify that the machine that hosts the data source is physically connected to the network. Verify that the connection pool properties as defined in the application server startup properties are valid. Verify that the database schema for OraBPEL has been installed in the data source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03002: The server is unable to look up the database schema version.The exception reported is: {0}

Cause: There was a problem with connecting to the data source where the version information is stored.

Action: Check all of the following to determine the location of the problem with connecting to the data source. Verify that the machine that hosts the data source is physically connected to the network. Verify that the connection pool properties as defined in the application server startup properties are valid. Verify that the database schema for OraBPEL has been installed in the data source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03003: The database schema version {0} from the database does not match the version {1} expected by the server.

Cause: The database schema for the SOA installation was not properly installed, or the installation was using a database schema installed for a prior release.

Action: The database schema currently in place has probably been configured for a previous release. Reinstall the database schema and start the server again.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03004: The database table "version" does not contain a data source vendor type

Cause: The database schema may have been modified by hand.

Action: Reinstall the database schema and start the process domain again.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03005: The database table "version" does not contain a version guid.

Cause: The database schema may have been modified by hand.

Action: Reinstall the database schema and start the server again.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03010: error while trying to instantiate the class {0} as the adapter manifest for {1}, data source {2}, the exception reported is: {3}

Cause: The adapter manifest class named in the error message was not in the system class path, or there was an incompatibility with the JDK used to compile the class and the current JVM version.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with the logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03011: The class {0} (for the adapter manifest for {1}, data source {2}) does not implement the IServerAdaptorManifest interface

Cause: This was an internal error. All adapter manifests registered with the system must conform to the IServerAdaptorManifest interface, and this one does not.

Action: Contact Oracle Support Services. Be sure to provide the error message and the exception trace in the log files (with loggers set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-03012: The adapter manifest class name for {0}, data source {1} is not specified

Cause: The adapter manifest class named in the error message was not in the system class path.

Action: Ensure that the Oracle BPEL libraries are set correctly in the system class path. If the libraries are configured correctly, the adapter configuration files might have been modified.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03013: cannot instantiate an instance for the class {0}

Cause: This was an internal error. Java class {0} that must be dehydrated or rehydrated within the OraBPEL server must implement the java.io.Serializable interface. And it must implement a default constructor.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-03410: error while trying to instantiate the agent class {0}; The exception reported was: {1}

Cause: The agent class might have relied on a class that was not found in the class path, or it might have relied on a JDK feature that was not compatible with the current JVM version.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-03411: invalid agent class

Cause: This was an internal error. The agent class {0} did not implement the IAgent interface. All agents managed by the system must implement this interface.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-03800: The process domain is not able to resolve which correlation set definition to apply to the received callback message for the operation {0}.

Cause: Correlation set definitions were registered with the process domain using operation name and process ID. The callback message was most likely missing the process ID.

Action: If the callback client is external, check that the callback URL contains the process identifier. If the client is another BPEL process, check that the correlation set is defined correctly in the receiving BPEL process.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03801: The received callback message is missing the operation name parameter. The process domain cannot resolve which correlation set definition to apply to the message without this parameter.

Cause: The callback message did not pass the operation name in the SOAP action property.

Action: If the callback client is external, check that the operation name is being passed in the message correctly. If the client is another BPEL process, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03802: The correlation set definition for operation {0}, process {1}, is not registered with the server.

Cause: The correlation set was not defined in the process.

Action: Redeploy the process to the container.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03803: The process domain cannot look up the engine bean; this bean is responsible for processing the callback of a received message. The exception reported is: {0}

Cause: This was an internal error. The SOA installation was not configured properly.

Action: Check that the engine bean has been properly deployed to the server and can be properly mounted from a Java class.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-03804: The synchronous polling thread is timing out waiting for a result from instance "{0}".

Cause: The callee was a durable synchronous process that had not reached its reply activity within the allotted timeout period.

Action: There may be a problem completing instance named in the error message. Check the process console for more information.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03805: The process domain is unable to find the protocol handler for the conversation type "{0}".

Cause: This was an internal error. Only the SOAP protocol handler is active by default.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with the logging set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-03806: The process domain is unable to process the callback for received message "{0}", for conversation "{1}", and the subscriber "{2}". The exception reported is: {3}

Cause: This error contained exceptions thrown from the underlying callback handler layer.

Action: Check the exception trace in the log (with the logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03810: A similar receive activity is being declared in the same process.

Cause: Another receive activity or equivalent (currently, onMessage branch in a pick activity) has already been enabled with the partnerLink "{0}", operation name "{1}" and correlation set "{2}" (or conversation ID). Appendix A - Standard Faults in the BPEL 1.1 specification specifies a fault should be thrown under these conditions.

Action: Redeploy the process after removing the conflicting receive activities.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03811: No correlation sets are defined for operation "{0}" (process "{1}").

Cause: There were no correlation sets defined for the operation and process named in the error message. All receive operations that do not use WS-Addressing to correlate messages must define at least one correlation set.

Action: Check the BPEL source to ensure that at least one correlationSet is defined for the operation named in the error message.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03812: cannot find the property alias "{0}", message type "{1}"

Cause: The property alias named in the error message was not defined in the BPEL/WSDL source.

Action: Check the BPEL/WSDL source to ensure that the property alias named in the error message has been defined.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03813: failure to evaluate the correlationAlias query "{0}" on the element "{1}".

Cause: The property alias was not defined correctly in the BPEL/WSDL source, or the payload is not as expected.

Action: Check the BPEL/WSDL source to ensure that property alias is defined correctly.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03850: Not able to acquire lock on invoke message {0}

Cause: More than one thread is contending for this entity

Action: No action required, it is rescheduled with delay
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03851: Not able to acquire lock on delivery message {0}

Cause: More than one thread is contending for this entity

Action: No action required, it is rescheduled with delay
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03852: Not able to acquire lock on cube instance for {0} : {1}

Cause: More than one thread is contending for this entity

Action: No action required, it is rescheduled with delay
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04000: The process domain is unable to count the number of instances. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04001: The process domain is unable to count the number of instances for the process "{0}" (revision "{1}"). The exception reported is: {2}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04002: An attempt to fetch the instances using the where condition "{0}" from the data source fails. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the SQL statement was constructed incorrectly.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04003: An attempt to fetch the work items using the where condition "{0}" from the data source fails. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the SQL statement has been constructed incorrectly.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04004: The process domain is unable to insert the current log entries for the instance "{0}" to the audit trail table. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04005: The process domain is unable to insert the current audit trail detail entries for the instance "{0}" to the audit details table. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04006: The process domain is unable to store the work items for the synchronous instance "{0}" to the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04007: The process domain is unable to store the audit trail for the synchronous instance "{0}" to the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04008: Unable to set the auto commit level for the current data source connection. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source, or the current transaction settings prohibit this action.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04009: unable to commit the current data source transaction; the exception reported is: {0}

Cause: There was a problem accessing the SOA data source, or the current transaction settings prohibit this action.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04010: The process domain is unable to purge the instances from the data source. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04011: The process domain is unable to delete the document "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04012: The process domain is unable to delete all the instances for the process "{0}" (revision "{1}") from the data source. The exception reported is: {2}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04013: The process domain is unable to fetch a list of the expired work items in the data source. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04014: The process domain is unable to look up the type for the instance "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04017: The process domain is unable to find the work items for the instance "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04018: The process domain is unable to find the audit trail entry for the instance "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04019: The process domain is unable to find the work items for the synchronous instance "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04020: The process domain is unable to find the audit trail for the synchronous instance "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04025: The process domain is unable to decode the properties for message GUID {0}, which are stored in column {1}; the exception reported is: {2}

Cause: This is an internal error. The properties have not been encoded properly.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-04026: The process domain is unable to find any pending callback messages in the data source. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04027: The process domain is unable to find any pending invoke messages in the data source. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04028: The process domain is unable to find any pending subscriptions in the data source. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04029: The process domain is unable to mark all instances (and activities) with process GUID {0} as stale. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04030: An attempt to fetch the audit details for the instance "{0}" (detail ID {1}) from the data source fails. The exception reported is: {2}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04031: An attempt to fetch the audit details for the instance "{0}" from the data source fails. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04032: The process domain is unable to read the audit detail for detailId "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the current transaction settings prohibit this action.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04033: The process domain is unable to fetch the document "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04034: The process domain is unable to find the closed instances for the domain "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04035: The process domain is unable to fetch the instance "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04036: The process domain is unable to fetch the scope activation message with key "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04037: The process domain is unable to fetch the work item "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04038: The process domain is unable to update or insert the document "{0}" into the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04039: The process domain is unable to update the key table "{0}". The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04040: The process domain is unable to update the LOB column "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04041: The process domain is unable to update or insert the instance "{0}" into the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04042: The process domain is unable to update or insert the serialized scope for the instance "{0}" into the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04043: The process domain is unable to delete or insert the scope activation message with key "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04044: The process domain is unable to update or insert the work item "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04045: The process domain is unable to batch update or insert the work items for the instance "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04046: The process domain is unable to batch insert a series of synchronous work items into the data source. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04048: The process domain is unable to insert the delivery data for conversation "{0}", subscriber "{1}" in the data source. The exception reported is: {2}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04049: The process domain is unable to select the delivery data for conversation "{0}" (subscriber "{1}") from the data source. The exception reported is: {2}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04050: The process domain is unable to select the delivery data for conversation "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04052: The process domain is unable to select the delivery data for subscriber "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04053: The process domain is unable to update the state of the delivery subscription "{1}" for conversation "{0}". The exception reported is: {2}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04054: The process domain is unable to update the state of the delivery subscription "{0}". The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04055: The process domain {0} is unable to delete handled delivery subscriptions. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04056: The process domain is unable to insert the delivery data for the message {0} and the operation {1} in the data source. The exception reported is: {2}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04057: The process domain is unable to delete the delivery data for the message {0} from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04058: The process domain "{0}" is unable to delete the handled delivery data from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04059: The process domain is unable to select the delivery data for the message {0} from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04060: The process domain is unable to select the delivery data for the message {0} and the operation {1} from the data source. The exception reported is: {2}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04061: The process domain is unable to update the state of the delivery the message {0}. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04062: The process domain is unable to delete the invocation data for the message {0} from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04063: The process domain "{0}" is unable to delete the handled invocation data from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04064: The process domain is unable to select the invocation data for the message {0} from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04065: The process domain is unable to select the invocation data for the process "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04066: The process domain is unable to insert the invocation data for the message {0} and the operation {1} in the data source. The exception reported is: {2}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04067: The process domain is unable to update the state of the invocation the message {0}. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04069: The process domain is unable to fetch a list of the stale instances belonging to the process "{0}" (revision "{1}"). The exception reported is: {2}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04076: The process domain is unable to look up the TX data source "{0}".

Cause: The J2EE container was not configured properly; a data source with the expected name has not been created or has been removed.

Action: Verify that the machine hosting the data source is physically connected to the network. In addition, verify that the connection pool properties, as defined in the application server startup properties, are valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04077: The process domain is unable to establish a connection with the data source with the connection URL "{0}". The exception reported is: {1}

Cause: The J2EE container was not configured properly; the connection parameters for the data source might not have been correct.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04078: The process domain is unable to release its data source connection. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source, or the transaction has become corrupt.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04079: cannot read BLOB stream from the data source with key "{0}"; the exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the current transaction settings prohibited this action.

Action: Verify that the machine hosting the data source is physically connected to the network. In addition, verify that the connection pool properties, as defined in the application server startup properties, are valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04080: The data stream for the instance or activity object "{0}" is not found in the data source.

Cause: The data stream with the instance or activity object key named in the error message was not found.

Action: Verify that the instance or activity key named in the error message refers to a valid instance or activity that has been started and not removed from the process domain.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04082: The process domain is unable to delete the instance "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04083: The process domain is unable to insert or update the exception entry for the activity "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04084: The process domain is unable to delete the exception entry for the activity "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04085: The process domain is unable to find the activity in the domain "{0}" with the custom key "{1}". The exception reported is: {2}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04087: failure to find schedulable activities for domain "{0}". The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04090: The process domain is unable to read the serialized scope for the instance "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04091: The process domain is unable to read the indexes for the instance "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04092: The process domain is unable to update or insert the indexes for the instance "{0}" into the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04099: The process domain is unable to find instances with root ID "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04100: The process domain is unable to find any invoke messages with the specified where condition in the data source. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source, or the SQL statement has been constructed incorrectly.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04101: The process domain is unable to find any callback messages with the specified where condition in the data source. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source, or the SQL statement has been constructed incorrectly.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04102: The process domain is unable to insert the process event for process "{0}" (revision "{1}") in the data source. The exception reported is: {2}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04103: The process domain is unable to find any process events with the specified where condition in the data source. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source, or the SQL statement has been constructed incorrectly.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04108: The process domain is unable to select the attachment by the key "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04109: The process domain is unable to delete the attachment by the key "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04110: The process domain is unable to insert the attachment into the data source. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04111: The process domain is unable to select the attachment reference "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04112: The process domain is unable to insert the attachment reference into the data source. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04113: The process domain is unable to remove the attachment reference of the instance "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04121: An attempt to fetch the test details using the where condition "{0}" from the data source fails. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the SQL statement has been constructed incorrectly.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04122: The process domain is unable to insert or update test details for the instance "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04123: The process domain is unable to update the state of the following delivery messages "{0}". The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04124: The process domain is unable to update the state of the following delivery subscriptions "{0}". The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04125: The process domain is unable to select the number of detail instances for the master instance specified by the conversation ID "{0}".

Cause: There was a problem accessing the SOA data source, or the SQL statement has been constructed incorrectly.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04126: The process domain is unable to select document references for the instance ID "{0}". The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04127: The process domain is unable to insert document references for the instance ID "{0}". The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04128: The process domain is unable to select document references for delivery message GUID "{0}". The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04129: The process domain is unable to insert document references for delivery message GUID "{0}". The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04132: cannot read CLOB stream from the data source with the key "{0}"; the exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the current transaction settings prohibited this action.

Action: Verify that the machine hosting the data source is physically connected to the network. Additionally verify that the connection pool properties as defined in the application server startup properties are valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04138: The process domain is unable to store the test definition for process "{0}", revision "{1}", test suite "{2}", location "{3}" in the data source. The exception reported is: {4}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04139: The process domain is unable to delete the test definition for the process "{0}", revision "{1}", test suite "{2}", location "{3}" in the data source. The exception reported is: {4}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04140: The process domain is unable to delete test definitions for the process "{0}", revision "{1}" in the data source. The exception reported is: {2}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04141: The process domain is unable to delete the events logged for the process "{0}", revision "{1}" from the data source. The exception reported is: {2}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04142: The process domain is unable to delete the events logged for the domain. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04143: The process domain is unable to insert the fault entry for the activity "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04144: The process domain is unable to update the fault entry for the activity "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04145: The process domain is unable to find the fault entry for the activity "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04146: The process domain is unable to delete the fault entry for the activity "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04147: The process domain was unable to fetch the activity guide instance with key "{0}" from the datastore. The exception reported is: {1}

Cause: There is a problem accessing the SOA datasource.

Action: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04148: The process domain was unable to update the activity guide instance with key "{0}" in the datastore. The exception reported is: {1}

Cause: There is a problem accessing the SOA datasource, or the data segment may be full.

Action: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04149: The process domain was unable to insert the activity guide instance with key "{0}" to the datastore. The exception reported is: {1}

Cause: There is a problem accessing the SOA datasource, or the data segment may be full.

Action: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04150: The process domain was unable to insert the audit counter for instance "{0}". The exception reported is: {1}

Cause: There is a problem accessing the SOA datasource.

Action: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04151: The process domain was unable to update the audit counter for the instance "{0}". The exception reported is: {1}

Cause: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

Action: There is a problem accessing the SOA datasource, or the data segment may be full.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04152: The process domain was unable to select the audit counter for the instance "{0}" from the datastore. The exception reported is: {1}

Cause: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

Action: There is a problem accessing the SOA datasource.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04153: The process domain was unable to select for update on the audit counter for the instance "{0}" from the datastore. The exception reported is: {1}

Cause: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

Action: There is a problem accessing the SOA datasource.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05000: failure to fetch the dispatcher trace for the engine "{0}"; the exception reported is: {1}

Cause: The dispatcher trace XML file was written to an output buffer that was not sized correctly.

Action: Contact Oracle Support Services. Provide the error message and the process that appeared to cause the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-05001: The message handler for the class {0} is not registered.

Cause: This was an internal error. It occurred because the dispatcher message handler was not registered in the MessageRegistry class.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-05002: error while attempting to process the message "{0}"; the reported exception is: {1}

Cause: This error contained an exception thrown by the message handler.

Action: Check the exception trace in the log (with logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05003: No message local handler is implemented for the message "{0}".

Cause: This was an internal error. It occurred when a remote message was handled locally.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-05004: error while sending a batch message to the dispatch queue; the exception reported is: {0}

Cause: There was a problem with enqueuing the message to the JMS queue or the dispatcher EJB could not be found in the JNDI context.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-05005: The process domain is unable to send a message to the JMS queue "{0}". The exception reported is: {1}

Cause: There was a problem with enqueuing the message to the JMS queue; the queue configuration might be incorrect.

Action: Verify that the JMS service for the application server has been configured properly.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05006: error while scheduling a batch message with the dispatcher; the exception reported is: {0}

Cause: There was a problem finding the dispatcher EJB in the current JNDI context.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-05007: there is no active transaction while scheduling a message with the dispatcher

Cause: this usually happens if the underlying subsystem rollback back the transaction without bubbling up the system or transaction exception to the bpel layer

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05213: The process identifier "{0}" for the BPEL process archive "{1}" is not valid.

Cause: The process identifier for the BPEL process archive named in the message was not valid.

Action: Ensure that the deployment descriptor contained in the BPEL process archive named in the error message has a valid process ID. Process identifiers might start with a letter, a dollar sign ($) or an underscore (_); process characters (other than the first character) include a letter, a number, a dollar sign ($), an underscore (_) or a hyphen (-).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05214: The process revision tag "{0}" for the BPEL process archive "{1}" is not valid.

Cause: The process revision tag for the BPEL process archive named in the message was not valid.

Action: Ensure that the deployment descriptor contained in the BPEL process archive named in the error message has a valid revision tag. Valid revision tags may contain the following characters: a letter, a number, a dollar sign ($), an underscore (_), a hyphen (-), or a period (.).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05215: The process domain is encountering the following errors while loading the process "{0}" (composite "{1}"): {2}.

Cause: This error contained an exception thrown by the underlying process loader module.

Action: Check the exception trace in the log (with logging level set to debug mode). If there is a patch installed on the server, verify that the bpelcClasspath domain property includes the patch classes.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05216: The class {0} for the process "{1}" (revision "{2}") does not implement the ICubeProcess interface.

Cause: The current BPEL component named in the error message was probably compiled with an older version of SCAC. All process classes contained within the process domain must implement this interface.

Action: Recompile the SOA composite again.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05217: error while attempting to instantiate the class {0} for the process "{1}" (revision "{2}"); the exception reported was: {3}

Cause: This error contained an exception thrown by the underlying process loader module.

Action: Verify the exception trace in the log (with logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05222: cannot find class for type {0}

Cause: This was an internal error. The persistence manager for the type named in the error message could not be found in the class path. All required persistence managers should be registered by default.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-05225: The persistence manager class {0} for the type {1} does not implement the IPersistenceManager interface.

Cause: This was an internal error. All persistence managers registered with the system must conform to the IPersistenceManager interface.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-05226: error while attempting to instantiate the persistence manager class {0} for type {1}; the exception reported was: {2}

Cause: The persistence manager class named in the error message was not in the system class path or there was an incompatibility with the JDK used to compile the class and the current JVM version.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05243: failure to obtain load lock for process "{0}"; the exception reported is: {1}

Cause: The lock timeout was too small for the current load or there was a large number of process modification requests.

Action: The default timeout is 120 seconds. If this is not sufficient, customize the value using the JVM system property orabpel.process.lock.timeout, which is added to the JVM start line.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05244: failure to obtain load lock for process "{0}"; timed out after {1} seconds.

Cause: The lock timeout was too small for the current load or there was a large number of process modification requests.

Action: The default timeout is 120 seconds. If this is not sufficient, customize the value using the JVM system property orabpel.process.lock.timeout, which is added to the JVM start line.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05250: error while attempting to deploy the BPEL component file "{0}"; the exception reported is: {1}

Cause: This error contained an exception thrown by the underlying deployment module.

Action: Verify the exception trace in the log (with logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05252: The bpel container could not find persistence manager {0} for type {1} in the classpath

Cause: During dehydration the bpel container would serialize all the objects in the scope, each object in the scope should have a persistence manager registered or available in the classpath, otherwise bpel container would not know how to serialize the object for the dehydration store.

Action: Please make sure the persistence manager {0} for type {1} is available in classpath. please refer the documentation on how to write a persistence manager.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05253: Cannot re-deploy a durable process "{0}" with keepInstancesOnRedeploy=true.

Cause: A durable BPEL process cannot be deployed when the flag keepInstancesOnRedeploy is set to "true".

Action: Remove the keepInstancesOnRedeploy flag and try again.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-08015: cannot find operation {0} of portType {1} in the WSDLs of composite "{2}

Cause: In the composite named in the error message, either the WSDL that defined portType named in the error message was changed, or there were multiple definitions of the same portType.

Action: Ensure that there is only one definition of portType named in the error message and redeploy the composite.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09004: cannot convert the object of the class {0} to XML text

Cause: The object of the class named in the error message was not converted to XML text because of the exception: {1}

Action: Ensure that a valid marshaller is registered for the class named in the error message and refer to the BPEL developer guide about how to create a marshaller for a JAVA type.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09006: A mismatch of a schema-generated object version cannot be used in the system.

Cause: Either the XML schema class {0} has been compiled with an older version of SCHEMAC, or the BPEL process domain to which the class is deployed could not use the helper classes that were generated for this class.

Action: Recompile XML schema using the SCHEMAC tool that is bundled with the current process domain.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09007: error while attempting to instantiate the XML marshaller class {0}

Cause: The exception reported was: {1}

Action: Ensure that marshaller is defined, and that it is available in the class path.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09008: error while marshalling the object to XML

Cause: The class {0} did not implement the com.collaxa.cube.engine.xml.IMarshaller interface.

Action: Ensure that the marshaller class {0} implements the correct interface. All XML marshallers used in the BPEL must implement this interface.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09009: The BPEL service engine is not able to instantiate the schema registry.

Cause: The class {0} (for the run-time schema registry) did not implement the ISchemaRegistry interface.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode)
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-09010: error attempting to create the schema registry class {0}

Cause: This is an internal error. The exception reported was: {1}

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode)
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-09200: When performing the assign operation, the to node {0} is invalid.

Cause: The node named in the error message was either null or an empty node set, and it was not an instance of org.w3c.Element.

Action: Verify the node value at line number {1} is not null and is an instance of org.w3c.Element.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09204: The result of from-spec is null.

Cause: Either the from node value or the xpath query in the from node value was invalid.

Action: According to BPEL4WS spec 1.1 section 14.3, the from node value should not be empty. Verify the from node value at line number {0} in the BPEL source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09205: The assign activity of the to node query is returning zero node.

Cause: Either the to node data or the xpath query in the to node was invalid.

Action: According to BPEL4WS spec 1.1 section 14.3, verify the to node value at line number {1} in the BPEL source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09207: There is an error while parsing the xml data.

Cause: The XML data was not valid; the reason was {0}.

Action: Ensure the XML data is valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09219: failure to save the element {0} during dehydration

Cause: This element was not a root element and the scope had reference to this element. The scope should have references only to root element.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-09221: failure to serialize the element {0} to the binary format during dehydration

Cause: The exception reported was: {1}

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode)
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-09222: failure to deserialize the document {0} from binary format during dehydration

Cause: The exception reported was: {1}

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode)
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09223: The assign activity part and query {0} are returning multiple nodes.

Cause: The assign activity part and query named in the error message returned multiple nodes. It should return single node.

Action: According to BPEL4WS specification 1.1 section 14.3, the assign activity part and query named in the error message should not return multiple nodes. Verify the part and xpath query named in the error message at line number {1} in the BPEL source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09224: cannot set a nonelement value to an element-based variable

Cause: An attempt to assign a nonelement value to an element-based variable failed.

Action: Verify the BPEL source for invalid assign activities.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09225: cannot set a nonmessage value to a message-based variable

Cause: An attempt to assign a nonmessage value to a message-based variable failed.

Action: Verify the BPEL source for invalid assign activities.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09226: cannot use a simple type variable in the setVariableData method

Cause: It was not allowed to use simple type variable in setVariableData method.

Action: Verify the BPEL JAVA exec source code for invalid assign activities.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09227: The from-spec for {2} operation must return either an attribute list or an element list.

Cause: The from-spec did not return an attribute list or an element list.

Action: Verify the assign activity for the operation named in the error message at line number {1} in the BPEL source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09228: The message part {2} of the WSDL variable {3} is not an XML element; {4} operation cannot be performed.

Cause: The operation named in the error message was not performed because the named message part of the WSDL variable named in the error message was not an XML element.

Action: Verify the message part named in the error message is a valid XML element at line number {1} in the BPEL source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09229: The to-spec does not yield any data; the {1} operation cannot be performed.

Cause: The operation named in the error message was not performed because to-spec did not yield any data.

Action: Verify the to-spec of the assign activity at line number {0} in the BPEL source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09230: The parent of the selection result {1} does not exist or is not an XML element; the {2} operation cannot be performed.

Cause: The operation named in the error message was not performed because the parent of the selection result named in the error message did not exist or was not an XML element.

Action: Verify the element of the assign activity at line number {0} in the BPEL source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09231: The selection result at list entry {1} does not have a parent node; the {2} operation cannot be performed.

Cause: The operation named in the error message was not performed because the selection result at the list entry named in the error message did not have a parent node.

Action: Verify the list entry of the assign activity at line number {0} in the BPEL source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09232: The selection result at list entry {1} is not an XML node; the {2} operation cannot be performed.

Cause: The operation named in the error message was not performed because the selection result at the list entry named in the error message was not an XML node.

Action: Verify the list entry of the assign activity at line number {0} in the BPEL source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09233: The selection result at list entry {1} is not an XML element; the {2} operation cannot be performed.

Cause: The operation named in the error message was not performed because the selection result at the list entry named in the error message was not an XML element.

Action: Verify the list entry of the assign activity at line number {0} in the BPEL source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09234: The selection result of {1} is not an XML element; the {2} operation cannot be performed.

Cause: The operation named in the error message was not performed because the selection result named in the error message was not an XML element.

Action: Verify the assign activity at line number {0} in the BPEL source and ensure the run-time data is valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09240: failure of the copyList assign operation

Cause: The element list specified by the to-spec used in the copyList operation was not contiguous.

Action: Verify the copyList operation of the assign activity at line number {0} in the BPEL source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09241: The copyList assign operation fails due to a type mismatch.

Cause: The from-list of copyList was element-based, while the to-list was not element-based.

Action: Verify the copyList operation of the assign activity at line number {0} in the BPEL source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09242: The copyList assign operation fails due to a type mismatch.

Cause: The from-list of the copyList operation was attribute-based, but the to-list was not attribute-based.

Action: Verify the copyList operation of the assign activity at line number {0} in the BPEL source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09243: The copyList assign operation fails.

Cause: The element returned from the to-list spec of the copyList operation did not have an element parent.

Action: Verify the copyList operation of the assign activity at line number {0} in the BPEL source and ensure that the run-time to-list data is valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09244: The copyList assign operation fails.

Cause: The element returned from the to-list spec of the copyList operation did not have a parent node.

Action: Verify the copyList operation of the assign activity at line number {0} in the BPEL source and ensure the run-time to-list data is valid
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09245: The copyList assign operation fails.

Cause: The members of the to-list spec of the copyList operation did not share the same parent node.

Action: Verify the copyList operation of the assign activity at line number {0} in the BPEL source and ensure the run-time to-list data is valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09248: cannot instantiate document builder {0}

Cause: The reason was: {1}

Action: Ensure that document builder class named in the error message exists in the class path.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09249: error while parsing the XML text {0}

Cause: The XML text was invalid because {1}.

Action: Verify that the XML text is valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09250: error while creating the XML document

Cause: The reason was {0}.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode)
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-09251: cannot perform copy XMLNS for prefix:{0}

Cause: Namespaces conflicted: {1} and {2}

Action: Verify the from element data of the assign operation.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09500: An error occurs while processing the XPath expression; the expression is {0}.

Cause: The XPath expression failed to execute; the reason was: {1}.

Action: Check the detailed root cause described in the exception message text and verify that the XPath query is correct.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09501: An error occurs while registering the XPath function {0}.

Cause: Registering the XPath function failed; the reason was: {1}.

Action: Check the detailed root cause described in the exception message text and verify that the XPath function named in the error message is defined in the domain property file.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09502: The syntax error occurs while parsing XPath expression {0}, at position {1}.

Cause: The XPath query syntax was wrong; the exception was: {2}

Action: Check the detailed root cause described in the exception message text and verify that the XPath expression named in the error message is correct. The XPath expression is defined in the BPEL process.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09503: an error occurs while parsing XPath expression {0}

Cause: The XPath expression was invalid; the reason was: {1}.

Action: Check the detailed root cause described in the exception message text and verify that the XPath expression named in the error message is correct. The XPath expression is defined in the BPEL process.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09504: The XPath variable or expression {0} is empty at line {1}.

Cause: An attempt to read or copy data referenced or computed by the XPath expression either had invalid data, according to the XML schema, or did not contain certain optional data.

Action: Ensure that the variable or expression result named in the error message is not empty. Enable XML schema validation of related variables to ensure the run-time data is valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09505: The XPath variable or expression {0} is empty at line {1}.

Cause: An attempt to create the missing to data by the XPath expression failed. Attribute ignoreMissingToData does not apply to this expression.

Action: Make sure the expression uses only: PathExpr ::= "/"RelativePathExpr RelativePathExpr ::= ForwardStep (("/") ForwardStep)* ForwardStep ::= (ForwardAxis QName) | AbbrevForwardStep AbbrevForwardStep ::= "@"? QName ForwardAxis ::= ("child" "::") | ("attribute" "::").
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09705: An error occurs while initializing BPEL variable {0}; the schema processor cannot find the element {1} in the following schemas: {2}.

Cause: The XSD element on which the variable was based was not properly defined in XSD or the WSDL.

Action: Ensure that the element named in the error message is valid in the XSD or the WSDL.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09706: An error occurs while initializing BPEL variable {0} at line {1}; the schema processor cannot find type {2} for part {3} in the following schemas: {4}.

Cause: The XSD type on which the variable was based was not properly defined in XSD or the WSDL.

Action: Ensure that the type named in the error message is valid in the WSDL.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09707: cannot initialize variable {0} at line {2}

Cause: The reason was: {1}.

Action: Ensure that the variable named in the error message is valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09717: validation of variable {0} failed

Cause: The reason was: {1}.

Action: Pleasehandle the exception in bpel.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20300: A problem occurs while processing reports data {0}.

Cause: The DataCaptureAgency class reported an exception.

Action: Examine the log file to determine the problem.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20301: The Reporting Data Publisher {0} fails.

Cause: The data publisher reported an exception.

Action: Examine the log file for more details.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20302: A problem occurs while setting up a connection to the JMS destination {0} using the connection factory {1}.

Cause: The JMS configuration was incorrect.

Action: Verify that the JMS configuration is valid.
Level: 1

Type: WARNING

Impact: Programmatic

ORABPEL-20303: An error occurs while publishing report data to the JMS destination {0}.

Cause: The JMS configuration was incorrect.

Action: Verify that the JMS destination is valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20304: The JMS destination lookup fails. The related report data will not be published.

Cause: The JMS configuration was incorrect.

Action: Verify that the JMS destination or JNDI name {0} is valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20305: The JMS connection factory lookup fails. The related report data will not be published.

Cause: The JMS configuration was incorrect.

Action: Verify that JNDI name {0} is valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20306: A problem occurs while releasing the JNDI resources used to publish to the destination {0}.

Cause: The JMS configuration was incorrect.

Action: Verify that JNDI name is correct.
Level: 1

Type: WARNING

Impact: Programmatic

ORABPEL-20307: The custom data publisher class {0} cannot be loaded.

Cause: The custom data publisher class named in the error message was not found.

Action: Verify that the class file and all dependencies can be loaded from the suitcase or from the application class path.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20308: The custom data publisher class {0} cannot be initialized properly.

Cause: An attempt to create the custom data publisher class named in the error message failed.

Action: Examine the log file for a class creation exception.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20309: The sensor cannot be registered because it has no name.

Cause: The sensor name was missing.

Action: Specify the sensor name.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20310: The sensor {0} cannot be registered because a sensor with the same name is already registered.

Cause: The sensor name was a duplicated name.

Action: Specify a unique sensor name.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20311: The sensor-sensor action association for sensor {0}, action {1} cannot be created because no sensor named {2} exists in the registry.

Cause: The sensor name was missing.

Action: Specify a valid sensor name in the association.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20312: The sensor-sensor action association for sensor {0}, action {1} cannot be created because no sensor action named {2} exists in the registry.

Cause: The sensor name was missing.

Action: Register the sensor action before specifying an assocation.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20313: The sensor action cannot be registered because it has no name.

Cause: The sensor name was missing.

Action: Specify the sensor action name.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20314: The sensor action {0} cannot be registered because a sensor action with the same name is already registered.

Cause: The sensor action name was a duplicated name.

Action: Specify a unique sensor action name.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20315: An error occurs while loading sensors and sensor actions for the process {1}, revision {2} in the domain {0}.

Cause: The loading of sensors failed.

Action: Examine the log file for the exception of loading sensors.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20316: No target is specified for sensor {0}.

Cause: The target information was missing.

Action: Specify a target.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20317: The target {1} for sensor {0} is invalid.

Cause: The target information was wrong.

Action: Specify a dollar sign ($) before the variable name and ensure that the variable exists.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20318: The configuration for sensor {0} is missing.

Cause: The sensor configuration was missing.

Action: The variableConfig element must be specified for variable sensors. Complete the variable sensor definition.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20319: The sensor {0} is a variable sensor but has activity or fault configurations defined.

Cause: The sensor configuration was wrong.

Action: Remove the unnecessary configuration elements.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20320: The sensor {0} is a fault sensor but has activity or variable configurations defined.

Cause: The sensor configuration was wrong.

Action: Remove the unnecessary configuration elements.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20321: The configuration for sensor {0} is missing.

Cause: The sensor configuration was missing.

Action: The activityConfig element must be specified for activity sensors. Complete the activity sensor definition.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20322: The sensor {0} is an activity sensor but has variable or fault configurations defined.

Cause: The sensor configuration was wrong.

Action: Remove the unnecessary configuration elements.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20323: The sensor {0} is invalid because {1} is an unrecognized sensor kind.

Cause: The sensor kind was wrong.

Action: Specify a valid sensor kind.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20324: The sensor action {0} is invalid because it publishes to a JMS destination but no destination is specified.

Cause: The JMS destination was missing in the sensor action.

Action: Specify the JMS destination property in the sensor action.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20325: The sensor action {0} is invalid because it publishes to a JMS destination but no connection factory is specified.

Cause: The JMS connection factory information was wrong.

Action: Specify the JMS connection factory.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20326: The sensor action {0} is invalid because it publishes to a custom publisher but no publisher class is specified.

Cause: The custom publisher class name was wrong.

Action: Specify the fully qualified class name of the custom data publisher.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20327: The sensor action {0} is invalid because {1} is an unrecognized publish type.

Cause: The publish type was wrong.

Action: Specify a valid publish type.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20328: The sensor action {0} is invalid because the associated sensor {1} cannot be found.

Cause: The associated sensor named in the error message was missing.

Action: Ensure that sensor names used in the sensor action file match those defined in the sensor file.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20329: The sensor action {0} is invalid because the connection name is not specified.

Cause: The connection name in the sensor action named in the error message was missing.

Action: Specify the connection name property in the sensor action.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20330: The Sensor.xsd schema cannot be loaded from the class path.

Cause: The installation of Sensor.xsd was missing

Action: Ensure that the Sensor.xsd file has not been modified in any way.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20331: The JMS Adapter cannot be loaded from the class path.

Cause: The loading of the JMS adapter failed.

Action: Ensure that the JMS adapter has been properly deployed in the application server.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20501: An error occurs while loading monitor model for the process {1}, revision {2} in the domain {0}.

Cause: The loading of monitor model failed.

Action: Examine the log file for the exception of loading monitor model.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20502: An error occurs while monitor database executing command {1}, for database {0}.

Cause: The monitor database command execution failed.

Action: Examine the log file for the exception of executing a monitor database command.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20503: An error occurs while monitor buisiness indicator evaluates the xpath {0}.

Cause: The monitor business indicator xpath evaluation execution failed.

Action: Examine the log file for the exception of executing a monitor business indicator xpath evaluation.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20504: An error occurs while monitor process activity execution for activity {0} and event {1}.

Cause: The monitor process activity execution failed.

Action: Examine the log file for the exception of executing a monitor process activity.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20505: An error occurs while monitor creates the registry. This error does not interfere in the BPEL process.

Cause: The monitor files are not found or an error occurs while loading the monitor files.

Action: Examine the log file for the exception of creating a monitor registry.
Level: 1

Type: WARNING

Impact: Programmatic

ORABPEL-20506: An error occurs while monitor loads the configuration.

Cause: The monitor config load failed.

Action: Examine the log file for the exception of loading a monitor config.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20507: An error occurs while monitor pubishes data to BAM.

Cause: The monitor BAM publish failed.

Action: Examine the log file for the exception of publishing monitor data to BAM publisher.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20508: An error occurs while monitor get the activity path information.

Cause: The monitor get activity path failed.

Action: Examine the log file for the exception of getting activity path information.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20509: Composite: {0}, Process: {1}, Process Revision: {2}, Business Indicator: {3}, Metric: {4}, Activity: {5}, Evaluation Event: {6}.Skipping evaluation for all metrics in this Business Indicator/Activity/Evaluation Event. No rows will be inserted.

Cause: The XPATH Evaluation of Business Indicator failed.

Action: Check XPath expression in conjunction with process variable state.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20510: Composite: {0}, Process: {1}, Process Revision: {2}, Business Indicator: {3}, Metric: {4}, Activity: {5}, Evaluation Event: {6}.A null value will be inserted for this metric.

Cause: The Metric XPATH Evaluation of Business Indicator failed.

Action: Check Metric XPath expression in conjunction with process variable state.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20511: An attempt to connect BAM failed. Error Message: {0}

Cause: Either BAM adapter credentials are incorrect or SOA/BAM trusted domain configuration is missing.

Action: See "Configuring the Oracle BAM Adapter" in Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite for more information.
Level: 1

Type: ERROR

Impact: Programmatic

74 ORAMED-01001 to ORAMED-09001

ORAMED-01001: Error occurred while assigning to target "{0}" using expression "{1}".

Cause: Error occurred while assigning to target "{0}" using expression "{1}".

Action: Check if source message has right values or source expression is valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01002: Metadata error occurred while assigning. Check if source and target expression are valid. ["{0}"].

Cause: Metadata error occurred while assigning. Check if source and target expression are valid. ["{0}"].

Action: Modify source or target for valid expression. Empty string, null and invalid expressions are not allowed
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01003: Invalid source used while assigning. Check if source expression is valid. ["{0}"].

Cause: Invalid source used while assigning. Check if source expression is valid. ["{0}"].

Action: Modify source for valid expression.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01004: Source evaluated from expression "{0}" is invalid.

Cause: Source evaluated from expression "{0}" is invalid.

Action: Check the expression for correctness. Modify the source expression based on the requirement, or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01005: Target creation for target expression "{0}" failed.

Cause: Target creation for target expression "{0}" failed.

Action: Check if the target expression is valid, otherwise, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01006: Encountered variable which is not supported or implemented "{0}".

Cause: Encountered variable which is not supported or implemented "{0}".

Action: Check if source and target expression for valid variable like $in, $out, $initial and so forth, otherwise Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01007: Header variable "{0}" not recognized.

Cause: Header variable "{0}" not recognized.

Action: Header variable should be of the format $in.header.<prefix>_<root-elem>. Fix the header variable.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01008: Property "{0}" not found in "{1}" message.

Cause: Property "{0}" not found in "{1}" message.

Action: Check source and target expression for valid property name otherwise Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01009: Failed to assign element "{0}" to element "{1}". Parent node not found.

Cause: Failed to assign element "{0}" to element "{1}". Parent node not found.

Action: Check target expression for valid element associated with proper owner document, otherwise Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01010: Failed to assign source "{0}" to target part "{1}". Assigning Text data to part is not supported unless target part is available.

Cause: Failed to assign source "{0}" to target part "{1}". Assigning Text data to part is not supported unless target part is available.

Action: Check source and target expression for valid expression, otherwise Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01011: Failed to assign attachment "{0}" from source to target. Attachment not available in source message.

Cause: Failed to assign attachment "{0}" from source to target. Attachment not available in source message.

Action: Check source expression is valid, otherwise Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01012: Part "{0}" not found in source message.

Cause: Part "{0}" not found in source message.

Action: Check source and target expression for valid part name otherwise Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01101: Error evaluating filter expression.

Cause: Error evaluating filter expression.

Action: Ensure that the filter expression is valid, otherwise Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01102: Error evaluating filter expression, "{0}".

Cause: Error evaluating filter expression, "{0}".

Action: Ensure that the filter expression metadata is valid, otherwise Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01104: Encountered variable which is not supported "{0}".

Cause: Encountered variable which is not supported "{0}".

Action: Check if source has valid variable $in, filter expression is supported only for inbound expression. Otherwise Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01201: Error occurred while transforming payload using "{0}" for target part "{1}".

Cause: Error occurred while transforming payload using "{0}" for target part "{1}".

Action: Review the XSL or source payload. Either the XSL defined does not match with the payload or payload is invalid.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01202: Fatal error occurred while transforming payload using XSL "{0}" for target part "{1}".

Cause: Fatal error occurred while transforming payload using XSL "{0}" for target part "{1}".

Action: Review the XSL for any syntax error.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01203: No part exists with name "{0}" in source message.

Cause: No part exists with name "{0}" in source message.

Action: Review the transformation definition in mplan. Contact Oracle Support Services if the error cannot be fixed.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01204: Initial source message is not available in the context. Failed evaluating "{0}".

Cause: Initial source message is not available in the context. Failed evaluating "{0}".

Action: Review the transformation/assign definition in mplan. Accessing initial source message is not supported during callback.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01205: Failed to persist streaming attachment for message "{0}".

Cause: Failed to persist streaming attachment for message "{0}".

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01301: Schematron validation fails with error "{0}".

Cause: Schematron validation fails with error "{0}".

Action: Fix the payload.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01302: Response payload for operation "{0}" is invalid.

Cause: Response payload for operation "{0}" is invalid.

Action: Response received by Mediator was either invalid or null. Examine why the service being invoked by Mediator is returning a null/invalid response. You can also try invoking the service directly and see if it sends back proper response.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01303: XSD schema validation fails with error "{0}".

Cause: XSD schema validation fails with error "{0}".

Action: Fix payload and resubmit.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01304: Schematron validation failure.

Cause: Schematron validation failure.

Action: Fix payload or schematron definition and resubmit.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01305: Group ID validation failure.

Cause: Group ID validation failure.

Action: XPATH Expression returned null Group Id. Check the XPATH expression, fix the payload and resubmit.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01306: Sequence ID validation failure."{0}".

Cause: Sequence ID validation failure."{0}".

Action: SequenceID value is incorrect. Either XPATh Expression returned null or sequenceID value does not fall within the sequence range. Check the XPATH expression, fix the payload and resubmit.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01351: Unable to execute "{0}" method on callout instance of "{1}".

Cause: Unable to execute "{0}" method on callout instance of "{1}".

Action: Check server log for any exceptions. Check if there is an issue in implementation of Java callout class.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01360: Wrong source message type. Neither a NormalizedMessage nor a BusinessEvent, message type class :{1}

Cause: Wrong source message type. Neither a NormalizedMessage nor a BusinessEvent, message type class :{1}

Action: Contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01361: Mediator does not support the Resequencing strategy."{0}"

Cause: Mediator does not support the Resequencing strategy."{0}"

Action: Mediator does not support the Resequencing strategy. Refer to the documentation of resequencer for more details.You can also contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01362: Unexpected runtime error occurred while processing the message.

Cause: Unexpected runtime error occurred while processing the message.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01363: Mediator does not have content to respond to the request-response type operation operation "{0}".

Cause: Mediator does not have content to respond to the request-response type operation operation "{0}".

Action: Examine your design to rectify, or reset the property oracle.soa.mediator.twoway.allowNullReply to true.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01364: Group cannot be unlocked as it is not in error state "{0}".

Cause: Group cannot be unlocked as it is not in error state "{0}".

Action: Group cannot be unlocked as it is not in error state
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01365: Group cannot be unlocked as it is an invalid group id "{0}".

Cause: Group cannot be unlocked as it is an invalid group id "{0}".

Action: Provide valid group id
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02001: This error occurs because of invalid filter expression "{0}".

Cause: This error occurs because of invalid filter expression "{0}".

Action: Review the filter expression and check for possible syntax errors in the filter expression.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02002: Invalid filter metadata "{0}". Either no filter expression specified or expression may be invalid.

Cause: Invalid filter metadata "{0}". Either no filter expression specified or expression may be invalid.

Action: Fix the filter condition metadata.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02051: Invalid callout implementation "{0}".

Cause: Invalid callout implementation "{0}".

Action: Fix the callout implementation.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02101: Cannot load XSL transform into the cache for XSL or XSLT "{0}".

Cause: Cannot load XSL transform into the cache for XSL or XSLT "{0}".

Action: Check XSL file for any syntax error and fix the same.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02102: Invalid part type "{0}".

Cause: Invalid part type "{0}".

Action: Ensure that the parts provided in transformation/xpath are valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02103: Invalid assign expression "{0}".

Cause: Invalid assign expression "{0}".

Action: Check assign xpath expression for any syntax error. If there are any syntax errors, correct the xpath expression.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02201: Could not load schema document into the cache for XSD "{0}". Reason : {1}

Cause: Could not load schema document into the cache for XSD "{0}". Reason : {1}

Action: Check the XSD schema for any syntax error and fix the same.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02202: Invalid part name in metadata for schematron validator "{0}".

Cause: Invalid part name in metadata for schematron validator "{0}".

Action: Fix the schematron metadata.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02203: Could not load schematron file {0}.

Cause: Could not load schematron file {0}.

Action: Provide the correct schematron document.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02204: Could not load wsdl interface for message with component dn "{0}".

Cause: Could not load wsdl interface for message with component dn "{0}".

Action: Fix the component to point to valid wsdl.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02205: Schematron document for schematron file {0} is invalid.

Cause: Schematron document for schematron file {0} is invalid.

Action: Fix the schematron document.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02206: Could not create XSD validator for schema with target namespace "{0}" for message "{1}".

Cause: Could not create XSD validator for schema with target namespace "{0}" for message "{1}".

Action: Check XML schema for any syntax error.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02207: Failed to validate redeployment of mediator.

Cause: Failed to validate redeployment of mediator.

Action: Configure composite properly, otherwise contact Oracle for support.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02208: Component is not valid. Either component/componentDN is null or there is a mismatch between "{0}" and "{1}"

Cause: Component is not valid. Either component/componentDN is null or there is a mismatch between "{0}" and "{1}"

Action: Configure composite properly, otherwise contact Oracle for support.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02209: Failed to fetch mediator from source URI "{0}".

Cause: Failed to fetch mediator from source URI "{0}".

Action: Configure composite properly.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02301: Could not load mediator mplan information. Reason : {0}

Cause: Could not load mediator mplan information. Reason : {0}

Action: Check your mediator mplan for any syntax error.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02302: Could not load metadata manager. Reason : {0}.

Cause: Could not load metadata manager. Reason : {0}.

Action: Check your composite configuration.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02303: Composite reference {0} not found for operation {1}.

Cause: Composite reference {0} not found for operation {1}.

Action: Check your composite.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02304: Could not load mediator mplan for componentDN "{0}" . It may be undeployed.

Cause: Could not load mediator mplan for componentDN "{0}" . It may be undeployed.

Action: Using SOA Enterprise Manager, check if composite is deployed. If the composite is not deployed, you can try deploying the composite again.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02305: Could not find mediator case for case name "{0}" . Mediator component may be redeployed with different case names.

Cause: Could not find mediator case for case name "{0}" . Mediator component may be redeployed with different case names.

Action: This message will be put in error state. Fix the mplan by adding the right case and then recover it through EM.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02401: Got invalid response from decision service : {0}

Cause: Got invalid response from decision service : {0}

Action: Ensure that the decision service used by the mediator is configured properly.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02402: Could not invoke decision service : {0}

Cause: Could not invoke decision service : {0}

Action: Ensure that the decision service used by the mediator is configured properly.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02403: Dynamic mplan returned by decision service is invalid. Mplan returned by decision service : {0}

Cause: Dynamic mplan returned by decision service is invalid. Mplan returned by decision service : {0}

Action: Ensure that the decision service used by the mediator is configured properly.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03001: Unable to lock Resequencer Groups for container ID "{0}" and timestamp "{1}".

Cause: Unable to lock Resequencer Groups for container ID "{0}" and timestamp "{1}".

Action: Unable to lock Resequencer Groups. Check your database connection.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03002: Unable to retrieve locked Resequencer Groups for containerId "{0}" and timestamp "{1}".

Cause: Unable to retrieve locked Resequencer Groups for containerId "{0}" and timestamp "{1}".

Action: Unable to retrieve lock Resequencer Groups. Check your database connection.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03003: Unable to store Resequencer Group."{0}".

Cause: Unable to store Resequencer Group."{0}".

Action: Unable to store Resequencer Group. Check your database connection or check data.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03004: Unable to store Resequencer Message."{0}"

Cause: Unable to store Resequencer Message."{0}"

Action: Unable to store Resequencer Message. Check your database connection or check data.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03005: Unable to unlock Resequencer Groups for container ID "{0}" and timestamp "{1}".

Cause: Unable to unlock Resequencer Groups for container ID "{0}" and timestamp "{1}".

Action: Unable to unlock Resequencer Groups. Check your database connection.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03006: Unable to retrieve Resequencer message. "{0}"

Cause: Unable to retrieve Resequencer message. "{0}"

Action: Unable to retrieve Resequencer message. Check your database connection.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03101: Unable to get subscriptions for message "{0}"

Cause: Unable to get subscriptions for message "{0}"

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03102: Error creating cache for cache policy "{0}". Reason : {1}

Cause: Error creating cache for cache policy "{0}". Reason : {1}

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03103: Cannot load Cache entry with NULL or EMPTY key.

Cause: Cannot load Cache entry with NULL or EMPTY key.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03104: Do not cache RuntimeESBSystem object for NULL or EMPTY system GUID.

Cause: Do not cache RuntimeESBSystem object for NULL or EMPTY system GUID.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03105: Could not read WSDL Definition for WSDL with NULL or EMPTY file name.

Cause: Could not read WSDL Definition for WSDL with NULL or EMPTY file name.

Action: The WSDL file being read is not available or reachable. Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03106: Do not cache WSDL Definition for NULL or EMPTY WSDL file name.

Cause: Do not cache WSDL Definition for NULL or EMPTY WSDL file name.

Action: The WSDL file being read is not available or reachable. Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03107: Could not read Schema Document for XSD with NULL or EMPTY file name.

Cause: Could not read Schema Document for XSD with NULL or EMPTY file name.

Action: The XSD schema file being read is not available or reachable. Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03108: Do not cache Schema Document for NULL or EMPTY XSD file name.

Cause: Do not cache Schema Document for NULL or EMPTY XSD file name.

Action: The XSD schema file being read is not available or reachable. Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03109: Could not read parsed filter expression for NULL or EMPTY expression.

Cause: Could not read parsed filter expression for NULL or EMPTY expression.

Action: The filter expression is null or empty. Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03110: Information to process an incoming callback message is not available.

Cause: Information to process an incoming callback message is not available.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03201: Retry of deferred message failed.

Cause: Retry of deferred message failed.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03202: Retry of callback message failed.

Cause: Retry of callback message failed.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03203: Retry of timeout message failed.

Cause: Retry of timeout message failed.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03301: Unexpected exception in case execution "{0}".

Cause: Unexpected exception in case execution "{0}".

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03302: Unexpected exception in one-way operation "{0}" on reference "{1}".

Cause: Unexpected exception in one-way operation "{0}" on reference "{1}".

Action: Check whether the reference service is properly configured and running or look at exception for analyzing the reason or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03303: Unexpected exception in request response operation "{0}" on reference "{1}".

Cause: Unexpected exception in request response operation "{0}" on reference "{1}".

Action: Check whether the reference service is properly configured and running or look at exception for analyzing the reason or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03304: Unexpected exception in asynchronized request execution "{0}".

Cause: Unexpected exception in asynchronized request execution "{0}".

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03401: Context lookup failed "{0}".

Cause: Context lookup failed "{0}".

Action: Ensure that the topic is mapped to a JNDI tree.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03402: Error creating "{0}".

Cause: Error creating "{0}".

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03403: Subscriber does not exist for system "{0}".

Cause: Subscriber does not exist for system "{0}".

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03405: Error converting field "{0}".

Cause: Error converting field "{0}".

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03406: Publisher does not exist for system "{0}".

Cause: Publisher does not exist for system "{0}".

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03408: Unable to store deferred message "{0}".

Cause: Unable to store deferred message "{0}".

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03409: Invalid, premature, or already-handled callback message. No correlation found for message with conversation ID "{0}".

Cause: Invalid, premature, or already-handled callback message. No correlation found for message with conversation ID "{0}".

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03501: Unable to start transaction; transaction status is "{0}".

Cause: Unable to start transaction; transaction status is "{0}".

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03502: Unable to resume transaction.

Cause: Unable to resume transaction.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03503: Unable to commit transaction. Transaction has been rolled back.

Cause: Unable to commit transaction. Transaction has been rolled back.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03504: Unable to rollback transaction.

Cause: Unable to rollback transaction.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03505: "{0}" object not found in JNDI tree.

Cause: "{0}" object not found in JNDI tree.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03506: Unable to get transaction status.

Cause: Unable to get transaction status.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03507: Unable to set rollback only for transaction; transaction status is "{0}".

Cause: Unable to set rollback only for transaction; transaction status is "{0}".

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03508: One of the routing rule execution resulted in a transaction rollback.

Cause: One of the routing rule execution resulted in a transaction rollback.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03509: Unable to suspend transaction.

Cause: Unable to suspend transaction.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03510: Error obtaining Transaction Manager.

Cause: Error obtaining Transaction Manager.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03511: "{0}" object not found in jndi tree

Cause: "{0}" object not found in jndi tree

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03601: Unable to create transformer. It could be because of transformation file or configuration issues. Reason : "{0}"

Cause: Unable to create transformer. It could be because of transformation file or configuration issues. Reason : "{0}"

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03602: Unable to create document.

Cause: Unable to create document.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03603: Unable to register base function "{0}" for "{1}".

Cause: Unable to register base function "{0}" for "{1}".

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03604: Unable to stream xslt results into temp file "{0}"

Cause: Unable to stream xslt results into temp file "{0}"

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03651: Unable to create callout instance for "{0}".

Cause: Unable to create callout instance for "{0}".

Action: Ensure that your callout configuration is correct. Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03652: Unable to execute "{0}" method on callout instance of "{1}".

Cause: Unable to execute "{0}" method on callout instance of "{1}".

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03701: Unable to configure xpath transformer.

Cause: Unable to configure xpath transformer.

Action: Check log file for any exceptions to fix the configuration otherwise contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03801: Unable to initialize filter/validator. "{0}" is not supported.

Cause: Unable to initialize filter/validator. "{0}" is not supported.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03802: Unable to create initial context.

Cause: Unable to create initial context.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03803: Unable to initialize Container ID Manager.

Cause: Unable to initialize Container ID Manager.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04001: Error executing service due to server down "{0}". Reason : {1}

Cause: Error executing service due to server down "{0}". Reason : {1}

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04002: Error executing service due to server down "{0}". Reason : {1}

Cause: Error executing service due to server down "{0}". Reason : {1}

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04004: Error persisting resequencer message,"{0}" , due to internal Error.. Reason : {1}

Cause: Error persisting resequencer message,"{0}" , due to internal Error.. Reason : {1}

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04101: Error receiving DB message.

Cause: Error receiving DB message.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04102: Error publishing DB message.

Cause: Error publishing DB message.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-09001: Parameter name contains "{0}" qname "{1}".

Cause: Parameter name contains "{0}" qname "{1}".

Action: Verify Name-Value parameters to be of the form 'name1=value1 name2=value2' with value not having any spaces.
Level: 1

Type: ERROR

Impact: Programmatic

75 OSSOIAP-90001 to OSSOIAP-90005

OSSOIAP-90001: The Identity Asserter received an unknown token type "{0}". Expected: "{1}"

Cause: Incorrect token type.

Action: Contact your Oracle single sign-on administrator to ensure that Proxy-Remote-User is the active token type.
Level: 1

Type: ERROR

Impact: Configuration

OSSOIAP-90002: The Identity Asserter received an unknown token class "{0}". Expected: a byte array

Cause: Incorrect token class.

Action: Contact your Oracle single sign-on administrator with exception/error information.
Level: 1

Type: ERROR

Impact: Internal Error

OSSOIAP-90003: The Identity Asserter received an empty token byte array.

Cause: Incorrect token conversion.

Action: Contact your Oracle single sign-on administrator with exception/error information.
Level: 1

Type: ERROR

Impact: Internal Error

OSSOIAP-90004: The Identity Asserter received an empty username.

Cause: System Error.

Action: Contact your Oracle single sign-on administrator with exception/error information.
Level: 1

Type: ERROR

Impact: Internal Error

OSSOIAP-90005: The Identity Asserter received an unrecognized callback.

Cause: The Identity Asserter received an unsupported callback.

Action: Contact your Oracle single sign-on administrator with exception/error information.
Level: 1

Type: ERROR

Impact: Internal Error

76 OVD-00001 to OVD-80015

OVD-00001: Transmission to {0} interrupted.

Cause: Could Not Send Response on connection.

Action: Possible network issue or Client disconnected.
Level: 1

Type: TRACE

Impact: Network

OVD-00002: Access denied for user {0} to add entry {1}.

Cause: Access Control List checking Plug-in denied adding entry.

Action: Check the Access Control policies to see if the add should be allowed or not.
Level: 1

Type: TRACE

Impact: Security

OVD-00003: Access denied for user {0} to create entry {1}.

Cause: Access Control List checking Plug-in denied creating a new entry.

Action: Check the Access Control policies to see if the operation should be allowed or not.
Level: 1

Type: TRACE

Impact: Security

OVD-00004: Access denied for user {0} to delete entry {1}.

Cause: Access Control List checking Plug-in denied deleting a new entry.

Action: Check the Access Control policies to see if the operation should be allowed or not.
Level: 1

Type: TRACE

Impact: Other

OVD-00005: Access denied for user {0} to add attribute {2} in entry {1}.

Cause: Access Control List checking Plug-in denied modify the attribute value.

Action: Check the Access Control policies to see if the operation should be allowed or not.
Level: 1

Type: TRACE

Impact: Other

OVD-00006: Access denied for user {0} to delete attribute {2} in entry {1}.

Cause: Access Control List checking Plug-in denied deleting the attribute value.

Action: Check the Access Control policies to see if the operation should be allowed or not.
Level: 1

Type: TRACE

Impact: Other

OVD-00007: Access denied for user {0} to replace attribute {2} in entry {1}.

Cause: Access Control List checking Plug-in denied replacing the attribute value.

Action: Check the Access Control policies to see if the operation should be allowed or not.
Level: 1

Type: TRACE

Impact: Other

OVD-00008: Bind: Selected (Adapter#{0} [Priority : {1}]) backend for: {2}.

Cause: Routing Plugin select the adapter for connecting to backend servers.

Action: Verify if the adapter selected is the right adapter else check adapter configuration.
Level: 1

Type: TRACE

Impact: Other

OVD-00009: Selected the following adapter to connect to backend servers.

Cause: Routing Plugin select the adapter for connecting to backend servers.

Action: Verify if the adapter selected is the right adapter else check adapter configuration.
Level: 1

Type: TRACE

Impact: Other

OVD-00010: Access denied for user {0} to rename DN {1} to {2}.

Cause: Insufficient access to perform RENAME operation.

Action: Ensure Access control configuration is correct.
Level: 1

Type: TRACE

Impact: Other

OVD-00011: {0} DATABASE Adapter Search using: BindDN: {1} Base:{2} Scope:{3} Attributes:{4} Filter:{5}

Cause: Identifies the database adapter picked up with the search parameters specified.

Action: Verify if the DB adapter configuration is correct.
Level: 1

Type: TRACE

Impact: Other

OVD-00345: Error closing database connection: {0}.

Cause: Could not release connection due to database access error.

Action: Check Oracle Virtual Directory server logs for more details.
Level: 1

Type: TRACE

Impact: Other

OVD-01000: Failure in loading configuration from Oracle Virtual Directory server.

Cause: The Oracle Virtual Directory server might be down.

Action: Possible network issue or server down.
Level: 1

Type: ERROR

Impact: Configuration

OVD-01001: Failure in saving configuration to Oracle Virtual Directory server.

Cause: The Oracle Virtual Directory server might be down.

Action: Possible network issue or server down.
Level: 1

Type: ERROR

Impact: Configuration

OVD-01002: Failure in registering children Proxy MBean.

Cause: Check the error message for the cause.

Action: Make sure AdminServer is running properly.
Level: 1

Type: ERROR

Impact: Configuration

OVD-01003: Failure in opening file: {0}

Cause: File does not exist.

Action: Check if the file exists. If not, check AdminServer log for possible causes
Level: 1

Type: ERROR

Impact: Configuration

OVD-01004: Failure in retrieving credential from file-based CSF.

Cause: Possible corrupt CSF wallet file.

Action: Sync the CSF wallet file from Oracle Virtual Directory component to AdminServer.
Level: 1

Type: ERROR

Impact: Configuration

OVD-01005: Failure in retrieving credential from JPS.

Cause: Possible corrupt CSF service.

Action: Make sure CSF service is ok.
Level: 1

Type: ERROR

Impact: Configuration

OVD-01006: Failure in setting credential into WebLogic Server CSF.

Cause: Possible corrupt CSF service.

Action: Make sure CSF service is ok.
Level: 1

Type: ERROR

Impact: Configuration

OVD-01007: Failure in loading the Oracle Virtual Directory credential from wallet file into WebLogic Server CSF.

Cause: Possible corrupt CSF service.

Action: Make sure CSF service is ok.
Level: 1

Type: ERROR

Impact: Configuration

OVD-01008: The IP Address: {0} is invalid.

Cause: Invalid IP Address value or format.

Action: Provide a valid IP Address.
Level: 1

Type: ERROR

Impact: Configuration

OVD-01009: Failure in saving listener config XML.

Cause: The Oracle Virtual Directory server might be down.

Action: Possible network issue or server down.
Level: 1

Type: ERROR

Impact: Configuration

OVD-01010: Failure in registering children listener proxy MBean.

Cause: Check the error message for the cause.

Action: Make sure AdminServer is running properly.
Level: 1

Type: ERROR

Impact: Configuration

OVD-01011: Failure in deregistering children listener proxy MBean.

Cause: Check the error message for the cause.

Action: Make sure AdminServer is running properly.
Level: 1

Type: ERROR

Impact: Configuration

OVD-01012: Failure in getting listener configuration name.

Cause: Check the error message for the cause.

Action: Make sure AdminServer is running properly.
Level: 1

Type: ERROR

Impact: Configuration

OVD-01013: Invalid parameters to create a new listener configuration.

Cause: The key count and value count does not match.

Action: Input matched key/value pairs.
Level: 1

Type: ERROR

Impact: Configuration

OVD-01014: Missing parameters to create a new listener configuration.

Cause: Parameter id is missing for the listener to be created.

Action: Specify a unique listener id.
Level: 1

Type: ERROR

Impact: Configuration

OVD-01015: Invalid id value.

Cause: Check the error message for the cause.

Action: Provide valid id value.
Level: 1

Type: ERROR

Impact: Configuration

OVD-01016: Failure in building the listener MBean ObjectName.

Cause: Check the error message for the cause.

Action: Input proper parameters for MBean ObjectName to be constructed.
Level: 1

Type: ERROR

Impact: Configuration

OVD-01017: Invalid id value.

Cause: Specified id is already used by existing listener.

Action: Specify a unique listener id.
Level: 1

Type: ERROR

Impact: Configuration

OVD-01018: Missing parameters to create a new listener configuration.

Cause: Port number is missing for the new listener.

Action: Specify a free port.
Level: 1

Type: ERROR

Impact: Configuration

OVD-01019: Not allowed to create an admin port.

Cause: You are trying to create new admin port.

Action: No action.
Level: 1

Type: ERROR

Impact: Configuration

OVD-01020: Failure in creating the new listener.

Cause: Check the error message for the cause.

Action: Fix the mistakes according to the error message.
Level: 1

Type: ERROR

Impact: Configuration

OVD-01021: Not allowed to delete or disable the admin port or "LDAP SSL Endpoint".

Cause: You are trying to delete or disable the admin port or "LDAP SSL Endpoint".

Action: No action.
Level: 1

Type: ERROR

Impact: Configuration

OVD-01022: Failure in setting port in listener config.

Cause: Check the error message for the cause.

Action: Fix the issue reported in the error message.
Level: 1

Type: ERROR

Impact: Configuration

OVD-01023: Invalid host name: {0}.

Cause: Invalid host name.

Action: Input a valid host name or IP Address.
Level: 1

Type: ERROR

Impact: Configuration

OVD-01024: Invalid port number: {0}.

Cause: Invalid port number.

Action: Input a valid port number.
Level: 1

Type: ERROR

Impact: Configuration

OVD-01025: Port number {0} is already in use.

Cause: The port number is used by other ports.

Action: Input a free port.
Level: 1

Type: ERROR

Impact: Configuration

OVD-01026: The value {0} contains one or more invalid special characters as in list: "{1}".

Cause: The input value contains invalid characters.

Action: Input a new value without any special characters.
Level: 1

Type: ERROR

Impact: Configuration

OVD-01027: Invalid logger name: {0}.

Cause: The logger name is already in use.

Action: Specify a unique logger name.
Level: 1

Type: ERROR

Impact: Configuration

OVD-01028: Invalid logger name: {0}.

Cause: The logger is not defined.

Action: Specify an existing logger.
Level: 1

Type: ERROR

Impact: Configuration

OVD-01029: Handler {0} is being used by Logger {1}.

Cause: The Handler is used.

Action: Do not remove a handler that is in use.
Level: 1

Type: ERROR

Impact: Configuration

OVD-01030: Unknown listener type.

Cause: The listener type is inknown.

Action: Using LDAP or HTTP as the listener type.
Level: 1

Type: ERROR

Impact: Configuration

OVD-01031: Invalid handler name {0}.

Cause: The handler is not defined.

Action: Use an existing handler.
Level: 1

Type: ERROR

Impact: Configuration

OVD-01032: Invalid hanler name {0}.

Cause: The handler name is already in use.

Action: Specify a unique handler name.
Level: 1

Type: ERROR

Impact: Configuration

OVD-01033: Logger {0} not defined.

Cause: Encountered an unexisting logger.

Action: Reload the configuration then retry.
Level: 1

Type: ERROR

Impact: Configuration

OVD-01034: Missing property name.

Cause: The property name is not defined.

Action: Input a property name.
Level: 1

Type: ERROR

Impact: Configuration

OVD-01035: Missing input handler object.

Cause: Handler object to be validated is missing.

Action: Input the handler object to be validated.
Level: 1

Type: ERROR

Impact: Configuration

OVD-01036: Missing handler name.

Cause: Handler name is missing from the handler object.

Action: A handler object must have a unique handler name.
Level: 1

Type: ERROR

Impact: Configuration

OVD-01037: Missing handler classname.

Cause: Handler classname is missing from the handler object.

Action: A classname must be specified for a handler object.
Level: 1

Type: ERROR

Impact: Configuration

OVD-01038: Missing input logger object.

Cause: Logger object to be validated is missing.

Action: Input the logger object to be validated.
Level: 1

Type: ERROR

Impact: Configuration

OVD-01039: Missing logger name.

Cause: Logger name is missing from the logger object.

Action: A logger object must have a unique logger name.
Level: 1

Type: ERROR

Impact: Configuration

OVD-01040: Missing logger name.

Cause: Did not input a logger name.

Action: Input a logger name.
Level: 1

Type: ERROR

Impact: Configuration

OVD-01041: Missing handler name.

Cause: Did not input a handler name.

Action: Input a handler name.
Level: 1

Type: ERROR

Impact: Configuration

OVD-01042: Invalid level: {0}.

Cause: The level value is invalid.

Action: Provide a valid logging level.
Level: 1

Type: ERROR

Impact: Configuration

OVD-01043: Logger {0} already has handler {1}.

Cause: The handler is already used in the logger.

Action: Do not add the same handler to a logger more than once.
Level: 1

Type: ERROR

Impact: Configuration

OVD-01044: Logger {0} does not have handler {1}.

Cause: The handler is not used by the logger.

Action: Do not remove a handler from a logger which does not use it.
Level: 1

Type: ERROR

Impact: Configuration

OVD-01045: Invalid handler attribute name: {0}.

Cause: The attribute name is invalid.

Action: Specify a valid attribute name.
Level: 1

Type: ERROR

Impact: Configuration

OVD-01046: Not allowed to change SSL authentication type for "LDAP SSL Endpoint" port.

Cause: You are trying to change SSL authentication type for "LDAP SSL Endpoint" port.

Action: No action.
Level: 1

Type: ERROR

Impact: Configuration

OVD-01047: Not allowed to disable SSL for "LDAP SSL Endpoint" port.

Cause: You are trying to disable SSL for "LDAP SSL Endpoint" port.

Action: No action.
Level: 1

Type: ERROR

Impact: Configuration

OVD-01048: Failed to add schema location: {0}

Cause: MBean might be out-of-sync with server configuration file.

Action: Reload the MBean Configuration and try again.
Level: 1

Type: ERROR

Impact: Configuration

OVD-02000: Failure in unsetting keystore/truststore for non-ssl port.

Cause: Check log message for the possible cause.

Action: No action.
Level: 1

Type: WARNING

Impact: Configuration

OVD-02001: Failure in updating port-in-use list when adding a new listener.

Cause: Check the log message for the possible cause.

Action: Delete the newly created listener and add it again.
Level: 1

Type: WARNING

Impact: Configuration

OVD-02002: Listener {0} to be deleted does not exist.

Cause: Trying to deleting an unexist listener.

Action: Input the correct listener id to be deleted.
Level: 1

Type: WARNING

Impact: Configuration

OVD-02003: Failure in updating port-in-use list when deleting listener {0}.

Cause: Check the log message for the possible cause.

Action: Do not use the port number again when creating new listener.
Level: 1

Type: WARNING

Impact: Configuration

OVD-20009: {0} Processing Outstanding Transactions.

Cause: Multiple transactions were being processed.

Action: Information only, and no further action required.
Level: 1

Type: NOTIFICATION

Impact: Other

OVD-20010: {0} Initializing Memory Indices

Cause: Setting Local Store Adapter transaction log size.

Action: Information only, and no further action required.
Level: 1

Type: NOTIFICATION

Impact: Other

OVD-20022: Failure in adding entry:{0}.

Cause: Failed to find target adapter for ADD operation.

Action: Verify that the DN of entry to be added is correct
Level: 1

Type: NOTIFICATION

Impact: Other

OVD-20023: Attempted BIND has multiple target adapters (selecting#{0}): {1}.

Cause: Multiple adapters qualify for bind operation.

Action: Ensure the routing configuration for all enabled adapaters are correct.
Level: 1

Type: NOTIFICATION

Impact: Other

OVD-20024: Failure in performing bind using subject DN :{0}.

Cause: Failed to find target adapter for BIND operation.

Action: Verify that the subject DN of BIND operation is correct.
Level: 1

Type: NOTIFICATION

Impact: Other

OVD-20025: Attempted DELETE has multiple target adapters (trying adapter#{0}): {1}.

Cause: Multiple adapters qualify for DELETE operation.

Action: Ensure routing configuration for all adapters is correct.
Level: 1

Type: NOTIFICATION

Impact: Other

OVD-20026: Failure in performing DELETE operation on DN:{0}.

Cause: Failed to find target adapter for DELETE operation.

Action: Verify that the DN of the entry to be deleted is correct.
Level: 1

Type: NOTIFICATION

Impact: Other

OVD-20027: Failure in retrieving entry for DN :{0}.

Cause: Multiple target adapters qualify for the specified DN.

Action: Ensure routing configuration of all adapters is correct.
Level: 1

Type: NOTIFICATION

Impact: Other

OVD-20028: Failure in retrieving entry for DN :{0}.

Cause: An attempt to find a target adapter has failed.

Action: Ensure that the DN of the entry to be retrieved is correct.
Level: 1

Type: NOTIFICATION

Impact: Other

OVD-20029: Attempted MODIFY has multiple target adapters (selecting#{0}): {1}.

Cause: Multiple target adapters qualify for the MODIFY operation.

Action: Ensure routing configuration of all adapters is correct.
Level: 1

Type: NOTIFICATION

Impact: Other

OVD-20030: Failure in performing MODIFY operation on DN :{0}.

Cause: Failed to find a target adapter for MODIFY operation.

Action: Ensure that the DN of entry to be modified is correct.
Level: 1

Type: NOTIFICATION

Impact: Other

OVD-20031: Attempted RENAME has multiple SOURCE target adapters (selecting #{0}): {1}.

Cause: Multiple source or target adapters qualify for RENAME operation.

Action: Ensure that the routing configuration of all adapters is correct.
Level: 1

Type: NOTIFICATION

Impact: Other

OVD-20032: Failure in performing RENAME operation for DN:{0}.

Cause: An attempt to find soure or target adapter has failed.

Action: Ensure that the source and target DN of the entry to be renamed is correct.
Level: 1

Type: NOTIFICATION

Impact: Other

OVD-20033: Attempted RENAME has multiple DESTINATION target adapters(selecting#{0}): {1}.

Cause: Multiple target adapters qualify for the new DN.

Action: Ensure that the routing configuration of all adapters is correct.
Level: 1

Type: NOTIFICATION

Impact: Other

OVD-20034: Failure in performing RENAME operation on DN:{0}.

Cause: An attempt to find target adapter for new DN has failed.

Action: Ensure that the target DN of the entry to be renamed is correct.
Level: 1

Type: NOTIFICATION

Impact: Other

OVD-20035: {0} Local Store adapter set to READ ONLY.

Cause: Tried to modify read-only Local Store Adapter.

Action: Modifying a read-only Local Store Adapter is not allowed.
Level: 1

Type: NOTIFICATION

Impact: Other

OVD-20058: Invalid target adapter ({0}) while attempting to retrieve:{1}.

Cause: An attempt to lookup target adapter has failed.

Action: Ensure that the DN of entry to be retrieved is correct.
Level: 1

Type: NOTIFICATION

Impact: Other

OVD-20060: Invalid target adapter ({0}) while attempting to rename:{1}.

Cause: Failed to lookup target adapter for RENAME operation.

Action: Ensure that the new DN of the entry to be renamed is correct.
Level: 1

Type: NOTIFICATION

Impact: Other

OVD-20061: Old Database Format Detected: Upgrading.

Cause: Encountered data files in old database format.

Action: Contact Oracle Virtual Directory administrator.
Level: 1

Type: NOTIFICATION

Impact: Other

OVD-20062: Datafile Compaction Disabled -- Skipped.

Cause: Data file is not being compacted.

Action: Information only, and no further action required.
Level: 1

Type: NOTIFICATION

Impact: Other

OVD-20063: Compacting Datafile:{0}

Cause: Data file is being compacted.

Action: Information only, and no further action required.
Level: 1

Type: NOTIFICATION

Impact: Other

OVD-20066: Upgrade Completed:{0}

Cause: Upgrade operation completed.

Action: Information only, no further action required.
Level: 1

Type: NOTIFICATION

Impact: Other

OVD-40001: {0} Entry with DN {1} missing RDN attribute: {2}

Cause: LDAP entry was missing RDN attribute and value

Action: Ensure that specified entry contains RDN attribute and value.
Level: 1

Type: WARNING

Impact: Other

OVD-40003: Error Initializing SSL:{0}

Cause: SSL Configuration errors

Action: Check the SSL configuration and retry
Level: 1

Type: WARNING

Impact: Other

OVD-40028: Maximum operations per connection exceeded ({0}/{1}, {2}/{3}).

Cause: Exceeded maximum number of operations that could be performed per connection.

Action: Ensure Quota settings are correct. Retry after rating period is over.
Level: 1

Type: WARNING

Impact: Other

OVD-40029: Maximum connections per subject({0}) exceeded.

Cause: Exceeded the maximum connections that any bound DN may have at any one time.

Action: Ensure Quota settings are correct. Retry after rating period is over.
Level: 1

Type: WARNING

Impact: Other

OVD-40030: Maximum concurrent connections({0}) exceeded.

Cause: Exceeded the maximum number of connections the Oracle Virtual Directory server could allow.

Action: Limit the number of active connections to Oracle Virtual Directory server from different clients.
Level: 1

Type: WARNING

Impact: Other

OVD-40031: Maximum connections per IP address({0}) exceeded.

Cause: Exceeded the maximum number of connections that an IP address may make at any one time.

Action: Ensure Quota settings are correct. Retry after rating period is over.
Level: 1

Type: WARNING

Impact: Other

OVD-40068: Invalid backend requested for search:{0}.

Cause: An attempt to lookup target adapter has failed.

Action: Ensure parameters of search request are correct.
Level: 1

Type: WARNING

Impact: Other

OVD-40069: Allowing searches for unindexed attributes.

Cause: Searching against unindexed attributes.

Action: Change the Local Store Adapter search configuration.
Level: 1

Type: WARNING

Impact: Other

OVD-40073: Closing user session {0}/{1} as idle time limit is exceeded.

Cause: Exceeded the maximum time period a connection can remain idle.

Action: Ensure that the idle connection time-out period is correct in server configuration.
Level: 1

Type: WARNING

Impact: Other

OVD-40074: Directory Error Reported: #{0} - {1}.

Cause: Error happened when processing LDAP entry.

Action: Make sure Oracle Virtual Directory server is running properly.
Level: 1

Type: WARNING

Impact: Other

OVD-40075: Bad filter error for: {0}.

Cause: Error when parsing filter.

Action: Ensure that the input in request is valid.
Level: 1

Type: WARNING

Impact: Other

OVD-40100: Peer identity not verified when SSL require client auth enabled: {0}.

Cause: The client did no provide a certificate or invalid certificate.

Action: Ensure that the client setup SSL mutual authentication.
Level: 1

Type: WARNING

Impact: Other

OVD-40110: Invalid LDAP search root specified or missing. {0}

Cause: The search root was invalid.

Action: Provide valid LDAP search root.
Level: 1

Type: WARNING

Impact: Other

OVD-40123: Configuration changed on disk. Failed while updating to MAS repository.

Cause: Check MAS log to find out.

Action: Manually sync from local to repository using asctl command line.
Level: 1

Type: WARNING

Impact: Other

OVD-40124: Failure in syncing files {0} from local to MAS repository.

Cause: Check MAS log to find out.

Action: Manually sync these files from local to repository using asctl command line.
Level: 1

Type: WARNING

Impact: Other

OVD-40125: Adapter {0} is neither operational nor provisioned.

Cause: The adapter did not exist.

Action: Refresh Adapters configuration from ODSM.
Level: 1

Type: WARNING

Impact: Other

OVD-60002: Unable to close the file: {0}.

Cause: Unable to close the file.

Action: Verify that the file exists.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60003: Error occured in communicating with client: {0}.

Cause: Client side of channel was closed for writing.

Action: Restart the client.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60004: Critical error: Printing stack trace.

Cause: Critical error occurred when processeing client request.

Action: Ensure that the request from client is correct.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60005: Invalid DN specified in Access Control List.

Cause: The DN specified in the Access Control List was incorrect.

Action: Specify a valid DN in valid DN format.Eg:cn=Jim Smith,ou=People,o=Division B,c=UK
Level: 1

Type: ERROR

Impact: Configuration

OVD-60006: Error in parsing backend types file.

Cause: Error parsing the configuration file.

Action: Verify if the configuration file conforms to the schema.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60007: Error in parsing backend properties.

Cause: Improper properties file was used.

Action: No action.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60008: Error in instantiating {0}.

Cause: Could not start the object mentioned in the log file.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

OVD-60009: Error in starting {0} : {1}.

Cause: Could not start the object mentioned in the log file.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

OVD-60010: Cannot modify root DSE.

Cause: Modification of root DSE opertation failed.

Action: Verify if the server allows modification of root DSE.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60011: bad value

Cause: The specified value was not appropriate.

Action: No action.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60012: Replace not supported on object.

Cause: Replace operation was not supported on the object.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60013: Failure in writing schema file: {0}.

Cause: Could not write to schema configuration files.

Action: Verify if the file system is writeable.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60014: Unable to modify.

Cause: Could not perform modification on the object.

Action: Check if the backend server allows modification.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60015: Error in opening mapping file: {0}.

Cause: Invalid file or no permissions or incorrect file location or file did not exist.

Action: Ensure a valid mapping file exists with correct permissions and in the correct location.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60016: IO error while reading the mapping file.

Cause: The Oracle Virtual Directory Server was unable to read mapping file.

Action: Ensure that the file system is available where mapping files are deployed.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60017: Invalid DN created by mapping rules: {0}.

Cause: The mapping rule was incorrectly specified.

Action: The DN composed from the mapping rules is incorrect.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60018: {0} Invalid DN as suffix: {1}.

Cause: Invalid DN.

Action: Provide a valid DN.Eg:cn=Jim Smith,ou=People,o=Division B,c=UK
Level: 1

Type: ERROR

Impact: Configuration

OVD-60019: {0} Invalid DN as base: {1}.

Cause: Invalid DN.

Action: Provide a valid DN.Eg:cn=Jim Smith,ou=People,o=Division B,c=UK
Level: 1

Type: ERROR

Impact: Configuration

OVD-60020: {0} Unable to open database mapping file {1}.

Cause: Invalid file or no permissions or incorrect file location or file did not exist.

Action: Ensure a valid mapping file exists with correct permissions and in the correct location.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60021: IO error while reading the Database Adapter Mapping file.

Cause: Oracle Virtual Directory Server was unable to read mapping files.

Action: Check Oracle Virtual Directory server logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60022: Invalid DN {0} is used as adapter root value.

Cause: Invalid DN.

Action: Provide a valid DN.Eg:cn=Jim Smith,ou=People,o=Division B,c=UK
Level: 1

Type: ERROR

Impact: Configuration

OVD-60023: Remote hosts are unavailable: {0}.

Cause: Could not establish a connection to the remote LDAP server.

Action: Ensure that the LDAP server is available.
Level: 1

Type: ERROR

Impact: Network

OVD-60024: Connection error: {0}.

Cause: Could not establish a connection due to incorrect connection details or LDAP server was unavailable.

Action: Ensure LDAP server is available and connection details are correct.
Level: 1

Type: ERROR

Impact: Network

OVD-60025: Unable to modify.

Cause: LDAP operations error.

Action: Check Oracle Virtual Directory server logs for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60026: Attempted to uses name: {0}.

Cause: Invalid DN.

Action: Ensure that the DN is valid.Eg:cn=Jim Smith,ou=People,o=Division B,c=UK
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60027: IO problem while initializing the datafile: {0}.

Cause: Error happened while accessing Local Store Adapter data files.

Action: Contact Oracle Virtual Directory administrator.
Level: 1

Type: ERROR

Impact: Operating System

OVD-60028: Problem while initializing the datafile: {0}.

Cause: Error happened while accessing Local Store Adapter data files.

Action: Contact Oracle Virtual Directory administrator.
Level: 1

Type: ERROR

Impact: Operating System

OVD-60029: Unable to modify data file.

Cause: IO exception happened while trying to free map file.

Action: Contact Oracle Virtual Directory administrator.
Level: 1

Type: ERROR

Impact: Operating System

OVD-60030: Error while updating free space file.

Cause: IO exception happened while trying to free map file.

Action: Contact Oracle Virtual Directory administrator.
Level: 1

Type: ERROR

Impact: Operating System

OVD-60031: Error: {0}.

Cause: Exception happened while trying to free map file.

Action: Contact Oracle Virtual Directory administrator.
Level: 1

Type: ERROR

Impact: Operating System

OVD-60032: IO Error writing EID#{0} to datafile: {1}.

Cause: Writing data to data file failed.

Action: Contact Oracle Virtual Directory administrator.
Level: 1

Type: ERROR

Impact: Operating System

OVD-60033: Error writing EID#{0} to datafile: {1}.

Cause: Writing data to data file failed.

Action: Contact Oracle Virtual Directory administrator.
Level: 1

Type: ERROR

Impact: Data

OVD-60034: Error deleting EID#{0} to datafile: {1}.

Cause: Removing data from data file failed.

Action: Contact Oracle Virtual Directory administrator.
Level: 1

Type: ERROR

Impact: Data

OVD-60035: Error reading entry #{0} : {1}.

Cause: Reading data from data file failed.

Action: Contact Oracle Virtual Directory administrator.
Level: 1

Type: ERROR

Impact: Data

OVD-60036: Error parsing entry #{0} : {1}.

Cause: Reading data from data file failed.

Action: Contact Oracle Virtual Directory administrator.
Level: 1

Type: ERROR

Impact: Data

OVD-60037: Error modifying EID#{0} in datafile: {1}.

Cause: Writing data from data file failed.

Action: Contact Oracle Virtual Directory administrator.
Level: 1

Type: ERROR

Impact: Data

OVD-60038: Error renaming EID#{0} in datafile: {1}.

Cause: Writing data from data file failed.

Action: Contact Oracle Virtual Directory administrator.
Level: 1

Type: ERROR

Impact: Data

OVD-60039: Unable to expire random access file: {0}.

Cause: Tried to expire the random access file and IO exception encountered.

Action: Contact Oracle Virtual Directory administrator.
Level: 1

Type: ERROR

Impact: Data

OVD-60040: Unable to open files.

Cause: Failed to open the files.

Action: Contact Oracle Virtual Directory administrator.
Level: 1

Type: ERROR

Impact: Data

OVD-60041: Error writing {0} ADD to transaction log: {1}.

Cause: Tried to write transaction log and it failed.

Action: Contact Oracle Virtual Directory administrator.
Level: 1

Type: ERROR

Impact: Data

OVD-60042: Error writing entry#{0} DELETE to transaction log: {1}.

Cause: Tried to write transaction log and it failed.

Action: Contact Oracle Virtual Directory administrator.
Level: 1

Type: ERROR

Impact: Data

OVD-60043: Error writing {0} MODIFY to transaction log: {1}.

Cause: Tried to write transaction log and it failed.

Action: Contact Oracle Virtual Directory administrator.
Level: 1

Type: ERROR

Impact: Data

OVD-60044: Error writing {0} RENAME to transaction log: {1}.

Cause: Tried to write transaction log and it failed.

Action: Contact Oracle Virtual Directory administrator.
Level: 1

Type: ERROR

Impact: Data

OVD-60045: Error opening the Transaction Log: {0}.

Cause: Tried to open transaction log and it failed.

Action: Contact Oracle Virtual Directory administrator.
Level: 1

Type: ERROR

Impact: Data

OVD-60046: Error truncating transaction log.

Cause: The access log file could not be truncated.

Action: Manually truncate the access log files.
Level: 1

Type: ERROR

Impact: Data

OVD-60047: Corrupt Transaction at {0}.

Cause: Local Store Adapter transaction corrupted.

Action: Contact OVD administrator.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60048: {0} Unable to open file: {1}.

Cause: File not found.

Action: Ensure that the file exists.
Level: 1

Type: ERROR

Impact: Data

OVD-60049: {0} Invalid DN suffix: {1}.

Cause: The suffix used for DN was incorrect.

Action: Use correct suffix for rules for constructing a DN.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60050: {0} Invalid DN: {1}={2},{3}.

Cause: The DN composed as shown was not correct.

Action: Make changes to the rules for constructing the DN to ensure valid DN syntax.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60051: Modification is not supported on this {0}.

Cause: Modication of this object is not supported.

Action: No action.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60052: Unable to listen on Port {0}:{1}.

Cause: Port may be occupied.

Action: Ensure that the port is free.
Level: 1

Type: ERROR

Impact: Network

OVD-60053: Error accepting connection from server socket: {0}.

Cause: Error while accepting connection from client.

Action: Retry starting the listener.
Level: 1

Type: ERROR

Impact: Network

OVD-60054: Critical error on server socket: {0}.

Cause: OS error was encountered.

Action: Check network settings.
Level: 1

Type: ERROR

Impact: Network

OVD-60055: Out of memory error: Printing stack trace.

Cause: Out of memory.

Action: Contact the Oracle Virtual Directory administrator.
Level: 1

Type: ERROR

Impact: Process

OVD-60056: Cannot stop server socket.

Cause: Error occured while closing server socket.

Action: Retry stopping the listener.
Level: 1

Type: ERROR

Impact: Network

OVD-60057: Error setting socket on new connection: {0}.

Cause: Error occured while setting socket on the new client connection.

Action: Retry starting the listener.
Level: 1

Type: ERROR

Impact: Network

OVD-60058: Critical error: Printing stack trace. {0}.

Cause: Critical error while processing the client connection.

Action: Check Oracle Virtual Directory log file for more details.
Level: 1

Type: ERROR

Impact: Network

OVD-60059: Error instantiating listener of type {0}:{1}.

Cause: Error while starting the listener.

Action: Check Oracle Virtual Directory log files for more details.
Level: 1

Type: ERROR

Impact: Network

OVD-60060: An error occurred.

Cause: An error occured while processing the request.

Action: Correct the error and re-submit the request.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60061: Directory Error#{0}: {1}.

Cause: An error occured while processing the request.

Action: Correct the error and re-submit the request.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60062: Error transforming DSML using: {0}.

Cause: Transforming DSML request failed.

Action: Turn on debug to get more error information.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60063: Error in XSLT frontend: {0}.

Cause: Failed when processing incoming requests to get query information.

Action: Turn on debug to get more error information.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60064: Missing MD5 capability.

Cause: Error with MD5 hashing compatability.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

OVD-60065: Error getting entry {0}:{1}.

Cause: Could not retrieve the specified entry.

Action: Verify that the specified entry exists in the directory.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60066: Error truncating change log: {1}.

Cause: No action required. Deprecated.

Action: No action required.
Level: 1

Type: ERROR

Impact: Data

OVD-60067: Error opening changelog database: {1}.

Cause: Deprecated.

Action: No action required.
Level: 1

Type: ERROR

Impact: Data

OVD-60068: Error closing changelog database: {1}.

Cause: Deprecated.

Action: No action required.
Level: 1

Type: ERROR

Impact: Data

OVD-60069: Error reading changelog entry#: {1}.

Cause: Deprecated.

Action: No action required.
Level: 1

Type: ERROR

Impact: Data

OVD-60070: Error parsing replication properties.

Cause: Deprecated.

Action: No action required.
Level: 1

Type: ERROR

Impact: Data

OVD-60071: Unable to locate agreement:.

Cause: Deprecated.

Action: No action required.
Level: 1

Type: ERROR

Impact: Data

OVD-60072: Cannot update replica status file for.

Cause: Deprecated.

Action: No action required.
Level: 1

Type: ERROR

Impact: Data

OVD-60073: File not found: {0}.

Cause: Could not find the file specified in the log message.

Action: Check that the file is present on the file system.
Level: 1

Type: ERROR

Impact: Data

OVD-60074: IO error: {0}.

Cause: Encountered error in writing files to the disk.

Action: Check that the file system is working properly.
Level: 1

Type: ERROR

Impact: Data

OVD-60075: Error closing files: {0}.

Cause: Error encountered in closing file mentioned in the log message.

Action: Ensure that the file system is working properly.
Level: 1

Type: ERROR

Impact: Data

OVD-60076: Error writing to changelog file: {0}.

Cause: Deprecated.

Action: No action required.
Level: 1

Type: ERROR

Impact: Data

OVD-60077: Cannot update replica status file for {0}.

Cause: Deprecated.

Action: No action required.
Level: 1

Type: ERROR

Impact: Data

OVD-60078: Error Connecting to Consumer: {0} port {1}.

Cause: Deprecated.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60079: Agreement {0}: Skipping Change#{1} - Already Exists on Consumer.

Cause: Deprecated.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60080: Agreement {0}: Error Transmitting Change#{1} - {2}.

Cause: Deprecated.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60081: Agreement {0}: Skipping Change#{1} - Doesnt Exist on Consumer.

Cause: Deprecated.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60082: Agreement {0}: Invalid Changetype:{1} in change#{2}.

Cause: Deprecated.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60083: Failure in parsing schema: {0}.

Cause: LDAP schema specified in the xml file was incorrect.

Action: Make sure the schema conforms to the standard.
Level: 1

Type: ERROR

Impact: Data

OVD-60084: Missing object class.

Cause: Object class definition not found.

Action: Ensure that LDAP schema has the definition for object class.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60085: Missing attributes: {0}, Not allowed attributes: {1}.

Cause: The attributes specified are missing in the LDAP schema.

Action: Ensure LDAP schema has definition for the attributes.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60086: Error parsing XML file.

Cause: Error ecountered when parsing the configuration xml files.

Action: Ensure that XML files are consistent with the xsd.
Level: 1

Type: ERROR

Impact: Data

OVD-60087: Error instantiating XML Handler.

Cause: Could not satisfy the requested configuration.

Action: Verify that the currently configured XML parameters are correct.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60088: Error writing XML file.

Cause: Could not write the XML file to disk.

Action: Verify the file has write permissions.
Level: 1

Type: ERROR

Impact: Data

OVD-60089: Usage: java InitReplica AgreementName filename.

Cause: Deprecated.

Action: No action required.
Level: 1

Type: ERROR

Impact: Data

OVD-60090: Unable to locate agreement: {0}.

Cause: Deprecated.

Action: No action required.
Level: 1

Type: ERROR

Impact: Data

OVD-60091: Cannot update replica status file for {0}.

Cause: Deprecated.

Action: No action required.
Level: 1

Type: ERROR

Impact: Data

OVD-60092: Not an LDAP URL.

Cause: URL specified was not a valid LDAP URL.

Action: Ensure LDAP URL follows the standard format as defined in LDAP v3 Protocol.Format Eg: ldap://host:port/DN?attributes?scope?filter?
Level: 1

Type: ERROR

Impact: Configuration

OVD-60093: Invalid LDAP URL.

Cause: URL specified was not a valid LDAP URL.

Action: Ensure LDAP URL follows the standard format as defined in LDAP v3 Protocol.Format Eg: ldap://host:port/DN?attributes?scope?filter?
Level: 1

Type: ERROR

Impact: Configuration

OVD-60094: Bad LDAP filter.

Cause: Incorrect LDAP filter specified.

Action: Specifiy LDAP filter per the LDAP V3 protocol specification.
Level: 1

Type: ERROR

Impact: Process

OVD-60095: Failure in LDAP search: {0}.

Cause: LDAP search failed with the error.

Action: Check the LDAP error code and resolve the error appropriately.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60096: Error opening {0} for writing: {1}.

Cause: OS error encountered when opening IO for writing.

Action: Check OS error and correct the issue.
Level: 1

Type: ERROR

Impact: Data

OVD-60097: Failure in exporting LDAP entries to LDIF format: {0}.

Cause: Failed to export LDAP entries in LDIF format.

Action: Verify the input parameters provided for LDIF export is correct.
Level: 1

Type: ERROR

Impact: Data

OVD-60098: Error adding entry: {0}.

Cause: Error encountered while adding entry specified in the log file.

Action: Check the LDAP error code and resolve the error accordingly.
Level: 1

Type: ERROR

Impact: Data

OVD-60099: Schema violation adding {0}: {1}.

Cause: LDAP schema error encountered when adding an entry.

Action: Ensure that the entry being added conforms to the LDAP schema.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60100: Error reading input: {0}.

Cause: OS error encountered when reading input.

Action: Check the OS error logged and correct the issue.
Level: 1

Type: ERROR

Impact: Data

OVD-60101: Bad LDAP Filter.

Cause: Incorrect LDAP filter specified.

Action: Specifiy LDAP filter per the LDAP V3 protocol specification.
Level: 1

Type: ERROR

Impact: Process

OVD-60102: Invalid Adapter Suffix: {0}.

Cause: The suffix used for adapter did not exist.

Action: Specify the right suffix for the adapter.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60104: Failure (null pointer) in instantiating adapter: {0}.

Cause: Error ecountered in creating adapter.

Action: Ensure that the adapter configuration is proper.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60105: Join view adapter is disabled because primary adapter {0} is not defined

Cause: Primary adapter not defined.

Action: Define a primary adapter.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60106: {0} Unable to instantiate join#{1} of type {2}({3}) on adapter#{4}.

Cause: Unable to instantiate join.

Action: Check Oracle Virtual Directory log file for more details.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60107: Modification is invalid on {0}.

Cause: Trying to modify an invalid entry.

Action: Check the target entry and see if it is valid.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60108: Name not found {0}.

Cause: Entry not found.

Action: Check whether entry exists.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60109: Missing target adapter for shadow join .

Cause: No target adapter was defined for shadow join.

Action: Define a target adapter.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60110: Attempt to join to undefined/unavailable target adapter #{0}.

Cause: Target adapter was undefined/unavailable for join.

Action: Define a target adapter.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60111: ERROR: rule has missing backend(adapter#{0}).

Cause: Backend adapter specified in the join rule was undefined/unavailable.

Action: Define a valid backend adapter.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60112: Shadow Joiner exception querying joined entries.

Cause: Exception while retrieving joined entries.

Action: Check Oracle Virtual Directory log file for more details.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60113: Shadow Joiner exception processing join results.

Cause: Exception while processing join results.

Action: Check Oracle Virtual Directory log file for more details.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60114: Missing join rule relationship.

Cause: Join rule relationship was missing.

Action: Add a valid join rule relationship.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60115: Missing target adapter for simple join.

Cause: Target adapter for simple join missing.

Action: Add a target adapter for simple join.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60116: Attempt to join to undefined/unavailable target adapter #{0}.

Cause: An attempt was made to join to a undefined/unavailable target adapter.

Action: Provide an available target adapter to join.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60117: Error no join relationships defined.

Cause: No join relationship defined.

Action: Define a join relationship.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60118: Transaction file failed to initialize.

Cause: Tried to start transaction processor and it failed.

Action: Contact Oracle Virtual Directory administrator.
Level: 1

Type: ERROR

Impact: Data

OVD-60119: Error, missing suffix name for local store adapter {0}.

Cause: Incorrect Local Store Adapter configuration.

Action: Check Local Store Adapter configuration.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60120: Error initializing mapping:.

Cause: Error while initializing mapping in the DB Adapter.

Action: Check the Oracle Virtual Directory server logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60121: {0} Invalid DN: {1}.

Cause: The DN specified was not a valid DN.

Action: Provide a valid DN.Eg:cn=Jim Smith,ou=People,o=Division B,c=UK
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60122: Error creating TLS tunnel: {0}.

Cause: Error encountered when connecting to backend server over TLS.

Action: Check error code and correct the error.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60123: Invalid format.

Cause: Invalid string representation of attribute type or object class.

Action: Specify a valid RFC2252-style string for attribute type and object class.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60124: haveattr requires attribute type as argument.

Cause: Attribute type was not specified for the operation.

Action: Specify a valid attribute type.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60125: haveattrval requires an argument specifying attribute=value.

Cause: Missing or invalid argument for the operation.

Action: Specify the argument in correct format.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60126: Matchdn requires a distinguished name argument.

Cause: Distinguished name was not specified for the operation.

Action: Specify a valid distinguished name.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60127: rename requires newattr=oldattr as argument.

Cause: Missing or invalid argument for the operation.

Action: Specify the argument in correct format.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60128: copy requires newattr=oldattr as argument.

Cause: Missing or invalid argument for the operation.

Action: Specify the argument in correct format.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60129: cappend requires newattr=oldattr as argument.

Cause: Missing or invalid argument for the operation.

Action: Specify the argument in correct format.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60130: rappend requires newattr=oldattr as argument.

Cause: Missing or invalid argument for the operation.

Action: Specify the argument in correct format.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60131: addvalue requires attribute=value as argument.

Cause: Missing or invalid argument for the operation.

Action: Specify the argument in correct format.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60132: deletevalue requires attribute=value as argument.

Cause: Missing or invalid argument for the operation.

Action: Specify the argument in correct format.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60133: replacevalue requires attribute=value as argument.

Cause: Missing or invalid argument for the operation.

Action: Specify the argument in correct format.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60134: Setdn requires distinguished name as an argument.

Cause: Distinguished name was not specified for the operation.

Action: Specify a valid distinguished name.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60135: splitvals requires attribute=delimiter as argument.

Cause: Wrong number of arguments specified for the operation.

Action: Specify the argument in correct format.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60136: Unknown operation specified in mapping file: {0}.

Cause: Invalid operation specified in mapping file.

Action: Specify a valid operation.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60137: No DN Specified at line: {0}.

Cause: Distinguished name missing at the specified line in mapping file.

Action: Specify a valid distinguished name.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60138: Error at line#{0}: {1}.

Cause: Failed to compile the mapping file.

Action: Verify the mapping file is correct.
Level: 1

Type: ERROR

Impact: Data

OVD-60139: Joiner: Missing backend handle for adapter#{0}.

Cause: No backend found for join.

Action: Define a backend for join.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60140: Usage: ImportLDIF filename.ldif.

Cause: Usage string.

Action: No action required.
Level: 1

Type: ERROR

Impact: Data

OVD-60141: {0} Bad Suffix: {1}.

Cause: Invalid DN.

Action: Provide a valid DN.Eg:cn=Jim Smith,ou=People,o=Division B,c=UK
Level: 1

Type: ERROR

Impact: Data

OVD-60142: Usage: ExportLDIF suffix filename.ldif.

Cause: Usage String.

Action: No action required.
Level: 1

Type: ERROR

Impact: Data

OVD-60143: {0} Unable to create connection to {1} as {2}.

Cause: Incorrect connection details.

Action: Check the connection details.
Level: 1

Type: ERROR

Impact: Network

OVD-60144: {0} Error opening database file:{1}.

Cause: Data file for the Local Store Adapter might be corrupted.

Action: Contact Oracle Virtual Directory administrator.
Level: 1

Type: ERROR

Impact: Data

OVD-60145: {0} Error initializing transaction processor:{1}.

Cause: Error happened when trying to start a transaction.

Action: Contact Oracle Virtual Directory administrator.
Level: 1

Type: ERROR

Impact: Process

OVD-60146: Error searching for {0}: {1}.

Cause: Could not find the specified group.

Action: Ensure that the group is available in datastore.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60148: GetBindDN: Missing backend handle.

Cause: No backend found for join.

Action: Define a backend for join.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60149: IO Error Starting Listener: {0}.

Cause: Error starting listener.

Action: Check Oracle Virtual Directory log file for more details.
Level: 1

Type: ERROR

Impact: Network

OVD-60150: Error starting connection acceptor: {0}.

Cause: Error while accepting client request.

Action: Check Oracle Virtual Directory server logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60151: Bad Basic Encoding Rules tag.

Cause: Error while processing the LDAP client request.

Action: Valid LDAP client request required.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60152: Indefinite length encoding not supported.

Cause: Indefinite length encoding was found in the Basic Encoding Rules.

Action: Valid LDAP client request required.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60154: Paged result control construction failure {0}.

Cause: An error occured while constructing a paged result control.

Action: Check Oracle Virtual Directory server logs for more details.
Level: 1

Type: ERROR

Impact: Process

OVD-60155: Unexpected schema type NULL for {0}.

Cause: Schema type was unavailable for attribute.

Action: Ensure that the schema is valid.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60156: Error retrieving BLOB data.

Cause: Error retrieving attribute value.

Action: Check Oracle Virtual Directory server logs for more details.
Level: 1

Type: ERROR

Impact: Data

OVD-60158: Remote server failure: {0}.

Cause: Search failed in the remote LDAP server.

Action: Check Oracle Virtual Directory server logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60159: Unable to create connection to {0}:{1} as {2}.

Cause: Could not create a connection to the LDAP server.

Action: Ensure connection details are correct.
Level: 1

Type: ERROR

Impact: Network

OVD-60160: Failure in loading database metadata {0}.

Cause: Error while initializing metadata for the DB Adapter.

Action: Ensure that the DB Adapter is correctly configured.
Level: 1

Type: ERROR

Impact: Data

OVD-60161: Unable to map entry to database.

Cause: No database mapping details found for the given entry.

Action: Provide correct mapping details.
Level: 1

Type: ERROR

Impact: Data

OVD-60162: Multi-table modify is not supported.

Cause: The mapping spans multiple DB tables.

Action: Provide a valid modify request or modify the DB mapping.
Level: 1

Type: ERROR

Impact: Data

OVD-60163: Database object class modification prohibited.

Cause: Object class modification not supported for database adapter.

Action: Provide a valid modify request.
Level: 1

Type: ERROR

Impact: Data

OVD-60164: No such attribute: {0}.

Cause: Attribute did not exist in the DB mapping.

Action: Provide a valid modify request or modify the DB mapping.
Level: 1

Type: ERROR

Impact: Data

OVD-60165: Multiple changetypes to the same attribute in a single modify is not allowed by DB adapter.

Cause: DB adapter did not support multiple changetypes for the same attribute.

Action: Provide a valid modify request.
Level: 1

Type: ERROR

Impact: Data

OVD-60166: Unable to delete rows.

Cause: Internal error.

Action: Check the Oracle Virtual Directory server logs for more details.
Level: 1

Type: ERROR

Impact: Data

OVD-60167: Unable to re-insert rows.

Cause: Internal error.

Action: Check the Oracle Virtual Directory server logs for more details.
Level: 1

Type: ERROR

Impact: Data

OVD-60168: DB Adapter has restrictions on mixed modify types when multiple values are used.

Cause: DB adapter did not support using multiple values for mixed modify types.

Action: Provide a valid modify request.
Level: 1

Type: ERROR

Impact: Data

OVD-60169: Unable to replace rows.

Cause: Internal error.

Action: Check the Oracle Virtual Directory server logs for more details.
Level: 1

Type: ERROR

Impact: Data

OVD-60170: Unable to insert rows.

Cause: Internal error.

Action: Check the Oracle Virtual Directory server logs for more details.
Level: 1

Type: ERROR

Impact: Data

OVD-60171: {0} Change contains unmapped attribute:{1} (dn: {2}).

Cause: Attribute did not exist in the DB mapping.

Action: Provide a valid moddn request or modify the DB mapping.
Level: 1

Type: ERROR

Impact: Data

OVD-60172: Error getting matches.

Cause: Error while retrieving results matching criteria.

Action: Check Oracle Virtual Directory server logs for more details.
Level: 1

Type: ERROR

Impact: Data

OVD-60173: Remote server failure: {0}.

Cause: Remote LDAP server was unavailable or busy.

Action: Ensure LDAP server is available.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60174: Remote server unreachable and marked inactive: {0}:{1}.

Cause: Remote LDAP server was unavailable.

Action: Ensure LDAP server is available.
Level: 1

Type: ERROR

Impact: Network

OVD-60176: JNDI exception: {0}.

Cause: LDAP operations error.

Action: Check the Oracle Virtual Directory server logs for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60177: Invalid DN exception - unconverted DN: {0}.

Cause: Invalid DN.

Action: Ensure that the DN is valid.Eg:cn=Jim Smith,ou=People,o=Division B,c=UK
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60178: Paged search control failure: {0}.

Cause: LDAP search failed with the paged search control.

Action: Check the Oracle Virtual Directory server logs for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60179: Cannot connect for {0} milliseconds.

Cause: Could not connect to server.

Action: Ensure server is available.
Level: 1

Type: ERROR

Impact: Network

OVD-60180: Cannot search for {0} milliseconds.

Cause: Could not connect to server to perform search.

Action: Ensure server is available.
Level: 1

Type: ERROR

Impact: Network

OVD-60182: Exception: {0}.

Cause: An exception has occurred while processing the request.

Action: Check Oracle Virtual Directory server logs for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60183: Invalid backend requested for search: {0}.

Cause: An attempt to lookup target adapter has failed.

Action: Ensure parameters of search request are correct.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60184: LDAP exception: {0}.

Cause: An exception has occurred while processing the request.

Action: Check Oracle Virtual Directory server logs for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60185: Repairing truncated deletion log.

Cause: Delete log was corrupted.

Action: Information only and no further action required.
Level: 1

Type: ERROR

Impact: Files

OVD-60186: Error renaming old files, aborting compaction.

Cause: Renaming old data files failed.

Action: Contact Oracle Virtual Directory administrator.
Level: 1

Type: ERROR

Impact: Files

OVD-60187: Compaction error: {0}.

Cause: IO exception happened while compacting the data file.

Action: Contact Oracle Virtual Directory administrator.
Level: 1

Type: ERROR

Impact: Files

OVD-60188: Upgrade error: {0}.

Cause: IO exception happened while upgrading.

Action: Contact Oracle Virtual Directory administrator.
Level: 1

Type: ERROR

Impact: Files

OVD-60189: Missing entry to be joined, received NULL.

Cause: Entry to be joined was missing in the primary adapter.

Action: Check if entry is present in the primary adapter.
Level: 1

Type: ERROR

Impact: Data

OVD-60191: Shadow Joiner exception processing alternative join results(rename detection processing).

Cause: Exception while processing alternative join results.

Action: Check Oracle Virtual Directory server logs for more details.
Level: 1

Type: ERROR

Impact: Data

OVD-60192: Failure in setting request control {0}.

Cause: Internal error.

Action: Check Oracle Virtual Directory server logs for more details.
Level: 1

Type: ERROR

Impact: Session

OVD-60193: Error no join relationships defined.

Cause: No join relationships defined.

Action: Define a join relationship.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60194: Unable to create new value with syntax {0}.

Cause: Could not create an instance of the specified syntax class.

Action: Ensure that the specified syntax class can be instantiated.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60196: No search root for user entries defined (srchroot missing).

Cause: Property srchroot missing.

Action: Define srchroot for user entries.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60197: No username to entry matching attributes (matchattrs undefined).

Cause: Property matchattrs not defined.

Action: Define matchattrs property.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60198: Fatal error connecting to directory handler.

Cause: No backend available.

Action: Verify the backends and Oracle Virtual Directory server are running properly.
Level: 1

Type: ERROR

Impact: Network

OVD-60199: Fatal error connecting to DoS tracker.

Cause: DoS connection not available.

Action: Verify Oracle Virtual Directory server is running properly.
Level: 1

Type: ERROR

Impact: Network

OVD-60200: LDAP Error Code {0}.

Cause: Performed an operation causing constraint violation error.

Action: Check the operation parameters.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60201: Invalid DN {0}.

Cause: The specified DN was invalid.

Action: Check the DN syntax and value.Eg:cn=Jim Smith,ou=People,o=Division B,c=UK
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60202: Error processing dynamic group : {0}.

Cause: Error encountered while procesing dynamic group entry.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60203: Cannot retrieve SOAP response.

Cause: Failed to retrieve SAX parameters from the SOAP response message.

Action: The SOAP server may be busy. Try again later.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60204: Cannot listen on host.

Cause: The admin host was invalid or unreachable.

Action: Provide a valid admin host.
Level: 1

Type: ERROR

Impact: Network

OVD-60205: Cannot instantiate Admin service.

Cause: Missing adminService.war or dsmlv2Admin.war file.

Action: Ensure that Oracle Home has those files.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60206: Cannot start Admin service.

Cause: Failed to start Admin server.

Action: Check the configuration for admin service and start the server again.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60207: Cannot authenticate.

Cause: Invalid user name or password.

Action: Provide a valid authentication credential.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60208: Cannot instantiate the local JDBC driver.

Cause: Failed to load DB drivers.

Action: Reinstall the correct JDBC drivers on the server and retry.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60209: Driver {0} not found. Use Manage Server Libraries command to install the correct JDBC drivers on the server.

Cause: DB service driver was invalid.

Action: Reinstall the JDBC driver.
Level: 1

Type: ERROR

Impact: Deployment

OVD-60210: Cannot load tables.

Cause: Failed to load the DB schema.

Action: Verify the validity of the DB Schema and its access authorization.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60211: Cannot load table columns.

Cause: Access the schema table column was restricted or it might be invalid.

Action: Check the validity of the table column and its accessibility.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60212: Cannot load primary keys.

Cause: The primary key to DB Schema was invalid or inaccessible.

Action: Verify the primary key setup and the server array .
Level: 1

Type: ERROR

Impact: Configuration

OVD-60213: Cannot load results.

Cause: The result may be too big or inaccessible .

Action: Check query size or the DB access credential.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60214: Cannot set Access Control Lists enabled.

Cause: Access Control List format could be invalid or not setup properly.

Action: Check the Access Control List configuratioin and try again.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60215: Error stopping server.

Cause: The server could be in an invalid state or down.

Action: Check the server processes and clean up manually.
Level: 1

Type: ERROR

Impact: Process

OVD-60216: Cannot start Oracle Virtual Directory server: {0}.

Cause: The configuration could be invalid or system resources were missing.

Action: Verify all the server configuration and the system resouces.
Level: 1

Type: ERROR

Impact: Process

OVD-60217: Cannot reload server.

Cause: The server may be in an invalid state.

Action: Try shutdown and start up server again.
Level: 1

Type: ERROR

Impact: Process

OVD-60218: An attempt to restart Oracle Virtual Directory server failed.

Cause: An internal error has occurred.

Action: Check the server log for errors.
Level: 1

Type: ERROR

Impact: Process

OVD-60219: Cannot start listener {0}.

Cause: Listener configuration could be invalid.

Action: Verify and fix listener configuration.
Level: 1

Type: ERROR

Impact: Ports

OVD-60220: Cannot stop listener {0}.

Cause: The listener could be down or in an invalid state.

Action: Manually verify the listener and cleanup needed.
Level: 1

Type: ERROR

Impact: Threads

OVD-60221: Cannot enable adapter {0}.

Cause: Invalide adapter configuration.

Action: Setup the adapter configuration correctly and retry.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60222: Cannot disable adapter {0}.

Cause: The adapter may be in a transaction or down.

Action: Wait for all transactions to finish and retry.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60223: Cannot retrieve adapter configs.

Cause: Adapter configuration file may be corrupted or invalid format.

Action: Verify the adapter configuration file and using the management tool to fix it.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60224: Cannot get adapter config for {0}.

Cause: The configuration for the adapter may be invalid.

Action: Fix the adapter configuration and retry.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60225: Cannot get listener configs.

Cause: The listener configurations could be invalid.

Action: Very the validity of the configurations and retry.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60226: Cannot get listener config {0}.

Cause: The configuration for the listener was wrong.

Action: Correct the listener configuration and retry.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60227: Cannot provision server.

Cause: The disk space may be full or file system was not writable.

Action: Check the configuration path or file system problem.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60228: Cannot provision listeners.

Cause: The disk space may be full or file system was not writable.

Action: Check the configuration path or file system problem.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60229: Error Setting Adapter {0}.

Cause: The disk space may be full or file system was not writable.

Action: Fix the configuration path or file system problem.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60230: Cannot provision adapters.

Cause: The disk space may be full or file system was not writable.

Action: Fix the configuration path or file system problem.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60231: Cannot load adapters.

Cause: The adapters configuration was invalid.

Action: Check the validity the configuraton and reload the adapters.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60232: Cannot provision adapter before {0}.

Cause: The named adapter may be invalid.

Action: Verify the named adapter and retry the provision again.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60233: Cannot move adapter {0}, up={1}.

Cause: The adapter may be at the top or the potential bug.

Action: Check the position of the adapter.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60234: Cannot remove provisioned listener {0}.

Cause: The disk may not be writable.

Action: Check the file system and its accessibility.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60235: Cannot rename provisioned listener from {0} to {1}.

Cause: The old name or the new name may be invalid.

Action: Check the name and try with a different name.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60236: Cannot load listeners.

Cause: The server may be down or resource was busy.

Action: Make sure the server is up and resource is available.
Level: 1

Type: ERROR

Impact: Threads

OVD-60237: Cannot remove provisioned adapter {0}.

Cause: The adapter name may be wrong.

Action: Verify the adapter name and try again.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60238: Cannot rename provisioned adapter from {0} to {1}.

Cause: The configuration versions may be invalid or the name was wrong.

Action: Verify the configuration versions or the adapter names.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60239: Cannot Store.

Cause: File system may be full or inaccessible.

Action: Check the disk space or file permissions.
Level: 1

Type: ERROR

Impact: Files

OVD-60240: Cannot store schema to {0}.

Cause: File system was not accessible.

Action: Check the file system accessibility and try again.
Level: 1

Type: ERROR

Impact: Files

OVD-60241: Cannot provision Access Control Lists.

Cause: The file system may be full or not accessible.

Action: Verify the file system and try again.
Level: 1

Type: ERROR

Impact: Files

OVD-60242: Cannot start Access Control Lists.

Cause: Access Control Lists format may be invalid.

Action: Check the validity of the Access Control Lists and retry.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60243: Cannot store file {0}.

Cause: File system may be full of inaccessible.

Action: Check the file system and try again.
Level: 1

Type: ERROR

Impact: Files

OVD-60244: Cannot retrieve file {0}.

Cause: The file system may be corrupted or inaccessible.

Action: Check the file system and retry.
Level: 1

Type: ERROR

Impact: Files

OVD-60245: Cannot find tail of {0}.

Cause: The file may be corrupted.

Action: Fix the file formate and retry.
Level: 1

Type: ERROR

Impact: Files

OVD-60246: Cannot store mapping {0}.

Cause: File system may be full or inaccesible.

Action: Check the file system and permission.
Level: 1

Type: ERROR

Impact: Files

OVD-60247: Cannot restart adapter {0}, nice={1}.

Cause: Backend Handler or routing handler was having problem.

Action: Make sure the system is not too busy then retry.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60248: Cannot restart listener {0}.

Cause: The listener may be down.

Action: Try to start up listener instead.
Level: 1

Type: ERROR

Impact: Threads

OVD-60249: Cannot deploy JAR.

Cause: The jar file may be missing or not readable.

Action: Check the validity and access to the jar file.
Level: 1

Type: ERROR

Impact: Deployment

OVD-60250: Cannot push to server.

Cause: File system may be full or inaccessible.

Action: Check the file system and its file permission.
Level: 1

Type: ERROR

Impact: Files

OVD-60251: Cannot load plugin "{0}".

Cause: The plugin jar file may be invalid or missing.

Action: Verify the jar file path.
Level: 1

Type: ERROR

Impact: Files

OVD-60252: Cannot load path {0}.

Cause: The file may be missing or corrupted.

Action: Pleaes verify the file path.
Level: 1

Type: ERROR

Impact: Files

OVD-60253: Cannot retrieve mapping information.

Cause: The mapping file was missing or corrupted.

Action: Check the mapping file.
Level: 1

Type: ERROR

Impact: Files

OVD-60254: Cannot load joiner "{0}".

Cause: The joiner jar file was missing or corrupted.

Action: Check the joiner jar file and retry.
Level: 1

Type: ERROR

Impact: Files

OVD-60255: Error retrieving status information.

Cause: The server configuration file was missing or corrupted.

Action: Check the server.os_xml.
Level: 1

Type: ERROR

Impact: Files

OVD-60256: Cannot retrieve hosts.

Cause: The DNS server may be down or not setup properly.

Action: Check the DNS server status and its setup.
Level: 1

Type: ERROR

Impact: Network

OVD-60257: Cannot generate key.

Cause: PKI key store path may be wrong or key parameters were invalid.

Action: Check the key store path and the validity of the key parameters.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60258: Cannot delete key.

Cause: The key may be protected from deletion or did not exist.

Action: Check the key and its file permission.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60259: Cannot import certificate into alias {0}.

Cause: The certificate may be invalid or its format was not supported by the server.

Action: Verify the certificate using key tool tools such as Oracle Wallet Manager.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60260: Cannot generate certificate request.

Cause: The key store may be missing. Otherwise, the PKI parameters could be invalid or not supported.

Action: Check the key store path and its parameters for certificate request generation.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60261: Cannot retrieve server certificate.

Cause: The certificate may not exist or the key store was corrupted.

Action: Using Oracle Wallet Manager or Sun keytool to verify its content first.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60262: Cannot retrieve keystore entries.

Cause: The keystore may be corrupted or missing.

Action: Check the key store path and use keytool to verify its validity.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60263: Cannot reset BackendHandler.

Cause: Failed to shutdown backend handler.

Action: No actions required.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60264: Cannot continue to wait ... .

Cause: Adapter sleep thread was interrupted.

Action: No actions required.
Level: 1

Type: ERROR

Impact: Threads

OVD-60265: Cannot instantiate the Schema Adapter.

Cause: Failed to initialize schema adapter.

Action: Make sure configuration files are correct.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60266: Cannot instantiate the Root Adapter.

Cause: Failed to initialize root adapter.

Action: Make sure configuration files are correct.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60267: Cannot Modify Schema.

Cause: Failed to modify schema.

Action: Make sure proper values are provided for schema modification.
Level: 1

Type: ERROR

Impact: Data

OVD-60268: Error performing modify : {0}.

Cause: Ldap operations error.

Action: Check the Oracle Virtual Directory server logs for more details.
Level: 1

Type: ERROR

Impact: Process

OVD-60269: Cannot instantiate the local driver manager.

Cause: Error while loading driver manager class.

Action: Check Oracle Virtual Directory server logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60270: Cannot connect to: {0} - {1}.

Cause: Could not create a connection to database.

Action: Ensure JDBC URL and JDBC driver properties are valid. Check Oracle Virtual Directory server logs for more details.
Level: 1

Type: ERROR

Impact: Data

OVD-60271: Unable to locate RDN component: {0}.

Cause: Could not locate the RDN in the DB mapping.

Action: Ensure that the mapping is valid.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60272: Unable to discover remote LDAP servers via DNS for: {0}.

Cause: No/Incorrect LDAP server information in DNS.

Action: Provide correct LDAP server information in DNS.
Level: 1

Type: ERROR

Impact: Network

OVD-60273: No remote host available.

Cause: Could not establish connection to remote host.

Action: Check the connection details.
Level: 1

Type: ERROR

Impact: Network

OVD-60274: Cannot return the connection.

Cause: Could not establish a connection to the LDAP server.

Action: Ensure LDAP server is available and connection details are correct.
Level: 1

Type: ERROR

Impact: Network

OVD-60275: Unknown error.

Cause: Ldap operations error.

Action: Check Oracle Virtual Directory server logs for more details.
Level: 1

Type: ERROR

Impact: Process

OVD-60276: Error during search.

Cause: Ldap operations error.

Action: Check Oracle Virtual Directory server logs for more details.
Level: 1

Type: ERROR

Impact: Process

OVD-60277: DNS failure: {0}.

Cause: Unable to establish connection with DNS.

Action: Ensure DNS server information is correct.
Level: 1

Type: ERROR

Impact: Network

OVD-60278: Cannot close connection.

Cause: Could not close connection to the LDAP server.

Action: Check the Oracle Virtual Directory server logs for more details.
Level: 1

Type: ERROR

Impact: Network

OVD-60279: Not a context holder.

Cause: Internal error.

Action: Check the Oracle Virtual Directory server logs for more details.
Level: 1

Type: ERROR

Impact: Process

OVD-60280: Checkin called.

Cause: Internal error.

Action: Check the Oracle Virtual Directory server logs for more details.
Level: 1

Type: ERROR

Impact: Process

OVD-60281: Cannot retrieve entry.

Cause: Could not retrieve entry from the LDAP results.

Action: Check the Oracle Virtual Directory server logs for more details.
Level: 1

Type: ERROR

Impact: Process

OVD-60282: Unexpected Exception.

Cause: Internal error.

Action: Check the Oracle Virtual Directory server logs for more details.
Level: 1

Type: ERROR

Impact: Process

OVD-60283: Logging Exception when trying to create a LoginContext {0}.

Cause: Internal error.

Action: Check the Oracle Virtual Directory server logs for more details.
Level: 1

Type: ERROR

Impact: Process

OVD-60284: Logging Exception when trying to call login {0}.

Cause: Incorrect username or password.

Action: Ensure username and password are correct.
Level: 1

Type: ERROR

Impact: Data

OVD-60285: Logging exception when trying to call logout {0}.

Cause: Error while trying to logout.

Action: Check the Oracle Virtual Directory server logs for more details.
Level: 1

Type: ERROR

Impact: Process

OVD-60286: Zero byte read request.

Cause: Internal error.

Action: Check the Oracle Virtual Directory server logs for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60287: Cannot create SSL socket factory.

Cause: The SSL configuration was not setup correctly or the wallet file was missing.

Action: Check the SSL configuration and its wallet file.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60288: Cannot retrieve remote server information.

Cause: Could not retrieve remote server information.

Action: Provide remote server information.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60289: Error registering new stream: {0}.

Cause: Internal error.

Action: Check the Oracle Virtual Directory server logs for more details.
Level: 1

Type: ERROR

Impact: Process

OVD-60290: Cannot write to file.

Cause: Write Local Store Adapter data to data file and IO exception occured.

Action: Contact Oracle Virtual Directory administrator.
Level: 1

Type: ERROR

Impact: Operating System

OVD-60291: Cannot load GlobalServicesInterface.

Cause: Failed to load global plugins.

Action: Make sure global plugins are properly configured in server.os_xml.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60292: Security exception. Cannot instantiate {0}.

Cause: Security violation, thrown by JVM security manager.

Action: Debug the plugin class to find the violation.
Level: 1

Type: ERROR

Impact: Security

OVD-60293: Cannot instantiate {0}.

Cause: Failed to instantiate the specified class.

Action: Make sure the specified class is not an interface nor an abstract class.
Level: 1

Type: ERROR

Impact: Programmatic

OVD-60294: Invalid permisions on class {0}.

Cause: Failed to access to the definition of the specified class or constructor.

Action: Make sure the specified class is accessible.
Level: 1

Type: ERROR

Impact: Programmatic

OVD-60295: Cannot Find Class {0}.

Cause: The definition of specified class could not be found.

Action: Make sure the specified class exists.
Level: 1

Type: ERROR

Impact: Files

OVD-60296: Cannot instantiate plugin : {0}.

Cause: Failed to instantiate the specified plugin.

Action: Make sure the plugin class can be instantiated.
Level: 1

Type: ERROR

Impact: Programmatic

OVD-60297: Failed to parse configuration file : {0}.

Cause: Serious configuration error.

Action: Check the configuration file syntax.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60298: Invalid library path. {0}.

Cause: The classpath settings was incorrect.

Action: Ensure that the class path settings are correct.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60299: Failed to get entry for DN: {0}.

Cause: The entry did not exist.

Action: No action required.
Level: 1

Type: ERROR

Impact: Process

OVD-60300: Cannot instantiate wrapper plugin {0}.

Cause: Failed to instantiate the specified plugin.

Action: Ensure that the correct class name is provided.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60301: This plugin only works on {0} adapters.

Cause: The plugin was configured to wrong type of adapters.

Action: Configure the plugin only on proper adapters.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60302: Invalid DN in addEntry.

Cause: Failed while adding entry to cache because of invalid entry DN.

Action: No action required.
Level: 1

Type: ERROR

Impact: Data

OVD-60303: Cache exception: {0}.

Cause: Cache plugin failed.

Action: No action required.
Level: 1

Type: ERROR

Impact: Process

OVD-60304: Null entryname.

Cause: Failed to unregister the query of this entry from entry cache.

Action: No action required.
Level: 1

Type: ERROR

Impact: Data

OVD-60305: Unable to start "{0}". May not be configured as global plug-in.

Cause: The base adapter name for the plugin was missing.

Action: Make sure the plugin is deployed as part of an existing adapter.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60306: Invalid criteria due to invalid filter: {0}.

Cause: The criteria was invalid LDAP filter.

Action: Check criteria syntax and provide a valid filter.
Level: 1

Type: ERROR

Impact: Data

OVD-60307: ERROR copying filter: {0}.

Cause: Error while parsing filter.

Action: Provide a valid filter.
Level: 1

Type: ERROR

Impact: Data

OVD-60308: If the directoryType is configured, an activation attribute is required.

Cause: Activation attribute was missing.

Action: Provide activation attribute.
Level: 1

Type: ERROR

Impact: Data

OVD-60309: If activation is configured, activation values are required.

Cause: Activation attribute was missing.

Action: Provide values for activation attribute.
Level: 1

Type: ERROR

Impact: Data

OVD-60310: If activation is configured, deactivation values are required.

Cause: Deactivation attribute was missing.

Action: Provide values for deactivation attribute.
Level: 1

Type: ERROR

Impact: Data

OVD-60311: Cannot execute mapping.

Cause: Exception encountered while executing mapping.

Action: Ensure that the mapping file is correct.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60312: Cannot instantiate Mapper.

Cause: Failed to instantiate a mapper.

Action: Make sure the mapping file existing and correct.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60314: Cannot generate a filter that always passes.

Cause: Failed to generate an all pass filter.

Action: No action required.
Level: 1

Type: ERROR

Impact: Process

OVD-60315: Cannot adjust filter.

Cause: Failed to reset to an all pass filter.

Action: Check the search request syntax.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60316: Invalid DN Exception creating adapter base entry.

Cause: Incorrect DN specified when creating a new adapter entry.

Action: Make sure a valid DN is specified in adapter configuration.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60317: The version of this system must be greater than or equal to 3.0.2 to run this plug-in.

Cause: The version of plugin was not supported in this version.

Action: Upgrade Oracle Virtual Directory server.
Level: 1

Type: ERROR

Impact: Upgrade

OVD-60318: Failure in appending the new adapter - type : {0}, name : {1}.

Cause: Failed when creating a new adapter instance.

Action: Check syntax of the new adapter.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60319: An attempt to start Oracle Virtual Directory server failed.

Cause: Could not start admin service.

Action: Ensure that the configured admin service port is available.
Level: 1

Type: ERROR

Impact: Ports

OVD-60320: Cannot parse schema {0}.

Cause: Could not parse the specified schema file.

Action: Make sure the schema file exists, and syntax of the schemas are correct.
Level: 1

Type: ERROR

Impact: Data

OVD-60321: Error parsing product version of server configuration.

Cause: Error encountered while checking schema version in server configuration file.

Action: Check schvers in the header of server.os_xml.
Level: 1

Type: ERROR

Impact: Data

OVD-60322: Error parsing adapters. {0}.

Cause: Error encountered while parsing adapter configuration.

Action: Check syntax of adapters.os_xml.
Level: 1

Type: ERROR

Impact: Data

OVD-60323: Error upgrading {0} configuration file.

Cause: Upgrading schema version of the specified configuration file.

Action: Check schvers in the header of the configuration file.
Level: 1

Type: ERROR

Impact: Upgrade

OVD-60324: Cannot load configuration.

Cause: Error encountered while parsing the configuration.

Action: Fix the error.
Level: 1

Type: ERROR

Impact: Data

OVD-60325: Cannot parse schemas.

Cause: Error encountered while parsing schema files.

Action: Fix the error.
Level: 1

Type: ERROR

Impact: Data

OVD-60326: Cannot verify checksums.

Cause: Failed to verify checksum while parsing configuration.

Action: Make sure configuration files exist and correct.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60327: Exception getting provisioned {0}: {1}.

Cause: Error encountered when parsing the specified configuration file.

Action: Correct the error.
Level: 1

Type: ERROR

Impact: Process

OVD-60328: Cannot store {0} configuration.

Cause: Not able to write specified configuration file.

Action: Make sure the file is writable.
Level: 1

Type: ERROR

Impact: Operating System

OVD-60330: Cannot parse DSML.

Cause: Error parsing DSML request.

Action: Make sure the DSML request is properly created.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60331: Failure in LDAP Add.

Cause: Error performing add operation.

Action: Ensure that the servers allows the operation to be performed.
Level: 1

Type: ERROR

Impact: Process

OVD-60332: Failure in LDAP Rename.

Cause: Error while performing moddn operation.

Action: Ensure that the servers allows the operation to be performed.
Level: 1

Type: ERROR

Impact: Process

OVD-60333: Failure in LDAP Modify.

Cause: Error while performing moddn operation.

Action: Ensure that the servers allows the operation to be performed.
Level: 1

Type: ERROR

Impact: Process

OVD-60334: Failure in LDAP Delete.

Cause: Error while performing moddn operation.

Action: Ensure that the servers allows the operation to be performed.
Level: 1

Type: ERROR

Impact: Process

OVD-60335: Failure in getting LDAP 1.

Cause: Failed to connect to LDAP server.

Action: Ensure LDAP server is available.
Level: 1

Type: ERROR

Impact: Network

OVD-60336: Failure in getting LDAP 2.

Cause: Failed to read the next entry in the result.

Action: Ensure that the connection to server is still available.
Level: 1

Type: ERROR

Impact: Network

OVD-60337: Cannot close selector.

Cause: Error while stopping the listener.

Action: Retry stopping the listener.
Level: 1

Type: ERROR

Impact: Network

OVD-60338: Cannot stop ReadSelector.

Cause: Error while stopping the listener.

Action: Retry stopping the listener.
Level: 1

Type: ERROR

Impact: Network

OVD-60339: Null ReadSelector.

Cause: Error while starting the listener.

Action: Retry starting the listener.
Level: 1

Type: ERROR

Impact: Network

OVD-60340: ReadSelector not open.

Cause: Error while starting the listener.

Action: Retry starting the listener.
Level: 1

Type: ERROR

Impact: Network

OVD-60341: Key not ready.

Cause: Error while accepting pending client requests.

Action: Restart the listener and retry.
Level: 1

Type: ERROR

Impact: Process

OVD-60342: Cannot obtain socket from RDS.

Cause: Could not obtain the socket from the Resource Discovery Service.

Action: Contact the Oracle Virtual Directory administrator.
Level: 1

Type: ERROR

Impact: Ports

OVD-60343: Cannot start web listener.

Cause: Could not start the web listener.

Action: Check the Oracle Virtual Directory server logs for more details.
Level: 1

Type: ERROR

Impact: Network

OVD-60344: Error parsing join condition filter: {0}, error: {1}.

Cause: Invalid join condition filter provided.

Action: Provide a valid join condition filter.
Level: 1

Type: ERROR

Impact: Data

OVD-60345: Cannot Load Joined Entry Set: {1}.

Cause: Could not load the joined entry set.

Action: Check Oracle Virtual Directory server logs for more details.
Level: 1

Type: ERROR

Impact: Process

OVD-60346: Critical error while performing ADD {0}.

Cause: Error occured when performing add operation.

Action: Check the error logged to see the exact LDAP error reported.
Level: 1

Type: ERROR

Impact: Process

OVD-60347: Critical error while performing COMPARE {0}.

Cause: Error occured when performing compare operation.

Action: Check the error logged to see the exact LDAP error reported.
Level: 1

Type: ERROR

Impact: Process

OVD-60348: Critical error while performing SEARCH {0}.

Cause: Error occured when performing search operation.

Action: Check the error logged to see the exact LDAP error reported.
Level: 1

Type: ERROR

Impact: Process

OVD-60350: Cannot instantiate the changelog.

Cause: Not supported operation anymore.

Action: No action required.
Level: 1

Type: ERROR

Impact: Process

OVD-60351: Error encrypting passwords in the configuration file.

Cause: Could not encryt the password stored in the configuration file.

Action: No action. Try restarting the server.
Level: 1

Type: ERROR

Impact: Security

OVD-60352: No version 3 schema (".xsd") files located in conf directory. Upgrade aborted.

Cause: Cannot find (".xsd") files.

Action: Make sure (".xsd") files exists in conf directory.
Level: 1

Type: ERROR

Impact: Files

OVD-60353: Error initializing XML: {0}.

Cause: Failed initialize specified configuration file during upgrading.

Action: Make sure the XML files are correct.
Level: 1

Type: ERROR

Impact: Files

OVD-60354: Unable to upgrade version information in server configuration.

Cause: Server could not update the version information in the server configuration.

Action: Restart the server to see if the problem goes away.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60355: An attempt to start Oracle Virtual Directory server failed.

Cause: Cannot start Process Control Service client.

Action: Ensure Process Control Service agent is running.
Level: 1

Type: ERROR

Impact: Process

OVD-60356: Cannot stop the server.

Cause: Error stopping server.

Action: Use PCS service to stop the server.
Level: 1

Type: ERROR

Impact: Process

OVD-60357: Debug license may not be used in standalone server environment.

Cause: Not an issue anymore. .

Action: No action required.
Level: 1

Type: ERROR

Impact: Log

OVD-60358: ThreadWorkGroup is destroyed: {0}.

Cause: The thread group has been destroyed.

Action: No action required.
Level: 1

Type: ERROR

Impact: Threads

OVD-60359: ChainException verifying if user is authenticated.

Cause: Failed when verifying user authentication.

Action: Make sure Oracle Virtual Directory server is running properly.
Level: 1

Type: ERROR

Impact: Security

OVD-60360: Invalid vde.home setting: {0}.

Cause: Not able to find vde.home directory.

Action: Make sure vde.home system property is correct.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60361: Modified against a read-only adapter.

Cause: No read-write backend LDAP server is configured.

Action: Make sure at least one Read/Write host exists in the Remote Hosts list for update operation
Level: 1

Type: ERROR

Impact: Configuration

OVD-60362: Caught LoginException {0}.

Cause: Incorrect login name or password.

Action: Provide correct login name and password.
Level: 1

Type: ERROR

Impact: Programmatic

OVD-60363: Caught NamingException {0}.

Cause: Error while kerberos login.

Action: Contact Oracle Virtual Directory administrator.
Level: 1

Type: ERROR

Impact: Programmatic

OVD-60364: Did not get backend LDAP connection.

Cause: Not able to get connection to LDAP server.

Action: Ensure LDAP server is available and the connection details are correct.
Level: 1

Type: ERROR

Impact: Network

OVD-60365: There is no stub implementation for the interface: {0}.

Cause: The Web Service has no port for the given interface.

Action: Ensure Web Service is running properly.
Level: 1

Type: ERROR

Impact: Programmatic

OVD-60366: Cannot set endpoint address for unknown port {0}.

Cause: The port name was unknown to the service.

Action: Ensure that the Web Service is running properly, and the port name is valid.
Level: 1

Type: ERROR

Impact: Ports

OVD-60367: Object class {0} not defined in server schema. adapter start aborting.

Cause: The specified object class was not defined.

Action: Define object class in server schema.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60368: No backend present for adapter plugins.

Cause: No backend repository available for adapter plugins.

Action: Ensure that the backend of concerned adapters are accessiable.
Level: 1

Type: ERROR

Impact: Network

OVD-60369: An Oracle Virtual Directory Plugin's class must be specified.

Cause: Plugin class element was missing or empty.

Action: Add Plugin class element with proper class name.
Level: 1

Type: ERROR

Impact: Files

OVD-60370: Cannot load the class {0}.

Cause: The specified plugin class not able to be found.

Action: Ensure that the class is in the classpath.
Level: 1

Type: ERROR

Impact: Files

OVD-60371: Cannot instantiate the plugin {0}.

Cause: Failed to instantiate the specified plugin class.

Action: Make sure the plugin class exists and has been properly deployed.
Level: 1

Type: ERROR

Impact: Files

OVD-60372: Illegal access to plugin class.

Cause: The plugin class was not allowed for access.

Action: Make sure proper privilege are set to load/run the plugins.
Level: 1

Type: ERROR

Impact: Security

OVD-60373: Error Parsing at line #{0}: {1}.

Cause: Error occured while parsing configuration files.

Action: Check the configuration file and make correction.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60374: Unknown Element : {0}.

Cause: The specified element did not exist.

Action: Ensure that the element exists in the schema of the concerned object.
Level: 1

Type: ERROR

Impact: Data

OVD-60375: Illegal value : {0} for element: {1}.

Cause: The value did not exist for the specified element.

Action: Provide a valid value for the specified element.
Level: 1

Type: ERROR

Impact: Data

OVD-60376: Listener {0} does not exist.

Cause: No such Listener.

Action: Check the Listener configuration.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60377: No schema supplied.

Cause: No schema supplied.

Action: Provide user schema to write.
Level: 1

Type: ERROR

Impact: Data

OVD-60378: Invalid JAR File.

Cause: The specified JAR file not recognized by Oracle Virtual Directory.

Action: Verify the file name is correct, which should end with zip/jar.
Level: 1

Type: ERROR

Impact: Data

OVD-60379: Unknown syntax {0}, valid values are BinarySyntax,DirectoryString,IA5String,IntegerSyntax.

Cause: Syntax specified was incorrect.

Action: Make sure the syntax specified is one of the valid syntaxes.
Level: 1

Type: ERROR

Impact: Data

OVD-60380: Cannot load syntax.

Cause: Error occured when mapping the syntax.

Action: Ensure syntax is one of BinarySyntax,DirectoryString,IA5String,IntegerSyntax.
Level: 1

Type: ERROR

Impact: Data

OVD-60381: Alias required.

Cause: Alias for the certificate not specified.

Action: Specify the alias for the certificate.
Level: 1

Type: ERROR

Impact: Data

OVD-60382: DN required.

Cause: Operation requires a dn value which was not specified.

Action: Ensure a valid DN value is specified.Eg:cn=Jim Smith,ou=People,o=Division B,c=UK
Level: 1

Type: ERROR

Impact: Data

OVD-60383: Cannot retrieve certificate.

Cause: Error retrieveing X509 Certificate.

Action: Verify if the certificates are provisioned.
Level: 1

Type: ERROR

Impact: Security

OVD-60384: Requested trust manager not supported.

Cause: The trust manager used was not supported.

Action: No action required.
Level: 1

Type: ERROR

Impact: Security

OVD-60385: SSL certificate error.

Cause: The wallet was empty or certificate was not valid.

Action: Use wallet manager or keytool to verify the wallet. The SSL configuration must be setup correctly.
Level: 1

Type: ERROR

Impact: Security

OVD-60386: Cannot load keystore.

Cause: The key store path was wrong or the key store was not readable.

Action: Use a keytool to verify the key store.
Level: 1

Type: ERROR

Impact: Security

OVD-60387: No Remote Servers Available.

Cause: No remote LDAP servers available.

Action: Ensure LDAP servers are available and connection details are correct.
Level: 1

Type: ERROR

Impact: Network

OVD-60388: Attribute type or value exists: {0}.

Cause: Attribute type of value specified already exists.

Action: Ensure that the add of attribute values of attribute is on non-unique values.
Level: 1

Type: ERROR

Impact: Data

OVD-60389: No database connection available in cache to process the request.

Cause: All database connections in the cache are active. No new connection can be created as the maximum limit was reached.

Action: Modify DB adapter configuration to increase the database connection limit.
Level: 1

Type: ERROR

Impact: Session

OVD-60390: Cannot parse Admin Group URL: {0}.

Cause: Invalid LDAP URL format for Admin Group.

Action: Provide a valid LDAP URL format.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60391: No LDAP connection available to process request for DN: {0}.

Cause: All LDAP connections in the cache are active. No new connection can be created as the maximum limit was reached.

Action: Modify LDAP adapter configuration to increase the LDAP connection limit.
Level: 1

Type: ERROR

Impact: Session

OVD-60392: Invalid DN.

Cause: The specified DN has more than 4000 characters.

Action: Check the DN value.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60393: Cannot retrieve database schema.

Cause: Database might not be available.

Action: Validate the database connection.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60394: Syntax {0} not defined.

Cause: Invalid syntax for the attribute.

Action: Correct the syntax for the attribute.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60395: Object ID {0} already in use.

Cause: The oid was already taken by another class.

Action: Use another oid.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60396: Can not retrieve admin credentials.

Cause: Credential Store Framework might be unavailable.

Action: Check Oracle Virtual Directory server log for more detail. Reset admin user name/password in ASCTL.
Level: 1

Type: ERROR

Impact: Security

OVD-60397: Can not set admin credentials.

Cause: Credential Store Framework might be unavailable.

Action: Check Oracle Virtual Directory server log for more detail.
Level: 1

Type: ERROR

Impact: Security

OVD-60398: Can not refresh credentials.

Cause: Credential Store Framework might be unavailable.

Action: Check Oracle Virtual Directory server log for more detail.
Level: 1

Type: ERROR

Impact: Security

OVD-60399: Cannot load Log configuration.

Cause: Log configuration could be invalid.

Action: Verify and fix Log configuration.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60400: Object ID {0} has syntax error.

Cause: The Object ID had an incorrect syntax.

Action: Correct the Object ID.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60401: Password Encryption type {0} not supported

Cause: Oracle Virtual Directory does not support specified Password Encryption type

Action: Change Password Encryption type in backend datasource to one of the supported types
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-60500: Failure in initializing Auditor.

Cause: AuditException happened when initialize Auditor.

Action: Find the cause in the error message and fix it.
Level: 1

Type: ERROR

Impact: Security

OVD-60501: Failure in logging audit message.

Cause: AuditException happened when logging the audit message.

Action: Enlarge the maxFileSize or maxDirSize, or cleanup old audit log files.
Level: 1

Type: ERROR

Impact: Security

OVD-60502: Failure in Auditor shutdown.

Cause: AuditException happened when shutdown Auditor.

Action: Find the cause in the error message and fix it.
Level: 1

Type: ERROR

Impact: Security

OVD-60503: Not able to find component Events file: {0}.

Cause: Not able to find specified file.

Action: Make sure the specified file exists.
Level: 1

Type: ERROR

Impact: Security

OVD-60504: Not able to close component Events file: {0}.

Cause: Not able to close specified file.

Action: Find the cause in the error message.
Level: 1

Type: ERROR

Impact: Security

OVD-60505: Unable to reset admin password or DN.

Cause: Password wallet might be unavailable.

Action: Find the cause in the error message.
Level: 1

Type: ERROR

Impact: Security

OVD-60506: AuditService for Oracle Virtual Directory is Null.

Cause: JPS Configuration for Oracle Virtual Directory AuditService might be wrong.

Action: Validate the JPS configuration file.
Level: 1

Type: ERROR

Impact: Security

OVD-60507: Oracle Virtual Directory Auditor is Null and not properly initialized.

Cause: JPS Configuration for Oracle Virtual Directory AuditService might be wrong.

Action: Validate the JPS configuration file and restart Oracle Virtual Directory server.
Level: 1

Type: ERROR

Impact: Security

OVD-60508: Failure in reloading audit configuration.

Cause: JPS Configuration for Oracle Virtual Directory AuditService might be wrong.

Action: Validate the JPS configuration file and restart Oracle Virtual Directory server.
Level: 1

Type: ERROR

Impact: Configuration

OVD-60509: Failure in auditing {0} operation.

Cause: Error happened while generating auditing message for the operation.

Action: Validate the configuration file, it might fail to be parsed.
Level: 1

Type: ERROR

Impact: Security

OVD-60600: Cannot set password : {0}.

Cause: Exception when set password.

Action: Make sure Oracle Virtual Directory and backend LDAP server are running properly.
Level: 1

Type: ERROR

Impact: Security

OVD-60601: Cannot rollback addition : {0}.

Cause: Exception when rollback addition operation.

Action: Make sure Oracle Virtual Directory and backend LDAP server are running properly.
Level: 1

Type: ERROR

Impact: Programmatic

OVD-60602: Cannot convert.

Cause: The encoding was not supported.

Action: Use supported encoding.
Level: 1

Type: ERROR

Impact: Data

OVD-60603: Message: {0}.

Cause: Error encountered in Jetty Logger.

Action: Restart the Oracle Virtual Directory server.
Level: 1

Type: ERROR

Impact: Log

OVD-60604: Cannot Create SSL Socket Factory.

Cause: Error creating SSL socket.

Action: Verify the backend servers are properly configured for SSL.
Level: 1

Type: ERROR

Impact: Security

OVD-60605: Failure in allocating RDS port {0}.

Cause: Failed in RDS API call to allocate port for Oracle Virtual Directory process.

Action: Ensure MAS instance is running properly.
Level: 1

Type: ERROR

Impact: Ports

OVD-60606: Failure in jaxb process.

Cause: Failed when trying to obtain RDS Socket.

Action: Check MAS instance is running properly.
Level: 1

Type: ERROR

Impact: Ports

OVD-60607: Failure in releasing RDS port {0}.

Cause: Not able to release RDS port.

Action: Make sure MAS and RDS are running properly.
Level: 1

Type: ERROR

Impact: Ports

OVD-60608: Failure in releasing RDS ports.

Cause: Not able to release RDS ports.

Action: Make sure MAS and RDS are running properly.
Level: 1

Type: ERROR

Impact: Ports

OVD-60609: Cannot load key for alias: {0}.

Cause: Failed to load private key.

Action: Make sure the key specified in configuration is the right key.
Level: 1

Type: ERROR

Impact: Security

OVD-60610: Cannot load certificate chain.

Cause: Exception when loading certification chain.

Action: Verify the SSL configuration.
Level: 1

Type: ERROR

Impact: Security

OVD-60611: Invalid LDAP URL

Cause: LDAP URL provided is null or empty

Action: Provide a valid LDAP URL
Level: 1

Type: ERROR

Impact: Data

OVD-60612: LDAP URL does not include ://

Cause: LDAP URL provided is not valid

Action: Provide a valid LDAP URL
Level: 1

Type: ERROR

Impact: Data

OVD-60613: Invalid scheme:

Cause: Invalid protocol scheme provided in LDAP URL

Action: Provide a valid protocol (ldap or ldaps) in LDAP URL
Level: 1

Type: ERROR

Impact: Data

OVD-60614: Missing closing bracket for IPv6

Cause: Invalid IPv6 address due to missing brackets

Action: Provide a valid IPv6 address in LDAP URL
Level: 1

Type: ERROR

Impact: Data

OVD-60615: IPv6 Host is empty

Cause: Invalid IPv6 address due to empty host

Action: Provide a valid IPv6 address
Level: 1

Type: ERROR

Impact: Data

OVD-60616: Unexpected character:

Cause: Invalid IPv6 address due to unexpected character

Action: Provide a valid IPv6 address in LDAP URL
Level: 1

Type: ERROR

Impact: Data

OVD-60617: Port outside valid range

Cause: Invalid port which is outside the valid range

Action: Provide a valid port which is between 1 & 65535 in LDAP URL
Level: 1

Type: ERROR

Impact: Data

OVD-60618: Invalid port number

Cause: Invalid port which is not a number

Action: Provide a valid port which is between 1 & 65535 in LDAP URL
Level: 1

Type: ERROR

Impact: Data

OVD-60619: Invalid attribute list

Cause: Invalid attribute list

Action: Provide a valid attribute list in LDAP URL
Level: 1

Type: ERROR

Impact: Data

OVD-60620: Attribute list ends with comma

Cause: Invalid attribute list that ends with comma

Action: Provide a valid attribute list in LDAP URL
Level: 1

Type: ERROR

Impact: Data

OVD-60621: Invalid search scope

Cause: Invalid seach scope provided in LDAP URL

Action: Provide a valid scope in LDAP URL
Level: 1

Type: ERROR

Impact: Data

OVD-60700: XSL Transform exception ({0}), {1}.

Cause: Error encountered with performins XSL transformation.

Action: Verify the XSLT file.
Level: 1

Type: ERROR

Impact: Data

OVD-60701: Service Configuration Not Present.

Cause: Can not find WebService configuration.

Action: Tag context might be missing from http listener config.
Level: 1

Type: ERROR

Impact: Data

OVD-60702: Cannot load security realm.

Cause: Failed to load security realm.

Action: Ensure security realm is correct in http listener config.
Level: 1

Type: ERROR

Impact: Data

OVD-60703: Cannot Retrieve User Name.

Cause: Failed while getting user name.

Action: Ensure username is provided.
Level: 1

Type: ERROR

Impact: Data

OVD-60704: Could Not Bind, Invalid User Name.

Cause: Bind failed using provided username and password.

Action: Ensure that the username/password are correct.
Level: 1

Type: ERROR

Impact: Data

OVD-60705: Invalid Syntax for Attribute: {0} Attribute Value: {1}.

Cause: Invalid syntax for attribute value.

Action: Ensure that the attribute value has correct syntax.
Level: 1

Type: ERROR

Impact: Data

OVD-60800: Failed to construct user DN

Cause: Error encountered while construct entry DN.

Action: Check the bind user DN
Level: 1

Type: ERROR

Impact: Data

OVD-61252: Alias {0} is not a key in the provided keystore.

Cause: The specified alias was not a key entry in the keystore.

Action: Provide a valid alias from the keystore.
Level: 1

Type: ERROR

Impact: Security

OVD-61258: Admin Domain restricts modification of attribute: {0}.

Cause: Server did not allow addition or modification of operational attributes.

Action: Ensure operational attributes are not added or modified.
Level: 1

Type: ERROR

Impact: Data

OVD-61259: Modifying distinguished value of the entry without modifying the DN.

Cause: Modify operation cannot be used to modify distinguished value of the entry.

Action: Modify DN operation should be used to rename an entry.
Level: 1

Type: ERROR

Impact: Data

OVD-61260: Attribute {0} is not present in the entry.

Cause: Named entry did not contain the specified attribute.

Action: Perform modify operation on attributes present in the entry.
Level: 1

Type: ERROR

Impact: Data

OVD-61261: Attribute {0} does not contain value {1}.

Cause: Named entry did not contain the specified attribute value.

Action: Perform modify operation on attribute values present in the entry.
Level: 1

Type: ERROR

Impact: Data

OVD-61262: Provided value cannot be parsed as a valid distinguished name.

Cause: Distinguished name of the request did not conform to the required syntax.

Action: Ensure that the distinguished name conforms to the required syntax.
Level: 1

Type: ERROR

Impact: Data

OVD-61263: Attribute {0} has no values for entry: {1}

Cause: Named entry has attribute which has no values

Action: Ensure all attributes present in the entry has values
Level: 1

Type: ERROR

Impact: Data

OVD-61264: TLS already established on this connection

Cause: Attempting to perform TLS on TLS enabled connection

Action: TLS not required for this connection
Level: 1

Type: ERROR

Impact: Security

OVD-61265: Outstanding LDAP operations on this connection

Cause: One or more LDAP operations outstanding on this connection

Action: Retry after oustanding operations are completed
Level: 1

Type: ERROR

Impact: Security

OVD-61266: StartTLS cannot be enabled on this connection

Cause: The corresponding LDAP listener is configured to reject StartTLS requests

Action: Enable StartTLS in listener configuration
Level: 1

Type: ERROR

Impact: Security

OVD-61400: Unable to get local host name.

Cause: Not able to query local host name.

Action: Refer Operation System manual to configure host name
Level: 1

Type: ERROR

Impact: Operating System

OVD-61401: Failure in getting DiameterFactory instance.

Cause: Internal error

Action: Check Oracle Virtual Directory log for more information.
Level: 1

Type: ERROR

Impact: Session

OVD-61402: Unable to create Diameter Client Stack.

Cause: Internal error

Action: Check Oracle Virtual Directory log for more information.
Level: 1

Type: ERROR

Impact: Session

OVD-61403: Unable to create listening point for incoming connections.

Cause: Ports might be occupied.

Action: Make sure listening ports are available.
Level: 1

Type: ERROR

Impact: Ports

OVD-61404: Failure in creating routing table.

Cause: Internal error

Action: Check Oracle Virtual Directory log for more information.
Level: 1

Type: ERROR

Impact: Ports

OVD-61405: Failure in CreateAndSendUDR.

Cause: Requested information might be missing to construct Diameter UDR.

Action: Check the request and make sure sufficient information with correct syntax were provided.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-61406: Failure in CreateAndSendPUR.

Cause: Requested information might be missing to construct Diameter PUR

Action: Check the request and make sure sufficient information with correct syntax were provided.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-61407: dataReference String Array is corrupted. Can not create UDR.

Cause: The value of DataReference control was not correct.

Action: Check syntax and value of DataReference control in the request.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-61408: Error while creating UDR.

Cause: Syntax error or missing information to construct UDR.

Action: Check Oracle Virtual Directory log for more information.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-61409: Error while cleaning up Diameter connection.

Cause: Failed to cleanup objects for Diameter connection.

Action: Check Oracle Virtual Directory log for more information.
Level: 1

Type: ERROR

Impact: Process

OVD-61410: No dataReference specified.

Cause: No value provided to DataReference control.

Action: Specify proper value for DataReference control.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-61411: serverName is missing for InitialFilterCriteria.

Cause: serverName value was missing in DataReference control while querying InitialFilterCriteria.

Action: Provide serverName in the DataReference control.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-61412: serviceIndication is missing for RepositoryData.

Cause: serviceIndication was missing in DataReference control while querying RepositoryData.

Action: Specify serviceIndication in the DataReference control.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-61413: Error while creating Diameter connection.

Cause: Not able to create connection to HSS server.

Action: Check Diameter Adapter configuration parameters and make sure they are correct.
Level: 1

Type: ERROR

Impact: Network

OVD-61414: Error while performing modify against Diameter Adapter.

Cause: Failed the ldapmodify operation against HSS server.

Action: Check Oracle Virtual Directory log for more information.
Level: 1

Type: ERROR

Impact: Process

OVD-61415: UnsupportedEncodingException caught when constructing RDN of base entry from filter

Cause: Syntax error of Diameter Adapter root DN.

Action: Correct root DN of the Diameter Adapter.
Level: 1

Type: ERROR

Impact: Data

OVD-61416: Attribute Type {0} is not valid for Diameter Adapter

Cause: The RDN attribute type in search request was not supported in the Diameter Adapter.

Action: Use a valid Diameter RDN in search base DN or filter.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-61417: Can not obtain connection to HSS Service.

Cause: HSS Service was not available

Action: Check if HSS service not available
Level: 1

Type: ERROR

Impact: Network

OVD-61418: Response waiting time exceeded maximum limit.

Cause: Either HSS service was not available or HSS was handling other transaction

Action: Check if HSS service is available, or try again later
Level: 1

Type: ERROR

Impact: Network

OVD-61419: Unknown result. Missing result Code.

Cause: HSS returned a message which did not contain a result code.

Action: Make sure HSS server functions properly.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-61420: Requested data does not exist in the HSS.

Cause: The requested data did not exist in the HSS.

Action: Create the data first before querying it.
Level: 1

Type: ERROR

Impact: Data

OVD-61421: The HSS can not fulfil the received request for reasons unknown: {0}

Cause: HSS server internal error.

Action: Check HSS server for more information.
Level: 1

Type: ERROR

Impact: Process

OVD-61422: The data required in the XML schema does not match what specified within the HSS

Cause: The requested data did not exist in the HSS.

Action: Add the data to the HSS before querying or updating it.
Level: 1

Type: ERROR

Impact: Data

OVD-61423: The RDN attribute of rootDN: {0} is not valid

Cause: The RDN attribute type in the rootDN of the Diameter Aapter was not valid.

Action: Use one of the following attribute as the RDN attribute type: ou, dc, c, cn
Level: 1

Type: ERROR

Impact: Configuration

OVD-61424: The requested operation is not allowed for the user.

Cause: The user was not allowed for the requested operation against the HSS.

Action: Make sure the user has privilege for the operation
Level: 1

Type: ERROR

Impact: Data

OVD-61425: The requested user data is not allowed to be read.

Cause: The data referenced in the request was not allowed to be read.

Action: Make sure the user data in the HSS is allowed to be read.
Level: 1

Type: ERROR

Impact: Data

OVD-61426: The requested user data is not allowed to be modified.

Cause: The data in the HSS was not allowed to be updated.

Action: Check the HSS that the UUP is permitted to update the referenced data.
Level: 1

Type: ERROR

Impact: Data

OVD-61427: The size of the data pushed to the receiving entity exceeded its capacity.

Cause: There was more data than the HSS is prepared to accept.

Action: Reduce the size of the data in the update request.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-61428: The request to update the repository data at the HSS could not be completed.

Cause: The requested update was based on an out-of-date version of the HSS repository schema.

Action: Execute a query to retrieve the current version of the data from the HSS.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-61429: The requested user data is not available at this time to satisfy the requested operation.

Cause: The requested user data was not available at this time to satisfy the requested operation.

Action: Check the request is against an existing user.
Level: 1

Type: ERROR

Impact: Data

OVD-61430: The request to update the repository data at the HSS could not be completed.

Cause: The related repository data was being updated by another entity.

Action: None
Level: 1

Type: ERROR

Impact: Data

OVD-61431: Search Operation Failure in Parsing HSS Data Reference Control.

Cause: Syntax error.

Action: Verify syntax of specified DataReference control.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-61432: Missing mandatory parameter: remotePeers.

Cause: remotePeers parameter was missing from Diameter adapter plugin configuration.

Action: Edit plugin and add remotePeers parameter.
Level: 1

Type: ERROR

Impact: Configuration

OVD-61433: Invalid value for the DiameterAdapter plug-in interface parameter: {0}

Cause: The interface parameter specified in the DiameterAdapter plug-in was not supported.

Action: The valid DiameterAdapter plugin-in interface parameters are: [Sh, Cx, Dx, Ro, Rf, Base]
Level: 1

Type: ERROR

Impact: Configuration

OVD-61434: Cannot retrieve XSS Ruleset for this URL {0}.

Cause: Failed to retrieve the rule set for this URL .

Action: Set the rule set and try again later.
Level: 1

Type: ERROR

Impact: Configuration

OVD-61600: Invalid operation for anonymous user.

Cause: The requested operation is not allowed to anonymous users.

Action: Refer product documents for details.
Level: 1

Type: ERROR

Impact: Requests/Responses

OVD-80001: An attempt to start Oracle Virtual Directory server failed.

Cause: One or more mandatory system properties are missing.

Action: Ensure that all mandatory system properties are set.
Level: 1

Type: ERROR

Impact: Process

OVD-80002: System Exiting....

Cause: The system was shut down because of missing plug-in files.

Action: Ensure that the plugins that are configured, the plugin source is available.
Level: 1

Type: ERROR

Impact: Process

OVD-80003: Fatal Error! Downgrading configuration not supported.

Cause: Changing configuration file schema version to older value.

Action: Make sure the new schema version is greater than the current schvers in configuration files.
Level: 1

Type: ERROR

Impact: Configuration

OVD-80004: Errors occurred while parsing {0}. Correct before starting. Shutting down...

Cause: Syntax errors in the specified configuration file.

Action: Correct the syntax errors in the configuration file.
Level: 1

Type: ERROR

Impact: Configuration

OVD-80005: Cannot read file : {0}.

Cause: Not able to open the specified file.

Action: Make sure the file exists and accessible.
Level: 1

Type: ERROR

Impact: Operating System

OVD-80006: Parse Error : {0}.

Cause: Error parsing configuration xml file.

Action: Correct the parsing error.
Level: 1

Type: ERROR

Impact: Configuration

OVD-80007: Errors occurred while parsing adapters. Correct before starting.

Cause: Error in parsing adapters.os_xml file.

Action: Correct the adapters.os_xml.
Level: 1

Type: ERROR

Impact: Configuration

OVD-80008: Configuration Error: {0} - {1}.

Cause: Error encountered when loading the configuration file.

Action: Make sure the configuration file is correct.
Level: 1

Type: ERROR

Impact: Configuration

OVD-80009: Errors occurred while parsing listeners. Correct before starting.

Cause: Error encountered when loading the listener configuration file.

Action: Correct the listeners.os_xml file.
Level: 1

Type: ERROR

Impact: Configuration

OVD-80010: Errors occurred while parsing the server configuration.

Cause: Error encountered when loading the server configuration file.

Action: Correct the errors in server.os_xml file.
Level: 1

Type: ERROR

Impact: Configuration

OVD-80011: Cannot parse Adapters.

Cause: Error occured when parsing adapters configuration.

Action: Check the adapters configuration.
Level: 1

Type: ERROR

Impact: Configuration

OVD-80012: Invalid data file: {0}.

Cause: Filename specified in configuration was invalid.

Action: Provide valid filename in configuration.
Level: 1

Type: ERROR

Impact: Configuration

OVD-80013: Configuration handler failure: {0}.

Cause: Configuration files might be missing.

Action: Make sure configuration files are in the right directory.
Level: 1

Type: ERROR

Impact: Configuration

OVD-80014: EUS Reversible Password Configuration Error: {0}.

Cause: Could not retrieve reversible password from the backend LDAP server.

Action: Make sure the EUS configuration for the backend LDAP server is done correctly.
Level: 1

Type: ERROR

Impact: Configuration

OVD-80015: Null admin user.

Cause: The admin user was null.

Action: Make sure that you have a valid CSF configuration containing admin user and password.
Level: 1

Type: ERROR

Impact: Configuration

77 OWS-00001 to OWS-65005

OWS-00001: The state of {0} is now: complete

Cause:

Action:
Level: 32

Type: TRACE

Impact: Data

OWS-00002: {0}, {1} waiting on: {2}

Cause:

Action:
Level: 32

Type: TRACE

Impact: Data

OWS-00003: {0} notifying: {1}, {2} of past creation

Cause:

Action:
Level: 32

Type: TRACE

Impact: Data

OWS-00004: {0} notifying: {1}, {2} of past initialization

Cause:

Action:
Level: 32

Type: TRACE

Impact: Data

OWS-00005: {0} notifying: {1}, {2} of past completion

Cause:

Action:
Level: 32

Type: TRACE

Impact: Data

OWS-00006: {0} now has {1} construction gates, {2} initialization gates, and {3} completion gates

Cause:

Action:
Level: 32

Type: TRACE

Impact: Data

OWS-00007: event: {0} at: {1}

Cause:

Action:
Level: 32

Type: TRACE

Impact: Data

OWS-00008: {0} has: {1} construction gates left

Cause:

Action:
Level: 32

Type: TRACE

Impact: Data

OWS-00009: {0} has: {1} initialization gates left

Cause:

Action:
Level: 32

Type: TRACE

Impact: Data

OWS-00010: {0} has: {1} completion gates left

Cause:

Action:
Level: 32

Type: TRACE

Impact: Data

OWS-00011: {0} has been created

Cause:

Action:
Level: 32

Type: TRACE

Impact: Data

OWS-00012: {0} has been initialized

Cause:

Action:
Level: 32

Type: TRACE

Impact: Data

OWS-00013: {0} has been completed

Cause:

Action:
Level: 32

Type: TRACE

Impact: Data

OWS-00014: notifying: {0}

Cause:

Action:
Level: 32

Type: TRACE

Impact: Data

OWS-00015: {0} has been read

Cause:

Action:
Level: 32

Type: TRACE

Impact: Data

OWS-00016: no method to retrieve the daylight savings offset (getDSTSavings) defined on TimeZone

Cause: Oracle did not find a method for setting daylight savings time for the default timezone on this system.

Action: Check that default timezone is set correctly. Check that the Java Runtime Environment(TM) (JRE) that is used is complete.
Level: 1

Type: ERROR

Impact: Configuration

OWS-00017: literal ArraySerializer.initialize error encountered: Exception message is {0} Stack trace is {1}

Cause: Could not initialize Literal Array Serializer for JAXRPC databinding

Action: System Internal Error - Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Programmatic

OWS-00018: getElementDateValue exception {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Data

OWS-00019: DOM Exception from removeElement {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Data

OWS-00020: problem found in XML parsing: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Data

OWS-00021: Error creating XML mapping factory: {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

OWS-00022: The WSDL generator can process only one service at a time. The first service is used.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

OWS-00023: could not copy {0} to {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Files

OWS-00024: {0} Failed to load dependent class: {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

OWS-00025: Exception converting WSDL types to XML Schema: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Data

OWS-00028: Warning while processing WSM client configuration: {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OWS-00029: Error reading WSM client configuration file: {0}.

Cause: The client side proprietry descriptor is invalid

Action: Validate the client properietary descriprtor as per the schema "http://xmlns.oracle.com/oracleas/schema/11/oracle-webservices-client-11_1.xsd"
Level: 1

Type: ERROR

Impact: Configuration

OWS-00030: Failed to find wsm client configuration file {0}

Cause: The user specified client side oracle webservices proprietary configuration file is missing.

Action: Ensure the valid location of client side config file is provided or it's available in classpath
Level: 1

Type: ERROR

Impact: Configuration

OWS-00031: Warning while processing WSM server configuration: {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OWS-00032: Error reading WSM server configuration file: {0}.

Cause: Cannot read WSM server configuration file

Action: Ensure given WSM configuration file(Oracle proprietry descriptor) at server side is valid
Level: 1

Type: ERROR

Impact: Configuration

OWS-00033: Failed to find deployment descriptor file {0}

Cause: Could not find deployment descriptor file

Action: Ensure server side deployment descriptor file is not missing
Level: 1

Type: ERROR

Impact: Configuration

OWS-00034: <input> element of operation "{0}" in binding "{1}" does not define name attribute. The default name "{2}" does not match the name defined in the corresponding portType section: "{3}". Add name attribute in the <input> element using same value in portType to achieve interoperability.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OWS-00035: <output> element of operation "{0}" in binding "{1}" does not define name attribute. The default name "{2}" does not match the name defined in the corresponding portType section: "{3}" Add name attribute in the <output> element using same value in PortType to achieve interoperability.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OWS-00036: XML fragment top level tag name "{0}" has been corrected to "{1}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Data

OWS-00037: No method found in SEI: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

OWS-00038: A WSDL port in the model is missing a name

Cause:

Action:
Level: 1

Type: WARNING

Impact: Data

OWS-00039: The schema using the namespace of {0} may cause unexpected failures, use {1} instead.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Data

OWS-00040: The element {0} in the supplied deployment descriptor will be ignored.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OWS-00041: Since no @WebMethod was found, all public, non static and non final methods in the class {0} will be exposed in the webservices/WSDL.

Cause:

Action:
Level: 32

Type: TRACE

Impact: Programmatic

OWS-00042: Ignoring method {0}: {1}

Cause:

Action:
Level: 32

Type: TRACE

Impact: Programmatic

OWS-00043: The WSDL contains a mixture of document and rpc styles, the generated WSDL will need to be modified to work correctly.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Data

OWS-00044: There is no management configuration for service: {0} in supplied proprietary deployment descriptor {1}, make sure the service name is correct

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OWS-00045: {0} does not have all the getter and setter methods. Set overwriteBeans to true to allow re-generation of correct value type class.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OWS-00046: Cannot update web.xml file, <url-pattern> {0} already exists.

Cause: The file output/war/WEB-INF/web.xml already contains a URL pattern that the system wants to use for another servlet mapping.

Action: Specify a unique uri argument or change the url-pattern in the existing web.xml.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00047: Could not update web.xml because <servlet-name> "{0}" already exists. The value of <servlet-name> generated by Web Services Assembler is the port name. If bottom-up assembly is used, specify a portName argument value that does not already exist. If topdown assembly or the genDDs command is used, put the two Web services in different WAR files, so that they do not share deployment descriptors.

Cause: The file output/war/WEB-INF/web.xml contained the URL and it was assigned to another servlet.

Action: For bottom-up assembly specify a different portName. For top-down assembly or genDDs separate two Web services into different WAR files or change the name of the servlet in the web.xml file.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00048: Could not update webservices.xml because <webservice-description-name> "{0}" already exists. The value of the <webservice-description-name> generated by Web Services Assembler is always the service name. If bottom-up assembly is used, specify a serviceName argument value that does not already exist. If topdown assembly or the genDDs command is used, put the two Web services in different WAR files so they do not share deployment descriptors.

Cause: The file output/war/WEB-INF/webservices.xml already contains a webservice-description-name. The system wants to re-use this name for a new Web service. The value of the <webservice-description-name> generated by the system is always the service name.

Action: If bottom-up assembly is used, specify a serviceName argument value that does not already exist. If top-down assembly or the genDDs command is used, put the two Web services in different WAR files, so that they do not share deployment descriptors.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00049: Could not update webservices.xml because <port-component-name> "{0}" already exists. The value of <port-component-name> generated by Web Services Assembler is always the port name. If bottom-up assembly is used, specify a portName argument value that does not already exist. If topdown assembly or the genDDs command is used, put the two Web services in different WAR files, so they do not share deployment descriptors.

Cause: The file output/war/WEB-INF/webservices.xml already contains a port-component-name that the system wants to use for a new port. The value of the <port-component-name> generated by the system is always the port name.

Action: If bottom-up assembly is used, specify a portName argument value that does not already exist. If top-down assembly or the genDDs command is used, put the two Web services in different WAR files, so that they do not share deployment descriptors.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00050: Could not update oracle-webservices.xml because <webservice-description> name "{0}" already exists.The name of the <webservice-description> generated by Web Services Assembler is always the service name. If bottom-up assembly is used, specify a serviceName argument value that does not already exist. If topdown assembly or the genDDs command is used, put the two Web services in different WAR files, so they do not share deployment descriptors.

Cause: The file output/war/WEB-INF/oracle-webservices.xml already contains a webservice-description-name that the system wants to use for a new webservice. The value of the <webservice-description-name> generated by the system is always the service name.

Action: If bottom-up assembly is used, specify a serviceName argument value that does not already exist. If top-down assembly or the genDDs command is used, put the two Web services in different WAR files so they do not share deployment descriptors.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00051: Could not update oracle-webservices.xml because <port-component> name "{0}" already exists. The value of <port-component> name generated by Web Services Assembler is always the port name. If bottom-up assembly is used, specify a portName argument value that does not already exist. If topdown assembly or the genDDs command is used, put the two Web services in different WAR files so they do not share deployment descriptors.

Cause: The file output/war/WEB-INF/webservices.xml already contains a port-component name that the system wants to use for a new port. The value of the <port-component> name generated by the system is always the port name.

Action: If bottom-up assembly is used, specify a portName argument value that does not already exist. If top-down assembly or the genDDs command is used, put the two Web services in different WAR files so they do not share deployment descriptors.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00052: Could not update oracle-webservices.xml because <endpoint-address-uri> "{0}" already exists. Specify a uri argument value that does not already exist.

Cause: The file output/war/WEB-INF/oracle-webservices.xml already contains an endpoint-address-uri that the system wants to use for a new webservice port.

Action: Specify a uri argument value that does not already exist.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00053: The wire signature of operation by name "{0}" is same as operation by name "{1}". This does not conform to WS-I Basic Profile v1.1. R2710: The operations in a wsdl:binding in a description MUST result in wire signatures that are different from one another. An endpoint that supports multiple operations must unambiguously identify the operation being invoked based on the input message that it receives. This is only possible if all the operations specified in the wsdl:binding associated with an endpoint have a unique wire signature.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

OWS-00054: When "linkReceiveWithReplyTo" is true, either receive destination/connection-factory or reply-to destination/connection-factory must be set.

Cause: The linkReceiveWithReplyTo argument requires the receive or reply-to arguments defined so the system can make the values the same.

Action: Specify replyToConnectionFactoryLocation and (replyToQueueLocation or replyToTopicLocation) or specify receiveConnectionFactoryLocation and ( receiveQueueLocation or receiveTopicLocation).
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00055: When "linkReceiveWithReplyTo" is true, the value of parameter "{0}" and parameter "{1}" should be same.

Cause: When the argument linkReceiveWithReplyTo is set to true and both replyTo* and receive* arguments are specified they must have the same value.

Action: Either remove one of the arguments shown in the message or set the arguments to the same value.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00056: JMS delivery mode "{0}" is invalid, ignore this setting.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OWS-00057: The received SOAP fault contains non standard fault element: "{0}". This element will be ignored.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Data

OWS-00058: The class "{0}" exists, but could not be loaded.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OWS-00059: Ignoring method "{1}" in SEI "{0}" because it is not JAX-RPC compliant. The reason is "{2}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

OWS-00060: Ignoring property name "{0}" in Java exception "{1}" because it is not JAX-RPC compliant

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

OWS-00061: Ignoring property name "{0}" in Java class "{1}" because it is not JAX-RPC compliant

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

OWS-00062: Ignoring exception of type "{0}" in Java method "{1}" because it is not JAX-RPC compliant

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

OWS-00063: File: "{0}" will be overwritten.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Files

OWS-00064: Attribute "schemaLocation" is not present on a schema import element.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OWS-00065: Interface "{0}" is not JAX-RPC compliant: it does not extend java.rmi.Remote.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

OWS-00066: Method "{0}" is not JAX-RPC compliant: it does not throw java.rmi.RemoteException.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

OWS-00067: There is no management configuration for port {0} in the supplied proprietary deployment descriptor. Ensure the port name is correct.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OWS-00068: found WSDL location property. The WSDL: {0} will be used.

Cause:

Action:
Level: 16

Type: TRACE

Impact: Configuration

OWS-00069: Applying custom type mapping from schema type {0} to java class {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

OWS-00070: No matching type found for the custom type mapping with QName {0}

Cause: A custom type has been defined in an oracle-webservices.xml file but no associated type can be found in the schemas associated with the webservice.

Action: Remove the custom type mapping or correct the name of the custom type mapping so it matches a type in the schema.
Level: 1

Type: WARNING

Impact: Configuration

OWS-00071: Custom type mappings for global elements are not supported. The custom type mapping with the QName of {0} will not be applied to the global element.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OWS-00072: unexpected encoding style: expected='{0}', actual='{1}'

Cause:

Action:
Level: 16

Type: TRACE

Impact: Configuration

OWS-00073: A failure occurred during Oracle Web Services Management agent interceptor {0} processing. {1}

Cause: Could not process Oracle Web Services Management Agent interceptor

Action: System Internal Error - Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00074: {0} does not have all the getter and setter methods. Ensure the user defined class matches type {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OWS-00075: Schema with schema namespace {0} is not supported

Cause:

Action:
Level: 1

Type: WARNING

Impact: Data

OWS-00076: The service implementation class: {0} does not implement java.io.Serializable. This class is not suitable for clustered environments indicated by the argument recoverable=true.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

OWS-00077: The Value Type class: {0} does not have a valid Java Bean pattern.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

OWS-00078: Oracle Web Services Management agent interceptor processing request message.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

OWS-00079: Oracle Web Services Management agent interceptor processing response message.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

OWS-00080: Oracle Web Services Management agent interceptor processing fault message.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

OWS-00081: Attempting to load Oracle Web Services Management agent via loader {0}[{1}].

Cause:

Action:
Level: 16

Type: TRACE

Impact: Configuration

OWS-00082: Loaded Oracle Web Services Management agent via loader {0}[{1}].

Cause:

Action:
Level: 1

Type: TRACE

Impact: Configuration

OWS-00083: Failed to load Oracle Web Services Management agent via loader {0}[{1}]. The cause was: {2}. Will attempt to use other loaders.

Cause:

Action:
Level: 16

Type: TRACE

Impact: Configuration

OWS-00084: Failed to find Oracle Web Services Management agent configuration {0}

Cause: Could not find Oracle Web Services Management agent configuration file

Action: Ensure correct location of OWSM agent configuration file is provided
Level: 1

Type: ERROR

Impact: Files

OWS-00085: The schema element {0} is not supported. The type {1} uses this schema element and will be ignored.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Data

OWS-00086: The nested generic type {0} is not supported.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Data

OWS-00101: Mapped {0} to javax.xml.soap.SOAPElement.

Cause: The system defaults to a SOAP element, since it could not determine how to map the specified schema type to a Java Bean.

Action: Switching to a different data binding like JAXB may allow the system to create Java objects for the type.
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00102: Mapped {0} to javax.xml.soap.SOAPElement{2}. Reason for not creating a custom Java type: {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OWS-00103: nested model group is not supported.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00104: namespace name constraint is not supported (except for ##any, ##other).

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00105: choice is not supported.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00106: wildcard or element is not supported.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00107: multiple occurrences are not supported.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00108: simple or mixed content is not supported.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00109: a mismatch was detected in the parent type.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00110: an unsupported simple type.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00111: expected a soap-enc type.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00112: found a simple type with attributes.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00113: mixed content was seen, this may not be a valid SOAP type.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00114: use of an unimplemented feature.

Cause: An unimplemented feature is used in the schema.

Action: Avoid the unimplemented feature or use the SAAJ API to construct the XML element.
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00115: the base type is not supported.

Cause: An unimplemented feature is used in the base type definition.

Action: Avoid the unimplemented feature or use the SAAJ API to construct the XML element.
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00116: Adding new import: "{0}"

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

OWS-00117: Leaving import as is: "{0}"

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-00118: Adding new field: "{0}"

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

OWS-00119: Deleting field: "{0}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00120: Marking field for deletion: "{0}"

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

OWS-00121: Leaving unused field as is: "{0}"

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

OWS-00122: Adding new annotation: "{0}" to {1} "{2}"

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

OWS-00123: Replacing annotation "{0}" with new annotation of type "{1}" having value {2} "{3}"

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

OWS-00124: Leaving user added annotation "{0}" as is that is of type {1} having value "{2}"

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-00125: Adding new method: "{0}"

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

OWS-00126: Deleting unused method: "{0}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00127: Marking unused method for deletion: "{0}"

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

OWS-00128: Leaving unused method as is: "{0}"

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

OWS-00129: Changing parameter type of "{0}" from "{1}" to "{2}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00130: Adding new parameter "{0}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00131: Deleting old parameter "{0}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00132: Changing return type of "{0}" from "{1}" to "{2}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00133: Changing access control of "{0}" "{1}" from "{2}" to "{3}"

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

OWS-00134: Adding modifier "{0}" to "{1}" "{2}"

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

OWS-00136: Adding initializer "{0}" to field "{1}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00137: Removing initializer "{0}" from field "{1}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00138: Changing initializer of field "{0}" from "{1}" to "{2}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00139: The body of the method by name "{0}" could not be merged. The new method required code is "{1}"

Cause: During top-down generation JDeveloper could not merge the generated code and modified code.

Action: None
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00140: No body expected for the method "{0}".

Cause: During top-down generation JDeveloper found unexpected code in the Java source file provided by the user.

Action: None
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00141: HTTP transport error: {0}

Cause: Error while getting the SOAPConnectionFactory object due to unsupported SAAJ communication infrastructure

Action: System Internal Error - Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00142: local transport error: {0}

Cause: Error occcured while processing request

Action: System Internal Error - Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00143: service error: {0}

Cause: Service Invocation failed. It might be because of an error while generating the stub implementation class or a dynamic proxy.

Action: None
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00144: not an interface: {0}

Cause: In the createService(Class serviceInterface, QName name) method client code has provided an interface that is not a Service interface.

Action: Ensure that the supplied interface extends javax.xml.rpc.Service
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00145: cannot locate service implementation class for service: {0}

Cause: An error occurred while generating a stub implementation class or a dynamic proxy. The service implementation class could not be found in the classpath.

Action: Ensure that the service implementation class is available in the classpath.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00146: failed to create service implementation instance: {0}

Cause: An error occurred while generating a stub implementation class or a dynamic proxy. The service implementation class does not implement a conctere service interface and thus could not be instantiated.

Action: Ensure that specified service implementation class implements JAXRPC service interface and it's available in the classpath.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00147: dynamic invocation error: {0}

Cause: Unexpected Error while invoking the service method.

Action: Ensure that the DII client that invoking the serivce is configured correctly.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00148: service: {0} does not contain port: {1}

Cause: Service Invocation failed because the <wsdl:service> element does not contain any ports.

Action: Ensure that the <wsdl:service> element has atleast one port defined.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00149: port: {0} does not contain operation: {1}

Cause: Service Invocation failed because service endpoint does not contain specified operation.

Action: Ensure that DII client invoking the operation that advertised in the service descriptor i.e WSDL.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00150: property: "{0}" must be set on a Call object before it can be invoked in this configuration

Cause: The Dynamic Invocation Interface (DII) client has not set the required property on the Call object.

Action: For DII client, ensure that all required properties are set correctly on Call object before invoking service.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00156: call object cannot be created without a TypeRegistry

Cause: Service Invocation failed because the InternalTypeMappingRegistry for serialization/deserialization provided to the Call object is null

Action: System Internal Error - Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00157: cannot set unrecognized property: {0} on a Call object

Cause: Client code is trying to set a property that is not specified for Call objects.

Action: Check the name of the property that is being set. Use only properties specified for Call objects.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00158: cannot get unrecognized property: {0} on a Call object

Cause: Client code is trying to get a property that is not specified for Call objects.

Action: Check the name of the property that client side code is trying to access. Use only properties specified for Call objects.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00159: WSDL data missing, this operation is not available

Cause: An unconfigured Dynamic Invocation Interface (DII) client is using the getCalls(Qname portName) method on a Service object that does not have an associated WSDL.

Action: Either use a fully configured DII client, or use a createCall() method that explicitly specifies all required port and operation information to create a Call object instance.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00160: WSDL data missing, {0}

Cause: An unconfigured (Dynamic Invocation Interface (DII) client uses getPort method on Service Implementation object which is not supported when WSDL information is missing

Action: Use the configured DII client by getting the service implementation object using creteService(java.net.URL wsdlDocLoc, QName name) method on ServiceFactory object
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00161: output parameters are only available after invoke() has been called

Cause: Dynamic Invocation Interface (DII) client code is trying to get the output parameters before invoking the service

Action: Ensure that the client code has invoked the service first before accessing the value of output parameters.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00162: cannot set parameter or return types on this Call object

Cause: Dynamic Invocation Interface (DII) client attempted to set parameter or return types on a Call object when service operation does not require input parameter and does not return anything.

Action: Check whether Call obect requires to set parameter or return type by calling isParameterAndReturnSpecRequired() on Call object
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00163: operation style: "{0}" not supported

Cause: Dynamic Invocation Interface (DII) Client sets the Call.OPERATION_STYLE_PROPERTY to other than 'rpc' or 'document'

Action: Set Call.OPERATION_STYLE_PROPERTY to either 'rpc' or 'document'
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00164: encoding style: "{0}" not supported

Cause: Dynamic Invocation Interface (DII) client sets the ENCODINGSTYLE_URI_PROPERTY to an unsupported value i.e other than 'http://schemas.xmlsoap.org/soap/encoding' or null

Action: Use either 'encoded' or 'literal' encoding style.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00165: could not find service: {0} in the specified WSDL file. The service names found were: {1}

Cause: Service name provided by client code is not available in the specified WSDL.

Action: Check the Service name used by the client code and ensure that correct Service name is used as per the specified WSDL.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00166: could not dispatch to method: {0} known methods are: {1}

Cause: Operation that Dynamic Invocation Interface (DII) client code is trying to invoke does not not match with any operation provided by the service.

Action: Make sure correct Operation name is used by the DII client code while configuring Call Object.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00167: The attachment DataHandler object cannot be null

Cause: The attachment DataHandler object cannot be null

Action: Make sure DataHandler attached to Call object is not null
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00168: error.build.wsdl.model: {0}

Cause: Error in the WSDL Model generation at the client side during service invocation. The useWSI property was set to true, but the WSDL does not conform to the WSI basic profile.

Action: Ensure that the specified WSDL is compliant to Web Services Interoperability(WS-I) Basic Profile.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00169: Wrong value type {0} for property {1}. java.io.File or org.w3c.dom.Element is expected

Cause: An unexpected value was set on a Call object. The value must be either of type java.io.File or of type org.w3c.dom.Element.

Action: Check the type of the value being set on the Call object.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00170: serialization error: {0}

Cause: Serializer class is missing.

Action: Make sure the serializer class is defined and available from the classpath.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00171: deserialization error: {0}

Cause: Deserializer failed.

Action: Check the incoming message.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00172: encoding error: {0}

Cause: Failed to initialize dynamic serializer/deserializer for RPC/ENC request

Action: System Internal Error - Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00173: malformed array type: {0}

Cause: The arrayType attribute is missing.

Action: Check the incoming message.
Level: 1

Type: ERROR

Impact: Requests/Responses

Cause: The array index is less than 0 or the end index is less than the start index.

Action: Check the incoming message.

OWS-00174: serialized array has too many elements

Cause: At least one array element position is outside the array boundaries in the inbound message.

Action: Check the incoming message
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00175: illegal array element position: {0}

Cause: Either the array dimension is empty and the element position is not one, or the array dimension length is not equal to the element position length.

Action: Check the incoming message
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00176: missing array position attribute

Cause: Sparse array does not have a position attribute

Action: Check the incoming message
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00177: array element position is out of bounds: {0}

Cause: An array position value is outside the array bounds

Action: Check the incoming message
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00178: unexpected null value during serialization or deserialization

Cause: Serializer cannot serialize a null object for a non-nillable parameter.

Action: Make sure the parameter is not null.
Level: 1

Type: ERROR

Impact: Requests/Responses

Cause: Deserializer cannot deserialize null to a non-nillable object.

Action: Check the incoming message.

OWS-00179: Unexpected error while processing a SOAP Message during {0}, message={1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Data

OWS-00180: unexpected reference element during deserialization; the element "{0}" is not defined as a referenceable type

Cause: Failed to deserialize the request message. The request element uses a reference type which is not specified in the WSDL.

Action: Correct the WSDL definition or correct the request message.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00181: unexpected element type: expected={0}, actual={1}

Cause: Failed to deserialize the request message. The request element type does not match what is defined in the WSDL.

Action: Correct the WSDL definition or correct the request message.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00182: unexpected element name: expected={0}, actual={1}

Cause: Failed to deserialize the request message. The request element name does not match what is defined in the WSDL.

Action: Correct the WSDL definition or correct the request message.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00183: unexpected array element type: expected={0}, actual={1}

Cause: The type of an array element does not match its definition in the schema.

Action: Verify that the type of the array element being sent matches the type defined in the schema.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00184: non-local reference (href): {0}

Cause: The href attribute, used to reference an attachment, is not specified using the "cid" (Content-ID) protocol string.

Action: Change the value of the href attribute, used to reference an attachment, to a string that begins with "cid:".
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00185: trailing block elements must have an id attribute

Cause: An element in the SOAP message contains a reference to another element. However no element was found with an id attribute matching the reference.

Action: Validate the correctness of the received message.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00186: malformed array dimensions: {0}

Cause: The dimensions of the array specified in the SOAP message cannot be translated into a valid number.

Action: Verify that the SOAP-ENC:arrayType attribute (for SOAP 1.1) or the arraySize attribute (for SOAP 1.2) is valid.
Level: 1

Type: ERROR

Impact: Requests/Responses

Cause: The bounds of the array are invalid. For example the lower bound of the array is larger than the upper bound.

Action: See error message.

OWS-00187: multi-dimensional array is not regular

Cause: One level in a multi-dimensional array instance is null or contains an invalid size.

Action: Ensure that all levels of the multi-dimensional array conatin valid values.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00188: illegal array offset: {0}

Cause: The value specified in the "offset" attribute of an array element is invalid.

Action: Ensure that the value specified in the offset attribute of the array element in the SOAP message is within the range of the array dimensions.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00189: array has unexpected rank: expected={0}, actual={1}, arrayType={2}

Cause: The rank of an array does not match the rank specified in the schema.

Action: Verify that that the soapenc:rank attribute of the array element in the schema matches with the actual dimensions of the array in the SOAPMessage.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00190: array has unexpected dimensions: expected={0}, actual={1}, arrayType={2}

Cause: The dimensions of an array in the SOAP element do not match those of the element defined in the Schema.

Action: Verify that the SOAP message matches the WSDL definition
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00191: unexpected encoding style: expected={0}, actual={1}

Cause: The encoding style being used in the message is invalid for the SOAP version. For example, SOAP 1.1 expects the encoding style http://schemas.xmlsoap.org/soap/encoding/ while SOAP 1.2 expects a range of values, one of which is http://www.w3.org/2003/05/soap-encoding.

Action: Ensure that the encoding style uri of the SOAP message is valid for the version of SOAP in use. Check the SOAP 1.1 and SOAP 1.2 for acceptable values.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00192: cannot encode XML type because it was not specified

Cause: Unable to find XML type for object.

Action: System Internal Error - Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00193: member {0} has already been defined

Cause: While deserializing the SOAP message a duplicate member variable or setter/getter was found in the target object.

Action: System Internal Error - Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00194: incomplete object encountered while deserializing

Cause: Failure during deserialization (XML to Java).

Action: System Internal Error - Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00195: circular reference detected while serializing: {0}

Cause: An object is referenced from another object that it references. For example A->B->A. This circular reference is not supported in RPC-Literal or Doc-Literal web services.

Action: Remove the circular dependency or change the web service to RPC-Encoded.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00196: no attachment with cid (Content-ID) "{0}" found in message

Cause: The cid (Content-ID) for a particular attachment that was referenced from the SOAP body was not found.

Action: Make sure that the cid is formatted properly. Examine the cid in the soap body with the Content-Id header of the SOAP Message MIME attachment and verify that they match.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00197: multiple attachments with the same cid (Content-ID) "{0}" found in message

Cause: Found multiple attachments with the same cid (Content-ID). This field must be unique

Action: If the SOAP message was manually constructed, verify that all the Content-ID headers contain a unique value.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00198: missing cid (Content-ID header) for attachment

Cause: An attachment was missing the Content-Id header.

Action: Examine the SOAP message and verify that all Content-Id headers contain a value.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00199: non "cid:" (Content-ID) reference: {0}

Cause: A SwaRef attachment was found with an invalid reference to a MIME attachment. MIME attachment references must begin with the string "cid:".

Action: Verify that the attachment reference begins with "cid".
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00203: serializeAsAttachment specified but no AttachmentEncoder was provided for type: "{0}"

Cause: Missing serializer for a particular attachment type.

Action: System Internal Error - Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00204: a deserializer must be registered with a deserialization state before it will accept listeners

Cause: A serializer class was not found during initialization of the serializer framework.

Action: System Internal Error - Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00205: cannot decode XML type "{0}"

Cause: Unable to construct an object from an XML instance (element).

Action: System Internal Error - Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00206: cannot serialize type "{0}"

Cause: An appropriate default serializer for the specified type could not be found.

Action: A custom serializer must be used for the indicated type. Implementing a custom serializer for a Web service is described in the Oracle Application Server Web Services Developer's Guide.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00207: null soap version not allowed.

Cause: The SOAP message did not contain enough information to determine the version of the SOAP specification used.

Action: Typcially the SOAP version is determined by inspecting the namespace declared on the root element (Envelope) of the SOAP message. This value should be one of http://schemas.xmlsoap.org/soap/envelope/ for SOAP 1.1 or http://www.w3.org/2003/05/soap-envelope for SOAP 1.2.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00208: cannot have enc:id and enc:ref attributes on the same element.

Cause: The SOAP message element contains both an id and a ref attribute. Using both on the same element is illegal.

Action: The Webservice client that created the message must be modified so that invalid SOAP messages are not created.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00209: unexpected element name: expected={0}, actual={1}

Cause: The deserializer encountered an unexpected element name when processing the SOAP message.

Action: The Webservice client that created the message must be modified so that the SOAP messages it creates conform to the messages described in this Webservice's WSDL.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00210: unexpected element type: expected={0}, actual={1}

Cause: The deserializer encountered an unexpected element type when processing the SOAP message.

Action: The Webservice client that created the message must be modified so that the SOAP messages it creates conform to the messages described in this Webservice's WSDL.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00211: unexpected null

Cause: The (de)serializer encountered an unexpected null element/object when processing the SOAP message.

Action: The Webservice client that created the message must be modified so that the SOAP messages it creates conform to the messages described in this Webservice's WSDL.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00212: unknown prefix in QName literal: {0}

Cause: The deserializer cannot figure out the Namespace URI for the given prefix when processing the SOAP message.

Action: The Webservice client that created the message must be modified so that invalid SOAP messages are not created.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00213: invalid XSD date: {0}

Cause: The deserializer encountered an invalid XSD date when processing the SOAP message.

Action: The Webservice client that created the message must be modified so that SOAP messages with invalid XSD dates are not created.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00214: invalid XSD boolean value: {0}

Cause: The deserializer encountered an invalid XSD boolean when processing the SOAP message.

Action: The Webservice client that created the message must be modified so that SOAP messages with invalid XSD boolean are not created.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00215: attachment location not found on element

Cause: The deserializer cannot determine the attachment location on an element with binary type.

Action: The Webservice client that created the message must be modified so that SOAP messages with attachments will correctly reference the attachments.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00216: attachment with id {0} not found in message

Cause: The deserializer cannot find the attachment from the specified location on an element with binary type.

Action: The Webservice client that created the message must be modified so that SOAP messages with attachments will correctly reference the attachments.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00217: invalid XSD positiveInteger value: {0}

Cause: The deserializer encountered an invalid XSD positiveInteger when processing the SOAP message.

Action: The Webservice client that created the message must be modified so that SOAP messages with invalid XSD positiveInteger are not created.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00218: invalid XSD nonNegativeInteger value: {0}

Cause: The deserializer encountered an invalid XSD nonNegativeInteger when processing the SOAP message.

Action: The Webservice client that created the message must be modified so that SOAP messages with invalid XSD nonNegativeInteger are not created.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00219: invalid XSD negativeInteger value: {0}

Cause: The deserializer encountered an invalid XSD negativeInteger when processing the SOAP message.

Action: The Webservice client that created the message must be modified so that SOAP messages with invalid XSD negativeInteger are not created.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00220: invalid XSD nonPositiveInteger value: {0}

Cause: The deserializer encountered an invalid XSD nonPositiveInteger when processing the SOAP message.

Action: The Webservice client that created the message must be modified so that SOAP messages with invalid XSD nonPositiveInteger are not created.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00222: invalid XSD unsignedLong value: {0}

Cause: The deserializer encountered an invalid XSD unsignedLong when processing the SOAP message.

Action: The Webservice client that created the message must be modified so that SOAP messages with invalid XSD unsignedLong are not created.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00223: invalid XSD unsignedInt value: {0}

Cause: The deserializer encountered an invalid XSD unsignedInt when processing the SOAP message.

Action: The Webservice client that created the message must be modified so that SOAP messages with invalid XSD unsignedInt are not created.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00224: invalid XSD unsignedShort value: {0}

Cause: The deserializer encountered an invalid XSD unsignedShort when processing the SOAP message.

Action: The Webservice client that created the message must be modified so that SOAP messages with invalid XSD unsignedShort are not created.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00225: invalid XSD unsignedByte value: {0}

Cause: The deserializer encountered an invalid XSD unsignedByte when processing the SOAP message.

Action: The Webservice client that created the message must be modified so that SOAP messages with invalid XSD unsignedByte are not created.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00227: error in initialization of standard type mapping: {0}

Cause: Internal error initializing the standard type mapping.

Action: System Internal Error - Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00228: {0} : is not a supported (de)serialization mechanism

Cause: The (de)serializer factory does not support the reported XML processing mechanism type.

Action: System Internal Error - Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00229: type mapping registration failed: {0}

Cause: An unexpected error occurred during registration of a Java to XML mapping. Check the nested error for the real cause.

Action: Look at the nested error to determine what action to take.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00230: type mapping retrieval failed: {0}

Cause: An unexpected error occurred during retrieval of a Java to XML mapping. Check the nested error for the real cause.

Action: Look at the nested error to determine what action to take.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00231: type mapping does not support the specified encoding style: {0}

Cause: The system does not support the specified schema type and encoding.

Action: Change the encodingStyle defined in the SOAP binding in the WSDL to a supported value.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00232: there is no type mapping for the specified encoding style: {0}

Cause: The system does not support the specified encoding.

Action: Change the encodingStyle defined in the SOAP binding in the WSDL to a supported value.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00233: no serializer is registered for ({0}, {1})

Cause: The system could not find a serializer that can convert the Java object to XML.

Action: Create a custom type mapping and serializer that can covert the Java object to XML.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00234: no deserializer is registered for (java type: {0}, schema type: {1})

Cause: The system could not find a deserializer that can convert the XML to a Java object.

Action: Create a custom type mapping and serializer that can covert the XML to a Java object.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00235: no deserializer is registered for schema type: {0}

Cause: The system could not find a deserializer that can convert the XML to a Java object.

Action: Create a custom type mapping and serializer that can covert the XML to a Java object.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00236: no deserializer is registered for java type: {0}

Cause: The system could not find a deserializer that can convert the XML to a Java object.

Action: Create a custom type mapping and serializer that can covert the XML to a Java object.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00237: dynamic resolution failed to find a serializer for java type:{0}, xml type {1}

Cause: An entry in a list or collection is a type that is not supported by the system.

Action: Change the instance of the entry to a supported Java type.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00238: dynamic resolution failed to find a serializer for java type: {0}, xmlType: {1}

Cause: An entry in a list or collection is a type that is not supported by the system.

Action: Change the instance of the entry to a supported Java type.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00241: Map entry key cannot be of java type:"{0}", xml type "{1}"

Cause: The key for a map entry has a type mapping for an object that the system does not support.

Action: Change the signature of the Java class to a supported Java type or change the instance of the key to a supported type.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00242: Map entry value cannot be of Java type:"{0}", XML type was "{1}"

Cause: The value for a map entry has a type mapping for an object that the system does not support.

Action: Change the signature of the Java class to a supported Java type or change the instance of the value to a supported type.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00243: Item in array cannot be of java type:"{0}"

Cause: An item in an array is a type that is not supported by the system.

Action: Change the signature of the Java class to a supported Java type or change the instance of the value to a supported type.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00245: unexpected null value for literal data

Cause: The element defined in the schema has a nillable attribute set to false but no value was found in the message.

Action: Change the client to supply a value for the literal type, or change the schema to accept nillable types.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00246: unexpected element name: expected={0}, actual={1}

Cause: A message contains an element that the system does not expect.

Action: Change the client to send messages corresponding to the schema, or change the schema to correspond to the messages.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00247: expected element is missing: {0}

Cause: The message does not contain an element that is defind as required in the schema.

Action: Change the schema to make the element optional, or change the client so that the message will include the required element.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00248: expected simple content, found element name: {0}

Cause: The system was expecting a simple content in the message but found an element instead.

Action: Change the client to send messages corresponding to the schema, or change the schema to correspond to the messages.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00249: object not initialized before use

Cause: A serializer was not initialized before calling a method that requires initialization.

Action: System Internal Error - Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00250: {0} is not an array type

Cause: The system found a Java object that is not an array when an array is expected.

Action: System Internal Error - Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00251: expected {0} parameter(s) but received: {1}. Expected parameters: {3}, received parameters:{4}

Cause: The number of parameters in the request SOAP message is incorrect.

Action: Confirm that the client is based on the correct version of the WSDL definition.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00252: illegal deserialization state: no deserializer is available for the current element

Cause: There is no deserializer registered for the element.

Action: A custom serializer must be used for the indicated type. Implementing a custom serializer for a Web service is described in the Oracle Application Server Web Services Developer's Guide.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00253: Invalid base64 data

Cause: The SOAP request content being processed by the XSDBase64BinaryEncoder is not Base64 encoded.

Action: Confirm that the client is based on the correct, current version of the WSDL document.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00254: generator error: {0}

Cause: An unexpected exception occurred during a generation operation.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00255: can''t write file: {0}

Cause: A generated file could not be written to disk. The most likely causes include insufficient disk space or permissions.

Action: Free some disk space or ensure that the process in which the generator is invoked is run as a user with sufficient permissions.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00256: can''t create directory: {0}

Cause: The directory for writing a generated file could not be created. The most likely causes include insufficient disk space or permissions.

Action: Free some disk space or ensure that the process in which the generator is invoked is run as a user with sufficient permissions.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00257: unsupported type encountered: '{'{1}'}'{0}

Cause: Serialization is not supported for this XML type.

Action: A custom serializer must be used for the indicated type. Implementing a custom serializer for a Web service is described in the Oracle Application Server Web Services Developer's Guide.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00258: no Java type for XML type: {0}

Cause: Unable to determine the corresponding Java type for a structured XML type when generating a serializer.

Action: Ensure that a Java type is associated with the structured XML type and that the custom serializer mapping is correct.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00259: unsupported encoding encountered: {0}

Cause: The encoding URI of custom serializer mapping does not match that of either SOAP 1.1 or SOAP 1.2.

Action: Correct the URI encoding of the custom serializer mapping.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00260: tie class generation error: {0}

Cause: When generating the tie class for a document literal operation, either more than one non-embedded parameter was found, or there were both embedded and non-embedded parameter.

Action: This sanity check should not have failed. Verify that the document literal operation is correct in the WSDL.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00262: There is no management configuration for port {0} in the supplied proprietary deployment descriptor. Ensure that the port name is correct

Cause: There is no management configuration information for the port in the supplied management configuration file.

Action: Verify that the port name is correct and the management configuration file is complete.
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00263: Could not find the Java class {0} for constructor analysis.

Cause: Could not find the Java class for constructor analysis when generating its serializer.

Action: Check the Java class name and the classpath where the Java class is loaded.
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00264: Current SOAP Version is null. Check port to make sure SOAP version is set.

Cause: Could not determine the SOAP version when generating serializer.

Action: Verify that the SOAP version is set in the WSDL.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00266: When using JMS transport, either all operations must be one-way, or the replyToConnectionFactoryLocation and replyToQueueLocation must be specified.

Cause: When using JMS transport for any two-way operation, the replyToConnectionFactoryLocation and replyToQueueLocation parameters must be specified with the jsmAssemble command.

Action: Re-run the jmsAssemble command with replyToConnectionFactoryLocation and replyToQueueLocation parameters.
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00267: cannot dispatch operation with more that one body block: {0}

Cause: Cannot generate tie class for operations with more than one body block.

Action: Verify that the offending operation has no more than one body block.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00268: cannot dispatch operation - either operation names are non-unique, or SOAPAction strings are non-unique: {0}

Cause: Cannot generate tie class for operation with non-unique operation name and non-unique SOAPAction.

Action: Verify that both the operation name and SOAPAction are unique in the WSDL.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00269: no encoder for type "{0}" and Java type "{1}"

Cause: Unable to find an encoder for a type and its corresponding Java type when generating serializer.

Action: Check whether the type is valid and supported.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00270: Invalid type in xsd:list type "{0}" and Java type "{1}"

Cause: Unable to find an encoder for the list item type and its corresponding Java type when generating serializer.

Action: Check whether the list item XML type is valid and supported.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00271: handler error: {0}

Cause: A handler error occurred, check the nested error for the real cause.

Action: Look at the nested error to determine what action to take.
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00272: A HandlerChain can only contain Handler instances: {0}

Cause: A non-handler instance was found in the handler chain.

Action: Remove the offending instance,
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00274: cannot create XSLT transformer for the WSDL

Cause: Failed to create a XSLT Transformer object for presentation of WSDL.

Action: Check whether the web service endpoint is valid and the service is properly deployed.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00275: WSDL transformation failed

Cause: XSLT Transformation failed when presenting WSDL.

Action: Check whether the web service endpoint is valid and the service is properly deployed.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00276: model error: {0}

Cause: A nested model or modeler exception occurred, most likely caused by an invalid WSDL.

Action: Verify that the WSDL is a valid one.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00277: unsupported XML Schema feature ({0})

Cause: An unsupported XML Schema feature was encountered during processing of WSDL schema.

Action: Remove the unsupported XML Schema feature from WSDL schema.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00278: unsupported type ({0}): {2}:{1}

Cause: An unsupported XML Schema type was encountered during processing of a WSDL schema element.

Action: Remove the unsupported type or change it to an equivalent supported type.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00279: unsupported type ({0}): {1}, caused by: {3}

Cause: An unsupported XML Schema type was encountered during processing of a WSDL schema element. Error details are provided.

Action: Look at the error details for possible action to handle the unsupported type.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00280: unsupported anonymous type ({0}), caused by: {1}

Cause: An unsupported XML Schema type was encountered during processing of an anonymous WSDL schema element. Error details are provided.

Action: Look at the error details for possible action to handle the unsupported type.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00281: invalid literal "{0}" in enumeration "{1}" (namespace: {2})

Cause: An invalid literal value of an enumeration was encountered when processing a WSDL schema.

Action: Correct the offending literal value in the enumeration.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00282: uniqueness constraint violation: {0} "{1}" already exists.

Cause: A component with the specified name occurs multiple times

Action: Check the validity of the WSDL or Java code for duplicate elements
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00283: The value type {0} can not be generated because two members result in the same name of {1}. A jaxrpc mapping file must be specified to resolve this naming conflict.

Cause: There is a naming conflict - two members have the same name

Action: Use a JAX-RPC mapping file.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00285: parent of type "{0}" already set to "{1}", new value = "{2}"

Cause: The specified type is duplicated within more than one parent type.

Action: Rewrite the type hierarchy, so that this type only occurs on one parent.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00286: parent of fault "{0}" already set to "{1}", new value = "{2}"

Cause: The specified fault is duplicated as a sub-type of more than one parent.

Action: Ensure that the fault only occurs within a single parent.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00287: LiteralArrayWrapper element member already set.

Cause: This element cannot be modeled as a LiteralArrayWrapper because it has more than one member

Action: None
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00288: LiteralArrayWrapper cannot have a parent type

Cause: This element cannot be modeled as a LiteralArrayWrapper because it has a parent type

Action: None
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00289: LiteralArrayWrapper cannot have subtypes

Cause: This element cannot be modeled as a LiteralArrayWrapper because it has a subtype

Action: None
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00290: LiteralArrayWrapper cannot have a content member

Cause: This element cannot be modeled as a LiteralArrayWrapper because it has a content member

Action: None
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00293: class {0} not found.

Cause: The specified Java class could not be loaded.

Action: The class must exist in the classpath when strictJAXRPCValidation is turned on.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00295: unexpected type: {0}

Cause: An unexpected type was found during the processing of your action. In the case of top-down design the WSDL contains an unsupported or invalid type. In the case of bottom-up design, the particular class file is currently not supported.

Action: Top-down design pattern: Correct any problems within the WSDL file. If the WSDL is valid, then it contains types that are currently not supported. Bottom-up design pattern: Correct any type issues within the Java class. Otherwise, the class contains types that are currently not supported. You may want to consider using a different type.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00296: The following type is invalid because it implements java.rmi.Remote: {0}

Cause: The serializable implementation class inappropriately implements java.rmi.Remote. This is not supported.

Action: Change the implementation class to not implement java.rmi.Remote.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00297: class {0} does not have a public accessible empty constructor

Cause: The serializable implementation class does not provide a public accessible no-arg constructor.

Action: Provide a public no-arg constructor or provide a custom seriallizer.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00299: class "{0}" cannot have a JavaBean property "{1}" and a public member of the same name.

Cause: The implementation class cannot contain public members with the same name as JavaBean properties.

Action: Consider making the public member private or protected or renaming the property or JavaBean property.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00300: nested inner classes are not supported: {0}

Cause: The implementation class contains a nested inner class, which is not supported.

Action: Consider refactoring the implementation class to remove the nested inner class. See the Oracle Application Server Web Services Developer's Guide.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00301: Duplicate type name "{0}" for Java type "{1}" found. To remove this error do not specify a single typeNamespace for all value types or specify a mapping file. This error could also be caused when a type name has been used more than once.

Cause: The same type name has been used for multiple Java types. Probably related to inner classes. A possible explanation is the erroneous use of a given type name multiple times.

Action: Use separate namespaces for the value types or use a mapping file. See the Oracle Application Server Web Services Developer's Guide.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00302: Type "{0}" is used as a "{1}" and a "{2}"

Cause: The same RMI Modeler type instance is used for two different XML types.

Action: Correct the XML type or the XML type hierarchy such that there is one Modeler per XML type, or have one type subclass the other type.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00303: Type "{0}" implements more than one interface: "{1}", "{2}" ...

Cause: The implementation class may implement only a single interface (SEI).

Action: Consider refactoring the implementation class to implement a single interface.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00304: Type {0} references an invalid type {1}, which is invalid for the following reason: {2}

Cause: The indicated type has a reference to an invalid type.

Action: Consider modifying the implementation class to not reference the inappropriate type.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00305: Ignoring target namespace for schema: "{0}", WSDL target namespace is used for the value types in the same package as Service Endpoint: "{1}"

Cause: The schema namespace is ignored and the WSDL target namespace will be used instead. This is because the namespace of the schema is different from the target namespace of the WSDL and the value types are in the same package as the Service Endpoint Interface (SEI).

Action: See error message.
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00306: The constructor for {0} has {1} arguments of type {2}; This ambiguity may result in unexpected behavior. Use a mapping file to guarantee correctness.

Cause: Multiple arguments of the same type introduce ambiguity that is difficult to resolve. This may cause unexpected results.

Action: Consider using a JAX-RPC mapping file to eliminate the ambiguity.
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00307: Service-specific exception {0} is not allowed to extend {1}.

Cause: Runtime exceptions other than SOAPFaultException are not allowed.

Action: Consider changing the exception to not be a runtime exception or make it a SOAPFaultException.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00308: Service-specific exception {0} is not allowed to implement {1}.

Cause: Service exceptions must not implement the java.rmi.Remote interface.

Action: Consider changing the exception to not implement Remote.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00309: Found a suitable parameterized constructor for {0}.

Cause: A constructor has been found that satisfies all of the member values and will be used in the creation of the fault.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

OWS-00310: Did not find a suitable parameterized constructor for {0}.

Cause: A suitable constructor that satisfes all of the getter methods could not be found.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

OWS-00311: Found a default constructor and a setter for every member of {0}.

Cause: The default constructor will be used in conjunction with the setter methods to satisfy all of the member variables.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

OWS-00312: Using the single java.lang.String parameter constructor for {0}.

Cause: Assuming the message member is the single string argument constructor.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

OWS-00313: Since no members could be found for {0}, the default constructor will be used for deserialization.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

OWS-00314: invalid operation: {0}

Cause: Invalid WSDL operation due to incorrect parameter order.

Action: Correct the parameter order of the specified operation.
Level: 1

Type: ERROR

Impact: Data

OWS-00315: invalid state while modeling operation: {0}

Cause: System Internal Error

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00316: result is "inout" parameter in operation: {0}

Cause: In/out parameters are not allowed.

Action: Consider changing the implementation to return a value.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00317: "{0}" specified in the parameterOrder attribute of message "{1}" is not a valid part of the message.

Cause: The specified parameter(s) in parameterOrder of portType operation is not a valid part of the message.

Action: Verify and correct the part name parameter specified in the WSDL portType: ensure that the operation parameterOrder is properly associated and used in the input and output message.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00318: one or more part names were omitted in the parameterOrder attribute of operation "{0}"

Cause: A message part name was not specified in the WSDL portType operation parameterOrder.

Action: Verify that input and output message part name are properly specified in the WSDL portType operation parameterOrder.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00319: parameter "{0}" of operation "{1}" appears with different types in the input and output messages

Cause: The parameter used in an operation appears with different types in the input and output message.

Action: Verify the type of the input and output message specified in the WSDL portType operation.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00320: missing header message definition for "{1}", referenced by the binding operation "{0}"

Cause: The soap header message defined in the binding operation is not specified in the WSDL message definition.

Action: Verify the soap header message defined in the binding operation. Ensure that it is properly specified in the WSDL message definition.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00321: missing operation "{0}" in port type, referenced by binding "{1}"

Cause: The operation specified in binding does not appear in the corresponding port type.

Action: Verify the binding operation. Ensure that it is specified in the corresponding port type in the WSDL.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00322: input message of binding operation "{0}" does not have a SOAP body extension

Cause: The input message of the binding operation does not have a SOAP body extension.

Action: Verify that the SOAP body extension 'soap:body' is properly specified in the input message of the binding operation in the WSDL.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00323: output message of binding operation "{0}" does not have a SOAP body extension

Cause: The output message of a binding operation does not have a SOAP body extension.

Action: Verify that the SOAP body extension 'soap:body' is properly specified in the output message of the binding operation in the WSDL.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00324: input message of binding operation "{0}" must specify a value for the "namespace" attribute

Cause: The soap request body of the input message of a binding operation must specify a value for the namespace attribute.

Action: Verify that the namespace attribute is properly specified in the soap request body of the input message of this binding operation in the WSDL.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00325: output message of binding operation "{0}" must specify a value for the "namespace" attribute

Cause: The soap request body of the output message of a binding operation must specify a value for the namespace attribute.

Action: Verify that the namespace attribute is properly specified in the soap request body of the output message of this binding operation in the WSDL.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00326: fault "{0}" in operation "{1}" matches more than one fault in the corresponding port type operation

Cause: The fault in a binding operation matches more than one fault in the corresponding port type operation.

Action: Verify the exact correspondence between the fault name in the binding operation and in the port type operation of the WSDL.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00327: fault "{0}" in operation "{1}" does not match any fault in the corresponding port type operation

Cause: The fault in a binding operation does not match any fault in the corresponding port type operation.

Action: Verify the the correspondence between the fault name in the binding operation and in the port type operation of the WSDL.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00328: fault "{0}" in operation "{1}" does not have a SOAP fault extension

Cause: The fault in a binding operation does not have a SOAP fault extension.

Action: Verify that the SOAP fault extension 'soap:fault' is properly specified in this fault of the binding operation.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00329: fault "{0}" refers to message "{1}", but the message has no parts

Cause: The fault refers to a message in definitions, but the message has no parts.

Action: Verify and ensure the fault message with properly specified part name in the WSDL.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00330: fault "{0}" refers to message "{1}", but the message has more than one parts

Cause: The fault refers to a message in definitions, but the message has more than one parts.

Action: Verify and correct the fault message with properly and exactly specified part name in the WSDL.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00331: in message "{0}", part "{1}" must specify a "type" attribute

Cause: In this WSDL, there is part must specify a type attribute in message.

Action: Verify the message in WSDL to ensure some part which also need a type definitions.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00332: in message "{0}", part "{1}" must specify an "element" attribute

Cause: In this WSDL, there is part in message must specify an element attribute.

Action: Verify the message in WSDL to ensure some part which also need an element definitions.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00334: the following naming conflicts occurred: {0}

Cause: There are naming conflicts occurred in WSDL.

Action: Verify the naming in WSDL is properly and correctly without conflict.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00335: Unsupported DIME layout: {0}

Cause: The DIME message layout specified in the operation is not supported.

Action: Verify and check the DIME layout specified. The supported layout are: closed-layout and open-layout.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00336: binding "{0}" uses both streaming attachments and mime-multipart

Cause: There is binding which uses both streaming attachments and mime-multipart in WSDL.

Action: Verify and correct the WSDL binding to ensure not both streaming attachments and mime-multipart is used.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00337: binding "{0}" uses both streaming attachments and DIME

Cause: There is binding which uses both streaming attachments and DIME message in WSDL.

Action: Verify and correct the WSDL binding to enusre not both streaming attachments and DIME is used.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00338: <portType> definition is not found in the WSDL

Cause: There is no service and portType definition found in the WSDL.

Action: Verify and check the WSDL. Either service or portType has to be defined and specified.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00339: IO error in processing schemas: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00340: The value of service-interface {0} MUST be package qualified. It is changed to {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00341: unrecognized type encountered: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00342: exception occurred while processing type {0}, {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00343: Service "{0}" does not contain any usable ports

Cause: There is no port in the current WSDL that is suitable for JAXRPC based proxy generation.

Action: Correct the WSDL, based on the other error or warning provided, so that there is one port in the current WSDL suitable for JAXRPC based proxy generation.
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00344: Port "{0}" does not contain any usable operations

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00345: ignoring port "{0}": because it references "{1}" that does not contain a SOAP Binding. Only soap:binding is supported.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Data

OWS-00346: ignoring port "{0}": no SOAP address specified

Cause: The "service/port" element is missing a required child element for SOAP binding: "soap:address".

Action: Add the missing element in the original WSDL or using a local copy if you do not own the service endpoint.
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00347: ignoring operation "{0}": not request-response or one-way

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00348: ignoring RPC-style operation "{0}": parameters are not encoded

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00349: ignoring operation "{0}": message part does not refer to a schema element declaration or refers to a schema type declaration without specifiying the name attribute.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00350: ignoring header "{0}" of binding operation "{1}". This header must be mapped to a parameter using a jaxrpc mapping file or the information in the header will be ignored at runtime.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00351: ignoring header "{0}" of binding operation "{1}": not literal

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00352: ignoring header "{0}" of binding operation "{1}": not SOAP-encoded

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00353: ignoring header "{0}" of operation "{1}": its type is not constant across all operations in this port

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00354: ignoring MIME part "{0}" of operation "{1}": either the part was not found in the specified message or the "mimePartToParameter" flag was set to false.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00355: value type package prefix is ignored for the types defined in the schema that has same target namespace as the target namespace of WSDL: "{0}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00356: binding "{0}" is ignored because it has an invalid attribute: transport="{1}"

Cause: The value of the transport attribute on the soap:binding element is not recognized. The SOAP1.1 value is "http://schemas.xmlsoap.org/soap/http".

Action: Correct the value of the transport attribute in the original WSDL or use a local copy if you do not own the service endpoint.
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00357: ignoring document-style operation "{0}": parameters are not literal

Cause: The value for the "use" attribute on document-style binding is invalid. the only value supported is "literal".

Action: Correct the original WSDL or use a local copy if you do not own the service endpoint.
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00358: ignoring operation "{0}": input message with multiparts is not WS-I compliant and is not currently supported

Cause: The wsdl:message referenced by the portType/operation/input element contains more than one part and doesnt comply with WS-I BP 1.1.

Action: If you have control over the WSDL, changes the message style for bare to wrapped, so that the WSDL comply with WS-I profile. Otherwise, use the SAAJ APIs to invoke the service without to use JAXRPC generated proxy.
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00359: ignoring operation "{0}": output message with multiparts is not WS-I compliant and is not currently supported

Cause: The wsdl:message referenced by the portType/operation/output element contains more than one part and doesnt comply with WS-I BP 1.1.

Action: If you have control over the WSDL, changes the message style for bare to wrapped, so that the WSDL comply with WS-I profile. Otherwise, use the SAAJ APIs to invoke the service without to use JAXRPC generated proxy.
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00360: The WSDL used has operations with literal and encoded use. -f:searchschema is not supported for this scenario.

Cause: The WSDL has soapbinding subelements with use="literal" as well as use="encoded". Searching of Schema is not supported for this scenario.

Action: Modify the WSDL to have only use="literal" or use="encoded"
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00361: ignoring fault "{0}" of operation "{1}", part name "{2}" is not unique

Cause: The WSDL uses the fault partname more than once.

Action: Update WSDL to specify unique fault part name.
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00362: Notification operation "{0}" in binding "{1}" is not supported.

Cause: Notification operations are not supported.

Action: Use a WSDL with no notification operations.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00363: Non conforming WSI WSDL used for wsdl:import

Cause: WSDL import element doesnt comply with WS-I

Action: Update the WSDL so that the imports precede all other top level elements in the WSDL.
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00364: Non conforming WSI WSDL used for wsdl:types

Cause: WSDL types element doesnt comply with WS-I

Action: Update the WSDL so that the wsdl:types elements appear immediately after the wsdl:imports or if no imports are present wsdl:types should be the first top level element.
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00365: parts "{0}" not found in the message "{1}", wrong WSDL

Cause: The part defined in the input soap body of the binding is not specified in the input message of the operation in the port type. The part defined in the output soap body of the binding is not specified in the output message of the operation in the port type.

Action: Make sure all the parts that are defined in the input soap body of the binding are defined in the input message of the corresponding operation of the port type. make sure all the parts that are defined in the output soap body of the binding are defined in the output message of the corresponding operation of the port type.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00366: Custom mappings for rpc-encoded web service is not supported (operation = "{0}").

Cause: the WSDL uses custom mappings and rpc encoded webservices.

Action: If WSDL has rpc encoded bindings do not specify custom serializers. "schema" argument to Web Services Assembler along with a message format of rpc encoded is not allowed. <type-mapping> in the oracle-webservices.xml is also not allowed with rpc encoded webservices.
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00367: a class by name : "{0}" is already available in the classpath

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00368: failed to make an unique serializer class : "{0}" , the error :"{1}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00369: failed to find accessor method "{0}" in Java type "{1}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00370: model is missing

Cause: The system is missing a model.

Action: System Internal Error - Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00371: Ignoring Unique Schema Constraint

Cause: The schema used by the WSDL has a unique constraint.

Action: Remove unique constraint
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00372: The key element has not been implemented

Cause: The WSDL uses the unsupported "key" schema element.

Action: Modify the schema to remove the key element
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00373: Model group definition has not been implemented

Cause: The WSDL uses a schema with a model group definition

Action: Modify the schema to remove the model group definition
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00374: Substitution Group Attribute has not been implemented

Cause: The WSDL references a schema that uses the substitutionGroup facility.

Action: Modify the schema to remove the substitutionGroup element
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00375: Block attribute has not been implemented

Cause: The WSDL refers to a schema that uses an unsupported block attribute.

Action: Update your schema to set "" or #all as values for the block attribute. All other values are unsupported.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00377: Base attribute must be specified in restriction tag.

Cause: The base attribute is not specified in the restriction tag.

Action: Specify a base type from which the complex type is to be derived by restriction.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00378: Enumeration {0} is not supported

Cause: The enumeration is not supported.

Action: Modify the schema to remove this enumeraton.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00379: Attribute restriction is not supported

Cause: The base type has an attribute element with the use="prohibited".

Action: Remove the use="prohibited" attribute on the base type.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00380: Group Schema Element has not been implemented

Cause: The "group" schema element is not supported

Action: Modify the schema to remove the group element
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00381: Unsupported Schema Element

Cause: Facets are not supported in the extension and restriction elements.

Action: Remove facets (elements like xsd:pattern, xsd:minInclusive etc which restrict values of an element) from your schema.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00382: Invalid value ({0}) for "minOccurs" attribute of element - {1}. Setting value to 0.

Cause: Invalid "minOccurs" attribute value. Setting value to 0.

Action: Set minOccurs to 0 if the assoicating element is optional. Otherwise, set the value to 1 or more.
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00383: The "maxOccurs" attribute of the {0} element has an unsupported value of {1}. Currently only boundless arrays are supported. maxOccurs must be 0,1 or unbounded. Setting to default value of "unbounded".

Cause: Invalid or unsupported "maxOccurs" attribute value. Setting value to 0.

Action: Set this value to a positive integer or unbounded to indicate there is no maximum number of occurrences.
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00384: Value ({0}) for "final" attribute of element -{1} is currently not supported. This attribute is ignored.

Cause: Unsupported final attribute value. Ignore the attribute.

Action: Set this value to "#all" or ""
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00385: Processing {0} QNAME HINT: {1} Name: {2}

Cause: Processing schema type.

Action: N/A
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

OWS-00386: sender error: {0}

Cause: Invalid configuration in oracle-webservices.xml or wsmgmt.xml.

Action: Verify the configuration setting in oracle-webservices.xml and/or wsmgmt.xml.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00387: missing body information

Cause: SOAP Body is missing in the request. The SOAP message was not sent.

Action: Verify request.getBody() returns a SOAP body instance.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00388: illegal value of "mustUnderstand" attribute: "{0}"

Cause: Response contains illegal value of "mustUnderstand" attribute.

Action: Verify the response SOAP message. Attribute "mustunderstand" must have a value of "0", "1", "true", or "false".
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00389: unrecognized operation (code: {0})

Cause: The SOAP message is invalid. It cannot be resolved to an operation's request or response.

Action: Regenerate the stub using either Jdeveloper or the Web Service Assembler tool.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00390: unrecognized fault block

Cause: The response fault is invalid.

Action: Verify the content of the fault response.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00391: received empty response

Cause: No SOAP Message is returned from the server.

Action: Verify the corresponding WSDL operation is not oneWay.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00392: stub was not initialized

Cause: The initialize() method of the stub was not invoked.

Action: Regenerate the stub using either JDeveloper or the Web Service Assembler tool. If problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00395: XML reader internal error: illegal state ({0})

Cause: XMLReader encounters an XML element that cannot be deserialized.

Action: Validate the XML document.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00396: XML reader error: unexpected character content: "{0}"

Cause: XMLReader encounters an element with an unexcpected character content.

Action: Validate the XML document.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00397: XML reader error: {0}

Cause: XMLReader cannot close the reading stream.

Action: Check network connection and file system connection.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00398: XML parsing error: {0}

Cause: XMLReader cannot read the next element.

Action: Validate the XML document.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00400: XML writer error: no prefix for URI: "{0}"

Cause: No prefix is specified for the URI.

Action: System Internal Error - Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00401: XML writer error: {0}

Cause: XML Writer encounters an IOException.

Action: Check network connection and file system connection.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00403: unexpected XML reader state. expected: {0} but found: {1}

Cause: The XML document does not have the expected start or end of an element.

Action: Check if any required element is missing or there are more elements where an end tag was expected.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00405: unrecognized operation: {0}

Cause: The soap operation is not valid.

Action: Check the operation name in the message and correct it.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00406: cannot dispatch ambiguous operation: {0}

Cause: The specified operation is overloaded.

Action: Remove the overloading by renaming one of the conflicting operations.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00407: unexpected header block: "{0}"

Cause: The QName of the header block is not correct.

Action: Correct the header block by verifying its namespace.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00408: invalid SOAP envelope: body is empty

Cause: The body of the soap message is empty.

Action: Provide the write content in the body element of the soap message.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00409: invalid SOAP envelope: body is missing

Cause: The body element is either missing or its namespace is wrong.

Action: Add the body if missing or correct the namespace of the body element.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00410: env:Body must be present in a SOAP 1.2 envelope

Cause: The body element is missing from the message. SOAP 1.2 requires that the env:Body element must be present.

Action: Add the soap body in the message.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00411: invalid SOAP envelope content

Cause: The content of the soap envelope is invalid.

Action: Correct the content of the soap envelope.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00412: invalid SOAP envelope

Cause: The root element of the message is not a soap envelope.

Action: Make the root element a valid soap envelope.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00413: SOAP envelope version mismatch

Cause: The namespace or the version of the envelope is not correct.

Action: Correct the namespace of the soap envelope.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00414: Caught exception while handling request: {0}

Cause: Refer to the details of the message for further information on possible causes.

Action: Refer to the details of the message for further information on possible actions.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00415: Caught exception while preparing response: {0}

Cause: Refer to the details of the message for further information on possible causes.

Action: Refer to the details of the message for further information on possible actions.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00416: Caught exception while invoking the post handling hook: {0}

Cause: Refer to the details of the message for further information on possible causes.

Action: Refer to the details of the message for further information on possible actions.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00417: Internal Server Error ({0})

Cause: Refer to the details of the message for further information on possible causes.

Action: Refer to the details of the message for further information on possible actions.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00418: Could not find the field in the Holder that contains the Holder value: {0}

Cause: Refer to the details of the message for further information on possible causes.

Action: Refer to the details of the message for further information on possible actions.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00420: No jar file (or directory) found at specified path: {0}

Cause: The specified jar file does not exist.

Action: Check if the jar file name is correct and it is in the right directory.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00422: Exception occured while verifiying EJB: Class: {0} Details: {1}

Cause: Error while parsing ejb-jar.xml. Refer to the details of the message for further information on possible causes.

Action: Refer to the details of the message for further information on possible actions.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00423: The EJB {0} was not found in the specified ejb location

Cause: The ejb-jar.xml does not contain the specified EJB.

Action: Check if the name of the EJB is correct and it is present in the ejb-jar.xml.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00425: Unable to locate ejb-jar.xml in {0}

Cause: The application does not contain an ejb-jar.xml deployment descriptor file. The deployment descriptor file is inspected to locate the endpoint service interface

Action: Add ejb-jar.xml and reassemble the application.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00426: Error parsing ejb-jar.xml. No session beans found.

Cause: The application does not contain any session bean definition. The business functions to be exposed as webservices should be defined in a session bean.

Action: Write an Enterprise Java Session Bean that contains the business functions that you want to expose.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00427: Error parsing ejb-jar.xml. Stateful session beans are not supported.

Cause: Creating webservices from a stateful session bean is not supported. The business functions to be exposed as webservices should be defined in a stateless session bean.

Action: Remove the stateful session bean, write a stateless session bean that contains the business functions that you want to expose.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00428: Method

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-00429: Return type

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-00430: Exception

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-00431: {0} ({1}, build {2})

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-00432: ERROR: {0}

Cause: Server or client artifacts generation has failed.

Action: This is a generic error indicating an error condition. You should also see a message describing the details.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00433: WARNING: {0}

Cause: Server or client artifacts generation has encountered a possible error.

Action: This is a generic warning. You should also see a message describing the details.
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00434: INFO: {0}

Cause: Oracle webservice compile tool generates this diagnostic information.

Action: This is used to indicate that the message follows is for informational purpose.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

OWS-00436: -import requires a WSDL-based configuration file

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00437: -define requires a service-based configuration file

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00439: You have specified : -gen:both or -gen:client with SEI. The use of these modes are recommended with WSDL only.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00440: all sources succesfully generated

Cause: Oracle webservice compile tool has successfully generated all code artifacts.

Action: See error message.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

OWS-00442: Problem validating implementation class. {0}

Cause: Supplied Service implementation class is not valid. It could be that the implementation class does not implement the interface correctly or it does not conform to JAXRPC requirements or the class is not found.

Action: Make sure the implementation class is JAXRPC compliant if it is a JAXRPC webservice; make sure the classpath containing the implementation class is correctly specified
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00450: parsing failed: {0}

Cause: SAXException is thrown from the parser while parsing the WSDL.

Action: Fix the WSDL according to the error reported by the parser.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00451: parsing failed: {0}

Cause: ParserConfigurationException is thrown from the parser while parsing the WSDL.

Action: Unexpected internal error.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00460: Element type "{1}" is missing required attribute "{0}"

Cause: The WSDL or Schema entity is missing the required attribute.

Action: Add the required attribte with a valid value to the WSDL or Schema entity.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00461: Element named "{0}" of type "{2}" is missing required attribute "{1}"

Cause: The WSDL or Schema entity is missing the required attribute.

Action: Add the required attribte with a valid value to the WSDL or Schema entity.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00463: missing required sub-entity "{0}" of element "{1}"

Cause: A sub-element required by the schema or WSDL specification is missing.

Action: Modify the schema or WSDL to add the required sub-element.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00464: Could not find Attribute : "{0}"

Cause: An attribute reference is not defined in the schema.

Action: Modify the schema to define the missing attribute reference.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00465: Unsupported schema feature : "{0}"

Cause: An element defined in the schema is not supported by the system.

Action: Modify the schema.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00466: The element is not supported in this context : "{0}"

Cause: A sub-element of the complex type extension/restriction definition in the schema is not supported by the system.

Action: Modify the complex type extension/restriction definition in the schema.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00467: Unsupported simple type definition : "{0}" inside "{1}" element

Cause: A simple type defined in the schema is not supported by the system.

Action: Modify the simple type to a simple type supported by the system.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00468: invalid sub-element "{0}" of element "{1}"

Cause: The WSDL contains an element with a sub-element that is not supported by the system. Check WSDL 1.1 specification.

Action: Modify the invalid sub-element based on the WSDL 1.1 specification.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00469: invalid attribute "{0}" of element "{1}"

Cause: The WSDL or schema contains an element with an attribute that is either formatted incorrectly or does not comply with the specifications support by the system. The specifications to check include SOAP, WSDL 1.1 and jaxrpc.

Action: See error message.
Level: 1

Type: WARNING

Impact: Data

OWS-00470: invalid value "{1}" for attribute "{0}"

Cause: A attribute on a WSDL or schema element has a value that is not expected by the system.

Action: or WSDL to comply with the value for the schema type of the attribute or change the type of the attribute to a simple type like string or int.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00471: invalid range found (min: {0}, max: {1})

Cause: A complex type in a schema defines min and max occurance on a type that the system does not support.

Action: Change the max occurances attribute to 1 so the system will except the schema.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00472: exclusive attributes: "{0}", "{1}"

Cause: A complex type in a schema defines two attributes that are not supposed to be defined at the same time.

Action: Remove one of the specified attriubutes from the schema.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00474: not a simple type: "{0}"

Cause: A schema type other than a simple type was found in a schema when a simple type is expected.

Action: Change the type specified in the error message to a simple schema type or change the reference to this type to a simple schema type.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00475: port type "{0}" in binding "{0}" not found.

Cause: The specified WSDL is invalid or complete. A binding in a WSDL document has a reference to a portType that is not defined in the WSDL.

Action: Change the value of the type attribute in the binding to the name of a portType that is defined in the WSDL.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00476: message "{0}" not found.

Cause: The specified WSDL is invalid or complete. An input, output or fault element has a value for the message attribute that is not defined in the WSDL.

Action: Change the value of the message attribute to a message that is defined in the WSDL.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00477: type "{0}" defined for the message part "{1}" could not found.

Cause: The type definition is not found in the schema.

Action: Add the type definition to the schema, or change the value of the type attribute to the name of an existing schema type.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00478: element "{0}" defined for the message part "{1}" could not found.

Cause: A schema contains a reference to an element name that does not exist in the specified set of schemas. The set of schemas can be inside of a WSDL document, imported from a WSDL document or imported from other schema documents.

Action: Change the reference to an element name that is found in the specified set of schemas, or define the type in the schema.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00480: Binding "{1}" used in port "{0}" not found.

Cause: The specified WSDL is invalid or complete. A port in the WSDL document has a reference to a binding that is not defined in the WSDL.

Action: Change the value of the binding attribute in the port to the name of a binding that is defined in the WSDL, or define the binding.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00481: The name "{0}" is not a valid XML NCName. (see http://www.w3.org/TR/1999/REC-xml-names-19990114/#NT-NCName)

Cause: The name is not a valid XML NCName.

Action: Correct the value of NCName. See http://www.w3.org/TR/1999/REC-xml-names-19990114/#NT-NCName for the format.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00482: The extensibility element "{0}" is unknown and has a wsdl:required attribute set to "true"

Cause: During WSDL validation, found unrecognized extensibility element with wsdl:required attribute set.

Action: Ensure required extension registry is set with WSDLReader when reading WSDL document into WSDL definition or remove wsdl:required attribute
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00483: The WSDL contains a mixture of styles - "document" and "rpc". Only "rpc" OR "document" is supported in a WSDL, not both.

Cause: WSDL contains a mixture of styles i.e both "Document" and "Rpc" style operation

Action: Multiple styles WSDL is not supported by JAXRPC/JAXWS. Make sure WSDL does not contain muplitple styles i.e both document and rpc style bidning operation.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00484: The WSDL contains a mixture of uses - "literal" and "encoded". Only "literal" OR "encoded" is supported in a WSDL, not both.

Cause: WSDL contains both "literal" and "encoded" use

Action: Make sure WSDL does not contain mixture of uses - "literal" and "encoded". Only "literal" or "encoded" is supported in a WSDL, not both
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00485: Operation "{0}" and "{1}" have conflicting SOAPAction values. Do not overload any operation or give unique SOAPAction value to each operation binding.

Cause: Two or more operations specified in WSDL have conflicting SOAPAction values.

Action: Do not overload any operation or give unique SOAPAction value to each operation binding.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00486: Operation "{0}" does not have a SOAPAction value. Give it a unique value.

Cause: In WSDL, overloaded operation does not contain SOAPAction value.

Action: Specify unique SOAPAction value for the overloaded operation.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00487: Element does not have name

Cause: Element declared in schema does not have a "name" attibute set.

Action: Specify a name to an Element defined in a schema.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00488: Attribute group does not have name

Cause: Attribute group does not contain any name.

Action: Specify a name to an attribute group.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00490: AttributeGroup "{0}" child missing ref attribute.

Cause: Child element of Attirbute group is missing "ref" attribute.

Action: Specify a name to a child element of Attibute group.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00491: Attribute declaration missing name.

Cause: In schema, attirbute declaration is missing name.

Action: Provide valide "name" to the attribute declaration.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00492: AttributeGroup missing ref attribute

Cause: During schema validation, found AttributeGroup element is missing "ref" attribute.

Action: Make sure AttributeGroup has "ref" attribute declared.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00493: Warning: {0} is already defined. Ignoring.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00494: The portType {0} is used by two bindings with different headers mapped to parameters. This usecase is not supported at this time. Map the same headers to parameters for all bindings using this port type.

Cause: The portType defined in WSDL is used by two bindings with different headers mapped to parameters.

Action: Map the same headers to parameters for all bindings using this port type.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00495: The specified service name "{0}" was not found.

Cause: In WSDL, service element does not have "name" attirbute defined.

Action: Make sure WSDL has valid service name.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00496: Error while loading the schemas defined in WSDL "{0}": "{1}"

Cause: Failed to load the schema specified in the WSDL.

Action: Ensure the schema location specified in the WSDL is correct.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00499: LiteralArrayWrapper may only have one element member.

Cause: LiteralArrayWrapper has more than one element member.

Action: Make sure LiteralArayWrapper contains one element member.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00500: The annotation type or property "{0}" has been deprecated in this version of Oracle WebServices.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Data

OWS-00501: No @WebService annotation found on the impl class {0}. This ejb bean is not a candidate for webservice processing.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Programmatic

OWS-00502: The annotations on the impl bean {0} or a referenced SEI are not consistent with the portType(s), binding(s) and service(s) in the WSDL specified by the wsdlLocation: {1}. Please refer to section 4.1.1 of the JSR-181 specification for details on the usage of wsdlLocation. The {2} was not found in the WSDL.

Cause: The WSDL specified by a wsdlLocation attribute is inconsistent with the portType and bindings declared in the same WSDL.

Action: Ensure that the annotations are consistent with the WSDL. See section 4.1.1 of the JSR-181 spec.
Level: 1

Type: WARNING

Impact: Configuration

OWS-00505: Not a java bean

Cause: The specified value type is not a valid Java Bean.

Action: Ensure that the all declared value types are valid Java Bean.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00506: Not a java bean. Class is not public.

Cause: The specified class is not a valid Java Bean.

Action: Ensure the specified class has "public" modifier.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00526: Not in class path

Cause: The specified class could not found in classpath.

Action: Ensure that all required classes or jar files containing classes are declared in classpath.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00527: Element "{0}" can not have both a type attribute and a nested type declaration.

Cause: The WSDL or schema contains an element with a type attribute and a nested type defined.

Action: None
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00528: Type "{0}" is not a valid JAXRPC value type or it is not serializable.

Cause: SEI contains method with unserializable return type or parameter type

Action: Ensure that all parameter types and return type are valid value types as per JAXRPC specification.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00529: Filenames "{0}" and "{1}" conflict in generated sdo type classses. Some files may be overwritten. This could happen if schemas use case-sensive type declaration, but some file systems are case-insensitive.

Cause: File names conflict.

Action: See error message.
Level: 1

Type: WARNING

Impact: Data

OWS-00530: WSDL is not WS-I BP compliant. Literal style WSDL at location "{0}" can not have soap encoded type.

Cause: Invalid WSDL. Provided WSDL has both literal and soap encoding style.

Action: Make sure WSDL has either "literal" or "encoding" style, NOT both
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00531: Could not find schema from URL source, file source, classpath or application context at this lcoation: "{0}"

Cause: Could not locate the schema document from file, url, classpath or application context.

Action: Verify that the specified location of schema is correct.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00532: Failed to retrieve policy

Cause: Could not retrieve the policy from the Policy Accessor.

Action: System Internal Error - Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00533: Value {0} is not valid for {1}

Cause: Invalid value encountered while deserializing a Java value from XML.

Action: Verify that XML datatype contains valid value as per the schema.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00534: The entity identified by systemid={2} and publicid={1} was resolved by {0}.

Cause: An entity was resolved using a resolver, usually an XML catalog.

Action: See error message.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

OWS-00535: The entity identified by systemid={1} and publicid={0} could not be resolved.

Cause: An entity could not be resolved. Usucally occurs during an XML catalog lookup failure.

Action: See error message.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

OWS-00536: The output of a binding operation "{0}" is missing

Cause: The output of a binding operation is missing.

Action: Verify that the output element is properly specified in the binding operation in the WSDL.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00537: The input element, under namespace of "http://schemas.xmlsoap.org/wsdl/", of the binding operation "{0}" is missing

Cause: The input element, under namespace of "http://schemas.xmlsoap.org/wsdl/", of a binding operation is missing.

Action: Verify that the input element is properly specified in the binding operation in the WSDL.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00538: The value of the BindingType annotation "{0}" does not match the SOAP version "{1}" on the WSDL.

Cause: The value of the BindingType annotation does not match the SOAP version on the WSDL.

Action: Verify the value of the BindingType annotation.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00539: The WebParam or WebResult annotation on method "{0}" does not match the WSDL or Schema; The "{1}" "{2}" element is missing.

Cause: The WebParam or WebResult annotation does not exist, or does not match the WSDL/Schema.

Action: Verify the value of the WebParam or WebResult annotation.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00540: Attempting read of url "{0}" with parent URL "{1}"

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

OWS-00541: Successful read of url "{0}" with parent URL "{1}"

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

OWS-00542: Unable to initialize, missing WebServicesProcessor

Cause: Unable to initialize interceptors due to missing WebService Processor

Action: System Internal Error - Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-00543: Unable to provision web service, cannot read WSDL. Error: {0}

Cause: Could not read WSDL.

Action: Check the WSDL URL for correctness and try again or check the server logs for details.
Level: 1

Type: ERROR

Impact: Files

OWS-00544: Error destroying interceptors {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-00545: Unable to read SOAP message {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Data

OWS-00546: Invalid port configuration {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OWS-00547: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OWS-00548: The error stack trace: {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-00549: The WSDL has overloaded operations "{0}".

Cause: The WSDL has overloaded operations.

Action: Avoid using overloaded operations.
Level: 1

Type: WARNING

Impact: Programmatic

OWS-00550: JDK1.5 enum is not supported "{0}".

Cause: JDK1.5 enum is not supported

Action: Provide a custom seriallizer.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-03001: Unable to load wsm config file: {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Configuration

OWS-03002: Failed to load wsm config schema: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OWS-03003: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OWS-03004: {0}

Cause: An exception occured while webservice management configuration.

Action: Verify that the oracle proprietary descriptor for configuration is valid xml file and confirms to the schema "http://xmlns.oracle.com/oracleas/schema/11/oracle-webservices-client-11_1.xsd"
Level: 1

Type: ERROR

Impact: Configuration

OWS-03005: Unable to connect to URL: {0} due to {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Network

OWS-03006: Trying to connect to URL: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Network

OWS-03007: Reading client wsmgmt config file.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

OWS-03008: Reading client wsmgmt configuration file without validation.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

OWS-03009: Error reading client wsmgmt configuration {0}

Cause: Unexpected error occurs while reading client configuration file

Action: NONE
Level: 1

Type: ERROR

Impact: Configuration

OWS-03010: Error creating default client wsmgmt configuration {0}

Cause: Unexpected error occured while creating default client side configuration file

Action: System Internal Error - Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OWS-03011: Error parsing client wsmgmt configuration file {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OWS-03012: Error parsing client wsmgmt configuration file {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OWS-03013: Error parsing client wsmgmt configuration file {0}

Cause: Unexpected error occured while parsing client webservice management configuration file

Action: Verify that client side configuration file is a valid xml file
Level: 1

Type: ERROR

Impact: Configuration

OWS-03014: Error loading policy access cache configuration {0}

Cause: Policy access cache configuration file could not be loaded due to unexpected error

Action: System Internal Error - Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OWS-03015: Error accessing policy from cache {0}

Cause: Accessing policy from cache is failed

Action: System Internal Error - Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OWS-03016: Error loading interceptor class {0}

Cause: Failed to looad the Inteceptor class

Action: Ensure all required webservices client side jar files available in classpath
Level: 1

Type: ERROR

Impact: Configuration

OWS-04001: System configured servlet pre-handler: {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-04002: The webservices management interceptor generated an exception during fault handling: {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-04003: The SOAP request for port: {0} is: {1}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-04004: Failed to unregister the web service MBeans {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-04005: An error occurred for port: {0}: {1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-04007: Error in system configured ejb prehandler: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-04008: The JAXRPC servlet has been destroyed for port: {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-04009: The webservices management interceptor ran the response chain.

Cause:

Action:
Level: 16

Type: TRACE

Impact: Requests/Responses

OWS-04010: The SOAP response for port: {0} is: {1}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-04011: Error in resolving the webservice endpoint: {0}

Cause: Failed to determine the WebService Endpoint for the servlet

Action: None
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-04012: Error initialising jms listeners: {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-04013: System configured ejb prehandler: {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-04014: Error in system configured servlet post-handler: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-04015: The webservice invocation was one way.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-04016: Resolving endpoint location :{0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-04017: The JAXRPC servlet has been initialized for port :{0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-04018: Error processing soap message over jms :{0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-04019: The webservices management interceptor ran the request chain.

Cause:

Action:
Level: 16

Type: TRACE

Impact: Requests/Responses

OWS-04020: Error during handler invocation:

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-04021: The webservices management interceptor ran the fault chain.

Cause:

Action:
Level: 16

Type: TRACE

Impact: Requests/Responses

OWS-04022: Inserted fault message for exception {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-04023: System configured servlet post-handler: {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-04024: Error in system configured ejb post-handler: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-04025: Failed to register the web service MBeans for endpoint: {0} the error is: {1}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-04026: An I/O error occurred for port: {0}: {1}.

Cause: An unexpected IO error occured while processing service request.

Action: None
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-04027: The webservice is an ejb webservice

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-04028: Error occurred while trying to display the test page: {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-04029: Error in system configured servlet pre-handler: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-04030: System configured ejb post-handler: {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-04031: [J2EEDatabaseImplementor] dsName {0} {1} {2} {3}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-04032: Error instantiating target class constructor {0} {1}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-04033: [J2EEDatabaseImplementor] method invoked {0} {1}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-04034: Error doing JNDI lookup on target {0} {1}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-04035: Error setting connection target: {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-04036: Error setting connection target: {0} {1}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-04037: Error creating target: {0} {1}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-04038: {0} {1}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-04039: Error closing connection: {0}

Cause: Failed to close the connection to specific database

Action: None
Level: 1

Type: ERROR

Impact: Network

OWS-04040: [J2EEDatabaseImplementor] target {0} {1}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-04041: {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Configuration

OWS-04042: Error happened while loading the DDs

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OWS-04043: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-04044: The referenced wsdl file has changed, please re-deploy {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Data

OWS-04045: Malformed Request Message: {0}

Cause: Received malformed SOAP request message

Action: Ensure the correct SOAP message constructed at client side
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-04046: {0} {1}

Cause: A server side fault occured while handling the SOAP message

Action: Please see the exception or server side log for more detail
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-04047: Cannot create xslt transformer

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-04048: xslt transformation failed

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-04049: Error creating the template

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-04050: Unable to load the webservices management interceptor pipeline

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-04051: non jsr109 run time

Cause:

Action:
Level: 1

Type: TRACE

Impact: Compliance

OWS-04052: Unable to determine operation id from SOAP Message.

Cause:

Action:
Level: 32

Type: TRACE

Impact: Requests/Responses

OWS-04058: Reading WSM config file.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Configuration

OWS-04059: Reading WSM config file without validation.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Configuration

OWS-04060: Writing WSM config file.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Configuration

OWS-04061: Internal JMX error {0}

Cause: Internal error while configuring JMX

Action: None
Level: 1

Type: ERROR

Impact: Configuration

OWS-04062: XML parser configuartion error {0}

Cause: An unexpected error occured while parsing configuring the XML parser

Action: None
Level: 1

Type: ERROR

Impact: Configuration

OWS-04063: Starting WSM Config Manager

Cause:

Action:
Level: 1

Type: TRACE

Impact: Configuration

OWS-04064: Stopping WSM Config Manager

Cause:

Action:
Level: 1

Type: TRACE

Impact: Configuration

OWS-04065: Error creating default port configuration for interceptor {0}

Cause: The default port configuration for interceptor could not be created

Action: None
Level: 1

Type: ERROR

Impact: Configuration

OWS-04066: Missing port info for service.

Cause: The Port information for the service is missing

Action: Add the necessary port information while configuring dynamic service.
Level: 1

Type: ERROR

Impact: Configuration

OWS-04067: Error reading config file {0}

Cause: Failed to read the interceptor configuration file

Action: None
Level: 1

Type: ERROR

Impact: Configuration

OWS-04068: Error serializing default config {0}

Cause: Failed to serialize the default configuration for interceptor.

Action: None
Level: 1

Type: ERROR

Impact: Configuration

OWS-04069: Error serializing global configuration for {0} interceptor {1}

Cause: Failed to serialize global configration for interceptor.

Action: None
Level: 1

Type: ERROR

Impact: Configuration

OWS-04070: Error serializing configuration {0}

Cause: Failed to serialize the configuration

Action: None
Level: 1

Type: ERROR

Impact: Configuration

OWS-04071: Unrecognized interceptor configuration: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OWS-04072: Error writing config file {0}

Cause: Error writing the configuration file for interceptor to FileManager

Action: None
Level: 1

Type: ERROR

Impact: Configuration

OWS-04073: Error parsing wsmgmt configuration file {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OWS-04074: Error parsing wsmgmt configuration file {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OWS-04075: Error parsing wsmgmt configuration file {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OWS-04076: port-component-link: {0} resolved to port: {1}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Configuration

OWS-04077: error resolving port-component-link: {0} {1}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Configuration

OWS-04078: looking at all ejb-modules in app: {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Configuration

OWS-04079: endpoint port found in ejb package: {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Configuration

OWS-04080: looking for ejb-module: {0} in app: {1}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Configuration

OWS-04081: looking at all web-modules in app: {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Configuration

OWS-04082: endpoint port found in web package: {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Configuration

OWS-04083: looking for web-module: {0} in app: {1}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Configuration

OWS-04085: {0}

Cause:

Action:
Level: 16

Type: NOTIFICATION

Impact: Configuration

OWS-04086: {0}

Cause: An unexpected error occured

Action: None
Level: 1

Type: ERROR

Impact: Configuration

OWS-04087: Duplicate message was eliminated

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-04088: New reliable message is being stored {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-04089: The Reliability Interceptor was initialized

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-04090: The Reliability Interceptor was initialized

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-04091: Error invoking impl {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

OWS-04092: Unable to configure parser: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OWS-04093: Unable to parse schema: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Data

OWS-04094: unknown tag <{0}> in {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Data

OWS-04095: Logging client transport for service-ref {0} to log {1}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Network

OWS-04096: Reading Client WSM config file.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Configuration

OWS-04097: Error creating client default port configuration for interceptor {0}

Cause: Failed to create client default port configuration for interceptor

Action: None
Level: 1

Type: ERROR

Impact: Configuration

OWS-04098: Unable to model port {0} for the test page: {1}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Data

OWS-04099: Unable to model operation {0} for the test page: {1}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Data

OWS-04100: Unable to find provider port that is associated with the servlet named {0}. Please make sure <provider-name>{0}</provider-name> exists in oracle-webservices.xml.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OWS-04101: Unable to add dynamic provider endpoint. Please make sure service name {0} and port name {1} are unique. They are specified as arguments to the ProviderConfig.addService() method or in the endpoint associated WSDL.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OWS-04102: Unable to configure dynamic provider endpoint across cluster due to exception {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OWS-04103: Unknown element <{0}> in descriptor: {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OWS-04104: The oracle-webservices.xml configuration references a web service description named "{0}", but there is no web service description with that name in webservices.xml.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OWS-04105: The final WSDL path "{0}" cannot be parsed as a URL: {1}

Cause: The URL path for the final WSDL is not valid

Action: Provide the valid URL location for the WSDL.
Level: 1

Type: ERROR

Impact: Configuration

OWS-04106: The value of the element named "{0}" ({1}) in {2} is invalid. Please refer to the XML schema of this descriptor for acceptable values.

Cause: Found invalid value of an element declared in webservice deployment descriptor

Action: Please refer to the XML schema of this descriptor for acceptable values for this element.
Level: 1

Type: ERROR

Impact: Configuration

OWS-04107: The proprietary implementor type is not specified.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OWS-04108: An error was encountered while trying to write the runtime configuration for the web service endpoint named "{0}": {1}

Cause: An error was encountered while trying to write the runtime configuration for the web service endpoint.

Action: None
Level: 1

Type: ERROR

Impact: Files

OWS-04109: The SOAP fault for port: {0} is: {1}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-04110: Error downloading import: Invalid URL

Cause: The specified URL for the imported WSDL is invalid

Action: Provide the correct URL location for the WSDL import
Level: 1

Type: ERROR

Impact: Data

OWS-04111: Proxy information not set, external import downloads may fail.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OWS-04112: The policy accessor configuration could not be loaded from {0}: {1}. Using default configuration instead.

Cause: Failed to load policy accessor configuration

Action: No action required as incase of this, default policy accessor configuration will be used
Level: 1

Type: WARNING

Impact: Configuration

OWS-04113: Policy advertisement failed for {0}: {1}

Cause: Failed to advertise the policy in the WSDL

Action: None
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-04115: An error occurred for port: {0}: {1}.

Cause: A server side exception occured while processing request or creating the response message

Action: Please see the server side log for the detail.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-04116: The error stack trace: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-04117: {0}

Cause: Exception occured while configuring dynamic provider based endpoint

Action: None
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-04119: Local service registration failed for {0}: {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OWS-04121: Invalid use of <web-site> element in oracle-webservices.xml.<web-site> element must have two attributes "host" and "port" with valid values

Cause: <web-site> element of oracle-webservice.xml doesn't contain 'host' and 'port' attributes with valid values

Action: Add valid 'host' and 'port' attributes to the <web-site> element, or remove the element.
Level: 1

Type: ERROR

Impact: Configuration

OWS-04122: Webservices deployment descriptor for module {0} not found at {1}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-04123: Unsupported oracle-webservices deployment descriptor for module {0}, schema version {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OWS-04124: Failed to register the web service Config MBeans for application: {0} endpoint: {1} the error is: {2}

Cause: Failed to register the web service config MBeans for endpoint

Action: None
Level: 1

Type: WARNING

Impact: Configuration

OWS-04125: cannot find WSDL definition required to validate input

Cause: cannot load web service WSDL definition, which is required for schema validation of input

Action: Ensure that the WSDL is available, or set schema validation of input to false
Level: 1

Type: ERROR

Impact: Configuration

OWS-04126: Input Violates Schema

Cause: SOAP body element of the input message cannot be validated against schema in the WSDL

Action: Correct input message body, input message type in the WSDL schema, or set schema validation of input to false
Level: 1

Type: ERROR

Impact: Data

OWS-04127: Invalid query string

Cause: User has specified invalid URL Query String.

Action: Verify that the correct query string is specified for acccessing the testpage.
Level: 1

Type: ERROR

Impact: Other

OWS-04128: Failed to deploy/initialize the application as given archive is missing required standard webservice deployment decriptor.

Cause: The user suppplied war archive is missing required webservice deployment descriptor

Action: Create WAR file with required webservice deployment descriptor or use WSA's jaxwsAssemble command to assemble the WAR file.
Level: 1

Type: ERROR

Impact: Other

OWS-04129: Failed to unregister mbean : "{0}". This may later cause error to register mbean with that name.

Cause: JMX Framework failed to unregister pre-existing MBean.

Action: See error message.
Level: 1

Type: NOTIFICATION

Impact: Deployment

OWS-04130: Failed to initialize Tie class "{0}" at runtime due to Error: {1}

Cause: Failed to initialize the tie class on server side due to classloading issue or java security.

Action: Please look the server log for exact cause of an error.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-04131: SOAP must understand error. Server could not understand WS-Security header "{0}" that has "mustUnderstand" attribute set as "true". Ensure that security policy has been attached and enabled on the webservice endpoint.

Cause: Server could not understand WS-Security header which has mustUnderstand flag set to true.

Action: The user needs to attach correct security policy to webservice endpoint.
Level: 1

Type: ERROR

Impact: Other

OWS-04132: SOAP must understand error. Server could not understand one or more SOAP headers : {0}

Cause: Server could not understand SOAP header which has mustUnderstand flag set to true.

Action: Please look the SOAPFault string for any detail message and check the client and server side configuration.
Level: 1

Type: ERROR

Impact: Other

OWS-11001: Binding "{0}" references unknown port type named "{1}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Data

OWS-11004: Unable to configure parser: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Data

OWS-11005: Unable to parse schema: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Data

OWS-11006: Could not find operation: {0}, {1}, {2}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Data

OWS-11007: Reading document at: {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Data

OWS-11008: Failed to read WSDL from {0}:WSDL not found

Cause:

Action:
Level: 1

Type: WARNING

Impact: Data

OWS-11011: Attribute "{0}" is not allowed in <wsdl:{1}> {2} - attribute ignored.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Data

OWS-11015: Trying to Access Resource at URL: {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Data

OWS-11016: Could not import schema using namespace "{0}" as systemId

Cause:

Action:
Level: 1

Type: WARNING

Impact: Data

OWS-12001: Wrong char in base64 {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12002: Element not bound, cannot determine SOAP version.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12003: Unknown SOAP Implementation

Cause: The SOAP Implementation was not for either 1.1 or 1.2

Action: Internal Error
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-12004: Not implemented

Cause: This functionality is not implemented

Action: None
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-12005: Data handler error: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12006: No data handler associated with this attachment

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12007: Null dataHandler argument to setDataHandler

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12008: Unable to externalize attachment

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12009: Unable to copy MIME header

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12010: Unable to copy MIME headers into attachment

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12011: Attachment part has no content!

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12012: Cannot set content from null InputStream!

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12013: There is no data

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12014: There is no data handler

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12015: Unable to get data from attachment

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12016: Unable to create DataContentHandler for {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12017: Parent element cannot be null.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12018: Cannot set parent from a different implementation.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12019: Error converting DOM nodes into SOAP nodes

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12020: Fragment contains invalid character!

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12021: No data handler associated with this OracleSOAPElement

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12022: DTD is not supported by SOAP 1.2

Cause: SOAP 1.2 Message contains reference to DTD

Action: None
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-12023: Prefix ''{0}'' is not defined.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12024: Unable to create a JAXP transformer

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12025: Envelope can only have one Header element.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12026: Envelope can only have one Body element.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12027: Cannot add element of type ''{0}'' to SOAP Envelope

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12028: Cannot add Header after Body

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12029: Cannot add more than one Body

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12030: SOAP Header must precede Body

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12031: Cannot set element QName for SOAPEnvelope!

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12032: SOAPHeaderElement can only have SOAPHeader as parent.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12033: Cannot set element QName for SOAPHeader!

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12034: Operation not supported

Cause: This functionality is not supported for this object

Action: None
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-12035: Content-Type not specified

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12036: Invalid Content-Type: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12037: Unable to internalize message

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12038: Invalid MIME type: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12039: DIME attachments must have a valid mime type

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12040: Error serializing message: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12041: Unsupported datatype in attachment: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12042: Unable to get header stream in saveChanges

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12043: Unrecognized PACKAGING_STYLE property value: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12044: Unsupported protocol: {0}

Cause: The specified protocol is not supported

Action: None
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-12045: Error adding child

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12046: SOAP Envelope attributes should be qualified. Attribute QName: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12047: Root element must be: ''Envelope''

Cause: Invalid SOAP message - does not have root element of <Envelope>

Action: None
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-12048: Envelope namespace must be: {0} is {1}

Cause: Invalid SOAP message - incorrect namespace for <Envelope> element

Action: None
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-12049: DTD is not supported by SOAP

Cause: SOAP Message contains reference to DTD

Action: None
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-12050: SOAP Version {0} is not supported

Cause: The SOAP Version was not either 1.1 or 1.2

Action: Please use a supported SOAP Version
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-12051: Can not have a DTD declaration in SOAP envelope

Cause: SOAP Message contains DTD declaration

Action: None
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-12052: Can not have a processing instruction in SOAP envelope

Cause: SOAP Message contains processing instruction

Action: None
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-12053: Source does not have a valid Reader or InputStream

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12054: Error setting the source for SOAPPart: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12055: SOAP exception while trying to externalize: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12056: Unable to copy MIME headers into SOAP part

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12057: Cannot set value on document node

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12058: Document nodes cannot have parents

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12059: Illegal Operation

Cause: This operation is not allowed on this object

Action: None
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-12060: Mime Header Content-Type: {0} requires SOAP envelope namespace: {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12061: Not implemented for comments

Cause: This functionality is not implemented for comments

Action: None
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-12062: Null object for BinaryDataContentHandler

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12063: Unable to write binary data to stream {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12064: GIF encoding not supported

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12065: "{0}" DataContentHandler requires Image object, was given object of type {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12066: Invalid content type "{0}" for ImageContentHandler

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12067: Null object for ImageContentHandler

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12068: JPEG objects must be of type Image or BufferedImage [Got: {0} ]

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12069: Unable to JPEG encode image {0}{1}{2}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12070: Invalid type "{0}" on StringDCH

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12071: Invalid content type "{0}" for XmlDCH

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12072: Unable to write XML attachment

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12073: Fault can''t have more than one ''detail'' element.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12074: Not supported in SOAP 1.1

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12075: DIME encoded messages must have SOAP Envelope as first payload

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12076: Invalid value of ''type'' parameter for Content-Type header: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12077: Could not find appropriate parser

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12078: Error reading from stream

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12079: SAX parse error

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12080: Transformation error

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12081: Cannot have more than one Value

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12082: Fault codes can only have Subcode and Value as children.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12083: Envelope can only contain Header and Body elements.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12084: Code element already exists

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12085: Node element already exists

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12086: Role element already exists

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12087: Detail element already exists

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12088: {0} not allowed in Fault

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12089: Fault can only have one detail

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12090: Node cannot have child elements.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12091: FaultReason can only contain Text elements

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12092: Role cannot have child elements.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12093: FaultText12 cannot have any child elements

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12094: Cannot construct URI with null/empty scheme!

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12095: Cannot construct URI with null/empty scheme-specific part!

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12096: Scheme is required!

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12097: Userinfo may not be specified if host is not specified!

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12098: Port may not be specified if host is not specified!

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12099: Query string cannot be specified in path and query string!

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12100: Fragment cannot be specified in both the path and fragment!

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12101: Cannot initialize URI with empty parameters.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12102: No scheme found in URI.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12103: {0} is invalid. Port should only contain digits!

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12104: Cannot initialize path from null string!

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12105: Path contains invalid escape sequence!

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12106: Path contains invalid character: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12107: Query string contains invalid escape sequence!

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12108: Query string contains invalid character:{0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12109: Fragment contains invalid escape sequence!

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12110: Fragment contains invalid character:{0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12111: Cannot set scheme from null string!

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12112: The scheme is not conformant.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12113: Userinfo cannot be set when host is null!

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12114: Userinfo contains invalid escape sequence!

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12115: Userinfo contains invalid character:{0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12116: Host is not a well formed address!

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12117: Port cannot be set when host is null!

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12118: Invalid port number!

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12119: Query string can only be set for a generic URI!

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12120: Query string cannot be set when path is null!

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12121: Fragment can only be set for a generic URI!

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12122: Fragment cannot be set when path is null!

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12123: UUID(): this should never happen: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12124: UUID(): Padding failure

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12125: UUID.toByteString(): should never happen:

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12126: Error reading stream

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12127: Not finished streaming payload

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12128: Unexpected end of stream

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12129: Buffer must be at least as large as boundary: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12130: Message not started or Part not ended

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12131: BASE64Decoder: Not enough bytes for an atom.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12132: CharacterEncoder::encodeBuffer internal error

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12133: Cannot set value of an element with non-text children.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12134: Cannot add more than one Header

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12135: Invalid content type "{0}" for BinaryDataContentHandler

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12136: Invalid Content-Type: {0}/{1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12137: Path contains invalid character!

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-12138: Envelope size exceeds limit

Cause: The size of the SOAP envelope exceeds the limit, which was configured for this port.

Action: Reduce the size of SOAP envelope or increase the set limit.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-12139: Envelope nesting depth exceeds limit

Cause: The depth of nesting XML elements in the SOAP body exceeds the limit, which was configured for this port.

Action: Reduce the nesting in the SOAP body or increase the set limit.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-12140: Error building Mime body part

Cause: The current part of the MIME Multipart is syntactically invalid

Action: Check that headers for all parts are legitimate names and syntactically correct
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-12141: Failed to match initial boundary

Cause: The MIME Multipart boundary delimiter characters '--' are missing

Action: Check that the sender is creating a MIME Multipart message as required
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-12142: Failed to match initial boundary

Cause: The current part of the Multipart is missing the required CRLF after the boundary

Action: Check that the sender is creating a well-formed MIME Multipart message
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-12143: Expected boundary delimiter

Cause: The MIME Multipart boundary was not found in between parts

Action: Check that the sender is creating a well-formed MIME Multipart message
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-12144: File has already been opened in streaming mode

Cause: An attempt was made to open an attachment for streaming more than once

Action: Do not use streaming attachments if a part must be opened more than once
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-12145: Output stream not available for streaming

Cause: An attempt was made to open a streaming attachment for writing

Action: Check if the code is requesting an OutputStream instead of an InputStream
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-12146: Error parsing content type: {0}

Cause: The HTTP Content-Type header is syntactically invalid

Action: Check that the sender is creating a valid MIME Multipart message as required
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-12147: MIME 'boundary' parameter not found in Content-Type

Cause: The HTTP Content-Type header is missing the required 'boundary' parameter

Action: Check that the sender is creating a valid MIME Multipart message as required
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-12148: Cannot find start part {0}

Cause: The 'start' part of the MIME Multipart message cannot be determined

Action: Ensure that the Content-Type has a 'start' parameter or that the message has at least one part
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-15001: An extension registry was not found for the element type ''{0}''

Cause: An extension registry was not found for an element type

Action: None
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-15002: A failure occurred in loading WSDL from ''{0}''

Cause: A failure occurred in loading WSDL

Action: Verify if the WSDL exists at the specified URL
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-15003: An error occurred finding pluggable providers: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-15004: WSDL contains an operation type of ''{0}'' which is not supported for port type ''{1}''

Cause: WSDL contains an operation type that is not supported

Action: Modify the WSDL and change the operation type to a supported one
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-15005: An error occurred when invoking the method. Type of WSIF invocation was ''{1}'' and method name was (''{0}'')

Cause: An error occurred when invoking the method

Action: Check client code and network connection
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-15006: Multiple WSIFProvider found supporting the same namespace URI ''{0}''. Found (''{1}'')

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-15007: Using WSIFProvider ''{0}'' for namespaceURI ''{1}''

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

OWS-15008: WSIFDefaultCorrelationService removing correlator due to timeout. ID:''{0}''

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-15009: Using correlation service - ''{0}''

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

OWS-15010: Exception thrown while processing asynchronous response - ''{0}''

Cause: Exception thrown while processing asynchronous response

Action: None
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-15011: Preferred port ''{0}'' was not available

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

OWS-50001: The @WebService.portName is not allowed on endpoint interfaces.: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-50002: The @WebService.serviceName is not allowed on endpoint interfaces.: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-50003: Could not find schema type : {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-50004: The method "{0}" does not have the AsyncHandler type parameter.

Cause: The callback type asynchronous method that returns java.util.concurrent.Future must have the last parameter of the type AsyncHandler.

Action: Add the last parameter of type AsyncHandler in the method, or regenerate the interface using wsa tool.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50005: Exception while retrieving the soap message from the internal callback handler.

Cause: Refer to the details of the message for further information on possible causes.

Action: Refer to the details of the message for further information on possible actions.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50006: Could not deserialize the soap message to get the return value

Cause: Refer to the details of the message for further information on possible causes.

Action: Refer to the details of the message for further information on possible actions.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50007: Could not create the instance of asynchronous response bean of type "{0}"

Cause: Cound not create the response Refer to the details of the message for further information on possible causes.

Action: Check if the bean has a default constructor and the constructor is accessible.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50008: Cound not set the field ''{0}'' in the object of type ''{1}''.

Cause: Possible causes are invalid field name, abcense of setter, inaccessible setter or mismatched field type.

Action: Correct the bean class based on the details of the message.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50009: The method "{0}" must have a parameterized return type.

Cause: The return type must be parameterized with the ResponseBean or the actual return type of the web service call.

Action: Add the appropriate return type as the parameter of the AsyncHandler parameter. Or use the JAX-WS artifacts generation tools to generate the proper interface of asynchronous methods.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50010: The method "{0}" must have a parameterized AsyncHandler parameter.

Cause: The AsyncHandler parameter must be parameterized with the ResponseBean or the actual return type of the web service call.

Action: Add the appropriate return type as the parameter of the Response. Or use the JAX-WS artifacts generation tools to generate the proper interface of asynchronous methods.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50011: Dispatch currently does not support REST style service.

Cause: The REST request cannot be processed via Dispatch. The feature is not yet supported.

Action: Construct an HTTP Request for a RESTful webservice.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50012: Could not determine the soap version from the BindingType annotation''s value "{0}". Assuming SOAP version as 1.1

Cause: The value of the BindingType annotation is invalid.

Action: Use one of the valid values for the BindingType annotation. Refer to the documentation of javax.xml.ws.BindingType.
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-50013: Could not determine a valid protocol binding to generate for the binding string {0}. A SOAP 1.1 binding will be the only protocol binding generated in the WSDL.

Cause: The value of the BindingType is not supported or is invalid

Action: Only SOAP and HTTP protocols are supported. Refer to the documentation or JAX-WS specification for valid values for javax.xml.ws.BindingType.
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-50014: Both @Deployment.restSupport() and @BindingType(javax.xml.ws.http.HTTPBinding.HTTP_BINDING) were specified. Only the latter will be used.

Cause: Both the @Deployment.restSupport() and @BindingType(javax.xml.ws.http.HTTPBinding.HTTP_BINDING) were provided.

Action: @Deployment.restSupport() has been deprecated. It should not be used. Use @BindingType(javax.xml.ws.http.HTTPBinding.HTTP_BINDING) instead.
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-50015: The given ws-addressing namespace "{0}" is not one of the supported wsa versions.

Cause: The input ws addressing version is not supported

Action: Correct the addressing version to use 2003/03 or 2004/08 or 2005/08.
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-50016: IOException converting AddressingInfo to String.

Cause: IO error converting addressing info to String

Action: correctAddressingInfo
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50017: Port Metadata missing from the given callback interface class.

Cause: Metadata such as port name or targetnamespace can not be found from the given input class.

Action: Add the needed annotation to the interface class.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50018: The file "{0}" does not exist.

Cause: The file name specified in syncInterfaceFileName could not be opened.

Action: Check if the file name is correct and it exist.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50019: The file "{0}" should have some class or interface defined.

Cause: The syncInterfaceFileName is not containing any class.

Action: Check if the file has any class defined. Make sure that the file is compilable and so free of errors.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50020: There is no method in the file "{0}" to convert to asynchronous method.

Cause: The interface file should have at least one method defined.

Action: Add the required methods in the interface file.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50021: Cannot determine what methods to convert to asynchronous in file "{0}".

Cause: The interface file has more than one method defined and no method name has been specified for conversion.

Action: Please sepcify what methods need to be converted to asynchronous methods.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50022: The file "{0}" does not exist.

Cause: The file name specified in asyncInterfaceFileName could not be opened.

Action: Check if the file name is correct and it exist.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50023: The file "{0}" should have some class or interface defined.

Cause: The asyncInterfaceFileName is not containing any class.

Action: Check if the file has any class defined. Make sure that the file is compilable and so free of errors.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50024: Java Model is not set in the file system.

Cause: The file system does not have any Java Model set.

Action: Make sure that the file system has the Java Model set.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50025: JAX-WS endpoint bean has @SOAPBinding.use annotation that specifies the 'encoded' message format which is not supported in JAX-WS. JAX-WS 2.0 mandates 'literal' use only and supports either rpc/literal or document/literal style binding.

Cause: In JAX-WS endpoint bean, @SOAPBinding.use annotation has 'encoded' value which is not supported in JAXWS

Action: In JAX-WS endpoint bean, use either rpc/literal or document/literal style binding.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50026: Invalid use of @WebMethod annotation on method "{0}".As per JSR-181, if 'exclude' element is specified on @WebMethod annotation then other elements must not be specified with it.

Cause: In JAX-WS endpoint bean, @WebMethod annotation has 'exclude' element that is used with other elements like 'action' or 'operationName' which is against the JSR-181 spec

Action: Do not use 'action' or 'operationName' element if 'exclude' element is specified on @WebMethod annotation.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50027: @SOAPBinding annotation is only allowed on a method if SOAPBinding.style is "DOCUMENT". Method "{0}" specifies @SOAPBinding.style to "RPC" which is against JSR-181 so it will be ignored and default sytle "DOCUMENT/LITERAL" will be used.

Cause: @SOAPBinding annotation at method level has 'rpc' style which is not valid as per JSR-181

Action: Do not specify the 'rpc' style with @SOAPBinding annotation used at method level in JAX-WS enpoint interface/bean.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50028: The parameter/return type "{0}" in the method "{1}" is not supported. This method will not be exposed.

Cause: The parameter/return type is NOT supported.

Action: Do not use the unsupported JAVA Type in method parameter or return value.
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-50029: The method "{0}" has more than one input parameter that is not mapped to a header and style is BARE. This method will not be exposed.

Cause: The java method has more than one input parameter that is not mapped to a header.

Action: Map java parameters to a header using @WebParam annotation or use wrapped style operation.
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-50030: wsdlDocumentLocation is currently not supported.

Cause: WSDLDocumentLocation is currently not supported

Action: See error message.
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-50031: Input address, serviceName and endpointName can not be all null

Cause: ServiceName, PortName, or Address can not be all null.

Action: Supply a non null argument for one of the parameters.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50032: Service name has not been specified for a non null port name.

Cause: ServiceName can not be null when port name is specified.

Action: Supply a non null service name.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50033: Exception occured building W3CEndpointReference.

Cause: Exception occured when building W3C EndpintReference.

Action: Verify that the Endpoint Reference address and other metadata to build W3C EndpointRefence are correct.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50034: The method "{0}" is ignored. {1}

Cause: The JAVA method is ignored in WSDL generation.

Action: See error message.
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-50035: "{0}" cannot be used as parameter type or return value in "{1}".

Cause: The JAVA type cannot be used as parameter type or return value in RPC-Literal and Document-Literal-BARE.

Action: See error message.
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-50036: Operations on portType should be unique, use @WebMethod(operationName="...") on java method "{0}" to resolve conflict.

Cause: Operations the WSDL port type need to be unique.

Action: Map non-unique JAVA method names to unique WSDL opeartion names using @WebParam(operation"...")
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50037: Failed to load endpoint interface class "{0}" specified with @WebService.endpointInterface annotation in endpoint bean class "{1}". This may cause unexpected behavior like generated WSDL would be different from the expected one.

Cause: Classloader failed to load the enpoint interface class that is implemented by the enpoint bean class

Action: Check that the endpoint interface class is in the classpath
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50038: Found "{0}" annotation on class "{1}" which is not allowed with PortableWebService endpoint class.

Cause: User has specified the annotation on either webservice endpoint interface or implementation class which is not allowed with Portable WebService

Action: Remove annotation which is not valid with @PortableWebService annotation.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50039: Could not load callback interface "{0}". Any methods defined in the interface will be ignored

Cause: Callback interface class is not available or misspelt.

Action: Make callback interface available.
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-50040: Failed while accessing Keystore details.

Cause: Keystore details are not setup.

Action: Configure keystore details for the server.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50041: [MessageID: {0}] Started asynchronous request processing for the service "{1}" with the message selector "{2}". Transaction enabled: "{3}"

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

OWS-50042: [MessageID: {0}] Could not complete asynchronous request processing successfully. No response will be sent to the client. Analyze the details of the exception as it is most likely the server side configuration error.

Cause: Asynchronous request processing resulted in exception

Action: Analyze the exception and take appropriate action.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50043: JMS queue connection failed.

Cause: JMS queues are not created, or wrong queue names are used.

Action: Check that queues are created and referenced with the right names.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50044: [MessageID: {0}] Could not send async request message to the JMS queue.

Cause: JMS queues are not created, or wrong queue names are used.

Action: Check that queues are created and referenced with the right names
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50045: Could not close the connection to JMS queue

Cause: Internal error.

Action: Can be ignored.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50046: [MessageID: {0}] Sending message to JMS queue "{1}" for async processing of service "{2}"

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

OWS-50047: [MessageID: {0}] No JMS queue specified for the request with non-anonymous replyTo for service "{1}"

Cause: JMS queues are not created, or wrong queue names are used.

Action: Check that queues are created and referenced with the right names
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50048: ConnectionFactory for the destination "{0}" used for asynchronous service processing is not specified. Using default: "{1}"

Cause: Connection factory is not specified.

Action: Specify connection factory if default is not good.
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-50049: Found the connectionFactory for the destination "{0}" used for async service processing: "{1}"

Cause:

Action:
Level: 32

Type: TRACE

Impact: Requests/Responses

OWS-50050: Found the JMS queue for async service processing: "{0}"

Cause:

Action:
Level: 32

Type: TRACE

Impact: Requests/Responses

OWS-50051: JMS queue for async service processing not found. Configure a JMS queue for this application.

Cause: JMS queue are either not created or misspelt in the annotations.

Action: Verify that the JMS queues are created and the same are referred in the annotations in the service implementation class.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50052: Simple MessageListener is not set as MDB might be listening to the queue.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-50053: Simple MessageListener is listening to the queue.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-50054: Successfully connected to queue "{0}" using connection factory "{1}"

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-50055: [MessageID: {0}] Successfully sent the message to queue "{1}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-50056: Received a fault and user did not supply a fault listener. Details: "{0}"

Cause: The web service implementation class does not have any methods annotated as FaultListener and either the input is fault, or the response from the callback service is fault.

Action: Add the fault listener method if desired.
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-50057: Failed while re-creating the soap message from the JMS message

Cause: System error

Action: Analyze the exception reported in the log.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50058: Failed while re-creating the addressing header from the JMS message

Cause: System error

Action: Analyze the exception reported in the log.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50059: [MessageID: {0}] Error while processing the message off the JMS queue.

Cause: System error

Action: Analyze the exception details.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50060: [MessageID: {0}] Request processor MDB failed.

Cause: Asynchronous request processinf MDB has failed.

Action: Analyze the exception details.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50061: Context is available locally. Should happen only while running in-process message listener.

Cause: Internal system error.

Action: Internal system error.
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-50062: [MessageID: {0}] Error while processing response. Will try the fault handler in web service implementation class.

Cause: Callback service may be down or policy of the callback service is not matching with the callback client.

Action: Analyze the exception details.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50063: [MessageID: {0}] Response is to be sent to the callback service

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-50064: [MessageID: {0}] Failed to send the response to the callback service.

Cause: Callback service may be down, the callback URL may be wrong or callback service is not configured properly.

Action: Verify the configuration of callback service and take action based on the details of exception.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50065: Saved the context for async service in JNDI with the key "{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-50066: Could not save the context for async service in JNDI with the key "{0}".

Cause: Internal system error.

Action: Internal system error.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50067: Could not cleanup the context for async service in JNDI as it was not found.

Cause: Internal system error.

Action: Internal system error.
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-50068: Removed the saved context for async service in JNDI for "{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-50069: Could not remove the saved context for async service in JNDI with the key "{0}".

Cause: Internal system error

Action: Internal system error.
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-50070: Found the context for async service in JNDI with key "{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-50071: [MessageID: {0}] Error while trying the fault handler in web service implementation class.

Cause: The fault handler method did not execute successfully.

Action: Check the fault handler code.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50072: [MessageID: {0}] Got SOAPFaultException while executing the asynchronous operation

Cause: This might be because of invalid request, missing resources in the service implementation or a bug.

Action: Analyze the exception details.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50073: [MessageID: {0}] Got Exception while executing the asynchronous operation.

Cause: This might be because of invalid request, missing resources in the service implementation or a bug.

Action: Analyze the exception details.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50074: [MessageID: {0}] Asynchronous response is ready to be queued.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-50075: Transaction not enabled for request processing.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-50076: [MessageID: {0}] Started asynchronous response processing for the service "{1}" with the message selector "{2}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-50077: [MessageID: {0}] Response Processor MDB is running under a transaction. rollbackOnly is "{1}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-50078: [MessageID: {0}] Response Processor MDB is not running in a transaction

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-50079: [MessageID: {0}] Completed asynchronous response processing successfully. Client must have received the response by now.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-50080: [MessageID: {0}] Completed asynchronous response processing with exception. Client will not receive any response.

Cause: Callback service is not up or it's configuration/policy is not matching with the async server.

Action: Analyze the exception and configure the callback service.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50081: [MessageID: {0}] Response processor MDB failed.

Cause: Callback service is not up or it's configuration/policy is not matching with the async server.

Action: Analyze the exception and configure the callback service.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50082: [MessageID: {0}] Sending response will not be retried as callback service sent soap fault back. Http response code was "{1}".

Cause: Callback service sent the fault back. Retrying may not help. There may be some configuration problem,

Action: Analyze the fault and configure the callback service properly.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50083: [MessageID: {0}] Request Processor MDB is running under container managed transaction.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-50084: [MessageID: {0}] Request Processor MDB is not running under container managed transaction

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-50085: [MessageID: {0}] Could not create the user transaction for request processing.

Cause: Internal system error.

Action: Analyze the exception in the log.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50086: [MessageID: {0}] Started the user transaction for request processing.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-50087: [MessageID: {0}] Could not begin the user transaction for request processing.

Cause: Internal system error.

Action: Analyze the exception in the log.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50088: [MessageID: {0}] Could not create user transaction for Web Method execution.

Cause: Internal system error.

Action: Analyze the exception in the log.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50089: [MessageID: {0}] Started a user transaction for executing the web method.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-50090: [MessageID: {0}] Could not begin user transaction for Web Method execution.

Cause: Internal system error

Action: Analyze the exception in the log.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50091: [MessageID: {0}] Suspended main transaction.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-50092: [MessageID: {0}] Could not suspend the main transaction for executing the web method.

Cause: Internal system error.

Action: Internal system error.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50093: [MessageID: {0}] User transaction was marked for rollback after executing the web method.

Cause: Web method execution marked the transaction for rollback.

Action: It might be because of invalid input or a bug in the web method. Analyze the failure.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50094: [MessageID: {0}] Could not rollback the user transaction after executing the web method.

Cause: Internal system error.

Action: Analyze the exception in the log.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50095: [MessageID: {0}] User transaction is being rolledback after getting unexpected exception in executing the web method.

Cause: Web method did not complete successfully.

Action: It might be because of invalid input or a bug in the web method. Analyze the failure.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50096: [MessageID: {0}] User transaction is being rolledback after getting failure in getting response.

Cause: There might be some problem with the callback service or its configuration.

Action: Check if the callback service is up and configured properly.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50097: [MessageID: {0}] Completed Request processing. About to commit the web method transaction. Transaction status is "{1}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-50098: [MessageID: {0}] Completed Request processing. Web method transaction is not active.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-50099: [MessageID: {0}] Committed main trasnaction successfully

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-50100: [MessageID: {0}] Could not get the transaction manager (javax.transaction.TransactionManager).

Cause: Internal system error.

Action: Internal system error.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50101: [MessageID: {0}] Resumed suspended transaction

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-50102: [MessageID: {0}] Could not resume the suspended main trsanction.

Cause: Internal system error

Action: Internal system error.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50103: [MessageID: {0}] Rolled back a user transaction after executing the web method.

Cause: There might be some problem with the callback service or its configuration.

Action: Check if the callback service is up and configured properly.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50104: [MessageID: {0}] Could not rollback a user transaction after executing the web method.

Cause: Internal system error.

Action: Internal system error.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50105: [MessageID: {0}] Committed user transaction for web method

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-50106: [MessageID: {0}] Could not commit the user transaction for web method execution.

Cause: Internal system error.

Action: Analyze the related exception report in the log.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50107: [MessageID: {0}] Could not rollback the main transaction

Cause: Internal system error.

Action: Internal system error.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50108: [MessageID: {0}] Could not commit the main transaction

Cause: Internal system error.

Action: Internal system error.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50109: [MessageID: {0}] Http response from the Callback service is "{1}".

Cause: Callback service returned http response other 200 or 202.

Action: Analyze the details of soap message returned by call service or the http error code.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50110: [MessageID: {0}] Asynchronous response sent to the callback.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-50111: [MessageID: {0}] Received soap fault from the callback.

Cause: Callback has sent a soap fault as the response.

Action: Analyze the fault and configure the callback service properly.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50112: [MessageID: {0}] Could not dump the soap message

Cause: Internal system error.

Action: Internal system error.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50113: [MessageID: {0}] Could not create SSLSocketFactory.

Cause: Keystore may not have been configured properly.

Action: Configure the keystore details for the server.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50114: [MessageID: {0}] KeyStore file locations are not available. Configure it for the server to make the SSL work.

Cause: Keystore may not have been configured properly.

Action: Configure the keystore details for the server.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50115: Exception in handler chain

Cause: Handler chain has thrown some exception

Action: Look at the details of exception.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50116: Exception ignored during close

Cause: Internal system error.

Action: Can be ignored
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

OWS-50117: Unsupported message context, jaxws handler will not be called

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-50118: Unsupported message context, "{0}" could not handle fault

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-50119: Dispatch invocation error

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-50120: Cannot load client proxy extension "{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-50121: Error parsing handler chain: "{0}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-50122: Could not process callback interface "{0}". Any methods defined in the interface will be ignored

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-50123: Unsupported operation when generating schemas "{0}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-50124: Unknown Exception when generating schemas: "{0}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-50125: Could not load schema from location "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-50126: Could not determine binding id for binding "{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-50127: Could not determine wsdl ports.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-50128: Could not find service "{0}"; Using first service in WSDL instead.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-50129: No wsdl location or document specified

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-50130: No web module with name of "{0}" so a new war will be created

Cause: TBD

Action: TBD
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50131: Found web module with name of "{0}", so the generated contents will be merged.

Cause: TBD

Action: TBD
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50132: Can not specify war argument and have an input be an ear that contains a war with a matching context root.

Cause: TBD

Action: TBD
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50133: Error extracting war "{0}".

Cause: TBD

Action: TBD
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50134: Error while processing ejb-jar.xml for ejb module at "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-50135: Could not load jaxrpc annotation parser, the webservices in this ejb will not be manageable

Cause: TBD

Action: TBD
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50136: Multiple webservice descriptions in webservices.xml has the same port name "{0}" and service name "{1}", defaulting to webservice description named "{2}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-50137: Could not find wsdl URI "{0}" specified in webservices.xml.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

OWS-50138: Could not write operation metadata for "{0}".

Cause: Exception in writing operation metadata

Action: Analyze the exception.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50139: HandlerChain configuration file: "{0}".

Cause: TBD

Action: TBD
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50140: Failed to resolve HandlerChain annotation "file" value ({0}) as it is specified on "{1}"

Cause: TBD

Action: TBD
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50141: Fabric Registration ignored because this service does not use SDO binding.

Cause: TBD

Action: TBD
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50142: Registering service with fabric with service id: "{0}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

OWS-50143: Fabric Registration ignored because Register class "{0}" can not be instantiated.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-50144: Fabric Registration ignored because Register class "{0}" can not be accessed.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-50145: Fabric Registration ignored because Register class "{0}" not found.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-50146: Fabric Registration failed due to exception: "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-50147: SDO Type Registration failed due to exception: "{0}".

Cause: TBD

Action: TBD
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50148: Could not generate wsdl for class "{0}". Exception message is "{1}"

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

OWS-50149: There is more than one webservice with the name of "{0}" this can cause problems at deployment or runtime. To resolve the conflict add a serviceName property to a WebService annotation

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-50150: Could not read wsdl at "{0}", will generate it. Exception is "{1}"

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

OWS-50151: The service name "{0}" could not be found in the wsdl "{1}". Defaulting to the first service in the wsdl "{2}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-50152: The port name "{0}" could not be found in the wsdl "{1}". Defaulting to the first port named "{2}" in the service named "{3}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-50153: Multiple port components have the same service name "{0}" and port name "{1}", default to port component name "{2}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-50154: Can not add partner links to wsdl because there are not two port types, actual number is "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-50155: Error processing handler chain: "{0}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-50156: Unsupported type when generating schemas: "{0}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-50159: [MessageID: {0}] Messages could not be read while cleaning up the asynchronous message queues. Exception: "{1}".

Cause: System error

Action: Internal error
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50160: [MessageID: {0}] Successfully sent the "business logic initiated" message to the queue "{1}" with the JMS session having transaction flag: "{2}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-50161: [MessageID: {0}] Successfully sent the "response generated" message to the queue "{1}" with the JMS session having transaction flag: "{2}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-50162: [MessageID: {0}] Request message was found in the queue while processing the response

Cause: There might be a server/jvm crash after successful execution of business logic.

Action: No action required.
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-50163: [MessageID: {0}] Response is not available. The web method execution did not complete or the response was lost.

Cause: Response is not available. The web method execution did not complete or the response was lost.

Action: Retry calling the method if it is safe to do so.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50164: [MessageID: {0}] Found and discarded "{1}" message.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-50166: [MessageID: {0}] Response was already generated in the earlier run. No processing is required in the request processor MDB.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-50167: [MessageID: {0}] Business logic was already initiated in the earlier run but it did not complete for some reason. A fault will be sent to the callback service as the non-idempotent operation cannot be retried.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-50168: [MessageID: {0}] No status messages found. Going to process the request.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-50169: [MessageID: {0}] Processing the request for the first time.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-50170: [MessageID: {0}] Processing the request as an idempotent operation.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-50171: [MessageID: {0}] Message property: "{1}" = "{2}"

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-50172: [MessageID: {0}] Did not cleanup the status messages as isMDBRunningInCMT = "{1}" and mainTransactionActive = "{2}"

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-50173: [MessageID: {0}] Method "{1}": Status of userTransForWebMethod: "{2}"

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-50174: [MessageID: {0}] Method "{1}": Status of MDB transaction: "{2}"

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-50175: [MessageID: {0}] Sending asynchronous response to the queue using transacted session flag as "{1}". Idempotent flag: "{2}". MDB transaction active: "{3}". User transaction active: "{4}"

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-50176: [MessageID: {0}] Creating status message of type "{1}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-50177: Could not read the context for async service from JNDI with the key "{0}".

Cause: Internal system error.

Action: Internal system error.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50178: The password for the identity keystore could not be read from the security credential store while sending the response to the callback service. It should have been stored as key "{0}" in the map "{1}". Assuming no password is necessary.

Cause: The password for the identity keystore is probably not saved in the security credentials or, the map or the key name may be wrong.

Action: Save the password with appropriate key and the map as specified in the error.
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-50179: The password for recovering the key could not be read from the security credential store while sending the response to the callback service. It should have been stored as key "{0}" in the map "{1}". Assuming key password to be same as the identity keystore password.

Cause: The password for the private key is probably not saved in the security credentials or, the map or the key name may be wrong.

Action: Save the password with appropriate key and the map as specified in the error.
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-50180: The password for the trust keystore could not be read from the security credential store while sending the response to the callback service. It should have been stored as key "{0}" in the map "{1}". Assuming no password is necessary.

Cause: The password for the trust keystore is probably not saved in the security credentials or, the map or the key name may be wrong.

Action: Save the password with appropriate key and the map as specified in the error.
Level: 1

Type: WARNING

Impact: Requests/Responses

OWS-50181: Exception while accessing the password from the security credential store for using SSL while sending the response to the callback service.

Cause: Internal system error.

Action: Analyze the details of the exception
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50182: Details of keystore:

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-50183: Could not get the transaction manager using "{0}". Exception: "{1}"

Cause: Method of getting transaction manager might have changed in this release.

Action: Internal system error.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50184: Could not get the transaction manager using "{0}"Got unexpected class "{1}" instead of javax.transaction.TransactionManager.

Cause: Method of getting transaction manager might have changed in this release.

Action: Internal system error.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50185: [MessageID: {0}] Ignoring the return value of the asynchronous web method as the sendAutoResponse is set to false.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-50186: [MessageID: {0}] Asynchronous response is ignored as the effective replyTo is none

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

OWS-50187: [MessageID: {0}] System Error: Could not get the addressing namespace and so the None URI.

Cause: Addressing namespace is not available.

Action: Internal system error.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-50188: [MessageID: {0}] An asynchronous request message is received and successfully recorded for service "{1}" with a replyTo address as "{2}"

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

OWS-50189: [MessageID: {0}] Completed asynchronous request processing. A response will be sent to the client.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

OWS-50190: [MessageID: {0}] Completed asynchronous request processing but the commit failed. A response will be sent to the client.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

OWS-51001: No TypeGeneratorFactory implementation found for factory {0}.

Cause: You may have specified a wrong factory name, or your Web Service libraries are not properly configured.

Action: Please ensure that you have specified a valid factory name.
Level: 1

Type: ERROR

Impact: Configuration

OWS-51500: Unable to open or locate the following file or directory: {0}.

Cause: A file or directory was not found or acessible.

Action: Ensure that the file or directory name is properly specified and accessible.
Level: 1

Type: ERROR

Impact: Files

OWS-51501: No schema mapping found for class {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

OWS-60001: Could not load schema resource at URL "{0}". Will try classpath search next.

Cause:

Action:
Level: 16

Type: TRACE

Impact: Network

OWS-60002: Could not resolve schema resource for namespace "{0}" at location "{1}"

Cause: Could not resolve the schema from given schemaLocation. This may be caused by network problem or malformed or incorrect schemaLocation URL/URI

Action: See error message.
Level: 1

Type: WARNING

Impact: Files

OWS-60003: Serializer initialization failed. Unable to define SDO data types.

Cause: Failed to define SDO data types from the given schema/schemas.

Action: Ensure that the schema/schemas provided through schemaLocation is/are valid and none of the schemas are conflicting with each other.
Level: 1

Type: ERROR

Impact: Other

OWS-65001: Invalid Incoming Addressing Headers: "{0}"

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

OWS-65002: Message discarded because of endpoint address is addressing none

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-65003: Error occured parsing given soap message.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

OWS-65004: Invalid URI "{0}" in Addressing element {1}.

Cause: Invalid URI found while reading the Addressing headers.

Action: Verify that the URI used for addressing is valid.
Level: 1

Type: ERROR

Impact: Requests/Responses

OWS-65005: AttributedURI type does not support Extensibility elements.

Cause: AttributedURI type has Extensibility elements.

Action: Do not specify Extensibility element with AttibureURI type.
Level: 1

Type: ERROR

Impact: Requests/Responses

78 PKI-01001 to PKI-07007

PKI-01001: Missing arguments in the command: {0}

Cause: An incomplete command was issued. For example, the wallet password or wallet location is missing.

Action: Check the usage of the command-line tool and provide all required arguments.
Level: 1

Type: ERROR

Impact: Other

PKI-01002: Invalid password.

Cause: Passwords must have a minimum length of eight characters and contain alphabetic characters combined with numbers or special characters.

Action: Make sure the password policy is followed and try again.
Level: 1

Type: ERROR

Impact: Other

PKI-01003: Passwords did not match.

Cause: When creating a wallet, the password entered the second time did not match the password entered the first time.

Action: Enter the same password both times.
Level: 1

Type: ERROR

Impact: Other

PKI-02001: A wallet already exists at: {0}

Cause: Attempted to create a new wallet at a location where a wallet already existed.

Action: Remove the existing wallet, or create the new wallet at another location.
Level: 1

Type: ERROR

Impact: Other

PKI-02002: Unable to open the wallet. Check password.

Cause: Wallet password may be wrong.

Action: Try again with the correct password.
Level: 1

Type: ERROR

Impact: Other

PKI-02003: Unable to load the wallet at: {0}

Cause: Possible causes include a wrong password, parsing errors, or the wallet file was not found.

Action: Check that the wallet is present at the specified location and the password is correct.
Level: 1

Type: ERROR

Impact: Other

PKI-02004: Unable to verify the wallet.

Cause: The wallet may be corrupted.

Action: Make sure you have the right wallet. Try opening the wallet in enterprise manager or by orapki to make sure it is appropriate.
Level: 1

Type: ERROR

Impact: Other

PKI-02005: Unable to delete the wallet at: {0}

Cause: Possible causes include insufficient permission or the wallet being used by another person.

Action: Obtain the necessary permission and check that the wallet is not being used.
Level: 1

Type: ERROR

Impact: Other

PKI-02006: The specified directory does not exist: {0}

Cause: Wallet creation failed because the specified directory did not exist.

Action: Create the directory prior to the wallet creation.
Level: 1

Type: ERROR

Impact: Other

PKI-02007: The specified location is not a directory: {0}

Cause: Wallet creation failed because the specified location was not a directory.

Action: Create the wallet in an existing directory instead.
Level: 1

Type: ERROR

Impact: Other

PKI-02008: Unable to modify a read-only Auto-login wallet.

Cause: Attempted to update a read-only Auto-login wallet.

Action: Specify the associated Password-protected (.p12 file) wallet.
Level: 1

Type: ERROR

Impact: Other

PKI-02009: Unable to create directory.

Cause: OS error in creating directory.

Action: Check file permissions and disk space.
Level: 1

Type: ERROR

Impact: Other

PKI-02010: Invalid MAC for Wallet. Wallet verification failed.

Cause: The wallet is possibly corrupted.

Action: Restore the wallet from a backup or recreate it.
Level: 1

Type: ERROR

Impact: Other

PKI-02011: Unable to set file permissions for wallet at {0}

Cause: Wallet permissions could not be set.

Action: Try to save the wallet in a different directory.
Level: 1

Type: ERROR

Impact: Other

PKI-03001: The entry already exists: {0}

Cause: Attempted to create a new entry with a previously used alias.

Action: Try again with another alias or delete the existing entry.
Level: 1

Type: ERROR

Impact: Other

PKI-03002: No entry found for the alias: {0}

Cause: The specified alias was not found in the secret store.

Action: Check the alias name and try again.
Level: 1

Type: ERROR

Impact: Other

PKI-03003: Secrets did not match.

Cause: The secret (password) entered the second time did not match the one entered the first time.

Action: Enter the same secret both times.
Level: 1

Type: ERROR

Impact: Other

PKI-03004: Unable to load the secret store.

Cause: Possible causes include a wrong password, the secret store file was not found or was corrupted.

Action: Check that the secret store file is present at the specified location and the password is correct.
Level: 1

Type: ERROR

Impact: Other

PKI-03005: Unable to load the Java keystore.

Cause: Possible causes include a wrong password, the Java keystore file was not found or was corrupted

Action: Check that the Java keystore file is present at the specified location and the password is correct.
Level: 1

Type: ERROR

Impact: Other

PKI-04001: Invalid Certificate.

Cause: The given certificate did not follow the X509/DER, X509/BASE64, PKCS7/DER, or PKCS7/BASE64 format.

Action: Use a valid certificate format.
Level: 1

Type: ERROR

Impact: Other

PKI-04002: No valid key or certificate in the wallet.

Cause: Attempted to use a wallet for authentication/signatures/SSL, but no key or certificate was found in the wallet.

Action: Import certificates into the wallet/keystore or use a self-signed wallet/keystore.
Level: 1

Type: ERROR

Impact: Other

PKI-04003: The trusted certificate is already present in the wallet.

Cause: Attempted to import a trusted certificate that already existed in the wallet.

Action: No action required. The trusted certificate is already present in the wallet.
Level: 1

Type: ERROR

Impact: Other

PKI-04004: The user certificate is already installed in the wallet.

Cause: Attempted to install a user certificate that already existed in the wallet.

Action: No action required. The user certificate is already installed in the wallet.
Level: 1

Type: ERROR

Impact: Other

PKI-04005: No matching certificate request in the wallet.

Cause: Attempted to install a user certificate, but no matching certificate request was found in the wallet.

Action: Make sure that the user certificate is being installed into the wallet where the certificate request was created.
Level: 1

Type: ERROR

Impact: Other

PKI-04006: No matching private key in the wallet.

Cause: Attempted to install a user certificate, but no matching private key was found in the wallet.

Action: Make sure that the user certificate is being installed to the wallet where the certificate request was created.
Level: 1

Type: ERROR

Impact: Other

PKI-04007: No matching certificate in the wallet for the DN: {0}

Cause: Attempted to access a user certificate, but no matching certificate of the DN was found.

Action: Make sure that a user certificate with the given DN exists in the wallet.
Level: 1

Type: ERROR

Impact: Other

PKI-04008: The alias is already taken in the wallet: {0}

Cause: Attempted to create a key or import a certificate with an alias, but the alias already existed in the wallet.

Action: Try again with another alias.
Level: 1

Type: ERROR

Impact: Other

PKI-04009: No matching private key or certificate request found for the alias: {0}

Cause: Attempted to install a user certificate into a wallet with an alias, but no matching private key / certificate request was found for this alias.

Action: Make sure that the user certificate is being installed with the same alias as the private key / certificate request.
Level: 1

Type: ERROR

Impact: Other

PKI-04010: No matching certificate found for the alias: {0}

Cause: Attempted to access a user certificate that is associated with an alias, but no matching certificate was found for this alias.

Action: Make sure that a user certificate exists in the wallet with the given alias.
Level: 1

Type: ERROR

Impact: Other

PKI-04011: Cannot remove the certificate request if its associated user certificate is still present in the wallet.

Cause: Attempted to remove a certificate request, but its associated user certificate was still present in the wallet.

Action: Remove the associated user certificate first.
Level: 1

Type: ERROR

Impact: Other

PKI-04012: Incomplete certificate chain

Cause: Attempted to install a user certificate whose trusted certificate was not present in the wallet.

Action: Ensure that the CA certificate/Certificate Chain that issued the user certificate is present as trusted certificate in the wallet.
Level: 1

Type: ERROR

Impact: Other

PKI-04013: Entry with matching alias not trusted cert.

Cause: Failed to add a trusted certificate into the wallet because the entry with that alias in the keystore was not a trusted cert.

Action: Specify a different alias.
Level: 1

Type: ERROR

Impact: Other

PKI-04014: No entry with matching alias is present in wallet/keystore.

Cause: Failed to delete an entry in wallet/keystore because no entry with that alias was present.

Action: Specify the correct alias.
Level: 1

Type: ERROR

Impact: Other

PKI-04015: Trusted cert cannot be removed.

Cause: The trusted cert is being used in a certificate chain.

Action: The user cert that has the trusted cert in its certificate chain should be removed first.
Level: 1

Type: ERROR

Impact: Other

PKI-04016: No user certificate found in the wallet.

Cause: No user certificate that can be used with SSL was found.

Action: Install a user certificate into the wallet.
Level: 1

Type: ERROR

Impact: Other

PKI-04017: Entry identified by alias not a key entry.

Cause: No entry in wallet/keystore had matching alias.

Action: Use a correct alias.
Level: 1

Type: ERROR

Impact: Other

PKI-04018: User cert does not match pvt key for input alias.

Cause: The private key with matching alias did not match the user certificate.

Action: Use a correct alias.
Level: 1

Type: ERROR

Impact: Other

PKI-05001: Unable to read CRL at: {0}

Cause: CRL was not present at the specified location or CRL was corrupted.

Action: Check the CRL file at the given location.
Level: 1

Type: ERROR

Impact: Other

PKI-05002: Unable to write CRL

Cause: Insufficient file permission or insufficient disk space.

Action: Ensure that a file can be created at the specified location.
Level: 1

Type: ERROR

Impact: Other

PKI-05003: Untrusted or expired CRL

Cause: The CRL at the user-given location expired or was not signed by a trusted authority.

Action: Get a valid or recent CRL from the CA.
Level: 1

Type: ERROR

Impact: Other

PKI-05004: No CRL found for the issuer: {0}

Cause: No CRL issued by the CA was found at the specified CRL location.

Action: Import the specified CA's CRL into the specified location.
Level: 1

Type: ERROR

Impact: Other

PKI-05005: CRL symlink failed with the error: {0}

Cause: Failed to set up a symlink for the CRL file.

Action: Make sure that the target CRL file exists and try again.
Level: 1

Type: ERROR

Impact: Other

PKI-05006: Unable to find signer for CRL.

Cause: No CA certificate in wallet for the CRL issuer was found.

Action: Add CA certificates from CRL issuer to wallet.
Level: 1

Type: ERROR

Impact: Other

PKI-07001: Unable to login to the LDAP server.

Cause: The username or password may be invalid.

Action: Try again with the correct credentials.
Level: 1

Type: ERROR

Impact: Other

PKI-07002: Unable to find the LDAP subtree: {0}

Cause: Attempted to search for CRLs from an LDAP server, but the subtree was not found.

Action: Confirm that the CRL file is present at the specified location.
Level: 1

Type: ERROR

Impact: Other

PKI-07003: Insufficient privilege to perform the operation in the LDAP server: {0}

Cause: Attempted to perform some operation in the LDAP server for which the user did not have permission.

Action: Obtain the necessary authorization or have an authorized user perform the operation.
Level: 1

Type: ERROR

Impact: Other

PKI-07004: Peer sent no certificates.

Cause: The peer sent no certificates (which was needed during handshake).

Action: Check peer configuration.
Level: 1

Type: ERROR

Impact: Other

PKI-07005: Untrusted Cert Chain.

Cause: No trusted certificate in wallet/keystore for peer certificate was found.

Action: Peer should use a different certificate or import the peer's CA certificate into your wallet.
Level: 1

Type: ERROR

Impact: Other

PKI-07006: Invalid certificate signature.

Cause: Certificate signature check failed.

Action: Use a different user certificate/certificate chain on peer.
Level: 1

Type: ERROR

Impact: Other

PKI-07007: Certificate is revoked.

Cause: The peer's certificate has been revoked.

Action: Use a different user certificate/certificate chain on peer.
Level: 1

Type: ERROR

Impact: Other

79 PROV-40000 to PROV-40000

PROV-40000: Unexpected error happened while provisioing AS topology

Cause: Internal Exception.

Action: See AS provisioing logs for more details.
Level: 1

Type: ERROR

Impact: Topology

80 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-00024: successfully flushed pending changes for session [{0}]

Cause:

Action:
Level: 1

Type: TRACE

Impact: Logging

RCS-00025: successfully canceled pending changed for session [{0}]

Cause:

Action:
Level: 1

Type: TRACE

Impact: Logging

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-01018: successfully registered resource type [{0}]

Cause:

Action:
Level: 1

Type: TRACE

Impact: Logging

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-02002: registered resource catalog adapter factory [{2}] for connection type [{1}]

Cause:

Action:
Level: 1

Type: TRACE

Impact: Logging

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-02007: found resource catalog adapter factory [{1}] for connection type [{0}]

Cause:

Action:
Level: 32

Type: TRACE

Impact: Logging

RCS-02008: created InitialContext for repository [{0}], repository Path [{1}] using InitialContextFactory [{2}]

Cause:

Action:
Level: 32

Type: TRACE

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-03004: renamed resource catalog from [{0}] to [{1}]

Cause:

Action:
Level: 1

Type: NOTIFICATION

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-03006: deleted resource catalog [{0}]

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Logging

RCS-03007: removed element [{1}] from folder [{2}] in resource catalog [{0}]

Cause:

Action:
Level: 1

Type: TRACE

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-03009: added element [{1}] to folder [{2}] in resource catalog [{0}]

Cause:

Action:
Level: 1

Type: TRACE

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-04005: evaluating attribute predicate [{0}]

Cause:

Action:
Level: 32

Type: TRACE

Impact: Logging

RCS-04006: returning [{1}] for attribute expression [{0}]

Cause:

Action:
Level: 32

Type: TRACE

Impact: Logging

RCS-04007: returning [{3}] for string comparison "[{0}] [{1}] [{2}]"

Cause:

Action:
Level: 32

Type: TRACE

Impact: Logging

RCS-04008: returning [{3}] for numeric comparison "[{0}] [{1}] [{2}]"

Cause:

Action:
Level: 32

Type: TRACE

Impact: Logging

RCS-04009: returning [{3}] for date comparison "[{0}] [{1}] [{2}]"

Cause:

Action:
Level: 32

Type: TRACE

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-05001: successfully processed transfer set [{0}]

Cause:

Action:
Level: 1

Type: NOTIFICATION

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

81 RCU-06000 to RCU-06138

RCU-06000: Could not connect to the database. Some fields are empty.

Cause: Could not connect to the database. Some fields are empty.

Action: Please enter valid values in all required fields
Level: 1

Type: ERROR

Impact: Installation

RCU-06001: Invalid port number: {0}. A valid port number ranges from 0 to 65535.

Cause: Invalid port number: {0}. A valid port number ranges from 0 to 65535.

Action: Please enter a valid port number
Level: 1

Type: ERROR

Impact: Installation

RCU-06002: The specified database does not meet the minimum requirement to load metadata repository.

Cause: The specified database does not meet the minimum requirement to load metadata repository.

Action: Please modify the prerequisite or the database configuration to meet the prerequisite requirements
Level: 1

Type: ERROR

Impact: Installation

RCU-06003: RCU could not find the Schema Version Registry in the database. No metadata repository schema could be dropped.

Cause: RCU could not find the Schema Version Registry in the database. No metadata repository schema could be dropped.

Action: Please contact the system administrator
Level: 1

Type: ERROR

Impact: Installation

RCU-06004: Enter password for the SYS user.

Cause: Enter password for the SYS user.

Action: Please enter the password for the sys user
Level: 1

Type: ERROR

Impact: Installation

RCU-06010: No Existing Prefixes

Cause: No Existing Prefixes

Action: Please create a new prefix
Level: 1

Type: ERROR

Impact: Installation

RCU-06011: A valid prefix should be specified. Prefix can contain only alpha-numeric characters. It should not start with a number and should not contain any special characters.

Cause: A valid prefix should be specified. Prefix can contain only alpha-numeric characters. It should not start with a number and should not contain any special characters.

Action: Please select a prefix from the existing prefixes or enter a new prefix
Level: 1

Type: ERROR

Impact: Installation

RCU-06012: There are no existing prefixes.

Cause: There are no existing prefixes.

Action: Please create a new prefix
Level: 1

Type: ERROR

Impact: Installation

RCU-06013: Specified prefix does not exist. Existing prefixes are: {0}

Cause: Specified prefix does not exist. Existing prefixes are: {0}

Action: Please specify another prefix
Level: 1

Type: ERROR

Impact: Installation

RCU-06014: Specified component does not exist. Existing components for prefix: {0} are: {1}

Cause: Specified component does not exist. Existing components for prefix: {0} are: {1}

Action: Please provide a component that exists
Level: 1

Type: ERROR

Impact: Installation

RCU-06015: No component selected/specified. Please select/specify atleast one component.

Cause: No component selected/specified. Please select/specify atleast one component.

Action: Please select atleast one component
Level: 1

Type: ERROR

Impact: Installation

RCU-06016: The specified prefix already exists.

Cause: The specified prefix already exists.

Action: Please specify another prefix
Level: 1

Type: ERROR

Impact: Installation

RCU-06017: There was no prefix specified and the specified component already exists.

Cause: There was no prefix specified and the specified component already exists.

Action: If the component is non-prefixable, only one instance can exist. If you want to re-create it, you have to drop it first
Level: 1

Type: ERROR

Impact: Installation

RCU-06018: {0} schema owner is empty.

Cause: {0} schema owner is empty.

Action: Please provide values for all schema owners
Level: 1

Type: ERROR

Impact: Installation

RCU-06019: Invalid format for schema owner {0}. Prefixable components should have the schema owner in the following format <prefix>_<Any String> where the prefix is {1}.

Cause: Invalid format for schema owner {0}. Prefixable components should have the schema owner in the following format <prefix>_<Any String> where the prefix is {1}.

Action: Please ensure that the schema owners of all prefixable components begin with the prefix, followed by "_"
Level: 1

Type: ERROR

Impact: Installation

RCU-06020: Schema Owner {0} is duplicated. Schema Owners must be unique.

Cause: Schema Owner {0} is duplicated. Schema Owners must be unique.

Action: Please provide unique schema owners
Level: 1

Type: ERROR

Impact: Installation

RCU-06021: The specified component ({0}) is non-prefixable and it already exists.

Cause: The specified component ({0}) is non-prefixable and it already exists.

Action: Please deselect the non-prefixable component as it already exists
Level: 1

Type: ERROR

Impact: Installation

RCU-06022: No components to resume execution. Please run in normal mode.

Cause: No components to resume execution. Please run in normal mode.

Action: No components to resume execution. Please run in normal mode.
Level: 1

Type: ERROR

Impact: Installation

RCU-06030: The specified tablespace {0} for component {1} does not have enough free space to hold the repository. The required free space is {2} MB, but the available space is {3} MB.

Cause: The specified tablespace {0} for component {1} does not have enough free space to hold the repository. The required free space is {2} MB, but the available space is {3} MB.

Action: Please modify the properties of the tablespace or change the prerequisite value
Level: 1

Type: ERROR

Impact: Installation

RCU-06040: Could not connect to the specified Middleware Administration Server. Some fields are empty.

Cause: Could not connect to the specified Middleware Administration Server. Some fields are empty.

Action: Please provide valid values for all required fields
Level: 1

Type: ERROR

Impact: Installation

RCU-06041: Could not connect to the specified Middleware Administration Server.

Cause: Could not connect to the specified Middleware Administration Server.

Action: Please verify that the connection details provided are correct and try again
Level: 1

Type: ERROR

Impact: Installation

RCU-06042: MAS registry for {0} schema already exists with the same name. Specify a different registry name.

Cause: MAS registry for {0} schema already exists with the same name. Specify a different registry name.

Action: Component is already registered. Please de-select this component for the purpose of registration
Level: 1

Type: ERROR

Impact: Installation

RCU-06043: Can not deregister, there is no MAS registry with this name.

Cause: Can not deregister, there is no MAS registry with this name.

Action: Component is not registered. Please de-select this component for the purpose of de-registration
Level: 1

Type: ERROR

Impact: Installation

RCU-06051: RCUCommandLine Error - Invalid Option passed:

Cause: RCUCommandLine Error - Invalid Option passed:

Action: Please provide valid command-line options
Level: 1

Type: ERROR

Impact: Installation

RCU-06052: RCUCommandLine Error - Invalid format/order of optionValue:

Cause: RCUCommandLine Error - Invalid format/order of optionValue:

Action: Please ensure that the format/order of the options and values in the command-line are correct
Level: 1

Type: ERROR

Impact: Installation

RCU-06053: RCUCommandLine Error - More than one mutually exclusive options passed:

Cause: RCUCommandLine Error - More than one mutually exclusive options passed:

Action: Please provide valid command-line options
Level: 1

Type: ERROR

Impact: Installation

RCU-06054: RCUCommandLine Error - Database type should be provided.

Cause: RCUCommandLine Error - Database type should be provided.

Action: Please provide the database type
Level: 1

Type: ERROR

Impact: Installation

RCU-06055: RCUCommandLine Error - Database connect string should be provided.

Cause: RCUCommandLine Error - Database connect string should be provided.

Action: Please provide the database connect string
Level: 1

Type: ERROR

Impact: Installation

RCU-06056: RCUCommandLine Error - Database hostname should be provided.

Cause: RCUCommandLine Error - Database hostname should be provided.

Action: Please provide the database hostname
Level: 1

Type: ERROR

Impact: Installation

RCU-06057: RCUCommandLine Error - Database port number should be provided.

Cause: RCUCommandLine Error - Database port number should be provided.

Action: Please provide the database port number
Level: 1

Type: ERROR

Impact: Installation

RCU-06058: RCUCommandLine Error - Database service name should be provided.

Cause: RCUCommandLine Error - Database service name should be provided.

Action: Please provide the database service name
Level: 1

Type: ERROR

Impact: Installation

RCU-06059: RCUCommandLine Error - Database user should be provided.

Cause: RCUCommandLine Error - Database user should be provided.

Action: Please provide the database user
Level: 1

Type: ERROR

Impact: Installation

RCU-06060: RCUCommandLine Error - Database password should be provided.

Cause: RCUCommandLine Error - Database password should be provided.

Action: Please provide the database password
Level: 1

Type: ERROR

Impact: Installation

RCU-06061: RCUCommandLine Error - Database role should be provided.

Cause: RCUCommandLine Error - Database role should be provided.

Action: Please provide the database role
Level: 1

Type: ERROR

Impact: Installation

RCU-06062: RCUCommandLine Error - Schema Prefix should be provided.

Cause: RCUCommandLine Error - Schema Prefix should be provided.

Action: Please provide the schema prefix
Level: 1

Type: ERROR

Impact: Installation

RCU-06063: RCUCommandLine Error - Tablespace name should be provided. Pass - DEFAULT_VALUE if you want the default to be used.

Cause: RCUCommandLine Error - Tablespace name should be provided. Pass - DEFAULT_VALUE if you want the default to be used.

Action: Please provide the tablespace name
Level: 1

Type: ERROR

Impact: Installation

RCU-06064: RCUCommandLine Error - Schema owner name should be provided. Pass - DEFAULT_VALUE if you want the default to be used.

Cause: RCUCommandLine Error - Schema owner name should be provided. Pass - DEFAULT_VALUE if you want the default to be used.

Action: Please provide the schema owner
Level: 1

Type: ERROR

Impact: Installation

RCU-06065: RCUCommandLine Error - Invalid Component Name:

Cause: RCUCommandLine Error - Invalid Component Name:

Action: Please provide a valid component name
Level: 1

Type: ERROR

Impact: Installation

RCU-06066: RCUCommandLine Error - Checkpoint object not found or is not readable. Cannot proceed in resume mode.

Cause: RCUCommandLine Error - Checkpoint object not found or is not readable. Cannot proceed in resume mode.

Action: RCUCommandLine Error - Checkpoint object not found or is not readable. Cannot proceed in resume mode.
Level: 1

Type: ERROR

Impact: Installation

RCU-06067: RCUCommandLine Error - No pending components found in checkpoint. Cannot proceed in resume mode.

Cause: RCUCommandLine Error - No pending components found in checkpoint. Cannot proceed in resume mode.

Action: RCUCommandLine Error - No pending components found in checkpoint. Cannot proceed in resume mode.
Level: 1

Type: ERROR

Impact: Installation

RCU-06068: Failed to write checkpoint object.

Cause: Failed to write checkpoint object.

Action: Failed to write checkpoint object.
Level: 1

Type: ERROR

Impact: Installation

RCU-06069: RCUCommandLine Error - MAS password should be provided.

Cause: RCUCommandLine Error - MAS password should be provided.

Action: RCUCommandLine Error - MAS password should be provided.
Level: 1

Type: ERROR

Impact: Installation

RCU-06080: Global prerequisite check failed - Check requirement for specified database

Cause: Global prerequisite check failed - Check requirement for specified database

Action: Please modify the global prerequisite or the database configuration to meet the global prerequisite requirements
Level: 1

Type: ERROR

Impact: Installation

RCU-06081: Failed - Obtain properties of the specified database

Cause: Failed - Obtain properties of the specified database

Action: Please make sure that the database is in a proper state
Level: 1

Type: ERROR

Impact: Installation

RCU-06082: Tablespace prerequisite check failed - Check tablespace requirement for each selected component

Cause: Tablespace prerequisite check failed - Check tablespace requirement for each selected component

Action: Please modify the properties of the tablespace or change the prerequisite value
Level: 1

Type: ERROR

Impact: Installation

RCU-06083: Failed - Check prerequisites requirement for selected component:

Cause: Failed - Check prerequisites requirement for selected component:

Action: Please make sure that the prerequisite requirements are met
Level: 1

Type: ERROR

Impact: Installation

RCU-06084: Invalid format for Java prerequisite: {0}

Cause: Invalid format for Java prerequisite: {0}

Action: Please make sure that the java prerequisite is in a valid format
Level: 1

Type: ERROR

Impact: Installation

RCU-06085: Error while executing Java prerequisite: {0}

Cause: Error while executing Java prerequisite: {0}

Action: Please make sure that the java prerequisite is in a valid format and all required classes and jar files are present
Level: 1

Type: ERROR

Impact: Installation

RCU-06090: Skipping Main operation: Failed in Connection step validation

Cause: Skipping Main operation: Failed in Connection step validation

Action: Please provide correct database details and try again
Level: 1

Type: ERROR

Impact: Installation

RCU-06091: Component name/schema prefix validation failed.

Cause: Component name/schema prefix validation failed.

Action: Please provide valid component name and prefix and try again
Level: 1

Type: ERROR

Impact: Installation

RCU-06092: Component Selection validation failed. Please refer to log at {0} for details.

Cause: Component Selection validation failed. Please refer to log at {0} for details.

Action: Please select one or more components to continue
Level: 1

Type: ERROR

Impact: Installation

RCU-06093: Skipping Main operation: Failed in SchemaTablespace step validation

Cause: Skipping Main operation: Failed in SchemaTablespace step validation

Action: Please check the properties of the database and the tablespaces specified
Level: 1

Type: ERROR

Impact: Installation

RCU-06094: Skipping Main operation: Failed in MAS Registration step validation

Cause: Skipping Main operation: Failed in MAS Registration step validation

Action: Please make sure that MAS is up and is in a proper state and try again or contact the system administrator
Level: 1

Type: ERROR

Impact: Installation

RCU-06100: Encountered an Exception while trying to execute Prerequisite: {0}

Cause: Encountered an Exception while trying to execute Prerequisite: {0}

Action: Please refer to the logs for details
Level: 1

Type: ERROR

Impact: Installation

RCU-06101: Prerequisite Failure for: {0} Required Value = {1}, Current Value = {2}, Comparison Operator: "{3}"

Cause: Prerequisite Failure for: {0} Required Value = {1}, Current Value = {2}, Comparison Operator: "{3}"

Action: Please modify the prerequisite or the database configuration to meet the prerequisite requirements
Level: 1

Type: ERROR

Impact: Installation

RCU-06102: Prerequisite Failure. The Prerequisite: {0} returned an empty result.

Cause: Prerequisite Failure. The Prerequisite: {0} returned an empty result.

Action: Please modify the database configuration to meet the prerequisite requirements
Level: 1

Type: ERROR

Impact: Installation

RCU-06103: DB Option Prerequisite failure for: {0} Required Value = {1}, Current Value = {2}

Cause: DB Option Prerequisite failure for: {0} Required Value = {1}, Current Value = {2}

Action: Please make sure that the DBOption has the required value
Level: 1

Type: ERROR

Impact: Installation

RCU-06104: DB Object Prerequisite failure for: {0} This object does not exist or its status is not VALID}

Cause: DB Object Prerequisite failure for: {0} This object does not exist or its status is not VALID}

Action: Please make sure that the DBObject exists and is valid
Level: 1

Type: ERROR

Impact: Installation

RCU-06105: DB Component Prerequisite failure for: {0} This component does not exist or its status is not VALID.

Cause: DB Component Prerequisite failure for: {0} This component does not exist or its status is not VALID.

Action: Please make sure that the DBComponent exists and is valid
Level: 1

Type: ERROR

Impact: Installation

RCU-06106: DB Version Prerequisite failure. Required Version = {0}, Current Version = {1}, Comparison Operator: "{3}"

Cause: DB Version Prerequisite failure. Required Version = {0}, Current Version = {1}, Comparison Operator: "{3}"

Action: Please make sure that the DBVersion has the required value
Level: 1

Type: ERROR

Impact: Installation

RCU-06107: DB Init Param Prerequisite failure for: {0} Required Value = {1}, Current Value = {2}, Comparison Operator: "{3}"

Cause: DB Init Param Prerequisite failure for: {0} Required Value = {1}, Current Value = {2}, Comparison Operator: "{3}"

Action: Please make sure that the DB Init parameter has the required value
Level: 1

Type: ERROR

Impact: Installation

RCU-06108: DB TablespaceFreeMB Prerequisite failure for: {0} Required space = {1}, Current space = {2}, Comparison Operator: "{3}"

Cause: DB TablespaceFreeMB Prerequisite failure for: {0} Required space = {1}, Current space = {2}, Comparison Operator: "{3}"

Action: Please modify the properties of the tablespace or change the prerequisite value
Level: 1

Type: ERROR

Impact: Installation

RCU-06120: Component dependencies not met for components with following ids: {0}.

Cause: Component dependencies not met for components with following ids: {0}.

Action: Please select the dependent components
Level: 1

Type: ERROR

Impact: Installation

RCU-06121: Component dependencies check failed. Please select the dependent components and try again.

Cause: Component dependencies check failed. Please select the dependent components and try again.

Action: Please select the dependent components
Level: 1

Type: ERROR

Impact: Installation

RCU-06130: Action failed - {0}

Cause: Action failed - {0}

Action: Please check the actions for the component or contact the system administrator
Level: 1

Type: ERROR

Impact: Installation

RCU-06131: Error while trying to connect to database.

Cause: Error while trying to connect to database.

Action: Please provide correct database details and try again or contact the system administrator
Level: 1

Type: ERROR

Impact: Installation

RCU-06132: Database type not supported - {0}

Cause: Database type not supported - {0}

Action: Please use a database type that is supported
Level: 1

Type: ERROR

Impact: Installation

RCU-06133: Error while trying to execute HostCommand action.

Cause: Error while trying to execute HostCommand action.

Action: Please check the host command action for the component or contact the system administrator
Level: 1

Type: ERROR

Impact: Installation

RCU-06134: Error while trying to execute JDBC action.

Cause: Error while trying to execute JDBC action.

Action: Please check the jdbc action for the component or contact the system administrator
Level: 1

Type: ERROR

Impact: Installation

RCU-06135: Error while trying to execute Java action.

Cause: Error while trying to execute Java action.

Action: Please check the java action for the component or contact the system administrator
Level: 1

Type: ERROR

Impact: Installation

RCU-06136: Error while trying to execute SQLPlus action.

Cause: Error while trying to execute SQLPlus action.

Action: Please check the sqlplus action for the component or contact the system administrator
Level: 1

Type: ERROR

Impact: Installation

RCU-06137: Error while trying to register with MAS.

Cause: Error while trying to register with MAS.

Action: Please make sure that MAS is up and is in a proper state and try again or contact the system administrator
Level: 1

Type: ERROR

Impact: Installation

RCU-06138: User halted the operation.

Cause: User halted the operation.

Action: Please click continue or restart the operation
Level: 1

Type: ERROR

Impact: Installation

82 REP-00001 to REP-80012

REP-00001: The Oracle Reports Builder message file cannot be found.

Cause: The file of error messages could not be opened or an internal error occurred while opening it.

Action: Reinstall Oracle Reports Builder or contact Oracle Support Services for assistance.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00002: The string from the message file cannot be retrieved.

Cause: Oracle Reports Builder could not retrieve the necessary error message or string.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00003: Global preference file cannot be opened.

Cause: The global preference file could not be opened. This is just a warning, so the product will continue to run even if this occurs. The possible causes of this error include the following: Case 1: The file was not found under the specified name in the specified location. Case 2: Lack of necessary privileges to open the file. Case 3: A system error made it impossible to open the file.

Action: Take the following actions to correct this error: If Case 1: Verify that the file named prefs.ora is stored in the appropriate directory. For more information, contact the database administrator. If Case 2: Verify privileges necessary to access the file, and change privileges accordingly. If Case 3: Consult the operating system documentation or the system administrator.
Level: 1

Type: ERROR

Impact: Other

REP-00004: User preference file cannot be opened.

Cause: The local (customized) preference file could not be opened. This is just a warning, so the product will continue to run even if this occurs. The possible causes of this error include the following: Case 1: The file was not found under the specified name in the specified location. Case 2: Lack of necessary privileges to open the file. Case 3: A system error made it impossible to open the file.

Action: Take the following actions to correct this error: If Case 1: Verify the file prefs.ora is located in the home directory, and change the directory and/or file name as appropriate. If Case 2: Verify privileges necessary to access the file, and change privileges accordingly. If Case 3: Consult the operating system documentation or contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

REP-00005: A syntax error exists at line {0} in global preference file.

Cause: One or more of the preferences in the global preference file was specified incorrectly on the line number shown in the message. The most likely cause of this error is that the file has been edited and one or more preferences incorrectly specified. As a result, the Oracle Reports Builder will ignore the incorrectly specified preferences.

Action: Edit the global preference file and ensure that all preferences are correctly specified, and make the necessary updates.
Level: 1

Type: ERROR

Impact: Other

REP-00006: A syntax error exists at line {0} in user preference file.

Cause: One or more of the preferences in the user preference file was specified incorrectly on the line number shown in the message. The most likely cause of this error is that the file has been edited and one or more preferences incorrectly specified. As a result, the Oracle Reports Builder will ignore the incorrectly specified preferences.

Action: Edit the global preference file and ensure that all preferences are correctly specified. If they are not, make the necessary updates.
Level: 1

Type: ERROR

Impact: Other

REP-00007: The user preference file cannot be written to.

Cause: An attempt was made to save preferences and the user preference file could not be written. The possible causes of this error include the following: Case 1: Lack of necessary privileges to write the file. Case 2: A system error made it impossible to write the file.

Action: Take the following actions to correct this error: If Case 1: Verify privileges necessary to write the file, and change the privileges accordingly. If Case 2: Consult the operating system documentation or contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

REP-00008: An unexpected memory error occurred while initializing preferences.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Memory

REP-00058: Data passing to a remote Reports Server is not supported.

Cause: A record group was passed to a report to be run remotely.

Action: Do not specify a Reports Server when passing a record group.
Level: 1

Type: ERROR

Impact: Data

REP-00059: Resources for subcomponent {0} cannot be located.

Cause: One of the subcomponents of the Oracle Reports Builder could not locate its resource file. Possible causes of this error include: Case 1: The resource file does not exist. Case 2: The resource file is in the wrong place. Case 3: The environment is not configured properly.

Action: Take the following actions to correct this error: If Case 1: Verify that the resource files are present. If Case 2: Verify that the resource files are in the proper directory. If Case 3: Verify that the environment is set correctly. On UNIX, verify that the proper environment variable is set; on Windows, check oracle.ini.
Level: 1

Type: ERROR

Impact: Other

REP-00060: A synchronous job cannot be run concurrently with another report.

Cause: An attempt was made to run a report initiated by Forms Runtime and requiring data passed from that tool, but one or more other reports are running or queued to run. Reports requiring passed data must be run immediately.

Action: Wait for all other reports currently listed in the Reports Server queue to run, then rerun report.
Level: 1

Type: ERROR

Impact: Other

REP-00061: An internal error occurred - rxmobfree: reference count is zero.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00062: An internal error occurred - rxmobnew: size mismatch.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00063: An internal error occurred - rxmobnew: memory manager mismatch.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Memory

REP-00064: An internal error occurred - rxmobnew: type mismatch.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00065: A virtual memory system error occurred.

Cause: Oracle Reports Builder has encountered a memory error.

Action: Make note of the error-specific code and contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Memory

REP-00066: An error occurred executing the CA utility.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00067: The value for keyword STYPE is invalid.

Cause: In Reports Converter, an invalid value was provided for the STYPE keyword.

Action: Check the syntax of the keyword. Valid values are DATABASE, REXFILE, RDFFILE, PLLDB, PLLFILE, or PLDFILE. For more information, see the Command Line Keywords appendix in the Publishing Reports to the Web manual.
Level: 1

Type: ERROR

Impact: Other

REP-00068: The value for DTYPE is invalid.

Cause: In Reports Converter, an invalid value was provided for the DTYPE keyword.

Action: Check the syntax of the keyword. Valid value are DATABASE, REXFILE, RDFFILE, REPFILE, TDFFILE, PLLDB, PLLFILE, PLXFILE, or PLDFILE. For more information, see the Command Line Keywords appendix in the Publishing Reports to the Web manual.
Level: 1

Type: ERROR

Impact: Other

REP-00069: An internal error occurred

Cause: An Oracle Reports Builder internal code error occurred.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00071: The SSL context cannot be allocated.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00072: The NNIT interface cannot be initialized.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00073: An unknown product cannot be run.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00074: An attempt to run another product using SSL failed.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00075: An error occurred when running the called Oracle component,

Cause: Oracle Reports Builder encountered an error after calling Forms Runtime or Graphics Runtime. The accompanying error message displays the error encountered by the called application.

Action: Resolve the error encountered by the called application and retry the operation.
Level: 1

Type: ERROR

Impact: Other

REP-00076: An internal failure occurred in product integration.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00077: The column in query {0} too long for data passing.

Cause: An attempt was made to pass data to a column of excessive size (likely a LONG column).

Action: Remove the column from the report definition and the calling document's definition.
Level: 1

Type: ERROR

Impact: Data

REP-00078: A single process integration was invoked with BATCH=NO.

Cause: An attempt was made to invoke Oracle Reports Builder specifying BATCH=NO with executable in which Oracle Reports Builder is linked with another product.

Action: Use an executable which integrates using multiple processes, or specify BATCH=YES.
Level: 1

Type: ERROR

Impact: Process

REP-00079: Value for keyword OVERWRITE is invalid.

Cause: In Reports Converter, an invalid value was specified for the OVERWRITE keyword.

Action: Reenter the command, specifying a value of YES, NO, or PROMPT for the OVERWRITE keyword.
Level: 1

Type: ERROR

Impact: Other

REP-00080: The specified value is invalid.

Cause: In Reports Converter, OVERWRITE=PROMPT was specified on the command line, then a value other than YES or NO was entered when prompted.

Action: Specify a value of YES or NO at the prompt, or CANCEL the operation.
Level: 1

Type: ERROR

Impact: Other

REP-00081: An error occurred during the file I/O operation.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00082: An error occurred executing the SCA utility.

Cause: The possible causes of this error include the following: Case 1: The initialization file is not current. Case 2: An abnormal condition.

Action: Take the following actions to correct this error: If Case 1: Ensure that the directory where the report is located is defined in the REPORTS_PATH located in $ORACLE_HOME/bin/reports.sh. If Case 2: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00083: The value for keyword DUNIT is invalid.

Cause: In Reports Converter, an invalid value was specified for the DUNIT keyword.

Action: Check the syntax of the keyword. Valid values are CENTIMETER, CHARACTER, INCH, or POINT. For more information, see the Command Line Keywords appendix in the Publishing Reports to the Web manual.
Level: 1

Type: ERROR

Impact: Other

REP-00084: The value for keyword PAGESIZE is invalid.

Cause: In Reports Converter, an invalid value was specified for the PAGESIZE keyword.

Action: Check the syntax and value of the keyword. Valid syntax is &lt;width&gt;x&lt;height&gt;. For more information, see the Command Line Keywords appendix in the Publishing Reports to the Web manual.
Level: 1

Type: ERROR

Impact: Other

REP-00085: The value for keyword FORMSIZE is invalid.

Cause: In Reports Converter, an invalid value was specified for the FORMSIZE keyword.

Action: Check the syntax and value of the keyword. Valid syntax is &lt;width&gt;x&lt;height&gt;. For more information, see the Command Line Keywords appendix in the Publishing Reports to the Web manual.
Level: 1

Type: ERROR

Impact: Other

REP-00086: DUNIT must be different than source report's unit of measurement.

Cause: In Reports Converter, an invalid value was specified for the DUNIT keyword that was in the same unit of measurement as the report to be converted.

Action: Check the syntax and value of the keyword. For more information, see the Command Line Keywords appendix in the Publishing Reports to the Web manual.
Level: 1

Type: ERROR

Impact: Other

REP-00087: The value for keyword DESTYPE is invalid.

Cause: In Reports Runtime, an invalid value was specified for the DESTYPE keyword.

Action: Check the syntax and value of the keyword. Valid values are SCREEN, FILE, PRINTER, MAIL, SYSOUT, or PREVIEW. For more information, see the Command Line Keywords appendix in the Publishing Reports to the Web manual.
Level: 1

Type: ERROR

Impact: Other

REP-00088: The value for keyword ONSUCCESS is invalid.

Cause: An invalid value was specified for the ONSUCCESS keyword.

Action: Specify COMMIT, ROLLBACK, or NOACTION either in the Runtime Settings tab of the Tools Options dialog or on the command line. To check the command line syntax, see the Command Line Keywords appendix in the Publishing Reports to the Web manual.
Level: 1

Type: ERROR

Impact: Other

REP-00089: The value for keyword ONFAILURE is invalid.

Cause: An invalid value was specified for the ONFAILURE keyword.

Action: Specify COMMIT, ROLLBACK, or NOACTION either in the Runtime Settings tab of the Tools Options dialog or on the command line. To check the command line syntax, see the Command Line Keywords appendix in the Publishing Reports to the Web manual.
Level: 1

Type: ERROR

Impact: Other

REP-00090: The value for keyword ACCESS is invalid.

Cause: For Oracle Reports Builder, an invalid value was specified for the ACCESS keyword.

Action: Specify FILE or DATABASE. To check the command line syntax, see the Command Line Keywords appendix in the Publishing Reports to the Web manual.
Level: 1

Type: ERROR

Impact: Other

REP-00091: The value for parameter {0} is invalid.

Cause: An invalid value was specified for the named parameter. For example, in the Reports Runtime command string, a character value was provided for a parameter with a data type of Number.

Action: Retry the operation, specifying a valid value for the parameter.
Level: 1

Type: ERROR

Impact: Other

REP-00092: Version 1.1 LANGUAGE argument not supported. Use Oracle National Language environment variable instead

Cause: For Oracle Reports Builder or Runtime, the LANGUAGE keyword was included in the command line string.

Action: Remove the LANGUAGE argument string from the command string, and set the Oracle National Language environment variable NLS_LANG to the appropriate value.
Level: 1

Type: ERROR

Impact: Other

REP-00094: FORMSIZE must be 80x24 if DUNIT is Character.

Cause: While using Reports Converter with DUNIT=Character, a Parameter Form size was specified that was not equal to 80x24.

Action: The character-mode Parameter Form size must be 80x24. Either specify a FORMSIZE of 80x24 when DUNIT=Character, or do not specify a FORMSIZE.
Level: 1

Type: ERROR

Impact: Other

REP-00095: The value for keyword ORIENTATION is invalid.

Cause: An invalid value was specified for the ORIENTATION keyword.

Action: Specify DEFAULT, LANDSCAPE, or PORTRAIT either in the Runtime Settings tab of the Tools Options dialog box or on the command line. To check the command line syntax, see the Command Line Keywords appendix in the Publishing Reports to the Web manual.
Level: 1

Type: ERROR

Impact: Other

REP-00096: The value for keyword MODE is invalid.

Cause: An invalid value was specified for the MODE keyword.

Action: Specify DEFAULT, BITMAP, or CHARACTER either in the Runtime Settings tab of the Tools Options dialog or on the command line. To check the command line syntax, see the Command Line Keywords appendix in the Publishing Reports to the Web manual.
Level: 1

Type: ERROR

Impact: Other

REP-00097: The value for keyword TRACEMODE is invalid.

Cause: Either an invalid or no value was specified for the TRACEMODE keyword, or keywords were specified out of order on the command line without being named.

Action: Either specify Append or Replace for Trace Mode in the Trace Settings dialog or TRACE_APPEND or TRACE_REPLACE on the command line, or check the syntax of the command. To check the command line syntax, see the Command Line Keywords appendix in the Publishing Reports to the Web manual.
Level: 1

Type: ERROR

Impact: Other

REP-00098: The report was not run as it was canceled in the Parameter Form.

Cause: The report was not executed because Cancel instead of Run Report was selected in the Runtime Parameter Form.

Action: No action is necessary.
Level: 1

Type: ERROR

Impact: Other

REP-00099: The report is aborted upon user request.

Cause: The report was stopped while it was executing.

Action: No action is necessary.
Level: 1

Type: ERROR

Impact: Other

REP-00100: The file pointer in file {0} cannot be positioned.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00101: File {0} cannot be read.

Cause: Oracle Reports Builder tried to read a file, which could be opened but not read.

Action: Consult the operating system documentation or contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

REP-00102: File {0} cannot be written to.

Cause: Oracle Reports Builder tried to write the file shown in the message and could not. The possible causes of this error include the following: Case 1: Lack of necessary privileges to write the file. Case 2: The file system does not have enough room for the file. Case 3: A system error made it impossible to open the file.

Action: Take the following actions to correct this error: If Case 1: Verify the privileges necessary to write the file, and change privileges accordingly. If Case 2: Make more room by deleting unnecessary files or expanding storage. If Case 3: Consult the operating system documentation or contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

REP-00103: File {0} cannot be closed.

Cause: Oracle Reports Builder tried to close the file, but was unsuccessful. The most likely reason is that a system error made it impossible to close the file.

Action: Consult the operating system documentation or contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

REP-00104: File {0} cannot be deleted.

Cause: Oracle Reports Builder tried to delete the file shown, but was unsuccessful. The most likely reason is that a system error made it impossible to delete the file.

Action: Consult the operating system documentation or contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

REP-00105: File {0} cannot be locked in exclusive mode.

Cause: Oracle Reports Builder tried to lock the file shown, but was unsuccessful. The most likely reason is that a system error made it impossible to lock the file.

Action: Consult the operating system documentation or contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

REP-00106: File {0} cannot be locked in shared mode.

Cause: Oracle Reports Builder tried to lock the file shown, but was unsuccessful. The most likely reason is that a system error made it impossible to lock the file.

Action: Consult the operating system documentation or contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

REP-00107: File {0} cannot be opened: bad name.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00108: File {0} cannot be found.

Cause: Oracle Reports Builder tried to access the file shown, but could not find it.

Action: Verify the file name. Specify a directory before the file name, or modify the REPORTS_PATH environment variable to include the directory where the file is located.
Level: 1

Type: ERROR

Impact: Other

REP-00109: There are too many files open.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00110: File {0} cannot be opened.

Cause: Oracle Reports Builder tried to open the file shown and could not. The possible causes of this error include the following: Case 1: The file was not found under the specified name in the specified location. Case 2: Lack of necessary privileges to open the file. Case 3: A system error made it impossible to open the file.

Action: Take the following actions to correct this error: If Case 1: Verify that the file is stored in the specified directory under the specified name. If it is not, change the directory and/or file name as appropriate. If Case 2: Verify the privileges necessary to open the file, and change the privileges accordingly. If Case 3: Consult the operating system documentation or contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

REP-00111: Directory {0} is protected.

Cause: Oracle Reports Builder attempted to read from or write to a directory that is read and write protected.

Action: Change the permissions on the directory as necessary.
Level: 1

Type: ERROR

Impact: Other

REP-00112: File {0} is write-protected.

Cause: Oracle Reports Builder attempted to write to a file that is write-protected.

Action: Change the permissions of the file as necessary.
Level: 1

Type: ERROR

Impact: Other

REP-00113: File {0} is read-protected.

Cause: Oracle Reports Builder attempted to read a file that is read-protected.

Action: Change the permissions of the file as necessary.
Level: 1

Type: ERROR

Impact: Other

REP-00114: File {0} no longer exists.

Cause: Oracle Reports Builder attempted to access a file that no longer exists.

Action: Remove the call to the file, re-create the file, or specify a different file.
Level: 1

Type: ERROR

Impact: Other

REP-00115: Directory {0} cannot be read.

Cause: Oracle Reports Builder attempted to read from or write to a directory that does not exist.

Action: Verify that the specified directory exists.
Level: 1

Type: ERROR

Impact: Other

REP-00116: Directory {0} cannot be accessed.

Cause: Oracle Reports Builder could not access the specified directory.

Action: Consult the system administrator.
Level: 1

Type: ERROR

Impact: Other

REP-00117: Exit to the host operating system failed.

Cause: Oracle Reports Builder attempted to exit the program and return control to the host operating system.

Action: No action is necessary.
Level: 1

Type: ERROR

Impact: Operating System

REP-00118: A temporary file cannot be created.

Cause: Oracle Reports Builder tried to create a temporary file but could not do so. The possible causes of this error include the following: Case 1: The environment variable that determines in what directory to create temporary files is set to an invalid directory. Case 2: There is not enough free space on the disk to create the temporary file. Case 3: A temporary file that cannot be modified already exists.

Action: Take the following actions to correct this error: If Case 1: Set the environment variable for temporary files to a valid directory. If Case 2: Free up some space on the disk. If Case 3: Remove the existing temporary file, if possible.
Level: 1

Type: ERROR

Impact: Other

REP-00119: File link boilerplate {0}'s Source Filename {1} cannot be found.

Cause: Oracle Reports Builder could not find the source file specified in the Source Filename property for the file link boilerplate object. The possible causes of this error include the following: Case 1: The file was not found under the specified name in the specified location. Case 2: Lack of necessary privileges to open the file. Case 3: A system error made it impossible to open the file.

Action: Take the following actions to correct this error: If Case 1: Verify that the file is stored in the specified directory under the specified name. If it is not, change the directory and/or file name as appropriate. If Case 2: Verify the privileges necessary to open the file, and change the privileges accordingly. If Case 3: Consult the operating system documentation or contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

REP-00120: Graph {0}'s associated document {1} cannot be found.

Cause: Oracle Reports Builder was unable to find the graph document. The possible causes of this error include the following: Case 1: The graph document was not found under the specified name in the specified location. Case 2: Lack of necessary privileges to open the graph document. Case 3: A system error made it impossible to open the graph document.

Action: Take the following actions to correct this error: If Case 1: Verify that the graph document is stored in the specified directory under the specified name. If it is not, change the directory and/or file name as appropriate. If Case 2: Verify the privileges necessary to open the graph document, and change the privileges accordingly. If Case 3: Consult the operating system documentation or contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

REP-00124: The temporary file cannot be written to.

Cause: Oracle Reports Builder tried to write to the temporary file but could not do so.

Action: Free up some space on the disk.
Level: 1

Type: ERROR

Impact: Other

REP-00125: An internal error occurred: Unable to load NLS character set.

Cause: ORA_NLS was not set, or the directory to which it points does not exist.

Action: Set ORA_NLS to point to the NLS directory containing character set files.
Level: 1

Type: ERROR

Impact: Other

REP-00126: File {0} is not a known type to Oracle Reports Builder. No file conversion can be performed. Check in anyway?

Cause: An attempt was made to check in a file of a type that Oracle Reports Builder cannot convert. For example, Oracle Reports Builder cannot convert a Form Builder (FMB) file.

Action: To continue checking in, click Yes. Otherwise, click No and nothing will be checked in.
Level: 1

Type: ERROR

Impact: Other

REP-00127: File {0} is not a known type to Oracle Reports Builder. No file conversion can be performed. Check out anyway?

Cause: An attempt was made to check out a file of a type that Oracle Reports Builder cannot convert. For example, Oracle Reports Builder cannot convert a Form Builder (FMB) file.

Action: To continue checking out, click Yes. Otherwise, click No and nothing will be checked out.
Level: 1

Type: ERROR

Impact: Other

REP-00128: There are unsaved changes in file {0}. Save before checkin?

Cause: An attempt was made to check in a file that is currently open and there are unsaved changes.

Action: To save and check in the file, click Yes. Click No to check in the file without the changes. Otherwise, click Cancel and nothing will be checked in.
Level: 1

Type: ERROR

Impact: Other

REP-00129: There are unsaved changes in file {0}. Check out anyway?

Cause: An attempt was made to check out a file that is is currently open and there are unsaved changes.

Action: To check out the file, click Yes. Note that this will overwrite all the changes made to this file. Otherwise, click No and nothing will be checked out.
Level: 1

Type: ERROR

Impact: Other

REP-00130: A module saved in the database cannot be checked in. Save it to file before checkin.

Cause: Checking in a module saved in the database is not supported.

Action: Save the module to the filesystem first and then check it in again.
Level: 1

Type: ERROR

Impact: Other

REP-00131: The communication layer cannot be initialized.

Cause: The required communication files were not found.

Action: Check the installation and setup and update with the latest patch.
Level: 1

Type: ERROR

Impact: Other

REP-00132: A JVM cannot be started.

Cause: Oracle Reports could not start up the required JVM services.

Action: Check the installation and setup and update with the latest patch.
Level: 1

Type: ERROR

Impact: Other

REP-00133: Java Classes cannot be found.

Cause: Some required files were not found. This could be caused by an invalid installation or missing files.

Action: Check the installation and setup and update with the latest patch.
Level: 1

Type: ERROR

Impact: Other

REP-00150: There are too many arguments.

Cause: More than the allowable number of arguments for the command were entered.

Action: Check the syntax of the command. For more information, see the Command Line Keywords appendix in the Publishing Reports to the Web manual. Reenter the command correctly.
Level: 1

Type: ERROR

Impact: Other

REP-00151: Duplicate arguments are specified for keyword {0}.

Cause: An argument was entered more than once for the keyword shown. The possible causes of this error include the following: Case 1: A positional argument was entered for the keyword and then the keyword was entered with another argument. Case 2: The same keyword was entered twice (for example, KEYWORD1=YES and KEYWORD1=NO).

Action: Check the syntax of the command (see the Command Line Keywords appendix in the Publishing Reports to the Web manual). Take the following actions to correct this error: If Case 1: Reenter the command with just the positional argument or just the keyword argument. If Case 2: Reenter the command specifying the keyword only once.
Level: 1

Type: ERROR

Impact: Other

REP-00152: A positional argument is specified after a keyword.

Cause: On the command line, an argument was entered without its keyword after being an argument was entered with its keyword. Once a keyword is used on the command line, all subsequent arguments must use keywords as well.

Action: Reenter the command making sure that no positional arguments (arguments where the keyword is implicit) are specified after arguments with keywords.
Level: 1

Type: ERROR

Impact: Other

REP-00153: Multiple values are not allowed for keyword {0}.

Cause: In the command, more than the allowable number of values for the keyword were entered. For example, KEYWORD=(A, B) was entered, where KEYWORD accepts only a single value.

Action: Check the syntax of the command. For more information, see the Command Line Keywords appendix in the Publishing Reports to the Web manual. Reenter the command without the extra values.
Level: 1

Type: ERROR

Impact: Other

REP-00154: The command file cannot be opened.

Cause: A command referenced the command file shown and the file could not be opened. The possible causes of this error include the following: Case 1: The file was not found under the specified name in the specified location. Case 2: Lack of necessary privileges to open the file. Case 3: A system error made it impossible to open the file.

Action: Take the following actions to correct this error: If Case 1: Verify that the file is stored in the specified directory under the specified name. If it is not, change the directory and/or file name or move the file into the specified directory. If Case 2: Verify the privileges necessary to access the file, and change the privileges accordingly. If Case 3: Consult the operating system documentation or contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

REP-00155: The value for keyword {0} is invalid.

Cause: The value entered for the keyword shown was not a valid value.

Action: Check the syntax of the keyword. For more information, see the Command Line Keywords appendix in the Publishing Reports to the Web manual. Reenter the command with the appropriate value for the keywords.
Level: 1

Type: ERROR

Impact: Other

REP-00156: The value for keyword DESTYPE is invalid.

Cause: In Reports Runtime, an invalid value was provided for the DESTYPE keyword.

Action: Check the syntax of the keyword. Valid values are SCREEN, FILE, PRINTER, MAIL or SYSOUT. For more information, see the Command Line Keywords appendix in the Publishing Reports to the Web manual. Reenter the command with the appropriate value for the keywords.
Level: 1

Type: ERROR

Impact: Other

REP-00157: The value for {0} must be either YES or NO.

Cause: A value other than YES or NO was entered for the keyword shown, and the keyword only accepts YES or NO.

Action: Reenter the command using a value of YES or NO for the keyword shown.
Level: 1

Type: ERROR

Impact: Other

REP-00158: The command line keyword {0} is unknown.

Cause: The referenced string was entered as a keyword, but there is no such keyword.

Action: Check the syntax of the command. For more information, see the Command Line Keywords appendix in the Publishing Reports to the Web manual. Reenter the command with the appropriate value for the keywords.
Level: 1

Type: ERROR

Impact: Other

REP-00159: A syntax error exists on the command line.

Cause: The string entered on the command line could not be parsed. The most likely cause of this error is that quotation marks or parentheses were entered without matching end quotation marks or parentheses.

Action: Check the syntax of the command. For more information, see the Command Line Keywords appendix in the Publishing Reports to the Web manual. Reenter the command using the appropriate syntax.
Level: 1

Type: ERROR

Impact: Other

REP-00160: A syntax error exists in the command file.

Cause: Something entered in the command file could not be parsed. The most likely cause of this error is that quotation marks or parentheses were entered without matching end quotation marks or parentheses.

Action: Check the syntax of the commands. For more information, see the Command Line Keywords appendix in the Publishing Reports to the Web manual. Edit the file and modify the commands as necessary to correct the commands.
Level: 1

Type: ERROR

Impact: Other

REP-00161: No command-line arguments are specified.

Cause: Reports Converter was invoked without specifying any command-line arguments.

Action: Specify the appropriate command-line arguments (for example, SOURCE, DEST) for Reports Converter. For more information, see the Command Line Keywords appendix in the Publishing Reports to the Web manual.
Level: 1

Type: ERROR

Impact: Other

REP-00162: The value for keyword SHOWWINDOW is invalid.

Cause: The value specified for the SHOWWINDOW keyword was not valid.

Action: Check the syntax of the keyword. Valid values are DEFAULT, WIZARD, and PREVIEWER. For more information, see the Command Line Keywords appendix in the Publishing Reports to the Web manual.
Level: 1

Type: ERROR

Impact: Other

REP-00163: The value for keyword DESTYPE is invalid.

Cause: The value specified for the DESTYPE keyword was not valid for the Reports Server.

Action: Check the syntax of the keyword. Valid values are FILE, PRINTER, MAIL, or CACHE.
Level: 1

Type: ERROR

Impact: Other

REP-00164: The value for keyword PARAMFORM is invalid.

Cause: The value specified for the PARAMFORM keyword was not valid.

Action: Reenter the command, specifying a value of YES, NO, or HTML[action] for the PARAMFORM keyword.
Level: 1

Type: ERROR

Impact: Other

REP-00165: The value for keyword SITENAME is missing.

Cause: No value was specified for the SITENAME keyword. A value is required for SITENAME in order to schedule a report.

Action: Specify a WEBDB site name for the keyword SITENAME.
Level: 1

Type: ERROR

Impact: Other

REP-00166: Read/write of the specified directory is not allowed.

Cause: Oracle Reports attempted to read from or write to a directory without read/write privileges.

Action: Check the command line options to identify the directory name. Add the directory to REPORTS_PATH, ORACLE_PATH, or the sourceDir property in the engine element in the server configuration file.
Level: 1

Type: ERROR

Impact: Other

REP-00171: Output from the remote server cannot be retrieved.

Cause: An error occurred when retrieving output from the remote server.

Action: Verify that the file is accessible, and that the server is set to allow retrieving outputs.
Level: 1

Type: ERROR

Impact: Other

REP-00172: The value for keyword SERVER is missing.

Cause: No value was specified for the mandatory keyword SERVER.

Action: Provide a valid argument for the keyword SERVER and rerun the command.
Level: 1

Type: ERROR

Impact: Other

REP-00173: The value for keyword SHOWJOBS is invalid.

Cause: In the Reports Queue Viewer, an argument provided in command line for the SHOWJOBS keyword was not valid.

Action: Reenter the command, specifying a value of PAST, CURRENT or FUTURE for the SHOWJOBS keyword.
Level: 1

Type: ERROR

Impact: Other

REP-00174: An internal error occurred while obtaining the Reports Server queue information.

Cause: The Reports Server did not return valid information about its queue to the queue viewer. This could be caused by one of the following reasons: Case 1: The connection to the Reports Server unexpectedly went down. Case 2: The Reports Server is in an unstable state, or has been shut down.

Action: Verify that the Reports Server is running. Contact the system administrator and retry the command after verifying that the Reports Server is running. If this problem persists, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00175: An internal error occurred while obtaining the Reports Server properties information.

Cause: The Reports Server did not return valid information about its properties to the queue viewer. This could be caused by one of the following reasons: Case 1: The connection to the Reports Server unexpectedly went down. Case 2: The Reports Server is in an unstable state, or has been shut down.

Action: Verify that the Reports Server is running. Contact the system administrator and retry the command after verifying that the Reports Server is running. If this problem persists, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00176: Server {0} is shutting down.

Cause: A report cannot be submitted when the specified Reports Server is shutting down.

Action: Submit to another Reports Server or wait until the Server is back up.
Level: 1

Type: ERROR

Impact: Other

REP-00177: An error occurred while running in a remote server.

Cause: An attempt to run a command line in the remote server failed.

Action: Check the command line.
Level: 1

Type: ERROR

Impact: Other

REP-00178: Reports Server {0} cannot establish connection.

Cause: A proper connection could not be established to the specified Reports Server.

Action: Check the network and check the status of the Reports Server in question.
Level: 1

Type: ERROR

Impact: Other

REP-00179: Report execution terminated unexpectedly while running.

Cause: The Reports Engine has crashed while running.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

REP-00180: The report has been canceled from the Reports Server.

Cause: The report was stopped while it was executing or removed from the queue before it was started.

Action: No action is necessary.
Level: 1

Type: ERROR

Impact: Other

REP-00181: An error occurred reading or writing the configuration file for the Reports Server.

Cause: The configuration file cannot be opened, or its content is incomprehensible.

Action: Check the configuration file and its access rights. Restart the server.
Level: 1

Type: ERROR

Impact: Configuration

REP-00182: A syntax error occurred on command line for the Reports Server.

Cause: The string entered on the command line could not be parsed. The most likely cause of this error is that quotation marks or parentheses were entered without matching end quotation marks or parentheses.

Action: Check the syntax of the command. For more information, see the Command Line Keywords appendix in the Publishing Reports to the Web manual. Reenter the command using the appropriate syntax.
Level: 1

Type: ERROR

Impact: Other

REP-00183: TNSNAME must be provided to start up the Reports Server.

Cause: An attempt was made to start up the Reports Server without specifying the TNSNAME to which the Server should listen.

Action: Specify the TNSNAME as a command-line argument.
Level: 1

Type: ERROR

Impact: Other

REP-00184: The specified MAXCONNECTS is out of range.

Cause: The MAXCONNECTS value specified is out of range for this platform. MAXCONNECTS must be at least 2, and cannot exceed 4096, and on some platforms the limit is even lower.

Action: Specify an appropriate value.
Level: 1

Type: ERROR

Impact: Other

REP-00185: Bad load arguments were supplied when starting up the Reports Server.

Cause: Inconsistent values were specified among MAXCONNECTS, MINLOAD, MAXLOAD, and INITLOAD.

Action: Verify that 0 &lt;= MINLOAD &lt;= INITLOAD &lt;= MAXLOAD &lt; MAXCONNECTS.
Level: 1

Type: ERROR

Impact: Other

REP-00186: A daemon cannot listen to the port.

Cause: Another daemon may be running that is already listening to the port.

Action: No action is necessary. Since a daemon is already running, submit the report to be run.
Level: 1

Type: ERROR

Impact: Other

REP-00187: A daemon cannot start up the engine.

Cause: A daemon cannot start up the engine executable and communicate with it. This is most likely an installation issue.

Action: Verify that the installation is done properly.
Level: 1

Type: ERROR

Impact: Other

REP-00188: Reports Server only accepts batch jobs.

Cause: A job was submitted to the Reports Server where BATCH=NO, DESTYPE=SCREEN, DESTYPE=PREVIEW, or DESTYPE=SYSOUT.

Action: These settings are not allowed. Change the command line accordingly.
Level: 1

Type: ERROR

Impact: Other

REP-00189: The Reports Server cache cannot be written to.

Cause: Reports Server failed to write to the cache directory.

Action: Verify that the cache directory is specified in the server configuration file and it is writable.
Level: 1

Type: ERROR

Impact: Other

REP-00190: A report cannot be run to screen in the background.

Cause: The report was specified to be run in the background, with DESTYPE=SCREEN. A report cannot run in the background while having its output sent to the screen.

Action: To send the output to the screen, run it in the foreground. To run the report in the background, specify a different DESTYPE.
Level: 1

Type: ERROR

Impact: Other

REP-00194: A character report cannot be run in bitmap mode using this executable.

Cause: Oracle Reports attempted to use the character-mode executable to run a character-mode report with MODE=BITMAP. This is not allowed.

Action: Change the value of the MODE keyword to match the mode of the executable.
Level: 1

Type: ERROR

Impact: Other

REP-00195: A report cannot be run in bitmap mode to screen using this executable.

Cause: Oracle Reports attempted to use the character-mode executable to run a bitmapped report to the screen. This is not allowed.

Action: Run the report using BATCH=YES or use a bitmapped executable.
Level: 1

Type: ERROR

Impact: Other

REP-00196: The report cannot be run in the background.

Cause: BACKGROUND=YES was specified under one of the following conditions, none of which are allowed: Case 1: Running the report from the designer. Case 2: BATCH=YES. Case 3: Running the report using the packaged procedure srw.run_report. Case 4: The platform on running the report does not support spawning of another process.

Action: Ensure that BACKGROUND=NO when any of the above condition are true.
Level: 1

Type: ERROR

Impact: Other

REP-00197: BATCH=YES or BACKGROUND=YES must be specified on the command line when running a bitmapped report.

Cause: Oracle Reports attempted to run a bitmapped report using the character-mode executable in the foreground or during an interactive session. This is not supported.

Action: To run a bitmapped report using the character-mode executable, specify either BATCH=YES or BACKGROUND=YES (unlike BATCH=YES, this setting provides access to the Runtime Parameter Form).
Level: 1

Type: ERROR

Impact: Other

REP-00200: Enough memory cannot be allocated.

Cause: Oracle Reports Builder cannot obtain enough memory from the system to complete the current task.

Action: Make more memory available, if possible, or ask the system administrator for assistance.
Level: 1

Type: ERROR

Impact: Memory

REP-00201: A zero or negative block size was requested.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00202: A null pointer cannot be freed.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00203: A null pointer was passed as a handle.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00204: The handle does not point into an mp block.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00205: There are too many simultaneous locks on one object.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00206: A null cache pointer is passed to virtual memory routine.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Memory

REP-00207: The requested block is larger than virtual memory space.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Memory

REP-00208: rmaloc was not given a function identifier.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00209: rmaloc was not given a structure identifier.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00210: An illegal operation was requested on a locked handle.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00211: A handle cannot be used after freeing it.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00212: No literal is specified.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00213: An attempt to lock a handle failed.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00214: A virtual memory buffer of size {0} KB cannot be allocated. Try a smaller size.

Cause: Oracle Reports Builder tried to allocate a virtual memory buffer size at or below the number specified for the BUFFERS keyword.

Action: Specify a smaller size for BUFFERS, either on the command line or in the Runtime Settings tab of the Preferences dialog box (select Edit, then Preferences), or free up more memory. For command line syntax, see the Command Line Keywords appendix in the Publishing Reports to the Web manual.
Level: 1

Type: ERROR

Impact: Memory

REP-00215: An error occurred locking, dereferencing, or freeing a memory handle.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Memory

REP-00216: There is insufficient memory to save the report as a JSP or XML.

Cause: The report definition file has exceeded 10 MB. The report cannot be saved as a JSP or XML if it exceeds 10 MB.

Action: Reduce the size of the file.
Level: 1

Type: ERROR

Impact: Memory

REP-00230: An error occurred while starting a thread.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00231: An error occurred while posting thread message.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Threads

REP-00232: An error occurred while getting thread message.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Threads

REP-00235: The Security Server TNSNAME is not provided in the config file.

Cause: Security Server TNSNAME must be specified in config file on security mode"

Action: Specify Security Server TNSNAME in the config file by using the keyword 'securitytnsname'.
Level: 1

Type: ERROR

Impact: Security

REP-00236: The Security Server cannot be connected.

Cause: An abnormal condition was encountered.

Action: Contact the system administrator. For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Security

REP-00238: Authentication failed.

Cause: The system userid/password is invalid or does not have privilege to run the report.

Action: Check the system userid/password to verify that it is correct or contact the system administrator to grant the necessary privilege.
Level: 1

Type: ERROR

Impact: Security

REP-00239: The Security server authentication failed: invalid user name.

Cause: The system user ID is incorrect.

Action: Check the system user ID to verify that it is correct or contact the system administrator about the system user ID.
Level: 1

Type: ERROR

Impact: Security

REP-00240: The Security Server authentication failed: invalid password.

Cause: The password for the system user ID is incorrect.

Action: Check the system user ID password to verify that it is correct or contact the system administrator about the system user ID password.
Level: 1

Type: ERROR

Impact: Security

REP-00241: The Security Server authentication failed: no privilege on the Reports Server.

Cause: The system user ID does not have privilege to access the Reports Server.

Action: Contact the system administrator about the system user ID's privilege on the Reports Server.
Level: 1

Type: ERROR

Impact: Security

REP-00242: The Security Server authentication failed: no privilege on the printer.

Cause: The system user ID does not have privilege to access the printer.

Action: Contact the system administrator about the system user ID's privilege on the printer.
Level: 1

Type: ERROR

Impact: Security

REP-00243: The Security Server authentication failed: no privilege on the module.

Cause: The system user ID does not have privilege to access the module.

Action: Contact the system administrator about the system user ID's privilege on the module.
Level: 1

Type: ERROR

Impact: Security

REP-00244: The Security Server authentication failed: no privilege of this access type.

Cause: The system user ID does not have privilege of this access type.

Action: Contact the system administrator about the system user ID's privilege of this access type.
Level: 1

Type: ERROR

Impact: Security

REP-00245: The Security Server authentication failed: no privilege of this output type.

Cause: The system user ID does not have privilege of this output type.

Action: Contact the system administrator about the system user ID's privilege of this output type.
Level: 1

Type: ERROR

Impact: Security

REP-00246: The Security Server authentication failed: no privilege for the given time.

Cause: The system user ID does not have privilege for the given time.

Action: Contact the system administrator about the system user ID's privilege for the given time.
Level: 1

Type: ERROR

Impact: Security

REP-00247: The Security Server authentication failed: no privilege for the given date.

Cause: The system user ID does not have privilege for the given date.

Action: Contact the system administrator about the system user ID's privilege for the given date.
Level: 1

Type: ERROR

Impact: Security

REP-00250: A symbol table overflow occurred.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00251: The identifier does not match a defined symbol.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00252: The path specified by environment variable {0} is too long and will be ignored.

Cause: The path specified by the environment variable is too long.

Action: Shorten the length of the designated path.
Level: 1

Type: ERROR

Impact: Other

REP-00253: The total length of the search paths is too long and will be truncated.

Cause: The combined length of search paths in the path environment is too long. The combined length cannot exceed 255 characters.

Action: Shorten the length of one or more paths in the path environment.
Level: 1

Type: ERROR

Impact: Other

REP-00300: An Oracle error occurred.

Cause: Oracle Reports Builder encountered an Oracle error.

Action: Scroll through the error message to see where the error occurred and, if possible, fix it. Otherwise, contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

REP-00301: The SELECT statement may not contain an INTO clause.

Cause: An INTO clause was entered in a SELECT statement, which is not allowed in Oracle Reports Builder.

Action: Remove the INTO clause.
Level: 1

Type: ERROR

Impact: Other

REP-00302: Parameter {0} cannot be found in the report.

Cause: Oracle Reports referenced a parameter that is not defined in the report. The most likely cause is that a parameter was deleted but not all references to it were deleted.

Action: Delete all references to the deleted parameter.
Level: 1

Type: ERROR

Impact: Other

REP-00303: The statement entered is not a SELECT statement.

Cause: What was entered in the SELECT Statement field is something other than a SELECT statement. The possible causes of this error include the following: Case 1: Something besides a SELECT statement was entered in the SELECT Statement field. Case 2: An external query was referecned that did not contain a SELECT statement.

Action: Take the following actions to correct this error: If Case 1: Enter a valid SELECT statement. If Case 2: Modify the external query or reference another external query.
Level: 1

Type: ERROR

Impact: Other

REP-00304: & in SELECT statement was not followed by a valid lexical parameter.

Cause: An ampersand (&) appears in the SELECT statement by itself. The possible causes of this error include the following: Case 1: A lexical reference either left out the name of the column or parameter altogether or there is a space between the ampersand and the name of the column or parameter. Case 2: An ampersand was accidentally typed in the SELECT statement.

Action: Take the following actions to correct this error: If Case 1: Verify that the column or parameter name immediately follows the ampersand with no spaces in between. If Case 2: Delete the ampersand.
Level: 1

Type: ERROR

Impact: Other

REP-00305: Reference {0} cannot be used as a lexical parameter because it is not a character value.

Cause: An invalid lexical reference appears in the SELECT statement. Lexical references can only be made to parameters or columns containing character data. The possible causes of this error include the following: Case 1: The wrong column or parameter was referenced. Case 2: The reference should be a bind reference, not a lexical reference. Case 3: The parameter or column referenced was created with a non-character data type.

Action: Take the following actions to correct this error: If Case 1: Change the name that follows the ampersand (&) so it references a parameter or column with a data type of Character. If Case 2: Replace the ampersand (&) with a colon (:) when referencing the parameter or column. If Case 3: Change the data type of the parameter or column to be Character, if appropriate.
Level: 1

Type: ERROR

Impact: Other

REP-00306: The name {0} is not a valid parameter name.

Cause: In making reference to a parameter, an attempt was made to create a parameter with an invalid name. For a bind reference, a parameter definition is automatically created using the name specified in the bind parameter. In this case, Oracle Reports Builder could not create the parameter because the name supplied was not a valid name.

Action: Check the naming conventions for data model objects and rules for parameter names. Rename the parameter and change the name in the bind reference.
Level: 1

Type: ERROR

Impact: Other

REP-00307: The SELECT statement may not contain a FOR UPDATE clause.

Cause: A FOR UPDATE clause was entered in the SELECT statement, which is not allowed in Oracle Reports Builder.

Action: Remove the FOR UPDATE clause.
Level: 1

Type: ERROR

Impact: Other

REP-00308: An internal error occurred: Unknown column type.

Cause: The possible causes of this error include the following: Case 1: An attempt was made to display the value of a column using SRW.MESSAGE, but the column's data type (for example, LONG, LONG RAW, ROWID) is not supported for that operation. Case 2: An attempt was made to pass the value of a column to Forms Runtime or Graphics Runtime as a parameter, but the column's data type (for example, LONG, LONG RAW, ROWID) is not supported for that operation.

Action: Do not attempt to display or pass this column's value.
Level: 1

Type: ERROR

Impact: Other

REP-00309: The specified database cannot connect after three attempts. Access denied.

Cause: Case 1: Some part of the logon string entered was incorrect. After three failed attempts, Oracle Reports Builder displays a dialog box with this message. Case 2: The NLS_LANG environment variable value may be invalid.

Action: Case 1: Accept the dialog box. Confirm the logon information with the system administrator, if necessary. Go back into Oracle Reports Builder and try connecting to Oracle again. If the problem persists, the system administrator may need to create a new Oracle logon. Case 2: Verify the NLS_LANG value is valid.
Level: 1

Type: ERROR

Impact: Other

REP-00310: An error occurred while processing bind variables in a query.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00311: An internal error occurred: Segmented memory used for lexical parameter.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Memory

REP-00312: An internal error occurred: Error dealing with segmented memory.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00313: An internal error occurred: Fetching data records would cause memory overflow.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Data

REP-00314: The column name exceeds 256 characters, and no alias is assigned.

Cause: One of the SQL SELECT statements contains an expression that is longer than 256 characters, but has no alias.

Action: Edit the SELECT statement and assign an alias to the expression.
Level: 1

Type: ERROR

Impact: Other

REP-00315: Each SELECT statement must have the same number of columns in a compound query.

Cause: A query with a UNION, INTERSECT, or MINUS set operator was entered in which the SELECT statements in the query do not have the same number of selected columns.

Action: Modify the SELECT statements so that they have the same number of columns.
Level: 1

Type: ERROR

Impact: Other

REP-00316: The types of corresponding columns must match in a compound query.

Cause: A query with a UNION, INTERSECT, or MINUS set operator was entered in which corresponding columns have different types. For example, column 1 in the first SELECT statement has data type CHAR, while column 1 in the second SELECT statement has data type NUMBER.

Action: Modify the SELECT statements so that all corresponding columns have the same data type.
Level: 1

Type: ERROR

Impact: Other

REP-00320: The database cannot be connected.

Cause: An attempt to connect to the database failed.

Action: Recheck the user ID and password and try again.
Level: 1

Type: ERROR

Impact: Other

REP-00321: An internal error occurred: Describe of query failed.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00322: An internal error occurred: Attempt to put back fetched rows failed.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00330: An internal error occurred: Location GET_REF parameters failed.

Cause: A CDE_MM.GET_REF call in a query did not specify a parameter list.

Action: Add the parameter list to the call in the query's SELECT statement.
Level: 1

Type: ERROR

Impact: Other

REP-00331: The GET_REF PL/SQL function requires 3 parameters.

Cause: The parameter list of a CDE_MM.GET_REF call in a query was incomplete.

Action: Add the necessary parameters to the call in the query's SELECT statement.
Level: 1

Type: ERROR

Impact: Other

REP-00332: The GET_REF PL/SQL function's last parameter must be of type ROWID.

Cause: A parameter of type ROWID was not provided as the last parameter for a GET_REF function.

Action: Check the parameter list and ensure the last parameter is of type ROWID.
Level: 1

Type: ERROR

Impact: Other

REP-00340: The role password cannot be verified, and the report is not opened.

Cause: Incorrect role password. For security reasons, the report cannot be openend.

Action: Try opening the report again and type in the correct role password.
Level: 1

Type: ERROR

Impact: Other

REP-00341: The roles specified in the report cannot be set, and the report is not opened.

Cause: The roles specified in the report cannot be set while opening the report. For security reasons, the report cannot be opened.

Action: Check role permissions and password.
Level: 1

Type: ERROR

Impact: Other

REP-00342: Roles specified on the command line cannot be set.

Cause: The roles specified on the command line cannot be set.

Action: Check role permissions and password.
Level: 1

Type: ERROR

Impact: Other

REP-00343: Default roles of the current user cannot be set.

Cause: Reports is unable to set the default roles of the current user that has passwords.

Action: Do not use default roles with passwords.
Level: 1

Type: ERROR

Impact: Other

REP-00344: The role password was not confirmed correctly.

Cause: The Confirm Password entered is different from the Role Password.

Action: Reenter and verify that Confirm Password exactly matches the Role Password.
Level: 1

Type: ERROR

Impact: Other

REP-00345: An empty role and a non-empty password is not valid.

Cause: No role is specified, while role password is specified.

Action: Leave all fields empty to not associate a role with this report.
Level: 1

Type: ERROR

Impact: Other

REP-00346: The role must be no longer than {0} characters. It will be truncated.

Cause: The role name specified is longer than is allowable. It will be truncated.

Action: Specify a shorter role name.
Level: 1

Type: ERROR

Impact: Other

REP-00347: The role password must be no longer than {0} characters. It will be truncated.

Cause: The role password specified is longer than is allowable. It will be truncated.

Action: Specify a shorter role password.
Level: 1

Type: ERROR

Impact: Other

REP-00348: The role password is incorrect.

Cause: The role password entered was incorrect.

Action: Reenter with the correct role password.
Level: 1

Type: ERROR

Impact: Other

REP-00450: PL/SQL error {0} was encountered.

Cause: Oracle Reports Builder encountered the identified PL/SQL error while running a report.

Action: Edit and recompile the PL/SQL in the report to avoid this error.
Level: 1

Type: ERROR

Impact: Other

REP-00451: PL/SQL error {0} was encountered. {1}.

Cause: Oracle Reports Builder encountered the identified PL/SQL error while running a report.

Action: Edit and recompile the PL/SQL in the report to avoid this error.
Level: 1

Type: ERROR

Impact: Other

REP-00452: PL/SQL error {0} was encountered. {1}. {2}.

Cause: Oracle Reports Builder encountered the identified PL/SQL error while running a report.

Action: Edit and recompile the PL/SQL in the report to avoid this error.
Level: 1

Type: ERROR

Impact: Other

REP-00453: PL/SQL error {0} was encountered. {1}. {2}. {3}.

Cause: Oracle Reports Builder encountered the identified PL/SQL error while running a report.

Action: Edit and recompile the PL/SQL in the report to avoid this error.
Level: 1

Type: ERROR

Impact: Other

REP-00490: An internal error occurred: Toolkit context unavailable.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00491: Data truncation is possible in column {0}.

Cause: The database column's width in the report is defined to be less than its width in the database. This can sometimes occur when the columns in the database are updated subsequent to the report being defined. This warning is raised only when RUNDEBUG is YES.

Action: Force the query to be reparsed. One method is to type a space at the end of a line in the SELECT Statement field and then accept the SQL Query Statement dialog.
Level: 1

Type: ERROR

Impact: Data

REP-00492: The token {0} is unrecognized.

Cause: The SELECT statement entered contains an item that is not part of SQL syntax.

Action: Review the SELECT statement and ensure that it follows SQL syntax.
Level: 1

Type: ERROR

Impact: Other

REP-00493: An internal error occurred: Unable to expand lexical references.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00494: An internal error occurred: Unable to process lexical references.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

REP-00495: An internal error occurred: Unable to tokenize the query.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00496: An internal error occurred: Unable to parse the query.

Cause: The SQL statement entered cannot be parsed because it contains an error.

Action: Review the SQL statement to ensure correct syntax. For more information, see the SQL Language Reference Manual.
Level: 1

Type: ERROR

Impact: Other

REP-00497: An internal error occurred: Query failed in rodslt.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00498: The number of columns selected by the query is incompatible with the report definition.

Cause: The query is selecting more columns than the report definition is expecting. This can happen when using an external query and the query has been changed since the report was defined.

Action: Update the report definition so that it accepts the changed query. For example, go to the SQL Query Statement dialog for the query that references the changed external query and modify it. Formulas, summaries, and fields that rely on any changed columns may also need to be updated.
Level: 1

Type: ERROR

Impact: Other

REP-00499: Column {0} selected by the query is incompatible with the report definition.

Cause: The column from the database does not match the column in the report definition. The possible causes of this error include the following: Case 1: The definition of the column in the database has changed since the report was defined. Case 2: The report uses an external query and the external query was changed since the report was defined.

Action: Take the following actions to correct this error: If Case 1: Update the report definition so that it accepts the changed column. For example, if the data type of the column has changed, reaccept the SQL Query Statement dialog external query so the column in the report definition has its data type updated. Formulas, summaries, and fields that rely on the changed column may also need to be updated. If Case 2: Update the report definition so that it accepts the changed query. For example, reaccept the SQL Query Statement dialog that references the changed external query and accept it. Formulas, summaries, and fields that rely on any changed columns may also need to be updated.
Level: 1

Type: ERROR

Impact: Other

REP-00500: The number entered is out of range.

Cause: The number specified is too large.

Action: Check the limits of the field. Look in the chapter where the field is described and enter a number that is within the limits.
Level: 1

Type: ERROR

Impact: Other

REP-00501: The specified database cannot be connected.

Cause: Oracle Reports Builder could not connect to Oracle The possible causes of this error include the following: Case 1: The Oracle database is temporarily unavailable. Case 2: The connect information was not valid.

Action: Take the following actions to correct this error: If Case 1: Retry the operation. Contact the system administrator if the problem persists. Note that after three failed attempts, Oracle Reports Builder closes. If Case 2: Verify the connect information, and try to connect again. Note that after three failed attempts, Oracle Reports Builder closes.
Level: 1

Type: ERROR

Impact: Other

REP-00502: An error occurred attempting to open terminal file {0}.

Cause: Oracle Reports Builder was unable to open the terminal definition file specified. Either the name of the file was specified incorrectly after the TERM keyword, or the file was not found.

Action: Verify the name of the terminal definition file, and its path. If the problem persists, contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

REP-00503: The report name is invalid.

Cause: An invalid name was specified for the name of a report.

Action: Specify a valid report name.
Level: 1

Type: ERROR

Impact: Other

REP-00504: The specified database is not connected.

Cause: An attempt was made to perform an operation that requires a connection to the database, but no database connection was established.

Action: Select File, then Connect to connect to the database.
Level: 1

Type: ERROR

Impact: Other

REP-00505: The width for this column is not valid.

Cause: The value entered in Width was invalid. The possible causes of this error include the following: Case 1: Zero or a negative number was entered. Width must be greater than zero. Case 2: Something that was not a number was entered. Case 3: For a column of non-numeric data type, a width of the form (x, y) was entered, where x is the precision and y is the scale. This type of Width specification is only valid when the data type is Number.

Action: Take the following actions to correct this error: If Case 1: Enter a number greater than zero. If Case 2: Enter a number greater than zero. If Case 3: Enter a number greater than zero or, if possible, change the data type of the column to Number.
Level: 1

Type: ERROR

Impact: Other

REP-00506: Database columns cannot be moved between queries.

Cause: An attempt was made to move a column into another group belonging to another query and the column is a database column. A database column must be selected by the query that owns its group.

Action: Select the column, if possible, in the query that owns the group to which it should be moved.
Level: 1

Type: ERROR

Impact: Other

REP-00507: The file name is invalid.

Cause: In a file selection dialog box, the dialog box was accepted without specifying a file name.

Action: Enter a name and then accept or cancel the dialog box.
Level: 1

Type: ERROR

Impact: Other

REP-00508: The object name is invalid.

Cause: In a database object selection dialog box, the dialog box was accepted without specifying an object name.

Action: Enter a name and then accept or cancel the dialog box.
Level: 1

Type: ERROR

Impact: Other

REP-00509: The number value is invalid.

Cause: In a numeric field, something other than a digit or a decimal point was entered.

Action: Enter a number that contains only digits and, if necessary, a decimal point.
Level: 1

Type: ERROR

Impact: Other

REP-00510: The Unit of Measurement value is invalid.

Cause: An invalid unit of measurement was entered in the Unit of Measurement field.

Action: Select the desired option from the list of values: 'Character', 'Inch', 'Centimeter' or 'Point'
Level: 1

Type: ERROR

Impact: Other

REP-00511: The Panel Print Order value is invalid.

Cause: The Panel Print Order entered was not one of the two valid options.

Action: Select the desired option from the list of values: 'Across/Down' or 'Down/Across'.
Level: 1

Type: ERROR

Impact: Other

REP-00512: The number value is invalid.

Cause: The number entered was a decimal value and Oracle Reports Builder was expecting a non-decimal value.

Action: Enter a non-decimal value.
Level: 1

Type: ERROR

Impact: Other

REP-00513: The Unit of Measurement value is invalid.

Cause: The Unit of Measurement is blank and an attempt was made to move to another setting.

Action: Select an option for Unit of Measurement.
Level: 1

Type: ERROR

Impact: Other

REP-00514: The Page Size value is invalid.

Cause: The Page Width and/or Page Height settings were left blank and they require a value.

Action: Enter a number for Page Width and/or Page Height.
Level: 1

Type: ERROR

Impact: Other

REP-00515: The Parameter Form Size value is invalid.

Cause: The Parameter Form Width and/or Parameter Form Height settings were left blank and they require a value.

Action: Enter a number for Parameter Form Width and/or Parameter Form Height.
Level: 1

Type: ERROR

Impact: Other

REP-00516: The Page Size value is invalid.

Cause: The value entered for Page Size was not in character units, and Page Size requires character units.

Action: Enter a value in characters for Page Size.
Level: 1

Type: ERROR

Impact: Other

REP-00517: The Form Size value is invalid.

Cause: The value entered for Form Size was not in character units, and Form Size requires character units.

Action: Enter a value in characters for Form Size.
Level: 1

Type: ERROR

Impact: Other

REP-00518: The Object Access value is invalid.

Cause: The Object Access setting entered was not one of the three valid choices.

Action: Select an option from the list of values: Database, File, or File/Database.
Level: 1

Type: ERROR

Impact: Other

REP-00519: The Default Text Edit Mode value is invalid.

Cause: The Default Text Edit Mode entered was not one of the two valid choices.

Action: Select an option from the list of values: Insert or Replace.
Level: 1

Type: ERROR

Impact: Other

REP-00520: The Group/Frame Indentation value is invalid.

Cause: The value entered for Group/Frame Indentation was outside the valid range of values.

Action: Enter a number between 0 and 4.
Level: 1

Type: ERROR

Impact: Other

REP-00521: The name {0} is not valid.

Cause: An object was given an invalid name.

Action: Verify the naming conventions for the object type.
Level: 1

Type: ERROR

Impact: Other

REP-00522: A default layout cannot be built because this report has no groups.

Cause: Insert&gt;Report Block was selected or a region was drawn using the Report Block tool in the Paper Layout editor before creating a query. A data source is required in order to create a default layout.

Action: Create one or more queries, then retry the operation.
Level: 1

Type: ERROR

Impact: Other

REP-00523: The Default Layout Style is invalid.

Cause: The Default Layout Style entered is not one of the valid options.

Action: Select a layout style from the list of values.
Level: 1

Type: ERROR

Impact: Other

REP-00524: The Print Direction is invalid.

Cause: The Repeat value entered is not one of the valid options.

Action: Select a value for Repeat from the list of values.
Level: 1

Type: ERROR

Impact: Other

REP-00525: The destination type is invalid.

Cause: The destination type entered for the system parameter DESTYPE is not one of the valid options. Possible causes of this error include the following: Case 1: An invalid value was entered for Destination Type in the Runtime Parameter Form. Case 2: An invalid value was entered for Initial Value in the Parameter Property Inspector for DESTYPE.

Action: Take the following actions to correct this error: If Case 1: Enter one of the valid values, Screen, File, Printer, Mail, or Sysout. If Case 2: Select a value for Initial Value from the list of the values.
Level: 1

Type: ERROR

Impact: Other

REP-00526: The initial value entered is longer than the parameter width.

Cause: The value entered is too long for the parameter on the Parameter Property Inspector. The possible causes of this error include the following: Case 1: The Initial Value entered is too big, given what was specified for the parameter's Width. Case 2: The Width entered is too small to contain the values to be entered for the parameter.

Action: Take the following actions to correct this error: If Case 1: Reenter the Initial Value, making sure that it is not wider than what is specified in Width. If Case 2: Delete the Initial Value. Move to the Width setting for the parameter and increase it such that it can contain the Initial Value specified. Reenter the Initial Value.
Level: 1

Type: ERROR

Impact: Other

REP-00527: A system parameter cannot be deleted.

Cause: An attempt was amde to delete a system parameter from the Parameter Property Inspector. This is not allowed.

Action: To remove the system parameter from the Runtime Parameter Form, suppress the display of the parameter.
Level: 1

Type: ERROR

Impact: Other

REP-00528: The data type value is invalid.

Cause: The value entered in Datatype for the parameter is not a valid data type.

Action: Select a value for Datatype from the list of values: Character, Number, or Date.
Level: 1

Type: ERROR

Impact: Data

REP-00529: The Type value is invalid.

Cause: The value entered in Type for the boilerplate is not a valid type.

Action: Select a value for Type from the list of values: Box, Graphic, Line, or Text.
Level: 1

Type: ERROR

Impact: Other

REP-00530: The file is too long. It will be truncated to fit.

Cause: An attempt was made to import a file into a field that has a maximum width less than the size of the file. Oracle Reports Builder only imported as much of the file as could fit in the field.

Action: To import the entire file, increase the size of the field.
Level: 1

Type: ERROR

Impact: Other

REP-00531: The Object Type is invalid.

Cause: In the Navigate to Object dialog box, the value entered for Object Type was invalid.

Action: Select a value from the list of values.
Level: 1

Type: ERROR

Impact: Other

REP-00532: There is no object of that type with this name.

Cause: The value entered in the Object Name field of the Navigate to Object dialog box does not correspond to an object of the specified type in the report.

Action: Verify the name and that the object is contained in the current report.
Level: 1

Type: ERROR

Impact: Other

REP-00533: Import is allowed only to a text entry field.

Cause: Import was selected from the Edit menu while in a non-text entry field (for example, a field that accepts only a number).

Action: Move to a text entry field to perform an import operation.
Level: 1

Type: ERROR

Impact: Other

REP-00534: Export is allowed only from a text entry field.

Cause: Export was selected from the Edit menu while in a non-text entry field (for example, a field that accepts only a number).

Action: Move to a text entry field to perform an export operation.
Level: 1

Type: ERROR

Impact: Other

REP-00535: No object named {0} exists in the database.

Cause: An attempt was made to perform an operation on a document stored in the database, but Oracle Reports Builder could not find the object.

Action: Verify the name and connection to the database where the document resides.
Level: 1

Type: ERROR

Impact: Other

REP-00536: An object in the database cannot be deleted without ownership.

Cause: An attempt was made to delete an object without ownership privileges.

Action: Request that the owner delete the object.
Level: 1

Type: ERROR

Impact: Other

REP-00537: An object in the database cannot be renamed without ownership.

Cause: An attempt was made to rename an object without ownership privileges.

Action: Request that the owner rename the object.
Level: 1

Type: ERROR

Impact: Other

REP-00538: An object named {0} already exists in the database.

Cause: The name entered for the object is already used for an existing object.

Action: Provide a different name for the object to avoid the conflict or delete the existing object.
Level: 1

Type: ERROR

Impact: Other

REP-00539: The default Parameter Form cannot fit in {0} pages.

Cause: The default Parameter Form is too big to fit on the number of pages allocated.

Action: In the report's Property Inspector, under Parameter Form Window, set the Number of Pages property to the maximum number of pages that the Parameter Form can span.
Level: 1

Type: ERROR

Impact: Other

REP-00540: The page size is too small for the default Parameter Form.

Cause: The current Form Width and Form Height settings are too small for the default Parameter Form.

Action: Increase the size of the Parameter Form pages in the Report Property Inspector by changing Form Width and Form Height. Alternatively, select Tools&gt;Default Parameter Form to default the Parameter Form and reduce its size by editing it in the Parameter Form editor.
Level: 1

Type: ERROR

Impact: Other

REP-00541: The source must be a report.

Cause: For Reports Runtime, Converter, or Tools&gt;File Conversion, something other than a report was specified as the source. These operations all require a report as their source.

Action: Specify a report as the source for the operation.
Level: 1

Type: ERROR

Impact: Other

REP-00542: No date masks have been specified as preferences.

Cause: While in the Parameter or Field Property Inspector of a parameter/field of Type Date, the List button was selected for Input Mask or Format Mask, but no masks are specified in the Date Mask list of the Preferences tab of the Tools Options dialog box.

Action: Enter a date format mask manually or go to the Preferences tab of the Tools Options dialog box and enter some date format masks in the Date Mask list.
Level: 1

Type: ERROR

Impact: Other

REP-00543: No number masks have been specified as preferences.

Cause: While in the Parameter or Field Property Inspector of a parameter/field of Type Number, the List button was selected for Input Mask or Format Mask, but no masks are specified in the Number Mask list of the Preferences tab of the Tools Options dialog box.

Action: Enter a number format mask manually or go to the Preferences tab of the Tools Options dialog and enter some number format masks in the Number Mask list.
Level: 1

Type: ERROR

Impact: Other

REP-00544: The online help system is not available.

Cause: Online help was not found. This may have happened because the help files are not installed or because of a help system error.

Action: Install Developer Tools during Oracle Fusion Middleware installation to install Oracle Reports Builder, which includes the Oracle Reports Online Help. Or, view the Reports Online Help on the Oracle Technology Network (OTN) at http://www.oracle.com/technology/products/reports/index.html.
Level: 1

Type: ERROR

Impact: Other

REP-00545: The number must be greater than 0.

Cause: Zero (0) was entered for Page Width, Page Height, or Logical Page Size in the Report Property Inspector.

Action: Enter a number greater than zero for Page Width, Page Height, or Logical Page Size.
Level: 1

Type: ERROR

Impact: Other

REP-00546: The parameter value is invalid.

Cause: In the Runtime Parameter Form, the parameter value entered was invalid.

Action: Retry the operation with a valid value for the parameter.
Level: 1

Type: ERROR

Impact: Other

REP-00548: An error occurred initializing Oracle Toolkit.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00549: The DESTYPE value is invalid.

Cause: An attempt was made to run a report in the background (that is, BATCH=YES), but DESTYPE specified was invalid for running in the background.

Action: Change the DESTYPE to File, Printer, Mail, or Sysout, or do not run the report with BATCH=YES.
Level: 1

Type: ERROR

Impact: Other

REP-00550: The parent group name is invalid.

Cause: The name entered does not identify a valid parent group in the report being defined.

Action: Select a group from the list of values.
Level: 1

Type: ERROR

Impact: Other

REP-00551: The parent group column is invalid.

Cause: The name entered does not identify a valid parent column in the report being defined. The column specified does not exist in the parent group.

Action: Select a column from the list of values. If the required column does not appear, add it to the SELECT statement of the parent query of the group specified in Parent Group.
Level: 1

Type: ERROR

Impact: Other

REP-00552: The child column name is invalid.

Cause: The name entered does not identify a valid child column in the report being defined. The column specified does not exist in the query.

Action: Select a column from the list of values. If the required column does not appear, add it to the SELECT statement of the query.
Level: 1

Type: ERROR

Impact: Other

REP-00553: The condition is invalid.

Cause: The Condition entered for the query is not one of the valid choices.

Action: Select a value from the list of values for Condition.
Level: 1

Type: ERROR

Impact: Other

REP-00554: The SQL clause value is invalid.

Cause: The value entered in SQL Clause is not one of the valid choices.

Action: Select a value from the list of values for SQL Clause: WHERE, HAVING, or START WITH.
Level: 1

Type: ERROR

Impact: Other

REP-00555: START WITH is Oracle-specific SQL syntax. The report will not run against a non-Oracle database.

Cause: The START WITH clause is only available with the Oracle database, but there is no connection or a non-Oracle database connection.

Action: Either run the report against an Oracle database or remove the START WITH clause before running it against a non-Oracle database.
Level: 1

Type: ERROR

Impact: Other

REP-00556: No data links are created. No foreign key in the child query {0} refers to a primary key in the parent query {1}.

Cause: An attempt was made to create a query-to-query link but no foreign key exists in the child query.

Action: Verify that the tables are accessible, and add the appropriate column constraints if desired.
Level: 1

Type: ERROR

Impact: Data

REP-00558: The query {0} created the lexical parameter {1}.

Cause: The specified query references one or more lexical parameters that did not exist.

Action: No action is needed. Oracle Reports Builder has already created the necessary lexical parameters.
Level: 1

Type: ERROR

Impact: Other

REP-00559: The query {0} has created the bind parameter {1}.

Cause: The specified query references one or more bind parameters that did not exist.

Action: No action is needed. Oracle Reports Builder has already created the necessary bind parameters.
Level: 1

Type: ERROR

Impact: Other

REP-00560: The group name value is invalid.

Cause: The group name entered in Group is not a valid group for the column. The group specified does not exist or cannot own the column.

Action: Create or modify the group such that it can own the column. A database column must be owned by the group associated with the query that selects it. A summary or formula column must be owned by a group that is below the groups that owns the columns being summarized in the group hierarchy (that is, the order of groups as they appear in the Data Model editor).
Level: 1

Type: ERROR

Impact: Other

REP-00561: The type value is invalid.

Cause: The value entered in Type for the column was not one of the valid choices.

Action: Select a value from the list of values for the column's Type: Formula, Summary, or Placeholder.
Level: 1

Type: ERROR

Impact: Other

REP-00562: The column data type value is invalid.

Cause: The value entered in Datatype was not one of the valid choices.

Action: Select a value from the list of values for Datatype.
Level: 1

Type: ERROR

Impact: Data

REP-00563: The data type value is invalid.

Cause: The value entered in Datatype was not one of the valid choices.

Action: Select a value from the list of values for Datatype: Ascending, Descending, or blank.
Level: 1

Type: ERROR

Impact: Data

REP-00564: The file type value is invalid.

Cause: The file type value entered in Read From File was not one of the valid types.

Action: Select a file type from the list of values for Read from File.
Level: 1

Type: ERROR

Impact: Other

REP-00565: The function value is invalid.

Cause: The function entered for Function was not one of the valid choices.

Action: Select one of the functions from the list of values.
Level: 1

Type: ERROR

Impact: Other

REP-00566: The database column cannot be deleted.

Cause: An attempt was made to delete a column with a Type of Database.

Action: Remove the column from the SELECT list of the query that selects it and the column will be deleted automatically.
Level: 1

Type: ERROR

Impact: Other

REP-00567: The summary source value is invalid.

Cause: The column entered in Source for the summary was not one of the valid choices. The possible causes of this error include the following: Case 1: The column does not exist. Case 2: The data type of the Source is Character or Date. Numeric functions (such as Percent, Sum, or Average) require a data type of Number.

Action: Take the following actions to correct this error: If Case 1: Select a column from the list of values for the function. If Case 2: Enter the name of another column in Source that is of data type Number.
Level: 1

Type: ERROR

Impact: Other

REP-00568: The Value if Null value is invalid.

Cause: The value of Value if Null in the Column Property Inspector is invalid for that column. For example, if data type of the column is Number, and a character string was sepcified in Value if Null.

Action: Specify a valid value for Value if Null.
Level: 1

Type: ERROR

Impact: Other

REP-00580: The filter type value is invalid.

Cause: The value entered for Type under Filter was not one of the valid choices.

Action: Select one of the filter types from the list of values.
Level: 1

Type: ERROR

Impact: Other

REP-00581: This is the only group of query {0}, and may not be deleted.

Cause: An attempt was made to delete a group that is the only one of the query. Each query must have at least one group.

Action: To delete the group, delete the group's query.
Level: 1

Type: ERROR

Impact: Other

REP-00582: A group cannot be moved out of its query.

Cause: An attempt was made to move a group between queries. Groups can only be moved within the set of groups belonging to the same query.

Action: Create a group similar to the one that was attempt to be moved under the other query, if possible.
Level: 1

Type: ERROR

Impact: Other

REP-00583: The SQL SELECT Statement is invalid.

Cause: The SQL SELECT statement entered was not valid.

Action: Check the SELECT statement for errors and correct them. For more information, see the SQL Language Reference Manual.
Level: 1

Type: ERROR

Impact: Other

REP-00584: Lexical parameters are not permitted in external queries.

Cause: A lexical reference was made in an external query. This is not allowed.

Action: Delete the reference altogether or, if possible, change it to a bind reference.
Level: 1

Type: ERROR

Impact: Other

REP-00585: The arent group {0} for child query {1} does not exist.

Cause: A query was deleted without deleting references to its groups in data links. This usually happens when a query is deleted without cascading the deletion to its associated objects.

Action: Update the data link in the child query.
Level: 1

Type: ERROR

Impact: Other

REP-00586: Adding this data link will create a cycle.

Cause: The group specified as the parent group for the data link is not eligible to be a parent because it is, directly or indirectly, a child of the query to which it is linked.

Action: If possible, move the group such that it is not a child of the query and therefore eligible to be its parent group.
Level: 1

Type: ERROR

Impact: Data

REP-00587: The PL/SQL group filter condition value is invalid.

Cause: Condition was selected for Filter Type, but no PL/SQL condition was entered.

Action: Enter the PL/SQL or change the Filter Type.
Level: 1

Type: ERROR

Impact: Other

REP-00588: The PL/SQL column formula value is invalid.

Cause: Formula was selected as the column's Type, but no PL/SQL for the formula was entered.

Action: Create a formula or change the column's Type.
Level: 1

Type: ERROR

Impact: Other

REP-00590: Only {0} pages were formatted. The last page is shown.

Cause: In the Previewer, an attempt was made to go to a page number that is larger than the total number of pages formatted.

Action: No action is needed. Do not attempt scroll down from the last page of the report.
Level: 1

Type: ERROR

Impact: Other

REP-00591: The first page is already shown.

Cause: In the Previewer, First was selected on the first page of the report.

Action: No action is needed. Do not attempt to scroll up from the first page of the report.
Level: 1

Type: ERROR

Impact: Other

REP-00592: The last page is already show.

Cause: In the Previewer, Last was selected on the last page of the report.

Action: No action is needed. Do not attempt to scroll down from the last page of the report.
Level: 1

Type: ERROR

Impact: Other

REP-00593: Page {0} is the current page.

Cause: In the Previewer, the page number of the current page was entered.

Action: Enter a different page number and select Go To.
Level: 1

Type: ERROR

Impact: Other

REP-00594: No report output is generated.

Cause: The report generated no output.

Action: Check the accompanying messages for errors in the data model and layout. If the problem persists, contact Oracle Support Services for assistance.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00595: The report definition was modified. Rerunning report.

Cause: A report was run and while its output was still in the Previewer, the report definition was modified. The report is rerun to reflect the most recent changes

Action: Save the changes, close the Previewer, and run the report again.
Level: 1

Type: ERROR

Impact: Other

REP-00596: A page number cannot be greater than {0} or less than 1.

Cause: An invalid value was entered for the Page Number setting on the Field Property Inspector for a Parameter Form field. The most likely cause is that values entered were zero, a negative number, or a number that is larger than the largest allowable value.

Action: Enter a number within the range shown in the message.
Level: 1

Type: ERROR

Impact: Other

REP-00597: This operation is invalid, since it moves objects out of bounds.

Cause: An attempt was made to move editor objects in such a way that they would be off the screen.

Action: Retry the operation so that it will not move objects off the screen.
Level: 1

Type: ERROR

Impact: Other

REP-00598: The anchor end point is out of the boundary of the object.

Cause: In moving an anchor, the end point was moved off of the boundary of the object it anchors.

Action: Move the anchor such that its endpoint is still on the boundary of the object.
Level: 1

Type: ERROR

Impact: Other

REP-00599: This text boilerplate is not editable.

Cause: An attempt was made to edit the text of a file link text boilerplate object while it was displayed in the Paper Layout view.

Action: To edit the text of a file link text boilerplate object, exit the report and edit the file containing the boilerplate text using a text editor.
Level: 1

Type: ERROR

Impact: Other

REP-00600: No list of values is available for this field.

Cause: An attempt was made to access a list of values for the current field when none is available.

Action: No action necessary.
Level: 1

Type: ERROR

Impact: Other

REP-00601: The list of values for this field is empty.

Cause: An attempt was made to select from a list of values and the list of values has no values. In order for some lists of values to contain values, another part of the report must be built first. For example, if a list of values is made up solely of column names and the data model is not complete, this error may display.

Action: Build the report fully. If the error persists, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00602: The accessible tables cannot be queried.

Cause: The dictionary view of accessible tables is not present or not available.

Action: See the system administrator.
Level: 1

Type: ERROR

Impact: Other

REP-00603: Table {0} cannot be described.

Cause: The dictionary view of accessible tables is not present or not available.

Action: See the system administrator.
Level: 1

Type: ERROR

Impact: Other

REP-00604: The SELECT statement cannot be built.

Cause: The Table and Columns Names dialog box was accepted without anything selected with which to build the SELECT statement.

Action: Select a table and, if desired, columns or the SELECT columns FROM table option, and then accept the dialog box. To exit the dialog box without building a SELECT statement, click Close.
Level: 1

Type: ERROR

Impact: Other

REP-00606: Link file {0} cannot be read.

Cause: Case 1: The file specified in the Source Filename property for the file link boilerplate object cannot be found or its format does not match that specified in the File Format property. Case 2: The REPORTS_DEFAULT_DISPLAY environment variable is set to YES and the image format used is not supported.

Action: Take the following actions to correct this error: If Case 1: Verify that the file is stored in the specified directory under the specified name, and that it is saved in the specified format. If it is not, change the directory, file name, or format as appropriate. If Case 2: Verify that the image format is one of the supported formats: GIF, JPEG, JPG, PNG, BMP.
Level: 1

Type: ERROR

Impact: Other

REP-00607: Run-only file {0} may not be opened.

Cause: An attempt was made to open a runfile (extension .rep). Runfiles cannot be opened, they can only be executed.

Action: Open the report definition that is associated with the .rep file. It should have an extension of .rdf.
Level: 1

Type: ERROR

Impact: Other

REP-00608: The Source Type is invalid.

Cause: Convert was selected from the File menu and the Source Type specified is not valid.

Action: Select a valid Source Type from the list of values.
Level: 1

Type: ERROR

Impact: Other

REP-00609: The Destination Type is invalid.

Cause: Convert was selected from the File menu and the Destination Type specified is not valid.

Action: Select the Destination Type from the list of values.
Level: 1

Type: ERROR

Impact: Other

REP-00610: An error occurred while attempting to print the screen. Verify that log file {0} is accessible.

Cause: Oracle Reports Builder attempted to write the contents of the screen to the file printdef.dat but could not locate the file.

Action: To determine the proper location for printdef.dat, see the installation instructions.
Level: 1

Type: ERROR

Impact: Other

REP-00611: The Destination Type value is not valid.

Cause: In the Runtime Parameter Form, the value provided for Destination Type that was not valid.

Action: Specify a value of Screen, File, Printer, or Mail for Destination Type.
Level: 1

Type: ERROR

Impact: Other

REP-00612: The date mask value is invalid.

Cause: The date mask entered does not correspond to any of the valid date masks.

Action: Verify the date mask format. For more information, see the date and time format mask information in the Building Reports manual.
Level: 1

Type: ERROR

Impact: Other

REP-00613: The Format Mask value does not match mask {0}.

Cause: The mask entered in Format Mask is not a valid mask. The possible causes of this error include the following: Case 1: The string entered as a mask contained invalid characters. Case 2: A number format mask was entered for a field with data type of Character.

Action: Take the following actions to correct this error: If Case 1: Select a value from the list of values. For more information, see the date and time format mask information in the Building Reports manual. If Case 2: Change the data type of the field to be Number, if possible. If the field is supposed to be Character data type and cannot be changed, a format mask cannot be specified for it.
Level: 1

Type: ERROR

Impact: Other

REP-00614: There is no window active for the Find and Replace action.

Cause: A Find and Replace operation was attempted using the Find And Replace dialog box, but the cursor was not positioned in an active Oracle Reports Builder window.

Action: Position the cursor in a text entry field before performing a Find and Replace operation.
Level: 1

Type: ERROR

Impact: Other

REP-00615: Find and Replace is valid only for a text entry field.

Cause: A Find and Replace operation was attempted using the Find And Replace dialog box, but the cursor was not positioned positioned in a text entry field. Find and Replace operations are valid only in text entry fields.

Action: Position the cursor in a entry field before performing a Find and Replace operation.
Level: 1

Type: ERROR

Impact: Other

REP-00616: Text cannot be replaced in an uneditable region.

Cause: Using the Find And Replace dialog box, text replacement was attempted in an inaccessible field.

Action: Replace text only in editable regions.
Level: 1

Type: ERROR

Impact: Other

REP-00617: The Runtime Parameter Form is already open. To run a new one, close the old one and run again.

Cause: An attempt was made to run a report with the Runtime Parameter Form already open.

Action: Close the currently open Runtime Parameter Form and try running again.
Level: 1

Type: ERROR

Impact: Other

REP-00619: A report cannot be run without a layout.

Cause: An attempt was made to run the report with no layout.

Action: Create a layout, then run the report.
Level: 1

Type: ERROR

Impact: Other

REP-00621: The Vertical Elasticity value is invalid.

Cause: The value entered for the object's Vertical Elasticity was not one of the valid values.

Action: Select a value from the list of values.
Level: 1

Type: ERROR

Impact: Other

REP-00622: The Horizontal Elasticity value is invalid.

Cause: The value entered for the object's Horizontal Elasticity was not one of the valid values.

Action: Select a value from the list of values.
Level: 1

Type: ERROR

Impact: Other

REP-00623: The Print Condition Type value is invalid.

Cause: The value entered for the Type of the Print Condition was not one of the valid values.

Action: Select a value from the list of values.
Level: 1

Type: ERROR

Impact: Other

REP-00624: The Print Condition Object value is invalid.

Cause: The value entered for the Object of the Print Condition was not one of the valid values.

Action: Select a value from the list of values.
Level: 1

Type: ERROR

Impact: Other

REP-00625: The Text Alignment value is invalid.

Cause: The value entered for Alignment was not one of the valid values. The value is not valid given the data type of the object. Flush/Left, Flush/Center, and Flush/Right are only valid for fields with data type of Character.

Action: Select a value from the list of values.
Level: 1

Type: ERROR

Impact: Other

REP-00626: The coordinate position value is invalid.

Cause: The x or y coordinate entered was not in the valid range for coordinates. Coordinates cannot be negative numbers.

Action: Enter a coordinate that is in the valid range.
Level: 1

Type: ERROR

Impact: Other

REP-00627: The object height or width must be a positive integer.

Cause: The Width or Height value entered was not a positive, whole number.

Action: Enter a positive, whole number.
Level: 1

Type: ERROR

Impact: Other

REP-00630: The value must be between {0} and {1}.

Cause: The number entered was too large or too small.

Action: Specify a number that is within the range shown in the message.
Level: 1

Type: ERROR

Impact: Other

REP-00631: The string must be no longer than {0} characters.

Cause: The string entered was too large.

Action: Enter a string that is smaller than the number of characters shown in the message.
Level: 1

Type: ERROR

Impact: Other

REP-00632: The value already exists in the list.

Cause: An attempt was made to add an item to a list, but the item was previously added to the list. For example, if an attempt was made to add lib1 to the report's Attached PL/SQL Library list, when lib1 was already found in the Attached PL/SQL Library list, this error displays.

Action: Once an item has been added to a list, do not attempt to add it again.
Level: 1

Type: ERROR

Impact: Other

REP-00633: No value is specified.

Cause: An attempt was made to perform a list operation on an item, but no item was specified. For example, if an attempt was made to add a PL/SQL library to the report's Attached PL/SQL Library list, but the PL/SQL Library field in the Attached PL/SQL Libraries dialog box was left blank and the Add button selected, this error displays.

Action: Specify the item to add in the appropriate field before choosing a button.
Level: 1

Type: ERROR

Impact: Other

REP-00634: The destination name must be shorter than {0} characters.

Cause: The destination specified (probably a file name) was too long.

Action: Specify a destination that it is of valid length.
Level: 1

Type: ERROR

Impact: Other

REP-00635: The value does not exist in the list.

Cause: The value specified was not in the list of valid choices.

Action: Specify one of the valid choices in the list. If possible, use the list of values to ensure that it is a valid choice.
Level: 1

Type: ERROR

Impact: Other

REP-00636: Property name {0} must be no longer than {1} characters. It will be truncated.

Cause: The string specified was longer than is allowable. It will be truncated.

Action: Specify a shorter string.
Level: 1

Type: ERROR

Impact: Other

REP-00637: Property name {0} must be no longer than {1} characters.

Cause: The file name specified was longer than is allowable.

Action: Specify a shorter file name.
Level: 1

Type: ERROR

Impact: Other

REP-00639: Set a valid DISPLAY value when REPORTS_DEFAULT_DISPLAY is set to NO.

Cause: REPORTS_DEFAULT_DISPLAY was set to NO and DISPLAY variable was not set.

Action: Specify a valid value for DISPLAY when REPORTS_DEFAULT_DISPLAY is set to NO.
Level: 1

Type: ERROR

Impact: Other

REP-00640: The field source value is invalid.

Cause: The Source value specified was invalid.

Action: Select a value from the list of values.
Level: 1

Type: ERROR

Impact: Other

REP-00650: The source group value is invalid.

Cause: The group name specified in Source for the repeating frame was invalid.

Action: Select a value from the list of values.
Level: 1

Type: ERROR

Impact: Other

REP-00651: The Print Direction value is invalid.

Cause: The Print Direction specified was not one of the valid values (Across, Across/Down, Down, Down/Across, and Matrix Cell).

Action: Select a value from the list of values.
Level: 1

Type: ERROR

Impact: Other

REP-00652: The Vertical Spacing value is invalid.

Cause: The Vertical Spacing specified was not a valid value.

Action: Enter zero or a positive integer for Vertical Spacing.
Level: 1

Type: ERROR

Impact: Other

REP-00653: The Horizontal Spacing value is invalid.

Cause: The Horizontal Spacing specified was not a valid value.

Action: Enter zero or a positive integer for Horizontal Spacing.
Level: 1

Type: ERROR

Impact: Other

REP-00654: The Maximum Records per Page value is invalid.

Cause: The Maximum Records per Page specified was not a valid value.

Action: Enter blank or a positive integer for Maximum Records per Page.
Level: 1

Type: ERROR

Impact: Other

REP-00655: The Minimum Widow Records value is invalid.

Cause: The Minimum Widow Records specified was not a valid value.

Action: Enter blank or a positive integer for Minimum Widow Records.
Level: 1

Type: ERROR

Impact: Other

REP-00660: The button source value is invalid.

Cause: Multimedia Column was selected as the source for the button action, but the source column was either not specified or invalid.

Action: Specify a valid source column for the button action, containing sounds, video, or images.
Level: 1

Type: ERROR

Impact: Other

REP-00661: The button source value is invalid.

Cause: Multimedia File was selected as the source for the button action, but the source file was either not specified or invalid.

Action: Specify a valid source file for the button action, containing sounds, video, or images.
Level: 1

Type: ERROR

Impact: Other

REP-00662: The button icon value is invalid.

Cause: Icon was selected as the button face, but the icon name was invalid.

Action: Enter the name of a valid icon file in the text field provided. Include all necessary path information.
Level: 1

Type: ERROR

Impact: Other

REP-00670: The boilerplate type value is invalid.

Cause: The Type specified for the boilerplate was not one of the valid values.

Action: Select a Type from the list of values: Box, Line, Graphic, and Text.
Level: 1

Type: ERROR

Impact: Other

REP-00671: The link file name value is invalid.

Cause: The file to which the file link boilerplate object was linked is not a valid file.

Action: In the Property Inspector for the File Link boilerplate object, check that the Source Filename property is set to an existing file in the current directory.
Level: 1

Type: ERROR

Impact: Other

REP-00672: The Minimum Widow Lines value is invalid.

Cause: The Minimum Widow Lines specified was not a valid value.

Action: Enter blank or a positive integer for Minimum Widow Lines.
Level: 1

Type: ERROR

Impact: Other

REP-00680: The anchoring object name value is invalid.

Cause: The object name entered in the Anchored To field of the Anchor Position dialog box was not the name of an object to which this object can be anchored.

Action: Select an object name for Anchored To from the list of values.
Level: 1

Type: ERROR

Impact: Other

REP-00681: The Edge value is invalid.

Cause: The Edge specified was not one of the valid values (Top, Left, Right, and Bottom).

Action: Select a value for Parent Edge or Object Edge from the list of values.
Level: 1

Type: ERROR

Impact: Other

REP-00682: The anchor point must be a percentage between 0 and 100.

Cause: The % specified was not in the valid range (0 to 100).

Action: Enter a value in the valid range for %.
Level: 1

Type: ERROR

Impact: Other

REP-00690: The starting page number value is invalid.

Cause: Start At was left blank.

Action: Enter zero or a positive integer for Start At.
Level: 1

Type: ERROR

Impact: Other

REP-00691: The page increment value is invalid.

Cause: Increment By was blank.

Action: Enter zero or a positive whole number for Increment By.
Level: 1

Type: ERROR

Impact: Other

REP-00692: The page number reset value is invalid.

Cause: Reset At was left blank.

Action: Select a repeating frame name or &Report from the list of values to indicate where to reset the page number to its Start At value.
Level: 1

Type: ERROR

Impact: Other

REP-00700: The color value is invalid.

Cause: The color specified was not one of the valid choices.

Action: Select a color for the field from the list of values.
Level: 1

Type: ERROR

Impact: Other

REP-00701: The pattern value is invalid.

Cause: The pattern specified was not one of the valid choices.

Action: Select a pattern for the field from the list of values.
Level: 1

Type: ERROR

Impact: Other

REP-00702: The pen width value is invalid.

Cause: The pen width specified was not one of the valid choices.

Action: Select a pen width from the list of values.
Level: 1

Type: ERROR

Impact: Other

REP-00703: The font value is invalid.

Cause: The font specified was not one of the valid choices.

Action: Select a font from the list of values.
Level: 1

Type: ERROR

Impact: Other

REP-00704: The text style value is invalid.

Cause: The text style specified was not one of the valid styles.

Action: Select one of the styles from the list of values.
Level: 1

Type: ERROR

Impact: Other

REP-00705: The text weight value is invalid.

Cause: The text weight specified was not one of the valid weights.

Action: Select one of the weights from the list of values.
Level: 1

Type: ERROR

Impact: Other

REP-00706: The text size value is invalid.

Cause: The point size specified was not one of the valid choices.

Action: Select a valid point size from the list of values.
Level: 1

Type: ERROR

Impact: Other

REP-00707: The text spacing value is invalid.

Cause: The spacing value specified was not in the valid range.

Action: Enter a number in the valid range.
Level: 1

Type: ERROR

Impact: Other

REP-00708: The character mode attribute value is invalid.

Cause: The character mode attribute specified was not valid. The values specified in Character Mode Attribute must be defined in the printer definition. To have these attributes appear in the list of values, they must also be listed in VISUAL_PREFS in the preferences file.

Action: Select the desired values from the list of values. If the desired value is not in the list of values, check the printer definition to verify if the value is a valid one.
Level: 1

Type: ERROR

Impact: Other

REP-00709: Sysout is only valid in batch mode.

Cause: Sysout was specified as the destination type when not running the report in batch mode. The possible causes of this error include the following: Case 1: Sysout was specified for DESTYPE in the Runtime Parameter Form. Case 2: Sysout was specified as the Initial Value for DESTYPE and was accepted when not running in batch mode. This may occur inadvertently when the Hide Parameter Form preference is checked.

Action: Take the following actions to correct this error: If Case 1: Run the report again, but enter a DESTYPE of something other than Sysout unless running in batch mode. If Case 2: Change the Initial Value for DESTYPE to something else or change the DESTYPE to something other than Sysout in the Runtime Parameter Form. If the Initial Value is left as Sysout, do not run in non-batch mode with Hide Parameter Form checked.
Level: 1

Type: ERROR

Impact: Other

REP-00710: The printer description file cannot be found.

Cause: Oracle Reports Builder could not find the printer description file specified for DESFORMAT.

Action: Specify a valid printer description file for DESFORMAT (for example, dflt).
Level: 1

Type: ERROR

Impact: Other

REP-00711: The destination type must be File, Printer, or Mail when printing from the Previewer.

Cause: The Print button was selected in the Previewer, but DESTYPE was restricted to a value other than File, Printer, or Mail.

Action: Ensure that DESTYPE can be set to one of the valid values before attempting to print from the Previewer.
Level: 1

Type: ERROR

Impact: Other

REP-00712: No printer is specified.

Cause: An attempt was made to print a report, without a printer name specified in either DESNAME or in the Printer Chooser dialog box.

Action: Specify a valid printer name using DESNAME. If the same printer is often used, enter the printer name in the Printer Chooser dialog box. Remember that entering a printer name using DESFORMAT will override the printer name set in the Printer Chooser dialog box.
Level: 1

Type: ERROR

Impact: Other

REP-00713: The printer name {0} specified by parameter {1} is invalid.

Cause: An attempt was made to generate a report, without a valid printer name specified in DESFORMAT (if DESTYPE was File or Mail) or DESNAME (if DESTYPE was Printer).

Action: Specify a valid printer name for DESFORMAT if DESTYPE was File or Mail, or a valid printer name for DESNAME if DESTYPE was Printer.
Level: 1

Type: ERROR

Impact: Other

REP-00714: The mail destination value is invalid.

Cause: An attempt was made to mail report output to another user, but did not specify a valid username for DESNAME.

Action: Specify a valid username for DESNAME.
Level: 1

Type: ERROR

Impact: Other

REP-00715: A trace file must be specified when tracing.

Cause: Trace mode or trace options were specified without specifying a trace file.

Action: Specify a trace file.
Level: 1

Type: ERROR

Impact: Other

REP-00716: The option specified for tracing is invalid.

Cause: Invalid trace options were specified.

Action: Respecify trace options. For more information about trace options, see the Publishing Reports to the Web manual.
Level: 1

Type: ERROR

Impact: Other

REP-00717: Options cannot be set or unset if not tracing.

Cause: An attempt was made to set or unset trace options while not tracing.

Action: Begin tracing before attempting to set or unset options.
Level: 1

Type: ERROR

Impact: Other

REP-00718: Trace break information cannot be traced with Reports Runtime.

Cause: An attempt was made to trace breaks while running the report using Reports Runtime.

Action: Do not specify the Break option when using Reports Runtime.
Level: 1

Type: ERROR

Impact: Other

REP-00719: Trace file {0} can be written to.

Cause: A trace file was specified that does not have write permission.

Action: Verify the trace file name is valid.
Level: 1

Type: ERROR

Impact: Other

REP-00720: The repeating frame value is invalid.

Cause: The repeating frame specified as the Vertical or Horizontal Frame in the Matrix Property Inspector is not valid.

Action: Select a repeating frame name from the list of values.
Level: 1

Type: ERROR

Impact: Other

REP-00721: The cross product group value is invalid.

Cause: The group entered for Cross Product Group in the Matrix Property Inspector is not valid.

Action: Select a group name from the list of values.
Level: 1

Type: ERROR

Impact: Other

REP-00723: Uncompiled program units exist, possibly due to no connection to the database.

Cause: An attempt was made to convert a report or load an old report, containing PL/SQL which needed to be recompiled.

Action: Load the report using Oracle Reports Builder, connect to database, and recompile the DE program units.
Level: 1

Type: ERROR

Impact: Other

REP-00724: The value of column {0} cannot be retrieved.

Cause: An attempt was made to get the value of the specified column by either issuing a command from the command line of the PL/SQL Interpreter or by executing a stand-alone PL/SQL program unit. A column value can only be retrieved during report execution.

Action: Do not attempt to use the PL/SQL Interpreter or a PL/SQL program unit to get the value of a column when the report has suspended execution (for example, at a breakpoint). Use an alternate method, such as one of the report-level triggers, to obtain the column value.
Level: 1

Type: ERROR

Impact: Other

REP-00725: The value of column {0} cannot be set.

Cause: An attempt was made to set the value of the specified column by either issuing a command from the command line of the PL/SQL Interpreter or by executing a stand-alone PL/SQL program unit. A column value can only be set during report execution.

Action: Do not attempt to use the PL/SQL Interpreter or a PL/SQL program unit to set the value of a column when the report has suspended execution (for example, at a breakpoint). Use an alternate method, such as one of the report-level triggers, to set the column value.
Level: 1

Type: ERROR

Impact: Other

REP-00726: The value of parameter {0} cannot be retrieved.

Cause: An attempt was made to get the value of the specified parameter by either issuing a command from the command line of the PL/SQL Interpreter or by executing a stand-alone PL/SQL program unit. A parameter value can only be retrieved during Parameter Form execution.

Action: Do not attempt to use the PL/SQL Interpreter or a PL/SQL program unit to get the value of a parameter when the report has suspended execution (for example, at a breakpoint). Use an alternate method, such as one of the report-level triggers, to obtain the parameter value.
Level: 1

Type: ERROR

Impact: Other

REP-00727: The value of parameter {0} cannot be set.

Cause: An attempt was made to set the value of the specified parameter by either issuing a command from the command line of the PL/SQL Interpreter or by executing a stand-alone PL/SQL program unit. A parameter value can only be set during Parameter Form execution.

Action: Do not attempt to use the PL/SQL Interpreter or a PL/SQL program unit to set the value of a parameter when the report has suspended execution (for example, at a breakpoint). Use an alternate method, such as one of the report-level triggers, to set the parameter value.
Level: 1

Type: ERROR

Impact: Other

REP-00728: Column {0} may not be referenced by parameter triggers.

Cause: An attempt was made to reference a column in a parameter-related trigger (Before Form, After Form, Validation), which is not allowed.

Action: Remove the references from the parameter-related triggers and add them to the Before Report trigger.
Level: 1

Type: ERROR

Impact: Other

REP-00729: The program unit {0} of size {1} bytes is too big to be loaded for the current platform at the limit of {2}.

Cause: The program unit was created on another operating platform and it too large to be loaded into the current operating platform.

Action: Reduce the size of the PL/SQL program unit.
Level: 1

Type: ERROR

Impact: Other

REP-00730: The bind variable is not defined.

Cause: A bind reference was made to a parameter or column that has not been defined yet.

Action: Create the parameter definition or column before making a bind reference to it. Or, attempt to use a lexical reference rather than a bind reference.
Level: 1

Type: ERROR

Impact: Other

REP-00732: An error occurred destroying the program unit.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00733: The specified name already exists.

Cause: An attempt was made to create a PL/SQL subprogram whose name is identical to an existing subprogram stored in the report.

Action: Rename the new subprogram so that it does not conflict with any existing subprograms.
Level: 1

Type: ERROR

Impact: Other

REP-00734: No argument is allowed.

Cause: The PL/SQL function or procedure entered requires arguments in a PL/SQL field that does not allow PL/SQL with arguments--for example, in a Format Trigger field, a Formula field, or as a group filter.

Action: Remove the arguments from the PL/SQL source.
Level: 1

Type: ERROR

Impact: Other

REP-00735: Program unit cannot be loaded.

Cause: Oracle Reports Builder could not load the entire program unit. It could be that the program unit references one or more objects stored in the database, but these objects were not found.

Action: Verify the connection to the correct database, and ensure that the program unit is making the correct references.
Level: 1

Type: ERROR

Impact: Other

REP-00736: Uncompiled program units exist.

Cause: An attempt was made to convert a report, or load an old report, containing PL/SQL that needed to be recompiled.

Action: Load the report using Oracle Reports Builder and modify the program units.
Level: 1

Type: ERROR

Impact: Other

REP-00737: The return type {0} is invalid.

Cause: The PL/SQL entered does not have the appropriate return type.

Action: Change the return type of the function to the one specified in the message.
Level: 1

Type: ERROR

Impact: Other

REP-00738: A function is required.

Cause: Something other than a function was entered where a function is required.

Action: Enter a function.
Level: 1

Type: ERROR

Impact: Other

REP-00739: Compiled PL/SQL from other platform cannot be executed.

Cause: An attempt was made to run a report on a platform that is not the same as the platform on which the PL/SQL in the report was compiled. The report does not contain the PL/SQL source and, as a result, Oracle Reports Builder could not recompile the PL/SQL on the current platform.

Action: Run the report on the original platform where the PL/SQL was compiled. Alternatively, obtain a copy of the source report with the source PL/SQL and recompile it from the current platform.
Level: 1

Type: ERROR

Impact: Other

REP-00740: An anchor cannot be anchored with another object.

Cause: An attempt was made to anchor an anchor to another layout object, or anchor a layout object to an anchor.

Action: Remove any anchors of anchors with other layout objects.
Level: 1

Type: ERROR

Impact: Other

REP-00741: A matrix cannot be anchored with another object.

Cause: An attempt was made to anchor a matrix object to another layout object, or anchor a layout object to a matrix object.

Action: Remove any anchors of matrix objects with other layout objects.
Level: 1

Type: ERROR

Impact: Other

REP-00742: A margin cannot be anchored with another object.

Cause: An attempt was made to anchor the margin to a layout object, or anchor a layout object to the margin.

Action: Remove any anchors of the margin to layout objects.
Level: 1

Type: ERROR

Impact: Other

REP-00743: A matrix repeating frame cannot be anchored with another object.

Cause: An attempt was made to anchor a matrix repeating frame with a Print Direction of Down or Across to another layout object.

Action: Remove any anchors of matrix repeating frames with Print Directions of Down or Across to other layout objects.
Level: 1

Type: ERROR

Impact: Other

REP-00744: An anchor must have different parent and child objects.

Cause: An attempt was made to create an anchor whose parent and child objects are the same; that is, anchor an object to itself.

Action: Ensure that all anchors have different parent and child objects.
Level: 1

Type: ERROR

Impact: Other

REP-00745: An object cannot be anchored more than once.

Cause: An attempt was made to create two anchors between the same two layout objects.

Action: Ensure that only one anchor exists between the same two layout objects.
Level: 1

Type: ERROR

Impact: Other

REP-00746: The PL/SQL references an object that does not exist.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00747: A Before Form trigger cannot reference a report column.

Cause: The Before Form trigger for the report references a column in the report, which is not allowed.

Action: Remove any column references from the Before Form trigger. To set the value of a column, do it from the Before Report trigger.
Level: 1

Type: ERROR

Impact: Other

REP-00748: A parameter trigger cannot reference a report column.

Cause: A Validation trigger for a parameter references one or more columns in the report, which is not allowed.

Action: Remove any column references in the Validation trigger of the Parameter Property Inspector.
Level: 1

Type: ERROR

Impact: Other

REP-00749: An After Form trigger cannot reference a report column.

Cause: The After Form trigger for the report references a column in the report, which is not allowed.

Action: Remove any column references in the After Form trigger. To set the value of a column, do it from the Before Report trigger.
Level: 1

Type: ERROR

Impact: Other

REP-00750: An error occurred closing the PL/SQL library.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00751: An error occurred accessing program units from PL/SQL library.

Cause: An abnormal condition was encountered. To save changes made to the PL/SQL library, consider saving it under a different name.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00752: The PL/SQL library cannot be saved.

Cause: An abnormal condition was encountered. To save changes made to the PL/SQL library, consider saving it under a different name.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00753: An error occurred attaching PL/SQL library {0}.

Cause: An attempt was made to attach an invalid PL/SQL library. This could happen because the PL/SQL library is corrupted, or because the file or object specified does not contain a PL/SQL library.

Action: Verify that the file or object specified contains a valid PL/SQL library.
Level: 1

Type: ERROR

Impact: Other

REP-00754: An error occurred inserting program units into a PL/SQL library.

Cause: An attempt was made to save a program unit into a corrupted PL/SQL library, or a file or object that is not a PL/SQL library.

Action: Verify the file or object specified contains a valid PL/SQL library and consider saving the current program unit.
Level: 1

Type: ERROR

Impact: Other

REP-00755: An error occurred opening PL/SQL library {0}.

Cause: An attempt was made to open a corrupted PL/SQL library, or a file or object that is not a PL/SQL library.

Action: Verify that the file or object contains a valid PL/SQL library.
Level: 1

Type: ERROR

Impact: Other

REP-00756: PL/SQL library {0} cannot be found.

Cause: An attempt was made to attach a PL/SQL library that does not exist, or to open a report with one or more attached PL/SQL libraries that were not found.

Action: Verify that the file or object exists. If the object is a report, reattach the PL/SQL library.
Level: 1

Type: ERROR

Impact: Other

REP-00757: The external location spec cannot be created.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00758: PL/SQL library {0} is already in use.

Cause: An attempt was made to attach a PL/SQL library that has the same name as another PL/SQL library that is already attached. This could happen if a file was renamed that contains a PL/SQL library, but the internal name recognized by Oracle Reports Builder was not changed.

Action: Save the PL/SQL library under a different name.
Level: 1

Type: ERROR

Impact: Other

REP-00759: One or more PL/SQL libraries have been modified since the report was saved; the PL/SQL will be recompiled.

Cause: An attempt was made to open or run a report that references one or more PL/SQL libraries, and part or all of the PL/SQL has been modified but not compiled since the report was last saved.

Action: No action is necessary; Oracle Reports Builder will recompile the PL/SQL.
Level: 1

Type: ERROR

Impact: Other

REP-00760: A print document session is currently in process.

Cause: From the File menu, Administration Report was already selected to produce a report on one or more reports.

Action: Finish producing the current report on reports, then try again to run another report on reports.
Level: 1

Type: ERROR

Impact: Other

REP-00761: The resource for printing the report cannot be opened.

Cause: Oracle Reports Builder cannot open the reports that document other reports for printing.

Action: Verify that the reports that document other reports (shipped with Oracle Reports Builder) are located in the proper directory. For details on the exact location of these reports, see the installation instructions.
Level: 1

Type: ERROR

Impact: Other

REP-00762: The user ID for the interoffice login is invalid.

Cause: An attempt was made to save report output to the interoffice repository, but a valid connect string was not specified for the interoffice document server.

Action: Specify a valid connect string for the interoffice document server.
Level: 1

Type: ERROR

Impact: Other

REP-00763: The interoffice client {0} cannot be launched.

Cause: An attempt was made to launch the interoffice client, but it failed to run.

Action: Verify that the interoffice client is properly installed.
Level: 1

Type: ERROR

Impact: Other

REP-00764: Error {0} occurred running the interoffice client.

Cause: The interoffice client was running to check in the documents into repository, but it failed on the indicated error code.

Action: Check the interoffice error code/message for the reason of failure.
Level: 1

Type: ERROR

Impact: Other

REP-00769: Sending to mail from the Parameter Form when the Paper Design view is open is invalid.

Cause: The Paper Design is open and destype is set to mail.

Action: Select mail directly from the Paper Design view and not from the Parameter Form.
Level: 1

Type: ERROR

Impact: Other

REP-00770: The Before Form trigger failed.

Cause: The Before Form trigger in the report returned false.

Action: Make the appropriate changes (either to the PL/SQL source in the Before Form trigger or to the report) to make the trigger return true.
Level: 1

Type: ERROR

Impact: Other

REP-00771: The After Form trigger failed.

Cause: The After Form trigger in the report returned false.

Action: Make the appropriate changes (either to the PL/SQL source in the After Form trigger or to the report) to make the trigger return true.
Level: 1

Type: ERROR

Impact: Other

REP-00772: Parameter Form Fields {0} and {1} may not have the same Source.

Cause: The same Source was specified for two Parameter Form fields. Fields on the Runtime Parameter Form must have unique sources.

Action: Change the Source of one of the fields.
Level: 1

Type: ERROR

Impact: Other

REP-00773: No Source was specified for Parameter Form Field {0}.

Cause: A Source was not specified for a Parameter Form field or the source parameter was deleted from the data model. Fields on the Runtime Parameter Form must have a source.

Action: Specify a valid Source for the Parameter Form field.
Level: 1

Type: ERROR

Impact: Other

REP-00774: No selectable values are available for LOV parameter {0}.

Cause: Either no values were specified for the LOV parameter's select list, or values were specified that cannot be selected.

Action: Check the SELECT statement or selectable value list of the parameter to ensure that the specified values are selectable.
Level: 1

Type: ERROR

Impact: Other

REP-00775: The data type of the first column of the SELECT statement does not match the data type of LOV parameter {0}.

Cause: The data type of the first column specified in the SELECT statement does not match the data type specified for the LOV parameter.

Action: Check the data type of the LOV parameter, the SELECT statement, and the columns in the database tables accessed by the SELECT statement to ensure that they match.
Level: 1

Type: ERROR

Impact: Data

REP-00776: There are columns with values in segmented memory when populating LOV parameter {0}. They will be ignored.

Cause: Columns were selected with values in segmented memory for the LOV parameter's select list, which is not allowed.

Action: Select different columns or move the column values.
Level: 1

Type: ERROR

Impact: Memory

REP-00777: There are columns whose types cannot be handled when populating LOV parameter {0}. They will be ignored.

Cause: Columns were selected whose types cannot be handled (for example, binary data).

Action: Select different columns.
Level: 1

Type: ERROR

Impact: Other

REP-00778: Some columns cannot be formatted correctly when populating LOV parameter {0}. They will be ignored.

Cause: The SELECT statement selecting values for the parameter's LOV retrieves columns whose values cannot be formatted according to their datatypes.

Action: Convert the values to valid ones or check the database to see if the values of the columns are valid.
Level: 1

Type: ERROR

Impact: Other

REP-00779: Some items of LOV parameter {0} are too long. These items will be truncated.

Cause: The items specified or columns selected contain some values that are too long to include in the LOV parameter's select list.

Action: Check the values of the items and reduce their length if necessary.
Level: 1

Type: ERROR

Impact: Other

REP-00780: The initial value entered is invalid against the input mask {0}.

Cause: The value entered in the Initial Value field violates the mask specified in the Input Mask field.

Action: Either enter a different value in Initial Value or change the mask in Input Mask.
Level: 1

Type: ERROR

Impact: Other

REP-00781: Bind variables are not allowed in the SELECT statement.

Cause: Bbind variables were included in the SELECT statement.

Action: Remove the bind variables from the SELECT statement.
Level: 1

Type: ERROR

Impact: Other

REP-00782: The data type of the parameter does not match the data type of its source columns.

Cause: The column selected has an invalid data type to furnish values for the LOV parameter's select list.

Action: Change the column's data type or specify a different column.
Level: 1

Type: ERROR

Impact: Data

REP-00783: The possible values list has bad syntax.

Cause: Incorrect syntax was specified to create the list of possible values for the LOV parameter.

Action: Edit the possible values list to ensure that it is a proper comma-separated list.
Level: 1

Type: ERROR

Impact: Other

REP-00784: A possible value has invalid width.

Cause: A value specified for the LOV parameter's list of possible values has an invalid width.

Action: Edit the possible values list so that all possible values have valid widths, or alter the width.
Level: 1

Type: ERROR

Impact: Other

REP-00785: A possible value is invalid against the input mask.

Cause: A value specified for the LOV parameter's list of possible values is not formatted in accordance with the specified input mask.

Action: Edit the possible values list to ensure that all possible values are valid against the input mask.
Level: 1

Type: ERROR

Impact: Other

REP-00786: The initial value is not among the possible values.

Cause: The initial value specified for the LOV parameter does not appear on the defined list of possible values.

Action: Add the initial value specified to the possible values list.
Level: 1

Type: ERROR

Impact: Other

REP-00787: The name of the first column of LOV parameter {0}'s select statement is not the same at runtime as design time.

Cause: There is a discrepancy between the columns specified in the original SELECT statement and what the tables in question now contains.

Action: Check the database to determine if the tables in question have been updated since the parameter list was created, or reapply the LOV parameter's SELECT statement.
Level: 1

Type: ERROR

Impact: Other

REP-00788: The value of restricted LOV parameter {0} is not among the selectable values.

Cause: The value specified for a LOV parameter is not on the parameter's select list.

Action: Select a value from the parameter's select list.
Level: 1

Type: ERROR

Impact: Other

REP-00790: Page Width and Page Height must either both be specified or both be blank.

Cause: A blank value was specified for either Page Width or Page Height in the Runtime Settings tab of the Tools Options dialog box.

Action: Specify a valid value for the blank setting, or make both settings blank.
Level: 1

Type: ERROR

Impact: Other

REP-00800: Select All is valid only in a text entry field.

Cause: Select All was selected from the Edit menu with the cursor positioned on an element in the Property Inspector other than a text field.

Action: While in the Property Inspector, select Edit then Select All only in a text field.
Level: 1

Type: ERROR

Impact: Other

REP-00801: The layout canvas must remain large enough to fit all layout objects.

Cause: The painting region of the Paper Layout editor was reduced by changing one or more settings in the Report Properties dialog box, or by resizing the margin, but the resized painting region is not large enough to fit all of the layout objects.

Action: Verify that all layout objects in the body, margin, header, and trailer sections of the report fit in the resized painting region.
Level: 1

Type: ERROR

Impact: Other

REP-00802: The Parameter Form canvas must remain large enough to fit all Parameter Form objects.

Cause: The painting region of the Parameter Form editor was reduced by changing one or more settings in the Report Properties dialog box, but the resized painting region is not large enough to fit all of the Parameter Form objects.

Action: Verify that all Parameter Form objects fit in the resized painting region.
Level: 1

Type: ERROR

Impact: Other

REP-00803: The canvas size specified is too large.

Cause: The report contains combined settings of page/form size and either logical page, maximum body page, maximum header page, maximum footer page, or number of Parameter Form pages that results in a value larger than that supported by Oracle Reports Builder (a dpi value greater than 2 gigabytes).

Action: Make the page/form size smaller, or decrease the value for logical page size, maximum body pages, maximum header pages, maximum footer pages, or number of Parameter Form pages.
Level: 1

Type: ERROR

Impact: Other

REP-00804: The report definition was modified during the current run. Oracle Reports Builder cannot continue running the Parameter Form or report.

Cause: While in the Runtime Parameter Form, the report was modified through an editor or Property Inspector.

Action: Cancel the Runtime Parameter Form and rerun the report.
Level: 1

Type: ERROR

Impact: Other

REP-00805: Menus cannot be initialized.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00806: An error occurred reading window resources.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00807: The array size is missing.

Cause: In the Runtime Settings dialog box, the Array Size field was left blank.

Action: Enter an Array Size value between 1 and 9999.
Level: 1

Type: ERROR

Impact: Other

REP-00808: The buffer size is missing.

Cause: In the Runtime Settings tab of the Tools Options dialog box, the Buffer Size field was left blank.

Action: Enter a Buffer Size value between 1 and 9999.
Level: 1

Type: ERROR

Impact: Other

REP-00809: The long chunk size is missing.

Cause: In the Runtime Settings tab of the Tools Options dialog box, the Long Chunk Size field was left blank.

Action: Enter a Long Chunk Size value between 1 and 9999.
Level: 1

Type: ERROR

Impact: Other

REP-00810: The Success/On Failure value is invalid.

Cause: In the character-mode Runtime Settings dialog box, On Success/On Failure specified an invalid value.

Action: Select a valid value for On Success/On Failure: Noaction, Rollback, or Commit.
Level: 1

Type: ERROR

Impact: Other

REP-00811: The Destination Type value is invalid.

Cause: In the character-mode Runtime Settings dialog, Destination Type specified an invalid value.

Action: Select a valid value for Destination Type: &lt;In Report Definition&gt;, Screen, File, Printer, or Mail.
Level: 1

Type: ERROR

Impact: Other

REP-00812: The Orientation value is invalid.

Cause: In the character-mode Runtime Settings dialog, Orientation specified an invalid value.

Action: Select a valid value for Orientation: &lt;In Report Definition&gt;, Landscape, or Portrait.
Level: 1

Type: ERROR

Impact: Other

REP-00813: The Mode value is invalid.

Cause: In the character-mode Runtime Settings dialog, Mode specified an invalid value.

Action: Select a valid value for Mode: &lt;In Report Definition&gt;, Default, Bitmap, or Character.
Level: 1

Type: ERROR

Impact: Other

REP-00814: The Background value is invalid.

Cause: In the character-mode Runtime Settings dialog box, Background specified an invalid value.

Action: Select a valid value for Background: &lt;In Report Definition&gt;, Yes, or No.
Level: 1

Type: ERROR

Impact: Other

REP-00815: The Orientation value is invalid.

Cause: In the character-mode Runtime Parameter Form, Orientation specified an invalid value.

Action: Select a valid value for Orientation: Landscape or Portrait.
Level: 1

Type: ERROR

Impact: Other

REP-00816: The Mode value is invalid.

Cause: In the character-mode Runtime Parameter Form, Mode specified an invalid value.

Action: Select a valid value for Mode: Bitmap or Character.
Level: 1

Type: ERROR

Impact: Other

REP-00817: The Background value is invalid.

Cause: In the character-mode Runtime Parameter Form, Background specified an invalid value.

Action: Select a valid value for Background: Yes or No.
Level: 1

Type: ERROR

Impact: Other

REP-00818: The page height has changed for the Parameter Form. Parameters might be crossed by page boundaries.

Cause: The height of the Runtime Parameter Form was changed in the Report Property Inspector. This might cause the page boundary to move such that it appears in the middle of an object in the Parameter Form.

Action: Examine the layout of the Parameter Form in the Parameter Form editor and ensure that none of the objects are directly on the page boundary (the darkened line in the editor). Alternatively, default (or redefault) the Parameter Form.
Level: 1

Type: ERROR

Impact: Other

REP-00819: AUTOCOMMIT ON for SQL Server connection cannot be set.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services. Another option is to remove all instances of SRW.DO_SQL. If this can be done while retaining all necessary functionality in the report, it will run.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-00820: cannot import specified image

Cause: The specified image cannot be imported.

Action: Check the image file to ensure it is a valid image and has not been corrupted.
Level: 1

Type: ERROR

Impact: Other

REP-00821: cannot export specified image

Cause: The specified object cannot be exported as an image.

Action: Create or select an image to export.
Level: 1

Type: ERROR

Impact: Other

REP-00822: no drawing imported

Cause: The specified drawing cannot be imported.

Action: Check the file to ensure it is a valid drawing and has not been corrupted.
Level: 1

Type: ERROR

Impact: Other

REP-00823: no drawing exported

Cause: The specified object cannot be exported as a drawing.

Action: Create or select a drawing to export.
Level: 1

Type: ERROR

Impact: Other

REP-00824: The data dictionary is not available on the connected database.

Cause: An attempt was made to access the Table and Column Names dialog box but the Data Dictionary is not available on the connected database.

Action: Connect to another database.
Level: 1

Type: ERROR

Impact: Data

REP-00825: The connected database is not Oracle or DB2. It cannot be used to store report documents.

Cause: An attempt was made to store a document to a database that is neither Oracle nor DB2, which is not allowed.

Action: Either connect to an Oracle or DB2 database or store the document as a file.
Level: 1

Type: ERROR

Impact: Other

REP-00828: Oracle Reports Builder tables are not installed in the database: cancelling report.

Cause: The report cannot be run because there are no Oracle Reports Builder tables in the database.

Action: Inform the database administrator that the Oracle Reports Builder tables were not successfully installed in the database.
Level: 1

Type: ERROR

Impact: Other

REP-00829: Oracle Reports Builder database tables are from an older version of Oracle Reports Builder ({0}): cancelling report.

Cause: Oracle Reports Builder tables in the database appear to have been installed from a previous version of the product. The report cannot run against an older version of the database tables.

Action: Inform the database administrator that the Oracle Reports Builder tables for this version were not successfully installed in the database.
Level: 1

Type: ERROR

Impact: Other

REP-00830: Oracle Reports Builder database tables appear to be corrupted or incorrectly installed: cancelling report.

Cause: The report cannot be run because the Oracle Reports Builder tables are in an unstable state.

Action: Inform the database administrator that the Oracle Reports Builder tables are either corrupted or incorrectly installed in the database.
Level: 1

Type: ERROR

Impact: Other

REP-00831: The query could not be built.

Cause: Oracle Reports Builder attempted to build a query at startup but it failed. One cause is that the database account against which the query was being built was not correct. Otherwise it is an abnormal condition.

Action: If Oracle Reports Builder was launched from another product, check that the database connection string in the other product is correct.
Level: 1

Type: ERROR

Impact: Other

REP-00900: The report cannot close while PL/SQL is still executing.

Cause: An attempt was made to close a report while associated PL/SQL was still executing.

Action: Finish executing the PL/SQL or abort it, then close the report.
Level: 1

Type: ERROR

Impact: Other

REP-00901: Tables and Columns function is not supported for this database server.

Cause: The connected database server does not have an accessible Data Dictionary to list tables and columns.

Action: No action is needed. Tables and Columns functionality is not available for these databases.
Level: 1

Type: ERROR

Impact: Other

REP-00910: The Cue Cards cannot be found. Reinstall the Cue Cards and try again.

Cause: An attempt was made to run the Cue Cards, where have not been properly installed.

Action: Reinstall the Cue Cards.
Level: 1

Type: ERROR

Impact: Other

REP-00911: The Oracle Reports page on OTN cannot be displayed. Reset the browser settings correctly.

Cause: In the Welcome to Oracle Reports Builder dialog box, Getting Started was selected, which displays the Oracle Reports page on the Oracle Technology Network (OTN), but the browser settings are not set correctly.

Action: 1. Edit the Windows registry using a registry editor (for example, open a command prompt window and type regedit.exe). 2. Select File, then Export to back up the current registry settings. 3. Navigate to the following key: HKEY_CURRENT_USER\Software\Oracle\Toolkit\Tkbrowser. 4. Set the BrowserName and the BrowserPath values to the browser name and location. For example: BrowserName: Internet Explorer BrowserPath: C:\Program Files\Internet Explorer\iexplore.exe 5. Close the registry editor. 6. Shut down and restart Oracle Reports Builder. 7. In the Welcome to Oracle Reports Builder dialog box, select Getting Started and click OK. 8. In the Information Navigator Preferences dialog box that displays, specify the following values: - From the Browser list, select the desired browser (for example, Microsoft Internet Explorer). - In the Command to launch browser field, specify the correct path to the browser; click Browse to navigate to the correct path location. For example: C:\Program Files\Internet Explorer\iexplore.exe 9. Click OK to save the settings and display the Oracle Reports page on the Oracle Technology Network (OTN) using the specified browser.
Level: 1

Type: ERROR

Impact: Browser

REP-00999: Unimplemented Error:

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01010: This name does not conform to SQL naming standards.

Cause: The name entered violates one or more SQL naming conventions.

Action: Name the object according to the appropriate naming conventions.
Level: 1

Type: ERROR

Impact: Other

REP-01011: Object {0} must be named.

Cause: The Name field was left blank for the object and a name is required.

Action: Name the object according to the appropriate naming conventions.
Level: 1

Type: ERROR

Impact: Other

REP-01012: There is another {0} object with this name.

Cause: The name entered duplicates the name of another object of the same type.

Action: Change the name of at least one of the objects.
Level: 1

Type: ERROR

Impact: Other

REP-01013: This name may not be the same as a reserved word.

Cause: The name entered duplicates a reserved word.

Action: Change the name of the parameter such that it conforms to parameter naming conventions.
Level: 1

Type: ERROR

Impact: Other

REP-01014: The name length cannot exceed 30 bytes.

Cause: The name entered was greater than 30 bytes, which is the limit for SQL names.

Action: Reduce the size of the name to 30 bytes or less.
Level: 1

Type: ERROR

Impact: Other

REP-01048: Owner and Access list are not overwritten.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01049: A report saved with a newer version of Oracle Reports Builder cannot be opened.

Cause: An attempt was made to open a report with an older version of Oracle Reports Builder than the one with which the report was saved.

Action: Use the same or a more recent version of Oracle Reports Builder to open the report.
Level: 1

Type: ERROR

Impact: Other

REP-01050: Document names in the database cannot be accessed.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01051: The document cannot be saved to file {0}.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01052: The document cannot be saved to the database.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01053: A new document ID cannot be obtained from the database.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01054: Table {0} cannot be deleted from.

Cause: An attempt was made to delete from a table and the operation failed, possibly due to lack of necessary privileges.

Action: Contact the system administrator to assign the necessary privileges to delete from the table.
Level: 1

Type: ERROR

Impact: Other

REP-01055: Table {0} cannot be locked.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01056: Object stored in the database cannot be renamed.

Cause: An attempt was made to rename a database object and the operation failed, possibly due to lack of necessary privileges.

Action: Make a copy of the object, or contact the system administrator to assign the necessary privileges to change the name.
Level: 1

Type: ERROR

Impact: Other

REP-01057: File {0} is not a valid Oracle Reports Builder file.

Cause: An attempt was made to access a file that is not in the proper format for Oracle Reports Builder.

Action: Verify that the correct file is being accessed.
Level: 1

Type: ERROR

Impact: Other

REP-01058: The document cannot be read from the database.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01059: unable to read document from file {0}

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01060: Oracle Reports Builder database tables have not been installed.

Cause: Oracle Reports Builder failed to access the SRW2_MODULE view in the current database.

Action: Verify Oracle Reports Builder was properly installed on the database. For help, contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

REP-01061: External file {0} cannot be read.

Cause: Read From File was activated and a file name specified as the value of a column, but Oracle Reports Builder could not successfully open or read the specified file.

Action: Check the spelling of the specified file in the Column Property Inspector, and verif that the specified file exists. If the file does exist, check the permissions on the file for read access.
Level: 1

Type: ERROR

Impact: Other

REP-01062: External query {0} cannot be found.

Cause: The possible causes of this error include the following: Case 1: REPORTS_PATH is not set. Case 2: There is no database connection. Case 3: The specified external query does not exist.

Action: Take the following actions to correct this error: If Case 1: Set REPORTS_PATH to a valid value. If Case 2: Connect to a database. If Case 3: Specify the correct name of the external query.
Level: 1

Type: ERROR

Impact: Other

REP-01063: The PL/SQL {0} has exceeded the platform specific size limit.

Cause: The PL/SQL could not be loaded because it is too large for the operating system. It may have been created on a different platform with a higher limit.

Action: Reduce the size of the PL/SQL so it can be loaded on the platform.
Level: 1

Type: ERROR

Impact: Other

REP-01064: Document {0} cannot be read.

Cause: An attempt was made to open a document whose definition, stored in either the database or the filesystem, has been lost or corrupted.

Action: This document cannot be used.
Level: 1

Type: ERROR

Impact: Other

REP-01065: External query {0} cannot be read.

Cause: An attempt was made to read an external query whose definition, stored in either the database or the filesystem, has been lost or corrupted.

Action: This external query cannot be used.
Level: 1

Type: ERROR

Impact: Other

REP-01066: Comment is corrupted and will be lost.

Cause: A storage error caused a comment to be corrupted. It will be discarded.

Action: No action is necessary. If desired, re-create the comment in the designer.
Level: 1

Type: ERROR

Impact: Other

REP-01067: Some information is missing in the report.

Cause: The report cannot be opened because the report definition is incomplete. It may have been corrupted.

Action: If the report is stored in the database, use SQL*Plus to determine whether the Oracle Reports Builder tables have been corrupted. If the report is an .rdf file, use a file system utility to check if the file is corrupted. Take appropriate actions to recover the data.
Level: 1

Type: ERROR

Impact: Other

REP-01070: An error occurred while opening or saving a document.

Cause: An error occurred while opening or saving a document.

Action: Verify the access privileges for the document.
Level: 1

Type: ERROR

Impact: Other

REP-01071: The end of an object or record scan was reached.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01072: The object cannot be found in the object store.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01073: The object was found in the object store when not expected.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01074: The object is too big.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01075: The object is invalid.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01076: The specified object store is invalid.

Cause: An attempt was made to use an invalid file or database object.

Action: Verify that the object specified is a valid Oracle document, stored in a file or in the database.
Level: 1

Type: ERROR

Impact: Other

REP-01077: The type specified for the object is invalid.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01078: A non-specific file error occurred.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01079: The function is unsupported.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01080: A unique key violation occurred.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01081: A page split occurred.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01082: A close error occurred.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01083: A file version error occurred.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01084: A file header is bad or missing.

Cause: An operation required Oracle Reports Builder to open a file. The file either did not have a header or it did not have the expected header. The header may have been changed in an editor or the file may not be compatible with this release of Oracle Reports Builder.

Action: Attempt to fix the header in an editor, although it is not recommended that Oracle Reports Builder files be edited in this way. For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01085: A file create error occurred.

Cause: An operation that required Oracle Reports Builder to create a file failed, most likely due to insufficient privileges to create the file.

Action: Obtain the necessary privileges for the file.
Level: 1

Type: ERROR

Impact: Other

REP-01086: A file open read-only error occurred.

Cause: An operation that required Oracle Reports Builder to open a file failed, most likely due to insufficient privileges to open the file.

Action: Obtain the necessary privileges for the file.
Level: 1

Type: ERROR

Impact: Other

REP-01087: A file open read-write error occurred.

Cause: An operation that required Oracle Reports Builder to open a file failed, most likely due to insufficient privileges to open the file.

Action: Obtain the necessary privileges for the file.
Level: 1

Type: ERROR

Impact: Other

REP-01088: A file write error occurred.

Cause: An operation that required Oracle Reports Builder to write to a file failed, most likely due to insufficient file privileges to write to the file.

Action: Obtain the necessary privileges for the file.
Level: 1

Type: ERROR

Impact: Other

REP-01089: A file read error occurred.

Cause: An operation that required Oracle Reports Builder to read a file failed, most likely due to insufficient file privileges to read the file.

Action: Obtain the necessary privileges for the file.
Level: 1

Type: ERROR

Impact: Other

REP-01090: A file close error occurred.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01091: The disk or file system is full.

Cause: An attempt was made to save an object, but there was not enough space in which to save it.

Action: Either delete some unnecessary files or expand the storage space.
Level: 1

Type: ERROR

Impact: Other

REP-01092: A file unique key violation occurred.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01093: Allocate failed.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01094: Reallocate failed.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01095: Free failed.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01096: The document {0} is currently locked.

Cause: An attempt was made to open a document that is already opened (locked) by another user.

Action: Wait until the other user closes the document before accessing it.
Level: 1

Type: ERROR

Impact: Other

REP-01097: PRODUCT_USER_PROFILE or SYSTEM.PRODUCT_PROFILE does not exist.

Cause: The possible causes of this error include the following: Case 1: The table does not exist. Case 2: The necessary privileges to access the table are not granted.

Action: Take the following actions to correct this error: If Case 1: If the table is not already created, create it. If Case 2: Get access to the table by creating a public synonym for the table in the PRODUCT_USER_PROFILE table, or by making the table public via the PRODUCT_USER_PROFILE table.
Level: 1

Type: ERROR

Impact: Other

REP-01098: An error occurred reading PRODUCT_USER_PROFILE or SYSTEM.PRODUCT_PROFILE data.

Cause: The table is not created correctly.

Action: Ensure that the table was created with the appropriate columns. If it was not, then modify it as necessary.
Level: 1

Type: ERROR

Impact: Other

REP-01099: Files not created with Oracle Reports Builder cannot be opened.

Cause: An attempt was made to open a file that is not an Oracle Reports Builder report.

Action: Verify that the file is an Oracle Reports Builder report.
Level: 1

Type: ERROR

Impact: Other

REP-01100: The data model is invalid for this type of report.

Cause: An attempt was made to create a default layout with a layout style that does not match the data model.

Action: Either change the data model to match the selected layout style or select a different layout style to match the data model. For more information, see the Oracle Reports online help.
Level: 1

Type: ERROR

Impact: Data

REP-01101: Group {0} has an invalid repeat direction.

Cause: An attempt was made to create a default layout, but the selected layout style requires a different repeat direction for one of the groups. Some layout styles place restrictions on the repeat directions that can be selected for groups.

Action: Either change the repeat direction to meet the layout style requirements or select a different layout style.
Level: 1

Type: ERROR

Impact: Other

REP-01102: The default layout cannot fit onto page of size {0}.

Cause: Oracle Reports Builder tried to create the default layout selected but could not fit the entire layout on the page because the page is not wide enough.

Action: If possible, increase the Page Width on the Report Property Inspector or rearrange objects such that the layout will fit on the page. Otherwise, make the report multiple pages wide.
Level: 1

Type: ERROR

Impact: Other

REP-01103: No column is selected in group {0}.

Cause: While trying to create a default layout, a column was not selected for a selected group. Consequently, Oracle Reports Builder cannot build a default layout because one or more of the dimensions of the layout have no value.

Action: In the Report Wizard, select at least one column from each selected group.
Level: 1

Type: ERROR

Impact: Other

REP-01104: Page level summaries are not supported in the default layout.

Cause: A default layout was generated that does not fit within the given amount of space. The possible causes of this error include the following: Case 1: The layout generated is too large given the dimensions specified in the Report Properties dialog box. Case 2: The layout is too big given the size of the marked area in the Paper Layout editor.

Action: Take the following actions to correct this error: If Case 1: Increase the report dimensions such that the layout can fit, or alter the layout so that it will fit within the current dimensions. If Case 2: Increase the size of the marked area.
Level: 1

Type: ERROR

Impact: Other

REP-01106: no field is generated for column {0}.

Cause: When the default layout was created, a field was not generated for the column in the message. The most likely cause is that a summary was not placed in the data model correctly. For example, the source of a summary column may have been specified to be a column in a group above the summary's group, which is not allowed.

Action: Debug the data model and redefault the layout.
Level: 1

Type: ERROR

Impact: Other

REP-01107: The across or down group in cross product group {0} is missing.

Cause: An attempt was made to create a default layout by selecting a Style of Matrix in the Report Wizard, but all of the dimension groups of the cross product group were assigned repeat directions of Down or Across. Each repeat direction should be assigned to the dimension groups in the cross product.

Action: Redisplay the Report Wizard and reassign the repeat directions of the dimension groups, making sure that each direction is assigned among the groups.
Level: 1

Type: ERROR

Impact: Other

REP-01108: The default layout cannot fit even in region extending to page boundaries.

Cause: An attempt was made to create a default layout that would be too large to fit within the defined height and width of a report page.

Action: Go back to the Report Wizard and reduce the values of default settings (for example, shorten some field widths). Alternatively, increase the size of a report page using the Report Property Inspector. Then re-create the default layout.
Level: 1

Type: ERROR

Impact: Other

REP-01109: Multiple group selection is incompatible with single group layout style.

Cause: More than one group was selected to add to the layout but the style selected only supports one group.

Action: Change the group selection so that only a single group is selected. Alternatively change the layout style to one that supports multiple groups.
Level: 1

Type: ERROR

Impact: Other

REP-01110: The matrix across group in cross product group {0} is missing.

Cause: An attempt was made to create a default layout by selecting a Style of Matrix or Matrix with Group in the Report Wizard, but all of the dimension groups of the cross product group were assigned repeat directions of Down.

Action: Change the repeat direction of one of the cross product dimension groups so that there is at least one Across group and one Down group.
Level: 1

Type: ERROR

Impact: Other

REP-01111: The matrix down group in cross product group {0} is missing.

Cause: An attempt was made to create a default layout by selecting a Style of Matrix or Matrix with Group in the Report Wizard, but all of the dimension groups of the cross product group were assigned repeat directions of Across.

Action: Change the repeat direction of one of the cross product dimension groups so that there is at least one Down group and one Across group.
Level: 1

Type: ERROR

Impact: Other

REP-01112: The matrix cross product group in the matrix report is missing.

Cause: An attempt was made to create a default layout by selecting a Style of Matrix or Matrix with Group in the Report Wizard, but a cross product group was not selected to be used as the matrix group.

Action: Change the repeat direction of one of the cross product group to Matrix.
Level: 1

Type: ERROR

Impact: Other

REP-01113: No groups or reports level columns have been selected.

Cause: While trying to create a default layout, no groups or report level columns were selected. Consequently, Oracle Reports Builder cannot build a default layout because one or more of the dimensions of the layout have no value.

Action: In the Report Wizard, select at least one report level column or a group to be defaulted.
Level: 1

Type: ERROR

Impact: Other

REP-01114: A single group selection is incompatible with a multiple group layout style.

Cause: A single group was selected to be defaulted but a defaulting style designed for a multiple groups was also selected.

Action: Change the group selection so that more than one group is selected. Alternatively, change the layout style to one that supports single groups.
Level: 1

Type: ERROR

Impact: Other

REP-01115: The full template layout cannot be shown because it does not fit onto the page.

Cause: The template layout could not be shown properly because it is too large to fit within the defined height and width of the report page. This does not mean that the template is invalid in any way.

Action: To show the template layout, temporarily enlarge the width and height of the report page. To do this, select the template in the Navigator and open the Property Inspector. Increase the Width and Height properties under the Report heading. Do not forget to reset the Width and Height properties before saving the template.
Level: 1

Type: ERROR

Impact: Other

REP-01118: A cross product group in the Matrix query is missing.

Cause: An attempt was made to create a query by selecting the Matrix query option in the Data Wizard, However, the cross product group does not exist in the query to be used as the matrix group.

Action: Restart the Data Wizard.
Level: 1

Type: ERROR

Impact: Other

REP-01200: The flow compilation failed.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01201: Query text is missing from query {0}.

Cause: A query was named, but either no SELECT statement was entered for it or something that did not begin with the keyword SELECT was entered. The SQL Query Statement dialog box only accepts SQL SELECT statements.

Action: Enter a SQL SELECT statement that begins with the word SELECT (upper or lower case may be used).
Level: 1

Type: ERROR

Impact: Other

REP-01202: An Oracle logon was not specified.

Cause: An attempt was made to run a report without an Oracle logon specified.

Action: Enter a logon string in the Connect dialog box and accept the dialog box before rerunning the report.
Level: 1

Type: ERROR

Impact: Other

REP-01203: Field {0} references an invalid column.

Cause: The column specified as the field's Source either is invalid or does not exist.

Action: Select a column from the list of values.
Level: 1

Type: ERROR

Impact: Other

REP-01204: Repeating frame {0} references an invalid group.

Cause: The group name specified in the Group field of the Repeating Frame Property Inspector either is invalid or does not exist.

Action: Select a group from the list of values.
Level: 1

Type: ERROR

Impact: Other

REP-01205: There is a loop in the positional dependency tree.

Cause: Explicit anchors were created such that an object is indirectly anchored to itself. For example, if object A was anchored to object B, object B to object C, and object C to object A, this error displays.

Action: Remove at least one of the anchors that caused the loop.
Level: 1

Type: ERROR

Impact: Other

REP-01206: An object is anchored to more than one other object.

Cause: In the layout, an object was anchored to more than one other object.

Action: Eliminate the anchors to other objects such that the object is anchored to only one other object.
Level: 1

Type: ERROR

Impact: Other

REP-01207: The PL/SQL procedure for group filter {0} is missing.

Cause: The Filter Type on the Group Property Inspector specified a vlue of PL/SQL, but a valid filter was not specified.

Action: Enter a valid PL/SQL function or change the filter type.
Level: 1

Type: ERROR

Impact: Other

REP-01208: A repeating frame of matrix {0} cannot be anchored.

Cause: An attempt was made to run a report with an anchor from an intersecting repeating frame of a matrix object to another object.

Action: Delete the anchor.
Level: 1

Type: ERROR

Impact: Other

REP-01209: Matrix {0} cannot be anchored.

Cause: An attempt was made to run a report with an anchor from a matrix object to another object, which is not allowed.

Action: Delete the anchor.
Level: 1

Type: ERROR

Impact: Other

REP-01211: Object {0} is larger than its enclosing object {1}.

Cause: An object is larger than its enclosing object. The most likely cause is that an attempt was made to enclose a large object within a small, fixed frame.

Action: Identify the object and the enclosing object and adjust their relative sizes and positions until the proper enclosure is achieved.
Level: 1

Type: ERROR

Impact: Other

REP-01212: Object {0} is not fully enclosed by its enclosing object {1}.

Cause: The possible causes of this error include the following: Case 1: An object is not fully enclosed by the page. That is, the object extends beyond the page boundary. Case 2: A repeating frame that forms a matrix is one or more layers above a repeating frame that it contains. In a matrix layout, repeating frames must be below repeating frames that they contain.

Action: Take the following actions to correct this error: If Case 1: Move or resize the object so that it does not extend outside the page boundary. Alternatively, increase the page size in the Report Property Inspector. If Case 2: Use Arrange&gt;Send to Back, Arrange&gt;Bring to Front, Arrange&gt;Move Backward, and Arrange&gt;Move Forward to arrange repeating frames such that, in terms of layers, the following is true: repeating frames are below repeating frames that they contain and down repeating frames are below across repeating frames.
Level: 1

Type: ERROR

Impact: Other

REP-01213: Field {0} references column {1} at a frequency below its group.

Cause: The source column for the field is in a group below that of the repeating frame that encloses it.

Action: Move the field into a repeating frame whose source group is at or above the group that contains the field's source column. Otherwise, move the field's source column into the enclosing repeating frame's group, if possible.
Level: 1

Type: ERROR

Impact: Other

REP-01214: Repeating frame {0} is enclosed by a child repeating frame.

Cause: The enclosed repeating frame's source group is above the enclosing repeating frame's source group.

Action: In the editor, make the enclosed repeating frame the enclosing repeating frame. Alternatively, if possible, change the group hierarchy such that the enclosed object's group is below the enclosing object's group.
Level: 1

Type: ERROR

Impact: Other

REP-01216: Object {0} has an illegal print condition.

Cause: The Print Condition for the specified object was invalid. For example, an attempt may have been made to set the Print Condition of a margin object.

Action: Change the Print Condition of the object to another, valid setting.
Level: 1

Type: ERROR

Impact: Other

REP-01218: Object {0} cannot page break before AND keep with parent.

Cause: Page Break Before was set for an object as well as Keep with Anchoring Object. The anchoring object, however, precedes the object and therefore the two settings are in conflict.

Action: Uncheck Page Break Before or Keep with Anchoring Object.
Level: 1

Type: ERROR

Impact: Other

REP-01219: Object {0} has no size; length or width is zero.

Cause: A layout object was created of zero width or height.

Action: Enlarge the opject so that it has a non-zero height and width.
Level: 1

Type: ERROR

Impact: Other

REP-01220: Object {0} has Minimum Widow Records greater than Maximum Records per Page.

Cause: Maximum Records per Page was set to a smaller value than Minimum Widow Records. This causes a conflict between the two settings and, in effect, indicates that no instances should be printed.

Action: Decrease Minimum Widow Records or increase Maximum Records per Page.
Level: 1

Type: ERROR

Impact: Other

REP-01222: The body size is invalid.

Cause: A body page width or height was specified that is negative or out of range. This is most likely due to setting the page size to an invalid value using the PAGESIZE executable argument.

Action: Enter a valid value using the PAGESIZE executable argument, or adjust the body panel size by resizing the margins in the Paper Layout editor.
Level: 1

Type: ERROR

Impact: Other

REP-01223: The page size is invalid.

Cause: A physical page width or height was specified that is negative or out of range. This is most likely due to setting the page size to an invalid value using the PAGESIZE executable argument.

Action: Enter a valid value using the PAGESIZE executable argument, or change the physical page size setting in the Report Property Inspector.
Level: 1

Type: ERROR

Impact: Other

REP-01225: The logical page size is invalid.

Cause: A logical page height was specified that is negative.

Action: Redefine the logical panel height to ensure that it is not defined using a negative number.
Level: 1

Type: ERROR

Impact: Other

REP-01226: The body location is beyond the print area.

Cause: The body panel is not enclosed within the physical page.

Action: Adjust the body panel size by resizing the margins in the Paper Layout editor.
Level: 1

Type: ERROR

Impact: Other

REP-01229: The spacing between records for repeating frame {0} is negative.

Cause: The value for Vertical Spacing and/or Horizontal Spacing specified for a repeating frame is negative.

Action: Respecify the appropriate Spacing setting for the repeating frame.
Level: 1

Type: ERROR

Impact: Other

REP-01230: Field {0} has an invalid page reset group.

Cause: In the Reset At field of the Page Numbering dialog box, a repeating frame was specified that does not enclose the layout field that should display the page number. An invalid repeating frame may have been specified, or the repeating frame was deleted after specifying it.

Action: Specify &Report or the name of a valid repeating frame as the Reset At value for the page number field.
Level: 1

Type: ERROR

Impact: Other

REP-01231: Object {0} has an invalid text wrap style.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01232: Matrix {0} has an invalid source frame.

Cause: An invalid object was specified as the source frame of the matrix object, or the repeating frames specified have invalid Print Directions.

Action: Change the Print Direction of horizontal source repeating frame to Down, and the Print Direction of the vertical source repeating frame to Across.
Level: 1

Type: ERROR

Impact: Other

REP-01233: The frames of matrix {0} do not fully intersect.

Cause: The repeating frames that form the matrix do not completely intersect. For example, if there are two down repeating frames, two across repeating frames, and one of the across repeating frames only intersects completely with one of the down repeating frames, this error displays.

Action: Redefault the matrix layout, if possible, or move the repeating frames that make up the matrix such that they fully intersect one another.
Level: 1

Type: ERROR

Impact: Other

REP-01234: The position of matrix {0} is not at the intersection of its frames.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01235: An error occurred generating index for Cross Product.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01236: Query {0} is invalid.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01237: The data link is invalid.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Data

REP-01238: Group {0} is invalid.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01239: Column {0} is invalid.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01240: The anchor is invalid.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01241: A circular column dependency originating with column {0} exists.

Cause: A column was created that directly or indirectly references itself. For example, Column A might reference Column B which in turn references Column A.

Action: Update or delete columns to eliminate the circular dependency.
Level: 1

Type: ERROR

Impact: Other

REP-01242: Matrices must have all down frames below all across frames.

Cause: In a matrix layout, down repeating frames must be below across repeating frames.

Action: Using Arrange&gt;Send to Back, Arrange&gt;Bring to Front, Arrange&gt;Move Backward, and Arrange&gt;Move Forward, arrange repeating frames such that, in terms of layers, the following is true: repeating frames are below repeating frames that they contain, and down repeating frames are below across repeating frames.
Level: 1

Type: ERROR

Impact: Other

REP-01243: An unimplemented type of summary is specified in column {0}.

Cause: A summary function was specified that is not available.

Action: Specify a valid summary function.
Level: 1

Type: ERROR

Impact: Other

REP-01245: The wrong number of source columns are defined for summary function of column {0}.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01246: The graph document is not found.

Cause: Oracle Reports Builder cannot find the associated graph document for the graph.

Action: Correct the file name and path of the graph document.
Level: 1

Type: ERROR

Impact: Other

REP-01247: The report contains uncompiled PL/SQL.

Cause: An attempt was made to run the report before all referenced PL/SQL constructs was compiled.

Action: Compile the PL/SQL, then run the report.
Level: 1

Type: ERROR

Impact: Other

REP-01248: All source columns of placeholder {0} must be in the same group.

Cause: An attempt was made to set the value of a placeholder column from columns belonging to different groups.

Action: Change the placeholder column's group to match the group of the columns changing the placeholder column's value.
Level: 1

Type: ERROR

Impact: Other

REP-01249: Column {0} has no PL/SQL formula.

Cause: A column of Type Formula was created with nothing in the Formula field.

Action: Create a formula for the column or change the column's Type.
Level: 1

Type: ERROR

Impact: Other

REP-01250: A circular query dependency exists.

Cause: The report contains at least two queries, with each requiring the other to be executed first.

Action: Edit one or more of the queries to remove the circular dependency.
Level: 1

Type: ERROR

Impact: Other

REP-01251: A circular query dependency originating with query {0} exists.

Cause: The report contains at least two queries, with each requiring the other to be executed first. The query listed in the message is one of the conflicting queries.

Action: Edit the query listed or another conflicting query to remove the circular dependency.
Level: 1

Type: ERROR

Impact: Other

REP-01252: The matrix should be surrounded by a repeating frame on group {0}.

Cause: The data model for the report contains a matrix with a parent group, but in the layout the repeating frame for the parent group either does not exist or does not surround the matrix.

Action: Modify the layout of the report so that the parent group has a repeating frame that surrounds the matrix.
Level: 1

Type: ERROR

Impact: Other

REP-01253: Matrix objects are on different regions of the layout.

Cause: The repeating frames of a matrix are on different regions of the layout (body, margin, header, or trailer).

Action: Move all repeating frames of the matrix to the same report region.
Level: 1

Type: ERROR

Impact: Other

REP-01254: Anchored objects are on different regions of the layout.

Cause: The anchoring and anchored objects of an anchor are on different regions of the layout (body, margin, header, or trailer).

Action: Move the above-mentioned objects to the same report region.
Level: 1

Type: ERROR

Impact: Other

REP-01255: An object cannot anchor to a hidden object.

Cause: The anchored object of an anchor is a hidden object.

Action: Either make the anchored object not hidden, or delete the anchor.
Level: 1

Type: ERROR

Impact: Other

REP-01256: File link boilerplate text is missing its source file.

Cause: A file name was not specified in the Source Filename property for the file link boilerplate object.

Action: Specify a directory path and file name in the Source Filename property in the file link boilerplate object's Property Inspector.
Level: 1

Type: ERROR

Impact: Other

REP-01257: Oracle Reports Builder cannot fetch data for child query from caller.

Cause: Oracle Reports Builder was invoked from another product, and Oracle Reports Builder has been instructed to fetch data for a child query from the caller. Data passed to Oracle Reports Builder can only be for a master query.

Action: Modify the caller's instructions so that Oracle Reports Builder does not request data for a child query.
Level: 1

Type: ERROR

Impact: Data

REP-01258: Group {0} has no columns.

Cause: A group was created that has no columns.

Action: Delete the group or assign one or more columns to the group.
Level: 1

Type: ERROR

Impact: Other

REP-01259: Group {0} has no break columns.

Cause: A parent group was created that has no break columns.

Action: Mark the Break Order check boxex of the break columns of the group.
Level: 1

Type: ERROR

Impact: Other

REP-01260: Groups {0} and {1} are from the same query and cannot be linked.

Cause: Two groups from the same query were linked with a data link, which is not allowed.

Action: Remove the data link or relink to another group.
Level: 1

Type: ERROR

Impact: Other

REP-01261: Group {0} can have only one parent.

Cause: One group has two queries as its parent (it can only have one).

Action: Remove data links from the same group to different queries.
Level: 1

Type: ERROR

Impact: Other

REP-01262: A circular data link dependency starting from group {0} exists.

Cause: A cycle with data links was created (that is, a parent was specified as the child of itself, either directly or indirectly).

Action: Remove at least one of the links in the cycle.
Level: 1

Type: ERROR

Impact: Data

REP-01263: Cross product group {0} has no or only one dimension group.

Cause: A cross product group was defined that has no or only one group inside. Cross product groups must have at least two dimension groups. Multiquery cross product groups must have at least two queries within the cross product group.

Action: Remove the cross product group or add dimension groups, or dimension queries (if multiquery).
Level: 1

Type: ERROR

Impact: Other

REP-01264: A data link of group {0} crosses cross a product boundary.

Cause: In the multiple-query matrix report, a query has some of its groups are inside the cross product and some outside.

Action: Move all groups of the query to either outside or inside of the cross product group.
Level: 1

Type: ERROR

Impact: Data

REP-01265: A cross product group {0} has no child groups.

Cause: A cross product group has no child group, which is required. The child group acts as the cell of the matrix.

Action: Create a child group for the cross product group.
Level: 1

Type: ERROR

Impact: Other

REP-01266: Page Level column {0} is not allowed in a cross product.

Cause: A column was creted in a cross product group that is or relies on a column that is a page-level summary (that is, a summary with Reset At of Page).

Action: Remove the column from the cross product group, or change the Reset At value of the column or the page-level summary upon which it relies.
Level: 1

Type: ERROR

Impact: Other

REP-01267: Graph {0} references an invalid column as a bind parameter.

Cause: The graph references a column that does not exist. An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01268: Graph {0} references a bind column {1} at the wrong frequency.

Cause: The column specified for the graph is in a group below that of the repeating frame that encloses the graph.

Action: Move the graph into a repeating frame whose source group is at or above the group that contains the specified column. Otherwise, move the specified column into the enclosing repeating frame's group, if possible.
Level: 1

Type: ERROR

Impact: Other

REP-01269: Graph {0} references an invalid report group.

Cause: The report group specified for the graph does not exist. An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01270: Graph {0} references a report group at the wrong frequency.

Cause: The report group specified for the graph is above the source group of the enclosing repeating frame.

Action: Move the graph into a repeating frame with a source group that is at or above its report group.
Level: 1

Type: ERROR

Impact: Other

REP-01271: Graph column name {1} has been specified multiple times in the graph document {0}.

Cause: The specified graph column or parameter has been referenced more than once in the graph document.

Action: Check the columns and parameters specified for the graph and delete any duplicates.
Level: 1

Type: ERROR

Impact: Other

REP-01272: Column {0} may not be used as a break column.

Cause: A Break Order was specified on a summary, function, or placeholder. These types of columns cannot be used as break columns.

Action: Review the rules for which columns can be break columns. For more information, see the online help topic 'Break Order property'.
Level: 1

Type: ERROR

Impact: Other

REP-01273: Source groups of matrix {0} are not from the same cross product.

Cause: The source groups of the repeating frames that form the dimensions of the matrix are not contained by the same cross product group. The dimensions of a matrix must be contained within the same cross product group.

Action: Change the source groups of the repeating frames or select different repeating frames to form the dimensions of the matrix.
Level: 1

Type: ERROR

Impact: Other

REP-01274: Invalid repeat direction combination in matrix {0}.

Cause: Matrix dimension repeating frames whose source groups are in the same "family" hierarchy (that is, are descendants or ancestors of each other) within a cross product group must have the same Print Direction. Parent-child relationships within a cross product group are used to create nesting in the matrix. As a result, the repeating frames associated with such groups must print in the same direction on the page.

Action: Change the Print Direction of the repeating frames as necessary, select different source groups for the repeating frames, or select different repeating frames to form the dimensions of the matrix.
Level: 1

Type: ERROR

Impact: Other

REP-01275: Page level column {1} may not be referenced from format trigger {0}.

Cause: PL/SQL was entered in a Format Trigger that references columns with a Reset At or Compute At of Page.

Action: Remove the reference to the page-level column or change the column's Reset At or Compute At to something other than Page.
Level: 1

Type: ERROR

Impact: Other

REP-01276: Placeholder {0} references one or more non-formula columns.

Cause: A placeholder column contains SRW.REFERENCE, but the column referenced is not a formula column. For placeholder columns, SRW.REFERENCE must refer to a formula column.

Action: Change the column referenced via SRW.REFERENCE.
Level: 1

Type: ERROR

Impact: Other

REP-01277: The SELECT element is invalid.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01278: The PL/SQL procedure in {0} is invalid.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01279: Frame or repeating frame {0} is invalid.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01280: Field {0} is invalid.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01281: Boilerplate {0} is invalid.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01282: Matrix {0} is invalid.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01283: Graph document {0} is invalid.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01284: Query {0} has no groups.

Cause: The data model contains a query that has no groups. Each query in the data model needs at least one group associated with it.

Action: Create a new group for the query.
Level: 1

Type: ERROR

Impact: Other

REP-01285: Query {0} has no SELECT elements.

Cause: The data model contains a query that does not select anything. Each query in the data model must select at least one element.

Action: Enter a SELECT statement in the query, selecting at least one element.
Level: 1

Type: ERROR

Impact: Other

REP-01286: Group {0} is a cross product as well as a dimension.

Cause: A group was specified to act as both a cross product group and as a dimension group for another cross product group, which is not allowed.

Action: Make the group either a cross product group or a dimension group, but not both.
Level: 1

Type: ERROR

Impact: Other

REP-01287: Cross product group {0} may not have a group filter.

Cause: A group filter was specified on a cross product group, which is not allowed.

Action: Remove the group filter from the cross product group. Create the group filter for another group, if necessary.
Level: 1

Type: ERROR

Impact: Other

REP-01288: The numeric argument for group filter of group {0} is missing.

Cause: First or Last was specified for a group's filter, but a number dictating how many records the group should filter was not specified.

Action: Specify a number for the group filter.
Level: 1

Type: ERROR

Impact: Other

REP-01289: An unimplemented type of group filter is specified in group {0}.

Cause: A group filter was specified that is not available or is invalid.

Action: Specify a valid group filter for the group.
Level: 1

Type: ERROR

Impact: Other

REP-01290: The Source data type is incompatible with the summary function in column {0}.

Cause: The summary column was assigned a Source whose data type is incompatible with the specified Function. For example, a temp may have been made to sum a character column.

Action: Verify that the data type of the source column is compatible with the Function specified in the Summary Column Property Inspector.
Level: 1

Type: ERROR

Impact: Data

REP-01291: Column {0} has an invalid reset group.

Cause: An invalid Reset At value was specified for a summary column. Reset At can be set to the same group as the summary column, any group above the summary column's, Page, or Report.

Action: Specify a valid Reset At value for the summary column in its Property Inspector.
Level: 1

Type: ERROR

Impact: Other

REP-01292: Column {0} has an invalid compute group.

Cause: An invalid Compute At value was specified for a summary column. Compute At can be set to the same group as the summary column, any group above the summary column's, Page, or Report.

Action: Specify a valid Compute At value for the summary column in its Property Inspector.
Level: 1

Type: ERROR

Impact: Other

REP-01293: Column {0} has an invalid product order.

Cause: A column in a cross product group was assigned an invalid value for Product Order, or no value at all.

Action: Specify a valid value for Product Order (consisting of only dimension groups within the cross product) in the column's Property Inspector.
Level: 1

Type: ERROR

Impact: Other

REP-01294: The width of column {0} is too large.

Cause: The column's width exceeds the maximum allowed for the operating system.

Action: Reduce the width of the column in the Column Property Inspector.
Level: 1

Type: ERROR

Impact: Other

REP-01295: The data format of column {0} is unsupported.

Cause: Read from File was selected for a column, but an invalid or unavailable data format was specified in the Format field in the Column Property Inspector.

Action: Specify a valid data format in the Format field. The list of values displays all valid data formats. Note that for LONG, RAW, and LONG RAW database columns, only Text and Oracle Format (Image) are valid values for Format.
Level: 1

Type: ERROR

Impact: Data

REP-01296: The data link child cannot be in the cross product group {0}.

Cause: An attempt was made to link a column to a column in a cross product group, or to the cross product group itself.

Action: Create data links between columns and groups other than cross product groups and their associated columns.
Level: 1

Type: ERROR

Impact: Data

REP-01297: The data link child column {0} must be a database column.

Cause: An attempt was made to link a column to another column that is not a database column (for example, a summary, formula, or placeholder column).

Action: Create data links using only database columns and groups.
Level: 1

Type: ERROR

Impact: Data

REP-01298: Columns {0} and {1} have incompatible types to be linked.

Cause: The parent and child columns in the data link have incompatible datatypes that cannot be linked. For example, an attempt was made to link a Number column to a Character column.

Action: Verify that the parent and child columns specified in data links have compatible datatypes.
Level: 1

Type: ERROR

Impact: Other

REP-01299: Groups {0} and {1} in different cross products cannot be linked.

Cause: An attempt was made to create a data link between dimension groups of two different cross product groups, or between columns of the dimension groups.

Action: Delete data links between two different cross product groups or their columns.
Level: 1

Type: ERROR

Impact: Other

REP-01300: Text boilerplate {0} has no contents.

Cause: A text boilerplate object was created that contains no text.

Action: Enter some text in the boilerplate object, or delete it.
Level: 1

Type: ERROR

Impact: Other

REP-01301: The data link creates a sibling of group {0} within a cross product.

Cause: A data link was defined that created a sibling of a dimension group within a cross product group. No siblings of dimension groups are allowed within the cross product.

Action: Delete the sibling of the dimension group.
Level: 1

Type: ERROR

Impact: Data

REP-01302: The cross product has two or more child groups.

Cause: A cross product group has more than one child group. Only one child is allowed per cross product group.

Action: Remove all but one of the child groups to the cross product group.
Level: 1

Type: ERROR

Impact: Other

REP-01303: The query must be completely in or out of cross product group {0}.

Cause: A query was created whose groups are not all inside the cross product, above the cross product, or below the cross product, respectively.

Action: Verify that each query's groups are all inside of a cross product, above a cross product, or below a cross product.
Level: 1

Type: ERROR

Impact: Other

REP-01304: Cross product group {0} contains another cross product as child.

Cause: A cross product group was created that is a child of another cross product group, which is not allowed.

Action: Ensure that the child group of the cross product group is not a cross product group.
Level: 1

Type: ERROR

Impact: Other

REP-01305: Frame {0} intersects but does not enclose object {1}.

Cause: The report layout contains a frame that does not completely enclose the named object. Thus, the object is not considered to be inside the frame.

Action: To enclose the object with the frame, resize or move the frame.
Level: 1

Type: ERROR

Impact: Other

REP-01306: Summary column {0} has an invalid source.

Cause: An invalid source was specified for the summary column. A summary column's source must be from the same group as the summary column, or from a group below the summary column.

Action: Change the source of the summary column to be from the same group as the summary column or from a group below the summary column.
Level: 1

Type: ERROR

Impact: Other

REP-01307: Summary column {0} has an invalid product order.

Cause: The possible causes of this error include: Case 1: A summary exists that is not a running summary (that is, its Reset At is not Report), but its Product Order is not a subset of the source column's product order. The source column of the summary must be at least as frequent as the summary, which means that the summary's Product Order should be some subset of the source column's Product Order. Case 2: A running summary (that is, its Reset At is Report) exists with a Product Order that is not a prefix of the source column's Product Order. For example, if the source column's Product Order were A,B,C, then the summary column's Product Order would have to be either A (by itself) or A,B. The summary's Product Order could not be B,A.

Action: Take the following actions to correct this error: If Case 1: Change the Product Order of the summary such that it is a subset of its source column's Product Order. If Case 2: Change the Product Order of the summary such that it is a prefix of the Source column's Product Order.
Level: 1

Type: ERROR

Impact: Other

REP-01308: Placeholder column {0} is not supported in a cross product.

Cause: An attempt was made to create a placeholder column inside of a cross product group. Cross product groups cannot contain placeholder columns.

Action: Delete the placeholder or move it outside the cross product group.
Level: 1

Type: ERROR

Impact: Other

REP-01309: Report level summary {0} cannot be a percent of total.

Cause: A summary was created at the report-level (that is, a summary outside of all the groups in the data model) with a Function of % of Total. This Function makes no sense for a report-level summary because it will always be 100%.

Action: Delete the summary or move it into a group where it will make sense.
Level: 1

Type: ERROR

Impact: Other

REP-01310: Boilerplate {0} references &{1} which is not a field.

Cause: A boilerplate object has a reference to a field that does not exist. It could be that the field being referenced was deleted or renamed and so this reference in the boilerplate object is now invalid.

Action: Depending on circumstances, remove the reference, replace it with a reference to another field, or create the field that it references.
Level: 1

Type: ERROR

Impact: Other

REP-01311: Object {0} with page-dependent references have been changed to fixed sizing.

Cause: A field or boilerplate object has a reference to a page calculation or a total number of pages variable. (This is known as a forward reference.) Such layout objects must be fixed in size both horizontally and vertically.

Action: The layout object's Horizontal and Vertical Elasticity have been set to Fixed by Oracle Reports Builder. Check the output to ensure that the values are not being truncated. If they are, enlarge the layout object so that it is large enough to contain the values.
Level: 1

Type: ERROR

Impact: Other

REP-01312: Page-level column {1} may not be referenced from graph {0}.

Cause: A column passed to a graph is or depends upon a page-level summary (that is, a summary with a Reset At or Compute At of Page). A column being passed to a graph cannot be or depend upon a page-level summary.

Action: Do not pass the column to the graph.
Level: 1

Type: ERROR

Impact: Other

REP-01313: Page-level column {1} may not be referenced from group filter {0}.

Cause: A column that was referenced in a group filter is or depends upon a page-level summary (that is, a summary with a Reset At or Compute At of Page). A column referenced by a group filter cannot be or depend upon a page-level summary.

Action: Do not reference the column in the group filter.
Level: 1

Type: ERROR

Impact: Other

REP-01314: Format trigger {0} references column {1} at the wrong frequency.

Cause: A format trigger references a column that is located at the wrong frequency.

Action: Remove the reference to the column from the format trigger.
Level: 1

Type: ERROR

Impact: Other

REP-01315: Group filter {0} references column {1} at the wrong frequency.

Cause: A group filter attempted to reference a column that is inaccessible.

Action: Remove the reference to the column from the group filter.
Level: 1

Type: ERROR

Impact: Other

REP-01316: Object {0} references column {1} at the wrong frequency.

Cause: A procedure or function attempted to reference a column that is inaccessible.

Action: Remove the reference to the column from the PL/SQL subprogram.
Level: 1

Type: ERROR

Impact: Other

REP-01317: Boilerplate {0} references field with source {1} at the wrong frequency.

Cause: A boilerplate object referenced a field using &fieldname, but the two objects are not located at the same frequency. For example, the boilerplate object and the field it references are located within different repeating frames.

Action: Place the boilerplate object and field at the same frequency, or remove the reference.
Level: 1

Type: ERROR

Impact: Other

REP-01318: An error occurred while setting transaction to read-only.

Cause: Having specified READONLY=YES, this error occurred at the start of report execution, while ending the current transaction (with a COMMIT) and starting the read-only transaction, or at the end of report execution, while ending the read-only transaction (with a COMMIT).

Action: Verify the database connection, and verify that that no cursors or locks were left pending by the previous transaction.
Level: 1

Type: ERROR

Impact: Transactioning

REP-01319: Implicit anchoring algorithm cannot uniquely identify the anchoring object {0}. Arbitrarily choosing {1}.

Cause: The specified object (object1) is in the "push path" of two objects and it is equidistant from both objects. As a result, Oracle Reports Builder cannot use its normal criteria (shortest distance) to determine the implicit anchor. In the absence of its normal criteria, Oracle Reports Builder randomly creates an implicit anchor to the specified object (object2). Note that the implicit anchor may vary between runs of the report.

Action: To avoid the random creation of an implicit anchor, explicitly anchor the specified object (object1) to another object.
Level: 1

Type: ERROR

Impact: Other

REP-01320: Program unit {0} references a column with invalid ID {1}.

Cause: A report was run containing invalid PL/SQL (for example, PL/SQL that did not compile). The PL/SQL source included a column reference that cannot be resolved.

Action: Check the column references in the PL/SQL source, recompile all of the PL/SQL source in the report, and rerun the report.
Level: 1

Type: ERROR

Impact: Other

REP-01322: Page break after on object {0} has no effect.

Cause: A Page Break After was activated on an object that has no other objects anchored to it (implicitly or explicitly). In this case, Page Break After has no effect and is invalid. Notice that this is a warning, not an error message.

Action: Deactivate Page Break After for the object.
Level: 1

Type: ERROR

Impact: Other

REP-01323: Output columns in format trigger {0} are not allowed.

Cause: In the format trigger for the specified object, an attempt was made to set the value of an Oracle Reports Builder column parameter. For example, the value of a column called COUNT1 can be used in a condition (for example, IF :COUNT1=10), but its value cannot be directly set in an assignment statement (for example, COUNT1=10).

Action: Remove the assignment statement from the format trigger.
Level: 1

Type: ERROR

Impact: Other

REP-01324: Output columns in group filter {0} are not allowed.

Cause: In the filter for the specified group, an attempt was made to set the value of an Oracle Reports Builder column or parameter. For example, the value of a column called COUNT1 can be used in a condition (for example, IF :COUNT1=10), but its value cannot be directly set in an assignment statement (for example, COUNT1=10).

Action: Remove the assignment statement from the group filter.
Level: 1

Type: ERROR

Impact: Other

REP-01325: Output columns in a Between Page Trigger are not allowed.

Cause: In the Between Page trigger, an attempt was made to set the value of an Oracle Reports Builder column or parameter. For example, the value of a column called COUNT1 can be used in a condition (for example, IF :COUNT1=10), but its value cannot be directly set in an assignment statement (for example, COUNT1=10).

Action: Remove the assignment statement from the group filter.
Level: 1

Type: ERROR

Impact: Other

REP-01326: Trigger {0} writes to column {1} at the wrong frequency.

Cause: In a report trigger, an attempt was made to set the value of an Oracle Reports Builder column at the wrong frequency in the report. Only report-level columns or parameters can be referenced and set, and any page-dependent columns (that is, Reset At of Page) or columns that rely on page-dependent columns cannot be referenced or set.

Action: Verify that the columns and parameters whose values are referenced or set are report-level columns and parameters.
Level: 1

Type: ERROR

Impact: Other

REP-01327: Column {0} writes to column {1} at the wrong frequency.

Cause: In a formula column, an attempt was made to set the value of an Oracle Reports Builder column at the wrong frequency in the report. Only columns that are in the same group or in a higher group in the group hierarchy can be referenced and set. For example, a formula for a report-level column can only reference other report-level columns.

Action: Verify that the columns whose values are referenced or set are in the same group or in a higher group in the group hierarchy.
Level: 1

Type: ERROR

Impact: Other

REP-01328: A report containing ROWLABEL column {0} cannot be run in a non-trusted OS.

Cause: An attempt was made to run a report that requires a secure database while connected to a non-secure database.

Action: Run the report while connected to a secure database.
Level: 1

Type: ERROR

Impact: Other

REP-01329: Column {0} cannot be linked to column {1} because the child column is not a database column.

Cause: A data link was created in which the child column is a summary, formula, or placeholder column. Only database columns can be linked.

Action: Create a data link using database columns.
Level: 1

Type: ERROR

Impact: Other

REP-01330: Lexical parameter {0} in query {1} must not change column dependencies.

Cause: A lexical parameter was created that changes the number, type, or names of columns, or introduces new dependencies on computed columns or new bind references, when the report is run.

Action: Change the lexical parameter so that it does not change columns or introduce new dependencies or bind references.
Level: 1

Type: ERROR

Impact: Other

REP-01331: Column {0} cannot be linked to column {1} because the child column is determined by a lexical parameter.

Cause: A data link was created in which child column's value is determined by a lexical parameter, which is not allowed.

Action: Replace the child column of the data link with another column.
Level: 1

Type: ERROR

Impact: Other

REP-01332: Group filter for {0} cannot reference column {1}. It is not a valid database column or it depends on a related query.

Cause: A group filter was created that references a database column not in the group's query or in a query above it, or references a computed column that depends on an unrelated column.

Action: Remove the offending reference from the group filter.
Level: 1

Type: ERROR

Impact: Other

REP-01333: Unsupported layout: a matrix may not be inside another matrix.

Cause: A matrix layout was created nested within another matrix layout, which is not allowed.

Action: Redesign the layout to avoid the nesting.
Level: 1

Type: ERROR

Impact: Other

REP-01335: Variable rotated text {0} is treated as fixed/contract width.

Cause: The report contains a boilerplate text object that was rotated to an angle that is not a multiple of 90 degrees, although both Horizontal and Vertical Elasticity values were set to Variable or Expand. In this case, the Horizontal Elasticity is treated as Fixed (if Expand was specified) or Contract (if Variable was specified), and this warning is displayed.

Action: Consider changing the Horizontal and Vertical Elasticity values for this boilerplate object.
Level: 1

Type: ERROR

Impact: Other

REP-01336: The source of field {0} is page-level calculation {1}. {2}.

Cause: The specified field references a page summary owned by the named group, but there is no repeating frame for that group that surrounds the field.

Action: Create a repeating frame whose Source is the named group to surround the field. If such a repeating frame already exists, extend it to enclose the field.
Level: 1

Type: ERROR

Impact: Other

REP-01337: Boilerplate {3} references field {0}, whose source is page-level calculation {1}. {2}.

Cause: The specified boilerplate object references the specified field, whose Source is a page-level computation. However, there is no repeating frame (whose Source is the named group) surrounding the field.

Action: Create a repeating frame whose Source is the named group to surround the field. If such a repeating frame already exists, extend it to enclose the field.
Level: 1

Type: ERROR

Impact: Other

REP-01338: Column mode is not allowed on repeating frame {0}.

Cause: The Column Mode setting for a repeating frame does not satisfy either of the following conditions: Print Direction of Down and a Vertical Elasticity of Fixed. Print Direction of Across and a Horizontal Elasticity of Fixed.

Action: Change the Print Direction or Vertical/Horizontal Elasticity of the repeating frame, or deactivate Column Mode.
Level: 1

Type: ERROR

Impact: Other

REP-01339: Graph {0} is missing a data column specification.

Cause: A value was specified for the graph Query, but no columns were specified to be passed from the report to the graph document.

Action: To pass no data from the report to the graph document, specify nothing for the graph Query and Source. To pass data, specify the columns to be passed in addition to the graph Query and Source.
Level: 1

Type: ERROR

Impact: Data

REP-01340: Passed-in columns do not match report definition {0}.

Cause: Another component (for example, Oracle Forms) passed a query to Oracle Reports Builder and there is a mismatch between the columns passed and the columns expected by Oracle Reports Builder. Possible causes of this error include: Case 1: Oracle Reports Builder was expecting more or fewer columns than the number that was actually passed by the calling application. Case 2: The parameter list of the calling application described a column differently than what Oracle Reports Builder expected. For example, if the report's query selects a character column and the calling application assigns that column a date data type, this error is raised.

Action: Take the following actions to correct this error: If Case 1: Ensure that the calling application is passing the same number of columns that Oracle Reports Builder expects. If Case 2: Ensure that the datatypes and names of the columns being passed by the calling application match the dataypes and names in the report.
Level: 1

Type: ERROR

Impact: Other

REP-01341: Data truncation is possible in column {0}.

Cause: The database column's width in the report is defined to be less than its width in the database. This can occur when the columns in the database are updated subsequent to the creation of the report definition.

Action: Force the query to be reparsed. One method is to type a space at the end of a line in the SELECT Statement and then accept the SQL Query Statement dialog box.
Level: 1

Type: ERROR

Impact: Data

REP-01342: The type of the data link to query {0} is illegal for a non-Oracle server.

Cause: A data link was created with the START WITH clause and run while connected to a non-Oracle database. START WITH is only supported by Oracle.

Action: Remove the data link that uses START WITH or connect to Oracle.
Level: 1

Type: ERROR

Impact: Data

REP-01343: Button {0} is invalid.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01344: Button {0} has no action source file.

Cause: An action of Multimedia File was specified for the named button, but either a source file was not specified, or a source file was specified that does not exist.

Action: Open the Property Inspector for the specified button and verify that a valid file was selected as source for the button action.
Level: 1

Type: ERROR

Impact: Other

REP-01345: Button {0} has an invalid source column.

Cause: An action of Multimedia Column was specified for the named button, but either a source column was not specified, or an invalid source column was specified.

Action: Open the Property Inspector for the specified button and verify that a valid column was selected as source for the button action.
Level: 1

Type: ERROR

Impact: Other

REP-01346: Button {0} references source column {1} at the wrong frequency.

Cause: The column specified in the Property Inspector for the named button is in a group below that of the repeating frame that encloses the button.

Action: Move the button into a repeating frame whose source group is at or above the group that contains the specified column. Otherwise, move the specified column into the enclosing repeating frame's group, if possible.
Level: 1

Type: ERROR

Impact: Other

REP-01347: Button {0} has an invalid icon file.

Cause: Either an invalid file or a nonexistent file was specified as the icon file for the button face.

Action: Ensure that the specified icon file exists and is of the proper format and uncorrupted.
Level: 1

Type: ERROR

Impact: Other

REP-01348: The source column of field {0} is in sound or video format.

Cause: A column was specified containing sound or video as the source for a field, but fields cannot display sound and video.

Action: Specify another column (not sound or video) as source of the field.
Level: 1

Type: ERROR

Impact: Other

REP-01349: The PL/SQL action is missing from button {0}.

Cause: The PL/SQL trigger that serves as the specified button's action references a piece of PL/SQL that does not exist.

Action: Debug the trigger and ensure that it references a valid program unit.
Level: 1

Type: ERROR

Impact: Other

REP-01350: Output columns in action trigger {0} are not allowed.

Cause: The PL/SQL trigger that serves as a button action contains a bind variable that returns a value. A PL/SQL action trigger cannot return a value.

Action: Remove the bind variable from the PL/SQL.
Level: 1

Type: ERROR

Impact: Other

REP-01351: Icon {1} on button {0} cannot be found.

Cause: The icon specified as the button face for the named button cannot be found. The report will run, but the button will appear blank.

Action: Open the Property Inspector for the named button and verify that the icon specified exists and is in the correct format, and that the path information is correct.
Level: 1

Type: ERROR

Impact: Other

REP-01352: The fonts specified for this report cannot be found for the character set specified by NLS_LANG.

Cause: The NLS_LANG environment variable specifies a character set for which no font is available.

Action: Select a font that exists in the character set specified by NLS_LANG. Alternatively, use the Font Alias file to force an available font to be used, instead of the one specified in the report.
Level: 1

Type: ERROR

Impact: Other

REP-01353: The Web property of layout object {0} references field or column {1} at the wrong frequency.

Cause: One of the layout object properies (Bookmark, Action. Hyperlink, or Linktag) references a field or column, but the two objects are not located at the same frequency. For example, the layout object is located within a repeating frame whose source is a different group to that the column is in.

Action: Place the layout object in a repeating frame at the same frequency as the column object, or remove the reference.
Level: 1

Type: ERROR

Impact: Other

REP-01354: The Web property of layout object {0} references a page-dependent field or column {1}.

Cause: One of the layout object properies (Bookmark, Action. Hyperlink, or Linktag) references a field or boilerplate object that has a reference to a page calculation or a total number of pages variable. Web properties may only reference columns and fields that are not based on page calculations.

Action: Remove the Web property reference to the page-dependent field or column.
Level: 1

Type: ERROR

Impact: Other

REP-01355: PL/SQL is missing from PL/SQL-based query {0}.

Cause: A PL/SQL based query was created, but no PL/SQL was entered for it.

Action: Enter PL/SQL for the query.
Level: 1

Type: ERROR

Impact: Other

REP-01356: A column link is not allowed for linking to PL/SQL-based query {0}.

Cause: An attempt was made to link a column to another column that is in PL/SQL-based query, which is not allowed.

Action: Create group links and use the columns in the PL/SQL-based query as bind variables to set up intended column link conditions.
Level: 1

Type: ERROR

Impact: Other

REP-01357: Auto foreign key column link creation is only for SQL queries.

Cause: A link was dragged between two queries to automatically create column links based on foreign key relationships. However, this can be done only between two SQL queries.

Action: Drag a link between two SQL queries, or change the PL/SQL-based queries to SQL.
Level: 1

Type: ERROR

Impact: Other

REP-01365: A column link is not allowed for linking to Express-based query {0}.

Cause: An attempt was made to link a column to another column that is an Express-based query, which is not allowed.

Action: Create group links and use the columns in an Express-based query as bind variables to set up intended column link conditions.
Level: 1

Type: ERROR

Impact: Other

REP-01366: The XML Settings of object {0} reference page-dependent field or column {1}.

Cause: One of the object's XML properties references a field that contains a page calculation or a total number of pages variable. XML Settings canot reference columns and fields that are based on page calculations.

Action: Remove the XML Settings references to the page-dependent field or column.
Level: 1

Type: ERROR

Impact: Other

REP-01367: The XML Settings of object {0} reference field or column {1} at the wrong frequency.

Cause: One of the object's XML properties references a field or column that has a different frequency than the object (for example, the column may be in a different group than the object referencing it).

Action: Move the object such that it has the same frequency as the field or column (for example, place them in the same group) it references or remove the reference.
Level: 1

Type: ERROR

Impact: Other

REP-01368: Group {0} in the graph settings is invalid.

Cause: In the graph object's graph settings, the src attribute is an invalid group name.

Action: Ensure that value of the src attribute is a valid group name.
Level: 1

Type: ERROR

Impact: Other

REP-01369: An internal error occurred caused by form field {0}.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01370: Action {0} is unsupported.

Cause: The action specified against the form field is curently not supported.

Action: Remove the action entry from the report definition.
Level: 1

Type: ERROR

Impact: Other

REP-01371: Form field object {0} is unsupported.

Cause: This form field type is currently not supported by Oracle Reports.

Action: Remove the Form Field element from the report definition.
Level: 1

Type: ERROR

Impact: Other

REP-01372: The export value specified for {0} is invalid.

Cause: Either the export value is not specified or the export value is "off".

Action: Specify a valid export value ("off" is a reserved word).
Level: 1

Type: ERROR

Impact: Other

REP-01373: The validation and formatAndTreatment elements are not allowed for Form Field {0}.

Cause: The 'validation' or 'formatAndTreatment' element was specified for a Check Box and Radio Button.

Action: Remove the 'validation' or 'formatAndTreatment' element for the Form Field object.
Level: 1

Type: ERROR

Impact: Other

REP-01374: Font {0} is used to subset for the Form Field object {1}.

Cause: The font that is used to render a Form Field object was subsetted, which is not allowed.

Action: Either remove the font entry in uifont.ali or modify the font name of the Form Field object to a font that is not subset.
Level: 1

Type: ERROR

Impact: Other

REP-01400: coxr is not initialized.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01401: A fatal PL/SQL error occurred in program unit {2}.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01402: An unhandled PL/SQL exception occurred in program unit {2}.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01403: A PL/SQL procedure is suspended in program unit {2}.

Cause: A PL/SQL construct was suspended during execution or generation.

Action: Debug and recompile the PL/SQL constructs.
Level: 1

Type: ERROR

Impact: Other

REP-01404: PL/SQL compilation failed.

Cause: In generating the report, PL/SQL compilation failed.

Action: Debug the PL/SQL constructs.
Level: 1

Type: ERROR

Impact: Other

REP-01405: The PL/DQL code is not executable.

Cause: A PL/SQL construct did not compile properly or could not be executed.

Action: Debug the PL/SQL constructs.
Level: 1

Type: ERROR

Impact: Other

REP-01406: Parameterized code cannot be run directly.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01408: The PL/SQL cannot be initialized.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01409: Expected IS after PROCEDURE cannot be found.

Cause: A PL/SQL syntax error occurred.

Action: Correct the PL/SQL procedure in trigger/program unit and compile.
Level: 1

Type: ERROR

Impact: Other

REP-01410: An error occurred executing a PL/SQL filter in program unit {2}.

Cause: A PL/SQL syntax error occurred.

Action: Correct the PL/SQL procedure in trigger/program unit and compile.
Level: 1

Type: ERROR

Impact: Other

REP-01411: An error occurred executing PL/SQL formula in program unit {2}.

Cause: A PL/SQL syntax error occurred.

Action: Correct the PL/SQL procedure in program unit of formula column or trigger. Verify the variable declarations and usage.
Level: 1

Type: ERROR

Impact: Other

REP-01412: PL/SQL function {2} returned an invalid value or no value.

Cause: The report contains a PL/SQL function that does not specify a return value (for example, a format trigger that does not return TRUE or FALSE).

Action: Verify that the function includes a return statement for every code path.
Level: 1

Type: ERROR

Impact: Other

REP-01414: A library unit to run cannot be found in program unit {2}.

Cause: This is most likely an abnormal condition.

Action: Check the PL/SQL code and recompile it. If this error recurs, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01415: An unknown user exit {0} was encountered in program unit {2}.

Cause: A user exit was called, but it was not found.

Action: Verify the correct name for the user exit and that it has been compiled and linked.
Level: 1

Type: ERROR

Impact: Other

REP-01416: An error occurred in user exit {0} in program unit {2}. {1}.

Cause: An error occurred in a user exit. Possible errors: a reference to an unknown column, a truncated column value, unretrievable PL/SQL source, or the user exit was not found.

Action: Based on the submessage, debug the user exit. Veirfy columns references are valid and the PL/SQL code and user exit are accessible.
Level: 1

Type: ERROR

Impact: Other

REP-01417: An invalid integer argument was passed to procedure {0} in program unit {2}.

Cause: The packaged procedure referenced expected an integer for an argument, but it was not specified.

Action: Verify that the PL/SQL that references the packaged procedure correctly passes it an integer. For more information about PL/SQL packaged procedures, see the Oracle Reports online help.
Level: 1

Type: ERROR

Impact: Other

REP-01418: Null arguments were passed to procedure {0} in program unit {2}.

Cause: The exception SRW.NULL_ARGUMENTS was raised, either by a user-defined PL/SQL subprogram, or because a packaged subprogram was passed one or more null arguments.

Action: Check any PL/SQL code that might raise this exception. Also, check the argument list that is passed to the specified packaged subprogram.
Level: 1

Type: ERROR

Impact: Other

REP-01419: The PL/SQL program was aborted in program unit {2}.

Cause: A PL/SQL construct had a fatal error and was aborted.

Action: Check the PL/SQL constructs for errors.
Level: 1

Type: ERROR

Impact: Other

REP-01420: The PL/SQL program raised a program error in program unit {2}.

Cause: The exception SRW.PROGRAM_ERROR was raised, either by a user-defined PL/SQL subprogram, or because of an abnormal condition.

Action: Check any PL/SQL code that might raise this exception. If no PL/SQL raised the exception, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01421: A column of the wrong type was manipulated in procedure {0} in program unit {2}.

Cause: The data type of the column whose name was passed to a packaged procedure is not the correct data type for the packaged procedure (for example, the packaged procedure was expecting a column of Character data type and it was passed a column of another data type).

Action: Debug the PL/SQL that references packaged procedures and ensure that the packaged procedure is passed the name of a column of the correct data type. Also check the syntax of the packaged procedure to ensure that its is referenced properly.
Level: 1

Type: ERROR

Impact: Other

REP-01422: A procedure by this name already exists.

Cause: An attempt was made to create a new PL/SQL procedure with the same name as an existing PL/SQL procedure.

Action: Change the name of the new procedure or change the name of the existing procedure.
Level: 1

Type: ERROR

Impact: Other

REP-01423: Maximum rows of a query cannot be set after the query started executing in program unit {2}.

Cause: SRW.SET_MAX_ROW was used to reduce the number of rows fetched by a query. However, SRW.SET_MAX_ROW was called after the query was already fetched.

Action: Move SRW.SET_MAX_ROW to the Before Report trigger.
Level: 1

Type: ERROR

Impact: Other

REP-01424: An internal error occurred while executing procedure {0} in program unit {2}.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01425: An error occurred running DO_SQL package in program unit {2}: {0}.

Cause: An error occurred while Oracle Reports Builder was executing an SRW.DO_SQL call. Embedded in this message is an Oracle Reports Builder message and, possibly, an Oracle error message describing the exact error that occurred.

Action: Errors in SRW.DO_SQL are most often the result of a SQL error. Refer to the SQL Language Reference Manual and verify that the SQL statement in the SRW.DO_SQL call is correct.
Level: 1

Type: ERROR

Impact: Other

REP-01426: Procedure {0} was running from incorrect context in program unit {2}.

Cause: An attempt was made to call the named packaged procedure from an invalid area. For example, SRW.SET_ATTR cannot be called from a formula.

Action: Modify the PL/SQL code so that it does not call the packaged procedure from that context.
Level: 1

Type: ERROR

Impact: Other

REP-01427: A nonexistent query name was referenced in procedure {0} in program unit {2}.

Cause: A call was made to the SRW.SET_MAXROW procedure in a Before Report trigger, but the query referenced in the procedure call does not exist.

Action: Change the call to the SRW.SET_MAXROW procedure so that it references an existing query in the report.
Level: 1

Type: ERROR

Impact: Other

REP-01428: An error occurred while running procedure {0} in program unit {2}.

Cause: The exception SRW.RUN_REPORT_FAILURE was raised, either by a user-defined PL/SQL subprogram, or because of an abnormal condition after SRW.RUN_REPORT was called.

Action: Check any PL/SQL code that might raise this exception. If no PL/SQL raised the exception, check the command line string passed to SRW.RUN_REPORT. Verify that BATCH=YES, that the specified report exists, and that all parameter values are correct.
Level: 1

Type: ERROR

Impact: Other

REP-01429: Procedure {0} cannot be invoked with BATCH=NO in program unit {2}.

Cause: A call was made to the SRW.RUN_REPORT procedure with a command line string containing BATCH=NO, which is not allowed.

Action: Remove BATCH=NO from the SRW.RUN_REPORT command string.
Level: 1

Type: ERROR

Impact: Other

REP-01430: A REP file for report {0} cannot be created: compilation errors found.

Cause: There is an error in the PL/SQL in the report to be converted.

Action: Open the report and debug the PL/SQL.
Level: 1

Type: ERROR

Impact: Other

REP-01433: An error occurred running user exit {0} in program unit {2}.

Cause: While running the user exit named in the message, an error occurred.

Action: Debug the user exit and ensure that it is linked.
Level: 1

Type: ERROR

Impact: Other

REP-01434: Procedure {0} cannot be invoked with a user ID in program unit {2}.

Cause: A call was included to the SRW.RUN_REPORT procedure with a command line string containing a userid/password, which is not allowed.

Action: Remove the userid/password from the SRW.RUN_REPORT command string.
Level: 1

Type: ERROR

Impact: Other

REP-01435: The value of column {0} was truncated in program unit {2}.

Cause: A column (for example, a placeholder) was assigned a value larger than its width could contain, raising the SRW.TRUNCATED_VALUE exception. The exception was not handled, raising this error.

Action: Make the column wide enough to contain the assigned value, or handle the exception in the PL/SQL source.
Level: 1

Type: ERROR

Impact: Other

REP-01436: The PL/SQL references an object that is not in the scope in program unit {2}.

Cause: In a parameter's Validation Trigger field, PL/SQL source referenced a report column, which is not allowed.

Action: Remove the reference to the report column from the parameter's Validation Trigger.
Level: 1

Type: ERROR

Impact: Other

REP-01437: A run time error in the PL/SQL development environment (DE).

Cause: This is most likely an abnormal condition.

Action: Refer to the accompanying development environment error message for details on the problem. For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01438: The GETREF function parameter {0} must be of type LONG, LONG RAW, or RAW.

Cause: The second parameter in a CDE_MM.GET_REF call specifies a column that is not of type LONG, LONG RAW, or RAW.

Action: Change the second parameter to specify a column of the correct type.
Level: 1

Type: ERROR

Impact: Other

REP-01440: An unknown column name was passed to {0} in program unit {2}.

Cause: A column name specified in the named program unit in one of the triggers is invalid.

Action: Verify the column name is correct.
Level: 1

Type: ERROR

Impact: Other

REP-01441: A column value was not available for {0} in program unit {2}.

Cause: A column name specified in the named program unit in one of the triggers is not available.

Action: Verify the column value is correct.
Level: 1

Type: ERROR

Impact: Other

REP-01442: Column value {0} cannot be set in program unit {2}.

Cause: A value is not settable for this column.

Action: Verify the procedure is correct.
Level: 1

Type: ERROR

Impact: Other

REP-01443: Column value {0} is invalid in program unit {2}.

Cause: A column value specified in the named program unit in one of the triggers is invalid.

Action: Verify the column value is correct.
Level: 1

Type: ERROR

Impact: Other

REP-01444: No more rows exist in the group handle.

Cause: SRW.GH_NEXT() is called when the group handle is already at the last row.

Action: Catch a SRW.NO_DATA_FOUND exception in PL/SQL.
Level: 1

Type: ERROR

Impact: Other

REP-01445: The JAVA class cannot be found.

Cause: The requested class could not be located within the Reports classpath.

Action: Ensure that the class is correctly specified (for example, java/lang/String) and that the class is in the Reports classpath specified in the REPORTS_CLASSPATH environment variable.
Level: 1

Type: ERROR

Impact: Other

REP-01446: The JAVA method cannot be found.

Cause: The requested method could not be located within in the specified class.

Action: Ensure that the method exists within the specified class and has the correct signature: '(Ljava/lang/String;)Ljava/lang/String;'.
Level: 1

Type: ERROR

Impact: Other

REP-01447: A JAVA exception was encountered.

Cause: An error occurred attempting to start the JVM and access the requested Java class and method.

Action: Check the JVM install and environment.
Level: 1

Type: ERROR

Impact: Other

REP-01448: The data model group passed to SRW.GH_CREATE() does not exist.

Cause: The group name parameter of SRW.GH_CREATE() is invalid.

Action: Ensure that the group name is correctly specified. Catch the SRW.UNKNOWN_GROUP exception in PL/SQL.
Level: 1

Type: ERROR

Impact: Data

REP-01508: Cross Product: value of calculation cannot be found.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01510: Group Manager: unable to compute column {0}.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01516: Reset At Page is an invalid option for column {0} in Web-based reports.

Cause: A column in the report layout has Reset At Page, which is invalid for Web-based reports.

Action: Specify Reset At for either a group or report for Web-based reports.
Level: 1

Type: ERROR

Impact: Other

REP-01517: Column {0} references column {1}, which has incompatible frequency.

Cause: A column in the data model references another column (for example, in the Formula field) in the data model, but the two columns are assigned to incompatible groups. For example, if a formula column with a Group of Report referenced a column with a Group of G_Emp, this error is raised.

Action: Remove the column reference, or assign the referencing column to a group that is compatible with the group of the referenced column.
Level: 1

Type: ERROR

Impact: Other

REP-01518: Group Manager: internal error {0} occurred while processing group {1}.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01607: Record Manager: the source of report level column {0} is not available.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01610: Record Manager: a query with internal joins has Maximum Number of Rows set.

Cause: SRW.SET_MAXROW was probably used to set Maximum Number of Rows on the cell query of a multiquery cross product.

Action: Remove the call to SRW.SET_MAXROW for the cell query.
Level: 1

Type: ERROR

Impact: Other

REP-01760: Error Utility: internal error #1 occurred.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01761: Internal error {0} occurred while processing {2} {1}.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01762: Internal error {0} occurred.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01780: Stack utility: an error occurred during allocation.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01781: Stack utility: an error occurred during push.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01782: Stack utility: an error occurred during pop.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01783: Stack utility: an attempt was made to pop an empty stack.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01800: A formatter error occurred.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01801: An unknown file type was encountered for a Read from File field.

Cause: An attempt was made to create a file column, but the file type entered was invalid.

Action: Display the list of values and pick a valid file type.
Level: 1

Type: ERROR

Impact: Other

REP-01802: Contents of a field cannot be read from a text file.

Cause: Read from File was selected for a column, but Oracle Reports Builder could not find the files pointed to by the column. The possible causes of this error include the following: Case 1: The files do not exist. Case 2: The necessary privileges to access the files are not granted. Case 3: A system error made it impossible to find the files.

Action: Take the following actions to correct this error: If Case 1: Uncheck Read from File or create the necessary files. If Case 2: Update privileges, if possible. If Case 3: Consult the operating system documentation or contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

REP-01803: Destination file {0} cannot be opened.

Cause: The destination file specified for the report could not be opened.

Action: Consult the operating system documentation or contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

REP-01804: Printer definition file {0} cannot be opened.

Cause: The printer definition file for the specified printer could not be opened.

Action: Consult the operating system documentation or contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

REP-01805: Mail text file {0} cannot be opened.

Cause: An attempt was made to send the report output to a mail message, but the file for the message could not be opened.

Action: Consult the Oracle*Mail documentation or contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01806: Mail command file {0} cannot be opened.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01807: The mail report command failed.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01808: The print command file cannot be opened.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01809: The print report command failed.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01810: The Oracle Reports Builder ASCII Driver will be used to run a character report.

Cause: An attempt was made to print a character-mode report to a printer or a file using either a PostScript driver or the Microsoft Windows Generic Text driver.

Action: No action necessary.
Level: 1

Type: ERROR

Impact: Other

REP-01811: An error occurred while generating a graph.

Cause: Oracle Reports Builder called Graphics Runtime to generate a graph, but no graph was created.

Action: Verify that the named graph document exists and will run.
Level: 1

Type: ERROR

Impact: Other

REP-01812: Too many pages formatted. There is either too much data or an error in the report's definition.

Cause: The possible causes of this error include the following: Case 1: A user-defined limit set to catch too much data has been reached. Case 2: An error in the report definition has been reached.

Action: Take the following actions to correct this error: If Case 1: Abort running the program. Check the value of PAGE_LIMIT in the PRODUCT_PROFILE table. Ensure that it is either '0', which means the user is allowed to format an unlimited number of pages, or some value sufficiently large to enable the user to format the report. If Case 2: Debug the report in the Report Editor.
Level: 1

Type: ERROR

Impact: Data

REP-01813: Object {0} is too large to fit in a matrix cell.

Cause: The data fetched into a matrix cell exceeds the capacity of the cell. For example, the cell may contain a variable field, and the data may be longer than expected.

Action: Either enlarge the matrix cells until they are able to contain the data fetched into them, or redefine the data.
Level: 1

Type: ERROR

Impact: Other

REP-01814: The report cannot be formatted. Object {1} cannot fit within location {0}.

Cause: The referenced object is causing the most recently formatted page to start with exactly the same state as the previous page. Formatting will therefore cycle until abnormally terminated. Possible causes of this error include: Case 1: An object whose Print Condition type is All overflows to the next page. Case 2: An object whose sizing is Variable or Expand does not appear to extend beyond page boundaries in the Paper Layout editor but does when the report is formatted. Case 3: A repeating frame does not appear to extend beyond page boundaries in the Paper Layout editor but does when the report is formatted.

Action: Using the referenced object as a guide, examine the report layout for objects that may extend beyond page boundaries. Note: The object referenced in the message is the object that extends beyond the boundary. This object may be pushed beyond the boundary by another object, and this second object may need modification.
Level: 1

Type: ERROR

Impact: Other

REP-01815: A bad Oracle Number was encountered.

Cause: A formula providing the value of a column failed to specify any value.

Action: Debug any formulas in the report columns and ensure that each formula specifies a value where necessary.
Level: 1

Type: ERROR

Impact: Other

REP-01816: No value was specified for COPIES, and no output was created.

Cause: In the Runtime Parameter Form or the Print Job dialog box, zero (0) copies was specified.

Action: Specify a value of one or more copies.
Level: 1

Type: ERROR

Impact: Other

REP-01817: The start page occurs after the end page. No pages were generated.

Cause: In the Print Job dialog box, a starting page number was specified that is greater than the ending page number.

Action: Change either the starting page number or the ending page number such that the starting number is less than the ending number.
Level: 1

Type: ERROR

Impact: Other

REP-01818: Data in image format could not be read.

Cause: Possible causes of this error include: Case 1: An attempt was made to read a file or database column as containing an image, but the file or column's contents are of the wrong format. Case 2: The width of the Oracle Reports Builder column specified may be truncating the image because it is too small. Case 3: REPORTS_DEFAULT_DISPLAY is set to YES and the image format used is not supported.

Action: Take the following actions to correct this error: If Case 1: Verify that the file or column specified contains an image in a valid format. If Case 2: Change the width of the Oracle Reports Builder column so that it is large enough to display the image. If Case 3: Verify that the image format is one of the supported formats: GIF, JPEG, JPG, PNG, BMP.
Level: 1

Type: ERROR

Impact: Data

REP-01819: Filename {0} is longer than the platform maximum of {1} characters.

Cause: A name was specified for a file that is longer than the platform-allowed maximum. This is most likely to occur when accessing a file using Read from File, and the file name in the database is too long.

Action: Verify that the database is not corrupted, or run the report on a platform that accepts filenames of the specified length.
Level: 1

Type: ERROR

Impact: Other

REP-01820: The Oracle Reports Builder ASCII Driver cannot be used to run a bitmap report.

Cause: An attempt was made to print a bitmapped report when the Oracle Reports Builder ASCII Driver is the default printer.

Action: Select a different printer, then print the report.
Level: 1

Type: ERROR

Impact: Other

REP-01825: The Before Report trigger returned FALSE.

Cause: The report includes a Before Report trigger that returned a value of FALSE rather than TRUE. When a trigger returns a value of FALSE, report formatting stops.

Action: Verify that the report trigger is meant to return a value of FALSE.
Level: 1

Type: ERROR

Impact: Other

REP-01826: The Between Page trigger returned FALSE.

Cause: The report includes a Between Page trigger that returned a value of FALSE rather than TRUE. When a trigger returns a value of FALSE, report formatting stops.

Action: Verify that the report trigger is meant to return a value of FALSE.
Level: 1

Type: ERROR

Impact: Other

REP-01827: Parentheses in the format mask do not balance.

Cause: Unmatched parenthesis exist in the format mask.

Action: Edit the format mask and insert the necessary parenthesis.
Level: 1

Type: ERROR

Impact: Other

REP-01828: A format mask may contain at most one set of parentheses.

Cause: More than one set of parentheses was used in the format mask.

Action: Use only one set of parentheses in the format mask.
Level: 1

Type: ERROR

Impact: Other

REP-01829: Left parenthesis must precede right parenthesis in a format mask.

Cause: The order of the parentheses was reversed in the format mask; that is, the right, or close, parenthesis was used before the left, or open parenthesis.

Action: Edit the format mask and reverse the order of the parentheses.
Level: 1

Type: ERROR

Impact: Other

REP-01830: The Exponent field in a format mask must contain exactly 4 Es.

Cause: The scientific notation specified for the field contained too many or too few E's.

Action: Enter the format mask with four E's. To have extra E's appear in the output, put them in quotation marks (").
Level: 1

Type: ERROR

Impact: Other

REP-01831: A closing quotation mark in format mask is missing.

Cause: An opening quotation mark (") was entered before the string in the format mask, but not a closing one. The possible causes of this error include the following: Case 1: No closing quotation mark was entered after the string. Case 2: One quotation mark was entered within the quotation marks that begin and end the string.

Action: Take the following actions to correct this error: If Case 1: Add an ending quotation mark after the string. If Case 2: Enter another quotation mark next to the quotation mark inside the string.
Level: 1

Type: ERROR

Impact: Other

REP-01832: Illegal character {0} was encountered in the format mask.

Cause: A character was entered in a format mask that is not valid for format masks.

Action: Delete the illegal character. For more information, see the date and time format mask information in the Building Reports manual.
Level: 1

Type: ERROR

Impact: Other

REP-01833: A format mask must contain at least one digit.

Cause: The format mask entered contains no digits. At least one token in the mask must represent a digit.

Action: Enter a token in the format mask that represents a digit. The tokens that represent digits are 0, 9, *, and S. For more information, see the date and time format mask information in the Building Reports manual.
Level: 1

Type: ERROR

Impact: Other

REP-01834: A format mask may contain at most one < character.

Cause: The format mask included two left angle brackets (&lt;&lt;). The angle brackets need not be entered sequentially to cause the error.

Action: Delete the extra left angle bracket or place it inside quotation marks (") as part of a string if it should appear in the output.
Level: 1

Type: ERROR

Impact: Other

REP-01835: A format mask may contain at most one > character.

Cause: The format mask included two right angle brackets (&gt;&gt;). The angle brackets need not be entered sequentially to cause the error.

Action: Delete the extra right angle bracket or place it inside quotation marks (") as part of a string if it should appear in the output.
Level: 1

Type: ERROR

Impact: Other

REP-01836: A left angle bracket must come before a right angle bracket in a format mask.

Cause: The left angle bracket (&lt;) must come before the right angle bracket (&gt;) in a format mask.

Action: Ensure that all angle brackets that are to appear in the output are placed inside quotation marks ("). For the angle brackets that delineate the beginning and ending of the decimal aligned region, ensure that the left angle bracket precedes the right angle bracket in the format mask.
Level: 1

Type: ERROR

Impact: Other

REP-01837: A format mask may contain at most one decimal point.

Cause: A format mask was entered with multiple decimal points.

Action: To have extra decimal points appear in the output, place them in quotation marks ("). Remove any extra decimal points outside of quotation marks.
Level: 1

Type: ERROR

Impact: Other

REP-01838: A format mask may contain at most one scale point.

Cause: The token V was entered more than once within the format mask.

Action: To have extra V's appear in the output, place them in quotation marks ("). Otherwise, delete the V's until there is only one in the format mask.
Level: 1

Type: ERROR

Impact: Other

REP-01839: A comma is not allowed before the first digit in a format mask.

Cause: A comma (,) was entered before the first digit in the format mask, which is illegal.

Action: To have a comma appear before the digits in the output, place it in quotation marks (") as a string. Otherwise, delete the comma.
Level: 1

Type: ERROR

Impact: Other

REP-01840: A comma is not allowed after the last digit in a format mask.

Cause: A comma (,) was entered after the last digit in the format mask, which is illegal.

Action: To have a comma appear after the digits in the output, place it in quotation marks (") as a string. Otherwise, delete the comma.
Level: 1

Type: ERROR

Impact: Other

REP-01841: A comma is not allowed after the decimal point in a format mask.

Cause: A comma (,) was entered after the decimal point in the format mask.

Action: To have a comma appear after the decimal point in the output, place it in quotation marks (") as a string. Otherwise, delete the comma.
Level: 1

Type: ERROR

Impact: Other

REP-01842: A format mask may contain at most one exponent field.

Cause: The token EEEE was entered more than once within the format mask. This token may be entered only once per format mask.

Action: To have the extra E's appear in the output, place them in quotation marks ("). Otherwise, delete the extra EEEE tokens until there is only one in the format mask.
Level: 1

Type: ERROR

Impact: Other

REP-01843: Format masks with exponent fields must have exactly one digit before the decimal point.

Cause: A scientific notation format mask was entered that had no digits or more than one digit to the left of the decimal point.

Action: Delete digits or add a digit until there is only one to the left of the decimal point.
Level: 1

Type: ERROR

Impact: Other

REP-01844: An internal error occurred: Bad index in a flexible array.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01845: The decimal point must come between the angle brackets in a format mask.

Cause: A decimal point was placed outside the left and right angle brackets (\&lt; and \&gt;) of the format mask.

Action: Edit the format mask to either remove the decimal point or place it between the brackets.
Level: 1

Type: ERROR

Impact: Other

REP-01846: A Roman numeral format mask must be simply \"RN\" or \"rn\".

Cause: A Roman numeral format mask token (RN or rn) was specified, along with other format mask tokens.

Action: To format the values as Roman numerals, eliminate all format mask tokens except RN or rn from Format Mask. Otherwise, do not use the RN or rn token.
Level: 1

Type: ERROR

Impact: Other

REP-01847: The current process failed while trying to set up for printing.

Cause: An attempt was made to print a report. The possible causes of this error include the following: Case 1: In the Runtime Parameter Form or on the command line, Printer was specified for DESTYPE, but an invalid printer name was specified for DESNAME. Case 2: The report that was executed in turn executes a second report using SRW.RUN_REPORT. DESTYPE for both reports is set to either File or Printer, but the first report must be run to the screen.

Action: Take the following actions to correct this error: If Case 1: Retry the operation, specifying a valid printer name for DESNAME. If Case 2: Change the DESTYPE for the first report to Screen or Previewer and run it again.
Level: 1

Type: ERROR

Impact: Process

REP-01848: The current process failed while trying to begin printing.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

REP-01849: The current process failed while printing.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

REP-01850: An error occurred in column {0} of line {1} of printer definition file {2}: End of file reached inside quoted string.

Cause: The printer definition file contains a quoted string that was not ended with a quote before the end of the file.

Action: Use the location specified in the error message to locate the error and add the end quote to the quoted string in the printer definition file.
Level: 1

Type: ERROR

Impact: Other

REP-01851: An error occurred in column {0} of line {1} of printer definition file {2}: String is longer than {3} characters.

Cause: A string in the printer definition file is longer than the maximum number of allowable characters.

Action: Reduce the length of the string.
Level: 1

Type: ERROR

Impact: Other

REP-01852: An error occurred in column {0} of line {1} of printer definition file {2}.

Cause: An incorrect keyword is included in the printer definition file.

Action: Verify the printer definition file syntax.
Level: 1

Type: ERROR

Impact: Other

REP-01853: An error occurred in column {0} of line {1} of printer definition file {2}.

Cause: An incorrect keyword was found in the printer definition file.

Action: Verify the printer definition file syntax.
Level: 1

Type: ERROR

Impact: Other

REP-01854: An error occurred in column {0} of line {1} of printer definition file {2}: Invalid control character {3}.

Cause: An invalid control character was found in the printer definition file.

Action: Replace or remove the invalid control character in the printer definition file.
Level: 1

Type: ERROR

Impact: Other

REP-01855: An error occurred in column {0} of line {1} of printer definition file {2}: Unknown character {3}.

Cause: An unknown character was found in the printer definition file.

Action: Replace or remove the unknown character in the printer definition file.
Level: 1

Type: ERROR

Impact: Other

REP-01856: An error occurred in column {0} of line {1} of printer definition file {2}: {3} is not a valid ASCII character.

Cause: An invalid ASCII character appears in the printer definition file.

Action: Replace or remove the invalid ASCII character in the printer definition file.
Level: 1

Type: ERROR

Impact: Other

REP-01857: An error occurred in column {0} of line {1} of printer definition file {2} following {3}.

Cause: An unmatched parenthesis was found in the printer definition file.

Action: Edit the printer definition file and insert the necessary parenthesis.
Level: 1

Type: ERROR

Impact: Other

REP-01858: An error occurred in column {0} of line {1} of printer definition file {2}: octal {3} is not a valid ASCII character.

Cause: The octal code for an ASCII character in the printer definition file is incorrect.

Action: Edit the printer definition file and correct the code for the ASCII character.
Level: 1

Type: ERROR

Impact: Other

REP-01859: An error occurred in column {0} of line {1} of printer definition file {2}: hex {3} is not a valid ASCII character.

Cause: The hex code for an ASCII character in the printer definition file in incorrect.

Action: Edit the printer definition file and correct the code for the ASCII character.
Level: 1

Type: ERROR

Impact: Other

REP-01860: An error occurred in column {0} of line {1} of printer definition file {2}.

Cause: The printer definition file contains an incomplete code string.

Action: Edit the printer definition file and complete the code string with the appropriate word.
Level: 1

Type: ERROR

Impact: Other

REP-01861: An error occurred in column {0} line {1} of file {2}.

Cause: The printer definition file contains an incomplete "box" code string.

Action: Edit the printer definition file and complete the "box" code string with the appropriate word.
Level: 1

Type: ERROR

Impact: Other

REP-01862: An error occurred in column {0} of line {1} of printer definition file {2}.

Cause: The printer definition file does not include the required code "printer".

Action: Edit the printer definition file and add the required code "printer" followed by the name of the printer in a quoted string, preferably on the first line of the printer definition file.
Level: 1

Type: ERROR

Impact: Other

REP-01863: An error occurred in column {0} of line {1} of printer definition file {2}.

Cause: The printer definition file contains the name of the printer after the "printer" code, but the name does not appear in a quoted string.

Action: Edit the printer definition file and place quotation marks (") around the name of the printer after the "printer" code.
Level: 1

Type: ERROR

Impact: Other

REP-01864: An error occurred in column {0} line {1} of file {2}.

Cause: The printer definition file does not contain any of the code words expected in a printer definition file.

Action: Edit the printer definition file and add the code words that are missing.
Level: 1

Type: ERROR

Impact: Other

REP-01865: An error occurred in column {0} of line {1} of printer definition file {2}.

Cause: The printer definition file contains the "width" code, but no number specifying the width of the report appears after it.

Action: Edit the printer definition file and insert a number specifying the width of the report after the "width" code.
Level: 1

Type: ERROR

Impact: Other

REP-01866: An error occurred in column {0} of line {1} of printer definition file {2}.

Cause: The printer definition file contains the "height" code, but no number specifying the height of the report appears after it.

Action: Edit the printer definition file and insert a number specifying the height of the report after the "height" code.
Level: 1

Type: ERROR

Impact: Other

REP-01867: An error occurred in column {0} of line {1} of printer definition file {2}.

Cause: The printer definition file contains the word "before" but not the accompanying word "report".

Action: Edit the printer definition file to include a complete "before report" entry.
Level: 1

Type: ERROR

Impact: Other

REP-01868: An error occurred in column {0} of line {1} of printer definition file {2}.

Cause: The printer definition file contains the word "between" but not the accompanying word "pages".

Action: Edit the printer definition file to include a complete "between pages" entry.
Level: 1

Type: ERROR

Impact: Other

REP-01869: An error occurred in column {0} of line {1} of printer definition file {2}.

Cause: The printer definition file (for a multipage report) contains the code word "after" but not the accompanying word "report".

Action: Edit the printer definition file to include a complete "after report" entry.
Level: 1

Type: ERROR

Impact: Other

REP-01870: An error occurred in column {0} of line {1} of printer definition file {2}.

Cause: The printer definition file contains the "code" code with a user-defined string, but the string is not enclosed within quotation marks.

Action: Edit the printer definition file and enclose the "code" user-defined string with quotation marks.
Level: 1

Type: ERROR

Impact: Other

REP-01871: An error occurred in column {0} of line {1} of printer definition file {2}.

Cause: The printer definition file contains a generalized string using "dec", but "dec" is not followed with a left parenthesis.

Action: Edit the printer definition file and add parentheses around the value following "dec".
Level: 1

Type: ERROR

Impact: Other

REP-01872: An error occurred in column {0} of line {1} of printer definition file {2}.

Cause: The printer definition file contains a generalized string (for example, dec or octal), but no value follows the right parenthesis.

Action: Edit the printer definition file and add a value between the parentheses in the generalized string.
Level: 1

Type: ERROR

Impact: Other

REP-01873: An error occurred in column {0} of line {1} of printer definition file {2}.

Cause: The printer definition file contains a generalized string using "octal", but "octal" is not followed with a left parenthesis.

Action: Edit the printer definition file and add parentheses around the value following "octal".
Level: 1

Type: ERROR

Impact: Other

REP-01874: An error occurred in column {0} of line {1} of printer definition file {2}.

Cause: The printer definition file contains a generalized string (for example, dec or octal), but no value follows the left parenthesis.

Action: Edit the printer definition file and add a value between the parentheses in the generalized string.
Level: 1

Type: ERROR

Impact: Other

REP-01875: An error occurred in column {0} of line {1} of printer definition file {2}.

Cause: The printer definition file contains a generalized string using "hex", but "hex" is not followed with a left parenthesis.

Action: Edit the printer definition file and add parentheses around the value following "hex".
Level: 1

Type: ERROR

Impact: Other

REP-01876: An error occurred in column {0} of line {1} of printer definition file {2}.

Cause: The printer definition file contains a generalized string (for example, dec or octal), but no value follows the left parenthesis.

Action: Edit the printer definition file and add a value between the parentheses in the generalized string.
Level: 1

Type: ERROR

Impact: Other

REP-01877: An error occurred in column {0} of line {1} of printer definition file {2}.

Cause: The printer definition file contains a generalized string using "^", but no control character follows the "^".

Action: Edit the printer definition file and add a control character after "^".
Level: 1

Type: ERROR

Impact: Other

REP-01878: An error occurred in column {0} of line {1} of printer definition file {2}.

Cause: The printer definition file contains a keyword and generalized string (for example, after report or before report), but no left parenthesis follows the word "control".

Action: Edit the printer definition file and add a left parenthesis following the word "control".
Level: 1

Type: ERROR

Impact: Other

REP-01879: An error occurred in column {0} of line {1} of printer definition file {2}.

Cause: The printer definition file contains a keyword and generalized string (for example, after report or before report), but no control character follows the left parenthesis.

Action: Edit the printer definition file and add a control character between the parentheses after the word "control".
Level: 1

Type: ERROR

Impact: Other

REP-01880: An error occurred in column {0} of line {1} of printer definition file {2}.

Cause: The printer definition file contains the "box" code string, but the drawing string specified between quotation marks is more than one character long.

Action: Edit the printer definition file, making sure that one and only one character is specified as a drawing string.
Level: 1

Type: ERROR

Impact: Other

REP-01881: An error occurred in column {0} of line {1} of printer definition file {2}.

Cause: The printer definition file contains the "box" code string, but no drawing string is specified.

Action: Edit the printer definition file and specify a drawing string.
Level: 1

Type: ERROR

Impact: Other

REP-01882: An error occurred in column {0} line {1} of file {2}.

Cause: The printer definition file contains the "box" code string, but the following required word (one of 'horizontal', 'vertical', 'top', 'center', or 'bottom') is not specified.

Action: Edit the printer definition file and add the appropriate required word.
Level: 1

Type: ERROR

Impact: Other

REP-01883: Unexpected end of printer definition file was reached.

Cause: Oracle Reports Builder was able to open the printer definition file, but an error occurred while reading it.

Action: Verify that the correct printer definition file is specified. Also, check the contents of the printer definition file. Edit the file if necessary.
Level: 1

Type: ERROR

Impact: Other

REP-01884: A hang occurred while sending output.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01885: Output could not be sent to the printer.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-01886: Expected I after M in the format mask cannot be found.

Cause: The M entered in a format mask was not followed by I. The only token that begins with M is the MI token.

Action: To use the MI token, enter an I after the M. To have the character M appear in the output, place it inside double quotation marks ("). Otherwise, delete the M from Format Mask.
Level: 1

Type: ERROR

Impact: Other

REP-01887: Expected R after P in the format mask cannot be found.

Cause: The P entered in a format mask was not followed by R. The only token that begins with P is the PR token.

Action: To use the PR token, enter an R after the P. To have the character P appear in the output, place it inside double quotation marks ("). Otherwise, delete the P from Format Mask.
Level: 1

Type: ERROR

Impact: Other

REP-01888: Only one sign token is allowed.

Cause: More than one sign token was entered in a format mask.

Action: Delete all sign tokens but one from the format mask.
Level: 1

Type: ERROR

Impact: Other

REP-01889: A trailing sign token must be at the end.

Cause: A sign token was not placed at the end of the format mask.

Action: Place the sign token (for example, MI, PR, DB, and CR) at the end of the format mask.
Level: 1

Type: ERROR

Impact: Other

REP-01890: The S token must be at the beginning or end.

Cause: The S token was not placed at the beginning or the end of the format mask.

Action: Place the S token at the beginning or the end of the format mask or delete it.
Level: 1

Type: ERROR

Impact: Other

REP-01891: Parentheses tokens must surround other tokens.

Cause: The parentheses tokens do not surround all other tokens in the format mask.

Action: Place the parentheses around all of the other tokens in the format mask.
Level: 1

Type: ERROR

Impact: Other

REP-01892: The destype specified is not supported for pdf or html.

Cause: An invalid destination type (destype) was specified for pdf or html output.

Action: Specify a destination type (destype) of file or cache for pdf or html output.
Level: 1

Type: ERROR

Impact: Other

REP-01893: The destype specified is not supported on this platform.

Cause: An invalid destination type (destype) was specified for the operating system (for example, Sysout, while running on Microsoft Windows).

Action: Specify a valid destination type.
Level: 1

Type: ERROR

Impact: Other

REP-01894: The report definition was modified during the current run. No new pages will be generated.

Cause: While previewing a report (using Oracle Reports Builder), the report's definition was modified, and then an attempt was made to view additional pages from the Previewer. Oracle Reports Builder cannot guarantee that all of the information used at runtime is still present, so formatting is halted.

Action: No action required.
Level: 1

Type: ERROR

Impact: Other

REP-01895: A date formatting error occurred while processing field {0}.

Cause: Oracle Reports Builder could not format the specified date field.

Action: Check the format mask of the specified date field.
Level: 1

Type: ERROR

Impact: Other

REP-01896: An error occurred in column {0} of line {1} of printer definition file {2}: Expected backspace or overstrike to follow hilight.

Cause: The specified printer definition file contains the 'hilight' setting, but the setting was not completed properly.

Action: Add either 'overstrike' or 'backspace &lt;sequence&gt;' after 'hilight'.
Level: 1

Type: ERROR

Impact: Other

REP-01897: An error occurred in column {0} of line {1} of printer definition file {2}: Non-numeric user-defined printer codes are not supported.

Cause: The specified printer definition file contains a user-defined printer code that is not a number.

Action: Change the user-defined printer code to a number.
Level: 1

Type: ERROR

Impact: Other

REP-01898: An error occurred in column {0} of line {1} of printer definition file {2}: Hilight setting can only be defined once.

Cause: The specified printer definition file contains more than one hilight setting.

Action: Remove all but one of the hilight settings from the printer definition file.
Level: 1

Type: ERROR

Impact: Other

REP-01899: Graphics Display or Icon cannot be converted to .gif format - image skipped.

Cause: Oracle Reports Builder was unable to convert an embedded Graphics Display or icon to a GIF format for displaying within an HTML document. This only occurs when Oracle Reports Builder cannot access a window system in order to draw the image.

Action: Run the report using the bitmap executable under a windowing system to allow Oracle Reports Builder access to a display.
Level: 1

Type: ERROR

Impact: Other

REP-01920: Character mode runtime is incompatible with DESFORMAT of PDF, HTML, HTMLCSS, SPREADSHEET, or RTF.

Cause: An attempt was made to run a report with a destination format of PDF, HTML, HTMLCSS, SPREADSHEET, or RTF. These formats are only available when running in a bitmap environment and producing a bitmap output.

Action: Rerun the report with a bitmap executable or set MODE=BITMAP if already running with a bitmap executable.
Level: 1

Type: ERROR

Impact: Other

REP-01921: Input printer tray {0} is not available on the selected printer.

Cause: An attempt was made to alter the input printer tray but the name of the tray specified is not available on the currently selected printer.

Action: Change the selected printer to one that supports the specified tray or alter the tray name to one supported by the specified printer. Use Page Setup to view the list of printer trays supported by the printer.
Level: 1

Type: ERROR

Impact: Other

REP-01922: A PDF compression error was encountered.

Cause: The compression engine failed compressing this page.

Action: Turn off compression for this report by specifying PDFCOMP=NO on command line.
Level: 1

Type: ERROR

Impact: Other

REP-01923: A PDF Font Embed error was encountered.

Cause: The font specified for embedding into the PDF document cannot be found or is invalid.

Action: The [PDF:Embed] section must be present in the uifont.ali file. Check to ensure that the entry of font in the uifont.ali is syntactically correct. Verify that the location of font files is added to REPORTS_PATH in the registry/environment variable.
Level: 1

Type: ERROR

Impact: Other

REP-01924: Font file {0} cannot be found.

Cause: The font file specified in UIFONT.ALI is not found.

Action: Verify that the font file exists in REPORTS_PATH.
Level: 1

Type: ERROR

Impact: Other

REP-01925: Font file {0} is invalid.

Cause: The font file appears to be corrupt or invalid.

Action: Ensure the specified file is a valid font file.
Level: 1

Type: ERROR

Impact: Other

REP-01926: Identical name {0} was specified for dissimilar form field types {1} and {2}.

Cause: The name specified for a form field conflicts with an existing form field of different type.

Action: Select a new name for one of the form fields. Change the type of the form field to match that of the existing form field.
Level: 1

Type: ERROR

Impact: Other

REP-01927: Cannot print document or generate output in printer format because the printer is offline or paused.

Cause: When destination type is printer or format is printer name, running request fails if the printer is offline or paused.

Action: Bring the printer online and try again.
Level: 1

Type: ERROR

Impact: Other

REP-01940: An error occurred in column {0} line {1} of file {2}: Expected visualorder, logicalorder, contextualshaping, contextuallayout, multibyte, or pcharset.

Cause: The printer definition file contains the 'nls' code string, but the required word (one of 'visualorder', 'logicalorder', 'contextualshaping', 'contextuallayout', 'multibyte', or 'pcharset') is not specified.

Action: Edit the printer definition file and add the required word.
Level: 1

Type: ERROR

Impact: Other

REP-01941: An error occurred in column {0} line {1} of file {2}: Expected yes or no.

Cause: The printer definition file contains 'visualorder', 'logicalorder', 'contextualshaping', 'contextuallayout', 'multibyte', or 'pcharset' code string, but the required word (either 'yes' or 'no) is not specified.

Action: Edit the printer definition file and add the appropriate 'yes' or 'no'.
Level: 1

Type: ERROR

Impact: Other

REP-01942: An error occurred in column {0} line {1} of file {2}: Expected name of character set to follow pcharset.

Cause: The printer definition file contains the 'pcharset' code string, but the required string (name of character set) is not specified.

Action: Edit the printer definition file and add the name of character set.
Level: 1

Type: ERROR

Impact: Other

REP-01943: An error occurred in column {0} line {1} of file {2}: Defined printer character set is unsupported.

Cause: The printer definition file contains an unsupported printer character set.

Action: Edit the printer definition file and specify the name of a supported character set.
Level: 1

Type: ERROR

Impact: Other

REP-01944: Invalid reference value {0} was specified for Report property {1}

Cause: The value specified for the indicated property cannot be resolved or is at a wrong frequency.

Action: Ensure that the reference exists and resolves to a valid value. Only Report-level columns can be referenced with this property.
Level: 1

Type: ERROR

Impact: Other

REP-01950: The Source specified is invalid.

Cause: The Source specified for Reports Converter is not a valid source.

Action: Verify that the correct object or file is specified and that the STYPE is correct for that file or object.
Level: 1

Type: ERROR

Impact: Other

REP-01951: The Destination specified is invalid.

Cause: The Destination specified for Reports Converter is not a valid destination.

Action: Verify that the correct object or file is specified and that the DTYPE is correct for that file or object.
Level: 1

Type: ERROR

Impact: Other

REP-01952: The number of Destination items must be zero or match the number of Source items.

Cause: In the Convert dialog box, or while using Reports Converter, the number of Destination items specified was greater than zero and did not match the number of Source items specified.

Action: To have Oracle Reports Builder derive the Destination names from the specified Source names, leave Destination blank. Otherwise, verify that the number of Destination names specified matches the number of Source names specified. If wildcards are used in the Source specification, verify that the number of Destination names matches the number of Source items in the expanded wildcard list.
Level: 1

Type: ERROR

Impact: Other

REP-02000: An error occurred in the user exit.

Cause: An error occurred in the user exit.

Action: Debug the code or contact the database administrator.
Level: 1

Type: ERROR

Impact: Other

REP-02001: An error occurred in IAF GET: unknown column {0}.

Cause: An unknown column name was specified in the user exit's IAF GET statement.

Action: Specify a valid column name in the IAF GET statement.
Level: 1

Type: ERROR

Impact: Other

REP-02002: An error occurred in IAF PUT: unknown column {0}.

Cause: An unknown column name was specified in the user exit's IAF PUT statement.

Action: Specify a valid column name in the IAF PUT statement.
Level: 1

Type: ERROR

Impact: Other

REP-02003: The user exit cannot be found.

Cause: Oracle Reports Builder could not find the user exit that it was supposed to run at this point. The most likely cause is that the name and/or location of the user exit code was not specified correctly.

Action: Verify the name and location of the code when installing it. Otherwise, contact the database administrator.
Level: 1

Type: ERROR

Impact: Other

REP-02004: PL/SQL source code of object {0} could not be retrieved.

Cause: From the File menu, Administration Report was selected to document one or more reports, but the RWEPLS user exit failed to retrieve the PL/SQL source code of an object. This is most likely an abnormal condition.

Action: Check the PL/SQL source code in the named object. For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-02005: An error occurred in IAF PUT: the value of column {0} was truncated.

Cause: The IAF PUT statement assigned a value to the named column, but the column was not wide enough to hold the entire value, causing it to truncate.

Action: Widen the column so that it is can hold the entire value.
Level: 1

Type: ERROR

Impact: Other

REP-02100: An error occurred in Calculation Manager.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-02101: Calculation Manager: the source column cannot use segmented memory.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-02102: Calculation Manager: the computed column cannot use segmented memory.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-02103: The PL/SQL formula returned invalid value or no value for column {0}.

Cause: An SRW.DO_SQL statement was entered that caused this Oracle message.

Action: Edit the SRW.DO_SQL statement. For more information about the Oracle message, see the Oracle Messages and Codes Manual.
Level: 1

Type: ERROR

Impact: Other

REP-02300: Error {0} occurred.

Cause: An SRW.DO_SQL statement was entered that caused this Oracle message.

Action: Edit the SRW.DO_SQL statement. For more information about the Oracle message, see the Oracle Messages and Codes Manual.
Level: 1

Type: ERROR

Impact: Other

REP-02301: An error occurred allocating a SQLDA descriptor: {0}.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-02302: An error occurred parsing the SQL statement: {0}.

Cause: Oracle Reports Builder encountered an error while parsing the SRW.DO_SQL statement.

Action: Refer to the Oracle message to see why the SQL statement could not be parsed.
Level: 1

Type: ERROR

Impact: Other

REP-02303: An error occurred describing bind variables: {0}.

Cause: Oracle Reports Builder encountered an error while describing bind variables in an SRW.DO_SQL statement.

Action: Refer to the Oracle message to see why the bind variables could not be described.
Level: 1

Type: ERROR

Impact: Other

REP-02304: An error occurred opening a SQL cursor: {0}.

Cause: Oracle Reports Builder encountered an error while opening a cursor in an SRW.DO_SQL statement.

Action: Refer to the Oracle message to see why the cursor could not be opened.
Level: 1

Type: ERROR

Impact: Other

REP-02305: An error occurred describing the SELECT list: {0}.

Cause: Oracle Reports Builder encountered an error while describing the SELECT list in an SRW.DO_SQL statement.

Action: Refer to the Oracle message to see why the bind variables could not be described.
Level: 1

Type: ERROR

Impact: Other

REP-02306: An error occurred fetching bind variables: {0}.

Cause: Oracle Reports Builder encountered an error while fetching bind variables in an SRW.DO_SQL statement.

Action: Refer to the Oracle message to see why the bind variables could not be fetched.
Level: 1

Type: ERROR

Impact: Other

REP-02307: An error occurred fetching a data record: {0}.

Cause: Oracle Reports Builder encountered an error while fetching a data record in an SRW.DO_SQL statement.

Action: Refer to the Oracle message to see why the data record could not be fetched.
Level: 1

Type: ERROR

Impact: Data

REP-02308: An error occurred processing the SELECT list: {0}.

Cause: Oracle Reports Builder encountered an error while processing the SELECT list in an SRW.DO_SQL statement.

Action: Refer to the Oracle message to see why the SELECT list is invalid.
Level: 1

Type: ERROR

Impact: Other

REP-02309: An error occurred formatting a date field: {0}.

Cause: Oracle Reports Builder encountered an error while formatting a date field in an SRW.DO_SQL statement.

Action: Refer to the Oracle message to see why the date field could not format.
Level: 1

Type: ERROR

Impact: Other

REP-02310: An error occurred putting a value into a column: {0}.

Cause: Oracle Reports Builder encountered an error while trying to insert a value into a column in an SRW.DO_SQL statement.

Action: Refer to the Oracle message to see why the value could not be assigned.
Level: 1

Type: ERROR

Impact: Other

REP-02311: An error occurred during Commit: {0}.

Cause: Oracle Reports Builder encountered an error while trying to do a commit in an SRW.DO_SQL statement.

Action: Refer to the Oracle message to see why the commit failed.
Level: 1

Type: ERROR

Impact: Other

REP-02312: An error occurred allocating a data record: {0}.

Cause: Oracle Reports Builder encountered an error while allocating a data record in an SRW.DO_SQL statement.

Action: Refer to the Oracle message to see why the record could not be allocated.
Level: 1

Type: ERROR

Impact: Data

REP-02313: An error occurred parsing the SELECT list: {0}.

Cause: Oracle Reports Builder encountered an error while parsing the SELECT list in an SRW.DO_SQL statement.

Action: Refer to the Oracle message to see why the SELECT list could not be parsed.
Level: 1

Type: ERROR

Impact: Other

REP-02314: An error occurred closing a SQL cursor: {0}.

Cause: Oracle Reports Builder encountered an error while trying to close a SQL cursor in an SRW.DO_SQL statement.

Action: Refer to the Oracle message to see why the close cursor operation failed.
Level: 1

Type: ERROR

Impact: Other

REP-02315: An error occurred freeing a data record: {0}.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Data

REP-02316: Column {0} cannot be found.

Cause: A column referred to in an SRW.DO_SQL statement cannot be found.

Action: Debug the PL/SQL and verify that the SRW.DO_SQL statement contains the correct column name.
Level: 1

Type: ERROR

Impact: Other

REP-02317: The value of column {0} was truncated.

Cause: A column value obtained via an SRW.DO_SQL statement was truncated.

Action: Go to the column's Property Inspector and increase its Width. Or, restrict the size of the value that the SRW.DO_SQL statement is putting into the column.
Level: 1

Type: ERROR

Impact: Other

REP-02400: DEBUG: internal error 0 occurred.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-02500: Error {0} occurred. See the Release Notes for further information about this error

Cause: The error is documented in the Release Notes.

Action: See the Release Notes.
Level: 1

Type: ERROR

Impact: Other

REP-02550: The in-process server was not started: {0}.

Cause: An abnormal condition was encountered.

Action: Refer to the in-process server message to see why it failed to start. Then restart the Oracle Reports Builder.
Level: 1

Type: ERROR

Impact: Other

REP-03000: An internal error occurred starting Oracle Toolkit.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03001: An internal error occurred initializing the File Dialog.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03002: An error occurred initializing the printer. Verify that a printer is installed.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03020: An internal error occurred starting Oracle Resource Manager.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03021: An internal error occurred processing a menu resource.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03022: An internal error occurred processing a window resource.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03023: The resource file cannot be found.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03040: An internal error occurred starting Oracle Observer Model.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03060: An internal error occurred initializing the color table. Checking VGS resources is recommended.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03080: An internal error occurred initializing Oracle Image.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03081: An error occurred running the image viewer.

Cause: A Previewer button was selected with a defined action of displaying an image, but the image viewer is unavailable. Possible causes of this error include: Case 1: The image specified as the source is in an incorrect format. Case 2: There is no available memory. Case 3: An abnormal condition was encountered.

Action: Take the following actions to correct this error: If Case 1: Ensure that the image file specified as the source of the button action is in a displayable format. If Case 2: Make more memory available, if possible, or ask the system administrator for assistance. If Case 3: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03082: An error occurred running the sound dialog.

Cause: A Previewer button was selected with a defined action of playing a sound, but the sound dialog is unavailable. Possible causes of this error include: Case 1: The sound file specified as the source is in an incorrect format. Case 2: There is no available memory. Case 3: An abnormal condition was encountered.

Action: Take the following actions to correct this error: If Case 1: Ensure that the sound file specified as the source of the button action is in a playable format. If Case 2: Make more memory available, if possible, or ask the system administrator for assistance. If Case 3: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03083: An error occurred running the video player.

Cause: A Previewer button was selected with a defined action of playing a video, but the video player is unavailable. Possible causes of this error include: Case 1: The video file specified as the source is in an incorrect format. Case 2: There is no available memory. Case 3: An abnormal condition was encountered.

Action: Take the following actions to correct this error: If Case 1: Ensure that the video file specified as the source of the button action is in a playable format. If Case 2: Make more memory available, if possible, or ask the system administrator for assistance. If Case 3: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03085: Multimedia source file {0} cannot be found.

Cause: The button was clicked in the Previewer, but the source for the button's intended action (whether sound, image, or video) cannot be found or has been corrupted.

Action: Open the Property Inspector for the button in question and verify the existence, format, and path information for the specified source file.
Level: 1

Type: ERROR

Impact: Other

REP-03086: The multimedia source file is not available.

Cause: The button was clicked in the Previewer, but the source for the button's intended action (whether sound, image, or video) has been corrupted.

Action: Open the Property Inspector for the button in question and verify the existence, format, and path information for the specified source file. If it is correct, check the file itself.
Level: 1

Type: ERROR

Impact: Other

REP-03087: ImageViewer is not supported in this configuration.

Cause: The platform or configuration does not support displaying images via the ImageViewer.

Action: No action is necessary.
Level: 1

Type: ERROR

Impact: Other

REP-03088: Sound is not supported in this configuration.

Cause: The platform or configuration does not support playback of sound files.

Action: No action is necessary.
Level: 1

Type: ERROR

Impact: Other

REP-03089: Video is not supported in this configuration.

Cause: The platform or configuration does not support playback of video files.

Action: No action is necessary.
Level: 1

Type: ERROR

Impact: Other

REP-03100: A matrix must include at least 1 Down and 1 Across repeating frame.

Cause: An attempt was made to create a matrix (selecting Arrange, then Create Matrix) without the proper objects selected in the Paper Layout editor. A matrix layout requires that at least one group have a repeat direction of Down and one have a repeat direction of Across.

Action: Select two repeating frames--one Down, one Across--that overlap, then select Create Matrix from the Arrange Menu.
Level: 1

Type: ERROR

Impact: Other

REP-03101: All selected Down and Across repeating frames must be nested.

Cause: An attempt was made to create a matrix (selecting Arrange, then Create Matrix) and the Down and Across repeating frames were not properly overlapping and nested.

Action: Verify that the selected Down and Across repeating frames are properly overlapping and nested before creating the matrix.
Level: 1

Type: ERROR

Impact: Other

REP-03102: Anchors, matrices, and margins cannot be grouped.

Cause: Group was selected from the Arrange menu and at least one of the objects selected was an anchor, matrix, or margin.

Action: Deselect all anchors, matrices, and margins before grouping objects.
Level: 1

Type: ERROR

Impact: Other

REP-03103: Only text and graphical boilerplate objects can be rotated.

Cause: An attempt was made to rotate a frame, a field, a margin, an anchor, a matrix object, a file link boilerplate object, or a graph. None of these can be rotated.

Action: Rotate any boilerplate objects except images and file link boilerplate objects. Depending on the operating system, the text of a rotated boilerplate text object may or may not be visible.
Level: 1

Type: ERROR

Impact: Other

REP-03104: Anchors and matrices cannot be scaled separately from their associated objects.

Cause: An attempt was made to scale one of the layout objects listed above without also scaling its associated object, which is not allowed.

Action: Select at least one associated object (anchoring object for anchors, repeating frames for matrices), then retry the scaling operation.
Level: 1

Type: ERROR

Impact: Other

REP-03105: A graph Column must be selected for the graph Query.

Cause: A name was entered for the graph Query, but no graph Columns were selected. If a graph Query is specified, graph Columns must also be specified.

Action: Specify graph Columns or remove the value from the graph Query.
Level: 1

Type: ERROR

Impact: Other

REP-03106: a graph Column was selected without a graph Query name. The selected graph Column will be ignored.

Cause: A Source or graph Column was selected but a name for a graph Query was not entered.

Action: Enter the name of the graph query to which to pass data.
Level: 1

Type: ERROR

Impact: Other

REP-03107: Object {0} cannot be moved in front of its child {1}.

Cause: An attempt was made to move a layout object in front of one or more of its own child objects.

Action: To move the layout object, toggle Confine mode off, then move it. Otherwise, no action is necessary.
Level: 1

Type: ERROR

Impact: Other

REP-03108: Object {0} cannot be moved behind its container {1}.

Cause: An attempt was made to move a layout object behind one or more of its own parent objects.

Action: To move the layout object, toggle Confine mode off, then move it. Otherwise, no action is necessary.
Level: 1

Type: ERROR

Impact: Other

REP-03109: The alignment operation failed because of container constraints.

Cause: An attempt was made to align multiple layout objects but the result of such an operation would have violated container constraints (that is, moved a field outside of its enclosing frame).

Action: Select Edit, then Undo to ensure the layout is the same as before the attempted operation. Then, either resize or reposition the container in question to perform the operation, or do nothing.
Level: 1

Type: ERROR

Impact: Other

REP-03110: Same size operation failed because of container constraints.

Cause: An attempt was made to change one or more layout objects to the same size, but the result of such an operation would have violated container constraints (that is, enlarged a field beyond its enclosing frame).

Action: Select Edit, then Undo to ensure the layout is the same as before the attempted operation. Then, either resize or reposition the container in question to perform the operation, or do nothing.
Level: 1

Type: ERROR

Impact: Other

REP-03111: Changing the border width of {0} violates the constraints of confined mode.

Cause: An attempt was made to change the border width of an object such that the result would have violated container constraints (that is, widening the border of a boilerplate object so that it extended beyond its enclosing frame).

Action: No action is necessary.
Level: 1

Type: ERROR

Impact: Other

REP-03112: Objects cannot be created in the template layout body layer.

Cause: An attempt was made to create an object in the layout body layer of a template. Objects may only be created in the margin, header pages, or trailer pages of a template.

Action: No action is necessary.
Level: 1

Type: ERROR

Impact: Other

REP-03130: Parameter Form fields and images cannot be rotated.

Cause: An attempt was made to rotate one of the Parameter Form objects, which is not allowed.

Action: Rotate any boilerplate objects, except images, in the Parameter Form editor. Depending on the operating system, the text of boilerplate text that is rotated may or may not be visible.
Level: 1

Type: ERROR

Impact: Other

REP-03131: Parameter Form boilerplate text cannot fit on the page.

Cause: Text was entered in the Title, Hint, Status, or Label field in the Parameter Form Builder that is too long to fit on the page.

Action: Reduce the length of the appropriate text field.
Level: 1

Type: ERROR

Impact: Other

REP-03140: A Program Unit Editor internal error occurred: Could not get document handle.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03150: One editor must remain open for each report.

Cause: An attempt was made to close all three of the editors (Data Model, Layout, and Parameter Form) for a report. At least one editor must remain open.

Action: Leave one editor open for each report.
Level: 1

Type: ERROR

Impact: Other

REP-03151: The width for column {0} is invalid and cannot be highlighted, since group {1} is not selected.

Cause: An invalid value was entered for the Width of a column in the Report Wizard. Since the group that owns the column is not selected, the column is not listed.

Action: Select the group that owns the column. Scroll down to the column and enter a valid value for Width.
Level: 1

Type: ERROR

Impact: Other

REP-03152: The link, anchor, or polygon creation must be completed in the editor before this action.

Cause: An attempt was made to perform some action (for example, close the report) before finishing the creation of a data link in the Data Model editor, an anchor in the Paper Layout editor, or a polygon in the Paper Layout editor or Parameter Form editor.

Action: Complete the unfinished object before continuing.
Level: 1

Type: ERROR

Impact: Other

REP-03153: Insufficient resources are available to create the window.

Cause: There were insufficient resources available to create the requested window.

Action: Make more resources available by closing windows or other applications.
Level: 1

Type: ERROR

Impact: Other

REP-03154: Insufficient resources are available to create the document.

Cause: There were insufficient resources available to create the requested document (report, external query, PL/SQL library).

Action: Make more resources available by closing windows or other applications.
Level: 1

Type: ERROR

Impact: Other

REP-03200: Concurrent previewer actions are not allowed.

Cause: An attempt was made to activate more than one button at one time, in either the same or multiple Previewers. For example, play a sound and display a video at the same time.

Action: Activate only one button at a time.
Level: 1

Type: ERROR

Impact: Other

REP-03290: Query Builder does not support lexical parameters.

Cause: An attempt was made to pass lexical parameters to Query Builder, which is not supported. Query Builder only supports bind parameters.

Action: Remove all lexical parameters from the query and reenter Query Builder.
Level: 1

Type: ERROR

Impact: Other

REP-03300: A fatal error occurred: {0}.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03301: An error occurred: {0}.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03302: A fatal error occurred during Quit. Exiting Oracle Reports Builder.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03335: An unhandled internal CA error occurred.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03350: An unhandled internal UI error occurred.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03351: An undefined failure in the UI occurred.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03352: An unexpected error in the UI occurred.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03353: The attribute cannot be created.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03354: The attribute cannot be set.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03355: The attribute cannot be set or retrieved.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03356: The unknown attribute cannot be set or retrieved.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03357: The attributes values are conflicting and cannot be set.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03358: The attribute cannot be set to an out of range value.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03359: This function call is out of context.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03360: The view class does not support being a scrollee.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03361: This function call provokes an illegal recursion.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03362: The internal API memory allocator failed.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Memory

REP-03363: The client supplied memory allocation functions failed.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Memory

REP-03364: An attempt to use an unsupported function failed.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03365: Attributes cannot be set out of context.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03366: An attempt to perform an illegal operation on a root view failed.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03367: One of the parameters to the functions is out of range.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03368: The connection to the windowing system failed.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03369: The connection to the windowing system is broken.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03370: The windowing system failed.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03371: uiER_CL_FORMAT_UNAVAILABLE

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03372: uiER_CL_FORMAT_UNREGISTERED

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03373: The operation timed out.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03374: uiER_NOT_FOUND

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03375: uiER_ILLEGAL_TOPITEM

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03376: uiER_SE_BAD_FORMAT

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03377: The view class does not support the scroller interface.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03378: An attempt to remove a readshare color from a palette failed.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03379: An attempt to create a window failed.

Cause: Oracle Reports Builder was unable to create a window. There may be too many reports or windows open, and lack of memory resources.

Action: Close some reports and windows.
Level: 1

Type: ERROR

Impact: Other

REP-03380: An attempt to create a view failed.

Cause: Oracle Reports Builder was unable to create a view. There may be too many reports or windows open, and lack of memory resources.

Action: Close some reports and windows.
Level: 1

Type: ERROR

Impact: Other

REP-03381: An attempt to create a color palette failed.

Cause: Oracle Reports Builder was unable to create a color palette. There may be too many reports or windows open, and lack of memory resources.

Action: Close some reports and windows.
Level: 1

Type: ERROR

Impact: Other

REP-03400: An error occurred initializing DE. Checking DE resources is recommended.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03420: An internal error occurred in Oracle Reports Builder.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03430: An unhandled internal HH error occurred.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03431: The attribute value is invalid.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03432: The context is invalid.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03433: The specified word cannot be found.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03434: A link to external document was found.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03435: The help session is null.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03436: The document is not a help document.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03437: The document revision is newer than help.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03438: The specified attribute is not settable.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03439: The specified attribute is not gettable.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03440: The link is invalid.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03441: Logical attributes are missing or bad.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03442: The NLS language string is missing or bad.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03443: No search string is specified.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03444: The string begins with a percent sign.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03445: An unknown toolkit error occurred.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03446: An unknown object store error occurred.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03447: An out of memory condition occurred.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Memory

REP-03448: An unknown Resource Manager error occurred.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03480: An unhandled internal REM error occurred.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03485: An unhandled internal VGS error occurred.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03500: An unhandled internal UT error occurred.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03510: An unhandled internal ZOM error occurred.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03600: Both document nodes and non-document nodes selected. Select only nodes from one of these types of nodes.

Cause: Navigator&gt;Delete was selected, but both object nodes and document nodes are selected. Documents cannot be closed and deleted in the same action.

Action: To delete objects, deselect all document nodes. To close documents, deselect all object nodes. Then select Navigator&gt;Delete again.
Level: 1

Type: ERROR

Impact: Other

REP-03601: This report style can only have one Section.

Cause: Tabular, Form Letter, and Mailing Label report styles have only one Section each.

Action: Specify all overrides in the existing Section.
Level: 1

Type: ERROR

Impact: Other

REP-03602: The minimum number of levels cannot be deleted.

Cause: Tabular, Form Letter, and Mailing Label report styles have one Section each. Group Above and Group Left report styles have two sections each. Matrix and Matrix Group have one section under each normal, across, and down cell.

Action: Verify that the particular report style has the minimum number of levels.
Level: 1

Type: ERROR

Impact: Other

REP-03700: Selection Observer initialization failed.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-03701: Selection Observer failed while shutting down.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-04001: An error occurred in the OLE subsystem.

Cause: An unspecified OLE2 error occurred during initialization. Refer to the accompanying OLE error message for more information. Other possible causes of this error include the following: Case 1: The OLE2 server is not functioning correctly. Case 2: An error occurred during installation of Oracle Reports Builder and the OLE2 functionality did not install correctly. Case 3: An abnormal condition was encountered.

Action: Take the following actions to correct this error: If Case 1: Refer to the OLE2 server documentation for more information. If Case 2: Reinstall Oracle Reports Builder. If Case 3: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-04002: An error occurred while initializing OLE subsystem.

Cause: An error occurred during initialization of OLE2 libraries. Refer to the accompanying OLE error message for more information. Other possible causes of this error include the following: Case 1: The OLE2 server is not functioning correctly. Case 2: An error occurred during installation of Oracle Reports Builder and the OLE2 functionality did not install correctly. Case 3: An abnormal condition was encountered.

Action: Take the following actions to correct this error: If Case 1: Refer to the OLE2 server documentation for more information. If Case 2: Reinstall Oracle Reports Builder. If Case 3: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-04003: An error occurred while creating OLE object.

Cause: An attempt was made to create an OLE2 object when an OLE error occurred.

Action: Refer to the accompanying OLE2 error message for more information.
Level: 1

Type: ERROR

Impact: Other

REP-04004: An error occurred while restoring OLE object.

Cause: An attempt was made to restore an OLE2 object when an OLE error occurred.

Action: Refer to the accompanying OLE2 error message for more information.
Level: 1

Type: ERROR

Impact: Other

REP-04005: An error occurred while saving OLE object.

Cause: An attempt was made to save an OLE2 object when an OLE error occurred.

Action: Refer to the accompanying OLE2 error message for more information.
Level: 1

Type: ERROR

Impact: Other

REP-04006: An error occurred while performing a cut/copy operation. An OLE object is not placed in the clipboard.

Cause: An attempt was made to cut or copy an OLE2 object when an OLE error occurred.

Action: Refer to the accompanying OLE2 error message for more information.
Level: 1

Type: ERROR

Impact: Other

REP-04007: An error occurred while pasting OLE object from clipboard.

Cause: An attempt was made to paste an OLE2 object from the clipboard when an OLE error occurred.

Action: Refer to the accompanying OLE2 error message for more information.
Level: 1

Type: ERROR

Impact: Other

REP-04008: An error occurred while trying to perform operation defined by an OLE object.

Cause: An attempt was made to perform an action normally supported by the OLE2 server when an OLE error occurred.

Action: Refer to the accompanying OLE error message for more information.
Level: 1

Type: ERROR

Impact: Other

REP-04009: An error occurred while trying to activate an OLE object.

Cause: An attempt was made to activate an OLE2 object (for example, double-click on it in the Previewer) when an OLE error occurred.

Action: Refer to the accompanying OLE2 error message for more information.
Level: 1

Type: ERROR

Impact: Other

REP-04020: Conversion of OLE object to a different type failed.

Cause: An attempt was made to convert an OLE2 object contained in a piece of boilerplate to an OLE2 object of a different type when an OLE error occurred. This indicates a problem with the OLE2 server.

Action: Check that the object is correctly installed and reinstall, if necessary.
Level: 1

Type: ERROR

Impact: Other

REP-04021: Microsoft Object Linking and Embedding is not supported on this platform

Cause: An attempt was made to run a report that was created on a platform supporting OLE2, and created with OLE2 objects, on a platform that does not support OLE2.

Action: No action is necessary. Remove the object if desired.
Level: 1

Type: ERROR

Impact: Other

REP-04022: The incorrect version of OLE libraries are installed. OLE functionality will be disabled.

Cause: The OLE2 libraries installed are incompatible with those supported by the installed version of Oracle Reports Builder. As Oracle Reports Builder cannot guarantee that the OLE2 support will function, it disabled OLE2 functionality.

Action: Install the correct libraries.
Level: 1

Type: ERROR

Impact: Other

REP-04023: There is insufficient memory available to complete the operation.

Cause: There is not sufficient memory remaining on the system to perform the desired action.

Action: Exit any unnecessary applications that are running. If that does not work, see the Microsoft documentation for suggested procedures to enhance memory usage.
Level: 1

Type: ERROR

Impact: Memory

REP-04024: DOS SHARE services are required for successful operation. SHARE is not running.

Cause: The DOS SHARE utility is required, but SHARE is not running.

Action: Verify that SHARE is running.
Level: 1

Type: ERROR

Impact: Other

REP-04025: A read failure occurred.

Cause: Data cannot be read from the specified device.

Action: Check the device to determine if it is malfunctioning, and, if so, consult the device documentation to determine the proper error recovery procedures.
Level: 1

Type: ERROR

Impact: Other

REP-04026: A write failure occurred.

Cause: Data cannot be written to the specified device.

Action: Check the device to determine if it is read-only. If not, consult the device documentation to determine the proper error recovery procedures.
Level: 1

Type: ERROR

Impact: Other

REP-04027: Too many files opened. There are insufficient resources to open another file.

Cause: An attempt was made to open more files than are supported by Windows.

Action: Close some applications. Also, check the config.sys file and ensure that FILES is not set below 20. Note: Remember that OLE2 boilerplate objects reserve either two or three file handles per object and so there may be more files open than expected.
Level: 1

Type: ERROR

Impact: Other

REP-04028: No space is left on the device.

Cause: The device is full.

Action: Delete unnecessary data or write to a different device.
Level: 1

Type: ERROR

Impact: Other

REP-04029: Presentation of the OLE object failed. Cannot render OLE object.

Cause: An attempt was made to display an OLE2 object in a report but the display aspects defined by the OLE2 server were unavailable.

Action: Verify that the OLE2 object has not been corrupted and that the server is correctly installed. Reinstall if necessary.
Level: 1

Type: ERROR

Impact: Other

REP-04030: Restoration of original display aspects of the OLE object failed. Object content will be used.

Cause: An attempt was made to display an OLE2 object in a report but the display aspects defined by the OLE2 server were corrupted or stored in the database and could not be restored. Oracle Reports Builder will display the object using the default aspect.

Action: Verify that the OLE2 server is correctly installed. Reinstall if necessary.
Level: 1

Type: ERROR

Impact: Other

REP-04031: The server application cannot be found.

Cause: An attempt was made to access an OLE2 server via an OLE2 object, but the server is currently inaccessible. The server may have been deleted, renamed, or manually reinstalled in a different location.

Action: Check the installation of the server and reinstall if necessary.
Level: 1

Type: ERROR

Impact: Other

REP-04032: Connection to the linked OLE object source failed.

Cause: Oracle Reports Builder is trying to connect to the specified source of the OLE2 object boilerplate but cannot.

Action: Verify that the OLE2 object source has not been moved or deleted, and that its file name has not been changed.
Level: 1

Type: ERROR

Impact: Other

REP-04033: Connection to the linked object source failed, because it is across a network that is not connected to this machine.

Cause: An attempt was made to link to an OLE2 object that is stored on a device to which there is no established network connection.

Action: Establish a connection to the proper device.
Level: 1

Type: ERROR

Impact: Network

REP-04034: A file cannot be not found or an invalid file name is used by an OLE object.

Cause: An OLE2 object is attempting to access a file that it cannot find.

Action: Verify that the file has not been corrupted, moved, or renamed.
Level: 1

Type: ERROR

Impact: Other

REP-04035: A share violation has occurred while performing operation on OLE object.

Cause: Possible causes: an attempt was made to link to the same file via multiple OLE2 objects, or to access the same temporary file via different applications.

Action: Verify multiple OLE2 objects are not attempting to access the same file at the same time. Also, check the intallation of the OLE2 server.
Level: 1

Type: ERROR

Impact: Other

REP-04036: Access was denied while performing an operation on an OLE object.

Cause: An attempt was made to update an OLE2 object without write access.

Action: Obtain the proper permissions to the file before trying to update it.
Level: 1

Type: ERROR

Impact: Other

REP-04037: File operation on OLE object failed because disk is write-protected.

Cause: An attempt was made to save to file an OLE2 object but it failed because the disk is write-protected.

Action: Save the object to a disk with write privileges, if possible. If not, no action is necessary.
Level: 1

Type: ERROR

Impact: Other

REP-04038: Unexpected error occurred in the file system while performing an operation on an OLE object.

Cause: A non-specific file error such as a corruption of the hard disk occurred.

Action: Refer to the operating system documentation more information.
Level: 1

Type: ERROR

Impact: Other

REP-04039: An unexpected error was returned by OLE.

Cause: A non-specific OLE error occurred.

Action: Refer to the Microsoft documentation for more information.
Level: 1

Type: ERROR

Impact: Other

REP-04040: Incorrect or corrupted OLE object persistent data was encountered. The OLE object cannot be restored from this data

Cause: The information used by the OLE server to restore the OLE2 object in the report is incorrect or has been corrupted. Possible causes for this error include: Case 1: If boilerplate, the file has become corrupted. Case 2: If field, either the database has been corrupted, or the LONG RAW column referenced does not contain OLE2 objects.

Action: Take the following actions to correct this error: If Case 1: Verify that the object is viable by embedding it in a container using another application. If Case 2: Use SQL*Plus to check the table in the database and verify the contents of the column.
Level: 1

Type: ERROR

Impact: Data

REP-04041: No operations are defined on this object or the object is static.

Cause: An attempt was made to take some action on an OLE2 object but no actions have been defined as applying to the object. Possibly the object was converted to a static bitmap.

Action: No action is necessary.
Level: 1

Type: ERROR

Impact: Other

REP-04042: The requested action on the OLE object is valid, but cannot be performed at this moment. The object server may be busy.

Cause: An attempt to take a valid action on an OLE2 object failed, due to lack of server resources. A possible cause is that an attempt was made to open a second instance of a single-instance application.

Action: Check system resources (such as memory) and increase where possible, or try the operation later.
Level: 1

Type: ERROR

Impact: Other

REP-04043: The operation requested on the object is invalid and cannot be performed.

Cause: The action attempted on an OLE2 object was not recognized as valid.

Action: Verify that the proper version of the OLE server is correctly installed. Reinstall if necessary.
Level: 1

Type: ERROR

Impact: Other

REP-04044: The system registry cannot be accessed.

Cause: A read or write operation in the system registry failed.

Action: Verify that there are enough free system resources and the registry is not corrupted. Consult the Microsoft documentation.
Level: 1

Type: ERROR

Impact: Other

REP-04045: A problem occurred in the system registry.

Cause: Some information about the server is missing from the registry.

Action: Verify that the OLE server is installed correctly. Reinstall if necessary.
Level: 1

Type: ERROR

Impact: Other

REP-04100: An attempt to execute data source failed.

Cause: An internal error occurred while executing the specific pluggable data source.

Action: Look for more details in the engine trace.
Level: 1

Type: ERROR

Impact: Data

REP-04101: An attempt to create conditions for pluggable data source failed.

Cause: An internal error occurred while creating conditions for the specific pluggable data source.

Action: Look for more details in the engine trace in case of a custom PDS.
Level: 1

Type: ERROR

Impact: Data

REP-04102: An attempt to fetch pluggable data source failed.

Cause: An internal error occurred when fetching the resultset of the pluggable data source.

Action: Look for more details in the engine trace in case of a custom PDS.
Level: 1

Type: ERROR

Impact: Data

REP-04103: An attempt to set up pluggable data source driver failed.

Cause: An internal error occurred.

Action: Verify the installation. For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Data

REP-04104: Pluggable data source {0} references unknown column {1}

Cause: An invalid column is being referenced in the pluggable data source query.

Action: Verify the PDS query.
Level: 1

Type: ERROR

Impact: Data

REP-04105: An attempt to create pluggable data source factory {0} failed.

Cause: The pluggable data source factory class specification in the preference file is invalid.

Action: Validate the specification of pluggable data source factory classes in the preference file.
Level: 1

Type: ERROR

Impact: Data

REP-04106: An attempt to edit the query failied because it was created with a later version ({0}) of pluggable data source factory {1}.

Cause: Query was created with a later version of pluggable data source factory than the current Builder session's registered factory. For this to occur, the major version of the factories must be different. Major version is the value left of the decimal point in the factory version number.

Action: Upgrade the registered Oracle Reports Builder pluggable data source factory to one with the equivalent major version number.
Level: 1

Type: ERROR

Impact: Data

REP-04107: The query will be upgraded from version {0} to current factory version {1}.

Cause: The query was created with an earlier version of pluggable data source factory than the current Builder session's registered factory. For this to occur, the major version of the factories must be different. Major version is the value left of the decimal point in the factory version number.

Action: No action is necessary. The query will be automatically upgraded to the version number of the current factory.
Level: 1

Type: ERROR

Impact: Other

REP-04108: The version of the query {0} is different from the pluggable data source factory {1}.

Cause: The query was created with version of pluggable data source factory that is slightly different than the current Builder session's registered factory. For this to occur, the minor version of the factories must be different. Minor version is the value right of the decimal point in the factory version number.

Action: No action is necessary. The Edit operation will proceed.
Level: 1

Type: ERROR

Impact: Data

REP-04109: Factory {0} is not a registered factory class.

Cause: The factory class may not be specified correctly in the preference file.

Action: Verify that the factory class is specified correctly in the preference file.
Level: 1

Type: ERROR

Impact: Other

REP-04110: Query definition for query {0} cannot be found.

Cause: Oracle Reports Builder could not connect to the data source referred in the query.

Action: Check the connection information for the PDS query.
Level: 1

Type: ERROR

Impact: Other

REP-04111: Pluggable data source {0} cannot be created.

Cause: Case 1: There is no JVM. Case 2: There is no Oracle Reports pluggable data source driver. Case 3: Pluggable data source class failed to return new pluggable data source object.

Action: In Case 1: Check the Oracle Reports and Java installation on the machine. In Case 2: Check if the correct Oracle Reports jar file is in the right place. In Case 3: Check if the right pluggable data source class is in place.
Level: 1

Type: ERROR

Impact: Data

REP-04112: Oracle Reports Builder can not display the image for pluggable data source {0}.

Cause: The bitmap image may be corrupted.

Action: Verify that the bitmap image is not corrupted by confirming that it is saved in .gif format and it can be viewed in the appropriate image tool.
Level: 1

Type: ERROR

Impact: Data

REP-04113: Changing the type of pluggable data source bound to this parameter may affect query behavior in the Data Model.

Cause: An attempt was made to change a query of one PDS type to another.

Action: Verify any parameters used in the query when changing PDS type.
Level: 1

Type: ERROR

Impact: Data

REP-04200: An error occurred in the Mail subsystem.

Cause: An unspecified error occurred during one of the mail operations. Refer to the accompanying error message for more information. Other possible causes of this error include the following: Case 1: MAPI is not properly installed. Case 2: The Windows mail service provider is not properly installed.

Action: Take the following actions to correct this error: If Case 1: For other applications using MAPI, check to see if they are functioning properly. If not, try reinstalling MAPI. If Case 2: Verify that the Windows mail service provider is installed, and a mail account exists on the system. For assistance, ask the mail administrator.
Level: 1

Type: ERROR

Impact: Other

REP-04201: An error occurred while initializing the Mail subsystem.

Cause: Oracle Reports Builder tried to initialize MAPI, and could not. Refer to the accompanying error message for more information. Other possible causes of this error include the following: Case 1: MAPI is not installed, the MAPI DLL is out of date, or the Mail entry in the WIN.INI file or registry points to the wrong location. Case 2: There is not enough memory available to perform the operation. Case 3: While logging on, an invalid service profile name, username, or password was entered.

Action: Take the following actions to correct this error: If Case 1: Reinstall MAPI, or correct the Mail entry in the WIN.INI file or registry. If Case 2: Exit any unnecessary applications that are running. If that does not work, see the Microsoft documentation for suggested procedures to enhance memory usage. If Case 3: Verify that the logon information is correct, and try again. If that does not work, confirm the account information with the mail administrator.
Level: 1

Type: ERROR

Impact: Other

REP-04202: An error occurred while logging on to the Mail subsystem.

Cause: An attempt was made to log on to the Mail subsystem and an error occurred. Refer to the accompanying error message for more information. Other possible causes of this error include the following: Case 1: An invalid service profile name, username, or password was entered. Case 2: There is not enough memory available.

Action: Take the following actions to correct this error: If Case 1: Verify that the logon information is correct, and try again. If that does not work, confirm the account information with the mail administrator. If Case 2: Exit any unnecessary applications that are running. If that does not work, see the Microsoft documentation for suggested procedures to enhance memory usage.
Level: 1

Type: ERROR

Impact: Logging

REP-04203: An error occurred while sending a mail message.

Cause: An error occurred while composing or sending a mail message. Refer to the accompanying error message for more information. Other possible causes of this error include the following: Case 1: There is not enough free space on the disk. Case 2: There is not enough memory available.

Action: Take the following actions to correct this error: If Case 1: Free up some space on the disk. If Case 2: Exit any unnecessary applications that are running. If that does not work, see the Microsoft documentation for suggested procedures to enhance memory usage.
Level: 1

Type: ERROR

Impact: Other

REP-04204: An error occurred while trying to validate recipient's name or address.

Cause: Oracle Reports Builder tried to validate the destination mail address, and an error occurred.

Action: Confirm that the recipient has a valid mail account, or ask the mail administrator for assistance. Refer to the accompanying error message for more information.
Level: 1

Type: ERROR

Impact: Other

REP-04220: There is a problem with the Mail subsystem.

Cause: An unspecified error occurred during one of the mail operations.

Action: Try to free up some disk space or exit any unnecessary applications that are running. If other applications are using MAPI, check to see if they are functioning properly. If not, try reinstalling MAPI.
Level: 1

Type: ERROR

Impact: Other

REP-04221: An attachment file cannot be accessed.

Cause: An error occurred while trying to access attachment file. Possible causes of this error include the following: Case 1: The attachment file cannot be found. Case 2: The attachment file could not be opened, or there was an error reading or writing it.

Action: Take the following actions to correct this error: If Case 1: Exit any unnecessary applications that are running. If that does not work, see the Microsoft documentation for suggested procedures to enhance memory usage. If Case 2: Free up some space on the disk.
Level: 1

Type: ERROR

Impact: Other

REP-04222: There is insufficient memory to complete the operation.

Cause: The mail operation cannot be completed, because there is not enough memory available.

Action: Exit any unnecessary applications that are running. If that does not work, see the Microsoft documentation for suggested procedures to enhance memory usage.
Level: 1

Type: ERROR

Impact: Memory

REP-04223: No space is left on the device.

Cause: The mail operation cannot be completed because there is not enough free space available on the disk.

Action: Free up some space on the disk.
Level: 1

Type: ERROR

Impact: Other

REP-04224: The user name, password, or service profile name is incorrect.

Cause: The logon information entered is invalid.

Action: Verify that the logon information is correct, and try again. If that does not work, confirm the account information with the mail administrator.
Level: 1

Type: ERROR

Impact: Other

REP-04225: The operation cannot be completed because the user is not logged on.

Cause: The mail operation could not be completed.

Action: Log on to the Mail subsystem, and try again.
Level: 1

Type: ERROR

Impact: Other

REP-04226: A password is required.

Cause: An attempt was made to log on to the Mail subsystem without specifying a password.

Action: Specify a valid password, and try again. If that does not work, contact the mail administrator.
Level: 1

Type: ERROR

Impact: Other

REP-04227: The service configuration is invalid.

Cause: The Mail subsystem is incorrectly configured.

Action: Contact the mail administrator.
Level: 1

Type: ERROR

Impact: Configuration

REP-04228: MAPI does not support the service requested by Oracle Reports Builder.

Cause: The given implementation of MAPI has limited functionality.

Action: Consider upgrading the Windows mail service provider. Contact the mail administrator.
Level: 1

Type: ERROR

Impact: Other

REP-04229: The character set requested is not supported.

Cause: The default character set is not supported by MAPI.

Action: Contact the mail administrator.
Level: 1

Type: ERROR

Impact: Other

REP-04230: The size of the text string passed is too large.

Cause: The text string passed is too large for the given implementation of MAPI.

Action: Shorten the string, and try again.
Level: 1

Type: ERROR

Impact: Other

REP-04232: Too many files are opened.

Cause: The given implementation of MAPI does not support the number of files open.

Action: Close all unnecessary documents.
Level: 1

Type: ERROR

Impact: Other

REP-06004: Oracle Reports Builder failed to connect to the specified Express server.

Cause: Express server is not running.

Action: Verify that Express server is running.
Level: 1

Type: ERROR

Impact: Other

REP-06006: The Express initialization file, XPDATA.INI, cannot be found.

Cause: The Express initialization file, XPDATA.INI, was not found.

Action: Check the existence and path of the XPDATA.INI file.
Level: 1

Type: ERROR

Impact: Other

REP-06007: The Express connection file (XCF) entry cannot be found in the [Install] section of the Express initialization file, XPDATA.INI.

Cause: The Express connection file (XCF) entry was not found in the [Install] section of the Express initialization file, XPDATA.INI.

Action: Add an XCF entry to XPDATA.INI file, or replace with a valid XPDATA.INI.
Level: 1

Type: ERROR

Impact: Other

REP-06008: The path specified in ORACLE_HOME cannot be found.

Cause: The path specified in the the ORACLE_HOME variable was not found.

Action: Check the ORACLE_HOME setting.
Level: 1

Type: ERROR

Impact: Other

REP-06009: The Oracle SNAPI (OSN) entry cannot be found in the [Install] section of the Express initialization file, XPDATA.INI.

Cause: The Oracle SNAPI (OSN) entry was not found in the [Install] section of the Express initialization file, XPDATA.INI.

Action: Add an OSN entry to XPDATA.INI, or replace with a valid XPDATA.INI.
Level: 1

Type: ERROR

Impact: Other

REP-06010: The Express server description cannot be found in any Express connection files (XCFs).

Cause: The Express server description was not found in any Express connection files (XCFs).

Action: Check the XCF files.
Level: 1

Type: ERROR

Impact: Other

REP-06011: The size of the generated SQL SELECT statement exceeds the 64K limit.

Cause: The size of the generated SQL SELECT statement exceeds the 64K limit.

Action: Modify the query to reduce the size of the SQL statement.
Level: 1

Type: ERROR

Impact: Other

REP-06013: A query failed to run. The Express Query Dialog was invoked with a set of measures/dimensions from a previous query

Cause: The Express Query Dialog was invoked with a set of measures/dimensions from a previous query.

Action: Reexamine the measures/dimensions in the query.
Level: 1

Type: ERROR

Impact: Other

REP-06014: The report ID was not defined when calling the backend XPFetch[N().

Cause: The report ID was not defined before calling the backend XPFetch().

Action: Define the report ID and resubmit the call to the backend XPFetch().
Level: 1

Type: ERROR

Impact: Other

REP-06015: A duplicate report ID was used when calling the backend XPPrepare().

Cause: A duplicate report ID was used when the backend XPPrepare() was called.

Action: Select a unique report ID and resubmit the call to the backend XPPrepare().
Level: 1

Type: ERROR

Impact: Other

REP-06017: The saved query contained incorrect or missing information.

Cause: When the query was saved, it contained incorrect or missing information.

Action: Check the query and correct the information or supply the missing information and try again.
Level: 1

Type: ERROR

Impact: Other

REP-06018: The internal Oracle Express system databases were not attached.

Cause: The internal Oracle Express system databases were not attached.

Action: Attach the internal Oracle Express system databases and try again.
Level: 1

Type: ERROR

Impact: Other

REP-06019: The Oracle Express database specified in the saved query was not attached.

Cause: The Oracle Express database that was specified in the saved query was not attached.

Action: Attach the specified Oracle Express database to the saved query and try again.
Level: 1

Type: ERROR

Impact: Other

REP-06021: The Oracle Express support was not installed.

Cause: The Oracle Express support was not installed.

Action: Install the Oracle Express support and try again.
Level: 1

Type: ERROR

Impact: Other

REP-06023: An unexpected end-of-line was received while parsing the Oracle Express query.

Cause: The Oracle Express query might be missing the \s at the end of the line.

Action: Check the Oracle Express query for a missing \s at the end of the line, add it, and try again.
Level: 1

Type: ERROR

Impact: Other

REP-06026: A duplicate report ID was detected.

Cause: A duplicate report ID was used.

Action: Select a unique report ID and try again.
Level: 1

Type: ERROR

Impact: Other

REP-06027: An undefined report ID was detected.

Cause: The report ID that was used has not yet been defined.

Action: Define the report ID and try again.
Level: 1

Type: ERROR

Impact: Other

REP-06030: The XCONNECT.INI file was missing or was invalid.

Cause: This message probably occurred as the result of a missing XCONNECT.INI file. If the XCONNECT.INI file is not missing, then it probably has an invalid General section.

Action: Check in ORACLE_HOME/OLAP/ECF620 to ensure that the XCONNECT.INI file is there. If not, then add it. If the XCONNECT.INI file is there, verify that it has a valid General section.
Level: 1

Type: ERROR

Impact: Other

REP-06031: This report contains Oracle Express queries that are 6i versions. Convert these queries?

Cause: An older version of Oracle Express queries cannot be edited or run with the current version of Oracle Express.

Action: Reply YES to converting the older version of Oracle Express queries to the newer version of Oracle Express. The queries will be automatically converted.
Level: 1

Type: ERROR

Impact: Other

REP-06032: The Oracle Express query {0} failed to convert.

Cause: This error message could have occurred for one of the following reasons: Case 1: The Oracle Express 6i query was corrupted. Case 2: The Oracle Express pluggable data source malfunctioned.

Action: Take the following actions to correct this error: If Case 1: Ensure that the query is not corrupted by editing and rerunning it in the OracleAS Reports Services environment. If Case 2: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-06033: This operation requires converting the {0} Oracle Express query to the newer version of Oracle Express. Proceed with this conversion?

Cause: Older versions of Oracle Express queries cannot be edited or run with the current version of Oracle Express.

Action: Accept the conversion by replying YES to the conversion. The queries will be automatically converted.
Level: 1

Type: ERROR

Impact: Other

REP-06051: The Oracle Portal connection failed.

Cause: The database server might be down or the user ID and password authentication failed.

Action: Check that the database server is available, verify that the user ID and password are correct and try again.
Level: 1

Type: ERROR

Impact: Other

REP-06052: The database requested does not contain a valid Oracle Portal definition.

Cause: This error might have occurred for one of the following reasons: Case 1: The database is not a valid version for the Oracle Portal installation. Case 2: The logged in user does not have permission to read the component definition tables.

Action: Take the following actions to correct this error: If Case 1: Select a valid database for the Oracle Portal installation. If Case 2: Obtain permissions for the logged in user to read the component definition tables.
Level: 1

Type: ERROR

Impact: Other

REP-06053: There are no components in Oracle Portal that can be imported.

Cause: This is an information only message notifying that there are no components available to be imported.

Action: No action is necessary.
Level: 1

Type: ERROR

Impact: Other

REP-06054: The requested template cannot be found.

Cause: This can occur for one of the following reasons: Case 1: The REPORTS_XSL_TEMPLATE environment variable was incorrectly edited. Case 2: The template XSL file was removed from the location where it is supposed to be located.

Action: Take the following actions to correct this error: If Case 1: Correct the REPORTS_XSL_TEMPLATE and continue. If Case 2: Ensure the template XSL file is in the proper location and continue.
Level: 1

Type: ERROR

Impact: Other

REP-06055: A template error occurred.

Cause: The XSL template file was not a well-formed template.

Action: Verify that the XSL template file is correct. If it is, then the best solution is to restore the original one. Experienced users can edit the file to correct the problems.
Level: 1

Type: ERROR

Impact: Other

REP-06056: A temporary directory was invalid.

Cause: The transformation process requires a temporary directory to write a temporary file. The temporary directory might not exist or it might not allow a temporary file to be written to it.

Action: Look at the REPORTS_TMP environment variable and ensure that it corresponds to an existing, writable temporary directory.
Level: 1

Type: ERROR

Impact: Other

REP-06057: A portal component has not been selected.

Cause: OK was clicked without selecting a portal component.

Action: Select a portal componet or click Cancel.
Level: 1

Type: ERROR

Impact: Other

REP-06058: Database client library error.

Cause: Oracle Reports cannot connect to the portal database because of a JDBC error. A common cause is a version mismatch of a database client library in the path.

Action: Verify that the Oracle Reports bin directory is listed in the path search order before any other ORACLE_HOME/bin or other directory that could have a database client. If this does not solve the problem, check the Java classpath and verify that the correct version of the JDBC library is listed before any other library.
Level: 1

Type: ERROR

Impact: Other

REP-06101: The Java Virtual Machine failed to start. Check the Java Runtime Environment setup. {0}:{1}.

Cause: The Java runtime environment in the installation is not valid.

Action: Verify that the installation is correct. Reinstall if necessary.
Level: 1

Type: ERROR

Impact: Other

REP-06102: The XML parser failed to start.

Cause: The XML parser jar files are missing in the installation.

Action: Verify that the Oracle Fusion Middleware installation is correct. Reinstall if necessary.
Level: 1

Type: ERROR

Impact: Other

REP-06103: An error occurred with the Java Runtime Environment setup.

Cause: The Java runtime environment in the installation is not valid.

Action: Verify that the installation is correct. Reinstall if necessary.
Level: 1

Type: ERROR

Impact: Other

REP-06104: The XML report definition is invalid.

Cause: The report definition is invalid.

Action: Verify the XML report definition.
Level: 1

Type: ERROR

Impact: Other

REP-06105: An error occurred in the XML report definition at line {0}.

Cause: The report definition is invalid.

Action: Verify the XML report definition.
Level: 1

Type: ERROR

Impact: Other

REP-06106: An error occurred in the XML report definition at line {0} in {1}.

Cause: The report definition is invalid.

Action: Verify the XML report definition.
Level: 1

Type: ERROR

Impact: Other

REP-06107: The URL for the XML report definition is invalid: {0}.

Cause: The report definition is invalid.

Action: Verify the URL location / XML report definition.
Level: 1

Type: ERROR

Impact: Other

REP-06108: The XML report definition cannot be applied.

Cause: This is an internal error.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-06109: The report definition file {0} cannot be saved.

Cause: This is an internal error.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-06110: The query {0} cannot be created.

Cause: The PDS query is invalid.

Action: Look into the trace information for more details in case of a custom PDS.
Level: 1

Type: ERROR

Impact: Other

REP-06111: The query {0} cannot be modified.

Cause: The PDS query is invalid.

Action: Look into the trace information for more details in case of a custom PDS.
Level: 1

Type: ERROR

Impact: Other

REP-06112: The column {0} cannot be created.

Cause: The PDS query is invalid.

Action: Look into the trace information for more details in case of a custom PDS.
Level: 1

Type: ERROR

Impact: Other

REP-06113: The column {0} cannot be modified.

Cause: The PDS query is invalid.

Action: Look into the trace information for more details in case of a custom PDS.
Level: 1

Type: ERROR

Impact: Other

REP-06114: The data link {0} cannot be created.

Cause: The PDS query is invalid.

Action: Look into the trace information for more details in case of a custom PDS.
Level: 1

Type: ERROR

Impact: Data

REP-06115: The data link {0}cannot be modified.

Cause: The PDS query is invalid.

Action: Look into the trace information for more details in case of a custom PDS.
Level: 1

Type: ERROR

Impact: Data

REP-06116: The field {0} cannot be created.

Cause: The PDS query is invalid.

Action: Look into the trace information for more details in case of a custom PDS.
Level: 1

Type: ERROR

Impact: Other

REP-06117: The field {0} cannot be modified.

Cause: The PDS query is invalid.

Action: Look into the trace information for more details in case of a custom PDS.
Level: 1

Type: ERROR

Impact: Other

REP-06118: The layout for {0} cannot be defaulted.

Cause: This is an internal error.

Action: Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-06119: Format exception {0} for the field {1} cannot be created.

Cause: This is an internal error.

Action: Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-06120: Condition {0} in the format exception {1} for the field {2} is invalid.

Cause: This is an internal error.

Action: Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-06121: The specified layout style {0} is invalid.

Cause: An attempt was made to use an invalid layout style.

Action: Verify the layout style for the report.
Level: 1

Type: ERROR

Impact: Other

REP-06122: The specified layout style {0} in {1} is invalid.

Cause: An attempt was made to use invalid layout style.

Action: Verify the layout style for the report.
Level: 1

Type: ERROR

Impact: Other

REP-06123: Source {0} for field {1} is invalid.

Cause: The value used for the field is invalid.

Action: Verify the value.
Level: 1

Type: ERROR

Impact: Other

REP-06124: A PL/SQL compilation error occurred in {0}.

Cause: The PL/SQL procedure is invalid.

Action: Verify the PL/SQL procedure.
Level: 1

Type: ERROR

Impact: Other

REP-06200: Reports tag library directive cannot be found: {0} in report file

Cause: Reports was unable to locate the expected JSP taglib directive in the user supplied report file.

Action: All Web-based reports must contain the tag library directive. Open any demo .JSP file and copy the taglib lines into the report.
Level: 1

Type: ERROR

Impact: Other

REP-06201: Prefix attribute {0} in report file cannot be found.

Cause: The file does not contain an rw:objects tag. The tag library directive does not contain the correct prefix attribute or is otherwise corrupted.

Action: The rw:objects tag supplies data for report blocks and charts. If this tag is not required in the file then this message can be ignored. If data is required, use the data wizard to add a data model to the report. Open any demo .jsp file and replace the taglib lines in the report with the lines from the demo file.
Level: 1

Type: ERROR

Impact: Other

REP-06202: A rw:report tag in the template file cannot be found.

Cause: The file contains a taglib directive but does not contain a rw:report tag.

Action: The template file can still be used but the rw:report tag must be added to a report before a data model can be added.
Level: 1

Type: ERROR

Impact: Other

REP-06203: Template file cannot be parsed.

Cause: Reports was unable to parse the indicated file. Any attempt to execute the report will not run.

Action: Check the JSP syntax against the documentation in the Help system.
Level: 1

Type: ERROR

Impact: Other

REP-06204: The <rw:objects> tag cannot be found. Save operation aborted

Cause: The &lt;rw:objects&gt; tag was missing or invalid JSP syntax was found within the document.

Action: Check the JSP syntax against the documentation in the Help system.
Level: 1

Type: ERROR

Impact: Other

REP-06205: The ID attribute of tag {0} is not unique.

Cause: The report contains duplicate JSP ID attributes.

Action: JSP ID attributes must be unique within a page. Change the ID of the tags that are not unique.
Level: 1

Type: ERROR

Impact: Other

REP-06206: Tag {0} must be inside the rw:report tag.

Cause: A Reports JSP tag is outside the rw:report tag.

Action: All Reports JSP tags must be inside the rw:report tag. Move the tag inside the rw:report tag. The easiest way to prevent this error is to move the &lt;/rw:report&gt; tag to the bottom of the page.
Level: 1

Type: ERROR

Impact: Other

REP-06207: Tag {0} tag has an invalid scope.

Cause: A Reports JSP tag is outside of the correct context.

Action: Move the tag to its correct scope.
Level: 1

Type: ERROR

Impact: Other

REP-06208: More than one rw:report tag is found. A report page can have only one rw:report tag.

Cause: The report contains more than one set of rw:report tags.

Action: Add &lt;rw:report&gt; after the taglib lines at the top of the page. Add &lt;/rw:report&gt; at the bottom of the page. Remove the extra rw:report tags.
Level: 1

Type: ERROR

Impact: Other

REP-06209: Required Reports JSP tags are missing. The required Reports JPS tags have been added to the saved file.

Cause: When saving the JSP file, required Reports JSP tags were not found.

Action: Click OK to add the required tags and save the file. Click Cancel to prevent Oracle Reports Builder from adding the tags, and not save the file.
Level: 1

Type: ERROR

Impact: Other

REP-06210: Required Reports JSP tags are being added to the file.

Cause: If the file does not contain the required Reports JSP tags when it is first opened, Oracle Reports Builder adds the Reports JSP tags to the file loaded in memory. The original file on disk is not touched.

Action: Click OK to continue working on the file.
Level: 1

Type: ERROR

Impact: Other

REP-06211: The graph XML definition cannot be parsed.

Cause: Oracle Reports was unable to parse the XML definition of the graph.

Action: Check the graph XML DTD against the Oracle BI Beans documentation.
Level: 1

Type: ERROR

Impact: Other

REP-06212: The graph definition cannot be parsed.

Cause: Oracle Reports was unable to parse the definition of the graph.

Action: Check the graph tag against the reports.tld.
Level: 1

Type: ERROR

Impact: Other

REP-06213: A report level cursor cannot be created.

Cause: An internal error occurred when creating the report level cursor.

Action: Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-06214: A group cursor cannot be created.

Cause: An internal error occurred when creating the group cursor.

Action: Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-06215: An error occurred retrieving the next row from the cursor.

Cause: An internal error occurred when moving the group cursor to the next row.

Action: Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-06216: Unable to create related cursor

Cause: An internal error occurred when creating the related group cursor.

Action: Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-06217: No source specified for cursor

Cause: An internal error occurred. The cursor's source (that is, report for report level cursor, group for group cursor) is not specified.

Action: Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-06218: Value of unknown column {0} cannot be retrieved.

Cause: The column name is invalid.

Action: Provide a valid column name.
Level: 1

Type: ERROR

Impact: Other

REP-06219: Column {0} is not in the given cursor hierarchy.

Cause: The column does not belong to the cursor provided.

Action: Modify the report so that the column belongs to given cursor hierarchy.
Level: 1

Type: ERROR

Impact: Other

REP-06220: Value of column cannot be retrieved.

Cause: An internal error occurred when getting the value of the column.

Action: Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-06221: Column {0} cannot be found.

Cause: An internal error occurred when looking for a column.

Action: Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-06222: The column in the given cursor cannot be found.

Cause: The column does not belong to the cursor provided.

Action: Modify the report so that column belongs to the given cursor.
Level: 1

Type: ERROR

Impact: Other

REP-06223: Attempt to determine which cursor a column belongs to failed.

Cause: An internal error occurred when trying to find out to which cursor a column belongs, among a given list of cursors.

Action: Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-16500: This program can only be invoked as a CGI executable.

Cause: The Web CGI executable was invoked outside the Web Server context.

Action: The CGI executable must be invoked by a Web server to work properly.
Level: 1

Type: ERROR

Impact: Other

REP-16501: The Reports Web Agent key map file was not set up properly.

Cause: The key map file cannot be found at the location specified.

Action: Check the file location.
Level: 1

Type: ERROR

Impact: Other

REP-16504: The message subsystem cannot be initialized.

Cause: The Oracle Reports message file cannot be found or opened.

Action: Check the installation. Verify that the Oracle Reports message file was installed properly.
Level: 1

Type: ERROR

Impact: Other

REP-16505: A general error occurred during initialization.

Cause: A general error occurred.

Action: Check the installation and availability of system resources.
Level: 1

Type: ERROR

Impact: Other

REP-16506: The URL contains badly-formed escapes.

Cause: The submitted URL is badly formed.

Action: See the URL rules in the Web Agent documentation.
Level: 1

Type: ERROR

Impact: Other

REP-16507: The key is unrecognized.

Cause: The key map configuration is active, but the specified key in the URL is unrecognized, and the command line cannot be built.

Action: Check the key value and keymap file setup and contents.
Level: 1

Type: ERROR

Impact: Other

REP-16508: Key %s is unrecognized.

Cause: The key map configuration is active, but the specified key in the URL is unrecognized, and the command line cannot be built. This error may be due to bad URL syntax, or the key in the URL was not found in the key map file.

Action: Check the key value and keymap file setup and contents.
Level: 1

Type: ERROR

Impact: Other

REP-16509: Syntax errors are found in the key map file.

Cause: Syntax errors occurred in the key map file.

Action: Check the key map file contents (see Web Agent documentation for rules). Check a definition of submitted key.
Level: 1

Type: ERROR

Impact: Other

REP-16510: Usage in incorrect.

Cause: This is a generic error for a non-verbose run.

Action: Enable verbocity and check the real message.
Level: 1

Type: ERROR

Impact: Other

REP-16511: The URL contains too many parameters.

Cause: The URL contains too many parameters (it is too long).

Action: Use a shorter URL or the key map file to shorten the URL.
Level: 1

Type: ERROR

Impact: Other

REP-16512: out of memory

Cause: There is not enough memory to perform the operation.

Action: Verify that enough system resources are available.
Level: 1

Type: ERROR

Impact: Memory

REP-16513: Communication with the Reports Server is lost.

Cause: Reports Server is not answering.

Action: Verify that Reports Server is up and the tnsnames.ora network setup has a correct entry for it.
Level: 1

Type: ERROR

Impact: Other

REP-16514: The report cannot be run.

Cause: This is a generic error for a report run failure.

Action: See the detailed error message from Reports Server.
Level: 1

Type: ERROR

Impact: Other

REP-16515: The report output cannot be accessed.

Cause: The Web Agent cannot access Reports Server run output.

Action: Check the Web Agent setup (especially WEBLOC variable).
Level: 1

Type: ERROR

Impact: Other

REP-16516: The Reports Server is being shut down.

Cause: Reports Server is going down.

Action: Try again later.
Level: 1

Type: ERROR

Impact: Other

REP-16517: The Oracle Reports job is canceled upon user request.

Cause: The Oracle Reports job was canceled.

Action: Try again if necessary.
Level: 1

Type: ERROR

Impact: Other

REP-16518: The Reports Engine terminated abnormally.

Cause: The Reports Engine had problem with the report.

Action: Contact the Reports Server administrator.
Level: 1

Type: ERROR

Impact: Other

REP-16519: The Oracle Reports job has terminated with an error.

Cause: This is a generic error message for report run error.

Action: See the detailed error message from Reports Server.
Level: 1

Type: ERROR

Impact: Other

REP-16520: An error occurred while queuing a job to Reports Server.

Cause: An error occurred while enqueing report to run.

Action: Try again later.
Level: 1

Type: ERROR

Impact: Other

REP-16521: An error occurred while parsing the Reports Server command line.

Cause: An error occurred while attempting to run a report and process a command line.

Action: Contact the Reports Server administrator.
Level: 1

Type: ERROR

Impact: Other

REP-16522: The Reports Server name is not specified.

Cause: An error occurred while attempting to run a report and process a command line.

Action: Contact the Reports Server administrator. Check the command line for a server name.
Level: 1

Type: ERROR

Impact: Other

REP-16523: A report name is not specified.

Cause: An error occurred while attempting to run a report and process a command line.

Action: Contact the Reports Server administrator. Check the command line for a report name.
Level: 1

Type: ERROR

Impact: Other

REP-16524: A database logon is not specified.

Cause: An error occurred while attempting to run a report and process a command line.

Action: Contact the Reports Server administrator. Check the command line for database logon.
Level: 1

Type: ERROR

Impact: Other

REP-16525: The scheduling command cannot be interpreted.

Cause: An error occurred while attempting to run a report and process a command line.

Action: Contact the Reports Server administrator. Check the SCHEDULE parameter.
Level: 1

Type: ERROR

Impact: Other

REP-16526: The time tolerance cannot be interpreted.

Cause: An error occurred while attempting to run a report and process a command line.

Action: Contact the Reports Server administrator. Check the TOLERANCE parameter.
Level: 1

Type: ERROR

Impact: Other

REP-16527: The Parameter Form type is invalid.

Cause: An error occurred while attempting to run a report and process a command line.

Action: Contact the Reports Server administrator. Check the PARAMFORM parameter.
Level: 1

Type: ERROR

Impact: Other

REP-16528: An error occurred while communicating with the Reports Server.

Cause: A communication problem occurred.

Action: Try again later.
Level: 1

Type: ERROR

Impact: Other

REP-16529: The job cannot be killed.

Cause: This is a generic message for job kill failure.

Action: Investigate why the job cannot be killed.
Level: 1

Type: ERROR

Impact: Other

REP-16530: The job ID is invalid.

Cause: The ID of the Reports Server job is invalid.

Action: Verify the ID.
Level: 1

Type: ERROR

Impact: Other

REP-16531: The job is already finished.

Cause: The ID of the Reports Server job is invalid.

Action: Verify the ID.
Level: 1

Type: ERROR

Impact: Other

REP-16532: The job is not done yet. Try again later.

Cause: The ID of the Reports Server job is invalid.

Action: Verify the ID.
Level: 1

Type: ERROR

Impact: Other

REP-16533: There are insufficient privileges to perform the requested action.

Cause: The ID of the Reports Server job is invalid.

Action: Verify the ID and privileges.
Level: 1

Type: ERROR

Impact: Other

REP-16534: Report output cannot be accessed.

Cause: The Oracle Reports output directory is not accessible.

Action: Check the directory specification and the setup (REPORTS_WEBLOC or REPORTS_WEBLOC_TRANSLATED environment is probably invalid).
Level: 1

Type: ERROR

Impact: Other

REP-16535: Report output cannot be accessed.

Cause: The Oracle Reports output directory is not accessible.

Action: Check the directory specification and the setup (REPORTS_WEBLOC or REPORTS_WEBLOC_TRANSLATED environment is probably invalid).
Level: 1

Type: ERROR

Impact: Other

REP-16537: Report output cannot be saved.

Cause: Report output of the returned name already exists in the Web directory.

Action: Check the Web Agent setup (REPORTS_WEBLOC_TRANSLATED environment probably points to the same location as a Reports Server cache).
Level: 1

Type: ERROR

Impact: Other

REP-16538: Report output was successfully printed.

Cause: The report was successfully run to the printer.

Action: No action is needed.
Level: 1

Type: ERROR

Impact: Other

REP-16539: Report output was successfully mailed.

Cause: The report was successfully run to mail.

Action: No action is needed.
Level: 1

Type: ERROR

Impact: Other

REP-16540: Report output was successfully written to the requested destination.

Cause: The report was successfully run to the requested destype.

Action: No action is needed.
Level: 1

Type: ERROR

Impact: Other

REP-16541: Log on before running the report.

Cause: It is necessary to log on before running the report.

Action: Log on again.
Level: 1

Type: ERROR

Impact: Other

REP-16542: Report output was successfully written to the InterOffice repository.

Cause: The report was successfully run to the InterOffice repository.

Action: No action is needed.
Level: 1

Type: ERROR

Impact: Other

REP-16543: The report output cannot be accessed.

Cause: The Oracle Reports output directory is not accessible.

Action: Check the directory specification. Check the setup (REPORTS_VIRTUAL_MAP, REPORTS_PHYSICAL_MAP and REPORTS_SHARED_CACHE environment is probably invalid.)
Level: 1

Type: ERROR

Impact: Other

REP-16544: The report output cannot be accessed.

Cause: The Oracle Reports output directory is not accessible.

Action: Check directory specification. Check the setup (REPORTS_VIRTUAL_MAP, REPORTS_PHYSICAL_MAP and REPORTS_SHARED_CACHE environment is probably invalid.)
Level: 1

Type: ERROR

Impact: Other

REP-20091: Save the current document before disconnecting from the database?

Cause: An open document is stored in the database. If disconnected from the database, changes cannot be saved to the database.

Action: Select Yes to save the document before disconnecting from the database; the document remains open to reconnect if desired and save it to the database again. Select No to disconnect from the database without saving the document; the document remains open. Select Cancel to remain connected to the database without saving; once again, the document remains open.
Level: 1

Type: ERROR

Impact: Other

REP-20099: Printer changed while previewing. Printer font remapping could cause truncation. Continue with printing?

Cause: In the time between running the report and selecting Print from the Previewer, the default printer has changed.

Action: Select Yes to print anyway. Select No to halt printing, then close the report and either reset the printer and run the report again, or simply run it again to format it for the current printer.
Level: 1

Type: ERROR

Impact: Other

REP-20128: The report was not run with DESTYPE=PREVIEW. Screen font remapping could cause truncation. Continue with printing?

Cause: Print was selected from the Previewer, but specified Screen instead of Preview, which formats the report as though using printer fonts and provides a more accurate view of the report's printed output.

Action: Select Yes to print anyway. Select No to halt printing. Then close the report and run it again while specifying Preview to format it for the printer.
Level: 1

Type: ERROR

Impact: Other

REP-20129: Opening a report saved with a newer version of Oracle Reports Builder. Functionality may be lost. Continue?

Cause: An attempt was made to open a report with a version of Oracle Reports Builder older than the version used to create the report. If the report uses functionality unavailable in the older version, that functionality will be eliminated from the report.

Action: To avoid losing functionality, do not open the report until after upgrading to the most recent version of Oracle Reports Builder.
Level: 1

Type: ERROR

Impact: Other

REP-20135: A layout does not exist. Create a default layout?

Cause: An attempt was made to run the report after creating a data model but before creating a layout.

Action: Select Yes to create a default layout using the Report Wizard. Select No to run the report without a layout.
Level: 1

Type: ERROR

Impact: Other

REP-20136: The region chosen for the default layout is too small. Extend the region to page boundaries?

Cause: The Report Block tool was used to draw a region for a layout that was not large enough to accommodate the settings specified in the Report Block Wizard.

Action: Select Yes to have Oracle Reports Builder extend the possible range of the layout to the boundaries of a report page, or select No and change the settings in the Report Block Wizard to shrink the size of the layout.
Level: 1

Type: ERROR

Impact: Other

REP-20138: Oracle Reports Builder tables may not be installed in the database.

Cause: Oracle Reports Builder was not able to access its tables in the database.

Action: Inform the database administrator that the Oracle Reports Builder tables were not successfully installed in the database.
Level: 1

Type: ERROR

Impact: Other

REP-20139: New Parameter Form layout will not fit its current size. Increase the number of pages to fit?

Cause: The new Parameter Form is too big to fit on the number of pages specified for the Parameter Form in the Report Properties dialog box.

Action: Either select Yes to have Oracle Reports Builder increase the number of pages in the Parameter Form, or select No and change the settings in the Report Properties dialog to enlarge the Parameter Form.
Level: 1

Type: ERROR

Impact: Other

REP-20144: Opening a report saved with a newer version of Oracle Reports Builder. Functionality may be lost.

Cause: An attempt was made to open a report with a version of Oracle Reports Builder older than the version used to create the report. If the report uses functionality unavailable in the older version, that functionality will be eliminated from the report.

Action: To avoid losing functionality, do not open the report until after upgrading to the most recent version of Oracle Reports Builder.
Level: 1

Type: ERROR

Impact: Other

REP-20146: This action may invalidate references to columns in the referenced object.

Cause: Collapsing a Database Ref, Database Nested Table, or Database Varray column invalidates any external use of the referenced columns. for example, in PL/SQl Program Units or in Summary Columns.

Action: To use the referenced columns, do not collapse the Database Ref, Database Nested Table, or Database Varray columns referencing them.
Level: 1

Type: ERROR

Impact: Other

REP-20147: A column link for this detail SQL query cannot be implemented. Converting to group link.

Cause: Oracle Reports Builder can only insert column to column links into supported SQL. It defaults to a group to group link in this case.

Action: Manually insert the required link clause into the detail SQL query.
Level: 1

Type: ERROR

Impact: Other

REP-20150: Page width of report {0} was changed to fit the font for a character cell as a consequence of font-mapping.

Cause: A character font has been substituted for a bitmapped font in the report, and the page width has been adjusted accordingly. A possible cause: a bitmapped report is being opened in the character-mode runtime engine.

Action: To map the font to a specific font, edit the font alias file (uifont.ali or Oracle Font Aliases, depending on the platform) to map the fonts to the desired ones. Otherwise, no action is necessary.
Level: 1

Type: ERROR

Impact: Other

REP-20151: Some fonts have been changed according to the mapping in the font aliases file.

Cause: One or more fonts saved with the report have been mapped to different ones, due to a change in platform, display, report destination, or mode.

Action: To map the font to a specific font, edit the font alias file (uifont.ali or Oracle Font Aliases, depending on the platform) to map the fonts to the desired ones. Otherwise, no action is necessary.
Level: 1

Type: ERROR

Impact: Other

REP-20160: An AutoRecovery file was detected. Recover unsaved changes for {0}?

Cause: Oracle Reports Builder can automatically recover unsaved report changes if it stops responding or there is a power failure.

Action: Either select Yes to have Oracle Reports Builder recover unsaved report changes, or select No to ignore.
Level: 1

Type: ERROR

Impact: Other

REP-20161: Unable to save AutoRecovery file, Autosave functionality would be disabled.

Cause: Oracle Reports Builder tried to write an AutoRecovery file and could not. The possible causes of this error include the following: Case 1: Lack of necessary privileges to write the file. Case 2: The file system does not have enough room for the file. Case 3: A system error made it impossible to open the file.

Action: Either select OK to have Oracle Reports Builder to disable Autosave, or select Cancel to take the following actions to correct this error: If Case 1: Verify the privileges necessary to write the file. If Case 2: Make more room by deleting unnecessary files or expanding storage. If Case 3: Consult the operating system documentation or contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

REP-20190: Quit will terminate the current report, as well as any other pending reports.

Cause: A request to exit the Reports Server or Reports Background Engine was issued while one or more reports are still executing or awaiting execution.

Action: To finish report execution, cancel the operation. Otherwise, accept the warning dialog.
Level: 1

Type: ERROR

Impact: Other

REP-20191: Cannot exit Windows when this program is running. Close the Reports Background Engine and exit Windows.

Cause: The Reports Background Engine requires Windows, but a request was issued to exit Windows while the Reports Background Engine is still running.

Action: Exit the Reports Background Engine before exiting Windows.
Level: 1

Type: ERROR

Impact: Operating System

REP-25206: Converting {0} to {1} failed.

Cause: The most likely cause of this error is that the source type specified was incorrect.

Action: Ensure that the source file is of the specified source type.
Level: 1

Type: ERROR

Impact: Other

REP-25207: Invalid conversion: stype and dtype are not of the same document type.

Cause: An attempt was made to convert a document of one type to another type; that is, an attempt to convert one of the possible report files to a PL/SQL file, or vice versa.

Action: Ensure that the source and destination of theconversion are the same type of document.
Level: 1

Type: ERROR

Impact: Other

REP-25401: User exit .DLL file {0} cannot be found.

Cause: The report attempted to execute a user exit, but the user exit .DLL file could not be located. This file typically resides in: the current directory the Windows directory (typically \\WINDOWS) the Windows system directory (typically \\WINDOWS\\SYSTEM) the directory containing the executable file for the current task the directories listed in the PATH environment variable the list of directories mapped in a network

Action: Locate the specified .DLL file and place it in one of the directories listed above.
Level: 1

Type: ERROR

Impact: Other

REP-25402: An internal error occurred attempting to locate user exit .DLL file {0} within file {1}

Cause: The report attempted to execute a user exit, but certain functions used to locate and execute user exits cannot be located in the user exit .DLL file. This means that the user exit .DLL was built incorrectly, because these functions are located in a .OBJ file shipped with Oracle Reports Builder, which should always be linked into the user exit .DLL.

Action: Rebuild the specified user exit .DLL correctly.
Level: 1

Type: ERROR

Impact: Other

REP-31681: Connecting to a different database may invalidate existing data model.

Cause: Only one connection to a database is valid at a time. If a connection is established to different database, the existing data model may not be valid afterward.

Action: To keep the existing data model valid, do not reconnect to a different database unless the queries are compatible with the new database connection.
Level: 1

Type: ERROR

Impact: Data

REP-31700: The report definition is incomplete, or the query does not have break groups. Cannot run the Web Wizard.

Cause: The report definition was not completed before running the Web Wizard. To run the Web Wizard, the report definition must contain a Data Model with multiple groups and a valid Paper Layout.

Action: Create at least one query with multiple groups and default the layout using the Report Wizard.
Level: 1

Type: ERROR

Impact: Other

REP-31800: Image file {0} cannot be found.

Cause: Oracle Reports Builder could not locate one of its image files. Possible causes of this error include: Case 1: The image file does not exist Case 2: The image file is in the wrong place. Case 3: The environment is not configured properly.

Action: Take the following actions to correct this error: If Case 1: Verify that the image file is present. If Case 2: Verify that the image file is in the proper directory. If Case 3: Verify that the environment is set correctly. On UNIX, verify that the proper environment variable is set, and on MS Windows check the file oracle.ini.
Level: 1

Type: ERROR

Impact: Other

REP-31801: Image {0} specified in the template cannot be found.

Cause: Oracle Reports Builder could not locate the image corresponding to the chosen templage. Possible causes of this error include: Case 1: The image file does not exist Case 2: The image file is in the wrong place. Case 3: The environment is not configured properly.

Action: Take the following actions to correct this error: If Case 1: Verify that the image file is present. If Case 2: Verify that the image file is in the proper directory. If Case 3: Verify that the environment is set correctly. On UNIX, verify that the proper environment variable is set, and on MS Windows check the file oracle.ini.
Level: 1

Type: ERROR

Impact: Other

REP-31802: Enter a SQL statement on this page.

Cause: In order for the wizard to create the report, a valid SQL text must exist.

Action: Enter a SQL statement.
Level: 1

Type: ERROR

Impact: Other

REP-31803: SQL text cannot be checked due to no database connection.

Cause: The wizard requires a connection to a database in order to check the SQL text.

Action: Connect to a database by typing in a login string whenever the Connect dialog is shown. Confirm logon information with the database administrator.
Level: 1

Type: ERROR

Impact: Other

REP-31804: The SQL is OK.

Cause: The wizard has checked the SQL text against the database and has confirmed that it will work.

Action: No changes are needed to the SQL text.
Level: 1

Type: ERROR

Impact: Other

REP-31805: Break level {0} has no valid break columns.

Cause: Each break level must contain at least one valid break column. A break column cannot be a summary or placeholder column. Nor can it have a data type of Raw, Longraw, or Long.

Action: Provide at least one valid break column for the break level or move all columns that are currently in this break level to another level which contains a valid break column.
Level: 1

Type: ERROR

Impact: Other

REP-31806: All fields cannot be designated to be break fields.

Cause: All fields were chosen to be break fields. Each break field designated groups the data of the fields that are not break fields. With no non-break fields, this situation is invalid.

Action: Designate at least one field to be a non-break field. For example, remove all break fields from the highest numbered break level (that is, from the bottom of the list of break fields).
Level: 1

Type: ERROR

Impact: Other

REP-31807: Template file {0} cannot be found.

Cause: Oracle Reports Builder could not locate the template file with the given name. Possible causes of this error include: Case 1: The template file does not exist. Case 2: The template file is in the wrong place. Case 3: The environment is not configured properly.

Action: Take the following actions to correct this error: If Case 1: Verify that the template file is present. If Case 2: Verify that the template file is in the proper directory. If Case 3: Verify that the environment is set correctly. On UNIX, verify that the proper environment variable is set, and on MS Windows check the file oracle.ini.
Level: 1

Type: ERROR

Impact: Other

REP-31808: A SQL statement must be entered.

Cause: A SQL statement was not entered for the wizard to generate a report.

Action: Enter a SQL statement in the wizard tab.
Level: 1

Type: ERROR

Impact: Other

REP-31809: At least one field to display must be chosen.

Cause: No field has been selected to display.

Action: Select some fields to display.
Level: 1

Type: ERROR

Impact: Other

REP-31810: At least one break group must be created.

Cause: The current report style needs breaks groups.

Action: Create some break groups.
Level: 1

Type: ERROR

Impact: Other

REP-31811: At least one matrix row must be selected.

Cause: Nothing has been selected as matrix rows.

Action: Select some columns as matrix rows.
Level: 1

Type: ERROR

Impact: Other

REP-31812: At least one matrix column must be selected.

Cause: Nothing has been selected as matrix columns.

Action: Select some columns as matrix columns.
Level: 1

Type: ERROR

Impact: Other

REP-31813: At least one matrix cell must be selected.

Cause: Nothing has been selected as matrix cells.

Action: Select some columns as matrix cells.
Level: 1

Type: ERROR

Impact: Other

REP-31814: At least one matrix break must be selected.

Cause: Nothing has been selected as matrix breaks.

Action: Create some matrix break groups.
Level: 1

Type: ERROR

Impact: Other

REP-31815: At least one field must be displayed per group.

Cause: This problem is due to: 1) This field has been specified as a group field. 2) The group of this field has been defaulted, and this field is the only one that has been marked as "to be defaulted" in its group.

Action: 1) If this field has been specified as a group field, go to the group page to deselect this field. 2) If the group of this field has been default, go to the group page to deselect that group.
Level: 1

Type: ERROR

Impact: Other

REP-31816: Groups to be defaulted must be selected.

Cause: No group has been selected to be defaulted.

Action: Select groups to be defaulted.
Level: 1

Type: ERROR

Impact: Other

REP-31817: At the top of the group. Cannot move up.

Cause: This column is at the top of its group.

Action: Do not try to move this column up.
Level: 1

Type: ERROR

Impact: Other

REP-31818: At the bottom of the group. Cannot move down.

Cause: This column is at the bottom of its group.

Action: Do not try to move this column up.
Level: 1

Type: ERROR

Impact: Other

REP-31819: Report level columns cannot be reordered.

Cause: Report level columns do not have the POS attribute.

Action: Set where to display the report level columns in the Paper Layout editor.
Level: 1

Type: ERROR

Impact: Other

REP-31820: Selected groups have no columns in them.

Cause: Selected groups have no columns in them, so no report can be generated.

Action: Select some other groups.
Level: 1

Type: ERROR

Impact: Other

REP-31821: There is no text specified in the text editor.

Cause: The text for a mailing label or form letter report is empty.

Action: Type some text in the text editor.
Level: 1

Type: ERROR

Impact: Other

REP-31822: One group must be selected.

Cause: No group has been selected.

Action: Go to the group page and select one group.
Level: 1

Type: ERROR

Impact: Other

REP-31823: One and only one group must be selected.

Cause: There is more than one group selected.

Action: Select one and only one group.
Level: 1

Type: ERROR

Impact: Other

REP-31824: Another group must be selected since there are no columns in the selected group.

Cause: There are no columns in the selected group.

Action: Select another group that has columns.
Level: 1

Type: ERROR

Impact: Other

REP-31825: Cancel the wizard and fix the problem in report editors.

Cause: The data model is invalid or the default region is too small.

Action: Fix the problem in the Data Model editor or Paper Layout editor.
Level: 1

Type: ERROR

Impact: Other

REP-31826: A custom template file name is not specified.

Cause: A custom template is selected, but no template file name is specified.

Action: Type a custom template file name, or click Browse button to navigate to it.
Level: 1

Type: ERROR

Impact: Other

REP-31827: Invalid print direction or illegal defaulting of page level summary column.

Cause: The print direction against one or more groups is invalid for the requested default style, or page level summary column was selected to be defaulted (page level summaries are not supported within defaulting).

Action: Alter the print direction against the group or the default style, or deselect all page level summaries.
Level: 1

Type: ERROR

Impact: Other

REP-31828: The query definition is invalid.

Cause: The query is not properly defined.

Action: Define a valid query.
Level: 1

Type: ERROR

Impact: Other

REP-31906: This type of graph requires more categories than have been selected.

Cause: The number of categories required for a graph depends on the type of graph selected. This type of graph requires more categories than were selected.

Action: Select the minimum number of categories required by the type of graph selected in a previous panel.
Level: 1

Type: ERROR

Impact: Other

REP-31907: This type of graph requires more data columns than have been selected

Cause: The number of data columns required for this graph depends on the type of graph selected. This type of graph requires more data columns than were selected.

Action: Select the minimum number of data columns required by the type of graph selected in a previous panel.
Level: 1

Type: ERROR

Impact: Data

REP-31908: The Data Model has changed. Reselect categories and data for the created graph.

Cause: The data model has been changed for an existing graph.

Action: Reselect the categories and data for the graph.
Level: 1

Type: ERROR

Impact: Data

REP-31909: This type of graph requires %s categories.

Cause: The number of categories required for a graph depends on the type of graph selected. This type of graph requires %s categories.

Action: Select the minimum number of categories required by the type of graph selected in a previous panel.
Level: 1

Type: ERROR

Impact: Other

REP-31910: This type of graph requires %s data columns.

Cause: The number of data columns required for this graph depends on the type of graph selected. This type of graph requires %s data columns.

Action: Select the minimum number of data columns required by the type of graph selected in a previous panel.
Level: 1

Type: ERROR

Impact: Data

REP-31950: An error occurred in the Oracle Reports Builder graph support.

Cause: An error occurred initializing the Graph Wizard.

Action: Verify that all components are installed properly. Restart the product.
Level: 1

Type: ERROR

Impact: Other

REP-31951: The Graph Wizard cannot be initialized.

Cause: The Graph Builder library could not be initialized.

Action: Verify that the Graph Wizard and Graphics Runtime are properly installed and that there are enough system resources available.
Level: 1

Type: ERROR

Impact: Other

REP-31952: The Graph Wizard cannot be initialized due to incorrect version of libraries.

Cause: The Graph Builder library could not be initialized.

Action: Verify that the Graph Wizard libraries are properly installed and that there are enough system resources available.
Level: 1

Type: ERROR

Impact: Other

REP-31953: An error occurred in the Graph Wizard.

Cause: The Graph Builder library could not be initialized.

Action: Verify that the Graph Wizard libraries are properly installed and that there are enough system resources available.
Level: 1

Type: ERROR

Impact: Other

REP-31954: An error occurred in the Graph Wizard user interface.

Cause: The Graph Wizard failed to load properly.

Action: Verify that the Graph Wizard libraries are properly installed and that there are enough system resources available.
Level: 1

Type: ERROR

Impact: Other

REP-31955: An error occurred in the graph runtime executable while attempting to create a graph.

Cause: The Graph Builder failed to build the graph.

Action: Verify that the Graph Wizard libraries are properly installed and that there are enough system resources available.
Level: 1

Type: ERROR

Impact: Other

REP-31980: Incorrect field mapping is specified. The graph will not be generated.

Cause: Fields for both category and value axes were not specified in the Graph Wizard.

Action: Reenter the Graph Wizard and specify fields for both Category and Value axes.
Level: 1

Type: ERROR

Impact: Other

REP-31981: The Data Model is empty or invalid.

Cause: The Graph Wizard was invoked on an empty report.

Action: Create report (at least a data model) and try again.
Level: 1

Type: ERROR

Impact: Data

REP-32600: An unexpected error occurred. Aborting.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-32601: The report already exists in a translation file.

Cause: An attempt was made to overwrite an existing translation file.

Action: Select a different name for the translation file.
Level: 1

Type: ERROR

Impact: Other

REP-32602: Oracle Reports Builder cannot be initialized.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-32603: The VGS system cannot be initialized.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-32604: A fatal error occurred loading report {0}. Check version.

Cause: The specified report cannot be loaded.

Action: Verify that the correct version of the report is being opened.
Level: 1

Type: ERROR

Impact: Other

REP-32605: The report file cannot be opened for reading.

Cause: The report file is unreadable.

Action: Check the read permission of the report file.
Level: 1

Type: ERROR

Impact: Other

REP-32606: File {0} cannot be opened for reading.

Cause: The specified file cannot be opened.

Action: Verify that the file exists and is readable.
Level: 1

Type: ERROR

Impact: Other

REP-32607: The translation builder tree does not exist.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-32608: Translations for that language do not exist.

Cause: The Translation Manager cannot translate into the given target language.

Action: Verify that the target language is supported.
Level: 1

Type: ERROR

Impact: Other

REP-32609: This is not a valid report tree.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-32610: Source data file {0} does not match.

Cause: The translation file being merged into the report was not created from the selected report.

Action: Merge the translation file into the original report.
Level: 1

Type: ERROR

Impact: Data

REP-32612: The string for the base language cannot be merged.

Cause: An attempt was made to merge the untranslated strings back into the original report.

Action: Translate the strings in the translation file and try again.
Level: 1

Type: ERROR

Impact: Other

REP-32613: A matching VGS string in NX file cannot be found.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-32614: Successfully merged strings for language {0}.

Cause: The operation was completed with no errors.

Action: No action is necessary.
Level: 1

Type: ERROR

Impact: Other

REP-32615: The merge operation failed.

Cause: The merge operation encountered errors.

Action: Check the log file for more information.
Level: 1

Type: ERROR

Impact: Other

REP-32616: Translations in NX file cannot be found.

Cause: The translation file does not contain translated strings.

Action: Verify that the correct translation file is used for the given report.
Level: 1

Type: ERROR

Impact: Other

REP-32617: The NX file is corrupt.

Cause: An abnormal condition was encountered.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-32618: The NX file cannot be opened for reading.

Cause: The translation file cannot be opened.

Action: Verify that the file exists and is readable.
Level: 1

Type: ERROR

Impact: Other

REP-32750: The data of image {0} cannot be unpacked. The image has been removed.

Cause: Case 1: The image data is corrupted. Case 2: REPORTS_DEFAULT_DISPLAY is set to YES and the image format used is not supported.

Action: Take the following actions to correct this error: If Case 1: Import the image again. If Case 2: Verify that the image format is one of the supported formats: GIF, JPEG, JPG, PNG, BMP.
Level: 1

Type: ERROR

Impact: Data

REP-32751: Some text segments are missing.

Cause: Text segments cannot be found for some boilerplate text. The report could be corrupted.

Action: Check the boilerplate text objects in the report. Remove suspicious ones and create replacements for them.
Level: 1

Type: ERROR

Impact: Other

REP-34202: A value must be entered.

Cause: No value has been entered.

Action: Enter a value.
Level: 1

Type: ERROR

Impact: Other

REP-34203: WARNING: The user modified Format Trigger will be overwritten. Continue?

Cause: Format trigger has been modified.

Action: Click Yes to overwrite the user modified trigger. Click No or Cancel to retain the modified trigger.
Level: 1

Type: ERROR

Impact: Other

REP-34205: At least one condition must be specified.

Cause: No condition was specified in the Format Exception dialog box.

Action: Specify at least one condition.
Level: 1

Type: ERROR

Impact: Other

REP-34300: No distribution list is available.

Cause: No distribution target has been specified for the report.

Action: Create a distribution list.
Level: 1

Type: ERROR

Impact: Other

REP-34301: The value for the field is invalid.

Cause: An invalid value or no value has been entered for the field.

Action: Enter a valid value.
Level: 1

Type: ERROR

Impact: Other

REP-34302: The destination format is not compatible with the runtime mode.

Cause: The destination format must be compatible with the current mode for running the report. Likewise, the destination format must be compatible with all other destination formats in the report. There is no support for mixing bitmap output with character mode output.

Action: Ensure all the destination formats are compatible with either character or bitmap output modes.
Level: 1

Type: ERROR

Impact: Other

REP-34305: The keyword setting for the destid={0} is invalid.

Cause: Keyword settings are incorrect in the distribution file.

Action: Alter the distribution file to ensure that all entries have valid values.
Level: 1

Type: ERROR

Impact: Other

REP-34306: No distribution ID has been specified for the destination.

Cause: In the distribution file, the ID for the destination is missing.

Action: Add a destination ID to the destination line. For example: Dest1:
Level: 1

Type: ERROR

Impact: Other

REP-34307: The destination ID is not unique.

Cause: In the distribution file, the ID for the destination is not unique.

Action: Add a unique destination ID for the entry.
Level: 1

Type: ERROR

Impact: Other

REP-34308: Reference parameter {0} in the distribution list is invalid.

Cause: The reference parameter in the distribution list refers to a wrong group.

Action: Repeat on the same group as that of the reference parameter.
Level: 1

Type: ERROR

Impact: Other

REP-34309: A reference parameter is not allowed in a Report-level distribution list.

Cause: A reference parameter was found in a Report-level distribution list.

Action: Remove the reference paramter distribution item from the Report-level distribution list.
Level: 1

Type: ERROR

Impact: Other

REP-34310: A reference parameter is not allowed in a distribution list for XML destination files.

Cause: An XML destination cannot have a reference parameter in the distribution list.

Action: Remove the reference parameter for the XML file destination from the distribution list.
Level: 1

Type: ERROR

Impact: Other

REP-34311: The XSL transformation file cannot be found.

Cause: The XSL transformation file distribution.xsl could not be located.

Action: Ensure that the XSL file is placed in ORACLE_HOME/reports/conf.
Level: 1

Type: ERROR

Impact: Other

REP-34312: An error occurred in XSL template.

Cause: An error occurred when applying XSL transformation. This could be due to an error in the XSL file.

Action: Check the XSL file and ensure the transformations are correct.
Level: 1

Type: ERROR

Impact: Other

REP-34313: The external file {0} specified in destination {1} cannot be found.

Cause: An external file specified in the distribution list was not found.

Action: Verify the correct path of the external file specified.
Level: 1

Type: ERROR

Impact: Other

REP-34314: The foreach tag cannot be used before both the mail and attach tags at destination {0}.

Cause: The foreach tag was used before both the mail tag and the attach tag.

Action: Correct the entry in the XML distribution file to use a single level of foreach tag.
Level: 1

Type: ERROR

Impact: Other

REP-34315: The instance attribute cannot be used without a foreach tag at destination {0}.

Cause: The instance attribute was used without an enclosing foreach tag.

Action: Correct the entry in the XML distribution file to use a foreach tag at the appropriate level.
Level: 1

Type: ERROR

Impact: Other

REP-34316: Reference parameters cannot be used without a foreach tag in destination {0}.

Cause: Reference parameters were used without a foreach tag.

Action: Correct the entry in the XML distribution file to use a foreach tag appropriately.
Level: 1

Type: ERROR

Impact: Other

REP-34317: The instance attribute cannot be used if 'srctype' is not 'report' in destination {0}.

Cause: The instance attribute was used for a body or attach tag whose source is not a report section.

Action: Correct the entry in the XML distribution file to remove the instance attribute.
Level: 1

Type: ERROR

Impact: Other

REP-34318: The foreach tag cannot be used if 'srctype' is not 'report' in destination {0}.

Cause: A foreach tag was used before an attach tag whose source is not a report section.

Action: Correct the entry in the XML distribution file to remove the foreach tag.
Level: 1

Type: ERROR

Impact: Other

REP-34319: An unknown report section {0} was specified as the source in destination {1}.

Cause: The src attribute in the include tag does not specify a valid report section.

Action: Correct the entry in the XML distribution file to use a valid report section. The valid report sections can be any one of 'headerSection', 'mainSection', 'trailerSection', or 'report'.
Level: 1

Type: ERROR

Impact: Other

REP-34320: Report sections used in destination {1} do not repeat on the same group.

Cause: The report sections used in include tags do not repeat on the same group.

Action: Modify the report definition so that all the sections used repeat on the same group. Use only those report section combinations that repeat on the same group.
Level: 1

Type: ERROR

Impact: Other

REP-34321: Only one external file can be specified in the body or attachment at destination {0}.

Cause: More than one external file was specified for the corresponding body or attach tag. Each body or attach tag whose srctype is file, can have only one include tag referring to an external file.

Action: Correct the entry in the XML distribution file and specify only one external file for the body or attach tag.
Level: 1

Type: ERROR

Impact: Other

REP-34322: Inline text for body or attach tag for destination {0} can be specified only if 'srctype' is 'text'.

Cause: Inline text was specified for a body or an attach tag whose 'srctype' is not 'text'.

Action: Correct the entry in the XML distribution file and specify the correct 'srctype'.
Level: 1

Type: ERROR

Impact: Other

REP-34323: Tag {0} specified for destination {1} cannot be empty.

Cause: An empty tag was encountered. Only the include and the property tags can be empty. All other tags must have at least one child.

Action: Correct the entry in the XML distribution file by either removing the empty tag or inserting the appropriate child tag for it.
Level: 1

Type: ERROR

Impact: Other

REP-34324: Inline text is missing when 'srctype' is 'text' at destination {0}.

Cause: Inline text was not specified for a body or an attach tag whose 'srctype' is specified as 'text'.

Action: Correct the entry in the XML distribution file by specifying the appropriate srctype for the corresponding body or attach tag. If the 'srctype' should be 'text', replace the include tag with inline text.
Level: 1

Type: ERROR

Impact: Other

REP-34325: A reference parameter is not allowed in a distribution list for DelimitedData destination files.

Cause: DelimitedData destination cannot have a reference parameter in the distribution list.

Action: Remove the reference parameter for the DelimitedData file destination from the distribution list.
Level: 1

Type: ERROR

Impact: Other

REP-34326: SPREADSHEET format is not supported in distribution.

Cause: SPREADSHEET destination cannot be used in distribution.

Action: Remove the SPREADSHEET destination from the distribution XML file.
Level: 1

Type: ERROR

Impact: Other

REP-34501: A Web design tool is not registered.

Cause: The mail destination specified is too long. Destination names must be less than 1024 characters. The PREFS.ORA file does not contain an entry for a Web design tool.

Action: Specify a mail destination the 'To' field that is less than 1024 characters. Add an entry for the Web design tool.
Level: 1

Type: ERROR

Impact: Other

REP-34502: The Web design tool registered cannot be found or run.

Cause: The Web design tool does not exist, or the file exists but cannot run.

Action: Correct the PREFS.ORA file and move the Web design program to the correct directory.
Level: 1

Type: ERROR

Impact: Other

REP-34551: Feature {0} is deprecated. See the Oracle Reports documentation for more information.

Cause: The feature is deprecated.

Action: See the Oracle Reports documentation on the Oracle Technology Network (OTN).
Level: 1

Type: ERROR

Impact: Other

REP-34552: The Oracle Graphics Graph in this document will not be saved.

Cause: There are one or more obsolete Oracle Graphics graphs in this document that will not be saved.

Action: Replace the Oracle Graphics graphs with new graphs generated with the Graph Wizard.
Level: 1

Type: ERROR

Impact: Other

REP-35000: The output image format specified is not supported.

Cause: The output image format specified on the command line is not supported by Oracle Reports.

Action: Specify one of the supported output image formats. Refer to the Oracle Reports online help for a list of supported output image formats.
Level: 1

Type: ERROR

Impact: Other

REP-35001: An interanl error occurred writing the image.

Cause: The image stream may be invalid or corrupt. A failure occurred while reading the image data from the image stream.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-35002: The Reports Toolkit System is not available.

Cause: An error occurred initializing the Reports Toolkit System. The required Java classes were not found.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-35003: CGM or OGD format cannot be converted to image for HTML/HTMLCSS output.

Cause: CGM or OGD is used in the report. It is not supported when Display is not available.

Action: Remove the OGD or CGM image used in the report. Set DISPLAY and REPORTS_DEFAULT_DISPLAY to NO. Verify that the image format is one of the supported formats: GIF, JPEG, JPG, PNG, BMP.
Level: 1

Type: ERROR

Impact: Other

REP-35004: The Oracle Reports Font Toolkit Subsystem is not available.

Cause: An error occurred while initializing the Oracle Reports Font Toolkit Subsystem. The required Java classes were not found.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-35503: PDFOWNER and PDFUSER cannot have the same value.

Cause: PDFOWNER and PDFUSER cannot be same.

Action: Specify different values for PDFUSER and PDFOWNER.
Level: 1

Type: ERROR

Impact: Other

REP-50000: A generic error occurred while running the job.

Cause: A generic error occurred while running the job.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-50001: The server is initializing.

Cause: Reports Server is initializing.

Action: Wait until the Reports Server is ready to serve requests.
Level: 1

Type: ERROR

Impact: Other

REP-50002: The server is shutting down.

Cause: The Reports Server is shutting down.

Action: Restart the Reports Server.
Level: 1

Type: ERROR

Impact: Other

REP-50003: The command line is invalid: {0}.

Cause: An invalid command line was submitted.

Action: Refer to the Oracle Reports documentation for command-line arguments and syntax.
Level: 1

Type: ERROR

Impact: Other

REP-50004: No report is specified on the command line.

Cause: There is no report name specified on the command line.

Action: Specify the name of the report on the command line.
Level: 1

Type: ERROR

Impact: Other

REP-50005: No USERID is specified on the command line.

Cause: There is no USERID keyword specified on the command line.

Action: Specify USERID on the command line as part of the database connection information.
Level: 1

Type: ERROR

Impact: Other

REP-50006: The SCHEDULE argument is invalid on the command line: {0}.

Cause: The SCHEDULE argument value on the command line is not correct.

Action: Refer to the Oracle Reports documentation for the correct SCHEDULE argument syntax.
Level: 1

Type: ERROR

Impact: Other

REP-50007: The TOLERANCE argument is invalid on the command line: {0}.

Cause: The TOLERANCE argument value on the command line is not correct.

Action: Refer to Oracle Reports documentation for correct TOLERANCE argument syntax.
Level: 1

Type: ERROR

Impact: Other

REP-50008: The report is successfully submitted.

Cause: The report is successfully submitted to the Reports Server.

Action: No action required.
Level: 1

Type: ERROR

Impact: Other

REP-50009: The report is successfully run.

Cause: The report ran successfully in the Reports Server.

Action: No action required.
Level: 1

Type: ERROR

Impact: Other

REP-50108: The job is waiting in the queue.

Cause: The job is waiting in the queue to be executed.

Action: No action required.
Level: 1

Type: ERROR

Impact: Other

REP-50109: The report is opening to run.

Cause: Opening the report to run.

Action: No action required.
Level: 1

Type: ERROR

Impact: Other

REP-50110: Report {0} is running.

Cause: Running the specified report.

Action: No action required.
Level: 1

Type: ERROR

Impact: Other

REP-50111: Report {0} finished successfully.

Cause: The report has finished successfully.

Action: No action required.
Level: 1

Type: ERROR

Impact: Other

REP-50112: The report terminated with error: {0}.

Cause: The report terminated with the stated error.

Action: Correct the error and rerun the report.
Level: 1

Type: ERROR

Impact: Other

REP-50113: The engine crashed.

Cause: The engine crashed due to an internal error.

Action: For assistance, contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-50114: The job is canceled upon user request.

Cause: The job was canceled at the user's request.

Action: No action required.
Level: 1

Type: ERROR

Impact: Other

REP-50115: The job is canceled as the server is shutting down.

Cause: The job was canceled because the Reports Server is shutting down.

Action: No action required.
Level: 1

Type: ERROR

Impact: Other

REP-50116: The job execution failed and is waiting for retry.

Cause: The job execution has failed and waiting to be retried.

Action: No action required.
Level: 1

Type: ERROR

Impact: Other

REP-50117: The job is sending output.

Cause: The job is sending output to specified destinations.

Action: No action required.
Level: 1

Type: ERROR

Impact: Other

REP-50118: Report execution is initialized.

Cause: Initializing report execution.

Action: No action required.
Level: 1

Type: ERROR

Impact: Other

REP-50119: A Before Report trigger is running.

Cause: The report is running a Before Report trigger.

Action: No action required.
Level: 1

Type: ERROR

Impact: Other

REP-50120: A Between Pages trigger is running.

Cause: The report is running a Between Pages trigger.

Action: No action required.
Level: 1

Type: ERROR

Impact: Other

REP-50121: An After Report trigger is running.

Cause: The report is running an After Report trigger.

Action: No action required.
Level: 1

Type: ERROR

Impact: Other

REP-50122: A Before Parameter Form trigger is running.

Cause: The report is running a Before Parameter Form trigger.

Action: No action required.
Level: 1

Type: ERROR

Impact: Other

REP-50123: An After Parameter Form trigger is running.

Cause: The report is running an After Parameter Form trigger.

Action: No action required.
Level: 1

Type: ERROR

Impact: Other

REP-50124: Page {0} is formatting.

Cause: Oracle Reports is formatting the specified page.

Action: No action required.
Level: 1

Type: ERROR

Impact: Other

REP-50125: An internal exception occurred: {0}.

Cause: Oracle Reports encountered an internal exception.

Action: For assistance, contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-50126: File {0} cannot be opened for writing.

Cause: Oracle Reports cannot open the specified file for writing.

Action: Check the write permission of the file, or of the directory in which the file is stored.
Level: 1

Type: ERROR

Impact: Other

REP-50127: File {0} cannot be written to.

Cause: Oracle Reports cannot write content to the specified file.

Action: Check available disk space to verify that that there is enough space to write the file. Verify that no other applications are writing to the same file.
Level: 1

Type: ERROR

Impact: Other

REP-50131: An attempt to bind to {0} failed.

Cause: Binding to Reports Server failed.

Action: Verify that the Reports Server is running and that it is accessible from this machine.
Level: 1

Type: ERROR

Impact: Other

REP-50133: The job has been transferred to {0}, the new job ID is {1}.

Cause: The job has been transferred to another server.

Action: No action required.
Level: 1

Type: ERROR

Impact: Other

REP-50134: Cache subitem {0} does not exist.

Cause: An internal error occurred. Some of the report output is deleted unexpectedly.

Action: Rerun the job to get the correct output.
Level: 1

Type: ERROR

Impact: Other

REP-50135: Class {0} cannot be located.

Cause: Oracle Reports cannot locate the specified class.

Action: Verify that the specified class is in the CLASSPATH and REPORTS_CLASSPATH.
Level: 1

Type: ERROR

Impact: Other

REP-50136: An error occurred reading the input stream: {0}.

Cause: Oracle Reports cannot read an input stream due to the stated error.

Action: Correct the error and rerun the report.
Level: 1

Type: ERROR

Impact: Other

REP-50137: The input stream cannot be closed: {0}.

Cause: Oracle Reports cannot close the input stream due to the stated error.

Action: For assistance, contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-50138: A mail server is not available.

Cause: There is no mail server specified in Reports Server configuration file.

Action: Add a &lt;mail&gt; element with a server attribute to the Reports Server configuration file.
Level: 1

Type: ERROR

Impact: Other

REP-50139: File {0} cannot be deleted.

Cause: The specified file cannot be deleted.

Action: The file is probably being used by another application. Close that application and try again.
Level: 1

Type: ERROR

Impact: Other

REP-50140: An internal error {0} occurred.

Cause: An internal error occurred.

Action: For assistance, contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-50141: File {0} cannot be opened.

Cause: Oracle Reports cannot open the specified file.

Action: Check whether the specified file exists.
Level: 1

Type: ERROR

Impact: Other

REP-50142: File {0} cannot be read.

Cause: Oracle Reports cannot read the specified file.

Action: Check read permission for specified file.
Level: 1

Type: ERROR

Impact: Other

REP-50143: The job is submitted successfully.

Cause: The job has been submitted successfully.

Action: No action required.
Level: 1

Type: ERROR

Impact: Other

REP-50145: Duplicate parameter {0} is specified.

Cause: The parameter was specified more than once on the command line.

Action: Remove the duplicate parameters.
Level: 1

Type: ERROR

Impact: Other

REP-50148: A Base64 format error occurred.

Cause: An internal error occurred.

Action: For assistance, contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-50149: The parameter value is invalid: {0}.

Cause: Bad parameter value specified.

Action: Refer to the Oracle Reports documentation for the correct syntax for the parameter.
Level: 1

Type: ERROR

Impact: Other

REP-50150: The Reports Server object cannot be accessed.

Cause: An incorrect signature or key to access the Reports Server object was provided.

Action: Verify permission to access the Reports Server, and correct pair of signature keys.
Level: 1

Type: ERROR

Impact: Other

REP-50151: An error occurred while sending the file to the printer: {0} - {1}.

Cause: Error while sending file to specified printer due to the stated reason.

Action: Correct the error and try again.
Level: 1

Type: ERROR

Impact: Other

REP-50152: An error occurred while sending mail: {0}.

Cause: Error while sending mail due to stated reason.

Action: Correct the error and try again.
Level: 1

Type: ERROR

Impact: Other

REP-50153: The mail to list is missing.

Cause: Missing TO or DESNAME parameter for mail. These parameters point to the recipient list of the report.

Action: Add TO or DESNAME to the command line or the URL.
Level: 1

Type: ERROR

Impact: Other

REP-50155: The job status is unknown.

Cause: Unknown job status.

Action: No action required.
Level: 1

Type: ERROR

Impact: Other

REP-50156: The scheduled job has expired.

Cause: The scheduled job has run for specified number of times or its expiration time has passed.

Action: No action required.
Level: 1

Type: ERROR

Impact: Other

REP-50157: An error occurred while sending the file to printer {0}. Exit with error code {1}.

Cause: An error occurred while sending the file to the specified printer.

Action: Check if the printer or printer driver is correctly installed.
Level: 1

Type: ERROR

Impact: Other

REP-50158: Job finished successfully but output is purged from cache.

Cause: The job has finished successfully, but the output has been purged manually or by the cache system and is no longer available.

Action: Rerun the job to regenerate the output.
Level: 1

Type: ERROR

Impact: Other

REP-50159: The report generated successfully but distribution to destinations failed.

Cause: The job has executed successfully, but there were some errors during the distribution of the output.

Action: Check the error for each destination, fix them if possible, and rerun the job.
Level: 1

Type: ERROR

Impact: Other

REP-50160: The report is distributing.

Cause: Oracle Reports is distributing the report.

Action: No action required.
Level: 1

Type: ERROR

Impact: Other

REP-50161: The database connection string {0} is invalid.

Cause: The database connection string format is not correct.

Action: Specify a correct database connection string in the format userid=&lt;username&gt;/&lt;password&gt;@&lt;tnsname&gt;.
Level: 1

Type: ERROR

Impact: Other

REP-50162: The job output is distributing.

Cause: Oracle Reports is distributing the job output.

Action: No action required.
Level: 1

Type: ERROR

Impact: Other

REP-50163: The job output is copying.

Cause: Oracle Reports is copying the job output.

Action: No action required.
Level: 1

Type: ERROR

Impact: Other

REP-50164: The job output is printing.

Cause: Oracle Reports is printing the job output.

Action: No action required.
Level: 1

Type: ERROR

Impact: Other

REP-50165: The job output is mailing.

Cause: Oracle Reports is mailing the job output.

Action: No action required.
Level: 1

Type: ERROR

Impact: Other

REP-50166: The job output is uploading.

Cause: Oracle Reports is uploading the job output.

Action: No action required.
Level: 1

Type: ERROR

Impact: Other

REP-50168: A syntax error occurred in the Reports Server configuration file {0}.

Cause: A syntax error occurred in the specified Reports Server configuration file.

Action: Refer to rwserverconf.xsd for the correct syntax for the server configuration file.
Level: 1

Type: ERROR

Impact: Configuration

REP-50169: The type of the value for attribute {0} is invalid.

Cause: The type of the value for the specified attribute in the server configuration file is not valid.

Action: Refer to rwserverconf.xsd for correct syntax for the attribute.
Level: 1

Type: ERROR

Impact: Other

REP-50170: A syntax error occurred in the Reports Server configuration XSD file {0}.

Cause: A syntax error occurred in the the server configuration XSD file.

Action: Use the original rwserverconf.xsd, without any change.
Level: 1

Type: ERROR

Impact: Configuration

REP-50171: Authentication failed.

Cause: Authentication failed.

Action: Provide the correct authentication information.
Level: 1

Type: ERROR

Impact: Security

REP-50175: File {0} cannot be found.

Cause: Oracle Reports cannot find the specified file.

Action: Check if the file exists on the file system.
Level: 1

Type: ERROR

Impact: Other

REP-50177: The naming service is not available.

Cause: The naming server is down.

Action: Start the naming server.
Level: 1

Type: ERROR

Impact: Other

REP-50180: The naming service failed to shut down.

Cause: Oracle Reports could not stop the naming server.

Action: For assistance, contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-50200: OID server cannot connect.

Cause: The OID server is probably down.

Action: Verify that the OID server is up.
Level: 1

Type: ERROR

Impact: Other

REP-50201: The user role cannot be retrieved from the OID server.

Cause: The OID server is probably down.

Action: Verify that the OID server is up. Also check the Reports Server trace file under $ORACLE_HOME/reports/logs/&lt;server&gt;.trc for more information.
Level: 1

Type: ERROR

Impact: Other

REP-50509: Destination ID {0} failed with error {1}.

Cause: Distribution to the ID failed with specified error.

Action: Check the distribution list and correct the error.
Level: 1

Type: ERROR

Impact: Other

REP-50602: Servlet config file {0} cannot be parsed. {1}.

Cause: The servlet config file could not be parsed. The XML syntax is incorrect.

Action: Correct the servlet config file and start the server.
Level: 1

Type: ERROR

Impact: Other

REP-50603: The servlet file cannot be found {0}. {1}.

Cause: The rwservlet file is not found.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

REP-51000: The Reports Server name is not specified.

Cause: The Reports Server name is not specified on the command line or in the URL.

Action: Specify the Reports Server name as follows: server=&lt;server_name&gt;.
Level: 1

Type: ERROR

Impact: Other

REP-51002: Bind to Reports Server {0} failed.

Cause: Failed to connect to Reports Server.

Action: Verify that Reports Server is running and that the Reports Server name is correct.
Level: 1

Type: ERROR

Impact: Other

REP-51004: Get connection object failed.

Cause: Failed to get a connection object from the server. This can happen because the server has reached the maximum number of connections allowed, or the client does not have privileges to make a connection to the server.

Action: Increase the maxConnect attribute of the connection element and verify that the client has connect privileges to the server.
Level: 1

Type: ERROR

Impact: Other

REP-51015: Sending job output to the client failed due to {0}.

Cause: Failed to send job output to client.

Action: Fix the problem related to stated reason and rerun the job.
Level: 1

Type: ERROR

Impact: Other

REP-51017: The user ID is incomplete.

Cause: The value specified for the user ID was incomplete.

Action: Specify correct syntax for the user ID: &lt;username&gt;/&lt;password&gt;@&lt;tnsname&gt;.
Level: 1

Type: ERROR

Impact: Other

REP-51018: Database user authentication is missing.

Cause: No database user authentication information was provided.

Action: Provide valid database user authentication information.
Level: 1

Type: ERROR

Impact: Security

REP-51019: System user authentication is missing.

Cause: No system user authentication information was provided.

Action: Provide valid system user authentication information.
Level: 1

Type: ERROR

Impact: Security

REP-51020: Authentication for both system user and database user does not match.

Cause: The system and the database user authentication information was different.

Action: Provide the same authentication information for the system and database user.
Level: 1

Type: ERROR

Impact: Security

REP-51021: System and database user authentication is missing.

Cause: No system user and database user authentication information was provided.

Action: Provide valid system and database user authentication information.
Level: 1

Type: ERROR

Impact: Security

REP-51024: The client has not been connected to Reports Server.

Cause: An internal error occurred. The client has not connected to Reports Server before using the server.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-51025: User {0} does not have the privilege to run command {1}.

Cause: An attempt to run the indicated command failed due to insufficient privileges.

Action: Contact the Oracle Reports administrator to request the necessary privileges.
Level: 1

Type: ERROR

Impact: Other

REP-51026: No output is generated for job {0}.

Cause: No output was generated for the indicated job.

Action: Check the report and job definition and rerun the job.
Level: 1

Type: ERROR

Impact: Other

REP-51027: Engine {0} cannot be killed.

Cause: An attempt was made to kill an engine in an older version of Reports Server.

Action: This operation is not supported.
Level: 1

Type: ERROR

Impact: Other

REP-52001: The key map file {0} cannot be read.

Cause: Failed to read the Reports key map file.

Action: Verify that the Reports key map file is in ORACLE_HOME/reports/conf and that it contains valid information.
Level: 1

Type: ERROR

Impact: Other

REP-52002: The key map file {0} cannot be parsed.

Cause: The Reports key map file cannot be parsed.

Action: Verify that the Reports key map file has valid entries.
Level: 1

Type: ERROR

Impact: Other

REP-52003: Read Reports template {0} failed

Cause: The Reports Servlet template cannot be read.

Action: Verify that the Reports Servlet template is in ORACLE_HOME/reports/templates.
Level: 1

Type: ERROR

Impact: Other

REP-52004: The authentication template {0} cannot be read.

Cause: Failed to read the Reports Servlet authentication template.

Action: Verify that the Reports Servlet authentication template is in ORACLE_HOME/reports/templates.
Level: 1

Type: ERROR

Impact: Security

REP-52005: The specified key {0} does not exist in the key map file.

Cause: The specified key does not exist in the Reports key map file.

Action: Verify that the Reports key map file contains the specified key.
Level: 1

Type: ERROR

Impact: Other

REP-52006: The specified URL {0} cannot be decoded.

Cause: The specified URL cannot be decoded.

Action: Verify that the URL is a valid URL.
Level: 1

Type: ERROR

Impact: Other

REP-52007: A Parameter Form format error was encountered.

Cause: The submitted Parameter Form has an invalid format.

Action: Check if the hidden_run_parameters variable in the Parameter Form is null.
Level: 1

Type: ERROR

Impact: Other

REP-52009: No such Web command ({0}).

Cause: The Web command passed in from rwservlet is not a valid command.

Action: Check the help page for rwservlet for a valid Web command.
Level: 1

Type: ERROR

Impact: Other

REP-52010: The specified key map file {0} does not exist.

Cause: The specified key map file does not exist.

Action: Verify that the Reports key map file is in ORACLE_HOME/reports/conf.
Level: 1

Type: ERROR

Impact: Other

REP-52242: The job with job ID {0} cannot be killed.

Cause: Insufficient privileges to perform this operation, or a job with the specified jobid does not exist.

Action: Sufficient privileges are required for this operation. Either log in as administrator or as a user who has sufficient privileges. Specify a valid jobid in the command.
Level: 1

Type: ERROR

Impact: Other

REP-52251: The output of job ID {0} requested on {1} cannot be retrieved.

Cause: Insufficient privileges for this operation, or invalid job ID or nonexistent output.

Action: Sufficient privileges are required for this operation. Check if a valid job ID is provided in the command.
Level: 1

Type: ERROR

Impact: Other

REP-52260: No Oracle Home is specified.

Cause: Oracle Home is not defined in the environment.

Action: Define Oracle Home in the environment. See Configuration chapter in the Publishing Reports to the Web manual for details.
Level: 1

Type: ERROR

Impact: Other

REP-52261: Parameter {0} has an incorrect value {1}.

Cause: The specified parameter has an invalid value.

Action: Provide correct value for the parameter.
Level: 1

Type: ERROR

Impact: Other

REP-52262: Diagnostic output is disabled.

Cause: Reports Server is unsecure, the DIAGNOSTIC property is set to NO in rwservlet.properties file, and a valid AUTHID is not specified in command line.

Action: Specify a valid AUTHID in the command line or contact the system sdministrator.
Level: 1

Type: ERROR

Impact: Other

REP-52265: The specified Web command {0} is not supported.

Cause: The web command is not a valid command for this utility.

Action: Check the Publishing Reports to the Web manual for a list of valid commands for this utility.
Level: 1

Type: ERROR

Impact: Other

REP-52266: The in-process Reports Server {0} failed to start.

Cause: There maybe a server with same name already existing in the network.

Action: Verify that the server is not already started as a stand alone server.
Level: 1

Type: ERROR

Impact: Other

REP-52268: The specified HTML code is not allowed: {0}

Cause: HTML tags were specified in the URL command.

Action: Either remove the HTML tags in the URL and rerun the report, or set ALLOWHTMLTAGS in rwservlet.properties to YES and restart the OC4J container. However, note that any HTML code included as part of the report request URL may lead to a security compromise as it causes certain browsers to execute any script or code in the URL. This property is set to NO by default, disallowing any malicious HTML code to be entered in the URL when running a report.
Level: 1

Type: ERROR

Impact: Other

REP-52280: An Oracle OID generic error occurred.

Cause: Failed to get resource type or resoruce values from OID.

Action: Check the Oracle OID configuration.
Level: 1

Type: ERROR

Impact: Other

REP-52281: The connection to Oracle OID using provider URL {0} cannot be established.

Cause: An attempt to connect to Oracle OID using given provider URL and user ID failed.

Action: Check the Reports Servlet configuration file and verify that the provider URL and user ID are correct.
Level: 1

Type: ERROR

Impact: Other

REP-52282: The specified resource type {0} in OID cannot be found.

Cause: The specified resource type is not created in OID

Action: Verify that the resource type has been defined in OID.
Level: 1

Type: ERROR

Impact: Other

REP-52283: The specified resource key {0} in OID cannot be found.

Cause: The specified resource key is not created in OID

Action: Verify that the resource key has been defined in OID.
Level: 1

Type: ERROR

Impact: Other

REP-52284: The create resource URL cannot be retrieved from OID.

Cause: The create resource URL is not defined in OID.

Action: Verify that the create resource URL has been defined in OID.
Level: 1

Type: ERROR

Impact: Other

REP-52285: The user name or subscriber name cannot be found in Logon Server cookie.

Cause: User is not logged on to Logon Server.

Action: Log on to Logon Server.
Level: 1

Type: ERROR

Impact: Other

REP-52286: Parameter SSOCONN requires the Reports Server to be secure and Single Sign-On turned on.

Cause: Either the Reports Server is running in non-secure mode, or the SINGLESIGNON parameter in rwservlet.properties is set to NO.

Action: Verify that the Reports Server is running in secure mode, and the SINGLESIGNON parameter in rwservlet.properties is set to YES.
Level: 1

Type: ERROR

Impact: Other

REP-52287: Parameter SSOCONN and AUTHID cannot be used together.

Cause: SSOCONN and AUTHID are both used in the command line. The AUTHID value overwrites the SSO userid, and SSOCONN requires the SSO user ID. Therefore, using the keywords together on the command line causes a conflict.

Action: Remove either SSOCONN or AUTHID from the command line.
Level: 1

Type: ERROR

Impact: Security

REP-53000: The connection is invalid.

Cause: An internal error occurred.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-53053: Arguments for the function call are invalid.

Cause: Bad arguments for the function call.

Action: Refer to the Oracle Reports help for the function arguments.
Level: 1

Type: ERROR

Impact: Other

REP-53054: AUTHID is not allowed in the URL.

Cause: AUTHID was specified in the URL.

Action: Either remove AUTHDID in the URL and rerun the report, or set ALLOWAUTHID in rwservlet.properties to YES and restart the OC4J container.
Level: 1

Type: ERROR

Impact: Security

REP-54000: The cache item is not found in the cache system.

Cause: The cache item has been deleted manually or by the cache system.

Action: Submit the request again to rerun the report.
Level: 1

Type: ERROR

Impact: Other

REP-54001: The cache group item is not found in the cache system.

Cause: An internal error occurred.

Action: Submit the request again without use cache. There is no tolerance in the command line or URL.
Level: 1

Type: ERROR

Impact: Other

REP-54002: The cache item is no longer valid.

Cause: The cache item might have been cleaned up by the cache system due to resource constraints.

Action: Submit the request again to rerun the report.
Level: 1

Type: ERROR

Impact: Other

REP-54003: The syntax for the value of the time argument {0} is invalid.

Cause: The syntax for the time argument is incorrect.

Action: Refer to the Oracle Reports documentation for the correct syntax of the time argument.
Level: 1

Type: ERROR

Impact: Other

REP-54004: No cache directory is specified.

Cause: There is no cache directory specified in the server configuration file.

Action: Specify a cache directory in the server configuration file.
Level: 1

Type: ERROR

Impact: Other

REP-54005: The cache directory {0} does not exist.

Cause: The specified cache directory does not exist.

Action: Create a cache directory before starting Reports Server.
Level: 1

Type: ERROR

Impact: Other

REP-54006: The cache directory {0} cannot be created.

Cause: Unable to create a cache directory.

Action: Ensure write permission and enough disk space for the cache directory.
Level: 1

Type: ERROR

Impact: Other

REP-54007: The cacheSize value specified {0} is invalid.

Cause: The cacheSize value specified is not valid.

Action: Correct the cacheSize value in the server config file and start the server.
Level: 1

Type: ERROR

Impact: Other

REP-55005: An engine access violation occurred.

Cause: An incorrect key to access the engine object was provided.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-55006: An attempt to load {0} failed.

Cause: Failed to load the specified dynamic library.

Action: Verify that the dynamic library exists in PATH on NT or LD_LIBRARY_PATH on UNIX.
Level: 1

Type: ERROR

Impact: Other

REP-55008: The report cannot be created. The command line is: {0}.

Cause: An attempt to create a report in the engine specified on the command line failed.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-55009: The Report Engine failed to start. Port {0} specified in the server config file may be already in use.

Cause: The ORB port specified in the config file is not available for the Reports Engine.

Action: Specify a free port.
Level: 1

Type: ERROR

Impact: Ports

REP-55010: An incorrect value is specified for the ORBPorts element.

Cause: The ORB port specified is not in valid format.

Action: Specify a proper integer value for the ORBPorts element.
Level: 1

Type: ERROR

Impact: Other

REP-55100: The urlparameter not specified for the job.

Cause: The URL to be downloaded is not specified in the command line.

Action: Specify the URL in the command line using urlparameter.
Level: 1

Type: ERROR

Impact: Other

REP-55101: A timeout occurred in accessing the URL {0}.

Cause: The engine cannot access the URLstream.

Action: Check if the URL is accessible. If the engine is running behind a firewall, specify the necessary proxy settings in the server configuration file.
Level: 1

Type: ERROR

Impact: Performance

REP-55102: An error occurred setting the proxy information.

Cause: Proxy settings could not be set.

Action: Check if the proxy settings file is valid.
Level: 1

Type: ERROR

Impact: Other

REP-55103: API {0} is not applicable to the URL engine.

Cause: The API used is not applicable to the URL engine.

Action: Verify the API used.
Level: 1

Type: ERROR

Impact: Other

REP-55105: The distribution failed. Verify the distribution list.

Cause: The distribution file may be invalid.

Action: Ensure that the XML distribution file conforms to the DTD.
Level: 1

Type: ERROR

Impact: Other

REP-55106: The DESTYPE value is invalid.

Cause: The destination type (DESTYPE) value is null.

Action: Specify a valid destination type (DESTYPE): FILE, PRINTER, MAIL, or CACHE.
Level: 1

Type: ERROR

Impact: Other

REP-56000: Cluster {0} cannot be joined.

Cause: The Reports Server cluster was not joined because other Reports Servers could not be found.

Action: Verify that this machine can see other Reports Servers. Use osfind to check for other Reports Server on the network.
Level: 1

Type: ERROR

Impact: Other

REP-56001: LocationService cannot be found.

Cause: Unable to locate VisiBroker's LocationService.

Action: This should not happen with VisiBroker 4.5. Report this problem to Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

REP-56003: References for LocationService cannot be resolved.

Cause: References for VisiBroker's LocationService could not be resolved.

Action: This should not happen with VisiBroker 4.5. Report this problem to Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

REP-56014: The arguments for function call {0} are invalid.

Cause: The arguments for the specified function call were invalid.

Action: Refer to jasmine.idl for the function arguments.
Level: 1

Type: ERROR

Impact: Other

REP-56017: Security violation: access to job output not allowed.

Cause: An attempt was made to access job output by a non-owner.

Action: This is security violation, and should not be attempted.
Level: 1

Type: ERROR

Impact: Security

REP-56022: Engine {0} cannot be launched due to {1}.

Cause: The specified engine could not be launched for the stated reason.

Action: Fix the problem described in the message, and restart Reports Server.
Level: 1

Type: ERROR

Impact: Other

REP-56027: An internal error occurred: Engine registration failed.

Cause: An internal error occurred when registering the engine to Reports Server.

Action: Contact Oracle Support Services if problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-56030: The initial engine number must be between minengine ({0}) and maxengine ({1}).

Cause: The value of initEngine is not between the minEngine and maxEngine values specified in the server configuration file.

Action: Change the value of initEngine, minEngine, or maxEngine so that minEngine &lt;= initEngine &lt;= maxEngine.
Level: 1

Type: ERROR

Impact: Other

REP-56033: Job {0} does not exist.

Cause: The requested job does not exist.

Action: Specify a valid ID of a job that exists in the Reports Server.
Level: 1

Type: ERROR

Impact: Other

REP-56034: A job that is in current or scheduled queue cannot be resubmitted.

Cause: An attempt was made to resubmit a job that is in the current or scheduled job queue.

Action: Kill or cancel the job in the current or scheduled queue, then resubmit it.
Level: 1

Type: ERROR

Impact: Other

REP-56035: Connection object cannot be accessed.

Cause: The client did not provide the correct key to access the connection object in Reports Server.

Action: This should not happen; ensure that the connection attempt is legitimate.
Level: 1

Type: ERROR

Impact: Other

REP-56036: The job has been scheduled successfully.

Cause: This is a notification generated when a job has been scheduled successfully.

Action: This is a job submission status. No action is needed.
Level: 1

Type: ERROR

Impact: Other

REP-56040: Server {0} already exists in the network.

Cause: Another Reports Server in the network has the same name.

Action: Specify a different name for this Reports Server.
Level: 1

Type: ERROR

Impact: Other

REP-56041: Proxy server for the Reports 6i client cannot be started.

Cause: A failure occurred when attempting to start the proxy server that is used for the Reports 6i client.

Action: Verify that the Reports Server name is defined in tnsnames.ora.
Level: 1

Type: ERROR

Impact: Other

REP-56042: This function is not supported.

Cause: The invoked function is not supported.

Action: Do not use this function.
Level: 1

Type: ERROR

Impact: Other

REP-56043: No securityUserid is specified in the server configuration file.

Cause: The securityUserid property is missing from the security element specification in the server configuration file.

Action: Add the securityUserid property to the security element in the server configuration file.
Level: 1

Type: ERROR

Impact: Configuration

REP-56044: Parameter {0} has invalid value {1}.

Cause: The specified parameter has an incorrect value.

Action: Refer to the Oracle Reports documentation for the correct parameter value syntax and type.
Level: 1

Type: ERROR

Impact: Other

REP-56045: No Oracle Home is specified.

Cause: No Oracle Home is specified in the Reports Server running environment.

Action: Verify that the ORACLE_HOME environment variable is set in the environment where Reports Server runs.
Level: 1

Type: ERROR

Impact: Other

REP-56046: No method {0} is defined in class {1}.

Cause: No method is defined in the specified Java class.

Action: Add the method into the Java class.
Level: 1

Type: ERROR

Impact: Other

REP-56048: Engine {0} crashed.

Cause: Reports Server detected that the specified engine crashed.

Action: Reports Server should restart another engine. Report the problem to Oracle Support Services with the testcase that caused the engine crash.
Level: 1

Type: ERROR

Impact: Other

REP-56049: No portalUserid is specified in the server configuration file.

Cause: The portalUserid property is missing from the destination element for destype=oraclePortal in the server configuration file.

Action: Add the portalUserid property to the destination element in the server configuration file.
Level: 1

Type: ERROR

Impact: Configuration

REP-56050: Persistent file {0} in invalid or corrupted.

Cause: An attempt to read the Reports Server persistent file failed.

Action: Delete the Reports Server persistent file &lt;server_name&gt;.dat in ORACLE_HOME/reports/server.
Level: 1

Type: ERROR

Impact: Other

REP-56051: The connection to server {0} failed.

Cause: The specified server in the same cluster may be down or not ready.

Action: Verify that the server is up and ready.
Level: 1

Type: ERROR

Impact: Other

REP-56052: The connection to server {0} is dropped.

Cause: The specified server in the same cluster has been shut down.

Action: This is for information only, no action is needed.
Level: 1

Type: ERROR

Impact: Other

REP-56053: Cluster server {0} has been registered.

Cause: The specified server in the same cluster has been registered.

Action: This is for information only, no action is needed.
Level: 1

Type: ERROR

Impact: Other

REP-56054: A connection to server {0} is established.

Cause: The new Reports Server has connected to the specified Reports Server to form a cluster.

Action: This is for information only, no action is needed.
Level: 1

Type: ERROR

Impact: Other

REP-56055: The max connections allowed ({0}) is exceeded.

Cause: There are more concurrent connection attempts than the server is allowed.

Action: Increase the value of the maxConnect attribute of the connection element in the server configuration file if desired.
Level: 1

Type: ERROR

Impact: Other

REP-56062: The repositoryConn property is missing from jobStatusRepository.

Cause: The repositoryConn property is missing from the jobStatusRepository element specification in the server configuration file.

Action: Add the repositoryConn property to the jobStatusRepository element in the server configuration file.
Level: 1

Type: ERROR

Impact: Other

REP-56066: PL/SQL error {0} occurred when inserting job information into the database.

Cause: The indicated PL/SQL error occurred when inserting job information into the database.

Action: Check the PL/SQL error manual for the appropriate action.
Level: 1

Type: ERROR

Impact: Other

REP-56067: PL/SQL error {0} occurred when removing job information from the database.

Cause: The indicated PL/SQL error occurred when removing job information from the database.

Action: Check the PL/SQL error manual for the appropriate action.
Level: 1

Type: ERROR

Impact: Other

REP-56068: PL/SQL error {0} occurred when cleaning job information from the database.

Cause: The indicated PL/SQL error occurred when cleaning information from the database.

Action: Check the PL/SQL error manual for the appropriate action.
Level: 1

Type: ERROR

Impact: Other

REP-56069: An internal error occurred: No cache item for job {0}.

Cause: No cache item associated with the specified job was found.

Action: Resubmit the job.
Level: 1

Type: ERROR

Impact: Other

REP-56070: Error message for error {0} cannot be retrieved.

Cause: An attempt to retrieve the error message for the specified error code failed.

Action: Report the problem to Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

REP-56071: A security check failed with error message {0}.

Cause: A security check failed due to the stated reason.

Action: Verify the privileges to run the report.
Level: 1

Type: ERROR

Impact: Security

REP-56072: The administrator password in the secure server cannot be changed.

Cause: An attempt was made to change the Oracle Reports administrator password in secure mode.

Action: Use Oracle Portal to change the Oracle Reports administrator password.
Level: 1

Type: ERROR

Impact: Other

REP-56073: The password is invalid.

Cause: An attempt was made to change the Oracle Reports administrator password, but the old password provided was incorrect.

Action: Provide the correct old password.
Level: 1

Type: ERROR

Impact: Other

REP-56074: Additional privileges are required to perform the operation.

Cause: An attempt was made to perform an operation for which the user does not have privileges.

Action: Only an Oracle Reports administrator can perform this operation.
Level: 1

Type: ERROR

Impact: Other

REP-56075: The job cannot be reordered if not in the current queue.

Cause: An attempt was made to reorder the job in the past or scheduled job queue.

Action: Reordering jobs can only be done in the current job queue.
Level: 1

Type: ERROR

Impact: Other

REP-56079: The Oracle Portal module status cannot be updated.

Cause: An attempt to update the Oracle Portal module status failed.

Action: Report the problem to Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

REP-56081: The minEngine value ({0}) must be smaller than maxEngine ({1}).

Cause: The value of minEngine is larger than maxEngine in the server configuration file.

Action: Change the value of minEngine or maxEngine so that minEngine &lt;= maxEngine.
Level: 1

Type: ERROR

Impact: Other

REP-56082: The maxEngine value must be larger than minEngine ({0}) and initEngine ({1}).

Cause: The value of maxEngine is smaller than the values of minEngine and initEngine specified in the server configuration file.

Action: Change the value of initEngine, minEngine, or maxEngine so that minEngine &lt;= initEngine &lt;= maxEngine.
Level: 1

Type: ERROR

Impact: Other

REP-56083: The Oracle Portal folder for job {0} cannot be created.

Cause: An attempt to create an Oracle Portal folder for job ouput failed.

Action: Verify permission to create the folder.
Level: 1

Type: ERROR

Impact: Other

REP-56084: The Oracle Portal folder has been created for job {0}.

Cause: This a notification message that the Oracle Portal folder has been created.

Action: This is for information only, no action is needed.
Level: 1

Type: ERROR

Impact: Other

REP-56085: The engineId {0} is invalid.

Cause: An invalid engineId attribute for the job element is specified in the server configuration file.

Action: Check the engineId attribute in the server configuration file.
Level: 1

Type: ERROR

Impact: Other

REP-56091: Job {0} is redirected to engine {1} on server {2}.

Cause: This a notification message that the specified job has been transferred to another server's engine.

Action: This is for information only, no action is needed.
Level: 1

Type: ERROR

Impact: Other

REP-56092: No class is defined for destination type {0}.

Cause: The class attribute is missing for the destination element in the server configuration file.

Action: Specify the java class name for the destination element in the reports server configuration file.
Level: 1

Type: ERROR

Impact: Other

REP-56093: Cached output for job {0} is no longer valid.

Cause: The cached output has been deleted and no longer valid for use.

Action: Rerun the report.
Level: 1

Type: ERROR

Impact: Other

REP-56095: Job {0} is waiting for the Oracle Portal folder to be created.

Cause: This a notification message that the specified job is waiting for the Oracle Portal folder to be created.

Action: This is for information only, no action is needed.
Level: 1

Type: ERROR

Impact: Other

REP-56096: Registration of the remote server is rejected because it does not participate in the cluster

Cause: Another Reports Server tried to register to this Reports Server, but this server does not participate in the cluster.

Action: This is for information only, no action is needed.
Level: 1

Type: ERROR

Impact: Other

REP-56097: Engine {0} callback timeout is reached.

Cause: The Reports engine callback timeout value was reached.

Action: Increase the value of the callbackTimeOut attribute for the engine element in the server configuration file.
Level: 1

Type: ERROR

Impact: Performance

REP-56098: Engine name {0} is invalid.

Cause: The engine name provided to the Reports Server is invalid.

Action: Report the problem to Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

REP-56099: The specified jobtype {0} is not supported.

Cause: The jobtype provided to the Reports Server is invalid.

Action: Check the server configuration file to see what jobtypes are supported.
Level: 1

Type: ERROR

Impact: Other

REP-56100: No engine is defined for jobtype {0}.

Cause: No engine is defined for specified jobtype in the server configuration file.

Action: Define an engine for the specified jobtype in the server configuration file.
Level: 1

Type: ERROR

Impact: Other

REP-56101: Reports Server cannot be shut down remotely when running in process mode.

Cause: An attempt was made to shut down Reports Server remotely when running in process mode.

Action: Shut down the process in which Reports Server is running.
Level: 1

Type: ERROR

Impact: Process

REP-56102: The proxy server has terminated unexpectedly.

Cause: The proxy server terminated unexpectedly.

Action: Check whether the Reports Server tnsname is included in tnsnames.ora.
Level: 1

Type: ERROR

Impact: Other

REP-56103: The proxy server callback has timed out.

Cause: The proxy server has not called back within an expected time.

Action: Report the problem to Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

REP-56104: The pluginParam element {0} is invalid due to {1}.

Cause: An invalid value for the pluginParam element is specified in the server configuration file, most likely the file or URL does not exist.

Action: Verify that the file or URL that is specified for the pluginParam element in the server configuration file is valid.
Level: 1

Type: ERROR

Impact: Other

REP-56105: Engine {0} died with error: {1}.

Cause: The specified engine died for the stated reason.

Action: Fix the error and restart the server.
Level: 1

Type: ERROR

Impact: Other

REP-56106: Engine {0} is destroyed due to timeout.

Cause: The specified Engine did not call back in the expected time.

Action: Increase the value of the callbackTimeOut attribute of the engine element in the server configuration file if desired.
Level: 1

Type: ERROR

Impact: Other

REP-56107: The specified environment ID {0} is invalid for Job Type {1} in the command line.

Cause: An invalid ENVID argument is specified in the command line.

Action: Specify an ENVID that is already defined in the server configuration file (id attribute of environment elelemnt)or define a environment ID in the server configuration file and restart Reports Server.
Level: 1

Type: ERROR

Impact: Other

REP-56108: No connStr property is defined for workflow notification in the server configuration file.

Cause: The connStr property is not specified for workflow nofication in the server configuration file.

Action: Specify a valid connStr (in the format of database connection string) for workflow notification in the server configuration file.
Level: 1

Type: ERROR

Impact: Configuration

REP-56109: Job {0} is terminated due to a connection timeout.

Cause: No activity was detected for the specified job in the timeout period. Either the client has terminated unexpectedly, the client program has hung, or the client program took too long handling other processes.

Action: Check client program status, or if needed, increase the idleTimeOut attribute for connection element in the server configuration file.
Level: 1

Type: ERROR

Impact: Other

REP-56110: The security repository Oracle Portal cannot be connected.

Cause: An attempt to connect to Oracle Portal failed. Oracle Portal is probably down, or an invalid connection string was specified.

Action: Verify that Oracle Portal is up, and the connection string is correct.
Level: 1

Type: ERROR

Impact: Security

REP-56111: Bad or damaged persist file is backed up as: {0}.

Cause: Reports Server shut down abnormally while writing to the indicated file.

Action: Resubmit the lost current and scheduled jobs as information about past, current, and scheduled jobs might be lost. Provide the backed up file when reporting the problem to Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

REP-56112: Backup of the damaged persist file {0} cannot be created.

Cause: The persist file is damaged. Reports Server encountered an error while creating a backup.

Action: Rename the file manually, then restart Reports Server. Resubmit all current and scheduled jobs as information about past, current, and scheduled jobs will be lost.
Level: 1

Type: ERROR

Impact: Other

REP-56113: The JSP report cannot be resubmitted.

Cause: JSP reports are not stored in the Reports Server persistence cache so they cannot be rerun.

Action: Submit a new JSP report to the Reports Server.
Level: 1

Type: ERROR

Impact: Other

REP-56114: The attempt to bind to the naming server failed.

Cause: The naming server may be down.

Action: Start the naming server.
Level: 1

Type: ERROR

Impact: Other

REP-56115: Engine {0} does not exist.

Cause: An attempt was made to access or kill an engine that does not exist.

Action: Provide the correct engine name.
Level: 1

Type: ERROR

Impact: Other

REP-56116: A relative path for desname {0} is not allowed when destype=file.

Cause: A relative path was specified for desname when destype=file, which is not allowed.

Action: Specify the absolute path for desname.
Level: 1

Type: ERROR

Impact: Other

REP-56117: JOBTYPE {0} is invalid.

Cause: An invalid JOBTYPE argument was specified in the command line.

Action: Correct the JOBTYPE argument and resubmit the job.
Level: 1

Type: ERROR

Impact: Other

REP-56118: The report is aborted upon user request.

Cause: This a notification message that the current job was cancelled.

Action: No action required.
Level: 1

Type: ERROR

Impact: Other

REP-56119: An invalid value {0} is specified for attribute {1}.

Cause: The specified value in the server configuration file is invalid for the attribute.

Action: Refer to the Publishing Reports to the Web manual for information about the attribute and valid values.
Level: 1

Type: ERROR

Impact: Other

REP-56120: A syntax error exists on the command line for the Reports Server.

Cause: The syntax for one or more arguments on the command line is invalid.

Action: Refer to the Publishing Reports to the Web manual for correct command-line argument syntax.
Level: 1

Type: ERROR

Impact: Other

REP-56121: Authentication failed.

Cause: The AUTHID specified was invalid.

Action: Specify a correct AUTHID.
Level: 1

Type: ERROR

Impact: Security

REP-56122: Reports Server {0} cannot be connected.

Cause: An attempt to connect to Reports Server failed.

Action: Verify that Reports Server is running and that the Reports Server name is correct.
Level: 1

Type: ERROR

Impact: Other

REP-56123: An insufficient number of ports is assigned for Reports Server and engines in the config file.

Cause: The number of ports assigned is less than the number required to start server and engines.

Action: Increase the number of ORB ports in the server configuration file.
Level: 1

Type: ERROR

Impact: Ports

REP-56124: Report Server failed to start; port {0} specified in the server config file may already be in use.

Cause: The ORB port specified in the server configuration file is not available for the Reports Server.

Action: Specify a free port.
Level: 1

Type: ERROR

Impact: Ports

REP-56125: The ORBPorts property value in the config file is invalid.

Cause: The ORB port specified in the server configuration file is not in a valid format.

Action: Specify proper integer values for ORB ports either as a range (4000-6000), or comma separated values (4000,5000,6000).
Level: 1

Type: ERROR

Impact: Other

REP-56126: The server config file {0} cannot be parsed. {1}.

Cause: An attempt to parse the server config file failed due to invalid XML syntax.

Action: Correct the server configuration file and start the Reports Server.
Level: 1

Type: ERROR

Impact: Other

REP-56127: The {0} element cannot be decrypted.

Cause: An attempt to decrypt the indicated element failed.

Action: Verify that the encrypted property is set properly for the element in the server configuration file.
Level: 1

Type: ERROR

Impact: Other

REP-56128: The {0} destination cannot be initialized. Nested exception: {1}.

Cause: An attempt to initialize the indicated destination failed.

Action: Check and correct the destination element in the server configuration file.
Level: 1

Type: ERROR

Impact: Other

REP-56129: Permission is denied for {0}.

Cause: An attempt to run the report failed due to lack of permissions.

Action: Change the parameter values or contact the Oracle Reports administrator.
Level: 1

Type: ERROR

Impact: Other

REP-56130: Permission to run Web command {0} is not granted.

Cause: An attempt to run the indicated Web command failed due to lack of permissions.

Action: Contact the Oracle Reports administrator.
Level: 1

Type: ERROR

Impact: Other

REP-56131: Permission to run Web command {0} is not granted.

Cause: An attempt to run the indicated Web command failed due to lack of permissions.

Action: Contact the Oracle Reports administrator.
Level: 1

Type: ERROR

Impact: Other

REP-56132: Access is denied to the report definition file.

Cause: An attempt to read the report definition file failed due to lack of permissions.

Action: Contact the Oracle Reports administrator to obtain access privileges.
Level: 1

Type: ERROR

Impact: Other

REP-56133: Access is denied to write to the specified location.

Cause: An attempt to write to the folder failed due to lack of permissions.

Action: Change the desname location or contact the Oracle Reports administrator.
Level: 1

Type: ERROR

Impact: Other

REP-56134: Server config file cannot be found.

Cause: The server configuration file rwserver.conf was not found.

Action: Contact the Oracle Reports administrator.
Level: 1

Type: ERROR

Impact: Other

REP-56135: Reports Server is not started using PCS.

Cause: The Reports Server was not started using PCS in the MAS environment.

Action: Start the server using PCS.
Level: 1

Type: ERROR

Impact: Other

REP-56136: An error occurred retrieving the environment required to spawn the engine.

Cause: An attempt to retrieve needed environment variables failed.

Action: Contact the Oracle Reports administrator.
Level: 1

Type: ERROR

Impact: Other

REP-56137: The minEngine value must be smaller than maxEngine {0} and initEngine {1}.

Cause: The value of minEngine is larger than maxEngine and initEngine in the server configuration file.

Action: Change the value of initEngine, minEngin, or maxEngine so that minEngine &lt;= initEngine &lt;= maxEngine.
Level: 1

Type: ERROR

Impact: Other

REP-56138: Job {0} has completed execution.

Cause: An attempt was made to kill a job that was running or scheduled.

Action: Check the job status. Only jobs that are running or scheduled can be killed.
Level: 1

Type: ERROR

Impact: Other

REP-56139: The requested operation is unauthorized.

Cause: An attempt to perform an operation failed due to lack of proper authorization.

Action: Contact the Oracle Reports administrator.
Level: 1

Type: ERROR

Impact: Other

REP-57000: An internal error occurred in the Oracle Reports API:

Cause: An internal error occurred.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-57001: The in-process server is not initialized.

Cause: An internal error occurred.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-57002: An attempt to load {0} failed.

Cause: An internal error occurred.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-57003: A column data type {0} is not valid.

Cause: A column in the report contains an unsupported data type.

Action: Use only supported datatypes. Refer to the Oracle Reports documentation for supported datatypes.
Level: 1

Type: ERROR

Impact: Data

REP-57004: The value of column {0} cannot be retrieved, cursor out of range in cache.

Cause: An internal error occurred.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-57005: The value of column {0} cannot be retrieved in cache.

Cause: An internal error occurred.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-57052: An internal error occurred in the in-process server.

Cause: An internal error occurred.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-58000: Attribute value {0} for attribute name {1} in tag {2} is invalid.

Cause: The value of the attribute for the JSP tag is invalid.

Action: Verify that the attribute value is valid. Refer to the Reference&gt;Oracle Reports JSP tags section of the Oracle Reports online Help.
Level: 1

Type: ERROR

Impact: Other

REP-58001: Either tag attribute {0} or {1} must exist in tag {2}.

Cause: One of the specified two optional attributes must exist.

Action: Specify at least one of the two attributes.
Level: 1

Type: ERROR

Impact: Other

REP-58002: A cursor for group {0} cannot be created.

Cause: A cursor object cannot be created for a group in an rw:foreach or an rw:graph tag.

Action: Verify that the group name is valid.
Level: 1

Type: ERROR

Impact: Other

REP-58004: Format trigger {0} cannot be run.

Cause: Failed to run a PL/SQL format trigger in an rw:field tag.

Action: Verify that the name of the format trigger is correct.
Level: 1

Type: ERROR

Impact: Other

REP-58005: There is no current report for group {0}.

Cause: There is no report object for the rw:foreach tag.

Action: Verify that a report object is created by enclosing the report block inside the rw:report tag.
Level: 1

Type: ERROR

Impact: Other

REP-58006: There is no current report for layout object {0}.

Cause: There is no report object for the rw:include tag.

Action: Verify that a report object is created by enclosing the report block inside the rw:report tag.
Level: 1

Type: ERROR

Impact: Other

REP-58008: There is no current report for column {0}.

Cause: There is no report object for the rw:field or rw:getValue tags.

Action: Verify that a report object is created by enclosing the report block inside the rw:report tag.
Level: 1

Type: ERROR

Impact: Other

REP-58009: A cursor containing column {0} cannot be found.

Cause: The column does not belong to any of the enclosing cursors.

Action: Verify that the column name is valid.
Level: 1

Type: ERROR

Impact: Other

REP-58010: Data type {0} is not supported.

Cause: Invalid dataType attribute (NOT USED CURRENTLY) in rw:getValue.

Action: Use any of the supported data types.
Level: 1

Type: ERROR

Impact: Data

REP-58011: ID {0} in {1} tag is used in a previous {2} tag.

Cause: The value for the ID attribute is not unique.

Action: Use a unique ID value.
Level: 1

Type: ERROR

Impact: Other

REP-58012: Only one rw:report tag is allowed in a JSP report.

Cause: There is more than one rw:report tag in the JSP report.

Action: Verify that there is only one rw:report tag in the JSP report.
Level: 1

Type: ERROR

Impact: Other

REP-58013: Only one rw:objects tag is allowed in a JSP report.

Cause: More than one rw:objects tags exists in the JSP report.

Action: Verify that there is only one rw:objects tag in the JSP report.
Level: 1

Type: ERROR

Impact: Other

REP-58014: rw:objects must be the first JSP tag in rw:report body.

Cause: A JSP tag other than rw:object is the first Reports JSP tag in the body of the rw:report tag.

Action: Verify that there is only one rw:objects tag in the body of the rw:report tag. The rw:objects tag must be the first Reports JSP tag inside the body of the rw:report tag.
Level: 1

Type: ERROR

Impact: Other

REP-58015: breakLevel {0} in the rw:field tag does not match the ID of any enclosing rw:foreach.

Cause: The value of a breakLevel attribute from an rw:field tag does not match the ID of any enclosing rw:foreach tags.

Action: Verify that the value for the breakLevel attribute is valid.
Level: 1

Type: ERROR

Impact: Other

REP-58016: The formatMask {0} attribute is not valid.

Cause: The value of a formatMask attribute from an rw:field or an rw:getValue tag is invalid.

Action: Verify that the value for the formatMask attribute is valid.
Level: 1

Type: ERROR

Impact: Other

REP-58017: FormatTrigger {0} in rw:field tag is not a valid PL/SQL program unit.

Cause: The value of the formatTrigger attribute from an rw:field tag is not a program unit name, or it has an invalid signature.

Action: Verify that the value for the formatTrigger attribute is valid.
Level: 1

Type: ERROR

Impact: Other

REP-58018: Column name {0} in {1} of rw:graph is not valid.

Cause: A column name specified in one of the attributes of the rw:graph tag is not valid.

Action: Verify that the column name is valid. Refer to the Reference&gt;Oracle Reports JSP tags section of the Oracle Reports online Help for the correct syntax of the attributes.
Level: 1

Type: ERROR

Impact: Other

REP-58019: Tag {0} (ID {1}) is not in rw:report body.

Cause: A Reports JSP tag is not in a rw:report tag's body.

Action: Add the tag in a rw:report body.
Level: 1

Type: ERROR

Impact: Other

REP-58100: An error occurred starting the internal Web server at port {0}. Error: {1}.

Cause: Errors occurred while starting the internal Web server.

Action: Verify that the port is not in use. Also check the .log files and log directory under (docroot)/port# for more information. Unless specified from the command line, the docroot should be located at under $REPORTS_TMP/docroot.
Level: 1

Type: ERROR

Impact: Ports

REP-58101: An error occurred stopping the internal Web server: {0}.

Cause: Errors were encountered while stopping the internal Web server.

Action: Check the .log files and config directory under (docroot)/port# for more information. Unless specified on the command line, the docroot is located in the $REPORTS_TMP/docroot directory.
Level: 1

Type: ERROR

Impact: Other

REP-58102: An error occurred sending request {0} to the internal Web server: {1}.

Cause: Errors were encountered when sending the JSP to the internal Web server.

Action: Check the .log files and the log directory under (docroot)/port# for more information. Unless specified on the command line, the docroot is located in the $REPORTS_TMP/docroot directory.
Level: 1

Type: ERROR

Impact: Requests/Responses

REP-58103: An error occurred configuring the internal Web server: {0}.

Cause: Errors were encountered when configuring the configuration files from the internal Web server.

Action: Check the .log files and config directory under (docroot)/port# for more information. Unless specified on the command line, the docroot is located in the $REPORTS_TMP/docroot directory.
Level: 1

Type: ERROR

Impact: Other

REP-58104: Port {0} is in use.

Cause: The port specified from the command line is in use.

Action: Specify a different port, or allow Reports to choose a free port.
Level: 1

Type: ERROR

Impact: Ports

REP-58105: A free port within the {0} to {1} range cannot be automatically found for the internal Web server.

Cause: All ports within the range appear to be in use.

Action: Specify a free port to use from the command line.
Level: 1

Type: ERROR

Impact: Ports

REP-58106: Begin port {0} must be less than end port {1}.

Cause: The begin port is greater or equal to end port.

Action: Specify a begin port less than end port from the command line.
Level: 1

Type: ERROR

Impact: Ports

REP-58107: Port numbers must be within range 1-65536.

Cause: The port used is not within the specified range.

Action: Specify a free port in the specified range from the command line.
Level: 1

Type: ERROR

Impact: Ports

REP-58108: HTML tags are not allowed: {0}.

Cause: HTML tags were specified in the query string.

Action: Remove the HTML tags in the query string and rerun the report.
Level: 1

Type: ERROR

Impact: Other

REP-58109: Web server cannot be created.

Cause: A problem was encountered while attempting to create the Web server.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

REP-60003: An error occurred retrieving the environment required to spawn the engine.

Cause: Reports Server was unable to retrieve the current environment setting prevailing on the system.

Action: Ensure that rwu90.dll is installed and available in the system path on Windows. On UNIX, ensure that librwu90.so is installed and available in the LD_LIBRARY_PATH environment variable.
Level: 1

Type: ERROR

Impact: Other

REP-62000: Connection class {0} cannot be loaded.

Cause: The connection class mentioned in the configuration file jdbcpds.conf for the selected driver is invalid.

Action: Ensure that a valid driver connection class is specified in the configuration file jdbcpds.conf and that it is available.
Level: 1

Type: ERROR

Impact: Other

REP-62001: No entry is present for the driver {0} in the jdbcpds.conf file.

Cause: The driver used in query is not specified in the configuration file jdbcpds.conf.

Action: Ensure that the entry for the required driver along with the related driver information is specified in the configuration file jdbcpds.conf.
Level: 1

Type: ERROR

Impact: Configuration

REP-62002: The data source cannot be connected.

Cause: The connection information is invalid.

Action: Ensure that the username, password, database, and driver type are all valid.
Level: 1

Type: ERROR

Impact: Data

REP-62003: Configuration file jdbcpds.conf cannot be found.

Cause: The configuration file jdbcpds.conf is not found in the reports/conf directory.

Action: Ensure that the configuration file jdbcpds.conf is available in the reports/conf directory.
Level: 1

Type: ERROR

Impact: Configuration

REP-62004: A parsing error occurred in the configuration file jdbcpds.conf. Number of errors: {0}

Cause: The XML section in the configuration file jdbcpds.conf does not conform with its inline DTD.

Action: Ensure that the XML section in jdbcpds.conf refers to the correct inline DTD.
Level: 1

Type: ERROR

Impact: Configuration

REP-62005: An error occurred on line number {0}.

Cause: An error was found on the specified line of the configuration file jdbcpds.conf.

Action: Correct the error on the specified line.
Level: 1

Type: ERROR

Impact: Other

REP-62006: The lexical parameter {0} used in the query is invalid.

Cause: The lexical parameter used in the query or procedure is invalid.

Action: Ensure that the query or procedure uses valid lexical parameters. Create new parameters if they are not available.
Level: 1

Type: ERROR

Impact: Other

REP-62007: A SQL error occurred: {0}.

Cause: The data source has reported this SQL syntax error in the specified query or procedure.

Action: Ensure that the syntax of the query or procedure is valid. Refer to the documentation of the specific data source.
Level: 1

Type: ERROR

Impact: Other

REP-62008: The query or procedure for the specified data source is invalid.

Cause: The syntax of the query or procedure is invalid for the specified data source.

Action: Ensure that the syntax of the query or procedure is valid. Refer to the documentation of the specific data source.
Level: 1

Type: ERROR

Impact: Data

REP-62009: The reference parameter value is invalid.

Cause: The value of the reference parameter is invalid.

Action: Verify that the reference column types and values are correct.
Level: 1

Type: ERROR

Impact: Other

REP-62010: A query or procedure is missing.

Cause: The query or procedure text field is empty.

Action: Type a valid query or procedure in the text area.
Level: 1

Type: ERROR

Impact: Other

REP-62011: The database URL {0} is invalid.

Cause: Invalid database URL.

Action: Verify the specified database name and the selected driver type.
Level: 1

Type: ERROR

Impact: Other

REP-62012: Either the number of columns or the types of columns does not match the query definition.

Cause: The data fetched does not match the number of columns or the column types that are specified in the query definition.

Action: Verify that both the number of columns and the column types match the query definition.
Level: 1

Type: ERROR

Impact: Other

REP-62013: The column type {0} used in the query/procedure is not supported by the Reports JDBC query.

Cause: This column type is not supported by the Reports JDBC query interface.

Action: Ensure that only column types that are supported by the Reports JDBC query interface are used. Refer to the JDBC specification and the Reports documentation for supported types.
Level: 1

Type: ERROR

Impact: Other

REP-62014: The inline DTD section of the configuration file jdbcpds.conf has been modified.

Cause: The format of the inline DTD section in the configuration file jdbcpds.conf has been altered.

Action: If the DTD format is modified, ensure that the configuration file is valid as per the JDBCPDS requirement.
Level: 1

Type: ERROR

Impact: Configuration

REP-62015: The sign-on parameter {0} is invalid.

Cause: The specified sign-on parameter for the query or procedure is invalid.

Action: Ensure that the sign-on parameter is available and valid for the JDBC query type in the report.
Level: 1

Type: ERROR

Impact: Other

REP-62016: The sign-on parameter value {0} is invalid.

Cause: The specified connect string for this sign-on parameter is invalid.

Action: Ensure that the specified connect string for this sign-on parameter is valid for the selected driver.
Level: 1

Type: ERROR

Impact: Other

REP-62017: A reference parameter of type Date is not supported by the JDBC driver used.

Cause: The driver used to connect to database does not support the Date data type as reference parameter.

Action: Use the String data type for the reference parameter or use a different JDBC driver that supports the Date data type as reference parameter.
Level: 1

Type: ERROR

Impact: Other

REP-62200: No image exists for the specified ID {0}

Cause: The image ID specified does not map to an existing image object in the store.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-62201: The image source is invalid

Cause: The image source is not valid.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-62202: Unsupported image format

Cause: The format of the image used is not supported.

Action: Ensure that the report uses a supported image format as specified in the Oracle Reports documentation.
Level: 1

Type: ERROR

Impact: Other

REP-62203: Internal error reading the image {0}

Cause: The image data appears to be corrupt or invalid.

Action: Ensure that the image is valid. For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-62204: Internal error writing the image {0}

Cause: There was an internal error writing the image to the output stream.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-62205: Internal error during color reduction

Cause: An error occurred doing color reduction on GIF images.

Action: Use a diffent GIF image with lesser colors or chose another image format.
Level: 1

Type: ERROR

Impact: Other

REP-62206: The input image used is corrupt or invalid

Cause: The image data appears to be corrupt or invalid.

Action: Ensure that the image is valid.
Level: 1

Type: ERROR

Impact: Other

REP-62207: Encountered an unsupported version of GIF image

Cause: This GIF version is not supported.

Action: Ensure that the GIF images used adhere to the standards specified in the Oracle Reports documentation.
Level: 1

Type: ERROR

Impact: Other

REP-62350: URL {0} is invalid.

Cause: The location pointed to by the URL appears to be invalid.

Action: Ensure that the location pointed to by the URL is valid.
Level: 1

Type: ERROR

Impact: Other

REP-62351: The proxy setting specified in proxyinfo.xml will be not be effective.

Cause: The proxy setting was ignored due to an invalid configuration in the proxyinfo.xml file.

Action: Ensure that the proxy setting in proxyinfo.xml is correct.
Level: 1

Type: ERROR

Impact: Other

REP-62352: The FTP proxy server specified is not responding : {0}.

Cause: The proxy specified in the proxyinfo.xml file does not support SOCKS protocol.

Action: Ensure that the proxy supports SOCKS protocol.
Level: 1

Type: ERROR

Impact: Other

REP-62353: The destination file name is missing.

Cause: Destination file name missing in the desname argument.

Action: Specify a valid destination file name.
Level: 1

Type: ERROR

Impact: Other

REP-62354: The directory specified is invalid.

Cause: Invalid directory is specified in the desname argument.

Action: Specify a valid directory path.
Level: 1

Type: ERROR

Impact: Other

REP-62370: URL {0} is invalid.

Cause: The location pointed to by the URL appears to be invalid.

Action: Ensure that the location pointed by the URL is valid.
Level: 1

Type: ERROR

Impact: Other

REP-62371: The proxy setting specified in proxyinfo.xml is not be effective.

Cause: The proxy setting was ignored due to an invalid configuration in the proxyinfo.xml file.

Action: Ensure that the proxy setting in proxyinfo.xml is correct.
Level: 1

Type: ERROR

Impact: Other

REP-63000: No URL specified for {0}

Cause: There was no URL specified for either the data definition or the data source.

Action: Specify a URL for both the data definition and the data source.
Level: 1

Type: ERROR

Impact: Other

REP-63001: Invalid stream in the Data Definition URL {0}

Cause: The Data Stream pointed to by the URL appears to be invalid.

Action: Ensure that the XML Stream pointed to by the URL is valid.
Level: 1

Type: ERROR

Impact: Data

REP-63002: URL specified has an invalid XML stream: {0}

Cause: The URL appears to have invalid XML stream.

Action: Ensure that the XML stream pointed to by the URL contains valid XML.
Level: 1

Type: ERROR

Impact: Other

REP-63003: URL {0} read error

Cause: Could not access the specified URL. A timeout occurred while accessing the URL.

Action: Ensure that the URL is accessible and check that the proxy information in the xmlpds.conf file is correct.
Level: 1

Type: ERROR

Impact: Other

REP-63004: Generic error while parsing the URL stream {0}

Cause: The data stream pointed to by the URL appears to be invalid.

Action: Ensure that the XML stream pointed to by the URL is valid.
Level: 1

Type: ERROR

Impact: Other

REP-63005: The Inline DTD section of xmlpds.conf file has been modified

Cause: The Inline DTD section of the configuration file xmlpds.conf has been modified.

Action: Ensure that the configuration file is still valid, per the XMLPDS requirement.
Level: 1

Type: ERROR

Impact: Configuration

REP-63006: Invalid reference parameter value

Cause: The value of the reference parameter is invalid.

Action: Verify that the types and values of the referenced columns are correct.
Level: 1

Type: ERROR

Impact: Other

REP-63007: Configuration file xmlpds.conf not found

Cause: The configuration file xmlpds.conf was not found in the reports/conf directory.

Action: Ensure that the configuration file xmlpds.conf is located in the reports/conf directory.
Level: 1

Type: ERROR

Impact: Configuration

REP-63008: Parsing error in the xmlpds.conf configuration file Number of errors: {0}

Cause: The XML section in the xmlpds.conf file does not conform with the corresponding inline DTD.

Action: Ensure the XML section in the xmlpds.conf file conforms with the corresponding inline DTD.
Level: 1

Type: ERROR

Impact: Configuration

REP-63009: The proxy setting specified in xmlpds.conf will be not be effective

Cause: The proxy setting was ignored due to an invalid configuration in the xmlpds.conf file.

Action: Ensure that the proxy setting in the configuration file xmlpds.conf is correctly specified.
Level: 1

Type: ERROR

Impact: Configuration

REP-63500: No URL is specified for data source {0}/

Cause: There was no URL specified for the data source.

Action: Specify a URL for the data source.
Level: 1

Type: ERROR

Impact: Data

REP-63501: The specified URL {0} is not compatible with the file format {1} at line number {2}.

Cause: The URL appears to have invalid content.

Action: Ensure that the content pointed to by the URL is a valid file format.
Level: 1

Type: ERROR

Impact: Other

REP-63502: The data is invalid.

Cause: Content is not compatible with the file format selected.

Action: Ensure that the text is valid for the file format selected.
Level: 1

Type: ERROR

Impact: Data

REP-63503: Either the number of columns or the type of columns does not match the query definition.

Cause: The data fetched does not match the number of columns or the column types that are specified in the query definition.

Action: Verify that both the number of columns and the column types match the query definition.
Level: 1

Type: ERROR

Impact: Other

REP-63504: A read error occurred in accessing URL {0}.

Cause: Could not access the specified URL. A timeout occurred while accessing the URL.

Action: Ensure that the URL is accessible and check that the proxy information in the textpds.conf file is correct.
Level: 1

Type: ERROR

Impact: Other

REP-63505: The Inline DTD section of textpds.conf has been modified.

Cause: The Inline DTD section of the configuration file textpds.conf has been modified.

Action: Ensure that the configuration file is still valid, per the TextPDS requirement.
Level: 1

Type: ERROR

Impact: Configuration

REP-63506: The reference parameter is invalid.

Cause: The reference parameter is invalid.

Action: Verify that the name, types, and values of the referenced columns are correct.
Level: 1

Type: ERROR

Impact: Other

REP-63507: The configuration file textpds.conf cannot be found.

Cause: The configuration file textpds.conf was not found in the reports/conf directory.

Action: Ensure that the configuration file textpds.conf is located in the reports/conf directory.
Level: 1

Type: ERROR

Impact: Configuration

REP-63508: A parsing error occurred in textpds.conf. Number of errors: {0}.

Cause: The XML section in the textpds.conf file does not conform with the corresponding inline DTD.

Action: Ensure the XML section in the textpds.conf file conforms with the corresponding inline DTD.
Level: 1

Type: ERROR

Impact: Other

REP-63509: The proxy setting specified in textpds.conf is invalid.

Cause: The proxy setting was ignored due to an invalid configuration in the textpds.conf file.

Action: Ensure that the proxy setting in the configuration file textpds.conf is correctly specified.
Level: 1

Type: ERROR

Impact: Configuration

REP-63510: No fileFormat is specified in textpds.conf.

Cause: The entry for fileFormat in textpds.conf is missing.

Action: Ensure that at least one fileFormat element is specified in the textpds.conf.
Level: 1

Type: ERROR

Impact: Other

REP-63511: The fileFormat specification is invalid.

Cause: The entry for fileFormat in textpds.conf is invalid.

Action: Ensure that fileFormat is specified per the DTD of textpds.conf.
Level: 1

Type: ERROR

Impact: Other

REP-63512: No entry is present for fileFormat {0} in textpds.conf.

Cause: The fileFormat used in the query is not defined in textpds.conf.

Action: Ensure that the entry for the required fileFormat along with the column information is specified in textpds.conf.
Level: 1

Type: ERROR

Impact: Other

REP-63513: The Serialized XML section of the saved report is invalid.

Cause: The Serialized XML section has been modified.

Action: Ensure that Serialized XML section is specified per the TextPDS format.
Level: 1

Type: ERROR

Impact: Other

REP-63514: The column type {0} used in the query is not supported by a Text query.

Cause: This column type is not supported by the Text query interface.

Action: Ensure that only column types that are supported by the Text query interface are used. Refer to the TextPDS specification and the Oracle Reports documentation for supported types.
Level: 1

Type: ERROR

Impact: Other

REP-63515: The data in log file {0} is not according to the date pattern {1} specified in the config file.

Cause: The data in the log file is not valid according to the date pattern specified in the config file.

Action: Ensure that data in the log file is specified according to the date pattern.
Level: 1

Type: ERROR

Impact: Data

REP-64000: No Oracle Home is specified.

Cause: ORACLE_HOME is missing in the command line.

Action: Specify ORACLE_HOME=&lt;oracle_home_dir&gt; in the command line.
Level: 1

Type: ERROR

Impact: Other

REP-64001: The Oracle Reports Bridge failed to start.

Cause: The Oracle Reports Bridge failed to start.

Action: Check log file for detailed message and take appropriate action.
Level: 1

Type: ERROR

Impact: Other

REP-64002: The Oracle Reports Bridge initialization failed {0}.

Cause: The Oracle Reports Bridge initialization failed.

Action: Check the actual message and take appropriate action.
Level: 1

Type: ERROR

Impact: Other

REP-64003: The local port is not set. One-way Oracle Reports Bridge is started.

Cause: One-way Oracle Reports Bridge is started.

Action: No action needed. Set local port to start two-way bridge if needed.
Level: 1

Type: ERROR

Impact: Ports

REP-64004: AUTHID is not specified.

Cause: AUTHID argument is not specified in command line.

Action: Specify AUTHID=&lt;username&gt;/&lt;password&gt; in the command line.
Level: 1

Type: ERROR

Impact: Security

REP-64005: Authentication failed.

Cause: The AUTHID specified was invalid.

Action: Specify a correct AUTHID.
Level: 1

Type: ERROR

Impact: Security

REP-64006: The Oracle Reports Bridge shutdown failed.

Cause: An attempt to shut down The Oracle Reports Bridge failed.

Action: Check the trace for detailed message and take appropriate action.
Level: 1

Type: ERROR

Impact: Other

REP-64009: The Oracle Reports Bridge is already running.

Cause: Another Oracle Reports Bridge is already running with the same port.

Action: Change the port in the config file and start again.
Level: 1

Type: ERROR

Impact: Other

REP-64010: The local listener failed to start.

Cause: The open socket could not be opened.

Action: Check socket is available and usable.
Level: 1

Type: ERROR

Impact: Other

REP-64011: Request {0} cannot be served.

Cause: Unable to serve the Oracle Reports Bridge request.

Action: Check the actual message and take appropriate action.
Level: 1

Type: ERROR

Impact: Requests/Responses

REP-64012: A fatal error {0} occurred. Restart the Oracle Reports Bridge.

Cause: The Oracle Reports Bridge is not able to serve any request.

Action: Restart the Oracle Reports Bridge.
Level: 1

Type: ERROR

Impact: Other

REP-64013: The Oracle Reports Bridge failed to serve the request {0}.

Cause: An internal error occurred.

Action: Check the actual message; the Oracle Reports Bridge may recover from this error.
Level: 1

Type: ERROR

Impact: Requests/Responses

REP-64014: The Oracle Reports Bridge name is not specified.

Cause: The NAME=&lt;bridgename&gt; argument is missing in the command line.

Action: Specify NAME=&lt;bridgename&gt; in the command line.
Level: 1

Type: ERROR

Impact: Other

REP-64015: The command is invalid.

Cause: Invalid command-line argument.

Action: Check command-line arguments.
Level: 1

Type: ERROR

Impact: Other

REP-64016: Cannot connect to the Oracle Reports Bridge {0}.

Cause: The Oracle Reports Bridge is not running on specified port.

Action: The Oracle Reports Bridge may be down. Or check the Bridge port in Bridge config file and try again.
Level: 1

Type: ERROR

Impact: Other

REP-64017: The Oracle Reports Bridge config file is not found.

Cause: Configuration file rwbridge.conf is not found.

Action: Contact the Oracle Reports administrator.
Level: 1

Type: ERROR

Impact: Other

REP-64018: The Oracle Reports Bridge is not started using PCS.

Cause: The Oracle Reports Bridge is not started using PCS in the MAS environment.

Action: Start the Oracle Reports Bridge using PCS.
Level: 1

Type: ERROR

Impact: Other

REP-65001: Communication error {0} occurred.

Cause: A network IO error occurred.

Action: Check the actual message and take appropriate action.
Level: 1

Type: ERROR

Impact: Other

REP-65002: The communication channel {0} cannot be initialized.

Cause: Multicast initialization failed.

Action: Check the actual message and take appropriate action.
Level: 1

Type: ERROR

Impact: Other

REP-65003: The request timed out.

Cause: Waiting for a response from the server timed out.

Action: No action required. If all retries fail, increase the timeout value in the network config file.
Level: 1

Type: ERROR

Impact: Requests/Responses

REP-65004: The naming server cannot be bound.

Cause: Naming service may be down.

Action: Start the naming service and try again.
Level: 1

Type: ERROR

Impact: Other

REP-65005: The network config file cannot be found.

Cause: rwnetwork.conf is not found.

Action: Contact the Oracle Reports administrator.
Level: 1

Type: ERROR

Impact: Network

REP-80001: An internal error occurred.

Cause: Unexpected internal exception.

Action: For assistance, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

REP-80002: The report object is invalid.

Cause: The report object is invalid, possibly invalid object handle, or an already deleted object.

Action: Discard this object handle and get a new one.
Level: 1

Type: ERROR

Impact: Other

REP-80003: The report object name is invalid.

Cause: The name does not follow report object naming rules; for example, it may contain an invalid character.

Action: Follow the report object naming rules to create a valid name.
Level: 1

Type: ERROR

Impact: Other

REP-80004: A dialog window not allowed at this time.

Cause: The Plugin tried to display a dialog window when it is not allowed; for example, when Reports is running in batch mode.

Action: Plugin must not raise a dialog window when it is not allowed.
Level: 1

Type: ERROR

Impact: Other

REP-80005: The dialog window location is invalid.

Cause: The requested dialog window location is invalid.

Action: Set a valid dialog window location.
Level: 1

Type: ERROR

Impact: Other

REP-80006: The dialog window size is invalid.

Cause: The requested dialog window size is invalid.

Action: Set a valid dialog window size.
Level: 1

Type: ERROR

Impact: Other

REP-80007: The help system cannot be displayed.

Cause: Failure to display online help.

Action: Check the online help system setup.
Level: 1

Type: ERROR

Impact: Other

REP-80008: The helpset ID is invalid.

Cause: Invalid helpset ID.

Action: Correct the helpset ID.
Level: 1

Type: ERROR

Impact: Other

REP-80009: The help topic is invalid.

Cause: The help topic is invalid.

Action: Correct the help topic.
Level: 1

Type: ERROR

Impact: Other

REP-80010: The trace file cannot be written to.

Cause: Fail to write to trace file.

Action: Check the trace file setup, file write permission, and whether the disk is full.
Level: 1

Type: ERROR

Impact: Other

REP-80011: Sign-on parameter {0} for {1} cannot be set.

Cause: The column is not a valid sign-on parameter of this plugin type.

Action: Use the Property Palette to set this column as a sign-on parameter of this plugin type.
Level: 1

Type: ERROR

Impact: Other

REP-80012: The link between two columns of mismatched datatypes is invalid.

Cause: The column link is formed between two columns of different data types.

Action: Ensure the link is formed between the columns whose datatypes are compatible.
Level: 1

Type: ERROR

Impact: Other

83 RTD-10001 to RTD-10532

RTD-10001: Could not serialize a client configuration request.

Cause: The RTD Smart Client attempted to request from the server the client configuration settings, for example the integration point request timeout. There was a failure in communication.

Action: This is not a crucial request, and intermittent failures may be tolerated. However, if they persist please verify the integrity of your network connection.
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10002: Session timeout set to {0} milliseconds.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10003: Can neither read nor create the specified configuration cache file, {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10004: Could not add existing client to endpoint, {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10005: Session timeout walker failed while looking for stale sessions

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10006: Failure getting server configuration for client

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10007: Failure setting up default responses

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10008: Could not find the client's application configuration file "{0}".

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10009: Failure setting up client dispatcher's default responses from file, "{0}"

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10010: Error releasing file lock.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10011: Client configuration request failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10012: Could not serialize an Integration Point request.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10013: Asynchronous invoke not attempted because previous request is still running. Integration Point: {0}, Inline Service: {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10014: Asynchronous invoke timed out for Integration Point "{0}" in Inline Service "{1}"

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10015: Asynchronous invoke failed for Integration Point "{0}" in Inline Service "{1}" Cause: {2}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10016: Asynchronous invoke failed for Integration Point "{0}" in Inline Service "{1}"

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10017: Request failed for Integration Point "{0}" in Inline Service "{1}". Error detail: {2}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10018: Request failed for Integration Point "{0}" in Inline Service "{1}". This Integration Point defines no default response. Error detail: {2}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10019: Request failed for Integration Point "{0}" in Inline Service "{1}" -- will use default response. Error detail: {2}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10020: Client summary exception: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10021: Failed to serialize default response for Integration Point "{0}".

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10022: Failed to serialize client configuration.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10023: Could not serialize {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10024: Error while trying to deserialize from bytes: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10025: Invalid UTF-8 data

Cause: The contents of the server's response do not appear to be decodeable according to UTF-8.

Action: Verify the response manually or contact Oracle support.
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10026: Compiling {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10027: Error initializing Velocity code generator.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10028: Error loading Inline Services. {0} ####

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10029: Failed to load Inline Service "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10030: Failed to load Inline Service. Don't have the Inline Service name.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10031: Upgraded and loaded Inline Service {0}:{1} in deployment state {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10032: Loaded Inline Service {0}:{1} in deployment state {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10033: The InlineService Poller did not stop within 30 seconds.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10034: The InlineService Poller was interrupted while stopping.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10035: Error loading Inline Service {0} in deployment state {1}. Will mark it as invalid in the database.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10036: Found the application parameter {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10037: Setting this Inline Service to parent-first classloading

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10038: Setting this Inline Service to parent-last classloading

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10039: Apploader for {0} finalized

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10040: Error encountered when upgrading this file {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10041: Failed to deserialize Inline Service "{0}"

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10042: Cannot get Inline Service "{0}" from the database. Will mark it invalid.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10043: Error reading Inline Service with ID {0} from database.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10044: Error saving Inline Service "{0}" -- could not serialize.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10045: Error accessing the local file-resident copy of Inline Service "{0}".

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10046: Error reading latest version of Inline Service "{0}" from database. Will use the version on file system

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10047: External rule cache was cleared. Approximately {0} bytes of memory was freed.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10048: {0} rules that were last accessed more than {1} hours ago were removed.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10049: Approximately {0} bytes of cache memory can now be garbage collected.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10050: Rule did not compile: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10051: missing or malformed rule identifier: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10052: Returned default true for cached invalid rule (did not compile): {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10053: Returned default true for rule with missing or malformed rule identifier: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10054: Returned default false for cached invalid rule (did not compile):

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10055: Returned default false for rule with missing or malformed rule identifier:

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10056: Execution of rule caused an evaluation exception: {1} {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10057: Did not stop Inline Service {0}:{1} because {2} sessions are still active and no progress was observed in closing them over the past {3} seconds.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10058: Stopping Inline Service {0}:{1}, {2} sessions remain.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10059: Stopped Inline Service {0}:{1} in deployment state {2}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10060: Response for an asynchronous request to advisor "{0}" will not be sent

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10061: Error delivering response message: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10062: Error in session learn.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10063: Error in Application Session Cleanup.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10064: Error removing session from session table

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10065: Error removing session from Inline Service.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10066: Could not close endpoint data, {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10067: Could not remove closed endpoint data.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10068: Error escaping the trace for this request

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10069: StringCatalog.getString() was called with an invalid ID, {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10070: Decision Service Forwarding Channel in instance, {0}, using address {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10071: Cannot load Inline Service with ID {0}. No Decision Service is present.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10072: Cannot load Inline Service with ID {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10073: Failed to invoke maintenance operation for Inline Service, {0}, because this RTD instance has no Inline Services loaded.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10074: Could not find the maintenance operation named {3} for app {0} in deployment state {1} at RTD instance {2}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10075: Failed to invoke maintenance operation on RTD instance {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10076: Failed to delegate application invoke to Inline Service, {0}, because no Inline Services are loaded

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10077: Failed to delegate application invoke because Inline Service, {0}, is not available.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10078: Failed to delegate application invoke.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10079: Dump Study returned {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10080: Could not load Inline Service in RTD instance {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10081: Exception while trying to retrieve configuration {0} from database.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10082: Uncaught exception while registering this instance in the cluster

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10083: Error enumerating local InetAddresses

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10085: The SDClusterViewChangeListener, {0}, threw an exception in hostJoined({1}).

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10086: Error stopping SDCluster

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10087: RTD Instance {0} saw {1} leave the cluster.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10088: The SDClusterViewChangeListener, {0}, threw an exception in hostLeft({1}).

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10089: This RTD instance, {0}, is now the CLUSTER COORDINATOR

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10090: This RTD instance, {0}, is now NOT THE CLUSTER COORDINATOR

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10091: Learning Service ready in RTD instance, {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10092: Batch Manager ready in RTD instance, {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10093: Decision Service ready.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10094: Batch Agent ready.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10095: Decision Service stopped.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10096: Batch Agent stopped.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10097: Learning Service stopped in RTD instance, {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10098: Batch Manager stopped in RTD instance, {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10099: Failed to close all lingering Decision Center sessions.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10100: Attribute "{0}" will not be aggregated since "{1}" is aggregated already. Only one partitioning attribute can be aggregated

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10101: Error initializing Batch Agent

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10102: Unexpected exception in BatchAgentServlet.destroy

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10103: BatchGroup, {0}, could not stop batch job, {1}, with ID, {2}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10104: Could not pause batch job, {0}, with ID, {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10105: Could not resume batch job, {0}, with ID, {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10106: Agent {0} has left the cluster, so reassigning its job, {1}, which never started

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10107: Could not wrap BatchManager in a StandardMBean implementing {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10108: Could not register BatchManager as an MBean with ObjectName='{0}' and interface={1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10109: Could not unregister MBean named {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10110: No batch agent is available to run BatchJob, {0}. agents={1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10111: StateChangedListener, {0}, threw exception. batchID={1}, oldState={2}, newState={3}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10113: BatchManager.runWaitingStartBatchProxie threw an exception running StartBatchProxy.run

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10114: BatchManager.registerAgent: agentID={1}, rtdInstance={0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10115: BatchManager.registerBatch: agentID={0}, batchName={1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10116: Could not pause batch job, {0}, with ID={1}. Batch Agent instance={2} not running

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10117: Could not pause batch job, {0}, with ID={1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10118: Could not resume batch job, {0}, with ID={1} because its server is not reachable

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10119: Could not resume batch job, {0}, with ID={1}. Batch Agent instance={2} not running

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10120: Could not resume batch job, {0}, with ID={1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10121: Could not start batch job, {0}, with ID={1}, parameters={2}. Batch Agent instance={3} not running

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10122: Could not start batch job, {0}, with ID={1}, parameters={2}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10123: Could not stop batch job, {0}, with ID={1}. Batch Agent instance={2} not running

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10124: Could not stop batch job, {0}, with ID={1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10125: Could not drop batches for application={0}, deploymentState={1}. Batch Agent instance={2} not running

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10126: Could not drop batches for application={0}, deploymentState={1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10127: Unexpected exception in BatchManagerServer.destroy

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10128: Could not start batch job, {0}, with batch ID, {1}, on agent, {2}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10129: The inline service has null deployment state.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10130: The InlineServiceManagerMBean could not stop its new-service poller within 30 seconds

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10131: The InlineServiceManagerMBean was interrupted while stopping its new-service poller.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10132: Error while stopping Inline Service "{0}".

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10133: Error while getting Inline Service "{0}".

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10134: DeleteChoiceHistory failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10135: MakeLoadable failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10136: DeleteAllOperationalData failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10137: DeleteStudy failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10138: Change Inline Service logging priority to {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10139: OracleRTD logging priority changed to {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10140: Unable to refresh Inline Service MBeans from database

Cause: An Exception or Error was trapped while reloading the Inline Services from the database and updating their MBeans.

Action: Verify connectivity to the SDDS. In a development environment you may choose to delete all records from SDApps.
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10141: The SDKernel could not stop its new-service poller within 30 seconds

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10142: The SDKernel was interrupted while stopping its new-service poller.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10143: Error unwrapping Inline Service {0} in deployment state {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10144: Could not wrap BatchAgentKernelImpl in a StandardMBean implementing {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10145: Could not register BatchAgent as an MBean with ObjectName='{0}' and interface={1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10146: Could not unregister MBean named {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10147: Agent({0} Error calling BatchManager.registerBatch. Batch Manager not running. batchName={1}, parmDesc={2}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10148: Agent({0} Error calling BatchManager.registerBatch. batchName={1}, parmDesc={2}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10149: Agent({0} Error calling BatchManager.unregisterBatch. Batch Manager not running. batchName={1}, parmDesc={2}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10150: Agent({0} Error calling BatchManager.unregisterBatch. batchName={1}, parmDesc={2}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10151: Error calling BatchManager.updateStatus. Batch Manager not running. batchName={0}, batchID={1}, state={2}, rows={3}, errors={4}, inputRowKey={5}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10152: Error calling BatchManager.updateStatus. batchName={0}, batchID={1}, state={2}, rows={3}, errors={4}, inputRowKey={5}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10153: BatchAgent.invoke terminated. Application={0}, deploymentState={1} undeployed.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10154: BatchAgent.startBatchForBatchManager: Unknown batch, {0}, agent={1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10155: BatchAgent.startBatchForBatchManager: ClassNotFound, {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10156: BatchAgent.startBatchForBatchManager: Could not create instance of {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10157: Batch Agent sees new Batch Manager connection.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10158: Call to BatchManager.registerAgent failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10159: BatchJob, {0}, for BatchName={1}, failed to initialize

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10160: BatchJob, {0}, caught exception from job.cleanup. BatchName={1}, rowNum={2}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10161: Error closing LearningRecordWriter: batchName={0}, batchID={1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10162: Restart BatchJob, {0}, fetch rows: Prematurely returned last row while iterating through previously fetched rows. BatchName={1}, rowNumber={2}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10163: BatchJob, {0}, threw an exception from getInputRow. BatchName={1}, rowNum={2}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10164: BatchJob, {0}, threw an exception from Inline Service session init snippet. BatchName={1}, rowNum={2}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10165: BatchJob, {0}, return Fatal from executeRow. BatchName={1}, rowNum={2}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10166: BatchJob, {0}, threw an exception from executeRow. BatchName={1}, rowNum={2}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10167: BatchJob, {0}, threw an exception from Inline Service session cleanUp snippet. BatchName={1}, rowNum={2}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10168: BatchJob, {0}, detected an uncaught exception. BatchName={1}, rowNum={2}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10169: BatchJob, {0}, threw an exception from flushOutputs. BatchName={1}, rowNum={2}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10170: Could not invalidate HTTP session

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10171: Response stream is already closed. Cannot send any more data

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10172: Could not successfully stop Decision Service.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10173: Could not successfully stop Learning Service.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10174: Could not successfully stop Batch Manager.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10175: Could not successfully stop Batch Agent.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10176: RTD Kernel's thread pool did not stop within {0} seconds.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10177: RTD Kernel's thread pool could not be shutdown.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10178: Delayed job failed to execute

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10179: Invoke failed: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10180: Invoke failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10181: Could not acquire run lock for stuck session({0}) to remove from session table

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10182: SessionIdleTimeoutMilliSec set to {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10183: Integration Point request timeout set to {0} milliseconds.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10184: Integration Point single-threaded response time set to {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10185: A Decision Service request was received from untrusted host, {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10186: Oracle RTD {0} build {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10187: Changed the operational data cleanup period to {0} hours

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10188: Operational data cleaner started

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10189: RTD's DBCleaner did not stop within {0} seconds.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10190: RTD's DBCleaner stop operation was interrupted.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10191: Operational data cleaner stopped

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10192: Execution of database cleanup procedure {0} failed during shutdown.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10193: Error while executing database cleanup procedure {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10194: Learning Server blockingModelBuild() called

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10195: A learning record with the time stamp in the past is ignored by model "{0}". {1} < {2} - {3}ms

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10196: Archive model "{0}.{1}" saved to database in {2} seconds. Model size: {3} KB, size before compression: {4} KB.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10197: Learning model "{0}.{1}" saved to database in {2} seconds. Model size: {3} KB, size before compression: {4} KB.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10198: A new time window has been forced for model {0} of study {1} beginning from {2}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10199: Data collected by model {0} of study {1} has been deleted.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10200: Data collected for values of attribute {0} between {1} and {2} has been deleted from model {3} of study {4}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10201: "{0}" is not a valid value for date/time model attribute "{1}".

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10202: "{0}" is not a valid value for numeric model attribute "{1}".

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10203: Unexpected exception in LSServer.destroy

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10204: Failed to save study "{0}".

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10205: The study {0} has been deleted

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10206: Unknown action name {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10207: Model snapshot with minimum absolute correlation value {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10208: Model snapshot with number of bins {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10209: Saving model snapshot of study {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10210: Completed snapshot of study {0}. {1} rows inserted. {2} warnings.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10211: Negative count_total {0}. Clamping to 0.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10212: Model Quality is too high: {0}. Clamping to 1.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10213: Negative count_positive {0}. Clamping to 0.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10214: count_positive {0} ought not be higher than count_total {1}. Clamping to count_total.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10215: {0} had unexpected negative value {1}. Clamping to 0.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10216: {0} was NaN. Resetting to 0.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10217: Predictiveness cannot be negative ({0}). Clamping to 0.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10218: Predictiveness cannot be greater than 1 ({0}). Clamping to 1.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10219: Correlation cannot be less than -1 ({0}). Clamping to -1.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10220: Correlation cannot be greater than 1 ({0}). Clamping to 1.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10221: count_input cannot be negative ({0}). Clamping to 0.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10222: count_output_input cannot be negative ({0}). Clamping to 0.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10223: count_output_input {0} should not be greater than count_input {1}. Increasing count_input

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10224: x cannot be negative ({0}). Clamping to 0.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10225: y cannot be negative ({0}). Clamping to 0.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10226: Saving model snapshot to {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10227: This row could not be processed: {0}. The original query was: {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10228: Failed to read data version of prediction model "{0}" of study "{1}".

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10229: Data collected by all models of study {0} has been deleted.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10230: Processing of {0} learning records in range {1}:{2} took {3} seconds ({4} records/second); IO time: {5} seconds.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10231: Stored procedure SDCommitStudy encountered data changed by an operation that occurred after the start of this serializable transaction. Will retry after set period of time.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10232: Failed to load study "{0}"

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10233: The maximum number of concurrent database requests for managing strict session affinity has changed to {0}{1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10234: Error removing timed out integration point requests.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10235: Error closing stale Decision Service session

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10236: Performance counters disabled

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10237: Could not locate performance counters log file, {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10238: Could not write header to performance counters log file, {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10239: Performance counters will be appended every {0} milliseconds to file {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10240: Could not write data to performance counters log file, {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10241: SessionIdleTimeoutMilliSec set to {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10242: Session timeout task failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10243: Decision Service session timed out but timer task could not acquire session's run lock. Session ID={0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10244: Error closing timed-out session

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10245: Error discarding session({0})

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10246: Failed to load prediction model "{0}"

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10247: "{0}" is not a valid value for numeric model attribute "{1}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10248: "{0}" is not a valid value for numeric model attribute "{1}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10249: Error initializing Decision Service

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10250: Unexpected exception in destroy method of servlet, SDHttpServerEndPoint

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10251: Error while trying to deserialize from input stream

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10252: Could not read permissions for Inline Service {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10253: Management Service ready.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10254: Management Service stopped.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10255: Unexpected exception in WorkbenchServlet.destroy

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10256: Parser for {0} created

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10257: Failure invoking the operation "{0}" for the service "{1}" at url "{2}"

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10258: Deploying soap services for servlet, {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10259: Soap services deployed successfully.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10260: Error deploying axis service: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10261: Error undeploying soap services for servlet, {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10262: Deployed the soap service file: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10263: Exception in Discovery Explorer: {0}

Cause: There was an Exception obtaining the Decision Center query results from the Learning Server.

Action: Refresh the report and attempt the query again.
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10264: Discovery Explorer error: {0}

Cause: An unrecoverable error was encountered while processing this Decision Center query.

Action: This server should be restarted. If it was an OutOfMemoryError then the heap size should be adjusted.
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10265: No value for {0} found in properties

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10266: DeployCustomUI failed for {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10267: Error reading DC session id from database for Inline Service "{0}", in Deployment State "{1}".

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10268: Deployed Inline Service {0}:{1} in deployment state {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10269: Invalid Dynamic Choice grouping size: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10271: AppRequiredReadOnlyCommand, {0}, is updating its metadata. This can happen by accident, by setting an SDO-contained object into another SDO (e.g. WSResult) without first cloning with EMF copy.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10272: Exception caught by SerializedScheduler when running job, {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10273: No TimerProviderAndJobRunner is available to the SerializedScheduler

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10274: Error output while running script: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10275: The script {0} ran longer than the configured timeout of {1} milliseconds and was destroyed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10276: Error loading build.number resource.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10277: Error loading version.properties resource.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10278: Failed to load {0} resource.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10279: The string "{0}" is not properly URL encoded.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10280: stacktrace.properties file not found in classpath.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10281: No value was found for the system property {0}. Using the default value {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10282: A value was found for the system property {0}. Using the value {1}, not using the default value {2}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10283: There was an error accessing the system property named {0}. No value could be found. Returning the default value {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10284: There was an error parsing the system property named {0}. The value found was "{1}" Returning the default value {2}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10285: The Database {0} BatchUpdater for {1} did not stop within {2} seconds after closing.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10286: The Database {0} BatchUpdater for {1} was interrupted while closing.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10287: The Database BatchUpdater did not stop within {0} seconds after closing. BU={1}, for {2}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10288: The Database BatchUpdater was interrupted when stopping. BU={0}, for {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10289: DatabaseProvider stopped.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10290: Exception during output of batched statements: database {0} operation for {1}. Batch size is {2}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10291: The BatchUpdater's AutoFlusher would not stop within {0} seconds.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10292: The BatchUpdater's AutoFlusher was interrupted while stopping.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10293: An exception was encountered while flushing buffers

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10294: Database {0} operation for table {1} executed successfully after {2,choice,1#one retry|1<{2} retries}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10295: Stored procedure {0} executed successfully after {1,choice,1#one retry|1<{1} retries}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10296: A leaked resultset was detected and closed for you

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10297: A leaked statement was detected and closed for you

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10298: A leaked connection was detected and closed for you

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10299: Error invoking method, {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10300: Cannot access Decision Center when no workbench soap session has been established

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10301: Cannot access Decision Center without opening an inline service

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10302: Cannot access Decision Center when no application has been opened

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10303: SeriesColorTag requires an rgb that is 6 characters. Instead, got {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10304: Could not obtain InitialContext

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10305: No J2EE context is available to look up data source names

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10306: Management Service exception

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10307: Management Service error

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10308: Could not open log file, {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10309: Could not write header to Load Generator statistics log file, {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10310: Could not write data to Load Generator statistics log, {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10311: Error closing SDClientInterface

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10312: The specified location of the Load Generator script is invalid: {0}. This could cause script elements using relative file references to fail at runtime.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10313: Load Generator's maximum think time, {0}, is less than its minimum think time, {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10314: Could not create client using client-config-url, "{0}"

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10315: Could not create client using location, "{0}". Example location is http://localhost:8080

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10316: Error loading file {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10317: Code generation failed for project {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10318: I/O error while generating Java files for "{0}".

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10319: Internal error while generating code for "{0}".

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10320: There was an error formatting source

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10321: Error reading file "{0}"

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10322: Error writing file "{0}"

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10323: Error handling resource changed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10324: Exception occured when visiting model objects as part of validation.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10325: Unexpected exception in SDValidator processing loop. Continuing with loop.

Cause: RTD Studio's background metadata validation job encountered an Exception.

Action: Please close your Inline Service project and re-open it. If this does not resolve the issue please restart Studio.
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10326: Could not find the static resource {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10327: Internal error

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10328: Saving of user name and password failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10329: Detected a CSRF attack. Additional info (ZIP compressed and Base64 encoded file):{0}

Cause: RTD CSRF defences are triggered.

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10330: Storage exception.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10331: "Could not obtain fusion mbean server"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10332: "Could not obtain oc4j mbean server"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10333: RTD schema version {0} was detected, expected version is {1}, RTD will not be started. Refer to the installation documentation for schema or server upgrade instructions.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10334: Error retrieving schema version from Database

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10335: Error loading SDSchemaVersion.properties

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10336: Exception was thrown while executing RTD job

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10337: Exception was thrown in topology changed listener

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10338: Request was forwarded to this RTD instance, but Decision Service is not running here

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10339: Could not execute incoming remote procedure call: operation={0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10340: Could not lookup my own end-point address for web service, {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10341: Unhandled exception in RpcReadyListener

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10342: Could not send asynchronous request to endpoint, {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10343: Could not execute post-initialization task, {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10344: Could not determine whether server is ready

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10345: System property, weblogic.Name, is undefined

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10346: Could not find one MBean with name, {0}. Found {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10347: RpcReceiver.getAddress() was called before RPC is ready

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10348: There was an error while unwrapping Inline Service, {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10349: Could not create a backup of Inline Service {0} in {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10350: Could not serialize remote procedure request, {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10351: Could not deserialize remote procedure request, {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10352: Could not execute incoming remote procedure call

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10353: Could not access credentials for the BI system user

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10354: Could not remove potentially stale Decision Service sessions from RTD instance, {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10355: Could not locate an active Batch Manager.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10356: Unable to read a study definition created by a newer version of the software

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10357: Study "{0}" committed to database in {1} seconds

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10358: Learning task did not stop in {0} seconds, while in state, {1}; proceeding with shutdown

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10359: Learning Server forceLearning failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10360: Learning Server blockingModelBuild failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10361: Delete study, {0}, failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10362: Study {0} deleted

Cause:

Action:
Level: 1

Type: INFO

Impact: Programmatic

RTD-10363: Create snapshot for study, {0}, failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10364: Snapshot for study {0} created

Cause:

Action:
Level: 1

Type: INFO

Impact: Programmatic

RTD-10365: Delete snapshot for study, {0}, failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10366: Snapshot for study {0} deleted

Cause:

Action:
Level: 1

Type: INFO

Impact: Programmatic

RTD-10367: Clear model {0} in study {0} failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10368: Model {0} in study {1} cleared

Cause:

Action:
Level: 1

Type: INFO

Impact: Programmatic

RTD-10500: Message to {0} was discarded

Cause: An RTD server attempted to send a message to another server it mistakenly believed to be in the cluster.

Action: If this message does not coincide with a planned server departure, verify that the sender and receiver are operational. Also verify that the SDTopology database table in the SDDS accurately reflects the makeup of the cluster as reported by Coherence.
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10501: Caller is not authorized to access the batch job named {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10502: Caller is not authorized to administer batch jobs named, {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10503: Unknown batch name, {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10504: A time window for model {0} of study {1} beginning from {2} has existed, cannot start a new time window with the same beginning.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10505: The choice history for inline service {0} has been cleared

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10506: Clear choice history for inline service {0} failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10507: The statistics for inline service {0} has been cleared

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10508: Clear statistics for inline service {0} failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10509: The study for inline service {0} has been cleared

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10510: Clear study for inline service {0} failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10511: All operational data for {0} has been cleared

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10512: Clear all operational data for inline service {0} failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10513: Inline service {0} has been unlocked

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10514: Failed to unlock inline service {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10515: Inline service {0} has been deleted

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10516: Failed to delete inline service {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10517: The model {0} for inline service {1} has been cleared

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10518: Clear model {0} for inline service {1} failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10519: Unknown batch ID, {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10520: Batch Agent is not reachable: AgentID={0}, rtdInstance={1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10521: Learning Server is not active on this host

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10522: Learning Server is not active on this host

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10523: Recursion was detected in the definition of this entity. The InlineService cannot be loaded.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

RTD-10524: Likelihood value = {0} but it should be a probability between 0 and 1 inclusive.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10525: Invalid security header in client request.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10526: Inline Service \"{0}\" is not found in server.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10527: My RTD RPC endpoint address is {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RTD-10528: RTD RPC was not ready within {0} seconds

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10529: Unable to schedule next learning dispatcher task:

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10530: Save study, {0}, failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

RTD-10531: Study {0} saved

Cause:

Action:
Level: 1

Type: INFO

Impact: Programmatic

RTD-10532: Data collected by all models of study {0} has been saved.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

84 RUL-00000 to RUL-09043

RUL-00000: An internal error occurred during type checking ''{5}''. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: An internal error occurred during type checking.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-00001: An invalid assignment target was encountered. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: An invalid target of an assignment expression was encountered.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00002: The operator ''+'' accepts only numeric and String operands. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: One of the operands of an addition expression was an incorrect type.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00003: The operator ''{5}'' accepts only boolean and fact set operands. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: One of the operands of a boolean expression was an incorrect type.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00004: The operator ''{5}'' accepts only numeric operands. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: One of the operands of a numeric expression was an incorrect type.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00005: The operator ''{5}'' accepts only integer operands. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: An operator that only accepts integer operands had an operand that was not an integer.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00006: The operator ''{5}'' accepts only String, numeric, boolean, or Object operands. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: A comparison expression contained an operand of an incorrect type.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00007: The operator ''{5}'' accepts only numeric, String, or Comparable operands. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: A comparison expression contained an operand of an incorrect type.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00008: The operator ''exists'' accepts only fact set operands. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: The operand of an exists operator was an incorrect type.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00009: The operator ''instanceof'' accepts only Object operands. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: The operand of an instanceof operator was an incorrect type.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00010: Unable to convert from type ''{5}'' to type ''{6}''. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: An RL expression contained an implicit conversion from one type to another and that implicit conversion was not possible.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00011: Incorrect number of arguments encountered in function or method invocation. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: An RL function or a Java method invocation was coded with an incorrect number of arguments.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00012: Incorrect argument type encountered in function or method invocation. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: An argument in an RL function or a Java method invocation was an incorrect type.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00013: Nested arrays are not supported. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: RL code was written to use nested arrays.

Action: RL does not support nested arrays. Rewrite the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00014: This rule has only {5,number,integer} logical support expressions. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: The logical rule property was assigned a value that was greater than the number of supporting expressions in the rule condition.

Action: Correct the value assigned to the logical property.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00015: Cannot use ''{5}'' in a rule condition. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: An RL construct that is not valid in a rule condition was encountered in a rule condition.

Action: Correct the offending rule condition.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00016: Cannot use ''{5}'' outside a rule condition. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: An RL construct that is only valid in a rule condition was encountered outside of a rule condition.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00017: A fact pattern cannot contain an expression. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: A fact pattern contained an expression.

Action: Correct the offending RL code by moving the expression to a test following the fact pattern.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00018: A fact pattern cannot contain the ''new'' operator. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: A fact pattern contained a new operator.

Action: Correct the offending RL code by removing the new operator.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00019: A fact pattern cannot contain a function or method call. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: A fact pattern contained a function or method invocation.

Action: Correct the offending RL code by moving the invocation to a test following the pattern.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00020: The symbol ''{5}'' is undefined. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: An undefined RL program element was encountered.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00021: The symbol ''{5}'' is not public. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: An RL program element that was not public was referenced and therefore was not accessible.

Action: If the program element is a Java class, ensure that the class has been imported or is referenced with its fully qualified name, and that it is present in the class path. If the program element is a Java method, a Java field, an RL function, or an RL function variable, ensure that it has been declared to be public.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00022: The fact class for ''{5}'' should be declared earlier in rule session. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: A fact class for the offending class needed to be declared earlier in the rule session. Typically a super class was encountered in a fact context (fact class statement, rule condition, assert, retract, modify) after one or more of its subclasses has appeared in a fact context.

Action: Add or move a fact class statement for the class to an earlier position in the RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00023: The fact class should be declared earlier. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: A fact class for the offending class needed to be declared earlier in the rule session. Typically a super class was encountered in a fact context (fact class statement, rule condition, assert, retract, modify) after one or more of its subclasses has appeared in a fact context.

Action: Add or move a fact class statement for the class to an earlier position in the RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00024: The fact class ''{5}'' cannot extend both ''{6}'' and ''{7}''. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: Fact class multiple inheritance was detected.

Action: Correct the offending RL code to restrict to single inheritance.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00025: Fact class multiple inheritance is not supported. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: Fact class multiple inheritance was detected.

Action: Correct the offending RL code to restrict to single inheritance.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00026: An exception was thrown in an invoked Java method. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: A Java method invoked from RL threw an exception.

Action: Investigate the root cause of the exception thrown by the Java method. It is available as the cause of the exception thrown with this message.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00027: The symbol ''{5}'' is defined more than once. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: An RL program element was defined more than once.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00030: The class ''{5}'' has no member named ''{6}''. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: An attempt to access a nonexistent member of a class was detected.

Action: Correct the offending reference.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00031: The class ''{5}'' has no static member named ''{6}''. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: An attempt to access a nonexistent static member of a class was detected.

Action: Correct the offending reference.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00032: The class ''{5}'' has no public member named ''{6}''. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: An attempt was made to access a member of a class that is not public.

Action: Remove the offending reference or make the member public.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00033: A fully qualified package or class name is required. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: An import statement did not contain a fully qualified class name.

Action: Correct the import statement.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00034: An invalid action was encountered. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: An invalid RL action was encountered.

Action: Correct the RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00040: Encountered ''{5}'' when expecting {6}. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: An unexpected program element was encountered.

Action: Correct the RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00041: Encountered ''{5}'' when expecting one of: {6} {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: An unexpected program element was encountered.

Action: Correct the RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00042: The XML identifier ''{5}'' is invalid. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: An invalid XML identifier was encountered.

Action: Correct the RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00043: Cannot use both ''property'' and ''hide property''. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: A fact class statement contained both property and hide property clauses. Only of one of them may be specified.

Action: Correct the RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00044: The class ''{6}'' cannot extend final class ''{5}''. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: An RL class was declared to extend a second RL class which was declared to be final.

Action: Correct the RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00045: Cannot hide exposed property ''{5}''. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: An attempt was made to hide a property of class when that property has already been exposed. For example, an attempt to hide a property of a super class.

Action: Correct the RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00046: Cannot expose hidden property ''{5}''. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: An attempt was made to expose a property of class when that property has already been hidden. For example, an attempt to expose a property of a super class which has a fact class statement that hid that property.

Action: Correct the RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00050: An error was encountered in a property getter when asserting fact. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: An IllegalArgumentException was thrown when getting property. This exception is available as the root cause exception in the exception created with this message.

Action: Inspect root cause exception.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00051: An error was encountered when defining property ''{5}''. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: An RLIllegalArgumentException was thrown when defining a property. This exception is available as the root cause exception in the exception created with this message.

Action: Inspect root cause exception.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00052: A null object cannot be dereferenced. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: An attempt was made to dereference a null object reference.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00054: The ruleset stack is empty. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: An attempt was made to get a ruleset from the top of the ruleset stack when the stack was empty.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00055: The ruleset ''{5}'' is already on the ruleset stack. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: An attempt was made to push a ruleset onto the top of the ruleset stack when the same ruleset was already on the top of the stack.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00056: The ruleset ''{5}'' is undefined. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: A reference was made to a ruleset that was undefined.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00057: The package ''{5}'' is undefined. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: A reference was made to an undefined package.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00058: Cannot convert xpath test type ''{5}'' to ''{6}''. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: An error in an XPATH test was detected.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00059: The xpath test operator ''{5}'' is not supported. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: An unsupported XPATH operator was encountered.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00060: The xpath test constant ''{5}'' is not supported. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: An unsupported XPATH literal was encountered.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00061: The xpath ''/'' is not supported. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: XPATH '/' was encountered but is not supported by RL.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00062: An xpath cannot begin with ''{5}''. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: The XPATH cannot start with the offending text.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00063: Invalid xpath syntax ''{5}'' was encountered. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: An XPATH syntax error was encountered.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00064: The property ''{5}'' is undefined. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: An undefined property was encountered in an XPATH.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00065: The property ''{5}'' must be public in a class that supports xpath. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: A nonpublic property was encountered in an XPATH.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00067: An XML identifier is missing. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: An XML identifier was expected.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00068: Encountered an unexpected ''@'' in an XML name. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: An unexpected '@' character was encountered in an XML name.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00069: Encountered an unexpected ''/'' in an XML name. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: An unexpected '/' character was encountered in an XML name.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00070: The array index ''{5,number,integer}'' is out of bounds. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: An attempt was made to index into an array with an index that was outside the bounds of the array.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00071: An array size cannot be negative. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: An attempt was made to create an array with a negative size.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00072: Encountered an array element type mismatch. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: An attempt was made to store the wrong type of object in an array.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00073: Cannot store an object of type ''{5}'' in array of type ''{6}''. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: An attempt was made to store the wrong type of object in an array.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00074: The RL object is not an array. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: An attempt was made to use an object as an array and the object was not an array.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00075: A subscript must be applied to an array. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: An array reference was missing an index.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00076: A subscript must be an integer type. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: A nonintegral array index was encountered.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00077: An invalid value of ''{5}'' is assigned to the rule property 'logical'. The value must be greater than 0. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: A non-positive value was assigned to the logical rule property.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00080: The class ''{5}'' does not support cloning. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: An attempt was made to clone an object whose class does not support cloning.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00081: Cannot cast to class ''{5}''. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: An attempt was made to cast an object to a class to which it cannot be cast.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00082: An invalid argument ''{5}'' was passed to ''{6}''. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: An invalid argument was passed to an RL function or Java method.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00083: The RL class ''{5}'' cannot extend a Java class. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: An RL class was defined to extend a Java class which is not supported.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00084: Cannot find a constructor for class ''{5}''. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: An applicable constructor for the class could not be found.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00085: Cannot include ''{5}'' because {6}. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: An error occurred in an include statement.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00086: The function was missing a return statement. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: A function was defined to return a value but it did not contain a return statement.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00087: A ''return'' must only be used in a function or a rule action. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: A return statement was encountered in an invalid location.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00088: A ''catch'' or ''finally'' must be specified. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: A try statement did not have at least one of a catch or finally clause.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00089: error: {5} {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: A divide by 0 was detected.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00090: An internal error was encountered: {5} {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: An internal rules engine error was encountered.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-00091: The aggregate {5} was not an implementation of {6}. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: The aggregate did not implement the required interface.

Action: Correct the aggregate implementation or change the RL code to reference a correct aggregate function.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00092: The argument of aggregate function in the fact path is wrong. The argument should be association name or property of an association. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: The argument of aggregate function in the fact path was wrong.

Action: The argument should be association name or property of an association.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00093: An invalid boolean expression encountered in fact path. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: An invalid boolean expression was encountered in a fact path.

Action: Correct the offending RL code.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00094: The association ''{6}'' defined in ''{5}'' is reverse association, but it is corresponding to a forward reference. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: The association in a Reverse Association was not a forward reference.

Action: Change the association to forward reference.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00095: Invocation of the executeRuleset method on a RuleSession obtained from a pool using peer RuleSessions is not allowed.

Cause: This RuleSession was obtained from a pool and the executeRuleset method was invoked. This is not allowed when peer RuleSessions are in use.

Action: Eliminate the executeRuleset method invocation or do not use a RuleSession pool.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00096: Rule ''{5}'' defined in rule group ''{6}'' must contain exactly {7} patterns. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: The specified rule was in a rule group with the mutex property set to true and the rule had an incorrect number of patterns (fact clauses).

Action: Change the rule to have the correct number of patterns.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00097: Rule ''{5}'' defined in rule group ''{6}'' has a fact clause of type ''{7}'' when type ''{8}'' is required. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: The specified rule was in a rule group with the mutex property set to true. All rules in a mutex group must have the same fact clauses with the same fact types in the same order. This rule contained a fact clause that did not match the expected fact type.

Action: Change the rule to specify the correct fact types in the same order as other rules in the rule group.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00098: The loop property of ''{5}'' did not match the loop property of the group it was a member of. All members of a rule group must have the same loop property value. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: A member of a rule group had the loop property set to a value that does not match the loop property value for the group. All members of a rule group must have the same loop property value.

Action: Change loop property value in either the named group member or the named group to resolve the conflict.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00099: The aggregate contained more than one pattern. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: The aggregate contained more than one pattern.

Action: Only one pattern is allowed in an aggregate. Change the RL code to contain a single pattern.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00100: The aggregate pattern contained an expression that could not be folded into the pattern. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: The aggregate pattern contained an expression that could not be folded into the pattern.

Action: All expressions following the pattern in the aggregate must be folded into the pattern. Some complex tests may not be foldable. Rewrite the expression to simplify it so it may be folded into the pattern.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00101: The RL function run, step or runUntilHalt was invoked from a rule action. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: One of the RL functions, run, step, or runUntilHalt was invoked from a rule action.

Action: Edit the rule action to remove the invocation of the run, step, or runUntilHalt function.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-00102: The RL function getFactByType found more than one instance of the fact type, {5}. {0} {1,choice,0#|0<at line {1,number,integer}} {2,choice,0#|0< column {2,number,integer}} {1,choice,0#|0< } {3,choice,0#|0<in {4}}

Cause: The RL function getFactByType found more than one instance of the specified fact type.

Action: Modify rules to avoid creating multiple instances of the fact type.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01001: {0} is not a valid selection with respect to the domain. Ensure sure your selection is in the valid domain.

Cause: The value is not a valid selection with respect to the domain.

Action: Provide a valid selection with respect to the domain.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01002: Range constraint has been violated. {0} is not in the range of {1} and {2}. Ensure the value satisfies the range constraint

Cause: Range constraint has been violated. The value is not in the range.

Action: Ensure the value satisfies the range constraint
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01003: Unable to add jar file {0} into the data model. Ensure the jar file is in the correct location, is not corrupted, and that all dependent Java classes have been imported into the data model.

Cause: Unable to add jar file into the data model.

Action: Ensure the jar file is in the correct location, is not corrupted, and that all dependent Java classes have been imported into the data model.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01004: Unable to deserialize XML to data model. Ensure the XML element is well-formed and conforms to the data model schema.

Cause: Unable to deserialize XML to data model.

Action: Ensure the XML element is well-formed and conforms to the data model schema.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01005: Unable to serialize data model into XML. See the base exception for resolution.

Cause: Unable to serialize data model into XML.

Action: See the base exception for resolution.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01006: Missing the element/attribute {0} in the data model XML document. Ensure the required element is in the data model XML document.

Cause: Missing the element/attribute in the data model XML document.

Action: Ensure the required element is in the data model XML document.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01007: The referenced Fact Type {0} is not defined in the data model. Ensure the referenced Fact Type is defined in the data model.

Cause: The referenced Fact Type is not defined in the data model.

Action: Ensure the referenced Fact Type is defined in the data model.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01008: The pattern {0} is not a valid regular expression. Provide a valid pattern. Refer to java.util.regex.Pattern for more information.

Cause: The pattern is not a valid regular expression.

Action: Provide a valid pattern. Refer to java.util.regex.Pattern for more information.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01009: The input String {0} does not match the regular expression constraint pattern {1}. Ensure the input String conforms to the given pattern. Refer to java.util.regex.Pattern for more information.

Cause: The input String does not match the regular expression constraint pattern.

Action: Ensure the input String conforms to the given pattern. Refer to java.util.regex.Pattern for more information.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01010: Unable to add the new element into the data model. An element with the same name, {0}, is already in the data model. If you wish to replace this existing element, remove it from the data model and then add the new element.

Cause: Unable to add the new element into the data model. An element with the same name is already in the data model.

Action: If you wish to replace this existing element, remove it from the data model and then add the new element.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01011: Error while deserializing range constraint. The bounds {0} and {1} are not in the correct format. Ensure the bound values in XML document are in the correct double format, or contact Oracle Support Services.

Cause: Error while deserializing range constraint. The bounds are not in the correct format.

Action: Ensure the bound values in XML document are in the correct double format, or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01012: Unable to add JAXB class {0} into the data model. Ensure the class is in class path.

Cause: Unable to add JAXB class into the data model.

Action: Ensure the class is in class path.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01013: Unable to add Java class {0} to the data model. Ensure the class and its associated classes, including parent classes and attribute type classes, are on the current class path.

Cause: Unable to add Java class to the data model.

Action: Ensure the class and its associated classes, including parent classes and attribute type classes, are on the current class path.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01014: Unable to add XML schema path {0} into data model. See the base exception for resolution.

Cause: Unable to add XML schema path into data model.

Action: See the base exception for resolution.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01015: The user path {0} is not a directory or zip file. Ensure the user path is either a directory, zip file, or jar file.

Cause: The user path is not a directory or zip file.

Action: Ensure the user path is either a directory, zip file, or jar file.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01016: Cannot load Java class {0}. Ensure the class and all its dependent classes are either in the class path, or user specified path.

Cause: Cannot load Java class.

Action: Ensure the class and all its dependent classes are either in the class path, or user specified path.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01017: Cannot load Java class. The class name must be valid.

Cause: Cannot load Java class.

Action: Provide a valid class name.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01018: Cannot load Java class {0}. The class must be inside a package.

Cause: Cannot load Java class.

Action: The class must be inside a package.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01019: Cannot reimport Java class {0}. Ensure the class and its associated classes, including parent classes and attribute type classes, are on the current class path. See base exception for detail.

Cause: Cannot reimport Java class.

Action: Ensure the class and its associated classes, including parent classes and attribute type classes, are on the current class path. See base exception for detail.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01020: Can not load Java class {0}. The class name contains RL reserved word {1}.

Cause: Cannot load Java class. The class name contains RL reserved word.

Action: Change the name of the Java class.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01021: Java Class {0} has a field {1} that is a RL reserved word.

Cause: Java Class has a field that is a RL reserved word.

Action: Change the name of the field.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01022: Java Class {0} has a property {1} that is a RL reserved word.

Cause: Java Class has a property that is a RL reserved word.

Action: Change the name of the property.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01023: Java Class {0} has a method {1} that is a RL reserved word.

Cause: Java Class has a method that is a RL reserved word.

Action: Change the name of the method.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01024: Jaxb Output directory is null or an empty string.

Cause: Jaxb Output directory is null or an empty string.

Action: Provide a valid output directory.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01025: Jaxb Output directory {0} is not a valid directory.

Cause: Jaxb Output directory is not a valid directory.

Action: Provide a valid output directory.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01026: Jaxb Output directory {0} is not writable.

Cause: Jaxb Output directory is not writable.

Action: Provide a writable output directory.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01027: Package name is not a valid Java Identifier.

Cause: Package name is not a valid Java Identifier.

Action: Provide a valid Java Identifier for the package name.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01028: XML Schema name is null or an empty string.

Cause: XML Schema name is null or an empty string.

Action: Provide a valie XML Schema name.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01029: XML Schema {0} does not exist.

Cause: XML Schema does not exist.

Action: Provide an XML Schema that exists.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01030: Time out while importing XML Schema {0}. If you need to access the schema through a proxy server, properly set system properties for proxy server. Refer to document about importing an XML schema.

Cause: Time out while importing XML Schema.

Action: If you need to access the schema through a proxy server, properly set system properties for proxy server. Refer to document about importing an XML schema.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01031: There is a circular dependency among variables.

Cause: There is a circular dependency among variables.

Action: Resolve the circular dependency.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01032: There is a circular dependency among functions.

Cause: There is a circular dependency among functions.

Action: Resolve the circular dependency.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01033: There is a circular dependency among RL Facts.

Cause: There are circular dependency among RL Facts.

Action: Resolve the circular dependency.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01034: There is a circular dependency among variables and functions.

Cause: There are circular dependency among variables and functions.

Action: Resolve the circular dependency.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01035: The value to be validated is null.

Cause: The value to be validated is null.

Action: Provide a valid value.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01101: Unable to serialize the ruleset into XML. See base exception for resolution.

Cause: Unable to serialize the ruleset into XML.

Action: See base exception for resolution.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01102: Unable to deserialize the XML document into a ruleset. See the base exception for resolution.

Cause: Unable to deserialize the XML document into a ruleset.

Action: See the base exception for resolution.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01103: Missing the element/attribute {0} in ruleset XML document. Ensure the required element is in the ruleset XML document.

Cause: Missing an element/attribute in ruleset XML document.

Action: Ensure the required element is in the ruleset XML document.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01104: Unable to load dictionary document(s) from the repository due to version incompatibility. The current code version is \\"{0}\\", document version is \\"{1}\\".

Cause: Unable to load dictionary document(s) from the repository due to version incompatibility. The current code version is different than the document version.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01113: Variable {0} is not in scope.

Cause: Variable is not in scope.

Action: Specify a variable that is in scope.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01114: Interface {0} not found.

Cause: Interface not found.

Action: Specify a valid interface.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01115: Variable {0} is no longer defined in this scope.

Cause: Variable is no longer defined in this scope.

Action: Specify an variable that is in scope.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01116: Fact Type {0} is no longer defined.

Cause: Fact Type is no longer defined.

Action: Remove references to Fact Type or define Fact Type.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01117: Fact Type {0} has no methods named {1}.

Cause: Fact Type has no methods with that name.

Action: Specify a different method.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01118: Method {0} with matching parameter list not found.

Cause: Method with matching parameter list not found.

Action: Specify a method that exists.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01119: Expression is already used in a different RuleElement.

Cause: Expression is already used in a different RuleElement.

Action: Use a new expression for this RuleElement.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01120: Function {0} is no longer defined.

Cause: Function is no longer defined.

Action: Define the function again or specify a different function.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01121: In Call function or method {0}, the number of arguments does not match parameter list.

Cause: In Call function or method, the number of arguments does not match parameter list.

Action: Provide a number of arguments that matches the parameter list.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01122: Function {0} requires argument {1}, but this is not in the call argument map.

Cause: Function requires an argument, but this is not in the call argument map.

Action: Recreate the call to the function.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01123: Condition must have a pattern expression.

Cause: Condition must have a pattern expression.

Action: Add a pattern to the condition.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01124: {0} is not a valid modifier.

Cause: The value is not a valid modifier.

Action: Provide a valid modifier.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01125: Variable {0} must have an initial value.

Cause: Variable must have an initial value.

Action: Provide an initial value.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01126: If statement must contain at least one test block.

Cause: "If" statement does contain at least one test block.

Action: Provide a test block for the statement.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01127: Else statement must be the last test block.

Cause: "Else" statement is not the last test block.

Action: Make the "else" statement the last test block.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01128: Missing object name.

Cause: Missing object name.

Action: Provide an object name.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01129: Fact Type {0} not found in data model.

Cause: Fact Type not found in data model.

Action: Add the Fact Type to the data model or select a different Fact Type.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01130: Fact Type {0} has no public constructors.

Cause: Fact Type has no public constructors.

Action: Provide a constructor to the Fact Type.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01131: Unable to locate public constructor for {0} with {1} args.

Cause: Unable to locate public constructor for Fact Type with args.

Action: Provide a constructor with that number of arguments or use a different constructor
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01132: RL fact constructors must have named parameters.

Cause: RL fact constructors must have named parameters.

Action: Recreate the Fact Type or refresh the element.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01133: {0} is not a valid operator.

Cause: The value is not a valid operator.

Action: Provide a valid operator.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01134: {0} is not valid for type {1}.

Cause: The value is not valid for the given type.

Action: Provide a valid value for this type.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01135: OperatorNode cannot be used in multiple expressions.

Cause: OperatorNode cannot be used in multiple expressions.

Action: Use the OperatorNode in only one expression.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01136: Duplicate pattern variable name.

Cause: More than one pattern contains the same variable name.

Action: Change the variable name on one of the patterns.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01137: Retract can only be called within the action block of a Rule.

Cause: Retract can only be called within the action block of a Rule.

Action: Remove this retract action from its current location.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01138: Return statement can only be defined in the action block of a rule or in a function.

Cause: Return statement can only be defined in the action block of a rule or in a function.

Action: Remove the return statement.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01139: Return statements in rule action blocks cannot return values.

Cause: Return statements in rule action blocks cannot return values.

Action: Remove the return value from the return.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01140: RL code generator missing/incorrect for {0}.

Cause: RL code generator missing/incorrect for element.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01141: RuleSet missing name.

Cause: RuleSet missing name.

Action: Provide a name for the RuleSet.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01142: {0} is a duplicate rule name within this rule set.

Cause: Two rule sets have the same name.

Action: Provide a different name for one of the rule sets.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01143: There is no rule named {0} in this rule set.

Cause: There is no rule with the given name in this rule set.

Action: Provide a different rule name.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01144: Move operation {0} is not valid.

Cause: Move operation is not valid.

Action: Do not attempt to use this move operation.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01201: The passed-in dictionary object is null when saving the dictionary into repository. Make sure the dictionary object was property created.

Cause: The passed-in dictionary object is null when saving the dictionary into repository.

Action: Make sure the dictionary object was property created.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01202: Base directory for the dictionary should be given.

Cause: Base directory for the dictionary should be given.

Action: Provide the base directory for the dictionary.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01203: Error locating repository root directory {0}. Ensure the repository path is valid and appropriate permission is granted.

Cause: Error locating repository root directory.

Action: Ensure the repository path is valid and appropriate permission is granted.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01204: Error writing XML document to {0}. Refer to base exception for resolution.

Cause: Error writing XML document.

Action: Refer to base exception for resolution.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01205: Error parsing XML document from {0}. Refer to base exception for resolution.

Cause: Error parsing XML document.

Action: Refer to base exception for resolution.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01206: The requested dictionary {0} is not in repository. Ensure the dictionary name is correct.

Cause: The requested dictionary is not in repository.

Action: Ensure the dictionary name is correct.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01207: Error loading dictionary {0}. Refer to the base exception.

Cause: Error loading dictionary.

Action: Refer to the base exception.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01208: Error saving dictionary {0}. Check write permission for the repository directory. Refer to the base exception.

Cause: Error saving dictionary.

Action: Check write permission for the repository directory. Refer to the base exception.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01209: Error removing dictionary {0}. Refer to the base exception.

Cause: Error removing dictionary.

Action: Refer to the base exception.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01210: While deserializing the rule set, the RL function {0} could not be found in the data model. Ensure the function has been defined in data model.

Cause: While deserializing the rule set, the RL function could not be found in the data model.

Action: Ensure the function has been defined in data model.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01211: While deserializing the rule set, the Java class {0} could not be found in the data model. Ensure the class has been defined in data model.

Cause: While deserializing the rule set, the Java class could not be found in the data model.

Action: Ensure the class has been defined in data model.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01212: While deserializing ruleset, the Java method {0} in class {1} could not be found in the data model. Ensure the method has been defined in data model.

Cause: While deserializing ruleset, the Java method in class could not be found in the data model.

Action: Ensure the method has been defined in data model.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01213: Error initializing the repository. Refer to the base exception.

Cause: Error initializing the repository.

Action: Refer to the base exception.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01214: There is a problem with repository connection. Make sure the repository has been initialized correctly.

Cause: There is a problem with repository connection.

Action: Make sure the repository has been initialized correctly.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01215: Error retrieving dictionary names. Refer to the base exception.

Cause: Error retrieving dictionary names.

Action: Refer to the base exception.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01216: Error saving dictionary {0}. Refer to the base exception.

Cause: Error saving dictionary.

Action: Refer to the base exception.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01217: Unable to remove dictionary {0}. The specified dictionary is not found in repository.

Cause: Unable to remove dictionary. The specified dictionary is not found in repository.

Action: Specify a dictionary that exists in the repository.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01218: Error closing the repository. Refer to the base exception.

Cause: Error closing the repository.

Action: Refer to the base exception.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01219: Dictionary {0} is not found in repository.

Cause: Dictionary is not found in repository.

Action: Provide the name of a dictionary in the repository.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01220: Unable to mark dictionary {0}. Refer to the base exception.

Cause: Unable to mark dictionary.

Action: Refer to the base exception.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01221: Unable to list versions for dictionary {0}. Refer to the base exception.

Cause: Unable to list versions for dictionary.

Action: Refer to the base exception.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01222: Unable to load dictionary {0}. Refer to the base exception.

Cause: Unable to load dictionary.

Action: Refer to the base exception.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01223: Unable to load dictionary {0} version {1}. Refer to the base exception.

Cause: Unable to load dictionary version.

Action: Refer to the base exception.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01224: Dictionary {0} version {1} is not found in repository.

Cause: Dictionary version is not found in repository.

Action: Select a version of the dictionary that exists.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01225: Error removing dictionary {0} version {1}. Refer to the base exception.

Cause: Error removing dictionary version.

Action: Refer to the base exception.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01226: The file path passed to function exportDictionary() is null.

Cause: The file path passed to function exportDictionary() is null.

Action: Provide a non-null file path.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01227: Unable to export dictionary {0}. Refer to the base exception.

Cause: Unable to export dictionary.

Action: Refer to the base exception.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01228: Unable to export dictionary {0} version {1}. Refer to the base exception.

Cause: Unable to export dictionary version.

Action: Refer to the base exception.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01229: The file path passed to function importDictionary() is null.

Cause: The file path passed to function importDictionary() is null.

Action: Provide a non-null file path.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01230: Unable to import the file {0}. Refer to the base exception.

Cause: Unable to import the file.

Action: Refer to the base exception.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01231: Version {0} exists in repository.

Cause: Version exists in repository.

Action: Provide a different version for the dictionary or remove it from the repository first.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01232: The dictionary to be saved does not have a name or the name is an empty string.

Cause: The dictionary to be saved does not have a name or the name is an empty string.

Action: Provide a valid name.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01233: The file path {0} is not a valid path leading to a file.

Cause: The file path is not a valid path leading to a file.

Action: Provide a valid path that leads to a file.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01234: A dictionary with name {0} and version name {1} already exists in repository. Note dictionary and version names are case insensitive.

Cause: A dictionary with the same name and verison already exists in repository.

Action: Provide a name and version that do not exist. Note dictionary and version names are case insensitive.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01235: The dictionary to be saved does not have a version name or the version name is an empty string.

Cause: The dictionary to be saved does not have a version name or the version name is an empty string.

Action: Provide a valid version name for the dictionary before saving.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01236: Unable to load the dictionary. It does not have a name or the name is an empty string.

Cause: Unable to load the dictionary. It does not have a name or the name is an empty string.

Action: Provide a valid name.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01237: Unable to load the dictionary. It does not have a version name or the version name is an empty string.

Cause: Unable to load the dictionary. It does not have a version name or the version name is an empty string.

Action: Provide a valid version name.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01238: Unable to remove the dictionary. The dictionary name is null or an empty string.

Cause: Unable to remove the dictionary. The dictionary name is null or an empty string.

Action: Provide a valid dictionary name.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01239: Unable to remove the dictionary. The dictionary version name is null or an empty string.

Cause: Unable to remove the dictionary. The dictionary version name is null or an empty string.

Action: Provide a valid dictionary version name.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01240: Unable to export the dictionary. The dictionary name is null or an empty string.

Cause: Unable to export the dictionary. The dictionary name is null or an empty string.

Action: Provide a valid dictionary name.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01241: Unable to export the dictionary. The dictionary version name is null or an empty string.

Cause: Unable to export the dictionary. The dictionary version name is null or an empty string.

Action: Provide a valid dictionary version name.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01242: Unable to mark the dictionary. The new version name is null or an empty string.

Cause: Unable to mark the dictionary. The new version name is null or an empty string.

Action: Provide a valid version name.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01243: Unable to mark the dictionary. The dictionary name is null or an empty string.

Cause: Unable to mark the dictionary. The dictionary name is null or an empty string.

Action: Provide a valid name.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01244: Unable to mark the dictionary. The current version name is null or an empty string.

Cause: Unable to mark the dictionary. The current version name is null or an empty string.

Action: Provide a valid version name.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01245: Unable to get version names for the dictionary. The dictionary name is null or an empty string.

Cause: Unable to get version names for the dictionary. The dictionary name is null or an empty string.

Action: Provide a valid name for the dictionary.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01246: Unable to get description for dictionary {0}.

Cause: Unable to get description for dictionary.

Action: XYZ
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01247: Unable to get description for dictionary {0} version {1}.

Cause: Unable to get description for dictionary version.

Action: XYZ
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01248: Unable to set description for dictionary {0}.

Cause: Unable to set description for dictionary.

Action: XYZ
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01249: Unable to set description for dictionary {0} version {1}.

Cause: Unable to set description for dictionary version.

Action: XYZ
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01250: While creating a rule repository instance, the parameter is null.

Cause: While creating a rule repository instance, the parameter is null.

Action: Provide a non-null parameter.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01251: The specified dictionary {0} version {1} does not exist in repository.

Cause: The specified dictionary version does not exist in repository.

Action: Provide a dictionary version that exists in the repository.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01252: Unable to load 10.1.3.0.0 dictionary {0} using 10.1.3SOA code base. The dictionary might need to be fixed manually.

Cause: Unable to load 10.1.3.0.0 dictionary using 10.1.3SOA code base.

Action: The dictionary might need to be fixed manually. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01253: Unable to load 10.1.3.0.0 dictionary {0} version {1} using 10.1.3SOA code base. The dictionary might need to be fixed manually.

Cause: Unable to load 10.1.3.0.0 dictionary version using 10.1.3SOA code base.

Action: The dictionary might need to be fixed manually. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01301: The ruleset with name {0} already exists in the dictionary. Use a different name for the ruleset.

Cause: The ruleset with name already exists in the dictionary.

Action: Use a different name for the ruleset.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01302: There is no data model defined for the ruleset {0}. Set a data model first before creating the ruleset.

Cause: There is no data model defined for the ruleset.

Action: Set a data model first before creating the ruleset.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01303: The ruleset with the same name {0} is already in dictionary. If you want to replace the existing ruleset, remove it from dictionary first.

Cause: The ruleset with the same name is already in dictionary.

Action: If you want to replace the existing ruleset, remove it from dictionary first.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01304: The ruleset with the name {0} is not in dictionary.

Cause: The ruleset with the name is not in dictionary.

Action: Specify a ruleset name that exists in the dictionary.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01305: An OptionSet {0} already exists. Either remove the existing OptionSet from the dictionary, or change the name of the OptionSet being added.

Cause: An OptionSet with the same name already exists.

Action: Either remove the existing OptionSet from the dictionary, or change the name of the OptionSet being added.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01306: The data model added to the dictionary is null. Ensure the data model is a valid object.

Cause: The data model added to the dictionary is null.

Action: Ensure the data model is a valid object.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01307: The dictionary name is either null or an empty string. Ensure the dictionary is valid.

Cause: The dictionary name is either null or an empty string.

Action: Ensure the dictionary is valid.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01401: The path specified: {0} does not exist. Ensure the path exists on the host system.

Cause: The path specified does not exist.

Action: Ensure the path exists on the host system.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01402: The dictionary specified was null or is invalid. Ensure that the constructor for RuleObjectHelper is passed a valid Dictionary.

Cause: The dictionary specified was null or is invalid.

Action: Ensure that the constructor for RuleObjectHelper is passed a valid Dictionary.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01403: The parameter is null. Ensure that the parameter is not null.

Cause: The parameter is null.

Action: Ensure that the parameter is not null.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01404: The Fact Type {0} was not located.

Cause: The Fact Type was not located.

Action: Ensure the Fact Type exists or select a different name.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01405: Could not parse name {0} for type {1}.

Cause: Could not parse name for type.

Action: Choose another name for the type.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01406: Unable to locate bound pattern for {0} member: {1}.

Cause: Unable to locate bound pattern for member.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01407: getObject failed to locate Fact Type for {0}.

Cause: getObject failed to locate specified Fact Type.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01408: getObject failed to locate Method for {0} {1}.

Cause: getObject failed to locate Method.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01409: Could not parse mapper name {0} for {1}.

Cause: Could not parse mapper name for element.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01410: Failed to locate Method of name {0} and type: {1}.

Cause: Failed to locate Method.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01411: Failed to locate Field {0} {1}.

Cause: Failed to locate Field.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01412: Failed to lookup {0} named {1}.

Cause: Failed to lookup element.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01413: Unknown getObject {0} of type {1} at {2}.

Cause: Unknown getObject.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01414: Extended type information missing for {0} when retrieving type for {1}.

Cause: Extended type information missing when retrieving type.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01415: getTable failed: {0}.

Cause: getTable failed.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01416: sub map {0} not located: {1}.

Cause: Sub map not located.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01417: Missing parameter name at {0} fails with: {1}.

Cause: Missing parameter name.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01418: Parameter at {0} did not have valid expression, {1}.

Cause: Parameter does not have valid expression.

Action: Provide a valid expression for the parameter.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01419: convertTableParm received exception from sdk: {0}

Cause: convertTableParm received exception from sdk.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01420: Get raw table failed: {0}.

Cause: Get raw table failed.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01421: An advanced expression is missing the sub map.

Cause: An advanced expression is missing the sub map.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01422: The map field ADV_BODY was not located for an expression, may be wrong type of expression.

Cause: The map field ADV_BODY was not located for an expression, may be wrong type of expression.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01423: The map field ADV_OPERAND is missing. Internal error.

Cause: The map field ADV_OPERAND is missing. Internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01424: The map field ADV_OPERAND true name is missing. Internal error.

Cause: The map field ADV_OPERAND true name is missing. Internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01425: The map field ADV_FUNCTION is missing. Internal error.

Cause: The map field ADV_FUNCTION is missing. Internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01426: The map field ADV_FUNCTION true name is missing. Internal error.

Cause: The map field ADV_FUNCTION true name is missing. Internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01427: An indentifier {0} was not located attempting to parse: {1}.

Cause: An indentifier was not located attempting to parse.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01428: The expression is invalid and had {0} tokens.

Cause: The expression is invalid.

Action: Correct the expression to be valid.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01429: SDK Exception was received {0} {1}

Cause: SDK Exception was received.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01430: Unknown instance type in an advanced expression {0}

Cause: Unknown instance type in an advanced expression

Action: Provide a valid advanced expression.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01431: Update for Map field {0} failed with: {1}

Cause: Update for Map field failed.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01432: In routine {0} null return from addOperator conjunction for {1} root.

Cause: In routine null return from addOperator conjunction for root.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01433: An illegal expression table, contains no conjunctions, but more than one entry. Conjunctions must be used to join multiple entries.

Cause: An illegal expression table, contains no conjunctions, but more than one entry.

Action: Add conjunctions to join multiple entries.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01434: An illegal expression table, two operands require an operator. Select operator to apply to the operands.

Cause: An illegal expression table, two operands require an operator.

Action: Select operator to apply to the operands.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01435: Expected expression table, field {0} is not a table

Cause: Expected expression table, field is not a table

Action: Contace Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01436: Failed to parse expression in row {0}.

Cause: Failed to parse expression in row.

Action: Provide a valid expression in this row.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01437: Test Expression at {0} is missing a conjunction.

Cause: Test Expression at is missing a conjunction.

Action: Specify a conjunction for this test expression.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01438: Test Expression at {0} is missing operands.

Cause: Test Expression is missing operands.

Action: Specify operands for this test expression.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01439: Test Expression at {0} is missing operator.

Cause: Test Expression is missing operator.

Action: Specify a valid operator for this test expression.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01440: Test Expression at {0} has an invalid operator: {1} and received exception: {2}.

Cause: Test Expression has an invalid operator.

Action: Specify a valid operator for this test expression.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01441: Test Expression at {0} has more operands than the operator allows.

Cause: Test Expression has more operands than the operator will allow.

Action: Specify the correct number of operands.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01442: Test Expression at {0} has no operator and two operands.

Cause: Test Expression has no operator and two operands.

Action: Provide a valid operator for the two operands.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01443: Unable to build expression for {0} return code: {1}

Cause: Unable to build expression for return code.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01444: Failed to get field {0} returns {1}.

Cause: Failed to get field.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01445: Name was null or empty cannot be retrieved

Cause: Name was null or empty and cannot be retrieved.

Action: Provide a valid name to retrieve.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01446: {0} is not a valid identifier. Modify this to be valid RL identifier.

Cause: Value is not a valid identifier.

Action: Modify this to be valid RL identifier.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01447: Failed to create the Action statements during Rule update.

Cause: Failed to create the Action statements during Rule update.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01448: Assert at [{0}] parameter list could not be built, returns {1}.

Cause: Assert in parameter list could not be built.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01449: Unable to parse expression for the Action {1} for number {0}, check error details. Returns {2}

Cause: Unable to parse expression for the Action.

Action: Check the error details and provide a valid expression.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01450: Action at [{0}] failed to build parameter list, returns {1}.

Cause: Action failed to build parameter list

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01451: Unable to build Assign statement at [0].

Cause: Unable to build Assign statement at [0].

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01452: Unable to build return expression at [{0}], returns{1}.

Cause: Unable to build return expression.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01453: The alias {0} is duplicated in another {1} named {2}. Change one of the aliases. Aliases must be unique within {1} type.

Cause: The alias is duplicated in another component.

Action: Change one of the aliases. Aliases must be unique within all components of each component type.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01454: Field at [{0}] is not a valid identifier. Change the name to be a valid identifier.

Cause: Field is not a valid identifier.

Action: Change the name to be a valid identifier.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01455: Unable to locate Fact Type for field named {0} at [{1}].

Cause: Unable to locate Fact Type for field

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01456: Unknown parameter Fact Type {0} parameter at [{1}].

Cause: Unknown parameter Fact Type parameter.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01457: Exception generated for add of property: {0}.

Cause: Exception generated for add of property.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01458: Duplicate names are not allowed. {0} is used previously for this type. Change the name to be unique or delete the pre-existing entity.

Cause: Duplicate names are not allowed. The name is used previously for this type.

Action: Change the name to be unique or delete the pre-existing entity.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01459: Exception received for add of Fact: {0}.

Cause: Exception received for add of Fact.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01460: There is no matching Fact Type for {0} at position {1}.

Cause: There is no matching Fact Type.

Action: Provide a valid Fact Type.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01461: Parameter names must be valid RL identifiers. Parameter at position {0} is not a valid identifier.

Cause: Parameter name is not a valid identifier.

Action: Specify a valid RL identifier for the name.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01462: Failed to delete function, returns {0}.

Cause: Failed to delete function.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01463: Missing function rl statement. Function may be empty but must have a body.

Cause: Function body is entirely empty.

Action: Function body does not need to contain RL statements, but must contain more than the empty string.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01464: The block table had an empty statement and was malformed, returns{0}.

Cause: The block table had an empty statement and was malformed.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01465: Expected expression to describe the constant. The expression was not located in the map, returns {0}.

Cause: Expected expression to describe the constant. The expression was not located in the map.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01466: Constant must have a an initializing value. Add a value or an expression.

Cause: Constant must have a an initializing value.

Action: Add a value or an expression.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01467: Failed to create expression node from advanced expression, returns {0}.

Cause: Failed to create expression node from advanced expression.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01468: Missing field {0} in map. This is an internal error {1}.

Cause: Missing field in map. This is an internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01469: Failed to delete previous constant, returns {0}.

Cause: Failed to delete previous constant.

Action: Contract Oracle Support Services
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01470: Invalid range value. Ranges must be valid doubles.

Cause: Invalid range value.

Action: Provide a valid range of double values.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01471: Invalid Constraint type: {0}.

Cause: Invalid Constraint type.

Action: Specify a valid constraint type.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01472: Could not locate {0} named {1} in dictionary.

Cause: Could not locate component in dictionary.

Action: Specify the name of a component that exists in the dictionary.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01473: Duplicate Rule name {0} in the RuleSet change the name of the new Rule.

Cause: Duplicate Rule name in the RuleSet.

Action: Change the name of one of the rules.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01474: Duplicate Rule name {0} in the RuleSet, updates may not change the Rule name to that of an existing Rule. Change the Rule name.

Cause: Duplicate Rule name in the RuleSet, updates may not change the Rule name to that of an existing Rule.

Action: Change the Rule name.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01475: Invalid priority value. Rule priority must be an integer. Modify priority to contain only digits.

Cause: Invalid priority value. Rule priority must be an integer.

Action: Modify priority to contain only digits.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01476: The dictionary does not have a data model. Internal error.

Cause: The dictionary does not have a data model.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01477: Pattern table, failed to add null root at [{0}].

Cause: Pattern table, failed to add null root.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01478: Failed on return from test in build pattern Test Expression for pattern {0}, return {1}.

Cause: Failed on return from test in build pattern Test Expression for pattern.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01479: Pattern table {0} could not be located in the map, returns {1}.

Cause: Pattern table could not be located in the map.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01480: Pattern instance name at [{0}] is not valid. Pattern instance names must be valid rl names.

Cause: Pattern instance name is not valid.

Action: Specify valid RL names for the pattern instance names.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01481: Pattern instance name {0} at [{1}] is a duplicate of Pattern instance name at [{2}]. Pattern instance names must be unique.

Cause: Pattern instance name is a duplicate of Pattern instance name.

Action: Specify pattern instance names that are unique.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01482: Pattern instance name {0} at [{1}] is missing a conjunction. Patterns must be joined by conjunctions.

Cause: Pattern instance name is missing a conjunction.

Action: Specify conjunctions between each pattern.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01483: Failed to build Pattern expression.

Cause: Failed to build Pattern expression.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01484: Table {0} get length failed with {1}.

Cause: Table get length failed.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01485: Failed while working on Statement Table, returns{0}.

Cause: Failed while working on Statement Table.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01486: Failed to parse Statement for row {0}, returns{1}.

Cause: Failed to parse Statement.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01487: Failed to parse a variable type name {0}, returns {1}.

Cause: Failed to parse a variable type name.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01488: vartype is null for var name: {0}.

Cause: vartype is null for var name.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01489: Invalid object type for {0}.

Cause: Invalid object type.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01490: Edit point {0} is not within the expression.

Cause: Edit point is not within the expression.

Action: Set edit point to be within the expression.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01491: ADV_TYPE selection is missing from the expression map, returns{0}.

Cause: ADV_TYPE selection is missing from the expression map.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01492: Failed to create the parameter mask for inserted function, returns{0}.

Cause: Failed to create the parameter mask for inserted function.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01493: ADV_CVALUE is missing from the expression map, returns{0}.

Cause: ADV_CVALUE is missing from the expression map.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01494: Constraint {0} cannot be retrieved. The Constraint may have been removed.

Cause: Constraint cannot be retrieved. The Constraint may have been removed.

Action: Specify a constraint which exists.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01495: Operand {1} had no type and is being ignored.

Cause: Operand had no type and is being ignored.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01496: Possible error, Constraint choice list has no selection.

Cause: Possible error, Constraint choice list has no selection.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01497: For Constraint named: {0}, no Dictionary object could be located. Check to make sure the constraint was not deleted from the dictionary.

Cause: For Constraint, no Dictionary object could be located.

Action: Check to make sure the constraint was not deleted from the dictionary.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01498: Function type was set, but no Function was selected. Internal error.

Cause: Function type was set, but no Function was selected.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01499: Constraint {0} cannot be retrieved. The Constraint may have been removed.

Cause: Constraint cannot be retrieved. The Constraint may have been removed.

Action: Specify a constraint that exists in the datamodel.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01500: Dictonary object for Function operand in row [{0}] could not be located. Ensure function has not been deleted.

Cause: Dictonary object for Function operand in row could not be located.

Action: Ensure function has not been deleted.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01501: Object lookup failed for {0}. Internal error returns {1}.

Cause: Object lookup failed for component.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01502: Internal error returns {1}. External type information cannot be parsed

Cause: External type information cannot be parsed

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01503: Function type was set, but no Function was selected. For {0}.

Cause: Function type was set, but no Function was selected.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01504: Dictonary object for Function operand in row [{0}] could not be located, returns{1}. Ensure function has not been deleted.

Cause: Dictonary object for Function operand could not be located.

Action: Ensure function has not been deleted.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01505: Type Constant was set and not constant value is present. Enter or select a Constant.

Cause: Type Constant was set and not constant value is present.

Action: Enter or select a Constant.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01506: Must select operand for an expression. No selection was located.

Cause: Must select operand for an expression. No selection was located.

Action: Specify an operand for the expression.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01507: Failed to determine the type of the Simple {0} operand, type returned null. Internal error.

Cause: Failed to determine the type of the Simple operand, type returned null.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01508: Failed to getObject for {0} at [{1}], returns {2}. Internal Error.

Cause: Failed to getObject.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01509: The operand type {0} does not exist. Internal error, invalid operand type set.

Cause: The operand type does not exist. Internal error, invalid operand type set.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01510: Missing constant value, must have a constant. Enter either an rl expression or a literal constant.

Cause: Missing constant value, must have a constant.

Action: Enter either an rl expression or a literal constant.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01511: Failed to pass Constraint check for {0}. Exception received: {1}

Cause: Failed to pass Constraint check.

Action: Specify values that conform to constraints.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01512: Failed operator add, invalid root exception received {0}

Cause: Failed operator add, invalid root exception received

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01513: Failed to retrieve properties for {0}. Internal Error.

Cause: Failed to retrieve properties.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01514: setRootOperator received an exception {0}. Correct the operator.

Cause: setRootOperator received an exception.

Action: Correct the operator.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01515: setRootOperator for an Assign received an exception {0}. Correct the operator.

Cause: setRootOperator for an Assign received an exception.

Action: Correct the operator.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01516: setRootOperator die Define received an exception {0}

Cause: setRootOperator die Define received an exception.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01517: setRoot could not produce an operator for {0}.

Cause: setRoot could not produce an operator for component.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01518: Improper root {0}.

Cause: Improper root.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01519: Failed to build parameter table, returns {0}. See error stack for complete description.

Cause: Failed to build parameter table.

Action: See error stack for complete description.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01520: Failed to build method parameter table, returns {0}. See error stack for complete description.

Cause: Failed to build method parameter table.

Action: See error stack for complete description.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01521: Missing Pattern Type not selected, make a Pattern Type selection

Cause: Missing Pattern Type not selected.

Action: Make a Pattern Type selection.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01522: Failed to locate Pattern Type, returns{0}. Check that Pattern Type exists.

Cause: Failed to locate Pattern Type.

Action: Check that Pattern Type exists.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01523: setRootPattern received an exception {0}

Cause: setRootPattern received an exception.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01524: Failed to create Pattern. No Pattern type specified for the Pattern.

Cause: Failed to create Pattern. No Pattern type specified for the Pattern.

Action: Specify a Pattern type for the Pattern.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01525: Attempted to add operand, without an operator. Internal Error.

Cause: Attempted to add operand, without an operator.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01526: Received exception for addPattern. {0}

Cause: Received exception for addPattern.

Action: Correct exception or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01527: Received exception for loadClass. {0}

Cause: Received exception for loadClass.

Action: Correct exception or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01528: A {0} named {1} is not located in the current dictionary.

Cause: Component is not located in the current dictionary.

Action: Specify a component that exists in the dictionary.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01529: A Rule named {0} is not part of RuleSet {1}. You may have inadvertantly modified the Rule name. If you modify the Rule name, the action becomes a copy and no other fields may be modified.

Cause: Rule is not part of the RuleSet.

Action: The Rule name may have inadvertantly been modified. If the Rule name is modified, the action becomes a copy and no other fields may be modified.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01530: The map type: {0} is not correct. A map of type {1} was expected. This is an internal error.

Cause: The map type is not correct. A map of another type was expected.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01531: The file specified: {0} could not be turned into a URL, which is the internal format. Check the file specification to make sure it is correct.

Cause: The file specified could not be turned into a URL, which is the internal format.

Action: Check the file specification to make sure it is correct.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01532: The Fully Qualified Name: {0} was not located in the list, load fails.

Cause: The Fully Qualified Name was not located in the list, load fails.

Action: Check the name or specify a name which exists in the list.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01533: Index at {0} is out of range of the tree.

Cause: Index is out of range of the tree.

Action: Specify an index which is in the range of the tree.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01534: Item should be one of {0} but is: {1}. Internal error.

Cause: Item should be a different value. Internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01535: Expected Row type of {0} but found {1}. Internal error.

Cause: Expected Row of one type but found a different one. Internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01536: The field {0} was found, but was NOT a table. Internal error.

Cause: The field was found, but was NOT a table. Internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01537: The RuleObjectHelper that returns the sub map, must use the same dictionary. The dictionaries are not the same.

Cause: The RuleObjectHelper that returns the sub map, must use the same dictionary. The dictionaries are not the same.

Action: Specify dictionaries that are the same.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01538: Index {0} is out of range of the table.

Cause: Index is out of range of the table.

Action: Specify an index that is within the table range.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01539: RL Generation failed.

Cause: RL Generation failed.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01540: The row was not present that contained rowId: {0}

Cause: The row was not present that contained rowId.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01541: The map is not a map that may issue an update: {0}. Only first class maps representing dictionary entities may be updated. Check the map type.

Cause: The map is not a map that may issue an update. Only first class maps representing dictionary entities may be updated. Check the map type.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01542: A choice list {0} had not had a valid entry selected. Therefore no selection could be returned.

Cause: A choice list had not had a valid entry selected. Therefore no selection could be returned.

Action: Specify a valid selection.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01543: The expression in {0} was NOT a constant.

Cause: The expression in was NOT a constant.

Action: Specify a constant for the expression.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01544: Failed to create a customization entry. The root cause is: {0}

Cause: Failed to create a customization entry.

Action: See root cause message.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01546: During a load class, a ClassNotFoundException was received: {0}

Cause: During a load class, a ClassNotFoundException was received.

Action: Specify a class that exists on the classpath or add the specified class to the classpath.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01547: During the setting of a decorated choice list, a class of {0} is not handled. This is an internal error.

Cause: During the setting of a decorated choice list, a class is not handled. This is an internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01548: The set of a dependent field failed: {0}. Set the value correctly.

Cause: The set of a dependent field failed.

Action: Set the value correctly.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01549: During the setting of a decorated choice list, no match was found in the list for {0}. This is an internal error or the result of a deleted dictionary object.

Cause: During the setting of a decorated choice list, no match was found in the list. This is an internal error or the result of a deleted dictionary object.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01550: During the setting of a list {0}, no match was found in the list for {1}.

Cause: During the setting of a list, no match was found in the list for the specified name.

Action: Specify a name that exists in the list.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01551: Missing dependent field {0}. This is an internal error, the map does not have an expected field.

Cause: Missing dependent field. This is an internal error, the map does not have an expected field.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01552: Dependent field {0} failed with {1} from a helper routine.

Cause: Dependent field failed with error from a helper routine.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01553: Dependent field {0} could not process the value: {1}.

Cause: Dependent field could not process the value.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01554: Dependent field {0} has no handlers.

Cause: Dependent field has no handlers.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01555: Expected String[] or ArrayList table and {0} is {1}.

Cause: Expected String[] or ArrayList table, but returned otherwise.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01556: Missing the true name list for {0}.

Cause: Missing the true name list.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01557: Missing the alias list for {0}.

Cause: Missing the alias list.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01558: AddEmptyRow cannot be performed for {0} row type.

Cause: AddEmptyRow cannot be performed for row type.

Action: Do not attempt this operation on this type of object.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01559: Function {0} was not located when attempting to build parameter table.

Cause: Function was not located when attempting to build parameter table.

Action: Check that function exists or specify a different function.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01560: During parameter table building an object {0} was not selected.

Cause: During parameter table building an object was not selected

Action: Select an object.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01561: During parameter table creation, an object {0} could not be located in the data model: {1}

Cause: During parameter table creation, an object could not be located in the data model

Action: During parameter table creation, an object could not be located in the data model
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01562: {0} statement failed to create a parameter table: {1}

Cause: Statement failed to create a parameter table

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01563: An {0} statement failed to create an expression. The expression body is missing.

Cause: A statement failed to create an expression. The expression body is missing.

Action: Specify an expression body.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01564: {0} could not locate an expression. Expected an RLText node but got {1}.

Cause: Component could not locate an expression. Expected an RLText node but got otherwise.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01565: List creation failed: {0}

Cause: List creation failed

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01566: Unable to locate Pattern of relative row {0}. This is an internal error. The Pattern table may have been corrupted.

Cause: Unable to locate Pattern of relative row.

Action: This is an internal error. The Pattern table may have been corrupted. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01567: Searching the Pattern table failed, no rowid. This is an internal error. The Pattern table may have been corrupted.

Cause: Searching the Pattern table failed, no rowid.

Action: Searching the Pattern table failed, no rowid. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01568: Searching the Pattern table failed, could not locate the parent Rule map. This is an internal error. The Pattern table parent pointer may have been corrupted.

Cause: Searching the Pattern table failed, could not locate the parent Rule map. .

Action: This is an internal error. The Pattern table parent pointer may have been corrupted. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01569: Searching the Pattern table failed, no Pattern table was located in the Rule Map. This is an internal error. The Pattern table may have been corrupted.

Cause: Searching the Pattern table failed, no Pattern table was located in the Rule Map.

Action: This is an internal error. The Pattern table may have been corrupted. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01570: Failed to create Action at {0}, received exception: {1}

Cause: Failed to create Action.

Action: See underlying exception.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01571: Field name at [{0}] is not a valid RL identifier. Modify the field name {1} to be a valid RL name.

Cause: Field name is not a valid RL identifier.

Action: Modify the field name to be a valid RL name.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01572: Rules must have at least one Pattern.

Cause: Rules must have at least one Pattern.

Action: Add at least one Pattern to each Rule.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01573: Make a selection for {0}.

Cause: No value selected for the component.

Action: Make a selection for the value of the component.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01574: Method Name {0} with no parent.

Cause: Method Name with no parent.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01575: Bind Instance Name {0} not located for Condition in Rule.

Cause: Bind Instance Name not located for Condition in Rule.

Action: Provide a valid bind instance name for the Condition.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01576: token: {0} at {1} is unterminated

Cause: Token is unterminated.

Action: Terminate token.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01577: token: {0} at {1} is not a known token

Cause: Token is not a known token.

Action: Provide a valid token in that location.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01578: token: {0} at {1} is unmatched

Cause: Token is unmatched.

Action: Match token.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01579: token: {0} at {1} is an invalid number

Cause: Token is an invalid number.

Action: Provide a valid number for this token.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01580: Syntax error for token '{0}' at column {1}

Cause: Syntax error for token.

Action: Correct the syntax error.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01581: token: {0} at {1} is an unknown parser error

Cause: Token is an unknown parser error

Action: Correct parser error.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01582: properties {0} and {1} have the same aliases {2}. Aliases must be unique within a Class. Change one of the aliases.

Cause: Two properties have the same aliases.

Action: Aliases must be unique within a Class. Change one of the aliases.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01583: methods {0} and {1} have the same aliases {2}. Aliases must be unique within a Class. Change one of the aliases.

Cause: Two methods have the same aliases.

Action: Aliases must be unique within a Class. Change one of the aliases.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01584: The field {0} was NOT set. Select a value for {0}.

Cause: The field was NOT set.

Action: Select a value for the field.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01585: The type specified {0}. Is not a valid node type. See documentation for the SDK and JavaNode class.

Cause: The type specified. Is not a valid node type.

Action: See documentation for the SDK and JavaNode class.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01586: The Root Node for type {0}, could not be located in the NodeTable. Refer to the documentation for the SDK and JavaNode class.

Cause: The Root Node for type, could not be located in the NodeTable.

Action: Refer to the documentation for the SDK and JavaNode class.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01599: An error has occurred. {0} is incorrect.

Cause: An error has occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01600: Fact Type {0} cannot be deleted as it is used {1} time(s) in the dictionary.

Cause: Fact Type cannot be deleted as it is used in the dictionary.

Action: Remove the refrences to the Fact Type and then attempt to delete it.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01601: Function {0} cannot be deleted as it is used {1} time(s) in the dictionary.

Cause: Function cannot be deleted as it is used in the dictionary.

Action: Remove the refrences to the Function and then attempt to delete it.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01602: Constraint {0} cannot be deleted as it is used {1} time(s) in the dictionary.

Cause: Constraint cannot be deleted as it is used in the dictionary.

Action: Remove the refrences to the Constraint and then attempt to delete it.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01603: Variable {0} cannot be deleted as it is used {1} time(s) in the dictionary.

Cause: Variable cannot be deleted as it is used in the dictionary.

Action: Remove the refrences to the Variable and then attempt to delete it.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01604: Dictionary object is null, found while checking consistency for deleting Fact Type {0}.

Cause: Dictionary object is null, found while checking consistency for deleting Fact Type.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01605: Fact Type {0} is used in variable {1}.

Cause: Fact Type is used in variable.

Action: Remove variable before attempting to remove Fact Type
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01606: Fact Type {0} is used in function {1}.

Cause: Fact Type is used in function.

Action: Remove function before attempting to remove Fact Type.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01607: Fact Type {0} is used in another Fact Type {1} as array component type.

Cause: Fact Type is used in another Fact Type as array component type.

Action: Remove references to this Fact Type before attempting to remove this component.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01608: Fact Type {0} is used in another Fact Type {1} as its interface.

Cause: Fact Type is used in another Fact Type as its interface.

Action: Remove references to this Fact Type before attempting to remove this component.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01609: Fact Type {0} is used in another Fact Type {1} as its super class.

Cause: Fact Type is used in another Fact Type as its super class.

Action: Remove references to this Fact Type before attempting to remove this component.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01610: Fact Type {0} is used in another Fact Type {1} as its field type.

Cause: Fact Type is used in another Fact Type as its field type.

Action: Remove references to this Fact Type before attempting to remove this component.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01611: Fact Type {0} is used in method {1} of the class {2}.

Cause: Fact Type is used in a method of the class.

Action: Remove references to this Fact Type before attempting to remove this component.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01612: Fact Type {0} is used in one of the constructors in the class {1}.

Cause: Fact Type is used in one of the constructors in the class.

Action: Remove references to this Fact Type before attempting to remove this component.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01613: Fact Type {0} is used in ruleset {1} rule {2} pattern {3}.

Cause: Fact Type is used in a rule pattern.

Action: Remove references to this Fact Type before attempting to remove this component.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01614: Fact Type {0} is used in the action of ruleset {1} rule {2}.

Cause: Fact Type is used in the action of a rule.

Action: Remove references to this Fact Type before attempting to remove this component.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01615: Dictionary object is null while checking consistency for deleting function {0}.

Cause: Dictionary object is null while checking consistency for deleting function.

Action: Remove references to this Fact Type before attempting to remove this component.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01616: Function {0} is used in variable {1}.

Cause: Function is used in a variable.

Action: Remove references to this Function before attempting to remove this component.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01617: Function {0} is used in ruleset {1} rule {2} pattern {3}.

Cause: Function is used in rule pattern.

Action: Remove references to this Function before attempting to remove this component.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01618: Function {0} is used in the action of ruleset {1} rule {2}.

Cause: Function is used in the action of rule.

Action: Remove references to this Function before attempting to remove this component.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01619: Dictionary object is null while checking consistency for deleting constraint {0}.

Cause: Dictionary object is null while checking consistency for deleting constraint.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01620: Constraint {0} is used in variable {1}.

Cause: Constraint is used in variable.

Action: Remove references to this Constraint before attempting to remove this component.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01621: Constraint {0} is used in ruleset {1} rule {2} pattern {3}.

Cause: Constraint is used in rule pattern.

Action: Remove references to this Constraint before attempting to remove this component.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01622: Constraint {0} is used in the action of ruleset {1} rule {2}.

Cause: Constraint is used in the action of rule.

Action: Remove references to this Constraint before attempting to remove this component.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01623: Dictionary object is null while checking consistency for deleting variable {0}.

Cause: Dictionary object is null while checking consistency for deleting variable.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01624: Variable {0} is used in another variable {1}.

Cause: Variable is used in another variable.

Action: Remove references to this Variable before attempting to remove this component.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01625: Variable {0} is used in ruleset {1} rule {2} pattern {3}.

Cause: Variable is used in ruleset rule pattern.

Action: Remove references to this Variable before attempting to remove this component.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01626: Variable {0} is used in the action of ruleset {1} rule {2}.

Cause: Variable is used in the action of rule.

Action: Remove references to this Variable before attempting to remove this component.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01627: The schema {0} has been imported. Delete it if you want to reimport the same schema.

Cause: The schema has been imported.

Action: Delete it if you want to reimport the same schema.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01701: The name cannot be blank. Enter a name.

Cause: The name cannot be blank.

Action: Enter a name.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01702: The name \\"{0}\\" is already in use. Enter a different name

Cause: The name is already in use.

Action: Enter a different name
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01703: The rule must have at least one pattern. Add a pattern.

Cause: The rule must have at least one pattern.

Action: Add a pattern.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01704: \\"{0}\\" is not the name of a Fact Type. Enter a valid Fact Type.

Cause: The value is not the name of a Fact Type.

Action: Enter a valid Fact Type name.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01706: The pattern variable \\"{0}\\" is used more than once. Change one of the names.

Cause: The pattern variable is used more than once.

Action: Change one of the names.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01707: Priority must be blank, or a positive or negative number.

Cause: Priority must be blank, or a positive or negative number.

Action: Specify a valid value.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01708: Data validation error: {0}

Cause: Data validation error

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01709: \\"{0}\\" is not a valid Fact Type.

Cause: The value is not a valid Fact Type.

Action: Specify a valid Fact Type.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01710: \\"{0}\\" is not a valid choice for {1}.

Cause: Selected value is not a valid choice for the component.

Action: Specify a valid value.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01711: Expression cannot be blank. Enter an expression

Cause: Expression cannot be blank.

Action: Enter an expression
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01712: Invalid variable name \\"{0}\\": contains multiple spaces.

Cause: Invalid variable name, contains multiple spaces.

Action: Specify a variable name that does not contain multiple spaces.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01713: Invalid rule set name \\"{0}\\": Must begin with a letter and contain only letters and numbers.

Cause: Invalid rule set name.

Action: Specify a rule set name that begins with a letter and contains only letters and numbers.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01714: Invalid rule name \\"{0}\\": Must begin with a letter and contain only letters and numbers.

Cause: Invalid rule name.

Action: Specify a rule name that begins with a letter and contains only letters and numbers.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01716: \\"{0}\\" is not a valid function name.

Cause: The name is not a valid function name.

Action: Specify a valid function name.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01717: \\"{0}\\" is not a valid identifier name, or a string has not been properly surrounded with quotes(\\"\\").

Cause: The value is not a valid identifier name, or a string has not been properly surrounded with quotes("").

Action: Specify a valid identifier name or surround the identifier with quotes.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01718: \\"{0}\\" is not a valid constraint name.

Cause: The value is not a valid constraint name.

Action: Specify a valid constraint name.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01719: Nothing to restore.

Cause: Nothing to restore.

Action: None.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01720: Nothing to discard.

Cause: Nothing to discard.

Action: None.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01721: Missing test on Pattern. Confirm or supply a test

Cause: Missing test on Pattern.

Action: Confirm or supply a test
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01722: {0} must match the pattern: {1}

Cause: Value must match the pattern value.

Action: Specify a matching value.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01723: {0} must be a number between {1} and {2}

Cause: The value must be a number between the upper and lower bound.

Action: Specify a valid value.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01724: Array {0} must be followed by []

Cause: Array must be followed by []

Action: Add [] to array definition.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01725: {0} is not an Array and cannot be followed by []

Cause: The value is not an Array and cannot be followed by []

Action: Specify a valid value.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01726: Data type operator for {0}, at position {1}: {2} {3} {4}

Cause: Data type operator error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01727: Incorrect number of parameters for function {0} at {1}

Cause: Incorrect number of parameters for the function.

Action: Specify the correct number of parameters for the function.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01728: Test expression must return true or false, not \\"{0}\\"

Cause: Test expression must return true or false, but did not.

Action: Specify a test expression that returns a boolean value.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01729: Must be a literal value. Strings must be quoted with \\"\\".

Cause: Must be a literal value.

Action: Provide a numeric value or quote Strings.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01730: Must be a number.

Cause: Value is not a number.

Action: Specify a numeric value.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01731: The nested Pattern has an empty NestedTable. Remove the nested Pattern or add nested entries.

Cause: The nested Pattern has an empty NestedTable.

Action: Remove the nested Pattern or add nested entries.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01801: The value {0} is not in the option list for {1}.

Cause: The value is not in the option list.

Action: Specify a value that is in the option list.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01802: RuleComponent {0} is not associated with a Dictionary

Cause: RuleComponent is not associated with a Dictionary

Action: Recreate the RuleComponent using the factory methods in the dictionary components, or contact Oracle Support Service.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01803: Action of FORM_ASSERT_NEW requires TARGET of class alias. See javadoc for Action.

Cause: Action of FORM_ASSERT_NEW requires TARGET of class alias.

Action: Specify an alias for the Action target. See javadoc for Action.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01804: Action of FORM_ASSIGN requires requires assignable target and single parameter. See javadoc for Action.

Cause: Action of FORM_ASSIGN requires requires assignable targetand single parameter.

Action: Specify valid values for the Action.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01805: Action of FORM_NESTED_TABLE requires ActionTable. See javadoc for Action.

Cause: Action of FORM_NESTED_TABLE requires ActionTable.

Action: Specify an ActionTable for the Action. See javadoc for Action.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01806: System error: unable to instantiate component copy

Cause: System error: unable to instantiate component copy

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01807: Action of FORM_ASSERT or FORM_RETRACT requires TARGET variable (not \\"{0}\\"). See javadoc for Action.

Cause: Action of FORM_ASSERT or FORM_RETRACT requires target variable.

Action: Specify a target variable for the Action. See javadoc for Action.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01808: Unable to save rule set. SDK Exception: \\"{0}\\"

Cause: Unable to save rule set.

Action: Correct exception or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01809: Unable to load rule set. SDK Exception: \\"{0}\\"

Cause: Unable to load rule set.

Action: Correct exception or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01810: Expression parameter conflict, Form is \\"{0}\\" but property {1} was set.

Cause: Conflicting form and property set.

Action: Resolve conflict. See javadoc for Action.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01811: The number of rows in this table cannot be changed.

Cause: The number of rows in this table cannot be changed.

Action: Do not attempt to add or remove rows from this table.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01812: Row not found

Cause: Row not found.

Action: Specify a row that exists.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01813: Enum constraint {0} contains invalid values for property {1}

Cause: Enum constraint contains invalid values for property

Action: Remove invalid values from constraint.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01814: Program set option list contains invalid values for {0}

Cause: Program set option list contains invalid values.

Action: Remove invalid values from program set option list.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01815: Null values not allowed for key or value put ( {0}, {1} )

Cause: Null values not allowed for key or value of put() call

Action: Specify a non-null value for key and value.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01816: put() key must be of type String

Cause: put() key must be of type String

Action: Specify a key of type String
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01817: Property {0} is read only

Cause: Property is read only

Action: Do not attempt to set property.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01818: Value for property {0} must be of type {1}

Cause: Value for property must be of type.

Action: Specify a value of the correct type.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01819: \\"{0}\\" is not a valid property of {1}

Cause: The value is not a valid property of the component.

Action: Specify a valid property of the component.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01820: Constraint \\"{0}\\" not found in data model

Cause: Constraint not found in data model.

Action: Specify a Constraint in the data model
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01821: Only CUSTOM and program set OPTIONS properties can be removed

Cause: Only CUSTOM and program set OPTIONS properties can be removed.

Action: Do not attempt to remove the specified property.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01822: Cannot set Property {0} in custom mode, has default CONSTRAINT_FIXED.

Cause: Cannot set Property in custom mode, has default CONSTRAINT_FIXED.

Action: Do not attempt to set this property or change the constraint to something other than fixed.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01880: While loading ruleset {0} from persistence to editor, unable to find this ruleset in the dictionary.

Cause: While loading ruleset from persistence to editor, unable to find this ruleset in the dictionary.

Action: Specify a different ruleset or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01881: The ruleset to be loaded contains a pattern {0}, which has nested conjunction tests. Oracle Rules Editor API currently doesn't support the nested tests.

Cause: The ruleset to be loaded contains a pattern, which has nested conjunction tests. Oracle Rules Editor API currently doesn't support the nested tests.

Action: Remove the nested conjunction tests.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01882: The ruleset to be loaded contains a test which is not in the format (lhs op rhs). Oracle Rules Editor API only supports simple test given above.

Cause: The ruleset to be loaded contains a test which is not in the format (lhs op rhs).

Action: Oracle Rules Editor API only supports simple test given above.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01883: Unable to save priority {0} for rule {1}. Make sure the priority is a well-formatted integer.

Cause: Unable to save priority for rule.

Action: Ensure the priority is a well-formatted integer.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01884: While saving the editor DataModel, the type \\"{1}\\" of variable \\"{0}\\" is not found in persistent DataModel.

Cause: While saving the editor DataModel, the type of the variable is not found in persistent DataModel.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01885: While saving the editor DataModel, the enumeration constraint \\"{0}\\" does not have a list of possible values.

Cause: While saving the editor DataModel, the enumeration constraint does not have a list of possible values.

Action: Specify a list of values for the constraint.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01886: While saving the editor DataModel, the return type \\"{1}\\" of function \\"{0}\\" is not found in the persistent DataModel.

Cause: While saving the editor DataModel, the return type of function is not found in the persistent DataModel.

Action: Import or define the Fact Type of the return function.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01887: While saving the editor DataModel, the parameter type \\"{1}\\" of function \\"{0}\\" is not found in the persistent DataModel.

Cause: While saving the editor DataModel, the parameter type of function is not found in the persistent DataModel.

Action: Import or define the Fact Type of the function.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01888: While saving the editor DataModel, the exception type \\"{1}\\" of function \\"{0}\\" is not found in the persistent DataModel.

Cause: While saving the editor DataModel, the exception type of function is not found in the persistent DataModel.

Action: Import or define the Fact Type of the function.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01889: While saving the editor DataModel, RLFact Type \\"{0}\\" super class \\"{1}\\" is not found in the persistent DataModel.

Cause: While saving the editor DataModel, RLFact Type super class is not found in the persistent DataModel.

Action: Import or define the Fact Type.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01890: While saving the editor DataModel, the type \\"{1}\\" of property \\"{0}\\" is not found in the persistent DataModel.

Cause: While saving the editor DataModel, the type of property is not found in the persistent DataModel.

Action: Import or define the Fact Type.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01891: While saving the editor DataModel, the corresponding Java Property \\"{0}\\" is not found in the persistent DataModel.

Cause: While saving the editor DataModel, the corresponding Java Property is not found in the persistent DataModel.

Action: Import or define the Fact Type.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01892: The lower or upper bound for the range constraint \\"{0}\\" is not found in the datamodel.

Cause: The lower or upper bound for the range constraint is not found in the datamodel.

Action: Specify an lower and upper bound for the range constraint.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01893: The lower or upper bound \\"{0}\\" for the range constraint \\"{1}\\" is not a well formatted double.

Cause: The lower or upper bound for the range constraint is not a well formatted double.

Action: Specify a well formatted double for both values.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01894: The global variable \\"{0}\\" is not initialized.

Cause: The global variable is not initialized.

Action: Specify an initializer for the global variable.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01895: While validating \\"{0}\\", found {1} Error(s).

Cause: While validating component, an error was found.

Action: Correct the underlying errors.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01896: While checking for uses before a delete an invalid type of {0} was used. Change the type.

Cause: While checking for uses before a delete an invalid type was used.

Action: Change the type.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01897: While checking for uses before a delete, no data model was located.

Cause: While checking for uses before a delete, no data model was located.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-01898: While checking for uses before a delete of a Constraint, no Form property was located.

Cause: While checking for uses before a delete of a Constraint, no Form property was located.

Action: Specify a form property before attempting delete.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01899: The Primitive Fact Type {0} cannot be deleted.

Cause: The Primitive Fact Type cannot be deleted.

Action: Do not attempt to delete the fact type.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01900: Unable to delete Fact Type {0}.

Cause: Unable to delete Fact Type.

Action: Unknown.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01901: Unable to delete Constraint {0}.

Cause: Unable to delete Constraint.

Action: Unknown
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01902: The built-in function {0} cannot be deleted.

Cause: The built-in function cannot be deleted.

Action: Do not attempt to delete the built-in function.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01903: Unable to delete Function {0}.

Cause: Unable to delete Function.

Action: Unknown.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01904: Unable to delete Variable {0}.

Cause: Unable to delete Variable.

Action: Unknown.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01905: A {0} cannot be deleted.

Cause: Component cannot be deleted.

Action: Do not attempt to delete component.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01906: A Java property cannot be deleted.

Cause: A Java property cannot be deleted.

Action: Do not attempt to delete the property.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01907: A constraint must have a name.

Cause: A constraint must have a name.

Action: Specify a name for the constraint.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01908: Range Constraint {0} does not have a lower bound.

Cause: Range Constraint does not have a lower bound.

Action: Specify a lower bound for the range constraint.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01909: Range Constraint {0} does not have a well formatted lower bound {1}.

Cause: Range Constraint does not have a well formatted lower bound.

Action: Specify a well formatted lower bound.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01910: Range Constraint {0} does not have a upper bound.

Cause: Range Constraint does not have a upper bound.

Action: Specify an upper bound.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01911: Range Constraint {0} does not have a well formated upper bound {1}.

Cause: Range Constraint does not have a well formated upper bound.

Action: Specify a well formatted upper bound.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01912: Range Constraint {0} has a lower bound {1} larger than upper bound {2}.

Cause: Range Constraint has a lower bound larger than upper bound.

Action: Specify a lower bound smaller than upper bound.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01913: Enumeration Constraint {0} does not have enumeration values defined.

Cause: Enumeration Constraint does not have enumeration values defined.

Action: Define values for enumeration constraint.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01914: Regular Expression Constraint {0} does not have the regular expression defined.

Cause: Regular Expression Constraint does not have the regular expression defined.

Action: Define a regular expression for the constraint.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01915: Function name {0} is not a valid identifier.

Cause: Function name is not a valid identifier.

Action: Specify a valid function name.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01916: Function name {0} is an RL reserved word.

Cause: Function name is an RL reserved word.

Action: Specify a function name that is not an RL reserved word.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01917: Return type of function {0} has to be defined.

Cause: Return type of function has to be defined.

Action: Specify return type.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01918: Return type \\"{1}\\" of Function {0} is not defined in the datamodel.

Cause: Return type of Function is not defined in the datamodel.

Action: Import or define the Fact Type or specify a return type that is in datamodel.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01919: Body of Function {0} has to be defined.

Cause: Body of Function has to be defined.

Action: Define body of function.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01920: Function {0} has two parameters with the same name.

Cause: Function has two parameters with the same name.

Action: Change the name of one of the duplicate parameter names.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01921: Duplicated Function Name {0}.

Cause: Duplicated Function Name.

Action: Specify a different name for the function.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01922: Duplicated Function Alias {0}.

Cause: Duplicated Function Alias.

Action: Specify a different alias for the function.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01923: InitValue {0} is not valid.

Cause: InitValue is not valid.

Action: Provide a valid init value.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01924: DataModel Component {0} has an alias \\"{1}\\" starting with space.

Cause: DataModel Component has an alias starting with space.

Action: Specify an alias that does not start with a space.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01925: DataModel Component {0} has an alias \\"{1}\\" ending with space.

Cause: DataModel Component has an alias ending with space.

Action: Specify an alias that does not end with a space.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01926: DataModel Component {0} has an alias \\"{1}\\" containing double space.

Cause: DataModel Component has an alias containing double space.

Action: Remove the double space from the alias.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01927: Property must have a name.

Cause: Property must have a name.

Action: Specify a name for the property.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01928: Property name {0} is not a valid identifier.

Cause: Property name is not a valid identifier.

Action: Specify a valid identifer for the property name.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01929: Property name {0} is an RL reserved word.

Cause: Property name is an RL reserved word.

Action: Specify a name that is not an RL reserved word.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01930: Property {0} must have a type.

Cause: Property must have a type.

Action: Specify a type for the property .
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01931: Type \\"{1}\\" of property {0} is not defined in the datamodel.

Cause: Type of property is not defined in the datamodel.

Action: Import or define the type of the property into the datamodel or specify a type that is already in the datamodel.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01932: RL Fact Type name {0} is not a valid identifier.

Cause: RL Fact Type name is not a valid identifier.

Action: Specify a valid identifer for the RL Fact Type name.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01933: RL Fact Type name {0} is an RL reserved word.

Cause: RL Fact Type name is an RL reserved word.

Action: Specify a name for the RL Fact Type that is not an RL reserved word.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01934: RL Fact Type {0} contains duplicate property names.

Cause: RL Fact Type contains duplicate property names.

Action: Change the name of one of the duplicate property names.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01935: RL Fact Type {0} contains duplicate property aliases.

Cause: RL Fact Type contains duplicate property aliases.

Action: Change the name of one of the duplicate property names.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01936: Duplicated RL Fact Type Name {0}.

Cause: Duplicated RL Fact Type Name.

Action: Change the name of one of the duplicate fact types.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01937: Duplicated RL Fact Type Alias {0}.

Cause: Duplicated RL Fact Type Alias.

Action: Change one of the duplicate aliases.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01938: Global Variable name {0} is not a valid identifier.

Cause: Global Variable name is not a valid identifier.

Action: Change one of the duplicate variable names.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01939: Global Variable name {0} is a RL reserved word.

Cause: Global Variable name is an RL reserved word.

Action: Specify a global variable name that is not an RL reserved word.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01940: Value of Global variable {0} is not set.

Cause: Value of global variable is not set.

Action: Specify the value of the global variable.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01941: Value {1} of Global variable {0} is not valid.

Cause: Value of Global variable is not valid.

Action: Specify a vaild value for the global variable.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01942: Global Variable {0} must have a type.

Cause: Global variable must have a type.

Action: Specify a type for the global variable.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01943: Type \\"{1}\\" of Global Variable {0} is not defined in the datamodel.

Cause: Type of Global Variable is not defined in the datamodel.

Action: Import or define the type of variable into the datamodel or specify a different type for the variable.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01944: Value of Global variable {0} does not match its type {1}.

Cause: Value of Global variable does not match its type.

Action: Specify a value that matches type or change the type.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01945: Duplicated Global Variable Name {0}.

Cause: Duplicated Global Variable Name.

Action: Change one of the variable names.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01946: Duplicated Global Variable Alias {0}.

Cause: Duplicated Global Variable Alias.

Action: Change one of the variable aliases.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01947: One parameter in Function {0} has no name.

Cause: One parameter in Function has no name.

Action: Specify a name for the Function parameter.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01948: Formal Parameter name {0} is not a valid identifier.

Cause: Formal Parameter name is not a valid identifier.

Action: Specify a valid identifier for the formal parameter.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01949: Formal Parameter name {0} is a RL reserved word.

Cause: Formal Parameter name is an RL reserved word.

Action: Specify a name that is not an RL reserved word.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01950: Type for Formal Parameter {0} has to be defined.

Cause: Type for Formal Parameter has to be defined.

Action: Import or define type of parameter, or specify a different type.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01951: Type \\"{1}\\" of Formal Parameter {0} is not defined in the datamodel.

Cause: Type of Formal Parameter is not defined in the datamodel.

Action: Import or define type of parameter, or specify a different type.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01952: Duplicated Property Alias {0}.

Cause: Duplicated Property Alias.

Action: Change the name of one property alias.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01953: Duplicated Method Alias {0}.

Cause: Duplicated Method Alias.

Action: Change the name of one method alias.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01954: Duplicated Java Fact Type Alias {0}.

Cause: Duplicated Java Fact Type Alias.

Action: Change the name of one Java Fact Type alias.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01955: One parameter in Function {0} has no alias.

Cause: One parameter in Function has no alias.

Action: Specify an alias for this parameter.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01956: Function {0} has two parameters with the same alias.

Cause: Function has two parameters with the same alias.

Action: Change one of the duplicate parameter aliases.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-01958: Constraint {0} is used in other component(s) of the dictionary. Remove all references in order to modify the constraint name.

Cause: Constraint is used in other component(s) of the dictionary.

Action: Remove all references in order to modify the constraint name.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-02001: See the base exception for details.

Cause: Unknown.

Action: See the base exception for details.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-02002: File corresponding to the path {0} does not exist. Ensure the file exists in the file system.

Cause: File corresponding to the path does not exist.

Action: Ensure the file exists in the file system.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-02101: ID ''{0}'' includes both a tag and a revision which are mutually exclusive.

Cause: The only client of this API is rule SDK internal and tag and revision are not used.

Action: None.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-02102: Document ID has not been validated.

Cause: A rule SDK internal failed to validate a document ID before invoking the repository store layer.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-02103: ID ''{0}'' is missing the dictionary name.

Cause: A document ID was missing the dictionary name.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-02104: ID ''{0}'' is missing the document name.

Cause: A document ID was missing the document name.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-02105: ID ''{0}'' is missing the document type.

Cause: A document ID was missing the document type.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-02106: ID ''{0}'' contains an invalid wildcard. The wildchar character, '*', must apply to the entire field.

Cause: A invalid wildcard was supplied in the document ID.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-02107: Wildcards only valid with listDocuments, ID ''{0}''.

Cause: A wildcard was supplied in the document ID to be used for access other than listDocuments.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-02108: Repository does not support revision control and ID ''{0}'' contains a revision.

Cause: The only client of this API is rule SDK internal and tag and revision are not used.

Action: None.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-02109: Repository does not support tags and ID ''{0}'' contains a tag.

Cause: The only client of this API is rule SDK internal and tag and revision are not used.

Action: None.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-02110: No registration exists for ''{0}''.

Cause: No RepositoryConnection implementation was available for the specified key.

Action: Verify that the key is correct and that the corresponding RepositoryConnection was successfully registered.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-02111: Unsupported operation.

Cause: None.

Action: None.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-02112: The dictionary name in ID ''{0}'' is not a legal Unicode identifier.

Cause: An invalid dictionary name was specified.

Action: Specify a valid dictionary name. It must be a legal Unicode identifier.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-02113: The document name in ID ''{0}'' is not a legal Unicode identifier.

Cause: A invalid document name was supplied in the document ID.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-02114: The document type in ID ''{0}'' is not a legal Unicode identifier.

Cause: A invalid document type was supplied in the document ID.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-02115: The marker in ID ''{0}'' is not a legal Unicode identifier.

Cause: An invalid marker was specified.

Action: Specify a valid marker. It must be a legal Unicode identifier.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-02116: invalid or missing registration

Cause: A RepositoryConnection registration was null or one of its properties was null (not specified).

Action: Verify that the key is correct and that the corresponding RepositoryConnection was successfully registered.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-02117: ID ''{0}'' is missing the marker.

Cause: A marker was not specified in the document ID.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-02118: ID ''{0}'' is not valid for use with this repository connection.

Cause: The document ID was not created with this connection.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-02119: Unable to load repository store add-in class ''{0}''. The store is unavailable.

Cause: An error was encountered in loading the specified RepositoryConnection implementation class.

Action: Verify that the class is available on the class path.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-02120: repository connection factory initialization failure

Cause: An error was encountered initializing the RepositoryConnection factory.

Action: Investigate the exception that was logged.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-02201: missing initialization property for key ''{0}''

Cause: A required initialization parameter was missing.

Action: Provide the missing initialization parameter.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-02202: URL ''{0}'' is not a WebDAV collection.

Cause: A WebDAV URL was expected to be a path to a folder (a WebDAV collection) but it was not.

Action: Verify that the URL is correct and that it does identify a folder.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-02203: WebDAV error

Cause: A WebDAV error occurred.

Action: Consult the root cause exception.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-02204: WebDAV error occurred for URL ''{0}''.

Cause: The URL for the WebDAV repository was incorrect.

Action: Supply a valid WebDAV URL.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-02205: WebDAV repository ''{0}'' does not exist.

Cause: The specified WebDAV repository was not be found.

Action: Verify that the path to the repository is correct.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-02206: null document

Cause: A null XML Document was supplied.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-02207: WebDAV error occurred for document ''{0}'', WebDAV URL ''{1}''

Cause: A error occurred accessing a rule dictionary document on the WebDAV repository.

Action: Consult the root cause exception.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-02208: Marker ''{0}'' is invalid.

Cause: None.

Action: None.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-02209: ID ''{0}'' is not valid for document creation, modification nor deletion.

Cause: None.

Action: None.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-02210: ID ''{0}'' is not valid for document access.

Cause: An internal ID identifying a document that is part of a rule dictionary was not valid.

Action: Contact Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-02211: Error encountered while marking document ''{0}'' resulting in document ''{1}''.

Cause: None.

Action: None.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-02301: missing initialization property for key ''{0}''

Cause: A required initialization parameter was missing.

Action: Provide the missing initialization parameter.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-02302: error accessing file ''{0}''

Cause: An I/O error occurred accessing the file repository.

Action: The nested exception specifies the root cause. Investigate and resolve.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-02303: null document

Cause: A null XML Document was supplied.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-02304: ID ''{0}'' is not valid for document creation, modification nor deletion.

Cause: None.

Action: None.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-02305: file path ''{0}'' does not exist

Cause: The specified file repository could not be found.

Action: Verify that the path to the file is correct.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-02306: Marker ''{0}'' is invalid.

Cause: None.

Action: None.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-02307: ID ''{0}'' is not valid for document access.

Cause: An internal ID identifying a document that was part of a rule dictionary was not valid.

Action: Contact Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-02308: Error: Respository file path argument missing.

Cause: A path to the file repository to create was missing.

Action: Supply a valid path.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-02309: Error: ''{0}'' already exists.

Cause: A file at the specified location already exists.

Action: Supply a path to a file that does not already exist.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-02310: Error creating ''{0}'': {1}

Cause: An error occured creating the file repository.

Action: Resolve the source of the error.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-02311: Unable to rename ''{0}'' so that it can be replaced. This can be caused by another rules based application reading the repository at the same time as this attempt to update it. The operation may be retried. If this error persists, then some other application is keeping the repository open.

Cause: An attempt to rename the original repository file so that the new one can be written failed.

Action: Verify that it is not being accessed by another application and then retry.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-02312: Unable to rename updated file ''{0}'' to ''{1}''. The repository update failed. The old repository content is in the file ''{2}''. The updated repository content is in the file ''{0}''. To recover from this error, manually rename the file ''{0}'' to ''{1}''.

Cause: An attempt to rename the new repository file to the correct name failed.

Action: Recover manually by renaming the files as directed in the error message.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-02313: Unable to delete the file ''{0}'' which contains old repository content. It may be deleted manually.

Cause: An attempt to delete the old, renamed repository file failed.

Action: Recover by manually deleting the file as directed in the error message.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-04001: unable to instantiate RuleAdministrator

Cause: An error occurred getting a JSR-94 RuleAdministrator instance.

Action: Verify that jsr94.jar and jsr94_obr.jar are present.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-04002: unable to instantiate RuleRuntime

Cause: An error occurred getting a JSR-94 RuleRuntime instance.

Action: Verify that jsr94.jar and jsr94_obr.jar are present.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-04003: JSR-94 RuleServiceProvider registration failure

Cause: An error occurred registering the Oracle Business Rules JSR-94 RuleServiceProvider.

Action: Verify that jsr94.jar and jsr94_obr.jar are present.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-04004: The creation of a RuleExecutionSet from an abstract syntax tree is not supported.

Cause: An attempt was made to create a RuleExecutionSet with a method that takes an abstract syntax tree. This is not supported.

Action: Create a RuleExecutionSet with a supported method.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-04005: null argument

Cause: A null was passed to an extension to JSR-94 to programmatically create a RuleExecutionSet.

Action: Correct the invocation of the method.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-04006: missing rule execution set URI

Cause: None.

Action: None.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-04007: RuleExecutionSet specification is missing for URI ''{0}''.

Cause: None.

Action: None.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-04008: RuleExecutionSet is registered with URI ''{0}'' already.

Cause: None.

Action: None.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-04009: unable to create an XML DocumentBuilder

Cause: An error occurred getting a DocumentBuilder.

Action: Verify that the XML parser configuration is correct.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-04010: rule execution set name missing

Cause: An XML or programmatic specification of a RuleExecutionSet was missing the name of the RuleExecutionSet.

Action: Supply the missing name.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-04011: missing repository location

Cause: An XML or programmatic specification of a RuleExecutionSet was missing the repository location.

Action: Supply the missing repository location.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-04012: missing dictionary name

Cause: An XML or programmatic specification of a RuleExecutionSet was missing the name of the rule dictionary.

Action: Supply the missing rule dictionary name.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-04013: registration failed for ''{0}''

Cause: None.

Action: None.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-04014: deregistration failed for ''{0}''

Cause: None.

Action: None.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-04015: No RuleExecutionSet is registered under URI ''{0}''.

Cause: An attempt was made to deregister a RuleExectionSet that had not been registered.

Action: Verify that the URI is correct.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-04016: internal error: corrupted document, no registrations

Cause: None.

Action: None.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-04017: internal error: missing registration for ''{0}''

Cause: None.

Action: None.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-04018: Multiple dictionaries were found in the RuleExecutionSet specification. The second dictionary is named ''{0}'' in repository ''{1}''

Cause: An XML or programmatic specification of a RuleExecutionSet contained references to more than one rule dictionary.

Action: Limit the specification to a single rule dictionary.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-04019: missing MDS instance name

Cause: An XML or programmatic specification of a RuleExecutionSet that references a rule dictionary in an MDS repository was missing the name of the MDS instance.

Action: Supply the missing MDS instance name.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05003: The visible fact type \\"{0}\\" should only inherit from one visible fact type, but inherits from visible fact types \\"{1}\\" and \\"{2}\\".

Cause: A visible fact type inherited from more than one visible fact type.

Action: Make one of the fact types not visible.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05004: The file tools.jar containing com.sun.tools.javac.Main cannot be found on the class path. Ensure that it is on the class path.

Cause: The file tools.jar containing com.sun.tools.javac.Main could not be found on the class path.

Action: Add tools.jar to the class path.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05005: The class com.sun.tools.javac.Main does not contain the method \\"invoke\\".

Cause: The class com.sun.tools.javac.Main does not contain the method "invoke"

Action: Verify that your JVM installation is not corrupted.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05006: The fact type \\"{0}\\" has the same alias as an unrelated bucketset.

Cause: A bucketset has the same alias as a fact type, but the fact type or bucketset is not created from importing a Java enum.

Action: Provide different aliases for the fact type or bucketset.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05011: The schema \\"{1}\\" is not on schema path \\"{0}\\".

Cause: The schema root path is set, but the schema that was added is not on this same path. Set the correct schema root path or move the schema to be added.

Action: See the base exception for resolution.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05013: The Java class \\"{0}\\" cannot be added to the data model. Ensure that the class and its associated classes, including parent classes and attribute type classes, are on the current class path.

Cause: The Java class could not be added to the data model.

Action: Ensure that the class and its associated classes, including parent classes and attribute type classes, are on the current class path.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05015: The user path \\"{0}\\" is not a directory or zip file. Ensure that the user path is either a directory, zip file, or JAR file.

Cause: The user path was not a directory or zip file.

Action: Ensure that the user path is either a directory, zip file, or JAR file.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05016: The Java class \\"{0}\\" cannot be loaded. Ensure that the class and all its dependent classes are on either the class path or the user-specified path.

Cause: Could not load Java class.

Action: Ensure that the class and all its dependent classes are either in the class path, or user specified path.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05017: The Java class cannot be loaded. The class name must be valid.

Cause: Could not load Java class.

Action: The class name must be valid.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05018: The Java class \\"{0}\\" cannot be loaded. The class must be inside a package.

Cause: Could not load Java class.

Action: The class must be inside a package.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05019: The Java class \\"{0}\\" cannot be imported. Ensure that the class and its associated classes, including parent classes and attribute type classes, are on the current class path. See the base exception for detail.

Cause: Could not reimport Java class.

Action: Ensure that the class and its associated classes, including parent classes and attribute type classes, are on the current class path. See base exception for detail.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05020: The Java class \\"{0}\\" cannot be loaded. The class name contains RL reserved word \\"{1}\\".

Cause: Could not load Java class. The class name contained an RL reserved word.

Action: Remove the RL reserved word from the class name.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05021: The Java class \\"{0}\\" has a field \\"{1}\\" that is an RL reserved word.

Cause: Java class had a field that is an RL reserved word.

Action: Change the name of the field.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05022: The Java class \\"{0}\\" has a property \\"{1}\\" that is an RL reserved word.

Cause: Java class had a property that is an RL reserved word.

Action: Change the name of the property.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05023: The Java class \\"{0}\\" has a method \\"{1}\\" that is an RL reserved word.

Cause: Java class had a method that is an RL reserved word.

Action: Change the name of the method.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05024: The JAXB output directory is null or an empty string.

Cause: JAXB output directory was null or an empty string.

Action: Use a valid directory.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05025: The JAXB output directory \\"{0}\\" is not a valid directory.

Cause: JAXB output directory was not a valid directory.

Action: Use a valid directory.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05026: The JAXB output directory \\"{0}\\" is not writable.

Cause: JAXB output directory was not writable.

Action: Use a valid directory.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05027: The package name is not a valid Java identifier.

Cause: Package name was not a valid Java identifier.

Action: Provide a package name that is a valid Java identifier.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05028: The XML schema name is null or an empty string.

Cause: XML schema name was null or an empty string.

Action: Provide a valid schema name.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05029: The XML schema \\"{0}\\" does not exist.

Cause: XML schema did not exist.

Action: Provide an XML schema that exists.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05030: The source code generated by \\"{0}\\" in the directory \\"{1}\\" cannot be compiled.

Cause: JAXB generated source code could not be compiled.

Action: Make sure tools.jar is in CLASSPATH.
Level: 1

Type: WARNING

Impact: Programmatic

RUL-05034: A \\"return\\" action is missing. Add a return action or change the function return type to void.

Cause: A return action was missing.

Action: Add a return action or change the function return type to void.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05035: The value to be validated is null.

Cause: The value to be validated was null.

Action: Provide a value that is not null.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05036: The XSL resource named \\"{0}\\" cannot be located on the class path.

Cause: The XSL resource named could not be located on the class path.

Action: Check that the XSL resource name and class path are correct.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05037: A cyclical definition exists in the data model \\"{0}\\" .

Cause: Data model contained cyclical definitions of RL or ADF-BC Fact Types.

Action: Remove cyclical dependencies from the data model. For RL Fact Types, the cycle must be broken by removing properties. For ADF-BC Fact Types, the cycle must be broken by marking properties nonvisible.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05038: The XML schema \\"{0}\\" cannot be added to the data model because JAXB source cannot be generated. See the base exception for resolution.

Cause: The XML schema could not be added into the data model because the JAXB source files could not be generated.

Action: See the base exception for resolution.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05039: The XML schema path \\"{0}\\" cannot be added to the data model. Could not generate JAXB mapping. See the base exception for resolution.

Cause: The XML schema could not be added into the data model because the JAXB mapping could not be generated.

Action: See the base exception for resolution.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05040: The XML schema path \\"{0}\\" cannot be added to the data model because JAXB source cannot be compiled. See the base exception for resolution.

Cause: The XML schema could not be added into the data model because the JAXB source could not be compiled.

Action: See the base exception for resolution.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05041: The XML schema path \\"{0}\\" cannot be added to the data model because the path cannot be added to data model and class loader. See the base exception for resolution.

Cause: The XML schema could not be added into the data model because the schema path could not be added to the data model and class loader.

Action: See the base exception for resolution.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05042: The XML schema \\"{0}\\" does not exist.

Cause: XML schema did not exist.

Action: Provide an XML schema that exists.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05043: The decision function parameter \\"{0}\\" does not uniquely identify an XML element in \\"{1}\\".

Cause: The type of a decision function parameter is an XML fact type that has more than one element of that type in the imported XML schema, and the name of the parameter {0} does not match any of the element names in the schema {1}.

Action: Enter a parameter name that matches the element name you want to use from the XML schema.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05101: The ruleset cannot be serialized to XML. See base exception for resolution.

Cause: Ruleset could not be serialized to XML.

Action: See base exception for resolution.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05102: The XML document cannot be deserialized into a ruleset. See the base exception for resolution.

Cause: XML document could not be deserialized into a ruleset.

Action: See the base exception for resolution.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05103: The ruleset visibility filter cannot be evaluated. Check syntax of dates, times, and numbers.

Cause: Could not evaluate ruleset visibility filter.

Action: Check syntax of dates, times, and numbers.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05130: component does not support property \\"{0}\\"

Cause: Component did not support the property specified.

Action: Do not use this property.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05140: The XML schema \\"{0}\\" could not be mapped to XML fact types. See base exception for detail.

Cause: XML schema could not be mapped to XML fact types.

Action: See base exception for detail.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05148: The ADF-BC View Definition name is null.

Cause: The ADF-BC View Definition name was null.

Action: Specify a valid ADF-BC View Definition name.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05149: exception while attempting to import the ADF-BC View Definition \\"{0}\\"

Cause: An exception occurred while attempting to import the View Definition.

Action: See base exception for detail.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05161: The decision function \\"{0}\\" requires fact type \\"{1}\\", but this type is not part of the input.

Cause: Decision function rule flow checking detected a missing fact type required by the called decision function.

Action: Assert the required fact types before invoking the decision function.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05162: The rule set \\"{0}\\" requires fact type \\"{1}\\", but this type is not part of the input.

Cause: Decision function rule flow checking detected a missing fact type required by the called ruleset.

Action: Assert the required fact types before invoking the ruleset.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05163: The fact type \\"{0}\\" is not used in any ruleset called by this decision function.

Cause: Decision function rule flow checking detected an unused fact type.

Action: Reference all asserted fact types in a rule condition or decision function output type list.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05164: The fact type \\"{0}\\" is referenced, but is not asserted nor input.

Cause: Decision function rule flow checking detected a fact type that was referenced in a rule condition, a nested decision function input, or the output of this decision function that is not an input to this decision function, nor an output of a called decision function, and is not asserted by a ruleset in this decision function.

Action: Ensure that all fact types in conditions are asserted or input to the decision function.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05165: The decision function \\"{0}\\" has two adjacent entries in the ruleset or decision function table with the name \\"{1}\\".

Cause: The decision function has two adjacent entries in the ruleset / decision function table that have the same name. This is an error, because no rules will fire when the second entry is called.

Action: Remove one of the entries.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05170: unexpected exception

Cause: An unexpected exception occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05171: A RuleDictionary instance or name is required.

Cause: A RuleDictionary instance or name was not supplied.

Action: Provide a RuleDictionary instance or name.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05172: A decision function name is required.

Cause: A decision function name was not supplied.

Action: Provide a decision function name.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05173: A transaction instance is required.

Cause: A transaction instance was not supplied.

Action: Provide a transaction instance.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05174: A valid file name is required.

Cause: The file name was missing or null.

Action: Provide a valid file name.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05175: A decision point name is required.

Cause: A decision point name was missing or null.

Action: Provide a decision point name.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05176: The rule dictionary \\"{0}\\" cannot be found within the current class path.

Cause: The Rule Dictionary {0} could not be found within the current class path.

Action: Change the class path or provide a different rule dictionary.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05177: A fact type named \\"{0}\\" does not exist in the rule dictionary.

Cause: The fact type did not exist in the Rule Dictionary's combined data model.

Action: Provide a fact type name that exists.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05178: A decision function named \\"{0}\\" does not exist in the rule dictionary.

Cause: The decision function was not found within the combined rule dictionary.

Action: Provide a different decision function.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05179: naming exception creating transaction

Cause: A naming exception was thrown when attempting to create a transaction.

Action: Correct the environment configuration.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05180: naming exception when looking up data source

Cause: A naming exception was thrown when attempting to look up the data source.

Action: Correct the environment configuration.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05181: error looking up data source

Cause: An error was encountered looking up the data source.

Action: See the underlying exception.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05182: error interacting with rule session

Cause: An error was encountered interacting with the rule session.

Action: See the underlying exception.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05183: error loading the view object

Cause: An error was encountered loading the view object.

Action: See the underlying error.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05184: error writing decision point dictionary

Cause: An error was encountered writing the decision point dictionary.

Action: See the underlying error.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05185: error loading or creating decision point dictionary

Cause: An error was encountered loading or creating the decision point dictionary.

Action: See the underlying error.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05186: error setting up rule session pool for decision point

Cause: An error was encountered setting up the rule session pool for the decision point.

Action: See the underlying error.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05187: An error was encountered getting a rule session from the decision point rule session pool.

Cause: An error was encountered getting a rule session from the decision point rule session pool.

Action: See the underlying error.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05188: An error was encountered returning a rule session to decision point rule session pool.

Cause: An error was encountered returning a rule session to the decision point rule session pool.

Action: See the underlying error.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05200: The fully qualified dictionary name is not valid for accessing a dictionary. Each component of the name {0} must begin with a letter and consist of letters, digits, or the underscore character.

Cause: The fully qualified dictionary name was not valid for accessing a dictionary.

Action: Change the name so that each component of the name begins with a letter and consist of letters, digits, or the underscore character.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05201: The fully qualified dictionary name is not valid for obtaining a list of dictionary names.

Cause: The fully qualified dictionary name was not valid for obtaining a list of dictionary names.

Action: Use the dictionary's local name.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05202: A repository type must be specified.

Cause: A repository type was not specified.

Action: Specify a repository type.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05203: This repository connection has been closed and can no longer be used to access the repository. A new connection must be established.

Cause: The repository connection was closed and could not be used to access the repository.

Action: Establish a new connection.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05204: A dictionary with name \\"{0}\\" does not exist in repository.

Cause: A dictionary with the given name did not exist in repository.

Action: Provide the name of a dictionary that exists.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05205: A dictionary named \\"{0}\\" already exists in the repository.

Cause: A dictionary with the given name already exists in repository.

Action: Provide a name for the dictionary that does not already exist.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05206: There is an error when initializing the repository. Refer to the base exception.

Cause: There was an error initializing the repository.

Action: Refer to the base exception.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05207: There is a repository error. Refer to the base exception.

Cause: A repository error occurred.

Action: Refer to the base exception.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05208: There is a mismatch between the fully qualified name of the dictionary and the name with which it was retrieved.

Cause: There was a mismatch between the fully qualified name of the dictionary and the name with which it was retrieved.

Action: Ensure that the package and name in the dictionary match the directory structure and rules file name.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05209: The dictionary with name \\"{0}\\" cannot be saved. The dictionary has already been modified and this version is older than the latest version in the repository. Edit the dictionary again to modify the latest version.

Cause: The dictionary could not be saved because the version in the repository was newer than the version being saved.

Action: Edit the dictionary again.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05210: The repository does not support a sandbox feature. Change the application code to test if the sandbox feature is supported and only invoke sandbox operations if it is supported.

Cause: The repository did not support a sandbox feature and a sandbox operation was invoked.

Action: Re-code the application to test if the sandbox feature is supported and only invoke sandbox operations if it is supported.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05211: A sandbox named \\"{0}\\" already exists and as a result sandbox creation failed. Use the existing sandbox or use a different name.

Cause: A sandbox with the supplied name already exists and as a result sandbox creation failed.

Action: Use the existing sandbox or use a different name.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05212: The name of the sandbox is missing. Provide a nonempty sandbox name.

Cause: The sandbox name was missing.

Action: Provide a nonempty sandbox name.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05304: The ruleset with the name \\"{0}\\" was not in the dictionary.

Cause: The ruleset with the name was not in the dictionary.

Action: Provide the name of a ruleset that exists in the dictionary.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05355: The same location is provided for both dictionary \\"{0}\\" and output destination \\"{1}\\". The canonical path is \\"{2}\\".

Cause: The same location was provided for both the dictionary and the output destination.

Action: Check both paths to ensure they are correct.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05356: The dictionary path location \\"{0}\\" does not exist.

Cause: The dictionary path location does not exist.

Action: Provide a path to the dictionary that does exist.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05357: The destination path \\"{0}\\" location cannot be written.

Cause: The output destination location cannot be written.

Action: Provide a destination that is writable.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05400: Another thread updated the in-memory copy of the dictionary. Try your changes again.

Cause: Another thread updated the in-memory copy of the dictionary.

Action: Try your changes again.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05401: The path \\"{0}\\" does not exist. Ensure that the path exists on the host system.

Cause: The path specified did not exist.

Action: Ensure that the path exists on the host system.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05403: The parameter \\"{0}\\" is null. Ensure that the parameter is not null.

Cause: The parameter was null.

Action: Ensure that the parameter is not null.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05534: internal error. Item should be one of \\"{0}\\" but is \\"{1}\\".

Cause: Item was not one of the required values.

Action: Internal error. Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05576: token: \\"{0}\\" at \\"{1}\\" is unterminated

Cause: Token was unterminated.

Action: Terminate token.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05577: Token: \\"{0}\\" at \\"{1}\\" is not a known token.

Cause: Token was not a known token.

Action: Provide a different token.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05578: invalid target of assignment at column \\"{1}\\"

Cause: Target (left hand side of "=") of assignment is not valid.

Action: Provide a nonfinal variable as a target.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05579: Token: \\"{0}\\" at \\"{1}\\" is an invalid number.

Cause: Token was an invalid number.

Action: Provide a valid number.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05580: syntax error for token \\"{0}\\" at column \\"{1}\\"

Cause: Token contained a syntax error.

Action: Correct the syntax error.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05581: Token: \\"{0}\\" at \\"{1}\\" is an unknown parser error.

Cause: Token caused an unknown parser error.

Action: Correct the error in the expression.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05582: Token: \\"{0}\\" at \\"{1}\\" is unmatched.

Cause: Token was unmatched.

Action: Match token.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05583: A primitive type or a fact type is expected, but neither can be found.

Cause: The parser was expecting the name of a type, but none was found.

Action: Select a valid type.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05584: The variable \\"{2}\\" must be final to be used here.

Cause: A nonfinal variable was used in a rule condition.

Action: Mark the variable as final, or do not use the variable here.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05600: The dictionary \\"{0}\\" must have a DictionaryFinder to resolve dictionary links.

Cause: Dictionary did not have a DictionaryFinder to resolve dictionary links.

Action: Provide a DictionaryFinder to resolve dictionary links.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05601: The dictionary cannot be found using link \\"{0}\\".

Cause: The dictionary could not be found using the provided link.

Action: Provide a valid link.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05602: The dictionary link \\"{0}\\" refers to a dictionary with validation warnings.

Cause: Dictionary link referred to a dictionary with validation warnings.

Action: Provide a dictionary link without validation warnings.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05701: The name cannot be blank. Enter a name.

Cause: The name was blank.

Action: Enter a name.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05703: The rule or decision table must have at least one pattern or test. Add a pattern or a test.

Cause: The rule or decision table had no patterns.

Action: Add a pattern.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05704: The pattern must have a valid fact type. Enter a visible non-primitive fact type.

Cause: The pattern did not have a fact type.

Action: Enter a valid fact type.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05706: The pattern variable \\"{0}\\" is used more than once in the same rule. Change one of the names.

Cause: The pattern variable was used more than once in the same rule.

Action: Change one of the names.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05707: The priority must be a predefined value such as 'high' or 'low', or a number.

Cause: Priority was not a predefined value or a number.

Action: Priority must be a predefined value or a number.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05709: The variable \\"{0}\\" is used more than once in the same rule. Change one of the names.

Cause: The variable was used more than once in the same rule.

Action: Change one of the names.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05710: The value chosen, \\"{0}\\", is not a valid choice for \\"{1}\\" of \\"{2}\\".

Cause: The value was not a valid choice.

Action: Enter a valid choice.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05711: The expression cannot be blank.

Cause: The expression was blank.

Action: Enter an expression.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05712: The value \\"{0}\\" of \\"{1}\\" cannot be blank. Select a value.

Cause: The value was blank.

Action: Select a value.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05713: invalid alias \\"{0}\\", must begin with a letter and contain only letters, numbers, \\".\\", \\"-\\", \\"_\\",\\"'\\", \\":\\", \\"/\\", and single spaces

Cause: The element contained an invalid alias.

Action: Must begin with a letter and contain only letters, numbers, ".", "-", "_","'", ":", "/" and single spaces.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05714: invalid name \\"{0}\\", must begin with a letter and contain only letters and numbers

Cause: The element contained an invalid name.

Action: Must begin with a letter and contain only letters and numbers.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05715: The value \\"{0}\\" is excluded by bucketset \\"{1}\\".

Cause: Expression value was excluded by a bucketset.

Action: Choose an allowed value.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05716: The function \\"{0}\\" is not valid here.

Cause: Function was not valid here.

Action: Provide the name of a valid function.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05717: The identifier \\"{0}\\" is not valid here.

Cause: Identifier was not valid here.

Action: Provide a valid identifier.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05720: data type mismatch for test \\"{0}\\": {2} {3} {4}

Cause: There was a data type mismatch for the test.

Action: Provide a different operator or provide different operands.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05721: The result type of the expression is \\"{2}\\" but should be \\"{3}\\".

Cause: The result type of the expression is not as expected.

Action: Provide a different expression, or add a cast to the expression.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05724: The array \\"{0}\\" must be followed by \\"[]\\".

Cause: Array was not followed by [].

Action: Add [] to the end of the array.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05725: The value \\"{0}\\" is not an array and cannot be followed by \\"[]\\".

Cause: The value was not an Array and was not allowed to be followed by [].

Action: Remove the [] from the value.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05726: data type mismatch for operator \\"{0}\\" at position {1}: {2} {3} {4}

Cause: There was a data type mismatch for the operator.

Action: Provide a different operator or provide different operands.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05727: incorrect number of parameters for function \\"{0}\\" at {1}

Cause: There was an incorrect number of parameters for function.

Action: Provide the correct number of parameters for the function.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05728: The test expression must return true or false, not \\"{0}\\".

Cause: Test expression must return true or false but did not.

Action: Provide a test expression that returns true or false.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05729: The value must be a literal value. Strings must be quoted with double quotation marks.

Cause: Value was not a literal value.

Action: Provide a literal value. Strings must be quoted with "".
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05730: type \\"{0}\\" may not be used here

Cause: The provided type was not valid for use.

Action: Provide a valid type.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05731: The nested pattern has an empty nested table. Remove the nested pattern or add nested entries.

Cause: The nested Pattern had an empty NestedTable.

Action: Remove the nested Pattern or add nested entries.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05732: form value not set

Cause: Form value not set.

Action: Set form value.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05733: for a nested SimpleTestTable, incorrect operator \\"{0}\\" selected

Cause: Nested SimpleTestTable had incorrect operator selected.

Action: Select a valid operator.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05735: cannot cast type \\"{2}\\" to type \\"{3}\\"

Cause: Could not cast expression type to cast type.

Action: Provide a valid cast type.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05736: The date \\"{0}\\" is invalid. It must match the selected calendar format \\"{1}\\".

Cause: Date was invalid.

Action: Provide a date that matches the selected calendar format.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05737: The effective start date \\"{0}\\" must be strictly less than the effective end date {1}.

Cause: Effective start date was not strictly less than the effective end date.

Action: Provide an effective start date that is strictly less than the effective end date.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05738: The effective start date \\"{0}\\" must be greater than or equal to the rule set effective start date \\"{1}\\".

Cause: Effective start date was not greater than or equal to the rule set effective start date.

Action: Provide an effective start date that is greater than or equal to the rule set effective start date.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05739: The effective end date \\"{0}\\" must be less than or equal to the rule set effective end date \\"{1}\\".

Cause: Effective end date was not less than or equal to the rule set effective end date.

Action: Provide an effective end date that is less than or equal to the rule set effective end date.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05740: The \\"{0}\\" action does not allow nested actions in its action table. Remove all actions from the nested action table.

Cause: Action table was not empty.

Action: The action table is not empty, but should be. Remove all actions from the action table.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05741: The action contains the wrong number of expressions. Re-create the action. If the problem persists, contact Oracle Support Services.

Cause: The action contained the wrong number of expressions.

Action: Re-create the action. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05742: A calendar form incompatibility detected with forms \\"{0}\\" and \\"{1}\\". If the calendar form is set to \\"Time\\" on a rule set or any of the rules or decision tables within that rule set then the calendar form for that entire rule set is restricted to \\"Time\\".

Cause: Calendar form was incompatible.

Action: If the calendar form is set to "Time" on a rule set or any of the rules or decision tables within that ruleset then the calendar form for that entire rule set is restricted to "Time".
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05743: The Action's ExpressionTable is larger than the number of parameters or properties for the Action's Target. Set the value of removed properties or parameters to the empty string and validate the Action again.

Cause: The action's expression table was larger than the number of parameters or properties for the action's target.

Action: Set the value of removed properties or parameters to the empty string and validate the action again.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05744: The action with form \\"expression\\" and value \\"{0}\\" is not a statement. Change the expression to be an assignment statement or method call.

Cause: The expression action did not contain a statement.

Action: Change the expression to be an assignment statement or method call.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05745: The instanceof expression at column {1} is always false.

Cause: The instanceof expression is always false.

Action: Revise or remove the expression.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05746: The instanceof expression at column {1} is always true.

Cause: The instanceof expression is always true.

Action: Revise or remove the expression.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05747: To use the \\"new\\" operator with property values, fact type \\"{0}\\" at column {1} must have a visible constructor with no arguments.

Cause: The new operator with property values requires a no argument constructor.

Action: Make a no argument constructor for the fact type visible, or use a constructor with arguments rather than property values.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05804: The action \\"assign\\" requires a variable and an expression. Select a variable from the list and enter an expression for its value.

Cause: Action "assign" did not contain a variable and an expression.

Action: Select a variable from the list and enter an expression for its value.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05806: The \\"{0}\\" action requires at least one action in its nested action table. Add a nested action.

Cause: Action table was empty.

Action: Add at least one action to this action's nested action table.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05810: The action \\"modify\\" requires at least one property set.

Cause: Action "modify" did not have at least one property set.

Action: Set at least one property for the Action.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05811: The actions \\"assert\\", \\"retract\\", \\"modify\\", and \\"synchronized\\" require a variable. Select a variable from the list.

Cause: Action type "assert", "retract", "modify", and "synchronized" did not contain a variable.

Action: Select a variable from the list.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05812: A \\"try\\" action must be followed by a \\"catch\\" action or a \\"finally\\" action.

Cause: A "try" action is not followed by a "catch" or "finally" action.

Action: Add a "catch" or "finally" action after the "try" action.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05814: The program set option list contains invalid values for \\"{0}\\".

Cause: Program set option list contained invalid values.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05815: Null values are not allowed for key or value put ( {0}, {1} ).

Cause: Null values were provided for a key or value in call to method put.

Action: Provide a non-null key or value for put.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05817: The property \\"{0}\\" is read-only.

Cause: Property was read-only.

Action: Do not set the value of this read-only property.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05818: The value for property \\"{0}\\" must be of type \\"{1}\\".

Cause: Value for property was of the wrong type.

Action: Provide a value of the correct type for the property.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05819: The value \\"{0}\\" is not a valid property of \\"{1}\\".

Cause: Property specified was not a valid property of the element.

Action: Provide a valid property.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05821: CUSTOM and program set OPTIONS properties cannot be removed

Cause: An attempt was made to remove CUSTOM and program set OPTIONS properties.

Action: Do not attempt to remove these properties.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05822: The property \\"{0}\\" cannot be customized.

Cause: An attempt was made to customize the specified property.

Action: Do not attempt to customize this property.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05823: RuleSet is not valid, so RL generation is not possible.

Cause: Attempt to generate RL failed because RuleSet failed validation.

Action: Correct validation warnings.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05824: Dictionary components cannot be added or removed in customization mode.

Cause: Could not add or remove dictionary components in customization mode.

Action: Turn customization mode off to add or remove components.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05830: The decision table bucketset reference cannot be found.

Cause: Decision table bucket reference was not found.

Action: Provide a valid bucket reference.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05831: Select one or more values for this condition.

Cause: A Decision table condition cell has no valid bucket reference.

Action: Provide one or more valid bucket aliases for the values of the condition cell.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05832: The bucket name \\"{0}\\" is invalid.

Cause: Bucket name was invalid.

Action: Provide a valid bucket name.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05833: The bucket value contains invalid characters \\"{0}\\".

Cause: Bucket name contained invalid characters.

Action: Remove invalid characters in bucket name.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05834: The last bucket in the bucketset cannot be removed.

Cause: Could not remove the last bucket in a bucketset.

Action: Do not attempt to remove the last bucket in the bucketset.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05835: No buckets selected for condition \\"{0}\\". Select one or more buckets in one or more condition cells.

Cause: All rules had "don't care" set about condition.

Action: Select one or more buckets in one or more condition cells.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05836: The bucketset \\"{0}\\" has only one bucket. Add one or more buckets.

Cause: Bucketset had only one bucket.

Action: Add one or more buckets.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05837: The decision table has no conditions or rules.

Cause: Decision table had no conditions or rules.

Action: Add a condition or rule to the decision table.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05838: The decision table has no actions.

Cause: Decision table had no actions.

Action: Add an action to the decision table.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05839: The bucketset \\"{0}\\" has duplicate otherwise bucket named \\"{1}\\". Delete one of the otherwise buckets.

Cause: Bucketset had duplicate otherwise bucket.

Action: Delete one of the otherwise buckets.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05840: The decision table rule cannot reference rule \\"{0}\\" in both NO CONFLICT and RUN BEFORE lists.

Cause: Decision table rule referenced a rule in both NO CONFLICT and RUN BEFORE lists.

Action: Remove the decision table rule from one of NO CONFLICT and RUN BEFORE lists.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05841: The decision table rule cannot reference rule \\"{0}\\" in both NO CONFLICT and OVERRIDE lists.

Cause: Decision table rule referenced rule in both NO CONFLICT and OVERRIDE lists.

Action: Remove the decision table rule from one of NO CONFLICT and OVERRIDE lists.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05842: The decision table rule cannot reference rule \\"{0}\\" in both OVERRIDE and RUN BEFORE lists.

Cause: Decision table rule referenced rule in both OVERRIDE and RUN BEFORE lists.

Action: Remove the decision table rule from one of OVERRIDE and RUN BEFORE lists.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05843: The decision table rule cannot specify OVERRIDE or RUN BEFORE on itself.

Cause: Decision table rule cannot specify OVERRIDE or RUN BEFORE on itself.

Action: Select a different option.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05846: The bucketset must have a primitive or Calendar data type.

Cause: Bucketset did not have a primitive or Calendar data type.

Action: Provide a primitive or Calendar data type for the bucketset.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05847: The decision table action parameter \\"{0}\\" is a duplicate.

Cause: Decision table contained duplicate action parameter.

Action: Remove one of the duplicate decision table action parameters.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05848: In a decision table, an \\"assign new\\" action must be \\"always selected\\".

Cause: A decision table "assign new" action was not always selected.

Action: Select a decision table "assign new" action.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05849: The bucketset has duplicate bucket value \\"{0}\\".

Cause: Bucketset had a duplicate bucket value.

Action: Delete the duplicate bucket or choose another bucket value.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05850: The condition \\"{0}\\" has type \\"{1}\\", but has bucketset of type \\"{2}\\".

Cause: Condition expression's type was incompatible with its bucketset type.

Action: Associate a different bucketset with the condition expression.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05851: The decision table has unresolved conflicts.

Cause: The decision table had unresolved conflicts.

Action: Display the conflicts and mark each with "override", "run before", or "ignore".
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05852: The decision table has gaps.

Cause: The decision table had gaps.

Action: Display the gaps and add rules as needed, or check "allow gaps".
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05853: Bucket value contains invalid character \\"{0}\\".

Cause: Bucket value contained invalid char value.

Action: Provide a valid char value for bucket value.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05854: The bucket value must be a constant expression.

Cause: The bucket expression was not constant.

Action: Set the "constant" property of the bucket expression to "true".
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05855: The rules \\"{0}\\" and \\"{1}\\" do not conflict. Remove override information.

Cause: There was no conflict between decision table rules.

Action: Remove the override information.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05856: The parent object of type \\"{0}\\" with name \\"{1}\\" has more than one \\"{2}\\" with value \\"{3}\\".

Cause: Two elements had the same name.

Action: Provide a different name for one of the elements.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05895: while validating \\"{0}\\", found {1} error(s)

Cause: Data model element contained validation errors.

Action: Correct the errors.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05899: The primitive fact type \\"{0}\\" cannot be deleted.

Cause: An attempt was made to delete a primitive fact type.

Action: Do not attempt to delete primitive fact types.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05902: The built-in function \\"{0}\\" cannot be deleted.

Cause: An attempt was made to delete a built-in function.

Action: Do not attempt to delete the built-in function.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05905: The element \\"{0}\\" cannot be deleted.

Cause: An attempt was made to delete an element.

Action: Do not attempt to delete the element.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05906: A Java property cannot be deleted.

Cause: An attempt was made to delete a Java property.

Action: Do not attempt to delete Java properties.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05916: The name \\"{0}\\" is an RL reserved word.

Cause: An RL reserved word was provided as the name.

Action: Provide a different name that is not a reserved word.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05918: The function \\"{0}\\" has both a body and actions defined. Only one of these should be defined.

Cause: Function had both a body and actions defined.

Action: Remove either the body or the defined actions.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05919: The body of function \\"{0}\\" has to be defined.

Cause: Body of function was empty.

Action: Define the body of the function.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05920: The parent object of type \\"{0}\\" with name \\"{1}\\" has more than one \\"{2}\\" with name \\"{3}\\".

Cause: Two elements had the same name.

Action: Provide a different name for one of the elements.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05921: The parent object of type \\"{0}\\" with name \\"{1}\\" has more than one \\"{2}\\" with alias \\"{3}\\".

Cause: Two elements had the same alias.

Action: Provide a different alias for one of the elements.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05922: Linked dictionaries cannot have the same alias \\"{0}\\".

Cause: Two linked dictionaries had the same alias.

Action: Change the alias for one of the linked dictionaries.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05923: Linked dictionaries cannot have the same fully qualified name \\"{0}\\".

Cause: Two linked dictionaries had the same fully qualified name.

Action: Change the name of one of the linked dictionaries.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05924: The alias \\"{0}\\" cannot start with a space.

Cause: Alias started with a space.

Action: Change the alias so that it does not start with a space.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05925: The alias \\"{0}\\" cannot end with a space.

Cause: Alias ended with a space.

Action: Change the alias so that it does not end in a space.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05926: The alias \\"{0}\\" contains a double space or invalid character.

Cause: Alias contained a double space or invalid character.

Action: Change the alias so that it does not contain a double space or invalid character.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05927: The alias cannot be blank.

Cause: Alias was blank.

Action: Provide an alias.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05940: The value of global variable \\"{0}\\" is not set.

Cause: The value of the global variable was not set.

Action: Set the value of the global variable.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05942: The element \\"{0}\\" \\"{1}\\" must have a type.

Cause: Element did not have a type.

Action: Provide a type.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05943: The file corresponding to the path \\"{0}\\" does not exist. Ensure that the file exists in the file system.

Cause: File corresponding to the path did not exist.

Action: Ensure that the file exists in the file system.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05945: initialization of built-in data model failed

Cause: Initialization of built-in data model failed.

Action: If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05946: The class not found while initializing built-in data model. Ensure that rl.jar is on the class path.

Cause: The class was not found while initializing built-in data model.

Action: Ensure that rl.jar is on the class path.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05959: The result type of \\"{0}\\" cannot be aggregated.

Cause: Invalid result type for aggregate expression.

Action: The result type for minimum and maximum must be a primitive or Comparable type. The result type for sum and average must be a primitive numeric type.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05960: An aggregate pattern block must contain one pattern.

Cause: An aggregate pattern block has no patterns or more than one pattern.

Action: Add or remove patterns from the aggregate pattern block as needed.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05961: The pattern in the aggregate has operator \\"{0}\\" and form \\"{1}\\", should have operator OPERATOR_FOREACH and form FORM_FACT_TYPE.

Cause: The pattern in the aggregate had invalid operator and form combination.

Action: The pattern should use operator OPERATOR_FOREACH and form FORM_FACT_TYPE.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05962: The aggregate table does not contain an aggregate.

Cause: Aggregate table did not contain an aggregate.

Action: Provide an aggregate for the aggregate table.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05963: The aggregate variable \\"{0}\\" is used more than once. Change one of the names.

Cause: The aggregate variable was used more than once.

Action: Change one of the aggregate variable names.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05964: The aggregate must have an aggregate function. Specify a valid aggregate function.

Cause: The aggregate did not specify an aggregate function.

Action: Specify a valid aggregate function.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05965: The aggregate function \\"{0}\\" does not exist or does not implement oracle.rules.rl.Aggregate.

Cause: The specified aggregate function did not exist or did not implement orace.rules.rl.Aggregate.

Action: Provide a valid aggregate function.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05966: The aggregate must have a variable set. Enter a variable.

Cause: The aggregate did not have a variable set.

Action: Specify a variable for the aggregate.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05967: The aggregate variable cannot contain a double space.

Cause: Aggregate variable contained a double space.

Action: Provide an aggregate variable that does not contain a double space.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05968: The aggregate function count does not require an expression.

Cause: Aggregate function count did not require an expression.

Action: Remove the expression set for the count function expression.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-05969: cannot parse dictionary XML source

Cause: Dictionary source was not valid XML.

Action: Provide a valid XML dictionary.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-08000: No registration exists for \\"{0}\\"

Cause: No RepositoryConnection implementation was available for the specified key.

Action: Verify that the key is correct and that the corresponding RepositoryConnection was successfully registered.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-08001: invalid or missing registration

Cause: A RepositoryConnection registration was null or one of its properties was null (not specified).

Action: Verify that the key is correct and that the corresponding RepositoryConnection was successfully registered.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-08002: unable to load repository store add-in class \\"{0}\\", the store is unavailable.

Cause: An error was encountered in loading the specified RepositoryConnection implementation class.

Action: Verify that the class is available on the class path.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-08003: repository connection factory initialization failure

Cause: An error was encountered initializing the RepositoryConnection factory.

Action: Investigate the exception that was logged.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-08201: missing initialization property for key \\"{0}\\"

Cause: A required initialization parameter was missing.

Action: Provide the missing initialization parameter.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-08202: error accessing file \\"{0}\\"

Cause: An I/O error occurred accessing the file repository.

Action: The nested exception specifies the root cause. Investigate and resolve.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-08203: null document

Cause: A null XML Document was supplied.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-08204: File \\"{0}\\" does not exist.

Cause: The specified file repository could not be found.

Action: Verify that the path to the file is correct.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-08205: unable to rename \\"{0}\\" so that it can be replaced. This can be caused by another rules based application reading the repository at the same time as this attempt to update it. The operation may be retried. If this error persists, then some other application is keeping the repository open.

Cause: An attempt to rename the original repository file so that the new one can be written failed.

Action: Verify that it is not being accessed by another application and then retry.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-08206: unable to rename updated file \\"{0}\\" to \\"{1}\\". The repository update failed. The old repository content is in the file \\"{2}\\". The updated repository content is in the file \\"{0}\\". To recover from this error, manually rename the file \\"{0}\\" to \\"{1}\\".

Cause: An attempt to rename the new repository file to the correct name failed.

Action: Recover manually by renaming the files as directed in the error message.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-08207: unable to delete the file \\"{0}\\" which contains old repository content, it may be deleted manually

Cause: An attempt to delete the old, renamed repository file failed.

Action: Recover by manually deleting the file as directed in the error message.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-08220: error: respository file path argument missing

Cause: A path to the file repository to create was missing.

Action: Supply a valid path.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-08221: error: \\"{0}\\" already exists

Cause: A file at the specified location already exists.

Action: Supply a path to a file that does not already exist.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-08222: error creating \\"{0}\\": {1}

Cause: An error occured creating the file repository.

Action: Resolve the source of the error.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-08300: The required MDS instance name was not been specified.

Cause: The MDS instance name was not provided.

Action: Provide the MDS instance name.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-08301: More than one MDS configuration specifier was provided. Only one of a file path, a configuration URL, or an MDSSession instance can be provided. Correct by removing all but one of these.

Cause: Conflicting MDS configuration data was provided.

Action: Resolve the conflicts.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-08302: An MDS instance with name \\"{0}\\" did not exist. Either correct the MDS instance name or supply either the MDS file repository path or the MDS configuration URL.

Cause: An MDS instance with the supplied name did not exist.

Action: Supply a name of an existing MDS instance.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-08303: no dictionary supplied

Cause: A null rule dictionary XML document was supplied.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

RUL-08304: The MDS file repository path was not a string.

Cause: The path to the file-based MDS repository was not a string.

Action: Provide a valid file path.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-08305: The MDS configuration URL was not a string.

Cause: The URL to an MDS configuration file was not a string.

Action: Provide a URL.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-08306: The MDS session was not an instance of MDSSession.

Cause: The object passed as an MDSSession to use was not an instance of MDSSession.

Action: Provide a valid instance of MDSSession.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-08307: The MDS instance did not have persistence layer configured.

Cause: The MDSInstance did not have a persistence layer configured.

Action: Check that MDS is configured correctly in the application.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-08308: The MDS configuration did not contain a namespace that included the expected path \\"{0}\\".

Cause: The MDS configuration did not contain a namespace mapping that included the expected path.

Action: Check that MDS is configured correctly in the application.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-08309: The search path was not a list of strings. It was \\"{0}\\".

Cause: The search path was not a list of strings.

Action: Provide a list of strings in the search path initialization parameter.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-08310: An attempt was made to create, delete, or modify a rule dictionary in a repository connection that was configured such that only read access is supported.

Cause: An attempt was made to create, delete, or modify a : rule dictionary in a repository connection that was : configured such that only read access is supported.

Action: Use a repository connection that supports updates.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-09002: failed to execute RL code generated from dictionary: {0}

Cause: The RL code generated from the dictionary failed to execute.

Action: See base exception.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-09003: element is null: parentType0={0} , key0= {1} , valFrom0= {2} , to= + {3}

Cause: A method in the SDK returned null.

Action: None.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-09004: could not retrieve RuleComponent advanced expression

Cause: Problem retrieving advanced expression RuleComponent.

Action: None.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-09005: failed to connect to origin repository for location {0} , root cause: {1}

Cause: Failed to connect to origin repository.

Action: See base exception.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-09006: failed to connect to origin dictionary, name {0} version {1} , root cause: {2}

Cause: Failed to open origin dictionary.

Action: See base exception.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-09007: failed to close to origin repository, root cause: {0}

Cause: Failed to close to origin repository.

Action: See base exception.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-09008: failed to saveAs resulting dictionary, package: {0} dictionary: {1}

Cause: Failed to saveAs migrated dictionary.

Action: Check input parameters and source dictionary for validitiy.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-09009: destination directory {0} could not be created

Cause: Failed to connect to destination repository.

Action: See base exception.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-09010: dictionary: {0}::{1} already exists, failed

Cause: Dictionary indicated already exists.

Action: Remove the existing dictionary or provide a different name.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-09011: failed to create destination dictionary {0} {1} because {2}

Cause: Failed to create destination dictionary.

Action: See base exception.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-09012: failed to load ruleset {0} from origin dictionary, root cause: {1}

Cause: Failed to load ruleset.

Action: See base exception.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-09013: The origin and destinations are not set.

Cause: The origin and destinations are not set.

Action: Set both the origin and destination locations.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-09014: Classpath and XML schema properties are not set

Cause: Classpath and XML schema properties are not set.

Action: Specify the classpath and XML schema properties.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-09015: unable to convert pattern operator: {0}

Cause: The pattern operator was unable to be migrated.

Action: Check the origin dictionary for validity.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-09016: Key {0} is not valid for SDK2 so skipping, message is: {1}.

Cause: The key was not a valid key for SDK2.

Action: None necessary. Some properties in SDK are not valid in SDK2.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-09017: key in ruleset processing: {0} is a {1} parent is a {2}

Cause: The value of a key in the dictionary was not of the correct type.

Action: Check source dictionary for validity.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-09018: missing arguments for WebDav: must supply either Oracle Wallet source or WebDAV name and password

Cause: Missing arguments for WebDav.

Action: Supply either Oracle Wallet source or WebDAV name and password.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-09019: missing arguments for WebDav proxy, must supply a host, a port, and either a Oracle Wallet source or proxy name and password

Cause: Missing arguments for WebDav proxy.

Action: Supply the proxy access values.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-09020: error: to= {0} , from= {1} , fromparent= {2}

Cause: RuleComponent or DictionaryComponent were null.

Action: None.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-09021: errors ({0}) in conversion: {1}

Cause: There were errors in the conversion.

Action: See base exception.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-09022: failed to get RuleSet, internal error: {0}

Cause: The migration failed to retrieve the indicated rule set.

Action: Check that the ruleset exists. Also see base exception.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-09023: Destination ExpressionTable is smaller than origin for target {0} : {1} > {2}

Cause: ExpressionTable is the wrong size.

Action: None.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-09024: invalid PROP_FORM value: {0}

Cause: Form value was invalid.

Action: Check the validity of the origin dictionary.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-09025: Constraint {0} was not migrated, regular expression constraint does not have an equivalent component in SDK2.

Cause: Source dictionary contained a regular expression constraint.

Action: None. Regular expression constraints do not have an equivalent structure in SDK2.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-09026: Value {0} could not be added to bucketset {1}.

Cause: The value was invalid to add to the bucketset.

Action: Ensure that the value is valid or add it manually after migration.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-09030: Number of {0} : {1}

Cause: None.

Action: None.
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RUL-09033: destination written, dictionary: {0} in package: {1}

Cause: None.

Action: None.
Level: 1

Type: NOTIFICATION

Impact: Programmatic

RUL-09034: Origin and destination repositories may not be the same.

Cause: The Origin and Destination Repositories were the same.

Action: Provide different repositories for the origin and destination.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-09035: no origin repository connection, open an origin repository

Cause: No origin repository connection.

Action: Open an origin repository.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-09036: origin dictionary not set, open an origin dictionary.

Cause: Origin dictionary was not set.

Action: Set the origin dictionary.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-09037: Destination dictionary not set, open a destination dictionary.

Cause: Destination dictionary not set.

Action: Set the destination dictionary.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-09038: The {0} property has not been set, set this property.

Cause: Property indicated was not set.

Action: Set the indicated property.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-09039: The element {0} has been set to an invalid value {1}.

Cause: The element indicated was set to an invalid value.

Action: Set a valid value for the element.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-09040: Destination dictionary name and destination package must be null or MIGRATE_ALL when origin dictionary is MIGRATE_ALL.

Cause: Destination dictionary name and destination package was not null or MIGRATE_ALL.

Action: Set the value to null or MIGRATE_ALL.
Level: 1

Type: ERROR

Impact: Programmatic

RUL-09043: An exception occurred {0}, check root exception.

Cause: An exception occurred.

Action: See base exception.
Level: 1

Type: ERROR

Impact: Programmatic

85 SDF-10001 to SDF-10601

SDF-10001: Object missing from tree :

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

SDF-10201: Error instantiating application module

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

SDF-10401: Exception during Extract

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

SDF-10601: An error has occured

Cause: TODO

Action: TODO
Level: 1

Type: ERROR

Impact: Application Diagnostics

86 SDP-25001 to SDP-26455

SDP-25001: An unexpected exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25002: Unable to create JNDI Context

Cause: An exception has occurred.

Action: Check the stack trace for more details. Check the JNDI Context initialization parameters.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25003: Unable to create an instance of Driver Locator

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25005: Failed to create Sending Core instance

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25006: Failed to remove an EJB instance

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25007: An error occurred while processing an outbound message.

Cause: The outbound JMS message does not contain a valid message or request information.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25008: An unexpected error occurred while processing an outbound message.

Cause: An unexpected exception has occurred while processing the outbound message.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25009: An error occurred while storing a message.

Cause: An unexpected exception has occurred while processing the message.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-25010: An error occurred while sending an outbound message.

Cause: An unexpected exception has occurred while processing the outbound message.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25011: An error occurred while transforming an outbound message.

Cause: An unexpected exception has occurred while processing the outbound message.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25012: An error occurred while processing error statuses.

Cause: An unexpected exception has occurred while processing error statuses.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25015: There are no transformed messages of message {0} for recipients {1}. Skipping message delivery to these recipients.

Cause: An unexpected exception has occurred while transforming an outbound message.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25020: Unable to schedule a timed failover event

Cause: An unexpected exception has occurred while scheduling a timed failover event.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25021: An error occurred while processing a timed failover event

Cause: An unexpected exception has occurred while processing a timed failover event.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25030: Unable to schedule a timer to refresh the driver locator cache.

Cause: An unexpected exception has occurred while scheduling a timer to refresh the driver cache.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Configuration

SDP-25031: Unable to refresh the driver locator cache.

Cause: An unexpected exception has occurred while refreshing the driver locator cache.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Configuration

SDP-25032: An error occurred while registering driver information {0}.

Cause: An unexpected exception has occurred while registering the driver information.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Configuration

SDP-25033: An error occurred while unregistering driver information {0}.

Cause: An unexpected exception has occurred while unregistering the driver information.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Configuration

SDP-25034: There are total {0} registered User Messaging Drivers. Driver(s): {1}

Cause: A Messaging Driver registered with the Messaging Server

Action: None
Level: 1

Type: NOTIFICATION

Impact: Configuration

SDP-25035: Messaging store not found.

Cause: An unexpected exception has occurred while attempting to find the messaging store.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25037: Error while retrieving configuration property: {0}.

Cause: Unable to read from the messaging server configuration file 'configuration/appconfig.xml' or the named property does not exist.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Configuration

SDP-25038: Error while loading the messaging server configuration properties. Falling back to default configuration.

Cause: Unable to read from the messaging server configuration file 'configuration/appconfig.xml'.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Configuration

SDP-25040: Unable to create an instance of CommandReceiverBean.

Cause: An unexpected exception has occurred while attempting to process a command.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25041: Received driver registration command message: {0}.

Cause: A driver sent its registration information to this engine.

Action: None
Level: 1

Type: TRACE

Impact: Configuration

SDP-25042: An error occurred while processing a command message.

Cause: An unexpected exception has occurred while attempting to process a command.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Configuration

SDP-25043: An unknown command message was received, ignoring: {0}.

Cause: The engine received an unknown command message and was unable to process the command.

Action: Check the current log file for additional details, if the system is not functional. Otherwise, ignore this warning.
Level: 1

Type: WARNING

Impact: Configuration

SDP-25044: Received driver unregistration command message: {0}.

Cause: A driver was undeployed and it sent an unregistration command to the engine.

Action: None
Level: 1

Type: TRACE

Impact: Configuration

SDP-25055: Failed to create Receiving Core instance.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25057: An error occurred while processing an inbound message.

Cause: The inbound JMS message does not contain a valid message.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25058: An unexpected error occurred while processing an inbound message.

Cause: An unexpected exception has occurred while processing the inbound message.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25059: An unknown JMS message is received, ignoring: {0}.

Cause: The engine received an unknown JMS message and was unable to process it.

Action: Check the current log file for additional details, if the system is not functional. Otherwise, ignore this warning.
Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-25060: There is no application that has registered this address as an access point. Message will not be delivered.

Cause: There is no application that has registered this recipient address as an access point.

Action: Check the current log file for additional details, if the system is not functional. Otherwise, ignore this warning.
Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-25061: An unexpected error occurred while processing inbound message statuses.

Cause: An unexpected exception has occurred while attempting to process inbound message statuses.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25062: Cannot correlate status with any message; storing for possible later processing.

Cause: An inbound status arrived in an unexpected order.

Action: Check the current log file for additional details, if the system is not functional. Otherwise, ignore this warning.
Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-25063: There is no application client information for this status: {0}

Cause: There is no application client information associated with this access point holder.

Action: Check the current log file for additional details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25064: An unexpected error occurred while recording a status processing update.

Cause: An unexpected exception has occurred while attempting to record a status processing update.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25065: An unexpected error occurred while sending a message to failover address {0}.

Cause: An exception has occurred while sending out a failover message.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25066: An unexpected error occurred while processing an outbound message status.

Cause: An unexpected exception has occurred while attempting to process an outbound message status.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25070: Unable to retrieve messaging engine sending and/or receiving queues from configuration.

Cause: A severe configuration error has occurred and the system is not functional.

Action: Check the messaging engine configuration and the stack trace, if available, for more details.
Level: 1

Type: ERROR

Impact: Configuration

SDP-25080: An error occurred while converting a message.

Cause: An invalid message content or inappropriate converter was used to perform the message conversion.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25081: An error occurred while adding a message converter rule: {0}

Cause: An invalid message converter rule was provided.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25082: No predicates and/or devices matched. Ignoring converter rule (MIME type: {0}, delivery type: {1}, predicate: {2}).

Cause: An invalid message converter rule was provided.

Action: Check the current log file for additional details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25083: Message content is not an instance of MimeMultipart

Cause: An invalid message content was provided to this converter.

Action: Check the current log file for additional details. Check User Messaging Service Javadoc on OTN for more information on sending MimeMultipart messages.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25084: Could not lookup physical device {0} for recipient {1}

Cause: An invalid recipient was provided or there is no device mapping for this recipient.

Action: Check the current log file for additional details. Send the message with a valid recipient.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25085: Message {0} has a nonunique Message ID or recipient, and does not look like a redelivery attempt.

Cause: A message was sent or received that appears to be a duplicate of an already processed message; re-enqueuing message with delay specified.

Action: Ensure that messages are assigned unique Message IDs.
Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-25086: Retrying delivery of message {0}

Cause: Previous attempt to deliver message failed. Retrying.

Action: None.
Level: 1

Type: TRACE

Impact: Requests/Responses

SDP-25087: Message {0} is marked for retry but has already been delivered.

Cause: A message was marked for retry by JMS but has already been delivered; dropping message.

Action: None.
Level: 1

Type: TRACE

Impact: Requests/Responses

SDP-25088: Unable to refresh the driver locator cache, due to the following error: {0}

Cause: An unexpected error has occurred while refreshing the driver locator cache.

Action: Check the reported error message and correct any configuration problems.
Level: 1

Type: ERROR

Impact: Configuration

SDP-25100: An unexpected exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25101: Caught an unexpected database exception.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Data

SDP-25102: TopLink database platform class {0} not found. Using default database platform.

Cause: No TopLink database platform class is available with the configured name.

Action: Add new or update existing <DatabasePlatform> with a valid TopLink database platform class in usermessagingserver/configuration/appconfig.xml.
Level: 1

Type: WARNING

Impact: Configuration

SDP-25103: Could not instantiate TopLink database platform class.

Cause: An exception has occurred while instantiating the TopLink database platform class.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Configuration

SDP-25104: Initializing Messaging Store in transient mode.

Cause: Initializing Messaging Store in transient mode. Message history will not persist across server restarts.

Action: n/a
Level: 1

Type: NOTIFICATION

Impact: Configuration

SDP-25105: Initializing Messaging Store in {0} mode.

Cause: Initializing Messaging Store in persistent mode. Message history will persist across server restarts.

Action: n/a
Level: 1

Type: NOTIFICATION

Impact: Configuration

SDP-25106: Conflicting recipient IDs for Message {0}.

Cause: A conflict between recipient identifiers has been detected.

Action: Ensure that applications are using unique Message IDs.
Level: 1

Type: WARNING

Impact: Programmatic

SDP-25107: Message ID {0} in Status object does not match previously recorded Message ID {1}.

Cause: A status object returned from a driver contained a different Message ID than expected.

Action: Ensure that drivers are mapping Gateway IDs to Message IDs correctly.
Level: 1

Type: WARNING

Impact: Data

SDP-25108: One or more addresses from Access Point {0} is already registered by another application.

Cause: An access point address can only be registered by one application at a time.

Action: Resolve the conflict among applications.
Level: 1

Type: TRACE

Impact: Requests/Responses

SDP-25109: Could not initialize persistence context.

Cause: An exception has occurred while initializing the persistence context.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Configuration

SDP-25110: An error occurred while initializing persistence session, with the following error message: {0}

Cause: An error occurred while attempting to initialize and log in to the TopLink persistence session.

Action: Check the reported error message and correct any configuration or database availability problems.
Level: 1

Type: WARNING

Impact: Session

SDP-25111: An error occurred while initializing persistence session, with the following exception stack trace:

Cause: An exception occurred while attempting to initialize and log in to the TopLink persistence session.

Action: Check the reported exception message and correct any configuration or database availability problems.
Level: 1

Type: TRACE

Impact: Session

SDP-25200: An unexpected exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25201: No endpoint URL is available for the web service callback operation.

Cause: No endpoint URL is available for the web service listener callback.

Action: Ensure a valid callback URL is specified when registering a message or status listener.
Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-25250: An unexpected exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25251: Messaging Exception while processing Parlay X request.

Cause: A Messaging Exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-25252: Exception while initializing Parlay X Messaging servlet.

Cause: An exception occurred while initializing the Parlay X Messaging servlet.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Deployment

SDP-25253: Exception while initializing Parlay X Messaging content servlet.

Cause: An exception occurred while initializing the Parlay X Messaging content servlet.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Deployment

SDP-25254: Exception while processing SOAP attachment content.

Cause: An exception occurred while processing message content in a SOAP attachment.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-25255: Message contains multiple attachments. All but first attachment will be ignored.

Cause: The client application sent a message with multiple attachment parts.

Action: Client applications should send one attachment part per message. Complex content should be sent as a MIME Multipart object.
Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-25256: Permission denied.

Cause: The client application did not have permission to invoke the attempted operation.

Action: Check the stack trace for more details.
Level: 1

Type: TRACE

Impact: Security

SDP-25257: Error initializing JAXP DatatypeFactory. Some data types may not be converted correctly.

Cause: Could not acquire instance of class javax.xml.datatype.DatatypeFactory. Marshalling/unmarshalling of some XML elements may not happen correctly.

Action: Ensure that the server's JAXP framework is configured correctly.
Level: 1

Type: WARNING

Impact: Configuration

SDP-25258: Error initializing the Servlet Endpoint Context. Parlay X module will not be able to service requests correctly.

Cause: Could not initialize the Servlet Endpoint Context.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25259: Error initializing access to Messaging Server. Parlay X module will not be able to service requests correctly.

Cause: Could not initialize internal Messaging Client endpoint.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25300: An unexpected exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25301: JNDI context is null.

Cause: JNDI context was null.

Action: See the Javadoc on Oracle Technology Network (OTN) for more information about how to instantiate a JNDI context.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25302: EJB home for UserPrefsService is null.

Cause: EJB home for UserPrefsService is null.

Action: See the Javadoc on Oracle Technology Network (OTN) for more information about how to specify an EJB home.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25303: Unable to connect to User Messaging Service (UMS) server at {0}.

Cause: EJB Naming Exception was caught when creating a UserPrefsServices object.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25304: EJB Remote Exception was caught at server {0}

Cause: EJB Remote Exception was caught.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25305: EJB Create Exception was caught at server {0}

Cause: EJB Create Exception was caught.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25306: XML Document object is null.

Cause: XML Document object is null.

Action: Specify a valid XML document object.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25307: No file to upload. File name is not set.

Cause: The file name to be uploaded was not set.

Action: Invoke setFileName() to set the file name.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25308: The file, {0}, cannot be read.

Cause: The file cannot be read.

Action: Check the file.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25309: File not found: {0}

Cause: The file with the given file name does not exist.

Action: Check to see if the path and file name are correct. File name must be in /path/filename or file://path/filename format.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25310: The URL is malformed: {0}

Cause: The URL is malformed.

Action: The URL must be in file://path/filename format.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25311: The document cannot be uploaded. Parser and stack are out of sync. Tag name: {0} Local name: {1}

Cause: The document cannot be uploaded because parser and stack were out of sync.

Action: Fix mismatched tags.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25312: Provisioning Exception was caught.

Cause: Provisioning Exception was caught.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25313: Null Pointer Exception was caught.

Cause: Null Pointer Exception was caught.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25314: Rule {0} is already defined.

Cause: Rule with the same name was already defined.

Action: Choose a different rule name to avoid conflict.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25316: Input parameter, UserPrefsServices, is null.

Cause: The UserPrefsServices object was null.

Action: Pass a valid UserPrefsServices object as a parameter. Check User Messaging Service Javadoc on OTN for more information.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25317: Required input parameter, UserID, is null.

Cause: Failed to invoke method, because required input parameter, UserID, is null.

Action: Pass a valid UserID. Check User Messaging Service Javadoc on OTN for more information.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25318: Invalid input parameter. DeviceAddress object is null.

Cause: Input parameter, DeviceAddress object, is null.

Action: Pass a valid DeviceAddress object. Check User Messaging Service Javadoc on OTN for more information.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25319: UserRuleSet is not set. Call initProcessor() first.

Cause: UserRuleSet object is null.

Action: Call initProcessor() first to complete initialization.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25320: Rule Set is null.

Cause: The Rule Set was not available or could not be created.

Action: Use a valid Rule Set.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25321: XML String representing the Rule Set is null.

Cause: The XML document element representing the Rule Set was null or empty.

Action: Use a valid Rule Set XML element.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25322: User Rule Set is null.

Cause: The User Rule Set was not available or could not be created.

Action: Use a valid User Rule Set object.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25323: User Rule Set is inconsistent. See exception for more details.

Cause: User Rule Set is inconsistent.

Action: Check User Rule Set for consistency.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25324: XML document is invalid. See exception for details.

Cause: XML document is invalid. See stacktrace for more details.

Action: Validate the XML document.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25325: Cannot serialize Rule Session.

Cause: Cannot serialize Rule Session, which is not critical.

Action: No action needed.
Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-25326: Filter XML is null.

Cause: The Preference Rules were missing or inconsistent.

Action: Use a well-formed User Preference XML document.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25327: Cannot create Rule Session.

Cause: Cannot create Rule Session.

Action: No action needed.
Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-25328: UserPrefsException was caught.

Cause: UserPrefsException was caught.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-25329: Rule {0} does not exist.

Cause: The expected rule was not found.

Action: Check the rule by name on the User Preference page.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25330: Business Term Type has changed.

Cause: Business Term Type has changed.

Action: Recheck the Preference Rules.
Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-25331: Cannot instantiate User Prefs Services.

Cause: Cannot instantiate User Prefs Services due to an initialization error.

Action: Check User Prefs Services configuration such as DataSource and TopLink DB Platform.
Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-25332: Directory for User Prefs Services File Persistence does not exist.

Cause: Directory for User Prefs Services File Persistence does not exist.

Action: System will try to create the directory.
Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-25333: invalid directory: {0}

Cause: The given path was not a valid directory.

Action: Specify a valid directory, not a file.
Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-25334: Device name is null.

Cause: Device name is null.

Action: Provide a valid Device name.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25335: invalid user ID: {0}

Cause: An invalid user ID was specified.

Action: Specify a valid user ID.
Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-25336: Input parameter, UserPrefsObject, is null.

Cause: Required parameter, UserPrefsObject, is null.

Action: Provide a valid UserPrefsObject.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25337: Failed to move a rule: origin rule number is out of the range of existing rules.

Cause: Origin rule number is not valid.

Action: Specify a valid rule number.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25338: Cannot find object to update: {0}

Cause: Cannot find object to update.

Action: Could be a problem in implementing persistence.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25339: Object already exists.

Cause: Tried to persist an object that already exists.

Action: To overwrite existing value, use '-overwrite' flag.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25340: Object not found.

Cause: Tried to remove an object that does not exist.

Action: (None)
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25341: The order of calling methods is wrong.

Cause: The order of calling methods is wrong.

Action: Check the order of the methods being called.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25342: Cannot find default address for user {0}.

Cause: The default address of that user was not set.

Action: Check that default address is set from UserPreference Administrator page.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25343: No devices are defined.

Cause: Tried to call delivery preferences without defining devices.

Action: Define devices for use with delivery preferences.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25344: Invalid action {0} is found and ignored.

Cause: An invalid action was detected.

Action: Use one of the valid actions: BROADCAST, FAIL_OVER, and DO_NOT_SEND.
Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-25345: Runtime exception was caught.

Cause: Runtime exception was caught.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25346: No configured Business Terms are available, only system terms will be used.

Cause: Business Term configuration could not be read.

Action: Ensure that business term configuration is correct
Level: 1

Type: WARNING

Impact: Configuration

SDP-25347: Device {0} cannot be added because it is present in the list.

Cause: A device was present in the list already.

Action: Ensure that the device to be added is not in the device list.
Level: 1

Type: WARNING

Impact: Configuration

SDP-25348: Failed to move a device: device ID index number is out of the range of device list.

Cause: Device ID index number is not valid.

Action: Specify a valid device ID index number.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25349: Name of rule is not set.

Cause: Rule name was not set.

Action: Set the name of the rule.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25350: FilterOperation of a rule is not set.

Cause: FilterOperation of a rule was not set.

Action: Set the FilterOperation of the rule.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25351: ActionOperation of a rule is not set.

Cause: ActionOperation of a rule was not set.

Action: Set the ActionOperation of the rule.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25352: Condition of a rule is not set.

Cause: Condition of a rule was not set.

Action: Set the condition of the rule.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25353: unable to send a BROADCAST message because no address is set

Cause: An address has not been set for the BROADCAST action.

Action: Set at least one address for the BROADCAST action.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25354: A failover address is not set for the FAIL_OVER action.

Cause: An address has not been set for the FAIL_OVER action.

Action: Set at least one address for the FAIL_OVER action.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25355: error while loading the business rule terms configuration

Cause: The business rule terms configuration file configuration/businessterms.xml could not be read.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Configuration

SDP-25356: Cannot persist device address {0} for user GUID {1}, because one already exists.

Cause: An identical device address already exists.

Action: Remove the conflicting device address, overwrite it, or specify a different address.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25357: Cannot persist rule set for user GUID {0}, because one already exists.

Cause: A rule set already exists for this user.

Action: Remove the conflicting rule set, or overwrite it.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25358: Cannot upload rule set for user GUID {0}, because one already exists.

Cause: A rule set already exists for this user.

Action: Try uploading the user messaging preferences using merge option 'overwrite' or 'append' (refer to command help for details).
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25359: Cannot upload user device for user GUID {0}, because one already exists.

Cause: A user device already exists for this user.

Action: Try uploading the user messaging preferences using merge option 'overwrite' or 'append' (refer to command help for details).
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25360: Initializing User Messaging Preferences services.

Cause: User Messaging Preferences services were initialized as part of application startup or deployment.

Action: None.
Level: 1

Type: NOTIFICATION

Impact: Other

SDP-25361: The Java VM does not support the encoding {0}.

Cause: The Java VM does not support the encoding used for XML string representing the RuleSet.

Action: Check your server Java VM and make sure it supports the encoding.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25362: This User Preference object cannot be deleted because it is backed by the user profile in the identity store: {0}.

Cause: An attempt was made to delete a read-only object backed by the user profile in the identity store.

Action: None.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25363: No UserRuleSet exists for userID {0}.

Cause: The user does not have a UserRuleSet.

Action: Check spelling of user ID.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25364: setFilterOperation has not been called.

Cause: Incorrect calling sequence.

Action: Invoke method setFilterOperation() first.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25365: Condition does not exist: {0}

Cause: Condition cannot be found.

Action: Check spelling of condition name or ID.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25366: Source parameter is greater than the number of conditions.

Cause: Source parameter is out of range.

Action: Provide correct source parameter.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25367: Error creating FilterCondition, type {0} is not valid.

Cause: Incorrect type has been found.

Action: Use correct type.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25368: Term {0} is not valid.

Cause: Term is not valid.

Action: Use a valid term.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25369: Term of type {0} does not accept operation {1}.

Cause: Unmatched type and operation.

Action: Use matching type and operation.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25370: Method setFilterTerm() has not been called.

Cause: setFilterTerm() method has not been called prior to current method invocation.

Action: Invoke setFilterTerm() first.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25371: FilterTerm should be initialized.

Cause: FilterTerm has not been initialized.

Action: Initialize FilterTerm first.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25372: Inconsistent FilterTerm.getName() : {0}, {1}

Cause: Name of filter term does not match the name of filter condition.

Action: Fix the inconsistency of filter term name and filter condition name.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25373: Inconsistent FilterTerm.getTypeName() : {0}, {1}

Cause: Type name of filter term does not match the name of filter condition.

Action: Fix the inconsistency of filter term type name and filter condition type name.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25374: Term operation should be defined.

Cause: Undefined term operation.

Action: Define operation of the term.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25375: Term of type {0} does not accept operation {1}.

Cause: Operation was not accepted by the term.

Action: Specify an operation that can be accepted by the term.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25376: TermOperation must be set.

Cause: TermOperation was not set.

Action: Set TermOperation properly.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25377: Operand {0} just allows {1} arguments, but is given {2}.

Cause: Number of arguments does not meet the requirement of the operand.

Action: Set correct number of arguments.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25378: Object {0} should be of type {1}.

Cause: Object has an incorrect Java type.

Action: Correct the type of object.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25379: Type {0} is not supported.

Cause: Object's type is not supported by User Preferences.

Action: Change the type of object to one of following supported Java types: String, Integer, Double and Date
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25380: User {0} does not exist in the system.

Cause: User name not found.

Action: Provide the correct user name.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25381: Device not found for user {0}.

Cause: Device does not exist.

Action: Provide a valid Device name or username.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25382: DeliveryType is missing in the address {0}.

Cause: Address does not have required DeliveryType.

Action: Provide a valid DeliveryType in the address in <DeliveryType>:<Address> format.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25383: Cannot persist device address {0}.

Cause: An exception occurred when storing device address.

Action: Check stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25384: Cannot create RuleSet for the user {0}.

Cause: An exception occurred while creating RuleSet for this user.

Action: Check stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25385: Saving UserRuleSet failed. Cannot get XMLString for user {0}.

Cause: An exception occurred while savinging RuleSet for this user.

Action: Check stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25386: Could not find entity to update.

Cause: Unable to find the entity in storage.

Action: None.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25387: Rule fact for term {0} has been ignored as it does not have the correct type, {1}.

Cause: The fact from user or application had an incorrect data type.

Action: Provide the fact with the correct data type as indicated.
Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-25388: Device named {0} of user {1} not found.

Cause: The user does not have a device with that name.

Action: Check username and device name.
Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-25400: An unexpected exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25401: Unable to set the parameter {0} in the configuration because of exception {1}.

Cause: An exception has occurred while attempting to set the specified parameter in the configuration object.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25402: Could not find the value for the configuration parameter {0}, using default value.

Cause: There is no such entry for the parameter {0} in the configuration file.

Action: Check configuration parameter.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25403: Error in registering messaging Runtime MBeans.

Cause: Exception was thrown.

Action: Check stack trace
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25404: Error in unregistering messaging Runtime MBeans.

Cause: Exception was thrown.

Action: Check stack trace.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25405: Naming exception thrown looking up Management Store: Unable to initialize SDP Messaging Runtime MBeans

Cause: Naming exception thrown while looking up the Management Store EJB.

Action: Check stack trace.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25406: Create exception thrown while creating Management Store: Unable to initialize SDP Messaging Runtime MBeans.

Cause: Create exception thrown while creating Management Store EJB.

Action: Check stack trace.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25407: Exception initializing Runtime MBean.

Cause: An exception was thrown during runtime MBean initialization.

Action: Check stack trace.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25408: Invalid query parameter: query field: {0}, query condition: {1}, query value: {2}

Cause: Invalid combination of query parameters or invalid query value.

Action: Check stack trace.
Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-25409: Unable to initialize the composite type for the MBean.

Cause: OpenDataException was caught.

Action: Check stack trace.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25410: Unable to convert to composite type and return composite data for the MBean. Name: {0}

Cause: OpenDataException was caught.

Action: Check stack trace.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25411: Unable to load Driver properties.

Cause: An exception has occurred while attempting to load the driver configuration properties.

Action: Check stack trace.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25413: Could not find the value for the configuration parameter {0}, using default value.

Cause: There is no such entry for the parameter {0} in the configuration file.

Action: Check configuration parameter.
Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-25414: Could not find the application deployment MBean for {0}

Cause: The application may not have started correctly.

Action: Check the application deployment status.
Level: 1

Type: WARNING

Impact: Process

SDP-25415: Found multiple application deployment MBeans for {0}

Cause: The application may not have started correctly.

Action: Check the application deployment status.
Level: 1

Type: WARNING

Impact: Process

SDP-25416: Error occurred while attempting to get the parent server MBean for {0}

Cause: An exception was thrown while attempting to get the parent server MBean.

Action: Check stack trace.
Level: 1

Type: ERROR

Impact: Process

SDP-25500: An unexpected exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25502: Unable to create JNDI Context

Cause: An exception has occurred.

Action: Check the stack trace for more details. Check the JNDI Context initialization parameters.
Level: 1

Type: ERROR

Impact: Configuration

SDP-25503: Unable to connect to the messaging server.

Cause: An exception has occurred.

Action: Check the stack trace for more details. Check that the messaging server is up. Check the JNDI Context initialization parameters.
Level: 1

Type: ERROR

Impact: Configuration

SDP-25504: Unable to register application information with the messaging server.

Cause: An exception has occurred.

Action: Check the stack trace for more details. Check that the messaging server is up. Check the JNDI Context initialization parameters.
Level: 1

Type: ERROR

Impact: Configuration

SDP-25505: Unable to enqueue outbound message.

Cause: Engine Sending Queue may not be available.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25506: Unable to get receiving queues from application information.

Cause: An exception has occurred.

Action: Check the stack trace for more details. Check the Application information properties.
Level: 1

Type: ERROR

Impact: Configuration

SDP-25507: Unable to enqueue inbound message status because no engine queues were found.

Cause: The client is not aware of any engine queues to enqueue the status.

Action: Check that the application is registered successfully with the messaging server.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25508: Unable to enqueue inbound message status.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25509: An error occurred while notifying the MessageDispatcherBean about engine queues.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Configuration

SDP-25510: An error occurred while attempting to retrieve the actual password from the credential store.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Configuration

SDP-25511: An error occurred while dequeuing a message from the application receiving queue.

Cause: An invalid JMS message was dequeued by the Dispatcher MDB.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25512: An invalid message was dequeued from the application receiving queue: {0}

Cause: An invalid JMS message was dequeued by the Dispatcher MDB.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25513: JNDI lookup of application callback listener failed.

Cause: An invalid callback listener was previously registered and could not be invoked.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-25514: An error occurred while dispatching an inbound message to the application.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25515: An error occurred while dispatching an inbound status to the application.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25516: Message/Status listener not configured. Suspending messaging client MDB to disable asynchronous message/status callbacks.

Cause: Message/Status listener was not configured by the application.

Action: If the application requires asynchronous message/status callbacks, configure the listener information. Otherwise, ignore this warning.
Level: 1

Type: WARNING

Impact: Configuration

SDP-25517: Messaging client MDB suspend failed: {0}

Cause: 1) The Messaging client was unable to access the MDB MBean because the container may not be in RUNNING state. 2) The server administrator username 'weblogic' does not exist.

Action: 1) Check the state of the container. Check the stack trace for more details. 2) Specify a valid server administrator username using the system property -Doracle.ums.admin.user and restart the server.
Level: 1

Type: WARNING

Impact: Configuration

SDP-25520: MessagingWebServiceClientImpl.send() operation failed.

Cause: An exception has occurred when invoking webservice send().

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25521: MessagingWebServiceClientImpl.receive() operation failed.

Cause: An exception has occurred while receiving messages from webservice.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25522: The application onMessage() callback operation failed.

Cause: An exception has occurred while attempting to call the application onMessage callback method.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25523: The application onStatus() callback operation failed.

Cause: An exception has occurred while attempting to call the application onStatus callback method.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25530: Creating Messaging EJB Client instance using Application information: {0}.

Cause: An application attempted to create a Messaging EJB Client instance.

Action: None
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

SDP-25531: Registering updated application information: {0}.

Cause: The application information changed.

Action: None
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

SDP-25532: An error occurred while retrieving the Application Information from the application JNDI context.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Configuration

SDP-25540: Unable to build a valid WSClient Application Name. Inbound messaging for this client may not work.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-25541: An error occurred while generating received message statuses.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25542: Security principal in client EJB Context "{0}" does not match security principal in ApplicationInfo "{1}". This may cause permission errors during future Messaging Client operations.

Cause: The security principal in the current EJBContext is different from the ApplicationInfo security principal field specified when creating the Messaging Client instance (or the default value, if no principal was provided).

Action: Ensure that the security principals used by this application for all Messaging Client operations match one another.
Level: 1

Type: WARNING

Impact: Security

SDP-25543: The current authenticated user "{0}" does not match the configured security principal "{1}".

Cause: The security principal in effect for the current thread is different from the security principal field specified when creating the Messaging Client instance.

Action: Ensure that the security principals used by this application for all Messaging Client operations match one another, or avoid configuring a specific security principal.
Level: 1

Type: WARNING

Impact: Security

SDP-25600: An unexpected exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25700: An unexpected exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25701: Unable to instantiate class {0}.

Cause: Unable to instantiate a class.

Action: Check to see if that class is in classpath or not.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25702: Unable to set content of Message object.

Cause: Unable to set content of a message.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25704: Error in setMultiplePayload.

Cause: An error occurred in setMultiplePayLoad().

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25705: Exception printing message content.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25706: Failed to clone message content.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25707: Failed to clone headers. Message = {0} .

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25708: Unable to perform JNDI lookup of JMS QCF: {0}.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25709: Unable to perform JNDI lookup.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25710: Could not close JMS queue connection.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25711: Received unknown object: {0}.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25712: Message received with invalid format: {0}.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25713: Unable to perform JNDI lookup of JMS Queue: {0}.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25714: Access control exception was caught. Name: {0} Action:{1}.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25715: Invalid format, skipping: {0}

Cause: Invalid queue information.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25716: Error occurred in looking up QueueConnectionFactory in JNDI, skipping: {0}

Cause: Error occurred in looking up QueueConnectionFactory in JNDI.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25717: Error occurred in looking up Queue in JNDI, skipping: {0}.

Cause: Error occurred in looking up queue in JNDI.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25718: Error occurred in getQueueInfoList.

Cause: Error occurred in getQueueInfoList().

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25719: Failed to authenticate user {0}.

Cause: Failed to authenticate a user.

Action: Check username and password and try again.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25720: Sender Address is null or empty.

Cause: Sender Address has an error.

Action: Enter a valid non-null value for sender.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25721: Recipient Address is null or empty.

Cause: Recipient Address has an error.

Action: Enter a valid non-null value for Recipient.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25722: Message content is empty.

Cause: Message content was not set properly.

Action: Enter a valid non-null value for the content.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25723: Message object is null.

Cause: Message is null.

Action: Set a valid non-null value of Message object.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25724: Message subject and content are null.

Cause: Message subject and content.

Action: Enter a valid non-null value for subject and/or content.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25725: Message serialization failed.

Cause: Failed to serialize message due to unexpected I/O Error.

Action: Ensure that content is being created according to recommendations for Message class.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25726: Connection failed to remote host {0} using HTTP Proxy {1}. Error: {2}.

Cause: There was a problem with either the remote host or the HTTP Proxy. Check the associated connection error for the exact cause.

Action: Check the value of the remote host and the HTTP Proxy settings.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25727: Unable to create JMS QueueSender, {0}. Cause: There was a problem in the connection to the JMS provider.

Cause: There was a problem in the connection to the JMS provider.

Action: Check the container log for additional errors from the JMS adapter.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25728: Could not determine server platform type. Generic values will be used for platform-specific data.

Cause: The Java EE server platform could not be determined. Either this application is executing in a Java SE environment, or the Java EE server is configured incorrectly.

Action: If executing in a Java SE environment, no action is necessary. Otherwise ensure that Java Required Files module is deployed to this environment.
Level: 1

Type: NOTIFICATION

Impact: Configuration

SDP-25729: An exception occurred while enabling the WS-Security configuration: {0}

Cause: An exception occurred while attaching a WS-Security policy to a web service client or endpoint.

Action: Ensure that any WS-Security policies are specified in the correct format.
Level: 1

Type: WARNING

Impact: Security

SDP-26000: An unexpected exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26001: Cannot create JNDI Context.

Cause: Cannot create JNDI Context.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26002: Dispatcher got a message: id ({0}) from ({1}) to ({2}), subject ({3}) content ({4}).

Cause: None

Action: None
Level: 1

Type: TRACE

Impact: Requests/Responses

SDP-26003: Dispatcher sent message with id: {0}.

Cause: None

Action: None
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

SDP-26004: No Messaging Engine Queue information to enqueue status.

Cause: No Engine Queue information to enqueue status.

Action: Check the stack trace for more details. Check Engine Queue information.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26005: Dispatcher failed to find a driver.

Cause: Dispatcher failed to find a driver.

Action: Compare delivery type and content type between message and available drivers.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

SDP-26006: Exception while dispatching message to driver resource adapter.

Cause: Exception while dispatching message to driver resource adapter.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26007: Received inbound queue information from messaging engine: {0}

Cause: None

Action: None
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

SDP-26008: An exception occurred while attempting to parse a Message: {0}.

Cause: None

Action: None
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

SDP-26009: Could not get JNDI InitialContext.

Cause: None

Action: None
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26010: Unable to start driver: {0}.

Cause: Unable to start driver.

Action: Check stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26011: Failed to invoke registerDriverInfo().

Cause: Exception thrown while invoking registerDriverInfo().

Action: Check stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26012: unable to remove scheduled workers

Cause: An exception has occurred while removing a driver thread.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26013: Unable to cleanly stop driver: {0}.

Cause: Unable to cleanly stop driver.

Action: Check stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26014: Unable to process inbound message/status.

Cause: Exception occurred while processing inbound message/status.

Action: Check stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26015: Unable to process command message.

Cause: Exception occurred while processing command message.

Action: Check stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26017: Attempting to register driver {0}.

Cause: None

Action: None
Level: 16

Type: TRACE

Impact: Process

SDP-26018: Located {0} DriverConnectionFactory successfully.

Cause: None

Action: None
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26019: Error occurred while registering driver.

Cause: Error occurred while registering driver.

Action: Check stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26020: Registration of driver {0} succeeded.

Cause: None

Action: None
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26021: Timed out while waiting for reply from Messaging engine.

Cause: The registration command timed out in the JMS queue because the Messaging engine is down or the system is under heavy load.

Action: Check if the Messaging engine is up and ensure the system is not under extremely heavy load.
Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-26022: Illegal DeliveryType specified, ignoring type {0}. Exception: {1}

Cause: Illegal DeliveryType specified.

Action: Check message delivery type.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26023: Benchmark logging is enabled for all inbound messages, which may slow down system performance. To disable it, unset environment variable sdpm_inbound_benchmark_logging and restart.

Cause: Benchmark logging is enabled when environment variable sdpm_inbound_benchmark_logging=true.

Action: To disable benchmark logging, unset environment variable sdpm_inbound_benchmark_logging and restart.
Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-26024: Registration of driver {0} did not complete; will retry periodically until messaging server responds.

Cause: None

Action: None
Level: 1

Type: WARNING

Impact: Process

SDP-26025: Error in registering messaging driver Runtime MBeans.

Cause: Exception was thrown.

Action: Check stack trace
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26026: Error in unregistering messaging driver Runtime MBeans.

Cause: Exception was thrown.

Action: Check stack trace
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26027: Ignoring property {0} with unsupported Java type {1} during driver initialization.

Cause: A property with an unsupported Java type was found in 'configuration/driverconfig.xml' during driver initialization.

Action: Use one of the following valid Java types: java.lang.Boolean, java.lang.String, java.lang.Integer, java.lang.Double, java.lang.Byte, java.lang.Short, java.lang.Long, java.lang.Float, java.lang.Character
Level: 1

Type: WARNING

Impact: Configuration

SDP-26028: Ignoring property {0} with invalid value {1} and/or Java type {2} during driver initialization.

Cause: A property with an invalid value and/or unsupported Java type was found in 'configuration/driverconfig.xml' during driver initialization.

Action: Use a valid value and/or one of the following valid Java types: java.lang.Boolean, java.lang.String, java.lang.Integer, java.lang.Double, java.lang.Byte, java.lang.Short, java.lang.Long, java.lang.Float, java.lang.Character
Level: 1

Type: WARNING

Impact: Configuration

SDP-26029: Unable to load driver configuration properties from 'configuration/driverconfig.xml'.

Cause: An exception occurred while attempting to load the driver configuration properties from 'configuration/driverconfig.xml'.

Action: Check the stack trace.
Level: 1

Type: ERROR

Impact: Configuration

SDP-26030: Unable to schedule worker used to attempt driver registration.

Cause: An exception occurred while scheduling a worker to attempt driver registration.

Action: Check the stack trace.
Level: 1

Type: WARNING

Impact: Process

SDP-26031: Lookup of encoded credential value {0} in the credential store for property {1} failed during driver initialization. Passing through the value as-is.

Cause: A property with an invalid encoded credential value was found in 'configuration/driverconfig.xml' during driver initialization.

Action: Use a valid encoded credential value and ensure the application has permission grants to access the credential store.
Level: 1

Type: WARNING

Impact: Configuration

SDP-26032: JNDI lookup of driver connection factory {0} failed with the following error message: {1}. Will retry until successful.

Cause: Driver connection factory could not be located in JNDI. Driver registration will not occur until this lookup succeeds.

Action: Wait for server startup to proceed. If driver registration does not occur, ensure that the driver connection factory JNDI name is configured correctly.
Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-26033: Started messaging driver: {0}

Cause: Driver was started.

Action: None.
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26034: Stopped messaging driver: {0}

Cause: Driver was stopped.

Action: None.
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26035: JNDI lookup of server command endpoint {0} failed with the following error message: {1}. Will retry until successful.

Cause: Messaging Server command module could not be located in JNDI. Driver registration will not occur until this lookup succeeds.

Action: Wait for server startup to proceed. If driver registration does not occur, ensure that the messaging server is deployed and started.
Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-26036: Receiver received message with id: {0}.

Cause: None

Action: None
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

SDP-26100: An unexpected exception was caught.

Cause: An unexpected exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26101: Content type parsing error {0}.

Cause: Error occurred while trying to parse the content type.

Action: Check and see if the content type is specified correctly.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26102: Error while writing e-mail message content.

Cause: An exception has occurred while writing e-mail content and headers to an e-mail message.

Action: Check stack trace or error log.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26103: Error while writing e-mail subject.

Cause: Cannot write the subject.

Action: Check stack trace or error log.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26104: Recipient address error.

Cause: Recipient e-mail address has an error.

Action: Check and see if the recipient e-mail address is correct.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26105: unable to deliver to following address(es): {0} Reason: {1}

Cause: One or more recipient e-mail addresses had an error.

Action: Ensure that the e-mail address is correct.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26106: failed to send the e-mail message

Cause: Unable to login to SMTP server.

Action: Check SMTP server host name, port, user name, and password.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26107: failed to add header - name: {0} value: {1}

Cause: Unable to add an e-mail header to a multipart message

Action: Check the stack trace or error log.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26108: failed to initialize e-mail driver

Cause: Could not initialize Email Driver.

Action: Check stack trace or error log. Check e-mail driver parameters and make sure all e-mail servers are up.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26109: Caught exception while closing connection to e-mail server.

Cause: An exception was caught while closing connection.

Action: Check stack trace or error log.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26110: Starting Email Driver failed.

Cause: Could not start Email Driver.

Action: Check stack trace or error log. Check e-mail driver parameters and make sure all servers are up.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26111: Could not remove listener from Email Driver

Cause: Could not remove listener from Email Driver

Action: Check stack trace or error log
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26112: Null protocol error

Cause: Protocol was null.

Action: Specify an appropriate protocol for this driver.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26113: No incoming e-mail server.

Cause: Incoming server was not set.

Action: Set incoming server parameters.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26114: Username is missing.

Cause: Username was not set.

Action: Set the username in e-mail driver parameters.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26115: failed to receive an inbound e-mail message

Cause: An exception has occurred while receiving an inbound e-mail message.

Action: Check stack trace or error log.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26116: Protocol {0} is not supported.

Cause: An unsupported protocol was provided.

Action: Check the e-mail protocol name in e-mail driver parameters.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26117: Connection information of the inbound e-mail server is missing. Check the server host name, user name, and password.

Cause: Connect information was missing or incomplete.

Action: Provide the required connection information.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26118: failed to open folder: {0}

Cause: Folder name is not correct or does not exist.

Action: Check folder name spelling.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26119: Max retry limit reached for trying to connect to user {0}

Cause: Email driver has reached Max retry limit to connect to user.

Action: Check stack trace or error log. Check e-mail driver parameters and make sure all servers are up.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26120: IMAP server failed to expunge e-mail messages. mail box: {0}

Cause: An exception was caught when doing expunge.

Action: Check stack trace or error log. Check e-mail driver parameters and make sure all servers are up.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26121: Attempt to reconnect {0}. Error Count: {1} Retry Count: {2}.

Cause: Attempt to reconnect to the incoming e-mail server

Action: Check e-mail driver parameters and make sure all servers are up.
Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-26122: An exception has been thrown when connecting to user {0}

Cause: Email driver could not connect to user.

Action: Check username and password. Make sure the user exists and is accessible.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26123: Could not initialize Email Store for user {0}

Cause: Could not initialize Email Store for user.

Action: Check stack trace or error log. Check username and password.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26124: invalid folder: {0}

Cause: An invalid folder name was specified.

Action: Check and see if the specified folder is valid and accessable.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26125: An exception has occurred while sending out a message.

Cause: An exception occurred while sending out a message.

Action: Check stack trace or error log. Check Proxy Driver parameters and remote gateway.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26126: unrecoverable message - {0}

Cause: failed to recover an e-mail message

Action: Check stack trace or error log.
Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-26127: Collision on e-mail message polling. Pausing for {0} seconds.

Cause: Multiple e-mail drivers polling the same e-mail account at the same time.

Action: (None)
Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-26128: A duplicate inbound e-mail message has been discarded: gateway message ID: {0}, recipient addresses: {1}, subject: {2}.

Cause: A duplicate message was detected and discarded by the e-mail receiver.

Action: (None)
Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-26129: unable to deliver to following addresses: {0} Reason: {1}

Cause: Recipient e-mail address was valid but sending failed for reason indicated in error message.

Action: Ensure that e-mail driver and SMTP server are operational and configured correctly, baed on information provided in error message.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26150: An unexpected exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26151: Failed to process a received message in SMPP driver, because driver context is null

Cause: Driver context is null

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26152: WorkManager object is null in SMPP driver.

Cause: The caller of setWorkManager() passed in a null WorkManager object as an argument

Action: Make sure WorkManager object is not null.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26153: Received status message with incorrect format.

Cause: The status received from SMSC does not have message ID or state.

Action: Correct the SMSC.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26154: Failed to process received status in SMPP driver, because driver context is null.

Cause: Driver Context is null

Action: Check driver context.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26155: unable to initialize SMPP driver, because a driver attribute, sms.account.id, is not set.

Cause: The account ID was not set.

Action: Set the correct account information.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26156: Failed to initialize SMPP Driver because driver attributes sms.server.host, sms.server.transmitter.port or sms.server.receiver.port is not set.

Cause: SMSC server or account information is not correct or missing.

Action: Check those parameters.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26157: SMPP driver failed to send out a message, because Message object is null.

Cause: Null message object.

Action: Check the caller of this method.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26158: Caught exception while closing connection

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26159: Illegal data length value from SMSC received and ignored: {0}

Cause: SMPP Driver has detected a corrupted data field from SMSC and it is trying to recover.

Action: This error suggests communication errors between SMPP driver and SMSC. Check to see if this driver supports that SMSC.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26160: SMPP Driver not configured. Configure and restart this driver. Required Properties: SmsAccountId, SmsServerHost, TransmitterSystemId, ReceiverSystemId, TransmitterSystemType, ReceiverSystemType, TransmitterSystemPassword, ReceiverSystemPassword, ServerTransmitterPort, ServerReceiverPort.

Cause: SMPP Driver was not configured.

Action: Configure and restart this driver. Required Properties: SmsAccountId, SmsServerHost, TransmitterSystemId, ReceiverSystemId, TransmitterSystemType, ReceiverSystemType, TransmitterSystemPassword, ReceiverSystemPassword, ServerTransmitterPort, ServerReceiverPort.
Level: 1

Type: ERROR

Impact: Configuration

SDP-26161: Starting SMPP Driver: {0}

Cause: SMPP Driver resource adapter initialization.

Action: None
Level: 1

Type: NOTIFICATION

Impact: Configuration

SDP-26162: Message content could not be decoded using character set {0}

Cause: The message content retrieved from the SMSC could not be decoded using the specified character set.

Action: Ensure that the Default Encoding configuration parameter is correct.
Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-26163: Data stream ended unexpectedly while reading packet from SMSC

Cause: The data stream ended unexpectedly while reading a packet from the SMSC. Message or command will be dropped.

Action: None.
Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-26164: Failed to bind receiver connection; will retry until bind operation is successful.

Cause: Could not bind to the SMSC as a receiver. Bind operation will be retried periodically until it is successful.

Action: None required. Change value of configuration parameter "BindRetryDelay" to adjust retry interval.
Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-26200: An unexpected exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26201: Unable to remove listener from XMPPDriver.

Cause: Unable to remove listener from XMPPDriver .

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26202: Unable to shut down XMPPDriver.

Cause: Unable to shut down XMPPDriver.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26203: XMPP Driver not configured. Configure and restart this driver. Required properties: IMServerHost, IMServerUsername, IMServerPassword.

Cause: XMPP Driver was not configured.

Action: Configure and restart this driver. Required properties: IMServerHost, IMServerUsername, IMServerPassword.
Level: 1

Type: ERROR

Impact: Configuration

SDP-26204: Error occurred while initializing {0}

Cause: Error occurred while initializing driver instance.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26205: Driver, {0}, initialization succeeds.

Cause: Driver initialization succeeds.

Action: Check the stack trace for more details.
Level: 16

Type: TRACE

Impact: Process

SDP-26206: Driver, {0}, initialization fails.

Cause: Driver initialization fails.

Action: Check the stack trace for more details.
Level: 16

Type: TRACE

Impact: Process

SDP-26207: Invalid value for im.retry.limit. Value reset to default - {0}

Cause: Invalid value for im.retry.limit. Value reset to default

Action: Specify a valid value for im.retry.limit
Level: 1

Type: NOTIFICATION

Impact: Configuration

SDP-26208: Invalid value for im.retry.interval. Value reset to default - {0} seconds

Cause: Invalid value for im.retry.interval. Value reset to default.

Action: Specify a valid value for im.retry.interval
Level: 1

Type: NOTIFICATION

Impact: Configuration

SDP-26209: Unable to initialize accounts

Cause: Unable to initialize accounts.

Action: Check username, password and IM server.
Level: 1

Type: ERROR

Impact: Configuration

SDP-26210: Unable to connect to XMPP server: {0}

Cause: Check the associated stack trace for the cause of the connection failure.

Action: Check the XMPP server hostname and port parameters and make sure the server is up.
Level: 1

Type: ERROR

Impact: Configuration

SDP-26212: Shut down complete

Cause: Shut down complete.

Action: None
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26213: Exception while sending message - from: {0} to: {1}.

Cause: Exception while sending message.

Action: Check stack trace and recipient address
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26214: Caught an exception in XMPP driver while sending out a message.

Cause: An unexpected exception was caught.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26215: The XMPP driver has no previous account to replace.

Cause: No previous XMPP (IM) account was found. Unable to replace previous account.

Action: None
Level: 1

Type: WARNING

Impact: Configuration

SDP-26216: No accounts defined in XMPP driver.

Cause: No XMPP accounts defined.

Action: Define a valid XMPP (IM) account.
Level: 1

Type: ERROR

Impact: Configuration

SDP-26217: Could not locate an account to deliver this message from sender {0}. Using the first account ( {1} ) to deliver this message.

Cause: Could not locate an account to deliver this message.

Action: To retain the original message sender, add sender of the message to 'user' configuration property of the driver.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26218: I/O problem using HTTP Proxy {0} for account: {1}

Cause: The connection with the HTTP Proxy was broken.

Action: Check stack trace for more information. Check HTTP Proxy settings to see if proxy is correct and reachable.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26219: Server DNS problem with account: {0}

Cause: The hostname could not be resolved by DNS.

Action: Check the stack trace, account parameters, and DNS server.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26220: Server I/O problem with account: {0}

Cause: The connection with the XMPP server was broken.

Action: Check the account parameters and the network connection.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26221: Third-party transport connectivity is no longer supported. Ignoring all applicable configuration properties.

Cause: This is an upgraded XMPP Driver instance making use of third-party transport connectivity that is no longer supported in this version.

Action: None
Level: 1

Type: WARNING

Impact: Configuration

SDP-26222: Agent registration failed for {0}. Error Code: {1}

Cause: Agent registration failed.

Action: Check error code and from address.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26223: Fatal Error on Presence object build.

Cause: Fatal Error on Presence object build.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26224: Exception managing presence

Cause: Exception managing presence.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26225: Received Error Message. Code: {0} Text: {1}.

Cause: Received Error Message.

Action: Check error code and error message.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26226: Unauthorized login to Jabber/XMPP server: {0}

Cause: Invalid username and/or password was supplied.

Action: Check username and password.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26227: New account registration failed. It appears that the Jabber/XMPP server does not allow automatic registration. Contact the server administrator for a new account. Now disconnecting from server: {0}

Cause: New account registration failed. It appears that the Jabber/XMPP server does not allow automatic registration.

Action: Contact the server administrator for a new account.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26228: New account registration failed. Either this account already exists and you have entered an incorrect password or there is a problem with the Jabber/XMPP server. Now disconnecting from server: {0}

Cause: New account registration failed. Either this account already exists and you have entered an incorrect password or there is a problem with the Jabber/XMPP server.

Action: Check that the specified account does not exist. Check that your password is valid
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26229: Plaintext authentication failed; disconnecting from server: {0}

Cause: Plaintext authentication failed.

Action: Check username and password and check with the Jabber/XMPP server administrator.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26230: Digest authentication failed. Attempting plain-text authentication: {0}

Cause: Digest authentication failed.

Action: Digest authentication failed. Check with the Jabber/XMPP server administrator.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26231: InfoQuery packet:

Cause: None

Action: None
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26232: Presence packet:

Cause: None

Action: None
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26233: Message packet:

Cause: None

Action: None
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26234: Disconnecting from Jabber/XMPP server: {0}. Cause: 1) The account was disconnected by the XMPP server due to another conflicting login. 2) The XMPP server went offline. Action: 1) Identify and shut down the conflicting XMPP driver that is using the same account. 2) Check the status of the XMPP server.

Cause: 1) The account was disconnected by the XMPP server due to another conflicting login. 2) The XMPP server went offline.

Action: 1) Identify and shut down the conflicting XMPP driver that is using the same account. 2) Check the status of the XMPP server.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

SDP-26235: Account disconnected: {0}. Cause: I/O or authentication error. Action: Check account host, username and password configuration. Check the connectivity to the XMPP server.

Cause: The account was disconnected from the server either due to I/O or authentication error.

Action: Check account host, username and password configuration. Check the connectivity to the XMPP server.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

SDP-26236: Got an unexpected exception when receiving a message.

Cause: Got an exception when receiving a message.

Action: Check to see if the message is well-formed.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26237: The call for conversion does not supply account information. The first account is being used for conversion.

Cause: The call for conversion did not supply the necessary account information.

Action: Provide the correct account information.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26238: cannot deliver to this {0} user, because {0} transport is not enabled in the driver. Set the value for driver parameter: {1}.

Cause: Because transport was not enabled in the driver, delivery could not be made to the Yahoo, MSN, AOL, or ICQ user.

Action: Enable the transport in the driver.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26239: Invalid network name in address: {0}

Cause: Invalid network name in address

Action: Specify a valid network name in address.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26240: Max Retry Limit ( {0} ) is reached. Restart the driver to try reconnecting for account {1}.

Cause: The Max Retry Limit was reached while attempting to reconnect.

Action: Restart the XMPP driver to try again.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26241: Reconnecting now... attempt #{0} for account {1}.

Cause: None

Action: None
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

SDP-26242: Reconnecting in {0} seconds for account {1}.

Cause: None

Action: None
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

SDP-26243: Account {0} is disconnected from the server at the request of the driver.

Cause: None.

Action: None.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

SDP-26244: Missing value for parameters {0} and/or {1}.

Cause: None

Action: None
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

SDP-26245: Could not initialize XMPPDriver.

Cause: XMPPDriver was misconfigured.

Action: Check driver parameters, account information and Jabber/XMPP server.
Level: 1

Type: ERROR

Impact: Process

SDP-26246: Caught exception while closing connection of XMPP server.

Cause: Caught exception in XMPP driver while closing server connection.

Action: Check stack trace.
Level: 1

Type: ERROR

Impact: Process

SDP-26247: Caught exception while closing connection.

Cause: Caught exception while closing connection.

Action: Check stack trace.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26248: Account disconnected: {0}. Cause: Unknown. Action: Check account host, username and password configuration. Check the connectivity to the XMPP server.

Cause: The account was disconnected from the server due to an unknown error.

Action: Check account host, username and password configuration. Check the connectivity to the XMPP server.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

SDP-26249: Account connected: {0}

Cause: The driver successfully connected to the server for this account.

Action: None.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

SDP-26250: An unexpected exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26251: Could not initialize Proxy Driver

Cause: Could not initialize Proxy Driver.

Action: Check stack trace or error log. Check Proxy Driver parameters and remote gateway.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26252: Error occurred while initializing Proxy Driver: DriverConnection returned by DriverConnectionFactory is null.

Cause: DriverConnection returned by DriverConnectionFactory was null

Action: Check stack trace or error log. Check Proxy Driver parameters and remote gateway.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26254: Failed to initialize Proxy Driver with GatewayURL={0} and Username={1}. Check driver configuration properties and remote gateway, and restart the driver.

Cause: Failed to initialize Proxy Driver with the specified GatewayURL, Username and Password.

Action: Check stack trace or error log. Check Proxy Driver properties: GatewayURL, Username and Password. Also check the status of the remote gateway.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26255: Exception occurred while initializing Proxy Driver

Cause: Exception occurred while initializing Proxy Driver

Action: Check stack trace or error log. Check Proxy Driver parameters and remote gateway.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26256: Proxy Driver has not been configured. Configure and restart this driver. Required Property: GatewayURL.

Cause: Proxy Driver was not configured.

Action: Configure and restart this driver. Required Property: GatewayURL.
Level: 1

Type: ERROR

Impact: Configuration

SDP-26257: Exception occurred while invoking Proxy Driver remote request

Cause: Exception occurred while invoking Proxy Driver remote request

Action: Check stack trace or error log. Check Proxy Driver configuration and remote gateway.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26350: An unexpected exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26351: VoiceXML Driver property VoiceXMLReceiveURL is empty.

Cause: VoiceXMLReceiveURL was not set and could not be dynamically generated.

Action: Check the validity of the VoiceXMLReceiveURL property. Ensure the host and port are that of the server where this driver is deployed.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26352: VoiceXMLDriver: VoiceXMLOutboundServletURI cannot be null

Cause: VoiceXMLOutboundServletURI is null

Action: Assign proper value for Outbound Servlet URL.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26353: VoiceXMLDriver::Deliver: Message URL = {0}

Cause: None

Action: None
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

SDP-26354: VoiceXMLDriver::Deliver: URL sent to Voice Gateway = {0}

Cause: None

Action: None
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

SDP-26355: VoiceXMLDriver::Deliver: Reply message = {0}

Cause: None

Action: None
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

SDP-26356: VoiceXMLDriver: Socket error from VoiceXML Gateway.

Cause: Socket Error from the Gateway

Action: Check VoiceXML server URL and the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26357: VoiceXMLDriver could not initialize.

Cause: Initialization failed.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26358: VoiceXMLDriver: Exception while processing the HTTP request.

Cause: Exception while processing the HTTP request

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26359: VoiceXMLDriver: Caught exception while closing connection

Cause: Caught exception while closing connection

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26360: VoiceXML Driver not configured. Configure and restart this driver. Required Properties: VoiceXMLOutboundServletURI.

Cause: VoiceXML Driver was not configured.

Action: Configure and restart this driver. Required Properties: VoiceXMLOutboundServletURI.
Level: 1

Type: ERROR

Impact: Configuration

SDP-26400: An unexpected exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26401: Messaging Worklist Driver not configured. Configure and restart this driver. Required Properties: BPELConnectionURL.

Cause: Messaging Worklist Driver was not configured.

Action: Configure and restart this driver. Required Properties: BPELConnectionURL.
Level: 1

Type: ERROR

Impact: Configuration

SDP-26450: An unexpected exception was caught.

Cause: An unexpected exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26451: One or more sets of extension endpoints were configured using identical protocols and mapped domains: {0}. The first endpoint listed in the configuration file will be used.

Cause: Each of the listed protocol/domain pairs is used to configure multiple extension endpoints.

Action: Remove the conflicting endpoint configuration, or ensure that each endpoint has unique protocol and mapped domain parameters.
Level: 1

Type: WARNING

Impact: Configuration

SDP-26452: No extension endpoint could be found for the specified recipient address.

Cause: None of the configured extension endpoints matched the protocol and domain of the message recipient.

Action: Ensure that an endpoint is configured for the desired protocol and domain, or configure a default (empty) domain.
Level: 1

Type: NOTIFICATION

Impact: Configuration

SDP-26453: No configuration element was found for this Extension Driver deployment. Create a configuration and restart this Extension Driver.

Cause: No configuration element was found for this Extension Driver deployment.

Action: Create a configuration and restart this Extension Driver.
Level: 1

Type: ERROR

Impact: Configuration

SDP-26454: Extension Driver not configured. Configure and restart this driver. The configuration must contain at least one Extension endpoint with a valid endpoint URL and protocol.

Cause: Extension Driver was not configured.

Action: Configure and restart this driver. The configuration must contain at least one Extension endpoint with a valid endpoint URL and protocol.
Level: 1

Type: ERROR

Impact: Configuration

SDP-26455: Error while processing Extension Driver configuration for property group with Endpoint URL: {0}. Check the corresponding property group configuration, then restart this driver. The configuration must contain an Extension endpoint with a valid endpoint URL and protocol.

Cause: An error occurred while processing the Extension Driver configuration.

Action: Check the corresponding property group configuration, then restart this driver. The configuration must contain an Extension endpoint with a valid endpoint URL and protocol.
Level: 1

Type: WARNING

Impact: Configuration

87 SOA-00000 to SOA-31033

SOA-00000: Malformed WS Binding port. Missing # between namespace URI and service/port names.

Cause: Malformed webservice binding component port configuration

Action: Correct the port attribute for ws binding component in the composite configuration.
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00001: Malformed WS Binding port. Missing '/' between service and port name

Cause: Malformed webservice binding component port configuration

Action: Correct the port attribute for ws binding component in the composite configuration.
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00002: No service name found.

Cause: No service name found in webservice binding component configuration

Action: Add the service name attribute for ws binding component in the composite configuration.
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00003: Number of SOAP body elements and parts do not match in operation: {0}

Cause: Malformed SOAP request. Number of Parts in the soap body does not match with WSDL definition.

Action: Correct the SOAP message.
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00004: Response message does not match output defined in the WSDL: output of operation "{0}" is null, but response message contains payload.

Cause: SOAP response does not match WSDL definition.

Action: Correct the SOAP message.
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00007: Unable to find service: {0}

Cause: Specified service is not found in the WSDL.

Action: Either correct the wsdl or the service name.
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00008: Unable to find port: {0}

Cause: Specified port is not found in the WSDL.

Action: Either correct the wsdl or the port name.
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00009: Unable to find operation: {0}

Cause: Specified operation is not found in the WSDL.

Action: Either correct the wsdl or the operation name.
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00010: Error in create Documentbuilder.

Cause: Failure to create a new DocumentBuilder class.

Action: Server configuration may have to be corrected.
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00011: Problem in parsing componentType {0}.

Cause: Problem in parsing component type file.

Action: Correct the component type file configuraiton.
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00012: Request message does not match input defined in the WSDL: input of operation "{0}" is null, but request message contains payload.

Cause: Request message does not match input defined in the WSDL. Input is not defined, but there is an input payload.

Action: Correct the wsdl.
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00013: Malformed WSDL Interface attribute. Missing # between namespace URI and interface name.

Cause: Malformed WSDL Interface attribute. Missing # between namespace URI and interface name.

Action: Add # between namespace URI and interface name.
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00014: No interface name found.

Cause: Specified interface not found in the WSDL definition.

Action: Correct the input wsdl or interface name.
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00015: Error in getting XML input stream: {0}

Cause: Failure in processing XML document.

Action: Make sure the xml input is valid.
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00016: Failed to concatanate the following 2 urls: home= "{0}" and relative="{1}".

Cause: Failure in creating urls from the given home url and relative url.

Action: Correct the home or the relative urls.
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00018: Failed to find a component type file: compositeDN = "{0}" and component="{1}".

Cause: Failed to find component type file.

Action: Correct the component type file name.
Level: 1

Type: WARNING

Impact: Requests/Responses

SOA-00019: Missing "{0}" delimeter

Cause: Missing a delimiter.

Action: Add the missing delimiter.
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00020: Unable to instantiate composite class loader due to exception {0}

Cause: Failure instantiating composite classloader.

Action: Check the exception for detailed messages.
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00021: No reference "{0}" defined for service "{1}"

Cause: No Reference defined for the given service.

Action: Correct the composite configuration.
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00022: Error Loading XML Schema {0}

Cause: Failure to find the specified schema.

Action: Correct the schema location referenced.
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00023: Incorrect config object type.

Cause: Incorrect Object Configuration type.

Action: Correct the configuration for the object.
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00025: Unable to convert to SDO: {0}

Cause: Failed to convert xml input to SDO object.

Action: Check the exception message. You may have to correct the schema definition or configuration.
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00026: Error converting SDO to XML: {0}

Cause: Failure in converting sdo objects to xml messages.

Action: Check the exception message. You may have to correct the schema definition or configration.
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00027: Cannot remove property "{0}" that was defined in the componentType.

Cause: Unable to remove the property defined in the component type file.

Action: Correct the component type configuraiton file.
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00028: Invalid value for mode. It should be either active or retired mode.

Cause: Invalid mode specified in the composite

Action: Provide valid mode such as active or retired.
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00029: Invalid value for mode. It should be either on or off state.

Cause: Invalid state specified in the composite

Action: Provide valid state such as on or off.
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00030: Could not use reflection to get properties from the bean of class: {0}. {1}

Cause: Failure in retrieving bean properties

Action: Check exception message for details.
Level: 1

Type: WARNING

Impact: Requests/Responses

SOA-00031: Binding Type {0} is unknown.

Cause: The type of binding is undefined.

Action: Please check document for valid binding types supported.
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00032: An MBean of name "{0}" already exists. Unable to create MBean for this composite.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

SOA-00033: An MBean of name "{0}" doesnt exist. Unable to update its state.

Cause: Specified mbean does not exist.

Action: Correct the mbean name used.
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00034: Unable to load the "{0}" file from "{1}" directory.

Cause: Failed to load the file using mdm configuration.

Action: Correct the MDM configuration.
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00035: Variable "{0}" not defined in mdm-url-resolver.xml.

Cause: The variable is not defined in the mdm configuration file.

Action: Correct the mdm configration file.
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00036: mdm-url-resolver.xml not loaded

Cause: MDM url resolver is not loaded.

Action: Check the server configuration for MDM setup.
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00037: Malformed Java Binding port. Missing # between namespace URI and service/port names.

Cause: Port type in binding component is invalid.

Action: Check the port type attribute and correct the syntax used.
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00038: Malformed Java Binding port. Missing name of the portType

Cause: Port type in binding component is invalid.

Action: Check the port type attribute and correct the syntax used.
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00039: Invalid composite element name "{0}". Element names in a composite have to be unique.

Cause: Invalid composite file.

Action: Correct the element name used for the composite.
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00040: Unable to convert sdo to xml, element name not found.

Cause: Failed to convert sdo objects to xml messages

Action: Check the schema definition referenced from the wsdl.
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00041: Unable to create composite loader dir {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

SOA-00042: Unable to close resource input stream. This can lead to a loss of system file descriptor resources:

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

SOA-00043: Unable to convert sdo to xml, missing sdo metadata.

Cause: Failed to convert sdo objects to xml messages. Metadata for the conversion is not found.

Action: Check the schema definition referenced from the wsdl.
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-00044: Failed to parse XML string {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Data

SOA-00045: Failed to create parser {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

SOA-10000: Import type {0} is not currently defined. The only valid import types are "wsdl" and "edl". If you are attempting to import an xsd file, please do so through a WSDL document.

Cause: The import type specified for the composite import is unrecognized

Action: Make sure the import type is one of the currently recognized types (.edl, .wsdl)
Level: 1

Type: ERROR

Impact: Configuration

SOA-10001: No binding node (e.g. <binding.ws>) found for {0}. Please make sure that the composite specifies a binding of a given type.

Cause: No bindings are configured for the given service or reference

Action: Check that the composite's services and references specify at least one binding.
Level: 1

Type: ERROR

Impact: Configuration

SOA-10002: Unable to add a code source to the composite classloader due to an exception. Please ensure that the proper resources are available in the SCA-INF/classes, SCA-INF/gen-classes, and SCA-INF/lib composite archive sub-directories.

Cause: Unable to add a code source to the composite's classloader due to an exception

Action: Ensure that resources are available in the SCA-INF/classes, SCA-INF/gen-classes, and SCA-INF/lib composite archive sub-directories.
Level: 1

Type: ERROR

Impact: Deployment

SOA-10003: Failed to retrieve the application topology node from the TopologyService using {0}.

Cause: Unable to retrieve a toplogy node from the Toplogy Service

Action: Please check whether the toplogy node path is valid
Level: 1

Type: ERROR

Impact: Deployment

SOA-10004: Failed to create MAS-enabled componentType lookup; {0}.

Cause: Unable to create a strategy that enables the lookup of .componentType files in a MAS environment

Action: Make sure the toplogy node path, composite home directory, and strategy class name are correct
Level: 1

Type: ERROR

Impact: Deployment

SOA-10005: Failed to retrieve {0} document from topology node {1}.

Cause: Unable to retrieve a document from the topolgy node

Action: Make sure the toplogy node path, composite home directory, and the document name are correct
Level: 1

Type: WARNING

Impact: Other

SOA-10006: Error occurred while retrieving {0} document from topology node {1}. The underlying cause was a {2}.

Cause: An error occurred during the retrieval of a document from a topology node

Action: Make sure the resource path is valid and that the deployment succeeded
Level: 1

Type: ERROR

Impact: Configuration

SOA-10007: Error occurred while attempting to retrieve message part {0} from a normalized message payload with elements {1}.

Cause: An attemp to retrieve a message part of a given name from a Normalized Message failed

Action: Make sure that there is no mismatch between the WSDL defined part name and a configured part name
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-10008: Error occurred during deployment of component: {0} to service engine: {1}, for composite: {2}

Cause: An error occurred during component deployment

Action: Please check the root cause of the failure
Level: 1

Type: ERROR

Impact: Deployment

SOA-10009: Error occurred during creation of domain/instance noun: {0}

Cause: An error occurred during creating noun for domain/instance

Action: Please check the root cause of the failure
Level: 1

Type: ERROR

Impact: Configuration

SOA-10010: Error occurred while getting portable mbean factory: {0}

Cause: An error occurred while getting portable mbean factory

Action: Please check the root cause of the failure
Level: 1

Type: ERROR

Impact: Configuration

SOA-20000: Message Router for {0} is null. Please validate that the composite deployment completed successfully by checking the server logs.

Cause: There is no message router found for the composite

Action: Check that the composite deployment completed successfully
Level: 1

Type: ERROR

Impact: Deployment

SOA-20001: Message Router for {0} is not able to process messages. The composite state is set to "off". The composite can be turned "on" by using the administrative consoles.

Cause: The composite state or mode do not allow processing of messages

Action: Use the management consoles to set the mode and state of the composite to enable processing
Level: 1

Type: ERROR

Impact: Configuration

SOA-20002: No path info set for provider invocation. Unable to determine composite and service for processing.

Cause: There is no path information in the inovcation URI that facilitates routing of the message to the composite service

Action: Make sure that the invoking URL is of the form http://host:port/soa-infra/services/applicationName/compositeName/serviceName
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20003: Unable to register service.

Cause: There was an issue during the attempt to create the endpoint for the composite service

Action: Make sure that the WSDL either has a service and port that correspond to the values specified in the composite file or that there is no empty service node in the WSDL
Level: 1

Type: ERROR

Impact: Deployment

SOA-20004: Unable to deregister service.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20006: Unable to register reference {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20007: Cannot find binding component for service "{0}".

Cause: There is no binding component configured in the SOA Platform that can handle the given service binding type

Action: Make sure that the binding type specified for the composite's service is valid
Level: 1

Type: ERROR

Impact: Configuration

SOA-20008: Cannot find binding component for reference "{0}".

Cause: There is no binding component configured in the SOA Platform that can handle the given reference binding type

Action: Make sure that the binding type specified for the composite's reference is valid
Level: 1

Type: ERROR

Impact: Configuration

SOA-20009: Cannot find service engine for component "{0}" in composite "{1}".

Cause: There is no service engine configured in the SOA Platform that can handle the given component implmentation type

Action: Make sure that the implementation type specifed for the composite's component is valid
Level: 1

Type: ERROR

Impact: Configuration

SOA-20010: Unable to find Binding Component for type "{0}".

Cause: No binding component found for the given type

Action: Make sure the configured type has a corresponding SOA Platform configured binding component
Level: 1

Type: ERROR

Impact: Configuration

SOA-20011: Unable to find Service Engine for type "{0}".

Cause: No service engine found for the given type

Action: Make sure the configured type has a corresponding SOA Platform configured service engine
Level: 1

Type: ERROR

Impact: Configuration

SOA-20012: Unable to find component or reference identified by "{0}".

Cause: Unable to find a component or reference of the given name in the composite

Action: Make sure the composite wires are properly formed and reference existing components and/or references
Level: 1

Type: ERROR

Impact: Configuration

SOA-20013: MDS Root mis-configuration.

Cause: The MDS root directory is misconfigured

Action: Make sure the composite directories specified in the deployed-composites.xml file are correct
Level: 1

Type: ERROR

Impact: Deployment

SOA-20018: Cannot read WSDL "{0}" from Metadata Manager.

Cause: There was a problem reading a WSDL document from the MDS repository

Action: Make sure the composite imports point to the valid WSDL paths
Level: 1

Type: ERROR

Impact: Deployment

SOA-20019: Object "{0}" does not exist in metadata repository.

Cause: The requested file or resource does not exist in the MDS repository

Action: Make sure the resource path is valid
Level: 1

Type: ERROR

Impact: Configuration

SOA-20020: Deployment of composite "{0}" failed: {1}.

Cause: Unable to deploy the composite

Action: Check the associated exception for more information
Level: 1

Type: ERROR

Impact: Deployment

SOA-20021: Undeployment of composite "{0}" failed: {1}.

Cause: There was an error generated during the undeployment of a composite

Action: Check the associated exception for more information concerning the undeployment issue
Level: 1

Type: ERROR

Impact: Deployment

SOA-20025: Failed to find a WSDL Definition for service: "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20026: Failed to find composites to deploy based on path: "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20027: Unable to create interceptors, InterceptorChainFactory may not be defined for "{0}".

Cause: There was a problem creating an interceptor chain associated with the composite

Action: Make sure that the interceptor chain factories are configured in the SOA platform's configuation file located in the fabric war's WEB-INF directory
Level: 1

Type: ERROR

Impact: Deployment

SOA-20028: Unable to create mbeans for the composite "{0}" because of error "{1}".

Cause: There was an error generated during the creation of the composite MBean

Action: Check the associated exception for the cause of the error
Level: 1

Type: ERROR

Impact: Deployment

SOA-20029: Unable to unregister mbean for the composite "{0}" because of error "{1}".

Cause: There was an error while attempting to unregister the composite MBean

Action: Check the associated exception for the cause of the error
Level: 1

Type: ERROR

Impact: Deployment

SOA-20030: Unable to unregister deployed composites runtime mbean because of error "{0}".

Cause: There was an error while attempting to unregister the deployed composites MBean

Action: Check the associated exception for the cause of the error
Level: 1

Type: ERROR

Impact: Deployment

SOA-20031: An active composite for "{0}" has already been registered. Only one active composite is allowed.

Cause: An attempt was made to deploy an active composite for an application that already has an active composite

Action: Make sure that only one active composite is associated with a given application. You can deactive/activate composites via the management consoles
Level: 1

Type: ERROR

Impact: Deployment

SOA-20032: The composite "{0}" is retired. New instances cannot be initiated.

Cause: An attempt was made to initiate a composite instance using a retired composite

Action: Make sure to create a new instance with an active composite. The composite mode can be configured via the management consoles
Level: 1

Type: ERROR

Impact: Deployment

SOA-20034: No composite found for application "{0}", composite name "{1}" and revision "{2}".

Cause: An attempt was made to reload a composite application for which resources can not be found in the metadata repository

Action: Make sure that the application name, composite name, revision, and label specify a valid metadata store
Level: 1

Type: ERROR

Impact: Configuration

SOA-20035: Composite "{0}" has already been loaded.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-20036: Composite "{0}" has been loaded.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-20037: Composite home directory "{0}" does not exist.

Cause: The composite home directory specified is not valid

Action: Make sure the composite home directory specified in deployed-composites.xml is valid
Level: 1

Type: ERROR

Impact: Deployment

SOA-20038: Composite "{0}" does not exist.

Cause: No composite message router was found for the specified composite

Action: Make sure the composite distinguished name specified is valid and that the composite application deployed successfully
Level: 1

Type: ERROR

Impact: Deployment

SOA-20039: Operation not supported.

Cause: An attempt was made to undeploy using the deployment update mechanism

Action: N/A
Level: 1

Type: ERROR

Impact: Deployment

SOA-20040: Message exchange pattern not currently supported.

Cause: The attempted message exchange pattern is not supported

Action: Make sure that the composite wiring is valid
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20041: Deployment failure on rollback: {0}

Cause: An error was raised during an attempt to rollback a composite deployment

Action: Make sure that all composite resources have been removed
Level: 1

Type: ERROR

Impact: Deployment

SOA-20042: Not enough information to ascertain composite name from pathInfo "{0}".

Cause: The path information in the URI was not sufficient enough to identify a composite

Action: Make sure that the URL used to invoke the composite service has the proper application name, composite name, revision, and label
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20043: No deployed composite found for path "{0}".

Cause: The path information in the URI was not sufficient enough to identify a composite

Action: Make sure that the URL used to invoke the composite service has the proper application name, composite name, revision, and label
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20044: Unable to retrieve resource "{0}" associated with composite "{1}".

Cause: An attempt to retrive a composite application associated resource (e.g. a WSDL file) failed

Action: Make sure the URL specified is correct
Level: 1

Type: ERROR

Impact: Deployment

SOA-20045: No WSDL URL provided

Cause: No WSDL URI was specified for the composite associated WSDL

Action: Make sure the WSDL import in the composite file is valid and specifies a URI for the file
Level: 1

Type: ERROR

Impact: Deployment

SOA-20046: Deployment of MBEANS for composite "{0}" failed: {1}.

Cause: There was a problem deploying the composite MBeans

Action: Check the associated exception for more information. There may have been a problem deregistering the MBean during a previous undeployment.
Level: 1

Type: ERROR

Impact: Deployment

SOA-20047: Unable to initialize composite parser: {0}.

Cause: Unable to initialize the composite parser

Action: Make sure that any parser providers registered in the fabric war web.xml file are valid
Level: 1

Type: ERROR

Impact: Configuration

SOA-20048: Unable to discover local host name: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20049: Unable to register composite loader due to exception: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20050: Binding components failed to create holder type for {0}.

Cause: The required holder class is not available on the classpath

Action: Make sure the holder class is available in the classpath
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20051: Return value from the Java Service method {0} is invalid.

Cause: The service returned a value of a different type than was expected

Action: Verify that the service and the WSDL correspond
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20052: Binding Component failed to access holder value for {0}.

Cause: Unable to call a setter/getter on the holder class instance

Action: Make sure the access method is public
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20053: Binding Component is unable to locate operation {0} for java service {1}.

Cause: The requested method does not exist on the target service class

Action: Verify that the target service implements all methods defined in the WSDL
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20054: Binding Component failed to invoke method {0}.

Cause: The requested method of the target service is not public

Action: Verify that the targets service's methods are public
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20055: Missing WebResult method annoation for java service {0}.

Cause: The @WebResult annotation is not defined for the service interface

Action: Make sure the @WebResult annotation is specified in the service interface
Level: 1

Type: ERROR

Impact: Programmatic

SOA-20056: Could not locate service for {0}.

Cause: The requested service is not registered

Action: Make sure the service is registered and named correctly
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20057: Could not find invocation context containing sdo metadata for component {0}.

Cause: The requested service is not registered

Action: Make sure the service is registered and named correctly
Level: 1

Type: ERROR

Impact: Deployment

SOA-20058: Could not find registry for {0}.

Cause: The requested service registry does not exist

Action: Make sure that the registry is available and named correctly
Level: 1

Type: ERROR

Impact: Deployment

SOA-20059: Unable to copy the WSDL definition due to exception

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20060: Partname metadata for the parameter {0} is missing.

Cause: A parameter of a method of the service interface is missing the @PartName annotation

Action: Make sure the @PartName annotation is specified for the parameters of the method
Level: 1

Type: ERROR

Impact: Programmatic

SOA-20061: Input argument {0} has a wrong parameter java type.

Cause: Unable to create an instance of a parameter value

Action: Make sure the parameter classes are available and have default constructors
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20097: Binding component is unable to load schema from this location: {0}

Cause: Could not load an imported schema

Action: Make sure the schema is available in the location specfied in the WSDL
Level: 1

Type: ERROR

Impact: Deployment

SOA-20098: Binding component failed to initialize.

Cause: There was an internal error during initialization

Action: Please contact support
Level: 1

Type: ERROR

Impact: Deployment

SOA-20099: WSDL port metadata in composite {0} not found

Cause: There was an internal error during load

Action: Please contact support
Level: 1

Type: ERROR

Impact: Deployment

SOA-20100: Binding component failed to register Metadata types with SDO provider.

Cause: There was an internal error during load

Action: Please contact support
Level: 1

Type: ERROR

Impact: Deployment

SOA-20101: Metadata for operation {0}, service {1} can not be found.

Cause: The operation was not defined in the service WSDL

Action: Make sure the operation is defined in the service WSDL
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20102: An error occurred while scheduling deployment. Exception reported is "{0}"

Cause: There was an error while attempting to schedule a deployment

Action: Check the associated exception for the cause of the error
Level: 1

Type: ERROR

Impact: Deployment

SOA-20104: The composite for model "{0}" is not found!

Cause: There was an error during retrieval of the service associated composite

Action: Make sure the composite is valid
Level: 1

Type: ERROR

Impact: Configuration

SOA-20106: Binding Component is unable to load schema at "{0}" due to missing system id in the referening source schema.

Cause: Unable to load schema due to missing system id in the referencing WSDL or schema

Action: Ensure the system id is defined in the WSDL
Level: 1

Type: ERROR

Impact: Deployment

SOA-20107: Configuration Error in Java Binding. Unable to find portType or interface.

Cause: Service or port names were not specified in the binding configuration

Action: Make sure the service and port name are available in the binding configuration
Level: 1

Type: ERROR

Impact: Configuration

SOA-20108: The resource "{0}" not found in the composite "{1}"

Cause: Unable to retrieve a resource from the composite's MDS repository

Action: Make sure the resource path specified, relative to composite URI, is correct
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20109: Invocation Exeption: {0}:

Cause: The service generated an error during invocation

Action: Ensure that the service is operating correctly
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20110: This {0} method is not implemented!

Cause: One way operations are not supported for SDO dynamic stubs

Action: Consider using an alternate message exchange pattern
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20111: Binding Component failed to create user defined faults.

Cause: A SOAP fault was generated by the service invocation

Action: Ensure that the service is operating properly. The fault may be expected.
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20112: The called service raised a fault.

Cause: The service generated an exception

Action: Ensure that the service is operating properly
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20113: Unable to access the following endpoint(s): {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20114: Unable to update reference instance with response payload due to exception

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20115: Illegal modification to existing composite {0}. Changes are not allowed to elements of the composite distinguished name (application name, composite name, revision, and label). If you are attempting a re-deployment of a failed deployment, please undeploy and then deploy the composite.

Cause: The attempted change of the deployed composite file was not valid

Action: Make sure the change you are making is allowed
Level: 1

Type: ERROR

Impact: Deployment

SOA-20116: Only changes to policy references of {1} of composite {0} are supported by the Web Service Binding Components. All other changes (e.g. changes to the port attribute of a binding) will be ignored.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-20117: The wire target URI {1}/{2} for composite {0} is not valid. No service {2} is defined for component {1} in its componentType file. Please check the componentType file for component {1} for valid service names.

Cause: The composite wire appears to be malformed since no such component/service pair exists

Action: Please check the componentType file for the component for valid service names.
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20118: The wire source URI {1}/{2} for composite {0} is not valid. No reference {2} is defined for component {1} in its componentType file. Please check the componentType file for component {1} for valid reference names.

Cause: The composite wire appears to be malformed since no such component/reference pair exists

Action: Please check the componentType file for the component for valid reference names.
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20119: Unable to find a WSDL that has a definition for service {0} and port {1}. Please make sure that the port attribute for the binding defined in the composite file is correct by checking the namespace, service name, and port name. In addition, check that the WSDL associated with the binding namespace is imported and currently reachable (check the import nodes at the top of the composite file). Finally, validate the HTTP proxy settings for the server.

Cause: Unable to find a WSDL that has a definition corresponding to the provided service and port names

Action: Please make sure that the port attribute for the binding defined in the composite file is correct by checking the namespace, service name, and port name. In addition, check that the WSDL associated with the binding namespace is imported and currently reachable (check the import nodes at the top of the composite file). Finally, validate the HTTP proxy settings for the server.
Level: 1

Type: ERROR

Impact: Deployment

SOA-20120: Unable to find a composite definition in {0}. Please make sure there is a composite.xml definition file that defines a composite with the same name as the composite name in the composite JAR name.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20121: An attempt was made to deploy a composite '{0}' that has already been deployed. This is an internal error, and does not require any action. The original composite definition remains in effect.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-20122: Unable to find a file named 'adf-config.xml' in the search path starting at {0}. The 'adf-config.xml' file is required to configure the MDS instance used for composite deployment. Repackage the composite application, providing an MDS store a and namespace named after the composite name.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20124: Unable to process the MDS configuration at {0}. Please verify the formatting and contents of the 'adf-config.xml' file. Also, check the rest of the log for MDS failures, which could help point out the root cause of the processing failure.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20125: Cannot create an XSLT transformer. Please ensure that your JAXP environmentis properly configured with an XSLT 1.0 transformer.

Cause: Unable to create the adf-config xml transformer

Action: Make sure the adf-config file is property formatted
Level: 1

Type: ERROR

Impact: Deployment

SOA-20126: Updating MDS configuration at {0} with file-based MDS root {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-20127: Exception when processing MDS configuration.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20128: The context header qname is invalid or malformed. Please check that the correct context header qname is specified for the contextHeadersQNames property in the fabric-config.xml file

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20129: Could not create a context header due to exception

Cause: Unable to create the context header

Action: Ensure that the context provider implementation is valid and working
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20130: Entry Binding Component: invocation of service {0}, operation {1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-20131: External Binding Component: invocation of service {0}, operation {1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-20132: Binding Component found port type: {1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-20133: Binding Component registered the following schema with SDO implementation within context of classloader {1} ==> {0}

Cause:

Action:
Level: 32

Type: TRACE

Impact: Other

SOA-20134: No annotation found on service interface.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20135: Exception creating JAXWS servant. Exception: {0}, Message: {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20136: WS Binding: exception durign SOAP invocation: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20138: No oracle-archive.xml found; will use file scanning for application '{0}'

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20139: Unable to find a registered server for pathInfo {0}. Please ensure that the given composite is deployed. If this is occurring during the processing of a callback, please make sure that the "#" delimeter in the callback URL is properly encoded.

Cause: The path provided in the invocation URI does not map to a deployed composite

Action: Make sure the URI is correct and references a deployed composite application
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20141: Schema validation failed for message part {0}. Please ensure at the message sender level that the data sent is schema compliant.

Cause: Validation of the message part against its schema failed.

Action: Please take actions at the message sender to ensure that the data is schema compliant.
Level: 1

Type: ERROR

Impact: Data

SOA-20143: Unable to register a service endpoint for a defined reference callback. Please ensure the WSDL and reference configuration are correct.

Cause: Unable to register a callback endpoint for the defined reference callback

Action: Make sure that the application configuration is correct. For example, ensure that the associated WSDL does not have any mis-spelled message names.
Level: 1

Type: ERROR

Impact: Configuration

SOA-20144: Unable to find a target component or reference based on invocation context {0}. Plese check the composite file and make sure a wire exists for the specified reference or source URI.

Cause: Unable to find a wire for the reference

Action: Make sure that the service or component reference is actually wired to a target
Level: 1

Type: ERROR

Impact: Deployment

SOA-20145: The serviceName/serviceID attribute is missing.

Cause: Unable to find serviceName attribute for the binding

Action: Make sure that the serviceName is specified in the composite
Level: 1

Type: ERROR

Impact: Deployment

SOA-20146: Unable to deploy service {0} with multiple WS bindings. Please make sure there is only one WS binding for the given service in the composite file.

Cause: Unable to deploy a service with multiple WS bindings

Action: Make sure that the service has only one WS binding
Level: 1

Type: ERROR

Impact: Deployment

SOA-20147: javaInterface attribute for the binding is missing or the inteface class is not available.

Cause: Unable to find javaInterface attribute for the binding

Action: Make sure that javaInterface attribute is specified on the composite
Level: 1

Type: ERROR

Impact: Deployment

SOA-20148: null

Cause: Failure in looking up EJB

Action: Make sure JNDI properties, jndi name specified are correct.
Level: 1

Type: ERROR

Impact: Deployment

SOA-20149: Caller is not in allowed role!

Cause: Failure in authenticating ejb invocation

Action: Make sure invocation client has the right role mapped.
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20150: SOA EJB Invoker could not load bean interface class defined for service {0}.

Cause: Failure in loading ejb interface class

Action: Make sure interface class is included in the deployment package.
Level: 1

Type: ERROR

Impact: Deployment

SOA-20151: SOA EJB Invoker could not locate composite for service {0}.

Cause: Failure in locating composite

Action: Make sure the composite configuration is correct
Level: 1

Type: ERROR

Impact: Configuration

SOA-20152: SOA EJB Invoker could not locate method named {0} with {1} of arguments on interface class {2} for service.

Cause: Failure in locating method

Action: Make sure the composite configuration is correct
Level: 1

Type: ERROR

Impact: Configuration

SOA-20153: Failure in processing jps credential store properties, exception stack: {0} .

Cause: Failure in processing credential store properties

Action: Make sure the properties are specified correctly or permission to access the the store has been setup.
Level: 1

Type: ERROR

Impact: Configuration

SOA-20154: The path "{0}" has already been used by another direct binding. Please select a different path override.

Cause: Illegal pathOverride used in composite configuration. The alias name has already been used for other another direct binding.

Action: Select a different path alias for the direct binding component.
Level: 1

Type: ERROR

Impact: Configuration

SOA-20155: Expected protocol 'soadirect, got ' {0} + ' instead.

Cause: Illegal protocol used in direct binding composite configuration.

Action: Correct path should start with "soadirect"
Level: 1

Type: ERROR

Impact: Configuration

SOA-20156: Invalid service path "{0}".

Cause: Service Path used in the invocation is invalid.

Action: Correc the service path.
Level: 1

Type: ERROR

Impact: Configuration

SOA-20157: Service not found for path "{0}".

Cause: Service not found for the path name used in the invocation.

Action: Check composite configuration to see if the path name used matches.
Level: 1

Type: ERROR

Impact: Configuration

SOA-20158: Direct binding component failed to initialize.

Cause: Exception occured during the direct binding component initialization.

Action: Check the exception for detailed failure cause.
Level: 1

Type: ERROR

Impact: Configuration

SOA-20159: Direct binding component not initialized.

Cause: Direct binding component has not been initialized.

Action: Check server startup log to see any detailed exception log.
Level: 1

Type: ERROR

Impact: Configuration

SOA-20160: Could not obtain keystore location or password

Cause: Could not obtain the keystore location or password for setting up 2 Way SSL

Action: Make sure that the keystore is available in the default location or is specified in the SOA configuration. In addition, make sure the keystore password is configured in the credential store.
Level: 1

Type: NOTIFICATION

Impact: Configuration

SOA-20161: Unable to create SSL Socket Factory

Cause: Could not create the SSLSocketFactory for supporting 2 Way SSL

Action: Check the associated exception for the cause of the failure.
Level: 1

Type: ERROR

Impact: Network

SOA-20168: Could not find a port for the dynamic reference given service name {0} and port type {1}

Cause: Could not find a port that matched the supplied service name and port type for the dynamic reference

Action: Check the dynamic reference configuration and the supplied WSDL to ensure proper configuration.
Level: 1

Type: ERROR

Impact: Configuration

SOA-20169: Folder {0} is not able to process messages. The folder state is set to "off". The folder can be turned "on" by using the administrative consoles.

Cause: The folder state or mode do not allow processing of messages

Action: Use the management consoles to set the mode and state of the folder to enable processing
Level: 1

Type: ERROR

Impact: Configuration

SOA-20170: Partition {0} does not exist. Make sure the partition was created and exists.

Cause: The folder can not be found

Action: Check the folder name and make sure such a folder was created and exists
Level: 1

Type: ERROR

Impact: Configuration

SOA-20171: Cannot find port type {0} in the WSDL. Make sure the port type is defined in the WSDL

Cause: The port type cannot be found

Action: Check the WSDL and make sure the port type is defined in the WSDL
Level: 1

Type: ERROR

Impact: Configuration

SOA-20172: No source URI specified for the given invocation or callback. Please make sure there is a wire specified for the context {0}.

Cause: No source URI for the wire

Action: Check the composite and make sure a wire is defined for the interaction.This is most likely an indication of an error in the wiring.
Level: 1

Type: ERROR

Impact: Configuration

SOA-20173: @WebService or @PortableWebService annotation is required, but not found on {0}.

Cause: Interface class does not contain @WebService annoation.

Action: Add @WebService annotation that describes the service in the interface class.
Level: 1

Type: ERROR

Impact: Configuration

SOA-20174: Failed to get application helper context using service id '{0}'.

Cause: Unable to create application helper context.

Action: Check the underlying cause from the SDO implementation.
Level: 1

Type: ERROR

Impact: Programmatic

SOA-20175: Binding property {0} overridden by a message property of the same name.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20176: Both csf-key and username/password have been set. The csf-key will be used for authentication processing.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20177: Could not lookup the service endpoint from UDDI either due to a UDDI connection error or the provided ServiceKey {0} was invalid.

Cause: Could not lookup service endpoint from UDDI. Either by error on UDDI connection or invalid ServiceKey

Action: Check the OSR-UDDI inquiryUrl configuration and the supplied ServiceKey to ensure proper configuration.
Level: 1

Type: ERROR

Impact: Configuration

SOA-20178: Failed to initialize ADR home directories.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20204: Failed to register SOA diagnostic dumps, DFW (diagnostic framework) not available.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20205: Failed to deregister SOA diagnostic dumps, DFW (diagnostic framework) not available.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20206: Failed to deregister SOA diagnostic dumps, local soa dumps registry not available.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20207: No MBean server found, can not register SOA dump: soa.env.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20208: Can not find facade locator, the following SOA diagnostic dumps not registered: {0}, {1}, {2}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20209: Failed to look up SOA data source: jndi = [{0}], soa.db dump can not be registered.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20210: SOA data source not available (NULL), soa.db dump not registered.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20211: JNDI context not available, can not look up SOA data source, no DB dump (soa.db) registration.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20212: Not registering SOA incident rules file.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20213: Not unregistering SOA incident rules file {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-20214: Not registering custom incident rules file {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-20215: Not unregistering custom incident rules file {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-20252: No binding found for reference [{1}] of composite [{0}]. A callback endpoint can not be created. Please make sure the composite is deployed to this server.

Cause: There is no reference binding available or deployed

Action: Check that the composite deployment completed successfully and is targeted for this server.
Level: 1

Type: ERROR

Impact: Deployment

SOA-20253: The composites {0} failed during server startup. Please check the logs for more information.

Cause: Composites failed in deployment during server restart

Action: Check the associated exception for more information
Level: 1

Type: ERROR

Impact: Deployment

SOA-21500: Error occured when creating target MDS instance.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21501: Error occured when rolling back MDS label.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21502: Error occured when creating MDS label.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21503: MDS store of namespace {0} does not have versioning support. Cannot be used in MAS based deployment.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21504: Only single composite is supported in a SAR archive.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21505: Invalid composite name in undeploy: {0}, both composite name and revision need to be specified.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21506: Cannot find revision in undeploy : {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21507: Error reading deployed-composites.xml.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21508: Cannot find composite deployment coordinator.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21509: Error in reading data from deployer client.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21510: There was an error deploying the composite on {1}: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21511: Cannot find archive: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21512: Data transfer error in MDS.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21513: Command {0} not supported.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21514: MDS Transfer directory {0} already exists for composite {1}. Removing and replacing to deploy new version of composite.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-21515: Cannot find composite {0} in sar file : {1}. Abort deployment.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21516: Cannot find base composite for: {0}. Abort redeployment.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21517: Composite with same revision ID already exists: {0}. Please set the overwrite flag or use different revision ID. Abort deployment.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21518: Protocol {0} is not supported. Only http is supported.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21519: Error parsing composite {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21520: Cannot find shared data archive: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21521: Error removing archive data from MDS for composite: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21522: Error occurs in applying deployment plan {1} to sar file: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21523: Composite {0} cannot be automatically set as default due to state: {1} or mode: {2}. The state needs to be on and the mode needs to be active.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-21524: Error occured in processing sar file {0} before transfering into MDS store. Please make sure the sar file is a valid jar file.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21525: Cannot find JPS context: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21526: Error occurs in checking JPS role.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21527: User {0} doesn't have the privilege of deploying/undeploying composites. Only users of SOAAdmin/SOAOperator role are authorized to deploy/undeploy composites.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21528: There was an error undeploying composite on {1}: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21529: There was an error deploying/undeploying composite on {1}: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21530: CompositeDeploymentServlet-----> received request from user: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21531: CompositeDeploymentServlet-----> completed deployment/undeployment successfully. Time spent: {0} sec.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21532: CompositeDeploymentServlet initialized.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-21533: User [{0}] has been successfully authorized.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21534: Start unzipping data to base directory: {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21535: Complete unzipping data.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21536: Calling DeployManager to attach deployplan: {0} to SAR file: {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21537: Sending back error message: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21538: Removing temporary directory: {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21539: Perform deployment operation with redeploy flag: {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-21540: Perform undeployment operation: {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21541: Calling coordinator to undeploy {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21542: Undeploying revision: {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-21543: Deploying SAR file: {0} to domain: {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21544: Deploying shared data file: {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21545: Calling coordinator to deploy {0}, with isForceDefault flag: {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21546: Calling coordinator to update composite. base composite: {0}, new composite: {1}, isForceDefault flag: {2}, keepInstancesOnRedeploy flag: {3}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21547: AutoDeployer-> starting deploying shared data file: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21548: AutoDeployer-> shared data file {0} was successfully deployed. Time spent: {1} sec. This file will be removed.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21549: AutoDeployer-> starting deploying SAR file: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21550: AutoDeployer-> SAR file {0} was successfully deployed. Time spent: {1} sec. SAR file will be removed.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21551: AutoDeployer-> removing temporary MDS data directory {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21552: Preparing transfering data into MDS for package: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21553: Transfered data into MDS successfully for package: {0}. Transfered size: {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21554: Removed extra data from MDS successful for package: {0}. Removed size: {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21555: Preparing removing data from MDS for package: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21556: Removed data from MDS successfully for package: {0}. Removed size: {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21560: Cannot remove temporary directory: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-21561: Removing label {0} in namespace {1} of MDS storage

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21562: Composite from sar file: {0} already exists in the target server. Will NOT attempt redeployment and this sar file will be removed from the autodeploy directory.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21563: The composite ({0}) imported a shared library: {1}/{2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21564: The classloader for the shared library ({1}/{2}) referenced by the composite ({0}) cannot be found.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-21566: There was an error exporting composite on {1}: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21567: Sending back jar file: {0} of length: {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21568: CompositeDeploymentServlet-----> completed exporting composite {0} successfully. Time spent: {1} sec.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21569: CompositeDeploymentServlet-----> completed exporting post deployment updates {0} successfully. Time spent: {1} sec.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21570: CompositeDeploymentServlet-----> completed importing post deployment updates {0} successfully. Time spent: {1} sec.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21571: There was an error exporting post deployment changes on {1}: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21572: There was an error importing post deployment changes on {1}: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21573: CompositeDeploymentServlet-----> completed exporting shared data of pattern {0} successfully. Time spent: {1} sec.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21574: There was an error exporting shared data on {1}: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21575: adf-config.xml file cannot be null.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21576: Cannot find adf-config file: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21577: Cannot get adf-config file URL: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21578: Cannot create SOA MDS instance.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21579: Cannot find composite: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21580: Cannot find deployed-composites.xml.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21581: The composite name in composite.xml of the jar file: {0} does not match the composite name to be updated: {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21582: The composite revision in composite.xml of the jar file: {0} does not match the composite revision to be updated: {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21583: Composite does not exist, cannot import updates: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21584: Composite label cannot be null: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21585: Error read deployed-composites.xml: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21586: Cannot find deployed-composites.xml to save.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21587: Cannot update deployed-composites.xml.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21588: There was an error removing shared data on {1}: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21589: CompositeDeploymentServlet-----> completed removing shared data of folder {0} successfully. Time spent: {1} sec.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21590: Error occurred when modifying the revision in composite.xml.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21591: Cannot find Fabriclifecycle: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21592: SOA platform is not fully started. Please retry later.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21593: Calling coordinator to deploy resource files.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21598: Calling coordinator to patch composite {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-22000: The shared library "{0}" is not deployed; Thus, it cannot be redeployed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-22001: The shared library "{0}" is already deployed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-22002: Deploying new shared library: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-22003: Redeploying shared library: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-22004: Found shared library "{0}" in the MDS respository

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-22005: Found version {1} of shared library "{0}" in the MDS repository

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-22006: {0} was removed from the MDS repository

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-22007: {0} was not removed from the MDS repository

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-22008: {0} was not removed from the MDS repository (It may not be empty)

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-22009: Failed to remove shared library {0}/{1} from the MDS repository

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-22010: SharedLibraryDeploymentCoordinator not found

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-22011: {0} is not a directory

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-22012: Failed to delete {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-22013: {0} does not exist, so nothing to delete.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-22014: Shared library {0}/{1} has subscribers.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-22015: The shared library {0}/{1} cannot be undeployed because it is referenced by one or more composites: {2}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-22016: A shared library classloader named {0} was created for {1}/{2}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-22017: The classloader {0} for shared library {1}/{2} has been committed.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-22018: The following codesources were added to the shared library ({0}/{1}) classloader: {2}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-22019: The classloader {0} for shared library {1}/{2} has been closed.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-25000: set user and password...

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25001: set config plan...

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25002: sarLocation cannot be found: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25003: ---->Deploying composite success.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25004: ---->Response code={0}, error:{1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25005: Exception:{0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25006: ---->Undeploying composite ({0}) success.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25007: Config plan was successfully attached.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25008: Must provide a sar file or composite.xml.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25009: Config plan file already exists, please provide overwrite as true to overwrite the file.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25010: Config plan was successfully generated.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25011: Config plan was successfully extracted.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25012: Config plan was successfully validated.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25013: Report file already exists, please provide overwrite as true to overwrite the file.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25014: Ant script does not exist: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25015: oracle.home is not available. Please provide this property.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25016: Cannot find ANT script $oracle.home/bin/ant-sca-compile.xml.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25017: Invoking ANT script: {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25018: Cannot find ANT script $oracle.home/bin/ant-sca-package.xml.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25019: Cannot find ANT script $oracle.home/bin/ant-sca-test.xml.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25020: Cannot find composite lifecycle mbean.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25021: Composite ({0}) is successfully started.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25022: Composite ({0}) is successfully stopped.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25023: Composite ({0}) is successfully activated.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25024: Composite ({0}) is successfully retired.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25025: Composite ({0}) is successfully set as default composite.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25026: Invalid update type: {0}, please choose among: none/all/property/runtime.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25027: Removing existing sar file: {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25028: ---->Export composite success.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25029: Invalid update type: {0}, please choose among: all/property/runtime.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25030: Removing existing jar file: {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25031: ---->Export updates success.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25032: ---->Cannot find post deployment property updates.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25033: ---->Cannot find post deployment runtime/metadata updates.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25034: ---->Cannot find any post deployment updates.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25035: ---->Import updates success.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25036: ---->Export shared data success.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25037: ---->Cannot find shared data of given pattern: {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25038: Calling composite store mbean to export composite...

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25039: Composite was successfully exported.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25040: Calling composite store mbean to export composite with all post deployment updates ...

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25041: Composite with all post deployment updates was successfully exported.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25042: Calling composite store mbean to export composite with property post deployment updates ...

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25043: Composite with property post deployment updates was successfully exported.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25044: Calling composite store mbean to export composite with runtime post deployment updates ...

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25045: Composite with runtime post deployment updates was successfully exported.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25046: No connection to a server exists. This operation can be executed only in the online mode.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25047: INFO: SOA server down, use domain runtime mbean...

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25048: Cannot find composite store mbean on this server.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25049: Calling composite store mbean to export all post deployment updates, if any...

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25050: All post deployment updates of the composite was successfully exported.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25051: Calling composite store mbean to export property post deployment updates, if any...

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25052: Property post deployment updates of the composite was successfully exported.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25053: Calling composite store mbean to export runtime post deployment updates, if any...

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25054: Runtime post deployment updates of the composite was successfully exported.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25055: Calling composite store mbean to import post deployment updates...

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25056: Post deployment updates was successfully imported.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25057: Calling composite store mbean to export shared data...

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25058: Shared data was successfully exported.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25059: ---->Remove shared data success.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25060: Partition was successfully created.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25061: Cannot find folder lifecycle mbean on this server.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25062: Partition was successfully deleted.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25063: All composites in the partition were successfully started.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25064: All composites in the partition were successfully stopped.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25065: All composites in the partition were successfully activated.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25066: All composites in the partition were successfully retired.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25067: Cannot find jar file: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25068: Merge completed successfully, created merged updates in jar file: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25069: Merge completed but no jar file created, check log file for details: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-25070: Found multiple composite store mbeans.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25071: Found multiple domain runtime composite store mbeans.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25072: Cannot find composite store mbean on this server.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25073: start composite operation failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25074: Found multiple composite lifecycle mbeans.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25075: Cannot find composite lifecycle mbean on this server.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25076: stop composite operation failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25077: activate composite operation failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25078: retire composite operation failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25079: assign default composite operation failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25080: get default composite revision operation failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25081: list deployed composites operation failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25082: list composites in partition operation failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25083: create partition operation failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25084: Found multiple folder mbeans.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25085: delete partition operation failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25086: start composites in partition operation failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25087: stop composites in partition operation failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25088: activate composites in partition operation failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25089: retire composites in partition operation failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25090: list all partitions operation failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25091: Found multiple EDNConfig mbeans.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25092: Cannot find EDNConfig mbean on this server.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25093: EDN event delivery is successfully enabled.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25094: enable EDN events operation failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25095: EDN event delivery is successfully disabled.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25096: disable EDN events operation failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25097: SOA Platform is running and accepting requests.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25098: SOA Platform is not ready: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-30000: Received event: Subject: {2} Sender: {1} Event: {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-30001: Error closing queue connection

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-30002: Error shutting down

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-30003: Error enqueueing event

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-30004: Error closing queue session

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-30005: Invalid consistency level {2} for event {0} to {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-30006: No processor registered for target {0}

Cause: No business event processor is registered for the target

Action: Make sure the service engine or event target supports business events
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-30007: Processor threw exception "{2}" during onEvent for event {0} sent to {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-30008: Sent event {1} to {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-30009: Ignored event named {1} from {0} to supress potential infinite recurison

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-31000: Received event: Subject: {2} Sender: {1} Event: {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-31001: Error closing queue connection

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-31002: Error shutting down

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-31003: Error enqueueing event

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-31004: Error closing queue session

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-31005: Invalid consistency level {2} for event {0} to {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-31006: No processor registered for target {0}

Cause: No business event processor is registered for the target

Action: Make sure the service engine or event target supports business events
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-31007: Processor threw exception "{2}" during onEvent for event {0} sent to {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-31008: Sent event {1} to {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-31009: Ignored event named {1} from {0} to supress potential infinite recurison

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-31033: Sent OAOO event [QName: "{1}" to target: "{0}"]: {2}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

88 SSL-28750 to SSL-29249

SSL-28750: unknown error

Cause: An Oracle Security Server error of an unspecified type occurred.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-28751: memory allocation failure

Cause: The allocation of memory failed due to insufficient system memory.

Action: Terminate other processes to free up memory or add memory to the system.
Level: 00001

Type: ERROR

Impact: Other

SSL-28752: data source initialization failure

Cause: A data source failed to initialize. Frequently, this error is caused by insufficient system resources.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-28753: failure to terminate use of data source

Cause: The system failed to terminate its use of a data source. This error may have been caused by memory or disk corruption, among other things.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-28755: object retrieval failure

Cause: The system failed to retrieve information from a file or a database.

Action: Check if the data source exists, or check to ensure that the correct information exists.
Level: 00001

Type: ERROR

Impact: Other

SSL-28756: callback failure to allocate memory

Cause: A function supplied by the caller failed to allocate memory. This error could have been caused by system memory exhaustion.

Action: Terminate other processes to free up memory or add memory to the system.
Level: 00001

Type: ERROR

Impact: Other

SSL-28757: system attempt to allocate 0 bytes of memory

Cause: The system attempted to allocate 0 bytes of memory because there was no available memory left to allocate. This error could have been caused by insufficient system memory.

Action: Terminate other processes to free up memory or add memory to the system.
Level: 00001

Type: ERROR

Impact: Other

SSL-28758: memory release failure

Cause: The release of a memory fragment failed. This may be due to memory corruption either within the application or in the Oracle Security Server library.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-28759: failure to open file

Cause: The system could not open the specified file.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-28763: Invalid parameter type found in configuration file.

Cause: A parameter in the sqlnet.ora file may have been specified incorrectly.

Action: Check the sqlnet.ora file for this parameter value.
Level: 00001

Type: ERROR

Impact: Other

SSL-28764: failure to retrieve a configuration parameter

Cause: The system failed to retrieve a configuration parameter from the sqlnet.ora file. This error may have occurred because a necessary configuration parameter was not specified in the sqlnet.ora file.

Action: Supply the needed configuration parameter in the sqlnet.ora file.
Level: 00001

Type: ERROR

Impact: Other

SSL-28766: failure to terminate use of data source

Cause: The system failed to terminate its use of a data source. This error may have been caused by memory or disk corruption, or a system error.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-28767: invalid version number

Cause: Version number of the wallet was incorrect. A corrupt wallet or an incompatible wallet was provided.

Action: Ensure that proper wallet is being used.
Level: 00001

Type: ERROR

Impact: Other

SSL-28768: bad magic number

Cause: An invalid magic number was specified in a data file. This could have been caused by a corrupted disk or by some other process overwriting the file.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-28769: Specified method does not exist.

Cause: The data access method that was specified in the configuration file is not supported.

Action: Specify a supported method. Consult the Oracle Security Server documentation to determine the supported types.
Level: 00001

Type: ERROR

Impact: Other

SSL-28770: Data source is already initialized.

Cause: The caller attempted to initialize a data source which was already initialized.

Action: This is a programming error. An application should not attempt to initialize a data source more than once.
Level: 00001

Type: ERROR

Impact: Other

SSL-28771: Data source is not yet initialized.

Cause: The caller attempted to use a data source which had not yet been initialized.

Action: This is a programming error. The application must always initialize the data source before it can be used.
Level: 00001

Type: ERROR

Impact: Other

SSL-28773: failure to write magic and version numbers

Cause: Both the magic and version numbers failed to write. This usually occurs because of insufficient disk space.

Action: Delete unnecessary files to free up disk space or add disk space to the system.
Level: 00001

Type: ERROR

Impact: Other

SSL-28774: file cannot write to disk

Cause: The output of a file failed. This error usually occurs because of insufficient disk space.

Action: Delete unnecessary files to free up disk space or add disk space to the system.
Level: 00001

Type: ERROR

Impact: Other

SSL-28775: file cannot close

Cause: Failed to close a file which is used by a data access method. This error usually indicates memory corruption or a system error.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-28776: Output buffer supplied is too small.

Cause: The data returned by a function was too large for the supplied buffer.

Action: Call the routine again with a larger buffer.
Level: 00001

Type: ERROR

Impact: Other

SSL-28777: binding creation failure

Cause: Failed to create a binding for use in the parsing of a parameter value. This error can be caused by the parameter value being in an incorrect format, such as a right parenthesis was not supplied where expected, or due to insufficient system memory.

Action: Make sure that the parameter is specified in the correct format. If the format is correct, free up system memory by terminating processes or adding more memory.
Level: 00001

Type: ERROR

Impact: Other

SSL-28778: Configuration parameter is not specified in the proper format.

Cause: The configuration parameter was not specified in the proper format.

Action: Consult the Oracle Security Server documentation for a description of the proper format for this parameter.
Level: 00001

Type: ERROR

Impact: Other

SSL-28779: no data access method specified in parameter

Cause: No method for data access was specified in the parameter value.

Action: Specify a method for data access in the parameter. Consult the Oracle Security Server documentation for the supported data access methods for this data type.
Level: 00001

Type: ERROR

Impact: Other

SSL-28780: invalid data access method specified by the parameter

Cause: The data access method specified by the parameter value is not supported.

Action: Specify a supported data access method. Consult the Oracle Security Server documentation for the supported data access methods for this data data type.
Level: 00001

Type: ERROR

Impact: Other

SSL-28781: No data for the access method is specified in the parameter.

Cause: No data was specified in the parameter for use with the specified access method.

Action: Consult the Oracle Security Server documentation for the data that must be specified for the access method.
Level: 00001

Type: ERROR

Impact: Other

SSL-28782: data source is not allocated

Cause: No memory was allocated for a data source.

Action: Ensure that the application calls in the data source initialization function.
Level: 00001

Type: ERROR

Impact: Other

SSL-28783: invalid parameter

Cause: There was no match for the parameter name that was used in the configuration file.

Action: Check your sqlnet.ora file for the correct parameter name.
Level: 00001

Type: ERROR

Impact: Other

SSL-28784: file name translation failure

Cause: The translation of a file name from Oracle format to native format has failed.

Action: Specify a correct file name. Consult your Oracle documentation for the correct file name format.
Level: 00001

Type: ERROR

Impact: Other

SSL-28785: parameter does not exist

Cause: A necessary configuration parameter was not found in the parameter file.

Action: Supply the required parameter.
Level: 00001

Type: ERROR

Impact: Other

SSL-28786: decryption of encrypted private key failure

Cause: An incorrect password was used to decrypt an encrypted private key.

Action: Enter the correct password.
Level: 00001

Type: ERROR

Impact: Other

SSL-28787: private key encryption failure

Cause: This may have been caused by an error in the mkwallet parameter of the sqlnet.ora file.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-28788: user provided invalid information

Cause: User may have responded to a prompt with unexpected input, or an unknown error occurred.

Action: Enter correct input, or enable tracing to check the trace file for errors.
Level: 00001

Type: ERROR

Impact: Other

SSL-28790: NLS string open failure

Cause: The opening of a string for use by the NLS subsystem failed.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-28791: certificate verification failure

Cause: Verification of the certificate, which the user supplied, failed.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-28794: data type attribute did not initialize

Cause: The initialization of the attribute data type failed. This error may be due to insufficient system resources.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-28795: data type attribute did not terminate

Cause: The termination of the use of the attribute data type subsystem failed.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-28796: access method is not supported

Cause: The method specified to access data is not supported.

Action: Use a supported access method. Consult your Oracle documentation to determine which access methods are supported.
Level: 00001

Type: ERROR

Impact: Other

SSL-28797: invalid key data type

Cause: The type specified for a key is not supported.

Action: Correct the key type. Consult your Oracle documentation to determine which key types are supported.
Level: 00001

Type: ERROR

Impact: Other

SSL-28800: data source failed to open

Cause: A data source (a file or a database) failed to open.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-28802: invalid mode or data source in configuration file

Cause: An invalid mode or data source has been specified in the configuration file (sqlnet.ora).

Action: Check the method parameter in the sqlnet.ora file. If the parameter value is correct, then enable tracing to determine the exact error.
Level: 00001

Type: ERROR

Impact: Other

SSL-28803: I/O operation failure

Cause: The system or application failed to access a data source (file or database).

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-28804: Data source cannot close.

Cause: The data source, which could be either a file or a database), failed to close.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-28805: Cannot retrieve information from the data source.

Cause: The system or application failed to retrieve information from the data source (file or database).

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-28806: Cannot write to the data source.

Cause: The system or application failed to write to the data source (file or database).

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-28807: Cannot update the data source.

Cause: The system or application failed to update the data source (file or database).

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-28808: Cannot retrieve method information from the configuration file.

Cause: The system or application failed to retrieve method information from the sqlnet.ora configuration file.

Action: Check the method configuration parameters in the sqlnet.ora file. If the method configuration parameters are correct, then enable tracing to determine the exact error.
Level: 00001

Type: ERROR

Impact: Other

SSL-28809: Cannot delete information from the data source.

Cause: The system or application failed to delete information from the data source (file or database).

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-28810: Cannot create key descriptor.

Cause: The system failed to create a key descriptor.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-28814: Cannot convert a number in Oracle format to native format.

Cause: Failed to convert a number from Oracle format to native format.

Action: This is an internal programming exception. Enable tracing to try and reproduce the problem. Contact Oracle customer support and supply the trace file.
Level: 00001

Type: ERROR

Impact: Other

SSL-28815: Cannot convert a number in native format to Oracle format.

Cause: Failed to convert a number from native format to Oracle portable format failed.

Action: This is an internal programming exception. Enable tracing to try and reproduce the problem. Contact Oracle customer support and supply the trace file.
Level: 00001

Type: ERROR

Impact: Other

SSL-28818: No package context provided.

Cause: The context that holds the state of the security package was not passed to a function or procedure that was expecting it.

Action: This is an internal error. Enable tracing to find more information. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-28836: Wallet is not open.

Cause: The wallet to be used has not yet been opened.

Action: Call the function that opens the wallet.
Level: 00001

Type: ERROR

Impact: Other

SSL-28840: Wallet is already open.

Cause: An attempt was made to open a wallet that was already open.

Action: This is a programming error. A wallet should only be opened once.
Level: 00001

Type: ERROR

Impact: Other

SSL-28841: Operation is not supported.

Cause: An attempt was made to perform an operation that is not supported.

Action: This is a programming error. Please refer to Oracle documentation to determine which operations are supported.
Level: 00001

Type: ERROR

Impact: Other

SSL-28842: Incorrect file permissions

Cause: The subject file did not have the correct permissions for the operation.

Action: Ensure that the file permissions allow the current operation.
Level: 00001

Type: ERROR

Impact: Other

SSL-28843: Operating system error while creating/opening file

Cause: An operating system dependent error occurred while trying to create/ open the file or while trying to set the appropriate permissions on the file.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-28844: No wallet present

Cause: There was no wallet in the location specified.

Action: Check to ensure that the wallet is in the correct directory location.
Level: 00001

Type: ERROR

Impact: Other

SSL-28845: No certificate

Cause: Either there is no certificate or the system cannot find it.

Action: Check to ensure that the certificate is in the specified wallet.
Level: 00001

Type: ERROR

Impact: Other

SSL-28846: No private key

Cause: Either there is no private key or the system cannot find it.

Action: Check to ensure that the private key is in the specified wallet.
Level: 00001

Type: ERROR

Impact: Other

SSL-28847: No clear private key file

Cause: Failed to retrieve private key from SSO wallet

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-28848: No encrypted private key file

Cause: Failed to retrieve private key from the wallet

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-28849: No Trustpoints

Cause: The wallet does not have any trusted certificates

Action: Ensure that the wallet/keystore has trusted certificates.
Level: 00001

Type: ERROR

Impact: Other

SSL-28853: Initialization failure

Cause: Either initialization or module loading has failed.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-28854: Memory allocation failure

Cause: The allocation of memory failed due to insufficient system memory.

Action: Terminate other processes to free up memory or add memory to the system.
Level: 00001

Type: ERROR

Impact: Other

SSL-28855: Unsupported SSL operation

Cause: An unsupported operation was attempted, for example, an attempt was made to select a mode of operation that is not allowed.

Action: Refer to the SSL chapter in the product's documentation.
Level: 00001

Type: ERROR

Impact: Other

SSL-28857: Unknown SSL error

Cause: An unknown SSL error occurred.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-28858: SSL protocol error

Cause: An error occurred while negotiating the SSL handshake between two processes.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-28859: SSL negotiation failure

Cause: An error occurred during negotiation between two processes as part of the SSL protocol. This error will occur if the two sides to the connection do not support a common cipher suite.

Action: Configure each process so they support a common cipher suite. Then attempt the connection again. If error occurs again, enable tracing and retry the connection. Then contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-28860: Fatal SSL error

Cause: An error occurred during the SSL connection to the peer. It is likely that this side sent data which the peer rejected.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-28861: SSL connection would block

Cause: This error is informational. It should never be communicated to the user.

Action: Enable tracing and retry the connection to determine the exact cause of the error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-28862: SSL connection failed

Cause: This error occurred because the peer closed the connection.

Action: Enable tracing on both sides and examine the trace output. Contact Oracle Customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-28863: SSL session not found

Cause: This error is informational. It indicates that a specified session does not exist.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-28864: SSL connection closed gracefully

Cause: This error is informational. It indicates that the connection closed without error.

Action: This error is not normally visible to the user. Enable tracing and retry the connection. If the error persists, contact Oracle customer support.
Level: 00001

Type: ERROR

Impact: Other

SSL-28865: SSL connection closed

Cause: The SSL connection closed because of an error in the underlying transport or because the peer process quit unexpectedly.

Action: Enable tracing and retry the connection. The trace output should indicate how the failure occurred.
Level: 00001

Type: ERROR

Impact: Other

SSL-28866: Invalid peer certificate encoding

Cause: A field from a certificate in the peer's certificate chain could not be recognized.

Action: Refer to Oracle Wallet Manager documentation to find out how to obtain the peer's certificate. Then contact Oracle customer support with the peer's certificate chain.
Level: 00001

Type: ERROR

Impact: Other

SSL-28867: Integer value is too big.

Cause: The certificate presented had an integer field whose value was too large.

Action: Refer to Oracle Wallet Manager documentation to find out how to obtain the peer's certificate. Then contact Oracle customer support with the peer's certificate chain.
Level: 00001

Type: ERROR

Impact: Other

SSL-28868: Peer certificate chain check failed.

Cause: The check of the certificate list presented by the peer failed. Possible causes include: 1. the expiration of one of the certificates; 2. a certificate authority in a certificate was not recognized as a trust point; 3. the signature in a certificate could not be verified.

Action: Refer to Oracle Wallet Manager documentation to find out how to open your wallet and ensure that: 1. all of the certificates installed in your wallet are current 2. a certificate authority's certificate from your peer's certificate chain is added as a trusted certificate in your wallet
Level: 00001

Type: ERROR

Impact: Other

SSL-28869: Peer's certificate is expired.

Cause: The certificate being used to authenticate a client or server has expired.

Action: Obtain a new certificate, which is unexpired, and attempt the connection again.
Level: 00001

Type: ERROR

Impact: Other

SSL-28870: Name comparison failure

Cause: A comparison of the names contained in two certificates failed.

Action: This error is not normally visible to the user. Enable tracing and retry the connection. If the error persists, contact Oracle customer support.
Level: 00001

Type: ERROR

Impact: Other

SSL-28871: Peer certificate chain is incomplete.

Cause: The peer certificate chain presented was incomplete because it did not end with a self-signed root certificate.

Action: Refer to Oracle Wallet Manager documentation to find out how to open your wallet and ensure that: 1. the certificate authority's root certificate is self-signed. 2. a certificate authority's certificate from your peer's certificate chain is added as a trusted certificate in your wallet
Level: 00001

Type: ERROR

Impact: Other

SSL-28872: Invalid peer certificate format

Cause: The peer certificate does not conform to the X.509v3 standard.

Action: Refer to Oracle Wallet Manager documentation to find out how to get the peer certificate. Then contact Oracle customer support with the peer's certificate.
Level: 00001

Type: ERROR

Impact: Other

SSL-28874: SSL: I/O closed - override goodbye kiss

Cause: This error is informational. It indicates that the connection closed without error.

Action: This error is not normally visible to the user. Enable tracing and retry the connection. If the error persists, contact Oracle customer support.
Level: 00001

Type: ERROR

Impact: Other

SSL-28875: SSL: use server-gated cryptographic suites

Cause: This is used as a internal status indicator and not really an error.

Action: This message is not normally visible to the user. Enable tracing and retry the connection. If the error persists, contact Oracle customer support.
Level: 00001

Type: ERROR

Impact: Other

SSL-28876: Internet Explorer SGC Error

Cause: An error occurred when processing a certificate sent from Microsoft Internet Explorer.

Action: This error is not normally visible to the user. Enable tracing and retry the connection. If the error persists, contact Oracle customer support.
Level: 00001

Type: ERROR

Impact: Other

SSL-28879: no protocol side set

Cause: An application attempted to provide credentials to an SSL connection but had not previously stated whether the process was a client or a server.

Action: This error is not normally visible to the user. Enable tracing and retry the connection. If the error persists, contact Oracle customer support.
Level: 00001

Type: ERROR

Impact: Other

SSL-28884: invalid cipher suite

Cause: An invalid cipher suite string has been specified in the product's configuration file.

Action: Refer to the product documentation for information about supported cipher suites.
Level: 00001

Type: ERROR

Impact: Other

SSL-28885: No certificate with the required key usage found.

Cause: Certificate not created with the appropriate X509v3 key usage extension.

Action: Refer to Oracle Wallet Manager documentation to find out the supported key usages.
Level: 00001

Type: ERROR

Impact: Other

SSL-28890: Entrust Login Failed

Cause: An application failed to log in to an Entrust Profile. Possible causes include: 1. Entrust Admin/Authority was not online. 2. Invalid password for Entrust profile was specified. 3. Invalid path to Entrust profile was specified 4. Invalid Entrust initialization file was specified. 5. Entrust Server Login program was not executed (server-side only).

Action: Make sure that 1. Entrust Authority is online; 2. Password for Entrust profile is specified correctly; 3. Path to Entrust profile is specified correctly; 4. A valid Entrust initialization file is provided; 5. Entrust Server Login program is run before the database startup. For more information, enable tracing and examine the trace output to get exact the Entrust failure codes.
Level: 00001

Type: ERROR

Impact: Other

SSL-29000: Certificate not installed

Cause: Trying to delete a certificate which has not been installed.

Action: Refer to the Oracle Wallet Manager documentation for information about delete option.
Level: 00001

Type: ERROR

Impact: Other

SSL-29002: SSL transport detected invalid or obsolete server certificate.

Cause: The client detected a mismatch between the server's distinguished name specified on the server's certificate and the server's SID or service name.

Action: Refer to the SSL chapter in Oracle Advanced Security Administrator's Guide for information about enabling server distinguished name matching. Contact your administrator to perform the appropriate action.
Level: 00001

Type: ERROR

Impact: Other

SSL-29003: SSL transport detected mismatched server certificate.

Cause: The client detected a mismatch between the server's distinguished name specified on the server's certificate and the server's SID or service name.

Action: Refer to the SSL chapter in Oracle Advanced Security Administrator's Guide for information about enabling server distinguished name matching. Contact your administrator to perform the appropriate action.
Level: 00001

Type: ERROR

Impact: Other

SSL-29005: The certificate is invalid.

Cause: The peer certificate encoding is invalid when using SSL 2.0.

Action: Refer to Oracle Wallet Manager documentation to find out how to obtain the peer's certificate. Then contact Oracle customer support with the peer's certificate chain.
Level: 00001

Type: ERROR

Impact: Other

SSL-29006: The certificate request message is invalid when using SSL 2.0.

Cause: There is an error processing the SSL 2.0 REQUEST-CERTIFICATE message.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29007: Bad Clear Key Length when using SSL 2.0

Cause: The clear key length of an SSL 2.0 Client Master key handshake message is invalid.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29008: Bad DH Param key length

Cause: The length of the Diffie-Hellman params exceeds export restrictions.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29009: Bad encrypted key length when using SSL 2.0

Cause: The encrypted key length of an SSL 2.0 Client Master key handshake message is invalid.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29010: Export key length does not meet export restrictions.

Cause: The server sent a ServerKeyExchange message with an export key which does not meet export restrictions. For RSA, the export key must be exactly 512 bits.

Action: Obtain a certificate with the appropriate key length.
Level: 00001

Type: ERROR

Impact: Other

SSL-29011: Finished message is incorrect.

Cause: The FINISHED message data verification failed.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29012: Bad key argument length when using SSL 2.0

Cause: The key argument length of an SSL 2.0 Client Master Key handshake message is invalid.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29013: SSL MAC verification failure

Cause: Verification of SSL Record MAC failed.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29014: Maximum fragment length extension is incorrect.

Cause: The maximum fragment length extension specified is incorrect.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29015: incorrect message length

Cause: The message length is not correct.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29016: inadequate PKCS1 message padding

Cause: The message was not properly padded before encryption.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29017: The premaster secret length is incorrect.

Cause: The premaster secret sent by the peer has an incorrect length.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29018: The premaster secret contains an incorrect version number.

Cause: The premaster secret must contain the same version number as the ClientHello. The version sent by the client was incorrect.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29019: The protocol version is incorrect.

Cause: There is a protocol version mismatch between the two peers.

Action: Specify the correct protocol version in the product's configuration file.
Level: 00001

Type: ERROR

Impact: Other

SSL-29020: The handshake record length is too long.

Cause: The handshake record length exceeds the maximum that is allowed by the SSL specification.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29021: Secret key length is incorrect when using SSL 2.0.

Cause: The length of the decrypted ENCRYPTED-KEY is incorrect.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29022: Operation is being attempted on the wrong side of the client/server connection.

Cause: The SSL network layer has detected that the operation has been attempted on the wrong side of the client/server connection.

Action: Select the protocol side (of this protocol) to be the same as the one selected with a previous protocol.
Level: 00001

Type: ERROR

Impact: Other

SSL-29023: The buffers are not empty.

Cause: Trying to free buffers that are not empty.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29024: Certificate validation failure

Cause: The certificate sent by the other side could not be validated. This may occur if the certificate has expired, has been revoked, or is invalid for another reason.

Action: Check the certificate to determine whether it is valid. Obtain a new certificate, alert the sender that the certificate has failed, or resend.
Level: 00001

Type: ERROR

Impact: Other

SSL-29025: Error found in certificate check callback.

Cause: The application callback failed during additional certificate validation. Additional checks include CRL validation and extension checking.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29026: Decryption failure

Cause: SSL record decryption failed.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29027: Error in entropy collection

Cause: The internal entropy collection failed to generate enough seed data.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29028: Server verification failure when using SSL 2.0

Cause: Processing of an SSL 2.0 SERVER-VERIFY message failed.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29029: SSL handshake already completed

Cause: The system is trying to initiate a handshake when it has already been completed.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29030: SSL handshake is requested.

Cause: The peer sends this message if it wishes to renegotiate. The application can either proceed with the renegotiation or reject the request.

Action: This is not an error. To find out more details enable tracing and retry the connection. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29031: SSL handshake is required.

Cause: Renegotiation cannot proceed before the SSL handshake is completed.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29032: The given identity is not complete.

Cause: The certificate list does not contain both private key and certificate.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29034: Correct cipher suite or client authentication is needed.

Cause: Before installing a private key, a cipher suite or client authentication suite using the same key exchange algorithm must be installed first. This has not been done.

Action: Install a cipher suite or client authentication suite that uses the same key exchange algorithm as the private key before re-installing the private key.
Level: 00001

Type: ERROR

Impact: Other

SSL-29036: This feature is not supported

Cause: Operation is not supported by the current connection parameters.

Action: Check the Oracle documentation to determine the appropriate connection parameters required for this operation.
Level: 00001

Type: ERROR

Impact: Other

SSL-29037: No certificate is present

Cause: The other client or server sent a certificate message that contained no certificates.

Action: Check the other side (client or server) to ensure they have appropriate credentials.
Level: 00001

Type: ERROR

Impact: Other

SSL-29038: There are no matching certificates.

Cause: The other client or server sent a certificate message that contained a certificate which was not signed by a trusted certificate authority (CA).

Action: Check to ensure that the other client or server sends a certificate which is signed by a CA that is in your trusted list. Or, include the CA certificate for the other client or server's certificate as a trustpoint in your wallet.
Level: 00001

Type: ERROR

Impact: Other

SSL-29039: There are no matching cipher suites.

Cause: Neither end of the handshake can agree on a cipher suite.

Action: Check to ensure that both sides of the handshake select cipher suites that are supported.
Level: 00001

Type: ERROR

Impact: Other

SSL-29040: There are no supported cipher suites.

Cause: This end of the handshake cannot support any cipher suites. This connection and the peer have some matching cipher suites, however, these cipher suites cannot be negotiated because they cannot be supported by the connection.

Action: Check to ensure that both sides of the handshake select cipher suites that are supported by the connection. Refer to Oracle documentation for supported cipher suites.
Level: 00001

Type: ERROR

Impact: Other

SSL-29043: Read is required.

Cause: Renegotiation with the peer has not yet started. There is application data which must be processed before the handshake can proceed.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29044: Renegotiation has already been requested.

Cause: Renegotiation has already been requested.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29045: Renegotiation request has been refused.

Cause: A renegotiated handshake has been refused by the peer.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29046: Session is resumable.

Cause: Server is trying to resume a session with different session parameters.

Action: Server should resume the session with the correct session parameters.
Level: 00001

Type: ERROR

Impact: Other

SSL-29047: Mismatch in Transport Layer Security extension

Cause: Neither side can agree on a TLS extension.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29048: Unexpected message received.

Cause: An unexpected message has been received.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29049: Unknown record

Cause: The record type is unknown.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29050: Installed client authentication mode is not supported.

Cause: The enabled client authentication mode(s) cannot be used within the selected cipher suite.

Action: Enable a client authentication mode that can be used within the selected cipher suite.
Level: 00001

Type: ERROR

Impact: Other

SSL-29051: The given public key type is not supported.

Cause: The public key in the first certificate is not supported.

Action: Check to ensure that the certificate complies with the X.509v3 standard.
Level: 00001

Type: ERROR

Impact: Other

SSL-29052: Write buffer is not empty.

Cause: There is an attempt to free a write buffer that is not empty.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29084: The parameter specified is illegal.

Cause: The parameter is not correct. For example, it could be bad input, or an invalid message.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29095: Index is not correct.

Cause: The instance identified by the index parameter doesn't exist.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29096: The given length is incorrect.

Cause: The specified length is too small or is invalid.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29100: Cannot create local key ID.

Cause: Creation of local key identifier for the certificate or the private key failed.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29101: Cannot add private key bag.

Cause: The private key could not be added to the PKCS#12 object. Possible reasons are: (i) A required parameter is NULL (ii) The PKCS#12 construct is not supported (iii) An ASN.1 encoding error occurred in the certificate.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29102: Cannot add certificate bag.

Cause: Creation of certificate bag failed. The application could have run out of memory.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29103: Cannot create PKCS #12 wallet.

Cause: Creation of PKCS#12 wallet failed possibly due to memory allocation failure.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-29104: Cannot add certificate request.

Cause: Adding certificate request to the PKCS#12 wallet failed.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-29105: Cannot export PKCS #12 wallet.

Cause: A required parameter is NULL or the PKCS#12 construct is not supported.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29106: Cannot import PKCS #12 wallet.

Cause: A required parameter is NULL or the BER-encoding is malformed.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29107: Cannot create PKCS #12 wallet.

Cause: PKCS#12 wallet creation failed. The application may have run out of memory.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-29108: Cannot initialize random object.

Cause: The random object could not be initialized or seeded. Either memory allocation has failed or the pseudo random number generator module has not been installed.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29109: Cannot create private key object.

Cause: The private key object could not be created. Memory allocation may have failed.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29110: Invalid PKCS #12 bag type

Cause: The PKCS #12 bag type is invalid. Either one of the required parameters is NULL or the requested OID is not in the list.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29111: Invalid index

Cause: The index passed for getting the bag type is less than 1.

Action: Check to ensure that the index is greater than 1.
Level: 00001

Type: ERROR

Impact: Other

SSL-29112: Cannot access attributes from a PKCS #12 certificate bag.

Cause: The certificate cannot be accessed. One of the required parameters is probably NULL, or the index specified by the application does not contain a certbag, or the certificate could be malformed.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29113: Cannot access attributes from a PKCS #12 key bag.

Cause: Retrieval of the private key failed. One of the required parameters is probably NULL or the index specified by the application does not contain a key bag.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29114: Cannot import private key.

Cause: The private key could not be imported. One of the required parameters could be NULL or the encoded private key could be malformed.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-29115: Cannot export private key.

Cause: The private key could not be exported. Either the application ran out of memory or the key type is not valid.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-29116: Cannot get PKCS #12 attributes.

Cause: Retrieval of an attribute failed. One of the required parameters could be NULL.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-29117: Cannot add PKCS #12 attributes.

Cause: Could not add an attribute. The attribute parameter could be NULL.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-29118: Cannot create PKCS #12 attributes.

Cause: Creation of the attributes failed, possibly due to a memory allocation error.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-29119: Cannot import certificate.

Cause: The certificate cannot be imported. One of the required parameters could be NULL or the certificate has an invalid X.509 BER or DER encoding.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-29120: Cannot export certificate.

Cause: The certificate cannot be exported. One of the required parameters could be NULL.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-29122: could not add pkcs11 info to the pkcs12 wallet

Cause: Failed while adding pkcs11 information into a pkcs12 wallet.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-29123: could not get pkcs11 info from the pkcs12 wallet

Cause: An error was encountered while retrieving pkcs11 information from the wallet.

Action: Enable tracing to determine the exact cause of this error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-29124: pkcs11 library name already set

Cause: pkcs11 library information was already set in the wallet.

Action: Use a different wallet that does not have this information. If issue persists, enable tracing to determine the exact cause of the error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-29125: pkcs11 token label already set

Cause: pkcs11 token label information was already set in the wallet.

Action: Use a different wallet that does not have this information. If issue persists, enable tracing to determine the exact cause of the error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-29126: pkcs11 token passphrase already set

Cause: The pkcs11 token passphrase can be set only once in the wallet.

Action: Use a different wallet that does not have this information. If issue persists, enable tracing to determine the exact cause of the error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-29127: unknown pkcs11 information

Cause: An unknown pkcs11 information type was encountered. The wallet may have been corrupted due to a system error or memory corruption.

Action: Enable tracing and retry the failed operation. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29128: pkcs11 library name not set

Cause: The wallet does not have pkcs11 library information.

Action: Ensure that the wallet was created with valid library location or update the wallet with this information.
Level: 00001

Type: ERROR

Impact: Other

SSL-29129: pkcs11 token label not set

Cause: The wallet does not have pkcs11 token label information.

Action: Ensure that the wallet was created with valid token label information or update the wallet with this information.
Level: 00001

Type: ERROR

Impact: Other

SSL-29130: pkcs11 token passphrase not set

Cause: The wallet does not have pkcs11 token passphrase.

Action: Ensure that the wallet was created with valid token passphrase information or update the wallet with this information.
Level: 00001

Type: ERROR

Impact: Other

SSL-29131: pkcs11 certificate label already set in wallet

Cause: The pkcs11 certificate label was already set in the wallet.

Action: Use an empty wallet (created with orapki).
Level: 00001

Type: ERROR

Impact: Other

SSL-29135: Seed generation for Random Number Generator failed.

Cause: Generation of seed for random number generator failed.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29136: The allocated buffer is too small.

Cause: The output buffer is too small.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29137: The global context is incorrect.

Cause: The global context is incorrectly configured or invalid.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29140: Cannot create certificate object.

Cause: Creation of the certificate object failed. The application could have run out of memory.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29141: Cannot import in the der format.

Cause: Cannot import the certificate into the certificate object. The reason could be a malformed certificate.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29150: DES self-test failure

Cause: DES power up self-test has failed.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29151: 3DES self-test failure

Cause: 3DES power up self-test has failed.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29152: SHA-1 self-test failure

Cause: The SHA-1 power up self-test has failed.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29153: RSA self-test failure

Cause: The RSA power up self-test has failed.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29154: deterministic RNG self-test failure

Cause: The deterministic Random Number Generator power up self-test has failed.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29155: continuous key pair consistency check self-test failure

Cause: The public-private key pair check test failed.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29156: conditional RNG self-test failure

Cause: Continuous Random Number Generator test, which is needed in FIPS mode, has failed.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29157: Unable to build an absolute path to the library.

Cause: Not able to construct an absolute path to the location of the library.

Action: Enable tracing and attempt the connection again. Contact Oracle customer support with the trace output.
Level: 00001

Type: ERROR

Impact: Other

SSL-29158: Unable to open library.

Cause: Opening of the library failed.

Action: Check to ensure that the library is present in the location specified, and that it has the appropriate file permissions.
Level: 00001

Type: ERROR

Impact: Other

SSL-29159: Unable to read library.

Cause: Not able to read the library on which the DAC check has to be performed. Read call failed.

Action: Check if the library has the appropriate file permissions.
Level: 00001

Type: ERROR

Impact: Other

SSL-29160: NZ library being used is different.

Cause: The NZ library being used at runtime is not the same one on which the digest was computed for the software integrity check.

Action: Check to ensure that the library being used is the same as the one on which the digest was pre-computed.
Level: 00001

Type: ERROR

Impact: Other

SSL-29161: software integrity self-test failure

Cause: The software integrity check test on the NZ shared library has failed.

Action: Check to ensure that the library being used is the same as the one on which the digest was pre-computed.
Level: 00001

Type: ERROR

Impact: Other

SSL-29162: Non-FIPS cipher suites being used in FIPS mode.

Cause: The cipher suite being used does not contain FIPS-approved algorithms.

Action:
Level: 00001

Type: ERROR

Impact: Other

SSL-29163: Third party PKI vendor is not supported in FIPS mode.

Cause: Third party PKI vendors like Entrust and MCS are not supported in FIPS mode.

Action: Use only Oracle PKI when running in FIPS mode.
Level: 00001

Type: ERROR

Impact: Other

SSL-29164: External PKCS #12 wallet is not supported in FIPS mode.

Cause: PKCS #12 wallets created using third party software cannot be used in FIPS mode.

Action: Use only PKCS #12 wallets created by Oracle Wallet Manager when running in FIPS mode.
Level: 00001

Type: ERROR

Impact: Other

SSL-29176: CRL signature verification failed

Cause: A CRL is verified before being used. CRL signature cannot be verified.

Action: Get a new CRL from CA
Level: 00001

Type: ERROR

Impact: Other

SSL-29177: certificate serial number is not in CRL

Cause: Cert is not revoked

Action:
Level: 00001

Type: ERROR

Impact: Other

SSL-29178: certificate serial number is in CRL

Cause: Cert has been revoked

Action: Reject the certificate
Level: 00001

Type: ERROR

Impact: Other

SSL-29179: certificate validation check failed

Cause: Could not complete checking certificate status with a CRL.

Action: Enable tracing to find more information on this error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-29180: Unsupported validation protocol

Cause: The certificate validation protocol is not supported

Action: Make sure a supported certificate validation protocol is specified
Level: 00001

Type: ERROR

Impact: Other

SSL-29181: ldap_open failed

Cause: Could not connect to the LDAP server

Action: Ensure that correct LDAP information was provided. Enable tracing to find more information. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-29182: ldap_bind failed

Cause: Could not log in to the LDAP server

Action: Ensure that correct LDAP credentials were provided. Enable tracing to find more information. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-29183: ldap_search failed

Cause: Failed to complete search operation in LDAP server

Action: Enable tracing to find more information on this error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-29184: ldap_result failed

Cause: Failed to retrieve results from LDAP operation

Action: Enable tracing to find more information on this error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-29185: ldap_first_attribute failed

Cause: Could not get the first attribute from LDAP entry.

Action: Enable tracing to find more information on this error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-29186: ldap_get_values_len failed

Cause: Failed to retrieve attribute values from LDAP entry

Action: Enable tracing to find more information on this error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-29187: unsupported validation mechanism

Cause: The validation mechanism specified in OID is not supported

Action: Make sure a supported validation mechanism is set in OID
Level: 00001

Type: ERROR

Impact: Other

SSL-29188: ldap_count_entries failed

Cause: Failed to get count of entries from a search result chain.

Action: Enable tracing to find more information on this error. Contact Oracle customer support if needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-29189: No entry found in OID

Cause: CRL not found in OID

Action: Upload the CRL to OID
Level: 00001

Type: ERROR

Impact: Other

SSL-29190: Multiple entries in OID

Cause: For a given issuer name there should be only one CRL in OID

Action: Make sure there is only one CRL for a given issuer name in OID
Level: 00001

Type: ERROR

Impact: Other

SSL-29191: OID connection information not set

Cause: To connect to OID the connection information must be available

Action: Set the OID connection information.
Level: 00001

Type: ERROR

Impact: Other

SSL-29192: Validation mechanism not set in OID

Cause: The validation mechanism to be used is not set in OID

Action: Set validation mechanism to be used in OID at cn=ValidationMechanism, cn=Validation, cn=PKI, cn=Products, cn=OracleContext
Level: 00001

Type: ERROR

Impact: Other

SSL-29193: no CRL found using CRLDP mechanism

Cause: A CRL could not fetched using CRL Distribution point (CRLDP)

Action: Contact the CA
Level: 00001

Type: ERROR

Impact: Other

SSL-29194: no CRL found in cache

Cause: CRL not in cache

Action:
Level: 00001

Type: ERROR

Impact: Other

SSL-29195: CRL is expired

Cause: CRL nextUpdate time is in the past

Action: Get a new CRL from the CA
Level: 00001

Type: ERROR

Impact: Other

SSL-29222: Distinguished name does not match.

Cause: Distinguished name (DN) on certificate doesn't match user.

Action: Create the global user in the database with the DN that matches with the one in the user certificate on the client side.
Level: 00001

Type: ERROR

Impact: Other

SSL-29223: Cannot create certificate chain.

Cause: Unable to create a certificate chain with the existing trust points for the certificate that is to be installed.

Action: Install the trust point that signed the certificate.
Level: 00001

Type: ERROR

Impact: Other

SSL-29224: Cannot locate matching certificate request.

Cause: No matching certificate request for the certificate was found.

Action: Install the correct certificate.
Level: 00001

Type: ERROR

Impact: Other

SSL-29225: Certificate already installed.

Cause: Attempting to install a certificate into a persona which already has it.

Action: Do not install the certificate.
Level: 00001

Type: ERROR

Impact: Other

SSL-29226: No matching private key found.

Cause: Could not locate a matching private key in the persona for the given certificate (public key).

Action:
Level: 00001

Type: ERROR

Impact: Other

SSL-29227: Certificate is expired.

Cause: Certificate is no longer valid..

Action: Obtain another certificate or renew this certificate.
Level: 00001

Type: ERROR

Impact: Other

SSL-29228: Cannot calculate the number of bytes for output.

Cause: The cryptographic engine is confused about the algorithm.

Action: Check the parameters being used with the cryptographic functions.
Level: 00001

Type: ERROR

Impact: Other

SSL-29229: the magic number found in the header does not match expected

Cause: The input TDU has either been corrupted or is not being used correctly.

Action: Check that the TDU is being used from the beginning. If possible, compare the size of the TDU upon generation to the size being used.
Level: 00001

Type: ERROR

Impact: Other

SSL-29230: the header length is not sufficient for message header

Cause: The input TDU has either been corrupted or it is not being used correctly.

Action: Check that the TDU is being used from the beginning. If possible, compare the size of the TDU upon generation to the size being used.
Level: 00001

Type: ERROR

Impact: Other

SSL-29231: the cryptographic engine failed to initialize

Cause: During initialization of the cryptographic engine, some failure occurred. Possible causes include running out of memory and trying to seed the random number generator.

Action: Make sure the executable has been linked with compatible library versions, and that you are not running out of swap space.
Level: 00001

Type: ERROR

Impact: Other

SSL-29232: the cryptographic engine key initialization failed

Cause: During initialization of a key for cryptography, some failure occurred. This includes running out of memory and passing illegal arguments.

Action: Make sure the executable has been linked with compatible library versions, and that the correct parameters are being used for the cryptographic functions.
Level: 00001

Type: ERROR

Impact: Other

SSL-29233: the key object could not be encoded

Cause: The key object may be corrupted or may be an unsupported type.

Action: Check the key object being passed to the encoding routine.
Level: 00001

Type: ERROR

Impact: Other

SSL-29234: a key object was not extracted from encoding

Cause: The encoding may be corrupted or may not be a key object at all.

Action: Check the encoding and parameters passed to decoding routine.
Level: 00001

Type: ERROR

Impact: Other

SSL-29235: the key information could not be retrieved

Cause: The key may be corrupted or may be an unsupported type.

Action: Check the parameters being used with the cryptographic functions.
Level: 00001

Type: ERROR

Impact: Other

SSL-29236: the random number generator will not accept seed

Cause: The cryptographic engine may have run out of memory.

Action: Make sure the executable has been linked with compatible library versions.
Level: 00001

Type: ERROR

Impact: Other

SSL-29237: the cryptographic engine could not finish the algorithm

Cause: The cryptographic engine does not have enough information to correctly finish applying the algorithm.

Action: Check the parameters being used with the cryptographic functions.
Level: 00001

Type: ERROR

Impact: Other

SSL-29238: the cryptographic engine could not apply the algorithm

Cause: The cryptographic engine does not have enough information to correctly apply the algorithm.

Action: Check the parameters being used with the cryptographic functions.
Level: 00001

Type: ERROR

Impact: Other

SSL-29239: the cryptographic engine could not initialize the algorithm

Cause: The cryptographic engine does not have enough information to correctly initialize the algorithm.

Action: Check the parameters being used with the cryptographic functions.
Level: 00001

Type: ERROR

Impact: Other

SSL-29240: the cryptographic engine does not recognize the algorithm

Cause: The application may be passing wrong parameters.

Action: Check the parameters being used with the cryptographic functions.
Level: 00001

Type: ERROR

Impact: Other

SSL-29241: a buffer block needs more space but its length is fixed

Cause: The application has preallocated an output buffer that is too short for the operation and has specified that the buffer should not grow as needed.

Action: Either preallocate a larger buffer or allow the toolkit to grow the output buffer as needed.
Level: 00001

Type: ERROR

Impact: Other

SSL-29242: the asymmetric key is too short to be used with the data.

Cause: An asymmetric key must be at least 11 bytes longer than the data it is being used to encrypt.

Action: Use an asymmetric key with more bits or break the data into smaller pieces.
Level: 00001

Type: ERROR

Impact: Other

SSL-29243: the toolkit does not recognize the type of key being used

Cause: The application may be passing wrong parameters.

Action: Check the parameters being used with the toolkit functions.
Level: 00001

Type: ERROR

Impact: Other

SSL-29245: the toolkit does not recognize the function being used

Cause: The application is probably passing the wrong parameters.

Action: Check the parameters being used with the toolkit functions.
Level: 00001

Type: ERROR

Impact: Other

SSL-29246: the toolkit could not parse the tdu

Cause: The TDU could be corrupted.

Action: Check the parameters being used with the toolkit functions.
Level: 00001

Type: ERROR

Impact: Other

SSL-29247: an unopen toolkit object was used before it was opened

Cause: Some toolkit objects must be opened before they can be used.

Action: Check the parameters being used with the toolkit functions.
Level: 00001

Type: ERROR

Impact: Other

SSL-29248: an unrecognized WRL was used to open a wallet

Cause: WRL's have a specific set of types and must be formatted correctly.

Action: Check the parameters being used with the toolkit functions.
Level: 00001

Type: ERROR

Impact: Other

SSL-29249: an unrecognized state was passed to a cryptographic function

Cause: The application is probably passing the wrong parameters.

Action: Check the parameters being used with the toolkit functions.
Level: 00001

Type: ERROR

Impact: Other

89 SSLCFG-00131 to SSLCFG-00202

SSLCFG-00131: invalid authentication type

Cause: The value specified for authentication type was not valid.

Action: See the FMW Admin Guide for valid authentication types.
Level: 1

Type: ERROR

Impact: Configuration

SSLCFG-00148: unable to validate one or more cipher value(s) {0}

Cause: The specified cipher value(s) was invalid.

Action: See the FMW Admin Guide for valid cipher values.
Level: 1

Type: ERROR

Impact: Configuration

SSLCFG-00149: unable to validate one or more SSL version value(s) {0}

Cause: The specified SSL version value(s) was invalid.

Action: See the FMW Security Guide for valid SSL version values.
Level: 1

Type: ERROR

Impact: Configuration

SSLCFG-00150: version incompatible with the cipher(s)

Cause: The specified SSL version was incompatible with the cipher(s).

Action: Use SSL version "v1" with AES ciphers.
Level: 1

Type: ERROR

Impact: Configuration

SSLCFG-00152: ciphers are incompatible with the authentication type

Cause: The specified cipher was incompatible with the authentication type.

Action: See the FMW Admin Guide for valid cipher and authentication type combinations.
Level: 1

Type: ERROR

Impact: Configuration

SSLCFG-00173: invalid certificate validation method

Cause: The method specified for certificate validation was not valid.

Action: See the FMW Admin Guide for valid certificate validation methods.
Level: 1

Type: ERROR

Impact: Configuration

SSLCFG-00189: path to the CRL file/directory not specified

Cause: CRL file/directory path was required to be provided with the certificate validation method "crl".

Action: Specify a valid CRL file/directory path.
Level: 1

Type: ERROR

Impact: Configuration

SSLCFG-00194: invalid wallet/keystore name

Cause: An invalid value was provided for wallet/keystore name.

Action: Ensure that the wallet/keystore name is a valid file name.
Level: 1

Type: ERROR

Impact: Configuration

SSLCFG-00197: cannot change password of auto-login wallet

Cause: Password could be changed only for a password protected wallet.

Action: Provide a password protected wallet as input.
Level: 1

Type: ERROR

Impact: Configuration

SSLCFG-00199: wallet/keystore required with the authentication type {0}

Cause: Wallet/Keystore value was not specified.

Action: Provide a wallet/keystore value with this authentication type.
Level: 1

Type: ERROR

Impact: Configuration

SSLCFG-00200: v2Hello cannot be selected by itself. Select at least one more version.

Cause: The version vHello could not be selected by itself.

Action: Select either v1 or v3 along with v2Hello.
Level: 1

Type: ERROR

Impact: Configuration

SSLCFG-00201: wallet/keystore being used for SSL, deletion failed.

Cause: Could not delete wallet/keystore since it was being used for SSL.

Action: Select a wallet/keystore that is not in use.
Level: 1

Type: ERROR

Impact: Configuration

SSLCFG-00202: duplicate wallet/keystore name

Cause: A pre-existing wallet/keystore with this name was found.

Action: Provide a different name for the new wallet/keystore.
Level: 1

Type: ERROR

Impact: Configuration

90 STS-10506 to STS-15541

STS-10506: Username Token Password type {0} is not recognized

Cause: The password type has not been configured in the sts configuration file

Action: Create a mapping for the passwordtype in the usernametokenpasswordtypeuris map
Level: 1

Type: ERROR

Impact: Configuration

STS-10507: Multiple partners {2} were returned during the token mapping operation with Attribute ID={0} and Token Value={1}

Cause: Multiple partner entries have the same identification strings

Action: Update the configuration for the partners so that there is no conflict
Level: 1

Type: ERROR

Impact: Configuration

STS-12500: Xpath Exception: {0}.

Cause: An Xpath exception occurred while trying to locate desired xml element.

Action: Verify that incoming xml message was correct.
Level: 1

Type: ERROR

Impact: Other

STS-12501: JAXB Exception: {0}.

Cause: A JAXB exception occurred while trying to parse the xml element.

Action: Verify that the xml message was correct.
Level: 1

Type: ERROR

Impact: Other

STS-12507: Invalid Key Exception: {0}.

Cause: An invalid key exception has occurred.

Action: Verify that all the keys present in all the certificates are valid (correct length, format, etc).
Level: 1

Type: ERROR

Impact: Other

STS-12508: Signature Exception: {0}.

Cause: A signature exception has occurred, certificate signature could not be verified.

Action: Check logs and exception message for more information.
Level: 1

Type: ERROR

Impact: Other

STS-12510: Signing template configured in the template is missing.

Cause: An error occurred due to missing signing template.

Action: Check configuration to add the missing signing template or check the template to specify an existing signing template.
Level: 1

Type: ERROR

Impact: Other

STS-12511: Encryption template configured in the validation template is missing.

Cause: An error occurred due to missing encryption template.

Action: Check configuration to add the missing encryption template or check the validation template to specify an existing signing template.
Level: 1

Type: ERROR

Impact: Other

STS-12512: Token processing Exception: {0}

Cause: An exception has occurred during token processing.

Action: Check logs and exception message for more information.
Level: 1

Type: ERROR

Impact: Other

STS-12513: Keysource Exception: {0}.

Cause: A keysource exception has occurred during token processing

Action: Check logs and exception message for more information.
Level: 1

Type: ERROR

Impact: Other

STS-12514: No authenticator was found for authentication type: {0}.

Cause: AuthenticationType specified for UsernameToken validation is invalid in template

Action: Check the authentication type in validation template
Level: 1

Type: ERROR

Impact: Other

STS-12515: No validation template found.

Cause: Validation template was not found

Action: Check configuration to add validation template
Level: 1

Type: ERROR

Impact: Other

STS-12516: Unknown token: {0}.

Cause: Token is not known type

Action: Check the token type in the message
Level: 1

Type: ERROR

Impact: Other

STS-12517: Unknown name id format: {0}

Cause: Name ID format is not known

Action: Check the nameid format
Level: 1

Type: ERROR

Impact: Other

STS-12518: User was not mapped.

Cause: The user could not be mapped.

Action: Check the logs for more information
Level: 1

Type: ERROR

Impact: Other

STS-12519: Recipient providerID not found

Cause: The recipient provider not found

Action: Check logs for more information
Level: 1

Type: ERROR

Impact: Other

STS-12520: Certificate not found for provider: {0}

Cause: Certificate was not found for the provider

Action: Obtain the required certificates
Level: 1

Type: ERROR

Impact: Other

STS-12521: Requester providerID not found.

Cause: The requester provider was not found.

Action: Check the logs for more information
Level: 1

Type: ERROR

Impact: Other

STS-12531: Requested claims have been filtered due to policies

Cause: The Requester or Recipient Partner profiles filtered out some requested claims

Action: Check the list of attributes that can be requested by a Requester in the partner profiles of the Requester and Recipient
Level: 1

Type: ERROR

Impact: Other

STS-12532: WSS Token Error: {0}.

Cause: Token is Missing

Action: Check that the token is present in wss header
Level: 1

Type: ERROR

Impact: Other

Cause: Token Type mismatch.

Action: Check that the token matches the token type in the validation template of the endpoint

Cause: Custom token not correctly defined in configuration

Action: Check that the custom token is configured correctly in the server

STS-12533: Invalid Token Mapping Action for None Token Type: {0}

Cause: Token Mapping Action is not valid

Action: The token mapping action should be none or maprequesterbindingdata for tokentype none
Level: 1

Type: ERROR

Impact: Other

STS-15504: Validation template cannot be used to process the following type of token: {0}

Cause: The validation template is configured to process a token type different from the one presented

Action: Check that the validation template is configured for the correct protocol type
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15505: Token is missing during validation processing with validation template {0}

Cause: The security token is missing in the incoming request

Action: Check that the request is providing the expected security token for the validation template
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15506: Missing data for SAML Authentication Statement

Cause: The authentication method or context is missing

Action: Check that the token was validated correctly and that an authentication mechanism was set by the validation module
Level: 1

Type: ERROR

Impact: Requests/Responses

Cause: The authentication instant is missing

Action: Check that the token was validated correctly and that an authentication mechanism was set by the validation module

STS-15507: Digest Password Type not supported for Username Token Validation

Cause: The Username Token contains a Password of type Digest

Action: Contact the client to request the password to be of type Text in the Username Token
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15508: Authorization Failure for Relying Party {0}, Requester {1} and User {2}

Cause: The authorization policy evaluation failed for the specified parameters

Action: Check the configuration and/or policy for any errors
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15509: Assertion ID is missing

Cause: The SAML Assertion in the Validation Request has AssertionID missing

Action: Check the logs and Exception for more information
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15510: Invalid SAML version in the token

Cause: THE SAML Version specified in the token is not valid

Action: Check the logs and Exception for more information
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15511: Issuer information is missing

Cause: Issuer information in the token to be validated is missing

Action: Check the logs and Exception for more information
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15512: Invalid issue instant

Cause: Token Issue instant is not valid

Action: Check the logs and Exception for more information
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15513: NOT_BEFORE Condition failed for the token

Cause: NOT_BEFORE condition for the token validity failed

Action: Check the logs and Exception for more information
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15514: NOT_ONAFTER Condition for the token failed

Cause: NOT_ONAFTER condition for the token validity failed

Action: Check the logs and Exception for more information
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15515: Authentication Time is invalid

Cause: Authentication time for the token is not valid

Action: Check the logs and Exception for more information
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15516: Subject is invalid

Cause: Subject for the token is not Valid

Action: Check the logs and Exception for more information
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15517: Authentication Method is not specified

Cause: Authentication Method is not specified in the token

Action: Check the logs and Exception for more information
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15518: Authentication Instant is missing

Cause: Authentication Instant is missing in the token

Action: Check the logs and Exception for more information
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15519: Authentication Context is missing

Cause: Authentication Context is not specified in the token

Action: Check the logs and Exception for more information
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15520: Subject Confirmation NOT_ONBEFORE condition failed

Cause: The assertion not before condition was not satisfied

Action: Check the logs and Exception for more information
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15521: Subject Confirmation NOT_ONAFTER condition failed

Cause: The subject confirmation not on or after condition was not satisfied

Action: Check the logs and Exception for more information
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15522: Authentication Statement NOT_ON_AFTER condition failed

Cause: The authentication statement not on or after condition was not satisfied

Action: Check the logs and Exception for more information
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15523: Creation Date could not be parsed

Cause: The created date format could not be parsed

Action: Check the logs and Exception for more information
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15524: Creation Time is not valid

Cause: The created time was before the valid period

Action: Check the logs and Exception for more information
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15525: Nonce was already used

Cause: The nonce in the message was previously used

Action: Check the logs and Exception for more information
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15526: No Username in the token

Cause: There is no user name in the token

Action: Check the logs and Exception for more information
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15527: Invalid Nonce Encoding

Cause: The nonce encoding type is invalid

Action: Check the logs and Exception for more information
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15528: Nonce could not be decoded

Cause: Nonce could not be decoded

Action: Check the logs and Exception for more information
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15530: Token could not be prased

Cause: The token could not be parsed

Action: Check the logs and Exception for more information
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15531: Token Type {0} is invalid

Cause: Token Type is not valid

Action: Check that the token type in the SOAP request is valid
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15532: Signature in the token could not be verified

Cause: Signature in the token could not be verified

Action: Check the logs and Exception for more information
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15533: Nonce Encoding is neither null nor default

Cause: Nonce Encoding is neither null nor default

Action: Check the logs and Exception for more information
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15534: Message could not be decrypted

Cause: The message could not be decrypted

Action: Check the logs and Exception for more information
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15535: SAML 1.1 Assertion does not contain any statements

Cause: No Attribute Statement and no Authentication Statement are included in the Assertion

Action: Check that the Oracle Secure Token Service is configured to include one of the statements
Level: 1

Type: ERROR

Impact: Requests/Responses

Cause: No Attribute Statement and no Authentication Statement are included in the Assertion, even if Oracle Secure Token Service is configured to include an Attribute Statement

Action: Check that at least one attribute can be used to populate the Attribute Statement

STS-15538: WSS token validation failed for ValidationTemplateID: {0} and Message {1}

Cause: Invalid WSS token

Action: Provide valid WSS token.
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15541: WSTrust token validation failed for ValidationTemplateID: {0} and Message {1}

Cause: Invalid WSTrust token

Action: Provide valid WSTrust token.
Level: 1

Type: ERROR

Impact: Requests/Responses

91 TCM-00006 to TCM-99009

TCM-00006: The NameId for the request is not valid.

Cause: The NameId for a service request did not contain a Name or an Identifier.

Action: Provide either a Name or an Identifier for a service request.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-00007: The Id for the request is not valid.

Cause: The document identifier for the request was not valid. The value supplied was null or an empty string.

Action: Provide a valid document identifier for a document service request.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-00008: The SectionFlags for the request are not valid.

Cause: The wrong section flags were provided for the request.

Action: Consult the API documentation for the proper section flags for the request.
Level: 1

Type: ERROR

Impact: Programmatic

TCM-00009: No session has been established.

Cause: A session was expected to exist but was not found. This may occur if operations were called after logging out.

Action: Log in and properly establish a session before attempting an operation.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-00010: The version of the JRE used by the repository is too low to support Imaging. The required minimum is {0}. The repository is using {1}.

Cause: An attempt was made to establish a connection to a Content Server repository using the wrong JRE.

Action: Upgrade the Content Server JRE to the minimum required version. The required version will be stated in the error message.
Level: 1

Type: ERROR

Impact: Configuration

TCM-00012: Unable to log in to the UOA repository

Cause: IPM could not log in to the UOA system.

Action: Check to make sure the UOA system is up and running properly.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-00013: Basic Authentication requires SSL.

Cause: An attempt was made to log in to IPM without using SSL, which is required.

Action: Configure the IPM Server for SSL and use https in the web services URL.
Level: 1

Type: NOTIFICATION

Impact: Configuration

TCM-00015: Unable to find file {0}

Cause: A file used for input could not be found.

Action: Check the file path given in the error message and verify that it exists.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-00016: Unable to open file {0}

Cause: A file used for input could not be opened.

Action: Check the file path given in the error message and verify that it is readable.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-00020: Unable to authenticate user.

Cause: Invalid credentials were supplied during login.

Action: Provide valid credentials.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-00021: This session is already established.

Cause: An attempt was made to log in to a session that was already established.

Action: Either use the existing session without logging in again, or log out to establish a new session.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-00022: Service was called without credentials. The calling user cannot be authenticated.

Cause: No credentials were provided for the service request.

Action: Ensure the proper security credentials are applied to the login services.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-00026: The requested definition is not found.

Cause: The user does not have access to the definition.

Action: Check the user's access to the requested definition.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-00027: User does not have permission to access this page.

Cause: An attempt was made to access a definition page that the user does not have permission to access.

Action: Check the user's permissions to the requested definition.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-00028: The definition arrays supplied are empty.

Cause: The definitions supplied for an import or export operation were empty arrays.

Action: Make sure that the definitions arrays are filled in with valid definition NameIds.
Level: 1

Type: ERROR

Impact: Programmatic

TCM-00029: The {0} section is read-only and cannot be modified.

Cause: At least one definition section specified for modify was read only and cannot be changed.

Action: Remove the read-only section from the modify section set argument.
Level: 1

Type: ERROR

Impact: Programmatic

TCM-00040: Encountered exception initializing regions.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-00041: Cache is Ready = {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-00042: Cache Distributed = {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-00043: Imaging region exists.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

TCM-00044: Cache failed during initialization and may be disabled.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

TCM-00045: The cache age limit must be set to a positive number

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

TCM-00102: Workflow Agent login failure.

Cause: The Workflow Agent failed to log in.

Action: Review the server logs for further information.
Level: 1

Type: WARNING

Impact: Requests/Responses

TCM-00103: Workflow Agent logout failure.

Cause: The Workflow Agent failed to log out.

Action: Review the server logs for further information.
Level: 1

Type: WARNING

Impact: Requests/Responses

TCM-00104: Workflow Agent error processing a message.

Cause: An error occurred trying to process a worklfow agent message.

Action: Review the server logs for further information.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-00105: Document {0} returning to workflow agent queue for retry.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-00106: Workflow agent processing fault recorded for document {0}.

Cause: An error was encountered processing a document. The document was identified in the error message. The error could be due to the workflow server being down.

Action: Review the server logs for further information. The workflow agent will attempt to reprocess the document.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-00107: Workflow agent cannot record fault for document {0}. Returning to workflow agent queue for retry.

Cause: An error was encountered processing a document, and the workflow agent was unable to record the error as a fault. The document was identified in the error message.

Action: Review the server logs for further information. The workflow agent will attempt to reprocess the document.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-00110: Constructed Input Agent Bean.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-00111: Destroyed Input Agent Bean.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-00112: Input Agent encountered an error during shutdown.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

TCM-00113: An error occurred trying to read the Input Agent configuration.

Cause: An error occurred trying to read the Input Agent Bean configuration.

Action: Review the server logs for further information.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-00114: An error occurred initializing the Input Agent Bean.

Cause: An error occurred initializing the Input Agent Bean.

Action: Review the server logs for further information.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-00115: Beginning Input Agent initialization.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-00116: Input Agent initialization is complete.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-00118: Input Agent timer service is not initialized. Cannot continue.

Cause: Input Agent timer service is not initialized.

Action: Check the Application Server installation and restart the service.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-00119: Input Agent configuration is empty. Cannot continue.

Cause: Input Agent configuration is empty.

Action: Check the JDBC connection and reboot the server.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-00120: Input Agent time interval is not set. Cannot continue.

Cause: Input Agent time interval is not set.

Action: Update the Check Interval setting to a valid value in the IPM config MBean.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-00121: An error occurred resetting an input job.

Cause: An error occurred resetting an input job.

Action: Review the server logs for further information.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-00122: An error occurred checking for work.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

TCM-00126: Beginning Input Agent servlet initialization.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-00127: Input Agent servlet initialization is complete.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-00128: The JMS Queue browser cannot be closed properly.

Cause: There was a problem closing the JMS Queue browser.

Action: Review the server logs for more information.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-00129: Input Agent is checking for work.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-00130: Beginning Input Agent Cleanup timer initialization.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-00131: Input Agent Cleanup timer initialization is complete.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-00150: Constructed Input Filing MDB.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-00151: Destroyed Input Filing MDB.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-00152: Error while unregistering Input Filing MDB.

Cause: An error occurred while unregistering Input Filing MDB.

Action: Review the server logs for further information.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-00153: Beginning filing for Input {0} and data source {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-00154: Filing {0} completed successfully with {1} documents processed successfully out of {2} documents.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-00155: Filing {0} failed with {1} documents that failed to index.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-00156: Error indexing document number {0}.

Cause: An error occurred while indexing a document.

Action: Review the server logs for further information.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-00157: An error occurred filing file {0}.

Cause: An error occurred while filing a job.

Action: Review the server logs for further information.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-00158: Failed to cancel job.

Cause: Failed to cancel a job.

Action: Review the server logs for further information.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-00159: Cannot determine what Input Source to use for job and cannot abort or cancel job.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

TCM-00160: Input Filing MDB failed to log out.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

TCM-00161: Failed to resume filing for data source {0} and batch {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

TCM-00162: Failed to load Batch for new filing.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

TCM-00163: An error occurred while completing a batch.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

TCM-00164: Input Agent cannot find WLS Runtime MBean server.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

TCM-00165: The Input {0} is currently marked offline, so the request to process data source {1} is being rolled back

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-00166: Resubmitting job for input source {0} due to error: {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-00170: Constructed Ticket Agent MDB.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-00171: Destroyed Ticket Agent MDB.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-00172: Beginning Ticket Agent servlet initialization.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-00173: Ticket Agent servlet initialization is complete.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-00174: An error occurred while restarting the Ticket Agent MDB.

Cause: An error occurred while restarting the Ticket Agent MDB.

Action: Review the server logs for further information.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-00175: Ticket Agent timer service is not initialized. Cannot continue.

Cause: Ticket Agent timer service is not initialized.

Action: Check the Application Server configuration and restart the service
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-00176: An error occurred while initializing Ticket Agent MDB.

Cause: An error occurred while initializing Ticket Agent MDB.

Action: Review the server logs for further information.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-00177: Beginning Ticket Agent initialization.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-00178: Ticket Agent initialization is complete.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-00179: Encountered an error while attempting to clean up expired tickets from the IPM system

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

TCM-00196: Encountered an error while logging out of IPM system

Cause:

Action:
Level: 1

Type: WARNING

Impact: Requests/Responses

TCM-00199: IPM API error encountered, attempting restart.

Cause: An IPM API error was encountered.

Action: Review the server logs for further information.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-00777: A database error occurred.

Cause: An operation caused an unexpected database error.

Action: Review the logs for the specifics of the database error. You may need to contact Oracle Support Services to resolve the issue.
Level: 1

Type: ERROR

Impact: Data

TCM-00787: A repository error occurred.

Cause: An unknown error has occurred with a repository.

Action: Review the logs to determine the cause of the error. You may need to contact Oracle Support Services to resolve the issue.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-00788: The following error is reported by the repository: {0}

Cause: An error has occurred with a repository. The details of the error were part of the error message.

Action: Review the message and logs to determine the cause of the error. You may need to contact Oracle Support Services to resolve the issue.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-00789: The Content Server returned no data. This may be an indication of an incorrect server port number, or a connection failure during a request.

Cause: The Content Server was shut down in the middle of a request

Action: Check to make sure the Content Server is still up and running.
Level: 1

Type: ERROR

Impact: Configuration

TCM-00790: UOA shared libraries are not properly deployed and targeted to this IPM server.

Cause: The UOA shared libraries have not been properly deployed and targeted to this IPM server. This occurs most often when UOA is not installed at the same time as IPM from configuration wizard.

Action: Ensure that the UOA shared libraries are deployed and targeted to the IPM Managed Server instances.
Level: 1

Type: ERROR

Impact: Configuration

TCM-00791: The Content Server does not have a defined document profile field.

Cause: The Content Server repository did not have a defined profile trigger.

Action: Configure a profile trigger in the Content Server. This can be accomplished by setting EnableIdcProfileField=1 and then restarting the Content Server.
Level: 1

Type: ERROR

Impact: Configuration

TCM-00888: Validation Error.

Cause: Data supplied to an imaging operation was invalid.

Action: Correct the invalid data and resend.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-00998: Multiple errors in a subsystem. {0}

Cause: An error occurred in UOA that has multiple causes.

Action: Review the logs for the errors. You may need to contact Oracle Support Services to resolve the issue.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-00999: Error in a subsystem. {0}

Cause: An error occurred in a repository, or when communicating with a workflow server.

Action: Review the logs for the error. You may need to contact Oracle Support Services to resolve the issue.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-01008: Unable to add application. The application category already exists.

Cause: A UOA category of the same name already exists.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-01009: Unable to add application. The system document category does not exist.

Cause: A UOA system document category has not been properly configured.

Action: Ensure that the UOA repository has been initialized prior to creating applications.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-01010: Unable to add application. The application documents folder already exists

Cause: A UOA folder used for storage of application documents already exists.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-01017: Unable to update application. User does not have proper permissions.

Cause: The current user has not been given the proper rights to update the application.

Action: Refrain from modifying the application until the proper rights have been granted.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-01018: Unable to delete application. The application contains documents.

Cause: A user attempted to delete an application that still contains documents.

Action: Delete all of the documents belonging to the application before attempting to delete the application.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-01019: Another application operation is in progress. Try again later.

Cause: A user attempted an application operation while another operation was in progress.

Action: Wait 30 to 60 seconds and try again.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-01020: This document operation is blocked by repository database inconsistencies. This may be due to concurrent application activity (for example, adding, modifying, or deleting an application). Try again later.

Cause: A user attempted a document operation while the repository metadata table is in an inconsistent state. This could be due to a concurrent application operation.

Action: Wait 30 to 60 seconds and try again.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-01021: Failed to delete application in the repository. Contact an administrator for assistance.

Cause: The system was not able to delete the application in the repository.

Action: Review the logs for possible reasons.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-01025: The NameId for the application does not contain a name or an identifier.

Cause: The NameId for the application did not contain a name or an identifier.

Action: Provide either a name or an identifier for the application.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-01027: Lifecycle policy action specification, {0}, is not found.

Cause: The specified lifecycle policy action specification was not found in the UOA system.

Action: Ensure that UOA is configured with the specified lifecycle policy action specification.
Level: 1

Type: ERROR

Impact: Configuration

TCM-01028: Lifecycle policy date rule specification, {0}, is not found.

Cause: The specified lifecycle policy date rule specification was not found in the UOA system.

Action: Ensure that UOA is configured with the specified lifecycle policy date rule specification.
Level: 1

Type: ERROR

Impact: Configuration

TCM-01031: Missing a closing delimiter near "{0}".

Cause: An opening delimiter ([) was found without a closing delimiter (]) in a Format Value function.

Action: Review the Format Value text and ensure that there are matching delimiters.
Level: 1

Type: ERROR

Impact: Programmatic

TCM-01032: The workflow mapping function, {0}, is not a known function.

Cause: A workflow Format Value contains a reference to an unknown function.

Action: Review the API documentation for valid workflow function names.
Level: 1

Type: ERROR

Impact: Programmatic

TCM-01033: The workflow mapping function, {0}, is not allowed.

Cause: A workflow function was specified in a location where it is not allowed.

Action: Review the API documentation for valid workflow function usage.
Level: 1

Type: ERROR

Impact: Programmatic

TCM-01034: The workflow mapping function, {0}, has too many parameters.

Cause: Too many parameters were provided for a workflow function.

Action: Review the API documentation for valid workflow function usage.
Level: 1

Type: ERROR

Impact: Programmatic

TCM-01035: The workflow mapping function, {0}, requires a parameter.

Cause: A workflow function was missing a required parameter.

Action: Review the API documentation for valid workflow function usage.
Level: 1

Type: ERROR

Impact: Programmatic

TCM-01036: The workflow mapping function, {0}, does not accept a parameter.

Cause: A parameter was provided to a workflow function that does not accept parameters.

Action: Review the API documentation for valid workflow function usage.
Level: 1

Type: ERROR

Impact: Programmatic

TCM-01037: Null applications are not allowed.

Cause: A null value was provided to a function that requires an application definition.

Action: Provide a valid, non-null, application definition.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-01039: The document is not allowed to be updated. It is read-only.

Cause: The current user was not given the proper rights to update documents belonging to the application.

Action: Refrain from modifying the application's documents until the proper rights have been granted.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-02001: The requested document, id={0}, was not found.

Cause: Document does not exist, or user does not have proper rights.

Action: Verify document and user rights before attempting to access the document.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-02003: The requested id, {0}, is not a document.

Cause: Item returned by UOA is not a document.

Action: Retry action against document.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-02004: The document is currently locked by {0}

Cause: Document is already locked.

Action: Unlock document and try again.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-02005: The document cannot be locked

Cause: Document could not be locked to the user.

Action: Verify user permissions and try again.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-02006: The document is locked to another user: {0}

Cause: Document is locked to another user.

Action: Administrator or current document owner must unlock document.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-02007: The document cannot be unlocked

Cause: Document could not be unlocked by the user.

Action: Verify the document state and try to unlock document again.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-02008: The documents cannot be deleted because they are in a legislative hold in the repository.

Cause: An attempt was made to delete documents that are in legislative hold.

Action: Refrain from deleting documents until legislative holds have been removed.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-02009: Primary application category not found.

Cause: Primary application category not found in UOA.

Action: Verify that the UOA system has been initialized correctly for IPM.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-02011: The document is not locked to the requester

Cause: Document is not locked to the user.

Action: Document must be unlocked before trying again.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-02012: An invalid file was received "{0}".

Cause: Invalid file was given to the API.

Action: Verify the file and try again.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-02014: Original document field values cannot be retrieved.

Cause: Document fields could not be retrieved from UOA.

Action: Verify user permissions and try again.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-02015: Invalid field value for field "{0}".

Cause: Could not resolve field for field value.

Action: Verify application definition and try again.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-02016: The file name is invalid. A file name must have a file extension, cannot be empty or null, and cannot include any path information.

Cause: An invalid file name was provided for the document.

Action: Enter a valid file name. Do not include any path information.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-02019: Replacement or versioning is not allowed for this document.

Cause: Document cannot be updated.

Action: Document update is not allowed for documents in this application.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-02020: Page Management functions are valid only with TIFF document types.

Cause: Cannot modify because it is not a tiff document.

Action: Page management functions are only valid for tiff documents.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-02021: A page management operation cannot complete because of a system error.

Cause: Page operation failed. System error occurred accessing image.

Action: Verify and try again.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-02022: The supporting content key is invalid.

Cause: Supporting content key for the document is invalid.

Action: Enter unique supporting content key.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-02023: Cannot find the field {0}, id {1} in the application context.

Cause: Document missing field information. Cannot create document.

Action: Enter correct field information.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-02024: Invalid upload token.

Cause: Token for the uploaded file is invalid.

Action: Use valid token.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-02025: Cannot move document. Source and destination application are the same.

Cause: Source and destination applications are the same.

Action: Specify different application when moving documents.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-02026: The document data provided to the service is invalid

Cause: Invalid data stream was given to the API

Action: Check the file and make sure it is valid
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-02027: The requested supporting content for the document, id={0}, key={1}, was not found.

Cause: Supporting content key does not return any results.

Action: Verify supporting content key is correct.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-02028: This document consists of multiple versions. The destination application does not support versioning.

Cause: Document consists of multiple versions. Destination application does not support versioning.

Action: Choose a destination application that supports versioning.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-02029: Write permissions are required on the document in order to set supporting content.

Cause: Write permissions are required on the document in order to set supporting content.

Action: Verify user permissions are set correctly for the document
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-02030: View permissions are required on the document in order to get supporting content.

Cause: View permissions are required on the document in order to get supporting content.

Action: Verify user permissions are set correctly for the document
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-02031: Copy failed, document not found.

Cause: Document does not exist or user does not have rights to copy.

Action: Verify document and user rights before attempting to copy.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-02032: Moved failed, no document move rights

Cause: Document does not exist or user does not have rights to move.

Action: Verify document and user rights before attempting to move.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-02033: Update failed, no document update rights

Cause: Document does not exist or user does not have rights to update

Action: Verify document and user rights before attempting to update.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-02034: The document version must be greater than 0.

Cause: Document version must be greater than 0

Action: Set version to a value greater than 0
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-02035: File, "{0}," is zero length. Documents must have a file length greater than zero.

Cause: File with zero length was given to the API.

Action: Check the file and make sure its length is greater than zero.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-02036: Either a valid file, a valid field list, or both, are required to update a document.

Cause: Invalid file and field list has been passed into update document.

Action: Verify valid file and field list have been passed in.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-02037: The supporting content key already exists.

Cause: Supporting content key for the document already exists.

Action: Enter unique supporting content key.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-02038: The document identifier, {0}, is invalid.

Cause: The document identifier for the request was invalid.

Action: Enter a valid document identifier.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-02039: The document action could not be performed because the document is under records management in the repository.

Cause: A user attempted a document operation while the document is under records management in the repository.

Action: Refrain from operating or a records managed document.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-02040: The file timeout {0} is invalid for document operations. The timeout must be greater than or equal to 0.

Cause: The timeout for document operations must be greater than or equal to 0. The current value is invalid

Action: Set timeout value to greater than or equal to 0.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-03004: Annotation list is Null

Cause: Annotation list to search is Null.

Action: Ensure that annotation list object is not null.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-03012: An error occurred while saving annotations

Cause: An error occurred while saving annotations.

Action: A repository-specific exception occurred when saving annotations. Check the repository-specific exception stack for diagnostic details.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-03018: Error reading file {0}

Cause: An error occurred while reading the file

Action: Check the file and its permissions
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-03024: An annotation cannot be accepted due to the lack of permission.

Cause: An annotation cannot be accepted due to the lack of permission.

Action: Ensure that all annotations' security settings are compatible with the user's permission set.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-03029: Invalid document Id saving/retrieving document annotations: {0}

Cause: Invalid document Id when saving/retrieving document annotations.

Action: Supply a valid document Id.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-03035: User does not have sufficient annotation permission in the destination application.

Cause: User does not have sufficient annotation permission in the destination application.

Action: Ensure that the user has sufficient annotation permissions in the destination application for any annotations to be applied.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-03036: An error occurred retrieving annotations for the document.

Cause: Annotations for the specified document could not be retrieved.

Action: A repository-specific exception occurred when saving annotations. Check the repository-specific exception stack for diagnostic details.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-03037: Error saving annotations to a document version that is not the current version.

Cause: An attempt was made to save annotations to a document version that is not the current version.

Action: Annotations cannot be saved to previous versions of a document.
Level: 1

Type: WARNING

Impact: Requests/Responses

TCM-04001: A valid Input name or ID must be specified for the operation to complete.

Cause: The requested Name and ID of the input to be deleted is invalid.

Action: Provide a valid Name or ID for the Input to delete
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04002: No Input definitions found for the input name {0}, ID {1}.

Cause: The specified Input could not be found in the system.

Action: Recheck the Input name or ID.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04003: Multiple Input definitions found for input name {0}, ID {1}.

Cause: The name or ID provided has multiple Input Definitions associated with it.

Action: Examine the system for data integrity.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04004: Input name is empty

Cause: The name of the Input is invalid

Action: Make sure the Input name is not missing, blank or only strings
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04005: Invalid Input properties

Cause: The properties section of the Input Definition was invalid.

Action: Make sure that the Input properties section is not missing.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04006: Input source must be set

Cause: The Input Definition is missing the input source

Action: Provide a valid input source
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04008: The Input's Source Properties section is invalid

Cause: The Input Source Properties section of the Input definition is invalid.

Action: Check to make sure the properties are set and have valid values.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04009: The specified data source is invalid.

Cause: The Data Source in the Input Source Properties was invalid.

Action: Make sure that the data source is specified and has a valid value.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04010: The Input Source in the definition is invalid

Cause: The Input Source is invalid.

Action: Check the Input Source and make sure it's valid.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04012: The Input does not define any mappings, or one or more mappings are invalid

Cause: The Input Mappings section of the Input definition is invalid.

Action: Check to make sure mappings have been set and map between valid fields.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04013: The provided StateUpdates are invalid.

Cause: No valid values were provided for updating the input's state.

Action: Ensure that the Input.StateFlags provided for all updates are valid.
Level: 1

Type: WARNING

Impact: Requests/Responses

TCM-04014: The specified input's state cannot be updated

Cause: Updating the current state for the specified input failed.

Action: Ensure that the specified input exists, and that the new state settings are valid.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04015: The specified input definition cannot be updated

Cause: Updating the provided sections of the input definition failed.

Action: Ensure values have been properly provided for all of the definition sections you are attempting to update
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04016: The provided Input object is null

Cause: The Input object provided is null.

Action: Provide a valid Input, with appropriate sections completed.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04017: Cannot find the configuration file for the local Input Server settings.

Cause: The configuration file specified could not be found.

Action: Ensure that the specified file exists, and that the user has the correct permissions
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04018: An error was encountered loading the configuration file

Cause: The configuration file couldn't be opened.

Action: Ensure that the specified file exists, and that the user has the correct permissions
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04019: Failed to get the Input Source list

Cause: Could not get a listing of available Input Sources

Action: Check the jar configuration files and make sure they are defined correctly
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04020: The Input Path for CSV filings has not been configured properly.

Cause: The Input Path is missing from the CSV configuration file.

Action: Check the CSV configuration file to make sure it exists and is correct.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04021: Input Source {0} cannot be found

Cause: The requested Input Source was not found

Action: Check the /META-INF/input-agent-config.properties file of Input Source jar and make sure it's correct.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04022: Error loading Input Source Plugin

Cause: An error occurred while trying to load the input source

Action: Check the class path to make sure the input source can be loaded.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04023: The stage path cannot be initialized for processing

Cause: The stage directory could not be initialized.

Action: Check the permissions to the Input Directory.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04024: The file {0} cannot be moved to the directory {1}

Cause: The input file could not be properly staged for processing.

Action: Check the input file and stage path for proper permissions.
Level: 1

Type: WARNING

Impact: Requests/Responses

TCM-04025: the configuration folder path cannot be found

Cause: The configuration file wasn't found

Action: Make sure all the configuration files are in place and are correct.
Level: 1

Type: WARNING

Impact: Requests/Responses

TCM-04026: The specified Input Source "{0}" cannot be found

Cause: The given Input Source name does not match any sources that the Input Server has loaded.

Action: Check the Input Source name.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04027: One or more of the Input Fields are mapped to multiple Application or system fields

Cause: One of the input mappings is assigned to multiple locations.

Action: Remove all duplicate mappings from the definition
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04028: The requested input field isn't mapped to an application field

Cause: The requested mapping wasn't found in the index

Action: Pass in the correct input field name
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04029: The parser has not been initialized, call StartFiling

Cause: Start Filing wasn't called on the parser

Action: Call start filing
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04030: The input file cannot be properly closed

Cause: A file error closing the input file

Action: Check file permissions and input file
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-04032: The specified data range is invalid

Cause: Start and end positions for examining the data source are invalid

Action: Request a valid range
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-04033: Date value does not conform to the short, medium or long format type for the current locale, date cannot be parsed.

Cause: Date format does not parse to a valid date

Action: Pass in a date value that conforms to the locales short, medium or long format
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04034: Cannot get the local machine name

Cause: The host could not be determined.

Action: Check the error code.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04035: The application({0},{1}) specified in the mapping cannot be found. Verify that the application exists and you have permissions to it.

Cause: The application that the mapping is pointing to could not be found

Action: Check to make sure that you have access to that Application or that the Application is still valid.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04036: The mapping for input section {0} is invalid

Cause: The application field specified in the Input mapping is invalid.

Action: Check to make sure that the specified application field ID is set and exists in the target application
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04038: Application "{0}" cannot be loaded. Verify that the application exists and you have permissions to it.

Cause: The Application specified could not be loaded

Action: Check to make sure that the Application exists and you have access to it.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04039: The Sample Path for CSV filings has not been configured correctly.

Cause: The sample path is not configured correctly

Action: Make sure the sample path configuration value is set to a valid location
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04040: The sample path {0} cannot be initialized for processing

Cause: The sample path could not be created

Action: Make sure the sample path is valid, accessible by the server and has the correct permissions
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04041: The get contents request for data source {0} cannot be processed because it is not a sample source.

Cause: User attempted to get sample data for a data source that wasn't a sample source.

Action: Use only sample sources when requesting source contents.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04045: The Input {0} has {1} unfinished batches open against it and cannot be deleted

Cause: There is an open batch against the Input

Action: Wait for the filing to finish before deleting the Input
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04046: Input {0} has active or pending jobs and cannot be deleted

Cause: There are queued jobs for the Input

Action: Wait for all the work to finish before deleting the Input
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04047: The Input Agent service cannot be accessed to process commands.

Cause: The Input Agent could not be found to communicate with.

Action: Validate that the Imaging.ear is started and running properly.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04048: Content cannot be read from the data source {0}

Cause: The data source content could not be read

Action: Examine the inner exception for more information
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04049: The StateUpdate value passed to the ModifyState call is invalid

Cause: The state update object passed to the API request is invalid

Action: Check the StateUpdate object to make sure it's properly formed
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04050: No Application is specified in the Input Mapping section

Cause: The input definition does not have the destination application id set

Action: Set the Application Id in the Input mapping section
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04051: The input file locale has already been set and cannot be changed

Cause: A locale has already been specified for the input file and cannot be changed

Action: Remove the extra locale command from the input file
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04052: The locale identifier {0} is not a valid locale identifier

Cause: The locale parameter specified in the locale command is invalid

Action: Specify a valid locale
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04053: The locale command can only be used at the beginning of the input file

Cause: The locale command was used after the start of the file

Action: Only use the locale command at the top of the input file
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04054: The start position {0} or range {1} specified are invalid. Make sure that the start position and range values are positive and that the range is greater than the start.

Cause: The start position or range values are invalid.

Action: Examine the calling code and ensure that the start position and range are greater than 0 and that the range is greater than the start position
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-04055: The value {0} provided for the Input Server state update is the wrong type or is out of range.

Cause: The value provided to the StateFlag request was invalid.

Action: Check to make sure the correct type has been passed for the StateFlag and that the value is in the correct range.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-05003: The UOA Repository search failed

Cause: No Search was found matching the selected search id

Action: Re-list the available searches
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-05004: The Search Definition supplied was null

Cause: A null value was provided for the search.

Action: Provide a non-null search.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-05005: The Search Name supplied was null or empty

Cause: Search name was null or empty

Action: Provide a valid search name.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-05006: The search supplied has a results formatting structure that is null.

Cause: The search formatting structure was null or empty.

Action: Provide a valid search formatting structure.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-05007: The requested search, {0}, was not found.

Cause: The user does not have access to the search.

Action: Check the user's access to the requested search.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-05009: A required search parameter, {0}, was missing.

Cause: A required parameter was missing for this search

Action: Resubmit the search with the required parameter(s).
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-05012: Invalid operator used in search parameter

Cause: An invalid operator was used in the search parameter

Action: Use an operator defined in the operator picklist.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-05013: A Search Argument was provided that was not defined in the search

Cause: A search argument was provided that was not defined in the search

Action: Provide only those arguments defined in the search.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-05014: The search argument contains a value for a read-only parameter

Cause: A search argument was provided containing a value for a read-only parameter

Action: Remove the read only parameter from the search arguments.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-05015: There are multiple search arguments for a single parameter.

Cause: Multiple search arguments were provided for a single parameter.

Action: Verify that the number of the search arguments matches the number of parameters.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-05016: The type for the search argument does not match the search parameter type.

Cause: A search argument with an incorrect type was provided for a search parameter.

Action: Use an argument with a type that matches the search parameter type.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-05017: The entered value, {0}, is < 1. The default maximum rows returned value must be >= 1.

Cause: A value less than 1 was entered for the defalut value for the maximum number of rows to be returned from a search.

Action: Use a value that is greater than or equal to 1.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-06001: Unable to retrieve Role: {0}

Cause: The role specified was not found.

Action: Add the role to the security provider or use a defined role.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-06002: Access is denied.

Cause: User does not have access to the requested information.

Action: Update the user's permissions.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-06004: Unable to locate the security member specified.

Cause: The security member does not exist.

Action: Add the security member to the security provider.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-06009: Unable to locate the system group: {0}

Cause: The specific system group was not found.

Action: Add the system group using the security provider.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-06010: Agent users are only allowed to log in through the agent services.

Cause: An agent user was used to attempt a log in.

Action: Log in using a different user.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-06011: Users assigned the 'admin' group either directly or indirectly are not allowed to log into IPM.

Cause: Users assigned the 'admin' group are not allowed to log in because the repository attaches special meaning to this group.

Action: Log in using a different user or remove the 'admin' group association with this user.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-06012: The User {0} does not exist in the policy store.

Cause: The security provider was unable to locate the user specified.

Action: Enter the user into the security provider.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-06013: Unable to locate the default policy store.

Cause: Unable to load the policy store.

Action: The default policy store has not been configured correctly.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-06014: The user's principal does not contain a subject.

Cause: The principal object was not found in the user token.

Action: Make sure the principal exists within the user token.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-06015: The Group {0} does not exist in the policy store.

Cause: The authentication provider was unable to locate the group specified.

Action: Enter the group into the authentication provider.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-06016: Access to modify the security of this definition is denied.

Cause: The user was unable to modify the security of this definition.

Action: Update the user permissions with the modify permission.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-06017: Access to modify the document security of this definition is denied.

Cause: The user was unable to modify the document security of this definition.

Action: Update the user permissions to include the modify document security permission.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-06018: Unable to create resource in policy store for: {0}

Cause: Unable to create resource in policy store for: {0}

Action: The default policy store has not been configured correctly.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-06019: Bad principal type returned by Policy Store for "{0}": {1}

Cause: Bad principal type returned by Policy Store for "{0}": {1}

Action: The default policy store has not been configured correctly.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-06020: No Security Profile was found during system startup.

Cause: No Security Profile was found during system startup.

Action: The system has not been configured correctly to use a security profile.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-06021: The Security Profile failed to initialize during system startup: {0}

Cause: The Security Profile failed to initialize during system startup: {0}

Action: The system has not been configured correctly to use the security profile.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-07001: Requested output format does not support multiple pages

Cause: An output format was requested that does not support multiple pages.

Action: Choose a different output format, or restrict the output request to a single page.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-07002: Invalid Document reference in render request

Cause: The supplied documentObject parameter is null

Action: Provide a valid Document object reference when calling RenderManager.render().
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-07003: Invalid input stream in render request

Cause: The supplied sourceStream parameter is null

Action: Provide a valid InputStream object reference when calling RenderManager.render().
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-07004: No render options in render request

Cause: The supplied options parameter is null

Action: Provide a valid RenderOptions object reference when calling RenderManager.render().
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-07008: This document contains annotations that prevent the user from accessing this document in its raw format

Cause: This document contains annotations that prevent the user from accessing this document in its raw format.

Action: Export to TIFF with the annotations burned in or contact your administrator for access to the native format.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-07009: The mime-type of "{0}" is not supported.

Cause: An unsupported mime-type was requested.

Action: Correct the document content (mime) type.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-07011: An I/O error occurred during image translation.

Cause: An I/O error occurred during image translation.

Action: Check permissions and free space in the server temp directory.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-07012: An error occurred when loading an image for translation.

Cause: An error occurred when loading an image for translation.

Action: Image handling components failed to load the image. Check nested exception details for diagnostic information.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-07013: There was an error reading TIFF headers. The file may be corrupt.

Cause: There was an error reading TIFF headers. The file may be corrupt.

Action: Check permissions and free space in the server temp directory.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-07014: An error occurred when processing image manipulation commands during save.

Cause: An error occurred when processing image manipulation commands during save.

Action: Image handling components failed to load the image. Check nested exception details for diagnostic information.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-07016: An I/O error occurred creating the output for this request.

Cause: An I/O error occurred creating the output for this request.

Action: Check for nested exceptions, permissions and free space in the server temp directory.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-07017: No document specified when burning annotations into image

Cause: No document specified when burning annotations into image.

Action: Specify a valid document path to the document source.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-07019: The requested scale is not within the allowed value range; {0}-{1}

Cause: The requested scale is not within the allowed value range.

Action: Provide a scale factor value within the supported range.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-07020: The requested fit rectangle is empty

Cause: The requested fit rectangle cannot be empty.

Action: Provide a non-null, non-empty rectangle.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-07021: Unable to get annotation permissions from document

Cause: Annotation permissions could not be determined.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-07022: The supplied document object is null

Cause: The cache was given a null document object.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-07023: A cache exception occurred. {0}

Cause: A RenderPageCache exception occurred: {0}

Action: Check the cache exception code and nested exception details for diagnostic information.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-07024: A RenderPageCache object was not found

Cause: An error occurred retrieving an object from the cache.

Action: Check the directory and nested exception details for diagnostic information.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-07025: Page number must be a positive value.

Cause: Page number must be a positive value.

Action: Provide page number values greater than zero.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-07026: Bounding rectangle specified is empty.

Cause: Bounding rectangle specified is empty.

Action: Provide a non-empty rectangle definition.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-07027: The supplied outputType parameter is null.

Cause: The supplied outputType parameter is null.

Action: Provide a value for the outputType parameter.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-07028: An invalid argument was provided to method {0}({1}).

Cause: An invalid argument was provided to a method call.

Action: Provide non-null values. Page specifications must be > 0.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-07029: Cannot burn the annotations into the destination file {0}.

Cause: An error occurred while burning annotations into the destination tiff.

Action: Check the embedded exception for the specific cause of the error.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-07030: An invalid path was specified. Provide a non-null, non-empty string or an existing directory path.

Cause: An invalid path was set for the render CacheLocation.

Action: Provide an empty value or an existing directory path.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-07031: An invalid value was specified. Check spelling and character case.

Cause: An invalid value was specified.

Action: Check spelling and character case.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-07033: An invalid value was specified. Enter a value from 0 to 100.

Cause: An invalid value was specified.

Action: Enter a value from 0 to 100.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-07036: An error occurred during document translation.

Cause: An error occurred during document translation.

Action: Check nested exception details for diagnostic information.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-07037: An error occurred retrieving a rendition to create a copy with.

Cause: An error occurred retrieving a rendition to create a copy with.

Action: The rendering system was unable to generate a rendition of the document. Check the nested exception details for diagnostic information.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-07038: The requested page number is beyond the document page range.

Cause: The requested page number is beyond the document page range.

Action: Specify a valid page number that is within the range of document pages.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-07039: This document content is sealed. IRM content cannot be rendered.

Cause: This document content is sealed. IRM content cannot be rendered.

Action: Download the native document and use Oracle IRM Desktop to access this file content.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-07040: RenderAgent is not initialized. Requests cannot be processed.

Cause: RenderAgent is not initialized. Requests cannot be processed.

Action: RenderAgentBean initialization failed. Check the nested exception details for diagnostic information.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-07041: The specified viewer cache days value of {0} is invalid. The number of days must be greater than or equal to 0 and less than or equal to 30.

Cause: The cache days value that was given is invalid.

Action: Check the cache days parameter sent to the MBean is in the valid range of 0-30.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-08001: System folder "{0}" is not found

Cause: A UOA system folder was not found.

Action: Ensure proper UOA system installation.
Level: 1

Type: ERROR

Impact: Installation

TCM-08005: User does not have create permissions.

Cause: An attempt was made to create documents in an application where the user does not have create permission.

Action: Ensure user is granted create permission or refrains from creating documents.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-08006: User does not have delete permissions.

Cause: An attempt was made to delete documents in an application where the user does not have delete permission.

Action: Ensure user is granted delete permission or refrains from deleting documents.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-08008: User does not have permission to access the "{0}" system folder.

Cause: An attempt was made to access a system folder, but the user does not have the proper permission.

Action: Ensure user is granted the proper permission or refrains from accessing the folder
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-08009: Workspace "{0}" is not found.

Cause: A workspace in UOA was not found.

Action: Ensure proper UOA system installation.
Level: 1

Type: ERROR

Impact: Installation

TCM-08010: Interrupted during login retry. Stopping further login attempts.

Cause: An agent thread was interrupted while attempting to log in.

Action: Check to see if the thread was shut down.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-08011: Unable to log in to the IPM system

Cause: An error was encountered while logging in to the IPM system.

Action: Check the IPM logs and any inner exception for details on why the login failed.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-09010: An error occurred trying to list storage policy volumes.

Cause: An error occurred trying to obtain a list of storage volumes from a repository.

Action: Ensure that the repository is running and functioning correctly.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-09011: An error occurred trying to determine the default storage policy volume.

Cause: An error occurred trying to determine the default volume for a repository.

Action: Ensure that the repository is running and functioning correctly.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-09012: An error occurred trying to list retention policies.

Cause: An error occurred trying to list retention policies for a repository.

Action: Ensure that the repository is running and functioning correctly.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-09013: An error occurred trying to validate a volume.

Cause: An error occurred trying to validate a volume for a repository.

Action: Ensure that the repository is running and functioning correctly.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-09014: An error occurred trying to validate a storage group.

Cause: An error occurred trying to validate a storage group for a repository.

Action: Ensure that the repository is running and functioning correctly.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-09015: An error occurred trying to validate a retention policy.

Cause: An error occurred trying to validate a retention policy for a repository.

Action: Ensure that the repository is running and functioning correctly.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-09016: An error occurred trying to find a retention policy.

Cause: An error occurred trying to find a retention policy in a repository.

Action: Ensure that the repository is running and functioning correctly.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-09017: An error occurred trying to discover lifecycle policies.

Cause: An error occurred trying to find lifecycle policies in a UOA repository.

Action: Ensure that UOA is running and functioning correctly.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-09018: An error occurred trying to create a storage policy.

Cause: An error occurred trying to create a storage policy in a UOA repository.

Action: Ensure that UOA is running and functioning correctly.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-09019: An error occurred trying to delete a storage policy.

Cause: An error occurred trying to delete a storage policy in a UOA repository.

Action: Ensure that UOA is running and functioning correctly.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-09020: An error occurred trying to load action specifications.

Cause: An error occurred trying to load action specifications in a UOA repository.

Action: Ensure that UOA is running and functioning correctly.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-09021: An error occurred trying to load date rule specifications.

Cause: An error occurred trying to load date rule specifications in a UOA repository.

Action: Ensure that UOA is running and functioning correctly.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-09030: Error connecting to workflow system.

Cause: An error occurred trying to connect to a workflow server.

Action: Ensure that the workflow server is running and functioning correctly.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-09032: Error determining workflow composite services. The composite DN is {0}.

Cause: An error occurred trying to determine services for a composite.

Action: Ensure that the workflow server is running and functioning correctly.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-09033: Error getting workflow system components.

Cause: An error occurred trying to determine components for a workflow server.

Action: Ensure that the workflow server is running and functioning correctly.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-09034: Error reading workflow service WSDL document {0}

Cause: An error occurred trying to read the workflow service WSDL document.

Action: Ensure that the workflow server is running and functioning correctly. If WSDL protocol is HTTPS, ensure SSL configurations for both IPM and the workflow server are correct.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-09035: Error accessing credential key ''{0}''

Cause: An error occurred access a credential key in the credential store.

Action: Ensure that the correct key was provided and the credentials are properly configured in the credential store.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-09036: Unsupported workflow service. Service definition exceeds hierarchical depth of {0}.

Cause: Workflow service Definition exceeded the maximum hierarchical depth given in the error message.

Action: Select a different workflow service operation.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-09037: Unsupported workflow service. Service definition contains choice elements.

Cause: Workflow service definition contains unsupported choice elements.

Action: Select a different workflow service operation.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-10001: An error was encountered while searching the repository for closed batches

Cause: An error occurred while searching the CDB repository for closed batches

Action: Check the associated exception and CDB log files for errors
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-10002: Batch ID {0} for Application {1} has been closed and cannot be indexed into, operation aborted

Cause: The user requested to index a document into a batch that has been closed

Action: Check the calling code to determine why the batch was committed too early
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-10003: Batch ID {0} for Application {1} has already been committed

Cause: The user attempted to commit a batch that was already closed

Action: Check the calling code to determine why the batch was committed twice
Level: 1

Type: WARNING

Impact: Requests/Responses

TCM-10004: No Batches found for the Batch Name {0}, ID {1}.

Cause: The Batch could not be found in the CDB system

Action: Check the NameId passed to the API and make sure it exists
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-10005: The target application specified in the Batch object is invalid

Cause: The target application specified in the Batch object is invalid

Action: Check the Batch object and ensure that the target application is valid
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-10006: No Batches found for Batch ID {0}

Cause: The Batch could not be found in the CDB system

Action: Check the NameId passed to the API and make sure it exists
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-10007: The Batch provided is null

Cause: The specified Batch is null

Action: Pass a valid Batch object to the API call
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-10008: The requested Batch ID {0} has documents indexed into it and cannot be removed.

Cause: The requested batch could not be deleted because it had documents indexed to it.

Action: Double check that the correct batch was requested and verify that it is empty.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-11001: Turning on or off the auditing configuration failed

Cause: An FDK Exception was generated by the UOA system when attempting to set the auditing configuration.

Action: Correct the underlying UOA repository configuration.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-11002: The search of the audit history failed.

Cause: The search of the repository for auditing data resulted in a repository exception.

Action: Correct the error identified in the underlying repository exception.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-14000: The provided URL ticket is invalid.

Cause: The provided URL ticket was determined to be invalid.

Action: Pass a valid ticket to the API call.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-14001: The URL ticket is set to expire but does not have an expiration time set.

Cause: The URL ticket was set to expire, but did not have an expiration time set.

Action: Turn off the expiration or set the expiration time for the ticket.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-14002: No parameters exist in the provided URL ticket.

Cause: No parameters were specified in the URL ticket.

Action: Add at least 1 parameter to the URL ticket.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-14003: The parameter for value {0} in the URL ticket is missing a name.

Cause: The ticket parameter did not have a name defined.

Action: Assign a name to the ticket parameter.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-14004: The parameter {0} does not have a value assigned to it.

Cause: Ticket parameter did not have a value defined.

Action: Assign a value to the parameter.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-14005: The provided ticket identifier is invalid.

Cause: The ticket identifier was invalid.

Action: Specify a valid ticket identifier.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-14006: A ticket with the identifier {0} cannot be found.

Cause: The provided ticket identifier could not be found in the system.

Action: Verify that the ticket identifier is correct.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-14007: The ticket agent is not processing requests.

Cause: The ticket agent service could not be located.

Action: Verify that the IPM ear deployment is valid and is running.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-14008: A create ticket request that is set to expire has an invalid expiration date.

Cause: An attempt was made to create a ticket with an expiration date in the past.

Action: Fix the create request so that the ticket has a date in the future.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-14009: The ticket parameter name {0} is longer than the maximum allowed name length of 200.

Cause: An attempt was made to create a ticket parameter with a name that is too long.

Action: Shorten the parameter name to be less than 200 characters.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-14010: The ticket parameter value {0} is longer than the maximum allowed value length of 200.

Cause: An attempt was made to create a ticket parameter with a value that is too long.

Action: Shorten the parameter value to be less than 200 characters.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-15000: The provided Connection object is null

Cause: No Connection was provided

Action: Call the method with a valid Connection object
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-15001: Failed to remove the connection as it has the following application dependencies: {0}.

Cause: Connection is still in use

Action: Remove the dependent applications prior to removing the connection
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-16001: The import data supplied is null.

Cause: Data supplied for the import operation was null.

Action: Verify the import data is valid and not null.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-16002: Import/Export requires administrator privileges in order to run.

Cause: The user supplied does not have the proper permissions.

Action: Verify the user is an administrator.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-70007: The specified Input Source {0} cannot be found.

Cause: An Input Source name was provided that does not match any sources that the Input Server has loaded.

Action: Check the Input Source name.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-70008: The server interval setting is missing from the configuration file.

Cause: The server interval configuration is missing from the configuration file.

Action: Check the configuration file.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-70009: The Input Definition is invalid.

Cause: The Input parameter was null.

Action: Supply a valid Input to the call.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-70010: No data was provided for the mapped document file section.

Cause: A document file was not provided.

Action: Add a patch to the desired document image file to the input file.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-70013: Cannot find the field {0}, id {1} in the Application, check the Application and Input for proper mappings.

Cause: The application field for a section mapping couldn't be found

Action: Check to make sure the application field hasn't been deleted and examine the Input field mappings
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-70015: The Batch {0} given to Input Agent is marked closed and cannot be used to add objects to.

Cause: The Batch that Input Agent was assigned to file to is marked as closed

Action: Restart the entire input file as a new filing.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-70016: A check interval setting of {0} is invalid. Specify a value between 1 and 60.

Cause: An invalid check interval was provided.

Action: Set the interval between 1 and 60.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-70017: An error occurred while manipulating the Input Filing Queue

Cause: An error occurred while trying to browse the input queue

Action: Check the embedded error for more details
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-70018: The value {0} is too large or small to fit in a numeric field.

Cause: The value that was parsed was outside the valid range for a numeric type.

Action: Fix the value so that it is inside the numeric data type range.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-70020: The retry count setting {0} is invalid, enter a value between 1 and 100

Cause: An invalid retry count was set into the MBean

Action: Try using a retry value between 1 and 100
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-70021: The input value {0} could not be converted to a date. It does not conform to a short, medium or long date format for the current locale.

Cause: An invalid date string was parsed from the input file

Action: Correct the value so that it is in the correct date format
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-70022: The input value {0} could not be converted to a number.

Cause: An invalid decimal string was parsed from the input file

Action: Correct the value so that it is a valid number
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-70023: The input value {0} could not be converted to a decimal.

Cause: An invalid date string was parsed from the input file

Action: Correct the value so that it is a valid decimal
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-70024: An existing set of state information was found for the job {0} for Input {1} and cannot be duplicated. Input Agent is ignoring this request.

Cause: Existing filing State information was found for the data source and Input and cannot be added twice.

Action: Clear out all filings for the Input and allow the server to remove the extra state information.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-70025: There is no valid document id to run the command on.

Cause: The command could not be executed because the last document failed to index and no document id was specified.

Action: Either fix the indexing error for the last document in the file or specify a document id to apply the command to.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-70026: The supporting content key value was not found in the command.

Cause: No key value was specified for the supporting content command.

Action: Add a supporting content key to the supporting content command.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-70027: The supporting content file path was not found in the command.

Cause: The supporting content file name was not found.

Action: Add the supporting content's full path to the command.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-70028: The annotation file path was not found in the command.

Cause: The annotation file name was not found.

Action: Add the annotation file's full path to the command.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-70029: The file cleanup expire days {0} is invalid. The number of days must be greater than or equal to 0 and less than or equal to 30.

Cause: An invalid file cleanup expire day count was provided.

Action: Provide an integer value in the range from 0 to 30 days.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-71002: The input source cannot set up the stage path correctly.

Cause: The plugin encountered an error trying to set up the stage path.

Action: Check to make sure the plugin can get to the machine name.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-71003: Encountered error {0} while writing to the error file {1}

Cause: An error occurred while writing to the error file.

Action: Check the disk, path, and user permissions.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

TCM-71004: The failed path {0} cannot be initialized for processing.

Cause: The failed directory could not be initialized.

Action: Check the permissions to the Input Directory and subdirectories.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-71005: The file mask {0} is invalid because it contains path information in addition to the file mask. Remove the additional path information.

Cause: The file mask has at least a partial path in it, which is not supported.

Action: Remove the path portion of the file mask
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-71006: Cannot lock the input file {0} for processing.

Cause: The input file could not be locked for processing.

Action: Make sure another program isn't accessing the file.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-71007: Cannot save file {0} since a file with the same name already exists there

Cause: The user tried to upload a sample file with a name that already exists in the directory

Action: Specify a unique name before uploading to the sample directory
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-71008: Cannot save the given file to the sample directory. Error message provided is: {0}.

Cause: The sample file could not be saved to the sample directory.

Action: Check the embedded exception for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-71009: The state file {0} cannot be created.

Cause: The state file could not be created.

Action: Check the stage directory to make sure that it has enough space and the correct permissions.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-71010: The state file {0} cannot be updated.

Cause: The state file could not be updated.

Action: Check the stage directory to make sure that it has enough space and the correct permissions.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-71011: No instances of the delimiter {0} were found in the current line of the input file

Cause: The delimiter is missing for the input file line

Action: Check the delimiter in the Input Definition and make sure it's the correct one for the input file
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-71012: The file {0} is 0 bytes in length and cannot be processed.

Cause: An attempt was made to process an input file that has 0 bytes.

Action: Process a file with data in it.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-71013: The file state information cannot be loaded for data source {0}

Cause: Error loading the filing state for the input file

Action: Examine the database and any inner exceptions to determine the cause of the load error
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-71014: The filing state information cannot be found for data source {0}.

Cause: The filing state could not be found for the input file

Action: Check the database to make sure that the filing state entry still exists
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-90001: Conversation ID not found: {0}

Cause: Conversation identifier was not found in current session.

Action: Start over, if the problem persists, contact your system administrator.
Level: 1

Type: WARNING

Impact: Session

TCM-90002: Task Context is unavailable.

Cause: Workflow Task Context was not available.

Action: Start over. If the problem persists, contact your system administrator.
Level: 1

Type: WARNING

Impact: Session

TCM-90003: Invalid Task ID: {0}

Cause: Task ID provided was not available in request or in cache.

Action: Start over, if the problem persists, contact your system administrator.
Level: 1

Type: WARNING

Impact: Session

TCM-90004: Task {0} already acquired by {1}

Cause: The chosen workflow task has already been acquired by another user.

Action: Select another task and try again.
Level: 1

Type: WARNING

Impact: Session

TCM-90005: Username cannot be changed.

Cause: Username cannot be changed without changing sessions.

Action: Logout and log in with the desired user.
Level: 1

Type: WARNING

Impact: Session

TCM-90006: Username cannot be null.

Cause: Username passthrough is set to TRUE. Username is required with this setting.

Action: Provide a valid username and try again.
Level: 1

Type: WARNING

Impact: Session

TCM-91000: An unexpected system error occurred. Contact your system administrator for support.

Cause: An error has occurred.

Action: Contact Oracle Support Services for help determining the cause.
Level: 1

Type: ERROR

Impact: Programmatic

TCM-91001: SolutionParameter not found for: SolutionNamespace={0}, CommandNamespace={1}, ConfigurationNamespace={2}, ParameterKey={3}

Cause: SolutionParameter was not found in "AXF_SOLUTION_PARAMETERS" table for the provided SolutionNamespace, CommandNamespace, ConfigurationNamespace, ParameterKey.

Action: Verify that the "AXF_SOLUTION_PARAMETERS" table contains this value.
Level: 1

Type: ERROR

Impact: Configuration

TCM-91002: SystemParameter not found for: Namespace={0}, ParameterType={1}, ParameterKey={2}

Cause: SystemParameter was not found in "AXF_SYSTEM_PARAMETERS" table for the provided SolutionNamespace, ParameterType, ParameterKey.

Action: Verify that the "AXF_SYSTEM_PARAMETERS" table contains this value.
Level: 1

Type: ERROR

Impact: Configuration

TCM-91003: There was an error with the supplied XPath: {0}

Cause: There was an error with the provided XPath

Action: Verify XPATH configuration in "AXF_XPATH_ATTRIBUTE" table
Level: 1

Type: ERROR

Impact: Configuration

TCM-91004: SolutionNamespace cannont be modified in an existing Conversation

Cause: SolutionNamespace cannot be modified in an existing Conversation identifier.

Action: Start a new Conversation identifier for the new SolutionNamespace.
Level: 1

Type: ERROR

Impact: Programmatic

TCM-91005: SolutionNamespace not configured: {0}

Cause: Provided SolutionNamespace was not configured in the "AXF_SOLUTIONS" table.

Action: Ensure the SolutionNamespace entered has a matching entry in the "AXF_SOLUTIONS" table.
Level: 1

Type: ERROR

Impact: Configuration

TCM-91006: System cache failure

Cause: The system cache failed.

Action: Contact Oracle Support Services with all log information, and restart your server.
Level: 1

Type: ERROR

Impact: Process

TCM-91007: Unable to load command {0} using configured command class {1}

Cause: Failed to create the instance of command provided in the "AXF_COMMANDS" table

Action: Check configuration entry in "AXF_COMMANDS" table and verify that the matching class has been loaded in the application server
Level: 1

Type: ERROR

Impact: Configuration

TCM-91008: Unable to find command "{0}" in the database.

Cause: Unable to find the provided command in "AXF_COMMANDS" table

Action: Check the command entry in "AXF_COMMANDS" table
Level: 1

Type: ERROR

Impact: Configuration

TCM-91009: Unable to create named connection: {0}

Cause: Failed to find the workflow connection information from the Imaging system

Action: Check configuration entry in "AXF_SOLUTION_ATTRIBUTE" table and the corrresponding entry in "CONNECTION_DETAILS" table.
Level: 1

Type: ERROR

Impact: Configuration

TCM-91010: Unable to create named connection without a provider specified

Cause: Failed to create named connection without a provider specified

Action: Check configuration entry in "AXF_SOLUTION_ATTRIBUTE" table and the corrresponding entry in "CONNECTION_DETAILS" table.
Level: 1

Type: ERROR

Impact: Configuration

TCM-91014: Solution Parameter Key {0} has an invalid value of {1} for Solution Namespace = {2} -- Command Namespace = {3} -- Configuration Namespace = {4}

Cause: The Solution Parameter Key has an invalid value in "AXF_SOLUTION_PARAMETERS" for the provided SolutionNamespace, ParameterType, ParameterKey.

Action: Verify the configuration parameter in "AXF_SYSTEM_PARAMETERS" table for the Redirect Command.
Level: 1

Type: ERROR

Impact: Configuration

TCM-91015: Error executing pl/sql procedure: {0} using connection: {1} for conversation: {2}

Cause: Failed to execute pl/sql procedure in UpdateTaskFromProcedureCommand.

Action: Verify the configuration parameter in "AXF_SYSTEM_PARAMETERS" table for UpdateTaskFromProcedureCommand.
Level: 1

Type: ERROR

Impact: Configuration

TCM-91016: Unable to retrieve database connection using JNDI name: {0}

Cause: Failed to retrieve the JNDI name from Application Server.

Action: Verify the configuration parameter in "AXF_SYSTEM_PARAMETERS" table and ensure that JNDI is setup correctly in application server.
Level: 1

Type: ERROR

Impact: Configuration

TCM-91017: Unable to retrieve the web root context from the application server.

Cause: Failed to retrieve the web root context from the application server.

Action: Contact Oracle Support Services for help determining cause.
Level: 1

Type: ERROR

Impact: Configuration

TCM-91018: SolutionNamespace attribute not found for: Namespace={0}, ParameterKey={1}

Cause: SolutionNamespace attribute was not found in the "AXF_SOLUTION_ATTRIBUTES" table for the BPEL_CONNECTION key.

Action: Check the "AXF_SOLUTION_ATTRIBUTES" Table for the missing configuration.
Level: 1

Type: ERROR

Impact: Configuration

TCM-91019: Command Parameter Key {0} has an invalid value of {1} for Solution Namespace = {2}, Command Namespace = {3}

Cause: Command Parameter Key is missing, invalid or empty for Solution Namespace.

Action: Check the request parameters for command.
Level: 1

Type: ERROR

Impact: Configuration

TCM-91020: Unable to decode the value in URL {0}

Cause: This encoding is not supported.

Action: Check the encoding URL value.
Level: 1

Type: ERROR

Impact: Configuration

TCM-91021: UCM unable to process the request - {0}

Cause: UCM is unable to process the request.

Action: Check the UCM configuration.
Level: 1

Type: ERROR

Impact: Configuration

TCM-91201: Unable to create sorts for workflow

Cause: Got the workflow exception while creating ordering

Action: Check permission for workflow user and workflow log
Level: 1

Type: ERROR

Impact: Configuration

TCM-91202: Unable to create predicates for workflow

Cause: Got the workflow exception while creating predicate

Action: Check permission for workflow user and workflow log
Level: 1

Type: ERROR

Impact: Configuration

TCM-91203: Payload column is not supported for filtering

Cause: Payload column is not supported for filtering

Action: Remove payload from column filtering
Level: 1

Type: ERROR

Impact: Configuration

TCM-91204: Attributes list is null or empty

Cause: Attributes list was null or empty

Action: Supply at least one attribute
Level: 1

Type: ERROR

Impact: Configuration

TCM-91205: Unable to find the value specified by xpath : {0}

Cause: Xpath found no matching element in the workload payload.

Action: Verify the xpath value in "AXF_XPATH_ATTRIBUTES" table and that the workflow payload has a corresponding entry.
Level: 1

Type: ERROR

Impact: Configuration

TCM-91206: Workflow admin userid is missing

Cause: Failed to get the workflow admin userid.

Action: Check the workflow admin userid in CSF of application server for the matching alias key in "CONNECTION_DETAILS" table.
Level: 1

Type: ERROR

Impact: Configuration

TCM-91207: Workflow admin password is missing

Cause: Failed to get the workflow admin password.

Action: Check the workflow admin password in CSF of application server for the matching alias key in "CONNECTION_DETAILS" table.
Level: 1

Type: ERROR

Impact: Configuration

TCM-91208: Workflow provider url is missing

Cause: Failed to get the workflow provider url.

Action: Check the host and port in "CONNECTION_DETAILS" database table
Level: 1

Type: ERROR

Impact: Configuration

TCM-91209: Unable to authenticate from workflow

Cause: Failed to authenticate with workflow server.

Action: Check the workflow password in CSF of application server for the matching alias key in "CONNECTION_DETAILS" table.
Level: 1

Type: ERROR

Impact: Configuration

TCM-91210: Unable to locate the security member specified

Cause: Failed to locate the security policy store.

Action: Check the application server security configuration for authentication.
Level: 1

Type: ERROR

Impact: Configuration

TCM-91211: Unable to locate the security store identity

Cause: Failed to locate the security store identity.

Action: Check the application server security configuration for authentication.
Level: 1

Type: ERROR

Impact: Configuration

TCM-91212: User {0} does not exist in the policy store.

Cause: User did not exist in the policy store.

Action: Validate the user in the policy store.
Level: 1

Type: ERROR

Impact: Configuration

TCM-91213: Unable to find the users in the policy store.

Cause: Failed to find the users in the policy store.

Action: Verify that users exist in the policy store.
Level: 1

Type: ERROR

Impact: Configuration

TCM-91214: Unable to find the roles in the policy store.

Cause: Failed to find the roles in the policy store

Action: Check the application server security configuration for authentication
Level: 1

Type: ERROR

Impact: Configuration

TCM-91215: Unable to find the policies in the policy store

Cause: Unable to find the policies in the policy store

Action: Check the application server security configuration for authentication
Level: 1

Type: ERROR

Impact: Configuration

TCM-91216: Unable to get the payload value for {0}

Cause: Failed to find an element in workflow payload using xpath

Action: Verify the xpath value in "AXF_XPATH_ATTRIBUTES" table and the workflow payload has it
Level: 1

Type: ERROR

Impact: Configuration

TCM-91217: Unable to load XML file '{0}' into XML Document

Cause: Failed to load XML file into XML Document to create the views.

Action: Check the XML file permissions, format, and location on disk.
Level: 1

Type: ERROR

Impact: Configuration

TCM-91218: View name is blank. It must be set to create a view. XML = {0}

Cause: View name was blank in the provided XML file.

Action: Ensure that the view name is not empty in the XML file and node tag is /workflowSet/FFMSet/FFMDefinition/[<view name>]/FFMDetail/name.
Level: 1

Type: ERROR

Impact: Configuration

TCM-91219: User name is blank. It must be set to create a view. XML = {0}

Cause: User name was blank, it must be set to create a view.

Action: Ensure that the user name is not blank in the XML file and node tag is /workflowSet/viewSet/viewDefinition/[<view name>]//userList/user[<user>].
Level: 1

Type: ERROR

Impact: Configuration

TCM-91220: User name or realm is blank. It must be set to create a view. XML = {0}

Cause: User name or realm was blank.

Action: Ensure that the user name or realm is blank in the XML file.
Level: 1

Type: ERROR

Impact: Configuration

TCM-91221: View Filter Column name is blank. It must be set to create a view. XML = {0}

Cause: View filter Column name was blank.

Action: Ensure that the View Filter Column name is not blank in the XML file and node tag is /workflowSet/viewSet/viewDefinition/[<view name>]//userViewDetail/viewPredicate/clause[<position>]/column.
Level: 1

Type: ERROR

Impact: Configuration

TCM-91222: Filter Operation is blank. It must be set to create a view. XML = {0}

Cause: Filter operation was blank.

Action: Ensure that the Filter Operation is not blank in the XML file and node tag is /workflowSet/viewSet/viewDefinition/[<view name>]//userViewDetail/viewPredicate/clause[<position>]/operator.
Level: 1

Type: ERROR

Impact: Configuration

TCM-91223: Filter Value is blank. XML = {0}

Cause: Filter value was blank.

Action: Ensure that the Filter Value is not blank in the XML file and node tag is /workflowSet/viewSet/viewDefinition/[<view name>]//userViewDetail/viewPredicate/clause[<position>]/value.
Level: 1

Type: ERROR

Impact: Configuration

TCM-91224: View Ordering column name is blank. XML = {0}

Cause: View ordering column name was blank.

Action: Ensure that the View ordering column name is not blank in the XML file and node tag is /workflowSet/viewSet/viewDefinition/[<view name>]/userViewDetail/viewOrdering/clause[<position>]/column.
Level: 1

Type: ERROR

Impact: Configuration

TCM-91225: View Ordering sort order is blank. XML = {0}

Cause: View ordering sort order was blank.

Action: Ensure that the View ordering sort order is not blank in the XML file and node tag is /workflowSet/viewSet/viewDefinition/[<view name>]/userViewDetail/viewOrdering/clause[<position>]/sortOrder
Level: 1

Type: ERROR

Impact: Configuration

TCM-91226: View Creation failed. XML = {0}

Cause: Failed to create the workflow View

Action: Check user permissions to create the view and also check the workflow server log
Level: 1

Type: ERROR

Impact: Configuration

TCM-91227: View Column name was blank. XML = {0}

Cause: View column name was blank, it must be set to create a view

Action: View Column name is blank in the XML fileand node tag is /workflowSet/viewSet/viewDefinition/[<view name>]/userViewDetail/viewColumns/column[<position>]
Level: 1

Type: ERROR

Impact: Configuration

TCM-91228: Unable to get the next task

Cause: Failed to retrieve the next task from workflow.

Action: There may be no tasks for this user in workflow. Check the workflow server log.
Level: 1

Type: ERROR

Impact: Configuration

TCM-91229: Unable to get list of tasks

Cause: Failed to get list of tasks

Action: Workflow server may be not running or password is not correct in CSF. Check the workflow server log
Level: 1

Type: ERROR

Impact: Configuration

TCM-91230: Unable to get list of views

Cause: Failed to get list of views

Action: Workflow server may be not running or password is not correct in CSF. Check the workflow server log
Level: 1

Type: ERROR

Impact: Configuration

TCM-91231: Unable to acquire task id {0} for user {1}

Cause: Failed to acquire task id from workflow.

Action: The task may be already acquired by another user. Check the workflow server log.
Level: 1

Type: ERROR

Impact: Configuration

TCM-91232: got the stale object from workflow

Cause: The task from workflow is out of date.

Action: Log out from the application and try again.
Level: 1

Type: ERROR

Impact: Configuration

TCM-91233: Unable to release task id {0} for user {1}

Cause: Failed to release task id from workflow.

Action: Verify that the task can be acquired by the current user. Check the workflow server log.
Level: 1

Type: ERROR

Impact: Configuration

TCM-91234: Unable to get the task detail for {0}

Cause: Failed to get the task detail from workflow.

Action: Verify that the task is not already completed or purged in workflow.
Level: 1

Type: ERROR

Impact: Configuration

TCM-91235: Task ID is null

Cause: Task Id was invalid or null.

Action: Logout from application and try again.
Level: 1

Type: ERROR

Impact: Configuration

TCM-91236: Unable to update the task for {0}

Cause: Failed to update the task in workflow.

Action: Verify that the task may be acquired to update the payload. Check the workflow server log.
Level: 1

Type: ERROR

Impact: Configuration

TCM-91237: Unable to update outcome for {0}

Cause: Failed to update the outcome in workflow.

Action: Verify that the task may be acquired to update and that the outcome is valid. Check the workflow server log.
Level: 1

Type: ERROR

Impact: Configuration

TCM-91238: Unable to acquire next available task for {0}

Cause: Failed to acquire next available task in workflow.

Action: There may be no task for this user in the workflow. Check the workflow server log.
Level: 1

Type: ERROR

Impact: Configuration

TCM-91239: Unable to update transaction ID in workflow payload

Cause: Failed to update transaction ID in workflow payload.

Action: Verify Transaction field exists in the workflow payload.
Level: 1

Type: ERROR

Impact: Configuration

TCM-91240: Unable to get comments

Cause: Failed to get comments from workflow.

Action: Check the user's permission to get comments. Check the workflow server log.
Level: 1

Type: ERROR

Impact: Configuration

TCM-91241: Comment is null.

Cause: The value of Comment was null.

Action: Contact your system administrator.
Level: 1

Type: ERROR

Impact: Configuration

TCM-91242: Unable to update comment in workflow

Cause: Failed to update the comment in workflow.

Action: User may not have permission to update the comment. Check the workflow server log.
Level: 1

Type: ERROR

Impact: Configuration

TCM-91243: Invalid URL for identity search URL

Cause: Received URL was Invalid for identity search

Action: Check the URL for identity search in the database
Level: 1

Type: ERROR

Impact: Configuration

TCM-91244: Unable to open the connection for identity search URL

Cause: Failed to open the connection for identity search URL.

Action: Verify that the Web service is available for identity search.
Level: 1

Type: ERROR

Impact: Configuration

TCM-91245: Unable to parse the XML date received from identity search URL

Cause: Failed to parse XML date received from identity search URL

Action: Check the XML format of input file as it may be invalid. There may be some invalid tag in the file
Level: 1

Type: ERROR

Impact: Configuration

TCM-91246: Unable to acquire the task. Task is not assigned to the group or is assigned to a different user.

Cause: Either the task was not assigned to the group or it was assigned to a different user.

Action: Select another task from the list.
Level: 1

Type: ERROR

Impact: Configuration

TCM-91247: Invalid Task attribute Key {0}

Cause: Received Invalid Task attribute Key.

Action: Check your configuration or command for the attribute Key value
Level: 1

Type: ERROR

Impact: Configuration

TCM-92002: Access is denied.

Cause: User does not have access to the requested information.

Action: Ensure user is defined with proper permissions.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92501: Duplicate annotation IDs exist

Cause: Duplicate annotation IDs exist.

Action: Ensure that each annotation has a unique id. Annotations cannot be added more than once.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92502: Null or empty annotation Id specified

Cause: Null or empty annotation Id specified.

Action: Ensure that annotation id is not null or empty.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92503: Null annotation object specified

Cause: Invalid annotation object specified.

Action: Ensure that annotation object is not null and has a valid Id.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92504: Annotation list is Null

Cause: Annotation list to search is null.

Action: Ensure that annotation list object is not Null.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92505: Annotation requires at least three points

Cause: This annotation requires at least three points.

Action: Provide three points, or use a LineAnnot object.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92506: There was an error deserializing an annotation file for this document.

Cause: There was an error deserializing an annotation file for this document.

Action: Check the nested exception details for diagnostic information.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92507: There was an error serializing an annotation file for this document.

Cause: There was an error serializing an annotation file for this document.

Action: Check the nested exception details for diagnostic information.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92508: An annotation list cannot be merged with itself

Cause: An annotation list cannot be merged with itself.

Action: Specify a unique list of annotations.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92509: A null value was supplied where an AnnotPoint object is expected.

Cause: A null value was supplied where an AnnotPoint object is expected

Action: Provide a valid AnnotPoint object
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92510: The requested scale is not within the allowed value range; {0}-{1}

Cause: The requested scale is not within the allowed value range.

Action: Provide a proper scale value within the supported range.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92511: Page number must be a positive value.

Cause: Page number must be a positive value.

Action: Provide a page number that is greater than zero.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92512: Bounding rectangle specified is empty.

Cause: Bounding rectangle specified is empty.

Action: Supply a non-null, non-empty rectangle definition.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92513: The Document Store provider {0} cannot be loaded

Cause: The specified Document Store could not be loaded

Action: Make sure the provided class is correct and that it exists in the classpath
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92514: Redact annotation cannot be assigned HIDDEN security.

Cause: Redact annotation cannot be assigned HIDDEN security.

Action: Use a different security setting.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92515: The page annotations include at least one annotation from another page.

Cause: An attempt was made to replace page annotations with at least one annotation from a different page.

Action: Supply only annotations for the page specified.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92516: Error deserializing annotations. InputStream is null.

Cause: Error deserializing annotations. InputStream is null.

Action: Supply a serialized annotation stream.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92517: Transformation process returned error code {0}.

Cause: Transformation process returned an error code.

Action: See the transformation process return code for diagnostic information.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92518: There was an error launching the external transformation process: {0} {1}

Cause: There was an error launching the external transformation process

Action: The transformation process failed unexpectedly. Check nested exception details for diagnostic information.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92521: The path specified for GdFontPath configuration is invalid.

Cause: The path specified for GdFontPath configuration is invalid.

Action: Provide a valid path to a directory containing True Type Fonts.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92522: There was an error reading TIFF headers. The file may be corrupt.

Cause: There was an error reading TIFF headers. The file may be corrupt.

Action: Check permissions and free space in the server temp directory.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92700: The cache config file can not be found

Cause: The cache configuration file was not found.

Action: Inspect the Cache jar and verify that the CacheConfig.xml file exists.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92701: The cache storage configuration is not in the config file

Cause: The configuration for the cache storage adaptor could not be found.

Action: Add a valid storage adaptor to the cache config file.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92702: The cache configuration file cannot be read for processing

Cause: The cache configuration file could not be read.

Action: Please examine the inner exception to determine why the read operation failed.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92703: The cache storage adaptor could not be found

Cause: The storage adaptor implementation could not be found.

Action: Check the cache config file and verify that the storage adaptor is correct.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92704: The cache storage adaptor could not be instantiated

Cause: The storage adaptor could not be loaded.

Action: Examine the adaptor code and verify it has a parameterless constructor.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92705: Error writing to Lock file {0}.

Cause: There was a problem writing to a file.

Action: Check the inner exception to determine the cause of the error.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92706: A lock could not be acquired on lock file {0}.

Cause: The lock file could not be locked and validated.

Action: Check the inner exception to determine the cause of the error.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92707: The directory {0} could not be created.

Cause: The specified directory could not be created.

Action: Examine the path to make sure it is not full and that the server account has write privileges to it.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92708: The Document ID {0} is not valid.

Cause: The Document ID that was specified is not valid.

Action: Pass in a valid Document ID to the cache service.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92709: An error occurred while queuing the cache request for processing.

Cause: An exception was raised while attempting to queue the cache request.

Action: Look at the inner exception to get details on the cause of the error.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92710: The cache repository interface configuration value was not found.

Cause: The configuration for the repository interface could not be found.

Action: Add a valid repository interface to the cache config file.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92711: The configuration string for the repository interface could not be parsed.

Cause: The configuration information for the repository interface is not valid.

Action: Look at the repository configuration and make sure that the values are separated by semicolons.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92712: The viewer cache IPM repository interface could not be initialized.

Cause: The viewer cache IPM repository interface could not be initialized for processing.

Action: Examine the inner exception to get specifics on why the initialization failed.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92713: The viewer cache repository could not retrieve requested document {0}.

Cause: The requested document could not be retrieved from the viewer cache repository.

Action: Examine the inner exception to get specifics on why the operation failed.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92714: The viewer cache repository interface {0} could not be found.

Cause: The cache repository implementation could not be found.

Action: Check the cache config file and verify that the repository configuration is correct.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92715: An instance of the viewer cache repository {0} could not be created.

Cause: The cache repository could not be loaded.

Action: Examine the inner exception and repository implementation to determine the load error.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92716: The viewer cache repository could not get the annotations for document {0}.

Cause: The requested annotation set could not be retrieved from the viewer cache repository.

Action: Examine the inner exception to get specifics on why the operation failed.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92717: The file {0} can not be found for processing.

Cause: The requested file could not be found for processing.

Action: Determine if the file exists and has the correct permissions.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92718: {0} is not a valid document page.

Cause: The requested page to retrieve from cache is invalid.

Action: Check the cache request and verify the requested page is greater than 0.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92719: The requested page range of {0} to {1} is not valid.

Cause: The requested cache page range is invalid.

Action: Check the end page of the cache request and verify that it is greater than the start page.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92720: The cache directory for object {0} could not be locked for processing

Cause: The cache lock file failed verification.

Action: Check to make sure that the IPM services have full access to the directory and it is not shared with other IPM systems.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92721: A failure occurred while attempting to get configuraiton values from IPM.

Cause: An error was encountered while trying to look up the configuration data.

Action: Look at the nested error to get the exact cause of the error.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92722: Page number {0} is invalid, document {1} only has {2} pages.

Cause: The requested page is not in the document.

Action: Request a page number that is in the document's page range.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92723: Processing was aborted while waiting for results.

Cause: The operation was stopped while waiting for the operations results.

Action: Check the logs to see if an operation was forcibly stopped.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92724: An error was encountered while trying to read or write to the image stream.

Cause: A failure occurred while reading or writing from an image.

Action: Check the inner exception to determine the cause of the error.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92725: The image could not be converted to a PNG stream because the image writer could not be found or have its options set.

Cause: The PNG image writer could not be loaded or could not have its options set.

Action: Check the Java installation and verify all the libraries are installed.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92726: Could not get the annotation security for document {0}.

Cause: The document's annotation security could not be determined.

Action: Check the inner exception to determine the cause of the error.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92727: This document contains annotations that prevent the user from accessing this document in its raw format

Cause: This document contains annotations that prevent the user from accessing this document in its raw format.

Action: Export to TIFF with the annotations burned in or contact your administrator for access to the native format.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92728: The image information for document {0}, page {1} could not be read.

Cause: The image information could not be read.

Action: Check the inner exception to determine the cause of the error.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-92999: An error occurred in a subsystem. {0}

Cause: An error occurred in a rendering subsystem.

Action: Review the logs for the error. You may need to contact Oracle Support Services to resolve the issue.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-99001: The repository definition identifier, {0}, is not valid.

Cause: An attempt was made to add a repository configuration with a duplicate identifier.

Action: Use a unique identifier.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-99002: The repository definition name, {0}, is not valid.

Cause: An attempt was made to add a repository configuration with a duplicate name.

Action: Use a unique name.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-99003: The repository definition identifier, {0}, is not unique.

Cause: An attempt was made to add a repository configuration with a duplicate identifier.

Action: Use a unique identifier.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-99004: The repository definition name, {0}, is not unique.

Cause: An attempt was made to add a repository configuration with a duplicate name.

Action: Use a unique name.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-99005: A system repository definition already exists.

Cause: An attempt was made to add a system repository configuration when one already exists.

Action: Remove the existing system repository first.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-99006: The destination repository is read only and does not support this operation.

Cause: An attempt was made to copy or move a document to a repository that is not writeable.

Action: Change the destination repository to one that is writeable.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-99007: The destination repository is not the same as the source repository.

Cause: An attempt was made to move a document to a different repository.

Action: Ensure that the source and destination repositories are the same.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-99008: The destination repository is not the same type as the source repository.

Cause: An attempt was made to move a document to a different type of repository.

Action: Ensure that the source and destination repositories are the same type.
Level: 1

Type: ERROR

Impact: Requests/Responses

TCM-99009: The repository must be initialized to support IPM prior to creating a connection.

Cause: An attempt was made to create a connection to a system that is not yet configured.

Action: Ensure that target UCM system is configured prior to creating a connection.
Level: 1

Type: ERROR

Impact: Requests/Responses

92 TOP-00001 to TOP-72023

TOP-00001: The attribute [{0}] is not declared as type ValueHolderInterface, but its mapping uses indirection.

Cause: attributeName is not declared as type ValueHolderInterface, but the mapping uses indirection. The mapping is set to use indirection, but the related attribute is not defined as type ValueHolderInterface. It is raised on foreign reference mappings.

Action: If you want to use indirection on the mapping, change the attribute to type ValueHolderInterface. Otherwise, change the mapping associated with the attribute so that it does not use indirection.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00002: The attribute [{0}] is declared as type ValueHolderInterface, but its mapping does not use indirection.

Cause: attributeName is declared as type ValueHolderInterface, but TopLink is unable to use indirection. The attribute is defined to be of type ValueHolderInterface, but the mapping is not set to use indirection. It is raised on foreign reference mappings.

Action: If you do not want to use indirection on the mapping, change the attribute so it is not of type ValueHolderInterface. Otherwise, change the mapping associated with the attribute to use indirection.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00006: Attribute name is missing.

Cause: The attribute name is missing or not specified in the mapping definition.

Action: Specify the attribute name in the mapping by calling the method setAttributeName(String attributeName).
Level: 1

Type: ERROR

Impact: Configuration

TOP-00007: The attribute [{0}] should be of type Vector (or a type that implements Map or Collection, if using Java 2).

Cause: When using Java 2, the specified attributeName is not defined as type vector, or a type that implements the Map or Collection interface. This occurs in one-to-many mapping, many-to-many mapping, and collection mapping when mapping is set not to use indirection, and the attribute type is not declared.

Action: Declare the attribute to be of type java.util.Vector.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00008: The descriptor [{0}] has been set to use inheritance, but a class indicator field has not been defined. {2}When using inheritance, a class indicator field or class extraction method must be set. {2}Parent Descriptor: [{1}]

Cause: The class indicator field is defined, but the descriptor is set to use inheritance. When using inheritance, a class indicator field or class extraction method must be set. The class indicator field is used to create the right type of domain object.

Action: Set either a class indicator field or class extraction method.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00009: This mapping does not have a direct field name set.

Cause: The direct field name from the target table is not set in the direct collection mapping.

Action: Specify the direct field name by calling the method setDirectFieldName(String fieldName).
Level: 1

Type: ERROR

Impact: Configuration

TOP-00010: This mapping does not have a field name set.

Cause: The field name is not set in the mapping. It is raised from direct to field mapping, array mapping, and structure mapping.

Action: Specify the field name by calling the method setFieldName(String fieldName).
Level: 1

Type: ERROR

Impact: Configuration

TOP-00011: The foreign key information for this mapping is defined incorrectly.

Cause: One-to-one mapping foreign key is defined incorrectly. Multiple foreign key fields were set for one-to-one mapping by calling the method setForeignKeyFieldName(String fieldName).

Action: Use the method addForeignKeyFieldName(String sourceForeignKeyName, String targetPrimaryKeyFieldName) to add multiple foreign key fields.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00012: Descriptors must use an identity map in order to use the "Check Cache" existence checking option.

Cause: The descriptor has been set not to use identity map, but the existence checking is set to be performed on identity map: the descriptor must use an identity map to use the Check cache does exist option.

Action: Either use identity map, or set the existence checking to some other option.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00013: The instance variable [{0}] in the object [{1}] is inaccessible.

Cause: TopLink is unable to access the attributeName instance variable in object objectName. The instance variable in the domain object is not accessible. This exception is raised when TopLink tries to access the instance variable using the java.lang.reflect Java package. The error is a purely Java exception, and TopLink wraps only the reflection exception.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00014: Problem in cloning the object [{0}]. The clone method [{1}] is not accessible.

Cause: TopLink is unable to clone the object domainObject because the clone method methodName is not accessible. The method name specified using useCloneCopyPolicy(String cloneMethodName) or the clone() method to create the clone on the domain object, is not accessible by TopLink using Java reflection. The error is a purely Java exception, and TopLink wraps only the reflection exception.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00015: This class does not define a default constructor, which TopLink requires.

Cause: The domain class does not define a public default constructor, which TopLink needs to create new instances of the domain class.

Action: Define a public default constructor or use a different instantiation policy.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00016: The descriptor callback method [{0}], with parameter (DescriptorEvent), is inaccessible.

Cause: The descriptor callback method eventMethodName with DescriptorEvent as an argument is not accessible. This exception is raised when TopLink tries to access the event method using Java reflection. The error is a purely Java exception, and TopLink wraps only the reflection exception.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00017: Trying to access the method [{0}] on the object [{1}]. The underlying method is inaccessible.

Cause: Attempt to invoke inaccessible methodName on the object objectName. The underlying getter method to access an attribute in the domain object is not accessible. This exception is raised when TopLink tries to access an attribute through a method using the java.lang.reflect Java package. The error is a purely Java exception, and TopLink wraps only the reflection exception.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00018: Illegal method access in a Transformation mapping using a ValueHolder.

Cause: The method used by the transformation mapping using a value holder is invalid. This exception is raised when TopLink tries to access the method using Java reflection. The problem occurs when the method base valueholder is instantiated.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00019: Illegal access while invoking the attribute method on a Transformation mapping. The underlying method is inaccessible.

Cause: On transformation mapping, the underlying attribute method that is used to retrieve values from the database row while reading the transformation mapped attribute is not accessible.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00020: The method [{0}] is inaccessible.

Cause: On transformation mapping, the method methodName that is used to retrieve value from the object while writing the transformation mapped attribute is not accessible. The error is a purely Java exception, and TopLink wraps only the reflection exception.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00021: Problem in extracting class from row [{0}]. The static method [{1}], with parameter (DatabaseRow), is not accessible.

Cause: TopLink is unable to extract data row, because TopLink cannot access the row specified in the databaseRow argument of the method. The method to extract class from row on the domain object is not accessible. The error is a purely Java exception, and TopLink wraps only the reflection exception.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00022: Problem in creating new instance. The creation method [{0}] is not accessible.

Cause: TopLink is unable to create a new instance, because the method methodName that creates instances on the domain class is not accessible. The error is a purely Java exception, and TopLink wraps only the reflection exception.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00023: The descriptor callback method [{0}], with parameter (Session), is inaccessible.

Cause: The descriptor callback method eventMethodName with Session as an argument is inaccessible. This exception is raised when TopLink tries to access the event method using Java reflection. The error is a purely Java exception, and TopLink wraps only the reflection exception.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00024: The instance variable [{0}] in the object [{1}] is inaccessible. {3}Argument: [{2}]

Cause: The attributeName instance variable in the object objectName is not accessible through Java reflection. The error is raised by Java, and TopLink wraps only the reflection exception.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00025: The method [{0}] with argument [{1}] is not accessible.

Cause: TopLink is unable to invoke a method setMethodName on the object with parameter parameter. The attribute's set accessor method is not accessible through Java reflection. The error is raised by Java and TopLink wraps only the reflection exception.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00026: Trying to get value for instance variable [{0}] of type [{1}] from the object [{2}]. The specified object is not an instance of the class or interface declaring the underlying field.

Cause: TopLink is unable to get a value for an instance variable attributeName of type typeName from the object. The specified object is not an instance of the class or interface declaring the underlying field. An object is accessed to get the value of an instance variable that does not exist.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00027: Trying to invoke the method [{0}] on the object [{1}]. The number of actual and formal parameters differs, or an unwrapping conversion has failed.

Cause: TopLink is unable to invoke method methodName on the object objectName. The get accessor method declaration on the domain object differs from the one that is defined. The number of actual and formal parameters differ, or an unwrapping conversion has failed.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00028: Illegal argument while instantiating a method-based proxy in a Transformation mapping.

Cause: The method that the method-based proxy uses in a transformation mapping is receiving invalid arguments when the valueholder is being instantiated. This exception is raised when TopLink tries to access the method using the java.lang.reflect Java package.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00029: The number of actual and formal parameters differs, or an unwrapping conversion has failed.

Cause: The number of actual and formal parameters differs, or an unwrapping conversion has failed. On transformation mapping, the method used to retrieve values from the database row while reading the transformation mapped attribute is getting an invalid argument.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00030: The number of actual and formal parameters differs for method [{0}], or an unwrapping conversion has failed.

Cause: The number of actual and formal parameters differs for method methodName, or an unwrapping conversion has failed. On transformation mapping, the method used to retrieve value from the object while writing the transformation mapped attribute is getting an invalid argument. The error is a purely Java exception, and TopLink wraps only the reflection exception.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00031: The number of actual and formal parameters for the descriptor callback method [{0}] differs, or an unwrapping conversion has failed.

Cause: The number of actual and formal parameters for the descriptor callback method eventMethodName differs, or an unwrapping conversion has failed. The callback event method is invoked with an invalid argument. This exception is raised when TopLink tries to invoke the event method using Java reflection. The error is a purely Java exception, and TopLink wraps only the reflection exception.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00032: Trying to set value [{0}] for instance variable [{1}] of type [{2}] in the object. The specified object is not an instance of the class or interface declaring the underlying field, or an unwrapping conversion has failed.

Cause: An invalid value is being assigned to the attribute instance variable. TopLink is unable to set a value for an instance variable attributeName of type typeName in the object. The specified object is not an instance of the class or interface that is declaring the underlying field, or an unwrapping conversion has failed. TopLink assigns value by using Java reflection. Java raises the error and TopLink wraps only the reflection exception.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00033: Trying to invoke [{0}] on the object [{1}]. The number of actual and formal parameters differs, or an unwrapping conversion has failed.

Cause: An illegal argument is being passed to the attribute's set accessor method. TopLink is unable to invoke method setMethodName on the object. The number of actual and formal parameters differs, or an unwrapping conversion has failed. Java raises the error and TopLink wraps only the reflection exception.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00034: This class does not define a public default constructor, or the constructor raised an exception.

Cause: The class does not define a public default constructor, or the constructor raised an exception. This error occurs when you invoke the default constructor for the domain object to create a new instance of the object while building new domain objects if:The class represents an abstract class, an interface, an array class, a primitive type, or void.The instantiation fails for some other reason. Java raises the error and TopLink wraps only the reflection exception.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00035: Invalid event.

Cause: Applications should never encounter this exception. This exception usually occurs at the time of developing TopLink, although in cases, where you write new mapping, it is possible to get this exception. In direct collection mapping and many-to-many mapping, the target table and relational table are populated at the end of the commit process, and if a data modification event is sent to any other mapping, then this exception is raised.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00036: Invalid event code [{0}].

Cause: An application should never encounter this exception. This exception usually occurs at the time of developing TopLink, although in cases, where you write new mappings, it is possible to get this exception. In direct collection mapping and many-to-many mapping, the target table and relational table are populated at the end of the commit process, and if a data modification event is sent to these two mappings with wrong event code, then this exception is raised.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00037: Invalid descriptor event code [{0}].

Cause: An application should never encounter this exception. This exception usually occurs at the time of developing TopLink. The exception means that the descriptor event manager does not support the event code passed in the event.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00038: Identity map constructor failed because an invalid identity map was specified.

Cause: The identity map constructor failed because an invalid identity map was specified. The identity map class given in the descriptor cannot be instantiated. The exception is a Java exception that is raised by a Java reflection when TopLink instantiates the identity map class. TopLink wraps only the Java exception.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00039: This descriptor does not specify a Java class.

Cause: The descriptor does not define a Java class. The Java class is not specified in the descriptor.

Action: Specify the Java class.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00040: Descriptor is missing for [{0}]. It was probably not added to the Session.

Cause: A descriptor for the referenced interface is not added to the session.

Action: Add that descriptor to the session.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00041: A non-read-only mapping must be defined for the sequence number field.

Cause: A non-read-only mapping is not defined for the sequence number field. A mapping is required so that TopLink can put and extract values for the primary key.

Action: Define a mapping.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00043: Missing class for indicator field value [{0}] of type [{1}].

Cause: TopLink is missing the class for indicator field value classFieldValue of type type. There was no class entry found in the inheritance policy for the indicator field value that was read from the database. It is likely that the method addClassIndicator(Class class, Object typeValue) was not called for the field value. The class and typeValue are stored in a hash table, and later the class is extracted from the hash table by passing typeValue as a key. Because Integer(1) is not equivalent to Float(1), this exception occurs when the type of typeValue is incorrectly specified.

Action: Verify the descriptor.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00044: Missing class indicator field from database row [{0}].

Cause: The class indicator field is missing from the database row that was read from the database. This is performed in the inheritance model where after reading rows from the database, child domain objects are to be constructed depending upon the type indicator values.

Action: Verify the printed row for correct spelling.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00045: Missing mapping for field [{0}].

Cause: TopLink is missing a mapping for field; a mapping for the field is not specified.

Action: Define a mapping for the field.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00046: There should be one non-read-only mapping defined for the primary key field [{0}].

Cause: A mapping for the primary key is not specified. There should be one non-read-only mapping defined for the primary key field.

Action: Define a mapping for the primary key.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00047: The multiple table primary key mapping must be specified when a custom multiple table join is used.

Cause: The multiple table primary key mapping is not specified when a custom multiple table join is used. If multiple tables are specified in the descriptor and the join expression is customized, then the primary keys for all the tables must be specified. If the primary keys are not specified, then the exception occurs.

Action: Call the method addMultipleTablePrimaryKeyFieldName(String fieldNameInPrimaryTable, String fieldNameInSecondaryTable) on the descriptor to set the primary keys.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00048: Multiple writable mappings exist for the field [{0}]. Only one may be defined as writable, all others must be specified read-only.

Cause: Multiple writable mappings for the field fieldName are defined in the descriptor. Exactly one must be defined as writable; the others must be specified as read-only. When multiple write mappings are defined for the field, TopLink is unable to choose the appropriate mapping for writing the value of the field in the database row. Therefore, the exception is raised during the validation process of descriptors. The most common cause of this problem is when the field has direct-to-field mapping, as well as one-to-one mapping. In this case, the one-to-one mapping must either be read-only or a target foreign key reference.

Action: Make one of those mappings read-only.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00049: An attribute transformation method name is not specified for this mapping.

Cause: The attribute transformation method name in the transformation mapping is not specified. This method is invoked internally by TopLink to retrieve value to store in the domain object.

Action: Define a method and set the method name on the mapping by calling the method setAttributeTransformation(String methodName).
Level: 1

Type: ERROR

Impact: Configuration

TOP-00050: A field name is not set for this mapping.

Cause: No field name is specified in direct-to-field mapping.

Action: Set the field by calling setFieldName(String fieldName).
Level: 1

Type: ERROR

Impact: Configuration

TOP-00051: No foreign keys have been specified for this mapping.

Cause: Neither the selection criteria nor the foreign keys were specified on one-to-one mapping. If the selection criterion is not specified, then TopLink tries to build one from the foreign keys specified in the mapping.

Action: Specify the fields.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00052: No reference key has been specified for this mapping.

Cause: No query key named queryKey is found in descriptor. No reference key from the target table is specified on direct collection mapping.

Action: Specify the fields by calling the method setReferenceKeyFieldName(String fieldName).
Level: 1

Type: ERROR

Impact: Configuration

TOP-00053: The relation table name is not set for this mapping.

Cause: The relation table name is not set in this many-to-many mapping.

Action: Set the relation table name by calling the method setRelationTableName(String tableName).
Level: 1

Type: ERROR

Impact: Configuration

TOP-00054: There are no source relation keys specified for this mapping.

Cause: There are no source relation keys specified in this many-to-many mapping.

Action: Add source relation keys to the mapping.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00055: The descriptor callback method [{0}] cannot be found. It must take a Session or a DescriptorEvent as its argument.

Cause: TopLink cannot find the descriptor callback method on the domain class. It must take a Session or a DescriptorEvent as its argument. TopLink tries to invoke the method using Java reflection. It is a Java exception and TopLink is wrapping only the main exception.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00056: The method [{0}] with parameters (Record) or (Record, Session) is not found.

Cause: TopLink cannot find the method methodName(Record databaseRow) or methodName(Record databaseRow, Session session). TopLink wraps the Java reflection exception that is caused when the method is being created from the method name. This method is set by calling setAttributeMethodName(String aMethodName).

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00057: Inaccessible constructor.

Cause: The constructor is inaccessible to TopLink. TopLink wraps the Java reflection exception that is caused when it is creating a new instance of the domain.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00058: The method [{0}] with parameters () or (Session) not found.

Cause: TopLink failed to find a method with signature methodName() or methodName(oracle.toplink.sessions.Session). TopLink wraps the Java reflection exception that was raised by its attempt to create a Method type (java.lang.reflect) from the method names in the transformation mapping.

Action: Ensure that the method methodName is defined on the domain class that owns the attribute mapped by the transformation mapping.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00059: The instance variable [{0}] is not defined in the domain class [{1}], or it is not accessible.

Cause: The instance variable attributeName is not defined in the domain class, or it is not accessible. TopLink wraps the Java reflection exception that is caused when it is creating a Field type (java.lang.reflect.Field) from the attribute name.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00060: The method [{0}] or [{1}] is not defined in the object [{2}].

Cause: The method setMethodName or getMethodName is not defined for the attribute in the domain class javaClassName, or it is not accessible. TopLink wraps the Java reflection exception that is caused when it is creating a Method type from the method name.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00061: The static class extraction method [{0}], with parameter (Record), does not exist, or is not accessible.

Cause: The static class extraction method methodName(Record databaseRow) does not exist, or is not accessible. A Java reflection exception wrapped in a TopLink exception is raised when a class extraction method is being created from the method name in the inheritance policy.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00062: The clone method [{0}], with no parameters, does not exist, or is not accessible.

Cause: The clone method methodName() does not exist, or is not accessible. A Java reflection exception wrapped in a TopLink exception is raised when a method to create clones is being created from the method name in the copy policy.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00063: The instance creation method [{0}], with no parameters, does not exist, or is not accessible.

Cause: The instance creation method methodName() does not exist, or is not accessible. A Java reflection exception wrapped in a TopLink exception is raised when a method to create the new instance is being created from the method name in the instantiation policy.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00064: No target foreign keys have been specified for this mapping.

Cause: The foreign keys in the target table are not specified in one-to-many mappings. These fields are not required if a selection criterion is given in the mapping, but otherwise they must be specified.

Action: Set target foreign keys or selection criteria.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00065: No target relation keys have been specified for this mapping.

Cause: There are no target relation keys specified in many-to-many mappings.

Action: Call method addTargetRelationKeyFieldName(String targetRelationKeyFieldName, String targetPrimaryKeyFieldName) to set the fields.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00066: Could not deserialize object from byte array.

Cause: Attempt to deserialize an object from the byte array that is read from the database. The exception is raised when the serialized object mapping is converting the byte array into an object.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00067: Could not serialize object into byte array.

Cause: Attempt to serialize an object into a byte array. The exception is raised when a serialized object mapping is converting the object into a byte array.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00068: The value of an aggregate in object [{0}] is null. Null values not allowed for Aggregate mappings unless "Allow Null" is specified.

Cause: The value of the aggregate in the source object object is null. Null values are not allowed for aggregate mappings unless allow null is specified in the aggregate mapping.

Action: Call the mapping method allowNull. Provide parameters only if you are making a distinction between foo() and foo(integer).
Level: 1

Type: ERROR

Impact: Configuration

TOP-00069: A NullPointerException was thrown while extracting a value from the instance variable [{0}] in the object [{1}].

Cause: An object is accessed to get the value of an instance variable through Java reflection. This exception is raised only on some JVMs.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00070: A NullPointerException was thrown while extracting a value through the method [{0}] in the object [{1}].

Cause: The getter method is invoked to get the value of an attribute through Java reflection. This exception is raised only on some JVM.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00071: A NullPointerException was thrown while setting the value of the instance variable [{0}] to the value [{1}].

Cause: A NullPointerException has been raised while setting the value of the attributeName instance variable in the object to value. An object is accessed to set the value of an instance variable through Java reflection. This exception is raised only on some JVMs.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00072: A NullPointerException was thrown while setting a value through the method [{0}] with argument [{1}].

Cause: A NullPointerException has been raised while setting the value through setMethodName method in the object with an argument argument. The set accessor method is invoked to set the value of an attribute through Java reflection. This exception is raised only on some JVMs.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00073: Cannot find descriptor for parent class [{0}].

Cause: TopLink is unable to find the descriptor for the parent class. The descriptor of a subclass has no parent descriptor.

Action: The method setParentClass(Class parentClass) must be called on the subclass descriptor.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00074: The primary key fields are not set for this descriptor.

Cause: The primary key fields are not set for this descriptor.

Action: Add primary key field names using method setPrimaryKeyFieldName(String fieldName).
Level: 1

Type: ERROR

Impact: Configuration

TOP-00075: The reference class is not specified for this descriptor.

Cause: The reference class is not specified in the foreign reference mapping.

Action: Set the reference class by calling the method setReferenceClass(Class aClass).
Level: 1

Type: ERROR

Impact: Configuration

TOP-00077: The reference descriptor for [{0}] should be set to be an Aggregate descriptor.

Cause: The referenced descriptor for class className is not set to an aggregate descriptor. An aggregate mapping should always reference a descriptor that is aggregate.

Action: Call the method descriptorIsAggregate on the referenced descriptor.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00078: The reference field [{0}] for this mapping must exist in the reference table.

Cause: The table for the reference field is not the reference table. If the reference field name that is specified in the direct collection mapping is qualified with the table name, then the table name should match the reference table name.

Action: Qualify the field with the proper name, or change the reference table name.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00079: The reference table is not specified for this mapping.

Cause: The reference table name in the direct collection mapping is not specified.

Action: Use the method setReferenceTableName(String tableName) on the mapping to set the table name.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00080: The relation key field [{0}] for this mapping must exist in the relation table.

Cause: The table for the relation key field is not the relation table. If the source and target relation fields names that are specified in the many-to-many mapping are qualified with the table name, then the table name should match the relation table name.

Action: Qualify the field with the proper name, or change the relation table name.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00081: The method [{0}] should return the type of the mapped attribute, not void.

Cause: The method attributeMethodName that is specified in the transformation mapping does not have a return type set in the attribute, as it should because this method is used to extract value from the database row.

Action: Verify the method and make appropriate changes.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00082: The descriptor callback method [{0}], with parameter (DescriptorEvent), is not accessible.

Cause: The descriptor callback method with DescriptorEvent as an argument is not accessible. Java raises a security exception when a Method type is created from the method name using Java reflection. The method is a descriptor event callback on the domain object that takes DescriptorEvent as its parameter.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00083: The descriptor callback method [{0}], with parameter (Session), is not accessible.

Cause: The descriptor callback method with Session as an argument is not accessible. Java raises a security exception when a Method type is created from the method name using Java reflection. The method is a descriptor event callback on the domain object, which takes class and session as its parameters.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00084: The method [{0}], with parameters (Record) or (Record, Session), is not accessible.

Cause: Access to the method methodName(Record databaseRow) or methodName(Record databaseRow, Session session) has been denied. Java raises a security exception when a Method type is created from the attribute method name using Java reflection. The attribute method that is specified in the transformation mapping is used to extract value from the database row and set by calling setAttributeTransformation(String methodName).

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00085: The method [{0}], with parameters () or (Session), is not accessible.

Cause: TopLink failed to find a method with signature methodName() or methodName(oracle.toplink.sessions.Session). Java raises a security exception when a Method type is created from the method name using Java reflection. These are the methods that extract the field value from the domain object in the transformation mapping.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00086: The instance variable [{0}] in the class [{1}] is not accessible.

Cause: Access to the instance variable attributeName in the class javaClassName is denied. Java raises a security exception when creating a Field type from the given attribute name using Java reflection.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00087: The methods [{0}], [{1}] in the object [{2}] are not accessible

Cause: The methods setMethodName and getMethodName in the object javaClassName are inaccessible. Java raises a security exception when creating a Method type from the given attribute accessor method name using Java reflection.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00088: The static class extraction method [{0}], with parameter (Record), is not accessible.

Cause: The static class extraction method methodName(Record databaseRow) is not accessible. Java raises a security exception when creating a Method type from the given class extraction method name using Java reflection. The method is used to extract the class from the database row in the inheritance policy.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00089: The clone method [{0}], with no parameters, is not accessible.

Cause: The clone method methodName() is inaccessible. Using ClassDescriptor method useCloneCopyPolicy (java.lang.String methodName), you can specify that the creation of clones within a unit of work is done by sending the methodName method to the original object. If the clone method methodName with no arguments is inaccessible (your application does not have sufficient privileges to call the method), Java raises a security exception when reflectively accessing the method with the given method name using the java.lang.reflect Java package.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00090: The instance creation method [{0}], with no parameters, is not accessible.

Cause: The instance creation method methodName() is inaccessible. Using any of the ClassDescriptor methods useFactoryInstantiationPolicy (java.lang.Class factoryClass, java.lang.String methodName), useFactoryInstantiationPolicy (java.lang.Class factoryClass, java.lang.String methodName, java.lang.String factoryMethodName), useFactoryInstantiationPolicy (java.lang.Object factory, java.lang.String methodName), or useMethodInstantiationPolicy(java.lang.String staticMethodName), you can specify how new instances are created. If any of the methods or factory methods are inaccessible (your application does not have sufficient privileges to call the method), Java raises a security exception when reflectively accessing the method with the given method name using the java.lang.reflect Java package.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00091: To use sequence-generated IDs, both the "Sequence Number Name" and "Sequence Number Field Name" properties must be set for this descriptor.

Cause: Either the sequenceNumberName or the sequenceNumberFieldName property is not set. To use sequence-generated IDs, both the sequenceNumberName and sequenceNumberFieldName properties must be set for the descriptor.

Action: To use sequence-generated IDs, set both the sequence number name and field name properties.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00092: The size of the target''s primary key does not match the size of the foreign key.

Cause: The size of the primary keys on the target table does not match the size of the foreign keys on the source in one-to-one mapping.

Action: Verify the mapping and the reference descriptor's primary keys.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00093: The table [{0}] is not present in this descriptor.

Cause: The table tableName is not present in the descriptor.

Action: Verify the qualified field names that are specified in the mappings and descriptor so that any fields that are qualified with the table name reference the correct table.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00094: Descriptors must have a table name defined.

Cause: No table is specified in the descriptor. The descriptor must have a table name defined.

Action: Call the method addTableName(String tableName) or setTableName(String tableName) to set the tables on the descriptor.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00096: The number of target keys does not match the number of source keys.

Cause: The size of the foreign keys on the target table does not match the size of the source keys on the source table in the one-to-many mapping.

Action: Verify the mapping.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00097: Problem cloning the object [{0}]. The clone method [{0}] triggered an exception.

Cause: TopLink has encountered a problem in cloning the object domainObject clone method. The methodName triggered an exception. Java raises this exception when the cloned object is invoked while the object is being cloned. The clone method is specified on the copy policy that is usually invoked to create clones in unit of work.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00098: The underlying descriptor callback method [{0}], with parameter (DescriptorEvent), triggered an exception.

Cause: A descriptor callback method eventMethodName(DescriptorEvent event) is not accessible. The exception occurs when the descriptor event method is invoked using Java reflection.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00099: The method [{0}] on the object [{1}] triggered an exception.

Cause: The method methodName on the object objectName is throwing an exception. Java is throwing an exception while getting an attribute value from the object through a method accessor.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00100: A method has triggered an exception.

Cause: A method has raised an exception. Java raises this exception while instantiating a method based proxy and instantiating transformation mapping.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00101: The underlying method triggered an exception.

Cause: The underlying method raises an exception. Java is throwing an exception while invoking an attribute transformation method on transformation mapping. The method is invoked to extract value from the database row to set into the domain object.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00102: The method [{0}] triggered an exception.

Cause: The method methodName is throwing an exception. Java is throwing exception while invoking field transformation method on transformation mapping. The method is invoked to extract value from the domain object to set into the database row.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00103: Problem in extracting class from row [{0}], using static method [{1}], with parameter (DatabaseRow). An exception was triggered.

Cause: TopLink encountered a problem extracting the class type from row rowName while invoking a class extraction method.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00104: Problem in creating new instance using creation method [{0}]. The creation method triggered an exception.

Cause: TopLink is unable to create a new instance. The creation method methodName caused an exception.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00105: The underlying descriptor callback method [{0}], with parameter (Session), triggered an exception.

Cause: The underlying descriptor callback method eventMethodName(Session session) raises an exception. Java is throwing an exception while invoking a descriptor event method that takes a session as its parameter.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00106: The method [{0}] on the object is throwing an exception. {2}Argument: [{1}]

Cause: The method setMethodName on the object raises an exception. Java is throwing an exception while invoking a set accessor method on the domain object to set an attribute value into the domain object.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00108: Cannot find value in class indicator mapping in parent descriptor [{0}].

Cause: The indicator value is not found in the class indicator mapping in the parent descriptor for the class.

Action: Verify the addClassIndicator(Class childClass, Object typeValue) on the inheritance policy.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00109: This descriptor should not have a write lock field defined because it is a child descriptor. It inherits its parent descriptor''s write lock field.

Cause: The child descriptor has a write-lock field defined. This is unnecessary, because it inherits any required locking from the parent descriptor.

Action: Check your child descriptor, and remove the field.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00110: Descriptor is missing for class [{0}].

Cause: The descriptor for the reference class className is missing from the mapping.

Action: Verify the session to see if the descriptor for the reference class was added.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00111: Multiple table primary key field names must be fully qualified.

Cause: Multiple table primary key field names are not fully qualified. These field names are given on the descriptor if it has more than one table.

Action: Specify the field names with the table name.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00112: Only one table can be added by using setTableName(String). Use addTableName(String) to add multiple tables to a descriptor.

Cause: Attempt to enter more than one table through this method.

Action: Use the method addTableName(String tableName) to add multiple tables to the descriptor.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00113: The constructor was inaccessible.

Cause: The constructor is inaccessible. Java is throwing this exception while invoking a default constructor to create new instances of the domain object.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00114: Problem in creating new instance using creation method [{0}]. The creation method is not accessible.

Cause: The new instance methodName creation method is inaccessible. Java is throwing an exception while calling a method to a build new instance of the domain object. This method is given by the user to override the default behavior of creating new instances through a class constructor.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00115: No conversion value provided for the attribute [{0}].

Cause: The field conversion value for the attribute value attributeValue was not given in the object type mapping.

Action: Verify the attribute value, and provide a corresponding field value in the mapping.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00116: No conversion value provided for the value [{0}] in field [{1}].

Cause: The attribute conversion value for the fieldValue was not given in the object type mapping.

Action: Verify the field value, and provide a corresponding attribute value in the mapping.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00118: The object [{0}] must not have read-only mappings to its write lock fields.

Cause: The domain object className cannot have a read-only mapping for the write-lock fields when the version value is stored in the object.

Action: Verify the mappings on the write-lock fields.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00119: The object''s [{0}] mappings to its write lock fields must be read-only.

Cause: The domain object className does not have a read-only mapping for the write-lock fields when the version value is stored in the cache.

Action: Verify the mappings on write-lock fields.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00120: The query key [{0}] is defined in the parent descriptor [{1}], but not in the child descriptor [{2}].

Cause: The query key queryKeyName is defined in the parent descriptor, but not in the child descriptor. The descriptor has not defined the abstract query key.

Action: Define any class that implements the interface descriptor by the abstract query key in the interface descriptor.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00122: setExistenceCheck() with argument [{0}] is not understood.

Cause: The interface descriptor parent does not have at least one abstract query key defined. The string given to the method setExistenceChecking(String token) is not understood.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00125: The mapping for the attribute [{0}] uses indirection, and so must be initialized to a new ValueHolder. Currently the value is: [{1}].

Cause: The mapping for the attribute getAttributeName() uses indirection and must be initialized to a new value holder.

Action: Ensure that the mapping uses indirection and that the attribute is initialized to a new value holder.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00126: No subclass matches this class [{0}] for this Aggregate mapping with inheritance.

Cause: No subclass matches this class theClass when inheritance is in aggregate relationship mapping.

Action: Verify the subclass and the relationship mapping.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00127: The get method for the attribute [{0}] does not return a ValueHolderInterface, but the mapping uses indirection.

Cause: The return type of the method used to get the attribute getAttributeName() of a mapping is not declared as type ValueHolderInterface, but the mapping is using indirection.

Action: Verify that the method used to get the attribute named getAttributeName() of DatabaseMapping returns a value holder, or change the mapping so it does not use indirection.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00128: The get method for the attribute [{0}] returns a ValueHolderInterface, but the mapping does not use indirection.

Cause: The return type of the method used to get the attribute getAttributeName() of DatabaseMapping is declared as type ValueHolderInterface, but the mapping is not using indirection.

Action: Ensure that the mapping is using indirection, or change the return type from value holder.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00129: The set method for the attribute [{0}] does not take a ValueHolderInterface as its parameter, but the mapping uses indirection.

Cause: The return type of the method used to set the attribute getAttributeName() of DatabaseMapping is not declared as type ValueHolderInterface, but the mapping is using indirection.

Action: Ensure that the set method parameter is declared as a valueholder, or change the mapping so it does not use indirection.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00130: The set method for the attribute [{0}] takes a ValueHolderInterface as its parameter, but the mapping does not use indirection.

Cause: The return type of the method used to set the attribute getAttributeName() of DatabaseMapping is declared as type ValueHolderInterface, but the mapping is not using indirection.

Action: Ensure that the mapping is changed to use indirection, or that the method parameter is not declared as a value holder.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00131: The get method for the attribute [{0}] should return a Vector (or a type that implements Map or Collection, if using Java 2).

Cause: The return type of the method used to get the attribute getAttributeName() of DatabaseMapping is not declared as type Vector (or a type that implements the Map or Collection interface if using Java 2).

Action: Declare the return type of the method used to get the attribute getAttributeName() of DatabaseMapping as type Vector (or a type that implements the map or collection interface if using Java 2).
Level: 1

Type: ERROR

Impact: Configuration

TOP-00133: The set method for the attribute [{0}] should take a Vector as its parameter (or a type that implements Map or Collection, if using Java 2).

Cause: The parameter type of the method used to set the attribute getAttributeName() of DatabaseMapping is not declared as type Vector (or a type that implements the map or collection interface, if using Java 2).

Action: Declare the parameter type of the method used to set the attribute getAttributeName() of DatabaseMapping as type Vector (or a type that implements the Map or Collection interface, if using Java 2).
Level: 1

Type: ERROR

Impact: Configuration

TOP-00135: The multiple table foreign key relationship refers to an unknown table [{0}].

Cause: The table in the multiple table foreign key relationship refers to an unknown table.

Action: Verify the table name.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00138: The attribute [{0}] is not declared as a superclass of [{1}], but the mapping uses transparent indirection.

Cause: The attribute getAttributeName() of DatabaseMapping is not declared as a supertype of validTypeName, but the mapping is using transparent indirection.

Action: Verify the attribute's type and the mapping setup.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00139: The get method for the attribute [{0}] does not return a superclass of [{1}], but the mapping uses transparent indirection.

Cause: The return type of the method used to get the attribute getAttributeName() of DatabaseMapping is not declared as a super-type of validTypeName, but the mapping is using transparent indirection.

Action: Verify the attribute's type and the mapping setup.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00140: The set method for the attribute [{0}] does not take a superclass of [{1}] as its parameter, but the mapping uses transparent indirection.

Cause: The parameter type of the method used to set the attribute getAttributeName() of DatabaseMapping is not declared as a supertype of validTypeName, but the mapping is using transparent indirection.

Action: Verify the attribute's type and the mapping setup.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00141: The field [{0}] is not present in the table [{1}] in the database.

Cause: The field fieldname is not present in the table tableName in the database.

Action: Verify the field name for the attribute.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00142: The table [{0}] is not present in the database.

Cause: The table whose name is provided by the Descriptor method getTableName is not present in the database.

Action: Verify the table name for the descriptor.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00143: The multiple table insert order Vector specified, [{0}], has more or fewer tables than are specified in the descriptor. {2}All of the tables [{1}] must be included in the insert order Vector.

Cause: The multiple table insert order vector specified the Descriptor method getMultipleTableInsertOrder has fewer or more tables than are specified in the Descriptor method getTables. All the tables must be included in the insert order vector.

Action: Ensure that all table names for the descriptor are present and that there are no extra tables.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00144: Transparent indirection can only be used with CollectionMappings.

Cause: Transparent indirection is being used with a mapping other than a CollectionMapping.

Action: Verify the mapping. It must be a collection mapping.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00145: The indirect container class [{0}] must implement the constructor [{1}] with parameter (ValueHolderInterface).

Cause: The indirect container class does not implement the constructor.

Action: Implement the constructor for the container.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00146: The indirect container class [{0}] could not be instantiated using the constructor {1}(ValueHolderInterface).

Cause: TopLink is unable to instantiate the indirect container class using the constructor.

Action: Validate the constructor for the indirect container class.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00147: The container policy [{0}] should only be used in JDK 1.1.x. It was instantiated for [{1}].

Cause: You have used a container policy with an incompatible version of the JDK. This container policy must only be used with JDK 1.3.1 or later.

Action: Validate the container policy being used.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00148: The container policy [{0}] is not compatible with transparent indirection.

Cause: The container policy is incompatible with transparent indirection.

Action: Change the container policy to be compatible with transparent indirection, or do not use transparent indirection.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00149: NoIndirectionPolicy objects should not receive this message.

Cause: NoIndirectionPolicy object calls this method.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00150: The mapping for the attribute [{0}] uses transparent indirection so the attribute [{0}] must be initialized to an appropriate container. Currently the value is [{1}]. {2} - Must be instance of an implementor of Collection or Map.

Cause: The mapping for the attribute getAttributeName() of DatabaseMapping uses transparent indirection and must be initialized to an appropriate container.

Action: Initialize the mapping to an appropriate container.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00151: The operation [{0}] is invalid for this mapping.

Cause: An invalid mapping operation has been used.

Action: See the documentation for valid mapping operations.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00152: The operation [{1}] is invalid for this indirection policy [{0}].

Cause: An invalid indirection policy operation has been used.

Action: See the documentation for valid indirection policy operations.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00153: The reference descriptor for [{0}] should be set to be an Aggregate Collection descriptor.

Cause: The reference descriptor for className is not set to an aggregate collection descriptor.

Action: Set the reference descriptor to an aggregate collection descriptor.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00154: The indirection container class [{0}] does not implement IndirectContainer.

Cause: An invalid indirection container class has been used.

Action: Verify the container class.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00155: This mapping does not include a foreign key field linked to the primary key field [{0}].

Cause: The mapping does not include a foreign key field linked to the primary key field.

Action: Link the foreign key to the appropriate primary key.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00156: The structure name is not set for this mapping.

Cause: The structure name is not set.

Action: Set the structure name appropriately.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00157: Normal descriptors do not support non-relational extensions.

Cause: Relational descriptors do not support nonrelational extensions.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00158: This descriptor''s parent class has been set to itself.

Cause: The descriptor's parent class has been set to itself.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00159: Proxy indirection is available only in JDK 1.3-compliant or higher virtual machines.

Cause: An attempt to use proxy indirection has been made, but JDK 1.3.1 or later is not being used.

Action: Use JDK 1.3.1 or later.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00160: The attribute [{0}] of class [{1}] is typed as [{2}], which was not specified in the list of interfaces given to the useProxyIndirection() method. {4}Valid interfaces are: [{3}].

Cause: The attribute was not specified in the list of interfaces given to use proxy indirection.

Action: Verify the attribute.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00161: The method [{0}] in class [{1}] returns a value of type [{2}], which was not specified in the list of interfaces given to the useProxyIndirection() method. {4}Valid interfaces are: [{3}].

Cause: The return type for the indirection policy is invalid for the indirection policy.

Action: Ensure that the parameter type of the getter method is correct for the indirection policy.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00162: The method [{0}] in class [{1}] takes a parameter of type [{2}], which was not specified in the list of interfaces given to the useProxyIndirection() method.{4}Valid interfaces are: [{3}].

Cause: The parameter for the setter method is incorrect for the indirection type.

Action: Ensure that the parameter type of the setter method is correct for the indirection policy.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00163: This mapping''s attribute class does not match the collection class. [{1}] cannot be assigned to [{0}].

Cause: The container policy is invalid for the collection type.

Action: Ensure that the container policy is correct for the collection type.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00164: The amendment method [{1}], in amendment class [{0}], is invalid, not public, or cannot be found. {2}Descriptor amendment methods must be declared "public static void" with (ClassDescriptor) as the single parameter.

Cause: The amendment method that is provided is invalid, not public, or cannot be found.

Action: Ensure that the amendment method is public, static, returns void, and has a single argument: Descriptor.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00165: This descriptor''s amendment method [{1}] in amendment class [{0}] triggered an exception.

Cause: The specified amendment method threw an exception.

Action: Examine the returned exception for further information.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00166: There is no mapping for the attribute [{0}].

Cause: There is no mapping for the attribute.

Action: Validate the mapping and attribute.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00167: A valid constructor was not found for the indirection container class [{0}].

Cause: A valid constructor was not found for the indirection container class.

Action: Add a default constructor or a constructor with a ValueHolderInterface in the container class.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00168: Problem in creating new instance using the default constructor. The default constructor triggered an exception.

Cause: The constructor is missing.

Action: Create the required constructor.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00169: Problem in creating new instance of factory using the default constructor. The default constructor triggered an exception.

Cause: The constructor is missing.

Action: Create the required constructor.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00170: Problem (illegal access) in creating new instance of factory using the default constructor.

Cause: Permissions do not allow access to the constructor.

Action: Adjust the Java security permissions to permit access to the constructor.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00171: The factory class does not define a public default constructor, or the constructor raised an exception.

Cause: An instantiation failed inside the associated constructor.

Action: Determine which objects are being instantiated, and verify that all are instantiated properly.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00172: Factory constructor not found.

Cause: A method call from inside the constructor is invalid because this method does not exist.

Action: Ensure that the factory has a default constructor for the called method.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00173: The factory constructor was inaccessible.

Cause: A method on a null object was called from inside a constructor. The factory constructor was inaccessible.

Action: Examine the internal exception and take the appropriate action.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00174: Problem in creating factory. The creation method [{0}] is not accessible.

Cause: A method was called on an object from inside a factory instantiation, and Java has determined this method to be invalid.

Action: Determine why the method is invalid, and replace the method with a valid one.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00175: Problem creating factory using creation method [{0}]. The creation method triggered an exception.

Cause: A problem was encountered creating factory using creation method. The creation method triggered an exception.

Action: Examine the exception and take the corresponding action.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00176: Problem in creating factory using creation method [{0}]. The creation method is not accessible.

Cause: A method called to instantiate a factory threw a NullPointerException. The creation method is not accessible.

Action: Do not use that method to instantiate a factory.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00177: Mapping is missing for the attribute: [{0}].

Cause: Mapping is missing for the attribute attributeName.

Action: The attribute must be mapped.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00178: Cannot find mapping for attribute [{0}] in entity bean [{1}]. The attribute must mapped.

Cause: Cannot find mapping for an attribute attributeName in an entity bean beanName.

Action: Map the attribute.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00179: The attribute, [{0}] uses Bidirectional Relationship Maintenance, but has ContainerPolicy, [{1}] which does not support it. The attribute should be mapped with a different collection type.

Cause: The attribute uses bidirectional relationship maintenance, but has ContainerPolicy, which does not support it.

Action: The attribute must be mapped with a different collection type.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00181: The AttributeTransformer class, [{0}] cannot be found.

Cause: The AttributeTransformer class cannot be found.

Action: Ensure that the AttributeTransformer class exists and is on the classpath.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00182: The FieldTransformer class, [{0}] cannot be found.

Cause: The FieldTransformer class cannot be found.

Action: Ensure that the FieldTransformer class exists and is on the classpath.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00183: The class, [{0}] cannot be used as an AttributeTransformer.

Cause: Invalid use of a class className as an AttributeTransformer.

Action: Examine the internal exception stack trace and make the appropriate correction.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00184: The class, [{0}] cannot be used as a FieldTransformer.

Cause: Invalid use of a class className as a FieldTransformer.

Action: Do not use the class as a FieldTransformer.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00185: ReturningPolicy contains field, [{0}] with two different types: [{1}] and [{2}].

Cause: ReturningPolicy contains field with two different types.

Action: The field was added to ReturningPolicy twice with different types. The field must be added to ReturningPolicy once. You must remove excessive addFieldForInsert and/or addInsertField calls.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00186: ReturningPolicy contains field, [{0}] added twice: using addInsertField and addInsertFieldReturnOnly.

Cause: ReturningPolicy contains field that has been added twice using addInsertField and addInsertFieldReturnOnly.

Action: A field must be added to ReturningPolicy only once. You must remove excessive addField calls.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00187: ReturningPolicy contains field, [{0}] with type [{1}], but the same field in descriptor has type [{2}].

Cause: ReturningPolicy contains field with type Type, but the same field in descriptor has type differentType.

Action: Specify field type in addField method only in the event that it cannot be obtained from the descriptor.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00188: ReturningPolicy contains unmapped field, [{0}] which requires type.

Cause: ReturningPolicy contains unmapped field fieldName that requires type.

Action: You must specify field type in the addField method.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00189: ReturningPolicy contains mapped field, [{0}] which requires type.

Cause: ReturningPolicy contains mapped field fieldName that requires type.

Action: You must specify field type in the addField method.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00190: ReturningPolicy contains field, [{0}] mapped with [{1}] mapping which is not supported.

Cause: ReturningPolicy contains a field that is mapped with unsupported mapping.

Action: You cannot use ReturningPolicy with this field. Do not add it to ReturningPolicy.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00191: ReturningPolicy contains field, [{0}] which is not supported: it is either sequence field, or class type indicator, or used for locking.

Cause: ReturningPolicy contains a field fieldName that is not supported. Field is either sequence field, class type indicator, or used for locking.

Action: You cannot use ReturningPolicy with this field. Do not add it to ReturningPolicy.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00192: ReturningPolicy contains field, [{0}] but custom [{1}] doesn't output it.

Cause: ReturningPolicy contains a field fieldName, but custom query queryName does not output it.

Action: Update the custom query so that it outputs a value for this field.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00193: There is no custom [{0}] set, but ReturningPolicy contains field(s) to be returned and [{1}] doesn't support generating call with returning.

Cause: There is no custom query set, but ReturningPolicy contains one or more fields to be returned and doesn't support generating call with return.

Action: Specify a custom InsertObjectQuery or UpdateObjectQuery through DescriptorQueryManager setInsertQuery, setInsertCall, setUpdateQuery, or setUpdateCall methods that outputs values for fields added to ReturningPolicy.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00194: The class extraction method [{0}], must be a static method on the descriptor's class.

Cause: The class extraction method must be a static method on the descriptor's class.

Action: Make the class extraction method a static method on the descriptor's class.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00195: The shared class {1} must not reference the isolated class {0}.

Cause: The shared class must not reference the isolated class.

Action: Ensure that the shared class does not reference the isolated class.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00196: UpdateAllFields has not been set or has been set to false. When using CMPPolicy.setForceUpdate(true) you must also call CMPPolicy.setUpdateAllFields(true)

Cause: updateAllFields flag has not been set or has been set to false. When using setForceUpdate(true) method of CMPPolicy you must also call setUpdateAllFields(true) method of CMPPolicy.

Action: Ensure that updateAllFields is set to true if forceUpdate is true.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00197: The mapping [{0}] is not the appropriate type for this descriptor

Cause: A mapping of an inappropriate type has been set for this descriptor.

Action: The mapping type has to map the descriptor type, e.g. relational mapping for relational descriptor, EIS mapping for EIS descriptor, and XML mapping for XML descriptor.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00198: In order to use ObjectChangeTrackingPolicy or AttributeChangeTrackingPolicy, {0} has to implement ChangeTracker interface.

Cause: The object does not implement the ChangeTracker interface.

Action: Ensure that the object implements ChangeTrackerInterface in order to use ObjectChangeTrackingPolicy or AttributeChangeTrackingPolicy.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00199: In order to use Fetch Group, the domain class ({0}) has to implement FetchGroupTracker interface.

Cause: The domain class does not implement the FetchGroupTracker interface.

Action: Ensure that the domain class implements the FetchGroupTracker interface in order to use the fetch group.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00200: Attempt to register an object with dead indirection as a new object. Possibly the object was deleted or removed from the cache during a merge of a serialized clone. This is a concurrency violation, consider a locking strategy.

Cause: Attempt to register an object with dead indirection as a new object. Possibly, the object was deleted or removed from the cache during a merge of a serialized clone or did not exist in the cache at the time of the merge. This is a concurrency violation.

Action: Ensure that the object exists in the cache before attempting to merge a deserialized version into the cache. Consider a locking strategy. For more information, see "Merging Changes in Working Copy Clones" on page 112-12 and "Indirection, Serialization, and Detachment" on page 17-11.
Level: 1

Type: ERROR

Impact: Configuration

TOP-00201: An object was attempted to be built in the session cache, but the descriptor is marked as isolated in the unit of work, so should never be accessed outside of a unit of work.

Cause: Attempt to built and object in the session cache, but the descriptor is marked as isolated in the unit of work.

Action: Ensure that the descriptor is never accessed outside of a unit of work.
Level: 1

Type: ERROR

Impact: Configuration

TOP-02001: Wait was interrupted. {0}Message: [{1}]

Cause: In a multi threaded environment, one of the waiting threads was interrupted.

Action: Such exceptions are application-dependent.
Level: 1

Type: ERROR

Impact: Threads

TOP-02002: Wait failure on ServerSession.

Cause: A request for a connection from the connection pool has been forced to wait, and that wait has been interrupted.

Action: Such exceptions are application-dependent.
Level: 1

Type: ERROR

Impact: Threads

TOP-02003: Wait failure on ClientSession.

Cause: A request for a connection from the connection pool has been forced to wait, and that wait has been interrupted.

Action: Such exceptions are application-dependent.
Level: 1

Type: ERROR

Impact: Threads

TOP-02004: A signal was attempted before wait() on ConcurrencyManager. This normally means that an attempt was made to {0}commit or rollback a transaction before it was started, or to rollback a transaction twice.

Cause: A signal was attempted before a wait on concurrency manager. This usually means that an attempt was made to commit or roll back a transaction before it was started, or to rollback a transaction twice.

Action: Verify transactions in the application.
Level: 1

Type: ERROR

Impact: Threads

TOP-02005: Wait failure on Sequencing Connection Handler for DatabaseSession.

Cause: An InterruptedException was raised while DatabaseSession sequencing waited for a separate connection to become available.

Action: Examine concurrency issues involving object creation with your DatabaseSession.
Level: 1

Type: ERROR

Impact: Threads

TOP-02006: Attempt to acquire sequencing values through a single Connection({0}) simultaneously in multiple threads

Cause: Several threads attempted to concurrently obtain sequence objects from the same DatabaseSession or ClientSession.

Action: Avoid concurrent writing through the same DatabaseSession or ClientSession.
Level: 1

Type: ERROR

Impact: Threads

TOP-02007: Max number of attempts to lock object: {0} exceded. Failed to clone the object.

Cause: Maximum number of attempts to lock object was exceed resulting in a failure to clone the object.

Action: Ensure that the number of attempts is within the limit.
Level: 1

Type: ERROR

Impact: Threads

TOP-02008: Max number of attempts to lock object: {0} exceded. Failed to merge the transaction.

Cause: Maximum number of attempts to lock object was exceed resulting in a failure to merge the transaction.

Action: Ensure that the number of attempts is within the limit.
Level: 1

Type: ERROR

Impact: Threads

TOP-02009: Max number of attempts to lock object exceded. Failed to build the object. Thread: {0} has a lock on the object but thread: {1} is building the object

Cause: Maximum number of attempts to lock object was exceed resulting in a failure to build the object: thread threadNumber has a lock on the object, but thread anotherThreadNumber is building the object

Action: Ensure that the number of attempts is within the limit.
Level: 1

Type: ERROR

Impact: Threads

TOP-03001: The object [{0}], of class [{1}], could not be converted to [{2}].

Cause: Attempt to convert an object object of class ObjectClass to JavaClass. The object cannot be converted to a given type.

Action: Ensure that the object being converted is of the right type.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-03002: The object [{0}], of class [{1}], from mapping [{2}] with descriptor [{3}], could not be converted to [{4}].

Cause: Attempt to convert an object object of class ObjectClass from mapping mappingType to JavaClass. The object cannot be converted to a given type.

Action: Ensure that the object being converted is of the right type.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-03003: Incorrect date format: [{0}] (expected [YYYY-MM-DD])

Cause: The date in dateString is in an incorrect format. The expected format is YYYY-MM-DD.

Action: Verify the date format.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-03004: Incorrect time format: [{0}] (expected [HH:MM:SS])

Cause: The time in timeString is in an incorrect format. The expected format is HH:MM:SS.

Action: Verify the time format.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-03005: Incorrect timestamp format: [{0}] (expected [YYYY-MM-DD HH:MM:SS.NNNNNNNNN])

Cause: The timestamp timestampString is in an incorrect format. The expected format is YYYY-MM-DD HH:MM:SS.NNNNNNNNN.

Action: Verify the timestamp format.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-03006: [{0}] must be of even length to be converted to a byte array.

Cause: Attempt to convert String object of uneven length to a ByteArray. This object cannot be converted to a ByteArray.

Action: Verify the object being converted.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-03007: The object [{0}], of class [{1}], could not be converted to [{2}]. Please ensure that the class [{0}] is on the CLASSPATH. You may need to use alternate API passing in the appropriate class loader as required, or setting it on the default ConversionManager

Cause: Attempt to convert an object object of class ObjectClass to JavaClass. The class JavaClass is not on the classpath.

Action: Ensure that the class JavaClass is on the classpath.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-03008: Incorrect date-time format: [{0}] (expected [YYYY-MM-DD'T'HH:MM:SS])

Cause: Incorrect date-time format object. The expected format is YYYY-MM-DD'T'HH:MM:SS.

Action: Ensure that the date-time object is in the expected format of YYYY-MM-DD'T'HH:MM:SS.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-04003: Configuration error. Class [{0}] not found.

Cause: The driver class name was not found.

Action: Verify the class name given in JDBCLogin.
Level: 1

Type: ERROR

Impact: Configuration

TOP-04005: DatabaseAccessor not connected.

Cause: The session is not connected to the database while attempting to read or write on the database.

Action: An application may have to log in again because the connection to the database might have been lost.
Level: 1

Type: ERROR

Impact: Configuration

TOP-04006: Error reading BLOB data from stream in getObject().

Cause: An error occurred reading BLOB data from the database. There are two possibilities for this exception: either the BLOB data was not read properly from the result set or TopLink cannot process the BLOB data using ByteArrayOutputStream.

Action: Verify whether the underlying driver supports BLOBs properly. If it does, then report this problem to Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

TOP-04007: Could not convert object type due to an internal error. {0}java.sql.TYPES: [{1}]

Cause: Attempt to convert an object type on internal error.java.sql.TYPES = type. The object from the result set cannot be converted to the type that was returned from the metadata information.

Action: Verify whether the underlying driver supports the conversion type properly. If it does, then report this problem to Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

TOP-04008: You cannot logout while a transaction is in progress.

Cause: Attempt to log out while the transaction is still in progress. You cannot log out while a transaction is in progress.

Action: Wait until the transaction is finished.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-04009: The sequence table information is not complete.

Cause: The sequence information given to TopLink is not sufficiently complete to get the set of sequence numbers from the database. This usually happens on native sequencing on an Oracle database.

Action: Verify the data provided, especially the sequence name provided in TopLink.
Level: 1

Type: ERROR

Impact: Configuration

TOP-04011: Error preallocating sequence numbers. The sequence table information is not complete.

Cause: An error occurred preallocating sequence numbers on the database; the sequence table information is not complete.

Action: Ensure the sequence table was properly created on the database.
Level: 1

Type: ERROR

Impact: Configuration

TOP-04015: Synchronized UnitOfWork does not support the commitAndResume() operation.

Cause: A synchronized UnitOfWork does not support the commitAndResume operation. When the TopLink session is configured with an ExternalTransactionController, any unit of work requested by a client must operate within the context of a JTS external global transaction (see ). The JTS specification does not support the concept of check pointing a transaction-that is, committing the work performed and then continuing to work within the same transaction context. JTS does not support nested transactions, either. As a result, if a client code invokes commitAndResume on a synchronized unit of work, this error is reported.

Action: None required.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-04016: Configuration error. Could not instantiate driver [{0}].

Cause: A configuration error occurred when TopLink attempted to instantiate the given driver class. TopLink cannot instantiate the driver.

Action: Check the driver.
Level: 1

Type: ERROR

Impact: Configuration

TOP-04017: Configuration error. Could not access driver [{0}].

Cause: A configuration error occurred when TopLink attempted to instantiate the given driver class. TopLink cannot instantiate the driver.

Action: Check the driver.
Level: 1

Type: ERROR

Impact: Configuration

TOP-04018: The TransactionManager has not been set for the JTS driver.

Cause: The transaction manager has not been set for the JTSSynchronizationListener.

Action: Set a transaction manager for the JTSSynchronizationListener.
Level: 1

Type: ERROR

Impact: Configuration

TOP-05001: An attempt was made to delete the object [{0}], but it has no version number in the identity map. {3}It may not have been read before the delete was attempted. {3}Class> {1} Primary Key> {2}

Cause: Attempt to delete the object object that does not have a version number in the identity map. This object either was never read or has already been deleted.

Action: Use SQL logging to determine the reason for the exception. The last delete operation shows the object being deleted when the exception was raised.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-05003: The object [{0}] cannot be deleted because it has changed or been deleted since it was last read. {3}Class> {1} Primary Key> {2}

Cause: The object state has changed in the database. The object object cannot be deleted because it has changed or been deleted since it was last read. This usually means that the row in the table was changed by some other application.

Action: Refresh the object, which updates it with the new data from the database.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-05004: An attempt was made to update the object [{0}], but it has no version number in the identity map. {3}It may not have been read before the update was attempted. {3}Class> {1} Primary Key> {2}

Cause: An attempt has been made to update the object object that does not have a version number in the identity map. It may not have been read before being updated, or it has been deleted.

Action: Use SQL logging to determine the reason for the exception. The last update operation shows the object being updated when the exception was raised.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-05006: The object [{0}] cannot be updated because it has changed or been deleted since it was last read. {3}Class> {1} Primary Key> {2}

Cause: The object state has changed in the database. The object object cannot be updated because it has changed or been deleted since it was last read. This usually means that the row in the table was changed by some other application.

Action: Refresh the object, which updates it with the new data from the database.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-05007: The object [{0}] must have a non-read-only mapping to the version lock field.

Cause: The object object does not have a non-read-only mapping corresponding to the version lock field. The mapping, which is needed when the lock value is stored in the domain object rather than in a cache, was not defined for the locking field.

Action: Define a mapping for the field.
Level: 1

Type: ERROR

Impact: Configuration

TOP-05008: Must map the version lock field to java.sql.Timestamp when using Timestamp Locking

Cause: A write lock value that is stored in a domain object is not an instance of java.sql.Timestamp.

Action: Change the value of the attribute to be an instance of java.sql.Timestamp.
Level: 1

Type: ERROR

Impact: Configuration

TOP-05009: The object of class [{1}] with primary key [{0}] cannot be unwrapped because it was deleted since it was last read.

Cause: Attempt to unwrapped an object of class className with primary key key-the object was deleted since it had been last read.

Action: Ensure the existence of the object being upwrapped.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06001: Cursored SQL queries must provide an additional query to retrieve the size of the result set.

Cause: Additional size-retrieving query was not specified: cursored SQL queries must provide an additional query to retrieve the size of the result set. Failure to include the additional query causes this exception.

Action: Specify a size query.
Level: 1

Type: ERROR

Impact: Configuration

TOP-06002: Aggregated objects cannot be written/deleted/queried independently from their owners. {1}Descriptor: [{0}]

Cause: An aggregated object was deleted independently of its owner: aggregate objects cannot be written or deleted independent of their owners. No identity is maintained on such objects.

Action: Do not try to delete aggregate objects directly.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06003: The number of arguments provided to the query for execution does not match the number of arguments in the query definition.

Cause: The number of arguments provided to the query for execution does not match the number of arguments provided with the query definition.

Action: Check the query and the query execution.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06004: The object [{0}], of class [{1}], with identity hashcode (System.identityHashCode()) [{2}], {3}is not from this UnitOfWork object space, but the parent session''s. The object was never registered in this UnitOfWork, {3}but read from the parent session and related to an object registered in the UnitOfWork. Ensure that you are correctly{3}registering your objects. If you are still having problems, you can use the UnitOfWork.validateObjectSpace() method to {3}help debug where the error occurred. For more information, see the manual or FAQ.

Cause: The object clone of class clone.getClass() with identity hash code (System.identityHashCode()) (System.identityHashCode(clone)) is not from this unit of work space, but from the parent session. The object was never registered in this unit of work, but read from the parent session and related to an object registered in the unit of work.

Action: Verify that you are correctly registering your objects. If you are still having problems, use the validateObjectSpace method of the UnitOfWork to help debug where the error occurred.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06005: The object [{0}], of class [{1}], with identity hashcode (System.identityHashCode()) [{2}], {3}is the original to a registered new object. The UnitOfWork clones registered new objects, so you must ensure that an object {3}is registered before it is referenced by another object. If you do not want the new object to be cloned, use the{3}UnitOfWork.registerNewObject(Object) API. If you are still having problems, you can use the UnitOfWork.validateObjectSpace() {3}method to help debug where the error occurred. For more information, see the manual or FAQ.

Cause: The object clone of class clone.getClass() with identity hash code (System.identityHashCode()) (System.identityHashCode(clone)) is the original to a registered new object. Because the unit of work clones new objects that are registered, ensure that an object is registered before it is referenced by another object. If you do not want the new object to be cloned, use the registerNewObject(Object) method of the UnitOfWork.

Action: Verify that you are correctly registering your objects. If you are still having problems, use the validateObjectSpace method of the UnitOfWork to help debug where the error occurred.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06006: The mapping [{0}] does not support batch reading.

Cause: The mapping that does not support batch reading was used. The optimization of batch reading all the target rows is not supported for the mapping.

Action: The problem is a TopLink development problem, and you should never encounter this error code unless the mapping is a new custom mapping. Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06007: Missing descriptor for [{0}].

Cause: The descriptor for the reference class is missing. The descriptor related to the class or the object is not found in the session.

Action: Verify whether or not the related descriptor was added to the session, and whether or not the query is performed on the right object or class.
Level: 1

Type: ERROR

Impact: Configuration

TOP-06008: Missing descriptor for [{0}] for query named [{1}].

Cause: The descriptor DomainClassName for the query named queryName is missing. The descriptor where named query is defined is not added to the session.

Action: Verify whether or not the related descriptor was added to the session, and whether or not the query is performed on the right class.
Level: 1

Type: ERROR

Impact: Configuration

TOP-06013: Incorrect size query given to CursoredStream.

Cause: The size query given on the queries returning cursor streams is not correct. The execution of the size query did not return any size.

Action: If the cursor stream query was a custom query, then check the size of the query that was specified, or report this problem to Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

TOP-06014: Objects cannot be written during a UnitOfWork, they must be registered.

Cause: Attempt to write an object in a unit of work using modify queries. These objects must be registered.

Action: Prior to modification, register objects in the unit of work, so during commit the unit of work can perform the required changes to the database.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06015: Invalid query key [{0}] in expression.

Cause: The query key key does not exist. Usually this happens because of a misspelled query key.

Action: Check the query key that was specified in the expression and verify that a query key was added to the descriptor.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06016: Objects or the database cannot be changed through a ServerSession. All changes must be done through a ClientSession''s UnitOfWork.

Cause: Attempt to change an object or a database through the server session: all changes must be performed through a client session's unit of work. The objects cannot be changed on the server session by modifying queries. Objects are changed in the client sessions that are acquired from this server session.

Action: Use the client session's unit of work to change the object.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06020: No concrete class indicated for the type in the row [{0}].

Cause: No concrete class is indicated for the type in this row. The type indicator read from the database row has no entry in the type indicator hash table or if class extraction method was used, it did not return any concrete class type. The exception is raised when subclasses are being read.

Action: Check the class extraction method, if specified, or check the descriptor to verify all the type indicator values were specified.
Level: 1

Type: ERROR

Impact: Configuration

TOP-06021: Cursors are not supported for interface descriptors, or abstract class multiple table descriptors using expressions. Consider using custom SQL or multiple queries.

Cause: No cursor support is provided for abstract class multiple table descriptors using expressions.

Action: Consider using custom SQL or multiple queries.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06023: The list of fields to insert into the table [{0}] is empty. You must define at least one mapping for this table.

Cause: There are no fields to be inserted into the table. The fields to insert into the table table, are empty.

Action: Define at least one mapping for this table.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06024: Modify queries require an object to modify.

Cause: An object to modify has not been specified for a modify query.

Action: Verify that the query contains an object before executing.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06026: Query named [{0}] is not defined. Domain class: [{1}]

Cause: The query is not defined. When executing a query on the session, the parameter that takes the query is null.

Action: Verify that the query is passed properly.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06027: Query sent to a unactivated UnitOfWork.

Cause: The unit of work has been released and is now inactive.

Action: The unit of work, once released, cannot be reused unless the commitAndResume method is called.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06028: An attempt to read beyond the end of stream occurred.

Cause: Attempt to read from the cursor streams beyond its limits (beyond the end of the stream).

Action: Ensure that the stream is checked for an end of stream condition before attempting to retrieve more objects.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06029: A reference class must be provided.

Cause: The reference class in the query is not specified: a reference class must be provided.

Action: Ensure that the query is correct.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06030: Refreshing is not possible if caching is not enabled.

Cause: Attempt to refresh while the caching is not set: the read queries that skip the cache to read objects cannot be used to refresh the objects. Refreshing is not possible without identity.

Action: Ensure that the query is correct.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06031: size() is only supported on expression queries, unless a size query is given.

Cause: TopLink did not find a size query. Size is supported only on expression queries unless a size query is given.

Action: The cursor streams on a custom query should also define a size query.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06032: The SQL statement has not been properly set.

Cause: The SQL statement has not been properly set. The user should never encounter this error code unless queries have been customized.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

TOP-06034: Invalid query item expression [{0}].

Cause: TopLink is unable to validate a query item expression.

Action: Validate the expression being used.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06041: The selection object passed to a ReadObjectQuery was null.

Cause: The selection object that was passed to a ReadObjectQuery (or refresh) was null.

Action: Check setSelectionObject method on read query.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06042: A session name must be specified for non-object-level queries. See the setSessionName(String) method.

Cause: Data read and data modify queries are being executed without the session name. Only object-level queries can be directly executed by the session broker, unless the query is named.

Action: Specify the session name.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06043: ReportQueries without primary keys cannot use readObject(). {1}ReportQueryResult: [{0}].

Cause: Attempt to read the object by a ReportQuery without a primary key: the report query result that was returned is without primary key values. An object from the result can be created only if primary keys were also read.

Action: See the documentation about retrievePrimaryKeys method on report query.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06044: The primary key read from the row [{0}] during the execution of the query was detected to be null. Primary keys must not contain null.

Cause: The primary key that was read from the row databaseRow during the execution of the query was detected to be null: primary keys must not contain null.

Action: Check the query and the table on the database.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06045: The subclass [{0}], indicated in the row while building the object, has no descriptor defined for it.

Cause: The subclass has no descriptor defined for it.

Action: Ensure the descriptor was added to the session, or check class extraction method.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06046: Cannot delete an object of a read-only class. The class [{0}] is declared as read-only in this UnitOfWork.

Cause: Attempt to delete a read-only class.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06047: Invalid operator [{0}] in expression.

Cause: The operator used in the expression is not valid.

Action: Check ExpressionOperator class to see a list of all the operators that are supported.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06048: Illegal use of getField() [{0}] in expression.

Cause: Invalid use of getField method's data in the expression. This is a TopLink development exception that you should not encounter.

Action: Report this problem to Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06049: Illegal use of getTable() [{0}] in expression.

Cause: Invalid use of getTable method's data in the expression. This is a TopLink development exception that you should not encounter.

Action: Report this problem to Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06050: ReportQuery result size mismatch. Expecting [{0}], but retrieved [{1}]

Cause: The number of attributes requested does not match the attributes returned from the database in report query. This can happen as a result of a custom query on the report query.

Action: Check the custom query to ensure it is specified, or report the problem to Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06051: Partial object queries are not allowed to maintain the cache or be edited. You must use dontMaintainCache().

Cause: Attempt to cache a partial object: partial objects are never put in the cache. Partial object queries are not allowed to maintain the cache or to be edited. Use the dontMaintainCache method.

Action: Call the dontMaintainCache method before executing the query.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06052: An outer join (getAllowingNull or anyOfAllowingNone) is only valid for OneToOne, OneToMany, ManyToMany, AggregateCollection and DirectCollection Mappings, and cannot be used for the mapping [{0}].

Cause: Invalid use of an outer join: an outer join (getAllowingNull method) is valid only for one-to-one mappings and cannot be used for the mapping.

Action: Do not attempt to use the getAllowingNull method for mappings other than one-to-one.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06054: Cannot add the object [{0}], of class [{1}], to container class [{2}] using policy [{3}].

Cause: TopLink is unable to add an object to a container class using policy. This is TopLink development exception, and you should never encounter this problem unless a custom container policy has been written.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06055: The method invocation of the method [{0}] on the object [{1}], of class [{2}], triggered an exception.

Cause: The invocation of a method on the object anObject threw a Java reflection exception while accessing the method.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06056: Cannot create a clone of object [{0}], of class [{1}], using [{2}].

Cause: Attempt to create a clone of the object anObject using policy. This is a TopLink development exception, and you should never encounter this problem unless a custom container policy has been written.

Action: Report this problem to Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06057: The method [{0}] is not a valid method to call on object [{1}].

Cause: Invalid call of the method methodName on object aReceiver. This is a TopLink development exception, and you should never encounter this problem unless a custom container policy has been written.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06058: The method [{0}] was not found in class [{1}].

Cause: The method named methodName was not found in the class aClass. This exception is raised when looking for a clone method on the container class. The clone is needed to create clones of the container in unit of work.

Action: Define a clone method on the container class.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06059: The class [{0}] cannot be used as the container for the results of a query because it cannot be instantiated.

Cause: Attempt to instantiate a class aClass as the container for the results of a query-this class cannot be instantiated as a container. The exception is a Java exception that is raised when a new interface container policy is being created using Java reflection. TopLink wraps only the Java exception.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06060: Could not use object [{0}] of type [{1}] as a key into [{2}] of type [{3}]. The key cannot be compared with the keys currently in the Map.

Cause: Attempt to use the object anObject of type ObjectClass as a key into aContainer which is of type ContainerClass. The key cannot be compared with the keys currently in the map. This raises a Java reflection exception while accessing the method. TopLink wraps only the Java exception.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06061: Cannot reflectively access the method [{0}] for object [{1}], of class [{2}].

Cause: Attempt to reflectively access the method aMethod for object: anObject of type ObjectClass. This raises a Java reflection exception while accessing the method. TopLink wraps only the Java exception.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06062: The method [{0}], called reflectively on object [{1}], of class [{2}], triggered an exception.

Cause: The method aMethod was called reflectively on objectClass and threw an exception. The method aMethod raises a Java reflection exception while accessing a method. TopLink wraps only the Java exception.

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06063: Invalid operation [{0}] on cursor.

Cause: Invalid operation operationName on the cursor. The operation is not supported.

Action: Check the class documentation and look for the corresponding method to use.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06064: Cannot remove the object [{0}], of class [{1}], from container class [{2}] using policy [{3}].

Cause: Attempt to remove anObject of type anObjectClass from aContainerClass using policy. This is a TopLink development exception and you should never encounter this problem unless a custom container policy has been written.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06065: Cannot add the object [{0}], of class [{1}], to container [{2}].

Cause: Attempt to add an element to the collection container policy (cannot add object anObject of type ObjectClass to a ContainerClass).

Action: Inspect the internal exception, and refer to the Java documentation.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06066: The object [{0}], of class [{1}], with identity hashcode (System.identityHashCode()) [{2}], {3}has been deleted, but still has references. Deleted objects cannot be referenced after being deleted. {3}Ensure that you are correctly registering your objects. If you are still having problems, you can use the UnitOfWork.validateObjectSpace() {3}method to help debug where the error occurred. For more information, see the manual or FAQ.

Cause: Object references remained after the deletion of the object: the object clone of class clone.getClass with identity hash code (System.identityHashCode()) (System.identityHashCode(clone)) has been deleted, but it still has references.

Action: Ensure that you are correctly registering your objects. If you are still having problems, use the validateObjectSpace() method of the UnitOfWork to help identify where the error occurred.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06068: Cannot compare table reference to [{0}] in expression.

Cause: Attempt to compare table reference to data in expression.

Action: Check the expression.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06069: The field [{0}] in this expression has an invalid table in this context.

Cause: Field has invalid table in this context for field fieldName in expression.

Action: Check the expression.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06070: Invalid use of a query key [{0}] representing a "to-many" relationship in an expression. Use anyOf() rather than get().

Cause: Invalid use of a query key representing a one-to-many relationship in expression.

Action: Use the anyOf operator instead of the get operator.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06071: Invalid use of anyOf() for a query key [{0}] not representing a to-many relationship in an expression. Use get() rather than anyOf().

Cause: Invalid use of anyOf for a query key not representing a to-many relationship in expression.

Action: Use the get operator instead of the anyOf operator.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06072: Querying across a VariableOneToOneMapping is not supported. {2}Descriptor: [{0}] {2}Mapping: [{1}]

Cause: Attempt to query across a variable one-to-one mapping. This is not supported.

Action: Change the expression such that the query is not performed across a variable one-to-one mapping.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06073: Malformed expression in query. Attempting to print an object reference into an SQL statement for query key [{0}].

Cause: Ill-formed expression in query that is attempting to print an object reference into a SQL statement for queryKey.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06074: This expression cannot determine if the object conforms in memory. You must set the query to check the database.

Cause: Expression cannot determine if the object conforms in memory.

Action: Set the query to check the database; change the query such that it does not attempt to conform to the results of the query.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06075: Object comparisons can only use the equal() or notEqual() operators. Other comparisons must be done through query keys or direct attribute level comparisons. {1}Expression: [{0}]

Cause: Invalid operator was used for the object comparison: object comparisons can use only the equal or notEqual operators; other comparisons must be performed through query keys or direct attribute level comparisons.

Action: Ensure the query uses only equal and notEqual if object comparisons are being used.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06076: Object comparisons can only be used with OneToOneMappings. Other mapping comparisons must be done through query keys or direct attribute level comparisons. {2}Mapping: [{0}] {2}Expression: [{1}]

Cause: Unsupported type of mapping was used for the object comparison: object comparisons can be used only with one-to-one mappings; other mapping comparisons must be performed through query keys or direct attribute level comparisons.

Action: Use a query key instead of attempting to compare objects across the mapping.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06077: Object comparisons cannot be used in parameter queries. You must build the expression dynamically. {1}Expression: [{0}]

Cause: Object comparison was parameterized: object comparisons cannot be used in parameter queries.

Action: Change the query so that it does not attempt to use objects when using parameterized queries.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06078: The class of the argument for the object comparison is incorrect. {3}Expression: [{0}] {3}Mapping: [{1}] {3}Argument: [{2}]

Cause: An incorrect class of the argument was used for the object comparison.

Action: Ensure the class for the query is correct.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06079: Object comparison cannot be used for target foreign key relationships. Query on the source primary key instead. {3}Expression: [{0}] {3}Mapping: [{1}] {3}Argument: [{2}]

Cause: Object comparison was used for target foreign key relationships: object comparisons cannot be used for target foreign key relationships

Action: Query on the source primary key.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06080: Invalid database call [{0}]. The call must be an instance of DatabaseCall.

Cause: Invalid database call: the call must be an instance of DatabaseCall.

Action: Ensure the call being used is a DatabaseCall.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06081: Invalid database accessor [{0}]. The accessor must be an instance of DatabaseAccessor.

Cause: Invalid database accessor: the accessor must be an instance of DatabaseAccessor.

Action: Ensure the accessor being used is a DatabaseAccessor.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06082: The method [{0}] with argument types [{1}] cannot be invoked on Expression.

Cause: The nonexisting method methodName with argument type argTypes was invoked on an expression.

Action: Ensure the method being used is a supported method.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06083: Queries using in() cannot be parameterized. Disable either query preparation or binding.

Cause: The query that was using IN was parameterized: queries using IN cannot be parameterized.

Action: Disable the query prepare or binding.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06084: The redirection query was not configured properly. The class or method name was not set.

Cause: The redirection query was not configured properly: the class or method name was not set.

Action: Verify the configuration for the redirection class.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06085: The redirection query''s method is not defined or defined with the wrong arguments. It must be declared "public static" and have arguments (DatabaseQuery, Record, Session) or (Session, Vector). {2}Class: [{0}] {2}Method: [{1}]

Cause: The redirection query's method is not defined or it is defined with the wrong arguments. It must be public static and have the following arguments: DatabaseQuery, DatabaseRow, or Session (the interface).

Action: Check the redirection query's method.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06086: The redirection query''s method invocation triggered an exception.

Cause: The static invoke method provided to MethodBaseQueryRedirector threw an exception when invoked.

Action: Check the static invoke method for problems.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06087: The example object class [{0}] does not match the reference object class [{1}].

Cause: There is a class mismatch between the example object and the reference class specified for this query.

Action: Ensure that the example and reference classes are compatible.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06088: There are no attributes for the ReportQuery.

Cause: A ReportQuery has been built with no attributes specified.

Action: Specify the attribute for the query.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06089: The expression has not been initialized correctly. Only a single ExpressionBuilder should be used for a query. {1}For parallel expressions, the query class must be provided to the ExpressionBuilder constructor, and the query''s ExpressionBuilder must {1}always be on the left side of the expression. {1}Expression: [{0}]

Cause: The expression has not been initialized correctly. Only a single ExpressionBuilder should be used for a query. For parallel expressions, the query class must be provided to the ExpressionBuilder constructor, and the query's ExpressionBuilder must always be on the left side of the expression.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06090: Cannot set ReportQuery to "check cache only".

Cause: The checkCacheOnly method was invoked on a ReportQuery. You cannot invoke the checkCacheOnly method on a ReportQuery, because a ReportQuery returns data rather than objects and the TopLink cache is built with objects.

Action: Do not use a ReportQuery in this case.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06091: The type of the constant [{0}], used for comparison in the expression, does not match the type of the attribute [{1}].

Cause: The type of the constant used for comparison in the expression does not match the type of the attribute.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06092: Uninstantiated ValueHolder detected. You must instantiate the relevant Valueholders to perform this in-memory query.

Cause: Uninstantiated value holders have been detected.

Action: Instantiate the value holders for the collection on which you want to query.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06094: The parameter name [{0}] in the query''s selection criteria does not match any parameter name defined in the query.

Cause: An unmapped field was used in a parameterized expression.

Action: Map the field or define an alternate expression that does not rely on the unmapped field.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06095: Public clone method is required.

Cause: A delegate class of an IndirectContainer implementation does not implement Cloneable. If you implement IndirectContainer you must also implement Cloneable. For example, see oracle.toplink.indirection.IndirectSet. The clone method must clone the delegate. For example, the IndirectSet implementation uses reflection to invoke the clone method because it is not included in the common interface shared by IndirectSet and its base delegate class, HashSet.

Action: Ensure that your IndirectContainer implementation or its delegate class implements Cloneable.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06096: Clone method is inaccessible.

Cause: A delegate class of an IndirectContainer implementation implements Cloneable but the IndirectContainer implementation does not have access to the specified clone method. That is, a java.lang.IllegalAccessException is raised when the delegate's clone method is invoked.

Action: Ensure that both the delegate clone method and the delegate class are public. Ensure permission is set for Java reflection in your VM security settings. See also the invoke method of java.lang.reflect.Method.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06097: clone method threw an exception: {0}.

Cause: A delegate class of an IndirectContainer implementation implements Cloneable and the IndirectContainer implementation has access to the specified clone method, but the specified clone method raises a java.lang.reflect.InvocationTargetException when invoked.

Action: Verify the implementation of the delegate's clone method.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06098: Unexpected Invocation Exception: {0}.

Cause: A proxy object method raises an unexpected exception when invoked (that is, some exception other than InvocationTargetException and ValidationException.)

Action: Review the proxy object to see where it is throwing the exception described in the exception message. Ensure this exception is no longer raised.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06099: Joining across inheritance class with multiple table subclasses not supported: {0}, {1}

Cause: Joining with query across inheritance class with multiple table subclasses. This is not supported: joining cannot be used on relationships with inheritance classes that have subclasses that span multiple tables as this requires multiple separate queries. The multiple queries cannot be joined into a single query.

Action: Use batch reading on the relationship instead, as this will provide equivalent or better performance.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06100: Multiple values detected for single-object read query.

Cause: Multiple values detected for single-object read query. This is a CMP compliance option that ensures the finder methods for a single object only return a single row.

Action: Set the system property toplink.cts.checkMultipleRows to false, or ensure that the finder query only returns a single row from the database.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06101: Executing this query could violate the integrity of the global session cache which must contain only the latest versions of objects. In order to execute a query that returns objects as of a past time, try one of the following: Use a HistoricalSession (acquireSessionAsOf), all objects read will be cached and automatically read as of the same time. This will apply even to triggering object relationships. Set shouldMaintainCache to false. You may make any object expression as of a past time, provided none of its fields are represented in the result set (i.e. used only in the where clause).

Cause: Executing this query could violate the integrity of the global session cache which must contain only the latest versions of objects.

Action: To execute a query that returns objects of a historical nature, you must do one of the following:Use a HistoricalSession (acquireSessionAsOf). All objects read will be cached and automatically read at that time. This applies also to triggering object relationships.Set shouldMaintainCache to false. You may make any object expression as of a previous time, provided none of its fields are represented in the result set (i.e. used in the where clause).
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06102: At present historical queries only work with Oracle 9R2 or later databases, as it uses Oracle's Flashback feature.

Cause: Invalid database was used: historical queries only work with Oracle 9.2.0.4 or later databases, as it uses the Oracle database Flashback feature.

Action: Ensure that historical queries are only used with an Oracle 9.2.0.4 or later database.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06103: You may not execute a WriteQuery from inside a read-only HistoricalSession. To restore past objects, try the following: read the same object as it is now with a UnitOfWork and commit the UnitOfWork.

Cause: Invalid query was executed on a historical session: you may not execute a WriteQuery from inside a read-only HistoricalSession. To restore historical objects, try the following: read the same object as it is now with a UnitOfWork and commit the UnitOfWork.

Action: To restore historical objects, read the same object as it is now with a UnitOfWork and commit the UnitOfWork.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06104: The object, {0}, does not exist in the cache.

Cause: The object does not exist in the cache.

Action: Ensure that the object exists in the cache.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06105: Query has to be reinitialized with a cursor stream policy.

Cause: The cursor stream policy was not used on the query instantiation.

Action: Reinitialize the query with a cursor stream policy.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06106: The object of type [{0}] with primary key [{1}] does not exist in the cache.

Cause: The object with primary key does not exist in the cache.

Action: Ensure that the object exists in the cache.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06107: Missing update statements on UpdateAllQuery.

Cause: Missing update statements on UpdateAllQuery.

Action: Add update statements using the addUpdate method.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06108: Update all query does not support inheritance with multiple tables

Cause: For UpdateAllQuery, inheritance was used with multiple tables: UpdateAllQuery does not support inheritance with multiple tables.

Action: Do not use UpdateAllQuery in this situation.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06109: The named fetch group ({0}) is not defined at the dscriptor level.

Cause: The named fetch group is not defined at the descriptor level.

Action: Ensure the fetch group is defined in the descriptor.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06110: Read query cannot conform the unfetched attribute ({0}) of the partially fetched object in the unit of work identity map.

Cause: Read query cannot conform to the unfetched attribute of the partially fetched object in the unit of work identity map.

Action: Do not use unfetched attribute conforming, or explicitly fetch the attribute before conforming.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06111: The fetch group attribute ({0}) is not defined or not mapped.

Cause: The fetch group attribute is not defined or mapped.

Action: Ensure that any attribute defined in a fetch group is defined in the class and mapped.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06112: Fetch group cannot be set on report query.

Cause: A fetch group was set on report query: fetch groups cannot be set on report queries.

Action: Remove the fetch group setting on ReportQuery, or use ReadObjectQuery or ReadObjectQuery instead.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06113: Fetch group cannot be used along with partial attribute reading.

Cause: Fetch group was used together with partial attribute reading: fetch groups cannot be used together with partial attribute reading.

Action: Remove the partial attribute reading setting in the query.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06114: You must define a fetch group manager at descriptor ({0}) in order to set a fetch group on the query ({1})

Cause: A fetch group manager is not defined at the descriptor while attempting to set a fetch group on a query.

Action: You must define a fetch group manager at the descriptor in order to set a fetch group on the query.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06115: Queries on isolated classes, or queries set to use exclusive connections, must not be executed on a ServerSession or, in CMP, outside of a transaction.

Cause: An isolated query was executed on a server session: queries on isolated classes, or queries set to use exclusive connections, must not be executed on a ServerSession or in CMP outside of a transaction.

Action: Do not execute queries on isolated classes or queries set to use exclusive connections on a ServerSession or in CMP outside of a transaction.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06116: No Call or Interaction was specified for the attempted operation.

Cause: No call or interaction method was specified for the attempted operation.

Action: Specify a call or interaction method.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06117: Can not set a query, that uses a cursored result, to cache query results.

Cause: A query that uses a cursored result to cache query results was set.

Action: Do not cache query results or do not use a cursor policy.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06118: A query on an Isolated class must not cache query results on the query.

Cause: Query on an isolated class attempted to cache query results on the query.

Action: Do not cache query results for a query on an isolated class.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06119: The join expression {0} is not valid, or for a mapping type that does not support joining.

Cause: The join expression is not valid, or is for a mapping type that does not support joining.

Action: Joining is supported only for one-one and one-many mappings.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06120: The partial attribute {0} is not a valid attribute of the class {1}.

Cause: The partial attribute attributeName is not a valid attribute of the class className.

Action: Ensure that this attribute exists, and is mapped.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06121: The query has not been defined correctly, the expression builder is missing. For sub and parallel queries ensure the queries builder is always on the left.

Cause: The query has not been defined correctly: the expression builder is missing.

Action: Ensure the queries builder is always on the left for sub queries and parallel queries.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06122: The expression is not a valid expression. {0}

Cause: Attempt to use an invalid expression expression.

Action: Ensure the correctness of the expression.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06123: The container class specified [{0}] cannot be used because the container needs to implement {1}.

Cause: Invalid container class specified: the container class className cannot be used, because the container needs to implement interfaceName.

Action: Ensure that the class specified as a container implements the correct interface.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06124: Required query of {0}, found {1}

Cause: TopLink was expecting to find the query queryName, but instead found an incorrect query queryName.

Action: Provide the correct query.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06125: ReadQuery.clearQueryResults() can no longer be called. The call to clearQueryResults now requires that the session be provided. clearQueryResults(session) should be called.

Cause: The ReadQuery method clearQueryResults() was called: this method cannot be called anymore. The call to the clearQueryResults method now requires that the session be provided.

Action: Call the ReadQuery method clearQueryResults(session).
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06126: A query is being executed that uses both conforming and cached query results. These two settings are incompatible.

Cause: A query is being executed that uses both conforming and cached query results. These two settings are incompatible.

Action: Ensure that the query uses either conforming or cached query results.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06127: A reflective call failed on the TopLink class {0}, your environment must be set up to allow Java reflection.

Cause: A reflective call failed on the TopLink class classNAME.

Action: Set up your environment to allow Java reflection
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06128: Batch Reading is not supported on Queries using custom Calls.

Cause: Attempt to use batch reading on a query using a custom call: batch reading is not supported on queries using custom calls.

Action: Do not use batch reading on queries using custom calls.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-06129: Refreshing is not possible if the query does not go to the database.

Cause: Attempt to refreshing the query that does not go to the database. This is not possible.

Action: Avoid refreshing queries that do not go to the database.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-07001: You must login to the ServerSession before acquiring ClientSessions.

Cause: Attempt to allocate client sessions before logging in to the server.

Action: Ensure you have called login method on your server session or database session. This error also appears in multi-threaded environments as a result of concurrency issues. Check that all your threads are synchronized.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07002: The pool named [{0}] does not exist.

Cause: The pool name used while acquiring client session from the server session does not exist.

Action: Verify the pool name given while acquiring client session and all the existing pools on the server session.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07003: Max size must be greater than min size.

Cause: The maximum number of connections in a connection pool is less than the minimum number of connections. The connection pool size must be greater than the minimum number of connections.

Action: Check addConnectionPool(String poolName, JDBCLogin login, int minNumberOfConnections, int maxNumberOfConnections) method on the server session.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07004: Pools must be configured before login.

Cause: Attempt to add connection pools after logging in to the server session: pools must all be added before login on the server session has been done. Once logged in, you cannot add pools.

Action: Check addConnectionPool(String poolName, JDBCLogin login, int minNumberOfConnections, int maxNumberOfConnections) on server session. This method should be called before logging in on the server session.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07008: The Java type [{0}] is not a valid database type.

Cause: The Java type javaClass is not a valid database type. The Java type of the field to be written to the database has no corresponding type on the database.

Action: Check the table or stored procedure definition.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07009: Missing descriptor for [{0}]. Verify that the descriptor has been properly registered with the Session.

Cause: The descriptor className is not found in the session.

Action: Ensure that the related descriptor to the class was properly registered with the session.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07010: Start index is out of range.

Cause: This is a TopLink development exception and you should never encounter this problem. It happens when a copy of a vector is created with a start and end index.

Action: Report this problem to Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07011: Stop index is out of range.

Cause: This is a TopLink development exception and you should never encounter this problem. It happens when a copy of a vector is created with a start and end index.

Action: Report this problem to Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07012: Fatal error occurred.

Cause: This is a TopLink development exception and you should never encounter this problem. It happens when test cases are executed.

Action: Report this problem to Oracle Support Services. This error commonly occurs if you attempt to call the commit method on an invalid (or previously committed) unit of work. If cannotCommitUOWAgain method of ValidationException appears in the stack trace, verify that the commit method was called on valid UnitOfWork instances.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07013: You are using the deprecated SessionManager API and no TOPLink.properties file could be found in your classpath. No sessions could be read in from file.

Cause: The toplink.properties file cannot be found on the system classpath.

Action: Ensure that there is a toplink.properties file located on the system classpath.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07017: Child descriptors do not have an identity map, they share their parent''s

Cause: An identity map is added to the child descriptor. A child descriptor shares its parent's identity map.

Action: Check the child descriptor and remove the identity map from it.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07018: File error.

Cause: You should never encounter this problem. It happens when test cases are executed.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07023: Incorrect login instance provided. A DatabaseLogin must be provided.

Cause: The login instance provided to the login method is incorrect. A JDBCLogin must be provided.

Action: Use a JDBCLogin.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07024: Invalid merge policy.

Cause: This is a TopLink development exception and you should never encounter it.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07025: The only valid keys for DatabaseRows are Strings and DatabaseFields.

Cause: The key on the database row is not either of type String or of type DatabaseField.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07027: The sequence named [{0}] is setup incorrectly. Its increment does not match its pre-allocation size.

Cause: The sequence sequenceName is set up incorrectly: increment does not match preallocation size.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07028: writeObject() is not allowed within a UnitOfWork.

Cause: Attempt to use writeObject() method in a UnitOfWork.

Action: Ensure that a writeObject() method is not in the UnitOfWork.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07030: You cannot set read pool size after login.

Cause: Attempt to set read pool size after the server session has already been logged in.

Action: Set the pool size before login.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07031: You cannot add descriptors to a SessionBroker.

Cause: Attempt to add a descriptor directly to a session broker.

Action: Descriptors are added to the sessions contained in the session broker.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07032: There is no session registered for the class [{0}].

Cause: The descriptor related to the domain class domainClass was not found in any of the sessions registered in the session broker.

Action: Check the sessions.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07033: There is no session registered with the name [{0}].

Cause: A session sessionName is not registered in the session broker.

Action: Check the session broker.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07038: Error while logging message to Session log.

Cause: Error while logging message to session's log.

Action: Check the internal exception.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07039: Cannot remove from the set of read-only classes in a nested UnitOfWork. {0}A nested UnitOfWork''s set of read-only classes must be equal to or a superset of its parent''s set of read-only classes.

Cause: Attempt to remove from the set of read-only classes in a nested unit of work. A nested unit of work's set of read-only classes must be equal to or be a superset of its parent's set of read-only classes.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07040: Cannot change the set of read-only classes in a UnitOfWork after that UnitOfWork has been used. {0}Changes to the read-only set must be made when acquiring the UnitOfWork or immediately after.

Cause: Attempt to change the set of read-only classes in a unit of work after that unit of work has been used. Changes to the read-only set must be made when acquiring the unit of work or immediately after.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07042: Database platform class [{0}] not found.

Cause: The platform class className was not found and a reflection exception is raised.

Action: Check the internal exception.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07043: [{0}] does not have any tables to create on the database.

Cause: A project project does not have any tables to create on the database.

Action: Validate the project and tables you are attempting to create.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07044: The container class specified [{0}] cannot be used as a container because it does not implement Collection or Map.

Cause: Illegal attempt to use the class className as the container-this class does not implement the Collection or Map interfaces.

Action: Implement either the Collection or Map interfaces in the container class.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07047: The container specified [{0}] does not require keys. You tried to use the method [{1}].

Cause: Invalid Map class was specified for the container policy. The container specified (of Class aPolicyContainerClass) does not require keys. You tried to use the method methodName.

Action: Use map class that implements the Map interface.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07048: Neither the instance method or field named [{0}] exists for the item class [{1}], and therefore cannot be used to create a key for the Map.

Cause: The key method on the map container policy is not defined. The instance method methodName does not exist in the reference class className and therefore cannot be used to create a key in a map. A map container policy represents the way to handle an indexed collection of objects. Usually the key is the primary key of the objects stored, so the policy needs to know the name of the primary key getter method in order to extract it from each object using reflection. For instance, a user might call policy.setKeyMethodName("getId").

Action: Check the second parameter of the useMapClass method of DatabaseQuery.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07051: Missing attribute [{1}] for descriptor [{0}], called from [{2}]

Cause: Missing attribute attributeName for descriptor descriptor called from methodName. This is a TopLink development exception, and you should never encounter it.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07052: An attempt was made to use [{0}] (with the key method [{1}]) as a container for a DirectCollectionMapping [{0}]. The useMapClass() method cannot be used, only the useCollectionClass() API is supported for DirectCollectionMappings.

Cause: The method useMapClass was called on a DirectCollectionMapping. It is invalid to call the useMapClass method on a DirectCollectionMapping. TopLink cannot instantiate Java attributes mapped using a DirectCollectionMapping with a map. The useMapClass method is supported for OneToManyMapping and ManyToManyMapping. The Java 2 Collection interface is supported using the useCollectionClass method.

Action: Use the useCollectionClass method. Do not call the useMapClass method on DirectCollectionMapping.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07053: release() attempted on a Session that is not a ClientSession. Only ClientSessions may be released.

Cause: TopLink is unable to release a session that is not a client session. Only client sessions can be released.

Action: Modify the code to ensure the client session is not released.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07054: acquire() attempted on a Session that is not a ServerSession. ClientSessions may only be acquired from ServerSessions.

Cause: TopLink is unable to acquire a session that is not a client session. Client sessions can be acquired only from server sessions.

Action: Modify the code to ensure an acquire session is attempted only from server sessions.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07055: Optimistic Locking is not supported with stored procedure generation.

Cause: Attempt to use optimistic locking with stored procedure generation. This is not supported.

Action: Do not use optimistic locking with stored procedure generation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07056: The wrong object was registered into the UnitOfWork. The object [{0}] should be the object from the parent cache [{1}].

Cause: The wrong object was registered into the unit of work. It should be the object from the parent cache.

Action: Ensure that the object is from the parent cache.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07058: Invalid Connector [{0}] (must be of type DefaultConnector).

Cause: The connector selected is invalid and must be of type DefaultConnector.

Action: Ensure that the connector is of type DefaultConnector.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07059: Invalid data source name [{0}].

Cause: Invalid data source name dsName.

Action: Verify the data source name.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07060: Cannot acquire data source [{0}].

Cause: TopLink is unable to acquire the data source with the name dsName, or an error has occurred in setting up the data source.

Action: Verify the data source name. Check the nested SQL exception to determine the cause of the error. Typical problems include:The connection pool was not configured in your config.xml file.The driver is not on the classpath.The user or password is incorrect.The database server URL or driver name is not properly specified.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07061: Exception occurred within JTS.

Cause: An exception occurred within the Java Transaction Service (JTS).

Action: Examine the JTS exception and see the JTS documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07062: Field-level locking is not supported outside of a UnitOfWork. To use field-level locking, a UnitOfWork must be used for ALL writing.

Cause: Attempt to use FieldLevelLocking outside a unit of work. This is not supported. In order to use field-level locking, a unit of work must be used for all write operations.

Action: Use a unit of work for writing.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07063: Exception occurred within EJB container.

Cause: An exception occurred within the EJB container.

Action: Examine the EJB exception and see the JTS documentation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07064: Exception occurred in reflective EJB primary key extraction. Please ensure your primary key object is defined correctly. {2}Key: [{0}] {2}Bean: [{1}]

Cause: An exception occurred in the reflective enterprise bean primary key extraction.

Action: Ensure that your primary key object is defined correctly.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07065: The remote class for the bean cannot be loaded or found. Ensure that the correct class loader is set. {2}Bean: [{0}] {2}Remote Class: [{1}]

Cause: The remote class for the bean cannot be loaded or found.

Action: Ensure that the correct class loader is set properly.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07066: Cannot create or remove beans unless a JTS transaction is present. {1}Bean: [{0}]

Cause: Attempt to create or remove an enterprise bean outside of a transaction: TopLink is unable to create or remove enterprise beans unless a JTS transaction is present, bean=bean.

Action: Ensure that the JTS transaction is present.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07068: The project class [{0}] was not found for the project [{1}] using the default class loader.

Cause: The platform class platformName was not found for the project projectName using the default class loader.

Action: Validate the project and platform.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07069: An exception occurred looking up or inovking the project amendment method, ''{0}'' on the class ''{1}''.

Cause: An exception occurred while looking up or invoking the project amendment method amendmentMethod on the class amendmentClass.

Action: Validate the amendment method and class.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07070: A TOPLink.properties resource bundle must be located on the CLASSPATH in a TopLink directory.

Cause: Attempt to load toplink.properties resource bundle outside the classpath: the resource bundle must be located on the classpath in a TopLink directory.

Action: Validate the classpath and the location of the TopLink resource bundle.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07071: Cannot use input/output parameters without using binding.

Cause: Attempt to use input or output parameters without using binding.

Action: Use binding on the StoredProcedureCall.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07072: The database platform class [{0}] was not found for the project [{1}] using the default class loader.

Cause: SessionManager failed to load the class identified by the value associated with properties platform-class or external-transaction-controller-class during initialization when it loads the TopLink session common properties from the TopLink global properties file (sessions.xml for non-EJB applications, or toplink-ejb-jar.xml for EJB applications).

Action: Ensure that your TopLink global properties file is correctly configured. Pay particular attention to the platform-class and external-transaction-controller-class properties.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07073: The Oracle object type with type name [{0}] is not defined.

Cause: The Oracle object type with type name typeName is not defined.

Action: Ensure that the Oracle object type is defined.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07074: The Oracle object type name [{0}] is not defined.

Cause: The Oracle object type typeName is not defined.

Action: Ensure that the Oracle object type is defined.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07075: Maximum size is not defined for the Oracle VARRAY type [{0}]. A maximum size must be defined.

Cause: The Oracle VARRAY type typeName maximum size is not defined.

Action: Verify the maximum size for the Oracle VARRAY.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07076: When generating the project class, the project''s descriptors must not be initialized. {1}Descriptor: [{0}]

Cause: Attempt to generate a project class while descriptors have already been initialized: when generating the project class, the descriptors must not be initialized.

Action: Ensure that the descriptors are not initialized before generating the project class.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07077: The home interface [{0}], specified during creation of the BMPWrapperPolicy, does not contain a correct findByPrimaryKey() method. A findByPrimaryKey() method must exist that takes the PrimaryKey class for this bean.

Cause: The home interface toString method specified during creation of BMPWrapperPolicy does not contain a correct findByPrimaryKey method. A findByPrimaryKey method must exist that takes the PrimaryKey class for this bean.

Action: Ensure that a findByPrimaryKey method exists and is correct.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07078: The "sessionName" [{0}], specified on the deployment descriptor for [{1}], does not match any session specified in the TopLink properties file.

Cause: The sessionName specified on the deployment descriptor does not match any session specified in the toplink.properties file.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07079: The descriptor for [{0}] was not found in the session [{1}]. Check the project being used for this session.

Cause: The descriptor was not found in the session.

Action: Check the project being used for this session.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07080: A FinderException was thrown when trying to load [{0}], of class [{1}], with primary key [{2}].

Cause: A FinderException is raised when attempting to load an object from the class with the primary key.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07081: The aggregate object [{0}] cannot be directly registered in the UnitOfWork. It must be associated with the source (owner) object.

Cause: Attempt to register an aggregate object directly in the unit of work. This is not supported. The aggregate object must be associated with the source (owner) object.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07082: The TopLink properties file [{0}] specified multiple project files for the server named [{1}]. Please specify one of [projectClass], [projectFile], or [xmlProjectFile].

Cause: The toplink.properties file specified multiple project files for the server. Only one project file can be specified.

Action: Specify either projectClass, projectFile, or xmlProjectFile.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07083: The TopLink properties file [{0}] did not include any information on the TopLink project to use for the server named [{1}]. Please specify one of [projectClass], [projectFile], or [xmlProjectFile].

Cause: The toplink.properties file does not include any information on the TopLink project to use for the server. One project file must be specified.

Action: Specify either projectClass, projectFile, or xmlProjectFile.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07084: The file [{0}] is not a valid type for reading. ProjectReader must be given the deployed XML Project file.

Cause: The specified file is not a valid type for reading. ProjectReader must be given the deployed XML project file.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07085: At least one sub session need to be defined in the TopLink session broker {0}

Cause: TopLink is unable to create an instance of the external transaction controller specified in the properties file.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07086: The session type ''{0}'' of the session name ''{1}'' was not defined properly.

Cause: The session manager cannot load the class corresponding to the session's type class name.

Action: Ensure that the class name of the session's type is fully qualified in the sessions.xml file or toplink.properties file.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07087: The session type ''{0}'' was not found for the ''{1}'' using default class loader.

Cause: The session manager cannot load the class corresponding to the session's type class name.

Action: Ensure that the class name of the session's type is fully qualified in the sessions.xml file or toplink.properties file.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07088: Cannot create an instance of the external transaction controller [{0}], specified in the properties file.

Cause: The session manager cannot load the class corresponding to the external transaction controller's class name.

Action: Ensure that the class name of the external transaction controller is valid and fully qualified in the sessions.xml file or toplink.properties file.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07089: An exception occurred looking up or invoking the session amendment method [{0}] on the class [{1}] with parameters [{2}].

Cause: The session manager cannot load the class corresponding to the amendment class name, or it cannot load the method on the amendment class corresponding to the amendment method name.

Action: Ensure that the class name of the amendment class is fully qualified, and the amendment method exists in the amendment class in the sessions.xml file or toplink.properties file.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07091: Cannot set listener classes!

Cause: TopLink is unable to create the listener class that implements SessionEventListener for the internal use of SessionXMLProject.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07092: Cannot add a query whose types conflict with an existing query. Query To Be Added: [{0}] is named: [{1}] with arguments [{2}].The existing conflicting query: [{3}] is named: [{4}] with arguments: [{5}].

Cause: TopLink has detected a conflict between a custom query with the same name and arguments to a session.

Action: Ensure that no query is added to the session more than once or change the query name so that the query can be distinguished from others.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07093: In the query named [{0}], the class [{2}] for query argument named [{1}] cannot be found. Please include the missing class on your classpath.

Cause: TopLink is unable to create an instance of the query argument type.

Action: Ensure that the argument type is a fully qualified class name and the argument class is included in the classpath environment.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07095: The sessions.xml resource [{0}] was not found on the resource path. Check that the resource name/path and classloader passed to the SessionManager.getSession are correct. The sessions.xml should be included in the root of the application's deployed jar, if the sessions.xml is deployed in a sub-directory in the application's jar ensure that the correct resource path using "/" not "\" is used.

Cause: The sessions.xml or toplink.properties file cannot be loaded.

Action: Ensure that the path to either of the files exists on the classpath environment. The sessions.xml should be included in the root of the deployed JAR file. When using a WAR file, the sessions.xml file should be located in the WEB-INF/classes directory. When using EJB 3.0, TopLink automatically loads the ejb3-toplink-sessions.xml file.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07096: Cannot use commit() method to commit UnitOfWork again.

Cause: TopLink cannot invoke commit method on an inactive unit of work that was committed or released.

Action: Ensure you invoke commit method on a new unit of work or invoke commitAndResume method so that the unit of work can be reused. For more information about the commitAndResume method, see Oracle TopLink API Reference.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07097: Operation not supported: [{0}].

Cause: TopLink cannot invoke an unsupported operation on an object.

Action: Do not use the operation indicated in the stack trace.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07099: The deployment project xml resource [{0}] was not found on the resource path. Check that the resource name/path and classloader passed to the XMLProjectReader are correct. The project xml should be included in the root of the application's deployed jar, if the project xml is deployed in a sub-directory in the application's jar ensure that the correct resource path using "/" not "\" is used.

Cause: The file name specified for the XML-based project is incorrect.

Action: Verify the name and location of the file.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07101: No "meta-inf/toplink-ejb-jar.xml" could be found in your classpath. The CMP session could not be read in from file.

Cause: The toplink-ejb-jar.xml file was not found.

Action: Ensure that the file is on your classpath.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07102: Encountered a null value for a cache key while attempting to remove{2}an object from the identity map: [{0}]{2}containing an object of class: [{1}] (or a class in this hierarchy){2}The most likely cause of this situation is that the object has already been garbage-{2}collected and therefore does not exist within the identity map.{2}Please consider using an alternative identity map to prevent this situation.{2}For more details regarding identity maps, please refer to the TopLink documentation.

Cause: Encountered a null value for a cache key while attempting to remove an object from the identity map. The most likely cause of this situation is that the object has already been garbage-collected and therefore does not exist within the identity map.

Action: Ignore. The removeFromIdentityMap method of the Session is intended to allow garbage collection, which has already been done.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07103: A null reference was encountered while attempting to invoke{1}method: [{0}] on an object which uses proxy indirection.{1}Please check that this object is not null before invoking its methods.

Cause: A null reference was encountered while attempting to invoke a method on an object that uses proxy indirection.

Action: Check that this object is not null before invoking its methods.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07104: Sequencing login should not use External Transaction Controller.

Cause: A separate connection(s) for sequencing was requested, but the sequencing login uses the external transaction controller.

Action: Either provide a sequencing login that does not use an external transaction controller or do not use separate connection(s) for sequencing.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07105: Error encountered converting encryptiong class: [{0}]

Cause: Error encountered while converting encryption class.

Action: Ensure the encryption class name is correctly specified in the sessions.xml file and that the encryption class specified is available on the classpath. A common reason for this exception is the usage of JDK 1.3 and earlier versions. The TopLink JCE encryption mechanism requires JDK 1.4 and later (or JDK 1.3 configured with the JCE plug-in) to function properly.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07106: Error encountered during string encryption.

Cause: Error encountered during password string encryption.

Action: An error is raised while trying to encrypt the password string. A common reason for this exception is the usage of JDK 1.3 and earlier versions. The TopLink JCE encryption mechanism requires JDK 1.4 and later (or JDK 1.3 configured with the JCE plug-in) to function properly.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07107: Error encountered during string decryption.

Cause: Error encountered during password string decryption.

Action: An exception was raised while trying to decrypt the password string. A common reason for this exception is the usage of JDK 1.3 and earlier versions. The TopLink JCE encryption mechanism requires JDK 1.4 and later (or JDK 1.3 configured with the JCE plug-in) to function properly.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07108: This operation is not supported for non-relational platforms.

Cause: Attempt to use an operation that is not supported for nonrelational platforms.

Action: Do not use this operation on the current platform, or use a relational database platform.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07109: The login in the project used to create the session is null, it must be a valid login.

Cause: The login in the project used to create the session is null meaning no login was specified for the TopLink project. The login used for the project must be a valid login.

Action: Add login information using TopLink Workbench or using Java code.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07110: At present HistoricalSession only works with Oracle 9R2 or later databases, as it uses Oracle's Flashback feature.

Cause: Attempt to use a HistoricalSession with a non-Oracle database. At present, HistoricalSession only works with Oracle databases that have a Flashback feature (Oracle database 9.2.0.4 or later).Generic history support (see oracle.toplink.history.HistoryPolicy) works for any database. If a HistoryPolicy is incorrectly set, TopLink may be defaulting to using flashback instead. An AsOfSCNClause is implicitly flashback only.

Action: Ensure that the HistoryPolicy is set correctly.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07111: You may not acquire a HistoricalSession from a UnitOfWork, another HistoricalSession, a ServerSession, or a ServerSessionBroker. You may acquire one from a regular session, a ClientSession, or a ClientSessionBroker.

Cause: Invalid attempt to acquire a HistoricalSession: you may not acquire a HistoricalSession from a unit of work, another HistoricalSession, a ServerSession, or a ServerSessionBroker. You may acquire a HistoricalSession from a regular session, a ClientSession, or a ClientSessionBroker.

Action: To recover objects, read the objects in both a HistoricalSession and UnitOfWork, and call mergeCloneWithReferences(historicalObject) method on the UnitOfWork.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07112: You have specified that Toplink use the feature : {0}, but this feature is not available in the currently running JDK version :{1}.

Cause: Attempt to use a TopLink feature that is not available in the current JDK version.

Action: You must use the version of the JDK that supports this feature.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07113: {0} does not support call with returning.

Cause: Attempt to use an unsupported call with returning for a platform.

Action: Set stored procedures with output parameters in setInsertQuery, setInsertCall, setUpdateQuery, or setUpdateCall methods of the DescriptorQueryManager.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07114: Isolated Data is not currently supported within a Client Session Broker. Session named {0} contains descriptors representing isolated data.

Cause: Attempt to use isolated data within a ClientSessionBroker: isolated data is not currently supported within a ClientSessionBroker. Session contains descriptors representing isolated data.

Action: Ensure that isolated data is not used.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07115: A Exclusive Connection cannot be used for ClientSession reads without isolated data. Please update the ConnectionPolicy, used, to remove ExclusiveConnection configuration or the project to set certain data to be exclusive.

Cause: Attempt to use ExclusiveConnection for ClientSession reads without isolated data. This is not supported.

Action: You must update the ConnectionPolicy used to remove ExclusiveConnection configuration, or the project to set certain data to be exclusive.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07116: Invalid arguments are used. Please refer to public API of the calling method and use valid values for the arguments.

Cause: Invalid arguments are used in the method.

Action: Refer to the public API of the calling method and use valid values for the arguments.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07117: There is an attempt to use more than one cursor in SQLCall {0}

Cause: Attempt to use more than one cursor in a SQLCall.

Action: TopLink currently supports only one cursor per call.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07118: setCustomSQLArgumentType method was called on SQLCall {0}, but this call doesn't use custom SQL

Cause: The setCustomSQLArgumentType method was invoked on SQLCall, but this method does not use custom SQL.

Action: Don't call this method on SQLCall that does not use custom SQL.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07119: Unprepared SQLCall {0} attempted translation

Cause: Unprepared SQLCall attempted translation.

Action: SQLCall must be prepared before translation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07120: Parameter {0} in SQLCall {1} cannot be used as a cursor, because it is has parameter type other than OUT

Cause: Attempt to use parameter in SQLCall as a cursor, but this parameter is of type other than OUT.

Action: Ensure that the parameter used as a cursor has parameter type OUT.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07121: {0} does not support stored functions

Cause: Attempt to use stored functions for a platform that does not support stored functions.

Action: Do not define stored functions on this platform.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07122: The exclusive connection associated with the session is unavailable for the query on {0}

Cause: The exclusive connection associated with the session is unavailable for the query on the object.Isolated objects with indirection read through an ExclusiveIsolatedClientSession must not have indirection triggered after the ExclusiveIsolatedClientSession has been released.

Action: Reread the objects through the current ExclusiveIsolatedClientSession.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07123: A successful writeChanges() has been called on this UnitOfWork. As the commit process has been started but not yet finalized, the only supported operations now are commit, commitAndResume, release, any non-object level query or SQLCall execution. The operation {0} is not allowed at this time.

Cause: Attempt to perform an operation that is not allowed at this time: a successful writeChanges operation has been called on this UnitOfWork. As the commit process has been started, but not yet finalized, the only supported operations now are commit, commitAndResume, release, any nonobject level query, or SQLCall execution.

Action: Execute one of the supported operations to continue.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-07124: An unsuccessful writeChanges() has been called on this UnitOfWork. Given the danger that partial changes have been written to the datastore but not rolled back (if inside external transaction), the only supported operations now are release, global transaction rollback, any non-object level query or SQLCall execution. The operation {0} was attempted.

Cause: Attempt to perform an operation that is not allowed at this time: an unsuccessful writeChanges operation has been called on this UnitOfWork. Given the possibility that partial changes have been written to the data store but not rolled back (if inside external transaction), the only supported operations now are release, global transaction rollback, any nonobject level query or SQLCall execution.

Action: Determine the cause of the original failure and retry in a new UnitOfWork.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-07125: Once the UnitOfWork has been committed and/or released, no further operation should be performed on it. The operation {0} was attempted on it.

Cause: Attempt to perform an operation on an inactive unit of work: once the UnitOfWork has been committed and/or released, no further operation should be performed on it.

Action: Acquire a new UnitOfWork, or use the commitAndResume method instead of commit method in the future.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-07126: writeChanges cannot be called on a NestedUnitOfWork. A nested UnitOfWork never writes changes directly to the datastore, only the parent UnitOfWork does.

Cause: Attempt to call a writeChanges method on a NestedUnitOfWork. This is not supported: a nested UnitOfWork never writes changes directly to the data store, only the parent UnitOfWork does.

Action: Call the commit method instead, and then the writeChanges method on the parent UnitOfWork.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-07127: You can only writes changes to the datastore once, just as you can only call commit once.

Cause: Attempt to write changes to the data store more than once: you can only write changes to the data store once.

Action: You must either roll back the transaction, or call the commit method on this UnitOfWork and start a new transaction.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-07128: Session [{0}] is already logged in.

Cause: Attempt to log in to a session more than once.

Action: Do not try to login again.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07129: The method''s arguments cannot have null value.

Cause: Attempt to use null values for arguments in a method that cannot have null values.

Action: Ensure that the method's arguments do not have a null value.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07130: Nested unit of work is not supported for attribute change tracking.

Cause: Attempt to use a nested UnitOfWork with attribute change tracking. This is not supported.

Action: Do not use a nested UnitOfWork with attribute change tracking.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07131: {0} is the wrong type. The collection change event type has to be add or remove.

Cause: The collection change event is of the wrong type. The collection change event type has to be added or removed.

Action: Ensure that the collection change event type used is defined in CollectionChangeEvent.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-07132: {0} is the wrong event class. Only PropertyChangeEvent and CollectionChangeEvent are supported.

Cause: Wrong event class. Only PropertyChangeEvent and CollectionChangeEvent classes are supported.

Action: Ensure that the event class is either PropertyChangeEvent or CollectionChangeEvent.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-07133: Old commit is not supported for attribute change tracking.

Cause: Attempt to use old commit for attribute change tracking. This is not supported.

Action: Do not try to use attribute change tracking with an old commit.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07134: Server platform {0} is read only after login.

Cause: Attempt to make changes to the server platform after login: the server platform is read-only after login.

Action: Changes to the server platform must be made before login. You must either:CMP application: define a class that implements oracle.toplink.ejb.cmp.DeploymentCustomization, and customize its public String beforeLoginCustomization(Session session) method to change your server platform. Consult the documentation for defining a customization class in your orion-ejb-jar.xml file.Non-CMP/POJO application: define a subclass of oracle.toplink.sessions.SessionEventAdapter, and override the public void preLogin(SessionEvent event) method to change your server platform. The session is contained in the event. Consult the documentation for sessions.xml and using SessionEventAdapter.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07135: You cannot commit and resume a unit of work containing any modify all queries

Cause: Attempt to commit and resume a UnitOfWork containing an UpdateAllQuery. This is not supported.

Action: You must either commit and continue in a new UnitOfWork, or do not use UpdateAllQuery.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-07136: Nested unit of work is not supported for a modify all query

Cause: Attempt to use a nested UnitOfWork for an UpdateAll query. This is not supported.

Action: Do not use a nested UnitOfWork for an UpdateAllQuery.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-07137: The object is partially fetched (using fecth group), the unfetched attribute ({0}) is not editable.

Cause: Attempt to edit an unfetched attribute: the object is partially fetched (using fetch group), the unfetched attribute is not editable.

Action: Do not edit the unfetched attribute, or explicitly fetch the attribute before editing it.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-07139: Modify all queries cannot be issued within a unit of work containing other write operations.

Cause: Attempt to issue an UpdateAll query within a UnitOfWork containing other write operations.

Action: Do not use UpdateAllQuery within a UnitOfWork containing other write operations.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-07140: Sequence type {0} doesn''t have method {1}.

Cause: Sequence type does not have the method.

Action: Do not call this method on this type of sequence.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07144: {0}: platform {1} doesn''t support {2}.

Cause: Platform does not support sequence.

Action: Do not use this sequence type on this platform.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07145: {2} attempts to connect to sequence {0}, but it is already connected to {1}. Likely the two sessions share the DatasourcePlatform object

Cause: Two attempts have been made to connect to sequence, but the sequence is already connected to a platform. Likely the two sessions share the DatasourcePlatform object.

Action: Ensure that the sequence is used by a single session only.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-07146: QuerySequence {1} doesn''t have select query.

Cause: QuerySequence does not have select query.

Action: Ensure that the sequence has a select query.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07147: Platform {0} cannot create platform default sequence - it doesn''t override createPlatformDefaultSequence method

Cause: Attempt to create platform default sequence by a platform that does not override the createPlatformDefaultSequence method.

Action: You must either override the createPlatformDefaultSequence method on the platform, or explicitly set default sequence by calling setDefaultSequence on DatasourceLogin.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07148: commitAndResume() cannot be used with a JTA/synchronized unit of work.

Cause: Attempt to use commitAndResume() method with a JTA or a synchronized unit of work.

Action: Do not use commitAndResume() with a JTA or a synchronized unit of work.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-07149: The composite primary key attribute [{2}] of type [{4}] on entity class [{0}] should be of the same type as defined on its primary key class [{1}]. That is, it should be of type [{3}].

Cause: Attempt to provide an invalid specification of the composite primary key: the names of the primary key fields or properties in the primary key class PKClassName and those of the entity bean class ClassName must correspond and their types must be the same.

Action: Ensure that the names of the primary key fields or properties in the primary key class PKClassName and those of the entity bean class ClassName correspond, and their types are the same.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07150: Invalid composite primary key specification. The names of the primary key fields or properties in the primary key class [{1}] and those of the entity bean class [{0}] must correspond and their types must be the same. Also, ensure that you have specified id elements for the corresponding attributes in XML and/or an @Id on the corresponding fields or properties of the entity class.

Cause: Attempt to specify an invalid LAZY fetch type on an attribute attributeName within entity class ClassName.

Action: Provide the fetch type other than LAZY on an attribute attributeName within entity class ClassName.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07151: The type [{1}] for the attribute [{0}] on the entity class [{2}] is not a valid type for an enumerated mapping. The attribute must be defined as a Java enum.

Cause: An invalid EJB 3.0 annotation annotation has been specified in the entity class ClassName on accessor method methodName. It is not supported.

Action: Specify a valid annotation on this accessor method.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07152: Table per class inheritance is not supported. Entity class [{0}].

Cause: Table per class inheritance is not supported. Entity class ClassName.

Action: Use different approach.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07153: Mapping annotations cannot be applied to fields or properties that are transient or have a @Transient specified. [{0}] is in violation of this restriction.

Cause: The descriptor named query query already exists. Named query names must be unique.

Action: Provide a unique name for the query.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07154: The attribute [{3}] in entity class [{2}] has a mappedBy value of [{1}] which does not exist in its owning entity class [{0}]. If the owning entity class is a @MappedSuperclass, this is invalid, and your attribute should reference the correct subclass.

Cause: An annotation @AssociationTable was not found on either the owning mapping class ClassName, or nonowning mapping class DifferentClassName for the @ManyToMany annotation.

Action: Ensure that the annotation @AssociationTable exists.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07155: The type [{1}] for the attribute [{0}] on the entity class [{2}] is not a valid type for a serialized mapping. The attribute type must implement the Serializable interface.

Cause: An annotation @AttributeOverride columns was not specified on a mapping mapping from entity class ClassName.

Action: Specify this annotation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07156: Unable to find the class named [{0}]. Ensure the class name/path is correct and available to the classloader.

Cause: TopLink was unable to find the class ClassName. Ensure the class name/path is correct and available to the class loader.

Action: Ensure the class name and/or path is correct and available to the class loader.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07157: Entity class [{0}] must use a @JoinColumn instead of @Column to map its relationship attribute [{1}].

Cause: Attempt to use an invalid@Column annotation by the entity class ClassName to map its relationship attribute attribute.

Action: Ensure the entity class ClassName uses a @JoinColumn attribute instead of a @Column attribute to map its relationship attribute attributeName.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07158: Error encountered when building the @NamedQuery [{1}] from entity class [{0}].

Cause: Error encountered when building the @NamedQuery annotation from entity class ClassName.

Action: Ensure the correctness of the annotation specification.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07159: The map key [{0}] on the entity class [{1}] could not be found for the mapping [{2}].

Cause: Invalid use of an unnamed @NamedQuery annotation with the query string string by an entity class ClassName .

Action: Specify a name for @NamedQuery.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07160: @OneToMany for attribute name [{1}] in entity class [{0}] should not have @JoinColumn(s) specified. In the case where the @OneToMany is not mapped by another entity (that is, it is the owning side and is uni-directional), it should specify (optional through defaulting) a @JoinTable.

Cause: @OneToMany annotation for attribute attributeName in entity class ClassName has both an @AssocationTable and @JoinColumn(s) annotations specified.

Action: Specify one annotation only: @AssocationTable or @JoinColumn(s).
Level: 1

Type: ERROR

Impact: Configuration

TOP-07161: Entity class [{0}] has no primary key specified. It should define either an @Id, @EmbeddedId or an @IdClass. If you have defined PK using any of these annotations then please make sure that you do not have mixed access-type (both fields and properties annotated) in your entity class hierarchy.

Cause: Primary key annotation is not specified for the entity class ClassName.

Action: Define either an @Id, @EmbeddedId or an @IdClass annotation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07162: Entity class [{0}] has multiple @EmbeddedId's specified (on attributes [{1}] and [{2}]). Only one @EmbeddedId can be specified per entity.

Cause: Multiple @EmbeddedId annotations are specified (on attributeName and differentAttributeName) for entity class ClassName.

Action: Specify only one @EmbeddedId annotation for this entity.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07163: Entity class [{0}] has both an @EmbdeddedId (on attribute [{1}]) and an @Id (on attribute [{2}]. Both id types cannot be specified on the same entity.

Cause: Entity class ClassName has both an @EmbdeddedId (on attribute attributeName) and an @Id (on attribute differentAttributeName).

Action: Specify only one ID type on this entity: either @EmbdeddedId or @Id.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07164: The type [{1}] for the attribute [{0}] on the entity class [{2}] is not a valid type for a lob mapping. For a lob of type BLOB, the attribute must be defined as a java.sql.Blob, byte[], Byte[] or a Serializable type. For a lob of type CLOB, the attribute must be defined as a java.sql.Clob, char[], Character[] or String type.

Cause: Attribute attributeName in an entity class ClassName has an invalid type for a @Lob annotation of type BLOB.

Action: Define this attribute as a java.sql.Blob, byte[], Byte[] or a Serializable type.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07165: The type [{1}] for the attribute [{0}] on the entity class [{2}] is not a valid type for a temporal mapping. The attribute must be defined as java.util.Date or java.util.Calendar.

Cause: Attribute attributeName in entity class ClassName has an invalid type for a @Lob annotation of type CLOB.

Action: Define this attribute as a java.sql.Clob, char[], Character[] or String type.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07166: A table generator that uses the reserved name [{0}] for its 'name' has been found in [{1}]. It cannot use this name since it is reserved for defaulting a sequence generator's 'sequence name'.

Cause: Conflict between annotations @Annotation and @DifferentAnnotation.

Action: Ensure that these two annotations are not conflicting.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07167: A sequence generator that uses the reserved name [{0}] for its 'sequence name' has been found in [{1}]. It cannot use this name since it is reserved for defaulting a table generator's 'name'.

Cause: Attempt to use a reserved annotation name AnnotationName by an entity class ClassName: cannot use this name, because it is reserved for name.

Action: Specify a different name for this annotation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07168: The attribute [{0}] of type [{1}] on the entity class [{2}] is not valid for a version property. The following types are supported: int, Integer, short, Short, long, Long, Timestamp.

Cause: Attempt to specify a generator with type Type by an annotation @Annotation.

Action: Ensure that this annotation specifies a generator of a different type.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07169: Class [{0}] has two @GeneratedValues: for fields [{1}] and [{2}]. Only one is allowed.

Cause: The callback method methodName on the entity listener ListenerClassName has an incorrect signature.

Action: Provide only one parameter of type Object for this method.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07172: Error encountered when instantiating the class [{0}].

Cause: TopLink was unable to instantiate the entity listener using the @EntityListener annotation.

Action: Ensure that the annotation is correctly specified.
Level: 1

Type: ERROR

Impact: Deployment

TOP-07173: A property change event has been fired on a property with name [{1}] in [{0}]. However this property does not exist.

Cause: Attempt to fire a property change event on a nonexisting property propertyName in a change event EventClassName.

Action: Ensure that this property exists.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-07174: The getter method [{1}] on entity class [{0}] does not have a corresponding setter method defined.

Cause: The getter method methodName on an entity class ClassName does not have a corresponding setter method defined.

Action: Define a corresponding setter method.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07175: The mapping [{0}] does not support cascading version optimistic locking.

Cause: Attempt to use the mapping MappingType that does not support cascading version optimistic locking.

Action: Use a different mapping.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07176: The mapping [{0}] does not support cascading version optimistic locking because it has a custom query.

Cause: Attempt to use the mapping MappingType that does not support cascading version optimistic locking. This mapping has a custom query.

Action: Use a different mapping.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07177: The aggregate descriptor [{0}] has privately-owned mappings. Aggregate descriptors do not support cascading version optimistic locking.

Cause: Attempt to use an aggregate descriptor DescriptorName that has privately-owned mappings: aggregate descriptors do not support cascading version optimistic locking.

Action: Use a different descriptor.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07178: OracleOCIProxyConnector requires OracleOCIConnectionPool datasource.

Cause: Attempt to use invalid arguments in an entity callback method methodName on a OracleOCIProxyConnector: it requires the OracleOCIConnectionPool data source.

Action: Provide OracleOCIProxyConnector with the OracleOCIConnectionPool argument.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07179: OracleJDBC10_1_0_2ProxyConnector requires datasource producing OracleConnections.

Cause: Attempt to use invalid arguments in an entity callback method methodName on a OracleJDBC10_1_0_2ProxyConnector.

Action: Provide OracleJDBC10_1_0_2ProxyConnector with data source producing Oracle Connections.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07180: OracleJDBC10_1_0_2ProxyConnector requires Oracle JDBC version 10.1.0.2 or higher so that OracleConnection declares openProxySession method.

Cause: Attempt to use the OracleJDBC10_1_0_2ProxyConnector with Oracle JDBC version 10.1.0.1 or earlier: OracleJDBC10_1_0_2ProxyConnector requires Oracle JDBC version 10.1.0.2 or later.

Action: Provide OracleJDBC10_1_0_2ProxyConnector with Oracle JDBC version 10.1.0.2 or later in order for the OracleConnection to declare the openProxySession method.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07181: OracleJDBC10_1_0_2ProxyConnector requires ''proxytype'' property to be an int converted to String, for instance Integer.toString(OracleConnection.PROXYTYPE_USER_NAME)

Cause: Attempt to use an invalid type for the proxytype property on the OracleJDBC10_1_0_2ProxyConnector: it requires the proxytype property to be an int converted to a String.

Action: On the OracleJDBC10_1_0_2ProxyConnector, provide the proxytype property of type int converted to a String. For example, Integer.toString(OracleConnection.PROXYTYPE_USER_NAME).
Level: 1

Type: ERROR

Impact: Configuration

TOP-07182: EC - Could not find driver class [{0}]

Cause: TopLink could not find the driver class.

Action: Ensure that the driver class exists and is on the classpath.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07183: Error closing persistence.xml file.

Cause: TopLink cannot close persistence.xml file.

Action: If you modified the persistence.xml, ensure that this file is not read-only.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07184: [{0}] system property not specified. It must be set to a class that defines a ''getContainerConfig()'' method.

Cause: The system property propertyName is not specified.

Action: Set this property to a class that defines a getContainerConfig() method.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07185: Cannot find class [{0}] specified in [{1}]

Cause: TopLink cannot find class ClassName.

Action: Ensure that the class exists and is properly specified.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07186: Cannot invoke method [{0}] on class [{1}] specified in [{2}]

Cause: TopLink cannot invoke method methodName on configuration class ClassName.

Action: Ensure that this method exists in this class.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07187: [{0}] should define a public static method [{1}] that has no parameters and returns Colleciton

Cause: Class ClassName does not define a public static method methodName.

Action: In the class ClassName, define a public static method methodName that has no parameters and returns a Collection.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07188: Non-null class list is required.

Cause: Class list is null.

Action: Provide a non-null class list.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07189: Cannot create temp classloader from current loader: [{0}]

Cause: TopLink cannot create a temporary class loader from the current loader ClassLoaderName.

Action: Ensure the validity of the current class loader.
Level: 1

Type: ERROR

Impact: Deployment

TOP-07190: [{0}] failed

Cause: Failure in the execution of the methodName method.

Action: Ensure the correctness of the method.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-07191: The entity class [{0}] was not found using class loader [{1}].

Cause: An entity class ClassName was not found using class loader ClassLoaderName.

Action: Ensure that the entity class exists and is on the classpath.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-07192: ClassFileTransformer [{0}] throws an exception when performing transform() on class [{1}].

Cause: Class file transformer TransformerName threw an exception when performing transform() method on class ClassName.

Action: Ensure the correctness of the transform() method. Check the internal exception for details on the root cause of this exception
Level: 1

Type: ERROR

Impact: Programmatic

TOP-07193: Jar files in persistence XML are not supported in this version of TopLink.

Cause: Attempt to use JAR files in the persistence.xml file: JAR files are not supported in this version of Toplink.

Action: Do not use JAR files.
Level: 1

Type: ERROR

Impact: Deployment

TOP-07194: Could not bind: [{0}] to: [{1}].

Cause: Attempt to use an unsupported method setFlushMode().

Action: Do not use this method.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-07195: Exception configuring EntityManagerFactory.

Cause: TopLink could not bind name to anotherName.

Action: Ensure the correct use of this binding.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07196: [{0}] of type [{1}] cannot be casted to [{2}].

Cause: Exception configuring EntityManagerFactory.

Action: Ensure the correct configuration of this factory class. Check the internal exception for details on the root cause of this exception
Level: 1

Type: ERROR

Impact: Configuration

TOP-07197: This operation is not supported for this class: [{0}], [{1}].

Cause: TopLink could not calculate changes, because the primary key is set to null.

Action: Set the primary key to a non-null value.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-07198: Class: [{0}] was not found while converting from class names to classes.

Cause: Attempt to cast an instance of class ClassName to AnotherClassName. This is an invalid cast.

Action: Provide a valid cast.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-07199: A primary table was not defined for entity {0} in the entity-mappings file: {1}. A primary table is required to process an entity relationship.

Cause: An attribute attributeName in an entity class ClassName has a mappedBy value of value. This value does not exist in its owning entity class ClassName.

Action: If the owning entity class is an @EmbeddableSuperclass, this is invalid. Make your attribute reference the correct subclass.
Level: 1

Type: ERROR

Impact: Configuration

TOP-07200: The attribute [{1}] was not found on the embeddable class [{0}]. It is referenced in the @AttributeOverride for the @Embedded attribute [{3}] on class [{2}].

Cause: Either name or referencedColumnName element is not specified: if there is more than one join column, both the name and the referencedColumnName elements must be specified in each @JoinColumn annotation.

Action: Ensure that both the name and the referencedColumnName elements are specified in each @JoinColumn annotation.
Level: 1

Type: ERROR

Impact: Configuration

TOP-08001: Syntax Recognition Problem parsing the query [{0}]. The parser returned the following [{1}].

Cause: The TopLink EJB QL parser does not recognize a clause in the EJB QL string.

Action: Validate the EJB QL string.
Level: 1

Type: ERROR

Impact: Configuration

TOP-08002: General Problem parsing the query [{0}]. The parser returned the following [{1}].

Cause: TopLink has encountered a problem while parsing the EJB QL string.

Action: Check the internal exception for details on the root cause of this exception.
Level: 1

Type: ERROR

Impact: Configuration

TOP-08003: The class [{0}] was not found. The parser returned the following [{1}].

Cause: The class specified in the EJB QL string was not found.

Action: Ensure that the class is on the appropriate classpath.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-08004: A parsing problem was encountered resolving the alias - [{0}].

Cause: TopLink was unable to resolve the alias used in the EJB QL string.

Action: Validate the identifiers used in the EJB QL string.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-08005: A problem was encountered resolving the class name - The class [{0}] was not found.

Cause: TopLink was unable to resolve the class for an alias. This means that the class specified cannot be found.

Action: Ensure that the class is specified properly and is on the classpath.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-08006: A problem was encountered resolving the class name - The descriptor for [{0}] was not found.

Cause: The class specified in the query does not have a TopLink descriptor.

Action: Ensure that the class has been mapped and is specified correctly in the EJB QL string.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-08009: The expression [{0}] is currently not supported.

Cause: An unsupported expression was used in the EJB QL.

Action: Change the query to use only supported expressions.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-08010: General Problem parsing the query [{0}].

Cause: TopLink has encountered a problem while parsing the EJB QL string.

Action: Check the internal exception for details on the root cause of this exception.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-09000: Several [{0}] SessionLoaderExceptions were thrown:

Cause: The session loader caught one or more XML parsing exceptions while loading session information. The specific XML exceptions follow.

Action: Verify your session configuration XML file.
Level: 1

Type: ERROR

Impact: Configuration

TOP-09001: Unknown tag name: [{0}] in XML node: [{1}].

Cause: An unknown tag was encountered in the specified XML node.

Action: Examine the specified XML node in your session configuration XML file. Ensure that you use only the tags defined for that node in the appropriate TopLink XSD. See the directory where you installed TopLink (for example, <ORACLE_HOME>/toplink/config/xsds)
Level: 1

Type: ERROR

Impact: Configuration

TOP-09002: Unable to load Project class [{0}].

Cause: The specified class loader could not load a class with the name given by the project-name property.

Action: Verify the value of the project-name property and if correct, ensure that a class with that name is in your classpath.
Level: 1

Type: ERROR

Impact: Configuration

TOP-09003: Unable to process XML tag [{0}] with value [{1}].

Cause: The session loader caught an exception while either parsing the value of the specified tag or calling the setter method associated with the specified tag.

Action: Verify the value shown for the specified tag.
Level: 1

Type: ERROR

Impact: COnfiguration

TOP-09004: The project-xml file [{0}] was not found on the classpath, nor on the filesystem.

Cause: The session loader could not find the file identified by the project-xml tag on either the classpath or the file system.

Action: Verify the value of the project-xml tag and if correct, ensure that a project.xml file with that name exists in your classpath or file system.
Level: 1

Type: ERROR

Impact: Configuration

TOP-09005: An exception was thrown while loading the project-xml file [{0}].

Cause: The session loader caught an exception while trying to load the file identified by the project-xml tag either because the file could not be found, or because the file could not be parsed.

Action: Verify the configuration of the project XML file and ensure that a project.xml file with that name specified by the project-xml tag exists in your classpath or file system.
Level: 1

Type: ERROR

Impact: Configuration

TOP-09006: A {0} was thrown while parsing the XML file. It occurs at line {1} and column {2} in the XML document.

Cause: The session loader caught a SAX exception while trying to parse the XML at the given line and column of the specified XML file. TopLink 10g supports only UTF-8 encoding. The TopLink SAXParseException occurs if you attempt to read a non-UTF-8 formatted XML file.

Action: Verify that the XML is correctly formatted at the given line and column. Alternatively, ensure the Oracle parser is in your classpath and that it appears before any other XML parser.
Level: 1

Type: ERROR

Impact: Configuration

TOP-09007: An exception was thrown while parsing the XML file.

Cause: The session loader caught an exception unrelated to XML parsing (for example, a premature end-of-file exception) while trying to parse the specified XML file.

Action: Verify the integrity of the XML file.
Level: 1

Type: ERROR

Impact: Configuration

TOP-09008: Unexpected value [{0}] of tag [{1}].

Cause: The value of an XML tag does not correspond to any known TopLink required values.

Action: Please verify the list of values for this tag.
Level: 1

Type: ERROR

Impact: Configuration

TOP-09009: Tag [{0}] has unknown attribute.

Cause: There is an incorrect name value pair when processing transport properties for the XSD tag.

Action: Please verify that all properties have both the name and the value filled in, in the session configuration XML file.
Level: 1

Type: ERROR

Impact: Configuration

TOP-09010: A {0} was thrown while parsing the XML file against the XML schema.

Cause: An exception was raised while parsing the XML file against the XML schema.

Action: Examine the exception and take the appropriate action.
Level: 1

Type: ERROR

Impact: Configuration

TOP-10001: Exception [EJB - {0}]: Exception creating bean of type [{1}].

Cause: The PersistenceManager for the given application server failed to create and EJB bean (for example, a problem was encountered during the create process, such as a NullPointerException).

Action: Check the exception contained in the javax.ejb.CreateException for additional information.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10002: Exception [EJB - {0}]: Error removing primary key [{1}] for bean of type [{2}].

Cause: The PersistenceManager for the given application server failed to remove an EJB bean (for example, a problem was encountered during the removal, such as a NullPointerException).

Action: Check the exception contained in the javax.ejb.RemoveException for additional information.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10003: Exception [EJB - {0}]: An EJB Exception has occurred in bean of type [{1}].

Cause: An internal, unexpected exception was raised.

Action: See the exception message provided.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10004: Exception [EJB - {0}]: Cannot find bean of type [{1}] using finder: [{2}].

Cause: An unexpected exception was encountered while executing the finder method.

Action: See the exception message provided.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10007: Exception [EJB - {0}]: Exception creating bean of type [{1}]. Bean already exists.

Cause: The PersistenceManager for a given application server failed to create an EJB bean, because an EJB bean with the given primary key already exists.

Action: Verify the application logic to ensure the primary key is unique.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10008: Exception [EJB - {0}]: Cannot find bean of type [{1}] using finder [{2}]

Cause: A scalar finder (one that returns a single object) was invoked on a home interface, and returned a null value.

Action: Verify the application logic to ensure the desired EJB bean exists.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10009: Exception [EJB - {0}]: Cannot find bean of type [{2}] using findByPrimaryKey with primary key [{1}].

Cause: A finder method using the primary key indicated, returned a null value.

Action: Verify the application logic to ensure the desired EJB exists.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10010: Exception [EJB - {0}]: Exception creating bean of type [{1}]. Create cannot be invoked on this bean since it has been deployed as read only.

Cause: An attempt was made to create an entity marked as read-only using session().getProject().setDefaultReadOnlyClasses (aVector). You cannot create a read-only entity.

Action: Read-only entities should be read from the database (not created by the home interface). Adjust the application to read the required entities beforehand.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10011: Exception [EJB - {0}]: Exception removing bean of type [{1}]. Remove cannot be invoked on this bean since it has been deployed as read only.

Cause: An attempt was made to delete an entity marked as read-only using session().getProject().setDefaultReadOnlyClasses (aVector). You cannot delete a read-only entity.

Action: Determine whether or not the object should be read-only or not. If it should, do not try to remove it.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10014: Exception [EJB - {0}]: Error in non-transactional write for bean of type [{1}].

Cause: The PersistenceManager for a given application server failed to end a local transaction (made up of a non-synchronized, non-JTA UnitOfWork) after a remove, create, business method, or home method invocation.

Action: See the exception message provided.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10016: Exception [EJB - {0}]: An error occurred while getting transaction from TransactionManager.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10021: Exception [EJB - {0}]: An error occurred while attempting to assign sequence numbers for bean of type [{1}].

Cause: The PersistenceManager for a given application server, whose shouldAssignSequenceNumbers method returns true, failed to assign a sequence number to an entity.

Action: See the exception message provided.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10022: Exception [EJB - {0}]: RemoteException on method call [{1}] for bean of type {2}.

Cause: A java.rmi.RemoteException was raised when an entity was activated, loaded, passivated, or stored.

Action: See the exception message provided.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10023: Exception [EJB - {0}]: Sequence Exception for bean of type {1}.

Cause: An exception was raised while handling a post-insert DescriptorEvent preventing the specified entity from being assigned a primary key.

Action: See the exception message provided.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10025: Exception [EJB - {0}]: An internal error has occurred while accessing the EJBContext [{1}].

Cause: Internal error.

Action: Contact Oracle Support Services if required.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10026: Exception [EJB - {0}]: An internal error has occurred locating the generated subclass [{1}].

Cause: Internal error.

Action: Contact Oracle Support Services if required.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10027: Exception [EJB - {0}]: An internal error has occurred in a server process. EJBContext [{1}] not properly initialized.

Cause: Internal error.

Action: Contact Oracle Support Services if required.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10028: Exception [EJB - {0}]: The specified attribute [{1}] cannot be merged since it does not exist for beans of type [{2}].

Cause: The registerOrMergeAttribute method of the SessionAccessor, called from within an EJB setter method, failed to obtain a DatabaseMapping for the given attribute from the PersistenceManager.

Action: Verify that the given attribute belongs to the EJB class and if it does, verify that a mapping exists for it.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10029: Exception [EJB - {0}]: An internal error occurred accessing the bean or primary key class.

Cause: Failed to wrap an EJB bean for return to the application because the attempt to extract the primary key from the bean failed.

Action: See the exception message provided.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10030: Exception [EJB - {0}]: An internal error occurred accessing the bean of type [{1}] or primary key class.

Cause: Failed to initialize primary key fields due to java.lang.NoSuchFieldException.

Action: See the exception message provided.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10031: Exception [EJB - {0}]: Unable to prepare bean of type [{1}] with pk [{2}] for invocation.

Cause: One of the following failed with an exception other than javax.ejb.ObjectNotFoundException: a conforming find using the same query as a find by primary key; an Oracle Containers for J2EE startCall method invocation for a BUSINESS METHOD operation; or a WebLogic preInvoke method invocation.

Action: See the exception message provided.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10032: Exception [EJB - {0}]: Finder not yet implemented: {2}{1}.

Cause: Associated finder method has no implementation.

Action: Provide an implementation for the finder method.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10033: Exception [EJB - {0}]: findByPrimaryKey invoked with null primary key for bean of type [{1}].

Cause: A find by primary key was called with a null primary key value.

Action: Ensure the primary key is not null when the finder method is invoked.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10034: Exception [EJB - {0}]: Remove on bean of type [{1}] invoked with null primary key.

Cause: A find by primary key was called with a null primary key value.

Action: Ensure the primary key is not null when the finder method is invoked.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10036: Exception [EJB - {0}]: An error occurred during code generation.

Cause: The PersistenceManager for a given application server failed to generate a bean subclass.

Action: See the exception message provided.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10037: Exception [EJB - {0}]: Error while executing ejbSelectMethod: [{1}] on bean of type [{2}].

Cause: An EJB select failed with an exception other than javax.ejb.ObjectNotFoundException.

Action: See the exception message provided.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10038: Exception [EJB - {0}]: Error while executing ejbHomeMethod: [{1}].

Cause: The invocation of a home interface method (excluding finder or create methods) failed.

Action: See the exception message provided.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10040: Exception [EJB - {0}]: No transaction was active on invocation of {1} method.

Cause: A create or remove EJB failed because the PersistenceManager does not have a transaction.

Action: Ensure your application has a transaction available. This may be a configuration problem related to your ejb-jar.xml file or an application logic problem in your client code.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10041: Exception [EJB - {0}]: The parameter passed to the {1} method has already been deleted.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10043: Exception [EJB - {0}]: Unable to wrap the results of the finder because " + " they have already been wrapped. If using a custom query (ex: a redirect query), " + " then be sure that you called 'setShouldUseWrapperPolicy(false)'.

Cause: The results of a finder query could not be wrapped because they were already wrapped.

Action: If a redirect query is used, be sure to call the setShouldUseWrapperPolicy(false) method first.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10045: Exception [EJB - {0}]: Unable to wrap the results of the finder as " + " EJBLocalObjects because there is no Local interface. If executing an ejbSelect " + " query, make sure the result-type-mapping tag is correctly.

Cause: Error resolving the local interface.

Action: Double-check your local interface configuration.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10046: Exception [EJB - {0}]: Unable to wrap the results of the finder as " + " EJBObjects because there is no Remote interface. If executing an ejbSelect " + " query, make sure the result-type-mapping tag is correctly.

Cause: Error resolving the remote interface.

Action: Please double-check your remote interface configuration.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10047: Exception [EJB - {0}]: Trying to create a bean with a null primary key. Check your " + " bean's ejbCreate method to ensure the primary key fields are set. If TopLink " + " sequencing is being used, make sure hat sequencing is setup correctly on all the " + " beans in the TopLink project.

Cause: The PersistenceManager for a given application server failed to create a bean because the primary key was not defined.

Action: Make sure the primary key is defined properly, either in the application logic or through the sequence number configuration.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10049: Exception [EJB - {0}]: The argument [{1}] of type [{2}] is not of the correct type for the " + " relationship. See section 10.3.6 of the EJB 2.1 specification. The argument type expected was [{3}].

Cause: The argument is not of the correct type for the relationship. See section 10.3.6 of the EJB 2.1 specification.

Action: Check the parameter type to ensure that it is of the correct type for this collection.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10051: Exception [EJB - {0}]: An attempt was made to access a Collection/Iterator outside a transaction " + " or in one other than the one in which it was acquired. See section 10.3.8 of " + " the EJB 2.1 specification.

Cause: An attempt was made to access a Collection or Iterator outside a transaction or in one other than the one in which it was acquired. See section 10.3.8 of the EJB 2.1 specification.

Action: Check the CMR collection to determine whether it is being accessed in the same transaction.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10052: Exception [EJB - {0}]: Cannot find bean of type [{2}] with primary key [{1}] for remote method invocation.

Cause: Cannot find bean of type with primary key for remote method invocation.

Action: The exception will be raised if the finder method returns a null result during remote method invocation. Ensure that the bean has already existed before lookup.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10053: Exception [EJB - {0}]: Cannot find bean of type [{2}] with primary key [{1}] for local method invocation.

Cause: Cannot find bean of type with primary key for local method invocation.

Action: This exception will be raised if the finder method returns a null result during local method invocation. Ensure that the bean already exists before lookup.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10054: Exception [EJB - {0}]: An internal error has occurred while accessing the bean of type [{1}]

Cause: An internal error has occurred while accessing the bean.

Action: An internal exception occurred during create bean instance. Check the internal exception.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10055: Exception [EJB - {0}]: An error has occurred while cascading the delete from the bean of type [{1}] to the [{2}] relationship.

Cause: An error has occurred while cascading the delete from the bean to the relationship.

Action: An error occurred while performing cascade-delete of private owned objects. Check the underlying exception.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10056: Exception [EJB - {0}]: An error has occurred while performing relationship maintenance for the bean of type [{1}] with the [{2}] relationship.

Cause: An error has occurred while performing relationship maintenance for the bean with the relationship.

Action: Check the private-owned (cascade-delete) relationship in the domain object and also the underlying exception.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10057: Exception [EJB - {0}]: Multiple results were found while executing the single object finder [{2}] for the bean of type [{1}].

Cause: Multiple results were found while executing the single object finder for the bean.

Action: Check if the query is passed properly and also the underlying TopLink query exception.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10058: Exception [EJB - {0}]: Unable to invoke method [{1}] on bean of type [{2}] because this bean is read only.

Cause: Unable to invoke method on bean because this bean is read only.

Action: Check the bean descriptor to see if the read-only flag was specified.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10059: Exception [EJB - {0}]: Unable to invoke method [{1}] on bean of type [{2}] because the target bean " + " of type [{3}] is read only. Either the target bean's object model (in the case of bi-directional relationship) or database table would not be modified by this operation.

Cause: Unable to invoke method on bean because the target bean is read only. Either the target bean's object model (in the case of a bidirectional relationship) or the database table would not be modified by this operation.

Action: Check the target bean descriptor for the 1:1 relationship in the domain object, to see if the read-only flag was specified.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10060: Exception [EJB - {0}]: Unable to invoke method [{1}] on collection [{2}] in bean of type [{3}] because the source bean is read only.

Cause: Unable to invoke method on collection in bean because the source bean is read only.

Action: Check the source bean descriptor for the 1:M and M:M relationship in the domain object, to see if the read-only flag was specified.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10061: Exception [EJB - {0}]: Unable to invoke method [{1}] on collection [{2}] in bean of type [{3}] because the target bean of type [{4}] is read only. " + " Either the target bean's object model (in the case of bi-directional relationship) or database table would not be modified by this operation.

Cause: Unable to invoke method on collection in bean because the target bean is read only. Either the target bean's object model (in the case of a bidirectional relationship) or the database table will not be modified by this operation.

Action: Check the bidirectional target bean descriptor to see if the read-only flag was specified.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10062: Exception [EJB - {0}]: Unable to retrieve underlying data for object type : {2} primary keys: {1}. Transaction must be restarted and objects refreshed.

Cause: Unable to retrieve underlying data for object primary keys. The transaction must be restarted and objects refreshed.

Action: The underlying object is garbage collected and removed from the cache. Restart the transaction and refresh all objects.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10063: Exception [EJB - {0}]: Unknown collection type : {1} passed to container policy.

Cause: Unknown collection type passed to container policy.

Action: Ensure that the correct collection type is used.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10064: Exception [EJB - {0}]: Any changes to fields must be performed within a transaction.

Cause: Any changes to fields must be performed within a transaction.

Action: Ensure that any changes are performed within a transaction.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10065: Exception [EJB - {0}]: An error occurred while adding object {1} to collection {2}.

Cause: An error occurred while adding an object to a collection.

Action: An error occurred during relationship maintenance for the add method. Check the underlying exception.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10066: Exception [EJB - {0}]: An error occurred while removing object {1} from collection {2}.

Cause: An error occurred while removing an object from a collection.

Action: An error occurred during relationship maintenance for the remove method. Check the underlying exception.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10067: Exception [EJB - {0}]: An error occurred while performing relationship maitenance for the field {1}.

Cause: An error occurred while performing relationship maintenance for a field.

Action: An error occurred on relationship maintenance for the cmr field. Check the underlying exception.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10068: Exception [EJB - {0}]: An error occurred with the DataSource {1}. TopLink CMP requires use of a managed-data-source. A native-data-source cannot be used.

Cause: An error occurred with the data source. TopLink CMP requires use of a managed-data-source. A native-data-source cannot be used.

Action: Check the data-sources.xml file in OC4J. TopLink CMP requires the use of a managed-data-source.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10069: Exception [EJB - {0}]: Failed lookup of object under JNDI name: {1}.

Cause: Failed lookup of object under JNDI name.

Action: Check the JNDI name and also the underlying javax.naming.NamingException.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-10070: Exception [EJB - {0}]: An internal error occurred accessing the bean of type [{1}] or primary key class of type [{2}].

Cause: An internal error occurred accessing the bean of type or primary key class of type.

Action:
Level: 1

Type: ERROR

Impact: Programmatic

TOP-12000: Error Sending connection service to {0}.

Cause: Failed to add a connection to CacheSynchronizationManager or RemoteCommandManager.

Action: See the generated exception for the root cause.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-12001: Unable to Connect to {0}.

Cause: CacheSynronizationManager failed to connect to the specified service.

Action: See the generated exception for the root cause.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-12002: Unable to propagate changes to {0}.

Cause: CacheSynronizationManager failed to propagate changes to the specified service.

Action: See the generated exception for the root cause.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-12003: Error in invocation: {0}.

Cause: Error invoking a remote call.

Action: See the generated exception for the root cause.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-17007: {0} property must be set.

Cause: The specified property is not set.

Action: Verify your interaction and ensure that the specified property is set (see "Configuring Custom EIS Interactions for Basic Persistence Operations" on page 73-6 or "Creating an EIS Interaction for a Named Query" on page 116-26).
Level: 1

Type: ERROR

Impact: Configuration

TOP-17008: Invalid {0} property encountered.

Cause: Invalid property encountered.

Action: Verify your interaction and remove the specified property (see "Configuring Custom EIS Interactions for Basic Persistence Operations" on page 73-6 or "Creating an EIS Interaction for a Named Query" on page 116-26).
Level: 1

Type: ERROR

Impact: Configuration

TOP-17009: {0} or {1} property must be set.

Cause: The specified properties are not set.

Action: Verify your interaction and ensure that the specified properties are set (see "Configuring Custom EIS Interactions for Basic Persistence Operations" on page 73-6 or "Creating an EIS Interaction for a Named Query" on page 116-26).
Level: 1

Type: ERROR

Impact: Configuration

TOP-17010: Output record contains an unsupported message type

Cause: The output record contains an unsupported message type.

Action: Verify your interaction and ensure that you specify a supported message type. Ensure that the required connector JAR file is on your classpath (see "EIS Project Concepts" on page 68-1).
Level: 1

Type: ERROR

Impact: Configuration

TOP-17011: No connection factory has been specified.

Cause: The connection factory is not specified.

Action: Verify your interaction and ensure that you specify a connection factory (see "Configuring EIS Connection Specification Options at the Project Level" on page 70-3 or "Configuring EIS Connection Specification Options at the Session Level" on page 96-2 ).
Level: 1

Type: ERROR

Impact: Configuration

TOP-17012: InteractionSspec must be a CciJMSInteractionSpec.

Cause: InteractionSpec is not a CciJMSInteractionSpec.

Action: Verify your interaction and ensure that you specify a valid interaction specification type (CciJMSInteractionSpec). Ensure that the required connector JAR file is on your classpath (see "EIS Project Concepts" on page 68-1).
Level: 1

Type: ERROR

Impact: Configuration

TOP-17013: Record must be a CciJMSRecord.

Cause: Record is not a CciJMSRecord.

Action: Verify your interaction and ensure that you specify a valid record type (CciJMSRecord). Ensure that the required connector JAR file is on your classpath (see "EIS Project Concepts" on page 68-1).
Level: 1

Type: ERROR

Impact: Configuration

TOP-17014: Unknown interaction specification type

Cause: Unknown interaction specification type.

Action: Verify your interaction and ensure that you specify a valid interaction specification type. Ensure that the required connector JAR file is on your classpath (see "EIS Project Concepts" on page 68-1).
Level: 1

Type: ERROR

Impact: Configuration

TOP-17015: Input must contain a single text element.

Cause: Invalid input: input must contain a single text element.

Action: Verify your interaction and ensure that you specify valid input-a single text element (see "Configuring Custom EIS Interactions for Basic Persistence Operations" on page 73-6 or "Creating an EIS Interaction for a Named Query" on page 116-26).
Level: 1

Type: ERROR

Impact: Configuration

TOP-17016: A timeout occurred - no message was received.

Cause: A time-out occurred-no message was received.

Action: Verify your interaction and the EIS on which you invoked it.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-17017: Input record contains an unsupported message type.

Cause: Input record contains an unsupported message type.

Action: Verify your interaction and ensure that you specify a valid message type. Ensure that the required connector JAR file is on your classpath (see "EIS Project Concepts" on page 68-1).
Level: 1

Type: ERROR

Impact: Configuration

TOP-17018: Cannot invoke "begin()" on a non-transacted session.

Cause: TopLink cannot invoke begin method on a nontransacted session.

Action: To be determined.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-17019: Problem testing for transacted session:

Cause: Problem testing for transacted session.

Action: To be determined.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-17020: InteractionSspec must be an AQInteractionSpec.

Cause: InteractionSpec is not an AQInteractionSpec.

Action: Verify your interaction and ensure that you specify a valid Oracle AQ interaction specification type (AQInteractionSpec). Ensure that the required connector JAR file is on your classpath (see "EIS Project Concepts" on page 68-1).
Level: 1

Type: ERROR

Impact: Configuration

TOP-17021: Record must be an AQRecord.

Cause: Record is not an AQRecord.

Action: Verify your interaction and ensure that you specify a valid Oracle AQ record type (AQRecord). Ensure that the required connector JAR file is on your classpath (see "EIS Project Concepts" on page 68-1).
Level: 1

Type: ERROR

Impact: Programmatic

TOP-17022: Input must contain a single raw element.

Cause: Invalid input: input must contain a single raw element.

Action: Verify your Oracle AQ interaction and ensure that you specify valid input-a single raw element (see "Configuring Custom EIS Interactions for Basic Persistence Operations" on page 73-6 or "Creating an EIS Interaction for a Named Query" on page 116-26).
Level: 1

Type: ERROR

Impact: Programmatic

TOP-17023: An exception occurred setting MQQueueConnectionFactory attributes.

Cause: An exception occurred setting MQQueueConnectionFactory attributes.

Action: Verify your interaction and ensure that you specify an appropriate IBM MQSeries connection factory (see "Configuring EIS Connection Specification Options at the Project Level" on page 70-3 or "Configuring EIS Connection Specification Options at the Session Level" on page 96-2).
Level: 1

Type: ERROR

Impact: Programmatic

TOP-17024: Could not delete file: {0}

Cause: TopLink cannot delete the specified file.

Action: To be determined.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-17025: This mapping requires a foreign key grouping element, as mulitple foreign keys exist.

Cause: No grouping element is specified: this mapping requires a foreign key grouping element, as mulitple foreign keys exist.

Action: Verify your EIS mappings (see Chapter 74, "Introduction to EIS Mappings".
Level: 1

Type: ERROR

Impact: Programmatic

TOP-18001: Error while processing incomming JMS message

Cause: Failed to process the incoming JMS message.

Action: See the generated exception for the root cause.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-18002: The topic created in the JMS service for the interconnection of sessions must be set in the JMSClusteringService

Cause: JMSClusteringService failed to start because the Topic created in the JMS service for the interconnection of sessions is null.

Action: Ensure that the Topic created in the JMS service for the interconnection of sessions is set in the JMSClusteringService.
Level: 1

Type: ERROR

Impact: Configuration

TOP-18003: Failed to lookup the session's name defined it the env-entry element of the Message Driven Bean

Cause: Failure in looking up the session's name defined it the env-entry element of the message-driven bean.

Action: Verify the correctness of the env-entry element definition of the Message Driven Bean.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-18004: The Message Driven Bean (MDB) cannot find the session.

Cause: The message-driven bean (MDB) cannot find the session.

Action: Ensure that the session that this MDB's getSession() method returns is not null session.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-20001: Could not find the parameter type: [{2}], defined in the ejb-jar.xml, of the finder: [{1}] in the entity bean: [{0}].

Cause: TopLink could not find the parameter type, defined in the ejb-jar.xml file of the finder in the entity bean.

Action: Check the finder definition in the ejb-jar.xml file and the bean home to ensure that the named finder has the specified method parameter type(s).
Level: 1

Type: ERROR

Impact: Programmatic

TOP-20002: The finder method: [{1}] with the parameters as: [{2}], defined in the ejb-jar.xml, is not found in the home of bean: [{0}].

Cause: The finder method with the parameters as defined in the ejb-jar.xml file is not found in the home of bean.

Action: Check the ejb-jar.xml file and the bean home to ensure that the finder with the specified name and method parameter type(s) are defined.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-20003: The ejbSelect method: [{1}] with the parameters as: [{2}], defined in the ejb-jar.xml, is not found in the bean class of bean: [{0}].

Cause: The ejbSelect method with the parameters, as defined in the ejb-jar.xml file, is not found in the bean class.

Action: Check the ejb-jar.xml file and the bean class to ensure that the ejbSelect method is defined with the specified name and method parameter type(s).
Level: 1

Type: ERROR

Impact: Programmatic

TOP-20004: The finder method: [{1}] of bean: [{0}] in ejb-jar.xml file is not well defined. It should start with either 'find' or 'ejbSelect'.

Cause: The finder method of bean in the ejb-jar.xml file is not well defined. It should start with either find or ejbSelect.

Action: Check the ejb-jar.xml file to ensure that the query name starts with find or ejbSelect, according to the EJB specification.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-20005: The abstract getter method: [{0}] is not defined in the bean: [{1}].

Cause: The abstract get method is not defined in the bean.

Action: Check the ejb-jar.xml file and the bean class to ensure that the abstract get method is well defined.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-20006: The cmp field: [{0}] is not defined in the bean: [{1}].

Cause: The CMP field is not defined in the bean.

Action: Check the ejb-jar.xml file and the bean class to ensure that the CMP field defined in the ejb-jar.xml file is also defined in the bean class.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-22001: Could not join multicast group

Cause: DiscoveryManager failed to join a multicast group due to a java.io.IOException: either a MulticastSocket could not be created, or the invocation of the joingGroup method of the MulticastSocket failed.

Action: See the generated exception for the root cause.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-22002: Could not send service announcement

Cause: DiscoveryManager failed to inform other services that its service had started up.

Action: Consider increasing the announcement delay: the amount of time in milliseconds that the service should wait between the time that this remote service is available and a session announcement is sent out to other discovery managers. This may be needed to give some systems more time to post their connections into the naming service. See the setAnnouncementDelay method of the DiscoveryManager.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-22003: Failed doing lookup of local host

Cause: DiscoveryManager failed to do the lookup of a local host.

Action: See the generated exception for the root cause.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-22004: Failed trying to receive a service announcement from a remote service

Cause: DiscoveryManager caught a java.io.IOException while blocking for announcements from other DiscoveryManagers.

Action: See the generated exception for the root cause.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-22101: Could not obtain JNDI context with properties {0}

Cause: Failure to get a JNDI context with the specified properties due to a javax.naming.NamingException.

Action: See the generated exception for root cause. Verify that the properties for looking up the context are correct.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-22102: Could not post connection in local naming service under name {0}

Cause: Failure to post a connection in the local naming service with the name serviceName.

Action: See the generated exception for the root cause.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-22103: Could not look up remote connection under name {0} with URL {1}

Cause: Failure to look up a remote connection with the specified name and URL.

Action: See the generated exception for the root cause. Verify that the remote connection and URL are correct.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-22104: Could not look up hostname

Cause: The getLocalHost method of the java.net.InetAddress failed to look up the specified host name.

Action: See the generated exception for the root cause. Verify that the host is online and reachable.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-22105: Could not propagate command to {0}

Cause: Failure to propagate a command to the specified connection.

Action: See the generated exception for the root cause. Verify that the remote host of the specified connection is online and reachable if the generated exception included a CommunicationException.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-22106: Could not create external JMS connection with Topic {0}, Topic Factory {1}, and Context properties {2}

Cause: Failure to create JMS connection with Topic, Topic Factory, and Context properties.

Action: Verify that the JMS Topic is configured correctly with the application server and the specified Topic. Topic Factory and Context properties info can be used by a Java client to the JMS Topic.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-22107: Could not remove local connection in local naming service under name {0}

Cause: Failure to establish a remove local connection in local naming service under name.

Action: Restart the application server or use the application server tool to remove name from its JNDI if this tool is available.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-22108: Could not serialize or desiralize command

Cause: Failure to serialize or deserialize command.

Action: If the command is a user defined command, make sure it is serializable. If it is a TopLink command, file a bug report including the stack trace.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-22109: Failed to receive JMS message from JMS provider

Cause: Failure to receive JMS message from JMS provider.

Action: Make sure that TopLink sessions are the only publishers to the JMS Topic and that the TopLink sessions use the same project.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-22110: Failed to discover local host IP address.

Cause: Failure to discover local host IP address.

Action: Replace the $HOST string of the URL with the known host name or IP address.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-22111: Failed to get ServerPlatform. The ServerPlatform must be set either on Session or RemoteCommandManager.

Cause: Failure to get server platform. The server platform must be set on Session or RemoteCommandManager.

Action: Set the correct ServerPlatform on the RemoteCommandManager. This exception is raised when the user does not use a TopLink Session and implements the CommandProcessor.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-23001: Error looking up external Transaction resource under JNDI name [{0}]

Cause: Error looking up external transaction resource under JNDI name name.

Action: Examine the internal exception and take the appropriate action.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-23002: Error obtaining status of current externally managed transaction

Cause: Error obtaining the status of the current externally-managed transaction.

Action: Examine the internal exception and take the appropriate action.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-23003: Error obtaining current externally managed transaction

Cause: Error obtaining the current externally managed transaction.

Action: Examine the internal exception and take the appropriate action.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-23004: Error obtaining the Transaction Manager

Cause: Error obtaining the transaction manager.

Action: Examine the internal exception and take the appropriate action.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-23005: Error binding to externally managed transaction

Cause: Error binding to the externally managed transaction.

Action: Examine the internal exception and take the appropriate action.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-23006: Error beginning new externally managed transaction

Cause: Error beginning a new externally managed transaction.

Action: Examine the internal exception and take the appropriate action.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-23007: Error committing externally managed transaction

Cause: Error committing the externally managed transaction.

Action: Examine the internal exception and take the appropriate action.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-23008: Error rolling back externally managed transaction

Cause: Error rolling back the externally managed transaction.

Action: Examine the internal exception and take the appropriate action.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-23009: Error marking externally managed transaction for rollback

Cause: Error marking the externally managed transaction for rollback.

Action: Examine the internal exception and take the appropriate action.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-23010: No externally managed transaction is currently active for this thread

Cause: No externally managed transaction is currently active for this thread.

Action: Ensure that the transaction is still active.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-23011: UnitOfWork [{0}] was rendered inactive before associated externally managed transaction was complete.

Cause: A UnitOfWork was rendered inactive before the associated externally managed transaction was complete.

Action: Examine the internal exception and take the appropriate action.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-23012: No transaction is currently active

Cause: Attempt to use an EntityTransaction while using JTA. This is an invalid operation.

Action: Examine the internal exception and take the appropriate action.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-23013: Transaction is currently active

Cause: Attempt to enlist multiple data sources in the transaction.

Action: Enlist only one data source per transaction.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-23014: Cannot use an EntityTransaction while using JTA.

Cause: Exception occurred in Proxy execution.

Action: Examine the internal exception and take the appropriate action.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-23015: Cannot enlist multiple datasources in the transaction.

Cause: No entity transaction is currently active for this thread.

Action: Ensure that the transaction is active.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-25001: Invalid XPath string: {0}

Cause: Attempt to use an invalid XPath string.

Action: Ensure that the XPath is specified correctly.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-25002: An integer index could not be parsed from this XPath string: {0}

Cause: An integer index could not be parsed from this XPath string.

Action: Update any XPath strings that contain an index, and ensure that only a single integer value is contained between the square braces.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-25003: An error occurred marshalling the object

Cause: An error occurred marshalling the object.

Action: Check the nested exception to determine the cause of the problem. Typically, there is a problem with the object being written.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-25004: An error occurred unmarshalling the document

Cause: An error occurred unmarshalling the document.

Action: Check the nested exception to determine the cause of the problem. Typically, there is a problem with the XML document being read.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-25005: An error occurred validating the object

Cause: An error occurred validating the object.

Action: The XML generated from the object is invalid according to the schema. Ensure that any values set in the domain classes do not violate any schema constraints when marshalled.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-25006: A default root element was not specified for the XMLDescriptor mapped to {0}

Cause: A default root element is not specified for the XMLDescriptor mapped to target.

Action: Specify the default root element for the descriptor.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-25007: A descriptor for class {0} was not found in the project

Cause: A descriptor for a class was not found in the project.

Action: Make sure that any classes referenced through CompositeObject and/or CompositeCollection mappings have descriptors in the project.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-25008: A descriptor with default root element {0} was not found in the project

Cause: A descriptor with a default root element was not found in the project.

Action: Set a default root element on any descriptor that maps to the root of a document. Make sure that the root element of the XML document being read in is mapped to a descriptor in the project.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-25010: A schema reference was not specified for the XMLDescriptor mapped to {0}

Cause: A schema reference is not specified for the XMLDescriptor mapped to target.

Action: Specify the schema reference for the descriptor.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-25011: A null argument was encountered

Cause: A null argument was encountered.

Action: Ensure that this argument is not null.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-25012: An error occurred resolving the XML Schema.

Cause: An error occurred resolving the XML Schema.

Action: Check any schema references and make sure that the schema can be accessed by the application at runtime.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-25013: An error occurred while trying to set the schemas.

Cause: An error occurred while trying to set the schemas.

Action: An error was encountered while attempting to set schemas on an XML parser. Check the nested exception to determine the correct course of action.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-25014: An error occurred while trying to instantiate the schema platform.

Cause: An error occurred while trying to instantiate the schema platform.

Action: An error was encountered while instantiating the schema platform. Check the nested exception to determine the correct course of action.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-25015: An error occurred trying to resolve the namespace URI for {0}. A namespace resolver was not specified on the descriptor.

Cause: An error occurred while trying to resolve the namespace URI for a target. A namespace resolver was not specified on the descriptor.

Action: Ensure that any descriptors that make use of namespaces have a namespace resolver specified on them.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-25016: A namespace for the prefix {0} was not found in the namespace resolver.

Cause: A namespace for the prefix was not found in the namespace resolver.

Action: Ensure that any namespace prefix which is used by a descriptor or mapping has a corresponding entry in that descriptor's namespace resolver.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-25017: Either enumClass or enumClassName must be set on the JAXBTypesafeEnumConverter.

Cause: Enumeration class is not specified.

Action: Set either enumClass or enumClassName on the JAXBTypesafeEnumConverter.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-25018: The fromString method on the enum class {0} does not exist or could not be invoked.

Cause: Error during the invocation of the fromString method on the enumeration class ClassName: the method does not exist or could not be invoked.

Action: See the generated exception for the root cause.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-25019: The specified enum class {0} could not be found.

Cause: The specified enumeration class ClassName was not found.

Action: Ensure the correct specification of the enumeration class.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-25020: The method getResult() must not be called before the endDocument() event has been called.

Cause: Attempt to call the method getResult before the call to the endDocument event.

Action: Call the getResult method after the endDocument event has been called.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-25501: Cannot create URL for file [{0}] .

Cause: Failure to create a URL for the specified file.

Action: Ensure that all specified XPath strings on mappings are valid and correct.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-26001: WLS->OC4J TopLink migration exception: There contains multiple migratable JARs in the input EAR({0}), and orion-ejb-jar.xml is also provided in the input. The migration utility only supports single migratable JAR in an EAR if orion-ejb-jar.xml is also in the input.

Cause: The migration utility only supports a single migratable JAR file in an EAR file if the orion-ejb-jar.xml file is also in the input.

Action: Remove the orion-ejb-jar.xml file from the input directory, or keep only one migratable JAR file in the input EAR file.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-26002: The program security manager prevents the migration utility from creating a JAR class loader for Jar file({0})

Cause: The program security manager prevents the migration utility from creating a JAR class loader for the JAR file.

Action: Configure the program security manager to grant permission on the program to create the JAR class loader.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-26003: The program security manager prevents the migration utility from creating directory({0})

Cause: The program security manager prevents the migration utility from creating a directory.

Action: Configure the program security manager to grant permission on the program to create a local directory.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-26004: The file({0}) is not accessible by the migration utility

Cause: The file is not accessible by the migration utility.

Action: Check to ensure that the file is on the specified path and is readable.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-26005: The program security manager prevents the migration utility from deleting directory({0})

Cause: The program security manager prevents the migration utility from deleting a directory.

Action: Configure the program security manager to grant permission to the program to delete files.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-26006: i/o exception occurs when reading data from an input stream

Cause: A java.io.IOException occurred when reading data from an input stream.

Action: Check to ensure that the file is not locked and is accessible.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-26007: i/o exception occurs when closing data from an input or output stream

Cause: A java.io.IOException occurred when closing data from an input or output stream.

Action: Check to ensure that the file is not locked and is accessible.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-26008: i/o exception occurs when closing data from an zip file

Cause: A java.io.IOException occurred when closing data from a zip file.

Action: Check to ensure that the zip file is not locked and is accessible.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-26009: Jar file({0}) not found or accessible in the specified path

Cause: The JAR file was not found or was not accessible on the specified path.

Action: Check to ensure that the JAR file is not locked and is accessible.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-26010: Query method({0}) with parameters({1}) of the entity({2}) defined in ejb-jar.xml is not well defined as it starts by neither 'find' nor 'ejbSelect'

Cause: Query method with parameters of the entity defined in the ejb-jar.xml file is not well defined as it does not start with find or ejbSelect.

Action: Check the ejb-jar.xml file to ensure that the finder name starts with either find or ejbSelect according to the EJB spec.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-26011: The class({1}) defined as a parameter type of the query({0}) of the entity({2}) in ejb-jar.xml could not be loaded. Most likely, the class is not included not in the classpath.

Cause: The class defined as a parameter type of the query of the entity in ejb-jar.xml could not be loaded.

Action: Ensure that the bean class is included on the classpath.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-26012: Finder method({0}) with parameters({1}) defined in ejb-jar.xml is not defined at the entity({2})'s (local and/or remote) home interface

Cause: The finder method with parameters defined in the ejb-jar.xml file is not defined at the entity's local and/or remote home interface.

Action: Check the ejb-jar.xml file and the bean home to ensure that the finder method parameter types are properly defined.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-26013: ejbSelect method({0}) with parameters({1}) defined in ejb-jar.xml is not defined at the entity({2})'s bean class

Cause: The ejbSelect method with parameters defined in the ejb-jar.xml file is not defined at the entity's bean class.

Action: Check the ejb-jar.xml file and the bean class to ensure that the ejbSelect method parameter types are properly defined.
Level: 1

Type: ERROR

Impact: Configuration

TOP-26014: Entity({0}) specified in weblogic-cmp-jar.xml is not defined in weblogic-ejb-jar.xml.

Cause: The entity specified in the weblogic-cmp-jar.xml file is not defined in the weblogic-ejb-jar.xml file.

Action: Ensure that the entity is consistently defined in the deployment descriptor files.
Level: 1

Type: ERROR

Impact: Configuration

TOP-26015: No entity element is defined in weblogic-cmp-rdbms-jar.xml file

Cause: No entity element is defined in the weblogic-cmp-rdbms-jar.xml file.

Action: Ensure that all entities defined in the ejb-jar.xml file are mapped in the WebLogic CMP descriptor file.
Level: 1

Type: ERROR

Impact: Configuration

TOP-26016: The weblogic cmp descriptor file({0}) specified in the weblogic-ejb-jar.xml is not found in the directory ({1})

Cause: The WebLogic CMP descriptor file specified in the weblogic-ejb-jar.xml file was not found in the directory.

Action: Ensure that the WebLogic CMP descriptor file, specified in the weblogic-ejb-jar.xml file, is included in the input directory.
Level: 1

Type: ERROR

Impact: Configuration

TOP-26017: The cmp descriptor file({1}) is not found in the jar({0}) file to be migrated.

Cause: The CMP descriptor file is not found in the JAR file to be migrated.

Action: Ensure that the WebLogic CMP descriptor file, specified in the weblogic-ejb-jar.xml file, is included in the input archive JAR file.
Level: 1

Type: ERROR

Impact: Configuration

TOP-26018: Some of the entity beans ({0}) defined at ejb-jar.xml in the jar ({1}) are not explicitly mapped in orion-ejb-jar.xml. You need to provide the completely mapped orion-ejb-jar.xml to the migration tool. You can obtain the completely mapped orion-ejb-jar.xml from the /application-deployment directory after deploying the application.

Cause: Some of the entity beans EntityBeanClassName-s defined in the ejb-jar.xml file in the JAR jarName are not explicitly mapped in the orion-ejb-jar.xml file.

Action: Provide the completely mapped orion-ejb-jar.xml file to the migration tool. You can obtain the completely mapped orion-ejb-jar.xml file from the /application-deployment directory after deploying the application.
Level: 1

Type: ERROR

Impact: Configuration

TOP-26019: The entity ({0}) in orion-ejb-jar.xml is not mapped as no table or primary key mapping is specified. You need to provide the completely mapped orion-ejb-jar.xml to the migration tool. You can obtain the completely mapped orion-ejb-jar.xml from the /application-deployment directory after deploying the application.

Cause: The entity EntityName in the orion-ejb-jar.xml file is not mapped, because no table is specified.

Action: Provide the completely mapped orion-ejb-jar.xml file to the migration tool. You can obtain the completely mapped orion-ejb-jar.xml file from the /application-deployment directory after deploying the application.
Level: 1

Type: ERROR

Impact: Configuration

TOP-26020: The entity ({0}) specified in orion-ejb-jar.xml is not defined in ejb-jar.xml.

Cause: The entity EntityName specified in the orion-ejb-jar.xml file is not defined in the ejb-jar.xml file.

Action: Define this entity in the ejb-jar.xml file.
Level: 1

Type: ERROR

Impact: Configuration

TOP-27001: The XML Platform class was not found: {0}

Cause: The XML platform class ClassName was not found.

Action: Ensure that this class is on the classpath.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-27002: The XML Platform could not be instantiated: {0}

Cause: Failure to instantiate the XML platform ClassName.

Action: See the generated exception for the root cause.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-27003: A new XML document could not be created.

Cause: The XML platform failed to create a new XML document.

Action: See the generated exception for the root cause.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-27004: The XPath was invalid.

Cause: The XPath is invalid.

Action: See the generated exception for the root cause.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-27005: An error occurred while validating the document.

Cause: Error during the document validation.

Action: See the generated exception for the root cause.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-27006: Could not resolve XML Schema: {0}

Cause: Failure to resolve an XML Schema schema: XML platform parser error occurred.

Action: See the generated exception for the root cause.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-27101: An error occurred while parsing the document.

Cause: Failure to parse the document.

Action: See the generated exception for the root cause.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-27102: File not found: [{0}]

Cause: Failure to find the XML platform parser file.

Action: Ensure that the parser file exists and is accessible (on the classpath).
Level: 1

Type: ERROR

Impact: Programmatic

TOP-27103: ** Parsing error, line [{0}], uri [{1}] [{2}]

Cause: SAX parser error at line lineNumber, URI uri.

Action: See the generated exception for the root cause.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-27201: An error occurred while transforming the document.

Cause: Error during the transforming of the document.

Action: See the generated exception for the root cause.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-27202: Unknown type encountered: {0}

Cause: Unknown type type encountered.

Action: See the generated exception for the root cause.
Level: 1

Type: ERROR

Impact: Programmatic

TOP-28001: A ValidationException was thrown while trying to create session: [{0}] . The most likely causes of this issue are that your [{1}] file is not available on the classpath or it does not contain a session called: [{0}].

Cause: A ValidationException was thrown while trying to create a session sessionName.

Action: Ensure that your fileName file is on the classpath. If it is on the classpath, ensure that this file contains the session sessionName.
Level: 1

Type: ERROR

Impact: Deployment

TOP-28002: TopLink is attempting to load a ServerSession named [{0}] from [{1}], and not getting a ServerSession.

Cause: Failure to load a ServerSession sessionName from sourceName.

Action: Ensure that the server session's type is correct.
Level: 1

Type: ERROR

Impact: Deployment

TOP-28003: TopLink has loaded Session [{0}] from [{1}] and it either does not have a server platform specified or specifies a server platform that does not use an external transaction controller. Please specify an appropriate server platform if you plan to use JTA.

Cause: Server platform specification was not found: TopLink has loaded a session sessionName from sourceName, but this session either does not have a server platform specified, or specifies a server platform that does not use an external transaction controller.

Action: If you plan to use JTA, specify an appropriate server platform.
Level: 1

Type: ERROR

Impact: Deployment

TOP-28004: Error in setup of EntityManager factory: JavaSECMPInitializer.initializeFromMain returned false.

Cause: Error while setting up an oracle.toplink.sessions.entitymanager.EntityManagerFactory.

Action: Ensure the correct setup of the EntityManagerFactory: initializeFromMain method of the EntityContainer returns true.
Level: 1

Type: ERROR

Impact: Deployment

TOP-28005: An Exception was thrown in setup of EntityManager factory.

Cause: Error during the setup of oracle.toplink.sessions.entitymanager.EntityManagerFactory.

Action: See the generated exception for the root cause.
Level: 1

Type: ERROR

Impact: Deployment

TOP-28006: ClassNotFound: [{0}] specified in [{1}] property.

Cause: Failure to find the class ClassName specified in the property propertyName.

Action: Ensure that the class exists and is on the classpath.
Level: 1

Type: ERROR

Impact: Deployment

TOP-28007: Failed to instantiate ServerPlatform of type [{0}] specified in [{1}] property.

Cause: Failure to instantiate a server platform of type ServerPlatformType specified in the property propertyName.

Action: See the generated exception for the root cause.
Level: 1

Type: ERROR

Impact: Deployment

TOP-72000: Error reading ejb-jar.xml file

Cause: Failure to read an ejb-jar.xml file due to a java.io.IOException or javax.xml.parsers.ParserConfigurationException.

Action: See the generated exception for the root cause.
Level: 1

Type: ERROR

Impact: Deployment

TOP-72001: ejb-jar.xml does not use expected doc type -//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN

Cause: Failure to parse the specified file because it did not use the expected doctype: -//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN

Action: Verify that your ejb-jar.xml file uses the correct documentation type.
Level: 1

Type: ERROR

Impact: Deployment

TOP-72002: There was a concrete instance variable named "{0}" already defined on the class "{1}". Please either 1) remove this instance variable from the class, refresh in the MW, and update from the ejb-jar.xml again, or 2) remove the field from the ejb-jar.xml file and update again.

Cause: There was a concrete instance variable variableName already defined on the class ClassName.

Action: Either remove this instance variable from the class, refresh in the TopLink Workbench, and update from the ejb-jar.xml file again, or remove the field from the ejb-jar.xml file and update again.
Level: 1

Type: ERROR

Impact: Deployment

TOP-72003: A mapping for the field named "{0}" could not be created on the descriptor "{1}". Check to see that there are abstract getters and setters accessible for this field.

Cause: A mapping for a field fieldName could not be created on the descriptor DescriptorName.

Action: Check to ensure that there are abstract get and set methods accessible for this field.
Level: 1

Type: ERROR

Impact: Deployment

TOP-72004: Neither local home nor remote home interface for the class "{0}" was found on the classpath. The finders for this class were not updated.

Cause: Neither local home nor remote home interface for the class ClassName was found on the classpath. The finders for this class were not updated.

Action: Update the finders for this class; ensure that either local home or remote home interface for the class is on the classpath.
Level: 1

Type: ERROR

Impact: Deployment

TOP-72005: The finder method named "{0}" was not defined on a home interface for the entity "{1}". The finder was not updated.

Cause: The finder method methodName was not defined on a home interface for the entity EntityName. The finder was not updated

Action: Define the finder method.
Level: 1

Type: ERROR

Impact: Deployment

TOP-72006: TopLink Mapping Workbench could not determine a project persistence type from the xml file.

Cause: TopLink Workbench could not determine a project persistence type from the XML file.

Action: Specify the persistence type for your TopLink project.
Level: 1

Type: ERROR

Impact: Deployment

TOP-72007: Could not find a corresponding ejbSelect method in the bean class: "{0}". No information was updated for this query.

Cause: Failure to find a corresponding ejbSelect method in the bean class ClassName. No information was updated for this query.

Action: Define ejbSelect method in your bean class.
Level: 1

Type: ERROR

Impact: Deployment

TOP-72008: The EJB descriptor, "{0}", must have an EJB name specified.

Cause: The EJB descriptor DescriptorName does not have an EJB name specified.

Action: In your EJB descriptor, specify an EJB name.
Level: 1

Type: ERROR

Impact: Deployment

TOP-72009: The EJB descriptor, "{0}", must have a primary key class specified.

Cause: The EJB descriptor DescriptorName does not have a primary key class specified.

Action: In your EJB descriptor, specify a primary key class.
Level: 1

Type: ERROR

Impact: Deployment

TOP-72010: The EJB name, "{0}", was used by more than one descriptor. EJB names must be unique.

Cause: The EJB name EJBName was used by more than one descriptor. EJB names must be unique.

Action: Ensure that the EJB name is specified in one and only one descriptor.
Level: 1

Type: ERROR

Impact: Deployment

TOP-72011: The element "{1}" cannot have an empty text attribute "{0}"

Cause: An element elementName has an empty text attribute attributeName.

Action: Use a non-empty text attribute for the subelement.
Level: 1

Type: ERROR

Impact: Deployment

TOP-72012: There were multiple entities with the ejb-name "{0}" in the xml file.

Cause: There are multiple entities with the same EJB bean name BeanName in the XML file.

Action: Use a unique EJB bean name for each entity.
Level: 1

Type: ERROR

Impact: Deployment

TOP-72013: The entity "{0}" did not have a valid cmp-version. The version must be "1.x" or "2.x".

Cause: The entity EntityName does not have a valid cmp-version definition. The cmp-version must be 1.x or 2.x.

Action: Use a cmp-version value of 1.x or 2.x only.
Level: 1

Type: ERROR

Impact: Deployment

TOP-72014: The ejb-name "{0}" in the ejb-relationship-role "{1}" is not found in any entity of the xml file

Cause: The EJB bean name BeanName in the ejb-relationship-role element is not found in the XML file.

Action: Use the EJB bean name of an existing entity for the ejb-relationship-role.
Level: 1

Type: ERROR

Impact: Deployment

TOP-72015: There was an invalid multiplicity in a relationship involving the mapping "{0}" in the descriptor "{1}". The multiplicity must be "One" or "Many".

Cause: There was an invalid multiplicity value defined for a relationship involving the mapping Mapping Name in a descriptor DescriptorName. The multiplicity must be either One or Many.

Action: Use a multiplicity value of One or Many only.
Level: 1

Type: ERROR

Impact: Deployment

TOP-72016: The entity "{0}" did not have a valid persistence-type. The type must be "Bean" or "Container".

Cause: The entity EntityName does not have a valid persistence type. The type must be either Bean or Container.

Action: Use a persistence-type value of Bean or Container only.
Level: 1

Type: ERROR

Impact: Deployment

TOP-72017: The query method-name "{0}" does not start with "find" or "ejbSelect". No information was updated for this query.

Cause: The query method methodName does not start with find or ejbSelect. No information was updated for this query.

Action: Verify that the query method name starts with either find or ejbSelect.
Level: 1

Type: ERROR

Impact: Deployment

TOP-72018: TopLink Mapping Workbench requires that all entities in the xml file for this project have the same persistence-type and/or cmp-version. The project will be set according to the persistence-type and/or cmp-version of the first entity in the file.

Cause: Attempt to use a nonuniform persistence type for the TopLink Workbench project: TopLink Workbench requires that all entities in the XML file for this project have the same persistence-type and/or cmp-version. The project will be set according to the persistence-type and/or cmp-version of the first entity in the file.

Action: Provide all entities in the XML file for this project with the same persistence-type and/or cmp-version.
Level: 1

Type: ERROR

Impact: Deployment

TOP-72019: The project, "{0}", must have at least one EJB descriptor.

Cause: The project ProjectName does not have an EJB descriptor: it must have at least one EJB descriptor.

Action: Provide an EJB descriptor for the project.
Level: 1

Type: ERROR

Impact: Deployment

TOP-72021: The class "{0}" could not be found on the classpath. A descriptor could not be created for it.

Cause: The class ClassName could not be found on the classpath. A descriptor could not be created for it.

Action: Ensure that the class ClassName is on the classpath.
Level: 1

Type: ERROR

Impact: Deployment

TOP-72022: There is an element, "{1}", that does not have a required attribute, "{0}".

Cause: There is an element that does not have a required attribute.

Action: Add the subelement to the parent element.
Level: 1

Type: ERROR

Impact: Deployment

TOP-72023: EntityBean {1} has an ABSTRACT setter with an EntityBean attribute type for attribute {0} but no corresponding CMR field.

Cause: Entity bean BeanName has an abstract setter method with an EntityBean attribute type for attribute attributeName, but does not have a corresponding CMR field.

Action: Verify that all CMP entities have the same cmp-version value.
Level: 1

Type: ERROR

Impact: Deployment

93 TPC-00001 to TPC-90022

TPC-00001: The document root cannot be deleted.

Cause: The user tried to delete the document root.

Action: Do not try to delete the document root.
Level: 1

Type: ERROR

Impact: Logging

TPC-00002: Failed to create folder "{0}".

Cause: The user does not have permission to create a folder.

Action: Check user permissions.
Level: 1

Type: ERROR

Impact: Logging

TPC-00003: Failed to create local directory "{0}".

Cause: The user does not have permission to create the local directory.

Action: Check user permissions.
Level: 1

Type: ERROR

Impact: Logging

TPC-00004: Failed to create team document directory item.

Cause: The user does not have permission to create documents.

Action: Check user permissions.
Level: 1

Type: ERROR

Impact: Logging

TPC-00005: Failed to delete team document.

Cause: The document has already been deleted or the user does not have permission.

Action: Verify document existence and check user permissions.
Level: 1

Type: ERROR

Impact: Logging

TPC-00006: Failed to download document "{0}".

Cause: The download failed because of connection failures or the user does not have permission.

Action: Verify connectivity and check user permissions.
Level: 1

Type: ERROR

Impact: Logging

TPC-00007: Failed to get document connector.

Cause: Failed to get an instance of the document connector.

Action: Verify connector installation and check user permissions.
Level: 1

Type: ERROR

Impact: Logging

TPC-00008: Failed to rename document item to "{0}".

Cause: The user does not have permission to rename documents.

Action: Check user permissions.
Level: 1

Type: ERROR

Impact: Logging

TPC-00009: Failed to show team document content.

Cause: The user does not have permissions to view the document.

Action: Check user permissions.
Level: 1

Type: ERROR

Impact: Logging

TPC-00010: Failed to upload team document.

Cause: The user does not have permissions to upload team documents.

Action: Check user permissions.
Level: 1

Type: ERROR

Impact: Logging

TPC-00011: Connector for "{0}" may not be properly installed. Use Check for Update to install or fix the problem.

Cause: The connector is not properly installed or the user does not have permission.

Action: Verify the connector installation and the user permissions.
Level: 1

Type: ERROR

Impact: Logging

TPC-00012: Work Item Connector Login Error.

Cause: The user could not log in to the connector.

Action: Ensure the user credentials are correct.
Level: 1

Type: ERROR

Impact: Logging

TPC-00013: Creating User Repository Error.

Cause: The user does not have permission to create a repository.

Action: Check user permissions.
Level: 1

Type: ERROR

Impact: Logging

TPC-00014: Failed to construct the connector.

Cause: The connector parameters are incorrect.

Action: Verify the connector parameters in the administration screen.
Level: 1

Type: ERROR

Impact: Logging

TPC-00015: Failed to log in to "{0}" repository.

Cause: Failed to access repository.

Action: Check connection and access permission.
Level: 1

Type: ERROR

Impact: Logging

TPC-00016: Missing the required user repository.

Cause: Miss the required user repository.

Action: Add needed user repository.
Level: 1

Type: ERROR

Impact: Logging

TPC-00017: No item has been found with the specified ID. Enter a valid ID value.

Cause: No item with the specified ID exists.

Action: Enter a valid ID value.
Level: 1

Type: ERROR

Impact: Logging

TPC-00018: Specify your username.

Cause: The username cannot be empty.

Action: Provide data for the username.
Level: 1

Type: ERROR

Impact: Logging

TPC-00019: Specify your password.

Cause: The password cannot be empty.

Action: Provide data for the password.
Level: 1

Type: ERROR

Impact: Logging

TPC-00020: Cannot save your account information to server. Contact your administrator.

Cause: There is an issue with server connectivity or user credentials.

Action: Contact your administrator.
Level: 1

Type: ERROR

Impact: Logging

TPC-00021: Update failed. Check field values and try again.

Cause: Invalid values for some fields.

Action: Verify field values and try again.
Level: 1

Type: ERROR

Impact: Logging

TPC-00022: Cannot delete a repository that is being used by any team(s). Make sure that no team is using the current repository.

Cause: The repository is being used by one or more teams.

Action: Remove the repository from all teams.
Level: 1

Type: ERROR

Impact: Logging

TPC-00023: Cannot save the new repository "{0}". Make sure its name is unique.

Cause: The repository name is not unique.

Action: Specify a unique repository name.
Level: 1

Type: ERROR

Impact: Logging

TPC-00024: Cannot update repository "{0}". Check your log file for details.

Cause: TPC server has encountered problem during updating the repository. Check the server's log to find out what has caused the problem.

Action: Check your log file for details.
Level: 1

Type: ERROR

Impact: Logging

TPC-00025: Create new repository error.

Cause: The repository parameters are incorrect.

Action: Verify the repository parameters.
Level: 1

Type: ERROR

Impact: Logging

TPC-00026: Delete repository error.

Cause: The user does not have permission to delete the repository.

Action: Check user permissions.
Level: 1

Type: ERROR

Impact: Logging

TPC-00027: Repository Access Error.

Cause: The user credentials may not be correct or there may be connectivity issues.

Action: Verify the user credentials and the connectivity of the repository.
Level: 1

Type: ERROR

Impact: Logging

TPC-00028: Repository field cannot be empty.

Cause: The repository name cannot be empty.

Action: Provide a name for the repository.
Level: 1

Type: ERROR

Impact: Logging

TPC-00029: Test failed.

Cause: The username and password are not correct.

Action: Provide a valid username and password.
Level: 1

Type: ERROR

Impact: Logging

TPC-00030: Update User Repository Account Failure.

Cause: Failed to update user repository account.

Action: Check account parameters.
Level: 1

Type: ERROR

Impact: Logging

TPC-00031: Repository field cannot be empty.

Cause: The repository field cannot be empty.

Action: Provide repository name.
Level: 1

Type: ERROR

Impact: Logging

TPC-00032: Update repository error.

Cause: The repository data is invalid.

Action: Verify the repository data.
Level: 1

Type: ERROR

Impact: Logging

TPC-00033: Repository server name cannot be changed once it is committed.

Cause: The repository server name cannot be changed once it is created.

Action: Do not change repository server name.
Level: 1

Type: ERROR

Impact: Logging

TPC-00034: Create repository server error.

Cause: The repository server parameter values are incorrect.

Action: Verify the parameter values.
Level: 1

Type: ERROR

Impact: Logging

TPC-00035: Rename repository server error

Cause: The repository server name is invalid.

Action: Verify the repository server name.
Level: 1

Type: ERROR

Impact: Logging

TPC-00036: Repository server "{0}" is already used. Choose a different name.

Cause: The specified repository server name is already in use.

Action: Choose a different name.
Level: 1

Type: ERROR

Impact: Logging

TPC-00037: Create new role error.

Cause: The role name is invalid.

Action: Verify that the name of the role is valid.
Level: 1

Type: ERROR

Impact: Logging

TPC-00038: Name field cannot be empty.

Cause: The name field cannot be empty.

Action: Enter data in name field.
Level: 1

Type: ERROR

Impact: Logging

TPC-00039: Failed to delete role.

Cause: The user does not have permission to delete the role.

Action: Check user permissions.
Level: 1

Type: ERROR

Impact: Logging

TPC-00040: Failed to delete role "{0}". Make sure no team member uses this role.

Cause: The role is already associated to some users.

Action: Remove the role from all users.
Level: 1

Type: ERROR

Impact: Logging

TPC-00041: You can only delete a team that does not have any member. Make sure there is no user associated with this team.

Cause: The team has members associated with it.

Action: Remove all members from the team in order to delete it.
Level: 1

Type: ERROR

Impact: Logging

TPC-00042: You can only delete a team that does not have any subteam. Make sure there is no team under this team.

Cause: The team has teams beneath it in the hierarchy.

Action: Remove all teams below the specified team.
Level: 1

Type: ERROR

Impact: Logging

TPC-00043: Cannot save the new team "{0}". Make sure its name is unique.

Cause: The team name is not unique.

Action: Enter a unique name for the team.
Level: 1

Type: ERROR

Impact: Logging

TPC-00044: Failed to Create Team.

Cause: Some data fields are invalid.

Action: Verify the team fields.
Level: 1

Type: ERROR

Impact: Logging

TPC-00045: Failed to Delete Team.

Cause: The user may not have permission to delete teams.

Action: Check user permissions.
Level: 1

Type: ERROR

Impact: Logging

TPC-00046: Team name cannot be empty.

Cause: The team name is empty.

Action: Provide a value for the team name.
Level: 1

Type: ERROR

Impact: Logging

TPC-00047: Create new team error.

Cause: Some data fields are invalid.

Action: Verify the team fields.
Level: 1

Type: ERROR

Impact: Logging

TPC-00048: Update team error.

Cause: Some data fields are invalid.

Action: Verify the team fields.
Level: 1

Type: ERROR

Impact: Logging

TPC-00049: Create new user error.

Cause: Some data fields are invalid.

Action: Verify the user fields.
Level: 1

Type: ERROR

Impact: Logging

TPC-00050: You can only delete a user that does not belong to any team. Make sure the current user is not associated with any team.

Cause: The specified user was associated with a team, so deletion was not allowed.

Action: Remove the user from all teams.
Level: 1

Type: ERROR

Impact: Logging

TPC-00051: Failed to Delete User.

Cause: The user did not have the permissions required to delete other users.

Action: Check user permissions.
Level: 1

Type: ERROR

Impact: Logging

TPC-00052: Username, password and email field cannot be empty.

Cause: Empty username, password or email field.

Action: Enter data for all fields.
Level: 1

Type: ERROR

Impact: Logging

TPC-00053: Login exists. Use different login.

Cause: The login ID already exists.

Action: Provide a unique login ID.
Level: 1

Type: ERROR

Impact: Logging

TPC-00054: Failed to open file "{0}".

Cause: The connection failed or the user does not have permission.

Action: Verify connectivity and check user permissions.
Level: 1

Type: ERROR

Impact: Logging

TPC-00055: Failed to change Team Server password.

Cause: Server connectivity issue.

Action: Verify server connectivity or contact your administrator.
Level: 1

Type: ERROR

Impact: Logging

TPC-00056: The new password does not match the retyped password.

Cause: The new password does not match the retyped password.

Action: Verify the passwords entered.
Level: 1

Type: ERROR

Impact: Logging

TPC-00057: The old password entered is incorrect.

Cause: The old password entered is incorrect.

Action: Provide the correct password.
Level: 1

Type: ERROR

Impact: Logging

TPC-00058: Failed to create buddy "{0}".

Cause: Server connectivity issue.

Action: Verify server connectivity or contact your administrator.
Level: 1

Type: ERROR

Impact: Logging

TPC-00059: Buddy "{0}" already exists.

Cause: The specified buddy already exists.

Action: Refresh your buddy list.
Level: 1

Type: ERROR

Impact: Logging

TPC-00060: Fail to create group "{0}" on the server.

Cause: Server connectivity issue or the group name is invalid.

Action: Verify server connectivity and verify that the group name is valid.
Level: 1

Type: ERROR

Impact: Logging

TPC-00061: Make sure you enter a valid account name before clicking the Add button.

Cause: The account name is invalid.

Action: Verify the account name.
Level: 1

Type: ERROR

Impact: Logging

TPC-00062: Failed to connect to chat server "{0}".

Cause: The connection information is incorrect.

Action: Verify the connection information.
Level: 1

Type: ERROR

Impact: Logging

TPC-00063: Failed to log in to chat server "{0}".

Cause: The login credentials are incorrect.

Action: Verify the login credentials and connection information.
Level: 1

Type: ERROR

Impact: Logging

TPC-00064: Failed to save the work item.

Cause: Some of the workitem field values are invalid.

Action: Verify the input data.
Level: 1

Type: ERROR

Impact: Logging

TPC-00065: Failed to update password.

Cause: The password is invalid.

Action: Ensure the password is 12 characters or less.
Level: 1

Type: ERROR

Impact: Session

TPC-00066: Failed to log in to team server.

Cause: The login credentials are incorrect.

Action: Verify the login credentials.
Level: 1

Type: ERROR

Impact: Session

TPC-00067: Invalid username and/or password.

Cause: Invalid username and/or password.

Action: Verify the login name and password.
Level: 1

Type: ERROR

Impact: Session

TPC-00068: Invalid server name and/or server port.

Cause: Invalid server name and/or server port.

Action: Verify the server name and/or server port.
Level: 1

Type: ERROR

Impact: Logging

TPC-00069: Failed to update query "{0}".

Cause: The query specification is incorrect.

Action: Verify the query fields are valid.
Level: 1

Type: ERROR

Impact: Logging

TPC-00070: Failed to create new query "{0}".

Cause: The query specification is incorrect.

Action: Verify the query fields are valid.
Level: 1

Type: ERROR

Impact: Logging

TPC-00071: Cannot save the query. Make sure the query is valid.

Cause: The query specification is incorrect.

Action: Verify the query fields are valid.
Level: 1

Type: ERROR

Impact: Logging

TPC-00072: Query "{0}" already exists. Provide another name.

Cause: The specified query already exists.

Action: Provide a unique name for the query.
Level: 1

Type: ERROR

Impact: Logging

TPC-00073: Duplicate Tag Name Error.

Cause: The tag name already exists.

Action: Provide a unique name for the tag.
Level: 1

Type: ERROR

Impact: Logging

TPC-00074: Failed to add tag to the current work item.

Cause: Connectivity issue.

Action: Verify connectivity or contact your administrator.
Level: 1

Type: ERROR

Impact: Logging

TPC-00075: Failed to create new tag.

Cause: The user does not have permission to create new tags.

Action: Check user permissions.
Level: 1

Type: ERROR

Impact: Logging

TPC-00076: Missing Required Information.

Cause: Missing Required Information.

Action: Provide tag name and description.
Level: 1

Type: ERROR

Impact: Logging

TPC-00077: Tag "{0}" already exists.

Cause: The tag name already exists.

Action: Provide a unique tag name.
Level: 1

Type: ERROR

Impact: Logging

TPC-00078: No result found. Either the tag used has been changed or there is no item associated with the tag. Close this window and try again.

Cause: The tag used has been changed or there is no item associated with the tag.

Action: Select a different tag.
Level: 1

Type: ERROR

Impact: Logging

TPC-00079: Failed to delete the context.

Cause: Connectivity issue.

Action: Verify server connectivity or contact your administrator.
Level: 1

Type: ERROR

Impact: Logging

TPC-00080: There is no context being saved.

Cause: There are no open files to be saved to the context.

Action: Open files in the editor and then save the context.
Level: 1

Type: ERROR

Impact: Logging

TPC-00081: Failed to update the context.

Cause: The context files may not be present in the local file system.

Action: Restore the file system or delete the context.
Level: 1

Type: ERROR

Impact: Logging

TPC-00082: Restore context exception: "{0}".

Cause: An error was encountered during restoring the context. Detailed exception should have been provided in the message dialog.

Action: Check the log files.
Level: 1

Type: ERROR

Impact: Logging

TPC-00083: Cannot retrieve context.

Cause: The context was not properly stored.

Action: Delete the context and reopen the files manually.
Level: 1

Type: ERROR

Impact: Logging

TPC-00084: Save context exception: "{0}".

Cause: An error was encountered during saving the context. Detailed exception should have been provided in the message dialog.

Action: Check the log files.
Level: 1

Type: ERROR

Impact: Logging

TPC-00085: Cannot find document "{0}" to add.

Cause: The document may have been removed from the content store.

Action: Verify the document exists in the content store and contact your administrator.
Level: 1

Type: ERROR

Impact: Logging

TPC-00086: Failed to download attachment "{0}".

Cause: Connectivity issue.

Action: Verify the connectivity and retry or contact your administrator.
Level: 1

Type: ERROR

Impact: Logging

TPC-00087: Failed to update attachment "{0}".

Cause: Connectivity issue.

Action: Verify the connectivity and retry or contact your administrator.
Level: 1

Type: ERROR

Impact: Logging

TPC-00088: Failed to update attributes on attachment "{0}". Error: {1}.

Cause: Connectivity issue.

Action: Verify the connectivity and retry or contact your administrator.
Level: 1

Type: ERROR

Impact: Logging

TPC-00089: Failed to upload attachment "{0}". Error: {1}.

Cause: Connectivity issues or the upload directory is not properly set.

Action: Verify the connectivity and the upload directory.
Level: 1

Type: ERROR

Impact: Logging

TPC-00090: Cannot create the work item relationship.

Cause: Connectivity issues or the specified work item does not exist.

Action: Verify the connectivity and ensure the work item specified was not deleted.
Level: 1

Type: ERROR

Impact: Logging

TPC-00091: Connector "{0}" is installed but its version "{1}" is not supported. Supported version is "{2}" or lower.

Cause: Connector versions mismatched.

Action: Use only supported version of the client connector.
Level: 1

Type: ERROR

Impact: Logging

TPC-00092: Cannot update team query "{0}".

Cause: User may not have permission to update team query.

Action: Check permission to update team query.
Level: 1

Type: ERROR

Impact: Logging

TPC-00093: You can only delete a team that does not have any repository. Make sure there is no repository associated with this team.

Cause: The team has repositories associated with it.

Action: Remove all repositories from the team in order to delete it.
Level: 1

Type: ERROR

Impact: Logging

TPC-00094: Failed to Update User.

Cause: The user does not have permissions to update this user.

Action: Check user permissions.
Level: 1

Type: ERROR

Impact: Logging

TPC-00095: Failed to delete team member "{0}".

Cause: The team member may be in use.

Action: Remove all associations to the team member.
Level: 1

Type: ERROR

Impact: Logging

TPC-00096: Failed to delete team repository for team "{0}" using repository "{1}".

Cause: The user does not have permissions to update the team repository.

Action: Check user permissions.
Level: 1

Type: ERROR

Impact: Logging

TPC-00097: Failed to create team repository for team "{0}" using repository "{1}".

Cause: The user does not have permissions to create the team repository.

Action: Check user permissions.
Level: 1

Type: ERROR

Impact: Logging

TPC-00098: Failed to delete team parameter for team "{0}" using repository "{1}".

Cause: The user does not have permissions to delete the parameter.

Action: Check user permissions.
Level: 1

Type: ERROR

Impact: Logging

TPC-00099: Failed to update team parameter for team "{0}" using repository "{1}".

Cause: The user does not have permissions to update the parameter.

Action: Check user permissions.
Level: 1

Type: ERROR

Impact: Logging

TPC-00100: Failed to create team member "{0}".

Cause: Some required property of the team member may be missing.

Action: Make sure the user associated with the team member is specified correctly.
Level: 1

Type: ERROR

Impact: Logging

TPC-00101: Cannot grant privilege "{0}" to role "{1}". Make sure it does not exist.

Cause: The association is not unique.

Action: Specify a unique association for the role.
Level: 1

Type: ERROR

Impact: Logging

TPC-00102: Cannot revoke privilege "{0}" from role "{1}". Make sure it exists.

Cause: The association may not exist.

Action: Specify correct association to delete. This may be an error in the application.
Level: 1

Type: ERROR

Impact: Logging

TPC-00103: Cannot update privilege "{0}" for role "{1}".

Cause: The association may not exist.

Action: Specify correct association to update. This may be an error in the application.
Level: 1

Type: ERROR

Impact: Logging

TPC-00104: Cannot create role "{0}".

Cause: The role may exist.

Action: Specify unique role to create.
Level: 1

Type: ERROR

Impact: Logging

TPC-00105: Cannot update role "{0}".

Cause: The role may not exist.

Action: Specify correct role to update. This may be an error in the application.
Level: 1

Type: ERROR

Impact: Logging

TPC-00106: Cannot grant privilege "{0}" for login "{1}".

Cause: The association is not unique.

Action: Specify a unique association for the login.
Level: 1

Type: ERROR

Impact: Logging

TPC-00107: Cannot revoke privilege "{0}" from login "{1}".

Cause: The association may not exist or the login may not exist.

Action: Specify correct login.
Level: 1

Type: ERROR

Impact: Logging

TPC-00108: Cannot update team "{0}".

Cause: The team information may not be specified properly.

Action: Specify correct team information.
Level: 1

Type: ERROR

Impact: Logging

TPC-00109: Cannot delete team "{0}".

Cause: The team may not exist.

Action: Specify correct team.
Level: 1

Type: ERROR

Impact: Logging

TPC-00110: Invalid email address. Specify valid email address.

Cause: Email address specified is invalid.

Action: Specify valid email address.
Level: 1

Type: ERROR

Impact: Logging

TPC-00111: You have lost connection to TPC server. "{0}" Fix the problem and retry.

Cause: You have lost connection to the server for the reason mentioned.

Action: Log in to TPC server.
Level: 1

Type: ERROR

Impact: Logging

TPC-00112: Server did not send valid certificate.

Cause: Invalid certificate from server caused by the specified reason.

Action: Verify that you have specified correct server name and/or server port.
Level: 1

Type: ERROR

Impact: Logging

TPC-00113: You need a valid certificate to log in.

Cause: User rejected a certificate sent by TPC server. The certificate is needed in SSL connection mode.

Action: Verify and accept the certificate before you connect.
Level: 1

Type: ERROR

Impact: Logging

TPC-00114: Unexpected problem during accepting the certificate. Try again.

Cause: The certificate is either empty or there was a problem in accepting the certificate.

Action: Verify and accept the certificate again.
Level: 1

Type: ERROR

Impact: Logging

TPC-00115: Failed to delete attachment "{0}". Error: {1}.

Cause: The specified attachment cannot be found in the content store.

Action: Verify the document exists in the content store and contact your administrator.
Level: 1

Type: ERROR

Impact: Logging

TPC-00116: Password cannot be reused.

Cause: The old password cannot be reused.

Action: Specify password different than the old one.
Level: 1

Type: ERROR

Impact: Logging

TPC-00117: You must specify a new password to commit. Click Cancel otherwise.

Cause: You either did not type in a new password or specify a blank new password.

Action: Specify a new password to commit and it cannot be blank. Hit Cancel otherwise.
Level: 1

Type: ERROR

Impact: Logging

TPC-00118: User canceled.

Cause: User has canceled login.

Action: None.
Level: 1

Type: ERROR

Impact: Logging

TPC-00119: Unable to establish connection with server using this url: {0}.

Cause: Failed to log in to specified server URL.

Action: Specify correct server URL.
Level: 1

Type: ERROR

Impact: Logging

TPC-00120: Value is required for "{0}".

Cause: Value for the specific input field is required but it has not been provided

Action: Specify value for the field
Level: 1

Type: ERROR

Impact: Logging

TPC-00121: Invalid value for "{0}". Value should be a type of "{0}".

Cause: An incorrect type of value was specified.

Action: Specify correct value.
Level: 1

Type: ERROR

Impact: Logging

TPC-00122: Password for "{0}" is not valid after the login was renamed. Make sure you reset the password.

Cause: The user's login was renamed. Its password is no longer valid

Action: Reset the password for the login.
Level: 1

Type: WARNING

Impact: Logging

TPC-00123: Repository name cannot contain any of these characters: #/\?

Cause: The repository name contains specified invalid character(s)

Action: Provide valid repository name.
Level: 1

Type: ERROR

Impact: Logging

TPC-00128: Query name cannot contain any of these characters: #/\?

Cause: The query name contains specified invalid character(s)

Action: Provide valid query name.
Level: 1

Type: ERROR

Impact: Logging

TPC-00129: Tag name cannot contain any of these characters: #/\?

Cause: The tag name contains specified invalid character(s)

Action: Provide valid tag name.
Level: 1

Type: ERROR

Impact: Logging

TPC-00130: Your client version "{0}" is currently not compatible with TPC server version "{1}". Download a patch to fix this problem.

Cause: You need to install a TPC patch to fix this issue.

Action: Contact Oracle Support if the patch is not available.
Level: 1

Type: ERROR

Impact: Logging

TPC-00131: Dependent field(s) "{0}" need input value(s).

Cause: Vvalues of the dependent fields are missing.

Action: Provide value(s) for the dependent fields.
Level: 1

Type: ERROR

Impact: Logging

TPC-60000: Team Productivity Center services initialized.

Cause: Service started normally.

Action: No action needed.
Level: 1

Type: NOTIFICATION

Impact: Threads

TPC-60001: Cannot insert record with blank ID.

Cause: The record has a blank ID.

Action: Enter a value for the ID.
Level: 1

Type: WARNING

Impact: Threads

TPC-60002: The record you want to update does not exist.

Cause: The record does not exist.

Action: Refresh your data.
Level: 1

Type: WARNING

Impact: Threads

TPC-60003: Cannot retrieve a record with a null ID.

Cause: The ID is null.

Action: Make sure the record has a valid ID.
Level: 1

Type: ERROR

Impact: Threads

TPC-60004: Cannot retrieve a record with a null name.

Cause: The Item name is null.

Action: Make sure the record has a valid name.
Level: 1

Type: ERROR

Impact: Threads

TPC-60005: Cannot create a record with a null or empty password.

Cause: Password for this record is either null or empty.

Action: Make sure the record has a valid password.
Level: 1

Type: ERROR

Impact: Threads

TPC-60006: Username or password is invalid.

Cause: Invalid username and/or password.

Action: Verify the login name and password.
Level: 1

Type: ERROR

Impact: Threads

TPC-60007: Team Productivity Center services failed to start.

Cause: Cannot find required startup credentials.

Action: Verify the server was installed correctly.
Level: 1

Type: ERROR

Impact: Threads

TPC-60008: Cannot delete record.

Cause: The server received an error during deletion of the record.

Action: Verify the record is not being used by others.
Level: 1

Type: ERROR

Impact: Threads

TPC-60009: Cannot connect to an inactive account.

Cause: You are trying to connect using account that has been deactivated.

Action: Contact TPC Administrator to activate it.
Level: 1

Type: ERROR

Impact: Threads

TPC-60010: TPC Server requires authentication for this request. Authenticate with the server, or upgrade your client to fix the problem.

Cause: You either did not authenticate with the server, or your client version is no longer supported by the server.

Action: Authenticate with the server, or upgrade your client to correct the problem.
Level: 1

Type: ERROR

Impact: Threads

TPC-60011: Cannot initialize session in the webservice context.

Cause: Internal error on the server.

Action: Contact TPC Administrator.
Level: 1

Type: ERROR

Impact: Threads

TPC-60012: This request is not supported by the server.

Cause: You have requested a service that is not supported by the server.

Action: Contact TPC Administrator.
Level: 1

Type: ERROR

Impact: Threads

TPC-60013: TPC client version "{0}" is not supported. Supported version is "{1}" or higher. Use Check for Update to upgrade your client.

Cause: Client and Server versions mismatched.

Action: Use Check for Update to upgrade the client.
Level: 1

Type: ERROR

Impact: Logging

TPC-60014: This client is no longer supported. Use Check for Update to install or upgrade TPC client to "{0}" or higher to fix the problem.

Cause: Your client is not recognized by the server either because it is invalid or no longer supported.

Action: Use Check for Update to install or upgrade the TPC client.
Level: 1

Type: ERROR

Impact: Logging

TPC-60015: Server version does not exist.

Cause: This is an internal error caused by missing a server version from the database.

Action: Contact TPC Administrator.
Level: 1

Type: ERROR

Impact: Logging

TPC-60016: TPC Server has terminated your session. Relogin to fix the problem.

Cause: TPC server has terminated client session either unexpectedly or for scheduled maintenance.

Action: Relogin to the server once it becomes available again. Contact TPC Administrator for the availability of the server.
Level: 1

Type: ERROR

Impact: Threads

TPC-60017: Service is about to shut down...

Cause: One of the TPC service is about to shut down.

Action: Save all works and log off.
Level: 1

Type: ERROR

Impact: Threads

TPC-60041: TPC server version "{0}" is not valid. Expected at least in this format: #.#.#.#

Cause: This is an internal error caused by invalid server version recorded on the database.

Action: Contact TPC Administrator.
Level: 1

Type: ERROR

Impact: Logging

TPC-60042: TPC client version "{0}" is not valid. Expected at least in this format: #.#.#.#

Cause: This is an internal error caused by invalid client version.

Action: Correct your TPC client installation. You can do this by removing the old one then reinstall, or install correct TPC client to another JDeveloper client.
Level: 1

Type: ERROR

Impact: Logging

TPC-60043: Your client version "{0}" is newer than your TPC server version "{1}". The server supports clients begining with version "{2}" or lower. Use either a supported client or upgrade the server to fix the problem.

Cause: Your client has a newer version which is not supported by your server.

Action: Use either a supported client or upgrade the server to fix the problem.
Level: 1

Type: ERROR

Impact: Logging

TPC-60044: Your client version "{0}" is currently not compatible with TPC server version "{1}". Download a patch to fix this problem.

Cause: You need to install a TPC patch to fix this issue.

Action: Contact Oracle Support if the patch is not available.
Level: 1

Type: ERROR

Impact: Logging

TPC-90001: Test failed. Make sure your username and password are correct.

Cause: Test failed.

Action: Make sure your username and password are correct.
Level: 1

Type: ERROR

Impact: Logging

TPC-90002: Cannot create connector record in the target database. Make sure the specified connector jar or bundle file is correct.

Cause: Cannot create connector record in the target database.

Action: Make sure the specified connector jar or bundle file is correct.
Level: 1

Type: ERROR

Impact: Logging

TPC-90003: Incorrect connector definition. Check the connector.xml file and make sure all required parameters are defined correctly.

Cause: Incorrect connector definition.

Action: Check the connector.xml file and make sure all required parameters are defined correctly.
Level: 1

Type: ERROR

Impact: Logging

TPC-90004: The local file name specified is not a jar or zip file. Select the correct file.

Cause: The local file name specified is not a jar or zip file.

Action: Select the correct file.
Level: 1

Type: ERROR

Impact: Logging

TPC-90005: Cannot find the file to install the selected connector.

Cause: Cannot find the file to install the selected connector.

Action: Make sure connector jar files are properly located.
Level: 1

Type: ERROR

Impact: Logging

TPC-90006: Cannot copy otpc.war file. Make sure the destination folder is not read only.

Cause: Cannot copy otpc.war file.

Action: Make sure the destination folder is not read only.
Level: 1

Type: ERROR

Impact: Logging

TPC-90007: Failed to create temporary directory.

Cause: Failed to create temporary directory.

Action: Check permission and space to create installation directory.
Level: 1

Type: ERROR

Impact: Logging

TPC-90008: Failed to deploy Team Productivity Center server.

Cause: Failed to deploy Team Productivity Center server.

Action: Check permission and space for deployment directory.
Level: 1

Type: ERROR

Impact: Logging

TPC-90009: Failed to install the selected connector.

Cause: Failed to install the selected connector.

Action: Check permission and space for installation directory and file.
Level: 1

Type: ERROR

Impact: Logging

TPC-90010: Installation failed. Review the system log.

Cause: Installation failed.

Action: Review the system log.
Level: 1

Type: ERROR

Impact: Logging

TPC-90011: The specified application server directory is not valid. Make sure the folder exists and is writable.

Cause: The specified Application Server directory is not valid.

Action: Make sure the folder exists and is writable.
Level: 1

Type: ERROR

Impact: Logging

TPC-90012: The otpc.war file specified does not function properly. The install image may be corrupted. Download a working copy of the installer.

Cause: The otpc.war file specified does not function properly.

Action: The install image may be corrupted. Download a working copy of the installer.
Level: 1

Type: ERROR

Impact: Logging

TPC-90013: JDBC Driver library path is not correct.

Cause: JDBC Driver library path is not correct.

Action: Corrrect JDBC Driver library path.
Level: 1

Type: ERROR

Impact: Logging

TPC-90014: Falied to add JDBC driver library to system class path.

Cause: Falied to add JDBC driver library to system class path.

Action: Review system log.
Level: 1

Type: ERROR

Impact: Logging

TPC-90015: JDBC driver class cannot be found.

Cause: JDBC driver class cannot be found.

Action: Make sure jdbc driver class is in appropriate jar file.
Level: 1

Type: ERROR

Impact: Logging

TPC-90016: No component has been selected. Select the components to install.

Cause: No component has been selected.

Action: Select the components to install.
Level: 1

Type: ERROR

Impact: Logging

TPC-90017: SQL Exception.

Cause: SQL Exception.

Action: Check system log.
Level: 1

Type: ERROR

Impact: Logging

TPC-90018: Cannot create database tables or populate seed data. Review the system log.

Cause: Cannot create database tables or populate seed data.

Action: Review the system log.
Level: 1

Type: ERROR

Impact: Logging

TPC-90019: Cannot connect to the specified database. Make sure all parameters are set correctly.

Cause: Cannot connect to the specified database.

Action: Make sure all parameters are set correctly.
Level: 1

Type: ERROR

Impact: Logging

TPC-90020: The file otpc.war already exists and cannot be overwritten. Make sure it is overwritable.

Cause: The file otpc.war already exists and cannot be overwritten.

Action: Make sure otpc.war is overwritable.
Level: 1

Type: ERROR

Impact: Logging

TPC-90021: Update failed. Check field values and try again.

Cause: Update failed.

Action: Check field values and try again.
Level: 1

Type: ERROR

Impact: Logging

TPC-90022: The version to be installed "{0}" is not newer than the current version "{0}".

Cause: The version for installation or upgrade is the same or lower than the current installation.

Action: Check for new version.
Level: 1

Type: ERROR

Impact: Logging

94 TRS-10000 to TRS-30030

TRS-10000: TRSConnectionMgr: DataSource is null.

Cause: DataSource is not set.

Action: Set DataSource first using MBeans.
Level: 1

Type: ERROR

Impact: Configuration

TRS-10001: Dispatcher failed to get jobs. {0}

Cause: SQLException

Action: Check database.
Level: 1

Type: ERROR

Impact: Data

TRS-10002: {0} failed to check job status. {1}

Cause: SQLException

Action: Check database
Level: 1

Type: ERROR

Impact: Data

TRS-10003: TxnReplayer URL:{0} is malformed. Replay item cannot be processed. {1}

Cause: Malformed TxnReplayer URL

Action: Change TxnReplayer URL specified in MBean or web.xml
Level: 1

Type: ERROR

Impact: Configuration

TRS-10004: Cannot open TxnReplayer URL:{0}. Replay item cannot be processed. {1}

Cause: TxnReplayer might not be running

Action: Check network. Make sure TxnReplayer is running
Level: 1

Type: ERROR

Impact: Network

TRS-10005: Dispatcher encountered an error during update of the REPLAY_USERS table. {0}

Cause: SQLException

Action: Check database
Level: 1

Type: ERROR

Impact: Data

TRS-10006: JOB FAILED: clientId = {0}, JobId ={1}.

Cause: Job might be hanging or crashed.

Action: Consult administrator.
Level: 1

Type: ERROR

Impact: Data

TRS-10007: {0} failed to get database connection.

Cause: Database related

Action: Check database, or check DataSource.
Level: 1

Type: ERROR

Impact: Data

TRS-10008: Dispatcher failed to prepare SQL Statement. {0}

Cause: SQLException

Action: Check database
Level: 1

Type: ERROR

Impact: Data

TRS-10009: Error creating DispatcherRuntimeInfo MBean. {0}

Cause: Open MBean metadata information cannot be constructed.

Action: Check MBean validity constraints.
Level: 1

Type: ERROR

Impact: Data

TRS-10010: Data source name: {0} cannot be resolved. Dispatcher thread will not start

Cause: Cannot resolve DataSource name

Action: Check DataSource name
Level: 1

Type: ERROR

Impact: Configuration

TRS-10011: {0} - error registering. {1}

Cause: MBean might already exist, or other reasons

Action: Ignore if MBean already exists. Otherwise consult administrator.
Level: 1

Type: ERROR

Impact: Data

TRS-10012: {0} - error querying number of jobs. {1}

Cause: SQLException

Action: Check database
Level: 1

Type: ERROR

Impact: Data

TRS-10013: {0} - error closing resultset. {1}

Cause: SQLException

Action: Check database
Level: 1

Type: ERROR

Impact: Data

TRS-10014: {0} - error closing statement. {1}

Cause: SQLException

Action: Check database
Level: 1

Type: ERROR

Impact: Data

TRS-10015: {0} - error querying replay items. {1}

Cause: SQLException

Action: Check database
Level: 1

Type: ERROR

Impact: Data

TRS-10016: {0} - error querying replay users. {1}

Cause: SQLException

Action: Check database
Level: 1

Type: ERROR

Impact: Data

TRS-10017: {0} - error querying replay types. {1}

Cause: SQLException

Action: Check database
Level: 1

Type: ERROR

Impact: Data

TRS-10018: DispatcherRuntimeInfo - error creating composite item. {0}

Cause: Open MBean related OpenDataException

Action: Consult administrator
Level: 1

Type: ERROR

Impact: Data

TRS-10019: DispatcherRuntimeInfo - error creating composite job. {0}

Cause: Open MBean related OpenDataException

Action: Consult administrator
Level: 1

Type: ERROR

Impact: Data

TRS-10020: {0} - error inserting replay type. {1}

Cause: SQLException

Action: Check database
Level: 1

Type: ERROR

Impact: Data

TRS-10021: {0} - error updating replay type. {1}

Cause: SQLException

Action: Check database
Level: 1

Type: ERROR

Impact: Data

TRS-10022: {0} - error removing replay items. {1}

Cause: SQLException

Action: Check database
Level: 1

Type: ERROR

Impact: Data

TRS-10023: {0} - error removing replay jobs. {1}

Cause: SQLException

Action: Check database
Level: 1

Type: ERROR

Impact: Data

TRS-10024: {0} - error removing replay users. {1}

Cause: SQLException

Action: Check database
Level: 1

Type: ERROR

Impact: Data

TRS-10025: {0} - error in database connection operations: commit, rollback or setAutoCommit. {1}

Cause: SQLException

Action: Check database
Level: 1

Type: ERROR

Impact: Data

TRS-10026: {0} - error loading settings. {1}

Cause: Error related to preference node

Action: Consult administrator
Level: 1

Type: ERROR

Impact: Data

TRS-10027: {0} - Cannot resolve DataSource Name {1}.

Cause: Cannot resolve DataSource

Action: Check DataSource name
Level: 1

Type: ERROR

Impact: Configuration

TRS-10028: {0} - DataSource name is null

Cause: DataSource name is null

Action: Check DataSource name in MBean or web.xml
Level: 1

Type: ERROR

Impact: Configuration

TRS-10029: {0} - error inserting replay items. {1}

Cause: SQLException

Action: Check database
Level: 1

Type: ERROR

Impact: Data

TRS-10030: {0} - Cannot find keystore password from Credential Store.

Cause: Cannot find keystore password

Action: Consult administrator
Level: 1

Type: ERROR

Impact: Security

TRS-10031: TRSConnectionMgr: fail to get database connection. {0}

Cause: SQLException

Action: Check database
Level: 1

Type: ERROR

Impact: Data

TRS-10032: Cannot access Credential Store.

Cause: Credential store is not existing

Action: Consult administrator
Level: 1

Type: ERROR

Impact: Security

TRS-10033: Fail to get private key.

Cause: cannot get private key

Action: Check keystore, keystore password, certificate alias.
Level: 1

Type: ERROR

Impact: Security

TRS-10034: Client {0}, Replay item #{1}: Cannot update item status to {2}. {3}

Cause: SQLException

Action: Check database
Level: 1

Type: ERROR

Impact: Data

TRS-10035: Client {0}, Replay item #{1}: Dependency not met. Parent item #{2} status is {3}.

Cause: Parent item status is not DONE

Action: Check parent item status
Level: 1

Type: ERROR

Impact: Data

TRS-10036: Client {0}, Replay item #{1}: Invalid Dependency #{2}.

Cause: DEPENDENCY value is not valid

Action: Check DEPENDENCY column for this item in table
Level: 1

Type: ERROR

Impact: Data

TRS-10037: Client {0}, Replay item #{1}: Fail to parse parameter. {2}

Cause: Cannot parse xml parameter

Action: Check PARAMS column for this item in table
Level: 1

Type: ERROR

Impact: Data

TRS-10038: Client {0}, Replay item #{1}: Error in retrieving password. {2}

Cause: Cannot get user's password

Action: Check security configuration
Level: 1

Type: ERROR

Impact: Security

TRS-10039: Client {0}, Replay item #{1}: Cannot find replay type class. {2}

Cause: Replay type class is missing

Action: Check to make sure the class library is available
Level: 1

Type: ERROR

Impact: Data

TRS-10040: Client {0}, Replay item #{1}: Cannot instantiate replay type class. {2}

Cause: Replay type class cannot be instantiated

Action: Class might be an interface or abstract
Level: 1

Type: ERROR

Impact: Data

TRS-10041: Client {0}, Replay item #{1}: Cannot find method with the right signature. {2}

Cause: No method available with the specified signature

Action: Check parameter provided in REPLAY_ITEM table
Level: 1

Type: ERROR

Impact: Data

TRS-10042: Client {0}, Replay item #{1}: Invocation access failure. {2}

Cause: Replay type method cannot be invoked

Action: The method does not have access to the definition of the specified class, field, method or constructor
Level: 1

Type: ERROR

Impact: Data

TRS-10043: Client {0}, Replay item #{1}, Calling Method = {2}, Class = {3}, Parameters = {4}: Invocation target failure. {5}

Cause: Replay type class cannot be invoked

Action: The invoked method throws an exception
Level: 1

Type: ERROR

Impact: Data

TRS-10044: Client {0}, Replay item #{1}: Unexpected exception. {2}

Cause: not known

Action: Check the error stack
Level: 1

Type: ERROR

Impact: Data

TRS-10045: Client {0}, Replay item #{1}: Unexpected error. {2}

Cause: not known

Action: Check the error stack
Level: 1

Type: ERROR

Impact: Data

TRS-10046: Query pending replay items for client {0} failed. {1}

Cause: SQLException

Action: Check database
Level: 1

Type: ERROR

Impact: Data

TRS-10047: Job #{0} for client {1} caught unexpected exception - {2}

Cause: The job is possibly determined dead by dispatcher or it has encountered other errors.

Action: Check the error stack
Level: 1

Type: ERROR

Impact: Data

TRS-10048: Cannot update job status to {0} for job id {1}.

Cause: SQLException

Action: Check database
Level: 1

Type: ERROR

Impact: Data

TRS-10049: Public key encryption is not set up properly. The feature is disabled.

Cause: Encryption configuration is not set up properly.

Action: Check public key encryption setup.
Level: 1

Type: ERROR

Impact: Security

TRS-10050: Default schema has not been set for user {0}, job {1}.

Cause: no default schema

Action: Set default schema in MBean
Level: 1

Type: ERROR

Impact: Configuration

TRS-10051: Caught RejectedExecutionException for user {0}, job {1}.

Cause: The job cannot be accepted for execution.

Action: Check thread pool
Level: 1

Type: ERROR

Impact: Configuration

TRS-10052: Thread pool is shut down for user {0}, job {1}.

Cause: Thread pool is shut down.

Action: Restart application.
Level: 1

Type: ERROR

Impact: Threads

TRS-10053: Missing ResourceBundle: {0}.

Cause: ResourceBundle is missing

Action: Check if resourcebundle is available
Level: 1

Type: ERROR

Impact: Data

TRS-10054: Client {0}, Replay item #{1}: Error processing the item.

Cause: Exception happened during processing this item

Action: Check log for errors logged before
Level: 1

Type: ERROR

Impact: Data

TRS-10055: Query outstanding replay items for client {0} failed. {1}

Cause: SQLException

Action: Check database
Level: 1

Type: ERROR

Impact: Data

TRS-10056: Worker servlet detects job {0} for client {1} has unexpected status. The job is not executed.

Cause: The job is determined dead by dispatcher, so it is not executed.

Action: Adjust failure recovery timeout if this error happens very frequently.
Level: 1

Type: ERROR

Impact: Data

TRS-10057: {0}: Failed to enable auto archive of replay jobs and replay items. {1}

Cause: IllegalArgumentException

Action: Check auto archive attributes
Level: 1

Type: ERROR

Impact: Data

TRS-10058: {0}: Failed to disable auto archive of replay jobs and replay items. {1}

Cause: IllegalArgumentException

Action: Make sure auto archive was previously enabled
Level: 1

Type: ERROR

Impact: Data

TRS-10059: Failed to create archive file {0}. {1}

Cause: Exception happened during creation of archive file

Action: Check database and make sure disk is not full
Level: 1

Type: ERROR

Impact: Data

TRS-10060: Failed to get value of attribute {0}.

Cause: Failed to get MBean attribute value

Action: Make sure attribute name is correct
Level: 1

Type: ERROR

Impact: Data

TRS-10061: Failed to set attribute {0} to {1}.

Cause: Failed to set MBean attribute value

Action: Make sure attribute name and value are correct
Level: 1

Type: ERROR

Impact: Data

TRS-10062: Database operation failed after retrying. Number of retries is {0}.

Cause: Database failure

Action: Check database.
Level: 1

Type: ERROR

Impact: Data

TRS-10063: Exception caught. Exiting Dispatcher thread.

Cause: Application is stopped or database failure.

Action: If it is database failure, check database.
Level: 1

Type: ERROR

Impact: Other

TRS-10064: Job Timeout triggered for client {0} for job {1} with status {2}. Updated time {3}, Timeout Value {4}

Cause: The job has been in the present state for more than the timeout value.

Action: Adjust failure recovery timeout if this error happens very frequently.
Level: 1

Type: ERROR

Impact: Data

TRS-10065: Failed to recover job {0} for client {1}

Cause: Database error may have occurred while updating job status to error.

Action: Check database connections.
Level: 1

Type: ERROR

Impact: Data

TRS-10066: Failed to query for the last processed item for client {0} and job {1}

Cause: Database error may have occurred while querying for replay items.

Action: Check database connections.
Level: 1

Type: ERROR

Impact: Data

TRS-10067: No items have been updated for client {0}

Cause: The item has been in the present state for more than the timeout value.

Action: Adjust item processing timeout if this error happens very frequently.
Level: 1

Type: ERROR

Impact: Data

TRS-10068: Failed to recover replay item for client {0} job {1}

Cause: Database error may have occurred while updating replay item status.

Action: Check database connections.
Level: 1

Type: ERROR

Impact: Data

TRS-10069: Received HTTP error code {0} for request {1}

Cause: Some error has occurred in the TxnReplayer component.

Action: Check log for errors logged before.
Level: 1

Type: ERROR

Impact: Data

TRS-10070: Cannot persist settings change for key: {0}, value: {1}

Cause: Some error has occurred in Java preference node persistent storage.

Action: Check default Java preference node storage location for your system.
Level: 1

Type: ERROR

Impact: Data

TRS-10071: Client {0}, Replay item #{1}: Custom Java class {2} cannot be found

Cause: Custom Java class is missing

Action: Check to make sure the custom Java class library is available
Level: 1

Type: ERROR

Impact: Data

TRS-10072: Client {0}, Replay item #{1}: Invalid parameter value {2} for the {3} of type {4} has been detected

Cause: Parameter value is not valid

Action: Check PARAMS column for this item in table
Level: 1

Type: ERROR

Impact: Data

TRS-10073: Client {0}, Replay item #{1}: Invalid parameter value for the {2} of type {3} has been detected. {4}

Cause: Parameter value is not valid

Action: Check PARAMS column for this item in table
Level: 1

Type: ERROR

Impact: Data

TRS-10074: Client {0}, Replay item #{1}: The value {2} of type char is empty

Cause: Parameter value is not valid

Action: Check PARAMS column for this item in table
Level: 1

Type: ERROR

Impact: Data

TRS-10075: Client {0}, Replay item #{1}: Invalid parameter value {2} {3} of type boolean has been detected

Cause: Parameter value is not valid

Action: Check PARAMS column for this item in table
Level: 1

Type: ERROR

Impact: Data

TRS-10076: Client {0}, Replay item #{1}: NULL is not a valid parameter value for the {2} of type {3}

Cause: Parameter value is not valid

Action: Check PARAMS column for this item in table
Level: 1

Type: ERROR

Impact: Data

TRS-10077: Cannot get Response from {0}. Replay item cannot be processed. {1}

Cause: TxnReplayer might not be running

Action: Check network. Make sure TxnReplayer is running
Level: 1

Type: ERROR

Impact: Network

TRS-10078: Client {0}, Replay item #{1}: the replay type has an invalid PASSWORD_TYPE value {2}.

Cause: Invalid PASSWORD_TYPE in REPLAY_TYPE table

Action: Provide valid value for the PASSWORD_TYPE column of the corresponding replay type in the REPLAY_TYPE table
Level: 1

Type: ERROR

Impact: Data

TRS-10079: Client {0}, Replay Item {1}: PARAMS column in REPLAY_ITEM table cannot be null or empty.

Cause: The PARAMS column in REPLAY_ITEM table is null or empty

Action: The PARAMS should have a value
Level: 1

Type: ERROR

Impact: Data

TRS-10080: TRS cannot publish the business event.

Cause: Client {0}, Item {1}: The event publication failed

Action: Check the following: (1) check the configuration (for example datasource) for event publication; (2) check the event payload; (3) check the DOM parser specified
Level: 1

Type: ERROR

Impact: Data

TRS-10081: Cannot parse property {0} for Replay type {1}. The property will be ignored.

Cause: The TYPE_PROPERTIES value for the replay type is in wrong format.

Action: Verify the value is a single string with a sequence of name value pairs, for example, "name1=value1;name2=value2;name3=value3;..."
Level: 1

Type: ERROR

Impact: Data

TRS-10082: Client {0}, Replay item #{1}: Application Module Configuration should not be empty for the replay type.

Cause: The ADF_CONFIG_NAME value for the replay type is empty.

Action: Provide valid value for ADF_CONFIG_NAME column in REPLAY_TYPE table for the replay type.
Level: 1

Type: ERROR

Impact: Data

TRS-10083: Client {0}, Replay item #{1}: Servlet URL should not be empty for the replay type.

Cause: The ReplayServletURL value for the replay type is empty.

Action: Provide valid ReplayServletURL value in TYPE_PROPERTIES column in REPLAY_TYPE table for the replay type.
Level: 1

Type: ERROR

Impact: Data

TRS-10084: Client {0}, Replay item #{1}: Cannot authenticate the user.

Cause: The username and password provided in replay item cannot be authenticated.

Action: Check the username and password for the replay item.
Level: 1

Type: ERROR

Impact: Data

TRS-10085: Client {0}, Replay item #{1}: Received error response from ReplayServlet with HTTP status code {2}. Detailed message: {3}

Cause: The server encountered error when processing the request.

Action: Check the log for details.
Level: 1

Type: ERROR

Impact: Data

TRS-10086: Client {0}, Replay item #{1}: Cannot post to ReplayServlet due to transport error.

Cause: Cannot post to the ReplayServlet due to transport/network problems.

Action: Check the network or increase the timeout.
Level: 1

Type: ERROR

Impact: Data

TRS-10087: Client {0}, Replay item #{1}: Cannot post to ReplayServlet due to protocol violation.

Cause: There may be a mismatch between client and server in interpreting the HTTP specification.

Action: Report the bug.
Level: 1

Type: ERROR

Impact: Data

TRS-10088: Authentication failed because it cannot post to ReplayServlet due to transport error.

Cause: Cannot post to the ReplayServlet due to transport/network problems.

Action: Check the network or increase the timeout.
Level: 1

Type: ERROR

Impact: Data

TRS-10089: Authentication failed because it cannot post to ReplayServlet due to protocol violation.

Cause: There may be a mismatch between client and server in interpreting the HTTP specification.

Action: Report the bug.
Level: 1

Type: ERROR

Impact: Data

TRS-10090: Failed to validate credential for user {0} for replay type {1}.

Cause: Incorrect username or password.

Action: Check whether username or password is correctly set up for the replay type.
Level: 1

Type: ERROR

Impact: Data

TRS-19000: Entity Object {0} with key {1} not found.

Cause: The entity object row is not found in the database.

Action: Please check if the transaction needs to be changed and resubmitted.
Level: 1

Type: ERROR

Impact: Data

TRS-19001: Cannot find attribute {0} in Entity Object {1}.

Cause: The definition of attribute is not found in the entity object.

Action: Please make sure that the mobile entity object and server entity object have consistent attribute definitions.
Level: 1

Type: ERROR

Impact: Data

TRS-19002: Entity Object {0} with key {1} has an update conflict on attribute {2}. Current server-side value is ({3}), client-side old value is ({4}) and new value is ({5}).

Cause: The server value is different from the client's old value. Some other transaction(s) might have updated the server value since client's last synchronization.

Action: Please check if the transaction needs to be changed and resubmitted.
Level: 1

Type: ERROR

Impact: Data

TRS-20000: TRSConnectionMgr: invalid Database Retries is defined in MBeans. It is treated as no database retry.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

TRS-20001: Client {0}, Replay item #{1}: Plain user password is provided in REPLAY_ITEM table, which is not secure.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Security

TRS-20002: Client {0}, Replay item #{1}: The value {2} {3} of type char is longer than 1 character. Ignoring the rest of the characters.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Data

TRS-20003: {0} Preferences has invalid values. Reset using web.xml values.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

TRS-20004: {0} - error unregistering. {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

TRS-20005: {0} - cannot resolve backup DataSource name {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

TRS-20006: {0} failed to close statement. {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Data

TRS-20007: TRSConnectionMgr: failed to return connection to the pool. {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Data

TRS-20008: The system property {0} has value ({1}), which is different from the expected value ({2}).

Cause: The Java VM does not have the system property needed to support full features of TRS.

Action: Set the property or check documentation on its impact.
Level: 1

Type: WARNING

Impact: Configuration

TRS-20009: {0}: Failed to save archive attributes to preference node. {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Data

TRS-20010: {0}: Failed to remove archive attributes from preference node. {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Data

TRS-20011: TRSConnectionMgr is retrying to get connection. Number of times that TRSConnectionMgr retried:{0}

Cause: Database failure.

Action: Check database.
Level: 1

Type: WARNING

Impact: Configuration

TRS-20012: TRSDBExecutor is retrying the database operation. Number of times that TRSDBExecutor retried:{0}

Cause: Database failure.

Action: Check database.
Level: 1

Type: WARNING

Impact: Configuration

TRS-20013: A Replay Item for client {0} has been updated to status "ADMIN_REVIEW".

Cause: TxnReplayer failed while processing replay items.

Action: Adjust failure recovery timeout if this error happens very frequently.
Level: 1

Type: WARNING

Impact: Data

TRS-20014: {0} jobs to be submitted, but the expected number is {1} jobs.

Cause: Job query failed to pick up all new jobs.

Action: Increase dispatcher cycle time if this warning happens very frequently.
Level: 1

Type: WARNING

Impact: Data

TRS-20015: Client {0}, Replay item #{1}: USER_PASSWORD column is ignored for "CSF" password type.

Cause: User password is retrieved from credential store for replay types with "CSF" password type.

Action: Remove the value in USER_PASSWORD column in REPLAY_ITEM table for replay items with "CSF" password type.
Level: 1

Type: WARNING

Impact: Data

TRS-20016: {0} - Cannot access the MBean Server through JNDI: {1}. {2}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

TRS-20017: Test certificate is used for public key encryption.

Cause: Test certificate was configured as the default certificate for development purpose only.

Action: Use a secure certificate in a production environment.
Level: 1

Type: WARNING

Impact: Configuration

TRS-20018: {0}: Cannot close SQL result set. {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-20019: {0}: Cannot close SQL statement. {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-20020: {0}: Cannot close File Writer. {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30000: TRSConnectionMgr: using backup DataSource

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30001: Changing TxnReplayer URL from {0} to {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

TRS-30002: Changing Dispatcher loop delay from {0} to {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

TRS-30003: DispatcherListener: Starting Dispatcher thread.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Threads

TRS-30004: DispatcherListener: Stopping Dispatcher thread.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Threads

TRS-30005: The keystore provider is {0}. The keystore URL is {1}. The keystore type is {2}. The certificate alias is {3}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

TRS-30006: Client {0}, Replay item #{1}: Begin processing the item.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30007: Client {0}, Replay item #{1}: Successfully processed the item.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30008: Client {0}, Replay item #{1}: Checking replay item dependency.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30009: Client {0}, Replay item #{1}: Calling Method={2}, Class={3}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

TRS-30010: Client {0}, Replay item #{1}: Invoking method {2} of Class {3} succeeded.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

TRS-30011: Client {0}, Replay item #{1}: Use custom XSD {2}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30012: Client {0}, Replay item #{1}: Use custom XSL {2}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30013: Public key encryption is disabled.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

TRS-30014: {0}: Inserted item {1} successfully.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30015: {0}: Enabling auto archive of replay jobs and replay items

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30016: Auto archive is enabled. Archive Time is {0}. Archive Interval is {1}. Archive Age is {2}. Archive Path is {3}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30017: {0}: Successfully removed {1} replay items

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30018: {0}: Successfully removed {1} replay jobs

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30019: Removing replay jobs older than {0} and with job status DONE or ERROR

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30020: Removing replay items older than {0} and with any status but PENDING, PROCESSING or ADMIN_REVIEW

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30021: Successfully created archive file {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30022: Recovering job {0} for client {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30023: Recovering replay items for client {0} and job {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30024: Persist setting changes for key: {0}, value: {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30025: {0}: Successfully removed {1} lone replay items

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30026: {0}: Successfully removed {1} parent/child replay items

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30027: {0}: Successfully removed {1} replay items in total

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30028: Successfully disabled auto archive of replay jobs and replay items

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30029: Publish business event

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

TRS-30030: Successful credential validation for user {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Data

95 UCM-CS-000001 to UCM-CS-800279

UCM-CS-000001: general exception

Cause: An exception occurred in the content server.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Logging

UCM-CS-000002: Error:

Cause: An error occurred in the content server.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Logging

UCM-CS-000003: Unknown system error encountered.

Cause: An error occurred in the content server.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Logging

UCM-CS-000004: Unknown error encountered.

Cause: The system encountered an unknown error.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Logging

UCM-CS-000005: Null pointer is dereferenced.

Cause: A null pointer exception occurred in the content server.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Logging

UCM-CS-000006: Trace Message:({0})

Cause: A general trace message from the content server.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: NOTIFICATION

Impact: Logging

UCM-CS-001001: The NativeOsUtils class is not loaded.

Cause: The required library 'NativeOsUtils' was not successfully loaded.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Configuration

UCM-CS-001002: Native file operations are disabled.

Cause: The system's ability to do native file operations has been disabled.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Configuration

UCM-CS-001003: The platform {0} is not supported.

Cause: The specified operating system does not supported.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Configuration

UCM-CS-001004: The platform {0} is not supported for this operation.

Cause: The specified operating system did not support the specified operation.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Configuration

UCM-CS-001005: The argument {0} is missing.

Cause: The method or service was missing the required argument.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Configuration

UCM-CS-001006: {0} is missing from {1}.

Cause: The method or service was missing the required argument.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Configuration

UCM-CS-001007: Unable to load database queries in table {0} for component {1}. The table does not exist.

Cause: An error was encountered while loading the queries for the named component.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Configuration

UCM-CS-001008: The feature {0} is not installed.

Cause: The required feature has not been installed.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Configuration

UCM-CS-001009: The feature {0} is at level {1}, but level {2} is required.

Cause: An error was encountered while validating features. The requested feature is not supported.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Configuration

UCM-CS-001010: Incompatibility with feature {0} at level {1} has been detected.

Cause: The specified feature was incompatible with a feature provided either by the system or another component.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Configuration

UCM-CS-001011: The feature {0} does not match feature {1}.

Cause: The feature did not match an already installed feature.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Configuration

UCM-CS-001012: The feature {0} is installed at level {1}, but is also provided at level {2}.

Cause: The feature already existed at a later version.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Configuration

UCM-CS-001013: The instance name {0} is not valid.

Cause: The instance name specified contained illegal characters.

Action: The instance name needs to be configured to be a valid name. Please check documentation for how to configure.
Level: 1

Type: ERROR

Impact: Configuration

UCM-CS-001014: {0} component, version {1}, requires missing feature(s). {2}

Cause: For the specified component to function correctly it needs the listed features.

Action: The components that provide the listed features need to be installed.
Level: 1

Type: ERROR

Impact: Configuration

UCM-CS-005001: Unable to copy the file {0} to {1}.

Cause: An error occurred while copying files.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Files

Cause: An error occurred while copying files.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

UCM-CS-005002: Unable to rename the file {0} to {1}.

Cause: An error occurred while renaming files.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Files

Cause: An error occurred while renaming files.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

UCM-CS-005003: Unable to open {0}.

Cause: An error occurred while opening the named file.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Files

UCM-CS-005004: Unable to read {0}.

Cause: An error occurred while accessing a file.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Files

UCM-CS-005005: Unable to write {0}.

Cause: An error occurred while writing a file.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Files

UCM-CS-005006: The file is missing.

Cause: The specified file was missing.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Files

UCM-CS-005007: The file {0} does not exist.

Cause: The specified file did not exist.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Files

UCM-CS-005008: The file {0} already exists.

Cause: The file already existed in the system.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Files

UCM-CS-005009: The file {0} already exists in {1} directory.

Cause: The file already existed in the named directory.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Files

UCM-CS-005010: File I/O error encountered while reading from file.

Cause: An error occurred while reading the file.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Files

UCM-CS-005011: File I/O error encountered while writing to file.

Cause: An error occurred while writing the specified file.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Files

UCM-CS-005012: Unable to delete {0}.

Cause: An error occurred while deleting the specified file.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Files

UCM-CS-005013: Could not create the file {0}.

Cause: An error occurred while creating the specified file.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Files

Cause: An error occurred while creating the specified file.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

UCM-CS-005014: File I/O error encountered while saving to file {0}.

Cause: An error occurred while saving the specified file.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Files

UCM-CS-005015: The file path {0} is invalid.

Cause: The specified file path was invalid.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Files

UCM-CS-005016: Unable to find the file {0}. This may be a problem with the virtual machine.

Cause: The system expected a file at the specified location, but it was missing.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Files

UCM-CS-005017: Unable to find the file {0}.

Cause: The system was unable to locate the file at the specified location.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Files

UCM-CS-005018: Error encountered while creating long-term lock {1} on directory {0}.

Cause: An error occurred while creating the long term lock.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Files

UCM-CS-005019: Unable to create the directory.

Cause: An error occurred while creating the directory.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Files

UCM-CS-005020: Unable to create directory {0}.

Cause: An error occurred while creating the specified directory.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Files

UCM-CS-005021: Directory {0} does not exist.

Cause: The system was unable to locate a directory at the specified location.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Files

UCM-CS-005022: File {0} does not exist.

Cause: The system was unable to locate a file at the specified location.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Files

Cause: The system was unable to locate a file at the specified location.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.

UCM-CS-005023: Directory {0} cannot be accessed.

Cause: An error occurred while accessing the directory.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Files

UCM-CS-005024: File {0} cannot be accessed.

Cause: An error occurred while accessing the specified file.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Files

UCM-CS-005025: Directory {0} is read-only.

Cause: A read-only directory was specified.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Files

UCM-CS-005026: File {0} is read-only.

Cause: A read-only file was specified.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Files

UCM-CS-005027: Directory {0} has an invalid path.

Cause: The system tried to access an invalid directory path.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Files

UCM-CS-005028: File {0} has an invalid path.

Cause: The system tried access an invalid file path.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Files

UCM-CS-005029: Accessing the directory {0} caused a system error.

Cause: An error was encountered while accessing the directory.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Files

UCM-CS-005030: File {0} caused a system error when accessed.

Cause: An error was encountered while accessing the file.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Files

UCM-CS-005031: Unable to rename the file {0} to {1}.

Cause: An error was encountered when trying to rename the specified file.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Files

UCM-CS-005032: The source file does not exist.

Cause: The specified file did not exist.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Files

UCM-CS-005033: The target file cannot be accessed.

Cause: The system was unable to access the specified file path.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Files

UCM-CS-005034: Unable to copy the file {0} to {1}. The source file does not exist.

Cause: An error was encountered while copying the file. The source file did not exist.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Files

UCM-CS-005035: Unable to copy the file {0} to {1}.

Cause: An error was encountered while copying the file.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Files

UCM-CS-005037: File is locked by another process.

Cause: The file was locked by another process.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Files

UCM-CS-005038: File {0} cannot be deleted. It may be locked by another process.

Cause: An error was encountered while deleting the file.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Files

UCM-CS-005039: Long-term lock {0} cannot be created for agent {1}.

Cause: An error was encountered while attempting to create a long-term lock.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Files

UCM-CS-010001: Cannot end string with {0}.

Cause: During the parsing of a string, an illegal end character was encountered.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Data

UCM-CS-010002: Encountered an unterminated quote ({0}) at {1} in {2}.

Cause: During the parsing of a string, the parser found an unclosed quoted string.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Data

UCM-CS-010003: Error encountered converting data with {0} character encoding.

Cause: An encoding error was encountered while converting the data.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Data

UCM-CS-010004: Error encountered converting data with the default character encoding.

Cause: The system encountered an error while converting data with the default character encoding.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Data

UCM-CS-010005: An error occurred decoding the stream.

Cause: An error was encountered while decoding the data.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Data

UCM-CS-010006: Cannot find the parameter {0}.

Cause: The system could not find the named parameter.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Data

UCM-CS-010007: The table does not exist.

Cause: The named table did not exist or was not loaded into the resource container.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Data

UCM-CS-010008: The column {0} does not exist in this table.

Cause: The specified column did not exist in the table.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Data

UCM-CS-010009: Parameter {0} is not present.

Cause: The parameter was not defined in the current data set.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Data

UCM-CS-010010: Unable to parse result set {0}.

Cause: An error was encountered while parsing the result set.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Data

UCM-CS-010011: Unable to parse properties. Name-value pair {0} is missing an equal sign (=).

Cause: An error was encountered while parsing a property name-value pair.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Data

UCM-CS-010012: Error decoding the string. The string is badly formatted: {0}

Cause: An error was encountered while decoding the badly formatted string.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Data

UCM-CS-010013: A name-value pair is missing the name in GET or POST syntax.

Cause: An error was encountered while parsing the request.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Data

UCM-CS-010014: The input terminated before being able to read the line.

Cause: An error was encountered while reading the input stream.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Data

UCM-CS-010015: The stream terminated before being able to read HTTP protocol line.

Cause: An error was encountered while reading the input stream.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Data

UCM-CS-010016: Unable to parse data; the request method was not specified.

Cause: An error was encountered while parsing the input stream. The request method has not been specified.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Data

UCM-CS-010017: The POST request did not send sufficient data.

Cause: An error was encountered while parsing the request.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Data

UCM-CS-010018: Unable to read the stream to determine the format.

Cause: An error was encountered while processing the server request.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Data

UCM-CS-010019: Unable to read additional bytes.

Cause: An error was encountered while processing the server file request.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Data

UCM-CS-010020: Client terminated the upload of file {0}.

Cause: The client terminated the upload of the file.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Data

UCM-CS-050001: illegal state

Cause: Something put the system into an unexpected error; this is a generic error.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-050002: The transaction listener {0} failed to close.

Cause: The transaction failed to close when performing the service request.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-050003: Database table does not exist.

Cause: An error was encountered while performing a database activity.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-050004: Cannot bind all parameters in query {0}.

Cause: An error was encountered while creating the SQL query. The number of parameters required was inconsistent with the number of parameters provided.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-050005: Unable to initialize the database {0}.

Cause: An error was encountered while the system was initializing the database connections.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-050006: Unable to create database connection for {0}.

Cause: An error was encountered while trying to create a database connection for the named server instance.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-050007: Server busy. Unable to obtain a connection to the database.

Cause: The server was unable to establish a connection to the database.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-050008: Unable to execute query {0}.

Cause: An error was encountered while executing the specified query.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-050009: Unable to execute callable query {0}.

Cause: An error was encountered while executing the named callable query.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-050010: Unable to create the result set for query {0}.

Cause: An error was encountered while creating the results for the specified query.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-050011: Unable to execute SQL statement {0}.

Cause: An error was encountered while executing the given SQL statement.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-050012: Unable to determine the database type.

Cause: An error was encountered while determining the database type.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-050013: Error occurred while closing connection: ({0}).

Cause: An error was encountered while closing the database connection.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-050014: Cannot begin the transaction. JDBC Error:

Cause: An error was encountered while beginning a database transaction.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-050015: Cannot commit the transaction. JDBC Error:

Cause: An error was encountered while committing a database transaction.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-050016: Failed to find indexable webviewable for content item {0} with revlabel {1} and dID {2}.

Cause: An error was encountered while indexing the specified content item.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-050017: Text conversion of the file {0} failed.

Cause: An error was encountered while indexing the specified content item.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-050018: Indexing failed.

Cause: An error was encountered while indexing the specified content item.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-050019: The creation date ({0}) of the new revision is not later than the creation date ({1}) of the latest revision in the system.

Cause: An error was encountered while importing the content item. The create date for the new revision must be later than the older revision.

Action: The Archiver uses dates to validate the correct order of revisions. By default, it uses the dCreateDate, but this can be configured to use the dInDate by setting the configuration parameter UseRevisionCreateDate to true.
Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-050020: The release date ({0}) of the new revision is not later than the release date ({1}) of the latest revision in the system.

Cause: An error was encountered while importing the content item. The in date for the new revision must be later than the older revision.

Action: The Archiver uses dates to validate the correct order of revisions. By default, it uses the dCreateDate, but this can be configured to use the dInDate by setting the configuration parameter UseRevisionCreateDate to true.
Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-050021: Oracle WebCenter Content failed to initialize inside its servlet environment.

Cause: An error was encountered during initialization of the servlet environment./td>

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-050022: Active index ({0}) is not valid for the indexer engine ({1}).

Cause: The currently active search index was invalid for the configured indexer engine.

Action: A rebuild of the search collection is required.
Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-050023: An error occurred during indexing.

Cause: The system encountered an error while indexing a document.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entries that are part of this message stack.
Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-050024: Search collection is not up-to-date.

Cause: The system has determined that the search indexing collection configuration has been modified.

Action: A rebuild of the search collection is recommended.
Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-050025: Commit is called by thread {0} in auto-commit mode.

Cause: A database commit call was made in a thread configured to be in auto-commit mode.

Action: The stack trace can be examined to determine which component or feature tried to perform the commit.
Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-060000: Starting the service {0} version {1} PID {2}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

UCM-CS-060001: {0} component, version {1}, provides {2} feature(s)

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

UCM-CS-060002: Server ready and waiting for connection on port {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

UCM-CS-060003: Event generated by user {0} at host {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

UCM-CS-060004: User {0} changed the following entry in config.cfg on server {1}:

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

UCM-CS-060005: Restarting rebuild of the search index.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

UCM-CS-060006: Starting rebuild of the search index.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

UCM-CS-060007: Finished rebuilding the search index with a total of {0} files successfully indexed. A total of {1} files had a full text index.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

UCM-CS-060008: Finished rebuilding the search index with a total of {0} files successfully indexed. A total of {1} files had a full text index and {2} failed to index.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

UCM-CS-060009: Indexing aborted.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

UCM-CS-060010: Text index {0} is optimized.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

UCM-CS-060011: Started monitoring.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

UCM-CS-060012: Event {0} has finished

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

UCM-CS-060013: Shutting down server connections.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

UCM-CS-060014: Trace is verbose.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

UCM-CS-060015: Trace sections list has been updated to {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

UCM-CS-060016: Referred to by {0}.\&lf;

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Files

UCM-CS-060017: User agent is {0} and request method is {1}.\&lf;

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Files

UCM-CS-060018: The refresh activity '{0}' has completed {1} out of {2} links with {3} errors.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

UCM-CS-060019: The fsconfig.hda file has been created in the data/filestore/config directory.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

UCM-CS-060020: Added:

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

UCM-CS-060021: Modified:

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

UCM-CS-060022: Removed:

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

UCM-CS-060023: Trace is not verbose.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

UCM-CS-100001: Oracle WebCenter Capture URL has not been configured. Please contact the Administrator.

Cause: ODDCURLPath environment variable is not set.

Action: Set the ODDCURLPath to point to ODDC server.
Level: 1

Type: ERROR

Impact: Configuration

UCM-CS-100002: Unable to detach Oracle WebCenter Content document from siebel entity.

Cause: Database delete operation failed since the row does not exist if the document is already detached.

Action: Refresh the Managed Attachments window.
Level: 1

Type: ERROR

Impact: Data

UCM-CS-100003: Error: siebelEntityField and siebelEntityValue are mandatory Parameters.

Cause: One of the parameters SiebeleEntityField OR SiebeleEntittyValue is missing.

Action: Make sure the URL has the parameters SiebeleEntityField AND SiebeleEntittyValue.
Level: 1

Type: ERROR

Impact: Programmatic

UCM-CS-100101: User '{0}' does not have sufficient access privileges to perform this operation. Access privileges may have expired, requiring the user to re-select Managed Attachments from the Oracle E-Business Suite Zoom Menu.

Cause: User does not have sufficient access privileges to perform this operation.

Action: Contact Administrator for getting appropriate Roles for Access.
Level: 1

Type: ERROR

Impact: Configuration

Cause: Access privileges may have expired.

Action: User needs to re-select Managed Attachments from the Oracle E-Business Suite Zoom Menu.

UCM-CS-100102: Failed to detach document '{0}'

Cause: Document detach operation failed because the document is already detached or deleted.

Action: Refresh Managed Attachments page and try this operation again.
Level: 1

Type: ERROR

Impact: Data

UCM-CS-100103: User '{0}' does not have sufficient access privileges to perform this operation. Access privileges may have expired, requiring the user to re-access Managed Attachments from the PeopleSoft User Interface.

Cause: User does not have sufficient access privileges to perform this operation.

Action: Contact Administrator for getting appropriate Roles for Access.
Level: 1

Type: ERROR

Impact: Configuration

Cause: Access privileges may have expired.

Action: User needs to re-select Managed Attachments from the Oracle E-Business Suite Zoom Menu.

UCM-CS-800001: Cannot load archive.

Cause: Cannot load archive.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800002: Cannot build archive.

Cause: Cannot build archive.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800003: No value was provided and no default value is set for the metadata field

Cause: No value was provided and no default value is set for the metadata field

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800004: The form '{0}' already contains a field named '{1}'.

Cause: The form already contains a field of the same name.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800005: Dashboard error occured while saving as new dashboard

Cause: Dashboard error occured while saving as new dashboard

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800006: Workflow approve action does not work for non-existent item.

Cause: Workflow approve action does not work for non-existent item.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800007: Unable to load from RSS URL location. Check RSS dashboard options in edit view.

Cause: Unable to load from RSS URL location. Check RSS dashboard options in edit view.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800008: Unable to update the configuration information.

Cause: Unable to update the configuration information.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800009: Unable to update the data source information.

Cause: Unable to update the data source information.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800010: Unable to export the report type xml data.

Cause: Unable to export the report type xml data.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800011: Unable to check in report.

Cause: Unable to check in report.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800012: Unable to run the scheduled report.

Cause: Unable to run the scheduled report.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800013: Unable to checkout default reports.

Cause: Unable to checkout default reports.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800014: The report template is missing.

Cause: The report template is missing.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800015: Unable to get the service data source parameters.

Cause: Unable to get the service data source parameters.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800016: Unable to get the query data source parameters.

Cause: Unable to get the query data source parameters.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800017: The BL Publisher RTF processor failed.

Cause: The BL Publisher RTF processor failed.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800018: Unable to get the related content.

Cause: Unable to get the related content.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800019: Unable to get the related content types.

Cause: Unable to get the related content types.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800020: The related type ID is missing.

Cause: The related type is missing a field.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800021: The related type name '{0}' does not exist.

Cause: The related type name does not exist.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800022: The related type name '{0}' already exists.

Cause: The related type name already exists.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800023: The related type class ID is missing.

Cause: The related type class ID is missing.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800024: The supersede related type cannot be edited. Related content currently exists.

Cause: The supersede related type cannot be edited. Related content currently exists.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800025: The content ID (dID) is missing.

Cause: The content ID is missing.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800026: No external sources were found. Check to see if the 'ExternalHelper' component is installed and enabled.

Cause: No external sources were found. Check to see if the 'ExternalHelper' component is installed and enabled.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800027: More than one superseded content links selected. Please remove excess superseded links.

Cause: More than one superseded content links selected. Please remove excess superseded links.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800028: URMAgent or RetentionManager components are disabled. Please click ok to enable the components. Then, restart the server and configure UrmAgent source.

Cause: URMAgent or RetentionManager components are disabled. Please click ok to enable the components. Then, restart the server and configure UrmAgent source.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800029: {0} disposition action is not defined in DispositionActionsList

Cause: Disposition Action is not specified for this dDispostion.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800030: Error while checking setup requirements for new component install.

Cause: Error while checking setup requirements for new component install.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800031: Cannot checkout content item: Not Revisionable.

Cause: Cannot checkout content item: Not Revisionable.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800032: Cannot edit content item: Not Editable.

Cause: Cannot edit content item: Not Editable.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800033: Cannot delete content item: Not Deletable.

Cause: Cannot delete content item: Not Deletable.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800034: User does not have access to folders(or parent folders) or folder does not exists.

Cause: User does not have access to folders(or parent folders) or folder does not exists.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800035: Error retrieving information about category '{0}'

Cause: Error retrieving information about the category

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800036: Error retrieving information about folder '{0}'

Cause: Error retrieving information about the folder

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800037: Error retrieving information about series '{0}'

Cause: Error retrieving information about the series

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800038: Error creating category named '{0}': category with specified id exists

Cause: Error creating item, item with specified id exists

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800039: Unable to get screening results for categories

Cause: Unable to get screening results

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800040: Unable to prepare the HDA edit form.

Cause: Unable to prepare the HDA edit form.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800041: Unable to notify pending event actions

Cause: Unable to notify pending event actions

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800042: Unable to Mark Reviewed

Cause: Unable to Mark Reviewed

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800043: Unable to supersede content or records.

Cause: Unable to supersede content or records.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800044: Access denied - cutoff items are readonly

Cause: Access denied - cutoff items are readonly

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800045: Failed to delete metadata history.

Cause: Failed to delete metadata history.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800046: Disposition contains unprocessed content or record.

Cause: Disposition contains unprocessed content or record.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800047: Unable to find log or report information.

Cause: Unable to find log or report information.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800048: Failed to process report.

Cause: Failed to process report.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800049: Cannot edit frozen content or folder

Cause: Cannot edit frozen content or folder

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800050: Unable to run batch services for notifications

Cause: Unable to run batch services

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800051: Unable to list scheduled freezes

Cause: Unable to list scheduled freezes

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800052: Cannot delete frozen content.

Cause: Cannot delete frozen content.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800053: Unable to Notify Process Monitoring Alerts

Cause: Unable to Notify Process Monitoring Alerts

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800054: Unable to reset performance process monitoring

Cause: Unable to reset performance process monitoring

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800055: Unable to reset performance process monitoring alerts

Cause: Unable to reset performance process monitoring alerts

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800056: Unable to parse category dispositions information

Cause: Unable to parse category dispositions information

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800057: The field {0} requires an integer entry.

Cause: The field requires an integer entry.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800058: System derived cutoff must be first action

Cause: System derived cutoff must be first action

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800059: Invalid Trigger Event: first disposition rule has no preceding action

Cause: Invalid Trigger Event: first disposition rule has no preceding action

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800060: Delete Revision action is forbidden in permanent categories

Cause: Delete Revision action is forbidden in permanent categories

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800061: Destroy or Delete Revision action is forbidden in permanent categories

Cause: Destroy or Delete Revision action is forbidden in permanent categories

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800062: Destroy action is forbidden in permanent categories

Cause: Destroy action is forbidden in permanent categories

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800063: The first character of the Name field must be alphabetic

Cause: The first character of the Name field must be alphabetic

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800064: The Name field contains invalid character

Cause: The Name field contains invalid character

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800065: User does not have all matching Supplemental Markings.

Cause: User does not have all matching Supplemental Markings.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800066: User does not have Security Markings.

Cause: User does not have Security Markings.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800067: User does not have group(alias)/user permissions (ACL-based collaboration security privilege).

Cause: User does not have group(alias)/user permissions (ACL-based collaboration security privilege).

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800068: Performance process monitoring time exceeded max limit

Cause: Performance process monitoring time exceeded max limit

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800069: This class can only contain classes

Cause: This class can only contain classes

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800070: This class can only contain files

Cause: This class can only contain files

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800071: This class can only contain content items (or volumes)

Cause: This class can only contain content items (or volumes)

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800072: This class can contain classes, files, or content items

Cause: This class can contain classes, files, or content items

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800073: This file can only contain sub-files

Cause: This file can only contain sub-files

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800074: This file can only contain content items (or volumes)

Cause: This file can only contain content items (or volumes)

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800075: This file can contain sub-files or content items

Cause: This file can contain sub-files or content items

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800076: This sub-file can only contain content items (or volumes)

Cause: This sub-file can only contain content items (or volumes)

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800077: This volume can only contain content items

Cause: This volume can only contain content items

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800078: There was an internal error in submitting the form

Cause: There was an internal error in submitting the form

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800079: There was an internal error in reseting the form

Cause: There was an internal error in reseting the form

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800080: Error initiating connection or retrieving HTTP response code.

Cause: Error initiating connection or retrieving HTTP response code.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800081: Unable to get response stream from HTTP request.

Cause: Unable to get response stream from HTTP request.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800082: Http request needs a response rule to be specified is requesting agent a browser or an application

Cause: Http request needs a response rule to be specified is requesting agent a browser or an application

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800083: Unable to initiate connection.

Cause: Unable to initiate connection.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800084: The connection is currently not available.

Cause: The connection is currently not available.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800085: Credential map data was not successfully loaded.

Cause: Credential map data was not successfully loaded.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800086: Credentials map table {0} is missing.

Cause: Credentials map table is missing.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800087: Error creationg charge type '{0}'.

Cause: Error creationg charge type.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800088: Error editing charge type '{0}'.

Cause: Error editing charge type.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800089: Error deleting charge type '{0}'.

Cause: Error deleting charge type.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800090: Error retrieving information about charge type '{0}'.

Cause: Error retrieving information about charge type.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800091: Charge type '{0}' already exists.

Cause: Error creating charge type: charge type with specified id exists.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

Cause: Charge type already exists.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.

UCM-CS-800092: Invalid adjustment amount. Adjustment amount cannot make the invoice amount less than zero.

Cause: Invalid adjustment amount. Adjustment amount cannot make the invoice amount less than zero.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800093: Error creationg payment type '{0}'.

Cause: Error creationg payment type.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800094: Error editing payment type '{0}'.

Cause: Error editing payment type.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800095: Error deleting payment type '{0}'.

Cause: Error deleting payment type.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800096: Error retrieving information about payment type '{0}'.

Cause: Error retrieving information about payment type.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800097: Payment type '{0}' already exists.

Cause: Error creating payment type: charge type with specified id exists.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

Cause: Payment type already exists.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.

UCM-CS-800098: Error creationg customer '{0}'.

Cause: Error creationg customer.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800099: Error editing customer '{0}'.

Cause: Error editing customer.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800100: Error deleting customer '{0}'.

Cause: Error deleting customer.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800101: Error retrieving information about customer '{0}'.

Cause: Error retrieving information about customer.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800102: Customer '{0}' already exists.

Cause: Error creating customer: customer with specified id exists.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800103: Payment type '{0}' already exists.

Cause: Error creating payment type: charge type with specified id exists.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

Cause: Payment type already exists.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.

UCM-CS-800104: Charge type '{0}' already exists.

Cause: Error creating charge type: charge type with specified id exists.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

Cause: Charge type already exists.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.

UCM-CS-800105: Error creating charge transaction '{0}'.

Cause: Error creating charge transaction.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800106: Error browsing charge transactions for invoice '{0}'.

Cause: Error browsing charge transactions.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800107: Object Type is missing. You must provide an object type for charges with actions (Creation, Destruction or Reservation).

Cause: Object Type is missing. You must provide an object type for charges with actions (Creation, Destruction or Reservation).

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800108: Invalid object type. The charge types object type does not match the external items object type

Cause: Invalid object type. The charge types object type does not match the external items object type

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800109: Invalid media type. The charge types media type does not match the external items media type

Cause: Invalid media type. The charge types media type does not match the external items media type

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800110: Invalid external item. The specific external item does not exist.

Cause: Invalid external item. The specific external item does not exist.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800111: Cannot delete a paid transaction.

Cause: Cannot delete a paid transaction.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800112: Unable to retrieve transaction results.

Cause: Unable to retrieve transaction results.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800113: External Item is missing. You must provide an ID or Name for the external item you wish to add a transaction for.

Cause: External Item is missing. You must provide an ID or Name for the external item you wish to add a transaction for.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800114: Must select one or more charge periods for calculation and indicate a number for charge increments. (Days, Weeks, etc).

Cause: Must select one or more charge periods for calculation and indicate a number for charge increments. (Days, Weeks, etc).

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800115: Must indicate a number for charge increments for each selected charge period.

Cause: Must indicate a number for charge increments for each selected charge period.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800116: Must select a department client for processing.

Cause: Must select a department client for processing.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800117: Error Processing Storage Charges.

Cause: Error Processing Storage Charges.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800118: Cannot delete charge type '{0}' is being used by charge transactions.

Cause: Cannot delete charge type, it is being used by charge transactions.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800119: Cannot delete customer '{0}' is being used by charge invoices.

Cause: Cannot delete customer, they are is being used by charge invoices.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800120: Error creating storage item.

Cause: Error creating storage item.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800121: Error deleting storage '{0}'

Cause: Error deleting storage item.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800122: Storage item is unavailable

Cause: Storage item is unavailable

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800123: Storage item is blocked

Cause: Storage item is blocked

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800124: Storage item is reserved

Cause: Storage item is reserved

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800125: Storage '{0}' is not empty.

Cause: Storage item is not empty.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800126: Unable to block storage item(s). One or more storage item(s) contains an external content item(s).

Cause: Unable to block storage item(s). One or more storage item(s) contains an external content item(s).

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800127: Unable to reserve storage item(s). One or more storage item(s) contains an external content item(s) or is reserved.

Cause: Unable to reserve storage item(s). One or more storage item(s) contains an external content item(s) or is reserved.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800128: Unable to delete storage item(s). One or more storage item(s) contains an external content item(s).

Cause: Unable to delete storage item(s). One or more storage item(s) contains an external content item(s).

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800129: Error updating storage availability.

Cause: Error updating storage availability.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800130: Unable to get storage items for export.

Cause: Unable to get storage items for export.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800131: Error editing storage types.

Cause: Error editing storage types.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800132: Error retrieving information about storage type '{0}'.

Cause: Error retrieving information about storage type.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800133: Error creating storage type '{0}': storage type with specified id exists.

Cause: Error creating storage type: storage type with specified id exists.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800134: Error creating object type '{0}': object type with specified id exists.

Cause: Error creating object type: object type with specified id exists.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800135: Object Type is Linked to another object type.

Cause: Object Type is Linked to another object type.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800136: Error creating media type '{0}': media type with specified id exists.

Cause: Error creating media type: media type with specified id exists.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800137: Media type '{0}' is being used by external content.

Cause: Media type is being used by external content.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800138: Error editing request.

Cause: Error editing request.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800139: Cannot complete requests that have not been processed

Cause: Cannot complete requests that have not been processed

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800140: Cannot update a checked out request with any other status than completed

Cause: Cannot update a checked out request with any other status than completed

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800141: Cannot update a non-processed request with status of returned

Cause: Cannot update a non-processed request with status of returned

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800142: Check out date cannot be less than request date

Cause: Check out date cannot be less than request date

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800143: Error rejecting reservation items.

Cause: Error rejecting reservation items.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800144: Error processing reservation content workflow.

Cause: Error processing reservation content workflow.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800145: Unable to get reservation items for export.

Cause: Unable to get reservation items for export.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800146: The external item is already pending or checked out.

Cause: The external item is already pending or checked out.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800147: Record already checked out with another item. Cannot check this item out at this time.

Cause: Record already checked out with another item. Cannot check this item out at this time.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800148: Notify Requestors of Overdue Requests

Cause: Notify Requestors of Overdue Requests

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800149: Item duplicated within request. Item maybe contained within another requested item.

Cause: Item duplicated within request. Item maybe contained within another requested item.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800150: Failed to check in content item for reservation.

Cause: Failed to check in content item for reservation.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800151: Requested item has been destroyed. Cannot reserve.

Cause: Requested item has been destroyed. Cannot reserve.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800152: Reservation items belonging to this group still exist in the system.

Cause: Reservation items belonging to this group still exist in the system.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800153: The external item '{0}' does not exist.

Cause: The external item does not exist.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800154: Item inside of a non record container must be a non record

Cause: Item inside of a non record container must be a non record

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800155: Access denied by manager

Cause: Access denied by manager

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800156: An error occurred writing the audit.

Cause: An error occurred writing the audit.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800157: Not authorized to perform action.

Cause: Not authorized to perform action.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800158: Error processing user label.

Cause: Error processing user label.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800159: Error processing storage label.

Cause: Error processing storage label.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800160: Unable to get user label.

Cause: Unable to get user label.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800161: There are no users selected that contain barcode values. Cannot print labels.

Cause: There are no users selected that contain barcode values. Cannot print labels.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800162: There is no user(s) selected to print barcode labels for. Please select/input user(s) to print barcodes for.

Cause: There is no user(s) selected to print barcode labels for. Please select/input user(s) to print barcodes for.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800163: Content items location does not match the storage location being imported.

Cause: Content items location does not match the storage location being imported.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800164: Error moving storage item, cannot move storage items into 'Other' type storage items

Cause: Error moving storage item, cannot move storage items into 'Other' type storage items

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800165: Error moving storage item, cannot move storage items of type 'Root'.

Cause: Error moving storage item, cannot move storage items of type 'Root'.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800166: Error moving storage item, cannot move storage items of type 'Other'.

Cause: Error moving storage item, cannot move storage items of type 'Other'.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800167: Error moving storage item, storage item already exists within the selected storage item.

Cause: Error moving storage item, storage item already exists within the selected storage item.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800168: Error moving storage item, cannot move storage item into itself.

Cause: Error moving storage item, cannot move storage item into itself.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800169: There is a badly defined table element in the web form. The block has been defined as repeating, but it has no table assigned to it.

Cause: There is a badly defined table element in the web form. The block has been defined as repeating, but it has no table assigned to it.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800170: Encountered an unexpected end of the table. Cannot find close for repeat block.

Cause: Encountered an unexpected end of the table. Cannot find close for repeat block.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800171: An unmatched closing tag was encountered. The advanced element {0} is not properly closed by {1}.

Cause: An unmatched closing tag was encountered. The advanced element is not properly closed.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800172: An IO error was encountered during the generation of the web form.

Cause: An IO error was encountered during the generation of the web form.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800173: There is no content for the web form file.

Cause: There is no content for the web form file.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800174: Unable to access native web form file.

Cause: Unable to access native web form file.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800175: Content '{0}' file name does not match with previous revisions.

Cause: Content file name does not match with previous revisions.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800176: Unable to access system folders.

Cause: Unable to access system folders.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800177: Unable to force security on moved folder or content.

Cause: Unable to force security on moved folder or content.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800178: Unable to retrieve folder information.

Cause: Unable to retrieve folder information.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800179: Unable to retrieve folder.

Cause: Unable to retrieve folder.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800180: Unable to update columns.

Cause: Unable to update columns.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800181: Unable to retrieve columns.

Cause: Unable to retrieve columns.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800182: Unable to retrieve administration configuration.

Cause: Unable to retrieve administration configuration.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800183: Unable to update administration configuration.

Cause: Unable to update administration configuration.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800184: Virtual folder name specifies invalid characters.

Cause: Virtual folder name specifies invalid characters.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800185: Unable to move items.

Cause: Unable to move items.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800186: Unable to delete items.

Cause: Unable to delete items.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800187: Unable to copy items.

Cause: Unable to copy items.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800188: Unable to create shortcut.

Cause: Unable to create shortcut.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800189: Unable to create virtual folder.

Cause: Unable to create virtual folder.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800190: Unable to display virtual folder information.

Cause: Unable to display virtual folder information.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800191: Unable to update virtual folder.

Cause: Unable to update virtual folder.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800192: Unable to remove all content.

Cause: Unable to remove all content.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800193: Unable to restore items.

Cause: Unable to restore items.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800194: Unable to retrieve specified fields.

Cause: Unable to retrieve specified fields.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800195: Unable to update specified fields.

Cause: Unable to update specified fields.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800196: Unable to retrieve specified field defaults.

Cause: Unable to retrieve specified field defaults.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800197: Unable to update specified field defaults.

Cause: Unable to update specified field defaults.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800198: Unable to retrieve specified virtual folder.

Cause: Unable to retrieve specified virtual folder.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800199: Unable to update specified virtual folder.

Cause: Unable to update specified virtual folder.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800200: Unable to edit specified virtual folder.

Cause: Unable to edit specified virtual folder.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800201: Unable to display virtual folder information.

Cause: Unable to display virtual folder information.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800202: Unable to open folder.

Cause: Unable to open folder.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800203: Unable to get reference.

Cause: Unable to get reference.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800204: Unable to move, destination is a subfolder.

Cause: Unable to move, destination is a subfolder.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800205: Unable to add shortcut.

Cause: Unable to add shortcut.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800206: Unable to move shortcut.

Cause: Unable to move shortcut.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800207: Unable to copy shortcut.

Cause: Unable to copy shortcut.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800208: Reference is a ancestor of shortcut.

Cause: Reference is a ancestor of shortcut.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800209: Unable to load environment.

Cause: Unable to load environment.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800210: Unable to change login

Cause: Unable to change login

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800211:

Cause: Local Folder and Directory already specified.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800212:

Cause: Directory not empty.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800213: Unable to archive.

Cause: Unable to archive.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800214: The folder structure is locked.

Cause: The folder structure is locked.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800215: This folder cannot currently be changed.

Cause: This folder cannot currently be changed.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800216: Search Name could not be found

Cause: Search Name could not be found

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800217: Search text could not be found for validation

Cause: Search text could not be found for validation

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800218: Cannot perform an empty search

Cause: Cannot perform an empty search

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800219: SES does not support left-truncated wildcards

Cause: SES does not support left-truncated wildcards

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800220: SES does not support different criteria conjunctions

Cause: SES does not support different criteria conjunctions

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800221: SES does not support the '{0}' operator

Cause: SES does not support that operator

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800222: Permission denied to freeze federated items

Cause: Permission denied to freeze federated items

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800223: Archive does not contain a file for item '{0}'

Cause: Archive does not contain a file for that item

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800224: 'xCategoryID' and 'xFolderID' cannot both be specified for item '{0}'

Cause: 'xCategoryID' and 'xFolderID' cannot both be specified for the item

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800225: Cannot assign folder IDs to a non-record for item '{0}'

Cause: Cannot assign folder IDs to a non-record for the item

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800226: Cannot edit frozen item

Cause: Cannot edit frozen item

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800227: Cannot delete frozen item

Cause: Cannot delete frozen item

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800228: Cannot delete frozen item or item is in frozen folders.

Cause: Cannot delete frozen item or item is in frozen folders.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800229: The external item was successfully deleted

Cause: The external item was successfully deleted

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800230: Unable to get external item information.

Cause: Unable to get external item information.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800231: Unable to get external batch status details information.

Cause: Unable to get external batch status details information.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800232: Unable to reset external batch status information.

Cause: Unable to reset external batch status information.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800233: Notify External Batch Status Alerts

Cause: Notify External Batch Status Alerts

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800234: Unable to run external report

Cause: Unable to run external report

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800235: Error checking or creating WebDAV locks cache file.

Cause: Error checking or creating WebDAV locks cache file.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800236: Not allowed to lock this folder through WebDAV.

Cause: Not allowed to lock this folder through WebDAV.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800237: Unable to perform lock. Lock request did not send owner information.

Cause: Unable to perform lock. Lock request did not send owner information.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800238: Unable to lock file. All locks must be requested as exclusive.

Cause: Unable to lock file. All locks must be requested as exclusive.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800239: Unable to lock file. Bad request.

Cause: Unable to lock file. Bad request.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800240: Unable to undo checkout during lock cleaning cycle.

Cause: Unable to undo checkout during lock cleaning cycle.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800241: The requested location does not exist.

Cause: The requested location does not exist.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800242: Infinity is not allowed. Please upgrade your web filter and restart the Content Server.

Cause: Infinity is not allowed. Please upgrade your web filter and restart the Content Server.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800243: Unable to lock file at this path. Please use the tip-revision path.

Cause: Unable to lock file at this path. Please use the tip-revision path.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800244: Unable to unlock file at this path. Please use the tip-revision path.

Cause: Unable to unlock file at this path. Please use the tip-revision path.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800245: Unable to put file at this path. Please only use the tip-revision path of an existing file.

Cause: Unable to put file at this path. Please only use the tip-revision path of an existing file.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800246: Unable to delete file at this path. Please use the tip-revision path.

Cause: Unable to delete file at this path. Please use the tip-revision path.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800247: Could not send WebDAV XML to client.

Cause: Could not send WebDAV XML to client.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800248: Error getting owner from lock {0}. Please ensure that your XML libraries are properly installed.

Cause: Error getting owner from lock. Please ensure that your XML libraries are properly installed.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800249: Could not parse incoming WebDAV XML request.

Cause: Could not parse incoming WebDAV XML request.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800250: Could not create WebDAV input stream from the DataBinder.

Cause: Could not create WebDAV input stream from the DataBinder.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800251: Could not get bytes from input stream.

Cause: Could not get bytes from input stream.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800252: Folio item {0} not found

Cause: Folio item not found

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800253: Could not write folio {0}

Cause: Could not write folio

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800254: Unable to save changes.

Cause: Unable to save changes.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800255: Unable to edit folio template.

Cause: Unable to edit folio template.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800256: Unable to create new folio.

Cause: Unable to create new folio.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800257: Unable to create new folio template.

Cause: Unable to create new folio template.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800258: Unable to create new template folio.

Cause: Unable to create new template folio.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800259: Unable to load folio node.

Cause: Unable to load folio node.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800260: Unable to load temporary folio node.

Cause: Unable to load temporary folio node.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800261: Unable to load folio edit page.

Cause: Unable to load folio edit page.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800262: Unable to generate unique ids.

Cause: Unable to generate unique ids.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800263: Unable to create folio snapshot.

Cause: Unable to create folio snapshot.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800264: Unable to lock folio.

Cause: Unable to lock folio.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800265: Unable to load archived folio.

Cause: Unable to load archived folio.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800266: Previous revision of the folio does not exist.

Cause: Previous revision of the folio does not exist.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800267: Unable to checkin archived folio item.

Cause: Unable to checkin archived folio item.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800268: Unable to create folio from basket.

Cause: Unable to create folio from basket.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800269: Unable to clone folio.

Cause: Unable to clone folio.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800270: Folio parent node data missing.

Cause: Folio parent node data missing.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800271: This service cannot edit folio templates.

Cause: This service cannot edit folio templates.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800272: Could not add folio to archive.

Cause: Could not add folio definition to archive.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800273: Unable to edit locked folio.

Cause: Unable to edit locked folio.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800274: Error indexing folio links.

Cause: Error indexing folio links.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800275: Declassify On Date is not a valid date

Cause: Declassify On Date is not a valid date

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800276: Publication Date is not a valid date

Cause: Publication Date is not a valid date

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800277: Failed to check in '{0}' freeze audit information. Please reference '{1}' audit log.

Cause: Failed to check in freeze audit information. Please reference audit log.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800278: Unable to run disposition action.

Cause: Unable to run disposition action.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800278: Installing the RelatedContent component...

Cause: Installing the RelatedContent component...

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

UCM-CS-800279: Offsite FTP cannot change to the direcotry '{0}'. Please make sure it exists on the FTP site.

Cause: Offsite FTP cannot change direcotry.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action. Also, examine the preceding or following log entriesthat are part of this message stack.
Level: 1

Type: ERROR

Impact: Error

96 UCS-45209 to UCS-45412

UCS-45209: UCS-45209: Could not find the Coherence cache "{0}" in JNDI. Will use a cache created from the com.tangosol.net.CacheFactory.

Cause: The cache was not defined in the web.xml.

Action: Define the cache in a resource-ref element in the web.xml
Level: 1

Type: WARNING

Impact: Process

UCS-45412: Could not find the Coherence cache "{0}" in JNDI. Will use a cache created from the com.tangosol.net.CacheFactory.

Cause: The cache was not defined in the web.xml.

Action: Define the cache in a resource-ref element in the web.xml
Level: 1

Type: WARNING

Impact: Process

97 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-00004: Headers:

Cause: The application was running in debug mode. Logs all HTTP request headers.

Action: Turn off the debug mode.
Level: 32

Type: NOTIFICATION

Impact:

UIX-00005: Header {0} = {1}

Cause: The application was running in debug mode. Logs all the HTTP request header names and their values in debug mode.

Action: Turn off the debug mode.
Level: 32

Type: NOTIFICATION

Impact:

UIX-00005: Header {0} = {1}

Cause: The application was running in the debug mode. Logs all the HTTP request header names and their values in debug mode.

Action: Turn off the debug mode.
Level: 32

Type: NOTIFICATION

Impact:

UIX-00006: Requested page = {0}

Cause: The application was running in the debug mode.

Action: Turn off debug mode.
Level: 32

Type: NOTIFICATION

Impact:

UIX-00007: Page state: {0}

Cause: The application was running in the debug mode.

Action: Turn off debug mode.
Level: 32

Type: NOTIFICATION

Impact:

UIX-00008: Event = {0}

Cause: The application was running in debug mode.

Action: Turn the debug mode off.
Level: 32

Type: NOTIFICATION

Impact:

UIX-00009: Parameter {0} = {1}

Cause: The application was running in debug mode.

Action: Turn the debug mode off.
Level: 32

Type: NOTIFICATION

Impact:

UIX-00010: Rendering page = {0}

Cause: The application was running in debug mode.

Action: Turn off the debug mode.
Level: 32

Type: NOTIFICATION

Impact:

UIX-00011: finished doGet

Cause: The application was running in debug mode.

Action: Turn off the debug mode.
Level: 32

Type: NOTIFICATION

Impact:

UIX-00012: Time (s): {0}

Cause: The application was running in debug mode.

Action: Turn off the debug mode.
Level: 32

Type: NOTIFICATION

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:

98 UPGAST-00001 to UPGAST-02007

UPGAST-00001: unable to continue due to an unexpected error

Cause: An unexpected error occurred.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00002: Invalid argument {0}; an argument must begin with a hyphen.

Cause: A command-line argument did not start with a hyphen.

Action: Run the command again, using a hyphen to identify any arguments. Enter the command ua -help for details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00003: invalid argument {0}

Cause: The specified argument was not recognized.

Action: Run the command again, specifying a valid argument. Enter the command ua -help for details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00004: Value for argument {0} not supplied.

Cause: The value for a command-line argument was not specified.

Action: Run the command again, specifying the required value for the command-line argument. Enter the command ua -help for details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00005: Mandatory argument {0} not supplied.

Cause: A mandatory command-line argument was not supplied.

Action: Run the command again, specifying the mandatory command-line argument. Enter the command ua -help for details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00006: Mandatory arguments {0} not supplied.

Cause: The listed mandatory command-line arguments were not supplied.

Action: Run the command again, specifying each mandatory command-line argument. Enter the command ua -help for details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00007: Invalid source Oracle home directory: {0}.

Cause: The source Oracle home directory did not exist or cannot be accessed.

Action: Run the command again, specifying a valid source Oracle home directory.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00008: Invalid Oracle Universal Installer inventory location file: {0}.

Cause: The Oracle Universal Installer inventory location file was not found.

Action: Run the command again, specifying a valid Oracle Universal Installer inventory location file.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00009: Invalid log level: {0}.

Cause: The log level specified was not recognized.

Action: Run the command again, specifying a valid log level. See the command line help for details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00010: Port number {0} is not valid.

Cause: The port number specified was not a positive numeric value or was out of range.

Action: Run the command again, specifying a valid port number.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00011: Host name {0} is not valid or unknown.

Cause: Lookup of the specified host name failed.

Action: Run the command again, specifying a valid host name.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00012: Required port is missing.

Cause: A required port was not entered.

Action: Enter the required port.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00013: Invalid source Oracle home. The source Oracle home must be an Oracle home found in the Oracle Universal Installer inventory.

Cause: The specified source Oracle home directory did not exist in the Oracle Universal Installer inventory.

Action: Run the command again, specifying a valid source Oracle home directory.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00014: unable to connect to WebLogic Server at {0}:{1}

Cause: Failed connecting to the WebLogic Server at the specified host and port.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00015: Invalid Oracle instance home directory: {0}.

Cause: The Oracle instance home directory did not exist or cannot be accessed.

Action: Run the command again, specifying a valid Oracle instance home directory.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00016: Required password is missing.

Cause: A required password was not entered.

Action: Enter the required password.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00019: Unable to connect to database. {0}.

Cause: The database connection failed for the specified reason.

Action: Correct the problem using information provided in the log file; then retry the operation.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00020: Required connect string is missing.

Cause: A required connect string was not entered.

Action: Enter the required connect string.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00021: Required user name is missing.

Cause: A required user name was not entered.

Action: Enter the required user name.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00022: The source file {0} does not exist.

Cause: The source file for a file copy operation did not exist.

Action: Check the location of the specified file. This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00023: cannot read file {0}

Cause: The specified file could not be read.

Action: Check the permissions of the specified file and ensure that the file has read access.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00024: unable to expand wildcard file specification {0}

Cause: The specified file specification could not be expanded.

Action: See log file for details. This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00025: The directory {0} is not an Oracle instance home directory.

Cause: The directory specified was not a valid Oracle instance home directory.

Action: Run the command again, specifying a valid destination Oracle instance home directory.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00026: The source Oracle home installation type must be an Identity Management installation type. {0} is not an Identity Management installation type.

Cause: An incorrect source Oracle home was specified.

Action: Specify a source Oracle home that is an Identity Management installation type.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00027: The source Oracle home installation type must be a middle-tier installation type. {0} is not a middle-tier installation type.

Cause: An incorrect source Oracle home was specified.

Action: Specify a source Oracle home that is a middle-tier installation type.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00028: Required service name is missing.

Cause: A required service name was not entered.

Action: Enter the required service name. A service name typically includes the domain; for example, db1.example.com.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00030: Required Oracle instance home directory is missing.

Cause: A required Oracle instance home directory was not entered.

Action: Enter the required Oracle instance home directory.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00031: unable to get the active DomainMBean for the WebLogic Server domain

Cause: Failed getting the active DomainMBean for the WebLogic Server domain.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00032: unable to communicate with the WebLogic Server

Cause: Communication with the WebLogic Administrative Server was either lost or never established.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00033: unable to create a datasource definition named {0}

Cause: The creation of a domain-level datasource in the WLS Adminisrtation Server failed.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00034: unable to establish an EDIT connection

Cause: The connection to the Edit service in the WLS Administration Server failed.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00035: unable to save configuration changes

Cause: Verification in the WLS Administration Server failed.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00036: unable to start an edit operation

Cause: The Edit service in the WLS Administration Server failed to start an edit operation.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00037: unable to fetch or store attribute "{0}" in the WebLogic Server

Cause: This is an internal logic error. The most common cause is an incorrect attribute name.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00038: unable to locate an MBean named "{0}"

Cause: One of the upgrade steps was looking for an MBean with this name. That is was not found might or might not be an error, depending on context.

Action: See the secondary error message for additional details.
Level: 1

Type: WARNING

Impact: Upgrade

UPGAST-00039: Portal middle-tier upgrade does not allow the -noRetainPorts command-line argument.

Cause: The -noRetainPorts command-line argument was specified during a Portal middle-tier upgrade.

Action: Rerun the upgrade specifying the -retainPorts command-line argument
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00040: unable to get the DomainRuntimeMBean for the WebLogic Server domain

Cause: Failed getting the DomainRuntimeMBean for the current WebLogic Server domain.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00041: unable to determine OID and RDBMS location

Cause: Not all of the needed information was supplied on the command line.

Action: Specify -dbHost -dbPort -dbServiceName -oidHost and -oidSslPort options.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00042: unable to resolve OPMN MBean

Cause: unable to find management information for the non-J2EE components

Action: Make sure that nonJ2EE components have been configured with the WLS Admin Server.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00043: The -noStopComponents argument cannot be specified along with the retain ports option.

Cause: The option to not stop source components was specified with the retain ports option.

Action: Run the command again, without specifying -noStopComponents.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00044: The source Oracle home does not contain any components which require an upgrade.

Cause: The specified source Oracle home directory did not contain any components that would require an upgrade.

Action: Run the command again, specifying a valid source Oracle home directory.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00045: The version of the source Oracle home is not supported.

Cause: The specified source Oracle home directory was not a supported version. For middle-tier upgrade, the source Oracle home version must be 10.1.2 or 10.1.3. For Identity Management upgrade, the source Oracle home version must be 10.1.2 or 10.1.4.

Action: Run the command again, specifying a valid source Oracle home directory.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00047: Upgrades of BAM schemas are not allowed from this type of Oracle home.

Cause: The user has chosen to perform a BAM schema upgrade from an Oracle home that was not a SOA Oracle home.

Action: Perform the BAM schema upgrade from a SOA Oracle home.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00048: unable to open the log file

Cause: failed to open the log file

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00049: unable to read the log file

Cause: failed to read the log file

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00050: unable to create logging directory: {0}

Cause: The directory for log files could not be created.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00051: unable to create the log file

Cause: failed to create the log file

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00052: unable to initialize logging

Cause: Initialization of logging failed

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00053: No upgrade components were found in the config file {0}.

Cause: No upgrade components in the specified configuration file.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00054: error loading config file {0}

Cause: failed to load the configuration file

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00055: error reading the Oracle Universal Installer inventory

Cause: An error occurred while reading the Oracle Universal Installer inventory.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00056: error initializing upgrade plug-in for {0}

Cause: An unexecpted error occurred initializing an upgrade plug-in.

Action: Contact Oracle Support Services. See the secondary error message for additional details.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00057: Invalid source data home directory: {0}.

Cause: The source data home directory did not exist or cannot be accessed.

Action: Run the command again, specifying a valid source data home directory.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00058: {0} file does not exist or cannot be accessed.

Cause: The specified file did not exist or could not be accessed.

Action: Make sure the path to the file is correct.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00059: Invalid database type: {0}.

Cause: The database type specified was not recognized.

Action: Run the command again, specifying a valid database type. See the command line help for details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00060: An invalid installation type {0} has been found in properties file {1}.

Cause: The installation type found in the source Oracle home was not supported.

Action: Specify a source Oracle home that has a supported installation type.
Level: 1

Type: SET_AT_RUNTIME

Impact: Upgrade

UPGAST-00061: installation type not found

Cause: The installation type of the source Oracle home could not be determined.

Action: Ensure that the source Oracle home is a supported version and is working properly.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00062: An invalid installation type has been found in source Oracle home {0}.

Cause: The installation type of the source Oracle home was not supported.

Action: Ensure that the source Oracle home is a supported version and is working properly.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00063: unable to load the properties file {0}

Cause: An error was encountered reading or parsing the properties file of the source Oracle home. The information in the ias.properties file is used to determine the type of the source Oracle home.

Action: See the secondary message for additional details.
Level: 1

Type: WARNING

Impact: Upgrade

UPGAST-00064: no components need to be upgraded

Cause: No components were found in the source Oracle home that need upgrading. An upgrade will not be needed.

Action: No action needed.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGAST-00065: Configuration parameter {0} not found in source Oracle home {1}.

Cause: The information in the ias.properties file is used to determine the type and contents of the source Oracle home. In this case, a parameter in the properties file was missing and, as a result, the upgrade cannot proceed.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00066: Configuration parameter {0} has invalid value of {1} in source Oracle home {2}.

Cause: The information in the ias.properties file is used to determine the type and contents of the source Oracle home. In this case, a parameter in the properties file was invalid and, as a result, the upgrade cannot proceed.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00067: One or more errors occurred while identifying components to be upgraded.

Cause: Errors were encountered while analyzing the source Oracle home.

Action: See the log file for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00068: One or more errors occurred while initializing components to be upgraded.

Cause: Errors were encountered while setting up the components upgrade software.

Action: See the log file for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00069: Examination found that no components need to be upgraded. No upgrade will be performed.

Cause: No components were identified as needing upgrade during the examinaton phase. No upgrade will be performed.

Action: No action needed.
Level: 1

Type: WARNING

Impact: Upgrade

UPGAST-00073: failed to set startup type to manual for Windows service {0}

Cause: An error was encountered when changing the startup mode of a Windows service. At the end of the upgrade process, each Windows service associated with the 10g Oracle home is set to manual startup. Windows services in the source home must be set to manual startup to prevent resource conflicts with the 11g upgraded instance.

Action: Using the Windows Services utility, manually set the startup type for the specified Windows service.
Level: 1

Type: WARNING

Impact: Upgrade

UPGAST-00074: spawned process timed out

Cause: A spawned process stopped responding.

Action: Examine the log file to determine what actions were being performed when the error occurred.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00075: spawn process exception

Cause: An error was encountered spawning a process.

Action: Examine the log file to determine what actions were being performed when the error occurred.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00076: spawned process exception

Cause: An error was encountered in a spawned process.

Action: Examine the log file to determine what actions were being performed when the error occurred.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00077: The IP address of the source host {0} cannot be determined.

Cause: The network address of a host could not be determined.

Action: Check the validity of the specified host.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00078: The IP address of the destination host {0} cannot be determined.

Cause: The network address of a host could not be determined.

Action: Check the validity of the specified host.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00079: failed to create temporary directory: {0}

Cause: An error was encountered creating a temporary directory.

Action: Ensure that the directory location exists and is not protected.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00080: failed to start WebLogic Server {0}

Cause: An error was encountered starting a WebLogic Server.

Action: Examine the log file to determine the reason why the WebLogic server failed to start.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00081: failed to stop WebLogic Server {0}

Cause: An error was encountered stopping a WebLogic Server.

Action: Examine the log file to determine the reason why the WebLogic server failed to stop.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00082: Required Oracle Single Sign-On policy.properties file is missing.

Cause: The required Oracle Single Sign-On policy.properties file was not entered.

Action: Enter the required Oracle Single Sign-On policy.properties file.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00084: {0} file does not exist or cannot be accessed.

Cause: The specified Oracle Single Sign-On policy.properties file did not exist or could not be accessed.

Action: Specify a valid Oracle Single Sign-On policy.properties file.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00085: unable to load the properties file {0}

Cause: An error was encountered reading or parsing the Oracle Single Sign-On properties file.

Action: See the secondary message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00086: expected property "DefaultAuthLevel" not found in {0}

Cause: The Oracle Single Sign-On properties file does not contain an expected property.

Action: Specify a valid Oracle Single Sign-On policy.properties file.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00087: Either the ASA install directory, the ARM install directory, or both install directories must be specified.

Cause: A required ASA install directory or ARM install directory was not entered.

Action: Enter at least one of the install directories.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00088: Argument {0} is not valid for this upgrade operation.

Cause: The specified argument could not be used with the type of upgrade attempted.

Action: Run the command again, without the invalid argument.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00089: Required schema name is missing.

Cause: A required schema name was not entered.

Action: Enter the required schema name.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00090: failed to connect to Oracle Internet Directory

Cause: unable to connect to the Oracle Internet Directory server

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00091: errors during the examine of components

Cause: Errors were encountered while checking components' readiness for upgrade.

Action: See the log file for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00092: errors during the upgrade of components

Cause: Errors were encountered while upgrading one or more components.

Action: See the log file for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00093: {0} directory does not exist or cannot be accessed.

Cause: The specified directory did not exist or could not be accessed.

Action: Specify a valid directory.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00094: Either the -asaDir argument, -armDir argument, or both arguments must be specified.

Cause: A required -asaDir argument or -armDir argument was not entered on the command-line.

Action: Enter at least one of the required arguments.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00095: error setting the Oracle look-and-feel for the graphical user interface

Cause: An internal error occurred while setting the appearance for the graphical user interface.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00096: error initializing the help system

Cause: An internal error occurred while setting up the help system.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00097: The IP address of the host {0} cannot be determined.

Cause: The network address of the specified host could not be determined.

Action: Check the validity of the specified host.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00098: A running Oracle Internet Directory server cannot be located.

Cause: No running Oracle Internet Directory server was detected in the 11g configuration. Upgrade needs this server.

Action: Ensure that at least one Oracle Internet Directory has been configured and is running.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00099: End point named {0} cannot be found for {1}.

Cause: The named end point could not be located for a component.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00100: Required Oracle Universal Content Management directory is missing.

Cause: The required Oracle Universal Content Management directory was not entered.

Action: Enter the required Oracle Universal Content Management directory.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00101: Unable to access the schema version registry. Reason: {0}.

Cause: Access to schema version registry failed for the specified reason.

Action: See log file for details. Correct the problem causing the failure to connect to the schema version registry and then retry connecting.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00102: Required ODS schema password is missing.

Cause: The required ODS schema password was not entered.

Action: Enter the required ODS schema password.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00103: failed to get Oracle Internet Directory host and port

Cause: An error was encountered while trying to determine host and port information for an LDAP server.

Action: See log file for details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00104: Required Oracle Internet Directory password is missing.

Cause: The required Oracle Internet Directory password was not entered.

Action: Enter the required Oracle Internet Directory password.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00105: Required SYS password is missing.

Cause: The required SYS password was not entered.

Action: Enter the required SYS password.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00106: Identity Management upgrade not allowed from this type of Oracle home.

Cause: The user has chosen to perform an Identity Management upgrade from an Oracle home that does not allow this type of upgrade.

Action: Perform the upgrade from an Identity Management Oracle home.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00107: The DISPLAY environment variable is not set. The graphical user interface (GUI) requires that this environment variable be set on UNIX.

Cause: The required DISPLAY environment variable was not defined.

Action: Set the required DISPLAY environment variable and then rerun the Assistant.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00108: Required Oracle Universal Content Management directory is missing.

Cause: The required Oracle Universal Content Management directory was not entered.

Action: Enter the required Oracle Universal Content Management directory.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00109: The destination Oracle instance is not an Identity Management instance.

Cause: An incorrect destination Oracle instance was specified.

Action: Specify a destination Oracle instance that is an Identity Management instance.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00110: The destination Oracle instance is not a middle-tier instance.

Cause: An incorrect destination Oracle instance was specified.

Action: Specify a destination Oracle instance that is a middle-tier instance.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00111: Verify instance option is not available for this type of Oracle home.

Cause: The user has chosen to perform a verify instance from a Oracle home that does support verify.

Action: None.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00112: A middle-tier upgrade is not allowed from an Identity Management Oracle home.

Cause: The user has chosen to perform a middle-tier upgrade from an Oracle home that does not allow this type of upgrade.

Action: Perform the upgrade from an Oracle home that allows middle-tier upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00113: Specify which schemas are to be upgraded using the {0} and {1} arguments.

Cause: The user has chosen to perform a metadata repository upgrade without specifying which schemas to upgrade.

Action: Specify the schemas to be upgraded.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00114: Upgrades of Oracle Portal and Discoverer schemas are not allowed from this type of Oracle home.

Cause: The user has chosen to perform an Oracle Portal or Discoverer schema upgrade from an Oracle home that does not allow this type of upgrade.

Action: Perform the upgrade from an Oracle home that allows Oracle Portal or Discoverer schema upgrades.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00115: Upgrades of B2B schemas are not allowed from this type of Oracle home.

Cause: The user has chosen to perform a B2B schema upgrade from an Oracle home that is not a SOA Oracle home.

Action: Perform the B2B schema upgrade from a SOA Oracle home.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00116: Select which metadata repository schemas are to be upgraded.

Cause: The user has chosen to upgrade metadata repository schemas but did not specify which schemas to upgrade.

Action: Specify the metadata repository schemas to be upgraded.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00117: Argument {0} is not valid with the graphical user interface.

Cause: The specified argument cannot be used with the graphical user interface.

Action: Run the command again, without the invalid argument.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00118: End point named {0} not found while setting port values.

Cause: An attempt was made to change a port number. A required ListeningEndpoint attribute was not found.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00119: Port value {1} cannot be set for the end point named {0}.

Cause: An error occurred while setting a new port value.

Action: Contact Oracle Support Services.
Level: 1

Type: SET_AT_RUNTIME

Impact: Upgrade

UPGAST-00120: The password for schema {0} cannot be obtained from the credential storage facility (CSF).

Cause: An error occurred while fetching a stored password.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00121: A middle-tier upgrade is not allowed from a SOA Oracle home.

Cause: The user has chosen to perform a middle-tier upgrade from an Oracle home that does not allow this type of upgrade.

Action: Perform the upgrade from an Oracle home that allows middle-tier upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00122: Select a middle tier component to be upgraded.

Cause: The user has chosen to upgrade middle tier components but did not specify which component to upgrade.

Action: Specify the middle tier component to be upgraded.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00123: The database cluster specification contains syntax errors.

Cause: The cluster specification must be of the form "host:port:instance^...@service". See documentation for further details.

Action: Correct the errors.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00124: The root script file {0} cannot be written.

Cause: A file I/O error has prevented the creation of a necessary root script file.

Action: Check that Oracle home directory protections allow the file to be created.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00125: The Oracle home that the Assistant is running from is not found in the Oracle Universal Installers inventory.

Cause: The Assistant was not found in the Oracle Universal Installers inventory.

Action: Specify an inventory location pointer file on the command line or reinstall an Oracle home for the Assistant to run from.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00126: The Assistant is not supported in this Oracle home.

Cause: The Assistant was not supported in this Oracle home and therefore could not be run from this Oracle home.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00127: Oracle Internet Directory upgrade failed. The Assistant will not proceed.

Cause: It is not possible to continue with the upgrade of the other components in the instance because they depend on the successful completion of Oracle Internet Directory upgrade.

Action: See log file for details. Correct the problem and retry.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00128: Oracle Internet Directory examination failed. The Assistant will not proceed.

Cause: It is not possible to continue with the examination of the other components in the instance because they depend on the successful completion of Oracle Internet Directory examination.

Action: See log file for details. Correct the problem and retry.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00129: Registered database server not found for {0}:{1} service {2}.

Cause: A database server was not registered with the supplied connection information.

Action: Check that information entered is correct.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00130: Registered schema named {0} not found.

Cause: A schema was not registered under the supplied name.

Action: Check spelling of schema name.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00131: Required ASA install directory is missing.

Cause: A required ASA install directory was not entered.

Action: Enter the required ASA install directory.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00132: Required ARM install directory is missing.

Cause: A required ARM install directory was not entered.

Action: Enter the required ARM install directory.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00133: unable to get host name or port for a database server object

Cause: No value was obtained for the host name or port number.

Action: Check that the database server is properly registered at farm level and that host name and port values are correct.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00134: Required dump file name is missing.

Cause: A required dump file was not entered.

Action: Enter the required dump file name.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00135: Required password was not supplied

Cause: No value was entered in response to a password prompt.

Action: Run the Assistant again and supply all required passwords.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00136: The source install directory is not a valid Oracle Identity Manager 9.1 installation.

Cause: The source install directory specified did not include the mandatory configuration files and directories.

Action: Check the log file for additional details. Specify a valid Oracle Identity Manager 9.1 source install directory.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00137: Required Oracle Universal Records Management directory is missing.

Cause: The required Oracle Universal Records Management directory was not entered.

Action: Enter the required Oracle Universal Records Management directory.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00138: upgrade exception occurred

Cause: An unexpected upgrade exception has occurred.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00139: Upgrading the OWA packages to a new version as the database contains the older version. This process might take time.

Cause: The OWA software package of Portal was detected, and its presence requires additional time for the upgrade to complete.

Action: No action needed.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGAST-00140: Startup of {0} OPMN managed processes failed (Reason: {1}).

Cause: The starting of OPMN or OPMN managed processes has failed.

Action: Check the log file for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00141: startup of 11g OPMN managed processes failed

Cause: The starting of OPMN or OPMN managed processes has failed.

Action: Check the log file for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00142: User chose to cancel rather than upgrade OID without DIP.

Cause: OID and DIP are both configured in the source Oracle Home, but only OID in the destination. User chose not to proceed.

Action: Configure DIP in the destination Instance and run the Assistant again.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00143: Although an Oracle Directory Integration Platform instance is configured within your source environment, one was not found within the destination environment. If you proceed with upgrade without configuring DIP in your destination environment, only OID will be upgraded. You will not be able to use the Assistant to upgrade DIP at a later time. Would you like to proceed with the upgrade?

Cause: OID and DIP are both configured in the source Oracle home, but only OID in the destination.

Action: If you want to upgrade DIP, configure DIP in the destination Instance and run the Assistant again.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00144: Specify which component to be upgraded using either the {0}, {1}, or {2} argument.

Cause: The user has chosen to perform a middle tier upgrade without specifying which component to be upgraded.

Action: Specify the component to be upgraded.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00145: Specify only one component to be upgraded using either the {0}, {1}, or {2} argument.

Cause: The user has chosen to perform a middle tier upgrade and has specified more than one component to be upgraded.

Action: Specify only one component to be upgraded.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00146: PostgreSQL JDBC driver is missing or corrupted {0}.

Cause: The user has chosen an upgrade with a PostgreSQL database but the JDBC driver that Oracle has certified for use is either missing or corrupt.

Action: Locate the precise version of the PostgreSQL JDBC driver jar file that Oracle has certified, and copy it into the ORACLE_HOME/jlib direcotry. The name of the jar file must match the expected name, and the SHA1 signature of the file must match the expected value.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00147: Required Oracle Identity Manager namespace is missing.

Cause: The required Oracle Identity Manager namespace was not entered.

Action: Enter the required Oracle Identity Manager namespace.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00148: Required Oracle Universal Records Management directory is missing.

Cause: The required Oracle Universal Records Management directory was not entered.

Action: Enter the required Oracle Universal Records Management directory.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00149: Required RPD file location is missing.

Cause: A required RPD file location was not entered.

Action: Enter the required RPD file location.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00150: Required catalog directory is missing.

Cause: A required catalog directory was not entered.

Action: Enter the required catalog directory.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00151: Upgrade repository or upgrade catalog must be selected.

Cause: The upgrade repository checkbox or the upgrade catalog checkbox was not selected.

Action: Select the upgrade repository checkbox or the upgrade catalog checkbox, or both.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00152: Required confirm password is missing.

Cause: A required confirm password was not entered.

Action: Enter the required confirm password.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00153: Password does not match the confirm password.

Cause: The password and confirm password were not the same.

Action: Enter a matching password and confirm password.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00154: Password must be at least 8 characters in length and contain both numbers and non-numbers.

Cause: The password entered did not meet the minimum password length requirements or contained characters that were not a mix of numbers and non-numbers.

Action: Enter a password of at least 8 charaters in length that contains a mix of numbers and non-numbers.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00155: Unable to connect to ODI Supervisor account: {0}.

Cause: The ODI supervisor user name or password were incorrect, or the ODI master repository name was incorrect, or an internal error occured

Action: Correct the problem by entering the correct user name and password for both the ODI master repository and the ODI supervisor account; then, retry the operation.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00156: The catalog directory is not a valid catalog directory.

Cause: The catalog directory specified did not include the mandatory file root.atr.

Action: Specify a valid catalog directory.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00157: Both {0} and {1} must be specified or both {2} and {3} must be specified.

Cause: A required RPD file and RPD administrator user name was not entered or a required catalog directory and catalog deliveries directory was not entered.

Action: Specify the RPD File and RPD administrator user name or the catalog directory and catalog deliveries directory, or all.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00158: Required BI Publisher repository directory is missing.

Cause: A required BI Publisher repository directory was not entered.

Action: Enter the required BI Publisher repository directory.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00159: Required 10g RPD admininstrator user name is missing.

Cause: A required 10g RPD admininstrator user name was not entered.

Action: Enter the required 10g RPD admininstrator user name.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00160: unable to create directory: {0}

Cause: The specified directory could not be created.

Action: Check the permissions for creating the specified directory.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00161: The ASA application directory is not a valid ASA application directory.

Cause: The ASA application directory specified did not include the mandatory files bharosauio.properties, bharosa_client.properties, and bharosa_common.properties

Action: Specify a valid ASA application directory.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00162: The ARM application directory is not a valid ARM application directory.

Cause: The ARM application directory specified did not include the mandatory files bharosa_server.properties and bharosa_common.properties

Action: Specify a valid ARM application directory.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00163: Specify which component to be upgraded using either the {0} or the {1} argument.

Cause: The user has chosen to perform a middle tier upgrade without specifying which component to be upgraded.

Action: Specify the component to be upgraded.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00164: Specify only one component to be upgraded using either the {0} or the {1} argument.

Cause: The user has chosen to perform a middle tier upgrade and has specified more than one component to be upgraded.

Action: Specify only one component to be upgraded.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00165: {0} is a directory instead of a RPD file.

Cause: The RPD file specified was not a file.

Action: Specify a valid RPD file.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00166: Required E-Business Suite data template directory is missing.

Cause: A required E-Business Suite data template directory was not entered.

Action: Enter the required E-Business Suite data template directory.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00167: Upgrade BI Publisher repository directory option or upgrade E-Business Suite data template directory option must be selected.

Cause: The upgrade BI Publisher repository directory option or the upgrade E-Business Suite data template directory option was not selected.

Action: Choose either the upgrade BI Publisher repository directory option or the upgrade E-Business Suite data template directory option.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00168: {0} or {1} must be specified, but not both

Cause: A required argument was not specified or you have specified both arguments.

Action: Specify only one of the required arguments.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00169: Required catalog deliveries directory is missing.

Cause: A required catalog deliveries directory was not entered.

Action: Enter the required catalog deliveries directory.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00170: unable to validate the 10g RPD administrator user name and password. Reason: {0}.

Cause: The validation of the 10g RPD administrator user name and password failed for the specified reason.

Action: Correct the problem using information provided; then retry the operation.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00171: A middle-tier upgrade is not allowed from a Web Center Oracle home.

Cause: The user has chosen to perform a middle-tier upgrade from an Oracle home that does not allow this type of upgrade.

Action: Perform the upgrade from an Oracle home that allows middle-tier upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00172: The database credentials entered are not for a valid OAAM database.

Cause: The user has entered incorrect OAAM database credentials.

Action: Enter valid OAAM datbase credentials. See the secondary error message.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00173: The plugin for {0} has requested an input value named {1} but that name is not in the template.

Cause: The plugin is doing something inconsistently.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00174: failed to create or write to response file

Cause: The file specified for saving responses could not be created or written to.

Action: Specify a file in a location that is writable.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00175: Can not read response file {0}.

Cause: The file specified for reading responses does not exist, or can not be read.

Action: Specify a readable response file.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00176: Response file specifies an unknown upgrade step {0}.

Cause: The response file specifies an upgrade step that is unknown in this Fusion Middleware installation.

Action: Specify a response file generated for this installation.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00177: Response file line is not understood: {0}

Cause: The response file contains syntax errors.

Action: Specify a response file generated by the Patch Set Assistant.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00178: Response file specifies a bad input name, {0}.

Cause: The response file contains syntax errors, or is not of the correct version.

Action: Specify a response file generated by the Patch Set Assistant for this installation.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00179: unexpected internal error

Cause: An internal error occurred.

Action: See the secondary error message for additional details.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00180: error loading upgrade plug-in for {0}

Cause: An unexpected error occurred loading an upgrade plug-in.

Action: Contact Oracle Support Services. See the secondary error message for additional details.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00181: error during execution of upgrade plug-in for {0}

Cause: An unexpected error occurred during execution of an upgrade plug-in.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00182: The examination phase for plug-in {0} will not be run due to a previous error.

Cause: An error occurred when loading or initializing the plug-in which prevents the examiniation phase from running.

Action: Review the log file for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00183: The upgrade phase for plug-in {0} will not be run due to a previous error.

Cause: An error occurred when loading or initializing the plug-in which prevents the upgrade phase from running.

Action: Review the log file for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00184: Response file specifies a bad input value, {0}.

Cause: The response file contains syntax errors, or is not of the correct version.

Action: Specify a response file generated by the Patch Set Assistant for this installation.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00185: failed to load JDBC driver

Cause: There was a failure loading a JDBC driver.

Action: See the log file for details. This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00186: Unable to connect to database. Some fields are empty.

Cause: Required fields to connect to a database were not supplied.

Action: Enter the missing required fields and rerun.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00187: Unable to connect to WebLogic Admin Server. Some fields are empty.

Cause: Required fields to connect to a WebLogic Admin Server were not supplied.

Action: Enter the missing required fields and rerun.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00188: SQL script {0} does not exist.

Cause: SQL script could not be located. This is an internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00189: Exception raised while running an external command.

Cause: An exception was raised while running an external command (such as sqlplus) in a subprocess. Check the stack trace for detailed information.

Action: Attempt to correct the environment problem if any, then retry the upgrade. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00190: {0} component version is {1}, status is {2}, upgraded flag is {3}

Cause: During upgrade a component reported a successful upgrade but the SCHEMA_VERSION_REGISTRY was not updated correctly. This is an internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00191: unable to validate the SCHEMA_VERSION_REGISTRY for component {0}

Cause: An unexpected error occurred validating the SCHEMA_VERSION_REGISTRY. This is an internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00192: dependency by component {0} on component {1} is unresolved

Cause: An expected dependency was not found when discovering upgrade components.

Action: Make sure the dependent component has been installed.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00193: error during preparation of upgrade plug-in for {0}

Cause: An unexpected error occurred during preparation of the environment for an upgrade plug-in.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00194: failed to load JDBC driver

Cause: There was a failure loading a JDBC driver.

Action: See the log file for details. This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00196: A validation function for plug-in {0} will not be run due to a previous error.

Cause: An error occurred when loading or initializing the plug-in which prevents the validation function from executing.

Action: Review the log file for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00197: No upgrade descriptor files were found in the Oracle Fusion Middleware home.

Cause: There was a problem installing the Oracle Fusion Middleware software.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00198: Descriptor tag {0} is only allowed in components of type={1}

Cause: An upgrade plugin descriptor is improperly formed,

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00199: unable to connect to the SOA Server at {0}:{1}

Cause: Failed connecting to the SOA Server at the specified host and port.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00200: Message reference {0} in item {1} is not defined.

Cause: An upgrade plugin descriptor is improperly formed,

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00201: User must select at least one of the BIEE or BIP upgrade-content check boxes.

Cause: During a BIPLATFORM schema upgrade the user unchecked both the BIEE and BIP content check boxes. At least one of these boxes must be checked.

Action: Check the BIEE content box, the BIP content box, or both check boxes before continuing
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00202: Unable to validate credentials. Some fields are empty.

Cause: Required fields to validate credentials were not supplied.

Action: Enter the missing required fields and rerun.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00203: Internal Error, validate method is not implemented by upgrade plug-in.

Cause: Required validate method was not implemented by upgrade plug-in.

Action: Implement the required validate method.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00795: Verify instance option is not available from an Application Developer Oracle home.

Cause: The user has chosen to perform a verify instance from an Application Developer Oracle home.

Action: None.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00796: A middle-tier upgrade is not allowed from an Application Developer Oracle home.

Cause: The user has chosen to perform a middle-tier upgrade from an Oracle home that does not allow this type of upgrade.

Action: Perform the upgrade from an Oracle home that allows middle-tier upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00797: Oracle Fusion Middleware Upgrade Assistant cannot be run from an Application Developer Oracle home.

Cause: The user has chosen to perform a upgrade from an Oracle home that does not allow an upgrade.

Action: None.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00798: Oracle Fusion Middleware Upgrade Assistant cannot be run from a Web Center Oracle home.

Cause: The user has chosen to perform a upgrade from an Oracle home that does not allow an upgrade.

Action: None.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00799: Verify instance option is not available from a Web Center Oracle home.

Cause: The user has chosen to perform a verify instance from a Web Center Oracle home.

Action: None.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00800: Oracle Fusion Middleware Patch Set Assistant cannot be run from a Web Tier Oracle home.

Cause: The user has chosen to perform a patch set upgrade from an Oracle home that does not allow a patch set upgrade.

Action: Perform the patch set upgrade from an Oracle home that allows a patch set upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-01001: Upgrade is unable to connect to SSL port of OID.

Cause: Repository upgrade framework was unable to connect to the OID server using the host name, SSL port number and password specified. The server might be down.

Action: Verify that the OID server is running. Verify that the host name, SSL port number, and cn=orcladmin password are correctly specified.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-01002: Upgrade is unable to connect to the metadata repository database.

Cause: Repository upgrade framework was unable to connect to the metadata repository database. The database might be down, or the password might be incorrect.

Action: Verify that the Repository Database instance and listener have been started. Verify that the user name and password are correct. Retry the operation.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-01003: Upgrade is unable to open XML file: {0}.

Cause: Repository upgrade framework was unable to open the xml file mrua.xml, or the file was corrupted.

Action: Verify that the file exists in the specified directory, and that the read permission on the file is set correctly. Examine the file to ensure that the contents are correct. Edit the file if needed to correct any errors.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-01004: Upgrade is unable to dynamically load component-specific software modules.

Cause: Repository upgrade framework was unable to dynamically load the Java classes of its component-specific software modules. mrua.xml file might have been corrupted.

Action: This is an internal error. Verify that the Java classpath has been correctly set, the mrua.xml file is correct, and that the .jar files for all component-specific software modules are present in the jlib directory. Contact Oracle Support Services for assistance.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-01005: error initializing component-specific software module {0}

Cause: Repository Upgrade was unable to initialize the named component-specific software module. This is an internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-01006: Schema upgrade failed for {0}.

Cause: Repository Upgrade framework detected that schema upgrade of the component named in the error message failed.

Action: Examine the upgrade log files for additional error messages. It may be possible to correct the problem and retry the upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-01007: Schema upgrade returned improper status.

Cause: The Repository Upgrade component-specific software module for the named component returned an incorrect status to the upgrade framework. This is an internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-01008: Schema examination failed for {0}.

Cause: Repository upgrade framework determined that the examination phase of upgrade failed for the named component. This is often due to a failed prerequisite check. No schemas changes have been made to the component that failed.

Action: Check the upgrade log files for the cause of the message. Correct the source of the problem if possible, and retry the examination. Do not go on to perform an actual upgrade in upgrade mode unless all components succeed during examination.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-01009: SQL script {0} does not exist.

Cause: The repository upgrade component-specific software module named in the error message attempted to run a SQL script that could not be located. This is an internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-01011: Verify that database version {0} has been certified with Oracle Fusion Middleware.

Cause: Repository upgrade framework determined that the database release number of the repository database is at a version that was not yet certified with Oracle Fusion Middleware repository upgrade at the time the product shipped. Upgrade will continue.

Action: Verify that this version of the database has been certified for use with Oracle Fusion Middleware repository upgrade. If upgrade is performed using an uncertified release of the database, errors may occur during or after the upgrade. Upgrade should not be performed using database releases that have not yet been certified for use with the current release of Oracle Fusion Middleware.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-01012: unable to load PL/SQL package DBMS_IAS_VERSION

Cause: Repository upgrade framework was unable to load or validate the PL/SQL package DBMS_IAS_VERSION. This is an internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INTERNAL_ERROR

Impact: Upgrade

UPGAST-01013: unable to load PL/SQL package DBMS_IAS_VERSION10G

Cause: Repository upgrade framework was unable to load or validate the PL/SQL package DBMS_IAS_VERSION10G. This is an internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INTERNAL_ERROR

Impact: Upgrade

UPGAST-01014: Component-specific software module raised an exception: {0}.

Cause: During repository upgrade one of the component-specific software modules raised an uncaught exception to the upgrade framework. This is an internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-01015: Some repository upgrade component-specific software modules report failure.

Cause: One or more component-specific software modules returned an error status during repository upgrade. Some other components might have upgraded successfully.

Action: Review the upgrade logs to determine which components have failed, and pinpoint the source of the errors for each component. Correct the conditions that caused the errors. It may be possible to rerun the upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-01016: Upgrade from OracleAS release {0} is not allowed.

Cause: Repository upgrade framework detected that the metadata repository is from an OracleAS release that is no longer supported for upgrade to the current release.

Action: Start with an OracleAS release that is directly upgradable to the current release. It may be necessary to perform the upgrade as a two-step processs. First uppgrade the repository to a newer release that is supported by the current release of Oracle Fusion Middleware. Then repeat the upgrade process from that supported release to the current release of Oracle Fusion Middleware.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-01017: Some Oracle Fusion Middleware components not set to VALID status in schema_version_registry. Check the log file.

Cause: During repository upgrade one or more components did not record the necessary version and status information in SCHEMA_VERSION_REGISTRY. This is an internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-01018: {0} component version is: {1} {2} upgraded flag is: {3}.

Cause: During repository upgrade one or more components reported a successful upgrade but the version and status information was not updated in SCHEMA_VERSION_REGISTRY. This is an internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-01019: {0} is not in schema_version_registry namespace {1}.

Cause: Repository upgrade framework detected that the named component was missing a required entry in SCHEMA_VERSION_REGISTRY. This might be caused by an internal error or incorrect configuration before the upgrade was performed. The component might not be recorded in the repository database.

Action: Verify that the component already has been created in the repository database by Repository Creation Utility (RCU) under the same namespace being used for upgrade. Retry the upgrade. If RCU has created the component schemas and the error persists, contact Oracle Support Services.
Level: 1

Type: INTERNAL_ERROR

Impact: Upgrade

UPGAST-01020: Oracle home {0} does not exist.

Cause: Repository upgrade framework detected that the OracleHome input parameter refers to a nonexistant or inacessible directory.

Action: Verify that the OracleHome parameter has been specified correctly and refers to an existing Oracle home directory. If the directory exists, verify that the file permissions on the directory permit access. Retry the upgrade operation.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-01021: Oracle home {0} does not contain the bin directory.

Cause: Repository upgrade framework determined that the OracleHome input parameter refers to an existing directory; however, that directory lacked a bin subdirectory. The directory did not appear to be a valid Oracle home.

Action: Verify that the OracleHome parameter refers to an existing Oracle home directory, which must contain a bin subdirectory. Retry the upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-01022: Metadata repository is at MRC version: {0}.

Cause: Repository upgrade detected that the metadata repository that was being upgraded is currently at the version listed in the message. This is an informational message.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGAST-01023: Metadata repository database is at RDBMS version: {0}.

Cause: Repository upgrade framework detected that the metadata repository database is at the version release number listed in the message. This is an informational message.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGAST-01024: Oracle home {0} does not contain the rdbms directory.

Cause: Repository upgrade framework determined that the OracleHome input parameter refers to an existing directory, however, that directory lacked the rdbm subdirectory. The directory did not appear to be a valid Oracle home.

Action: Verify that the OracleHome parameter points to an existing Oracle home directory that contains an rdbms subdirectory. Retry the upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-01025: Loaded PL/SQL package DBMS_IAS_VERSION.

Cause: Repository upgrade framework successfully loaded and validated the PL/SQL package DBMS_IAS_VERSION. This is an informational message.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGAST-01026: DBMS_IAS_VERSION package version is: {0}.

Cause: Repository upgrade framework determined that the PL/SQL package DBMS_IAS_VERSION was at the software revision level specified in the message. This is an informational message.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGAST-01027: not installed

Cause: Repository upgrade framework detected that a necessary software component was not installed. This is an internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-01028: All repository upgrade component-specific software modules report success.

Cause: Repository upgrade framework detected that all components reported success during the examination or upgrade phase of repository upgrade. All components returned either the upgrade successful or the already upgraded status. This message is displayed after repository upgrade has completed successfully. This is an informational message.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGAST-01029: All Oracle Fusion Middleware components set to VALID status in schema_version_registry.

Cause: Repository upgrade framework reports that all components were set to the VALID state in SCHEMA_VERSION_REGISTRY, and all component version numbers were correct. This is an informational message.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGAST-01030: Component {0} has valid schema_version_registry settings after upgrade.

Cause: The component named in the message had the correct and expected data in SCHEMA_VERSION_REGISTRY. This is an informational message.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGAST-01031: {0} is not in schema_version_registry namespace {1}.

Cause: The repository upgrade component-specific software module reported that an optional component was not found in SCHEMA_VERSION_REGISTRY. This is an informational message.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGAST-01032: {0} app_registry entry is: {1} {2}.

Cause: Repository Upgrade component-specific software module reported that the named component has an entry in the 10g APP_REGISTRY view. This is an informational message.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGAST-01033: {0} schema_registry entry is: {1} {2} namespace {3}.

Cause: Repository upgrade component-specific software module reported that the named component has this version and status information recorded in SCHEMA_VERSION_REGISTRY under the specified namespace. This is an informational message.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGAST-01034: Verify that connect string is correct and database listener process is started.

Cause: Repository upgrade framework was unable to connect to the metadata repository database. This might be caused by an invalid database connection string, or because the database listener was down.

Action: Verify that connect string is correct and database listener process is started.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-01035: Verify that user name and password are correct.

Cause: Repository upgrade framework was unable to connect to the metadata repository database. This might have been caused by an invalid user name or password. This is a warning message.

Action: Verify that user name and password are correct.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-01036: Connect as user 'SYS AS SYSDBA', not just 'SYS'.

Cause: Repository upgrade framework was unable to connect to the metadata repository database. The possible cause is that the user name must be SYS AS SYSDBA, not SYS. This is a warning message.

Action: Connect as user 'SYS AS SYSDBA', not just 'SYS'.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-01037: Start the database.

Cause: Repository upgrade framework was unable to connect to the metadata repository database. The possible cause is that the database instance is down and needs to be started. This is a warning message.

Action: Start the database.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-01038: Oracle Fusion Middleware Repository Upgrade Framework {0}

Cause: Repository upgrade framework reported its software product version. This is an informational message.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGAST-01039: error while reading from app_registry

Cause: The repository upgrade component-specific software module encountered an error while attempting to access the OracleAS 10g APP_REGISTRY view. This is an internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-01040: {0} is not present in app_registry.

Cause: The repository upgrade component-specific software module detected that a component is missing an entry in the OracleAS 10g APP_REGISTRY view. This error condition will cause the examination phase of upgrade to fail.

Action: Verify that the database being upgraded contains an OracleAS Metadata Repository. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-01041: {0} is not present in app_registry.

Cause: Repository upgrade component-specific software module detected that an optional component is missing from the 10g APP_REGISTRY view. This is an informational message.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGAST-01042: SQL version and status query failed for component {0}.

Cause: The repository upgrade component-specific software module encountered an error while trying to obtain version and status information for the component. This is an internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-01043: unable to connect to the source database

Cause: Repository upgrade framework was unable to connect to the source database instance. The database might be down, or the password might be incorrect.

Action: Verify that the source connect string, user name, and password are correct. Verify that the database server and listener are running. Examine the log file for additional information.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-01044: unable to connect to the target database

Cause: Repository upgrade framework was unable to connect to the target database instance. The database might be down, or the password might be incorrect.

Action: Verify that the target connect string, user name, and password are correct. Verify that the database server and listener are running. Examine the log file for additional information.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-01045: Database version {0} is not supported.

Cause: A database connection could not be established because the database type identifier was not recognized as one of the known types that are supported by Repository Upgrade.

Action: Use only a supported database type either Oracle or Microsoft.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-01047: Repository upgrade component-specific software module protocol error.

Cause: During execution of a repository upgrade component-specific software module, the upgrade mode was neither examine nor upgrade.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-01048: Repository upgrade internal protocol error.

Cause: During execution of schema upgrade an uncaught exception was rasied during the examine or upgrade phases.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-01050: error loading config file {0}

Cause: The Assistant failed to load its configuration file.

Action: See secondary message for details.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-01051: unable to connect to the Oracle B2B schema {0}

Cause: Repository upgrade framework was unable to connect to the Oracle B2B schema. The database might be down, or the password might be incorrect.

Action: Verify that the host, port, service name, and password are correct. Verify that the database server and listener are running. Examine the log file for additional information.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-01052: unable to connect to the Oracle BAM schema {0}.

Cause: Repository upgrade framework was unable to connect to the Oracle BAM database schema. The database might be down, or the password might be incorrect.

Action: Verify that the host, port, service name, and password are correct. Verify that the database server and listener are running. Examine the log file for additional information.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-01060: SCHEMA_VERSION_REGISTRY table CUSTOM1 or CUSTOM2 column is missing.

Cause: Repository Upgrade framework detected that the SCHEMA_VERSION_REGISTRY database table is missing the CUSTOM1 or CUSTOM2 columns. This error message identifies an older preproduction version of schema version registry table that is no longer compatible with current software. The two custom columns need to be added to correct the problem. This is an interim error condition that can occur during product development cycle but will not occur in the production version of Oracle Fusion Middleware.

Action: The two missing columns CUSTOM1 and CUSTOM2 need be added to the schema version registry table. After the columns have been added this error will not appear again, and OFM Upgrade Assistant can be run again. To add the missing columns the user should connect to the database as SYS or SYSTEM user and then execute this SQL statement which will add the two missing columns to the table: ALTER TABLE SYSTEM.SCHEMA_VERSION_REGISTRY$ ADD (custom1 NUMBER, custom2 VARCHAR2(30));
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-01061: Exception raised while repository upgrade was attempting to access MAS topology for BAM: {0}.

Cause: Repository upgrade framework was unable to access the MAS topology for BAM. The error message displays the base exception that caused the failure. This error message indicates a severe error condition.

Action: Verify that BAM has been installed and configured for this instance. Verify that the MAS topology service is running. Examine the log file for additional information. Contact Oracle Support Services if BAM has been installed and configured yet this error persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-01062: Exception raised while repository upgrade was running an external command.

Cause: An exception was raised while running an external command (such as sqlplus) in a subprocess. Check the stack trace for detailed information.

Action: Attempt to correct the environment problem if any, then retry the upgrade. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-01063: Exception raised while repository upgrade was performing SQL queries.

Cause: An exception was raised while performing SQL operations to determine schema versions. Check the stack trace for detailed information.

Action: Attempt to correct the environment problem if any, then retry the upgrade. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-01064: The MAS topology for Business Intelligence may be corrupted. Unable to fetch node: {0} of {1}.

Cause: Repository upgrade framework was unable to access the MAS topology for Business Intelligence. The error message indicates which topology node was missing. Either Business Intelligence is not configured for this instance, or the Business Intelligence topology is corrupt. This error message indicates a severe error condition.

Action: Verify that Business Intelligence has been installed and configured for this instance. Verify that the MAS topology service is running. Examine the log file for additional information. Contact Oracle Support Services if BI has been installed and configured yet this error persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-01065: LDAP DBCN entry is corrupted. Unable to fetch node: {0} of {1}.

Cause: Repository upgrade framework was unable to access the LDAP directory to obtain a list of OracleAS 10g Metadata Repositories. The error message indicates which topology node was missing. This error message indicates a severe error condition.

Action: Delete the directory record that was identified as being corrupt. Examine the log file for additional information. After deleting the corrupt record, retry the repository upgrade that failed. Contact Oracle Support Services if this error persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-01066: unable to connect to the Oracle OIM schema {0}.

Cause: Repository upgrade framework was unable to connect to the Oracle OIM database schema. The database might be down, or the password might be incorrect.

Action: Verify that the host, port, service name, and password are correct. Verify that the database server and listener are running. Examine the log file for additional information.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-01067: unable to connect to the Oracle ODI schema {0}.

Cause: Repository upgrade framework was unable to connect to the Oracle ODI database schema. The database might be down, or the password might be incorrect.

Action: Verify that the host, port, service name, and password are correct. Verify that the database server and listener are running. Examine the log file for additional information.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-01068: unable to connect to the Oracle OAAM schema {0}.

Cause: Repository upgrade framework was unable to connect to the Oracle OAAM database schema. The database might be down, or the password might be incorrect.

Action: Verify that the host, port, service name, and password are correct. Verify that the database server and listener are running. Examine the log file for additional information.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-01069: PostgreSQL JDBC driver SHA1 signature is invalid. Expected: {0} Computed: {1}.

Cause: The user has chosen an upgrade with a PostgreSQL database but the JDBC driver that was found does not have the expected SHA1 signature.

Action: Locate the precise version of the PostgreSQL JDBC driver jar file that Oracle has certified, and copy it into the ORACLE_HOME/jlib directory. The name of the jar file must match the expected name, and the SHA1 signature of the file must match the expected value.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-01070: Unable to process PostgreSQL JDBC driver jar file for SHA1.

Cause: The user has chosen an upgrade with a PostgreSQL database but the JDBC driver that was found does not have the expected SHA1 signature.

Action: Locate the precise version of the PostgreSQL JDBC driver jar file that Oracle has certified, and copy it into the ORACLE_HOME/jlib directory. The name of the jar file must match the expected name, and the SHA1 signature of the file must match the expected value.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-01071: Unable to close input stream for SHA1 calculation.

Cause: The user has chosen an upgrade with a PostgreSQL database and while computing the SHA signature of the JDBC driver an internal error was detected while closing the input stream.

Action: This is an internal error. Locate the precise version of the PostgreSQL JDBC driver jar file that Oracle has certified, verify the file is not zero-length, and copy it into the ORACLE_HOME/jlib directory. The name of the jar file must match the expected name, and the SHA1 signature of the file must match the expected value.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-01072: unable to connect to the Oracle BI schema {0}

Cause: Repository upgrade framework was unable to connect to the Oracle BI schema. The database might be down, or the password might be incorrect.

Action: Verify that the host, port, service name, and password are correct. Verify that the database server and listener are running. Examine the log file for additional information.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-01073: unable to connect to the Oracle ECM schema {0}

Cause: Repository upgrade framework was unable to connect to the Oracle ECM schema. The database might be down, or the password might be incorrect.

Action: Verify that the host, port, service name, and password are correct. Verify that the database server and listener are running. Examine the log file for additional information.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-01074: unable to connect to the database {0}

Cause: Repository upgrade framework was unable to connect to the database instance. The database might be down, or the password might be incorrect.

Action: Verify that the host, port, service name, and password are correct. Verify that the database server and listener are running. Examine the log file for additional information.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-01075: An in-place upgrade will be performed on the original copy of database schemas

Cause: While performing an ODI schema upgrade user has unchecked the option box labeled 'Check that Upgrade Occurs Only on Cloned Repositories'

Action: By unchecking this option box the user acknowledges that the ODI upgrade will modify the orginal copy of the ODI database schemas. Verify that a baclup has been taken of the ODI schemas prior to upgrade when using this option.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-02001: Unable to connect to {0} because {1}.

Cause: The identified server could not be contacted.

Action: Review the log file for the server. Verify that the source of the URL is correct.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-02002: Repository schema {0} wrong status {1} or version {2}.

Cause: Something went wrong the last time the metadata repository was upgraded.

Action: Check the log from the repository upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-02003: unable to obtain port number.

Cause: Component was not running or was misconfigured.

Action: Check that the component is running.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-02004: Error {1} while requesting {0}.

Cause: The server was unavailable.

Action: Review the log file for the server. Verify that the source of the URL is correct.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-02005: Verification has run into an unexpected error {1} on object {0}.

Cause: An unexpected error occurred during verification.

Action: See the secondary message for additional details.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-02006: Request to {0} URL {1} received error "{2}".

Cause: The identified server did not respond as expected.

Action: Review the identified server's log to identify the problem.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-02007: Unable to find a schema with password to test on database {0}.

Cause: To verify that the database is available, verification looks in the Credential Store for schema credentials. It was unable to locate a schema with credentials.

Action: None. The database cannot be tested.
Level: 1

Type: ERROR

Impact: Upgrade

99 UPGCMP-00019 to UPGCMP-06005

UPGCMP-00019: Component {0} is not in the SCHEMA_VERSION_REGISTRY for namespace {1}.

Cause: Repository upgrade framework detected that the named component was missing a required entry in SCHEMA_VERSION_REGISTRY. This might be due to an internal error or incorrect configuration before the upgrade was performed. The component might be missing from the repository database.

Action: Verify that the component already has been created in the repository database by the Repository Creation Utility under the same namespace being used for upgrade. Retry the upgrade. If the Repository Creation Utility has created the component schemas and the error persists, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00037: Component {0} is not present in the SCHEMA_VERSION_REGISTRY for namespace {1}.

Cause: The repository upgrade component-specific software module discovered that an optional component was not present in SCHEMA_VERSION_REGISTRY. This is an informational message.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGCMP-00038: Component {0} app_registry entry is: {1} {2}.

Cause: Repository upgrade component-specific software module detected that the component had an entry in the 10g APP_REGISTRY view. This is an informational message.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGCMP-00039: Component {0} schema_registry entry is: {1} {2} in the namespace {3}.

Cause: Repository upgrade component-specific software module logged this data that was retrieved from SCHEMA_VERSION_REGISTRY. This is an informational message.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGCMP-00045: failure reading from app_registry

Cause: Repository upgrade component-specific software module encountered an error while attempting to access the OracleAS 10g APP_REGISTRY view. This is an internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00046: Component {0} is not present in app_registry.

Cause: Repository upgrade component-specific software module detected that a component was missing an entry in the OracleAS 10g APP_REGISTRY view. This error condition will cause the examination phase of upgrade to fail.

Action: Verify that the database being upgraded contains an OracleAS metadata repository. If the problem persists notify Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00047: Component {0} is not present in app_registry.

Cause: Repository upgrade component-specific software module detected that an optional component was missing from the 10g APP_REGISTRY view. This is an informational message.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGCMP-00048: SQL version and status query failed for component {0}.

Cause: The repository upgrade component-specific software module encountered an error while trying to obtain version and status information for the component. This is an internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00049: unable to connect to the source database

Cause: Repository upgrade was unable to connect to the source database instance. The database might be down, or the password might be incorrect.

Action: Verify that the source connect string, user name, and password are correct. Verify that the database server and listener are running. Examine the log file for additional information.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00050: unable to connect to the target database

Cause: Repository upgrade was unable to connect to the target database instance. The database might be down, or the password might be incorrect.

Action: Verify that the target connect string, user name, and password are correct. Verify that the database server and listener are running. Examine the log file for additional information.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00101: unable to retrieve password for {0} schema

Cause: Oracle Portal repository upgrade component-specific software module encountered an error while fetching Oracle Portal password from Oracle Internet Directory.

Action: Verify that the Oracle Internet Directory associated with Oracle Portal is up and running and the Oracle Portal password within the Oracle Internet Directory is accessible. After making sure that Oracle Internet Directory is accessible, retry the upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00102: Oracle Portal {0} upgrade log files available in {1}.

Cause: The location of Oracle Portal repository upgrade logs was generated by the Oracle Portal component-specific software module. This is an informational message.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGCMP-00103: cannot find Perl in the Oracle home

Cause: Perl was missing from the Oracle home.

Action: Verify that the Oracle home where you are running th Assistant contains the Perl executable.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00104: failure during the Oracle Portal {0} run

Cause: An error occurred either during Oracle Portal precheck run or upgrade run.

Action: Contact Oracle Support Services with the log file details.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00105: failure with progress bar during the upgrade phase of Oracle Portal

Cause: An unexpected error was encountered updating the progress bar.

Action: The Oracle Portal component upgrade was not impacted and the error can be ignored.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGCMP-00201: missing 10g Entry in SCHEMA_VERSION_REGISTRY

Cause: Oracle Internet Directory schema details were not found in the SCHEMA_VERSION_REGISTRY table.

Action: Refer to the Upgrade Guide for Oracle Identity Management for steps to perform the OID upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00202: The upgrade is not supported from a schema version of {0}.

Cause: An unsupported base schema version was being upgraded.

Action: Refer to the Upgrade Guide for Oracle Identity Management for supported versions for upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00203: failure retrieving ODSSM schema password

Cause: There is no LDAP attribute entry for the ODSSM schema password.

Action: Create 'orclPasswordAttribute' in the Oracle Internet Directory with ODSSM schema password under entry: 'cn=dsaconfig,cn=configsets,cn=oracle internet directory' for upgrade to work.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00204: failure during upgrade precheck: {0}

Cause: Error occurred during the Oracle Internet Directory upgrade precheck.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00205: The ODS schema upgrade is INVALID.

Cause: Some of the packages in the Oracle Internet Directory schema were INVALID after upgrade.

Action: To see which objects are invalid, log in to the Database as user 'ODS' and execute 'select object_name from user_objects where status='INVALID' '. Restore the backed up database and correct the schema before running the Assistant again.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00206: error during Oracle Internet Directory upgrade: {0}

Cause: An unexpected error occurred during Oracle Internet Directory Upgrade.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00207: Error getting OID Component name and ASInstance name

Cause: Unable to get values from 11g opmn.xml

Action: 1. Check that 11g OPMN is running 2. Check that $ORACLE_INSTANCE/config/OPMN/opmn/opmn.xml exists 3. Contact Oracle Support Services if the above steps do not help you resolve the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00208: Could not read details from OID subregistrysubentry

Cause: An error occurred while reading entries from 10g OID

Action: 1. Make sure 10g OID is up and running 2. Contact Oracle Support Services if the above steps do not help you resolve the problem
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00209: error while contacting Oracle Internet Directory: {0}

Cause: unable to connect to the Oracle Internet Directory server. See the exception details for exactly what happened.

Action: 1. Check that Oracle Internet Directory is running. 2. Check that the Oracle Internet Directory connection details are correct in preceding messages in this log.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00210: exception during LDAP schema upgrade : {0}

Cause: Check the preceding messages in this log for detailed cause.

Action: 1. Check the preceding messages in this log for the specific problem. 2. Ensure that the Oracle Internet Directory server is up. 3. Ensure that the Oracle Internet Directory connection credentials are correct. 4. Contact Oracle Support Services if the above steps do not resolve the problem.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00211: error during Oracle Internet Directory schema upgrade: {0}

Cause: An error in SQL processing was detected during Oracle Internet Directory schema upgrade.

Action: Check the SQL messages in $ORACLE_HOME/upgrade/logs/ua<timestamp>.out for the problem and correct the problem before running the Assistant again. Contact Oracle Support Services if you are unable to correct the problem.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00212: error during Oracle Internet Directory schema validation: {0}

Cause: An error occurred during validation of the ODS schema.

Action: 1. Check if Database is running. 2. Check the preceding messages in this log for any errors. Contact Oracle Support Services if you are unable to correct the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00213: error starting Oracle Internet Directory server with retained ports

Cause: An unexpected error occurred while setting Oracle Internet Directory ports to their 10g values.

Action: Check the preceding messages in this log for detailed cause.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00214: error trying to start the Oracle Internet Directory server: {0}

Cause: An unexpected error occurred when trying to restart the Oracle Internet Directory server after the schema upgrade. See the detailed message at $OI/diagnostics/logs/OID/<oid_comp_name>/oidmon*.log

Action: 1. Check that OPMN is running. 2. Check whether Oracle Internet Directory was already running 3. Contact Oracle Support Services if the above steps do not help resolve the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00215: Error connecting to database: {0}

Cause: An error occurred when trying to contact/connect to Oracle Database

Action: 1. Check that Database is running. 2. Check the preceding messages in this log for any errors. 3. Contact Oracle Support Services if the above steps do not help resolve the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00216: Error reading {0} value from {1} file

Cause: An error occurred when trying to read a value from the specified file.

Action: 1. Check that the specified file exists and is readable. 2. Check the preceding messages in this log for any errors. 3. Contact Oracle Support Services if the above steps do not help resolve the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00217: Error writing {0} value to {1} file

Cause: An error occurred when trying to write a value to the specified file.

Action: 1. Check that the specified file exists and is write-enabled. 2. Check the preceding messages in this log for any errors. 3. Contact Oracle Support Services if the above steps do not help resolve the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00218: Missing value for {0} in the {1} file

Cause: An error occurred when trying to read a value from the specified file.

Action: 1. Add the missing value in the specified file and retry. 2. Check the preceding messages in this log for any errors. 3. Contact Oracle Support Services if the above steps do not help resolve the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00219: Error deleting the {0} file

Cause: An error occurred when trying to delete the specified file.

Action: 1. Manually delete the specified file and your upgrade is complete. 2. Check the preceding messages in this log for any errors. 3. Contact Oracle Support Services if the above steps do not help resolve the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00220: Error updating registration details of OID in WLS: {0}

Cause: An error occurred when trying to run 'opmnctl updatecomponentregistration' for OID.

Action: 1. Check the preceding messages in this log to see if the WLS server details are right. 2. Check if the WLS server is up and running. 3. Check the preceding messages in this log for any errors. 4. Manually run $Oracle_Instance/bin/opmnctl updatecomponentregistration for OID at the end of upgrade. 5. Contact Oracle Support Services if the above steps do not help resolve the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00221: Error finding OID MBean in WLS: {0}

Cause: An error occurred when trying to find OID Mbean 'oracle.as.management.mbeans.register:instance=<instName>,Location=AdminServer,name=<oidCompName>,type=component' in WLS.

Action: 1. Check the preceding messages in this log to see if the WLS server details are right. 2. Check if the WLS server is up and running. 3. Check the preceding messages in this log for any errors. 4. Manually register OID component in WLS after upgrade. Refer to the OPMN documentation for the same. 5. Contact Oracle Support Services if the above steps do not help resolve the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00222: error trying to stop the Oracle Internet Directory server: {0}

Cause: An unexpected error occurred when trying to stop the Oracle Internet Directory server after the schema upgrade. See the detailed message.

Action: 1. Check that OPMN is running. 2. Check whether Oracle Internet Directory was already stopped 3. Contact Oracle Support Services if the above steps do not help resolve the problem.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00223: error trying to start the Oracle Process Manager(OPMN): {0}

Cause: An unexpected error occurred when trying to start the Oracle Process Manager after the schema upgrade. See the detailed message at $OI/diagnostics/logs/OPMN/opmn/opmn.log

Action: 1. Check that OPMN port is not occupied. 2. Check whether OPMN was already running 3. Contact Oracle Support Services if the above steps do not help resolve the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00224: error trying to add configset entry to OID: {0}

Cause: An unexpected error occurred when trying to add configset entry to OID using oidctl. See the detailed message at $OI/diagnostics/logs/OID/<oid_component_name>/oidctl.log

Action: 1. Check that oidctl binary is present under $OH/bin directory. 2. Verify that the connectstring used in oidctl syntax is the same as the one in $OI/config/tnsnames.ora file. 3. Contact Oracle Support Services if the above steps do not help resolve the problem.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00225: Error trying to set the SSL properties in the new 11g configset entry of OID: {0}

Cause: An unexpected error occurred when trying to add ssl properties to OID.

Action: 1. Check that orclsslwalleturl attribute value is a valid path. 2. Contact Oracle Support Services if the above steps do not help resolve the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00301: Unknown technology.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00302: Target Master Repository is invalid.

Cause: Target Master Repositority wasn't found in the given schema.

Action: Define valid Target Master Repository credentials.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00303: Target Work Repository {0} is invalid.

Cause: Target Work Repositority wasn't found in the given schema.

Action: Define valid Target Work Repository credentials.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00304: Target Master Repository is not clone.

Cause: Target and Source Master Repositories are the same.

Action: Make clone of Source Master Repository.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00305: Target Work Repository {0} is not clone.

Cause: Target Work Repository and Source Master Repositories are the same.

Action: Enter correct credentials for Target Work Repository.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00306: Target Work Repository {0} is not clone.

Cause: Target Work Repository has the same schema as Sourcer Work Repository.

Action: Enter correct credentials for Target Work Repository.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00307: More than one Target Work Repository has the same credentials as Target Master Repository.

Cause: Only one Target Work Repository is allowed to have the same credentials as Target Master Repository.

Action: Enter correct credentials for Target Work Repositories.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00308: Target Work Repository {0} must have the same credentials as Target Master Repository.

Cause: Wrong Target Work Repository has the same credentials as Target Master Repository.

Action: Enter correct credentials for Target Work Repository.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00309: Same Target Work Repositories credentials

Cause: Two or more Target Work Repository have the same schema name.

Action: Enter correct credentials for Target Work Repositories.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00310: Target Work Repository {0} has the same credentials as Target Master Repository.

Cause: Source Master Repository doesn't host Work Repository.

Action: Check credentials for Target Work Repository.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00311: Folder with 11g KM is not available

Cause: Folder oracledi/xml-reference/ doesn't exist

Action: Check you ODI Home folder.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00312: Target and Source Master Repositories has the same connection string.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00313: Target Work Repository {0} is hosted in Target Master Repository.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00314: Source Work Repository {0} is hosted in Source Master Repository.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00315: Target Master Repository upgrade is started.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00316: Target Work Repository {0} upgrade is started.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00317: Repository validation.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00318: Getting work repositories.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00319: Getting Original Master Repository connection information.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00320: KM replacing is selected.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00321: Topology upgrade is selected.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00322: Looking for KM {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00323: KM {0} was found.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00324: Topology and Security Metadata upgrade failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00325: Target Master Repository upgrade failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00326: Target Work Repository upgrade failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00327: Invalid credentials for ODI Supervisor.

Cause: A wrong credentials were provided to upgrade Master and Work Repositories.

Action: Enter correct credentials for ODI Supervisor.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00328: Target Work Repository {0} is invalid.

Cause: Target Work Repositority doesn't belong to Master Repository.

Action: Define valid Target Work Repository credentials.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00329: Can not connect to Master Repository.

Cause: A wrong credentials were provided to upgrade Master Repository.

Action: Define valid Master Repository credentials.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00330: Can not connect to Work Repository.

Cause: A wrong credentials were provided to upgrade Work Repository.

Action: Using Topology Navigator, define valid Work Repository credentials.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00331: Master Repository has invalid state.

Cause: Previous upgrade of Master Repository was unsuccessful.

Action: Restory Master Repository from Backup and try to upgrade again.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00332: Work Repository has invalid state.

Cause: Previous upgrade of Work Repository was unsuccessful.

Action: Restory Work Repository from Backup and try to upgrade again.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00333: Unknow error happened.

Cause: Unknow error happened.

Action: Restory Master Repository from Backup and try to upgrade again.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00334: Unknow error happened.

Cause: Unknow error happened.

Action: Restory Work Repository from Backup and try to upgrade again.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00335: ODI schema "{0}" does not contain a valid ODI repository.

Cause: Master Repositority wasn't found in the given schema.

Action: Define valid Master Repository credentials.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00336: ODI schema "{0}" does not contain a valid 11g ODI repository.

Cause: 11g Master Repositority wasn't found in the given schema.

Action: Please use ODI Upgrade Assisant to perform the upgrade operation from current version to 11.1.1.6.0.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00337: ODI Master schema version found is "{0}".

Cause: ODI PSA is meant for upgrade of ODI repository from 11.1.1.3.0 to 11.1.1.6.0 only.

Action: Please use ODI Upgrade Assisant to perform the upgrade operation from current version to 11.1.1.6.0.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00338: User "{0}" has insufficient privileges.

Cause: DBA user doesn't have SYSDBA privilege.

Action: Try to use user with SYSDBA privilege.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00339: Grant execute in dbmsd_lock failed

Cause:

Action:
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00340: Grant operation failed for schema "{0}".

Cause: Cannot grant execute on dbms_lock to the schema .

Action: Check credentials for Target Work Repository.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00401: The BIPublisher {0} run has an error. {1}.

Cause: An error occurred either during BIPublisher precheck run or upgrade run.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00402: unable to get target schema prefix

Cause: 11g schema prefix is not provided.

Action: Enter value for option '-schemaPrefix' while invoking the upgrade utility.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00403: 10g schema for BIPublisher does not have VALID status in SCHEMA_VERSION_REGISTRY

Cause: The BIPublisher 10g schema version registry entry is invalid.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00404: 11g schema for BIPublisher does not have VALID status in SCHEMA_VERSION_REGISTRY.

Cause: The BIPublisher 11g schema version registry entry is invalid.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00405: The table {0} does not exist.

Cause: The upgrade assistant could not find the table.

Action: Check the upgrade assistant has access to the table.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00406: Error: A SQL error occured during the migration.

Cause: Perhaps the tablespace or log file is full.

Action: Notify your DBA. If unable to resolve, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00407: Error: Database connections for 10g and 11g are not the same type.

Cause: The database types must be the same (i.e., migrating from DB2 to Oracle is disallowed).

Action: Ensure both database connections are of same type.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00408: Error: Table {0} does not exist in 10g instance.

Cause: Perhaps the scheduler was not installed under this database account.

Action: Ensure that the appropriate database account is specified.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00409: Error: Table {0} does not exist in 11g instance.

Cause: Perhaps the scheduler was not installed under this database account.

Action: Ensure that the appropriate database account is specified.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00410: Error: Failed to create connection for user {0} using connection string {1}.

Cause: The username, password, or other connection information was incorrect.

Action: Provide the correct connection information.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00501: Directory {0} does not exist.

Cause: The upgrade directory is required for the upgrade task to proceed.

Action: Create the directory shown in the error and retry.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00502: No zip file is found for import in {0}.

Cause: A required zip file was missing from the specified upgrade directory.

Action: Run the export utility on 10.1.2 and copy the zip file to the upgrade directory.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00503: error during the {0} phase of Oracle B2B upgrade

Cause: An error occurred either during Oracle B2B precheck run or upgrade run.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00504: MDS configuration exception is detected during Oracle B2B upgrade: {0}.

Cause: During the Oracle B2B schema upgrade an MDS configuration exception was detected. Refer to the secondary error message for details about the cause of the failure.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00505: MDS exception is detected during Oracle B2B upgrade: {0}.

Cause: During the Oracle B2B schema upgrade an MDS exception was detected. Refer to the secondary error message for details about the cause of the failure.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00506: No files are found for import in {0}.

Cause: A required .zip file was missing from the specified upgrade directory.

Action: Run the export utility on 10.1.2 and copy the zip file to the upgrade directory.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00507: MDS transfer fails due to secondary error {0}.

Cause: An error occurred while transferring data from MDS. Refer to the secondary error message for details about the cause of the failure.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00602: Error while retrieving tablespace for OAAM Upgrade.

Cause: Unable to retrieve tablespace of Schema indexes.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00603: SQL error.

Cause: JDBC error while executing query

Action: Make sure DB is reachable and configured properly
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00604: An unknown error occured.

Cause: Unknown

Action: See the secondary error message in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00701: The Discoverer {0} run has an error. {1}.

Cause: An error occurred either during Discoverer precheck run or upgrade run.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00702: unable to get target schema prefix

Cause: 11g schema prefix is not provided.

Action: Enter value for option '-schemaPrefix' while invoking the upgrade utility.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00703: 10g schema for Discoverer does not have VALID status in SCHEMA_VERSION_REGISTRY

Cause: The Discoverer 10g schema version registry entry is invalid.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00704: 11g schema for Discoverer does not have VALID status in SCHEMA_VERSION_REGISTRY.

Cause: The Discoverer 11g schema version registry entry is invalid.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00705: Discoverer 10g database objects are not available or not in a valid state.

Cause: Discoverer 10g database objects were not available or not in a valid state.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00706: Discoverer 11g database objects are not available or not in a valid state.

Cause: Discoverer 11g database objects were not available or not in a valid state.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00707: Discoverer 10g metadata record with key {0} is corrupt. {1}.

Cause: Specified Discoverer 10g metadata record is corrupt.

Action: Delete the corrupted record and rerun metadata repository upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00801: error during the Oracle BAM {0} run

Cause: An error occurred either during Oracle BAM precheck run or upgrade run.

Action: Contact Oracle Support Services with the log file details.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00802: Oracle BAM precheck failure

Cause: An error occurred during Oracle BAM precheck run.

Action: Contact Oracle Support Services with the log file details.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00803: Oracle BAM upgrade failure

Cause: An error occurred during Oracle BAM upgrade run.

Action: Contact Oracle Support Services with the log file details.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00804: Oracle BAM precheck success

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGCMP-00805: Oracle BAM upgrade success

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGCMP-00806: Oracle BAM is already upgraded

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGCMP-00807: Oracle BAM is already upgraded.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGCMP-00808: Oracle BAM OC4J is running. Stop the Oracle BAM OC4J application and retry the upgrade.

Cause: Oracle BAM OC4J was running.

Action: Oracle BAM OC4J instance is running. Stop the Oracle BAM OC4J and retry the upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00809: The Oracle BAM schema is not a valid 10.1.3 schema.

Cause: The Oracle BAM database schema was not a valid 10.1.3 schema.

Action: Ensure that the Oracle BAM schema is a version 10.1.3 schema.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00901: Failed to update the rule Dictionary at {0}

Cause: Error occured while trying to update dictionary

Action: Moved the composite to Partially_Upgraded_Composites. Upgrade the composite manually.
Level: 1

Type: WARNING

Impact: Upgrade

UPGCMP-00902: Invalid arguments are passed.

Cause: Invalid arguments are passed

Action: Moved the composite to Partially_Upgraded_Composites. Upgrade the composite manually.
Level: 1

Type: WARNING

Impact: Upgrade

UPGCMP-00903: Failed to create a template project at {0}

Cause: Error occured while creating the template BPEL composite

Action: Upgrade the Approval process manually.
Level: 1

Type: WARNING

Impact: Upgrade

UPGCMP-00904: Invalid target type {0} encountered.

Cause: Invalid target type is encountered while generation of rules in BPEL composite.

Action: Moved the composite to Partially_Upgraded_Composites. Upgrade the composite manually.
Level: 1

Type: WARNING

Impact: Upgrade

UPGCMP-00905: Rule with rule key {0} is not default rule.

Cause: The Approval process contains only a single rule which is not default rule.

Action: Moved the composite to Partially_Upgraded_Composites. Upgrade the composite manually.
Level: 1

Type: WARNING

Impact: Upgrade

UPGCMP-00906: Failed to retrieve user login for the user with key {0}

Cause: Error in retrieving user details from the database.

Action: Moved the composite to Partially_Upgraded_Composites. Upgrade the composite manually.
Level: 1

Type: WARNING

Impact: Upgrade

UPGCMP-00907: Failed to retrieve group name for the group with key {0}

Cause: Error in retrieving group details from the database.

Action: Moved the composite to Partially_Upgraded_Composites. Upgrade the composite manually.
Level: 1

Type: WARNING

Impact: Upgrade

UPGCMP-00908: Approval Task is associated with a custom adapter

Cause: {0} is associated with a task assignment adapter

Action: {0} : Implement the task assignment logic in corresponding BPEL Composite.
Level: 1

Type: WARNING

Impact: Upgrade

UPGCMP-00909: Callback URL cannot be set

Cause: Cannot set the callback url in file {0}

Action: Set the Callback URL manually in the file {0}
Level: 1

Type: WARNING

Impact: Upgrade

UPGCMP-00910: Error in parsing the xml file

Cause: Cannot parse the xml file : {0}. Cause : {1}

Action: Upgrade the process manually
Level: 1

Type: WARNING

Impact: Upgrade

UPGCMP-00911: Error in writing parsed XML Document to File

Cause: Error in writing parsed XML Document to File : {0}. Cause : {1}

Action: Upgrade the process manually
Level: 1

Type: WARNING

Impact: Upgrade

UPGCMP-00912: Rule construction is based on Task information.

Cause: Task Information unavailable for rule creation

Action: Update the payload with task information and upgrade the process manually.
Level: 1

Type: WARNING

Impact: Upgrade

UPGCMP-00921: Error while connecting to the target database.

Cause: DB is not reachable

Action: Make sure DB is up and running and reachable
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00922: OIM ADT constarint is violated

Cause: OIM ADT constarint is violated

Action: Verify OIm schema
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00923: Unable to locate the file. Check logs for more details.

Cause: Unable to find file

Action: Make sure path is correct
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00924: SQL error [{0}]

Cause: JDBC error while executing query

Action: Make sure DB is reachable and configured properly
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00925: An unknown error occured [{0}]

Cause: Unknown

Action: See the secondary error message in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01001: unexpected upgrade exception

Cause: An unexpected error occurred while a component was being examined or upgraded.

Action: Check the log file for more details and contact Oracle Support Services, if needed.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-01101: exception while backing up file {0}

Cause: Errors occurred backing up the specified configuration file during mod_plsql upgrade.

Action: See the secondary error message for more details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01102: exception while upgrading mod_plsql

Cause: Errors occurred while upgrading one of the mod_plsql configuration files.

Action: See the secondary error message for more details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01103: exception while replacing source Oracle home references in: {0}

Cause: Errors occurred while replacing the Oracle home references in the specified configuration file.

Action: See the secondary error message for more details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01104: exception while copying file {0} to {1}

Cause: Errors occurred copying the specified configuration file.

Action: See the secondary error message for more details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01105: File {0} does not exist in the target instance.

Cause: The specified configuration file for the destination instance was not found.

Action: See the secondary error message for more details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01106: failure to remove obsolete configuration properties from {0}

Cause: Errors occurred removing obsolete properties from the specified configuration file.

Action: See the secondary error message for more details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01201: exception during the upgrade of Oracle Portal

Cause: Oracle Portal upgrade failed while upgrading one of the Oracle Portal configuration files.

Action: See the secondary error message for more details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01202: File {0} does not exist in the destination Oracle instance.

Cause: The specified Oracle Portal configuration file was not found in the destination Oracle instance.

Action: See the secondary error message in the OFM Upgrade Assistant log file for the cause of the failure. Ensure that the configuration file is present in the destination Oracle instance.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01203: Oracle Portal upgrade completed with errors.

Cause: Errors were encountered during the Oracle Portal component upgrade.

Action: Check the OFM Upgrade Assistant log file for details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01204: The default location {0} of the log directory has changed in file {1} of the source Oracle home.

Cause: The default location of log directory has changed in the given file in the source Oracle home.

Action: Check the value of log directory in the destination instance for the given file. Change it to point to the correct location if required.
Level: 1

Type: WARNING

Impact: Upgrade

UPGCMP-01231: unable to copy file: {0}

Cause: The Oracle JPDK upgrade failed to copy the specified configuration file.

Action: See the secondary error message in the OFM Upgrade Assistant log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01232: unable to create the directory: {0}

Cause: The Oracle JPDK upgrade failed to create the specified directory.

Action: See the secondary error message in the OFM Upgrade Assistant log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01233: unable to upgrade the <preferenceStore> tag from providers.xml file: {0}

Cause: The Oracle JPDK upgrade failed to migrate some of the provider configurations from the specified configuration file.

Action: See the secondary error message in the OFM Upgrade Assistant log file for the cause of the failure. Rerun the middle-tier upgrade after fixing the cause or migrate the configuration manually from the source Oracle home to the destination instance home.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01234: unable to upgrade Provider Group changes from source to destination iasProviders.xml file: {0}

Cause: The Oracle JPDK upgrade failed to migrate the Provide Group changes from the specified configuration file.

Action: See the secondary error message in the OFM Upgrade Assistant log file for the cause of the failure. Rerun the middle-tier upgrade after fixing the cause or migrate the configuration manually from the source Oracle home to the destination instance home.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01235: unable to upgrade JNDI entries from source to destination orion-web.xml file: {0}

Cause: The Oracle JPDK upgrade failed to migrate the JNDI entries from the specified configuration file.

Action: See the secondary error message in the OFM Upgrade Assistant log file for the cause of the failure. Rerun the middle-tier upgrade after fixing the cause or migrate the configuration manually from the source Oracle home to the destination instance home.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01236: unable to upgrade the Provider UI Security Settings Registry file: {0}

Cause: The Oracle JPDK upgrade failed to migrate the specified Provider UI Security registry file.

Action: See the secondary error message in the OFM Upgrade Assistant log file for the cause of the failure. Rerun the middle-tier upgrade after fixing the cause or migrate the configuration manually from the source Oracle home to the destination instance home.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01237: Arguments passed for Oracle JPDK upgrade are illegal.

Cause: The arguments passed to the Oracle JPDK upgrade were incorrect.

Action: See the secondary error message in the OFM Upgrade Assistant log file for the cause of the failure and rerun the middle-tier upgrade after fixing the cause of the error.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01238: No Namespace URI is present for the file {0}.

Cause: The Namespace URI is missing in the specified configuration file.

Action: See the secondary error message in the OFM Upgrade Assistant log file for the cause of the failure and rerun the middle-tier upgrade after fixing the cause of the error.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01239: unable to create cache.xml at {0}

Cause: The Oracle JPDK upgrade failed to create the cache.xml file at the specified location in the destination instance home.

Action: See the secondary error message in the OFM Upgrade Assistant log file for the cause of the failure and rerun the middle-tier upgrade after fixing the cause of the error.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01240: failure creating invalidation entries for cache.xml

Cause: The Oracle JPDK upgrade failed to create the invalidation entries in the specified configuration file.

Action: See the secondary error message in the OFM Upgrade Assistant log file for the cause of the failure and rerun the middle-tier upgrade after fixing the cause of the error.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01241: failure while trying to obfuscate an authorization attribute in {0}

Cause: The Oracle JPDK upgrade failed to obfuscate the authorization attributes in the specified configuration file.

Action: See the secondary error message in the OFM Upgrade Assistant log file for the cause of the failure and rerun the middle-tier upgrade after fixing the cause of the error.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01242: exception during Oracle JPDK upgrade

Cause: The Oracle JPDK upgrade failed while upgrading one of the configuration files.

Action: See the secondary error message in the OFM Upgrade Assistant log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01271: OmniPortlet is unable to upgrade proxy settings.

Cause: The OmniPortlet upgrade failed to upgrade proxy settings.

Action: Check the write permissions of provider.xml in the destination instance. Check the OFM Upgrade Assistant log file for other possible causes.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01272: OmniPortlet is unable to upgrade customizations.

Cause: The OmniPortlet upgrade failed to copy the portlet customizations from the source Oracle home to the destination instance.

Action: Check the write permissions of the customization directory in the destination instance. Check the OFM Upgrade Assistant log file for other possible causes.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01273: OmniPortlet is unable to upgrade Locale Personalization Level.

Cause: The OmniPortlet upgrade failed to copy the Locale Personalization Level from the source Oracle home to the destination instance.

Action: Check the write permissions of provider.xml in the destination instance. Check the OFM Upgrade Assistant log file for other possible causes.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01275: OmniPortlet is unable to upgrade the encodeHtmlField setting.

Cause: The OmniPortlet upgrade failed to copy the encodeHtmlField setting from the source Oracle home to the destination instance.

Action: Check the write permissions of provider.xml in the destination instance. Check the OFM Upgrade Assistant log file for other possible causes.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01276: OmniPortlet is unable to upgrade the exportConnectionInfo setting.

Cause: The OmniPortlet upgrade failed to copy the exportConnectionInfo setting from the source Oracle home to the destination instance.

Action: Check the write permissions of provider.xml in the destination instance. Check the OFM Upgrade Assistant log file for other possible causes.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01277: OmniPortlet is unable to upgrade Security Repository settings.

Cause: The OmniPortlet upgrade failed to copy the Security Repository settings from the source Oracle home to the destination instance.

Action: Check the write permissions of provider.xml in the destination instance. Check the OFM Upgrade Assistant log file for other possible causes.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01278: OmniPortlet is unable to upgrade Preference Store settings.

Cause: The OmniPortlet upgrade failed to copy the Preference Store settings from the source Oracle home to the destination instance.

Action: Check the write permissions of provider.xml in the destination instance. Check the OFM Upgrade Assistant log file for other possible causes.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01279: Web Clipping is unable to upgrade Trusted Certificate Location.

Cause: The Web Clipping upgrade failed to copy the Trusted Certificate Location from the source Oracle home to the destination instance.

Action: Check the write permissions of provider.xml in the destination instance. Check the OFM Upgrade Assistant log file for other possible causes.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01280: Web Clipping is unable to upgrade Proxy settings.

Cause: The Web Clipping upgrade failed to copy the Proxy settings from the source Oracle home to the destination instance.

Action: Check the write permissions of provider.xml in the destination instance. Check the OFM Upgrade Assistant log file for other possible causes.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01281: Web Clipping is unable to upgrade translated URL-service providers.

Cause: The Web Clipping upgrade failed to copy the URL-service provider definition files from the source Oracle home to the destination instance.

Action: Check the OFM Upgrade Assistant log file for details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01282: Web Clipping is unable to upgrade Oracle Web Cache settings.

Cause: The Web Clipping upgrade failed to copy the Oracle Web Cache settings from the source Oracle home to the destination instance.

Action: Check the write permissions of $ORACLE_HOME/portal/conf/cache.xml in the destination instance. Check the OFM Upgrade Assistant log file for other possible causes.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01284: Web Clipping is unable to upgrade Security Repository settings.

Cause: The Web Clipping upgrade failed to copy the Security Repository settings from the source Oracle home to the destination instance.

Action: Check the write permissions of provider.xml in the destination instance. Check the OFM Upgrade Assistant log file for other possible causes.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01285: Web Clipping is unable to upgrade the database respository schema.

Cause: The Web Clipping upgrade failed to upgrade the database respository schema to the new version.

Action: Ensure that the given database repository URL is correct. Check the OFM Upgrade Assistant log file for other possible causes.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01286: OmniPortlet is unable to upgrade the useThinGraph setting.

Cause: The OmniPortlet upgrade failed to copy the useThinGraph setting from the source Oracle home to the destination instance.

Action: Check the write permissions of provider.xml in the destination instance. Check the OFM Upgrade Assistant log file for other possible causes.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01287: exception during Oracle Portal tools upgrade

Cause: Errors were encountered while running the Oracle Portal tools upgrade.

Action: Check the OFM Upgrade Assistant log file for details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01288: failure to import init-param {0} from source {1}

Cause: Errors occurred importing initialization parameters from the specified configuration file.

Action: See the secondary error message for more details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01301: error parsing file {0}

Cause: An error occurred parsing the specified file.

Action: See the secondary error message for more details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01302: error updating file {0}

Cause: An error occurred updating the specified file.

Action: See the secondary error message for more details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01501: invalid Oracle Internet Directory version for upgrade

Cause: Oracle Internet Directory is not at version 11.1 or later.

Action: Upgrade Oracle Internet Directory before upgrading Oracle Directory Integration Platform.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01502: Oracle Directory Integration Platform is already upgraded.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGCMP-01503: unable to connect to the Oracle Internet Directory server

Cause: DIP upgrade needs to communicate with the Oracle Internet Directory server. See detailed preceding message in log for why that was not possible.

Action: Ensure that the Oracle Internet Directory server is running.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01504: A Oracle Directory Integration Platform upgrade parameter is missing.

Cause: A required parameter was not available for Oracle Directory Integration Platform upgrade. This is an internal failure of the OFM Upgrade Assistant.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-01505: Oracle Directory Integration Platform upgrade failed in the examine phase.

Cause: The upgrade of Oracle Directory Integration Platform failed while checking for a valid starting configuration.

Action: See the secondary messages for more details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01506: unexpected error

Cause: An unexpected error occurred while upgrading Oracle Directory Integration Platform.

Action: See the secondary messages for more details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01507: unexpected error

Cause: An unexpected error occurred.

Action: See secondary message for more details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01508: error during Oracle Directory Integration Platform schema upgrade

Cause: The schema files for the Oracle Directory Integration Platform component might be invalid or corrupt.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-01509: error during subscriber upgrade

Cause: Upgrading subscriber schema with invalid file or invalid file content.

Action: The subscriber schema files are not valid. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-01510: error during LDAP operation

Cause: An error occurred while performing an LDAP operation on the Oracle Internet Directory server. See secondary message for more details.

Action: Check that Oracle Internet Directory server is fully operational.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01511: error reading Oracle Directory Integration Platform profile information from file system

Cause: A template profile could not be read from the OH/ldap/odi/conf directory.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-01512: error creating profile

Cause: There was an unexpected error while creating an Oracle Directory Integration Platform profile.

Action: See secondary message for more details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01513: invalid parameter for profile creation

Cause: An incorrect parameter was used for template profile creation.

Action: See secondary message for more details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01514: error connecting to database

Cause: Oracle Directory Integration Platform upgrade was unable to connect to the database.

Action: Ensure that the database connect string, user name, and password are correct, and the database and listener are running.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01515: error reading Oracle Directory Integration Platform configuration information from the database

Cause: Incorrect SQL was detected while reading Oracle Directory Integration Platform information. This is a coding error within Upgrade.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-01516: error during rootcontext upgrade

Cause: The Oracle Directory Integration Platform schema file had invalid file content.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-01517: error importing SSL wallet

Cause: Oracle Directory Integration Platform upgrade was unable to import the SSL wallet from the source Oracle home to the Oracle Directory Integration Platform application node.

Action: See secondary message for more details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01518: failure to connect to the Oracle Internet Directory server

Cause: The upgrade was unable to connect to an Oracle Internet Directory server, as required.

Action: Ensure that the Oracle Internet Directory server is up and running.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01519: error creating CSF key

Cause: KEY creation for Oracle Directory Integration Platform encountered some error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-01520: error creating data source.

Cause: Failure in data source creation for Oracle Directory Integration Platform.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-01702: Unexpected exception occurred during Oracle Web Cache upgrade.

Cause: An unexpected exception occurred.

Action: Check the log file for the cause of this problem.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01703: The source Oracle Web Cache version {0} is not supported for upgrade.

Cause: The source Oracle Web Cache version is not supported for upgrade.

Action: Upgrade the source Oracle Web Cache to a supported version first.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01704: Upgrade exception occurred during Oracle Web Cache upgrade on {0}.

Cause: An exception occurred when upgrading Oracle Web Cache configuration files.

Action: Check the log file for more details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01706: The destination Oracle Web Cache version {0} is not supported by this Upgrade Assistant.

Cause: The destination Oracle Web Cache version is not supported for upgrade.

Action: Run the Upgrade Assistant for the destination version.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01721: The local CACHE element cannot be found in the source configuration file.

Cause: The configuration file of the source Oracle Web Cache does not contain the CACHE element for the source Web Cache component.

Action: Check the configuration file of the source Oracle Web Cache.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01722: The local CACHE element cannot be found in the destination configuration file.

Cause: The pre-upgrade configuration file of the destination Oracle Web Cache does not contain a valid CACHE element for the destination Oracle Web Cache.

Action: Check the destination Oracle Web Cache configuration file.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01723: Cannot create URL for {0}.

Cause: Exception occurred when creating configuration file URL object. The file name string is malformed and cannot be parsed.

Action: Check configuration files, and contact Oracle Support Services if needed.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01724: The source configuration file webcache.xml does not exist or is invalid.

Cause: The source configuration file webcache.xml does not exist or is invalid.

Action: Ensure that the source configuration file is valid and Oracle Web Cache 10g can start before running Upgrade Assistant.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01730: Backing up configuration file failed.

Cause: Exception occurred when backing up destination configuration file.

Action: Check destination environment for the cause of this problem.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01731: Cannot read port properties from OPMN or OHS property file.

Cause: The OPMN or OHS port properties file doesn't exist or is invalid.

Action: Check the log file for more details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01732: Cannot obtain a free port number for the listening port.

Cause: Cannot obtain a free TCP port number for port number conversion.

Action: Manually modify the port number in Oracle WebCache configuration file after upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01733: Testing TCP port {0} failed: {1}

Cause: Exception occurred when testing the port number.

Action: Check the log file for more details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01735: The destination administration port number {0} conflicts with one source listening port. Importing destination administration port failed.

Cause: The destination administration port number conflicts with one source non-admin listening port.

Action: Manually change the administration port number after upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01736: The specified CRL path is not a directory. Migrating CRL files in {0} stopped.

Cause: The CRL path specified in CRLPATH is not a directory.

Action: Check the CRL configuration in source configuration file.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01801: Folder {0} doesn't exist.

Cause: Standalone agent component is not installed

Action: Install standalone agent component.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-01901: failure creating Oracle Reports specific upgrade items

Cause: The Oracle Reports upgrade failed to create Oracle Reports specific upgrade items.

Action: Check the log file for more details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01903: unable to create Oracle Reports server component {0}

Cause: The creation of the specified Oracle Reports server component failed.

Action: Check the log file for more details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01904: unable to create Oracle Reports bridge component {0}

Cause: The creation of the Oracle Reports bridge component failed.

Action: Check the log file for more details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01905: failure during upgrade of file {0}

Cause: The Oracle Reports upgrade failed to upgrade the specified configuration file.

Action: Check the log file for more details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01906: unable to upgrade dependent components file {0}

Cause: The Oracle Reports upgrade failed to upgrade a dependent component file.

Action: Check the log file for more details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01907: unable to upgrade Oracle Reports element

Cause: The Oracle Reports upgrade failed to upgrade an Oracle Reports element.

Action: Check the log file for more details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01908: exception getting FRCOMMON node; FRCOMMON node managed files will not be upgraded

Cause: An exception has occurred getting the FRCOMMON node.

Action: Check the log file for more details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01909: exception parsing file {0}

Cause: An exception has occurred parsing a configuration file.

Action: Check the log file for more details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01910: exception upgrading registry entries

Cause: The Oracle Reports upgrade failed to upgrade registry entries.

Action: Check the log file for more details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02001: unable to complete examination phase for Oracle Single Sign-On midtier upgrade for the given source Oracle home

Cause: The source Oracle home did not have a supported product version. Supported source product version numbers start with either 10.1.2 or 10.1.4

Action: Verify that the source Oracle home slated for upgrade has a supported version number.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02002: unable to complete the examination phase for Oracle Single Sign-On midtier upgrade to Oracle Access Manager for the given destination Oracle home

Cause: The destination Oracle home was not at a supported version. Supported product version numbers start with 11.1.

Action: Select a destination Oracle home that is of a supported version for upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02003: The source Oracle home policy.properties configuration file does not exist.

Cause: Either the source Oracle home is corrupted or a valid path was not provided.

Action: Restore a valid source Oracle home from backup or provide a valid path.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02004: The source Oracle home policy.properties configuration file is not readable.

Cause: The source Oracle home is corrupted.

Action: Restore a valid source Oracle home from backup.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02005: unable to get the Oracle Access Manager logger

Cause: The Oracle Single Sign-On upgrade to Oracle Access Manager could not find an internal resource.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-02006: unable to complete Oracle Single Sign-On upgrade examination phase

Cause: Received an unexpected error while attempting to access the policy.properties configuration file in the source Oracle home.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-02007: Could not connect to the Admin Domain MBean Server

Cause: The connection settings are incorrect or Admin Server is down

Action: Ensure that the Admin Domain MBean server is up and that the connection information is correct
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02009: Source Oracle Single Sign-On Schema is Invalid

Cause: The MBean look-up failed.

Action: Ensure that the Admin Domain MBean server is up and OAM Upgrade Mbean is registered.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02010: Error in osso.conf obfuscation

Cause: osso.conf is not generated properly.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02101: source file {0} is not found

Cause: The specified Discoverer configuration file was not found.

Action: Ensure that the source Oracle home is correctly configured.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02102: destination file {0} is not found

Cause: The specified Discoverer configuration file was not found.

Action: Ensure that the destination Oracle instance is correctly configured.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02103: Discoverer upgrade does not support upgrade from version {0}.

Cause: Discoverer upgrade does not support upgrade from the specified version.

Action: Ensure that the version of the source Discoverer installation is certified to work with the OFM Upgrade Assistant.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02104: Discoverer upgrade does not support upgrade to version {0}.

Cause: Discoverer upgrade does not support upgrade to the specified version.

Action: Ensure that the version of the destination Discoverer installation is certified to work with the OFM Upgrade Assistant.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02105: Discoverer configuration file {0} does not exist.

Cause: The specified configuration file did not exist.

Action: Ensure that the destination Discoverer instance is correctly configured.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02107: Discoverer configuration file {0} appears to be corrupted.

Cause: Specified configuration file was corrupted.

Action: Ensure that the destination Discoverer instance is correctly configured.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02108: Source Oracle home specified is invalid.

Cause: Specified Oracle home was invalid.

Action: Ensure that the source Oracle home is specified correctly.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02109: Destination Discoverer installation is remote.

Cause: Specified destination Discoverer installation (Oracle home) was on a remote host.

Action: Ensure that both source and destination Discoverer installations are on the same host.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02201: Oracle Forms Services upgrade does not support upgrade from version {0}.

Cause: Oracle Forms Services upgrade does not support upgrade from the specified version.

Action: Ensure that the version of the source Oracle Forms Services installation is certified to work with the OFM Upgrade Assistant.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02202: Oracle Forms Services upgrade does not support upgrade to version {0}.

Cause: Oracle Forms Services upgrade does not support upgrade to the specified version.

Action: Ensure that the version of the destination Oracle Forms Services installation is certified to work with the OFM Upgrade Assistant.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02203: invalid section name in the configuration file {0}

Cause: An invalid section name was found in the configuration file.

Action: Correct the application section syntax in the specified configuration file and run the upgrade again.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02205: invalid or missing Oracle Forms Services configuration file {0}

Cause: The specified Oracle Forms Services configuration file was either invalid or missing.

Action: Fix the parent configuration file and run the upgrade again.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02206: Oracle Forms Services is not configured in the source Oracle home {0}.

Cause: Oracle Forms Services was not configured in the source Oracle home so no upgrade of Oracle Forms Services occurred.

Action: No upgrade required for the Oracle Forms Services component.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02208: The source File {0}, does not contain any additional user configuration, it will not be upgraded.

Cause: The specified Oracle Forms Services source file did not contain any additional user configuration. No Oracle Forms Services upgrade is needed.

Action: No Action required.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02210: error reading file {0}

Cause: The specified file is either missing or there was a permission error reading the file.

Action: Ensure that the file exists and the file permissions are correct. Run the upgrade again.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02211: error writing the User entries to file {0}

Cause: An error occurred writing the User entries to the specified file.

Action: Rerun upgrade again.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02212: Source file {0} is already upgraded, it will not be upgraded again.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGCMP-02213: Configuration file error while parsing {0}.

Cause: An error occurred while parsing the specified configuration file.

Action: Fix the syntax errors in the configuration file and run the upgrade again.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02214: Permissions problem writing the file, {0}.

Cause: A permissions error occurred while writing the specified configuration file.

Action: Fix the file permissions and run the upgrade again.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02215: error reading the Oracle Forms Services configuration file {0} from the source Oracle home

Cause: An unexpected error occurred while reading Oracle Forms Services configuration file {0} from the source Oracle home.

Action: See secondary message for details to resolve the error.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02218: failure to upgrade Oracle Forms Services configuration file {0}

Cause: An unexpected error occurred during upgrade of the specified Oracle Forms Services configuration file.

Action: See secondary message for details to resolve the error.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02301: unable to parse httpd.conf

Cause: A possible syntax error was encountered in the httpd.conf file.

Action: Inspect httpd.conf for possible syntax errors.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02310: unable to parse the default DMS configuration {0}

Cause: A possible syntax error was encountered in the default DMS configuration file.

Action: Inspect the default DMS configuration file for possible syntax errors.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02351: OHS upgrade failure while upgrading {0}

Cause: An unexpected exception occurred while upgrading the specified OHS configuration file.

Action: Check the OFM Upgrade Assistant log file for more details regarding the cause of this problem.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02352: unable to parse {0}

Cause: A possible syntax error was encountered in the specified configuration file.

Action: Inspect the specified configuration file for possible syntax errors.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02353: unable to retrieve the reference httpd.conf file from 11g instance.

Cause: The download of the httpd.conf file from 11g instance failed.

Action: Ensure that httpd.conf exists in the 11g OHS instance.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02354: unable to upload the upgraded OHS configuration files to the destination 11g instance

Cause: The upload of upgraded OHS configuration files to destination 11g instance failed.

Action: Make sure instance is in place.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02355: The wallet already exists; SSL wallet {0} is not imported.

Cause: The SSL wallet already exists, most likely from a previous upgrade run.

Action: This is not an error. No action is required.
Level: 1

Type: WARNING

Impact: Upgrade

UPGCMP-02356: unable to import the SSL wallet {0}

Cause: An internal error has occurred.

Action: Import the SSL wallet manually after upgrade or contact Oracle Support Services for help.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-02357: unable to import the SSL wallet {0}

Cause: An error occurred importing the specified SSL wallet.

Action: Ensure that the wallet is a valid 10g wallet, and run the upgrade again.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02358: unable to configure the SSL end point for {0}

Cause: An internal error has occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-02359: failure while upgrading an SSLWallet directive.

Cause: An internal error has occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-02360: unable to write out the upgraded config file {0}.

Cause: An error was encountered while attempting to write to a file.

Action: Ensure that the file exists and is writable.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02361: file I/O error while parsing {0}

Cause: The file was either missing or not readable.

Action: Ensure that the file exists and is readable.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02401: Could not connect to the Admin Edit MBean Server

Cause: The connection settings are incorrect or server is down

Action: Ensure that the Admin Edit MBean server is up and that the connection information is correct
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02402: Could not connect to the Admin Domain MBean Server

Cause: The connection settings are incorrect or server is down

Action: Ensure that the Admin Domain MBean server is up and that the connection information is correct
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02403: The {0} parameter is missing

Cause: A parameter required by the OIF Upgrade Plugin is missing

Action: Ensure that the required parameter is set
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02404: Some required parameters are missing

Cause: One or several parameters required by the OIF Upgrade Plugin are missing

Action: Ensure that all the required parameters are set
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02405: Missing file or directory from OIF 10g install: {0}

Cause: A directory or file from the OIF 10g deployment is missing or not readable

Action: Ensure that the directory or file exists and is readable
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02406: Missing file or directory from OIF 11g install: {0}

Cause: A directory or file from the OIF 11g deployment is missing or not writable

Action: Ensure that the directory or file exists and is writable
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02407: An error occurred during the execution of the {0} OIF Upgrade Item

Cause: An Upgrade Item from the OIF Upgrade plugin failed

Action: Check the logs and fix the error that caused the failure
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02408: Unexpected error occurred during the OIF Upgrade Plugin execution

Cause: An error occurred during OIF Upgrade plugin execution

Action: Check the logs for more information
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02501: OVD upgrade failed.

Cause: An error occurred during OVD Upgrade process.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02502: OVD Registration Error.

Cause: An error occurred while registering OVD.

Action: Ensure that the Weblogic Server is running.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02503: Error deleting the $OI/OVD/tmp.dat file.

Cause: Could not delete the $OI/OVD/tmp.dat file

Action: Manually delete the $OI/OVD/tmp.dat file.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02504: OVD MBean not found.

Cause: Was not able to find the OVD Mbean.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02505: Error migrating 10g server.os_xml to 11g.

Cause: Unable to migrate server.os_xml configuration file.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02506: Error migrating 10g listeners.os_xml to 11g.

Cause: Unable to migrate listeners.os_xml configuration file.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02507: Error migrating 10g adapters.os_xml to 11g.

Cause: Unable to migrate adapters.os_xml configuration file.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02508: OVD Upgrade Exception.

Cause: An I/O error occurred while upgrading listeners.os_xml.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02509: XML Configuration error

Cause: An error occurred while upgrading configuration files.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02601: Unable to load OAAM property file {0} from the WebApp at {1}

Cause: An error occurred while loading OAAM upgrade related properties.

Action: Check make sure 10G WebApp is valid and its path is correct.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02602: Unable to get connection to OAAM database

Cause: An error occurred while getting connection to OAAM database.

Action: Check the log file and then verify the database properties.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02604: Error occurred while generating sequence value

Cause: An error occurred while generating sequence.

Action: Check the OAAM database and make sure all the sequences exist.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02605: OAAM CSF Credential already exists for the mapName [{0}] and keyName [{1}]

Cause: OAAM CSF Keys already exist. So not migrating the secret keys from 10G Keystore.

Action: Please delete the CSF Credential using Enterprise Manager and re-run the Middle Tier upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02606: Could not migrate secret key with alias [{0}] from keystore [{1}] to CSF

Cause: An error occurred while trying to migrate secret key from keystore to CSF.

Action: Check the upgrade logs, fix the issue and re-run Middle Tier upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02607: Could not find the CSF MBean with the name [{0}]

Cause: An error occurred while trying to lookup CSF MBean.

Action: Make sure OAAM domain is properly configured and CSF MBeans are properly deployed. Fix those issues and re-run Middle Tier upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02608: Could not open keystore [{0}]

Cause: Could not open keystore.

Action: Make sure the keystore password is valid. Fix those issues and re-run Middle Tier upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02609: Could not find key alias [{0}] in keystore [{1}]

Cause: Could not find key alias in keystore.

Action: Make sure OAAM 10G keystore is properly configured. Fix those issues and re-run Middle Tier upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02610: Could not find retrieve key with alias [{0}] from keystore [{1}]

Cause: Could not retrieve key from keystore.

Action: Make sure the keyalias password is valid. Fix those issues and re-run Middle Tier upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02611: OAAM table VCRYPT_DB_PATCHES does not exist for the specified OAAM schema user name.

Cause: The OAAM table VCRYPT_DB_PATCHES could not be found using the entered credentials.

Action: Make sure you have entered credentials for a valid OAAM database.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02701: WLS/LDAP reports problems

Cause: Error occurred while moving users and groups from the RPD to the identity store.

Action: Users and groups may not be migrated.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02703: Could not decrypt password for {0}

Cause: Error occurred while decrypting a password.

Action: The password will not be upgraded and will need to be entered in EM.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02704: Application role {0} does not exist

Cause: Error occurred while importing RPD groups.

Action: Enterprise group membership and application roles will need to be confirmed in EM.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02705: Repository file not found in : {0}

Cause: Error occurred while copying RPD.

Action: The RPD file must be moved to the expected location.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02706: Unable to create the directory {0}

Cause: Error occurred creating a directory.

Action: Investigate the permissions on the file system.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02707: Expected a single subdirectory under {0}

Cause: Error occurred calculating a file path.

Action: Confirm a single instance is installed.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02708: Could not configure logging (Error creating {0})

Cause: OBIPS could not be configured to log upgrade messages.

Action: The WLS configuration should be examined.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02709: Cannot upgrade an RPD which is in the TEMP directory ({0})

Cause: The source RPD was in the temporary directory.

Action: Move the source RPD to another location.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02710: Error setting application role {0} as child of {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02711: Error mapping application role {0} to enterprise group {1}

Cause: Error occurred while importing RPD groups.

Action: The application role will have to be manually assigned to the enterprise group in EM.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02712: Expected {0} Oracle instance, found {1}

Cause: Upgrade Assistant can only import to an 11g installation with a single Oracle instance.

Action: Check that a single instance is installed.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02713: Errors were reported during the catalog upgrade. Please refer to the log file for details.

Cause: Error occurred upgrading the catalog.

Action: Please refer to the log file for details of the errors
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02714: Error creating the app role {0}

Cause: See secondary error message for root cause.

Action: Check the permissions, or copy the item locally.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02715: Error accessing the directory {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02716: Could not rename directory {0} to {1}

Cause: Could not rename the directory.

Action: Check the file permissions.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02717: Cannot copy {0} to a subdirectory of itself ({1})

Cause: Cannot copy a directory to a subdirectory of itself.

Action: Select a source directory which is not in the 11g instance.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02718: The catalog upgrade did NOT complete successfully. Please refer to earlier in this upgrade log file or the OBIPS log files found under {0} for more information.

Cause: OBIPS encountered a fatal error during upgrade of the catalog.

Action: Please refer to the upgrade log file and to OBIPS log files for details of the errors.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02719: Error granting {0} permission to app role {1}

Cause: See secondary error message for root cause.

Action: The permission may need to be granted manually.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02720: RPD migration utility encountered the following fatal error: {0}

Cause: RPD migration utility failed to complete successfully.

Action: Please review the above error messages and take appropriate action.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02721: The Upgrade assistant failed to convert the 10g Administrator user name

Cause: RPD migration utility failed to complete successfully.

Action: Please create an Administrator user in the 10g RPD with an ASCII name.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02722: The Upgrade assistant failed to convert the 10g Administrator password

Cause: RPD migration utility failed to complete successfully.

Action: Please change the 10g RPD Administrator password to an ASCII string.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02723: The Upgrade assistant failed to convert the 11g RPD ecryption password

Cause: RPD migration utility failed to complete successfully.

Action: Please select a different password.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02801: Directory {0} does not exist.

Cause: Non existent directory mentioned.

Action: Please mention a location that is a existing directory.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02802: Directory {0} is not readable.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02803: Directory {0} is not writable.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02804: Target directory {0} must have space >= source directory.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02805: Insufficient arguements passed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02806: Invalid arguements passed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02807: Invalid source file type passed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02808: No valid report file found for upgrade in the source directory

Cause: No valid report file found for upgrade

Action: Please make sure there are valid report files in the source directory.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02901: unable to connect to the SOA server at {0}:{1}

Cause: SOA Connection Details are not correct or the SOA server is down.

Action: Check the SOA connection details, start the SOA server if it is down.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02902: {0} not found. Upgrade cannot Continue

Cause: 9102 Patch detected but {0} not found

Action: Make sure that {0} is present under {1}
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02903: Unable To Connect to target Database

Cause: DB is not reachable

Action: Make sure DB is up and running and reachable
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02904: Unexpected Error

Cause: Unexpected behavior

Action: See the secondary error message in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02905: SQL error [{0}]

Cause: JDBC error while executing query

Action: Make sure DB is reachable and configured properly
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02906: An unknown error occured [{0}]

Cause: Unknown

Action: See the secondary error message in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02907: Error while transforming {0} [contents to {1} format]

Cause: Transforming error

Action: See the secondary error message in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02908: Error while unmarshalling oim-config.xml

Cause: Unmarshalling error

Action: See the secondary error message in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02909: Error while locating the file {0}

Cause: Unable to find file

Action: Make sure path is correct
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02910: Error while generating {0}

Cause: Error during creation

Action: See the secondary error message in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02912: An error uccured while upgrading the feature {0}

Cause: Problem in feature upgrade

Action: See the secondary error message in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02913: Please run Admin and oimserver first to populate MDS , then run feature Upgrade

Cause:

Action:
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02914: {0} location Not valid

Cause:

Action:
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02915: Please perform schema upgrade prior to performing feature upgrade

Cause:

Action:
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02916: Error in loading {0}

Cause: Loading file

Action: Make sure the file is present at the correct location in correct format
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02917: [{0}] Error while while updating the failure state of the feature : [{1}]

Cause: Logging error

Action: See the secondary error message in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02918: MT Plugin can not be run unless Schema and Feature Upgrade are successful

Cause:

Action:
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02919: Failed to load XML. Unable to find record in

Cause: Record not found

Action: See the secondary error message in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02920: Error while performing I/O [{0}]

Cause: Error in I/O

Action: Make sure path and format is correct
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02921: Database connection is null

Cause: DB error

Action: Make sure Db is up and running
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02922: Problem in featchin data from {0} table

Cause: DB error

Action: See the secondary error message in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02923: {0} is null

Cause: Object uninitialized/doesnt exist

Action: See the secondary error message in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02924: Error while copying the {0} to {1}

Cause: I/O Error

Action: Make sure source file exists, destination is writable, and there is space on disk
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02925: Error in importing {0}

Cause: Import error

Action: See the secondary error message in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02926: OIM schema is null

Cause: Error - OIm schema found to be null

Action: Verify OIM schema
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02927: Error while creating {0} for {1}

Cause: Unable to create object

Action: Make sure path is correct and there is space on file system
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02928: No record found in {0} table

Cause: Database Table empty

Action: See the secondary error message in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02929: Error while encrypting data

Cause: Problem with data encryption

Action: See the secondary error message in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02930: Rollback failed

Cause: Error while rolling back the transaction

Action: See the exception details in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02931: Commit failed

Cause: Error while committing the transcation

Action: See the exception details in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02932: updated status update in {0} failed [for key]

Cause: Error while updating DB Table

Action: See the exception details in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02933: encrypted data update in schema table failed.

Cause: Error while updating encrypted data in schema table

Action: See the exception details in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02934: [{0}] Error while retrieving all the groups information :

Cause: Error while retrieving all the groups information

Action: See the exception details in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02935: Error while retrieving all the organizations information :

Cause: Error while retrieving all the organizations information

Action: See the exception details in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02936: Error while finding user form list

Cause: Error while finding user form list

Action: See the exception details in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02937: Error while closing db resources

Cause: Error while closing db resources

Action: See the exception details in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02938: Error while finding group list

Cause: Error while finding group list

Action: See the exception details in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02939: Error in exporting the files to MDS

Cause: Error while exporting the files to MDS

Action: See the secondary error message in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02940: Error while parsing

Cause: Error while parsing

Action: See the secondary error message in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02941: [{0}] error occured in request data set generation

Cause: Error occured in request data set generatio

Action: See the secondary error message in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02942: Error while finding field label for field :

Cause: Error while finding field label for a field

Action: See the secondary error message in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02943: Error occured while writing dataset to file

Cause: Error occured while writing dataset to file

Action: See the secondary error message in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02944: [{0}] error while finding IT resource type

Cause: error while finding IT resource type

Action: See the secondary error message in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02945: [{0}] error while interacting with data base

Cause: error while interacting with data base

Action: See the secondary error message in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02946: [{0}] error while creating scheduler task

Cause: error while creating a scheduler task

Action: See the secondary error message in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02947: Error while converting to xml

Cause: Error while converting to xml format

Action: See the secondary error message in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02948: SOD Upgrade : Error in checking OIM Version

Cause: Error in version checking while doing SOD upgrade

Action: See the secondary error message in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02949: Jobs does not exist for the task defintion:

Cause: Jobs does not exist for the given task defintion.

Action: See the secondary error message in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02950: Unable to seed scheduler data due to configuration problems.

Cause: Unable to seed scheduler data due to configuration problems

Action: Contact System Administrator
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02951: Error while Scheduling the jobs

Cause: Error while Scheduling the jobs

Action: See the secondary error message in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02952: Error while loading Custom OES polices

Cause: Error while loading Custom OES Polcies

Action: See the secondary error message in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02953: Error while generating report for feature {0}

Cause: Error while genrating Report

Action: See the secondary error message in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02954: Error in encoding Lookup Query

Cause: Error while encoding Lookup Query

Action: See the secondary error message in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02955: [{0}] error while retrieving job paramaters

Cause: error while retrieving job paramaters

Action: See the secondary error message in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02956: Unable to find source for jobs

Cause: Unable to find source for jobs

Action: See the secondary error message in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02957: [{0}] error while fetching job keys

Cause: Error while fetching job keys

Action: See the secondary error message in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02958: Error in obtaining default locale code

Cause: Error while obtaining default locale code

Action: See the secondary error message in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02959: User Customization Upgrade :Error in updating User Display Name

Cause: Error in updating User Display Name while performing User Customization Upgrade

Action: See the secondary error message in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02960: User Customization Upgrade :Error in generating display name

Cause: Error in generating display name while performing User Customization Upgrade

Action: See the secondary error message in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02961: Error in Updating Self registration form changes

Cause: Error in Updating Self registration form changes

Action: See the secondary error message in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02962: Self Register Form Update: error in parsing [{0}]

Cause: Parsing error during Self Register Form Update

Action: See the secondary error message in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02963: Error in retrieving the customized search attributes

Cause: Error in retrieving the customized search attributes

Action: See the secondary error message in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02964: JAXB Error while updating User.xml with search Attributes

Cause: JAXB Error while updating User.xml with search Attributes

Action: See the secondary error message in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02965: File not Found Error while updating User.xml with search Attributes

Cause: File not Found Error while updating User.xml with search Attributes

Action: See the secondary error message in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02966: User Customization Upgrade :Error in updating User Common Name

Cause: Error in updating User Common Name while performing User Customization Upgrade

Action: See the secondary error message in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02967: Error while finding group name

Cause: Error while finding group name

Action: See the secondary error message in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02968: Error while retrieving organization list

Cause: Error while retrieving organization list

Action: See the exception details in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02969: Exception occured while reading the file {0}

Cause: Exception occured while reading file

Action: Make sure source file exists, destination is writable, and there is space on disk
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02970: Role Name Uniqueness : Error in updating {0}

Cause: Error in updating during Role Name Uniqueness

Action: See the exception details in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02971: SQL Error while setting user lookup value

Cause: SQL Error while setting user lookup value

Action: See the secondary error message in the log file for the cause of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-05001: The 10g table {0}.{1} does not use the default columns. It cannot be upgraded

Cause: The 10g table metadata must not have been changed.

Action: Select a 10g table with the default columns for upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-05002: The schema {0} does not exist.

Cause: The upgrade assistant could not find the schema.

Action: Select a table which contains the schema.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-05003: The table {0} does not exist.

Cause: The upgrade assistant could not find the table.

Action: Check the upgrade assistant has access to the table.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-05004: The table {0} is not empty.

Cause: Cannot upgrade into a non-empty table.

Action: Provide an 11g schema with empty tables.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-05101: Audit Server database schema has already been updated.

Cause: Specified Audit Server database schema has already been updated.

Action: No user action is required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGCMP-05102: Audit Server database schema successfully updated.

Cause: Specified Audit Server database schema was successfully updated.

Action: No user action is required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGCMP-05103: The Audit schema updated is INVALID.

Cause: Specified Audit Server database schema was updated but is invalid.

Action: Restore the Audit Server database from a backup and retry.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-05104: Audit Server database schema is valid after update.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGCMP-05105: Audit Server database schema update failed.

Cause: Specified Audit Server database schema update failed.

Action: Check the log file and if necessary restore the database from backup.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-05106: Updating Audit Server database objects to PS2.

Cause: The Audit Server database schema update script is now running.

Action: This is an informational message. No user action is required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGCMP-05107: A SQL statement failed in Audit Server database schema update.

Cause: A SQL error took place, likely because there are data in the OAAM table. Please note that although created in AS 11gR1 PS1 release, the OAAM table in audit schema is supposed to start being used since AS 11gR1 PS2 release. It is supposed to be empty now.

Action: Please move the existing data out of the OAAM table, for the schema to be upgraded. It is important to ensure that the table definition is consistent with the event definitions in component_events.xml.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-05201: Seed data has already been loaded.

Cause: Seed data for specified database schema has already been loaded.

Action: No user action is required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGCMP-05202: Failure during the SDF run: {0}.

Cause: An error occurred during seed data loading stage.

Action: Contact Oracle Support Services with the log file details.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-05203: Error contacting database: {0}.

Cause: An error occurred when trying to contact/connect to Oracle Database.

Action: 1. Check that Database is running. 2. Check the preceding messages in this log for any errors. 3. Contact Oracle Support Services if the above steps do not help resolve the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-05401: Database type {0} is not supported.

Cause: Repository upgrade was run against an unsupported database type.

Action: Run the upgrade against either an Oracle, Microsoft SQL Server or IBM DB2 database.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-05402: Upgrade installation files could not be found.

Cause: The SQL files required to perform upgrade could not be found in the Oracle home.

Action: Ensure you are running PSA from a WebCenter Oracle home.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-05403: The expected temporary tablespace {0} could not be found.

Cause: A temporary tablespace with the name '[prefix]_IAS_TEMP' needs to exist in the database instance but it could not be found.

Action: Create a user temporary tablespace with the name '[prefix]_IAS_TEMP' using the DB2 command line and rerun PSA.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-05501: Oracle Metadata Services schema upgrade is invalid.

Cause: Specified Metadata Services schema was updated but is invalid.

Action: Restore the Metadata Services schema from a backup and retry. Check the error messages in Oracle Metadata service component log files. Correct the problem before running the Assistant again.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-05502: The upgrade is not supported from Oracle Metadata Services schema version of {0}.

Cause: An unsupported base schema version was being upgraded.

Action: Refer to the Oracle Metadata Services Upgrade Guide for supported versions to upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-05503: Oracle Metadata Service schema version {0} is latest one. Upgrade is not required.

Cause: Specified Oracle Metadata Services database schema version is the latest one. Upgrade is not required.

Action: No user action is required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGCMP-05504: Error in upgrading Oracle Metadata Services schema.

Cause: An unexpected error occurred during Oracle Metadata Services schema upgrade.

Action: Check the error messages in Oracle Metadata service component log files. Correct the problem before running the Assistant again. Contact Oracle Support Services if you are unable to correct the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-05505: Error occurred while verifying the character set in target Metadata Services schema

Cause: Some SQL error occurred while verifying the character set in target Metadata Services schema.

Action: Check the error messages in Oracle Metadata service component log files. Correct the problem before running the Assistant again. Contact Oracle Support Services if you are unable to correct the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-05506: Error occurred while closing the resources during Metadata Services schema upgrade

Cause: Some error occurred while closing the resources during Metadata Services schema upgrade.

Action: Check the error messages in Oracle Metadata service component log files. Correct the problem before running the Assistant again. Contact Oracle Support Services if you are unable to correct the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-05507: Error occurred while closing Metadata Services schema upgrade log files.

Cause: An unexpected error occurred while closing Metadata Services schema upgrade log files.

Action: Check the error messages in Oracle Metadata service component log files. Correct the problem before running the Assistant again. Contact Oracle Support Services if you are unable to correct the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-06001: BI Platform database schema has already been updated.

Cause: Specified BI Platform database schema has already been updated.

Action: No user action is required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGCMP-06002: BI Platform database schema successfully updated.

Cause: Specified BI Platform database schema was successfully updated.

Action: No user action is required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGCMP-06003: BI Platform database schema is valid after update.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGCMP-06004: The BI Platform database schema updated is INVALID.

Cause: Specified BI Platform database schema was updated but is invalid.

Action: Restore the BI Platform database from a backup and retry.
Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-06005: BI Platform database schema update failed.

Cause: Specified BI Platform database schema update failed.

Action: Check the log file and if necessary restore the database from backup.
Level: 1

Type: ERROR

Impact: Upgrade

100 WCS-03051 to WCS-47826

WCS-03051: No event is selected.

Cause: There was invalid or missing information in the connection.xml or adf-config.xml file.

Action: Verify that the connections.xml and adf-config.xml file contains a valid entry with the correct connection information.
Level: 1

Type: WARNING

Impact: Other

WCS-03052: event date validation error

Cause: An invalid date or time was selected for the event.

Action: Verify the date and time.
Level: 1

Type: ERROR

Impact: Other

WCS-03053: No upcoming events were found.

Cause: Either the connections.xml file did not contain a valid connection entry for the Group Space Events service, or the adapter was not defined.

Action: Verify that the connections.xml file contains a valid connection for the Group Space Events service, and the Group Space Events server is running
Level: 1

Type: WARNING

Impact: Other

WCS-03101: The Events service is not able to acquire an adapter from the server.

Cause: Either the connections.xml file did not contain a valid connection entry for the Personal Events service, or the adapter was not defined.

Action: Verify that the connections.xml file contains a valid connection entry for the Personal Events service, and the specified adapter is defined.
Level: 1

Type: ERROR

Impact: Other

WCS-03102: The Events service is unavailable.

Cause: The connections.xml file either did not contain a valid connection entry for the Personal Events service, or it was missing the entry for Personal Events with the state attribute set to default.

Action: Verify that the connections.xml file contains a valid connection entry for the Personal Events service, and the Personal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03103: Data query in Personal Events service failed

Cause: Either the connections.xml file did not contain a valid connection entry for the Personal Events service, or the Personal Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Personal Events service, and the Personal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03104: Create event in Personal Events service failed

Cause: Either the connections.xml file did not contain a valid connection entry for the Personal Events service, or the Personal Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Personal Events service, and the Personal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03105: Update event in Personal Events service failed

Cause: Either the connections.xml file did not contain a valid connection entry for the Personal Events service, or the Personal Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Personal Events service, and the Personal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03106: Delete event in Personal Events service failed

Cause: Either the connections.xml file did not contain a valid connection entry for the Personal Events service, or the Personal Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Personal Events service, and the Personal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03107: failure to send event mail in Personal Events service

Cause: Either the connections.xml file did not contain a valid connection for the Mail service, or the Mail server was down.

Action: Verify that the connections.xml file contains a valid connection for the Mail service, and that the Mail server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03108: failure to retrieve online meeting

Cause: Either the connections.xml file did not contain a valid connection entry for the Conference service, or the Conference server was down.

Action: Verify that the connections.xml file contains a valid connection for the Conference service, and the Conference server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03109: failure to retrieve personal event list

Cause: Either the connections.xml file did not contain a valid connection entry for the Personal Events service, or the Personal Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Personal Events service, and the Personal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03110: failure to retrieve personal event detail

Cause: Either the connections.xml file did not contain a valid connection entry for the Personal Events service, or the Personal Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Personal Events service, and the Personal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03111: The Personal Events service credential is not configured properly.

Cause: The Personal Events service credential was not configured properly.

Action: Verify that the Personal Events service credential is correct, and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-03112: The Personal Events service is not properly configured.

Cause: The Personal Events service was not properly configured in connections.xml.

Action: Verify that the connections.xml file contains a valid entry for the Personal Events service.
Level: 1

Type: ERROR

Impact: Other

WCS-03113: The Personal Events server is not available.

Cause: The Personal Events server was not available.

Action: Verify that the connections.xml file contains a valid entry for the Personal Events service, and the Personal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03114: failure to send personal event

Cause: Either the connections.xml file did not contain a valid connection for the Mail service, or the Mail server was down.

Action: Verify that the connections.xml file contains a valid connection for the Mail service, and the Mail server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03115: failure to log in to the Exchange server

Cause: The credential for the Personal Events service was not configured properly or the Exchange server was not running.

Action: Verify that the credential for the Personal Events service is correct, and the Exchange server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03116: failure to log in to the Exchange server

Cause: The credential for the Personal Events service credential was not configured properly.

Action: Verify that the credential for the Personal Events service is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-03201: The Events service is not able to acquire an adapter for an Events server.

Cause: Either the connections.xml file did not contain a valid connection entry for the Group Space Events service.

Action: Verify that the connections.xml file contains a valid connection entry for the Group Space Events service.
Level: 1

Type: ERROR

Impact: Other

WCS-03202: The Events service is unavailable.

Cause: Either the connections.xml file did not contain a valid connection entry for the Group Space Events service, or the Group Space Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Group Space Events service, and the Group Space Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03203: Data query in Events service failed

Cause: Either the connections.xml file did not contain a valid connection entry for the Group Space Events service, or the Group Space Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Group Space Events service, and the Group Space Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03204: Create event in Events service failed

Cause: Either the connections.xml file did not contain a valid connection entry for the Group Space Events service, or the Group Space Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Group Space Events service, and the Group Space Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03205: Update event in Events service failed

Cause: Either the connections.xml file did not contain a valid connection entry for the Group Space Events service, or the Group Space Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Group Space Events service, and the Group Space Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03206: Delete event in Events service failed

Cause: Either the connections.xml file did not contain a valid connection entry for the Group Space Events service, or the Group Space Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Group Space Events service, and the Group Space Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03207: Send event mail in Events service failed

Cause: Either the connections.xml file did not contain a valid connection for the Mail service, or the Mail server was down.

Action: Verify that the connections.xml file contains a valid connection for the Mail service, and Mail server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03208: The changes to the event cannot be saved.

Cause: The event was modified or deleted by another user after the event was retrieved.

Action: Refresh the Events task flow to view changes, and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-03209: cannot create the category

Cause: The category could not be created because a category of the same name already exists.

Action: Select the existing category.
Level: 1

Type: ERROR

Impact: Other

WCS-03210: cannot add the group space event to the personal calendar

Cause: Either the connections.xml file did not contain a valid connection entry for the Personal Events service, or the Personal Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Personal Events service, and the Personal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03211: cannot add the group space event to the personal calendar

Cause: The Personal Events service was not configured properly in connections.xml or the Personal Events service is down.

Action: Verify that the connections.xml file contains a valid connection entry for the Personal Events service, and the Personal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03212: cannot add the group space event to the personal calendar

Cause: The credential for the Personal Events service was not configured properly.

Action: Verify that the credential for the Personal Events service is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-03213: failure to create category

Cause: Either the connections.xml file did not contain a valid connection entry for the Group Space Events service, or the Group Space Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Group Space Events service, and the Group Space Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03214: failure to retrieve categories

Cause: Either the connections.xml file did not contain a valid connection entry for the Group Space Events service, or the Group Space Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Group Space Events service, and the Group Space Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03215: failure to retrieve group space event list

Cause: Either the connections.xml file did not contain a valid connection entry for the Group Space Events service, or the Group Space Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Group Space Events service, and the Group Space Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03216: failure to retrieve group space event detail

Cause: Either the connections.xml file did not contain a valid connection entry for the Group Space Events service, or the Group Space Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Group Space Events service, and the Group Space Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03217: failure to check the relationship for the event

Cause: Either the connections.xml file did not contain a valid connection entry for the Relationship service,or the Relationship service was down.

Action: Verify that the connections.xml file contains a valid entry for the Relationship service, the Relationship service is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03218: failure to save the display mode preference

Cause: Either the connections.xml file did not contain a valid connection entry for the Preferences service, or the Preferences service was down.

Action: Verify that the connections.xml file contains a valid entry for the Preferences service, and the Preferences service is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03219: failure to change the repeat attributes

Cause: Either the connections.xml file did not contain a valid connection entry for the Events service, or the Events service was down.

Action: Verify that the connections.xml file contains a valid entry for the Events service, and the Events service is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03220: The event was deleted by another user after you retrieved it. Refresh the Events task flow to see the changes if necessary.

Cause: The event was deleted by another user after you retrieved it.

Action: Refresh the Events task flow to view changes, and try again.
Level: 1

Type: WARNING

Impact: Other

WCS-03221: The event was updated by another user after you retrieved it. Refresh the Events task flow to see the changes if necessary.

Cause: The event was updated by another user after you retrieved it.

Action: Refresh the Events task flow to view changes, and try again.
Level: 1

Type: WARNING

Impact: Other

WCS-03222: You do not have permission to update this event or your permission to update this event is revoked. Refresh the Events task flow to see the changes if necessary.

Cause: You do not have permission to update this event or your permission to update this event is revoked.

Action: Refresh the Events task flow to view changes, and try again.
Level: 1

Type: WARNING

Impact: Other

WCS-03223: You do not have permission to view this event or your permission to view this event is revoked. Refresh the Events task flow to see the changes if necessary.

Cause: You do not have permission to view this event or your permission to view this event is revoked.

Action: Refresh the Events task flow to view changes, and try again.
Level: 1

Type: WARNING

Impact: Other

WCS-03224: You do not have permission to create the event or your permission to create the event is revoked. Refresh the Events task flow to see the changes if necessary.

Cause: You do not have permission to create this event or your permission to create this event is revoked.

Action: Refresh the Events task flow to view changes, and try again.
Level: 1

Type: WARNING

Impact: Other

WCS-03225: You do not have permission to delete the event or your permission to delete the event is revoked. Refresh the Events task flow to see the changes if necessary.

Cause: You do not have permission to delete this event or your permission to delete this event is revoked.

Action: Refresh the Events task flow to view changes, and try again.
Level: 1

Type: WARNING

Impact: Other

WCS-03226: You do not have permission to manage the event or your permission to manage the event is revoked. Refresh the Events task flow to see the changes if necessary.

Cause: You do not have permission to manage this event or your permission to manage this event is revoked.

Action: Refresh the Events task flow to view changes, and try again.
Level: 1

Type: WARNING

Impact: Other

WCS-03227: Event not found.

Cause: The event doesn't exist or was deleted.

Action: The event doesn't exist or was deleted.
Level: 1

Type: WARNING

Impact: Other

WCS-03301: The Web Conference service is unavailable.

Cause: Either the connections.xml file did not contain a valid connection entry, or the adapter was not defined in the adf-config.xml file.

Action: Verify that the connections.xml file contains a valid connection entry, and the specified adapter is defined in the adf-config.xml file.
Level: 1

Type: ERROR

Impact: Other

WCS-03302: The Web Conference service is unavailable.

Cause: The connections.xml file either did not contain a valid connection entry or the entry for conference service with the state attribute set to default was missing.

Action: Verify that the connections.xml file contains a valid connection entry and that the conference server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03303: failure to query data in WebCenter Conference service

Cause: There was an issue with the connections.xml file, or the Conference server was down.

Action: Verify that the connections.xml file contains a valid connection entry and that the Conference server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03304: failure to create conference in WebCenter Conference service

Cause: There was an issue with the connections.xml file, or the Conference server was down.

Action: Verify that the connections.xml file contains a valid connection entry and that the Conference server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03305: failure to update conference in WebCenter Conference service

Cause: There was an issue with the connections.xml file, or the Conference server was down.

Action: Verify that the connections.xml file contains a valid connection entry and that the Conference server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03306: failure to delete conference in WebCenter Conference service

Cause: There was an issue with the connections.xml file, or the Conference server was down.

Action: Verify that the connections.xml file contains a valid connection entry and that the Conference server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03307: failure to retrieve personal meetings

Cause: There was an issue with the connections.xml file, or the Conference server was down.

Action: Verify that the connections.xml file contains a valid connection entry and that the Conference server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03308: The Conference service is not properly configured.

Cause: The Conference service was not properly configured in connections.xml.

Action: Verify that the connections.xml file contains a valid entry for the Conference service.
Level: 1

Type: ERROR

Impact: Other

WCS-03309: The Conference service is properly not configured.

Cause: The Conference service was not configured in connections.xml.

Action: Verify that the connections.xml file contains a valid entry for the Conference service.
Level: 1

Type: WARNING

Impact: Other

WCS-03310: The Conference service is not properly configured.

Cause: The ambiguous connections of Conference service were found in connections.xml.

Action: Verify that the connections.xml file contains a valid entry for the Conference service.
Level: 1

Type: ERROR

Impact: Other

WCS-03701: WebCenter Tasks service unable to acquire a data connection.

Cause: There was an issue with the connections.xml file, or the BPEL server was down.

Action: Verify that the connections.xml file contains a valid entry with the bpel.state set to default, and that the BPEL server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03702: Tasks query failed in WebCenter Task service.

Cause: There was an issue with the connections.xml file, or the BPEL server was down.

Action: Verify that the connections.xml file contains a valid entry with the bpel.state set to default, and that the BPEL server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03703: Create task failed in WebCenter Task service.

Cause: There was an issue with the connections.xml file, or the BPEL server was down.

Action: Verify that the connections.xml file contains a valid entry with the bpel.state set to default, and that the BPEL server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03704: Task update failed in WebCenter Tasks service.

Cause: There was an issue with the connections.xml file, or the BPEL server was down.

Action: Verify that the connections.xml file contains a valid entry with the bpel.state set to default, and that the BPEL server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03705: Task purge failed in WebCenter Tasks service.

Cause: There was an issue with the connections.xml file, or the BPEL server was down.

Action: Verify that the connections.xml file contains a valid entry with the bpel.state set to default, and that the BPEL server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03706: Task delete failed in WebCenter Tasks service.

Cause: There was an issue with the connections.xml file, or the BPEL server was down.

Action: Verify that the connections.xml file contains a valid entry with the bpel.state set to default, and that the BPEL server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-04001: unable to resolve the name {0}

Cause: The object with the given name could not be found.

Action: Check the JNDI configuration or the context passed.
Level: 1

Type: ERROR

Impact: Other

WCS-04002: ADFConfig does not contain adf-collaboration-config details with namespace: {0}.

Cause: The collaboration configuration tag 'adf-collaboration-config' might have been missing in ADFConfig.

Action: Ensure that the adf-config.xml file contains the adf-collaboration-config tag.
Level: 1

Type: ERROR

Impact: Other

WCS-04003: No adapter found for service {0}

Cause: No adapter configuration found or the implementation class could not be loaded.

Action: Ensure adapter is configured properly or change the SessionFactory to override the default behavior.
Level: 1

Type: ERROR

Impact: Other

WCS-04004: unable to load the class {0}

Cause: The class named in the error message was not available in the class path.

Action: Check the class path and ensure this class is available.
Level: 1

Type: ERROR

Impact: Other

WCS-04005: unable to load the class {0}, due to: {1}

Cause: Either the class named in the error message was not available in the class path or it could not be instantiated.

Action: Check the logs for more details. Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-04006: ADFConfig {0} {1} does not contain the required attribute {1}.

Cause: The required attribute was missing from the configuration.

Action: Ensure that the required attribute is added to the configuration.
Level: 1

Type: ERROR

Impact: Other

WCS-04007: The attachment size is too large to be consumed.

Cause: The storage quota was exceeded.

Action: Select a different attachment with a smaller size.
Level: 1

Type: WARNING

Impact: Other

WCS-04008: The attachment type is not supported.

Cause: The attachment type was not supported.

Action: Try with a different MIME type.
Level: 1

Type: WARNING

Impact: Other

WCS-04009: The attachment cannot be found.

Cause: The attachment was not readable.

Action: Try a different attachment.
Level: 1

Type: WARNING

Impact: Other

WCS-04010: failure to create, update, or fetch the service configuration file {0}, due to: {1}

Cause: One of the following was the cause: There was a concurrent modification by another user; there was an MDS I/O exception; the metadata was not found; a validation error occurred; or the update was not supported.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-04011: unable to find the service configuration file {0}, due to: {1}

Cause: The service was not provisioned for this group space.

Action: Provision this service or contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-04012: unable to find the credentials for user {0}

Cause: The credentials were either not supplied, or were invalid.

Action: Supply credentials using the External Application configured for the service.
Level: 1

Type: WARNING

Impact: Other

WCS-04013: failure to authenticate the user {0}, due to: {1}

Cause: There was a failure while connecting to server, or the credentials were invalid.

Action: Ensure the credentials are supplied and are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-04014: no connections available for: {0}

Cause: There are no connections defined for this connection type.

Action: At least one connection must be defined for this connection type.
Level: 1

Type: WARNING

Impact: Other

WCS-04015: There are multiple connections defined for the connection type {0}, but no default connection is specified.

Cause: Multiple connections of this type were defined, but the default connection was not specified.

Action: Select the appropriate connection for this type and mark it as the default.
Level: 1

Type: ERROR

Impact: Other

WCS-04016: unable to look up connection with name {0}

Cause: Either the connection name was wrong or the connection was deleted.

Action: Verify the name of the connection supplied and also ensure that the connection with this name is available.
Level: 1

Type: ERROR

Impact: Other

WCS-04017: failure to create session instance for: {0}

Cause: An instantiation exception occurred for the session class. Either this class was not a valid class or it could not be loaded from the class path.

Action: Verify that the session class supplied is a valid class, and that it is available in the class path.
Level: 1

Type: ERROR

Impact: Other

WCS-04018: failure to create session for {0}, due to: {1}

Cause: Either the required configuration was missing or class was not found.

Action: Verify that the session class supplied is a valid class, and that it is available in the class path.
Level: 1

Type: ERROR

Impact: Other

WCS-04019: There are multiple adapters for the session {0}, but the default adapter is not specified.

Cause: Multiple adapters were defined for this session type, but the default adapter was not specified in the connection.

Action: Update the connection and ensure that the adapter name is specified (ensure that the "adapter.name" property exists).
Level: 1

Type: ERROR

Impact: Other

WCS-04020: No adapter found with name {0}.

Cause: Adapter not found with the given name.

Action: Ensure the adapter with this name configured in the adf-config.xml file.
Level: 1

Type: ERROR

Impact: Other

WCS-04021: Not an instance of {1} : {0}

Cause: Supplied class is not an instance of SessionManager class.

Action: Check the service configuration property "session.manager.class".
Level: 1

Type: ERROR

Impact: Other

WCS-04022: The {0} service is unavailable.

Cause: Cannot establish connection to the server, either the server is down or the connect details are wrong..

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-04023: Cache not available.

Cause: Cache is not initialized.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-04024: unable to find object {0} in the cache

Cause: The object was either not cached or it had expired.

Action: Ensure that the object is cached.
Level: 1

Type: WARNING

Impact: Other

WCS-04025: Session not initialized {0}.

Cause: Either initialize method on the session is not invoked or initialization has failed.

Action: Check logs for more details or Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-04026: null session instance is returned from SessionFactory: {0}

Cause: The SessionFactory returned a null session, and it should not.

Action: Check the SessionFactory implementation for more details or contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-04027: Session Factory class not defined.

Cause: Either the service-config for the session is missing or "session.factory.class" property is missing.

Action: Check the service-config.xml for the given session type exists and "session.factory.class" property is defined with a qualified class name that is available in the classpath. Contact system administrator for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-04030: System user session is requested from session {0}, but administrator user name is not defined in the connection nor in adf-config.

Cause: Missing "admin.user" property from connection and/or adf-config.xml.

Action: Ensure that either the connection or ADF service-config contains a property called "admin.user" with a valid administrator user.
Level: 1

Type: WARNING

Impact: Other

WCS-04031: unknown error

Cause: An unexpected server exception occurred.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-04032: Could not get access to cache object.

Cause: API should be invoked only for getting access to the root cache.

Action: Try using correct API.
Level: 1

Type: WARNING

Impact: Other

WCS-04033: Invalid cache name: {0}.

Cause: Cache name supplied is either empty or null.

Action: Supply valid name for the cache.
Level: 1

Type: WARNING

Impact: Other

WCS-04034: Not able to fetch data due to {0}.

Cause: Might be because the backend system is not reachable.

Action: Try after sometime.
Level: 1

Type: WARNING

Impact: Other

WCS-04035: Session Type for Session instance {0} is null.

Cause: Session Factory does not set the SessionType on the Session instance created.

Action: Check the session factory implementation.
Level: 1

Type: WARNING

Impact: Other

WCS-04036: User not found: {0}.

Cause: Unable to find the user with the supplied name in the user repository.

Action: Check user with the given identity exists in the user repository.
Level: 1

Type: WARNING

Impact: Other

WCS-04037: Supplied class {0} is not an instance of {1}.

Cause: Supplied class is not an instance of SessionFactory class.

Action: Check the adf-config.xml or service-config.xml configuration property "session.factory.class".
Level: 1

Type: ERROR

Impact: Other

WCS-04039: Session Manager instance creation failed for {0}

Cause: Either the required configuration is missing or class is not found..

Action: Check the class supplied is a valid class and its available in the classpath.
Level: 1

Type: ERROR

Impact: Other

WCS-04040: CacheFactory not specified.

Cause: CacheFactory instance is not found.

Action: Set appropriate CacheFactory instance on the Cache class.
Level: 1

Type: ERROR

Impact: Other

WCS-04201: Error loading relationship service implementation

Cause: The relationship service encountered a problem while loading a relationship service implementation.

Action: Check the stack trace for more information
Level: 1

Type: ERROR

Impact: Other

WCS-04202: Relationship Service is already registered: {0}, ignoring...

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-04206: Error checking create permission

Cause: There was an error loading the relationship security provider.

Action: Check to make sure that the relationship security provider is properly configured.
Level: 1

Type: ERROR

Impact: Other

WCS-04207: Could not instantiate relationship repository

Cause: The relationship service encountered a problem while instantiating the repository.

Action: Check the stack trace for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-04208: jdbc/WebCenterDS data source not found: {0}

Cause: The jdbc/WebCenterDS data source could not be found.

Action: Ensure that the jdbc/WebCenterDS data source is created.
Level: 1

Type: WARNING

Impact: Other

WCS-04301: Relationship repository is not available.

Cause: An error was encountered while checking if the relationship repository was available.

Action: Check the log for errors that may have caused this.
Level: 1

Type: ERROR

Impact: Other

WCS-04302: Relationship already exists between [sourceApplicationId={0} sourceResourceId={1}] and [targetApplicationId={2} targetResourceId{3}].

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-04303: Resource does not exist [applicationId={0} resourceId={1}].

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-04304: Target resource was not found [targetApplicationId={0} targetResourceId={1}].

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-04305: Relationship was marked as a bi-directional relationship, however no target to source back relationship was found for target [targetApplicationId={0} targetResourceId={1}].

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-04306: Source object was not found [sourceApplicationId={0} sourceResourceId={1}].

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-04401: Exception during event or action

Cause: The relationship service encountered a problem while performing an event or action

Action: Check the application log for more information on the cause
Level: 1

Type: ERROR

Impact: Other

WCS-04403: Could not find relationship service {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-04404: Service {0} threw exception for getViewObject() on RelatedObject {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-04405: linksDetailedPanelWindow is null: cannot add partial target to RequestContext.

Cause: The relationship popup task flow is not included in the page.

Action: Check to make sure the relationship popup task flow is included in the page.
Level: 1

Type: WARNING

Impact: Other

WCS-04406: Cannot get current RichLinksDetailButtonRow. FacesContext.getCurrentInstance().getRenderKit() returned null for component: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-04407: Exception while checking for existing links

Cause: An error was encountered while checking for existing links.

Action: Check the application log for more information on the cause.
Level: 1

Type: ERROR

Impact: Other

WCS-04408: Error instantiating RichLinksDetailButtonRow

Cause: The relationship service encountered a problem while instantiating a custom component.

Action: Check the relationship links button component for valid attributes.
Level: 1

Type: ERROR

Impact: Other

WCS-04409: Error instantiating RichLinskDetailMenuItem

Cause: The relationship service encountered a problem while instantiating a custom component.

Action: Check the relationship links menu component for valid attributes.
Level: 1

Type: ERROR

Impact: Other

WCS-04410: Could not find Links Detail Popup in the LinksDetailBean bean

Cause: The relationship service encountered a problem while encoding the popup.

Action: Make sure the links popup task flow is included in the page.
Level: 1

Type: ERROR

Impact: Other

WCS-04412: Attribute value is null for component: {0}

Cause: A required attribute value is bound to a null value.

Action: Make sure the required attributes of this component are bound to non-null values.
Level: 1

Type: WARNING

Impact: Other

WCS-04413: An exception occurred while parsing parameter

Cause: A number format exception was encountered while parsing a parameter.

Action: Make sure the window width/height parameters for launching relationship views are valid numbers.
Level: 1

Type: WARNING

Impact: Other

WCS-04414: Got null from registry for service ID {0}, including all target services: {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-04415: Service {0} returned null for target view object with objectId: {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-04418: User principal is null.

Cause: The user principal returned by the security context was null.

Action: Make sure security is property configured for the application.
Level: 1

Type: WARNING

Impact: Other

WCS-04419: Links components cannot render

Cause: The links-detail-popup task flow panelWindow was not found.

Action: Make sure the view includes the links-detail-popup task flow.
Level: 1

Type: WARNING

Impact: Other

WCS-04601: unexpected error

Cause: An unexpected error occurred for the RTC service.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-04602: Unable to load RTC configuration

Cause: Connections context could not be acquired.

Action: Ensure that the connections.xml file is available and valid.
Level: 1

Type: WARNING

Impact: Other

WCS-04603: Unable to load RTC configuration

Cause: No RTC (Real-Time Communication) connection was specified.

Action: Ensure that the property 'selected.connection' for the RTC service's 'service-config' element within the application's adf-config.xml file is available with a valid RTC connection name value.
Level: 1

Type: WARNING

Impact: Other

WCS-04604: Unable to lookup RTC connection {0}

Cause: The specified connection name either did not exist or did not resolve to a valid RTC connection.

Action: Ensure that the property 'selected.connection' for the RTC service's 'service-config' element within the application's adf-config.xml file contains a valid RTC connection name (as defined in the application's connections.xml file).
Level: 1

Type: WARNING

Impact: Other

WCS-04605: Unable to load RTC adapter {0}

Cause: The specified RTC adapter name was invalid.

Action: Ensure that the property 'adapter.name' of the RTC connection is valid and the corresponding adapter definition is available within the RTC 'service-config' element in the application's adf-config.xml file.
Level: 1

Type: WARNING

Impact: Other

WCS-04606: Unable to load RTC adapter {0}

Cause: The specified RTC adapter class does not extend from IMPConnection class.

Action: Ensure that the RTC adapter class extends IMPConnection class and follows its contract.
Level: 1

Type: WARNING

Impact: Other

WCS-04607: Unable to load RTC adapter {0}

Cause: The specified RTC adapter class could not be instantiated.

Action: Ensure that the RTC adapter class extends IMPConnection class and follows its contract.
Level: 1

Type: WARNING

Impact: Other

WCS-04608: Unable to load RTC adapter {0}

Cause: The RTC configuration object was null or invalid.

Action: Ensure that the RTC configuration is valid.
Level: 1

Type: WARNING

Impact: Other

WCS-04610: Unable to create instance of the UserManager implementation class {0}.

Cause: The specified user manager class could not be instantiated.

Action: Ensure that the class exists and can be instantiated with a default constructor.
Level: 1

Type: WARNING

Impact: Other

WCS-04611: Unable to find a valid RTC connection.

Cause: No RTC connections were found within the application's connections.xml file.

Action: Ensure that there is a valid RTC connection defined in the application's connections.xml file.
Level: 1

Type: WARNING

Impact: Other

WCS-04612: Invalid RTC address resolver specified: {0}

Cause: Specified address resolver was invalid.

Action: Ensure that the resolver type is one of DEFAULT, PROFILE_ATTRIBUTE, or CUSTOM.
Level: 1

Type: WARNING

Impact: Other

WCS-04614: Invalid attribute specified for PROFILE address resolver: {0}

Cause: The specified profile attribute for the address resolver was invalid.

Action: Ensure that the 'rtc.address.resolver.mapping' attribute is not null and contains a valid profile attribute.
Level: 1

Type: WARNING

Impact: Other

WCS-04615: Unable to load custom RTC address resolver: {0}

Cause: The custom class could not be initialized.

Action: Ensure that the custom class extends RtcAddressResolver and follows the contract specified by it.
Level: 1

Type: WARNING

Impact: Other

WCS-04616: Unable to load custom RTC address resolver: {0}

Cause: No custom class was specified for the CUSTOM type RTC address resolver.

Action: Ensure that the 'rtc.address.resolver.mapping' attribute is not null and contains a fully qualified and valid class name that extends from the RtcAddressResolver class.
Level: 1

Type: WARNING

Impact: Other

WCS-04619: The RTC address resolver supplied is invalid or null.

Cause: The RTC address resolver supplied was invalid or null.

Action: Ensure that 'rtc.address.resolver.mapping' attribute is not null.
Level: 1

Type: WARNING

Impact: Other

WCS-04620: The domain supplied is invalid or null.

Cause: The domain supplied was invalid or null.

Action: Ensure that the 'domain' attribute is not null or invalid.
Level: 1

Type: WARNING

Impact: Other

WCS-04621: Invalid timeout value specified: {0} Defaulting to {1}

Cause: The presence cache timeout value was either null or not a valid number.

Action: Ensure that the 'rtc.cache.time' attribute is not null and contains a valid number.
Level: 1

Type: WARNING

Impact: Other

WCS-04625: Failed to instantiate IMPSession for the logged-in user.

Cause: The adapter class could not be instantiated.

Action: Ensure that the property 'adapter-class' has been defined for the adapter in the adf-config.xml and is valid.
Level: 1

Type: WARNING

Impact: Other

WCS-04701: Unable to load LCS adapter: base connection URL is missing.

Cause: The property 'base.connection.url' was missing.

Action: Ensure that the LCS connection entry contains the 'base.connection.url' property and points to a valid URL.
Level: 1

Type: ERROR

Impact: Other

WCS-04702: Unable to load LCS adapter: LCS PoolName is missing.

Cause: The property 'LCSPoolName' was missing.

Action: Ensure that the LCS connection entry in connections.xml contains the 'LCSPoolName' property and contains a valid LCS pool name.
Level: 1

Type: WARNING

Impact: Other

WCS-04703: Unable to perform operation {0}

Cause: Failed to perform the operation on remote Web service.

Action: Ensure that the RTC configuration is correct, the remote system is available, and the errors generated in the remote system's logs have been fixed.
Level: 1

Type: ERROR

Impact: Other

WCS-04704: Failed to log on user {0}.

Cause: User login failed.

Action: Check user credentials and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-04705: Exception caught while fetching buddy list for user {0}

Cause: Failed to retrieve buddy list from the Remote Service.

Action: Ensure that valid LCS connection entries have been supplied and the server is up.
Level: 1

Type: WARNING

Impact: Other

WCS-04706: Exception caught while fetching presence information using user account {0}

Cause: Failed to fetch presence information from the remote service .

Action: Ensure that valid LCS connection entries have been supplied and the server is up.
Level: 1

Type: WARNING

Impact: Other

WCS-04707: Failed to add user {0} to the logged in user's buddy list (logged in user:{1})

Cause: Failed to update buddy list of the user.

Action: Ensure that the server is up and responding.
Level: 1

Type: WARNING

Impact: Other

WCS-04708: Failed to remove user {0} from the logged in user's buddy list (logged in user:{1})

Cause: Failed to update buddy list of the user.

Action: Ensure that the server is up and responding.
Level: 1

Type: WARNING

Impact: Other

WCS-04751: Unable to load OCMS adapter

Cause: Missing property 'base.connection.url'

Action: Ensure that the OCMS connection entry contains the 'base.connection.url' property and points to a valid URL. It should look like http://host:port. This is the machine where the OCMS server is installed.
Level: 1

Type: WARNING

Impact: Other

WCS-04758: Exception caught while fetching buddy list for user {0}

Cause: Exception caught while fetching buddy list.

Action: Ensure that valid OCMS connection entries have been supplied and the server is up.
Level: 1

Type: WARNING

Impact: Other

WCS-04759: Failed to subscribe for presence for user {0}

Cause: The OCMS Server threw back exception while subscribing for user's presence.

Action: Ensure that valid OCMS connection entries have been supplied
Level: 1

Type: WARNING

Impact: Other

WCS-04760: Failed to do bulk subscribe using user account {0}

Cause: The OCMS Server threw back exception while subscribing for users' presence.

Action: Ensure that valid OCMS connection entries have been supplied
Level: 1

Type: WARNING

Impact: Other

WCS-04761: Failed to get bulk presence using user account {0}

Cause: Failed to fetch presence information from the remote service .

Action: Ensure that valid OCMS connection entries have been supplied and resolve any exceptions thrown during subscription.
Level: 1

Type: WARNING

Impact: Other

WCS-04762: Failed to get group space user's connection instance

Cause: Failed to login using the group space credentials.

Action: Ensure that the server is up and responding.
Level: 1

Type: WARNING

Impact: Other

WCS-04763: Exception caught while fetching presence information for user {0}

Cause: Failed to fetch presence information from the remote service .

Action: Ensure that valid OCMS connection entries have been supplied and resolve any exceptions thrown during subscription.
Level: 1

Type: WARNING

Impact: Other

WCS-04764: Failed to add user {0} to the group space user's buddy list (group space user:{1})

Cause: Failed to update buddy list of the group space user.

Action: Ensure that the server is up and responding.
Level: 1

Type: WARNING

Impact: Other

WCS-04765: Failed to remove user {0} from the group space user's buddy list (group space user:{1})

Cause: Failed to update buddy list of the group space user.

Action: Ensure that the server is up and responding.
Level: 1

Type: WARNING

Impact: Other

WCS-04768: Unable to read admin information for the OCMS Connection.

Cause: Admin information not available to establish the connection.

Action: Provide admin username and password parameters for the connection.
Level: 1

Type: ERROR

Impact: Other

WCS-04769: Unable to read buddy list information for group space user {0}.

Cause: Buddy List information cannot be read for the Group Space.

Action: Make sure that the MDS database is accessible.
Level: 1

Type: ERROR

Impact: Other

WCS-04771: Unable to read call information.

Cause: Call information cannot be read for the current third party call.

Action: Make sure that the third party service is up and running.
Level: 1

Type: ERROR

Impact: Other

WCS-04801: Invalid timeout value specified: {0} Defaulting to {1}

Cause: The presence cache timeout value was either null or not a valid number.

Action: Ensure that the 'rtc.cache.time' attribute is not null and contains a valid number.
Level: 1

Type: WARNING

Impact: Other

WCS-04804: Unable to acquire RTC connection for user {0}. RTCService running in dummy mode.

Cause: Exception caught while initializing IMPConnection.

Action: Check the log file for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-04805: Unable to acquire associated external application details.

Cause: The external application ID could not be loaded from the RTC connection configuration.

Action: Ensure that the 'ext.app.id' attribute is not null and refers to a valid external application ID.
Level: 1

Type: ERROR

Impact: Other

WCS-04806: Unable to acquire associated external application details.

Cause: The external application was not found for the external application ID.

Action: Ensure that external application ID refers to a valid external application.
Level: 1

Type: ERROR

Impact: Other

WCS-04901: Not initializing RtcAction {0} as it does not extend from RtcAction

Cause: Specified class does not extend from RtcAction.

Action: Ensure that the specified class is a proper subclass of RtcAction.
Level: 1

Type: WARNING

Impact: Other

WCS-04902: Failed to initialize RtcAction {0}

Cause: Unable to instantiate the supplied RtcAction subclass.

Action: Ensure that the specified class is a proper subclass of RtcAction, and provides a default constructor.
Level: 1

Type: WARNING

Impact: Other

WCS-04903: ADFConfig does not contain rtc-config details with namespace : {0}.

Cause: The RTC actions tag 'rtcC:actions' might be missing in ADFConfig.

Action: Ensure adf-config.xml file contains rtcC:actions tag.
Level: 1

Type: WARNING

Impact: Other

WCS-04904: Cannot process call request : User Profile for user {0} not found

Cause: User has selected PSTN call method but its profile cannot be found for the user to read the contact number.

Action: Ensure that the user profile exists in the system.
Level: 1

Type: WARNING

Impact: Other

WCS-04905: Cannot process call request : Contact information for user {0} not found

Cause: User has selected PSTN call method but has not supplied the correct ldap attribute to read the contact information.

Action: Ensure that correct ldap attribute has been supplied in connection/adf-config and its value has been set in the profile.
Level: 1

Type: WARNING

Impact: Other

WCS-04906: Cannot process call request : Incorrect call method supplied

Cause: User has supplied an incorrect call method.

Action: Ensure that correct call method is supplied. Refer to the documentation to find the supported call methods.
Level: 1

Type: WARNING

Impact: Other

WCS-05001: Cannot retrieve the metadata for a group space

Cause: Unable to fetch the group space metadata due to an internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05002: An error occurred while trying to get the ScopeAPI implementation for the service {0}.

Cause: Service {0} does not support provisioning.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05003: The service object passed to the wrapper is null.

Cause: A null service object was retrieved from the service registry.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05004: A group space template named {0} already exists.

Cause: Name specified for the group space template was not unique. A template with the same name already exists.

Action: Provide a unique name for the group space template.
Level: 1

Type: ERROR

Impact: Other

WCS-05005: Cannot create group space template

Cause: No name was provided for the group space template.

Action: Provide a unique name for the group space template.
Level: 1

Type: ERROR

Impact: Other

WCS-05006: Unable to retrieve information about {0}.

Cause: No group space template was found with the name specified.

Action: Provide the name of an existing group space template.
Level: 1

Type: ERROR

Impact: Other

WCS-05007: The reference to the group space template metadata {0} is invalid.

Cause: No group space template was found with the name specified.

Action: Provide the name of an existing group space template.
Level: 1

Type: ERROR

Impact: Other

WCS-05008: Unable to get mutable metadata for the group space template {0}

Cause: Some portion of the group space template metadata has already been modified.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05009: Metadata for the group space template {0} is invalid.

Cause: MDS reported a metadata validation error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05010: An error occurred reading or writing metadata of group space template {0}.

Cause: MDS reported an IO error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05011: The commit operation failed due to a concurrent metadata change for group space template {0}.

Cause: MDS reported a concurrent metadata change error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05012: Unable to find security policy store metadata while creating group space template {0}

Cause: An error was detected in the application's configuration.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05013: Unable to execute group space related operation on {0}

Cause: Either the metadata did not exist, an invalid metadata reference was used or an attempt was made to get mutable metadata that has already been changed.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05014: Unable to get metadata for group space {0}.

Cause: Either the metadata did not exist, an invalid metadata reference was used or an attempt was made to get mutable metadata that has already been changed.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05015: Cannot create metadata for group space {0}

Cause: Metadata for the specified group space already exists.

Action: Provide a different name.
Level: 1

Type: ERROR

Impact: Other

WCS-05018: The reference to the metadata of group space {0} is invalid.

Cause: The metadata reference was invalid.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05019: Unable to get mutable metadata for the group space {0}

Cause: Some portion of the group space metadata has already been modified.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05020: Metadata of group space {0} is invalid.

Cause: MDS reported a metadata validation error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05021: An error occurred reading or writing metadata of group space {0}.

Cause: MDS reported an IO error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05022: The commit operation failed due to a concurrent metadata change for group space {0}.

Cause: MDS reported a concurrent metadata change error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05023: Cannot retrieve a list of members for the current group space.

Cause: An error occurred trying to access the specified group space.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05025: Could not create group space {0} from group space template {1}.

Cause: An internal error occurred.

Action: Contact Administrator.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05026: Cannot save group space {0} as group space template {1}

Cause: Either the specified group space template already exists or the name was invalid.

Action: Provide a valid,unique name for the group space template.
Level: 1

Type: ERROR

Impact: Other

WCS-05027: Unable to get preference metadata for the group space {0}

Cause: Either the metadata does not exist, an invalid metadata reference was used or an attempt was made to get mutable metadata that has changed.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05035: Unexpected error in renaming group space from {0} to {1}. Contact administrator or try again after some time.

Cause: An invalid character was found in the name.

Action: Remove the invalid character(s) from the name and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-05036: A group space named {0} already exists.

Cause: A group space with the specified name exists.

Action: Specify a unique name for the group space.
Level: 1

Type: ERROR

Impact: Other

WCS-05037: The group space template name contains an invalid character {0}.

Cause: An invalid character was found in the group space template name.

Action: Remove the invalid character(s) from the group space template name and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-05038: A group space template named {0} already exists.

Cause: A group space template with the specified name already exists.

Action: Specify a unique name for the group space template.
Level: 1

Type: ERROR

Impact: Other

WCS-05039: An error occurred attempting to save this group space as a group space template.

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05040: The group space name contains one or more blank space characters.

Cause: A blank space was found in the group space name.Blank spaces are not allowed.

Action: Remove all blank spaces from the group space name and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-05041: The group space template name contains one or more blank space characters.

Cause: A blank space was found in the name of the group space template. Blank spaces are not allowed.

Action: Remove all blank spaces from the group space template name and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-05042: Unable to get metadata {1} for group space {0}.

Cause: Either the metadata did not exist, an invalid metadata reference was used or an attempt was made to get mutable metadata that has already been changed.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05043: A group space with display name {0} already exists.

Cause: A group space with the specified display-name exists.

Action: Specify a unique display-name for the group space.
Level: 1

Type: ERROR

Impact: Other

WCS-05047: An error occurred attempting to invite a user to join a group space.

Cause: Connection details for the BPEL Server providing group space invitation services were not available.

Action: Ask your WebCenter administrator to configure a connection to the BPEL Server providing group space invitation services.
Level: 1

Type: ERROR

Impact: Other

WCS-05048: unexpected error while trying to invite users to group space {0}

Cause: The BPEL server that provides the group space invitation service might have been down.

Action: Ask the WebCenter administrator to restart the BPEL Server, and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-05058: Cannot create policy store metadata for group space {0}

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05059: Cannot save the changes

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05063: Cannot delete group space {0} due to unknown errors.

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05065: Cannot not get the list of available services

Cause: No services were available in the service registry.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05066: An error occurred attempting to unsubscribe a user from group space {0}.

Cause: The BPEL Server supporting group space unsubscription may be down

Action: Ask your WebCenter administrator to restart the BPEL Server and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-05067: An error occurred during unsubscription.

Cause: Connection details for the BPEL Server providing group space unsubscription services were not available.

Action: Ask your WebCenter administrator to configure a connection to the BPEL Server providing group space unsubscription services.
Level: 1

Type: ERROR

Impact: Other

WCS-05068: An error occurred attempting to unsubscribe user from group space {0}: {1}.

Cause: Connection details for the BPEL Server providing group space unsubscription services were not available.

Action: Ask your WebCenter administrator to configure a connection to the BPEL Server providing group space unsubscription services.
Level: 1

Type: ERROR

Impact: Other

WCS-05069: An error occurred during group space subscription.

Cause: The BPEL URL has not been configured yet.

Action: Notify your WebCenter administrator that the BPEL service supporting group space subscription is not configured
Level: 1

Type: ERROR

Impact: Other

WCS-05070: An error occurred attempting to subscribe a user to the group space:{0}.

Cause: The BPEL Server providing the group space subscription service may be down.

Action: Ask your WebCenter administrator to restart the BPEL Server, and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-05071: An error occurred attempting to subscribe user to the group space {0}: {1}.

Cause: The BPEL Server providing the group space subscription service may be down.

Action: Ask your WebCenter administrator to restart the BPEL Server, and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-05072: Error occurred while navigating to the group space {0}.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05073: Could not create group space with name {0}

Cause: The scope name provided couldn't be created.

Action: Please contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05074: An error occurred attempting to access a page of the renamed group space.

Cause: The group space rename operation was not successful.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05075: An error occurred attempting to rename a group space.

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05077: Cannot access the BPEL Server

Cause: An error occurred attempting to retrieve the BPEL Several URL configured in connections.xml

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05078: Cannot delete workflow approval metadata from the group space

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-05079: Cannot get the security handler for group space template {0}

Cause: The policy store metadata was not available for group space template security initialization.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05080: Cannot create the group space template {0}

Cause: The group space template was not created due to an error reported by the metadata store.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05081: Unable to retrieve metadata object for group space {0}

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05082: Adding workflow approval metadata to the group space failed

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-05083: An error occurred attempting to rename group space {0} to {1}.

Cause: The group space rename operation was successful.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05084: An unexpected error occurred attempting to delete the group space {0}.

Cause: The group space delete operation was unsuccessful.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05085: Group space name cannot be null

Cause: Group space name was blank.

Action: Enter a valid alphanumeric name for the group space
Level: 1

Type: ERROR

Impact: Other

WCS-05086: Group space name is a reserved keyword.

Cause: The group space name specified was a reserved keyword.

Action: Specify a valid alphanumeric name for the group space which excludes the following reserved keywords: webcenter, pages, page, spaces, space, group, groups, group space, group spaces, webcenter space, webcenter spaces, webcenter administration, my group spaces, admin, last.
Level: 1

Type: ERROR

Impact: Other

WCS-05087: The group space name contains invalid characters. Only alphanumeric and space characters are allowed.

Cause: Group space name contained non-alphanumeric/space characters.

Action: Specify a valid alphanumeric name for the group space that only contains a-z, A-Z, 0-9, _, or a space character
Level: 1

Type: ERROR

Impact: Other

WCS-05088: cannot delete the seeded group space template {0}

Cause: An attempt was made to delete a seeded group space template.

Action: Do not try to delete a seeded group space template.
Level: 1

Type: ERROR

Impact: Other

WCS-05089: Connection details for the BPEL Server providing group space notification services are not available. Unable to send add or delete notifications to members of group space{0}

Cause: Connection details for the BPEL Server providing group space invitation services were not available or configured incorrectly.

Action: Ask your WebCenter administrator to configure a connection to the BPEL Server providing group space notification services.
Level: 1

Type: ERROR

Impact: Other

WCS-05090: An error occurred attempting to send a notification to a member added to or deleted from group space {0}

Cause: An error occurred attempting to send a group space notification.

Action: Contact Oracle Support.
Level: 1

Type: ERROR

Impact: Other

WCS-05091: Connection details for the BPEL Server providing notification services in WebCenter Spaces not found.

Cause: Connection details for the BPEL Server providing notification services in WebCenter Spaces were not available.

Action: Ask your WebCenter administrator to configure a connection to the BPEL Server providing notification services in Webcenter Spaces
Level: 1

Type: ERROR

Impact: Other

WCS-05092: One of the arguments passed to API call {0} is null

Cause: A null argument was passed to an API call

Action: Invoke the API with non-null arguments
Level: 1

Type: ERROR

Impact: Other

WCS-05093: Group space template name cannot be null

Cause: No name was specified for the group space template.

Action: Specify a valid alphanumeric name for group space template.
Level: 1

Type: ERROR

Impact: Other

WCS-05094: Group space template name is a reserved keyword.

Cause: The template name specified was a reserved keyword.

Action: Specify a valid alphanumeric name for the template which excludes the following reserved keywords: webcenter, pages, page, spaces, space, group, groups, group space, group spaces, webcenter space, webcenter spaces, webcenter administration, my group spaces, admin, last
Level: 1

Type: ERROR

Impact: Other

WCS-05095: Template name contains invalid characters. Only alphanumeric and space characters are allowed.

Cause: Template name contains non-alphanumeric or space characters

Action: Specify a valid alphanumeric name for the template that only contains:a-z, A-Z, 0-9, _, or a space character
Level: 1

Type: ERROR

Impact: Other

WCS-05096: A template with name {0} already exists.

Cause: A template with the specified name exists.

Action: Specify a unique name.
Level: 1

Type: ERROR

Impact: Other

WCS-05097: Cannot upload group space icon

Cause: An error occurred while attempting to upload the file to WebCenter

Action: Try again or contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

WCS-05098: Cannot upload a group space logo

Cause: An error occurred attempting to upload the file to WebCenter

Action: Try again or contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

WCS-05099: Unable to set lock on group space {0}

Cause: A lock could not be acquired for this group space.

Action: Wait and try after again.
Level: 1

Type: ERROR

Impact: Other

WCS-05100: Unable to execute operation on group space {0}

Cause: Group space {0} was locked by some other operation.

Action: Wait for the first operation to complete and try again..
Level: 1

Type: ERROR

Impact: Other

WCS-05101: Unable to execute group space operation

Cause: The group space was locked by some other operation.

Action: Wait for the first operation to complete and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-05102: Errors while creating group space {0} from group space template {1}

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-05103: Errors while renaming group space {0}

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-05104: unexpected error while trying to request change membership to group space {0}

Cause: The BPEL server might have been down.

Action: Ensure BPEL server is up and retry. Contact the group space moderator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-05105: unexpected error while trying to send notification to user {0}

Cause: The BPEL server might have been down.

Action: Ensure BPEL server is up and retry. Contact the group space moderator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-05106: unexpected error creating region in cache

Cause: An attempt to create a region in the JOC (Java Object Cache) failed.

Action: Ensure that the JOC configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05107: unexpected error getting object {0} from region {1} in cache

Cause: An attempt to retrieve an object from the cache failed.

Action: Ensure that the JOC configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05108: Search {0} for group space returned more than {2} results.

Cause: Search matched {1} results for group space template. The maximum number of result records allowed for this report is {1}.

Action: Restrict your query further, or use a different query.
Level: 1

Type: ERROR

Impact: Other

WCS-05109: Group space operation resulted in unexpected exception.

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-05111: Creating template resulted in unexpected exception.

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-05112: fetching group space member count resulted in unexpected exception.

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-05113: An error occurred while trying to provision the service ''{0}''. The service did not get provisioned.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05114: An error occurred while trying to unprovision the service ''{0}''. The service did not get unprovisioned.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05115: An error occurred while trying to determine the selected service.

Cause: An unexpected error occurred.

Action: Reload the browser page, and if problem persists, contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05116: An error occurred while trying to process the service that was selected.

Cause: An unexpected error occurred.

Action: Reload the browser page, and if problem persists, contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05117: An error occurred while trying to load the configuration screen for the selected service.

Cause: An unexpected error occurred.

Action: Reload the browser page, and if problem persists, contact the administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-05118: Failed to delete the group space {0} Security metadata

Cause: Deletion of group space security metadata failed

Action: An unexpected error occurred while trying to deleting the scope {0}. Please contact administrator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-05119: An unexpected error occurred while trying to provision/unprovision services.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05120: An unexpected error occurred while trying to save the configuration for the service ''{0}''.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05121: An unexpected error occurred while trying to upload an image for group space {0}.

Cause: An unexpected error occurred during image upload.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05122: There was an error while fetching the GUID for scope ID {0}.

Cause: An unexpected error occurred while fetching the GUID for the space {0}.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05123: Metadata Not Found Exception occurred while fetching the service config metadata for a group space {0}.

Cause: An unexpected error occurred while fetching the service config metadata for group space {0}

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05124: An exception occurred while fetching the Space Manager for the group space {0}.

Cause: An unexpected error occurred while fetching the Space Manager for the group space {0}.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05125: An exception occurred while fetching the Space for the group space {0}.

Cause: An unexpected error occurred while fetching the Space for the group space {0}.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05126: An exception occurred while fetching the GUID for the group space {0}.

Cause: An unexpected error occurred while fetching the GUID the GUID for the group space {0}.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05127: An exception occurred while fetching the contacts list for group space {0}.

Cause: An unexpected error occurred fetching the contacts list for group space {0}.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05128: An exception occurred while fetching the GUID for the group space {0}.

Cause: An unexpected error occurred while fetching the GUID for the group space {0}.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05129: Error occurred while launching the delete role confirmation.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05130: Error occurred while launching add/invite members table.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05131: Error occurred while getting the message for inviting non-members.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05132: Error occurred while performing operations on roles.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05133: Error occurred while adding custom attributes name={0} and value={1}.

Cause: An unexpected error occurred while adding the custom attributes.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05134: Error occurred while deleting the name={0} custom attribute

Cause: An unexpected error occurred while deleting the custom attribute.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05135: Error occurred while editing the custom attribute name={0} and value={1}.

Cause: An unexpected error occurred while editing the custom attribute.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05136: Error occurred while fetching the custom attributes for group space {0}

Cause: An unexpected error occurred while fetching the custom attribute.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05137: No Such Attribute exists.

Cause: Unable to find the custom attributes

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05138: Unexpected error in getting the list of group spaces. You can try again later or contact Administrator.

Cause: Unexpected error in getting spaces.

Action: Please contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05139: Unexpected error in retrieving the group space {0}.

Cause: Unexpected error in retrieving the group space.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05140: Unexpected error while rolling back the service {0}

Cause: Error in rolling back the service.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05141: Unknown errors in Create Group Space. Please contact Administrator.

Cause: Post creating the group space, there were errors.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05142: Group space was created successfully but refreshing the group space list failed. You may try to refresh the group space list manually.

Cause: List refresh failed after creating group space.

Action: Manually refresh the group spaces list.
Level: 1

Type: ERROR

Impact: Other

WCS-05143: Errors were encountered in creating group space. The main error is - {0}. You may want to delete the current group space if it is visible in your lists. Contact the administrator if the problem persists.

Cause: Errors were seen in post-processing the create group space.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05144: Errors were encountered while creating the group space. The main error is - {0}. Rollback of the creation also failed. You may want to clean the current group space if it is visible in your lists. You may want to try to create the group space again later or contact the administrator.

Cause: Error in post-processing the group space.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05145: Group space was created with warnings. These are some of the warnings - {0}

Cause: Group space was created with warnings.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05146: Unexpected errors in deleting the group space. Contact Administrator.

Cause: Unexpected error in deleting the group space.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05147: Deletion of the group space resulted in errors. The main error is - {0}. You may want to try deleting the group space again later. If the error persists, contact the administrator.

Cause: Delete of the group spaces resulted in error.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05148: Deletion of group space resulted in errors. The main error is - {0}. Rollback of the deletion failed as well. You may want to try deleting the groups space again later. If the error persists, contact the administrator.

Cause: Delete of the group spaces resulted in error.

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05149: Group space was deleted successfully but refreshing the group space list failed. You may try to refresh the group space list manually.

Cause: List refresh failed after deleting group space.

Action: You can refresh the group spaces list manually.
Level: 1

Type: ERROR

Impact: Other

WCS-05150: Unexpected errors in renaming the group space. Contact Administrator.

Cause: Unknown errors in renaming the group space.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05151: Rename of the group space resulted in errors. The main error is - {0}. You may want to try to rename the group space again later. If the error persists, contact the administrator.

Cause: Rename of the group space resulted in error.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05152: Rename of the group space resulted in errors. The main error is - {0}. Rollback of renaming also failed. You may want to try to rename the group space again later or contact the administrator.

Cause: Group space was renamed but there were errors in processing.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05153: Group space was renamed successfully but refreshing the group space list failed. You may try to refresh the group space list manually.

Cause: Refreshing the list after renaming the group space failed.

Action: Manually refresh the list of group spaces.
Level: 1

Type: ERROR

Impact: Other

WCS-05154: Group space was renamed with warnings. These are some of the warnings - {0}.

Cause: Group space was renamed with warnings.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05155: Unexpected error in retrieving the group spaces list.

Cause: Unexpected error in retrieving the group spaces list.

Action: Try again after some time. If problem persist, contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05156: Unexpected error while provisioning some optional services in the group space. You may want to provision them again by going to Group Space Administration.

Cause: Unexpected error while provisioning some optional services in the group space.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05157: Provisioning some optional services in the group space didn't go through successfully. You may want to provision them again by going to Group Space Administration.

Cause: Provisioning some optional services in the group space didn't go through successfully.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05158: Unexpected error while unprovisioning the services.

Cause: Unexpected error in unprovisioning the services.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05159: Group space was deleted with warnings. These are some of the warnings - {0}.

Cause: Group space was renamed with warnings.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05160: Unexpected errors in while granting user access on new group space : {0}. Please contact Administrator.

Cause: Unexpected errors in while granting access on new group space : {0}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05161: Unexpected errors in while removing access on new group space : {0}. Please contact Administrator.

Cause: Unexpected errors in while removing access on new group space : {0}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05162: Unknown error in removing access for the group space : {0}

Cause: Unexpected errors in while removing access on group Space : {0}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05163: Unknown error in mapping access for the new group space : {0}

Cause: Unexpected errors in while mapping access on group Space : {0}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05164: Unexpected errors in provisioning services for new group Space : {0}

Cause: Unexpected errors in provisioning services for new group Space : {0}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05165: Unknown error in re-provisioning services since delete failed for group space : {0}

Cause: Unexpected errors in while re-provisioning services on group Space : {0}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05166: Unknown error while creating metadata for new template : {0}

Cause: Unexpected errors in while copying metadata from space : {0} to template {1}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05167: Unknown error in creating metadata for the new group space : {0}

Cause: Unexpected errors in while creating metadata for group Space : {0}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05168: Unknown error in renaming the group space.

Cause: Unexpected errors in renaming the group space.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05169: Unknown error in renaming services from group space {0} to the group space {1}.

Cause: Unexpected errors in renaming the services.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05170: Updates or deletes are being performed on group space {0} by another Moderator. Please try again after some time.

Cause: Group space {0} is already being deleted.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05171: Error occurred while trying to determine if service {0} is provisioned in the current group space.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05172: The role {0} does not exist and hence could not be assigned to the user {1}.

Cause: Role {0} may have already been deleted .

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05173: Error occurred while trying to modify the role for user {0}.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05174: Error occurred while accessing footer information.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05175: Group space {0} already exists.

Cause: Name specified for the group space was not unique. A group space with the same name already exists.

Action: Provide a unique name for the group space.
Level: 1

Type: ERROR

Impact: Other

WCS-05176: Group space name must contain at least one alphanumeric character

Cause: Group space name did not contain any alphanumeric characters

Action: Provide at least one alphanumeric character for group space name.
Level: 1

Type: ERROR

Impact: Other

WCS-05177: Unable to perform the operation on the selected group space(s) due to unknown errors

Cause: Selection of group space(s) failed

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05178: Failed to refresh the group spaces list due to unknown errors

Cause: Unknown error occurred while trying to refresh the group spaces list

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05179: Unable to perform the operation on the selected group space template(s) due to unavoidable errors

Cause: Selection of group space template(s) failed

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05180: An error occurred while trying to delete the group space template(s).

Cause: Selection of group space template(s) failed

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05181: Error in Create Group Space

Cause: Error occurred during group space creation

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05182: Error in closing the Create GS pop-up

Cause: Error occurred while closing the Group space Popup

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05183: Another user is modifying the settings. Please try after some time.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05184: Unable to delete selected group space(s).

Cause: Selection of group space(s) failed

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05185: Unable to export selected group space(s) due to unknown errors

Cause: Selection of group space(s) failed

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05186: Error occurred while checking existing status of the group space {0}.

Cause: An unexpected error occurred while checking existing status of the group space.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05187: Error occurred while retrieving the group space {0} creation date

Cause: An unexpected error occurred while retrieving the group space creation date.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05188: Error occurred while retrieving the group space {0} status changed date.

Cause: An unexpected error occurred while retrieving the group space status changed date.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05189: Failed to validate the name/display name

Cause: Failed to validate the name/display name

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05190: An error occurred in post-processing the invite for {0} in group space {1}. Please contact Administrator.

Cause: Unable to cleanup invited status metadata

Action: Please contact Administrator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-05191: Unexpected error occurred while saving the group space changes

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05192: Unexpected error occurred while making group space public.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05193: Unexpected error retrieving data for the spaces switcher.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05194: Group space template {0} based on group space {1} created successfully with the errors.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05195: Group space template {0} deletion failed due to concurrent operation performed on the same resource by some other user.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05196: Unable to retrieve email-id for the group space.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05197: Group space e-mail-id is not available because the mail service is not configured.

Cause: Group space e-mail id is not available because the mail service is not configured.

Action: Contact the administrator to configure the mail service.
Level: 1

Type: ERROR

Impact: Other

WCS-05198: Failed to initialize cache for group space template {0}.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05199: Failed to publish/unpublish the selected group space template {0}.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05200: Failed to update cache for group space template {0}.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05201: Unknown error occurred while processing the templates.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05202: User was added but could not be notified due to some errors.

Cause: The BPEL server may be down.

Action: Ensure BPEL server is up and retry.
Level: 1

Type: ERROR

Impact: Other

WCS-05203: Template name must contain at least one alphanumeric character

Cause: Template name did not contain any alphanumeric characters

Action: Provide at least one alphanumeric character for template name.
Level: 1

Type: ERROR

Impact: Other

WCS-05204: Group Space display name cannot be null

Cause: Group space display name was blank.

Action: Enter a valid alphanumeric name for the group space display name
Level: 1

Type: ERROR

Impact: Other

WCS-05205: Group space display name is a reserved keyword. One of: webcenter, pages, page, spaces, space, group, groups, group space, group spaces, webcenter space, webcenter spaces, webcenter administration, my group spaces, admin, last

Cause: The group space display name specified was a reserved keyword

Action: Specify a valid alphanumeric name for the group space display name which excludes the following reserved keywords: webcenter, pages, page, spaces, space, group, groups, group space, group spaces, webcenter space, webcenter spaces, webcenter administration, my group spaces, admin, last.
Level: 1

Type: ERROR

Impact: Other

WCS-05206: The group space display name contains invalid characters. Only alphanumeric and space characters are allowed.

Cause: Group space display name contained non-alphanumeric/space characters.

Action: Specify a valid alphanumeric name for the group space display name that only contains a-z, A-Z, 0-9, _, or a space character
Level: 1

Type: ERROR

Impact: Other

WCS-05207: Group space display name must contain at least one alphanumeric character

Cause: Group space display name did not contain any alphanumeric characters

Action: Provide at least one alphanumeric character for group space display name.
Level: 1

Type: ERROR

Impact: Other

WCS-05208: Select at least one Group Space to change state/status of Group Space.

Cause: No Group Space has been selected or changing the state.

Action: Select at least one Group Space.
Level: 1

Type: ERROR

Impact: Other

WCS-05209: There are no templates available for creating the Group Space(s). Create new templates or publish available templates if any to continue creating Group Space(s). If the problem persists contact system administrator

Cause: No templates available for creating Group Space.

Action: Create new templates or publish existing templates if any.
Level: 1

Type: ERROR

Impact: Other

WCS-05210: Unknown error occurred while initiating creation of a group space.

Cause: Unable to launch the Create Group Space popup.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05211: Unknown error occurred while retrieving the list of templates.

Cause: Unknown error occurred while retrieving the list of templates.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05212: User {0} not authorized to perform the operation {1}.

Cause: User {0} not authorized to perform the operation {1}.

Action: User {0} not authorized to perform the operation {1}.
Level: 1

Type: ERROR

Impact: Other

WCS-05213: Unexpected Error occurred while performing the method {0}. Contact system administrator.

Cause: Unexpected Error occurred while performing the method {0}.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05214: Unable to retrieve information about {0} as another user is modifying the {0}. Please try again after some time.

Cause: Cannot retrieve metadata for group space {0} as another user is modifying the settings. Please try after some time.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05215: User(s) added successfully, but sending notification to the user(s) failed

Cause: The BPEL server may be down.

Action: Ensure BPEL server is up and retry.
Level: 1

Type: ERROR

Impact: Other

WCS-05216: User was removed successfully, but sending notification to the user failed

Cause: The BPEL server may be down.

Action: Ensure BPEL server is up and retry.
Level: 1

Type: ERROR

Impact: Other

WCS-05217: User's role was modified successfully, but sending notification to the user failed

Cause: The BPEL server may be down.

Action: Ensure BPEL server is up and retry.
Level: 1

Type: ERROR

Impact: Other

WCS-05218: Unknown error occurred while navigating to Group Space {0}.

Cause: Unable to navigate to the Group Space.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05219: You can try accessing the group space from the ''Group Space drop-down'' or ''My Group Spaces''. If the group space is not listed, try refreshing the listing in ''My Group Spaces''. If group space is still not visible contact administrator.

Cause: You can try accessing the group space from the 'group space drop-down' or 'My Group Spaces'. If the group space is not listed, try refreshing the listing in 'My Group Spaces'.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05220: Deletion or Rename is being performed on group space {0} by another Moderator. Refresh the list of Group Spaces and try again after some time.

Cause: Group space {0} is already being deleted or renamed.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05221: An unexpected error occurred while trying to delete group space template. Try again after some time. If the problem persists, contact administrator.

Cause: An unexpected error occurred while trying to delete group space template.Contact administrator.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05222: Some optional services in the group space could not be provisioned as they were disabled. You may want to provision them again by going to Group Space Administration.

Cause: Unexpected error while provisioning some optional services in the group space.

Action: Contact Administrator and look in the logs for information about the specific service that has been disabled.
Level: 1

Type: ERROR

Impact: Other

WCS-05223: Admin Role does not exist in the policy store for scope {0}, so creating it

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-05224: Unexpected error occurred while revoking group space public status.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05974: An error occurred while creating the Group Space Template{0} based on Group Space {1}

Cause: An error occurred while creating the Group Space Template{0}

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05975: An error occurred while inviting {0} members to Group Space {1}

Cause: An error occurred while inviting the members to Group Space{1}

Action: Contact administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05976: An error occurred while fetching the roles for Group Space {0}

Cause: An error occurred while fetching the roles for Group Space{0}

Action: Contact administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05978: An error occurred when user {0} tried to reject the invite for group space {1}

Cause: Failed to execute rejection of group space invite

Action: Check the parameters being passed to the rejectInvite API or contact administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05979: An error occurred when user {0} tried to accept invite for group space {2} with role {1}

Cause: Failed to execute acceptance of group space invite

Action: Check the parameters being passed to the acceptInvite API or contact administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05980: An unexpected error occurred while instantiating group space web services client

Cause: Unable to create an instance of GroupSpaceWSClient

Action: Please verify the context parameters or contact administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05981: Deleting group space {0} failed

Cause: WebService API failed to execute deleting web service call.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05982: Creating group space {0} failed

Cause: WebService API failed to execute create web service call.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05983: An error occurred while revoking the roles {1} users in Group Space{0}

Cause: WebService API failed to execute revoke role web service call.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05984: An error occurred while granting roles for {1} users in Group Space{0}

Cause: WebService API failed to execute grant role web service call.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05985: Getting group space template {0} metadata failed

Cause: WebService API failed to execute get space template metadata web service call.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05986: Getting group space metadata {0} failed

Cause: WebService API failed to execute get space metadata web service call.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05987: Getting group spaces for search string {0} failed

Cause: WebService API failed to execute get spaces web service call.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05988: Getting group space templates for search string {0} failed

Cause: WebService API failed to execute get template web service call.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05989: Setting the Custom Attributes for scope {0} failed

Cause: WebService API failed to execute Custom Attributes.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05990: An error occurred while attempting to retrieve spaces web service endpoint configured in connections.xml of caller application

Cause: Unable to retrieve spaces web service endpoint configured in caller applications connections.xml

Action: Please check spaces web service endpoint configured in connections.xml
Level: 1

Type: ERROR

Impact: Other

WCS-05991: One of the arguments passed to API call {0} is null

Cause: A null argument was passed to an API call

Action: Ensure to invoke the API with non-null arguments
Level: 1

Type: ERROR

Impact: Other

WCS-05992: No group space name is provided

Cause: Group space name is not provided

Action: Ensure to invoke the API with non-null arguments
Level: 1

Type: ERROR

Impact: Other

WCS-05993: No group space template name is provided

Cause: Group space template name is not provided

Action: Ensure to invoke the API with non-null arguments
Level: 1

Type: ERROR

Impact: Other

WCS-05994: No group space user name is provided

Cause: Group space user name is not provided

Action: Ensure to invoke the API with non-null arguments
Level: 1

Type: ERROR

Impact: Other

WCS-05995: No group space role name is provided

Cause: Group space role name is not provided

Action: Ensure to invoke the API with non-null arguments
Level: 1

Type: ERROR

Impact: Other

WCS-05996: No group space custom attribute Name is provided

Cause: Group space custom attribute name is not provided

Action: Ensure to invoke the API with non-null arguments
Level: 1

Type: ERROR

Impact: Other

WCS-05997: No group space custom attribute value is provided

Cause: Group space custom attribute value is not provided

Action: Ensure to invoke the API with non-null arguments
Level: 1

Type: ERROR

Impact: Other

WCS-05998: Error while setting the new end point for the group space web services

Cause: Group space web services client already has an endpoint {0}

Action: It cannot be overridden at the run-time. Try setting it in connections.xml and restarting the application
Level: 1

Type: ERROR

Impact: Other

WCS-05999: Spaces Web Service context is NULL

Cause: Group space web service client is null

Action: You need to set the context for the client and then initialize it
Level: 1

Type: ERROR

Impact: Other

WCS-06001: JCR session leak: leaked {0} sessions during {1} request to URI {2}.

Cause: JCR sessions have not been returned to the pool after the request ended.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-06002: Connection "{0}" is not a content repository connection.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-06905: Credentials for connection {0} not found using External Application Identifier {1}.

Cause: An attempt to fetch user credentials failed. User credentials may not have been provisioned or the external application configuration may be incorrect.

Action: Verify the external application configuration. If necessary, provision credentials for the user.
Level: 1

Type: WARNING

Impact: Other

WCS-06906: invalid credentials for connection {0} using External Application Identifier {1}

Cause: An attempt to log in using the provisioned credentials failed. The user's credentials for this connection might have been changed or the external application configuration might have been incorrect.

Action: If the provisioned credentials for the given user are not valid, then those credentials must be provisioned again. It might also be necessary to verify the external application configuration.
Level: 1

Type: WARNING

Impact: Other

WCS-06908: JCR Repository creation failure

Cause: A JCR repository instance could not be created from the parameters provided.

Action: Check the configuration parameters, and retry.
Level: 1

Type: WARNING

Impact: Other

WCS-06910: External Application Definition not found using External Application Identifier {0}

Cause: An attempt to fetch user credentials failed. The External Application ID is incorrect.

Action: Verify that the External Application definition has been created for this connection.
Level: 1

Type: WARNING

Impact: Other

WCS-06911: There is no authenticated user and PUBLIC credentials are not supported for External Application ID {0}.

Cause: An attempt to fetch credentials failed because there is not currently an authenticated user and the External Application ID does not support PUBLIC credentials.

Action: Use an External Application ID that supports PUBLIC credentials or authenticate so that no attempt to use PUBLIC credentials will occur.
Level: 1

Type: WARNING

Impact: Other

WCS-06912: There is no authenticated user and the PUBLIC credentials provisioned for External Application ID {0} are not valid.

Cause: An attempt to login using PUBLIC credentials failed because the provisioned PUBLIC credentials are not valid.

Action: Contact your system administrator and inform them that the PUBLIC credentials need to be updated or authenticate so that no attempt to utilize the PUBLIC credentials will occur.
Level: 1

Type: WARNING

Impact: Other

WCS-06913: The SHARED credentials provisioned for External Application ID {0} are not valid.

Cause: An attempt to login using SHARED credentials failed because the provisioned SHARED credentials are not valid.

Action: Contact your system administrator and inform them that the SHARED credentials need to be updated.
Level: 1

Type: WARNING

Impact: Other

WCS-07001: severe internal error

Cause: An irrecoverable internal error has occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-07002: error obtaining Documents service ADF configuration

Cause: An error occurred while obtaining or interpreting the DocLib section of ADF configuration.

Action: Verify that the Documents service section of the ADF configuration is present, complete, and contains valid data.
Level: 1

Type: WARNING

Impact: Other

WCS-07003: error obtaining content repository connection

Cause: A JNDI Naming Exception occurred while attempting to obtain the content repository connection.

Action: Verify that connections.xml contains a valid entry for the content repository connection.
Level: 1

Type: WARNING

Impact: Other

WCS-07004: content repository login failure

Cause: The attempt to log on to the content repository failed.

Action: Make sure the credentials used are valid.
Level: 1

Type: WARNING

Impact: Other

WCS-07005: JCR error connecting to content repository

Cause: A JCR repository exception (other than login) occurred.

Action: Use the associated JCR exception text to diagnose the problem.
Level: 1

Type: WARNING

Impact: Other

WCS-07006: run-time error obtaining content repository

Cause: An unexpected run-time exception occurred.

Action: Use the associated run-time exception text to diagnose the problem.
Level: 1

Type: WARNING

Impact: Other

WCS-07007: cannot list items in directory {0}

Cause: An error occurred while trying to list the items in the specified folder.

Action: Make sure that the content repository connection is accessible and that the specified folder exists.
Level: 1

Type: WARNING

Impact: Other

WCS-07008: cannot get breadcrumbs for directory {0}

Cause: An error occurred while trying to list the breadcrumbs items for the specified folder.

Action: Make sure that the content repository connection is accessible and that the specified folder exists.
Level: 1

Type: WARNING

Impact: Other

WCS-07010: error listing folder {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07011: The Rich Text Editor could not load the target document, it may have been deleted.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07012: The Rich Text Editor could not load the destination folder, it may have been deleted.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07013: No content repository connection with the name "{0}" can be found.

Cause: A JNDI Name Not Found Exception occurred while attempting to obtain the content repository connection.

Action: Verify connections.xml contains an entry for the specified content repository connection name.
Level: 1

Type: WARNING

Impact: Other

WCS-07014: An attempt to log on to the content repository did not complete within the allotted time.

Cause: The content repository may have been slowed by heavy loads or network congestion.

Action: Wait a while, and then retry. Optionally, ask the system administrator to allocate more resources for the content repository or to lengthen the timeout period.
Level: 1

Type: WARNING

Impact: Other

WCS-07015: An attempt to log on to the content repository did not succeed because the Documents service is disabled.

Cause: Login failed because the Documents service was disabled. Another login was still executing, exceeding its allotted timeout period.

Action: Wait a while, and then retry. Optionally, ask the system administrator to allocate more resources for the content repository or to lengthen the timeout period.
Level: 1

Type: WARNING

Impact: Other

WCS-07016: Cannot get the user name for the selected user.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07017: The target Content Server does not support the following query used to retrieve recent documents: {0}.

Cause: Required components may not have been installed or properly configured.

Action: Check the Content Server installation guide for WebCenter for details on required components and their configuration.
Level: 1

Type: ERROR

Impact: Other

WCS-07018: An error occurred while trying to convert the following object from {0} to {1}: {2}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07019: Cannot create folder "{0}" in "{1}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07020: Error refreshing the JCR session.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07021: The transferable object contains no usable data.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07022: After fail-over, failed to get the item {0} from the repository.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07023: Click the Refresh icon to see the latest content.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07024: Click the Refresh icon to see the latest content. You may need to navigate up the folder hierarchy before refreshing.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07025: Unable to rename the selected document.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07026: Unable to perform the operation. The document or folder may have been deleted or you do not have permission.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07027: An error occurred performing post operation refreshing. The current document or folder may have been deleted or you do not have permission.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07028: The folder being renamed no longer exists.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07029: Unable to checkout {0}. This document is already checked out.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07030: Unable to perform the current operation.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07031: Unable to delete selected documents or folders.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07032: Unable to rename the selected folder.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07033: Unable to create folder.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07034: Unable to display folder properties.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07035: Unable to create new HTML document.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07036: Unable to upload the document.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07037: Unable to edit the HTML document.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07038: Unable to display document properties.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07039: Unable to display folder properties.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07040: Unable to save folder properties.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07041: Unable to check in the document.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07042: Unable to check out the document.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07043: Unable to cancel the document check-out.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07044: Unable to view version history for the document.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07045: Unable to copy selected documents or folders.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07046: Unable to paste selected documents or folders.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07047: A document or folder with the same name exists in this folder.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07048: A document or folder with the same name exists in this folder.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07049: You do not have permission.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07050: The folder no longer exists.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07051: The selected documents or folders no longer exist.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07052: The document no longer exists.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07053: The parent folder no longer exists.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07054: The document or folder being copied/moved no longer exists or the target folder no longer exists.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07055: The parent folder is currently unavailable.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07056: One or more of the selected documents or folders no longer exists.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07057: The document being renamed no longer exists.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07058: The document or folder no longer exists.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07059: The maximum number of folders stored within a folder has been reached. Contact your systems administrator.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07060: The maximum number of documents stored within a folder has been reached. Contact your systems administrator.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07061: The document is checked out by another user.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07062: The document is checked out by another user.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07063: The document is not checked out.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07064: An unknown error occurred in the Oracle Content Server.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07065: The selected document or folder or its parent folder may have been deleted or your permissions may have been revoked.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07066: Unable to move selected documents or folders.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07067: A document or folder with the same name exists in this folder.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07068: A document or folder with the same name exists in this folder.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07069: The folder name contains an invalid character.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07070: The folder name is too long.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07071: Unable to save document properties.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07072: The destination cannot be a child folder of the source folder.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07201: Oracle Content Server error: {0}

Cause: An unexpected error occurred in the Oracle Content Server.

Action: Check the Oracle Content Server logs for details on this exception.
Level: 1

Type: WARNING

Impact: Other

WCS-07301: Repository error: {0}

Cause: An unexpected error occurred in the content repository.

Action: Check the base exception and repository's log for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-07302: Repository error

Cause: An unexpected error occurred in the content repository.

Action: Check the base exception and repository's log for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-07303: Unsupported repository operation

Cause: The Documents service tried to invoke an operation that is not supported by the underlying document repository.

Action: Avoid this operation with this repository.
Level: 1

Type: WARNING

Impact: Other

WCS-07304: Access Denied

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07305: Versioning is not supported on this repository.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07306: Locking is not supported on this repository.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07307: The recent documents query is not supported on this repository.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07401: Unexpected exception: {0}

Cause: An unexpected exception occurred.

Action: Check the server logs for details on this exception.
Level: 1

Type: WARNING

Impact: Other

WCS-07402: Unexpected error

Cause: An unexpected error occurred.

Action: Check the server logs for details on this error.
Level: 1

Type: ERROR

Impact: Other

WCS-07403: Unsupported resource type

Cause: The Documents service tried to perform an operation on a resource but failed to do so because the resource type was not recognized.

Action: Avoid this operation with this particular type of resource.
Level: 1

Type: WARNING

Impact: Other

WCS-07404: Renaming the root folder is not allowed.

Cause: An attempt was made to rename the root folder.

Action: Avoid the rename operation with the root folder.
Level: 1

Type: WARNING

Impact: Other

WCS-07405: Error reading the document's content.

Cause: The document's content could not be accessed.

Action: Verify that the document is available.
Level: 1

Type: WARNING

Impact: Other

WCS-07406: Error performing paste.

Cause: An error prevented the items from being pasted at the destination folder.

Action: Verify that the destination folder still exists, is writable, and no items with the same names exist there.
Level: 1

Type: ERROR

Impact: Other

WCS-07407: When searching between dates, if the dates are not specified in ascending order, the search may not return any results.

Cause: The begin and end dates have been specified in the wrong order.

Action: Specify the dates in ascending order.
Level: 1

Type: WARNING

Impact: Other

WCS-07408: Operation not allowed on Public folders.

Cause: An attempt has been made to perform an illegal operation on a Public folder.

Action: Do not select a Public folder wen performing operations such as delete and rename. If performing a copy or move operation then select item(s) inside the Public folder, not the Public folder itself.
Level: 1

Type: ERROR

Impact: Other

WCS-07501: There is no role matching the given ID: {0}.

Cause: The application attempted to look up a service role with an invalid role ID.

Action: Ensure that your application uses a valid service role ID.
Level: 1

Type: ERROR

Impact: Other

WCS-07502: Cannot grant role {0} for scope {1}.

Cause: Could not grant the super administrator role to the scope. The super administrator role can only be granted to the default scope; other roles must be granted on a group space scope.

Action: Verify that the role mapping is correctly defined.
Level: 1

Type: ERROR

Impact: Other

WCS-07503: Cannot log on to the content repository.

Cause: The username and password used for the current login were not correct.

Action: Check the username and password.
Level: 1

Type: WARNING

Impact: Other

WCS-07504: There was an unknown content repository exception.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07505: The repository login was interrupted.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07801: Cannot seed the WebCenter data into the content repository.

Cause: An error occurred while seeding data for the Documents service in the content repository.

Action: Check the underlying exception and content repository log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07802: Cannot find the adf-config.xml file.

Cause: Could not find an adf-config.xml document in the classpath.

Action: To enable the Documents service in WebCenter, ensure adf-config.xml and connections.xml containing Documents service information are on the classpath.
Level: 1

Type: ERROR

Impact: Other

WCS-07803: Cannot open a connection to the Oracle Content Server.

Cause: The application failed to open a connection to the Oracle Content Server.

Action: Check that the Oracle Content Server connection is properly configured and that the server is available.
Level: 1

Type: ERROR

Impact: Other

WCS-07804: Cannot create the Security Group, {0}, in the Oracle Content Server.

Cause: A Content Server error occurred while executing the operation.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07805: Cannot create the seeded role, {0}, in the Oracle Content Server.

Cause: A Content Server error occurred while executing the operation.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07806: Cannot create the folder, {0}, in the folder, {1}, in the Oracle Content Server.

Cause: A Content Server error occurred while executing the operation.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07807: Cannot rename the folder, {0}, to {1}, in the Oracle Content Server.

Cause: A Content Server error occurred while executing the operation.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07808: Cannot delete the folder, {0}, in the Oracle Content Server.

Cause: A Content Server error occurred while executing the operation.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07809: Cannot get folder with the path, {0}, from the Oracle Content Server.

Cause: A Content Server error occurred while executing the operation.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07810: Error obtaining the content repository connection "{0}".

Cause: A JNDI Naming Exception occurred while attempting to obtain the content repository connection.

Action: Verify that connections.xml contains a valid content repository connection.
Level: 1

Type: ERROR

Impact: Other

WCS-07811: Unsupported repository connection "{0}" for the Documents service.

Cause: The specified content repository is not currently supported for Documents service WebCenter Spaces integration. The supported content repository types is Oracle Content Server.

Action: Verify that adf-config.xml and connections.xml contain a valid entry for the Documents service repository.
Level: 1

Type: ERROR

Impact: Other

WCS-07812: Cannot remove permissions, {0}, for user, {1}, to the account for the folder, {2}.

Cause: The application failed to remove permissions for the user on the folder.

Action: Check that the permissions and user are valid and that the folder exists.
Level: 1

Type: ERROR

Impact: Other

WCS-07813: Cannot grant permissions, {0}, for user, {1}, to the account for the folder, {2}.

Cause: The application failed to grant permissions for the user on the folder.

Action: Check that the permissions and user are valid and that the folder exists.
Level: 1

Type: ERROR

Impact: Other

WCS-07814: Error while removing an account from all users credentials.

Cause: A Content Server error occurred while executing the operation.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07816: Unable to seed the WebCenter data in the Oracle Content Server repository.

Cause: A Content Server error occurred while seeding the WebCenter data in the repository.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07817: Unable to seed the Personal Folder data in the Oracle Content Server repository.

Cause: A Content Server error occurred while seeding the Personal Folder data in the repository.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07818: Cannot find the WebCenter administrators to seed in the Document Library repository.

Cause: The application failed to determine the list of WebCenter administrators.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07819: Cannot release the session pool.

Cause: Failed to release the session pool for the content repository administrative connection.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07820: Cannot create a search result row from the JCR node.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07821: Error while calling the EC_SET_PROPERTY service with dECPropType = {0}, dECPropKey = {1}, dECPropSubKey = {2}, dECPropValue = {3}.

Cause: A call to the Oracle Content Server EC_SET_PROPERTY service during repository setup failed to complete.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07822: Cannot get the WebCenter URL.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07823: Cannot grant the account, {0}, to all users.

Cause: An error occurred while trying to grant the account to all users.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07824: Unable to get the admin session to the Oracle Content Server repository.

Cause: An error occurred while trying to obtain an admin sesion to the Oracle Content Server repository.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07825: Cannot remove role, {0}, for user, {1}.

Cause: The application failed to remove the specified role from the user.

Action: Check the role and user are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-07826: Cannot remove role {0} and permissions, {1}, to the account for the folder, {2} for the user {3}.

Cause: The application failed to remove the role and permissions on the folder for the user.

Action: Check that the permissions and user are valid and that the folder exists.
Level: 1

Type: ERROR

Impact: Other

WCS-07827: Cannot add role, {0}, for user, {1}.

Cause: The application failed to add the specified role to the user.

Action: Check the role and user are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-07828: Cannot add role {0} and permissions, {1}, to the account for the folder, {2} for the user {3}.

Cause: The application failed to add the role and permissions on the folder for the user.

Action: Check that the permissions and user are valid and that the folder exists.
Level: 1

Type: ERROR

Impact: Other

WCS-07829: Cannot update the account for the group space {0}, with permission, {1}, for all users.

Cause: An error occurred while trying to update the group space account for all users.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07830: Cannot set default attributes, {0}, for the key, {1}

Cause: An error occurred while trying to set default attributes for the specified key.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07831: Cannot delete default attributes for the key, {0}.

Cause: An error occurred while trying to delete default attributes for the specified key.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07832: Cannot determine account and permission from the default attributes for the group space, {0}.

Cause: An error occurred while trying to determine the account and permission from the default attributes for the group space. The default attributes are not in the correct format.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07833: The Java Object Cache is not available.

Cause: An error occurred while trying to retrieve the cache.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07834: A Java Object Cache operation timed out. Distributed caches may be inconsistent.

Cause: A cache operation timed out.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07835: Java Object Cache, Put operation failed.

Cause: A cache put operation failed.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07836: Java Object Cache, Destroy operation failed.

Cause: A cache destroy operation failed.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07837: Java Object Cache, Get operation failed.

Cause: A cache get operation failed.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07838: Java Object Cache, release ownership failed.

Cause: A cache unlock operation on a cached object failed.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-08001: Supplied class {0} is not an instance of {1}.

Cause: Forum service adapter details were not configured properly in the adf-config.xml file or the adapter implementation class was not correct.

Action: Check that the adapter class name in the adf-config file is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-08002: Not able to invoke constructor of class {0} through Constructor.newInstance() call.

Cause: Application tried to instantiate a class through Constructor.newInstance().

Action: Check that the adapter class name in the adf-config file is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-08003: Not able to find the method "{0}" in the class "{1}".

Cause: Matching constructor was not found in the adapter implementation class.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-08004: Not able to resolve the name {0}

Cause: Not able to acquire Context to look up.

Action: Check for JNDI configuration.
Level: 1

Type: ERROR

Impact: Other

WCS-08005: User "{0}" is not authorized.

Cause: Contact your administrator for access to discussions forum.

Action: Provide valid user credentials, or check if user exists or has appropriate permissions.
Level: 1

Type: WARNING

Impact: Other

WCS-08006: User "{0}" not logged on.

Cause: User might not have logged on to the system.

Action: Try logging on using correct user credentials.
Level: 1

Type: WARNING

Impact: Other

WCS-08007: User "{0}" not found

Cause: User might not have been created, or user might have been deleted from the back-end application.

Action: Contact your administrator or try different user credentials.
Level: 1

Type: ERROR

Impact: Other

WCS-08008: Service "{0}" is not a valid service or it is not supported by the "{1}" adapter implementation.

Cause: Adapter implementation does not recognize this service type.

Action: Read the documentation for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-08009: Discussion forum Category with name "{0}" already exists.

Cause: Category with the given name already exists.

Action: Try with a different category name.
Level: 1

Type: WARNING

Impact: Other

WCS-08010: Category not found.

Cause: Category does not exists or user is not authorized to access it.

Action: Provide a valid category ID.
Level: 1

Type: WARNING

Impact: Other

WCS-08011: Discussion forum object Forum with name "{0}" already exists.

Cause: Discussion forum object Forum with the given name already exists.

Action: Try with a different forum name.
Level: 1

Type: WARNING

Impact: Other

WCS-08012: No forums were found.

Cause: Forum does not exists or user is not authorized to access it.

Action: Provide a valid forum ID.
Level: 1

Type: WARNING

Impact: Other

WCS-08013: Topic not found.

Cause: Topic does not exists or user is not authorized to access it.

Action: Provide a valid topic ID.
Level: 1

Type: WARNING

Impact: Other

WCS-08014: Message not found.

Cause: Message does not exists or user is not authorized to access it.

Action: Provide a valid message ID.
Level: 1

Type: WARNING

Impact: Other

WCS-08015: There is a problem with the supplied attachments.

Cause: Possible causes: attachment was larger than expected, it was not readable or available, or it was not a supported mime type.

Action: Try with a different attachment or contact your system administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-08016: Unable to look up the forum connection with name "{0}".

Cause: Either the forum connection name is not valid or corresponding connection details are deleted from the connection store.

Action: Check the default connection name in adf-config and connection details in connection store for discussion forum service or contact your system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-08017: Ambiguous forum connection definitions found in the connection store.

Cause: More than 1 connection type found for discussion forum service. Unable to decide which one to use.

Action: Configure the appropriate connection name as the default connection to use from the management console or contact your system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-08018: Discussion forum object Message with subject "{0}" is prevented from being posted.

Cause: Discussion forum object Message is rejected because of any one of the following reasons: 1) blocking a set of users from posting, 2) preventing a user from posting more than once every X seconds, 3) rejecting any messages that contain profanity from the back-end application.

Action: If you are authorized to post messages and your text has valid language, then try again after some time.
Level: 1

Type: WARNING

Impact: Other

WCS-08019: Host address "{0}" configured in connection store is not correct.

Cause: IP address of the host configured in connection store could not be determined.

Action: Configure the correct host name in connection store or contact your system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-08020: Unable to connect to discussion server.

Cause: Possible reasons: The IP address of the host configured in the connection store could not be determined, or the connection was refused by the host.

Action: Configure the correct host name in connection store or contact your system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-08021: Forum connection details are not available in the connection store.

Cause: Forum connection details were not available in the connection store.

Action: Configure discussion forum service connection details in connection store or contact your system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-08022: Unable to create discussion forum object Forum with name "{0}".

Cause: Unable to create discussion forum object Forum with the supplied name and description.

Action: Contact your administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-08023: Not able to reach service endpoint port type due to {0}.

Cause: Service end point is not reachable.

Action: Contact your administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-08024: Input parameter value "{0}" supplied is invalid.

Cause: Invalid input parameter value is supplied.

Action: Provide valid values for the input parameters.
Level: 1

Type: ERROR

Impact: Other

WCS-08025: You do not have permission to see forums for this group space.

Cause: User is not authorized to access the forum.

Action: Contact your administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-08026: You do not have permission to see recent topics for this group space.

Cause: User is not authorized to access the recent topics.

Action: Contact your administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-08027: You do not have permission to see popular topics for this group space.

Cause: User is not authorized to access the popular topics.

Action: Contact your administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-08201: Not able to create forum configuration file for community "{0}" due to : {1}.

Cause: Possible failure creating the category or forum, or an issue with the MDS write operation.

Action: Contact your system administrator or read the discussion forum service configuration documentation for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-08202: Failed to flush changes into preference store due to {0}.

Cause: Possible failure in the backing store, or a failure to contact the backing store.

Action: Contact system administrator
Level: 1

Type: ERROR

Impact: Other

WCS-09001: The IMAP host cannot be null or an empty string.

Cause: The IMAP server host address was not specified.

Action: Configure Mail Service connection.
Level: 1

Type: ERROR

Impact: Other

WCS-09002: The SMTP host cannot be null or an empty string.

Cause: The SMTP server host address was not specified.

Action: Configure Mail Service connection.
Level: 1

Type: WARNING

Impact: Other

WCS-09003: Anonymous user access is not permitted on the mail service. Users must log on to the application.

Cause: User was not logged on to the application. ADF security context was not set to authenticated user.

Action: Log on to the application using the ADF authentication mechanism.
Level: 1

Type: WARNING

Impact: Other

WCS-09004: User credentials not found in the credential store for user "{0}" with external application ID: {1}.

Cause: Mapped user credentials for the current logged on user were not found in the credential store.

Action: Supply valid credentials.
Level: 1

Type: WARNING

Impact: Other

WCS-09005: Multiple connection definitions found for mail service.

Cause: Multiple connection definitions were defined in the registry; could not identify the default connection to use.

Action: Specify the default connection to be used in adf-config.xml. For more details, refer to the Mail Service documentation for creating connections.
Level: 1

Type: WARNING

Impact: Other

WCS-09006: Lookup for connection "{0}" failed.

Cause: Failed to get the JNDI context, or the mail connection with the given name was not available.

Action: Supply proper connection name, and ensure that the entry exists in the connection repository.
Level: 1

Type: ERROR

Impact: Other

WCS-09007: ADF connections context could not be acquired. Failed to find mail connection.

Cause: Failed to get the JNDI context for the connection repository.

Action: ADF connection context details were missing from the adf-config.xml file. For more information, refer to the ADF Developer's Guide.
Level: 1

Type: ERROR

Impact: Other

WCS-09008: Failed to create mail session due to: {0}

Cause: Unexpected failure: either the IMAP/SMTP server did not respond, it failed to understand the request, or it was not configured properly.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-09009: Failed to connect to the mail server. Connection timed out.

Cause: Could not connect to the mail server in the given time.

Action: Confirm that the IMAP/SMTP servers are running or increase the timeout value.
Level: 1

Type: WARNING

Impact: Other

WCS-09010: Failed to read messages from the folder "{0}". Further information: {1}

Cause: Either the IMAP folder had issues or the search term was not supported by the server.

Action: Contact your system administrator to check the issues in the log file.
Level: 1

Type: WARNING

Impact: Other

WCS-09011: Failed to get message with ID "{0}" from the folder "{1}". Further information: {2}.

Cause: Either the IMAP folder had issues or the search term was not supported by the server.

Action: Contact your system administrator to check the issues in the log file.
Level: 1

Type: WARNING

Impact: Other

WCS-09012: Failed to send the message with subject "{0}". Further information: {1}

Cause: Either the SMTP server did not respond or the message was corrupted.

Action: Contact your system administrator to check the issues in the log file.
Level: 1

Type: ERROR

Impact: Other

WCS-09013: Message with ID "{0}" has been permanently removed from the "{1}" folder.

Cause: Either this message did not exist on the IMAP folder or it was been deleted via expunge on the folder.

Action: The IMAP folder has been expunged to permanently delete all messages. The message cannot be recovered.
Level: 1

Type: WARNING

Impact: Other

WCS-09014: Unable to find the "{0}" folder.

Cause: Either the folder with this name did not exist on the IMAP server or the mail server did not support folders.

Action: Ensure that the folder with the given name exists and that the IMAP server is properly configured.
Level: 1

Type: WARNING

Impact: Other

WCS-09015: Failed to perform the {0} operation due to: {1}.

Cause: Either the mail server was down or it did not support this operation.

Action: Ensure that the IMAP and SMTP servers are properly configured and available.
Level: 1

Type: ERROR

Impact: Other

WCS-09016: Logon failed: unknown user name or incorrect password

Cause: The user credentials acquired from the credential store were incorrect.

Action: Ensure that the user credentials supplied for logon are correct.
Level: 1

Type: WARNING

Impact: Other

WCS-09017: Could not make an attachment: not a valid body part for creating an attachment.

Cause: Either the body part was not recognized, it could not be attached to the message, or the body part could not be processed.

Action: Contact your system Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-09018: No recipients for the mail specified.

Cause: No recipients for the mail specified.

Action: At least one recipient must be specified for the mail to be delivered.
Level: 1

Type: ERROR

Impact: Other

WCS-09019: No mail connection found.

Cause: No mail connection was specified.

Action: The mail connection is not available in the connection repository. Ensure that a connection to the mail server is defined.
Level: 1

Type: ERROR

Impact: Other

WCS-09020: Connection to the server failed.

Cause: Connection to the server failed: either the host or port information was wrong or the server was down.

Action: Check the mail server connection details and ensure that the mail server is up and running.
Level: 1

Type: ERROR

Impact: Other

WCS-09021: User name to connect to the mail server for Email Gateway is not supplied.

Cause: Connection to the server failed: mail user account was not complete.

Action: User account details are required to connect to the mail server.
Level: 1

Type: ERROR

Impact: Other

WCS-09022: User password to connect to the mail server for Email Gateway is not supplied.

Cause: Connection to the server failed: mail user account is not complete.

Action: User account details are required to connect to the mail server.
Level: 1

Type: ERROR

Impact: Other

WCS-09023: Cannot attach file. Either the file exceeds the maximum allowed file size or it is empty(zero bytes). Attached files must be less than 2 MB.

Cause: Either the attachment size is 0(zero) or greater than 2 MB.

Action: Attach a file within in the expected size limit.
Level: 1

Type: ERROR

Impact: Other

WCS-09025: Message delivery failure: The message could not be sent because connecting to the SMTP mail server failed. The server may be unavailable. If the problem persists, report the error to your administrator.

Cause: Connection to the server failed: either the host or port information was wrong or the server was down.

Action: Check the mail server connection details and ensure that the mail server is up and running.
Level: 1

Type: ERROR

Impact: Other

WCS-09026: Error processing the message.

Cause: The message might have been sent with improper encoding.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-09201: Distribution list "{0}" already exists.

Cause: A distribution list with the supplied name already exists.

Action: Create the distribution list with a different name.
Level: 1

Type: ERROR

Impact: Other

WCS-09202: Distribution list "{0}" is not available.

Cause: A distribution list with the supplied name does not exist.

Action: Verify the supplied name and ensure that the list exists on the mail server.
Level: 1

Type: ERROR

Impact: Other

WCS-09203: Mandatory connection property "{0}" missing from the directory connection.

Cause: The mandatory connection property required to establish directory connection was not supplied.

Action: Verify the supplied directory connection details, and ensure that the required details are supplied.
Level: 1

Type: ERROR

Impact: Other

WCS-09204: Filter criteria not defined for the directory search: {0}.

Cause: Filter criteria was not defined for the directory search.

Action: Search criteria should contain filter details.
Level: 1

Type: ERROR

Impact: Other

WCS-09205: Incorrect format for the schema attribute. Value retrieved is: {0}.

Cause: The schema was not specified properly.

Action: Check the base DN for the schema details and supply the complete base DN.
Level: 1

Type: ERROR

Impact: Other

WCS-09214: Failed to acquire the initial directory context for name: {0}, due to : {1}

Cause: Failed to acquire the connection either the connection details are wrong or server is not reachable.

Action: Ensure proper configuration is provided or Contact your administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-09215: Unable to create the distribution list: {0}, Mandatory attributes missing. Further information: {1}

Cause: Mandatory attributes to create a group are missing.

Action: Contact System Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-09216: Unexpected error occurred. Further info: {0}

Cause: Unexpected error occurred contact system administrator.

Action: Contact Oracle Support
Level: 1

Type: ERROR

Impact: Other

WCS-09217: Unable to lookup the context name: {0}, due to : {1}

Cause: Unable to find the context.

Action: Contact System Administrator
Level: 1

Type: WARNING

Impact: Other

WCS-09218: Unable to destroy the context name: {0}, due to : {1}

Cause: Either context does not exists or its not a proper context name.

Action: Contact System Administrator
Level: 1

Type: WARNING

Impact: Other

WCS-09219: Unable to modify attributes for the context name: {0}, due to : {1}

Cause: Either context does not exists or its not a proper context name.

Action: Contact System Administrator
Level: 1

Type: WARNING

Impact: Other

WCS-09220: Unable to find the attribute: {0} under context {1}, due to {2}

Cause: Required attribute not found in the context object.

Action: Ensure the required attribute is available in the context object.
Level: 1

Type: WARNING

Impact: Other

WCS-09251: Failed to make attachment, due to: {0}.

Cause: Either the file size was too large or the selected file was not readable. Check the server settings.

Action: Ensure that the file is available and readable. Also ensure that the file is not too large. If the problem persists, then contact your system administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-09252: Failed to remove attachment due to: {0}.

Cause: Either this attachment did not exist or it failed to read the message. See the error log for more details.

Action: Contact your system administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-09253: Failed to send message, due to: {0}.

Cause: Either the mail session was expired or the user was not logged in.

Action: Contact your system Administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-09254: Failed to read attachments, due to: {0}.

Cause: Either the mail session is expired or the user is not logged-in.

Action: Contact your system Administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-09255: External application ID not defined.

Cause: The required configuration parameter External Application ID was not found.

Action: Contact your system Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-09256: This message has been deleted.

Cause: This message had been deleted.

Action: Only non-deleted mails can be viewed.
Level: 1

Type: WARNING

Impact: Other

WCS-09257: No compose message object found.

Cause: User may not be in the compose mode or the state is lost.

Action: Ensure the user is in compose message view.
Level: 1

Type: WARNING

Impact: Other

WCS-09258: Unable to find the attachment table component.

Cause: Unable to find the table component in the current view.

Action: Ensure the table component id name is not changed.
Level: 1

Type: WARNING

Impact: Other

WCS-09259: Unable to find the backing bean by name {0}.

Cause: Either the backing bean is removed or the name is changed.

Action: Ensure the backing bean names are intact.
Level: 1

Type: WARNING

Impact: Other

WCS-09501: An unexpected error occurred.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-09502: Supplied class {0} is not an instance of {1}.

Cause: Announcement service adapter details might not have been configured properly in the adf-config.xml file or adapter implementation class was not proper.

Action: Check that the adapter class name in the adf-config file is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-09503: Not able to invoke constructor of class {0} through Constructor.newInstance() call.

Cause: Application is trying to instantiate a class through Constructor.newInstance().

Action: Check that the adapter class name in the adf-config file is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-09504: Not able to find the method "{0}" in the class "{1}".

Cause: Matching constructor might not be found the adapter implementation class.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-09505: User "{0}" is not authorized.

Cause: Contact your administrator for access to announcements.

Action: Provide valid user credentials, or check if user exists or has appropriate permissions.
Level: 1

Type: WARNING

Impact: Other

WCS-09506: User "{0}" not logged on.

Cause: User might not have logged on to the system.

Action: Try logging on using correct user credentials.
Level: 1

Type: WARNING

Impact: Other

WCS-09507: User "{0}" is not found.

Cause: User might not have been created, or user might have been deleted from the back-end application.

Action: Contact your administrator or try different user credentials.
Level: 1

Type: WARNING

Impact: Other

WCS-09508: Announcement configuration file for community "{0}" not found or details such as category ID and announcement ID are not available.

Cause: There was a failure in creating the announcement configuration or an issue with the MDS read or write operation.

Action: Contact your system administrator or read the announcement service configuration documentation for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-09509: Announcement not found.

Cause: Announcement object with the supplied announcement ID was not available or it was not accessible.

Action: Provide a valid announcement ID.
Level: 1

Type: WARNING

Impact: Other

WCS-09510: Announcement parent not found.

Cause: Announcement parent object with the supplied ID was not available or it was not accessible.

Action: Provide a valid accessible parent ID.
Level: 1

Type: WARNING

Impact: Other

WCS-09511: Announcement parent not found.

Cause: Announcement parent object is not accessible from discussion forum.

Action: Check if discussion service is configured properly.
Level: 1

Type: WARNING

Impact: Other

WCS-09512: Unable to lookup the announcement connection with name "{0}".

Cause: Either the announcement connection name is not valid or corresponding connection details are deleted from the connection store.

Action: Check the default connection name in adf-config for discussion announcement service or contact your system administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-09513: Ambiguous announcement connection definitions found in the connection store.

Cause: More than 1 connection type found for discussion announcement service. Unable to decide which one to use.

Action: Configure the appropriate connection name as the default connection to use from the management console or contact your system administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-09516: Announcement service configuration not found

Cause: service configuration details are missing

Action: Ensure service config details are either loadable from classpath or from adf-config.
Level: 1

Type: WARNING

Impact: Other

WCS-09517: Announcement service configuration not correct.

Cause: service configuration details are not provided as expected.

Action: Correct the service configuration details.
Level: 1

Type: WARNING

Impact: Other

WCS-09518: Host address "{0}" configured in connection store is not correct.

Cause: IP address of the host configured in connection store could not be determined.

Action: Configure the correct host name in connection store or contact your system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-09519: Not able to log on to the back-end system with host address "{0}".

Cause: Possible reasons: The IP address of the host configured in the connection store could not be determined, or the connection was refused by the host.

Action: Configure the correct host name in connection store or contact your system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-09520: Expiry date cannot be earlier than start date.

Cause: Expiry date is specified to be earlier than start date.

Action: Specify expiry date to be later than start date.
Level: 1

Type: WARNING

Impact: Other

WCS-09601: Not able to create announcement configuration file for community {0} due to : {1}.

Cause: Possible failure creating category or announcement or an issue with the MDS write operation.

Action: Contact your system administrator or read the announcement service configuration documentation for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-09602: Failed to flush changes into preference store due to {0}.

Cause: Possible failure in the backing store, or failure to contact the backing store.

Action: Contact system administrator
Level: 1

Type: ERROR

Impact: Other

WCS-11001: Error on content write: {0}

Cause: The content write operation failed for the given reason.

Action: Investigate the reason for the failure.
Level: 1

Type: ERROR

Impact: Other

WCS-11002: Internal server error: {0}

Cause: An unexpected internal error has occurred.

Action: Contact your Oracle Support representative.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-11003: Invalid Request

Cause: The client has submitted an invalid HTTP request.

Action: Re-send the corrected request.
Level: 1

Type: WARNING

Impact: Other

WCS-11004: Path not found: {0}

Cause: The requested path has not been found on the server.

Action: Correct the path on the client and re-send the request.
Level: 1

Type: WARNING

Impact: Other

WCS-11005: Not an ISO8601 date: {0}

Cause: The client supplied a date which is not in ISO8601 format.

Action: Correct the date format on the client and re-send the request.
Level: 1

Type: WARNING

Impact: Other

WCS-11006: Not an HTTP date: {0}

Cause: The client supplied a date which is not in HTTP date format.

Action: Correct the date format on the client and re-send the request.
Level: 1

Type: WARNING

Impact: Other

WCS-11007: Namespace not supported: {0}

Cause: The repository does not support the given namespace.

Action: Specify a valid namespace.
Level: 1

Type: WARNING

Impact: Other

WCS-11008: Bad request

Cause: The client submitted a request that could not be understood by the server.

Action: Correct the syntax and resubmit the request.
Level: 1

Type: WARNING

Impact: Other

WCS-11009: Not modified

Cause: The client has performed a conditional GET request, access is allowed but the document has not changed.

Action: No action required as resource has not been modified and hence it is not returned.
Level: 1

Type: ERROR

Impact: Other

WCS-11010: Not acceptable

Cause: The requested resource could not generate an entity with an acceptable media-type for the client.

Action: If applicable, resubmit the request with a broader acceptance criteria.
Level: 1

Type: ERROR

Impact: Other

WCS-11011: Precondition failed

Cause: A request precondition has failed.

Action: If applicable, resubmit the request with different preconditions.
Level: 1

Type: ERROR

Impact: Other

WCS-11012: The Java virtual machine does not support the UTF-8 character set.

Cause: The UTF-8 character set is not supported by the Java virtual machine.

Action: Contact your Oracle Support Representative.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-11013: No DAV dead property name matches the JCR property name {0}.

Cause: A unexpected JCR property name has been found that does not correspond to a DAV dead property name.

Action: Contact your Oracle Support Representative.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-11014: Cannot close the servlet output stream.

Cause: There was an error closing the servlet output stream.

Action: Review the server logs for possible cause of failure.
Level: 1

Type: ERROR

Impact: Other

WCS-11015: Cannot close content input stream.

Cause: There was an error closing the content input stream.

Action: Review the server logs for possible cause of failure.
Level: 1

Type: ERROR

Impact: Other

WCS-11016: Invalid resource name: {0}

Cause: The given name is not a valid resource name.

Action: The client should resubmit the request with a corrected URL.
Level: 1

Type: ERROR

Impact: Other

WCS-11017: Invalid resource name; illegal escape sequence in path: {0}

Cause: The given name was not a valid resource name as it contains an illegal escape sequence.

Action: The client should resubmit the request with a corrected URL.
Level: 1

Type: WARNING

Impact: Other

WCS-11018: Forbidden request method: {0}

Cause: The requested HTTP method was not completed as the server forbids the execution of this type of method.

Action: Compatible clients should not use the specified HTTP method.
Level: 1

Type: ERROR

Impact: Other

WCS-11019: Folder listing is disabled.

Cause: Folder listing has been disabled.

Action: Folder listing must be explicitly enabled in the application's web.xml.
Level: 1

Type: WARNING

Impact: Other

WCS-12001: No handlers could be found for services with IDs: {0}.

Cause: Handlers enable services to manage their data and metadata in the manner best suited to each service. Handlers that were recorded by the system during export were not available on import.

Action: Include compatible versions of handlers in the application and restart the import process.
Level: 1

Type: ERROR

Impact: Other

WCS-12002: The handler found in the classpath at run time cannot process the data or metadata of the archive: {0}.

Cause: Handlers enable services to manage their data and metadata in the manner best suited to each service. The version of the handler used during import was not compatible with the version of the handler used while creating the data or metadata on export.

Action: Include compatible versions of handlers in the application and restart the import process.
Level: 1

Type: ERROR

Impact: Other

WCS-12003: The required handlers are not found: {0}.

Cause: Handlers enable services to manage their data and metadata in the manner best suited to each service. Not all handlers that were used while creating this archive could be found during the import.

Action: Include compatible versions of handlers in the application and restart the import process.
Level: 1

Type: ERROR

Impact: Other

WCS-12004: Unable to retrieve the JAXB bean for the export/import document in MDS.

Cause: An error occurred in the MDS configuration of the application.

Action: Check the MDS configuration files of the application.
Level: 1

Type: ERROR

Impact: Other

WCS-12006: The export archive does not contain any scope metadata.

Cause: An error occurred during the export process, or the exported archive was damaged.

Action: Reattempt import with a different export file.
Level: 1

Type: ERROR

Impact: Other

WCS-12007: Scope with name {0} already exists in the import destination and it does not match with the scope being imported.

Cause: A scope with the specified name already exists for the current application instance. This caused a conflict between the source and target instances.

Action: Delete the scope from the current application instance and reattempt the import.
Level: 1

Type: ERROR

Impact: Other

WCS-12009: The Lifecycle Manager MBean cannot be deregistered.

Cause: There are numerous possible reasons for this failure.

Action: For information, review other messages in the log file and the reported exception stacks.
Level: 1

Type: WARNING

Impact: Other

WCS-12010: The Lifecycle Manager MBean cannot be created and registered. This problem will not prevent the application from running. However, the Lifecycle Manager will be unavailable.

Cause: There are numerous possible reasons for this failure.

Action: For information, review other messages in the log file and the reported exception stacks.
Level: 1

Type: WARNING

Impact: Other

WCS-12011: An MBean with the same name is already registered.

Cause: The name that was used to register the MBean is in use by another bean in the MBean server.

Action: Check the MBeans registered in the MBean server.
Level: 1

Type: WARNING

Impact: Other

WCS-12012: Information related to run time MBeans cannot be saved in the ADFContext application scope.

Cause: The system failed to store data in the ADFContext application scope. Lifecycle functions may not be available.

Action: Review the log files to see if there are any other problems which may have resulted in the ADFContext object becoming unusable.
Level: 1

Type: WARNING

Impact: Other

WCS-12013: An internal class cast error has occurred. Actual class: {0}, cast-to class: {1}.

Cause: The possible errors could be in the code or application configuration.

Action: Resolve any application configuration errors. If the problem recurs on subsequent attempts, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12014: The activity {0} has ended but completed less child activities ({1}) than the expected ({2}).

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-12015: The activity {0} has ended but completed more child activities ({1}) than the expected ({2}).

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-12016: The activity {0} has completed more child activities ({1}) than the expected ({2}).

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-12017: The export/import listener {0} has thrown an exception, which is being ignored.

Cause: A class listening to export/import progress events has thrown an exception.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: WARNING

Impact: Other

WCS-12018: The resource {0} for lifecycle operation cannot be found on the classpath.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-12019: The connection {0} cannot be exported because it is not a Reference or Referenceable.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-12020: An error has occurred while exporting the connection {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-12021: The output stream for table {0} failed to close. The exception {1} will not be thrown.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-12022: A SQL exception was thrown while closing the connection. This exception will be ignored.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-12023: An error has occurred while closing the output stream to which the XML was being written. The export process will not be aborted.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-12024: Value of the SQL type is not recognized, attempting to use the CHAR handler.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-12025: Value of the SQL type is not recognized.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-12026: A SQL exception {0} was caught while rolling back in response to an earlier exception {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-12027: A SQL exception {0} was caught while closing the statement {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-12028: A SQL exception {0} was caught while closing the connection {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-12029: An error {1} has occurred while creating a DocumentName for table {0}. The import will not be aborted.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-12030: An error {1} has occurred while retrieving input stream from MDS for {0}. The import will not be aborted.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-12031: An error {1} has occurred while deleting the table export document {0} from MDS. The import will not be aborted.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-12032: The Queue Callback handler was interrupted while waiting for child threads to complete.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-12033: Exception occurred in child thread: {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-12034: The Queue Consumer with name {0} was interrupted while taking an object from the queue. The Queue Consumer will continue and ignore the exception: {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-12038: IOException while creating stage directory for export

Cause: The possible causes could be coding, hardware, or file system errors.

Action: Review the full exception stack for details of the exception.
Level: 1

Type: ERROR

Impact: Other

WCS-12039: IOException while creating temporary directory to extract the import archive to

Cause: The possible causes could be coding, hardware, or file system errors.

Action: Review the full exception stack for details of the exception.
Level: 1

Type: ERROR

Impact: Other

WCS-12040: IOException extracting import archive

Cause: The possible causes could be coding, hardware, or file system errors.

Action: Review the full exception stack for details of the exception.
Level: 1

Type: ERROR

Impact: Other

WCS-12041: Input archive path not set on context.

Cause: The possible errors could be in the code or application configuration.

Action: Resolve any application configuration errors. If the problem recurs on subsequent attempts, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12042: Input archive does not exist.

Cause: The possible errors could be in the code or application configuration.

Action: Resolve any application configuration errors. If the problem recurs on subsequent attempts, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12043: MDSConfigurationException constructing source instance for MDS transfer.

Cause: The possible errors could be in the code or application configuration.

Action: Resolve any application configuration errors. If the problem recurs on subsequent attempts, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12044: An unanticipated exception {0} has occurred while generating the oracle-archive.xml deployment descriptor of the export archive.

Cause: Cause is dependent upon the type and details of the exception being processed.

Action: Review the exception being processed for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-12045: Operation aborted because of an exception thrown by subunit ({0})

Cause: The cause of the exception that was thrown is dependent upon the type and details of the exception.

Action: Review the exception thrown for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-12046: MDSException while creating lifecycle document in MDS transfer source

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12047: The import archive file {0} does not contain a metadata archive.

Cause: The supplied file to import was not a valid export archive.

Action: Retry the import operation with a valid export archive.
Level: 1

Type: ERROR

Impact: Other

WCS-12048: FileNotFoundException extracting metadata transport archive

Cause: The possible causes could be coding, hardware, or file system errors.

Action: Resolve any hardware or file system errors. If the problem recurs on subsequent attempts, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12049: IOException while extracting metadata transport archive

Cause: The possible causes could be coding, hardware, or file system errors.

Action: Review the full exception stack for details of the exception.
Level: 1

Type: ERROR

Impact: Other

WCS-12050: IOException while creating metadata transport archive

Cause: The possible causes could be coding, hardware, or file system errors.

Action: Review the full exception stack for details of the exception.
Level: 1

Type: ERROR

Impact: Other

WCS-12051: Output path has not been set on operation context.

Cause: The possible errors could be in the code or application configuration.

Action: Resolve any application configuration errors. If the problem recurs on subsequent attempts, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12052: MDSException constructing transfer list for MDS transfer.

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12053: MDSException performing MDS transfer.

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12054: MDSException deleting existing metadata.

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12055: An exception has occurred while creating the transformer factory to write lifecycle information document.

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12056: IOException occurred creating lifecycle information document

Cause: An error occurred writing to the file system while creating the lifecycle information document. The possible causes could be application configuration, or hardware errors.

Action: Review the full exception stack for details of the exception.
Level: 1

Type: ERROR

Impact: Other

WCS-12057: TransformerException while writing lifecycle information document

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12058: Input path has not been set on operation context.

Cause: The possible errors could be in the code or application configuration.

Action: Resolve any application configuration errors. If the problem recurs on subsequent attempts, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12059: IOException while creating oracle-archive.xml

Cause: An error occurred while writing the oracle-archive.xml file to the file system. The possible causes could be application configuration, or hardware errors.

Action: Review the full exception stack for details of the exception.
Level: 1

Type: ERROR

Impact: Other

WCS-12060: IOException while creating transport archive

Cause: The possible causes could be coding, hardware, or file system errors.

Action: Review the full exception stack for details of the exception.
Level: 1

Type: ERROR

Impact: Other

WCS-12061: Output archive path has not been set on operation context.

Cause: The possible errors could be in the code or application configuration.

Action: Resolve any application configuration errors. If the problem recurs on subsequent attempts, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12062: An unexpected exception occurred while removing lock {0}:{1}

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12063: MDSException occurred while removing lock {0}:{1}

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12064: A lock is blocking the import.

Cause: Another operation was being performed that prevented application import.

Action: Retry the import operation after the other operation is complete.
Level: 1

Type: ERROR

Impact: Other

WCS-12065: A lock exists that prevents the application import.

Cause: Another application import was being performed that prevented this import.

Action: Retry the import operation after the other operation is complete
Level: 1

Type: ERROR

Impact: Other

WCS-12066: MDSException while creating application import lock

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12067: A lock is blocking the import of scope {0}.

Cause: Another operation was being performed that prevented the import.

Action: Retry the import operation after the other operation is complete
Level: 1

Type: ERROR

Impact: Other

WCS-12068: A lock exists that prevents the import of scope {0}.

Cause: An import of the specified scope was being performed that prevented this import.

Action: Retry the import operation after the other operation is complete
Level: 1

Type: ERROR

Impact: Other

WCS-12069: MDSException while creating scope import lock

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12070: A lock exists that blocks the export set import.

Cause: Another operation was being performed that prevented the export set import.

Action: Retry the import operation after the other operation is complete
Level: 1

Type: ERROR

Impact: Other

WCS-12071: A lock exists that prevents the export set import.

Cause: An export set import was already being performed preventing this import.

Action: Retry the import operation after the other operation is complete
Level: 1

Type: ERROR

Impact: Other

WCS-12072: MDSException while creating an export set import lock

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12073: MDSException while obtaining the Lifecycle bean from the MDS session

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12074: ID of export set in MDS does not match that of the application. MDS ID: {0}, Application ID: {1}.

Cause: An export set was imported from an incompatible source and has been ignored.

Action: Import an export set from a compatible instance.
Level: 1

Type: ERROR

Impact: Other

WCS-12076: NamingException while binding connection {0} to the export connections.xml

Cause: The possible causes could be coding or application configuration errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12077: NamingException while getting environment for exporting the ADF credential store

Cause: The possible causes could be coding or application configuration errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12078: IOException while exporting ADF credential store

Cause: The possible causes could be coding, hardware, or file system errors.

Action: Review the full exception stack for details of the exception.
Level: 1

Type: ERROR

Impact: Other

WCS-12079: JPSException while exporting JPS credential store

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12080: MDSException while creating lifecycle information metadata in transport set

Cause: An existing document with the same name as the lifecycle information document was found in the transport set being constructed.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12081: ReferenceException while creating lifecycle information metadata in transport set

Cause: An unexpected exception occurred while creating the lifecycle document in transport set.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12082: UnsupportedUpdateException while creating lifecycle information metadata in transport set

Cause: An unexpected exception occurred while creating the lifecycle document in the transport set.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12083: MDSException while building transfer list for lifecycle metadata

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12084: MDSException while constructing metadata store for MDS transfer

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12085: ParserConfigurationException while creating lifecycle information document

Cause: An unexpected exception occurred while creating the lifecycle document in the transport set.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12086: SAXException while creating lifecycle information document

Cause: An unexpected exception occurred while creating the lifecycle document in the transport set.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12087: ServiceException while getting registered services

Cause: There was an error in the application's configuration.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12088: Cannot find lifecycle service extension registry

Cause: An error in the application's configuration.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12089: Destination path specified to create the temporary directory is not a directory.

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Resolve any application configuration or hardware errors. If the problem recurs on subsequent attempts, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12090: The source path specified to archive does not exist

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Resolve any application configuration or hardware errors. If the problem recurs on subsequent attempts, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12091: The source path specified to archive is not a directory

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Resolve any application configuration or hardware errors. If the problem recurs on subsequent attempts, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12092: A file already exists with the same name as the destination folder.

Cause: A call was made to extract an archive to a destination directory with the same name as an existing file.

Action: Retry the operation that caused this error.
Level: 1

Type: ERROR

Impact: Other

WCS-12093: {0} is an invalid value for the maximum number of steps. The maximum number of steps must be a least 1.

Cause: The probable cause is a coding error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12094: MDSException while constructing metadata store for MDS transfer

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12095: Import archive {0} does not exist or could not be read.

Cause: The specified file could not be found either because it does not exist or does not have the correct access permissions.

Action: Check that the path is correct, the file exists and has the appropriate access permissions.
Level: 1

Type: ERROR

Impact: Other

WCS-12096: A lock is blocking the export.

Cause: Another operation was being performed that prevented application export.

Action: Retry the export operation after the other operation is complete.
Level: 1

Type: ERROR

Impact: Other

WCS-12097: A lock exists that prevents the application export.

Cause: An import was being performed that prevented this export.

Action: Retry the export operation after the other operation is complete
Level: 1

Type: ERROR

Impact: Other

WCS-12098: MDSException while creating application export lock

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12099: An unexpected exception occurred while refreshing lock {0}:{1}

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: WARNING

Impact: Other

WCS-12100: MDSException occurred while refreshing lock {0}:{1}

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: WARNING

Impact: Other

WCS-12101: Unable to find data source

Cause: The data source hasn't been configured

Action: Configure the data source
Level: 1

Type: ERROR

Impact: Other

WCS-12102: An exception occured whilst refreshing lock {0}:{1}

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12920: A problem was encountered when invoking a method on a remote mBean ({0}) which has caused the local operation to fail.

Cause: In order for the local operation to be performed a method on a remote mBean has to be invoked - there are numerous reasons why the remote method invocation could fail ranging from connection problems between servers to the remote object simply not existing

Action: Review the log files for a record of this error in order to ascertain the primary cause.
Level: 1

Type: ERROR

Impact: Other

WCS-12950: The required customization class is not found: {0}

Cause: To export the specified customization class, first an instance of the class must be created. An instance of this class could not be created because the class was not included in the classpath.

Action: Include the customization class in the classpath of the application and restart the application.
Level: 1

Type: ERROR

Impact: Other

WCS-12951: The required customization class cannot be instantiated: {0}

Cause: To export the specified customization class, first an instance of the class must be created. An instance of this class could not be created because it is an interface or abstract class.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12952: The required customization class cannot be instantiated: {0}

Cause: To export the specified customization class, first an instance of the class must be created. An instance of this class could not be created because the current method was unable to access it.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12953: A listener cannot be registered to generate notification about the progress of the export. The export will continue but notification will not be generated on its progress.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-12955: The notification has arrived out of sequence. Latest sequence:{0}; sequence of this notification:{1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-12957: An exception occurred while importing data, no data has been imported.

Cause: The possible causes could be hardware, or application configuration errors.

Action: For information, review other messages in the log file and the reported exception stacks. Resolve any application configuration or hardware errors.
Level: 1

Type: WARNING

Impact: Other

WCS-12958: Import has failed with errors.

Cause: The possible causes could be hardware, or application configuration errors.

Action: For information, review other messages in the log file and the reported exception stacks. Resolve any application configuration or hardware errors.
Level: 1

Type: ERROR

Impact: Other

WCS-12959: Export has failed with errors.

Cause: The possible causes could be hardware, or application configuration errors.

Action: For information, review other messages in the log file and the reported exception stacks. Resolve any application configuration or hardware errors.
Level: 1

Type: ERROR

Impact: Other

WCS-12980: Service {0} has not been provisioned for Scope {1}.

Cause: The Service has not been provisioned for the specified Scope.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12981: Service {0} has already been provisioned for Scope {1}.

Cause: The Service has already been provisioned for the specified Scope.

Action: Do not provision the Service for a Scope it is already provisioned for or unprovision the Service first.
Level: 1

Type: ERROR

Impact: Other

WCS-12982: Scope {0} is not known.

Cause: A Scope with the specified name has not been created.

Action: Create a Scope with the specified name using the createScope method on the ServiceContext.
Level: 1

Type: ERROR

Impact: Other

WCS-12983: Service {0} has not been configured for the application.

Cause: The Service has not been configured for the application.

Action: Configure the Service and try the operation again.
Level: 1

Type: ERROR

Impact: Other

WCS-12984: An error occurred removing the security policies for service {0}.

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Review the full exception stack for details of the exception.
Level: 1

Type: ERROR

Impact: Other

WCS-12985: An error occurred invoking isProvisioned for service {0}.

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Review the full exception stack for details of the exception.
Level: 1

Type: WARNING

Impact: Other

WCS-12990: Specified key does not match that of the lock with type ''{0}'' and name ''{1}''.

Cause: The application attempted to manipulate a lock with an incorrect lock key.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12991: Lock with type ''{0}'' and name ''{1}'' already exists.

Cause: A lock with the specified type and name already exists.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12992: Lock with type ''{0}'' and name ''{1}'' does not exist.

Cause: The application attempted to manipulate a lock that no longer exists.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12993: Lock with type ''{0}'' and name ''{1}'' could not be created as a lock with type ''{2}'' exists.

Cause: A lock with a type that prevents locks with the specified type being created exists.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-14001: An unexpected error occurred.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-14002: An object of type {0} with this id ({1}) already exits.

Cause: An attempt was made to create an object with an id that is already in use.

Action: Specify a unique id.
Level: 1

Type: ERROR

Impact: Other

WCS-14004: The name ({0}) is not valid.

Cause: The specified name is not valid.

Action: Specify a valid name.
Level: 1

Type: ERROR

Impact: Other

WCS-14005: The specified list type could not be found.

Cause: The specified list type could not be found. This may be due to the list type being deleted by another user.

Action: Try reloading to see if the list has been deleted.
Level: 1

Type: ERROR

Impact: Other

WCS-14006: Object has been changed by another user.

Cause: The object has been changed by another user.

Action: Reload the object and try the operation again.
Level: 1

Type: ERROR

Impact: Other

WCS-14007: An Object of type {0} with id={1} could not be found.

Cause: The specified object could not be found. This may be due to the list being deleted by another user.

Action: Specify a valid id.
Level: 1

Type: ERROR

Impact: Other

WCS-14008: Object ({0}) is immutable.

Cause: An attempt to change this object was made, but this object is currently immutable.

Action: Retrieve mutable object to make changes.
Level: 1

Type: ERROR

Impact: Other

WCS-14010: {0} is not a valid reference name to MDS.

Cause: The name is not a valid MDS reference name.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-14011: The MDS session does not support updates.

Cause: MDS was not configured correctly to support updates.

Action: Configure the MDS store to support updates.
Level: 1

Type: ERROR

Impact: Other

WCS-14012: An IO error occurred when accessing metadata.

Cause: An IO error occurred in MDS.

Action: See the log for more details on the specific IO error to correct the problem.
Level: 1

Type: ERROR

Impact: Other

WCS-14013: The object is not valid.

Cause: The metadata for the object does not pass validation.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-14014: Failed to construct attribute set for list [{0}].

Cause: Failed to construct attribute set for list.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-14015: Failed to add data flavor to ListTransferable. List=[{0}] DataFlavor=[{1}]

Cause: Failed to add data flavor to ListTransferable.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-14016: The query attribute predicate {0}{1}{2} was ignored because the column does not exist or the comparator is not supported.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-14017: An error occurred when deleting metadata.

Cause: An error occurred in MDS while deleting metadata.

Action: See the log for more details on the specific error to correct the problem.
Level: 1

Type: ERROR

Impact: Other

WCS-14018: A column with the name ({0}) already exists.

Cause: A column was created or renamed with the name of an existing column in the list.

Action: Specify a unique column name within the list.
Level: 1

Type: ERROR

Impact: Other

WCS-14019: A list with the name ({0}) already exists.

Cause: A list was created or renamed with the name of an existing list.

Action: Specify a unique list name.
Level: 1

Type: ERROR

Impact: Other

WCS-14020: The maximum number of columns for this list has been exceeded.

Cause: A list was created or modified with more than 30 columns.

Action: Do not add more than 30 columns to a list.
Level: 1

Type: ERROR

Impact: Other

WCS-14021: User does not have permission to perform {0} operation for {1}.

Cause: User does not have permission to perform the specified operation.

Action: Grant the user permission to perform the specified operation.
Level: 1

Type: ERROR

Impact: Other

WCS-14022: The Lists service is not provisioned for scope {0}.

Cause: The Lists service is not provisioned for the specified scope.

Action: Provision the Lists service for the specified scope.
Level: 1

Type: ERROR

Impact: Other

WCS-14023: The value is the wrong data type. The data type expected is {0}.

Cause: The value is the wrong data type.

Action: Use the value with the correct data type.
Level: 1

Type: ERROR

Impact: Other

WCS-14024: The WebCenter repository is not available.

Cause: An error occurred accessing the repository.

Action: Contact your system administrator. Check the log for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-14025: An error occurred accessing the WebCenter metadata repository.

Cause: An error occurred accessing the repository.

Action: Contact your system administrator. Check the log for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-14501: The list was not found.

Cause: The list could not be found.

Action: Remove the list view for the invalid list from the page.
Level: 1

Type: ERROR

Impact: Other

WCS-14502: This row was deleted by another user after you displayed it. Refresh the list to see the changes.

Cause: This row no longer exists. It was deleted by another user.

Action: Refresh the list to see the changes.
Level: 1

Type: ERROR

Impact: Other

WCS-14503: This row was modified by another user after you displayed it. Refresh the list to see the changes.

Cause: This row was modified by another user after you displayed it. You must have the current values in order to modify the row.

Action: Refresh the list to see the changes.
Level: 1

Type: ERROR

Impact: Other

WCS-14504: This list was deleted by another user after you displayed it. Click the Refresh icon or Cancel button, as appropriate, to see the changes.

Cause: This list no longer exists. It was deleted by another user.

Action: Click the Refresh icon to see the changes.
Level: 1

Type: ERROR

Impact: Other

WCS-14505: This list was modified by another user after you displayed it. Click the Refresh icon or Cancel button, as appropriate, to see the changes.

Cause: This list was modified by another user after you displayed it. You must have the current definition.

Action: Click the Refresh icon to see the changes.
Level: 1

Type: ERROR

Impact: Other

WCS-14506: Invalid minimum/maximum range

Cause: Minimum value must be less than or equal to maximum value.

Action: Modify the mininum value or maximum value.
Level: 1

Type: ERROR

Impact: Other

WCS-14507: Default value is out of range

Cause: Default value must be between the mininum and maximum values.

Action: Modify the default value, mininum value, or maximum value.
Level: 1

Type: ERROR

Impact: Other

WCS-14508: An error occurred accessing the WebCenter repository.

Cause: An error occurred accessing the repository.

Action: Contact your system administrator. Check the log for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-14509: You no longer have permission to perform this operation. Click the Refresh icon or Cancel button, as appropriate, to see the changes.

Cause: You do not have permission to perform the specified operation.

Action: You must be granted permission to perform the specified operation.
Level: 1

Type: ERROR

Impact: Other

WCS-14510: The Lists service has been disabled, so you can no longer perform this operation. Click the Refresh icon or Cancel button, as appropriate, to see the changes.

Cause: The Lists service is not enabled.

Action: Enable the Lists service.
Level: 1

Type: ERROR

Impact: Other

WCS-14514: An unexpected error occurred. Please retry the operation.

Cause: An unexpected error occurred.

Action: Retry the operation. If the problem persists, contact your administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-14515: Default value is too long

Cause: Default value must not exceed the maximum length.

Action: Modify the default value or maximum length.
Level: 1

Type: ERROR

Impact: Other

WCS-14516: The WebCenter metadata repository was temporarily unavailable. Please retry the operation.

Cause: The connection to the WebCenter metadata repository failed.

Action: Retry the operation. If the problem persists, contact your administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-18001: An unexpected error occurred.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18002: Missing Configuration for List of Contacts. Could not locate the class {0}.

Cause: An incorrect class name was provided.

Action: Please contact Oracle Support.
Level: 1

Type: ERROR

Impact: Other

WCS-18003: Class {0} does not implement the interface {1}.

Cause: The specified class had not implemented the required interface.

Action: Ensure that the class implements the required interface.
Level: 1

Type: ERROR

Impact: Other

WCS-18004: Cannot instantiate class {0}.

Cause: The specified class did not have a default constructor accessible to public.

Action: Ensure that the class has a default constructor and it is accessible to public.
Level: 1

Type: ERROR

Impact: Other

WCS-18005: Cannot instantiate class {0}.

Cause: Either the specified class was not a concrete implementation or it did not have a default constructor accessible to public.

Action: Ensure that the class is a concrete implementation and has a default constructor accessible to public.
Level: 1

Type: ERROR

Impact: Other

WCS-18006: The implementation class {0} returned null.

Cause: The implementation class returned a null object.

Action: Ensure that the implementation class returns a non-null list of contacts.
Level: 1

Type: WARNING

Impact: Other

WCS-18007: An error occurred while trying to validate metadata.

Cause: Invalid metadata has been introduced.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18008: Unable to save the metadata in persistence store

Cause: An error occurred while writing to persistence store or metadata was locked by another user.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18009: Cannot apply the current metadata changes to a concurrently modified metadata.

Cause: Recent changes in this session conflicts with changes made in the same session.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18010: Cannot locate the requested metadata.

Cause: The metadata was not found in the configured metadata stores or it had been deleted on this session.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18011: Cannot obtain the metadata for write operations.

Cause: The metadata store could be spanning multiple back-end stores or concurrent updates were attempted.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18012: Metadata already exists in metadata store.

Cause: An attempt was made to create a metadata document when it already exists.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18013: The reference to the specified metadata is invalid.

Cause: The reference to the metadata was incorrect.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18014: Could not be complete the sort operation.

Cause: A null table component was returned.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18015: Could not get contact details.

Cause: The selected contact details were unavailable due to an internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18016: Could not launch the dialog for view {0}.

Cause: Profile page details are unavailable due to an internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18017: Could not perform a people search.

Cause: Instance of identity store is not available.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18018: Could not get display name from user profile.

Cause: User did not have the display name or user's profile was not accessible.

Action: Contact the administrator of directory services/webcenter.
Level: 1

Type: WARNING

Impact: Other

WCS-18019: Could not get name from user profile.

Cause: User does not have the name or user's profile is not accessible.

Action: Please contact the administrator of directory services/webcenter.
Level: 1

Type: WARNING

Impact: Other

WCS-18020: Could not save the search criterion.

Cause: An internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18021: Could not fetch the search criterion.

Cause: An internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18022: Could not fetch the sort criteria.

Cause: An internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18023: Could not save the sort criteria.

Cause: An internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18024: Cannot get an instance of the identity store

Cause: There was either an improper configuration or an internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18025: Could not create the contacts list.

Cause: An internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18026: Could not perform a people search.

Cause: An internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18401: An unexpected error occurred in the Message Board sub-system.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18402: Failed to create an instance of Message Board

Cause: Message Board viewing user name not found

Action: Make sure that the user is logged in
Level: 1

Type: ERROR

Impact: Other

WCS-18403: Failed to create an instance of Message Board

Cause: Message Board owner user name not specified

Action: Provide owner user name in the request for an instance of Message Board
Level: 1

Type: ERROR

Impact: Other

WCS-18404: Failed to persist Message Board message

Cause: An unexpected error occurred

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18405: Failed to publish Message Board activity

Cause: Activity Stream service raised an exception

Action: Verify the reason for the failure in the Activity Stream sub-system
Level: 1

Type: ERROR

Impact: Other

WCS-18406: Message Board message cannot be deleted

Cause: User is not authorized to delete this message

Action: Resubmit the request with correct parameters
Level: 1

Type: ERROR

Impact: Other

WCS-18407: Failed to delete Message Board message

Cause: Message does not exist

Action: Resubmit the request with correct parameters
Level: 1

Type: ERROR

Impact: Other

WCS-18408: Message Board message cannot be updated

Cause: User is not authorized to update this message

Action: Resubmit the request with correct parameters
Level: 1

Type: ERROR

Impact: Other

WCS-18409: Failed to update Message Board message

Cause: Message does not exist

Action: Resubmit the request with correct parameters
Level: 1

Type: ERROR

Impact: Other

WCS-18410: Message Board message cannot be added

Cause: Message content is empty

Action: Provide a non empty message board message text
Level: 1

Type: ERROR

Impact: Other

WCS-18411: Message Board message cannot be hidden

Cause: User is not authorized to hide message

Action: Resubmit the request with correct parameters
Level: 1

Type: ERROR

Impact: Other

WCS-18412: Failed to hide Message Board message

Cause: Message does not exist

Action: Resubmit the request with correct parameters
Level: 1

Type: ERROR

Impact: Other

WCS-18413: Failed to retrieve user display name from profile service

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-18414: Failed to add message to Message Board.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18415: Failed to hide or unhide message in Message Board.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18416: Failed to delete message in Message Board.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18417: Failed to query messages in Message Board.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18418: Failed to update message in Message Board.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18419: Failed to create an instance of Message Board.

Cause: Message Board preferences manager not specified

Action: Provide preferences manager in the request for Message Board
Level: 1

Type: ERROR

Impact: Other

WCS-18420: Failed to query preferences for Message Board.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18421: Message cannot be added to Message Board.

Cause: User is not authorized to add message

Action: Resubmit the request with correct parameters
Level: 1

Type: ERROR

Impact: Other

WCS-18501: An unexpected error occurred in the profile sub-system.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18502: User: {0} not found in identity store.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18503: Personal status note can be changed only for the current user

Cause: attempt made by an user to update personal status of another user

Action: login as the user whose status you want to change
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18504: unexpected error operating on personal status note

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18505: unexpected error saving profile

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18506: Current user does not have view profile privilege.

Cause: Insufficient privilege to view Profile.

Action: Contact Webcenter Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-18507: Insufficient Privilege.

Cause: Cannot Edit Profile.

Action: Contact Webcenter Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-18508: Unexpected error retrieving user {0}''s photo

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18509: Unexpected error saving user {0}''s photo to the back-end. The photo may not have been saved. Please refresh to find out and then retry the operation.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18510: Unexpected error invalidating user {0}''s photo cache

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18511: User not specified

Cause: The supplied username was null or blank.

Action: Specify a valid username that is not null or blank.
Level: 1

Type: ERROR

Impact: Other

WCS-18512: Unexpected error serving the requested photo {0}

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18514: Unexpected error saving the Profile Admin Settings

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18515: Unexpected error saving the Profile user preference

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18516: Unexpected error initializing the admin config bean

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18517: Unexpected error saving the profile

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18518: Unexpected Error Initializing profile cache

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18519: Unexpected error doing cache operations on profile

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18520: Unexpected error retrieving unique identifier for user {0}''s photo

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18521: Unexpected error evaluating property ''{0}'' of base {1}

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18522: Modifying property ''{0}'' of base {1} not allowed

Cause: The application does not allow modifying the value of the specified property of the specified base object.

Action: Ensure that property of the object being modified is not read-only.
Level: 1

Type: ERROR

Impact: Other

WCS-18523: Error getting the instant message address for the person

Cause: unexpected error getting the sip address

Action: contact the administrator
Level: 1

Type: ERROR

Impact: Other

WCS-18524: Error getting tag data

Cause: unexpected error getting tag data

Action: contact the administrator
Level: 1

Type: ERROR

Impact: Other

WCS-18525: Unexpected error saving attribute: {0}

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services with the error on the log.
Level: 1

Type: ERROR

Impact: Other

WCS-18701: An unexpected error occurred in the Feedback sub-system.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18702: Failed to create an instance of Feedback

Cause: Feedback object's viewing user name not found

Action: Make sure that the user is logged in
Level: 1

Type: ERROR

Impact: Other

WCS-18703: Failed to create an instance of Feedback

Cause: Feedback object's user name not specified

Action: Provide user name in the request for an instance of Feedback
Level: 1

Type: ERROR

Impact: Other

WCS-18704: Failed to persist Feedback message

Cause: An unexpected error occurred

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18705: Failed to publish Feedback activity

Cause: Activity Stream service raised an exception

Action: Verify the reason for the failure in the Activity Stream sub-system
Level: 1

Type: ERROR

Impact: Other

WCS-18706: Feedback message cannot be deleted

Cause: User is not authorized to delete this message

Action: Resubmit the request with correct parameters
Level: 1

Type: ERROR

Impact: Other

WCS-18707: Failed to delete Feedback message

Cause: Message does not exist

Action: Resubmit the request with correct parameters
Level: 1

Type: ERROR

Impact: Other

WCS-18708: Feedback message cannot be updated

Cause: User is not authorized to update this message

Action: Resubmit the request with correct parameters
Level: 1

Type: ERROR

Impact: Other

WCS-18709: Failed to update Feedback message

Cause: Message does not exist

Action: Resubmit the request with correct parameters
Level: 1

Type: ERROR

Impact: Other

WCS-18710: Feedback message cannot be added

Cause: User is not authorized to add message

Action: Resubmit the request with correct parameters
Level: 1

Type: ERROR

Impact: Other

WCS-18711: Feedback message cannot be hidden

Cause: User is not authorized to hide message

Action: Resubmit the request with correct parameters
Level: 1

Type: ERROR

Impact: Other

WCS-18712: Failed to hide Feedback message

Cause: Message does not exist

Action: Resubmit the request with correct parameters
Level: 1

Type: ERROR

Impact: Other

WCS-18713: Feedback message cannot be added

Cause: Feedback message content is empty

Action: Provide a non empty feedback message text
Level: 1

Type: ERROR

Impact: Other

WCS-18714: Failed to retrieve user display name from profile service

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-18715: Failed to add feedback.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18716: Failed to hide or unhide feedback.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18717: Failed to delete feedback.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18718: Failed to query feedback messages.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18719: Failed to create an instance of Feedback

Cause: Feedback object's preferences manager not specified

Action: Provide preferences manager in the request for an instance of Feedback
Level: 1

Type: ERROR

Impact: Other

WCS-18720: Failed to query preferences for Feedback object.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19001: Unexpected error occurred

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19002: Unable to execute WebCenter operation on {0}

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19003: Metadata file {0} not found

Cause: The expected metadata file was not found

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19004: Unexpected error occurred while creating page table

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19005: Internal error while creating policy store metadata for WebCenter {0}

Cause: Policy store for WebCenter not found

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19007: Unable to copy WebCenter or group space policies for {0}

Cause: Exception occurred while copying WebCenter policies.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19008: No matching users were found with search string {0}

Cause: No users matched the search string you entered: {0}

Action: Enter a new search term and try again
Level: 1

Type: ERROR

Impact: Other

WCS-19010: No matching roles were found with search string {0}

Cause: No WebCenter roles matched the search string you entered: {0}

Action: Enter a new search term and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19013: User name can not be null

Cause: A null or empty string was provided for the user name.

Action: Enter a valid user name.
Level: 1

Type: ERROR

Impact: Other

WCS-19014: Role name can not be null

Cause: A null or empty string was provided for the role name.

Action: Enter a valid role name.
Level: 1

Type: ERROR

Impact: Other

WCS-19016: Unable to grant user {2} with role {1} in {0}

Cause: An attempt to grant a user role failed. Either, role {1} does not exist, user {0} does not exist, or the user is already granted the role

Action: Determine the cause and, if necessary, try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19017: Unable to revoke role {1} from user{0}

Cause: An attempt to grant a user role failed. Either, role {1} does not exist, user {0} does not exist, or the user does not have the specified role.

Action: Determine the cause and, if necessary, try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19018: Unable to add role {0} to the policy store

Cause: An attempt to create a new role failed. Either the role already exists, or the policy store is currently unavailable

Action: Determine the cause and, if necessary, try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19019: An error occurred while trying to remove role{0} from the policy store

Cause: An attempt to delete the specified role failed. Either the role does not exist, or the policy store is currently unavailable.

Action: Determine the cause and, if necessary, try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19020: User {0} has already been granted the role {1}.

Cause: User has been already granted the same role.

Action: Determine the cause and, if necessary, try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19022: Role {0} already exists in the policy store

Cause: An attempt to create a new role failed because the policy store contains a role with the name specified.

Action: Enter a unique name for the role.
Level: 1

Type: ERROR

Impact: Other

WCS-19025: Only authenticated users can perform the requested operation

Cause: You do not have sufficient privileges to perform the requested operations.

Action: Ask your WebCenter administrator to grant you the appropriate privileges and then try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19026: Unable to revoke permission {0}

Cause: The specified permission was not removed from the policy store. The permission may not exist

Action: Check whether the permission exists in the policy store
Level: 1

Type: ERROR

Impact: Other

WCS-19027: Unable to grant permission {0}

Cause: The user was not granted the specified permission. The user may already be assigned that permission.

Action: Check whether the user is assigned this permission.
Level: 1

Type: ERROR

Impact: Other

WCS-19029: Application policy for WebCenter Spaces could not be found

Cause: The application policy for WebCenter Spaces was missing from the policy store.

Action: Check the WebCenter Spaces policy store is configured correctly.
Level: 1

Type: ERROR

Impact: Other

WCS-19030: Page definition for page {0} not found

Cause: Page definition for page {0} does not exist.

Action: Check whether the page definition for page {0} exists
Level: 1

Type: ERROR

Impact: Other

WCS-19031: Policy store instance cannot be null

Cause: No policy store instance was found

Action: Verify and instantiate the policy store instance and try the operation again.
Level: 1

Type: ERROR

Impact: Other

WCS-19032: Security Manager already initialized

Cause: An attempt was made to initialize the Security Manager but it was already initialized.

Action: Use the existing Security Manager.
Level: 1

Type: ERROR

Impact: Other

WCS-19033: Security Manager is not initialized

Cause: A security operation was attempted before the Security Manager was initialized.

Action: Initialize the Security Manager and try again
Level: 1

Type: ERROR

Impact: Other

WCS-19034: WebCenterSecurityManager class cannot be initialized directly

Cause: An attempt was made to initialize the WebCenterSecurityManager class through a protected constructor.

Action: Initialize the WebCenterSecurityManager class with a default constructor.
Level: 1

Type: ERROR

Impact: Other

WCS-19035: Security Manager is null

Cause: Security Manager could not be initialized

Action: Use valid parameters and try again.
Level: 1

Type: WARNING

Impact: Other

WCS-19036: Scoped Security Manager is null for scope {0}

Cause: Security manager can not be initialized

Action: Please try to initialize again with proper parameters
Level: 1

Type: WARNING

Impact: Other

WCS-19037: Invalid context {1} for scope {0}

Cause: Current scope did not match the cached scope

Action: Refresh your page again and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19038: An error occurred while importing security policies.

Cause: Failed to create security policies (grants, roles and permissions) during import.

Action: Verify that the export archive is valid, otherwise check logs for error details and contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19039: ADFContext is NULL, so returning NULL as username

Cause: An internal error occurred while fetching the user name.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19040: SecurityContext is NULL, so returning NULL as username

Cause: SecurityContext was not found for the current session

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19042: Unable to retrieve Personal Sidebar items

Cause: An error locating for opening the JSPX document for the Personal Sidebar

Action: Ensure that the JSPX document pointing to the Personal Sidebar is available to the application
Level: 1

Type: ERROR

Impact: Other

WCS-19043: Unable to persist personalization for tag with webcenterId ''{0}'' in the Personal Sidebar

Cause: An error saving the personalization document for the Personal Sidebar JSPX, or the tag with this webcenterId could not be located.

Action: Ensure that the personalization is enabled on the Personal Sidebar JSPX, and the tag has a unique webcenterId
Level: 1

Type: ERROR

Impact: Other

WCS-19044: Unable to retrieve item called {0} from the shell in the request {1}

Cause: Either the item name is incorrect or the item is not available in the current shell context

Action: Verify that the item name is correct and that the shell context is setup properly for the current request.
Level: 1

Type: WARNING

Impact: Other

WCS-19045: Unable to register shell handler of type {0}

Cause: Either the class name of the shell handler is incorrect or there was a problem while instantiating the shell handler

Action: Verify whether the shell handler type is correct or determine why the shell handler is not instantiating properly
Level: 1

Type: WARNING

Impact: Other

WCS-19046: Unable to retrieve the visibility of shell panel {0}

Cause: An error occurred trying to retrieve the visibility information from the shell handler of the current request.

Action: Defaulting visibility to 'true'
Level: 1

Type: WARNING

Impact: Other

WCS-19048: Unable to retrieve panel metadata for panel properties (panel name: {0})

Cause: The metadata for the panel in the shell metadata document may be corrupted or missing, or the name of the panel is incorrect.

Action: Verify whether the panel name is correct and whether the metadata for the panel is valid
Level: 1

Type: ERROR

Impact: Other

WCS-19049: An attempt to set change the skin was ignored

Cause: An attempt was made to change the skin but this feature is not yet implemented.

Action: Contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

WCS-19051: An attempt was made to set the template and ignored

Cause: This change would not take place as the feature is not implemented

Action: Please contact Oracle Support for more details
Level: 1

Type: WARNING

Impact: Other

WCS-19054: Error retrieving a physical page view-id for the request {0} (context URL {1})

Cause: The request URL could be invalid, or an unknown problem occurred fetching the metadata

Action: Verify the request URL and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19055: Unable to display a page for the requested URL {0}

Cause: The request URL was invalid, either because there was no shell handler or the shell handler could not provide a physical page to forward to.

Action: Verify the request URL and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19058: Unable to retrieve scope IDs for the current user

Cause: An internal error occurred while fetching the scope for the current user.

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19061: Unable to INSTANTIATE shell handler factory of type {0}

Cause: Shell handler factory of type {0} was not in the classpath.

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19062: Unable to INITIALIZE the shell handler factory

Cause: An internal error occurred while initializing the shell handler factory.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19066: Unable to set up the default shell handler factory.

Cause: An internal error occurred while setting up the default shell handler factory.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19067: Unable to navigate to the newly created page

Cause: An error occurred trying to reference the newly created page (the page may not have been created properly).

Action: Try to selecting the new page from the pages dropdown list. If the page is not listed, try creating the page again
Level: 1

Type: ERROR

Impact: Other

WCS-19068: Unable to create page in the current scope

Cause: An unexpected error occurred while trying to create a page in a scope.

Action: Ask your WebCenter administrator to resolve the issue.
Level: 1

Type: ERROR

Impact: Other

WCS-19070: Unable to delete page {0} ({1})

Cause: An attempt to delete a page failed. Either the page and/or its associated files (for example, ADFm page definition) have been modified but not saved

Action: Verify that the page is not being modified and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19071: Page {0} ({1}) not deleted properly. Unable to remove associated metadata.

Cause: An attempt was made to delete a page when metadata associated with the page was in use.

Action: Try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19072: Unable to retrieve the list of users

Cause: An attempt to retrieve the user list failed.Either the Identity store was corrupt or is inaccessible.

Action: Verify that the identity store is valid and accessible, and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19073: Unable to register page {0} (of scope {1}) for navigation

Cause: An error occurred while registering the page {0}.

Action: Try to register the page again and if unsuccessful contact Oracle Support.
Level: 1

Type: WARNING

Impact: Other

WCS-19075: No users available

Cause: No users found in the WebCenter Spaces identity store.

Action: Contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

WCS-19077: Permission class {0} does not have proper constructor method

Cause: The specified class does not have the required constructor

Action: Provide the required constructor in the specified class
Level: 1

Type: ERROR

Impact: Other

WCS-19079: Unable to process the security extension metadata

Cause: The argument is not an instance of ExtensionPermissionMetadata

Action: Provide an instance of ExtensionPermissionMetadata as the argument
Level: 1

Type: ERROR

Impact: Other

WCS-19080: Unable to access permission class {0} in your project libraries

Cause: Either the specified permission class does not exist or it is not in the correct location.

Action: Ensure that the specified permission class is in the correct location.
Level: 1

Type: ERROR

Impact: Other

WCS-19082: Unable to load up the {0} service.

Cause: An internal error occurred and the {0} service failed to load.

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19083: Access to permission class {0} is not allowed

Cause: An attempt was made to access the specified permission class.Permission class {0} is not accessible.

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19084: Permission class{0} can not be instantiated

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19085: Unable to instantiate the policy store for WebCenter Spaces

Cause: An error occurred while trying to access the WebCenter Spaces policy store.

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19088: Failed to register application management beans

Cause: Application management beans(MBean) registration failed.Either there are issues with OC4J or the application was not packaged properly.

Action: Restart OC4J or examine OC4J log files for further details.
Level: 1

Type: ERROR

Impact: Other

WCS-19089: Failed to unregister application management beans

Cause: Application management beans(MBean) unregistration failed. Either the Mbeans were not registered or the Mbeans were already unregistered.

Action: Examine the OC4J log files for further details.
Level: 1

Type: ERROR

Impact: Other

WCS-19090: Unable to complete the export process

Cause: The export process failed due to an internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19101: Unable to save the export archive on the local file system due to an unexpected error.

Cause: Unexpected error occurred while saving the export archive on the local file system.

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19102: Unexpected error occurred while exporting the security policy. Unable to export the policy store.

Cause: An unexpected error occurred while exporting policy store metadata to the local file system.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19104: Unable to export connection details for external application with ID {0}

Cause: An internal error occurred. Unable to retrieve details for an external Application appearing in the Oracle WebCenter Spaces provides an open architecture to many different identity stores. Applications pane in the Sidebar

Action: Ask your WebCenter administrator to clean up external applications appearing in the Sidebar or reconfigure the external application connection using Enterprise Manager.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19105: Unable to find connection details for external application with ID {0}

Cause: No connection details found for external application with the specified ID.

Action: Remove the external application link associated with the specified ID from the Applications pane in the Sidebar.
Level: 1

Type: WARNING

Impact: Other

WCS-19106: Unable to save preference settings

Cause: An error occurred while attempting to save preferences settings to the metadata store.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19107: Invalid date format {0} retrieved from the preference store.

Cause: An attempt was made to retrieve date information but the source date format was invalid.

Action: Verify whether the date format source returns the correct date format.
Level: 1

Type: WARNING

Impact: Other

WCS-19108: Invalid time format {0} retrieved from the preference store.

Cause: An attempt was made to retrieve time information but the source time format was invalid.

Action: Verify whether the time format source returns the correct time format
Level: 1

Type: WARNING

Impact: Other

WCS-19109: Unable to find service.

Cause: Unable to find the service metadata in the Oracle WebCenter Framework

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19119: Unable to add the new link : {0}

Cause: An attempt to add a new link {0} to the metadata store failed.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19120: Unable to add link as no proper handler found for the selected resource type

Cause: An attempt to add a new link but the resource being added is neither a task flow or an external application.

Action: Only task flows or external application link can be included.
Level: 1

Type: ERROR

Impact: Other

WCS-19121: Unable to retrieve the shell configuration metadata

Cause: The metadata file is corrupt or missing.

Action: Ensure that the file exists and complies with the schema.Alternatively, contact your WebCenter administrator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-19122: Invalid shell panel name

Cause: The shell panel name was probably NULL.

Action: Provide a valid shell panel name.
Level: 1

Type: ERROR

Impact: Other

WCS-19123: Unable to retrieve the shell handler for the current request {1}

Cause: The shell handler was not set for the current request

Action: Verify the URL and that the WebCenter shell filter is configured to handle requests of this kind
Level: 1

Type: WARNING

Impact: Other

WCS-19124: Unable to save changes to shell metadata

Cause: An error occurred while saving the shell metadata document.

Action: Ensure that the shell metadata document is not corrupt and is writeable and personalizeable.
Level: 1

Type: ERROR

Impact: Other

WCS-19125: Account for user {0} is disabled

Cause: The account for user {0} account is disabled.

Action: Ask the WebCenter administrator to activate the account.
Level: 1

Type: ERROR

Impact: Other

WCS-19126: Account for user {0} is inactive

Cause: The account for user {0} is disabled.

Action: Ask the WebCenter administrator to activate the account.
Level: 1

Type: ERROR

Impact: Other

WCS-19127: The account for user {0} is locked

Cause: The account is locked for user {0}

Action: Ask the WebCenter administrator to unlock the account.
Level: 1

Type: ERROR

Impact: Other

WCS-19128: Password has expired for user account {0}

Cause: Password for this user has expired

Action: Contact the WebCenter administrator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-19129: Incorrect Old Password for user account {0}

Cause: The old password specified for this user is not correct.

Action: Enter the correct password
Level: 1

Type: ERROR

Impact: Other

WCS-19130: Password for user account {0} is null

Cause: No password was specified.

Action: Enter a valid password.
Level: 1

Type: ERROR

Impact: Other

WCS-19131: Error occurred granting permissions to user {0} for the newly created page {1}

Cause: An unexpected error occurred while granting the user permission

Action: Contact the WebCenter administrator
Level: 1

Type: WARNING

Impact: Other

WCS-19132: Unable to retrieve the permission target for page {0}

Cause: An unexpected error occurred. The ADFm page definition of the page may be missing

Action: Ensure that the page definition exists and is valid.
Level: 1

Type: WARNING

Impact: Other

WCS-19133: Unable to determine the tab in focus

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

WCS-19134: Unable to hide a tab, locked by another user

Cause: An attempt was made to hide a tab that is currently locked by another user.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19135: No tab selected for hiding

Cause: Unable to determine which tab has focus.

Action: Select the tab you want to hide and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19136: Unable to hide the tab.

Cause: An attempt was made to hide the last open tab.

Action: Open some other tab and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19137: Unable to determine the tab focus for hiding

Cause: Unable to determine which tab has focus.

Action: Select the tab you want to hide and try again. Alternatively, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19138: Unable to encode the value {1} of parameter {0} using encoding format {2}

Cause: The encoding format was unexpectedly invalid.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19139: Unable to decode the value {1} of parameter {0} using encoding format {2}

Cause: The encoding format was unexpectedly invalid.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19140: Unable to update the page titled {0} ({1})

Cause: An error occurred while saving the changes.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19141: Unable to save changes to the metadata store

Cause: An error occurred while saving the changes.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19142: Role mapping SPIs are throwing exception

Cause: An internal occurred error while accessing role mapping SPIs.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19143: Unable to retrieve the catalog for adding applications

Cause: An attempt to access the external application catalog failed. Either the external application catalog is not configured or configuration details are unavailable.

Action: Check whether the ext-app-catalog attribute is configured in webcenter-config.xml
Level: 1

Type: ERROR

Impact: Other

WCS-19144: Role name for user account is null or contains invalid characters

Cause: Either the role name was left blank or the role name contained invalid characters.

Action: Enter a valid role name.
Level: 1

Type: ERROR

Impact: Other

WCS-19145: Operation succeeded with errors. The mapping of roles failed

Cause: Changes in services failed due to the following errors

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19146: Grant role completed with errors The mapping of roles failed in scope {0}

Cause: Changes in services failed due to the following errors

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19147: Page path can not be null

Cause: The specified page path is null or an empty string.

Action: Provide a valid string for the page path.
Level: 1

Type: ERROR

Impact: Other

WCS-19148: Cannot get the service categories metadata from the application metadata

Cause: Service category metadata has not been defined in the application metadata

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19149: Cannot get metadata for all services from the application metadata.

Cause: All service metadata has not been defined in the application metadata.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19150: Cannot get metadata for configurable services from the application metadata

Cause: Metadata for configurable services has not been defined in the application metadata.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19151: Cannot find a service with the ID {0}

Cause: No definition exists for a service with the specified service identifier

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19152: User {0} already has access.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19153: Edit the user to modify his role.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19154: This exception is due to one or more of the following exceptions -

Cause: One or more services configurations have failed.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19155: User {0} already has access or is invited.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19156: You cannot send an invite to this user as an invite has already been sent.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19157: Group space {0} may have been deleted or renamed

Cause: An attempt was made to access a group space that has been deleted or renamed.

Action: Contact the group space moderator or try searching for the group spaces.
Level: 1

Type: ERROR

Impact: Other

WCS-19158: Cannot personalize visibility of page {0} in group space {1}

Cause: A personalization attempt failed. Either the backing store could not be accessed or some other personalization operation was performed simultaneously.

Action: Try the operation again. If the problem persists, contact your WebCenter administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19159: Unable to save page creation

Cause: An attempt to save the new page failed. Either the back-end store could not be accessed or another page was created simultaneously.

Action: Try the operation again. If the problem persists, contact your WebCenter administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19160: Unable to save the personal sequence of pages in scope {0}

Cause: An attempt to personalize the page sequence failed. Either the back-end store could not be accessed or some other personalization operation was performed simultaneously

Action: Try the operation again. If the problem persists, contact your WebCenter administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19161: Unable to save the change in sequence of pages in scope {0}

Cause: An attempt to change page sequence failed. Either the back-end store could not be accessed or a similar operation was performed simultaneously.

Action: Try the operation again. If the problem persists, contact your WebCenter administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19162: Revoke role completed with errors The mapping of roles failed

Cause: Changes in services failed due to the following errors

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19163: Scope is NULL for Security Manager

Cause: Scope identifier passed to the security manager is NULL.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19164: The security policy in the archive file was found to be invalid.

Cause: The imported security policy file was found to be invalid.

Action: Export the data again and try the import operation again.
Level: 1

Type: WARNING

Impact: Other

WCS-19165: The security policy in the archive file to be imported is invalid as it contains more than one jazn-policy node.

Cause: The imported security policy file is invalid as it contains more than one jazn-policy node.

Action: Export the data again the import operation again.
Level: 1

Type: WARNING

Impact: Other

WCS-19166: The security policy in the archive file to be imported is located on a read-only file system and this means the data cannot be updated.

Cause: The imported security policy file is located on a read-only file system and this means the data cannot be updated.

Action: Export the data again and try the import operation again.
Level: 1

Type: WARNING

Impact: Other

WCS-19167: Failed to import security configuration from the selected archive.

Cause: An unexpected error occurred while updating the deployed application in the import source archive.

Action: Check the logs for details of the error.Alternatively, contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

WCS-19168: Role {0} is created successfully but failed to copy the permissions from role {1}. The role {1} is not found.

Cause: An attempt to create the role failed because the base role was not found.

Action: Check whether the base role is still available.
Level: 1

Type: ERROR

Impact: Other

WCS-19169: An error occurred while trying to remove a role {0} from the policy store.

Cause: The specified role does not exist in the policy store.

Action: Check the details of the error and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19170: Application role {0} still used in the policy store

Cause: The specified role is in use.

Action: Remove the usage of the role and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19171: Application role {0} to be granted is not found

Cause: Specified role was not found.

Action: Check the role name {0} and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19172: Internal error while creating security manager for WebCenter Space {0}

Cause: Unable to resolve the Scope GUID for Scope {0}

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19173: New passwords for user account {0} do not match

Cause: Passwords were entered incorrectly.

Action: Enter the correct passwords.
Level: 1

Type: ERROR

Impact: Other

WCS-19174: Few of the mandatory resource(s) are in use. Please try again later.

Cause: The lock, client is trying to release is already locked.

Action: Try after some time
Level: 1

Type: ERROR

Impact: Other

WCS-19175: Unable to release the lock on document {0}

Cause: A call to release lock in the back-end has failed.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19176: Releasing the current lock on {0} failed

Cause: The lock, client is trying to release is already released.

Action: Acquire the lock again to release.
Level: 1

Type: ERROR

Impact: Other

WCS-19177: Name Cannot Be Null

Cause: Name Cannot Be Null

Action: Enter a User or Group
Level: 1

Type: WARNING

Impact: Other

WCS-19178: User Not Found

Cause: User Not Found

Action: Enter a username
Level: 1

Type: WARNING

Impact: Other

WCS-19179: Role Not Found

Cause: Group Not Found

Action: Enter a Group
Level: 1

Type: WARNING

Impact: Other

WCS-19180: User with this name doesn't exist

Cause: User with this name doesn't exist

Action: Enter a role which has users
Level: 1

Type: WARNING

Impact: Other

WCS-19181: Unable to read the application configuration metadata

Cause: The metadata file could have got corrupt or removed

Action: Please ensure that the file exists and complies with the schema, or contact the administrator for assistance
Level: 1

Type: ERROR

Impact: Other

WCS-19182: Unable to move link/folder

Cause: The metadata file could have got corrupt or removed

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

WCS-19183: Unable to create folder {0}

Cause: The metadata file could have got corrupt or removed

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

WCS-19184: Unable to delete link/folder {0}

Cause: The metadata file could have got corrupt or removed

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

WCS-19185: Role cannot be created because it contains special characters or whitespace

Cause: Creation of Role {0} failed because it contains special characters or whitespace

Action: Remove special characters used in your role, also remove any whitespace and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19186: Role {0} cannot be created, as the role of same name exists in the policy store

Cause: Creation of Role {0} failed because policy store already contains a role of same name

Action: Try changing role name
Level: 1

Type: ERROR

Impact: Other

WCS-19187: Granting of Role {0} partially succeeded for identity {1}. Granting permissions for {2} failed. You can take actions regarding these warnings in group space settings.

Cause: Granting of Role for certain Services failed due to RoleMapping Exception

Action: Please check the log for actual error stack.
Level: 1

Type: ERROR

Impact: Other

WCS-19188: Revoking of Role {0} partially succeeded for identity {1}. Revoking permissions for {2} failed. You can take actions regarding these warnings in group space settings.

Cause: revoking of Role for certain Services failed due to RoleMapping Exception

Action: Please check the log for actual error stack.
Level: 1

Type: ERROR

Impact: Other

WCS-19189: Mapping the permissions {0} failed. You may want to try the operation again after some time or can contact Administrator.

Cause: Granting of Role for certain Services failed due to RoleMapping Exception

Action: Please check the log for actual error stack.
Level: 1

Type: ERROR

Impact: Other

WCS-19190: Fatal Error while granting role for certain services.

Cause: Granting of Role for certain Services failed due to RoleMapping Exception

Action: Please check the log for actual error stack.
Level: 1

Type: ERROR

Impact: Other

WCS-19191: Current User / Role {0} has been already granted the application role {1}.

Cause: Current User / Role {0} has been already granted the application role.

Action: Don't Provision this user since it is already provisioned.
Level: 1

Type: ERROR

Impact: Other

WCS-19192: Role has been granted with errors. You might want to contact Administrator or Remove/Grant Role again.

Cause: Role was granted with errors.

Action: Contact the Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19193: Fatal Error while granting the role.

Cause: Fatal Error while granting the role.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19194: Invitations were sent out but persisting the invited users data resulted in fatal error.

Cause: Members Fatal Error while granting the role.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19195: Page {0} cannot be found in the system

Cause: The page may have been deleted or the page path is incorrect

Action: Specify a correct path to an existing page
Level: 1

Type: ERROR

Impact: Other

WCS-19196: {0} : Irresolvable error(s) occurred. You may want to contact Administrator with the error reference.

Cause: Fatal Error occurred.

Action: Contacts the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19197: {0} : Unexpected error(s) occurred. You may want to contact Administrator with the error reference.

Cause: Fatal Error occurred.

Action: Contacts the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19198: {0} : Unknown error(s) occurred. You may want to contact Administrator with the error reference.

Cause: Fatal Error occurred.

Action: Contacts the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19199: {0} : Multiple errors occurred - {1}

Cause: Fatal Error occurred.

Action: Contacts the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19200: Fatal error while removing some grants. Please contact Administrator with error reference.

Cause: Fatal Error occurred.

Action: Contacts the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19201: Fatal error while removing the role. Please contact Administrator with error reference.

Cause: Fatal Error occurred.

Action: Contacts the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19202: Revoking role was partially successful. You can try this operation again after some time or contact Administrator.

Cause: Fatal Error occurred.

Action: Contacts the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19203: Fatal error while creating the role. Please contact Administrator with error reference.

Cause: Fatal Error occurred.

Action: Contacts the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19204: Unable to save Invite message for group space {0} due to unknown errors. Please try later or contact administrator

Cause: Error occurred while obtaining the invite message

Action: Try later or contact administrator
Level: 1

Type: ERROR

Impact: Other

WCS-19205: Unable to save member changes for a group space{0} due to unknown errors. Please try later or contact administrator

Cause: Error occurred while saving the member changes

Action: Try later or contact administrator
Level: 1

Type: ERROR

Impact: Other

WCS-19206: Could not find security policy in the archive file being imported.

Cause: The security policy file was not found in import archive.

Action: Export the data again and try the import operation again.
Level: 1

Type: ERROR

Impact: Other

WCS-19207: One or more mandatory roles are not found in the copied instance for scope {0}. Role Name: {1}

Cause: One or more mandatory roles are not found in the copied instance.

Action: Add the mandatory role {1} in the security metadata to get the webcenter functionality or contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19208: Deletion of security metadata failed for scope {0}

Cause: Deletion of roles for the current scope {0} has failed.

Action: Try later or contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19209: An unexpected error occurred while trying to upload WebCenter logo to path {0}

Cause: MDS StreamedObject creation failed for WebCenter logo

Action: Contact administrator for further assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-19210: The image upload failed as the image file you tried to upload was invalid. Provide a valid image file.

Cause: Unable to upload the WebCenter logo as the file is null or not available.

Action: Upload a valid image file
Level: 1

Type: ERROR

Impact: Other

WCS-19211: An error occurred while trying to retrieve the templates to be used for page creation. Please contact Administrator with error reference.

Cause: An unexpected error occurred.

Action: Contacts the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19212: An error occurred while trying to determine the template selected for page creation. Please contact Administrator with error reference.

Cause: An unexpected error occurred.

Action: Contacts the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19213: Unable to persist customization for tag with webcenterId ''{0}'' in the Personal Sidebar

Cause: An error saving customizations on the Personal Sidebar JSPX, or the tag with this webcenterId could not be located.

Action: Ensure that the customization is enabled on the Personal Sidebar JSPX, and the tag has a unique webcenterId
Level: 1

Type: ERROR

Impact: Other

WCS-19214: Failed to get the custom page permission for pageDef {0} for action {1}

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19215: Failed to get the roles having permission {0}

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19216: Failed to get the users having permission {0}

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19217: Unable to get list of links

Cause: An error occurred while getting the list.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19218: An error occurred while saving the page default settings. The settings may not have been saved.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19219: Unexpected error occurred while deleting the page

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19220: Search for role {0} resulted in more than one result. Contact Administrator for finding out the reasons

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19221: While provisioning the services, errors were encountered for following services - {0}. Check if these services have been configured correctly.

Cause: While copying the services, errors were encountered for certain services.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19222: Unknown error in adding link to the table

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19223: Unknown error in retrieving the link information

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19224: Unknown error in updating the link information

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19225: Unknown error in deleting the link

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19226: Unable to close connection

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19227: Unexpected error occurred while restoring the page

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19228: Unexpected error occurred while creating list of tabs

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19229: Error occurred in getting the complete list of pages you can access. Please contact the administrator.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19230: Invalid page name

Cause: Invalid page name

Action: Please enter a valid page name.
Level: 1

Type: ERROR

Impact: Other

WCS-19231: Unexpected error occurred while creating the page

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19232: While provisioning the services, errors were encountered for following services - {0}. Check if these services have been configured correctly.

Cause: While provisioning the services, errors were encountered for certain services.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19233: While renaming all the provisioned services, errors were encountered for following services - {0}.

Cause: While renaming the group space, errors were encountered for certain services.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19234: While unprovisioning the services, errors were encountered for following services - {0}.

Cause: While unprovisioning the services, errors were encountered for certain services.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19235: Unknown error occurred. Please contact Administrator.

Cause: Unknown error occurred.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19236: The following service(s) are currently unavailable: {0}. If the problem persists contact your WebCenter administrator.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19237: Unable to export as could not acquire the required lock to proceed with export. The group space {0} being exported is deleted, renamed or is being exported/imported by another user. Refresh the group space list and try again.

Cause: Unable to acquire a lock on the scope of group space.

Action: Refresh the group space list and try export again. If the problem persist contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19238: Unable to export as could not acquire the required lock to proceed with export. The group space template {0} being exported is deleted, renamed or is being exported/imported by another user. Refresh the group space template list and try again.

Cause: Unable to acquire a lock on the scope of group space template.

Action: Refresh the group space template list and try export again. If the problem persist contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19239: Could not acquire the required lock to proceed with import. Group space(s) on the target application could have been deleted, renamed or are being exported/imported by another user. Refresh the group space list and try again.

Cause: Unable to acquire a global lock of group space to avoid creation, delete, rename or import of group space(s).

Action: Wait for some time and try import again. If the problem persist contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19240: Could not acquire the required lock to proceed with import. Group space template(s) on the target application could have been deleted, renamed or are being exported/imported by another user. Refresh the group space template list and try again.

Cause: Unable to acquire a global lock of group space template to avoid creation, delete, rename or import of group space template(s).

Action: Wait for some time and try import again. If the problem persist contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19241: Errors occurred in the page.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19242: Unexpected error occurred while accessing copyright message.

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19243: Unexpected error occurred while accessing privacy URL.

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19244: Unexpected error occurred while accessing footer information.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19245: An error occurred while saving the page security settings. The settings may not have been saved.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19246: Error occurred while refreshing the table of pages.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19247: Modification of role operation not supported for scope {0}

Cause: Currently the modification of role not supported.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19248: Group space {0} being exported is either online or being exported/imported by another user. Try exporting after sometime.

Cause: Group space is either online or blocked by another user/process.

Action: Refresh the group space list and try export again. If the problem persist contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19249: Group space template {0} being exported is either online or being exported/imported by another user. Try exporting after sometime.

Cause: Group space template is either online or blocked by another user/process.

Action: Refresh the group space template list and try export again. If the problem persist contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19250: Group space template {0} on the target application is either online or being exported/imported by another user. Try importing after sometime.

Cause: Group space template either online or blocked by another user/process.

Action: Wait for some time and try import again. If the problem persist contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19251: You are trying to import group space(s) with an archive file that contains group space template(s). Check the archive file and try again.

Cause: The archive file contains template(s) but attempt is to import group space(s).

Action: Use an archive file that contains group space(s) exported. Contact oracle support service for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-19252: You are trying to import group space template(s) with an archive file that contains group space(s). Check the archive file and try again.

Cause: The archive file contains group space(s) but attempt was to import group space template(s).

Action: Use an archive file that contains group space tempate(s) exported. Contact oracle support service for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-19253: Cannot locate the document ''{0}''.

Cause: The path is incorrect or it is not available in the system.

Action: Verify whether the path is correct and is available in the system.
Level: 1

Type: ERROR

Impact: Other

WCS-19254: Error occurred while reading the WebCenter environment configuration file {0}.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19255: Unexpected error occurred while navigating to Group Space Administration page.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19256: Error occurred while saving the folder.

Cause: An unexpected error occurred while saving the folder.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19257: Unexpected error occurred while acquiring the write lock on the document {0}.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19258: Error occurred while clearing the Deleted/Renamed Group Space Tab.

Cause: Error occurred while clearing the Deleted/Renamed Group Space Tab.

Action: Error occurred while clearing the Deleted/Renamed Group Space Tab.
Level: 1

Type: ERROR

Impact: Other

WCS-19259: Group space {0} on the target application is either online or being exported/imported by another user. Try importing after sometime.

Cause: Group space either online or blocked by another user/process.

Action: Wait for some time and try import again. If the problem persist contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19260: The current process could not be executed. Please try again after some time.

Cause: An unexpected error occurred while saving the WebCenter admin changes.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19261: Error occurred while saving the WebCenter Admin changes.

Cause: An unexpected error occurred while saving the WebCenterAdmin changes.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19262: The WebCenter admin settings is being modified by another administrator. Please try again after some time.

Cause: An unexpected error occurred while saving the WebCenter admin changes.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19263: Fatal error occurred while getting the roles for current scope.

Cause: An unexpected error occurred while getting the roles.

Action: Please contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19264: Fatal error occurred while inviting user {0} for role {1}

Cause: An unexpected error occurred while getting the members.

Action: Please contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19265: Fatal error occurred while getting members.

Cause: An unexpected error occurred while getting the members.

Action: Please contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19266: Fatal error occurred while getting invitation message from the repository.

Cause: An unexpected error occurred while getting message.

Action: Please contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19267: Error occurred while reading the list of tabs from persistence store.

Cause: An unexpected error occurred while reading the list of tabs.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19268: Error occurred while storing the list of tabs to persistence store.

Cause: An unexpected error occurred while storing the list of tabs.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19269: Error in processing the pages.

Cause: Unexpected error occurred while adding the tab.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19270: Error in processing the pages.

Cause: Unexpected error occurred while removing the tab.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19271: Error in processing the pages.

Cause: Unexpected error occurred while finding the tab.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19272: Error in processing the pages.

Cause: Unexpected error occurred while creating the menu model.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19273: Error in navigation.

Cause: Unexpected error occurred while navigating to secondary tab.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19274: Error in processing the pages.

Cause: Unexpected error occurred while preparing the children.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19275: Error in processing the pages.

Cause: Unexpected error occurred while preparing the tab for current request.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19276: Error in navigation.

Cause: Unexpected error occurred while getting the navigable path to the tab.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19277: An error occured while changing the page visibility. Refresh the page list and retry.

Cause: Unexpected error occurred while changing the tab's visibility.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19278: Error in renaming the page.

Cause: Unexpected error occurred while changing the page name.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19279: Error in creating a copy of the page.

Cause: Unexpected error occurred while coping the page.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19280: The role name {0} is reserved, please use some other name.

Cause: Unexpected error occurred while creating the role name.

Action: Try creating a role with some other name.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19281: Unexpected error occurred while refreshing list of pages.

Cause: Unexpected error occurred while refresh.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19282: Unable to save the BusinessRole sequence of pages.

Cause: An attempt to customize the BR page sequence failed. Either the back-end store could not be accessed or some other customization operation was performed simultaneously

Action: Try the operation again. If the problem persists, contact your WebCenter administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19283: Error in reordering the pages.

Cause: Unexpected error occurred while reordering the pages.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19284: Error in reordering the business-role pages.

Cause: Unexpected error occurred while reordering the business-role pages.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19285: Error in reordering the tabs.

Cause: Unexpected error occurred while reordering the tabs.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19286: Error in moving the page up.

Cause: Unexpected error occurred while moving the page up.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19287: Error in moving the page down.

Cause: Unexpected error occurred while moving the page down.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19288: Error in processing the pages.

Cause: Unexpected error occurred while closing the tab.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19289: Unexpected error in closing tab(s).

Cause: Unexpected error occurred while closing the tabs.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19290: Unexpected error in getting list of moderators.

Cause: Unexpected error occurred while getting the list of moderators.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19291: Unexpected error occurred in getting the page Uri for the favorites.

Cause: Unexpected error occurred while getting the Uri for the favorites.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19292: Unexpected error occurred in creating the new folder.

Cause: Unexpected error occurred while creating a new folder.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19293: Unexpected error occurred while getting the list of favorites.

Cause: Unexpected error occurred while getting the list of favorites.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19294: Unexpected error occurred while trying to navigate to bookmark.

Cause: Unexpected error occurred while trying to navigate to bookmark.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19295: Error occurred while reverting the WebCenter Admin changes.

Cause: An unexpected error occurred while reverting the WebCenterAdmin changes.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19296: The application failed to access backend data store and cannot process requests

Cause: Access to backend data store failed

Action: Ensure backend data store containing WebCenter schema and MDS schema is accessible.
Level: 1

Type: ERROR

Impact: Other

WCS-19297: The URL typed by current user is not accessible, so redirecting to the unAuthorized page

Cause: The current user does not have privileges to see the current URL

Action: Please contact system administrator
Level: 1

Type: ERROR

Impact: Other

WCS-19298: Unexpected error occurred, please retry the operation

Cause: An internal error occurred

Action: Retry the operation. Contact Oracle Support Services if the issue persists.
Level: 1

Type: ERROR

Impact: Other

WCS-19299: Unexpected error occurred while preparing the administration tabs

Cause: An internal error occurred

Action: Retry the operation. Contact Oracle Support Services if the issue persists.
Level: 1

Type: ERROR

Impact: Other

WCS-19300: Unexpected error trying to restore the Login page

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19301: Unexpected error trying to navigate to the Login page

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19302: Unexpected error trying to open the Login page for edit

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19303: Unexpected error occured while moving a page to top of the pages list

Cause: Unexpected error occured while moving a page to top of the pages list

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19304: Unexpected error occured while moving a page to bottom of the pages list

Cause: Unexpected error occured while moving a page to bottom of the pages list

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19305: Drag and drop is not allowed for ungrouped view

Cause: Drag and drop was attempted in ungrouped view

Action: Drag and drop operation is not allowed for ungrouped view
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19306: Reorder of personal pages is not allowed here

Cause: A personal page was selected as either the drag source or the drop target

Action: Exclude personal pages from drag and drop operations
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19307: Unexpected error occurred while creating mandatory document.

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19308: Failed to grant a role {1} to identity {0} in scope {2}

Cause: Failed to find identity {0} in Identity Store while Granting a role {1} in scope {2}

Action: Create a new Identity {0} in Identity Store and try again
Level: 1

Type: WARNING

Impact: Other

WCS-19309: Unexpected error retrieving services for configuration

Cause: An unexpected error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19310: Unexpected error occured while trying to retrieve list of languages

Cause: Unexpected error occured while trying to retrieve list of languages

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19311: Granting of group {0} for role {1} in scope {2} failed for the following errors : {3}

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19312: Users : {0}, failed with the errors {1}

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19313: Setting {0} role for {1} failed. Please contact Administrator

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19314: Group space template {0} being exported is seeded. Exporting seeded template is not allowed.

Cause: Group space template is seeded.

Action: Refer to export documentation or contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19315: One or more page(s) of group space {0} is being edited by user(s) {1}. Please try export later.

Cause: One or more group space page is in edit mode. Cannot export when sandbox is created.

Action: Close all the pages from edit mode or contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19316: One or more page(s) of group space {0} is being edited by user(s) {1}. Please try import later.

Cause: One or more group space page is in edit mode.

Action: Close all the pages from edit mode or contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19317: An unexpected error has occured while sending notification to the administrator.

Cause: An unexpected error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19318: Granting of Role {0} partially succeeded for identity {1}. Granting permissions for {2} failed.

Cause: Granting of Role for certain Services failed due to RoleMapping Exception

Action: Please check the log for actual error stack.
Level: 1

Type: ERROR

Impact: Other

WCS-19319: Revoking of Role {0} partially succeeded for identity {1}. Revoking permissions for {2} failed.

Cause: revoking of Role for certain Services failed due to RoleMapping Exception

Action: Please check the log for actual error stack.
Level: 1

Type: ERROR

Impact: Other

WCS-19320: File {0} in location {1} already exists. Do you want to overwrite it?

Cause: File already exists in the location where the export archive is being saved.

Action: Enter a new location or overwrite the file.
Level: 1

Type: ERROR

Impact: Other

WCS-23001: unexpected error has occurred

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26001: Search Configuration Error: {0}

Cause: A configuration error has been encountered.

Action: Refer to the error details and the documentation for how to debug this.
Level: 1

Type: ERROR

Impact: Other

WCS-26021: Invalid Query {0}.

Cause: An invalid query was sent.

Action: Query validity is dependent on the service running it. Refer to the query in the log and the documentation for the service involved to debug this.
Level: 1

Type: ERROR

Impact: Other

WCS-26022: Contradiction caused when clause "{0}" is added to "{1}"

Cause: An unexpected programming error occurred. This is not something that can be fixed.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26023: The addition of criteria to {0} existing date criterion is not supported

Cause: An unexpected programming error occurred. This is not something that can be fixed.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26041: General Search Execution Error

Cause: A general execution error has been encountered.

Action: Query execution error is dependent on the service running it. Refer to the Query in the log and the documentation for the service involved to debug this.
Level: 1

Type: ERROR

Impact: Other

WCS-26061: General Search Response Error

Cause: A general response error has been encountered.

Action: Query execution response error is dependent on the service running it. Refer to the Query in the log and the documentation for the service involved to debug this.
Level: 1

Type: ERROR

Impact: Other

WCS-26062: Query results are immutable; removing elements from it is unsupported.

Cause: A caller tried to remove an element from the result set.

Action: Inform the caller that this is not a supported function.
Level: 1

Type: ERROR

Impact: Other

WCS-26063: SQL ResultSet consumption failed with the message "{0}".

Cause: A SQL ResultSet cannot be consumed.

Action: Refer to the underlying exception to debug this.
Level: 1

Type: WARNING

Impact: Other

WCS-26064: Cannot call "remove" method before calling "next" method.

Cause: Caller tried to call "remove" method of QueryResult class before calling "next" method.

Action: Inform the caller that this is an illegal operation.
Level: 1

Type: ERROR

Impact: Other

WCS-26065: Cannot convert "{0}" value to "{1}".

Cause: The target object had no "valueOf" method to convert the source.

Action: No action is needed; appropriate contingencies have been applied.
Level: 1

Type: WARNING

Impact: Other

WCS-26066: Parameter type {0} cannot be converted into a primitive type.

Cause: The conversion failed because the bean property was not of primitive type.

Action: No action is needed; appropriate contingencies have been applied.
Level: 1

Type: WARNING

Impact: Other

WCS-26081: General Search Authentication Error

Cause: A general authentication error has been encountered.

Action: Query execution authentication error is dependent on the service running it. Refer to the Query in the log and the documentation for the service involved to debug this.
Level: 1

Type: ERROR

Impact: Other

WCS-26091: Search API Implementation error in {0} class

Cause: An implementation error has been encountered.

Action: Report to the provider of the Search API Implementation.
Level: 1

Type: ERROR

Impact: Other

WCS-26101: An error occurred while parsing an XML document at {0}.

Cause: The XML document in question may not be well-formed or valid with respect to the referred XML schema.

Action: Examine the XML document again and check the XML schema to make sure there are not any mistakes or typos.
Level: 1

Type: ERROR

Impact: Other

WCS-26102: An error occurred while parsing the search configuration in adf-config.xml at {0}.

Cause: The XML fragment within adf-config.xml may not be well-formed or valid with respect to what is expected for search configuration.

Action: Examine the adf-config.xml document again and check the documented XML schema to make sure there are not any mistakes or typos.
Level: 1

Type: ERROR

Impact: Other

WCS-26103: An unexpected XML error occurred.

Cause: Something with the underlying XML system or implementation of JAXP failed unexpectedly.

Action: Check the nested exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-26121: A general MDS error has occurred.

Cause: An MDS-related error has occurred. Something with the MDS setup is misconfigured.

Action: Check the nested exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-26122: An MDS error has occurred because a Metadata Object by the name of {0} cannot be found.

Cause: An MDS Metadata Object was not found.

Action: Check the details of the Metadata Object and check the MDS repository to confirm that it is there.
Level: 1

Type: ERROR

Impact: Other

WCS-26123: Encountered "{0}" with message "{1}" when committing MDS changes.

Cause: Something within the current MDS Session cannot be committed.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26124: Saved Search Deletion aborted because the Metadata Object (MO) Reference for ID "{0}" is not found.

Cause: The system is in an inconsistent state allowing deletion of non-existent MDS documents

Action: There is nothing to be done about this. No deletion is performed.
Level: 1

Type: WARNING

Impact: Other

WCS-26125: Encountered "{0}" with message "{1}" while formulating the final MDS Condition.

Cause: Some MDS conditions that are being joined caused a failure to come up with the final condition.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26126: MDS query result is null

Cause: MDS query result set is null. The MDS repository might be unavailable.

Action: Perform the operation again after MDS repository becomes available again.
Level: 1

Type: ERROR

Impact: Other

WCS-26141: A configuration error has occurred for the Search service model. The offending configuration is {0}.

Cause: The Search service keeps its configuration in adf-config.xml, connections.xml, and MDS.

Action: Check in the appropriate configuration files to see if there are any obvious erroneous data.
Level: 1

Type: ERROR

Impact: Other

WCS-26142: A security error has occurred for the Search service model. The offense is {0}.

Cause: The Search service model security maintained by the service caused a failure.

Action: Check the security settings for each underlying service to identify any anomalies.
Level: 1

Type: ERROR

Impact: Other

WCS-26143: Failed to commit changes to Search preferences, encountering {0}.

Cause: Some underlying MDS issues with the Preferences implementation is causing the failure.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26161: Encountered a message from MDS indicating unsupported operation while deleting a Saved Search with ID "{0}", MO Reference name "{1}", and MO Absolute Name "{2}".

Cause: The deletion of a Saved Search triggered some MDS operation that is not supported on said Saved Search document.

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26162: A saved search with name "{0}" already exists, use a different name.

Cause: The name you provided is used already.

Action: Use a different name when saving your searches.
Level: 1

Type: ERROR

Impact: Other

WCS-26163: Duplicated identifier found while adding a saved search with a identifier "{0}" with Metadata Object name "{1}"; replacing with "{2}".

Cause: The system is in an inconsistent state where an old ID is used on a new Saved Search.

Action: This is a cautionary message only. Appropriate actions will be taken to fix the uniqueness issue.
Level: 1

Type: WARNING

Impact: Other

WCS-26164: Encountered an MDS exception "{1}" with message "{2}" while querying for saved searches with condition "{0}".

Cause: An underlying MDS exception occurred during the query execution.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26165: Failed to retrieve a Saved Search in MDS with Metadata Object reference name "{0}", and absolute name "{1}".

Cause: This can be due to an MDS misconfiguration issue.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26166: Failed to retrieve most recent Saved Searches in MDS with Metadata Object reference name "{0}", and absolute name "{1}".

Cause: This can be due to an MDS misconfiguration issue.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26167: Encountered an MDS exception "{2}" with message "{3}" while saving a saved search with Metadata Object name "{0}", and absolute name "{1}".

Cause: This can be due to an MDS misconfiguration issue.

Action: Refer to MDS documentation to resolve a lookup failure with the given details.
Level: 1

Type: ERROR

Impact: Other

WCS-26168: Encountered an MDS exception "{2}" with message "{3}" while deleting a saved search with Metadata Object name "{0}", and absolute name "{1}".

Cause: An underlying MDS exception caused this.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26169: Encountered an MDS reference exception "{1}" with message "{2}" while retrieving Saved Search Metadata Object reference in MDS with Metadata Object absolute name "{0}".

Cause: An underlying MDS exception caused this.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26170: Saved Search Update aborted because the Metadata Object (MO) Reference for ID "{0}" is not found.

Cause: This can be due to an MDS misconfiguration issue.

Action: Refer to MDS documentation to resolve a lookup failure with the given details.
Level: 1

Type: WARNING

Impact: Other

WCS-26171: Encountered an MDS exception "{1}" with message "{2}" while creating a document with Metadata Object absolute name "{0}".

Cause: An underlying MDS exception caused this.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26181: Failed to retrieve UI Metadata in MDS with Metadata Object reference name "{0}", and absolute name "{1}".

Cause: This can be due to an MDS misconfiguration issue.

Action: Refer to MDS documentation to resolve a lookup failure with the given details.
Level: 1

Type: WARNING

Impact: Other

WCS-26182: Encountered an MDS exception "{2}" with message "{3}" while adding a UI Metadata with identifier "{0}" and Metadata Object name "{1}".

Cause: An underlying MDS exception caused this.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26183: Encountered an MDS exception "{1}" with message "{2}" while querying for UI Metadata with condition "{0}".

Cause: An underlying MDS exception caused this.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26184: Encountered an MDS reference exception "{1}" with message "{2}" while looking up UI Metadata Object reference in MDS with Metadata Object absolute name "{0}".

Cause: An underlying MDS exception caused this.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26185: Encountered an MDS exception "{0}" with message "{1}" while creating default service list in MDS.

Cause: An underlying MDS exception occurred during the creation of the service list in the Search UI Metadata.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26186: Encountered an MDS exception "{1}" with message "{2}" while updating UI Metadata Object in MDS with Metadata Object absolute name "{0}".

Cause: An underlying MDS exception occurred during the update of the the Search UI Metadata.

Action: The update by this user will be lost. Refresh the page and continue.
Level: 1

Type: ERROR

Impact: Other

WCS-26201: Encountered "{2}" with message "{3}" when loading QueryManager Class "{0}" for service "{1}" in Extension Handler.

Cause: Any one of the possible exceptions resulting from loading a class using reflection occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26202: Search Extension Registry loading failed, encountering "{0}" with message "{1}".

Cause: There may be misconfiguration in the adf-config.xml file.

Action: Check your adf-config.xml to see if the Search extension registry is declared. Make sure that the version numbers match those specified in the documentation.
Level: 1

Type: ERROR

Impact: Other

WCS-26203: Cannot access children, encountering "{0}" with message "{1}".

Cause: Encountered a Search exception when trying to extract children executors from a Query Federator

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26204: Failed in creating a Row QueryHandler for "{0}", encountering "{1}" with message "{2}".

Cause: A run time or Search exception was encountered. This can be due to the creation process timing out or any service-specific creation failure.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26205: {0} occurred during the preparation of Query Handler with identifier "{1}".

Cause: The Query Handlers are prepared in parallel; the preparation failed because of underlying concurrency mechanism.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26206: Creation of Row QueryHandler did not complete within the time limit for executor {0}.

Cause: The time allowed to create a Row QueryHandler is not sufficient.

Action: If this problem is persistent, increase the value of prepareExecutionTimeoutMs parameter in adf-search-config section of adf-config.xml file.
Level: 1

Type: WARNING

Impact: Other

WCS-26221: Search execution was interrupted because of "{0}" with message "{1}".

Cause: The service search execution was interrupted because of a timeout of a failure.

Action: Examine the log to determine the root cause and take appropriate debugging steps.
Level: 1

Type: ERROR

Impact: Other

WCS-26222: Search execution failure for service "{0}", encountering "{1}" with message "{2}".

Cause: An exception occurred while executing search.

Action: Examine the log to determine the root cause and take appropriate debugging steps.
Level: 1

Type: ERROR

Impact: Other

WCS-26223: Search executors not initialized due to null Query.

Cause: Query is not set so no Query Executors have been initialized.

Action: No action is necessary; this is just a diagnostic message.
Level: 1

Type: WARNING

Impact: Other

WCS-26224: Query Handler creation of {0} was interrupted.

Cause: The Query Handler named took too long to be created and was timed out.

Action: Increase your prepareTimeoutMs value in the search-config section of the adf-config.xml file
Level: 1

Type: WARNING

Impact: Other

WCS-26321: {0} occurred during Search result transfer of service with identifier "{1}"

Cause: An unexpected exception occurred when transferring search results after execution.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26322: Skipping consumption of a Date ComplexPredicate with 1 child because its type {0} is not AttributePredicate<Calendar> as expected.

Cause: A Date ComplexPredicate was passed down from the query that contains the wrong type for its single child.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26323: Skipping consumption of a Date ComplexPredicate with 2 children because their types {0} and {1} are not AttributePredicate<Calendar> as expected.

Cause: A Date ComplexPredicate was passed down from the query that contains the wrong type for both its children.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26324: Skipping consumption of a Date ComplexPredicate with {0} children because we only support at most two.

Cause: Too many children are passed down the Date ComplexPredicate when we can only handle two.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26325: Execution of the search query to show all rows did not complete within the time limit for executor {0}.

Cause: The time allowed to execute the search query to show all rows is not sufficient.

Action: Increase the value of showAllExecutionTimeoutMs parameter in adf-search-config section of adf-config.xml file.
Level: 1

Type: ERROR

Impact: Other

WCS-26326: Execution of the search query did not complete within the time limit for executor {0}.

Cause: The time allowed to execute the search query is not sufficient.

Action: If this problem is persistent, increase the value of executionTimeoutMs parameter in adf-search-config section of adf-config.xml file.
Level: 1

Type: WARNING

Impact: Other

WCS-26327: Query execution failed for {0}.

Cause: Query execution failed.

Action: Examine the log files to extract the root cause to identify the proper debugging steps.
Level: 1

Type: WARNING

Impact: Other

WCS-26341: Search UI Metadata Lookup Failed: {0}

Cause: The UI Metadata document necessary for rendering Search views could not be found.

Action: Refer to the error messages presented in the dialog box and act accordingly.
Level: 1

Type: ERROR

Impact: Other

WCS-26342: Search UI Metadata Update Failed: {0}

Cause: The UI Metadata document necessary for rendering Search views could not be updated (customized).

Action: Refer to the error messages presented in the dialog box and act accordingly.
Level: 1

Type: ERROR

Impact: Other

WCS-26343: Search Options Update Failed

Cause: An MDS error caused the update of search options to fail.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26361: Failed to update the last used date / time of saved search with ID "{0}".

Cause: An MDS error caused the update of the Saved Search document to fail when updating the last accessed date.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26362: Saved Search Update Failed

Cause: An error occurred when trying to update a Saved Search.

Action: Refer to the error messages presented in the dialog box and act accordingly.
Level: 1

Type: ERROR

Impact: Other

WCS-26363: Saved Search Creation Failed

Cause: An error occurred when trying to create a Saved Search.

Action: Refer to the error messages presented in the dialog box and act accordingly.
Level: 1

Type: ERROR

Impact: Other

WCS-26364: Saved Search Deletion Failed

Cause: An error occurred when trying to delete a Saved Search.

Action: Refer to the error messages presented in the dialog box and act accordingly.
Level: 1

Type: ERROR

Impact: Other

WCS-26365: Failed to delete saved search with ID "{0}".

Cause: An MDS error caused the deletion of the Saved Search document to fail.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26366: Failed to update the sharing setting of saved search with ID "{0}".

Cause: An MDS error caused the update of the Saved Search document to fail when updating the sharing setting.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26367: Saved search with ID "{0}" could not be found.

Cause: Saved search was deleted by another user.

Action: Refresh page to get updated list of saved searches.
Level: 1

Type: WARNING

Impact: Other

WCS-26381: Resource ID is not available to show the resource.

Cause: A link to render a resource did not carry the unique identifier for that resource and therefore could not perform the rendering.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26391: Encountered an exception "{2}" with message "{3}" while populating Data Flavor "{0}" of "{1}" class.

Cause: Failed to populate the given Data Flavor in the Resource Catalog Adapter.

Action: Examine the log for the root cause and take appropriate debugging steps.
Level: 1

Type: WARNING

Impact: Other

WCS-26392: Failed to initialize Search service context DirContext Schema with message "{0}"

Cause: A naming exception was encountered when binding attributes while initializing the Resource Catalog schema for the Search service.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26393: Failed to get attributes of resource "{0}"

Cause: Failed to get attributes of a given resource.

Action: Examine the log for the root cause and take appropriate debugging steps.
Level: 1

Type: WARNING

Impact: Other

WCS-26401: Encountered "{0}" during proxy login with application entity "{1}" to Oracle SES at [{2}], as search user "{3}".

Cause: The proxy login operation encountered error. Some underlying exception is causing the error.

Action: Refer to the root exception and identify the proper debugging steps.
Level: 1

Type: ERROR

Impact: Other

WCS-26402: Received status "{0}" during proxy login with application entity "{1}" to Oracle SES at [{2}], as search user "{3}". Defaulting to public.

Cause: The application entity may not have been provisioned in the identity management system used by SES, or its password may have been expired.

Action: Log on to the Oracle SES administration tool and make sure that the application entity has been provisioned. Then make sure that the account is enabled on the identity management system and has not expired.
Level: 1

Type: WARNING

Impact: Other

WCS-26421: Failed to initialize data group ID from {0} in {1}, encountering {2}

Cause: Either the group ID in question does not exist or SES is down.

Action: Make sure that SES is up and check the group IDs present on SES.
Level: 1

Type: WARNING

Impact: Other

WCS-26422: Failed to discover attributes from {0} in {1}, encountering {2}

Cause: Some underlying exception is causing the discovery of attributes from SES to fail.

Action: Refer to the root exception and identify the proper debugging steps.
Level: 1

Type: WARNING

Impact: Other

WCS-26423: No attributes discovered from {0} in {1}

Cause: The SES instance in question does not offer any attributes to query on.

Action: Confirm that Oracle SES is up.
Level: 1

Type: WARNING

Impact: Other

WCS-26424: Failed to discover info source nodes from {0} in {1}, encountering {2}

Cause: Some underlying exception is causing the discovery of info source nodes of SES to fail.

Action: Refer to the root exception and identify the proper debugging steps.
Level: 1

Type: WARNING

Impact: Other

WCS-26441: Retrieving the SES Reference failed with Connection Architecture

Cause: Something occurred when getReference of the SesReferenceable is called.

Action: Refer to the root exception and identify the proper debugging steps.
Level: 1

Type: WARNING

Impact: Other

WCS-26442: Looking up the SES Connection failed with Connection Architecture

Cause: Encountered a JCA ResourceException when calling getConnection on the connection factory for Searchlets.

Action: Refer to the root exception and identify the proper debugging steps.
Level: 1

Type: WARNING

Impact: Other

WCS-26443: Connection entry "{0}" not found

Cause: The specified connection entry is not in connections.xml

Action: Add the specified connection entry to connections.xml
Level: 1

Type: ERROR

Impact: Other

WCS-26444: Invalid value for addrType attribute in "{1}" entry. Expected value is "{0}"

Cause: Incorrect value for addrType attribute found in connections.xml

Action: Update connections.xml with the correct value for addrType attribute
Level: 1

Type: ERROR

Impact: Other

WCS-26461: Failed to marshal SES Filter for Advanced Search due to JAXB issues - {0}

Cause: A JAXB problem has caused the marshalling of an SES filter before sending it to SES for execution.

Action: Examine the log to look at the XML structure to verify validity.
Level: 1

Type: WARNING

Impact: Other

WCS-26462: SES Search Execution failed, encountering "{1}" with message "{2}".

Cause: The cause is embedded in the Exception and can be SES-specific.

Action: Examine the log files to extract the root cause to identify the proper debugging steps.
Level: 1

Type: ERROR

Impact: Other

WCS-26463: Can not convert SES Result Element value from {0} to {1}

Cause: Conversion from SES Result Element value failed.

Action: No action is needed. The conversion will default to using String
Level: 1

Type: WARNING

Impact: Other

WCS-26464: Cannot find attribute mapping for column {0}

Cause: You have specified a column ID that cannot be found in the list of SES attributes.

Action: Examine your SES installation and make sure the attribute has a valid column ID.
Level: 1

Type: WARNING

Impact: Other

WCS-26465: Failed to create JAXBContext using package {0}

Cause: A JAXBContext instance could not be created for the SES cluster deserializer.

Action: Make sure that the required files can be found in the specified package and that the required classes can be loaded from the classpath.
Level: 1

Type: ERROR

Impact: Other

WCS-26466: Failed to unmarshal byte stream into Cluster

Cause: Unmarshalling failed because a JAXBContext instance could not be obtained.

Action: Make sure that the required files can be found in the specified package and that the required classes can be loaded from the classpath.
Level: 1

Type: WARNING

Impact: Other

WCS-26501: Creation of the Tags service failed.

Cause: The Tags service is loaded by reflection. Something may have happened to cause that to fail.

Action: Check whether the class name logged is accessible through the class path of the WebCenter Web application.
Level: 1

Type: ERROR

Impact: Other

WCS-26502: Query Federator for the Tags service not created because a Tags Service cannot be created.

Cause: The creation of the Tags service was unsuccessful causing the subsequent creation of a Row Query Federator for Tagging to fail.

Action: Check for /META-INF/tagging-class-config.properties and verify that a correct accessible class is specified.
Level: 1

Type: ERROR

Impact: Other

WCS-26503: findSystemResources failed because of invalid arguments passed in to the method: keywords ({0}).

Cause: One of the input arguments to findSystemResources was invalid.

Action: Make sure that arguments passed in to findSystemResources are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26504: findSystemTags failed because of invalid arguments passed in to the method: keywords ({0}).

Cause: One of the input arguments to findSystemResources was invalid.

Action: Make sure that arguments passed in to findSystemTags are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26505: lookupTag failed because of invalid arguments passed in to the method: tagName ({0}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26506: findFilteredPersonalTags failed because of invalid arguments passed in to the method: userId ({0}), filter ({1}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26507: findTopFilteredSystemTags failed because of invalid arguments passed in to the method:userId({0}), filter ({1}), count({2}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26508: findTopFilteredPersonalTags failed because of invalid arguments passed in to the method: userId ({0}), filter ({1}), count({3}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26509: findAllTopFilteredSystemTags failed because of invalid arguments passed in to the method:userId({0}), filter({1}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26510: findAllTopFilteredPersonalTags failed because of invalid arguments passed in to the method: userId ({0}), filter ({1}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26511: findSystemTags failed because of invalid arguments passed in to the method: userId ({0}), filter ({1}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26512: findRelatedSystemTagsByTag failed because of invalid arguments passed in to the method: userId ({0}), tagWords ({1}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26513: findRelatedSystemTags failed because of invalid arguments passed in to the method: serviceId ({0}), resourceId({1}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26514: findRecommendedTags failed because of invalid arguments passed in to the method: serviceId ({0}), resourceId ({1}), userId ({2}), count ({3}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26515: deleteTag failed because of invalid arguments passed in to the method: tag ({0}).

Cause: One of the input arguments is invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26516: deletePersonalTags failed because of invalid arguments passed in to the method: userId ({0}), tagWord ({1}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26517: renamePersonalTags failed because of invalid arguments passed in to the method: userId ({0}), oldTagWord ({1}) newTagWord({2}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26518: renamePersonalTags failed because of invalid arguments passed in to the method: userId ({0}), tagWord ({1}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26519: getTagsByName failed because of invalid arguments passed in to the method: userId ({0}), tagWord ({1}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26520: lookupResource failed because of invalid arguments passed in to the method: serviceId ({0}), resourceId({1}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26521: createNewResource failed because of invalid arguments passed in to the method: serviceId ({0}), resourceId ({1}), resource name ({2}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26522: findFilteredPersonalResource failed because of invalid arguments passed in to the method: userId ({0}), filter ({1}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26523: findSystemResources failed because of invalid arguments passed in to the method: userId ({0}), userFilters ({1}), tagFilters ({2}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26524: findPersonalResources failed because of invalid arguments passed in to the method: userId ({0}), userFilters ({1}), tagFilters ({2}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26525: findRelatedSystemResources failed because of invalid arguments passed in to the method: serviceId ({0}), resourceId ({1}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26526: findRelatedUsers failed because of invalid arguments passed in to the method: serviceId ({0}), resourceId ({1}).

Cause: One of the input arguments is invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26527: findRelatedUsersByTag failed because of invalid arguments passed in to the method: userId({0}), tagWords ({1}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26528: createNewBookmark failed because of invalid arguments passed in to the method: userId ({0}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26529: lookupBookmark failed because of invalid arguments passed in to the method: serviceId ({0}), resourceId ({1}, userId ({2}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26530: saveBookmark failed because of invalid arguments passed in to the method: bookmark ({0}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26531: deleteBookmark failed because of invalid arguments passed in to the method: bookmark ({0}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26532: A bookmark has been updated at the same time.

Cause: There was a concurrent update on the bookmarks.

Action: Ask user to retry the operation.
Level: 1

Type: ERROR

Impact: Other

WCS-26533: A database exception was thrown (for example., Unique Key constraint violation error).

Cause: Tried to insert a duplicate object.

Action: Retry the action.
Level: 1

Type: ERROR

Impact: Other

WCS-26534: Resource can not be displayed because the service with ID {0} is not found in the Service Registry.

Cause: Service definition is not found in Service Registry.

Action: Please register the service in Service Registry
Level: 1

Type: ERROR

Impact: Other

WCS-26535: Tags service is not available due to {0}.

Cause: Check the cause specified in the message.

Action: Act appropriately to reverse the cause.
Level: 1

Type: ERROR

Impact: Other

WCS-26536: Resource can not be displayed because the authorizerClass {0} is not found.

Cause: Class specified by authorizerClass is not found.

Action: Check the class path of the application to verify inclusion of the authorizerClass.
Level: 1

Type: WARNING

Impact: Other

WCS-26537: findPopularTags failed because of invalid arguments passed in to the method: userId ({0}), order ({1}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26538: findPopularTags failed because of invalid arguments passed in to the method: userId ({0}), serviceId ({1}), resourceId ({2}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26539: findUpdatedResources failed because of invalid arguments passed in to the method: serviceId ({0}), date ({1})).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26601: No service ID or resource ID - cannot perform {0}.

Cause: The consumption of the EditBookmarkBean from the view layer did not pass in the service or the resource IDs necessary.

Action: Check the view layer to make sure that the resourceId and the serviceId parameters are passed into the page flow scope.
Level: 1

Type: ERROR

Impact: Other

WCS-26602: Cannot create a recommended list because the Tags service cannot be created.

Cause: The creation of the Tags service was unsuccessful, so the recommended list could not be created.

Action: Check for /META-INF/tagging-class-config.properties and verify that a correct accessible class is specified.
Level: 1

Type: ERROR

Impact: Other

WCS-26603: Bookmark cannot be loaded because Tags service cannot be created.

Cause: The creation of the Tags service was unsuccessful, so the bookmark object could not be created.

Action: Check for /META-INF/tagging-class-config.propertie sand verify that a correct accessible class is specified.
Level: 1

Type: ERROR

Impact: Other

WCS-26604: Bookmark saving failed because a Tags service cannot be created.

Cause: The creation of the Tags service was unsuccessful, so the bookmark could not be saved.

Action: Check for /META-INF/tagging-class-config.properties and verify that a correct accessible class is specified.
Level: 1

Type: ERROR

Impact: Other

WCS-26605: lookupBookmark failed because of invalid arguments passed in to the method: service ID ({0}), resource ID ({1}), and user ID ({2}).

Cause: One of the input arguments to lookupBookmark was invalid.

Action: Make sure that arguments passed in to lookupBookmark are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26606: createBookmark failed because of invalid arguments passed in to the method: service ID ({0}), resource ID ({1}), resource name ({2}), and user ID ({3}).

Cause: One of the input arguments to createBookmark was invalid.

Action: Make sure that arguments passed in to createBookmark are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26607: findRecommendedTags failed because of invalid arguments passed in to the method: service ID ({0}), resource ID ({1}), and user ID ({2}).

Cause: One of the input arguments to findRecommendedTags was invalid.

Action: Make sure that arguments passed in to findRecommendedTags are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26608: This item has been tagged by the same user at the same time. Re-apply your changes.

Cause: Concurrent update on the bookmarks.

Action: Retry the action.
Level: 1

Type: WARNING

Impact: Other

WCS-26609: Some items whose tags are to be renamed have been updated at the same time. Re-apply your changes.

Cause: Concurrent update on the bookmarks.

Action: Retry the action.
Level: 1

Type: WARNING

Impact: Other

WCS-26610: Some items whose tags are to be deleted have been updated at the same time. Re-apply your changes.

Cause: Concurrent update on the bookmarks.

Action: Retry the action
Level: 1

Type: WARNING

Impact: Other

WCS-26611: Tagging Button or Tagging Menu Item will not be rendered because the region "tagging-launch-dialog" is not included in the page.

Cause: While building the page, the tagging button was added without adding a corresponding popup task flow.

Action: Check to make sure the "tagging-launch-dialog" region is indeed included in the page.
Level: 1

Type: WARNING

Impact: Other

WCS-26612: The tagging component "{0}" was not rendered because the underlying Tags service was not available.

Cause: The underlying Tags service was not available.

Action: Look for the errors causing the underlying Tags service to not be available and fix them.
Level: 1

Type: WARNING

Impact: Other

WCS-26621: EncodeBegin error for TaggingPopup tag

Cause: Catastrophic error

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-26622: Error in Tagging Button tag usage - component {0} has attribute {1} whose value is {2}.

Cause: The attribute mentioned in the error cannot be null, but no value was found for this attribute.

Action: Correct your tag usage.
Level: 1

Type: WARNING

Impact: Other

WCS-26623: Component {0} does not support client listeners.

Cause: Tried to add a client listener to a component that does not support client listeners.

Action: Contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

WCS-32003: Unable to load WebCenter Worklist configuration

Cause: Connections context could not be acquired.

Action: Ensure that the connections.xml file is available and valid.
Level: 1

Type: WARNING

Impact: Other

WCS-32004: Worklist Connection ''{0}'' is an invalid WebCenter Worklist connection.

Cause: The BPEL Worklist connection is invalid.

Action: Verify the specified Worklist connection is to a valid, accessible BPEL Workflow instance.
Level: 1

Type: ERROR

Impact: Other

WCS-32005: The adf-config.xml element associated with the BPEL connection to be used by the To-Dos and Group Tasks service was not present.

Cause: The application's adf-config.xml file was missing the adf-task-config element containing a BPELConnection name.

Action: Add the adf-config.xml entry associated with the To-Dos and Group Tasks service's BPEL connection using the appropriate configuration manipulation.
Level: 1

Type: WARNING

Impact: Other

WCS-32006: The adf-config.xml element associated with the BPEL connection to be used by the Worklist service was not present.

Cause: The application's adf-config.xml file was missing the adf-worklist-config element containing one or more BPELConnection names.

Action: Add the adf-config.xml entry associated with the Worklist service BPEL connection using the appropriate configuration manipulation.
Level: 1

Type: WARNING

Impact: Other

WCS-32007: The BPEL Connection named ''{0}'' was not present in the connections.xml file. This will prevent the To-Dos and Group Tasks service from being able to function as a BPEL connection is required.

Cause: The BPEL Connection matching the name specified in the adf-config.xml segment for the To-Dos and Group Tasks service requires adding to connections.xml.

Action: Add the BPEL Connection entry associated with the To-Dos and Group Tasks service adf-config.xml entry to connections.xml using the appropriate configuration manipulation.
Level: 1

Type: WARNING

Impact: Other

WCS-32008: The BPEL Connection named ''{0}'' was not present in the connections.xml file. This will prevent the Worklist service from being able to interact with the required this BPEL connection.

Cause: The BPEL Connection matching the name specified in the adf-config.xml segment for the Worklist service requires adding to connections.xml.

Action: Add the BPEL Connection entry associated with the Worklist service adf-config.xml entry to connections.xml using the appropriate configuration manipulation.
Level: 1

Type: WARNING

Impact: Other

WCS-32009: The Worklist service does not have a ConnectionName configuration entry in adf-config.xml that maps to a BPELConnection in connections.xml, therefore the Worklist service was not configured for this application.

Cause: There was no Worklist service ConnectionName entry in adf-config.xml that maps to a corresponding BPELConnection name in connections.xml.

Action: Make sure there is a ConnectionName configuration entry in adf-config.xml in the adf-worklist-config element that maps to a BPELConnection entry in connections.xml using the appropriate configuration manipulation.
Level: 1

Type: WARNING

Impact: Other

WCS-32010: The To-Dos and Group Tasks service does not have an entry in adf-config.xml that maps to a BPELConnection in connections.xml, therefore the To-Dos and Group Tasks service was not configured for this application.

Cause: There was no To-Dos and Group Tasks service ConnectionName entry in adf-config.xml that maps to a corresponding BPELConnection name in connections.xml.

Action: Make sure there is a ConnectionName configuration entry in adf-config.xml in the adf-task-config element that maps to a BPELConnection entry in connections.xml using the appropriate configuration manipulation.
Level: 1

Type: WARNING

Impact: Other

WCS-32011: The connection associated with connection name ''{0}'' was not of type BPELConnection. This will prevent the To-Dos and Group Tasks service from being able to use this connection.

Cause: The To-Dos and Group Tasks service ConnectionName entry in adf-config.xml was not mapped to a corresponding BPELConnection name in connections.xml.

Action: Either recreate the connection to one of connection type BPELConnection in connections.xml, or update the To-Dos and Group Tasks service's adf-task-config adf-config.xml entry to refer to a BPELConnection.
Level: 1

Type: WARNING

Impact: Other

WCS-32012: The connection associated with connection name ''{0}'' was not of type BPELConnection. This will prevent the Worklist service from being able to use this connection.

Cause: The Worklist service ConnectionName entry in adf-config.xml was not mapped to a corresponding BPELConnection name in connections.xml.

Action: Either recreate the connection to one of connection type BPELConnection in connections.xml, or update the Worklist service's adf-worklist-config adf-config.xml entry to refer to a BPELConnection.
Level: 1

Type: WARNING

Impact: Other

WCS-32013: Unable to interact with the BPEL client APIs.

Cause: The Worklist service was unable to interact with the BPEL client APIs.

Action: See the exception in the associated notification.
Level: 1

Type: ERROR

Impact: Other

WCS-32100: The WebCenter Worklist has queried the BPEL Worklist connection named ''{0}'', and encountered a WebCenter Executor error. Please see related exception for details. If the WebCenter Worklist is running in an Application Server, check to see if the wsm-pm application is up and running.

Cause: Either, there is an issue with the BPEL Worklist instance being queried or, (if the WebCenter application is running in an Application Server) the wsm-pm application required by the Worklist is down.

Action: Validate the BPEL Worklist connection details in connections.xml, and check that the wsm-pm application process is up and running (if the WebCenter application is running in an Application Server).
Level: 1

Type: ERROR

Impact: Other

WCS-32101: Cache not available.

Cause: Cache is not initialized.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-32102: Could not operate on cache object.

Cause: Examine the associated Cache related exceptions that have been logged.

Action: Contact system administrator, if unable to resolve through examination of related logged Cache exception.
Level: 1

Type: ERROR

Impact: Other

WCS-32103: Unable to query BPEL repository.

Cause: The Worklist service was unable to connect to the BPEL repository, as an exception occurred while querying the BPEL Client APIs.

Action: See the exception in the associated notification.
Level: 1

Type: ERROR

Impact: Other

WCS-33001: Exception while executing Query for Recent Activities "{0}" : "{1}".

Cause: The execution of the search query for recent activities failed.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-33002: Unable to find any services to query.

Cause: The Service Framework has not provided any services to query.

Action: Add services to application that can be searched for recent activity.
Level: 1

Type: ERROR

Impact: Configuration

WCS-33003: Exception while executing Search Query Thread for Recent Activities "{0}" : "{1}".

Cause: The query of a specific service for recent activity has failed.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-33004: Unable to retrieve user preference "{0}".

Cause: The user preferences could not be read.

Action: Check the WebCenter preference configuration and MDS settings.
Level: 1

Type: ERROR

Impact: Configuration

WCS-33005: Recency value of "{0} minutes" is too low (minimum value is 1 minute).

Cause: The number of minutes considered to be recent is too low.

Action: Increase the recency value preference to greater than or equal to 1 minute.
Level: 1

Type: ERROR

Impact: Programmatic

WCS-33006: Search Execution API returned null.

Cause: The search API used to query for recent activity returned a null object.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

WCS-33007: Service Extension for Recent Activities was not found.

Cause: The WebCenter Service Extension for Recent Activities could not be found.

Action: Check the WebCenter configuration in adf-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

WCS-33008: View Layer API Exception: Exception {0}. Message: {1}.

Cause: Unable to render the recent activity UI.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-33009: Exception reading from Recent Activity Cache: {0} : {1}.

Cause: The data cache for recent activity for this user has failed.

Action: Clear the cache by clicking the Refresh button. If the problem persists, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-33010: Invalid recent activity entry returned from service {0} with title "{1}".

Cause: The service returning recent activity has responded with invalid data.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

WCS-33011: Unhandled Error or Exception: {0} : {1}.

Cause: The recent activity API has caught an unhandled Exception or Error, possibly thrown in an underlying service.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-33501: Unable to execute the search for recent activity. Search has not been provisioned.

Cause: The WebCenter Recent Activity Service depends on the availability of the Search service to execute the search for recent activities, but the Search service has not been provisioned for the current scope.

Action: Provision the Search service for this scope.
Level: 1

Type: ERROR

Impact: Other

WCS-33502: The value given for the groupSpace parameter is not a valid group space scope.

Cause: The task flow parameter groupSpace has been set to a scope that does not exist. If this application contains no groupSpace scopes, this parameter must be null.

Action: Edit the task flow parameter in the page definition to set the groupSpace parameter to a valid value (usually null).
Level: 1

Type: ERROR

Impact: Other

WCS-33503: Unable to obtain recent activity data.

Cause: The search may have timed out, failed, or been unable to find anything to search.

Action: Refresh the Recent Activity component using the refresh icon.
Level: 1

Type: ERROR

Impact: Other

WCS-33504: Recent Activity in the Personal Space requires a groupSpace taskflow parameter value to use for the search.

Cause: Recent Activity cannot search the Personal Space.

Action: Edit the Recent Activities taskflow properties and specify a group space taskflow parameter.
Level: 1

Type: ERROR

Impact: Other

WCS-34002: Item not found.

Cause: Item did not exist in repository.

Action: Do not reference items that do not exist.
Level: 1

Type: WARNING

Impact: Other

WCS-34003: Item not found, ancestor depth is not valid.

Cause: The depth of the ancestor was not valid.

Action: Check the depth of the node first.
Level: 1

Type: WARNING

Impact: Other

WCS-34004: This node is not in sync with the file system.

Cause: The session contains stale file system information.

Action: Invoke refresh() or save() to synchronize the session with the file system.
Level: 1

Type: WARNING

Impact: Other

WCS-34005: This node does not have a primary item.

Cause: Folders do not have primary items.

Action: Do not invoke getPrimaryItem() on a folder node.
Level: 1

Type: WARNING

Impact: Other

WCS-34007: Path not found: {0}.

Cause: The method was invoked with an invalid path.

Action: Invoke the method with a valid path.
Level: 1

Type: WARNING

Impact: Other

WCS-34008: Unsupported repository operation.

Cause: A method has been invoked that is not supported.

Action: Any code calling this method should be removed or skipped.
Level: 1

Type: WARNING

Impact: Other

WCS-34013: Invalid file system adapter repository reference.

Cause: The Reference provided to initialize the repository does not describe a file system connection or has incorrect parameters.

Action: Invoke the FSRepository constructor with a valid Reference constructed from FSRepository.getReference.
Level: 1

Type: WARNING

Impact: Other

WCS-34014: {0} is not a valid file system mount point.

Cause: The mount point is not a valid file system directory.

Action: Invoke the repository constructor with a valid root directory.
Level: 1

Type: WARNING

Impact: Other

WCS-34015: {0} is not a known workspace in this repository

Cause: Could not access the workspace, as the file system adapter does not support workspaces.

Action: Invoke login() with a null or empty workspace name.
Level: 1

Type: WARNING

Impact: Other

WCS-34016: The file system adapter does not accept login credentials

Cause: Could not login as the file system adapter does not accept login credentials.

Action: Invoke login() with null credentials.
Level: 1

Type: WARNING

Impact: Other

WCS-34017: Impersonation is not allowed.

Cause: Could not execute the impersonate method as the file system adapter does not support impersonation.

Action: Do not invoke the impersonate() method.
Level: 1

Type: WARNING

Impact: Other

WCS-34018: Cannot complete the delete operation.

Cause: An unexpected file system error occurred during the delete operation.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-34019: Cannot complete the move operation.

Cause: An unexpected file system error occurred during the move operation.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-34021: Cannot access the file system.

Cause: There was an error reading a file.

Action: See the chained IOException for more details on this error.
Level: 1

Type: ERROR

Impact: Other

WCS-34022: This property is not a REFERENCE.

Cause: This property is not a REFERENCE.

Action: Do not invoke getNode() on this property.
Level: 1

Type: WARNING

Impact: Other

WCS-34023: Illegal single value access: property is multi valued.

Cause: Accessed a single value property on a multi valued property.

Action: Do not access a single value property on a multi valued property.
Level: 1

Type: WARNING

Impact: Other

WCS-34024: Illegal multi value access: property is single valued.

Cause: Accessed a multi value property on a single value property.

Action: Do not access a multi value property on a single value property.
Level: 1

Type: WARNING

Impact: Other

WCS-34025: XPath error

Cause: Error occurred while processing XPath.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-34026: Invalid XPath query

Cause: The XPath query was invalid.

Action: Correct the XPath query.
Level: 1

Type: WARNING

Impact: Other

WCS-34028: Invalid call to setProperty: the target type is not valid.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-34029: Invalid call to setProperty: this property cannot be set or the value is not compatible

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-34030: Cannot move a file or folder to a file.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-34031: Save cannot include only the source or the destination of a move.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-34032: Cannot specify an index on move destination.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-34034: Cannot move a property.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-34035: An item with the same name already exists at the destination.

Cause: An attempt was made to overwrite an existing item.

Action: Specify the overwrite option, or remove the item before attempting this operation.
Level: 1

Type: WARNING

Impact: Other

WCS-34036: Move prevented by constraint violation.

Cause: Could not perform the requested move operation as it violates the constraints defined in the JCR specification.

Action: Verify that the target node is a valid parent and/or this node can be renamed.
Level: 1

Type: WARNING

Impact: Other

WCS-34037: Access denied

Cause: Could not perform the specified action as it is not allowed on the path specified.

Action: Contact the system administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-34038: The session has pending changes.

Cause: The operation could not proceed as there are pending changes in the session.

Action: Invoke save() or refresh() before performing the operation.
Level: 1

Type: WARNING

Impact: Other

WCS-34047: Invalid parameter

Cause: Could not parse a parameter to this call as it is invalid.

Action: Check and correct the parameters for this call.
Level: 1

Type: WARNING

Impact: Other

WCS-34306: Error while executing a search.

Cause: An unexpected error occurred while executing a search.

Action: Check the search criteria is valid and verify that the Portal instance is up and running.
Level: 1

Type: ERROR

Impact: Other

WCS-34307: Invalid node type : {0}

Cause: An invalid node type was specified for the search.

Action: Verify that the search query is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34308: Cannot determine the node type for the search.

Cause: An unexpected error occurred while determining the node type for the search.

Action: Check the search query is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34310: Invalid search query.

Cause: The XPath specified for the search was invalid.

Action: Ensure that the search query is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34311: An error occurred while building the search.

Cause: An error occurred while building the search query.

Action: Ensure the search query is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34320: Property cannot be created for {0} as the data type, {1}, is invalid. Path: {2}; node ID: {3}; node site ID: {4}.

Cause: The data type for the requested property was invalid.

Action: Specify a valid data type for the property, and retry.
Level: 1

Type: ERROR

Impact: Other

WCS-34321: Primary item name for node type, {0}, cannot be returned. NodeTypeID: {1}; NodeTypeSiteID: {2}.

Cause: The node type was invalid.

Action: Check if the requested node type exists in the repository.
Level: 1

Type: ERROR

Impact: Other

WCS-34322: Property definitions of node type, {0}, cannot be determined.

Cause: An error occurred while creating the property definitions.

Action: Check if the requested node type exists in the repository.
Level: 1

Type: ERROR

Impact: Other

WCS-34323: Super types of node type, {0}, cannot be determined.

Cause: An error occurred while creating the super types.

Action: Check the node type is valid and retry.
Level: 1

Type: ERROR

Impact: Other

WCS-34324: Primary item name for node type, {0}, cannot be determined.

Cause: The node type was not found.

Action: Check the node type is valid and retry.
Level: 1

Type: ERROR

Impact: Other

WCS-34325: Node definitions for node type, {0}, cannot be determined.

Cause: Node definition could not be created.

Action: Check the node type is valid and retry.
Level: 1

Type: ERROR

Impact: Other

WCS-34326: Super types of node type, {0}, cannot be determined. NodeTypeID: {1}; NodeTypeSiteID: {2}.

Cause: The node type was not found.

Action: Verify that the requested node type exists in the repository.
Level: 1

Type: ERROR

Impact: Other

WCS-34327: Invalid credentials.

Cause: Session could not be created for the user.

Action: Verify that the credentials passed are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34328: Database connection could not be obtained.

Cause: Could not access the database, which may be down.

Action: Verify that the Portal instance is up and running.
Level: 1

Type: ERROR

Impact: Other

WCS-34329: Insufficient privileges to perform the operation.

Cause: You did not have the sufficient privilege to perform this operation.

Action: Contact the Portal administrator to check your privileges.
Level: 1

Type: WARNING

Impact: Other

WCS-34330: The requested node type, {0}, does not exist.

Cause: Could not locate the requested node type as it does not exist.

Action: Verify that the node type exists in the repository.
Level: 1

Type: ERROR

Impact: Other

WCS-34331: Property definitions of node type, {0}, cannot be returned. NodeTypeID: {1}; NodeTypeSiteID: {2}.

Cause: An error occurred while creating the property definitions.

Action: Check the node type is valid, verify that the Portal instance is up and running.
Level: 1

Type: ERROR

Impact: Other

WCS-34332: Property, {0}, cannot be set for node type, {1}. NodeTypeID: {2}; NodeTypeSiteID: {3}.

Cause: Property value was invalid.

Action: Provide a property value that is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34333: Oracle data-source, {0}, cannot be looked up.

Cause: The data-source was not available.

Action: Verify that the data-source is created correctly and is available.
Level: 1

Type: ERROR

Impact: Other

WCS-34335: The root nodes of the Portal repository cannot be obtained.

Cause: An error occurred while listing the root nodes.

Action: Verify that the Portal instance is up and running.
Level: 1

Type: ERROR

Impact: Other

WCS-34336: Statement/Connection objects cannot be closed.

Cause: An error occurred while closing the statement or connection objects.

Action: Verify that the Portal instance is up and running.
Level: 1

Type: ERROR

Impact: Other

WCS-34337: The child nodes of folder, {2}, cannot be obtained. Parent folder ID: {0}; folder site ID: {1}.

Cause: A SQL exception occurred while trying to list the child nodes.

Action: Verify the folder ID, folder page group ID and path are valid, verify that the Portal instance is up and running.
Level: 1

Type: ERROR

Impact: Other

WCS-34338: Property, {0}, is a single-valued property.

Cause: The property was a single valued property.

Action: Verify the value for the property is a single value.
Level: 1

Type: ERROR

Impact: Other

WCS-34339: Unable to check if the session is live.

Cause: An error occurred while checking whether the session is live.

Action: Verify that the Portal instance is up and running.
Level: 1

Type: ERROR

Impact: Other

WCS-34340: The Portal session cannot be logged out.

Cause: An error occurred while logging out of the Portal session; it is possible the Portal instance is no longer available.

Action: Verify that the Portal instance is up and running.
Level: 1

Type: ERROR

Impact: Other

WCS-34341: Cannot determine UUID for node, {0}.

Cause: An error occurred while determining the UUID of context node.

Action: Verify that the path is correct and that the node is referenceable.
Level: 1

Type: ERROR

Impact: Other

WCS-34342: Cannot get the node, {0}.

Cause: An error occurred while getting the requested node.

Action: Verify that the path is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34343: Cannot get the node for the given UUID, {0}.

Cause: Error getting the requested node.

Action: Verify that the UUID is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34344: Cannot determine if item exists at given path, {0}.

Cause: An error occurred while determining if the requested item exists.

Action: Verify that the path is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34346: Property definitions of node type cannot be determined. NodeTypeID: {0}; NodeTypeSiteID: {1}.

Cause: An error occurred while creating the property definitions.

Action: Verify that the node type exists in the Portal repository.
Level: 1

Type: ERROR

Impact: Other

WCS-34347: Property, {0}, cannot be set for node type. NodeTypeID: {1}; NodeTypeSiteID: {2}.

Cause: Property value was invalid.

Action: Provide a property value that is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34348: Cannot retrieve all the node types from the Portal repository.

Cause: An error occurred while retrieving the Portal node types.

Action: Verify that the Portal instance is up and running.
Level: 1

Type: ERROR

Impact: Other

WCS-34349: Cannot get the properties for node with ID: {0}, site ID: {1}.

Cause: An error occurred while obtaining the properties of the node from the repository.

Action: Verify that the node and node type are valid, and verify that the Portal instance is up and running.
Level: 1

Type: ERROR

Impact: Other

WCS-34350: Cannot get the references for the requested node. Node ID: {0}; node site ID: {1}.

Cause: An error occurred while obtaining the references for the requested node.

Action: Verify the node is valid, and verify that the Portal instance is up and running.
Level: 1

Type: ERROR

Impact: Other

WCS-34351: Cannot get binary property value for property, {0}, that belongs to node, {1}.

Cause: An error occurred while fetching the binary property of node.

Action: Verify that the path is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-34352: Cannot get Portal property name for property ID: {0}.

Cause: An error occurred while getting the Portal property name.

Action: Verify that the requested property is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34354: The Portal session could not be logged out.

Cause: A SQL error occurred when attempting to log out.

Action: Verify that the Portal instance is up and running.
Level: 1

Type: ERROR

Impact: Other

WCS-34355: Cannot determine the length of the given input stream.

Cause: An error occurred while determining the length of the input stream.

Action: Verify that the input stream is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34356: Current operation is not supported for the single-valued property, {0}.

Cause: The current operation could not be performed on a single property as single-valued properties are not supported by such an operation.

Action: This API cannot be invoked on a single-valued property.
Level: 1

Type: ERROR

Impact: Other

WCS-34357: This node, {0}, cannot be referenced and hence, does not have a UUID property.

Cause: The context node does not have a UUID property.

Action: Make this request on a referenceable node.
Level: 1

Type: ERROR

Impact: Other

WCS-34358: Current operation is not supported for the multi-valued property, {0}.

Cause: The current operation could not be performed on a multi-valued property as multi-valued properties are not supported by such an operation.

Action: This API cannot be invoked on a multi-valued property.
Level: 1

Type: ERROR

Impact: Other

WCS-34359: This operation is not supported by the Portal repository.

Cause: An error occurred while performing this action as the operation is not supported by the underlying Portal repository.

Action: Check the operation being attempted is a valid operation for the repository.
Level: 1

Type: ERROR

Impact: Other

WCS-34360: The Portal repository has only 1 workspace, so this request is invalid.

Cause: The underlying Portal repository has only one workspace.

Action: This is an invalid request since the repository is a single workspace repository. Retry with a valid request.
Level: 1

Type: ERROR

Impact: Other

WCS-34361: Cannot convert length of property, {0}, to long.

Cause: An error occurred while converting the length to the long data type.

Action: Verify the value of the property is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34362: Cannot parse the date value for property, {0}.

Cause: An error occurred while parsing the date value.

Action: Verify the value of the property is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34363: The requested property cannot be found. Path of context node: {0}; Relative Path: {1}.

Cause: The property was not found.

Action: Verify that the requested property is valid and that the path is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34364: The requested item, {0}, cannot found.

Cause: An error occurred while getting the requested item.

Action: Verify that the item exists in the Portal repository.
Level: 1

Type: ERROR

Impact: Other

WCS-34365: The property, {0}, cannot be converted to a reference.

Cause: The property could not be converted to a reference or was a multi-valued property.

Action: Verify that the property can be converted to a reference.
Level: 1

Type: ERROR

Impact: Other

WCS-34366: {0} is a folder and hence, it does not have a primary item.

Cause: The request could not be performed because folders cannot have primary items.

Action: This is an invalid request.
Level: 1

Type: ERROR

Impact: Other

WCS-34367: The requested node was not found. Path of context node: {0}; Relative Path: {1}.

Cause: The node was not found.

Action: Verify that the requested node is valid and that the path is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34368: The given path, {0}, is invalid.

Cause: The specified path was invalid.

Action: Provide a valid path.
Level: 1

Type: WARNING

Impact: Other

WCS-34416: Error determining if child node, {0}, could be added.

Cause: An error occurred while determining whether the child node could be added.

Action: Verify the node is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34417: Error determining if child node, {0}, based on type, {1}, could be added.

Cause: An error occurred while determining whether a child node based on the given type could be added.

Action: Verify the node and type are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34418: Error removing the child item, {0}, for node type, {1}.

Cause: An error occurred while removing the child item.

Action: Verify item and node type are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34419: Error removing the property, {0}, for node type, {1}.

Cause: An error occurred while removing the property.

Action: Verify the node type and property are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34421: The connection cannot be closed.

Cause: The system encountered an unexpected error while trying to close a database connection.

Action: Verify that the Portal instance is up and running.
Level: 1

Type: ERROR

Impact: Other

WCS-34422: The node types array object could not be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the node types object in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34423: The "all node types" node type iterator could not be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the node type iterator in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34424: The Portal node types linked list object could not be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the Portal node types linked list object in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34425: The cache region, {0}, has already been defined.

Cause: The cache region has already been defined.

Action: No action is required as this is just indicating that the cache region has already been defined.
Level: 1

Type: WARNING

Impact: Other

WCS-34428: Generic cache exception when trying to retrieve object from cache.

Cause: A cache exception occured when trying to retrieve the object from the cache.

Action: Contact the WebCenter administrator to check the status of the Cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34429: Object cannot be stored in cache as the cache is full.

Cause: The object could not be stored in cache because the cache was full.

Action: Contact the WebCenter administrator to check the status of the Cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34430: The root node does not have a parent node.

Cause: The parent node was requested for a root node.

Action: Request the parent node of any node except the parent node.
Level: 1

Type: ERROR

Impact: Other

WCS-34431: The node type iterator object cannot be removed from the cache.

Cause: The node type iterator object could not be removed from the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34432: The node type name cannot be returned from the qualified name.

Cause: The namespace could not be resolved.

Action: Verify the specified node type name is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34433: The property name cannot be returned from the qualified name.

Cause: The namespace could not be resolved.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-34434: The property definition name cannot be returned from the qualified name.

Cause: The namespace could not be resolved.

Action: Verify the property type is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34435: The item at the requested depth, {0}, cannot be found.

Cause: An error occurred while getting the requested item.

Action: Verify that the depth is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34436: The root node does not have a parent.

Cause: Could not request the parent node as root nodes do not have parent nodes.

Action: Verify that the context node is not the root node.
Level: 1

Type: ERROR

Impact: Other

WCS-34437: The Portal session cannot be restored.

Cause: A SQL error occurred when attempting to restore the session for the user.

Action: Verify that the user has been authenticated.
Level: 1

Type: ERROR

Impact: Other

WCS-34438: The declared property definition array object cannot be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the declared property definition array object in cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34440: The property definition array object cannot be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the property definition array object in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34441: The property iterator object cannot be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the property iterator object in the cache.

Action: Contact the WebCenter administrator to check the status of the Cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34442: The property object cannot be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the property object in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34443: The node iterator object cannot be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the node iterator object in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34444: The node object cannot be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the node object in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34446: The node type object cannot be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the node type object in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34447: The "primary node types" node type iterator cannot be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the node type iterator in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34448: The "mixin node types" node type iterator cannot be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the node type iterator in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34449: The "super types" node type array cannot be stored in cache.

Cause: The system encountered an unexpected exception when trying to store the node type array in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34450: The child node definitions of the node type cannot be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the child node definitions of the node type in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34451: The property definitions of the node type cannot be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the property definitions of the node type in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34452: The boolean object cannot be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the boolean object in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34453: The requested child node definition of the node type cannot be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the child node definition of the node type in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34454: The requested property definition of the node type cannot be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the property definition of the node type in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34456: The repository property objects cannot be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the repository property objects in cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34457: The repository property definition objects cannot be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the repository property definition objects in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34458: One of the cache regions could not be destroyed.

Cause: The system encountered an unexpected exception when trying to destroy one of the cache regions.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34459: The cache could not be initialized.

Cause: The system encountered an unexpected exception when trying to initialize the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34460: The cache configuration file could not be read.

Cause: The system encountered an IO exception when trying to read the cache configuration file.

Action: Verify that the configuration file exists.
Level: 1

Type: ERROR

Impact: Other

WCS-34461: The repository node type objects could not be stored in cache.

Cause: The system encountered an unexpected exception when trying to store the repository node type objects in cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34462: Cannot get the super types for node type: {0}.

Cause: An error occurred while fetching the super types of the given node type.

Action: Verify that the requested node type exists in the Portal repository and is a custom type.
Level: 1

Type: ERROR

Impact: Other

WCS-34463: The cache region, {0}, cannot be found.

Cause: Could not find the requested region, as it has not been defined in Java Object Cache (JOC).

Action: Verify that the region name is valid and is expected to exist in this hierarchy.
Level: 1

Type: ERROR

Impact: Other

WCS-34464: Oracle Text search is unable to run.

Cause: An error occurred with Oracle Text while running a search.

Action: Check with the Administrator of the Portal you are trying to search that Oracle Text is valid. Additional information as to the cause of the error may be in the portal diagnostics log.
Level: 1

Type: ERROR

Impact: Other

WCS-34465: A root search can not be performed as the base languages of the page groups are different.

Cause: The search could not be performed because the base language of the page groups to be searched are not the same.

Action: Only perform searches which search a single page group.
Level: 1

Type: ERROR

Impact: Other

WCS-34466: Cannot look up the database connection with the name {0} from connections.xml.

Cause: An error occurred while attempting to look up the database connection; the named database connection may not exist in connections.xml.

Action: Make sure the database connection is created in connections.xml.
Level: 1

Type: ERROR

Impact: Other

WCS-35006: cannot load metadata from XML node

Cause: The content of the data-control file (.dcx) might be invalid.

Action: Verify that the content in the data-control file (.dcx) is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-35008: Login failed.

Cause: The specified user credentials were invalid.

Action: Provide valid user credentials.
Level: 1

Type: ERROR

Impact: Other

WCS-35013: missing method parameters

Cause: The data-control operation was invoked without any parameters.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-35016: Retrieving data-control definition from run-time data-control object returned null.

Cause: The ADF framework did not set the data-control definition within the run-time data control.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-35300: Parameters for the operation are missing.

Cause: The ADF framework passed a null parameter map to the data-control operation.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-35301: The path parameter is not correct.

Cause: The path string that was specified was not a valid JCR repository path.

Action: Verify that the specified path string is a valid path in the content repository, and that it starts with /.
Level: 1

Type: ERROR

Impact: Other

WCS-35302: The type parameter is not correct.

Cause: The type string that was specified was not a valid node type in the JCR repository.

Action: Make sure the type specified is valid in the content repository on which the data control is based. Both the prefix and the local name should be valid. For example, nt:file and nt:folder are valid types.
Level: 1

Type: ERROR

Impact: Other

WCS-35303: cannot generate XPath query

Cause: The parameters that were given in the search operation could not be resolved into a valid XPath query string using the content repository session.

Action: Ensure the attribute names and prefixes used in the parameters are valid and registered in the JCR repository.
Level: 1

Type: ERROR

Impact: Other

WCS-35304: incorrect attribute {0} specified in the predicate

Cause: The specified attribute was not found in the repository.

Action: Provide a valid attribute name.
Level: 1

Type: ERROR

Impact: Other

WCS-35305: incorrect prefix for the attribute {0} in the predicate

Cause: The namespace that was used in the attribute was not correct or not registered in the JCR repository.

Action: Provide a valid prefix, or report the problem to the provider of the JCR adapter used with the repository.
Level: 1

Type: ERROR

Impact: Other

WCS-35306: cannot resolve attribute {0} using the repository session

Cause: An invalid attribute or an unregistered prefix was used in the JCR session.

Action: Provide a valid attribute name in the JCR repository session.
Level: 1

Type: ERROR

Impact: Other

WCS-35307: operator {0} not supported

Cause: An invalid operator was specified.

Action: Specify a valid operator.
Level: 1

Type: ERROR

Impact: Other

WCS-35309: The XPath query {0} is not supported by the JCR adapter.

Cause: The JCR adapter might not have been compliant with the XPath support that is required to work with the Content Repository data control.

Action: Verify that the XPath query is supported by this JCR adapter.
Level: 1

Type: ERROR

Impact: Other

WCS-35310: error in the JCR repository

Cause: An error occurred in the JCR adapter.

Action: Check the exception's cause and JCR adapter's error log.
Level: 1

Type: ERROR

Impact: Other

WCS-35311: error getting the item's URL

Cause: An error occurred while generating the URL for an item.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-35312: invalid return attribute name {0}

Cause: An invalid Java name was entered. The name of a return attribute must be a valid Java name and must be different from "name", "URL", "path" and "primaryType".

Action: Verify that the attribute name is valid and is not "name", "URL", "path" and "primaryType".
Level: 1

Type: ERROR

Impact: Other

WCS-35313: invalid return attribute type

Cause: An invalid return attribute type was specified. Return attributes must be one of the following JCR types: Boolean, Integer, Double, String, or Date.

Action: Specify a valid return attribute type.
Level: 1

Type: ERROR

Impact: Other

WCS-35314: cannot get value for attribute {0}

Cause: The value for the specified attribute could not be retrieved from the JCR node.

Action: Verify that the JCR path for the attribute is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-35501: No repository was set in the environment.

Cause: No repository was specified for this resource.

Action: Specify a repository to use in creating the resource.
Level: 1

Type: ERROR

Impact: Other

WCS-35502: could not log on to the content repository

Cause: There was a problem logging on to the content repository.

Action: Verify that the connection and credentials are defined correctly and that the repository is accessible.
Level: 1

Type: ERROR

Impact: Other

WCS-35503: An error occurred while accessing the content repository.

Cause: There was a problem accessing the content repository.

Action: Verify that the content repository is accessible.
Level: 1

Type: ERROR

Impact: Other

WCS-35504: An error occurred while trying to close the connection.

Cause: Could not close the content repository connection.

Action: Verify that the connection is still available, and try to close it again.
Level: 1

Type: ERROR

Impact: Other

WCS-35505: Item {0} is not a file or folder.

Cause: An item was specified that is not a file or folder.

Action: Specify an item that is either a file or a folder.
Level: 1

Type: ERROR

Impact: Other

WCS-35506: Item {0} does not exist.

Cause: An item was specified that does not exist.

Action: Verify that the specified item exists.
Level: 1

Type: ERROR

Impact: Other

WCS-35507: unknown control type: {0}

Cause: An unknown control type was specified.

Action: Specify a known control type.
Level: 1

Type: ERROR

Impact: Other

WCS-35508: {0} does not name a ContentDirContext.

Cause: An item was specified that is not a ContentDirContext.

Action: Verify that the item specified is a ContentDirContext.
Level: 1

Type: ERROR

Impact: Other

WCS-35509: invalid search operation: {0}

Cause: An unrecognized search operation was specified.

Action: Use only recognized search operations.
Level: 1

Type: ERROR

Impact: Other

WCS-35510: unable to generate schema

Cause: An error occurred while adding attributes to the schema.

Action: Make sure the schema attributes are defined properly and are not already bound.
Level: 1

Type: ERROR

Impact: Other

WCS-35511: unable to create DataFlavor

Cause: An error occurred while trying to create a DataFlavor from the given MIME type.

Action: Make sure the MIME type is valid and non-null, and that any referenced classes can be loaded.
Level: 1

Type: WARNING

Impact: Other

WCS-35513: unable to create TaskFlowDescriptor

Cause: An error occurred while trying to create a TaskFlowDescriptor object.

Action: Make sure the required classes are in the classpath.
Level: 1

Type: ERROR

Impact: Other

WCS-35514: This feature is only available in a design environment.

Cause: A call to a design time only feature was made from run time.

Action: Do not call this method from run time code.
Level: 1

Type: ERROR

Impact: Other

WCS-35900: Illegal value state, cannot read a value previously streamed.

Cause: The application mixed calls to getStream() and other get* accessors on the same value object.

Action: Verify your application code.
Level: 1

Type: ERROR

Impact: Other

WCS-35901: Illegal value state, cannot stream a value previously read.

Cause: The application mixed calls to getStream() and other get* accessors on the same value object.

Action: Verify your application code.
Level: 1

Type: ERROR

Impact: Other

WCS-35902: Error in value conversion (source type = {0}, target type = {1}).

Cause: The JCR values could not be converted to the specified type; the source and target type may not be compatible.

Action: Verify the value conversion rules defined in the JCR specification.
Level: 1

Type: ERROR

Impact: Other

WCS-35903: Error in value conversion (invalid ISO8601 string).

Cause: The specified string was not a valid ISO8601 string as specified by JCR and therefore could not be converted to a date.

Action: Verify the format of the date string.
Level: 1

Type: ERROR

Impact: Other

WCS-35904: Cannot create REFERENCE values.

Cause: Values of type REFERENCE are not supported by this JCR repository.

Action: Avoid using properties of type REFERENCE in your application.
Level: 1

Type: WARNING

Impact: Other

WCS-35905: Input/Output error while reading the binary stream.

Cause: The data for the binary property could not be accessed.

Action: Verify that the storage medium for the JCR repository is accessible.
Level: 1

Type: WARNING

Impact: Other

WCS-35906: UTF8 encoding not supported on this JVM

Cause: The JVM does not support UTF-8 encoding.

Action: Use a supported Java 5 compliant JVM.
Level: 1

Type: WARNING

Impact: Other

WCS-35907: This iterator does not contain any more elements.

Cause: The iterator has exhausted all its elements.

Action: Check the usage of the RangeIterator by your application.
Level: 1

Type: WARNING

Impact: Other

WCS-35908: This iterator does not support the remove operation.

Cause: The remove() operation is not supported on this iterator.

Action: Avoid making calls to RangeIterator#remove() in your application.
Level: 1

Type: WARNING

Impact: Other

WCS-35909: The item at path {0} is not a node.

Cause: An item was found at the specified path but it was not a node.

Action: Check that your application is specifying the correct path.
Level: 1

Type: WARNING

Impact: Other

WCS-35910: "{0}" is not a known namespace prefix.

Cause: The name or path contained a namespace prefix unknown to this repository.

Action: Check the namespace mappings in the current session.
Level: 1

Type: WARNING

Impact: Other

WCS-35911: "{0}" is not a known namespace URI.

Cause: The repository did not recognize the specified namespace URI.

Action: Check the set of namespaces allowed by the current repository.
Level: 1

Type: WARNING

Impact: Other

WCS-35912: The prefix "{0}" is already used.

Cause: The specified prefix was already mapped to a namespace and could not be remapped.

Action: Change the prefix mapping for the URI associated with that prefix before mapping it to another URI.
Level: 1

Type: WARNING

Impact: Other

WCS-35913: {0} is a reserved namespace prefix and cannot be remapped

Cause: The "xml" prefix could not be remapped as it is reserved by JCR.

Action: Check that your application is not trying to remap the "xml" prefix.
Level: 1

Type: WARNING

Impact: Other

WCS-35914: Namespace prefix remapping is not permitted

Cause: Could not remap the namespace as the JCR repository does not permit persistent namespace remapping.

Action: Use the session for any namespace remapping requirements.
Level: 1

Type: WARNING

Impact: Other

WCS-35915: Invalid JCR name or path: {0}

Cause: The name or path specified was not a valid JCR name or path.

Action: Check that the name or path uses valid namespace prefixes and satisfies the JCR grammar rules for names and paths.
Level: 1

Type: WARNING

Impact: Other

WCS-35916: Cannot append an absolute Path

Cause: Could not append an absolute path to the existing path.

Action: Make sure that the appended path is always relative.
Level: 1

Type: WARNING

Impact: Other

WCS-35918: Unexpected error while accessing node type

Cause: An unexpected error occurred while accessing a node type.

Action: Contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

WCS-35919: No such node type: {0}

Cause: The node type specified was unknown to the JCR repository.

Action: Ensure that your are using correct node types for this repository.
Level: 1

Type: WARNING

Impact: Other

WCS-35920: Not a supported query language: {0}

Cause: The query language specified was a not a supported query language; this repository only supports XPath.

Action: Make sure you use only XPath queries.
Level: 1

Type: WARNING

Impact: Other

WCS-35921: Saved queries are not supported.

Cause: Could not save the query as this repository does not support saved queries.

Action: Ensure that your application does not call unsupported JCR functionality.
Level: 1

Type: WARNING

Impact: Other

WCS-35922: Incorrect XPath expression

Cause: Could not recognize the XPath expression specified as it is not supported by this JCR repository.

Action: Check that your XPath query conforms to the JCR specification.
Level: 1

Type: WARNING

Impact: Other

WCS-35923: XPath expression error: invalid enumeration value.

Cause: An internal data structure used an invalid value.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-35924: XPath expression error: invalid expression tree.

Cause: The XPath expression specified was not recognized as it is not supported by this JCR repository.

Action: Check that your XPath query conforms to the JCR specification.
Level: 1

Type: WARNING

Impact: Other

WCS-35925: Error while generating XML representation of expression tree

Cause: Could not create an XML representation of this expression tree.

Action: Check the exception stack trace for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-35926: Invalid xpath expression.

Cause: The XPath expression specified was not recognized as it is not supported by this JCR repository.

Action: Check that your XPath query conforms to the JCR specification.
Level: 1

Type: WARNING

Impact: Other

WCS-35927: Invalid qualified name: {0}

Cause: The specified XPath expression contained an invalid qualified name.

Action: Check that your XPath query conforms to the JCR specification.
Level: 1

Type: WARNING

Impact: Other

WCS-35928: Unexpected error during XML export.

Cause: There was an XML processing error while performing an XML export operation.

Action: Check that you are using Oracle XML parser v2.
Level: 1

Type: WARNING

Impact: Other

WCS-35930: Index out of bound while accessing path

Cause: The specified index for a path element was not valid.

Action: Check your use of the path object.
Level: 1

Type: WARNING

Impact: Other

WCS-35988: FOTY0012: argument node does not have a typed value

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-35989: XPST0010: The query uses an axis that is not supported by the query engine.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-35990: XPST0081: A QName used in the expression contains a namespace prefix that cannot be expanded into a namespace URI by using the statically known namespaces.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-35991: "{0}" is not a valid expression for use as a search string with jcr:contains().

Cause: The specified full text search expression was not a valid argument for jcr:contains().

Action: Check the full text search expression syntax defined in the JCR specification.
Level: 1

Type: WARNING

Impact: Other

WCS-35992: "{0}" is not a valid expression for use as a search string with jcr:like().

Cause: The specified regular expression was not a valid argument for jcr:like().

Action: Check the regular expression syntax defined in the JCR 1.0 specification.
Level: 1

Type: WARNING

Impact: Other

WCS-35993: This XPath expression contains constructs that are not supported by this query engine.

Cause: Could not execute this XPath query as it contained constructs that were not supported by this repository.

Action: Check that your XPath query conforms to the JCR specification.
Level: 1

Type: WARNING

Impact: Other

WCS-35994: XPTY0004: It is a type error if, during the static analysis phase, an expression is found to have a static type that is not appropriate for the context in which the expression occurs, or during the dynamic evaluation phase, the dynamic type of a value does not match a required type as specified by the matching rules in 2.5.4 SequenceType Matching.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-35995: XPST0017: It is a static error if the expanded QName and number of arguments in a function call do not match the name and arity of a function signature in the static context.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-35996: FORG0006: invalid argument type

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-35997: FORG0001: invalid value for cast/constructor

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-35998: XPTY0006: (Not currently used)

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-35999: FONC0001: undefined context item

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36201: Unable to find Page Definition for the template page.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36202: Cannot find page with name "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36203: Failed to create SubPath "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36204: Cannot find Page Definition with name "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36205: Unable to find page with path "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36206: Pages metadata file already exists under the path "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36207: Unable to update DataBindings.cpx to update page usageId.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36208: Scope folder "{0}" for rename does not exist.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36209: Failed to get Permission class for page "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36210: Failed to get Permission target for page "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36211: Cache is not available.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36212: Failed to add pages to cache "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36213: Failed to invalidate cache "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36214: Failed to invalidate cache for scope "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36215: A page with name {0} under path {1} does not exist.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36216: Failed to remove the page permissions for "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36217: Failed to create .rdf file for page "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36218: Failed to delete .rdf file "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36301: Unable to find page "{0}" in the Binding Context.

Cause: Page objects do not exist in the Binding Context.

Action: Check if the page in the specified path exists.
Level: 1

Type: ERROR

Impact: Other

WCS-36302: Unable to create a document with name "{0}".

Cause: Invalid MO name supplied for creation in MDS.

Action: Check the name provided for creation of the document and ensure that it is a valid MO name.
Level: 1

Type: ERROR

Impact: Other

WCS-36303: Unable to create a document in path "{0}".

Cause: MDS raised an MDS_UNSUPPORTED_UPDATE exception while creating document.

Action: Check the MDS config to ensure that the path is editable.
Level: 1

Type: ERROR

Impact: Other

WCS-36304: Unable to create a pagedefs directory under the scope "{0}".

Cause: MDS raised an exception while creating pagedefs folder.

Action: Check the MDS config to ensure that the path is editable.
Level: 1

Type: ERROR

Impact: Other

WCS-36305: Unable to delete page "{0}".

Cause: MDS raised an exception while deleting the page.

Action: Check the MDS config to ensure that the path is editable.
Level: 1

Type: ERROR

Impact: Other

WCS-36306: Unable to create metadata for page "{0}".

Cause: MDS raised an exception while creating metadata for page.

Action: The metadata for the page already exists under the scope.
Level: 1

Type: ERROR

Impact: Other

WCS-36307: Unable to copy page "{0}".

Cause: MDS raised an exception while copying the page.

Action: Check the MDS config to ensure that the path is editable.
Level: 1

Type: ERROR

Impact: Other

WCS-36308: Unable to rename scope "{0}" to "{1}".

Cause: MDS raised an exception while renaming the pages under the scope.

Action: Check the MDS config to ensure that the path is editable.
Level: 1

Type: ERROR

Impact: Other

WCS-36309: An unexpected error occurred.

Cause: An unexpected error occurred.

Action: Contact your system administrator.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-36310: Unable to create a page with the name "{0}".

Cause: A page with the same name already exists.

Action: Change to use a different name.
Level: 1

Type: ERROR

Impact: Other

WCS-36311: PageService object is not an instance of PageServiceImpl.

Cause: PageService object is not an instance of PageServiceImpl.

Action: Create a Page service instance and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-36312: Could not flush changes to MDS. Adding view activity failed.

Cause: Could not flush changes to MDS.

Action: Try to create a new page.
Level: 1

Type: ERROR

Impact: Other

WCS-36313: Unable to find page definition file for page "{0}".

Cause: The page definition file does not exist or the page definition path is wrong in the Binding Context file.

Action: Check if the page definition file exists and make sure its path is correct in the Binding Context file.
Level: 1

Type: ERROR

Impact: Other

WCS-36314: Unable to create a page for now because another page is being created.

Cause: Another page is being created and all page metadata is locked.

Action: Try again.
Level: 1

Type: ERROR

Impact: Other

WCS-36701: Failed to redirect because the page is not specified.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36702: An ADF component with name "{0}" is not found.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36703: Failed to redirect because the page is not specified.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36704: User {0} already has access to the page.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36705: You do not have permission to change page security settings anymore.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36706: You do not have permission to change page properties anymore.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36707: Failed to save the changes because another page operation was in progress.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36801: Failed to change page permission to "{0}".

Cause: An unexpected error occurred when changing page permission.

Action: Check error stack for details.
Level: 1

Type: ERROR

Impact: Other

WCS-36802: Failed to grant page permission "{0}" to user "{1}".

Cause: An unexpected error occurred when granting page permission to a user.

Action: Check error stack for details.
Level: 1

Type: ERROR

Impact: Other

WCS-36803: Failed to revoke page permission from user "{0}".

Cause: An unexpected error occurred when granting page permission to a user.

Action: Check error stack for details.
Level: 1

Type: ERROR

Impact: Other

WCS-36804: Failed to change page security to default mode.

Cause: An unexpected error occurred when changing page security mode.

Action: Check error stack for details.
Level: 1

Type: ERROR

Impact: Other

WCS-37001: An unexpected error occurred.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-37002: An object of type {0} with this ID ({1}) already exits.

Cause: An attempt was made to create an object with an existing ID.

Action: Use a unique ID to Create the object.
Level: 1

Type: ERROR

Impact: Other

WCS-37003: Configuration invalid.

Cause: Either the configuration does not exist or the MDS instance is not specified.

Action: Specify a valid configuration with a MDS instance.
Level: 1

Type: ERROR

Impact: Other

WCS-37004: The name ({0}) is invalid.

Cause: The name specified was not valid.

Action: Specify a valid name.
Level: 1

Type: ERROR

Impact: Other

WCS-37006: Object modified by another user.

Cause: The object has been changed by another user.

Action: Refresh the object and try again.
Level: 1

Type: WARNING

Impact: Other

WCS-37007: Object of type {0} with ID={1} could not be found.

Cause: The ID is invalid.

Action: Specify a valid object ID.
Level: 1

Type: ERROR

Impact: Other

WCS-37008: Object ({0}) is immutable.

Cause: An attempt to change this object was made but this object is currently immutable.

Action: Either update object to allow changes or perform this operation on another object.
Level: 1

Type: ERROR

Impact: Other

WCS-37009: Method: {1} in class: {0} is invalid.

Cause: The specified class.method does not exist or is invalid.

Action: Check underlying method/property specification.
Level: 1

Type: ERROR

Impact: Other

WCS-37010: {0} is not a valid reference name to MDS.

Cause: The name specified is not a valid MDS reference name.

Action: Correct the name to a valid reference.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-37500: The note no longer exists.

Cause: Another user deleted the note.

Action: Refresh the links to see the latest changes.
Level: 1

Type: ERROR

Impact: Other

WCS-37501: This note has been modified by another user.

Cause: Another user modified the note. You can only modify the latest version.

Action: Refresh the page to see the latest changes.
Level: 1

Type: ERROR

Impact: Other

WCS-38001: An unexpected error occurred.

Cause: The cause of this error is unknown.

Action: Try repeating the action that caused this error.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-38002: Data source ({0}) does not exist.

Cause: The specified data source is invalid.

Action: Specify a valid data source and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-38003: Invalid configuration.

Cause: Either the configuration does not exist or MDSInstance is not specified.

Action: Specify a valid MDS configuration and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-38004: Object ({0}) is immutable.

Cause: An attempt to change this object was made but this object is currently immutable.

Action: Either update the object to allow changes or perform this operation on another object.
Level: 1

Type: ERROR

Impact: Other

WCS-38005: An object of type {0} with ID={1} could not be found.

Cause: The object ID is invalid.

Action: Specify a valid object ID.
Level: 1

Type: ERROR

Impact: Other

WCS-38006: Unable to perform transformation

Cause: Transformation input sources were invalid.

Action: Validate the input sources and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-38007: A search error occurred while searching for lists.

Cause: The search parameters were invalid.

Action: Validate the search parameters and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-38008: An error occurred while configuring the List API.

Cause: An invalid List API configuration was specified.

Action: Specify a valid List API configuration and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-38009: An error occurred while looking up list row data.

Cause: The database connection not found.

Action: Verify that a valid database connection exists and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-38010: A search error occurred while searching the discussion forums.

Cause: A connection to the discussion forum service could not be established.

Action: Validate the discussion forum connection details in connections.xml and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-38011: An error occurred while retrieving recent activity information.

Cause: Invalid parameters were passed to the Recent Activity API.

Action: Validate the API usage and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-38012: A search error occurred while searching the service.

Cause: Invalid parameters were passed to the Search API.

Action: Validate the API usage and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-38013: Unable to instantiate class

Cause: An invalid class reference was detected.

Action: Validate the class usage and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-38014: Illegal access exception while accessing class

Cause: An invalid class reference was detected.

Action: Validate the class usage and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-38015: Unable to find class

Cause: An unknown class was referenced.

Action: Verify the class reference and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-38016: Unable to find 'getEnabledScopes' method in class

Cause: Class is missing required method.

Action: Verify that the method exists and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-38017: Service exception while getting service registry.

Cause: Invalid parameters were passed to the Service Registry API.

Action: Validate the API usage and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-38018: A null stream was returned for the RSS XML

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-38019: Object instance for reading RSS feed is not available

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-38020: Unable to get a HTTP connection object for the URL {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-38021: Null object for the XML document

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-38022: The RSS XML does not have a root element

Cause: Invalid XML content detected

Action: Ensure that the RSS feed URL returns XML conforming to the RSS format
Level: 1

Type: WARNING

Impact: Other

WCS-38023: The root element name of the RSS XML is not rss

Cause: The XML content is not RSS XML format compliant.

Action: Ensure that the XML returned by the feed URL is RSS XML format compliant.
Level: 1

Type: WARNING

Impact: Other

WCS-38024: The root element name of the RSS XML does not have any child elements

Cause: The XML content returned by the feed URL is not valid

Action: Ensure that the XML returned by the feed URL is RSS XML format compliant.
Level: 1

Type: WARNING

Impact: Other

WCS-38025: The XML content returned by the feed URL does not have the channel element

Cause: The XML content is not RSS XML format compliant

Action: Ensure that XML returned by the feed URL is RSS XML format compliant.
Level: 1

Type: WARNING

Impact: Other

WCS-38026: The channel element of the RSS XML does not have any child elements

Cause: The XML content returned by the feed URL is invalid

Action: Ensure that the XML returned by the feed URL is RSS XML format compliant.
Level: 1

Type: WARNING

Impact: Other

WCS-39001: Unable to get portlet response (Internal Error) for portlet binding {0}.

Cause: An internal error occurred in the portlet run-time code.

Action: Check the portlet client logs to locate the cause of the problem.
Level: 1

Type: ERROR

Impact: Other

WCS-39002: The binding context for this request is null.

Cause: An internal error occurred in setting the context for the request.

Action: Check if the page definition exists for this page and the request is correctly passing through the adfBinding filter, where bindingcontext is created. You can see this error for log level finer, when the application does not have any Model objects.
Level: 1

Type: ERROR

Impact: Other

WCS-39003: Unable to get the binding container for page {0}.

Cause: The application was unable to load the page definition for the requested page.

Action: Check whether the page definition for page {0} is properly defined.
Level: 1

Type: ERROR

Impact: Other

WCS-39251: Unable to process portlet action for portlet binding {0}.

Cause: An exception occurred during the processing of a portlet action in the portlet client.

Action: Check the portlet client logs for portlet binding {0}.
Level: 1

Type: ERROR

Impact: Other

WCS-39252: Unable to access the portlet container.

Cause: A failure occurred trying to access the portlet container. It could be a configuration problem where the run time is not able to locate the registered producer metadata.

Action: Check the portlet run-time logs and confirm your configuration (MDS path location) in adf-config.xml.
Level: 1

Type: ERROR

Impact: Other

WCS-39253: Unable to get the portlet with instance ID {0} from the container for portlet binding {1}.

Cause: The portlet instance was stale or unavailable in the list of portlet instances from the registered producer.

Action: Confirm whether the portlet instance ID {0} is correct and has not been modified. Try removing the portlet and associated portlet bindings {1} from the page and page definition and add this portlet to the page again.
Level: 1

Type: ERROR

Impact: Other

WCS-39254: Runnable portlet for portlet instance {0} for portlet binding {1} is null.

Cause: This error occurred due to some internal errors in the portlet client.

Action: Check the portlet client logs for this error and take appropriate action.
Level: 1

Type: ERROR

Impact: Other

WCS-39255: Unable to get portlet response for portlet instance ID {0} for portlet binding {1}.

Cause: Errors have occurred in the Portlet runtime while getting the portlet response. The Stack trace for the actual error should be able to provide more information about the cause of error.

Action: Check the portlet client logs for the cause and action of this error.
Level: 1

Type: ERROR

Impact: Other

WCS-39256: Unable to find the public parameter {0} for portlet binding {1}.

Cause: The public parameter {0} defined in the portlet binding {1} did not match the available portlet public parameters.

Action: Check the public parameter exposed by the portlet and make sure the public parameters used in the portlet bindings are the same as the one available in the portlet.
Level: 1

Type: ERROR

Impact: Other

WCS-39257: Unable to set portlet mode {0} for portlet binding {1}

Cause: An exception occurred in the portlet run-time client.

Action: Check the portlet run-time client logs.
Level: 1

Type: ERROR

Impact: Other

WCS-39258: Unable to set the portlet window state {0} for the portlet view component {1}.

Cause: An exception occurred in the portlet run-time client.

Action: Check the portlet run-time client logs.
Level: 1

Type: ERROR

Impact: Other

WCS-39259: Unable to process the portlet action for the portlet component {0} exception {1}.

Cause: An exception occurred during the processing of a portlet action in the portlet client.

Action: Check the portlet client logs for the portlet component {0}.
Level: 1

Type: ERROR

Impact: Other

WCS-39260: Unable to get the portlet binding object for the portlet component {0}.

Cause: Run time was not able to evaluate the value attribute of the portlet tag.

Action: Check the value attribute of the portlet tag and ensure it is defined properly in the associated page definition.
Level: 1

Type: ERROR

Impact: Other

WCS-39261: Portlet bindings object {0} is not properly defined for the portlet view component {1} (not of type portlet binding).

Cause: The portlet binding (value) defined for portlet component {0} is of an illegal type.

Action: Check whether the portlet binding defined for the portlet component {0} is pointing to the PortletBinding element in the page definition.
Level: 1

Type: ERROR

Impact: Other

WCS-39262: Unable to get portlet binding object {0} from page {1}.

Cause: The portlet servlet was not able to locate the portlet bindings from the supplied information.

Action: Check if the value attribute of the portlet tag is correctly defined and a PortletBinding of that object exists in the page defs. Also ensure that ADFPhaseListener (or its subclasses) are registered in the lifecycle phase listener in your application faces-config.xml.
Level: 1

Type: ERROR

Impact: Other

WCS-39263: Unknown error for portlet instance Id {0} exception {1}.

Cause: Errors have occurred in the Portlet runtime while getting the portlet response. The Stack trace for the actual error should be able to provide more information about the cause of error.

Action: Check portlet client logs for the cause and action of this error.
Level: 1

Type: ERROR

Impact: Other

WCS-39264: Portlet bindings are null for portlet component {0}.

Cause: Run time was not able evaluate the value attribute of the portlet tag.

Action: Check the value attribute of the portlet tag and ensure it is defined properly in the associated page definition.
Level: 1

Type: ERROR

Impact: Other

WCS-39265: Unable to get portlet response (time-out) for portlet binding {0}.

Cause: Timeout occurred while performing a task at the producer side. This can happen if some tasks at the producer are taking longer than the timeout specified for the registered producer.

Action: Edit the registration details for this producer and increase the timeout entry.
Level: 1

Type: ERROR

Impact: Other

WCS-39266: Unable to get portlet metadata naming policy.

Cause: The portlet metadata naming policy class could not be initialized.

Action: The default naming policy will be used unless the resource META-INF/portlet/ADFPortletNamingPolicy is accessible and contains the name of a valid naming policy class.
Level: 1

Type: ERROR

Impact: Other

WCS-39267: Portlet binding was not refreshed.

Cause: The portlet binding was not refreshed when it was accessed by the portlet view component to which it is bound.

Action: Check that the refresh option on the portlet binding is not set to Never.
Level: 1

Type: ERROR

Impact: Other

WCS-39268: Page variable {0} not defined in page definition {1}.

Cause: The named page variable which is referenced by the parameter definition of a PortletBinding is not defined.

Action: Verify that the Portlet parameter page variable declarations in the page definition are correct.
Level: 1

Type: ERROR

Impact: Other

WCS-39269: FullPageModeRequest object not found on Portlet UIComponent {0}

Cause: The request object required to forward to Portlet full page modes is missing from the Portlet UIComponent.

Action: This is an internal error. The redirect to the full page mode will still occur but some information, such as stylesheet information may be missing when the full page mode is rendered.
Level: 1

Type: ERROR

Impact: Other

WCS-39270: Invalid request made to the portlet servlet.

Cause: A request was made to the portlet servlet for a full page mode rendition or for portlet iframe content but the request parameters and / or information stored in the session were incomplete or incorrect.

Action: Portlet authors should ensure that all links or form action URLs back to the portlet are created using the appropriate portlet API.
Level: 1

Type: ERROR

Impact: Other

WCS-39501: Unable to create portlet parameter {0} with associated page variable {1} for portlet binding {2}.

Cause: Portlet parameter name {0} or associated page variable {1} for portlet binding {2} was not defined or was null.

Action: Check the portlet parameter name {0} or associated page variable {1} in portlet binding {2}. If they are properly defined, they should use name and pageVariable with non-null string values.
Level: 1

Type: WARNING

Impact: Other

WCS-39502: Unable to find variable manager for page definition {0}.

Cause: The variable manager was not defined in the page definition.

Action: Check the page definition {0} and ensure that page variables are being used and that the VariableIterator element is available inside executable binding section.
Level: 1

Type: WARNING

Impact: Other

WCS-39503: ADF lifeCycle does not execute properly for portlet bindings {0}.

Cause: The ADF lifeCycle terminated abruptly.

Action: Check log files for any errors that occurred during the execution life cycle on other resources in the page definition.
Level: 1

Type: WARNING

Impact: Other

WCS-39504: Warning: Runnable portlet for portlet instance {0} for portlet binding {1} is null, trying to get again.

Cause: This error was due to some internal errors from the portlet client.

Action: Check portlet client logs for this error and take the appropriate action.
Level: 1

Type: WARNING

Impact: Other

WCS-39505: Unable to create portlet event {0} with associated payload {1} for portlet binding {2}.

Cause: Portlet parameter event {0} or associated payload {1} for portlet binding {2} was not defined or was null.

Action: Check the portlet event name {0} or associated payload {1} in portlet binding {2}. If they are properly defined, they should use name and payload with non-null string values.
Level: 1

Type: WARNING

Impact: Other

WCS-39507: Iframe content request checksum verification failed.

Cause: The checksum verification of the parameters in the request for Portlet markup in the iframe has failed.

Action: This may indicate that a deliberately modified request for Portlet content has been made.
Level: 1

Type: WARNING

Impact: Other

WCS-39508: Portlet mode change unauthorized. Portlet {0} bound to PortletBinding {1}; Requested mode: {2}

Cause: A portlet mode change was requested but the user does not have permission to access that mode.

Action: The mode change may have been via mode change links rendered by the Portlet.
Level: 1

Type: WARNING

Impact: Other

WCS-40001: Configuration error: property "{0}".

Cause: The named configuration property has a invalid value.

Action: Correct the value of the property.
Level: 1

Type: ERROR

Impact: Configuration

WCS-40002: Configuration error: property "{0}" value "{1}" is not an integer.

Cause: The named configuration property does not have an integer value.

Action: Specify an integer value for the named property.
Level: 1

Type: ERROR

Impact: Configuration

WCS-40003: Configuration error: property "{0}" invalid value "{1}".

Cause: The named configuration property has a invalid value.

Action: Correct the value of the property.
Level: 1

Type: ERROR

Impact: Configuration

WCS-40004: Configuration error: property "{0}" value "{1}" is not a number.

Cause: The named configuration property does not have a numeric value.

Action: Specify a numeric value for the named property.
Level: 1

Type: ERROR

Impact: Configuration

WCS-40009: {0} element without a name or default='true'.

Cause: User or subscriber cache partition settings are being defined for an unnamed entity.

Action: Specify a name or declare the element as defining default values.
Level: 1

Type: ERROR

Impact: Configuration

WCS-40010: Parameter {0} specifies an unrecognized cache level: {1}.

Cause: A cache configuration parameter uses an invalid cache level.

Action: Correct the parameter such that it uses a cache level of either 'system' or 'user'.
Level: 1

Type: ERROR

Impact: Configuration

WCS-40011: Invalid cache configuration parameter: {0}.

Cause: A configuration parameter starting with 'cache.' has an invalid name.

Action: Correct the parameter name.
Level: 1

Type: ERROR

Impact: Configuration

WCS-40014: Unable to open Java Object Cache.

Cause: Java Object Cache failed to open.

Action: Examine the Java Object Cache log file to determine the cause.
Level: 1

Type: ERROR

Impact: Other

WCS-40015: Object {0} is too big to cache in region {1}.

Cause: Portlet content cannot be cached because it is too large.

Action: Reconfigure the cache such that enough space is available for the content.
Level: 1

Type: ERROR

Impact: Other

WCS-40016: Unable to insert data into cache region {0} using key {1}.

Cause: An error occurred while trying to cache portlet content.

Action: Examine the Java Object Cache log file to determine the cause.
Level: 1

Type: ERROR

Impact: Other

WCS-40017: Unable to access cache to get entry for {0}.

Cause: An error occurred while trying to retrieve content from the cache.

Action: Examine the Java Object Cache log file to determine the cause.
Level: 1

Type: ERROR

Impact: Other

WCS-40018: Unable to access cache to remove entry for {0}.

Cause: An error occurred while trying to remove content from the cache.

Action: Examine the Java Object Cache log file to determine the cause.
Level: 1

Type: ERROR

Impact: Other

WCS-40021: Configuration error: property "{0}" cannot be greater than property "{1}".

Cause: The named configuration properties have invalid values.

Action: Correct the values of the properties.
Level: 1

Type: ERROR

Impact: Configuration

WCS-40022: Configuration error: property "{0}" cannot be less than property "{1}".

Cause: The named configuration properties have invalid values.

Action: Correct the values of the properties.
Level: 1

Type: ERROR

Impact: Configuration

WCS-40024: Timing out task: {0}.

Cause: A task took too long to complete.

Action: If the problem persists, increase the timeout period for the task.
Level: 1

Type: WARNING

Impact: Threads

WCS-40025: Muffling exception in method {0}, context = {1}.

Cause: An error occurred but processing was allowed to continue.

Action: Use the context information to determine if remedial action is required.
Level: 1

Type: WARNING

Impact: Other

WCS-40026: Invalid client id "{0}" for portlet resource request handle "{1}".

Cause: A portlet resource request contained an invalid client id.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40027: Error proxying resource.

Cause: An unexpected error occurred while proxying a request for a portlet resource.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40029: Error accessing ADF configuration.

Cause: The portlet client was unable to access ADF configuration information.

Action: Examine the associated stack trace to resolve the issue.
Level: 1

Type: WARNING

Impact: Configuration

WCS-40030: Cannot export portlet {0} because it is a producer offered portlet.

Cause: An attempt has been made to export a producer offered portlet.

Action: Remove the offered portlet from the export set.
Level: 1

Type: ERROR

Impact: Other

WCS-40031: Unexpected portlet (handle = {0}) in group {1} for producer {2}.

Cause: The producer returned a portlet in an export set that was not requested by the client.

Action: Check the producer's log file to determine that it is functioning correctly.
Level: 1

Type: WARNING

Impact: Other

WCS-40032: Failed to export portlets with handles: {0}. Reason given by producer was: {1}.

Cause: A producer was unable to export one or more portlets.

Action: Resolve the issue given by the producer as the reason for the failure and retry the export.
Level: 1

Type: WARNING

Impact: Other

WCS-40033: Producer {0} does not support the WSRP ImportPortlets operation. Unable to proceed with import using API.

Cause: An attempt was made to import data obtained using the WSRP ExportPortlets operation into a producer that does not support the ImportPortlets operation.

Action: The client will fall back to importing portlets by cloning. Enable ImportPortlets on the producer to import portlets using the API.
Level: 1

Type: WARNING

Impact: Other

WCS-40034: Error calling producer to import portlets for export group {0}.

Cause: The producer failed to import a group of portlets.

Action: Examine the associated exception and producer logs to resolve the issue.
Level: 1

Type: WARNING

Impact: Other

WCS-40035: Unexpected portlet with ID {0} in ImportPortletResponse.

Cause: The producer returned a portlet in an import response that was not requested by the client.

Action: Check the producer's log file to determine that it is functioning correctly.
Level: 1

Type: WARNING

Impact: Other

WCS-40040: Error calling producer to delete portlet handle {0} overwritten during import.

Cause: A call to the producer to delete a portlet failed.

Action: Delete the portlet manually if possible.
Level: 1

Type: WARNING

Impact: Other

WCS-40041: Unable to import portlet with ID {0}.

Cause: A portlet with the same ID already exists but is based on a different offered portlet.

Action: Remove the existing portlet and retry the import operation.
Level: 1

Type: WARNING

Impact: Other

WCS-40042: Failed to import portlets with IDs: {0}. Reason given by producer was: {1}.

Cause: A producer was unable to import one or more portlets.

Action: Resolve the issue given by the producer as the reason for the failure and retry the import.
Level: 1

Type: WARNING

Impact: Other

WCS-40046: Filter unable to modify markup.

Cause: An exception caused filtering of portlet markup to fail.

Action: Examine the associated exception to resolve the issue.
Level: 1

Type: WARNING

Impact: Other

WCS-40047: Could not load markup filter {0}. Portlet markup cannot be filtered.

Cause: An error prevented a portlet markup filter from being created.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40050: Unexpected content type "{0}" in {1} response.

Cause: The producer responded with a content type the client was not expecting.

Action: Consult the producer's log file to determine why the incorrect content type was used.
Level: 1

Type: ERROR

Impact: Other

WCS-40052: WSRP producer {0} supports the export feature but does not support export by value. Portlets will be exported by cloning.

Cause: The producer supports the export feature but does not support export by value.

Action: If possible, enable the export by value feature on the producer.
Level: 1

Type: WARNING

Impact: Other

WCS-40053: WSRP v2 style import failed for producer {0}. Will attempt import by cloning.

Cause: An attempt to import portlets by calling the producer's ImportPortlets operation failed.

Action: Consult the client and producer logs to determine why the import failed.
Level: 1

Type: WARNING

Impact: Other

WCS-40055: Error processing initSession for producer {0}.

Cause: Invoking a WSRP producer's InitCookie operation failed.

Action: Consult the producer's log file to determine the cause of the failure.
Level: 1

Type: WARNING

Impact: Other

WCS-40057: Ignoring remote producer requery handle: {0}.

Cause: This feature is not implemented.

Action: No action required.
Level: 1

Type: WARNING

Impact: Other

WCS-40058: ID {0} not found.

Cause: An ID requested for export does not correspond to an object.

Action: Verify that the ID is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-40059: ID {0} is not for a producer or portlet.

Cause: An ID requested for export does not correspond to a producer or a portlet. Only producers and portlets can be exported.

Action: Correct the ID or remove it from the export request.
Level: 1

Type: ERROR

Impact: Other

WCS-40060: Error during export. input mds repository file path = {0}. output mds repository file path = {1}. input connections file path and name = {2}. export ID = {3}. producer/portlet IDs to export: {4}.

Cause: An exception was thrown during an export operation.

Action: Examine the exception and resolve the issue that caused the failure.
Level: 1

Type: ERROR

Impact: Other

WCS-40061: Error during import. input mds repository file path = {0}. output mds repository file path = {1}. output connections file path and name = {2}. export ID = {3}.

Cause: An exception was thrown during an import operation.

Action: Examine the exception and resolve the issue that caused the failure.
Level: 1

Type: ERROR

Impact: Other

WCS-40062: No object with ID {0}.

Cause: An ID does not correspond to an object.

Action: Verify that the ID is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-40063: Object with ID {0} expected type {1} actual type {2}.

Cause: An ID does not correspond to an object of the expected type.

Action: Verify that the ID and expected type are correct.
Level: 1

Type: ERROR

Impact: Other

WCS-40064: Parse error : unknown element "{0}".

Cause: An internal error occurred.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40065: Parse error : unknown attribute "{0}".

Cause: An internal error occurred.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40066: Source portlet ID = "{0}" not found when attempting to create copy name = "{1}" ID = "{2}".

Cause: An ID does not correspond to an object.

Action: Verify that the ID is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-40067: Future.get() returned null [activity {0}].

Cause: An internal error occurred.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40068: Future.get() returned type "{0}" expected "{1}".

Cause: An internal error occurred.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40069: Could not import portlet with ID "{0}".

Cause: A suitable offered portlet could not be found.

Action: Check that the producer that owns the imported portlet is properly registered.
Level: 1

Type: ERROR

Impact: Other

WCS-40070: Portlet lists differ between locale {0} and {1}.

Cause: The remote producer returned unexpected portlets for a particular locale.

Action: Check that the remote producer is functioning correctly.
Level: 1

Type: ERROR

Impact: Other

WCS-40071: Portlet {0} has no definition.

Cause: An attempt was made to create a RunnablePortletBean based on a PortletBean without a definition.

Action: Associate a PortletDef with the PortletBean before creating a RunnablePortletBean.
Level: 1

Type: ERROR

Impact: Other

WCS-40072: Mode {0} not allowed on producer offered portlets.

Cause: An attempt was made to change to a invalid mode for a producer offered portlet.

Action: Only use this mode for non-offered portlets.
Level: 1

Type: ERROR

Impact: Other

WCS-40073: Invalid portlet rendition generated.

Cause: An internal error occurred.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40074: Could not import producer with ID "{0}" because that ID is already used by an object of a different type "{1}".

Cause: The ID given for an imported producer is in use.

Action: If possible, use a different ID for the imported producer.
Level: 1

Type: ERROR

Impact: Other

WCS-40075: Could not import portlet with ID "{0}" because that ID is already used by an object of a different type "{1}".

Cause: The ID given for an imported portlet is in use by an object which is not a portlet.

Action: If possible, use a different ID for the imported portlet.
Level: 1

Type: ERROR

Impact: Other

WCS-40076: Could not import portlet with ID "{0}" because that ID is already used by a portlet with a different producerPortletId. Importing producerPortletId = "{1}", existing producerPortletId = "{2}".

Cause: The ID given for an imported portlet is in use by a portlet based on a different producer offered portlet.

Action: If possible, use a different ID for the imported portlet.
Level: 1

Type: ERROR

Impact: Other

WCS-40077: Could not import portlet with ID "{0}" because that ID is already used by a portlet belonging to a different producer with ID "{1}".

Cause: The ID given for an imported portlet is in use by a portlet belonging to a different producer.

Action: If possible, use a different ID for the imported portlet.
Level: 1

Type: ERROR

Impact: Other

WCS-40078: Errors during transport: {0}.

Cause: The portlet producer reported errors during an export or import operation.

Action: Refer to the errors reported by the producer.
Level: 1

Type: ERROR

Impact: Other

WCS-40079: SOAP Exception Fault Code = {0}

Cause: The portlet producer raised a SOAP fault in response to a request.

Action: Refer to the error reported by the producer.
Level: 1

Type: ERROR

Impact: Other

WCS-40080: Unexpected input of type {0} passed to the {1} pipe.

Cause: An internal error occurred.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40081: Unexpected output of type {0} passed to the {1} pipe.

Cause: An internal error occurred.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40082: Could not create a runnable for portlet {0}.

Cause: An internal error occurred.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40083: Error copying portlet {0}.

Cause: An internal error occurred.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40084: Error returned from prepareRendition(): {0}

Cause: An error occurred while preparing portlet markup.

Action: Use the reported error message to resolve the issue.
Level: 1

Type: ERROR

Impact: Other

WCS-40085: JNDI lookup failed for {0}.

Cause: Looking up an object using the Java Naming and Directory Interface failed.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40086: Unable to obtain interaction for producer {0}.

Cause: An internal error occurred.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40087: WSRP registration returned null producer.

Cause: An internal error occurred.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40088: {0}Pipe caught exception: {1}: {2}

Cause: An internal error occurred.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40089: WSRP producer returned markup but did not specify a MIME type.

Cause: The producer behaved in an unexpected way.

Action: Contact the producer's administrator.
Level: 1

Type: WARNING

Impact: Compliance

WCS-40090: WSRP producer returned both {0} and {1}. The {2} field will be ignored.

Cause: The producer behaved in an unexpected way by returning values for mutually exclusive fields.

Action: Contact the producer's administrator.
Level: 1

Type: WARNING

Impact: Compliance

WCS-40091: Parse error processing SOAP response: {0}

Cause: The portlet client was unable to process a response it received from a producer.

Action: Check the producer URL and verify that the producer is running. Alternatively, contact the producer's administrator.
Level: 1

Type: ERROR

Impact: Requests/Responses

WCS-40092: Web producer responded with an error: {0} (Fault code: {1})

Cause: The portlet client received an error in response to a request to a producer.

Action: Check the producer URL and service ID. Alternatively, contact the producer's administrator.
Level: 1

Type: ERROR

Impact: Requests/Responses

WCS-40093: An I/O error occurred while contacting a producer.

Cause: The portlet client was unable to successfully communicate with the producer.

Action: Examine the stack trace associated with this message to determine the root cause.
Level: 1

Type: ERROR

Impact: Network

WCS-40094: Portlet instance "{0}" already exists.

Cause: An attempt was made to create a portlet with a name that is already in use.

Action: Retry the operation using a different name.
Level: 1

Type: ERROR

Impact: Other

WCS-40095: Unable to locate connection: {0}.

Cause: A connection used for a producer cannot be found.

Action: Check that the connection exists.
Level: 1

Type: ERROR

Impact: Other

WCS-40096: Unable to locate URL connection: {0}.

Cause: A URL connection used by a producer connection cannot be found.

Action: Check that the URL connection exists.
Level: 1

Type: ERROR

Impact: Other

WCS-40097: Error processing notification of {0} operation for object {1}.

Cause: A portlet operation succeeded but notification of a listener failed.

Action: Examine the stack trace associated with this message to determine the root cause.
Level: 1

Type: ERROR

Impact: Other

WCS-40098: Unsupported WSRP service version: {0}.

Cause: An attempt was made to use a WSRP service of an supported version.

Action: Use a version of the WSRP service that is supported or upgrade the portlet client.
Level: 1

Type: ERROR

Impact: Compliance

WCS-40099: No suitable WSRP ports found in WSDL at {0}.

Cause: An attempt was made to use a WSDL document that does not define any WSRP ports that are compatible with this version of the portlet client.

Action: Verify that the URL for the WSRP WSDL document is correct and that the document is valid.
Level: 1

Type: ERROR

Impact: Compliance

WCS-40100: WSRP producer responded with an error ({0}).

Cause: The portlet client received an error in response to a request to a producer.

Action: Examine the stack trace associated with this message to determine the cause.
Level: 1

Type: ERROR

Impact: Other

WCS-40101: Cannot open Web producer connection.

Cause: An error occurred while opening a Web producer connection.

Action: Verify that the connection URL and any proxy server settings are correct.
Level: 1

Type: ERROR

Impact: Network

WCS-40102: Error setting proxy server details ({0}) for connection {1}.

Cause: There is a problem with the proxy server defined for a connection.

Action: Correct the proxy server details for the connection.
Level: 1

Type: ERROR

Impact: Network

WCS-40103: HTTP {0} request to URL {1} failed with status code {2} reason {3}. Check that the producer URL has been correctly specified, that the producer server machine and producer container are running, that the producer application is deployed correctly, and that the client can reach the server if behind a firewall.

Cause: There was a problem communicating over HTTP to a remote producer.

Action: Check that the producer URL has been correctly specified, that the producer server machine and producer container are running, that the producer application is deployed correctly, and that the client can reach the server if behind a firewall. Also check that the producer server has no errors.
Level: 1

Type: ERROR

Impact: Network

WCS-40104: HTTP error

Cause: There was a problem communicating over HTTP to a remote producer.

Action: Check that the producer URL has been correctly specified, that the producer server machine and producer container are running, that the producer application is deployed correctly, and that the client can reach the server if behind a firewall. Lastly check that the producer server has no errors.
Level: 1

Type: ERROR

Impact: Network

WCS-40105: Remote error

Cause: There was an error on the remote producer server.

Action: Check the remote producer server logs for further details.
Level: 1

Type: ERROR

Impact: Other

WCS-40106: Client queue full.

Cause: This request was rejected because the client portlet request queue was full.

Action: Resubmit the request, or if this persists consider increasing the configured queue size.
Level: 1

Type: ERROR

Impact: Other

WCS-40107: Client request time out.

Cause: The client portlet request took too long to complete and so was timed out. This could have been because the client was too busy, the network was slow, or the remote producer server was too busy or in error.

Action: Resubmit the request, or if this persists consider increasing the configured timeout periods.
Level: 1

Type: ERROR

Impact: Other

WCS-40108: Client producer connection not found.

Cause: The client producer connection was not found in connections.xml.

Action: Create the producer connection.
Level: 1

Type: ERROR

Impact: Other

WCS-40109: Client metadata error.

Cause: An internal error occurred.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40110: Error

Cause: An internal error occurred.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40111: Invalid Keystore Type ({0}).

Cause: The valid keystore types are JKS and PKCS12.

Action: Correct the keystore type given for the connection.
Level: 1

Type: ERROR

Impact: Configuration

WCS-40112: Content type error.

Cause: The portlet response was of the wrong content type.

Action: This may indicate that the producer is returning an error, or that the URL registered is incorrect and not actually a producer URL, Check the registration and producer server logs.
Level: 1

Type: ERROR

Impact: Other

WCS-40113: External Application : {0} does not exist.

Cause: The external application does not exist.

Action: Verify that the external application specified in the registration wizard exists.
Level: 1

Type: ERROR

Impact: Other

WCS-40114: Error determining disk cache status.

Cause: An error occurred while requesting the status of the caching service's disk cache.

Action: Check the caching service's configuration and log file.
Level: 1

Type: ERROR

Impact: Other

WCS-40115: Error reading exception from byte array.

Cause: An internal error occurred.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40116: Error writing exception to byte array.

Cause: An internal error occurred.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40117: The portlet attempted to issue a redirect in response to a render request. Redirect URL: {0}.

Cause: The portlet attempted to redirect the browser window in response to a render request.

Action: This operation is not allowed in an Oracle WebCenter application. A portlet may only issue a redirect in response to a user interaction directly within the portlet. Contact the portlet developer.
Level: 1

Type: ERROR

Impact: Other

WCS-40118: The parameter {0} may not be used in conjunction with wsrp-urlType {1}. The parameter will be ignored.

Cause: The WSRP portlet markup contained an incorrectly formatted wsrp_rewrite token.

Action: Contact the portlet developer.
Level: 1

Type: WARNING

Impact: Compliance

WCS-40119: The WSRP service defined by {0} is not compatible with this version of the portlet client.

Cause: The portlet client could not communicate with the remote producer using WSRP. This may be because the WSRP service implements a pre-release version of the WSRP 2.0 specification.

Action: If possible, update the WSRP container that is running the service.
Level: 1

Type: ERROR

Impact: Compliance

WCS-40120: External application not found.

Cause: The portlet is configured on the client with an external application, however the application or user credential for it was not found.

Action: Correct the portlet configuration, external application configuration, or user.
Level: 1

Type: ERROR

Impact: Other

WCS-40121: External application authentication failed.

Cause: The portlet is associated with an external application, however the user credentials failed authentication.

Action: Correct the user credentials.
Level: 1

Type: ERROR

Impact: Other

WCS-40122: ADF context get connections context failed.

Cause: An unexpected error occurred.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40123: Portlet transfer not supported for transfer mode {0}.

Cause: An MDS transfer was performed that included portlet metadata but is not supported by the portlet MDS transfer listener.

Action: No action required.
Level: 1

Type: WARNING

Impact: Other

WCS-40124: Queue Full [cause={0} submittedTasks={1} queuedTasks={2} queueFreeSpace={3} completedTasks={4} activeThreads={5} corePoolSize={6} keepAliveTime={7} largestPoolSize={8} maxPoolSize={9} poolSize={10} isShutdown={11} isTerminated={12} isTerminating={13}]

Cause: A portlet request was submitted to be processed but the queue of portlet requests was already too large so it was rejected.

Action: If the server is under load then such warnings are fine, however if the system is not under load then the configuration settings such as thread pool size and queue size should be checked in relation to the server's hardware specification.
Level: 1

Type: WARNING

Impact: Other

WCS-40125: Possible loss of portlet customizations for producer {0} : V2 export imported to V1.

Cause: A WSRP V2 producer export may contain portlet customizations but is being imported to a V1 producer which cannot import them.

Action: Check that there are either no customizations to be imported, or that it is acceptable to not import them.
Level: 1

Type: WARNING

Impact: Other

WCS-40126: This portlet must be rendered within an IFRAME.

Cause: This portlet has declared that it must be rendered within an IFRAME. It cannot be rendered inline on an ADF page.

Action: Set the property renderPortletInIFrame on the portlet tag to "auto" or "true".
Level: 1

Type: ERROR

Impact: Other

WCS-40127: Null resource ID for portlet resource request handle "{0}"

Cause: A portlet resource request contained a null resource ID.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40128: Unable to verify or sign resource URL.

Cause: The supplied resource key is invalid.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40129: Unable to proxy request for resource with ID: "{0}" due to an incorrect checksum.

Cause: A portlet resource request was received whose URL was not generated by the portlet client.

Action: Do not attempt to modify portlet resource URLs.
Level: 1

Type: WARNING

Impact: Other

WCS-40130: Portlet {0} needs user property {1}.

Cause: A user property that a portlet requires for complete functionality is not defined in the current context.

Action: Specify a value for the missing property.
Level: 1

Type: WARNING

Impact: Other

WCS-40131: Error introspecting object of class {0}. Unable to set WSRP UserProfile data correctly.

Cause: An unexpected error occurred.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40132: Unable to set field {0} to value {1} for UserProfile bean of class {2}.

Cause: An exception was thrown while trying to set a UserProfile value.

Action: If possible, resolve the issue by setting the corresponding user property value correctly.
Level: 1

Type: ERROR

Impact: Other

WCS-40133: User attribute {0} cannot be retrieved from the identity store repository.

Cause: The identity store repository cannot provide the required information.

Action: User profile information passed to producers may be incomplete.
Level: 1

Type: WARNING

Impact: Other

WCS-40134: Unable to lookup value for user property {0}.

Cause: User profile information is not available.

Action: Verify that the identity store repository is correctly configured.
Level: 1

Type: WARNING

Impact: Other

WCS-40135: Security context is not available.

Cause: The current ADFContext does not define a security context.

Action: Verify that the application's security settings are correct.
Level: 1

Type: WARNING

Impact: Other

WCS-40136: User profile information is not available.

Cause: The current Security Context does not define user profile information.

Action: Verify that the identity store repository is correctly configured.
Level: 1

Type: WARNING

Impact: Other

WCS-40137: Unable to set field {0} to value {1} for UserProfile bean of class {2}. Expected format: {3}.

Cause: The format of data supplied for UserProfile data is incorrect.

Action: If possible, resolve the issue by setting the user property value correctly.
Level: 1

Type: ERROR

Impact: Other

WCS-40138: External Application Adapter not configured for portlets.

Cause: A portlet uses an External Application, but an adapter is not configured.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40139: Web adapter using default private key.

Cause: No private key was defined.

Action: Set the key to a random value using the 'private.key' Servlet context parameter.
Level: 1

Type: WARNING

Impact: Configuration

WCS-40140: Private key is being padded using a default character sequence.

Cause: The specified private key is too short.

Action: Make sure that the value of 'private.key' Servlet context parameter is at least 10 characters in length.
Level: 1

Type: WARNING

Impact: Configuration

WCS-40141: Resource URL checksums may not be correct across all nodes.

Cause: Data cannot be written to MDS in order to coordinate private key generation.

Action: Make sure MDS is correctly configured and writable.
Level: 1

Type: WARNING

Impact: Configuration

WCS-40142: Error removing lock following private key generation.

Cause: A exception was raised while releasing a lock.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40143: Using locally generated private key.

Cause: It was not possible to co-ordinate distributed creation of a key.

Action: If possible, resolve the issue using information in this log.
Level: 1

Type: WARNING

Impact: Other

WCS-40144: Import of producer {0} failed. The failure has been stored for possible retry.

Cause: A producer import failed, however the operation was instructed to accept and store failures for later retry rather than to fail completely.

Action: The reason for failure must be investigated and corrected, then the import retried.
Level: 1

Type: WARNING

Impact: Other

WCS-40146: Portlet session invalid.

Cause: A producer response indicated that the session was invalid.

Action: Retry the request, but if the problem persists it may indicate a problem with the producer, and the producer status and logs should be checked.
Level: 1

Type: ERROR

Impact: Other

WCS-40147: Could not import portlet with ID "{0}" because the portlet does not exist on the remote producer.

Cause: The producer being imported to is different from that exported from and does not include the specified portlet.

Action: Check if the producer being imported to is of the correct type.
Level: 1

Type: WARNING

Impact: Other

WCS-40149: Exception exporting producer with ID "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-40500: Unable to read portlet deployment descriptor from path "{0}".

Cause: The path to the portlet deployment descriptor was wrong.

Action: Check that the portlet deployment descriptor exists and is readable at the given directory.
Level: 1

Type: ERROR

Impact: Configuration

WCS-40501: Error processing deployment descriptor "{0}".

Cause: There was a problem parsing the deployment descriptor.

Action: Check that the portlet deployment descriptor conforms to the appropriate schema.
Level: 1

Type: ERROR

Impact: Configuration

WCS-40502: Null value passed to method {0}.

Cause: A null value was passed to the specified method.

Action: Check that a non-null value is passed to the specified method.
Level: 1

Type: ERROR

Impact: Programmatic

WCS-40503: Unable to load resource bundle "{0}".

Cause: The specified resource bundle could not be found.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40504: Parameter of invalid type passed to method {0}.

Cause: One of the parameters passed to the specified method was of an incorrect type.

Action: Check that the correct set of parameter types are being passed to the specified method.
Level: 1

Type: ERROR

Impact: Programmatic

WCS-40505: Unable to create instance of class "{0}".

Cause: Unable to create instance of the specified class.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40507: Unrecognized character encoding "{0}".

Cause: The specified character was not recognized.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40508: Window state "{0}" is not allowed in current context.

Cause: The specified window state is not allowed.

Action: Check that the use of the specified window state is allowed by the consumer.
Level: 1

Type: ERROR

Impact: Programmatic

WCS-40509: Portlet mode "{0}" is not allowed in current context.

Cause: The specified portlet mode is not allowed.

Action: Check that the use of the portlet mode is allowed by the consumer.
Level: 1

Type: ERROR

Impact: Programmatic

WCS-40510: Illegal call to {0}: response is already committed.

Cause: The response was already committed.

Action: Do not call the specified method on a committed response.
Level: 1

Type: ERROR

Impact: Programmatic

WCS-40511: Content type "{0}" is not allowed in current context.

Cause: The response was trying to set a content type that is not allowed by the request.

Action: Correct the portlet code.
Level: 1

Type: ERROR

Impact: Programmatic

WCS-40512: Value "{0}" not recognized as a session scope.

Cause: The specified value is an invalid value for the session scope.

Action: Use one of the session scope values defined by the javax.portlet.PortletSession interface.
Level: 1

Type: ERROR

Impact: Programmatic

WCS-40515: Portlet mode "{0}" referenced by portlet "{1}" is not defined in the deployment descriptor.

Cause: The specified portlet mode for the portlet was not defined in the portlet deployment descriptor.

Action: Check that the configuration allows for the specified mode.
Level: 1

Type: ERROR

Impact: Configuration

WCS-40516: Error initializing Java Object Cache.

Cause: Java Object Cache failed to start.

Action: Consult the Java Object Cache log file for more information.
Level: 1

Type: ERROR

Impact: Configuration

WCS-40517: Error loading preferences from path "{0}".

Cause: Preference data could not be accessed properly.

Action: Check the persistence store is configured correctly.
Level: 1

Type: ERROR

Impact: Configuration

WCS-40518: Error saving preferences to path "{0}".

Cause: Preference data could not be accessed properly.

Action: Check the persistence store is configured correctly.
Level: 1

Type: ERROR

Impact: Configuration

WCS-40519: Error deleting preferences under path "{0}".

Cause: Preference data could not be deleted.

Action: Check the persistence store is configured correctly.
Level: 1

Type: ERROR

Impact: Configuration

WCS-40520: Cannot find JNDI data source with specified name "{0}" or the Oracle Portal repository data source "{1}".

Cause: The JNDI data source in the configuration could not be found at the specified location.

Action: Check the container configuration for the data source is correct.
Level: 1

Type: ERROR

Impact: Configuration

WCS-40521: Error getting connection from data source with JNDI path "{0}".

Cause: There was an error getting the connection from the specified data source.

Action: Check that the data source referenced is available.
Level: 1

Type: ERROR

Impact: Configuration

WCS-40522: Error getting connection from Oracle Portal repository with the name "{0}".

Cause: There was an error connecting to the Oracle Portal repository.

Action: Check that the Oracle Portal repository is available.
Level: 1

Type: ERROR

Impact: Configuration

WCS-40526: An internal error has occurred in method {0}.

Cause: The specified method caused an internal error.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40530: Method {0} cannot be called after method {1}.

Cause: The specified methods were not called in the correct order.

Action: Check that the specified methods are called in the correct order.
Level: 1

Type: ERROR

Impact: Other

WCS-40531: No such portlet "{0}".

Cause: The specified portlet was not available.

Action: Check that the portlet is available.
Level: 1

Type: ERROR

Impact: Configuration

WCS-40532: Invalid handle "{0}".

Cause: Session, portlet, or registration handle specified was invalid.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40533: Illegal call to {0}: an output stream is already in use.

Cause: The specified method cannot be called once the portlet has started writing binary data.

Action: Correct the portlet code.
Level: 1

Type: ERROR

Impact: Programmatic

WCS-40534: Illegal call to {0}: a writer is already in use.

Cause: The specified method cannot be called once the portlet has started writing character data.

Action: Correct the portlet code.
Level: 1

Type: ERROR

Impact: Programmatic

WCS-40535: Illegal call to {0}: a content type has not been set.

Cause: The setContentType() method was not called before the specified method.

Action: Correct the portlet code.
Level: 1

Type: ERROR

Impact: Programmatic

WCS-40538: Error attempting to create handle "{0}".

Cause: The specified handle could not be created.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40539: Error checking for existence of handle "{0}".

Cause: The specified handle could not be found.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40540: Error attempting to delete handle "{0}".

Cause: The specified handle could not be deleted.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-40541: Portlet "{0}" is not modifiable in this context.

Cause: The specified portlet is read only in this context.

Action: Check that the portlet is modifiable.
Level: 1

Type: ERROR

Impact: Programmatic

WCS-40542: Invalid URL "{0}".

Cause: The specified URL is invalid.

Action: Correct the portlet code.
Level: 1

Type: ERROR

Impact: Programmatic

WCS-40543: Unable to read Web application deployment descriptor from path "{0}".

Cause: The path to the Web application deployment descriptor was incorrect.

Action: Check that the Web application deployment descriptor exists and is readable at the given directory.
Level: 1

Type: ERROR

Impact: Configuration

WCS-40544: Value "{1}" for JNDI environment entry "{0}" is not supported. Allowable values are "{2}".

Cause: The JNDI environment entry was not one of the allowable values specified.

Action: Check the JNDI environment entry is one of the allowable values specified.
Level: 1

Type: ERROR

Impact: Configuration

WCS-40545: Location specified for persistent store "{0}" must be a directory.

Cause: The location of the specified persistent store is not a directory.

Action: Check the specified persistent store is a directory and that there is not a file in existence at the given location.
Level: 1

Type: ERROR

Impact: Configuration

WCS-40546: Unable to create persistent store root directory at "{0}".

Cause: It was not possible to create the persistent store root directory at the specified location.

Action: Check that the parent directory is writable.
Level: 1

Type: ERROR

Impact: Configuration

WCS-40547: Cannot resolve relative path ({0}) for persistent store, oracle.home system property is not set.

Cause: The oracle.home was not set for the specified relative path.

Action: Set the oracle.home system property.
Level: 1

Type: ERROR

Impact: Configuration

WCS-40548: Error connecting to database {0}/{1}@{2}.

Cause: There is an error connecting to the specified database.

Action: Check that the specified database connection details are correct.
Level: 1

Type: ERROR

Impact: Configuration

WCS-40549: Error obtaining details of persisted objects.

Cause: There was an error obtaining details of persisted objects.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Data

WCS-40550: Unexpected database error.

Cause: An unexpected database error occurred.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Data

WCS-40551: Unable to create persistent store directory "{0}" for group "{1}".

Cause: It was not possible to create the persistent store directory for the specified group.

Action: Check that the parent directory is writable.
Level: 1

Type: ERROR

Impact: Configuration

WCS-40552: Unable to read mime mappings from path "{0}".

Cause: The path to the mime mappings file was wrong.

Action: Check that the mime mappings file exists and is readable at the given directory.
Level: 1

Type: ERROR

Impact: Configuration

WCS-40554: Portlet with handle "{0}" is hidden.

Cause: The portlet entity was hidden and not currently available.

Action: Make sure the portlet is made available if that is the desired usage.
Level: 1

Type: ERROR

Impact: Configuration

WCS-40555: Error processing file "{0}" at line {1} column {2}.

Cause: An error occurred while processing the file at the specified line and column.

Action: Fix the error to the file based on the message specified.
Level: 1

Type: ERROR

Impact: Configuration

WCS-40556: Object named "{0}" could not be found in the persistent store.

Cause: Container object could not be found in the persistent store.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Data

WCS-40561: Request timed out while shutting down portlet "{0}".

Cause: A timeout occurred while waiting for a portlet to shutdown.

Action: No action required.
Level: 1

Type: WARNING

Impact: Other

WCS-40562: Exception thrown while shutting down portlet "{0}".

Cause: The specified portlet raised an exception while it was being shutdown.

Action: Resolve the issue if possible by looking at the exception raised.
Level: 1

Type: WARNING

Impact: Other

WCS-40563: Exception thrown while deleting entity "{0}".

Cause: The specified entity raised an exception while it was being deleted.

Action: Resolve the issue if possible by looking at the exception raised.
Level: 1

Type: WARNING

Impact: Other

WCS-40564: Exception thrown while releasing session with handle "{0}".

Cause: The specified session raised an exception while is was being released.

Action: Resolve the issue if possible by looking at the exception raised.
Level: 1

Type: WARNING

Impact: Other

WCS-40565: Invalid security role reference: "{0}".

Cause: The security role specified is invalid.

Action: Check and reconfigure the security roles set for the portlets.
Level: 1

Type: WARNING

Impact: Configuration

WCS-40566: Locale "{0}" can only be matched to "{1}" Resource Bundle.

Cause: The locale requested by the client is not supported at the language level by the portlet. Fallback to English or Base bundle has occurred.

Action: The portlet must support the locale in the request.
Level: 1

Type: WARNING

Impact: Configuration

WCS-40570: The oracle.portlet.server.useStatelessProxying request attribute is being ignored when creating a resource URL.

Cause: Stateless proxying is not possible for resources served using the ResourceServingPortlet.serveResource() method.

Action: Use the RenderResponse.encodeURL() method to create the resource URL.
Level: 1

Type: WARNING

Impact: Other

WCS-40571: The oracle.portlet.server.useStatelessProxying request attribute is being ignored when creating a resource URL.

Cause: Stateless proxying is not possible for resources that require URL rewriting.

Action: If URL rewriting of the resource response is not required, set the oracle.portlet.server.resourceRequiresRewriting response attribute to false.
Level: 1

Type: WARNING

Impact: Other

WCS-40572: Portlet with handle "{0}" cannot be accessed using WSRP version {1}, it requires at least WSRP version {2}.

Cause: The portlet uses features that are not supported by the version of the WSRP protocol being used to access it.

Action: Check that the WSRP producer is accessed using the minimum protocol version (or higher).
Level: 1

Type: ERROR

Impact: Configuration

WCS-40573: Fast Connection Failover detected. Retrying operation once.

Cause: The portlet container detected that the database used for personalization has performed Fast Connection Failover. The portlet container will retry the operation once.

Action: Contact the database administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-40574: Java Object Cache support configured for this portlet application, but no display name specified in web.xml. Java Object Cache support will be disabled.

Cause: Java Object Cache support has been configured to persist portlet registration and preference data, but no display name has been configured for the portlet application in web.xml. Java Object Cache support will be disabled for this portlet application.

Action: Specify a unique display-name for this portlet application in web.xml
Level: 1

Type: ERROR

Impact: Configuration

WCS-40575: PortletApplicationImpl.initHandler error processing config handler "{0}".

Cause: Error processing the specified config handler.

Action: Check the JNDI environment entry mentioned.
Level: 1

Type: ERROR

Impact: Configuration

WCS-40576: PortletApplicationImpl.initHandler error calling config handler setters "{0}" and "{1}".

Cause: Error calling the specified config handler setters.

Action: Check the locations of these files.
Level: 1

Type: ERROR

Impact: Configuration

WCS-40577: PortletApplicationImpl.loadMimeCsMappings() error closing input stream "{0}".

Cause: The path to the mime mappings file was wrong.

Action: Check that the mime mappings file exists and is readable at the given directory.
Level: 1

Type: ERROR

Impact: Configuration

WCS-40578: PortletApplicationImpl.isConfigFileChanged error calling config handler has changed methods for "{0}" and "{1}".

Cause: Error calling the specified config handler with change methods.

Action: Check the locations of these files.
Level: 1

Type: ERROR

Impact: Configuration

WCS-42301: The external application ID {0} found while rendering the credential provisioning page is invalid.

Cause: The external application being referred was probably deleted.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

WCS-42302: No back URL exists in the process scope.

Cause: The credential provisioning page could not establish the back URL because of the following possible reasons: 1) The page was run either in the standalone mode or as a dialog. 2) There was some unexpected error while setting the back URL in the process scope.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

WCS-42303: cannot retrieve the back URL to redirect the credential provisioning page

Cause: An I/O error occurred while trying to obtain the back URL to redirect the credential provisioning page.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

WCS-42304: The external application ID is found to be null while rendering the credential provisioning page.

Cause: The credential provisioning page was probably run standalone, or it was invoked from a portlet added from a producer that was not associated with an external application.

Action: While running the credential provisioning page, ensure that: 1) It is not run in the standalone mode. 2) It is invoked from the link in portlets added from the producers associated with the external application.
Level: 1

Type: ERROR

Impact: Configuration

WCS-42305: The page is available only to authenticated users.

Cause: You had not logged into the application before accessing the external application credential provisioning page.

Action: Ensure that you have logged in before accessing the external application credential provisioning page.
Level: 1

Type: ERROR

Impact: Configuration

WCS-42306: cannot initialize credential provisioning page

Cause: An unexpected error occurred while trying to initialize the external application. Review the underlying exception in the logs for exact cause.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

WCS-42307: cannot store credentials of external application {0} for user {1}

Cause: There was an unexpected error while trying to store external application credentials for the user. Review the underlying exception in the logs for exact cause.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

WCS-42501: An unexpected error occurred.

Cause: Review the root cause of the exception for more details.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

WCS-42502: A required parameter is missing. Parameter=[{0}]

Cause: An attempt was made to invoke a method without passing all the required parameters.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

WCS-42503: call to API {0} not supported at design time

Cause: This operation was not supported at design time.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

WCS-42504: The external application context cannot be configured.

Cause: An unexpected error occurred in initializing the external application manager while setting up the context. Review the underlying exception in the logs for the exact cause.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

WCS-42505: The page is available only to authenticated users.

Cause: A null user subject was obtained while trying to automatically log in to the external application.

Action: Ensure that the user has logged into the application before accessing the automated login functionality.
Level: 1

Type: ERROR

Impact: Security

WCS-42506: An unexpected error occurred while trying to automatically log in to the external application.

Cause: An error occurred while trying to log in to the external application. Review the underlying exception in the logs for more details.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

WCS-42507: The external application that needs to be accessed cannot be found.

Cause: The external application ID was not available in the servlet request.

Action: Ensure that the external application ID is passed in the form of the extappid parameter while invoking the automated login servlet.
Level: 1

Type: ERROR

Impact: Configuration

WCS-42508: cannot automatically log in to the external application

Cause: The login URL was not specified for the external application being used for automated login.

Action: To use the automated login functionality for an external application, ensure that the login URL is specified.
Level: 1

Type: ERROR

Impact: Configuration

WCS-42509: A list of all external application connections cannot be obtained.

Cause: An unexpected error occurred while trying to obtain the list of all external application connections. Review the underlying exception in the logs to determine the exact cause.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

WCS-42510: Connection for the external application {0} cannot be obtained.

Cause: An unexpected error occurred while trying to obtain the connection for the external application. Review the underlying exception in the logs to determine the exact cause.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

WCS-42511: Cannot encode string {0} using encoding scheme {1}

Cause: Encoding Scheme was not supported

Action: Contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Logging

WCS-42512: An error occurred after notifying service of change in the external application {0} credentials.

Cause: An unexpected error occurred while the service was trying to process change in the external application credentials.

Action: Review the underlying exception in the logs. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Logging

WCS-42513: An unexpected condition occurred while trying to automatically log in to the external application {0} - {1}

Cause: A unexpected condition while trying to log in to the external application. Review the underlying exception in the logs for more details.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Logging

WCS-42601: The login URL {0} obtained for the external application {1} is invalid.

Cause: The data in the external application definition was damaged.

Action: Check the underlying connection data and ensure that the URL for the specified external application is valid.
Level: 1

Type: ERROR

Impact: Configuration

WCS-42602: The option for enabling automated login for the external application is not supported.

Cause: The login URL for the external application was not specified.

Action: To enable automated login for the external application, set the login URL for the application.
Level: 1

Type: ERROR

Impact: Programmatic

WCS-42603: cannot process authentication failure for external application {0}

Cause: Public credentials were not enabled for this external application.

Action: To obtain external application credentials for a public user, configure the external application to specify public credentials.
Level: 1

Type: ERROR

Impact: Configuration

WCS-42604: Credentials cannot be stored or deleted.

Cause: The external application identifier was not specified for the credential.

Action: Specify the external application identifier for the credential and then try to store or remove the credential.
Level: 1

Type: ERROR

Impact: Programmatic

WCS-42605: user {0} not authorized to access external application {1}

Cause: The user did not have access to the external application.

Action: Contact your administrator for the necessary permission. If you are a public user, the administrator needs to allow public access to this external application by specifying public credentials.
Level: 1

Type: ERROR

Impact: Configuration

WCS-42606: The credentials specified by the user {0} for the external application {1} are invalid.

Cause: Credentials for the external application have changed.

Action: Invoke the credential provisioning page to accept the latest set of credentials.
Level: 1

Type: ERROR

Impact: Configuration

WCS-42607: Shared access credentials for the external application {0} are invalid.

Cause: Shared access credentials for the external application may have changed.

Action: Contact the administrator to update the shared access credentials.
Level: 1

Type: ERROR

Impact: Configuration

WCS-42608: Public access credentials for external application {0} are invalid.

Cause: Public access credentials for the external application may have changed.

Action: Contact the administrator to update the public access credentials.
Level: 1

Type: ERROR

Impact: Configuration

WCS-42609: Credentials not found for the user {0} for the external application {1}.

Cause: external application credentials were not provisioned for the user.

Action: Provide a link to the credential provisioning page so that the user can specify credentials.
Level: 1

Type: ERROR

Impact: Configuration

WCS-42610: Unable to obtain shared or public credentials for the external application {0}.

Cause: The shared or public credentials might have been damaged.

Action: Contact the administrator to specify the credentials. If the error still persists, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

WCS-42613: Credentials cannot be deleted for the external application {0}.

Cause: The credential store may not have been configured correctly.

Action: Ensure that the credential store is configured correctly.
Level: 1

Type: WARNING

Impact: Logging

WCS-42614: Field {0} in external application {1} is invalid.

Cause: The external application field used for the store or fetch credential operation does not exist.

Action: Check the field name used for the operation and ensure that it has been defined.
Level: 1

Type: WARNING

Impact: Logging

WCS-42651: The listener {0} cannot be added to the external application.

Cause: An unexpected error occurred while trying to register the listener. Review the underlying exception in the logs to determine the exact cause.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

WCS-42652: The listener {0} cannot be deregistered.

Cause: An unexpected error occurred while trying to deregister the listener. Review the underlying exception in the logs to determine the exact cause.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

WCS-42653: An external application with the name {0} already exists.

Cause: The name specified for the external application was already used by another application.

Action: Specify a unique name for the external application.
Level: 1

Type: ERROR

Impact: Configuration

WCS-42654: URL {0} specified for external application {1} is invalid.

Cause: The HTTP URL set for the external application was invalid.

Action: Specify a valid HTTP URL.
Level: 1

Type: ERROR

Impact: Configuration

WCS-42655: Property {0} specified for external application {1} is invalid.

Cause: The property specified for the external application was either null or empty.

Action: Set a valid value for the specified property.
Level: 1

Type: ERROR

Impact: Configuration

WCS-42656: The authentication method {0} specified for the external application {1} is invalid.

Cause: The authentication method set for the external application was not one of the following: GET, BASIC, or POST.

Action: Set the authentication method as GET, POST, or BASIC. The default authentication method is POST.
Level: 1

Type: ERROR

Impact: Configuration

WCS-42657: Field {0} already exists in external application {1}.

Cause: A duplicate field was encountered in the additional fields definition.

Action: Ensure that the names of the additional fields defined for the external application are unique.
Level: 1

Type: ERROR

Impact: Configuration

WCS-42658: default value not specified for Field {0} in external application {1}

Cause: The specified additional field of the external application was marked as hidden.

Action: Specify a default value for the additional field marked as hidden. If there is no default value, mark the field as to be displayed to users.
Level: 1

Type: ERROR

Impact: Configuration

WCS-42659: The {0} credential specified for external application {1} is invalid.

Cause: Either the user name or password was not specified.

Action: Ensure that both the user name and password are specified for shared or public credentials in an external application.
Level: 1

Type: ERROR

Impact: Configuration

WCS-42660: external application {0} not found

Cause: The name passed for retrieving the external application was invalid or the underlying external application was deleted.

Action: Pass a valid external application name for retrieving the application.
Level: 1

Type: ERROR

Impact: Configuration

WCS-42661: The ID of the external application cannot be set.

Cause: The external application ID could not be set because the external application already had an ID set.

Action: The ID of an external application cannot be modified. To set a new ID, delete the external application and re-create the application with a new ID.
Level: 1

Type: ERROR

Impact: Programmatic

WCS-42662: The external application {0} cannot be created.

Cause: An external application with the specified name already existed.

Action: Specify a unique name for your external application.
Level: 1

Type: ERROR

Impact: Configuration

WCS-42663: The external application {0} cannot be created.

Cause: An unexpected error occurred while trying to create the external application. Review the underlying exception in the logs to determine the exact cause.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

WCS-42664: The external application {0} cannot be modified.

Cause: An unexpected error occurred while trying to modify the external application. Review the underlying exception in the logs to determine the exact cause.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

WCS-42665: cannot delete external application {0}

Cause: An unexpected error occurred while trying to delete the external application. Review the underlying exception in the logs to determine the exact cause.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

WCS-42666: An error has occurred while trying to retrieve the external application {0}.

Cause: An unexpected error occurred while trying to obtain the given external application. Review the underlying exception in the logs to determine the exact cause.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

WCS-42667: An error has occurred while trying to retrieve all available external applications.

Cause: An unexpected error occurred while trying to obtain all external applications. Review the underlying exception in the logs to determine the exact cause.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

WCS-42668: An error has occurred while trying to check if the specified external application name {0} is already used by another external application.

Cause: An unexpected error occurred while trying to check if the external application name was already used. Review the underlying exception in the logs to determine the exact cause.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

WCS-42669: An error has occurred while trying to obtain a list of external application names.

Cause: An unexpected error occurred while trying to obtain a list of external application names. Review the underlying exception in the logs to determine the exact cause.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

WCS-42670: An error has occurred while trying to obtain a map containing the ID-name pair of the external application.

Cause: An unexpected error occurred while trying to obtain a map containing the ID-name pair of the external application. Review the underlying exception in the logs to determine the exact cause.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

WCS-42671: An external application with the display name {0} already exists.

Cause: The display name specified for the external application was already used by another application.

Action: Specify a unique display name for the external application.
Level: 1

Type: ERROR

Impact: Configuration

WCS-42701: An unexpected naming exception has occurred while trying to create the external application connection {0}.

Cause: An unexpected naming exception occurred while trying to create an external application connection. Review the underlying exception in the logs to determine the exact cause.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

WCS-42702: cannot update external application connection {0}

Cause: An unexpected naming exception occurred while trying to update the external application connection. Review the underlying exception in the logs to determine the exact cause.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Logging

WCS-42703: cannot delete external application connection {0}

Cause: An unexpected naming exception occurred while trying to delete the external application connection. Review the underlying exception in the logs to determine the exact cause.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

WCS-42704: An unexpected naming exception has occurred while trying to look up the external application connection {0}.

Cause: An unexpected naming exception occurred while trying to look up the external application connection. Review the underlying exception in the logs to determine the exact cause.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

WCS-42705: An unexpected naming exception has occurred while trying to list all available external application connections.

Cause: An unexpected naming exception occurred while trying to list external application connections. Review the underlying exception in the logs to determine the exact cause.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

WCS-42706: Invalid fragment obtained while trying to build the external application connection from the reference {0}.

Cause: Could not parse the required external application connection attributes from the reference because the entry in connections.xml may have been tampered with.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

WCS-42707: An unknown error occurred while trying to obtain connections context.

Cause: An unknown exception occurred while trying to obtain connections context. Review the underlying exception in the logs to determine the exact cause.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

WCS-42708: A Connection Store cannot be configured for the external application {0}.

Cause: An unexpected error occurred while trying to set up the connection store for the application. Review the underlying exception in the logs to determine the exact cause.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

WCS-42801: An error occurred while creating a transferable object for the external application connection {0}.

Cause: An unexpected error occurred while creating a transferable object for an external application connection. Review the underlying exception in the logs to determine the exact cause.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

WCS-42802: An error occurred while generating the transfer data for the external application connection {0}. DataFlavor={1}, TransferData={2}

Cause: An unexpected error occurred while generating the transfer data for an external application connection. Review the underlying exception in the logs to determine the exact cause.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

WCS-42803: cannot initialize the Resource Catalog adapter.

Cause: An unexpected error occurred while initializing the Resource Catalog adapter. Review the underlying exception in the logs to determine the exact cause.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

WCS-43001: Unable to find the service with ID "{0}" in the service registry.

Cause: Either the service ID is wrong or the corresponding META-INF/service-definition.xml file is not available in the classpath.

Action: Ensure the service ID is correct and the corresponding META-INF/service-definition.xml file is available in the classpath. Note: service-definition.xml file is mostly available from service libraries (within .jar file) of each service, make sure the required service libraries are in the classpath.
Level: 1

Type: WARNING

Impact: Other

WCS-43002: Cannot add service to the registry with the same ID. Service with ID "{0}" is already registered from source "{1}". Failed to add service read from source "{2}".

Cause: Either the service-definition contains a service Id that conflicts with another service definition or the same service library (.jar containing the service-definition.xml) is available from multiple classpath locations.

Action: Ensure the service ID is correct in the corresponding META-INF/service-definition.xml file. Also ensure the same jar file is not available from multiple classpath locations.
Level: 1

Type: WARNING

Impact: Other

WCS-43003: Failed to parse the service-definition.xml found at location "{0}". Due to : {1}

Cause: Either the service-definition.xml does not conform to the schema or its not well-formed xml file or its not readable.

Action: Verify the corresponding service-definition.xml file conforms to the schema with well-formed xml and read access is set on it.
Level: 1

Type: WARNING

Impact: Other

WCS-43004: ServiceContext resource configuration file "{0}" not found, cannot proceed.

Cause: The main configuration file that defines the default implementation of ServiceContext class is missing.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-43005: ServiceContext resource configuration file "{0}" found, but the data is missing. Cannot proceed.

Cause: The main configuration file that defines the default implementation of ServiceContext class is misconfigured, all the required data is not available in this file.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-43006: ServiceContext resource configuration file "{0}" found, but the class defined "{1}" is not an instance of oracle.webcenter.framework.service.ServiceContext.

Cause: The main configuration file that defines the default implementation of ServiceContext class is misconfigured, the supplied class is not an instance oracle.webcenter.framework.service.ServiceContext.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-43007: service-definition being processed from source location "{0}" does not conform to the schema. Missing 'definitions' tag.

Cause: This is caused due to wrong configuration of service-definition.xml file.

Action: Update the corresponding file and ensure it starts with 'definitions' tag with namespace as 'http://xmlns.oracle.com/webcenter/framework/service' (e.g.: <definitions xmlns="http://xmlns.oracle.com/webcenter/framework/service">).
Level: 1

Type: WARNING

Impact: Other

WCS-43008: Required attribute "{0}" missing from tag "{1}".

Cause: This is caused when the user is required to set the mandatory attribute for the given tag, but and its not set.

Action: Modify the appropriate configuration file to and supply the mandatory attribute with corresponding value.
Level: 1

Type: WARNING

Impact: Other

WCS-43009: Attempt to invoke "{0}" method on class "{1}", when its locked.

Cause: This class or method is locked and cannot be invoked in the current state.

Action: Do not invoke methods on this class in a state its not accessible, please check the class documentation for more help.
Level: 1

Type: WARNING

Impact: Other

WCS-43010: Scope object cannot be null.

Cause: This is caused when an attempt is made to set scope with null value.

Action: Supply a valid scope object, or create a scope from ServiceContext.
Level: 1

Type: WARNING

Impact: Other

WCS-43011: Unable to find the "{0}" view definition from service: {1}.

Cause: The required view definition is missing from the service-definition file.

Action: Check the appropriate service-definition.xml file to have an entry of the required view definition. Refer to service documentation for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-43012: Error occurred processing the service-definition.xml file from source location "{0}". Due to: {1}.

Cause: Either the service-definition is malformed or does not conform to the schema defined.

Action: Update the corresponding service-definition.xml with correct details.
Level: 1

Type: WARNING

Impact: Other

WCS-43013: ExtensionRegistry instance found "{0}" for registry Id "{1}", is not an instance of {2} class.

Cause: This is caused due to wrong configuration of adf-service-config tag in the adf-config.xml file.

Action: Check the adf-config.xml file for an entry of adf-service-config tag. Search for extension-registry tag here with ID "oracle.webcenter.framework.service.ServiceRegistry", this tag's registry-class attribute should point to a class that is extending from ServiceRegistry class.
Level: 1

Type: WARNING

Impact: Other

WCS-43014: Either the supplied registry Class "{0}" for extension-registry ID "{1}", is not an instance of oracle.webcenter.framework.service.ExtensionRegistry or the class is not available in the classpath. Please check the adf-config.xml for corresponding configuration details.

Cause: This is caused due to wrong configuration of extension-registry in the adf-config.xml file.

Action: Check the adf-config.xml file for an entry of adf-service-config tag. Search for extension-registry tag and ensure this tag's registry-class attribute point's to a class that is an instance of 'oracle.webcenter.framework.service.ExtensionRegistry' class. Also this class should be available in the classpath, otherwise it will fail to load.
Level: 1

Type: WARNING

Impact: Other

WCS-43015: Unable to find the Extension Registry information in the adf-config for registry ID "{0}". Please check the adf-config.xml for corresponding configuration details.

Cause: This is caused due to missing tension-registry in configuration in the adf-config.xml file.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-43016: Either the supplied handler Class "{0}" for extension-registry ID "{1}", is not an instance of oracle.webcenter.framework.service.ExtensionHandle or the class is not available in the classpath. Please check the adf-config.xml for corresponding configuration details.

Cause: This is caused due to wrong configuration of extension-registry in the adf-config.xml.

Action: Check the adf-config.xml file for an entry of adf-service-config tag. Search for extension-registry tag and ensure this tag's handler-class attribute point's to a class that is an instance of 'oracle.webcenter.framework.service.ExtensionHandler' class. Also this class should be available in the classpath, otherwise it will fail to load.
Level: 1

Type: WARNING

Impact: Other

WCS-43017: Extension tag name cannot be null or empty value.

Cause: Wrong extension configuration, mandatory tag name cannot hold null or empty string.

Action: Refer to the service framework documentation for details on extension-registry configuration.
Level: 1

Type: WARNING

Impact: Other

WCS-43018: No Extension Registry information available for element type "{0}", with the ServiceRegistry. Please check the adf-config.xml for extension registry configuration details.

Cause: This is caused due to missing extension-registry configuration in the adf-config.xml for the specified registry Id.

Action: Check the adf-config.xml file for an entry of adf-service-config tag. Search for extension-registry tag for the appropriate registry Id that is missing and ensure all the registry details are provided.
Level: 1

Type: WARNING

Impact: Other

WCS-43019: ADFConfig does not contain adf-service-config details. Ensure adf-config.xml file contains adf-service-config tag with namespace : {0}.

Cause: This is caused due to missing adf-service-config tag from adf-config.xml file.

Action: Check the adf-config.xml file for an entry of adf-service-config tag.
Level: 1

Type: WARNING

Impact: Other

WCS-43020: No ADF Config information.

Cause: ADFConfig could not be acquired, either adf-config.xml file is missing or application is not configured properly.

Action: >Examine the adf-config.xml file and add or update the WebCenter section.
Level: 1

Type: ERROR

Impact: Configuration

WCS-43021: No Oracle WebCenter Framework information in adf-config file.

Cause: The application adf-config.xml was found, but the Oracle WebCenter Framework section could not be read or is missing.

Action: Examine the adf-config.xml file and add or update the WebCenter section.
Level: 1

Type: ERROR

Impact: Configuration

WCS-43022: Unable to find ResourceUriListener class: {0}.

Cause: Either the class name is wrongly configured or the class is not available in the classpath for this application to load.

Action: Examine the adf-config.xml file and add or update the WebCenter section specifying the resource Uri class.
Level: 1

Type: ERROR

Impact: Configuration

WCS-43023: Unable to instantiate ResourceUriListener class: {0}.

Cause: Either the class does not have required constructor or it fails to initialize.

Action: Ensure the supplied ResourceUri Listener class implements the proper interface and has the required constructors.
Level: 1

Type: ERROR

Impact: Programmatic

WCS-43024: Unable to access ResourceUriListener class: {0}.

Cause: This is caused when the application tries to reflectively create an instance, set or get field or invoke methods, but the currently executing method does not have access to the definition of the specified class, field, methods or constructor.

Action: Ensure that the ResourceUri Listener class implements the proper interface and all its required methods and constructors have public access.
Level: 1

Type: ERROR

Impact: Programmatic

WCS-43025: Failed to initialize specified ResourceUri Handler.

Cause: A runtime problem occurred whilst initializing the Resource handler.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-43026: No resource ID found for resource group: {0}.

Cause: This error occurs when the resource view does not define corresponding group ID.

Action: Supply valid resource group ID.
Level: 1

Type: WARNING

Impact: Other

WCS-43027: Failed to generate an absolute URL to a resource view.

Cause: A runtime problem occurred whilst generating the absolute URL to a resource view.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-43028: Scope with name "{0}" already exists.

Cause: This error occurs when user tries to create a scope with a name that is already created. Duplicate scopes are not allowed.

Action: Chose a different name for the scope.
Level: 1

Type: WARNING

Impact: Other

WCS-43029: Scope with name "{0}" does not exist.

Cause: This error occurs when user tries to read a scope with a name that is not created earlier.

Action: Create the scope with the appropriate name and then access it.
Level: 1

Type: WARNING

Impact: Other

WCS-43030: Could not handle complex element "{0}". Neither element has a class attribute nor any of the ElementTypeResolvers could handle it.

Cause: This can occur due to missing extension-registry configuration in the adf-config.xml or there is no set/add method on the corresponding application bean to handle complex node.

Action: Have a proper extension handler registered for this complex node or have set/add method on the bean with the tag name.
Level: 1

Type: WARNING

Impact: Other

WCS-43031: XML processing error: unable to create instance of the class: {0}. {1}

Cause: This can occur due to missing extension-registry configuration in the adf-config.xml or there is no set/add method on the corresponding application bean to handle complex node.

Action: Have a proper extension handler registered for this complex node or have set/add method on the bean with the tag name.
Level: 1

Type: WARNING

Impact: Other

WCS-43032: Class: {0} does not have set or add method for tag: {1}.

Cause: This can occur due to missing extension-registry configuration in the adf-config.xml file or there is no set/add method on the corresponding application bean to handle complex node.

Action: Have a proper extension handler registered for this complex node or have set/add method on the bean with the tag name.
Level: 1

Type: WARNING

Impact: Other

WCS-43033: An error occurred processing the xml, due to: {0}.

Cause: Runtime problem invoking the operation.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-43034: Unable to set or get an ADF Preference value.

Cause: The ADF Preference service raised an exception whilst initializing, getting or setting a preference value.

Action: Check MDS classpath includes PreferenceNode.xsd.
Level: 1

Type: WARNING

Impact: Other

WCS-43036: Cannot provide the resource link. No FacesContext and no webapp base URL set.

Cause: Unable to build up a URL to WebCenter from outside of the web application.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-43038: Unable to find help for the current topic.

Cause: Either the help system is not setup or it is not accessible.

Action: Examine the WebCenter Configuration for Help and make sure that Help System is up and running.
Level: 1

Type: ERROR

Impact: Configuration

WCS-43039: Scope Provider resource configuration file "{0}" not found, cannot proceed.

Cause: The main configuration file that defines the default implementation of ScopeMetadataProvider class is missing.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-43040: Scope Provider resource configuration file "{0}" found, but the data is missing. Cannot proceed.

Cause: The main configuration file that defines the default implementation of ScopeMetadataProvider class is misconfigured, all the required data is not available in this file.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-43041: ScopeMetadataProvider resource configuration file "{0}" found, but the class defined "{1}" is not an instance of oracle.webcenter.framework.service.ScopeMetadataProvider.

Cause: The main configuration file that defines the default implementation of ScopeMetadataProvider class is misconfigured, the supplied class is not an instance oracle.webcenter.framework.service.ScopeMetadataProvider.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-43042: Resource Action not created due to missing attributes.

Cause: The Group ID (Service ID) and the Resource ID are not present as f:attribute values in the consuming JSPX page.

Action: Check the JSPX page where this originated from and make sure you add the groupId and resourceId attributes and that they are not null.
Level: 1

Type: WARNING

Impact: Other

WCS-43043: Failed to load resource action handler class "{0}"; using default.

Cause: The resource action handler class specified failed to load.

Action: Check the classpath to inspect whether this class is available; then check accompanying exceptions in the log to further debug the cause.
Level: 1

Type: WARNING

Impact: Other

WCS-43044: Failed to parse view renderer "{0}" as a valid TaskFlow ID; returning null.

Cause: The specified task flow ID cannot be parsed properly.

Action: Check the value of the view renderer specified and investigate how you arrived at that value.
Level: 1

Type: WARNING

Impact: Other

WCS-43045: Failed to parse view renderer "{0}" as a valid TaskFlow ID; treating it as a View ID instead.

Cause: The specified task flow ID cannot be parsed properly.

Action: Check the META-INF/service-definition.xml of the service to verify whether it is a view ID or a TaskFlow ID by checking the documented syntax of both.
Level: 1

Type: WARNING

Impact: Other

WCS-43046: Can not find TaskFlowId in pageFlowScope; returning null.

Cause: The task flow ID sought in the pageFlowScope is not found.

Action: This is an internal warning and should not be acted on.
Level: 1

Type: WARNING

Impact: Other

WCS-43047: The JPS Service Locator cannot be obtained.

Cause: The error was caused while obtaining the JPS Service Locator. Review the underlying exception in the logs to determine the exact cause.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Security

WCS-43048: User Principal could not be found for authenticated user.

Cause: This indicates an error with the Identity Store, or Java Platform Security setup.

Action: This is an internal warning. The Administrator needs to verify the Identity Store setup.
Level: 1

Type: WARNING

Impact: Other

WCS-43049: An error occured reading the Connections Context.

Cause: This indicates an error with reading the Connection Context.

Action: Refer to exception detail. If insufficent details to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

WCS-43050: An error occured reading a service's configuration.

Cause: This indicates an error with reading a service's configuration.

Action: Refer to exception detail. If insufficent details to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

WCS-43051: cannot access Java Object Cache

Cause: An exception occured while accessing Java object cache.

Action: Review the exception thrown for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-43052: cannot create userprofile region in Java Object Cache

Cause: An exception occured while creating userprofile region in Java object cache.

Action: Review the exception thrown for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-43053: cannot create userprofile region in Java Object Cache.

Cause: An exception occured while removing userprofile region from Java object cache.

Action: Review the exception thrown for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-44001: cannot load role provider implementation for service ID: {0}

Cause: The provider class configured in role-mapping-metadata tag of the specified service definition was not available to the classloader.

Action: Ensure that the provider class specified in the service-definition.xml file is available to the classloader.
Level: 1

Type: ERROR

Impact: Security

WCS-44002: The Role Mapping provider encountered an exception while performing security role mapping for service {0}.

Cause: This is caused by an error experienced by service-specific Role Mapping provider.

Action: Inspect the server logs and rectify the problem encountered by the service Role Mapping provider.
Level: 1

Type: ERROR

Impact: Security

WCS-44003: The Role Mapping provider cannot find the service role: {0}. Exception from the provider: {1}.

Cause: The Role Mapping provider cannot find the service role. Review the exception from the provider to determine the exact cause.

Action: Inspect the server logs and rectify the problem encountered by the service Role Mapping provider.
Level: 1

Type: ERROR

Impact: Security

WCS-44004: An internal JPS error has occurred while retrieving information from the Application Policy Store.

Cause: This may have been caused when retrieving information from the Application Policy Store.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Security

WCS-44005: cannot find security extension in Service Registry for service ID: {0}

Cause: No security extension was registered for the given service.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Security

WCS-44006: There is no mapped service role for the WebCenter role {1} to which the user {0} is assigned.

Cause: A user was assigned to a WebCenter role that was not yet mapped to any service role.

Action: Ensure that the WebCenter role is mapped to a service role.
Level: 1

Type: WARNING

Impact: Security

WCS-44007: An internal JPS error has occurred while initializing the Application Policy Store.

Cause: The Application Policy Store (jps-config.xml) was probably not configured correctly.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Security

WCS-44009: Error obtaining JPS Service instance: {0}.

Cause: The value returned for the JPS Service instance was null. This may be caused by configuration error in jps-config.xml.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Security

WCS-44010: A JPS error is encountered while deleting users from the service ID/service role: {0} / {1}.

Cause: The error was caused while accessing the application policy store for deleting users. Review the underlying exception in the logs to determine the exact cause.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Security

WCS-44101: Invalid PeoplePicker Scope {0} passed.

Cause: The scope is not of the valid type. It can be GLOBAL or SUB_SCOPED

Action: Pass a valid scope
Level: 1

Type: WARNING

Impact: Configuration

WCS-44102: Invalid PeoplePicker Scope ID {0} passed.

Cause: An invalid Scope ID has been passed.

Action: Ensure a valid scope/community ID is passed.
Level: 1

Type: WARNING

Impact: Configuration

WCS-44103: Unknown error encountered while selecting user(s) in people picker.

Cause: Review the root cause of the exception for more details.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Security

WCS-44104: Scope Id is a required parameter for scoped people search.

Cause: Scope Id not provided.

Action: Provide Scope Id.
Level: 1

Type: WARNING

Impact: Security

WCS-44105: And unknown error occurred while trying to validate if user {0} exists

Cause: Review the root cause of the exception for more details.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Security

WCS-44106: Unknown error encountered while selecting group(s) in group picker.

Cause: Review the root cause of the exception for more details.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Security

WCS-44107: And unknown error occurred while trying to validate if group {0} exists

Cause: Review the root cause of the exception for more details.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Security

WCS-44108: The search exceeded the time limit. Check the identity store connection details or refine your search criterion.

Cause: The underlying identity store and policy store could be down.

Action: Check that underlying repositories are accessible. Check logs and contact Oracle Support
Level: 1

Type: WARNING

Impact: Security

WCS-44109: The search exceeded the size limit. Refine your search criterion.

Cause: The search results in a large dataset that is not supported by the underlying identity store.

Action: Refine your search criterion to something more narrow.
Level: 1

Type: WARNING

Impact: Security

WCS-44110: An unexpected error occurred while searching for users/roles. Check logs for further details.

Cause: An unexpected error occurred while searching for identities. Consult the underlying cause.

Action: If the underlying cause does not provide any action, contact Oracle Support.
Level: 1

Type: ERROR

Impact: Security

WCS-44151: An error is encountered while retrieving the Identity Store.

Cause: This is caused when the Identity Store configured in jps-config.xml is not accessible or is not running.

Action: Ensure that the Identity Store is configured correctly in jps-config.xml and is running.
Level: 1

Type: ERROR

Impact: Security

WCS-44152: An error is encountered while sending an e-mail.

Cause: The error occurred because the e-mail account or the e-mail service was not configured correctly or the e-mail server was not running.

Action: Ensure that your e-mail account and the e-mail service are configured properly and the e-mail server is running.
Level: 1

Type: ERROR

Impact: Security

WCS-44153: An error is encountered while generating the HMAC token.

Cause: The JVM did not support MessageDigest algorithms, such as MD5 or SHA, or the UTF8 encoding.

Action: Ensure the JVM supports UTF8 encoding and MD5/SHA message digest algorithms. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44154: An error has occurred while getting the scope roles for scope ID {0}.

Cause: Either the policy store was configured incorrectly or was inaccessible or the scope ID passed was invalid.

Action: Ensure that the policy store is configured correctly and is running. Also, ensure that the scope ID passed is valid.
Level: 1

Type: ERROR

Impact: Security

WCS-44155: The permission class is null for the service ID: {0}.

Cause: The permission class was not defined in the service-definition.xml file.

Action: Ensure that the permission class is defined in the service-definition.xml file for the service.
Level: 1

Type: ERROR

Impact: Security

WCS-44156: The value of resource bundle is null for the service ID: {0}.

Cause: The resource bundle was not defined in the service-definition.xml file.

Action: Ensure that the resource bundle is defined in the service-definition.xml file.
Level: 1

Type: ERROR

Impact: Security

WCS-44157: The value of permission target is null for the service ID: {0}.

Cause: The permission target was not defined in the service-definition.xml file.

Action: Ensure that the permission target is defined in the service-definition.xml file.
Level: 1

Type: ERROR

Impact: Security

WCS-44158: The value of permission action is not defined for the service ID: {0}.

Cause: The permission action (permission-action-list tag) was not defined in the service-definition.xml file.

Action: Ensure that the permission actions are defined in the service-definition.xml file by using the permission-action-list tag.
Level: 1

Type: ERROR

Impact: Security

WCS-44159: The value of permission admin action is not defined for the service ID: {0}.

Cause: The permission admin action (permission-manage-action tag) was not defined in the service-definition.xml file.

Action: Ensure that the permission admin actions are defined in the service-definition.xml file by using the permission-manage-action tag.
Level: 1

Type: ERROR

Impact: Security

WCS-44160: The role mapping class is not defined for the service ID: {0}.

Cause: The role mapping class was not defined in the service-definition.xml file.

Action: Ensure that the role mapping class is defined in the service-definition.xml file.
Level: 1

Type: ERROR

Impact: Security

WCS-44161: The role mapping resource bundle is not defined for the service ID: {0}.

Cause: The role mapping resource bundle was not defined in the service-definition.xml file.

Action: Ensure that the role mapping resource bundle is defined in the service-definition.xml file.
Level: 1

Type: ERROR

Impact: Security

WCS-44162: Security Extension is not defined for the service ID: {0}.

Cause: The Security Extension (security-definition node) was not defined in the service-definition.xml file of the service.

Action: Ensure that the Security Extension (security-definition node) is properly defined in the service-definition.xml file.
Level: 1

Type: ERROR

Impact: Security

WCS-44163: An error has occurred while retrieving service extension definition(service-definition.xml).

Cause: The service jars are not correctly packaged or the jars are corrupt.

Action: Ensure that webcenter framework shared library is correctly defined and the library jars are not corrupt.
Level: 1

Type: ERROR

Impact: Security

WCS-44164: An error has occurred while retrieving the spi file .

Cause: The are multiple spi files.

Action: Ensure that only spi file with the name oracle.webcenter.security.selfregistration.custom.SelfRegActionHandlerSpi.properties exists.
Level: 1

Type: ERROR

Impact: Security

WCS-44165: The principal is not of type JpsRole

Cause: The principal object passed to the api is not of type JpsRole.

Action: Ensure that the parameter passed to the api is of type JpsRole.
Level: 1

Type: WARNING

Impact: Security

WCS-44166: Application Policy for {0} does not exist. Creating a new application policy.

Cause: The application did not package any policies.

Action: None as a new policy has been created. However ensure that application did not indeed package any policies and this was not a case of policies not being migrated. Contact Oracle Support in that case.
Level: 1

Type: WARNING

Impact: Security

WCS-44167: Public registration is not enabled for this site.

Cause: The public registration option is not enabled.

Action: Ensure that public registration is enabled in the general tab of Webcenter administration.
Level: 1

Type: ERROR

Impact: Security

WCS-44168: The principal argument is null

Cause: The principal object passed to the api is null.

Action: Ensure that the parameter passed to the api is not null.
Level: 1

Type: WARNING

Impact: Security

WCS-46001: unexpected error has occurred

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

WCS-46002: cannot initialize the resource catalog

Cause: There was an error initializing the catalog using the catalog specified in adf-config.xml or there was a problem with the underlying resource catalog service.

Action: Verify that the catalog name specified in adf-config.xml is valid.
Level: 1

Type: WARNING

Impact: Logging

WCS-46004: cannot create item for resource [{0}], path [{1}], catalog [{2}]

Cause: There was an internal error when creating an item for the resource indicated above.

Action: Verify that the Resource Catalog and resource adapters are working correctly.
Level: 1

Type: WARNING

Impact: Logging

WCS-46005: cannot create a Folder object for resource [{0}], catalog [{1}]

Cause: There was an internal error when creating the folder object using the path specified.

Action: Verify that the Resource Catalog and resource adapters are working correctly.
Level: 1

Type: WARNING

Impact: Logging

WCS-46006: cannot retrieve items in [{0}] from catalog [{1}]

Cause: There was an error retrieving any resources from the catalog.

Action: Verify that the catalog is correctly configured in adf-config.xml.
Level: 1

Type: WARNING

Impact: Logging

WCS-46007: Search predicate [{0}] is not valid for search path [{1}] in catalog [{2}].

Cause: The search condition specified was invalid or incorrect.

Action: Correct the code that creates the search condition for the resource catalog viewer.
Level: 1

Type: WARNING

Impact: Logging

WCS-46008: Specified folder [{0}], path [{1}] to search does not exist in catalog [{2}].

Cause: The selected folder does not exist anymore.

Action: Perform the search by selecting a different folder.
Level: 1

Type: WARNING

Impact: Logging

WCS-46009: cannot execute search for folder [{0}]

Cause: An internal error occurred while executing the requested search.

Action: Verify that the Resource Catalog and resource adapters are working correctly.
Level: 1

Type: WARNING

Impact: Logging

WCS-46010: cannot retrieve folder path for item [{0}]

Cause: The folder path specified was not found.

Action: The folder path requested is either incorrect or does not exist anymore.
Level: 1

Type: WARNING

Impact: Logging

WCS-46011: cannot find Item [{0}] in catalog [{1}]

Cause: The requested item could not be found.

Action: The item requested is either incorrect or does not exist anymore.
Level: 1

Type: WARNING

Impact: Logging

WCS-46012: cannot find Folder [{0}] in catalog [{1}]

Cause: The requested folder could not be found.

Action: The folder requested is either incorrect or does not exist anymore.
Level: 1

Type: WARNING

Impact: Logging

WCS-46013: cannot retrieve icon

Cause: Icon associated with the requested resource not found.

Action: Verify that the underlying resource provider adapter supports the iconURI attribute.
Level: 1

Type: WARNING

Impact: Logging

WCS-46014: cannot retrieve attributes for item [{0}]

Cause: Could not retrieve one or more attributes.

Action: Verify that the underlying resource provider supports the requested attributes.
Level: 1

Type: WARNING

Impact: Logging

WCS-46015: cannot retrieve transferable for item [{0}]

Cause: Could not retrieve transferable for resource.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

WCS-46016: cannot retrieve repository reference for item [{0}]

Cause: Could not retrieve a repository reference.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

WCS-46017: cannot retrieve schema attributes for folder [{0}]

Cause: Error occurred while fetching information about the schema.

Action: Verify that the Resource Catalog and resource adapters are working correctly.
Level: 1

Type: WARNING

Impact: Logging

WCS-46018: cannot retrieve any resources for folder [{0}]

Cause: Error occurred while fetching resource catalog resources.

Action: Verify that the Resource Catalog and resource adapters are working correctly.
Level: 1

Type: WARNING

Impact: Logging

WCS-46019: cannot retrieve any folders for folder [{0}]

Cause: Error occurred while fetching resource catalog folders.

Action: Verify that the Resource Catalog and resource adapters are working correctly.
Level: 1

Type: WARNING

Impact: Logging

WCS-46020: cannot retrieve any items for folder [{0}]

Cause: Error occurred while fetching resource catalog items.

Action: Verify that the Resource Catalog and resource adapters are working correctly.
Level: 1

Type: WARNING

Impact: Logging

WCS-46021: cannot retrieve any attributes for item [{0}]

Cause: Error occurred while fetching resource catalog resource attributes.

Action: Verify that the Resource Catalog and resource adapters are working correctly.
Level: 1

Type: WARNING

Impact: Logging

WCS-46022: cannot execute a search in folder [{0}], search criteria [{1}], include subfolders [{2}]

Cause: Search could not be executed due to unknown reasons.

Action: Verify that the Resource Catalog and resource adapters are working correctly.
Level: 1

Type: WARNING

Impact: Logging

WCS-46023: cannot retrieve the complete path for folder [{0}]

Cause: Error occurred while fetching the full path of the resource.

Action: The resource may not exist anymore. Refresh the viewer to get the latest content.
Level: 1

Type: WARNING

Impact: Logging

WCS-46024: cannot retrieve the current folder

Cause: There was an error while retrieving information about the current folder.

Action: The folder may not exist anymore. Refresh the viewer to get the latest content.
Level: 1

Type: WARNING

Impact: Logging

WCS-46025: cannot initialize the catalog using the parameters specified in adf-config.xml

Cause: The catalog name specified in adf-config.xml could not be used or the there was an error retrieving the catalog name from the catalog selector class specified in adf-config.xml.

Action: Verify that the catalog name specified in adf-config.xml or the one returned by the catalog selector class exists.
Level: 1

Type: WARNING

Impact: Logging

WCS-46027: cannot print attributes for item [{0}]

Cause: Error printing information about the item attributes in the viewer.

Action: Check the error stack for more information.
Level: 1

Type: WARNING

Impact: Logging

WCS-46028: cannot load ResourceCatalogConfig implementation using class [{0}]

Cause: Resource catalog configuration implementation class defined in adf-config.xml is invalid.

Action: Check adf-config.xml to verify the implementation class is valid.
Level: 1

Type: WARNING

Impact: Logging

WCS-46029: cannot instantiate the catalog config class [{0}]

Cause: An error occurred while instantiating a class defined in the <rcv-adf-config> section in adf-config.xml.

Action: Verify that the class name is correct and it implements the required interface
Level: 1

Type: WARNING

Impact: Logging

WCS-46030: cannot obtain the catalog name. ResourceCatalogSelector=[{0}] DefaultCatalog=[{1}].

Cause: The resource catalog viewer was unable to determine the catalog to use for the current context and no default was specified.

Action: Verify the ResourceCatalogSelector implementation and specify a default catalog in adf-config.xml.
Level: 1

Type: WARNING

Impact: Logging

WCS-46032: cannot retrieve item for item with ID [{0}]

Cause: An error occurred while fetching the item using the item id.

Action: Review the resource catalog service logs for additional information.
Level: 1

Type: WARNING

Impact: Logging

WCS-46033: cannot retrieve root folder

Cause: An error occurred while fetching the root folder.

Action: Check the Resource Catalog logs for additional information.
Level: 1

Type: WARNING

Impact: Logging

WCS-46035: cannot initialize the catalog context with catalog [{0}]

Cause: The catalog name specified in adf-config.xml could not be used or the there was an error retrieving the catalog name from the catalog selector class specified in adf-config.xml.

Action: Verify that the catalog name specified in adf-config.xml or the one returned by the catalog selector class exists.
Level: 1

Type: WARNING

Impact: Logging

WCS-46037: cannot retrieve the catalog instance

Cause: The catalog name specified in adf-config.xml could not be used or the there was an error retrieving the catalog name from the catalog selector class specified in adf-config.xml.

Action: Verify that the catalog name specified in adf-config.xml or the one returned by the catalog selector class exists.
Level: 1

Type: WARNING

Impact: Logging

WCS-46039: cannot parse the rcv config in adf-config.xml

Cause: The rcv config xml element specified in adf-config.xml could not be parsed.

Action: Verify that the rcv config element specified in adf-config.xml exists and it is valid.
Level: 1

Type: WARNING

Impact: Logging

WCS-47201: An unexpected error occurred in the activity stream sub-system.

Cause: An unexpected error occured.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-47202: publish activity failed because of invalid arguments passed in to the method: activity ({0}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-47203: retrieve activities failed because of invalid arguments passed in to the method: privateAndUpActorIds ({0}), sharedAndUpActorIds ({1}), publicActorIds ({2}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-47205: Can not get connections. Connections Exception is thrown.

Cause: Connections exception thrown.

Action: Check the exception's detail to see the reason why the exception is thrown.
Level: 1

Type: ERROR

Impact: Other

WCS-47206: Service Framework Exception is thrown.

Cause: Connections exception thrown.

Action: Check the exception's detail to see the reason why the exception is thrown.
Level: 1

Type: ERROR

Impact: Other

WCS-47207: Settings Exception is thrown.

Cause: Settings exception thrown.

Action: Check the exception's detail to see the reason why the exception is thrown.
Level: 1

Type: ERROR

Impact: Other

WCS-47695: Unexpected error saving settings

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47696: Fatal error initializing the settings management sub-system

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-47697: Unexpected error retrieving settings

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47698: Unable to locate the settings document

Cause: Either the document path was incorrect or the document had got deleted.

Action: Ensure that the document path is correct and that the document exists.
Level: 1

Type: ERROR

Impact: Other

WCS-47699: Unable to determine current user

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47700: An unexpected error occurred in the People Connections sub-system.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-47801: An unexpected error occurred in the Connections sub-system.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-47802: User not specified

Cause: The supplied username was null or blank.

Action: Specify a valid username that is not null or blank.
Level: 1

Type: ERROR

Impact: Other

WCS-47803: Unexpected error retrieving connections for user ''{0}''

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47804: Unexpected error retrieving invitations for current user

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47805: User ''{0}'' not found

Cause: The system could not find any user with the specified username.

Action: Specify a valid username.
Level: 1

Type: ERROR

Impact: Other

WCS-47806: Unexpected error sending invitation to user ''{0}''

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47807: No invitation found with ID ''{0}''

Cause: The system could not find any invitation with the specified ID.

Action: Ensure that the specified invitation ID is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-47808: Invitation ID not specified

Cause: The supplied invitation ID was null or blank.

Action: Specify a valid invitation ID that is not null or blank.
Level: 1

Type: ERROR

Impact: Other

WCS-47809: Unexpected error accepting invitation with ID ''{0}''

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47810: Unexpected error declining invitation with ID ''{0}''

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47811: Unexpected error ignoring invitation with ID ''{0}''

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47812: Unexpected error removing connection with user ''{0}''

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47813: Unexpected error retrieving profile of user ''{0}''

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47814: Unexpected error retrieving the connection lists owned by user ''{0}''

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47815: Connection list not specified

Cause: The supplied connection list name was null or blank.

Action: Specify a valid connection list name that is not null or blank.
Level: 1

Type: ERROR

Impact: Other

WCS-47816: Connection list named ''{0}'' not found for user ''{1}''

Cause: The system could not find any connection list with the specified name owned by the specified user.

Action: Ensure that the username is correct and that the connection list name refers to a connection list owned by that user.
Level: 1

Type: ERROR

Impact: Other

WCS-47817: Unexpected error getting Connection list ''{0}'' for user ''{1}''

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47818: User does not have the privilege required to perform specified operation

Cause: Either the system policy or the target user's access control settings restrict the current user from performing this operation

Action: Contact the Administrator to grant the required permission, or contact the target user to allow access
Level: 1

Type: ERROR

Impact: Other

WCS-47819: Unexpected error creating a Connection list with name ''{0}''

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47820: Unexpected error adding users to Connection list with name ''{0}''

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47821: Unexpected error deleting Connection list with name ''{0}''

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47822: Unexpected error retrieving members of Connection list with name ''{0}''

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47823: Unexpected error retrieving invitations sent by current user

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47824: Unexpected error removing user ''{0}'' from one or more Connection lists

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47825: Unexpected error setting Connection list membership of user ''{0}''

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47826: Unexpected error retrieving the Connection lists to which user ''{0}'' belongs

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

101 WOR-70021 to WOR-70229

WOR-70021: The specified Reports Server object was not found.

Cause: The Reports Server that was specified is not registered with OracleAS Portal.

Action: Register the Reports Server, or specify the correct Reports Server name.
Level: 1

Type: ERROR

Impact: Other

WOR-70024: The specified Reports Calendar was not found.

Cause: The specified Reports Calendar does not exist or is not registered with OracleAS Portal.

Action: Register the Reports Calendar, or specify the correct Reports Calendar name.
Level: 1

Type: ERROR

Impact: Other

WOR-70071: cannot complete rwcalsum.show_control

Cause: There was an internal error while rendering the calendar.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WOR-70082: not a valid number

Cause: A value was entered that contains nonnumeric characters.

Action: Enter only numeric characters.
Level: 1

Type: ERROR

Impact: Other

WOR-70135: failure to save parameters

Cause: The operation to save parameters failed.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WOR-70136: failure to initialize Builder attributes - %0

Cause: Initialization of the specified Reports Builder attributes failed.

Action: Refer to the relevant Reports Builder error message, and take the appropriate action.
Level: 1

Type: ERROR

Impact: Other

WOR-70137: failure to initialize servers - %0

Cause: Initialization of the specified Reports Server failed.

Action: Verify that the Reports Server is properly registered.
Level: 1

Type: ERROR

Impact: Other

WOR-70166: unable to delete object <B>%0 (version %1)</B> from Oracle Portal

Cause: The application was unable to delete the specified object.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WOR-70174: invalid error ID

Cause: An invalid error ID was specified.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WOR-70175: cannot access the server

Cause: The server was not accessible because the security check failed.

Action: Contact the portal administrator to get access to the server.
Level: 1

Type: ERROR

Impact: Other

WOR-70176: cannot access the printer

Cause: The printer was not accessible because the security check failed.

Action: Contact the portal administrator to get access to the printer.
Level: 1

Type: ERROR

Impact: Other

WOR-70177: cannot access the module

Cause: The module was not accessible because the security check failed.

Action: Contact the portal administrator to get access to the module.
Level: 1

Type: ERROR

Impact: Other

WOR-70178: cannot access the output type:

Cause: The output type (destype) was not accessible because the security check failed.

Action: Contact the portal administrator to get access to the output type.
Level: 1

Type: ERROR

Impact: Other

WOR-70179: cannot access the output format

Cause: The output format (desformat) was not accessible because the security check failed.

Action: Contact the portal administrator to get access to the output format.
Level: 1

Type: ERROR

Impact: Other

WOR-70180: cannot run the report

Cause: The calendar check failed. The report cannot be run at this time.

Action: View the availability calendar to see when the report can be run.
Level: 1

Type: ERROR

Impact: Other

WOR-70181: cannot use the server at this moment

Cause: The calendar check failed. The report cannot be run on this server at this time.

Action: Check the availability calendar to see when the server can be used to run the report.
Level: 1

Type: ERROR

Impact: Other

WOR-70182: cannot use the printer at this moment

Cause: The calendar check failed. Printing on this printer is not possible at this time.

Action: Check the availability calendar to see when the report can be printed on this printer.
Level: 1

Type: ERROR

Impact: Other

WOR-70183: generic access check failure

Cause: The required privileges to perform this task were missing.

Action: Ask the portal administrator for the required privileges.
Level: 1

Type: ERROR

Impact: Other

WOR-70184: LOV access check failure for parameter

Cause: The LOV access check failed. The user currently does not have the privileges required to access this LOV.

Action: Ask the portal administrator for the required privileges.
Level: 1

Type: ERROR

Impact: Other

WOR-70185: failure of low-range access check for parameter

Cause: The value specified was less than the valid lower limit for this parameter.

Action: Specify a value within the valid range.
Level: 1

Type: ERROR

Impact: Other

WOR-70186: failure of high-range access check for parameter

Cause: The value specified was higher than the valid high limit for this parameter.

Action: Specify a value within the valid range.
Level: 1

Type: ERROR

Impact: Other

WOR-70187: failure of validation escape access check

Cause: The validation trigger failed.

Action: Contact the portal administrator.
Level: 1

Type: ERROR

Impact: Other

WOR-70188: No report is specified.

Cause: A report name was not specified.

Action: Specify a valid report name.
Level: 1

Type: ERROR

Impact: Other

WOR-70189: No server is specified.

Cause: A server name was not specified.

Action: Specify a valid server name.
Level: 1

Type: ERROR

Impact: Other

WOR-70190: Conflicting module and report names are specified.

Cause: The report name and the module name were conflicting.

Action: Ensure that the report name and the module name are the same.
Level: 1

Type: ERROR

Impact: Other

WOR-70210: exception when sending a request to the Reports Server

Cause: An exception occurred when sending a request to the Reports Server. The report was not sent.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WOR-70212: The Oracle Reports Web gateway URL setting is not specified. Cannot run report.

Cause: The Oracle Reports Web gateway URL was not specified.

Action: Edit the server component, and specify the Oracle Reports Web gateway.
Level: 1

Type: ERROR

Impact: Other

WOR-70229: The browser cannot display this Reports portlet.

Cause: The browser version was not supported. The Reports portlet cannot be displayed in this version of the browser.

Action: Upgrade the browser version. Refer to the product documentation for supported browser versions.
Level: 1

Type: ERROR

Impact: Other

102 WSM-00001 to WSM-09024

WSM-00001: A JAXB context for path "{0}" cannot be created due to underlying error "{1}".

Cause: The error could have been caused by creating the JAXB2.0 marshaller/unmarshaller.

Action: Contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Other

WSM-00002: A class of type {0} cannot be marshaled due to underlying error "{1}".

Cause: Error occurred in JAXB marshalling (1.e converting java object to xml.)

Action: Contact Oracle Support Services or refer to http://java.net/jaxb.
Level: 32

Type: INCIDENT_ERROR

Impact: Other

WSM-00003: An element of type {0} cannot be unmarshaled due to underlying error "{1}".

Cause: Error occurred while doing JAXB unmarshall i.e converting XML to Java.

Action: Contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Other

WSM-00004: WS-Security Exception : {0}

Cause: The system encountered a generic failure in security.

Action: Contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Security

WSM-00005: Error in sending the request.

Cause: Failure occurred while trying to send the request message, possibly due to a failure in security code.

Action: Retry the operation for a maximum of 3 times. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Security

WSM-00006: Error in receiving the request: {0}.

Cause: Failure occurred while processing the request message, possibly due to a failure in security checks.

Action: Refer to the policy for the expected nature of the request message and retry the operation.
Level: 1

Type: ERROR

Impact: Security

WSM-00007: JPS exception

Cause: The error was most likely due to an invalid JPS configuration.

Action: Correct the JPS configuration and retry the operation.
Level: 1

Type: ERROR

Impact: Security

WSM-00008: Web service authentication failed.

Cause: Authentication failed at the server end.

Action: Resend valid credentials.
Level: 1

Type: ERROR

Impact: Security

WSM-00009: The password policy does not match. Expected: {0}, Received:{1}.

Cause: The expected and actual password types did not match.

Action: Refer to the policy to determine the allowed password type value.
Level: 1

Type: ERROR

Impact: Security

WSM-00010: Message rejected as the nonce element in the WS-Security header is missing.

Cause: Nonce was required according to policy requirements, but was not found.

Action: Resend the request with valid value of nonce.
Level: 1

Type: ERROR

Impact: Security

WSM-00011: The wsu:Created element is required.

Cause: The Created element was required, but was not found.

Action: Resend the request with valid value of the Created element with the UTC timestamp of the instance in which the request was created.
Level: 1

Type: ERROR

Impact: Security

WSM-00012: The password is ignored, as it is not required by the policy.

Cause: The password was sent in the <UsernameToken>, when it was not required.

Action: The password type prescribed by the policy is None, so password should not be sent.
Level: 1

Type: WARNING

Impact: Security

WSM-00013: The nonce is ignored, as it is not required by the policy.

Cause: The nonce was sent in the <UsernameToken>, when it was not required.

Action: Because the policy does not require the nonce, it should not be sent.
Level: 1

Type: WARNING

Impact: Security

WSM-00014: The creation timestamp is ignored, as it is not required by the policy.

Cause: The creation timestamp was sent in the <UsernameToken>, when it was not required.

Action: Because the policy does not require the creation timestamp inside <UsernameToken>, it should not be sent.
Level: 1

Type: WARNING

Impact: Security

WSM-00015: The user name is missing.

Cause: Username was expected but was not found.

Action: Either the username element or the username inside the username element is missing. Resend the request with a valid username.
Level: 1

Type: ERROR

Impact: Security

WSM-00016: The username/password credentials or certificates {0} are missing.

Cause: It is possible that username/password or certificate is missing.

Action: Resend valid credentials.
Level: 1

Type: ERROR

Impact: Security

WSM-00017: The <bindings> element for {0}:{1} is missing.

Cause: It is likely that the bindings element is missing inside policy.

Action: Re-create the policy with valid bindings.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00018: There is more than one security header with the same role {0}.

Cause: More than one security header was found with the same role associated.

Action: Refer to the WS-Security 1.0 or 1.1 specifications. Do not send more than one security header having the same role.
Level: 1

Type: ERROR

Impact: Security

WSM-00019: The version of SOAP used is not supported: {0}.

Cause: An envelope was obtained that conforms to an unsupported version of SOAP.

Action: Use a supported version. SOAP 1.1 and 1.2 are supported.
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00020: Error sending the response.

Cause: A failure occurred while building the response.

Action: Retry a maximum of three times. If the retry attempts fail, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Other

WSM-00021: Error receiving the response.

Cause: A failure occurred while processing the response, most likely due to a failure in the security check.

Action: Retry sending the response to the client.
Level: 1

Type: ERROR

Impact: Security

WSM-00022: Error sending a fault.

Cause: A failure occurred while sending the fault.

Action: Retry for a maximum of three times. If the retry attempts fail, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Other

WSM-00023: Error receiving a fault.

Cause: A failure occurred while processing the fault, most likely due to a failure in the security check.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Security

WSM-00024: The SAML token is missing from the security header. Ensure that there is a SAML token policy attached on the client side. Tokens found in the security header are :- {0}.

Cause: The SAML assertion that was expected inside the security header was not found.

Action: Insert valid SAML assertions and resend the request.
Level: 1

Type: ERROR

Impact: Security

WSM-00025: SAML token verification failure.

Cause: SAML token verification failed.

Action: Check the validity period of the SAML assertion using Conditions, or determine whether the assertion must be signed. Ensure that the SAML token conforms to the requirements of the SAML 1.0 specification.
Level: 1

Type: ERROR

Impact: Security

WSM-00026: The SAML token cannot be added to the security header.

Cause: A failure occurred while adding the SAML token to the security header.

Action: Check the log file for a possible cause.
Level: 1

Type: ERROR

Impact: Other

WSM-00027: The configuration parameter {0} contains an invalid value [{1}].

Cause: The configuration settings were invalid.

Action: Check the configuration and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00028: Failure in getting user credentials from client.

Cause: Failure occurred while extracting user credentials from the client side.

Action: Check Keystore/Username and the Password/CSF configuration.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00029: The algorithms used to encrypt the data do not match those specified in the policy. : Expected : {0}, Actual : {1}.

Cause: The expected and actual data encryption algorithms did not match.

Action: Check the policy to determine the permitted values for the data encryption algorithm.
Level: 1

Type: ERROR

Impact: Security

WSM-00030: The encryption method key wrap algorithms do not match : Expected : {0}, Actual : {1}.

Cause: The expected and actual key wrap encryption algorithms did not match.

Action: Check the policy to determine the permitted values for the key wrap encryption algorithm. In addition, refer to WS-Security Policy 1.1 for a list of allowed values.
Level: 1

Type: ERROR

Impact: Security

WSM-00031: The digest algorithms do not match.

Cause: The actual digest algorithms for the signature did not match the expected algorithms.

Action: Check the policy to determine the permitted values for the signature digest algorithms.
Level: 1

Type: ERROR

Impact: Security

WSM-00033: The encrypted message elements or parts do not comply with the policy. The following headers/elements (<name space: local name>) or attachments (<attachment ID: attachment type>) must be encrypted:- {0}

Cause: Parts or elements to be encrypted according to policy were different from those in the SOAP message.

Action: Refer to the policy and WS-Security specifications to ensure that all encryption requirements mandated by the policy and the specifications are met.
Level: 1

Type: ERROR

Impact: Security

WSM-00034: Error in Encryption reference mechanism compliance : Expected : {0} , Actual : {1}. Ensure that a compatible policy is attached at the client side.

Cause: The expected and actual encryption reference mechanisms did not match.

Action: Check the policy to determine the permitted values for the encryption reference mechanism.
Level: 1

Type: ERROR

Impact: Security

WSM-00035: Error in Signature reference mechanism compliance : Expected : {0} , Actual : {1}. Ensure that a compatible policy is attached at the client side.

Cause: The expected and actual signature reference mechanisms did not match.

Action: Check the policy to determine the allowed value of the signature reference mechanism.
Level: 1

Type: ERROR

Impact: Security

WSM-00036: The signed message elements or parts do not comply with the policy. The following headers/elements (<name space: local name>) or attachments (<attachment ID: attachment type>) must be signed:- {0}

Cause: Parts or elements to be signed according to policy were different from those in the soap message.

Action: Refer to the policy and WS-Security specifications to make sure that all the signature requirements mandated by the policy and the specifications are met.
Level: 1

Type: ERROR

Impact: Security

WSM-00037: Error in signature confirmation compliance.

Cause: The error could have occurred because the response signature confirmation element was not signed.

Action: Check that all the signature confirmations in the response are signed and referenced in the response signature.
Level: 1

Type: ERROR

Impact: Security

WSM-00039: Timestamp element is not found in the message in accordance with policy.

Cause: Timestamp policy compliance failed.

Action: Check the policy to find out whether a timestamp is required. If the policy indicates that the timestamp is not required, it should not be present; if timestamp is required, it should be present.
Level: 1

Type: ERROR

Impact: Security

WSM-00042: The request must be made over SSL.

Cause: The request was expected to be sent over SSL, but it was not.

Action: Check the SSL port and send the request over SSL.
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00043: No peer certificates are present from the HTTP request.

Cause: A certificate in the trust chain is missing.

Action: Ensure that the complete certificate chain is propagated in the request, if certificates signed by CA are used.
Level: 1

Type: ERROR

Impact: Security

WSM-00044: The HTTP authorization header is missing.

Cause: The authorization Header was not found.

Action: For basic over HTTP authentication, ensure that the request HTTP headers contain an authorization header.
Level: 1

Type: ERROR

Impact: Security

WSM-00045: HTTP authentication/authorization failure.

Cause: Failure occurred in basic authentication.

Action: Use the appropriate Base64 encoded combination of a valid username and password.
Level: 1

Type: ERROR

Impact: Security

WSM-00046: Error in advertisement of WS-Policy.

Cause: An error occurred while advertising ORAWSDL to WS-Policy.

Action: Contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Other

WSM-00047: Invalid key referencing mechanism: {0}.

Cause: The sign or encryption key reference mechanism used was invalid.

Action: Valid supported values are direct, issuerserial, SKI, or thumbprint.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00048: The signature confirmation value is invalid. Expected : {0}, Actual : {1}.

Cause: Signature confirmation sent in the response was invalid.

Action: See the WS-Security 1.1 specification for the correct @Value of SignatureConfirmation.
Level: 1

Type: ERROR

Impact: Security

WSM-00049: The expected {0} signature is missing in the request messsage.

Cause: No signature (message, or endorsing) was found in the request to confirm.

Action: Resend the request with at least one <Signature>.
Level: 1

Type: WARNING

Impact: Security

WSM-00050: Cannot obtain security token reference.

Cause: The message was not signed or encrypted properly.

Action: Check the <ds:Reference> section of the message.
Level: 1

Type: ERROR

Impact: Other

WSM-00051: The encrypted data or key cannot be obtained.

Cause: The referenced encrypted object could not be found.

Action: Ensure that the reference points to valid <EncryptedData> element.
Level: 1

Type: ERROR

Impact: Other

Cause: The referenced encrypted object could not be found.

Action: Ensure that the reference points to valid <EncryptedKey> element.

WSM-00052: There is an invalid or nonexistent configuration for the Login Module class [{1}] in the Java Platform Security (JPS) context [{0}].

Cause: An invalid or nonexistent configuration for Login Module could have been used.

Action: Change the configuration and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00053: The propagated subject is either null or empty.

Cause: No Subject was found.

Action: Send a valid nonempty Subject.
Level: 1

Type: ERROR

Impact: Security

WSM-00054: The password credentials cannot be obtained from the Credential Store Framework (CSF). Unable to retrive the csfKey "{0}". The csf map "{1}" found in the credential store is being used and the following keys are found in this map <CsfKeyName: UserName>:- {2}

Cause: Failure occurred while doing query for credentials from Credential Store Framework (CSF).

Action: Check CSF configuration.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00055: The keystore located at {0} cannot be loaded due to {1}. Ensure that valid keystore type and password are configured.

Cause: The following keystore-related configuration properties may not be valid:keystore.type, keystore.pass. Also, the keystore could be corrupt or could have been tampered with.

Action: Verify the configuration properties mentioned above and retry the operation. In a rare situation, replace or regenerate the keystore.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00056: The key, {0}, is not retrieved.{4}Ensure that the correct key password is set in the credential store for the above key. The location of the key store being used is "{1}" and its type is "{2}". The following aliases are found in the keystore:- {3}

Cause: Error occurred while obtaining key from store.

Action: Make sure the key exists in the keystore. Check JPS configuration settings for correct key alias, key password and keystore password. Also, check the values of the key keystore-csf-key and its password in the oracle.wsm.security map, through EM or WLST. In a rare situation, this error can also happen if the actual keystore type is ORACLE_WALLET and the keystore type specified in JPS configuration file is PKCS12.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00057: The certificate, {0}, is not retrieved.{4}The location of the key store being used is "{1}" and its type is "{2}". The following aliases are found in the keystore:- {3}

Cause: Failure occurred while retrieving certificate from store.

Action: Verify keystore location configuration property as well as make sure that the requested certificate is present.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00058: The key type {0} is not supported.

Cause: The private key algorithm that was used is unsupported.

Action: Ensure that the private key follows the RSA algorithm.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00059: Signature method algorithms are mismatched. Expected : {0}, Actual : {1}.

Cause: Expected and actual values of signature method algorithms did not match.

Action: Check the policy and WS-Security Policy 1.1 specification for valid values.
Level: 1

Type: ERROR

Impact: Security

WSM-00060: Error validating timestamp.

Cause: Timestamp is expired.

Action: Check the timestamp. Check the allowed clockskew and message expiration time.
Level: 1

Type: ERROR

Impact: Security

WSM-00061: Signature digest verification failure. The system property xml.debug.verify should be enabled for the details about the digest calculations during verification phase (note xml.debug.verify slows down the signature verification for very large messages). Caused by:-{0}

Cause: Digest verification failed possibly due to corrupted digest, or a message that was tampered with.

Action: Recompute the digest and send the message again.
Level: 1

Type: ERROR

Impact: Security

WSM-00062: The path to the certificate used for the signature is invalid.

Cause: The intermediate and root certificates of the signing certificate were not present in the keystore at the verifying end.

Action: Make sure that the entire certificate chain is available in the keystore for verification.
Level: 1

Type: ERROR

Impact: Security

WSM-00063: The version of SAML is incorrect. Expected : {0}, Actual : {1}.

Cause: SAML version in the SAML assertion did not match the expected version.

Action: Check to see that the major version and minor version of the assertion are according to policy.
Level: 1

Type: ERROR

Impact: Security

WSM-00064: SAML subject confirmation mismatch. Expected : {0}, Actual : {1}.

Cause: Subject confirmation method in SAML assertion did not match the policy requirements.

Action: Check to see that the confirmation method for all the SAML assertions is sender-vouches.
Level: 1

Type: ERROR

Impact: Security

WSM-00065: Error sending request over SSL.

Cause: Failure in creating SSL request possibly due to invalid configuration of Credential Store FrameWork (CSF).

Action: Check the JPS configuration for CSF.
Level: 1

Type: ERROR

Impact: Other

WSM-00066: The matching certificate for the given Subject Key Identifier (SKI) cannot be found.

Cause: None

Action: None
Level: 1

Type: NOTIFICATION

Impact: Security

WSM-00067: None SOAP message parts can be encrypted.

Cause: The elements to be encrypted in the policy were selected to be either of soap Envelope/Body/Header.

Action: The core soap nodes cannot be encrypted according to WS-Security 1.0 specification.
Level: 1

Type: ERROR

Impact: Security

WSM-00068: The security token is missing.

Cause: Security token was expected but was not found.

Action: Security token is missing. Resend request with valid Security token.
Level: 1

Type: ERROR

Impact: Security

WSM-00069: The security header is missing. Ensure that there is a valid security policy attached at the client side, and the policy is enabled.

Cause: Security header was expected but was not found.

Action: Security header is missing. It could be that client side policy has not been applied. Resend request with appropriate Security header.
Level: 1

Type: ERROR

Impact: Security

WSM-00070: The nonce cannot be validated.

Cause: Failure occurred while performing nonce Validation.

Action: This may be due to a repeated value of nonce. Resend the request with a valid nonce.
Level: 1

Type: ERROR

Impact: Security

WSM-00071: Error validating the wsu:Created attribute.

Cause: Failure occurred while doing Created(Timestamp) validation.

Action: Resend the request with a valid timestamp, and or within the expiration limits.
Level: 1

Type: ERROR

Impact: Security

WSM-00072: An encryption algorithm suite policy compliance failure occurred.

Cause: Failure occurred in encryption algorithms policy compliance check.

Action: Check the encryption algorithm requirements of the policy and resend the message with appropriate value of algorithm suite.
Level: 1

Type: ERROR

Impact: Security

WSM-00073: The mechanism {0} used in the authentication header is not supported.

Cause: The value of mechanism attribute used was not supported.

Action: Change the policy to point to valid value of mechanism(basic), and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00074: The authorization header {0} is not correctly encoded using the Base64 encoding.

Cause: The authorization header was not encoded according to Base64 requirements.

Action: Encode the header with Base64(username:realm:password) format and resend the request.
Level: 1

Type: ERROR

Impact: Security

WSM-00075: The realm property is not configured in the policy.

Cause: The realm property was not configured in the policy.

Action: Configure appropriate value of realm inside the policy.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00076: The user name is missing from the encoded authorization header.

Cause: The Authorization header did not contain a properly encoded username, or username was null.

Action: Encode the header with Base64(username:realm:password) format and resend the request.
Level: 1

Type: NOTIFICATION

Impact: Security

WSM-00077: The password is missing from the encoded authorization header.

Cause: The Authorization header did not contain password encoded properly, or password was null.

Action: Encode the header with Base64(username:realm:password) format and resend the request.
Level: 1

Type: ERROR

Impact: Security

WSM-00078: The configuration of the credentials in the policy is incorrect.

Cause: Credential configuration in the policy was incorrect.

Action: Configure policy with valid Credential Store Framework (CSF) key, or username/password properties.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00079: The <BinarySecurityToken> element is missing.

Cause: <BinarySecurityToken> was not found.

Action: For reference mechanisms that are configured with value direct, send the certificate inside <BinarySecurityToken> element.
Level: 1

Type: ERROR

Impact: Security

WSM-00080: STR Dereferencing Transform not found

Cause: STR Dereferencing Transform was not found.

Action: For reference mechanisms that are configured with value SKI, the Transforms section should contain the STR Dereferencing Transform.
Level: 1

Type: ERROR

Impact: Security

WSM-00081: The X.509 certificate is not signed.

Cause: The X509 token used was not signed according to requirements of certificate authentication scenario.

Action: Sign the X509 token (depending upon the reference mechanism used) for certificate authentication.
Level: 1

Type: ERROR

Impact: Security

WSM-00082: The roles and/or attributes of the user profile cannot be retrieved.

Cause: No information could be obtained regarding the user roles or attributes.

Action: Try resending the request for another user.
Level: 1

Type: ERROR

Impact: Security

WSM-00083: Error computing the digest for this reference.

Cause: Digest computation for the <Reference> failed.

Action: Check log file for possible cause.
Level: 1

Type: ERROR

Impact: Security

WSM-00084: Error computing <SignatureValue> for this signature block.

Cause: Signature value computation for the signature block failed.

Action: Check log file for possible cause.
Level: 1

Type: ERROR

Impact: Security

WSM-00085: The certificates cannot be retrieved from the keystore.

Cause: Failure occurred while trying to retrieve certificate from keystore.

Action: Use a valid alias for the certificate and retry the operation.
Level: 1

Type: ERROR

Impact: Security

WSM-00086: Error initializating nonce cache.

Cause: Failure occurred while initializing iAS Cache.

Action: Check log file for possible cause.
Level: 1

Type: ERROR

Impact: Security

WSM-00087: Either {0} property or the oracle.j2ee.home system property is not set.

Cause: The cache configuration file for iAS cache was not found.

Action: Set the system property oracle.j2ee.home or javacache.config.home system property to the path of the configuration file javacache.xml.
Level: 1

Type: ERROR

Impact: Security

WSM-00088: The ObSSOCookie is missing.

Cause: The OAM security token was not found.

Action: Resend the request by embedding the ObSSOCookie token inside a <BinarySecurityToken> element.
Level: 1

Type: ERROR

Impact: Security

WSM-00089: The attachments security transform is incorrect. Expected : {0}, Actual : {1}.

Cause: The attachment security transform used was incorrect.

Action: Refer to the recipient's policy for information about which SwA Security Transform is to be used.
Level: 1

Type: ERROR

Impact: Security

WSM-00090: The signature for the attachment is non-compliant.

Cause: The attachment signature was not compliant.

Action: Refer to the recipient's policy for information about which SwA Security Transform is to be used.
Level: 1

Type: ERROR

Impact: Security

WSM-00091: The encryption of the attachment is non-compliant.

Cause: The attachment encryption was not compliant.

Action: Refer to the recipient's policy for information about which SwA Security Transform is to be used.
Level: 1

Type: ERROR

Impact: Security

WSM-00092: The <EncryptedKey> element is missing in the request. Ensure that there is a message protection policy attached at the client side.

Cause: No <EncryptedKey> elements were found in the request.

Action: Refer to the WS-Security 1.0 and 1.0 specifications for the semantics.
Level: 1

Type: ERROR

Impact: Security

WSM-00093: The <saml:Assertion> element is missing in the security header. Ensure that there is a SAML token policy attached at the client side. Tokens found in the security header are:- {0}.

Cause: No SAML assertions were found inside the security Header.

Action: Resend the message with at least one SAML assertion in the header.
Level: 1

Type: ERROR

Impact: Security

WSM-00094: The negotiated cipher suite does not meet policy requirements. Expected : {0}, Actual : {1}.

Cause: The negotiated cipher suite did not meet policy requirements.

Action: Check the recipient's policy for the permitted values of the cipher suite.
Level: 1

Type: ERROR

Impact: Security

WSM-00095: There is more than one assertion assigned to the same category {0} in the security policy.

Cause: Two or more assertions assigned to the same category were used.

Action: Ensure that assertions inside a security policy belong to different categories.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00096: The order of the assertions is incorrect.

Cause: Assertion order does not match the requirements of policy.

Action: Use the following order for client side policy : authentication -> msgprotection or authentication -> authorization and following for server side security policy msg-protection -> authentication or msg-protection -> authentication -> authorization.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00097: HTTP basic authentication header is missing.

Cause: HTTP basic authentication header was missing.

Action: Client must provide the HTTP basic authentication header.
Level: 1

Type: NOTIFICATION

Impact: Security

WSM-00098: User realm {0} is either null or is a mismatch with service realm {1}.

Cause: User realm was either null or was a mismatch with service realm.

Action: Make sure user realm sent from client matches with the service realm.
Level: 1

Type: NOTIFICATION

Impact: Security

WSM-00099: Username, password, or both are missing from the HTTP authentication header.

Cause: Username, password, or both were missing from HTTP authentication header.

Action: Make sure the HTTP request header contains the username/password token.
Level: 1

Type: ERROR

Impact: Security

WSM-00100: Found more than one keystore files {0} in application classpath. By default the first keystore is used. Make sure the desired keystore is being used by clearing others from the classpath.

Cause: Found more than one keystore file in application classpath. By default, the first keystore is used.

Action: To ensure the desired keystore is being used, remove other keystores from the classpath, if possible.
Level: 1

Type: WARNING

Impact: Security

WSM-00101: The specified keystore file {0} cannot be found; it either does not exist or its path is not included in the application classpath.

Cause: Keystore file did not exist or its path was either incorrect or not included in the application classpath.

Action: Verify the keystore file does exist and its path is included in the application classpath.
Level: 1

Type: ERROR

Impact: Security

WSM-00102: The specified user/subject does not belong to any role in system ID store.

Cause: The subject/user did not belong to any defined role in system ID store.

Action: Verify and make sure that the specified user belongs to one or more roles.
Level: 1

Type: ERROR

Impact: Security

WSM-00103: The policy is configured incorrectly without specifying roles, or denyAll or permitAll elements.

Cause: The policy was incorrectly configured with no roles and no denyAll/permitAll elements.

Action: Correct the policy by configuring it with a denyAll element, a permitAll element, or at least one role.
Level: 1

Type: ERROR

Impact: Security

WSM-00104: The specified JPS context {0} cannot be found in system-level JPS configuration file.

Cause: The JPS context could not be found in system level JPS configuration.

Action: Verify system level JPS configuration file to ensure that it contains the context.
Level: 1

Type: ERROR

Impact: Security

WSM-00105: Credential Store service instance is missing. Either the Oracle WSM JPS context being used for the keystore does not contain a reference to the Credential Store service instance, or the reference is not valid. The Credential Store service instance needs to be declared at the same level (system or application) as the keystore service instance. Therefore, if an application-level keystore is being used, a Credential Store Framework (CSF) store must also be declared at the application level.

Cause: No Credential Store (CSF) was found at the level where keystore was used.

Action: Verify that the WSM JPS context is configured correctly. The error indicates that either the WSM JPS context which is being used for keystore does not contain reference to the Credential Store service instance, or the reference is not valid. The Credential Store service instance needs to be declared at the same level (system or application) as the keystore service instance. Therefore, if an application level keystore is being used, a CSF store must also be declared at the the application level.
Level: 1

Type: ERROR

Impact: Security

WSM-00106: Assertion assigned to a non-security category {0} cannot be added to policy assigned to a security category.

Cause: Assertion belonging to non-security categories could not be added to policies belonging to security category.

Action: Ensure that assertions in security policy also belongs to security category.
Level: 1

Type: ERROR

Impact: Security

WSM-00107: Assertion belonging to {0} category is not valid for generic policy. Only assertion of type security/logging can be added to a generic policy (policy applicable to clients and servers). Check the assertions added to the generic policy.

Cause: Invalid assertions were found in generic policy.

Action: Only assertion of type security/logging can be added to a generic policy (policy applicable to clients and servers). Recheck the assertions added to the generic policy.
Level: 1

Type: ERROR

Impact: Security

WSM-00108: If password type is set to digest, addNonce and addCreated should be true.

Cause: UserNameToken Assertion had Passwordtype as digest but addNonce or addCreated was false.

Action: In case of passwordtype as digest, addNonce and addCreated both should be true. Recheck the assertion.
Level: 1

Type: ERROR

Impact: Security

WSM-00109: Algorithm suite is not supported, only TripleDes is supported for Kerberos assertion.

Cause: Kerberos Assertion had algorithm-suite other than TripleDES.

Action: Only TripleDES algorithm is supported in case of Kerberos, so set algorithm-suite as TripleDes.
Level: 1

Type: ERROR

Impact: Security

WSM-00110: Basic192 and *RSA15 algorithm-suites are not supported for SSL. Change the algorithm suite to one that is supported.

Cause: Basic192 or RSA algorithm-suite was used for SSL.

Action: Use other supported Algorithm-suite for SSL except Basic192 and RSA algorithms.
Level: 1

Type: ERROR

Impact: Security

WSM-00111: Keystore is not properly configured in JPS config.

Cause: Keystore was not properly configured in JPS configuration or through config override properties.

Action: Check the keystore configuration, and try again.
Level: 1

Type: ERROR

Impact: Security

WSM-00112: Missing keystore service instance reference in Oracle WSM JPS context.

Cause: Keystore Service instance reference was not found in WSM JPS context.

Action: Add the keystore service instance reference to WSM JPS context, and try again.
Level: 1

Type: ERROR

Impact: Security

WSM-00113: Unsupported configuration value for Client Credential Configuration location.

Cause: An unsupported configuration value of Client Credential location configuration was provided.

Action: Refer to the documentation for valid values and add the proper configuration value for Client Credential Configuration Location, and try again.
Level: 1

Type: ERROR

Impact: Security

WSM-00114: No matching SSL cipher suite is found for algorithm suite value, specified in the Policy.

Cause: No matching SSL cipher suite was found for algorithm suite value, specified in WS Policy.

Action: Set algorithm suite of Web Service policy to a value that has matching SSL cipher suite.
Level: 1

Type: ERROR

Impact: Security

WSM-00115: JSSE System Property for SSL cipher suite is either not set or does not match algorithm suite value specified in WS Policy.

Cause: JSSE System Property for SSL cipher suite was either not set or did not match algorithm suite value specified in WS Policy.

Action: Set JSSE System Property (https.cipherSuites) to a value that matches algorithm suite as specified in WS Policy.
Level: 1

Type: ERROR

Impact: Security

WSM-00116: Error retrieving SOAP body from SOAP message.

Cause: An error ocurred while retrieving SOAPBody from SOAPMessage. Either the SOAPMessage was not proper or had been tampered with.

Action: Check whether the SOAPMessage is according to the Specifications and try again.
Level: 1

Type: ERROR

Impact: Security

WSM-00117: Error occurred while transforming the security header.

Cause: TransformerException occurred while transforming the WssHeader to String. The SOAPMessage might not have been proper or it did not conform to the specifications.

Action: Check the SOAPMessage and try again.
Level: 1

Type: ERROR

Impact: Security

WSM-00118: OAM token can be inserted only on hosted clients where authenticated subject has been established.

Cause: Insertion of an OAM token tried from a non-hosted client where Authenticated Subject is not established.

Action: Try to add OAM token from a hosted client as only the hosted clients can insert the OAM token extracting it from Authenticated Subject
Level: 1

Type: ERROR

Impact: Security

WSM-00119: Either authorization header or requireTLS must be present.

Cause: The security policy attached did not have either auth Header or requireTLS set to true.

Action: Change the policy to have either auth Header or requireTLS to be true.
Level: 1

Type: ERROR

Impact: Security

WSM-00120: Cannot compute endorsing signature as no message signature is present.

Cause: The security policy did not sign anything from the message, so no signature was there. Endorsing Signature could not be computed as the signature which it was trying to endorse was not present.

Action: Change the policy to Sign at least something in the message.
Level: 1

Type: ERROR

Impact: Security

WSM-00121: Only the attachments are to be signed/encrypted and they are not present.

Cause: Only the attachments were to be signed/encrypted and they were not present.

Action: Retry after putting attachments in the SOAP Message.
Level: 1

Type: ERROR

Impact: Security

WSM-00122: Valid timestamp is not present in the message.

Cause: Timestamp was not present in the message or the timestamp present did not conform to specifications.

Action: Ensure the timestamp is present in the message.
Level: 1

Type: ERROR

Impact: Security

WSM-00123: Timestamp of the message is in future.

Cause: The message had Created timestamp of a time in future so it failed Future message validation.

Action: Ensure freshness of the message and check policy-accessor-config.xml for the configured values of agent.clock.skew.
Level: 1

Type: ERROR

Impact: Security

WSM-00124: Timestamp of the message is in past.

Cause: The message was older than the permissible time limit so it failed Past message validation.

Action: Ensure freshness of the Message and check the policy-accessor-config.xml for the configured values of agent.clock.skew and agent.expire.time.
Level: 1

Type: ERROR

Impact: Security

WSM-00125: Password digest validation failed.

Cause: The password digest in the message was not correct so it failed the digest validation.

Action: Retry after ensuring password digest is proper.
Level: 1

Type: ERROR

Impact: Security

WSM-00126: Subject does not contain JPS user.

Cause: The subject mentioned did not have the JPS User.

Action: Retry after ensuring JPS user in the subject.
Level: 1

Type: ERROR

Impact: Security

WSM-00127: User not in identity store.

Cause: The user mentioned was not present in the identity store.

Action: Retry after ensuring that user is present in the identity Store.
Level: 1

Type: ERROR

Impact: Security

WSM-00128: Keystore instance is null.

Cause: Could not obtain keystore instance. Either the keystore instance type was wrong or the keystore configuration was wrong.

Action: Check JPS configuration settings. Use correct keystore instance type.
Level: 1

Type: ERROR

Impact: Security

WSM-00129: Unsupported SAML token provided : {0}.

Cause: An unsupported SAML token confirmation method was provided.

Action: Provide a supported SAML token confirmation method and retry the operation.
Level: 1

Type: ERROR

Impact: Security

WSM-00130: SAML assertion subject is missing.

Cause: The SAML assertion subject name was not specified.

Action: Provide the SAML assertion subject and retry the operation.
Level: 1

Type: ERROR

Impact: Security

WSM-00131: Unsupported data encryption algorithm: {0}.

Cause: An unsupported data encryption algorithm was provided.

Action: Consult the documentation for the supported encryption algorithms and retry the operation.
Level: 1

Type: ERROR

Impact: Security

WSM-00132: Invalid JPS configuration.

Cause: An invalid JPS configuration was provided.

Action: Make sure that the JPS configuration is valid.
Level: 1

Type: ERROR

Impact: Security

WSM-00133: Unsupported MessageContext type {0}.

Cause: Unsupported MessageContext type was provided.

Action: Correct the MessageContext type and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-00134: The signature key, {0}, is not retrieved due to exception {1}.

Cause: Error occurred while obtaining the signature key from store.

Action: Check JPS configuration settings. Make sure that the key password , keystore password, and key alias are valid.
Level: 1

Type: ERROR

Impact: Security

WSM-00135: The encryption key, {0}, is not retrieved due to exception {1}.

Cause: Error occurred while obtaining encryption key from store.

Action: Check JPS configuration settings. Use correct key password, keystore password, and key alias.
Level: 1

Type: ERROR

Impact: Security

WSM-00136: The signature certificate, {0}, is not retrieved due to exception {1}.

Cause: Failure occurred while retrieving the signature certificate from store.

Action: Check JPS configuration settings for keystore location and make sure that the requested certificate is present.
Level: 1

Type: ERROR

Impact: Security

WSM-00137: The encryption certificate, {0}, is not retrieved due to exception {1}.

Cause: Failure occurred while retrieving the encryption certificate from store.

Action: Check JPS configuration settings for keystore location and make sure that the requested certificate is present.
Level: 1

Type: ERROR

Impact: Security

WSM-00138: The path to the certificate is invalid. Validation failed for the certificate {0} Certificates in cert path used for validation are:- {1}

Cause: The intermediate and root certificates of the certificate were not present in the keystore during verification.

Action: Make sure that the entire certificate chain is available in the keystore for verification.
Level: 1

Type: ERROR

Impact: Security

WSM-00139: The scenario category {0} is not supported.

Cause: The scenario category is not supported.

Action: Consult the Oracle documentation for supported categories.
Level: 1

Type: ERROR

Impact: Security

WSM-00140: Invalid execution stage {0} resulting in system internal error.

Cause: System encountered an invalid execution stage.

Action: Retry the operation, If problem persists contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Security

WSM-00141: Error retrieving SOAP header from SOAP message.

Cause: An error occurred while retrieving the header from the SOAP Message. The SOAP message was invalid or was tampered with.

Action: Make sure that the SOAP message is valid according to the specifications and retry the operation.
Level: 1

Type: ERROR

Impact: Security

WSM-00142: Assertion belonging to {0} category is not valid for Component policy

Cause: Assertion belonging to authentication or message protection category was found in Component policy and it is invalid.

Action: Modify the policy to correct the problem and retry the operation.
Level: 1

Type: ERROR

Impact: Security

WSM-00143: Failure creating Java Keystore instance for type {0}.

Cause: Either the keystore type provided is not supported or there is no implementation provider for Java keystore.

Action: Consult the Oracle documentation for supported Keystore types and make sure the implementation provider for Java Keystore is available.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00144: Failure retrieving Keystore aliases.

Cause: Keystore may have not been initialized.

Action: Check the log file for possible causes and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00145: Keystore location or path can not be null or empty; it must be configured through JPS configuration or policy configuration override.

Cause: Keystore location/path was either missing, set to be null, or empty.

Action: Make sure that Keystore location is configured properly in the JPS configuration or through policy configuration override.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00146: Keystore type {0} defined using keystore.type property in the JPS configuration or through policy configuration override is not supported.

Cause: Invalid or unsupported keystore.type property value was found.

Action: Consult the oracle documentation to ensure that a valid keystore.type is configured either through JPS configuration or using policy configuration override.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00147: JPS context property is no longer supported in policy configuration

Cause: Unsupported JPS context property value was found.

Action: Remove JPS context property from the configuration file.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00148: Security policy cannot be applied to streamed attachments. Streaming should be turned off if there are any security policies for attachments.

Cause: Security policy cannot be applied to streamed attachments.

Action: Make sure streaming is off if security policies are being used for attachments.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00149: SAML assertion is missing.

Cause: Failed to locate SAML assertion with ID {0}.

Action: Make sure that a valid SAML asssertion exists.
Level: 1

Type: ERROR

Impact: Security

WSM-00150: Processed header list fetched from InterceptorContext is null, agentFunction:{0}, listType:{1}.

Cause: Processed header list fetched from InterceptorContext is null.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Security

WSM-00151: Role class {0} specified in the policy is either invalid or is not available in the classpath. Exception thrown : {1}.

Cause: Class name required for retrieving principal/role from subject is either invalid or class not present in the classpath

Action: Specify a valid class name in the policy and ensure that the instances of the class specified are associated with the subject created.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00152: Callback {0} is not supported by Oracle WSM callback handler.

Cause: Callback specified is not supported by Oracle WSM callback handler.

Action: Specify a valid callback class that Oracle WSM callback handler can support.
Level: 1

Type: WARNING

Impact: Security

WSM-00153: Error retrieving Weblogic Server subject from JPS subject using SubjectSecurityUtil API

Cause: A failure occurred while converting JPS subject to Weblogic Server subject.

Action: Check log file for possible cause.
Level: 1

Type: ERROR

Impact: Security

WSM-00154: The empty or all-spaces value set explicitly for property {0} is detected and it is not valid value.

Cause: The property value was probably set unintentionally to empty or all-spaces through policy configuration override or JPS configuration.

Action: Make sure that the value provided either through policy configuration override, policy binding, or JPS configuration is not empty or all spaces.
Level: 1

Type: ERROR

Impact: Security

WSM-00155: Error retrieving Oracle WSM security policies.

Cause: A failure occurred while retrieving Oracle WSM security policies.

Action: Check log file for possible cause.
Level: 1

Type: ERROR

Impact: Security

WSM-00156: Invalid binary security token.

Cause: Binary security token in the header and the certificate used for endorsing signature did not match.

Action: Make sure a valid binary security token is being passed.
Level: 1

Type: ERROR

Impact: Security

WSM-00157: Recipient key alias not configured and signer certificate was not available because no part of the request was signed.

Cause: Recipient key alias not configured and signer's certificate was not available because no part of request was signed.

Action: Set recipient key alias in service policy or sign part of the request.
Level: 1

Type: ERROR

Impact: Security

WSM-00158: KerberosLoginModule class is not available in the classpath

Cause: The class for the Kerberos login module was not available in the classpath.

Action: Make sure that the KerberosLoginModule class is included in the classpath, and configure the class name properly in policy-config.xml.
Level: 1

Type: ERROR

Impact: Security

WSM-00159: TextCallbackHandler class is not available in the classpath

Cause: The class for the Text callback handler was not available in the classpath.

Action: Make sure that the TextCallbackHandler class is included in the classpath, and configure the class name properly in policy-config.xml.
Level: 1

Type: ERROR

Impact: Security

WSM-00160: The SSL policy must contain a requireTLS element.

Cause: The security policy attached did not have requireTLS set to true.

Action: Change the policy to have requireTLS as true.
Level: 1

Type: ERROR

Impact: Security

WSM-00161: Client encryption public certificate is not configured for Async web service client

Cause: Client encryption public certificate is not configured for async web service client with message protection.

Action: Make sure that client public certificate is configured in client keystore, or provided through client config override for Async web service client that uses message protection
Level: 1

Type: ERROR

Impact: Security

WSM-00162: Invalid recipient cert type: {0} may have been provided through override; It should be either a X509Certificate object or Base64 encoded value in String format.

Cause: Invalid recipient cert type may have been provided through override; It should be either a X509Certificate object or Base64 encoded value in String format.

Action: Verify that only X509Certificate object, or Base64 encoded String value are provided in Policy, descriptor file or through program.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00163: Failure in getting recipient certificate using recipient key alias {0}

Cause: The recipient key alias might not be valid

Action: Check to see if there is such certificate in keystore corresponding to the recipient key alias provided.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00164: Cannot obtain a valid recipient cert for client message sending

Cause: Encountered error while obtaining recipient certificate for sending request.

Action: Must provide valid recipient certificate, or recipient alias for client to send request with message protection.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00165: Creating recipient certificate from base64 encoded string: {0} failed.

Cause: Encountered error while creating recipient certificate from base64 encoded string.

Action: Must provide valid certificate in valid base64 encoded string.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00166: Extract certificate from saved ReplyTo header failed.

Cause: X509Certificate within ReplyTo header element might be invalid.

Action: Ensure that cert. insertion, ReplyTo header serialization/deserializaton to JMS queue are all working properly.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00167: Actual Hostname {0} and Hostname retrieved from Certificate {1} do not match

Cause: HostName verification of certificate retrieved from WSDL failed

Action: Either ensure that the Subject Dn matches the Hostname of the Service or disable the HostName Verification check
Level: 1

Type: ERROR

Impact: Security

WSM-00168: Unable to extract X509Certificate from WSDL Definition Object as WSDL definition Object is unavailable

Cause: WSDL definition required for extraction of X509Certificate not available

Action: Ensure that WSDL Definition Object is available from the MessageContext
Level: 1

Type: ERROR

Impact: Security

WSM-00169: Error decrypting the request message.

Cause: The request message could not be decrypted using the key specified for decryption.

Action: Ensure that the key used for decryption is same as the one used for encryption.
Level: 1

Type: ERROR

Impact: Security

WSM-00170: There are no assertions available under the ExactlyOne policy operator.

Cause: There are no assertions under ExactlyOne policy operator.

Action: Ensure that one or more security assertions are kept under ExactlyOne policy operator.
Level: 1

Type: ERROR

Impact: Security

WSM-00171: A client policy contains an ExactlyOne policy operator.

Cause: A client policy contained an ExactlyOne policy operator.

Action: Remove the ExactlyOne policy operator or switch to a service binding.
Level: 1

Type: ERROR

Impact: Security

WSM-00172: A generic policy contains an ExactlyOne policy operator.

Cause: A generic policy contained an ExactlyOne policy operator.

Action: Remove the ExactlyOne policy operator or switch to a service binding.
Level: 1

Type: ERROR

Impact: Security

WSM-00173: A policy contains more than one ExactlyOne policy operator.

Cause: A policy contained more than one ExactlyOne policy operator.

Action: Remove the additional ExactlyOne policy operators.
Level: 1

Type: ERROR

Impact: Security

WSM-00174: A policy contains a nested ExactlyOne policy operator.

Cause: A policy contained a nested ExactlyOne policy operator.

Action: Remove the nested ExactlyOne policy operators.
Level: 1

Type: ERROR

Impact: Security

WSM-00175: Recipient Certificate for async callback client is not found under the ReplyTo element in async callback client message context

Cause: Recipient cert. for async callback client is not available from message context.

Action: Ensure that original async client has public encryption certificate configured and is inserted into the ReplyTo header or the original async request. Also ensure that the original ReplyTo header along with client encryption certification is preserved and restored to the callback client message context.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00176: The mapped long name(s) for property {0} is null, the property might not be available for client programmatic override. Make sure it is indeed the intension, otherwise, add a mapping to map ConfigOverrideMapping.

Cause: The config override property does not have a corresponding long name mapping

Action: Make sure this is indeed intended, otherwise, add a mapping to the ConfigOverrideMapping.
Level: 1

Type: WARNING

Impact: Configuration

WSM-00177: The CSF key provided by the user is not present in the credential store. So using the default key is being used.

Cause: The CSF key provided by the user is not present in the credential store

Action: Provide a valid key. Till then the default key will be used.
Level: 1

Type: WARNING

Impact: Security

WSM-00178: Public key not found for SAML signature verification.

Cause: Public key not found for SAML signature verification

Action: Ensure that public key is present in Security header which is reqruied For SAML signature verification
Level: 1

Type: WARNING

Impact: Configuration

WSM-00179: SAML assertion issuer name is invalid.

Cause: SAML assertion issuer name is invalid.

Action: Check to see that the overridden SAML trused issuers has SAML assertion issuer name.
Level: 1

Type: ERROR

Impact: Security

WSM-00180: The trust version {0} is not supported for policy advertisement, hence ignored. The default trust version {1} is advertised.

Cause: The trust version specified in the policy is not supported.

Action: Modify the policy with a supported trust version.
Level: 1

Type: WARNING

Impact: Configuration

WSM-00181: A policy issued-token attributes require-internal-reference and require-external-reference both are false, one of them has to be true.

Cause: A policy issued-token attribute require-internal-reference and require-external-reference can not both be false.

Action: At least one of the attribute require-internal-reference and require-external-reference must be set to true
Level: 1

Type: ERROR

Impact: Configuration

WSM-00182: A policy request-security-token-template element attribute token-type has an unsupported value: {0}

Cause: A policy request-security-token-template element contains a token-type that is not supported.

Action: Check documentation for supported token-type
Level: 1

Type: ERROR

Impact: Configuration

WSM-00183: A policy request-security-token-template element attribute algorithm-suite has a value: {0} which does not match to that of msg-security: {1}, change it to match {1}.

Cause: A policy request-security-token-template element contains an algorithm-suite value that does not match to that of msg-security.

Action: Change the algorithm-suite attribute value to match exactly the one in msg-security
Level: 1

Type: ERROR

Impact: Configuration

WSM-00184: An attribute trust-version has an unsupported version: {0}

Cause: A policy contains an unsupported WS-TRUST version.

Action: Check documentation for supported WS-TRUST version
Level: 1

Type: ERROR

Impact: Configuration

WSM-00185: Attribute require-client-entropy and require-server-entropy can not both be set to false, at lease one of them must be set to true.

Cause: A policy can not have both require-client-entropy and require-server-entropy attributes set to false.

Action: At lease set one of them to true
Level: 1

Type: ERROR

Impact: Configuration

WSM-00186: A policy request-security-token-template key-type attribute is expected to be: {0}, but got: {1}

Cause: A policy request-security-token-template key-type attribute value is not set to the expected Bearer.

Action: Set the attribute value to the expected
Level: 1

Type: ERROR

Impact: Configuration

WSM-00187: A policy request-security-token-template key-type attribute is expected to be: {0}, but got: {1}

Cause: A Bearer policy request-security-token-template key-type attribute value is not set to the expected Symmetric or Public.

Action: Set the attribute value to one of the expeted value Symmetric or Public
Level: 1

Type: ERROR

Impact: Configuration

WSM-00188: STS Trust Config policy attribute port-uri has invalid value "{0}", it must be not null, not empty and in the format of http(s)://host:port/sts-service

Cause: STS trust config attribute port-uri is either null, empty or not in the format of "http(s)://host:port/sts-service-name".

Action: Provide valid attribute value which is in the format of "http(s)://host:port/sts-service"
Level: 1

Type: ERROR

Impact: Configuration

WSM-00189: STS Trust Config policy attribute port-endpoint has invalid value "{0}", it must be not empty and in the format of target-namespace#wsdl.endpoint(service-name/port-name)

Cause: STS trust config attribute port-endpoint is either empty or not in the format of "target-namespace#wsdl.endpoint(service-name/port-name)".

Action: Provide valid attribute value which is in the format of "target-namespace#wsdl.endpoint(service-name/port-name)"
Level: 1

Type: ERROR

Impact: Configuration

WSM-00190: STS Trust Config policy attribute policy-reference-uri can not have empty value.

Cause: The value of STS trust config attribute policy-reference-uri is empty or not in the URI format

Action: Specify value for attribute policy-reference-uri
Level: 1

Type: ERROR

Impact: Configuration

WSM-00191: STS Trust Config policy attribute sts-keystore-recipient-alias can not have null or empty value.

Cause: The value of STS trust config attribute sts-keystore-recipient-alias is null or empty

Action: Specify a non null or empty value for attribute sts-keystore-recipient-alias
Level: 1

Type: ERROR

Impact: Configuration

WSM-00192: Kerberos name identifier format is not supported for SAML 1.1 token.

Cause: Kerberos name identifier format is not supported for SAML 1.1 token.

Action: Kerberos name identifier format is only for SAML 2.0 token, use other name identifier formats.
Level: 1

Type: ERROR

Impact: Security

WSM-00193: Security policy contains NULL or empty value for signed-element local name or namespace.

Cause: Security policy contains NULL or empty value for signed-element local name or namespace.

Action: Signed-element local name or namespace must not be null or empty.
Level: 1

Type: ERROR

Impact: Security

WSM-00194: Security policy contains NULL or empty value for signed-part header namespace.

Cause: Security policy contains NULL or empty value for signed-part header namespace.

Action: Signed-part header namespace must not be null or empty.
Level: 1

Type: ERROR

Impact: Security

WSM-00195: Security context for derived key unknown (cannot determine the base symmetric key).

Cause: Security context for derived key unknown (cannot determine the base symmetric key).

Action: DerivedKeyToken should include SecurityReferenceToken (can only be empty in responses where the message context includes the base key).
Level: 1

Type: ERROR

Impact: Security

WSM-00196: Unable to resolve base key referenced in DerivedKeyToken.

Cause: Unable to resolve base key referenced in DerivedKeyToken.

Action: Ensure the SecurityTokenReference in the DerivedKeyToken specifies a valid base key within the security context.
Level: 1

Type: ERROR

Impact: Security

WSM-00197: Unsupported SecurityTokenReference type for DerivedKeyToken.

Cause: Unsupported SecurityTokenReference type for DerivedKeyToken.

Action: Ensure the SecurityTokenReference in the DerivedKeyToken is one of the supported types.
Level: 1

Type: ERROR

Impact: Security

WSM-00198: Unable to resolve EncryptedKey that matches EncryptedKeySHA1 in KeyInfo.

Cause: Unable to resolve EncryptedKey that matches EncryptedKeySHA1 in KeyInfo.

Action: The value of the EncryptedKeySHA1 should match an encrypted key in the security context.
Level: 1

Type: ERROR

Impact: Security

WSM-00199: Unsupported key identifier type "{0}" in security token reference.

Cause: Unsupported key identifier type in security token reference.

Action: Use only of the supported key idetifier types in the security token.
Level: 1

Type: ERROR

Impact: Security

WSM-00200: Exception encountered while checking compliance; returning false.

Cause: Exception encountered while checking compliance; returning false.

Action: Check log for exception details.
Level: 1

Type: ERROR

Impact: Security

WSM-00201: There are no <EncryptedKey> elements in the request.

Cause: There are no <EncryptedKey> elements in the request.

Action: The request should have an <EncryptedKey> element.
Level: 1

Type: ERROR

Impact: Security

WSM-00202: Proof key type is invalid, valid vaues are null, public, symmetric.

Cause: The value of ketype is invalid for SAML Issued Token Policy , valid values are null (no proof key), public, symmetric

Action: Specify valid value for keytype based on the policy
Level: 1

Type: ERROR

Impact: Configuration

WSM-00203: Invalid OPSS Trust Service

Cause: OPSS TrustService is empty or null

Action: Configure Trust Service in OPSS
Level: 1

Type: ERROR

Impact: Configuration

WSM-00204: Invlaid issued token from trust token exchange

Cause: Issued token is null

Action: Check Logs and correct any errors during issuance
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00205: Proof key type is invalid, valid value is bearer

Cause: The value of ketype is invalid for SAML Bearer Issued Token Policy , valid value is bearer

Action: Specify bearer as the key type for this policy
Level: 1

Type: ERROR

Impact: Configuration

WSM-00206: Requester credentials for authenticating to STS are invalid

Cause: Requester Credentials required for autenticating to STS are missing

Action: Configure sts.auth.user.csf.key or sts.auth.x509.csf.key in issued token policy
Level: 1

Type: ERROR

Impact: Configuration

WSM-00207: Assymetric proof key is invalid

Cause: Assymetric proof key is invalid

Action: Configure sts.auth.x509.csf.key in issued token policy
Level: 1

Type: ERROR

Impact: Configuration

WSM-00208: STS On behalf of user is invalid

Cause: STS On behalf of user is invalid

Action: Configure sts.auth.on.behalf.of.csf.key in issued token policy
Level: 1

Type: ERROR

Impact: Configuration

WSM-00209: Permission{0} required to switch the identity not granted to the resource. {1}

Cause: Permission required to switch the identity not granted

Action: Grant Permission for identity switching to the codesource.
Level: 1

Type: ERROR

Impact: Security

WSM-00210: Client is unable to find actual webservice endpoint to set in appliesTo

Cause: Client requires appliesTo and unable to find the actual webservice endpoint URL

Action: Chenck if agent binding ws port ID , service name and port name in log file
Level: 1

Type: ERROR

Impact: Configuration

WSM-00211: Trust token provider tried creating RequestSecurityToken message and it failed because algoirthm use to generate asymmetric key pair was invalid

Cause: Trust token provider tried creating RequestSecurityToken message and it failed because algoirthm use to generate asymmetric key pair was invalid

Action: Check the asymmetric key algorithm
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00212: Trust token provider tried creating RequestSecurityToken message and it failed because assymetic proofk key was invalid

Cause: Trust token provider tried creating RequestSecurityToken message and it failed because assymetic proofk key was invalid

Action: Check if sts.auth.x509.csf.key is configured correctly in issued token client policy
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00213: Unable to parse SOAP message sent by STS

Cause: Unable to parse SOAP message sent by STS

Action: Check if message sent by STS is valid
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00214: Unable to parse RequestSecurityTokenRespnseCollection

Cause: Unable to parse RequestSecurityTokenResponseCollection

Action: Check if RequestSecurityTokenResponseCollection message sent by STS is valid
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00215: Unable to parse STSTrustConfig

Cause: Unable to parse STSTrustConfig

Action: Check if STSTrustConfig is valid
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00216: Unable to create SOAP RequestSecurityToken message

Cause: Unable to create SOAP RequestSecurityToken message

Action: Failure in creating SOAP RequestSecurityToken message, check log files
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00217: STS endpoint URL or WSDL URL (if configured) is invalid

Cause: STS endpoit URL is invalid

Action: Check if STS endpoint URL is valid
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00218: Security token returned by STS is null

Cause: Security token returned by STS is null

Action: Check if RSTR message sent by STS is valid
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00219: Proof token returned by STS is null

Cause: Proof token returned by STS is null

Action: Check if RSTR message sent by STS is valid
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00220: Invalid proof token type, valid values are computedKey and BinarySecret

Cause: Invalid proof token type, valid values are computedKey and BinarySecret

Action: Check the proof token type, valid values are computedKey and BinarySecret
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00221: Computed key in RSTR message sent by STS is invalid

Cause: Computed key in RSTR message sent by STS is invalid

Action: Check the computed key in RSTR message sent by STS
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00222: Computed key algorithm in RSTR message sent by STS is invalid}

Cause: Computed key algorithm in RSTR message sent by STS is invalid, valid value is http://docs.oasis-open.org/ws-sx/ws-trust/200512/CK/PSHA1

Action: Check the computed key in RSTR message sent by STS, valid value is http://docs.oasis-open.org/ws-sx/ws-trust/200512/CK/PSHA1
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00223: Request type is invalid, valid value is issue

Cause: Request type invalid, valid value is issue

Action: Check request type in response sent by STS
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00224: User credentials of the user on behalf of whom the token is to be issued is missing

Cause: User credentials of the user on behalf of whom the token is to be issued is missing

Action: Check on.behalf.of property in issued token policy. If its set to true then either subject or sts.auth.on.behalf.of.csf-key property needs to be present
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00225: STS On behalf of user password is invalid

Cause: STS On behalf of user password is invalid

Action: Configure sts.auth.on.behalf.of.csf.key in issued token policy
Level: 1

Type: ERROR

Impact: Configuration

WSM-00226: Security policy contains NULL or empty value for encrypted-element local name or namespace.

Cause: Security policy contains NULL or empty value for encrypted-element local name or namespace.

Action: Encrypted-element local name or namespace must not be null or empty.
Level: 1

Type: ERROR

Impact: Security

WSM-00227: Could not resolve key to use for decryption.

Cause: Could not resolve key to use for decryption.

Action: Ensure request contains all the information necessary to succesfully resolve decryption key.
Level: 1

Type: ERROR

Impact: Security

WSM-00228: Oracle system user is missing in identity store

Cause: Could not find oracle system user .

Action: Check if OracleSystemUser exists in identity store
Level: 1

Type: ERROR

Impact: Configuration

WSM-00229: jndi.lookup.csf.key missing in policy-accessor-config

Cause: Could not find valid jndi.lookup.csf.key in policy-accessor-config.xml .

Action: Check jndi.lookup.csf.key is configured correclty in policy-accessor-config.xml
Level: 1

Type: ERROR

Impact: Configuration

WSM-00230: Cannot find service information from WSDL {0}

Cause: Cannot find service information from WSDL

Action: Check the service information in the WSDL
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00231: Cannot find client compatible policy for STS {0}, port name {1}

Cause: Cannot find compatible client policy for STS invocation

Action: Check if policy store has compatible client policy
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00232: Failed to create dynamic STS policy

Cause: Failed to create dynamic STS policy

Action: Check exception stack trace for details
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00233: STS WSDL URI {0} is invalid

Cause: STS trust config attribute wsdl-uri is not in the format of "http(s)://host:port/sts-service?wsdl".

Action: Provide valid attribute value which is in the format of "http(s)://host:port/sts-service?wsdl
Level: 1

Type: ERROR

Impact: Configuration

WSM-00234: The <saml:Assertion> element of version {0} is missing in the security header.

Cause: Saml assertion with specific version e.g. 1.1, or 2.0 etc. is missing. in the received message

Action: Check exception stack trace for details
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00235: Failed to initialize dispatcher

Cause: Failed to initialize dispatcher for client to STS communication

Action: Check exception stack trace for details
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00236: Keystore name property value was not set through JPS configuration

Cause: Keystore name property value was not set through JPS configuration.

Action: Make sure that the value is provided for keystore name through JPS configuration.
Level: 1

Type: ERROR

Impact: Security

WSM-00237: FKS keystore with stripeName {0}, keystoreName {1} can not be loaded due to {2}.

Cause: The following FKS keystore-related configuration properties may not be valid:keystore.type, keystore.pass, keystore.name. Also, check permissions on the keystore.

Action: Verify the configuration properties mentioned above and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00238: Unable to read FKS keystore. Grant necessary permission to read FKS keystore, stripe name {0} and keystore name {1}

Cause: FKS keystore may have not been initialized or necessary permissions are not granted.

Action: Ensure that necessary permission to read FKS keystore is granted.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00239: FKS trust store can not be loaded, ensure that necessary permissions are granted.

Cause: FKS trust store can not be loaded, probably necessary permissions are not granted.

Action: Ensure that necessary permission to read FKS trust store is granted.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00240: FKS trust store is NULL, ensure that FKS system trust store exist.

Cause: FKS trust store is NULL, may be it doesn't exists or probably necessary permissions are not granted.

Action: Ensure that FKS trust store exists in system stripe and permissions are granted.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00241: Failure retrieving FKS trust store aliases.

Cause: FKS trust store may have not been initialized.

Action: Check the log file for possible causes and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00242: The certificates cannot be retrieved from the trust store.

Cause: Failure occurred while trying to retrieve certificate from trust store.

Action: Use a valid alias for the certificate and retry the operation.
Level: 1

Type: ERROR

Impact: Security

WSM-00243: Unable to read key from FKS keystore. Grant necessary permission to read alias {2} from FKS keystore, stripe name {0} and keystore name {1}

Cause: Unable to read key from FKS keystore. FKS keystore may have not been initialized or necessary permissions are not granted.

Action: Ensure that alias exists in keystore and necessary permission to read key alias is granted.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00244: Unable to read certificate from FKS keystore. Grant necessary permission to read certificate alias {2} from FKS keystore, stripe name {0} and keystore name {1}

Cause: Unable to read certificate from FKS keystore. FKS keystore may have not been initialized or necessary permissions are not granted.

Action: Ensure that alias exists in keystore and necessary permission to read certificate alias is granted.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00245: Failure retrieving FKS key store aliases.

Cause: Unable to list alias from FKS key store.

Action: Check the log file for possible causes and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00246: Failure retrieving IssuedTokenAssertion from advertised policy.

Cause: Possibilly there is a failure in parsing the advertised policy

Action: Check the log file for possible causes and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-00247: Failed to sign with RSA Key Pair

Cause: Failed to sign with RSA Key Pair

Action: Check exception stack trace for details
Level: 1

Type: ERROR

Impact: Security

WSM-00248: Attesting entity attribute {0} is unsupported.

Cause: Unsupported attesting entity attribute is used

Action: Attesting entity attribute must be DN.
Level: 1

Type: ERROR

Impact: Security

WSM-00249: SAML token DN validation failed for SAML assertion signer DN {0}.

Cause: SAML token DN list validation failed.

Action: Assertion signer DN is not present in trusted DN list, if DN is valid then add it to trusted DNs list.
Level: 1

Type: ERROR

Impact: Security

WSM-00250: Unable to find an implementation class for {0}.

Cause: Unable to find an implementation class for 'javax.el.ExpressionFactory'.

Action: Make sure that the implementation class for 'javax.el.ExpressionFactory' is available in the classpath.
Level: 1

Type: ERROR

Impact: Security

WSM-00251: Failed to create an instance of {0}.

Cause: Failed to create an instance of the javax.el.ExpressionFactory implementation class.

Action: Make sure that the javax.el.ExpressionFactory implementation class can be instantiated.
Level: 1

Type: ERROR

Impact: Security

WSM-00252: Failed to evaluate the constraint expression "{0}" due to the exception: {1}

Cause: Failed to evaluate the constraint expression.

Action: Make sure that the constraint expression is valid. Check exception stack trace for details.
Level: 1

Type: ERROR

Impact: Security

WSM-00253: The constraint expression "{0}" is not valid. The constraint expression should evaluate to the boolean values.

Cause: The constraint expression is not valid.

Action: Make sure that the constraint expression evaluates to the boolean values.
Level: 1

Type: ERROR

Impact: Security

WSM-00254: The current server time is "{0}", incoming message creation time is "{6}", configured agent expiry is {5} seconds, incoming message expiry is {7} seconds, effective message expiry (minimum of agent expiry and incoming message expiry) is {1} seconds, configured clock skew is {2} seconds. The acceptable time range is "{3}" to "{4}". The incoming message is before/after the acceptable time.

Cause: The incoming message is outside the valid range as allowed by clock skew and expiry times.

Action: Adjust times on servers/clients. Check the allowed clockskew and message expiration time and configure them as required.
Level: 1

Type: ERROR

Impact: Security

WSM-00256: The property "{0}" is not set. The csf map "{1}" found in the credential store is being used and the following keys are found in this map <CsfKeyName: UserName>:- {2} The properties found in the JPS config are <PropertyName: Value>:- {3}

Cause: The property value is null.

Action: Make sure that the value provided either through policy configuration override, policy binding, or JPS configuration is not null.
Level: 1

Type: ERROR

Impact: Security

WSM-00257: Callback class name "{0}" set for SAML certificate validation not found

Cause: Callback class set for SAML certificate validation not found.

Action: Make sure that callback class name is correct and added in classpath.
Level: 1

Type: ERROR

Impact: Security

WSM-00258: Callback class name "{0}" set for SAML certificate validation is invalid.

Cause: Callback class set for SAML certificate validation is not valid.

Action: Make sure that callback class correctly extends required class.
Level: 1

Type: ERROR

Impact: Security

WSM-00259: SAML certificate validation callback failed. {0}.

Cause: Callback class set for SAML certificate validation failed.

Action: Check the error message for details.
Level: 1

Type: ERROR

Impact: Security

WSM-00260: SAML over SSL certificate validation failed because certificate returned from callback and actual certificate differ. Actual certificate DN={0} and callback cert DN={1}

Cause: SAML over SSL certificate validation failed because certificate returned from callback and actual certificate differ.

Action: Make sure that client certificate sent over SSL and certificate returned from callback are same.
Level: 1

Type: ERROR

Impact: Security

WSM-00261: SAML certificate validation callback failed because certificate returned from callback is NULL.

Cause: Callback class set for SAML certificate validation failed because certificate returned from callback is NULL.

Action: Check callback implementation class for the reason of null certificate.
Level: 1

Type: ERROR

Impact: Security

WSM-00262: SAML assertion with confirmation method {0} is missing inside signature.

Cause: SAML assertion is missing inside signature.

Action: Ensure that SAML assertion has required inside signature.
Level: 1

Type: ERROR

Impact: Security

WSM-00263: Failed to create SAML token as 'anonymous' user principal found in Subject.

Cause: Failed to create SAML token as 'anonymous' user principal found in Subject.

Action: Make sure that the subject is created from a valid user.
Level: 1

Type: ERROR

Impact: Security

WSM-00264: Must Understand check failed for headers: '{0}' in the SOAP message.

Cause: Unprocessed 'mustUnderstand' header element in SOAP message.

Action: Make sure that you have attached security policy at service side.
Level: 1

Type: ERROR

Impact: Security

WSM-00265: The Username token is missing in the security header. Ensure that there is a Username token policy attached on the client side. Tokens found in the security header are :- {0}.

Cause: Username token was expected in the security header but was not found.

Action: Username token is missing. Resend request with valid username token.
Level: 1

Type: ERROR

Impact: Security

WSM-00266: The Kerberos token is missing in the security header.

Cause: Kerberos token was expected in the security header but was not found.

Action: Resend request with valid kerberos token.
Level: 1

Type: ERROR

Impact: Security

WSM-00268: The certificate to be validated is NULL.

Cause: The certficate to be validated is null.

Action: Make sure that the certificate to be validated is not null.
Level: 1

Type: ERROR

Impact: Security

WSM-00269: There is no trusted certificate found in the trust store.

Cause: Trust store does not have any trusted certificate.

Action: Make sure that the required trusted certificates are present in the trust store.
Level: 1

Type: ERROR

Impact: Security

WSM-00270: The issuer "{0}" is not found in the trust store.

Cause: The issuer certificate is not present in the trust store.

Action: Make sure that the issuer certificate is present in the trust store.
Level: 1

Type: ERROR

Impact: Security

WSM-00271: Basic constraints check failed due to the certificate "{0}" is not a CA certificate.

Cause: The certificate is not a CA certificate.

Action: Make sure that the issuer certificate is a CA certificate.
Level: 1

Type: ERROR

Impact: Security

WSM-00272: Basic Constraints check failed for the certificate "{0}", since only an end-entity certificate may follow this certificate in the certification path chain.

Cause: Basic Constraints check failed for the issuer certificate.

Action: Make sure that the issuer certificate is a valid.
Level: 1

Type: ERROR

Impact: Security

WSM-00273: Failed to verify the issuer "{0}".

Cause: The issuer certificate verification failed.

Action: Check error logs for more details.
Level: 1

Type: ERROR

Impact: Security

WSM-00274: The certification path for the certificate "{0}" is NULL.

Cause: The certification path is found to be null.

Action: Check error logs for more details.
Level: 1

Type: ERROR

Impact: Security

WSM-00275: The Identity type "{0}" is not suported.

Cause: The Identity type published in the WSDL certificate is not supported.

Action: Make sure that the identity type published in the WSDL certificate is either X509Certificate or supported one.
Level: 1

Type: ERROR

Impact: Security

WSM-00276: Validation failed for the identity published in the WSDL endpoint "{1}". Caused By: {0}

Cause: Validation failed for the Identity published in the WSDL certificate.

Action: Check error logs for more details.
Level: 1

Type: ERROR

Impact: Security

WSM-00277: Endorsing signature is not found in the message. Ensure that a compatible policy is attached at the client side. The security policy "{1}" is attached to the service. Tokens found in the security header are :- {0}.

Cause: Endorsing signature is expected in the message but not found.

Action: Make sure that the endorsing signature is included in the message.
Level: 1

Type: ERROR

Impact: Security

WSM-00278: Failed to decrypt the encrypted key due to {1}. Ensure that the client is properly configured with the server certificate. Client should be using this certificate:- {0}.

Cause: An error occurred while decrypting the encrypted key.

Action: Ensure that the client is properly configured with the server's certificate.
Level: 1

Type: ERROR

Impact: Security

WSM-00279: The following Fault Message is received at the client side from the service:- {0}. The client side policy is:- {4}. The service endpoint url is:- {3}. Keystore properties:- {1}. Properties found in the message context (Partial list):- {7}. PolicyReference OverrideProperty: {6} Policy configuration properties (some of these may be overridden by the properties passed in the PolicyReference or message context, for details about the order of precedence of properties consult documentation):- {5}. Other related information:- {2}.

Cause: Fault Message received at the client side from the service

Action: Check the log file for possible causes.
Level: 1

Type: ERROR

Impact: Security

WSM-00311: Keystore reloading failed due to {0}

Cause: Reloading of the keystore failed.

Action: Restart the server to load the latest keystore.
Level: 1

Type: ERROR

Impact: Security

WSM-00314: The Xpath transformation of the type "{0}" is not allowed. Only Xpath transformations of the type "{1}" are allowed. To allow all the Xpath transformations, set the property "{2}" to true.

Cause: The Xpath transformation present in the incoming SOAP message is not supported.

Action: Make sure that incoming SOAP message contains only supported Xpath expressions, see the exception stack trace for details.
Level: 1

Type: ERROR

Impact: Security

WSM-00315: The details of the keystore {0} removed from the system.

Cause: Removing the keystore details as keystore was replaced with a wrong one.

Action: Replace the keystore with a valid one. After keystore has been replaced, it will be reloaded on next invocation.
Level: 1

Type: ERROR

Impact: Security

WSM-00316: The CSF key "{0}" is reserved and can not be used for username credentials. Ensure that the reserved CSF keys {1} and {2} are not used.

Cause: The CSF key being used is reserved and can not be used for username credentials.

Action: Ensure that the reserved CSF keys are not used. Check error logs for more details.
Level: 1

Type: ERROR

Impact: Security

WSM-01501: failure in parsing the policy attachment

Cause: The XML was not well formed, or the XML did not follow the policy attachment schema.

Action: Ensure that the XML is well formed, and the XML follows the policy attachment schema.
Level: 1

Type: ERROR

Impact: Data

WSM-01502: failure in parsing the assertion template

Cause: The XML was not well formed, or the XML did not follow the assertion template schema.

Action: Ensure that the XML is well formed, and the XML follows the assertion template schema.
Level: 1

Type: ERROR

Impact: Data

WSM-01503: failure in parsing the assertion

Cause: The XML was not well formed, or the XML did not follow the assertion schema.

Action: Ensure that the XML is well formed, and the XML follows the assertion schema.
Level: 1

Type: ERROR

Impact: Data

WSM-01504: failure in parsing the property set configuration

Cause: The XML was not well formed, or the XML did not follow the property set Config schema.

Action: Ensure that the XML is well formed, and the XML follows the property set Config schema.
Level: 1

Type: ERROR

Impact: Data

WSM-01505: failure in creating a copy of the policy {0}

Cause: Copying of the policy failed.

Action: Ensure that the policy to be copied is valid. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-01506: failure in creating a copy of the assertion template {0}

Cause: Copying of the assertion template failed.

Action: Ensure that the assertion template to be copied is valid. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-01507: failure in creating a copy of the assertion {0}

Cause: Copying of the assertion failed.

Action: Ensure that the assertion to be copied is valid. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-01508: failure in transforming policy {0} to XML

Cause: The policy could not be serialized to XML.

Action: Ensure that the policy Java object can be serialized to XML format.
Level: 1

Type: ERROR

Impact: Data

WSM-01509: failure in transforming policy set {0} to XML

Cause: The policy set could not be serialized to XML.

Action: Ensure that the policy set Java object can be serialized to XML format.
Level: 1

Type: ERROR

Impact: Data

WSM-01510: failure in transforming policy attachment {0} to XML

Cause: The policy attachment could not be serialized to XML.

Action: Ensure that the policy attachment Java object can be serialized to XML format.
Level: 1

Type: ERROR

Impact: Data

WSM-01511: failure in transforming assertion template {0} to XML

Cause: The assertion template could not be serialized to XML.

Action: Ensure that the assertion template Java object can be serialized to XML format.
Level: 1

Type: ERROR

Impact: Data

WSM-01512: failure in transforming assertion {0} to XML

Cause: The assertion could not be serialized to XML.

Action: Ensure that the assertion Java object can be serialized to XML format.
Level: 1

Type: ERROR

Impact: Data

WSM-01513: failure in transforming configuration {0} to XML

Cause: The configuration could not be serialized to XML.

Action: Ensure that the configuration Java object can be serialized to XML format.
Level: 1

Type: ERROR

Impact: Data

WSM-01514: failure in transforming policy reference {0} to XML

Cause: System could not serialize policy reference to XML.

Action: Ensure passed policy reference Java object doesn't have issues that causes the serialization to XML to fail.
Level: 1

Type: ERROR

Impact: Data

WSM-01515: failure in transforming policy subject {0} to XML

Cause: System could not serialize policy subject to XML.

Action: Ensure passed policy subject Java object doesn't have issues that cause the serialization to XML to fail.
Level: 1

Type: ERROR

Impact: Data

WSM-01524: failure in serialization of WSDL

Cause: WSDL Serialization failed.

Action: Ensure WSDL Extensions are available and configured. Consult diagnostic log for details or contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-01526: WSDL Definition object is null

Cause: WSDL Definition Object is not available

Action: Ensure that a valid WSDL Definition object is sent to OWSM for advertisement of wsdl.
Level: 1

Type: ERROR

Impact: Data

WSM-01600: error in creating or initializing the assertion, key={0}, qname={1}, wspqname={2}, constructorName={3}

Cause: An assertion object could not be created.

Action: Verify that the assertion follows the interface requirements defined in the Oracle documentation.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-01601: failure in loading the resource

Cause: The requested resource could not be loaded.

Action: Ensure that the requested resource is present in the class path.
Level: 1

Type: ERROR

Impact: Configuration

WSM-01602: error in loading class {0}

Cause: The requested class could not be loaded.

Action: Ensure that the requested class is present in the class path.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-01603: failure in parsing the policy

Cause: Parsing of the policy failed.

Action: Ensure that the policy XML follows the policy schema, or a valid policy file exists.
Level: 1

Type: ERROR

Impact: Data

WSM-01604: XML Parser Configuration error

Cause: The XML Parser was not configured properly.

Action: Consult Oracle documentation or Java documentation on how to configure the XML Parser.
Level: 1

Type: ERROR

Impact: Configuration

WSM-01605: XML parser exception

Cause: Parsing of the XML failed.

Action: Ensure that the XML is well formed.
Level: 1

Type: ERROR

Impact: Data

WSM-01606: system I/O error

Cause: The system could not open the Input/Output streams.

Action: Consult the Java documentation.
Level: 1

Type: ERROR

Impact: Files

WSM-01607: XPath expression evaluation error

Cause: Evaluation of the XPATH expression failed.

Action: Ensure that the XPATH expression is valid, and the XML follows the schema.
Level: 1

Type: ERROR

Impact: Data

WSM-01608: The class cannot be found.

Cause: The requested class was not found in the class path.

Action: Ensure that the class name is correct in the configuration files and is in the class path.
Level: 1

Type: ERROR

Impact: Configuration

WSM-01610: cannot initialize standard serializers/deserializers

Cause: The standard serializer and deserializer objects could not be loaded.

Action: Ensure that the product configuration is correct. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-01611: The class cannot be loaded because of Java security restrictions.

Cause: The requested classes could not be loaded due to class loading security restrictions.

Action: Contact the site administrator or consult the Java documentation to ensure that the classes have the necessary Java security permissions.
Level: 1

Type: ERROR

Impact: Configuration

WSM-01612: An instance of the requested class cannot be created.

Cause: The system could not create an instance of the requested class.

Action: Consult the Java documentation or contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-01613: The XML parser cannot be configured.

Cause: The XML parser could not be configured.

Action: Consult the Java documentation on how to configure the XML parser.
Level: 1

Type: ERROR

Impact: Configuration

WSM-01614: The assertion XML Java Document cannot be serialized to a String.

Cause: The assertion XML Java Document could not be serialized to a String.

Action: Check the assertion for any errors and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-01615: The assertion XML String cannot be converted to a Java object.

Cause: The assertion XML String could not converted to a Java Document.

Action: Ensure that the String being converted to XML is a well-formed XML.
Level: 1

Type: ERROR

Impact: Data

WSM-01616: Policy {0} cannot be inserted into the WSDL.

Cause: The WSDL extensions for the policy could not be found or were incorrectly configured.

Action: Ensure that the WSDL extensions for the policy being injected are available and configured. Consult Oracle documentation for more information.
Level: 1

Type: ERROR

Impact: Data

WSM-01617: error in parsing the policies embedded in the WSDL

Cause: The WSDL extensions for the policy could not be found or were incorrectly configured.

Action: Ensure that the WSDL extensions for policy are available and configured. Consult Oracle documentation for more information.
Level: 1

Type: ERROR

Impact: Data

WSM-01618: error in parsing the policy references embedded in the WSDL

Cause: The XML for the policy references in the WSDL could not be parsed.

Action: Ensure that the WSDL extensions for the policy reference are available and configured. Consult Oracle documentation for more information.
Level: 1

Type: ERROR

Impact: Data

WSM-01619: This assertion type is not recognized.

Cause: The assertion type was not recognized.

Action: Consult Oracle documentation for the supported assertion types.
Level: 1

Type: ERROR

Impact: Data

WSM-01620: cannot convert XML Java Document to String

Cause: The XML Java Document being converted was not well formed.

Action: Ensure that the assertions can be serialized to a String.
Level: 1

Type: ERROR

Impact: Data

WSM-01621: Policy intersection algorithm is not defined for assertion type :

Cause: The policy intersection algorithm was not found for the assertion.

Action: Ensure that the intersection algorithm for the assertion used is configured.
Level: 1

Type: ERROR

Impact: Data

WSM-01622: Policy merge algorithm is not defined for assertion type :

Cause: The policy merge algorithm was not found for the assertion.

Action: Ensure that the merge algorithm for the assertion used is configured.
Level: 1

Type: ERROR

Impact: Data

WSM-01623: Policy reference cannot be resolved :

Cause: The policy reference was invalid.

Action: Ensure that the policy reference is valid.
Level: 1

Type: ERROR

Impact: Data

WSM-01624: The policy does not exist in the policy store :

Cause: The policy reference was invalid, or the referenced policy could not be retrieved.

Action: Ensure that the policy reference is valid, and the policy exists in the policy store.
Level: 1

Type: ERROR

Impact: Data

WSM-01625: The Name attribute of the property is missing.

Cause: The Name attribute for a property was missing.

Action: Provide a value for the Name attribute.
Level: 1

Type: ERROR

Impact: Data

WSM-01626: The Type attribute of the property is missing.

Cause: The Type attribute for a property was missing.

Action: Provide a value for the Type attribute.
Level: 1

Type: ERROR

Impact: Data

WSM-01627: The assertion contains too many bindings.

Cause: The assertion contained more than one binding.

Action: Ensure that the assertion contains a single binding.
Level: 1

Type: ERROR

Impact: Data

WSM-01628: The policy normalization algorithm is not defined for this assertion type

Cause: The policy normalization algorithm was not found for the assertion.

Action: Ensure that the normalization algorithm for the assertion used is configured.
Level: 1

Type: ERROR

Impact: Data

WSM-01629: The assertion template contains too many assertions.

Cause: The assertion template contained more than one assertion.

Action: Ensure that assertion template contains only one assertion.
Level: 1

Type: ERROR

Impact: Data

WSM-01630: Element {0} is not a known policy element.

Cause: XML parsing failed; the system encountered unsupported XML elements.

Action: Ensure that the XML follows the schema, and the XML contains only those elements that are supported.
Level: 1

Type: ERROR

Impact: Data

WSM-01631: The assertion {0} contains multiple bindings.

Cause: The assertion contained more than one binding.

Action: Ensure that the assertion contains only one binding.
Level: 1

Type: ERROR

Impact: Data

WSM-01632: The assertion {0} contains multiple policies as child elements.

Cause: The assertion contained more than one policy child element.

Action: Ensure that the assertion contains only one policy child element.
Level: 1

Type: ERROR

Impact: Data

WSM-01633: Assertion type {0} does not match the corresponding Java Object type created.

Cause: The assertion type was incorrectly defined for the assertion.

Action: Ensure that the correct assertion type is set for the assertion.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-01635: Passed Java Object {0} does not extend the Assertion class

Cause: The Assertion class did not extend the correct classes.

Action: Consult Oracle Documentation for creating assertion implementations.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-01636: The assertion type {0} is not supported.

Cause: The assertion type does not match any of the predefined assertion types.

Action: Ensure that the assertion type is supported.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-01637: The policy attachment cannot be parsed.

Cause: The policy attachment XML was invalid.

Action: Ensure that policy attachment XML follows the policy attachment XML schema.
Level: 1

Type: ERROR

Impact: Data

WSM-01638: The policy attachment is not valid because the domain is not specified.

Cause: The policy attachment did not contain domain expressions.

Action: Ensure that policy attachment XML follows the policy attachment XML schema.
Level: 1

Type: ERROR

Impact: Data

WSM-01640: The policy reference {0} is not valid.

Cause: The policy reference could not be resolved.

Action: Ensure that the referenced policy exists in the policy store.
Level: 1

Type: ERROR

Impact: Data

WSM-01641: The policy advertisement level is not specified for the policy.

Cause: The policy advertisement level was not specified.

Action: Ensure that a valid value is set for the policy advertisement level.
Level: 1

Type: ERROR

Impact: Configuration

WSM-01642: Policy advertisement is not supported for unsupported WSDL elements.

Cause: Policy advertisement was not supported for the WSDL object.

Action: Consult Oracle documentation for supported WSDL objects.
Level: 1

Type: ERROR

Impact: Data

WSM-01643: What the XML system expects is different from what is encountered.

Cause: Usage of system was invalid or the feature was unsupported.

Action: Consult Documentation on usage and supported features.
Level: 1

Type: ERROR

Impact: Data

WSM-01644: The WSDL object {0} is not supported.

Cause: The WSDL object was not supported.

Action: Consult Oracle documentation for the supported WSDL objects.
Level: 1

Type: ERROR

Impact: Data

WSM-01645: The resource pattern {0} does not match the corresponding WSDL object.

Cause: WSDL Objects did not match.

Action: Ensure that the WSDL Objects match.
Level: 1

Type: ERROR

Impact: Data

WSM-01646: The value for the attachTo attribute of the policy is not valid.

Cause: The attachTo attribute of the policy did not match any of the predefined attachTo values.

Action: Consult Oracle documentation for the valid values for the attachTo attribute.
Level: 1

Type: ERROR

Impact: Data

WSM-01647: There are no policies that match the specified category {0} and resource pattern {1}.

Cause: No policies matched the specified search criteria.

Action: Ensure that the policies that match the search categories exist in the policy store.
Level: 1

Type: ERROR

Impact: Data

WSM-01650: cannot construct policy object

Cause: Construction of the policy Java object failed.

Action: Consult the diagnostic log for details.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-01651: cannot advertise requested policies

Cause: Advertisement of the policies failed.

Action: Consult the diagnostic log for details, or contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Programmatic

WSM-01652: error in parsing the time stamp in the policy set document

Cause: The Timestamp attribute in the XML representation of a policy set document is not a valid number.

Action: Correct or remove the invalid attribute value.
Level: 1

Type: NOTIFICATION

Impact: Data

WSM-01653: The assertion contains more than one Guard element.

Cause: The assertion contained more than one guard.

Action: Ensure that the assertion contains a single guard.
Level: 1

Type: ERROR

Impact: Data

WSM-01654: failure in serialization of security scenario assertion

Cause: The SecurityScenario in OraPolicy could not be serialized or was incorrectly configured.

Action: Ensure that the OraPolicy is correct. Consult Oracle documentation for more information.
Level: 1

Type: ERROR

Impact: Data

WSM-01655: There are no policies that match the specified category {0}.

Cause: No policies matched the specified category.

Action: Ensure that the policies that match the search category exist in the policy store.
Level: 1

Type: ERROR

Impact: Data

WSM-01656: generic Oracle WSM Policy Manager error

Cause: An internal error occurred during the Policy related operation.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

WSM-01657: Oracle WSM Advertisement Engine must be initialized with valid properties. Following properties [{0}] are either empty or null

Cause: WSM Advertisement Engine initialized with invalid parameters.

Action: Ensure that valid parameters are set during WSM Advertisement Engine configuration
Level: 1

Type: ERROR

Impact: Configuration

WSM-01658: X509 Certificate will not be advertised as {0} not found

Cause: Implementation class for advertising X509 Certificate in WSDL is not available

Action: Ensure that implementation class required for advertising X509 Certificate in WSDL is not available. Consult diagnostic log for details or contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

WSM-01659: A JAXBContext cannot be created due to underlying exception "{0}".

Cause: One or more expected classes could not be located.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

WSM-01660: A JAXB unmarshaller cannot be created due to underlying exception "{0}".

Cause: An error occurred while creating an unmarshaller.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

WSM-01661: A string cannot be unmarshalled into an object due to underlying exception "{0}".

Cause: The string is not suitable for unmarshalling to the requested type.

Action: Provide a string that is suitable for unmarshalling to the requested type.
Level: 1

Type: ERROR

Impact: Data

WSM-01662: The QName "{0}" does not match the expected QName "{1}" for the unmarshalled object.

Cause: The string is not suitable for unmarshalling to the requested type.

Action: Provide a string that is suitable for unmarshalling to the requested type.
Level: 1

Type: ERROR

Impact: Data

WSM-01663: A null or empty string cannot be unmarshalled into an Intent object.

Cause: An attempt was made to unmarshall an Intent from a null or empty String.

Action: Provide a String that contains a marshalled Intent.
Level: 1

Type: ERROR

Impact: Data

WSM-01664: A null or empty string cannot be unmarshalled into a PolicySet object.

Cause: An attempt was made to unmarshall a PolicySet from a null or empty String.

Action: Provide a String that contains a marshalled PolicySet.
Level: 1

Type: ERROR

Impact: Data

WSM-01665: A JAXB marshaller cannot be created due to underlying exception "{0}".

Cause: An error occurred while creating a marshaller.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

WSM-01666: An object cannot be marshalled to a string due to underlying exception "{0}".

Cause: Marshalling the supplied type of the object is not supported.

Action: Provide an object of a supported type.
Level: 1

Type: ERROR

Impact: Data

WSM-01667: An object cannot be marshalled to a DOM object due to underlying exception "{0}".

Cause: Marshalling the supplied type of the object is not supported.

Action: Provide an object of a supported type.
Level: 1

Type: ERROR

Impact: Data

WSM-01668: A null Intent object cannot be marshalled.

Cause: An attempt was made to marshall a null Intent object.

Action: Provide a non-null Intent object.
Level: 1

Type: ERROR

Impact: Data

WSM-01669: A null PolicySet object cannot be marshalled.

Cause: An attempt was made to marshall a null PolicySet object.

Action: Provide a non-null PolicySet object.
Level: 1

Type: ERROR

Impact: Data

WSM-01670: An object cannot be marshalled into a null DOM object.

Cause: An attempt was made to marshall an object into a null Document object.

Action: Provide a non-null Document object.
Level: 1

Type: ERROR

Impact: Data

WSM-01671: The DOM element cannot be null for policy subject identified by the resource pattern: "{0}".

Cause: The null DOM element was passed.

Action: Pass a valid non-null DOM element.
Level: 1

Type: ERROR

Impact: Compliance

WSM-01672: The policy reference URI: "{1}" for policy subject identified by the resource pattern: "{0}" cannot be empty.

Cause: Empty policy references were found in the DOM element node.

Action: Verify the DOM element node and make sure the policy references specify a valid value and the referenced policies exist in the repository.
Level: 1

Type: ERROR

Impact: Compliance

WSM-01673: Duplicate policy references: "{1}" are found for policy subject identified by resource pattern "{0}".

Cause: Duplicate policy references were found in the same DOM element node.

Action: Remove the duplicate policy references from the DOM element node.
Level: 1

Type: ERROR

Impact: Compliance

WSM-01674: The DOM element: "{1}" for policy subject identified by resource pattern "{0}" is unsupported element.

Cause: Policies cannot be retrieved for unsupported DOM element node.

Action: Verify that a supported DOM element node is provided for retrieving the policy.
Level: 1

Type: WARNING

Impact: Compliance

WSM-01675: The policy references cannot be null.

Cause: A null policy reference was passed.

Action: Pass the valid non-null policy reference object.
Level: 1

Type: ERROR

Impact: Compliance

WSM-01676: The resource pattern cannot be null.

Cause: A null resource pattern was passed.

Action: Pass a valid non-null resource pattern.
Level: 1

Type: ERROR

Impact: Compliance

WSM-01677: The domain expression cannot be null.

Cause: A null domain expression was passed.

Action: Pass a valid non-null domain expression.
Level: 1

Type: ERROR

Impact: Compliance

WSM-01678: Element {0} is not a valid child element for Policy object.

Cause: Invalid child element found for Policy object.

Action: Check the policy string being parsed and make sure only valid child elements are present for the Policy.
Level: 1

Type: ERROR

Impact: Data

WSM-01679: A DOM node cannot be unmarshalled into an object due to underlying exception "{0}".

Cause: The string is not suitable for unmarshalling to the requested type.

Action: Provide a string that is suitable for unmarshalling to the requested type.
Level: 1

Type: ERROR

Impact: Data

WSM-01680: A null node cannot be unmarshalled into a RepositoryInfo object.

Cause: An attempt was made to unmarshall a RepositoryInfo from a null node.

Action: Provide a node that contains a marshalled RepositoryInfo.
Level: 1

Type: ERROR

Impact: Data

WSM-01681: A null or empty string cannot be unmarshalled into a RepositoryInfo object.

Cause: An attempt was made to unmarshall a RepositoryInfo from a null or empty String.

Action: Provide a String that contains a marshalled RepositoryInfo.
Level: 1

Type: ERROR

Impact: Data

WSM-01682: A null RepositoryInfo object cannot be marshalled.

Cause: An attempt was made to marshall a null RepositoryInfo object.

Action: Provide a non-null RepositoryInfo object.
Level: 1

Type: ERROR

Impact: Data

WSM-01683: The passed String "{0}" could not be parsed using UTF encoding.

Cause: Underlying JVM does not support UTF-8 encoding.

Action: Check the JVM configuration to make sure it supports UTF-8 encoding format.
Level: 1

Type: ERROR

Impact: Data

WSM-01684: A null or empty string cannot be unmarshalled into a Policy object.

Cause: An attempt was made to unmarshall a Policy from a null or empty String.

Action: Provide a String that contains a marshalled Policy.
Level: 1

Type: ERROR

Impact: Data

WSM-01685: Issuer Uri is not available. Either sts_trust_config_service_policy is not attached to service or the Issuer Uri is missing from the policy. Ignore this warning if sts_trust_config_client_policy is attached to client.

Cause: Issuer Uri is not available. Either sts_trust_config_service_policy is not attached to service or the Issuer Uri is missing from the policy. Ignore this warning if sts_trust_config_client_policy is attached to client.

Action: Attach sts_trust_config_service_policy if not attached yet, or specify issuer uri value in the policy if not specified. Ignore if using sts_trust_config_client_policy.
Level: 1

Type: NOTIFICATION

Impact: Configuration

WSM-01686: Advertisement failed due to an unexpected assertion type: {0}.

Cause: The assertion type is not recognized.

Action: Internal error. Provide
Level: 1

Type: ERROR

Impact: Configuration

WSM-01687: The constant property "{0}" cannot be overriden.

Cause: There is an attempt to override a property value which is defined as a constant in the policy.

Action: Ensure that there is no attempt to override a constant property.
Level: 1

Type: WARNING

Impact: Configuration

WSM-01688: X509 Certificate will not be advertised due to underlying exception "{0}".

Cause: Either the keystore was not available or the keystore configuration was incorrect.

Action: Ensure the keystore exists and that the keystore password and aliases are correct.
Level: 1

Type: WARNING

Impact: Configuration

WSM-01689: Advertisement failed due to an incorrect ws-policy/ws-securitypolicy specification version {0}/{1}.

Cause: Invalid ws-policy/ws-securitypolicy specification version used to advertise policy.

Action: Ensure the ws-policy/ws-securitypolicy specification versions are correct.
Level: 1

Type: WARNING

Impact: Configuration

WSM-01690: Assertion {0} located by QName {1} is not an instanceof type {2}.

Cause: An internal error, probably policy was not deserialized into the correct assertion instance.

Action: Consult diagnostic log for details or contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-01691: Cannot construct or access policy object for policy "{0}" due to underlying exception "{1}".

Cause: Construction of the policy Java object failed for the given policy name.

Action: Consult the diagnostic log for details.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-01692: Advertisement failed due to multiple ws-policy specification version specified.

Cause: Multiple ws-policy specification version used to advertise policy.

Action: Remove the duplicate ws-policy specification versions and try again.
Level: 1

Type: WARNING

Impact: Configuration

WSM-01693: Advertisement failed due to multiple wssecurity-policy specification version specified.

Cause: Multiple ws-securitypolicy specification version used to advertise policy.

Action: Remove the duplicate ws-securitypolicy specification versions and try again.
Level: 1

Type: WARNING

Impact: Configuration

WSM-01694: Policy compatibility check failed due to invalid policy set. {0}.

Cause: Policy compatibility check failed due to invalid policy set.

Action: Ensure that the policy set attached to the client is a valid policy set. Consult diagnostic log for details or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WSM-01695: Encountered internal error while attempting to reorder PolicyReferences "{0}" in a PolicySet "{1}".

Cause: Encountered unexpected Policy model exception during reordering PolicyReferences in a PolicySet

Action: Consult diagnostic log for details or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WSM-01696: While validating the input PolicySet array to be merged, the PolicySet in the array have no common ResourcePattern, basePattern={0}, invalid input PolicySet array= {1}

Cause: While validating the input PolicySet array to be merged, the PolicySet in the array have no common ResourcePattern

Action: Make sure ResourcePattern of all PolicySet in the array either all null, or for non-null ones they must all have the same ResourcePattern.
Level: 1

Type: ERROR

Impact: Other

WSM-01697: While validating the input PolicySet array to be merged, there are multple PolicySet that have ResourcePattern that are not the same as that of the base, only single PolicySet in the input is allowed, basePattern={0}, invalid input PolicySet array= {1}

Cause: While validating the input PolicySet array to be merged, there are multple PolicySet that have ResourcePattern that are not the same as that of the base PolicySet

Action: Make sure that the input PolicySet array has a single PolicySet if its ResourcePattern is different that that of the base PolicySet
Level: 1

Type: ERROR

Impact: Other

WSM-01698: Runtime PolicySet is locked and it can not be modified with operation "{0}" and argument "{1}".

Cause: Runtime PolicySet is locked and read only; it cannot be modified

Action: Donot modify PolicySet
Level: 1

Type: ERROR

Impact: Other

WSM-01699: Runtime PolicySet "{0}" operation got an invalid argument "{1}" with value "{2}".

Cause: Runtime PolicySet add method passed in a null or invalid argment(s).

Action: Check the arguments and correct them.
Level: 1

Type: ERROR

Impact: Other

WSM-01700: The current Runtime PolicySet "{0}" merge method got an invalid PolicySet "{1}" in the List of PolicySet passed in; it is not an instance of PolicySet, very likely it is a CallbackPolicySet

Cause: Runtime PolicySet merge method passed invalid argument.

Action: Check the arguments and correct them.
Level: 1

Type: ERROR

Impact: Other

WSM-01751: The name of an assertion property is empty.

Cause: The name of an assertion property was empty.

Action: Make sure that you specify a name for all assertion properties.
Level: 1

Type: ERROR

Impact: Data

WSM-01752: The data type of the value does not match the data type of property {0}. The expected data type is String.

Cause: The datatype of the property value entered was not of type String.

Action: Make sure that the data type for the property value is of type String.
Level: 1

Type: ERROR

Impact: Data

WSM-01753: The data type of the value does not match the data type of property {0}. The expected data type is Boolean.

Cause: The data type of the property value entered was not of type Boolean.

Action: Make sure that the data type for the property value is of type Boolean.
Level: 1

Type: ERROR

Impact: Data

WSM-01754: The data type of the value does not match the data type of property {0}. The expected data type is Integer.

Cause: The data type of the property value entered was not of type Integer.

Action: Make sure that the data type for the property value is of type Integer.
Level: 1

Type: ERROR

Impact: Data

WSM-01755: An empty value is specified for property {0}.

Cause: An empty value was specified for a property that has a data type of type Password.

Action: Specify a value for all properties that have a data type of type Password.
Level: 1

Type: ERROR

Impact: Data

WSM-01756: The Property Set name field of context: {0} is empty

Cause: The Property Set Name field in one of the assertions was empty.

Action: Make sure that you specify a name for all assertion property sets.
Level: 1

Type: ERROR

Impact: Data

WSM-01757: The name attribute for the "Config" element is empty.

Cause: The name for the Config element was empty.

Action: Make sure that a name is specified for the Config element.
Level: 1

Type: ERROR

Impact: Data

WSM-01758: The assertion name is empty.

Cause: The assertion name was empty.

Action: Make sure that the assertion name is specified.
Level: 1

Type: ERROR

Impact: Data

WSM-01759: The policy ID is empty.

Cause: The policy ID was empty.

Action: Make sure that the policy ID is specified.
Level: 1

Type: ERROR

Impact: Data

WSM-01760: The policy name is empty.

Cause: The policy name was empty.

Action: Make sure that the policy name is specified.
Level: 1

Type: ERROR

Impact: Data

WSM-01761: Specifying a policy ID for a child policy is not permitted : {0}.

Cause: Policy ID must not be specified for child policies.

Action: Remove the policy ID of the child policy.
Level: 1

Type: NOTIFICATION

Impact: Data

WSM-01762: Specifying a policy name for a child policy is not permitted : {0}.

Cause: Policy name must not be specified for child policies.

Action: Remove the policy name of the child policy.
Level: 1

Type: NOTIFICATION

Impact: Data

WSM-01763: The value specified for the policy attachTo attribute {0}, does not match any of the supported values.

Cause: The value specified for the policy attachTo attribute did not match any of the supported values.

Action: Specify a valid value for the attachTo attribute. Consult the Oracle documentation for the supported values.
Level: 1

Type: ERROR

Impact: Data

WSM-01764: The value specified for the policy category {0} does not match any of the supported values.

Cause: The value specified for policy category attribute did not match any of the supported values.

Action: Specify a valid value for the category attribute. Consult the Oracle documentation for the supported values.
Level: 1

Type: ERROR

Impact: Data

WSM-01765: The data type of the value specified for property {0} is not supported.

Cause: The data type specified for the property did not match any of the supported data types.

Action: Specify a valid data type for the property. Consult the Oracle documentation for the supported data types.
Level: 1

Type: ERROR

Impact: Data

WSM-01766: The assertion template ID cannot be empty.

Cause: The assertion template ID was empty.

Action: Specify a value for assertion template ID.
Level: 1

Type: ERROR

Impact: Data

WSM-01767: The assertion template name cannot be empty.

Cause: The assertion template name was empty.

Action: Specify a value for the assertion template name.
Level: 1

Type: ERROR

Impact: Data

WSM-01768: The value specified for the assertion template attachTo attribute {0} does not match any of the supported values.

Cause: The value specified for the assertion template attachTo attribute did not match any of the supported values.

Action: Specify a valid value for the attachTo attribute. Consult the Oracle documentation for the supported values.
Level: 1

Type: ERROR

Impact: Data

WSM-01769: The value specified for the assertion template category {0} does not match any of the supported values.

Cause: The value specified for the assertion template category attribute did not match any of the supported values.

Action: Specify a valid value for the category attribute. Consult the Oracle documentation for the supported values.
Level: 1

Type: ERROR

Impact: Data

WSM-01770: A value or default value is not specified for property {0}.

Cause: No value or default value was specified for the property.

Action: Specify a value or a default value for the property.
Level: 1

Type: ERROR

Impact: Data

WSM-01771: Attaching multiple reliable messaging policies is not supported. Only one reliable messaging policy can be attached to a policy subject

Cause: More than one reliable messaging policy was attached to a policy subject.

Action: Make sure that only one reliable messaging policy is attached to a policy subject.
Level: 1

Type: ERROR

Impact: Data

WSM-01772: Attaching multiple Message Transmission Optimization Mechanism (MTOM) policies is not supported. Only one MTOM policy can be attached to a policy subject.

Cause: More than one MTOM policy was attached to a policy subject.

Action: Make sure that only one reliable MTOM is attached to a policy subject.
Level: 1

Type: ERROR

Impact: Data

WSM-01773: Attaching multiple WS-Addressing policies is not supported. Only one WS-Addressing policy can be attached to a policy subject.

Cause: The user attached more than one WS-Addressing policy.

Action: Make sure that only one reliable WS-Addressing is attached to a policy subject.
Level: 1

Type: ERROR

Impact: Data

WSM-01774: The policy "{0}" cannot be attached to policy subject "{1}" having unsupported subject type "{2}".

Cause: A policy was attached to an unsupported policy subject.

Action: Make sure that the policy subject supports policy attachment. Consult the Oracle documentation for the supported values.
Level: 1

Type: ERROR

Impact: Data

WSM-01775: The policy "{0}" cannot be attached to ResourcePattern "{1}" SubjectType "{2}" of attachTo "{3}" since it may only be used with "{4}".

Cause: An incompatible policy was attached to the policy subject.

Action: Make sure that the attached policy is compatible with the policy subject.
Level: 1

Type: ERROR

Impact: Data

WSM-01776: The policy reference "{0}" is invalid.

Cause: The policy reference was invalid because the policy did not exist.

Action: Make sure that the referenced policy exists in the policy store.
Level: 1

Type: ERROR

Impact: Data

WSM-01777: Attaching multiple authorization security policies is not supported. Only one authorization security policy can be attached to a policy subject.

Cause: More than one authorization security policy was attached to a policy subject.

Action: Make sure that only one authorization security policy is attached to a policy subject.
Level: 1

Type: ERROR

Impact: Data

WSM-01778: Attaching multiple authentication security policies is not supported. Only one authentication security policy can be attached to a policy subject.

Cause: More than one authentication security policy was attached to a policy subject.

Action: Make sure that only one authentication security policy is attached to a policy subject.
Level: 1

Type: ERROR

Impact: Data

WSM-01779: Attaching multiple message protection security policies is not supported. Only one message protection security policy can be attached to a policy subject.

Cause: More than one message protection security policy was attached to a policy subject.

Action: Make sure that only one message protection security policy is attached to a policy subject.
Level: 1

Type: ERROR

Impact: Data

WSM-01780: The policy reference category and the policy category do not match.

Cause: There was a mismatch between the policy reference category and the policy category.

Action: Ensure that the policy reference category matches the policy category.
Level: 1

Type: ERROR

Impact: Data

WSM-01781: Validation failure due to generic error.

Cause: A generic internal error occurred.

Action: Consult the diagnostic logs for details.
Level: 1

Type: ERROR

Impact: Data

WSM-01782: Policy contains no assertions. A policy must contain at least one assertion.

Cause: The policy did not contain any assertions.

Action: Make sure that the policy contains at least one assertion.
Level: 1

Type: ERROR

Impact: Data

WSM-01783: Guard does not contain any of the three elements of resource-match, action-match and constraint-match.

Cause: Guard does not contain any of the three elments of resource-match, action-match and constraint-match.

Action: Make sure that at least one of three elements of resource-match, action-match and constraint-match is specified with its corresponding value in the Guard element.
Level: 1

Type: ERROR

Impact: Data

WSM-01784: Validation not supported for Custom Documents. Only a Policy or PolicySet can be validated.

Cause: Validation is not supported for Custom Documents.

Action: Ensure that the document is either a Policy or a PolicySet.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-01785: Signing or encryption of the soap fault is not supported.

Cause: The soap fault is to be signed or encrypted.

Action: Make sure that the soap fault is not to be signed or encrypted.
Level: 1

Type: ERROR

Impact: Data

WSM-01786: Attaching multiple STS-Config policies is not supported. Only one STS-Config policy can be attached to a policy subject.

Cause: More than one sts-config policy was attached to a policy subject.

Action: Make sure that only one sts-config policy is attached to a policy subject.
Level: 1

Type: ERROR

Impact: Data

WSM-01791: Combination of a sts-config policy and a non sts authentication/message protection policy is not valid.

Cause: sts-config policy and non sts policy was attached to a policy subject.

Action: Make sure that a sts-config policy and a non sts config policy are not attached together to a policy subject.
Level: 1

Type: ERROR

Impact: Data

WSM-01792: Attachment of a sts-config policy without any sts policy is invalid. Attach a valid sts policy together with a sts-config policy.

Cause: Sts policy was attached without sts-config policy to a policy subject.

Action: Make sure that a sts config policy is attached together with a sts policy to a policy subject.
Level: 1

Type: ERROR

Impact: Data

WSM-01801: The type of resources expression is empty or missing.

Cause: The value specified for the appliesTo attribute was empty.

Action: Specify a valid non-empty value for the appliesTo attribute.
Level: 1

Type: ERROR

Impact: Data

WSM-01802: The type of resources expression "{0}" is not supported.

Cause: The value specified for the appliesTo attribute was invalid.

Action: Specify a valid value for the appliesTo attribute.
Level: 1

Type: ERROR

Impact: Data

WSM-01811: The attachment expression is empty or missing. A non-empty expression with a function is expected.

Cause: The value specified for the attachTo attribute was empty.

Action: Specify a valid, non-empty value for the attachTo attribute.
Level: 1

Type: ERROR

Impact: Data

WSM-01812: The function "{2}" at index {1} in attachment expression "{0}" is empty. A function requires a non-empty value.

Cause: The argument for a function was missing or empty.

Action: Specify a valid, non-empty value for the function argument.
Level: 1

Type: ERROR

Impact: Data

WSM-01813: The function "{2}" at index {1} in attachment expression "{0}" duplicates a previous function. A function may only appear once in an expression.

Cause: A function appeared more than once in an attachment expression.

Action: Remove the duplicated function from the expression.
Level: 1

Type: ERROR

Impact: Data

WSM-01814: The function "{2}" is not expected at index {1} in attachment expression "{0}". An operator is expected at this point.

Cause: A function was found in an attachment expression where an operator was expected.

Action: Specify the "and" operator between each function.
Level: 1

Type: ERROR

Impact: Data

WSM-01815: A function is expected at index {1} in attachment expression "{0}".

Cause: The attachment expression ended with an operator.

Action: Remove the dangling operator or add the missing function.
Level: 1

Type: ERROR

Impact: Data

WSM-01816: The operator "{2}" at index {1} in attachment expression "{0}" is not supported. "and" is the only supported operator.

Cause: An unrecognized operator was found in an attachment expression.

Action: Specify the "and" operator between each function.
Level: 1

Type: ERROR

Impact: Data

WSM-01817: The text "{2}" at index {1} in attachment expression "{0}" is not expected. A function is expected at this point.

Cause: An unrecognized block of text was found in an attachment expression where a function was expected.

Action: Specify a valid function in the expression.
Level: 1

Type: ERROR

Impact: Data

WSM-01818: The text "{2}" at index {1} in attachment expression "{0}" is unrecognized. The operator "and" is expected at this point.

Cause: An unrecognized block of text was found in an attachment expression where an operator was expected.

Action: Specify the "and" operator between each function.
Level: 1

Type: ERROR

Impact: Data

WSM-01821: The function "{0}" in attachment expression "{1}" is incompatible with "{2}" type of resources.

Cause: A function was found in an attachment expression that is not usable with the type of resource.

Action: Specify a function that is compatible with the associated type of resource.
Level: 1

Type: ERROR

Impact: Data

WSM-01822: The function "{0}" in attachment expression "{1}" is not supported for attachment.

Cause: A function was found in an attachment expression that is not usable for attachment.

Action: Specify a function that is compatible with the associated type of resource.
Level: 1

Type: ERROR

Impact: Data

WSM-01823: Attaching multiple policies of category "{0}" is not supported. Policies in list [ "{1}" ] already have the category, current policy "{2}" also has that category.

Cause: More than one policy with the same category was attached to a policy subject.

Action: Make sure that only one such policy is attached to a policy subject.
Level: 1

Type: ERROR

Impact: Data

WSM-01824: Invalid category : {0} for policy : {1}. Only policies assigned to the security category are supported.

Cause: The Policy category provided was not valid.

Action: Verify that the Policy category is correct.
Level: 1

Type: ERROR

Impact: Compliance

WSM-01825: Policy: {0} contains unsupported assertions.

Cause: Policy contains unsupported assertions. Assertions of type http-security are not supported for WLS JAXWS web services.

Action: Check the assertion type.
Level: 1

Type: ERROR

Impact: Security

WSM-02000: Cannot retrieve assertion template {0}.

Cause: A failure occurred while retrieving the assertion template from the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02001: Cannot serialize XML to policy attachment.

Cause: The policy attachment XML was not well formed, or the XML did not follow the policy attachment schema.

Action: Ensure that the XML is well formed, and the XML follows the policy attachment schema.
Level: 1

Type: ERROR

Impact: Data

WSM-02002: Cannot retrieve policies.

Cause: A failure occurred while retrieving policies from the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02003: Cannot retrieve policy references for resource pattern {0}.

Cause: A failure occurred while retrieving policy references from the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02004: Cannot search policies for condition {0}.

Cause: A failure occurred while searching for policies in the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02005: Cannot perform policy compatibility check for policies {0}.

Cause: An internal error was encountered while performing the policy compatibility check.

Action: Contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02006: Cannot add policies {0} to data store.

Cause: A failure occurred while adding policies to the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02007: Cannot delete assertion templates {0}.

Cause: A failure occurred while deleting assertion templates from the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02008: Cannot delete policies {0}.

Cause: A failure occurred while deleting policies from the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02009: Cannot delete all assertion templates from the data store.

Cause: A failure occurred while deleting all assertion templates from the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02010: Unable to delete all policies from the data store.

Cause: A failure occurred while deleting all policies from the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02011: Cannot delete assertion template {0}.

Cause: A failure occurred while deleting the specified assertion template from the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02012: Cannot delete policy {0}.

Cause: A failure occurred while deleting the specified policy from the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02013: Cannot retrieve policy configuration {0}.

Cause: A failure occurred while retrieving the policy configuration.

Action: Check the policy configuration, and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02014: The value for the attachTo attribute {0} is not valid.

Cause: The value for the attachTo attribute is not valid.

Action: Consult Oracle documentation for the valid values for the attachTo attribute.
Level: 1

Type: ERROR

Impact: Data

WSM-02015: Cannot retrieve object(s) due to Java RuntimeException.

Cause: The unexpected RuntimeException was encountered while trying to access data store.

Action: Check the log file for possible causes, and retry the operation.
Level: 1

Type: WARNING

Impact: Data

WSM-02016: Cannot retrieve timestamp for the last data store update.

Cause: A problem occurred while accessing the repository.

Action: Examine the logs for the cause of the failure.
Level: 1

Type: WARNING

Impact: Data

WSM-02044: Cannot save assertion template {0} to data store.

Cause: Another process was trying to update the same assertion template.

Action: Ensure that no other process is trying to update the same assertion template object and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02045: Cannot delete policy version from data store.

Cause: Failure occurred while deleting policy versions from the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02046: Cannot delete assertion template versions from data store.

Cause: Failure occurred while deleting assertion template versions from the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02047: Unable to create multiple policies.

Cause: Failure occurred while creating multiple policies

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02048: Unable to update multiple policies.

Cause: Failure occurred while updating multiple policies.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02049: Unable to update the assertion template.

Cause: Failure occurred while updating an assertion template.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02050: Unable to set the older version of a policy as the latest version.

Cause: Failure occurred while setting an older version of a policy as the latest version.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02051: Unable to add resources to policy attachment.

Cause: Failure occurred while trying to add resources to a policy attachment.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02052: Unable to remove resources from policy attachment.

Cause: Failure occurred while trying to remove resources from policy attachment.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02053: Unable to set the older version of a policy as the latest version.

Cause: Failure occurred while setting an older version of a policy as the latest version.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02054: Failure in looking up EJB component.The EJB JNDI name is "{0}", the provider URL is "{1}"..

Cause: Failure occurred in looking up requested component on the application server.

Action: Make sure that the right configuration is passed for the EJB lookup and retry the operation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

WSM-02055: Failure calculating smart digest for policy {0}

Cause: Failure occurred in calculating smart digest when updating or creating policy.

Action: You can ignore this message or you can retry the operation. Increase the log levels for more details as to the underlying cause for the smart digest calculation failure.
Level: 1

Type: WARNING

Impact: Data

WSM-02056: Unable to locate the RMI port for communication

Cause: Failure occurred when looking up RMI port for the application server.

Action: Confirm that the RMI port settings are correct in the application server configuration and retry the operation.
Level: 1

Type: WARNING

Impact: Data

WSM-02057: Mismatch in EJB lookup. Expected object type: {0}, Actual object type: {1}.

Cause: Mismatch in expected EJB object type and actual object type.

Action: Confirm that the Policy Manager EJB is configured correctly, and its version is compatible with the client.
Level: 1

Type: WARNING

Impact: Data

WSM-02058: Failure occurred in Policy Manager while seeding policies in data store.

Cause: Failure occurred in Policy Manager while seeding policies in data store.

Action: Make sure the correct configuration is passed to Policy Manager for seeding policies.
Level: 1

Type: ERROR

Impact: Data

WSM-02059: Version-related operations are not supported for the configured datastore.

Cause: Version-related operations are not supported for the configured datastore.

Action: Make sure the datastore used is a database and not file-system based.
Level: 1

Type: ERROR

Impact: Data

WSM-02060: EJB lookup failed due to invalid lookup configuration

Cause: Unable to perform EJB lookup.

Action: Make sure that valid JNDI name and JNDI properties are supplied for EJB lookups.
Level: 1

Type: ERROR

Impact: Data

WSM-02061: Failed to close Initial Context created for EJB lookups

Cause: Unable to close the Java Initial Context.

Action: Confirm that no other component is using the context and there are no memory leaks.
Level: 1

Type: ERROR

Impact: Data

WSM-02062: Unable to retrieve credentials for the specified csf-key {0}

Cause: Credential configuration in the policy accessor configuration file was incorrect.

Action: Configure policy with valid CSF key.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02063: The password credentials cannot be obtained from the Credential Store.

Cause: Failure occurred while querying for credentials from CSF.

Action: Check CSF configuration.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02064: The Java Object Name {0} being created is invalid.

Cause: An error occurred while creating the specifed JMX ObjectName.

Action: Check the MBean ObjectName being instantiated and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02065: The MBean being registered is not a JMX compliant MBean

Cause: Failed to register MBean.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02066: Failed to get server context

Cause: Failed to get server initial context.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02067: Cannot register MBean {0}, an MBean with same name already exists on the server

Cause: The MBean being registered already exists on the server.

Action: Check the name of the MBean being registered and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02068: Failed to register MBean {0}

Cause: Failed to register MBean.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02069: Failed to deregister MBean {0}

Cause: Failed to deregister MBean.

Action: No action needs to be taken at this time. However, if the server exhibits any erraneous behavior, try restarting the server.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02070: Failed to load updates.xml file

Cause: Failed to load updates.xml file.

Action: Make sure that the wsm-seed-policies.jar exists and it corresponds to the latest version and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02071: No entries found in the wsm-seed-policies.jar file

Cause: The wsm-seed-policies.jar file does not contain any entries.

Action: Make sure that the wsm-seed-policies.jar file is not corrupted and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02072: Failed to load wsm-seed-policies.jar file

Cause: The wsm-seed-policies.jar file could not be loaded.

Action: Make sure that the wsm-seed-policies.jar file exists in the application classpath and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02073: Unable to connect to the WSM datastore

Cause: Unable to connect to the WSM datastore.

Action: Make sure the datastore settings are correctly set in the wsm-pm application and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02074: Invalid arguments passed to find the difference in shipped documents between versions

Cause: The arguments supplied to find difference between repository versions are invalid.

Action: Make sure that the arguments passed comply with the Javadoc requirements and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02075: Cannot unregister MBean {0}. since it does not exist on the server

Cause: The MBean being unregistered does not exists on the sever.

Action: Check the name of the MBean being unregistered and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02076: Unable to get an instance of PortableMBeanFactory.

Cause: Could not obtain an instance of PortableMBeanFactory.

Action: Check the configuration and try again.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02077: Unable to get a handle to MBeanServer.

Cause: Could not obtain an instance to MBeanServer

Action: Check the configuration and try again.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02078: Unable to construct MBean ObjectName due to null object name string.

Cause: MBean object name is invalid.

Action: Make sure that the supplied object name is not null and retry the lookup.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02079: Failed to connect to Policy Manager instance due to error "{0}".

Cause: Connection to Policy Manager failed.

Action: Make sure that the WSM Policy Manager is up and running and retry the operation.
Level: 1

Type: TRACE

Impact: Data

WSM-02080: Failure to get executor due to underlying error "{0}".

Cause: Failed to get the correct executor to perform requested action.

Action: Check the system security configuration and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02081: Failed to login to perform requested action.

Cause: Failed to login to perform requested action.

Action: Check the system security configuration and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-02082: Unsupported callback handler.

Cause: Unsupported callback handler.

Action: Check the system security configuration and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-02083: Invalid security configuration entry name.

Cause: Invalid security configuration entry name.

Action: Check the system security configuration and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-02084: Access denied. Permission "{0}" is required to access the wsm policy manager "{1}" method "{2}".

Cause: Permission required to access the policy manager API.

Action: Ensure that the user accessing policy manager api has required permission.
Level: 1

Type: ERROR

Impact: Security

WSM-02100: Error parsing the resource from String {0}.

Cause: An XML parsing failure occurred while creating the document from the passed String.

Action: Verify that the passed String is a well-formed XML and follows the XML schema for its object type.
Level: 1

Type: ERROR

Impact: Data

WSM-02101: Generic Oracle WSM Policy Manager error.

Cause: An internal error occurred during the Policy Manager operation.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02102: The policy name is missing.

Cause: The policy name was missing.

Action: Make sure that the supplied policy has a valid name, and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-02103: The assertion template name is missing.

Cause: The assertion template name was missing.

Action: Make sure that the supplied assertion template has a valid name, and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-02104: The assertion template from file {0} cannot be parsed.

Cause: A failure occurred while parsing the assertion template from the file.

Action: Check for any syntax errors in the file specified, and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02105: The policy search query is not valid.

Cause: An invalid policy search condition was specified.

Action: Check the search query and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-02106: Cannot retrieve policy {0}.

Cause: A failure occurred while retrieving the policy.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02107: Cannot update policy {0}.

Cause: A failure occurred while updating the policy.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02108: Cannot retrieve version {0} of policy {1}.

Cause: A failure occurred while retrieving the requested version of the policy.

Action: Check the version and policy details and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02109: Cannot retrieve version {0} of assertion template {1}.

Cause: A failure occurred while retrieving the requested version of the specified assertion template.

Action: Check the version and assertion template details, and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02111: The configuration name is missing.

Cause: The policy configuration name was missing.

Action: Provide a valid name for the policy configuration, and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-02112: The policy attachment name is missing.

Cause: The policy attachment name was missing.

Action: Provide a valid policy attachment name, and retry the operation
Level: 1

Type: ERROR

Impact: Programmatic

WSM-02113: Error in creating the policy attachment {0}.

Cause: A failure occurred while creating the policy attachment.

Action: Check the specified values and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02114: Error in deleting the policy attachment {0}.

Cause: A failure occurred while deleting the policy attachment.

Action: Check the specified values and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02115: Error in updating the policy attachment {0}.

Cause: A failure occurred while updating the policy attachment.

Action: Check the specified values and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02116: The resource pattern used in the search is empty or contains wildcard characters like %.

Cause: The resource pattern specified in the search was empty or contained wildcard characters such as %.

Action: Correct the search criteria and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02117: Cannot delete all policy attachments from the data store.

Cause: A failure occurred when deleting multiple policy attachments from the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02118: The query service cannot be created.

Cause: A failure occurred while creating the query service.

Action: Check the Policy Manager configuration and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02119: The update service cannot be created.

Cause: A failure occurred while creating the update service.

Action: Check the Policy Manager configuration and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02120: Unable to connect to the policy access service.

Cause: A connection to the policy access service could not be created.

Action: Check the Policy Manager configuration and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02121: Internal system error, cannot look up credential.

Cause: A failure occurred while looking up credentials due to an internal system configuration error.

Action: Contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-02122: The protocol is invalid.

Cause: The protocol was invalid.

Action: Check Oracle documentation for the supported protocols.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02123: Cannot access policy-accessor-config.xml file.

Cause: A failure occurred while reading the policy-accessor-config.xml file.

Action: Ensure that the file exists.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02124: Cannot create policy access service.

Cause: The user connecting to the policy access service did not have sufficient privileges.

Action: Confirm that the user has rights to connect to the policy access service, and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02125: Cannot perform policy compatibility check.

Cause: A failure occurred while performing a policy compatibility check.

Action: Contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-02126: Cannot add policy {0} to data store.

Cause: A failure occurred while adding the policy to the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02127: Cannot add assertion template {0} to data store.

Cause: A failure occurred while adding the assertion template to the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02128: Cannot read WSDL.

Cause: A failure occurred while parsing the WSDL.

Action: Confirm that the supplied WSDL follows the WSDL XML schema.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-02129: Cannot create policy service.

Cause: The user connecting to the policy service did not have sufficient privileges.

Action: Confirm that the user has privileges to connect to the policy service, and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02130: Cannot retrieve policy attachment from data store.

Cause: A failure occurred while retrieving the policy attachment from the data store.

Action: Retry the operation.
Level: 1

Type: WARNING

Impact: Data

WSM-02131: Standard WSDL is provided, but ORAWSDL is required.

Cause: The WSDL did not have the expected Oracle extensions.

Action: Retry the operation with WSDL with Oracle Extensions.
Level: 1

Type: WARNING

Impact: Data

WSM-02132: Cannot find service {0} in WSDL.

Cause: The service was not found in the WSDL.

Action: Retry the operation with the correct parameters.
Level: 1

Type: WARNING

Impact: Data

WSM-02133: Cannot find policies in WSDL.

Cause: No policies were found in the WSDL.

Action: Confirm that the supplied WSDL contains the correct policies.
Level: 1

Type: WARNING

Impact: Data

WSM-02134: Cannot access Policy Manager EJB.

Cause: The user connecting to the Policy Manager EJB did not have sufficient privileges.

Action: Confirm that the user has privileges to connect to the Policy Manager EJB, and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02135: Insufficient privileges for accessing the Policy Manager interface.

Cause: Caller's privileges for accessing the Policy Manager EJB were insufficient.

Action: Examine underlying errors for root cause.
Level: 1

Type: ERROR

Impact: Data

WSM-02136: Bulk update operations are not supported for file-based data stores.

Cause: The bulk update operation failed because the data store does not support transactions.

Action: Use a repository that supports transactions, for example, a database repository.
Level: 1

Type: ERROR

Impact: Data

WSM-02138: Cannot save policy attachment {0} to data store.

Cause: A concurrent update failure occurred while saving the policy attachment in the data store.

Action: Make sure no other process is trying to update the same policy attachment object and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02139: Cannot save policy {0} to data store.

Cause: A concurrent update failure occurred while saving the policy in the data store.

Action: Make sure no other process is trying to update the same policy object and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02201: A comparator is required for a search criterion.

Cause: A search comparator was not provided.

Action: Supply a comparator.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02202: The comparator "{0}" is not supported for a numeric attribute search criterion.

Cause: The search comparator is not supported for numeric comparisons.

Action: Supply a comparator that supports numeric comparisons.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02203: The comparator "{0}" is not supported for a text attribute search criterion.

Cause: The search comparator is not supported for numeric comparisons.

Action: Supply a comparator that supports numeric comparisons.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02204: The comparator "UNKNOWN" is not supported for an attribute search criterion.

Cause: The search comparator UNKNOWN is not supported for attribute comparisons.

Action: Supply a comparator that supports attribute comparisons.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02205: The search criterion "{0}" cannot be parsed.

Cause: The search criterion was corrupt or used an unrecognized schema.

Action: Supply a supported search criterion.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02206: The document name "{0}" is not valid for a search criterion.

Cause: The document name contained illegal characters, such as a slash character.

Action: Supply a legal document name.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02207: A document type is required for a search criterion.

Cause: The document type was null, whitespace, or empty.

Action: Supply a non-empty document type.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02208: A document URI ends with a path separator.

Cause: The document URI ends with a path separator.

Action: Supply a document URI that does not appear to be a path.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02209: A document URI is required for a search criterion.

Cause: The document URI was empty.

Action: Supply a non-empty document URI.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02210: An element search criterion cannot be created with the child search expression "{0}" because it contains a non-attribute criterion.

Cause: The search expression contained one or more attribute criteria.

Action: Supply an expression containing only attribute criteria.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02211: A number is required for a search criterion.

Cause: A number was not provided.

Action: Supply a valid number.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02212: The search expression "{0}" contains invalid operator "{1}".

Cause: The search expression contained an invalid operator.

Action: Supply an expression with a valid operator.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02213: A search operator is required for a search expression.

Cause: A search operator was not provided.

Action: Supply a valid operator.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02214: The operator "UNKNOWN" is not supported for a search expression.

Cause: The search operator UNKNOWN is not supported for expressions.

Action: Supply a valid operator.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02215: A QName is required for a search criterion.

Cause: A search QName was not provided.

Action: Supply a valid Name.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02216: The search expression "{0}" contains a close parenthesis at index {1} without a matching open parenthesis.

Cause: The search expression contained an unbalanced parenthesis.

Action: Supply an expression with matching open and close parenthesis.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02217: The search expression "{0}" contains an open parenthesis without a matching close parenthesis.

Cause: The search expression contained an unclosed parenthesis.

Action: Supply an expression with matching open and close parenthesis.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02218: The comparator "{0}" is not supported for text content search criterion.

Cause: The search comparator is not supported for text comparisons.

Action: Supply a comparator that supports text comparisons.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02251: Subject metadata is required to build a PolicySet.

Cause: Subject metadata was not provided for building a PolicySet.

Action: Supply valid subject metadata.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02252: A repository accessor is required to build a PolicySet.

Cause: A repository accessor was not provided for building a PolicySet.

Action: Supply suitable repository accessor instance.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02253: The resource pattern for the subject "{0}" is invalid. External attachments and policy usage tracking is disabled.

Cause: An invalid resource pattern was provided with the metadata for a policy subject.

Action: Contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02254: The constraint value "{0}" is invalid and caused ParseException, process continues as if there is no constraint being set in the global PolicySet.

Cause: Parsing of constraint set in the global PolicySet caused ParseException

Action: Correct the value of constraint in global PolicySet and retry.
Level: 1

Type: WARNING

Impact: Data

WSM-02261: A map of terms is required when creating a ResourcePattern.

Cause: A null map of terms was provided to the ResourcePattern constructor.

Action: Supply a valid map of terms when creating a resource pattern.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-02262: A "{0}" term is required when creating a ResourcePattern.

Cause: The required term was not provided to the ResourcePattern constructor.

Action: Supply a valid map of terms when creating a resource pattern.
Level: 1

Type: ERROR

Impact: Data

WSM-02263: A map of terms is required when creating a ResourcePattern.

Cause: A null String was provided to the ResourcePattern constructor.

Action: Supply a valid resource pattern String.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-02264: "{0}" is not a recognized resource pattern.

Cause: The supplied String did not match one of the known resource pattern formats.

Action: Supply a valid resource pattern String.
Level: 1

Type: ERROR

Impact: Data

WSM-02265: The resource patterns to be combined must be provided.

Cause: The resource pattern to combine must be supplied for creating valid resource pattern.

Action: Supply valid resource patterns
Level: 1

Type: ERROR

Impact: Data

WSM-02301: Failed to get document from URL "{0}" due to underlying error "{1}"

Cause: URL resource was not loaded.

Action: Check that the passed URL is valid and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02302: Failed to access document repository due to underlying error "{0}"

Cause: The Document Repository could not be accessed.

Action: Check the configuration for accessing Document Repository and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Requests/Responses

WSM-02303: The passed search expression "{0}" could not be parsed due to underlying error "{1}"

Cause: Failure in parsing the passed search expression.

Action: Check that the passed search expression is valid and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02304: The passed expressionMap "{0}" contains search expression which cannot be parsed due to underlying error "{1}".

Cause: Failure in parsing the search expression contained in the passed expressionMap.

Action: Check that the passed expressionMap contains valid search expression and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02310: Failed to retrieve requested documents due to underlying error "{0}". The operation will be retried.

Cause: Failure in retrieving the requested documents.

Action: No corrective action needed as this time, the operation will be retried.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02311: Failed to retrieve requested documents due to underlying error "{0}".

Cause: Failure in retrieving the requested documents.

Action: Check that the document repository is reachable and is correctly configured.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02312: Failed to store resource usage information to underlying error "{0}". The operation will be retried.

Cause: Failure in persisting usage information.

Action: This condition can happen in a normal situation and the operation would be retried automatically. There is no immediate concern unless the warning message displays continuously even in a low usage environment.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02313: Failed to store resource usage information to underlying error "{0}".

Cause: Failure in persisting usage information.

Action: Check that the document repository is reachable and is correctly configured.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02351: A invalid bean class "{0}" is provided.

Cause: A invalid bean class was provided to the bean factory to create a bean instance.

Action: Provide a valid bean class.
Level: 1

Type: ERROR

Impact: Data

WSM-02352: A invalid bean type "{0}" is provided.

Cause: A invalid bean type was provided to the bean factory to create a bean instance.

Action: Provide a valid bean type.
Level: 1

Type: ERROR

Impact: Data

WSM-02353: Unable to get the Action Executor.

Cause: A failure occurred while getting Action Executor.

Action: Check that valid subject is passed to get the Action Executor
Level: 1

Type: ERROR

Impact: Configuration

WSM-02354: Unexpected exception "{0}" caught when privileged method is called.

Cause: Unexpected exception caught on calling a privileged code.

Action: Check the underlying signature of method called in privileged code
Level: 1

Type: ERROR

Impact: Configuration

WSM-02355: A subject passed to BeanFactory is null.

Cause: The subject passed to the bean factory is null.

Action: Ensure that the subject is not null.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-02356: Cannot cast to "{0}" object.

Cause: Unable to cast the object. It may be using older implementation.

Action: Verify that the older implementation is not being used.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02359: Lookup attempted for unsupported Server.

Cause: A lookup is attempted for unsupported Server.

Action: Check the system configurations to ensure correct server is running.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02360: The path to the jar file "{0}" is either invalid or the jar file is corrupt.

Cause: The path provided to the jar file is either incorrect or the jar file is corrupt

Action: Provide the path to a valid jar file.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02361: A invalid Policy Manager RESTful service URI "{0}" is provided.

Cause: A invalid Policy Manager RESTful service URI was provided to the bean factory to create a bean instance.

Action: Provide a valid Policy Manager RESTful service URI.
Level: 1

Type: ERROR

Impact: Data

WSM-02362: An unsupported operation "{0}" is invoked.

Cause: An unsupported operation was invoked.

Action: Invoke a supported operation.
Level: 1

Type: WARNING

Impact: Data

WSM-02363: An invalid keystore/truststore specified as system property.

Cause: An invalid keystore/truststore specified as system property.

Action: Provide a valid keystore/truststore as system property.
Level: 1

Type: WARNING

Impact: Data

WSM-02364: An invalid cryptographic algorithm specified in keystore/truststore.

Cause: An invalid cryptographic algorithm specified in keystore/truststore.

Action: Provide a valid cryptographic algorithm in keystore/truststore.
Level: 1

Type: WARNING

Impact: Data

WSM-02365: A invalid trust or key store location "{0}" is provided.

Cause: An invalid trust/key store path was provided to the bean factory to create a bean instance.

Action: Provide a valid trust/key store path.
Level: 1

Type: ERROR

Impact: Data

WSM-02366: Keystore instance of type "{0}" is not found.

Cause: Keystore instance is not found.

Action: Add the keystore instance and try again.
Level: 1

Type: ERROR

Impact: Data

WSM-02367: An invalid cryptographic algorithm is requested.

Cause: An invalid cryptographic algorithm is requested but is not available in the environment.

Action: Provide a valid algorithm and try again.
Level: 1

Type: ERROR

Impact: Data

WSM-02368: A certificate provided in keystore "{0}" is invalid.

Cause: A certificate in the trust chain is missing.

Action: Ensure that the complete certificate chain is propagated.
Level: 1

Type: ERROR

Impact: Data

WSM-02369: Certificate location "{0}" is invalid.

Cause: A certificate location is invalid.

Action: Provide valid certificate location and try again.
Level: 1

Type: ERROR

Impact: Data

WSM-02370: Unable to read certificate from keystore "{0}".

Cause: Unable to read certificate from keystore.

Action: Ensure that alias exists in keystore and necessary permission to read key alias is granted.
Level: 1

Type: ERROR

Impact: Data

WSM-02371: Unable to recover key from keystore "{0}".

Cause: Security provider is requested is not available in the environment.

Action: Ensure to request correct security provider.
Level: 1

Type: ERROR

Impact: Data

WSM-02373: Policy manager url "{0}" is not supported in this environment.

Cause: An unsupported policy manager url was configured.

Action: Correct policy manager configuration and try again.
Level: 1

Type: WARNING

Impact: Data

WSM-02374: The policy manager repository path "{0}" does not contain any valid directories.

Cause: An invalid directory was provided when attempting to create an MDS instance for a file-based repository.

Action: Provide a valid directory and try again.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-02375: One or more directories are required to connect to a file-based policy manager.

Cause: A path was not provided when attempting to create a file-based repository.

Action: Provide a valid directory and try again.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-02376: The policy manager repository session cannot be created due to underlying error "{0}".

Cause: Policy manager encountered an unexpected condition.

Action: Follow the recommendations for the underlying exception.
Level: 1

Type: ERROR

Impact: Data

WSM-02377: Unable to access member "{0}" of class "{1}".

Cause: Unable to access field or method of a class.

Action: Ensure to field name and class name is correct.
Level: 1

Type: ERROR

Impact: Data

WSM-02378: Unable to find member "{0}" of class "{1}".

Cause: Unable to find field or method of a class.

Action: Ensure to field name and class name is correct.
Level: 1

Type: ERROR

Impact: Data

WSM-02379: Trying to access member "{0}" of class "{1}" illegally that violates its access modifiers.

Cause: Trying to access illegally field or method of a class.

Action: Ensure to field name and class name is correct.
Level: 1

Type: ERROR

Impact: Data

WSM-02380: Unable to find implementation of member "{0}" in class "{1}".

Cause: Unable to find implementation of field or method in a class.

Action: Ensure to field name and class name is correct.
Level: 1

Type: ERROR

Impact: Data

WSM-02381: Unable to invoke method "{0}" of class "{1}" with values "{2}".

Cause: Unable to invoke method of a class.

Action: Ensure to method name and class name is correct.
Level: 1

Type: ERROR

Impact: Data

WSM-02382: The path to the jar files "{0}" are either invalid or the jar files are corrupt.

Cause: The path provided to the jersey jar files are either incorrect or the jar files are corrupt

Action: Provide the path to a valid jar file.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02383: Class name cannot be null.

Cause: Class name is null or invalid.

Action: Ensure to class name is correct.
Level: 1

Type: ERROR

Impact: Data

WSM-02384: Class method name cannot be null.

Cause: Method name is null or invalid.

Action: Ensure to method name is correct.
Level: 1

Type: ERROR

Impact: Data

WSM-02385: Class field name cannot be null.

Cause: Class field name is null or invalid.

Action: Ensure to class field name is correct.
Level: 1

Type: ERROR

Impact: Data

WSM-02386: Failure constructing object for class ( "{0}" ) with the given params: "{1}".

Cause: Unable to create instance of class.

Action: Ensure to call correct constructor.
Level: 1

Type: ERROR

Impact: Data

WSM-02387: Class cannot be null.

Cause: Class is null or invalid.

Action: Ensure to class loaded correctly.
Level: 1

Type: ERROR

Impact: Data

WSM-02388: Unable to load class "{0}".

Cause: Unable to load class.

Action: Ensure to class name correct.
Level: 1

Type: ERROR

Impact: Data

WSM-02401: Failed to store policy usage information to the repository because document criterion "{1}" is not a valid document name for the repository due to underlying error "{0}".

Cause: The document criterion contains invalid document name for the repository.

Action: Choose a valid document name and try again.
Level: 1

Type: ERROR

Impact: Data

WSM-02402: Expression "{0}" does not identify specific documents.

Cause: An invalid search expression was specified.

Action: Check the search expression and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02403: Failed to store policy usage information to the repository because the expressionMap "{0}" has document criterion with invalid document name for the repository resulting in underlying error "{1}".

Cause: The search expression within the map has document criterion having invalid document name for the repository.

Action: Choose a valid document name and try again.
Level: 1

Type: ERROR

Impact: Data

WSM-02451: Document cannot be deleted from repository due to underlying error "{0}".

Cause: Failure in deleting requested document.

Action: Check that the document exists in the repository
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02452: Document criterion "{0}" is invalid for the requested operation due to underlying error "{0}".

Cause: Document criteria is invalid for the requested operation.

Action: Check that the document criterion is valid for the repository.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02453: Failed to delete the document with version "{1}" and criterion "{0}" due to underlying error "{2}".

Cause: Failure in deleting the specified version of the document.

Action: Check that the document with the specified version exists in repository.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02454: The search expression "{0}" does not identify a unique document.

Cause: The search expression do not identify unique document.

Action: Supply an expression which identifies unique document.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02455: Document version cannot be promoted to tip due to underlying error "{0}".

Cause: Failure in promoting the requested document.

Action: Check that the document exists in the repository.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02456: A retrieval flag cannot be parsed into a number due to underlying error "{0}".

Cause: Failure in parsing flags for document retrieval operation.

Action: Check that the value specified for the flags are valid.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02457: Document retrieval failed due to underlying error "{0}".

Cause: Failure in retrieving documents due to invalid document criteria.

Action: Check that the value specified for the document criteria are valid.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02458: Document "{0}" cannot be overwritten as it does not exist in the repository.

Cause: Failure in write operation using WRITE_EXISTING mode since document do not exist in repository.

Action: Define a new search criterion.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02459: Document "{0}" cannot be created as already exists in the repository.

Cause: Failure in write operation using WRITE_NEW mode since document exists in repository.

Action: Define a new search criterion.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02460: Unable to write invalid document due to underlying error "{0}".

Cause: URI for the document is invalid for the write operation.

Action: Check that the document URI is valid for the repository
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02461: A document without a naming attribute cannot be written.

Cause: Document name is not specified at time of document creation.

Action: Please specify a valid document name for the document creation.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02462: The session state is invalid due to underlying error "{0}".

Cause: Session state is invalid for the given operation.

Action: Retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02463: A document transformer cannot be created due to underlying error "{0}".

Cause: The DOM Parser was not configured properly.

Action: Consult Java documentation.
Level: 1

Type: ERROR

Impact: Other

WSM-02464: A DOM document cannot be marshalled into XML due to underlying transformation error "{0}".

Cause: Parsing of the document failed.

Action: Ensure that the document is in well-formed XML format.
Level: 1

Type: ERROR

Impact: Other

WSM-02465: A DOM document builder cannot be created due to underlying error "{0}".

Cause: The XML Parser was not configured properly.

Action: Consult Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02466: An XML document cannot be unmarshalled into DOM due to underlying parsing error "{0}".

Cause: Parsing of the XML failed.

Action: Ensure that the XML is well formed.
Level: 1

Type: ERROR

Impact: Data

WSM-02467: An XML document cannot be unmarshalled into DOM due to underlying I/O error "{0}".

Cause: The system could not open the Input/Output streams.

Action: Consult the Java documentation.
Level: 1

Type: ERROR

Impact: Files

WSM-02468: The document specified in search expresion "{0}" resulted in underlying error "{1}".

Cause: The document name specified for the repository is invalid.

Action: Please specify a valid document name.
Level: 1

Type: ERROR

Impact: Files

WSM-02469: Unable to retrieve document due to underlying error "{0}".

Cause: URI for the document is invalid for the retrieve operation.

Action: Check that the document URI is valid for the repository
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02470: Unable to write document due to invalid Write Mode "{0}".

Cause: Invalid Write Mode specified to write a document.

Action: Check that a valid Write Mode is specified to write a document.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02471: The exception "{0}" is caused because invalid document uri is being used.

Cause: URI for any document is invalid.

Action: Check that all the document URI used are valid for the repository
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02472: REST client got an unexpected error, http status:"{0}", msg:"{1}", type:"{2}".

Cause: REST client got an unexpected error.

Action: Check the REST client request and error message logged for possible cause
Level: 1

Type: ERROR

Impact: Data

WSM-02473: REST Service got an exception, http status:"{0}", msg:"{1}", type:"{2}", uriPath:"{3}" .

Cause: REST service got an expection.

Action: Check the REST request and server error message logged for possible cause
Level: 1

Type: ERROR

Impact: Data

WSM-02474: REST Client got an exception, http status:"{0}", msg:"{1}", type:"{2}", uriPath:"{3}" .

Cause: REST client got an expection.

Action: Check the REST client request and client error message logged for possible cause
Level: 1

Type: ERROR

Impact: Data

WSM-02475: Unable to marshal/unmarshall the document "{1}" due to underlying error "{0}" resulting in deletion failure.

Cause: Unable to marshal/unmarshall the document resulting in deletion failure.

Action: Check that the document exists in the repository
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02476: The document "{0}" cannot be deleted since it is being used by other documents.

Cause: Cannot delete a referenced document.

Action: Before deleting the document, delete othe documents referring the document.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02477: Unable to create object for marshalling/unmarshalling of resource documents due to underlying error "{0}".

Cause: Failed to create instance of ResourceMarshaller.

Action: Refer the logs for details.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02478: Unable to marshal/unmarshall the document due to underlying error "{0}".

Cause: Unable to marshal/unmarshall the document.

Action: Check that the document is valid
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02479: The specified document "{0}" is invalid and cannot be created as it cannot be marshaled.

Cause: The specified document is invalid as it cannot be marshaled.

Action: Please specify a valid document for the document creation.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02551: Unable to retrieve document due to underlying error "{0}".

Cause: URI for the jar is invalid for the retrieve operation.

Action: Check that the jar URI is valid.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02552: Unable to load seed policies jar file

Cause: Inability to load seed policies jar either automatically or by a provided path

Action: Check that the path to the jar file is correct
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02553: Unable to load updates.xml from the seed policy jar

Cause: There is some problem while loading updates.xml from the seed policies jar

Action: Make sure a valid seed policies jar is provided containing a valid updates.xml file
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02554: The access to the store or credentials is denied.

Cause: The credentials store access is denied.

Action: Ensure Store is properly initialized.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02555: Cannot retrieve requested documents for condition {0}.

Cause: A failure occurred retriving documents from the data store.

Action: Retry the operation.
Level: 1

Type: WARNING

Impact: Data

WSM-02556: Document(s) identified by condition {0} does not exist in the data store

Cause: A failure occured retriving document(s) from the data store.

Action: Make sure the document(s) being requested exists in the data store and retry the operation.
Level: 1

Type: WARNING

Impact: Data

WSM-03001: Oracle WSM Monitor internal error {0}

Cause: An unexpected error occurred while monitoring Oracle WSM Agent.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-03002: Failure initializing Oracle WSM Monitor, {0} is null.

Cause: Creation of one or more DMS Event sensors failed while initializing Oracle WSM Monitor.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

WSM-03003: The topology node value {0} is not valid.

Cause: The topology node value passed from the security interceptor to Oracle WSM Agent was invalid.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

WSM-03004: The parameter {0} is not valid.

Cause: The parameter was either null or invalid.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

WSM-04501: generic error in accessing the data store

Cause: An internal error occurred while accessing the MDS data store.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-04502: The name of the resource is empty.

Cause: The name of the resource to be updated or retrieved was empty.

Action: Assign a name to the resource being processed.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-04503: resource {0} does not exist in the data store

Cause: The requested resource was not found in the data store.

Action: Check the search criteria and try again.
Level: 1

Type: ERROR

Impact: Data

WSM-04504: resource {0} cannot be updated

Cause: The resource could not be updated.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

WSM-04505: resource {0} cannot be created

Cause: The specified name has already been assigned to another resource.

Action: Specify a unique name, and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-04506: cannot create resource {0}

Cause: The resource could not be saved to the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-04507: cannot delete resource {0}

Cause: The resource could not be deleted from the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-04508: cannot update resource {0}

Cause: The resource could not be updated to the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-04509: cannot initialize the connection to the data store

Cause: Connecting to the data store failed.

Action: Check the data store credentials, and retry the operation. Ensure that WSM-PM is installed, deployed correctly and running at http://<host:port>/wsm-pm/ and by clicking the Validator link. Also, ensure that the database to which WSM-PM connects is up and the mds-owsm data source is configured properly and targeted to the right server.
Level: 1

Type: ERROR

Impact: Data

WSM-04510: The version {0} for resource {1} cannot be found.

Cause: The requested version for the specified resource was not found.

Action: Check the search criteria, and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-04511: cannot perform simultaneous deletes

Cause: Deleting multiple resources simultaneously from the data store failed.

Action: Check supplied data, and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-04512: internal data store error

Cause: A generic data store exception occurred.

Action: Check the data store credentials that were provided and retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-04513: cannot commit changes to the repository

Cause: A failure occurred while finalizing changes to the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-04514: The version {0} for resource {1} cannot be deleted.

Cause: Deleting the specified version(s) of the resource failed.

Action: Check the supplied values, and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-04515: Auditing is disabled for MDS operations.

Cause: An internal error occurred; failed to initialize the auditor.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-04516: The version of the passed resource is invalid.

Cause: The requested version of the resource was invalid.

Action: The version number must be a positive integer.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-04517: cannot update resource {0}

Cause: The resource to be updated was concurrently being updated by another process.

Action: Make sure no other process is attempting to change the resource being updated, and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-04518: document name is invalid

Cause: The document name was invalid.

Action: Specify a name for the document that follows the document naming conventions. Refer to Oracle documentation for the naming rules.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-04519: Unable to create document.

Cause: The repository permissions were read-only. Creation of a new document requires write permissions.

Action: Reconfigure the repository to have write permissions.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-04520: The repository timestamp is invalid.

Cause: The repository timestamp was invalid or missing.

Action: Retry the operation. If the problem persists, consult the diagnostic logs.
Level: 1

Type: NOTIFICATION

Impact: Programmatic

WSM-04521: Resource to be deleted does not exist in datastore.

Cause: The resource could not be deleted since it does not exist in the data store.

Action: You don't need to take any action, the resource is not present in the datastore.
Level: 1

Type: ERROR

Impact: Data

WSM-04601: A JDBC URL is required to connect to a database-based MDS repository.

Cause: A null or empty JDBC URL was provided when attempting to create an MDS instance for a database-based repository.

Action: Provide a valid JDBC URL and try again.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-04602: A password is required to connect to a database-based MDS repository.

Cause: A null or empty password was provided when attempting to create an MDS instance for a database-based repository.

Action: Provide a valid password and try again.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-04603: A username is required to connect to a database-based MDS repository.

Cause: A null or empty username was provided when attempting to create an MDS instance for a database-based repository.

Action: Provide a valid username and try again.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-04606: One or more directories are required to connect to a file-based MDS repository.

Cause: A path was not provided when attempting to create an MDS instance for a file-based repository.

Action: Provide a valid directory and try again.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-04611: An MDS session cannot be created due to underlying error "{0}".

Cause: MDS encountered an unexpected condition.

Action: Follow the recommendations for the underlying exception.
Level: 1

Type: ERROR

Impact: Data

WSM-04641: The operation "{0}" for document "{1}" cannot be performed on a closed session.

Cause: A operation was requested on a session that has already been closed.

Action: Create a new repository session and perform the operation again.
Level: 1

Type: NOTIFICATION

Impact: Programmatic

WSM-04642: The operation "{0}" for document "{1}" cannot be performed on a read-only session.

Cause: A write operation was requested on a read-only session.

Action: Provide the name of a creator to associate with write operations.
Level: 1

Type: NOTIFICATION

Impact: Configuration

Cause: See error message.

Action: Create a new session on a writable repository and try again.

WSM-04643: The operation "{0}" cannot be performed on virtual document "{1}".

Cause: A write operation was requested on a virtual document.

Action: Choose a different document name and try again.
Level: 1

Type: NOTIFICATION

Impact: Configuration

WSM-04651: The search criterion "{0}" does not identify a specific document to be created.

Cause: The supplied criterion does not have the correct type.

Action: Supply a NAME search criterion.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-04652: The document "{0}" already exists in the repository.

Cause: The document already exists in the repository.

Action: Choose a different name for the document to create or perform an update instead.
Level: 1

Type: ERROR

Impact: Data

WSM-04653: The document "{0}" cannot be created in a read-only repository.

Cause: The repository is read-only.

Action: Reconfigure the repository to support writes and try again.
Level: 1

Type: ERROR

Impact: Configuration

WSM-04654: The name "{0}" is invalid for creating a document due to underlying reason "{2}".

Cause: The document name is invalid for the repository.

Action: Choose a valid name and try again.
Level: 1

Type: ERROR

Impact: Data

WSM-04655: Repository information cannot be marshalled due to underlying parser error "{2}"

Cause: The system does not support the required DOM document builder configuration.

Action: Correct underlying error or contact Oracle Support Services for assistance.
Level: 32

Type: INCIDENT_ERROR

Impact: Other

WSM-04656: Repository information cannot be marshalled due to underlying marshalling error "{2}"

Cause: The repository information object could not be marshalled into a DOM document.

Action: Correct underlying error or contact Oracle Support Services for assistance.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-04657: The document "{0}" cannot be created in a session spanning multiple stores due to underlying error "{2}".

Cause: The document to be created belongs in a store that is different from other write operations in the session.

Action: Create the document in a different session.
Level: 1

Type: ERROR

Impact: Configuration

WSM-04661: The document "{0}" cannot be deleted in a read-only repository.

Cause: The repository is read-only.

Action: Reconfigure the repository to support writes and try again.
Level: 1

Type: ERROR

Impact: Data

WSM-04662: The name "{0}" is invalid for deleting a document due to underlying reason "{2}".

Cause: The document name is invalid for the repository.

Action: Choose a valid name and try again.
Level: 1

Type: ERROR

Impact: Data

WSM-04663: The document "{0}" cannot be deleted in a session spanning multiple stores due to underlying error "{2}".

Cause: The document to be created belongs in a store that is different from other write operations in the session.

Action: Delete the document in a different session.
Level: 1

Type: ERROR

Impact: Data

WSM-04664: Version {1} to {3} of document "{0}" cannot be deleted.

Cause: The repository does not support deletion of individual versions of a document.

Action: Ignore the document version or delete the entire document.
Level: 1

Type: ERROR

Impact: Data

WSM-04671: A concurrent write prevented the document "{0}" from being written due to underlying error "{2}".

Cause: Two or more incompatible operations were performed on the same document.

Action: Perform the incompatible operations in different sessions.
Level: 1

Type: ERROR

Impact: Data

Cause: A document in this session was modified by another session.

Action: Retry the operation.

WSM-04672: The document "{0}" cannot be written to repository due to underlying error "{2}".

Cause: An I/O error occurred while writing to repository.

Action: Correct the underlying problem and retry.
Level: 1

Type: ERROR

Impact: Data

WSM-04673: The session cannot be commited due to underlying error "{2}".

Cause: The resource could not be deleted since it does not exist in the data store.

Action: You don't need to take any action, the resource is not present in the datastore.
Level: 1

Type: ERROR

Impact: Data

WSM-04674: The document "{0}" cannot be validated due to underlying error "{2}".

Cause: Validation failed for a metadata object written in the session.

Action: Correct the underlying problem and retry.
Level: 1

Type: ERROR

Impact: Data

WSM-04681: The document "{0}" to be modified was not found in the repository due to underlying error "{2}".

Cause: The document was not found in the repository.

Action: Create the document instead of modifying it.
Level: 1

Type: ERROR

Impact: Data

WSM-04682: The document "{0}" cannot be modified in a session spanning multiple stores due to underlying error "{2}".

Cause: The document to be modified belongs in a store that is different from other write operations in the session.

Action: Modify the document in a different session.
Level: 1

Type: ERROR

Impact: Data

WSM-04691: The document "{0}" cannot be found in repository due to underlying error "{2}".

Cause: The document was not found in the repository.

Action: Create the document and try again.
Level: 1

Type: NOTIFICATION

Impact: Data

WSM-04692: The name "{0}" is invalid for retrieving a document due to the error "{2}".

Cause: The document name is invalid for the repository.

Action: Choose a valid name and try again.
Level: 1

Type: ERROR

Impact: Data

WSM-04693: Version information is not available for document "{0}".

Cause: The document does not exist

Action: Create the document first.
Level: 1

Type: ERROR

Impact: Data

Cause: The repository does not support versioning.

Action: Configure the repository to support versioning.

WSM-04694: An invalid directory was provided to connect to a file-base MDS repository.

Cause: An invalid directory was provided when attempting to create an MDS instance for a file-based repository.

Action: Provide a valid directory and try again.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-04695: The retrieved version of document "{0}" is no longer available.

Cause: A new version of the document was created after it was initially retrieved.

Action: Retry the operation to get the latest version of the document.
Level: 1

Type: ERROR

Impact: Data

WSM-04696: The operation "{0}" cannot be performed on a closed session.

Cause: A operation was requested on a session that has already been closed.

Action: Create a new repository session and perform the operation again.
Level: 1

Type: NOTIFICATION

Impact: Programmatic

WSM-04697: The operation "{0}" cannot be performed on a read-only session.

Cause: A write operation was requested on a read-only session.

Action: Provide the name of a creator to associate with write operations.
Level: 1

Type: NOTIFICATION

Impact: Configuration

Cause: See error message.

Action: Create a new session on a writable repository and try again.

WSM-04698: Versions {1} to {3} of document "{0}" are not deletable due to underlying error "{2}".

Cause: An I/O error occurred while trying to delete versions of a document from repository.

Action: Correct the underlying problem and retry.
Level: 1

Type: ERROR

Impact: Data

WSM-04699: A write lock is not available to delete versions {1} to {3} of document "{0}" due to underlying error "{2}".

Cause: A write lock could not be obtained to delete versions of a document.

Action: Retry the operation.
Level: 1

Type: WARNING

Impact: Data

WSM-06001: Error obtaining Policy Set.

Cause: Failed to get PolicySet.

Action: Check log file for possible causes.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06017: Error converting to the canonical path for the File Policy Resolver.

Cause: An invalid canonical path was passed for the File Policy Resolver.

Action: Verify the canonical path passed for the File Policy Resolver and retry the operation.
Level: 1

Type: ERROR

Impact: Files

WSM-06036: The class cannot be instantiated.

Cause: The system could not instantiate a class.

Action: Consult the Java documentation or Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-06101: The policy set cannot be created for null Service Component Architecture (SCA) node.

Cause: The PolicySet could not be generated for the null Service Component Architecture (SCA) node.

Action: Pass a valid SCA node object.
Level: 1

Type: ERROR

Impact: Compliance

WSM-06102: The policy reference URI "{0}" is not valid.

Cause: The Policy Reference URI provided was not valid.

Action: Verify that the Policy Reference URI in the SCA node is correct and the policy exists in the repository.
Level: 1

Type: ERROR

Impact: Compliance

WSM-06103: No configuration has been specified for the Policy Accessor.

Cause: The Policy Accessor object could not be initialized because it is not correctly configured.

Action: Call the init method to initialize the Policy Accessor object before invoking this method.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06104: The protocol specified for Policy Accessor is not supported.

Cause: A policy access protocol was specified that was invalid for this environment.

Action: Change protocol to one that is supported by the environment. For J2EE environments, the supported protocols are "local" and "remote"; for J2SE environments, the supported protocols are "classpath", "local", and "remote".
Level: 1

Type: ERROR

Impact: Compliance

WSM-06105: The duplicate policy references are found in the same Service Component Architecture (SCA) binding node.

Cause: The same policy has been attached multiple times and so duplicate policy references were found in the same Service Component Architecture (SCA) binding node.

Action: Remove the duplicate policy references from the SCA binding node by attaching each policy only once.
Level: 1

Type: ERROR

Impact: Compliance

WSM-06106: The policy reference URI cannot be empty.

Cause: Empty policy references were found in the Service Component Architecture (SCA) node.

Action: Verify the Service Component Architecture (SCA) node and make sure the policy references specify a valid value and the referenced policies exist in the repository.
Level: 1

Type: ERROR

Impact: Compliance

WSM-06107: The node that is expected is <binding.ws> or <component>. The node {0} passed is not a supported node.

Cause: An unsupported Service Component Architecture (SCA) node was found.

Action: Specify a supported SCA node. Consult Oracle documentation for further details
Level: 1

Type: ERROR

Impact: Compliance

WSM-06108: Error initializing the Oracle WSM Policy Resolver because incorrect configuration is passed

Cause: The Policy Resolver did not get created. This could be due to the wrong configuration being passed.

Action: Verify the configuration passed for creating the Policy Resolver. Verify that the correct Policy Accessor protocol is passed.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06109: Cannot retrieve policies.

Cause: The policies were not retrieved. This may be due to incorrect policy references in the Service Component Architecture (SCA) node.

Action: Verify that the policy references are referring to policies that exist in the repository. Also, ensure that the data store is seeded with policies.
Level: 1

Type: ERROR

Impact: Data

WSM-06110: The MetaData Store (MDS) home cannot be null.

Cause: The Policy Repository was not valid because MDS Home is set to null.

Action: Check the mds.home.module property for the correct value for MDS Home.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06111: The policy name cannot be null.

Cause: The policy name passed was null or empty.

Action: Verify that the policy name is not an empty string, and verify that a null policy name is not being passed.
Level: 1

Type: ERROR

Impact: Compliance

WSM-06112: Policies are not supported for a node of type:{0}.

Cause: Policies cannot be retrieved for unsupported Service Component Architecture (SCA) nodes.

Action: Verify that a supported SCA node is provided for retrieving the policy.
Level: 1

Type: WARNING

Impact: Compliance

WSM-06113: The configuration name cannot be null or empty.

Cause: The configuration file was either empty or did not exist.

Action: Verify that the configuration file exists and contains policy references to retrieve policies from the Policy Repository.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06114: The home directory for the File Policy Resolver cannot be null.

Cause: The home directory for File Policy Resolver was null.

Action: Verify that a valid home directory is passed for the File Policy Resolver.
Level: 1

Type: ERROR

Impact: Files

WSM-06115: The path for the File Policy Resolver does not exist.

Cause: The path for File Policy Resolver did not exist.

Action: Ensure that a valid path is passed for File Policy Resolver.
Level: 1

Type: ERROR

Impact: Files

WSM-06116: The path for the File Policy Resolver is not a directory.

Cause: An invalid directory name was passed for the File Policy Resolver.

Action: Verify that a valid directory name is passed for the File Policy Resolver.
Level: 1

Type: ERROR

Impact: Files

WSM-06118: The resource name for the File Policy Resolver cannot be null.

Cause: The resource name for the File Policy Resolver is null.

Action: Verify that a valid resource name is passed for the File Policy Resolver.
Level: 1

Type: ERROR

Impact: Files

WSM-06119: The file {0} for the File Policy Resolver does not exist under {1}.

Cause: The file did not exist.

Action: Verify that the file exists at the specified location.
Level: 1

Type: ERROR

Impact: Files

WSM-06120: The resource name for the File Policy Resolver cannot be null.

Cause: The resource name for the File Policy Resolver was null.

Action: Ensure that a non-null resource name is passed for the File Policy Resolver.
Level: 1

Type: ERROR

Impact: Files

WSM-06121: No policy is found for the policy reference: {0}.

Cause: No policy was found for the specified policy reference.

Action: Verify that the policy exists in the repository for the given policy reference, and that the correct policy reference is passed.
Level: 1

Type: ERROR

Impact: Data

WSM-06122: Error retrieving policies.

Cause: An unexpected error occurred while retrieving the policies from the Policy Manager.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-06123: Error initializing internally the File Policy Resolver: {0} {1}

Cause: An unexpected error occurred while initializing the File Policy Resolver.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Security

WSM-06124: Error initializing the Oracle WSM Policy Manager Policy Resolver : {0} {1}.

Cause: An unexpected error occurred while initializing the Policy Manager Policy Resolver. The Policy Manager Policy Resolver was not able to find the property named mds.config

Action: Verify that the property mds.config exists and is referencing a valid property file.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-06125: Error in the XPath expression {0}.

Cause: The XPath Expression for the policy reference for the given Service Component Architecture (SCA) node was invalid.

Action: Verify the XPath for the policy reference within the SCA node.
Level: 1

Type: ERROR

Impact: Compliance

WSM-06128: Error accessing the PolicySet : {0} : {1}.

Cause: An unexpected error occurred while accessing the PolicySet.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-06129: Error parsing the PolicySet : {0} : {1}.

Cause: An unexpected error occurred while parsing the PolicySet.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-06130: Error creating the policy parser.

Cause: The Policy Parser did not get created.

Action: Check the configuration for the Policy Parser.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06132: Error creating a connection to Oracle WSM Policy Manager.

Cause: A failure occurred while connecting to the Policy Manager.

Action: Ensure that the Policy Manager is up and running. Ensure that WSM-PM is installed, deployed correctly and running at http://<host:port>/wsm-pm/ and by clicking the Validator link. Also, ensure that the database to which WSM-PM connects is up and the mds-owsm data source is configured properly and targeted to the right server.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06133: Error connecting to Oracle WSM Policy Manager.

Cause: A failure occurred while connecting to Policy Manager J2EE Application.

Action: Before connecting to a Policy Manager, ensure that the Policy Manager is up and running.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06134: The class cannot be found.

Cause: The class could not be found in the classpath.

Action: Verify that the class name is correct in the configuration files and ensure that the class is specified in the classpath variable.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06135: The class cannot be loaded due to Java 2 security restrictions.

Cause: Some classes were not loaded due to class loading security restrictions.

Action: Contact the site administrator or Java documentation to ensure that the classes have the necessary Java2 security permissions.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06137: The "mds" policy access protocol is deprecated - use "local" instead.

Cause: A deprecated Policy Accessor Protocol was specified.

Action: Update the configuration to use the standard protocol name.
Level: 1

Type: WARNING

Impact: Configuration

WSM-06138: The "owsm" policy access protocol is deprecated - use "remote" instead.

Cause: A deprecated Policy Accessor protocol was specified.

Action: Update the configuration to use the standard protocol name.
Level: 1

Type: WARNING

Impact: Configuration

WSM-06139: Error closing a stream

Cause: Failure occurred in closing the stream while parsing the configuration file or the policy in the FILE protocol.

Action: Verify that the correct configuration file or policy name is provided.
Level: 1

Type: WARNING

Impact: Configuration

WSM-06140: Failure finding policy {0} in the classpath roots path {1}.

Cause: The policy did not exist in any of the configured roots.

Action: Correct the reference to point to a policy that exists.
Level: 1

Type: WARNING

Impact: Configuration

Cause: The configured roots are invalid.

Action: Correct the classpath roots to point to the correct locations.

WSM-06141: Error initializing Policy Resolver.

Cause: The Policy Resolver was not initialized.

Action: Invoke the init method to initialize the Policy Resolver before executing this method.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06142: Unable to retrieve policy store timestamp.

Cause: The Policy Resolver could not connect to Policy Manager to retrieve the policy store timestamp.

Action: Check the MDS configuration file.
Level: 1

Type: WARNING

Impact: Configuration

WSM-06143: The validation check in the policy "{0}" failed.

Cause: An error occurred while validating the policy.

Action: Ensure that the policy is valid.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06144: Null policy subject value is not allowed from JEE application.

Cause: The null policy subject value was passed from JEE application.

Action: Ensure that a valid policy subject is passed from the JEE application.
Level: 1

Type: ERROR

Impact: Compliance

WSM-06145: Internal system error, cannot look up credential

Cause: Failure occurred while looking up credentials.

Action: Internal system configuration error. Contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-06146: Error deleting the attachment entries.

Cause: Failure occurred while deleting the attachment entries.

Action: Ensure that a valid list of policy subjects for deactivated lifecycle type is passed
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-06147: There is mismatch in Policy reference category "{0}" and Policy category "{1}". Policy reference category should match with Policy category.

Cause: Mismatch in expected policy category and fetched policy category.

Action: Confirm that the Policy Reference category is correct and that it matches the Policy category.
Level: 1

Type: WARNING

Impact: Data

WSM-06148: Unable to apply property overrides to Policy

Cause: Unable to apply property overrides to Policy.

Action: Make sure the policy model conforms to the Oracle Web service policy model.
Level: 1

Type: WARNING

Impact: Data

WSM-06149: The policy reference URI is not valid : {0}

Cause: The Policy Reference URI provided was not valid.

Action: Verify that the Policy Reference URI is correct.
Level: 1

Type: ERROR

Impact: Compliance

WSM-06150: Invalid category : {0} for policy : {1}. Only policies assigned to the security category are supported.

Cause: The Policy category provided was not valid.

Action: Verify that the Policy category is correct.
Level: 1

Type: ERROR

Impact: Compliance

WSM-06152: The Policy Cache is not available.

Cause: The Policy Cache is not available.

Action: You may need to restart the server.
Level: 1

Type: ERROR

Impact: Compliance

WSM-06153: Could not access the Policy Cache.

Cause: Cannot access the Policy Cache.

Action: You may need to restart the server.
Level: 1

Type: ERROR

Impact: Compliance

WSM-06154: Could not initialize Policy Java Object Cache.

Cause: Cannot initialize the Policy Cache.

Action: You may need to restart the server.
Level: 1

Type: ERROR

Impact: Compliance

WSM-06155: Could not re-create Policy Java Object Cache.

Cause: Could not re-create the Policy Cache.

Action: You may need to restart the server.
Level: 1

Type: ERROR

Impact: Compliance

WSM-06201: The {0} repository accessor class cannot be accessed due to underlying error "{1}".

Cause: The nullary constructor for the specified accessor is not accessible to the configuration framework.

Action: Specify a valid accessor.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06202: The {0} repository accessor class cannot be initialized due to underlying error "{1}".

Cause: A exception was encountered during evaluation of a static initializer for the specified accessor class.

Action: Specify a valid accessor.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06203: The {0} repository accessor class cannot be used as a repository accessor because it does not implement the {1} interface.

Cause: The specified accessor does not implement the IRepositoryAccessor interface.

Action: Specify a valid accessor.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06204: The {0} repository accessor class cannot be linked due to underlying error "{1}".

Cause: The specified accessor depends on a class whose signature has changed since the accessor was compiled.

Action: Update the accessor class or revert to an older version of the dependent class.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06205: The repository accessor "{0}" cannot be found due to underlying error "{1}".

Cause: The specified accessor was not found.

Action: Specify a valid accessor.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06206: The {0} repository accessor class cannot be instantiated due to underlying error "{1}".

Cause: The specified accessor is an abstract class, an interface, an array class, a primitive type, or void, or the class does not have a nullary constructor.

Action: Specify a valid accessor.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06207: A task scheduler was not available for configuring the {0} repository accessor for context "{1}".

Cause: A task scheduler was not supplied to the configuration framework.

Action: Provide a task scheduler to the configuration framework.
Level: 1

Type: WARNING

Impact: Configuration

WSM-06208: Access to the {0} repository accessor class is denied due to underlying error "{1}".

Cause: The configuration framework does not have permission to instantiate the specified accessor.

Action: Ensure the necessary permissions are granted to the WSM code base.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06209: An action executor cannot be created for user "{0}" due to underlying error "{1}".

Cause: The configuration framework did not have permission to get an action executor.

Action: Ensure the necessary permissions are granted to the WSM code base.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06210: An instance of the {2} bean for the local repository at path "{3}" was not available for configuring the {0} repository accessor for context "{1}".

Cause: A bean instance could not be obtained by the configuration framework.

Action: Correct underlying problem and wait for coniguration refresh.
Level: 1

Type: WARNING

Impact: Configuration

WSM-06211: An instance of the {2} bean for the local repository at path "{3}" was provided for configuring the {0} repository accessor for context "{1}".

Cause: A bean instance was obtained by the configuration framework.

Action: None.
Level: 1

Type: NOTIFICATION

Impact: Configuration

WSM-06212: An instance of the {2} bean for a remote repository was not available for configuring the {0} repository accessor for context "{1}".

Cause: A bean instance could not be obtained by the configuration framework.

Action: Correct underlying problem and wait for coniguration refresh.
Level: 1

Type: WARNING

Impact: Configuration

WSM-06213: An instance of the {2} bean for a remote repository was provided for configuring the {0} repository accessor for context "{1}".

Cause: A bean instance was obtained by the configuration framework.

Action: None.
Level: 1

Type: NOTIFICATION

Impact: Configuration

WSM-06214: A task scheduler was provided for configuring the {0} repository accessor for context "{1}".

Cause: A task scheduler was supplied to the configuration framework.

Action: None.
Level: 1

Type: NOTIFICATION

Impact: Configuration

WSM-06215: An instance of the {1} bean for the local repository at path "{2}" was not available for configuring the {0} repository accessor for the default context.

Cause: A bean instance could not be obtained by the configuration framework.

Action: Correct underlying problem and wait for coniguration refresh.
Level: 1

Type: WARNING

Impact: Configuration

WSM-06216: An instance of the {1} bean for the local repository at path "{2}" was provided for configuring the {0} repository accessor for the default context.

Cause: A bean instance was obtained by the configuration framework.

Action: None.
Level: 1

Type: NOTIFICATION

Impact: Configuration

WSM-06217: An instance of the {1} bean for a remote repository was not available for configuring the {0} repository accessor for the default context.

Cause: A bean instance could not be obtained by the configuration framework.

Action: Correct underlying problem and wait for coniguration refresh.
Level: 1

Type: WARNING

Impact: Configuration

WSM-06218: An instance of the {1} bean for a remote repository was provided for configuring the {0} repository accessor for the default context.

Cause: A bean instance was obtained by the configuration framework.

Action: None.
Level: 1

Type: NOTIFICATION

Impact: Configuration

WSM-06219: A task scheduler was not available for configuring the {0} repository accessor for the default context.

Cause: A task scheduler was not supplied to the configuration framework.

Action: Provide a task scheduler to the configuration framework.
Level: 1

Type: WARNING

Impact: Configuration

WSM-06220: A task scheduler was provided for configuring the {0} repository accessor for the default context.

Cause: A task scheduler was supplied to the configuration framework.

Action: None.
Level: 1

Type: NOTIFICATION

Impact: Configuration

WSM-06221: The password credentials cannot be obtained from the Credential Store.

Cause: Failure occurred while querying for credentials from CSF.

Action: Check CSF configuration.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06222: The credentials passed to the credentials store are expired.

Cause: The Credentials have expired.

Action: Ensure valid credentials are passed
Level: 1

Type: ERROR

Impact: Configuration

WSM-06223: The access to the store or credentials is denied.

Cause: The requested access Credentials or Store is denied.

Action: Ensure Store is properly initialized and valid credentials are passed
Level: 1

Type: ERROR

Impact: Configuration

WSM-06224: Unexpected exception "{0}" caught when privileged method is called.

Cause: Unexpected exception caught on calling a privileged code.

Action: Check the underlying signature of method called in privileged code
Level: 1

Type: ERROR

Impact: Configuration

WSM-06225: Unable to retrieve credentials for the specified CSF key {0}.

Cause: Credential configuration in the policy accessor configuration file was incorrect.

Action: Configure policy with valid CSF key.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06301: Subject Metadata is required when registering a listener.

Cause: A null value was provided for the subject metadata.

Action: Provide a valid metadata.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-06302: A listener is required for asynchronous notification.

Cause: A null value was provided for asynchronous listener registration.

Action: Provide a valid listener.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-06303: The method "{0}" was not called with required permission "{1}"

Cause: The method was not called with required permission

Action: Ensure necessary permissions are granted to the caller before calling the required methods.
Level: 1

Type: ERROR

Impact: Security

WSM-07501: Failure in Oracle WSM Agent processRequest, category={0}, function={1}, application={2}, composite={3}, modelObj={4}, policy={5}, policyVersion={6}, assertionName={7}.

Cause: Processing request failed in the security interceptor while enforcing policy.

Action: Check the log file for possible causes.
Level: 1

Type: ERROR

Impact: Configuration

WSM-07502: Failure in Oracle WSM Agent processResponse, category= {0}, function={1}, application={2}, composite={3}, modelObj={4}, policy={5}, policyVersion={6}, assertionName={7}.

Cause: Processing response failed in the security interceptor while enforcing policy.

Action: Check the log file for possible causes.
Level: 1

Type: ERROR

Impact: Configuration

WSM-07503: Failure in Oracle WSM Agent processFault, category= {0}, function={1}, application={2}, composite={3}, modelObj={4}, policy={5}, policyVersion={6}, assertionName={7}.

Cause: Processing fault failed in the security interceptor while enforcing policy.

Action: Check the log file for possible causes.
Level: 1

Type: ERROR

Impact: Configuration

WSM-07504: Failure in Oracle WSM Agent processEvent, category= {0}, function={1}, application={2}, composite={3}, modelObj={4}.

Cause: Processing Fabric Lifecycle event failed in security interceptor.

Action: Check the log file for possible causes
Level: 1

Type: ERROR

Impact: Configuration

WSM-07505: Failure in Oracle WSM Agent initialization, category= {0}, function={1}.

Cause: Agent initialization failed in the security interceptor.

Action: Check the log file for possible causes.
Level: 1

Type: ERROR

Impact: Configuration

WSM-07506: Failure in Oracle WSM Agent processFinish, category= {0}, function={1}, application={2}, composite={3}, modelObj={4}.

Cause: Agent finish failed in the security interceptor.

Action: Check the log file for possible causes.
Level: 1

Type: ERROR

Impact: Configuration

WSM-07507: Failure in Oracle WSM Agent, category= {0}, function={1}, stage={2} due to RuntimeException.

Cause: An unexpected RuntimeException was encountered while trying to access security interceptor.

Action: Check the log file for possible causes and retry the operation.
Level: 1

Type: WARNING

Impact: Data

WSM-07508: Oracle WSM Agent initialization failed due to PolicySet validation errors: {0}, with PolicySet={1}

Cause: Agent not initialized due to PolicySet validation errors

Action: Check the log for detail
Level: 1

Type: ERROR

Impact: Configuration

WSM-07509: Oracle WSM Agent must be initialized with valid properties. Following parameters [{0}] are either Empty or null

Cause: Agent not initialized with valid parameters.

Action: Initialize the Agent with required parameters
Level: 1

Type: ERROR

Impact: Configuration

WSM-07600: Error while copying the message.

Cause: An unexpected error occurred while cloning SOAP or normalized message context.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Security

WSM-07601: Failure initializing the WSPolicyExecutor class {0}.

Cause: An unexpected error occurred while initializing the policy engine.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-07602: Failure in WS-Policy Execution due to exception.

Cause: Due to an unexpected error, policy execution failed at runtime.

Action: Check the log file for possible causes.
Level: 1

Type: ERROR

Impact: Security

WSM-07603: Failure in log assertion execution caused by exception.

Cause: File I/O problem or SOAP message access problem occurred.

Action: Verify file access permission and the SOAP message.
Level: 1

Type: ERROR

Impact: Files

WSM-07604: Internal error during policy enforcement.

Cause: An unexpected error occurred while enforcing the policy.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Security

WSM-07605: The binding.ws port ID {0} is invalid.

Cause: An unexpected error occurred in the Oracle WSM processEvent API.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-07606: Policy {0} execution failure.

Cause: Due to an unexpected error, policy execution failed at runtime.

Action: Check the log file for possible causes.
Level: 1

Type: ERROR

Impact: Security

WSM-07607: Failure in execution of assertion {0} executor class {1}.

Cause: The policy engine failed to execute an assertion.

Action: Check the log file for possible causes.
Level: 1

Type: ERROR

Impact: Security

WSM-07608: The assertion type is not valid.

Cause: Policy execution failed due to an invalid assertion.

Action: Check the assertion type.
Level: 1

Type: ERROR

Impact: Security

WSM-07609: Policy with attachto value of {0} cannot be applied to subject of type {1}.

Cause: The attached policy was incompatible with the subject.

Action: Verify that the subject type and the policy's Attachto value are compatible.
Level: 1

Type: ERROR

Impact: Security

WSM-07610: Internal error in policy status audit. One or more of the argument passed is null, result:{0}, agentFunction:{1}, policy:{2}, msgCtx:{3}

Cause: An internal error occurred; the enforcement auditor encountered one or more null arguments.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-07611: Failure initializing of enforcement auditor: category={0}, function= {1}, topologyNode={2}.

Cause: An internal error occurred; the enforcement auditor initialization failed.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-07612: Failure shutting down enforcement auditor.

Cause: An internal error occurred; the enforcement auditor shutdown failed.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-07613: Failure enforcing auditing policy.

Cause: An internal error occurred while auditing security or management policy enforcement.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-07614: Failure in Agent initialization due to invalid topology node path. Topology node path cannot be null or empty for non-JSE client. category={0}, function={1}, topologyNode={2}, isRunningInJEE={3}

Cause: Oracle WSM Agent initialization failed due to problem creating and initializing DMS instrumentation. An invalid, null, or empty topology node path was encountered for non-JSE client.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-07616: Resource name not retrievable from MessageContext. Guard evaluation requires resource name to be present in MessageContext

Cause: Resource name not retrievable from MessageContext. Guard evaluation requires resource name to be present in MessageContext

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Security

WSM-07617: Policy: {0} contains unsupported assertions.

Cause: Policy contains unsupported assertions. Assertions of type http-security are not supported for WLS JAXWS web services.

Action: Check the assertion type.
Level: 1

Type: ERROR

Impact: Security

WSM-07618: Failed to execute the assertion "{0}" in the conditional policy. {1}

Cause: Failed to execute the assertion

Action: Check exception stack trace for details
Level: 1

Type: ERROR

Impact: Security

WSM-07619: Failed to retrieve the Welogic Server subject.

Cause: An error occurred while retrieving Weblogic Server subject.

Action: Check log file for possible cause.
Level: 1

Type: ERROR

Impact: Security

WSM-07620: Agent cannot enforce policies due to either failure in retrieving polices or error in validations, detail= "{0}".

Cause: Either policies can not be retrieved or Policy/PolicySet have validation errors.

Action: Correct the validation errors and retry again.
Level: 1

Type: ERROR

Impact: Security

WSM-07621: Oracle WSM Advertisement Engine failed with valid PolicySet, validation errors: [{0}], and PolicySet: [{1}]

Cause: Advertisment failed due to runtime PolicySet validation error in WSMEngineInvoker

Action: Check log for detail to correct Runtime PolicySet
Level: 1

Type: ERROR

Impact: Other

WSM-09001: The audit event definitions cannot be found.

Cause: Component audit event definitions were missing.

Action: Check the installation for any missing or corrupted JAR files.
Level: 1

Type: ERROR

Impact: Configuration

WSM-09002: The audit event definitions file cannot be opened.

Cause: Component audit event definitions could not be opened.

Action: Check the installation for any corrupted JAR files, or free up system resources.
Level: 1

Type: ERROR

Impact: Configuration

WSM-09003: The audit event definitions file cannot be read.

Cause: Component's audit event definitions were not readable.

Action: Check the installation for any corrupted JAR files.
Level: 1

Type: ERROR

Impact: Configuration

WSM-09004: Component auditing cannot be initialized.

Cause: The audit framework encountered an error.

Action: Check the logs for the possible causes.
Level: 1

Type: WARNING

Impact: Logging

WSM-09005: It is not possible to verify that the event is enabled.

Cause: The audit framework encountered an error.

Action: Check the logs for the possible causes.
Level: 1

Type: ERROR

Impact: Logging

WSM-09006: The event cannot be audited. Another attempt will be made to audit the event.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Logging

WSM-09007: The event cannot be audited.

Cause: The audit framework encountered an error.

Action: Check the logs for the possible causes.
Level: 1

Type: ERROR

Impact: Logging

WSM-09008: A URL cannot be created for {0}.

Cause: XML utility encountered an error.

Action: Check the logs for the possible causes.
Level: 1

Type: ERROR

Impact: Logging

WSM-09009: Failure parsing the XML file

Cause: XML utility encountered an error.

Action: Check the logs for the possible causes.
Level: 1

Type: ERROR

Impact: Logging

WSM-09010: Error opening and/or closing the stream

Cause: XML utility encountered an error.

Action: Check the logs for the possible causes.
Level: 1

Type: ERROR

Impact: Logging

WSM-09011: Error writing the XML file

Cause: XML utility encountered an error.

Action: Check the logs for the possible causes.
Level: 1

Type: ERROR

Impact: Logging

WSM-09012: Key, {0}, is not found in the resource bundle {1}.

Cause: No key was found in the provided resource bundle.

Action: Add the key to the resource bundle and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-09013: Failure shutting down auditing.

Cause: An exception was caught when attempting to shut down the audit framework.

Action: Examine the stack trace for any underlying errors.
Level: 1

Type: WARNING

Impact: Logging

WSM-09014: Streaming SOAP message attachment is not being logged.

Cause: SOAP message attachment was not logged because it was a streaming attachment.

Action: Check the logs for the possible causes.
Level: 1

Type: WARNING

Impact: Logging

WSM-09015: Interrupted while checking out object from pool.

Cause: Received interrupt while checking out from pool.

Action: Check the logs for the possible causes.
Level: 1

Type: ERROR

Impact: Other

WSM-09016: Failure creating transformer using factory {0}.

Cause: Transformer factory failed to create new transformer instance.

Action: Check the logs for the possible causes.
Level: 1

Type: ERROR

Impact: Other

WSM-09017: Failure checking out a transformer instance.

Cause: Failure checking out a transformer instance.

Action: Check the logs for the possible causes.
Level: 1

Type: ERROR

Impact: Other

WSM-09018: A ScheduledExecutorService is required when creating a scheduler wrapper.

Cause: A ScheduledExecutorService was not provided when constructing a wrapper.

Action: Provide a valid ScheduledExecutorService instance.
Level: 1

Type: ERROR

Impact: Other

WSM-09019: An executor requires a task for scheduling.

Cause: A task was not provided when scheduling a task.

Action: Provide a valid task.
Level: 1

Type: ERROR

Impact: Other

WSM-09020: An executor rejected a task due to error "{0}".

Cause: The ScheduledExecutorService refused to schedule a task.

Action: Check the logs for the possible causes.
Level: 1

Type: ERROR

Impact: Other

WSM-09021: A TimerManager is required when creating a scheduler wrapper.

Cause: A TimerManager was not provided when constructing a wrapper.

Action: Provide a valid TimerManager instance.
Level: 1

Type: ERROR

Impact: Other

WSM-09022: A timer cannot schedule a task due to illegal argument error "{0}".

Cause: A task was not provided when scheduling a task.

Action: Provide a valid task.
Level: 1

Type: ERROR

Impact: Other

Cause: The scheduling parameters were negative.

Action: Provide non-negative values.

WSM-09023: A timer cannot schedule a task due to illegal state error "{0}".

Cause: A task could not be scheduled because the underlying TimerManager was stopped.

Action: Schedule the task using a running TimerManager.
Level: 1

Type: ERROR

Impact: Other

WSM-09024: Failure parsing the XML URL when: {0}, from: {1}

Cause: XML utility parseXMLDocument from URL encountered an error.

Action: Check the logs for the possible causes.
Level: 1

Type: ERROR

Impact: Logging

103 WWC-00000 to WWC-59083

WWC-00000: normal, successful completion

Cause: The operation was successful if this message is displayed by itself. Unexpected errors may have occurred if other messages accompany this message.

Action: None, if this message is displayed by itself. If other messages accompany this message, review the information in those error messages and take corrective action.
Level: 1

Type: ERROR

Impact: Other

WWC-00001: message not found: %0.%1

Cause: The message identified by the stated type/name combination was not found in the system message table.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWC-00002: message ID not found: %0

Cause: The message identified by the given ID was not found in the system message table.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWC-00006: internal error

Cause: A process encountered a low-level, unexpected condition. This is the generic internal error number for program exceptions.

Action: Report this error to Oracle Support Services. Include the error, the attempted operations that led to the error, any unusual circumstances that occurred before receiving this error message, and the complete stack trace produced by this error.
Level: 1

Type: ERROR

Impact: Other

WWC-35002: an attempt to access the session context without a valid session

Cause: User sessions are cleaned up by a background job after a specified time interval. An attempt was made to access a session that did not exist.

Action: Close all browser instances to ensure that the session cookie is removed. Reopen the browser and log in to the Single Sign-On Server again.
Level: 1

Type: ERROR

Impact: Other

WWC-35006: unable to obtain session information from the cookie

Cause: An error was encountered while decrypting the Oracle Portal session cookie.

Action: Close all browser instances to ensure that the session cookie is removed. Reopen the browser and log in to the Single Sign-On Server again.
Level: 1

Type: ERROR

Impact: Other

WWC-35009: an unexpected error; error message: %1

Cause: An unexpected exception occurred. The error message may provide further details.

Action: Review the information in the error message and take appropriate corrective action.
Level: 1

Type: ERROR

Impact: Other

WWC-35026: The proxy was not found.

Cause: The parameters specified to locate the proxy were not correct.

Action: Check the parameters and provide the correct values.
Level: 1

Type: ERROR

Impact: Other

WWC-35038: A proxy with the specified name already exists.

Cause: A proxy with the specified already existed.

Action: Either use the existing proxy or specify a different proxy name.
Level: 1

Type: ERROR

Impact: Other

WWC-35039: The session context cannot be restored because the session is marked as inactive.

Cause: The session cookie contained a session reference marked as inactive.

Action: Close all browser instances to ensure that the session cookie is removed. Reopen the browser and log in to the Oracle Single Sign-On Server again.
Level: 1

Type: ERROR

Impact: Other

WWC-35040: The session context cannot be restored because the cookie value does not match the value stored in the session repository.

Cause: The session cookie was not consistent with the user session in the repository.

Action: Close all browser instances to ensure that the session cookie is removed. Reopen the browser and log in to the Oracle Single Sign-On Server again.
Level: 1

Type: ERROR

Impact: Other

WWC-35041: This API can be used only in non-Web sessions.

Cause: An attempt was made to call an API from a browser session, but the API was designated to be called from a SQL session.

Action: Check whether the API being called is meant for SQL sessions only. Do not call such APIs from a browser session.
Level: 1

Type: ERROR

Impact: Other

WWC-35042: The Globalization Support language code specified is not valid.

Cause: The language abbreviation specified was invalid.

Action: Specify a correct language abbreviation.
Level: 1

Type: ERROR

Impact: Other

WWC-35043: The value for the Globalization Support territory specified is not valid.

Cause: The territory specified was invalid.

Action: Specify a correct territory.
Level: 1

Type: ERROR

Impact: Other

WWC-38164: error while displaying the Navigator

Cause: An internal error occurred while generating the list of objects to display in the Navigator. This may be because the requested object has been deleted, or some other internal error.

Action: Click the Navigator link at the top of the screen. If that does not solve the problem, restart the browser and try again.
Level: 1

Type: ERROR

Impact: Other

WWC-40018: General invalidation message processing exception: %1

Cause: One of the following occurred: <ol> <li>An error occurred when an invalidation message was sent. This can occur when Oracle Web Cache goes down, or is stopped while Oracle Portal writes an invalidation message to the Oracle Web Cache invalidation port. </li> <li>Some other unexpected exception occurred while processing an invalidation message.</li> </ol>

Action: Ensure that Oracle Web Cache is running and the invalidation port is accepting connections.
Level: 1

Type: ERROR

Impact: Other

WWC-40019: cannot open Oracle Web Cache connection

Cause: Oracle Portal was not able to send the invalidation message to Oracle Web Cache. This can happen if one or more of the following occurred: <ol> <li>There was a problem in connecting to Oracle Web Cache from the host running the Portal database. An intermittent network issue could have caused this error. Or, the Oracle Web Cache host cannot be reached. Verify that the Portal database host can consistently resolve and ping the Oracle Web Cache host. If a firewall exists between the two hosts, ensure that the firewall allows invalidation messages to pass through.</li> <li>Oracle Web Cache was not running. It might have been stopped, or restarted at the time when the invalidation messages were sent by Oracle Portal or providers. Or, Oracle Web Cache might have failed.</li> <li>Oracle Web Cache invalidation port problems were encountered. This can happen if the Oracle Web Cache invalidation port value used by Oracle Portal is different from the actual Oracle Web Cache invalidation port. Try restarting the Oracle Portal OC4J instance to see if this helps.</li> <li>Another process used the Oracle Web Cache invalidation port before Oracle Web Cache started listening on it.</li> <li>Issues with the Oracle Web Cache invalidation password were encountered. Possibly, the Oracle Web Cache invalidator password value in Oracle Portal was different from the actual Oracle Web Cache invalidator password.</li> </ol>

Action: Verify the cause of this behavior and take the appropriate corrective action.
Level: 1

Type: ERROR

Impact: Other

WWC-40064: Error invalidating content: Invalid user name/password passed to Oracle Web Cache

Cause: The invalidation failed because an incorrect user name or password was used while contacting Oracle Web Cache.

Action: Try restarting Oracle Portal's OC4J instance (oc4j_portal) to see if it helps resolve the issue.
Level: 1

Type: ERROR

Impact: Other

WWC-40065: Error closing HTTP connection: Timeout while communicating with Web Cache to send an invalidation

Cause: The invalidation failed because of a timeout that occurred while Oracle Portal was attempting to read the response from Oracle Web Cache.

Action: Ensure that there is no network issue between Oracle Portal and Oracle Web Cache. Also, check whether the Oracle Web Cache process is not responding.
Level: 1

Type: ERROR

Impact: Other

WWC-41031: unable to connect to the LDAP server

Cause: The connection parameters required for connecting to the Oracle Internet Directory server were not available.

Action: Use the APIs "wwsec_oid.get_oid_host" and "wwsec_oid.get_oid_port" to verify that the preference store values for Oracle Internet Directory parameters exist and are valid. If necessary, run the command-line script ptlasst in MIDTIER mode to configure the Oracle Internet Directory connection parameters: ptlasst.csh -mode MIDTIER -type OID
Level: 1

Type: ERROR

Impact: Other

WWC-41078: The user you are trying to create already exists.

Cause: The user name specified already existed in Oracle Internet Directory.

Action: Enter a different user name.
Level: 1

Type: ERROR

Impact: Other

WWC-41082: E-mail is a mandatory field. You must specify its value.

Cause: The e-mail field was not populated.

Action: Enter an e-mail address for the user.
Level: 1

Type: ERROR

Impact: Other

WWC-41083: The user lacks permission to perform this operation.

Cause: An attempt was made to perform an action for which the user did not have sufficient privileges.

Action: Contact the portal administrator and request that the necessary privileges be granted to perform this task.
Level: 1

Type: ERROR

Impact: Other

WWC-41084: A user name is required to proceed to the next step.

Cause: No user name was provided.

Action: Enter a valid user name in the Username field.
Level: 1

Type: ERROR

Impact: Other

WWC-41094: unable to save default group - %1

Cause: An error occurred while setting the default group for a given user.

Action: Verify that the specified default group exists and the user has the necessary privileges to access this group.
Level: 1

Type: ERROR

Impact: Other

WWC-41223: Enter a group name.

Cause: The group name field was empty.

Action: Enter a group name.
Level: 1

Type: ERROR

Impact: Other

WWC-41227: unauthorized to perform the operation

Cause: An attempt was made to perform a task on a group, but the user did not have ownership, or the appropriate privileges to perform that task.

Action: Contact the portal administrator. Either request to be added to the group's OWNER list, or that the necessary privileges be granted to perform the task.
Level: 1

Type: ERROR

Impact: Other

WWC-41228: group not found

Cause: An attempt was made to access a group, but the specified group was not found.

Action: Verify the name of the group.
Level: 1

Type: ERROR

Impact: Other

WWC-41229: The user does not have permission to perform this operation.

Cause: An attempt was made to perform a task, but the user had insufficient privileges to perform the action.

Action: Contact the portal administrator. Request the necessary privileges be granted to perform the task.
Level: 1

Type: ERROR

Impact: Other

WWC-41239: You are not an owner of this group.

Cause: An attempt was made to perform a task on a group, but the user did not have ownership, or the privilege to perform that task.

Action: Contact the portal administrator. Either request to be added to the group's OWNER list, or that the necessary privileges be granted to perform the task.
Level: 1

Type: ERROR

Impact: Other

WWC-41358: This group cannot be deleted or there is no such group found.

Cause: One of the following occurred: <ol> <li>An attempt was made to delete a special group, such as the DBA or PORTAL_ADMIN group.</li> <li>The specified group profile did not exist in Oracle Internet Directory.</li> </ol>

Action: Check the details of the group to be deleted.
Level: 1

Type: ERROR

Impact: Other

WWC-41359: The schema owner cannot be deleted.

Cause: An attempt was made to delete the schema owner, but the schema owner cannot be deleted.

Action: Check the details of the user to be deleted.
Level: 1

Type: ERROR

Impact: Other

WWC-41401: The group exists already.

Cause: An attempt was made to add a group, but a group with the specified name already existed.

Action: Either use the existing group, or specify a different group name.
Level: 1

Type: ERROR

Impact: Other

WWC-41402: There is no such group.

Cause: An attempt was made to access a group that did not exist.

Action: Check the name of the group required. If available, use the popup list to specify the group name.
Level: 1

Type: ERROR

Impact: Other

WWC-41404: The specified manager does not exist.

Cause: The manager specified for a given user did not exist.

Action: Verify that the manager specified for the given user is correct. If available, use the popup list to specify the manager's name.
Level: 1

Type: ERROR

Impact: Other

WWC-41405: already a member of the group

Cause: An attempt was made to add a user (or group) to a given group, but the specified user (or group) was already a member of that group.

Action: Check the name of the user (or group) being added.
Level: 1

Type: ERROR

Impact: Other

WWC-41406: The specified user does not exist.

Cause: An attempt was made to access a user that did not exist.

Action: Check the name of the specified user. If the name is available, select the user from the list.
Level: 1

Type: ERROR

Impact: Other

WWC-41408: There are no accessible objects.

Cause: There are no objects on which the specified privileges have been granted to the given user.

Action: Verify that the criteria specified are correct.
Level: 1

Type: ERROR

Impact: Other

WWC-41409: invalid value specified

Cause: An attempt was made to call the API using invalid parameter values.

Action: Check the values for the parameters.
Level: 1

Type: ERROR

Impact: Other

WWC-41410: The specified site does not exist.

Cause: An attempt was made to access a site, but the specified site ID did not exist.

Action: Check the ID of the site specified.
Level: 1

Type: ERROR

Impact: Other

WWC-41413: The user ID does not exist.

Cause: An attempt was made to access a user, but the specified user ID did not exist.

Action: Check the ID of the user specified.
Level: 1

Type: ERROR

Impact: Other

WWC-41415: The user does not have permission to perform this operation.

Cause: An attempt was made to perform an operation, but the user did not have sufficient privileges. This error message was displayed in Oracle Portal when viewing pages, or editing page layout or style.

Action: Log in to Oracle Portal as a user with privileges to perform the operation. Alternatively, contact the portal administrator to request that the necessary privileges be granted.
Level: 1

Type: ERROR

Impact: Other

WWC-41417: Unexpected error encountered in %0 (%1)

Cause: An unexpected error was encountered.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWC-41419: Authentication failure. Try again.

Cause: An attempt was made to log in with incorrect password or user name details.

Action: Log in again using a valid user name and password combination. If your password is case-sensitive, enter the correct case for your password.
Level: 1

Type: ERROR

Impact: Other

WWC-41426: There is no such user or group found. Enter the name of a valid user or group and try again.

Cause: While creating or editing a page, an invalid user or group name was specified when attempting to set access privileges for the page.

Action: Verify that the name for the user or group is valid. If necessary, use the popup list to specify the user or group name.
Level: 1

Type: ERROR

Impact: Other

WWC-41428: Adding the group as a member would result in a circular reference.

Cause: An attempt was made to add a group as a member to itself.

Action: Verify that the group being added as a member is different from the group to which it is being added.
Level: 1

Type: ERROR

Impact: Other

WWC-41430: Invalid group name. Group names should not exceed 50 characters.

Cause: An attempt was made to enter an invalid group name.

Action: Verify that the specified group name is less than 50 characters in length, or less than 255 bytes in length (for multibyte character set databases).
Level: 1

Type: ERROR

Impact: Other

WWC-41432: The description exceeds 500 characters. Group descriptions must be 500 characters or less.

Cause: The group description specified was too long.

Action: Enter a group description that is less than 500 characters in length.
Level: 1

Type: ERROR

Impact: Other

WWC-41433: Specify an appropriate database user name. It should be an existing proxy client to %1. The proxy client must not be the Oracle Portal schema itself.

Cause: When editing a user, an attempt was made to assign a database schema to the user's account but the specified database schema has not been granted connect privileges to the Portal schema.

Action: Use the Schema portlet to create a new schema that can be assigned to users. Select the "Use this Schema for Portal Users" check box. To edit an existing schema for this purpose, select Edit Schema in the Schema portlet.
Level: 1

Type: ERROR

Impact: Other

WWC-41438: Login is not possible because the login URL being retrieved for this application is not a fully qualified URL. Notify the portal administrator.

Cause: Oracle Portal was unable to construct the URL required to redirect to the Oracle Single Sign-On Server. Partner application information may not be configured correctly.

Action: Contact the portal administrator and request that Oracle Portal be reregistered with the Oracle Single Sign-On Server.
Level: 1

Type: ERROR

Impact: Other

WWC-41439: Login is not possible because there is either invalid or no configuration information stored in the enabler configuration table (WWSEC_ENABLER_CONFIG_INFO$).

Cause: One of the following occurred: <ol> <li>An alias defined in the Apache configuration caused Apache to translate host.example.com to just host. If this is the case, the Login link will show only host:port (dropping the domain).</li> <li>The default domain was not set in the Apache configuration. When this occurs, only the host name is shown in the Login link and the domain is not included.</li> <li>Oracle Portal was configured with an incorrect host or port.</li> </ol>

Action: Do one of the following: <ol> <li>Remove all such aliases from the Apache configuration.</li> <li>Include the domain in the ServerName paramenter.</li> <li>Fix the Host in the IASInstance element and ListenPort in the WebCacheComponent element in iasconfig.xml and run ptlconfig -dad portal -site. The ptlconfig script and the iasconfig.xml file are usually located in the directory portal/conf under the Oracle Portal and Oracle Wireless middle-tier home.</li> </ol> NOT USED
Level: 1

Type: ERROR

Impact: Other

WWC-41440: You cannot log in because there is an error trying to parse the login URL for this application.

Cause: A login request was made using a very long URL.

Action: Check the URL and reduce its length if it appears to be too long. There is no theoretical limit for the length of the URLs.
Level: 1

Type: ERROR

Impact: Other

WWC-41441: unable to process the login request

Cause: The login URL was not constructed successfully. The reason is unknown. This problem could occur if Oracle Portal was unable to communicate with another component.

Action: Ensure that all components in the system are configured properly, are up and running, and are functioning correctly.
Level: 1

Type: ERROR

Impact: Other

WWC-41443: %1, you have logged in to the Oracle Single Sign-On Server, but you are not authorized to log in to Oracle Portal. See your portal administrator to enable logins for your account.

Cause: The option 'Allow User to Log On' was not selected for this user. The user may log in to Oracle Single Sign-On, but not Oracle Portal.

Action: Contact the portal administrator. Request that the 'Allow User to Log On' option is selected for this user.
Level: 1

Type: ERROR

Impact: Other

WWC-41446: The system failed to initialize the necessary HTTP request to the Oracle Single Sign-On Server.

Cause: The Oracle Single Sign-On Server was not running.

Action: Check whether the Oracle Single Sign-On Server is up and running.
Level: 1

Type: ERROR

Impact: Other

WWC-41447: The system failed to retrieve the necessary HTTP request to the SSO Server.

Cause: This error occurs in the following cases: <ol> <li>The Oracle Single Sign-On Server was not operational. <li>There was an incorrect Querypath Url Prefix in the Oracle Single Sign-On Server settings.</li> </ol>

Action: Do one of the following: <ol> <li>Check whether the Oracle Single Sign-On Server is up and running. </li> <li>Verify the Querypath Url Prefix in the Oracle Single Sign-On Server settings.</li> </ol>
Level: 1

Type: ERROR

Impact: Other

WWC-41450: An invalid or null argument was passed into this routine.

Cause: An invalid or null argument was passed into this routine.

Action: Check that valid parameter values are passed to this routine.
Level: 1

Type: ERROR

Impact: Other

WWC-41451: There is no external application user name mapping for the given user and the given application.

Cause: There was no external application user name mapping for the given user and the given application.

Action: Log in to the external application and save the login credentials in the password store by selecting the 'Remember My Login Information' check box on the application login screen.
Level: 1

Type: ERROR

Impact: Other

WWC-41452: The address from which this authentication request was made, does not match your IP address. Notify your administrator if you believe this message to be in error.

Cause: The system had IP address checking enabled and the IP address from the the client did not match the IP address associated with the original authentication. Using a proxy server can cause this problem.

Action: Disable IP address checking if a proxy server is being used.
Level: 1

Type: ERROR

Impact: Other

WWC-41453: The cookie version specified in the authentication message is not supported by this configuration. Notify your administrator.

Cause: The Oracle Single Sign-On Server does not support the version of the URLC token specified in the partner application configuration.

Action: Contact the portal administrator. Request that Oracle Portal be reregistered with the Oracle Single Sign-On Server.
Level: 1

Type: ERROR

Impact: Other

WWC-41454: The decryption of the authentication information was unsuccessful. This may be caused by data inconsistency, an incorrect encryption key in this application's configuration, or an invalid access attempt. Notify your administrator.

Cause: The URCL token received from the Oracle Single Sign-On Server was not decrypted.

Action: Contact the portal administrator to ensure that the Oracle Portal configuration is correct. Request that Oracle Portal be reregistered with the Oracle Single Sign-On Server if required.
Level: 1

Type: ERROR

Impact: Other

WWC-41470: Error while connecting to the Oracle Internet Directory.

Cause: The Oracle Internet Directory Server might not have been operational.

Action: Contact the portal administrator to ensure that the Oracle Internet Directory Server is operational.
Level: 1

Type: ERROR

Impact: Other

WWC-41471: Multiple groups with the given name were found in the directory. The group cannot be resolved uniquely.

Cause: Multiple groups with the given name were found in the directory.

Action: Use the popup list next to the name field to find the group name.
Level: 1

Type: ERROR

Impact: Other

WWC-41472: This API is deprecated.

Cause: An attempt was made to use a deprecated API.

Action: Check the latest API documentation for alternatives to this API.
Level: 1

Type: ERROR

Impact: Other

WWC-41496: unable to refresh the cache for OID parameters

Cause: The Oracle Internet Directory Server might not have been operational.

Action: Check whether the Oracle Internet Directory port is operational and that the Oracle Portal configuration is referring to the correct host name and port. Use the command-line script 'ldapbind' to check if the LDAP port is up and running.
Level: 1

Type: ERROR

Impact: Other

WWC-41610: The list of External Applications is too large.

Cause: The list of External Applications returned from the Oracle Single Sign-On Server was too large.

Action: Try reducing the character length of External Application names by renaming them.
Level: 1

Type: ERROR

Impact: Other

WWC-41611: The Enabler Configuration is missing.

Cause: The Partner Application domain was not correctly set in the Oracle Single Sign-On Server configuration.

Action: Run the command-line script ptlasst in MIDTIER mode to configure the Oracle Single Sign-On Server: ptlasst -mode MIDTIER -type SSO NOT USED
Level: 1

Type: ERROR

Impact: Other

WWC-41657: Your account is locked. Ask your administrator to reset the password.

Cause: The number of attempts to log in with an incorrect password exceeded the maximum number allowed.

Action: Contact your administrator to reset your password.
Level: 1

Type: ERROR

Impact: Other

WWC-41742: There is a conflict with your assigned user name. There is a user entry with this name, but with a different globally unique identifier, which must be resolved before you can log on with this name. Notify your administrator.

Cause: One or both of the following occurred: <ol> <li>Oracle Single Sign-On was using a stale user entry from its cache when transmitting user data to the Oracle Portal repository.</li> <li>The user profile for the specified user name already existed in the Oracle Portal schema, but it contained an incorrect globally unique identifier.</li> </ol>

Action: Contact the portal administrator to restart Oracle Single Sign-On after diabling its cache. If the problem persists, then request the portal administrator to delete the existing local user profile using the wwsec_api.delete_portal_user API. Then, log in using that user's credentials.
Level: 1

Type: ERROR

Impact: Other

WWC-41743: An exception is raised when accessing the Oracle Internet Directory: %1.

Cause: An attempt was made to access the Oracle Internet Directory.

Action: Refer to the additional information (if any) displayed with this error message and take the appropriate action. Contact your portal administrator if additional information is not available.
Level: 1

Type: ERROR

Impact: Other

WWC-41744: You do not have permission to perform this operation in the Oracle Internet Directory (error status: %1).

Cause: An attempt was made to perform an action in the Oracle Internet Directory without sufficient access privileges.

Action: Contact the portal administrator and request the necessary privileges be granted to perform this task.
Level: 1

Type: ERROR

Impact: Other

WWC-41745: An entry is not found in the Oracle Internet Directory (error status: %1).

Cause: An attempt was made to access an Oracle Internet Directory entry that did not exist.

Action: Check the value of the Oracle Internet Directory entry being accessed.
Level: 1

Type: ERROR

Impact: Other

WWC-41746: A value is not found in the Oracle Internet Directory (error status: %1).

Cause: An attempt was made to search for an attribute value that did not exist in the specified directory entry.

Action: Verify that the name of the attribute being searched is correct.
Level: 1

Type: ERROR

Impact: Other

WWC-41747: Multiple matches are found for the specified criteria in the Oracle Internet Directory (error status: %1).

Cause: Multiple matches were found for the specified criteria in the Oracle Internet Directory.

Action: Verify that the specified search criteria are correct.
Level: 1

Type: ERROR

Impact: Other

WWC-41748: The specified entry or value already exists in the Oracle Internet Directory (error status: %1).

Cause: An attempt was made to do one of the following: <ol> <li>Add a user or group entry in Oracle Internet Directory that already existed.</li> <li>Add an owner/member to a group that has already been added.</li> </ol>

Action: Check the name of the user or group that is being added. Check it either as an owner, or as a member of a group.
Level: 1

Type: ERROR

Impact: Other

WWC-41755: No portlet is specified.

Cause: An attempt was made to call a portlet with an invalid reference.

Action: Remove the portlet and then add it again.
Level: 1

Type: ERROR

Impact: Other

WWC-41778: Delegated Administration Service (DAS) is not configured properly. Contact the administrator.

Cause: The DAS operation base URL was not specified in the Oracle Internet Directory.

Action: Specify the DAS operation base URL in the Oracle Internet Directory and refresh the Oracle Internet Directory cache in the repository.
Level: 1

Type: ERROR

Impact: Other

WWC-41780: The system failed to process the HTTPS request to the SSO Server to retrieve the list of external applications.

Cause: The wallet parameters were not available.

Action: Specify a valid wallet path and wallet password to access the external application information from the Oracle Single Sign-On Server using HTTPS.
Level: 1

Type: ERROR

Impact: Other

WWC-41781: The system failed to process the HTTPS request to the SSO Server with specified wallet details.

Cause: The Oracle Single Sign-On Server could not be reached using the given Query Path URL Prefix and the specified wallet parameters.

Action: Verify that the Query Path URL Prefix, wallet path, and wallet password are correct and that the Oracle Single Sign-On Server is up and running.
Level: 1

Type: ERROR

Impact: Other

WWC-41875: No external applications are registered in the Oracle AS Single Sign-On Server.

Cause: No external application existed.

Action: Add an external application. Portal administrators with single sign-on administrator privileges can add external applications.
Level: 1

Type: ERROR

Impact: Other

WWC-41876: No external applications are selected for display. To select applications to display, click \"Personalize\".

Cause: One of the following occurred: <ol> <li>The portlet was customized to hide all external applications.</li> <li>No external applications existed.</li> </ol>

Action: Do one of the following: <ol> <li>Display one or more applications in the portlet.</li> <li>Add an external application. Portal administrators with single sign-on administrator privileges can add external applications.</li> </ol>
Level: 1

Type: ERROR

Impact: Other

WWC-41932: The specified user already exists. Specify a different user name.

Cause: An attempt was made to create a user that already existed in Oracle Internet Directory.

Action: Specify a different user name.
Level: 1

Type: ERROR

Impact: Other

WWC-41934: An error occurred when attempting to set the default group.

Cause: One of the following occurred: <ol> <li>An attempt was made to assign a group as the default group when the user was not a member of that group.</li> <li>The user did not have sufficient privileges to perform this task.</li> <li>An error occurred while accessing the Oracle Internet Directory.</li> </ol>

Action: Ensure that the user is already a member of the group when it is assigned as the default group. Report the error to your portal administrator and request that the appropriate privileges be granted if needed.
Level: 1

Type: ERROR

Impact: Other

WWC-41935: An error occurs when attempting to set the default page.

Cause: An attempt was made to set the default page, but the specified page did not exist.

Action: Specify a valid default page name.
Level: 1

Type: ERROR

Impact: Other

WWC-41937: Password is a mandatory field. You must specify its value.

Cause: A password was not specified.

Action: Specify a password for the user.
Level: 1

Type: ERROR

Impact: Other

WWC-41947: User Name is a mandatory field. You must specify its value.

Cause: A user name was not specified.

Action: Specify a user name.
Level: 1

Type: ERROR

Impact: Other

WWC-41948: Confirm Password is a mandatory field. You must specify its value.

Cause: The password was not confirmed.

Action: Reenter the password to ensure that it was entered correctly.
Level: 1

Type: ERROR

Impact: Other

WWC-41966: The preference store is missing the name of the schema required to perform this operation. Unable to continue.

Cause: The name of the Oracle Single Sign-On schema is not available in the preference store.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWC-41974: You cannot access this screen because the enabler configuration is missing.

Cause: An attempt was made to construct the URL required to access the Oracle Single Sign-On Server but the enabler configuration was not found. This can occur if the host or port information stored in the enabler configuration is removed after the user logged in.

Action: Contact the portal administrator. Request that Oracle Portal be reregistered with the Oracle Single Sign-On Server. NOT USED
Level: 1

Type: ERROR

Impact: Other

WWC-42001: A null name is supplied. Supply a valid attribute name.

Cause: A null value was provided for a required attribute.

Action: Specify an appropriate value for the attribute.
Level: 1

Type: ERROR

Impact: Other

WWC-43002: You do not have permission to perform this operation.

Cause: An attempt was made to perform an action for which the user had insufficient privileges.

Action: Contact the portal administrator and request that the necessary privileges be granted to perform this task.
Level: 1

Type: ERROR

Impact: Other

WWC-43007: There are no entities in cache to invalidate.

Cause: A message was sent to Oracle Web Cache to invalidate an object, but the object was not found.

Action: No action required.
Level: 1

Type: ERROR

Impact: Other

WWC-43100: A provider with this name is already registered.

Cause: An attempt was made to register a provider, but the name specified has already been used.

Action: Specify a different provider name.
Level: 1

Type: ERROR

Impact: Other

WWC-43101: This provider is not found.

Cause: A provider with the name specified could not be found.

Action: Ensure that you entered the name correctly, or use the Navigator to find the provider you require.
Level: 1

Type: ERROR

Impact: Other

WWC-43102: The name field is empty.

Cause: A name for the provider was not specified.

Action: Specify a provider name.
Level: 1

Type: ERROR

Impact: Other

WWC-43103: The name field exceeds the maximum length.

Cause: The provider name specified was too long.

Action: Enter a provider name that is less than 200 characters in length.
Level: 1

Type: ERROR

Impact: Other

WWC-43105: The owning schema field is empty.

Cause: An owning schema was not specified. This field is mandatory for database providers.

Action: Enter an owning schema.
Level: 1

Type: ERROR

Impact: Other

WWC-43106: Schema %1 was not found.

Cause: The schema entered was not found.

Action: Enter a valid schema name.
Level: 1

Type: ERROR

Impact: Other

WWC-43107: The package name field is empty.

Cause: The package name was not specified. This field is mandatory for database providers.

Action: Enter a package name.
Level: 1

Type: ERROR

Impact: Other

WWC-43109: The package name exceeds the maximum length.

Cause: The specified package name was too long.

Action: Enter a package name that is less than 2000 characters in length.
Level: 1

Type: ERROR

Impact: Other

WWC-43112: The timeout must be left blank or be a positive value.

Cause: The specified timeout value was a negative value.

Action: Either leave the timeout blank or enter a positive value.
Level: 1

Type: ERROR

Impact: Other

WWC-43113: The value for login frequency is not valid.

Cause: An invalid value for the login frequency was specified.

Action: Set the login frequency to one of: Once, Always, Never or Public.
Level: 1

Type: ERROR

Impact: Other

WWC-43116: The specified node is not found.

Cause: It was not possible to find the local portal node record.

Action: Contact the portal administrator and report this error. This error indicates data inconsistencies in the portal instance.
Level: 1

Type: ERROR

Impact: Other

WWC-43132: The implementation package is not in a valid state.

Cause: A PL/SQL package implementing a provider was in an 'INVALID' state. For example, the PL/SQL package may contain a syntax error, or reference a missing or invalid object.

Action: Recompile the PL/SQL package. If the compilation fails, resolve the errors reported.
Level: 1

Type: ERROR

Impact: Other

WWC-43133: The implementation package is not found.

Cause: A PL/SQL package or package body implementing a provider was not found.

Action: Ensure that the schema and package name specified for the provider is correct and that the PL/SQL package has been created in the specified schema.
Level: 1

Type: ERROR

Impact: Other

WWC-43134: An error occurred when attempting to call the providers register function.

Cause: An attempt was made to register a provider.

Action: Ensure that the provider is operational, and that the registration details are correct.
Level: 1

Type: ERROR

Impact: Other

WWC-43135: The Web URL for Web implementations is not valid.

Cause: The URL specified for the Web provider was not valid, or was null.

Action: Specify the correct Web provider URL.
Level: 1

Type: ERROR

Impact: Other

WWC-43137: An HTTP proxy is indicated but the proxy is invalid.

Cause: It was specified that this provider required a proxy, but the proxy definition provided was invalid.

Action: Verify the proxy settings in the Global Settings page.
Level: 1

Type: ERROR

Impact: Other

WWC-43139: The Web application type is invalid.

Cause: The Web provider had an invalid value for the HTTP application type.

Action: Ensure that the HTTP application type is one of EXTERNAL_SECURED, PORTAL or null. Constants are defined for these values in the WWPRO_API_PROVIDER_REGISTRY public API package.
Level: 1

Type: ERROR

Impact: Other

WWC-43140: The Web external application ID is invalid.

Cause: The external application ID specified was not valid.

Action: Use the list of values provided to select a valid value, or leave this field blank.
Level: 1

Type: ERROR

Impact: Other

WWC-43141: The following error occurs when converting \"%1\" into an integer: %2

Cause: An attempt was made to convert a string into a number.

Action: Review the reported error and take the appropriate action.
Level: 1

Type: ERROR

Impact: Other

WWC-43144: The following error occurs when converting \"%1\" into a date: %2

Cause: An attempt was made to convert a string into a date.

Action: Review the reported error and take the appropriate action.
Level: 1

Type: ERROR

Impact: Other

WWC-43145: The value \"%1\" is not a valid content type.

Cause: The specified portlet content type was invalid.

Action: Ensure that the portlet's content type is one of text/html or text/xml.
Level: 1

Type: ERROR

Impact: Other

WWC-43146: The specified shared key is not valid.

Cause: The specified shared key was not valid.

Action: Enter a key that is between 10 and 30 characters in length.
Level: 1

Type: ERROR

Impact: Other

WWC-43147: The following error occurs during the call to Web provider: %1

Cause: A call to the Web provider failed with the specified error.

Action: Review the reported error and take the appropriate action.
Level: 1

Type: ERROR

Impact: Other

WWC-43167: The specified name is invalid. Names are alphanumeric and cannot contain spaces or special characters.

Cause: An invalid name was specified.

Action: Enter a name that contains only letters, numbers, and underscores.
Level: 1

Type: ERROR

Impact: Other

WWC-43169: This provider cannot be deleted.

Cause: An attempt was made to delete a provider that was offline or could not be deleted.

Action: If the provider is offline, make it online before attempting to delete it.
Level: 1

Type: ERROR

Impact: Other

WWC-43176: The provider URL specified may be wrong or the provider is not running.

Cause: Oracle Portal could not contact the provider because the URL specified was either incorrect or the provider was not running.

Action: Verify that the URL specified during provider registration is correct and that the provider is up and running. One way to verify this for a Web provider is to enter the URL in a browser. If the provider information is correct and the provider is up, the provider's test page is displayed. If the URL is correct and the provider is up, there may be a problem with the configuration of the portal repository. Contact the portal administrator to enable debug logging in the portal repository and view the log information.
Level: 1

Type: ERROR

Impact: Other

WWC-43183: The portlet ID and portlet name must be unique within a provider.

Cause: An attempt was made to register a provider that contains portlets and the portlet names or portlet IDs were not unique within that provider.

Action: Contact the developer responsible for the provider and request that this issue be resolved.
Level: 1

Type: ERROR

Impact: Other

WWC-43184: invalid portlet ID

Cause: The portlet ID was invalid or null.

Action: Contact the developer responsible for the provider and request that this issue be resolved.
Level: 1

Type: ERROR

Impact: Other

WWC-43185: The portlet ID value of %1 is invalid. The portlet ID must be in the range -2147483648 to 2147483648.

Cause: A portlet ID was not in a valid range.

Action: Contact the developer responsible for the provider and request that this issue be resolved.
Level: 1

Type: ERROR

Impact: Other

WWC-43186: The portlet name for portlet with ID=%1 is null. The portlet name cannot be null.

Cause: A portlet name was null.

Action: Contact the developer responsible for the provider and request that this issue be resolved.
Level: 1

Type: ERROR

Impact: Other

WWC-43187: The portlet name '%1' contains space characters. The portlet name should not contain any space characters.

Cause: A portlet name contained space characters.

Action: Contact the developer responsible for the provider and request that this issue be resolved.
Level: 1

Type: ERROR

Impact: Other

WWC-43188: You have registered this Web provider with the \"Same Cookie Domain\" check box selected.

Cause: Cookies created by this provider were forwarded to the user's browser and managed by the browser instead of Oracle Portal. After being managed by the browser, the cookies were sent to any other Web server that: <ol> <li>Was accessed within the same browser session.</li> <li>Fell within the relaxed scope specified when the cookie was created. </li> </ol>

Action: This can result in cookie collisions and errors or loss of sessions in unrelated Web applications. To minimize the possibility of cookie collisions, ensure that: <ol> <li>Any custom cookies created by the Web provider have names that are unique to that Web provider.</li> <li>All portal instances accessed using the Federated Portal Adapter are configured with different DAD names.</li> <li>PDK-Java release 1 (JServ) Web providers requiring this setting are installed in uniquely named JServ servlet zones.</li> <li>PDK-Java release 2 (OC4J) Web providers do not use this setting if they use servlet sessions. This is because the cookie used to identify the session is always called JSESSIONID. This name is specified in the Servlet 2.3 specification. Relaxing the scope of a JSESSIONID cookie will almost certainly cause session-related problems to occur in other, unrelated, Web applications.</li> </ol>
Level: 1

Type: ERROR

Impact: Other

WWC-43190: An error occurs while trying to refresh the provider. The original registration cannot be found.

Cause: The provider URL used for the registration might not have been a valid URL or was not accessible.

Action: Ensure that the provider URL is valid and properly accessible from portal.
Level: 1

Type: ERROR

Impact: Other

WWC-43192: The provider package name %1 is reserved for internal use and cannot be used for registering a provider.

Cause: The specified package name is reserved for internal use by Oracle Portal. Users cannot use it for registering providers.

Action: Specify a different package name.
Level: 1

Type: ERROR

Impact: Other

WWC-43220: The signature key password field is empty.

Cause: The signature key password was not specified.

Action: Specify the signature key password.
Level: 1

Type: ERROR

Impact: Other

WWC-43255: Registration handle cannot be null.

Cause: The registration handle used to refer to the registration of the provider in all provider communications was not present.

Action: Check whether the provider has a registration port. If a registation port exists, contact the provider administrator and request that the provider supply the necessary registration handle. If the provider expects an out-of-band registration handle, supply the value of the handle in the Connection tab.
Level: 1

Type: ERROR

Impact: Other

WWC-43256: Registration handle length exceeds 255 characters.

Cause: The length of the registration handle generated or supplied for this registration exceeded 255 characters.

Action: If you supplied the value for the registration handle as an out-of-band registration handle, provide a value that is less than 255 characters in length. If the registration handle is generated by the provider, contact the WSRP provider administrator.
Level: 1

Type: ERROR

Impact: Other

WWC-43257: Portlet handle cannot be null.

Cause: The provider did not generate a handle for this portlet, or Oracle Portal failed to store the portlet handle returned by the provider.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWC-43258: Portlet handle length exceeds 255 characters.

Cause: The portlet handle returned by the WSRP provider exceeded 255 characters.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWC-43259: Translations for portlet multivalue attributes cannot be fetched.

Cause: The provider did not return translations for the portlet attributes, or Oracle Portal failed to store them.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWC-43273: An error occurs during the call to the WSRP provider: %1.

Cause: A problem occurred while getting the service description. This may be because the provider sent unsupported extensions.

Action: Try turning off extensions on the producer side or contact the WSRP provider administrator or portal administrator.
Level: 1

Type: ERROR

Impact: Other

WWC-43274: Markup types for the WSRP provider portlet \"%1\" [Provider ID: %2] are not found in the Portlet Medatada Repository.

Cause: If the WSRP provider's WSDL URL has changed, this might have caused existing portlets to be replaced with the portlets of the new provider. If the WSDL URL has not changed, there could be some data inconsistency.

Action: Check for changes in the WSRP provider's registration URL. If the URL has not changed, try reregistering the provider.
Level: 1

Type: ERROR

Impact: Other

WWC-43275: The Web Service URL is either empty or not properly formed.

Cause: The Web Service URL might be empty or it was not formed properly.

Action: Provide a correct URL or contact the WSRP provider administrator.
Level: 1

Type: ERROR

Impact: Other

WWC-43277: The producer URL specified may be wrong or the producer is not running.

Cause: The URL specified was either incorrect or the producer was not running. This caused a problem when Oracle Portal tried to contact the producer using that URL.

Action: Verify that the URL specified for the producer registration is correct and that the producer is up and running. One way to verify this is to enter the registration URL in a browser. If the URL is correct and the producer is up and running, you will see the producer's WSDL document.
Level: 1

Type: ERROR

Impact: Other

WWC-43295: The default user field is empty.

Cause: A default user was not specified.

Action: Specify a default user.
Level: 1

Type: ERROR

Impact: Other

WWC-43296: The issuer name field is empty.

Cause: An issuer name was not specified.

Action: Specify an issuer name.
Level: 1

Type: ERROR

Impact: Other

WWC-43297: The store path field is empty.

Cause: The store path was not specified.

Action: Specify the absolute location of the keystore on the server.
Level: 1

Type: ERROR

Impact: Other

WWC-43298: The store password field is empty.

Cause: The store password was not specified.

Action: Specify the store password.
Level: 1

Type: ERROR

Impact: Other

WWC-43299: The signature key alias field is empty.

Cause: The signature key alias was not specified.

Action: Specify the signature key alias.
Level: 1

Type: ERROR

Impact: Other

WWC-43300: The mode parameter must be MODE_SHOW, MODE_SHOW_ABOUT, MODE_SHOW_EDIT, MODE_SHOW_EDIT_DEFAULTS, MODE_SHOW_DETAILS, MODE_SHOW_HELP, or MODE_PREVIEW.

Cause: A show request was made to a portlet with an invalid show mode.

Action: Ensure that the show mode for the request is one of: MODE_SHOW, MODE_SHOW_ABOUT, MODE_SHOW_EDIT, MODE_SHOW_HELP, MODE_SHOW_EDIT_DEFAULTS, MODE_SHOW_DETAILS, MODE_PREVIEW, or MODE_LINK. Note that these constants are defined in the WWPRO_API_PROVIDER public API.
Level: 1

Type: ERROR

Impact: Other

WWC-43302: get_portlet returns an implementation type other than Database or Web for Portlet %1.%2.

Cause: The portlet returned an invalid implementation type.

Action: Ensure that the portlet implementation type is one of: PLSQL_IMPL or HTTP_IMPL. These constants are defined in the API WWPRO_API_PROVIDER_REGISTRY public API.
Level: 1

Type: ERROR

Impact: Other

WWC-43303: Web portlets can only be displayed in the parallel mode.

Cause: A Web provider portlet was called by the PL/SQL API that was created to show PL/SQL portlets.

Action: Contact the portal administrator. This message indicates data inconsistency.
Level: 1

Type: ERROR

Impact: Other

WWC-43307: The user does not have permission to update the portlets ACL.

Cause: Either an attempt was made to update the portlet's access control list (ACL), or the portlet was offline.

Action: Contact the portal administrator. Request that the required privileges be granted, or ensure that the portlet is online.
Level: 1

Type: ERROR

Impact: Other

WWC-43308: The specified portlet is not found in the Portlet Metadata Repository.

Cause: The specified portlet was not found in the Portlet Metadata Repository. This error suggests data inconsistency.

Action: Refresh the provider that contains the portlet and attempt the operation again.
Level: 1

Type: ERROR

Impact: Other

WWC-43309: You do not have permission to access the portlet called \"%1\" (%2,%3).

Cause: An attempt was made to access the portlet, but the user had insufficient privileges.

Action: Contact the portal administrator. Request access to the portlet be granted.
Level: 1

Type: ERROR

Impact: Other

WWC-43310: The specified portlet's provider is offline.

Cause: An attempt was made to access a portlet, but its provider was offline.

Action: Ensure that the provider is online and attempt the operation again.
Level: 1

Type: ERROR

Impact: Other

WWC-43339: analysis failure of the WSDL

Cause: Parsing of the provided WSDL failed. This could be due to an error entering the URI of the WSDL, or because the WSDL did not describe a valid WSRP service.

Action: Verify that the URI entered is correct, and check with the producer's administrator that the URI is valid.
Level: 1

Type: ERROR

Impact: Other

WWC-43343: Error: Cannot get portlet markup. Try reloading the portlet or the page.

Cause: A request for portlet markup failed.

Action: Try reloading the portlet or the page. Verify that you still have permission to use the portlet and that the producer is running.
Level: 1

Type: ERROR

Impact: Other

WWC-43722: The provider group \"%1\" is not registered.

Cause: The provider group specified was not found in the portal repository.

Action: Ensure that the name of the provider group requested is correct.
Level: 1

Type: ERROR

Impact: Other

WWC-43725: The provider group \"%1\" is already registered with Oracle Portal.

Cause: The provider group specified was already registered with Oracle Portal.

Action: This error suggests data inconsistency. Contact the portal administrator.
Level: 1

Type: ERROR

Impact: Other

WWC-43733: error accessing remote provider group server: %1

Cause: An error occurred while accessing the remote provider group server.

Action: Check the error text, and any subsequent error messages, for specific details.
Level: 1

Type: ERROR

Impact: Other

WWC-43735: The provider group \"%2\" defined by the server at URL \"%1\" is already registered with Oracle Portal.

Cause: An attempt was made to register a provider group but a provider group with the same details had already been registered with Oracle Portal.

Action: Use the provider group previously registered with these details.
Level: 1

Type: ERROR

Impact: Other

WWC-44009: The name is already in use. Recommended Name:%1

Cause: An attempt was made to specify a page or tab name that already existed.

Action: Specify a different name for the page or tab.
Level: 1

Type: ERROR

Impact: Other

WWC-44081: Specify a display name for this style.

Cause: A display name was not specified when creating or copying a style.

Action: Specify a display name for the style.
Level: 1

Type: ERROR

Impact: Other

WWC-44085: This region is already split.

Cause: An attempt was made to split a region that was already split.

Action: Specify a different region, that is, one that is not already split.
Level: 1

Type: ERROR

Impact: Other

WWC-44087: A region with this display name already exists.

Cause: An attempt was made to create a region but a regions with the specified name already existed.

Action: Specify a unique name for the region.
Level: 1

Type: ERROR

Impact: Other

WWC-44089: This region is not found.

Cause: An attempt was made to delete, split, edit, or copy a region but the region could not be found.

Action: Specify a valid region.
Level: 1

Type: ERROR

Impact: Other

WWC-44090: cannot delete the main region

Cause: An attempt was made to delete the main region of the page but the main region cannot be deleted unless the page is deleted.

Action: Specify a different region for deletion.
Level: 1

Type: ERROR

Impact: Other

WWC-44091: Specify a numeric value for the region width.

Cause: An attempt was made to edit the width of a region but a nonnumeric value was specified.

Action: Ensure that the width value is an integer value (preferably between 1 and 100). If the width is a relative width, specify the % symbol (for example, 65%). If the width is an absolute width, specify only the numeric value (for example, 35).
Level: 1

Type: ERROR

Impact: Other

WWC-44102: Specify a display name.

Cause: Name and display name values were not provided for a page.

Action: Specify name and display name values for the page. These values may not be null.
Level: 1

Type: ERROR

Impact: Other

WWC-44131: You do not have permission to perform this operation.

Cause: An attempt was made to perform an operation but the user did not have sufficient privileges.

Action: Log in to Oracle Portal as a user with privileges to perform the operation. Alternatively, contact the portal administrator to request that the necessary privileges be granted.
Level: 1

Type: ERROR

Impact: Other

WWC-44132: error while setting the default page

Cause: An attempt was made to set the default page for a user or group but the operation failed.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWC-44151: This style is not found.

Cause: An attempt was made to access a style but the specified style name and page group ID did not exist.

Action: Provide a valid style name and page group ID.
Level: 1

Type: ERROR

Impact: Other

WWC-44214: The URL specified is invalid.

Cause: The value specified for a URL attribute did not begin with a valid protocol such as http://, https://, or ftp://.

Action: Correct the URL, entering a valid protocol.
Level: 1

Type: ERROR

Impact: Other

WWC-44233: The name is not valid. Valid names contain only alphabetic or numeric characters, plus underscore. No spaces or special characters are allowed. Enter a valid name.

Cause: The name that was entered contained invalid characters.

Action: Specify a different name using only the characters A to Z, a to z, 0 to 9, and underscore (_).
Level: 1

Type: ERROR

Impact: Other

WWC-44234: Page not found.

Cause: An attempt was made to view or edit an Oracle Portal page but the specified page did not exist,

Action: Verify that the specified page name or page ID is correct.
Level: 1

Type: ERROR

Impact: Other

WWC-44250: You do not have permission to move the selected portlets.

Cause: An attempt was made to move one or more portlets, but the user did not have the appropriate privileges.

Action: Log in as a user with Personalize (Full) privileges on the page containing the portlets. Alternatively, add the same portlet to the destination region and hide the portlet in the source region.
Level: 1

Type: ERROR

Impact: Other

WWC-44251: You do not have permission to move the selected objects.

Cause: An attempt was made to move one or more items or portlets, but the user did not have the appropriate privileges.

Action: Log in as a user with either Manage Content privileges on the page containing the item or portlet, or Manage privileges on the item itself. Alternatively, add the same portlet to the destination region and hide the portlet in the source region.
Level: 1

Type: ERROR

Impact: Other

WWC-44258: You do not have permission to move content into the selected region.

Cause: An attempt was made to add content to a region, but the user did not have the appropriate privileges.

Action: Log in as a user with the appropriate privileges to perform the operation.
Level: 1

Type: ERROR

Impact: Other

WWC-44279: The default page for the system cannot be deleted.

Cause: An attempt was made to delete a system default page. Such pages cannot be deleted.

Action: Do not attempt to delete this page.
Level: 1

Type: ERROR

Impact: Other

WWC-44284: error while adding banner for the template

Cause: An attempt was made to set the default navigation page for a page group, but the specified navigation page did not exist.

Action: Select a different navigation page to be the default navigation page for the page group.
Level: 1

Type: ERROR

Impact: Other

WWC-44334: Portlet Information cannot be obtained.

Cause: An attempt to access a portlet failed because the provider or the portlet was not found.

Action: Ensure that the provider is online, the portlet is available, and that the user has permission to access the provider or portlet.
Level: 1

Type: ERROR

Impact: Other

WWC-44366: This page cannot be copied as a JSP file.

Cause: An attempt was made to copy a page that was not a standard page as a JSP file. Only standard pages can be copied as JSP files.

Action: Choose a standard page when copying as a JSP file.
Level: 1

Type: ERROR

Impact: Other

WWC-44552: Specify a numeric value for the space between portlets.

Cause: When editing a region, a nonnumeric value was specified for the "Space between Portlets" field.

Action: Specify an integer value (preferably between 1 and 100) for the "Space between Portlets" field. If no space is required between portlets, specify 0 or null.
Level: 1

Type: ERROR

Impact: Other

WWC-44570: Specify a numeric value for the space around portlets.

Cause: When editing a region, a nonnumeric value was specified for the "Space around Portlets" field.

Action: Specify an integer value (preferably between 1 and 100) for the "Space around Portlets" field. If no space is required around portlets, specify 0 or null.
Level: 1

Type: ERROR

Impact: Other

WWC-44582: error while creating tab

Cause: An attempt to add a tab failed. Either the specified tab name was invalid or the user did not have permission to add a tab.

Action: Specify a valid name for the tab, or ensure that the user has the appropriate privileges to add a tab.
Level: 1

Type: ERROR

Impact: Other

WWC-44583: error while editing tab

Cause: An attempt to edit a tab failed. Either the specified tab name was invalid or the user did not have permission to edit the tab.

Action: Specify a valid name for the tab, or ensure that the user has the appropriate privileges to edit the tab.
Level: 1

Type: ERROR

Impact: Other

WWC-44650: Specify a numeric value for item icon height.

Cause: An invalid value was specified for the Item Icon Height field.

Action: Specify a positive number for the height (in pixels) of item images.
Level: 1

Type: ERROR

Impact: Other

WWC-44651: Specify a numeric value for item icon width.

Cause: An invalid value was specified for the Item Icon Width field.

Action: Specify a positive number for the width (in pixels) of item images.
Level: 1

Type: ERROR

Impact: Other

WWC-44652: Invalid number of columns. Value should be at least be 1.

Cause: An invalid value was specified for the number of columns.

Action: Specify a positive number for the number of columns in the region.
Level: 1

Type: ERROR

Impact: Other

WWC-44662: To perform this action, select a portlet, item, or tab using the check boxes below

Cause: An action button was clicked without first selecting any portlets, items, or tabs.

Action: Select one or more portlets, items, or tabs before clicking an action button.
Level: 1

Type: ERROR

Impact: Other

WWC-44704: error while creating the page parameter

Cause: An attempt to create a page parameter failed.

Action: Refresh the screen and verify that the page is still available.
Level: 1

Type: ERROR

Impact: Other

WWC-44705: error while reordering page parameter \"%1\"

Cause: An attempt to reorder page parameters failed.

Action: Refresh the screen and verify that the page and page parameter are still available.
Level: 1

Type: ERROR

Impact: Other

WWC-44706: error while deleting page parameter \"%1\"

Cause: An attempt to delete a page parameter failed.

Action: Refresh the screen and verify that the page and page parameter are still available.
Level: 1

Type: ERROR

Impact: Other

WWC-44707: error while editing page parameter \"%1\"

Cause: An attempt to edit the value of a page parameter failed.

Action: Refresh the screen and verify that the page parameter is still available.
Level: 1

Type: ERROR

Impact: Other

WWC-44708: invalid page parameter name \"%1\"

Cause: The specified page parameter name was invalid.

Action: Enter a valid page parameter name. Refer to the Page Properties Parameter tab for a list of valid page parameter names.
Level: 1

Type: ERROR

Impact: Other

WWC-44709: error while editing value of portlet parameter \"%1\"

Cause: An attempt to edit the value of a portlet parameter failed.

Action: Refresh the screen and verify that the portlet parameter is still available.
Level: 1

Type: ERROR

Impact: Other

WWC-44714: error while personalizing page parameter \"%1\"

Cause: An attempt to personalize a page parameter failed.

Action: Refresh the screen and verify that the page parameter is still available.
Level: 1

Type: ERROR

Impact: Other

WWC-44715: error while resetting page parameters to default values

Cause: An attempt to reset page parameters to their default values failed.

Action: Refresh the screen and verify that the personalization screen is still available.
Level: 1

Type: ERROR

Impact: Other

WWC-44721: error while fetching portlet parameters

Cause: An attempt to fetch portlet parameters failed.

Action: Refresh the screen and verify that the portlet is still available.
Level: 1

Type: ERROR

Impact: Other

WWC-44751: error while editing value of parameter \"%1\"

Cause: An attempt to edit the value of an event parameter failed.

Action: Refresh the screen and verify that the event parameter is still available.
Level: 1

Type: ERROR

Impact: Other

WWC-44752: error while linking event \"%1\" to page \"%2\"

Cause: An attempt to link an event to a page failed.

Action: Refresh the screen and verify that the event and the page are still available.
Level: 1

Type: ERROR

Impact: Other

WWC-44753: error while removing link from event \"%1\"

Cause: An attempt to remove a link from an event failed.

Action: Refresh the screen and verify that the event is still available.
Level: 1

Type: ERROR

Impact: Other

WWC-44754: error while updating link between event \"%1\" and page \"%2\"

Cause: An attempt to update the target page for an event failed.

Action: Refresh the screen and verify that the event and the page are still available.
Level: 1

Type: ERROR

Impact: Other

WWC-44755: invalid event output name \"%1\"

Cause: The specified event output name was invalid.

Action: Specify a valid event output name.
Level: 1

Type: ERROR

Impact: Other

WWC-44756: The name is already used. Pick a name that is unique.

Cause: The specified name has already been used.

Action: Specify a different, unique name.
Level: 1

Type: ERROR

Impact: Other

WWC-44757: error while creating the parameter: %1

Cause: An attempt to create a parameter failed.

Action: Refresh the screen and verify that the parent object is still available.
Level: 1

Type: ERROR

Impact: Other

WWC-44758: error while editing the parameter: %1

Cause: An attempt to edit a parameter failed.

Action: Refresh the screen and verify that the parent object is still available.
Level: 1

Type: ERROR

Impact: Other

WWC-44759: Parameter cannot be personalized.

Cause: An attempt to personalize a parameter failed. The parameter cannot be personalized.

Action: Refresh the screen and verify whether or not the parameter can be personalized.
Level: 1

Type: ERROR

Impact: Other

WWC-44761: error while deleting parameter: %1

Cause: An attempt to delete a parameter failed.

Action: Refresh the screen and verify that the parent object and the parameter are still available.
Level: 1

Type: ERROR

Impact: Other

WWC-44762: parameter \"%1\" not found

Cause: The specified parameter was not found.

Action: Refresh the screen and verify that the parent object is still available and that the user has the appropriate access privileges.
Level: 1

Type: ERROR

Impact: Other

WWC-44765: Search for parameter \"%1\" causes an error: %2.

Cause: An attempt to search for a parameter failed.

Action: Refresh the screen and verify that the object is still available and that the user has the appropriate access privileges.
Level: 1

Type: ERROR

Impact: Other

WWC-44766: error while creating the parameter mapping: %1

Cause: An attempt to create a parameter map failed.

Action: Refresh the screen and verify that the parent object is still available.
Level: 1

Type: ERROR

Impact: Other

WWC-44767: error while updating the parameter mapping: %1

Cause: An attempt to edit a parameter map failed.

Action: Refresh the screen and verify that the parent object is still available.
Level: 1

Type: ERROR

Impact: Other

WWC-44768: unsupported from type \"%1\"

Cause: The source object type specified was not supported.

Action: Select a different source object.
Level: 1

Type: ERROR

Impact: Other

WWC-44769: Parameter \"%1\" already has the smallest display order and cannot be moved up.

Cause: An attempt was made to move the first parameter in the list to the top of the display order.

Action: Refresh the screen and verify that the parameter is already at the top of the display order.
Level: 1

Type: ERROR

Impact: Other

WWC-44770: failure to move parameter \"%1\" up in the display order: %2

Cause: An attempt to move a parameter up in the display order failed.

Action: Refresh the screen and verify that the parameter is still available.
Level: 1

Type: ERROR

Impact: Other

WWC-44775: flow element not found

Cause: The specified flow element was not found.

Action: Refresh the screen and verify that the dependent object is still available.
Level: 1

Type: ERROR

Impact: Other

WWC-44779: error while creating flow link \"%1\"

Cause: An attempt to create a flow link failed.

Action: Refresh the screen and verify that the parent page is still available.
Level: 1

Type: ERROR

Impact: Other

WWC-44780: error while deleting flow link \"%1\"

Cause: An attempt to delete a flow link failed.

Action: Refresh the screen and verify that the parent page is still available.
Level: 1

Type: ERROR

Impact: Other

WWC-44781: flow link not found

Cause: The specified flow link was not found.

Action: Refresh the screen and verify that the parent page is still available.
Level: 1

Type: ERROR

Impact: Other

WWC-44783: invalid parent type for event \"%1\"

Cause: The specified parent object did not have a valid type.

Action: Refresh the screen and verify that the parent object is still available.
Level: 1

Type: ERROR

Impact: Other

WWC-44784: Parent of event \"%1\" is not a portlet.

Cause: The specified parent object was not a portlet.

Action: Specify a portlet.
Level: 1

Type: ERROR

Impact: Other

WWC-44786: Event \"%1\" already exists.

Cause: The specified event name already existed.

Action: Specify a different, unique event name.
Level: 1

Type: ERROR

Impact: Other

WWC-44787: error while creating event \"%1\": %2

Cause: An attempt to create an event failed.

Action: Refresh the screen and verify that the parent object is still available.
Level: 1

Type: ERROR

Impact: Other

WWC-44788: error while deleting event: %1

Cause: An attempt to delete an event failed.

Action: Refresh the screen and verify that the event is still available.
Level: 1

Type: ERROR

Impact: Other

WWC-44789: error while deleting events: %1

Cause: An attempt to delete events failed.

Action: Refresh the screen and verify that the events are still available.
Level: 1

Type: ERROR

Impact: Other

WWC-44790: event not found

Cause: The specified event was not found.

Action: Refresh the screen and verify that the parent object is still available.
Level: 1

Type: ERROR

Impact: Other

WWC-44791: event \"%1\" not found

Cause: The specified event was not found.

Action: Refresh the screen and verify that the parent object is still available.
Level: 1

Type: ERROR

Impact: Other

WWC-44792: events not found

Cause: The specified events were not found.

Action: Refresh the screen and verify that the parent objects are still available.
Level: 1

Type: ERROR

Impact: Other

WWC-44793: error while creating event map: %1

Cause: An attempt to create an event map failed.

Action: Refresh the screen and verify that the event is still available.
Level: 1

Type: ERROR

Impact: Other

WWC-44794: error while deleting event map: %1

Cause: An attempt to delete an event map failed.

Action: Refresh the screen and verify that the event is still available.
Level: 1

Type: ERROR

Impact: Other

WWC-44795: event map not found

Cause: The specified event map was not found.

Action: Verify that the parent object is still available.
Level: 1

Type: ERROR

Impact: Other

WWC-44801: error while searching for parameter mapping: %1

Cause: The specified parameter map was not found.

Action: Refresh the screen, verify that the parent object is still available and that the user has the appropriate access privileges.
Level: 1

Type: ERROR

Impact: Other

WWC-44803: duplicate event maps not allowed

Cause: An attempt was made to duplicate an event map.

Action: Edit or delete the existing event map, or create a new event map.
Level: 1

Type: ERROR

Impact: Other

WWC-44812: Error while fetching portlet events

Cause: An attempt to fetch portlet events failed.

Action: Refresh the screen and verify that the portlet is still available.
Level: 1

Type: ERROR

Impact: Other

WWC-44815: Error while retrieving link from event \"%1\"

Cause: An attempt to retrieve the link from an event failed.

Action: Refresh the screen and verify that the event is still available.
Level: 1

Type: ERROR

Impact: Other

WWC-44816: Error while retrieving the target page for event \"%1\"

Cause: An attempt to retrieve the target page for an event failed.

Action: Refresh the screen and verify that the event is still available.
Level: 1

Type: ERROR

Impact: Other

WWC-44829: Error while writing parameter map metadata: %1

Cause: An attempt to write parameter map metadata failed.

Action: Refresh the screen and verify that the parameter map is still available.
Level: 1

Type: ERROR

Impact: Other

WWC-44833: error while adding display name or description for event \"%1\"

Cause: An attempt to add a display name or description for an event failed.

Action: Refresh the screen and verify that the event is still available.
Level: 1

Type: ERROR

Impact: Other

WWC-44834: error while editing the event: %1

Cause: An attempt to edit an event failed.

Action: Refresh the screen and verify that the event is still available.
Level: 1

Type: ERROR

Impact: Other

WWC-44835: error while creating page event from portlet event \"%1\": %2

Cause: An attempt to create a page event from a portlet event failed.

Action: Refresh the screen and verify that the portlet event is still available.
Level: 1

Type: ERROR

Impact: Other

WWC-44836: error while invalidating page cache after updating event: %1

Cause: An attempt to invalidate the page cache after updating an event failed.

Action: Refresh the screen and verify that the event or dependent object is still available.
Level: 1

Type: ERROR

Impact: Other

WWC-44840: invalid context for parameter \"%1\"

Cause: The parent object (portlet, page, or event) for the parameter was not valid.

Action: Refresh the screen and verify that the parent object still exists.
Level: 1

Type: ERROR

Impact: Other

WWC-44841: error during a parameter change event: %1

Cause: An attempt to update a parameter failed.

Action: Refresh the screen and verify that the parameter or dependent object are still available.
Level: 1

Type: ERROR

Impact: Other

WWC-44843: page not found: %1,%2

Cause: The specified page was not found.

Action: Verify that the page exists and that the details of the specified page are correct.
Level: 1

Type: ERROR

Impact: Other

WWC-44875: portal template not found

Cause: An attempt was made to base a page on an invalid template.

Action: Specify a valid template.
Level: 1

Type: ERROR

Impact: Other

WWC-44891: The system variable \"%1\" is not valid. Specify a different value.

Cause: An invalid system variable was specified.

Action: Specify a valid system variable, one of USER_NAME, USER_ID, COMPANY_NAME, SUBSCRIBER_ID, NLS_LANG, or NLS_TERRITORY.
Level: 1

Type: ERROR

Impact: Other

WWC-44899: error during a parameter map change event: %1

Cause: An attempt to update a parameter map failed.

Action: Refresh the screen and verify that the parameter map or the dependent objects are still available.
Level: 1

Type: ERROR

Impact: Other

WWC-44901: error while deleting flow link children: %1

Cause: An attempt to delete the children of a flow link failed.

Action: Refresh the screen and verify that the dependent objects are still available.
Level: 1

Type: ERROR

Impact: Other

WWC-44902: error while deleting parameter maps: %1

Cause: An attempt to delete parameter maps failed.

Action: Refresh the screen and verify that the dependent objects are still available.
Level: 1

Type: ERROR

Impact: Other

WWC-44929: You can only download JSP file from a JSP page.

Cause: An attempt was made to download a JSP file from a non-JSP type page.

Action: Specify a JSP page to download.
Level: 1

Type: ERROR

Impact: Other

WWC-44930: You do not have privileges to download the JSP file for this JSP page.

Cause: An attempt was made to download the JSP file of a JSP page without the appropriate privileges.

Action: Log in as a user with privileges to perform the operation.
Level: 1

Type: ERROR

Impact: Other

WWC-44932: The page's template cannot be changed to \"%1\" because the page contains portlets or items and the selected template has no portlet regions or item regions.

Cause: A template was selected without an item region or portlet region for the items or portlets on the page.

Action: Select a different template. Ensure that the template contains the necessary region types.
Level: 1

Type: ERROR

Impact: Other

WWC-44997: error while refreshing the portlet repository

Cause: An attempt to refresh the portlet repository failed.

Action: The page is published as a portlet. Refresh the repository manually.
Level: 1

Type: ERROR

Impact: Other

WWC-45026: Number of objects in each section must be a number greater than zero.

Cause: An invalid value was specified for the number of objects in each section.

Action: Specify a number greater than zero.
Level: 1

Type: ERROR

Impact: Other

WWC-45235: Number entered for the limit must be a valid number greater than or equal to zero.

Cause: An invalid number value was specified for the limit.

Action: Specify a valid number between 0 and 50.
Level: 1

Type: ERROR

Impact: Other

WWC-45256: This page group is not configured to allow JSP access.

Cause: An attempt was made to copy a JSP to a page group that was not configured to allow JSP access.

Action: Edit the properties of the page group and, on the Configure tab, enable "JSP Access".
Level: 1

Type: ERROR

Impact: Other

WWC-45290: The portlet is not found (%1 , %2).

Cause: An attempt was made to access a portlet with a given portlet ID and provider ID, using the API call, wwsbr_folder_portlet.describe_parameters. The specified portlet was not found.

Action: Ensure that the specified provider ID and portlet ID are correct.
Level: 1

Type: ERROR

Impact: Other

WWC-46800: document not found

Cause: An attempt was made to access a document that did not exist or that was no longer accessible.

Action: Verify that the specified URL is still valid, if applicable. Visit the parent page to verify that the item still exists.
Level: 1

Type: ERROR

Impact: Other

WWC-46805: You do not have permission to perform this operation.

Cause: An attempt was made to perform an action but the user does not have the appropriate privileges.

Action: Log in as a user who has the appropriate privileges to perform the operation.
Level: 1

Type: ERROR

Impact: Other

WWC-46811: Your file cannot be uploaded because it is larger than the maximum allowed file size.

Cause: An attempt was made to upload a file that exceeded the maximum size allowed per file.

Action: Reduce the size of the file, or contact the portal administrator and request that the maximum permitted file size be increased.
Level: 1

Type: ERROR

Impact: Other

WWC-46813: Your file cannot be uploaded because doing so would exceed the total amount of space allocated for uploaded files.

Cause: An attempt was made to upload a file that would result in the allocated space quota being exceeded.

Action: Create some free space by deleting other documents, or contact the portal administrator and request that the quota allocation be increased.
Level: 1

Type: ERROR

Impact: Other

WWC-47499: You do not have permission to access this screen.

Cause: An attempt was made to access a screen but the user did not have sufficient privileges.

Action: Log in as a user with at least the 'All Logs - Edit' privilege.
Level: 1

Type: ERROR

Impact: Other

WWC-49100: unable to locate type %1

Cause: An attempt was made to load a nonexistent dynamic type.

Action: Verify the name of the dynamic type.
Level: 1

Type: ERROR

Impact: Other

WWC-49101: invalid conversion requested for type %1

Cause: A mismatch occurred between the dynamic type loaded and the requested conversion type. For example, the type_to_number() method was invoked after loading a date type.

Action: Ensure that the type loaded and the requested conversion type match. For example, if a number type is loaded a number, invoke the type_to_number() method for conversion.
Level: 1

Type: ERROR

Impact: Other

WWC-49102: no conversion performed for type %1, value %2

Cause: The value provided could not be converted to the requested type using the available format masks. The format mask used may be invalid.

Action: Provide a valid format mask.
Level: 1

Type: ERROR

Impact: Other

WWC-50003: object not found

Cause: The specified path to the given object did not exist.

Action: Verify that the path is valid. Path names are case-sensitive.
Level: 1

Type: ERROR

Impact: Other

WWC-50015: You do not have permission to perform this operation.

Cause: An attempt was made to perform an operation but the user did not have the appropriate privileges.

Action: Log in as a user who has the appropriate privileges to perform the operation.
Level: 1

Type: ERROR

Impact: Other

WWC-53100: general error

Cause: An attempt to access the Oracle Internet Directory failed.

Action: Wait for a while and attempt the operation again. Contact the portal administrator if the problen persists.
Level: 1

Type: ERROR

Impact: Other

WWC-53101: invalid input parameter

Cause: Invalid values were specified for input parameters.

Action: Check the specified input parameter values.
Level: 1

Type: ERROR

Impact: Other

WWC-53102: The specified user is not a member of any group.

Cause: The specified user was not a member of any group.

Action: Check the specified user name.
Level: 1

Type: ERROR

Impact: Other

WWC-53103: The specified subscriber does not exist in the directory.

Cause: An attempt was made to access a subscriber that did not exist in the directory.

Action: Check the name of the subscriber required.
Level: 1

Type: ERROR

Impact: Other

WWC-53104: The specified user does not exist in the directory.

Cause: The specified user did not exist in the directory.

Action: Check the name of the specified user.
Level: 1

Type: ERROR

Impact: Other

WWC-53105: The root Oracle Context does not exist in the directory.

Cause: The root Oracle Context was not found in the directory.

Action: Check the Oracle Internet Directory Server configuration and ensure the root Oracle Context information is loaded properly.
Level: 1

Type: ERROR

Impact: Other

WWC-53106: Multiple subscriber entries are found for the specified subscriber nickname.

Cause: Multiple subscriber entries with the same subscriber nickname were found in the Oracle Internet Directory.

Action: Verify that the nickname attribute of subscribers in the Oracle Internet Directory are unique.
Level: 1

Type: ERROR

Impact: Other

WWC-53107: Root Oracle Context does not contain all the required information.

Cause: The root Oracle Context level was not found.

Action: Check the Oracle Internet Directory Server configuration and ensure that the root Oracle Context information is loaded properly.
Level: 1

Type: ERROR

Impact: Other

WWC-53108: Oracle Context does not exist for the subscriber.

Cause: Oracle Context was not found for the subscriber.

Action: Check the Oracle Internet Directory Server configuration and ensure that the subscriber Oracle Context information is loaded properly.
Level: 1

Type: ERROR

Impact: Other

WWC-53109: Oracle Context for the subscriber is invalid.

Cause: Oracle Context for the subscriber was invalid.

Action: Check the Oracle Internet Directory Server configuration and ensure that the subscriber Oracle Context information is loaded properly.
Level: 1

Type: ERROR

Impact: Other

WWC-53110: Multiple user entries exist for the specified user nickname.

Cause: Multiple users with the given name were found in the directory.

Action: Use the popup list next to the name field to specify the user name.
Level: 1

Type: ERROR

Impact: Other

WWC-53111: The specified group does not exist in the directory.

Cause: An attempt was made to access a group that did not exist in the directory.

Action: Check the name of the group required.
Level: 1

Type: ERROR

Impact: Other

WWC-53112: Multiple group entries exist for the specified group nickname in the directory.

Cause: Multiple groups with the given name were found in the directory.

Action: Verify that the group name is valid. Use the popup list next to the name field to specify the group name.
Level: 1

Type: ERROR

Impact: Other

WWC-53113: Your account is locked. Have your administrator reset your password, or wait for the lockout duration to transpire.

Cause: The user account was locked because the number of failed login attempts exceeded the maximum number allowed, as specified by the password policy.

Action: Contact the portal administrator and request that the password be reset. Alternatively, wait for the lockout period to expire.
Level: 1

Type: ERROR

Impact: Other

WWC-53114: The password is about to expire and should be changed.

Cause: A password was about to expire.

Action: Change the password before it expires.
Level: 1

Type: ERROR

Impact: Other

WWC-53115: Your user name or password is incorrect.

Cause: An attempt was made to authenticate with incorrect login credentials.

Action: Specify the correct login credentials.
Level: 1

Type: ERROR

Impact: Other

WWC-53116: Your password has expired.

Cause: A password has expired.

Action: Contact the portal administrator and request that the password be reset.
Level: 1

Type: ERROR

Impact: Other

WWC-53117: The entity handle properties are being reset by the caller.

Cause: An unexpected condition was encountered.

Action: Report this error to Oracle Support Services. Include the operations that led to the error, any unusual circumstances that occurred before receiving this error, and the complete stack trace produced by this error.
Level: 1

Type: ERROR

Impact: Other

WWC-53118: unable to locate the subscriber for the specified user

Cause: An unexpected condition was encountered.

Action: Report this error to Oracle Support Services. Include the operations that led to the error, any unusual circumstances that occurred before receiving this error, and the complete stack trace produced by this error.
Level: 1

Type: ERROR

Impact: Other

WWC-53119: The password is about to expire; change the password now.

Cause: A password was about to expire.

Action: Change the password before it expires.
Level: 1

Type: ERROR

Impact: Other

WWC-53120: Your password is smaller than the minimum required length of a password.

Cause: The password specified was less than the minimum required length required for passwords.

Action: Specify a password that is equal to, or greater than, the minimum required password length. If necessary, contact the portal administrator to confirm the minimum required length of passwords.
Level: 1

Type: ERROR

Impact: Other

WWC-53121: Your password does not contain the minimum number of numeric characters required.

Cause: The password specified did not contain the minimum number of numeric characters required.

Action: Specify a password that contains at least the minimum number of numeric characters required. If necessary, contact the portal administrator to confirm the minimum number of numeric characters required for passwords.
Level: 1

Type: ERROR

Impact: Other

WWC-53122: Your password cannot be null.

Cause: A null value was specified for a password.

Action: Specify a valid password.
Level: 1

Type: ERROR

Impact: Other

WWC-53123: Your new password cannot be the same as your old password.

Cause: While changing a password, the new password was the same as the previous password.

Action: Specify a new password that is different from the previous password.
Level: 1

Type: ERROR

Impact: Other

WWC-53124: Your password contains an invalid value.

Cause: The password specified contained one or more invalid characters.

Action: Specify a password that does not contain any invalid characters.
Level: 1

Type: ERROR

Impact: Other

WWC-53125: Your password has expired. You should change your password soon.

Cause: A password had expired but the user has been allowed to log in and change the password.

Action: Change the password as soon as possible.
Level: 1

Type: ERROR

Impact: Other

WWC-53126: Your password has expired. Contact your administrator to change your password.

Cause: A password had expired.

Action: Contact the portal administrator to change the password.
Level: 1

Type: ERROR

Impact: Other

WWC-53127: A user property is not found.

Cause: An attempt was made to search for a property that did not exist in the directory.

Action: Check the property name.
Level: 1

Type: ERROR

Impact: Other

WWC-53128: Your account has been disabled.

Cause: An account was disabled.

Action: Contact the portal administrator and request that the account be enabled.
Level: 1

Type: ERROR

Impact: Other

WWC-53129: A property is not found while searching for the property in the directory.

Cause: An attempt was made to search for a property that did not exist in the directory.

Action: Check the property name.
Level: 1

Type: ERROR

Impact: Other

WWC-53149: The Portal was unable to establish contact with the Oracle Internet Directory because the following connection parameters are missing:%1

Cause: The connection parameters specified were not available.

Action: Run the command-line script ptlasst in MIDTIER mode to configure the Oracle Internet Directory connection parameters: ptlasst -mode MIDTIER -type OID
Level: 1

Type: ERROR

Impact: Other

WWC-53200: The specified grantee has already been granted %1 privilege. To change the privilege of this grantee, select the appropriate privilege from the drop-down list shown against the name of the grantee and click Apply or OK.

Cause: An attempt was made to add a privilege for a grantee that has already been granted a different privilege. Only a single privilege can be granted on an object to any grantee.

Action: Change the privilege of this grantee by selecting the appropriate privilege from the drop-down list shown against the name of the grantee.
Level: 1

Type: ERROR

Impact: Other

WWC-53201: Value specified for the limit set for total space allocated must be a positive integer.

Cause: The value specified for the total space allocated was invalid.

Action: Specify a positive integer for the total space allocated.
Level: 1

Type: ERROR

Impact: Other

WWC-53202: Value specified for the limit set for maximum file size must be a positive integer.

Cause: The value specified for the maximum file size was invalid.

Action: Specify a positive integer for the maximum file size.
Level: 1

Type: ERROR

Impact: Other

WWC-53203: Value specified for the SMTP port must be a positive integer.

Cause: The value specified for the SMTP port was invalid.

Action: Specify a positive integer for the SMTP port.
Level: 1

Type: ERROR

Impact: Other

WWC-53204: Value specified for the URL connection timeout interval must be a positive integer.

Cause: The value specified for the URL connection timeout interval was invalid.

Action: Specify a positive integer for the URL connection timeout interval.
Level: 1

Type: ERROR

Impact: Other

WWC-53205: Value specified for log switch interval must be a positive integer.

Cause: The value specified for the log switch interval was invalid.

Action: Specify a positive integer for the log switch interval.
Level: 1

Type: ERROR

Impact: Other

WWC-53206: Value specified for the directory synchronization interval must be a positive integer.

Cause: The value specified for the interval between DIP notifications was invalid.

Action: Specify a positive integer for the interval between DIP notifications.
Level: 1

Type: ERROR

Impact: Other

WWC-53207: Value specified for the Web Cache invalidation port must be a positive integer.

Cause: The value specified for the invalidation port was invalid.

Action: Specify a positive integer for the invalidation port.
Level: 1

Type: ERROR

Impact: Other

WWC-53208: Value specified for the Web Cache administration port must be a positive integer.

Cause: The value specified for the administration port was invalid.

Action: Specify a positive integer for the administration port.
Level: 1

Type: ERROR

Impact: Other

WWC-53209: Value specified for the maximum Web Cache expiry time must be a positive integer.

Cause: The value specified for the maximum expiry time was invalid.

Action: Specify a positive integer for the maximum expiry time.
Level: 1

Type: ERROR

Impact: Other

WWC-53218: Cannot set the directory synchronization parameters because the provisioning profile does not exist.

Cause: An attempt was made to set directory synchronization parameters when the provisioning profile did not exist.

Action: Create the provisioning profile by running ptlasst using -mode MIDTIER -type DIPREG and retry.
Level: 1

Type: ERROR

Impact: Other

WWC-53220: An exception occurs while creating the user account in the Oracle Internet Directory. Verify that the specified password conforms to the password policy.

Cause: The password specified violated the password policy or an attribute value was invalid.

Action: Specify a password that complies with the password policy and retry. Contact the portal administrator if the problem persists.
Level: 1

Type: ERROR

Impact: Other

WWC-53221: An exception occurs while creating the user account in the Oracle Internet Directory: %1

Cause: The password specified violated the password policy or an attribute value was invalid. The error message provides specific information about the cause.

Action: Take appropriate action based on the error message. Contact the portal administrator if the problem persists.
Level: 1

Type: ERROR

Impact: Other

WWC-53222: The URL contains an invalid parameter value.

Cause: The value specified for the parameter in the URL was invalid.

Action: Provide the correct value for the parameter and resubmit the request, or log in to the Oracle Single Sign-On Server again.
Level: 1

Type: ERROR

Impact: Other

WWC-53314: Number of users returned exceeds the search return limit. Narrow the search criteria and try again.

Cause: A large number of users matched the search criteria specified.

Action: Change the search criteria so that a smaller number of users is returned. Alternatively, contact the portal administrator and request that the LOV size limit be increased.
Level: 1

Type: ERROR

Impact: Other

WWC-53366: Number of groups returned exceeds the search return limit. Narrow the search criteria and try again.

Cause: A large number of groups matched the search criteria specified.

Action: Change the search criteria so that a smaller number of groups is returned. Alternatively, contact the portal administrator and request that the LOV size limit be increased.
Level: 1

Type: ERROR

Impact: Other

WWC-53377: The external application does not exist and may have been deleted. Update your link. If using the External Applications portlet, customize the portlet to update the list of links.

Cause: Some of the existing external application links were no longer valid.

Action: Refresh the portlet so that these obselete links are removed.
Level: 1

Type: ERROR

Impact: Other

WWC-57102: To perform this action, select a portlet or tab using the check boxes below.

Cause: An action button was clicked without first selecting any portlets or tabs.

Action: Select one or more portlets or tabs before clicking an action button.
Level: 1

Type: ERROR

Impact: Other

WWC-57103: No region selected. Select a region, then click %1.

Cause: An attempt was made to copy or move an item to a page that did not have an item region.

Action: Create an item region, and then copy or move the item.
Level: 1

Type: ERROR

Impact: Other

WWC-57106: To perform this action, select a portlet, item, or level using the check boxes below.

Cause: An action button was clicked without first selecting any portlets, items, or levels.

Action: Select one or more portlets, items, or levels before clicking an action button.
Level: 1

Type: ERROR

Impact: Other

WWC-57124: Moving tabs is not allowed. Only portlets can be moved using the Move button. To reorder tabs, click the Arrange Tabs icon.

Cause: An attempt was made to move a tab. Tabs cannot be moved between regions.

Action: Although tabs cannot be moved between regions, you may reorder tabs within a single tab region. To reorder tabs, click the Arrange Tabs icon in the tab region.
Level: 1

Type: ERROR

Impact: Other

WWC-57186: Page %1 is a system-level cache page; no personalization is allowed.

Cause: An attempt was made to personalize a page that was cached at the system level. This is not permitted because all users see the same content on such pages. Only pages that are cached at the user level (or not cached at all) can be personalized.

Action: To modify this page, make changes affecting all users; this requires privileges to edit the page.
Level: 1

Type: ERROR

Impact: Other

WWC-57216: Invalid number of rows. Value should be at least be 1.

Cause: The value specified for the number of rows was invalid.

Action: Specify a positive number for the number of rows in the region.
Level: 1

Type: ERROR

Impact: Other

WWC-57239: Choose a page for the template input parameter.

Cause: Page was specified as the value type for the template input, but a page was not selected.

Action: Click the Browse Pages icon and choose a page for the template input.
Level: 1

Type: ERROR

Impact: Other

WWC-57267: error while configuring the page group

Cause: An attempt to configure a page group failed.

Action: Refresh the screen and verify that the page group is still available.
Level: 1

Type: ERROR

Impact: Other

WWC-57268: error while writing parameter metadata: %1

Cause: An attempt to write parameter metadata failed.

Action: Refresh the screen and verify that the parameter is still available.
Level: 1

Type: ERROR

Impact: Other

WWC-57269: The parent object '%1' does not have a valid ID.

Cause: The parent object ID was invalid.

Action: Refresh the screen and verify that the parent object is still available.
Level: 1

Type: ERROR

Impact: Other

WWC-57270: error during a flow link change event: %1

Cause: An attempt to update a flow link failed.

Action: Refresh the screen and verify that the dependent pages are still available.
Level: 1

Type: ERROR

Impact: Other

WWC-57272: The reference path %1 for the portlet instance %2 is not valid.

Cause: The format of the reference path was incorrect. The correct format is <id>_<portletname>_<providerid>.

Action: Specify correct values and use the correct reference path format.
Level: 1

Type: ERROR

Impact: Other

WWC-57305: Tab pages cannot be edited directly.

Cause: An attempt was made to directly edit a tab.

Action: Edit the page that contains the tab.
Level: 1

Type: ERROR

Impact: Other

WWC-57306: This page cannot be edited in Layout Mode.

Cause: An attempt was made to edit a PL/SQL, JSP, or URL page in Layout Mode. Only standard pages can be edited in Layout Mode.

Action: Edit the page properties from the Navigator, or edit the page content using an editor appropriate for the page type.
Level: 1

Type: ERROR

Impact: Other

WWC-57307: Invalid expiry value. Value should be at least be 1 minute.

Cause: The value specified for the cache expiration time was invalid.

Action: Specify a positive number for the cache expiration time.
Level: 1

Type: ERROR

Impact: Other

WWC-57323: The selected portal template is not found.

Cause: The selected portal template could not be found. The page may have been deleted.

Action: Choose another portal template.
Level: 1

Type: ERROR

Impact: Other

WWC-57324: The selected page does not contain any item placeholders.

Cause: The selected page did not contain any placeholder items, so it could not be used as a portal template.

Action: Choose a page that contains placeholder items.
Level: 1

Type: ERROR

Impact: Other

WWC-57331: Specify a numeric value for height.

Cause: The value specified for the region height was invalid.

Action: Specify a number (preferably between 1 and 100) for the region height. Note that leaving this field blank is the same as entering 1.
Level: 1

Type: ERROR

Impact: Other

WWC-57354: Invalid timeout value. Value should be number (zero or more).

Cause: The value specified for the page timeout was invalid.

Action: Specify a positive number for the page timeout.
Level: 1

Type: ERROR

Impact: Other

WWC-57357: In order to choose another option, you must first Detach the portal template.

Cause: An attempt was made to choose another template option without first detaching the current template.

Action: Click Detach from Template to remove the template from the page, then proceed.
Level: 1

Type: ERROR

Impact: Other

WWC-57365: The given tabstring for the page is invalid.

Cause: The tabstring specified for the page was invalid.

Action: Specify a valid tabstring for the page.
Level: 1

Type: ERROR

Impact: Other

WWC-57381: The language specified in the URL is invalid.

Cause: The URL specified contained an invalid language element, for example, it may have been null.

Action: Specify a different language element, or remove it completely.
Level: 1

Type: ERROR

Impact: Other

WWC-57382: The version specified in the URL is invalid.

Cause: The URL specified contained an invalid version element, for example, it may have been null.

Action: Specify a different version element, or remove it completely.
Level: 1

Type: ERROR

Impact: Other

WWC-57383: The language specified in the URL is not currently supported by this Portal.

Cause: The URL specified contained a reference to a language that did not represent a legitimate language code, or was not currently available in this portal.

Action: Specify a different language element, or remove it completely.
Level: 1

Type: ERROR

Impact: Other

WWC-57384: The URL contains a reference to a version, but specifies a page: Portal does not support versioning of pages.

Cause: The URL specified requested a page and a version. Oracle Portal does not support versioning of pages and cannot resolve this URL.

Action: Remove the version element from the URL.
Level: 1

Type: ERROR

Impact: Other

WWC-57385: The template cannot be detached from the page because you do not have privileges to access one or more portlets on the template.

Cause: An attempt was made to detach a template from a page, but the user did not have the privileges to access every portlet on the template. These privileges are required because, when detaching a template, the portlets on the template are copied to the page.

Action: Contact the portal administrator and request that the appropriate privileges be granted.
Level: 1

Type: ERROR

Impact: Other

WWC-57421: Specify a numeric value for the space between items.

Cause: The value specified for the Space between Items field was invalid.

Action: Specify a number (preferably betweeen 1 and 100) for the Space between Items field. If you do not want any space between items, specify 0 or null.
Level: 1

Type: ERROR

Impact: Other

WWC-57422: Specify a numeric value for the space around items.

Cause: The value specified for the Space around Items field was invalid.

Action: Specify a number (preferably between 1 and 100) for the Space around Items field. If you do not want any space around items, specify 0 or null.
Level: 1

Type: ERROR

Impact: Other

WWC-57436: invalid item attribute parameter name \"%1\"

Cause: The specified item attribute parameter name was invalid.

Action: Specify a valid item attribute parameter name.
Level: 1

Type: ERROR

Impact: Other

WWC-59083: unable to get SSO login configuration from mod_osso

Cause: The operation to retrieve the SSO login configuration from mod_osso failed.

Action: Verify that the OracleAS Portal middle-tier mod_osso is properly registered with an Oracle SSO Server.
Level: 1

Type: ERROR

Impact: Other

104 WWS-18000 to WWS-33951

WWS-18000: Document written successfully but the annotation failed.

Cause: The write operation of the file completed, but the comments for it failed.

Action: Check the WebDAV error file in your Personal Page for possible reasons why this occurred.
Level: 1

Type: ERROR

Impact: Other

WWS-18001: %1

Cause: A redirect required to get to the requested collection has failed.

Action: Check that the redirected URL is valid and WebDAV is set up correctly for this portal.
Level: 1

Type: ERROR

Impact: Other

WWS-18002: The document %1 cannot be located.

Cause: The requested document did not exist in the location specified.

Action: In Oracle Portal, check whether the document is accessible. If it is accessible, there is an internal error. Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWS-18003: No such lock token %1 is associated with document ID %2.

Cause: No lock was associated with this resource.

Action: To create a lock, check it out using the lock command.
Level: 1

Type: ERROR

Impact: Other

WWS-18004: User not authorized to perform the requested operation

Cause: An attempt was made to perform an operation but the user does not have the necessary privileges to perform the task.

Action: If applicable, contact the portal administrator and request that privileges be granted to perform such operations.
Level: 1

Type: ERROR

Impact: Other

WWS-18005: Driver versions do not match

Cause: The version of the OraDAV module on the middle tier and its database counterpart do not match.

Action: Check your installation.
Level: 1

Type: ERROR

Impact: Other

WWS-18006: Unknown driver parameter: %1

Cause: The version of the OraDAV module on the middle tier and its database counterpart do not match.

Action: Check your installation.
Level: 1

Type: ERROR

Impact: Other

WWS-18007: Invalid argument: %1

Cause: The argument value specified is not valid.

Action: Check that the values supplied for all arguments are valid.
Level: 1

Type: ERROR

Impact: Other

WWS-18008: The requested operation is prohibited on the specified document.

Cause: An attempt to perform an operation on a document failed.

Action: Check the permissions of the user, security on the document, and the status of the document.
Level: 1

Type: ERROR

Impact: Other

WWS-18009: Supplied container version %1 does not match %2 for %3

Cause: The version of the OraDAV module on the middle tier does not match the drivers in the database.

Action: Check the installation and ensure that all necessary patches have been applied.
Level: 1

Type: ERROR

Impact: Other

WWS-18010: Document %1 is locked.

Cause: The document requested was checked out.

Action: Check in or undo the checkout for the document to release the lock.
Level: 1

Type: ERROR

Impact: Other

WWS-18011: The document exists but is not the expected type.

Cause: The document found was a file when a directory was expected. Or, the document found was a directory when a file was expected.

Action: Check that the operation attempted is valid for this type of resource.
Level: 1

Type: ERROR

Impact: Other

WWS-18012: ROWID %1 from %2 is already exposed.

Cause: The document specified is already exposed to the client.

Action: No action is required, as the document is already exposed to the client.
Level: 1

Type: ERROR

Impact: Other

WWS-18014: The collection %1 already contains non-external data.

Cause: The directory specified exists and is not empty.

Action: Check the WebDAV error file in your Personal Page for possible reasons why this error occurred.
Level: 1

Type: ERROR

Impact: Other

WWS-18017: A WebDAV table is corrupt.

Cause: One of the internal WebDAV tables contains invalid data.

Action: Use the DAV Loader utility, wwdav_loader, to repopulate the WebDAV tables with the latest data available from OracleAS Portal.
Level: 1

Type: ERROR

Impact: Other

WWS-18018: The log file is already open.

Cause: An attempt to open a log file failed as it was already open.

Action: If necessary, close the log file.
Level: 1

Type: ERROR

Impact: Other

WWS-18019: Some objects being dropped do not exist.

Cause: An attempt was made to drop repository objects but some of the objects do not exist.

Action: Check your installation.
Level: 1

Type: ERROR

Impact: Other

WWS-18020: %1 already exists.

Cause: The specified resource already exists.

Action: Check the WebDAV error file in your Personal Page for possible reasons why the error occurred.
Level: 1

Type: ERROR

Impact: Other

WWS-18024: %1 does not exist.

Cause: The specified resource was not found.

Action: Check the WebDAV error file in your Personal Page for possible reasons why this error occurred.
Level: 1

Type: ERROR

Impact: Other

WWS-18025: %1 in storage area %2 is currently in use for storage and therefore cannot be deleted.

Cause: An attempt to delete a resource failed because the requested resource was open and in use.

Action: Ensure that the resource is not in use before attempting to delete it.
Level: 1

Type: ERROR

Impact: Other

WWS-18026: %1

Cause: An internal error has occurred.

Action: Check the WebDAV error file in user's Personal Page for possible reasons why this error occurred.
Level: 1

Type: ERROR

Impact: Other

WWS-18027: Cannot return a multistatus response.

Cause: An error occurred while trying to return a multistatus response for the requested operation.

Action: Check the WebDAV error file in the Personal Page and the Oracle HTTP Server error log file for possible reasons why this error occurred.
Level: 1

Type: ERROR

Impact: Other

WWS-18028: Cannot upload document as quota was exceeded.

Cause: An attempt to upload a document failed. The size quota permitted was exceeded.

Action: Check the page group quota and if necessary, free up some space.
Level: 1

Type: ERROR

Impact: Other

WWS-18029: The requested operation is forbidden.

Cause: An attempt to perform an operation failed.

Action: Check the permissions of the user and also whether this operation is permitted.
Level: 1

Type: ERROR

Impact: Other

WWS-18067: User %1 does not have a personal page in which the WebDAV error message log file can be created.

Cause: No Personal Page was found for the logged-in user.

Action: Create a Personal Page for this user, into which the WebDAV error log file can be placed.
Level: 1

Type: ERROR

Impact: Other

WWS-18068: The personal page for %1 does not include an item region in which the WebDAV error message log file can be created.

Cause: No item region was available on the Personal Page for the logged-in user.

Action: Create an item region on the Personal Page for this user, in which the WebDAV error log file can be placed.
Level: 1

Type: ERROR

Impact: Other

WWS-18070: There is no item in which to store error messages.

Cause: A WebDAV error log file item does not exist.

Action: Create the WebDAV error log file item in the user's Personal Page.
Level: 1

Type: ERROR

Impact: Other

WWS-18072: An exception has occurred that was not anticipated: %1

Cause: An internal error occurred.

Action: Check the WebDAV error log file in the user's Personal Page for possible reasons why this error occurred. Also check the Apache error log file.
Level: 1

Type: ERROR

Impact: Other

WWS-18073: An exception occurred while creating or referencing the required preference.

Cause: The preference required for the WebDAV error log file was not created.

Action: Check the Apache error log file for possible reasons why this error occurred.
Level: 1

Type: ERROR

Impact: Other

WWS-18075: The default region of page %1 is incompatible with the object type being placed in it.

Cause: The default region type did not allow file types to be placed in it.

Action: Check the value of the region type and ensure it allows file types to be uploaded.
Level: 1

Type: ERROR

Impact: Other

WWS-18076: The error log item for user %1 cannot be used. It may not exist, cannot be found, or cannot be created.

Cause: An attempt to write to the WebDAV error log file failed. Either the WebDAV error log file does not exist, cannot be found, or cannot be created.

Action: Check whether the WebDAV error log exists.
Level: 1

Type: ERROR

Impact: Other

WWS-18077: No file-based item types are available. File upload via WebDAV is not available in this page group.

Cause: No file-based or image-based item types were specified for the page group.

Action: Select some allowable item types for the page group.
Level: 1

Type: ERROR

Impact: Other

WWS-18085: Expecting data to be returned from query using condition %1, but no data found.

Cause: An internal error occurred.

Action: Check the WebDAV error file in the user's Personal Page for possible reasons why this error occurred.
Level: 1

Type: ERROR

Impact: Other

WWS-18086: An internal module call has been made using an invalid or inconsistent set of parameters. module: %1, parameters: %2.

Cause: It was not possible to create the WebDAV error log file as the user name was not supplied.

Action: Check the Apache error log file for possible reasons why this error occurred.
Level: 1

Type: ERROR

Impact: Other

WWS-18087: An error occurred during the %1 for %2.

Cause: The attempted operation failed to complete.

Action: Check the WebDAV error file in the user's Personal Page for possible reasons why this error occurred.
Level: 1

Type: ERROR

Impact: Other

WWS-18088: An error occurred during the %1 from %2 to %3.

Cause: The attempted operation failed to complete.

Action: Check the WebDAV error file in the user's Personal Page for possible reasons why this error occurred.
Level: 1

Type: ERROR

Impact: Other

WWS-18089: An error occurred during the %1 operation.

Cause: The attempted operation failed to complete.

Action: Check the WebDAV error file in the user's Personal Page for possible reasons why this error occurred.
Level: 1

Type: ERROR

Impact: Other

WWS-18090: Cannot create a lock with scope %1 on the given resource of type %2. Shared or S locks are not permissible and collections or C cannot be locked.

Cause: The attempted operation failed to complete.

Action: Check the WebDAV error file in the user's Personal Page for possible reasons why this error occurred.
Level: 1

Type: ERROR

Impact: Other

WWS-18091: Updating the last-modified date for %1 failed, since it is expected to be collection.

Cause: It was not possible to update the last modified date as it is not a directory.

Action: Check the WebDAV error file in the user's Personal Page for possible reasons why this error occurred.
Level: 1

Type: ERROR

Impact: Other

WWS-18092: Deleting the root path or top-level directory is not allowed.

Cause: The attempted operation is not permitted.

Action: The root path or top-level directory cannot be deleted.
Level: 1

Type: ERROR

Impact: Other

WWS-18093: Writing to the root directory is not allowed.

Cause: The attempted operation is not permitted.

Action: Writing to the root directory cannot be done.
Level: 1

Type: ERROR

Impact: Other

WWS-18094: Moving %1 to %2 with destination name %3 fails. Moving resources across page groups is not allowed.

Cause: An invalid operation was attempted.

Action: Resources cannot be moved across page groups.
Level: 1

Type: ERROR

Impact: Other

WWS-18095: Copying %1 to %2 with destination name %3 failed. Copying resources across page groups is not allowed.

Cause: The attempted operation is not permitted.

Action: Resources cannot be copied across page groups.
Level: 1

Type: ERROR

Impact: Other

WWS-18096: The name %1 in path %2 contains slashes, which is not allowed.

Cause: This name cannot contain slashes.

Action: Remove the slashes from the name.
Level: 1

Type: ERROR

Impact: Other

WWS-18097: The creation of %1 failed, since its parent, %2, is either not a collection or is the root directory.

Cause: The attempted operation failed to complete.

Action: Check the WebDAV error file in the user's Personal Page for possible reasons why this error occurred.
Level: 1

Type: ERROR

Impact: Other

WWS-18098: The resource is already exclusively locked.

Cause: The document specified is checked out.

Action: Check in or undo the checkout for the document to release the lock.
Level: 1

Type: ERROR

Impact: Other

WWS-18099: The resource cannot be locked because it is a collection. Collections cannot be checked out and locked.

Cause: An attempt was made to check out a directory but this is not supported.

Action: Do not check out a directory, as it is not permitted.
Level: 1

Type: ERROR

Impact: Other

WWS-18100: Insufficient write permissions on the folder.

Cause: An attempt was made to modify a directory but the user did not have sufficient permissions.

Action: If applicable, contact the portal administrator and request that privileges be granted to perform this operation.
Level: 1

Type: ERROR

Impact: Other

WWS-18101: WebDAV Path not found.

Cause: The resource cannot be found in the underlying tables.

Action: Check the WebDAV error file in the user's Personal Page for possible reasons why this error occurred.Also check the Apache error log file.
Level: 1

Type: ERROR

Impact: Other

WWS-18102: Cannot validate at the given depth %1.

Cause: It is not possible to check for locks at the given level in the directory hierarchy.

Action: Check the WebDAV error file in the user's Personal Page for possible reasons why this error occurred. Also check the Apache error log file.
Level: 1

Type: ERROR

Impact: Other

WWS-18103: It is not possible to perform the %1 operation on version zero of a document (dav-id = %2). This version is a placeholder for the first complete version of the document, which will only be available once the author has submitted it for review and it has been approved.

Cause: The attempted operation failed. It is not possible to perform any operations on this resource until it has been submitted to the approval system.

Action: To allow modifications, submit it to the approval system and approve it, if the user is not an approver or owner of the document.
Level: 1

Type: ERROR

Impact: Other

WWS-18104: There is not yet a complete initial version of this document; it is still being edited or reviewed. It will become available for general use after it has been approved.

Cause: The attempted operation failed. It is not possible to perform any operations on this resource until it has been submitted to the approval system.

Action: Wait until the document has been submitted to the approval system.
Level: 1

Type: ERROR

Impact: Other

WWS-18105: OracleAS Portal has checked for the existence of WebDAV locks on the resource with dav-id = %1, to a depth of %2, and has found that locks exist. This may have caused OracleAS Portal to terminate the current action.

Cause: The attempted action required implicitly or explicitly that a WebDAV resource be moved or removed, for example, a file or image item. The operation failed because this resource was locked, either by a WebDAV client, or has been checked out. When a resource is locked, it indicates that someone is actively using the resource and therefore it is not appropriate to move or remove the resource.

Action: Determine why the item is locked or checked out and, if safe to do so, unlock or check in the item and attempt the operation again.
Level: 1

Type: ERROR

Impact: Other

WWS-18121: The requested menu action is invalid.

Cause: A menu action specified in the request is not supported by this portal.

Action: Ensure that the Portal WebDAV URL is pointing to the correct address.
Level: 1

Type: ERROR

Impact: Other

WWS-18122: The access control list is not allowed for this document.

Cause: Item Level Security is not enabled on this document.

Action: Contact your portal administrator. Request that Item Level Security is enabled on the document for which access control is required.
Level: 1

Type: ERROR

Impact: Other

WWS-18123: Unknown error occurred while processing the menu request.

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWS-18131: The operation %1 has been attempted on a resource, a version of which is pending approval. The operation is not allowed at this time.

Cause: An attempt was made to update a resource that is pending approval. The version in the approval process remains locked until it is either rejected or approved.

Action: Wait for the resource to be approved or rejected and attempt the operation again.
Level: 1

Type: ERROR

Impact: Other

WWS-18132: Locked: %1

Cause: The given path is locked in WebDAV possibly because the resource is in use or pending approval.

Action: Attempt the operation again after all locks have been removed.
Level: 1

Type: ERROR

Impact: Other

WWS-18133: The item type used for uploading content from DAV has mandatory fields which cannot be set from WebDAV.

Cause: The item type which has been chosen in the page properties for the type of file being uploaded has mandatory fields with no default values. It is not possible to upload items of this type from WebDAV as these fields cannot be set by the WebDAV Client.

Action: Either make these fields optional in the item type properties, specify a default value for these fields in the item type properties, or change the item type used for uploading files of this type in the page properties.
Level: 1

Type: ERROR

Impact: Other

WWS-18136: The Approval/Rejection operation is not allowed for this document.

Cause: The document is not pending approval.

Action: Check that Workflow is enabled and the document is submitted for Approval/Rejection.
Level: 1

Type: ERROR

Impact: Other

WWS-18137: You do not have permission to Approve or Reject this document

Cause: You are not an approver or owner, nor do you have have manage content or administration privileges for this document.

Action: Make sure that you are logged on as a user who has permission to perform this operation.
Level: 1

Type: ERROR

Impact: Other

WWS-18138: The page does not include an editable item region to upload the file.

Cause: No editable item region was available on the page.

Action: Create an editable item region on the page or mark an existing one as editable.
Level: 1

Type: ERROR

Impact: Other

WWS-18139: The Submit for Approval operation is not allowed for this document.

Cause: The document is not in draft status.

Action: Check that Workflow is enabled and the document is in draft status.
Level: 1

Type: ERROR

Impact: Other

WWS-18140: Synchronizing of the Item types for WebDAV Upload in the imported page has not been performed.

Cause: The WebDAV item types selected for use in the imported page could not be updated to reflect the new settings in the portal.

Action: In the page properties of the imported page, set the WebDAV itemtype settings to the desired values.
Level: 1

Type: ERROR

Impact: Other

WWS-19679: The item is already approved.

Cause: The item cannot be approved or rejected because it has already been approved.

Action: Refresh your browser window to update your notifications. The item you were trying to approve or reject will no longer be listed.
Level: 1

Type: ERROR

Impact: Other

WWS-19680: Item has been rejected!

Cause: The item cannot be approved or rejected because it has already been rejected.

Action: Refresh your browser window to update your notifications. The item you were trying to approve or reject will no longer be listed.
Level: 1

Type: ERROR

Impact: Other

WWS-19699: You do not have permission to view this item.

Cause: Viewing the item required an appropriate privilege.

Action: Ask the page group administrator or page manager to grant you the appropriate privilege.
Level: 1

Type: ERROR

Impact: Other

WWS-19722: There are pending approvals in this routing process; the step cannot be moved.

Cause: The change was rejected because the approval process definition had items pending approval.

Action: Wait until all the pending items are approved, then try again.
Level: 1

Type: ERROR

Impact: Other

WWS-19746: You have entered invalid values for the number of notification items, the subscription time, or the subscription cache time.

Cause: A non-numeric value was entered.

Action: Enter a valid number value.
Level: 1

Type: ERROR

Impact: Other

WWS-20331: You must first specify an HTML Content Layout.

Cause: No valid HTML Content Layout was selected.

Action: Select an HTML Content Layout from the list or create one first if there is none available in the list.
Level: 1

Type: ERROR

Impact: Other

WWS-20369: Webcache could not access <a href=\"%1\">this URL</a>

Cause: An exception was raised by the <esi:include> tag while fetching the contents of this item. Typically, this is because the item's URL is not accessible from the Web cache.

Action: Verify that the URL is valid and accessible from your browser. If the Web page displays properly, then verify the proxy settings in the Web cache. Note that URLs that require HTTP authentication headers are not supported.
Level: 1

Type: ERROR

Impact: Other

WWS-22200: The value entered is invalid. Choose a valid value from the LOV.

Cause: The value entered is not one of the values from the LOV.

Action: Enter a valid value from the LOV.
Level: 1

Type: ERROR

Impact: Other

WWS-22201: You cannot copy the item because the category to which it belongs does not exist in the destination page group.

Cause: The category that the item belongs to does not exist in the destination page group.

Action: Re-create the category in the destination page group or assign the item to a shared category.
Level: 1

Type: ERROR

Impact: Other

WWS-22202: You cannot copy the item because one or more of the perspectives associated with it does not exist in the destination page group.

Cause: The perspective attached to the item does not exist in the destination page group.

Action: Re-create the perspective in the destination page group, detach the perspective from the item, or attach a shared perspective to the item.
Level: 1

Type: ERROR

Impact: Other

WWS-22203: You cannot move the item because the category to which it belongs does not exist in the destination page group.

Cause: The category that the item belongs to does not exist in the destination page group.

Action: Re-create the category in the destination page group or assign the item to a shared category.
Level: 1

Type: ERROR

Impact: Other

WWS-22204: You cannot move the item because one or more of the perspectives associated with it does not exist in the destination page group.

Cause: The perspective attached to the item does not exist in the destination page group.

Action: Re-create the perspective in the destination page group, detach the perspective from the item, or attach a shared perspective to the item.
Level: 1

Type: ERROR

Impact: Other

WWS-22208: The message cannot be added to the queue as the queue does not exist.

Cause: The specified queue does not exist.

Action: Create the queue before attempting to add a message to the queue.
Level: 1

Type: ERROR

Impact: Other

WWS-22209: The height value is invalid. Value should be at least 1 pixel.

Cause: An invalid value was entered for the portlet height.

Action: Enter a positive number for the portlet height.
Level: 1

Type: ERROR

Impact: Other

WWS-22210: Item is not checked out.

Cause: The item types for WebDAV upload in the imported page are not synchronized.

Action: Check out the item, make the necessary changes, then check it in.
Level: 1

Type: ERROR

Impact: Other

WWS-22211: Item is not enabled for checkout.

Cause: An attempt was made to check out an item that was not enabled for checkout.

Action: Enable the item for checkout, then check out the item.
Level: 1

Type: ERROR

Impact: Other

WWS-22212: The image that you are trying to reference does not exist.

Cause: The image does not exist in the Oracle Application Server Metadata Repository.

Action: Supply an image that does exist.
Level: 1

Type: ERROR

Impact: Other

WWS-22213: An invalid path was supplied to the Default Content attribute.

Cause: The path supplied to the core attribute was invalid.

Action: Select a value from the LOV or supply a valid value.
Level: 1

Type: ERROR

Impact: Other

WWS-22214: An invalid path was supplied to the Item Link attribute.

Cause: The path supplied to the core attribute was invalid.

Action: Select a value from the LOV or supply a valid value.
Level: 1

Type: ERROR

Impact: Other

WWS-22215: An invalid number was entered for the version number attribute.

Cause: The number supplied to the version number attribute was either not greater than zero or is a value that has already been used up by an existing version.

Action: Supply a positive number that is unique across this item.
Level: 1

Type: ERROR

Impact: Other

WWS-22216: Portal ESE Search : The portal event is acting on an object that cannot be found.

Cause: The portal event handler is trying to find the object being processed, but it cannot be found.

Action: Check your configuration. If you cannot resolve this issue, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWS-22217: Privileges cannot be assigned to the PUBLIC user.

Cause: An attempt was made to assign an item level privilege to the PUBLIC user. This is not allowed.

Action: Assign the item level privilege to users and groups other than PUBLIC.
Level: 1

Type: ERROR

Impact: Other

WWS-22218: Another user is drafting an update of this item. Wait to update until that draft is published or deleted.

Cause: An attempt was made to update an item for which a draft version existed, although only one draft version of an item can exist.

Action: Wait until that draft is published or deleted.
Level: 1

Type: ERROR

Impact: Other

WWS-22219: An attempt was made to unzip an item that is pending approval or has a draft version. You must wait until the item is approved or rejected, or until the draft is published or deleted.

Cause: An attempt was made to unzip an item that is pending approval or is a draft item.

Action: If it is an item that is pending approval, unzip it after it is approved or rejected. If it is a draft item, unzip it after it is published or deleted.
Level: 1

Type: ERROR

Impact: Other

WWS-22220: Invalid portlet caching period. Value should be at least 1 minute.

Cause: You entered an invalid value for the portlet caching period.

Action: Enter a portlet caching period of at least 1 minute.
Level: 1

Type: ERROR

Impact: Other

WWS-22221: The delete or purge did not succeed. The item or one of its associated sub-items is checked out by another user.

Cause: An item cannot be deleted or purged when the item or one of its associated sub-items is checked out by another user.

Action: Wait to perform the action until the other user checks in the item or its associated sub-item.
Level: 1

Type: ERROR

Impact: Other

WWS-22222: You cannot modify the Access Settings of an item on a page that is cached at the system level.

Cause: You attempted to modify the access settings of an item on a page cached at the system level, which affects all users. Item Level Security is disabled for pages cached at the system level.

Action: If you require Item Level Security on this item, then choose a different caching option for the page. Choose either user-level caching or no caching.
Level: 1

Type: ERROR

Impact: Other

WWS-22223: This item does not have any translatable attribute and hence, cannot be edited in the nondefault language of the page group.

Cause: You attempted to edit an item that does not have any translatable attribute in the nondefault language.

Action: Edit the item in the default language of the page group and make the necessary changes.
Level: 1

Type: ERROR

Impact: Other

WWS-22224: An attempt was made to set an invalid publish date.

Cause: The publish date for an item must be immediately or anytime greater than 2 minutes from immediately. For example, if the publish date is currently today at 12:00, and the publish date is set for today at 12:02, an exception is thrown and this error message is rendered.

Action: Reset the item's publish date to either immediately or more than 2 minutes from immediately.
Level: 1

Type: ERROR

Impact: Other

WWS-22225: You cannot copy the page because the HTML template used by one of the regions of the page or its sub-pages is not from the Shared Objects page group.

Cause: The HTML template used by a region on the page or its sub-pages is not from the Shared Objects page group.

Action: Move the HTML template to the Shared Objects page group.
Level: 1

Type: ERROR

Impact: Other

WWS-22226: Item type cannot be deleted because items are based on it.

Cause: Deleting an item type also deletes all items that are based on the type. Though you may have permission to delete item types, you do not have permission to delete specific items.

Action: Verify that only non-essential content is based on the item type. Obtain the required privilege level to delete items. Then, try again.
Level: 1

Type: ERROR

Impact: Other

WWS-22227: Page type cannot be deleted because pages are based on it.

Cause: Deleting a page type also deletes all pages that are based on the type. Though you may have permission to delete page types, you may not have permission to delete specific pages.

Action: Verify that only non-essential pages are based on the page type. Obtain the required privilege level to delete pages. Then, try again.
Level: 1

Type: ERROR

Impact: Other

WWS-22228: The action cannot be completed because a sub-item of the item has a status of Pending.

Cause: The item you tried to modify has one or more sub-items pending approval. You cannot perform this action on items with sub-items that are pending approval.

Action: Complete the approval process on the sub-item and try again.
Level: 1

Type: ERROR

Impact: Other

WWS-22229: Copy cannot be completed because a sub-item of the item has a status of Pending.

Cause: The item you tried to copy has one or more sub-items pending approval. You cannot copy items with sub-items that are pending approval.

Action: Complete the approval process on the sub-item and try again.
Level: 1

Type: ERROR

Impact: Other

WWS-22230: Move cannot be completed because a sub-item of the item has a status of Pending.

Cause: The item you tried to move to another page has one or more sub-items pending approval. You cannot move items to another page when they have associated sub-items that are pending approval. However, you can move such items within the same page.

Action: Complete the approval process on the sub-item and try again.
Level: 1

Type: ERROR

Impact: Other

WWS-22231: Delete cannot be completed because a sub-item of the item has a status of Pending.

Cause: The item you tried to delete has one or more sub-items pending approval. You cannot delete items with sub-items that are pending approval.

Action: Complete the approval process on the sub-item and try again.
Level: 1

Type: ERROR

Impact: Other

WWS-22232: The attribute display type cannot be changed from a multi-line to a single-line because items are based on the item type that uses this attribute.

Cause: An attempt was made to switch an attribute from a multi-line to a single-line display type. This action was prevented because items exist that are based on the item types that use this attribute. This action can be completed successfully only after the attribute has been detached from the item types that use it.

Action: Detach the attribute from the item types that use it, and try again. Detaching an attribute from an item type means that all items based on the type lose the values that were entered for the attribute.
Level: 1

Type: ERROR

Impact: Other

WWS-22233: Copy cannot be completed because a sub-item of an item on the page has a status of Pending.

Cause: An attempt was made to copy a page containing items with sub-items pending approval.

Action: Complete the approval process on the sub-items, and try again.
Level: 1

Type: ERROR

Impact: Other

WWS-22234: Deleted items cannot be unzipped. Undelete the item to unzip it.

Cause: An attempt was made to unzip a deleted item.

Action: Unzip the item after it is undeleted.
Level: 1

Type: ERROR

Impact: Other

WWS-22235: %1 does not exist.

Cause: The object cannot be found in the transport set.

Action: Export the transport set again, including this required object.
Level: 1

Type: ERROR

Impact: Other

WWS-22236: BPEL process name cannot be null.

Cause: An attempt was made to create or edit a BPEL process without specifying a name.

Action: Enter a name for the BPEL process.
Level: 1

Type: ERROR

Impact: Other

WWS-22237: BPEL process deployment location cannot be null.

Cause: An attempt was made to create or edit a BPEL process without specifying its process deployment location.

Action: Enter the deployment location for the BPEL process.
Level: 1

Type: ERROR

Impact: Other

WWS-22238: BPEL process WSDL location cannot be null.

Cause: An attempt was made to create or edit a BPEL process without specifying its WSDL location.

Action: Enter the WSDL location for the BPEL process.
Level: 1

Type: ERROR

Impact: Other

WWS-22239: BPEL process operation cannot be null.

Cause: An attempt was made to create or edit a BPEL process without specifying its operation.

Action: Enter the operation for the BPEL process.
Level: 1

Type: ERROR

Impact: Other

WWS-22240: This BPEL process name is already used. Use another name.

Cause: An attempt was made to create or edit a BPEL process with a name that is already being used for another BPEL process.

Action: Enter a different, unique name for BPEL process.
Level: 1

Type: ERROR

Impact: Other

WWS-22241: The specified BPEL process is not available.

Cause: A process was specified that did not exist.

Action: Specify a different process.
Level: 1

Type: ERROR

Impact: Other

WWS-22242: Specify a name without spaces or special characters.

Cause: The name entered contains invalid characters.

Action: Specify a valid name. Valid characters are [A-Z], [a-z], [0-9] and "_".
Level: 1

Type: ERROR

Impact: Other

WWS-22243: Specify a description that does not contain the following characters: \ / : * ? \" < > | , & # %

Cause: The description entered contains invalid characters.

Action: Specify a valid description. The description may not contain the following characters: \ / : * ? " < > | , & # %
Level: 1

Type: ERROR

Impact: Other

WWS-22244: Specify a valid deployment location.

Cause: The deployment location entered is not a valid URL.

Action: Specify a valid URL for deployment location.
Level: 1

Type: ERROR

Impact: Other

WWS-22245: Specify a valid process WSDL location.

Cause: The process WSDL location entered is not a valid URL.

Action: Specify a valid URL for process WSDL location.
Level: 1

Type: ERROR

Impact: Other

WWS-22246: Specify an operation without spaces or special characters.

Cause: The operation entered contains invalid characters.

Action: Specify a valid operation. Valid characters are [A-Z], [a-z], [0-9] and "_".
Level: 1

Type: ERROR

Impact: Other

WWS-22247: BPEL process that you are editing is not editable.

Cause: The process specified is no longer editable. This process is being used by one or more pages or page groups.

Action: Remove its associations with pages and page groups and try again.
Level: 1

Type: ERROR

Impact: Other

WWS-22248: BPEL process that you are removing is not removable.

Cause: The process specified cannot be removed. This process is being used by one or more pages or page groups.

Action: Remove its associations with pages and page group and then try again.
Level: 1

Type: ERROR

Impact: Other

WWS-22249: Add Tab cannot be completed because the region contains an item that has a sub-item with status of Pending.

Cause: An attempt was made to add a tab to a region where one or more items had sub-items pending approval.

Action: Complete the approval process on the sub-item and try again.
Level: 1

Type: ERROR

Impact: Other

WWS-22250: Process WSDL Location is not valid.

Cause: The URL specified in the WSDL Location is not reachable.

Action: Check if the URL specified is reachable through the proxy configured in Portal Global Settings.If the URL is SSL enabled, then check for the valid certificates in the database wallet.
Level: 1

Type: ERROR

Impact: Other

WWS-22251: Process Name not found in specified WSDL location.

Cause: Process Name not found in specified WSDL location.

Action: Ensure that the process name given is associated with the WSDL.
Level: 1

Type: ERROR

Impact: Other

WWS-22252: Process Deployment Location not found in specified WSDL location.

Cause: Process Deployment Location not found in specified WSDL location.

Action: Ensure that the Process Deployment Location is associated with the WSDL.
Level: 1

Type: ERROR

Impact: Other

WWS-22253: Process Operation not found in specified WSDL location.

Cause: Process Operation not found in specified WSDL location.

Action: Ensure that the Operation Name is associated with the WSDL.
Level: 1

Type: ERROR

Impact: Other

WWS-22254: Unexpected error in processing input parameters - %1.

Cause: Unexpected error in processing input parameters.

Action: Refer to database error messages guide for detailed information on the error. If the same error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWS-22255: BPEL is not configured for this instance. Check the Administrator's guide for steps to enable it.

Cause: BPEL is not enabled for this portal instance.

Action: Refer to Administrator's guide on how to enable BPEL. This is a post-installation step and needs to be performed manually.
Level: 1

Type: ERROR

Impact: Other

WWS-22257: URL supplied not a callback URL. Portal callback URL construct is like protocol://host:port/bpel/WSPortalApproval.

Cause: URL supplied is not a callback URL. Enter proper portal callback URL and then register.

Action: Portal callback URL construct is like protocol://host:port/bpel/WSPortalApproval. If callback webservice is not deployed yet check Administrator's guide for steps to deploy it.
Level: 1

Type: ERROR

Impact: Other

WWS-22258: Datasource connection maintained for the Callback Webservice is not pointing to %1_APPROVAL schema.

Cause: Datasource connection maintained for the Callback Webservice at the WLS is not pointing to proper APPROVAL schema.

Action: Check Administrator's guide for steps to maintain the connection.
Level: 1

Type: ERROR

Impact: Other

WWS-22260: The value entered for the PL/SQL code exceeds the 2000 characters limit. Reduce it and try again.

Cause: The size of the PL/SQL content entered was exceeding 2000 characters.

Action: Reduce the content to be less than or equal to 2000 characters.
Level: 1

Type: ERROR

Impact: Other

WWS-22507: Item does not exist.

Cause: An action was attempted on an item that no longer exists.

Action: Refresh the page so that it displays the current content.
Level: 1

Type: ERROR

Impact: Other

WWS-22517: An error has occurred while rendering the URL associated with the page. %1

Cause: An error occurred while redirecting to the URL associated with the current page.

Action: Check the validity of the URL associated with the current page.
Level: 1

Type: ERROR

Impact: Other

WWS-22518: An error has occurred while executing the PL/SQL associated with the page. %1

Cause: The PL/SQL code associated with the current page executed with errors.

Action: Check the validity of the PL/SQL code that executes when the current page is viewed.
Level: 1

Type: ERROR

Impact: Other

WWS-22519: The attribute does not exist.

Cause: No value was found for the custom attribute associated with the current page.

Action: Edit the properties for the current page, and provide values for the custom attributes associated with it.
Level: 1

Type: ERROR

Impact: Other

WWS-23017: Invalid search pattern specified

Cause: A null value is specified for the search pattern.

Action: Specify a non-null value for the search pattern.
Level: 1

Type: ERROR

Impact: Other

WWS-25824: The specified name is already in use.

Cause: The category/perspective name entered is not unique within this namespace.

Action: Enter a unique category/perspective name, one that is not used by another category, perspective, page or tab with the same parent.
Level: 1

Type: ERROR

Impact: Other

WWS-25827: This portlet cannot search any of the submitted page groups.

Cause: A search submission portlet submitted a search to a search results portlet. The results portlet is customized to show results from a specific set of page groups and these do not include any of the page groups chosen in the submission portlet.

Action: Change the list of page groups chosen for the submission portlet or those chosen for the results portlet so that both portlets refer to a common set of page groups.
Level: 1

Type: ERROR

Impact: Other

WWS-25828: This portlet cannot search all the submitted page groups.

Cause: A search submission portlet submitted a search to a search results portlet. The page groups selected for the results portlet were not all the same as those selected for the submission portlet. Only those page groups common to the submission portlet and the results portlet were searched.

Action: Change the list of page groups chosen for the submission portlet or those chosen for the results portlet so that both portlets refer to a common set of page groups.
Level: 1

Type: ERROR

Impact: Other

WWS-25829: This portlet cannot search any of the default page groups from the submitted portlet.

Cause: A search submission portlet submitted a search to a search results portlet. The submission portlet searched a list of page groups that were chosen as the defaults for that portlet. The results portlet is customized to show results from a different set of page groups, not one of which was common to the submission portlet.

Action: Change the default list of page groups for the submission portlet, or change the customizations in the Edit Defaults of the results portlet, so that both portlets refer to a common set of page groups.
Level: 1

Type: ERROR

Impact: Other

WWS-25830: This portlet cannot search all of the default page groups from the submitted portlet.

Cause: A search submission portlet submitted a search to a search results portlet. The page groups identified for the submission portlet are different from those identified for the results portlet. Only the page groups common to the submission portlet's default page groups and the result portlet's customizations are searched.

Action: Change the default list of page groups for the submission portlet, or change the customizations in the Edit Defaults of the results portlet, so that both portlets refer to a common set of page groups.
Level: 1

Type: ERROR

Impact: Other

WWS-25838: The expiration time must be an integer value between 1 and 1440 minutes.

Cause: An expiration time was specified that is not an integer between 1 and 1440 minutes.

Action: Enter an expiration time that is an integer between 1 and 1440 minutes.
Level: 1

Type: ERROR

Impact: Other

WWS-25845: The number of saved searches to display must be a number.

Cause: The value for the number of saved searches to display was invalid, it must be a number.

Action: Specify the number of saved searches to display
Level: 1

Type: ERROR

Impact: Other

WWS-25883: Some or all of the Oracle Text indexes are missing or invalid. Oracle Text searching is disabled.

Cause: Oracle Text search capabilities could not be used because not all the Oracle Text indexes were present and valid.

Action: Ensure that the Oracle Text indexes are present and valid. If necessary, create or re-create these indexes. For more information, refer to the Oracle Portal Configuration Guide.
Level: 1

Type: ERROR

Impact: Other

WWS-25902: An error occurred while creating Oracle Text object %1.

Cause: Oracle Text encountered an error while creating the preference or section group.

Action: Review the diagnostics logs for other messages. Correct these errors, then try again.
Level: 1

Type: ERROR

Impact: Other

WWS-25903: An error occurred while dropping Oracle Text object %1.

Cause: Oracle Text encountered an error while removing the preference or section group.

Action: Review the diagnostics logs for other messages. Correct these errors, then try again.
Level: 1

Type: ERROR

Impact: Other

WWS-25907: %1 cannot be used in search criteria.

Cause: The specified search attribute does not exist in the Oracle Text indexes.

Action: The Oracle Text indexes need to be updated to include the new attribute. Oracle Text indexes are updated automatically. Either wait until the indexes are updated, or use a different search attribute.
Level: 1

Type: ERROR

Impact: Other

WWS-25934: The search query contained invalid query syntax: %1

Cause: This usually occurs when a Query Language operator was used and the search expression contained invalid Oracle Text syntax.

Action: Correct the query language syntax.
Level: 1

Type: ERROR

Impact: Other

WWS-25976: The basic search results page is missing.

Cause: The page selected to display results from Basic Search portlets and Basic Search Box items is missing.

Action: Specify a valid page for basic search results in the Search tab of the Global Settings screen.
Level: 1

Type: ERROR

Impact: Other

WWS-25977: The search results page is missing.

Cause: The page selected to display results from Advanced, Custom and Saved Search portlets was missing.

Action: Specify a valid page in the Search tab of the Global Settings screen.
Level: 1

Type: ERROR

Impact: Other

WWS-25978: The destination page for Advanced Search links is missing.

Cause: The destination page selected for Advanced Search links is missing. Links to advanced search pages cannot be displayed.

Action: Specify a valid page for Advanced Search links in the Search tab of the Global Settings screen.
Level: 1

Type: ERROR

Impact: Other

WWS-25979: Page selected to display search results is missing.

Cause: The page selected to display results from this search portlet is missing.

Action: Edit the defaults of this portlet and specify a valid search results page in the Results Display tab.
Level: 1

Type: ERROR

Impact: Other

WWS-25980: Display name for the saved search is missing

Cause: A display name for the saved search has not been provided.

Action: Enter a display name for the saved search.
Level: 1

Type: ERROR

Impact: Other

WWS-25981: You do not have permission to view this item.

Cause: Viewing the item required an appropriate privilege.

Action: Ask the page group administrator or page manager to grant you the appropriate privilege.
Level: 1

Type: ERROR

Impact: Other

WWS-25982: A search parameter value is invalid.

Cause: A value specified for a search parameter in the URL is incorrect.

Action: Specify a valid value for the search parameter.
Level: 1

Type: ERROR

Impact: Other

WWS-25983: You do not have access to this page.

Cause: You need to be logged in to access this page.

Action: Log in to Oracle Portal as a valid user.
Level: 1

Type: ERROR

Impact: Other

WWS-25984: No HTML content to display.

Cause: The file was either empty or could not be displayed as HTML.

Action: Verify that the file item has a format that can be displayed as HTML.
Level: 1

Type: ERROR

Impact: Other

WWS-25985: No Themes to display.

Cause: The file was either empty or Oracle Text could not extract themes from the content.

Action: Verify that the file item has a format that can be processed by Oracle Text.
Level: 1

Type: ERROR

Impact: Other

WWS-25986: No gists to display.

Cause: The file was either empty or Oracle Text could not extract gists from the content.

Action: Verify that the file item has a format that can be processed by Oracle Text.
Level: 1

Type: ERROR

Impact: Other

WWS-26000: Oracle Text Base URL cannot be null.

Cause: No value is specified for the Oracle Text Base URL.

Action: Specify a value for the Oracle Text Base URL. Typically, this is the URL to the Portal instance, up to and including the Portal DAD. For example, http://hostname.domain:port/pls/dad/.
Level: 1

Type: ERROR

Impact: Other

WWS-26001: Link text for Internet Search Engine cannot be null if a URL is specified.

Cause: A URL was specified for the Internet Search Engine, but link text was not specified.

Action: Specify link text for the Internet Search Engine.
Level: 1

Type: ERROR

Impact: Other

WWS-26119: Unable to render XML Schema Document.

Cause: An internal error caused the generation of the requested XSD to fail.

Action: Check your configuration. If you cannot resolve the issue, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWS-26120: Resource not found

Cause: Either 1. The Resource has been deleted or moved during the operation and so can no longer be found, or 2. The configuration of the Web server listener is not correct.

Action: This error is expected to occur infrequently if the Portal is being used to move or delete content while the Search Engine is indexing content. If this occurs frequently, check your configuration.
Level: 1

Type: ERROR

Impact: Other

WWS-26121: Permission denied

Cause: You cannot perform this action because of one of the following reasons: 1. The Search Engine has not authenticated with Oracle Internet Directory and secure crawl is enabled, or 2. Secure crawling is disabled and the requested resource is not public, or 3. The configuration of the Web server listener is not correct

Action: Check the secure crawling configuration in the Global Settings and whether the Search Engine has authenticated with Oracle Internet Directory successfully, if applicable. If this is still not solved and the requested resource is accessible through the Portal UI to an unauthenticated user, check your configuration.
Level: 1

Type: ERROR

Impact: Other

WWS-26122: Internal exception in top level crawler procedure.

Cause: An internal error has caused the entry point to the XML generation to fail.

Action: Check your configuration. If you cannot resolve the issue, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWS-26123: Unexpected exception while rendering XML

Cause: An internal error has caused the code which outputs the XML to fail.

Action: If you cannot resolve the issue, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWS-28652: The bulk action cannot be performed on all the selected objects.

Cause: One or more of the selected objects did not meet the required conditions for the action to be performed.

Action: Ensure that the objects are in the correct state, and have the correct permissions applied to them so that the required action can be performed.
Level: 1

Type: ERROR

Impact: Other

WWS-30071: Item %1 from page group %2 is not a valid image.

Cause: The item specified is not a valid image.

Action: Choose a valid image.
Level: 1

Type: ERROR

Impact: Other

WWS-30074: The value for results per page must be an integer greater than zero.

Cause: A value specified for the results-per-page is not an integer greater than zero.

Action: Specify a value for the results-per-page that is an integer greater than zero.
Level: 1

Type: ERROR

Impact: Other

WWS-30502: The page ID does not exist.

Cause: The page that this item belongs to does not exist.

Action: Refresh the page, and try to edit the item again.
Level: 1

Type: ERROR

Impact: Other

WWS-30518: The item ID does not exist.

Cause: This item does not exist.

Action: Refresh the page, and try to edit the item again.
Level: 1

Type: ERROR

Impact: Other

WWS-30529: You must specify a valid Style name.

Cause: This error occurs when an internal API is called to retrieve a style setting value and the setting name or its type are not provided.

Action: Provide the setting name and type.
Level: 1

Type: ERROR

Impact: Other

WWS-30534: You cannot move a page into itself.

Cause: An attempt was made to make a page the sub-page of itself.

Action: Choose another page as the parent of the page.
Level: 1

Type: ERROR

Impact: Other

WWS-30535: You cannot move the root page of a page group.

Cause: Moving the root page of a page group is not permitted.

Action: Consider moving each of the root page's sub-pages, or creating a new page group.
Level: 1

Type: ERROR

Impact: Other

WWS-30538: Another user has updated the value of this item.

Cause: This error occurs when one user attempts to update page group properties at the same time as another user.

Action: Close the page group properties screen, then reload it.
Level: 1

Type: ERROR

Impact: Other

WWS-30541: Specify a name.

Cause: A name was not provided.

Action: Make sure that the Name field is not left blank.
Level: 1

Type: ERROR

Impact: Other

WWS-30542: Specify a display name.

Cause: A display name was not provided.

Action: Make sure that the Display Name field is not left blank.
Level: 1

Type: ERROR

Impact: Other

WWS-30558: An error occurred while executing the PL/SQL associated with the item. %1

Cause: The PL/SQL code associated with the item executed with errors.

Action: Check the validity of the PL/SQL code that executes when the item is viewed.
Level: 1

Type: ERROR

Impact: Other

WWS-30563: You cannot copy the page because the category used by the page or its sub-pages is not from the Shared Objects page group.

Cause: The category used by the page or its sub-pages is not from the Shared Objects page group.

Action: Move the category to the Shared Objects page group.
Level: 1

Type: ERROR

Impact: Other

WWS-30573: You do not have permission to perform this operation.

Cause: The user does not have permission to perform this operation.

Action: Make sure that you are logged on as the user who has permission to perform the operation.
Level: 1

Type: ERROR

Impact: Other

WWS-30582: You cannot copy the page because the style used by the page or its sub-pages is not from the Shared Objects page group.

Cause: The style used by the page or its sub-pages is not from the Shared Objects page group.

Action: Move the style to the Shared Objects page group.
Level: 1

Type: ERROR

Impact: Other

WWS-30584: The action cannot be completed because the value entered for the TEXT attribute is too large.

Cause: The value entered for the TEXT attribute exceeds 32 KB.

Action: Enter a text value that does not exceed 32 KB.
Level: 1

Type: ERROR

Impact: Other

WWS-30586: The item name must be unique in this page.

Cause: The name specified for the item is not unique.

Action: Specify a name that is unique across all the items on this page as well as all the tabs and sub-pages of this page.
Level: 1

Type: ERROR

Impact: Other

WWS-30589: A category with the specified name already exists in this namespace.

Cause: The category name entered is not unique within this namespace.

Action: Enter a unique category name that is not already used by another category with the same parent.
Level: 1

Type: ERROR

Impact: Other

WWS-30590: A perspective with the specified name already exists in this namespace.

Cause: The perspective name entered is not unique within this namespace.

Action: Enter a unique perspective name that is not already used by another perspective with the same parent.
Level: 1

Type: ERROR

Impact: Other

WWS-30593: Invalid number format entered.

Cause: An invalid value was entered for a number attribute. It is possible that the LOV associated with the attribute returns incorrect values.

Action: Request that the owner of the LOV change it to return the correct type of values.
Level: 1

Type: ERROR

Impact: Other

WWS-30595: A style with the specified name already exists

Cause: The style name entered is not unique.

Action: Enter a unique style name that is not used in the current page group nor in the Shared Objects page group.
Level: 1

Type: ERROR

Impact: Other

WWS-30601: The date entered is invalid.

Cause: An invalid date was entered.

Action: Enter a valid date.
Level: 1

Type: ERROR

Impact: Other

WWS-30603: Invalid value entered for color.

Cause: An invalid value was entered in the style's color field.

Action: Enter a valid color value.
Level: 1

Type: ERROR

Impact: Other

WWS-30617: At least one search term is required.

Cause: No search criteria were provided for the search.

Action: Enter some search criteria and submit the search.
Level: 1

Type: ERROR

Impact: Other

WWS-30626: You cannot copy the page because the Portal template which the page or its sub-pages are based on is not from the Shared Objects page group.

Cause: The Portal template that the page and its sub-pages are based on is not from the Shared Objects page group.

Action: Copy the Portal template to the Shared Objects page group and change the page to be based on it.
Level: 1

Type: ERROR

Impact: Other

WWS-30627: No language specified for translation

Cause: No language was specified in the internal API that creates translations for the page group. One way to avoid this is to create translations through the user interface.

Action: Specify a language for translation.
Level: 1

Type: ERROR

Impact: Other

WWS-30628: Specify a name that does not contain the following characters: \ / : * ? \" < > | , & # %

Cause: A name was entered that contained invalid characters.

Action: Specify a valid name. The name must not contain the following characters: \ / : * ? " < > | , & # %
Level: 1

Type: ERROR

Impact: Other

WWS-30629: Specify a name without spaces or special characters.

Cause: The name entered contains invalid characters.

Action: Specify a valid name. Valid characters are [A-Z], [a-z], [0-9] and "_".
Level: 1

Type: ERROR

Impact: Other

WWS-30630: An attribute with the specified name already exists.

Cause: The attribute name entered is not unique.

Action: Enter a unique attribute name, one that is not used in the current page group nor in the Shared Objects page group.
Level: 1

Type: ERROR

Impact: Other

WWS-30632: You cannot copy the page because the type of the page or its sub-pages is not from the Shared Objects page group.

Cause: The type of the page or its sub-pages is not from the Shared Objects page group.

Action: Move the page type to the Shared Objects page group.
Level: 1

Type: ERROR

Impact: Other

WWS-30640: The Page Group's default language cannot be deleted.

Cause: An attempt was made to remove a page group's default language. This action is not permitted.

Action: Some translation languages can be removed. For a list of these, go to the Translations tab of page group properties.
Level: 1

Type: ERROR

Impact: Other

WWS-30641: The Page Group ID does not exist.

Cause: An invalid page group ID was entered.

Action: Enter a valid page group ID.
Level: 1

Type: ERROR

Impact: Other

WWS-30644: A page group with the specified name already exists.

Cause: The page group name entered is not unique.

Action: Enter a unique page group name.
Level: 1

Type: ERROR

Impact: Other

WWS-30660: Invalid date: %1

Cause: An invalid date value was entered for the search attribute.

Action: Enter a valid date value.
Level: 1

Type: ERROR

Impact: Other

WWS-30661: Invalid number: %1

Cause: An invalid number value was entered for the search attribute.

Action: Enter a valid number value.
Level: 1

Type: ERROR

Impact: Other

WWS-30662: Procedure Call and Link Text cannot be null. Enter valid values for both of these fields.

Cause: A value was not entered for the Procedure Call or the Link Text.

Action: Enter values for both fields. If you do not want to add a procedure call to the page type, ensure that both fields are null.
Level: 1

Type: ERROR

Impact: Other

WWS-30663: A URL is not specified for this page.

Cause: The URL for a URL page is not specified.

Action: Specify a URL for the URL page.
Level: 1

Type: ERROR

Impact: Other

WWS-30664: Valid PL/SQL code is not specified for this page.

Cause: The PL/SQL code for a PL/SQL page is not specified.

Action: Specify PL/SQL code for the PL/SQL page.
Level: 1

Type: ERROR

Impact: Other

WWS-30666: You cannot copy the page because the style used by one of the regions on the page or its sub-pages is not from the Shared Objects page group.

Cause: The style used by a region on the page or its sub-pages is not from the Shared Objects page group.

Action: Move the style to the Shared Objects page group.
Level: 1

Type: ERROR

Impact: Other

WWS-30667: Saved search name already exists. Enter a new name.

Cause: The name given for the saved search already exists.

Action: Specify a unique name for the saved search.
Level: 1

Type: ERROR

Impact: Other

WWS-30670: You cannot copy the page because the item attribute parameter of the item template used by the page or its sub-pages is not from the Shared Objects page group.

Cause: The item attribute parameter of the item template used by the page or its sub-pages is not from the Shared Objects page group.

Action: Copy the attribute to the Shared Objects page group.
Level: 1

Type: ERROR

Impact: Other

WWS-30671: You cannot copy the page because an attribute associated with one of the regions on the page or its sub-pages is not from the Shared Objects page group.

Cause: The attribute associated to a region on the page or its sub-pages is not from the Shared Objects page group.

Action: Move the attribute to the Shared Objects page group.
Level: 1

Type: ERROR

Impact: Other

WWS-30675: Display Name cannot be null.

Cause: Nothing was entered in the Display Name field.

Action: Enter a valid Display Name.
Level: 1

Type: ERROR

Impact: Other

WWS-30676: You cannot copy the page because one or more of the perspectives associated with the page or its sub-pages are not from the Shared Objects page group.

Cause: The perspective attached to the page or its sub-pages is not from the Shared Objects page group.

Action: Move the perspective to the Shared Objects page group.
Level: 1

Type: ERROR

Impact: Other

WWS-30677: You cannot copy the page because the HTML page skin used by the page or its sub-pages is not from the Shared Objects page group.

Cause: The HTML page skin used by the page or its sub-pages is not from the Shared Objects page group.

Action: Move the HTML page skin to the Shared Objects page group.
Level: 1

Type: ERROR

Impact: Other

WWS-30680: Page group not found.

Cause: An attempt was made to move an item to a nonexistent page group.

Action: Pass in a valid page group name to the move item API.
Level: 1

Type: ERROR

Impact: Other

WWS-30683: Enter a number greater than zero.

Cause: One or more numeric values greater than zero were required but not entered in page group properties.

Action: Provide all the required number values.
Level: 1

Type: ERROR

Impact: Other

WWS-30686: An item type with the specified name already exists.

Cause: The item type name entered is not unique.

Action: Enter a unique item type name, one that is not used in the current page group nor in the Shared Objects page group.
Level: 1

Type: ERROR

Impact: Other

WWS-30687: A page type with the specified name already exists.

Cause: The page type name entered is not unique.

Action: Enter a unique page type name, one that is not used in the current page group nor in the Shared Objects page group.
Level: 1

Type: ERROR

Impact: Other

WWS-30693: This user does not exist.

Cause: An attempt was made to provide access to a user that does not exist.

Action: Provide a valid user name.
Level: 1

Type: ERROR

Impact: Other

WWS-30695: Page name contains spaces or special characters.

Cause: The specified page name contained spaces or special characters.

Action: Remove the spaces and special characters from the page name.
Level: 1

Type: ERROR

Impact: Other

WWS-30698: The specified user name is invalid.

Cause: An invalid user name or group name was entered.

Action: Enter a valid user name or group name. If you are not sure of the name, click the Browse Users or Browse Groups icon and select from the list provided.
Level: 1

Type: ERROR

Impact: Other

WWS-30699: Path Alias Name is not defined for the Database Access Descriptor.

Cause: The CGI environment variables were not initialized.

Action: Check the middle tier log files.
Level: 1

Type: ERROR

Impact: Other

WWS-30701: You cannot copy the page because the item template used by the page or its sub-pages is not from the Shared Objects page group.

Cause: The item template used by the page or its sub-pages is not from the Shared Objects page group.

Action: Copy the item template to the Shared Objects page group and change the page to use it.
Level: 1

Type: ERROR

Impact: Other

WWS-30706: You must specify a database schema.

Cause: A schema name was not specified.

Action: Specify a valid schema name.
Level: 1

Type: ERROR

Impact: Other

WWS-30707: Invalid schema specified. Database schema does not exist.

Cause: The database schema specified does not exist.

Action: Specify a valid database schema.
Level: 1

Type: ERROR

Impact: Other

WWS-30710: You must specify an expiration date.

Cause: The item is set to expire on a future date, but an expiration date was not specified.

Action: Specify the expiration date.
Level: 1

Type: ERROR

Impact: Other

WWS-30711: You must specify the number of days for the expiration period.

Cause: The item is set to expire in a certain number of days, but the number of days was not specified.

Action: Specify the number of days from the publish date when the item should expire.
Level: 1

Type: ERROR

Impact: Other

WWS-30712: Publish date must be in the proper date format. A 4-digit year must be indicated.

Cause: The publish date was entered in an invalid format.

Action: Enter the publish date in the format specified. Ensure that the year is indicated in four digits.
Level: 1

Type: ERROR

Impact: Other

WWS-30713: Publish date cannot be earlier than current date.

Cause: An attempt was made to publish this item before the current date, or an attempt was made to create a sub-item with a publish date that precedes the publish date of the parent item.

Action: Change the publish date of the item to a future date, or set the publish date of the sub-item to the same or a later date than the publish date of the parent item.
Level: 1

Type: ERROR

Impact: Other

WWS-30714: Expire date must be in the proper date format. A 4-digit year must be indicated.

Cause: The expiration date was entered in an invalid format.

Action: Enter the expiration date in the format specified. Ensure that the year is indicated in four digits.
Level: 1

Type: ERROR

Impact: Other

WWS-30715: Expire date must be later than current date.

Cause: An expiration date was entered for the item that was not later than the current date.

Action: The item can be expired only in the future. Specify an expiration date that is later than the current date.
Level: 1

Type: ERROR

Impact: Other

WWS-30716: An expire date that is the same as or earlier than the publish date signifies an Expired item, which cannot be edited. In order to edit this item, you must modify the expiration period.

Cause: The item has expired and cannot be edited.

Action: Un-expire the item, then try again.
Level: 1

Type: ERROR

Impact: Other

WWS-30717: Number format specified for the expiration period is invalid.

Cause: An invalid number was entered for the expiration period.

Action: Specify a valid number.
Level: 1

Type: ERROR

Impact: Other

WWS-30718: This item is currently being unzipped. To unzip again, wait until the status is set to Complete.

Cause: The Unzip link was clicked while the file was in the process of being unzipped.

Action: To unzip the Zip file again, wait until the current unzip process is complete.
Level: 1

Type: ERROR

Impact: Other

WWS-30719: Publish date cannot be earlier than creation date.

Cause: An attempt was made to enter a publish date that precedes the item's creation date.

Action: Enter a publish date that is either the same or later than the current date.
Level: 1

Type: ERROR

Impact: Other

WWS-30720: Unable to create items.

Cause: Oracle Portal was unable to refresh a portlet provider or the Portlet Repository.

Action: Check the refresh log to determine the provider that throws error, then verify that the provider registration for that provider is correct. Ensure that the provider is up and running during refresh.
Level: 1

Type: ERROR

Impact: Other

WWS-30721: You cannot copy the page because the default WebDAV item type of the page or its sub-pages is not from the Shared Objects page group.

Cause: The default WebDAV item type of the page or its sub-pages is not from the Shared Objects page group.

Action: Copy the item type to the Shared Objects page group.
Level: 1

Type: ERROR

Impact: Other

WWS-30722: The value entered for the page group quota is less than the page group's current usage.

Cause: The new value for the page group quota was not greater than or equal to the number of megabytes already consumed by the contents of the page group.

Action: Enter a value greater than or equal to the current usage.
Level: 1

Type: ERROR

Impact: Other

WWS-30723: The value entered for the page group quota is invalid.

Cause: The value entered for the page group quota is invalid.

Action: Enter a valid value or select No Limit to impose no quota restriction on the page group's use of space. Valid values include any positive number, including fractional values, such as 50.5.
Level: 1

Type: ERROR

Impact: Other

WWS-30724: Quota for this page group is exceeded.

Cause: The document or image could not be uploaded because the page group quota has been exceeded.

Action: Contact the portal administrator.
Level: 1

Type: ERROR

Impact: Other

WWS-30725: Expire date must be later than the publish date.

Cause: An attempt was made to enter an item expiration date that precedes the item publish date.

Action: Enter an expiration date that is later than the publish date.
Level: 1

Type: ERROR

Impact: Other

WWS-30728: Invalid number format entered for number type attribute or invalid values specified for number type list of values.

Cause: An invalid value or no value was specified for a number type attribute that is associated with this item type. The invalid value may be an invalid user-entered number or may be a selection from a list of values that contains invalid values.

Action: Edit the item type and provide valid values to all number type attributes. This may involve revising a list of values that is attached to a number type attribute.
Level: 1

Type: ERROR

Impact: Other

WWS-30730: Unable to get the list of providers.

Cause: The registration information for some provider was invalid, or an internal error occurred in the provider subsystem.

Action: Verify that registration information for all providers is valid.
Level: 1

Type: ERROR

Impact: Other

WWS-30731: Invalid date format specified.

Cause: An attempt was made to specify an invalid date format.

Action: Specify a valid date format.
Level: 1

Type: ERROR

Impact: Other

WWS-30738: This e-mail address is invalid.

Cause: An attempt was made to enter an e-mail address in an invalid format.

Action: Enter the e-mail address in a valid format, for example, name@oracle.com.
Level: 1

Type: ERROR

Impact: Other

WWS-30741: This item has been checked out so you cannot edit it.

Cause: Another user has checked the item out. The Edit icon was displayed because the page has not been refreshed since the other user checked the item out.

Action: Refresh the page to show the current status of its content. As soon as the other user checks the item in, you will be able to edit it.
Level: 1

Type: ERROR

Impact: Other

WWS-30742: Advanced Search link cannot be null.

Cause: The choice to specify an Advanced Search link was made, but the advanced search link value was not specified. The Advanced Search link is specified either by selecting a page or specifying a URL.

Action: Specify an Advanced Search link value.
Level: 1

Type: ERROR

Impact: Other

WWS-30743: Advanced Search page cannot be null.

Cause: The choice was made to specify an Advanced Search page, but the Advanced Search value was not specified. The Advanced Search page is specified either by selecting a page or specifying a URL.

Action: Specify an Advanced Search page value.
Level: 1

Type: ERROR

Impact: Other

WWS-30748: Pending items cannot be unzipped. The item must first be approved.

Cause: An attempt was made to unzip an item that is pending approval. Items pending approval cannot be unzipped.

Action: Unzip after the item is approved.
Level: 1

Type: ERROR

Impact: Other

WWS-30749: Search Results Page Names cannot be null.

Cause: One or both search results pages were not specified.

Action: Choose search results pages for basic and advanced searches.
Level: 1

Type: ERROR

Impact: Other

WWS-31365: Valid date format: %1

Cause: Dates were not entered in the correct format.

Action: Enter the date using the format specified.
Level: 1

Type: ERROR

Impact: Other

WWS-32018: The format of this URL has changed. Change the source of this URL to the New URL displayed below. The Old URL is not supported in future releases. If your browser does not automatically redirect you in 30 seconds, click the New URL below to go to the new page.

Cause: Portal URLs have changed, the old URL format is no longer valid.

Action: Wait to be redirected to the new URL, or click the link displayed.
Level: 1

Type: ERROR

Impact: Other

WWS-32021: An error was encountered while deleting the page group. The page group has been deleted but you should check the logs for more information.

Cause: A page group that had some data inconsistency was deleted.

Action: No further action required. The page group has been deleted. You can look at the logs for additional details on the data inconsistency.
Level: 1

Type: ERROR

Impact: Other

WWS-32022: The category has been created but it was not possible to place the search portlets on to the category page. The category page will not show the items or pages in the category.

Cause: This is usually caused when the category page template has been modified and the region in which the portlets are to be placed has been removed.

Action: If the category template is deleted, it will be re-created with the correct regions the next time a category is created. However, existing categories will not be based on the new template. See the Oracle Portal Configuration Guide, for information on how to remove and re-create all of the category pages based on a re-created template.
Level: 1

Type: ERROR

Impact: Other

WWS-32023: The perspective has been created, but it was not possible to place the search portlets onto the perspective page. The perspective page will not show the items or pages in the perspective.

Cause: This is usually caused when the perspective page template has been modified and the region in which the portlets are to be placed has been removed.

Action: If the perspective template is deleted, it will be re-created with the correct regions the next time a perspective is created. However, existing perspectives will not be based on the new template. See the Oracle Portal Configuration Guide, for information on how to remove and re-create all of the perspective pages based on a re-created template.
Level: 1

Type: ERROR

Impact: Other

WWS-32024: The file could be not filtered.

Cause: There may be a problem with an unsupported file format. To search file content and Themes and Gist, and view as HTML, the file must be filtered and converted to plain text. This is not always possible because some file formats are not supported. This error might also be caused by a problem with the setup and configuration of Oracle Text.

Action: Ensure that the document is in a format supported by Oracle Text. See the Oracle Portal Configuration Guide, available on Portal Center, for information on how to work with Oracle Text.
Level: 1

Type: ERROR

Impact: Other

WWS-32025: The search criteria specified results in too many potential search terms.

Cause: The combination of operator and search term were used to create a list of potential search terms that is too large. This can occur when using the "partially match (%term%)" operator with a non-specific search term.

Action: Enter a more specific search term or use a different operator.
Level: 1

Type: ERROR

Impact: Other

WWS-32026: The Oracle Text installation is not complete: Knowledge base file or files are missing.

Cause: The Knowledge Base supplied with Oracle Text was not installed.

Action: Complete the installation of Oracle Text.
Level: 1

Type: ERROR

Impact: Other

WWS-32028: The Oracle Text search query is too complex to process.

Cause: The Oracle Text search query provided is valid, but too complex for the installed version of Oracle Text to process.

Action: Simplify the search query expression and try again.
Level: 1

Type: ERROR

Impact: Other

WWS-32029: Oracle Text error %1

Cause: Oracle Text was unable to process the search query due to the specified error, starting with DRG-.

Action: For information on DRG- errors, refer to the Oracle Text documentation.
Level: 1

Type: ERROR

Impact: Other

WWS-32101: No data found

Cause: No data was found for the requested object.

Action: Try another request for a valid object.
Level: 1

Type: ERROR

Impact: Other

WWS-32103: You do not have permission to perform this operation.

Cause: The user does not have permission to perform this operation.

Action: Make sure that you are logged on as a user who has permission to perform the operation.
Level: 1

Type: ERROR

Impact: Other

WWS-32110: Page name is missing.

Cause: A page name was required but not entered.

Action: Enter a valid page name.
Level: 1

Type: ERROR

Impact: Other

WWS-32111: Display name is missing.

Cause: A display name was required but not entered.

Action: Enter a valid display name.
Level: 1

Type: ERROR

Impact: Other

WWS-32118: Invalid required value for an attribute.

Cause: One or more attributes required a value that was not provided.

Action: Provide values for all required attributes. Attributes that require a value are marked with an asterisk, *.
Level: 1

Type: ERROR

Impact: Other

WWS-32139: The page group ID does not exist.

Cause: An invalid page group ID was passed to a function getting the default language of a page group.

Action: Pass a valid page group ID.
Level: 1

Type: ERROR

Impact: Other

WWS-32141: The page does not exist.

Cause: An invalid page was specified to be rendered in the page portlet.

Action: Pass a valid page by changing the parameter value passed to the page portlet.
Level: 1

Type: ERROR

Impact: Other

WWS-32143: Invalid display mode

Cause: This portlet does not support the specified display mode.

Action: Choose either the Show or Edit display mode.
Level: 1

Type: ERROR

Impact: Other

WWS-32146: You cannot move the root page.

Cause: Moving the root page of a page group is not permitted.

Action: Consider moving each of the root page's sub-pages or creating a new page group.
Level: 1

Type: ERROR

Impact: Other

WWS-32147: You cannot move an object into itself.

Cause: Moving a page into one of its own sub-pages is not permitted.

Action: Choose a different destination for the page.
Level: 1

Type: ERROR

Impact: Other

WWS-32150: The item name cannot contain an invalid character.

Cause: A name containing one or more invalid characters was entered for the item.

Action: Enter a valid name for the item. Item names can contain the characters A to Z, a to z, 0 to 9, and _. Item names cannot contain the characters \/:*?"<>|,&#%.
Level: 1

Type: ERROR

Impact: Other

WWS-32153: PL/SQL code cannot exceed 2000 bytes.

Cause: Maximum length of PL/SQL code is 2000 bytes. The input length was longer than 2000 bytes.

Action: Reduce the code within 2000 bytes.
Level: 1

Type: ERROR

Impact: Other

WWS-33668: You cannot copy the page because the item attribute parameter of the item template used by the page or its sub-pages is not from the Shared Objects page group.

Cause: The item attribute parameter of the item template used by the page or its sub-pages is not from the Shared Objects page group.

Action: Copy the attribute to the Shared Objects page group.
Level: 1

Type: ERROR

Impact: Other

WWS-33797: You cannot move the item because the type of an item is not from the Shared Objects page group.

Cause: The type of the item is not from the Shared Objects page group.

Action: Move the item type to the Shared Objects page group.
Level: 1

Type: ERROR

Impact: Other

WWS-33951: You cannot copy the page because the type of an item on the page or its sub-pages is not from the Shared Objects page group.

Cause: The type of an item on the page or its sub-pages is not from the Shared Objects page group.

Action: Move the item type to the Shared Objects page group.
Level: 1

Type: ERROR

Impact: Other

105 WWU-52262 to WWU-83028

WWU-52262: Exception in %1 : %2

Cause: An unknown exception occurred during the export-import operation.

Action: Do nothing. The selected object will be exported. If the export fails, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-52263: The object %1 was not added to the transport set because it already exists as (or is the child of) an explicit object.

Cause: The object is already marked for export.

Action: Do nothing. The selected object will be exported.
Level: 1

Type: ERROR

Impact: Other

WWU-52293: An unknown exception occurred while validating the system tables. Aborting the export.

Cause: An abnormal exception occurred while performing the schema validation and cleanup.

Action: Check the schema-validation document, correct it, and export again.
Level: 1

Type: ERROR

Impact: Other

WWU-52294: An unknown exception occurred while validating the system tables. Exiting the validation process. All changes performed by the validation process will be reverted.

Cause: An abnormal exception occurred while performing the schema validation and cleanup.

Action: Check the schema-validation document and correct it.
Level: 1

Type: ERROR

Impact: Other

WWU-52295: An unknown exception occurred during the resolution of page group objects. The entire page group import is being rolled back.

Cause: An unknown exception occurred during the resolution of page group objects.

Action: Follow these steps: <br /> 1. If the log displays the cause of the error, correct the error and run the import again. <br /> 2. Run the schema-validation utility to correct the error and run the import again. <br /> 3. If you are still unable import successfully, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-52298: The resource is held up by other process. Try deleting again later.

Cause: The object to be deleted is in use by some other Portal session.

Action: Try to delete the resource again later.
Level: 1

Type: ERROR

Impact: Other

WWU-52320: The source attribute %1 has been promoted to the Shared Objects page group. The same attribute on the target belongs to a local page group.

Cause: The same attribute on the source and the target belongs to different page groups. The source attribute was promoted to the Shared Objects page group, while the target attribute belongs to a local page group.

Action: Promote the local attribute on the target to the Shared Objects page group, and re-import it.
Level: 1

Type: ERROR

Impact: Other

WWU-52321: The source attribute %1 belongs to a local page group. The same attribute on the target was promoted to the Shared Objects page group.

Cause: The same attribute on the source and the target belongs to different page groups. The source attribute belongs to a local page group, while the target attribute has been promoted to the Shared Objects page group.

Action: Promote the local attribute on the source to the Shared Objects page group, and re-import it.
Level: 1

Type: ERROR

Impact: Other

WWU-52322: The type or unique identifier of the source attribute %1 does not match the target attribute %1.

Cause: A different attribute on the target uses the same name as the attribute on the source.

Action: Delete the attribute on the target, and re-import it.
Level: 1

Type: ERROR

Impact: Other

WWU-52323: The source attribute %1 exists on the target under a different name. The target attribute cannot be reused.

Cause: The attribute name has been changed on the source or the target.

Action: Import the attribute in overwrite mode, or make the names the same on both the source and the target.
Level: 1

Type: ERROR

Impact: Other

WWU-52324: The length of the source attribute %1 is less than the same target attribute. Overwriting the target attribute can result in data inconsistency on the target.

Cause: The length of a text attribute on the target is greater than the length of the same text attribute on the source.

Action: Modify the length of the text attribute on the source and re-import it, or import it in reuse mode.
Level: 1

Type: ERROR

Impact: Other

WWU-52325: The length of the target attribute %1 is less than the same source attribute. Reuse of the target attribute can result in data inconsistency on the source.

Cause: The length of a text attribute on the target is less than the length of the same text attribute on the source.

Action: Modify the length of the text attribute on the target and re-import it, or import it in overwrite mode.
Level: 1

Type: ERROR

Impact: Other

WWU-52326: The source style %1 was promoted to the Shared Objects page group. The same style on the target belongs to a local page group.

Cause: The same style on the source and the target belongs to different page groups. The source style was promoted to the Shared Objects page group, while the target style belongs to a local page group.

Action: Promote the local style on the target to the Shared Objects page group and re-import it.
Level: 1

Type: ERROR

Impact: Other

WWU-52327: The source style %1 belongs to a local page group. The same style on the target was promoted to the Shared Objects page group.

Cause: The source style belongs to a local page group, while the target style has been promoted to the Shared Objects page group.

Action: Promote the local style on the source to the Shared Objects page group and re-import it.
Level: 1

Type: ERROR

Impact: Other

WWU-52328: The unique identifier of the source style %1 does not match the unique identifier of the target style %1.

Cause: A different style on the target uses the same name as the source style.

Action: Delete the style on the target and re-import the source style.
Level: 1

Type: ERROR

Impact: Other

WWU-52329: The source style %1 exists on the target with a different name. The target style cannot be reused.

Cause: The style name has been changed on the source or on the target.

Action: Either import the style in overwrite mode, or make the names the same on the source and the target.
Level: 1

Type: ERROR

Impact: Other

WWU-52330: The source item type %1 exists on the target with a different name. The target item type cannot be reused.

Cause: The item type's name has been changed on the source or on the target.

Action: Either import the item type in overwrite mode, or make the names the same on the source and the target.
Level: 1

Type: ERROR

Impact: Other

WWU-52331: The type or unique identifier of the source item type %1 does not match the target item type %1.

Cause: A different item type on the target uses the same name as the item type on the source.

Action: Delete the item type on the target and re-import it.
Level: 1

Type: ERROR

Impact: Other

WWU-52332: The source item type %1 was promoted to the Shared Objects page group. The same item type on the target belongs to a local page group.

Cause: The source item type has been promoted to the Shared Objects page group, while the target item type belongs to a local page group.

Action: Promote the local item type on the target to the Shared Objects page group and re-import it.
Level: 1

Type: ERROR

Impact: Other

WWU-52333: The source item type %1 belongs to a local page group. The same item type on the target has been promoted to the Shared Objects page group.

Cause: The source item type belongs to a local page group, while the target item type has been promoted to the Shared Objects page group.

Action: Promote the local item type on the source to the Shared Objects page group and re-import it.
Level: 1

Type: ERROR

Impact: Other

WWU-52334: The source page type %1 exists on the target with a different name. The target page type cannot be reused.

Cause: The page type's name has been changed on the source or on the target.

Action: Either import the page type in overwrite mode, or make the names the same on both the source and the target.
Level: 1

Type: ERROR

Impact: Other

WWU-52335: The type or unique identifier of the source page type %1 does not match the target page type %1.

Cause: A different page type on the target uses the same name as on the source page type.

Action: Delete the page type on the target and re-import it.
Level: 1

Type: ERROR

Impact: Other

WWU-52336: The source page type %1 has been promoted to the Shared Objects page group. The same page type on the target belongs to a local page group.

Cause: The source page type has been promoted to the Shared Objects page group, while the target page type belongs to a local page group.

Action: Promote the local page type on the target to the Shared Objects page group and re-import it.
Level: 1

Type: ERROR

Impact: Other

WWU-52337: The source page type %1 belongs to a local page group. The same page type on the target has been promoted to the Shared Objects page group.

Cause: The source page type belongs to a local page group, while the target page type has been promoted to the Shared Objects page group.

Action: Promote the local page type on the source to the Shared Objects page group and re-import it.
Level: 1

Type: ERROR

Impact: Other

WWU-52338: The portlet instance with unique identifier(portlet_inst_guid): %1 will be deleted from the page in the transport set because it has a dependency that does not exist on the target.

Cause: The portlet's dependency, such as its page, Web Provider, Database Provider, or so on, does not exist on the target.

Action: Promote the portlet's dependency to the transport set in the source and re-import it. If the dependency is a Web Provider, register it on the target to make the portlet available in the Portlet Repository.
Level: 1

Type: ERROR

Impact: Other

WWU-52339: An unexpected error occurred while extracting an HTML template's data into its corresponding transport tables.

Cause: An unexpected error occurred while extracting metadata from an HTML template. Because metadata was not extracted, the import might result in errors.

Action: Contact Oracle Support Services and provide the logs obtained.
Level: 1

Type: ERROR

Impact: Other

WWU-52340: An unexpected error occurred while importing the HTML template with the unique identifier %1, in the page group with identifier %2.

Cause: An unexpected error occurred while importing an HTML template.

Action: Contact Oracle Support Services and provide the logs obtained.
Level: 1

Type: ERROR

Impact: Other

WWU-52341: The source htmltemplate %1 was promoted to the Shared Objects page group. The same htmltemplate on the target belongs to a local page group.

Cause: The same htmltemplate on the source and the target belongs to different page groups. The source htmltemplate was promoted to the Shared Objects page group, while the target htmltemplate belongs to a local page group.

Action: Promote the local htmltemplate on the target to the Shared Objects page group and re-import it.
Level: 1

Type: ERROR

Impact: Other

WWU-52342: The source htmltemplate %1 belongs to a local page group. The same htmltemplate on the target was promoted to the Shared Objects page group.

Cause: The source htmltemplate belongs to a local page group, while the target htmltemplate has been promoted to the Shared Objects page group.

Action: Promote the local htmltemplate on the source to the Shared Objects page group and re-import it.
Level: 1

Type: ERROR

Impact: Other

WWU-52343: The unique identifier of the source htmltemplate %1 does not match the unique identifier target htmltemplate %1.

Cause: A different htmltemplate on the target uses the same name as the source htmltemplate.

Action: Delete the htmltemplate on the target and re-import the source htmltemplate.
Level: 1

Type: ERROR

Impact: Other

WWU-52454: An unexpected error has occurred. Verify the log in debug mode, which provides detailed error messages.

Cause: An unexpected error occurred while importing the access-related information.

Action: Contact Oracle Support Services and provide the logs obtained.
Level: 1

Type: ERROR

Impact: Other

WWU-52463: You do not have permission to %0 ACLs on %1.

Cause: The user did not have sufficient privileges to manage the access control lists (ACLs) of the listed object.

Action: Ask the Oracle Portal administrator to grant the required privileges. Try the import operation again after the privileges have been granted.
Level: 1

Type: ERROR

Impact: Other

WWU-52464: Unable to resolve %0 external application on the target OracleAS Portal.

Cause: Either the listed external application does not exist in the target OracleAS Single Sign-On, or there are multiple external applications with this name.

Action: Check the external application in the target OracleAS Single Sign-On. Create the application if it does not exist. Otherwise, check for external applications with duplicate names. Note that names of external applications are case-insensitive. Delete any redundant external applications. Re-import after taking one of these corrective actions.
Level: 1

Type: ERROR

Impact: Other

WWU-52465: Name not updated for object type: %0, object name: %1

Cause: The object list has not been updated with the mapping name while importing.

Action: Contact Oracle Support Services and provide the logs obtained.
Level: 1

Type: ERROR

Impact: Other

WWU-52501: Initialization of component(ID : %1 Name : %2) failed.

Cause: An unexpected error occurred while calculating the dependencies of the object.

Action: Retry the import. If the retry fails, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-52566: Generation of component %1, failed with errors.

Cause: The component generation has failed with compilation errors due to missing dependencies or privileges.

Action: Resolve the missing dependencies/privileges from a DB session and retry the import of the failed component.
Level: 1

Type: ERROR

Impact: Other

WWU-52567: Import of %1 failed.

Cause: The import failed for the object in the transport set.

Action: Retry the import. If the retry fails, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-52571: Warning : Import of color %1 failed.

Cause: An unexpected error occurred while creating the color on the target.

Action: Retry the import. If the retry fails, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-52572: Warning : Import of font %1 failed.

Cause: An unexpected error occurred while creating the font on the target.

Action: Retry the import. If the retry fails, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-52573: Warning : Import of image %1 failed.

Cause: An unexpected error occurred while creating the image on the target.

Action: Retry the import. If the retry fails, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-52574: Warning : Import of template %1 failed.

Cause: An unexpected error occurred while creating the template on the target.

Action: Retry the import. If the retry fails, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-52594: The DB Provider schema %1 does not have EXECUTE privileges on the OracleAS Portal packages used by the DB Provider portlets.

Cause: The EXECUTE privilege on OracleAS Portal packages, used by the portlets, was not granted to the DB Provider schema.

Action: Grant the EXECUTE privilege on OracleAS Portal packages to the DB Provider schema using the script provsyns.sql.
Level: 1

Type: ERROR

Impact: Other

WWU-52595: The schema %1 does not exist in this database instance.

Cause: The schema used by a Portal DB Provider that is being imported in the current import was not found in the this database instance.

Action: Create the schema in this database instance and grant the CONNECT and RESOURCE roles to it.
Level: 1

Type: ERROR

Impact: Other

WWU-52596: The component %1 does not exist on target.

Cause: This component was exported as an external object. Make sure that this component exists on target before import.

Action: Export this component separately first or promote this component as explicit and repeat the export and import process.
Level: 1

Type: ERROR

Impact: Other

WWU-52872: Mapping not found for Page ID %1 and Page Group ID %2 .

Cause: There is a dependency on the specified page and page group, and neither one exists on the target.

Action: Promote the specified page/page group to the transport set in the source, and re-import it. If the import still fails, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-52883: Transport set name cannot be NULL.

Cause: No name has been specified for the transport set.

Action: Specify a name for the transport set.
Level: 1

Type: ERROR

Impact: Other

WWU-52884: Transport set %1 has already been exported and is now available for import.

Cause: The transport set has already been exported.

Action: If the export was successful, the transport set can now be used for import.
Level: 1

Type: ERROR

Impact: Other

WWU-52885: Transport set %1 has not yet been exported and is therefore unavailable for import.

Cause: The transport set has not been exported.

Action: Export the transport set.
Level: 1

Type: ERROR

Impact: Other

WWU-52886: Transport set %1 does not exist.

Cause: The transport set was not found on the server.

Action: Verify that the transport set name was entered correctly. You may need to re-create the transport set.
Level: 1

Type: ERROR

Impact: Other

WWU-52887: Transport set %1 is currently unavailable for either export or import. See the transport set for more details.

Cause: The transport set status is neither EXTRACT_COMPLETE nor AVAILABLE.

Action: Browse the list of transport sets to determine the status.
Level: 1

Type: ERROR

Impact: Other

WWU-52888: Multiple matches found for transport set %1. Choose the one you want from the LOV.

Cause: More than one transport set with the same name was found.

Action: Use the user/timestamp on the list of values to identify the transport set you want.
Level: 1

Type: ERROR

Impact: Other

WWU-52889: Transport set %1 is not available for adding more objects.

Cause: The transport set is not available because it has already been exported or imported.

Action: Browse the list of transport sets to determine the status.
Level: 1

Type: ERROR

Impact: Other

WWU-52926: Transport set %1 does not contain any objects.

Cause: The transport set is empty.

Action: To access the transport set, add at least one object to it.
Level: 1

Type: ERROR

Impact: Other

WWU-52927: Logged-in user %1 does not have MANAGE privilege on any transport set and therefore cannot perform this action.

Cause: You do not appear to have MANAGE privilege on any transport sets.

Action: Ask your portal administrator to assign you this privilege.
Level: 1

Type: ERROR

Impact: Other

WWU-52969: Transport set does not exist. Cannot pre-check search preferences.

Cause: Search preferences cannot be pre-checked because the specified transport set does not exist.

Action: Verify the transport set name, or re-create the transport set.
Level: 1

Type: ERROR

Impact: Other

WWU-52970: Could not obtain transport set information. Cannot pre-check search preferences.

Cause: Search preferences cannot be pre-checked because information about the given transport set could not be obtained.

Action: Verify the transport set name, or re-create the transport set.
Level: 1

Type: ERROR

Impact: Other

WWU-52971: Cannot obtain search preference with ID %1 from system table.

Cause: The preference for a search portlet marked for export does not exist in the system tables.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-52972: An error occurred when performing export pre-check of search portlet preferences.

Cause: An unexpected error occurred while pre-checking search preferences prior to export.

Action: Check that the customizations for the search portlets you are exporting are valid.
Level: 1

Type: ERROR

Impact: Other

WWU-52973: An error occurred when exporting system preferences for search portlets.

Cause: The exporting of search preferences has failed.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-52974: Transport set does not exist. Cannot export search preferences.

Cause: The specified transport set does not exist. Exporting of search preferences cannot continue.

Action: Verify the transport set name, or re-create the transport set.
Level: 1

Type: ERROR

Impact: Other

WWU-52975: Could not obtain transport set information. Cannot export search preferences.

Cause: Cannot export search preferences because could not obtain information about the given transport set.

Action: Verify the transport set name, or re-create the transport set.
Level: 1

Type: ERROR

Impact: Other

WWU-52976: Exception occurred while exporting search portlet preferences.

Cause: An unexpected error occurred while attempting to export search portlet preferences.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-52977: Generating dependencies from search portlet preferences has failed. The transport set will not be valid for importing.

Cause: The dependencies in the search portlet preferences to be exported could not be obtained.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-52978: An error occurred while generating search portlet dependencies.

Cause: The dependencies in the search portlet preferences to be exported could not be obtained.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-52979: Exception occurred during search pre-check.

Cause: An unexpected error occurred while pre-checking search preferences.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-52980: An error occurred while marking an object in the transport set.

Cause: An error occurred while marking a search portlet preference dependency included in the transport set.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-52981: Exception occurred while setting the page as failed pre-check.

Cause: An unexpected error occurred while attempting to mark a page as failed pre-check.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-52982: There was an error in checking dependencies. Dependencies contained in search preferences did not exist in dependency table.

Cause: Dependencies in the search preferences are not in the search dependency table.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-52983: Error occurred checking for missing dependencies.

Cause: An unexpected error occurred while checking if a search preference has missing dependencies.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-52984: Cannot obtain new IDs from target tables. Cannot proceed with search pre-check.

Cause: An error occurred while attempting to get the ID of an object in the target tables.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-52985: Pre-check cannot continue because inconsistent data was found in dependency table and search transport table.

Cause: The information in the search preferences does not match information in the search dependency table.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-52986: Exception occurred resolving search portlet preferences.

Cause: An unexpected error occurred while attempting to resolve search preference information.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-52987: Exception occurred resolving search portlet preference import actions.

Cause: An unexpected error occurred while attempting to determine the import action of search portlet preferences.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-52988: Exception occurred resolving search portlet preference reference paths.

Cause: An unexpected error occurred while attempting to resolve a search portlet's reference path.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-52989: An error occurred getting object information from the object path. Object type does not exist.

Cause: The object type of a search preference dependency is not valid.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-52990: Exception occurred while updating dependency table with new IDs from the object path.

Cause: An unexpected error occurred while attempting to update the dependency table with the new IDs.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-52991: Exception occurred while determining IDs from the target tables.

Cause: An unexpected error occurred when attempting to obtain the ID of a search preference dependency from the target tables.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-52992: Exception occurred while determining IDs from the transport tables.

Cause: An unexpected error occurred when attempting to obtain the ID of a search preference dependency from the transport tables.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-52993: Exception occurred while resolving dependency IDs.

Cause: An unexpected error occurred while attempting to determine the new IDs of search preference dependencies.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-52994: Exception occurred while importing search portlet preferences.

Cause: An unexpected error occurred when attempting to import search portlet preferences.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-52995: Exception occurred while inserting new search portlet preferences.

Cause: An unexpected error occurred when attempting to insert new search portlet preferences into the target tables.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-52996: Error populating search dependency table with page group objects.

Cause: An unexpected error occurred when obtaining the page group dependencies from the search portlets being exported.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-52997: An error occurred while populating search dependency table with image objects.

Cause: An unexpected error occurred when obtaining the image dependencies from the search portlets being exported.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-52998: An error occurred while populating search dependency table with style objects.

Cause: An unexpected error occurred when obtaining the style dependencies from the search portlets being exported.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-52999: An error occurred while populating search dependency table with attribute objects.

Cause: An unexpected error occurred when obtaining the attribute dependencies from the search portlets being exported.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74000: An error occurred while populating search dependency table with item type objects.

Cause: An unexpected error occurred when obtaining the item type dependencies from the search portlets being exported.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74001: Efforts to determine the page path have failed. Object not found.

Cause: An unexpected error occurred while obtaining the path of the page selected to display search results. The page cannot be found.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74002: Efforts to determine the page path have failed. Language not found.

Cause: An unexpected error occurred while obtaining the path of the page selected to display search results. The language cannot be found.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74003: Efforts to determine the page path have failed due to invalid domain.

Cause: An unexpected error occurred while obtaining the path of the page selected to display search results. The domain is invalid.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74004: Efforts to determine the page path have failed due to invalid object type.

Cause: An unexpected error occurred while obtaining the path of the page selected to display search results. The object type is invalid.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74005: An error occurred while populating search dependency table with page objects.

Cause: An unexpected error occurred while obtaining the page dependencies from the search portlets being exported.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74006: Efforts to determine the category path have failed because the category was not found.

Cause: An unexpected error occurred while obtaining the path of the category selected as search criteria. The category cannot be found.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74007: Efforts to determine the category path have failed because the language was not found.

Cause: An unexpected error occurred while obtaining the path of the category selected as search criteria. The language cannot be found.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74008: Efforts to determine the category path have failed due to invalid domain.

Cause: An unexpected error occurred while obtaining the path of the category selected as search criteria. The domain is invalid.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74009: Efforts to determine the category path have failed due to invalid object type.

Cause: An unexpected error occurred while obtaining the path of the category selected as search criteria. The object type is invalid.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74010: An error occurred while populating the search dependency table with category objects.

Cause: An unexpected error occurred while obtaining the category dependencies from the search portlets being exported.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74011: Efforts to determine the perspective path have failed because the object was not found.

Cause: An unexpected error occurred while obtaining the path of the perspective selected as search criteria. The object cannot be found.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74012: Efforts to determine the perspective path have failed because the language was not found.

Cause: An unexpected error occurred while obtaining the path of the perspective selected as search criteria. The language cannot be found.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74013: Efforts to determine the perspective path have failed due to invalid domain.

Cause: An unexpected error occurred while obtaining the path of the perspective selected as search criteria. The domain is invalid.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74014: Efforts to determine the perspective path have failed due to invalid object type.

Cause: An unexpected error occurred while obtaining the path of the perspective selected as search criteria. The object type is invalid.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74015: An error occurred while populating the search dependency table with perspective objects.

Cause: An unexpected error occurred while obtaining the perspective dependencies from the search portlets being exported.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74017: An error occurred when attempting to clean up search preferences.

Cause: An unexpected error occurred while removing dangling references from the preferences of the search portlets being exported.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74019: Copying data from source tables to transport tables failed.

Cause: An unexpected error occurred while copying preferences of the search portlets being exported from the source table to the transport table.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74021: The page on which portlet resides does not exist.

Cause: Obtaining the page on which the search portlet resides failed because the page does not exist in the transport set.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74022: Too many pages were returned when attempting to determine the page on which the portlet resides.

Cause: Obtaining the page on which the search portlet resides failed because too many pages were returned from the query.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74023: An error occurred getting the ID of the page object that contains the search portlet.

Cause: An unexpected error occurred when attempting to get the object ID of the page on which the search portlet resides.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74024: Checking page group dependencies failed.

Cause: An unexpected error occurred while checking if the page groups selected in search portlet customizations will exist in the target after import.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74025: Checking image dependencies failed.

Cause: An unexpected error occurred while checking if the images selected in search portlet customizations will exist in the target after import.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74026: Checking style dependencies failed.

Cause: An unexpected error occurred while checking if the styles selected in search portlet customizations will exist in the target after import.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74027: Checking page dependencies failed.

Cause: An unexpected error occurred while checking if the pages selected in search portlet customizations will exist in the target after import.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74028: Checking submission attributes dependencies failed.

Cause: An unexpected error occurred while checking if the submission attributes selected in search portlet customizations will exist in the target after import.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74029: Checking item type attribute default value failed.

Cause: An unexpected error occurred while checking to see if the item types selected in the search portlet customizations will exist in the target after import.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74030: Checking category attribute default value failed.

Cause: An unexpected error occurred while checking to see if the categories selected in the search portlet customizations will exist in the target after import.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74031: Checking perspective attribute default value failed.

Cause: An unexpected error occurred while checking to see if the perspectives selected in the search portlet customizations will exist in the target after import.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74032: Checking results attributes dependencies failed.

Cause: An unexpected error occurred while checking to see if the results attributes selected in the search portlet customizations will exist in the target after import.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74034: Resolving results page dependencies failed.

Cause: An unexpected error occurred while replacing source IDs with target IDs for the results page option in the search portlet customizations.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74035: Resolving image dependencies failed.

Cause: An unexpected error occurred while replacing source IDs with target IDs for the image option in the search portlet customizations.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74036: Resolving style dependencies failed.

Cause: An unexpected error occurred while replacing source IDs with target IDs for the style option in the search portlet customizations.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74037: Resolving page groups dependencies failed.

Cause: An unexpected error occurred while replacing source IDs with target IDs for the page group option in the search portlet customizations.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74038: Exception occurred while resolving default values identified by a pair of IDs.

Cause: An unexpected error occurred while replacing source IDs with target IDs for attributes in the search portlet customizations, where the default values are objects in the portal.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74039: Exception occurred while resolving default values identified by a set of ID pairs.

Cause: An unexpected error occurred while replacing source IDs with target IDs for attributes in the search portlet customizations, where the default values are objects in the portal.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74040: Resolving submission attributes dependencies failed.

Cause: An unexpected error occurred while replacing source IDs with target IDs for the submission attributes option in the search portlet customizations.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74041: Resolving display attributes dependencies failed.

Cause: An unexpected error occurred while replacing source IDs with target IDs for the display attributes option in the search portlet customizations.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74043: Cannot resolve search preferences because the transport set does not exist.

Cause: The search preferences for the portlets being imported cannot be resolved because the transport set does not exist.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74044: Could not resolve search preferences because the transport set information could not be obtained.

Cause: The search preferences for the portlets being imported cannot be resolved because the transport set information cannot be obtained.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74045: Exception occurred while updating existing search portlet preferences.

Cause: An unexpected error occurred while the preferences for the search portlets being imported were being updated.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74047: Could not import search preferences because the transport set does not exist.

Cause: The search preferences for the portlets being imported cannot be imported because the transport set does not exist.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74048: Could not import search preferences because transport set information could not be obtained.

Cause: The search preferences for the portlets being imported cannot be imported because the transport set information cannot be obtained.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74062: Error resolving search portlet translations.

Cause: An unexpected error occurred while resolving translations of search portlet preferences.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74063: Error resolving search portlet string preferences.

Cause: An unexpected error occurred while the translations of search string preferences were being resolved, with the languages that exist in the target portal.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74066: Error populating the search mapping table with page group objects.

Cause: An unexpected error occurred while attempting to obtain page group dependencies for the search items to be exported.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74071: Error resolving pages to be searched.

Cause: An unexpected error occurred while replacing source IDs with target IDs for the pages that are defined within search portlet customizations; that is, pages defined using the 'Search-In' option.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74072: Check for missing pages failed.

Cause: An unexpected error occurred while checking if the page groups selected in search item customizations will exist in the target after import.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74100: Page %1 of the page group with unique identifier %2 applies the user's default style. The default style of the user on the target will be used.

Cause: The page group is using a user default style.

Action: The default style of the user on the target will be used. Or bring the source user's default style on the target and associate it with the user.
Level: 1

Type: ERROR

Impact: Other

WWU-74101: Unable to find data for the attribute with unique identifier %1 and page group identifier %2. An attempt to import this transport set could result in errors.

Cause: Data was not found for the specified attribute in the specified page group. The export proceeded without the attribute. An attempt to import the resulting transport set could result in errors. This is a data inconsistency issue in the base system, possibly in the itemtype or pagetype attribute association table.

Action: Contact Oracle Support Services, and provide the export logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74102: Multiple records were found while obtaining the metadata of the attribute with unique identifier %1 and page group identifier %2. An attempt to import this transport set could result in errors.

Cause: An unexpected error occurred while obtaining attribute metadata. The export will proceed without the attribute. An attempt to import the resulting transport set could result in errors. This error may indicate a data inconsistency issue in the base system, possibly in the attribute metadata table.

Action: Contact Oracle Support Services and provide the export logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74103: Unable to add the attribute with unique identifier %1 and page group identifier %2. An attempt to import this transport set could result in errors.

Cause: An unexpected error occurred while adding the specified attribute. The export proceeded without the attribute. An attempt to import the resulting transport set could result in errors.

Action: Contact Oracle Support Services, and provide the export logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74104: Multiple records were found while getting the page type of the page %1 in the page group with unique identifier %2. An attempt to import this transport set could result in errors.

Cause: An unexpected error occurred while obtaining the page type. The export will proceed without the type. An attempt to import the resulting transport set could result in errors. This error may indicate a data inconsistency issue in the base system, possibly in the pagetype metadata table.

Action: Contact Oracle Support Services, and provide the export logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74105: No page type definition found for page %1 in the page group with unique identifier %2. An attempt to import this transport set could result in errors.

Cause: An unexpected error occurred while obtaining the page type definition. The export proceeded without the page type definition. An attempt to import the resulting transport set could result in errors. This is a data inconsistency issue in the base system. The page table contains an inconsistent pagetype entry.

Action: Contact Oracle Support Services, and provide the resulting logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74106: Cannot add the page type of page %1 in the page group with unique identifier %2. An attempt to import this transport set could result in errors.

Cause: An unexpected error occurred while adding the page type metadata. The export will proceed without the page type metadata. An attempt to import the resulting transport set could result in errors.

Action: Contact Oracle Support Services, and provide the export logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74107: No item type definition found for item %1 in page group with unique identifier %2. An attempt to import this transport set could result in errors.

Cause: An unexpected error occurred while obtaining the item type definition. The export proceeded without the item type. An attempt to import the resulting transport set could result in errors. This is a data inconsistency issue in the base system. An inconsistent itemtype entry is present in the item table.

Action: Contact Oracle Support Services, and provide the export logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74108: Multiple records were found while obtaining the item type of item %1 in the page group with unique identifier %2. An attempt to import this transport set could result in errors.

Cause: An unexpected error occurred while obtaining the specified item type. The export proceeded without the item type. An attempt to import the resulting transport set could result in errors. This may be a data inconsistency issue in the base system, possibly in the itemtype metadata table.

Action: Contact Oracle Support Services, and provide the export logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74109: Unable to add the item type of item %1 in the page group with unique identifier %2. An attempt to import this transport set could result in errors.

Cause: An unexpected error occurred while adding the item type. The export will proceed without the item type metadata. An attempt to import the resulting transport set could result in errors.

Action: Contact Oracle Support Services, and provide the export logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74110: Multiple records were found while obtaining the category of page %1 in the page group with unique identifier %2. An attempt to import this transport set could result in errors.

Cause: An unexpected error occurred while getting the specified category. The export proceeded without the category. An attempt to import the resulting transport set could result in errors. This error may indicate a data inconsistency issue in the base system, possibly in the category metadata table.

Action: Contact Oracle Support Services, and provide the export logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74111: Unable to add the category of page %1 in the page group with unique identifier %2. An attempt to import this transport set could result in errors.

Cause: An unexpected error occurred while adding the category. The export will proceed without the category metadata. An attempt to import the resulting transport set could result in errors.

Action: Contact Oracle Support Services, and provide the export logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74112: Cannot find the perspective with the unique identifier %1 and page group identifier %2. An attempt to import this transport set could result in errors.

Cause: An unexpected error occurred while getting the specified perspective. The export proceeded without the perspective. An attempt to import the resulting transport set could result in errors. This is a data inconsistency issue in the base system. An inconsistent perspective entry is present in the item or page perspective association tables.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74113: Multiple records were found while obtaining the perspective with the unique identifier %1 and page group identifier %2. An attempt to import this transport set could result in errors.

Cause: An unexpected error occurred while obtaining the specified perspective. The export proceeded without the perspective. An attempt to use the resulting transport set could result in errors. This error may indicate a data inconsistency issue in the base system, possibly in the perspective metadata table.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74114: Unable to add the perspective with the unique identifier %1 and page group identifier %2. An attempt to import this transport set could result in errors.

Cause: An unexpected error occurred while adding the perspective. The export will proceed without the perspective. An attempt to import the resulting transport set could result in errors.

Action: Contact Oracle Support Services, and provide the export logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74115: Multiple records were found while obtaining the style of the page %1 with page group identifier %2. An attempt to import this transport set could result in errors.

Cause: An unexpected error occurred while obtaining the style of the specified page. The export proceeded without the style. Import of the resulting transport set could result in errors. This error may indicate a data inconsistency issue in the base system, possibly in the style metadata table.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74116: Unable to add the style of the page %1 with page group identifier %2. An attempt to import this transport set could result in errors.

Cause: An unexpected error occurred while adding the style. The export will proceed without the style. An attempt to import the resulting transport set could result in errors.

Action: Contact Oracle Support Services, and provide the export logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74117: Cannot find record for the external application with the unique identifier %1. Portlets based on this application will get lost on import.

Cause: The specified external application was not found. The export will proceed without the dependencies. If the resulting transport set is imported, portlets that are dependent on this application will not be found. This error may indicate a data inconsistency issue in the base system. For example, there may be an inconsistent external application entry in the provider table.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74118: Multiple records were found while obtaining the details of external application with the unique identifier %1. Portlets based on this application will get lost during import.

Cause: An unexpected error occurred while obtaining the details of the specified external application. The export proceeded without the dependencies. If the resulting transport set is imported, the portlets that are dependent on this application will not be found. This error may indicate a data inconsistency issue in the base system, possibly in the external application table.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74119: Unable to add the external application dependency with the unique identifier %1. Portlets based on this application will get lost on import.

Cause: An unexpected error occurred while adding the external application dependency. The export proceeded without the dependency. If the resulting transport set is imported, portlets that are dependent on this application will not be found.

Action: Contact Oracle Support Services, and provide the export logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74120: Cannot find the page group with unique identifier %1, in which the portlet was exposed as shared. An attempt to import this transport set could result in errors.

Cause: The page group where the portlet is exposed as shared could not be found. The export proceeded without the page group. If the resulting transport set is imported, the portlet could be lost. This may be a data inconsistency issue in the base system, possibly in the portlet instance table. For example, the shared portlet instance entry may have a wrong pgrp identifier.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74121: Unable to add the dependencies of generic page portlet with the unique identifier %1 and page group identifier %2. An attempt to import this transport set could result in errors.

Cause: An unexpected error occurred while adding the dependencies of the generic page portlet. The export proceeded without the dependencies. If the resulting transport set is imported, the generic page portlet could result in errors.

Action: Contact Oracle Support Services, and provide the export logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74122: Cannot find the definition of the DB Provider component that is exposed as the portlet with unique identifier %1. Portlets based on this component will get lost upon import.

Cause: Could not find the definition of the specified DB Provider exposed as a portlet. The export proceeded without the portlet definition. If the resulting transport set is imported, portlets based on this component will get lost upon import. This error may indicate a data inconsistency issue in the base system. For example, the wrong portlet ID information may be stored in the portlet instance table.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74123: Cannot find details for the provider with the unique identifier %1. An attempt to import this transport set could result in errors.

Cause: No data was found while obtaining the provider definition. The export will proceed without it. An attempt to import the resulting transport set could result in errors, possibly the loss of the portlets owned by this provider. This error may indicate a data inconsistency issue in the base system. For example, an inconsistent provider entry may be stored in the portlet instance table.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74124: Multiple records were encountered while obtaining details for the provider with unique identifier %1. An attempt to import this transport set could result in errors.

Cause: An unexpected error occurred while getting the provider definition. The export proceeded without it. An attempt to import the resulting transport set could result in errors, possibly the loss of this provider's portlets. This error may indicate a data inconsistency issue in the base system, possibly in the provider metadata table.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74125: No data was found while obtaining the provider associated with the page group with unique identifier %1. An attempt to import this transport set could result in errors.

Cause: An unexpected error occurred while obtaining the specified provider. The export proceeded without the provider definition. An attempt to import the resulting transport set could result in errors. For example, the navigation page portlets dependent on this provider could be lost. This error may indicate a data inconsistency issue in the base system, possibly in the page group table or the provider metadata table.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74126: No data was found while obtaining the page with unique identifier %1 and page group %2. This page is a page-link dependency of another page. The page link will get lost on import.

Cause: An unexpected error occurred while obtaining the specified page. This page is a page-link dependency of another page. The export will proceed without the page link. An attempt to import the resulting transport set will result in errors, including the loss of the page link. This error may indicate a data inconsistency issue in the base system. For example, inconsistent page link entries may be present in the page table.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74127: Unable to get the page with unique identifier %1 and page group %2. This page is page-link dependency of another page. The page link will get lost on import.

Cause: An unexpected error occurred while adding the page link dependency. The export proceeded without the page link dependency definition. An attempt to import the resulting transport set will result in errors, most likely because the page link will get lost.

Action: Contact Oracle Support Services, and provide the export logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74128: Cannot find the template metadata with unique identifier %1 and page group %2. Import of this transport set could result in errors for pages based on this template.

Cause: An unexpected error occurred while obtaining the specified template metadata. The export proceeded without the template. Importing the resulting transport set could result in errors for any pages that are based on the specified template. This error may indicate a data inconsistency issue in the base system. For example, the page table may contain an inconsistent template entry.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74129: Multiple records were found while obtaining the template metadata with unique identifier %1 and page group %2. Importing this transport set could result in errors for pages based on this template.

Cause: An unexpected error occurred while obtaining the specified template's metadata. The export proceeded without the template. Importing the resulting transport set could result in errors for pages based on this template. This error may indicate a data inconsistency issue in the base system, possibly in the template metadata table.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74132: Unable to get the UI template %1 of schema %2 associated with the given page.

Cause: An unexpected error occurred while adding the specified UI template. The export proceeded without the template. Importing the resulting transport set could result in broken connections between pages and their related UI templates.

Action: Contact Oracle Support Services, and provide the export logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74133: Unable to get the dependencies associated with the page %1. Importing this transport set could result in errors for this page.

Cause: An unexpected error occurred while adding the dependencies associated with the page. The export proceeded without the page dependencies. Importing the resulting transport could result in errors for this page.

Action: Contact Oracle Support Services, and provide the export logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74134: Unable to get the default settings of the page group with unique identifier %1. Some of the default settings could be lost on import.

Cause: An unexpected error occurred while adding the specified page group's default settings. The export proceeded without them. Importing the resulting transport set could result in loss of the page group's default settings.

Action: Contact Oracle Support Services, and provide the export logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74135: Unable to add the page group with unique identifier %1 as an external dependency. An attempt to import this transport set could result in errors.

Cause: An unexpected error occurred while adding the page group as an external dependency. The export proceeded without it. Importing the resulting transport set could result in errors attributable to the omitted page group.

Action: Contact Oracle Support Services, and provide the export logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74136: Unable to add the category with unique identifier %1 of the page group %2 as an external dependency. Import of this transport set could result in errors.

Cause: An unexpected error occurred while adding the category as an external dependency. The export proceeded without adding the category. Importing the resulting transport set could result in errors for any children of the omitted category.

Action: Contact Oracle Support Services, and provide the export logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74137: Unable to add the perspective with unique identifier %1 of the page group %2 as an external dependency. Import of this transport set could result in errors.

Cause: An unexpected error occurred while adding the perspective as an external dependency. The export proceeded without the perspective. Importing the resulting transport set could result in errors for any children of the omitted perspective.

Action: Contact Oracle Support Services, and provide the export logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74138: Unable to add the page with unique identifier %1 of the page group %2 as an external dependency. Import of this transport set could result in errors.

Cause: An unexpected error occurred while adding the page as an external dependency. The export proceeded without the page. Importing the resulting transport set could result in errors for any children of the omitted page.

Action: Contact Oracle Support Services, and provide the export logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74139: Unable to add the color %1. The components using this color that are imported from this transport set will use the default color that is specified for like components on the target.

Cause: An unexpected error occurred while adding the specified color. The export proceeded without the color metadata. All the components in the resulting transport set that used this color will no longer have access to it. On the target, these components will use the default color that is specified for like components. This error may indicate a data inconsistency issue in the base system.

Action: As a workaround, after importing this transport set, bring in the associated color and re-associate it with the relevant components. Before proceeding with the import of this transport set, consult the Export/Import section of the Portal Configuration Guide for additional information on object behavior.
Level: 1

Type: ERROR

Impact: Other

WWU-74140: Unable to add the font %1. The components that use this font that are imported from this transport set will use the default font that is specified for like components on the target.

Cause: An unexpected error occurred while adding font. The export proceeded without the font metadata. If the resulting transport set contains components that used this font, on import they will use the default font specified on the target. This error may indicate a data inconsistency issue in the base system.

Action: As a workaround, after importing this transport set, bring in the associated font and re-associate it with the relevant components. Before proceeding with the import of this transport set, consult the Export/Import section of the Portal Configuration Guide for additional information on object behavior.
Level: 1

Type: ERROR

Impact: Other

WWU-74141: Unable to add the image %1. The components in this transport set that use this image will use the target's default image instead. The default image is often an X, indicating a broken image.

Cause: An unexpected error occurred while adding the specified image. The export proceeded without the image. Components that used this image that are imported from the resulting transport set will use the target's default image. This error may indicate a data inconsistency issue in the base system.

Action: As a workaround, after importing this transport set, bring in the associated image and re-associate it with the relevant components. Before proceeding with the import of this transport set, consult the Export/Import section of the Portal Configuration Guide for additional information on object behavior.
Level: 1

Type: ERROR

Impact: Other

WWU-74142: Unable to add the JavaScript %1. The components in the transport set that use this script will use the default JavaScript.

Cause: An unexpected error occurred while adding the JavaScript. The export proceeded without it. If the resulting transport set is imported, the components that used this script on the source will use the default JavaScript on the target. This error may indicate a data inconsistency issue in the base system.

Action: As a workaround, after importing this transport set, bring in the associated JavaScript and re-associate it with the relevant components. Before proceeding with the import of this transport set, consult the Export/Import section of the Portal Configuration Guide for additional information on object behavior.
Level: 1

Type: ERROR

Impact: Other

WWU-74143: Unable to add the colors, images, and fonts that are referenced by the template with unique identifier %1. On the target, the template will use the default values of these referenced objects.

Cause: An unexpected error occurred while adding the colors, images, and fonts that are referenced by the template. The export proceeded without the referenced objects. Importing the resulting transport set will result in the use of the target's default values for the referenced objects. This error may indicate a data inconsistency issue in the base system.

Action: As a workaround, after importing this transport set, bring in the associated objects and re-associate them with the template. Before importing this transport set, consult the Export/Import section of the Portal Configuration Guide for additional information on object behavior.
Level: 1

Type: ERROR

Impact: Other

WWU-74144: Unable to add the template %1. This transport set will not contain this template.

Cause: An unexpected error occurred while adding the specified template. The export proceeded without the template. Importing the resulting transport set could result in errors should any objects be dependent upon this template. This error may indicate a data inconsistency issue in the base system.

Action: As a workaround, after importing this transport set, bring in the associated template and re-associate it with the relevant objects. Before importing this transport set, consult the Export/Import section of the Portal Configuration Guide for additional information on object behavior.
Level: 1

Type: ERROR

Impact: Other

WWU-74145: Unable to add the LOV %1. An attempt to import this transport set could result in errors.

Cause: An unexpected error occurred while adding the specified LOV. The export proceeded without the LOV. This error may indicate a data inconsistency issue in the base system.

Action: As a workaround, after importing this transport set, bring in the associated LOV and re-associate it with the relevant objects. Before proceeding with the import of this transport set, consult the Export/Import section of the Portal Configuration Guide for additional information on object behavior.
Level: 1

Type: ERROR

Impact: Other

WWU-74146: Unable to add the link %1. An attempt to import this transport set could result in errors.

Cause: An unexpected error occurred while adding the specified link. The export proceeded without the link. Importing the resulting transport set could result in errors related to objects that use this link. This error may indicate a data inconsistency issue in the base system.

Action: As a workaround, after importing this transport set, bring in the associated link and re-associate it with the relevant objects. Before importing the transport set, consult the Export/Import section of the Portal Configuration Guide for additional information on object behavior.
Level: 1

Type: ERROR

Impact: Other

WWU-74147: Unable to add all the colors. Importing this transport set could result in errors.

Cause: An unexpected error occurred while adding all the colors. The export proceeded without the colors. Importing the resulting transport set could result in the application of undesirable colors to any affected objects. This error may indicate a data inconsistency issue in the base system.

Action: As a workaround, after importing this transport set, bring in the associated color and re-associate it with the relevant objects. Before importing this transport set, consult the Export/Import section of the Portal Configuration Guide for additional information on object behavior.
Level: 1

Type: ERROR

Impact: Other

WWU-74148: Unable to add all the fonts. Importing this transport set could result in errors.

Cause: An unexpected error occurred while adding all the fonts. The export proceeded without the fonts. Importing the resulting transport set could result in the application of undesirable fonts to affected objects. This error may indicate a data inconsistency issue in the base system.

Action: As a workaround, after importing this transport set, bring in the associated fonts and re-associate them with the relevant objects. Before importing this transport set, consult the Export/Import section of the Portal Configuration Guide for additional information on object behavior.
Level: 1

Type: ERROR

Impact: Other

WWU-74150: Unable to add all the images. Import of this transport set could result in errors.

Cause: An unexpected error occurred while adding all the images. The export proceeded without the images. Import of the resulting transport set could result in problems for the objects that use these images. This error may indicate a data inconsistency issue in the base system.

Action: As a workaround, after importing this transport set, bring in the associated images and re-associate them with the relevant objects. Before proceeding with the import of this transport set, consult the Export/Import section of the Portal Configuration Guide for additional information on object behavior.
Level: 1

Type: ERROR

Impact: Other

WWU-74151: Unable to add all the JavaScripts. Import of this transport set could result in errors.

Cause: An unexpected error occurred while adding all the JavaScripts. The export proceeded without these JavaScripts. Importing the resulting transport set could result in problems for the objects that use these JavaScripts. This error may indicate a data inconsistency issue in the base system.

Action: As a workaround, after importing this transport set, bring in the associated JavaScripts and re-associate them with the relevant objects. Before proceeding with the import of this transport set, consult the Export/Import section of the Portal Configuration Guide for additional information on object behavior.
Level: 1

Type: ERROR

Impact: Other

WWU-74152: Unable to add all the templates. An attempt to import this transport set could result in errors.

Cause: An unexpected error occurred while adding all the templates. The export proceeded without these templates. This error may indicate a data inconsistency issue in the base system.

Action: As a workaround, after importing this transport set, bring in the associated templates and re-associate them with the relevant objects. Before proceeding with the import of this transport set, consult the Export/Import section of the Portal Configuration Guide for additional information on object behavior.
Level: 1

Type: ERROR

Impact: Other

WWU-74153: Unable to add the objects referenced by the data component %1. Import of this transport set could result in errors.

Cause: An unexpected error occurred while adding objects referenced by the specified data component. The export proceeded without the referenced objects. Import of the resulting transport set could result in errors. This error may indicate a data inconsistency issue in the base system.

Action: As a workaround, after importing this transport set, bring in the associated objects and re-associate them with the relevant data component. Before proceeding with the import of this transport set, consult the Export/Import section of the Portal Configuration Guide for additional information on object behavior.
Level: 1

Type: ERROR

Impact: Other

WWU-74154: Unable to add the objects referenced by the report %1. Import of this transport set could result in errors.

Cause: An unexpected error occurred while adding objects referenced by the specified report. The export proceeded without the referenced objects. Import of the resulting transport set could result in errors. This error may indicate a data inconsistency issue in the base system.

Action: As a workaround, after importing this transport set, bring in the associated objects and re-associate them with the specified report. Before proceeding with the import of this transport set, consult the Export/Import section of the Portal Configuration Guide for additional information on object behavior.
Level: 1

Type: ERROR

Impact: Other

WWU-74155: Unable to add the objects referenced by the menu link %1. Import of this transport set could result in errors.

Cause: An unexpected error occurred while adding objects referenced by the specified menu link. The export proceeded without the referenced objects. Import of the resulting transport set could result in errors. This error may indicate a data inconsistency issue in the base system.

Action: As a workaround, after importing this transport set, bring in the associated objects and re-associate them with the specified menu link. Before proceeding with the import of this transport set, consult the Export/Import section of the Portal Configuration Guide for additional information on object behavior.
Level: 1

Type: ERROR

Impact: Other

WWU-74156: Unable to add the objects referenced by the application %1.

Cause: An unexpected error occurred while adding objects referenced by the application. The export proceeded without the referenced objects. Import of the resulting transport set could result in errors. This error may indicate a data inconsistency issue in the base system.

Action: As a workaround, after importing this transport set, bring in the associated objects and re-associate them with the specified application. Before proceeding with the import of this transport set, consult the Export/Import section of the Portal Configuration Guide for additional information on object behavior.
Level: 1

Type: ERROR

Impact: Other

WWU-74157: Unable to add the application %1. Import of this transport set could result in errors.

Cause: An unexpected error occurred while adding the specified application. The export proceeded without the application. Import of the resulting transport set could result in errors. This error may indicate a data inconsistency issue in the base system.

Action: As a workaround, after importing this transport set, bring in the associated objects and re-associate them with the specified application. Before proceeding with the import of this transport set, consult the Export/Import section of the Portal Configuration Guide for additional information on object behavior.
Level: 1

Type: ERROR

Impact: Other

WWU-74158: Unable to add the component %1 of type %2 of the application %3. Import this transport set could result in errors.

Cause: An unexpected error occurred while adding the specified component. The export proceeded without the component. Import of the resulting transport set could result in errors. This error may indicate a data inconsistency issue in the base system.

Action: As a workaround, after importing this transport set, bring in the specified component. Before proceeding with the import of this transport set, consult the Export/Import section of the Portal Configuration Guide for additional information on object behavior.
Level: 1

Type: ERROR

Impact: Other

WWU-74159: Unable to add item link dependency of item having unique identifier (id) %1 in pagegroup with identifier %2.

Cause: An unexpected error occurred while extracting item link dependency.

Action: The export will proceed without the dependency. On import, the itemlink item will lose the association. Edit the item link and point to another item or bring the page containing the required item from the source for it to work. Contact Oracle Support Services and provide the logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74160: Unable to add item template dependency having unique identifier %1 with pagegroup identifier %2. The export will proceed without the item template. On import, the item/page configured with the item template will throw run time errors.

Cause: An unexpected error occurred while adding item template dependency.

Action: The export will proceed without the item template dependency.Contact Oracle Support Services and provide the logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74161: Unable to add HTML template dependencies of regions in page with unique identifier %1 in pagegroup with identifier %2. The export will proceed without HTML template dependencies. However the import could result in errors.

Cause: An unexpected error occurred while adding HTML template of region. This could be due to a corrupted HTML template entry in region table.

Action: The export will proceed without HTML template dependencies. Contact Oracle Support Services and provide the logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74162: An unexpected error occurred while adding HTML template dependencies of pagegroup with identifier %1. The export will proceed without them. Import could result in errors for pages/regions using them.

Cause: An unexpected error occurred while adding HTML template dependencies of given pagegroup.

Action: The export will proceed without HTML templates. Contact Oracle Support Services and provide the logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74163: Unable to add item placeholder dependency of item. The configured item has unique identifier %1 in pagegroup with identifier %2.

Cause: An unexpected error occurred while extracting item placeholder dependency.

Action: The export will proceed without the item placeholder dependency. On import, the item placeholder item will lose the association. You can edit the item and point it to another item or bring the page containing the required item from the source for it to work. Contact Oracle Support Services and provide the logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74164: An unexpected error occurred while updating object details. %1

Cause: An unexpected error occurred while updatng object details.

Action: Contact Oracle Support Services and provide the logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74165: An unexpected error occurred while getting object IDs. %1

Cause: An unexpected error occurred while getting object Ids.

Action: Contact Oracle Support Services and provide the logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74166: An unexpected error occurred while getting object list. %1

Cause: An unexpected error occurred while getting object list.

Action: Contact Oracle Support Services and provide the logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74167: An unexpected error occurred while altering manifest data for duplicate entries in reference objects. %1

Cause: An unexpected error occurred while altering manifest data.

Action: Contact Oracle Support Services and provide the logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74168: An unexpected error occurred while altering manifest data for duplicate entries in external objects. %1

Cause: An unexpected error occurred while altering manifest data for external objects.

Action: Contact Oracle Support Services and provide the logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74169: An unexpected error occurred while altering manifest data for duplicate entries. %1

Cause: An unexpected error occurred while altering manifest data.

Action: Contact Oracle Support Services and provide the logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74170: An unexpected error occurred while retrieving dependencies. %1

Cause: An unexpected error occurred while retrieving dependencies.

Action: Contact Oracle Support Services and provide the logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74171: An unexpected error occurred while retrieving dependencies. %1

Cause: An unexpected error occurred while retrieving dependencies.

Action: Contact Oracle Support Services and provide the logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74172: An unexpected error occurred while updating manifest data on to table. %1

Cause: An unexpected error occurred while updating manifest data on to table.

Action: Contact Oracle Support Services and provide the logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74173: An unexpected error occurred while updating manifest data for promoted objects on to table. %1

Cause: An unexpected error occurred while updating manifest data for promoted objects on to table.

Action: Contact Oracle Support Services and provide the logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74174: An invalid export ID %1 is passed for dependency calculation.

Cause: An invalid export id is passed for dependency calculation

Action: Make sure that a correct export id is passed. Contact Oracle Support Services and provide the logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74175: An unexpected error occurred while calculating manifest for a transport set. %1

Cause: An unexpected error occurred while calculating manifest for a transport set.

Action: Contact Oracle Support Services and provide the logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74176: No objects were found in table for export ID %1 while calculating manifest.

Cause: No objects were found in table while calculating manifest.

Action: Contact Oracle Support Services and provide the logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74180: An unexpected error occurred while altering the dependency list for each explicit object that was deleted. %1

Cause: An unexpected error occurred while altering the dependency list for each explicit object that was deleted.

Action: Contact Oracle Support Services and provide the logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74181: An unknown error while deleting object %2 from detail table for export ID %1. %3.

Cause: An unexpected error occurred while deleting object from detail table.

Action: Contact Oracle Support Services and provide the logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74182: An unknown error while deleting the given set of explicit objects. %1.

Cause: An unexpected error occurred while deleting the given set of explicit objects.

Action: Contact Oracle Support Services and provide the logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74183: An unknown error while deleting the newly added objects and calculate manifest. %1.

Cause: An unexpected error occurred while deleting the newly added objects and calculate manifest.

Action: Contact Oracle Support Services and provide the logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74184: An unknown error while getting all the explicit objects in the given transport set. %1.

Cause: An unexpected error occurred while getting all the explicit objects in the given transport set.

Action: Contact Oracle Support Services and provide the logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74185: An unknown error while getting all the reference objects in the given transport set. %1.

Cause: An unexpected error occurred while getting all the reference objects in the given transport set.

Action: Contact Oracle Support Services and provide the logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74186: An unknown error while getting all the external objects in the given transport set. %1.

Cause: An unexpected error occurred while getting all the external objects in the given transport set.

Action: Contact Oracle Support Services and provide the logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74187: An invalid import mode %1 is passed for dependency calculation while updating the record.

Cause: An invalid import mode is passed for dependency calculation.

Action: Make sure that a correct mode is passed. Contact Oracle Support Services and provide the logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74188: An invalid import category %1 is passed for dependency calculation while updating the record.

Cause: An invalid import category is passed for dependency calculation.

Action: Make sure that a correct category is passed. Contact Oracle Support Services and provide the logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74189: An unknown error while updating the import modes of the objects passed. %1.

Cause: An unexpected error occurred while updating the import modes of the objects passed.

Action: Contact Oracle Support Services and provide the logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74190: User performing the operation does not have superadmin privilege to promote shared object.

Cause: User Performing the operation does not have superadmin privilege to promote shared object.

Action: Ask portal administrator to assign the user superadmin privilege.
Level: 1

Type: ERROR

Impact: Other

WWU-74191: An unknown error while promoting a given set of external objects. %1.

Cause: An unexpected error occurred while promoting a given set of external objects.

Action: Contact Oracle Support Services and provide the logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74201: The PL/SQL item with the unique identifier %1 will throw a runtime error because the schema %2 associated with it is not present on the target.

Cause: The schema associated with the PL/SQL item does not exist on the target database.

Action: Migrate the schema using the database export/import utilities, and re-associate it with the PL/SQL item.
Level: 1

Type: ERROR

Impact: Other

WWU-74202: The PL/SQL page %1 will throw a runtime error because the schema %2 associated with it is not present on the target. You can migrate the schema later on and re-associate it again.

Cause: The schema does not exist on the target database.

Action: Migrate the schema using the database export/import utilities, and re-associate it with the PL/SQL page.
Level: 1

Type: ERROR

Impact: Other

WWU-74203: The PL/SQL attribute %1 will throw a runtime error because the schema %2 associated with it is not present on the target.

Cause: The schema associated with the PL/SQL attribute does not exist on the target database.

Action: Migrate the schema using the database export/import utilities, and re-associate it with the PL/SQL attribute.
Level: 1

Type: ERROR

Impact: Other

WWU-74204: The LOV %1 associated with %2 attribute does not exist. The LOV is being reset.

Cause: The list of values does not exist on the target.

Action: Bring in the list of values separately, and re-associate or promote it to the transport set in the source. Then re-import it.
Level: 1

Type: ERROR

Impact: Other

WWU-74205: The contained object %1 will not be imported because the container object %2 is reused for the target.

Cause: This can happen when the contained object is forcefully set to reuse mode because the container object was set to reuse mode.

Action: If you want the contained object to be merged to the target, bring in the container object in overwrite mode.
Level: 1

Type: ERROR

Impact: Other

WWU-74206: Unable to import the page group %1. The internal identifier of the new page group already exists.

Cause: The internal identifier of the page group being imported was already in use on the target.

Action: Try importing again. If the retry fails, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74207: Unable to update the properties of the page group %1 being imported.

Cause: An unexpected error occurred while updating the page group properties.

Action: Try importing again. If the retry fails, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74208: Unable to propagate the new internal identifier of the page group being imported.

Cause: The internal identifier of the page group was not updated to all of the page group objects.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74209: Unable to resolve the text attribute with internal identifier %1, of the custom item of the page group with internal identifier %2 .

Cause: Resolution of the item with the text attribute failed.

Action: Try importing again. If the retry fails, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74210: Multiple records found pointing to the same text attribute with internal identifier %1, of the custom item of the page group with internal identifier %2 .

Cause: More than one row was found for the text attribute of the custom item during resolution.

Action: Try importing again. If the retry fails, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74211: Unable to resolve the URL with internal identifier %1, of the page group with internal identifier %2 .

Cause: Resolution of the item with the URL attribute failed.

Action: Try importing again. If the retry fails, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74212: Multiple records found pointing to the same URL with internal identifier %1, of the page group with internal identifier %2 .

Cause: More than one row was found for the URL during resolution.

Action: Try importing again. If the retry fails, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74213: Unable to find the page type function with internal identifier %1 of the page group with internal identifier %2 .

Cause: The attempt to find the page type function failed.

Action: Try importing again. If the retry fails, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74214: Unable to update the attribute %1.

Cause: The attribute update failed.

Action: Try importing again. If the retry fails, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74215: Unable to update the style %1.

Cause: The style update failed.

Action: Try importing again. If the retry fails, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74216: Unable to add translation for category %1 of the page group with internal identifier %2 .

Cause: Failed to add translation for category.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74217: Unable to add translation for perspective %1 of page group with internal identifier %2 .

Cause: Failed to add translation for perspective.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74218: create_item_DAV_err |Due to DAV error, unable to add item %1 of the page group with internal identifier %2 .

Cause: An unexpected DAV error occurred while creating the item on the target.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74219: Due to an unexpected error, unable to add item %1 of the page group with internal identifier %2 .

Cause: An unexpected error occurred while creating the item on the target.

Action: Try importing again. If the retry fails, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74220: Due to DAV error, unable to update item %1 of the page group with internal identifier %2 .

Cause: An unexpected DAV error occurred while updating the item on the target.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74221: Due to an unexpected error, unable to update item %1 of the page group with internal identifier %2 .

Cause: An unexpected error occurred while updating the item on the target.

Action: Try importing again. If the retry fails, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74222: Unable to create the region attributes for the region with unique identifier %1 .

Cause: An unexpected error occurred while creating the region attributes.

Action: Try importing again. If the retry fails, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74223: Unable to create region with unique identifier %1 for the page with internal identifier %2 because it already exists on the target system.

Cause: Could not create region because it already exists on the target system.

Action: Try importing again. If the retry fails, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74224: Unable to create region with unique identifier %1 for the page with internal identifier %2, due to an unexpected error.

Cause: An unexpected error occurred while creating the region on the target.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74225: Unable to update region with unique identifier %1 for the page with internal identifier %2, due to an unexpected error.

Cause: An unexpected error occurred while updating the region on the target.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74226: Unable to update properties of the region with unique identifier %1 because it exists on another page.

Cause: Region exists on another page.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74227: Unable to create Page, Tab, Template, or Navigation Page %1 due to an unexpected error.

Cause: An unexpected error occurred while creating the page on the target.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74228: Unable to update Page, Tab, Template, or Navigation Page %1 due to an unexpected error.

Cause: An unexpected error occurred while updating the page on the target.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74229: Unable to share the portlet instance %1.

Cause: Failed to share the portlet instance on the target.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74230: Unable to locate page group %1 on the target. Child objects of this page group will not be imported.

Cause: The child objects of this page group will not be imported because the page group does not exist on the target.

Action: In the source, promote the page group in your transport set, or export the page group explicitly, then import it.
Level: 1

Type: ERROR

Impact: Other

WWU-74231: The source default language %1 of the page group %2 is either not installed or not available on the target.

Cause: The default language of the page group is either not installed or not available on the target.

Action: Install and make available the default language on the target and re-import.
Level: 1

Type: ERROR

Impact: Other

WWU-74232: Default language %1 of the page group %2 is not installed on the target portal.

Cause: The source page group's default language is not installed on the target portal.

Action: Install the language on the target, and re-import.
Level: 1

Type: ERROR

Impact: Other

WWU-74233: An unexpected error occurred while deleting version %1 of item with unique identifier %2 .

Cause: Deleting an item version has resulted in an unexpected error.

Action: Verify that the page with the item renders properly. If it does not, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74234: Unable to merge approval-related infrastructure due to an unexpected error.

Cause: An unexpected error occurred while merging approval-related infrastructure on the target.

Action: Manually re-create the approval process on the target.
Level: 1

Type: ERROR

Impact: Other

WWU-74235: Unable to synchronize style attributes due to an unexpected error.

Cause: An unexpected error occurred while synchronizing style attributes on the target.

Action: Ensure that all the imported styles have correct settings for their attributes. If they do not, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74236: The template %1 cannot be reused because it has undergone significant changes since the last import.

Cause: The template on the target has undergone significant changes since the last import. This will affect the import of pages that are dependent on the template. Consequently, the template cannot be reused.

Action: Set the import mode to overwrite. Save for later, and rerun pre-check.
Level: 1

Type: ERROR

Impact: Other

WWU-74237: The page %1 has failed precheck because its template %2 cannot be reused. Make %2 overwrite to proceed with import.

Cause: The page's template on the target has undergone significant changes since the last import. Consequently, the template cannot be reused if the pages are to be overwritten.

Action: Set the import mode of the template to overwrite. Save for later, and rerun pre-check.
Level: 1

Type: ERROR

Impact: Other

WWU-74239: Portal template %1 belonging to %2 page group is being imported in replace on import mode. Any changes done to the template objects (items, portlets, etc) on the page(s) using the template will be overwritten by the template replication when the import operation completes.

Cause: Portal template replication deletes all template objects (items, portlets, etc) found in the pages using the template and re-creates them based on the template definition. This will remove any changes done at the page level for those template objects.

Action: If portal template needs to undergo constant updates do not make changes to the pages' template objects. If template objects changes need to be preserved, bring the portal template in reuse mode (uncheck the Replace on Import checkbox in the manifest).
Level: 1

Type: ERROR

Impact: Other

WWU-74240: Portal template %1 belonging to %2 page group is being reused. If pages using the template accompany the template in the same transport set (and are imported in replace on import mode) they might have inconsistent behavior upon import.

Cause: When importing the portal template in reuse mode (and there are significant changes between the source and the target template) and pages using the template are imported in replace on import mode, the pages will not be correctly synchronized with portal template on the target.

Action: Make sure the source and the target template are synchronized first by importing the portal template in overwrite mode. After this synchronization is done, pages using the template can be imported in replace on import mode with the template set to reuse mode.
Level: 1

Type: ERROR

Impact: Other

WWU-74241: The unique identifier of the source page/template/navigation page %1 of the page group %2 does not match the unique identifier of target page/template/navigation page %1. The page name you specified in source is already in use in target.

Cause: A different page already exists on the target with the same name.

Action: Delete the page on the target and import again.
Level: 1

Type: ERROR

Impact: Other

WWU-74242: The unique identifier of the source category %1 of the page group %2 does not match the unique identifier of target category %1. The category name you specified on source is already in use on target.

Cause: A different category already exists on the target with the same name.

Action: Delete the category on the target and import again.
Level: 1

Type: ERROR

Impact: Other

WWU-74243: The source category %1 has been promoted to shared objects but the same category %2 exists on the target in a local page group. The local category on the target cannot be overwritten or reused by the shared category on the source. Promote the local category on the target to shared objects and import the dump file again.

Cause: The source category has been promoted but the same category exists on the target in a local page group.

Action: Promote the local category on the target and re-import.
Level: 1

Type: ERROR

Impact: Other

WWU-74244: The source category %1 belongs to a local page group. The same category %2 on the target has been promoted to shared objects. The shared category on the target cannot be overwritten or reused by the local category on the source.

Cause: The source category belongs to a local page group. The same category on the target has been promoted.

Action: Promote the local category on the source and re-import it.
Level: 1

Type: ERROR

Impact: Other

WWU-74245: The unique identifier of the source perspective %1 of the page group %2 does not match the unique identifier of target perspective %1. The perspective name specified on the source is already in use on the target.

Cause: A different perspective already exists on the target with the same name.

Action: Delete the perspective on the target and import again.
Level: 1

Type: ERROR

Impact: Other

WWU-74246: The source perspective %1 has been promoted to shared objects but the same perspective %2 exists on the target in a local page group. The local perspective on the target cannot be overwritten or reused by the shared perspective on the source. Promote the local perspective on the target to shared objects and import the dump file again.

Cause: The source perspective has been promoted but the same perspective exists on the target in a local page group.

Action: Promote the local perspective on the target and re-import.
Level: 1

Type: ERROR

Impact: Other

WWU-74247: The source perspective %1 belongs to a local page group. The same perspective %2 on the target has been promoted to shared objects. The shared perspective on the target cannot be overwritten or reused by the local perspective on the source.

Cause: The source perspective belongs to a local page group. The same perspective on the target has been promoted.

Action: Promote the local perspective on the source and re-import it.
Level: 1

Type: ERROR

Impact: Other

WWU-74248: Pre-check failed for %1 %2 of %3 pagegroup as %2 is being imported as an external object which does not exist on the target. An external object must exist on the target for it to be re-used.

Cause: Object is being imported as an external object but it does not exist on the target.

Action: Promote the external object in the transport set and re-import.
Level: 1

Type: ERROR

Impact: Other

WWU-74249: Unknown error occurred while resetting syspriv name for page with unique identifier %1. The syspriv name will not be reset for this page.

Cause: An unexpected error occurred while resetting the syspriv name for that page.

Action: Check if all the pages imported appear normally with all the links in the navigator. Otherwise, contact Oracle Support Services with the necessary logs.
Level: 1

Type: ERROR

Impact: Other

WWU-74250: The page configured for generic page portlet: %1 does not exist on target. Therefore resetting the values to default.

Cause: The page configured for portlet was not found. The user might not have added the dependent page to the transport set. Normally you would see a warning status against the explicit object.

Action: Add the dependent page to the transport set and re-import. Or bring in the required page separately and reconfigure it manually.
Level: 1

Type: ERROR

Impact: Other

WWU-74251: The unique identifier(GUID) of the source page group %1 does not match the unique identifier of target page group %1. The page group name you specified in source is already in use in target.

Cause: A different page group already exists on the target with the same name.

Action: Delete the page group on the target and import again.
Level: 1

Type: ERROR

Impact: Other

WWU-74252: Page group %1 is not found in target or in the transport set, this is required for successful import of object type %2 named %3.

Cause: The page group object listed under External Objects is not present on the target or in the transport set. The import cannot proceed for the explicitly selected object since its page group is not available on target.

Action: In source, promote the page group object from the external objects section and export/import the transport set again.
Level: 1

Type: ERROR

Impact: Other

WWU-74253: You (%1) cannot create a shared object since you do not have ANYTRANSPORTSET_MANAGE privilege.

Cause: A shared object can be imported only by a user who has ANYTRANSPORTSET_MANAGE privilege.

Action: Contact your administrator to obtain that privilege and then perform the import.
Level: 1

Type: ERROR

Impact: Other

WWU-74254: HTML template %1 belonging to %2 page group does not exist on the target. All pages and regions using it will be reset.

Cause: The HTML template does not exist on the target and therefore its association was reset.

Action: The user can migrate the HTML template individually and re-associate it.
Level: 1

Type: ERROR

Impact: Other

WWU-74255: Portal template %1 belonging to %2 page group does not exist on the target. All pages and items using it will be reset.

Cause: The Portal template does not exist on the target and therefore its association was reset.

Action: The user can migrate the Portal template individually and re-associate it.
Level: 1

Type: ERROR

Impact: Other

WWU-74256: An unknown fatal error has occurred during the import of transport set. See the debug logs for details.

Cause: An unknown fatal error has occurred during the import of transport set.

Action: See the debug log for details and contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74257: The language %1 (%2) is not installed on target and hence all the language-related data will be deleted.

Cause: The specified language is not installed on target.

Action: Install the language and re-import.
Level: 1

Type: ERROR

Impact: Other

WWU-74263: Deleting the text entries from text/plsql items for the null text handler.

Cause: Text ID is null for the item.

Action: No action required.
Level: 1

Type: ERROR

Impact: Other

WWU-74264: Deleting the text entries from pagetype attributes for the null text handler.

Cause: Text ID is null for pagetype attribute.

Action: No action required.
Level: 1

Type: ERROR

Impact: Other

WWU-74265: Deleting the url entries from url-items for the null url handler.

Cause: URL ID is null for the item.

Action: No action required.
Level: 1

Type: ERROR

Impact: Other

WWU-74266: Deleting the url entries from pagetype attributes for the null url handler.

Cause: URL ID is null for pagetype attribute.

Action: No action required.
Level: 1

Type: ERROR

Impact: Other

WWU-74267: An unknown fatal error has occurred during the export of transport set. See the debug logs for details.

Cause: An unknown fatal error has occurred during the export of transport set.

Action: See the debug log for details and contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74268: The page configured for news announcement OIP portlet: %1 does not exist on target. Therefore resetting the values to null.

Cause: The page configured for portlet was not found. It could have been deleted on the source.

Action: Edit the portlet and re-configure it to point to any valid page.
Level: 1

Type: ERROR

Impact: Other

WWU-74269: The page group configured for OIP summary portlet: %1 was not found on target. Therefore resetting the values to null.

Cause: The pagegroup configured for portlet was not found. This could be due to a data inconistency or an import error.

Action: Edit the portlet and re-configure it to point to a valid pagegroup.
Level: 1

Type: ERROR

Impact: Other

WWU-74271: Mapping not found for Region ID: %1. Hence display all regions property is being set for this page portlet.

Cause: Regions chosen for selective display customization for page portlets have issues during resolution.

Action: Instead of selective regions being displayed for the page portlet, all the regions will be displayed upon import.
Level: 1

Type: ERROR

Impact: Other

WWU-74301: An error occurred while exporting registration properties.

Cause: A problem may have occurred while inserting entries into the registration properties transport table.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74302: An error occurred while exporting user category maps.

Cause: A problem may have occurred while inserting entries into the role maps transport table.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74303: An error occurred while exporting the ws-security information.

Cause: A problem may have occurred while selecting and inserting the entries into the ws-security transport table.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74304: The WSRP provider %1 is configured for ws-security. But, the keystore and certificate information are not migrated.

Cause: The keystore and certificate information are not migrated.

Action: Edit the provider and furnish the keystore and certificate information.
Level: 1

Type: ERROR

Impact: Other

WWU-74305: An error occurred while importing ws-security information for the provider %1.

Cause: A problem may have occurred while inserting entries into the ws-security table.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74402: There has been a metadata inconsistency.

Cause: A metadata inconsistency resulted from the direct manipulation of system tables, such as WWAPP_APPLICATION$, WWAPP_APPLICATION_DETAIL$, WWV_MODULES$, or WWV_MODULE_DETAILS$, or from an incorrect component state during export.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74403: Metadata for %1 is not available in %2.

Cause: Metadata is not available due to the direct manipulation of system tables, such as WWAPP_APPLICATION$, WWAPP_APPLICATION_DETAIL$, WWV_MODULES$, or WWV_MODULE_DETAILS$.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74404: %1 contains more than one row for %2.

Cause: This error message can result from the direct manipulation of system tables, such as WWAPP_APPLICATION$, WWAPP_APPLICATION_DETAIL$, WWV_MODULES$, or WWV_MODULE_DETAILS$.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74405: %1 will not be considered for export.

Cause: Export time pre-checks have failed.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74406: No versions for component %1 are available at the time of this export.

Cause: No versions are available due to the direct manipulation of system tables, such as WWAPP_APPLICATION$, WWAPP_APPLICATION_DETAIL$, WWV_MODULES$, or WWV_MODULE_DETAILS$.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74407: Component %1 is in %2 state at the time of this export.

Cause: At the time of export, a production version was unavailable. This situation can arise if a component has only one version and that version is being edited, or if all the versions of the component are archive versions.

Action: Complete or cancel the edit operation before exporting. Ensure that the component has a production version.
Level: 1

Type: ERROR

Impact: Other

WWU-74408: Incorrect data detected for component %1 in table %2.

Cause: Incorrect data due to the direct manipulation of system tables, such as WWAPP_APPLICATION$, WWAPP_APPLICATION_DETAIL$, WWV_MODULES$, or WWV_MODULE_DETAILS$ was detected.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74409: Metadata for LOV %1 is not available in %2.

Cause: Metadata is not available due to the direct manipulation of metadata tables for lists of values.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74410: More than one row was detected for LOV %1 in %2.

Cause: More than one row was detected for the list of values (LOVs) due to the direct manipulation of metadata tables for LOVs.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74411: Metadata for menu %1 is not available in %2.

Cause: Menu metadata is not available due to the direct manipulation of metadata tables for menus.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74412: Metadata for data component %1 is not available in %2.

Cause: Component metadata is not available due to the direct manipulation of metadata tables for data component.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74413: More than one row detected for data component %1 in %2.

Cause: More than one row was detected for data component due to the direct manipulation of metadata tables for data component.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74414: At the time of this export, DB Provider schema %1 is missing for DB Provider %2.

Cause: Direct user intervention could have deleted the DB Provider schema.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74415: Metadata for owner of %1 is not available in %2.

Cause: Owner metadata is not available due to the direct manipulation of system tables, such as WWAPP_APPLICATION$, WWAPP_APPLICATION_DETAIL$, WWV_MODULES$, or WWV_MODULE_DETAILS$.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74416: Provider ID is null, though the component %1 is exposed as a provider.

Cause: The provider ID is null due to the direct manipulation of system tables, such as WWAPP_APPLICATION$, WWAPP_APPLICATION_DETAIL$, WWV_MODULES$, or WWV_MODULE_DETAILS$.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74417: The value %1 is invalid for flag %2 in table %3 .

Cause: Value is invalid due to the direct manipulation of system tables, such as WWAPP_APPLICATION$, WWAPP_APPLICATION_DETAIL$, WWV_MODULES$, or WWV_MODULE_DETAILS$.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74418: The combination of values in columns EXPOSE_AS_PROVIDER and PROVIDER_ID for component %1 is incorrect in table WWAPP_APPLICATION$.

Cause: The combination of values is incorrect due to the direct manipulation of system tables, such as WWAPP_APPLICATION$, WWAPP_APPLICATION_DETAIL$, WWV_MODULES$, or WWV_MODULE_DETAILS$.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74419: Could not perform pre-check due to insufficient data.

Cause: Direct manipulation of the system tables could have caused the unavailability of data.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74502: An error occurred while exporting data from web provider %1.

Cause: Export of personalization data from the web provider, or one of its portlets, failed.

Action: Check the debug messages for possible reasons for this failure, for example: <br /> 1) Web provider's application server may be down or inaccessible<br /> 2) Underlying network error<br /> If you are unable to further diagnose the problem, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74505: An error occurred while importing data to the web provider %1.

Cause: Import of personalization data to the web provider, or one of its portlets, failed.

Action: Check the debug messages for possible reasons for this failure, for example: <br /> 1) Web provider's application server may be down or inaccessible<br /> 2) Underlying network error<br /> If you are unable to further diagnose the problem, contact Oracle Support.
Level: 1

Type: ERROR

Impact: Other

WWU-74511: The version of the web provider you are trying to export from is not supported. Export cannot proceed for web provider %1.

Cause: The web provider is not version 10.1.2.0.0 or later, or you are trying to export customizations from a Federated Portal Adapter provider.

Action: Contact the web provider's administrator to arrange for this web provider to be upgraded. Note that Federated Portal Adapter providers do not support export/import of customizations.
Level: 1

Type: ERROR

Impact: Other

WWU-74512: The version of the web provider you are trying to import is not supported. Import cannot proceed for this web provider %1.

Cause: The web provider is not version 10.1.2.0.0 or later, or you are trying to import customizations from a Federated Portal Adapter provider.

Action: Contact the web provider's administrator to arrange for this web provider to be upgraded. Note that Federated Portal Adapter providers do not support export/import of customizations.
Level: 1

Type: ERROR

Impact: Other

WWU-74513: The version of the web provider you are trying to export/import is not supported. Export/Import will not proceed for this web provider.

Cause: Import of web provider or some of its portlets failed.

Action: It is possible that this version of the web provider is not supported by export and import. Refer to the documentation for supported versions. If you are still unable to export or import, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74514: Failed to write to transport set.

Cause: An internal error occurred during the import/export operation.

Action: Examine other error messages for more information if available, or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74515: An unexpected error occurred during import.

Cause: An internal error occurred during the import operation.

Action: Examine other error messages for more information if available, or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74516: An unexpected error occurred during export.

Cause: An internal error occurred during the export operation.

Action: Examine other error messages for more information if available, or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74517: Could not connect to web provider at %1.

Cause: Could not connect to the web provider to import or export customizations.

Action: Make sure that the web provider is available and that there are no network issues.
Level: 1

Type: ERROR

Impact: Other

WWU-74518: Timed out after %1ms waiting for response from web provider at %2.

Cause: A timeout occurred during communication with the web provider to import or export customizations.

Action: Make sure that the web provider is available and that there are no network issues.
Level: 1

Type: ERROR

Impact: Other

WWU-74519: Web provider does not implement data transport methods.

Cause: The specified web provider does not support import/export of customization data.

Action: Contact the web provider's administrator to enable this feature, or upgrade the web provider.
Level: 1

Type: ERROR

Impact: Other

WWU-74520: HMAC authentication failed with provider %1 using shared key %2.

Cause: An internal error occurred during the import/export operation.

Action: Examine other error messages for more information if available, or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74521: Web provider server error. Connection %1 unavailable

Cause: An internal error occurred on the remote web provider during the import/export operation.

Action: Examine the error stack for more information, or contact the web provider's adminstrator.
Level: 1

Type: ERROR

Impact: Other

WWU-74522: Unable to create HMAC checksum for provider %1 using shared key %2.

Cause: An internal error occurred during the import/export operation.

Action: Examine other error messages for more information if available, or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74523: An unexpected error occurred during the transport operation.

Cause: An internal error occurred during the transport operation.

Action: Examine other error messages for more information if available, or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74524: Unable to contact remote web provider: invalid URL %1.

Cause: Could not connect to the web provider to import or export customizations due to an invalid provider URL.

Action: Correct the web provider URL.
Level: 1

Type: ERROR

Impact: Other

WWU-74525: Unable to interact with the database.

Cause: An internal error occurred during the import/export operation.

Action: Examine other error messages for more information if available, or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74526: Failed to read from transport set for portlet instance %1, %2.

Cause: An internal error occurred during the import/export operation.

Action: Examine other error messages for more information if available, or contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

WWU-74550: An unexpected error occurred while exporting providers.

Cause: An unexpected error occurred while exporting providers.

Action: Check the debug logs for further details. Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74551: An unexpected error occurred while exporting provider groups.

Cause: An unexpected error occurred while exporting providers groups.

Action: Check the debug logs for further details. Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74552: An unexpected error occurred while exporting proxies.

Cause: An unexpected error occurred while exporting proxies.

Action: Check the debug logs for further details. Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74553: Unexpected Error while exporting portlet preferences

Cause: An unexpected error occurred while exporting portlet preferences.

Action: Check the debug logs for further details. Contact Oracle Support Services before importing.
Level: 1

Type: ERROR

Impact: Other

WWU-74554: An unexpected error has occurred, which has caused the entire provider export to be rolled back.

Cause: An unexpected error has caused the entire provider export to be rolled back.

Action: Check the debug logs for further details and contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74555: An unexpected error occurred while importing proxies.

Cause: An unexpected error occurred while importing proxies.

Action: Check the debug logs for further details and contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74556: An unexpected error occurred while updating providers.

Cause: An unexpected error occurred while updating provider information on the target.

Action: Check the debug logs for further details and contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74557: Preference name %1 for the portlet with reference path %2 could not be created, due to an unexpected error.

Cause: An unexpected error occurred while importing portlet preferences.

Action: Check the debug logs for further details and contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74558: Unable to create the preference value for name %1 of the portlet with reference path %2, due to an unexpected error.

Cause: An unexpected error occurred while importing the portlet's preferences.

Action: Check the debug logs for further details and contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74559: An unexpected error occurred while setting edit defaults for the portlet with reference path %1.

Cause: An unexpected error occurred while setting edit defaults for the imported portlets.

Action: Check the debug logs for further details and contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74560: Unable to validate the portlet with reference path %1.

Cause: An error occurred while validating the portlet.

Action: Check the debug logs for further details and contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74561: An error occurred while executing the web provider with unique identifier %1 of the portlet with reference path %2.

Cause: An unexpected error occurred during web provider execution.

Action: Check the debug logs for further details and contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74562: An error was encountered while the portlet with reference path %1 was executing.

Cause: An unexpected error occurred during portlet execution.

Action: Check the debug logs for further details and contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74563: The portlet with reference path %1 could not be registered due to an unexpected error.

Cause: An unexpected error occurred while registering the portlet.

Action: Check the debug logs for further details and contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74564: The portlet with reference path %1 could not be de-registered due to an unexpected error

Cause: An unexpected error occurred while de-registering the portlet.

Action: Check the debug logs for further details and contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74565: An unexpected error occurred while importing portlet preferences.

Cause: An unexpected error occurred while importing portlet preferences.

Action: Check the debug logs for further details and contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74566: A failure occurred while adding the provider with unique identifier %1 to the repository.

Cause: Provider refresh failed.

Action: Check the debug logs for further details and contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74567: Post-import massaging of provider objects failed due to an unexpected error.

Cause: An unexpected error occurred during post-import massage of providers.

Action: Check the debug logs for further details and contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74568: You do not have permission to register provider %1. If you proceed with the import, all portlets belonging to this provider will be deleted from your pages.

Cause: The user does not have sufficient privileges to register the provider.

Action: Ask the administrator to register the provider, or perform the import as a user who has privilege to register providers.
Level: 1

Type: ERROR

Impact: Other

WWU-74569: Unable to validate information for provider %1. If you proceed with the import, all portlets belonging to this provider will be deleted from your pages.

Cause: The registration API is unable to validate provider information.

Action: Try to register the provider manually. If that fails, check the debug logs for further details and contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74570: Call to register provider %1 failed. If you proceed with the import, all portlets belonging to this provider will be deleted from your pages.

Cause: The call to register provider has failed.

Action: Try to register the provider manually. If that fails, check the debug logs for further details and contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74571: An error occurred during provider %1 registration. If you proceed with the import, all portlets belonging to this provider will be deleted from your pages.

Cause: Provider registration failed.

Action: Try to register the provider manually. If that fails, check the debug logs for further details and contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74572: An unexpected error occurred during provider %1 registration. If you proceed with the import, all portlets belonging to this provider will be deleted from your pages.

Cause: An unexpected error occurred while registering the provider.

Action: Try to register the provider manually. If that fails, check the debug logs for further details and contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74573: Pre-check for database provider %1 failed, as its schema %2 does not exist on the target.

Cause: The database provider cannot be registered because its schema does not exist on the target.

Action: Export/import the schema and try again.
Level: 1

Type: ERROR

Impact: Other

WWU-74574: Pre-check passed with a warning for database provider %1, as its schema %2 differs from the %3 specified on the target.

Cause: Schema registration details differ on the source and target.

Action: Ensure that the provider on the target is valid. If you want the same registration details on the target as on the source, de-register the provider on the target, migrate the necessary schema, and re-import.
Level: 1

Type: ERROR

Impact: Other

WWU-74575: The URL specified during web provider %1 registration is different on the source and target. Import will assume that the providers are the same. Ensure that the provider has the same set of portlets on the source that it has on the target. Source URL: %2. Target URL: %3

Cause: The provider may have been independently registered on the target, using the same name but a different URL.

Action: Ensure that the provider has the same set of portlets on the source as on the target.
Level: 1

Type: ERROR

Impact: Other

WWU-74576: An unexpected error occurred during the provider pre-check. Pre-check has failed.

Cause: An unexpected error occurred during the provider pre-check.

Action: Try to register the provider manually. If that fails, check the debug logs for further details and contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74579: Invalid provider implementation - %2: %1. If you proceed with the import, all portlets belonging to this provider will be deleted from your pages.

Cause: The status of the provider implementation in the database is invalid.

Action: Try to compile the component manually to find out why they cannot compile (for example missing tables, custom procedures and so on). Then fix the issues and repeat the export once the components are compiled.
Level: 1

Type: ERROR

Impact: Other

WWU-74580: Missing provider implementation: %1. If you proceed with the import, all portlets belonging to this provider will be deleted from your pages.

Cause: The provider implementation package is missing.

Action: Compile the provider package and make sure that the implementation package is in valid state in provider schema.
Level: 1

Type: ERROR

Impact: Other

WWU-74581: Missing provider package implementation: %1. If you proceed with the import, all portlets belonging to this provider will be deleted from your pages.

Cause: The provider implementation package is missing.

Action: Compile the provider package and make sure that the implementation package is in valid state in provider schema.
Level: 1

Type: ERROR

Impact: Other

WWU-74582: Missing provider package body implementation: %1. If you proceed with the import, all portlets belonging to this provider will be deleted from your pages.

Cause: The provider implementation package body is missing.

Action: Compile the provider package and make sure that the implementation package is in valid state in provider schema.
Level: 1

Type: ERROR

Impact: Other

WWU-74583: An unexpected error occurred during provider implementation pre check of: %1. If you proceed with the import, all portlets belonging to this provider will be deleted from your pages.

Cause: An unexpected error occurred during the provider implementation pre-check.

Action: If the provider registration fails, check the provider implementation package. Then try to register the provider manually. If that fails, check the debug logs for further details and contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-74584: Invalid component implementation - %2: %1. If you proceed with the import, this component will be deleted from your pages.

Cause: The status of the component implementation in the database is invalid.

Action: Please go to the Portal UI, edit the component, click Apply to create a valid package. Then repeat the export once all the components have a valid package.
Level: 1

Type: ERROR

Impact: Other

WWU-74585: Missing component implementation: %1. If you proceed with the import, this component will be deleted from your pages.

Cause: The component implementation package is missing.

Action: Go to the Portal UI, edit the component which doesnot have a package, click Apply to create a valid package. Then repeat the export once all the components have a valid package.
Level: 1

Type: ERROR

Impact: Other

WWU-74586: Missing component package implementation: %1.If you proceed with the import, this component will be deleted from your pages.

Cause: The component implementation package is missing.

Action: Go to the Portal UI, edit the component which doesnot have a package, click Apply to create a valid package. Then repeat the export once all the components have a valid package.
Level: 1

Type: ERROR

Impact: Other

WWU-74587: Missing component package body implementation: %1. If you proceed with the import, this component will be deleted from your pages.

Cause: The component implementation package body is missing.

Action: Go to the Portal UI, edit the component which doesnot have a package, click Apply to create a valid package. Then repeat the export once all the components have a valid package.
Level: 1

Type: ERROR

Impact: Other

WWU-76778: There were some inconsistencies found and fixed. Check the debug log for further details.

Cause: Some inconsistencies may have occurred as a result of the import.

Action: Check the debug logs for further details on what the inconsistencies were and how they were corrected. Contact Oracle Support if the imported objects caused errors.
Level: 1

Type: ERROR

Impact: Other

WWU-80000: All the explicit objects in the transport set have failed pre-check. The import cannot proceed.

Cause: All the explicitly selected objects have failed the pre-check, either due to missing dependent objects or missing shared references.

Action: Check the pre-check log to determine the cause of failure. After correcting the errors, try importing again.
Level: 1

Type: ERROR

Impact: Other

WWU-80001: Some of the explicit objects in the transport set have failed pre-check. Proceed with import?

Cause: Some of the explicitly selected objects have failed pre-check, either due to missing dependent objects or missing shared references.

Action: Check the pre-check log to determine the cause of failure. After correcting the errors, try importing again.
Level: 1

Type: ERROR

Impact: Other

WWU-80002: Some of the objects in the transport set have failed pre-check with warnings/errors. Proceed with import?

Cause: Some of the objects have failed pre-check, either due to missing dependent objects or missing shared references.

Action: Review the pre-check log to determine the reason for the failure. After correcting the errors, try importing again, or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-80024: Unexpected error occurred while acquiring the transport set - %1

Cause: An unknown exception occurred while acquiring the transport set.

Action: Contact Oracle Support Services and provide the log information.
Level: 1

Type: ERROR

Impact: Other

WWU-80028: Source portal and transport set names cannot be NULL.

Cause: Source portal and transport set values are NULL.

Action: Select a source portal and then select the corresponding transport set from the list.
Level: 1

Type: ERROR

Impact: Other

WWU-80029: Transport set name cannot be NULL.

Cause: Transport set name is null for the selected source portal.

Action: Select a transport set from the list.
Level: 1

Type: ERROR

Impact: Other

WWU-80030: Source portal name cannot be NULL.

Cause: Source portal was not selected from the list of available sources.

Action: Select a source portal and then select the corresponding transport set from the list.
Level: 1

Type: ERROR

Impact: Other

WWU-80041: Transport set %1 does not exist on source portal %2 for acquiring source transport set.

Cause: The transport set was not found on the source portal.

Action: Verify that the transport set name was entered correctly for source. Verify the source DB link. You may need to re-create the transport set.
Level: 1

Type: ERROR

Impact: Other

WWU-80101: Web Provider: %1. Invalid url: %2 or the provider is not running. If you continue with import, the provider registration will fail and all portlet instances for this provider will be deleted from all pages being imported.

Cause: Web provider URL is invalid.

Action: Check the URL in a browser and make sure the url and proxy settings are correct before importing the provider.
Level: 1

Type: ERROR

Impact: Other

WWU-80102: Unexpected error occurred while populating provider record. %1

Cause: Unexpected error occurred while populating provider record.

Action: Contact Oracle Support Services and provide the logs.
Level: 1

Type: ERROR

Impact: Other

WWU-80154: Web provider : %1. Provider may not be running or Invalid url: %2. If you continue with import, all portlet instances for this provider will be deleted from pages being imported.

Cause: The web provider URL is invalid or provider may be down.

Action: Check the URL in a browser and make sure the url and proxy setup is correct for the provider.
Level: 1

Type: ERROR

Impact: Other

WWU-80157: An unexpected error occurred while checking free space. %1.

Cause: An unexpected error occurred while checking free space.

Action: Contact Oracle Support Services and provide the logs.
Level: 1

Type: ERROR

Impact: Other

WWU-80158: The data from the source portal could not be acquired. %1

Cause: The transport set data could not be acquired from the selected source portal.

Action: Select the source portal and acquire the desired transport set again.
Level: 1

Type: ERROR

Impact: Other

WWU-80161: job_queue_processes value :%1 which should be greater than %2.

Cause: The job queue processes value should be greater than %2 to allow the execution of background jobs.

Action: Increase the job_queue_processes before starting any export/import operations.
Level: 1

Type: ERROR

Impact: Other

WWU-80165: Unexpected error occurred while validating HTTP URL for provider %1. %2.

Cause: An unexpected error occurred while validating HTTP URL.

Action: Contact Oracle Support Services and provide the logs.
Level: 1

Type: ERROR

Impact: Other

WWU-80181: An unexpected error occurred while checking roles and privileges for user:%1.

Cause: An unexpected error occurred while checking roles and privileges for user.

Action: Contact Oracle Support Services and provide the logs.
Level: 1

Type: ERROR

Impact: Other

WWU-80182: An unexpected error occurred while checking privileges to perform import. %1.

Cause: An unexpected error occurred while checking privileges to perform import.

Action: Contact Oracle Support Services and provide the logs.
Level: 1

Type: ERROR

Impact: Other

WWU-80183: An unexpected error occurred while checking the sso schema dblink. %1.

Cause: An unexpected error occurred while checking the sso schema dblink.

Action: Contact Oracle Support Services and provide the logs.
Level: 1

Type: ERROR

Impact: Other

WWU-80184: An unexpected error occurred while checking languages. %1.

Cause: An unexpected error occurred while checking languages.

Action: Contact Oracle Support Services and provide the logs.
Level: 1

Type: ERROR

Impact: Other

WWU-80185: An unexpected error occurred while checking providers. %1.

Cause: An unexpected error occurred while checking providers.

Action: Contact Oracle Support Services and provide the logs.
Level: 1

Type: ERROR

Impact: Other

WWU-80186: An unexpected error occurred while checking provider DB schemas. %1.

Cause: An unexpected error occurred while checking provider DB schema.

Action: Contact Oracle Support Services and provide the logs.
Level: 1

Type: ERROR

Impact: Other

WWU-80187: An unexpected error occurred during Listing privileges and roles for Provider DB schema:%1. %2

Cause: An unexpected error occurred during the provider DB schema privileges and roles check.

Action: Contact Oracle Support Services and provide the logs.
Level: 1

Type: ERROR

Impact: Other

WWU-80188: An unexpected error occurred while checking the portal privileges granted for Provider schema:%1. %2

Cause: An unexpected error occurred while checking the portal privileges granted for Provider schema.

Action: Contact Oracle Support Services and provide the logs.
Level: 1

Type: ERROR

Impact: Other

WWU-80189: An unexpected error occurred during System pre-check. Mode:%1. %2

Cause: An unexpected error occurred during System precheck.

Action: Contact Oracle Support Services and provide the logs.
Level: 1

Type: ERROR

Impact: Other

WWU-80192: Component %1 was not found. This component was exported as external object and expected to exist on target before import.

Cause: This component was exported as external object and expected to exist on target before import.

Action: Make sure that this component exists with valid implementation before running import.
Level: 1

Type: ERROR

Impact: Other

WWU-80193: DB Schema entry is missing for owner %1 for component %2. This component was exported as external object and expected to exist on target before import.

Cause: This component was exported as external object and expected to exist on target before import.

Action: Make sure the component owner schema exists before running import.
Level: 1

Type: ERROR

Impact: Other

WWU-80194: The transport set %1 already exists on target.

Cause: The transport set you are trying to acquire already exists on target.

Action: Delete the transport set from browse transport set and try to acquire again.
Level: 1

Type: ERROR

Impact: Other

WWU-80202: An unexpected error occurred while checking components. %1.

Cause: An unexpected error occurred while checking components.

Action: Contact Oracle Support Services and provide the logs.
Level: 1

Type: ERROR

Impact: Other

WWU-80203: An unexpected error occurred while checking page group. %1.

Cause: An unexpected error occurred while checking page groups.

Action: Contact Oracle Support Services and provide the logs.
Level: 1

Type: ERROR

Impact: Other

WWU-80211: An unexpected error occurred while checking default languages for page groups. %1.

Cause: An unexpected error occurred while checking pagegroups.

Action: Contact Oracle Support Services and provide the logs.
Level: 1

Type: ERROR

Impact: Other

WWU-80285: Source Portal %1(%2) could not be validated.The portal versions between source and target portals are different.

Cause: The portal versions are not matching between source and target portals.

Action: Select a portal schema which has the same portal version as the target portal schema.
Level: 1

Type: ERROR

Impact: Other

WWU-80286: Unexpected error occurred while validating source portal %1(%2) . %3.

Cause: Unexpected error occurred while validation source portal.

Action: Contact Oracle support Services.
Level: 1

Type: ERROR

Impact: Other

WWU-80287: The souce portal %1(%2) cannot be registered.The source portal selected to register is pointing to itself.

Cause: The Database link selected to register as a source portal is pointing to the current schema.

Action: Select some other source portal.
Level: 1

Type: ERROR

Impact: Other

WWU-80289: The schema %1 in DBLink %2 is not a portal schema.

Cause: The DBLink is not pointing to valid 11g Portal Schema.

Action: Select a DBLink pointing to any valid 11g Portal Schema.
Level: 1

Type: ERROR

Impact: Other

WWU-80309: Source portal with name %1 is already registered. Enter another name.

Cause: The source portal name you are trying to register already exists.

Action: Enter another unique name.
Level: 1

Type: ERROR

Impact: Other

WWU-80317: An unexpected error occurred while checking external applications. %1.

Cause: An unexpected error occurred while checking external apps.

Action: Contact Oracle Support Services and provide the logs.
Level: 1

Type: ERROR

Impact: Other

WWU-80337: There were some inconsistencies found and hence export process is aborted. Check the debug log for further details. Fix those inconsistencies, by running schema validation in <a href=\"%1\">cleanup mode</a> to proceed.

Cause: Portal has inconsistent data and hence the process aborted.

Action: Fix those inconsistencies by running the schema validation in cleanup mode.
Level: 1

Type: ERROR

Impact: Other

WWU-80338: There were some inconsistencies found and hence import process is aborted. Check the debug log for further details. Fix those inconsistencies, by running schema validation in <a href=\"%1\">cleanup mode</a> to proceed.

Cause: Portal has inconsistent data and hence the process aborted.

Action: Fix those inconsistencies by running the schema validation in cleanup mode.
Level: 1

Type: ERROR

Impact: Other

WWU-80349: Invalid pagination option

Cause: Either no value or an invalid value has been specified for the Paginate Objects per section.

Action: Specify a numeric value for the Paginate Objects per section.
Level: 1

Type: ERROR

Impact: Other

WWU-80353: DBLink to SSO schema %1 is not reachable.

Cause: DBLink used to retrieve the external application list from SSO schema is not accessible.

Action: Check the dblink.
Level: 1

Type: ERROR

Impact: Other

WWU-80361: An unexpected error occurred while checking DBLinks for provider DB schema. %1.

Cause: An unexpected error occurred while checking DBLinks for provider DB schema.

Action: Contact Oracle Support Services and provide the logs.
Level: 1

Type: ERROR

Impact: Other

WWU-80365: The transport set name %1 entered already exists

Cause: A transport set with the same name already exists in the system.

Action: Give a different name to the transport set.
Level: 1

Type: ERROR

Impact: Other

WWU-80367: WSRP Provider: %1. Invalid URL: %2 or the provider is not running. If you continue with import, the provider registration will fail and all portlet instances for this provider will be deleted from all pages being imported.

Cause: WSRP provider URL is invalid.

Action: Check the URL in a browser and make sure the URL and proxy settings are correct before importing the provider.
Level: 1

Type: ERROR

Impact: Other

WWU-80375: Unexpected error occurred while copying the transport set -%1 to a new transport set - %2. %3

Cause: An unknown exception occurred while copying.

Action: Contact Oracle Support Services and provide the log information.
Level: 1

Type: ERROR

Impact: Other

WWU-80382: TNS entry error %1

Cause: A connection to a database or other service was requested using a connect identifier and the connect identifier specified could not be resolved into a connect descriptor using one of the naming methods configured.

Action: Check the net service name used as the connect identifier in the database link.
Level: 1

Type: ERROR

Impact: Other

WWU-80421: Directory Object %1 does not exist. Create the directory object and try again. Otherwise configure a different directory object to be used for dump creation using the Global Settings page.

Cause: The Directory object %1 does not exist.

Action: Configure the directory object to be used for dump creation using the Global Settings page .
Level: 1

Type: ERROR

Impact: Other

WWU-83014: Unable to add the dependencies of generic page portlet for page group identifier %1. An attempt to import this transport set could result in errors.

Cause: An unexpected error occurred while adding the dependencies of the generic page portlet. The export proceeded without the dependencies. If the resulting transport set is imported, the generic page portlet could result in errors.

Action: Contact Oracle Support Services and provide the export logs.
Level: 1

Type: ERROR

Impact: Other

WWU-83015: An unknown error while calculating manifest data.%1

Cause: An unexpected error occurred while calculating dependencies.

Action: Contact Oracle Support Services and provide the logs.
Level: 1

Type: ERROR

Impact: Other

WWU-83016: An unknown error in altering dependency list.%1

Cause: An unexpected error occurred while calculating dependencies.

Action: Contact Oracle Support Services and provide the logs.
Level: 1

Type: ERROR

Impact: Other

WWU-83017: There are no objects in the transport set.

Cause: There are no objects in the transport set.

Action: Add some objects to transport set and export again.
Level: 1

Type: ERROR

Impact: Other

WWU-83021: Unexpected error while generating pagegroup dependencies for search portlet.

Cause: An unexpected error occurred while calculating pagegroup dependencies for search portlet preferences.

Action: Contact Oracle Support Services and provide the dependency logs.
Level: 1

Type: ERROR

Impact: Other

WWU-83022: Unexpected error while generating image dependencies for search portlet.

Cause: An unexpected error occurred while calculating image dependencies for search portlet preferences.

Action: Contact Oracle Support Services and provide the dependency logs.
Level: 1

Type: ERROR

Impact: Other

WWU-83023: Unexpected error while generating style dependencies for search portlet.

Cause: An unexpected error occurred while calculating style dependencies for search portlet preferences.

Action: Contact Oracle Support Services and provide the dependency logs.
Level: 1

Type: ERROR

Impact: Other

WWU-83024: Unexpected error while generating attribute dependencies for search portlet.

Cause: An unexpected error occurred while calculating attribute dependencies for search portlet preferences.

Action: Contact Oracle Support Services and provide the dependency logs.
Level: 1

Type: ERROR

Impact: Other

WWU-83025: Unexpected error while calculating itemtype dependencies for search portlet.

Cause: An unexpected error occurred while calculating itemtype dependencies for search portlet preferences.

Action: Contact Oracle Support Services and provide the dependency logs.
Level: 1

Type: ERROR

Impact: Other

WWU-83026: Unexpected error while calculating page dependencies for search portlet.

Cause: An unexpected error occurred while calculating page dependencies for search portlet preferences.

Action: Contact Oracle Support Services and provide the dependency logs.
Level: 1

Type: ERROR

Impact: Other

WWU-83027: Unexpected error while calculating category dependencies for search portlet.

Cause: An unexpected error occurred while calculating category dependencies for search portlet preferences.

Action: Contact Oracle Support Services and provide the dependency logs.
Level: 1

Type: ERROR

Impact: Other

WWU-83028: Unexpected error while calculating perspective dependencies for search portlet.

Cause: An unexpected error occurred while calculating perspective dependencies for search portlet preferences.

Action: Contact Oracle Support Services and provide the dependency logs.
Level: 1

Type: ERROR

Impact: Other

106 WWV-00100 to WWV-61294

WWV-00100: Unexpected error encountered in %0 (%1).

Cause: An unhandled exception was raised during this operation.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-00201: cannot initialize component ID: %1, version: %2

Cause: The attributes of the component wizard could not be initialized.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-00202: cannot commit attributes

Cause: The attributes of the component wizard could not be saved. This could be caused by data inconsistency or an internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-00203: exception

Cause: The attributes of the component wizard could not be initialized or could not be saved.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-00204: failure to save report columns attribute values

Cause: Some attributes of the report were not saved, possibly because they were invalid.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-00205: failure of the set default columns

Cause: Some attributes were not saved, possibly because they were invalid.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-00206: The selected tables or views contain column types that are not supported.

Cause: Columns with unsupported types were selected for rendering.

Action: Change the query. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-00207: The selected objects contain columns that are either LOBs, object tables, or user-defined types.

Cause: The columns selected for rendering were unsupported types.

Action: Change the query. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-00208: Attempting access to an Oracle Multimedia or LOB object over a remote database. This is not supported.

Cause: An attempt was made to access an Oracle Multimedia or LOB object over a remote database. This action is not supported.

Action: Change the query or column selection. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-00250: cannot save attribute name: %1

Cause: The attributes of the component could not be saved.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-00251: cannot initialize component ID: %1, version: %2

Cause: The attributes of the component could not be initialized.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-00252: cannot commit attributes

Cause: The attributes of the component could not be saved.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-00253: exception

Cause: The attributes of the component wizard could not initialized or could not be saved.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-00254: failure to save report columns attribute values

Cause: Some attributes of the report were not saved, possibly because they were invalid.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-00255: failure to set default columns

Cause: Some attributes were not saved, possibly because they were invalid.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-00256: The selected Table or View contains column types that are not supported.

Cause: The columns selected for rendering were unsupported types.

Action: Change the query. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-00402: An unexpected error occurred: %1.

Cause: An unhandled exception was raised during this operation.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-00427: failure to set component %1 as Portal DB Provider object: %2

Cause: A component with the same ID already existed. The table WWAPP_APPLICATION_DETAIL$ may have been directly manipulated.

Action: Use datafix scripts to help resolve this error. Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-00428: failure to delete component %1 from Portal DB Provider: %2

Cause: The component was not deleted from the Portal DB Provider.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-00444: Portal DB Provider %1 does not exist.

Cause: The Portal DB provider could not be found.

Action: Verify that the provider exists. If it does not, create one.
Level: 1

Type: ERROR

Impact: Other

WWV-00482: unable to find Portal DB Provider for component %1

Cause: The application on which the component was built could not be found, possibly because it was removed from the application metadata table.

Action: Verify that the underlying application exists in the Navigator. If it does not, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-00486: Unable to run component %1. Package %2 does not exist.

Cause: An attempt was made to run a package but the user did not have the appropriate privileges to run it or the package did not exist.

Action: Check the user's privilege level. If the user has the appropriate privileges, verify that the package exists in the schema.
Level: 1

Type: ERROR

Impact: Other

WWV-00495: Display Name is already used by another component in this Portal DB Provider %1. Specify another Display Name.

Cause: The display name specified was already being used by another component.

Action: Specify a different, unique display name.
Level: 1

Type: ERROR

Impact: Other

WWV-00496: New Component Display Name is already used by another component in this Portal DB Provider %1. Specify another Display Name.

Cause: The display name specified was already being used by another component.

Action: Specify a different, unique name.
Level: 1

Type: ERROR

Impact: Other

WWV-00547: The Portal DB Provider schema %1 does not exist or is not a valid schema.

Cause: The schema specified could not be found.

Action: Verify that the schema name is correct or create the schema.
Level: 1

Type: ERROR

Impact: Other

WWV-00550: unexpected error

Cause: An unhandled exception was raised during the operation.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-00551: cannot find columns for table %1

Cause: The table selected did not have any columns of types supported by the component.

Action: Check the table for column types.
Level: 1

Type: ERROR

Impact: Other

WWV-00552: failure to parse query %1

Cause: The SQL INSERT statement could not be parsed due to incorrect syntax or usage, or a reference to inaccessible objects.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-00553: failure to fetch rows for query %1

Cause: The SQL SELECT statement could not fetch any rows.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-00600: Select query cannot be created.

Cause: An unexpected error was encountered while generating the SELECT statement.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-00601: failure during code generation

Cause: An unexpected error was encountered during code generation.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-00602: failure during code generation

Cause: An unexpected error was encountered during code generation.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-00605: failure to initialize builder attributes

Cause: Design time metadata for an image chart could not be fetched.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-00651: Failure to fetch rows. Raised exception %1

Cause: The rows could not be fetched.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-00652: Failure to define columns. Raised exception %1

Cause: No columns were defined in the query.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-00653: failure to parse the query %1

Cause: The query could not be parsed.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-00654: null cursor for the query %1

Cause: There was an error while parsing the query.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-00700: unable to find object %1

Cause: The object could not be found or the user did not have sufficient privileges to retrieve it.

Action: Verify that the object exists and, if it does, that the user has the appropriate privileges.
Level: 1

Type: ERROR

Impact: Other

WWV-00704: failure to get source for object %1: %2

Cause: The source for the requested object could not be contacted.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-00850: error in create_package

Cause: The package for the component could not be created. This could be because a package with the same name already existed, there was a problem with the underlying schema, or the package specification did not exist.

Action: Verify that the schema exists, a package with the same name exists, and the package specification exists.
Level: 1

Type: ERROR

Impact: Other

WWV-00851: error in create_package_body

Cause: The package body for the component could not be created. This could be because a package body with the same name already existed, there was a problem with the underlying schema, or the package specification did not exist.

Action: Verify that the schema exists, a package with the same name exists, and the package specification exists.
Level: 1

Type: ERROR

Impact: Other

WWV-00852: error in create_show

Cause: A problem was encountered while building the show procedure of the package.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-00853: error in create_show_parms

Cause: A problem was encountered while building the show_params procedure of the package.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-00854: error in create_help

Cause: A problem was encountered while building the help procedure of the package.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-00855: error in create_help_parms

Cause: A problem was encountered while building the help_params procedure of the package.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-00856: error in create_calendar_call

Cause: A problem was encountered while creating the calendar.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-00866: failure to initialize builder attributes

Cause: Design time metadata for this calendar component could not be fetched.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-00900: error in create_package

Cause: The package for the component could not be created. This could be because a package with the same name already existed, there was a problem with the underlying schema, or the package specification did not exist.

Action: Verify that the schema exists, a package with the same name exists, and the package specification exists.
Level: 1

Type: ERROR

Impact: Other

WWV-00901: error in create_package_body

Cause: The package body for the component could not be created. This could be because a package body with the same name already existed, there was a problem with the underlying schema, or the package specification did not exist.

Action: Verify that the schema exists, a package with the same name exists, and the package specification exists.
Level: 1

Type: ERROR

Impact: Other

WWV-00902: error in create_show

Cause: A problem was encountered while building the show procedure of the package.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-00903: error in create_show_parms

Cause: A problem was encountered while building the show_params procedure of the package.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-00904: error in create_help

Cause: A problem was encountered while building the help procedure of the package.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-00905: error in create_help_parms

Cause: A problem was encountered while building the help_params procedure of the package.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-00906: error in create_chart_call

Cause: A problem was encountered while creating the chart call.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-00907: error in create_about

Cause: A problem was encountered while building the about procedure of the package.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-00908: error in create_about_parms

Cause: A problem was encountered while building the about_params procedure of the package.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-01000: error in create_package

Cause: The package for the component could not be created. This could be because a package with the same name already existed, there was a problem with the underlying schema, or the package specification did not exist.

Action: Verify that the schema exists, a package with the same name exists, and the package specification exists.
Level: 1

Type: ERROR

Impact: Other

WWV-01001: error in create_package_body

Cause: The package body for the component could not be created. This could be because a package body with the same name already existed, there was a problem with the underlying schema, or the package specification did not exist.

Action: Verify that the schema exists, a package with the same name exists, and the package specification exists.
Level: 1

Type: ERROR

Impact: Other

WWV-01002: error in create_show

Cause: A problem was encountered while building the show procedure of the package.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-01003: error in create_show_parms

Cause: A problem was encountered while building the show_params procedure of the package.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-01004: error in create_help

Cause: A problem was encountered while building the help procedure of the package.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-01005: error in create_help_parms

Cause: A problem was encountered while building the help_params procedure of the package.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-01006: error in create_report_call

Cause: A problem was encountered while creating the report call.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-01007: error in create_show_body

Cause: A problem was encountered while creating the show_body call.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-01008: error in create_show_parm_list

Cause: A problem was encountered while creating the show_parm_list.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-01243: The template name is blank.

Cause: A name was not specified for the template.

Action: Specify a name for the template.
Level: 1

Type: ERROR

Impact: Other

WWV-01244: The template name already exists.

Cause: The template name specified already existed.

Action: Specify a different name for the template.
Level: 1

Type: ERROR

Impact: Other

WWV-01265: Failure to save template. Obsolete banner tags are not allowed.

Cause: The template could not be saved because an obsolete banner tag was used in the template.

Action: Remove the tag that is no longer supported. Refer to the Oracle Application Server Portal User's Guide for a list of supported tags.
Level: 1

Type: ERROR

Impact: Other

WWV-01283: The following tags can be used in the HTML as substitution variables for information that is provided by pages.

Cause: The template could not be created because an obsolete banner tag was used in the template.

Action: Remove the tag that is no longer supported. Refer to the Oracle Application Server Portal User's Guide for a list of supported tags.
Level: 1

Type: ERROR

Impact: Other

WWV-01284: The template definition is blank.

Cause: A template definition was not specified.

Action: Enter HTML for the template.
Level: 1

Type: ERROR

Impact: Other

WWV-01450: Failure to submit DBMS job: %1. The HTTP cookie might be too long. Close all browser windows and try again.

Cause: The job was not submitted. This could be because the HTTP cookie was too long.

Action: Close all browser windows and try again.
Level: 1

Type: ERROR

Impact: Other

WWV-01451: error executing batch job %1: %2

Cause: The job failed to execute.

Action: Verify that the job is submitted and running.
Level: 1

Type: ERROR

Impact: Other

WWV-01452: error executing batch job %0

Cause: The job failed to execute.

Action: Verify that the job is submitted and running.
Level: 1

Type: ERROR

Impact: Other

WWV-01500: unable to expire old results

Cause: Results could not be deleted from the batch submissions table. This could be because the table did not exist or there was an underlying database problem.

Action: Ensure that the database is not experiencing a rollback segment problem, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-01539: insufficient privileges

Cause: The user did not have sufficient privileges for the attempted operation.

Action: Log in as a user with the appropriate privileges. Alternatively, contact the portal administrator and request that the appropriate privileges be granted.
Level: 1

Type: ERROR

Impact: Other

WWV-01540: The job does not exist or the user does not have privilege to edit the job.

Cause: The specified job could not be found or the user did not have sufficient privileges.

Action: Verify that the job exists. If it exists, log in as a user with the appropriate privileges or contact the portal administrator and request that the appropriate privileges be granted.
Level: 1

Type: ERROR

Impact: Other

WWV-01603: failure to parse query

Cause: The SQL statement could not be parsed due to incorrect syntax or usage, or because it referred to inaccessible objects.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-01801: exception

Cause: An attempt was made to edit a dynamic page that contained more than 32 KB of HTML code.

Action: Avoid writing more than 32 KB of HTML code in a dynamic page.
Level: 1

Type: ERROR

Impact: Other

WWV-01805: unable to save check box

Cause: A limit was exceeded, such as using more than 15 check boxes in an HTML page.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-01809: unable to initialize component attributes (saved values)

Cause: A limit was exceeded, such as using more than 15 check boxes in an HTML page.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-01810: unable to initialize component attributes (base version)

Cause: The component attributes were not initialized because the component metadata could not be loaded.

Action: Contact Oracle Support Services to verify that the component metadata is intact.
Level: 1

Type: ERROR

Impact: Other

WWV-01814: unable to clean up component ID: %1, version: %2

Cause: The component metadata could not be deleted, possibly because there were some dependencies that had not been eliminated.

Action: Contact Oracle Support Services to verify that the component metadata is intact.
Level: 1

Type: ERROR

Impact: Other

WWV-01817: unable to obtain lock on component ID: %1, version %2 - check status

Cause: This component was already locked by another user.

Action: Unlock the component before attempting to edit it.
Level: 1

Type: ERROR

Impact: Other

WWV-01820: unable to initialize attribute for component ID %1, version %2

Cause: The component was not initialized because the component metadata could not be loaded.

Action: Contact Oracle Support Services to verify that the component metadata is intact.
Level: 1

Type: ERROR

Impact: Other

WWV-01822: unable to save hidden value for attribute ID: %1 for value: %2

Cause: An attempt to save the component metadata failed.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-01823: unable to save value for attribute ID: %1 for value: %2

Cause: An attempt to save the component metadata failed.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-01824: unable to save array value for attribute ID: %1 for value: %2

Cause: An attempt to save the component metadata failed.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-01825: unable to save LONG value for attribute ID: %1

Cause: An attempt to save the component metadata failed.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-01830: invalid component type: %1

Cause: The component type could not be found, possibly because it was removed from the master table.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-01831: invalid component ID: %1 or version: %2

Cause: The component ID or the module ID could not be found.

Action: Verify that a component with this ID exists.
Level: 1

Type: ERROR

Impact: Other

WWV-01832: unable to clean up components table for component ID: %1 or version: %2

Cause: The components table could not be cleaned up because there were dependencies that had not been cleaned up.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-01833: unable to create component for component type: %1

Cause: The component could not be created, possibly because there was an error while inserting into the component metadata table.

Action: Verify that this component already exists, or contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

WWV-01834: unable to execute function: %1

Cause: An attempt to execute a function in the component builder failed.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-01835: unable to initialize module attributes

Cause: The module attributes were not initialized because the component metadata could not be loaded.

Action: Contact Oracle Support Services to verify that the component metadata is intact.
Level: 1

Type: ERROR

Impact: Other

WWV-01838: wwv_utlattr.save_attribute_value failure

Cause: One or more component attributes could not be saved, possibly because the attributes were invalid.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-01839: wwv_utlattr.commit_attributes failure

Cause: One or more component attributes could not be saved, possibly because the attributes were invalid.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-01841: WWV_BUILDER.GET_LOV_FIRST_VALUE: fetch_row failure

Cause: Metadata might have been inconsistent.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-01849: failure to initialize builder attributes

Cause: Builder attributes could not be initialized because the design time metadata for the component could not be fetched.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-02124: unable to render report

Cause: The report cannot be rendered because the user did not the have appropriate privileges to select from the wwlog_activity$ table, or because the table did not exist.

Action: Verify that the table exists and that the user has the appropriate privileges.
Level: 1

Type: ERROR

Impact: Other

WWV-02192: unable to locate object

Cause: The component could not be found in the component metadata.

Action: Verify that the component appears in the Navigator.
Level: 1

Type: ERROR

Impact: Other

WWV-02200: Unable to delete object %0 (version %1). General error: %2.

Cause: The component version could not be found in the component metadata.

Action: Ensure that the component version exists.
Level: 1

Type: ERROR

Impact: Other

WWV-02210: No version is selected.

Cause: An attempt was made to delete a component version, but no versions were selected.

Action: Select the versions to delete by clicking the appropriate check boxes.
Level: 1

Type: ERROR

Impact: Other

WWV-02215: unable to drop PACKAGE: %0

Cause: The package could not be dropped because the user did not have the appropriate privileges or because the package did not exist.

Action: Ensure that the package exists in the schema and that the user has the appropriate privileges.
Level: 1

Type: ERROR

Impact: Other

WWV-02700: Unable to create Data Component %0. Data Component names must be unique. After creating a Data Component, click an edit link to change it.

Cause: A data component with the specified name already existed.

Action: Specify a different name for the component.
Level: 1

Type: ERROR

Impact: Other

WWV-02751: failure to save parameters

Cause: An error occurred in the user preference storage subsystem.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-03008: Column %1 is of type %2, therefore you cannot specify the precision attribute.

Cause: A value was specified for the precision attribute but the column was a data type that did not support the precision attribute.

Action: Do not specify a value for the precision attribute for columns of this data type.
Level: 1

Type: ERROR

Impact: Other

WWV-03009: Column %1 is of type %2, therefore you cannot specify the length or precision attribute.

Cause: A value was specified for the precision attribute but the column was a data type that did not support the precision attribute.

Action: Do not specify a value for the precision attribute for columns of this data type.
Level: 1

Type: ERROR

Impact: Other

WWV-03010: The length attribute is mandatory for column %1 of type %2. Enter a valid number.

Cause: The length attribute was not specified for the column.

Action: Specify a valid length for the column.
Level: 1

Type: ERROR

Impact: Other

WWV-03011: The length attribute for column %1 is not numeric. Enter a valid number.

Cause: A nonnumeric value was specified for the length attribute.

Action: Specify a valid number for the length attribute.
Level: 1

Type: ERROR

Impact: Other

WWV-03702: unable to find table: %0.%1

Cause: The table could not be found or the user did not have the appropriate privileges.

Action: Ensure that the table exists and that the user has appropriate privileges to access it.
Level: 1

Type: ERROR

Impact: Other

WWV-04008: failure to create help procedure - %1

Cause: An unexpected error occurred while generating or compiling a frame driver component package body.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-04150: failure to get attribute for %1

Cause: An unexpected error occurred while fetching the value of the attribute. This could be the result of inconsistent metadata.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-04151: failure to create cache for %1

Cause: An unexpected error occurred while generating the PL/SQL code for portlet caching.

Action: Regenerate the component. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-04152: invalid value %1

Cause: The value specified for the cache expiry period was incorrect.

Action: Provide an integer value for the cache expiry period.
Level: 1

Type: ERROR

Impact: Other

WWV-04154: failure to invoke Oracle Reports generator, returned %0

Cause: An unexpected error occurred while trying to invoke the Oracle Reports generator.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-04300: failure to execute - %1

Cause: A SQL or PL/SQL statement could not be parsed due to incorrect syntax or usage, or because it referred to an inaccessible object.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-05516: failure to unlock component: %1

Cause: The component could not be unlocked.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-06000: The font name specified already exists. Enter a new name that is unique.

Cause: A font with the specified name already existed.

Action: Specify a different name for the font.
Level: 1

Type: ERROR

Impact: Other

WWV-06001: The font value is invalid.

Cause: The value specified for the font was invalid.

Action: Specify a valid value for the font.
Level: 1

Type: ERROR

Impact: Other

WWV-06002: Cannot leave the font name blank. Enter a name for the font.

Cause: A name was not specified for the font.

Action: Specify a name for the font.
Level: 1

Type: ERROR

Impact: Other

WWV-06013: The specified font name does not exist.

Cause: This specified font could not be found.

Action: Check the name of the font and provide a valid name.
Level: 1

Type: ERROR

Impact: Other

WWV-06017: Cannot leave the font value blank. Enter a value for the font.

Cause: A value was not specified for the font.

Action: Specify a value for the font.
Level: 1

Type: ERROR

Impact: Other

WWV-06018: The font name can contain only alphanumeric characters and a set of special characters composed of _ $ # , and space.

Cause: The specified font name included invalid characters.

Action: Specify a name that contains only alphanumeric characters and the following special characters: _ $ # and space.
Level: 1

Type: ERROR

Impact: Other

WWV-06029: Font Name already exists.

Cause: A font with the specified name already existed.

Action: Specify a different name for the font.
Level: 1

Type: ERROR

Impact: Other

WWV-06100: failure to add image

Cause: An attempt to add an image failed.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-06101: Unable to add image because the image name is null.

Cause: A name was not specified for the image.

Action: Specify a name for the image.
Level: 1

Type: ERROR

Impact: Other

WWV-06102: failure to update image

Cause: An attempt to update an image failed.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-06103: Unable to update image because the image ID is null.

Cause: An attempt was made to update an image but the image ID was null.

Action: Ensure that the image exists.
Level: 1

Type: ERROR

Impact: Other

WWV-06117: The image specified does not exist.

Cause: The specified image could not be found.

Action: Specify the name of an image that does exist.
Level: 1

Type: ERROR

Impact: Other

WWV-06118: Cannot leave the image file name blank. Enter a file name for the image.

Cause: A file name was not specified for the image.

Action: Specify a valid file name for the image.
Level: 1

Type: ERROR

Impact: Other

WWV-06123: The specified image does not exist.

Cause: The specified image could not be found.

Action: Specify a valid image name.
Level: 1

Type: ERROR

Impact: Other

WWV-06127: The image name can contain only alphanumeric characters or the special characters _ $ # , and space.

Cause: The specified image name included invalid characters.

Action: Specify an image name that contains only alphanumeric characters and the following special characters: _ $ # and space.
Level: 1

Type: ERROR

Impact: Other

WWV-06133: Image name already exists.

Cause: An image with the specified name already existed.

Action: Specify a different name for the image.
Level: 1

Type: ERROR

Impact: Other

WWV-06200: failure to %1: %2

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-06201: The JavaScript name can contain only alphanumeric characters and the special characters underscore, $(dollar sign), or a #(hash value).

Cause: The specified JavaScript name included invalid characters.

Action: Specify a JavaScript name that contains only alphanumeric characters and the following special characters: _ $ # and space.
Level: 1

Type: ERROR

Impact: Other

WWV-06202: Javascript name cannot be NULL.

Cause: A name was not specified for the JavaScript.

Action: Specify a name for the JavaScript.
Level: 1

Type: ERROR

Impact: Other

WWV-06203: JavaScript name must not be longer than 30 characters: %1

Cause: The name specified for the JavaScript was too long.

Action: Specify a name for the JavaScript that is no more than 30 characters in length.
Level: 1

Type: ERROR

Impact: Other

WWV-06224: The JavaScript you have specified does not exist.

Cause: The specified JavaScript could not be found.

Action: Specify a valid JavaScript name.
Level: 1

Type: ERROR

Impact: Other

WWV-06241: JavaScript name already exists.

Cause: A JavaScript with the specified name already existed.

Action: Specify a different name for the JavaScript.
Level: 1

Type: ERROR

Impact: Other

WWV-06406: No link is specified.

Cause: An attempt was made to edit a link before a link was selected on the 'Column Formatting' tab.

Action: Select a link from the combo box on the 'Column Formatting' tab.
Level: 1

Type: ERROR

Impact: Other

WWV-06409: failure to save attribute %1: %2

Cause: The attribute was not saved.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-06450: failure to initialize builder attributes: %1

Cause: The design time metadata for this link component could not be fetched.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-06500: Unable to create LOV %1. LOV names must be unique. After creating an LOV, click an edit link to change it.

Cause: An LOV with the specified name already existed.

Action: Specify a different name for the LOV.
Level: 1

Type: ERROR

Impact: Other

WWV-06502: Invalid LOV type. An LOV must be STATIC or DYNAMIC.

Cause: The LOV type was invalid.

Action: Identify the LOV type as either STATIC or DYNAMIC.
Level: 1

Type: ERROR

Impact: Other

WWV-06550: failure to query LOV: %1

Cause: An error occurred as identified in the accompanying Oracle error.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-06551: failure to copy LOV: %1

Cause: An error occurred as identified in the accompanying Oracle error.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-06552: failure to update LOV: %1

Cause: An error occurred as identified in the accompanying Oracle error.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-06553: failure to delete LOV: %1

Cause: An error occurred as identified in the accompanying Oracle error.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-06554: failure to create LOV: %1

Cause: An error occurred as identified in the accompanying Oracle error.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-07002: failure to update menu

Cause: An attempt to update the menu failed.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-07003: failure to delete menu

Cause: An attempt to delete the menu failed.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-07004: failure to delete submenus

Cause: An attempt to delete the submenu failed.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-07005: failure to insert menu

Cause: An attempt to insert the menu failed.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-07200: failure to insert into table wwv_menus for module %1

Cause: An attempt to insert metadata for the menu failed.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-07201: failure to update table wwv_menus for module %1

Cause: An attempt to update the metadata for the menu failed.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-07202: failure to create package %1

Cause: An attempt to compile the package for the menu failed.

Action: Regenerate the component. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-07203: failure to create package body %1

Cause: An attempt to compile the package body for the menu failed.

Action: Regenerate the component. If the error persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-07902: Sorry, page not found.

Cause: The content of the dynamic page could not be found.

Action: Edit the dynamic page to check the query. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-08300: failure to parse as %1 - %2

Cause: The SQL statement could not be parsed due to incorrect syntax or usage, or because it referenced an inaccessible object.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-08301: failure to parse(V7) as %1 - %2

Cause: The SQL statement could not be parsed due to incorrect syntax or usage, or because it referenced an inaccessible object.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-08700: Set preference value failure: %1

Cause: The preference path might have been missing.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-08701: Get preference value failure

Cause: The preference path might have been missing.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-08800: unable to view object: %1

Cause: The database object type was invalid.

Action: Verify that an object of this type exists.
Level: 1

Type: ERROR

Impact: Other

WWV-08801: unable to show synonyms of remote objects: Table=%1 Owner=%2 DB_link=%3

Cause: An attempt was made to view a synonym on a remote table. This action is not supported.

Action: Do not attempt to view a synonym on a remote table.
Level: 1

Type: ERROR

Impact: Other

WWV-08900: failure to initialize attributes

Cause: The design time metadata for this QBE component could not be fetched.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-08901: error in create_package

Cause: The package for the component could not be created. This could be because a package with the same name already existed or there was a problem with the underlying schema.

Action: Verify that the schema exists and a package with the same name exists.
Level: 1

Type: ERROR

Impact: Other

WWV-08902: error in create_package_body

Cause: The package body for the component could not be created. This could be because a package body with the same name already existed, there was a problem with the underlying schema, or the package specification did not exist.

Action: Verify that the schema exists, a package with the same name exists, and the package specification exists.
Level: 1

Type: ERROR

Impact: Other

WWV-08903: error in create_show

Cause: A problem was encountered while building the show procedure of the package.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-08904: error in create_show_parms

Cause: A problem was encountered while building the show_params procedure of the package.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-08905: error in create_help

Cause: A problem was encountered while building the help procedure of the package.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-08906: error in create_help_parms

Cause: A problem was encountered while building the help_params procedure of the package.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-08907: error in create_show_adt

Cause: A problem was encountered while building the show_adt procedure of the package.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-09000: unable to describe object %1 of type %2

Cause: The specified object did not exist or the user did not have sufficient privileges.

Action: Verify that the object exists, and that the user has sufficient privileges on the object.
Level: 1

Type: ERROR

Impact: Other

WWV-09002: unknown type of request %1

Cause: The type was not of Table, View, or Synonym.

Action: Check the type of the object.
Level: 1

Type: ERROR

Impact: Other

WWV-09103: unable to parse cursor and define columns

Cause: The query was improperly written or the user did not have sufficient privileges on the query object.

Action: Check the syntax of the query and the user's privileges on the object.
Level: 1

Type: ERROR

Impact: Other

WWV-09104: unable to fetch row

Cause: The query was improperly written or the user did not have sufficient privileges on the query object.

Action: Check the syntax of the query and the user's privileges on the object.
Level: 1

Type: ERROR

Impact: Other

WWV-09105: unable to locate the row indicated by the ID %1

Cause: The query was improperly written or the user did not have sufficient privileges on the query object.

Action: Check the syntax of the query and the user's privileges on the object.
Level: 1

Type: ERROR

Impact: Other

WWV-09106: failure to insert

Cause: The dynamic SQL statement could not be parsed due to incorrect syntax or usage, or because it referenced an inaccessible object.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-09500: error in parse query %1

Cause: There was an error while parsing the query.

Action: Check the syntax of the query.
Level: 1

Type: ERROR

Impact: Other

WWV-09501: error in fetch column

Cause: There was an error while fetching the column.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-09502: invalid cursor

Cause: There was an error while parsing the query.

Action: Check the syntax, tables, and columns of the query.
Level: 1

Type: ERROR

Impact: Other

WWV-09600: error in parse query %1

Cause: There was an error while parsing the query.

Action: Check the syntax, tables, and columns of the query.
Level: 1

Type: ERROR

Impact: Other

WWV-09601: invalid cursor

Cause: There was an error while parsing the query.

Action: Check the syntax, tables, and columns of the query.
Level: 1

Type: ERROR

Impact: Other

WWV-09700: Error occurred when binding query %1.

Cause: There was an error while binding the query.

Action: Verify that the value of the column is the expected type.
Level: 1

Type: ERROR

Impact: Other

WWV-09701: Error occurred when deleting saved parameters.

Cause: There was an error while deleting the parameters.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-10200: unable to parse query

Cause: The query was improperly written, or the user did not have sufficient privileges on the query object.

Action: Check the query and the user's privileges on the object.
Level: 1

Type: ERROR

Impact: Other

WWV-10201: unable to execute query

Cause: The query was improperly written, or the user did not have sufficient privileges on the query object.

Action: Check the query and the user's privileges on the object.
Level: 1

Type: ERROR

Impact: Other

WWV-10202: unable to perform query

Cause: The query was improperly written, or the user did not have sufficient privileges on the query object.

Action: Check the query and the user's privileges on the object.
Level: 1

Type: ERROR

Impact: Other

WWV-10219: unable to compute column sum for column %0, value %1

Cause: An attempt to calculate the sum of a column failed.

Action: Ensure that the column is numeric.
Level: 1

Type: ERROR

Impact: Other

WWV-10223: unable to fetch column

Cause: An attempt to fetch the column value failed.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-10250: The contents of this link cannot be rendered.

Cause: The specified component did not have mobile support.

Action: Do not add this component to a mobile page.
Level: 1

Type: ERROR

Impact: Other

WWV-10403: %1 failure

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-10601: User %0 has insufficient privileges to grant privileges.

Cause: An attempt was made to grant privileges but the user did not have the appropriate privileges to perform this task.

Action: Log in as a user with privileges to perform this task, or contact the portal administrator and request that the appropriate privileges be granted.
Level: 1

Type: ERROR

Impact: Other

WWV-10602: User %0 has insufficient privileges to revoke privileges.

Cause: An attempt was made to revoke privileges but the user did not have the appropriate privileges to perform this task.

Action: Log in as a user with privileges to perform this task, or contact the portal administrator and request that the appropriate privileges be granted.
Level: 1

Type: ERROR

Impact: Other

WWV-10603: failure to grant privileges

Cause: The user did not have the privileges to perform this action, or the grantee could not be found.

Action: Log in as a user with privileges to perform this action or contact the portal administrator and request that the appropriate privileges be granted. If the user already has the appropriate privileges, verify that the grantee exists.
Level: 1

Type: ERROR

Impact: Other

WWV-10604: failure to revoke privileges

Cause: The user did not have the privileges to perform this action, or the grantee could not be found.

Action: Log in as a user with privileges to perform this action or contact the portal administrator and request that the appropriate privileges be granted. If the user already has the appropriate privileges, verify that the grantee exists.
Level: 1

Type: ERROR

Impact: Other

WWV-10605: User %1 has insufficient privileges to build in Portal DB Provider.

Cause: The user did not have the appropriate privileges to build in the provider.

Action: Log in as a user with sufficient privileges to perform this task, or contact the portal administrator and request that the appropriate privileges be granted.
Level: 1

Type: ERROR

Impact: Other

WWV-10606: User %1 has insufficient privileges to create Portal DB Provider.

Cause: The user did not have the appropriate privileges to create a database provider.

Action: Log in as a user with sufficient privileges to perform this task, or contact the portal administrator and request that the appropriate privileges be granted.
Level: 1

Type: ERROR

Impact: Other

WWV-10607: User %1 has insufficient privileges to Manage Shared Components.

Cause: The user did not have the appropriate privileges to manage shared components.

Action: Log in as a user with sufficient privileges to perform this task, or contact the portal administrator and request that the appropriate privileges be granted.
Level: 1

Type: ERROR

Impact: Other

WWV-10608: User %1 has insufficient privileges to Create Shared Components.

Cause: The user did not have the appropriate privileges to create shared components.

Action: Log in as a user with sufficient privileges to perform this task, or contact the portal administrator and request that the appropriate privileges be granted.
Level: 1

Type: ERROR

Impact: Other

WWV-10703: Insert label usage failure

Cause: An inappropriate value was specified for a label usage ID.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-10704: Insert text block usage failure

Cause: An inappropriate value was specified for a text block usage ID.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-10708: Insert label usage failure

Cause: An inappropriate value was specified for a label usage ID.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-10709: Insert text block usage failure

Cause: An inappropriate value was specified for a text block usage ID.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-11230: %1

Cause: OracleAS Portal encountered the Oracle error identified in the error message.

Action: Refer to the Oracle Error Message Guide for a description of the Oracle error.
Level: 1

Type: ERROR

Impact: Other

WWV-12208: unable to find LOV by NAME or by ID

Cause: The LOV could not be found. The LOV may have been removed.

Action: Verify that the LOV appears in the Navigator. If it does not, re-create it or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-12210: unable to obtain LOV Query: \"%0\"

Cause: The LOV could not be found. The LOV may have been removed.

Action: Verify that the LOV appears in the Navigator. If it does not, re-create it or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-12220: query not found, unable to parse

Cause: The LOV could not be found. The LOV may have been dropped or manually removed from the LOV tables.

Action: If this is a user-defined LOV, verify that it appears in the Navigator. If it is a system LOV, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-12227: You must supply an LOV query, name, cursor, or static values.

Cause: The LOV query, name, cursor, or static values were not specified.

Action: Specify an appropriate value for the LOV.
Level: 1

Type: ERROR

Impact: Other

WWV-12700: insufficient privileges

Cause: The user did not have sufficient privileges to perform this operation.

Action: Log in as a user with privileges to perform this task, or contact the portal administrator and request that the appropriate privileges be granted.
Level: 1

Type: ERROR

Impact: Other

WWV-12701: failure to modify user %1

Cause: The user settings could not be modified.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-12702: failure to create user %1

Cause: An attempt to create a user failed.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-12703: drop user operation failure

Cause: An attempt to drop a user failed.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-12704: failure to drop user %1

Cause: An attempt to drop a user failed.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-12950: Display name must be entered.

Cause: A display name was not specified.

Action: Specify a valid display name.
Level: 1

Type: ERROR

Impact: Other

WWV-12951: Display name is too long: more than %1 bytes.

Cause: The display name was too long.

Action: Specify a shorter display name.
Level: 1

Type: ERROR

Impact: Other

WWV-12952: Component display name must be entered.

Cause: A display name was not specified.

Action: Specify a display name.
Level: 1

Type: ERROR

Impact: Other

WWV-12953: Description must be entered.

Cause: A description was not specified.

Action: Specify a description.
Level: 1

Type: ERROR

Impact: Other

WWV-12954: Description length should not exceed 200 bytes.

Cause: The description was too long.

Action: Specify a description that is no more than 200 bytes.
Level: 1

Type: ERROR

Impact: Other

WWV-12955: Display length should not exceed 200 bytes.

Cause: The title was too long.

Action: Specify a title that is no more than 200 bytes.
Level: 1

Type: ERROR

Impact: Other

WWV-13000: Invalid component name: NULL - Name must be entered

Cause: A name was not specified for the component.

Action: Specify a valid name for the component.
Level: 1

Type: ERROR

Impact: Other

WWV-13001: Invalid component name: %1 - Spaces are not allowed. Select another name.

Cause: The component name contained spaces.

Action: Specify a name for the component that does not contain spaces.
Level: 1

Type: ERROR

Impact: Other

WWV-13002: Invalid component name: %1 - is a reserved word. Select another name.

Cause: The component name included an Oracle reserved word.

Action: Specify a name for the component that does not include any Oracle reserved words.
Level: 1

Type: ERROR

Impact: Other

WWV-13003: Invalid component name: %1 - Name already exists in the schema: %2. Select another name.

Cause: Another component in this database schema already existed with the same name as the one specified.

Action: Specify a different name for the component, or create it in a different schema.
Level: 1

Type: ERROR

Impact: Other

WWV-13004: Invalid SQL statement: %1

Cause: The SQL statement could not be parsed due to incorrect syntax or usage, or reference to inaccessible objects.

Action: Review the SQL statement and make the necessary changes.
Level: 1

Type: ERROR

Impact: Other

WWV-13005: exception

Cause: An attempt to initialize the attributes of the component failed.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-13006: initialization failure for component ID: %1, version %2

Cause: The design time metadata for this component could not be fetched.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-13010: Unable to describe SQL statement. Must be corrected.

Cause: The SQL statement could not be parsed due to incorrect syntax or usage, or reference to inaccessible objects.

Action: Review the SQL statement and make the necessary changes.
Level: 1

Type: ERROR

Impact: Other

WWV-13017: failure to save attribute for: %1

Cause: One or more attributes could not be saved, possibly because they were invalid.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-13018: commit failure

Cause: The design time metadata could not be saved because there were one or more invalid attributes, or because the component was not in an appropriate state.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-13020: This %1 does not exist or you do not have the required privileges.

Cause: The table, view, or synonym could not be found or the table owner did not grant the required privileges to the Portal DB Provider Schema.

Action: Confirm whether the table exists. If it does exist, contact the portal administrator and request that at least the SELECT privilege be granted to the Portal DB Schema on the table, view, or synonym.
Level: 1

Type: ERROR

Impact: Other

WWV-13021: %1 name cannot be null.

Cause: A value was not specified for this field.

Action: Specify a value for this field.
Level: 1

Type: ERROR

Impact: Other

WWV-13022: Duplicate columns are not allowed: %1.

Cause: Duplicate columns were found in the query.

Action: Check for duplicate columns and remove them.
Level: 1

Type: ERROR

Impact: Other

WWV-13023: Invalid columns: At least one column is required.

Cause: The columns names could not be found.

Action: Provide a valid list of columns.
Level: 1

Type: ERROR

Impact: Other

WWV-13024: Invalid object name: %1 - The object you have selected is not available. Select the correct object from the LOV.

Cause: The columns names could not be found.

Action: Provide a valid list of columns.
Level: 1

Type: ERROR

Impact: Other

WWV-13025: Invalid Object Name: %1 - The object you have selected is a synonym and its definition is not present in the DBE_SYNONYMS system view.

Cause: The definition of the specified synonym was not present in the DBE_SYNONYMS system view.

Action: Specify a valid synonym.
Level: 1

Type: ERROR

Impact: Other

WWV-13026: Default Start with Value cannot be null. Enter a valid value depending on the Start with Column selected.

Cause: The default start with value was null.

Action: Specify a valid start with value.
Level: 1

Type: ERROR

Impact: Other

WWV-13027: Display Column Expression cannot be null. Enter a column name or a column expression.

Cause: The display value was null.

Action: Specify a valid display value.
Level: 1

Type: ERROR

Impact: Other

WWV-13028: error in parsing SQL %1

Cause: An attempt to parse the query failed.

Action: Specify a valid query.
Level: 1

Type: ERROR

Impact: Other

WWV-13029: error in parsing PL/SQL %1

Cause: An attempt to parse the query failed.

Action: Specify a valid query.
Level: 1

Type: ERROR

Impact: Other

WWV-13031: Incomplete formatting condition for column %1: Enter a valid condition and select Row/Col to apply the format.

Cause: The formatting condition specified for the column was incomplete.

Action: Specify a valid formatting condition.
Level: 1

Type: ERROR

Impact: Other

WWV-13032: Incomplete formatting condition for Row/Col %1: No formatting condition specified.

Cause: The formatting condition specified for the column was incomplete.

Action: Specify a valid formatting condition.
Level: 1

Type: ERROR

Impact: Other

WWV-13033: Maximum Months Per Page must be an integer in the range 1 to 200.

Cause: The maximum months per page was not in the range of 1 to 200.

Action: Specify a valid value for months for each page.
Level: 1

Type: ERROR

Impact: Other

WWV-13034: Start Month should be less than or equal to End Month.

Cause: The start month was greater than the end month.

Action: Specify a valid start month.
Level: 1

Type: ERROR

Impact: Other

WWV-13036: %1

Cause: The date format was invalid.

Action: Specify a valid date format.
Level: 1

Type: ERROR

Impact: Other

WWV-13037: Invalid join condition. Specify a join condition.

Cause: The join condition was invalid.

Action: Specify a valid join condition.
Level: 1

Type: ERROR

Impact: Other

WWV-13038: Incomplete formatting condition for Cell/Col %1: No formatting condition specified.

Cause: The formatting condition was not specified.

Action: Specify a valid formatting condition.
Level: 1

Type: ERROR

Impact: Other

WWV-13039: Incomplete formatting condition for column %1: Enter a valid condition and select Cell/Col to apply the format.

Cause: The formatting condition was not specified.

Action: Specify a valid formatting condition.
Level: 1

Type: ERROR

Impact: Other

WWV-13040: Incomplete formatting condition for Bar/Col %1: No formatting condition specified.

Cause: The formatting condition was not specified.

Action: Specify a valid formatting condition.
Level: 1

Type: ERROR

Impact: Other

WWV-13041: Incomplete formatting condition for column %1: Enter a valid condition and select Bar/Col to apply the format.

Cause: The formatting condition was not specified.

Action: Specify a valid formatting condition.
Level: 1

Type: ERROR

Impact: Other

WWV-13050: failure to save attribute %1: %2

Cause: One or more attributes could not be saved, possibly because they were invalid.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-13051: failure to commit: %1

Cause: The design time metadata could not be saved because there were one or more invalid attributes, or because the component was not in an appropriate state.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-13053: URL initiation failure

Cause: The server could not be reached.

Action: Verify that the URL is valid and ensure that the proxy settings are correct.
Level: 1

Type: ERROR

Impact: Other

WWV-13054: Either the URL is malformed or the target server could be down.

Cause: The URL could not be reached.

Action: Verify that the URL is valid and ensure that the proxy settings are correct.
Level: 1

Type: ERROR

Impact: Other

WWV-13055: No content was retrieved from the URL OR you have not specified the URL itself.

Cause: The URL did not return any content or the URL was null.

Action: Specify a valid URL.
Level: 1

Type: ERROR

Impact: Other

WWV-13056: unknown exception: %1

Cause: An unhandled exception occurred during this operation.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-13057: HTTPS not supported by UTL_HTTP

Cause: The HTTPS protocol was not supported by this component.

Action: Specify a non-HTTPS URL.
Level: 1

Type: ERROR

Impact: Other

WWV-13058: Content and URL both cannot be null.

Cause: The URL and content were empty.

Action: Either the URL or the content must have a value.
Level: 1

Type: ERROR

Impact: Other

WWV-13059: Content and URL both cannot have values. Entry should be made in only one of them.

Cause: Both the URL and content had values.

Action: Specify a value for the URL or content, not for both.
Level: 1

Type: ERROR

Impact: Other

WWV-13065: The Portal DB Provider provider has been registered. However, execute privilege on the following packages could not be granted to the provider schema. Contact the administrator to get execute privileges for these packages for the provider schema. List of packages: %1

Cause: The package may have been locked by another session for a time sufficient to result into a timeout.

Action: Contact the portal administrator and request that EXECUTE privileges be granted on this package for the provider schema.
Level: 1

Type: ERROR

Impact: Other

WWV-13150: unable to execute function: %1

Cause: An attempt to move from one section to another in a wizard failed. This may have happened while executing the section level pre- and post- functions.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-13300: invalid component ID: %1

Cause: The component ID was invalid.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-13301: unable to retrieve values for component ID: %1

Cause: An attempt to load the component metadata for editing failed. This could be because the metadata had been removed or an inconsistency existed.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-13303: unable to save values for component ID: %1

Cause: An attempt to save the component metadata for editing failed. This could be because there was some inconsistency in the metadata or there was a problem in the underlying database.

Action: Examine the Oracle error. If it cannot be resolved, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-13304: unable to save LONG value for component ID: %1, attribute ID: %2, error: %3

Cause: An attempt to save the component metadata for editing failed. This could be because there was some inconsistency in the metadata or there was a problem in the underlying database.

Action: Examine the Oracle error. If it cannot be resolved, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-13305: unable to create a new version of component ID: %1, version: %2

Cause: An attempt to create a new version of a component failed. This could be because there was already a version with this number, or because there was a problem writing to the database.

Action: Examine the Oracle error. If it cannot be resolved, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-13306: unable to create a new copy of component ID: %1 as component ID: %2

Cause: An attempt to create a copy of a component failed. This could be because there was some problem while writing to the database.

Action: Examine the Oracle error. If it cannot be resolved, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-13307: Attribute %1 is not found in component %2.

Cause: The attribute for the component could not be found.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-13308: Attribute %1 is not found in type %2.

Cause: The attribute for the component could not be found.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-13309: Attribute with ID %1 does not exist.

Cause: The attribute for the component could not be found.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-13400: error creating new component version for component ID: %1

Cause: A new version for the component could not be created.

Action: Check if the component is locked, or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-13401: error creating new component version for component type: %1

Cause: A new version for the component could not be created.

Action: Check if the component is locked, or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-13402: unable to get schema for component ID: %1

Cause: The schema on which the application was built may have been removed.

Action: Re-create the schema. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-13403: unable to get name for component ID: %1

Cause: The component metadata may have been removed inconsistently.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-13404: unable to get component ID for: %1

Cause: The component metadata may have been removed inconsistently.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-13405: unable to get maximum version number for component ID: %1

Cause: The component metadata may have been removed inconsistently.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-13407: unable to get component type for component ID: %1, version %2

Cause: The component metadata may have been removed inconsistently.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-13409: unable to set component name to %1 for component ID: %2

Cause: The component metadata may have been removed inconsistently, or there may have been a problem writing to the database table.

Action: Check the Oracle error or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-13410: unable to set component schema to %1 for component ID: %2

Cause: The component metadata may have been removed inconsistently, or there may have been a problem writing to the database table.

Action: Check the Oracle error or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-13411: unable to get the maximum section number for component type: %1

Cause: The component metadata may have been removed inconsistently.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-13412: failure to initialize attributes for component ID: %1

Cause: The component metadata may have been removed inconsistently.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-13413: failure to save attribute %1, value %2

Cause: The component metadata may have been removed inconsistently, or there may have been a problem writing to the database table.

Action: Check the Oracle error or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-13414: failure to update component status for component ID: %1

Cause: The component metadata may have been removed inconsistently, or there may have been a problem writing to the database table.

Action: Check the Oracle error or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-13415: commit failure

Cause: The component metadata may have been removed inconsistently, or there may have been a problem writing to the database table.

Action: Check the Oracle error or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-13418: failure to insert component: %1

Cause: The component metadata may have been removed inconsistently, or there may have been a problem writing to the database table.

Action: Check the Oracle error or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-13419: failure to update component: %1

Cause: The component metadata may have been removed inconsistently, or there may have been a problem writing to the database table.

Action: Check the Oracle error or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-13420: failure to set Privilege from Portal DB Provider: %1

Cause: An error occurred as identified in the accompanying Oracle error.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-13421: failure to get module information: %1

Cause: An error occurred as identified in the accompanying Oracle error.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-13422: failure to query component: %1

Cause: An error occurred as identified in the accompanying Oracle error.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-13423: error while copying menu as: %1

Cause: An attempt to copy the menu failed.

Action: Verify that the source menu is valid or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-13424: Component %1 does not exist.

Cause: The component could not be found.

Action: Verify that the component exists or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-13426: failure to delete component: %1

Cause: An error occurred as identified in the accompanying Oracle error.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-13427: unable to set component title to %1 for component ID: %2

Cause: The component metadata may have been removed inconsistently, or there may have been a problem writing to the database table.

Action: Check the Oracle error or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-14500: User \"%1\" does not exist.

Cause: The user could not be found.

Action: Verify that the user specified is correct.
Level: 1

Type: ERROR

Impact: Other

WWV-14501: unable to retrieve user ID for user \"%1\"

Cause: A user ID for this user name could not be found, possibly because it was removed.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-14502: unable to execute SQL(%1)

Cause: The user did not have privileges on the table specified in the query, or the table could not be found.

Action: Log in as a user with the appropriate privileges on the table or contact the portal administrator and request that the appropriate privileges be granted. If the problem persists, verify that the table exists.
Level: 1

Type: ERROR

Impact: Other

WWV-14503: unable to execute SQL(%1) as user \"%2\"

Cause: The user did not have privileges on the table specified in the query, or the table could not be found.

Action: Log in as a user with the appropriate privileges on the table or contact the portal administrator and request that the appropriate privileges be granted. If the problem persists, verify that the table exists.
Level: 1

Type: ERROR

Impact: Other

WWV-14600: unable to determine action

Cause: The DML action was invalid.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-14601: error while building insert statement

Cause: An attempt to build the insert statement failed.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-14602: unable to parse statement %1

Cause: An attempt to parse the statement failed.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-14603: unable to handle data type

Cause: One of the data types was not supported.

Action: Specify supported data types.
Level: 1

Type: ERROR

Impact: Other

WWV-14604: error while binding

Cause: An attempt to bind the statement failed.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-14605: unable to insert row

Cause: An attempt to bind the statement failed.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-14606: error while executing insert

Cause: An attempt to execute the INSERT statement failed.

Action: Check the SQL error or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-14607: error while building delete statement

Cause: An attempt to build the delete statement failed.

Action: Contact Oracle Support Services. No rows deleted
Level: 1

Type: ERROR

Impact: Other

WWV-14609: error while executing delete

Cause: An attempt to execute a delete operation failed.

Action: Check the SQL error or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-14610: error while executing update

Cause: An attempt to execute an update operation failed.

Action: Check the SQL error or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-14612: This row was changed by somebody else.

Cause: An attempt to update the row failed.

Action: Refresh the row before updating.
Level: 1

Type: ERROR

Impact: Other

WWV-14613: error while executing select statement

Cause: An attempt to execute the SELECT statement failed.

Action: Check the error displayed or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-14614: unknown error while executing select

Cause: An attempt to execute the SELECT statement failed.

Action: Check the error displayed or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-14617: unexpected error - %1

Cause: An unhandled exception occurred during this operation.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-14618: Error while building %1 statement. Either no new values were entered or no columns could be updated.

Cause: An attempt to build the statement failed.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-14800: failure to parse query %1

Cause: The SQL statement in the error message could not be parsed due to incorrect syntax or usage, or because it referenced an inaccessible object.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-14801: unable to define columns for query %1

Cause: The user did not have privileges on the table specified in the query, or the table could not be found.

Action: Log in as a user with the appropriate privileges on the table or contact the portal administrator and request that the appropriate privileges be granted. If the problem persists, verify that the table exists.
Level: 1

Type: ERROR

Impact: Other

WWV-14802: unable to execute cursor using query %1

Cause: The user did not have privileges on the table specified in the query, or the table could not be found.

Action: Log in as a user with the appropriate privileges on the table or contact the portal administrator and request that the appropriate privileges be granted. If the problem persists, verify that the table exists.
Level: 1

Type: ERROR

Impact: Other

WWV-14803: unable to fetch rows using query %1

Cause: The user did not have privileges on the table specified in the query, or the table could not be found.

Action: Log in as a user with the appropriate privileges on the table or contact the portal administrator and request that the appropriate privileges be granted. If the problem persists, verify that the table exists.
Level: 1

Type: ERROR

Impact: Other

WWV-14901: failure to execute the PL/SQL code after successful submission of the form: %1

Cause: An error occurred as identified in the accompanying Oracle error.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-15000: unable to execute function: %1

Cause: An attempt to execute functions in the component builder failed.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-15100: failure to insert menu %1

Cause: An attempt to insert menu data failed.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-15106: failure to initialize builder attributes

Cause: Design time metadata for the menu component could not be fetched.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-15147: cannot add a menu item with blank name

Cause: A menu item name was not specified.

Action: Specify a valid item name.
Level: 1

Type: ERROR

Impact: Other

WWV-15151: Footer length cannot exceed 2000 characters.

Cause: The footer length was too long.

Action: Specify a footer that is less than 200 characters in length.
Level: 1

Type: ERROR

Impact: Other

WWV-15152: Name length cannot exceed 200 characters.

Cause: The menu item name was too long.

Action: Specify an item name that is less than 200 characters in length.
Level: 1

Type: ERROR

Impact: Other

WWV-15157: cannot change parent

Cause: The specified node was the top-most node, therefore it did not have a parent.

Action: Specify a child node.
Level: 1

Type: ERROR

Impact: Other

WWV-15200: Unexpected error encountered: %1

Cause: An unhandled exception occurred during this operation.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-15201: duplicate attribute name: %1

Cause: The attribute name specified already existed.

Action: Specify a different attribute name.
Level: 1

Type: ERROR

Impact: Other

WWV-15202: User %1 does not have privileges to create a Portal DB Provider.

Cause: The user did not have sufficient privileges to perform this task.

Action: Log in as a user with the appropriate privileges or contact the portal administrator and request that the appropriate privileges be granted.
Level: 1

Type: ERROR

Impact: Other

WWV-15238: failure to set default attributes for component %1

Cause: One or more attributes could not be saved, possibly because they were invalid.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-16062: cannot link to the module: %1

Cause: Target component was not present or was in an INVALID state.

Action: Ensure that the target component is present and is in a VALID state.
Level: 1

Type: ERROR

Impact: Other

WWV-16075: failure to initialize builder attributes: %1

Cause: Design time metadata for the image chart could not be fetched.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-16170: The session identifier specified is not valid for this Portal session.

Cause: The form's session was dropped or the user's login session expired.

Action: If this form requires the user to log in, ensure that the user's login session is active. Also, ensure that the form's session is not dropped by any action performed on the form.
Level: 1

Type: ERROR

Impact: Other

WWV-16409: unable to generate UI form: %1

Cause: The form could not be generated. There may not have been appropriate privileges on the tables used in the form.

Action: If tables are mentioned in the error, contact the portal administrator and request that the appropriate privileges be granted. Alternatively, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-16729: The following object cannot be exported:

Cause: An attempt to export the listed components failed.

Action: Refer to the specific error message for each component.
Level: 1

Type: ERROR

Impact: Other

WWV-16752: The test does not succeed.

Cause: The database object might have been invalid.

Action: Check the status of the database object.
Level: 1

Type: ERROR

Impact: Other

WWV-16753: Unable to connect to the remote database. There may be some error in the user name, password, or the connect string that was used for creating the database link, or the server may not be ready for a connection.

Cause: The user name, password, or connect string used to create the database link may have been incorrect, or the server may not have been ready for a connection.

Action: Verify that the database is up and verify that all connection information is correct.
Level: 1

Type: ERROR

Impact: Other

WWV-16865: The background job (ID= %1) for revoking privileges on Portal packages from the database user %2 fails. Thus, deleting the schema %2 is not possible.

Cause: A database issue could have caused the job to fail.

Action: Contact the database administrator to resolve the database issue that caused the job to fail and then try deleting the schema again.
Level: 1

Type: ERROR

Impact: Other

WWV-16866: The background job (ID= %1) for revoking privileges on Portal packages from the database user %2 is still running. Deleting the schema %2 cannot be done unless the job has completed.

Cause: Background jobs could take a long time to complete if the database was overloaded.

Action: Check the Grant Access page of the schema to see the list of packages on which privileges should be revoked before the schema can be deleted. If, after a while, some packages still exist on which privileges have not been revoked, contact the database administrator and request that the background job be examined further.
Level: 1

Type: ERROR

Impact: Other

WWV-16871: User name cannot be null.

Cause: A user name was not specified.

Action: Specify a valid user name.
Level: 1

Type: ERROR

Impact: Other

WWV-16942: Select another name for the script. The script %1 already exists.

Cause: A script with this name already existed.

Action: Specify a different name for the script.
Level: 1

Type: ERROR

Impact: Other

WWV-16969: The script is empty.

Cause: Content was not specified for the script.

Action: Specify at least one valid SQL statement in the script.
Level: 1

Type: ERROR

Impact: Other

WWV-17001: Argument name: %1: OUT and IN OUT arguments cannot have default values.

Cause: Default values were provided for parameters of types OUT or IN OUT.

Action: Remove the default values for these parameters.
Level: 1

Type: ERROR

Impact: Other

WWV-17002: Invalid argument: %1 cannot contain spaces.

Cause: The value specified contained a blank space. Blank spaces are not valid in this case.

Action: Specify a value that does not contain blank spaces.
Level: 1

Type: ERROR

Impact: Other

WWV-17003: Invalid columns: At least one column is required.

Cause: No columns were specified.

Action: Provide details for at least one column.
Level: 1

Type: ERROR

Impact: Other

WWV-17005: Invalid column %1: Mismatch between data type and default value.

Cause: The default value and the column were different data types.

Action: Ensure that the data types match.
Level: 1

Type: ERROR

Impact: Other

WWV-17007: rename failure

Cause: The database object may have been invalid.

Action: Check the status of the database object.
Level: 1

Type: ERROR

Impact: Other

WWV-17009: duplicate columns not allowed: %1

Cause: Multiple columns with the same name were found.

Action: Change the name of the columns so that each column has a distinct name.
Level: 1

Type: ERROR

Impact: Other

WWV-17021: Failure to grant the %1 privilege. To grant a privilege on a view, the user should have that privilege on all underlying objects of the view.

Cause: The user did not have privileges for all the objects referenced in the view.

Action: Log in as a user with the appropriate privileges or contact the portal administrator and request that the appropriate privileges be granted.
Level: 1

Type: ERROR

Impact: Other

WWV-17024: No columns selected. Select at least one column.

Cause: No columns were selected for the component.

Action: Select at least one column.
Level: 1

Type: ERROR

Impact: Other

WWV-17027: Duplicate constraints are not allowed: %1 is already used for specifying a constraint.

Cause: A constraint with the same name already existed.

Action: Specify a different name for the constraint.
Level: 1

Type: ERROR

Impact: Other

WWV-17043: unable to disable trigger %1

Cause: An attempt to disable a trigger failed. The user did not have the appropriate privileges, or the trigger may have been dropped during this operation.

Action: Log in as a user with the appropriate privileges or contact the portal administrator and request that the appropriate privileges be granted. If the problem persists, verify that the trigger exists.
Level: 1

Type: ERROR

Impact: Other

WWV-17044: unable to drop trigger %1

Cause: An attempt to drop a trigger failed. The user did not have the appropriate privileges, or the trigger may have been dropped during this operation.

Action: Log in as a user with the appropriate privileges or contact the portal administrator and request that the appropriate privileges be granted. If the problem persists, verify that the trigger exists.
Level: 1

Type: ERROR

Impact: Other

WWV-17046: Selected schema %1 does not exist or insufficient privilege to access it.

Cause: An attempt to select a schema failed. The schema did not exist or the user did not have the appropriate privileges to access it.

Action: Log in as a user with the appropriate privileges or contact the system administrator and request that the appropriate privileges be granted. If the problem persists, verify that the schema exists.
Level: 1

Type: ERROR

Impact: Other

WWV-17063: Select at least one table from the list of tables.

Cause: A table was not specified.

Action: Select a table or specify a valid table name.
Level: 1

Type: ERROR

Impact: Other

WWV-17077: Precision value for a numeric column must be in the range of -84 and 127.

Cause: The precision specified for the numeric column was invalid.

Action: Specify a valid precision for the numeric column.
Level: 1

Type: ERROR

Impact: Other

WWV-17078: A constraint name is required.

Cause: A name was not specified for the constraint.

Action: Specify a name for the constraint.
Level: 1

Type: ERROR

Impact: Other

WWV-17081: %1 length should not exceed %2 bytes.

Cause: The value specified was too long.

Action: Specify a shorter value.
Level: 1

Type: ERROR

Impact: Other

WWV-17082: %1 contains invalid characters. Cannot have the following characters in any name: `-=[];',./\~!@%^&*()+{}|:\"<>?

Cause: The specified name included invalid characters.

Action: Specify a name that does not contain the characters listed in the error message.
Level: 1

Type: ERROR

Impact: Other

WWV-17083: Cannot edit index (%1) used for enforcement of unique or primary key. Change the integrity constraints instead of editing the index.

Cause: An attempt was made to edit an index from a unique or primary key.

Action: Change the integrity constraints from the table instead of the unique or primary key.
Level: 1

Type: ERROR

Impact: Other

WWV-17085: Either the object %1 does not exist, or %1 is not a table or view, or the schema %2 does not have privilege on %1.

Cause: The object did not exist, it was not a table or view, or the schema did not have the appropriate privileges on it.

Action: Ensure that the object is a table or view and that the schema has appropriate privileges on it.
Level: 1

Type: ERROR

Impact: Other

WWV-17086: Column %1 is of type %2. Column of data type CLOB, BLOB, NCLOB, BFILE, LONG, LONG RAW, UROWID or Multimedia Object types(ORDSYS.ORDIMAGE, ORDSYS.ORDAUDIO, ORDSYS.ORDVIEW) cannot be a primary, unique, or foreign key.

Cause: The data type specified for the primary, unique, or foreign key column was not appropriate.

Action: Refer to the SQL documentation for a list of data types that are not allowed to be part of a primary, unique, or foreign key.
Level: 1

Type: ERROR

Impact: Other

WWV-17088: Column %1 is of data type %2. Maximum length is %3 and minimum is %4.

Cause: An invalid value was specified for the column length.

Action: Specify a value within the maximum and minimum values shown in the error message.
Level: 1

Type: ERROR

Impact: Other

WWV-17090: Default value's length exceeds the column length for column %1.

Cause: The value specified as the default column value was larger than the column could hold.

Action: Specify a value that fits in the column.
Level: 1

Type: ERROR

Impact: Other

WWV-17091: Invalid name: %1. A name cannot start with any of the following characters: `1234567890-=[]\;',./~!@#$%^&*()_+{}|:\"<>?

Cause: The name specified started with an invalid character.

Action: Specify a valid name and ensure that it does not start with any of the characters mentioned in the error message.
Level: 1

Type: ERROR

Impact: Other

WWV-17104: File name cannot be null.

Cause: A file name was not specified.

Action: Specify a valid file name.
Level: 1

Type: ERROR

Impact: Other

WWV-17106: Invalid file extension. Permissible extensions are .java for Java Source, .class for Java Class and .jar for Java Resource.

Cause: The extension of the file specified was not appropriate.

Action: Specify a .java, .class, or .jar file.
Level: 1

Type: ERROR

Impact: Other

WWV-17107: File does not exist or the file is empty.

Cause: The file specified did not exist or was empty.

Action: Specify a valid file name.
Level: 1

Type: ERROR

Impact: Other

WWV-17128: The constraint has not been added to the list. Click the Add-to-List button to do this.

Cause: The constraint was not added to the table.

Action: Click the Add to List button to add the constraint to the table.
Level: 1

Type: ERROR

Impact: Other

WWV-17129: Column %1 cannot be null because it is the primary key.

Cause: A value was not specified for the primary key.

Action: Specify a value for the primary key.
Level: 1

Type: ERROR

Impact: Other

WWV-17135: The database link was created successfully, however, connection to the remote database using the link %1 cannot be established.

Cause: The remote database or listener could be down, or the connect information supplied might have been incorrect.

Action: Verify the connect information. If the problem persists, ensure that the remote database and listener are up and running.
Level: 1

Type: ERROR

Impact: Other

WWV-17139: Either the column conditions are not specified properly or the specified where clause is invalid.

Cause: An incorrect condition or an invalid clause was specified.

Action: Review the column condition or clause and make appropriate changes.
Level: 1

Type: ERROR

Impact: Other

WWV-17141: Invalid name: %1. Cannot use spaces in the name.

Cause: The name specified contained a space.

Action: Specify a name that does not contain spaces.
Level: 1

Type: ERROR

Impact: Other

WWV-17245: create schema failure

Cause: A schema with the same name already existed or the user did not have sufficient privileges to create a schema.

Action: Specify a different, unique name for the schema. If the problem persists, contact the portal administrator and request that the appropriate privileges be granted.
Level: 1

Type: ERROR

Impact: Other

WWV-17246: update schema failure

Cause: A schema with the same name already existed or the user did not have sufficient privileges to update a schema.

Action: Specify a different, unique name for the schema. If the problem persists, contact the portal administrator and request that the appropriate privileges be granted.
Level: 1

Type: ERROR

Impact: Other

WWV-17293: GRANT ROLE action failure

Cause: The user did not have sufficient privileges to perform the GRANT ROLE action.

Action: Log in as a user with the appropriate privileges or contact the portal administrator and request that the appropriate privileges be granted.
Level: 1

Type: ERROR

Impact: Other

WWV-17294: REVOKE ROLE action failure

Cause: The user did not have sufficient privileges to perform the REVOKE ROLE action.

Action: Log in as a user with the appropriate privileges or contact the portal administrator and request that the appropriate privileges be granted.
Level: 1

Type: ERROR

Impact: Other

WWV-17298: failure to grant role %1

Cause: The user did not have sufficient privileges to perform the GRANT ROLE action.

Action: Log in as a user with the appropriate privileges or contact the portal administrator and request that the appropriate privileges be granted.
Level: 1

Type: ERROR

Impact: Other

WWV-17299: failure to revoke role %1

Cause: The user did not have sufficient privilege to perform the REVOKE ROLE action.

Action: Log in as a user with the appropriate privileges or contact the portal administrator and request that the appropriate privileges be granted.
Level: 1

Type: ERROR

Impact: Other

WWV-17300: cannot create role %1

Cause: An attempt to create a role failed, possibly because the user did not have the appropriate privileges.

Action: Log in as a user with the appropriate privileges or contact the portal administrator and request that the appropriate privileges be granted.
Level: 1

Type: ERROR

Impact: Other

WWV-17302: Schema or Password or Confirm Password does not follow Oracle naming conventions or is a reserved word.

Cause: The values specified for the fields did not conform to the rules for naming schema objects.

Action: Specify correct values for these fields. Refer to the SQL Reference for assistance.
Level: 1

Type: ERROR

Impact: Other

WWV-17310: Password or Confirm Password is null.

Cause: A value was not specified for the Password field or Confirm Password field.

Action: Specify the same value for the Password and the Confirm Password fields.
Level: 1

Type: ERROR

Impact: Other

WWV-17453: unable to terminate the session

Cause: Either the user did not have the appropriate privileges to terminate the session, or the session may have been terminated by another user.

Action: Verify that the session still exists. If it does, contact the portal administrator and request that the appropriate privileges be granted.
Level: 1

Type: ERROR

Impact: Other

WWV-17700: failure to query data component: %1

Cause: An error occurred as identified in the accompanying Oracle error.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-17701: failure to copy data component: %1

Cause: An error occurred as identified in the accompanying Oracle error.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-17702: failure to update data component: %1

Cause: An error occurred as identified in the accompanying Oracle error.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-17703: failure to delete data component: %1

Cause: An error occurred as identified in the accompanying Oracle error.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-17704: failure to create data component: %1

Cause: An error occurred as identified in the accompanying Oracle error.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-17717: Set default columns failure

Cause: One or more attributes were not saved, possibly because they were invalid.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-17719: unable to save value for attribute ID: %1 for value: %2

Cause: An attempt to save the component metadata failed.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-61269: failure to save parameters

Cause: An error occurred in the user preference storage subsystem.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WWV-61294: failure to initialize builder attributes

Cause: Design time metadata could not be fetched.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

107 WXE-00010 to WXE-21271

WXE-00010: %s

Cause: Internal error raised.

Action: No action required.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-00800: Auto-Restart started successfully

Cause: The Auto-Restart process has successfully completed its initialization.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-08000: Internal error. Auto-Restart process terminating.

Cause: An internal error occurred in the Auto-Restart process.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. This error usually occurs as a result of insufficient system resources. If the problem persists, contact Oracle Support.
Level: 1

Type: ERROR

Impact: Process

WXE-08001: Failed to start the cache server. Auto-Restart process terminating.

Cause: Failed to start the Oracle Web Cache server.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. This error usually occurs as a result of insufficient system resources. If the problem persists, contact Oracle Support.
Level: 1

Type: ERROR

Impact: Process

WXE-08002: Failed to find an Oracle Web Cache listening port that does not require SSL client-side certificates. Auto-Restart pinging is disabled.

Cause: Auto-Restart does not support the use of client-side certificates. If all Oracle Web Cache listening ports require client-side certificates, then pinging is disabled in the Auto-Restart mechanism.

Action: To enable pinging, add a listening port that does not require client-side certificates.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-08500: Cache server not responding on port %d.

Cause: The cache server may not have been running. The Auto-Restart process will continue to try to reach the cache server on the specified port.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-08501: Timeout occurred communicating with the cache server.

Cause: The cache server was either in an unstable state or slow responding to queries.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. From the Auto-Restart page of Oracle Enterprise Manager or Oracle Web Cache Manager, check the ping timeout interval and increase it if necessary.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-08502: Lost connection with the cache server.

Cause: There were communication errors between the Auto-Restart process and the cache server. The Auto-Restart process will continue to try to reach the cache server.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-08503: Operating system level error in %s() (%d): %s.

Cause: The specified system call returned the specified error.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 16

Type: ERROR

Impact: Operating System

WXE-08504: %u consecutive errors pinging the cache server.

Cause: The Auto-Restart process received the specified number of failures when attempting to reach the cache server.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-08505: %u consecutive error(s) pinging the cache server. %d error(s) required for restart.

Cause: The Auto-Restart process received the specified number of failures when attempting to reach the cache server. The error message indicates the number of times the Auto-Restart process will attempt to reach the cache server.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-08506: Unable to retrieve the cache server process ID from %s. Stopping the Auto-Restart process.

Cause: Unable to read the Oracle Web Cache server pid file. Most likely the file was deleted during a normal termination of the server. As a result, the Auto-Restart process was also shut down.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-08507: Cache server process not running.

Cause: There was no process on the system matching the process ID listed in the Oracle Web Cache server pid file.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 1

Type: NOTIFICATION

Impact: Process

WXE-08508: Restarting the cache server.

Cause: See accompanying error messages for more information.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 1

Type: ERROR

Impact: Process

WXE-08509: Starting the cache server.

Cause: See accompanying error messages for more information.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 1

Type: ERROR

Impact: Process

WXE-08510: SSL set hardware acceleration failed. NZE-%d.

Cause: The SSL library failed to initialize the hardware SSL acceleration. The specified error message provides more detail.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. See the "Network Security Messages (NZE)" chapter of the Oracle Database Error Messages for information about NZE errors.
Level: 16

Type: ERROR

Impact: Security

WXE-08511: SSL Set Thread Usage Failed. NZE-%d.

Cause: The SSL library failed to set the threading model. The specified error message provides more detail.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. See the "Network Security Messages (NZE)" chapter of the Oracle Database Error Messages for information about NZE errors.
Level: 16

Type: ERROR

Impact: Security

WXE-08512: SSL Engine Failed to Initialize. NZE-%d.

Cause: The SSL engine failed to initialize. The specified error message provides more detail.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. See the "Network Security Messages (NZE)" chapter of the Oracle Database Error Messages for information about NZE errors.
Level: 16

Type: ERROR

Impact: Security

WXE-08513: Cache server process ID %u is starting up.

Cause: The cache server is starting up.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Process

WXE-08514: Cache server process ID %u is shutting down.

Cause: The cache server is shutting down.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Process

WXE-08515: Event log message %d (%s) referenced %d time(s)

Cause: Occurrence frequency of various event_log message

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Logging

WXE-08516: Event log index %d contains %d node(s)

Cause: Occurrence frequency of various event_log message

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Logging

WXE-09000: Oracle Web Cache process of ID %d exits with code %d at line %d of file %s [label: %s]

Cause: The Oracle Web Cache process shutdown.

Action: No action required.
Level: 1

Type: ERROR

Impact: Process

WXE-09001: An error occurred while disabling core file creation.

Cause: Internal error. The system/library call to disable core file creation returned an error.

Action: If the problem persists, contact Oracle Support.
Level: 1

Type: WARNING

Impact: Logging

WXE-09003: File %.*s open failed; using %.*s instead

Cause: The attempt to open the specified file failed. Oracle Web Cache opened the new file instead.

Action: No action required.
Level: 1

Type: WARNING

Impact: Logging

WXE-09200: An error occurred while trying to create a background process.

Cause: Could not open standard input while Oracle Web Cache is creating a process.

Action: Determine why Oracle Web Cache cannot read standard input or write to standard output for null device.
Level: 1

Type: ERROR

Impact: Process

WXE-09401: %s[%d].%s: %s

Cause: Statistics information dumped to event log on server shutdown

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09402: %s[%d].%s: %ld

Cause: Statistics information dumped to event log on server shutdown

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09403: Maximum number of file/socket descriptors set to %s.

Cause: The specified number of file descriptors is set for use by Oracle Web Cache.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09404: DMS metadata load starting

Cause: Loading DMS metadata information

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09405: DMS metadata load complete

Cause: Loading DMS metadata information

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09411: DMS shutdown starting

Cause: Loading DMS metadata information

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09412: DMS shutdown complete

Cause: Loading DMS metadata information

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09418: DMS disabled

Cause: Loading DMS metadata information

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09420: Error accessing the Oracle Dynamic Monitoring Service library, %s: %s

Cause: An error occurred when attempting to open or access functions in the Oracle Dynamic Monitoring Service (DMS) library. See the operating system level error message included in this message. The error message provides further details, such as "file not found" or function not available".

Action: This message is no longer used as of Oracle Fusion Middleware 11g. If the problem persists, contact Oracle Support.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09421: Unable to open the Oracle Dynamic Monitoring Service library, %s:%s. Searching the library path.

Cause: An error occurred when attempting to open the Oracle Dynamic Monitoring Service (DMS) library. See the operating system level error message included in this message. The error message provides further details, such as "file not found". Oracle Web Cache will search the library path. If the library is still not / found, then Oracle Web Cache returns event message 09420. NOTE: DMS statistics collection has been disabled until the problem is resolved.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. If the problem persists, contact Oracle Support.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-09422: Error accessing %s in the Oracle Dynamic Monitoring Service library, %s: %s

Cause: An error occurred when attempting to open or access functions in the Oracle Dynamic Monitoring Service (DMS) library. See the operating system level error message included in this message. The error message provides further details, such as "file not found" or function not available".

Action: This message is no longer used as of Oracle Fusion Middleware 11g. If the problem persists, contact Oracle Support.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09424: The statistics persistent repository is disabled

Cause: The statistics persistent repository has been disabled by the user in the webcache.xml configuration file.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09425: The %s file is no longer valid

Cause: The wcstatsrepos.xml file has been modified since the cache was started. The contents and/or changes are ignored.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09426: The %s statistics persistent repository does not exist

Cause: The wcstatsrepos.xml file statistics persistent repository does not exist; this may be the first time the repository has been accessed.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09427: Failure during file move of %s. Statistics persistent repository is abandoned

Cause: File move or rename failed.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09428: An error occurs during statistics repository download. The file %s has been corrupted or moved.

Cause: The "wcstatsrepos.xml" file was corrupted or moved during the shutdown operation.

Action: Recover "wcstatsrepos.xml" by copying from "wcstatsrepos.bak".
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09429: Failed to open the %s file. Statistics persistent repository is abandoned

Cause: Failed to open the "wcstatsrepos.tmp" temporary file.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09430: Failure creating the %s file. Statistics persistent repository is abandoned

Cause: Failed to write to or close the "wcstatsrepos.tmp" temporary file.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09431: The statistics persistent repository is being reset by new version

Cause: The statistics persistent repository has been invalidated by the installation of a new Oracle Web Cache software version

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09432: Starting statistics persistent repository checkpoint operation

Cause: The statistics persistent repository is being checkpointed.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09433: Completed statistics persistent repository checkpoint operation

Cause: The statistics persistent repository is being checkpointed.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09438: The statistics persistent repository is being reset by new configuration

Cause: The statistics persistent repository has been invalidated by a change to the Oracle Web Cache configuration file (webcache.xml)

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09440: The statistics persistent repository is disabled by event

Cause: The statistics persistent repository has been disabled because the "last" event is marked as "VALID=NO".

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09441: DMS enabled

Cause: Loading DMS metadata information

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09442: Unable to resolve APIs in the Oracle Dynamic Monitoring Service library, %s:%s

Cause: An error occurred when attempting to resolve public APIs in the Oracle Dynamic Monitoring Service (DMS) library.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. If the problem persists, contact Oracle Support.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09443: All APIs in the Oracle Dynamic Monitoring Service library have been resolved

Cause: All external APIs have been identified and properly resolved.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09444: The statistics persistent repository cannot be processed: %d

Cause: The statistics persistent repository has been determined to not match the current statistics configuration.

Action: No action required. The statistics repository will be rebuilt automatically at the next specified checkpoint interval or when the webcache server shuts down.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09445: Dynamic Metric Services allocating excessive memory block:%d

Cause: The Dynamic Metric Services (DMS) is allocating a memory buffer that is potentially too large.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-09446: Statistics initialization commencing.

Cause: The statistics information initialization operation is beginning.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-09447: Statistics initialization complete.

Cause: The statistics information initialization operation is complete.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-09521: Oracle Web Cache fails to find user ( %s ) in /etc/passwd.

Cause: The specified user was not found in the password file.

Action: Add user to the password file.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09522: Oracle Web Cache fails to find group ( %s ) in /etc/group.

Cause: The specified group was not found in the group file.

Action: Add the group to the group file or modify the group ID in the Security page of Fusion Middleware Control.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09523: Invalid user ID ( %s ).

Cause: The specified user ID was invalid.

Action: Correct the user ID in the Security page of Fusion Middleware Control.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09524: Invalid group ID ( %s )

Cause: The specified group ID was invalid.

Action: Correct the group ID in the Security page of Fusion Middleware Control.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09525: Permission denied when setting user ID ( %s ).

Cause: The specified user did not have the required permissions when setting the user ID.

Action: Grant the user required permissions or log in as a different user.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09526: Permission denied when setting group ID ( %s ).

Cause: The user did not have the required permissions when setting group ID.

Action: Grant the user required permissions or log in as a different user.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09534: Unexpected File I/O Error ( %s ) when opening file %s.

Cause: Could not open specified file.

Action: Review specified error to determine the problem on your system.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09570: Directory not found when unlinking file %s

Cause: The directory was not found.

Action: Verify that Oracle Web Cache was installed properly. You may need to reinstall Oracle Web Cache.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09571: Too many files open when unlinking file %s.

Cause: Too many files were open for available system resources.

Action: Adjust system resources and restart Oracle Web Cache.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09572: No disk space available when unlinking file %s

Cause: Insufficient disk space was available on the system.

Action: The system is running low on disk space. Free up disk space and restart Oracle Web Cache.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09573: Unexpected File I/O Error ( %s ) when unlinking file %s.

Cause: There was an unexpected input/output file error.

Action: Review the specified error and correct the problem on the system.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09574: Permission denied when unlinking file %s.

Cause: Permission denied on file.

Action: Set correct permission on the specified file.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09600: SIGTERM caught - program will shut down once all connections are complete.

Cause: Normal notification behavior. Shutdown event written to the log file.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09601: SIGUSR1 caught - program will reread configuration files after all connections are complete.

Cause: Normal notification behavior. Configuration file reread event written to the log file.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09602: All configuration files have been reread.

Cause: Normal notification behavior. All configuration files have been reread and this configuration reload event written to the log file.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

WXE-09603: There was an error rereading the configuration files. The program is exiting.

Cause: Invalid Oracle Web Cache configuration files.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Correct the Oracle Web Cache configuration files and restart Oracle Web Cache.
Level: 1

Type: ERROR

Impact: Configuration

WXE-09604: Could not increase the number of file/socket descriptors to %s.

Cause: Ran out of file descriptors on the system.

Action: Decrease the Maximum Incoming Connections value in the Resource Limits of Fusion Middleware Control, or increase the system file descriptors. Run Oracle Web Cache as the root user.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09605: Cannot create OPMN shutdown thread. Continuing with startup.

Cause: Oracle Web Cache could not create OPMN shutdown thread.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Use OPMN to abort the Oracle Web Cache process during Oracle Web Cache shutdown.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09606: Cannot create OPMN shutdown event. Continuing with startup.

Cause: Oracle Web Cache could not create OPMN shutdown event.

Action: Use OPMN to abort the Oracle Web Cache process during Oracle Web Cache shutdown.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09607: The admin server started successfully.

Cause: The Oracle Web Cache admin server process started successfully.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 1

Type: NOTIFICATION

Impact: Process

WXE-09608: The cache server process started successfully.

Cause: The Oracle Web Cache server process has started successfully.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Process

WXE-09609: The server process could not initialize.

Cause: The Oracle Web Cache configuration is invalid.

Action: Review the error log file or use the Event Viewer to help determine the cause of the problem.
Level: 1

Type: ERROR

Impact: Process

WXE-09610: The server is exiting.

Cause: The cache server or admin server process is terminating.

Action: Review the error log file or use the Event Viewer to help determine the cause of the problem.
Level: 1

Type: NOTIFICATION

Impact: Process

WXE-09611: The server could not start the service thread.

Cause: The server process could not start the Service thread.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Determine why Oracle Web Cache cannot start a thread on your system.
Level: 1

Type: ERROR

Impact: Threads

WXE-09612: Oracle Web Cache %s, %s

Cause: Normal notification behavior. The Oracle Web Cache version number was written to the log file.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09614: The following Oracle Web Cache internal files are pre-populated to the cache: [[ %s ]]

Cause: The specified Oracle Web Cache internal files are loaded into the cache.

Action: No required action.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09615: SMALLDOCBUFFERSIZE larger than DOCBUFFERSIZE. Setting SMALLDOCBUFFERSIZE=%s

Cause: Invalid Oracle Web Cache configuration. The SMALLDOCBUFFERSIZE is larger than DOCBUFFERSIZE.

Action: Review your configuration. Oracle Web Cache will override your current configuration for SMALLDOCBUFFERSIZE.
Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-09616: The Oracle Web Cache is running in the routing only mode.

Cause: The Oracle Web Cache is running in the routing only mode.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09700: Unable to initialize NLS. Error %d

Cause: Internal error. A system/library call has unexpectedly failed.

Action: If the problem persists, contact Oracle Support.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09701: Unable to initialize NLS global structure.

Cause: Internal error. A system/library call has unexpectedly failed.

Action: If the problem persists, contact Oracle Support.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09702: NLS boot file not found or missing; using default.

Cause: Internal error. A system/library call has unexpectedly failed.

Action: If the problem persists, contact Oracle Support.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-09703: Stop Issued. The program will shut down after all accepted requests are served, or a timeout occurs.

Cause: Stop was issued.

Action: Oracle Web Cache will be stopped.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09704: Abort Issued. The program will shut down immediately.

Cause: Abort was issued.

Action: Oracle Web Cache will be stopped immediately.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09705: Error accessing the Oracle Notification Service library, %s: %s

Cause: An error occurred when attempting to open or access functions in the Oracle Notification Service (ONS) library. See the operating system level error message included in this message. The error message provides further details, such as "file not found" or function not available".

Action: This message is no longer used as of Oracle Fusion Middleware 11g. If the problem persists, contact Oracle Support.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09706: Ignoring unrecognized option: %s

Cause: An alert was logged.

Action: Refer to the logged alert details and take the appropriate action.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09707: Failed to start the server.

Cause: Failed to start the Oracle Web Cache server. This error usually occurs as a result of insufficient system resources or invalid configuration.

Action: If the problem persists, contact Oracle Support.
Level: 1

Type: ERROR

Impact: Process

WXE-09708: Failed to initialize DNS

Cause: Failed to initialize DNS.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. If the problem persists, contact Oracle Support.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09709: Failed to initialize the HTTP component

Cause: Failed to initialize HTTP.

Action: If the problem persists, contact Oracle Support.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09710: Cache server failed to initialize.

Cause: Insufficient system resources or invalid Oracle Web Cache configuration.

Action: Review the error log file or use the Event Viewer to help determine the cause of the problem.
Level: 1

Type: ERROR

Impact: Process

WXE-09711: Problem loading message file for event log. Exiting.

Cause: Message file for event log was not correctly loaded.

Action: Check the existence and permissions of the file wxeus.msb in $ORACLE_HOME/webcache/mesg/wxeus.msb on UNIX and ORACLE_HOME\\webcache\\mesg on Windows.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09712: Unable to open the Oracle Notification Service library, %s:%s. Searching the library path.

Cause: An error occurred when attempting to open the Oracle Notification Service (ONS) library. See the operating system level error message included in this message. The error message provides further details, such as "file not found". Oracle Web Cache will search the library path. If the library is still not / found, then Oracle Web Cache returns event message 09705.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. If the problem persists, contact Oracle Support.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-09716: LDMInit Error %d

Cause: LDM library cannot be initialized

Action: Check the error number
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09717: LDMOpen Error %d

Cause: LDM repository cannot be opened

Action: Check the error number
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09718: eOns component already initialized; continuing...

Cause: The eOns component could not be initialized directly by the Oracle Web Cache server because eOns has already been previously initialized. The Oracle Web Cache server will continue to startup.

Action: No action required.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-09719: Initializing eOns component using port %s.

Cause: The eOns component is being initialized with the identified port number

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09720: req-info

Cause: Logging request information to the event_log.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09721: Cluster initialization failure.

Cause: Cluster initialization fails.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09722: Could not create specified access_log file.

Cause: The access_log was unable to be created.

Action: If the problem persists, contact Oracle Support.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09723: Could not establish effective user identification.

Cause: Could not establish the effective user identification. This may indicate an improper installation.

Action: If the problem persists, contact Oracle Support.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09732: Oracle Instance configuration directory is not available.

Cause: One of the these environment variables, ORACLE_INSTANCE, COMPONENT_TYPE, or COMPONENT_NAME, is not defined.

Action: If the problem persists, contact Oracle Support.
Level: 1

Type: ERROR

Impact: Configuration

WXE-09733: The configuration file webcache.xml cannot be found.

Cause: The Oracle Web Cache instance may not be provisioned correctly or the file system is full.

Action: If the problem persists, contact Oracle Support.
Level: 1

Type: ERROR

Impact: Configuration

WXE-09807: Statistics query fatal error: %.*s

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-09811: Unknown value type:%d

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09812: Unknown instruction value type:%d

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09813: Bad operator in stack:%d

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09814: Unknown variable value type:%d

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09815: Unknown variable type:%d

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09816: Invalid register index

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09817: Invalid address value type

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09818: Incompatible operands

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09819: Unknown value type

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09820: Invalid addition operand type

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09821: Invalid subtraction operand type

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09822: Invalid less-than operand type

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09823: Invalid less-than-equal operand type

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09824: Invalid greater-than operand type

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09825: Invalid greater-than-equal operand type

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09826: Invalid multiply operand type

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09827: Invalid division operand type

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09828: Division by zero exception

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09829: Invalid modulo operand type

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09830: Invalid shift-left operand type

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09831: Invalid shift-right operand type

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09832: Invalid bitwise-AND operand type

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09833: Invalid exclusive-OR operand type

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09834: Invalid inclusive-OR operand type

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09835: Invalid function index type

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09836: Invalid instruction:%d

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09837: Stack overflow

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09838: Bad expression

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09839: Assignment needs an lvalue

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09840: Missing an operand

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09841: Assignment needs an lvalue

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09842: Missing expression ')'

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09843: Missing function '('

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09844: Missing function ')'

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09845: Unexpected character in input: '%c'

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09846: Too many variables

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09847: Unterminated string

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09848: Unterminated string

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09849: Unknown column number (only %d columns available)

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09850: Builtin function %s() argument type mismatch

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09851: Invalid logical-OR operand type

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09852: Expression already compiled

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09853: Expression not yet compiled

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09854: Invalid logical-AND operand type

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09855: Unknown statistics group member %.*s

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09856: Invalid ones-complement operand type

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09857: Invalid negation operand type

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09858: Invalid regular expression: %.*s

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09859: Expression context has not been initialized

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09860: Incorrect function argument separator usage

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09861: Invalid register name: '%c'

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09862: Expression too complex

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09863: Invalid row %d specified when %d rows exist; no value obtained

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09864: Query operation not yet implemented or supported: %s

Cause: The statistics query failed for the specified reason.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-10054: Unable to resume service, UIPI return value is %s.

Cause: Service could not be resumed.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Review the error to determine the problem on your system.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-10417: MIME Type Extension ( %s ) exceeds current size limit.

Cause: Unexpected MIME type configured.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-10418: Encoding Extension ( %s ) exceeds current size limit.

Cause: Unexpected encoding type configured.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-10419: Language Extension ( %s ) exceeds current size limit.

Cause: Unexpected language type configured.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-10536: You must specify a full path for %s. See %s %s.

Cause: Failed to specify full path name.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Specify a full path name for the file.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-10555: Bad integer value ( %s ). See %s %s.

Cause: Invalid drive letter.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Contact Oracle Support.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-10599: Unexpected error

Cause: Unexpected internal error.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Contact Oracle Support.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11057: Dynamic origin server capacity is reduced to %d.

Cause: Oracle Web Cache ran out of file descriptors on the computer.

Action: Increase the file descriptor limit. See the Oracle Fusion Middleware Secure Proxy Caching and Load Balancing Guide for Oracle Web Cache.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11058: Stale object updated for %.*s%.*s

Cause: The complete response was successfully received and the cache entry is updated with the new response.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11059: Garbage object updated for %.*s%.*s

Cause: The complete response was successfully received and the cache entry is updated with the new response.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11060: Object update aborted.

Cause: The response will not be used to update the stale or garbage object in the cache because it was determined that it is not cacheable.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11062: <!-- WEBCACHETAG--> and <!-- WEBCACHEEND--> tag parsing error

Cause: The syntax for the <!-- WEBCACHETAG--> and <!-- WEBCACHEEND--> tags was incorrect.

Action: Correct the syntax of the <!-- WEBCACHETAG--> and <!-- WEBCACHEEND--> tags in the source.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11064: ESI object %.*s%.*s parsing error

Cause: Object contained invalid ESI syntax.

Action: Correct the ESI syntax in the source.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11076: Cluster member %s - %s sent invalid configuration error

Cause: The cache cluster member sent a response to Oracle Web Cache that indicates it has a configuration file different than the local configuration file for the cache cluster. A cluster runtime operates with the same webcache.xml configuration file for all members.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Compare the two configuration files, and then propagate the proper version to all cluster members.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11077: Cluster member sent invalid configuration error

Cause: The cache cluster member sent a response to Oracle Web Cache that indicates it has a configuration file different than the local configuration file for the cache cluster. A cluster runtime operates with the same webcache.xml configuration file for all members.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Compare the two configuration files, and then propagate the proper version to all cluster members.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11078: Malformed environment object %.*s%.*s

Cause: The syntax of the XML file specified by the ESI environment is incorrect.

Action: Check the XML object for possible syntax errors.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11081: error while setting up the URI for +wcdebug for peer

Cause: Not applicable

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11082: error while constructing Inter-Cache Communication (ICC) header

Cause: Not applicable

Action: No action required.
Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11083: Proxy server configuration error: %s

Cause: The proxy server was not correctly configured.

Action: Check the proxy server configuration in the Origin Servers page of Fusion Middleware Control and the general configuration of the proxy server itself.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11085: Authentication for the remote or subscriber cache is being challenged by a central or provider cache. Retry.

Cause: Access to the central or provider cache requires authorization.

Action: Try accessing the cache again.
Level: 1

Type: TRACE

Impact: Security

WXE-11086: Retry-capable request removed from server %d

Cause: The request was sent to an origin server that was unable to service the request due to the specified error code. Other servers exist that might be able to service this request, so the server is being marked as "serviced

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11088: Following URL is now in cache:

Cause: The complete response was successfully received and populated into the cache.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11089: Error while sending the entity body to the origin server

Cause: Oracle Web Cache encountered a bad network connection or the origin server was down.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11091: Error while processing ESI for %.*s%.*s

Cause: An error was encountered while ESI processing was done for the response. The page will not be cached.

Action: No action required.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11092: Object validated for %.*s%.*s

Cause: The cached object was validated by the origin server and its expiration timestamps were updated accordingly.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11093: Content-Length value %d sent by origin server does not match number of bytes received, that is %d bytes for %.*s%.*s.

Cause: This error can occur if the origin server sent an incorrect Content-Length value or if the connection was unexpectedly terminated.

Action: Check that the origin server is sending the correct Content-Length for the URL mentioned.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11095: Update fails because object is no longer cacheable.

Cause: This request was no longer cacheable.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11096: Retry-capable request failed with error %s

Cause: The request was sent to an origin server that was unable to service the request due to the specified error code. Other servers exist that might be able to service this request, so the request is being re-submitted to another server.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11097: Retry-capable request submitted to another server (%d of %d)

Cause: The request was sent to an origin server that was unable to service the request due to the specified error code. Other servers exist that might be able to service this request, so the request is being re-submitted to another server.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11101: Unable to acquire write lock while inserting objects, cache insertion fails.

Cause: Read/write lock acquire fails.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11104: Unknown state in voluntary garbage collection

Cause: Unknown state in voluntary garbage collection.

Action: No action required.
Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11110: The maximum cache size is set too low. Oracle Web Cache failed to initialize.

Cause: The maximum cache size is set too low. Some of the data structures could not be initialized because of insufficient memory. This error could also be caused by changes to the file internal.xml.

Action: Increase the maximum cache size. If this fails, revert to the original values in internal.xml. Contact Oracle Support for information about the internal.xml file.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11111: Based on maximum cache memory limit %s, a cache table is created.

Cause: Normal trace behavior.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11118: Duplicate search key %.*s found in Surrogate-Key response header is discarded.

Cause: A duplicate search key was discovered in the Surrogate-Key response header.

Action: Remove the duplicate search key token from Surrogate-Key response header.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11119: The number of search keys changed.

Cause: The number of search keys has changed for the same cached object.

Action: No action required.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11126: Unable to start voluntary garbage collection fiber.

Cause: numHashBuckets_x < MINIMUM_CACHE_HASHTABLE_SIZE

Action: No action required.
Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11128: A duplicate cache insertion is found. Cache insertion fails.

Cause: Normal trace behavior.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11136: An error occurs during shutdown. The internal.xml file has been corrupted or moved.

Cause: The internal.xml file was corrupted or moved during the shutdown operation.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Recover internal.xml by copying from internal.xml.bak.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11138: Maximum number of versions is reached.

Cause: The number of versions in a cache entry has reached the maximum specified in the configuration.

Action: No action required.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11141: Traditional style basic key composed as %.*s.

Cause: Traditional style basic key composed.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11142: Traditional style cache key composed as %.*s.

Cause: Traditional style cache key composed.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11201: Oracle Web Cache is unable to resolve the IP address of %s. Check your DNS setup.

Cause: Oracle Web Cache was unable to resolve the IP address of the origin server.

Action: Check whether the origin server is a valid host. You can alter origin server configuration in the Origin Servers page of Fusion Middleware Control.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11202: Origin server %s does not use IPv4.

Cause: Oracle Web Cache only supports IP version 4. The IP address of the origin server could not be resolved because it used another version of IP.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Check that the origin server is a valid host and check the DNS setup. You can alter origin server configuration in the Origin Servers page of Fusion Middleware Control.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11203: Oracle Web Cache fails to connect to the origin server (id=%d).

Cause: An origin server is not available.

Action: Check the status of the origin server and the network connection.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11205: Oracle Web Cache marks the origin server %s (id=%d) as down and removes all session information bound to it.

Cause: The origin server was disabled or reached its failover threshold. Oracle Web Cache automatically distributes the request load over the remaining origin servers and polls the failed origin server for its current status.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11206: Oracle Web Cache is unable to start pinging the origin server. rc code=%d

Cause: There was a potential memory allocation error.

Action: Check the configured memory usage in the Resource Limits page of Fusion Middleware Control. If the problem persists, contact Oracle Support.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11207: Origin server %s (id=%d) is down; Oracle Web Cache starts polling for status.

Cause: The origin server reached its failover threshold. Oracle Web Cache automatically distributes the request load over the remaining origin servers and polls the failed origin server for its current status.

Action: No action required.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11208: Cache cluster member %s (id=%d) is down; cache cluster members start polling for status. Ping threshold set at %d.

Cause: The cache cluster member reached its failover threshold. Oracle Web Cache reassigns ownership of cache content, and polls the failed cache cluster member for its status.

Action: No action required.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11209: Origin server %s (id=%d) is back up; Oracle Web Cache stops polling and restores origin server.

Cause: The ping URL to the origin server succeeded.

Action: No action required.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11210: Cache cluster member %s (id=%d) is up; cache cluster members stop polling and restore it.

Cause: The ping URL to the cache cluster member succeeded.

Action: No action required.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11211: All origin servers for site %s are down. Last origin server was (id=%d).

Cause: All origin servers configured for the site are down.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11212: Cache cluster member %s (id=%d) pinged successfully. %d successful pings so far.

Cause: An origin server is not available.

Action: Check the status of the origin server and the network connection.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11220: Session binding routing to origin server %s:%u (id=%d) for site %.*s

Cause: Normal trace behavior.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11221: The origin server request is queued for site %.*s and site-to-server mapping %s.

Cause: The origin server was busy.

Action: Increase the capacity of the origin servers used by the site-to-server mapping.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11222: The origin server request is dropped due to a full queue for site %.*s and site-to-server mapping %s.

Cause: The origin server request queue was full.

Action: Increase the capacity of the origin servers used by the site-to-server mapping.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11223: The origin server request is routed to peer cache cluster member %s (id=%d) for site %.*s.

Cause: The request did not support session binding, and the requested object was owned by the peer cache cluster member.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11224: Site %.*s matches site-to-server mapping %s.

Cause: Normal trace behavior.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11225: Oracle Web Cache cannot find any running origin servers to route the request for site %.*s.

Cause: All origin servers are down.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11226: The session binding request is to a busy origin server %s:%u (id=%d) for site %.*s.

Cause: The session binding request was to a server was that was busy.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11227: Initial Request is routed to origin server %s using load balancing.

Cause: Normal trace behavior.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11228: No defined origin server can serve this request for site %.*s. The request is dropped.

Cause: This request was for a non-ESI page or for an ESI template and no matching site-to-server mapping was found. Dynamic origin servers are not allowed for these requests.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11229: This ESI fragment request is forwarded to a dynamic origin server for ESI provider site %.*s.

Cause: The request was for an ESI fragment without a matching site-to-server mapping. If possible, the request is forwarded to a dynamic origin server.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11232: Session binding to origin server %s:%u (id=%d) for site %.*s is given up because the origin server is down.

Cause: Normal trace behavior.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11233: Retry-capable request is routed to origin server %s using load balancing.

Cause: Normal trace behavior.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11234: No defined origin server which does not exclude ESI fragments can serve this ESI fragment request for site %.*s. The request is dropped.

Cause: This request was for an ESI fragment and any site-to-server mapping which matched for host and URL excluded ESI fragments. Use of a dynamic origin server for this site could cause a loopback to this Oracle Web Cache. Therefore, a dynamic server will not be used for for this request.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11235: The request for site %.*s is dropped because no origin server for site pattern %s is available.

Cause: The origin server was not available.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11240: Origin server %s:%u (id=%d) has %d connections timed out or closed for other reasons.

Cause: Normal trace behavior.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11250: ESI include fragment protocol does not match origin server protocol: Origin Server Protocol=%s URL=%s%.*s%.*s

Cause: The protocol used in the src attribute does not match the protocol specified in the Sites page of Fusion Middleware Control. Oracle Web Cache used the protocol configured for the origin server in the Sites or Site-to-Server Mapping page.

Action: Correct the protocol in the template for the fragment.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11260: Session binding cookie name %.*s with cookie value %.*s exceeds limit %d.

Cause: The cookie name and value exceeded the allowed length limit in Oracle Web Cache.

Action: Contact Oracle Support.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11261: Session binding query string parameter name %.*s with value %.*s exceeds limit %d.

Cause: The query string parameter name and value exceeded the allowed length limit in Oracle Web Cache.

Action: Contact Oracle Support.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11265: Starting dynamic origin server lookup (dispatcher %d entry %d)

Cause: Asynchronous dynamic origin server lookup started.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-11266: Completed dynamic origin server lookup (dispatcher %d entry %d)

Cause: Asynchronous dynamic origin server lookup completed.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-11270: Cache cluster member %s (id=%d) sent a peer member a configuration error in the response.

Cause: The response from a cache cluster member specified that its configuration did not match the configuration of a peer cache cluster member. This mismatch typically occurs because the configuration has not been propagated. You propagate configuration in the Cluster Operations page of Fusion Middleware Control.

Action: Contact Oracle Support.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11272: A response error from a cache cluster member is not from a known peer cache cluster member.

Cause: This error may be a logic error.

Action: Contact Oracle Support.
Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11290: DNS cache miss. Scheduling DNS task for host name %.*s

Cause: The entry for the host name was stale or missing in Oracle Web Cache's DNS cache. Oracle Web Cache scheduled a DNS task to get the host name.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11291: DNS lookup task scheduling fails for host %.*s.

Cause: Asynchronous task scheduling failed.

Action: Check the log of corresponding asynchronous task scheduling.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11292: DNS lookup succeeds for host %.*s.

Cause: The DNS cache miss and lookup succeeded.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11293: Oracle Web Cache fails to connect to dynamic origin server for ESI provider site and again performs a DNS lookup for host %.*s.

Cause: There was a possible stale DNS cache entry.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11294: Oracle Web Cache fails to connect to a dynamic origin server for ESI provider site with fresh DNS lookup result for host %.*s.

Cause: There was a potential system DNS error or invalid host.

Action: 1. Check whether the host is valid. 2. In a deployment environment, try to connect to this host and port. If the connection succeeds, then check the system/network DNS setup. 3. If problem persists, contact Oracle Support.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11295: Oracle Web Cache failed in DNS lookup for host %.*s.

Cause: There was a potential system DNS error or invalid host.

Action: 1. Check whether the host is valid. 2. In a deployment environment, try to connect to this host and port. If the connection succeeds, then check the system/network DNS setup. 3. If problem persists, contact Oracle Support
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11296: Dynamic origin server name %.*s is too long.

Cause: Dynamic origin server name specified for an ESI fragment is longer than 255 characters.

Action: Check the host name that appears in src attribute of <esi:include> tag.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11297: Cached DNS look up result for host %.*s is used.

Cause: Cached DNS look up result was used to establish a connection to a dynamic origin server.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11298: The request is dropped because no routing relationship is configured for serving the content.

Cause: No routing relationship is configured.

Action: Configure the routing relationships approriately.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11299: The DMS ECID %.*s detected in origin server response

Cause: The ECID generated internally by Oracle Web Cache was identified as mapping to the DMS ECID discovered in the incoming X-Oracle-DMS-ECID" origin server response header.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11300: The attempt to create an entry in the cache failed due to low memory.

Cause: Memory low during insertion.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11301: Compose key failed for slave object in file %s line %s.

Cause: Population_ComposeKeyIfCacheable() return invalid values.

Action: No action required.
Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11302: No I/O vector is found at line %d file %s.

Cause: tagInfo.nTotalNumberOfTags <= 0 && numDataBuffer > 0 for docBufList.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11303: Request method is not GET nor POST nor PUT; tunneling.

Cause: The HTTP method in the request is not one of GET, POST or PUT. Oracle Web Cache will tunnel this request between the client and the origin server.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11304: Cache miss request.

Cause: The cache did not have a object matching the request.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11306: Request is for a non-cacheable object, forwarding request to the backend.

Cause: Normal trace behavior.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11308: Request may not be cacheable according to caching rule.

Cause: Normal trace behavior.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11311: Oracle Web Cache generates a HTTP 200 OK status code.

Cause: The request completed successfully.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11312: invalid Oracle-ECID request header

Cause: Oracle Web Cache was unable to parse the Oracle-ECID request header.

Action: Correct the syntax of the Oracle-ECID request header.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11313: The cache server reached the maximum number of allowed incoming connections. Listening is temporarily suspended on port %d.

Cause: The cache server reached the maximum number of incoming connections specified in the Resource Limits page of Fusion Middleware Control.

Action: Try again later. If this message persists, increase the maximum incoming connections in the Resource Limits page of Fusion Middleware Control.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11314: Listening has resumed on port %d.

Cause: The number of incoming connection count is under the threshold, enabling the cache server to accept new requests from browsers.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11315: Oracle Web Cache generates a HTTP 202 Accepted status code.

Cause: The request was accepted.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11316: The request is for a End-User Performance Monitoring GIF file.

Cause: Normal activity for End-User Performance Monitoring.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11317: Oracle Web Cache generates an HTTP 304 Not-Modified status code.

Cause: Oracle Web Cache sent an HTTP 304 Not-Modified status code to the browser.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11321: Connection from browser cannot be established.

Cause: The handshake with the browser failed.

Action: No action required.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11322: Illegal value %d returned at frontend state machine.

Cause: Invalid status for Serv_HandleConn_DoGetRequest.

Action: No action required.
Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11324: Function Serv_HandleConn_x is called with invalid state %d.

Cause: Unknown state in Serv_HandleConn_x.

Action: No action required.
Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11325: Bad socket count

Cause: The socket count was inconsistent.

Action: No action required.
Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11327: The request contains incorrect content.

Cause: The object request could not be processed because the request contained incorrect or malformed information. Typical reasons are invalid, incomplete or malformed header information. This error can also occur when referencing ESI-only objects from non-ESI requests.

Action: Check the event log to determine which information is incorrect.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11328: Invalid socket

Cause: Invalid socket was found.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11330: The request prefix %.*s%.*s matches an alias for configured site %.*s.

Cause: The alias for the site matched the Host request header.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11331: Request matches configured site:

Cause: The Host request header matched the site name.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11332: Failed to rewrite URI from '%.*s' to '%.*s' according to rewrite rule '%.*s'. The original URI will be used.

Cause: URI rewrite failed. Oracle Web Cache will use the original URI in subsequent operations without rewriting.

Action: Modify URL rewrite rules.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11333: URI is rewritten from %.*s to %.*s according to rewrite rule %.*s.

Cause: URI rewrite was successful.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11334: User-Agent request header %.*s does not match any rule. Oracle Web Cache remapped User-Agent to the default value %.*s.

Cause: User-Agent request header did not match any rule.

Action: Manually modify user-agent rules in the webcache.xml file.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11335: User-Agent request header remapped from %.*s to %.*s according to mapping rule %s.

Cause: User-Agent request header matched a rule.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11336: The request fails authorization check.

Cause: The request was not processed due to insufficient privileges or authorization rejection.

Action: Make sure you are authorized to perform the administration, invalidation or monitoring operation.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11337: Administration service unavailable. Try again later.

Cause: There were too many administration requests.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Ensure that only one user is the administrator user.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11338: URL is in the cache

Cause: There was a matching entry in the cache for this request.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11339: Oracle Web Cache determined the request might be cacheable based on existing cache policy.

Cause: There was no matching cache entry for this request. However, based on existing cache policy, Oracle Web Cache determined that it is likely to be cacheable.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11340: A new entry in the cache is created.

Cause: Oracle Web Cache created an entry in the cache for this request.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11342: Oracle Web Cache determined the request might not be cacheable based on existing cache policy.

Cause: There was no matching cache entry for this request. However, based on existing cache policy, Oracle Web Cache determined that it is likely to be not cacheable.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11343: The requested site does not have a matching origin server mapping. A bad request error will be returned.

Cause: There was no matching site-to-server mapping for this non-ESI-fragment request.

Action: No action required.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11344: Returning a freshly cached object.

Cause: The cached object will be returned because it is still fresh.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11345: The cached object is stale and this request will be served stale.

Cause: The cached object is stale and Oracle Web Cache decided to serve the stale copy to the request.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11346: The cached object is stale and an origin server will be contacted for a fresh copy.

Cause: Because the cached object is stale, Oracle Web Cache fetched a new version of the object to update the cache and satisfy this request with the new response.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11347: The cached object is garbage.

Cause: The cached object is in garbage state, meaning that it could not be used to serve to the client.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11348: There is already another pending request for the same object being forwarded to the origin server for a fresh copy. This request will wait for the fresh copy.

Cause: The cached object is in garbage state, and there is another request for the same object being forwarded to the origin server for a fresh copy to update the cache. Therefore, this request will wait until the fresh copy arrives.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11349: The request will be forwarded to the origin server to obtain a fresh copy of the object.

Cause: The cached object was in garbage state, and there was no other request pending to update the cache. Oracle Web Cache will forward this request to the origin server for a fresh copy of the object to update the cache and satisfy this request with the new response.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11350: The request contains no site information in the URL or Host header. The configuration of the default site %s will be used.

Cause: The request did not contain a Host header, nor did it have an absolute URL that contained a site name. Oracle Web Cache will use the default site in the configuration for this request.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11351: The complete site name is: %s

Cause: The complete site name was resolved based on the configuration.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11352: There is no matching defined site or aliases in the configuration for this request.

Cause: The configuration did not contain a matching site definition for the request. The site name will be taken from the request as is.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11354: Out of memory while processing the request. A service unavailable response is returned to the client. Client IP: %s

Cause: Oracle Web Cache failed to obtain enough memory while processing the request.

Action: Adjust the maximum cache size in the Resource Limits page of Fusion Middleware Control. If the problem persists, contact Oracle Support.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11355: Single request header length exceeds configured maximum. A forbidden error response is returned to the client. Client IP: %s

Cause: One of the headers in the request exceeded the configured maximum.

Action: Adjust the maximum individual header size limit in the Security page of Fusion Middleware Control. If the problem persists, contact Oracle Support.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11356: Total request header length exceeds configured maximum. A forbidden error response is returned to the client. Client IP: %s

Cause: The total length of the headers in the request exceeded the configured maximum.

Action: Adjust the maximum combined header size limit in the Security page of Fusion Middleware Control. If the problem persists, contact Oracle Support.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11357: Failed to resolve the requested site name. A bad host error response is returned to the client.

Cause: The request did not contain enough information about the site name.

Action: No action required.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11358: Failed client certificate check. A forbidden error response is returned.

Cause: The request was for a URL that requires a client certificate, and the certificate check failed for this request.

Action: No action required.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11359: Host header missing in HTTP/1.1 request. A bad host error response is returned.

Cause: The request was an HTTP/1.1 request, but is missing the required Host header.

Action: No action required.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11360: Error processing the Transfer-Encoding header in the request. A bad request error response is returned.

Cause: An error was encountered while processing the Transfer-Encoding header in the request.

Action: No action required.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11361: Transfer-Encoding specified in the request is not supported. An HTTP not implemented error response is returned.

Cause: Oracle Web Cache only supports chunked encoding. Other types transfer encoding are not supported.

Action: No action required.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11362: Malformed request. A bad request error response is returned. Client IP: %s

Cause: The request was malformed.

Action: No action required.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11363: Out of memory while processing the request. The request is dropped.

Cause: Oracle Web Cache failed to obtain enough memory while processing the request.

Action: Adjust the maximum cache size in the Resource Limits page of Fusioin Middleware Control. If the problem persists, contact Oracle Support.
Level: 16

Type: ERROR

Impact: Memory

WXE-11364: Network error response is returned.

Cause: A network error was encountered while processing the request.

Action: Check other error messages related to this request.
Level: 16

Type: ERROR

Impact: Network

WXE-11365: Server busy response is returned.

Cause: The origin servers for the requested site were at full capacity, and the waiting queue was full.

Action: Increase the capacity of the origin servers.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11366: A client connection to listening port %d is dropped.

Cause: A connection failure was encountered between Oracle Web Cache and the client, so the request could not be completed.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11367: No matching origin server can be found for the requested site. A bad host error response is returned

Cause: The requested site did not have any matching origin servers in the configuration.

Action: Modify the Sites page of Oracle Enterprise Manager or Site-to-Server Mapping page of Oracle Web Cache Manager.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11368: ESI exception error response is returned.

Cause: An ESI exception was encountered while processing the request.

Action: Check other error messages related to this request.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11369: The request method is not supported. An HTTP not implemented error response is returned.

Cause: The request specified an unsupported method.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11370: A chunk-encoded request entity body contains a chunk that exceeds %u bytes. A bad request error response is returned. Client IP: %s

Cause: This chunk-encoded request contained a chunk that exceeded the DOCHEADERBUFFERSIZE setting in internal.xml

Action: Consider increasing DOCHEADERBUFFERSIZE.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11371: Malformed request. The chunk-encoded request entity body contains a line feed without a preceding carriage return. A bad request error response is returned. Client IP: %s

Cause: The request is malformed.

Action: No action required.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11372: Aborting origin server request

Cause: A request sent to Oracle Web Cache was aborted. Because Oracle Web Cache was in the process of forwarding the request to an origin server, the request to the origin server was also aborted.

Action: No action required.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11373: This request %.*s is not being enabled with End-User Performance Monitoring

Cause: A single response from the origin server to Oracle Web Cache was not enabled for End-User Performance Monitoring because of a software limitation.

Action: No action required.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11376: The cached object is stale and this request will be served stale. However origin server is already being contacted for the fresh copy by some other request

Cause: The cached object is stale and Oracle Web Cache decided to serve the stale copy to the request. The origin server was already contacted for the fresh copy by some other request

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11377: Aborting receiving request entity body because origin server connection has been aborted

Cause: An error occurred while sending the request entity body to an origin server. The origin server connection was aborted. Because of this, Oracle Web Cache is aborting the request received from the client.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11379: The request is using global site configuration.

Cause: Oracle Web Cache used global site configuration for this request.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11381: A request is sent for a forbidden operation.

Cause: The request was attempted to be performed on an IP address for which the operation is forbidden.

Action: Check the IP address to ensure the correct target platform was specified.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11382: The URL for the statistics monitoring request is not valid.

Cause: The incorrect URL was used for the statistics monitoring request.

Action: Check the URL.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11383: The request has an internal error.

Cause: The request was invalid.

Action: Contact Oracle Support.
Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11384: Changing incoming ECID from %.*s to %.*s

Cause: The ECID discovered in the incoming Oracle-ECID request header has been changed to reflect the nested client request.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11385: The request fails because the service is unavailable.

Cause: The request was not processed because the service at the specified IP address was not available.

Action: Make the sure service is available prior to initiating the invalidation request.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11386: The request fails because the portal service is unavailable.

Cause: The request was not processed because the service at the specified IP address was not available.

Action: Make sure the service is available prior to initiating the invalidation request.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11387: The request fails due to a gateway timeout.

Cause: The request was not be processed due to a gateway timeout.

Action: Make sure the gateway is active and available for processing requests.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11388: The DMS ECID %.*s overrides the legacy ECID %s.

Cause: The ECID generated internally by Oracle Web Cache was identified as mapping to the DMS ECID discovered in the incoming ECID-Context" client request header.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11389: The request fails due to unsupported ESI operation.

Cause: The request was not processed because no clients on the path of request can provide sufficient ESI processing capability.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Check the offending ESI tag for correctness or possible typographical errors.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11390: The ECID %.*s overrides the temporary ECID %s.

Cause: The ECID generated internally by Oracle Web Cache was overridden by the new ECID discovered in the incoming Oracle-ECID request header. From now on, events logged within the request/response context will be displayed with the new ECID instead of the temporary ECID.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11391: Detailed information about ECID %s is in the next line.

Cause: Additional information about the request represented by the ECID was acquired and will be printed in the next line in the event log.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-11392: The object is in the cache, but the inactivity timeout cookie must be updated.

Cause: The cached object will be returned to the client, but the inactivity timeout cookie must first be updated.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11393: The central cache or provider cache has challenged the remote or subscriber cache for identity information.

Cause: The central cache or provider cache requested content from its parent cache. Before receiving content, it must register itself as an Oracle Web Cache to establish a hierarchical relationship.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11394: The invalidation request is redundant.

Cause: The invalidation request was not processed because the request was redundant with a previous requests. This error can occur in cache hierarchies.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11396: unknown internal error

Cause: The error number was improperly set.

Action: Check which module is not setting the error number
Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11397: request failed due to insufficient memory

Cause: The object request failed due to insufficient memory necessary to process all of the objects.

Action: Increase the size of the pagefile.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11398: A client connection to listening port %d is dropped at the end of keep-alive session.

Cause: A connection between Oracle Web Cache and the client was terminated, marking the end of the keep-alive session.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11399: The port number in the Host header %.*s is replaced with the port number of the connection %.*s.

Cause: As a work around for an known Internet Explorer problem, the port number in the Host header was ignored and port number of the actual connection was used to determine the site instead.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11400: non-200 OK HTTP status code response code of %d

Cause: The response received from the origin server contained a HTTP status code other than 200 OK.

Action: If this is not the intended response, then check the application code.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11403: begin cacheability decision for url:

Cause: This marks the start of the cacheability decision for the specified URL. All messages logged between this message and the "final cacheability decision made" message are about the same request/response pair.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11404: Time %.*s in the Last-Modified header is after the current time. The cache is using the current time instead.

Cause: The Last-Modified response header received from the origin server contained a time that is in the future. The cache used the current time as the last-modified time instead.

Action: Check the application code that generates the Last-Modified response header, and make sure the machine where Oracle Web Cache is running has its clock in-sync with the clock of the application Web server.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11405: Request/Response matches no-cache rule with URL expression \"%s\".

Cause: The request URL matched a non-cacheable caching rule.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11406: Request/Response matches no-cache rule with MIME type expression \"%s\".

Cause: The request/response matched a non-cacheable caching rule.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11407: Request/Response matches no-cache rule with URL expression \"%s\" and MIME type expression \"%.*s\".

Cause: The request/response matched a non-cacheable caching rule.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11408: Request/Response matches no-cache catch-all rule.

Cause: The request/response matched a non-cacheable caching rule.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11409: HTTP POST request body length %d exceeds maximum cacheable post body limit %d.

Cause: The POST body length in the request exceeded the maximum cacheable limit for a POST body. Therefore, the corresponding response was not cached.

Action: If this response needs to be cached, contact Oracle Support.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11410: Response contains cookie \"%.*s=%.*s\", which is not present in the request.

Cause: The response received from the origin server contained a newly created cookie that was not present in the request. As a result, Oracle Web Cache considered the response to be non-cacheable.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11411: Response contains cookie \"%.*s=%.*s\", which does not match the same cookie value \"%.*s\" in the request.

Cause: The response received from the origin server contained a new cookie that is different from the cookie value in the request. As a result, Oracle Web Cache considered the response to be non-cacheable.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11412: The Surrogate-Control header conflicts with an existing caching rule. Cached objects associated with the previous rule will be marked for removal from the cache.

Cause: The Surrogate-Control header in the response contained control directives that were in conflict with an existing caching rule. This will cause Oracle Web Cache to mark all existing objects in the cache that were associated with the previous rule for removal.

Action: If this is not the intended behavior, then check the application logic, as well as the configured caching rule.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11413: The HTTP request method is not GET, or the URL contains query string parameters. The request is not cacheable.

Cause: The request used an HTTP method that was neither GET nor POST. As a result, Oracle Web Cache considered it to be non-cacheable.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11414: Basic cache key is composed with sitename %.*s, URI %.*s, method %.*s, post body %.*s.

Cause: The initial cache key was composed of the complete site name, the URL, the HTTP request method, and the POST body, if any.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11415: Final cache key is composed sitename %.*s, URI %.*s, method %.*s, post body %.*s, multiversion %.*s, compressed %.*s.

Cause: The final cache key was composed of the initial cache key plus any cookies and headers as specified by caching rule.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11416: The response is considered not cacheable due to the lack of caching directives.

Cause: The response did not contain any headers with caching directives and had no matching caching rule. As a result, Oracle Web Cache considered it to be non-cacheable.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11417: URL is not cacheable based on its HTTP headers.

Cause: The response contained regular HTTP headers that indicated it was not cacheable. As a result, Oracle Web Cache considered it to be non-cacheable.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11418: The response contains a Surrogate-Control header with either a no-store control directive or a zero-value max-age control directive, indicating that the response is non-cacheable.

Cause: The response contained a Surrogate-Control header with either a no-store control directive or a zero-value max-age control directive. As a result, Oracle Web Cache considered it to be non-cacheable.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11419: The Surrogate-Control header contains a nonzero max-age=%d+%d control directive, indicating that the response is cacheable.

Cause: The response contained a Surrogate-Control header with a nonzero max-age directive. As a result, Oracle Web Cache considered it to be cacheable.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11420: The response contains Surrogate-Control header with a zero-value max-age control directive and ETag header, indicating that the response is cacheable with validation.

Cause: The response contained Surrogate-Control header with a zero-value max-age control directive and ETag header. As a result, Oracle Web Cache considered it to be cacheable with validation.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11421: The response contains ETag and X-Oracle-Cache headers, indicating that the response is cacheable with validation.

Cause: The response contained ETag and X-Oracle-Cache headers. As a result, Oracle Web Cache considered it to be cacheable with validation.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11422: The Surrogate-Control header contains the vary control directive, overriding configuration.

Cause: The response Surrogate-Control header contained the vary control directive. It is used in place of the existing caching rule.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11423: Oracle Web Cache ran out of memory while creating caching rule according to the vary control directive of the Surrogate-Control header.

Cause: There was not sufficient memory for Oracle Web Cache to process the vary control directive.

Action: Adjust the maximum cache size in the Resource Limits page of Fusion Middleware Control. If the problem persists, contact Oracle Support.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11424: The request contains session %s, which makes it non-cacheable based on the existing caching rule.

Cause: The current caching rule for this URL specified that if a specific session exists in the request, then the request is treated as non-cacheable.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11425: The request does not contain session %s, which makes it non-cacheable based on the existing caching rule.

Cause: The current caching rule for this URL specified that if a specific session did not exist in the request, the request is treated as non-cacheable.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11426: The request does not contain cookie %s, which makes it non-cacheable based on the existing caching rule.

Cause: The current caching rule for this URL specified that if a specific cookie does not exist in the request, the request is treated as non-cacheable.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11427: The request does not contain HTTP request header %s, which makes it non-cacheable based on the existing caching rule.

Cause: The current caching rule for this URL specified that if a specific header does not exist in the request, the request was treated as non-cacheable.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11428: The X-Oracle-Expires header contains TTL of %d seconds, indicating that the response is cacheable.

Cause: The response contained an X-Oracle-Expires header with a nonzero TTL value. As a result, Oracle Web Cache considered it to be cacheable.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11429: The response contains ETag header and zero value TTL in X-Oracle-Expires header, indicating that the response is cacheable with validation.

Cause: The response contained an X-Oracle-Expires header with a zero value TTL and an ETag header. As a result, Oracle Web Cache considered it to be cacheable with validation.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11430: The response contains zero value TTL in X-Oracle-Expires header with no ETag header, indicating that the response is non-cacheable.

Cause: The response contained an X-Oracle-Expires header with a zero value TTL. As a result, Oracle Web Cache considered it to be not cacheable.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11431: In absence of any overriding headers in the response, the response is not cacheable based on the existing caching rule.

Cause: The response was not cacheable because the matching caching rule indicates so, and there are no overriding response headers in the response to override the caching rule.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11432: The HTTP response headers indicate that the response is cacheable.

Cause: The response contained the HTTP headers that indicate it is cacheable.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11433: An existing NCM entry states object is too large to be cacheable.

Cause: The response body size was possibly greater than the maximum cacheable object size.

Action: If this is not the desired behavior, increase the maximum cached object size value in the Resource Limits page of Fusion Middleware Control.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11434: The ESI include or inline tag for this fragment contains reference TTL=%d+%d, making the fragment cacheable.

Cause: The ESI include or inline tag for the fragment contained a nonzero reference TTL. As a result, Oracle Web Cache considered the fragment cacheable.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11442: Oracle Web Cache could not process the response for ESI because the Content-Type is not valid for ESI processing.

Cause: The Surrogate-Control response header contained a content token with values indicating that ESI parsing should be done, but the Content-Type header value was not text or HTML.

Action: If the content needs to be processed for ESI, the application code must modify the Content-Type to be text or HTML.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11443: The request does not contain header %.*s, which makes it non-cacheable based on the vary control directive in the Surrogate-Control response header.

Cause: The request was missing a required header to be cacheable based on the vary control directive in the Surrogate-Control response header.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11444: The request does not contain cookie %.*s, which makes it non-cacheable based on the vary control directive in the Surrogate-Control response header.

Cause: The request was missing a required cookie to be cacheable based on the vary control directive in the Surrogate-Control response header.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11445: Following URL will not be cached:

Cause: The final cacheability decision for this response is not cacheable.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11446: URL which will be cached is:

Cause: The final cacheability decision for this response is cacheable.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11447: Request/Response matches a dynamic caching rule.

Cause: The request/response matched a dynamic caching rule.

Action: No action required. caching rules.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11448: Request/Response does not match any caching rule.

Cause: The request/response did not match any configured caching rule.

Action: If this is not the intended behavior, then check the configured caching rules.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11449: The response is too large to be cached.

Cause: The response size is larger than the configured maximum size of a single cached object.

Action: Check the configured Maximum Size of Single Cached Object in the Resource Limits page of Fusion Middleware Control. If the problem persists, contact Oracle Support.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11450: Object is cached because it does not exceed allowed size for an object.

Cause: The object was cacheable because its response was within the configured maximum object size. Previously, the object was uncacheable because it exceeded the limit.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11451: Update fails because object is no longer cacheable.

Cause: This request was no longer cacheable.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11452: Update fails; Oracle Web Cache fetches response as a cache miss.

Cause: An update of the object failed. Oracle Web Cache processes the request as a cache miss.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11453: A new cache policy is created based on the Surrogate-Control header.

Cause: The caching properties specified in the Surrogate-Control header conflicts with the existing cache policy, therefore Oracle Web Cache created a new policy to be used for future requests.

Action: If this is not the intended behavior, then check the application logic, as well as the configured caching rule.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11454: Current compression is on, conflicting with the previous setting.

Cause: The response contains a compression setting either explicitly through the Surrogate-Control header or implicitly through the absence of it that was in conflict with an existing compression setting. This will cause Oracle Web Cache to mark all existing objects in the cache that were associated with the previous setting for removal.

Action: If this is not the intended behavior, then check the application logic, as well as the configured caching rule.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11455: The response indicates security validation is required, conflicting with the previous setting.

Cause: The response contains a security validation setting either explicitly through the Surrogate-Control: secure-view token or implicitly through the absence of it that was in conflict with an existing security validation setting. This will cause Oracle Web Cache to mark all existing objects in the cache that were associated with the previous setting for removal.

Action: If this is not the intended behavior, then check the application logic, as well as the configured caching rule.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11456: The response indicates version validation is required, conflicting with the previous setting.

Cause: The response contains a version validation setting either explicitly through the Surrogate-Control: version token or implicitly through the absence of it that was in conflict with an existing security validation setting. This will cause Oracle Web Cache to mark all existing objects in the cache that were associated with the previous setting for removal.

Action: If this is not the intended behavior, then check the application logic, as well as the configured caching rule.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11457: The response contains a Surrogate-Control: authentication token that is not supported by Oracle Web Cache.

Cause: The Surrogate-Control: authentication token value of response header indicates an authentication mechanism that is not supported by Oracle Web Cache for caching such documents. The response will not be cached.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. If this is not the intended behavior, then check the application logic.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11458: Following URL that requires Oracle Single Sign-On authentication is being inserted in the cache:

Cause: Caching is enabled for documents that require Oracle Single Sign-On authentication but have no other authorization requirement.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11459: URL is not cacheable because the request contains an Authorization header.

Cause: The request contained a HTTP header that indicated the response would be non-cacheable. As a result, Oracle Web Cache considered it to be non-cacheable.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11460: URL is not cacheable because the request contains a Proxy-Authorization header.

Cause: The request contained a HTTP header that indicated the response would be non-cacheable. As a result, Oracle Web Cache considered it to be non-cacheable.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11461: URL is not cacheable because the request contains a Cookie header.

Cause: The request contained a HTTP header that indicated the response would be non-cacheable. As a result, Oracle Web Cache considered it to be non-cacheable.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11462: URL is not cacheable because the response contains a Set-Cookie header.

Cause: The response contained regular HTTP headers that indicated it was not cacheable. As a result, Oracle Web Cache considered it to be non-cacheable.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11463: URL is not cacheable because the response contains a Cache-Control: no-store header.

Cause: The response contained regular HTTP headers that indicated it was not cacheable. As a result, Oracle Web Cache considered it to be non-cacheable.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11464: URL is not cacheable because the response contains a Cache-Control: no-cache header.

Cause: The response contained regular HTTP headers that indicated it was not cacheable. As a result, Oracle Web Cache considered it to be non-cacheable.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11465: URL is not cacheable because the response contains a Pragma: no-cache header.

Cause: The response contained regular HTTP headers that indicated it was not cacheable. As a result, Oracle Web Cache considered it to be non-cacheable.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11466: URL is not cacheable because the response contains a Warning header.

Cause: The response contained regular HTTP headers that indicated it was not cacheable. As a result, Oracle Web Cache considered it to be non-cacheable.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11467: URL is not cacheable because the Expires header indicates that it has expired.

Cause: The response contained regular HTTP headers that indicated it was not cacheable. As a result, Oracle Web Cache considered it to be non-cacheable.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11468: URL is not cacheable because the response contains no expiration information.

Cause: The response contained no expiration headers. As a result, Oracle Web Cache considered it to be non-cacheable.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11469: URL is cacheable because the response contains an ETag header.

Cause: The response contained HTTP headers that indicate it is cacheable.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11470: URL is cacheable because the response contains an Expires header, indicating it expires in the future.

Cause: The response contained HTTP headers that indicate it is cacheable.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11471: URL is cacheable because the response contains a Cache-Control header with a positive max-age directive.

Cause: The response contained HTTP headers that indicate it is cacheable.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11472: The response contains a Surrogate-Control header with a restore-POST directive, indicating that the response is not cacheable.

Cause: The response contained instructions to cache the request POST data content. As a result, Oracle Web Cache considered the response to be non cacheable. If this is a 302 redirect to a POST response, Oracle Web Cache will save the the request POST content in the cache to be used upon a future restore POST request.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11473: Cache key output truncated due to excessive post body size

Cause: The cache key message (11414, 11415) could not display the entire cache key because the post body message size exceeded the threshold specified in the configuration file.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11474: Current compression is off, conflicting with the previous setting.

Cause: The response contains a compression setting either explicitly through the Surrogate-Control header or implicitly through the absence of it that was in conflict with an existing compression setting. This will cause Oracle Web Cache to mark all existing objects in the cache that were associated with the previous setting for removal.

Action: If this is not the intended behavior, then check the application logic, as well as the configured caching rule.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11475: Current SSO authentication is on, conflicting with the previous setting.

Cause: The response contains an authentication setting either explicitly through the Surrogate-Control header or implicitly through the absence of it that was in conflict with an existing authentication setting. This will cause Oracle Web Cache to mark all existing objects in the cache that were associated with the previous setting for removal.

Action: If this is not the intended behavior, then check the application logic.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11476: Current SSO authentication is off, conflicting with the previous setting.

Cause: The response contains an authentication setting either explicitly through the Surrogate-Control header or implicitly through the absence of it that was in conflict with an existing authentication setting. This will cause Oracle Web Cache to mark all existing objects in the cache that were associated with the previous setting for removal.

Action: If this is not the intended behavior, then check the application logic.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11477: The response contains a Surrogate-Control: authentication token but SSO authentication is not enabled.

Cause: The Surrogate-Control: authentication token is present but SSO authentication is not enabled for caching. The response will not be cached.

Action: Turn on SSO authentication by editing webcache.xml: find the SECURITY element under the GENERAL element. Assign a positive value to the SSO_COOKIE_CACHE_TIME attribute.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11478: The response indicates security validation is not required, conflicting with the previous setting.

Cause: The response contains a security validation setting either explicitly through the Surrogate-Control: secure-view token or implicitly through the absence of it that was in conflict with an existing security validation setting. This will cause Oracle Web Cache to mark all existing objects in the cache that were associated with the previous setting for removal.

Action: If this is not the intended behavior, then check the application logic, as well as the configured caching rule.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11479: The response indicates version validation is not required, conflicting with the previous setting.

Cause: The response contains a version validation setting either explicitly through the Surrogate-Control: version token or implicitly through the absence of it that was in conflict with an existing security validation setting. This will cause Oracle Web Cache to mark all existing objects in the cache that were associated with the previous setting for removal.

Action: If this is not the intended behavior, then check the application logic, as well as the configured caching rule.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11480: Post body masked due to security

Cause: The cache key message (11414, 11415) will not display the entire cache key because the post body was masked.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11481: Request/Response matches caching rule with URL expression \"%s\".

Cause: The request/response matched a cacheable caching rule.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11482: Request/Response matches caching rule with MIME type expression \"%.*s\".

Cause: The request/response matched a cacheable caching rule.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11483: Request/Response matches caching rule with URL expression \"%s\" and MIME type expression \"%.*s\".

Cause: The request/response matched a cacheable caching rule.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11484: Request/Response matches catch-all caching rule.

Cause: The request/response matched a cacheable caching rule.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11485: Request/Response matches disabled caching rule with URL expression \"%s\".

Cause: The request/response matched a disabled caching rule; thus, the rule is ignored.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11486: Request/Response matches disabled caching rule with MIME type expression \"%.*s\".

Cause: The request/response matched a disabled caching rule; thus, the rule is ignored.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11487: Request/Response matches disabled caching rule with URL expression \"%s\" and MIME type expression \"%.*s\".

Cause: The request/response matched a disabled caching rule; thus, the rule is ignored.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11488: Request/Response matches disabled catch-all caching rule.

Cause: The request/response matched a disabled caching rule; thus, the rule is ignored.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11489: HTTP response-header parsing error on Surrogate-Control token: %.*s. Full header line is: %.*s.

Cause: An HTTP Surrogate-Control response header from the origin server contained an individual header value that was malformed or unexpected. The Surrogate-Control tokens up to the malformed one were processed. The malformed token and any tokens which follow it were ignored.

Action: If the behavior is still as expected, no action is required. If the behavior is not as expected, check the application code that generates the Surrogate-Control header.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11500: StatisticsTimerInterval configuration parameter should be between 10, 000 and 1, 000, 000 microseconds, and should be a factor of 1, 000, 000

Cause: Illegal configuration parameter for statistics timer interval.

Action: This error usually occurs as a result of wrong configuration. Contact Oracle Support.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11501: While getting detailed memory statistics, pointer swapped while filling HTML

Cause: While retrieving detailed memory statistics, the timer pointer swapped to a new index as it was filling the HTML template.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-11502: Unable to create or open file %s for write. Cache contents not written.

Cause: The cache server was unable to open the file specified. Either the file already exists and the Oracle Web Cache user does not have write permission on the file or the Oracle Web Cache user does not have write permission to the directory.

Action: Check permissions on the file and the directory and correct them to allow Oracle Web Cache to create the file or write to it.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11503: Abnormal statistics value of %s was detected. Value 0 was recorded.

Cause: Internal error. The statistics value that was returned was an abnormal (negative) value.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. If the problem persists, contact Oracle Support.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11504: Client IP checking for the statistics message fails. Access denied.

Cause: Oracle Web Cache allows statistics requests to be sent from configured trusted hosts or trusted subnets. The current statistics request message was not sent from an IP address that belongs to a trusted host or subnet.

Action: Add the IP address for the computer as trusted host in the Security page of Fusion Middleware Control.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11505: The number of statistics monitoring requests exceeds queue limit.

Cause: The number of statistics monitoring requests exceeded the request queue limit.

Action: Try the request at a later time.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11506: Invalid IP address in statistics request

Cause: The request to the statistics port is from invalid IP address.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11600: Illegal value set for HeuristicsValidityFunc

Cause: The heuristics validity function ID was corrupted. This error is the result of internal configuration errors.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. If the problem persists, contact Oracle Support.
Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11601: Illegal value set for HeuristicsPropensityFunc

Cause: The heuristics propensity function ID was corrupted. This error is the result of internal configuration errors.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. If the problem persists, contact Oracle Support.
Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11602: Illegal value set for HeuristicsThresholdFunc

Cause: The heuristics threshold function ID was corrupted.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. This error usually occurs as a result of internal configuration errors. If the problem persists, contact Oracle Support.
Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11604: Illegal value set for POPULARITYSCALE.

Cause: The popularity heuristic parameter is not valid.

Action: Contact Oracle Support.
Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11605: Illegal value set for THRESHOLDSCALE.

Cause: The threshold heuristic parameter is not valid.

Action: Contact Oracle Support.
Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11606: Illegal value set for THRESHOLDBASE.

Cause: The threshold base heuristic parameter is not valid.

Action: Contact Oracle Support.
Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11608: Illegal value set for ECATELMFACTOR.

Cause: The Cate LMFactor heuristic parameter is not valid.

Action: Contact Oracle Support.
Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11610: Illegal value set for OWNERSHIPPREFERENCE.

Cause: The ownership preference heuristic parameter is not valid.

Action: Contact Oracle Support.
Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11700: Client IP checking for the invalidation message fails. Access denied.

Cause: Oracle Web Cache allows invalidation to be sent from configured IP groups. The current invalidation message was not sent from an IP address that belongs to the configured groups.

Action: Configure trusted hosts in the Security page of Fusion Middleware Control.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11701: Authentication failed. Invalid username or password.

Cause: The invalidation message contained an incorrect username or password.

Action: Resend the invalidation message with the correct invalidator user name and password. You can change the password in the Security page of Fusion Middleware Control.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11702: The invalidation request contains an empty request body.

Cause: The invalidation request contained an empty request body.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Resend the invalidation request with a request body.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11703: Invalidation request specifies a wrong URL.

Cause: The invalidation message carried a wrong request URL.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11704: Invalidation message contains XML parsing errors.

Cause: The invalidation message contained invalid XML.

Action: Correct the XML errors in the invalidation message.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11705: Invalid validity level '%s' is requested.

Cause: The invalidation message specified an invalid validity level. The correct range of level is between 0 and 9.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Correct the message to use a validity level between 0 to 9.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11706: %d object(s) matching prefix '%s' are invalidated.

Cause: Invalidation of objects was successful.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-11707: Object with URL '%s' is successfully invalidated.

Cause: Invalidation was successful.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-11708: Object with URL '%s' is not cacheable. Invalidation is not done.

Cause: The URL was not a cacheable object. Invalidation is not performed for non-cacheable objects.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-11710: Object with URL '%s' not in the cache. Invalidation is not performed.

Cause: The object was not in the cache. Invalidation is not performed for non-cacheable objects.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-11711: Oracle Web Cache cannot compose key pattern for requested URL '%s'.

Cause: Oracle Web Cache could not compose a key pattern for requested URL expression.

Action: Correct the URL expression in the invalidation message.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11712: Invalidation message contains unrecognized cookies.

Cause: The invalidation message contained nonexistent cookies.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Correct the cookie name specified in the invalidation message.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11713: Invalid regular expression found in invalidation message. %s

Cause: The invalidation message contained an invalid regular expression that could not be compiled.

Action: Correct the regular expression in the invalidation message.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11715: Regular expression matching error. Error number: %d

Cause: The regular expression in the invalidation message was invalid. Oracle Web Cache could not perform regular expression matching successfully.

Action: Check regexec man page with the error number for syntax error description.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11716: Invalidation XML message cannot be parsed.

Cause: Invalidation XML message could not be parsed.

Action: No action required.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11717: Invalidation XML error found in invalidation message.

Cause: Oracle Web Cache received an invalidation message in an old version. It is unable to obtain all information about the URL node.

Action: Correct the invalidation message or use an invalidation version of either "WCS-1.1" or "WCS-1.0".
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11718: Cannot allocate memory for KeyParam structure.

Cause: Oracle Web Cache could not allocate memory for KeyParam structure.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Check memory configuration. Restart Oracle Web Cache if necessary.
Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11719: Cannot allocate memory for Invalidate_AttributeT structure.

Cause: Oracle Web Cache could not allocate memory for Invalidate_AttributeT structure.

Action: Check memory configuration. Restart Oracle Web Cache if necessary.
Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11720: Cannot allocate memory for or sizeof '%s'.

Cause: Oracle Web Cache could not allocate memory.

Action: Check memory configuration. Restart Oracle Web Cache if necessary.
Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11721: Cannot read value for XML element/attribute: '%s'.

Cause: Oracle Web Cache was unable to obtain all information about the specified XML element or attribute.

Action: Correct the XML in the invalidation message.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11722: Invalidation message specifies unknown version: '%s'.

Cause: The invalidation message specified an unknown version.

Action: Correct the invalidation message to use version "WCS-1.1 or "WCS-1.0".
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11723: Value of XML string '%s' too long. Actual length: %d, max length allowed: %d.

Cause: The XML string in the invalidation message exceeded the allowed length limit.

Action: Correct the XML in the invalidation message.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11724: URL path prefix does not end with '/': '%s'.

Cause: The URL path prefix did not end with '/' in the invalidation message.

Action: Correct the syntax of the URL path prefix in the invalidation message.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11725: Cannot create XML element/attribute: '%s'.

Cause: Oracle Web Cache could not create the XML element or attribute.

Action: Check the maximum cache size in the Resource Limits page of Fusion Middlewae Control. Restart Oracle Web Cache if necessary.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11726: Cannot set XML attribute '%s' for element '%s'.

Cause: Oracle Web Cache could not set the XML attribute value.

Action: Check the maximum cache size in the Resource Limits page of Fusion Middleware Control. Restart Oracle Web Cache if necessary.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11727: Unexpected/unsupported argument '%s' in function '%s'.

Cause: The invalidation message specified an unsupported name and value pair for <SYSTEMINFO ... />

Action: See Chapter "Sending Invalidation Requests" in the Oracle Web Cache Administrator's Guide for the possible values allowed for <SYSTEMINFO ... />.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11728: Cluster error: Peer cache '%d' returns bad response.

Cause: The invalidation response from a peer cache was not parsed.

Action: Check the network connection between current cache and its peer.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11729: Invalidation message contains conflicting HOST values: '%s' and '%s'.

Cause: The invalidation message contained conflicting HOST values in the URIPREFIX and the HOST attributes.

Action: Correct the host information in the invalidation message.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11730: Invalidation message from provider cache with IP %s port %d is dropped.

Cause: The invalidation message propagated from the specified provider cache is either outdated or invalid. Invalidation is discarded.

Action: No action required.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11731: Normal request is from an unknown Oracle Web Cache: IP %s port %s.

Cause: The invalidation message was propagated from an unknown cache. Invalidation is discarded.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11732: Invalidation contains host name '%s' which does not match the IP '%s' from which invalidation comes.

Cause: The invalidation message propagated from a cache provided no host name or the host name in the URIPREFIX or HOST attribute was not allowed for that cache. Invalidation is discarded.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Correct the host information in the invalidation message.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11733: Invalidation object is ignored due to lack of host information.

Cause: Invalidation propagated from a cache does not specify a host name in the URIPREFIX or HOST attribute of the message.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Correct the host information in the invalidation message.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-11734: Invalidation sent to subscriber cache with IP %s port %d has returned with response code: '%s'.

Cause: The provider cache response was received.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-11735: Subscriber cache with IP %s port %d is removed due to an exceeded failure count. Total subscriber(s): %d.

Cause: Subscriber cache was removed from the internal subscriber list because the invalidation propagated to it has failed too many times.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-11736: Failed to start fiber to send invalidation to subscriber cache with IP %s port %d.

Cause: Oracle Web Cache failed to send invalidation. to subscriber cache.

Action: Check the configuration file. Restart Oracle Web Cache if necessary.
Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11737: Invalidation message may be lost from provider cache with IP %s port %d.

Cause: The subscriber cache missed an invalidation message from the provider cache. All objects are invalidated.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-11738: Provider cache fails in propagating invalidation message to subscriber cache.

Cause: The provider cache failed in propagating the invalidation message to subscriber cache.

Action: Check the configuration file. Restart Oracle Web Cache if necessary.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11740: Invalidation message contains too many cookies, headers, or attributes. Maximum allowed is '%d'.

Cause: Invalidation message contained too many cookies, headers, or attributes. Invalidation was not performed.

Action: Rephrase the invalidation message.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11748: Invalidation with INFO '%s' has returned with status '%s'; number of objects invalidated: '%d'.

Cause: The result of the invalidation was successful. INFO is the comment specified in the INFO element of the invalidation request. The status can be SUCCESS for successful invalidations, URI NOT CACHEABLE for objects that are not cacheable, or URI NOT FOUND for objects not found in the cache.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-11750: Invalid syntax for the value of QUERYSTRING_PARAMETER in invalidation message:'%s'.

Cause: The invalidation message contained invalid syntax in the QUERYSTRING_PARAMETER value.

Action: Correct the error in invalidation message.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11752: Cannot decode %s with value '%s', therefore decoding is not done.

Cause: Cannot decode XML value specified. The original value is used.

Action: No action required.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11754: Cannot allocate new XML context for invalidation.

Cause: Oracle Web Cache could not create XML context for invalidation.

Action: Check memory resources on the machine. Reinstall Oracle Web Cache if necessary.
Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11755: Default URL size is too small for cache key.

Cause: Default URL size was too small for cache key.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11757: Unsupported OTHER element specified in invalidation message: name='%s', type='%s', value='%s'.

Cause: Unsupported OTHER element was specified in the invalidation message.

Action: See Chapter "Sending Invalidation Requests" in the Oracle Web Cache Administrator's Guide for all supported OTHER elements.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11761: Site %.*s has no matching site definition and thus cannot be verified.

Cause: Response header invalidation failed because the site specified in the original request does not have a corresponding site definition with which to verify the invalidation response header.

Action: Create an appropriate site definition.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11762: Syntactically incorrect URI, '%.*s', specified in invalidation response header.

Cause: Response header invalidation failed because the URI in the invalidation response header was not syntactically valid.

Action: Change application to only append invalidation response headers with valid URIs.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11763: URI, '%.*s', specified in invalidation response header does not match incoming request's site definition.

Cause: Response header invalidation failed because the URI in the invalidation response header did not match the site specified in the original request.

Action: Change application to only append invalidation response headers whose site matches that of the incoming request.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11764: Unable to open connection to invalidation port of peer cache member \"%s\" because its state is not Ready.

Cause: The invalidation port of the peer cache member is not ready to accept connections.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11800: CGI communication error.

Cause: Network I/O error while communicating with CGI application.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11802: Cannot open Service Manager: %s

Cause: The admin server was unable open the Windows Service Manager.

Action: If the problem persists, contact Oracle Support.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11803: Cannot open Windows Service %s: %s

Cause: The admin server was unable to open the specified service.

Action: If the problem persists, contact Oracle Support.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11804: Cannot obtain the system status for Windows service %s: %s

Cause: The admin server was unable to retrieve the status for the specified service.

Action: If the problem persists, contact Oracle Support.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11805: Cannot control service %s: %s

Cause: The admin server was unable to start or stop the specified Windows service.

Action: If the problem persists, contact Oracle Support.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11806: Cannot stop service %s

Cause: The admin server failed to stop the specified service.

Action: If the problem persists, contact Oracle Support.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11807: Windows service, %s, stopped

Cause: The admin server has successfully stopped the specified service.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-11809: The admin server could not start the cache server, running in admin-only mode: %s

Cause: The admin server was unable to start the cache server.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Review the error log file or use the Event Viewer to help determine the cause of the problem.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11810: Cannot start Auto-Restart. %s does not exist

Cause: Unable to find the specified Auto-Restart executable.

Action: Restore the Auto-Restart executable, webcachemon, to its proper location, which is the Oracle Web Cache bin directory.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11811: Unable to fork a new process for starting Auto-Restart.

Cause: Oracle Web Cache was unable to fork a new process.

Action: This is probably a temporary system resource issue. If the problem persists, contact Oracle Support.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11812: Auto-Restart did not start. An error code was returned.

Cause: The Auto-Restart process failed to start.

Action: There may be associated error messages from the Auto-Restart process indicating why it was unable to start. If there are no other error messages, it may be a system resource problem. For example, the exec() call may have failed. If the problem persists, contact Oracle Support.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11813: Cannot start service %s

Cause: The admin server failed to start the specified service.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. If the problem persists, contact Oracle Support.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11814: Logging info: %s

Cause: An error is logged.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Refer to the logged error details and take the appropriate action.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11815: The admin server process is unable to determine the OPMN auto-restart setting. Error reading or parsing %s

Cause: An error occurred while the admin server process was attempting to obtain the restart setting for Oracle Web Cache in the OPMN XML configuration file, opmn.xml.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. If the problem persists, contact Oracle Support.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11816: Error while changing the OPMN auto-restart setting for Oracle Web Cache. Command: %s. Return code: %d. Command output: %s

Cause: An error occurred while trying to execute the command specified. Oracle Web Cache uses this command to change the restart setting in the OPMN XML configuration file, opmn.xml.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Execute the command manually.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11817: Unable to allocate or access a shared memory segment of size %u bytes. %s(): %s

Cause: The specified operating-system level function, which creates or accesses a shared memory segment of the size specified in the error message, has failed for the specified reason.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. This error usually occurs as a result of insufficient system resources. Refer to the included operating system level error message for further information.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11818: Login attempt fails to admin server process.

Cause: An incorrect username or password was entered while attempting to access the admin server process. If this error occurs frequently, a malicious user might be attempting to crack the password

Action: Try the username and password again.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11819: Unable to open temporary file %s

Cause: The admin server was unable to create a temporary file used during the processing of new configuration changes.

Action: No action required
Level: 1

Type: WARNING

Impact: Files

WXE-11901: SSL context creation failed, NZE-%d

Cause: SSL library failed to create a context.

Action: See the "Network Security Messages (NZE)" chapter of the Oracle Database Error Messages for information about NZE errors.
Level: 1

Type: ERROR

Impact: Security

WXE-11902: SSL configuration fails, NZE-%d

Cause: SSL library configuration failed.

Action: See the "Network Security Messages (NZE)" chapter of the Oracle Database Error Messages for information about NZE errors.
Level: 1

Type: WARNING

Impact: Security

WXE-11903: SSL set credential fails, NZE-%d

Cause: SSL library failed to set credentials.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. See the "Network Security Messages (NZE)" chapter of the Oracle Database Error Messages for information about NZE errors.
Level: 1

Type: WARNING

Impact: Security

WXE-11904: SSL handshake fails NZE-%d

Cause: SSL handshake error occurred.

Action: See the "Network Security Messages (NZE)" chapter of the Oracle Database Error Messages for information about NZE errors.
Level: 16

Type: ERROR

Impact: Security

WXE-11905: SSL additional information: %.*s

Cause: This message provides additional diagnostic information about the preceeding SSL error.

Action: No action required.
Level: 1

Type: WARNING

Impact: Security

WXE-11907: The server cannot allocate memory while in %s.

Cause: The system has run out of memory.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Restart the system and Oracle Web Cache.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11908: SSL set peerid fails, NZE-%d

Cause: SSL library failed to create SSL Session

Action: This message is no longer used as of Oracle Fusion Middleware 11g. See the "Network Security Messages (NZE)" chapter of the Oracle Database Error Messages for information about NZE errors.
Level: 1

Type: WARNING

Impact: Security

WXE-11909: getpeername fails during SSL handshake, system error %d

Cause: Could not determine peer IP Address.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Contact Oracle Support.
Level: 1

Type: WARNING

Impact: Security

WXE-11910: failed to normalize Wallet Resource Locator (WRL) %s

Cause: WRL could not be parsed.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Confirm that the WRL is in the correct format.
Level: 1

Type: WARNING

Impact: Security

WXE-11912: unknown state in SSL session garbage collector

Cause: There is an unknown code bug.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Contact Oracle Support.
Level: 8

Type: INTERNAL_ERROR

Impact: Security

WXE-11913: SSL set hardware acceleration fails, NZE-%d.

Cause: The SSL library failed to initialize hardware SSL acceleration.

Action: See the "Network Security Messages (NZE)" chapter of the Oracle Database Error Messages for information about NZE errors.
Level: 1

Type: ERROR

Impact: Security

WXE-11914: SSL set thread usage fails, NZE-%d.

Cause: The SSL library failed to set threading model.

Action: See the "Network Security Messages (NZE)" chapter of the Oracle Database Error Messages for information about NZE errors.
Level: 1

Type: WARNING

Impact: Security

WXE-11915: The SSL engine fails to initialize, NZE-%d.

Cause: The SSL library engine failed to initialize.

Action: See the "Network Security Messages (NZE)" chapter of the Oracle Database Error Messages for information about NZE errors.
Level: 1

Type: ERROR

Impact: Security

WXE-11916: Oracle cryptographic toolkit context initialization fails, NZE-%d.

Cause: The SSL library toolkit context failed to initialize.

Action: See the "Network Security Messages (NZE)" chapter of the Oracle Database Error Messages for information about NZE errors.
Level: 1

Type: WARNING

Impact: Security

WXE-11917: SSL wallet %s file %s does not exist.

Cause: The wallet was not found in the wallet directory.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Check for wallet file ewallet.p12 or ewallet.der in the wallet directory.
Level: 1

Type: WARNING

Impact: Security

WXE-11918: The SSL Wallet %s file %s is not readable.

Cause: The wallet was not readable by Oracle Web Cache.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Check the file system permissions on this file.
Level: 1

Type: WARNING

Impact: Security

WXE-11919: The SSL wallet auto-login file %s does not exist. Wallet does not appear to be auto-login wallet.

Cause: The wallet auto-login file cwallet.sso was not found.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Check for wallet file cwallet.sso in wallet directory.
Level: 1

Type: WARNING

Impact: Security

WXE-11920: The SSL wallet auto-login file %s is not readable. Wallet does not appear to be auto-login wallet.

Cause: The wallet auto-login file cwallet.sso was not readable by Oracle Web Cache.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Check the file system permissions on this file.
Level: 1

Type: WARNING

Impact: Security

WXE-11921: The origin server wallet did not open. Operating without wallet for backend. Only Diffie-Hellman anonymous connections supported to origin servers.

Cause: Origin server wallet did not open or was not specified.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Without an origin server wallet, only Diffie-Hellman SSL Connections can be made.
Level: 1

Type: WARNING

Impact: Security

WXE-11922: %s wallet fails to open at location %s, NZE-%d, as user %s

Cause: The wallet could not be opened as the user specified.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Check for the existence of the wallet and make sure auto-login was enables as the user specified.
Level: 1

Type: WARNING

Impact: Security

WXE-11923: %s wallet fails to open at location %s, NZE-%d.

Cause: The wallet could not be opened

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Check for the existence of the wallet.
Level: 1

Type: WARNING

Impact: Security

WXE-11924: Oracle wallet fails to open persona, NZE-%d.

Cause: The SSL library failed to retrieve certificate from wallet.

Action: See the "Network Security Messages (NZE)" chapter of the Oracle Database Error Messages for information about NZE errors.
Level: 1

Type: WARNING

Impact: Security

WXE-11925: No wallet configured with SSL; server initialization fails.

Cause: SSL was configured without specifying a wallet.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Correct the configuration file.
Level: 1

Type: ERROR

Impact: Security

WXE-11926: Oracle Web Cache fails to set cipher suite in SSL handshake, NZE-%d.

Cause: The SSL library failed to set the cipher suite.

Action: See the "Network Security Messages (NZE)" chapter of the Oracle Database Error Messages for information about NZE errors.
Level: 1

Type: WARNING

Impact: Security

WXE-11927: Oracle Web Cache fails to get supported cipher suites, NZE-%d.

Cause: The SSL library failed to get the supported cipher suites.

Action: See the "Network Security Messages (NZE)" chapter of the Oracle Database Error Messages for information about NZE errors.
Level: 1

Type: ERROR

Impact: Security

WXE-11928: Oracle Web Cache fails to set session reference, NZE-%d.

Cause: The SSL library failed to get the supported cipher suites.

Action: See the "Network Security Messages (NZE)" chapter of the Oracle Database Error Messages for information about NZE errors.
Level: 1

Type: ERROR

Impact: Security

WXE-11929: SSL handshake fails NZE-%s.

Cause: SSL handshake error occurred.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. See the "Network Security Messages (NZE)" chapter of the Oracle Database Error Messages for information about NZE errors.
Level: 1

Type: WARNING

Impact: Security

WXE-11930: The object is in the cache, but Single Sign-On authentication is required.

Cause: The cached object will be served to the client, but Single Sign-On authentication must be done before the document is served.

Action: No action required.
Level: 1

Type: TRACE

Impact: Security

WXE-11931: The object is in the cache, but the inactivity timeout cookie must be updated.

Cause: The cached object will be served to the client, but the global inactivity timeout cookie must first be updated.

Action: No action required.
Level: 1

Type: TRACE

Impact: Security

WXE-11932: The request has a Single Sign-On authentication cookie validated by Oracle Web Cache.

Cause: The Single Sign-On authentication cookie associated with the request has been validated by Oracle Web Cache.

Action: No action required.
Level: 1

Type: TRACE

Impact: Security

WXE-11933: The request has a Single Sign-On authentication cookie that needs to be validated by origin server.

Cause: The Single Sign-On authentication cookie associated with the request needs to be validated by the origin server.

Action: No action required.
Level: 1

Type: TRACE

Impact: Security

WXE-11934: The request has a global inactivity timeout cookie validated by Oracle Web Cache.

Cause: The global inactivity timeout cookie associated with the request has been validated by Oracle Web Cache.

Action: No action required.
Level: 1

Type: TRACE

Impact: Security

WXE-11935: The request has a global inactivity timeout cookie that needs to be validated by origin server.

Cause: The global inactivity timeout cookie associated with the request needs to be updated by the origin server.

Action: No action required.
Level: 1

Type: TRACE

Impact: Security

WXE-11936: Oracle Web Cache has started watching for %.*s Single Sign-On authentication cookie.

Cause: Oracle Web Cache has received new Single Sign-On authentication cookie name settings from origin server.

Action: No action required.
Level: 1

Type: TRACE

Impact: Security

WXE-11937: Oracle Web Cache has started watching for %.*s global inactivity timeout cookie.

Cause: Oracle Web Cache has received new global inactivity timeout cookie name settings from an origin server.

Action: No action required.
Level: 1

Type: TRACE

Impact: Security

WXE-11938: A new %s cookie with key %llx:%llx stored in memory for %d seconds.

Cause: Oracle Web Cache has temporarily stored the cookie in memory.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11939: The %s cookie with key %llx:%llx and reference count %d in memory has been marked stale.

Cause: The cookie stored in memory has been marked stale for garbage collection.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11940: The %s cookie with key %llx:%llx is being removed from memory.

Cause: The stale cookie stored in memory is being garbage collected.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11941: Oracle-WebCache-OSSO response header contains token \"%.*s\" with unexpected value \"%.*s\".

Cause: Oracle Web Cache has received a response that contains a malformed Oracle-WebCache-OSSO response header. It is possible that this Oracle Web Cache release is incompatible with the origin server.

Action: Ensure that the Oracle Web Cache version is compatible with that of the origin server
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11942: CRL is enabled without enabling client side certificate.

Cause: CRL is enabled on one of the listening endpoints, without requiring client side certificate.

Action: Ensure that client side certificate is required on the endpoint.
Level: 1

Type: ERROR

Impact: Security

WXE-11950: Internal XML parser error. Error code: %d. Error Message: %s

Cause: An internal error occurred while inside the XML parser. Oracle Web Cache will attempt to log that internal error.

Action: This error usually occurs due to malformed XML. Look up the associated error code in the Oracle XDK documentation.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11951: invalid value for ESI redirect attribute

Cause: The value specified for the redirect attribute by the <esi:include> tag was invalid.

Action: Set the value of the redirect attribute value to either yes" or "no" in the ESI template.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11952: Start processing ESI document %.*s%.*s, nesting level %d

Cause: Start processing of an ESI document (template or fragment).

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11953: In ESI template %.*s%.*s, the fragment's site name and URL has been discovered as %.*s and %.*s

Cause: Start processing of an ESI fragment.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11960: Oracle Web Cache is unable to decode the URI passed in: %s

Cause: URI decoding was unsuccessful, and it will be used as it is.

Action: No action required.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11962: Oracle Web Cache is unable to allocate enough memory to parse ESI vars tag string

Cause: There was not sufficient memory for Oracle Web Cache to parse the string in the ESI vars tag.

Action: Adjust the maximum cache size in the Resource Limits page of Fusion Middleware Control. If the problem persists, contact Oracle Support.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11963: Oracle Web Cache failed to create new ESI fragment request. Template uri: %.*s

Cause: ESI fragment request could not be generated. This error is generally a result of insufficient memory.

Action: Adjust the maximum cache size in the Resource Limits page of Fusion Middleware Control. If the problem persists, contact Oracle Support.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11964: empty variable key in ESI vars tag

Cause: The variable key specified in the ESI template by the ESI vars tag was empty."key" was missing from $(VARIABLE_NAME{key="value"}).

Action: Correct the format of the ESI vars tag.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11965: invalid variable name in ESI vars tag

Cause: The variable name specified in the ESI template by the ESI vars tag is not defined.

Action: See the Oracle Web Cache Administrator's Guide for valid ESI variable names.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11966: In %.*s%.*s, request header failed to be added to the include request.

Cause: There was not sufficient memory for Oracle Web Cache to include the request, or there was a request header parsing error.

Action: Adjust the maximum cache size in the Resource Limits page of Fusion Middleware Control. If the problem persists, contact Oracle Support.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11967: malformed request header when fetching %.*s%.*s.

Cause: This request header did not have a colon (:)and was malformed.

Action: If the problem persists, contact Oracle Support.
Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11968: ESI fragment request URI parsing error

Cause: There was an unexpected condition in parsing the URI in an ESI fragment.

Action: If the problem persists, contact Oracle Support.
Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11969: invalid ESI variable string type

Cause: Oracle Web Cache reached some invalid vars string type other than TEXT, VARIABLE, and CRLF.

Action: If the problem persists, contact Oracle Support.
Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11970: Cache key composition failed

Cause: Oracle Web Cache could not generate a cache key for an ESI fragment

Action: If the problem persists, contact Oracle Support.
Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11971: Oracle Web Cache attempted to return the $(QUERY_STRING) decoded

Cause: A $(QUERY_STRING) was requested to be returned in decoded format. $(QUERY_STRING) must be returned in encoded format.

Action: Contact Oracle Support.
Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11972: Template host header does not match UMD host header for Portal UMD request. template header: %.*s UMD header: %.*s

Cause: In an Oracle Portal environment, a UMD specification is most likely using an incorrect URL specification. This could cause errors to be reported in the browser.

Action: Contact Oracle Support.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11973: Site name cannot be resolved.

Cause: Requested site in ESI fragment request could not be resolved.

Action: Make sure that site name in the ESI request is correct.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11974: Incomplete URI for ESI fragment.

Cause: URI for ESI fragment only had "http://" and was considered incomplete.

Action: Make sure that the URL in the ESI request is complete.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11975: Corrupted login data in ESI environment metadata block.

Cause: The application delivered data that could not be parsed to Oracle Web Cache.

Action: Fix the application.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11976: Duplicate name %s in ESI environment metadata block.

Cause: The environment block contained multiple name entries.

Action: Remove the duplicate entries. Only the first entry is used.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11977: Memory allocation failure while initializing login metadata hash table.

Cause: The Oracle Web Cache memory manager could not allocate any more memory.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Adjust the maximum cache size in the Resource Limits page of Fusion Middleware Control.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11978: In ESI template %s%s, failed to add request header value.

Cause: Wrong request-header was specified.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Check the ESI template file and correct the error in request_header attribute.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11979: In ESI template %s%s, failed to add the request header because value is missing

Cause: Value field in the request-header was missing.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Check the ESI template file and correct the error in the request_header attribute
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11985: Oracle Web Cache is unable to obtain the size of the default ESI fragment page %s.

Cause: The default ESI fragment was not readable or did not exist in the $ORACLE_HOME/webcache/files on UNIX or ORACLE_HOME\\webcache\\files directory on Windows.

Action: Create a readable default ESI fragment in the $ORACLE_HOME/webcache/files on UNIX or ORACLE_HOME\\webcache\\files directory on Windows, and then configure it in the Error Page of Fusion Middleware Control.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11986: The default ESI fragment page %s is too large.

Cause: The default ESI fragment was too large.

Action: Alter the size of the default ESI fragment to less than 32 KB.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11987: Oracle Web Cache fails to open the default ESI fragment page %s.

Cause: The default ESI fragment was not readable or did not exist in the $ORACLE_HOME/webcache/files on UNIX or ORACLE_HOME\\webcache\\files directory on Windows.

Action: Create a readable default ESI fragment in the $ORACLE_HOME/webcache/files on UNIX or ORACLE_HOME\\webcache\\files directory on Windows, and then configure it in the Error Page of Fusion Middleware Control.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11989: read error while loading default ESI fragment page %s

Cause: The default ESI fragment was not readable or did not exist in the $ORACLE_HOME/webcache/files on UNIX or ORACLE_HOME\\webcache\\files directory on Windows.

Action: Create a readable default ESI fragment in the $ORACLE_HOME/webcache/files on UNIX or ORACLE_HOME\\webcache\\files directory on Windows, and then configure it in the Error Page of Fusion Middleware Control.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11997: ESI stack overflow

Cause: Current stack maximum depth was set too low.

Action: Contact Oracle Support about how to increase the maximum stack depth.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12001: ESI <esi:include> tag nesting in template %.*s%.*s is too deep.

Cause: The fragment <esi:include> depth exceeded the maximum include depth of three levels.

Action: Decrease the depth number in the ESI template, or contact Oracle Support to change the maximum <esi:include> depth.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-12002: Origin server busy exception in ESI template %.*s%.*s, fragment %.*s%.*s

Cause: The origin server was busy and could not accept the new request.

Action: Check the health status of the origin server. If needed, increase the origin server capacity in the Origin Servers page of Fusion Middleware Control.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-12003: No connection exception in ESI template %.*s%.*s, fragment %.*s%.*s

Cause: The cache was unable to connect to the origin server.

Action: Check the health status of the origin server. If needed, increase the origin server capacity in the Origin Servers page of Fusion Middleware Control.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-12004: Network timeout exception in ESI template %.*s%.*s, fragment %.*s%.*s

Cause: The request to origin server timed out during a network connection.

Action: Check the health status of the origin server. If needed, increase the origin server capacity in the Origin Servers page of Fusion Middleware Control.
Level: 1

Type: WARNING

Impact: Network

WXE-12005: HTTP Client Error 4xx exception in ESI template %.*s%.*s, fragment %.*s%.*s

Cause: The origin server returned an HTTP 4xx status code.

Action: Check for errors in the ESI template and fragment files.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-12006: HTTP Server Error 5xx exception in ESI template %.*s%.*s, fragment %.*s%.*s

Cause: The origin server returned an HTTP 5xx status code.

Action: Check for errors in the ESI template and fragment files. Additionally, check the health status of the origin server.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-12007: Incompatible fragment version exception in ESI template %.*s%.*s, fragment %.*s%.*s

Cause: The value for the content control directive in the Surrogate-Control response-header was not compatible between the ESI fragment and template.

Action: Correct the error in either the ESI template or fragment file.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-12008: Incorrect response header exception in ESI template %.*s%.*s, fragment %.*s%.*s

Cause: The response header of the ESI fragment caused an error.

Action: Correct the error in the ESI fragment.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-12009: Incorrect ESI fragment exception in ESI template %.*s%.*s, fragment %.*s%.*s

Cause: Oracle Web Cache was unable to parse the ESI fragment.

Action: Correct the error in the ESI fragment.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-12010: Incorrect XML Fragment exception in ESI template %.*s%.*s, fragment %.*s%.*s

Cause: Oracle Web Cache was unable to parse the XML fragment.

Action: Correct the error in the XML fragment.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-12011: Generic exception in ESI template %.*s%.*s, fragment %.*s%.*s

Cause: A generic ESI exception occurred.

Action: Check the template and fragment, and then correct the error.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-12012: No exception handler is defined in template %.*s%.*s:.

Cause: An uncaught ESI exception was detected. An error page is returned.

Action: Correct the syntax error in the ESI template.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12013: No resolved virtual host mapping was found for template.

Cause: A ESI template contained an unresolved virtual host mapping.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-12014: The cached ESI inline fragment is stale because the origin server was contacted for a fresh copy of the parent page which contains this ESI inline fragment.

Cause: Because the cached object is stale, Oracle Web Cache will use the new fresh copy of the inline fragment.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-12015: Non-fetchable inline fragment %.*s%.*s not found in cache or already expired, fetching template %.*s%.*s from origin server again.

Cause: Normal trace behavior.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-12081: ESI parsing error. Dumping ESI content:

Cause: ESI parsing error.

Action: For any syntax errors, correct the ESI syntax. For any non-syntax related error, contact Oracle Support Services.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12082: Oracle Web Cache cannot parse ESI due to insufficient memory

Cause: Oracle Web Cache ran out of memory while parsing ESI.

Action: Adjust the maximum cache size in the Resource Limits page of Fusion Middleware Control. If the problem persists, contact Oracle Support.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12083: ESI parser internal error at line %d: %s

Cause: An ESI tag closed too early or there was an internal error of the ESI parser.

Action: For any syntax errors, correct the ESI syntax. For any non-syntax related error, contact Oracle Support.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12084: JESI fragment preprocessing error

Cause: Preprocessing of JESI fragment failed.

Action: Contact Oracle Support.
Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-12085: ESI syntax error. Bad exception type at line %d.

Cause: An invalid token was encountered.

Action: Correct the error at the specified location in the ESI template.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12086: ESI syntax error. Unrecognized keyword %s is at line %d.

Cause: An invalid token was encountered.

Action: Correct the error at the specified location in the ESI template.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12087: Bad Location response header in ESI fragment response

Cause: A redirection response contained an invalid Location header.

Action: Make sure that the application Web server sends a valid Location header.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12088: ESI syntax error. The src attribute is missing at line %d.

Cause: The src attribute is required for the <esi:include> and <esi:environment> tags.

Action: Correct the error at the specified location in the ESI template.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12089: Syntax error. The name attribute is missing at line %d.

Cause: The name attribute is required for the <esi:inline> tag, <esi:environment> tag, and the request_header element.

Action: Include the name attribute at the specified location in the ESI template.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12090: ESI syntax error. Bad attribute value appears at line %d.

Cause: An invalid or empty value string was found.

Action: Correct the error at the specified location in the ESI template.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12091: ESI syntax error. Multiple ESI <esi:environment> tags appear in a single template at line %d

Cause: Multiple <esi:environment> tags in a single ESI template are not allowed.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Configure the ESI template with one <esi:environment> tag.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12092: ESI Syntax error. Multiple request_body elements appear at line %d.

Cause: Multiple request_body elements are not allowed in <esi:include> and <esi:environment> tags.

Action: Correct the error at the specified location in the ESI template.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12093: ESI syntax error. The max-age attribute is incorrectly formatted at line %d.

Cause: The max-age attribute is not in the format of: max-age="expiration_time[+removal_time]

Action: Correct the error at the specified location in the ESI template.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12094: ESI syntax error. String length exceeds maximum at line %d.

Cause: The string length exceeded the maximum limit.

Action: Contact Oracle Support to change the string length limit.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12095: ESI syntax error. A variable requires a key at line %d.

Cause: The specified variable requires a format of $(VARIABLE_NAME{key}).

Action: Include a key in the variable at the specified location in the ESI template.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12096: ESI syntax error. The POST request method requires an request_body at line %d.

Cause: The specified POST fragment did not have a request_body element.

Action: Include the request_body element at the specified location in the ESI template.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12097: ESI syntax error. The position of the <esi:environment> tag at line %d is invalid.

Cause: The <esi:environment> did not appear before any <esi:include> tags in the syntax. To use the custom variables specified by the <esi:environment> tag with other ESI tags, the <esi:environment> must be included before other <esi:include> tags.

Action: Correct the error at the specified location in the ESI template.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12098: ESI syntax error. The value of the fetchable attribute at line %d is invalid.

Cause: A value of yes or no are the only possible values for the fetchable attribute.

Action: Change the value to either yes or no at the specified location in the ESI template.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12099: ESI syntax error. The same attribute appears multiple times in an ESI element at line %d.

Cause: An attribute can appear only once within an ESI element.

Action: Correct the error at the specified location in ESI object.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12100: Exhausted process memory. Exiting process.

Cause: Memory usage is greater than the process' system memory allocation.

Action: Reduce the maximum cache size limit or increase the operating system's memory limit for the Oracle Web Cache process, if possible.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-12101: Maximum receive buffer size 2 MB reached.

Cause: Receive buffer size is bigger than 2 MB on Windows platforms.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Reduce receive buffer size to below 2 MB.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12102: Unable to locate memory block (%db). Oracle Web Cache extends cache size over maximum limit to %dMB.

Cause: Memory request was not fulfilled with existing process memory, even after forced garbage collection.

Action: 1. From http://web_cache_hostname:web_cache_stats_port, select review the Detailed Memory Statistics. If requesting block size for garbage collection is larger than object buffer size, then consider: a. Increase the object buffer size. Contact Oracle Support for further information. b. Increase the maximum cache size in the Resource page of Fusion Middleware Control. 2. If the problem persists, contact Oracle Support.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-12103: Unable to locate large memory block (%db). Oracle Web Cache extends cache size over maximum limit to %dMB.

Cause: Large block memory request was not satisfied with existing process memory, even after forced garbage collection.

Action: 1. From http://web_cache_hostname:web_cache_stats_port, select review the Detailed Memory Statistics. If requesting block size for garbage collection is larger than object buffer size, then consider: a. Increase the object buffer size. Contact Oracle Support for further information. b. Increase the maximum cache size in the Resource Limits page of Fusion Middleware Control.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-12104: Oracle Web Cache process has page faulted

Cause: The Oracle Web Cache process has caused a hard operating system memory page fault to occur. This may indicate the physical system is overloaded or there is insufficient physical memory for the specified cache size.

Action: Try decreasing the maximum cache size.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-12200: Cache memory allocation for the cluster configuration block failed.

Cause: Memory allocation failed.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12201: Cache memory allocation for the cluster member table failed.

Cause: Memory allocation failed.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12202: Cluster member DNS lookup problem

Cause: Could not resolve the IP address from the cluster member's host name.

Action: Check the Cluster Members and Properties page of Fusion Middleware Control to see if the host name is correctly listed.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-12203: Cluster member number %s owner slot allocation %s:%s

Cause: Normal trace behavior.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-12204: Add cluster member number %s

Cause: Normal notification behavior.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-12205: Remove cluster member number %s

Cause: Normal notification behavior.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-12206: Cluster member number %s already marked alive

Cause: The local cache tried to add the specified cluster member, but it was already marked as alive.

Action: No action required.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-12207: Cluster member number %s already marked dead

Cause: The local cache tried to remove the specified cluster member, but it was already marked as dead.

Action: No action required.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-12209: A %s node cluster successfully initialized

Cause: Normal notification behavior.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-12212: Cluster member %s - %s configuration is invalid.

Cause: The configuration file of the specified cluster member does not match the configuration of the local cache.

Action: Check that all cluster members have the same configuration file.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-12213: Cluster member %s - %s configuration is valid.

Cause: Normal notification behavior.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-12217: Cluster member count %s is larger than maximum allowed %s

Cause: There are more than the maximum number of cluster members. There cannot be more than 99 cluster members.

Action: Reduce the number of cluster members by removing some members in the Cluster Members and Properties page of Fusion Middleware Control.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12400: HTTP request-header exceeds configured maximum individual header size ( %s ). Client IP: %s

Cause: Oracle Web Cache received an HTTP request with an abnormally large header, indicating a possible denial-of-service attack.

Action: If the problem persists, you may need to increase the maximum individual header size in the Security page of Fusion Middleware Control.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12401: HTTP request-header exceeds configured maximum combined header size. Client IP: %s

Cause: Oracle Web Cache received an HTTP request with an abnormally large header, indicating a possible denial-of-service attack.

Action: If the problem persists, you may need to increase the maximum combined header size in the Security page of Fusion Middleware Control.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12402: HTTP response-header parsing error: %.*s.

Cause: An HTTP response from the origin server contained a header or an individual header value that was malformed or unexpected.

Action: If the behavior is still as expected, no action is required. If the behavior is not as expected, check the application code which generates the specified header.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12403: HTTP response-header parsing error: %s ( %s ).

Cause: An HTTP response from the origin server contained a malformed header or an individual header value that was malformed or unexpected.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12404: The number of search keys exceeds the maximum limit of search keys in the Surrogate-Key response-header.

Cause: The number of search keys in the Surrogate-Key response-header exceeded the allowed configurable maximum defined in configuration file.

Action: Revise the Surrogate-Key response-header with configured maximum or fewer search keys.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-12405: Illegal time format in HTTP response-header.

Cause: HTTP response-header contains an illegal time format.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-12408: Unexpectedly large HTTP response-header.

Cause: An unexpectedly large response-header was received from the origin server, indicating a possible performance problem.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Contact Oracle Support.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-12409: Timeout while reading HTTP response.

Cause: No timely response received from the origin server, indicating that the origin server is down.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Start origin server, if it is not running.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12410: Error while reading HTTP response ( SSL error %d ).

Cause: Oracle Web Cache encountered an SSL read error.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. If the problem persists, contact Oracle Support.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12411: Non-parseable HTTP request-header line - questionable token syntax. Client IP: %s

Cause: An HTTP request from a browser contained a line with a token value containing either an unpaired parenthesis ( ( or ) ) or an unpaired double-quote ("). For example: Cookie: name="John Hancock

Action: No action required.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12412: HTTP request-header parsing error - malformed request line. Client IP: %s

Cause: An HTTP request from a browser contained a malformed request line; it contained either an unknown method name or an illegal version string.

Action: No action required.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12413: Unable to get Oracle name of ESI template character set ( %.*s ).

Cause: A recoverable internal error occurred while doing character set conversion.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-12414: Unable to get Oracle name of ESI fragment character set ( %.*s ).

Cause: A recoverable internal error occurred while doing character set conversion.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-12415: Unable to do character set conversion.

Cause: Internal error. A system/library call has unexpectedly failed.

Action: If the problem persists, contact Oracle Support.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-12416: NLS library failure while doing character set conversion.

Cause: Internal error. A system/library call has unexpectedly failed.

Action: If the problem persists, contact Oracle Support.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-12417: HTTP request-header parsing error - no header name. Client IP: %s

Cause: An HTTP request from a browser contained a malformed header line; the header name delimiting colon (':') was not present.

Action: No action required.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12419: Dump of offending HTTP request-header line:

Cause: Any of the causes associated with errors 12411, 12412 and 12417.

Action: No action required.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12420: The number of search keys exceeds the maximum hard limit of search keys in the Surrogate-Key response-header thus excessive search keys are discarded.

Cause: The number of search keys in the Surrogate-Key response-header exceeded the allowed hard maximum of 200.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Revise the Surrogate-Key response-header with 200 or fewer search keys.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12421: HTTP request is invalid due to a duplicate header occurrence: \"%.*s\". Client IP: %s

Cause: An HTTP request from a browser contained multiple occurrences of the same header type.

Action: No action required.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12422: Duplicate header occurrence(\"%.*s\") is in HTTP request.

Cause: An HTTP request from a browser contained multiple occurrences of the same header type.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-12423: Response ETag header has no value possibly indicating an application server problem. This message is only printed once per cache process.

Cause: The response contains a NULL or empty string ETag header. This could be a problem with the application server

Action: No action required.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-12424: Ignoring unrecognized token \"%.*s\" in Oracle-WebCache-OSSO response header.

Cause: Oracle Web Cache has received a response from origin server that contains a token in Oracle-WebCache-OSSO header that is not recognized by Oracle Web Cache.

Action: Ensure that the Oracle Web Cache version is compatible with that of the origin server
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-12425: Malformed invalidation capability request header (\"%.*s\") in HTTP request.

Cause: An HTTP request from a browser contained a malformed invalidation capability request header.

Action: No action required.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-12700: Site %.*s did not match any defined sites, resulting in no End User Performance Monitoring for URI

Cause: Normal trace behavior.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-12701: Site %.*s matched one of the defined sites for which End User Performance Monitoring is ON.

Cause: Normal trace behavior.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-12702: Site %.*s matched a defined site with End User Performance Monitoring OFF, resulting in no End User Performance Monitoring for URI

Cause: Normal trace behavior.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-12703: No matching End User Performance Monitoring rule found for site %.*s, resulting in End User Performance Monitoring for URI.

Cause: Normal trace behavior.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-12704: There are no End User Performance Monitoring rules defined for site %.*s, resulting in End User Performance Monitoring for URI.

Cause: Normal trace behavior.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-12705: Matching End User Performance Monitoring REGEXP rule found regexp:%s and the rule is %s

Cause: Normal trace behavior. Matching End User Performance Monitoring rule found. The rule determines whether or not to monitor End User Performance for the URI.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-12706: Matching End User Performance Monitoring SUBSTRING rule found. substring:%s and the rule is %s

Cause: Normal trace behavior. Matching End User Performance Monitoring rule found. The rule determines whether or not to monitor End User Performance for the URI.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-12712: OEMPERFFILE can only be set to an .html file.

Cause: The file specified by OEMPERFFILE must be an .html file, but it was not.

Action: Contact Oracle Support for help in specifying the correct OEMPERFFILE.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12713: OEMPERFFILE cannot be parsed. Use the following format: <SCRIPT SRC=\"%schronos_JavaScript_filename\"></SCRIPT> and restart Oracle Web Cache.

Cause: OEMPERFFILE could not be parsed.

Action: Use the following format for the value of OEMPERFFILE: <SCRIPT SRC=\"%schronos_JavaScript_filename\"></SCRIPT>. Then, restart Oracle Web Cache.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12714: Invalid string specified for OEMPERFFILE.

Cause: The file name specified by OEMPERFFILE is an invalid string.

Action: Contact Oracle Support for help in specifying the correct OEMPERFFILE.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12715: OEMPERFFILE contains an invalid path separator.

Cause: The file name specified for OEMPERFFILE contains an invalid path separator.

Action: Correct the file name specified for OEMPERFFILE.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12716: End-User Performance Monitoring is enabled.

Cause: Normal notification behavior. End-User Performance Monitoring is enabled. The event is written to the log file.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-12800: Oracle Web Cache fails to read the configuration file. Dynamic changes have not been applied.

Cause: Normal trace behavior.

Action: No action required.
Level: 1

Type: TRACE

Impact: Configuration

WXE-12801: Dynamic Changes Applied Successfully

Cause: Normal trace behavior.

Action: No action required.
Level: 1

Type: TRACE

Impact: Configuration

WXE-12802: The cache server cannot dynamically mark the origin servers as running because they are not responding. Other selected dynamic changes are applied.

Cause: The origin servers were not responding. The cache server disregarded this dynamic change, but applied other dynamic changes.

Action: No action required.
Level: 1

Type: TRACE

Impact: Configuration

WXE-12803: Dynamic Changes Not Applied

Cause: Normal trace behavior.

Action: No action required.
Level: 1

Type: TRACE

Impact: Configuration

WXE-12804: Event Log rolled over.

Cause: Normal trace behavior.

Action: No action required.
Level: 1

Type: TRACE

Impact: Logging

WXE-12805: Access log %s rolls over.

Cause: Access log rolled over as a result of an on-demand rollover request.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Logging

WXE-12806: Non-existent access log %s specified in rollover request.

Cause: On-demand rollover request was submitted with an invalid access log name.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Logging

WXE-12807: Event log not rolled over because the rollover file already exists.

Cause: Normal trace behavior.

Action: No action required.
Level: 1

Type: TRACE

Impact: Logging

WXE-12808: Access Log %s not rolled over because the rollover file already exists.

Cause: Access Log is rolled over as a result of on-demand rollover request.

Action: Submit another rollover request after more than one minute.
Level: 1

Type: NOTIFICATION

Impact: Logging

WXE-12809: Could not find the matching Origin Server entry in original configuration which the cache server is running with.

Cause: Normal trace behavior.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-12810: ESI fragment log for access log %s is not rolled over.

Cause: Regular access log was rolled over due to an on-demand rollover request, but accompanying ESI fragment log was not rolled over for some reason.

Action: Submit another rollover request after one minute.
Level: 1

Type: NOTIFICATION

Impact: Logging

WXE-12811: Dynamic event log rollover fails because the event log file does not exist.

Cause: Dynamic event log rollover failed because Oracle Web Cache failed to create the event log file at startup time.

Action: Review the event log file name specified in configuration.
Level: 1

Type: ERROR

Impact: Logging

WXE-12812: Dynamic event log rollover fails because the event log file could not be renamed.

Cause: Dynamic event log rollover failed because Oracle Web Cache could not rename the file.

Action: Check the permissions of the event log file or if any other application is using the event log file.
Level: 1

Type: ERROR

Impact: Logging

WXE-12813: Access log name is not specified in rollover request.

Cause: On-demand access log rollover request did not contain the access log name.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Logging

WXE-12814: ***** Request message notification begin *****

Cause: Request-specific event_log messages.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Logging

WXE-12815: ***** Request message notification complete *****

Cause: Request-specific event_log messages.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Logging

WXE-12817: Directory %s size reduced from %dMB to rollover criteria %dMB

Cause: The specified logfile was automatically purged because the directory exceeded the maximum size threshold designated in the configuration.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Logging

WXE-12818: Logfile %s (size %dMB) deleted due to rollover criteria (%dMB)

Cause: The specified logfile was automatically purged because the directory exceeded the maximum size threshold designated in the configuration.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Logging

WXE-12819: event_log reverted to old-style logging with WCDEBUG enabled

Cause: When the event_log is configured using the MODE="NEW" attribute (the default configuration), but the WCDEBUG feature is enabled, the logging sub-system must revert to the MODE="OLD" configuration.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Logging

WXE-12820: Logfile %s (size %dMB) deleted due to time-based retention criteria

Cause: The specified logfile was automatically purged because the directory exceeded the maximum retention period designated in the configuration.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Logging

WXE-12822: Oracle Web Cache fails to rename file from %.*s to %.*s (%s)

Cause: Dynamic event log rollover failed because Oracle Web Cache could not rename the file.

Action: Check the permissions of the event log file and if another application is using the event log file.
Level: 1

Type: TRACE

Impact: Logging

WXE-12900: Oracle Web Cache fails to read the final byte ('X') from Oracle Web Conferencing client; redirect fails.

Cause: Oracle Web Conferencing client did not send the character X to mark request end

Action: No action required.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12901: Oracle Web Cache fails to send the message to the Oracle Web Conferencing client; redirect fails.

Cause: Oracle Web Cache could not send Oracle Web Conferencing protocol message to client.

Action: No action required.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12902: The mx list is empty in the Oracle Web Conferencing path %s.

Cause: The configured mx path set was incorrect.

Action: Configure the correct mx path.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-12903: The Oracle Web Conferencing pass descriptor fails; Error: %s.

Cause: Oracle Web Cache was unable to pass descriptor to the mx server.

Action: Check the mx server configuration and log files.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12904: Oracle Web Conferencing redirect did not occur for mx path = %s.

Cause: Oracle Web Cache was not able to pass descriptor to the mx server on any of the mx server ports.

Action: Check the mx server configuration and log files.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12905: Oracle Web Conferencing redirect is successful.

Cause: Normal trace behavior.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-12906: The Windows socket could not be set to blocking; Error: %s.

Cause: The error was caused the by the error printed in the message.

Action: Debug from the error printed in the message.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12907: The Oracle Web Conferencing URL is not valid.

Cause: The URL received by webcache is invalid.

Action: Check the Oracle Web Conferencing configuration.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12908: The Oracle Web Conferencing pass descriptor is successful.

Cause: Normal trace behavior.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-13001: Virtual Host Map %s has a mixture of HTTP and HTTPS Protocol origin servers. All origin servers for a virtual host map must use the same protocol.

Cause: The specified virtual host map consists of origin servers with HTTP and HTTPS protocols. A virtual host mapping must consist of origin servers that use either the HTTP protocol exclusively or the HTTPS protocol exclusively.

Action: From the Sites page of Fusion Middleware Control, correct the mapping. Then, restart Oracle Web Cache.
Level: 1

Type: ERROR

Impact: Configuration

WXE-13002: Maximum allowed incoming connections are %u

Cause: Normal notification behavior indicating the maximum number of concurrent connections which will be accepted.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

WXE-13003: Configuration error. Stopping admin or cache server.

Cause: The admin or cache server was unable to parse or read its configuration information.

Action: Review any other error messages to determine the cause of the problem.
Level: 1

Type: ERROR

Impact: Configuration

WXE-13005: The session definition for the session \"%s\" is missing but used in the WTI session key configuration for server \"%s\".

Cause: A non-existent session definition is referenced by its name in WTI session key configuration in the configuration file.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Modify the configuration to either add the session definition or used another existing definition.
Level: 16

Type: ERROR

Impact: Configuration

WXE-13006: The session inactivity timeout for the session \"%s\" is missing but required in the WTI session key configuration for server \"%s\".

Cause: The session used for WTI session key does not have an inactivity timeout defined.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. A WTI session key is used for security purposes. It is based on a user session which should have an inactivity timeout. Please add the inactivity timeout to the session definition for this session.
Level: 16

Type: ERROR

Impact: Configuration

WXE-13007: The specified listening IP address \"%s\" is not valid.

Cause: The specified listening IP address was not valid 32-bit dotted decimal notation, resolvable host name, ANY, or asterisk (*).

Action: 1. Check if the specified listening address is configured as a valid 32-bit numeric address written as four numbers separated by dots. Oracle Enterprise Manager permits * permits ANY to support all IP addresses. 2. If you need to specify host name instead of an IP address, check if the host name can be resolved to an IP address on your system. 3. If you need to rely on DNS to resolve the host name, check if DNS is correctly working.
Level: 1

Type: ERROR

Impact: Configuration

WXE-13008: CRL is enabled for listen port %s but no CRL file or path is specified.

Cause: Both port specific and global settings of SSLCRLPATH and SSLCRLFILE are NIL but SSLCRLENABLE is set to "YES

Action: Modify the configuration to either specify a valid SSLCRLPATH and SSLCRLFILE or disable CRL checking.
Level: 1

Type: ERROR

Impact: Configuration

WXE-13009: CRL is enabled for listen port %s without enabling client side certificate.

Cause: CLIENT_CERT must be set to "YES" or "OPTIONAL" when SSLCRLENABLE is set to "YES".

Action: Modify the configuration and correct CLIENT_CERT setting or disable CRL checking.
Level: 1

Type: ERROR

Impact: Configuration

WXE-13010: MAXLOGSIZE (%d) cannot be larger than MAXREPSIZE (%d)

Cause: The maximum logfile rollover size specified by the MAXLOGSIZE parameter is larger than the repository rollover size specified by the MAXREPSIZE configuration parameter.

Action: Reduce the size specified by the MAXLOGSIZE configuration parameter, or increase the size specified by the MAXREPSIZE parameter.
Level: 1

Type: ERROR

Impact: Configuration

WXE-13011: Invalid tweak parameter \"%s\" value \"%s\"

Cause: The specified tweak parameter contains an unknown or invalid value.

Action: Check the documentation for the set of valid values for the specified tweak parameter.
Level: 1

Type: ERROR

Impact: Configuration

WXE-13050: Multiple access logs use the same file name: %s

Cause: Multiple access logs were configured to use the same output file name. The output file name cannot be shared by multiple access logs.

Action: Ensure that the ACCESSLOG element in the webcache.xml file has a unique FILENAME attribute.
Level: 1

Type: ERROR

Impact: Configuration

WXE-13051: List of IP addresses only valid for ALLOW=\"LIST_OF_IPS\" option

Cause: The specified secure subnet IP address(es) can only be supplied when the ALLOW="LIST_OF_IPS" attribute is specified for the SECURESUBNET element.

Action: Remove the list of IP addresses, or change the ALLOW attribute to the value "LIST_OF_IPS".
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-13052: Cache attribute INSTANCENAME %s does not match environment variable INSTANCE_NAME %s.

Cause: The instance name specified in configuration file is wrong.

Action: This does not affect Web Cache from starting up since runtime Web Cache do not make use of this attribute. This attribute is used by the Enterprise Manager to find the correct CACHE element.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-13074: A session caching rule refers to an invalid session name: %s

Cause: The session caching rule specifies a session ID which is not defined. This error usually occurs if webcache.xml has been edited manually instead of by using Fusion Middleware Control.

Action: Edit webcache.xml and set the session ID to a valid session definition.
Level: 1

Type: ERROR

Impact: Configuration

WXE-13075: A session binding rule refers to an invalid session name: %s

Cause: A session binding rule specified a session ID which was not defined. This error usually occurs if webcache.xml has been edited manually instead of by using Fusion Middleware Control.

Action: Edit webcache.xml and correct the session definition for the specified session ID.
Level: 1

Type: ERROR

Impact: Configuration

WXE-13076: A caching rule refers to an invalid expiration rule: %s

Cause: One of the caching rules contained the specified expiration rule. That expiration rule was invalid. This error usually occurs if webcache.xml has been edited manually instead of by using Fusion Middleware Control.

Action: Edit webcache.xml and find the specified expiration rule and replace it with a valid expiration rule.
Level: 1

Type: ERROR

Impact: Configuration

WXE-13077: A caching rule refers to an invalid multi-version cookie rule: %s

Cause: One of the caching rules contained the specified invalid multi-version cookie rule. This error usually occurs if webcache.xml has been edited manually instead of by using Fusion Middleware Control.

Action: Edit webcache.xml and find the multi-version cookie rule listed in the error message. Replace the rule with a valid one.
Level: 1

Type: ERROR

Impact: Configuration

WXE-13078: A caching rule refers to an invalid session rule: %s

Cause: One of the caching rules contained the specified invalid session rule. This error usually occurs if webcache.xml has been edited manually instead of by using Fusion Middleware Control.

Action: Edit webcache.xml and find the specified session rule. Replace the rule with a valid one.
Level: 1

Type: ERROR

Impact: Configuration

WXE-13079: Oracle Web Cache did not find a matching CACHE element in webcache.xml for the current host name (%s) and Oracle home (%s).

Cause: Oracle Web Cache was unable to find a CACHE element for this cache.The configuration file may be in error.

Action: Contact Oracle Support to fix the configuration file.
Level: 1

Type: ERROR

Impact: Configuration

WXE-13080: No NAME attribute is specified in ROLLOVER element under ACCESSLOGSTYLES

Cause: Unable to find a NAME attribute in ROLLOVER element for access logs. The ROLLOVER element for access logs must have a NAME attribute.

Action: Edit webcache.xml and find the ROLLOVER element under ACCESSLOGSTYLES which does not have NAME attribute. Add the NAME attribute to the ROLLOVER element.
Level: 1

Type: ERROR

Impact: Configuration

WXE-13081: Any Set-Cookie is not configured with the a session binding mechanism other than Cookie-based.

Cause: A session binding rule specifying a session of Any Set-Cookie was not configured with the Cookie-based session binding mechanism. Any Set-Cookie cannot use a mechanism of OC4J-based or Internal-Tracking.

Action: Change the session binding mechanism to Cookie-based.
Level: 1

Type: ERROR

Impact: Configuration

WXE-13082: Duplicate CACHE element found in webcache.xml for current instance name (%s), component name (%s), hostname (%s) and ORACLE_HOME (%s)

Cause: Identified a duplicate CACHE element for this cache.

Action: Check that the hostname and ORACLE_HOME printed in the error message match the expected values and check the CACHE elements in webcache.xml for one which is defined for these values.
Level: 1

Type: ERROR

Impact: Configuration

WXE-13106: Log file rollover schedule refers to an invalid TIME value for the HOURLY frequency: %u

Cause: Time value specified for the HOURLY frequency was invalid.

Action: TIME must be set to a nonzero positive integer value less than 60.
Level: 1

Type: ERROR

Impact: Configuration

WXE-13107: Log file rollover schedule refers to an invalid TIME value for the DAILY frequency: %u

Cause: Time value specified for the DAILY frequency was invalid.

Action: For DAILY rollover, the time format is "hhmm", where hh ranges from 0 to 23 and mm ranges from 0 to 59.
Level: 1

Type: ERROR

Impact: Configuration

WXE-13108: Log file rollover schedule refers to an invalid TIME value for the WEEKLY frequency: %u

Cause: Time value specified for the WEEKLY frequency was invalid.

Action: For WEEKLY rollover, the time format is "dhhmm", where "d" ranges from 0 to 6, "hh" ranges from 0 to 23 and mm ranges from 0 to 59.
Level: 1

Type: ERROR

Impact: Configuration

WXE-13109: XML parsing error in %s. Error code %u: %s

Cause: The specified XML file did not match the DTD for the file.

Action: See the related Oracle XML library error message for more details.
Level: 1

Type: ERROR

Impact: Configuration

WXE-13110: XML parser initialization error. Error code: %u

Cause: Unable to initialize the XML parser.

Action: If the problem persists, contact Oracle Support.
Level: 1

Type: ERROR

Impact: Configuration

WXE-13111: XML parsing failed for file: %s. Error Code: %u

Cause: An XML parsing error occurred when parsing the specified file.

Action: Review associated error messages for more information about the problem.
Level: 1

Type: ERROR

Impact: Configuration

WXE-13112: XML parsing failed. Error Code: %u

Cause: Failed to parse an XML message.

Action: Review associated error messages for more information about the problem.
Level: 16

Type: ERROR

Impact: Configuration

WXE-13113: Syntax error in %s. Exception: \"%s\" in attribute \"%s\" having value \"%s\" in element %s

Cause: An exception occurred while parsing the specified file.

Action: Edit the specified file to make it a valid XML object.
Level: 16

Type: ERROR

Impact: Configuration

WXE-13114: A root directory mapping must be specified before all other mappings

Cause: This error may have occurred if the internal configuration has been changed.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Contact Oracle Support.
Level: 16

Type: ERROR

Impact: Configuration

WXE-13115: Out of memory error while scanning object root

Cause: The process ran out of memory while scanning for objects in the object root.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. If the problem persists, contact Oracle Support.
Level: 1

Type: ERROR

Impact: Memory

WXE-13116: An error occurred scanning the directory %s

Cause: Oracle Web Cache was unable to get the contents of the specified directory.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. If the problem persists, contact Oracle Support.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-13117: Failed to add MIME type extension to pool: %s

Cause: An error occurred while processing the MIME type extensions settings.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. If the problem persists, contact Oracle Support.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-13118: Out of memory error while initializing MIME type information

Cause: An error occurred while processing the MIME type extensions settings.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. If the problem persists, contact Oracle Support.
Level: 16

Type: ERROR

Impact: Memory

WXE-13119: Duplicate origin server hosts specified for host %s port %s.

Cause: There are duplicate entries in the HOST section of the webcache.xml file.

Action: Remove the duplicate entries from webcache.xml.
Level: 16

Type: ERROR

Impact: Configuration

WXE-13120: CACHEWITH and CACHEWITHOUT cannot both have the value \"NO\" in a session caching policy for session %s.

Cause: The session caching policy has a value of "NO" for both CACHEWITH and CACHEWITHOUT in webcache.xml.

Action: Set at least one of them to be "YES", or remove the policy.
Level: 16

Type: ERROR

Impact: Configuration

WXE-13121: The caching rule for %s contains more than one multi-version cookie policy based on the same cookie: %s.

Cause: More than one multi-version cookie policy is associated for the same cookie with one caching rule.

Action: Remove the extra policies from the caching rule.
Level: 16

Type: ERROR

Impact: Configuration

WXE-13122: The caching rule for %s contains more than one session-caching policy based on the same session: %s.

Cause: More than one session caching policy is associated for the same session with one caching rule.

Action: Remove extra policies from the caching rule.
Level: 16

Type: ERROR

Impact: Configuration

WXE-13123: Site name %s:%s%s exceeds maximum individual header limit.

Cause: The site name was set to more than the maximum single header limit as defined in the security section.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Increase the maximum individual header size limit in the Security page of Fusion Middleware Control, so that the site name and port number string together is less than the specified limit.
Level: 16

Type: ERROR

Impact: Configuration

WXE-13124: Alias name %s:%s%s exceeds maximum individual header limit %d.

Cause: The alias name was set to more than maximum individual header limit as defined in the security section.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Increase the maximum individual header size limit in the Security page of Fusion Middleware Control or change the alias name in the Sites page of Fusion Middleware Control, so that the alias name and port number string together is less than the specified limit.
Level: 16

Type: ERROR

Impact: Configuration

WXE-13125: internal.xml does not have CALYPSOINTERNALPARAMS element.

Cause: Unable to find CALYPSOINTERNALPARAMS element in internal.xml.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Check whether internal.xml conforms to internal.dtd.
Level: 16

Type: ERROR

Impact: Configuration

WXE-13127: Oracle XML Schema processor failed to initialize%s.

Cause: Oracle XML Schema Processor failed to initialize.

Action: If the problem persists, contact Oracle Support.
Level: 16

Type: ERROR

Impact: Configuration

WXE-13128: XML file%s did not pass validation against schema checking%s.

Cause: Error occurs in validating the XML file against its corresponding XML schema

Action: Fix the error accordingly in the XML file
Level: 16

Type: ERROR

Impact: Configuration

WXE-13129: Setting internal tweak parameter '%s' value to '%s'.

Cause: Tweak mechanism was used to change the specified internal tweak parameter to the stated new value. This occurs only at startup.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

WXE-13130: Ignoring internal tweak parameter '%s'; value '%s' is illegal

Cause: Tweak mechanism can be used to change the specified internal tweak parameter's value, but only if the value is legal for that parameter. This occurs only at startup.

Action: Specify a legal value (please contact Oracle Support) and try again.
Level: 1

Type: WARNING

Impact: Configuration

WXE-13131: Ignoring unknown internal tweak parameter '%s'.

Cause: An attempt was made to use the tweak mechanism for an unknown internal tweak parameter. Because the parameter name was unknown, its value was ignored.

Action: Fix the name to be a legitimate internal tweak parameter (please contact Oracle Support) and try again.
Level: 1

Type: WARNING

Impact: Configuration

WXE-13132: Invalid logfile retention specified: %d %s

Cause: The specified logfile retention period is invalid. This problem can occur is the frequency definition is incorrectly spelled.

Action: Verify that the retention period count and frequency are correct.
Level: 16

Type: ERROR

Impact: Configuration

WXE-13133: Host 'name' is required

Cause: The 'name' attribute of the 'host' element was not specified, or was specified as an empty value.

Action: Specify a unique host name.
Level: 16

Type: ERROR

Impact: Configuration

WXE-13134: Oracle Web Cache did not find a matching CACHE element in webcache.xml for the current host name (%s), Oracle instance (%s) and system component name (%s).

Cause: Oracle Web Cache was unable to find a CACHE element for this cache.The configuration file may be in error.

Action: Contact Oracle Support to fix the configuration file.
Level: 1

Type: ERROR

Impact: Configuration

WXE-13200: Access logging was skipped as the request had not been parsed properly.

Cause: Due to an error in request parsing, access logging could not be completed.

Action: No action required.
Level: 16

Type: ERROR

Impact: Configuration

WXE-13212: Access log file %s could not be opened.

Cause: Access log file could not be opened.

Action: Check the status of access log file. For example, check the permission of the file.
Level: 1

Type: ERROR

Impact: Logging

WXE-13213: Invalid access log field name: %s

Cause: An invalid access log field is specified in the configuration file webcache.xml.

Action: Set valid access log field name.
Level: 1

Type: ERROR

Impact: Logging

WXE-13215: I/O Error when writing access Log buffer to file. error number: %d

Cause: I/O error happened when Oracle Web Cache tried to write to the access log file.

Action: Check the status of access log file. For example, see if the disk is full.
Level: 1

Type: ERROR

Impact: Logging

WXE-13250: Search key configuration error

Cause: Invalid Oracle Web Cache configuration for search key.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Contact Oracle Support.
Level: 1

Type: ERROR

Impact: Configuration

WXE-13251: The HTML file for End-User Monitoring was not found

Cause: End-User Monitoring configuration error.

Action: Disable End-User Monitoring or restore the HTML file that is missing. If the problem persists, contact Oracle Support.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-13252: On Demand Log File Rollover for file %s was not successful. File %s could not be created.

Cause: The rollover file could not be created.

Action: Check the file permissions.
Level: 1

Type: WARNING

Impact: Logging

WXE-13301: A failure occurred with DNS lookups. No more DNS lookups will occur.

Cause: The DNS server might be unavailable.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Check the DNS configuration on the local machine.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-13302: Failed to open directory: %s

Cause: Directory could not be opened because it does not exist or the access permissions are incorrect.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Check the configuration and the permissions for accessing the directory.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-13305: Failed to assign port %s: %s

Cause: The selected port is being used by another application.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Change the port to an unused port.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-13306: Failed to configure resources for port %s: %s

Cause: System listen function call failed.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Restart Oracle Web Cache. If the problem persists, contact Oracle Support.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-13307: Failed to allocate resources for port %s: %s

Cause: Socket creation failed.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. If the problem persists, Restart Oracle Web Cache and check open file descriptors.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-13308: Failed to listen on port %s: %s

Cause: Generally occurs when the port is in use by another application.

Action: Change the port to an unused port. Restart Oracle Web Cache. If the problem persists, contact Oracle Support.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-13309: Listening on port %s

Cause: Generally occurs when the port is in use by another application.

Action: Change the port to an unused port. Restart Oracle Web Cache. If the problem persists, contact Oracle Support.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-13310: Problem opening file %s (Access Denied).

Cause: The file could not be opened because of an access problem.

Action: Fix the file permissions so that the user running webcached can access the file.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-13312: Problem creating file %s (File Already Exists).

Cause: The file could not be created because it already exists.

Action: Choose a file name that does not exist.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-13313: Problem opening file %s (Invalid Drive).

Cause: The file could not be opened because the drive name is invalid.

Action: Correct the file specification.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-13314: Problem opening file %s (Invalid Name).

Cause: The file could not be opened because the file name is invalid.

Action: Correct the file specification.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-13315: Problem opening file %s (Too Many Open Files).

Cause: The file could not be opened because there are too many open files in the system.

Action: Close other files or programs and restart Oracle Web Cache.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-13316: Problem opening file %s (File Not Found).

Cause: The file could not be opened because the file could not be found.

Action: Correct the file specification.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-13317: Problem opening file %s (Sharing violation).

Cause: The file could not be opened because there has been a sharing violation.

Action: Close the file through other applications that are accessing it.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-13318: Problem opening file %s (Is a directory).

Cause: The file could not be opened because it is directory.

Action: Correct the file specification.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-13319: Problem opening file %s, system error %s (Internal error).

Cause: There was been an unknown error opening the file.

Action: Contact Oracle Support.
Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-13350: Error during network receive, system error %s

Cause: There was system error during the networking receive.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-13351: Timeout during network receive, socket number %s

Cause: There was timeout during the networking receive.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-13365: Error during network send, system error %s

Cause: There was system error during the networking send.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-13366: Timeout during network send, socket number %s

Cause: There was timeout during the networking send.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-13380: Error during SSL handshake, system error %s

Cause: There was system error during the SSL handshake.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-13381: Timeout during SSL handshake, socket number %s

Cause: There was timeout during the SSL handshake.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-13382: File %s cannot be opened.

Cause: The specified file could not be opened.

Action: Evaluate why the specified file cannot be opened. The file may not be located in the correct directory or permissions on the file may be incorrect. Correct the problem.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-13383: Unable to initialize DNS lookups

Cause: Cannot use DNS for TCP/IP host resolution.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-13400: parsing error of <!-- WEBCACHETAG--> and <!-- WEBCACHEEND--> at offset %d

Cause: An invalid token was encountered in the <!-- WEBCACHETAG--> and <!-- WEBCACHEEND--> tags.

Action: Correct the syntax of the <!-- WEBCACHETAG--> and <!-- WEBCACHEEND--> tags at the specified location in the object.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-13500: Login Information missing for WTI key server \"%s\"

Cause: A key server with the given server name is defined but no login (username, password) information is provided.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Please reconfigure WTI key server section to add the login information for this key server or remove this key server.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-13502: WTI Processor HTML parsing failure.

Cause: A failure is reported by the HTML parser.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Validate this HTML page's syntax.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-13503: WTI HTML parser context creation failure.

Cause: The system may be running low in memory.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Please increase the system memory.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-13504: WTI form descriptor creation failure.

Cause: The system may be running low in memory.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Please increase the system memory.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-13505: WTI processor failed in memory allocation.

Cause: The system may be running low in memory.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Please increase the system memory.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-13508: The WTI processor failed to generate a form descriptor.

Cause: A form descriptor cannot be generated in WTI processor.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Please check other form description generation error messages for detail.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-13509: The WTI processor failed to get a WTI session key.

Cause: A WTI session key cannot be retrieved by the WTI processor.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Please check other messages to find out the specific reason for key retrieval failure.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-13540: WTI processor found request invalid.Error Descriptor:%s

Cause: The cause should be shown by other more detailed messages.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-13541: WTI processor: request MAC verification failed.

Cause: The cause should be shown by other more detailed messages.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-13570: WTI processor found unexpected request parameter ordering.

Cause: The cause should be shown by other more detailed messages.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-13600: Assertion failed.

Cause: Assertion is failed. Diagnostic information is printed in trace dump file.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Contact Oracle Support.
Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-13601: Signal SIGSEGV caught

Cause: Signal SIGSEGV is caught. Diagnostic information is printed in trace dump file.

Action: Contact Oracle Support.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-13602: Signal SIGBUS caught

Cause: Signal SIGBUS is caught. Diagnostic information is printed in trace dump file.

Action: Contact Oracle Support.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-13603: Signal SIGFPE caught

Cause: Signal SIGFPE is caught. Diagnostic information is printed in trace dump file.

Action: Contact Oracle Support.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-13604: Signal SIGSEGV caught

Cause: Signal SIGSEGV is caught. Diagnostic information is printed in trace dump file.

Action: Contact Oracle Support.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-13606: Signal SIGABRT caught

Cause: Signal SIGABRT is caught. Diagnostic information is printed in trace dump file.

Action: Contact Oracle Support.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-13704: Compression error in: %s

Cause: A gzip library call failed.

Action: If the problem persists, contact Oracle Support.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-13705: Oracle Web Cache compresses object. Original size: %d bytes; Compressed size: %d bytes.

Cause: Normal trace behavior.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-13708: Compression is not yielding any benefit.

Cause: Compression was not able to reduce the size of the object.

Action: Disable compression for this object..
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-13709: Compression disabled for invalid MIME type '%.*s'; non-ascii or non-printable

Cause: An invalid MIME type was identified. The MIME type either contained non-ascii characters, or contained non-printable (undisplayable) characters. Compression is disabled for this MIME type.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-13710: Compression disabled for invalid MIME type '%.*s'; too large

Cause: An invalid MIME type was identified. The MIME type was too large to be stored in the MIME type compression table. Compression is disabled for this MIME type.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-13720: Oracle Web Cache disables compression for %s due to a low rate: %d%%.

Cause: Objects with this MIME type, file extension, or both, were compressed three times.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-13722: Compression policy for %s has expired. Re-instrumenting.

Cause: Six hours have passed since the compression setting for this MIME type and file extension were set. As a result, the compression setting was reset.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-13730: Object will be compressed.

Cause: No headers or policies disabled compression, so Oracle Web Cache compressed the object.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-13731: Object is too small to warrant compression.

Cause: The requested object was too small to compress.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-13732: Compression disabled for this object by a Surrogate-control header.

Cause: The Surrogate-Control header indicated that compression should be disabled.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-13733: Compression disabled for this Site.

Cause: An application-specific caching specified that compression should be disabled.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-13734: Compression disabled for this object by caching rule.

Cause: A caching rule specified that compression should be disabled.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-13735: Compression is disabled because the browser has known issues.

Cause: The browser was either Netscape version 4 or less, or it was Internet Explorere version 5.5 or less. These browsers have known issues.

Action: Upgrade the browser.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-13736: Compression is disabled because the browser does not support compression.

Cause: The user's browser does not support compression.

Action: Upgrade the browser.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-13737: Compression is internally disabled for: %s.

Cause: Compression for this object's MIME type or file extension is internally disabled.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-13738: Compression disabled because %s has a low compression rate.

Cause: The compression rate on this MIME type, file extension, or both, was poor. Therefore Oracle Web Cache is disabling compression for this type.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-13817: I/O Logging enabled; using file %s

Cause: As specified, I/O Logging has been enabled using the specified file.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-13818: I/O Logging disabled; file %s could not be accessed

Cause: As specified, I/O Logging has been enabled using the specified file.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-13916: Optimizer failure on pattern '%.*s' - trying original '%.*s'

Cause: The optimized regular expression failed to compile; an attempt was made to compile the original supplied (unoptimized) expression.

Action: No action required.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-14000: unknown internal error

Cause: error number is properly set

Action: check which module is not setting the error number
Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-14001: bad arguments

Cause: bad request

Action: check the code which is sending wrong argument to the calling function
Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-14002: Error while sending the request to origin server (id=%d) %s:%d

Cause: The request to the origin server failed.

Action: Ensure that the origin server is running.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14003: Error while receiving response from the origin server (id=%d) %s:%d

Cause: Oracle Web Cache was unable to receive a response from the origin server.

Action: Ensure that the origin server is running.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14004: HTTP status code error

Cause: The origin server returned a non-HTTP status code.

Action: Check the origin server to determine what application is sending the response.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14005: Content-Type buffer is too small

Cause: The buffer pool memory was not sufficient.

Action: Adjust the maximum individual header size limit in the Security page of Fusion Middleware Control. If the problem persists, contact Oracle Support.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14006: SSL handshake with origin server (id=%d) %s:%d fails.

Cause: The SSL handshake between Oracle Web Cache and the origin server failed.

Action: Check certificate configuration on the origin server.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14007: Connect request terminates.

Cause: The connection request to the origin server was terminated.

Action: If the problem persists, contact Oracle Support.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14008: Create request fails.

Cause: Oracle Web Cache failed to create a request to the origin server.

Action: If the problem persists, contact Oracle Support.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14009: Header operation fails.

Cause: Oracle Web Cache could not write to the HTTP response header from the origin server. This occurs if the Oracle Web Cache computer is experiencing a system memory problem.

Action: If the problem persists, contact Oracle Support.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14010: Invalid authentication credentials for proxy server

Cause: The user name and password for the proxy server failed.

Action: Correct the user name and password in the Origin Servers page of Fusion Middleware Control.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14011: Proxy tunnel authentication required

Cause: The user name and password for the proxy server failed.

Action: Correct the user name and password in the Origin Servers page of Fusion Middleware Control.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14012: Bad response from proxy tunnel

Cause: The proxy tunnel response was incorrect.

Action: Check the proxy server configuration and setup.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14013: Send request to origin server (id=%d) %s:%d times out.

Cause: The request to the origin server exceeded the network timeout limit.

Action: If the problem persists, adjust the network timeout between Oracle Web Cache and the origin server in the Resource Limits page of Fusion Middleware Control.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14014: Receive request from origin server (id=%d) %s:%d timed out.

Cause: The response from the origin server exceeded the network timeout limit.

Action: If the problem persists, adjust the network timeout between Oracle Web Cache and the origin server in the Resource Limits page of Fusion Middleware Control.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14015: Browser terminates connection; the request to the origin server is terminated.

Cause: The browser terminated its connection. As a result, Oracle Web Cache terminated its connection to the origin server.

Action: No action required.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14016: Connection to origin server (id=%d) %s:%d fails.

Cause: The origin server is down.

Action: Check the origin server.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14017: Connection to origin server times out.

Cause: The connection to the origin server exceeded the network timeout limit.

Action: If the problem persists, adjust the network timeout between Oracle Web Cache and the origin server in the Resource Limits page of Fusion Middleware Control.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14018: Socket creation fails for origin server.

Cause: The Oracle Web Cache computer has run short of system resources.

Action: If the problem persists, increase the Maximum Incoming Connections setting in the Resource Limits page Fusion Middleware Control.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14019: Dynamic origin server DNS failure

Cause: The DNS lookup for the ESI provider site failed, because either the site was down or does not exist.

Action: Ensure that the ESI provider site is operational. If it is, check the site configuration in the Sites page of Fusion Middleware Control.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14020: Origin server rejects queue entry.

Cause: The queue to the origin server was full, resulting in the new request not being accepted.

Action: If the problem persists, increase the capacity for the origin server in the Origin Servers page of Fusion Middleware Control.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14021: Capacity, as set by Web Cache, is exceeded for all origin servers that are available for processing this request.

Cause: Oracle Web Cache was unable to forward the request to the origin server, because the origin server reached its capacity and queue limit.

Action: If the problem persists, increase the capacity for the origin server in the Origin Servers page of Fusion Middleware Control.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14022: Load balancing and failover functionality fails.

Cause: All of the origin servers were down. Oracle Web Cache will continue to poll the origin server until they are back online.

Action: Check the state of the origin servers.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14023: No origin server is running.

Cause: All communication to the origin servers has failed. Oracle Web Cache will continue to poll the origin server until they are back online.

Action: Check the state of the origin servers.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14024: Dynamic origin server is not allowed for request.

Cause: The request was for a virtual host site. DNS discovery of origin servers is only permitted for ESI provider sites.

Action: Check the site configuration in the Sites page of Oracle Enterprise Manager or Site Definitions and Site-to-Server Mapping page of Fusion Middleware Control.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14025: Dynamic connection to origin server (id=%d) %s:%d fails.

Cause: Oracle Web Cache received the DNS lookup result for the ESI provider site, but was unable to connect to the site.

Action: Check that the ESI provider site is operational.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14026: Out of memory

Cause: Oracle Web Cache is running out of memory.

Action: No action required.
Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-14027: Connection request to origin server (id=%d) %s:%d times out.

Cause: The connection between Oracle Web Cache and the origin server timed out.

Action: No action required.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14028: incomplete header

Cause: The HTTP response from the origin server did not contain a properly formatted HTTP header.

Action: Check the application sending the response.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14029: invalid header

Cause: The HTTP header response from the origin server contained an invalid field.

Action: Check the application sending the response.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14030: Single response header is too long.

Cause: Origin Server is sending longer header than Oracle Web Cache is expecting.

Action: No Action required
Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-14031: Total header length is too long

Cause: Origin Server is sending longer headers than Oracle Web Cache is expecting.

Action: Check the Origin Server setting.
Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-14032: Buffer finished before \ is found.

Cause: The response from the origin server was not properly formatted.

Action: If the problem persists, check the application sending the response.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14033: Chunk length exceeded more 256 digits.

Cause: Origin Server is sending wrong chunking length header than specified in HTTP specification.

Action: Check the Origin Server setting.
Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-14034: Network %.*s during origin server %.*s (details: internal=%.*s system=%.*s)

Cause: A network operation failure was encountered between the origin server and Oracle Web Cache, so the request could not be completed.

Action: Check network status on the Oracle Web Cache host machine.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14035: strtol utility returned an error.

Cause: Internal string function failed.

Action: No action required.
Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-14036: time overflow

Cause: Invalid time string from Origin Server

Action: Check the Origin Server configuration setting
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14037: illegal time format

Cause: The creation time received from the origin server was for a time in the future.

Action: Check the application sending the response.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14038: invalidation operation

Cause: Internal error

Action: no action required
Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-14039: HTTP response not found

Cause: An HTTP response from the origin server was not found.

Action: Check the application sending the response.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14040: overflow

Cause: Could be wrong time format

Action: no action required
Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-14041: invalid format

Cause: The response contained an invalid time format or inversion of an integer.

Action: No action required.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14044: Unexpected EOF while reading HTTP response-header.

Cause: Connection prematurely closed by origin server.

Action: No action required.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-14045: Error Parsing Chunk Length for %.*s%.*s.

Cause: Incorrect chunk length

Action: No action required.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-14047: Oracle Web Cache encounters an invalid HTTP response.

Cause: An HTTP response from the origin server contained invalid contents. For example, the response indicated chunked contents but the response contained no chunks.

Action: Check the application sending the response.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-14050: The request is granted with view permission for the cached object.

Cause: In response to a security validation request from WebCache on behalf of the request, the origin server responded with "304 Not Modified", with the Surrogate-Control: view-granted token. The cached object will be used to serve the request.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14051: The request is validated with cached version %.*s

Cause: In response to a version validation request from Oracle Web Cache on behalf of the request, the origin server responded with "304 Not Modified", specifying the cached version in the Surrogate-Control: version token to be served to the client.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14052: New content is received from the origin server in response to a validation request from WebCache.

Cause: In response to a security or version validation request from Oracle Web Cache on behalf of the request, the origin server responded with new content. The cached objects will be updated accordingly.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14056: Origin server error: empty version string in Surrogate-Control in the response.

Cause: The response contains an empty Surrogate-Control: version string This will be treated as an invalid response, and an error will be sent to the client.

Action: Check that the origin server has proper support for version validation based caching.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14059: Object validation aborted.

Cause: The response will not be used to update the validation-required entry in the cache because it was determined that it is not cacheable.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14060: The response contains Surrogate-Control: secure-view, indicating the object requires security validation for all cache hits.

Cause: The Surrogate-Control header contains a secure-view token indicating that the cached entry requires security validation for all hits.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14061: The response contains the Surrogate-Control: version token with value %.*s, indicating the object requires version validation for all cache hits.

Cause: The Surrogate-Control header contains a Surrogate-Control: version token indicating that the cached entry requires version validation for all hits.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14062: The validation-required cache entry is updated with new content for an existing version %.*s

Cause: The complete response for an existing version of the validation-required cache entry was successfully received and the version in the entry is updated with the new response.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14063: The validation-required cache entry is updated with content for a new version %.*s

Cause: The complete response for a new version of the validation-required object was successfully received and the cache entry is updated with the new response.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14064: Failed to insert the new version %.*s to the validation-required cache entry as the maximum allowed versions is reached for the entry, and none of the existing versions can be removed.

Cause: The cache entry already contains the maximum allowed number of version objects, and all of them are currently being updated, so the new version received can not be added to the entry.

Action: Adjust the maximum allowed version objects per cache entry if you prefer to have all versions cached.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14066: Origin server denied view permission for the request.

Cause: In response to a security validation request, or Oracle Single Sign-On authentication request from Oracle Web Cache on behalf of the request, the origin server responded with "401 Unauthorized", meaning the user does not have view permission for the requested object in cache.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14067: Origin server error: missing Surrogate-Control: view-granted token in the response for a security validation request from WebCache.

Cause: In response to a security validation request from Oracle Web Cache on behalf of the request, the origin server responded with "304 Not Modified", but without the Surrogate-Control: view-granted token required to indicate that an authorization check has been performed. This will be treated as an invalid response, and an error will be sent to the client.

Action: Check that the origin server has proper support for security validation based caching.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14068: Origin server error: incorrect Surrogate-Control: version string in the response for a version validation request from WebCache.

Cause: In response to a version validation request from Oracle Web Cache on behalf of the request, the origin server responded with "304 Not Modified", but without the Surrogate-Control: version token required to indicate that version check has been performed, or with an incorrect version token that does not match any versions specified in the request. This will be treated as an invalid response, and an error will be sent to the client.

Action: Check that the origin server has proper support for version validation based caching.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14070: Origin server error: unexpected 304 response.

Cause: In response to regular request from Oracle Web Cache with no validation clause, the origin server returned "304 Not Modified". This will be treated as an invalid response, and an error will be sent to the client.

Action: Check that the origin server has proper support for validation based caching.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14071: Unexpected EOF while reading HTTP response-body.

Cause: Connection prematurely closed by origin server.

Action: No action required.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14072: The Location header of the 302 response is not found or is empty.

Cause: The origin server response was a 302 redirect response, but the required Location header was not found or was empty.

Action: Check the application sending the response.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14130: [site #%.*s - %s][filter type: %s][rule #%.*s%s]%.*s[action: allow]

Cause: The request matched a request-filtering rule for a filter type and the action specified for a rule match was allow. Request was allowed for this filter type. The other filter types, if any, were checked.

Action: No action required, unless this action is not the desired behavior.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14131: [site #%.*s - %s][filter type: %s][rule #%.*s%s]%.*s[action: allow - MONITOR ONLY]

Cause: The request matched a request-filtering rule for a filter type and the action specified for a rule match was allow. However, the rule was set to be in monitor-only mode, so the statistics for the rule were updated, but otherwise the rule was treated as disabled. The other rules, if any, for this filter type were checked.

Action: No action required, unless this action is not the desired behavior. This message is for informational purposes.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14132: [site #%.*s - %s][filter type: %s][rule #%.*s%s]%.*s[action: deny - %s]

Cause: The request matched a request-filtering rule for a filter type and the action specified for a rule match was deny. The request was denied.

Action: No action required, unless this action is not the desired behavior.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14133: [site #%.*s - %s][filter type: %s][rule #%.*s%s]%.*s[action: deny - %s - MONITOR ONLY]

Cause: The request matched a request-filtering rule for a filter type and the action specified for a rule match was deny. But the rule is in monitor-only mode, so the statistics for the rule were updated, but otherwise the rule was treated as disabled. The other rules, if any, for this filter type were checked.

Action: No action required, unless this action is not the desired behavior. This message is for informational purposes.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14143: Request filtering needs to check the POST body, but the POST body size exceeds the configured maximum. Oracle Web Cache returns a bad request error response.

Cause: Oracle Web Cache received an HTTP request with a POST body which request filtering must check, but the POST body size exceeds the maximum configured POST ody size. Oracle Web Cache returns a bad request error response.

Action: If the problem persists and rejecting the request is not acceptable, increase the configuration setting for the maximum POST body size if request filtering is needed in the Oracle Web Cache configuration. You configure this setting in the Security page (Properties > Security) of Oracle Web Cache Manager.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-14147: [site #%.*s - %s][filter type: %s][action: no match on any non-MONITOR-ONLY rule, so check other filters]

Cause: The request did not match any request-filtering rule for the Privileged IP filter type which is not a monitor-only rule. Therefore, check the other request filters for this request.

Action: No action required, unless this action is not the desired behavior. This message is for informational purposes.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14153: The request is from a Privileged IP address, so other request filter checks are bypassed.

Cause: The normal request filtering checks were bypassed for this request, because the request is coming from a privileged IP.

Action: No action required, unless this action is not the desired behavior.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-14200: One or more sites are ACL-protected. Initializing secure caching tables.

Cause: Normal notification. At least one site was configured as ACL-protected site. Oracle Web Cache will enable secure caching for those sites.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-14201: XML parser for WebDAV ACL initializes successfully.

Cause: Normal notification. XML parser for WebDAV ACL was initialized successfully.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-14210: Invalid authorization header (%s)

Cause: The authorization header in the request lacked the necessary items or was invalid.

Action: No action required.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14213: The requested object is ACL-protected. Starting ACL evaluation.

Cause: The client requested an object from an ACL-protected site. Therefore, an ACL evaluation was started.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14214: Oracle Web Cache does not have fresh copies of all ACLs. ACL evaluation terminates.

Cause: Required ACL object was missing, stale or in update status. Therefore, ACL evaluation was terminated.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14215: Oracle Web Cache does not have all the necessary information for the requesting user (%s). ACL evaluation terminates.

Cause: The user/group table did not contain an entry of the user or the user's group membership was not updated yet. Therefore, ACL evaluation was terminated.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14216: ACL evaluation completes. Access granted to the user (%s).

Cause: The user has read privilege for the requested URL.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14217: ACL evaluation completes. Access denied for the user (%s).

Cause: The user does not have read privilege for the requested URL.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14221: The response does not contain a valid X-Oracle-Current-User header.

Cause: The response does not contain the X-Oracle-Current-User header or the header is invalid.

Action: No action required.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14225: The insertion of user (%s) to the user/group table fails.

Cause: Oracle Web Cache tried to insert a user entry for the user but failed.

Action: No action required.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-14229: A user and a group have the same principal URL (%s).

Cause: A group had the same principal URL as a user.

Action: Check the origin server's user and group settings.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14233: Propfind request for fetching the password verifier of user (%s) is composed.

Cause: Propfind request for the password verifier of the requesting user was composed.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14234: Propfind request for fetching the group-membership of user (%s) is composed.

Cause: Propfind request for the group membership of the requesting user was composed.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14235: Propfind request for ACL HREF or ancestor ACL HREFs of the resource (%s) is composed.

Cause: Propfind request for ACL HREF, ancestor ACL HREFs, or both ACL HREF and ancestor HREFs was composed.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14236: Request for fetching ACL (%s) is composed.

Cause: Propfind request for fetching ACL object was composed.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14240: Starting post-processing of user password verifier.

Cause: Starting post-processing of password verifier.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14241: Starting post-processing of user groupmembership.

Cause: Starting post-processing of user groupmembership.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14242: Starting post-processing of resource ACL HREF.

Cause: Starting post-processing of resource ACL HREF.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14243: Starting post-processing of ancestor ACL HREFs.

Cause: Starting post-processing of ancestor ACL HREFs.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14244: Starting post-processing of both resource and ancestor ACL HREFs.

Cause: Starting post-processing of both resource and ancestor ACL HREFs.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14245: Starting post-processing of ACL object.

Cause: Starting post-processing of ACL object.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14246: Post processing successfully completes.

Cause: Post processing of fetcher response was completed successfully.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14250: Lexical analysis of XML response fails.

Cause: Transitioned to ERROR state in the lexical transition matrix. This condition might be caused by incorrect definitions of state variables or incorrect transition matrix.

Action: No action required.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14251: The syntax of the XML response is incorrect. Syntax analysis fails (error no: %d).

Cause: The syntax of XML response is wrong and building a syntax tree failed.

Action: No action required.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14252: The XML response has semantic error or the table/cache update fails.

Cause: There might be two possible reasons: (1) The XML response has semantic errors, so the post-processing function could not understand the response and extract necessary authentication data or ACL data from the response. (2) The post-processing function received all the data from the response, but failed upon updating password verifier, user groupmembership, ACL HREFs, or ACL object.

Action: No action required.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14260: No user groupmembership inserted. Data validation fails.

Cause: Oracle Web Cache failed in post-processing and insertion of user group membership. Possible reasons include but may not be limited to: 1) Server did not send a valid response. 2) There is syntax or semantic error in the response. 3) The special Oracle Web Cache user was not configured to have sufficient privileges.

Action: Check related server configuration and resources.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14261: The HREF list is incomplete. Data validation fails.

Cause: Oracle Web Cache could not insert all resource ACL HREF and ancestor ACL HREFs to the HREF list. Possible reasons include but may not be limited to: 1) Server did not send complete HREF list. 2) There is syntax or semantic error in the response. 3) The special Oracle Web Cache user was not configured to have sufficient privileges.

Action: Check related server configuration and resources.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14262: The HREF list is empty. Data validation fails.

Cause: Oracle Web Cache could not get the HREFs from the server or the response has syntax/semantic error. Possible reasons include but may not be limited to: 1) Server did not send valid response. 2) There is syntax or semantic error in the response. 3) The special Oracle Web Cache user was not configured to have sufficient privileges.

Action: Check related server configuration and resources.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14263: Some ACL objects have not been parsed. Data validation fails.

Cause: There is a syntax or semantic error in the ACL object. Oracle Web Cache could not parse it.

Action: Check server ACL objects.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14300: Empty resource HREF header or bad HREF format (%s).

Cause: The server sent an empty X-Oracle-Resource-Acl-Href header or the format of the HREF string is invalid.

Action: Check the X-Oracle-Resource-Acl-Href header in the origin server's response.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14301: Empty resource ancestor HREF header or bad ancestor href format (%s).

Cause: The server sent an empty X-Oracle-Ancestor-Acl-Hrefs header or the format of the ancestor HREF string is invalid.

Action: Check the X-Oracle-Ancestor-Acl-Href header in the origin server's response.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-15000: Requested resource has been moved permanently.

Cause: The requested resource was assigned a new permanent URI. Any future references to this resource should use the returned URI.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-15001: Requested resource has been moved temporarily.

Cause: The requested resource temporarily resided under a different URI.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-15002: Oracle Web Cache generates an HTTP 200 OK status code for a request with an Oracle-Web-Cache-Ping header.

Cause: The request completed successfully.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-15003: Cache entry requires validation. The request will be forwarded to the origin server with a validation clause added.

Cause: Cache entry is marked to require validation. Oracle Web Cache will add a conditional validation header "Oracle-Oracle Web Cache-Validate" to the request, listing the content information it has in the cache, and forward the modified request to the origin server. The origin server can respond with a full response, or a 304 Not Modified response to indicate to Oracle Web Cache that certain cached content can be used to service the request.

Action: No action required
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-15004: Invalid regular expression found in User-Agent remap rule. %s

Cause: The remap rule contained an invalid regular expression that could not be compiled.

Action: Correct the regular expression in the remap rule.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-15005: Parse error on URL: %.*s - invalid URL but continuing with processing

Cause: The input URL was invalid. Oracle Web Cache continued processing, but the origin server probably returned a bad request (400) response.

Action: Ensure that the URL uses valid HTTP syntax.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-15006: Problem normalizing '%.*s'; continuing with original value

Cause: Attempt to normalize the input string failed.

Action: Ensure user supplied URI or host name is properly HTTP encoded.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-15101: Address resolution of Oracle Web Cache's listening endpoint \"%s\" fails.

Cause: There was a problem in DNS.

Action: Check DNS configuration on the local machine.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-15102: CRL directory does not exist.

Cause: CRL is enabled for one of the listening endpoints, but the CRL directory does not exist.

Action: Contact Oracle Support.
Level: 1

Type: ERROR

Impact: Configuration

WXE-15300: Request for cached document is denied

Cause: The request sender was not authorized to access the object.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-15400: An orcl_wx_repost parameter is found with a non-GET request.

Cause: The request URL contained the special orcl_wx_repost parameter, but the request method was not a GET. The parameter will be stripped and the request processed as a regular request.

Action: No action required.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-15402: The orcl_wx_repost parameter is invalid.

Cause: The request URL contained the special orcl_wx_repost parameter, but its value was empty or invalid. It will be stripped from the URL, the request will be converted to a POST request with an empty body, and an additional request header Oracle-Oracle Web Cache-RePOST with the special value of UID=failed-restore will be sent to the origin server.

Action: No action required.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-15403: Forwarding the restore POST request to the owner cache of the POST data

Cause: This cache was not the owner of the POST data specified by the request. The request will be forwarded as is to the owner cache.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-15404: Failed to find POST data with key %.*s.

Cause: The POST data entry specified by the request was not found in the cache. It is either expired or the cache key was invalid. The orcl_wx_repost parameter will be stripped from the URL, the request will be converted to a POST request with an empty body, and an additional request header Oracle-Oracle Web Cache-RePOST with the special value of UID=failed-restore will be sent to the origin server.

Action: No action required.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-15405: POST data successfully restored.

Cause: Cache lookup of the POST data entry specified by the request was successful. The request has been converted to POST with the looked up POST content. The URL parameter orcl_wx_repost will be stripped and the restored request will be forwarded to the origin server.

Action: No action required.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-15406: The orcl_wx_sid parameter is invalid.

Cause: The request URL contained the special orcl_wx_sid parameter, but its value was empty or invalid. It will be stripped from the URL, and the request will be treated as it would be without the parameter.

Action: No action required.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-17001: A duplicate POST data cache insertion is found with key %.*s. POST data cache insertion fails.

Cause: An existing POST data cache entry existsed with the same key as the current one.

Action: Check the origin server to ensure no duplicate keys are sent for POST data records.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-17005: POST data cache insertion failed with key %.*s because the POST data is too large.

Cause: POST data was too large.

Action: Edit webcache.xml and find the POSTBODYCACHE element under the GENERAL element. Increase the MAXCACHEABLESIZE attribute to the desired value.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-17101: No matching cookies are found for cookie caching.

Cause: No cacheable cookies were found in the response.

Action: See the Oracle Access Manager Integration Guide.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-17102: A duplicate cookie cache insertion is found with key %.*s. Cookie cache insertion fails.

Cause: An existing cookie cache entry existed with the same key as the current one. This could be caused by concurrent requests from the same browser.

Action: See the Oracle Access Manager Integration Guide.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-17110: Previously saved cookies are added to the request.

Cause: A cookie record associated with the user was found and the cookies saved in the record were added to the request.

Action: See the Oracle Access Manager Integration Guide.
Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-17112: Cookie cache is enabled with no SSL enabled listen ports for browser requests.

Cause: The cookie cache feature only works for requests made over SSL connections. The configuration contained the switch that enables cookie caching but no listen ports for browser requests are SSL enabled.

Action: See the Oracle Access Manager Integration Guide.
Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-17113: Oracle Web Cache encountered an error while obtaining SSL session ID for cookie cache operations. NZE-%d

Cause: While trying to retrieve the SSL session ID needed by the cookie cache, an error occured. Cookie cache operations for this request will not succeed.

Action: See the Oracle Access Manager Integration Guide.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-19000: Audit initialization failed. Oracle Web Cache starts with audit logging disabled.

Cause: The audit library failed to initialize.

Action: If the problem persists, contact Oracle Support.
Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-20101: Open socket fd=%d exceeded FDArr_Size %d.

Cause: Potential file descriptor leakage.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Contact Oracle Support.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-20150: Failure in scheduling asynchronous task: %s.

Cause: Potential memory shortage. Note: This is for all asynchronous functions.

Action: This message is no longer used as of Oracle Fusion Middleware 11g. Contact Oracle Support.
Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-21271: Member cache ID is invalid (id=%d), %s.

Cause: This is a potential logic error. Param %s Desiree where the error happens

Action: Contact Oracle Support.
Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

108 XDF-10001 to XDF-10571

XDF-10001: BstrapObject::readInputSXML(): Issue with bootstrap config file.

Cause: Incorrect Bootstrap config file

Action: Provide a correct Bootstrap config file
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10002: BstrapObject::readFileToGetCommand(...): File {0} not found in the jar.

Cause: Missing a file in the applxdf.jar

Action: Check if the applxdf.jar is an valid jar
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10003: There was an error during XDF deployment(standalone=Y),check the log for detail

Cause: An error in XDF deployment

Action: Check the log for detail, fix the issue
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10004: There was an error running the SQL/PLSQL scripts, check the log for detail

Cause: An error running the SQL/PLSQL scripts

Action: Check the log for detail, fix the issue
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10005: There was an error during XDF deployment(standalone=N),check the log for detail

Cause: An error in XDF deployment

Action: Check the log for detail, fix the issue
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10006: BstrapObject::getConnection(): Could Not Get DB Connection

Cause: An error in database connection

Action: Fix database connection errors
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10007: DataCollect::getMVLogTableSpace(...): Table space is null.

Cause: Table space is null

Action: Fix Table space error
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10008: DBObject::readInputSXML: Null or Empty XML Document.

Cause: Invalid SXML file

Action: Use an valid SXML object file.
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10010: DBObject::stripRowTag(...): SXML Object File is null!

Cause: Invalid SXML file

Action: Use an valid SXML Object file
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10011: DBObject::stripRowTag(...): Could not get Object File Document Root!

Cause: Incorrect SXML file format

Action: Fix SXML file errors or select a correct SXML file
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10012: DBObject::stripRowTag(...): Invalid DB Object File Format!

Cause: Incorrect SXML file format

Action: Fix SXML file errors or select a correct SXML file
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10013: DBObject::executeDDLStmt: The statement is invalid and could not be executed!

Cause: An invalid DDL statement

Action: Check and fix Object file
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10014: DBObjectComparision::doCompare(): The object type {0} is not recognized.

Cause: Incorrect object type

Action: Fix object type in the SXML file
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10015: DBUtil::executeConsDDLSt: No connection available!

Cause: NO database connection

Action: Fix database connection errors
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10016: DBUtil::executeConsDDLSt: The statement is invalid and could not be executed!

Cause: An invalid ConsDDL statement

Action: Fix the SXML file
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10017: The statement is invalid and could not be executed!

Cause: An invalid DDL statement

Action: Fix the SXML file
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10019: MViewObject::getRemapParameters(): Could not retrieve tablespace information for object {0}.

Cause: May be caused by an invalid tspaceconfig file

Action: Check if a valid tspaceconfig file in the applxdf.jar
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10020: MVLogObject::getRemapParameters(): Could not retrieve tablespace information for object {0}.

Cause: Error in getting tablespace from target database

Action: XDF team debugs
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10021: BstrapObject::executeDDLSt: No connection available!

Cause: NO database connection

Action: Fix database connection errors
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10022: DBUtil::returnsRecord(...): No connection available!

Cause: NO database connection

Action: Fix database connection errors
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10023: DBUtil::getConsFromDB(...): No connection available!

Cause: NO database connection

Action: Fix database connection errors
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10024: DBUtil::dropConst(...): No connection available!

Cause: NO database connection

Action: Fix database connection errors
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10025: DBUtil::getConsColsFromDB: No connection available!

Cause: NO database connection

Action: Fix database connection errors
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10026: DBUtil::isConsNameInDB: No connection available!

Cause: NO database connection

Action: Fix database connection errors
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10027: IndexObject::renameIndex(...):No DB connection available.

Cause: NO database connection

Action: Fix database connection errors
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10028: IndexObject::isIntable(): No DB connection available.

Cause: NO database connection

Action: Fix database connection errors
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10029: IndexObject::isUniqueMatch:No DB connection available.

Cause: NO database connection

Action: Fix database connection errors
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10031: Value exceed {0} characters.

Cause: Too many characters or value to large

Action: Change value within the boundary
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10032: {0}={1}

Cause: Too many characters or value too large

Action: Change value within the boundary
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10033: The format for "{0}" pair is incorrect. Please check.

Cause: Parameters incorrect errors

Action: Fix incorrect parameters
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10034: Argument {0} is not recognized

Cause: Incorrect parameters in XdfSchemaDeploy

Action: Remove an incorrect parameters from command line
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10036: No Object Mode is provided!

Cause: No Object Mode is provided

Action: Provide Object Mode in the command line
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10037: Invalid Object Mode!

Cause: Invalid Object Mode

Action: Provide the correct Object Mode
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10038: No JDBC DB Address be provided!

Cause: No JDBC Address is provided

Action: Provide JDBC address
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10039: No JDBC Protocol be provided!

Cause: No JDBC Protocol is provided

Action: Provide JDBC Protocol
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10040: No Apps User Name be provided!

Cause: No Apps User Name is provided

Action: Provide Apps User Name
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10041: No Owner User Name be provided!

Cause: No Owner User Name is provided

Action: Provide Owner User Name
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10042: Object File Name is blank.

Cause: Object File Name is blank

Action: Provide the Object File Name.
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10043: Editioning View option contradicts with stand alone option!

Cause: Editioning View option can only be with standalone=n.

Action: Re-enter the options.
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10046: IO Exception when getting password.

Cause: IO Exception when getting password.

Action: Try again
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10501: Error on getting the revoke Grants statement: {0}

Cause: UNKNOWN

Action: Follow the error message detail to debug
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10502: Error on giving grant to the role: {0}

Cause: UNKNOWN

Action: Follow the error message detail to debug
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10504: Error on revoking Grants: {0}

Cause: UNKNOWN

Action: XDF team debugs
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10519: XDFLogger::log: Date format error.

Cause: Date format error

Action: XDF team debugs
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10520: XDFLogger::levelMap: Level number format error.

Cause: Incorrect level number

Action: XDF team debugs
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10521: ViewObject::dropView: Error while dropping view {0}.{1}

Cause: Cannot drop a view

Action: Check drop a view permission
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10525: XdfSchemaDeploy::applyXDF: The Role deployment NOT in a valid context.

Cause: Role deployment not in schema separation context

Action: Make sure the deployment run in schema separation option
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10526: XdfSchemaDeploy::applyXDF: The object type {0} is not recognized.

Cause: Incorrect object type

Action: FIX object type and re-run
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10531: XMLUtil::processorSetParam: Invalid value type in the hash table.

Cause: XMLUtil::processorSetParam: Invalid value type

Action: XDF team debugs
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10535: Invalid tablespace config file. Check and correct the file format.

Cause: Tablespace config file is null/empty/format error.

Action: Fix Tablespace config file and re-run
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10536: Invalid Tablespace Config File Format!

Cause: Invalid Tablespace Config File Format

Action: Fix Tablespace config file and re-run
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10537: TspaceConfig::loadTspaceConfig(): Implicit classification not in correct format.

Cause: TspaceConfig: Implicit classification not in correct format

Action: Fix Tablespace config file and re-run
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10538: In tablespce config file: Type-Value classification not in correct format.

Cause: TspaceConfig:Type-Value classification incorrect

Action: Fix Tablespace Type-Value classification and re-run
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10539: SQL Error: Missing FND_CLEANUP_PKG package in the target database.

Cause: Missing FND_CLEANUP_PKG package in the target database

Action: Re-run bootstrap mode to install FND_CLEANUP_PKG package
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10546: Unable to find Application Short Name.

Cause: No Application Short Name defined in the Object file

Action: Add Application Short Name
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10548: TableObject::getRemapParameters: Could not retrieve tablespace information for table {0}

Cause: Error in the process of getting tablespace information from config file

Action: XDF team debugs
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10549: Could not find the tablespace type for tablespace: {0}. Check if the tablespace exists or is valid in the target DB.

Cause: Incorrect Tablespace type

Action: Check if the tablespace exists or is valid in target DB.
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10560: compareTable/column Comment failed

Cause: UNKNOWN

Action: Follow the error message detail to debug
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10561: TableComparison::doObjectCmp:Executing comment statement: {0}

Cause: Failed executing comment statement

Action: Fix SXML file
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10562: Table SXML clob to xml doc processing error: {0}

Cause: UNKNOWN

Action: Follow the error message detail to debug
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10563: Alter Table Exception: {0}

Cause: Error in the alter table process, reason unknown

Action: XDF team debugs
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10564: DBUtil::isConsNameInDB: No connection available!

Cause: No database connection

Action: Fix database connection
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10565: Exit Status is 1!

Cause: Encountered error during the deployment

Action: Check the log for error details.
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10566: Not an empty table, could not add a NOT NULL column.

Cause: The table in the database has data.

Action: Modify the Object definition.
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10567: Could not modify the column to NOT NULL.

Cause: The table has null values on current column.

Action: Provide a default column value.
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10568: Could not get tablespace mappings from tablespace config file.

Cause: Read tablespace config file error.

Action: XDF team debug.
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10569: Error in loading/updating tablespace mappings; Exit the tool.

Cause: Read tablespace config file error.

Action: XDF team debug.
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10570: There was an error running the recompile package script.

Cause: An error on running the recompile packages SQL/PLSQL script.

Action: Check the XDF packages to fix the issue.
Level: 1

Type: ERROR

Impact: Application Diagnostics

XDF-10571: The XDF_MODE argument: {0} mismatches the XDF object file type: {1}.

Cause: User command line input error.

Action: Correct input arguments of XDF_MODE and/or XDF_FILE_NAME.
Level: 1

Type: ERROR

Impact: Application Diagnostics

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2014, Oracle and/or its affiliates. All rights reserved.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.